Communication method and communication apparatus

Abstract

A communication method and a communication apparatus. In a wireless access and backhaul-mobile terminal (WAB-MT) handover scenario, before a WAB-MT is handed over to a target backhaul-related RAN node (target BH-RAN-NODE) or during the handover of the WAB-MT, the target BH-RAN-NODE may acquire information of a wireless access and backhaul-next generation NodeB (WAB-gNB) bound to the WAB-MT (e.g., acquiring the information by means of a handover request), or the WAB-gNB acquires information of the target BH-RAN-NODE (e.g., acquiring the information by means of a handover command). The WAB-gNB and the target BH-RAN-NODE may establish an Xn interface on the basis of these pieces of information, and perform resource multiplexing by means of the Xn interface. Therefore, resource multiplexing can be performed between the WAB-gNB and the target BH-RAN-NODE as early as possible, so as to reduce interference and service experience degradation that may occur during WAB-MT handover, thereby ensuring the communication efficiency.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202411984372.2, filed with the State Intellectual Property Office of China on December 27, 2024, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more specifically, to a communication method and a communication device. Background Technology

[0003] In a wireless access and backhaul (WAB) architecture, a relay node can be called a WAB node. The functions of a WAB node include WAB access network functions and WAB terminal functions. For example, the WAB access network function (WAB-RAN) can be implemented using the WAB next generation NodeB (gNB) function (WAB-gNB) node, and the WAB terminal function can be implemented using the WAB mobile terminal (MT) function (WAB-MT) node. In other words, a WAB node can include both WAB-gNB and WAB-MT nodes, and these nodes can reside in the same physical device.

[0004] As a mobile relay node, the WAB node may cause interference if the access link and backhaul link are used improperly. Therefore, the WAB-gNB node and the WAB-MT node need to be time-domain staggered. This time-domain staggering can be understood as follows: when the WAB-gNB node schedules terminals under the WAB-gNB, the backhaul-related RAN node (BH-RAN-NODE) ​​accessed by the WAB-MT cannot schedule the WAB-MT. Otherwise, if the WAB-gNB and WAB-MT operate simultaneously and are located in the same physical device, interference will occur. In order for WAB-gNB and WAB-MT to be time-domain staggered, BH-RAN-NODE needs to be aware of the existence of WAB-gNB and know the binding relationship between WAB-gNB and WAB-MT, as well as the resource configuration of WAB-gNB (the resource configuration when WAB-gNB schedules terminals under WAB-gNB). In this way, BH-RAN-NODE can stagger the scheduling of WAB-MT. This process can be called resource negotiation, resource coordination, or resource multiplexing.

[0005] Currently, in WAB-MT node handover scenarios, i.e., when WAB-MT switches from the source BH-RAN-NODE to the target BH-RAN-NODE, the resource reuse between WAB-gNB and the target BH-RAN-NODE occurs relatively late, which may cause interference and service interruption for a period of time, reducing communication efficiency. Summary of the Invention

[0006] This application provides a communication method and communication device. Before the WAB-MT switches to the target backhaul access network node or during the switching process of the WAB-MT node, the target backhaul access network node can reuse resources with the WAB-gNB. This allows the WAB-gNB and the target backhaul access network node to reuse resources as early as possible, avoiding interference and service interruption, and ensuring communication efficiency.

[0007] Firstly, a communication method is provided. The subject executing this method can be the target backhaul access network node (target BH-RAN-NODE) ​​for WAB-MT handover, or a component (chip, chip system, or processor) that supports the target BH-RAN-NODE in implementing this method, or a logic module or software that can implement all or part of the target BH-RAN-NODE's functions. Taking the target BH-RAN-NODE as the executing entity as an example, the method includes: the target backhaul access network node of the WAB-MT handover receives first information from the source backhaul access network node (source BH-RAN-NODE) ​​of the WAB-MT handover. The first information includes at least one of the following: identification information of the radio access backhaul node base station function WAB-gNB, first resource configuration information of the WAB-gNB, or frequency information of the WAB-gNB, and identification information of the WAB-MT. The first resource configuration information includes the resource configuration of the WAB-gNB. The target backhaul access network node sends second resource configuration information to the WAB-gNB, the WAB-MT, or the source backhaul access network node according to the first information. The second resource configuration information is used for resource multiplexing between the WAB-gNB and the WAB-MT.

[0008] The communication method provided in the first aspect allows the target BH-RAN-NODE to obtain information about the WAB-gNB bound to the WAB-MT before or during the WAB-MT handover. The target BH-RAN-NODE can then reuse resources with the WAB-gNB based on this information, i.e., send second resource configuration information to the WAB-gNB, WAB-MT, or the source backhaul access network node. This enables early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT handover process and ensuring communication efficiency.

[0009] In one possible implementation of the first aspect, the second resource configuration information includes the resource configuration that WAB-gNB needs to adjust. The resource configuration that WAB-gNB needs to adjust must satisfy the following condition: after the WAB-MT handover, the resource configuration that WAB-gNB needs to adjust is time-domain offset from the time-domain resources of WAB-MT. Achieving time-domain offset between WAB-gNB and WAB-MT by determining the method of adjusting the resource configuration that WAB-gNB needs is flexible and easy to implement.

[0010] In one possible implementation of the first aspect, the second resource configuration information includes the resource configuration of the WAB-MT. The resource configuration of the WAB-MT needs to satisfy the following: after the WAB-MT switches to the target BH-RAN-NODE, the time-domain resources of the WAB-gNB and the WAB-MT are time-domain staggered. Achieving this time-domain staggering between the WAB-gNB and WAB-MT by determining the WAB-MT's resource configuration is flexible and easy to implement. The resource configuration of the WAB-MT can be understood as: the resource configuration of the WAB-MT after switching to the target BH-RAN-NODE, i.e., the resource configuration when the target BH-RAN-NODE schedules the WAB-MT.

[0011] In one possible implementation of the first aspect, the second resource configuration information includes the resource configuration of the target BH-RAN-NODE. The resource configuration of the target BH-RAN-NODE can be understood as the resource configuration when the target BH-RAN-NODE schedules WAB-MT. After receiving the second resource configuration information, the WAB-gNB determines the resource configuration that the WAB-gNB needs to adjust based on the resource configuration of the target BH-RAN-NODE. By having the WAB-gNB determine its own resource configuration based on the resource configuration of the target BH-RAN-NODE, the time-domain resources of the WAB-gNB and WAB-MT are staggered in the time domain. This implementation method is flexible and easy to implement. Specifically, the resource configuration of the target BH-RAN-NODE can be understood as: the resource configuration when the target BH-RAN-NODE schedules WAB-MT (i.e., the resource configuration of WAB-MT after handover).

[0012] The first resource configuration information of the WAB-gNB can be understood as the resource configuration information when the WAB-gNB schedules the UE. This information may include the frequency information and time-domain information of the WAB-gNB. For example, it may include the frequency information (e.g., operating frequency) used by the WAB-gNB when scheduling the UE. The time-domain information may include the time slot configuration information used by the WAB-gNB when scheduling the UE.

[0013] In one possible implementation of the first aspect, the identification information of the WAB-gNB includes: at least one IP address corresponding to the WAB-gNB, and / or, the base station identifier of the WAB-gNB. This implementation can improve the accuracy and efficiency of the target BH-RAN-NODE in determining whether a communication interface (Xn interface) exists with the WAB-gNB and in establishing that communication interface.

[0014] The identification information of WAB-MT can indicate a binding or association relationship between WAB-gNB and WAB-MT, or in other words, the identification information of WAB-MT can indicate a binding or association relationship between WAB-gNB and WAB-MT. For example, the identification information of WAB-MT can include: the "UE XnAP ID" of WAB-MT on the Xn interface between the source BH-RAN-NODE and the target BH-RAN-NODE, or the "UE XnAP ID" on the target BH-RAN-NODE.

[0015] In one possible implementation of the first aspect, when the first information includes the identification information of the WAB-gNB, the method further includes: the target backhaul access network node determining whether a communication interface exists between itself and the WAB-gNB based on the identification information of the WAB-gNB; if the communication interface does not exist, establishing the communication interface between the target backhaul access network node and the WAB-gNB; and the target backhaul access network node sending second resource configuration information to the WAB-gNB, including: the target backhaul access network node sending the second resource configuration information to the WAB-gNB through the communication interface. In this implementation, determining whether a communication interface exists between the target BH-RAN-NODE and the WAB-gNB avoids repeatedly establishing a communication interface when one already exists, reducing communication resource consumption and improving communication resource utilization. Using the communication interface to transmit the second resource configuration information improves the efficiency and accuracy of the second resource configuration information transmission.

[0016] In one possible implementation of the first aspect, establishing the communication interface between the target backhaul access network node and the WAB-gNB includes: the target backhaul access node establishing the communication interface (Xn interface) with the WAB-gNB based on at least one IP address. In this implementation, using first information including at least one IP address corresponding to the WAB-gNB and the target BH-RAN-NODE to establish the communication interface can improve the efficiency of establishing the communication interface.

[0017] In one possible implementation of the first aspect, if the first information does not include the first resource configuration information of the WAB-gNB, before the target backhaul access network node sends the second resource configuration information, the method further includes: the target backhaul access network node sending a request message to the WAB-gNB through the communication interface, the request message being used to request the first resource configuration information; and the target backhaul access network node receiving the first resource configuration information from the WAB-gNB through the communication interface. In this implementation, using the communication interface to obtain the first resource configuration information, and thus using the first resource configuration information for resource reuse, can ensure the accuracy and efficiency of resource reuse.

[0018] In one possible implementation of the first aspect, the target backhaul access network node sends second resource configuration information to the WAB-MT or the source backhaul access network node, including: if the first information does not include the identification information of the WAB-gNB, the target backhaul access network node sends the second resource configuration information to the WAB-MT or the source backhaul access network node. This implementation ensures that the second resource configuration information can be transmitted normally, and guarantees the normal operation of resource reuse.

[0019] In one possible implementation of the first aspect, when the first information includes the frequency information of the WAB-gNB, before the target backhaul access network node sends the second resource configuration information, the method further includes: the target backhaul access network node determining that the operating frequency of the WAB-gNB is the same as the operating frequency of the WAB-MT. In this implementation, sending the second resource configuration information (i.e., performing resource multiplexing) only after determining that the WAB-MT has switched over and that the WAB-gNB is operating in in-band mode can avoid useless resource multiplexing, reduce communication resource consumption, and improve the accuracy and efficiency of resource multiplexing.

[0020] In one possible implementation of the first aspect, after the target backhaul access network node sends the second resource configuration information, the method further includes: the target backhaul access network node sending a handover command to the WAB-MT, the handover command instructing the WAB-MT to switch from the source backhaul access network node to the target backhaul access network node. In this implementation, it can be ensured that before the WAB-MT switches to the target BH-RAN-NODE, the target BH-RAN-NODE can perform resource reuse with the WAB-gNB based on the WAB-gNB information. This allows for early resource reuse between the WAB-gNB and the target BH-RAN-NODE.

[0021] Secondly, a communication method is provided. The execution subject of this method can be the source backhaul access network node (source BH-RAN-NODE) ​​for WAB-MT handover, or a component (chip, chip system, or processor) that supports the source BH-RAN-NODE in implementing this method, or a logic module or software capable of implementing all or part of the source BH-RAN-NODE's functions. Taking the source BH-RAN-NODE as the execution subject as an example, the method includes: the source backhaul access network node determining the binding relationship between WAB-MT and WAB-gNB; the source backhaul access network node sending first information to the target backhaul access network node, the first information including at least one of the following: identification information of WAB-gNB, first resource configuration information of WAB-gNB, or frequency information of WAB-gNB, and identification information of WAB-MT, wherein the first resource configuration information includes the resource configuration of the WAB-gNB.

[0022] The second aspect provides a communication method where, before the WAB-MT handover, the source BH-RAN-NODE sends information about the WAB-gNB bound to the WAB-MT to the target BH-RAN-NODE. This allows the target BH-RAN-NODE to reuse resources based on the WAB-gNB information. This enables early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT handover process and ensuring communication efficiency.

[0023] In one possible implementation of the second aspect, the identification information of the WAB-gNB includes: at least one IP address corresponding to the WAB-gNB, and / or, the base station identifier of the WAB-gNB.

[0024] In one possible implementation of the second aspect, before the source backhaul access network node sends the first information to the target backhaul access network node, the method further includes: the source backhaul access network node receiving second information from the WAB-MT or the WAB-gNB, the second information including: the first IP address of the WAB-gNB, the first IP address including one or more IP addresses, and at least one IP address corresponding to the WAB-gNB including the first IP address. In this implementation, the source BH-RAN-NODE can send the first IP address of the WAB-gNB to the target BH-RAN-NODE, which can improve the efficiency and accuracy of determining whether an Xn interface exists and establishing an Xn interface between the target BH-RAN-NODE and the WAB-gNB.

[0025] In one possible implementation of the second aspect, if the first information does not include the identification information of the WAB-gNB, the method further includes: the source backhaul access network node receiving second resource configuration information from the target backhaul access network node, the second resource configuration information being used for resource multiplexing between the WAB-gNB and the WAB-MT; and the source backhaul access network node sending the second resource configuration information to the WAB-gNB or the WAB-MT.

[0026] For an explanation of the beneficial effects of the various possible implementation methods of the second aspect, please refer to the corresponding part of the first aspect and the explanation of the beneficial effects mentioned above, which will not be repeated here.

[0027] Thirdly, a communication method is provided. The subject of this method can be the target backhaul access network node (target BH-RAN-NODE) ​​for WAB-MT switching, or a component (chip, chip system, or processor) that supports the target BH-RAN-NODE in implementing this method, or a logic module or software that can implement all or part of the target BH-RAN-NODE's functions. Taking the target BH-RAN-NODE as the executing entity as an example, the method includes: the target backhaul access network node for WAB-MT handover receives a handover request from the source backhaul access network node for the WAB-MT handover; in response to the handover request, the target backhaul access network node sends a handover command to the WAB-MT, the handover command instructing the WAB-MT to handover from the source backhaul access network node to the target backhaul access network node, the handover command including: first identification information of the target backhaul access network node and identification information of the WAB-MT; the target backhaul access network node receives third information from the radio access backhaul node base station function WAB-gNB through a communication interface, the third information including: identification information of the WAB-MT and first resource configuration information, the first resource configuration information including the resource configuration of the WAB-gNB; the target backhaul access network node sends second resource configuration information to the WAB-gNB through the communication interface according to the first resource configuration information, the second resource configuration information being used for resource multiplexing between the WAB-gNB and the WAB-MT.

[0028] The third aspect provides a communication method where, before the WAB-MT handover, the target BH-RAN-NODE can send its information to the WAB-gNB bound to the WAB-MT via a handover command. Based on the information obtained from the target BH-RAN-NODE, the WAB-gNB can establish an Xn interface with the target BH-RAN-NODE, transmitting first resource configuration information and performing resource reuse through the Xn interface. This enables early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT handover process and ensuring communication efficiency.

[0029] For a detailed explanation of the second resource allocation information, please refer to the corresponding section of the first aspect above and the explanation of the beneficial effects; it will not be repeated here.

[0030] The identification information of the WAB-MT can indicate the binding or association relationship between the WAB-gNB and the WAB-MT. The target BH-RAN-NODE can determine which WAB-MT and WAB-gNB are associated based on the identification information of the WAB-MT, thereby enabling resource reuse between the WAB-MT and WAB-gNB. For example, the identification information of the WAB-MT may include: the Radio Network Temporary Identifier (C-RNTI) of the WAB-MT in the cell served by the target backhaul access network node, and / or, the identifier of the WAB-MT on the communication interface between the target backhaul access network node and the source backhaul access network node. For example, the identifier of the WAB-MT on the communication interface between the target backhaul access network node and the source backhaul access network node may be: the "UE XnAP ID" of the WAB-MT on the Xn interface between the source BH-RAN-NODE and the target BH-RAN-NODE, or the "UE XnAP ID" on the target BH-RAN-NODE.

[0031] In one possible implementation of the third aspect, the first identification information of the target backhaul access network node includes: at least one IP address corresponding to the target backhaul access network node, and / or, the base station identifier of the target backhaul access network node. In this implementation, utilizing the first identification information of the target BH-RAN-NODE can improve the efficiency and accuracy of the WAB-gNB in ​​determining whether an Xn interface exists between it and the target BH-RAN-NODE, and in establishing the Xn interface.

[0032] In one possible implementation of the third aspect, after the target backhaul access network node receives the third information from the WAB-gNB through the communication interface, the target backhaul access network node receives the access request from the WAB-MT. This implementation ensures that the target BH-RAN-NODE and WAB-gNB reuse resources before the WAB-MT switches to the target BH-RAN-NODE. This enables early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT handover process.

[0033] Fourthly, a communication method is provided. The executing entity of this method can be the source backhaul access network node (target BH-RAN-NODE) ​​for WAB-MT handover, a component (chip, chip system, or processor) supporting the source BH-RAN-NODE in implementing this method, or a logic module or software capable of implementing all or part of the source BH-RAN-NODE's functions. Taking the source BH-RAN-NODE as the executing entity as an example, the method includes: the source backhaul access network node for WAB-MT handover sending a handover request to the target backhaul access network node for the WAB-MT handover; the source backhaul access network node receiving a handover request response message from the target backhaul access network node; and the source backhaul access network node sending fourth information to the WAB-MT or the radio access backhaul node base station function WAB-gNB according to the handover request response message. The fourth information includes: the second identification information of the target backhaul access network node and the identification information of the WAB-MT.

[0034] The fourth aspect provides a communication method whereby, before the WAB-MT handover, the source BH-RAN-NODE can transmit the target BH-RAN-NODE's information to the WAB-gNB bound to the WAB-MT, enabling the WAB-gNB to reuse resources based on the acquired target BH-RAN-NODE information. This allows for early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT handover process and ensuring communication efficiency.

[0035] In one possible implementation of the fourth aspect, the second identification information of the target backhaul access network node includes: a first IP address corresponding to the target backhaul access network node, and / or, the base station identifier of the target backhaul access network node, wherein the first IP address corresponding to the target backhaul access network node includes: the IP address used to establish a communication interface between the target backhaul access network node and the source backhaul access network node. This implementation can improve the efficiency and accuracy of the WAB-gNB in ​​determining whether an Xn interface exists between it and the target BH-RAN-NODE and in establishing the Xn interface.

[0036] The WAB-MT identification information indicates the binding or association relationship between WAB-gNB and WAB-MT. For a detailed explanation of the WAB-MT identification information, please refer to the corresponding section and the explanation of its beneficial effects mentioned above; further details will not be repeated here.

[0037] In one possible implementation of the fourth aspect, after the source backhaul access network node sends the fourth information to the WAB-MT or the WAB-gNB, the method further includes: the source backhaul access network node sending a handover command to the WAB-MT, which instructs the WAB-MT to hand over from the source backhaul access network node to the target backhaul access network node. This implementation ensures that the target BH-RAN-NODE and the WAB-gNB reuse resources before the WAB-MT hands over to the target BH-RAN-NODE, enabling early resource reuse between the WAB-gNB and the target BH-RAN-NODE and reducing potential interference and service degradation during the WAB-MT handover process.

[0038] Fifthly, a communication method is provided. The execution subject of this method can be a WAB-gNB bound to WAB-MT, a component (chip, chip system, or processor) that supports WAB-gNB in ​​implementing this method, or a logic module or software that can implement all or part of the functions of WAB-gNB. Taking WAB-gNB as the executing entity as an example, the method includes: the WAB-gNB (Radio Access Backhaul Node Base Station Function) receives a handover command or fourth information. The handover command instructs the WAB-MT (Radio Access Backhaul Node Terminal Function) to switch from the source backhaul access network node to the target backhaul access network node. The handover command includes: first identification information of the target backhaul access network node and identification information of the WAB-MT. The fourth information includes: second identification information of the target backhaul access network node and identification information of the WAB-MT. In response to the handover command or fourth information, the WAB-gNB sends third information to the target backhaul access network node through a communication interface. The third information includes: identification information of the WAB-MT and first resource configuration information. The first resource configuration information includes the resource configuration of the WAB-gNB. The WAB-gNB receives second resource configuration information from the target backhaul access network node through the communication interface. The second resource configuration information is used for resource multiplexing between the WAB-gNB and the WAB-MT.

[0039] The fifth aspect provides a communication method whereby, before the WAB-MT handover, the WAB-gNB bound to the WAB-MT can obtain information about the target BH-RAN-NODE for the WAB-MT handover. The WAB-gNB then performs resource reuse based on this information and the target BH-RAN-NODE. This enables early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT handover process and ensuring communication efficiency.

[0040] For a detailed explanation of the second resource allocation information, please refer to the corresponding section of the first aspect above and the explanation of the beneficial effects; it will not be repeated here.

[0041] For explanations of the first identification information of the target backhaul access network node, the second identification information of the target backhaul access network node, and the identification information of WAB-MT, please refer to the corresponding parts of the third and fourth aspects above, as well as the explanation of the beneficial effects, which will not be repeated here.

[0042] In one possible implementation of the fifth aspect, the method further includes: the WAB-gNB determining whether a communication interface exists between itself and the target backhaul access network node based on either the first identification information or the second identification information of the target backhaul access network node; and establishing the communication interface between the WAB-gNB and the target backhaul access network node if no communication interface exists. In this implementation, by determining whether a communication interface exists between the target BH-RAN-NODE and the WAB-gNB, the redundant establishment of the communication interface when one already exists can be avoided, reducing the consumption of communication resources and improving the utilization rate of communication resources.

[0043] In one possible implementation of the fifth aspect, establishing the communication interface between the WAB-gNB and the target backhaul access network node includes: the WAB-gNB establishing the communication interface with the target backhaul access network node based on at least one IP address corresponding to the target backhaul access network node or a first IP address corresponding to the target backhaul access network node. In this implementation, using the IP address corresponding to the WAB-gNB and the target BH-RAN-NODE to establish the communication interface can improve the efficiency of establishing the communication interface.

[0044] In one possible implementation of the fifth aspect, after the WAB-gNB sends the third information to the target backhaul access network node through the communication interface, the WAB-MT switches from the source backhaul access network node to the target backhaul access network node according to the handover command. This implementation ensures that the target BH-RAN-NODE and WAB-gNB reuse resources before the WAB-MT switches to the target BH-RAN-NODE, enabling early resource reuse between the WAB-gNB and the target BH-RAN-NODE.

[0045] In a sixth aspect, a communication device is provided, the device comprising: a module (e.g., including a processing module and a communication module) for performing any of the steps of any of the first to fifth aspects above, or any possible implementation of any of the first to fifth aspects above.

[0046] In a seventh aspect, a communication device is provided, the device comprising at least one processor, the at least one processor being configured to execute: the method of any one of the first to fifth aspects above, or the method of any possible implementation of any one of the first to fifth aspects.

[0047] In one possible implementation, the communication device may further include a memory storing a computer program, and at least one processor executes the method of any one of the first to fifth aspects above, or the method of any possible implementation of any one of the first to fifth aspects above, by executing the computer program stored in the memory.

[0048] In one possible implementation, at least one processor executes the method of any one of the first to fifth aspects above, or the method of any possible implementation of any one of the first to fifth aspects above, via logic circuitry or processing circuitry.

[0049] In one possible implementation, the communication device may further include an interface circuit for performing specific signal transmission and reception.

[0050] For example, the communication device can be a target backhaul access network node, a source backhaul access network node, a wireless access backhaul base station functional node, or a wireless access backhaul terminal functional node. It can also be a component (chip, chip system, or processor) in the target backhaul access network node, source backhaul access network node, wireless access backhaul base station functional node, or wireless access backhaul terminal functional node. Alternatively, it can be a logic module or software that can realize all or part of the terminal functions.

[0051] Eighthly, a target backhaul access network node, a source backhaul access network node, a wireless access backhaul base station functional node, or a wireless access backhaul terminal functional node is provided, including the communication device provided in the sixth aspect above, or including the communication device provided in the seventh aspect above.

[0052] Ninthly, a computer program product is provided, comprising a computer program that, when executed by a processor, performs the method of any one of the first to fifth aspects above, or the method of any possible implementation of any one of the first to fifth aspects above.

[0053] In a tenth aspect, a computer-readable storage medium is provided, wherein a computer program is stored therein, and when the computer program is executed, it is used to perform the method of any one of the first to fifth aspects above, or the method of any possible implementation of any one of the first to fifth aspects above.

[0054] Eleventhly, a chip is provided, the chip comprising: a processor for calling and running a computer program from a memory, causing a communication device on which the chip is installed to perform the method of any one of the first to fifth aspects above, or the method of any possible implementation of any one of the first to fifth aspects above.

[0055] In a twelfth aspect, a chip or system-on-a-chip is provided, comprising: logic circuitry for implementing the methods of any one of the first to fifth aspects above, or any possible implementation of any one of the first to fifth aspects above. Optionally, the chip or system-on-a-chip may further include interface circuitry.

[0056] In a thirteenth aspect, a communication system is provided, comprising: the target backhaul access network node, the source backhaul access network node, the wireless access backhaul base station functional node, and the wireless access backhaul terminal functional node provided above. Attached Figure Description

[0057] Figure 1 is a schematic diagram of a vehicle-mounted mobile relay scenario in a WAB.

[0058] Figure 2 is a schematic diagram of an example WAB network architecture provided in an embodiment of this application.

[0059] Figure 3 is a schematic diagram of an example communication system architecture applicable to this application, provided by an embodiment of this application.

[0060] Figure 4 is a schematic diagram of another communication system architecture applicable to this application, provided by an embodiment of this application.

[0061] Figure 5 is a schematic flowchart of a communication method provided in an embodiment of this application.

[0062] Figure 6 is a schematic flowchart of a communication method provided in an embodiment of this application.

[0063] Figure 7 is a schematic flowchart of a communication method provided in an embodiment of this application.

[0064] Figure 8 is a schematic block diagram of a communication device provided in an embodiment of this application.

[0065] Figure 9 is a schematic block diagram of another communication device provided in the embodiments of this application. Detailed Implementation

[0066] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0067] In the description of the embodiments of this application, unless otherwise stated, " / " means "or", for example, A / B can mean A or B; "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0068] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0069] In this embodiment, each communication node (e.g., WAB-gNB, WAB-MT, BH-RAN-NODE) ​​may include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment. For example, the execution entity of the method provided in this embodiment can be a communication node, or a functional module within the communication node that can call and execute a program.

[0070] Furthermore, various aspects or features of this application can be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). Additionally, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0071] In the topology enhancement project of 3GPP Release 19, a new architecture for WAB is being studied. Its main scenarios include vehicle mounted relay (VMR) scenarios. Figure 1 shows a schematic diagram of a VMR scenario, in which relay nodes are deployed on vehicles (or even airplanes) to provide wireless coverage for terminals inside the vehicle to overcome the problem of poor wireless signal inside the vehicle. The relay nodes access macro base stations through wireless backhaul.

[0072] The functions of a WAB node include WAB access network functions and WAB terminal functions. The WAB access network function provides access services to users, while the WAB terminal function provides backhaul functionality. For example, the WAB access network function (WAB-RAN) can be implemented using the WAB base station function node (WAB-gNB), and the WAB terminal function can be implemented using the WAB-MT. The following explanation will use WAB-gNB and WAB-MT as examples. In other words, a WAB node can include both WAB-gNB and WAB-MT nodes, or vice versa.

[0073] Optionally, in this embodiment, the WAB-gNB node can also be described as: Wireless Access Backhaul Node Base Station Function, Wireless Access Backhaul Node Base Station Function Node, Wireless Access Backhaul Node Base Station Function Node, or WAB-gNB. Unless otherwise specified, all five terms have the same meaning. The WAB-MT node can also be described as: Wireless Access Backhaul Node Terminal Function, Wireless Access Backhaul Node Terminal Function Node, Wireless Access Backhaul Node Terminal Function Node, or WAB-MT. Unless otherwise specified, all five terms have the same meaning.

[0074] For example, Figure 2 shows a schematic diagram of a WAB network architecture. As shown in Figure 2, the user equipment (UE) accesses the WAB-gNB node through the Uu interface. The WAB-gNB node sends the UE's data to the WAB-MT node. The WAB-MT node encapsulates the UE's data in the MT's protocol data unit session (MT PDU Session) and sends it through the WAB-MT node's Uu interface, via the backhaul-related RAN node (BH-RAN-NODE) ​​connected to the WAB-MT node, until it reaches the user plane function (UPF) of the WAB-MT node. The UPF of the WAB-MT node can be referred to as the BH UPF. Then, the BH UPF parses the MT-related packet header information to obtain the UE-related packet header information and sends it to the UE's UPF according to the Internet Protocol (IP) routing. Logically, a PDU session is also established between the UE and its UPF, but data packets are transmitted within the MT's PDU session. For example, BH-RAN-NODE can be BH-gNB.

[0075] In WAB, UE data is directly wrapped in MT's PDU session. During the WAB-MT node backhaul, this data is regarded as the WAB-MT node's own user plane data. After this data reaches BH-RAN-NODE through the WAB-MT node's data radio bearer (DRB), BH-RAN-NODE can only see MT's data, not UE's data. It is not until it is sent to MT's UPF (i.e., BH UPF) that BH UPF will parse the MT-related packet header information, obtain the UE-related packet header information, and then forward it to UE's UPF.

[0076] The above examples illustrate how the UE transmits user plane data with the UPF (i.e., the UE's UPF). The control plane transmission between the WAB-gNB and the access and mobility management function (AMF) is similar. The control plane signaling is also wrapped in the MT's PDU Session and forwarded by the MT's UPF (i.e., BH UPF) to the WAB-gNB's AMF (i.e., UE / gNB-AMF) via IP routing.

[0077] Furthermore, the WAB-gNB can establish logical Xn interfaces with the BH-RAN-NODE and nearby base stations (other gNBs). The data transmission method on the Xn interface (taking WAB-gNB sending data to the BH-RAN-NODE as an example) involves the WAB-gNB first sending the data to the MT's UPF (BH UPF) via the MT's PDU Session. Then, the MT's UPF forwards the data to the BH-RAN-NODE via IP routing. In other words, the WAB-gNB sends data to the WAB-MT, which encapsulates the data in its PDU Session and sends it through the WAB-MT's Uu interface, via the BH-RAN-NODE connected to the WAB-MT, until it reaches the BH UPF. The BH UPF then parses the MT-related packet header information to obtain the WAB-gNB-related packet header information and sends it to the BH-RAN-NODE according to IP routing. This results in a roundabout data transmission process. Because BH-RAN-NODE cannot parse the application layer of MT packets, it cannot identify whether the packets are intended for its own Xn interface. Therefore, BH-RAN-NODE can only send all packets to BH UPF. Even if some data is intended for BH-RAN-NODE, BH-RAN-NODE will first send it to BH UPF, and then BH UPF will forward it back to BH-RAN-NODE via IP routing.

[0078] As a mobile relay node, the WAB node may cause interference if the access link and backhaul link are used improperly. Therefore, the WAB-gNB node and the WAB-MT node need to be time-domain staggered. This time-domain staggering means that when the WAB-gNB node schedules a UE under the WAB-gNB, the BH-RAN-NODE cannot schedule the WAB-MT. Otherwise, if the WAB-gNB and WAB-MT operate simultaneously and are located in the same physical device, interference will occur. To achieve this time-domain staggering, the BH-RAN-NODE needs to be aware of the existence of the WAB-gNB and know the binding relationship between the WAB-gNB and WAB-MT, as well as the resource configuration of the WAB-gNB. This allows the BH-RAN-NODE to schedule the WAB-MT in a staggered manner. This process can be called resource negotiation, resource coordination, or resource multiplexing. There can be a binding or correspondence between a WAB-gNB and a WAB-MT, and a BH-RAN-NODE can be associated with or schedule multiple WAB-MTs.

[0079] If the WAB-gNB and WAB-MT operate on the same frequency, the WAB node is said to operate in in-band mode. If the WAB-gNB and WAB-MT operate on different frequencies, the WAB node is said to operate in out-band mode. In in-band mode, the scheduling of WAB-gNB and WAB-MT needs to be staggered in the time domain to avoid interference. In out-band mode, WAB-gNB and WAB-MT operate on different frequencies, so there is no interference and no additional resource reuse is required. The resource configuration of WAB-gNB can be understood as the resource configuration when the WAB-gNB node schedules the UE, including time-frequency resource configurations used by the UE for data transmission or control signaling. The resource configuration of BH-RAN-NODE can be understood as the resource configuration when BH-RAN-NODE schedules WAB-MT.

[0080] Currently, the specific process for resource reuse is still under discussion, but the general plan includes two approaches:

[0081] Method 1: The BH-RAN-NODE learns the binding relationship between WAB-gNB and WAB-MT and the original resource configuration of WAB-gNB through the radio resource control (RRC) message of WAB-MT or the Xn message of WAB-gNB. It then determines the resource configuration of WAB-MT that satisfies the condition that the WAB-gNB node and the WAB-MT node are time-domain staggered. Finally, it instructs WAB-MT on the resource configuration via an RRC message. This is a method by which the BH-RAN-NODE's resource configuration avoids the constraints of WAB-gNB's resource configuration. The RRC message of WAB-MT can be understood as an RRC message transmitted between WAB-MT and BH-RAN-NODE via the Uu interface. For example, BH-RAN-NODE sends an RRC message to WAB-MT via the Uu interface, and WAB-MT forwards the RRC message to WAB-gNB through its internal interface. The Xn message of WAB-gNB can be understood as: the message transmitted between BH-RAN-NODE and WAB-gNB through the Xn interface. For example, the Xn message sent directly from BH-RAN-NODE to WAB-gNB through the Xn interface.

[0082] Method 2: BH-RAN-NODE learns the binding relationship between WAB-gNB and WAB-MT and the original resource configuration of WAB-gNB through RRC messages from WAB-MT (sent by BH-RAN-NODE to WAB-MT and then forwarded to WAB-gNB) or Xn messages from WAB-gNB. Combined with BH-RAN-NODE's resource configuration, it determines the resource configuration that WAB-gNB needs to modify. The resource configuration that needs modification must ensure that the WAB-gNB node and the WAB-MT node are time-domain staggered. Then, BH-RAN-NODE requests WAB-gNB to modify the resource configuration through RRC or Xn messages. This is a way for WAB-gNB's resource configuration to avoid conflict with BH-RAN-NODE's resource configuration.

[0083] Of course, the two methods mentioned above can also be combined to avoid each other.

[0084] In summary, the BH-RAN-NODE can learn about the binding relationship between the WAB-gNB and the WAB-MT, as well as the original resource configuration of the WAB-gNB, through the RRC messages of the WAB-MT or the Xn messages of the WAB-gNB. The standard prefers that the BH-RAN-NODE obtain this information through the Xn messages of the WAB-gNB. In this case, an Xn interface (or Xn connection) needs to be established between the WAB-gNB and the BH-RAN-NODE. This requires the WAB-gNB to know the identifier of the BH-RAN-NODE, or the BH-RAN-NODE to know the identifier of the WAB-gNB, for establishing the Xn interface between the WAB-gNB and the BH-RAN-NODE.

[0085] The above briefly explains the resource reuse method in general scenarios (or initial access scenarios). In the WAB-MT node handover (HO) scenario, that is, when the WAB-MT switches from the source BH-RAN-NODE (source backhaul access network node) to the target BH-RAN-NODE (target backhaul access network node), the target BH-RAN-NODE connected to the WAB-MT node also needs to know the binding relationship between WAB-gNB and WAB-MT as well as the resource configuration of WAB-gNB to perform the above-mentioned resource reuse process.

[0086] For the WAB-MT node handover scenario, some solutions suggest that reusing resources after the WAB-MT node handover is completed is too late and may cause interference and service interruption for a period of time after the handover. Therefore, the WAB-gNB node should be informed of the target BH-RAN-NODE identifier of the WAB-MT node handover as soon as possible, so as to establish an Xn interface with the target BH-RAN-NODE for resource reuse as soon as possible.

[0087] In related technologies, after the WAB-MT node switches to the target station (target BH-RAN-NODE), it can receive the base station identifier length (gNB-ID-Length) and cell global identifier (CGI) carried in the system information block 1 (SIB1) of the target cell (i.e., the cell corresponding to the target BH-RAN-NODE). Based on the base station identifier length (gNB-ID-Length) and CGI, the WAB-MT node determines the identifier (ID) of the target BH-RAN-NODE and then informs the WAB-gNB through the internal interface, thereby enabling the WAB-gNB to obtain the identifier of the target BH-RAN-NODE. The CGI includes a base station identifier (gNB ID) and a cell identifier (cell ID). The "gNB-ID-Length" information element indicates the length of the gNB ID used by this base station (i.e., the target BH-RAN-NODE) ​​(the standard supports a gNB ID length of 22 to 32 bits). The WAB-MT can extract the value of the gNB ID of the BH-RAN-NODE from the CGI of the serving cell (i.e., the target cell) based on the obtained length of the gNB ID of the target BH-RAN-NODE, and then inform the WAB-gNB through the internal interface.

[0088] In other words, the aforementioned related technologies are as follows: After the WAB-MT node handover is completed, the WAB-gNB obtains the identifier of the target BH-RAN-NODE, uses the identifier of the BH-RAN-NODE obtained by the WAB-gNB, establishes an Xn interface between the WAB-gNB and the target BH-RAN-NODE, and uses the Xn interface to perform resource multiplexing.

[0089] However, when the WAB-MT node performs connected-state measurements at the source station (source BH-RAN-NODE), it does not read the SIB1 of neighboring cells. This is because reading SIB1 is a very time-consuming operation, requiring the source station to specifically configure measurement intervals (gap). Generally, in connected state, a wide range of neighboring cell measurements are performed, and SIB1 is not read for each neighboring cell. In other words, before the WAB-MT node switches to the target BH-RAN-NODE, resource reuse between the WAB-gNB and the target BH-RAN-NODE is not possible. If the WAB-MT node switches to the target station (target BH-RAN-NODE) ​​and then reads SIB1, i.e., according to the aforementioned related technologies, resource reuse between the WAB-gNB and the target BH-RAN-NODE occurs relatively late.

[0090] In summary, in the WAB-MT node handover scenario, the WAB-gNB only initiates the resource reuse process between the WAB-gNB and the target BH-RAN-NODE after the WAB-MT node switches to the target BH-RAN-NODE. The relatively late resource reuse between the WAB-gNB and the target BH-RAN-NODE may cause interference and service interruption for a period of time, reducing communication efficiency.

[0091] In view of this, this application provides a communication method in which, before the WAB-MT switches to the target backhaul access network node or during the handover process of the WAB-MT node, the target backhaul access network node can obtain information about the WAB-gNB bound to the WAB-MT (e.g., through a handover request), or the WAB-gNB can obtain information about the target backhaul access network node (e.g., through a handover command). The WAB-gNB and the target backhaul access network node can establish an Xn interface based on this information and perform resource reuse through the Xn interface. This allows the WAB-gNB and the target backhaul access network node to perform resource reuse as early as possible, avoiding interference and service interruptions, and ensuring communication efficiency.

[0092] To facilitate understanding of the embodiments of this application, the communication system applicable to the embodiments of this application will be briefly introduced first with reference to Figures 3 and 4.

[0093] It is understood that the communication method provided in this application can be applied to a WAB architecture. For example, Figure 3 shows a schematic diagram of a system architecture to which this application can be applied. In the system architecture shown in Figure 3, there is a binding or corresponding relationship between WAB-MT and WAB-gNB. WAB-MT needs to switch from the source backhaul access network node (source BH-RAN-NODE) ​​to the target backhaul access network node (target BH-RAN-NODE). The communication method provided in this application can be used before WAB-MT switches from the source BH-RAN-NODE to the target BH-RAN-NODE, or during the switching process of WAB-MT from the source BH-RAN-NODE to the target BH-RAN-NODE.

[0094] As shown in Figure 3, after the WAB-MT switches from the source BH-RAN-NODE to the target BH-RAN-NODE, the WAB-MT can establish a Uu interface with the target BH-RAN-NODE.

[0095] As shown in Figure 3, in one possible implementation, before WAB-MT switches to the target BH-RAN-NODE, or during the switching process of the WAB-MT node, WAB-gNB can establish an Xn interface with the target BH-RAN-NODE.

[0096] For example, the communication system used in the system architecture shown in Figure 3 can be a 3GPP-related cellular system, such as Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5G mobile communication system, New Radio (NR), Future Evolution System (e.g., Future Communication Network), cloud radio access network (CRAN), or it can be an open RAN (O-RAN or ORAN) system, or it can be a communication system that integrates two or more of the above systems. This application does not impose limitations on the embodiments described herein.

[0097] In one possible scenario, the BH-RAN-NODE (including the source BH-RAN-NODE and the target BH-RAN-NODE) ​​or WAB-gNB can be a radio access network (RAN) node in a communication system. For example, the BH-RAN-NODE or WAB-gNB can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), or a next-generation NodeB (gNB) in a future communication network. For instance, the BH-RAN-NODE or WAB-gNB can be a macro base station, a micro base station, an indoor station, a relay node, a donor node, or a radio controller in a CRAN scenario. Optionally, the BH-RAN-NODE or WAB-gNB can also be a server, a wearable device, a vehicle, or in-vehicle equipment. For example, network equipment or RAN nodes in vehicle-to-everything (V2X) technology can be roadside units (RSUs). All or part of the functions of the BH-RAN-NODE or WAB-gNB in ​​this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The BH-RAN-NODE or WAB-gNB in ​​this application can also be a logical node, logical module, or software capable of implementing all or part of the functions of the BH-RAN-NODE or WAB-gNB.

[0098] In another possible scenario, multiple radio access network (RAN) nodes can collaborate to implement the functions of BH-RAN-NODE or WAB-gNB, with different RAN nodes implementing a portion of the functions of BH-RAN-NODE or WAB-gNB. For example, a RAN node can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). Optionally, a central unit can also be called a control unit.

[0099] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0100] The CU and DU can be configured according to the protocol layer functions of the wireless network they implement: for example, the CU can be configured to implement the functions of the Packet Data Convergence Protocol (PDCP) layer and above (such as the Radio Resource Control (RRC) layer and / or the Service Data Adaptation Protocol (SDAP) layer); the DU can be configured to implement the functions of the protocol layers below the PDCP layer (such as the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and / or the Physical (PHY) layer). Alternatively, the CU can be configured to implement the functions of the protocol layers above the PDCP layer (such as the RRC and / or SDAP layers), and the DU can be configured to implement the functions of the protocol layers below the PDCP layer (such as the RLC, MAC, and / or PHY layers).

[0101] In the embodiments of this application, the functions of the RAN node can be executed by modules (such as chips) within the RAN node, or by a control subsystem that includes RAN node functions. For example, a control subsystem that includes RAN node functions can be a control center in application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities.

[0102] In one possible implementation, in the O-RAN architecture, BH-RAN-NODE can include BH-RAN-NODE-CU and BH-RAN-NODE-DU, and WAB-gNB can include WAB-gNB-CU and WAB-gNB-DU.

[0103] In one possible implementation, the RAN Intelligent Controller (RIC) can control the BH-RAN-NODE and WAB-gNB. The RIC has E2 interfaces with both the BH-RAN-NODE and WAB-gNB, and communicates with them through these interfaces. For example, the RIC can act as a centralized control node. Xn messages between the BH-RAN-NODE (including the source and destination BH-RAN-NODE) ​​and the WAB-gNB can be forwarded through the RIC's E2 interface, as can Xn messages between the source and destination BH-RAN-NODE.

[0104] For example, Figure 4 shows a schematic diagram of another system architecture to which this application can be applied. As shown in Figure 4, in the O-RAN architecture, BH-RAN-NODE includes BH-RAN-NODE-CU and BH-RAN-NODE-DU, and WAB-gNB includes WAB-CU (which can also be described as WAB-gNB-CU) and WAB-CU (which can also be described as WAB-gNB-DU). The RIC has E2 interfaces with BH-RAN-NODE-CU, BH-RAN-NODE-DU, WAB-CU, and WAB-DU respectively. Through the E2 interfaces, the RIC can control BH-RAN-NODE-CU, BH-RAN-NODE-DU, WAB-CU, and WAB-DU. For example, Xn messages between BH-RAN-NODE-CU (including the source BH-RAN-NODE-CU and the target BH-RAN-NODE-CU) and WAB-CU can be forwarded through the E2 interfaces of the RIC. Xn messages between the source BH-RAN-NODE-CU and the destination BH-RAN-NODE-CU can also be forwarded through the E2 interface of the RIC.

[0105] It should be understood that the system architectures shown in Figures 3 and 4 are merely exemplary and should not impose any limitations on the communication system or system architecture applicable to the embodiments of this application. For example, the communication system shown in Figure 3 may include more or fewer network nodes, such as WAB-gNB, BH-RAN-NODE, or WAB-MT. As another example, the WAB-gNB or BH-RAN-NODE included in the communication architecture shown in Figure 3 may be various forms of RAN nodes as described above. The embodiments of this application are not shown one by one in the figures.

[0106] The following section uses specific examples to illustrate the communication method provided in this application.

[0107] It should be understood that in the examples below, BH-RAN-NODE (including source BH-RAN-NODE and target BH-RAN-NODE), WAB-gNB, and WAB-MT are used as examples to illustrate the method. As an example and not a limitation, the execution subject of the communication method provided in this application can also be a component (chip, chip system, or processor) that supports BH-RAN-NODE, WAB-gNB, or WAB-MT to implement the method, or it can be a logic module or software capable of implementing all or part of the functions of BH-RAN-NODE, WAB-gNB, or WAB-MT. The embodiments of this application are not limited herein.

[0108] For example, in the example below, the execution body BH-RAN-NODE (including source BH-RAN-NODE and target BH-RAN-NODE) ​​can be replaced with BH-RAN-NODE-CU (including source BH-RAN-NODE-CU and BH-RAN-NODE-CU), and WAB-gNB can also be replaced with WAB-CU.

[0109] Figure 5 is a schematic flowchart of a communication method according to an embodiment of this application. This method 500 can be applied to the scenario or communication architecture shown in Figure 3, and of course, it can also be applied to other communication scenarios or communication architectures with the aforementioned technical problems. This application embodiment does not impose any limitations here. In the example shown in Figure 5, the target BH-RAN-NODE first obtains the relevant information of WAB-gNB. For example, the handover request of WAB-MT carries the relevant information of WAB-gNB. After obtaining the relevant information of WAB-gNB, the target BH-RAN-NODE can establish an Xn interface with WAB-gNB and perform resource reuse, which can realize resource reuse by the target BH-RAN-NODE before sending the handover command to WAB-MT.

[0110] As shown in Figure 5, the method 500 illustrated in Figure 5 may include steps S501 to S509. The steps in method 500 are described in detail below with reference to Figure 5. The steps indicated by dashed lines are optional.

[0111] S501, the source BH-RAN-NODE determines the binding relationship between WAB-gNB and WAB-MT. Here, WAB-MT is the WAB-MT that needs to be switched, and the source BH-RAN-NODE can be understood as the source backhaul access network node for the switch of this WAB-MT.

[0112] Since a binding or correspondence can exist between a WAB-gNB and a WAB-MT, and a BH-RAN-NODE can associate with or schedule multiple WAB-MTs, during resource reuse, the BH-RAN-NODE needs to know which WAB-MT's time-domain resources it schedules and which WAB-gNB's time-domain resources are offset. Therefore, the BH-RAN-NODE needs to know the association or binding relationship between WAB-MTs and WAB-gNBs in order to reuse resources for them, ensuring that the WAB-gNB and WAB-MT nodes are offset in the time domain. For example, if a WAB node includes a first WAB-gNB and a first WAB-MT, and the source BH-RAN-NODE can schedule the first WAB-MT, then the source BH-RAN-NODE determines that there is a binding or association relationship between the first WAB-gNB and the first WAB-MT, and needs to reuse resources for the first WAB-MT and the first WAB-gNB.

[0113] In one possible implementation, the WAB-MT can send an RRC message to the source BH-RAN-NODE via the Uu interface. The RRC message can carry the identifier of the WAB-gNB associated with or bound to the WAB-MT. In this case, the source BH-RAN-NODE can determine the binding or association relationship between the WAB-gNB and the WAB-MT based on the identifier of the WAB-MT that sent the RRC message and the identifier of the WAB-gNB.

[0114] In one possible implementation, the WAB-gNB can send an Xn message to the source BH-RAN-NODE via the Xn interface (communication interface) between itself and the source BH-RAN-NODE. The Xn message can carry the identifier of the WAB-MT associated with or bound to the WAB-gNB. In this case, the source BH-RAN-NODE can determine the binding relationship between the WAB-gNB and the WAB-MT based on the identifier of the WAB-gNB that sent the Xn message and the identifier of the WAB-MT.

[0115] It should be understood that, in the embodiments of this application, the source BH-RAN-NODE can also determine which WAB-gNB the WAB-MT to be switched is associated with through other means, or in other words, the source BH-RAN-NODE can also obtain the association or binding relationship between WAB-MT and WAB-gNB through other means, and the embodiments of this application do not impose any restrictions here.

[0116] S502, the WAB-MT or WAB-gNB sends second information to the source BH-RAN-NODE. This second information includes the first IP address of the WAB-gNB, which may include one or more IP addresses. Correspondingly, the source BH-RAN-NODE receives the second information.

[0117] It should be understood that S502 is an optional step, indicated by a dashed line. That is, method 500 may also exclude S502. If method 500 does not include S502, S503 is executed directly after S501.

[0118] In one possible implementation, the WAB-gNB can send its first IP address to the WAB-MT through an internal interface. The WAB-MT can then send an RRC message to the source BH-RAN-NODE through the Uu interface. The RRC message can carry the first IP address of the WAB-gNB, meaning the second information can be implemented using the RRC message.

[0119] In one possible implementation, the WAB-gNB can send an Xn message to the source BH-RAN-NODE via the Xn interface between the WAB-gNB and the source BH-RAN-NODE. The Xn message can carry the first IP address of the WAB-gNB, that is, the second information can be implemented using the Xn message.

[0120] The first IP address of the WAB-gNB may include one or more IP addresses of the WAB-gNB. For example, the second information includes a list of IP addresses of the WAB-gNB, which includes one or more IP addresses. The one or more IP addresses of the WAB-gNB are ultimately used to establish the Xn interface between the target BH-RAN-NODE and the WAB-gNB. Since the network can assign multiple IP addresses to the WAB-gNB, the IP address used by the WAB-gNB when establishing the Xn interface with each neighboring station (e.g., multiple different BH-RAN-NODEs) can be different. The target BH-RAN-NODE can be understood as the target backhaul access network node for WAB-MT handover.

[0121] In one possible implementation, if the network assigns multiple IP addresses to the WAB-gNB, the WAB-gNB can send its corresponding multiple (or all) IP addresses (e.g., an IP address list) to the source BH-RAN-NODE via a second message, which then further instructs the target BH-RAN-NODE. Finally, the target BH-RAN-NODE selects one of these IP addresses to establish an Xn interface with the WAB-gNB. In this case, the WAB-gNB's first IP address can include multiple IP addresses.

[0122] In one possible implementation, the WAB-gNB can select one of its multiple (or all) corresponding IP addresses, send this IP address to the source BH-RAN-NODE via a second message, and then the source BH-RAN-NODE further instructs the target BH-RAN-NODE. The final target BH-RAN-NODE can then use this IP address to establish an Xn interface with the WAB-gNB. In this case, the first IP address of the WAB-gNB can include a single IP address.

[0123] In one possible implementation, if the WAB-gNB has only one IP address—that is, the network assigns only one IP address to the WAB-gNB—the WAB-gNB can send this IP address to the source BH-RAN-NODE via a second message, and the source BH-RAN-NODE can further instruct the target BH-RAN-NODE. The final target BH-RAN-NODE can then use this IP address to establish an Xn interface with the WAB-gNB. In this case, the WAB-gNB's first IP address can include its unique IP address.

[0124] By sending the first IP address of the WAB-gNB to the source BH-RAN-NODE, the source BH-RAN-NODE can send the first IP address of the WAB-gNB to the target BH-RAN-NODE, which can improve the efficiency and accuracy of establishing the Xn interface between the target BH-RAN-NODE and the WAB-gNB.

[0125] S503, the source BH-RAN-NODE sends first information to the target BH-RAN-NODE. The first information includes at least one of the following: identification information of the WAB-gNB, first resource configuration information of the WAB-gNB, or frequency information of the WAB-gNB, and identification information of the WAB-MT. The first resource configuration information includes the resource configuration of the WAB-gNB. Correspondingly, the target BH-RAN-NODE receives the first information.

[0126] For example, the source BH-RAN-NODE can send the first information to the target BH-RAN-NODE through the Xn interface between the source BH-RAN-NODE and the target BH-RAN-NODE.

[0127] For example, the first information can be carried in a handover request (HO request) sent by the source BH-RAN-NODE to the target BH-RAN-NODE.

[0128] Specifically, the identification information of WAB-MT can be used by the target BH-RAN-NODE to determine whether resource reuse between WAB-MT and WAB-gNB is necessary. In other words, the identification information of WAB-MT indicates a binding or association relationship between WAB-gNB and WAB-MT. The target BH-RAN-NODE can determine which WAB-MT and WAB-gNB are associated based on the identification information of WAB-MT, thereby enabling resource reuse between WAB-MT and WAB-gNB. Specifically, the target BH-RAN-NODE can pass the identification information of WAB-MT to WAB-gNB. In subsequent steps, WAB-gNB sends the identification information of WAB-MT to the target BH-RAN-NODE, enabling the target BH-RAN-NODE to determine the binding or association relationship between WAB-MT and WAB-gNB.

[0129] For example, the identification information of WAB-MT may include: the identifier of WAB-MT on the communication interface (Xn interface) between the target BH-RAN-NODE and the source BH-RAN-NODE. For instance, the identification information of WAB-MT may be: the "UE XnAP ID" of WAB-MT on the Xn interface between the source BH-RAN-NODE and the target BH-RAN-NODE, or the "UE XnAP ID" on the target BH-RAN-NODE side. The UE XnAP ID corresponding to WAB-MT is recognizable or understandable by both the target BH-RAN-NODE and the source BH-RAN-NODE; in other words, both the target BH-RAN-NODE and the source BH-RAN-NODE can determine the WAB-MT based on the "UE XnAP ID".

[0130] The identification information of the WAB-gNB may include: at least one IP address corresponding to the WAB-gNB, and / or, the base station identifier of the WAB-gNB (i.e., the gNB ID of the WAB-gNB). The at least one IP address corresponding to the WAB-gNB can be used to establish an Xn interface between the WAB-gNB and the target BH-RAN-NODE.

[0131] In one possible implementation, if method 500 includes S502, then at least one IP address corresponding to WAB-gNB may include one or more IP addresses of WAB-gNB sent by WAB-MT or WAB-gNB to the source BH-RAN-NODE in S502. That is, at least one IP address corresponding to WAB-gNB includes: a list of IP addresses of WAB-gNB or an IP address selected by WAB-gNB.

[0132] In one possible implementation, if method 500 includes S502, and the source BH-RAN-NODE obtains multiple IP addresses corresponding to WAB-gNB, then the source BH-RAN-NODE can select one IP address from the multiple IP addresses. That is, at least one IP address corresponding to WAB-gNB includes: the IP address selected by the source BH-RAN-NODE from the multiple IP addresses corresponding to WAB-gNB.

[0133] In one possible implementation, if method 500 does not include S502, then the source BH-RAN-NODE can send the IP address of the WAB-gNB on the Xn interface used between the source BH-RAN-NODE and the target BH-RAN-NODE. That is, at least one IP address corresponding to the WAB-gNB includes the IP address of the WAB-gNB on the Xn interface used between the source BH-RAN-NODE and the target BH-RAN-NODE. The IP address of the WAB-gNB on the Xn interface used between the source BH-RAN-NODE and the target BH-RAN-NODE can be used to establish the Xn interface between the target BH-RAN-NODE and the WAB-gNB.

[0134] In summary, the identification information of the WAB-gNB, including at least one IP address corresponding to the WAB-gNB, may include: a single IP address corresponding to the WAB-gNB, multiple IP addresses corresponding to the WAB-gNB, or the IP address of the WAB-gNB used on the Xn interface between the WAB-gNB and the source BH-RAN-NODE. The single IP address corresponding to the WAB-gNB may be one of the multiple IP addresses corresponding to the WAB-gNB (selected by the WAB-gNB or the source BH-RAN-NODE), or it may be the unique IP address of the WAB-gNB.

[0135] The base station identifier of the WAB-gNB (i.e., the gNB ID of the WAB-gNB) can be used by the target BH-RAN-NODE to determine whether an Xn interface already exists between it and the WAB-gNB. After establishing an Xn interface with a WAB-gNB, the target BH-RAN-NODE can save the base station identifier of that WAB-gNB.

[0136] The first resource configuration information of the WAB-gNB can be understood as the resource configuration information when the WAB-gNB schedules the UE. Optionally, the resource configuration when the WAB-gNB schedules the UE can also be described as the resource configuration of the WAB-gNB. The first resource configuration information of the WAB-gNB may include the frequency information and time-domain information of the WAB-gNB. For example, the frequency information of the WAB-gNB may include: the frequency information (e.g., operating frequency point) when the WAB-gNB schedules the UE. The time-domain information of the WAB-gNB may include: time slot configuration information when the WAB-gNB schedules the UE, etc.

[0137] The frequency information of the WAB-gNB can include the operating frequency of the WAB-gNB when scheduling the UE. It can be understood that the first resource configuration information of the WAB-gNB can include the frequency information of the WAB-gNB. For example, the frequency information of the WAB-gNB can include the operating frequency point of the WAB-gNB, that is, the operating frequency point of the WAB-gNB when scheduling the UE. The frequency information of the WAB-gNB can be used by the target BH-RAN-NODE to determine whether the WAB-MT will have the same operating frequency point as the WAB-gNB after handover, that is, whether the WAB-MT will operate in in-band mode with the WAB-gNB after handover.

[0138] By utilizing the information included in the first part of the information, the efficiency of resource reuse between the target BH-RAN-NODE and WAB-gNB can be improved.

[0139] S504, the target BH-RAN-NODE determines whether a communication interface (Xn interface) exists between it and WAB-gNB based on the first information.

[0140] In one possible implementation, if the first information includes at least one IP address corresponding to the WAB-gNB (e.g., a list of WAB-gNB IP addresses or the unique IP address of the WAB-gNB), but does not include the base station identifier of the WAB-gNB, then the target BH-RAN-NODE can determine whether it has established an Xn interface with the WAB-gNB based on the at least one IP address corresponding to the WAB-gNB. Since the target BH-RAN-NODE needs to use one of the base station's IP addresses when establishing an Xn interface with each base station, the target BH-RAN-NODE can obtain the IP addresses used by all base stations with which it has already established an Xn interface. If one of the IP addresses used by all base stations with which an Xn interface has been established is included in the at least one IP address corresponding to the WAB-gNB, then it proves that the target BH-RAN-NODE has established an Xn interface with the WAB-gNB. Otherwise, the target BH-RAN-NODE has not yet established an Xn interface with the WAB-gNB (or it cannot be determined whether the target BH-RAN-NODE has established an Xn interface with the WAB-gNB).

[0141] In one possible implementation, if the first information includes the base station identifier of the WAB-gNB, regardless of whether it includes at least one IP address corresponding to the WAB-gNB, then the target BH-RAN-NODE can determine whether an Xn interface has been established with the WAB-gNB based on the base station identifier. Since the target BH-RAN-NODE can save the base station identifier of a base station after establishing an Xn interface, it can obtain the base station identifiers corresponding to all base stations with which it has established Xn interfaces. If the base station identifiers of all base stations with established Xn interfaces include the base station identifier of the WAB-gNB, then it proves that the target BH-RAN-NODE has established an Xn interface with the WAB-gNB. Otherwise, the target BH-RAN-NODE has not yet established an Xn interface with the WAB-gNB.

[0142] In one possible implementation, if the first information does not include the identification information of the WAB-gNB, that is, it does not include at least one IP address corresponding to the WAB-gNB and the base station identifier of the WAB-gNB, then the target BH-RAN-NODE cannot determine whether an Xn interface has been established with the WAB-gNB.

[0143] In one possible implementation, if the first information includes the frequency information of the WAB-gNB, then the target BH-RAN-NODE can determine whether the operating frequency of the WAB-gNB and the operating frequency of the WAB-MT are the same based on the WAB-gNB's frequency information. The operating frequency of the WAB-MT can be understood as the operating frequency of the target BH-RAN-NODE when scheduling the WAB-MT after it has switched to the BH-RAN-NODE.

[0144] In one possible implementation, if it is determined that the operating frequency of WAB-gNB and WAB-MT are the same, meaning that WAB-MT will operate in in-band mode with WAB-gNB after handover, then the target BH-RAN-NODE only needs to determine whether an Xn interface exists with WAB-gNB based on the first information. In other words, only in this case is it necessary to execute steps S504 and subsequent steps of method 500.

[0145] In one possible implementation, if it is determined that the operating frequency of WAB-gNB and WAB-MT are different, i.e., WAB-MT will operate in out-band mode with WAB-gNB after handover, then the target BH-RAN-NODE does not need to determine whether an Xn interface exists with WAB-gNB, or the target BH-RAN-NODE does not need to perform resource reuse. In other words, in this case, steps S504 and subsequent steps of method 500 do not need to be executed.

[0146] Determining whether a communication interface exists between the target BH-RAN-NODE and WAB-gNB avoids redundantly establishing communication interfaces when they already exist, reducing the consumption of communication resources and improving the utilization rate of communication resources.

[0147] S505, if the target BH-RAN-NODE is determined to have no Xn interface with WAB-gNB, an Xn interface is established between the target BH-RAN-NODE and WAB-gNB.

[0148] It should be understood that S505 is an optional step, meaning that method 500 may not include S505. For example, if the target BH-RAN-NODE determines that a communication interface (Xn interface) already exists between it and the WAB-gNB, or if the WAB-MT operates in out-band mode after handover, or if the first information does not include the identification information of the WAB-gNB, then method 500 may not include S505. If method 500 does not include S505, then S506 is executed directly after S504.

[0149] In one possible implementation, if the first information includes at least one IP address corresponding to WAB-gNB, and the target BH-RAN-NODE determines that there is no Xn interface between it and WAB-gNB, the target BH-RAN-NODE can establish an Xn interface with WAB-gNB using at least one IP address corresponding to WAB-gNB. For example, the target BH-RAN-NODE can establish an Xn interface with WAB-gNB using any one of the multiple IP addresses corresponding to WAB-gNB, or the target BH-RAN-NODE can establish an Xn interface with WAB-gNB using one IP address corresponding to WAB-gNB. This IP address can be: the IP address of WAB-gNB used for the Xn interface between it and the source BH-RAN-NODE; an IP address selected by WAB-gNB or the source BH-RAN-NODE from the list of IP addresses of WAB-gNB; or the unique IP address of WAB-gNB. By using the first information, including at least one IP address corresponding to WAB-gNB and the target BH-RAN-NODE, to establish a communication interface, the efficiency of establishing a communication interface can be improved.

[0150] In one possible implementation, if the first information does not include at least one IP address corresponding to WAB-gNB, and the target BH-RAN-NODE determines that there is no Xn interface between it and WAB-gNB, the target BH-RAN-NODE can also obtain the IP address of WAB-gNB through other means. After obtaining the IP address of WAB-gNB, the target BH-RAN-NODE can then establish an Xn interface with WAB-gNB using the WAB-gNB's IP address.

[0151] S506, if the first information does not include the first resource configuration information of WAB-gNB, the target BH-RAN-NODE sends a request message to WAB-gNB through the Xn interface. The request message is used to request the first resource configuration information.

[0152] It should be understood that S506 is an optional step, meaning that method 500 may also exclude S506.

[0153] For example, if the first information includes the first resource configuration information of WAB-gNB, method 500 may not include S506.

[0154] For example, if the target BH-RAN-NODE determines that WAB-MT will operate in out-band mode with WAB-gNB after the handover, method 500 may or may not include S506.

[0155] It should be understood that the request message in S506 also needs to carry the identification information of WAB-MT.

[0156] In one possible implementation, if the first information does not include the identification information of the WAB-gNB, and also does not include the first resource configuration information of the WAB-gNB, then the target BH-RAN-NODE cannot determine whether an Xn interface has been established with the WAB-gNB, and therefore cannot send a request message to the WAB-gNB through the Xn interface. Thus, in one possible implementation, the target BH-RAN-NODE can send the request information to the source BH-RAN-NODE, which then sends the request information to the WAB-gNB. For example, the source BH-RAN-NODE can send the request information to the WAB-gNB through the RRC message of the WAB-MT, or through the Xn message of the WAB-gNB.

[0157] S507, in response to the request message, WAB-gNB sends the first resource configuration information to the target BH-RAN-NODE through the Xn interface.

[0158] It should be understood that S507 is an optional step, meaning that method 500 may also exclude S507. For example, if the first information includes the first resource configuration information of the WAB-gNB, or if the target BH-RAN-NODE determines that the WAB-MT will operate in out-band mode with the WAB-gNB after the handover, method 500 may exclude S507.

[0159] It should be understood that the first resource configuration information sent by the WAB-gNB to the target BH-RAN-NODE also needs to carry the identification information of the WAB-MT, or the WAB-gNB also needs to send the identification information of the WAB-MT to the target BH-RAN-NODE through the Xn interface.

[0160] In one possible implementation, if the target BH-RAN-NODE sends the request information to the WAB-gNB via the source BH-RAN-NODE, or in other words, the WAB-gNB cannot send the first resource configuration information to the target BH-RAN-NODE via the Xn interface, then in one possible implementation, the WAB-gNB can send the first resource configuration information to the source BH-RAN-NODE via the Xn interface between itself and the source BH-RAN-NODE, and the source BH-RAN-NODE can send the first resource configuration information to the target BH-RAN-NODE via the Xn interface between itself and the target BH-RAN-NODE. In another possible implementation, the WAB-gNB can send the first resource configuration information to the WAB-MT via an internal interface, the WAB-MT can send the first resource configuration information to the source BH-RAN-NODE via an RRC message, and then the source BH-RAN-NODE can send the first resource configuration information to the target BH-RAN-NODE via the Xn interface between itself and the target BH-RAN-NODE. Similarly... The WAB-gNB can send the WAB-MT identification information to the target BH-RAN-NODE in the manner described above.

[0161] Sending the first resource configuration information to the target BH-RAN-NODE via the communication interface can improve the efficiency and accuracy of the first resource configuration information transmission.

[0162] S508, the target BH-RAN-NODE sends the second resource configuration information to WAB-gNB, WAB-MT, or the source BH-RAN-NODE according to the first resource configuration information. The second resource configuration information is used for resource reuse between WAB-gNB and WAB-MT.

[0163] It should be understood that S508 is an optional step, meaning that method 500 may not include S508. For example, if the target BH-RAN-NODE determines that WAB-MT and WAB-gNB will operate in out-band mode after the handover, method 500 may not include S508. Sending the second resource configuration information only after determining that the target BH-RAN-NODE determines that WAB-MT and WAB-gNB will operate in in-band mode after the handover, i.e., performing resource reuse, can avoid useless resource reuse, reduce communication resource consumption, and improve the accuracy and efficiency of resource reuse.

[0164] After the target BH-RAN-NODE obtains the first resource configuration information, it can determine the second resource configuration information based on the first resource configuration information. There are three possible implementation methods:

[0165] Possible Implementation Method 1: The second resource configuration information includes the resource configuration that WAB-gNB needs to adjust. Since the scheduling of WAB-gNB and WAB-MT needs to be staggered in the time domain, when WAB-MT is in handover mode and WAB-gNB is operating in in-band mode, the target BH-RAN-NODE can determine which WAB-MT is bound to based on the WAB-MT's identification information. After determining the WAB-MT, it can determine the resource configuration that WAB-gNB needs to adjust based on the WAB-MT's post-handover resource configuration (e.g., time-domain resource configuration) and the WAB-gNB's resource configuration (i.e., the first resource configuration information). Since this WAB-MT needs to handover to the target BH-RAN-NODE, the target BH-RAN-NODE can determine the WAB-MT's post-handover resource configuration. Specifically, the resource configuration adjustments required by the WAB-gNB must satisfy the following: after the handover of the WAB-MT, the resource configuration adjustments required by the WAB-gNB must be time-domain staggered from the time-domain resources of the WAB-MT. That is, the scheduling of the WAB-gNB and the WAB-MT must be time-domain staggered, and the adjusted resource configuration is used for resource reuse between the WAB-gNB and the WAB-MT. In this case, the target BH-RAN-NODE can send the second resource configuration information to the WAB-gNB via the Xn interface.

[0166] If the target BH-RAN-NODE cannot determine whether an Xn interface has been established with the WAB-gNB, or if no Xn interface has been established, then the target BH-RAN-NODE cannot send the second resource configuration information to the WAB-gNB via the Xn interface. In one possible implementation, the target BH-RAN-NODE can send the second resource configuration information to the source BH-RAN-NODE, which then sends it to the WAB-gNB. For example, the source BH-RAN-NODE can send the second resource configuration information to the WAB-gNB via an RRC message from the WAB-MT, or via an Xn message from the WAB-gNB.

[0167] A possible implementation method two: The second resource configuration information includes the resource configuration of WAB-MT. Since it is necessary to ensure that the scheduling of WAB-gNB and WAB-MT is staggered in the time domain, after WAB-MT handover and when WAB-gNB is operating in in-band mode, the target BH-RAN-NODE can determine which WAB-MT is bound to by WAB-gNB based on the identification information of WAB-MT. After determining the WAB-MT, the resource configuration of WAB-MT can be determined based on the resource configuration of WAB-gNB (i.e., the first resource configuration information). Here, the resource configuration of WAB-MT can be understood as: the resource configuration of WAB-MT after handover to the target BH-RAN-NODE, that is, the resource configuration when the target BH-RAN-NODE schedules WAB-MT. Specifically, the resource configuration of WAB-MT needs to meet the following requirements: after WAB-MT switches to the target BH-RAN-NODE, the time-domain resources of WAB-gNB and WAB-MT are staggered in the time domain. That is, the scheduling of WAB-gNB and WAB-MT is staggered in the time domain, and the resource configuration of WAB-MT is used for resource reuse between WAB-gNB and WAB-MT. In this case, the target BH-RAN-NODE can send the second resource configuration information to WAB-gNB through the Xn interface, and WAB-gNB can forward the second resource configuration information to WAB-MT through its internal interface.

[0168] If the target BH-RAN-NODE cannot determine whether an Xn interface has been established with the WAB-gNB, or if no Xn interface has been established, the target BH-RAN-NODE cannot send the second resource configuration information to the WAB-gNB through the Xn interface. In one possible implementation, the target BH-RAN-NODE can send the second resource configuration information to the source BH-RAN-NODE, carrying the identification information of the WAB-MT. The source BH-RAN-NODE then sends the second resource configuration information to the WAB-MT via an RRC message based on the WAB-MT's identification information. Alternatively, the source BH-RAN-NODE can send the second resource configuration information to the WAB-gNB associated with the WAB-MT via the WAB-gNB's Xn message based on the WAB-MT's identification information. The WAB-gNB then forwards the second resource configuration information to the WAB-MT through its internal interface.

[0169] Possible Implementation Method 3: The second resource configuration information includes the resource configuration of the target BH-RAN-NODE. The resource configuration of the target BH-RAN-NODE can be understood as the resource configuration when the target BH-RAN-NODE schedules the WAB-MT (i.e., the resource configuration of the WAB-MT after handover). Since it is necessary to ensure that the scheduling of the WAB-gNB and WAB-MT is staggered in the time domain, after the handover of the WAB-MT and when the WAB-gNB is operating in in-band mode, the target BH-RAN-NODE can determine which WAB-MT the WAB-gNB is bound to based on the identification information of the WAB-MT, i.e., determine the binding relationship between the WAB-gNB and the WAB-MT. Then, the target BH-RAN-NODE can send the second resource configuration information to the WAB-gNB through the Xn interface. After receiving the second resource configuration information, the WAB-gNB determines the resource configuration that the WAB-gNB needs to adjust based on the resource configuration of the target BH-RAN-NODE and the first resource configuration information. Specifically, the resource configuration adjustments required by the WAB-gNB must satisfy the following: after the WAB-MT switches to the target BH-RAN-NODE, the resource configuration adjustments required by the WAB-gNB are time-domain staggered from the time-domain resources of the WAB-MT. That is, the scheduling of the WAB-gNB and the WAB-MT is time-domain staggered, and the adjusted resource configuration is used for resource reuse between the WAB-gNB and the WAB-MT. In this case, the target BH-RAN-NODE can send the second resource configuration information to the WAB-gNB via the Xn interface.

[0170] If the target BH-RAN-NODE cannot determine whether an Xn interface has been established with the WAB-gNB, or if no Xn interface has been established, then the target BH-RAN-NODE cannot send the second resource configuration information to the WAB-gNB via the Xn interface. In one possible implementation, the target BH-RAN-NODE can send the second resource configuration information to the source BH-RAN-NODE, carrying the identification information of the WAB-MT. The source BH-RAN-NODE, based on the WAB-MT's identification information, determines the WAB-gNB associated with the WAB-MT and sends the second resource configuration information to the WAB-gNB via the WAB-gNB's Xn message. Alternatively, the source BH-RAN-NODE can send the second resource configuration information to the WAB-MT via an RRC message, and the WAB-MT can then send the second resource configuration information to the WAB-gNB via its internal interface.

[0171] It should be understood that all steps included in method 500 can occur before the target BH-RAN-NODE sends the handover command to WAB-MT, i.e., before WAB-MT performs the handover. Alternatively, all steps included in method 500 can occur during the process of the target BH-RAN-NODE sending the handover command to WAB-MT.

[0172] For example, in some possible implementations, the second resource configuration information sent by the target BH-RAN-NODE to WAB-MT in S508 can be carried in the handover command sent by the target BH-RAN-NODE to WAB-MT. After WAB-MT receives the second resource configuration information, it can switch from the source BH-RAN-NODE to the target BH-RAN-NODE according to the handover command.

[0173] [Corrected according to detailed rule 91, 30.04.2026] For example, in some possible implementations, as shown in Figure 5, optionally, after S508, method 500 may also include S509, whereby the target BH-RAN-NODE sends a handover command to the WAB-MT, the handover command instructing the WAB-MT to hand over from the source BH-RAN-NODE to the target BH-RAN-NODE. Sending the handover command after sending the second resource configuration information ensures that the target BH-RAN-NODE can reuse resources based on the WAB-gNB information and the WAB-gNB before the WAB-MT hands over to the target BH-RAN-NODE. This enables resource reuse between the WAB-gNB and the target BH-RAN-NODE as early as possible, reducing potential interference and service experience degradation during the WAB-MT handover process.

[0174] For example, the target BH-RAN-NODE can send a handover command to the WAB-MT through the source BH-RAN-NODE. After receiving the handover command, the WAB-MT can switch from the source BH-RAN-NODE to the target BH-RAN-NODE.

[0175] The communication method provided in this application allows the target BH-RAN-NODE to obtain information about the WAB-gNB bound to the WAB-MT before or during the WAB-MT handover. The target BH-RAN-NODE can then reuse resources with the WAB-gNB based on this information. For example, the target BH-RAN-NODE can establish an Xn interface with the WAB-gNB based on the WAB-gNB information and utilize this interface for resource reuse. This enables early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT handover process and ensuring communication efficiency.

[0176] Figure 6 is a schematic flowchart of a communication method according to another embodiment of this application. In the example shown in Figure 6, the target BH-RAN-NODE of the WAB-MT handover can send its own information to the WAB-gNB bound to the WAB-MT. Based on the information of the target BH-RAN-NODE obtained, the WAB-gNB can establish an Xn interface with the target BH-RAN-NODE and perform resource reuse. This realizes resource reuse between the target BH-RAN-NODE and the WAB-gNB before the WAB-MT handover to the target BH-RAN-NODE, thereby enabling resource reuse between the WAB-gNB and the target BH-RAN-NODE as early as possible.

[0177] As shown in Figure 6, method 600 may include steps S601 to S608. The steps in method 600 are described in detail below with reference to Figure 6. The steps indicated by dashed lines are optional.

[0178] S601, the source BH-RAN-NODE sends a handover request to the target BH-RAN-NODE, requesting that WAB-MT need to hand over to the target BH-RAN-NODE. Correspondingly, the target BH-RAN-NODE receives the handover request. Here, WAB-MT is the WAB-MT that needs to be handed over, the source BH-RAN-NODE is the source backhaul access network node for the WAB-MT handover, and the target BH-RAN-NODE is the target backhaul access network node for the WAB-MT handover.

[0179] For example, the source BH-RAN-NODE can send a handover request message about WAB-MT to the target BH-RAN-NODE through the Xn interface, carrying WAB type indication information (such as a dedicated slice identifier for WAB, etc.). The target BH-RAN-NODE can determine that the UE to be handed over is a WAB-MT based on the handover request message.

[0180] For example, the handover request message of WAB-MT may include the identification information of WAB-MT, such as the "UE XnAP ID" of WAB-MT on the Xn interface between the source BH-RAN-NODE and the target BH-RAN-NODE at the source BH-RAN-NODE.

[0181] Optionally, in this embodiment of the application, the switching request may also be described as a switching request message or switching request information.

[0182] S602, the target BH-RAN-NODE sends a handover command to the WAB-MT through the source BH-RAN-NODE. The handover command includes the first identification information of the target BH-RAN-NODE and the identification information of the WAB-MT. The handover command instructs the WAB-MT to switch from the source BH-RAN-NODE to the target BH-RAN-NODE. Correspondingly, the WAB-MT receives the handover command.

[0183] For example, the target BH-RAN-NODE can first send a handover command to the source BH-RAN-NODE, and the source BH-RAN-NODE can forward the handover command to the WAB-MT.

[0184] The identification information of WAB-MT indicates the binding or association relationship between WAB-gNB and WAB-MT (or in other words, a binding or association relationship exists between WAB-gNB and WAB-MT). The target BH-RAN-NODE can determine which WAB-MT and WAB-gNB are associated based on the identification information of WAB-MT, thus enabling resource reuse between WAB-MT and WAB-gNB. Specifically, WAB-MT can pass its identification information to WAB-gNB. In subsequent steps, WAB-gNB sends the identification information of WAB-MT to the target BH-RAN-NODE, allowing the target BH-RAN-NODE to determine the binding or association relationship between WAB-MT and WAB-gNB.

[0185] In one possible implementation, the identification information of the WAB-MT may include: the Cell Radio Network Temporary Identifier (C-RNTI) of the WAB-MT within the cell served by the target BH-RAN-NODE, and / or, the identification of the WAB-MT on the communication interface between the target BH-RAN-NODE and the source BH-RAN-NODE.

[0186] The target BH-RAN-NODE can determine the C-RNTI of WAB-MT within the cell served by the target BH-RAN-NODE after WAB-MT switches to it. Optionally, if the identification information of WAB-MT includes the C-RNTI, the identification information of WAB-MT may further include: the identifier of the target cell of WAB-MT, that is, the cell ID serving WAB-MT under the target BH-RAN-NODE.

[0187] By utilizing the identification information of WAB-MT, the target BH-RAN-NODE can determine the binding or association relationship between WAB-MT and WAB-gNB, thereby ensuring that the target BH-RAN-NODE can correctly reuse resources, ensuring that resource reuse can proceed normally, and guaranteeing the efficiency and accuracy of resource reuse.

[0188] For example, the identifier of WAB-MT on the communication interface (Xn interface) between the target BH-RAN-NODE and the source BH-RAN-NODE may include: the "UE XnAP ID" of WAB-MT on the Xn interface between the source BH-RAN-NODE and the target BH-RAN-NODE, or the "UE XnAP ID" on the target BH-RAN-NODE side. The UE XnAP ID corresponding to WAB-MT is recognizable or understandable by both the target BH-RAN-NODE and the source BH-RAN-NODE, and both can determine the WAB-MT based on the "UE XnAP ID".

[0189] In one possible implementation, the first identification information of the target BH-RAN-NODE may include: at least one IP address corresponding to the target BH-RAN-NODE, and / or, the base station identifier of the target BH-RAN-NODE (i.e., the gNB ID of the target BH-RAN-NODE). The at least one IP address corresponding to the WAB-gNB can be used to establish an Xn interface between the WAB-gNB and the target BH-RAN-NODE.

[0190] For example, at least one IP address corresponding to the target BH-RAN-NODE may include: multiple IP addresses corresponding to the target BH-RAN-NODE (e.g., a list of IP addresses), or an IP address selected by the target BH-RAN-NODE from among its multiple corresponding IP addresses.

[0191] The base station identifier of the target BH-RAN-NODE (the gNB ID of the target BH-RAN-NODE) ​​can be used by the WAB-gNB to determine whether an Xn interface already exists between it and the target BH-RAN-NODE. After establishing an Xn interface with a BH-RAN-NODE, the WAB-gNB can save the base station identifier of that BH-RAN-NODE.

[0192] S603, WAB-MT sends the information in the handover command to WAB-gNB. Correspondingly, WAB-gNB receives the information in the handover command. The information in the handover command includes: the first identification information of the target BH-RAN-NODE and the identification information of WAB-MT.

[0193] For example, WAB-MT can forward information from the handover command to WAB-gNB through its internal interface.

[0194] By transmitting the information in the handover command to the WAB-gNB, the WAB-gNB can establish an Xn interface with the target BH-RAN-NODE based on this information, thereby enabling resource reuse. This ensures that resource reuse can proceed normally and guarantees its efficiency.

[0195] S604, WAB-gNB determines whether a communication interface (Xn interface) exists between itself and the target BH-RAN-NODE based on the information in the handover command.

[0196] In one possible implementation, if the handover command includes at least one IP address corresponding to the target BH-RAN-NODE (e.g., a list of IP addresses for the target BH-RAN-NODE or a specific IP address corresponding to the target BH-RAN-NODE), but does not include the base station identifier of the target BH-RAN-NODE, then the WAB-gNB can determine whether an Xn interface has been established with the target BH-RAN-NODE based on at least one IP address corresponding to the target BH-RAN-NODE. Since the WAB-gNB needs to use one IP address of each BH-RAN-NODE when establishing an Xn interface, the WAB-gNB can obtain the IP addresses used by all BH-RAN-NODEs with which it has already established an Xn interface. If one of the IP addresses used by all BH-RAN-NODEs with which an Xn interface has been established is included in at least one IP address corresponding to the target BH-RAN-NODE, then it proves that the WAB-gNB has established an Xn interface with the target BH-RAN-NODE. Otherwise, the WAB-gNB has not established an Xn interface with the target BH-RAN-NODE (or it cannot be determined whether the WAB-gNB has established an Xn interface with the target BH-RAN-NODE).

[0197] In one possible implementation, if the handover command includes the base station identifier of the target BH-RAN-NODE, regardless of whether it includes at least one IP address corresponding to the target BH-RAN-NODE, then the WAB-gNB can determine whether an Xn interface has been established with the target BH-RAN-NODE based on the base station identifier. Since the target WAB-gNB can save the base station identifier of a BH-RAN-NODE after establishing an Xn interface with it, it can obtain the base station identifiers corresponding to all BH-RAN-NODEs with which it has established Xn interfaces. If the base station identifiers of all BH-RAN-NODEs with established Xn interfaces include the base station identifier of the target BH-RAN-NODE, then it proves that the WAB-gNB has established an Xn interface with the target BH-RAN-NODE. Otherwise, the WAB-gNB has not yet established an Xn interface with the target BH-RAN-NODE.

[0198] By utilizing the first identification information of the target BH-RAN-NODE, the efficiency and accuracy of WAB-gNB in ​​determining whether an Xn interface exists between it and the target BH-RAN-NODE can be improved.

[0199] S605, if the WAB-gNB determines that there is no communication interface (Xn interface) between it and the target BH-RAN-NODE, the WAB-gNB establishes an Xn interface with the target BH-RAN-NODE.

[0200] Alternatively, in one possible implementation, if the WAB-gNB cannot determine whether the WAB-gNB has established an Xn interface with the target BH-RAN-NODE, the WAB-gNB can also establish an Xn interface with the target BH-RAN-NODE.

[0201] It should be understood that S605 is an optional step, meaning that method 600 may not include S605. For example, if a communication interface (Xn interface) already exists between WAB-gNB and the target BH-RAN-NODE, method 600 may not include S605. If method 600 does not include S605, S606 is executed directly after S604.

[0202] In one possible implementation, if the switching command includes at least one IP address corresponding to the target BH-RAN-NODE, the WAB-gNB can establish an Xn interface between the target BH-RAN-NODE and the target BH-RAN-NODE using at least one IP address corresponding to the target BH-RAN-NODE. For example, the WAB-gNB can establish an Xn interface between the target BH-RAN-NODE and any one of the multiple IP addresses corresponding to the target BH-RAN-NODE, or the WAB-gNB can establish an Xn interface between the target BH-RAN-NODE and the target BH-RAN-NODE using a single IP address. This IP address can be either an IP address selected by the target BH-RAN-NODE from its list of IP addresses, or a unique IP address of the target BH-RAN-NODE.

[0203] In one possible implementation, if the switching command does not include at least one IP address corresponding to the target BH-RAN-NODE, the WAB-gNB can also obtain the IP address of the target BH-RAN-NODE through other means. After obtaining the IP address of BH-RAN-NODE, the WAB-gNB can establish an Xn interface between the target BH-RAN-NODE and the target BH-RAN-NODE using the IP address of the target BH-RAN-NODE.

[0204] S606, the WAB-gNB sends third information to the target BH-RAN-NODE via the Xn interface. This third information includes the identification information of the WAB-MT and first resource configuration information, whereby the first resource configuration information includes the resource configuration of the WAB-gNB. Correspondingly, the WAB-gNB receives the third information via the communication interface.

[0205] In one possible implementation, the identification information of the WAB-MT may include: the C-RNTI of the WAB-MT in the cell served by the target BH-RAN-NODE, and / or, the identifier of the WAB-MT on the communication interface between the target BH-RAN-NODE and the source BH-RAN-NODE, such as "UE XnAP ID".

[0206] The first resource configuration information of the WAB-gNB can be understood as the resource configuration information when the WAB-gNB schedules the UE. Optionally, the resource configuration when the WAB-gNB schedules the UE can also be described as the resource configuration of the WAB-gNB. The first resource configuration information of the WAB-gNB may include the frequency information and time domain information of the WAB-gNB. For example, the frequency information of the WAB-gNB may include: the frequency information (e.g., operating frequency point) when the WAB-gNB schedules the UE. The time domain information of the WAB-gNB may include: the time slot configuration information when the WAB-gNB schedules the UE, etc.

[0207] S607, the target BH-RAN-NODE sends the second resource configuration information to WAB-gNB, WAB-MT, or the source BH-RAN-NODE according to the first resource configuration information. The second resource configuration information is used for resource reuse between WAB-gNB and WAB-MT.

[0208] After the target BH-RAN-NODE obtains the first resource configuration information, it can determine the second resource configuration information based on the first resource configuration information. There are three possible implementation methods:

[0209] Possible implementation method one: The second resource configuration information includes the resource configuration that WAB-gNB needs to adjust. In this case, the target BH-RAN-NODE can send the second resource configuration information to WAB-gNB through the communication interface (Xn interface). For details, please refer to the corresponding part of S508 in method 500. For the sake of brevity, it will not be repeated here.

[0210] In one possible implementation, if the WAB-gNB cannot determine whether an Xn interface has been established with the target BH-RAN-NODE, or if no Xn interface has been established, the target BH-RAN-NODE can send the second resource configuration information to the source BH-RAN-NODE, which then sends the second resource configuration information to the WAB-gNB. For example, the source BH-RAN-NODE can send the second resource configuration information to the WAB-gNB via an RRC message from the WAB-MT, or via an Xn message from the WAB-gNB.

[0211] Possible implementation method two: The second resource configuration information includes the resource configuration of WAB-MT. In this case, the target BH-RAN-NODE can send the second resource configuration information to WAB-gNB through the Xn interface, and WAB-gNB can forward the second resource configuration information to WAB-MT through its internal interface. For details, please refer to the corresponding part of S508 in method 500. For the sake of brevity, it will not be repeated here.

[0212] In one possible implementation, if the WAB-gNB cannot determine whether an Xn interface has been established with the target BH-RAN-NODE, or if no Xn interface has been established, the target BH-RAN-NODE can also send the second resource configuration information to the source BH-RAN-NODE, carrying the identification information of the WAB-MT. The source BH-RAN-NODE then sends the second resource configuration information to the WAB-MT via an RRC message based on the WAB-MT's identification information. Alternatively, the source BH-RAN-NODE can send the second resource configuration information to the WAB-gNB associated with the WAB-MT via an Xn message from the WAB-gNB, based on the WAB-MT's identification information. The WAB-gNB then forwards the second resource configuration information to the WAB-MT through its internal interface.

[0213] Possible implementation method three: The second resource configuration information includes the resource configuration of the target BH-RAN-NODE. In this case, the target BH-RAN-NODE can send the second resource configuration information to the WAB-gNB via the Xn interface. After receiving the second resource configuration information, the WAB-gNB determines the resource configuration that the WAB-gNB needs to adjust based on the resource configuration of the target BH-RAN-NODE and the first resource configuration information. For details, please refer to the corresponding part of S508 in method 500. For the sake of brevity, it will not be repeated here.

[0214] In one possible implementation, if the WAB-gNB cannot determine whether an Xn interface has been established with the target BH-RAN-NODE, or if no Xn interface has been established, the target BH-RAN-NODE can also send the second resource configuration information to the source BH-RAN-NODE, carrying the identification information of the WAB-MT. The source BH-RAN-NODE, based on the WAB-MT's identification information, determines the WAB-gNB associated with the WAB-MT and sends the second resource configuration information to the WAB-gNB via the WAB-gNB's Xn message. Alternatively, after the source BH-RAN-NODE determines the WAB-gNB associated with the WAB-MT, it can send the second resource configuration information to the WAB-MT via an RRC message, and the WAB-MT sends the second resource configuration information to the WAB-gNB through its internal interface.

[0215] It should be understood that, in the example shown in method 600, after the target BH-RAN-NODE sends a handover command to WAB-MT, WAB-MT will not immediately execute the handover process according to the handover command. Instead, WAB-MT will execute the handover process according to the handover command only after S606 or S607.

[0216] In one possible implementation, after S607 (or possibly after S606), the method 600 may optionally include S608, whereby the WAB-MT sends an access request to the target BH-RAN-NODE, requesting the WAB-MT to access the target BH-RAN-NODE. Correspondingly, the target BH-RAN-NODE receives the access request. That is, the WAB-MT will only execute the handover process according to the handover command after S607 or S606. This ensures that the target BH-RAN-NODE and WAB-gNB can reuse resources before the WAB-MT switches to the target BH-RAN-NODE. This allows for early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT handover process.

[0217] The communication method provided in this application allows the target BH-RAN-NODE to send its information to the WAB-gNB bound to the WAB-MT before the WAB-MT switches to the target BH-RAN-NODE. Based on the acquired information, the WAB-gNB can establish an Xn interface with the target BH-RAN-NODE and utilize this interface for resource reuse. This enables early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT switchover process and ensuring communication efficiency.

[0218] Figure 7 is a schematic flowchart of a communication method according to another embodiment of this application. In the example shown in Figure 7, the target BH-RAN-NODE during WAB-MT handover can send its own information to the WAB-gNB bound to WAB-MT. Based on the information obtained from the target BH-RAN-NODE, WAB-gNB can establish an Xn interface with the target BH-RAN-NODE and perform resource reuse. This enables resource reuse between the target BH-RAN-NODE and WAB-gNB before WAB-MT handover to the target BH-RAN-NODE, thereby allowing WAB-gNB and the target BH-RAN-NODE to perform resource reuse as early as possible.

[0219] As shown in Figure 7, the method 700 illustrated in Figure 7 may include steps S701 to S708. The steps in method 700 are described in detail below with reference to Figure 7. The steps indicated by dashed lines are optional.

[0220] S701, the source BH-RAN-NODE sends a handover request to the target BH-RAN-NODE, requesting that WAB-MT need to hand over to the target BH-RAN-NODE. Accordingly, the target BH-RAN-NODE receives the handover request.

[0221] Wherein, WAB-MT is the WAB-MT that needs to be switched, source BH-RAN-NODE is the source backhaul access network node for the WAB-MT switch, and target BH-RAN-NODE is the target backhaul access network node for the WAB-MT switch.

[0222] For an explanation of S701, please refer to the detailed description of S601 in Method 600. For the sake of brevity, it will not be repeated here.

[0223] S702, the target BH-RAN-NODE sends a handover request response message to the source BH-RAN-NODE. Correspondingly, the source BH-RAN-NODE receives this handover request response message.

[0224] S703, in response to the handover request response message, the source BH-RAN-NODE sends fourth information to WAB-MT or WAB-gNB. This fourth information includes the second identification information of the target BH-RAN-NODE and the identification information of WAB-MT. A binding or association relationship exists between WAB-MT and WAB-gNB.

[0225] For a detailed explanation of the identification information of WAB-MT, please refer to the description in S602 of method 600. For the sake of brevity, it will not be repeated here. Specifically, the source BH-RAN-NODE or WAB-MT can pass the identification information of WAB-MT to WAB-gNB. In subsequent steps, WAB-gNB sends the identification information of WAB-MT to the target BH-RAN-NODE, so that the target BH-RAN-NODE can determine the binding relationship or association relationship between WAB-MT and WAB-gNB.

[0226] The second identification information of the target BH-RAN-NODE may include: the first IP address corresponding to the target BH-RAN-NODE, and / or, the base station identifier of the target BH-RAN-NODE. The first IP address corresponding to the target BH-RAN-NODE includes: the IP address used to establish a communication interface between the target BH-RAN-NODE and the source BH-RAN-NODE.

[0227] Since the handover request response message sent by the target BH-RAN-NODE to the source BH-RAN-NODE does not include additional information about the target BH-RAN-NODE's IP address, the source BH-RAN-NODE can send the IP address of the target BH-RAN-NODE's Xn interface (used for communication with the source BH-RAN-NODE) ​​to the WAB-gNB. The WAB-gNB can then use this IP address to establish the Xn interface with the target BH-RAN-NODE. In other words, the first IP address corresponding to the target BH-RAN-NODE includes the IP address of the target BH-RAN-NODE's Xn interface (used for communication with the source BH-RAN-NODE).

[0228] For a detailed explanation of the base station identifier for the target BH-RAN-NODE, please refer to the explanation in S602 of Method 600. For the sake of brevity, it will not be repeated here.

[0229] For example, the source BH-RAN-NODE can identify WAB-MT based on the identification information of WAB-MT, thereby identifying the WAB-gNB associated with WAB-MT, and sending the aforementioned fourth information to WAB-gNB through the Xn message of WAB-gNB.

[0230] For example, the source BH-RAN-NODE can identify WAB-MT based on its identifier information and send the aforementioned fourth information to WAB-MT via an RRC message. After receiving the fourth information, WAB-MT can forward it to WAB-gNB through its internal interface. Ultimately, WAB-gNB needs to receive the fourth information.

[0231] S704, WAB-gNB determines whether a communication interface (Xn interface) exists between itself and the target BH-RAN-NODE based on the fourth information.

[0232] For the specific process of S704, please refer to the explanation of S604 in Method 600 above. For the sake of brevity, it will not be repeated here. The difference is that in S604, at least one IP address corresponding to the target BH-RAN-NODE can be used for judgment, while in S704, the first IP address corresponding to the target BH-RAN-NODE needs to be used for judgment.

[0233] By utilizing the second identification information of the target BH-RAN-NODE, the efficiency and accuracy of WAB-gNB in ​​determining whether an Xn interface exists between it and the target BH-RAN-NODE can be improved.

[0234] S705, if the WAB-gNB determines that there is no communication interface (Xn interface) between it and the target BH-RAN-NODE, the WAB-gNB establishes an Xn interface with the target BH-RAN-NODE.

[0235] Alternatively, in one possible implementation, if the WAB-gNB cannot determine whether the WAB-gNB has established an Xn interface with the target BH-RAN-NODE, the WAB-gNB can also establish an Xn interface with the target BH-RAN-NODE.

[0236] It should be understood that S705 is an optional step, meaning that method 700 may not include S705. For example, if a communication interface (Xn interface) already exists between WAB-gNB and the target BH-RAN-NODE, method 700 may not include S705. If method 700 does not include S705, S706 is executed directly after S704.

[0237] In one possible implementation, if the fourth information includes the first IP address corresponding to the target BH-RAN-NODE, the WAB-gNB can establish an Xn interface between the target BH-RAN-NODE and the target BH-RAN-NODE using the first address corresponding to the target BH-RAN-NODE.

[0238] In one possible implementation, if the fourth information does not include the first IP address corresponding to the target BH-RAN-NODE, the WAB-gNB can also obtain the IP address of the target BH-RAN-NODE through other means. After obtaining the IP address of BH-RAN-NODE, the WAB-gNB can establish an Xn interface with the target BH-RAN-NODE using the IP address of the target BH-RAN-NODE.

[0239] S706, the WAB-gNB sends third information to the target BH-RAN-NODE via the communication interface. This third information includes the identification information of the WAB-MT and first resource configuration information, whereby the first resource configuration information includes the resource configuration of the WAB-gNB. Correspondingly, the WAB-gNB receives the third information via the communication interface.

[0240] For the specific process of S706, please refer to the description of S606 in the above method 600. For the sake of brevity, it will not be repeated here.

[0241] S707, the target BH-RAN-NODE sends second resource configuration information to WAB-gNB, WAB-MT, or the source BH-RAN-NODE according to the first resource configuration information. The second resource configuration information is used for resource reuse between WAB-gNB and WAB-MT.

[0242] For the specific process of S707, please refer to the description of S607 in the above method 600. For the sake of brevity, it will not be repeated here.

[0243] It should be understood that, in the example shown in method 700, the source BH-RAN-NODE can send a handover command to WAB-MT based on the handover request response message.

[0244] In one possible implementation, after S707 (or possibly after S706), the source BH-RAN-NODE can send a handover command to the WAB-MT. The handover command instructs the WAB-MT to switch from the BH-RAN-NODE to the target BH-RAN-NODE. Upon receiving the handover command, the WAB-MT can then switch from the source BH-RAN-NODE to the target BH-RAN-NODE.

[0245] In another possible implementation, the fourth information sent by the source BH-RAN-NODE to the WAB-MT and the handover command can be the same signaling, that is, the fourth information is carried in the handover command. In this case, the WAB-MT will not immediately execute the handover process according to the handover command after receiving it, but will only execute the handover process according to the handover command after S707 or S706.

[0246] For example, in one possible implementation, after S707 (or possibly after S706), optionally, as shown in Figure 7, the method 700 may further include S708: the source BH-RAN-NODE sends a handover command to the WAB-MT, the handover command instructing the WAB-MT to handover from the BH-RAN-NODE to the target BH-RAN-NODE. Correspondingly, the WAB-MT receives the handover command. The WAB-MT executes the handover process according to the handover command. In this way, it can be ensured that the target BH-RAN-NODE and WAB-gNB reuse resources before the WAB-MT hands over to the target BH-RAN-NODE. This enables resource reuse between the WAB-gNB and the target BH-RAN-NODE as early as possible, reducing potential interference and service degradation during the WAB-MT handover process.

[0247] The communication method provided in this application allows the source BH-RAN-NODE to send information about the target BH-RAN-NODE to the WAB-gNB bound to the WAB-MT before the WAB-MT switches to the target BH-RAN-NODE. Based on this information, the WAB-gNB can establish an Xn interface with the target BH-RAN-NODE and utilize this interface for resource reuse. This enables early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT handover process and ensuring communication efficiency.

[0248] The examples above use the communication system shown in Figure 3 as an example. In the communication system shown in Figure 4, which includes the RIC, gNBs do not need to directly exchange control information. The RIC can act as a centralized control node, responsible for forwarding Xn interface messages between gNBs. For example, in the examples shown in Figures 5 to 7, the RIC can be responsible for: forwarding information on the Xn interface between WAB-gNB and the target BH-RAN-NODE; forwarding information on the Xn interface between WAB-gNB and the source BH-RAN-NODE; and forwarding information on the Xn interface between the source BH-RAN-NODE and the target BH-RAN-NODE.

[0249] During the process of RIC forwarding information on the Xn interface between the source BH-RAN-NODE and the target BH-RAN-NODE (such as the first information in S503, the second resource configuration information sent by the target BH-RAN-NODE to the source BH-RAN-NODE in S508, the handover request in S601, the handover command in S602, the second resource configuration information sent by the target BH-RAN-NODE to the source BH-RAN-NODE in S607, the handover request in S701, the handover request response message in S702, and the second resource configuration information sent by the target BH-RAN-NODE to the source BH-RAN-NODE in S707), the address of WAB-MT on the E2 interface, UE E2AP ID, must be carried. That is, RIC needs to forward messages sent by the source BH-RAN-NODE to the target BH-RAN-NODE and messages sent by the target BH-RAN-NODE to the source BH-RAN-NODE through E2 messages.

[0250] During the process of the RIC forwarding information on the Xn interface between the source BH-RAN-NODE and WAB-gNB (e.g., WAB-gNB sending second information to source BH-RAN-NODE in S502, source BH-RAN-NODE sending second resource configuration information to WAB-gNB in ​​S508, source BH-RAN-NODE sending second resource configuration information to WAB-gNB in ​​S607, source BH-RAN-NODE sending fourth information to WAB-gNB in ​​S703, source BH-RAN-NODE sending second resource configuration information to WAB-gNB in ​​S707, etc.), the base station identifier (gNB ID) of the receiving end (e.g., WAB-gNB or source BH-RAN-NODE) ​​needs to be carried when the information is sent from the sending end (e.g., source BH-RAN-NODE or WAB-gNB) to the RIC. Similarly, the base station identifier (gNB ID) of the sending end needs to be carried when the information is sent from the RIC to the receiving end.

[0251] During the process of the RIC forwarding information on the Xn interface between the target BH-RAN-NODE and WAB-gNB (e.g., the request information in S506, the request information in S507, the first resource configuration information, the second resource configuration information sent by the target BH-RAN-NODE to the WAB-gNB in ​​S508, the third information in S606, the second resource configuration information sent by the target BH-RAN-NODE to the WAB-gNB in ​​S607, the third information in S706, and the second resource configuration information sent by the target BH-RAN-NODE to the WAB-gNB in ​​S707), the base station identifier (gNB ID) of the receiving end (e.g., WAB-gNB or target BH-RAN-NODE) ​​needs to be carried when the information is sent from the sending end (e.g., the target BH-RAN-NODE or WAB-gNB) to the RIC. Similarly, the base station identifier (gNB ID) of the sending end needs to be carried when the information is sent from the RIC to the receiving end.

[0252] In some possible implementations, if the source BH-RAN-NODE in the execution entity of the above method embodiments is replaced with the source BH-RAN-NODE-CU, the target BH-RAN-NODE is replaced with the target BH-RAN-NODE-CU, and WAB-gNB is replaced with WAB-CU, then the RIC can be responsible for: forwarding information on the Xn interface between WAB-CU and the target BH-RAN-NODE-CU, forwarding information on the Xn interface between WAB-CU and the source BH-RAN-NODE-CU, and forwarding information on the Xn interface between the source BH-RAN-NODE-CU and the target BH-RAN-NODE-CU. The forwarding process is similar to that described above, and for simplicity, it will not be repeated here.

[0253] It should be understood that the above description is merely to help those skilled in the art better understand the embodiments of this application, and is not intended to limit the scope of the embodiments of this application. Based on the examples given above, those skilled in the art can obviously make various equivalent modifications or changes. For example, some steps in the above method embodiments may be unnecessary, or new steps may be added. Alternatively, any combination of two or more of the above embodiments may be used. Such modifications, changes, or combinations also fall within the scope of the embodiments of this application.

[0254] It should also be understood that the methods, situations, categories, and classifications of embodiments in this application are for the convenience of description only and should not constitute a special limitation. Various methods, categories, situations, and features in embodiments can be combined without contradiction.

[0255] It should also be understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0256] It should also be understood that the above description of the embodiments of this application focuses on highlighting the differences between the various embodiments. Any similarities or differences not mentioned can be referred to each other. For the sake of brevity, they will not be repeated here.

[0257] The methods of the embodiments of this application have been described in detail above with reference to Figures 1 to 7. The communication devices of the embodiments of this application will be described in detail below with reference to Figures 8 and 9.

[0258] This embodiment can divide each network element (including WAB-MT, WAB-gNB, source BH-RAN-NODE, and target BH-RAN-NODE) ​​into functional modules according to the above method. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0259] It should be noted that the relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0260] The WAB-MT, WAB-gNB, source BH-RAN-NODE, and target BH-RAN-NODE provided in this application embodiment are used to execute any of the communication methods provided in the above-described method embodiments, thus achieving the same technical effects as the methods described above. When using integrated units, the WAB-MT, WAB-gNB, source BH-RAN-NODE, or target BH-RAN-NODE may include a processing module, and optionally a storage module and a communication module. The processing module can be used to control and manage the actions of the WAB-MT, WAB-gNB, source BH-RAN-NODE, or target BH-RAN-NODE. For example, it can be used to support the WAB-MT, WAB-gNB, source BH-RAN-NODE, or target BH-RAN-NODE in executing the steps performed by the processing unit. The storage module can be used to support the storage of program code and data, etc. The communication module can be used to support communication between the WAB-MT, WAB-gNB, source BH-RAN-NODE, or target BH-RAN-NODE and other devices.

[0261] It should be understood that the WAB-MT, WAB-gNB, source BH-RAN-NODE, or target BH-RAN-NODE provided in this application can be components (chips, chip systems, or processors) that support the implementation of this method by the WAB-MT, WAB-gNB, source BH-RAN-NODE, or target BH-RAN-NODE. They can also be logical nodes, logical modules, or software that can implement all or part of the functions of the WAB-MT, WAB-gNB, source BH-RAN-NODE, or target BH-RAN-NODE, such as WAB-CU, source BH-RAN-NODE-CU, or target BH-RAN-NODE.

[0262] The processing module can be a processor or a controller. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, etc. The storage module can be a memory. The communication module can specifically be a radio frequency circuit, a Bluetooth chip, or a device that interacts with other electronic devices.

[0263] For example, FIG8 shows a schematic block diagram of a communication device 800 according to an embodiment of the present application. As shown in FIG8, the communication device 800 includes a processing unit 810 and a transceiver unit 820. The transceiver unit 820 is used to perform operations related to the transmission and reception of information or signaling under the control of the processing unit 810. The processing unit may also be referred to as a processing module, and the transceiver unit may also be referred to as a communication unit, communication module, or communication interface, etc.

[0264] In some embodiments, the communication device 800 may correspond to the target BH-RAN-NODE described in method 500 above, or it may be a component (chip, chip system, or processor) applied to the target BH-RAN-NODE, or it may be a logic module or software capable of implementing all or part of the functions of the target BH-RAN-NODE. Furthermore, each module or unit in the communication device 800 is used to execute the various actions or processes performed by the target BH-RAN-NODE in method 500 above.

[0265] The transceiver unit 820 is configured to: receive first information from the source BH-RAN-NODE during WAB-MT handover, the first information including at least one of: identification information of WAB-gNB, first resource configuration information of WAB-gNB, or frequency information of WAB-gNB, and identification information of WAB-MT, wherein the first resource configuration information includes the resource configuration of WAB-gNB; the processing unit 810 is configured to: control the transceiver unit 820 to send second resource configuration information to WAB-gNB, WAB-MT, or source BH-RAN-NODE according to the first information, the second resource configuration information being used for resource multiplexing between WAB-gNB and WAB-MT.

[0266] The communication device provided in this application embodiment can obtain information about the WAB-gNB bound to the WAB-MT before the WAB-MT handover, and perform resource reuse based on the WAB-gNB information and the WAB-gNB (sending a second resource configuration message to the WAB-gNB, WAB-MT, or the source BH-RAN-NODE). This enables resource reuse between the WAB-gNB and the target BH-RAN-NODE as early as possible, reducing interference and service experience degradation that may occur during the WAB-MT handover, and ensuring communication efficiency.

[0267] For an explanation of the identification information of WAB-gNB, please refer to the corresponding part of the above method 500. For the sake of brevity, it will not be repeated here.

[0268] In one possible implementation, if the first information includes the identification information of the WAB-gNB, the processing unit 810 is further configured to: determine whether there is a communication interface between itself and the WAB-gNB based on the identification information of the WAB-gNB; and establish the communication interface between itself and the WAB-gNB if the communication interface does not exist; the transceiver unit 820 is specifically configured to: send the second resource configuration information to the WAB-gNB through the communication interface.

[0269] In one possible implementation, the processing unit 810 is specifically used to: establish the communication interface based on at least one IP address and the WAB-gNB.

[0270] In one possible implementation, if the first information does not include the first resource configuration information of the WAB-gNB, before the transceiver unit 820 sends the second resource configuration information, the transceiver unit 820 is further configured to: send a request message to the WAB-gNB through the communication interface, the request message being used to request the first resource configuration information; and receive the first resource configuration information from the WAB-gNB through the communication interface.

[0271] In one possible implementation, the transceiver unit 820 is specifically used to: send second resource configuration information to WAB-MT or source BH-RAN-NODE if the first information does not include the identification information of WAB-gNB.

[0272] In one possible implementation, before the transceiver unit 820 sends the second resource configuration information, when the first information includes the frequency information of the WAB-gNB, the processing unit 810 is further configured to: determine that the operating frequency of the WAB-gNB is the same as the operating frequency of the WAB-MT.

[0273] In one possible implementation, after the transceiver unit 820 sends the second resource configuration information, the transceiver unit 820 is further configured to: send a handover command to the WAB-MT, the handover command being used to instruct the WAB-MT to switch from the source backhaul access network node to the target backhaul access network node.

[0274] In one possible implementation, the specific process by which each unit in the communication device 800 performs the corresponding steps described above is given in the description of the target BH-RAN-NODE in the previous embodiment of method 500. For the sake of brevity, it will not be repeated here.

[0275] In some embodiments: the communication device 800 may correspond to the source BH-RAN-NODE described in method 500 above, or it may be a component (chip, chip system, or processor) applied to the source BH-RAN-NODE, or it may be a logic module or software that can implement all or part of the source BH-RAN-NODE. Furthermore, each module or unit in the communication device 800 is used to execute the various actions or processes performed by the source BH-RAN-NODE in method 500 above.

[0276] The processing unit 810 is used to: determine the binding relationship between the WAB-MT and the WAB-gNB; the transceiver unit 820 is used to: send first information to the target backhaul access network node (target BH-RAN-NODE), the first information including: at least one of the identification information of the WAB-gNB, the first resource configuration information of the WAB-gNB, or the frequency information of the WAB-gNB, and the identification information of the WAB-MT, wherein the first resource configuration information includes the resource configuration of the WAB-gNB.

[0277] The communication device provided in this application sends information about the WAB-gNB bound to the WAB-MT to the target BH-RAN-NODE before the WAB-MT handover, enabling the target BH-RAN-NODE to reuse resources based on the WAB-gNB information. This allows for early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT handover process and ensuring communication efficiency.

[0278] In one possible implementation, before the transceiver unit 820 sends the first information to the target backhaul access network node, the transceiver unit 820 is further configured to: receive second information from the WAB-MT or the WAB-gNB, the second information including: the first IP address of the WAB-gNB, the first IP address including one or more IP addresses, and at least one IP address corresponding to the WAB-gNB including the first IP address.

[0279] In one possible implementation, if the first information does not include the identification information of the WAB-gNB, the transceiver unit 820 is further configured to receive second resource configuration information from the target backhaul access network node. The second resource configuration information is used for resource multiplexing between the WAB-gNB and the WAB-MT: sending the second resource configuration information to the WAB-gNB or the WAB-MT.

[0280] In some embodiments: the communication device 800 may correspond to the target BH-RAN-NODE described in method 600 above, or it may be a component (chip, chip system, or processor) applied to the target BH-RAN-NODE, or it may be a logic module or software capable of implementing all or part of the target BH-RAN-NODE. Furthermore, each module or unit in the communication device 800 is used to execute the various actions or processes performed by the target BH-RAN-NODE in method 600 above.

[0281] The transceiver unit 820 is configured to: receive a handover request from the source backhaul access network node (source BH-RAN-NODE) ​​for WAB-MT handover; the transceiver unit 820 is further configured to: in response to the handover request, send a handover command to the WAB-MT, the handover command instructing the WAB-MT to handover from the source backhaul access network node to the target backhaul access network node (i.e., the target BH-RAN-NODE), the handover command including: first identification information of the target backhaul access network node and identification information of the WAB-MT; receive third information from the WAB-gNB through the communication interface, the third information including: identification information of the WAB-MT and first resource configuration information, the first resource configuration information including the resource configuration of the WAB-gNB; and, based on the first resource configuration information, send second resource configuration information to the WAB-gNB through the communication interface, the second resource configuration information being used for resource multiplexing between the WAB-gNB and the WAB-MT.

[0282] The communication device provided in this application embodiment can send information about the target BH-RAN-NODE to the WAB-gNB bound to the WAB-MT via a handover command before the WAB-MT switches to the target BH-RAN-NODE. This allows the WAB-gNB to establish a communication interface (Xn interface) based on the acquired target BH-RAN-NODE information, enabling resource reuse through the communication interface. This allows for early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT handover process and ensuring communication efficiency.

[0283] In one possible implementation, after the transceiver unit 820 receives the third information from the WAB-gNB through the communication interface, the transceiver unit 820 is also used to: receive the access request from the WAB-MT.

[0284] In one possible implementation, the identification information of the WAB-MT includes: the wireless network temporary identifier (C-RNTI) of the WAB-MT within the cell served by the target backhaul access network node, and / or, the identifier of the WAB-MT on the communication interface between the target backhaul access network node and the source backhaul access network node.

[0285] In some embodiments: the communication device 800 may correspond to the source BH-RAN-NODE described in method 700 above, or it may be a component (chip, chip system, or processor) applied to the source BH-RAN-NODE, or it may be a logic module or software that can implement all or part of the source BH-RAN-NODE. Furthermore, each module or unit in the communication device 800 is used to execute the various actions or processes performed by the source BH-RAN-NODE in method 700 above.

[0286] The transceiver unit 820 is configured to: send a handover request to the target backhaul access network node (target BH-RAN-NODE) ​​for the WAB-MT handover; and receive a handover request response message from the target backhaul access network node. The processing unit 810 is configured to: control the transceiver unit 820 to send fourth information to the WAB-MT or WAB-gNB based on the handover request response message. The fourth information includes: the second identification information of the target backhaul access network node and the identification information of the WAB-MT.

[0287] The communication device provided in this application embodiment can transmit the target BH-RAN-NODE information to the WAB-gNB bound to the WAB-MT before the WAB-MT switches to the target BH-RAN-NODE. This allows the WAB-gNB to reuse resources based on the acquired target BH-RAN-NODE information. This enables early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT handover process and ensuring communication efficiency.

[0288] In one possible implementation, the second identification information of the target backhaul access network node includes: the first IP address corresponding to the target backhaul access network node, and / or the base station identifier of the target backhaul access network node, wherein the first IP address corresponding to the target backhaul access network node includes: the IP address used to establish a communication interface between the target backhaul access network node and the source backhaul access network node.

[0289] In one possible implementation, after the transceiver unit 820 sends the fourth information to the WAB-MT or WAB-gNB, the transceiver unit 820 is further configured to: send a handover command to the WAB-MT, the handover command being used to instruct the WAB-MT to hand over from the source backhaul access network node (source BH-RAN-NODE) ​​to the target backhaul access network node.

[0290] In some embodiments: the communication device 800 may correspond to the WAB-gNB described in method 600 or method 700 above, or it may be a component (chip, chip system, or processor) applied to the WAB-gNB, or it may be a logic module or software that can implement all or part of the WAB-gNB. Furthermore, each module or unit in the communication device 800 is used to execute the various actions or processes performed by the WAB-gNB in ​​method 600 or method 700 above.

[0291] The transceiver unit 820 is configured to: receive a handover command or fourth information, wherein the handover command instructs the Radio Access Backhaul Node Terminal Function (WAB-MT) to switch from the source backhaul access network node (source BH-RAN-NODE) ​​to the target backhaul access network node (target BH-RAN-NODE); the handover command includes: first identification information of the target backhaul access network node and identification information of the WAB-MT; the fourth information includes: second identification information of the target backhaul access network node and identification information of the WAB-MT; in response to the handover command or fourth information, send third information to the target backhaul access network node through a communication interface, wherein the third information includes: identification information of the WAB-MT and first resource configuration information, the first resource configuration information including the resource configuration of the WAB-gNB; and receive second resource configuration information from the target backhaul access network node (target BH-RAN-NODE) ​​through the communication interface, the second resource configuration information being used for resource multiplexing between the WAB-gNB and the WAB-MT.

[0292] The communication device provided in this application embodiment can acquire information about the target BH-RAN-NODE before the WAB-MT switches to the target BH-RAN-NODE. The WAB-gNB establishes a communication interface with the target BH-RAN-NODE based on the acquired information, and performs resource reuse through the communication interface. This enables early resource reuse between the WAB-gNB and the target BH-RAN-NODE, reducing potential interference and service degradation during the WAB-MT handover process, and ensuring communication efficiency.

[0293] In one possible implementation, the processing unit 810 is configured to: determine whether the communication interface exists between the target backhaul access network node and the target backhaul access network node based on the first identification information or the second identification information of the target backhaul access network node; and establish the communication interface between the processing unit 810 and the target backhaul access network node if the communication interface does not exist.

[0294] In one possible implementation, the processing unit 810 is specifically used to: establish the communication interface with the WAB-gNB based on at least one IP address corresponding to the target backhaul access network node or the first IP address corresponding to the target backhaul access network node.

[0295] In one possible implementation, the identification information of the WAB-MT includes: the wireless network temporary identifier (C-RNTI) of the WAB-MT within the cell served by the target backhaul access network node, and / or, the identifier of the WAB-MT on the communication interface between the target backhaul access network node and the source backhaul access network node.

[0296] Furthermore, the communication device 800 may also include a storage unit, and the transceiver unit 820 may be a transceiver, an input / output interface, pins, or interface circuitry. The storage unit is used to store instructions executed by the transceiver unit 820 and the processing unit 810. The transceiver unit 820, the processing unit 810, and the storage unit are coupled to each other. The storage unit stores instructions, the processing unit 810 executes the instructions stored in the storage unit, and the transceiver unit 820 performs specific signal transmission and reception under the control of the processing unit 810.

[0297] It should be understood that the transceiver unit 820 may be a transceiver, an input / output interface, or an interface circuit. The storage unit may be a memory. The processing unit 810 may be implemented by a processor.

[0298] As shown in Figure 9, the communication device 900 may include a processor 910. Optionally, the communication device 900 may also include a memory 920 and a transceiver 930. The dashed lines in Figure 9 indicate that this unit or module is optional. This communication device 900 can be used to implement the methods described in the above method embodiments.

[0299] In one possible implementation, the communication device 800 shown in FIG8 or the communication device 900 shown in FIG9 can implement the steps executed by WAB-gNB in ​​the aforementioned methods 500, 600, or 700. Similar descriptions can be found in the descriptions of the corresponding methods described above. To avoid repetition, further details are omitted here.

[0300] In one possible implementation, the communication device 800 shown in FIG8 or the communication device 900 shown in FIG9 can implement the steps of the target BH-RAN-NODE executed in the aforementioned methods 500, 600, or 700. Similar descriptions can be found in the descriptions of the corresponding methods described above. To avoid repetition, further details are omitted here.

[0301] In one possible implementation, the communication device 800 shown in FIG8 or the communication device 900 shown in FIG9 can implement the steps performed by the source BH-RAN-NODE in the aforementioned methods 500, 600, or 700. Similar descriptions can be found in the descriptions of the corresponding methods described above. To avoid repetition, further details are omitted here.

[0302] In one possible implementation, the communication device 800 shown in FIG8 or the communication device 900 shown in FIG9 can implement the steps executed by WAB-MT in the aforementioned methods 500, 600, or 700. Similar descriptions can be found in the descriptions of the corresponding methods described above. To avoid repetition, further details are omitted here.

[0303] In one possible implementation, the communication device 800 shown in FIG8 or the communication device 900 shown in FIG9 can be WAB-MT, WAB-gNB, source BH-RAN-NODE, target BH-RAN-NODE, or WAB-MT, WAB-gNB, source BH-RAN-NODE, target BH-RAN-NODE can include the communication device 800 shown in FIG8 or the communication device 900 shown in FIG9.

[0304] It should also be understood that the division of units or modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the device can be implemented entirely through software calls from processing elements; all units can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, while others are implemented in hardware. For example, each unit can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as a program in memory, and its function can be called and executed by a processing element within the device. Here, the processing element can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above units can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.

[0305] In one example, a unit in any of the above communication devices can be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits (ASICs), or one or more DSPs, or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. As another example, when a unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a CPU or other processor capable of calling programs. Furthermore, these units can be integrated together and implemented as a system-on-a-chip (SOC).

[0306] It should be understood that in the embodiments of this application, the processor can be a CPU, but it can also be other general-purpose processors, DSPs, ASICs, FPGAs, microprocessors (MPUs), microcontroller units (MCUs), graphics processing units (GPUs), artificial intelligence processors (AI processors), neural processing units (NPUs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0307] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), EPROM, electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be cache or random access memory (RAM) (which serves as an external cache). By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0308] This application also provides a communication system, which includes: the aforementioned WAB-MT, WAB-gNB (e.g., WAB-CU), source BH-RAN-NODE (e.g., source BH-RAN-NODE-CU), and target BH-RAN-NODE (e.g., target BH-RAN-NODE-CU).

[0309] Optionally, the communication system may also include a RIC.

[0310] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, all or part of the processes or functions according to the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means.

[0311] This application also provides a computer-readable medium for storing computer program code, the computer program including instructions for executing any of the communication methods provided in the embodiments of this application. The readable medium may be the memory described in the examples above, and this application does not limit this to such methods.

[0312] This application also provides a computer program product including instructions that, when executed, cause the WAB-MT, WAB-gNB, source BH-RAN-NODE, or target BH-RAN-NODE to perform operations corresponding to the network element or device described in the above method.

[0313] This application also provides a chip comprising a processing unit and a communication unit. The processing unit may be, for example, a processor, and the communication unit may be, for example, an input / output interface, pins, or circuitry. The processing unit can execute computer instructions to cause the chip within the communication device to perform any of the communication methods provided in the embodiments of this application.

[0314] Optionally, any of the communication devices provided in the above embodiments of this application may include the chip.

[0315] Optionally, the computer instructions are stored in a storage unit.

[0316] Optionally, the storage unit can be an internal storage unit within the chip, such as a register or cache. Alternatively, it can be an external storage unit within the communication device, such as ROM or other types of static storage devices capable of storing static information and instructions, like RAM. The processing unit and the storage unit can be decoupled and located on different physical devices, connected via wired or wireless means to implement their respective functions, thus supporting the chip in performing the various functions described in the above embodiments. Alternatively, the processing unit and the memory can also be coupled to the same device.

[0317] In this embodiment, the WAB-MT, WAB-gNB, source BH-RAN-NODE, target BH-RAN-NODE, communication system, computer-readable storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0318] In this application, various objects such as messages / information / devices / systems / apparatus / actions / operations / processes may be named. It is understood that these specific names do not constitute a limitation on the relevant objects. The names may be changed depending on the scenario, context, or usage habits. The understanding of the technical meaning of the technical terms in this application should be mainly determined from their functions and technical effects embodied / performed in the technical solution.

[0319] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0320] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0321] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method includes: The target backhaul access network node during the WAB-MT handover receives first information from the source backhaul access network node during the WAB-MT handover. The first information includes at least one of the following: identification information of the WAB-gNB, first resource configuration information of the WAB-gNB, or frequency information of the WAB-gNB, and identification information of the WAB-MT, wherein the first resource configuration information includes the resource configuration of the WAB-gNB. The target backhaul access network node sends second resource configuration information to the WAB-gNB, the WAB-MT, or the source backhaul access network node based on the first information. The second resource configuration information is used for resource reuse between the WAB-gNB and the WAB-MT.

2. The method according to claim 1, characterized in that, The identification information of the WAB-gNB includes: at least one IP address corresponding to the WAB-gNB, and / or, the base station identifier of the WAB-gNB.

3. The method according to claim 2, characterized in that, If the first information includes the identification information of the WAB-gNB, the method further includes: The target backhaul access network node determines whether there is a communication interface with the WAB-gNB based on the identification information of the WAB-gNB. In the absence of the communication interface, the communication interface is established between the target backhaul access network node and the WAB-gNB; The target backhaul access network node sends second resource configuration information to the WAB-gNB, including: The target backhaul access network node sends the second resource configuration information to the WAB-gNB through the communication interface.

4. The method according to claim 3, characterized in that, The establishment of the communication interface between the target backhaul access network node and the WAB-gNB includes: The target backhaul access node establishes the communication interface based on the at least one IP address and the WAB-gNB.

5. The method according to claim 3 or 4, characterized in that, If the first information does not include the first resource configuration information of the WAB-gNB, the method further includes the following steps before the target backhaul access network node sends the second resource configuration information: The target backhaul access network node sends a request message to the WAB-gNB through the communication interface. The request message is used to request the first resource configuration information. The target backhaul access network node receives the first resource configuration information from the WAB-gNB through the communication interface.

6. The method according to claim 1 or 2, characterized in that, The target backhaul access network node sends second resource configuration information to the WAB-MT or the source backhaul access network node, including: If the first information does not include the identification information of the WAB-gNB, the target backhaul access network node sends the second resource configuration information to the WAB-MT or the source backhaul access network node.

7. The method according to any one of claims 1 to 6, characterized in that, When the first information includes the frequency information of the WAB-gNB, before the target backhaul access network node sends the second resource configuration information, the method further includes: The target backhaul access network node determines that the operating frequency of the WAB-gNB is the same as that of the WAB-MT.

8. The method according to any one of claims 1 to 7, characterized in that, After the target backhaul access network node sends the second resource configuration information, the method further includes: The target backhaul access network node sends a handover command to the WAB-MT, the handover command being used to instruct the WAB-MT to switch from the source backhaul access network node to the target backhaul access network node.

9. A communication method, characterized in that, The method includes: The source backhaul access network node for the wireless access backhaul node terminal function WAB-MT switching determines the binding relationship between the WAB-MT and the WAB-gNB; The source backhaul access network node sends first information to the target backhaul access network node. The first information includes at least one of the following: the identification information of the WAB-gNB, the first resource configuration information of the WAB-gNB, or the frequency information of the WAB-gNB, and the identification information of the WAB-MT, wherein the first resource configuration information includes the resource configuration of the WAB-gNB.

10. The method according to claim 9, characterized in that, The identification information of the WAB-gNB includes: at least one IP address corresponding to the WAB-gNB, and / or, the base station identifier of the WAB-gNB.

11. The method according to claim 10, characterized in that, Before the source backhaul access network node sends the first information to the target backhaul access network node, the method further includes: The source backhaul access network node receives second information from the WAB-MT or the WAB-gNB. The second information includes: the first IP address of the WAB-gNB, the first IP address including one or more IP addresses, and at least one IP address corresponding to the WAB-gNB including the first IP address.

12. The method according to any one of claims 9 to 11, characterized in that, If the first information does not include the identification information of the WAB-gNB, the method further includes: The source backhaul access network node receives second resource configuration information from the target backhaul access network node, and the second resource configuration information is used for resource multiplexing between the WAB-gNB and the WAB-MT. The source backhaul access network node sends the second resource configuration information to the WAB-gNB or the WAB-MT.

13. A communication method, characterized in that, The method includes: The target backhaul access network node of the wireless access backhaul node terminal function WAB-MT handover receives the handover request from the source backhaul access network node of the WAB-MT handover. In response to the handover request, the target backhaul access network node sends a handover command to the WAB-MT. The handover command is used to instruct the WAB-MT to switch from the source backhaul access network node to the target backhaul access network node. The handover command includes: the first identification information of the target backhaul access network node and the identification information of the WAB-MT. The target backhaul access network node receives third information from the wireless access backhaul node base station function WAB-gNB through a communication interface. The third information includes: the identification information of the WAB-MT and the first resource configuration information, wherein the first resource configuration information includes the resource configuration of the WAB-gNB. The target backhaul access network node sends second resource configuration information to the WAB-gNB through the communication interface according to the first resource configuration information. The second resource configuration information is used for resource multiplexing between the WAB-gNB and the WAB-MT.

14. The method according to claim 13, characterized in that, The first identification information of the target backhaul access network node includes: at least one IP address corresponding to the target backhaul access network node, and / or, the base station identifier of the target backhaul access network node.

15. The method according to claim 13 or 14, characterized in that, After the target backhaul access network node receives the third information from the WAB-gNB through the communication interface, the target backhaul access network node receives the access request from the WAB-MT.

16. The method according to any one of claims 13 to 15, characterized in that, The identification information of the WAB-MT includes: the wireless network temporary identifier (C-RNTI) of the WAB-MT in the cell served by the target backhaul access network node, and / or the identifier of the WAB-MT on the communication interface between the target backhaul access network node and the source backhaul access network node.

17. A communication method, characterized in that, The method includes: The source backhaul access network node for the wireless access backhaul node terminal function WAB-MT handover sends a handover request to the target backhaul access network node for the WAB-MT handover. The source backhaul access network node receives a handover request response message from the target backhaul access network node; The source backhaul access network node sends fourth information to the WAB-MT or the wireless access backhaul node base station function WAB-gNB according to the handover request response message. The fourth information includes: the second identification information of the target backhaul access network node and the identification information of the WAB-MT.

18. The method according to claim 17, characterized in that, The second identification information of the target backhaul access network node includes: the first IP address corresponding to the target backhaul access network node, and / or the base station identifier of the target backhaul access network node, wherein the first IP address corresponding to the target backhaul access network node includes: the IP address used to establish a communication interface between the target backhaul access network node and the source backhaul access network node.

19. The method according to claim 17 or 18, characterized in that, The identification information of the WAB-MT includes: the wireless network temporary identifier (C-RNTI) of the WAB-MT in the cell served by the target backhaul access network node, and / or the identifier of the WAB-MT on the communication interface between the target backhaul access network node and the source backhaul access network node.

20. The method according to any one of claims 17 to 19, characterized in that, After the source backhaul access network node sends the fourth information to the WAB-MT or the WAB-gNB, the method further includes: The source backhaul access network node sends a handover command to the WAB-MT, the handover command being used to instruct the WAB-MT to switch from the source backhaul access network node to the target backhaul access network node.

21. A communication method, characterized in that, The method includes: The Wireless Access Backhaul Node Base Station Function (WAB-gNB) receives a handover command or fourth information. The handover command instructs the Wireless Access Backhaul Node Terminal Function (WAB-MT) to switch from the source backhaul access network node to the target backhaul access network node. The handover command includes: first identification information of the target backhaul access network node and identification information of the WAB-MT. The fourth information includes: second identification information of the target backhaul access network node and identification information of the WAB-MT. In response to the handover command or the fourth information, the WAB-gNB sends third information to the target backhaul access network node through the communication interface. The third information includes: the identification information of the WAB-MT and the first resource configuration information, wherein the first resource configuration information includes the resource configuration of the WAB-gNB. The WAB-gNB receives second resource configuration information from the target backhaul access network node through the communication interface. The second resource configuration information is used for resource multiplexing between the WAB-gNB and the WAB-MT.

22. The method according to claim 21, characterized in that, The first identification information of the target backhaul access network node includes: at least one IP address corresponding to the target backhaul access network node, and / or, the base station identifier of the target backhaul access network node.

23. The method according to claim 21, characterized in that, The second identification information of the target backhaul access network node includes: the first IP address corresponding to the target backhaul access network node, and / or the base station identifier of the target backhaul access network node, wherein the first IP address corresponding to the target backhaul access network node includes: the IP address used to establish a communication interface between the target backhaul access network node and the source backhaul access network node.

24. The method according to claim 22 or 23, characterized in that, The method further includes: The WAB-gNB determines whether there is a communication interface between itself and the target backhaul access network node based on the first identification information or the second identification information of the target backhaul access network node. In the absence of the aforementioned communication interface, the communication interface is established between the WAB-gNB and the target backhaul access network node.

25. The method according to claim 24, characterized in that, The establishment of the communication interface between the WAB-gNB and the target backhaul access network node includes: The WAB-gNB establishes the communication interface with the WAB-gNB based on at least one IP address corresponding to the target backhaul access network node or the first IP address corresponding to the target backhaul access network node.

26. The method according to any one of claims 21 to 25, characterized in that, The identification information of the WAB-MT includes: the wireless network temporary identifier (C-RNTI) of the WAB-MT in the cell served by the target backhaul access network node, and / or the identifier of the WAB-MT on the communication interface between the target backhaul access network node and the source backhaul access network node.

27. A communication device, characterized in that, include: A unit for performing the steps of the method as described in any one of claims 1 to 8, or a unit for performing the steps of the method as described in any one of claims 9 to 12, or a unit for performing the steps of the method as described in any one of claims 13 to 16, or a unit for performing the steps of the method as described in any one of claims 17 to 20, or a unit for performing the steps of the method as described in any one of claims 21 to 26.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, the computer program including program instructions that, when executed by a processor, cause the processor to perform: the method of any one of claims 1 to 8, or the method of any one of claims 9 to 12, or the method of any one of claims 13 to 16, or the method of any one of claims 17 to 20, or the method of any one of claims 21 to 26.

29. A computer program product, characterized in that, include: A computer program, when run on a computer, causes the computer to perform: the method as claimed in any one of claims 1 to 8, or the method as claimed in any one of claims 9 to 12, or the method as claimed in any one of claims 13 to 16, or the method as claimed in any one of claims 17 to 20, or the method as claimed in any one of claims 21 to 26.

30. A chip, characterized in that, Includes: a processor for retrieving and running a computer program from memory, causing a communication device on which the chip is mounted to perform: the method of any one of claims 1 to 8, or the method of any one of claims 9 to 12, or the method of any one of claims 13 to 16, or the method of any one of claims 17 to 20, or the method of any one of claims 21 to 26.

Images