Communication method and communication device

By informing the CU of the IAB-DU when the IAB authorization information is updated, the authorization status acquisition problem of the IAB node CU and the DU CU are solved, and flexible control and service quality management of the IAB node are realized.

CN118945897APending Publication Date: 2024-11-12HUAWEI TECH CO LTD
View PDF 0 Cites 3 Cited by

Patent Information

Application Number
CN202310531939.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-11
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In a network containing an access backhaul integrated (IAB) node, the CU of the IAB node is different from the CU of the DU, and the prior art is difficult to effectively understand the authorization status of the IAB node, resulting in the inability to accurately determine whether the establishment of the F1 interface or configuration is allowed. The community affects the flexible control of the network.

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, allow the establishment of the F1 interface, turn off the cell or prohibit the UE access based on the authorization information, so as to realize the IAB Flexible control of nodes.

Benefits of technology

It realizes flexible control of IAB nodes in a specific time and space range, ensuring the authorization status management and service quality of IAB nodes on the network side.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945897A_ABST
    Figure CN118945897A_ABST
Patent Text Reader

Abstract

Provided is a communication method, comprising: a first host node receiving IAB authorization information, the IAB authorization information being used for indicating an authorization state of a first IAB node, the first IAB node comprising a first distributed unit and a first mobile terminal, an RRC connection being present between the first mobile terminal and a second host node, f1 connection exists between the first distributed unit and the first host node or the first distributed unit tries to establish the F1 connection, and the first host node and the second host node are different host nodes; and the first host node determines whether to allow the first IAB node to provide service for the UE according to the IAB authorization information. When the IAB authorization information is updated, the latest IAB authorization information is informed to the CU of the IAB-DU, so that the CU of the IAB-DU can determine whether the IAB node is allowed to provide service for the UE or not based on the latest authorization information, and flexible control over the IAB node by a network side is facilitated.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] In a network including an integrated access and backhaul (IAB) node, there are multiple transmission links in the transmission path between a user equipment (UE) and an IAB donor (or donor node, or donor gNB), including at least one wireless backhaul link and one wireless access link. The wireless access link is a communication link between the UE and a relay node (or IAB node), and the wireless backhaul link is a communication link between IAB nodes or between an IAB node and a donor node. The service data of the UE is transmitted by the IAB node connecting to the IAB donor through the wireless backhaul link.

[0003] The IAB node consists of a mobile termination (MT) part and a distributed unit (DU) part. When the IAB node faces its parent node, it can act as a terminal device, that is, the role of 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, that is, the role of 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, connected to the 5G core network).

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

[0005] When the IAB node enters the network or the authorization status changes, it needs to obtain the 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 IABnode). 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.

[0006] In many scenarios (such as the migration scenario of the IAB node), 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 enters the network, if the CU of the IAB-MT configures the default configuration for the MT, and the IAB-DU sends an F1 interface establishment request to its CU, then the CU of the IAB-DU needs to know whether the IAB node is authorized or unauthorized in order to perform corresponding operations (such as, when the IAB node is unauthorized, rejecting the F1 interface establishment request of the IAB-DU). However, in the prior art, it is not considered how the CU of the IAB-DU obtains the authorization information of the current IAB when the CU of the IAB-MT is different from the CU of the IAB-DU. Summary of the invention

[0007] The present application provides a communication method and a communication device, by notifying the CU of the IAB-DU of the latest IAB authorization information when the IAB authorization information is updated, so that the CU of the IAB-DU can judge whether to delete the F1 interface / whether to allow the F1 interface to be established / 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, which is conducive to the network side to flexibly control the IAB node and realize the requirement of allowing or prohibiting the IAB node to work within a specific time / space range.

[0008] 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, and the present application does not limit this.

[0009] The method includes: a first host node receives access backhaul integrated IAB authorization information, 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; the first host node determines whether to allow the first IAB node to provide services for UE according to the IAB authorization information.

[0010] 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 judge 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.

[0011] 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 the present application does not limit this.

[0012] The method includes: a second host node sends access backhaul integrated IAB authorization information to a 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 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.

[0013] In a possible implementation manner, before the second host node sends the IAB authorization information to the first host node, the method further includes: the second host node receives the IAB authorization information from the core network access and mobility management function AMF.

[0014] In one possible implementation, before the second host node sends the IAB authorization information to the first host node, the method also 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.

[0015] In a possible implementation manner, 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.

[0016] 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 the present application does not limit this.

[0017] The method includes: a third host node sends access backhaul integrated IAB authorization information to a 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 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.

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

[0019] 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, and the present application does not limit this.

[0020] The method includes: a first access backhaul integrated IAB node sends IAB authorization information to a 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 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.

[0021] In a 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, and 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.

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

[0023] The method includes: a core network access and mobility management function AMF sends access backhaul integrated IAB authorization information to a first host node, wherein the IAB authorization information is used to indicate the authorization status of the first access backhaul integrated 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 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.

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

[0025] In a possible implementation manner, 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.

[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 second host node.

[0027] In a possible implementation manner, 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.

[0028] In a sixth 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 the present application does not limit this.

[0029] The method includes: a fourth host node sends access backhaul integrated IAB authorization information to a 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 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.

[0030] 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 the present application does not limit this.

[0031] 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, 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, 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.

[0032] In an eighth 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 the present application does not limit this.

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

[0034] In a ninth 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 the present application does not limit this.

[0035] The method includes: a third host node sends 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.

[0036] In the tenth aspect, a communication device is provided, including: a receiving module, used to receive access backhaul integrated IAB authorization information, the IAB authorization information is used to indicate the authorization status of a first 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; a processing module, used to determine whether to allow the first IAB node to provide services for the UE based on the IAB authorization information.

[0037] In the eleventh aspect, a communication device is provided, which is a host node that has an RRC connection with a first mobile terminal, and the device includes: a sending module, used to send 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, and there is an F1 connection between the first distributed unit and the first host node or an attempt to establish an F1 connection.

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

[0039] In a possible implementation, the receiving module is also used to receive 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.

[0040] In a possible implementation manner, 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.

[0041] 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, used to send 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.

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

[0043] In the thirteenth aspect, a communication device is provided, which is an access backhaul integrated IAB node, the device comprising: a sending module, used to send IAB authorization information to a first host node, the IAB authorization information is used to indicate the authorization status of the first IAB node, the first IAB node comprises 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 is made.

[0044] In a possible implementation, the device also includes: a receiving module, used 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, and 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.

[0045] In a fourteenth aspect, a communication device is provided, which is a core network access and mobility management function AMF that provides services for an access backhaul integrated IAB node, the device comprising: a sending module, used to send IAB authorization information to a first host node, the IAB authorization information is used to indicate the authorization status of the first access backhaul integrated IAB node, the first IAB node comprises 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 to establish an F1 connection is made, and the first host node and the second host node are different host nodes.

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

[0047] In a possible implementation manner, 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.

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

[0049] In a possible implementation manner, 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 the fifteenth aspect, a communication device is provided, which is a host node having an F1 connection with a first logical distributed unit, the device comprising: a sending module, used to send 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 comprises a first distributed unit and a first mobile terminal, the first distributed unit comprises 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, and the second logical distributed unit has an F1 connection with the first host node or attempts to establish an F1 connection.

[0051] In the sixteenth aspect, a communication device is provided, including: a sending module, used to send identification information of a first host node to a 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, 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.

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

[0053] In the eighteenth aspect, 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.

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

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

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

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

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

[0059] In the twenty-fourth aspect, a wireless communication device is provided, comprising various modules or units for executing the method in the sixth aspect or any possible implementation manner of the sixth aspect.

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

[0061] In the twenty-sixth aspect, a wireless communication device is provided, comprising various modules or units for executing the method in the eighth aspect or any possible implementation of the eighth aspect.

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

[0063] In a twenty-eighth aspect, a communication device is provided, comprising a processor, the processor being coupled to a memory, and being operable to execute the method in 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 a possible implementation, the communication device further comprises a memory. In a possible implementation, the communication device further comprises a communication interface, the processor being coupled to the communication interface. In a possible implementation, the communication device further comprises a communication interface, the processor being coupled to the communication interface.

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

[0065] 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 a related circuit on the chip or the chip system. The processor may also be embodied as a processing circuit or a logic circuit.

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

[0067] 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 one possible implementation, the input / output interface may be an input / output circuit.

[0068] 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 a related circuit on the chip or the chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0069] In a thirtieth aspect, a communication device is provided, comprising a processor, the processor being coupled to a memory and being used to execute instructions in the memory to implement the method in the fifth aspect and its possible implementation. In a possible implementation, the communication device further comprises a memory. In a possible implementation, the communication device further comprises a communication interface, and the processor is coupled to the communication interface. In a possible implementation, the transceiver may be a transceiver circuit. In a possible implementation, the input / output interface may be an input / output circuit.

[0070] 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 one possible implementation, the input / output interface may be an input / output circuit.

[0071] 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 a related circuit on the chip or the chip system. The processor may also be embodied as a processing circuit or a logic circuit.

[0072] 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 used to receive a signal through the input circuit and transmit a signal through the output circuit, so that any one of the first to ninth aspects, and any possible implementation of the above aspects is implemented.

[0073] In the specific implementation process, the above-mentioned communication device can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a trigger, and various logic circuits. The input signal received by the input circuit can be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter, and the input circuit and the output circuit can be different circuits or the same circuit. In this case, the circuit is used as an input circuit and an output circuit at different times. The embodiment of the present application does not limit the specific implementation method of the processor and various circuits.

[0074] In a thirty-second aspect, a processing device is provided, comprising a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute any one of the first to ninth aspects, and any possible implementation of the above aspects.

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

[0076] In a possible implementation manner, the memory may be integrated with the processor, or the memory and the processor may be provided separately.

[0077] 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 respectively. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0078] It should be understood that the relevant data interaction process, such as sending indication information, can be a process of outputting indication information from a processor, and receiving capability information can be a process of receiving input capability information from a processor. Specifically, the processed output data can be output to a transmitter, and the input data received by the processor can come from a receiver. Among them, the transmitter and the receiver can be collectively referred to as a transceiver.

[0079] The processor in the above aspects can be a chip, which can be implemented by hardware or by 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 software codes stored in a memory. The memory can be integrated in the processor or can be located outside the processor and exist independently.

[0080] In the thirty-third aspect, a computer program product is provided, comprising: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute any one of the first to ninth aspects, and a method in any possible implementation of the above aspects.

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

[0082] 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

[0083] Figure 1 It is an architectural diagram of an IAB system applicable to the technical solution of the present application.

[0084] Figure 2 This is a schematic diagram of the composition of an IAB node.

[0085] Figure 3 It is a schematic diagram of the IAB network control plane and user plane protocol stack.

[0086] Figure 4 It is a schematic flow chart of IAB node access to the network.

[0087] Figure 5 It is a schematic diagram of the local migration scenario of the IAB node.

[0088] Figure 6 The figure is a schematic diagram of an IAB topology redundancy scenario.

[0089] Figure 7 is a schematic diagram of a scenario of continuous local migration of a mobile IAB node.

[0090] Figure 8 It is a schematic diagram of the IAB node DU migration scenario.

[0091] Fig. 9 It is a schematic flow chart of an IAB authorization information transmission method provided by this application.

[0092] Fig.10 It is a schematic flow chart of another IAB authorization information transmission method provided by the present application.

[0093] Fig.11This is a schematic flow chart of another IAB authorization information transmission method provided by the present application.

[0094] Fig.12 This is a schematic flow chart of another IAB authorization information transmission method provided by the present application.

[0095] Fig.13 This is a schematic flow chart of another IAB authorization information transmission method provided by the present application.

[0096] Fig.14 This is a schematic flow chart of another IAB authorization information transmission method provided by the present application.

[0097] Fig.15 This is a schematic flow chart of another IAB authorization information transmission method provided by the present application.

[0098] Fig.16 This is a schematic flow chart of another IAB authorization information transmission method provided by the present application.

[0099] Fig.17 A schematic block diagram of a communication device provided in an embodiment of the present application.

[0100] Fig.18 A schematic block diagram of another communication device provided in an embodiment of the present application.

[0101] Fig.19 A schematic diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0102] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0103] 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), 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 system, non-terrestrial network (NTN) system, the 5th Generation (5G) system or new radio (NR) or future wireless communication system.

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

[0105] In the present 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.

[0106] 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 that has the same or similar function as the node or information used in this application is deemed to be a method or equivalent replacement of this application, and is within the scope of protection of this application, and will not be repeated below.

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

[0108] In a network including an IAB node (hereinafter referred to as the IAB network), the IAB node can provide wireless access services for terminal devices. The UE is connected to the IAB node via a wireless access link and is connected to the donor node (IABdonor / donor node) via a wireless backhaul link to transmit user service data.

[0109] 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 CU) and a distributed unit (DU) (referred to herein as Donor-DU) are separated, that is, the host node is composed of Donor-CU and 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 case in which the host node is composed of Donor-CU and Donor-DU as an example.

[0110] The IAB node consists of a mobile termination (MT) part and a distributed unit (DU) part. When the IAB node faces its parent node, it can be regarded as a terminal device. At this time, the IAB node plays the role of MT. When the 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. At this time, the IAB node plays the role of DU. Therefore, it can be considered that the 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.

[0111] Among them, the Donor-CU can also be in 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 is composed of CU-CP and CU-UP.

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

[0113] In order to ensure the reliability of service transmission, the IAB network supports multi-hop IAB nodes and multi-connection IAB node networking. Therefore, there may be multiple transmission paths between the terminal device and the host node. On one path, there is a certain hierarchical relationship between IAB nodes, and between IAB nodes and host nodes serving IAB nodes. Each IAB node regards the node that provides backhaul services to it as a parent node. Accordingly, each IAB node can be regarded as a child node of its parent node.

[0114] For example, see Figure 1 , the parent node of IAB node 1 is the host node, IAB node 1 is 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 through 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 through one or more IAB nodes. There are two available paths for the transmission of data packets between terminal device 1 and the host node, namely: terminal device 1→IAB node 4→IAB node 3→IAB node 1→host node, terminal device 1→IAB node 4→IAB node 2→IAB node 1→host node. There are three available paths for the transmission of data packets 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.

[0115] It is understandable that in an 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.

[0116] Exemplarily, 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.

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

[0118] Figure 2 A schematic diagram of a system architecture applicable to an embodiment of the present application is shown. Figure 2 As shown in the figure, IAB (or IAB equipment) is a wireless backhaul base station. Its particularity lies in that IAB must first establish a backhaul channel with the target macro station, and then provide wireless coverage services to the outside. It is similar to customer premise equipment (CPE), but the difference is that CPE provides wireless fidelity (WIFI) coverage to the outside. IAB provides base station wireless signals to the outside, 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 far away from 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.

[0119] In such Figure 2 The IAB network architecture shown in the figure takes standalone (SA) networking as an example. The IAB donor can be composed of a centralized unit (CU) and a distributed unit (DU), that is, the functions of the IAB donor are split, some functions are deployed in a CU, and the remaining functions are deployed in the DU. Multiple DUs share one CU, which can save costs and facilitate network expansion. The CU and DU are connected through the F1 interface. The CU represents the IAB donor connected to the core network through the next generation (nest generation, NG) interface, and the CU represents the IAB donor connected to other gNBs through the Xn interface.

[0120] The IAB node DU (may be referred to as IAB-DU in this application) is logically connected to the IABdonor CU (may be referred to as CU in this application) through the F1 interface. In fact, the connection between the IAB-DU and the CU is realized through the NR Uu interface between the IAB-MT and the parent node DU of each hop, but because the IAB-DU can communicate with the CU in the end, it can be considered that the F1 interface exists logically. The IAB-MT function is defined as a component similar to the UE. In the IAB network, the MT is called a function residing on the IABnode. Since the MT is similar to the function of an ordinary UE, it can be considered that the IAB node is connected to the upper node or network through the MT.

[0121] The user plane and control plane protocol stacks in the IAB network are as follows: Figure 3 As shown. The F1 interface supports the user plane protocol (F1-userplane, F1-U) and the control plane protocol (F1-control plane, F1-C), among which, Figure 3 As shown in (b), the user plane protocol includes one or more of the following protocol layers: GPRS tunneling protocol user plane (General Packet Radio Service tunneling protocol user plane, GTP-U), UDP (user datagram protocol, user datagram protocol), IP (internet protocol, Internet protocol) and other protocol layers; Figure 3As shown in (a), the control plane protocol includes one or more of the following: F1AP (F1 application protocol), SCTP (stream control transport protocol), IP and other protocol layers. Through F1-C, the IAB donor and IABnode can perform interface management, manage IAB-DU, and perform UE context-related configuration; through F1-U, the IAB donor and IAB node can perform user plane data transmission and downlink transmission status feedback.

[0122] It should be noted that the above Figure 1 and Figure 2 The above is only an example, and the technical solution of the present application can be applied to various communication systems including access network units. For example, the access network unit can be Figure 1 IAB in, or Figure 2 In addition, the communication system may also include a terminal device.

[0123] 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 a wireless transceiver function, which may be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it may also be deployed on the water (such as a ship, etc.); it may also be deployed in the air (for example, on an airplane, a balloon, and a satellite, 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 a wireless communication function. Exemplarily, the UE may be a mobile phone, a tablet computer, or a computer with a wireless transceiver function. 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 device for implementing the function of the terminal as an example. It should be understood that terminal is a general term, including the most common mobile phones, CPE, 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.

[0124] The network equipment involved in the embodiments of the present application includes a base station (BS), which may be a device deployed in a wireless access network that can communicate wirelessly with a terminal. Among them, the base station may have multiple 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 implementing the function of the network device may be a network device; it may also be a device that can support the network device to implement 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 implementing 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.

[0125] In the embodiment of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices.

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

[0127] It should also be understood that the above naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation to this application. This application does not exclude the possibility of using other naming in 6G networks and other future networks.

[0128] It should also be understood that Figure 2 The interface name between the network elements is only an example. The interface name in the specific implementation may be other names, and this application does not specifically limit this. In addition, the name of the information (or signaling) transmitted between the above network elements is only an example and does not constitute any limitation on the function of the information itself.

[0129] The following describes the process of IAB node integration. Figure 4 The flowchart of IAB node accessing the network is shown in FIG. The access process of IABnode2 is taken as an example. IAB node 1 is its parent node and is already in the network.

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

[0131] Phase 1: IAB-MT accesses the cell in a similar manner to an ordinary UE, establishes an RRC connection with the host node, and indicates that it is an IAB node when establishing the RRC connection (carrying the IAB node indication in the RRC connection setup complete (RRCSetupComplete) 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 the IAB authorization information element (IAB authorized information element, i.e., the "IAB authorization information" in the present invention) in the information indicating the CU to establish the UE initial context for the IAB-MT (INITIAL CONTEXT SETUPREQUEST). 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 the network access process of the IAB node is introduced here, it is assumed that the value of the IAB authorization information element is authorized, and the subsequent steps are performed.

[0132] Phase2: 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 in the subsequent initial establishment of the F1 interface (see Phase3 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 Phase2, in addition to configuring IAB node2, the nodes between the IAB node and the donor (IAB node1) will also be updated to inform these nodes how to select the next hop link and next hop RLC channel when receiving data packets from IAB node2 or sending data packets to IAB node2.

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

[0134] When 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. When the value of the IAB authorization information element is notauthorized, 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, etc.

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

[0136] The large-scale mobility of the IAB node will cause some impact on the core network side. The mobile IAB node requires 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.

[0137] It is uniformly explained here that the IAB node in this application can be a common IAB node or a mobileIAB 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), and this application does not limit this.

[0138] The above introduces the basic concepts of IAB and the network access process. The following introduces some topology change-related features of IAB. Specifically, these features are all inter-CU (inter-donor CU). For the case of non-inter-CU (intra-donor CU) and inter-donor DU (inter-donor DU), although it crosses donor-DU, it does not cross CU, so the CU can reconfigure it. The following scenarios involve interaction between CUs.

[0139] 1. Partial migration

[0140] Local migration of IAB nodes Figure 5 As shown. The IAB node where migration occurs is called a boundary node, such as IAB node2. The downstream node of the boundary node is called a descendant node, such as IAB node4. Before migration, there is an RRC connection between IAB-MT2 and CU1, an F1 interface between IAB-DU2 and CU1, and IAB node2 communicates with the IAB donor through the source path (through IAB node1 composed of IAB-MT1 and IAB-DU1). During local migration, IAB-MT2 undergoes cross-CU cell switching and establishes an RRC connection with CU2.

[0141] To avoid the need to re-establish the F1 interface, during local migration, IAB-DU2 still maintains the F1 interface with CU1 and does not establish an F1 interface with CU2. Therefore, the communication path between CU1 and IAB-DU2 becomes cross-topology: Figure 5 In the example, CU1 and CU2 are respectively referred to as F1-terminating CU and non-F1-terminating CU, or source CU and target CU. It should be noted that data does not pass through CU2 when transmitted on this path, and CU1 and Donor-DU2 communicate directly through the IP network.

[0142] The F1 anchor CU sends a transport migration management request (IAB TRANSPORT MIGRATIONMANAGEMENTIAB REQUEST) message to the non-F1 anchor CU, requesting to establish cross-topology traffic transmission. If the non-F1 anchor CU agrees to establish it, it replies with a transport migration management response (IAB TRANSPORT MIGRATION MANAGEMENTIAB RESPONSE) message to the F1 anchor CU. If it disagrees, it replies with a transport migration management reject (IAB TRANSPORT MIGRATIONMANAGEMENTIABREJECT) message. If the F1 anchor CU or the non-F1 anchor CU subsequently wants to modify or withdraw the QoS of the traffic, they can also exchange transport migration modification request / response (IAB TRANSPORT MIGRATIONMODIFICATIONIAB REQUEST / RESPONSE) messages.

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

[0144] In NR, UE can perform dual connection and connect to two different base stations to improve throughput and robustness. IAB-MT can also perform dual connection and connect to two different CUs. The data between IAB-DU and CU (specifically, F1 anchor CU) can be transmitted simultaneously through two paths, doubling the throughput. There is an RRC connection between IAB-MT and both CU1 and CU2, and there is an F1 interface between 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.

[0145] 3. Radio Link Failure recovery (RLF recovery)

[0146] When RLF occurs between IAB-MT and the source cell, other cells will be selected to initiate RRC re-establishment, which may be from other CUs. After inter-CU RRC re-establishment occurs in IAB-MT2, the topology is the same as local migration. The RRC connection of IAB-MT2 is changed to CU2, and the F1 interface of IAB-DU2 is still on CU1. The signaling interaction between RLF recovery and local migration is different, but the final state is the same.

[0147] 4. Continuous partial migration

[0148] like Figure 7 As shown in FIG. 1 , when MT switches from CU2 to CU3, the F1 interface of DU is always associated with CU1. Here, mIAB is the abbreviation of mobileIAB. Figure 7 The mAB node in the donor-DU is directly connected to the donor-DU, but there may be other IAB nodes between the mAB node and the donor-DU, which is not limited in this application. 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 following DU migration scenario).

[0149] 5. DU migration

[0150] 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. Figure 8 As shown, the RRC connection of MT is always on CU2, and the F1 interface of DU 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, and switches the UE from the cell under mAB-DU1 to the cell under mAB-DU2. Then CU1 releases the F1 interface with mAB-DU1, and the 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 CU of MT (also called RRC terminating CU).

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

[0152] The reason why it is assumed that DU migration is completely decoupled from MT migration is that the process of DU migration is relatively complicated (it is necessary to generate two logical DUs and switch UEs to the new logical DUs one by one). DU should not be migrated frequently, so the CU of DU should be a CU with a relatively large control range; MT migration is the switching of MT, which may be executed frequently. The selection of MT CU is determined by the signal quality, so the CU of MT may be different from the CU of DU.

[0153] 6. IAB integration to Different CU

[0154] Based on the assumption that DU migration and MT migration are completely decoupled, during the IAB integration process, the RRC connection of the MT and the F1 interface of the DU can be terminated on different CUs (e.g., the CU of the DU is a CU with a larger control range, and the CU of the MT is the CU corresponding to the cell with the best signal quality). In other words, once the IAB node enters the network, a Figure 5 The topology in .

[0155] In many scenarios (such as the migration scenario of the IAB node), 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 enters the network, if the CU of the IAB-MT configures the default configuration for the MT, and the IAB-DU sends an F1 interface establishment request to its CU, then the CU of the IAB-DU needs to know whether the IAB node is authorized or unauthorized in order to perform corresponding operations (such as, when the IAB node is unauthorized, rejecting the F1 interface establishment request of the IAB-DU). However, in the prior art, it is not considered how the CU of the IAB-DU obtains the authorization information of the current IAB when the CU of the IAB-MT is different from the CU of the IAB-DU.

[0156] The present application provides a variety of communication methods, as examples but 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, which is conducive to the network side to flexibly control the IAB node and realize the requirement of allowing or prohibiting the IAB node from working within a specific time / space range.

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

[0158] Depending on the specific scenario, the method of informing the CU of the IAB-DU of the latest IAB authorization information is also different. It should be understood that the description of the specific scenario in the embodiment of the present application is only an example, and the method provided in the embodiment of the present application can be applied to the application scenario described above and is also applicable to application scenarios with similar problems.

[0159] Several methods for informing the CU of the IAB-DU of the latest IAB authorization information are specifically introduced below. In the scenarios to which the following methods are applicable, the CU of the IAB-MT is different from the CU of the IAB-DU.

[0160] Method 1

[0161] Below Figure 7 Take the continuous local migration scenario shown in the figure as an example. Figure 7 CU1 is the F1 anchor CU of DU, CU2 is the source CU of MT, and CU3 is the target CU of MT. In method 1, the target CU of MT first informs the source CU of MT, and then the source CU of MT informs the F1 anchor CU of DU. Method 1 is suitable for the scenario of continuous local migration.

[0162] Fig. 9 A schematic flow chart 900 of method 1 is shown, Fig. 9 The method includes at least part of the following contents.

[0163] S910, the MT switches from CU2 to CU3.

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

[0165] S920, AMF sends IAB authorization information to CU3.

[0166] In a possible implementation, before AMF sends IAB authorization information to CU3, CU3 first sends a path switch request message to AMF to inform AMF that MT has been switched to CU3, and AMF transfers MT's services to CU3. AMF replies to CU3 with a path switch request confirmation (PATH SWITCH REQUEST ACK) message, carrying the value of the current IAB authorization information element and / or mobileIAB authorization information element (ie, IAB authorization information).

[0167] In another possible implementation, when the AMF finds that the IAB authorization information has changed, the value of the current IAB authorization information element and / or the mobile IAB authorization information element (ie, the IAB authorization information) is carried in the UE CONTEXT MODIFICATION REQUEST.

[0168] S930, CU3 sends IAB authorization information to CU2.

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

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

[0171] In another possible implementation, only when authorization is not granted, the information carries the (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.

[0172] 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 XnAPID of IAB-MT under CU3.

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

[0174] S940, CU2 sends IAB authorization information to CU1.

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

[0176] In a possible implementation manner, this message may be an IAB transport migration modification request message IABTRANSPORTMIGRATIONMODIFICATIONREQUEST.

[0177] In another possible implementation, 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) may be carried in this indication information.

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

[0179] Method 2

[0180] Below Figure 7 Taking the scenario of continuous local migration shown in the figure as an example, method 2 is introduced. Figure 7 CU1 is the F1 anchor CU of DU, CU2 is the source CU of MT, and CU3 is the target CU of MT. In method 2, the target CU of MT directly informs the F1 anchor CU of DU. Method 2 is applicable to the scenarios of local migration, continuous local migration, wireless link failure recovery and topology redundancy.

[0181] Fig.10 A schematic flow chart 1000 of method 2 is shown, Fig.10 The method includes at least part of the following contents.

[0182] S1010, MT switches from CU2 to CU3.

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

[0184] S1020, AMF sends IAB authorization information to CU3.

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

[0186] In another possible implementation, when the AMF finds that the IAB authorization information has changed, the value of the current IAB authorization information element and / or the mobileIAB authorization information element (ie, the IAB authorization information) is carried in a UE CONTEXT MODIFICATION REQUEST message.

[0187] 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 XnAPID of IAB-MT under CU3.

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

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

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

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

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

[0193] In another possible implementation, only when authorization is not granted, the 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.

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

[0195] It should be understood that, in addition to Figure 7 In addition to the continuous local migration scenario shown, method 2 can also be used in inter-CU partial migration, inter-CU RLF recovery, and inter-CU topology redundancy and the scenario where the master node (MN) of the IAB-MT is a non-F1 anchor point (CU3). Assume that there is no CU2. 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.

[0196] In different scenarios, some steps in steps S1010 to S1040 of the above method 2 are also different.

[0197] For the partial migration or RLF recovery scenarios, the migration behaviors of MT in step S1010 are different. In the partial migration scenario, MT switches from CU1 to CU3; in the RLF recovery scenario, a radio link failure occurs in MT under CU1, so 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.

[0198] 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 authorization information of IAB-MT will be sent to MN by AMF. Only when MN is CU3, it is necessary for CU3 to further inform the F1 anchor CU (i.e. CU1) of the authorization information. If MN is originally CU1 and CU1 is the F1 anchor CU, there is no technical problem.

[0199] 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 have an interactive path switching process with AMF. Therefore, there is only one way to obtain authorization information through UE context modification request.

[0200] In addition, for the topology redundancy scenario, it is also applicable to the IAB-MT EN-DC scenario, that is, the primary station of MT is MeNB (LTE base station), the secondary station is 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.

[0201] Method 3

[0202] Below Figure 7 Taking the scenario of continuous local migration shown in the figure as an example, method 3 is introduced. Figure 7 CU1 is the F1 anchor CU of DU, CU2 is the source CU of MT, and CU3 is the target CU of MT. In method 3, the F1 anchor CU of DU initiates the cross-topology traffic migration process to the target CU of MT, and the target CU of MT informs the IAB authorization information in the reply information. Method 3 is applicable to the scenarios of local migration, continuous local migration, wireless link failure recovery and topology redundancy.

[0203] Fig.11 A schematic flow chart 1100 of method 3 is shown, Fig.11 The method includes at least part of the following contents.

[0204] S1110, MT switches from CU2 to CU3.

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

[0206] S1120, AMF sends IAB authorization information to CU3.

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

[0208] In another possible implementation, when the AMF finds that the IAB authorization information has changed, the value of the current IAB authorization information element and / or the mobile IAB authorization information element (ie, the IAB authorization information) is carried in the UE context modification request.

[0209] 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 XnAPID of IAB-MT under CU3.

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

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

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

[0213] Specifically, CU3 carries the authorization information of IAB in the IAB transfer migration management response or IAB transfer migration management rejection message replied to CU1.

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

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

[0216] In another implementation, when the request is authorized, an IAB transmission migration management response message is replied, and when the request is not authorized, an IAB transmission migration management rejection message is replied.

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

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

[0219] It should be understood that, in addition to Figure 7 In addition to the continuous local migration scenario shown, method 3 can also be used in inter-CU partial migration, inter-CU RLF recovery, and 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 there is no CU2, 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.

[0220] In different scenarios, some steps in steps S1110 to S1140 of the above method 3 are also different.

[0221] For the partial migration or RLF recovery scenarios, the migration behaviors of the MT in step S1110 are 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 RLF recovery from CU1 to CU3.

[0222] 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 authorization information of IAB-MT will be sent to MN by AMF. Only when MN is CU3, it is necessary for CU3 to further inform the F1 anchor CU (i.e. CU1) of the authorization information. If MN is originally CU1 and CU1 is the F1 anchor CU, there is no technical problem.

[0223] 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 have an interactive path switching process with AMF. Therefore, the only way to obtain the authorization information here is through UE context modification request.

[0224] In addition, for the topology redundancy scenario, it is also applicable to the IAB-MT EN-DC scenario, that is, the primary station of MT is MeNB (LTE base station), the secondary station is 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.

[0225] Method 4

[0226] Below Figure 7 Taking the scenario of continuous local migration shown in the figure as an example, method 4 is introduced. Figure 7 CU1 is the F1 anchor CU of DU, CU2 is the source CU of MT, and CU3 is the target CU of MT. In method 4, the IAB-DU informs the F1 anchor CU of the current IAB authorization information. Method 4 is applicable to the scenarios of local migration, continuous local migration, wireless link failure recovery and topology redundancy.

[0227] Fig.12 A schematic flow chart 1200 of method 4 is shown, Fig.12 The method includes at least part of the following contents.

[0228] S1210, the MT switches from CU2 to CU3.

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

[0230] S1220, AMF sends IAB authorization information to IAB-MT.

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

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

[0233] In another possible implementation, only when authorization is not granted, the 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.

[0234] 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 XnAPID of IAB-MT under CU3.

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

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

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

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

[0239] For the above methods 1, 2 and 4, if the MT CU switching step is deleted, it can be applied to the scenario where the change of the IAB authorization status does not occur when the MT CU is switched. That is, whenever the MT CU or the MT itself receives the IAB authorization status, it informs the DU CU.

[0240] 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 accesses 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.

[0241] It should be understood that, in addition to Figure 7 In addition to the continuous local migration scenario shown, method 4 can also be used in inter-CU partial migration, inter-CU RLF recovery, and 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 there is no CU2, 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.

[0242] For the partial migration or RLF recovery scenarios, the migration behaviors of the MT in step S1210 are 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 RLF recovery from CU1 to CU3.

[0243] 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 authorization information of IAB-MT will be sent to MN by AMF. Only when MN is CU3, it is necessary for CU3 to further inform the F1 anchor CU (i.e. CU1) of the authorization information. If MN is originally CU1 and CU1 is the F1 anchor CU, there is no technical problem.

[0244] Method 5

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

[0246] Fig.13 A schematic flow chart 1300 of method 5 is shown. Fig.13 The method includes at least part of the following contents.

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

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

[0249] S1330, AMF sends IAB authorization information to CU1.

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

[0251] 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 IAB-MT is different from the CU of IAB-DU, the CU of DU can obtain the current authorization information of IAB-MT (also called the current authorization information of IAB node) through signaling interaction.

[0252] The above method introduces 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.

[0253] In the DU migration scenario, the CU of IAB-MT may be different from the CU of IAB-DU. Figure 8 Taking the DU migration shown as an example, several communication methods 6, 7 and 8 in this scenario are introduced.

[0254] Method 6

[0255] Below Figure 8Taking the DU migration scenario shown in the figure as an example, method 6 is introduced. 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.

[0256] Fig.14 A schematic flow chart 1400 of method 6 is shown, Fig.14 The method includes at least part of the following contents.

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

[0258] Specifically, CU1 sends a message to CU3, which carries IAB authorization information and / or mobileIAB authorization information.

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

[0260] In another possible implementation, only when authorization is not granted, the 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.

[0261] 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 (DU MIGRATION REQUEST) message.

[0262] 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 XnAPID of IAB-MT under CU3.

[0263] Method 7

[0264] Below Figure 8 Taking the DU migration scenario shown in the figure as an example, method 6 is introduced. Figure 8 CU1 is the source F1 anchor CU, CU2 is the CU of the MT, and CU3 is the target F1 anchor CU. In this method, the IAB-DU informs the target F1 anchor CU of the current IAB authorization information.

[0265] Fig.15 A schematic flow chart 1500 of method 7 is shown. Fig.15 The method includes at least part of the following contents.

[0266] S1510, the IAB-DU obtains IAB authorization information.

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

[0268] For example, CU1 sends an IAB-DU (logical DU associated with CU1, Figure 8 IAB-DU1) sends an F1 message to trigger DU migration, and the F1 message carries IAB authorization information.

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

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

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

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

[0273] S1520, IAB-DU (logical DU associated with CU3, Figure 8 IAB-DU2 in the IAB sends IAB authorization information to CU3.

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

[0275] Method 8

[0276] Below Figure 8 Taking the DU migration scenario shown in the figure as an example, method 6 is introduced. Figure 8 CU1 is the source F1 anchor CU, CU2 is the MT's CU, and CU3 is the target F1 anchor CU. In this method, the MT's CU informs the target F1 anchor CU of the current IAB authorization information.

[0277] Fig.16 A schematic flow chart 1600 of method 8 is shown, Fig.16 The method includes at least part of the following contents.

[0278] In one possible implementation,

[0279] 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 ends on CU3;

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

[0281] Specifically, CU2 carries the authorization information of IAB in the IAB transfer migration management response or IAB transfer migration management rejection message replied to CU3.

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

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

[0284] Optionally, when authorized, an IAB transmission migration management response message is replied, and when not authorized, an IAB transmission migration management rejection message is replied.

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

[0286] In another possible implementation,

[0287] S1610, CU1 sends an identifier (gNB ID and / or IP address) of CU3 to CU2, to inform CU2 that the DU will be migrated to CU3 or to request CU2 to configure resources for F1 interface transmission of CU3;

[0288] S1620, CU2 sends IAB authorization information to CU3.

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

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

[0291] Optionally, only when authorization is not granted, the (mobile) IAB authorization information element is carried in the indication information as notauthorized, or indication information of releasing the F1 connection or not establishing the F1 connection is carried in the indication information.

[0292] 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 XnAPID of IAB-MT under CU3.

[0293] Fig.17 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, and the processing unit 1720 is used for data processing. The transceiver unit 1710 can also be called a communication interface or a communication unit.

[0294] In a possible implementation, the device 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.

[0295] 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 a first host node, a second host node, a third host node or a 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.

[0296] 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 on 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.

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

[0298] It should also be understood that the device 1700 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (e.g., 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 may understand that the device 1700 may 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 may 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 embodiments of the methods, or the device 1700 may 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 of the methods, and may 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 embodiments of the methods, and to avoid repetition, it will not be repeated here.

[0299] The device 1700 of each of the above 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 method. The function 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 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.

[0300] In addition, the above-mentioned transceiver unit 1710 can also be a transceiver circuit (for example, can include a receiving circuit and a sending circuit), and the processing unit can be a processing circuit.

[0301] It should be pointed out that Fig.17 The device in the embodiment may be a network element or device in the foregoing embodiment, or may be a chip or a 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 or a microprocessor or an integrated circuit integrated on the chip. This is not limited here.

[0302] like Fig.18As shown, the embodiment of the present application further provides a communication device 1800. The communication device 1800 includes a processor 1810, the processor 1810 is coupled to a memory 1820, the memory 1820 is used to store computer programs or instructions or and / or data, and the processor 1810 is used to execute the computer programs or instructions and / or data stored in the memory 1820, so that the method in the above method embodiment is executed.

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

[0304] In one possible implementation, Figure 8 As shown, the communication device 1800 may further include a memory 1820 .

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

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

[0307] In one possible implementation, Figure 8 As shown, the wireless communication device 1800 may further include a transceiver 1830, and the transceiver 1830 is used for receiving and / or sending signals. For example, the processor 1810 is used to control the transceiver 1830 to receive and / or send signals.

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

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

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

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

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

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

[0314] like Fig.19 , 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.

[0315] Among them, the logic circuit 1910 can be a processing circuit in the chip system 1900. The logic circuit 1910 can be coupled to the storage unit and call the instructions in the storage unit so that the chip system 1900 can implement the methods and functions of each embodiment of the present application. The input / output interface 1920 can be an input / output circuit in the chip system 1900, outputting information processed by the chip system 1900, or inputting data or signaling information to be processed into the chip system 1900 for processing.

[0316] 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 method embodiments.

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

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

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

[0320] 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 executed by the end host node in the above method embodiment, or the method executed by the IAB node, or the method executed by the AMF.

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

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

[0323] In an embodiment of the present application, a terminal device or a 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. Among them, the hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also called 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 Linux operating system, Unix operating system, Android operating system, iOS operating system, or Windows operating system. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0324] The embodiments of the present application do not specifically limit the specific structure of the execution subject of the method provided in the embodiments of the present application, as long as it is possible to communicate 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. 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 the satellite that can call and execute the program.

[0325] Various aspects or features of the embodiments of the present application may be implemented as methods, devices, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein may encompass a computer program accessible from any computer-readable device, carrier, or medium. For example, a computer-readable medium may include, but is not limited to, a magnetic storage device (e.g., a hard disk, a floppy disk, or a magnetic tape, etc.), an optical disk (e.g., a compact disc (CD), a digital versatile disc (DVD), etc.), a smart card, and a flash memory device (e.g., an erasable programmable read-only memory (EPROM), a card, a stick, or a key drive, etc.).

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

[0327] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or 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. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

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

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

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

[0331] Those of ordinary skill 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 the present application.

[0332] Those skilled in the art can 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.

[0333] 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 only 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.

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

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

[0336] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially 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, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.

[0337] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope 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 hosting 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 integrated 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 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. The first host node and the second host node are different host nodes.

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

Cited By

  • Communication method and communication apparatus

    EP4697853A1

  • DCI enhancements for soft resource availability indication

    US12713447B2

  • Communication method and communication apparatus

    WO2024230369A1