Communication method and related apparatus

Abstract

A communication method and a related apparatus, relating to the technical field of communications. The communication method comprises: when a first trigger condition is satisfied, a relay node sending first information to a first host node, wherein the first information comprises the result of establishing a first F1 interface between the relay node and a target host node. In the present method, the first information is sent to the first host node, so that the first host node determines that the relay node has not established an F1 interface with a second host node indicated thereby, and / or the first host node determines that the relay node has established an F1 interface with a target host node configured by a network administrator, thereby enabling the first host node to initiate a UE handover procedure to the correct host node (that is, the target host node), avoiding a situation in which the relay node cannot complete DU migration normally due to conflict between CU triggering and OAM triggering, and ensuring that the relay node completes DU migration smoothly.

Description

Communication method and related device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 27, 2023, with application number 202311271246.8, and priority to the Chinese patent application entitled “Communication Methods and Related Devices”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method and related devices. Background Art

[0003] Compared to the fourth-generation mobile communication system, the fifth-generation (5G) and future mobile communication systems impose even more stringent requirements on various network performance indicators. For example, 5G boasts a 1,000-fold increase in capacity compared to 4G, requiring wider coverage, ultra-high reliability, and ultra-low latency. Given the abundance of high-frequency carrier frequency resources, the use of high-frequency small cell networks is becoming increasingly popular in hotspots to meet the ultra-high capacity requirements of 5G. Due to the poor propagation characteristics of high-frequency carriers, severe attenuation due to obstruction, and limited coverage, a large number of small cells need to be deployed densely. However, providing fiber backhaul for these densely deployed small cells is costly and difficult to implement, necessitating the need for economical and convenient backhaul solutions. Furthermore, to meet the need for wide coverage, fiber deployment is challenging and expensive in remote areas, necessitating the design of flexible and convenient access and backhaul solutions. Integrated access and backhaul (IAB) technology provides a solution to the above two problems: its access link (access link) and backhaul link (backhaul link, BL) both adopt wireless transmission solutions, reducing the deployment of optical fibers.

[0004] In an IAB network, a relay node (RN), also known as an IAB node, provides wireless access services and forwards service data for user equipment (UE). The UE's service data is transmitted by the IAB node via a wireless backhaul link to an IAB donor, also known as a donor node or donor gNodeB (DgNB). An IAB node consists of a mobile termination (MT) and a distributed unit (DU). When facing its parent node, the IAB node acts as a terminal device, i.e., the MT. When facing its child node (which may be another IAB node or a UE), it is considered a network device, i.e., the DU. A donor base station (DgNB) can be an access network element with full base station functionality, or an access network element with a separate centralized unit (CU) and distributed unit (DU). The host base station is connected to the core network element (e.g., connected to the 5G core network) serving the UE and provides wireless backhaul functionality for the IAB node.

[0005] In the IAB network, the DU migration of the IAB node supports two triggering modes: source CU triggering and operation administration and maintenance (OAM) triggering. In the source CU triggering mode, the source CU will send an indication message carrying the target CU to the DU in the IAB node, and the DU will complete the migration operation based on the indication message. The source CU is the CU connected to the DU before the migration, and the target CU is the CU connected to the DU after the migration. In the OAM triggering mode, the OAM server can be directly pre-configured in the IAB node or remotely trigger the IAB node to perform DU migration. However, the source CU triggering and the OAM triggering will conflict, resulting in the IAB node being unable to complete the DU migration normally.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide a communication method and related devices, which enable an IAB node to handle trigger conflicts caused by CU triggering and OAM triggering when performing DU migration, thereby ensuring that the IAB node completes DU migration.

[0008] In the application, the CU (or host) to which the MT is connected and the CU (or host) to which the DU is connected refer to logical connections, which do not represent direct physical connections. For example, the MT has a radio resource control (RRC) connection with the CU to which it is connected, and the DU has an F1 interface connection with the CU to which it is connected. Moreover, the logical connection may be in a state that is about to be established (for example, the DU has determined that an F1 connection will be established with a certain CU, but the F1 interface has not yet been established, and the establishment of the F1 interface is about to be initiated), or in a state that has already been established (for example, the DU has already established an F1 interface with the CU to which it is connected). In this application, the migration of a relay node generally refers to the migration of a DU in a relay node.

[0009] In a first aspect, embodiments of the present application provide a communication method that can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method is applied to a relay node and includes:

[0010] When the first trigger condition is met, the relay node sends the first information to the first host node; the first information includes the result of the relay node establishing the first F1 interface with the target host node and the identifier of the target host node; or, the first information includes the result of the relay node establishing the first F1 interface with the target host node, the identifier of the target host node, and the triggering method of the DU migration of the relay node;

[0011] The first trigger condition includes at least one of the following:

[0012] Based on the second information provided by the network management, the second information is used to instruct the relay node to establish the first F1 interface with the target host node; or, the relay node receives third information from the first host node, and the third information is used to instruct the relay node to establish a second F1 interface with a second host node, and the second host node is different from the target host node.

[0013] In an embodiment of the present application, a communication method is provided, in which the relay node sends a first message to the first host node when a first trigger condition is met. The first message includes the result of the relay node establishing a first F1 interface with the target host node, carries the identifier of the target host node and / or the triggering method of the DU migration, and the target host node is different from the second host node, so that the first host node knows that the relay node has not established an F1 interface with the second host node indicated by it, and / or lets the first host node know that the relay node has established an F1 interface with the target host node configured by the network management, so that the first host node can initiate the UE switching process to the correct host node (i.e., the target host node), avoiding the situation where the relay node cannot complete the DU migration normally due to a conflict between the CU trigger and the OAM trigger, and ensuring that the relay node successfully completes the DU migration.

[0014] The relay node in the embodiments of the present application can be a device equipped with a processor / chip capable of executing computer-executable instructions, or a processor / chip capable of executing computer-executable instructions. The relay node in the embodiments of the present application includes a terminal-side portion facing the parent node and a network-side portion facing the child node. For example, it can include a mobile operator (MT) and a user-defined unit (DU), or it can include an MT and a gNB, although this is not limited in the embodiments of the present application. The DU migration of the relay node is completely decoupled from the MT migration. Therefore, the host node connected to the MT of the relay node and the host node connected to the DU can be different or the same. For example, the MT and DU of the relay node are both connected to the first host node. For another example, the MT of the relay node is connected to the second host node, and the DU of the relay node is connected to the first host node. When the communication method in the embodiments of the present application is applied to an IAB network, the relay node can be an IAB node, the DU of the IAB node is connected to the first host node, and the host node connected to the MT of the IAB node is not limited in the embodiments of the present application. For example, it can be the first host node, the second host node, or the target host node.

[0015] The first host node in the embodiment of the present application may be a device equipped with a processor / chip that can be used to execute computer-executable instructions, or a processor / chip that can be used to execute computer-executable instructions. The first host node in the embodiment of the present application is the source CU corresponding to the DU of the relay node, and the first host node is connected to the DU of the relay node before the relay node performs DU migration. When the communication method in the embodiment of the present application is applied to an IAB network, the relay node may be an IAB node, and the first host node may be connected to the DU of the IAB node.

[0016] The second host node and the target host node in the embodiment of the present application can be devices equipped with a processor / chip that can be used to execute computer-executable instructions, or can be a processor / chip that can be used to execute computer-executable instructions. The second host node in the embodiment of the present application is the wrong host node after the DU is migrated, and the target host node is the correct host node after the DU is migrated. For example, in the case of a trigger conflict, the instruction triggered by the network manager shall prevail, then the host node indicated by the network manager is the correct host node, and the host node indicated by the first host node is the wrong host node. For example, in the case of a trigger conflict, the instruction triggered by the network manager shall prevail, the network manager instructs to migrate the DU of the relay node to the third host node, and the first CU instructs to migrate the relay node to the fourth host node. Then, the third host node is the correct host node, and the fourth host node is the wrong host node.

[0017] The network manager in the embodiment of the present application can be a device equipped with a processor / chip that can be used to execute computer-executable instructions, or it can be a processor / chip that can be used to execute computer-executable instructions. The network manager in the embodiment of the present application is the network manager of the relay node, which can communicate with the relay node. The network manager usually refers to an operation, management and maintenance (orchestration and management, OAM) server. The OAM trigger mentioned above usually refers to the OAM instructing the relay node to perform DU migration through pre-configuration or remote control. When the communication method in the embodiment of the present application is applied to the IAB network, the network manager can be an OAM server, and the OAM server can be connected to the IAB node. For example, the OAM is connected to the IAB node through the PDU session of the MT, or the OAM is directly connected to the IAB node through the IP network. The embodiment of the present application does not limit this.

[0018] The first trigger condition in the embodiments of the present application includes, but is not limited to: based on second information provided by the network manager, the second information is used to instruct the relay node to establish a first F1 interface with the target host node. Alternatively, the relay node receives third information from the first host node, the third information is used to instruct the relay node to establish a second F1 interface with a second host node, the second host node being different from the target host node.

[0019] In embodiments of the present application, the first information includes the result of establishing the first F1 interface between the relay node and the target donor node. This result may be, for example, that the relay node and the target donor node have completed establishing the F1 interface, or that the relay node and the target donor node have not completed establishing the F1 interface, etc., which is not limited in embodiments of the present application. Optionally, the first information may be carried in an F1 application protocol (F1AP) message, which may also carry an identifier of the target donor node, such as a gNB ID and / or IP address. Carrying the identifier of the target donor node in the first information facilitates communication between the first donor node and the target donor node and instructs the target donor node to perform UE handover. In one possible embodiment, the identifier of the target donor node carried in the first information may also be represented by an identifier of a target cell (i.e., a cell under the target DU) (e.g., an NR Cell Global Identity (NCGI)). The first donor node may obtain the identifier of the target donor node based on the identifier of the target cell.

[0020] In some scenarios, the first message may also carry a triggering method for DU migration (for example, an OAM trigger). Specifically, in a scenario where a CU trigger and an OAM trigger conflict, the OAM trigger shall prevail. Carrying the triggering method for DU migration (for example, an OAM trigger) in the first message can inform the first host node why the relay node did not establish the F1 interface according to its instructions.

[0021] Optionally, the first information can be carried in a class 1 RESPONSE message or a REJECT / FAILURE message of the F1 message triggered by the CU, and can also be carried in a separate class 2 message. Among them, the class 1 message needs to get a response from the other end, and the class 2 message does not need to get a response from the other end. For example, the relay node sends a class 1 message (such as RESPONSE / REJECT / FAILURE) to the first host node in response to another class 1 message (such as REQUEST) sent by the first host node to the relay node. When the relay node sends a class 2 message to the first host node, it does not need to be a response message to a specific message, and the class 2 message can be understood as a notification message.

[0022] The second information may be information pre-configured by the network administrator. For example, the pre-configured information instructs the relay node to perform DU migration at a specified time point. Specifically, the pre-configured information instructs the relay node to begin DU migration one hour after joining the network. The embodiments of this application do not limit the pre-configuration method or the content of the pre-configuration information. The second information may also be sent to the relay node by the network administrator via remote control. For example, the network administrator may send the second information to the relay node via a PDU session of the MT or an IP network.

[0023] It is understood that when the first trigger condition is met, the relay node generates the first information, and the first trigger condition in this case can be understood as a condition that triggers the relay node to generate the first information. Optionally, when the first trigger condition is met, the relay node also sends the first information, and the first trigger condition in this case can be understood as a condition that triggers the relay node to generate and send the first information.

[0024] In the IAB network, the DU migration of the IAB node supports two triggering modes: source CU triggering and OAM triggering. In the source CU triggering (hereinafter referred to as "CU triggering") mode, the source CU will send an indication message carrying the target CU to the DU in the IAB node, and the DU will complete the migration operation based on the indication message. The source CU is the CU connected to the DU before the migration, and the target CU is the CU connected to the DU after the migration. In the OAM triggering mode, the OAM server can be directly pre-configured in the IAB node or remotely trigger the IAB node to perform DU migration. Obviously, both CU triggering and OAM triggering can instruct the relay node to perform DU migration. If the CU triggering and OAM triggering occur at the same time, the relay node may not be able to complete the DU migration normally, or may migrate to the wrong host node. In addition, in the case of a conflict between the two triggers, at least one trigger indication (such as CU triggering) is not completed, which may also cause abnormalities such as control failure and information transmission errors.

[0025] In the implementation manner of the present application, a first trigger condition for generating (or generating and sending) the result of establishing an F1 interface between the relay node and the target host node is clearly given, wherein the result of establishing the F1 interface can be used to enable the first host node to send UE switching indication information to the correct host node, thereby avoiding the situation where the DU migration of the relay node cannot be completed normally or the migration is erroneous. When the relay node meets the first trigger condition, the relay node can generate (or generate and send) the first information in a timely manner, so that the first host node can initiate a user equipment (UE) switching request to the correct host node (target host node) according to the first information, so that the relay node can complete the DU migration normally, and avoid the relay node's DU migrating to the wrong host node.

[0026] In one possible implementation, when the first trigger condition is not met, for example, no F1 interface is established based on the second information (for example, the second information does not exist), or the second host node is the same as the target host node, when the result of establishing the first F1 interface with the target host node is sent to the first host node, the identifier of the target host node is not carried, and optionally, a triggering method for DU migration can be carried. Through this implementation, the first host node can be implicitly indicated that the target host node is the one selected by the first host node, or is the same as the one selected by the first host node, so that the signaling overhead is reduced under the premise that the first host node can correctly judge the target host node.

[0027] In a possible implementation manner, the result of the first F1 interface is that the F1 interface between the relay node and the target host node is established.

[0028] In the embodiment of the present application, the result of the first F1 interface is that the F1 interface between the relay node and the target host node is established (completed), wherein the target host node is different from the host node indicated by the CU trigger, or the target node is not indicated by the CU trigger. The relay node sends the information that its F1 interface establishment is completed to the first host node through the first information, so that the first host node can instruct the correct host node (target host node) to perform UE switching, so that the relay node can successfully complete the DU migration.

[0029] In a possible implementation manner, the second information is further used to trigger the release of the second F1 interface.

[0030] In the embodiments of the present application, the second information is used to instruct the relay node to establish a first F1 interface with the target host node. The second F1 interface is the F1 interface between the relay node and the second host node. If the relay node has already established the second F1 interface with the second host node before receiving the second information, the second information is used to trigger the release of the second F1 interface. This enables the relay node to establish the first F1 interface with the target host node. In addition, this can save resources of the second host node and facilitate the second host node to establish F1 interfaces with other relay nodes.

[0031] Optionally, the second information provided by the network management is equivalent to an OAM trigger, and the OAM trigger may occur after the CU trigger and before the relay node receives the second F1 interface establishment completion message. For example, the OAM trigger may occur after the relay node sends the F1 interface establishment message to the second host node and before the relay node receives the F1 SETUP RESPONSE message from the second host node.

[0032] In a possible implementation manner, the first information further includes an identifier of the target host node and / or a triggering method for the DU migration.

[0033] In an embodiment of the present application, the identifier of the target host node may be, for example, a gNB ID and / or an IP address. The triggering method for DU migration may be, for example, an OAM trigger. The first message carries the identifier of the target host node, which facilitates communication between the first host node and the target host node and instructs the target host node to perform UE handover. The first message carries the triggering method for DU migration, which allows the first host node to know the reason why the relay node did not establish the F1 interface according to its instructions. The identifier of the target host node may also be represented by the identifier of the target cell (e.g., NCGI). The first host node may obtain the identifier of the target host node based on the identifier of the target cell.

[0034] Optionally, when the first F1 interface is an F1 interface established by an OAM trigger indication and / or the OAM trigger is inconsistent with the CU trigger, the first information may include a triggering mode for DU migration.

[0035] Optionally, the first information can be carried in a class 1 RESPONSE message or a REJECT / FAILURE message of the F1 message triggered by the CU, or in a separate class 2 message. Among them, the class 1 message needs to get a response from the other end, and the class 2 message does not need to get a response from the other end. For example, the relay node sends a class 1 message (such as RESPONSE / REJECT / FAILURE) to the first host node in response to another class 1 message (such as REQUEST) sent by the first host node to the relay node. When the relay node sends a class 2 message to the first host node, it does not need to be a response message to a specific message, and the class 2 message can be understood as a notification message.

[0036] In a second aspect, embodiments of the present application provide a communication method that can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method is applied to a first host node and includes:

[0037] When the first trigger condition is met, the first host node receives first information from the relay node; the first information includes a result of the relay node establishing the first F1 interface with the target host node and an identifier of the target host node; or, the first information includes a result of the relay node establishing the first F1 interface with the target host node, an identifier of the target host node, and a triggering method for DU migration of the relay node;

[0038] The first trigger condition includes at least one of the following:

[0039] Based on the second information provided by the network management, the second information is used to instruct the relay node to establish the first F1 interface with the target host node; or, the relay node receives third information from the first host node, and the third information is used to instruct the relay node to establish a second F1 interface with a second host node, and the second host node is different from the target host node.

[0040] The relay node in the embodiments of the present application can be a device equipped with a processor / chip capable of executing computer-executable instructions, or a processor / chip capable of executing computer-executable instructions. The relay node in the embodiments of the present application includes a terminal-side portion facing the parent node and a network-side portion facing the child node. For example, it can include a mobile operator (MT) and a user-defined unit (DU), or it can include an MT and a gNB, although this is not limited in the embodiments of the present application. The DU migration of the relay node is completely decoupled from the MT migration. Therefore, the host node connected to the MT of the relay node and the host node connected to the DU can be different or the same. For example, the MT and DU of the relay node are both connected to the first host node. For another example, the MT of the relay node is connected to the second host node, and the DU of the relay node is connected to the first host node. When the communication method in the embodiments of the present application is applied to an IAB network, the relay node can be an IAB node, the DU of the IAB node is connected to the first host node, and the host node connected to the MT of the IAB node is not limited in the embodiments of the present application. For example, it can be the first host node, the second host node, or the target host node.

[0041] The first host node in the embodiment of the present application may be a device equipped with a processor / chip that can be used to execute computer-executable instructions, or a processor / chip that can be used to execute computer-executable instructions. The first host node in the embodiment of the present application is the source CU corresponding to the DU of the relay node, and the first host node is connected to the DU of the relay node before the relay node performs DU migration. When the communication method in the embodiment of the present application is applied to an IAB network, the relay node may be an IAB node, and the first host node may be connected to the DU of the IAB node.

[0042] The second host node and the target host node in the embodiment of the present application can be devices equipped with a processor / chip that can be used to execute computer-executable instructions, or can be a processor / chip that can be used to execute computer-executable instructions. The second host node in the embodiment of the present application is the wrong host node after the DU is migrated, and the target host node is the correct host node after the DU is migrated. For example, in the case of a trigger conflict, the instruction triggered by the network manager shall prevail, then the host node indicated by the network manager is the correct host node, and the host node indicated by the first host node is the wrong host node. For example, in the case of a trigger conflict, the instruction triggered by the network manager shall prevail, the network manager instructs to migrate the DU of the relay node to the third host node, and the first CU instructs to migrate the relay node to the fourth host node. Then, the third host node is the correct host node, and the fourth host node is the wrong host node.

[0043] The network manager in the embodiment of the present application can be a device equipped with a processor / chip that can be used to execute computer-executable instructions, or it can be a processor / chip that can be used to execute computer-executable instructions. The network manager in the embodiment of the present application is the network manager of the relay node, which can communicate with the relay node. The network manager usually refers to an operation, management and maintenance (orchestration and management, OAM) server. The OAM trigger mentioned above usually refers to the OAM instructing the relay node to perform DU migration through pre-configuration or remote control. When the communication method in the embodiment of the present application is applied to the IAB network, the network manager can be an OAM server, and the OAM server can be connected to the IAB node. For example, the OAM is connected to the IAB node through the PDU session of the MT, or the OAM is directly connected to the IAB node through the IP network. The embodiment of the present application does not limit this.

[0044] In an embodiment of the present application, the first information includes a result of establishing a first F1 interface between the relay node and the target donor node. This result may be, for example, that the relay node and the target donor node have completed establishing the F1 interface, or that the relay node and the target donor node have not completed establishing the F1 interface, etc., which is not limited in the embodiment of the present application. The first information may be, for example, a message carried in an F1 application protocol (F1AP), which carries an identifier of the target donor node, such as a gNB ID and / or an IP address. Carrying the identifier of the target donor node in the first information facilitates communication between the first donor node and the target donor node and instructs the target donor node to perform a handover of the UE. In one possible embodiment, the identifier of the target donor node carried in the first information may also be represented by an identifier of a target cell (e.g., an NR Cell Global Identity (NCGI)). The first donor node may obtain the identifier of the target donor node based on the identifier of the target cell.

[0045] In some scenarios, the first message may also carry a triggering method for DU migration (for example, an OAM trigger). Specifically, in a scenario where a CU trigger and an OAM trigger conflict, the OAM trigger shall prevail. Carrying the triggering method for DU migration (for example, an OAM trigger) in the first message can inform the first host node why the relay node did not establish the F1 interface according to its instructions.

[0046] Optionally, the first information can be carried in a class 1 RESPONSE message or a REJECT / FAILURE message of the F1 message triggered by the CU, and can also be carried in a separate class 2 message. Among them, the class 1 message needs to get a response from the other end, and the class 2 message does not need to get a response from the other end. For example, the relay node sends a class 1 message (such as RESPONSE / REJECT / FAILURE) to the first host node in response to another class 1 message (such as REQUEST) sent by the first host node to the relay node. When the relay node sends a class 2 message to the first host node, it does not need to be a response message to a specific message, and the class 2 message can be understood as a notification message.

[0047] Normally, the F1 interface establishment result received by the first host node from the relay node does not carry the identifier of the target host node. The first host node will send a UE handover instruction to the designated host node based on the instruction information in the CU trigger. For example, the CU instructs the relay node to establish an F1 interface with the second host node. After the F1 interface is established, the first host node will send a UE handover instruction to the second host node.

[0048] In one possible implementation, when the first trigger condition is not met, for example, the relay node does not establish an F1 interface based on the second information (for example, the second information does not exist), or the second host node is the same as the target host node, the result of the first host node receiving the first F1 interface does not carry the identifier of the target host node, and optionally, may carry a triggering method for DU migration. Through this implementation, the first host node can be implicitly indicated that the target host node is the one selected by the first host node, or is the same as the one selected by the first host node, so that the signaling overhead is reduced under the premise that the first host node can correctly judge the target host node.

[0049] In one possible implementation, the first host node can infer the triggering method of the DU migration and / or infer whether the second host node is different from the target host node by determining whether the relay node carries the identifier of the target host node when sending the F1 interface establishment result. Specifically, if the relay node carries the identifier of the target host node when sending the F1 interface establishment result, the first host node believes that the DU migration is triggered by OAM and / or that the second host node is different from the target host node; if the relay node does not carry the identifier of the target host node when sending the F1 interface establishment result, the first host node believes that the DU migration is triggered by the first host node, or that the second host node is the same as the target host node.

[0050] In one possible scenario, the first host node sends a UE handover instruction to the second host node. However, the relay node does not have an F1 interface established with the second host node, and instead establishes an F1 interface with the target host node. In this case, a handover anomaly may occur, preventing the relay node from completing the DU migration properly.

[0051] In the embodiment of the present application, the first host node receives the first information indicating the result of the first F1 interface established between the relay node and the target host node. The first host node can be informed that the relay node and the target host node have established the F1 interface, and send a UE handover indication to the target host node, thereby ensuring that the relay node successfully completes the DU migration.

[0052] In a possible implementation, the result of the first F1 interface is that the F1 interface between the relay node and the target host node is established. The beneficial effects of this implementation can refer to the beneficial effects of the corresponding implementation in the first aspect, and will not be repeated here.

[0053] In a third aspect, embodiments of the present application provide a communication method that can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method is applied to a relay node and includes:

[0054] The relay node sends fourth information to the network manager; the fourth information includes a result of the relay node establishing the third F1 interface with the target host node.

[0055] In an embodiment of the present application, a communication method is provided, in which the relay node sends a fourth information to the network manager, so that the network manager can obtain the current correct connection relationship of the relay node (the result of the relay node establishing the third F1 interface with the target host node), which facilitates the network manager to perform subsequent management and trigger the next DU migration of the relay node, thereby ensuring that the relay node can obtain the correct indication information during the subsequent DU migration process, so that the relay node can complete the DU migration normally.

[0056] The relay node, the first host node, the second host node, the target host node and the OAM server in the implementation manner of the present application can refer to the description corresponding to the first aspect or the second aspect above, and will not be repeated here.

[0057] The fourth information in the embodiments of the present application includes a result of the relay node establishing the third F1 interface with the target donor node. This result may be, for example, that the relay node and the target donor node have completed the establishment of the F1 interface, or that the relay node and the target donor node have not completed the establishment of the F1 interface, etc., and the embodiments of the present application are not limited thereto. The fourth information may carry an identifier of the target donor node, such as a gNB ID and / or an IP address, and / or an identifier of the target cell, such as an NR Cell Global Identity (NCGI).

[0058] In a possible implementation manner, the relay node sends the fourth information to the network manager when the second trigger condition is met;

[0059] The second trigger condition includes at least one of the following:

[0060] The relay node receives fifth information from the first host node, and the fifth information is used to instruct the relay node to establish the third F1 interface with the target host node; or, based on the sixth information provided by the network manager, the sixth information is used to instruct the relay node to establish a fourth F1 interface with the second host node, and the second host node is different from the target host node; or, the relay node receives seventh information from the target host node, and the seventh information is used to indicate that the establishment of the third F1 interface is completed.

[0061] An embodiment of the present application provides a communication method, in which the relay node sends a fourth message to the network manager when the second trigger condition is met, so that when a conflict occurs between the CU trigger and the OAM trigger, the network manager can obtain the correct connection relationship of the relay node through the fourth message, which facilitates the network manager's subsequent management of the relay node and triggering the next DU migration of the relay node.

[0062] The second trigger condition in the embodiments of the present application includes, but is not limited to: the relay node receiving fifth information from the first host node, the fifth information being used to instruct the relay node to establish a third F1 interface with the target host node. Alternatively, based on sixth information provided by the network management, the sixth information being used to instruct the relay node to establish a fourth F1 interface with a second host node, the second host node being different from the target host node. Alternatively, the relay node receiving seventh information from the target host node, the seventh information being used to indicate that the establishment of the third F1 interface is complete.

[0063] The fifth information may be carried in an F1AP message. The fifth information is used to instruct the relay node to establish a third F1 interface with the target host node, and may be a message instructing the relay node to send a request to establish an F1 interface to the target host node.

[0064] Among them, the above-mentioned sixth information can be a message pre-configured by the network manager in the relay node. The pre-configured time can be, for example, before the relay node enters the network, or after the relay node enters the network. The implementation method of the present application does not limit this. The pre-configured information can instruct the relay node to perform DU migration and the host node to which the DU is migrated at a preset time. For example, the pre-configured information can instruct the relay node to start DU migration one hour after entering the network, and instruct the relay node to migrate to the CU of the target host node. The sixth information can also be a message sent by the network manager to the relay node through remote control triggering. For example, the sixth message is sent to the relay node remotely through the PDU session of the MT or the IP network to instruct the relay node to establish a second F1 interface with the second host node.

[0065] The seventh information may be carried in an F1AP message, such as F1 SETUP RESPONSE. The relay node may generate the seventh information after receiving a message (such as F1 SETUP RESPONSE) indicating that the F1 interface setup is complete from the target host node.

[0066] It is understood that when the second trigger condition is met, the relay node generates the fourth information. In this case, the second trigger condition can be understood as a condition that triggers the relay node to generate the fourth information. Optionally, when the second trigger condition is met, the relay node also sends the fourth information. In this case, the second trigger condition can be understood as a condition that triggers the relay node to generate and send the fourth information.

[0067] In the IAB network, the DU migration of the IAB node supports two triggering modes: source CU triggering and OAM triggering. In the source CU triggering (hereinafter referred to as "CU triggering") mode, the source CU will send an indication message carrying the target CU to the DU in the IAB node, and the DU will complete the migration operation based on the indication message. The source CU is the CU connected to the DU before the migration, and the target CU is the CU connected to the DU after the migration. In the OAM triggering mode, the OAM server can be directly pre-configured in the IAB node or remotely trigger the IAB node to perform DU migration. Obviously, both CU triggering and OAM triggering can instruct the relay node to perform DU migration. If the CU triggering and OAM triggering occur at the same time, the relay node may not be able to complete the DU migration normally, or may migrate to the wrong host node. In addition, in the case of a conflict between the two triggers, at least one trigger indication (such as OAM triggering) is not completed, which may also cause abnormalities such as control failure and information transmission errors.

[0068] In the implementation manner of the present application, the first trigger condition for generating (or generating and sending) the result of establishing the F1 interface between the relay node and the target host node is clearly given, wherein the result of establishing the F1 interface can be used to enable OAM to obtain the latest connection status of the relay node. When the relay node meets the first trigger condition, the relay node can generate (or generate and send) the first information in a timely manner, so that OAM can update the connection status of the relay node in a timely manner, which is convenient for OAM to subsequently manage the relay node and re-trigger the DU migration of the relay node. Obviously, this situation is based on the indication information triggered by the CU. After the relay node establishes the F1 interface connection with the new host node (target host node), the first host node can send an indication of UE switching to the new host node. The first host node obtains that the relay node completes the establishment of the new F1 interface, for example, it can be a message that the relay node sends the F1 interface establishment completion to the first host node, for example, the relay node sends the F1 interface establishment completion message to the first host node through an F1AP message. Specifically, the implementation manner of the present application is not limited.

[0069] In a possible implementation manner, the fifth information is further used to trigger the release of the fourth F1 interface.

[0070] In the embodiments of the present application, the fifth information is used to instruct the relay node to establish a third F1 interface with the target host node. The fourth F1 interface is the F1 interface between the relay node and the second host node. If the relay node has already established the fourth F1 interface with the second host node before receiving the fifth information, the fifth information is used to trigger the release of the fourth F1 interface. This allows the relay node to establish the third F1 interface with the target host node. Furthermore, this saves resources of the second host node, facilitating the second host node's establishment of F1 interfaces with other relay nodes.

[0071] Optionally, the fifth information provided by the network management is equivalent to an OAM trigger, and the time of the OAM trigger may occur after the CU trigger and before the relay node receives the fourth F1 interface establishment completion message. For example, the OAM trigger may occur after the relay node sends the F1 interface establishment message to the second host node and before the relay node receives the F1 SETUP RESPONSE message from the second host node.

[0072] In a possible implementation manner, the fourth information further includes an identifier of the target host node and / or a triggering method for the DU migration.

[0073] In an embodiment of the present application, the identifier of the target host node may be, for example, a gNB ID and / or an IP address. The triggering method for DU migration may be, for example, a CU trigger. The fourth information carries the identifier of the target host node, which can facilitate OAM to know that the relay node has established an F1 interface with the target host node, and adjust the connection relationship of the relay node, so as to facilitate the subsequent management of the relay node and the execution of the next DU migration. The fourth information carries the DU migration triggering method, which can let OAM know according to whose instructions the relay node established the F1 interface. In a possible embodiment, the identifier of the target host node carried in the fourth information can also be represented by the identifier of the target cell (such as: NR cell global identifier NCGI), and OAM can obtain the identifier of the target host node based on the identifier of the target cell.

[0074] In a possible implementation manner, the fourth information further includes an identifier of the target host node and / or a triggering method for the DU migration, including:

[0075] When the second trigger condition includes the relay node receiving the fifth information from the first host node and / or the sixth information provided by the network manager, the fourth information also includes the identifier of the target host node and / or the triggering method of the DU migration.

[0076] In the implementation manner of the present application, the relay node receives the fifth information from the first host node, which is equivalent to the first host node instructing the relay node to establish an F1 interface with the target host node (CU trigger). Since in the implementation manner of the present application, in the case of a trigger conflict, the CU trigger shall prevail. Therefore, when a trigger conflict occurs and the indication information (fifth information) of the CU trigger is received, sending the fourth information to the OAM can enable the OAM to update the connection relationship of the IAB node in a timely manner, which is convenient for subsequent management. Based on the sixth information provided by the network management, it is equivalent to a trigger conflict, and the indications of the CU trigger are different from those of the OAM trigger (for example, the target host node is different from the second host node). In this case, sending the fourth information to the OAM can also enable the OAM to update the connection relationship of the IAB node in a timely manner, which is convenient for subsequent management.

[0077] In a fourth aspect, embodiments of the present application provide a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in the embodiments of the present application. The method is applied to network management and includes:

[0078] The network manager receives fourth information from the relay node, where the fourth information includes a result of the relay node establishing the third F1 interface with the target host node.

[0079] For the introduction of the relay node, the first host node, the second host node, the target host node and the OAM server in the implementation manner of the present application, reference may be made to the relevant description of the first aspect or the second aspect, which will not be repeated here.

[0080] The fourth information in the embodiments of the present application includes a result of establishing the third F1 interface between the relay node and the target donor node. This result may be, for example, that the relay node and the target donor node have completed establishing the F1 interface, or that the relay node and the target donor node have not completed establishing the F1 interface, etc., and the embodiments of the present application are not limited thereto. The fourth information may carry an identifier of the target donor node, such as a gNB ID and / or IP address, or an identifier of the target cell, such as an NR Cell Global Identity (NCGI).

[0081] Under normal circumstances, the network management will not receive the establishment result of the F1 interface returned by the relay node. After issuing the instruction information, the network management will default the relay node to perform DU migration according to the instruction information. The network management will adjust the connection relationship of the relay node based on the instruction information in the OAM trigger. For example, if OAM instructs the relay node to establish an F1 interface with the second host node, then OAM will adjust the connection relationship of the relay node to establish an F1 interface between the relay node and the second host node. However, in the case of a conflict between the CU trigger and the OAM trigger, the relay node may not establish the F1 interface according to the instruction information triggered by OAM, which will cause errors in the connection relationship recorded by OAM.

[0082] In one possible scenario, OAM instructs the relay node to establish an F1 interface with the second host node. However, the relay node actually established an F1 interface with the target host node according to the instruction triggered by the CU. In this case, OAM may still believe that the relay node has established an F1 interface with the second host node and perform subsequent management operations. This may cause management anomalies due to OAM recording an incorrect connection relationship of the relay node.

[0083] In the embodiment of the present application, the network management receives the fourth information indicating the result of the first F1 interface establishment between the relay node and the target host node. This allows the OAM to know that the relay node has established the F1 interface with the target host node and adjust the connection relationship of the relay node, thereby facilitating subsequent management of the relay node and execution of the next DU migration.

[0084] In a possible implementation, the fourth information further includes an identifier of the target host node and / or a triggering method for the DU migration. The beneficial effects of this implementation can be referred to the beneficial effects of the corresponding implementation in the third aspect, and will not be repeated here.

[0085] In a possible implementation manner, the fourth information further includes an identifier of the target host node and / or a triggering method for the DU migration, including:

[0086] When the second trigger condition includes the relay node receiving the fifth information from the first host node and / or the sixth information provided by the network manager, the fourth information further includes an identifier of the target host node and / or a triggering method for DU migration. For the beneficial effects of this embodiment, reference may be made to the beneficial effects of the corresponding embodiment in the third aspect and are not further elaborated here.

[0087] In a fifth aspect, embodiments of the present application provide a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in the embodiments of the present application. The method is applied to a relay node and includes:

[0088] The relay node receives the eighth information from the first host node and sends the ninth information to the first host node; the eighth information is used to instruct the relay node to perform DU migration, and the ninth information is used to instruct the relay node to refuse to perform the DU migration.

[0089] The relay node, the first host node, the second host node, the target host node and the OAM server in the implementation manner of the present application can refer to the description corresponding to the first aspect or the second aspect above, and will not be repeated here.

[0090] An embodiment of the present application provides a communication method, wherein upon receiving the indication information (eighth information) triggered by the CU, the relay node sends information to the first host node indicating that the DU migration is rejected. Since the relay node does not execute the action indicated by the CU trigger, a conflict between the CU trigger and the OAM trigger does not occur, thereby avoiding abnormal phenomena that may be caused by the trigger conflict and ensuring that the relay node can successfully complete the DU migration.

[0091] Optionally, the eighth information in the embodiments of the present application is used to instruct the relay node to perform DU migration, and may include an identifier of the post-migration donor node, such as a gNB ID and / or IP address. The ninth information is used to instruct the relay node to reject the DU migration indicated by the CU trigger, so as to inform the first donor node that the relay node did not perform DU migration according to its instructions. Both the eighth and ninth information may be carried in the F1AP message.

[0092] In the IAB network, the DU migration of the IAB node supports two triggering modes: CU triggering and OAM triggering. In the CU triggering mode, the source CU will send an indication message carrying the target CU to the DU in the IAB node, and the DU will complete the migration operation based on the indication message. The source CU is the CU connected to the DU before the migration, and the target CU is the CU connected to the DU after the migration. In the OAM triggering mode, the OAM server can be directly pre-configured in the IAB node or remotely trigger the IAB node to perform DU migration. Obviously, both CU triggering and OAM triggering can instruct the relay node to perform DU migration. If the CU triggering and OAM triggering occur at the same time, the relay node may not be able to complete the DU migration normally, or may migrate to the wrong host node. In addition, in the case of a conflict between the two triggers, at least one trigger indication (such as OAM triggering) is not completed, which may also cause abnormalities such as control failure and information transmission errors.

[0093] In the implementation manner of the present application, when the relay node receives the indication information triggered by CU, it directly gives the indication information of refusing to migrate, so that the relay node can only perform DU migration operations based on the indication information triggered by OAM, thereby avoiding the conflict between DU triggering and OAM triggering.

[0094] In a possible implementation manner, the ninth information includes the reason why the relay node refuses to perform the DU migration.

[0095] In the implementation manner of the present application, the reason for refusing to perform DU migration may be, for example, that the relay node only accepts OAM triggering, or that the relay node does not support CU triggering, etc., and this is not limited in the implementation manner of the present application. By giving the reason for refusing to perform DU migration, the first relay node can also know the specific reason for refusing to perform DU migration this time and record it. On the one hand, it can avoid the first host node instructing the relay node to perform DU migration again. On the other hand, it can also allow the first host node to understand the situation of the relay node more clearly. The relay node refuses to perform DU migration because it does not support CU triggering or only supports OAM triggering. It is not that the relay node refuses to perform DU migration for some reason, such as an abnormality in the relay node itself, or the relay node is temporarily unable to perform DU migration, etc.

[0096] Optionally, the ninth information can be carried in the class 1 RESPONSE message or REJECT / FAILURE message of the F1AP message triggered by the CU, or in a separate class 2 message. Among them, the processes in the F1AP message are divided into class 1 and class 2. The class 1 process refers to the situation where feedback is required in the same process, such as: F1 SETUP REQEUST--F1 SETUP RESPONSE / F1 SETUP FAILURE, GNB-DU CONFIGURATION UPDATE--GNB-DU CONFIGURATION UPDATE ACK / GNB-DU CONFIGURATION UPDATE FAILURE, etc., while the class 2 process refers to the process in which there is only one message and no feedback of the F1AP message is required, such as: UL RRC MESSAGE TRANSFER, DL RRC MESSAGE TRANSFER, etc.

[0097] In a possible implementation, the trigger condition for sending the ninth message is receiving the eighth message. After receiving the eighth message, the IAB node determines that it does not accept the trigger of the source CU and immediately replies with the ninth message.

[0098] In a sixth aspect, embodiments of the present application provide a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, etc., and the embodiments of the present application are not limited to this. The method is applied to a first host node, including:

[0099] The first host node sends eighth information to the relay node and receives ninth information from the relay node; the eighth information is used to instruct the relay node to perform DU migration, and the ninth information is used to instruct the relay node to refuse to perform the DU migration.

[0100] The relay node, the first host node, the second host node, the target host node and the OAM server in the implementation manner of the present application can refer to the description corresponding to the first aspect or the second aspect above, and will not be repeated here.

[0101] The embodiment of the present application provides a communication method, wherein a first host node sends CU trigger indication information (eighth information) to a relay node, and the first host node receives indication information (ninth information) for indicating rejection of CU triggering. Since the relay node refuses to perform the action indicated by the CU trigger, a conflict between the CU trigger and the OAM trigger will not occur, thereby avoiding abnormal phenomena that may be caused by the trigger conflict and ensuring that the relay node can successfully complete the DU migration.

[0102] The eighth information in the embodiments of the present application is used to instruct the relay node to perform DU migration and may include an identifier of the post-migration donor node, such as a gNB ID and / or IP address. The ninth information is used to instruct the relay node to reject the DU migration instructed by the CU trigger, thereby informing the first donor node that the relay node did not perform DU migration according to its instructions. Both the eighth and ninth information may be carried in an F1AP message.

[0103] In the IAB network, the DU migration of the IAB node supports two triggering modes: CU triggering and OAM triggering. In the CU triggering mode, the source CU will send an indication message carrying the target CU to the DU in the IAB node, and the DU will complete the migration operation based on the indication message. The source CU is the CU connected to the DU before the migration, and the target CU is the CU connected to the DU after the migration. In the OAM triggering mode, the OAM server can be directly pre-configured in the IAB node or remotely trigger the IAB node to perform DU migration. Obviously, both CU triggering and OAM triggering can instruct the relay node to perform DU migration. If the CU triggering and OAM triggering occur at the same time, the relay node may not be able to complete the DU migration normally, or may migrate to the wrong host node. In addition, in the case of a conflict between the two triggers, at least one trigger indication (such as OAM triggering) is not completed, which may also cause abnormalities such as control failure and information transmission errors.

[0104] In the implementation manner of the present application, when the relay node receives the indication information triggered by CU, it directly gives the indication information of refusing to migrate, so that the relay node can only perform DU migration operations based on the indication information triggered by OAM, thereby avoiding the conflict between DU triggering and OAM triggering.

[0105] In a possible implementation manner, the eighth information includes the reason why the relay node refuses to perform the DU migration.

[0106] The beneficial effects of this embodiment can refer to the beneficial effects of the corresponding embodiment in the fifth aspect, and will not be repeated here.

[0107] In a seventh aspect, embodiments of the present application provide a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, etc., and the embodiments of the present application are not limited to this. The method is applied to a relay node and includes:

[0108] The relay node receives tenth information from the network management, where the tenth information is used to instruct the relay node to perform DU migration;

[0109] The DU ignores the tenth information.

[0110] In an embodiment of the present application, a communication method is provided, in which, when a relay node receives indication information (the tenth information) of an OAM trigger, the OAM trigger indication information is ignored (equivalent to not performing an OAM trigger). This allows the relay node to perform DU migration only based on the indication information of the CU trigger, thereby avoiding conflicts when CU triggering and OAM triggering occur simultaneously, and ensuring that the relay node can normally complete DU migration.

[0111] For the introduction of the relay node, the first host node, the second host node, the target host node and the OAM in the implementation manner of the present application, reference can be made to the relevant description in the first aspect or the second aspect above, which will not be repeated here.

[0112] The tenth information may be information preconfigured on the relay node by the network administrator, or information sent to the relay node by the network administrator via remote control. For information on preconfiguration and remote control, please refer to the previous description and will not be repeated here. The tenth information may include the identifier of the host node after the relay node is migrated, such as the gNB ID and / or IP address. The tenth information may also include information such as the time when the relay node performs DU migration.

[0113] The DU ignoring the tenth information may be that the relay node refuses to receive the pre-configuration information of the network manager; it may also be that when the relay node is pre-configured by the network manager, the pre-configuration information is deleted; it may also be that when the pre-configuration information indicates that the relay node needs to migrate, the relay node ignores the instruction and does not perform DU migration according to the instructions of the pre-configuration information; it may also be that the DU migration triggered by the network manager through remote control is ignored. In one possible embodiment, the triggering condition for ignoring the tenth information is the receipt of the tenth information. When the relay node receives the tenth information, it directly ignores the tenth information even if no CU has configured other target host node information.

[0114] In the IAB network, the DU migration of the IAB node supports two triggering modes: source CU triggering and OAM triggering. In the source CU triggering (hereinafter referred to as "CU triggering") mode, the source CU will send an indication message carrying the target CU to the DU in the IAB node, and the DU will complete the migration operation based on the indication message. The source CU is the CU connected to the DU before the migration, and the target CU is the CU connected to the DU after the migration. In the OAM triggering mode, the OAM server can be directly pre-configured in the IAB node or remotely trigger the IAB node to perform DU migration. Obviously, both CU triggering and OAM triggering can instruct the relay node to perform DU migration. If the CU triggering and OAM triggering occur at the same time, the relay node may not be able to complete the DU migration normally, or may migrate to the wrong host node. In addition, in the case of a conflict between the two triggers, at least one trigger indication (such as CU triggering) is not completed, which may also cause abnormalities such as control failure and information transmission errors.

[0115] In the implementation manner of the present application, when the OAM-triggered indication information instructs the relay node to perform DU migration, the relay node ignores the OAM-triggered indication information, so that the relay node only executes the CU-triggered indication information, thereby avoiding the conflict between CU triggering and OAM triggering, and then ensuring that the relay node completes DU migration normally.

[0116] In a possible implementation manner, the relay node sends eleventh information to the network manager, where the eleventh information is used to indicate rejection of DU migration triggered by the network manager or to indicate that the network manager does not trigger DU migration of the relay node.

[0117] In the implementation manner of the present application, after the relay node receives the indication information of the OAM trigger, on the one hand, it will ignore the indication information of the OAM trigger and will not execute the DU migration indicated by the OAM trigger. On the other hand, the relay node will also send an eleventh message to the network management (OAM server) to indicate the rejection of the OAM trigger or to instruct the OAM server to no longer trigger the DU migration of the relay node. The OAM server knows that the DU migration indicated by it has not been executed by the relay node, thereby avoiding the OAM server adjusting the connection relationship of the relay node according to the indication information of the OAM trigger. Informing the OAM server not to trigger the DU migration can also save some control resources and avoid the conflict between the OAM trigger and the CU trigger again.

[0118] Optionally, the relay node sends instruction information to the OAM server, where the instruction information is used to instruct the relay node to establish an F1 interface with the target host node.

[0119] When the relay node ignores the indication information triggered by OAM, if the relay node performs DU migration according to the indication information triggered by CU and informs the OAM server of the relay node DU migration, the OAM server can update the connection relationship of the relay node in time, thereby facilitating the OAM server to perform subsequent management of the relay node.

[0120] In one possible implementation, the trigger condition for sending the eleventh message is receiving the tenth message. After receiving the tenth message, even if no source CU has configured other target host node information, the relay node determines not to accept the OAM trigger and immediately replies with the eleventh message.

[0121] In an eighth aspect, embodiments of the present application provide a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, etc., which is not limited in the embodiments of the present application. The method is applied to a network management, and includes:

[0122] The network management sends tenth information to the relay node, where the tenth information is used to instruct the relay node to perform DU migration;

[0123] The network manager receives eleventh information from the relay node, where the eleventh information is used to indicate rejection of DU migration triggered by the network manager or to indicate that the network manager does not trigger DU migration of the relay node.

[0124] In an embodiment of the present application, a communication method is provided, wherein after a network manager sends an OAM-triggered indication message (a tenth message) to a relay node, the network manager receives an eleventh message from the relay node, which is used to instruct the relay node to refuse to execute the OAM-triggered indication message, or to instruct the network manager not to trigger DU migration of the relay node. This allows the relay node to perform DU migration only based on the CU-triggered indication message, thereby avoiding conflicts when CU triggering and OAM triggering occur simultaneously, and ensuring that the relay node can normally complete DU migration.

[0125] For the introduction of the relay node, the first host node, the second host node, the target host node and the OAM in the implementation manner of the present application, reference can be made to the relevant description in the first aspect or the second aspect above, which will not be repeated here.

[0126] The tenth information may be information preconfigured on the relay node by the network administrator, or information sent to the relay node by the network administrator via remote control. For information on preconfiguration and remote control, please refer to the previous description and will not be repeated here. The tenth information may include the identifier of the host node after the relay node is migrated, such as the gNB ID and / or IP address. The tenth information may also include information such as the time when the relay node performs DU migration.

[0127] The eleventh information may be sent to the relay node through a PDU session between the IAB-MT and the core network, for example.

[0128] In the IAB network, the DU migration of the IAB node supports two triggering modes: source CU triggering and OAM triggering. In the source CU triggering (hereinafter referred to as "CU triggering") mode, the source CU will send an indication message carrying the target CU to the DU in the IAB node, and the DU will complete the migration operation based on the indication message. The source CU is the CU connected to the DU before the migration, and the target CU is the CU connected to the DU after the migration. In the OAM triggering mode, the OAM server can be directly pre-configured in the IAB node or remotely trigger the IAB node to perform DU migration. Obviously, both CU triggering and OAM triggering can instruct the relay node to perform DU migration. If the CU triggering and OAM triggering occur at the same time, the relay node may not be able to complete the DU migration normally, or may migrate to the wrong host node. In addition, in the case of a conflict between the two triggers, at least one trigger indication (such as CU triggering) is not completed, which may also cause abnormalities such as control failure and information transmission errors.

[0129] In the embodiment of the present application, the network management (OAM server) receives the eleventh message sent by the relay node, which indicates that the OAM trigger is rejected or that the OAM server is no longer triggering the DU migration of the relay node. This allows the OAM server to know that the DU migration it instructed was not executed by the relay node, thereby preventing the OAM server from adjusting the connection relationship of the relay node based on the instruction information of the OAM trigger. Informing the OAM server that the DU migration is no longer triggered can also save some control resources and avoid the recurrence of conflicts between OAM triggering and CU triggering.

[0130] In a possible implementation manner, the relay node sends eleventh information to the network manager, where the eleventh information is used to indicate rejection of DU migration triggered by the network manager or to indicate that the network manager does not trigger DU migration of the relay node.

[0131] In the implementation manner of the present application, after the relay node receives the indication information of the OAM trigger, on the one hand, it will ignore the indication information of the OAM trigger and will not execute the DU migration indicated by the OAM trigger. On the other hand, the relay node will also send an eleventh message to the network management (OAM server) to indicate the rejection of the OAM trigger or to instruct the OAM server to no longer trigger the DU migration of the relay node. The OAM server knows that the DU migration indicated by it has not been executed by the relay node, thereby avoiding the OAM server adjusting the connection relationship of the relay node according to the indication information of the OAM trigger. Informing the OAM server not to trigger the DU migration can also save some control resources and avoid the conflict between the OAM trigger and the CU trigger again.

[0132] Optionally, the relay node sends instruction information to the OAM server, where the instruction information is used to instruct the relay node to establish an F1 interface with the target host node.

[0133] When the relay node ignores the indication information triggered by OAM, if the relay node performs DU migration according to the indication information triggered by CU and informs the OAM server of the relay node DU migration, the OAM server can update the connection relationship of the relay node in time, thereby facilitating the OAM server to perform subsequent management of the relay node.

[0134] In a ninth aspect, embodiments of the present application provide a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method is applied to a relay node and includes:

[0135] The relay node sends the twelfth information to the first host node;

[0136] The twelfth information is used to indicate the triggering method of DU migration supported by the relay node; and / or, the relay node receives the thirteenth information from the first host node, and the thirteenth information is used to indicate the triggering method of DU migration supported by the relay node; the triggering method includes CU triggering and / or network management triggering.

[0137] In an embodiment of the present application, a communication method is provided, in which a relay node sends twelfth information to a first host node, the twelfth information being used to indicate a triggering method for DU migration supported by the relay node. And / or the relay node receives thirteenth information from the first host node when a third condition is satisfied, the thirteenth information being used to indicate a triggering method for DU migration supported by the relay node. This method enables the relay node and the first host node to know the triggering method for DU migration supported by the relay node, thereby reducing the possibility of triggering conflicts.

[0138] For the introduction of the relay node, the first host node, the second host node, the target host node and the OAM server in the embodiments of the present application, reference can be made to the relevant description of the first or second aspect mentioned above, which will not be repeated here.

[0139] The twelfth information and the thirteenth information in the embodiment of the present application are both used to indicate the triggering mode of DU migration supported by the relay node, for example, only supporting CU triggering, only supporting OAM triggering, or supporting both CU triggering and OAM triggering. In the case where the relay node supports both CU triggering and OAM triggering, the priority of CU triggering and OAM triggering can also be set, for example, based on OAM triggering (equivalent to the first and second aspects), or based on CU triggering (equivalent to the third and fourth aspects).

[0140] The twelfth information may be carried in the class 1 process of F1AP, for example, in the F1 SETUP REQUEST message or the GNB-DU CONFIGURATION UPDATE message. It may also be carried in the class 2 process of F1AP. The specific message used is not limited in this embodiment of the present application.

[0141] The thirteenth information may be carried in a class 1 process of F1AP, such as an F1 SETUP RESPONSE message or a GNB-CU CONFIGURATION UPDATE message. It may also be carried in a class 2 process of F1AP. The specific message used is not limited in this embodiment of the present application.

[0142] In a possible implementation, the relay node sends the twelfth information to the first host node, including:

[0143] When a third trigger condition is met, the relay node sends the twelfth information to the first host node;

[0144] The third trigger condition includes at least one of the following:

[0145] The relay node completes network access; or, the relay node completes DU migration.

[0146] The third trigger condition in the embodiment of the present application includes but is not limited to: the relay node completes network access or the relay node completes DU migration. It is understandable that the relay node completes network access generally means that the parent node of the relay node is already in the network, and the relay node and the host node in the network complete the establishment of the F1 interface. Alternatively, the relay node can provide services for the UE or the next-hop MT. The relay node completes DU migration, which may be that the relay node establishes a new F1 interface with a new host node, and the UE of the relay node has switched to the new DU and released the old F1 interface. For example, before DU migration, the relay node maintains an F1 interface connection with the first host node, and after DU migration, there is an F1 interface connection with the target host node. During the DU migration process, the relay node creates two logical DUs, namely DU1 and DU2. Before DU migration, the UE is in the cell corresponding to DU1, and after DU migration, the UE is in the cell corresponding to DU2. Before DU migration, DU1 has an F1 interface with the first host node. After DU migration, the F1 interface between DU1 and the first host node is released, and DU2 completes the establishment of the F1 interface with the target host node.

[0147] It is understood that when the third trigger condition is met, the relay node generates the twelfth information. In this case, the third trigger condition can be understood as a condition that triggers the relay node to generate the twelfth information. Optionally, when the third trigger condition is met, the relay node also sends the twelfth information. In this case, the third trigger condition can be understood as a condition that triggers the relay node to generate and send the twelfth information.

[0148] In an implementation manner of the present application, when the relay node completes network access or the relay node completes DU migration, the twelfth information is sent to the first host node to indicate the triggering method of DU migration supported by the relay node, so that the relay node and the first host node can know the triggering method of DU migration supported by the relay node, thereby reducing the possibility of triggering conflict when the relay node performs DU migration again.

[0149] In a tenth aspect, embodiments of the present application provide a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method is applied to a first host node, comprising:

[0150] The first host node sends thirteenth information to the relay node;

[0151] The thirteenth information is used to indicate the triggering method of DU migration supported by the relay node; and / or, the first host node receives the twelfth information from the relay node, and the twelfth information is used to indicate the triggering method of DU migration supported by the relay node; the triggering method includes CU triggering and / or network management triggering.

[0152] The twelfth information and the thirteenth information in the implementation manner of this application can refer to the relevant introduction of the ninth aspect and will not be repeated here.

[0153] The relay node, the first host node, the second host node, the target host node and the OAM server in the implementation manner of the present application can refer to the relevant description of the first aspect or the second aspect, which will not be repeated here.

[0154] In the embodiment of the present application, the above-mentioned triggering method includes CU triggering and / or network management triggering. When the above-mentioned triggering method includes only CU triggering or only network management triggering, the relay node can avoid triggering conflicts and ensure that the relay node completes DU migration normally. If the above-mentioned triggering method includes both CU triggering and OAM triggering, the possible conflicts can be handled by the methods provided in the first aspect, the second aspect, the third aspect, or the fourth aspect to ensure that the relay node completes DU migration normally.

[0155] The beneficial effects of the embodiments of the present application can be referred to the effective effects of the corresponding implementation methods in the ninth aspect, and will not be repeated here.

[0156] In one possible implementation, the first host node sends the thirteenth information to the relay node, including:

[0157] When the third trigger condition is met, the first host node sends thirteenth information to the relay node;

[0158] The third trigger condition includes at least one of the following:

[0159] The relay node completes network access; or, the relay node completes DU migration.

[0160] The third trigger condition in the implementation manner of this application can refer to the relevant introduction of the ninth aspect and will not be repeated here.

[0161] In an implementation manner of the present application, when the relay node completes network access or the relay node completes DU migration, the first host node sends the thirteenth information to the relay master node, which is used to indicate the triggering method of DU migration supported by the relay node, so that the relay node and the first host node can know the triggering method of DU migration supported by the relay node, thereby reducing the possibility of triggering conflicts when the relay node performs DU migration again.

[0162] In an eleventh aspect, an embodiment of the present application provides a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method is applied to a first host node, comprising:

[0163] When the fourth trigger condition is met, the first host node sends fourteenth information to the second host node; the fourteenth information is used to indicate cancellation of establishing the F1 interface between the second host node and the relay node;

[0164] The fourth trigger condition includes:

[0165] Receive fifteenth information from the relay node, where the fifteenth information includes that the relay node completes establishing an F1 interface with a target host node, and the target host node is different from the second host node.

[0166] In an embodiment of the present application, a communication method is provided in which, when a fourth trigger condition is satisfied, a first host node transmits fourteenth information to a second host node. The fourteenth information is used to instruct the second host node to cancel the establishment of an F1 interface with a relay node, thereby avoiding an abnormal situation caused by the second host node attempting to establish the F1 interface with the relay node again. In addition, the second host node can use its available resources to establish an F1 interface with another relay node.

[0167] The relay node, the first host node, the second host node, the target host node and the OAM server in the implementation manner of the present application can refer to the relevant descriptions of the first and second aspects mentioned above, which will not be repeated here.

[0168] The fourth trigger condition in the embodiment of the present application includes, but is not limited to, the first donor node receiving fifteenth information from the relay node, where the fifteenth information indicates that the relay node has established an F1 interface with the target donor node, and the target donor node is different from the second donor node. The fifteenth information may be carried in an F1AP message. The message may include an identifier of the target donor node, such as a gNB ID and / or IP address.

[0169] In the embodiment of the present application, the fourteenth information may be information sent by the first donor node to the second donor node via the Xn interface. The message may carry an identifier of the target donor node, such as a gNB ID and / or IP address.

[0170] It is understood that when the fourth trigger condition is met, the first host node generates the fourteenth information. In this case, the fourth trigger condition can be understood as a condition that triggers the first host node to generate the fourteenth information. Optionally, when the fourth trigger condition is met, the relay node also sends the fourteenth information. In this case, the fourth trigger condition can be understood as a condition that triggers the relay node to generate and send the fourteenth information.

[0171] In a twelfth aspect, an embodiment of the present application provides a communication method, which can be performed by a communication device. The communication device can be a device, or a chip (system) or circuit for a device, which is not limited in this application. The method is applied to a second host node, comprising:

[0172] The second host node receives fourteenth information from the first host node, where the fourteenth information is used to instruct the second host node to cancel establishing the F1 interface with the relay node.

[0173] In an embodiment of the present application, a communication method is provided in which a second host node receives fourteenth information from a first host node, the fourteenth information being used to instruct the second host node to cancel establishing an F1 interface with a relay node. This method can avoid an abnormal situation caused by the second host node attempting to establish the F1 interface with the relay node again. Furthermore, the method can enable the second host node to use available resources to establish F1 interfaces with other relay nodes.

[0174] The relay node, the first host node, the second host node, the target host node and the OAM server in the implementation manner of the present application can refer to the relevant descriptions of the first and second aspects mentioned above, which will not be repeated here.

[0175] In the embodiment of the present application, the fourteenth information may be information received by the second donor node from the first donor node via the Xn interface. This message may carry an identifier of the target donor node, such as a gNB ID and / or IP address.

[0176] In a thirteenth aspect, an embodiment of the present application provides a communication device, which includes a unit for executing any method as described in the first aspect.

[0177] In one possible design, the apparatus includes:

[0178] A processing unit, configured to generate first information when a first trigger condition is met; the first information includes a result of the relay node establishing the first F1 interface with the target host node and an identifier of the target host node; or, the first information includes a result of the relay node establishing the first F1 interface with the target host node, an identifier of the target host node, and a triggering method for DU migration of the relay node;

[0179] The first trigger condition includes at least one of the following:

[0180] Based on the second information provided by the network management, the second information is used to instruct the relay node to establish the first F1 interface with the target host node; or, the relay node receives third information from the first host node, and the third information is used to instruct the relay node to establish a second F1 interface with a second host node, and the second host node is different from the target host node.

[0181] In one possible implementation, the device further includes:

[0182] A communication unit, configured to send the first information.

[0183] The methods executed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned first aspect, and will not be repeated here.

[0184] Regarding the beneficial effects brought about by the thirteenth aspect and any possible implementation method, please refer to the description of the beneficial effects corresponding to the first aspect and the corresponding implementation method, and no further details will be given here.

[0185] In a fourteenth aspect, an embodiment of the present application provides a communication device, which includes a unit for executing any method as described in the second aspect.

[0186] In one possible design, the apparatus includes:

[0187] Communication unit,

[0188] When the first trigger condition is met, the first host node receives first information from the relay node; the first information includes a result of the relay node establishing the first F1 interface with the target host node and an identifier of the target host node; or, the first information includes a result of the relay node establishing the first F1 interface with the target host node, an identifier of the target host node, and a triggering method for DU migration of the relay node;

[0189] The first trigger condition includes at least one of the following:

[0190] Based on the second information provided by the network management, the second information is used to instruct the relay node to establish the first F1 interface with the target host node; or, the relay node receives third information from the first host node, and the third information is used to instruct the relay node to establish a second F1 interface with a second host node, and the second host node is different from the target host node.

[0191] In one possible implementation, the device further includes:

[0192] A processing unit is configured to process the first information.

[0193] The methods performed by the above-mentioned communication unit and processing unit can refer to the methods corresponding to the above-mentioned second aspect, which will not be repeated here.

[0194] Regarding the beneficial effects brought about by the fourteenth aspect and any possible implementation method, please refer to the description of the beneficial effects corresponding to the second aspect and the corresponding implementation method, which will not be repeated here.

[0195] In a fifteenth aspect, an embodiment of the present application provides a communication device, which includes a unit for executing any method as described in the third aspect.

[0196] In one possible design, the apparatus includes:

[0197] The processing unit is configured to generate fourth information; the fourth information includes a result of the relay node establishing a third F1 interface with the target host node.

[0198] In one possible implementation, the device further includes:

[0199] The communication unit is configured to send the fourth information to the network manager.

[0200] In a possible implementation, the processing unit is specifically configured to generate the fourth information when the second trigger condition is met;

[0201] The second trigger condition includes at least one of the following:

[0202] The relay node receives fifth information from the first host node, and the fifth information is used to instruct the relay node to establish the third F1 interface with the target host node; or, based on the sixth information provided by the network manager, the sixth information is used to instruct the relay node to establish a fourth F1 interface with the second host node, and the second host node is different from the target host node; or, the relay node receives seventh information from the target host node, and the seventh information is used to indicate that the establishment of the third F1 interface is completed.

[0203] In a possible implementation manner, the communication unit is specifically configured to send the fourth information to the network manager when the second trigger condition is met.

[0204] The methods executed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned third aspect, which will not be repeated here.

[0205] Regarding the beneficial effects brought about by the fifteenth aspect and any possible implementation method, please refer to the description of the beneficial effects corresponding to the third aspect and the corresponding implementation method, which will not be repeated here.

[0206] In the sixteenth aspect, an embodiment of the present application provides a communication device, which includes a unit for executing any method as described in the fourth aspect.

[0207] In one possible design, the apparatus includes:

[0208] The communication unit is configured to receive fourth information from the relay node, where the fourth information includes a result of the relay node establishing a third F1 interface with the target host node.

[0209] In one possible implementation, the device further includes:

[0210] A processing unit is configured to process the fourth information.

[0211] The methods executed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned fourth aspect, which will not be repeated here.

[0212] Regarding the beneficial effects brought about by the sixteenth aspect and any possible implementation method, please refer to the description of the beneficial effects corresponding to the fourth aspect and the corresponding implementation method, which will not be repeated here.

[0213] In the seventeenth aspect, an embodiment of the present application provides a communication device, which includes a unit for executing any method as described in the fifth aspect.

[0214] In one possible design, the apparatus includes:

[0215] The communication unit is configured to receive eighth information from the first host node, where the eighth information is configured to instruct the relay node to perform DU migration.

[0216] In a possible implementation manner, the device further includes:

[0217] The processing unit is configured to generate ninth information, where the ninth information is configured to instruct the relay node to refuse to perform the DU migration.

[0218] In a possible implementation, the communication unit is further configured to send ninth information to the first host node.

[0219] The methods executed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned fifth aspect, which will not be repeated here.

[0220] Regarding the beneficial effects brought about by the seventeenth aspect and any possible implementation method, please refer to the description of the beneficial effects corresponding to the fifth aspect and the corresponding implementation method, which will not be repeated here.

[0221] In the eighteenth aspect, an embodiment of the present application provides a communication device, which includes a unit for executing any method as described in the sixth aspect.

[0222] In one possible design, the apparatus includes:

[0223] The processing unit is configured to generate eighth information, where the eighth information is used to instruct the relay node to perform DU migration.

[0224] In a possible implementation manner, the device further includes:

[0225] The communication unit is used to send the eighth information to the relay node.

[0226] In a possible implementation, the communication unit is further configured to receive ninth information from the relay node, where the ninth information is configured to instruct the relay node to refuse to perform the DU migration.

[0227] The methods executed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned sixth aspect, which will not be repeated here.

[0228] Regarding the beneficial effects brought about by the eighteenth aspect and any possible implementation method, please refer to the description of the beneficial effects corresponding to the sixth aspect and the corresponding implementation method, which will not be repeated here.

[0229] In the nineteenth aspect, an embodiment of the present application provides a communication device, which includes a unit for executing any method as described in the seventh aspect.

[0230] In one possible design, the apparatus includes:

[0231] The communication unit is configured to receive tenth information from the network management, where the tenth information is used to instruct the relay node to perform DU migration.

[0232] In one possible implementation, the device further includes:

[0233] The processing unit is configured to process the tenth information, for example, ignoring the tenth information.

[0234] The methods executed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned seventh aspect, which will not be repeated here.

[0235] Regarding the beneficial effects brought about by the nineteenth aspect and any possible implementation method, please refer to the description of the beneficial effects corresponding to the seventh aspect and the corresponding implementation method, which will not be repeated here.

[0236] In the twentieth aspect, an embodiment of the present application provides a communication device comprising a unit for executing any method as described in the eighth aspect.

[0237] In one possible design, the apparatus includes:

[0238] a processing unit, configured to generate tenth information, wherein the tenth information is used to instruct the relay node to perform DU migration;

[0239] In one possible implementation, the device further includes:

[0240] The communication unit is configured to send tenth information to the relay node.

[0241] In a possible implementation, the communication unit is further configured to receive eleventh information from the relay node, where the eleventh information is used to indicate rejection of the DU migration triggered by the network manager or to indicate that the network manager does not trigger the DU migration of the relay node.

[0242] The methods executed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned eighth aspect, which will not be repeated here.

[0243] Regarding the beneficial effects brought about by the twentieth aspect and any possible implementation method, please refer to the description of the beneficial effects corresponding to the eighth aspect and the corresponding implementation method, which will not be repeated here.

[0244] In aspect 21, an embodiment of the present application provides a communication device comprising a unit for executing any method as described in aspect 9.

[0245] In one possible design, the apparatus includes:

[0246] a processing unit, configured to generate twelfth information, wherein the twelfth information is used to indicate a triggering method for DU migration supported by the relay node; and / or, to process thirteenth information from the first host node, wherein the thirteenth information is used to indicate a triggering method for DU migration supported by the relay node;

[0247] In one possible implementation, the device further includes:

[0248] A communication unit is configured to send the twelfth information and / or receive the thirteenth information.

[0249] The methods executed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned ninth aspect, which will not be repeated here.

[0250] Regarding the beneficial effects brought about by the twenty-first aspect and any possible implementation method, please refer to the description of the beneficial effects corresponding to the ninth aspect and the corresponding implementation method, which will not be repeated here.

[0251] In aspect 22, an embodiment of the present application provides a communication device, which includes an or unit for executing any method as in aspect 10.

[0252] In one possible design, the apparatus includes:

[0253] a processing unit configured to generate thirteen information, wherein the thirteenth information is used to indicate a triggering method for DU migration supported by the relay node; and / or, to process twelfth information from the relay node, wherein the twelfth information is used to indicate a triggering method for DU migration supported by the relay node;

[0254] The third trigger condition includes at least one of the following:

[0255] The relay node completes network access; or, the relay node completes DU migration.

[0256] In one possible implementation, the device further includes:

[0257] A communication unit is configured to send the thirteenth information and / or receive the twelfth information.

[0258] The methods executed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned tenth aspect, which will not be repeated here.

[0259] Regarding the beneficial effects brought about by the twenty-second aspect and any possible implementation method, please refer to the description of the beneficial effects corresponding to the tenth aspect and the corresponding implementation method, which will not be repeated here.

[0260] In aspect 23, an embodiment of the present application provides a communication device comprising a unit for executing any method as in aspect 11.

[0261] In one possible design, the apparatus includes:

[0262] a processing unit, configured to generate fourteenth information when the fourth trigger condition is met; the fourteenth information is used to indicate cancellation of establishing the F1 interface between the second host node and the relay node;

[0263] The fourth trigger condition includes:

[0264] Receive fifteenth information from the relay node, where the fifteenth information includes that the relay node completes establishing an F1 interface with a target host node, and the target host node is different from the second host node.

[0265] In one possible implementation, the device further includes:

[0266] a communication unit, configured to send fourteenth information when a fourth trigger condition is met;

[0267] The methods executed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned eleventh aspect, and will not be repeated here.

[0268] Regarding the beneficial effects brought about by the twenty-third aspect and any possible implementation method, please refer to the description of the beneficial effects corresponding to the eleventh aspect and the corresponding implementation method, which will not be repeated here.

[0269] In aspect 24, an embodiment of the present application provides a communication device, which includes a unit for executing any method as described in aspect 12.

[0270] In one possible design, the apparatus includes:

[0271] The communication unit is configured to receive fourteenth information from the first host node, where the fourteenth information is used to instruct to cancel establishing the F1 interface between the second host node and the relay node.

[0272] In one possible implementation, the device further includes:

[0273] A processing unit is used to process the fourteenth information.

[0274] The methods executed by the above-mentioned processing unit and communication unit can refer to the methods corresponding to the above-mentioned aspect 12, and will not be repeated here.

[0275] Regarding the beneficial effects brought about by the twenty-fourth aspect and any possible implementation method, please refer to the description of the beneficial effects corresponding to the twelfth aspect and the corresponding implementation method, and no further details will be given here.

[0276] Optionally, in the communication device described in any one of the thirteenth to twenty-fourth aspects and any possible implementation manner:

[0277] In one implementation, the communication apparatus is a communication device. When the communication apparatus is a communication device, the communication unit may be a transceiver or an input / output interface; and the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0278] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0279] In aspect 25, an embodiment of the present application provides a communication device, comprising a processor. The processor is coupled to a memory and can be configured to execute instructions in the memory to implement the method of any of aspects 1 to 12 above and any possible implementation manner. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

[0280] In aspect 26, an embodiment of the present application provides a communication device, comprising: a logic circuit and a communication interface. The communication interface is configured to receive or send information; the logic circuit is configured to receive or send information via the communication interface, so that the communication device performs the method of any one of aspects 1 to 12 above and any possible implementation thereof.

[0281] In aspect 27, an embodiment of the present application provides a computer-readable storage medium, which is used to store a computer program (also referred to as code, or instructions); when the computer program is run on a computer, the method of any one of aspects 1 to twelfth above and any possible implementation method is implemented.

[0282] In aspect 28, an embodiment of the present application provides a computer program product, which includes: a computer program (also referred to as code, or instructions); when the computer program is run, it enables the computer to execute the method of any aspect from aspect 1 to aspect 12 above and any possible implementation method.

[0283] In aspect 29, an embodiment of the present application provides a chip, comprising a processor configured to execute instructions. When the processor executes the instructions, the chip performs the method of any one of aspects 1 to 12 above, and any possible implementation thereof. Optionally, the chip further comprises a communication interface configured to receive or transmit signals.

[0284] In aspect 30, an embodiment of the present application provides a communication system, which includes at least one communication device as described in aspects 13 to 24, or the communication device described in aspect 25, or the communication device described in aspect 26, or the chip described in aspect 29.

[0285] In aspect 31, an embodiment of the present application provides a communication system, comprising at least one of a relay node, a first host node, a second host node, and an OAM server, wherein the first host node is used to execute the method of the above-mentioned first aspect, third aspect, fifth aspect, seventh aspect, or ninth aspect and any possible implementation manner, the first host node is used to execute the method of the above-mentioned second aspect, sixth aspect, tenth aspect, or eleventh aspect and any possible implementation manner, the second host node is used to execute the method of the above-mentioned twelfth aspect and any possible implementation manner, and the OAM server is used to execute the method of the above-mentioned fourth aspect or eighth aspect and any possible implementation manner.

[0286] In addition, in the process of executing the method described in any one of the first to twelfth aspects and any possible implementation methods, the process of sending information and / or receiving information in the above method can be understood as the process of the processor outputting information, and / or the process of the processor receiving input information. When outputting information, the processor can output the information to the transceiver (or communication interface, or sending module) so that it can be transmitted by the transceiver. After the information is output by the processor, it may also need to undergo other processing before it reaches the transceiver. Similarly, when the processor receives input information, the transceiver (or communication interface, or sending module) receives the information and inputs it into the processor. Furthermore, after the transceiver receives the information, the information may need to undergo other processing before it is input into the processor.

[0287] Based on the above principles, for example, the sending of information mentioned in the above method can be understood as the processor outputting information. For another example, the receiving of information can be understood as the processor receiving input information.

[0288] Optionally, for the operations such as transmission, sending and receiving involved in the processor, if there is no special explanation, or if they do not conflict with their actual functions or internal logic in the relevant description, they can be more generally understood as processor output, reception, input and other operations.

[0289] Optionally, in the process of executing the method described in any one of the first to twelfth aspects and any possible implementation methods, the processor may be a processor specifically used to execute these methods, or a processor that executes these methods by executing computer instructions in a memory, such as a general-purpose processor. The memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or may be separately provided on different chips. The embodiments of the present application do not limit the type of memory and the configuration of the memory and the processor.

[0290] In a possible implementation, the at least one memory is located outside the device.

[0291] In yet another possible implementation, the at least one memory is located within the device.

[0292] In another possible implementation, part of the at least one memory is located inside the device, and another part of the memory is located outside the device.

[0293] In an embodiment of the present application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0294] In an embodiment of the present application, a first trigger condition for generating (or generating and sending) a result of establishing an F1 interface between a relay node and a target host node is clearly given, wherein the result of establishing the F1 interface can be used to enable the first host node to send an indication message of UE switching to the correct host node, thereby avoiding the situation where the DU migration of the relay node cannot be completed normally or the migration is erroneous. When the relay node meets the first trigger condition, the relay node can generate (or generate and send) the first information in a timely manner, so that the first host node can initiate a switching request of the user equipment (UE) to the correct host node (target host node) according to the first information, so that the relay node can complete the DU migration normally, and avoid migrating the DU of the relay node to the wrong host node. BRIEF DESCRIPTION OF THE DRAWINGS

[0295] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0296] FIG1 is a schematic diagram of the structure of an IAB system provided in an embodiment of the present application;

[0297] FIG2 is a schematic diagram of the structure of an IAB node provided in an embodiment of the present application;

[0298] FIG3 is a schematic diagram of the structure of an IAB network provided in an embodiment of the present application;

[0299] FIG4 is a schematic diagram of a control plane protocol architecture in an IAB network provided in an embodiment of the present application;

[0300] FIG5 is a schematic diagram of a user plane protocol architecture in an IAB network provided in an embodiment of the present application;

[0301] FIG6 is an example of an IAB network architecture diagram provided in an embodiment of the present application;

[0302] FIG7 is an example of a BAP topology of an IAB network provided in an embodiment of the present application;

[0303] FIG8 is an example of DU migration in an IAB network provided by an embodiment of the present application;

[0304] FIG9 is a flow chart of a communication method provided in an embodiment of the present application;

[0305] FIG10 is a flow chart of another communication method provided in an embodiment of the present application;

[0306] FIG11 is a flow chart of another communication method provided in an embodiment of the present application;

[0307] FIG12 is a flow chart of another communication method provided in an embodiment of the present application;

[0308] FIG13 is a flow chart of another communication method provided in an embodiment of the present application;

[0309] FIG14 is a flow chart of another communication method provided in an embodiment of the present application;

[0310] FIG15 is a flow chart of another communication method provided in an embodiment of the present application;

[0311] FIG16 is a flow chart of another communication method provided in an embodiment of the present application;

[0312] FIG17 is a flow chart of another communication method provided in an embodiment of the present application;

[0313] FIG18 is a flow chart of another communication method provided in an embodiment of the present application;

[0314] FIG19 is a flow chart of another communication method provided in an embodiment of the present application;

[0315] FIG20 is a flow chart of another communication method provided in an embodiment of the present application;

[0316] FIG21 is a flow chart of another communication method provided in an embodiment of the present application;

[0317] FIG22 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0318] FIG23 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0319] FIG24 is a schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0320] In order to make the purpose, technical solutions and advantages of this application clearer, the embodiments of this application will be described below in conjunction with the drawings in the embodiments of this application.

[0321] The terms "first" and "second" in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to the process, method, product, or device.

[0322] The “embodiment” mentioned herein means that the specific features, structures or characteristics described in conjunction with the embodiment may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It can be understood explicitly and implicitly by those skilled in the art that in the various embodiments of the present application, unless otherwise specified and there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form a new embodiment according to their inherent logical relationship.

[0323] It should be understood that in the present application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0324] It should be noted that in this application, "indication" can include direct indication, indirect indication, explicit indication, and implicit indication. When describing that a certain indication information is used to indicate A, it can be understood that the indication information carries A, directly indicates A, or indirectly indicates A.

[0325] In this application, the information indicated by the indication information is referred to as the information to be indicated. In specific implementations, there are many ways to indicate the information to be indicated. For example, but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or an index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, where the other information is associated with the information to be indicated. Alternatively, only a portion of the information to be indicated can be indicated, while the rest of the information to be indicated is known or agreed upon in advance. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-specified) order of the various information, thereby reducing indication overhead to a certain extent. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. The transmission period and / or transmission timing of these sub-information can be the same or different. The specific transmission method is not limited in this application. The transmission period and / or transmission timing of these sub-information can be pre-defined, for example, according to a protocol, or can be configured by the transmitting device sending configuration information to the receiving device.

[0326] It should be noted that in this application, "send" can be understood as "output" and "receive" can be understood as "input". "Send information to A", where "to A" only indicates the direction of information transmission, A is the destination, and does not limit "sending information to A" to direct transmission on the air interface. "Sending information to A" includes sending information directly to A, and also includes sending information indirectly to A through a transmitter, so "sending information to A" can also be understood as "outputting information to A". Similarly, "receiving information from A" indicates that the source of the information is A, including receiving information directly from A, and also including receiving information indirectly from A through a receiver, so "receiving information from A" can also be understood as "inputting information from A".

[0327] Before introducing the present application, some of the terms used in the embodiments of the present application are briefly explained to facilitate understanding by those skilled in the art.

[0328] 1) Terminal side device is a device that provides voice and / or data connectivity to users. In the embodiments of the present application, the terminal side device may be referred to as user equipment (UE), terminal device, terminal, mobile station (MS), mobile terminal (MT), etc. For example, the terminal side device may include a handheld device with a wireless connection function, or a communication device connected to a wireless modem. The terminal side device can communicate with the core network via the radio access network (RAN) and exchange voice and / or data with the RAN.

[0329] Some examples of terminal-side devices include: mobile stations (MS), subscriber units, cellular phones, smart phones, wireless data cards, personal digital assistants (PDAs), computers, tablet computers, wireless modems, handsets, laptop computers, machine type communication (MTC) terminals, wearable devices, and vehicle-mounted terminal devices. Terminal-side devices also include restricted devices, such as devices with low power consumption, limited storage capacity, or limited computing power. Terminal-side devices also include information sensing devices such as barcodes, radio frequency identification (RFID), sensors, global positioning systems (GPS), and laser scanners.

[0330] The functions of the terminal-side device can be implemented by hardware components inside the terminal device, and the above-mentioned hardware components can be a processor and / or a programmable chip inside the above-mentioned terminal device. Optionally, the chip can be implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The above-mentioned PLD can be any one of a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), and a system on a chip (SOC), or any combination thereof.

[0331] 2) Donor gNodeB, also known as the donor node, can access the core network through the donor node. In other words, the donor base station is a device in the communication system that connects the terminal side device to the core network. The donor base station is generally connected to the core network through a wired link (such as an optical fiber cable). The donor base station can be responsible for receiving data from the core network and forwarding it to the wireless backhaul device (such as an IAB node), or receiving data from the wireless backhaul device and forwarding it to the core network. The donor base station can generally be connected to the network via a wired connection.

[0332] As an example, the donor base station may include a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a home evolved NodeB, or home Node B, HNB), a base band unit (BBU), etc., and may also include an evolved base station (NodeB or eNB or e-NodeB, evolutionary Node B) in an evolved LTE system (LTE-Advanced, LTE-A), or may also include a next generation node B (gNB) in a fifth generation mobile communication technology (5G) new radio (NR) system. As another example, the donor base station may include a centralized unit (CU) (abbreviated as Donor-CU or gNB-CU in this application) and a distributed unit (DU) (abbreviated as Donor-DU or gNB-DU in this application). The gNB-CU and gNB-DU are connected via the F1 interface, which may further include a control plane interface (F1-C) and a user plane interface (F1-U). The donor-CU and the core network are connected via a next-generation (NG) interface. A gNB-CU or donor-CU may exist with a separate user plane (UP) (referred to herein as CU-UP) and control plane (CP) (referred to herein as CU-CP). Specifically, a gNB-CU or donor-CU consists of a CU-CP and a CU-UP. A gNB-CU may include one gNB-CU-CP and at least one gNB-CU-UP. Alternatively, a donor-CU may include one donor-CU-CP and at least one donor-CU-UP.

[0333] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0334] The functions of the donor base station may be implemented by hardware components within the donor base station, such as a processor and / or programmable chip within the donor base station. For example, the chip may be implemented using an ASIC or a programmable logic device (PLD). The PLD may be any one of a CPLD, an FPGA, a GAL, and a SOC, or any combination thereof.

[0335] This application provides a communication method, which is applied to the field of communication technology, such as communication in an IAB network. In order to more clearly describe the solution of this application, some knowledge related to IAB is first introduced below.

[0336] In an IAB network, an IAB node can establish a wireless backhaul link with one or more upper-level nodes and access the core network through the upper-level node. The upper-level node can perform certain control on the relay node through various signaling (for example, data scheduling, timing modulation, power control, etc.). In addition, the relay node can establish an access link with one or more lower-level nodes and provide access services for one or more lower-level nodes. The upper-level node of the relay node can be a base station or another relay node. The lower-level node of the relay node can be a terminal or another relay node. In some cases, the upper-level node of an IAB node can also be referred to as its upstream node or parent node, and the lower-level node of the IAB node can also be referred to as its downstream node or child node.

[0337] Please refer to FIG1 , which is a schematic structural diagram of an IAB system provided in an embodiment of the present application.

[0338] As shown in Figure 1, an IAB node provides wireless access and wireless backhaul for UEs. An IAB donor node provides wireless backhaul functionality to the IAB node and provides an interface between the UE and the core network. The IAB node connects to the IAB donor node via a wireless backhaul link, connecting the UE served by the IAB node to the core network.

[0339] Please refer to FIG. 2 , which is a schematic diagram of the structure of an IAB node provided in an embodiment of the present application.

[0340] As shown in Figure 2, the IAB node in NR can be divided into two parts: the Mobile Equipment Unit (MT) and the User Equipment Unit (DU). The MT can also be understood as a component similar to a UE. In an IAB node, the MT is referred to as a function residing on the IAB node. Since the MT functions similarly to a regular UE, it can be understood that the MT is used for communication between the IAB node and its upper-level nodes. The DU, in contrast to the CU function of network equipment, is used for communication between the IAB node and its lower-level nodes. It should be understood that the upper-level node can be a base station or other IAB node, and the lower-level node can be a UE or other IAB node.

[0341] The communication method provided in the embodiments of the present application can be applied to various communication systems including relay nodes, such as NR systems, LTE systems, LTE-A systems, worldwide interoperability for microwave access (WiMAX), or wireless local area networks (WLAN). In LTE, relay nodes are generally referred to as RNs. In NR, relay nodes are generally referred to as IAB nodes. In some embodiments, relay nodes may also be referred to as relay devices, or relay transmission and reception points (rTRPs), and the upper node of the relay node may be a network device (including a DU of a network device, or including a CU of a network device, etc.).

[0342] Please refer to FIG3 , which is a schematic diagram of the structure of an IAB network provided in an embodiment of the present application.

[0343] As shown in Figure 3, the IAB network includes multiple UEs and multiple IAB nodes. Figure 3 takes two UEs and five IAB nodes as an example. Among them, the two UEs are UE1 and UE2, and the five IAB nodes are IAB nodes 1 to IAB nodes 5. It should be understood that the thick line in Figure 3 indicates the access link, and the thin line indicates the backhaul link. Among them, UE2 can be connected to the host base station via IAB node 5, IAB node 2, and IAB node 1. UE2 can also be connected to the host base station via IAB node 4, IAB node 2, and IAB node 1. Alternatively, UE2 can also be connected to the host base station via IAB node 4, IAB node 3, and IAB node 1. UE1 can be connected to the host base station via IAB node 4, IAB node 3, and IAB node 1. UE1 can be connected to the host base station via IAB node 4, IAB node 2, and IAB node 1.

[0344] It should be noted that the communication system shown in Figure 3 is only an example and does not limit the application scenarios applicable to the embodiments of the present application. It should be understood that the use of IAB nodes in the embodiments of the present application is only for descriptive purposes and does not mean that the solution of the embodiments of the present application is only used in NR scenarios. In the embodiments of the present application, IAB nodes can generally refer to any node or device with a relay function. The use of IAB nodes and relay nodes in the implementation of this application should be understood to have the same meaning.

[0345] In an IAB network, an IAB node is connected to the core network via an IAB host node. For example, in a standalone (SA) 5G architecture, an IAB node is connected to the 5G core network (5GC / 5GCN) via an IAB host node. For another example, in a dual connectivity (DC) or multi-connectivity (MC) 5G architecture (e.g., non-standalone, NSA scenarios), on the primary path, an IAB node can be connected to the evolved packet core (EPC) via an evolved NodeB (eNB), or to the 5G core network via an IAB host.

[0346] In the IAB network, a transmission path between the UE and the IAB host may include one or more IAB nodes. Each IAB node needs to maintain a wireless backhaul link towards the parent node, and also needs to maintain a wireless link with the child node. If the child node of the IAB node is a UE, there is a wireless access link between the IAB node and its child node (i.e., the UE). If the child node of the IAB node is another IAB node, there is a wireless backhaul link between the IAB node and its child node (i.e., the other IAB node). For example, referring to Figure 3, in the path "UE1→IAB node 4→IAB node 3→IAB node 1→IAB host", UE1 accesses IAB node 4 through a wireless access link, IAB node 4 is connected to IAB node 3 through a wireless backhaul link, IAB node 3 is connected to IAB node 1 through a wireless backhaul link, and IAB node 1 is connected to the IAB host node through a wireless backhaul link.

[0347] In the embodiment of the present application, the access IAB node refers to the IAB node accessed by the UE, and the intermediate IAB node refers to the IAB node that provides wireless backhaul services for the UE or IAB node. For example, referring to Figure 3, in the path "UE1→IAB node 4→IAB node 3→IAB node 1→IAB host", IAB node 4 is the access IAB node, and IAB node 3 and IAB node 1 are intermediate IAB nodes. It should be noted that an IAB node is an access IAB node for the UE accessing the IAB node; it is an intermediate IAB node for the UE accessing other IAB nodes. Therefore, whether an IAB node is an access IAB node or an intermediate IAB node is not fixed and can be determined according to the specific application scenario.

[0348] It should be noted that the communication system shown in Figure 3 is only an example and does not limit the application scenarios applicable to the embodiments of the present application. It should be understood that the use of the IAB node in the embodiments of the present application is only for descriptive purposes and does not mean that the solution of the embodiments of the present application is only used in new radio (NR) scenarios.

[0349] An F1 interface exists between the DU of the IAB node and the CU of the IAB host. This F1 interface may include a control plane and a user plane. The user plane is maintained between the IAB-DU and the IAB donor CU-UP, while the control plane is maintained between the IAB-DU and the IAB donor CU-CP. This F1 interface may also be referred to as an F1* interface, and this embodiment of the application does not impose any restrictions on the name of this interface. This document will refer to this interface as the F1 interface as an example.

[0350] The F1 interface supports user plane protocols (F1-U / F1*-U) and control plane protocols (F1-C / F1*-C). The user plane protocols include one or more of the following protocol layers: the General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U), the User Datagram Protocol (UDP), and the Internet Protocol (IP). The control plane protocols include one or more of the following protocol layers: the F1 Application Protocol (F1AP), the Stream Control Transport Protocol (SCTP), and the IP. The control plane of the F1 / F1* interface enables interface management, IAB-DU management, and UE context configuration between the IAB node and the IAB host. The user plane of the F1 / F1* interface enables user plane data transmission and downlink transmission status feedback between the IAB node and the IAB host.

[0351] For example, please refer to Figures 4 and 5, where Figure 4 is a schematic diagram of a control plane protocol architecture in an IAB network provided in an embodiment of the present application, and Figure 5 is a schematic diagram of a user plane protocol architecture in an IAB network provided in an embodiment of the present application.

[0352] On the control plane, as shown in Figure 4, a Uu interface is established between UE1 and IAB2-DU. The corresponding protocol layers include the radio link control protocol (RLC), media access control (MAC), and physical layer (PHY). An F1-C interface is established between the IAB2-DU and IAB donor CU 1. The corresponding protocol layers include the F1AP and SCTP layers. IAB donor DU 1 and IAB donor CU 1 are connected via a wired connection. The corresponding protocol layers include the Internet Protocol (IP), Layer 2, and Layer 1. BLs are established between IAB Node 2 and IAB Node 3, between IAB Node 3 and IAB Node 1, and between IAB Node 1 and IAB donor DU 1. The corresponding protocol layers include the Backhaul Adaptation Protocol (BAP), RLC, MAC, and PHY layers. In addition, a peer-to-peer radio resource control (RRC) layer and packet data convergence protocol (PDCP) layer are established between UE1 and IAB donor CU 1, and a peer-to-peer IP layer is established between IAB2-DU and IAB donor DU 1.

[0353] As can be seen, compared to the control plane protocol stack for a single air interface, the DU connected to the IAB node implements the functions of a single air interface gNB-DU (i.e., establishing peer RLC, MAC, and PHY layers with the UE, and establishing peer F1AP and SCTP layers with the CU). In other words, the DU connected to the IAB node in the IAB network implements the functions of a single air interface gNB-DU, while the IAB donor CU implements the functions of a single air interface gNB-CU.

[0354] On the control plane, RRC messages are encapsulated in F1AP messages for transmission between the access IAB node and the IAB donor CU. Specifically, in the uplink, UE1 encapsulates the RRC message in a PDCP protocol data unit (PDU), which is processed sequentially by the RLC, MAC, and PHY layers before being sent to the IAB2-DU. The IAB2-DU is processed sequentially by the PHY, MAC, and RLC layers to obtain a PDCP PDU. This PDCP PDU is then encapsulated in a F1AP message and processed sequentially by the SCTP and IP layers to obtain an IP packet. The IAB2-MT processes the IP packet through the BAP, RLC, MAC, and PHY layers before sending it to the IAB3-DU. The IAB3-DU is processed sequentially by the PHY, MAC, RLC, and BAP layers to obtain an IP packet. The IAB3-MT then uses similar operations as the IAB2-MT to send the IP packet to the IAB1-DU. Similarly, the IAB1-MT sends the IP packet to the IAB donor DU 1. After IAB donor DU 1 parses the IP packet, it sends it to IAB donor CU 1. IAB donor CU 1 processes the IP packet through the SCTP layer, the F1AP layer, and the PDCP layer, obtaining an RRC message. The downlink direction is similar and will not be described here.

[0355] For the user plane, as shown in Figure 5, a Uu interface is established between UE1 and IAB2-DU. The peer protocol layers include the RLC layer, MAC layer, and PHY layer. An F1-U interface is established between the IAB2-DU and IAB donor CU 1. The peer protocol layers include the GTP-U layer and the User Datagram Protocol (UDP) layer. IAB donor DU 1 and IAB donor CU 1 are connected via a wired connection. The peer protocol layers include the IP layer, L2, and L1. A BL is established between IAB node 2 and IAB node 3, between IAB node 3 and IAB node 1, and between IAB node 1 and IAB donor DU 1. The peer protocol layers include the BAP layer, RLC layer, MAC layer, and PHY layer. Furthermore, the peer SDAP layer and PDCP layer are established between UE1 and IAB donor CU 1, and the peer IP layer is established between the IAB2-DU and IAB donor DU 1.

[0356] As can be seen, compared to the user plane protocol stack of a single air interface, the IAB access node DU implements some of the functions of a single air interface gNB-DU (i.e., establishing peer RLC, MAC, and PHY layers with the terminal, and establishing peer GTP-U and UDP layers with the IAB donor CU 1). It can be understood that the IAB access node DU implements the functions of a single air interface gNB-DU, while the IAB donor CU implements the functions of a single air interface gNB-CU.

[0357] On the user plane, PDCP packets are encapsulated and transmitted in a GTP-U tunnel between the access IAB node and the IAB donor CU. The GTP-U tunnel is established on the F1-U interface.

[0358] The communication method provided in this application is primarily applicable to IAB networks, including standalone (SA) and non-standalone (NSA) IAB networks. An IAB node consists of a mobile operator (MT) and a user-defined unit (DU). An IAB donor can be further divided into a DU and a user-defined unit (CU). The CU can also be divided into a CU-CP and a CU-UP.

[0359] Please refer to FIG. 6 , which is an example of an IAB network architecture diagram provided in an embodiment of the present application.

[0360] Figure 6 shows an example of an IAB node connected to an IAB donor via a wireless backhaul link. Figure 6 uses a scenario involving one UE, two IAB nodes, and two IAB donors. The two IAB nodes are IAB node 1 and IAB node 2, each consisting of an MT and a DU. The two IAB donors are IAB donor 1 and IAB donor 2. Each IAB donor can be further divided into a DU and a CU, and the CU can be further divided into a CU-CP and a CU-UP. In Figure 6, the MT of IAB node 2 and the DU of IAB node 1, the MT of IAB node 1 and the DU of IAB donor 1, and the MT of IAB node 1 and the DU of IAB donor 2 all communicate through a wireless backhaul (BH) link; a Uu interface is established between the UE and the IAB2-DU; an F1-C interface is established between the IAB donor DU and the IAB donor CU-CP, and an F1-U interface is established between the IAB donor DU and the IAB donor CU-UP; the DU of IAB donor 2 and the CU of IAB donor 1 are connected through an Internet protocol (IP) network.

[0361] When the IAB node operates in SA mode, the IAB node can be connected to one parent node or two parent nodes. The two parent nodes can be controlled by the same IAB donor or by different IAB donors. An F1 interface is established between the DU part of the IAB node and an IAB donor. The IAB donor can be connected to the 5G core network, which is the dotted line part in Figure 6. The IAB-donor-CU-CP is connected to the control plane network elements (such as access and mobility management functions) in the 5GC through the NG control plane interface (NG-C), and the IAB-donor-CU-UP is connected to the user plane network elements (such as user plane functions) in the 5GC through the NG user plane interface (NG-U).

[0362] When the IAB node works in NSA mode, the IAB-donor-CU-UP can be connected to the EPC (for example, connected to the serving gateway (SGW)) through the S1 user plane interface (S1-U), there is an LTE Uu air interface connection between the MeNB and the MT of the IAB node, there is an X2-C interface between the MeNB and the IAB-donor-CU-CP, and the MeNB is connected to the EPC through the S1 interface (including the S1 interface user plane and the S1 interface control plane), which is the dotted line part in Figure 6.

[0363] In another possible scenario, the MeNB in ​​Figure 6 can be replaced with a 5G gNB. The LTE-Uu interface in Figure 6 is correspondingly replaced with an NR-Uu interface. The gNB can establish user plane and / or control plane interfaces with the 5GC. The gNB and IAB-donor provide dual connectivity services for the IAB node. The gNB can act as the primary base station or secondary base station for the IAB node.

[0364] The above is an example of an application scenario of the technical solution of the embodiment of the present application. It should be understood that the technical solution of the embodiment of the present application is not limited to application only in the network architecture shown in Figure 6.

[0365] In the IAB network, IAB nodes are mobile, such as vehicle-mounted IAB nodes. For example, a mobile IAB node can be called a mobile IAB node (mIAB). As shown in Figure 7, the mIAB node can switch from IAB donor 1 to IAB donor 2 during movement. Since the coverage of the donor CU1 is limited, it is impossible to maintain the F1 connection with the mIAB-DU all the time. Therefore, the F1 connection of the mIAB-DU needs to be migrated from Donor-CU1 to Donor-CU2. In this scenario, the way in which the mIAB-DU needs to migrate the RRC connection and the F1 connection from Donor-CU1 to Donor-CU2 can be called full migration.

[0366] For example, in the IAB network, in order to enhance network robustness and achieve more refined load balancing and topology management, the mAB node can perform a partial migration process, that is, the MT of the mAB node (IAB-MT2 in Figure 7) switches from one parent node (IAB-node1 in Figure 7) to another parent node (IAB-node3 in Figure 7). The two parent nodes belong to topologies controlled by different host CUs, that is, IAB-node1 in Figure 7 belongs to the topology controlled by Donor-CU1 (the solid box part in Figure 7), and IAB-node3 belongs to the topology controlled by Donor-CU2 (the dotted box part in Figure 7). During the partial migration process, the RRC connection of IAB-MT2 is switched from CU1 to CU2, but the F1 connection of IAB-DU2 is still terminated in CU1 (as shown by the solid arrow in Figure 7), and is not migrated to CU2 along with IAB-MT2. It is understandable that the F1 connection of the child node IAB node 4 of the IAB node 2 may also be terminated at CU1 (as indicated by the dotted arrow in FIG7 ).

[0367] For example, the F1 interface of IAB node 2 is terminated at CU1, and IAB host 1 can be referred to as the F1-terminating IAB-donor of IAB node 2. CU2 has an RRC connection with IAB node 2, but the F1 connection of IAB node 2 is not terminated at CU2, and IAB host 2 can be referred to as the non-F1-terminating IAB-donor of IAB node 2.

[0368] After IAB node 2 switches from the CU1 topology to the CU2 topology, the 3rd Generation Partnership Project (3GPP) Release-17 standard (R17) introduces the IAB Transport Migration Management process to migrate the data traffic of IAB node 2 from the CU1 topology to the CU2 topology. That is, CU1 can perform the IAB Transport Migration Management process to migrate the data traffic of IAB node 2 to CU2 through the Xn interface between CU1 and CU2. The IAB Transport Migration Management process is as follows:

[0369] Step S701: CU1 sends an IAB Transport Migration Management request message to CU2. Correspondingly, CU2 receives the IAB Transport Migration Management request message.

[0370] CU1 is the F1-terminating IAB-donor of IAB node 2, and CU2 is the non-F1-terminating IAB-donor of IAB node 2. The IAB transport migration management request message is used to request migration of data traffic of IAB node 2 to CU2.

[0371] Step S702: CU2 sends an IAB Transport Migration Management response message to CU1. Correspondingly, CU1 receives the IAB Transport Migration Management response message.

[0372] The IAB transmission migration management response message is used to respond to the IAB transmission migration management request message, so as to migrate the data traffic of the IAB node 2 to the CU2.

[0373] The details of the above-mentioned "IAB Transport Migration Management" process can be referred to the 3GPP protocol TS 38.423R17, but it is not limited to the method described in the above-mentioned protocol. In the above-mentioned "IAB Transport Migration Management" process, CUs realize the transfer (offloading) of data traffic by exchanging the quality of service (QoS) of data traffic and the corresponding integrated access and backhaul (IAB) configuration information. The R17 standard defines that this process is initiated by the F1-terminating IAB-donor (i.e., CU1 in Figure 7) to the Non-F1-terminating IAB-donor (i.e., CU2 in Figure 7).

[0374] Furthermore, in an IAB network, given the wide mobility of IAB nodes, when the above-mentioned mAB node moves far away, it may be difficult for the mAB-DU to maintain an IP connection with the original CU, or the transmission delay may be very large. Therefore, to support wide-range mobility, Rel-18 introduced an important feature, DU migration.

[0375] Please refer to FIG8 , which is an example of DU migration in an IAB network provided in an embodiment of the present application.

[0376] As shown in Figure 8, the RRC connection of mAB-MT is always on CU2, the F1 interface of mAB-DU can be migrated from CU1 to CU3, and the F1 interface of mAB-DU can also be migrated from CU1 to CU4. The mAB-DU1 and mAB-DU2 in Figure 8 can be understood as two logical DUs on a physical DU. DU migration is achieved in this way: assuming that the original DU is mAB-DU1, mAB-node generates a new logical DU as mAB-DU2, mAB-DU2 establishes an F1 interface with CU3, CU1 sends a UE handover request to CU3, and switches the UE from the cell under mAB-DU1 to the cell under mAB-DU2. Then CU1 releases the F1 interface between it and mAB-DU1. At this point, DU migration is completed. Alternatively, assuming that the original DU is mAB-DU1, mAB-node generates a new logical DU as mAB-DU2, mAB-DU2 establishes an F1 interface with CU4, CU1 sends a UE handover request to CU4, and hands over the UE from the cell under mAB-DU1 to the cell under mAB-DU2. Then CU1 releases the F1 interface between itself and mAB-DU1. At this point, DU migration is completed.

[0377] In Rel-18, DU migration and MT migration are assumed to be completely decoupled. That is, the DU's CU and the MT's CU can always be different. Therefore, if the F1 terminating CU of an mAB-DU is always CU2, the MT does not necessarily switch from CU1 to CU2 (although this is possible). In DU migration, the MT can be in CU2 while the DU migrates from CU1 to CU3 (specifically, CU2 can be the same CU as CU1 or CU3), or the DU migrates from CU1 to CU4 (specifically, CU2 can be the same CU as CU1 or CU4). The reason for assuming complete decoupling between DU and MT migration is that the DU migration process is complex (requiring the generation of two logical DUs and the individual switching of UEs to the new logical DUs). DU migration is not recommended for frequent use, and the DU's CU is preferably a CU with a large control range. MT migration, on the other hand, is a MT handover and may occur frequently. The MT CU selection is determined by signal quality, and the MT's CU may be different from the DU's CU.

[0378] How does an IAB-node know which CU its DU is connected to when joining the network? How does the IAB-node know which DU migration it needs to perform and the corresponding target CU? Currently, there are two methods: OAM triggering or CU triggering. The following describes each method in detail:

[0379] (1) In the case of OAM triggering, OAM configures the CU of the IAB-DU (for DU migration, it refers to the target CU) on the IAB-node. For example, it can be pre-configured when the IAB leaves the factory (for example, for IAB nodes with a determined approximate deployment location or deployed on a fixed running track, such as the IAB node on a bus); or after the IAB-MT joins the network, the OAM server selects a nearby base station that is suitable as the CU of the IAB-DU based on the location of the IAB-node, and sends the identifier of the IAB-DU CU to the IAB-node through the PDU session between the IAB-MT and the core network.

[0380] (2) For CU-triggered scenarios, specifically, for network access, CU2 informs the IAB-MT of CU1's identifier; for DU migration, CU1 informs the IAB-DU1 of CU3's identifier (it is generally not considered that CU2 informs the IAB-MT because DU migration is triggered by the DU's source CU). IAB-DU1 triggers IAB-DU2 through the internal interface to initiate the establishment of the F1 interface to CU3.

[0381] Although the IAB-node can determine that it is performing DU migration and the corresponding target CU through OAM triggering / CU triggering, in the case of a conflict between the OAM triggering and the CU triggering, the IAB-node still cannot determine the target CU corresponding to the DU migration, or the IAB-node may determine the wrong target CU corresponding to the DU migration. For example, the OAM triggering indicates that the target CU corresponding to the DU migration is CU2, and the CU triggering indicates that the target CU corresponding to the DU migration is CU3, then the IAB-node may not be able to determine whether the target CU corresponding to the DU migration is CU2 or CU3. It is understandable that the order in which the IAB-node receives the OAM triggering indication information and the CU triggering indication information is not limited. The CU triggering indication information may be received during the process of performing DU migration according to the OAM triggering indication information, or the OAM triggering indication information may be received during the process of performing DU migration according to the CU triggering indication information. At this time, since the IAB-node cannot determine the target CU corresponding to the DU migration, it may cause the IAB-node to be unable to perform DU migration normally, or the DU migration may fail.

[0382] In view of this, an embodiment of the present application provides a new communication method, which can enable the IAB node to handle the trigger conflict caused by CU triggering and OAM triggering when performing DU migration, so as to determine the target CU corresponding to DU migration, thereby ensuring that the IAB node successfully completes DU migration.

[0383] Please refer to Figure 9, which is a flow chart of a communication method provided in an embodiment of the present application. The communication method is applied to the field of communication technology, such as communication of an IAB network, and includes but is not limited to the following steps:

[0384] S901: The relay node generates first information.

[0385] S902: The relay node sends first information to the first host node. Correspondingly, the first host node receives the first information from the relay node.

[0386] It is understood that the relay node in the embodiments of the present application can be a device equipped with a processor / chip capable of executing computer-executable instructions, or a processor / chip capable of executing computer-executable instructions. The relay node in the embodiments of the present application includes a terminal-side portion facing the parent node and a network-side portion facing the child node. For example, it can include a mobile operator (MT) and a user-defined unit (DU), or it can include an MT and a gNB, although this is not limited in the embodiments of the present application. The DU migration and MT migration of the relay node are completely decoupled, so the host node connected to the MT of the relay node and the host node connected to the DU can be different or the same. For example, the MT and DU of the relay node are both connected to the first host node. For another example, the MT of the relay node is connected to the second host node, and the DU of the relay node is connected to the first host node. When the communication method in the embodiments of the present application is applied to an IAB network, the relay node can be an IAB node, the DU of the IAB node is connected to the first host node, and the host node connected to the MT of the IAB node is not limited in the embodiments of the present application. For example, it can be the first host node, the second host node, or the target host node. Exemplarily, the relay node may be the mAB node in FIG. 8 , configured to execute the communication method in the embodiment of the present application to determine the target CU corresponding to the DU migration, thereby ensuring that the IAB node successfully completes the DU migration.

[0387] It can be understood that the first host node in the embodiment of the present application can be a device equipped with a processor / chip that can be used to execute computer-executable instructions, or it can be a processor / chip that can be used to execute computer-executable instructions. The first host node in the embodiment of the present application is the source CU corresponding to the DU of the relay node, and the first host node is connected to the DU of the relay node before the relay node performs DU migration. When the communication method in the embodiment of the present application is applied to the IAB network, the relay node can be an IAB node, and the first host node can be connected to the DU of the IAB node. Exemplarily, the first host node can be CU1 in Figure 8 above, which is used to execute the communication method in the embodiment of the present application to determine the target CU corresponding to the DU migration, thereby ensuring that the IAB node successfully completes the DU migration.

[0388] The second host node and the target host node in the embodiment of the present application can be devices equipped with a processor / chip that can be used to execute computer-executable instructions, or can be a processor / chip that can be used to execute computer-executable instructions. The second host node in the embodiment of the present application is the wrong host node after the DU migration, and the target host node is the correct host node after the DU migration. For example, in the case of a trigger conflict, the instruction triggered by the network manager shall prevail, then the host node indicated by the network manager is the correct host node, and the host node indicated by the first host node is the wrong host node. For example, in the case of a trigger conflict, the instruction triggered by the network manager shall prevail, the network manager instructs to migrate the DU of the relay node to the third host node, and the first CU instructs to migrate the relay node to the fourth host node. Then, the third host node is the correct host node, and the fourth host node is the wrong host node. Exemplarily, the second host node can be CU4 in Figure 8 above, and the target host node can be CU3 in Figure 8 above, which is used to execute the communication method in the embodiment of the present application to determine the target CU corresponding to the DU migration, thereby ensuring that the IAB node successfully completes the DU migration.

[0389] The network manager in the embodiment of the present application can be a device equipped with a processor / chip that can be used to execute computer-executable instructions, or it can be a processor / chip that can be used to execute computer-executable instructions. The network manager in the embodiment of the present application is the network manager of the relay node, which can communicate with the relay node. The network manager usually refers to an operation, management and maintenance (orchestration and management, OAM) server, which can be any network element located in the core network. The OAM trigger mentioned above usually refers to the OAM instructing the relay node to perform DU migration through pre-configuration or remote control. When the communication method in the embodiment of the present application is applied to the IAB network, the network manager can be an OAM server, and the OAM server can be connected to the IAB node. For example, the OAM server is connected to the MT of the IAB node, or the OAM server is connected to the DU of the IAB node, and this embodiment of the present application is not limited to this.

[0390] Specifically, the above S901 and / or S902 are executed when the following triggering conditions are met:

[0391] When the first trigger condition is met, the relay node generates the first information. In this case, the first trigger condition can be understood as a condition that triggers the relay node to generate the first information. Optionally, when the first trigger condition is met, the relay node also sends the first information. In this case, the first trigger condition can be understood as a condition that triggers the relay node to generate and send the first information.

[0392] The first trigger condition includes, but is not limited to, one or more of the following:

[0393] (1) Based on the second information provided by the network manager, the network manager provides the second information to the relay node. The second information is used to instruct the relay node to establish a first F1 interface with the target host node.

[0394] (2) The relay node receives the third information from the first host node. Accordingly, the first host node sends the third information to the relay node. The third information is used to instruct the relay node to establish a second F1 interface with the second host node, which is different from the target host node.

[0395] It should be understood that the several trigger conditions listed above are merely illustrative examples of possible triggering the execution of S901 and / or S902, and should not be used to limit the embodiments of the present application. Embodiments obtained based on the supplementation or reasonable deformation of the above trigger conditions all fall within the scope of protection of the embodiments of the present application.

[0396] The first information includes a result of establishing the first F1 interface between the relay node and the target host node. For example, the result may be that the relay node and the target host node complete the establishment of the F1 interface, or that the relay node and the target host node do not complete the establishment of the F1 interface, etc. The embodiment of the present application is not limited to this. The first information may also carry an identifier of the target host node, such as a gNB ID and / or an IP address. The first information may also carry an identifier of the target cell (i.e., a cell under the target DU) (e.g., NR Cell Global Identity NCGI). The first host node may obtain the identifier of the target host node based on the identifier of the target cell.

[0397] Optionally, the first information may be, for example, a message carried in an F1 application protocol (F1 application protocol, F1AP), such as a class 1 RESPONSE MESSAGE or a class 2 MESSAGE.

[0398] Optionally, the second information may be information pre-configured by the network manager. For example, the pre-configuration information instructs the relay node to perform DU migration at a specified time point. Specifically, the pre-configuration information instructs the relay node to start DU migration one hour after joining the network. The implementation methods of the present application do not limit how to pre-configure, the content of the pre-configuration information, etc. The second information may also be sent to the relay node by the network manager through remote control. For example, the network manager may send the second information to the relay node through an IP network. Specifically, the network manager may first send the second information to the non-access stratum (NAS) layer of the relay node, and the NAS layer may then send the second information to the access stratum (AS) layer. The relay node obtains the second information from the AS layer.

[0399] Optionally, the third information is used to instruct the relay node to establish an F1 interface with the second donor node. The third information may carry an identifier of the second donor node, such as a gNB ID and / or an IP address.

[0400] Optionally, the third information may be carried in an F1AP message, and the message name may be MIAB F1 SETUP TRIGGERING.

[0401] In the IAB network, the DU migration of the IAB node supports two triggering modes: source CU triggering and OAM triggering. In the source CU triggering (hereinafter referred to as "CU triggering") mode, the source CU will send an indication message carrying the target CU to the DU in the IAB node, and the DU will complete the migration operation based on the indication message. The source CU is the CU connected to the DU before the migration, and the target CU is the CU connected to the DU after the migration. In the OAM triggering mode, the OAM server can be directly pre-configured in the IAB node or remotely trigger the IAB node to perform DU migration. Obviously, both CU triggering and OAM triggering can instruct the relay node to perform DU migration. If the CU triggering and OAM triggering occur at the same time, the relay node may not be able to complete the DU migration normally, or may migrate to the wrong host node. In addition, in the case of a conflict between the two triggers, at least one trigger indication (such as CU triggering) is not completed, which may also cause abnormalities such as control failure and information transmission errors.

[0402] In the implementation manner of the present application, a first trigger condition for generating (or generating and sending) the result of establishing an F1 interface between the relay node and the target host node is clearly given, wherein the result of establishing the F1 interface can be used to enable the first host node to send UE switching indication information to the correct host node, thereby avoiding the situation where the DU migration of the relay node cannot be completed normally or the migration is erroneous. When the relay node meets the first trigger condition, the relay node can generate (or generate and send) the first information in a timely manner, so that the first host node can initiate a user equipment (UE) switching request to the correct host node (target host node) according to the first information, so that the relay node can complete the DU migration normally, and avoid the relay node's DU migrating to the wrong host node.

[0403] In a possible implementation manner, the result of the first F1 interface is that the F1 interface between the relay node and the target host node is established.

[0404] It can be understood that the F1 interface between the relay node and the target host node is established. For example, the target host node generates and sends an F1AP message (for example, F1 SETUP RESPONSE) to the relay node to indicate that the F1 interface is established. It can also be that the relay node receives an F1AP message (for example, F1 SETUP RESPONSE) returned by the target host node to indicate that the F1 interface is established.

[0405] In the embodiment of the present application, the result of the first F1 interface is that the F1 interface between the relay node and the target host node is established (completed), wherein the target host node is different from the host node indicated by the CU trigger. The relay node sends the information that its F1 interface establishment is completed to the first host node through the first information, so that the first host node can instruct the correct host node (target host node) to perform the UE handover, so that the relay node can successfully complete the DU migration.

[0406] In a possible implementation manner, the second information is further used to trigger the release of the second F1 interface.

[0407] In the embodiments of the present application, the second information is used to instruct the relay node to establish a first F1 interface with the target host node. The second F1 interface is the F1 interface between the relay node and the second host node. If the relay node has already established the second F1 interface with the second host node before receiving the second information, the second information is used to trigger the release of the second F1 interface. This enables the relay node to establish the first F1 interface with the target host node. Furthermore, this can save resources of the second host node, facilitating the second host node's establishment of F1 interfaces with other relay nodes.

[0408] Optionally, the second information provided by the network management is equivalent to OAM triggering the DU migration of the relay node. The OAM triggering time may occur after the CU triggering and before the relay node receives the second F1 interface establishment completion message. For example, the OAM triggering may occur after the relay node sends the F1 interface establishment message to the second host node and before the relay node receives the F1 SETUP RESPONSE message from the second host node.

[0409] It should be noted that the second information may carry information indicating the release of the second F1 interface, or may not carry information indicating the release of the second F1 interface. In the case where the second information carries information indicating the release of the second F1 interface, the relay node may send a request to release the second F1 interface (for example, F1 REMOVAL REQUEST) to the second host node based on the indication information. In the case where the second information does not carry information indicating the release of the second F1 interface, the relay node may default to the DU migration indicated by the second information upon receiving the second information, and thereby autonomously send a request to release the second F1 interface (for example, F1 REMOVAL REQUEST) to the second host node. This is equivalent to a logic that can be built into the relay node, that is, after receiving the indication information triggered by OAM, it defaults to the OAM trigger and terminates the migration process indicated by the CU trigger.

[0410] By triggering the release of the second F1 interface, it is possible to ensure that the establishment of the first F1 interface is completed, so that the relay node can successfully complete the DU migration.

[0411] In a possible implementation manner, the first information further includes an identifier of the target host node and / or a triggering method for DU migration.

[0412] In this embodiment of the present application, the identifier of the target donor node may be, for example, a gNB ID and / or an IP address. The triggering method for DU migration may be, for example, an OAM trigger. The first message carries the identifier of the target donor node, facilitating communication between the first donor node and the target donor node, and instructing the target donor node to perform UE handover. The first message carries the DU migration triggering method, allowing the first donor node to understand why the relay node did not establish the F1 interface as instructed.

[0413] Optionally, when the first F1 interface is an F1 interface established by an OAM trigger indication and / or the OAM trigger is inconsistent with the CU trigger, the first information may include a triggering mode for DU migration.

[0414] Optionally, the first information can be carried in a class 1 RESPONSE message or a REJECT / FAILURE message of the F1 message triggered by the CU, and can also be carried in a separate class 2 message. Among them, the class 1 message needs to get a response from the other end, and the class 2 message does not need to get a response from the other end. For example, the relay node sends a class 1 message (such as RESPONSE / REJECT / FAILURE) to the first host node in response to another class 1 message (such as REQUEST) sent by the first host node to the relay node. When the relay node sends a class 2 message to the first host node, it does not need to be a response message to a specific message, and the class 2 message can be understood as a notification message.

[0415] Please refer to Figure 10, which is a flow chart of a communication method provided in an embodiment of the present application. It is understood that the steps in the embodiment of the present application can be considered as reasonable variations or supplements to the embodiment in Figure 9 above; alternatively, it is understood that the communication method in the embodiment of the present application can also be considered as an embodiment that can be executed independently, and this application does not limit this. The communication method provided in the embodiment of the present application is applicable to the field of communication technology, such as communication in an IAB network.

[0416] It can be understood that the IAB (including IAB-DU and IAB-MT) involved in the communication method provided in the embodiment of the present application can refer to the relay node in the communication method shown in Figure 9 above, CU1 can refer to the first host node in the communication method shown in Figure 9 above, CU3 involved in the communication method provided in the embodiment of the present application can refer to the target host node in the communication method shown in Figure 9 above, CU4 involved in the communication method provided in the embodiment of the present application can refer to the second host node in the communication method shown in Figure 9 above, and the OAM involved in the communication method provided in the embodiment of the present application can refer to the OAM server in the communication method shown in Figure 9 above, which will not be repeated here.

[0417] The communication method may include one or more steps from step 1 to step 6. It should be understood that for the convenience of description, the order of steps 1 to 6 is described here, and it is not intended to limit the execution to the above order. The embodiment of the present application does not limit the order of execution, execution time, and number of executions of the above one or more steps. Steps 1 to 6 are as follows:

[0418] Step 1. OAM triggers DU migration.

[0419] It is understood that OAM triggering DU migration can be triggered by pre-configuration or by remote control. For details, please refer to the description of OAM triggering in Figure 8 above, which will not be repeated here.

[0420] The OAM trigger instructs the IAB-node that the target CU for DU migration is CU3. It should be noted that OAM triggering DU migration generally refers to an instruction from the OAM server that instructs the IAB-node to perform or will perform DU migration. Accordingly, the IAB-node receives the instruction from the OAM server and prepares or is generating instruction information (for example, F1 SETUP RESQUEST) requesting DU migration. Alternatively, based on the OAM trigger, the IAB-node determines to perform DU migration with the target CU being CU3.

[0421] Step 2. IAB-DU2 sends an F1 interface establishment request (eg, F1 SETUP REQUEST) to CU3. Correspondingly, CU3 also receives the F1 interface establishment request from IAB-DU2.

[0422] Step 3. CU triggers DU migration. Specifically, CU1 sends a CU-triggered DU migration indication to IAB-DU1. This message may be carried in an F1AP message, for example, indicating that the target CU for DU migration is CU4. Optionally, this message may include an identifier for CU4, such as a gNB ID and / or IP address.

[0423] Step 4. CU3 sends a message (e.g., F1 SETUP RESPONSE) to IAB-DU2 indicating that the establishment of the F1 interface is complete. Correspondingly, IAB-DU2 also receives a message from CU3 indicating that the establishment of the F1 interface is complete.

[0424] It should be noted that the execution order of step 3 and step 4 is not limited in this embodiment of the application. For example, step 3 may be executed first and then step 4, or step 4 may be executed first and then step 3.

[0425] Step 5. IAB-DU1 sends an F1AP message to CU1.

[0426] From the above steps, it can be seen that the target CUs indicated by the OAM trigger and the CU trigger are different (CU3 and CU4 respectively), and the indication of the OAM trigger shall prevail (that is, IAB-DU2 establishes an F1 interface with CU3). Since IAB-DU2 and CU3 have already established the F1 interface, CU1 now needs to instruct CU3 to switch the UE. Therefore, the F1AP message sent by IAB-DU1 to CU1 includes the result of IAB-DU2 and CU3 establishing the F1 interface, for example, IAB-DU2 and CU3 have completed the establishment of the F1 interface. Optionally, the F1AP message will also carry the identifier of CU3, such as gNB ID and / or IP address, etc. It is used to allow CU1 to issue a UE switching instruction to the correct CU (CU3), thereby completing the DU migration of the IAB-node.

[0427] Optionally, the F1AP message may also carry indication information of a DU migration triggering mode (eg, OAM triggering).

[0428] Optionally, the F1AP message may be carried in a class 1 message of the CU-triggered F1 message, such as a RESPONSE message or a REJECT / FAILRE message. The F1AP message may also be carried in a class 2 message of the CU-triggered F1 message, such as a UL RRC MESSAGE TRANSFER or DL ​​RRC MESSAGE TRANSFER.

[0429] Optionally, when the following conditions are met, the F1AP message may carry indication information of the DU migration triggering mode.

[0430] Step 6. CU1 sends an instruction message to CU4 to cancel the establishment of the F1 interface.

[0431] The indication information may be carried in an F1AP message. For example, the indication message is used to indicate the cancellation of the F1 interface between CU4 and IAB-DU2. Optionally, the indication information may carry an identifier of IAB-DU2, such as a gNB ID and / or IP address.

[0432] Step 6 is optional and exemplary, and may be performed when one or more of the following conditions are met, including:

[0433] (1) CU1 receives the F1AP message described in step 5, which is equivalent to the completion of step 5. For example, CU1 receives an indication that the relay node and the target host node have completed the establishment of the F1 interface, and the target host node is different from the second host node. Specifically, CU1 receives an indication that IAB-DU2 and DU3 have completed the establishment of the F1 interface.

[0434] (2) CU1 and CU4 interact with each other. For example, CU1 sends an instruction message to CU4 to instruct CU4 to establish an F1 interface with IAB-DU2. Alternatively, CU1 sends an instruction message to CU4 to instruct CU4 to establish an F1 interface with IAB-DU2.

[0435] (3) There is a preset configuration in CU4, which is used to instruct CU4 to establish an F1 interface with IAB-DU2.

[0436] Optionally, conditions 2 and 3 occur during the DU migration process of the IAB-node.

[0437] The embodiments of the present application clarify that when a trigger conflict occurs during DU migration, the OAM trigger shall prevail, thereby avoiding the uncertainty of the target CU of DU migration caused by the trigger conflict and ensuring the smooth completion of DU migration.

[0438] In the embodiment shown in FIG10 , OAM triggering is earlier than CU triggering, and OAM triggering takes precedence. However, there are also cases where CU triggering is earlier than OAM triggering, and OAM triggering takes precedence.

[0439] Next, please refer to Figure 11, which is a flowchart of another communication method provided in an embodiment of the present application. It is understood that the steps in the embodiment of the present application can be regarded as reasonable variations or supplements to the embodiment of Figure 9 above; alternatively, it is understood that the communication method in the embodiment of the present application can also be regarded as an embodiment that can be executed independently, and this application does not limit this. The communication method provided in the embodiment of the present application is applied to the field of communication technology, such as communication in an IAB network.

[0440] It can be understood that the IAB (including IAB-DU and IAB-MT) involved in the communication method provided in the embodiment of the present application can refer to the relay node in the communication method shown in Figure 9 above, CU1 can refer to the first host node in the communication method shown in Figure 9 above, CU3 involved in the communication method provided in the embodiment of the present application can refer to the target host node in the communication method shown in Figure 9 above, CU4 involved in the communication method provided in the embodiment of the present application can refer to the second host node in the communication method shown in Figure 9 above, and the OAM involved in the communication method provided in the embodiment of the present application can refer to the OAM server in the communication method shown in Figure 9 above, which will not be repeated here.

[0441] The communication method may include one or more steps from step 1 to step 9. It should be understood that for the convenience of description, the description is given in the order of steps 1 to 9, and it is not intended to limit the execution to the above order. The embodiment of the present application does not limit the order of execution, execution time, and number of executions of the above one or more steps. Steps 1 to 9 are as follows:

[0442] Step 1. CU triggers DU migration.

[0443] Specifically, the CUI sends an F1AP message to IAB-DU1, instructing the IAB-node to perform DU migration. In response, IAB-DU1 receives the F1AP message from CU1. Optionally, the message may include the identifier of the target CU. For example, if the target CU is CU4, the F1AP message may include CU4's gNB ID and / or IP address.

[0444] Step 2. IAB-DU2 initiates an F1 interface establishment request to CU4. Correspondingly, CU4 also receives the F1 interface establishment request sent by IAB-DU2.

[0445] For example, the IAB-DU2 may initiate an F1 interface establishment request to the CU4 via an F1AP message, where the F1AP message may be, for example, an F1 SETUP REQUEST message. Optionally, the F1AP message may carry an identifier of the IAB-DU2, such as a gNB ID and / or IP address.

[0446] Step 3: CU4 sends a message indicating that the establishment of the F1 interface is completed to IAB-DU2. Correspondingly, IAB-DU2 also receives a message indicating that the establishment of the F1 interface is completed from CU4.

[0447] For example, CU4 may send a message indicating that the establishment of the F1 interface is completed to IAB-DU2 via an F1AP message. The F1AP message may be, for example, an F1 SETUP REQUEST message.

[0448] Step 4. OAM triggers DU migration.

[0449] It is understood that OAM triggering DU migration can be triggered by pre-configuration or by remote control. For details, please refer to the description of OAM triggering in Figure 8 above, which will not be repeated here.

[0450] The OAM trigger instructs the IAB-node that the target CU for DU migration is CU3. It should be noted that OAM triggering DU migration generally refers to an instruction from the OAM server that instructs the IAB-node to perform or will perform DU migration. Accordingly, the IAB-node receives the instruction from the OAM server and prepares or is generating instruction information (for example, F1 SETUP RESQUEST) requesting DU migration. Alternatively, based on the OAM trigger, the IAB-node determines to perform DU migration with the target CU being CU3.

[0451] Optionally, the execution order of step 3 and step 4 is not limited in the embodiment of the present application. For example, step 3 may be executed first and then step 4, or step 4 may be executed first and then step 3.

[0452] Step 5. IAB-DU2 sends an F1 interface release request to CU4. Correspondingly, CU4 also receives the F1 interface release request from IAB-DU2.

[0453] After receiving the OAM-triggered indication, the IAB-node knows that it must comply with the OAM-triggered indication. Therefore, the IAB-DU2 sends an F1 interface release request to the CU4. CU4 needs to release the F1 interface before the IAB-DU2 can establish an F1 interface with the CU of another host node.

[0454] The F1 interface release request may be carried in an F1AP message, such as an F1 REMOVAL REQUEST message.

[0455] Optionally, if before step 4, CU1 has started to switch UEs to CU4, then it is also necessary to switch these UEs back to CU1, or to other CUs except CU4.

[0456] Step 6. CU4 sends a message indicating that the F1 interface release is complete to IAB-DU2. Correspondingly, IAB-DU2 also receives a message indicating that the F1 interface release is complete from CU4.

[0457] The information on the completion of releasing the F1 interface may be carried in an F1AP message, for example, an F1 REMOVAL RESPONSE message.

[0458] Step 7. IAB-DU2 sends an F1 interface establishment request to CU3. Correspondingly, CU3 also receives the F1 interface establishment request sent by IAB-DU2.

[0459] After IAB-DU2 receives the F1 interface release completion message from CU4, IAB-DU2 may send F1 interface establishment request message to CU3.

[0460] Optionally, the message may be carried in an F1AP message, for example, an F1 SETUP REQUEST message.

[0461] Step 8. CU3 sends a message to IAB-DU2 indicating that the establishment of the F1 interface is complete. Correspondingly, IAB-DU2 also receives a message from CU3 indicating that the establishment of the F1 interface is complete.

[0462] Optionally, this information may be carried in an F1AP message, for example, an F1 SETUP RESPONSE message.

[0463] Step 9. IAB-DU1 sends an F1AP message to CU1.

[0464] From the above steps, it can be seen that the target CUs indicated by the OAM trigger and the CU trigger are different (CU3 and CU4 respectively), and the indication of the OAM trigger shall prevail (that is, IAB-DU2 establishes an F1 interface with CU3). Since IAB-DU2 and CU3 have already established the F1 interface, CU1 now needs to instruct CU3 to switch the UE. Therefore, the F1AP message sent by IAB-DU1 to CU1 includes the result of IAB-DU2 and CU3 establishing the F1 interface, for example, IAB-DU2 and CU3 have completed the establishment of the F1 interface. Optionally, the F1AP message will also carry the identifier of CU3, such as gNB ID and / or IP address, etc. It is used to allow CU1 to issue a UE switching instruction to the correct CU (CU3), thereby completing the DU migration of the IAB-node.

[0465] Optionally, the F1AP message may also carry indication information of a DU migration triggering mode (eg, OAM triggering).

[0466] Optionally, the F1AP message may be carried in a class 1 message of the CU-triggered F1 message, such as a RESPONSE message or a REJECT / FAILRE message. The F1AP message may also be carried in a class 2 message of the CU-triggered F1 message, such as a UL RRC MESSAGE TRANSFER or DL ​​RRC MESSAGE TRANSFER.

[0467] Optionally, when the following conditions are met, the F1AP message may carry indication information of the DU migration triggering mode.

[0468] The embodiments of the present application clarify that when a trigger conflict occurs during DU migration, the OAM trigger shall prevail, thereby avoiding the uncertainty of the target CU of DU migration caused by the trigger conflict and ensuring the smooth completion of DU migration.

[0469] Please refer to Figure 12, which is a flow chart of another communication method provided in an embodiment of the present application. This communication method is applied to the field of communication technology, such as communication in an IAB network, and includes but is not limited to the following steps:

[0470] S1201: The relay node generates fourth information.

[0471] S1202: The relay node sends fourth information to the network manager. Correspondingly, the network manager receives the fourth information from the relay node.

[0472] It is understood that the relay node in the embodiments of the present application can be a device equipped with a processor / chip capable of executing computer-executable instructions, or a processor / chip capable of executing computer-executable instructions. The relay node in the embodiments of the present application includes a terminal-side portion facing the parent node and a network-side portion facing the child node. For example, it can include a mobile operator (MT) and a user-defined unit (DU), or it can include an MT and a gNB, although this is not limited in the embodiments of the present application. The DU migration and MT migration of the relay node are completely decoupled, so the host node connected to the MT of the relay node and the host node connected to the DU can be different or the same. For example, the MT and DU of the relay node are both connected to the first host node. For another example, the MT of the relay node is connected to the second host node, and the DU of the relay node is connected to the first host node. When the communication method in the embodiments of the present application is applied to an IAB network, the relay node can be an IAB node, the DU of the IAB node is connected to the first host node, and the host node connected to the MT of the IAB node is not limited in the embodiments of the present application. For example, it can be the first host node, the second host node, or the target host node. Exemplarily, the relay node may be the mAB node in FIG. 8 , configured to execute the communication method in the embodiment of the present application to determine the target CU corresponding to the DU migration, thereby ensuring that the IAB node successfully completes the DU migration.

[0473] It can be understood that the first host node in the embodiment of the present application can be a device equipped with a processor / chip that can be used to execute computer-executable instructions, or it can be a processor / chip that can be used to execute computer-executable instructions. The first host node in the embodiment of the present application is the source CU corresponding to the DU of the relay node, and the first host node is connected to the DU of the relay node before the relay node performs DU migration. When the communication method in the embodiment of the present application is applied to the IAB network, the relay node can be an IAB node, and the first host node can be connected to the DU of the IAB node. Exemplarily, the first host node can be CU1 in Figure 8 above, which is used to execute the communication method in the embodiment of the present application to determine the target CU corresponding to the DU migration, thereby ensuring that the IAB node successfully completes the DU migration.

[0474] The second host node and the target host node in the embodiment of the present application can be devices equipped with a processor / chip that can be used to execute computer-executable instructions, or can be a processor / chip that can be used to execute computer-executable instructions. The second host node in the embodiment of the present application is the wrong host node after the DU migration, and the target host node is the correct host node after the DU migration. For example, in the case of a trigger conflict, the instruction triggered by the network manager shall prevail, then the host node indicated by the network manager is the correct host node, and the host node indicated by the first host node is the wrong host node. For example, in the case of a trigger conflict, the instruction triggered by the network manager shall prevail, the network manager instructs to migrate the DU of the relay node to the third host node, and the first CU instructs to migrate the relay node to the fourth host node. Then, the third host node is the correct host node, and the fourth host node is the wrong host node. Exemplarily, the second host node can be CU4 in Figure 8 above, and the target host node can be CU3 in Figure 8 above, which is used to execute the communication method in the embodiment of the present application to determine the target CU corresponding to the DU migration, thereby ensuring that the IAB node successfully completes the DU migration.

[0475] The network manager in the embodiment of the present application can be a device equipped with a processor / chip that can be used to execute computer-executable instructions, or it can be a processor / chip that can be used to execute computer-executable instructions. The network manager in the embodiment of the present application is the network manager of the relay node, which can communicate with the relay node. The network manager usually refers to an operation, management and maintenance (orchestration and management, OAM) server, which can be any network element located in the core network. The OAM trigger mentioned above usually refers to the OAM instructing the relay node to perform DU migration through pre-configuration or remote control. When the communication method in the embodiment of the present application is applied to the IAB network, the network manager can be an OAM server, and the OAM server can be connected to the IAB node. For example, the OAM server is connected to the MT of the IAB node, or the OAM server is connected to the DU of the IAB node, and this embodiment of the present application is not limited to this.

[0476] Optionally, the above S1201 and / or S1202 are executed when the following triggering conditions are met:

[0477] When the second trigger condition is met, the relay node generates the fourth information. In this case, the second trigger condition can be understood as a condition that triggers the relay node to generate the fourth information. Optionally, when the second trigger condition is met, the relay node also sends the fourth information. In this case, the second trigger condition can be understood as a condition that triggers the relay node to generate and send the fourth information.

[0478] The second trigger condition includes but is not limited to the following conditions:

[0479] (1) The relay node receives the fifth information from the first host node, and accordingly, the first host node also sends the fifth information to the relay node, wherein the fifth information is used to instruct the relay node to establish a third F1 interface with the target host node.

[0480] (2) Based on the sixth information provided by the network manager, the relay node receives trigger information from the network manager (which may be pre-configured or remotely controlled). Accordingly, the network manager also provides the sixth information to the relay node, which is equivalent to the network manager pre-configuring OAM trigger information on the relay node, or the network manager triggering DU migration through remote control. The sixth information is used to instruct the relay node to establish a fourth F1 interface with the second host node, which is different from the target host node.

[0481] (3) The relay node receives the seventh information from the target host node, and accordingly, the target host node also sends the seventh information to the relay node, wherein the seventh information is used to indicate that the establishment of the third F1 interface is completed.

[0482] It should be understood that the several trigger conditions listed above are only possible exemplary descriptions for triggering the execution of S1201 and / or S1202, and should not constitute a limitation on the embodiments of the present application. Embodiments obtained based on the supplement or reasonable deformation of the above trigger conditions all fall within the scope of protection of the embodiments of the present application.

[0483] The fifth information may be carried in an F1AP message, such as MIAB F1 SETUP TRIGGERING. The fifth information is used to instruct the relay node to establish a third F1 interface with the target host node, and may be a message instructing the relay node to send a request to the target host node to establish an F1 interface, such as an F1 SETUP REQUEST message.

[0484] Among them, the above-mentioned sixth information can be a message pre-configured by the network manager in the relay node. The pre-configured time can be, for example, before the relay node enters the network, or after the relay node enters the network. The implementation method of the present application does not limit this. The pre-configured information can instruct the relay node to perform DU migration and the host node to which the DU is migrated at a preset time. For example, the pre-configured information can instruct the relay node to start DU migration one hour after entering the network, and instruct the relay node to migrate to the CU of the target host node. The sixth information can also be a message sent by the network manager to the relay node through remote control triggering. For example, the sixth message is sent remotely to the relay node through the IP network to instruct the relay node to establish a second F1 interface with the second host node.

[0485] The seventh information may be carried in an F1AP message, such as F1 SETUP RESPONSE. The relay node may generate the seventh information after receiving a message (such as F1 SETUP RESPONSE) indicating that the F1 interface setup is complete from the target host node.

[0486] In the IAB network, the DU migration of the IAB node supports two triggering modes: source CU triggering and OAM triggering. In the source CU triggering (hereinafter referred to as "CU triggering") mode, the source CU will send an indication message carrying the target CU to the DU in the IAB node, and the DU will complete the migration operation based on the indication message. The source CU is the CU connected to the DU before the migration, and the target CU is the CU connected to the DU after the migration. In the OAM triggering mode, the OAM server can be directly pre-configured in the IAB node or remotely trigger the IAB node to perform DU migration. Obviously, both CU triggering and OAM triggering can instruct the relay node to perform DU migration. If the CU triggering and OAM triggering occur at the same time, the relay node may not be able to complete the DU migration normally, or may migrate to the wrong host node. In addition, in the case of a conflict between the two triggers, at least one trigger indication (such as OAM triggering) is not completed, which may also cause abnormalities such as control failure and information transmission errors.

[0487] In the implementation manner of the present application, the first trigger condition for generating (or generating and sending) the result of establishing the F1 interface between the relay node and the target host node is clearly given, wherein the result of establishing the F1 interface can be used to enable OAM to obtain the latest connection status of the relay node. When the relay node meets the first trigger condition, the relay node can generate (or generate and send) the first information in a timely manner, so that OAM can update the connection status of the relay node in a timely manner, which is convenient for OAM to subsequently manage the relay node and re-trigger the DU migration of the relay node. Obviously, this situation is based on the indication information triggered by the CU. After the relay node establishes the F1 interface connection with the new host node (target host node), the first host node can send an indication of UE switching to the new host node. The first host node obtains that the relay node completes the establishment of the new F1 interface, for example, it can be a message that the relay node sends the F1 interface establishment completion to the first host node, for example, the relay node sends the F1 interface establishment completion message to the first host node through an F1AP message. Specifically, the implementation manner of the present application is not limited.

[0488] In a possible implementation manner, the fifth information is further used to trigger the release of the fourth F1 interface.

[0489] This enables the relay node to establish a third F1 interface with the target host node. In addition, it can save resources of the second host node and facilitate the second host node to establish F1 interfaces with other relay nodes.

[0490] Optionally, the fifth information provided by the network management is equivalent to an OAM trigger, and the time of the OAM trigger may occur after the CU trigger and before the relay node receives the fourth F1 interface establishment completion message. For example, the OAM trigger may occur after the relay node sends the F1 interface establishment message to the second host node and before the relay node receives the F1 SETUP RESPONSE message from the second host node.

[0491] In a possible implementation manner, the fourth information further includes an identifier of the target host node and / or a triggering method for the DU migration.

[0492] The identifier of the target host node may be, for example, a gNB ID and / or IP address. The triggering method for DU migration may be, for example, CU triggering. The fourth information carries the identifier of the target host node, allowing OAM to know that the relay node has established an F1 interface with the target host node and adjust the relay node's connection relationship, facilitating subsequent management of the relay node and execution of the next DU migration. The fourth information carries the DU migration triggering method, allowing OAM to know under whose instructions the relay node established the F1 interface.

[0493] In a possible implementation, the fourth information further includes an identifier of the target host node and / or a triggering method for the DU migration, including:

[0494] When the above-mentioned second trigger condition includes the above-mentioned relay node receiving the above-mentioned fifth information from the above-mentioned first host node and / or the above-mentioned sixth information provided by the above-mentioned network management, the above-mentioned fourth information also includes the identifier of the above-mentioned target host node and / or the triggering method of the above-mentioned DU migration.

[0495] In the implementation manner of the present application, the relay node receives the fifth information from the first host node, which is equivalent to the first host node instructing the relay node to establish an F1 interface with the target host node (CU trigger). Since in the implementation manner of the present application, in the case of a trigger conflict, the CU trigger shall prevail. Therefore, when a trigger conflict occurs and the indication information (fifth information) of the CU trigger is received, sending the fourth information to the OAM can enable the OAM to update the connection relationship of the IAB node in a timely manner, which is convenient for subsequent management. Based on the sixth information provided by the network management, it is equivalent to a trigger conflict, and the indications of the CU trigger are different from those of the OAM trigger (for example, the target host node is different from the second host node). In this case, sending the fourth information to the OAM can also enable the OAM to update the connection relationship of the IAB node in a timely manner, which is convenient for subsequent management.

[0496] Please refer to Figure 13, which is a flowchart illustrating another communication method provided in an embodiment of the present application. It is understood that the steps in the embodiment of the present application can be considered as reasonable variations or supplements to the embodiment in Figure 12 above; alternatively, it is understood that the communication method in the embodiment of the present application can also be considered as an embodiment that can be executed independently, and this application does not limit this. The communication method provided in the embodiment of the present application is applicable to the field of communication technology, such as communication in an IAB network.

[0497] It can be understood that the IAB (including IAB-DU and IAB-MT) involved in the communication method provided in the embodiment of the present application can refer to the relay node in the communication method shown in Figure 12 above, CU1 can refer to the first host node in the communication method shown in Figure 12 above, CU3 involved in the communication method provided in the embodiment of the present application can refer to the target host node in the communication method shown in Figure 12 above, CU4 involved in the communication method provided in the embodiment of the present application can refer to the second host node in the communication method shown in Figure 12 above, and the OAM involved in the communication method provided in the embodiment of the present application can refer to the OAM server in the communication method shown in Figure 12 above, which will not be repeated here.

[0498] The communication method may include one or more steps from step 1 to step 5. It should be understood that for the convenience of description, the order of steps 1 to 5 is described here, and it is not intended to limit the execution to the above order. The embodiment of the present application does not limit the order of execution, execution time, and number of executions of the above one or more steps. Steps 1 to 5 are as follows:

[0499] Step 1. CU triggers DU migration.

[0500] Specifically, the CUI sends an F1AP message to IAB-DU1, instructing the IAB-node to perform DU migration. In response, IAB-DU1 receives the F1AP message from CU1. Optionally, the message may include the identifier of the target CU. For example, if the target CU is CU4, the F1AP message may include CU4's gNB ID and / or IP address.

[0501] Step 2. IAB-DU2 initiates an F1 interface establishment request to CU4. Correspondingly, CU4 also receives the F1 interface establishment request sent by IAB-DU2.

[0502] For example, the IAB-DU2 may initiate an F1 interface establishment request to the CU4 via an F1AP message, where the F1AP message may be, for example, an F1 SETUP REQUEST message. Optionally, the F1AP message may carry an identifier of the IAB-DU2, such as a gNB ID and / or IP address.

[0503] Step 3. OAM triggers DU migration.

[0504] It is understood that OAM triggering DU migration can be triggered by pre-configuration or by remote control. For details, please refer to the description of OAM triggering in Figure 8 above, which will not be repeated here.

[0505] The OAM trigger instructs the IAB-node that the target CU for DU migration is CU3. It should be noted that OAM triggering DU migration generally refers to an instruction from the OAM server that instructs the IAB-node to perform or will perform DU migration. Accordingly, the IAB-node receives the instruction from the OAM server and prepares or is generating instruction information (for example, F1 SETUP RESQUEST) requesting DU migration. Alternatively, based on the OAM trigger, the IAB-node determines to perform DU migration with the target CU being CU3.

[0506] Step 4. CU4 sends a message to IAB-DU2 indicating that the establishment of the F1 interface is complete. Correspondingly, IAB-DU2 also receives a message from CU4 indicating that the establishment of the F1 interface is complete.

[0507] For example, CU4 may send a message indicating that the establishment of the F1 interface is completed to IAB-DU2 via an F1AP message. The F1AP message may be, for example, an F1 SETUP RESPONSE message.

[0508] Optionally, the execution order of step 3 and step 4 is not limited in the embodiment of the present application. For example, step 3 may be executed first and then step 4, or step 4 may be executed first and then step 3.

[0509] Step 5. IAB-node sends IAB node information to the OAM server.

[0510] For example, IAB-DU1 may send IAB node information to the OAM server, or IAB-DU2 may send IAB node information to the OAM server, and IAB-MT may send IAB node information to the OAM server. This embodiment of the present application does not limit this.

[0511] The IAB node message may be used to indicate the establishment result of the F1 interface, for example, indicating the establishment result of the F1 interface between the IAB-node and CU4. The result may be, for example, that the establishment of the F1 interface is complete.

[0512] Optionally, the IAB node information may carry an identifier of CU4, such as a gNB ID and / or an IP address.

[0513] Optionally, the IAB node information may also carry a triggering mode of the DU migration of the IAB-node, for example, the DU migration of the IAB-node is triggered by the CU.

[0514] Optionally, when at least one of the following conditions is met, the triggering mode of the DU migration of the IAB-node may be carried in the IAB node information.

[0515] (1) The triggering method of DU migration of IAB-node is CU triggering.

[0516] (2) The target CU of the IAB-node's DU migration is different from the target CU indicated by the OAM trigger. For example, the IAB-node establishes an F1 interface with CU4 according to the CU trigger. However, the target CU indicated by the OAM trigger is CU3, which is different from CU3.

[0517] The embodiments of the present application clarify that in the event of a trigger conflict during DU migration, the CU trigger is used as the trigger. This avoids the situation where the target CU of the DU migration is uncertain due to the trigger conflict, ensuring the smooth completion of the DU migration. In addition, sending information such as the results of the DU migration of the IAB-node to the OAM server enables the OAM server to promptly adjust the connection relationship of the IAB-node, facilitating the OAM server's subsequent management of the IAB-node and the next DU migration.

[0518] In the embodiment shown in FIG13 , CU triggering is earlier than OAM triggering, and CU triggering takes precedence. However, there are also cases where OAM triggering is earlier than CU triggering, and CU triggering takes precedence.

[0519] Next, please refer to Figure 14, which is a flowchart of another communication method provided in an embodiment of the present application. It is understood that the steps in the embodiment of the present application can be regarded as reasonable variations or supplements to the embodiment of Figure 12 above; alternatively, it is understood that the communication method in the embodiment of the present application can also be regarded as an embodiment that can be executed independently, and this application does not limit this. The communication method provided in the embodiment of the present application is applied to the field of communication technology, such as communication in an IAB network.

[0520] It can be understood that the IAB (including IAB-DU and IAB-MT) involved in the communication method provided in the embodiment of the present application can refer to the relay node in the communication method shown in Figure 12 above, CU1 can refer to the first host node in the communication method shown in Figure 12 above, CU3 involved in the communication method provided in the embodiment of the present application can refer to the target host node in the communication method shown in Figure 12 above, CU4 involved in the communication method provided in the embodiment of the present application can refer to the second host node in the communication method shown in Figure 12 above, and the OAM involved in the communication method provided in the embodiment of the present application can refer to the OAM server in the communication method shown in Figure 12 above, which will not be repeated here.

[0521] The communication method may include one or more steps from step 1 to step 9. It should be understood that for the convenience of description, the description is given in the order of steps 1 to 9, and it is not intended to limit the execution to the above order. The embodiment of the present application does not limit the order of execution, execution time, and number of executions of the above one or more steps. Steps 1 to 9 are as follows:

[0522] Step 1. OAM triggers DU migration.

[0523] It is understood that OAM triggering DU migration can be triggered by pre-configuration or by remote control. For details, please refer to the description of OAM triggering in Figure 8 above, which will not be repeated here.

[0524] The OAM trigger instructs the IAB-node that the target CU for DU migration is CU3. It should be noted that OAM triggering DU migration generally refers to an instruction from the OAM server that instructs the IAB-node to perform or will perform DU migration. Accordingly, the IAB-node receives the instruction from the OAM server and prepares or is generating instruction information (for example, F1 SETUP RESQUEST) requesting DU migration. Alternatively, based on the OAM trigger, the IAB-node determines to perform DU migration with the target CU being CU3.

[0525] Step 2. IAB-DU2 sends an F1 interface establishment request (eg, F1 SETUP REQUEST) to CU3. Correspondingly, CU3 also receives the F1 interface establishment request from IAB-DU2.

[0526] Step 3. CU3 sends a message (e.g., F1 SETUP RESPONSE) to IAB-DU2 indicating that the establishment of the F1 interface is complete. Correspondingly, IAB-DU2 also receives a message from CU3 indicating that the establishment of the F1 interface is complete.

[0527] Step 4. CU triggers DU migration. Specifically, CU1 sends a CU-triggered DU migration indication to IAB-DU1. This message may be carried in an F1AP message, for example, indicating that the target CU for DU migration is CU4. Optionally, this message may include an identifier for CU4, such as a gNB ID and / or IP address.

[0528] Optionally, the execution order of step 3 and step 4 is not limited in the embodiment of the present application. For example, step 3 may be executed first and then step 4, or step 4 may be executed first and then step 3.

[0529] Step 5. IAB-DU2 sends an F1 interface release request to CU3. Correspondingly, CU3 also receives the F1 interface release request from IAB-DU2.

[0530] After receiving the OAM-triggered indication, the IAB-node knows that it must comply with the OAM-triggered indication. Therefore, the IAB-DU2 sends an F1 interface release request to the CU3. CU3 needs to release the F1 interface before the IAB-DU2 can establish an F1 interface with the CU of another host node.

[0531] The F1 interface release request may be carried in an F1AP message, such as an F1 REMOVAL REQUEST message.

[0532] Step 6: CU3 sends a message indicating that the F1 interface release is complete to IAB-DU2. Correspondingly, IAB-DU2 also receives a message indicating that the F1 interface release is complete from CU3.

[0533] The information on the completion of releasing the F1 interface may be carried in an F1AP message, for example, an F1 REMOVAL RESPONSE message.

[0534] Step 7. IAB-DU2 sends an F1 interface establishment request to CU4. Correspondingly, CU4 also receives the F1 interface establishment request sent by IAB-DU2.

[0535] After the IAB-DU2 receives the F1 interface release completion message from the CU4, the IAB-DU2 may send an F1 interface establishment request message to the CU4.

[0536] Optionally, the message may be carried in an F1AP message, for example, an F1 SETUP REQUEST message.

[0537] Step 8. CU4 sends a message indicating that the establishment of the F1 interface is completed to IAB-DU2. Correspondingly, IAB-DU2 also receives a message indicating that the establishment of the F1 interface is completed from CU4.

[0538] Optionally, this information may be carried in an F1AP message, for example, an F1 SETUP RESPONSE message.

[0539] Step 9. IAB-node sends IAB node information to the OAM server.

[0540] For example, IAB-DU1 may send IAB node information to the OAM server, or IAB-DU2 may send IAB node information to the OAM server, and IAB-MT may send IAB node information to the OAM server. This embodiment of the present application does not limit this.

[0541] The IAB node message may be used to indicate the establishment result of the F1 interface, for example, indicating the establishment result of the F1 interface between the IAB-node and CU4. The result may be, for example, that the establishment of the F1 interface is complete.

[0542] Optionally, the IAB node information may carry an identifier of CU4, such as a gNB ID and / or an IP address.

[0543] Optionally, the IAB node information may also carry a triggering mode of the DU migration of the IAB-node, for example, the DU migration of the IAB-node is triggered by the CU.

[0544] Optionally, when at least one of the following conditions is met, the triggering mode of the DU migration of the IAB-node may be carried in the IAB node information.

[0545] (1) The triggering method of DU migration of IAB-node is CU triggering.

[0546] (2) The target CU of the IAB-node's DU migration is different from the target CU indicated by the OAM trigger. For example, the IAB-node establishes an F1 interface with CU4 according to the CU trigger. However, the target CU indicated by the OAM trigger is CU3, which is different from CU3.

[0547] The embodiments of the present application clarify that in the event of a trigger conflict during DU migration, the CU trigger is used as the trigger. This avoids the situation where the target CU of the DU migration is uncertain due to the trigger conflict, ensuring the smooth completion of the DU migration. In addition, sending information such as the results of the DU migration of the IAB-node to the OAM server enables the OAM server to promptly adjust the connection relationship of the IAB-node, facilitating the OAM server's subsequent management of the IAB-node and the next DU migration.

[0548] Please refer to Figure 15, which is a flow chart of another communication method provided in an embodiment of the present application. This communication method is applied to the field of communication technology, such as communication in an IAB network, and includes but is not limited to the following steps:

[0549] S1501: The first host node sends the eighth information to the relay node. Correspondingly, the relay node also receives the eighth information from the first host node.

[0550] S1502: The relay node sends the ninth information to the first host node. Correspondingly, the first host node also receives the ninth information from the relay node.

[0551] For the introduction of the relay node, the first host node, the second host node, the target host node and the OAM server, please refer to the relevant description in FIG9 or FIG12 , which will not be repeated here.

[0552] The eighth information is used to instruct the relay node to perform DU migration, and may include an identifier of the donor node after migration, such as a gNB ID and / or IP address.

[0553] The ninth information is used to instruct the relay node to refuse to perform the DU migration indicated by the CU trigger, and is used to let the first host node know that the relay node does not perform the DU migration according to its own instructions.

[0554] Optionally, the eighth information and the ninth information may both be carried in an F1AP message.

[0555] In the implementation manner of the present application, when the relay node receives the indication information triggered by CU, it directly gives the indication information of refusing to migrate, so that the relay node can only perform the DU migration operation based on the indication information triggered by OAM, thereby avoiding the conflict between DU triggering and OAM triggering.

[0556] In a possible implementation manner, the ninth information includes the reason why the relay node refuses to perform the DU migration.

[0557] In the implementation manner of the present application, the reason for refusing to perform DU migration may be, for example, that the relay node only accepts OAM triggering, or that the relay node does not support CU triggering, etc., and this is not limited in the implementation manner of the present application. By giving the reason for refusing to perform DU migration, the first relay node can also know the specific reason for refusing to perform DU migration this time and record it. On the one hand, it can avoid the first host node instructing the relay node to perform DU migration again. On the other hand, it can also allow the first host node to understand the situation of the relay node more clearly. The relay node refuses to perform DU migration because it does not support CU triggering or only supports OAM triggering. It is not that the relay node refuses to perform DU migration for some reason, such as an abnormality in the relay node itself, or the relay node is temporarily unable to perform DU migration, etc.

[0558] Optionally, the ninth information can be carried in the class 1 RESPONSE message or REJECT / FAILURE message of the F1AP message triggered by the CU, or in a separate class 2 message. Among them, the processes in F1AP are divided into class 1 and class 2. The class 1 process refers to the situation where feedback is required in the same process, such as: F1 SETUP REQEUST--F1 SETUP RESPONSE / F1 SETUP FAILURE, GNB-DU CONFIGURATION UPDATE--GNB-DU CONFIGURATION UPDATE ACK / GNB-DU CONFIGURATION UPDATE FAILURE, etc., while the class 2 process refers to the process in which there is only one message and no feedback of the F1AP message is required, such as: UL RRC MESSAGE TRANSFER, DL RRC MESSAGE TRANSFER, etc.

[0559] Please refer to Figure 16, which is a flow chart of a communication method provided in an embodiment of the present application. It is understood that the steps in the embodiment of the present application can be considered as reasonable variations or supplements to the embodiment in Figure 15 above; alternatively, it is understood that the communication method in the embodiment of the present application can also be considered as an embodiment that can be executed independently, and this application does not limit this. The communication method provided in the embodiment of the present application is applicable to the field of communication technology, such as communication in an IAB network.

[0560] It can be understood that the IAB (including IAB-DU and IAB-MT) involved in the communication method provided in the embodiment of the present application can refer to the relay node in the communication method shown in Figure 15 above, CU1 can refer to the first host node in the communication method shown in Figure 15 above, CU3 involved in the communication method provided in the embodiment of the present application can refer to the target host node in the communication method shown in Figure 15 above, CU4 involved in the communication method provided in the embodiment of the present application can refer to the second host node in the communication method shown in Figure 15 above, and the OAM involved in the communication method provided in the embodiment of the present application can refer to the OAM server in the communication method shown in Figure 15 above, which will not be repeated here.

[0561] The communication method may include one or more steps from step 1 to step 2. It should be understood that for the convenience of description, the order of steps 1 to 2 is described here, and it is not intended to limit the execution to the above order. The embodiment of the present application does not limit the order of execution, execution time, and number of executions of the above one or more steps. Steps 1 to 2 are specifically as follows:

[0562] Step 1. CU1 sends CU-triggered DU migration indication information to IAB-DU. Correspondingly, IAB-DU also receives CU-triggered DU migration indication information from CUI.

[0563] Specifically, CU1 sends CU-triggered DU migration indication information to the IAB-DU. This message may be carried in an F1AP message, such as the MIAB F1 SETUP TRIGGERING message.

[0564] Optionally, the indication information may carry that the target CU of DU migration is CU3 or CU4, etc., which is not limited in this embodiment of the present application.

[0565] Optionally, when the CU triggers the indication of DU migration to the target CU (e.g., CU4), the message may carry an identifier of the target CU, such as a gNB ID and / or IP address.

[0566] Step 2: The IAB-DU sends an indication message of rejecting CU triggering to CU1. Correspondingly, CU1 also receives an indication message of rejecting CU triggering from the IAB-DU.

[0567] The above-mentioned indication information of rejecting the CU trigger can be carried in the class 1 RESPONSE message or REJECT / FAILURE message of the F1AP message triggered by the CU, or can be carried in a separate class 2 message. The processes in F1AP are divided into class 1 and class 2. The class 1 process refers to the situation where feedback is required in the same process, such as: F1 SETUP REQEUST--F1 SETUP RESPONSE / F1 SETUP FAILURE, GNB-DU CONFIGURATION UPDATE--GNB-DU CONFIGURATION UPDATE ACK / GNB-DU CONFIGURATION UPDATE FAILURE, etc., while the class 2 process refers to the process with only one message in the process and does not require feedback of the F1AP message, such as: UL RRC MESSAGE TRANSFER, DL RRC MESSAGE TRANSFER, etc. For example, the message in step 2 can be carried in MIAB F1 SETUP OUTCOME NOTIFICATION.

[0568] Optionally, the above indication information may further carry a reason for rejecting DU migration, for example, the IAB-node only accepts DU migration triggered by OAM.

[0569] In the implementation manner of the present application, when the relay node receives the indication information triggered by CU, it directly gives the indication information of refusing to migrate, so that the relay node can only perform the DU migration operation based on the indication information triggered by OAM, thereby avoiding the conflict between DU triggering and OAM triggering.

[0570] The implementations shown in FIG. 15 and FIG. 16 above are used to illustrate the case where the IAB-node only accepts OAM-triggered DU migration. Next, FIG. 17 and FIG. 18 are used to illustrate the case where the IAB-node only accepts CU-triggered DU migration.

[0571] Please refer to Figure 17, which is a flow chart of another communication method provided in an embodiment of the present application. This communication method is applied to the field of communication technology, such as communication in an IAB network, and includes but is not limited to the following steps:

[0572] S1701: The OAM server sends the tenth information to the relay node.

[0573] S1702 (optional): The relay node ignores the tenth information.

[0574] S1703 (optional): The relay node sends the eleventh information to the OAM server.

[0575] For the introduction of the relay node, the first host node, the second host node, the target host node and the OAM server, please refer to the relevant description in FIG9 or FIG12 , which will not be repeated here.

[0576] The tenth information may be information preconfigured on the relay node by the network administrator, or information sent to the relay node by the network administrator via remote control. For information on preconfiguration and remote control, please refer to the previous description and will not be repeated here. The tenth information may include the identifier of the host node after the relay node is migrated, such as the gNB ID and / or IP address. The tenth information may also include information such as the time when the relay node performs DU migration.

[0577] Among them, DU ignores (ignores) the tenth information, which may be that the relay node refuses to receive the pre-configuration information of the network manager; it may also be that when the relay node is pre-configured by the network manager, the pre-configuration information is deleted; it may also be that when the pre-configuration information indicates that the relay node needs to migrate, the relay node ignores the instruction and does not migrate the DU according to the instruction of the pre-configuration information; it may also be that the DU migration triggered by the network manager through remote control is ignored.

[0578] In the IAB network, the DU migration of the IAB node supports two triggering modes: source CU triggering and OAM triggering. In the source CU triggering (hereinafter referred to as "CU triggering") mode, the source CU will send an indication message carrying the target CU to the DU in the IAB node, and the DU will complete the migration operation based on the indication message. The source CU is the CU connected to the DU before the migration, and the target CU is the CU connected to the DU after the migration. In the OAM triggering mode, the OAM server can be directly pre-configured in the IAB node or remotely trigger the IAB node to perform DU migration. Obviously, both CU triggering and OAM triggering can instruct the relay node to perform DU migration. If the CU triggering and OAM triggering occur at the same time, the relay node may not be able to complete the DU migration normally, or may migrate to the wrong host node. In addition, in the case of a conflict between the two triggers, at least one trigger indication (such as CU triggering) is not completed, which may also cause abnormalities such as control failure and information transmission errors.

[0579] In the implementation manner of the present application, when the OAM-triggered indication information instructs the relay node to perform DU migration, the relay node ignores the OAM-triggered indication information, so that the relay node only executes the CU-triggered indication information, thereby avoiding the conflict between CU triggering and OAM triggering, and then ensuring that the relay node completes DU migration normally.

[0580] In a possible implementation manner, the relay node sends eleventh information to the network manager, where the eleventh information is used to indicate rejection of DU migration triggered by the network manager or to indicate that the network manager does not trigger DU migration of the relay node.

[0581] This allows the OAM server to know that the DU migration it instructed was not executed by the relay node, thereby preventing the OAM server from adjusting the connection relationship of the relay node based on the instruction information triggered by OAM. Informing the OAM server not to trigger DU migration can also save some control resources and avoid conflicts between OAM triggering and CU triggering.

[0582] Optionally, the relay node sends instruction information to the OAM server, where the instruction information is used to instruct the relay node to establish an F1 interface with the target host node.

[0583] When the relay node ignores the indication information triggered by OAM, if the relay node performs DU migration according to the indication information triggered by CU and informs the OAM server of the relay node DU migration, the OAM server can update the connection relationship of the relay node in time, thereby facilitating the OAM server to perform subsequent management of the relay node.

[0584] Please refer to Figure 18, which is a flowchart illustrating a communication method provided in an embodiment of the present application. It is understood that the steps in the embodiment of the present application can be considered as reasonable variations or supplements to the embodiment in Figure 17 above; alternatively, it is understood that the communication method in the embodiment of the present application can also be considered as an embodiment that can be executed independently, and this application does not limit this. The communication method provided in the embodiment of the present application is applicable to the field of communication technology, such as communication in an IAB network.

[0585] It can be understood that the IAB (including IAB-DU and IAB-MT) involved in the communication method provided in the embodiment of the present application can refer to the relay node in the communication method shown in Figure 17 above, CU1 can refer to the first host node in the communication method shown in Figure 17 above, CU3 involved in the communication method provided in the embodiment of the present application can refer to the target host node in the communication method shown in Figure 17 above, CU4 involved in the communication method provided in the embodiment of the present application can refer to the second host node in the communication method shown in Figure 17 above, and the OAM involved in the communication method provided in the embodiment of the present application can refer to the OAM server in the communication method shown in Figure 17 above, which will not be repeated here.

[0586] The communication method may include one or more steps from step 1 to step 3. It should be understood that for the convenience of description, the order of steps 1 to 3 is described here, and it is not intended to limit the execution to the above order. The embodiment of the present application does not limit the order of execution, execution time, and number of executions of the above one or more steps. Steps 1 to 3 are specifically as follows:

[0587] Before introducing the method shown in Figure 18, the possible prerequisites for executing the method shown in Figure 18 are described. For example, before executing the method shown in Figure 18, the IAB-node needs to receive an OAM trigger, or the OAM server needs to send an OAM trigger indication to the IAB-node.

[0588] Step 1. The IAB-node ignores the OAM trigger (Option 1).

[0589] After receiving an OAM trigger, the IAB-node can choose to ignore the OAM trigger indication. Specifically, it can always ignore the OAM configuration. For example, the IAB-node can directly ignore the message sent by the OAM server when it receives it. Another example is ignoring the DU migration policy pre-configured by the OAM server.

[0590] Optionally, ignoring the OAM-triggered indication information may include, for example, not performing DU migration according to the OAM-triggered indication information, or not replying to the OAM server according to the OAM-triggered indication information.

[0591] Step 2. The IAB-node sends the IAB node information (Option 2) to the OAM server.

[0592] Among them, the IAB node message can be used to instruct the IAB-node to refuse to execute the OAM trigger instruction information, and can also be used to instruct the OAM server not to trigger the DUmigration of the IAB-node, including: it can be no longer triggering the DUmigration of the IAB-node within a period of time, or it can be no longer triggering the DUmigration of the IAB-node permanently.

[0593] It should be noted that the order of executing the above steps 1 and 2 is not limited in the embodiment of the present application. For example, step 1 can be executed first and then step 2, or step 2 can be executed first and then step 1. In addition, the above steps 1 and 2 can also be regarded as two parallel methods, that is, only one of the steps can be executed, for example, only step 1 or only step 2.

[0594] The embodiments of the present application ignore OAM triggers or send IAB node messages to the OAM server, instructing the OAM server not to trigger DU migration of the IAB-node. This allows the relay node to perform DU migration operations based only on the instructions triggered by the CU, thereby avoiding conflicts between DU triggers and OAM triggers. Furthermore, the OAM server is informed that the DU migration it instructed was not executed by the relay node, thereby preventing the OAM server from timely adjusting the connection relationship of the relay node based on the instructions triggered by the OAM, thereby facilitating subsequent OAM management.

[0595] Please refer to Figure 19, which is a flow chart of another communication method provided in an embodiment of the present application. This communication method is applied to the field of communication technology, such as communication in an IAB network, and includes but is not limited to the following steps:

[0596] S1901: The relay node sends twelfth information to the first host node. Correspondingly, the relay node receives the twelfth information from the first host node.

[0597] S1902: The first host node sends the thirteenth information to the relay node. Correspondingly, the first host node receives the thirteenth information from the relay node.

[0598] The relay node, the first host node, the second host node, the target host node and the OAM server shown in the method shown in FIG19 can refer to the relevant description of FIG9 or FIG12 and will not be repeated here.

[0599] Specifically, the above S1901 and / or S1902 are executed when the following triggering conditions are met:

[0600] When the third trigger condition is met, the relay node generates the twelfth information. In this case, the third trigger condition can be understood as the condition that triggers the relay node to generate the twelfth information. Optionally, when the above-mentioned third trigger condition is met, the relay node will also send the twelfth information. In this case, the third trigger condition can be understood as the condition that triggers the relay node to generate and send the twelfth information. Optionally, when the third trigger condition is met, the first host node generates the thirteenth information. In this case, the third trigger condition can be understood as the condition that triggers the first host node to generate the thirteenth information. Optionally, when the above-mentioned third trigger condition is met, the first host node will also send the thirteenth information. In this case, the third trigger condition can be understood as the condition that triggers the first host node to generate and send the thirteenth information.

[0601] The third trigger condition includes, but is not limited to, one or more of the following:

[0602] (1) The relay node completes network access.

[0603] (2) The relay node completes the DU migration.

[0604] It should be understood that the several trigger conditions listed above are only possible exemplary descriptions for triggering the execution of S1901 and / or S1902, and should not be used to limit the embodiments of the present application. Embodiments obtained based on the supplement or reasonable deformation of the above trigger conditions all fall within the scope of protection of the embodiments of the present application.

[0605] Among them, the above-mentioned twelfth information and thirteenth information are both used to indicate the triggering method of DU migration supported by the relay node, for example, only supporting CU triggering, only supporting OAM triggering, or supporting both CU triggering and OAM triggering. In the case where the relay node supports both CU triggering and OAM triggering, the priority of CU triggering and OAM triggering can also be set, for example, based on OAM triggering (equivalent to the method shown in Figure 9), or based on CU triggering (equivalent to the method shown in Figure 12).

[0606] Optionally, the twelfth information may be carried in a class 1 process of F1AP, such as an F1 SETUP REQUEST message or a GNB-DU CONFIGURATION UPDATE message. It may also be carried in a class 2 process of F1AP. The specific message used is not limited in this embodiment of the present application.

[0607] Optionally, the thirteenth information may be carried in a class 1 process of F1AP, such as an F1 SETUP RESPONSE message or a GNB-CU CONFIGURATION UPDATE message. It may also be carried in a class 2 process of F1AP. The specific message used is not limited in this embodiment of the present application.

[0608] Optionally, the above S1901 and / or S1902 are executed when at least one of the following conditions is met:

[0609] (1) The above relay node completes network access.

[0610] (2) The above relay node completes DU migration.

[0611] The completion of the relay node joining the network generally means that the parent node of the relay node is already in the network and the relay node and the host node in the network have completed the establishment of the F1 interface. Alternatively, the relay node can provide services for the UE or the next-hop MT.

[0612] The relay node completes the DU migration, which may be that the relay node establishes a new F1 interface with a new host node, and the UE of the relay node has switched to the new DU and released the old F1 interface.

[0613] In a possible implementation manner, the triggering modes supported by the DU migration include CU triggering and / or network management triggering.

[0614] When the triggering method includes only CU triggering or only network management triggering, the relay node can avoid trigger conflicts and ensure that the relay node completes DU migration normally. If the triggering method includes both CU triggering and OAM triggering, the methods provided in Figures 9-14 can be used to handle possible conflicts and ensure that the relay node completes DU migration normally.

[0615] Please refer to Figure 20, which is a flow chart of a communication method provided in an embodiment of the present application. It is understood that the steps in the embodiment of the present application can be considered as reasonable variations or supplements to the embodiment in Figure 19 above; alternatively, it is understood that the communication method in the embodiment of the present application can also be considered as an embodiment that can be executed independently, and this application does not limit this. The communication method provided in the embodiment of the present application is applied to the field of communication technology, such as communication in an IAB network.

[0616] It can be understood that the IAB (including IAB-DU and IAB-MT) involved in the communication method provided in the embodiment of the present application can refer to the relay node in the communication method shown in Figure 19 above, CU1 can refer to the first host node in the communication method shown in Figure 19 above, CU3 involved in the communication method provided in the embodiment of the present application can refer to the target host node in the communication method shown in Figure 19 above, CU4 involved in the communication method provided in the embodiment of the present application can refer to the second host node in the communication method shown in Figure 19 above, and the OAM involved in the communication method provided in the embodiment of the present application can refer to the OAM server in the communication method shown in Figure 19 above, which will not be repeated here.

[0617] The communication method may include one or more steps from step 1 to step 2. It should be understood that for the convenience of description, the order of steps 1 to 2 is described here, and it is not intended to limit the execution to the above order. The embodiment of the present application does not limit the order of execution, execution time, and number of executions of the above one or more steps. Steps 1 to 2 are specifically as follows:

[0618] Step 1. CU1 sends F1AP information to IAB-DU. Correspondingly, IAB-DU also receives F1AP information (Option 1) from CU1.

[0619] The F1AP information is used to indicate the triggering methods of DU migration that the IAB-node can receive. For example, the IAB-node can be indicated to support CU triggering, OAM triggering, or both CU and OAM triggering. In addition, when the IAB-node is indicated to support both CU triggering and OAM triggering, the priority of CU triggering and OAM triggering can also be indicated.

[0620] Optionally, the F1AP message may be carried in a class 1 message, such as an F1 SETUPRESPONSE message or a GNB-CU CONFIGURATION UPDATE message.

[0621] Step 2. The IAB-DU sends F1AP information to CU1. Correspondingly, CU1 receives information from the IAB-DU (Option 2).

[0622] The F1AP information is used to indicate the triggering methods of DU migration that the IAB-node can receive. For example, the IAB-node can be indicated to support CU triggering, OAM triggering, or both CU and OAM triggering. In addition, when the IAB-node is indicated to support both CU triggering and OAM triggering, the priority of CU triggering and OAM triggering can also be indicated.

[0623] Optionally, the F1AP message may be carried in a class 1 message, such as an F1 SETUPREQUEST message or a GNB-DU CONFIGURATION UPDATE message.

[0624] It should be noted that the order of executing the above steps 1 and 2 is not limited in the embodiment of the present application. For example, step 1 can be executed first and then step 2, or step 2 can be executed first and then step 1. In addition, the above steps 1 and 2 can also be regarded as two parallel methods, that is, only one of the steps can be executed, for example, only step 1 or only step 2.

[0625] In embodiments of the present application, by setting the triggering method for DU migration supported by the IAB node, CU triggering conflicts can be reduced, thereby ensuring that the IAB node successfully completes DU migration. If the IAB node supports both triggering methods, the methods shown in Figures 9 to 14 can also be executed to determine the target CU for DU migration when a conflict occurs, thereby ensuring that the IAB node successfully completes DU migration.

[0626] Please refer to Figure 21, which is a flow chart of another communication method provided in an embodiment of the present application. This communication method is applied to the field of communication technology, such as communication in an IAB network, and includes but is not limited to the following steps:

[0627] S2101: The first host node generates fourteenth information.

[0628] S2102: The first host node sends fourteenth information to the second host node.

[0629] For an introduction to the relay node, the first host node, the second host node, the target host node and the OAM server shown in the method shown in FIG21 , please refer to the relevant descriptions in FIG9 or FIG12 , which will not be repeated here.

[0630] Specifically, the above S2101 and / or S2102 are executed when the following triggering conditions are met:

[0631] When the fourth trigger condition is met, the first host node generates the fourteenth information. In this case, the fourth trigger condition can be understood as a condition that triggers the first host node to generate the fourteenth information. Optionally, when the fourth trigger condition is met, the first host node also sends the fourteenth information. In this case, the fourth trigger condition can be understood as a condition that triggers the relay node to generate and send the fourteenth information.

[0632] The fourth trigger condition includes, but is not limited to, one or more of the following:

[0633] (1) The first host node receives indication information from the relay node, where the indication information is used to indicate that the relay node has completed establishing the F1 interface with the target host node.

[0634] (2) There is interaction between the first host node and the second host node.

[0635] (3) There is a pre-configuration in the second host node, and the pre-configuration is used to instruct the second host node to establish an F1 interface with the relay node.

[0636] Optionally, conditions 2 and 3 occur during the DU migration process of the IAB-node.

[0637] It should be understood that the several trigger conditions listed above are merely illustrative examples of possible triggering execution of S2101 and / or S2102, and should not be used to limit the embodiments of the present application. Embodiments obtained based on the supplementation or reasonable deformation of the above trigger conditions all fall within the scope of protection of the embodiments of the present application.

[0638] The fourteenth information is used to instruct the cancellation of the F1 interface between the second host node and the relay node, thereby avoiding abnormal situations caused by the second host node attempting to establish the F1 interface with the relay node again. In addition, the second host node can use its effective resources to establish the F1 interface with other relay nodes.

[0639] Optionally, the fourteenth information may carry an identifier of the target host node, such as a gNB ID and / or an IP address.

[0640] In the embodiment of the present application, when the fourth trigger condition is met, the first host node sends a fourteenth message to the second host node. The fourteenth message is used to instruct the second host node to cancel the establishment of the F1 interface between the second host node and the relay node, thereby avoiding an abnormal situation caused by the second host node attempting to establish the F1 interface with the relay node again. In addition, the second host node can use its available resources to establish the F1 interface with other relay nodes.

[0641] For the specific implementation of the method shown in Figure 21, please refer to the relevant description of step 6 in Figure 10, which will not be repeated here.

[0642] The above describes in detail the methods of the embodiments of the present application. The following provides an apparatus for implementing any method in the embodiments of the present application. For example, an apparatus is provided that includes units (or means) for implementing each step performed by the device in any of the above methods.

[0643] As shown in Figure 22, the communication device 220 may include a processing unit 2201 and a communication unit 2202. The processing unit 2201 and the communication unit 2202 may be software, hardware, or a combination of software and hardware.

[0644] The processing unit 2201 can implement a sending function and / or a receiving function, and can also be described as a transceiver unit. The processing unit 2201 can also be a unit that integrates an acquisition unit and a transmission unit, wherein the acquisition unit is used to implement the receiving function and the transmission unit is used to implement the transmission function. Optionally, the processing unit 2201 can be used to receive information sent by other devices, and can also be used to send information to other devices.

[0645] In one possible design, the communication device 220 may correspond to the relay node in the method embodiment shown in Figures 9 to 21 above, for example, the communication device 220 may be a relay node or a chip in a relay node. The communication device 220 may include a unit for executing the operations performed by the first host node in the method embodiment shown in Figures 9 to 21 above, and each unit in the communication device 220 is respectively for implementing the operations performed by the first host node in the method embodiment shown in Figures 9 to 21 above. The description of each unit is as follows:

[0646] The processing unit 2201 is configured to generate first information when a first trigger condition is met; the first information includes a result of the relay node establishing the first F1 interface with the target host node and an identifier of the target host node; or, the first information includes a result of the relay node establishing the first F1 interface with the target host node, an identifier of the target host node, and a triggering method for DU migration of the relay node;

[0647] The first trigger condition includes at least one of the following:

[0648] Based on the second information provided by the network management, the second information is used to instruct the relay node to establish the first F1 interface with the target host node; or, the relay node receives third information from the first host node, and the third information is used to instruct the relay node to establish a second F1 interface with a second host node, and the second host node is different from the target host node.

[0649] The communication unit 2202 is configured to send the first information.

[0650] or,

[0651] The processing unit 2201 is configured to generate fourth information; the fourth information includes a result of the relay node establishing a third F1 interface with the target host node.

[0652] The communication unit 2202 is configured to send the fourth information to the network management.

[0653] or,

[0654] The processing unit 2201 is configured to generate the fourth information when the second trigger condition is met;

[0655] The second trigger condition includes at least one of the following:

[0656] The relay node receives fifth information from the first host node, and the fifth information is used to instruct the relay node to establish the third F1 interface with the target host node; or, based on the sixth information provided by the network manager, the sixth information is used to instruct the relay node to establish a fourth F1 interface with the second host node, and the second host node is different from the target host node; or, the relay node receives seventh information from the target host node, and the seventh information is used to indicate that the establishment of the third F1 interface is completed.

[0657] The communication unit 2202 is configured to send the fourth information to the network management.

[0658] or,

[0659] The processing unit 2201 is configured to generate ninth information, where the ninth information is used to instruct the relay node to refuse to perform the DU migration.

[0660] The communication unit 2202 is configured to send ninth information to the first host node. In addition, the communication unit 2202 is further configured to receive eighth information from the first host node, where the eighth information is used to instruct the relay node to perform DU migration.

[0661] or,

[0662] The processing unit 2201 is configured to process the tenth information, for example, ignore the tenth information.

[0663] The communication unit 2202 is configured to receive tenth information from the network management, where the tenth information is used to instruct the relay node to perform DU migration.

[0664] or,

[0665] The processing unit 2201 is configured to generate twelve pieces of information;

[0666] The twelfth information is used to indicate the triggering method of DU migration supported by the relay node; and / or, processing the thirteenth information from the first host node, the thirteenth information is used to indicate the triggering method of DU migration supported by the relay node; the triggering method includes CU triggering and / or network management triggering.

[0667] The communication unit 2202 is configured to send the twelfth information and / or receive the thirteenth information.

[0668] or,

[0669] The processing unit 2201 is configured to generate fourteenth information when the fourth trigger condition is met; the fourteenth information is used to indicate cancellation of establishing the F1 interface between the second host node and the relay node;

[0670] The fourth trigger condition includes:

[0671] Receive fifteenth information from the relay node, where the fifteenth information includes that the relay node completes establishing an F1 interface with a target host node, and the target host node is different from the second host node.

[0672] The communication unit 2202 is configured to send fourteenth information when the fourth trigger condition is met.

[0673] The methods executed by the above-mentioned processing unit 2201 and the communication unit 2202 can refer to the methods corresponding to the above-mentioned Figures 9 to 21, and will not be repeated here.

[0674] Regarding the technical effects brought about by any of the above designs and any possible implementation methods, please refer to the introduction of the technical effects of the corresponding methods in Figures 9 to 21 above, and no further details will be given here.

[0675] Optionally, in the communication device described in any of the foregoing designs and any of the possible implementations:

[0676] In one implementation, the communication apparatus is a communication device. When the communication apparatus is a communication device, the communication unit may be a transceiver or an input / output interface; and the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0677] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0678] According to an embodiment of the present application, each unit in the device shown in Figure 22 can be separately or all merged into one or several other units to constitute, or a certain (some) unit therein can also be split into multiple smaller units to constitute, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the function of a unit can also be realized by multiple units, or the function of multiple units can be realized by one unit. In other embodiments of the present application, other units can also be included based on electronic equipment. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by collaboration of multiple units.

[0679] It should be noted that the implementation of each unit may also refer to the corresponding description of the method embodiments shown in Figures 9 to 21 above.

[0680] In the communication device 220 described in FIG. 22 , the occurrence of trigger conflicts can be avoided, or when a trigger conflict exists, the target CU of DU migration can be determined, thereby ensuring smooth completion of DU migration.

[0681] In another possible design, the communication device 220 may correspond to the first host node in the method embodiment shown in Figures 9 to 21 above, such as the communication device 220 may be the first host node or a chip in the first host node. The communication device 220 may include a unit for executing the operations performed by the first host node in the method embodiments shown in Figures 9 to 16 and 19 to 21 above, and each unit in the communication device 220 is respectively for implementing the operations performed by the first host node in the method embodiments shown in Figures 9 to 16 and 19 to 21 above. The description of each unit is as follows:

[0682] The communication unit 2202 is configured to receive first information from the relay node; the first information includes a result of the relay node establishing the first F1 interface with the target host node and an identifier of the target host node; or the first information includes a result of the relay node establishing the first F1 interface with the target host node, an identifier of the target host node, and a triggering method for DU migration of the relay node;

[0683] The processing unit 2201 is configured to process the first information.

[0684] or,

[0685] The communication unit 2202 is configured to receive fourth information from the relay node, where the fourth information includes a result of the relay node establishing a third F1 interface with the target host node.

[0686] The processing unit 2201 is configured to process the fourth information.

[0687] or,

[0688] The processing unit 2201 is configured to generate eighth information, where the eighth information is used to instruct the relay node to perform DU migration.

[0689] The communication unit 2202 is configured to send the eighth information to the relay node.

[0690] or,

[0691] Processing unit 2201 is used to generate thirteen information; the thirteenth information is used to indicate the triggering method of DU migration supported by the relay node; and / or, process twelfth information from the relay node, the twelfth information is used to indicate the triggering method of DU migration supported by the relay node; the triggering method includes CU triggering and / or network management triggering.

[0692] The communication unit 2202 is configured to send the thirteenth information and / or receive the twelfth information.

[0693] or,

[0694] The processing unit 2201 is configured to generate fourteenth information when the fourth trigger condition is met; the fourteenth information is used to indicate cancellation of establishing the F1 interface between the second host node and the relay node;

[0695] The fourth trigger condition includes:

[0696] Receive fifteenth information from the relay node, where the fifteenth information includes that the relay node completes establishing an F1 interface with a target host node, and the target host node is different from the second host node.

[0697] The communication unit 2202 is configured to send fourteenth information when the fourth trigger condition is met;

[0698] The methods executed by the above-mentioned processing unit 2201 and the communication unit 2202 can refer to the methods corresponding to the above-mentioned Figures 9-16 and Figures 19-21, and will not be repeated here.

[0699] Regarding the technical effects brought about by any of the above designs and any possible implementation methods, please refer to the introduction of the technical effects of the corresponding methods in Figures 9-16 and Figures 19-21 above, and no further details will be given here.

[0700] Optionally, in the communication device described in any of the foregoing designs and any of the possible implementations:

[0701] In one implementation, the communication apparatus is a communication device. When the communication apparatus is a communication device, the communication unit may be a transceiver or an input / output interface; and the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0702] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0703] According to an embodiment of the present application, each unit in the device shown in Figure 22 can be separately or all merged into one or several other units to constitute, or a certain (some) unit therein can also be split into multiple smaller units to constitute, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the function of a unit can also be realized by multiple units, or the function of multiple units can be realized by one unit. In other embodiments of the present application, other units can also be included based on electronic equipment. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by collaboration of multiple units.

[0704] It should be noted that the implementation of each unit may also refer to the corresponding description of the method embodiments shown in Figures 9 to 16 and Figures 19 to 21 above.

[0705] In the communication device 220 described in FIG. 22 , the occurrence of trigger conflicts can be avoided, or when a trigger conflict exists, the target CU of DU migration can be determined, thereby ensuring smooth completion of DU migration.

[0706] In another possible design, the communication device 220 may correspond to the OAM server in the method embodiments shown in Figures 12, 13, 14, 17, and 18 above, for example, the communication device 220 may be an OAM server or a chip in the OAM server. The communication device 220 may include a unit for executing the operations performed by the first host node in the method embodiments shown in Figures 12, 13, 14, 17, and 18 above, and each unit in the communication device 220 is respectively for implementing the operations performed by the OAM server in the method embodiments shown in Figures 12, 13, 14, 17, and 18 above. The description of each unit is as follows:

[0707] The communication unit 2202 is configured to receive fourth information from the relay node, where the fourth information includes a result of the relay node establishing a third F1 interface with the target host node.

[0708] The processing unit 2201 is configured to process the fourth information.

[0709] or,

[0710] The processing unit 2201 is configured to generate tenth information, where the tenth information is used to instruct the relay node to perform DU migration;

[0711] The communication unit 2202 is configured to send tenth information to the relay node.

[0712] The methods executed by the above-mentioned processing unit 2201 and the communication unit 2202 can refer to the methods corresponding to the above-mentioned Figures 12, 13, 14, 17 and 18, and will not be repeated here.

[0713] Regarding the technical effects brought about by any of the above designs and any possible implementation methods, please refer to the introduction of the technical effects of the corresponding methods in Figures 12, 13, 14, 17 and 18 above, which will not be repeated here.

[0714] Optionally, in the communication device described in any of the foregoing designs and any of the possible implementations:

[0715] In one implementation, the communication apparatus is a communication device. When the communication apparatus is a communication device, the communication unit may be a transceiver or an input / output interface; and the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0716] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0717] According to an embodiment of the present application, each unit in the device shown in Figure 22 can be separately or all merged into one or several other units to constitute, or a certain (some) unit therein can also be split into multiple smaller units to constitute, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the function of a unit can also be realized by multiple units, or the function of multiple units can be realized by one unit. In other embodiments of the present application, other units can also be included based on electronic equipment. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by collaboration of multiple units.

[0718] It should be noted that the implementation of each unit may also refer to the corresponding description of the method embodiments shown in the above-mentioned Figures 12, 13, 14, 17 and 18.

[0719] In the communication device 220 described in FIG. 22 , the network manager can obtain the connection relationship of the relay node in a timely manner, which facilitates the network manager's management of the relay node and the next DU migration, thereby ensuring the smooth completion of DU migration.

[0720] In another possible design, the communication device 220 may correspond to the second host node in the method embodiment shown in FIG. 21 above, for example, the communication device 220 may be the second host node, or a chip in the second host node. The communication device 220 may include a unit for executing the operations performed by the second host node in the method embodiment shown in FIG. 21 above, and each unit in the communication device 220 is respectively for implementing the operations performed by the second host node in the method embodiment shown in FIG. 21 above. The description of each unit is as follows:

[0721] The communication unit 2202 is configured to receive fourteenth information from the first host node, where the fourteenth information is used to instruct to cancel establishing the F1 interface between the second host node and the relay node.

[0722] The processing unit 2201 is configured to process the fourteenth information.

[0723] The method executed by the above-mentioned processing unit 2201 and the communication unit 2202 can refer to the method corresponding to the above-mentioned Figure 21, which will not be repeated here.

[0724] Regarding the technical effects brought about by any of the above designs and any possible implementation methods, please refer to the introduction of the technical effects of the corresponding method in Figure 21 above, and no further details will be given here.

[0725] Optionally, in the communication device described in any of the foregoing designs and any of the possible implementations:

[0726] In one implementation, the communication apparatus is a communication device. When the communication apparatus is a communication device, the communication unit may be a transceiver or an input / output interface; and the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0727] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication unit may be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, or related circuit on the chip (system) or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0728] According to an embodiment of the present application, each unit in the device shown in Figure 22 can be separately or all merged into one or several other units to constitute, or a certain (some) unit therein can also be split into multiple smaller units to constitute, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the function of a unit can also be realized by multiple units, or the function of multiple units can be realized by one unit. In other embodiments of the present application, other units can also be included based on electronic equipment. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by collaboration of multiple units.

[0729] It should be noted that the implementation of each unit can also refer to the corresponding description of the method embodiment shown in Figure 21 above.

[0730] In the communication device 220 described in Figure 22, the abnormal situation caused by the second host node trying to establish the F1 interface with the relay node again can be avoided. In addition, the second host node can use effective resources to establish the F1 interface with other relay nodes.

[0731] Please refer to Figure 23, which is a structural diagram of a communication device provided in an embodiment of the present application.

[0732] It should be understood that the communication device 230 shown in Figure 23 is only an example. The communication device of the embodiment of the present application may also include other components, or include components with similar functions to the various components in Figure 23, or not include all components in Figure 23.

[0733] The communication device 230 includes a communication interface 2301 and at least one processor 2302 .

[0734] The communication device 230 may correspond to any node or device among a relay node, a first host node, a second host node, a target host node, and an OAM server. The communication interface 2301 is used to transmit and receive signals, and the at least one processor 2302 executes program instructions, so that the communication device 230 implements the corresponding process of the method executed by the corresponding device in the above-mentioned method embodiment.

[0735] In one possible design, the communication device 230 may correspond to the relay node in the method embodiment shown in Figures 9 to 21 above, for example, the communication device 230 may be a relay node or a chip in a relay node. The communication device 230 may include a unit for executing the operations performed by the first host node in the method embodiment shown in Figures 9 to 21 above, and each unit in the communication device 230 is respectively for implementing the operations performed by the first host node in the method embodiment shown in Figures 9 to 21 above. The description of each unit is as follows:

[0736] Processor 2302 is configured to generate first information when a first trigger condition is met; the first information includes a result of the relay node establishing the first F1 interface with the target host node and an identifier of the target host node; or, the first information includes a result of the relay node establishing the first F1 interface with the target host node, an identifier of the target host node, and a triggering method for DU migration of the relay node;

[0737] The first trigger condition includes at least one of the following:

[0738] Based on the second information provided by the network management, the second information is used to instruct the relay node to establish the first F1 interface with the target host node; or, the relay node receives third information from the first host node, and the third information is used to instruct the relay node to establish a second F1 interface with a second host node, and the second host node is different from the target host node.

[0739] The communication interface 2301 is used to send the first information.

[0740] or,

[0741] Processor 2302 is configured to generate fourth information; the fourth information includes a result of the relay node establishing a third F1 interface with the target host node.

[0742] The communication interface 2301 is used to send the fourth information to the network management.

[0743] or,

[0744] Processor 2302, configured to generate the fourth information when a second trigger condition is met;

[0745] The second trigger condition includes at least one of the following:

[0746] The relay node receives fifth information from the first host node, and the fifth information is used to instruct the relay node to establish the third F1 interface with the target host node; or, based on the sixth information provided by the network manager, the sixth information is used to instruct the relay node to establish a fourth F1 interface with the second host node, and the second host node is different from the target host node; or, the relay node receives seventh information from the target host node, and the seventh information is used to indicate that the establishment of the third F1 interface is completed.

[0747] The communication interface 2301 is used to send the fourth information to the network management.

[0748] or,

[0749] The processor 2302 is configured to generate ninth information, where the ninth information is used to instruct the relay node to refuse to perform the DU migration.

[0750] The communication interface 2301 is configured to send ninth information to the first host node. In addition, the communication interface 2301 is further configured to receive eighth information from the first host node, where the eighth information is configured to instruct the relay node to perform DU migration.

[0751] or,

[0752] The processor 2302 is configured to process the tenth information, for example, ignore the tenth information.

[0753] The communication interface 2301 is configured to receive tenth information from the network management, where the tenth information is configured to instruct the relay node to perform DU migration.

[0754] or,

[0755] Processor 2302 is used to generate twelve information; the twelfth information is used to indicate the triggering method of DU migration supported by the relay node; and / or, to process thirteenth information from the first host node, the thirteenth information is used to indicate the triggering method of DU migration supported by the relay node; the triggering method includes CU triggering and / or network management triggering.

[0756] The communication interface 2301 is configured to send the twelfth information and / or receive the thirteenth information when a third trigger condition is met.

[0757] or,

[0758] Processor 2302 is configured to generate fourteenth information when the fourth trigger condition is met; the fourteenth information is used to indicate cancellation of establishing the F1 interface between the second host node and the relay node;

[0759] The fourth trigger condition includes:

[0760] Receive fifteenth information from the relay node, where the fifteenth information includes that the relay node completes establishing an F1 interface with a target host node, and the target host node is different from the second host node.

[0761] The communication interface 2301 is configured to send fourteenth information when the fourth trigger condition is met.

[0762] The methods executed by the processor 2302 and the communication interface 2301 can refer to the methods corresponding to Figures 9 to 21 above, and will not be repeated here.

[0763] Regarding the technical effects brought about by any of the above designs and any possible implementation methods, please refer to the introduction of the technical effects of the corresponding methods in Figures 9 to 21 above, and no further details will be given here.

[0764] Optionally, in the communication device described in any of the foregoing designs and any of the possible implementations:

[0765] In one implementation, the communication apparatus is a communication device. When the communication apparatus is a communication device, the communication interface may be a transceiver or an input / output interface; and the processor may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0766] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication interface can be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, or related circuit on the chip (system) or circuit; the processor can be at least one processor, processing circuit, or logic circuit.

[0767] According to an embodiment of the present application, each unit in the device shown in Figure 23 can be separately or all merged into one or several other units to constitute, or a certain (some) unit therein can also be split into multiple smaller units to constitute, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the function of a unit can also be realized by multiple units, or the function of multiple units can be realized by one unit. In other embodiments of the present application, other units can also be included based on electronic equipment. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by collaboration of multiple units.

[0768] It should be noted that the implementation of each unit may also refer to the corresponding description of the method embodiments shown in Figures 9 to 21 above.

[0769] In the communication device 230 described in FIG. 23 , the occurrence of trigger conflicts can be avoided, or when a trigger conflict exists, the target CU of DU migration can be determined, thereby ensuring smooth completion of DU migration.

[0770] In another possible design, the communication device 230 may correspond to the first host node in the method embodiment shown in Figures 9 to 21 above, such as the communication device 230 may be the first host node or a chip in the first host node. The communication device 230 may include a unit for executing the operations performed by the first host node in the method embodiments shown in Figures 9 to 16 and 19 to 21 above, and each unit in the communication device 230 is respectively for implementing the operations performed by the first host node in the method embodiments shown in Figures 9 to 16 and 19 to 21 above. The description of each unit is as follows:

[0771] Communication interface 2301, configured to receive first information from a relay node; the first information includes a result of the relay node establishing the first F1 interface with the target host node and an identifier of the target host node; or, the first information includes a result of the relay node establishing the first F1 interface with the target host node, an identifier of the target host node, and a triggering method for DU migration of the relay node;

[0772] Processor 2302 is configured to process the first information.

[0773] or,

[0774] The communication interface 2301 is configured to receive fourth information from the relay node, where the fourth information includes a result of the relay node establishing a third F1 interface with the target host node.

[0775] Processor 2302 is configured to process the fourth information.

[0776] or,

[0777] The processor 2302 is configured to generate eighth information, where the eighth information is used to instruct the relay node to perform DU migration.

[0778] The communication interface 2301 is used to send the eighth information to the relay node.

[0779] or,

[0780] Processor 2302 is used to generate thirteen information; the thirteenth information is used to indicate the triggering method of DU migration supported by the relay node; and / or, process twelfth information from the relay node, the twelfth information is used to indicate the triggering method of DU migration supported by the relay node; the triggering method includes CU triggering and / or network management triggering.

[0781] The communication interface 2301 is configured to send the thirteenth information and / or receive the twelfth information.

[0782] or,

[0783] Processor 2302 is configured to generate fourteenth information when the fourth trigger condition is met; the fourteenth information is used to indicate cancellation of establishing the F1 interface between the second host node and the relay node;

[0784] The fourth trigger condition includes:

[0785] Receive fifteenth information from the relay node, where the fifteenth information includes that the relay node completes establishing an F1 interface with a target host node, and the target host node is different from the second host node.

[0786] Communication interface 2301, configured to send fourteenth information when a fourth trigger condition is met;

[0787] The methods executed by the processor 2302 and the communication interface 2301 can refer to the methods corresponding to Figures 9-16 and 19-21 above, and will not be repeated here.

[0788] Regarding the technical effects brought about by any of the above designs and any possible implementation methods, please refer to the introduction of the technical effects of the corresponding methods in Figures 9-16 and Figures 19-21 above, and no further details will be given here.

[0789] Optionally, in the communication device described in any of the foregoing designs and any of the possible implementations:

[0790] In one implementation, the communication apparatus is a communication device. When the communication apparatus is a communication device, the communication interface may be a transceiver or an input / output interface; and the processor may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0791] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication interface can be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, or related circuit on the chip (system) or circuit; the processor can be at least one processor, processing circuit, or logic circuit.

[0792] According to an embodiment of the present application, each unit in the device shown in Figure 23 can be separately or all merged into one or several other units to constitute, or a certain (some) unit therein can also be split into multiple smaller units to constitute, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the function of a unit can also be realized by multiple units, or the function of multiple units can be realized by one unit. In other embodiments of the present application, other units can also be included based on electronic equipment. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by collaboration of multiple units.

[0793] It should be noted that the implementation of each unit may also refer to the corresponding description of the method embodiments shown in Figures 9 to 16 and Figures 19 to 21 above.

[0794] In the communication device 230 described in FIG. 23 , the occurrence of trigger conflicts can be avoided, or when a trigger conflict exists, the target CU of DU migration can be determined, thereby ensuring smooth completion of DU migration.

[0795] In another possible design, the communication device 230 may correspond to the OAM server in the method embodiments shown in Figures 12, 13, 14, 17, and 18 above, for example, the communication device 230 may be an OAM server or a chip in the OAM server. The communication device 230 may include a unit for executing the operations performed by the first host node in the method embodiments shown in Figures 12, 13, 14, 17, and 18 above, and each unit in the communication device 230 is respectively for implementing the operations performed by the OAM server in the method embodiments shown in Figures 12, 13, 14, 17, and 18 above. The description of each unit is as follows:

[0796] The communication interface 2301 is configured to receive fourth information from the relay node, where the fourth information includes a result of the relay node establishing a third F1 interface with the target host node.

[0797] Processor 2302 is configured to process the fourth information.

[0798] or,

[0799] Processor 2302 is configured to generate tenth information, where the tenth information is used to instruct the relay node to perform DU migration;

[0800] The communication interface 2301 is configured to send the tenth information to the relay node.

[0801] The methods executed by the processor 2302 and the communication interface 2301 can refer to the methods corresponding to Figures 12, 13, 14, 17 and 18 above, and will not be repeated here.

[0802] Regarding the technical effects brought about by any of the above designs and any possible implementation methods, please refer to the introduction of the technical effects of the corresponding methods in Figures 12, 13, 14, 17 and 18 above, which will not be repeated here.

[0803] Optionally, in the communication device described in any of the foregoing designs and any of the possible implementations:

[0804] In one implementation, the communication apparatus is a communication device. When the communication apparatus is a communication device, the communication interface may be a transceiver or an input / output interface; and the processor may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0805] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication interface can be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, or related circuit on the chip (system) or circuit; the processor can be at least one processor, processing circuit, or logic circuit.

[0806] According to an embodiment of the present application, each unit in the device shown in Figure 23 can be separately or all merged into one or several other units to constitute, or a certain (some) unit therein can also be split into multiple smaller units to constitute, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the function of a unit can also be realized by multiple units, or the function of multiple units can be realized by one unit. In other embodiments of the present application, other units can also be included based on electronic equipment. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by collaboration of multiple units.

[0807] It should be noted that the implementation of each unit may also refer to the corresponding description of the method embodiments shown in the above-mentioned Figures 12, 13, 14, 17 and 18.

[0808] In the communication device 230 described in FIG. 23 , the network manager can obtain the connection relationship of the relay node in a timely manner, which facilitates the network manager's management of the relay node and the next DU migration, thereby ensuring the smooth completion of DU migration.

[0809] In another possible design, the communication device 230 may correspond to the second host node in the method embodiment shown in FIG. 21 above. For example, the communication device 230 may be the second host node or a chip in the second host node. The communication device 230 may include a unit for executing the operations performed by the second host node in the method embodiment shown in FIG. 21 above, and each unit in the communication device 230 is respectively for implementing the operations performed by the second host node in the method embodiment shown in FIG. 21 above. The description of each unit is as follows:

[0810] The communication interface 2301 is configured to receive fourteenth information from the first host node, where the fourteenth information is used to instruct to cancel establishing the F1 interface between the second host node and the relay node.

[0811] Processor 2302 is configured to process the fourteenth information.

[0812] The method executed by the above-mentioned processor 2302 and communication interface 2301 can refer to the method corresponding to the above-mentioned Figure 21, which will not be repeated here.

[0813] Regarding the technical effects brought about by any of the above designs and any possible implementation methods, please refer to the introduction of the technical effects of the corresponding method in Figure 21 above, and no further details will be given here.

[0814] Optionally, in the communication device described in any of the foregoing designs and any of the possible implementations:

[0815] In one implementation, the communication apparatus is a communication device. When the communication apparatus is a communication device, the communication interface may be a transceiver or an input / output interface; and the processor may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0816] In another implementation, the communication device is a chip (system) or circuit used in a communication device. When the communication device is a chip (system) or circuit used in a communication device, the communication interface can be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, or related circuit on the chip (system) or circuit; the processor can be at least one processor, processing circuit, or logic circuit.

[0817] According to an embodiment of the present application, each unit in the device shown in Figure 23 can be separately or all merged into one or several other units to constitute, or a certain (some) unit therein can also be split into multiple smaller units to constitute, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the function of a unit can also be realized by multiple units, or the function of multiple units can be realized by one unit. In other embodiments of the present application, other units can also be included based on electronic equipment. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by collaboration of multiple units.

[0818] It should be noted that the implementation of each unit can also refer to the corresponding description of the method embodiment shown in Figure 21 above.

[0819] In the communication device 230 described in Figure 23, the abnormal situation caused by the second host node trying to establish the F1 interface with the relay node again can be avoided. In addition, the second host node can use ef...

Claims

1. A communication method, characterized in that: The method comprises: The relay node sends a first message to the first host node when the first trigger condition is met; the first message includes a result of the relay node establishing the first F1 interface with the target host node and an identifier of the target host node; or, the first message includes a result of the relay node establishing the first F1 interface with the target host node, an identifier of the target host node, and a triggering method for DU migration of the relay node; The first trigger condition includes at least one of the following: Based on second information provided by the network management, the second information is used to instruct the relay node to establish the first F1 interface with the target host node; or, the relay node receives third information from the first host node, and the third information is used to instruct the relay node to establish a second F1 interface with a second host node, and the second host node is different from the target host node.

2. The method according to claim 1, characterized in that The result of the first F1 interface is that the F1 interface between the relay node and the target host node is established.

3. The method according to claim 1 or 2, characterized in that: The second information is also used to trigger the release of the second F1 interface.

4. A communication method, characterized in that: The method comprises: When the first trigger condition is met, the first host node receives first information from the relay node; the first information includes a result of the relay node establishing the first F1 interface with the target host node and an identifier of the target host node; or, the first information includes a result of the relay node establishing the first F1 interface with the target host node, an identifier of the target host node, and a triggering method for DU migration of the relay node; The first trigger condition includes at least one of the following: Based on second information provided by the network management, the second information is used to instruct the relay node to establish the first F1 interface with the target host node; or, the relay node receives third information from the first host node, and the third information is used to instruct the relay node to establish a second F1 interface with a second host node, and the second host node is different from the target host node.

5. A communication method, characterized in that: The method comprises: The relay node sends fourth information to the network manager; the fourth information includes the result of the relay node establishing the third F1 interface with the target host node.

6. The method according to claim 5, characterized in that The relay node sends fourth information to the network manager, including: When the second trigger condition is met, the relay node sends the fourth information to the network manager; The second trigger condition includes at least one of the following: The relay node receives fifth information from the first host node, and the fifth information is used to instruct the relay node to establish the third F1 interface with the target host node; or, based on sixth information provided by the network management, the sixth information is used to instruct the relay node to establish a fourth F1 interface with the second host node, and the second host node is different from the target host node; or, the relay node receives seventh information from the target host node, and the seventh information is used to indicate that the establishment of the third F1 interface is completed.

7. The method according to claim 5 or 6, characterized in that: The fifth information is also used to trigger the release of the fourth F1 interface.

8. The method according to any one of claims 5 to 7, characterized in that: The fourth information also includes the identifier of the target host node and / or the triggering method of the DU migration.

9. The method according to claim 8, characterized in that The fourth information also includes the identifier of the target host node and / or the triggering method of the DU migration, including: In the case where the second trigger condition includes the relay node receiving the fifth information from the first host node and / or the sixth information provided based on the network management, the fourth information also includes the identifier of the target host node and / or the DU migration Trigger method.

10. A communication method, characterized in that: The method comprises: The network manager receives fourth information from the relay node, where the fourth information includes a result of the relay node establishing a third F1 interface with the target host node.

11. A communication method, characterized in that: The method comprises: The relay node receives the eighth information from the first host node, and sends the ninth information to the first host node; the eighth information is used to instruct the relay node to perform DU migration, and the ninth information is used to instruct the relay node to refuse to perform the DU migration.

12. The method according to claim 11, characterized in that The ninth information includes the reason why the relay node refuses to perform the DU migration.

13. A communication method, characterized in that: The method comprises: The first host node sends eighth information to the relay node, and receives ninth information from the relay node; the eighth information is used to instruct the relay node to perform DU migration, and the ninth information is used to instruct the relay node to refuse to perform the DU migration.

14. A communication method, characterized in that: The method comprises: The relay node receives tenth information from the network management, where the tenth information is used to instruct the relay node to perform DU migration; The DU ignores the tenth information.

15. The method according to claim 14, characterized in that The method further comprises: The relay node sends eleventh information to the network manager, where the eleventh information is used to indicate rejection of DU migration triggered by the network manager or to indicate that the network manager does not trigger DU migration of the relay node.

16. A communication method, characterized in that: The method comprises: The network management sends tenth information to the relay node, where the tenth information is used to instruct the relay node to perform DU migration; The network manager receives eleventh information from the relay node, where the eleventh information is used to indicate rejection of DU migration triggered by the network manager or to indicate that the network manager does not trigger DU migration of the relay node.

17. A communication method, characterized in that: The method comprises: The relay node sends twelfth information to the first host node; The twelfth information is used to indicate the triggering method of DU migration supported by the relay node; and / or the relay node receives the thirteenth information from the first host node, and the thirteenth information is used to indicate the triggering method of DU migration supported by the relay node; the triggering method includes CU triggering and / or network management triggering.

18. The method according to claim 17, characterized in that The relay node sends twelfth information to the first host node, including: When a third trigger condition is met, the relay node sends the twelfth information to the first host node; The third trigger condition includes at least one of the following: The relay node completes network access; or, the relay node completes DU migration.

19. A communication method, characterized in that: The method comprises: The first host node sends thirteenth information to the relay node; The thirteenth information is used to indicate the triggering method of DU migration supported by the relay node; and / or, the first host node receives the twelfth information from the relay node, and the twelfth information is used to indicate the triggering method of DU migration supported by the relay node; the triggering method includes CU triggering and / or network management triggering.

20. A communication method, characterized in that: The method comprises: When the fourth trigger condition is met, the first host node sends fourteenth information to the second host node; the fourteenth information is used to indicate cancellation of establishing the F1 interface between the second host node and the relay node; Wherein, the fourth trigger condition includes: The fifteenth information is received from the relay node, wherein the fifteenth information includes that the relay node completes the establishment of an F1 interface with a target host node, and the target host node is different from the second host node.

21. A communication method, characterized in that: The method comprises: The second host node receives fourteenth information from the first host node, where the fourteenth information is used to indicate to cancel establishing the F1 interface between the second host node and the relay node.

22. A communication device, characterized in that: Comprising means for performing the method as claimed in any one of claims 1 to 21.

23. A communication device, characterized in that: comprising a processor for executing the method as claimed in any one of claims 1 to 21.

24. A communication device, characterized in that: comprising a logic circuit and an interface, wherein the logic circuit and the interface are coupled; The interface is used for inputting and / or outputting information, and the logic circuit is used for executing the method according to any one of claims 1 to 21.

25. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store a computer program, and when the computer program is executed, the method according to any one of claims 1 to 21 is performed.

26. A communication system, characterized in that: comprising at least one of the following: a relay node, a first host node, a second host node, and a network manager; The relay node is used to execute the method as described in any one of claims 1 to 3, 5 to 9, 11 to 12, 14 to 15, 17 to 18, the first host node is used to execute the method as described in any one of claims 4, 13, 17-20, the second host node is used to execute the method as described in claim 21, and the network manager is used to execute the method as claimed in claim 10 or 16.

Images