Communication method and communication apparatus

By informing the CU of IAB-DU when the IAB authorization information is updated, the problem of how to obtain authorization information is solved at the same time as the IAB-MT and the CU of IAB-DU is different, and the flexibility and ability of flexible control of IAB nodes and network management are achieved. Controlled.

WO2024230369A1PCT designated stage expired Publication Date: 2024-11-14HUAWEI TECH CO LTD

Patent Information

Application Number
PCT/CN2024/085603
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2024-04-02
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

In a network containing IAB nodes, the prior art has failed to effectively solve the problem of how the IAB-MT CU is different from the IAB-DU CU. This makes it impossible to flexibly control the IAB node's CU. Working status.

Method used

When the IAB authorization information is updated, the latest IAB authorization information is notified to the CU of the IAB-DU, so that it can determine whether to delete the F1 interface, whether to allow the establishment of the F1 interface, whether the cell is turned off or the UE is prohibited, so as to realize the IAB nodes Flexible control.

Benefits of technology

It realizes flexible control of IAB nodes in a specific time and space range, ensures real-time update and accurate acquisition of authorization information of IAB nodes on the network side, and improves the flexibility and controllability of network management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024085603_14112024_PF_FP_ABST
    Figure CN2024085603_14112024_PF_FP_ABST
Patent Text Reader

Abstract

The present application provides a communication method, comprising: a first donor node receives IAB authorization information, the IAB authorization information being used for indicating the authorization state of a first IAB node, the first IAB node comprising a first distributed unit and a first mobile terminal, the first mobile terminal and a second donor node being in an RRC connection, the first distributed unit and the first donor node being in an F1 connection or attempting to establish an F1 connection, and the first donor node and the second donor node being different donor nodes; and, according to the IAB authorization information, the first donor node determines whether to allow the first IAB node to provide a service for a UE. When the IAB authorization information is updated, informing the latest IAB authorization information to a CU of an IAB-DU enables the CU of the IAB-DU to determine, on the basis of the latest authorization information, whether to allow the IAB node to provide a service for the UE, thus facilitating flexible control over IAB nodes by a network side.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 11, 2023, with application number 202310531939.X and application name “Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and more particularly, to a communication method and a communication device. Background Art

[0003] In a network containing integrated access and backhaul (IAB) nodes, the transmission path between user equipment (UE) and an IAB donor (also known as a donor node or donor gNB) consists of multiple transmission links, including at least one wireless backhaul link and one wireless access link. The wireless access link is the communication link between the UE and a relay node (also known as an IAB node), and the wireless backhaul link is the communication link between IAB nodes or between an IAB node and a donor node. UE service data is transmitted by the IAB node connecting to the IAB donor via the wireless backhaul link.

[0004] The IAB node consists of a mobile termination (MT) and a distributed unit (DU). When the IAB node faces its parent node, it can act as a terminal device, i.e., the role of an MT. When the IAB node faces its child node (the child node may be another IAB node or an ordinary UE), it is regarded as a network device, i.e., the role of a DU. The host node is an access network element with complete base station (gNB) functions, including a centralized unit (CU) and a distributed unit (DU). The host node is connected to the core network serving the UE (for example, to the 5G core network).

[0005] In this application, the MT of an IAB node is referred to as IAB-MT, the DU of the IAB node is referred to as IAB-DU, the CU of the host node that establishes an RRC connection with the IAB-MT is referred to as the CU of the IAB-MT, and the CU of the host node that establishes an F1 connection with the IAB-DU is referred to as the CU of the IAB-DU.

[0006] When the IAB node joins the network or the authorization status changes, it needs to obtain IAB authorization information from the access and mobility management function (AMF) network element of the core network. The IAB authorization information is the authorization status information of the IAB-MT (or the authorization status information of the IAB node). The authorization information is carried in the context-related information of the IAB-MT and is sent by the AMF of the IAB-MT to the CU of the IAB-MT.

[0007] In many scenarios (such as IAB node migration scenarios), the CU of the IAB-MT and the CU of the IAB-DU may be different. In some implementations, the CU of the IAB-DU is required to know the IAB authorization information of the IAB-MT. For example, when the IAB node initially joins the network, if the CU of the IAB-MT configures the MT with a default configuration and the IAB-DU sends an F1 interface establishment request to its CU, the CU of the IAB-DU needs to know whether the IAB node is authorized or unauthorized in order to perform corresponding operations (e.g., when the IAB node is unauthorized, reject the IAB-DU's F1 interface establishment request). However, the prior art does not consider how the CU of the IAB-DU can obtain the current IAB authorization information when the CU of the IAB-MT and the CU of the IAB-DU are different.

[0008] Summary of the Invention

[0009] The present application provides a communication method and a communication device. When IAB authorization information is updated, the latest IAB authorization information is notified to the CU of the IAB-DU. This enables the CU of the IAB-DU to determine, based on the authorization information, whether to delete the F1 interface, whether to allow the establishment of the F1 interface, whether to shut down the cell under the IAB-DU, or whether to configure the cell under the IAB-DU to prohibit UE access. This facilitates the network side to flexibly control the IAB node, and meets the requirements of allowing or prohibiting the operation of the IAB node within a specific time or space range.

[0010] In a first aspect, a communication method is provided. The method may be executed by a host node, or may be executed by a chip or circuit configured in the host node, which is not limited in this application.

[0011] The method includes: a first host node receives access backhaul integrated IAB authorization information, where the IAB authorization information is used to indicate the authorization status of the first IAB node, the first IAB node includes a first distributed unit and a first mobile terminal, an RRC connection exists between the first mobile terminal and a second host node, an F1 connection exists between the first distributed unit and the first host node or an F1 connection is attempted to be established, and the first host node and the second host node are different host nodes; and the first host node determines, based on the IAB authorization information, whether to allow the first IAB node to provide services for a UE.

[0012] According to the solution of the application, when the IAB authorization information is updated, the latest IAB authorization information is notified to the CU of the IAB-DU, so that the CU of the IAB-DU can determine whether to delete the F1 interface / whether to allow the establishment of the F1 interface / whether to shut down the cell under the IAB-DU / whether to configure the cell under the IAB-DU to prohibit UE access, etc. based on the authorization information.

[0013] In a second aspect, a communication method is provided. The method may be executed by a host node, or may be executed by a chip or circuit configured in the host node, and this application does not limit this.

[0014] The method includes: a second host node sends access backhaul integrated IAB authorization information to a first host node, where the IAB authorization information is used to indicate the authorization status of the first IAB node, the first IAB node includes a first distributed unit and a first mobile terminal, an RRC connection exists between the first mobile terminal and the second host node, and an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection.

[0015] In a possible implementation, before the second donor node sends the IAB authorization information to the first donor node, the method further includes: the second donor node receiving the IAB authorization information from the core network access and mobility function AMF.

[0016] In one possible implementation, before the second host node sends the IAB authorization information to the first host node, the method further includes: the second host node receives identification information of the first host node from a third host node, and the third host node is a host node that has an RRC connection with the first mobile terminal before the first mobile terminal establishes an RRC connection with the second host node.

[0017] In a possible implementation, the second host node sending the IAB authorization information to the first host node includes: the second host node sending the IAB authorization information to the first host node according to identification information of the first host node.

[0018] In a third aspect, a communication method is provided. The method may be executed by a host node, or may be executed by a chip or circuit configured in the host node, and this application does not limit this.

[0019] The method includes: a third host node sends access backhaul integrated IAB authorization information to a first host node, where the IAB authorization information is used to indicate the authorization status of the first IAB node, the first IAB node includes a first distributed unit and a first mobile terminal, an RRC connection exists between the first mobile terminal and the second host node, the third host node is a host node that has an RRC connection with the first mobile terminal before the first mobile terminal establishes an RRC connection with the second host node, and an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection.

[0020] In a possible implementation, before the third host node sends the IAB authorization information to the first host node, the method further includes: the third host node receiving the IAB authorization information from the second host node.

[0021] In a fourth aspect, a communication method is provided. The method may be executed by an IAB node, or may be executed by a chip or circuit configured in the IAB node, which is not limited in this application.

[0022] The method includes: a first access and backhaul integrated IAB node sends IAB authorization information to a first host node, where the IAB authorization information is used to indicate the authorization status of the first IAB node, the first IAB node includes a first distributed unit and a first mobile terminal, an RRC connection exists between the first mobile terminal and the second host node, and an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection.

[0023] In one possible implementation, before the first IAB node sends the IAB authorization information to the first host node, the method further includes: the first IAB node receives the IAB authorization information from the core network access and mobility management function AMF or the second host node, or the first IAB node receives the IAB authorization information from a fourth host node, where the fourth host node is a host node that has an F1 connection with the first distributed unit before the first distributed unit establishes an F1 connection with the first host node.

[0024] In the fifth aspect, a communication method is provided, which can be executed by AMF, or by a chip or circuit configured in AMF, and this application does not limit this.

[0025] The method includes: a core network access and mobility management function AMF sends access backhaul integrated IAB authorization information to a first host node, where the IAB authorization information is used to indicate the authorization status of the first access backhaul integrated IAB node, the first IAB node includes a first distributed unit and a first mobile terminal, an RRC connection exists between the first mobile terminal and the second host node, an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection, and the first host node and the second host node are different host nodes.

[0026] In a possible implementation, before the AMF sends the IAB authorization information to the first host node, the method further includes: the AMF receiving identification information of the first host node sent by the first IAB node.

[0027] In a possible implementation manner, the sending, by the AMF, the IAB authorization information to the first host node includes: sending, by the AMF, the IAB authorization information to the first host node according to the identification information of the first host node.

[0028] In a possible implementation, before the AMF sends the IAB authorization information to the first host node, the method further includes: the AMF receiving identification information of the first host node sent by the second host node.

[0029] In a possible implementation manner, the sending, by the AMF, the IAB authorization information to the first host node includes: sending, by the AMF, the IAB authorization information to the first host node according to the identification information of the first host node.

[0030] In a sixth aspect, a communication method is provided. The method can be executed by a host node, or can be executed by a chip or circuit configured in the host node. This application does not limit this.

[0031] The method includes: a fourth host node sends access backhaul integrated IAB authorization information to a first host node, where the IAB authorization information is used to indicate the authorization status of the first IAB node, the first IAB node includes a first distributed unit and a first mobile terminal, the first distributed unit includes a first logical distributed unit and a second logical distributed unit, an RRC connection exists between the first mobile terminal and the second host node, an F1 connection exists between the first logical distributed unit and the fourth host node, and the second logical distributed unit has an F1 connection with the first host node or attempts to establish an F1 connection.

[0032] In a seventh aspect, a communication method is provided. The method may be executed by an IAB node, or may be executed by a chip or circuit configured in the IAB node, and this application does not limit this.

[0033] The method includes: a first access and backhaul integrated IAB node sends identification information of a first host node to a core network access and mobility management function AMF, wherein the first IAB node includes a first distributed unit and a first mobile terminal, an RRC connection exists between the first mobile terminal and the second host node, an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection, and the AMF is used to send IAB authorization information to the first host node according to the identification information of the first host node, and the IAB authorization information is used to indicate the authorization status of the first IAB node.

[0034] In an eighth aspect, a communication method is provided. The method can be executed by a host node, or can be executed by a chip or circuit configured in the host node. This application does not limit this.

[0035] The method includes: a second host node sends identification information of a first host node to a core network access and mobility management function AMF, an RRC connection exists between the second host node and a first mobile terminal, the first mobile terminal is a mobile terminal in a first access and backhaul integrated IAB node, the first IAB node also includes a first distributed unit, an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection, the AMF is used to send IAB authorization information to the first host node according to the identification information of the first host node, and the IAB authorization information is used to indicate the authorization status of the first IAB node.

[0036] In the ninth aspect, a communication method is provided. The method can be executed by a host node, or can be executed by a chip or circuit configured in the host node. This application does not limit this.

[0037] The method includes: a third host node sends identification information of a first host node to a second host node, where the second host node is a host node that has an RRC connection with a first mobile terminal, the first host node is a host node that has an F1 connection with a first distributed unit or attempts to establish an F1 connection, and the third host node is a host node that has an RRC connection with the first mobile terminal before the first mobile terminal establishes an RRC connection with the second host node.

[0038] In the tenth aspect, a communication device is provided, including: a receiving module for receiving access backhaul integrated IAB authorization information, the IAB authorization information being used to indicate the authorization status of a first IAB node, the first IAB node including a first distributed unit and a first mobile terminal, an RRC connection existing between the first mobile terminal and the second host node, an F1 connection existing between the first distributed unit and the first host node or an attempt to establish an F1 connection, the first host node and the second host node being different host nodes; a processing module for determining whether the first IAB node is allowed to provide services for the UE based on the IAB authorization information.

[0039] In the eleventh aspect, a communication device is provided, which is a host node that has an RRC connection with a first mobile terminal. The device includes: a sending module for sending access backhaul integrated IAB authorization information to the first host node, and the IAB authorization information is used to indicate the authorization status of the first IAB node. The first IAB node includes a first distributed unit and the first mobile terminal. There is an F1 connection between the first distributed unit and the first host node or an attempt is made to establish an F1 connection.

[0040] In a possible implementation, the apparatus further includes: a receiving module configured to receive IAB authorization information from a core network access and mobility management function (AMF).

[0041] In one possible implementation, the receiving module is further used to receive identification information of the first host node from a third host node, where the third host node is a host node that has an RRC connection with the first mobile terminal before the first mobile terminal establishes an RRC connection with the second host node.

[0042] In a possible implementation, the sending module sending the IAB authorization information to the first host node includes: the sending module sending the IAB authorization information to the first host node according to identification information of the first host node.

[0043] In the twelfth aspect, a communication device is provided, which is a host node that has an RRC connection with the first mobile terminal before the first mobile terminal establishes an RRC connection with the second host node. The device includes: a sending module for sending access backhaul integrated IAB authorization information to the first host node, the IAB authorization information is used to indicate the authorization status of the first IAB node, the first IAB node includes a first distributed unit and the first mobile terminal, there is an RRC connection between the first mobile terminal and the second host node, and there is an F1 connection between the first distributed unit and the first host node or an attempt to establish an F1 connection.

[0044] In a possible implementation manner, the apparatus further includes: a receiving module, configured to receive IAB authorization information from the second host node.

[0045] In the thirteenth aspect, a communication device is provided, which is an access backhaul integrated IAB node, the device including: a sending module for sending IAB authorization information to a first host node, the IAB authorization information being used to indicate the authorization status of the first IAB node, the first IAB node including a first distributed unit and a first mobile terminal, an RRC connection existing between the first mobile terminal and the second host node, and an F1 connection existing between the first distributed unit and the first host node or an attempt to establish an F1 connection.

[0046] In one possible implementation, the device also includes: a receiving module, configured to receive IAB authorization information from a core network access and mobility management function AMF or a second host node, or the first IAB node receives IAB authorization information from a fourth host node, where the fourth host node is a host node that has an F1 connection with the first distributed unit before the first distributed unit establishes an F1 connection with the first host node.

[0047] In the fourteenth aspect, a communication device is provided, which is a core network access and mobility management function AMF that provides services for an access and backhaul integrated IAB node. The device includes: a sending module for sending IAB authorization information to a first host node, and the IAB authorization information is used to indicate the authorization status of the first access and backhaul integrated IAB node. The first IAB node includes a first distributed unit and a first mobile terminal. There is an RRC connection between the first mobile terminal and the second host node. There is an F1 connection between the first distributed unit and the first host node or an attempt to establish an F1 connection. The first host node and the second host node are different host nodes.

[0048] In a possible implementation, the apparatus further includes: a receiving module configured to receive identification information of the first host node sent by the first IAB node.

[0049] In a possible implementation, the sending module sending the IAB authorization information to the first host node includes: the AMF sending the IAB authorization information to the first host node according to the identification information of the first host node.

[0050] In a possible implementation, the receiving module is further configured to receive identification information of the first host node sent by the second host node.

[0051] In a possible implementation, the sending module sending the IAB authorization information to the first host node includes: the AMF sending the IAB authorization information to the first host node according to the identification information of the first host node.

[0052] In the fifteenth aspect, a communication device is provided, which is a host node that has an F1 connection with a first logical distributed unit. The device includes: a sending module for sending access backhaul integrated IAB authorization information to the first host node, and the IAB authorization information is used to indicate the authorization status of the first IAB node. The first IAB node includes a first distributed unit and a first mobile terminal. The first distributed unit includes a first logical distributed unit and a second logical distributed unit. There is an RRC connection between the first mobile terminal and the second host node, and the second logical distributed unit has an F1 connection with the first host node or attempts to establish an F1 connection.

[0053] In the sixteenth aspect, a communication device is provided, including: a sending module for sending identification information of a first host node to a core network access and mobility management function AMF, wherein the first IAB node includes a first distributed unit and a first mobile terminal, an RRC connection exists between the first mobile terminal and the second host node, an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection, and the AMF is used to send IAB authorization information to the first host node according to the identification information of the first host node, and the IAB authorization information is used to indicate the authorization status of the first IAB node.

[0054] In the seventeenth aspect, a communication device is provided, including: a sending module for sending identification information of a first host node to a core network access and mobility management function AMF, an RRC connection exists between the second host node and a first mobile terminal, the first mobile terminal is a mobile terminal in a first access and backhaul integrated IAB node, the first IAB node also includes a first distributed unit, an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection, the AMF is used to send IAB authorization information to the first host node according to the identification information of the first host node, and the IAB authorization information is used to indicate the authorization status of the first IAB node.

[0055] In aspect 18, a communication device is provided, including: a sending module for sending identification information of a first host node to a second host node, the second host node is a host node that has an RRC connection with a first mobile terminal, the first host node is a host node that has an F1 connection with a first distributed unit or attempts to establish an F1 connection, and the third host node is a host node that has an RRC connection with the first mobile terminal before the first mobile terminal establishes an RRC connection with the second host node.

[0056] In the nineteenth aspect, a wireless communication device is provided, comprising modules or units for executing the method in the first aspect or any possible implementation of the first aspect.

[0057] In the twentieth aspect, a wireless communication device is provided, comprising modules or units for executing the method in the second aspect or any possible implementation of the second aspect.

[0058] In aspect 21, a wireless communication device is provided, comprising modules or units for executing the method in aspect 3 or any possible implementation of aspect 3.

[0059] In aspect 22, a wireless communication device is provided, comprising modules or units for executing the method in aspect 4 or any possible implementation of aspect 4.

[0060] In aspect twenty-third, a wireless communication device is provided, comprising modules or units for executing the method in aspect five or any possible implementation of aspect five.

[0061] In aspect 24, a wireless communication device is provided, comprising modules or units for executing the method in aspect 6 or any possible implementation of aspect 6.

[0062] In aspect 25, a wireless communication device is provided, comprising modules or units for executing the method in aspect 7 or any possible implementation of aspect 7.

[0063] In aspect twenty-six, a wireless communication device is provided, comprising modules or units for executing the method in aspect eight or any possible implementation of aspect eight.

[0064] In aspect twenty-seven, a wireless communication device is provided, comprising modules or units for executing the method in aspect nine or any possible implementation of aspect nine.

[0065] In a twenty-eighth aspect, a communication device is provided, comprising a processor coupled to a memory and configured to execute the method of the first aspect and possible implementations thereof, the second aspect and possible implementations thereof, the third aspect and possible implementations thereof, the sixth aspect and possible implementations thereof, the eighth aspect and possible implementations thereof, or the ninth aspect and possible implementations thereof. In one possible implementation, the communication device further comprises a memory. In one possible implementation, the communication device further comprises a communication interface, the processor coupled to the communication interface. In one possible implementation, the communication device further comprises a communication interface, the processor coupled to the communication interface.

[0066] In one implementation, the communication device is a host node. When the communication device is a host node, the communication interface may be a transceiver, or an input / output interface.

[0067] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits on the chip or chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0068] In a twenty-ninth aspect, a communication device is provided, comprising a processor coupled to a memory and configured to execute instructions in the memory to implement the method of the fourth aspect and possible implementations thereof or the seventh aspect and possible implementations thereof. In one possible implementation, the communication device further comprises a memory. In one possible implementation, the communication device further comprises a communication interface, and the processor is coupled to the communication interface. In one possible implementation, the transceiver may be a transceiver circuit. In one possible implementation, the input / output interface may be an input / output circuit.

[0069] In one implementation, the communication device is an IAB node. When the communication device is an IAB node, the communication interface may be a transceiver or an input / output interface. In one possible implementation, the transceiver may be a transceiver circuit. In another possible implementation, the input / output interface may be an input / output circuit.

[0070] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits on the chip or chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0071] In a 30th aspect, a communication device is provided, comprising a processor coupled to a memory and configured to execute instructions in the memory to implement the method of the fifth aspect and its possible implementations. In one possible implementation, the communication device further comprises a memory. In one possible implementation, the communication device further comprises a communication interface, and the processor is coupled to the communication interface. In one possible implementation, the transceiver may be a transceiver circuit. In one possible implementation, the input / output interface may be an input / output circuit.

[0072] In one implementation, the communication device is an AMF. When the communication device is an AMF, the communication interface may be a transceiver or an input / output interface. In one possible implementation, the transceiver may be a transceiver circuit. In another possible implementation, the input / output interface may be an input / output circuit.

[0073] In another implementation, the communication device is a chip or a chip system. When the communication device is a chip or a chip system, the communication interface may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuits on the chip or chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0074] In a thirty-first aspect, a communication device is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal via the input circuit and transmit a signal via the output circuit, so that the method of any one of the first to ninth aspects, and any possible implementation of the aforementioned aspects, is implemented.

[0075] In a specific implementation, the communication device may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, or various logic circuits. The input signal received by the input circuit may be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to a transmitter and transmitted by the transmitter. The input circuit and the output circuit may be different circuits or the same circuit, in which case the circuit functions as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation of the processor and various circuits.

[0076] In aspect 32, a processing device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory and receive signals via a receiver and transmit signals via a transmitter to execute the method of any one of aspects 1 to 9, and any possible implementation of any of the above aspects.

[0077] In a possible implementation, there are one or more processors and one or more memories.

[0078] In a possible implementation, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0079] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0080] It should be understood that related data interaction processes, such as sending indication information, can be the process of outputting indication information from the processor, and receiving capability information can be the process of receiving input capability information from the processor. Specifically, the output data of the processing can be output to the transmitter, and the input data received by the processor can come from the receiver. The transmitter and receiver can be collectively referred to as a transceiver.

[0081] The processor in the above aspects can be a chip, which can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated in the processor or located outside the processor and exist independently.

[0082] In aspect thirty-third, a computer program product is provided, comprising: a computer program (also referred to as code, or instructions), which, when run, enables a computer to execute any one of aspects one to nine, and any possible implementation of the above aspects.

[0083] In aspect thirty-four, a computer-readable medium is provided, which stores a computer program (also referred to as code, or instructions) which, when run on a computer, enables the computer to execute any one of the first to ninth aspects mentioned above, as well as any possible implementation of the above aspects.

[0084] In the thirty-fifth aspect, a communication system is provided, comprising at least one of the aforementioned first host node, second host node, third host node, fourth host node, first IAB node and AMF. BRIEF DESCRIPTION OF THE DRAWINGS

[0085] FIG1 is an architecture diagram of an IAB system applicable to the technical solution of the present application.

[0086] FIG2 is a schematic diagram of the composition of an IAB node.

[0087] FIG3 is a schematic diagram of the IAB network control plane and user plane protocol stack.

[0088] FIG4 is a schematic flow chart of an IAB node accessing the network.

[0089] FIG5 is a schematic diagram of a local migration scenario of an IAB node.

[0090] FIG6 is a schematic diagram of an IAB topology redundancy scenario.

[0091] FIG7 is a schematic diagram of a scenario in which a mobile IAB node continuously migrates locally.

[0092] FIG8 is a schematic diagram of an IAB node DU migration scenario.

[0093] FIG9 is a schematic flow chart of an IAB authorization information transmission method provided by this application.

[0094] FIG10 is a schematic flowchart of another IAB authorization information transmission method provided by this application.

[0095] FIG11 is a schematic flowchart of another IAB authorization information transmission method provided by the present application.

[0096] FIG12 is a schematic flowchart of another IAB authorization information transmission method provided by the present application.

[0097] FIG13 is a schematic flowchart of another IAB authorization information transmission method provided by the present application.

[0098] FIG14 is a schematic flowchart of another IAB authorization information transmission method provided by the present application.

[0099] FIG15 is a schematic flowchart of another IAB authorization information transmission method provided by the present application.

[0100] FIG16 is a schematic flowchart of another IAB authorization information transmission method provided by the present application.

[0101] FIG17 is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0102] Figure 18 is a schematic block diagram of another communication device provided in an embodiment of the present application.

[0103] FIG19 is a schematic diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0104] The technical solution in this application will be described below with reference to the accompanying drawings.

[0105] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Wireless Fidelity (WIFI), Device to Device (D2D) communication system, Vehicle-to-Everything (V2X) communication system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, Machine to Machine (M2M) system, Machine Type Communication (MTC) system, Internet of Things (IoT) system. things, IoT) communication systems, non-terrestrial network (NTN) systems, the 5th Generation (5G) mobile communication systems or new radio (NR) systems or future wireless communication systems.

[0106] First, a brief introduction to the network architecture applicable to this application is given.

[0107] In this application, a relay node supporting integrated access and backhaul is referred to as an IAB node to distinguish it from a relay in LTE (long term evolution, LTE). A system including an IAB node is also referred to as a relay system.

[0108] It should be understood that the names of all nodes and information in this application are merely names set for the convenience of description in this application. The names in the actual network may be different. This application should not be understood as limiting the names of various nodes and information. On the contrary, any name with the same or similar function as the node or information used in this application is regarded as a method or equivalent replacement of this application, and is within the scope of protection of this application. No further details will be given below.

[0109] In order to design flexible and convenient access and backhaul solutions, both the access link (AL) and the backhaul link (BL) in the IAB scenario adopt wireless transmission solutions.

[0110] In a network containing IAB nodes (hereinafter referred to as the IAB network), the IAB nodes can provide wireless access services for terminal devices. The UE connects to the IAB node through a wireless access link and connects to the host node (IAB donor / donor node) through a wireless backhaul link to transmit user business data.

[0111] Exemplarily, the host node may be a host base station. The host node may be referred to as an IAB donor or DgNB (i.e., donor gNodeB) in a 5G network. The host node may be a complete entity, or it may be a form in which a centralized unit (CU) (referred to herein as Donor-CU, or simply as CU) and a distributed unit (DU) (referred to herein as Donor-DU) are separated, that is, the host node is composed of a Donor-CU and a Donor-DU. In the embodiments of the present application and in the accompanying drawings, the method provided in the embodiments of the present application is exemplified by taking the example of a host node consisting of a Donor-CU and a Donor-DU as an example.

[0112] An IAB node consists of a mobile termination (MT) part and a distributed unit (DU) part. When an IAB node faces its parent node, it can be regarded as a terminal device. In this case, the IAB node plays the role of an MT. When an IAB node faces its child node (the child node may be a terminal device or the terminal device part of another IAB node), it can be regarded as a communication device. In this case, the IAB node plays the role of a DU. Therefore, it can be considered that an IAB node consists of an MT part and a DU part. An IAB node can establish a backhaul connection with at least one parent node of the IAB node through the MT part. The DU part of an IAB node can provide access services for terminal devices or the MT part of other IAB nodes.

[0113] Among them, the Donor-CU can also be a form in which the user plane (UP) (abbreviated as CU-UP in this article) and the control plane (CP) (abbreviated as CU-CP in this article) are separated, that is, the Donor-CU consists of the CU-CP and the CU-UP.

[0114] The IAB node is connected to the core network via a wired link via the donor node. For example, in a standalone 5G architecture, the IAB node is connected to the 5G core (5GC) via a wired link via the donor node. In a non-standalone 5G architecture, the IAB node is connected to the evolved packet core (EPC) via the eNB on the control plane and to the EPC via the donor node and eNB on the user plane.

[0115] To ensure reliable service transmission, the IAB network supports multi-hop and multi-connection IAB node networking. Therefore, multiple transmission paths may exist between a terminal device and a host node. Within a path, IAB nodes maintain a defined hierarchical relationship between each other and between IAB nodes and the host node they serve. Each IAB node considers the node providing backhaul services to be its parent node. Accordingly, each IAB node can be considered a child of its parent node.

[0116] For example, referring to Figure 1, the parent node of IAB node 1 is the host node, which is in turn the parent node of IAB node 2 and IAB node 3. IAB node 2 and IAB node 3 are both the parent nodes of IAB node 4, and the parent node of IAB node 5 is IAB node 3. The uplink data packet of the terminal device can be transmitted to the host node via one or more IAB nodes, and then sent by the host node to the mobile gateway device (such as the UPF network element in the 5G network). The downlink data packet will be received by the host node from the mobile gateway device and then sent to the terminal device via one or more IAB nodes. There are two available paths for the transmission of data packets between terminal device 1 and the host node: terminal device 1 → IAB node 4 → IAB node 3 → IAB node 1 → host node, and terminal device 1 → IAB node 4 → IAB node 2 → IAB node 1 → host node. There are three available paths for data packet transmission between terminal device 2 and the host node, namely: terminal device 2 → IAB node 4 → IAB node 3 → IAB node 1 → host node, terminal device 2 → IAB node 4 → IAB node 2 → IAB node 1 → host node, and terminal device 2 → IAB node 5 → IAB node 2 → IAB node 1 → host node.

[0117] It is understandable that in the IAB network, a transmission path between a terminal device and a host node may include one or more IAB nodes. Each IAB node needs to maintain a wireless backhaul link to the parent node, and also needs to maintain a wireless link with the child node. If an IAB node is a node accessed by a terminal device, there is a wireless access link between the IAB node and the child node (i.e., the terminal device). If an IAB node is a node that provides backhaul services to other IAB nodes, there is a wireless backhaul link between the IAB node and the child node (i.e., other IAB nodes). For example, see Figure 1, in the path "terminal device 1→IAB node 4→IAB node 3→IAB node 1→host node". Terminal device 1 accesses IAB node 4 via a wireless access link, IAB node 4 accesses IAB node 3 via a wireless backhaul link, IAB node 3 accesses IAB node 1 via a wireless backhaul link, and IAB node 1 accesses the host node via a wireless backhaul link.

[0118] For example, the IAB node may be a customer premises equipment (CPE), a residential gateway (RG), etc. In this case, the method provided in the embodiment of the present application may also be applied to a home access scenario.

[0119] The above IAB networking scenarios are merely exemplary. In the IAB scenario combining multi-hop and multi-connection, there are many other possibilities for IAB networking scenarios, for example, a host node and an IAB node under another host node form a dual connection to serve a terminal device, etc., which are not listed here one by one.

[0120] Figure 2 shows a schematic diagram of the system architecture applicable to an embodiment of the present application. As shown in Figure 2, IAB (or IAB device) is a wireless backhaul base station. Its particularity is that IAB must first establish a backhaul channel with the target macro station, and then provide wireless coverage services to the outside world. It is similar to customer premise equipment (CPE), but the difference is that CPE provides wireless fidelity (WIFI) coverage to the outside world. IAB provides base station wireless signals to the outside world, such as the fifth generation (5G) signal. IAB is mainly used to extend the coverage of macro stations. It uses the high-power multi-antenna reception characteristics of its backhaul device to extend the remote coverage of macro stations, and change the weak coverage area that was originally a far point for the macro station into a good coverage area at a medium or near point. Since IAB needs to establish a connection relationship with a fixed macro station, it usually requires precise access to the target macro station to establish a backhaul channel.

[0121] In the IAB network architecture shown in Figure 2, taking a standalone (SA) network as an example, the IAB donor can be composed of a centralized unit (CU) and a distributed unit (DU). This means that the IAB donor's functions are split, with some functions deployed in a CU and the remaining functions in a DU. Multiple DUs share a single CU, saving costs and facilitating network expansion. The CU and DU are connected via the F1 interface. The CU, representing the IAB donor, connects to the core network via the next-generation (NG) interface, and connects to other gNBs via the Xn interface.

[0122] The IAB node DU (abbreviated as IAB-DU in this application) is logically connected to the IAB donor CU (abbreviated as CU in this application) via the F1 interface. In practice, the connection between the IAB-DU and the CU is achieved through the NR Uu interface between the IAB-MT and the parent node DU at each hop. However, since the IAB-DU can ultimately communicate with the CU, the F1 interface can be considered to exist logically. The IAB-MT function is defined as a component similar to a UE. In an IAB network, the MT is referred to as a function residing on the IAB node. Because the MT functions similarly to a regular UE, the IAB node can be considered to access the upper-level node or network through the MT.

[0123] Figure 3 shows the user and control plane protocol stacks in an IAB network. The F1 interface supports user plane protocols (F1-U) and control plane protocols (F1-C). As shown in Figure 3(b), the user plane protocols include one or more of the following protocol layers: General Packet Radio Service Tunneling Protocol User Plane (GTP-U), User Datagram Protocol (UDP), and Internet Protocol (IP). As shown in Figure 3(a), the control plane protocols include one or more of the following protocol layers: F1AP (F1 Application Protocol), SCTP (Stream Control Transport Protocol), and IP. Through F1-C, IAB donors and IAB nodes can manage interfaces, manage IAB-DUs, and perform UE context-related configuration. Through F1-U, IAB donors and IAB nodes can transmit user plane data and provide downlink transmission status feedback.

[0124] It should be noted that Figures 1 and 2 above are merely examples, and the technical solution of this application can be applied to various communication systems including access network units. For example, the access network unit can be, for example, the IAB in Figure 1 or the gNB in ​​Figure 2. Furthermore, the communication system may also include a terminal device.

[0125] The terminal device involved in the embodiments of the present application may also be referred to as a terminal, which may be a device with wireless transceiver functions, which may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it may also be deployed on the water (such as ships, etc.); it may also be deployed in the air (such as airplanes, balloons, and satellites, etc.). The terminal device may be a user equipment (UE). Among them, the UE includes a handheld device, a vehicle-mounted device, a wearable device, or a computing device with wireless communication functions. Exemplarily, the UE may be a mobile phone, a tablet computer, or a computer with wireless transceiver functions, etc. In addition, the terminal device may also be a device that can support the terminal to implement the function, such as a chip or a chip system, which may be installed in the terminal. In the technical solution provided in the embodiments of the present application, the technical solution provided in the embodiments of the present application is described by taking the terminal as an example in which the device for implementing the function of the terminal is a terminal. It should be understood that terminal is a general term, including the most common mobile phones, CPE, and integrated access backhaul (IAB) terminals. Terminal devices can also be virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in unmanned driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in smart cities, wireless terminals in smart homes, and so on.

[0126] The network equipment involved in the embodiments of the present application includes a base station (BS), which can be a device deployed in a wireless access network that can communicate wirelessly with a terminal. Among them, the base station may have various forms, for example, a macro base station, a micro base station, a relay station and an access point, a backhaul station, etc. Exemplarily, the base station involved in the embodiments of the present application may be a base station in 5G or a base station in LTE. Among them, the base station in 5G can also be called a transmission reception point (TRP) or a next generation base station (next generation nodded, gNB). In the embodiments of the present application, the device for realizing the function of the network device may be a network device; it may also be a device that can support the network device to realize the function, such as a chip or a chip system, which can be installed in the network device. In the technical solution provided in the embodiments of the present application, the device for realizing the function of the network device is a network device, and the network device is a base station as an example to describe the technical solution provided in the embodiments of the present application.

[0127] In the embodiment of the present application, the chip system can be composed of chips, or can include chips and other discrete devices.

[0128] It should be understood that the network architecture shown above is only an exemplary illustration, and the network architecture applicable to the embodiments of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0129] It should also be understood that the above naming is only defined to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in 6G networks and other future networks.

[0130] It should also be understood that the interface names between the various network elements in Figure 2 are merely examples, and in specific implementations, the interface names may be other names, which are not specifically limited in this application. In addition, the names of the information (or signaling) transmitted between the aforementioned network elements are merely examples and do not constitute any limitation on the function of the information itself.

[0131] The following describes the IAB node integration process. Figure 4 is a flowchart of the IAB node integration process, taking the integration process of IAB node 2 as an example. IAB node 1 is its parent node and is already in the network.

[0132] The IAB node network access process can be summarized as follows:

[0133] Phase 1: The IAB-MT accesses the cell in a manner similar to that of an ordinary UE, establishes an RRC connection with the donor node, and indicates that it is an IAB node when establishing the RRC connection (the IAB node indication is carried in the RRC Setup Complete message). When the CU sends the UE initial message (INITIAL UE Message) to the core network (specifically, the AMF network element in the core network), it also carries the IAB-node indication. The AMF authenticates the IAB-MT and carries an IAB authorization information element (IAB authorized information element, i.e., "IAB authorization information" in this invention) in the message instructing the CU to establish the UE initial context for the IAB-MT (INITIAL CONTEXT SETUP REQUEST). If the authentication is successful, the value of the IAB authorization information element is authorized; otherwise, the value of the IAB authorization information element is not authorized. Since this describes the network access process of the IAB node, it is assumed that the value of the IAB authorization information element is authorized, and the subsequent steps are performed.

[0134] Phase 2: The CU configures the backhaul link RLC channel (BH RLC Channel) and performs routing configuration for the IAB node through RRC messages. Specifically, only a default backhaul link RLC channel and a default route are configured at this time for use when the F1 interface is initially established (see Phase 3 for details). After the F1 interface is established, more backhaul link RLC channels and routing paths can be configured to the IAB node through F1-C information for subsequent use of more F1-C information and F1-U user plane data. In Phase 2, in addition to configuring IAB node 2, routing updates are also performed on the nodes between the IAB node and the donor (IAB node 1), informing these nodes how to select the next-hop link and next-hop RLC channel when receiving data packets from or sending data packets to IAB node 2.

[0135] Phase 3: IAB-DU2 uses the default configuration obtained in Phase 2 to initiate an F1 connection establishment request (F1 SETUP REQUEST message) to the donor-CU, carrying the cell configuration information of DU2, requesting to establish the F1 interface. The donor-CU replies with an F1 connection establishment response (F1 SETUP RESPONSE) message to IAB-DU2, activates the cell, and completes the F1 interface establishment. At this point, IAB-DU2 has been activated and can provide services to the UE and the next-hop IAB-MT.

[0136] If the value of the IAB authorization information element is authorized, the donor-CU will perform subsequent procedures (including configuring the return link RLC channel, etc.) according to the above description of IAB network access. If the value of the IAB authorization information element is not authorized, it means that this IAB node is not allowed to provide IAB services. The donor-CU may perform the following operations, for example, not configuring the default configuration for the IAB-MT, or configuring the default configuration for the IAB-MT but rejecting the F1 connection establishment request initiated by the IAB-DU.

[0137] In addition to the IAB authorization information sent by the AMF to the CU when the IAB node initially joins the network, if the IAB authorization status changes later (for example, because the IAB moves to a specific location or the IAB service time is specified), the AMF will send the updated IAB authorization information element value to the CU through the UE CONTEXT MODIFICATION REQUESET.

[0138] The large-scale mobility of IAB nodes will cause some impact on the core network side. Mobile IAB nodes require a separate authorization information element, the mobile IAB authorization information element, which is used in exactly the same way as the IAB authorization information element.

[0139] It is uniformly explained here that the IAB node in this application can be a common IAB node or a mobile IAB node. Correspondingly, when the IAB node is a mobile IAB node, its IAB authorization information uses a mobile IAB authorization information element (mobile IAB Authorized), which is not limited in this application.

[0140] The above describes the basic concepts of IAB and the network access process. The following describes some IAB features related to topology changes. Specifically, these features are all inter-CU (inter-donor CU)-related. In the case of non-inter-CU (intra-donor CU) and inter-donor DU (inter-donor DU)-related scenarios, although inter-donor DUs exist, reconfiguration by the CU is sufficient because there is no inter-CU interaction. However, the following scenarios require inter-CU interaction.

[0141] 1. Partial migration

[0142] Figure 5 illustrates the partial migration of an IAB node. The IAB node undergoing migration is called a boundary node, such as IAB node2. Downstream nodes from a boundary node are called descendant nodes, such as IAB node4. Before migration, an RRC connection existed between IAB-MT2 and CU1, an F1 interface existed between IAB-DU2 and CU1, and IAB node2 communicated with the IAB donor via the source path (through IAB node1, which consists of IAB-MT1 and IAB-DU1). During partial migration, IAB-MT2 underwent an inter-CU cell handover and established an RRC connection with CU2.

[0143] To avoid the need to re-establish the F1 interface, during partial migration, IAB-DU2 maintains the F1 interface with CU1 and does not establish an F1 interface with CU2. As a result, the communication path between CU1 and IAB-DU2 becomes cross-topology: In Figure 5, CU1 and CU2 are referred to as the F1-terminating CU and non-F1-terminating CU, respectively, and can also be referred to as the source CU and target CU. It's important to note that data transmitted along this path does not pass through CU2; CU1 and Donor-DU2 communicate directly over the IP network.

[0144] The F1 anchor CU sends an IAB TRANSPORT MIGRATION MANAGEMENT (IAB REQUEST) message to the non-F1 anchor CU to request the establishment of cross-topology traffic transmission. If the non-F1 anchor CU agrees to establish the transmission, it replies with an IAB TRANSPORT MIGRATION MANAGEMENT (IAB RESPONSE) message to the F1 anchor CU. If it disagrees, it replies with an IAB TRANSPORT MIGRATION MANAGEMENT (IAB REJECT) message. If the F1 anchor CU or the non-F1 anchor CU subsequently want to modify or withdraw the QoS of the traffic, they can also exchange IAB TRANSPORT MIGRATION MODIFICATION (IAB REQUEST / RESPONSE) messages.

[0145] 2. Topology redundancy (or dual connectivity)

[0146] As shown in Figure 6, in NR, the UE can perform dual connectivity, connecting to two different base stations to improve throughput and robustness. IAB-MT can also perform dual connectivity, connecting to two different CUs. Data between the IAB-DU and the CU (specifically, the F1 anchor CU) can be transmitted simultaneously over two paths, doubling the throughput. There is an RRC connection between the IAB-MT and both CU1 and CU2, and an F1 interface between the IAB-DU2 and CU1. For data transmission through the blue path, as with local migration, it also communicates through the IP network of CU1 and donor-DU2, without passing through CU2.

[0147] 3. Radio Link Failure Recovery (RLF Recovery)

[0148] When an RLF occurs between the IAB-MT and the source cell, it selects another cell to initiate RRC re-establishment, which may be in another CU. After an inter-CU RRC re-establishment occurs for IAB-MT2, the topology remains the same as for local migration. The RRC connection of IAB-MT2 is moved to CU2, while the F1 interface of IAB-DU2 remains on CU1. The signaling interactions for RLF recovery and local migration differ, but the final state is the same.

[0149] 4. Consecutive partial migration

[0150] As shown in Figure 7, when the MT switches from CU2 to CU3, the F1 interface of the DU is always associated with CU1. Here, mAB is the abbreviation of mobile IAB. The mAB node in Figure 7 is directly connected to the donor-DU, but there may be other IAB nodes between the mAB node and the donor-DU, and this application is not limited to this. In addition, the MT may be switched from CU1 to CU2 (for example, Figure 7), or it may be switched from other CUs to CU2 (which can be understood in conjunction with the DU migration scenario below).

[0151] 5. DU migration

[0152] When the mAB node moves far away, it may be difficult for the mAB-DU to maintain an IP connection with the original CU, or the transmission delay may be very large. Therefore, in order to support large-scale mobility, DU migration is introduced. As shown in Figure 8, the MT's RRC connection is always on CU2, and the DU's F1 interface is migrated from CU1 to CU3. The figure shows mAB-DU1 and mAB-DU2, which are two logical DUs on a physical DU. DU migration is achieved in this way: assuming that the source DU is mAB-DU1, the mAB node generates a new logical DU mIAB-DU2, and mAB-DU2 establishes an F1 interface with CU3. CU1 sends a UE handover request to CU3, switching the UE from the cell under mAB-DU1 to the cell under mAB-DU2. Then CU1 releases the F1 interface between itself and mAB-DU1, and DU migration is completed. Among them, CU1 is the source F1 anchor CU of IAB-DU, CU3 is the target F1 anchor CU of IAB-DU, and CU2 is the MT CU (also called RRC terminating CU).

[0153] Assume that DU migration and MT migration are completely decoupled, that is, the CU of the DU and the CU of the MT can always be different. Therefore, in continuous local migration, if the F1 anchor CU of the DU is always CU1, the MT does not necessarily switch from CU1 to CU2. This is just one of many implementation methods. In DU migration, the MT can be in CU2 while the DU migrates from CU1 to CU3. Optionally, CU2 can be the same CU as CU1 or CU3.

[0154] The reason why DU migration is assumed to be completely decoupled from MT migration is that the DU migration process is relatively complex (it requires generating two logical DUs and switching UEs to the new logical DUs one by one). DU migration is not suitable for frequent use, so the DU CU should be a CU with a relatively large control range. MT migration is MT switching, which may be performed frequently. The selection of the MT CU is determined by signal quality, so the MT CU may be different from the DU CU.

[0155] 6. IAB integration to different CUs

[0156] Based on the assumption that DU and MT migration are completely decoupled, during the IAB integration process, the MT's RRC connection and the DU's F1 interface can be terminated on different CUs (for example, the DU's CU has a larger control range, while the MT's CU corresponds to the cell with the best signal quality). In other words, the topology shown in Figure 5 is established as soon as the IAB node joins the network.

[0157] In many scenarios (such as IAB node migration scenarios), the CU of the IAB-MT and the CU of the IAB-DU may be different. In some implementations, the CU of the IAB-DU is required to know the IAB authorization information of the IAB-MT. For example, when the IAB node initially joins the network, if the CU of the IAB-MT configures the MT with a default configuration and the IAB-DU sends an F1 interface establishment request to its CU, the CU of the IAB-DU needs to know whether the IAB node is authorized or unauthorized in order to perform corresponding operations (e.g., when the IAB node is unauthorized, reject the IAB-DU's F1 interface establishment request). However, the prior art does not consider how the CU of the IAB-DU can obtain the current IAB authorization information when the CU of the IAB-MT and the CU of the IAB-DU are different.

[0158] The present application provides a variety of communication methods. As examples and not limitations, when the IAB authorization information is updated, the latest IAB authorization information can be notified to the CU of the IAB-DU, so that the CU of the IAB-DU can determine whether to delete the F1 interface / whether to allow the establishment of the F1 interface / whether to shut down the cell under the IAB-DU / whether to configure the cell under the IAB-DU to prohibit UE access, etc. based on the authorization information. This is conducive to the network side to flexibly control the IAB node and meet the requirements of allowing or prohibiting the IAB node from working within a specific time / space range.

[0159] It should be understood that when the present invention mentions ordinal numbers such as "first", "second", "third", "fourth" and "fifth", unless they do express the meaning of order according to the context, they should be understood as being merely for the purpose of distinction.

[0160] Depending on the specific scenario, the method for notifying the CU of the IAB-DU of the latest IAB authorization information also varies. It should be understood that the description of the specific scenario in the embodiments of the present application is only an example. In addition to being applicable to the application scenarios described above, the methods provided in the embodiments of the present application are also applicable to application scenarios with similar problems.

[0161] The following describes several methods for informing the CU of the IAB-DU of the latest IAB authorization information. The following methods are applicable to scenarios where the CU of the IAB-MT and the CU of the IAB-DU are different.

[0162] Method 1

[0163] The following example uses the continuous local migration scenario shown in Figure 7. In Figure 7, CU1 is the DU's F1 anchor CU, CU2 is the MT's source CU, and CU3 is the MT's target CU. In Method 1, the MT's target CU first notifies the MT's source CU, which then notifies the DU's F1 anchor CU. This method is suitable for continuous local migration scenarios.

[0164] FIG9 shows a schematic flowchart 900 of method 1 . The method in FIG9 includes at least part of the following contents.

[0165] S910: The MT switches from CU2 to CU3.

[0166] Specifically, before migration, there is an RRC connection between the IAB-MT and CU2, and an F1 interface between the IAB-DU and CU1. During local migration, the IAB-MT undergoes an inter-CU cell handover and establishes an RRC connection with CU3, but the IAB-DU maintains an F1 interface with CU1 and does not establish an F1 interface with CU3.

[0167] S920: AMF sends IAB authorization information to CU3.

[0168] In one possible implementation, before the AMF sends the IAB authorization information to CU3, CU3 first sends a path switch request message to the AMF, informing the AMF that the MT has been switched to CU3 and that the AMF transfers the MT's services to CU3. The AMF replies to CU3 with a path switch request confirmation (PATH SWITCH REQUEST ACK) message, which carries the value of the current IAB authorization information element and / or mobile IAB authorization information element (i.e., IAB authorization information).

[0169] In another possible implementation, when the AMF discovers that the IAB authorization information has changed, the AMF carries the value of the current IAB authorization information element and / or mobile IAB authorization information element (i.e., the IAB authorization information) in the UE CONTEXT MODIFICATION REQUEST.

[0170] S930: CU3 sends IAB authorization information to CU2.

[0171] Specifically, CU3 sends a message to CU2, carrying the authorization information of the (mobile) IAB.

[0172] In a possible implementation, the indication information sent by CU3 to CU2 directly carries a (mobile) IAB authorization information element, where the value of the (mobile) IAB authorization information element includes authorized or not authorized.

[0173] In another possible implementation, only when authorization is not granted, the information carries a (mobile) IAB authorization information element, in which case the value of the information element is not authorized, or the indication information carries indication information for releasing the F1 connection or not establishing the F1 connection.

[0174] Optionally, the IAB authorization information also carries an IAB node-related identifier to indicate which IAB node the authorization information is about. The IAB node-related identifier includes at least one of the following: gNB-DU ID of IAB-DU, UE XnAP ID of IAB-MT under CU1, UE XnAP ID of IAB-MT under CU2, and UE XnAP ID of IAB-MT under CU3.

[0175] In subsequent steps and embodiments, unless otherwise specified, the manner of indicating the IAB authorization information may be the same as that in this step.

[0176] S940: CU2 sends IAB authorization information to CU1.

[0177] Specifically, CU2 sends a message to CU1, carrying the indication information sent by CU3.

[0178] In a possible implementation, this message may be an IAB transport migration modification request message IAB TRANSPORT MIGRATION MODIFICATION REQUEST.

[0179] In another possible implementation, this indication information may carry at least one of the identifier of CU3 (e.g., gNB ID and / or IP address) and the identifier of MT under CU3 (e.g., UE XnAP ID).

[0180] Optionally, the IAB authorization information also carries an IAB node-related identifier, which is used to indicate which IAB node the authorization information is about.

[0181] Method 2

[0182] The following describes Method 2, using the continuous local migration scenario shown in Figure 7 as an example. In Figure 7, CU1 is the DU's F1 anchor CU, CU2 is the MT's source CU, and CU3 is the MT's target CU. In Method 2, the MT's target CU directly notifies the DU's F1 anchor CU. This method is applicable to scenarios involving local migration, continuous local migration, radio link failure recovery, and topology redundancy.

[0183] FIG10 shows a schematic flowchart 1000 of method 2. The method in FIG10 includes at least part of the following contents.

[0184] S1010: MT switches from CU2 to CU3.

[0185] Specifically, before migration, there is an RRC connection between the IAB-MT and CU2, and an F1 interface between the IAB-DU and CU1. During local migration, the IAB-MT undergoes an inter-CU cell handover and establishes an RRC connection with CU3, but the IAB-DU maintains an F1 interface with CU1 and does not establish an F1 interface with CU3.

[0186] S1020: AMF sends IAB authorization information to CU3.

[0187] In one possible implementation, before the AMF sends the IAB authorization information to CU3, CU3 first sends a path switch request message to the AMF, informing the AMF that the MT has been switched to CU3 and that the AMF transfers the MT's services to CU3. The AMF replies to CU3 with a path switch request confirmation message, which carries the value of the current IAB authorization information element and / or mobile IAB authorization information element (i.e., IAB authorization information).

[0188] In another possible implementation, when the AMF discovers that the IAB authorization information has changed, the AMF carries the value of the current IAB authorization information element and / or the mobile IAB authorization information element (i.e., the IAB authorization information) in the UE CONTEXT MODIFICATION REQUEST message.

[0189] Optionally, the IAB authorization information also carries an IAB node-related identifier to indicate which IAB node the authorization information is about. The IAB node-related identifier includes at least one of the following: gNB-DU ID of IAB-DU, UE XnAP ID of IAB-MT under CU1, UE XnAP ID of IAB-MT under CU2, and UE XnAP ID of IAB-MT under CU3.

[0190] S1030 , CU2 sends the identifier of CU1 to CU3 .

[0191] Specifically, CU2 sends an identification message to CU3, so as to let CU3 know that the current F1 anchor CU is CU1.

[0192] S1040 , CU3 sends IAB authorization information to CU1 .

[0193] Specifically, CU3 sends a message to CU1, carrying the authorization information of the (mobile) IAB node.

[0194] In a possible implementation, the indication information sent by CU3 to CU1 directly carries the (mobile) IAB authorization information element, including a value of authorized or not authorized.

[0195] In another possible implementation, only when authorization is not granted, the (mobile) IAB authorization information element "not authorized" is carried in the information, or the indication information carries indication information of releasing the F1 connection or not establishing the F1 connection.

[0196] Optionally, the IAB authorization information also carries an IAB node-related identifier, which is used to indicate which IAB node the authorization information is about.

[0197] It should be understood that in addition to the continuous local migration scenario shown in Figure 7, method 2 can also be used in inter-CU partial migration, inter-CU RLF recovery, and inter-CU topology redundancy (inter-CU topology redundancy) and the scenario where the master node (MN) of the IAB-MT is a non-F1 anchor point (CU3). Assuming that CU2 does not exist, there are only two CUs in these scenarios, namely CU1 and CU3. The IAB-MT migrates from CU1 to CU3. CU1 is both the source CU of the IAB-MT and the F1 anchor point CU of the IAB-DU.

[0198] In different scenarios, some steps S1010 to S1040 of the above method 2 may also be different.

[0199] For the partial migration or RLF recovery scenarios, the migration behavior of the MT in step S1010 is different. In the partial migration scenario, the MT switches from CU1 to CU3. In the RLF recovery scenario, a radio link failure occurs in the MT under CU1, so the MT performs radio link failure recovery from CU1 to CU3 (MT performs RLF recovery from CU1 to CU3). Step S1030 is deleted, and the remaining steps remain unchanged.

[0200] For the topology redundancy scenario, the reason why the MN of IAB-MT is limited to CU3 (SN is CU1) is that in dual connectivity, the RRC connection of IAB-MT is anchored on the MN. Although there is also an RRC connection between SN and IAB-MT, SN plays the role of forwarding RRC messages between MN and IAB-MT. The AMF will send the authorization information of IAB-MT to the MN. Only when the MN is CU3, it is necessary for CU3 to further inform the F1 anchor CU (i.e., CU1) of the authorization information; if the MN is originally CU1 and CU1 is also the F1 anchor CU, there is no technical problem.

[0201] For the topology redundancy scenario, step S1010 should be deleted. Both MN and SN can know which CU is the F1 anchor CU through MN indication, OAM indication, etc. In step S1020, MN obtains the latest authorization information of MT. Since no MT switching or RLF recovery occurs, CU does not interact with AMF in the path switching process. Therefore, the only way to obtain authorization information here is through UE context modification request.

[0202] In addition, for the topology redundancy scenario, it is also applicable to the IAB-MT EN-DC scenario, that is, the primary station of the MT is the MeNB (LTE base station), the secondary station is the SgNB (NR base station), and the secondary station is the F1 anchor host (F1-terminating donor), that is, CU1 is changed to MeNB, CU3 is changed to SgNB, and AMF is changed to MME.

[0203] Method 3

[0204] The following describes Method 3, using the continuous local migration scenario shown in Figure 7 as an example. In Figure 7, CU1 is the DU's F1 anchor CU, CU2 is the mobile station's source CU, and CU3 is the mobile station's target CU. In Method 3, the DU's F1 anchor CU initiates a cross-topology traffic migration process to the mobile station's target CU. The mobile station's target CU responds with the IAB authorization information. Method 3 is applicable to local migration, continuous local migration, radio link failure recovery, and topology redundancy scenarios.

[0205] FIG11 shows a schematic flowchart 1100 of method 3. The method in FIG11 includes at least part of the following contents.

[0206] S1110 , the MT switches from CU2 to CU3 .

[0207] Specifically, before migration, there is an RRC connection between the IAB-MT and CU2, and an F1 interface between the IAB-DU and CU1. During local migration, the IAB-MT undergoes an inter-CU cell handover and establishes an RRC connection with CU3, but the IAB-DU maintains an F1 interface with CU1 and does not establish an F1 interface with CU3.

[0208] S1120: AMF sends IAB authorization information to CU3.

[0209] In one possible implementation, before the AMF sends the IAB authorization information to CU3, CU3 first sends a path switch request message to the AMF, informing the AMF that the MT has been switched to CU3 and that the AMF transfers the MT's services to CU3. The AMF replies to CU3 with a path switch request confirmation message, which carries the value of the current IAB authorization information element and / or mobile IAB authorization information element (i.e., IAB authorization information).

[0210] In another possible implementation, when the AMF discovers that the IAB authorization information has changed, the AMF carries the value of the current IAB authorization information element and / or the mobile IAB authorization information element (i.e., the IAB authorization information) in the UE context modification request.

[0211] Optionally, the IAB authorization information also carries an IAB node-related identifier to indicate which IAB node the authorization information is about. The IAB node-related identifier includes at least one of the following: gNB-DU ID of IAB-DU, UE XnAP ID of IAB-MT under CU1, UE XnAP ID of IAB-MT under CU2, and UE XnAP ID of IAB-MT under CU3.

[0212] S1130 , CU1 sends a cross-topology transmission request to CU3 .

[0213] CU1, as the F1 anchor CU, sends an IAB transport migration management request message to CU3, requesting CU3 to help it establish cross-topology traffic.

[0214] S1140 , CU3 sends IAB authorization information to CU1 .

[0215] Specifically, CU3 carries (mobile) the IAB authorization information in the IAB transfer migration management response or IAB transfer migration management rejection message replied to CU1.

[0216] In a possible implementation, the information sent by CU3 to CU1 directly carries the (mobile) IAB authorization information element, and the value of the information element includes authorized or not authorized.

[0217] In another possible implementation, only when authorization is not granted, the (mobile) IAB authorization information element "not authorized" is carried in the information, or the information carries instruction information for releasing the F1 connection or not establishing the F1 connection.

[0218] In another implementation, when the request is authorized, a migration management response message is sent back to the IAB; when the request is not authorized, a migration management rejection message is sent back to the IAB.

[0219] In another implementation, when authorization is not granted, the cause value carried in the sent IAB transport migration management reject message is indication information about not authorizing the IAB.

[0220] Optionally, the IAB authorization information also carries an IAB node-related identifier, which is used to indicate which IAB node the authorization information is about.

[0221] It should be understood that in addition to the continuous local migration scenario shown in Figure 7, method 3 can also be used in inter-CU partial migration, inter-CU RLF recovery, and inter-CU topology redundancy (inter-CU topology redundancy) and the scenario where the master node (MN) of the IAB-MT is a non-F1 anchor point (CU3). Assuming that CU2 does not exist, there are only two CUs in these scenarios, namely CU1 and CU3. The IAB-MT migrates from CU1 to CU3. CU1 is both the source CU of the IAB-MT and the F1 anchor point CU of the IAB-DU.

[0222] In different scenarios, some steps in steps S1110 to S1140 of the above method 3 may also be different.

[0223] For the partial migration or RLF recovery scenarios, the migration behavior of the MT in step S1110 is different. In the partial migration scenario, the MT switches from CU1 to CU3. In the RLF recovery scenario, a radio link failure occurs in the MT under CU1, so the MT performs radio link failure recovery from CU1 to CU3 (MT performs RLF recovery from CU1 to CU3).

[0224] For the topology redundancy scenario, the reason why the MN of IAB-MT is limited to CU3 (SN is CU1) is that in dual connectivity, the RRC connection of IAB-MT is anchored on the MN. Although there is also an RRC connection between SN and IAB-MT, SN plays the role of forwarding RRC messages between MN and IAB-MT. The AMF will send the authorization information of IAB-MT to the MN. Only when the MN is CU3, it is necessary for CU3 to further inform the F1 anchor CU (i.e., CU1) of the authorization information; if the MN is originally CU1 and CU1 is also the F1 anchor CU, there is no technical problem.

[0225] For the topology redundancy scenario, step S1110 should be deleted. Both MN and SN can know which CU is the F1 anchor CU through MN indication, OAM indication, etc. In step S1120, MN obtains the latest authorization information of MT. Since no MT switching or RLF recovery occurs, CU does not interact with AMF in the path switching process. Therefore, the only way to obtain authorization information here is through UE context modification request.

[0226] In addition, for the topology redundancy scenario, it is also applicable to the IAB-MT EN-DC scenario, that is, the primary station of the MT is the MeNB (LTE base station), the secondary station is the SgNB (NR base station), and the secondary station is the F1 anchor host (F1-terminating donor), that is, CU1 is changed to MeNB, CU3 is changed to SgNB, and AMF is changed to MME.

[0227] Method 4

[0228] The following describes Method 4, using the continuous local migration scenario shown in Figure 7 as an example. In Figure 7, CU1 is the DU's F1 anchor CU, CU2 is the mobile station's source CU, and CU3 is the mobile station's target CU. In Method 4, the IAB-DU notifies the F1 anchor CU of the current IAB authorization information. Method 4 is applicable to scenarios involving local migration, continuous local migration, radio link failure recovery, and topology redundancy.

[0229] FIG12 shows a schematic flowchart 1200 of method 4. The method in FIG12 includes at least part of the following contents.

[0230] S1210: The MT switches from CU2 to CU3.

[0231] Specifically, before migration, there is an RRC connection between the IAB-MT and CU2, and an F1 interface between the IAB-DU and CU1. During local migration, the IAB-MT undergoes an inter-CU cell handover and establishes an RRC connection with CU3, but the IAB-DU maintains an F1 interface with CU1 and does not establish an F1 interface with CU3.

[0232] S1220: AMF sends IAB authorization information to IAB-MT.

[0233] Specifically, the AMF sends a message to the IAB-MT, carrying the (mobile) IAB's authorization information.

[0234] In a possible implementation, the indication information sent by the AMF to the IAB-MT directly carries the (mobile) IAB authorization information element, and the value of the information element is authorized or not authorized.

[0235] In another possible implementation, only when authorization is not granted, the (mobile) IAB authorization information element "not authorized" is carried in the information, or the indication information carries indication information of releasing the F1 connection or not establishing the F1 connection.

[0236] Optionally, the IAB authorization information also carries an IAB node-related identifier to indicate which IAB node the authorization information is about. The IAB node-related identifier includes at least one of the following: gNB-DU ID of IAB-DU, UE XnAP ID of IAB-MT under CU1, UE XnAP ID of IAB-MT under CU2, and UE XnAP ID of IAB-MT under CU3.

[0237] After receiving the IAB authorization information, the IAB-MT informs the IAB-DU of the authorization information through the internal interface.

[0238] S1230 , the IAB-DU sends IAB authorization information to CU1 .

[0239] In a possible implementation, the IAB-DU sends an F1AP message (eg, GNB-DU CONFIGURATION UPDATE) to CU1, carrying the (mobile) IAB authorization information.

[0240] Optionally, the IAB authorization information also carries an IAB node-related identifier, which is used to indicate which IAB node the authorization information is about.

[0241] For methods 1, 2, and 4 above, if the MT's CU switching step is omitted, they can be applied to scenarios where the IAB authorization status change does not occur during the MT's CU switching. In other words, whenever the MT's CU or the MT itself receives the IAB authorization status, it notifies the DU's CU.

[0242] Furthermore, the above methods 1 and 2 can also be applied to the scenario where the MT and DU are connected to two different CUs when the IAB initially joins the network, because in this scenario, the F1 interface has not been established and the CU of the DU cannot be informed through the F1 message.

[0243] It should be understood that in addition to the continuous local migration scenario shown in Figure 7, method 4 can also be used in inter-CU partial migration, inter-CU RLF recovery, and inter-CU topology redundancy (inter-CU topology redundancy) and the scenario where the master node (MN) of the IAB-MT is a non-F1 anchor point (CU3). Assuming that CU2 does not exist, there are only two CUs in these scenarios, namely CU1 and CU3. The IAB-MT migrates from CU1 to CU3. CU1 is both the source CU of the IAB-MT and the F1 anchor point CU of the IAB-DU.

[0244] For the partial migration or RLF recovery scenarios, the migration behavior of the MT in step S1210 is different. In the partial migration scenario, the MT switches from CU1 to CU3. In the RLF recovery scenario, a radio link failure occurs in the MT under CU1, so the MT performs radio link failure recovery from CU1 to CU3 (MT performs RLF recovery from CU1 to CU3).

[0245] For the topology redundancy scenario, the reason why the MN of IAB-MT is limited to CU3 (SN is CU1) is that in dual connectivity, the RRC connection of IAB-MT is anchored on the MN. Although there is also an RRC connection between SN and IAB-MT, SN plays the role of forwarding RRC messages between MN and IAB-MT. The AMF will send the authorization information of IAB-MT to the MN. Only when the MN is CU3, it is necessary for CU3 to further inform the F1 anchor CU (i.e., CU1) of the authorization information; if the MN is originally CU1 and CU1 is also the F1 anchor CU, there is no technical problem.

[0246] Method 5

[0247] In method 5, the CU of the MT tells the AMF which is the CU of the DU (such as CU1 in Figure 7), so that the AMF directly informs the CU of the DU every time it updates the IAB authorization status.

[0248] FIG13 shows a schematic flowchart 1300 of method 5. The method in FIG13 includes at least part of the following contents.

[0249] S1310. Optionally, the IAM-MT sends the gNB-DU ID of the IAB-DU to CU3 to inform CU1 of which DU F1 interface establishment is to be rejected.

[0250] S1320: CU3 sends the identifier of CU1 to the AMF. The identifier of CU1 includes the gNB ID and / or IP address of CU1. Optionally, CU3 also sends the UE NGAP ID of the IAB-MT and / or the gNB-DU ID of the IAB-DU to the AMF to identify the IAB node.

[0251] S1330: AMF sends IAB authorization information to CU1.

[0252] In one possible implementation, the AMF also sends the gNB-DU ID of the IAB-DU and / or the UE NGAP ID of the IAB-MT to CU1.

[0253] Through the above methods 1 to 5, signaling interaction between CUs and signaling interaction between CUs and IAB nodes are introduced, so that when the CU of the IAB-MT is different from the CU of the IAB-DU, the CU of the DU can obtain the current authorization information of the IAB-MT (also referred to as the current authorization information of the IAB node) through signaling interaction.

[0254] The above method describes how to communicate when the CU of the IAB-MT is different from the CU of the IAB-DU in local migration, continuous local migration, wireless link failure recovery, and topology redundancy scenarios.

[0255] In the DU migration scenario, the CU of the IAB-MT may be different from the CU of the IAB-DU. The following takes the DU migration shown in Figure 8 as an example to introduce several communication methods 6, 7 and 8 in this scenario.

[0256] Method 6

[0257] The following describes Method 6 using the DU migration scenario shown in Figure 8 as an example. In Figure 8, CU1 is the source F1 anchor CU, CU2 is the MT CU, and CU3 is the target F1 anchor CU. In Method 6, the source F1 anchor CU informs the target F1 anchor CU of the current IAB authorization information.

[0258] FIG14 shows a schematic flowchart 1400 of method 6. The method in FIG14 includes at least part of the following contents.

[0259] S1410, CU1 sends IAB authorization information to CU3

[0260] Specifically, CU1 sends a message to CU3, which carries IAB authorization information and / or mobile IAB authorization information

[0261] In a possible implementation, the indication information sent by CU1 to CU3 directly carries the (mobile) IAB authorization information element, including a value of authorized or not authorized.

[0262] In another possible implementation, only when authorization is not granted, the (mobile) IAB authorization information element "not authorized" is carried in the information, or the indication information carries indication information of releasing the F1 connection or not establishing the F1 connection.

[0263] In a possible implementation, this message may be a message in which CU1 requests to migrate the IAB-DU to CU3. For example, the message name may be a DU Migration Request message.

[0264] Optionally, the IAB authorization information also carries an IAB node-related identifier to indicate which IAB node the authorization information is about. The IAB node-related identifier includes at least one of the following: gNB-DU ID of IAB-DU, UE XnAP ID of IAB-MT under CU1, UE XnAP ID of IAB-MT under CU2, and UE XnAP ID of IAB-MT under CU3.

[0265] Method 7

[0266] The following describes Method 6 using the DU migration scenario shown in Figure 8 as an example. In Figure 8, CU1 is the source F1 anchor CU, CU2 is the MT CU, and CU3 is the target F1 anchor CU. In this method, the IAB-DU notifies the target F1 anchor CU of the current IAB authorization information.

[0267] FIG15 shows a schematic flowchart 1500 of method 7. The method in FIG15 includes at least part of the following contents.

[0268] S1510: The IAB-DU obtains IAB authorization information.

[0269] In this step, the IAB-DU may be IAB authorization information obtained from different network elements.

[0270] For example, CU1 sends an F1 message to the IAB-DU (a logical DU associated with CU1, IAB-DU1 in FIG8 ) to trigger DU migration. The F1 message carries IAB authorization information.

[0271] In one possible implementation, the IAB authorization information also carries the identifier of CU3 (gNB ID and / or IP address).

[0272] For another example, AMF / CU2 sends an RRC message to IAB-MT, which carries (mobile) IAB authorization information. IAB-MT then informs IAB-DU of the authorization information through an internal interface.

[0273] In a possible implementation, the F1 message sent by CU1 to the IAB-DU or the RRC message sent by AMF / CU2 to the IAB-MT directly carries the (mobile) IAB authorization information element, including the value of authorized or not authorized.

[0274] In another possible implementation, only when authorization is not granted, the (mobile) IAB authorization information element is carried in the F1 message or RRC message as not authorized, or an indication information of releasing the F1 connection or not establishing the F1 connection is carried.

[0275] S1520 , the IAB-DU (logical DU associated with CU3 , IAB-DU2 in FIG8 ) sends IAB authorization information to CU3 .

[0276] Optionally, the IAB authorization information also carries an IAB node-related identifier to indicate which IAB node the authorization information is about. The IAB node-related identifier includes at least one of the following: gNB-DU ID of IAB-DU, UE XnAP ID of IAB-MT under CU1, UE XnAP ID of IAB-MT under CU2, and UE XnAP ID of IAB-MT under CU3.

[0277] Method 8

[0278] The following describes method 6 using the DU migration scenario shown in Figure 8 as an example. In Figure 8, CU1 is the source F1 anchor CU, CU2 is the mobile operator's CU, and CU3 is the target F1 anchor CU. In this method, the mobile operator's CU informs the target F1 anchor CU of the current IAB authorization information.

[0279] FIG16 shows a schematic flowchart 1600 of method 8. The method in FIG16 includes at least part of the following contents.

[0280] In one possible implementation,

[0281] S1610 , CU3 sends an inter-topology transmission request message IAB transmission migration management request to CU2, requesting to establish F1 interface data transmission that passes through the CU2 topology and terminates on CU3;

[0282] S1620 , CU2 carries the (mobile) IAB authorization information in the IAB transfer migration management response or IAB transfer migration management rejection message replied to CU3 .

[0283] Specifically, CU2 carries (mobile) the IAB authorization information in the IAB transfer migration management response or IAB transfer migration management rejection message replied to CU3.

[0284] Optionally, the information sent by CU3 to CU1 directly carries the (mobile) IAB authorization information element, including a value of authorized or not authorized.

[0285] Optionally, only when the authorization is not granted, the (mobile) IAB authorization information element "not authorized" is carried in the information, or the information carries an indication information of releasing the F1 connection or not establishing the F1 connection.

[0286] Optionally, when the request is authorized, an IAB Transmission Migration Management Response message is replied; when the request is not authorized, an IAB Transmission Migration Management Rejection message is replied.

[0287] Optionally, when authorization is not granted, the cause value carried in the sent IAB transport migration management reject message is indication information about not authorizing the IAB.

[0288] In another possible implementation,

[0289] S1610: CU1 sends CU3's identifier (gNB ID and / or IP address) to CU2 to inform CU2 that the DU will be migrated to CU3 or to request CU2 to configure resources for CU3's F1 interface transmission.

[0290] S1620: CU2 sends IAB authorization information to CU3.

[0291] Specifically, CU2 sends a message to CU3, carrying the authorization information of the (mobile) IAB.

[0292] Optionally, the indication information sent by CU3 to CU2 directly carries a (mobile) IAB authorization information element, including a value of authorized or not authorized.

[0293] Optionally, only when authorization is not granted, the indication information carries the (mobile) IAB authorization information element "not authorized", or the indication information carries indication information of releasing the F1 connection or not establishing the F1 connection.

[0294] Optionally, the IAB authorization information also carries an IAB node-related identifier to indicate which IAB node the authorization information is about. The IAB node-related identifier includes at least one of the following: gNB-DU ID of IAB-DU, UE XnAP ID of IAB-MT under CU1, UE XnAP ID of IAB-MT under CU2, and UE XnAP ID of IAB-MT under CU3.

[0295] Figure 17 is a schematic block diagram of a communication device 1700 provided in an embodiment of the present application. The device 1700 includes a transceiver unit 1710 and a processing unit 1720. The transceiver unit 1710 can communicate with the outside world, and the processing unit 1720 is used to process data. The transceiver unit 1710 can also be referred to as a communication interface or a communication unit.

[0296] In a possible implementation, the apparatus 1700 may further include a storage unit, which may be used to store instructions and / or data, and the processing unit 1720 may read the instructions and / or data in the storage unit.

[0297] The device 1700 can be used to execute the actions performed by the host node in the above method embodiment. In this case, the device 1700 can be the first host node, the second host node, the third host node or the fourth host node, or a component that can be configured on the first host node, the second host node, the third host node or the fourth host node. The transceiver unit 1710 is used to execute the transceiver-related operations of the first host node, the second host node, the third host node or the fourth host node in the above method embodiment, and the processing unit 1720 is used to execute the processing-related operations of the first host node, the second host node, the third host node or the fourth host node in the above method embodiment.

[0298] Alternatively, the device 1700 can be used to execute the actions performed by the IAB node in the above method embodiment. In this case, the device 1700 can be an IAB node or a component that can be configured in the IAB node. The transceiver unit 1710 is used to execute the transceiver-related operations on the IAB node side in the above method embodiment, and the processing unit 1720 is used to execute the processing-related operations on the IAB node side in the above method embodiment.

[0299] Alternatively, the device 1700 can be used to execute the actions performed by the AMF in the above method embodiment. In this case, the device 1700 can be an AMF or a component that can be configured on the AMF, the transceiver unit 1710 is used to execute the transceiver-related operations on the AMF side in the above method embodiment, and the processing unit 1720 is used to execute the processing-related operations on the AMF side in the above method embodiment.

[0300] It should also be understood that the device 1700 here is embodied in the form of a functional unit. The term "unit" here can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 1700 can be specifically the first host node, the second host node, the third host node, the fourth host node, the IAB node or the AMF in the above-mentioned embodiments, and can be used to execute the various processes and / or steps corresponding to the first host node, the second host node, the third host node, the fourth host node, the IAB node or the AMF in the above-mentioned various method embodiments. Alternatively, the device 1700 can be specifically the first host node, the second host node, the third host node, the fourth host node, the IAB node or the AMF in the above-mentioned various method embodiments, and can be used to execute the various processes and / or steps corresponding to the first host node, the second host node, the third host node, the fourth host node, the IAB node or the AMF in the above-mentioned various method embodiments. To avoid repetition, it will not be repeated here.

[0301] The apparatus 1700 of each of the above-mentioned schemes has the function of implementing the corresponding steps performed by the first host node, the second host node, the third host node, the fourth host node, the IAB node or the AMF in the above-mentioned method. The functions can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

[0302] In addition, the transceiver unit 1710 may also be a transceiver circuit (for example, may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.

[0303] It should be noted that the apparatus in FIG17 may be a network element or device in the aforementioned embodiment, or may be a chip or chip system, such as a system on chip (SoC). The transceiver unit may be an input / output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip. This is not limited here.

[0304] As shown in FIG18 , an embodiment of the present application further provides a communication device 1800. The communication device 1800 includes a processor 1810, which is coupled to a memory 1820. The memory 1820 is configured to store computer programs, instructions, and / or data. The processor 1810 is configured to execute the computer programs, instructions, and / or data stored in the memory 1820, thereby executing the method in the above method embodiment.

[0305] In one possible implementation, the communication device 1800 includes one or more processors 1810 .

[0306] In a possible implementation, as shown in FIG8 , the communication device 1800 may further include a memory 1820 .

[0307] In a possible implementation, the communication device 1800 may include one or more memories 1820 .

[0308] In a possible implementation, the memory 1820 may be integrated with the processor 1810 or separately provided, or the processor 1820 may be outside the communication device 1800 .

[0309] In one possible implementation, as shown in Figure 8, the wireless communication device 1800 may further include a transceiver 1830, which is configured to receive and / or transmit signals. For example, the processor 1810 is configured to control the transceiver 1830 to receive and / or transmit signals.

[0310] As a solution, the communication device 1800 is used to implement the operations performed by the host node in the above method embodiment.

[0311] For example, the processor 1810 is used to implement the processing-related operations performed by the host node in the above method embodiment, and the transceiver 1830 is used to implement the sending and receiving-related operations performed by the host node in the above method embodiment.

[0312] As another solution, the communication device 1800 is used to implement the operations performed by the IAB node in the above method embodiment.

[0313] For example, the processor 1810 is used to implement the processing-related operations performed by the IAB node in the above method embodiment, and the transceiver 1830 is used to implement the sending and receiving-related operations performed by the IAB node in the above method embodiment.

[0314] As another solution, the communication device 1800 is used to implement the operations performed by the AMF in the above method embodiment.

[0315] For example, the processor 1810 is used to implement the processing-related operations performed by the AMF in the above method embodiment, and the transceiver 1830 is used to implement the sending and receiving-related operations performed by the AMF in the above method embodiment.

[0316] As shown in FIG19 , an embodiment of the present application provides a chip system 1900 . The chip system 1900 (or also referred to as a processing system) includes a logic circuit 1910 and an input / output interface 1920 .

[0317] Logic circuit 1910 may be a processing circuit within chip system 1900. Logic circuit 1910 may be coupled to a storage unit and invoke instructions within the storage unit, enabling chip system 1900 to implement the methods and functions of various embodiments of the present application. Input / output interface 1920 may be an input / output circuit within chip system 1900, outputting information processed by chip system 1900 or inputting data or signaling information to be processed into chip system 1900 for processing.

[0318] As a solution, the chip system 1900 is used to implement the operations performed by the first host node, the second host node, the third host node, the fourth host node, the IAB node or the AMF in the above various method embodiments.

[0319] For example, the logic circuit 1910 is used to implement the processing-related operations by the first host node in the above method embodiment; the input / output interface 1920 is used to implement the sending and / or receiving-related operations by the first host node in the above method embodiment.

[0320] An embodiment of the present application further provides a computer-readable storage medium on which computer instructions are stored for implementing the method executed by a terminal device or a method executed by a satellite in the above method embodiment.

[0321] For example, when the computer program is executed by a computer, the computer can implement the method performed by the end host node, the method performed by the IAB node, or the method performed by the AMF in the above method embodiment.

[0322] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to implement the method performed by the end host node in the above method embodiment, or the method performed by the IAB node, or the method performed by the AMF.

[0323] An embodiment of the present application also provides a communication system, which includes one or more of the first host node, the second host node, the third host node, the fourth host node, the IAB node and the AMF in the above embodiment.

[0324] The explanation and beneficial effects of the relevant contents in any of the wireless communication devices provided above may refer to the corresponding method embodiments provided above, and will not be repeated here.

[0325] In an embodiment of the present application, a terminal device or network device may include a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also known as main memory). The operating system of the operating system layer may be any one or more computer operating systems that implement business processing through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0326] The embodiments of the present application do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of the present application; as long as it is capable of communicating according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application, it is sufficient. For example, the execution subject of the method provided in the embodiments of the present application may be a terminal device or a satellite, or a functional module in the terminal device or satellite that is capable of calling and executing the program.

[0327] Various aspects or features of the embodiments of the present application can be implemented as methods, devices, or articles of manufacture using standard programming and / or engineering techniques. As used herein, the term "article of manufacture" can encompass a computer program accessible from any computer-readable device, carrier, or medium. For example, a computer-readable medium can include, but is not limited to, magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.).

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

[0329] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0330] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM may include the following forms: 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 link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0331] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0332] It should also be noted that the memory described herein is intended to comprise, but not be limited to, these and any other suitable types of memory.

[0333] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of this application.

[0334] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0335] In the several embodiments provided in the embodiments of the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0336] The units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0337] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0338] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0339] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the embodiments of the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: include: The first host node receives access backhaul integrated IAB authorization information, where the IAB authorization information is used to indicate an authorization state of the first IAB node, where the first IAB node includes a first distributed unit and a first mobile terminal, where an RRC connection exists between the first mobile terminal and the second host node, where an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection, and where the first host node and the second host node are different host nodes; The first donor node determines whether to allow the first IAB node to provide a service for the user equipment UE according to the IAB authorization information.

2. A communication method, characterized in that: include: The second host node sends access backhaul integrated IAB authorization information to the first host node, where the IAB authorization information is used to indicate the authorization status of the first IAB node. The first IAB node includes a first distributed unit and a first mobile terminal. An RRC connection exists between the first mobile terminal and the second host node, and an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection.

3. The method according to claim 2, characterized in that Before the second host node sends the IAB authorization information to the first host node, the method further includes: The second host node receives IAB authorization information from the core network access and mobility management function AMF.

4. The method according to claim 2 or 3, characterized in that: Before the second host node sends the IAB authorization information to the first host node, the method further includes: The second host node receives identification information of the first host node from a third host node, where the third host node is a host node that has an RRC connection with the first mobile terminal before the first mobile terminal establishes an RRC connection with the second host node.

5. The method according to claim 4, characterized in that The second host node sending the IAB authorization information to the first host node includes: the second host node sending the IAB authorization information to the first host node according to identification information of the first host node.

6. A communication method, characterized in that: include: The third host node sends access backhaul integrated IAB authorization information to the first host node, where the IAB authorization information is used to indicate the authorization status of the first IAB node. The first IAB node includes a first distributed unit and a first mobile terminal. An RRC connection exists between the first mobile terminal and the second host node. The third host node is a host node that has an RRC connection with the first mobile terminal before the first mobile terminal establishes an RRC connection with the second host node. There is an F1 connection or an attempt to establish an F1 connection between the first distributed unit and the first host node.

7. The method according to claim 6, characterized in that Before the third host node sends the IAB authorization information to the first host node, the method further includes: The third host node receives the IAB authorization information from the second host node.

8. A communication method, characterized in that: include: The first access backhaul integrated IAB node sends IAB authorization information to the first host node, where the IAB authorization information is used to indicate the authorization status of the first IAB node. The first IAB node includes a first distributed unit and a first mobile terminal. An RRC connection exists between the first mobile terminal and the second host node, and an F1 connection exists between the first distributed unit and the first host node.

9. The method according to claim 8, characterized in that Before the first IAB node sends the IAB authorization information to the first host node, the method further includes: The first IAB node receives IAB authorization information from the core network access and mobility management function AMF, or The first IAB node receives IAB authorization information from a fourth host node, where the fourth host node is a host node that has an F1 connection with the first distributed unit before the first distributed unit establishes an F1 connection with the first host node, or The first IAB node receives IAB authorization information from the second host node.

10. A communication method, characterized in that: include: The core network access and mobility management function AMF sends access backhaul integration IAB authorization information to the first host node, where the IAB authorization information is used to indicate the authorization status of the first access backhaul integration IAB node, where the first IAB node includes a first distributed unit and a first mobile terminal, where an RRC connection exists between the first mobile terminal and the second host node, where an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection, and where the first host node and the second host node are different host nodes. point.

11. The method according to claim 10, characterized in that Before the AMF sends the IAB authorization information to the first hosting node, the method further includes: The AMF receives identification information of the first host node sent by the first IAB node or the second host node.

12. The method according to claim 11, characterized in that The AMF sending the IAB authorization information to the first host node includes: the AMF sending the IAB authorization information to the first host node according to the identification information of the first host node.

13. A communication method, characterized in that: include: The fourth host node sends access backhaul integrated IAB authorization information to the first host node, where the IAB authorization information is used to indicate the authorization status of the first IAB node. The first IAB node includes a first distributed unit and a first mobile terminal. The first distributed unit includes a first logical distributed unit and a second logical distributed unit. There is an RRC connection between the first mobile terminal and the second host node, an F1 connection between the first logical distributed unit and the fourth host node, and the second logical distributed unit has an F1 connection with the first host node or attempts to establish an F1 connection.

14. A communication method, characterized in that: include: The first access and backhaul integrated IAB node sends the identification information of the first host node to the core network access and mobility management function AMF, the first IAB node includes a first distributed unit and a first mobile terminal, an RRC connection exists between the first mobile terminal and the second host node, and an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection, the AMF is used to send IAB authorization information to the first host node according to the identification information of the first host node, and the IAB authorization information is used to indicate the authorization status of the first IAB node.

15. A communication method, characterized in that: include: The second host node sends the identification information of the first host node to the core network access and mobility management function AMF, there is an RRC connection between the second host node and the first mobile terminal, the first mobile terminal is a mobile terminal in the first access and backhaul integrated IAB node, the first IAB node also includes a first distributed unit, there is an F1 connection between the first distributed unit and the first host node or an attempt to establish an F1 connection, the AMF is used to send IAB authorization information to the first host node according to the identification information of the first host node, and the IAB authorization information is used to indicate the authorization status of the first IAB node.

16. A communication device, characterized in that: is a host node that has an F1 connection with the first distributed unit or attempts to establish an F1 connection, and the device includes: A receiving module, configured to receive access backhaul integrated IAB authorization information, wherein the IAB authorization information is used to indicate an authorization state of a first IAB node, wherein the first IAB node includes a first distributed unit and a first mobile terminal, an RRC connection exists between the first mobile terminal and a second host node, and the device and the second host node are different host nodes; The processing module is configured to determine whether to allow the first IAB node to provide services for the UE according to the IAB authorization information.

17. A communication device, characterized in that: is a host node having an RRC connection with the first mobile terminal, and the device includes: A sending module is used to send access backhaul integrated IAB authorization information to a first host node, where the IAB authorization information is used to indicate the authorization status of the first IAB node, where the first IAB node includes a first distributed unit and the first mobile terminal, and there is an F1 connection between the first distributed unit and the first host node or an attempt is made to establish an F1 connection.

18. The device according to claim 17, characterized in that The device also includes: The receiving module is used to receive the IAB authorization information from the core network access and mobility management function AMF.

19. A communication device, characterized in that: The host node is a host node with which the first mobile terminal has an RRC connection before the first mobile terminal establishes an RRC connection with the second host node, and the device includes: A sending module is used to send access backhaul integrated IAB authorization information to a first host node, where the IAB authorization information is used to indicate the authorization status of the first IAB node, where the first IAB node includes a first distributed unit and the first mobile terminal, an RRC connection exists between the first mobile terminal and the second host node, and an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection.

20. The device according to claim 19, characterized in that The device also includes: A receiving module is used to receive the IAB authorization information from the second host node.

21. A communication device, characterized in that: The invention relates to an IAB node integrating access and backhaul, and the device comprises: A sending module is used to send IAB authorization information to a first host node, where the IAB authorization information is used to indicate the authorization status of the device, wherein the device includes a first distributed unit and a first mobile terminal, an RRC connection exists between the first mobile terminal and the second host node, and an F1 connection exists between the first distributed unit and the first host node or an F1 connection is attempted to be established.

22. The device according to claim 21, characterized in that The device also includes: A receiving module is used to receive the IAB authorization information from a core network access and mobility management function AMF or a fourth host node or the second host node, where the fourth host node is a host node that has an F1 connection with the first distributed unit before the first distributed unit establishes an F1 connection with the first host node.

23. A communication device, characterized in that: A core network access and mobility management function AMF that provides services for an integrated access and backhaul IAB node, the device comprising: A sending module is used to send IAB authorization information to a first host node, where the IAB authorization information is used to indicate the authorization status of a first access backhaul integrated IAB node, where the first IAB node includes a first distributed unit and a first mobile terminal, where an RRC connection exists between the first mobile terminal and the second host node, where an F1 connection exists between the first distributed unit and the first host node or an attempt is made to establish an F1 connection, and where the first host node and the second host node are different host nodes.

24. A communication device, characterized in that: is a host node having F1 connection with the first logical distributed unit, and the device includes: A sending module is used to send access backhaul integrated IAB authorization information to a first host node, where the IAB authorization information is used to indicate the authorization status of the first IAB node. The first IAB node includes a first distributed unit and a first mobile terminal. The first distributed unit includes a first logical distributed unit and a second logical distributed unit. An RRC connection exists between the first mobile terminal and the second host node. The second logical distributed unit has an F1 connection with the first host node or attempts to establish an F1 connection.

25. A communication device, characterized in that: A unit comprising a function of implementing the method according to claim 1, or the method according to any one of claims 2 to 5, or the method according to claim 6 or 7, or the method according to claim 8 or 9, or the method according to any one of claims 10 to 12, or the method according to claim 13, or the method according to claim 14, or the method according to claim 15.

26. A computer program product, characterized in that The computer program product comprises: a computer program code, when the computer program code is executed, Execute the method of claim 1, or Execute the method according to any one of claims 2 to 5, or Execute the method of claim 6 or 7, or Execute the method of claim 8 or 9, or Execute the method of any one of claims 10 to 12, or Execute the method of claim 13, or Execute the method of claim 14, or Execute the method of claim 15.

27. A computer-readable storage medium, characterized in that: The computer readable storage medium stores a computer program. When the computer program is executed, The device performs the method as claimed in claim 1, or The device performs the method according to any one of claims 2 to 5, or The device performs the method according to claim 6 or 7, or The device performs the method according to claim 8 or 9, or The device performs the method according to any one of claims 10 to 12, or causing the device to perform the method as claimed in claim 13, or causing the device to perform the method as claimed in claim 14, or The device is caused to perform the method as claimed in claim 15.

28. A chip system, characterized in that: comprising: a processor for calling and running a computer program from a memory, Enable a communication device equipped with the chip system to perform the method as claimed in claim 1; or Enable a communication device equipped with the chip system to perform the method as claimed in any one of claims 2 to 5; or Enable a communication device equipped with the chip system to perform the method according to claim 6 or 7; or Enable a communication device equipped with the chip system to perform the method as claimed in claim 8 or 9; or Enable a communication device equipped with the chip system to perform the method according to any one of claims 10 to 12; or Enable a communication device equipped with the chip system to perform the method as claimed in claim 13; or Enable a communication device equipped with the chip system to perform the method as claimed in claim 14; or The communication device equipped with the chip system executes the method as claimed in claim 15.

29. A communication system, characterized in that: The method comprises at least one of a first host node, a second host node, a third host node, a fourth host node, a first IAB node and an AMF, wherein the first host node is used to execute the method as claimed in claim 1, the second host node is used to execute the method as claimed in any one of claims 2 to 5 and 15, the first IAB node is used to execute the method as claimed in any one of claims 8, 9 or 14, the AMF is used to execute the method as claimed in any one of claims 10 to 12, the third host node is used to execute the method as claimed in claim 6 or 7, and the fourth host node is used to execute the method as claimed in claim 13.

Citation Information

Patent Citations

  • Communication method and communication device

    CN118945897A

  • Method and apparatus for authentication of integrated access and backhaul (IAB) nodes in wireless networks

    CN114342439A

  • Methods and devices for enhancing integrated access backhaul networks for new radio

    WO2022082566A1

Cited By

  • DCI enhancements for soft resource availability indication

    US12713447B2