Communication methods and communication devices

Abstract

This application provides a communication method comprising: a first donor node receiving IAB authorization information, the IAB authorization information indicating the authorization status of the first IAB node, the first IAB node comprising a first distributed unit and a first mobile terminal, the first mobile terminal having an RRC connection to a second donor node, and the first distributed unit attempting to establish or having an F1 connection to the first donor node, and being a different donor node from the first donor node and the second donor node; the first donor node determining, based on the IAB authorization information, whether the first IAB node is authorized to respond to a UE. When the IAB authorization information is updated, the latest IAB authorization information is notified to the CU of the IAB-DU, and as a result, the CU of the IAB-DU can determine, based on the latest authorization information, whether the IAB node is authorized to respond to a UE. This helps the network side to flexibly control the IAB nodes.

Description

Technical Field

[0001] This application claims priority to Chinese Patent Application No. 202310531939.X, titled "Communication Method and Communication Device", filed with the China National Intellectual Property Administration on May 11, 2023, the entire content of which is incorporated herein by reference.

[0002] This application relates to the field of communications, and more specifically, to communication methods and communication devices.

Background Art

[0003] In a network including an integrated access and backhaul (IAB) node, the transmission path between a user equipment (UE) and an IAB donor (also called an IAB donor or donor node, or donor gNB) includes a plurality of transmission links 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 (also called an IAB node). 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 connecting the IAB node and the IAB donor via the wireless backhaul link.

[0004] An IAB node includes a mobile termination (MT) portion and a distributed unit (DU) portion. When facing a parent node, the IAB node can function as a terminal device, i.e., an MT. When facing a child node (the child node may be another IAB node or a common UE), the IAB node is considered to function as a network device, i.e., a DU. A donor node is an access network element with full base station (gNB) functionality and includes a central unit (CU) and a distributed unit (DU). The donor node is connected to the core network corresponding to the UE (for example, connected to a 5G core network).

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

[0006] When an IAB node accesses the network or its authorization status changes, IAB authorization information needs to be retrieved from the Access and Mobility Management Function (AMF) network element within the core network. This IAB authorization information is the authorization status information of the IAB-MT (or referred to as the authorization status information of the IAB node). The authorization information is carried by context-related information of the IAB-MT and transmitted to the IAB-MT's CU by the IAB-MT's AMF.

[0007] In many scenarios (e.g., IAB node migration scenarios), the IAB-MT CU may differ from the IAB-DU CU. In some implementations, the IAB-DU CU also needs to know the IAB authorization information of the IAB-MT. For example, when an IAB node first accesses the network, if the IAB-MT CU sets default settings for the MT and the IAB-DU sends an F1 interface setup request to the IAB-DU CU, the IAB-DU CU needs to know whether the IAB node is authorized or not in order to perform the corresponding action (e.g., if the IAB node is not authorized, the IAB-DU's F1 interface setup request will be rejected). However, prior art does not consider how the IAB-DU CU knows the current IAB authorization information when the IAB-MT CU differs from the IAB-DU CU. [Overview of the Initiative]

[0008] This application provides a communication method and a communication device. When IAB authorization information is updated, the latest IAB authorization information can be notified to the CU of the IAB-DU, and as a result, the CU of the IAB-DU can decide, based on the authorization information, whether to delete the F1 interface, whether to allow the establishment of the F1 interface, whether to switch off the IAB-DU cell, whether to configure the IAB-DU cell to prohibit UE access, etc. This helps the network side to flexibly control IAB nodes and meets the requirement to allow or prohibit the operation of IAB nodes within a specific temporal / spatial range.

[0009] According to a first aspect, a communication method is provided. The method may be performed by a donor node or by a chip or circuit built within a donor node. This is not limited to the present application.

[0010] The method includes: a first donor node receiving integrated access backhaul IAB authorization information, the IAB authorization information indicating the authorization status of the first IAB node, the first IAB node comprising a first distributed unit and a first mobile terminal, the first mobile terminal having an RRC connection to a second donor node, the first distributed unit attempting to establish an F1 connection to the first donor node or having an F1 connection, and being a different donor node from the first donor node and the second donor node; and the first donor node determining, based on the IAB authorization information, whether the first IAB node is authorized to respond to user equipment.

[0011] According to the solution in this application, when IAB authorization information is updated, the latest IAB authorization information is notified to the CU of the IAB-DU, and as a result, the CU of the IAB-DU can decide, based on the authorization information, whether to delete the F1 interface, whether to allow the establishment of the F1 interface, whether to switch the IAB-DU cell off, whether to configure the IAB-DU cell to prohibit UE access, etc.

[0012] According to a second aspect, a communication method is provided. The method may be performed by a donor node or by a chip or circuit built within a donor node. This is not limited to the present application.

[0013] The method includes: a second donor node transmitting integrated access backhaul IAB authorization information to a first donor node, the IAB authorization information indicating the authorization status of the first IAB node, the first IAB node comprising a first distributed unit and a first mobile terminal, the first mobile terminal having an RRC connection to the second donor node, and the first distributed unit attempting to establish or having an F1 connection to the first donor node.

[0014] In a possible implementation, before the second donor node transmits the IAB authorization information to the first donor node, the method further includes the second donor node receiving the IAB authorization information from the Access Mobility Management Function Unit (AMF) within the core network.

[0015] In a possible implementation, before the second donor node transmits IAB authorization information to the first donor node, the method includes: the second donor node receiving identification information of the first donor node from the third donor node, the third donor node being a donor node that had an RRC connection to the first mobile terminal before the first mobile terminal established an RRC connection to the second donor node.

[0016] In a possible implementation, the transmission of IAB authorization information from a second donor node to a first donor node includes the second donor node transmitting IAB authorization information to the first donor node based on the identification information of the first donor node.

[0017] According to a third aspect, a communication method is provided. The method may be performed by a donor node or by a chip or circuit built within a donor node. This is not limited to the present application.

[0018] The method includes: a third donor node sending integrated access backhaul IAB authorization information to a first donor node, the IAB authorization information indicating the authorization status of the first IAB node, the first IAB node comprising a first distributed unit and a first mobile terminal, the first mobile terminal having an RRC connection to a second donor node, the third donor node being a donor node that had an RRC connection to the first mobile terminal before the first mobile terminal established an RRC connection to the second donor node, and the first distributed unit attempting to establish an F1 connection to the first donor node or having an F1 connection.

[0019] In a possible implementation, before the third donor node transmits the IAB authorization information to the first donor node, the method further includes the third donor node receiving the IAB authorization information from the second donor node.

[0020] According to a fourth aspect, a communication method is provided. The method may be performed by an IAB node or by a chip or circuit built within an IAB node. This is not limited to the present application.

[0021] The method includes: a first integrated access backhaul IAB node transmitting IAB authorization information to a first donor node, the IAB authorization information indicating the authorization status of the first IAB node, the first IAB node comprising a first distributed unit and a first mobile terminal, the first mobile terminal having an RRC connection to a second donor node, and the first distributed unit attempting to establish or having an F1 connection to the first donor node.

[0022] In possible implementations, before an IAB node sends IAB authorization information to the first donor node, the method is: The first IAB node receives IAB authorization information from the Access Mobility Management Function Unit (AMF) within the core network; or The first IAB node receives IAB authorization information from a fourth donor node, the fourth donor node being a donor node that had an F1 connection to the first distributed unit before the first distributed unit established an F1 connection to the first donor node.

[0023] According to a fifth aspect, a communication method is provided. The method may be performed by an AMF or by a chip or circuit built within the AMF. This is not limited to the present application.

[0024] The method is as follows: The Access Mobility Management Function (AMF) within the core network transmits the integrated access backhaul (IAB) authorization information to a first donor node. The IAB authorization information indicates the authorization status of the first integrated access backhaul (IAB) node. The first IAB node includes a first distributed unit and a first mobile terminal. The first mobile terminal has an RRC connection to a second donor node. The first distributed unit is attempting to establish an F1 connection to the first donor node or has an F1 connection. The first donor node and the second donor node are different donor nodes.

[0025] In a possible implementation, before the AMF transmits the IAB authorization information to the first donor node, the method further includes: the AMF receiving the identification information of the first donor node transmitted by the first IAB node.

[0026] In a possible implementation, the AMF transmitting the IAB authorization information to the first donor node includes: the AMF transmitting the IAB authorization information to the first donor node based on the identification information of the first donor node.

[0027] In a possible implementation, before the AMF transmits the IAB authorization information to the first donor node, the method includes: the AMF receiving the identification information of the first donor node transmitted by the second donor node.

[0028] In a possible implementation, the AMF transmitting the IAB authorization information to the first donor node includes: the AFM transmitting the IAB authorization information to the first donor node based on the identification information of the first donor node.

[0029] According to a sixth aspect, a communication method is provided. The method may be executed by a donor node or may be executed by a chip or circuit built within the donor node. This is not limited in the present application.

[0030] The method is as follows: A fourth donor node transmits integrated access backhaul IAB authorization information to a first donor node, and the IAB authorization information indicates 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. The first mobile terminal has an RRC connection to a second donor node. The first logical distributed unit has an F1 connection to the fourth donor node. The second logical distributed unit includes attempting to establish an F1 connection to the first donor node or having an F1 connection.

[0031] According to 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 built within the IAB node. This is not limited in this application.

[0032] The method is as follows: A first integrated access backhaul IAB node transmits identification information of a first donor node to an access mobility management function AMF in a core network. The first IAB node includes a first distributed unit and a first mobile terminal. The first mobile terminal has an RRC connection to a second donor node. The first distributed unit includes attempting to establish an F1 connection to the first donor node or having an F1 connection. The AMF is configured to transmit IAB authorization information to the first donor node based on the identification information of the first donor node, and the IAB authorization information indicates the authorization status of the first IAB node.

[0033] According to an eighth aspect, a communication method is provided. The method may be executed by a donor node, or may be executed by a chip or circuit built within the donor node. This is not limited in this application.

[0034] The method includes: a second donor node transmitting the identification information of a first donor node to an Access Mobility Management Function Unit (AMF) in the core network, the second donor node having an RRC connection to a first mobile terminal, the first mobile terminal being a mobile terminal in a first integrated access backhaul IAB node, the first IAB node further including a first distributed unit, the first distributed unit attempting to establish or having an F1 connection to the first donor node, and the AMF being configured to transmit IAB authorization information to the first donor node based on the identification information of the first donor node, the IAB authorization information indicating the authorization status of the first IAB node.

[0035] According to the ninth aspect, a communication method is provided. The method may be performed by a donor node or by a chip or circuit built within a donor node. This is not limited to the present application.

[0036] The method includes: a third donor node transmitting the identification information of the first donor node to a second donor node, the second donor node being a donor node that has an RRC connection to the first donor node, the first donor node being a donor node that is attempting to establish an F1 connection to the first distributed unit or is already an F1 connection, and the third donor node being a donor node that had an RRC connection to the first mobile terminal before the first mobile terminal established an RRC connection to the second donor node.

[0037] According to a tenth aspect, a communication device is provided, the device including: a receiving module configured to receive integrated access backhaul IAB authorization information, the IAB authorization information indicating the authorization status of a first IAB node, the first IAB node comprising a first distributed unit and a first mobile terminal, the first mobile terminal having an RRC connection to a second donor node, and the first distributed unit attempting to establish an F1 connection to the first donor node or having an F1 connection, and being a different donor node from the first donor node and the second donor node; and a processing module configured to determine, based on the IAB authorization information, whether the first IAB node is authorized to respond to a UE.

[0038] According to the eleventh aspect, a communication device is provided. The device is a donor node having an RRC connection to a first mobile terminal, the device is a transmitting module configured to transmit integrated access backhaul IAB authorization information to the first donor node, the IAB authorization information indicates 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 transmitting module which is attempting to establish or has an F1 connection to the first donor node.

[0039] In possible implementations, the device further includes a receiving module configured to receive IAB authorization information from the Access Mobility Management Function Unit (AMF) within the core network.

[0040] In a possible implementation, the receiving module is further configured to receive identification information of the first donor node from a third donor node, the third donor node being a donor node that had an RRC connection to the first mobile terminal before the first mobile terminal established an RRC connection to the second donor node.

[0041] In a possible implementation, the transmission of IAB authorization information by a second transmission module to a first donor node includes the transmission of IAB authorization information to the first donor node based on the identification information of the first donor node.

[0042] According to a twelfth aspect, a communication device is provided, the device being a donor node that had an RRC connection to a first mobile terminal before the first mobile terminal established an RRC connection to a second donor node, the device including a transmitting module configured to transmit integrated access backhaul IAB authorization information to the first donor node, the IAB authorization information indicating the authorization status of the first IAB node, the first IAB node including a first distributed unit and a first mobile terminal, the first mobile terminal having an RRC connection to a second donor node, and the first distributed unit attempting to establish an F1 connection to the first donor node or having an F1 connection.

[0043] In a possible implementation, the device further includes a receiving module configured to receive IAB authorization information from a second donor node.

[0044] According to the 13th aspect, a communication device is provided, the device being a first integrated access backhaul IAB node, the device including a transmitting module configured to transmit IAB authorization information to a first donor node, the IAB authorization information indicating the authorization status of the first IAB node, the first IAB node including a first distributed unit and a first mobile terminal, the first mobile terminal having an RRC connection to a second donor node, and the first distributed unit attempting to establish an F1 connection to the first donor node or having an F1 connection.

[0045] In possible implementations, the device is configured to receive IAB authorization information from the Access Mobility Management Function Unit (AMF) in the core network, or from a second donor node; or, the first IAB node receives IAB authorization information from a fourth donor node, the fourth donor node being a donor node that had an F1 connection to the first distributed unit before the first distributed unit established an F1 connection to the first donor node.

[0046] According to the 14th aspect, a communication device is provided. The method is an Access Mobility Management Function Unit (AMF) in a core network, corresponding to an Integrated Access Backhaul IAB node, the device including a transmitting module configured to transmit IAB authorization information to a first donor node, the IAB authorization information indicating the authorization status of the first Integrated Access Backhaul IAB node, the first IAB node including a first distributed unit and a first mobile terminal, the first mobile terminal having an RRC connection to a second donor node, and the first distributed unit attempting to establish an F1 connection to the first donor node or having an F1 connection, which is a different donor node from the first donor node and the second donor node.

[0047] In a possible implementation, the device further includes a receiving module configured to receive identification information of a first donor node transmitted by a first IAB node.

[0048] In a possible implementation, the transmission module transmitting IAB authorization information to the first donor node includes the AMF transmitting IAB authorization information to the first donor node based on the identification information of the first donor node.

[0049] In possible implementations, the receiving module is further configured to receive identification information of the first donor node transmitted by the second donor node.

[0050] In a possible implementation, the transmission of IAB authorization information by the transmitting module to the first donor node includes the AFM transmitting IAB authorization information to the first donor node based on the identification information of the first donor node.

[0051] According to the 15th aspect, a communication device is provided. The device is a donor node having an F1 connection to a first logical distributed unit, the device includes a transmitting module configured to transmit integrated access backhaul IAB authorization information to the first donor node, the IAB authorization information indicating 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, the first mobile terminal has an RRC connection to a second donor node, and the second logical distributed unit is attempting to establish an F1 connection to the first donor node or has an F1 connection.

[0052] According to the sixteenth aspect, a communication device is provided, the device including a transmitting module configured to transmit identification information of a first donor node to an Access Mobility Management Function Unit (AMF) in the core network, the first IAB node including a first distributed unit and a first mobile terminal, the first mobile terminal having an RRC connection to a second donor node, the first distributed unit attempting to establish an F1 connection to the first donor node or having an F1 connection, the AMF being configured to transmit IAB authorization information to the first donor node based on the identification information of the first donor node, the IAB authorization information indicating the authorization status of the first IAB node.

[0053] According to the 17th aspect, a communication device is provided, the device including a transmitting module configured to transmit identification information of a first donor node to an Access Mobility Management Function Unit (AMF) in the core network, the second donor node having an RRC connection to a first mobile terminal, the first mobile terminal being a mobile terminal in a first integrated access backhaul IAB node, the first IAB node further including a first distributed unit, the first distributed unit attempting to establish an F1 connection to the first donor node or having an F1 connection, the AMF being configured to transmit IAB authorization information to the first donor node based on the identification information of the first donor node, the IAB authorization information indicating the authorization status of the first IAB node.

[0054] According to the 18th aspect, a communication device is provided, the device including a transmitting module configured to transmit identification information of a first donor node to a second donor node, the second donor node being a donor node having an RRC connection to a first mobile terminal, the first donor node being a donor node attempting to establish or having an F1 connection to a first distributed unit, and the third donor node being a donor node that had an RRC connection to the first mobile terminal before the first mobile terminal established an RRC connection to the second donor node.

[0055] According to the 19th aspect, a wireless communication device is provided, the device including a module or unit configured to perform a method in the first aspect or any one of possible implementations of the first aspect.

[0056] According to the 20th aspect, a wireless communication device is provided, the device including a module or unit configured to perform a method in the second aspect or any one of possible implementations of the second aspect.

[0057] According to the 21st aspect, a wireless communication device is provided, the device including a module or unit configured to perform a method in any one of the third aspect or a possible implementation of the third aspect.

[0058] According to the 22nd aspect, a wireless communication device is provided, the device including a module or unit configured to perform a method in the fourth aspect or any one of possible implementations of the fourth aspect.

[0059] According to the 23rd aspect, a wireless communication device is provided, the device including a module or unit configured to perform a method in the fifth aspect or any one of possible implementations of the fifth aspect.

[0060] According to the 24th aspect, a wireless communication device is provided, the device including a module or unit configured to perform a method in the sixth aspect or any one of possible implementations of the sixth aspect.

[0061] According to the 25th aspect, a wireless communication device is provided, the device including a module or unit configured to perform a method in the 7th aspect or any one of possible implementations of the 7th aspect.

[0062] According to the 26th aspect, a wireless communication device is provided, the device including a module or unit configured to perform a method in the 8th aspect or any one of possible implementations of the 8th aspect.

[0063] According to the 27th aspect, a wireless communication device is provided, the device including a module or unit configured to perform a method in the 9th aspect or any one of possible implementations of the 9th aspect.

[0064] According to the 28th aspect, a communication device including a processor is provided. The processor may be coupled to storage and configured to perform methods in the first aspect and possible implementations of the first aspect, the second aspect and possible implementations of the second aspect, the third aspect and possible implementations of the third aspect, the sixth aspect and possible implementations of the sixth aspect, the eighth aspect and possible implementations of the eighth aspect, or the ninth aspect and possible implementations of the ninth aspect. In possible implementations, the communication device further includes storage. In possible implementations, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

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

[0066] In other implementations, the communication device is a chip or a chip system. If the communication device is a chip or a chip system, the communication interface may be an input / output interface, interface circuit, output circuit, input circuit, pin, associated circuit, or similar in the chip or chip system. Alternatively, the processor may be embodied as a processing circuit or logic circuit.

[0067] According to the 29th aspect, a communication device including a processor is provided. The processor may be coupled to storage and configured to execute instructions in the storage to carry out the methods in the fourth aspect and possible implementations of the fourth aspect, or the seventh aspect and possible implementations of the seventh aspect. In possible implementations, the communication device further includes storage. In possible implementations, the communication device further includes a communication interface, and the processor is coupled to the communication interface. In possible implementations, the transceiver may be a transceiver circuit. In possible implementations, the input / output interface may be an input / output circuit.

[0068] In the implementation, the communication device is an IAB node. If the communication device is an IAB node, the communication interface may be a transceiver or an input / output interface. In possible implementations, the transceiver may be a transceiver circuit. In possible implementations, the input / output interface may be an input / output circuit.

[0069] In other implementations, the communication device is a chip or a chip system. If the communication device is a chip or a chip system, the communication interface may be an input / output interface, interface circuit, output circuit, input circuit, pin, associated circuit, or similar in the chip or chip system. Alternatively, the processor may be embodied as a processing circuit or logic circuit.

[0070] According to the 30th aspect, a communication device including a processor is provided. The processor may be coupled to storage and configured to execute instructions in the storage to carry out the methods in the fifth aspect and possible implementations of the fifth aspect. In possible implementations, the communication device further includes storage. In possible implementations, the communication device further includes a communication interface, and the processor is coupled to the communication interface. In possible implementations, the transceiver may be a transceiver circuit. In possible implementations, the input / output interface may be an input / output circuit.

[0071] In the implementation, the communication device is an AMF. If the communication device is an AMF, the communication interface may be a transceiver or an input / output interface. In possible implementations, the transceiver may be a transceiver circuit. In possible implementations, the input / output interface may be an input / output circuit.

[0072] In other implementations, the communication device is a chip or a chip system. If the communication device is a chip or a chip system, the communication interface may be an input / output interface, interface circuit, output circuit, input circuit, pin, associated circuit, or similar in the chip or chip system. Alternatively, the processor may be embodied as a processing circuit or logic circuit.

[0073] According to the 31st aspect, a communication device is provided which includes an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal via the input circuit and transmit a signal via the output circuit to carry out a method in any one of the first to 9th aspects and any one of the possible implementations of those aspects.

[0074] In a particular implementation process, the communication device may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, various logic circuits, or the like. The input signal received by the input circuit may be received and input by, for example, a receiver, and the signal output by the output circuit may be output to, for example, a transmitter, and transmitted by the transmitter. The input circuit and the output circuit may be different circuits or the same circuit. In this case, the circuits are used as the input circuit and the output circuit, respectively, at different points in time. The specific implementations of the processor and various circuits are not limited to the embodiments of this application.

[0075] According to the 32nd aspect, a processing unit is provided which includes a processor and storage. The processor is configured to read instructions stored in the storage, receive signals via a receiver, and transmit signals via a transmitter to perform a method in any one of the first through 9th aspects and any one of the possible implementations of those aspects.

[0076] In possible implementations, there is one or more processors and one or more storage devices.

[0077] In possible implementations, the storage and processor may be integrated, or they may be located separately.

[0078] In a particular implementation process, the storage may be non-transitory memory, such as read-only memory (ROM). The storage and processor may be integrated on the same chip or located on different chips. The type of storage and the arrangement of the storage and processor are not limited to the embodiments of this application.

[0079] It should be understood that related data exchange processes, such as the transmission of instruction information, may be processes that output instruction information from the processor, and the reception of capability information may be processes that receive input capability information by the processor. Specifically, data output by the processor may be output to the transmitter, and input data received by the processor may be from the receiver. The transmitter and receiver may be collectively called transceivers.

[0080] The processor in the aforementioned embodiments may be a chip, and the processor may be implemented using hardware or software. When hardware is used for implementation, the processor may be a logic circuit, an integrated circuit, or the like. When software is used for implementation, the processor may be a general-purpose processor and may be implemented by reading software code stored in storage. The storage may be integrated with the processor or may be located outside the processor and exist independently.

[0081] According to the 33rd aspect, a computer program product is provided. The computer program product includes a computer program (sometimes called code or instructions). When the computer program is executed, the computer becomes capable of performing any one of the first through 9th aspects and any one of the possible implementations thereof.

[0082] According to the 34th aspect, a computer-readable medium is provided. The computer-readable medium stores a computer program (sometimes called code or instructions). When the computer program is executed on the computer, the computer becomes capable of performing any one of the first through 9th aspects and any one of the possible implementations thereof.

[0083] According to the 35th aspect, a communication system is provided which includes at least one of the first donor node, second donor node, third donor node, fourth donor node, first IAB node, and AMF described above. [Brief explanation of the drawing]

[0084] [Figure 1] Figure 1 is a diagram of the architecture of an IAB system applicable to the technical solution in this application.

[0085] [Figure 2] Figure 2 is a diagram showing the configuration of the IAB node.

[0086] [Figure 3] Figure 3 shows the control plane and user plane protocol stack in an IAB network.

[0087] [Figure 4] Figure 4 is a schematic flowchart of network access by IAB nodes.

[0088] [Figure 5] Figure 5 shows a partial migration scenario for an IAB node.

[0089] [Figure 6] Figure 6 shows an IAB topology redundancy scenario.

[0090] [Figure 7] Figure 7 illustrates a sequential partial migration scenario for mobile IAB nodes.

[0091] [Figure 8] Figure 8 shows a DU migration scenario for an IAB node.

[0092] [Figure 9] Figure 9 is a schematic flowchart of the IAB approval information transfer method according to the original application.

[0093] [Figure 10] Figure 10 is a schematic flowchart of another IAB approval information transfer method according to the present application.

[0094] [Figure 11] Figure 11 is a schematic flowchart of yet another IAB approval information transfer method according to the present application.

[0095] [Figure 12] Figure 12 is a schematic flowchart of yet another IAB approval information transfer method according to the present application.

[0096] [Figure 13] Figure 13 is a schematic flowchart of yet another IAB approval information transfer method according to the present application.

[0097] [Figure 14]Figure 14 is a schematic flowchart of yet another IAB approval information transfer method according to the present application.

[0098] [Figure 15] Figure 15 is a schematic flowchart of yet another IAB approval information transfer method according to the present application.

[0099] [Figure 16] Figure 16 is a schematic flowchart of yet another IAB approval information transfer method according to the present application.

[0100] [Figure 17] Figure 17 is a block diagram of a communication device according to an embodiment of the present application.

[0101] [Figure 18] Figure 18 is a block diagram of another communication device according to an embodiment of the present application.

[0102] [Figure 19] Figure 19 is a diagram of a chip system according to an embodiment of the present application. [Modes for carrying out the invention]

[0103] The technical solutions in this application will be explained below with reference to the attached drawings.

[0104] The technical solutions in the embodiments of this application are applicable to various communication systems, such as Global System for Mobile communications (GSM), Code Division Multiple Access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) systems, General Packet Radio Service (GPRS), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Wireless Fidelity (Wi-Fi) systems, Device-to-Device (D2D) communication systems, Vehicle-to-Everything (V2X) communication systems, Universal Mobile Telecommunications System (UMTS), and Worldwide Interoperability for Microwave Access. This technology may be applicable to WiMAX communication systems, machine-to-machine (M2M) communication systems, machine-type communication (MTC) systems, Internet of Things (IoT) communication systems, non-terrestrial network (NTN) systems, 5th generation (5G) mobile communication systems, new radio (NR) systems, or future wireless communication systems.

[0105] First, we will briefly describe the network architecture applicable to this application.

[0106] In this application, relay nodes that support integrated access backhaul are referred to as IAB nodes to distinguish them from LTE (long term evolution, LTE) relays, and a system including IAB nodes is also referred to as a relay system.

[0107] It should be understood that all node and information names in this application are merely designated for the purpose of facilitating explanation in this application, and that actual network names may differ. It should be understood that node and information names are limited in this application. Conversely, any name having the same or similar function as a node or information used in this application is considered a method or equivalent substitution in this application and falls within the scope of protection of this application. Further details are not provided below.

[0108] To design flexible and convenient access and backhaul solutions, wireless transmission solutions are used in IAB scenarios for both access links (AL) and backhaul links (BL).

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

[0110] For example, a donor node may be a donor base station. In a 5G network, a donor node may be abbreviated as an IAB donor or DgNB (i.e., donor gNodeB). A donor node may be a complete entity, or it may be a configuration in which a central unit (CU) (hereinafter abbreviated as donor CU or CU) and a distributed unit (DU) (hereinafter abbreviated as donor DU) are separated; in other words, a donor node includes a donor CU and a donor DU. Embodiments of this application and accompanying drawings illustrate the method provided in embodiments of this application using an example in which a donor node includes a donor CU and a donor DU.

[0111] An IAB node includes a mobile termination (MT) portion and a distributed unit (DU) portion. When facing a parent node, the IAB node can be considered a terminal device. In this case, the IAB node plays the role of an MT. When facing a child node (the child node may be a terminal device or terminal device portion of another IAB node), the IAB node can be considered a communication device. In this case, the IAB node plays the role of a DU. Therefore, an IAB node can be considered to include an MT portion and a DU portion. An IAB node can establish a backhaul connection to at least one parent node of an IAB node via its MT portion. A DU portion within an IAB node can provide access services to a terminal device or MT portion within another IAB node.

[0112] Alternatively, the donor CU may be in a form in which the user plane (UP) (abbreviated as CU-UP in this specification) and the control plane (CP) (abbreviated as CU-CP in this specification) are separated; in other words, the donor CU includes both CU-CP and CU-UP.

[0113] IAB nodes are connected to the core network via donor nodes through wired links. For example, in a 5G standalone architecture, IAB nodes are connected to the 5G core network (5G core, 5GC) via donor nodes through wired links. In a 5G non-standalone architecture, IAB nodes are connected to the evolved packet core network (EPC) via eNB on the control plane, and to the EPC via donor nodes and eNB on the user plane.

[0114] To ensure service transmission reliability, the IAB network supports multi-hop IAB node and multi-connection IAB node networking. Therefore, multiple transmission paths may exist between terminal devices and donor nodes. Within a single path, there are predetermined hierarchical relationships between IAB nodes and between IAB nodes and their corresponding donor nodes. Each IAB node considers the node providing backhaul services to it as its parent node. Conversely, each IAB node may be considered a child node of its parent node.

[0115] For example, referring to Figure 1, the parent node of IAB node 1 is the donor node, IAB node 1 is the parent node of IAB node 2 and IAB node 3, both IAB node 2 and IAB node 3 are parent nodes of IAB node 4, and the parent node of IAB node 5 is IAB node 3. Uplink data packets from a terminal device are transmitted to the donor node via one or more IAB nodes, and then may be transmitted by the donor node to a mobile gateway device (e.g., a UPF network element in a 5G network). Downlink data packets are received from the mobile gateway device by the donor node and then transmitted to the terminal device via one or more IAB nodes. There are two available paths for data packet transmission between terminal device 1 and the donor node, and they are: Terminal device 1 → IAB node 4 → IAB node 3 → IAB node 1 → Donor node, and The sequence is Terminal Device 1 → IAB Node 4 → IAB Node 2 → IAB Node 1 → Donor Node. There are three available paths for data packet transmission between terminal device 2 and the donor node, and they are: Terminal device 2 → IAB node 4 → IAB node 3 → IAB node 1 → Donor node, Terminal device 2 → IAB node 4 → IAB node 2 → IAB node 1 → Donor node, and The sequence is Terminal Device 2 → IAB Node 5 → IAB Node 2 → IAB Node 1 → Donor Node.

[0116] In an IAB network, it will be understood that a single transmission path between a terminal device and a donor node may include one or more IAB nodes. Each IAB node must maintain a wireless backhaul link to its parent node and wireless links to its child nodes. 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 another IAB node, there is a wireless backhaul link between the IAB node and the child node (i.e., the other IAB node). For example, referring to Figure 1, in the path "Terminal device 1 → IAB node 4 → IAB node 3 → IAB node 1 → Donor 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 donor node via a wireless backhaul link.

[0117] For example, the IAB node may be customer premises equipment (CPE), a residential gateway (RG), or similar. In this case, the method provided in the embodiments of this application may be further applied to home access scenarios.

[0118] The aforementioned IAB networking scenario is merely an example. In IAB scenarios combining multi-hop and multi-connectivity, there are many other possible IAB networking scenarios. For example, an IAB node of one donor node and another donor node might form dual connectivity to serve terminal devices. The possible scenarios cannot be listed individually here.

[0119] Figure 2 is a diagram of a system architecture applicable to the embodiments of this application. As shown in Figure 2, the IAB (or what is called an IAB device) is a wireless backhaul base station. An essential characteristic of the IAB is that it must first establish a backhaul channel with a target macro base station before providing wireless coverage services to the outside. This is similar to that of customer premises equipment (CPE), the difference being that CPE provides wireless fidelity (Wi-Fi) coverage to the outside. The IAB provides the base station's radio signal, for example, a 5th generation (5G) signal, to the outside. The IAB is primarily used to extend the coverage of a macro base station. Due to features such as the high-power multi-antenna receiving capability of the backhaul device, the IAB extends the remote coverage of the macro base station. In this way, a weak coverage area that was originally far from the macro base station is transformed into a good coverage area near the macro base station. The IAB needs to establish connectivity with a fixed macro base station, and therefore typically needs precise access to the target macro base station to establish a backhaul channel.

[0120] In the IAB network architecture shown in Figure 2, standalone (SA) networking is used as an example. An IAB donor can include a central unit (CU) and distributed units (DU). That is, the functions of the IAB donor are divided, with some functions deployed on the CU and the remaining functions deployed on the DU. Multiple DUs share one CU. This can reduce costs and facilitate network expansion. The CU is connected to the DU via an F1 interface. Instead of an IAB donor, the CU is connected to the core network via a next-generation (NG) interface. Instead of an IAB donor, the CU is connected to another gNB via an Xn interface.

[0121] An IAB node DU (sometimes abbreviated as IAB-DU in this application) is logically connected to an IAB donor CU (sometimes abbreviated as CU in this application) via an F1 interface. In practice, the IAB-DU is connected to the CU via an NR Uu interface between each hop of the IAB-MT and the parent node DU. However, since the IAB-DU can ultimately communicate with the CU, it is possible to think of the F1 interface as logically existing. The IAB-MT function is defined as a component similar to a UE. In an IAB network, the MT is referred to as a function that resides on an IAB node. Since the MT has functions similar to those of a typical UE, it is possible to think of the IAB node accessing the parent node or network via the MT.

[0122] The user plane and control plane protocol stacks in the IAB network are shown in Figure 3. The F1 interface supports the user plane protocol (F1-user plane, F1-U) and the control plane protocol (F1-control plane, F1-C). As shown in Figure 3(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), IP (Internet protocol), and other protocol layers. As shown in Figure 3(a), the control plane protocol includes one or more of the following protocol layers: F1AP (F1 application protocol), SCTP (stream control transport protocol), IP, and other protocol layers. Through F1-C, IAB donors and IAB nodes can perform interface management, IAB-DU management, UE context-related settings, and similar functions. Through F1-U, IAB donors and IAB nodes can perform functions such as user-plane data transmission and downlink transmission status feedback.

[0123] It should be noted that Figures 1 and 2 are merely examples. The technical solution in this application may be applicable to various communication systems, including access network units. For example, the access network unit may be an IAB in Figure 1 or a gNB as shown in Figure 2. The communication system may also further include terminal devices.

[0124] The terminal device in the embodiments of this application may also be called a terminal and may be a device having wireless transceiver functionality. The terminal device may be deployed on land, including indoors, outdoors, handheld, or in a vehicle, on water (e.g., on a ship), or in the air (e.g., on an airplane, balloon, or satellite). The terminal device may also be user equipment (UE). The UE includes handheld devices, in-vehicle devices, wearable devices, or computing devices having wireless communication capabilities. For example, the UE may be a mobile phone, a tablet computer, a computer with wireless transceiver functionality, or the like. The terminal device may also be a device capable of supporting the terminal in performing its functions, such as a chip or chip system. The device may be integrated into the terminal. The technical solutions provided in the embodiments of this application will illustrate the technical solutions provided in the embodiments of this application using an example in which a device configured to perform the functions of a terminal is the terminal. It should be understood that "terminal" is a general term and includes the most common mobile phones, CPEs, and integrated access and backhaul (IAB) terminals. Terminal devices may also be virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in smart cities, wireless terminals in smart homes, or similar.

[0125] The network device in the embodiments of this application may include a base station (BS) and may be a device located in a radio access network that is capable of performing wireless communication with a terminal. The base station may take multiple forms, such as a macro base station, a micro base station, a relay station, an access point, a backhaul station, or the like. For example, the base station in the embodiments of this application may be a base station in 5G or a base station in LTE. The base station in 5G may be called a transmission reception point (TRP) or a next-generation node B (gNB). In the embodiments of this application, the device configured to perform the functions of the network device may be the network device itself, or a device capable of supporting the network device in performing the functions, such as a chip or a chip system. The device may be installed in the network device. In the technical solutions provided in the embodiments of this application, an example in which the device configured to perform the functions of the network device is the network device and the network device is the base station is used to illustrate the technical solutions provided in the embodiments of this application.

[0126] In the embodiments of this application, the chip system may include a chip, or it may include a chip and other separate components.

[0127] It should be understood that the network architectures shown above are merely illustrative examples, and that the network architectures applicable to the embodiments of this application are not limited to them. Any network architecture capable of performing the functions of the aforementioned network elements is applicable to the embodiments of this application.

[0128] It should be further understood that the aforementioned names are merely established to distinguish different functions and do not constitute any limitation to the present application. The present application does not rule out the possibility of using other names in 6G networks and other future networks.

[0129] The names of the interfaces between network elements in Figure 2 are merely examples, and it should be further understood that interfaces may have other names in specific implementations. This is not particularly limited in this application. In addition, the names of the information (or signaling) transmitted between the aforementioned network elements are merely examples and do not constitute any limitation on the function of the information.

[0130] The following describes the process of accessing the network by an IAB node (IAB integration). Figure 4 is a flowchart of how an IAB node accesses the network. The process of accessing the network by IAB node 2 is used as an example. IAB node 1 is the parent node of IAB node 2 and is already in the network.

[0131] The network access procedure for IAB nodes can be summarized as follows:

[0132] Phase 1: The IAB-MT accesses the cell in a manner similar to that of a typical UE, establishes an RRC connection to the donor node, and indicates that it is an IAB node when it establishes the RRC connection (an IAB node indication is carried in the RRC Setup Complete information). The IAB node indication is also carried when the CU sends the Initial UE Message to the core network (specifically, the AMF network element within the core network). The AMF performs authentication to the IAB-MT and includes an IAB authorized information element (i.e., "IAB authorization information" in this invention) in the Initial Continuity Setup Request, which instructs the CU to establish the initial UE context of the IAB-MT. If authentication is successful, the value of the IAB authorized information element is permitted. Otherwise, the value of the IAB authorized information element is not permitted. The network access procedure for the IAB node is described herein. Therefore, if the value of the IAB authorization information element is permitted, it is assumed that the subsequent steps will be performed.

[0133] Phase 2: The CU configures the backhaul link RLC channel (BH RLC Channel) for the IAB node and performs routing configuration using RRC messages. Specifically, in this case, only the default backhaul link RLC channel and default route are configured for use during subsequent initial configuration of the F1 interface (see Phase 3 for details). After the F1 interface is established, more backhaul link RLC channels and routing paths can be configured for the IAB node by using F1-C information for use with subsequent more F1-C information and F1-U user plane data. In Phase 2, in addition to configuring IAB node 2, route updates are further performed on the node between the IAB node and the donor (IAB node 1) to inform the node how to select the next hop link and next hop RLC channel when a data packet from or sent to IAB node 2 is received.

[0134] Phase 3: IAB-DU2 uses the default settings acquired in Phase 2 to send an F1 Connection Setup Request (F1 SETUP REQUEST information, which carries the configuration information of the DU2 cell) to the donor CU, requesting the establishment of the F1 interface. The donor CU responds to IAB-DU2 with an F1 Connection Setup Response (F1 SETUP RESPONSE) information, activates the cell, and completes the establishment of the F1 interface. Thus, IAB-DU2 is activated and ready to respond to the UE and the next hop IAB-MT.

[0135] If the value of the IAB authorization information element is authorized, the donor CU will perform the subsequent steps (including setting up backhaul link RLC channels and similar) based on the above description of accessing the network by the IAB. If the value of the IAB authorization information element is not authorized, it indicates that the IAB node is not authorized to provide IAB services, and the donor CU may perform the following actions. For example, the default configuration may not be set for the IAB-MT, or the default configuration may be set for the IAB-MT, but the F1 connection setup request initiated by the IAB-DU may be rejected.

[0136] In addition to AMF sending IAB authorization information to CU when an IAB node first accesses the network, if the IAB's authorization status subsequently changes (for example, due to the IAB moving to a specific location or the IAB's service time being specified), AMF sends updated IAB authorization information element values ​​to CU using UE CONTEXT MODIFICATION REQUEST.

[0137] Large-scale mobility of IAB nodes will have some impact on the core network. Mobile IAB nodes require a separate authorization information element, namely a mobile IAB authorization information element. This information element is used in exactly the same way as the IAB authorization information element.

[0138] It should be consistently noted that in this application, the IAB node may be a general IAB node or a mobile IAB node. Accordingly, when the IAB node is a mobile IAB node, the mobile IAB Authorized information element is used as the IAB authorization information for the IAB node. This is not limited to the present application.

[0139] The above explains the basic concepts and network access processes of IAB. Below, we describe some topology change-related features of IAB. Specifically, these features all apply to the case of inter-CUs (inter-donor CUs). When intra-CUs (intra-donor CUs) and inter-donor DUs exist, the inter-donor DUs exist, but inter-CUs do not, allowing the CUs to perform reconfiguration. However, the following scenarios require interaction between CUs.

[0140] 1. Partial migration

[0141] Figure 5 shows a partial migration of an IAB node. The IAB node being migrated is called the boundary node, for example, IAB node 2. The downstream node of the boundary node is called the descendant node, for example, IAB node 4. Before the migration, there is an RRC connection between IAB-MT2 and CU1, and an F1 interface between IAB-DU2 and CU1. IAB node 2 communicates with the IAB donor via the source path (through IAB node 1, which includes IAB-MT1 and IAB-DU1). During the partial migration, an interCU cell handover is performed for IAB-MT2, and an RRC connection to CU2 is established.

[0142] To avoid introducing the process of re-establishing the F1 interface, during partial 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 changes to an inter-topological path. CU1 ←→ donor-DU2 ←→ IAB-MT3 ←→ IAB-DU3 ←→ IAB-MT2 ←→ IAB-DU2 In Figure 5, CU1 and CU2 are referred to as the F1-terminating CU and non-F1-terminating CU, respectively, and are sometimes called the source CU and target CU. It should be noted that the data does not pass through CU2 during transmission along the path, and CU1 and donor CU2 communicate directly with each other via the IP network.

[0143] The F1 terminating CU sends an IAB Transport Migration Management Request message to the F1 non-terminating CU to request the establishment of inter-topology traffic transmission. If the F1 non-terminating CU agrees to the establishment, it responds to the F1 terminating CU with an IAB Transport Migration Management Response message. If the F1 non-terminating CU does not agree to the establishment, it responds with an IAB Transport Migration Management Rejection message. If the F1 terminating CU or the F1 non-terminating CU subsequently plans to perform actions such as QoS modification or withdrawal on the traffic, further IAB Transport Migration Modification Request / Response messages may be exchanged.

[0144] 2. Topology redundancy (also known as dual connectivity)

[0145] As shown in Figure 6, in NR, the UE may be dual-connected to two different base stations, improving throughput and robustness. The IAB-MT may be dual-connected to two different CUs, and data between the IAB-DU and the CU (specifically, the F1-terminating CU) may be transmitted simultaneously through two paths, thereby doubling throughput. RRC connections exist between the IAB-MT and CU1 and CU2, respectively, and there is an F1 interface between IAB-DU2 and CU1. Data transmission via the blue path is similar to partial migration, and communication between CU1 and donor DU2 is performed over the IP network without going through CU2.

[0146] 3. Radio Link Failure Recovery (RLF recovery)

[0147] If an RLF occurs between the IAB-MT and the source cell, another cell may be selected to initiate RRC re-establishment. This cell may be from a different CU. After interCU RRC re-establishment is performed for IAB-MT2, the topology is the same as in partial migration. The RRC connection of IAB-MT2 is changed to CU2, and the F1 interface of IAB-DU2 is still on CU1. The signaling exchange differs between RLF recovery and partial migration, but the final state achieved is the same.

[0148] 4. Consecutive partial migration

[0149] As shown in Figure 7, the MT is handed over from CU2 to CU3, and the DU's F1 interface is always associated with CU1. Here, mIAB stands for Mobile IAB. The mIAB node in Figure 7 is directly connected to the donor DU, but there may be another IAB node between the mIAB node and the donor DU. This is not limited to the present application. The MT may also be handed over from CU1 to CU2 (e.g., Figure 7), or from another CU to CU2 (this will be understood in relation to the DU migration scenario described below).

[0150] 5. DU migration

[0151] When an mIAB node moves far away, it may be difficult for the mIAB-DU to maintain its IP connection to the original CU, or the transmission delay may be very large. Therefore, DU migration is introduced to support large-scale mobility. As shown in Figure 8, the MT's RRC connection is always on CU2, and the DU's F1 interface is migrated from CU1 to CU3. This figure shows two logical DUs, mIAB-DU1 and mIAB-DU2, on a physical DU. DU migration is performed in the following way: Assume the source DU is mIAB-DU1. The mIAB node generates a new logical DU, mIAB-DU2, and mIAB-DU2 establishes an F1 interface with CU3. CU1 sends a handover request for the UE to CU3, handing over the UE from the cell of mIAB-DU1 to the cell of mIAB-DU2. CU1 then releases the F1 interface with mIAB-DU1. Thus, the DU migration is complete. CU1 is the IAB-DU source F1 termination CU, CU3 is the IAB-DU target F1 termination CU, and CU2 is the MT CU (sometimes called the RRC termination CU).

[0152] DU migration is assumed to be completely separate from MT migration, meaning that the CU of DU can always be different from the CU of MT. Therefore, in a sequential partial migration, if the F1-terminating CU of DU is always CU1, MT is not necessarily handed over from CU1 to CU2. That is just one of several implementations. During DU migration, MT may be at CU2, and DU migrates from CU1 to CU3. Optionally, CU2 and CU1 or CU3 may be the same CU.

[0153] DU migration is assumed to be completely separate from MT migration because the DU migration process is complex (it requires the generation of two logical DUs, and the UEs must hand over to the new logical DUs one by one), and frequent DU migration is not appropriate. Therefore, the CU for DU should be a CU with a large control range. However, MT migration is an MT handover and may be performed frequently. The selection of the CU for MT is determined based on signal quality. Therefore, the CU for MT may differ from the CU for DU.

[0154] 6. Access to different CUs via IAB (IAB integration to different CUs)

[0155] Based on the aforementioned assumption that DU migration is completely separated from MT migration, in the IAB integration process, the MT's RRC connection and the DU's F1 interface may be terminated on different CUs (for example, the DU's CU may be a CU with a large control range, and the MT's CU may be a CU corresponding to the cell with the best signal quality). That is, when an IAB node accesses the network, the topology shown in Figure 5 is constructed.

[0156] In many scenarios (e.g., IAB node migration scenarios), the IAB-MT CU may differ from the IAB-DU CU. In some implementations, the IAB-DU CU also needs to know the IAB authorization information of the IAB-MT. For example, when an IAB node first accesses the network, if the IAB-MT CU sets default settings for the MT and the IAB-DU sends an F1 interface setup request to the IAB-DU CU, the IAB-DU CU needs to know whether the IAB node is authorized or not in order to perform the corresponding action (e.g., if the IAB node is not authorized, the IAB-DU's F1 interface setup request will be rejected). However, prior art does not consider how the IAB-DU CU knows the current IAB authorization information when the IAB-MT CU differs from the IAB-DU CU.

[0157] This application provides several communication methods. Exemplary, not limiting, examples include: when IAB authorization information is updated, the latest IAB authorization information can be notified to the IAB-DU's CU, which in turn can decide, based on the authorization information, whether to remove the F1 interface, whether to allow the establishment of the F1 interface, whether to switch the IAB-DU's cell off, or whether to configure the IAB-DU's cell to prohibit UE access. This helps the network side to flexibly control IAB nodes and meets the requirement to permit or prohibit the operation of IAB nodes within a specific temporal / spatial range.

[0158] In this invention, when ordinal numbers such as "first," "second," "third," "fourth," and "fifth" are mentioned, it should be understood that unless the ordinal number explicitly indicates a contextual order, it is merely used for distinction.

[0159] The method for notifying the IAB-DU's CU of the latest IAB approval information varies depending on the specific scenario. It should be understood that the description of specific scenarios in the embodiments of this application is merely an example. In addition to the application scenarios described above, the methods provided in the embodiments of this application are also applicable to application scenarios where similar problems exist.

[0160] The following details several methods for notifying the IAB-DU's CU of the latest IAB accreditation information. In scenarios where the following methods are applicable, the IAB-MT's CU differs from the IAB-DU's CU.

[0161] Method 1

[0162] The following uses the continuous partial migration scenario shown in Figure 7 as an example. In Figure 7, CU1 is the F1 termination CU of the DU, CU2 is the source CU of the MT, and CU3 is the target CU of the MT. In Method 1, the target CU of the MT first notifies the source CU of the MT, and then the source CU of the MT notifies the F1 termination CU of the DU. Method 1 is applicable to the continuous partial migration scenario.

[0163] Figure 9 is a schematic flowchart of Method 1. The method in Figure 9 includes at least some of the following:

[0164] S910:MT will be handed over from CU2 to CU3.

[0165] Specifically, prior to the migration, there is an RRC connection between IAB-MT and CU2, and an F1 interface between IAB-DU and CU1. During the partial migration, an interCU cell handover is performed for IAB-MT, and an RRC connection to CU3 is established. However, IAB-DU still maintains its F1 interface with CU1 and does not establish an F1 interface with CU3.

[0166] S920:AMF transmits IAB authorization information to CU3.

[0167] In possible implementations, before the AMF sends IAB authorization information to the CU3, the CU3 first sends route switching request information to the AMF to notify the AMF that the MT has been handed over to the CU3, and the AMF then forwards the MT's services to the CU3. The AMF responds to the CU3 with a PATH SWITCH REQUEST ACK information carrying the current values ​​of the IAB authorization information elements and / or the current values ​​of the mobile IAB authorization information elements (i.e., IAB authorization information).

[0168] In another possible implementation, if AMF detects that the IAB authorization information has changed, the current values ​​of the IAB authorization information elements and / or the mobile IAB authorization information elements (i.e., IAB authorization information) are carried in a UE Context Modification Request.

[0169] S930:CU3 transmits IAB authorization information to CU2.

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

[0171] In possible implementations, the instruction information sent by CU3 to CU2 directly carries the (mobile) IAB authorization information element, the value of which includes authorized or not authorized.

[0172] In another possible implementation, the information carries the (mobile) IAB authorization information element only if authorization is not granted. In this case, the value of the information element is not authorized. Alternatively, the instruction information carries instructions regarding releasing or not establishing an F1 connection.

[0173] Optionally, the IAB authorization information may need to further carry IAB node-related identifiers to indicate the IAB node associated with the authorization information. The IAB node-related identifiers must include at least one of the following: IAB-DU's gNB-DU ID, UE XnAP ID of IAB-MT in CU1, IAB-MT UE XnAP ID in CU2, and IAB-MT UE XnAP ID in CU3.

[0174] In subsequent steps and embodiments, unless otherwise specified, the method for indicating IAB authorization information may be the same as the method for indicating it in this step.

[0175] S940:CU2 transmits IAB authorization information to CU1.

[0176] Specifically, CU2 sends a message to CU1 that carries the instruction information transmitted by CU3.

[0177] In possible implementations, the message may be an IAB Transport Migration Modification Request message.

[0178] In another possible implementation, the instruction information may carry at least one of the following: the identifier of the CU3 (e.g., gNB ID and / or IP address) and the identifier of the MT in the CU3 (e.g., UE XnAP ID).

[0179] Optionally, the IAB authorization information may need to further carry IAB node-related identifiers to indicate the IAB node associated with the authorization information.

[0180] Method 2

[0181] Method 2 will be explained below using the continuous partial migration scenario shown in Figure 7 as an example. In Figure 7, CU1 is the F1 termination CU of the DU, CU2 is the source CU of the MT, and CU3 is the target CU of the MT. In Method 2, the target CU of the MT directly notifies the F1 termination CU of the DU. Method 2 is applicable to continuous partial migration, wireless link failure recovery, and topology redundancy scenarios.

[0182] Figure 10 is a schematic flowchart of Method 2. The method in Figure 10 includes at least some of the following:

[0183] S1010:MT will be handed over from CU2 to CU3.

[0184] Specifically, prior to the migration, there is an RRC connection between IAB-MT and CU2, and an F1 interface between IAB-DU and CU1. During the partial migration, an interCU cell handover is performed for IAB-MT, and an RRC connection to CU3 is established. However, IAB-DU still maintains its F1 interface with CU1 and does not establish an F1 interface with CU3.

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

[0186] In possible implementations, before the AMF sends IAB authorization information to the CU3, the CU3 first sends route switching request information to the AMF to notify the AMF that the MT has been handed over to the CU3, and the AMF then forwards the MT's services to the CU3. The AMF responds to the CU3 with a PATH SWITCH REQUEST ACK information carrying the current values ​​of the IAB authorization information elements and / or the current values ​​of the mobile IAB authorization information elements (i.e., IAB authorization information).

[0187] In another possible implementation, if AMF detects that the IAB authorization information has changed, the current values ​​of the IAB authorization information elements and / or the mobile IAB authorization information elements (i.e., IAB authorization information) are carried in a UE Context Modification Request.

[0188] Optionally, the IAB authorization information may need to further carry IAB node-related identifiers to indicate the IAB node associated with the authorization information. The IAB node-related identifiers must include at least one of the following: IAB-DU's gNB-DU ID, UE XnAP ID of IAB-MT in CU1, IAB-MT UE XnAP ID in CU2, and IAB-MT UE XnAP ID in CU3.

[0189] S1030:CU2 sends the identifier of CU1 to CU3.

[0190] Specifically, CU2 sends identification information to CU3 so that CU3 knows that the current F1-terminating CU is CU1.

[0191] S1040:CU3 sends IAB authorization information to CU1.

[0192] Specifically, CU3 sends a message to CU1 that carries authorization information for the (mobile) IAB node.

[0193] In possible implementations, the instruction information sent by CU3 to CU1 directly carries (mobile) IAB authorization information elements, including an authorization or denial value.

[0194] In another possible implementation, the information carries a (mobile) IAB authorization information element with a disauthorized value only if authorization is not granted. Alternatively, the instruction information carries instructions regarding releasing or not establishing an F1 connection.

[0195] Optionally, the IAB authorization information may need to further carry IAB node-related identifiers to indicate the IAB node associated with the authorization information.

[0196] In addition to the continuous partial migration scenario shown in Figure 7, it should be understood that Method 2 may be further applicable to inter-CU partial migration, inter-CU RLF recovery, and inter-CU topology redundancy scenarios where the IAB-MT's Master Node (MN) is non-F1-terminating (CU3). We assume that CU2 does not exist. In these scenarios, there are only two CUs, namely CU1 and CU3, and the IAB-MT migrates from CU1 to CU3. CU1 is not only the source CU of the IAB-MT, but also the F1-terminating CU of the IAB-DU.

[0197] In different scenarios, some of the steps S1010 through S1040 of Method 2 will differ.

[0198] In the case of a partial migration or RLF recovery scenario, there is a different MT migration behavior at step S1010. In the partial migration scenario, the MT is handed over from CU1 to CU3. In the RLF recovery scenario, the MT is experiencing a radio link failure at CU1. Therefore, the MT performs radio link failure recovery from CU1 to CU3 (the MT performs RLF recovery from CU1 to CU3). Step S1030 is deleted, and the other steps remain unchanged.

[0199] In a topology redundancy scenario, with dual connectivity, the IAB-MT's RRC connection is anchored on the MN, so the IAB-MT's MN is limited to CU3 (SN is CU1). There is an RRC connection between SN and IAB-MT, but SN is used to forward RRC messages between MN and IAB-MT. AMF sends authorization information from IAB-MT to MN. Only if MN is CU3 does CU3 need to further notify the F1-terminated CU (i.e., CU1) of the authorization information. If MN was originally CU1 and CU1 is the F1-terminated CU, there is no technical problem.

[0200] In the case of a topology redundancy scenario, step S1010 should be omitted. Both the MN and SN can know which CU is the F1-terminating CU based on MN instructions, OAM instructions, and similar. In step S1020, the MN obtains the latest authorization information for the MT. Since no MT handover or RLF recovery occurs, there is no exchange of routing procedures between the CU and the AMF. Therefore, the authorization information is obtained only by using a UE context change request in this case.

[0201] Furthermore, in the case of topology redundancy scenarios, this is also applicable to the IAB-MT EN-DC scenario. That is, the master node of the MT is the MeNB (LTE base station), the secondary node is the SgNB (NR base station), and the secondary node is the F1-terminating donor. In other words, CU1 is changed to a MeNB, CU3 is changed to a SgNB, and AMF is changed to an MME.

[0202] Method 3

[0203] Method 3 is described below using the continuous partial migration scenario shown in Figure 7 as an example. In Figure 7, CU1 is the F1 termination CU of the DU, CU2 is the source CU of the MT, and CU3 is the target CU of the MT. In Method 3, the F1 termination CU of the DU initiates the inter-topology traffic migration procedure to the target CU of the MT, and the target CU of the MT notifies the IAB authorization information in the response information. Method 3 is applicable to partial migration, continuous partial migration, radio link failure recovery, and topology redundancy scenarios.

[0204] Figure 11 is a schematic flowchart of Method 3. The method in Figure 11 includes at least some of the following:

[0205] S1110:MT will be handed over from CU2 to CU3.

[0206] Specifically, prior to the migration, there is an RRC connection between IAB-MT and CU2, and an F1 interface between IAB-DU and CU1. During the partial migration, an interCU cell handover is performed for IAB-MT, and an RRC connection to CU3 is established. However, IAB-DU still maintains its F1 interface with CU1 and does not establish an F1 interface with CU3.

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

[0208] In possible implementations, before the AMF sends IAB authorization information to the CU3, the CU3 first sends route switching request information to the AMF to notify the AMF that the MT has been handed over to the CU3, and the AMF then forwards the MT's services to the CU3. The AMF responds to the CU3 with a PATH SWITCH REQUEST ACK information carrying the current values ​​of the IAB authorization information elements and / or the current values ​​of the mobile IAB authorization information elements (i.e., IAB authorization information).

[0209] In another possible implementation, if AMF detects that the IAB authorization information has changed, the current values ​​of the IAB authorization information elements and / or the mobile IAB authorization information elements (i.e., IAB authorization information) are carried in a UE Context Modification Request.

[0210] Optionally, the IAB authorization information may need to further carry IAB node-related identifiers to indicate the IAB node associated with the authorization information. The IAB node-related identifiers must include at least one of the following: IAB-DU's gNB-DU ID, UE XnAP ID of IAB-MT in CU1, IAB-MT UE XnAP ID in CU2, and IAB-MT UE XnAP ID in CU3.

[0211] S1130:CU1 sends an inter-topology transfer request to CU3.

[0212] CU1, acting as an F1 termination CU, sends an IAB transport migration management request message to CU3, asking CU3 to help CU1 establish inter-topology traffic.

[0213] S1140:CU3 sends IAB authorization information to CU1.

[0214] Specifically, CU3 includes (mobile) IAB authorization information in the IAB transport migration management response or IAB transport migration management rejection message it sends back to CU1.

[0215] In possible implementations, the information transmitted from CU3 to CU1 directly carries (mobile) IAB authorization information elements, the values ​​of which include authorization or denial.

[0216] In another possible implementation, the information carries a (mobile) IAB authorization information element with a disauthorized value only if authorization is not granted. Alternatively, the information carries instruction information regarding releasing or not establishing an F1 connection.

[0217] In another implementation, if authorization is granted, the response is an IAB forwarding migration management response message; or, if authorization is not granted, the response is an IAB forwarding migration management rejection message.

[0218] In another implementation, if authorization is not granted, the Cause value carried in the IAB transfer migration management rejection message sent is instructional information regarding the denial of authorization for the IAB.

[0219] Optionally, the IAB authorization information may need to further carry IAB node-related identifiers to indicate the IAB node associated with the authorization information.

[0220] In addition to the continuous partial migration scenario shown in Figure 7, it should be understood that Method 3 may be further applicable to inter-CU partial migration, inter-CU RLF recovery, and inter-CU topology redundancy scenarios where the IAB-MT's Master Node (MN) is an F1 non-terminated (CU3). We assume that CU2 does not exist. In these scenarios, there are only two CUs, namely CU1 and CU3, and the IAB-MT migrates from CU1 to CU3. CU1 is not only the source CU of the IAB-MT, but also the F1-terminated CU of the IAB-DU.

[0221] In different scenarios, some of the steps S1110 through S1140 of Method 3 will differ.

[0222] In the case of a partial migration or RLF recovery scenario, there are different MT migration behaviors in step S1110. In the partial migration scenario, the MT is handed over from CU1 to CU3. In the RLF recovery scenario, the MT is experiencing a radio link failure at CU1. Therefore, the MT performs radio link failure recovery from CU1 to CU3 (the MT performs RLF recovery from CU1 to CU3).

[0223] In a topology redundancy scenario, with dual connectivity, the IAB-MT's RRC connection is anchored on the MN, so the IAB-MT's MN is limited to CU3 (SN is CU1). There is an RRC connection between SN and IAB-MT, but SN is used to forward RRC messages between MN and IAB-MT. AMF sends authorization information from IAB-MT to MN. Only if MN is CU3 does CU3 need to further notify the F1-terminated CU (i.e., CU1) of the authorization information. If MN was originally CU1 and CU1 is the F1-terminated CU, there is no technical problem.

[0224] In a topology redundancy scenario, step S1110 should be omitted. Both the MN and SN can determine which CU is the F1-terminating CU based on MN instructions, OAM instructions, and similar. In step S1120, the MN obtains the latest authorization information for the MT. Since no MT handover or RLF recovery occurs, there is no exchange of routing procedures between the CU and AMF. Therefore, authorization information is obtained only by using a UE context change request in this case.

[0225] Furthermore, regarding topology redundancy scenarios, this is also applicable to the IAB-MT EN-DC scenario. That is, the master node of the MT is the MeNB (LTE base station), the secondary node is the SgNB (NR base station), and the secondary node is the F1-terminating donor. In other words, CU1 is changed to a MeNB, CU3 is changed to a SgNB, and AMF is changed to an MME.

[0226] Method 4

[0227] Method 4 will be explained below using the continuous partial migration scenario shown in Figure 7 as an example. In Figure 7, CU1 is the F1 termination CU of the DU, CU2 is the source CU of the MT, and CU3 is the target CU of the MT. In Method 4, the IAB-DU notifies the F1 termination CU of the current IAB authorization information. Method 4 is applicable to partial migration, continuous partial migration, radio link failure recovery, and topology redundancy scenarios.

[0228] Figure 12 is a schematic flowchart of Method 4. The method in Figure 12 includes at least some of the following:

[0229] S1210: The manual transmission will be handed over from CU2 to CU3.

[0230] Specifically, prior to the migration, there is an RRC connection between IAB-MT and CU2, and an F1 interface between IAB-DU and CU1. During the partial migration, an interCU cell handover is performed for IAB-MT, and an RRC connection to CU3 is established. However, IAB-DU still maintains its F1 interface with CU1 and does not establish an F1 interface with CU3.

[0231] S1220:AMF transmits IAB authorization information to IAB-MT.

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

[0233] In possible implementations, the instruction information transmitted by the AMF to the IAB-MT directly carries the (mobile) IAB authorization information element, the value of which includes authorization or denial.

[0234] In another possible implementation, the information carries a (mobile) IAB authorization information element with a disauthorized value only if authorization is not granted. Alternatively, the instruction information carries instructions regarding releasing or not establishing an F1 connection.

[0235] Optionally, the IAB authorization information may need to further carry IAB node-related identifiers to indicate the IAB node associated with the authorization information. The IAB node-related identifiers must include at least one of the following: IAB-DU's gNB-DU ID, UE XnAP ID of IAB-MT in CU1, IAB-MT UE XnAP ID in CU2, and IAB-MT UE XnAP ID in CU3.

[0236] After the IAB-MT receives IAB authorization information, it notifies the IAB-DU of the authorization information via its internal interface.

[0237] S1230: IAB-DU transmits IAB authorization information to CU1.

[0238] In possible implementations, the IAB-DU sends F1AP information (e.g., GNB-DU CONFIGURATION UPDATE) to the CU1, carrying the authorization information for the (mobile) IAB.

[0239] Optionally, the IAB authorization information may need to further carry IAB node-related identifiers to indicate the IAB node associated with the authorization information.

[0240] With respect to methods 1, 2, and 4 described above, if the step of converting the MT's CU is removed, the method is applicable to scenarios where no change in IAB approval status occurs when the MT's CU is switched. In other words, whenever the MT's CU or the MT receives an IAB approval status, the MT's CU or the MT notifies the DU's CU.

[0241] Furthermore, methods 1 and 2 described above are also applicable to scenarios where the MT and DU are connected to two different CUs when the IAB first accesses the network. In this scenario, the F1 interface is not established, and the DU's CU cannot be notified by using F1 messages.

[0242] It should be understood that, in addition to the continuous partial migration scenario shown in Figure 7, Method 4 may be further applicable to inter-CU partial migration, inter-CU RLF recovery, and inter-CU topology redundancy scenarios where the IAB-MT's Master Node (MN) is non-F1-terminating (CU3). We assume that CU2 does not exist. In these scenarios, there are only two CUs, namely CU1 and CU3, and the IAB-MT migrates from CU1 to CU3. CU1 is not only the source CU of the IAB-MT, but also the F1-terminating CU of the IAB-DU.

[0243] In the case of a partial migration or RLF recovery scenario, there are different MT migration behaviors in step S1210. In the partial migration scenario, the MT is handed over from CU1 to CU3. In the RLF recovery scenario, the MT is experiencing a radio link failure at CU1. Therefore, the MT performs radio link failure recovery from CU1 to CU3 (the MT performs RLF recovery from CU1 to CU3).

[0244] In a topology redundancy scenario, with dual connectivity, the IAB-MT's RRC connection is anchored on the MN, so the IAB-MT's MN is limited to CU3 (SN is CU1). There is an RRC connection between SN and IAB-MT, but SN is used to forward RRC messages between MN and IAB-MT. AMF sends authorization information from IAB-MT to MN. Only if MN is CU3 does CU3 need to further notify the F1-terminated CU (i.e., CU1) of the authorization information. If MN was originally CU1 and CU1 is the F1-terminated CU, there is no technical problem.

[0245] Method 5

[0246] In Method 5, the MT's CU notifies the AMF of the DU's CU (for example, CU1 in Figure 7), and as a result, the AMF directly notifies the DU's CU whenever the IAB accreditation status is updated.

[0247] Figure 13 is a schematic flowchart 1300 of Method 5. The method in Figure 13 includes at least some of the following:

[0248] S1310: Optionally, IAM-MT sends the IAB-DU's gNB-DU ID to CU3 and notifies CU1 of DUs for which F1 interface establishment is rejected.

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

[0250] S1330: AMF transmits IAB authorization information to CU1.

[0251] In possible implementations, the AMF further transmits the gNB-DU ID from the IAB-DU and / or the UE NGAP ID from the IAB-MT to the CU1.

[0252] According to methods 1 to 5 described above, signaling exchange between CUs and between CUs and IAB nodes is introduced. As a result, if the CU of an IAB-MT differs from the CU of an IAB-DU, the CU of the DU can obtain the current authorization information of the IAB-MT (sometimes called the current authorization information of the IAB node) through its signaling exchange.

[0253] The methods described above explain how communication is performed when the IAB-MT CU differs from the IAB-DU CU in partial migration, sequential partial migration, wireless link failure recovery, and topology redundancy scenarios.

[0254] In a DU migration scenario, the CU (Communication Unit) of the IAB-MT may differ from that of the IAB-DU. To illustrate some of the communication methods 6, 7, and 8 in this scenario, we will use the DU migration shown in Figure 8 as an example.

[0255] Method 6

[0256] Method 6 will now be explained using the DU migration scenario shown in Figure 8 as an example. In Figure 8, CU1 is the source F1 termination CU, CU2 is the MT's CU, and CU3 is the target F1 termination CU. In Method 6, the source F1 termination CU notifies the target F1 termination CU of the current IAB authorization information.

[0257] Figure 14 is a schematic flowchart 1400 of Method 6. The method in Figure 14 includes at least some of the following:

[0258] S1410:CU1 sends IAB authorization information to CU3.

[0259] Specifically, CU1 sends a message to CU3 carrying IAB authorization information and / or mobile IAB authorization information.

[0260] In possible implementations, the instruction information sent by CU1 to CU3 directly carries (mobile) IAB authorization information elements, including an authorization or denial value.

[0261] In another possible implementation, the information carries a (mobile) IAB authorization information element with a disauthorized value only if authorization is not granted. Alternatively, the instruction information carries instructions regarding releasing or not establishing an F1 connection.

[0262] In possible implementations, the message may be one used by CU1 to request the migration of IAB-DU to CU3. For example, the message name may be a DU Migration Request message.

[0263] Optionally, the IAB authorization information may need to further carry IAB node-related identifiers to indicate the IAB node associated with the authorization information. The IAB node-related identifiers must include at least one of the following: IAB-DU's gNB-DU ID, UE XnAP ID of IAB-MT in CU1, IAB-MT UE XnAP ID in CU2, and IAB-MT UE XnAP ID in CU3.

[0264] Method 7

[0265] Method 7 will be explained below using the DU migration scenario shown in Figure 8 as an example. In Figure 8, CU1 is the source F1 termination CU, CU2 is the MT's CU, and CU3 is the target F1 termination CU. In this method, the IAB-DU notifies the target F1 termination CU of the current IAB authorization information.

[0266] Figure 15 is a schematic flowchart of Method 7. The method in Figure 15 includes at least some of the following:

[0267] S1510: IAB-DU obtains IAB accreditation information.

[0268] In this step, the IAB-DU can obtain IAB authorization information from different network elements.

[0269] For example, CU1 triggers DU migration by sending an F1 message to the IAB-DU (the logical DU associated with CU1, IAB-DU1 in Figure 8). The F1 message carries IAB authorization information.

[0270] In possible implementations, the IAB authorization information also carries the CU3 identifier (gNB ID and / or IP address).

[0271] In another example, the AMF / CU2 sends an RRC message to the IAB-MT, which carries (mobile) IAB authorization information, and the IAB-MT notifies the IAB-DU of the authorization information via an internal interface.

[0272] In a possible implementation, the F1 message sent by CU1 to the IAB-DU or the RRC message sent by the AMF / CU2 to the IAB-MT directly carries a (mobile) IAB authorization information element containing an authorization or non-authorization value.

[0273] In another possible implementation, the F1 message or the RRC message carries a (mobile) IAB authorization information element with a non-authorization value only when authorization is not granted. Alternatively, indication information regarding releasing the F1 connection or not establishing the F1 connection is carried.

[0274] S1520: The IAB-DU (logical DU associated with CU3, IAB-DU2 in FIG. 8) sends IAB authorization information to CU3.

[0275] Optionally, the IAB authorization information needs to further carry an IAB node-related identifier to indicate the IAB node associated with the authorization information. The IAB node-related identifier includes at least one of the following: The gNB-DU ID of the IAB-DU, The UE XnAP ID of the IAB-MT in CU1, The UE XnAP ID of the IAB-MT in CU2, and The UE XnAP ID of the IAB-MT in CU3.

[0276] Method 8

[0277] Hereinafter, Method 8 will be described by taking the DU migration scenario shown in FIG. 8 as an example. In FIG. 8, CU1 is the source F1 terminating CU, CU2 is the CU of the MT, and CU3 is the target F1 terminating CU. In this method, the CU of the MT notifies the target F1 terminating CU of the current IAB authorization information.

[0278] FIG. 16 is a schematic flowchart 1600 of Method 8. The method in FIG. 16 includes at least a part of the following content.

[0279] The possible implementations are as follows:

[0280] S1610:CU3 sends an inter-topology transfer request message, i.e., an IAB transfer migration management request, to CU2 to request the establishment of an F1 interface data transmission that passes through the CU2 topology and terminates on CU3.

[0281] S1620:CU2 includes (mobile) IAB authorization information in the IAB transfer migration management response or IAB transfer migration management rejection message that replies to CU3.

[0282] Specifically, CU2 includes (mobile) IAB authorization information in the IAB transfer migration management response or IAB transfer migration management rejection message that replies to CU3.

[0283] Optionally, the information transmitted by CU3 to CU1 directly carries (mobile) IAB authorization information elements, including authorized or unauthorized values.

[0284] Optionally, if authorization is not granted, the information carries an (mobile) IAB authorization information element with a disauthorized value. Alternatively, the information carries instructions regarding releasing or not establishing an F1 connection.

[0285] Optionally, if authorization is granted, the response is an IAB transfer migration management response message; or, if authorization is not granted, the response is an IAB transfer migration management rejection message.

[0286] Optionally, if authorization is not granted, the Cause value carried in the IAB Transfer Migration Management Rejection Message sent will be instructional information regarding the denial of authorization for the IAB.

[0287] Another possible implementation is as follows:

[0288] S1610:CU1 sends the identifier of CU3 (gNB ID and / or IP address) to CU2 to notify CU2 that the DU should be migrated to CU3, or to request CU2 to configure resources for F1 interface transmission on CU3.

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

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

[0291] Optionally, the instruction information transmitted by CU3 to CU2 directly carries (mobile) IAB authorization information elements, including authorized or unauthorized values.

[0292] Optionally, if authorization is not granted, the instruction information will carry an (mobile) IAB authorization information element with a value indicating non-authorization. Alternatively, the instruction information will carry instructions regarding releasing or not establishing an F1 connection.

[0293] Optionally, the IAB authorization information may need to further carry IAB node-related identifiers to indicate the IAB node associated with the authorization information. The IAB node-related identifiers must include at least one of the following: IAB-DU's gNB-DU ID, UE XnAP ID of IAB-MT in CU1, IAB-MT UE XnAP ID in CU2, and IAB-MT UE XnAP ID in CU3.

[0294] FIG. 17 is a block diagram of a communication device 1700 according to an embodiment of the present application. The device 1700 includes a transceiver unit 1710 and a processing unit 1720. The transceiver unit 1710 is capable of communicating with the outside, and the processing unit 1720 is configured to process data. The transceiver unit 1710 may also be referred to as a communication interface or a communication unit.

[0295] In a possible implementation, the device 1700 may further include a memory unit. The memory unit may be configured to store instructions and / or data. The processing unit 1720 is capable of reading the instructions and / or data in the memory unit.

[0296] The device 1700 may be configured to perform the operations executed by the donor node in the embodiment of the method described above. In this case, the device 1700 may be the first donor node, the second donor node, the third donor node, the fourth donor node, or a component that can be constructed within the first donor node, the second donor node, the third donor node, or the fourth donor node. The transceiver unit 1710 is configured to perform the reception / transmission related operations of the first donor node, the second donor node, the third donor node, or the fourth donor node in the embodiment of the method described above. The processing unit 1720 is configured to perform the processing related operations of the first donor node, the second donor node, the third donor node, or the fourth donor node in the embodiment of the method described above.

[0297] Alternatively, the device 1700 may be configured to perform operations performed by the IAB node in the embodiments of the method described above. In this case, the device 1700 may be an IAB node or a component that can be built within an IAB node. The transceiver unit 1710 is configured to perform the receive / transmit related operations on the IAB node side in the embodiments of the method described above. The processing unit 1720 is configured to perform the processing related operations on the IAB node side in the embodiments of the method described above.

[0298] Alternatively, the device 1700 may be configured to perform operations performed by the AMF in the embodiments of the method described above. In this case, the device 1700 may be the AMF or a component that can be built into the AMF. The transceiver unit 1710 is configured to perform the receive / transmit related operations on the AMF side in the embodiments of the method described above. The processing unit 1720 is configured to perform the processing related operations on the AMF side in the embodiments of the method described above.

[0299] It should be further understood that the apparatus 1700 in this invention is embodied in the form of a functional unit. The term “unit” in this invention may include an application-specific integrated circuit (ASIC), an electronic circuit, a processor configured to run one or more software or firmware programs (e.g., a shared processor, a dedicated processor, a group processor, or similar), storage, a combinational logic circuit, and / or other suitable components that support the functions described above. In an optional example, a person skilled in the art will understand that the apparatus 1700 may specifically be the first donor node, second donor node, third donor node, fourth donor node, IAB node, or AMF in the embodiments described above, and may be configured to perform the procedures and / or steps corresponding to the first donor node, second donor node, third donor node, fourth donor node, IAB node, or AMF in the embodiments of the methods described above. Alternatively, the apparatus 1700 may specifically be the first donor node, second donor node, third donor node, fourth donor node, IAB node, or AMF in the embodiments described above, and may be configured to perform the procedures and / or steps corresponding to the first donor node, second donor node, third donor node, fourth donor node, IAB node, or AMF in the embodiments of the methods described above. Details are not described here to avoid repetition.

[0300] The apparatus 1700 in the aforementioned solution has the function of performing the corresponding steps performed by the first donor node, second donor node, third donor node, fourth donor node, IAB node, or AMF in the aforementioned method. The function may be performed by hardware, or by hardware by running corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned function. For example, a transceiver unit may be replaced with a transceiver (for example, a transmitting unit in a transceiver unit may be replaced with a transmitter, and a receiving unit in a transceiver unit may be replaced with a receiver), and another unit, for example, a processing unit, may be replaced with a processor to separately perform the receive / transmit operations and associated processing operations in the embodiment of the method.

[0301] Alternatively, the transceiver unit 1710 may be a transceiver circuit (for example, including a receiver circuit and a transmitter circuit), and the processing unit may be a processing circuit.

[0302] It should be noted that the apparatus in Figure 17 may be a network element or device in the embodiments described above, or it may be a chip or chip system, such as a system on a chip (SoC). The transceiver unit may be an input / output circuit or a communication interface. The processing unit is a processor, microprocessor, or integrated circuit on a chip, but is not limited to this.

[0303] As shown in Figure 18, embodiments of the present application further provide a communication device 1800, which includes a processor 1810. The processor 1810 is coupled to a storage 1820, which is configured to store computer programs or instructions and / or data. The processor 1810 is configured to execute computer programs or instructions and / or data stored in the storage 1820 to perform the method in the embodiments of the method described above.

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

[0305] In possible implementations, the communication device 1800 may further include storage 1820, as shown in Figure 18.

[0306] In a possible implementation, the communication device 1800 includes one or more storage devices 1820.

[0307] In possible implementations, the storage 1820 and the processor 1810 may be integrated together, or they may be located separately, or the storage 1820 may be located outside the communication device 1800.

[0308] In possible implementations, the wireless communication device 1800 may further include a transceiver 1830, as shown in Figure 18. The transceiver 1830 is configured to receive and / or transmit signals. For example, the processor 1810 is configured to control the transceiver 1830 to receive and / or transmit signals.

[0309] In the solution, the communication device 1800 is configured to perform the operations performed by the donor node in the embodiment of the method described above.

[0310] For example, the processor 1810 is configured to perform processing-related operations performed by the donor node in the embodiment of the method described above, and the transceiver 1830 is configured to perform receiving / transmitting-related operations performed by the donor node in the embodiment of the method described above.

[0311] In another solution, the communication device 1800 is configured to perform the operations performed by the IAB node in the embodiment of the method described above.

[0312] For example, the processor 1810 is configured to perform processing-related operations performed by the IAB node in the embodiment of the method described above, and the transceiver 1830 is configured to perform receiving / transmitting-related operations performed by the IAB node in the embodiment of the method described above.

[0313] In yet another solution, the communication device 1800 is configured to perform the operations performed by the AMF in the embodiments of the method described above.

[0314] For example, the processor 1810 is configured to perform processing-related operations performed by the AMF in the embodiment of the method described above, and the transceiver 1830 is configured to perform receiving / transmitting-related operations performed by the AMF in the embodiment of the method described above.

[0315] As shown in Figure 19, the embodiments of the present application provide a chip system 1900, which may also be called a processing system, comprising a logic circuit 1910 and an input / output interface 1920.

[0316] The logic circuit 1910 may be a processing circuit within the chip system 1900. The logic circuit 1910 is coupled to and connected to a memory unit and is capable of calling instructions within the memory unit, thereby enabling the chip system 1900 to implement the methods and functions of the embodiments of this application. The input / output interface 1920 may be an input / output circuit within the chip system 1900, which outputs information processed by the chip system 1900 or inputs data or signaling information to be processed into the chip system 1900 for processing.

[0317] In the solution, the chip system 1900 is configured to perform the operations performed by the first donor node, second donor node, third donor node, fourth donor node, IAB node, or AMF in the embodiments of the method described above.

[0318] For example, the logic circuit 1910 is configured to perform processing-related operations performed by the first donor node in the embodiment of the method described above, and the input / output interface 1920 is configured to perform transmission and / or reception-related operations performed by the first donor node in the embodiment of the method described above.

[0319] Embodiments of the present application further provide a computer-readable storage medium for storing computer instructions for carrying out the methods performed by a terminal device or by a satellite in the embodiments of the methods described above.

[0320] For example, when a computer program is executed by a computer, the computer can implement the methods described in the embodiments of the above-described methods, such as the method executed by a donor node, the method executed by an IAB node, or the method executed by an AMF.

[0321] Embodiments of the present application further provide a computer program product including instructions. When the instructions are executed by a computer, the computer can implement the methods described in the embodiments of the above-described methods, which are executed by a donor node, an IAB node, or an AMF.

[0322] Embodiments of the present application further provide a communication system, which includes one or more of the first donor node, second donor node, third donor node, fourth donor node, IAB node, and AMF in the embodiments described above.

[0323] For a description of the relevant aspects and beneficial effects of any wireless communication device provided above, please refer to the corresponding embodiment of the method provided above. Further details are not provided here.

[0324] In embodiments of this application, a terminal device or network device may include a hardware layer, an operating system layer operating on the hardware layer, and an application layer operating on the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system in the operating system layer may be any one or more computer operating systems that perform service processing by using processes, such as the Linux operating system, Unix operating system, Android operating system, iOS operating system, Windows operating system, or similar. The application layer may include applications such as a browser, a contacts application, text processing software, and instant messaging software.

[0325] The specific structure of the implementer of the method provided in the embodiments of this application is not particularly limited in the embodiments of this application, provided that communication can be performed in accordance with the method provided in the embodiments of this application by executing a program that records the code of the method provided in the embodiments of this application. For example, the implementer of the method provided in the embodiments of this application may be a terminal device or a satellite, or a functional module located within a terminal device or satellite that is capable of calling and executing a program.

[0326] The embodiments or features of the present application may be implemented as methods, apparatus, or products using standard programming and / or engineering techniques. The term “product” as used in this specification may cover computer programs that can be accessed from any computer-readable component, carrier, or medium. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disk drives, floppy disks, magnetic tapes, or similar), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), or similar), smart cards, and flash memory (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, key drives, or similar).

[0327] The various storage media described in this specification may represent one or more devices and / or other machine-readable media configured to store information. The term “machine-readable media” may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0328] It should be understood that the processor in the embodiments of this application may be a central processing unit (CPU), or another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or another programmable logic device, discrete gate or transistor logic device, discrete hardware component, or the like. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like.

[0329] It should be further understood that the storage in the embodiments of this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM). For example, RAM may be used as an external cache. As an example, rather than an exhaustive list, RAM may include several forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus random access memory (direct rambus RAM, DR RAM).

[0330] It should be noted that if the processor is a general-purpose processor, DSP, ASIC, FPGA, or another programmable logic device, discrete gate or transistor logic device, or discrete hardware component, storage (storage module) may be integrated into the processor.

[0331] Furthermore, it should be noted that the storage described in this specification is intended to include, but is not limited to, these storages and any other storage of a suitable type.

[0332] Those skilled in the art will notice that the exemplary units and algorithmic steps described with reference to the embodiments disclosed in this specification can be implemented by electronic hardware or by a combination of computer software and electronic hardware. Whether the functions are performed by hardware or by software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but this should not be interpreted as going beyond the scope of the embodiments of this application.

[0333] For the sake of convenient and concise explanation, it will be readily apparent to those skilled in the art that detailed operating processes of the systems, devices, and units described above should be referred to the corresponding processes in the embodiments of the methods described above. Further details are not provided here.

[0334] In some embodiments provided in the present application, it should be understood that the disclosed systems, apparatus, and methods may be implemented in other ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into units is merely a logical functional division, and other divisions may be used in actual implementations. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not performed. Furthermore, the mutual coupling, direct coupling, or communication connection shown or described may be implemented through some interface. Indirect coupling or communication connection between apparatus or units may be implemented electronically, mechanically, or in other forms.

[0335] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected based on the actual requirements to achieve the objectives of the solution in the embodiment.

[0336] Furthermore, the functional units in the embodiments of this application may be integrated into a single processing unit, and each unit may exist physically independently, or two or more units may be integrated into a single unit.

[0337] When a function is implemented in the form of a software function unit and sold or used as a standalone product, the function may be stored on a computer-readable storage medium. Based on such understanding, the technical solutions in the embodiments of this application, or any part of the technical solutions that contribute to the prior art, may be implemented in the form of a software product. A computer software product is stored on a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, server, network device, or similar) to perform all or part of the steps in the method described in the embodiments of this application. The storage medium includes any medium capable of storing program code, such as a USB flash drive, removable hard disk drive, read-only memory (ROM), random access memory (RAM), magnetic disk, optical disk, or similar.

[0338] The foregoing description is merely a specific implementation of the present application and is not intended to limit the scope of protection of the present application. Any modifications or substitutions readily conceived by a person skilled in the art within the scope of the technical scope disclosed in the embodiments of the present application shall fall within the scope of protection of the present application. That is, the scope of protection of the present application shall be subject to the scope of protection of the claims.

Claims

1. It is a method of communication: Steps include: a first donor node receiving integrated access backhaul IAB authorization information, the IAB authorization information indicating the authorization status of the first IAB node, the first IAB node comprising a first distributed unit and a first mobile terminal, the first mobile terminal having an RRC connection to a second donor node, and the first distributed unit attempting to establish an F1 connection to the first donor node or having an F1 connection, and being a different donor node from the first donor node and the second donor node; and The first donor node determines, based on the IAB authorization information, whether the first IAB node is authorized to respond to the user equipment UE; A method that includes this.

2. It is a method of communication: The step is that a second donor node transmits integrated access backhaul IAB authorization information to a first donor node, the IAB authorization information indicating the authorization status of the first IAB node, the first IAB node comprising a first distributed unit and a first mobile terminal, the first mobile terminal having an RRC connection to the second donor node, and the first distributed unit attempting to establish an F1 connection to the first donor node or having an F1 connection; A method that includes this.

3. In the method according to claim 2, before the second donor node transmits the IAB authorization information to the first donor node, the method: The second donor node receives the IAB authorization information from the Access Mobility Management Function Unit (AMF) within the core network; A method that further includes this.

4. In the method according to claim 2 or 3, before the second donor node transmits the IAB authorization information to the first donor node, the method: The step of the second donor node receiving identification information of the first donor node from a third donor node, wherein the third donor node is a donor node that had an RRC connection to the first mobile terminal before the first mobile terminal established an RRC connection to the second donor node; A method that includes this.

5. The method according to claim 4, the step of the second donor node transmitting integrated access backhaul IAB authorization information to the first donor node is: A method comprising the step of the second donor node transmitting the integrated access backhaul IAB authorization information to the first donor node based on the identification information of the first donor node.

6. It is a method of communication: The third donor node transmits integrated access backhaul IAB authorization information to the first donor node, wherein the IAB authorization information indicates the authorization status of the first IAB node, the first IAB node comprises a first distributed unit and a first mobile terminal, the first mobile terminal has an RRC connection to a second donor node, the third donor node is a donor node that had an RRC connection to the first mobile terminal before the first mobile terminal established an RRC connection to the second donor node, and the first distributed unit is attempting to establish an F1 connection to the first donor node or has an F1 connection; A method that includes this.

7. In the method according to claim 6, before the third donor node transmits the IAB authorization information to the first donor node, the method: The third donor node receives the IAB authorization information from the second donor node; A method that includes this.

8. It is a method of communication: The first integrated access backhaul IAB node transmits IAB authorization information to a first donor node, wherein the IAB authorization information indicates the authorization status of the first IAB node, the first IAB node includes a first distributed unit and a first mobile terminal, the first mobile terminal has an RRC connection to a second donor node, and the first distributed unit has an F1 connection to the first donor node; A method that includes this.

9. In the method according to claim 8, before the IAB node transmits the IAB authorization information to the first donor node, the method: The first IAB node receives the IAB authorization information from the Access Mobility Management Function Unit (AMF) within the core network; A step in which the first IAB node receives the IAB authorization information from a fourth donor node, wherein the fourth donor node is a donor node that had an F1 connection to the first distributed unit before the first distributed unit established an F1 connection to the first donor node; or The first IAB node receives the IAB authorization information from the second donor node; A method that includes this.

10. It is a method of communication: Steps include: an Access Mobility Management Function Unit (AMF) within the core network transmitting integrated access backhaul IAB authorization information to a first donor node, wherein the IAB authorization information indicates the authorization status of the first integrated access backhaul IAB node, the first IAB node includes a first distributed unit and a first mobile terminal, the first mobile terminal has an RRC connection to a second donor node, and the first distributed unit is attempting to establish an F1 connection to the first donor node or has an F1 connection, and is a different donor node from the first donor node and the second donor node; A method that includes this.

11. In the method according to claim 10, before the AMF transmits the IAB authorization information to the first donor node, the method: The AMF receives identification information of the first donor node transmitted by the first IAB node or the second donor node; A method that further includes this.

12. The method according to claim 11, the step of the AMF transmitting IAB authorization information to the first donor node is: The AMF transmits the IAB authorization information to the first donor node based on the identification information of the first donor node; Methods that include...

13. It is a method of communication: The step is that a fourth donor node transmits integrated access backhaul IAB authorization information to a first donor node, the IAB authorization information indicating the authorization status of the first IAB node, the first IAB node comprising a first distributed unit and a first mobile terminal, the first distributed unit comprising a first logical distributed unit and a second logical distributed unit, the first mobile terminal having an RRC connection to the second donor node, the first logical distributed unit having an F1 connection to the fourth donor node, and the second logical distributed unit attempting to establish an F1 connection to the first donor node or having an F1 connection; A method that includes this.

14. It is a method of communication: The first integrated access backhaul IAB node transmits the identification information of a first donor node to the access mobility management function unit (AMF) in the core network, wherein the first IAB node includes a first distributed unit and a first mobile terminal, the first mobile terminal has an RRC connection to a second donor node, the first distributed unit is attempting to establish an F1 connection to the first donor node or has an F1 connection, and the AMF is configured to transmit IAB authorization information to the first donor node based on the identification information of the first donor node, the IAB authorization information indicates the authorization status of the first IAB node; A method that includes this.

15. It is a method of communication: The step is that a second donor node transmits the identification information of a first donor node to the Access Mobility Management Function Unit (AMF) in the core network, wherein the second donor node has an RRC connection to a first mobile terminal, the first mobile terminal is a mobile terminal in a first integrated access backhaul IAB node, the first IAB node further includes a first distributed unit, the first distributed unit is attempting to establish an F1 connection to the first donor node or has an F1 connection, the AMF is configured to transmit IAB authorization information to the first donor node based on the identification information of the first donor node, the IAB authorization information indicates the authorization status of the first IAB node; A method that includes this.

16. A communication device that is a donor node attempting to establish an F1 connection to a first distributed unit or that has an F1 connection: A receiving module configured to receive integrated access backhaul IAB authorization information, wherein the IAB authorization information indicates the authorization status of a first IAB node, the first IAB node comprises the first distributed unit and a first mobile terminal, the first mobile terminal has an RRC connection to a second donor node, and is a different donor node from the device and the second donor node; and Based on the aforementioned IAB authorization information, the first IAB node is configured to have a processing module that determines whether it is authorized to respond to a user device; A device that includes this.

17. A communication device which is a donor node having an RRC connection to a first mobile terminal: A transmitting module configured to transmit integrated access backhaul IAB authorization information to a first donor node, wherein the IAB authorization information indicates the authorization status of the first IAB node, the first IAB node comprises a first distributed unit and a first mobile terminal, and the first distributed unit is attempting to establish an F1 connection to the first donor node or has an F1 connection; A device that includes this.

18. In the apparatus according to claim 17: A receiving module configured to receive the IAB authorization information from the Access Mobility Management Function Unit (AMF) within the core network; A device that further includes the following.

19. A communication device that has an RRC connection to a first mobile terminal, which is a donor node that the first mobile terminal had before establishing an RRC connection to a second donor node: A transmitting module configured to transmit integrated access backhaul IAB authorization information to a first donor node, wherein the IAB authorization information indicates the authorization status of the first IAB node, the first IAB node comprises a first distributed unit and a first mobile terminal, the first mobile terminal has an RRC connection to a second donor node, and the first distributed unit is attempting to establish or has an F1 connection to the first donor node; A device that includes this.

20. In the apparatus according to claim 19: A receiving module configured to receive the IAB authorization information from the second donor node; A device that further includes the following.

21. A communication device that is an integrated access backhaul IAB node: A transmitting module configured to transmit IAB authorization information to a first donor node, wherein the IAB authorization information indicates the authorization status of the device, the device includes a first distributed unit and a first mobile terminal, the first mobile terminal has an RRC connection to a second donor node, and the first distributed unit is A transmitting module that is attempting to establish an F1 connection to the first donor node, or that has an F1 connection; A device that includes this.

22. A receiving module configured to receive IAB authorization information from the Access Mobility Management Function Unit (AMF), a fourth donor node, or a second donor node within the core network, wherein the fourth donor node is a donor node that had an F1 connection to the first distributed unit before the first distributed unit established an F1 connection to the first donor node; A device that includes this.

23. A communication device that is an Access Mobility Management Function Unit (AMF) within the core network and corresponds to an Integrated Access Backhaul (IAB) node: A transmitting module configured to transmit IAB authorization information to a first donor node, wherein the IAB authorization information indicates the authorization status of a first integrated access backhaul IAB node, the first IAB node comprises a first distributed unit and a first mobile terminal, the first mobile terminal has an RRC connection to a second donor node, and the first distributed unit is attempting to establish an F1 connection to the first donor node or has an F1 connection, and is a different donor node from the first donor node and the second donor node; A device that includes this.

24. A device that is a donor node having an F1 connection to the first logical distributed unit, and: A transmitting module configured to transmit integrated access backhaul IAB authorization information to a first donor node, wherein the IAB authorization information indicates 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, the first mobile terminal has an RRC connection to the second donor node, and the second logical distributed unit is attempting to establish an F1 connection to the first donor node or has an F1 connection; A device that includes this.

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

26. A computer program product that includes computer program code, wherein when the computer program code is executed, the device The method according to claim 1, The method according to any one of claims 2 to 5, The method according to claim 6 or 7, The method according to claim 8 or 9, The method according to any one of claims 10 to 12, The method according to claim 13, The method according to claim 14, or A computer program product that enables the execution of the method described in claim 15.

27. A computer-readable storage medium for storing a computer program, wherein when the computer program is executed, The apparatus will be able to perform the method described in claim 1. The apparatus will be capable of performing the method described in any one of claims 2 to 5. The apparatus becomes capable of performing the method described in claim 6 or 7. The apparatus becomes capable of performing the method described in claim 8 or 9. The apparatus will be capable of performing the method described in any one of claims 10 to 12. The apparatus will be able to perform the method described in claim 13. The apparatus becomes capable of performing the method described in claim 14, or A storage medium that enables the device to perform the method described in claim 15.

28. A chip system including a processor, wherein the processor is configured to: launch a computer program from storage and execute the computer program, A communication device incorporating the aforementioned chip system becomes capable of performing the method described in claim 1. A communication device incorporating the aforementioned chip system becomes capable of performing the method described in any one of claims 2 to 5. A communication device incorporating the aforementioned chip system becomes capable of performing the method described in claim 6 or 7. A communication device incorporating the aforementioned chip system becomes capable of performing the method described in claim 8 or 9. A communication device incorporating the aforementioned chip system becomes capable of performing the method described in any one of claims 10 to 12. A communication device incorporating the aforementioned chip system becomes capable of performing the method described in claim 13. A communication device incorporating the aforementioned chip system becomes capable of performing the method described in claim 14, or A communication device having the chip system introduced is a chip system that enables the method described in claim 15 to be carried out.

29. A communication system comprising at least one of the following: a first donor node, a second donor node, a third donor node, a fourth donor node, a first IAB node, and an AMF, The first donor node is configured to perform the method described in claim 1, The second donor node is configured to perform the method described in any one of claims 2 to 5 and 15, The first IAB node is configured to perform the method described in claim 8, 9, or 14, The AMF is configured to perform the method described in any one of claims 1 to 12, The third donor node is configured to perform the method described in claim 6 or 7, and The communication system wherein the fourth donor node is configured to perform the method described in claim 13.

Images