WO2025228175A1 - Communication method and apparatus - Google Patents

Abstract

The present application relates to the field of communications. Provided are a communication method and apparatus, which are capable of reducing signaling overheads for indicating configuration information. The method comprises: receiving first indication information, and performing communication on the basis of a first group of configuration information, wherein the first indication information indicates a plurality of groups of configuration information, trigger conditions of the plurality of groups of configuration information are different, and the plurality of groups of configuration information comprise the first group of configuration information.

Description

Communication methods and devices

This application claims priority to Chinese Patent Application No. 202410537870.6, filed with the State Intellectual Property Office of China on April 29, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference.

Technical Field

This application relates to the field of communications, and more particularly to communication methods and apparatus.

Background Technology

^Fifth -generation (5G) mobile communication systems impose stringent requirements on various network performance indicators. To meet the performance requirements of 5G systems, a large number of small cells need to be deployed densely, and network coverage needs to be provided for remote areas. However, providing fiber optic backhaul in both scenarios is costly and difficult to implement. Therefore, the cost-effective and convenient integrated access and backhaul (IAB) technology has emerged.

In IAB technology, the access link (AL) and backhaul link (BH) adopt wireless transmission schemes, reducing fiber optic deployment and thus meeting the current network requirements for performance indicators such as ultra-high capacity, wider coverage, ultra-high reliability, and ultra-low latency. Specifically, when an IAB node provides services to a user equipment (UE), it can be considered an IAB distributed unit (IAB-DU); or, when an IAB node faces its parent node (such as an IAB donor node), it can also act as an IAB mobile termination (IAB-MT).

In mobile IAB (mIAB) scenarios, IAB-DUs will frequently switch the host nodes they access, which will cause frequent release and updates of IAB-DU configuration information, increasing the signaling overhead of instructing IAB-DU configuration information.

Summary of the Invention

This application provides a communication method and apparatus that can reduce the signaling overhead of indicating configuration information.

Firstly, a communication method is provided, which can be executed by a first node, wherein the first node can be a device, component (e.g., processor, circuit, chip, or chip system), logic module, or software that implements some or all of the functions of the first node. The method includes: receiving first indication information, the first indication information indicating multiple sets of configuration information, the multiple sets of configuration information having different triggering conditions; and performing communication based on the first set of configuration information, the multiple sets of configuration information including the first set of configuration information.

Based on this scheme, the integrated IAB distributed unit DU (IAB-DU, i.e., the first node) receives multiple sets of configuration information with different trigger conditions configured by its host node (i.e., multiple sets of configuration information indicated by the host node through the first indication information); thus, it can communicate based on one set of configuration information (i.e., the first set of configuration information).

For example, the triggering conditions corresponding to multiple sets of configuration information can be related to the time when the first node reconnects to the network after connecting to the host node (such as reconnecting to the host node or a new host node, or switching to another host node). Therefore, different configuration information will be triggered during each reconnection process of the first node. This ensures that each time the first node reconnects to the network after connecting to the host node, one set of configuration information is in effect, allowing the first node to communicate using this set of configuration information. Compared to the scheme where the first node reacquires configuration information each time it connects to the network, this reduces the signaling overhead of instructing the configuration information.

In one possible design, receiving the first indication information includes: receiving the first indication information from a second node, which is located on the host node, or the second node is located on a descendant node of the host node.

In one possible design, the configuration information indicates the triggering conditions, and communication is performed based on the first set of configuration information, including: when the triggering conditions corresponding to the first set of configuration information are met, communication is performed based on the first set of configuration information.

In one possible design, the first set of configuration information is communicated, including: communicating based on the first set of configuration information at a first moment; the communication method further includes: communicating based on the second set of configuration information at a second moment, wherein the multiple sets of configuration information include the second set of configuration information, and the second moment is after the first moment.

Based on the two possible designs described above, different groups of configuration information are triggered when their corresponding triggering conditions are met (e.g., the first group of configuration information is triggered when its corresponding triggering conditions are met). For example, the triggering conditions can be time-related; therefore, it can be considered that different groups of configuration information are triggered at different times. Since the host node sends down multiple groups of configuration information at once, the first node can communicate using different configuration information at different times. Compared to the scheme where the first node indicates each configuration information separately, this reduces the signaling overhead of indicating configuration information.

In one possible design, the communication method further includes sending a second indication message that indicates the capability information of the first node.

Based on this possible design, the first node can report its capability information to the host node, enabling the host node or core network to configure appropriate configuration information for the first node based on this capability information; such as configuring appropriate handover methods and access resources for the first node, thereby improving the effectiveness of mobility management.

Secondly, a communication method is provided, which can be executed by a second node, wherein the first node can be a device, component (e.g., processor, circuit, chip, or chip system), logic module, or software that implements some or all of the functions of the first node. The method includes: determining first indication information, the first indication information indicating multiple sets of configuration information, the multiple sets of configuration information having different triggering conditions; and sending the first indication information.

Based on this scheme, the host node or its descendant node (i.e., the second node) can configure multiple sets of configuration information with different trigger conditions for the first node (i.e., multiple sets of configuration information indicated by the host node through the first indication information); thus, the first node can communicate based on one set of configuration information (i.e., the first set of configuration information).

For example, the triggering conditions corresponding to multiple sets of configuration information can be related to the time when the first node reconnects to the network after connecting to the host node (such as reconnecting to the host node or a new host node, or switching to another host node). Therefore, different configuration information will be triggered during each reconnection process of the first node. This ensures that each time the first node reconnects to the network after connecting to the host node, one set of configuration information is in effect, allowing the first node to communicate using this set of configuration information. Compared to the scheme where the first node reacquires configuration information each time it connects to the network, this reduces the signaling overhead of instructing the configuration information.

In one possible design, determining the first indication information includes: receiving first indication information from the parent node of the second node, wherein the parent node of the second node is located on the host node, or the parent node of the second node is a descendant node of the host node.

In one possible design, the communication method further includes receiving second indication information, which indicates the capability information of the first node.

The technical effects of any possible design in the second aspect can be referenced to the technical effects of the corresponding design in the first aspect, and will not be elaborated here.

In conjunction with the first or second aspect, the following possible designs also include:

In some possible designs, the capability information of the first node includes at least one of the following: the type of the first node, which is either a non-ground node or a ground node; ground nodes include stationary nodes or mobile nodes; non-ground nodes include stationary nodes or mobile nodes; whether the IAB node to which the first node belongs supports serving child nodes; whether the MT in the first node and the IAB node to which the first node belongs supports simultaneous switching; and whether the IAB node to which the first node belongs supports having the functions of both an IAB node and a host node.

Based on this possible design, the first node can report its capability information to the host node, enabling the host node or core network to configure appropriate configuration information for the first node based on this capability information; such as configuring appropriate handover methods and access resources for the first node, thereby improving the effectiveness of mobility management.

In one possible design, the second instruction information also indicates the effective period of the capability information and/or the effective area of the capability information.

Based on this possible design, the first node can also report the effective period and/or effective area of its capability information to the host node, so that the host node or core network can configure appropriate configuration information for the first node according to the effective period and/or effective area of the capability information; such as configuring appropriate triggering periods and/or triggering events for the first node to trigger its different functions, thereby improving the effectiveness of mobility management.

In some possible designs, any one of the multiple sets of configuration information indicates at least one of the following: identifier, trigger condition, coverage area of the first node, information of the first path, address information of the first node, paging area of the first node, configuration information of the first type of reference signal, or configuration information of the second type of reference signal; wherein, the trigger condition is used to trigger the configuration information, the first path is the transmission path between the first node and the host node to which the first node is connected, the configuration information of the first type of reference signal is used to transmit the first reference signal, and the configuration information of the second type of reference signal is used to transmit the second reference signal.

In some possible designs, the triggering conditions indicated by the first set of configuration information may include at least one of the following: the local clock of the first node is within a first time period; the distance between the first node and the reference position is less than or equal to a first threshold; the angle between the first node and the reference position is less than or equal to a second threshold.

In some possible designs, the configuration information indicates the coverage area of the first node, including: the first set of configuration information indicates at least one cell, the cells managed by the first node include at least one cell, and the coverage area of the first node includes the coverage area of at least one cell.

In some possible designs, the configuration information indicates the paging area of the first node, including: the configuration information indicates at least one Tracking Area Code (TAC), and the paging area of the first node includes at least one Tracking Area (TA) corresponding to at least one TAC; and/or, the configuration information indicates at least one Radio Access Area Code (RAC), and the paging area of the first node includes at least one Radio Access Area (RA) corresponding to at least one TAC.

In some possible designs, the period of the first reference signal is the first period, and the period of the second reference signal is either a non-periodic signal or the period of the second reference signal is the second period, which is greater than the first period.

In some possible designs, the first reference signal and the second reference signal are synchronization signals/physical layer broadcast channel block (SSB) signals; the first reference signal is mapped to a first type of time-domain location, which satisfies a first period; the second reference signal is mapped to a second type of time-domain location, which is either aperiodic or satisfies a second period, which is greater than the first period.

Based on the two possible designs mentioned above, since the period of the first reference signal is less than the period of the second reference signal; or, the first reference signal is a periodic signal and the second reference signal is an aperiodic signal; therefore, the first node can distinguish between the first reference signal and the second reference signal based on the period of the reference signal, thus avoiding interference between the reference signals.

Understandably, in mobile scenarios, the frequency with which terminal devices switch cells (e.g., IAB nodes, or IAB-DUs) is significantly higher than the frequency with which IAB nodes, IAB-MTs, or IAB-DUs (e.g., the first node) switch their access to a host node. Therefore, for the first node, the frequency with which it sends reference signals for cell search of the terminal device is higher than the frequency with which it sends reference signals for searching for the host node; that is, the period of the SSB used for cell search is shorter. Thus, the first node can use the first reference signal for cell search and the second reference signal for host node search; this saves resources compared to using the same period for both the first and second reference signals (e.g., both using the period of the first reference signal).

In some possible designs, the first reference signal and the second reference signal have different signal types.

In some possible designs, the time-domain location, frequency-domain location, or polarization of the first and second reference signals are different.

In some possible designs, the first reference signal corresponds to a predefined time-domain position; the time-domain position of the second reference signal is variable.

Based on the three possible designs described above, the first node can send the first reference signal and/or the second reference signal to each other node (i.e., nodes other than the first node); each node can distinguish between the first reference signal and the second reference signal based on the type, period, time domain location, etc. of the reference signal. For example, the first reference signal and the second reference signal can be used for different services, thereby avoiding interference between the reference signals.

In some possible designs, the first reference signal and the second reference signal satisfy a quasi-co-address relationship.

Based on this possible design, the first reference signal and the second reference signal can satisfy a quasi-co-location relationship, enabling the first node to perform joint channel estimation based on the first reference signal and the second reference signal, thereby improving the accuracy of channel estimation.

In some possible designs, the first type of time-domain location and the second type of time-domain location reuse the same SSB index.

Based on this possible design, since the first reference signal is mapped to a first type of time domain location and the second reference signal is mapped to a second type of time domain location, when the first type of time domain location and the second type of time domain location reuse the same SSB index, it indicates that the first reference signal and the second reference signal satisfy a quasi-co-location relationship. Therefore, the first node can indirectly indicate that the first reference signal and the second reference signal satisfy a quasi-co-location relationship based on the first type of time domain location and the second type of time domain location, thereby reducing the signaling overhead of indicating the quasi-co-location relationship.

In conjunction with the first or second aspect, in some possible designs, the first indication information is carried in any one of the following: Radio Resource Control (RRC) signaling, F1-Access Point (AP) message, or Xn-AP message.

Thirdly, a communication device is provided for implementing various methods. This communication device can be a first node in the first aspect; or, it can be a second node in the second aspect. The communication device includes modules, units, or means corresponding to the implementation of the methods, which can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

In some possible designs, the communication device may include a processing module and a transceiver module. The processing module can be used to implement the processing functions in any of the above aspects and any possible implementations thereof. The transceiver module may include a receiving module and a transmitting module, respectively used to implement the receiving function and the transmitting function in any of the above aspects and any possible implementations thereof.

In some possible designs, the transceiver module can consist of transceiver circuits, transceivers, transceivers, or communication interfaces.

Fourthly, a communication device is provided, comprising: a processor and a memory; the memory is used to store computer instructions, which, when executed by the processor, cause the communication device to perform the method described in any aspect. The communication device may be a first node in the first aspect or a second node in the second aspect. The communication device includes modules, units, or means for implementing the method, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the function.

Fifthly, a communication device is provided, comprising: a processor and a communication interface; the communication interface being used to communicate with a module outside the communication device; the processor being used to execute a computer program or instructions to cause the communication device to perform the method described in any aspect. The communication device may be a first node in the first aspect or a second node in the second aspect. The communication device includes modules, units, or means corresponding to the implementation of the method, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

Alternatively, the interface circuit can be a code/data read/write interface circuit, which receives computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmits them to the processor so that the processor runs the computer execution instructions to perform the methods described in any of the above aspects.

In one possible design, the communication device also includes a memory for storing computer programs or instructions. Optionally, the processor and memory are integrated together, or the processor and memory are separate.

In one possible design, the memory is coupled to the processor and is located outside the communication device.

A sixth aspect provides a communication device, comprising: at least one processor; the processor being configured to execute a computer program or instructions to cause the communication device to perform the method described in any aspect. The communication device may be a first node in the first aspect or a second node in the second aspect. The communication device includes modules, units, or means for implementing the method, which may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the function.

In some possible designs, the communication device includes a memory for storing necessary program instructions and data. This memory can be integrated with the processor, or it can be independent of the processor.

In some possible designs, when the device is a chip system, it can be composed of chips or contain chips and other discrete components.

It is understandable that when the communication device provided in any of the fourth to seventh aspects is a chip, the sending action/function of the communication device can be understood as outputting information, and the receiving action/function of the communication device can be understood as inputting information.

In a seventh aspect, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed on a communication device, enable the communication device to perform the method described in any aspect.

In an eighth aspect, a computer program product containing instructions is provided, which, when run on a communication device, enables the communication device to perform the method described in either aspect.

In a ninth aspect, a communication system is provided, the communication system including the communication device being either a first node in the first aspect or a second node in the second aspect.

The technical effects of any of the design methods in aspects three through nine can be found in the technical effects of different design methods in aspects one or two above, and will not be repeated here.

Attached Figure Description

Figure 1 is a schematic diagram of an IAB communication architecture provided in this application;

Figure 2 is a schematic diagram of another IAB communication architecture provided in this application;

Figure 3 is a schematic diagram of another IAB communication architecture provided in this application;

Figure 4 is a schematic diagram of an initial access process provided in this application;

Figure 5 is a schematic diagram of another initial access process provided in this application;

Figure 6 is a schematic diagram of a satellite-based communication architecture provided in this application;

Figure 7 is a schematic diagram of the structure of a communication system provided in this application;

Figure 8 is a schematic diagram of the network equipment in an Open Access Network (O-RAN) provided in this application;

Figure 9 is a schematic diagram of the functional division of each unit in an O-RAN provided in this application;

Figure 10 is a flowchart illustrating a communication method provided in this application;

Figure 11 is a schematic diagram of another communication system provided in this application;

Figure 12 is a schematic diagram of a first reference signal and a second reference signal provided in this application;

Figure 13 is a schematic diagram of another first reference signal and second reference signal provided in this application;

Figure 14 is a schematic diagram of another communication system provided in this application;

Figure 15 is a schematic diagram of another first reference signal and second reference signal provided in this application;

Figure 16 is a flowchart illustrating another communication method provided in this application;

Figure 17 is a schematic diagram of another communication system provided in this application;

Figure 18 is a schematic diagram of the structure of a communication device provided in this application;

Figure 19 is a structural schematic diagram of another communication device provided in this application;

Figure 20 is a structural schematic diagram of another communication device provided in this application.

Detailed Implementation

In the description of this application, unless otherwise stated, "/" indicates that the objects before and after are in an "or" relationship. For example, A/B can mean A or B. "And/or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can mean: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple.

Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

It is understood that the term "embodiment" used throughout the specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

It is understood that in this application, "...when" and "if" both refer to the corresponding processing that will be carried out under certain objective circumstances, and are not limited to a specific time, nor do they require a judgment action to be performed during implementation, nor do they imply any other limitations.

It is understood that some optional features in the embodiments of this application can be implemented independently in certain scenarios without relying on other features, such as the current solution on which they are based, to solve the corresponding technical problems and achieve the corresponding effects. Alternatively, they can be combined with other features as needed in certain scenarios. Correspondingly, the apparatus given in the embodiments of this application can also implement these features or functions, which will not be elaborated here.

It is understood that in this application, "used for indication" can include direct and indirect indication, as well as explicit and implicit indication. When describing "a certain indication information is used to indicate A" or "indication information of A," it can include whether the indication information directly or indirectly indicates A, but does not necessarily mean that the indication information carries A. The information indicated by a certain piece of information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also indirectly indicate the information to be indicated by indicating other information, where there is a correlation between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various information, thereby reducing the indication overhead to some extent. At the same time, the common parts of various information can be identified and indicated uniformly to reduce the indication overhead caused by individually indicating the same information. Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies and will not be repeated here. As mentioned above, for example, when multiple pieces of information of the same type need to be indicated, different indication methods may be used for different pieces of information. In specific implementation, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method. Therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to know the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. Moreover, the sending period or sending time of these sub-information can be the same or different. This application does not limit the specific sending method. The sending period or sending time of these sub-information can be predefined, for example, predefined according to the protocol, or configured by the transmitting device by sending configuration information to the receiving device.

In this application, unless otherwise specified, the same or similar parts between the various embodiments can be referred to each other. Unless otherwise specified or logically conflicting, the terminology and/or descriptions between different embodiments are consistent and can be mutually referenced. Different embodiments can be combined to form new embodiments based on their inherent logical relationships. The following descriptions of the embodiments of this application do not constitute a limitation on the scope of protection of this application.

To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies of this application is given below.

1. Non-terrestrial networks (NTN):

Fifth-generation (5G) new radio (NR) technology is evolving from release 18 (R18/R18) to R19. Simultaneously, NR technology has moved from the standardization phase to commercial deployment. The initial research on the NR standard protocol was for wireless communication technologies designed for terrestrial cellular network scenarios, capable of providing users with low latency, ultra-reliability, ultra-high speed, and massive connectivity wireless communication services. However, cellular networks cannot achieve seamless global coverage. For example, in areas without terrestrial base stations, such as ocean areas, polar regions, and rainforests, voice and data services cannot be provided to areas covered by cellular networks.

Compared to terrestrial communications, NTN communications offer significant advantages such as global coverage, long-distance transmission, flexible networking, convenient deployment, and freedom from geographical limitations. It has been widely applied in various fields including maritime communications, positioning and navigation, disaster relief, scientific experiments, video broadcasting, and Earth observation. NTN networks can be integrated with terrestrial networks, leveraging their respective strengths to create a seamless, globally integrated sea, land, air, space, and ground communications network, meeting the diverse and ubiquitous service needs of users.

Depending on the altitude of the flight platform above the ground, the NTN can include a low-altitude platform (LAP) subnetwork, a high-altitude platform (HAP) subnetwork, and a satellite communication subnetwork.

For example, in a LAP subnetwork, base stations or base station functions are deployed on low-altitude flight platforms (e.g., drones) at an altitude of 0.1km to 1km above the ground to provide coverage for terminals; in a HAP subnetwork, base stations or base station functions are deployed on high-altitude flight platforms (e.g., aircraft) at an altitude of 8km to 50km above the ground to provide coverage for terminals; and in a SATCOM subnetwork, base stations or base station functions are deployed on satellites at an altitude of more than 50km above the ground to provide coverage for terminals. Satellite communication, with its significant advantages such as global coverage, long-distance transmission, flexible networking, convenient deployment, and lack of geographical limitations, has been widely applied in various fields including maritime communication, positioning and navigation, disaster relief, scientific experiments, video broadcasting, and Earth observation.

Furthermore, based on the satellite's orbital altitude, satellite communication systems can be divided into geostationary orbit (GEO) satellite communication systems, medium earth orbit (MEO) satellite communication systems, and low earth orbit (LEO) satellite communication systems.

In satellite communication, based on the beam's operating mode, it can generally be divided into non-staring mode (earth-moving) and staring mode (earth-fixed or quasi-earth fixed). Furthermore, satellites typically transmit information via inter-satellite links (ISL) or satellite-to-ground links. ISL refers to the link used for communication between satellites; it can also be called an inter-satellite link or crosslink. In other words, ISL refers to the link for communication between satellites. A satellite-to-ground link refers to the link used for communication between a satellite and a relay node deployed on the ground.

It should be understood that the satellite mentioned in the embodiments of this application may be a satellite base station, or may include an orbital receiver or repeater for relaying information, or a network-side device mounted on a satellite.

2. Integrated Access and Backhaul (IAB):

With the development of technologies such as virtual reality (VR), augmented reality (AR), and the Internet of Things (IoT), there will be an increasing number of terminals in the future network, and the usage of network data will continue to rise. To accommodate the increasing number of terminals and the rapidly growing network data usage, higher demands are being placed on network capacity. In hotspot areas, the use of high-frequency small cell networks is becoming increasingly popular to meet ultra-high capacity requirements. High-frequency carriers have poor propagation characteristics, suffer severe attenuation due to obstruction, and have limited coverage. Therefore, a large number of small cells need to be deployed densely in hotspot areas. However, providing fiber optic backhaul for a large number of densely deployed small cells is costly and difficult to implement. Therefore, an economical and convenient backhaul solution is needed, and IAB technology provides a solution to this problem. When using IAB technology to solve the above problems, these small cells can be called IAB nodes.

To design flexible and convenient access and backhaul solutions, both the access link (AL) and BH in the IAB scenario adopt wireless transmission schemes and NR air interface protocols. For example, the access link in the embodiments of this application generally refers to the wireless access link, and the backhaul link generally refers to the wireless backhaul link. This will be explained uniformly here and will not be repeated in the following embodiments.

In a network containing IAB nodes (hereinafter referred to as an IAB network), IAB nodes can provide wireless access services to terminals and connect to the IAB host (or IAB donor, hereinafter referred to as the host node) via a wireless backhaul link to transmit user service data.

IAB nodes connect to the core network via wired links through the IAB host. For example, in a standalone 5G architecture, IAB nodes connect to the 5G network core (5G core, 5GC) via wired links through the host node. In a non-standalone 5G architecture, IAB nodes connect to the evolved packet core (EPC) via evolved NodeBs (eNBs) on the control plane, and to the EPC via the host node and eNBs on the user plane.

To ensure the coverage performance and service transmission reliability of the IAB network, the IAB network supports multi-hop IAB nodes and multi-connection IAB nodes. Therefore, multiple transmission paths may exist between the terminal served by an IAB node and the host node. A single transmission path may include multiple nodes, such as a terminal, one or more IAB nodes, and a host node. There is a defined hierarchical relationship between IAB nodes, and between IAB nodes and the host nodes serving them. Each IAB node considers the node providing backhaul services to it as its parent node. Correspondingly, each IAB node can be considered a child node of its parent node. That is, in this embodiment, the parent node of an IAB node is the node providing backhaul services to that IAB node. Accordingly, that IAB node can be considered a child node of its parent node.

Furthermore, in this embodiment, the upper-level node of the IAB node (e.g., the parent node of the IAB node, the parent node of the parent node of the IAB node, or the parent node of IAB node a (assuming IAB node a is the parent node of the parent node of the IAB node)) is regarded as the ancestor node of the IAB node. Correspondingly, the lower-level node of the IAB node (e.g., the child node of the IAB node, the child node of the child node of the IAB node, or the child node of IAB node b (assuming IAB node b is the child node of the child node of the IAB node)) is regarded as the descendant node or offspring node of the IAB node.

For example, as shown in Figure 1, in an IAB standalone (SA) networking scenario, the parent node of IAB node #1 is the host node. IAB node #1 is also the parent node of IAB nodes #2 and #3. IAB nodes #2 and #3 are both the parent nodes of IAB node #4, and the parent node of IAB node #5 is IAB node #2. Data packets from the terminal can be transmitted to the host node via one or more IAB nodes, and then sent by the host node to the mobile gateway device (e.g., a user plane function (UPF) element in a 5G network). After receiving the data packets from the mobile gateway device, the host node can send them to the terminal via one or more IAB nodes.

In the network shown in Figure 1, there are two available paths for data packet transmission between Terminal 1 and the host node: Terminal #1 → IAB Node #4 → IAB Node #3 → IAB Node #1 → Host Node, and Terminal #1 → IAB Node #4 → IAB Node #2 → IAB Node #1 → Host Node. There are three available paths for data packet transmission between Terminal #2 and the host node: Terminal #2 → IAB Node #4 → IAB Node #3 → IAB Node #1 → Host Node, Terminal #2 → IAB Node #4 → IAB Node #2 → IAB Node #1 → Host Node, and Terminal #2 → IAB Node #5 → IAB Node #2 → IAB Node #1 → Host Node.

Understandably, in an IAB network, a transmission path between a terminal and the host node can contain one or more IAB nodes. Each IAB node needs to maintain a radio backhaul link to its parent node and also maintain radio links with its child nodes. If an IAB node is the node through which a terminal accesses, the link between that IAB node and its child nodes (i.e., the terminal) is a radio access link. If an IAB node is the node that provides backhaul services to other IAB nodes, the link between that IAB node and its child nodes (i.e., the other IAB nodes) is a backhaul link.

For example, referring to Figure 1, in the path "Terminal #1 → IAB Node #4 → IAB Node #3 → IAB Node #1 → Host Node", Terminal #1 accesses IAB Node #4 via a wireless access link, IAB Node #4 accesses IAB Node #3 via a wireless backhaul link, IAB Node #3 accesses IAB Node #1 via a wireless backhaul link, and IAB Node #1 accesses the host node via a wireless backhaul link.

For example, the IAB node can be a customer premises equipment (CPE), a residential gateway (RG), or other similar devices. In this case, the method provided in this application embodiment can also be applied to home access scenarios.

The above-mentioned IAB standalone networking scenario is merely an example. In IAB scenarios that combine multi-hop and multi-connection, there are many other possibilities for IAB standalone networking, such as a host node and an IAB node under another host node forming a dual connection to provide terminal services, etc., which will not be listed here.

Furthermore, the IAB network also supports non-standalone (NSA) networking; for example, IAB nodes can support 4th generation (4G) and 5G dual connectivity (E-UTRAN NR dual connectivity, EN-DC); and/or, IAB nodes can support 5G and 6G EN-DC. Taking 4G and 5G EN-DC as an example, as shown in Figure 2, the eNB is the primary parent node of the IAB node, connected to the EPC via the S1 interface for user plane and control plane transmission. The host node is the secondary parent node of the IAB node, connected to the EPC via the S1-U interface for user plane transmission. The eNB and the host node communicate via the X-2 interface. Similarly, the terminal also supports EN-DC. For example, the terminal connects to its primary base station eNB via the LTE Uu interface and connects to its secondary base station IAB node via the NR Uu interface. The terminal's secondary base station can also be the host node.

The above-described IAB non-standalone networking scenario is merely an example. Multi-hop networking is also supported in IAB non-standalone networking scenarios. For example, one or more IAB nodes can be included between the IAB node and the host node. That is, the IAB node can be connected to the host node through a multi-hop wireless backhaul link, etc., which will not be listed here.

The existing IAB network supports two types of network topologies: tree-based topology and directed acyclic graph (DAG) topology. When the IAB network has a tree-based topology, each IAB node has only one parent node and can have one or more child nodes. When the IAB network has a DAG topology, each IAB node can have one or two parent nodes and can also have one or more child nodes.

In this embodiment, the host node can be a host base station. In a 5G network, the host node can be simply referred to as an IAB host or DgNB (i.e., donor gNodeB).

The host node can be a complete entity, or it can be a separate form of a centralized unit (CU) (hereinafter referred to as donor-CU, or simply CU) and a distributed unit (DU) (hereinafter referred to as donor-DU). In this case, the host node is composed of CU and DU. Similarly, the CU can be considered to be located on the host node, and the DU is also located on the host node.

In 5G, the logical interface between the IAB node (e.g., the DU of the IAB node) and the host node (or the CU/DU of the host node) is the F1 interface; the F1 interface can also be called the F1* interface, supporting both the user plane and the control plane. The protocol layer of the F1 interface refers to the communication protocol layer on the F1 interface. It is understood that in scenarios evolving after 5G (i.e., next-generation communication networks, such as 5.5G, 6G, etc.), the logical interface between the IAB node and the host node can also be other interfaces besides the F1 interface, and this application embodiment does not impose such limitations.

In this embodiment, the IAB node consists of a mobile terminal (MT) and a DU. The IAB node can establish a backhaul connection with at least one parent node of the IAB node through its MT (or, it can also be written as IAB-MT); in this case, IAB-MT can also be considered to be located within the IAB node; the IAB node can also be considered as a terminal or user equipment (UE). The DU of the IAB node (or, it can also be called IAB-DU) can provide access services to the terminal or the MT of other IAB nodes. In this case, IAB-DU can also be considered to be located within the IAB node; the IAB node can be considered as a network device.

For example, referring to Figure 3, the terminal connects to the host node through IAB node #2 and IAB node #1. Both IAB node #1 and IAB node #2 consist of a DU and a MT. The DU of IAB node #2 provides access services to the terminal. The DU of IAB node #1 provides access services to the MT of IAB node #2. The DU of the host node provides access services to the MT of IAB node #1.

In existing IAB networks, a backhaul adaptation protocol (BAP) layer has been introduced into the wireless backhaul link. The BAP layer is located above the radio link control (RLC) layer and can be used to implement functions such as packet routing and bearer mapping in the wireless backhaul link.

When an IAB node consists of MT and DU (or an IAB node includes MT and DU), MT and DU may share the BAP layer or not. That is, MT and DU each have their own BAP layer. Each BAP layer may include one or more BAP layer entities. Each BAP layer entity may include a transmitting part and a receiving entity. The transmitting part of the BAP layer entity may also be called the transmitting entity or the receiving entity of the BAP layer entity.

3. Initial Access in NR:

In an SA network scenario, as shown in Figure 4, the initial access in NR may include the following steps:

1): The UE performs cell search and selection. Specifically, the UE achieves downlink synchronization with the cell (such as the base station) and selects the cell with the best signal quality to camp on.

For example, the UE can perform cell search and obtain synchronization signals, which include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS); thereby identifying cells and synchronizing timing with them based on different signals, that is, achieving downlink synchronization.

2): The UE initiates random access to the base station (i.e., the base station to which the best cell selected by the UE belongs). Specifically, the UE can establish uplink synchronization with the cell and obtain uplink resources through the random access procedure.

For example, the UE can send a preamble during the random access process. The base station to which the cell belongs can adjust its clock according to the preamble to align the transmission timing of the UE with that of the base station, thus achieving uplink synchronization.

3): The UE establishes an RRC connection with the base station.

For example, a UE can send a Radio Resource Control (RRC) Setup Request message to a base station; after receiving the RRC Setup Request message, the base station can respond to the UE with an RRC Setup message.

4): The UE establishes the initial context with the base station. Alternatively, it can be considered as the UE establishing context information with the core network (such as the 5G core network (5th generation core, 5GC)) through the base station.

For example, when making decisions on various events, the base station needs to rely on the context information of the UE to determine the most appropriate decision result; therefore, the context information of the UE can be considered as being used to improve the accuracy of the base station's decision results.

Optionally, when the UE has data service requirements, the following steps can also be performed:

5) The UE establishes a Protocol Data Unit (PDU) session with the base station. Alternatively, it can be considered as the UE establishing a PDU session with the core network through the base station. The PDU session provides a PDU connection between the UE and the data network (DN), meaning it supports PDU exchange between the UE and the DN.

4. Initial access in the IAB network:

In an SA (Standalone) network scenario, the IAB node access network can include the IAB node's MT (hereinafter referred to as IAB-MT) access network and the IAB node's DU (hereinafter referred to as IAB-DU) access network. Specifically, as shown in Figure 5, the initial access in the IAB network can include the following steps:

1): IAB-MT access network.

For example, IAB-MT can perform host node search and selection (such as selecting the host node with the best signal quality), and then initiate random access to the selected host node. Furthermore, it can establish an RRC connection with the host node to achieve access to the core network (such as 5GC).

For example, during the IAB-MT's search for a host node, if the synchronization signal obtained by the IAB-MT comes from the host node, the IAB node can directly connect to the host node. In this case, after the IAB node accesses the network, the host node becomes the parent node of the IAB node. If the synchronization signal obtained by the IAB-MT comes from an IAB node associated with the host node (as shown by IAB node ' in Figure 5), the IAB node can connect to the host node through IAB node '. In this case, after the IAB node accesses the network, IAB node ' becomes the parent node of the IAB node.

An IAB node associated with a host node can be understood as either a node directly or indirectly connected to the host node, or a descendant node of the host node. For example, if an IAB node is connected to the host node through an IAB node', then it can be considered that the IAB node' is directly connected to the host node, or indirectly connected. In this case, the IAB' node is a child node of the host node, meaning it is a descendant node of the host node.

Specifically, the implementation process of the IAB-MT access network is similar to the initial access process in NR mentioned above. Please refer to the relevant descriptions above for details, which will not be repeated here.

For example, the selection of a host node by the IAB-MT can also be understood as the selection of a CU by the IAB-MT. The CU selected by the IAB-MT can also be called the RRC-terminating IAB-dornor-CU. Thus, after the IAB-MT accesses the network, this CU can serve the IAB-MT.

Optionally, after the RRC connection is established, the IAB node can also indicate its characteristics to the network (such as the core network) through the RRC Setup Complete message, such as indicating to the network that it is an IAB node; so that the network can perform identity authentication based on the characteristics.

2): The host node establishes a communication channel with the IAB node.

For example, the host node can establish one or more backhaul RLC channels on the transmission path between the host node and the IAB node. Specifically, BH RLC channels are established on the intermediate nodes between the host node and the IAB node.

Optionally, the host node can also update the BAP layer configuration, BAP path identifier (ID), and routing table updates of intermediate nodes. The BAP path ID indicates the routing path that a packet should follow to reach its destination node.

3): IAB-DU establishes an F1 interface based on the communication channel.

For example, after establishing the F1 interface, the IAB-DU can communicate with the host node via the F1 interface, or in other words, it can connect to the network via the F1 interface. Therefore, step 3) can also be understood as the IAB-DU accessing the network. Furthermore, the IAB-DU can also provide services to the UE.

During the establishment of an IAB-DU, the original configuration information is typically released, and new configuration information is acquired; communication is then established based on this new configuration information. Therefore, in mobile IAB (mIAB) scenarios, this triggers frequent switching of the host node to which the IAB-DU connects, leading to frequent release and updates of the IAB-DU's configuration information, thus increasing signaling overhead.

In view of this, the communication method and apparatus provided in the embodiments of this application allow the IAB-DU (i.e., the first node) to receive multiple sets of configuration information with different trigger conditions configured by its host node (i.e., multiple sets of configuration information indicated by the host node through the first indication information); thereby, communication can be performed based on one set of configuration information (i.e., the first set of configuration information) among the multiple sets of configuration information.

For example, the triggering conditions corresponding to multiple sets of configuration information can be related to the time when the first node reconnects to the network after connecting to the host node (such as reconnecting to the host node or a new host node, or switching to another host node). Therefore, different configuration information will be triggered during each reconnection process of the first node. This ensures that each time the first node reconnects to the network after connecting to the host node, one set of configuration information is in effect, allowing the first node to communicate using this set of configuration information. Compared to the scheme where the first node reacquires configuration information each time it connects to the network, this reduces the signaling overhead of instructing the configuration information.

The technical solution provided in this application can be used in various communication systems, including high-altitude platform station (HAPS) satellite communication systems, UAV (Unmanned Aerial Vehicle) NTN systems, such as integrated communication and navigation (ICAN) systems, global navigation satellite systems (GNSS), and ultra-dense low-Earth orbit (LEO) satellite communication systems. Satellite communication systems can be integrated with traditional mobile communication systems. For example, the mobile communication system can be a cellular system related to the 3rd generation partnership project (3GPP), such as the 4th generation (4G) long term evolution (LTE) system, the worldwide interoperability for microwave access (WiMAX) communication system, the evolved LTE system (LTE-Advanced, LTE-A) system, the 5G NR system, the vehicle to everything (V2X) system, the LTE and NR hybrid networking system, or the device-to-device (D2D) system, the machine-to-machine (M2M) communication system, the Internet of Things (IoT), and other next-generation communication systems, such as the 6th generation (6G) communication system.

Alternatively, the communication system may be a non-3GPP communication system, such as an open radio access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a communication system that integrates multiple of the above communication systems. This application does not impose any restrictions on this.

The communication systems and scenarios applicable to this application mentioned above are merely illustrative examples. The communication systems and scenarios applicable to this application are not limited thereto. The communication systems and scenarios provided in this application do not impose any limitations on the solutions of this application. This is hereby stated uniformly and will not be repeated below.

This application provides an exemplary communication system. The communication system may include at least one first node and at least one second node. Both the first and second nodes are located within a node of the IAB network, and the second node is capable of providing services to the first node. Alternatively, the second node may be considered a candidate parent node of the first node.

Optionally, the first node can be located on an IAB node; correspondingly, the second node can also be located on an IAB node, or the second node can be located on the host node. Specifically, the first node can be an IAB-DU, and the second node can be an IAB-DU of the candidate parent node of the first node, or the second node can be an IAB dornor-DU.

For example, the communication between the first node and the second node can be understood as follows: the first node communicates with the second node through the MT of its IAB node (i.e., the IAB-MT associated with the first node); correspondingly, the second node can also communicate with the first node through the MT.

For example, each node in the IAB network can serve at least one terminal device. Therefore, the node where the first node is located and the node where the second node is located can also serve at least one terminal device respectively, so the first node and the second node are also considered to be network devices.

In one possible implementation, both the first and second nodes are deployed on the NTN. In this case, the communication system can also be considered to be applied in an NTN scenario.

Optionally, the first and second nodes can be deployed on non-ground platforms, such as low-altitude platforms (e.g., drones), high-altitude platforms (e.g., aircraft), or satellites.

For example, assuming both the first and second nodes are deployed on satellites, or both are satellites, the communication system may also include an NTN gateway (or gateway station). Typically, the NTN gateway is deployed on the ground. The NTN gateway can communicate with the satellite, and the link between the satellite and the NTN gateway can be called a feeder link.

As shown in Figure 6(a), when the satellite acts as a wireless relay node, or in other words, the satellite has relay forwarding capabilities, the NTN gateway has the functions of a base station or some of the functions of a base station. In this case, the NTN gateway can function as a base station. Alternatively, the NTN gateway can be deployed separately from the base station; that is, in addition to the NTN gateway, the communication system also includes a base station. Figure 6 illustrates this using the example of deploying the NTN gateway and base station separately.

As shown in Figure 6(b), when a satellite can perform some or all of the functions of a base station, and has data processing capabilities, it can be used as a base station. In this case, the NTN gateway and the satellite can transmit user plane data of the terminal equipment through the satellite radio interface (SRI).

Furthermore, in cases where satellites can perform some or all of the functions of a base station, as shown in Figure 6(c), there are ISLs between different satellites, and satellites can communicate with each other via ISLs. Alternatively, as shown in Figure 6(d), a satellite can have the DU processing function of a base station, or in other words, a satellite can act as a DU. In this scenario, the CU processing function of the base station can be deployed on the ground, and the CU and DU communicate with each other via the F1 interface through an NTN gateway.

In the architecture shown in Figure 6 (as in Figure 6(a) to Figure 6(d)), NG refers to the interface between the base station and the core network. Uu refers to the interface between the base station and the terminal equipment. Xn refers to the interface between base stations. It is understood that as the communication system evolves, the names of the interfaces between the base station and the core network, between the base station and the terminal equipment, and between base stations may also change, and this application does not specifically limit them.

Optionally, when a satellite acts as a wireless relay node with relay forwarding capabilities, it can be considered to be operating in transparent mode. When a satellite has data processing capabilities and can perform some or all of the functions of a base station, it can be considered to be operating in regenerative mode. For a given satellite, it may support only transparent mode, only regenerative mode, or both transparent and regenerative modes, and it may be able to switch between transparent and regenerative modes.

In another possible implementation, the first node can be deployed on the NTN, and the second node can be deployed on the ground. In this case, the communication system can also be considered to be applied to a scenario where NTN and terrestrial networks are integrated.

For example, the implementation of the first node deployed on the NTN can be found in the relevant description of the above embodiments, and will not be repeated here. For example, the second node can be deployed as a terrestrial base station, or the second node can be a terrestrial base station.

Combining the two possible implementation methods mentioned above, and referring to Figure 7, we have provided an architecture for a communication system application in this application.

In satellite communications, satellites can provide communication, navigation, and positioning services to terminal devices using multiple beams. In other words, a satellite can use multiple beams to cover its service area. For example, different beams can communicate using one or more of time-division multiplexing, frequency-division multiplexing, space-division multiplexing, and polarization multiplexing.

In a protocol, beaming can be represented as a spatial domain filter, spatial filter, spatial domain parameter, spatial parameter, spatial domain setting, spatial setting, or quasi-colocation (QCL) information, QCL assumption, QCL indication, etc. Beaming can be indicated through transmission configuration indication (TCI) state parameters or spatial relation parameters. Therefore, in this application, beaming can be replaced by spatial domain filter, spatial filter, spatial parameter, spatial parameter, spatial setting, spatial setting, QCL information, QCL assumption, QCL indication, TCI-state, spatial relation, etc. These terms are also equivalent to each other. Beaming in this application can also be replaced with other beaming terms, and this application does not limit this.

As shown in Figure 7, satellite #1 can serve terminal devices #1 and #2, satellite #2 can serve terminal device #3, and satellite #3 can serve terminal device #4. Specifically, the satellites can communicate wirelessly with the terminal devices through broadcast communication signals and navigation signals, and they can also communicate wirelessly with the NTN gateway.

Satellites can connect to base stations or NTN gateways to enable communication between terminal devices and the network. For example, satellite #1 can connect to base station #1 to enable communication between base station #1 and terminal device #1 (and/or terminal device #2); alternatively, satellite #1 can connect to the NTN gateway via satellite #2 or satellite #3 to enable communication between the NTN gateway and terminal device #1 (and/or terminal device #2); or satellite #1 can connect to base station #2 via satellite #2 to enable communication between base station #2 and terminal device #1 (and/or terminal device #2). The communication links between satellites #1, #2, and #3 are ISLs (Independent Links). Base station #1, base station #2, and the NTN gateway can all receive information from the network and send information to the network. In other words, communication between the terminal device and the base station or NTN gateway can also be considered as communication between the terminal device and the network.

Similarly, satellite #2 can access base station #2 to enable communication between base station #2 and terminal device #3; or, satellite #2 can access the NTN gateway via satellite #3 to enable communication between the NTN gateway and terminal device #3; or, satellite #2 can access base station #1 via satellite #1 to enable communication between base station #1 and terminal device #3. Satellite #3 can access the NTN gateway to enable communication between the NTN gateway and terminal device #4; or, satellite #3 can access base station #2 to enable communication between base station #2 and terminal device #4; or, satellite #3 can access base station #1 via satellite #2 and satellite #1 to enable communication between base station #1 and terminal device #3.

When the communication system shown in Figure 7 is applied to an IAB network, for the path: Terminal device #1 (and/or Terminal device #2) → Satellite #1 → Base station #1; Satellite #1 can act as an IAB node, and Base station #1 can act as a host node; in this case, the first node can be deployed on satellite #1, and the second node can be deployed on base station #1. For the path: Terminal device #1 (and/or Terminal device #2) → Satellite #1 → Satellite #2 → Base station #2; Both satellite #1 and satellite #2 can act as IAB nodes, and base station #2 can act as a host node; in this case, the first node can be deployed on satellite #1, and the second node can be deployed on satellite #2. For the path: Terminal device #1 (and/or Terminal device #2) → Satellite #1 → Satellite #2 → Satellite #3 → NTN gateway; Both satellite #1 and satellite #2 can act as IAB nodes, and satellite #3 can act as a host node; in this case, the first node can be deployed on satellite #1, and correspondingly, the second node can be deployed on satellite #2.

Similarly, for the path: Terminal Device #3 → Satellite #2 → Base Station #2; Satellite #2 can act as an IAB node, and Base Station #2 can act as a host node; in this case, the first node can be deployed on Satellite #2, and the second node can be deployed on Base Station #2. For the path: Terminal Device #3 → Satellite #2 → Satellite #1 → Base Station #1; Both Satellite #1 and Satellite #2 can act as IAB nodes, and Base Station #1 can act as a host node; in this case, the first node can be deployed on Satellite #2, and the second node can be deployed on Satellite #1. For the path: Terminal Device #3 → Satellite #2 → Satellite #3 → NTN Gateway; Satellite #2 can act as an IAB node, and Satellite #3 can act as a host node; in this case, the first node can be deployed on Satellite #2, and correspondingly, the second node can be deployed on Satellite #3.

For the path: Terminal device #4 → Satellite #3 → Base station #2; Satellite #3 can act as an IAB node, and Base station #2 can act as a host node; in this case, the first node can be deployed on satellite #3, and the second node can be deployed on base station #2. For the path: Terminal device #4 → Satellite #3 → Satellite #2 → Satellite #1 → Base station #1; Satellite #1, Satellite #2, and Satellite #3 can all act as IAB nodes, and Base station #1 can act as a host node; in this case, the first node can be deployed on satellite #3, and the second node can be deployed on satellite #2.

It is understandable that the satellites in the architecture described in Figures 6 and 7 above can be replaced by non-ground payloads on other flight platforms such as drones and airplanes.

Optionally, the network device in this application embodiment is a device that connects a terminal device to a wireless network. The network device can be a node in a radio access network, also known as a base station or a radio access network (RAN) node (or device). For example, the network device may include an evolved Node B (NodeB, eNB, or e-NodeB) in an LTE or LTE-A system, such as a traditional macro base station (eNB) or a micro base station (eNB) in a heterogeneous network scenario. Alternatively, it may include a next-generation node B (gNB). Alternatively, it may include a TRP, a home base station (e.g., a home evolved Node B, or a home Node B, HNB), a base band unit (BBU), or a base band pool. Alternatively, it may include a base station in an NTN, which can be deployed on a high-altitude platform or satellite. In an NTN, the access network device can act as a Layer 1 (L1) relay, a base station, a DU, or an IAB node. Alternatively, the network device can be a device that implements base station functions in IoT, such as V2X, D2D, or machine-to-machine (M2M) devices that implement base station functions. Alternatively, it can include in-vehicle devices or wearable devices. Alternatively, it can include network devices in 5G networks or public land mobile networks (PLMNs) that evolve from 5G. The embodiments of this application are not limited.

Optionally, the base station in this application embodiment may include various forms of base stations, such as: macro base station, micro base station (also known as small station), relay station, access point, home base station, TRP, transmission point (TP), mobile switching center, etc. This application embodiment does not specifically limit these.

In some possible scenarios, the network device in this application embodiment can also be a module or unit capable of implementing some functions of a base station. For example, the network device can be a CU, DU, CU-control plane (CP), CU-user plane (UP), or radio unit (RU), etc. The CU and DU can be set separately, or they can be included in the same network element (such as BBU), that is, the BBU can include at least one CU and at least one DU. The RU can be included in radio equipment or radio unit; for example, it can be included in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

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

Referring to Figure 8(a), which is a schematic diagram of another communication architecture provided by an embodiment of this application, as shown in Figure 8(a), the CU and DU are included in the same BBU, and the RU is included in the radio frequency unit. Furthermore, the access network device shown in Figure 8(a) can communicate with the core network (CN) via a BH link, and the access network device can also communicate with the terminal device via an air interface. Specifically, the BBU in the access network device communicates with the CN via a BH link, and the RU in the access network device communicates with at least one terminal device via an air interface. The BBU can communicate with at least one RU via a fronthaul link; the BBU and RU may or may not be co-located.

Referring to Figure 8(b), a schematic diagram of another communication framework provided in an embodiment of this application is shown. This communication system includes a RAN intelligent controller (RIC). The RIC includes a near-real-time RIC (near-RT RIC) and a non-real-time RIC (non-RT RIC). The near-real-time RIC is used for model training and inference. For example, it is used to train an artificial intelligence (AI) model and then use that AI model for inference. The near-real-time RIC can obtain network-side and/or terminal-side information from access network devices (e.g., CU, CU-CP, CU-UP, DU, and/or RU) and/or terminal devices. This information can be used as training data or inference data.

Optionally, the near real-time RIC can deliver inference results to access network devices and/or terminal devices. Optionally, inference results can be exchanged between the CU and DU, and/or between the DU and RU. For example, the near real-time RIC delivers inference results to the DU, and the DU sends them to the RU. This is used to achieve near real-time intelligent management of the RAN. Through data collection and related operations on the E2 interface, near real-time control and optimization of O-RAN modules and resources are achieved.

For example, a non-real-time RIC is used for model training and inference. For instance, it can be used to train an AI model and then use that model for inference. The non-real-time RIC can obtain network-side and/or terminal-side information from RAN nodes (e.g., CU, CU-CP, CU-UP, DU, and/or RU) and/or terminal devices. This information can be used as training data or inference data, and the inference results can be delivered to the access network devices and/or terminal devices. Optionally, inference results can be exchanged between CUs and DUs, and/or between DUs and RUs; for example, the non-real-time RIC delivers the inference results to the DU, which then forwards them to the RU.

For example, near real-time RIC and non-real-time RIC can also be set up as separate network elements.

Optionally, near real-time RICs and non-real-time RICs can also be part of other devices. For example, near real-time RICs can be set in access network devices (e.g., CU, DU), while non-real-time RICs can be set in operations and maintenance (OAM), cloud servers, CN, or other access network devices.

For example, as shown in Figure 9, the O-RAN central unit (O-CU) is used to implement the radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, service data adaptation protocol (SDAP) layer, and other control functions in the 3GPP standard.

O-RAN Central Unit Control Plane (O-CU-CP): Similar to the CU-CP in the NR system, it is used to implement the functions of the RRC layer and the control plane functions of the PDCP layer. It is part of the O-CU.

O-RAN Central Unit User Plane (O-CU-UP): Similar to the CU-UP in the NR system, it is used to implement the functions of the SDAP layer and the user plane functions of the PDCP layer. It is part of the O-CU.

O-RAN distributed unit (O-DU): Based on low-layer function segmentation, it is used to implement the RLC layer, media access control (MAC) layer, and higher physical layer (Higher PHY) in the 3GPP standard. The higher physical layer functions include at least one of the following: forward error correction (FEC) encoding/decoding, scrambling/descrambling, or modulation/demodulation.

The O-RAN radio unit (O-RU) is based on low-layer function partitioning and is used to implement the lower physical layer (PHY) functions and radio frequency (RF) functions in the 3GPP standard. The PHY functions include at least one of the following: Fast Fourier Transform (FFT)/Inverse Fast Fourier Transform (iFFT) transformation, digital beamforming, or extraction and filtering of the Physical Random Access Channel (PRACH). It is similar to the TRP or RRH in 3GPP, but includes low-PHY functions such as FFT/iFFT or PHY extraction.

Optionally, the terminal device in this application embodiment can be a user-side device used to implement wireless communication functions, such as a terminal or a chip that can be used in the terminal. The terminal can be a UE, MT, access terminal, satellite terminal, terminal unit, terminal station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, wireless communication device, terminal agent, or terminal apparatus in a 5G network or a PLMN evolved from 5G. Access terminals can be cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, smartphones (such as mobile phones), personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, mobile internet devices (MIDs), in-vehicle devices (e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.) or wearable devices (e.g., smartwatches, smart bracelets, pedometers, smart glasses, etc.), virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, point-of-sale (POS) machines, customer-premises equipment (CPE), and light user equipment (light Wireless terminals include: UE (User Equipment), reduced capability UE (REDCAP UE), smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters), wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in telemedicine or telehealth services, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, wireless data cards, tablet computers (e.g., tablets, PDAs), wireless modems, handsets, laptop computers (e.g., laptops), machine-type communication (MTC) terminals (e.g., intelligent robots, robotic arms, workshop equipment), and flying equipment (e.g., intelligent robots, hot air balloons, drones, airplanes). Terminal devices can also be vehicle-mounted devices, such as vehicle-mounted devices, in-vehicle modules, in-vehicle chips, on-board units (OBUs), or telematics boxes (T-BOXs); alternatively, terminal devices can be terminals with communication functions in IoT, such as devices that function as terminals in V2X (e.g., vehicle-to-everything devices), devices that function as terminals in D2D communication, or devices that function as terminals in M2M communication. Terminals can be mobile or fixed.

The embodiments of this application do not limit the form of the terminal device. The device used to implement the functions of the terminal device can be the terminal device itself, or it can be a device that supports the terminal device in implementing the functions, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of chips, or it can include chips and other discrete devices. All or part of the functions of the terminal device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform).

Optionally, network devices and terminal devices, network devices and network devices, or terminal devices and terminal devices can communicate through licensed spectrum, or through unlicensed spectrum, or simultaneously through both licensed and unlicensed spectrum.

Optionally, communication between network devices and terminal devices, between network devices, or between terminal devices can be conducted using spectrum below 6 GHz, or using spectrum above 6 GHz, or simultaneously using spectrum below 6 GHz and spectrum above 6 GHz. The embodiments of this application do not limit the spectrum resources used for wireless communication.

The communication method provided in the embodiments of this application will now be described in detail with reference to the accompanying drawings. It is understood that in the embodiments of this application, the first node or the second node may execute some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also execute other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments of this application, and it is not necessary to execute all the operations in the embodiments of this application.

Referring to Figure 10, which is a flowchart of a communication method provided in this application, the communication method may include the following steps S1001 to S1002:

S1001, the second node sends a first indication message to the first node; correspondingly, the first node receives the first indication message from the second node. The first indication message indicates multiple sets of configuration information, each set used for different triggering conditions of the first node.

Optionally, the second node can be located on the host node; or, the second node can be located on the IAB node, in which case the second node can be a descendant node of the host node. That is, the first node can communicate with the host node through the second node.

For example, after the first node connects to the second node, the second node (or the host node) can send configuration information to the first node; that is, the above step S1001 is executed after the first node connects to the second node.

For example, when the second node is located on the host node, the first node accessing the second node can be understood as the first node accessing the host node, or in other words, the first node accessing the network. When the second node is located on an IAB node, the first node accessing the second node can be understood as the first node accessing the host node through the second node, or in other words, the first node accessing the network through the second node.

For example, the implementation of the first node accessing the second node can refer to the relevant description of the IAB-DU access network mentioned above, and will not be repeated here.

Optionally, the second node can send the first indication information to the first node via broadcast or multicast. That is, if the second node is located at the host node or IAB node, the second node can send the first indication information to the first node via broadcast or multicast.

Optionally, if the second node is an IAB node, the second node can obtain the first indication information from the host node. For example, the host node (such as the DU of the host node) can send the first indication information via unicast. For example, the first indication information can be carried in any of the following: an RRC message, an F1-AP message, or an Xn-AP message.

Specifically, when the second node is a descendant node of the host node (i.e., the second node is located on an IAB node), the host node (such as the host node's DU) can send the first indication information to its child node via unicast. If the second node is located on that child node, it means the host node is sending the first indication information to the IAB node where the second node is located. If the second node is not located on that child node, after receiving the first indication information, the child node can send the first indication information to its child nodes, further enabling the second node to receive the first indication information.

Optionally, the first node can be a ground node or a non-ground node; similarly, the second node can also be a ground node or a non-ground node; wherein, ground nodes include stationary nodes or mobile nodes, and non-ground nodes include stationary nodes or mobile nodes.

For example, in the embodiments of this application, a ground node refers to a node deployed on the ground; correspondingly, a non-ground node refers to a node deployed on a location other than the ground. For example, a non-ground node can be deployed on a satellite, a low-altitude platform (such as a drone), or a high-altitude platform (such as an aircraft).

A stationary node is a node that remains stationary relative to the ground. Therefore, a ground node is a stationary node, meaning a node deployed on the ground that remains stationary relative to the ground; a non-ground node is a stationary node, meaning a node deployed off the ground that remains stationary relative to the ground.

A mobile node is a node that moves relative to the ground. Therefore, a ground node is a mobile node, which is a node deployed on the ground and moving relative to the ground (e.g., a node deployed in a moving vehicle); a non-ground node is a mobile node, which is a node deployed off the ground and moving relative to the ground.

Referring to Figure 11 (Figure 11(a) and/or Figure 11(b)), an exemplary communication architecture is provided for an embodiment of this application.

As shown in Figure 11(a), IAB nodes #1 to #3 are all non-terrestrial nodes, as are host nodes A and B. The first node can be located at IAB node #3; if the host node is host node A, the second node can be located at IAB node #2 or host node A; that is, the first node can access host node A through IAB node #2. If the host node is host node B, the second node can be located at IAB node #1 or host node B; that is, the first node can access host node B through IAB node #1. Furthermore, host nodes A and B can communicate with the core network. In addition, any one of IAB nodes #1 to #3 can provide access services for terminal devices, and/or, any one of IAB nodes #1 to #3 can provide backhaul services for its descendant nodes.

As shown in Figure 11(b), IAB nodes #1 to #5 are all non-terrestrial nodes, while host node A and host node B are both terrestrial nodes. The first node can be located at IAB node #3. If the host node is host node A, the second node can be located at any of IAB nodes #2, #4, or host node A; that is, the first node can access host node A through IAB nodes #2 and #4. If the host node is host node B, the second node can be located at any of IAB nodes #1, #5, or host node B; that is, the first node can access host node B through IAB nodes #1 and #5. Furthermore, host node A and host node B can communicate with the core network. In addition, any of IAB nodes #1 to #5 can provide access services for terminal devices, and/or, any of IAB nodes #1 to #5 can provide backhaul services for the descendant nodes of that IAB node.

S1002, The first node communicates according to the first set of configuration information. Among them, the first set of configuration information is included in the multiple sets of configuration information.

For example, the first set of configuration information is the configuration information that is triggered for the first time among multiple sets of configuration information. For instance, if the triggering condition is related to the process of the first node reconnecting to the network after the first node connects to the second node, the first trigger refers to the configuration information that takes effect during the first network access process after the first node connects to the second node.

Optionally, the first node communicates according to the first set of configuration information, including: the first node provides services to terminal devices within its coverage area according to the first set of configuration information.

Optionally, the first node communicates based on the first set of configuration information, including: communicating based on the first set of configuration information at a first moment; the communication method further includes: communicating based on the second set of configuration information at a second moment, wherein the multiple sets of configuration information include the second set of configuration information, and the second moment is after the first moment.

For example, taking multiple sets of configuration information, including three sets of configuration information (i.e., configuration information #1 to configuration information #3), after receiving the first indication information, the first node can communicate using different configuration information at different times. For instance, the first node can communicate based on configuration information #1 at time #1, based on configuration information #2 at time #2, and based on configuration information #3 at time #3. Here, time #1, time #2, and time #3 are different.

The communication method provided in this application embodiment allows the IAB-DU (i.e., the first node) to receive multiple sets of configuration information with different trigger conditions configured by its host node (i.e., multiple sets of configuration information indicated by the host node through the first indication information); thereby, it can communicate based on one set of configuration information (i.e., the first set of configuration information) among the multiple sets of configuration information.

For example, the triggering conditions corresponding to multiple sets of configuration information can be related to the time when the first node reconnects to the network after connecting to the host node (such as reconnecting to the host node or a new host node, or switching to another host node). Therefore, different configuration information will be triggered during each reconnection process of the first node. This ensures that during each reconnection process after connecting to the host node, one set of configuration information from multiple sets becomes effective, allowing the first node to communicate using this set of configuration information. Compared to the scheme where the first node re-acquires configuration information each time it connects to the network, this reduces the signaling overhead of instructing the configuration information.

Optionally, any one of the multiple sets of configuration information indicates at least one of the following: identifier, triggering condition, coverage area of the first node, information of the first path, address information of the first node, paging area of the first node, configuration information of the first type of reference signal, or configuration information of the second type of reference signal.

Among them, the triggering condition is used to trigger the configuration information, the first path is the transmission path between the first node and the host node that the first node reconnects to, the first type of reference signal configuration information is used to transmit the first reference signal, and the second type of reference signal configuration information is used to transmit the second reference signal.

For example, the identifiers indicated by the configuration information are used to identify different configuration information.

Optionally, if the configuration information indicates the triggering condition, the first node can communicate according to the configuration information when the triggering condition is met. For example, if the triggering condition indicated by the first set of configuration information is a first condition, then communicating according to the first set of configuration information includes: communicating according to the first set of configuration information when the first condition is met. The triggering condition indicated by the first set of configuration information can also be called the triggering condition corresponding to the first set of configuration information. Therefore, communicating according to the first set of configuration information when the first condition is met can also be replaced by: communicating according to the first set of configuration information when the triggering condition corresponding to the first set of configuration information is met.

Optionally, the triggering condition can include the following three possible implementation methods:

In one possible implementation, the triggering condition is time-based. That is, multiple sets of configuration information can be triggered based on different times.

For example, different configuration information is triggered when the local clock of the first node is in different time periods (i.e., the configuration information corresponding to the time period in which the local clock of the first node is located takes effect). For instance, taking multiple sets of configuration information, including three sets of configuration information (i.e., the first set of configuration information to the third set of configuration information), the triggering condition indicated by the first set of configuration information can be that the local clock of the first node is in the first time period; similarly, the triggering condition indicated by the second set of configuration information can be that the local clock of the first node is in the second time period; and the triggering condition indicated by the third set of configuration information can be that the local clock of the first node is in the third time period. Among these, the first time period, the second time period, and the third time period are all different.

Optionally, the time period corresponding to the configuration information (i.e. the time period used to trigger the configuration information, such as the first time period corresponding to the first set of configuration information) may be related to the time when the first node reconnects to the network after connecting to the second node.

It should be understood that the first node will switch to different host nodes during its movement; this switching process can usually be considered as the process of accessing the network. Therefore, after the first node accesses the second node, switching to different new host nodes during its movement can also be considered as the first node re-accessing the network.

Therefore, the host node or core network can determine the time for the first node to reconnect to the network based on the movement speed and direction of movement of the first node and each node in the IAB network; for example, after the first node reconnects to the second node, it may reconnect to the network multiple times. Thus, the host node or core network can determine the times for the first node to reconnect to the network multiple times, and further, based on these times, determine different time periods. For example, each time period includes the time of one of the multiple reconnections by the first node. This allows different time periods to serve as trigger conditions for different sets of configuration information within multiple sets of configuration information.

Specifically, the direction and speed of movement of the first node can be communicated to the host node by the first node through the MT of its affiliated IAB node. For example, during the MT access process, it can be carried in the MT's access request information; such as the direction and speed of movement of the first node can be carried in message 1 (Msg 1) or MsgA in the random access procedure.

For example, consider multiple sets of configuration information, including three sets of configuration information (i.e., the first set of configuration information to the third set of configuration information). The triggering condition of the first set of configuration information is related to the first time period, the triggering condition of the second set of configuration information is related to the second time period, and the triggering condition of the third set of configuration information is related to the third time period. Assuming the first node switches to a new host node at time #1, time #2, and time #3 respectively, the host node or core network can determine the first time period based on time #1 (e.g., the first time period includes time #1). Similarly, it can determine the second time period based on time #2 and the third time period based on time #3. This ensures that the first set of configuration information takes effect when the local clock of the first node is within the first time period; the second set of configuration information takes effect when the local clock of the first node is within the second time period; and the third set of configuration information takes effect when the local clock of the first node is within the third time period.

Based on this possible implementation, multiple sets of configuration information can be triggered based on different time periods, meaning that multiple sets of configuration information take effect during different time periods. Therefore, the first node can use different configuration information for communication based on its local clock. For example, the effective period of the configuration information can be related to the time when the first node reconnects to the network after connecting to the second node. For instance, the effective period of the configuration information can include the time when the first node reconnects to the network, allowing the configuration information to take effect during the process of the first node reconnecting to the network. Compared to the scheme where the first node reacquires the configuration information every time it reconnects to the network, this reduces the signaling overhead of instructing the configuration information.

In another possible implementation, the triggering condition is location-based. That is, multiple sets of configuration information can be triggered based on different reference positions and threshold positions.

For example, each set of configuration information in the multiple sets of configuration information corresponds to a reference position and a threshold. Therefore, when the distance between the position of the first node and the reference position corresponding to a certain configuration information is less than or equal to the threshold corresponding to that configuration information, and/or when the angle between the position of the first node and the reference position corresponding to a certain configuration information is less than or equal to the threshold corresponding to that configuration information, the configuration information is triggered (i.e., the configuration information takes effect).

For example, when the triggering condition of the first set of configuration information is related to the distance between the first node and the reference position, the triggering condition of the first set of configuration information can be represented by the reference position and the first threshold; when the triggering condition of the first set of configuration information is related to the angle between the first node and the reference position, the triggering condition of the first set of configuration information can be represented by the reference position and the second threshold.

For example, the thresholds corresponding to multiple sets of configuration information can be the same or different. Specifically, the threshold can be pre-configured, or it can be a default value; in this case, the configuration information can indicate a reference position. Alternatively, the threshold can be indicated by the configuration information, in which case the configuration information can indicate both the reference position and the threshold. This allows the first node to determine the triggering condition of the configuration information based on the reference position and the threshold.

Optionally, the reference position and threshold corresponding to the configuration information can be related to the position of the first node during the process of reconnecting to the network.

For example, the host node or core network can determine the location of the first node when it reconnects to the network based on the movement speed and direction of movement of the first node and each node in the IAB network; for example, after the first node reconnects to the second node, it reconnects to the network multiple times. Thus, the host node or core network can determine the location of the first node when it reconnects to the network multiple times, and further, based on the location of the first node when it reconnects to the network multiple times, determine different reference locations. For example, the distance or angle between each reference location and the location of the first node during one of its multiple reconnections to the network is less than or equal to a threshold. This allows different reference locations to be used to determine the triggering conditions for different sets of configuration information in multiple sets of configuration information.

Specifically, the implementation of the first node reconnecting to the network, and the implementation of the host node or core network obtaining the first node's direction of movement and speed of movement, can be referred to the relevant description in one of the possible implementations above, and will not be repeated here.

For example, consider multiple sets of configuration information, including three sets of configuration information (i.e., the first set of configuration information to the third set of configuration information). The triggering condition for the first set of configuration information can be determined based on reference position #1 and threshold #1 (such as the first threshold or the second threshold). The triggering condition for the second set of configuration information can be determined based on reference position #2 and threshold #2. The triggering condition for the third set of configuration information can be determined based on reference position #3 and threshold #3. Taking the example of the first node switching to a new host node at position #1, position #2, and position #3 respectively, the host node or core network can determine the reference position #1 based on position #1. Similarly, the reference position #2 can be determined based on position #2, and the reference position #3 can be determined based on position #3, so that the first set of configuration information takes effect when the first node is at position #1; the second set of configuration information takes effect when the first node is at position #2; and the third set of configuration information takes effect when the first node is at position #3.

Based on this possible implementation, multiple sets of configuration information can be triggered based on different locations, meaning that multiple sets of configuration information take effect when the first node is in different locations. Therefore, the first node can use different configuration information for communication depending on its location. For example, the triggering condition for the configuration information can be related to the location of the first node when it reconnects to the network after connecting to the second node. For instance, the distance or angle between the reference location used for the triggering condition of the configuration information and the location of the first node when it reconnects to the network is less than or equal to a threshold, allowing the configuration information to take effect during the process of the first node reconnecting to the network. Compared to the scheme of re-acquiring configuration information every time the first node reconnects to the network, this reduces the signaling overhead of instructing the configuration information.

In another possible implementation, the triggering condition is an information-based triggering condition. That is, multiple sets of configuration information can be triggered based on different information.

For example, after the first node receives the first indication information, when the first node receives different information used to trigger the configuration information, it triggers different configuration information (that is, the configuration information corresponding to the information received by the first node (i.e. the information used to trigger the configuration information) takes effect).

For example, different information can be understood as: information with different formats; or, information from different host nodes; or, information with different content; the embodiments of this application are not limited thereto.

For example, taking multiple sets of configuration information, including three sets of configuration information (i.e., the first set of configuration information to the third set of configuration information), the first set of configuration information can be related to information #1; the second set of configuration information can be related to information #2; and the third set of configuration information can be related to information #3. Among them, information #1, information 2, and information 3 are all different from each other.

As mentioned above, during the network access process (i.e., during the establishment of the IAB-DU), the first node releases its original configuration information and acquires new configuration information. Therefore, if the first node receives information to trigger configuration information after accessing the second node, it indicates that the first node has re-accessed the network. It should be understood that the first node switches between different host nodes during its movement; this switching process can usually be considered as a network access process. Therefore, after accessing the second node, switching between different new host nodes during movement can be considered as the first node re-accessing the network during its movement. Alternatively, the first node transitions from RRC-idle to RRC-connected/inactive states. Furthermore, during the transition from RRC-idle/inactive to RRC-connected states, it needs to access a host node; therefore, the transition from RRC-idle/inactive to RRC-connected states can also be considered as the first node re-accessing the network.

For example, taking multiple sets of configuration information including three sets of configuration information (i.e., the first set of configuration information to the third set of configuration information) as an example, the first set of configuration information is related to information #1; the second set of configuration information is related to information #2; and the third set of configuration information is related to information #3. Therefore, after the first node connects to the second node, if information #1 is received, it means that the first set of configuration information is effective; if information #2 is received, it means that the second set of configuration information is effective; and if information #3 is received, it means that the third set of configuration information is effective.

Based on this possible implementation, multiple sets of configuration information can be triggered by different information. That is, each set of configuration information takes effect when the first node receives different information used to trigger the configuration. Therefore, the first node can use different configuration information for communication based on the different information received to trigger the configuration. It is understood that the original configuration information will be released and new configuration information will be acquired. Therefore, if the first node receives information used to trigger the configuration after connecting to the second node, it indicates that the first node has reconnected to the network. In other words, during the process of reconnecting to the network after connecting to the second node, the first node will acquire different information used to trigger the configuration. This allows the configuration information to take effect during the process of the first node reconnecting to the network. For example, the information used to trigger the configuration can be represented by 1 bit. Compared to the scheme where the first node resends the configuration information every time it reconnects to the network, this reduces the resource overhead of signaling indicating the configuration information.

Optionally, the coverage area of the first node can include the following two possible implementations:

In the first possible implementation, the configuration information can indicate at least one cell, where the coverage of the first node includes the coverage of the at least one cell, and the cells managed by the first node include the at least one cell.

It should be understood that an IAB node can manage one or more cells, and thus the coverage area of an IAB node can include the coverage areas of those one or more cells. Therefore, the cells managed by an IAB node are typically used to indicate the coverage area of that IAB node.

For example, the configuration information indicating at least one cell may include: an identifier indicating at least one cell. Specifically, the cell identifier may be a physical cell identifier (PCI).

For example, configuration information can indicate at least one cell through a cell list (such as a PCI list). Thus, multiple sets of configuration information can correspond to different cell lists.

In a second possible implementation, the configuration information can indicate one or more sub-regions. In this case, the coverage area of the first node includes these one or more sub-regions.

For example, one or more sub-regions can be referred to as a group of sub-regions; therefore, multiple sets of configuration information correspond to different groups of sub-regions. For ease of description, the following will use one or more sub-regions indicated by any one of the multiple sets of configuration information as an example, and will not be elaborated further here.

Optionally, the configuration information indicates one or more sub-regions, including: the configuration information indicates the reference position and threshold corresponding to one or more sub-regions respectively; wherein, the first sub-region is determined according to the reference position and threshold corresponding to the first sub-region, and the first sub-region is any one of the one or more sub-regions.

For example, the reference position and threshold corresponding to one or more sub-regions can be understood as: the reference position corresponding to one or more sub-regions, and the threshold corresponding to one or more sub-regions; that is, in one or more sub-regions, each sub-region corresponds to a reference position, and each sub-region corresponds to a threshold.

Optionally, the reference positions corresponding to different sub-regions can be the same or different; similarly, the thresholds corresponding to different sub-regions can be the same or different.

For example, the reference position and threshold corresponding to the sub-region can be implemented using a table; for instance, it can be implemented as shown in Table 1:

Table 1

Alternatively, the reference positions and thresholds corresponding to each sub-region can be implemented using sets, which may include the following: {sub-region #0; reference position #0; threshold #0}, {sub-region #1; reference position #1; threshold #1}, {sub-region #2; reference position #2; threshold #2}, {sub-region #3; reference position #3; threshold #3}, {…}. Here, the first column of the set represents each sub-region, the second column represents the reference position corresponding to each sub-region, and the third column represents the threshold corresponding to each sub-region.

Therefore, based on Table 1 or the set above, it can be seen that the reference position corresponding to sub-region #0 is reference position #0, and the threshold corresponding to sub-region #0 is threshold #0; similarly, the reference position corresponding to sub-region #1 is reference position #1, and the threshold corresponding to sub-region #1 is threshold #1; ...; the reference position corresponding to sub-region #3 is reference position #3, and the threshold corresponding to sub-region #3 is threshold #3.

For ease of description, the following example uses a table to illustrate the reference positions and thresholds corresponding to each sub-region. This will be explained uniformly here and will not be repeated.

Optionally, the configuration information can indicate the identifiers (such as the index of each sub-region) corresponding to one or more sub-regions. In this case, the first node can combine the identifiers corresponding to one or more sub-regions, as well as the correspondence between one or more sub-regions and their respective reference positions and thresholds (as shown in Table 1 above), to determine the reference position and threshold corresponding to each sub-region. For example, the configuration information can indicate sub-regions #0 to #2; in this case, the reference position corresponding to sub-region #0 is reference position #0, and the threshold corresponding to sub-region #0 is threshold #0; the reference position corresponding to sub-region #1 is reference position #1, and the threshold corresponding to sub-region #1 is threshold #1; the reference position corresponding to sub-region #2 is reference position #2, and the threshold corresponding to sub-region #2 is threshold #2.

Optionally, the distance between the reference position corresponding to the first sub-region and any position on the boundary of the first sub-region is less than or equal to the threshold corresponding to the first sub-region.

For example, the first node can draw a circular region by using the first reference position corresponding to the first sub-region as the center; this circular region is the first sub-region. The radius of the circular region can be less than or equal to the threshold corresponding to the first sub-region. That is, the distance between any position on the boundary of the circular region (i.e., the first sub-region) and the center of the circle (i.e., the reference position corresponding to the first sub-region) is less than or equal to the threshold corresponding to the first sub-region.

Optionally, the first path is the transmission path between the first and second nodes. Therefore, multiple sets of configuration information correspond to different information for the first path.

For example, the configuration information may indicate the identifier of the first path, or the configuration information may indicate the bearer information on the first path, or the configuration information may indicate the routing information of the first path.

For example, as shown in Figure 11, when the first node is located at IAB node #3 and the host node that the first node reconnects to includes host node A, taking the uplink transmission as an example, in Figure 11(a), the first path refers to: IAB node #3 → IAB node #2 → host node A; in Figure 11(b), the first path refers to: IAB node #3 → IAB node #2 → IAB node #4 → host node A.

When the host node that the first node reconnects to includes host node B, taking the uplink transmission as an example, in Figure 11(a), the first path refers to: IAB node #3 → IAB node #1 → host node B; in Figure 11(b), the first path refers to: IAB node #3 → IAB node #1 → IAB node #5 → host node B.

Optionally, multiple sets of configuration information can correspond to different address information. Therefore, when different configuration information takes effect, the address information of the first node will be different.

For example, the address information can be an Internet Protocol (IP) address or a BAP address. That is, multiple sets of configuration information can correspond to different IP addresses, or multiple sets of configuration information can correspond to different BAP addresses.

Optionally, the configuration information may indicate the paging area of the first node by indicating at least one tracking area code (TAC) and/or at least one radio access network area code (RAC (or RANAC)). That is, the configuration information indicating the paging area of the first node includes: the configuration information indicating at least one TAC, and/or the configuration information indicating at least one RAC.

The paging area of the first node includes at least one tracking area (TA) corresponding to at least one TAC, and/or the paging area of the first node includes at least one radio access network area (RA) corresponding to at least one TAC.

It should be understood that a TA consists of one or more RAs; therefore, at least one RA corresponding to a TAC can be understood as: the TA corresponding to a TAC consists of that at least one RA. In other words, a unique TA or TAC can be determined based on the RA.

For example, at least one TAC can be a set of TACs, or a collection of TACs. Similarly, at least one RAC can be a set of RACs, or a collection of RACs. Therefore, multiple sets of configuration information can correspond to different sets of TACs, and/or multiple sets of configuration information can correspond to different sets of RACs.

Based on the foregoing description of configuration information, it can be seen that, in the case of configuration information indicator, triggering condition, coverage area of the first node, information of the first path, address information of the first node, and paging area of the first node, if the coverage area of the first node is represented by a cell list, the address information of the first node is represented by an IP address or BAP address, and the paging information of the first node is represented by a TAC set and/or a RAC set, multiple sets of configuration information may include the contents shown in Table 2:

Table 2

The implementation of each parameter in Table 2 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

It should be noted that Table 2 is an exemplary implementation of multiple sets of configuration information indicated by the first indication information; in fact, multiple sets of configuration information may also include any one or more parameters in Table 2 above, that is, multiple sets of configuration information may include any one or more columns of information in Table 2 above, and this application embodiment does not limit this. For example, multiple sets of configuration information can also be regarded as a set of configuration information, or it can also be regarded as a configuration pool. Therefore, the first indication information indicating multiple sets of configuration information can be understood as: the first indication information indicates a set of configuration information or a configuration pool.

Optionally, the first indication information may also indicate the validity period of the configuration information set or configuration pool. Thus, when the local clock of the first node is within the validity period, the first node can communicate based on one set of configuration information (such as the first set of configuration information) from multiple sets of configuration information.

Optionally, the first reference signal is used for the terminal device to access the network; the second reference signal is used for any one of the IAB node, IAB-MT, or IAB-DU (such as the first node) to access the network.

For example, the first reference signal can be used for beam scanning when a terminal device accesses an IAB node; correspondingly, the second reference signal is used for beam scanning when any of the IAB node, IAB-MT, or IAB-DU (such as the first node) accesses a host node.

For example, the implementation of the first reference signal and the second reference signal may include, but is not limited to, the following:

Implementation Method 1: The first reference signal and the second reference signal are reference signals of different types. For example, the first reference signal is the synchronization signal/physical broadcast channel block (SSB (or SS/PBCH block)) synchronization signal, and the second reference signal is the handover dedicated SSB signal (called HO (handover) SSB).

The first reference signal is a periodic signal, and the period of the first reference signal is the first period. For example, the typical period of the first period is in the millisecond range, such as 5 milliseconds (ms), 10 ms, 20 ms, 40 ms, 80 ms, 160 ms, etc.

The second reference signal can be an aperiodic signal or a periodic signal. When the second reference signal is a periodic signal, its period is the second period. For example, typical periods of the second period are in the range of 1 second (s), 2s, 4s, 8s, 16s, 32s, 64s, 128s, 256s, 512s, 1024s, etc. The second period is longer than the first period.

Optionally, the first reference signal and the second reference signal differ in at least one of their time-domain position, frequency-domain position, or polarization. For example, the first reference signal and the second reference signal may differ in their time-domain position (e.g., the occupied frame, subframe, time slot, symbol, etc.), such as when the first and second reference signals can be time-division multiplexed. Another example is that the first and second reference signals may differ in their frequency-domain position, such as when the first and second reference signals can be frequency-division multiplexed, and the second reference signal does not necessarily need to be located at a pre-defined synchronization raster frequency point. Yet another example is that the first and second reference signals employ different polarization methods (e.g., linear polarization, left-hand circular polarization, right-hand circular polarization, elliptic polarization, etc.). Any two of the above three examples can be combined, or all three can be satisfied simultaneously, indicating that at least one of the time-domain position, frequency-domain position, or polarization of the first and second reference signals differs.

Optionally, the first reference signal corresponds to a predefined time-domain location, while the time-domain location of the second reference signal is variable. For example, the first reference signal corresponding to a predefined time-domain location indicates that the first reference signal has a predefined resource pattern. As another example, the second reference signal having a variable time-domain location indicates that the resource pattern of the second reference signal is variable, supporting dynamic scheduling. For instance, Table 3 shows several possible examples of the predefined resource pattern of the first reference signal, assuming that Table 3 describes the first reference signal as an SSB.

Table 3

In this table, Case A indicates that the sub-carrier space (SCS) of the SSB is 15 kHz, and the time-domain position of the first symbol of the SSB satisfies {2, 8} + 14 × n, where n is the time slot, and the maximum number of SSBs is limited. The meanings of other Cases are similar and will not be repeated here. Based on Table 3, the first node can determine the resource pattern of the first reference signal. The resource pattern of the second reference signal is variable, meaning that the resource pattern of the second reference signal is not limited to the Cases in Table 3, and can be more flexible (e.g., the position of the first symbol can be variable), which is not limited in this application.

For example, Figure 12 is a schematic diagram of a first reference signal and a second reference signal provided in this application. The first reference signal is shown as a solid box in Figure 12, and the second reference signal is shown as a dashed box in Figure 12. It is assumed that the second reference signal in Figure 12 is a periodic signal. It can be seen that the second period is greater than the first period, and the resource pattern of the first reference signal (four solid boxes) is different from the resource pattern of the second reference signal (two dashed boxes).

Optionally, the first reference signal and the second reference signal satisfy a quasi-co-address (QCL) relationship. For example, the quasi-co-address relationship between the first reference signal and the second reference signal indicates that the properties of the second reference signal can be inferred from the first reference signal.

Implementation Method 2: The first reference signal and the second reference signal are reference signals of the same type, but they are mapped to different types of time domain locations. For example, the first reference signal and the second reference signal are SSB synchronization signals, but the first reference signal is mapped to a first type of time domain location (referred to as Type-1 Occasion), and the second reference signal is mapped to a second type of time domain location (referred to as Type-2 Occasion).

The first type of time-domain location satisfies the first period. For example, the occcasion of the first reference signal mapping is periodic. The second type of time-domain location is either aperiodic or satisfies the second period. For example, when the second type of time-domain location satisfies the second period, the occcasion of the second reference signal mapping is periodic.

Specifically, the implementation of the first cycle and the second cycle can be referred to the relevant description of Implementation Method 1 above, and will not be repeated here.

Optionally, the time-domain position and frequency-domain position of the first reference signal and the second reference signal are different in at least one aspect. For example, the time-domain positions of the first reference signal and the second reference signal are different, such as when the first reference signal and the second reference signal can be time-division multiplexed. Another example is that the frequency-domain positions of the first reference signal and the second reference signal are different, such as when the first reference signal and the second reference signal can be frequency-division multiplexed. Either one of the above two examples or both can be satisfied, indicating that the time-domain position and frequency-domain position of the first reference signal and the second reference signal are different.

Optionally, the first reference signal corresponds to a predefined time-domain position, while the time-domain position of the second reference signal is variable. Specific examples can be found in the relevant descriptions in Table 3 above. For instance, based on Table 3, the first device can determine the resource pattern of the first reference signal. The variable resource pattern of the second reference signal means that the resource pattern of the second reference signal is not limited to the Case in Table 3, and can be more flexible (e.g., the position of the first symbol can be variable), which is not limited in this application.

For example, Figure 13 is a schematic diagram of another first reference signal and second reference signal provided in this application. In Figure 13, taking the first reference signal and the second reference signal as both being SSB synchronization signals as an example, the SSB shown in the dashed box is mapped to the second type of time domain position, and the SSB shown in the solid box is mapped to the first type of time domain position.

Optionally, the first reference signal and the second reference signal satisfy a quasi-co-location relationship. For example, in case two, the first reference signal and the second reference signal can be the same beam mapped to different time slots, thus exhibiting a quasi-co-location relationship.

Optionally, the first type of time-domain location and the second type of time-domain location reuse the same SSB index. For example, assuming the first reference signal and the second reference signal are the same SSB, and the same SSB maps to different types of Occasions, then the first type of time-domain location and the second type of time-domain location reuse the same SSB index (the same SSB index indicates the same SSB). Optionally, the terminal's transmission configuration indicator state (TCI state) remains unchanged during subsequent handover; for example, different types of Occasions reuse the same SSB index, and the terminal's TCI state remains unchanged during handover.

Implementation Method 3: The first reference signal is the SSB synchronization signal, and the second reference signal is another type of reference signal (such as tracking reference signal (TRS), channel state information reference signal (CSI-RS), etc.), and the second reference signal has a quasi-co-address relationship with the SSB synchronization signal.

The first reference signal is a periodic signal, and the period of the first reference signal is the first period. The second reference signal is either an aperiodic signal or a periodic signal. When the second reference signal is a periodic signal, the period of the second reference signal is the second period.

Specifically, the implementation of the first cycle and the second cycle can be referred to the relevant description of Implementation Method 1 above, and will not be repeated here.

Optionally, the first reference signal and the second reference signal differ in at least one of their time-domain position, frequency-domain position, or polarization. For example, the first reference signal and the second reference signal may differ in their time-domain position, such as by time-division multiplexing. Another example is that the first reference signal and the second reference signal may differ in their frequency-domain position, such as by frequency-division multiplexing. Yet another example is that the first reference signal and the second reference signal employ different polarization methods (such as linear polarization, left-hand circular polarization, right-hand circular polarization, elliptic polarization, etc.). Any two of the above examples can be combined, or all three can be satisfied simultaneously, indicating that the first reference signal and the second reference signal differ in at least one of their time-domain position, frequency-domain position, or polarization.

Optionally, the first reference signal corresponds to a predefined time-domain position, while the time-domain position of the second reference signal is variable. Specific examples can be found in Table 3 and Figure 12 above. For instance, based on Table 3, the first device can determine the resource pattern of the first reference signal. The variable resource pattern of the second reference signal means that the resource pattern of the second reference signal is not limited to the Case in Table 3, and can be more flexible (e.g., the position of the first symbol can be variable), which is not limited in this application.

Combining the three implementation methods described above, optionally, the first node can send the second reference signal via broadcast or multicast (e.g., the first node sends the second reference signal through the MT of its affiliated IAB node). Correspondingly, the second reference signal can be received by other nodes besides the first node (e.g., at least one third node). For ease of description, the following description uses the example of a third node receiving the second reference signal.

For example, the third node can be a ground node or a non-ground node. As shown in Figure 14, taking the first node as being located at IAB node #1 as an example, IAB node #1 can broadcast a second reference signal. Furthermore, the second reference signal is received by IAB node #2 and/or host node B. Therefore, IAB node #2 and/or host node B can be regarded as the third node.

Optionally, the third node can measure the signal quality of the second reference signal and process the measurement results (i.e., the signal quality of the second reference signal).

In one possible implementation, the third node can determine whether it needs to switch the currently connected host node (or the descendant node of the host node (i.e., the parent node of the third node)) based on the signal quality of the second reference signal. For example, if the first node is the parent node of the third node, and the signal quality of the second reference signal is poor, the third node can consider connecting to other nodes (e.g., switching to other nodes). If the first node is not the parent node of the third node (or the ancestor node of the third node), and the signal quality of the second reference signal is good, the third node can consider connecting to the first node (e.g., switching to the first node).

In one possible implementation, the third node can also inform the first node of the signal quality of the second reference signal. Thus, the first node can determine whether the signal quality of the second reference signal interferes with the communication of other nodes, and further adjust its transmission power accordingly.

Optionally, the resources used to carry the first reference signal are different from the resources used to carry the second reference signal. For example, the first and second reference signals can be carried on different random access channel (RACH) opportunities (ROs); the resources carrying the reference signals can also be called resources associated with the reference signals. Therefore, it can also be considered that the RO associated with the first reference signal is different from the RO associated with the second reference signal. As shown in Figure 15, the solid shaded box represents the RO associated with the first reference signal; the dashed shaded box represents the RO associated with the second reference signal.

Understandably, in mobile scenarios, the frequency with which terminal devices switch cells (such as IAB nodes or IAB-DUs) is significantly higher than the frequency with which IAB nodes, IAB-MTs, or IAB-DUs (such as the first node) switch their access to the host node. Therefore, for the first node, the frequency with which it sends reference signals for cell search for terminal devices is higher than the frequency with which it sends reference signals for searching for the host node; that is, the period of the SSB used for cell search is shorter.

If the SSB used for cell search is directly applied to the host node search process, the frequency of cell search is much higher than that of IAB-MT or IAB-DU (i.e., the SSB period is shorter). This causes the first node to send SSBs even when it does not need to perform host node searches, resulting in a significant waste of resources. Furthermore, it can cause interference between SSBs (e.g., it becomes impossible to distinguish whether the SSB is used for cell search or host node search).

Therefore, the first node uses the first reference signal for cell search and the second reference signal for host node search. Compared with the scheme of directly applying the SSB used for cell search to the host node search process, this can save resources. In addition, it can also avoid interference between reference signals.

Optionally, the first node may also broadcast or report its capability information to the host node (or the second node). For example, the first node may report its capability information during the process of connecting to the second node; for instance, the capability information may be carried on Msg5. Alternatively, the first node may report its capability information after connecting to the second node.

For example, the first node can indicate its capability information through the second indication information. Specifically, as shown in Figure 16, after step S1002, the communication method may further include the following step S1003:

S1003, the first node sends a second indication message to the second node, and correspondingly, the second node receives the second indication message from the first node. The second indication message indicates the capability information of the first node.

For example, when the second node is located at the host node, the first node sending the second indication information to the second node can be understood as the first node sending the second indication information to the host node it has accessed. When the second node is located at the IAB node, after receiving the second indication information, the second node can send the second indication information to its parent node until the second indication information is transmitted to the accessed host node.

Optionally, the capability information of the first node may include at least one of the following: the type of the first node, whether the IAB node to which the first node belongs supports serving child nodes, whether the first node and the MT in the IAB node to which the first node belongs support simultaneous switching, and whether the first node supports simultaneously having the functions of an IAB node and a host node. The type of the first node is either a non-ground node or a ground node. Ground nodes include stationary nodes or mobile nodes, and non-ground nodes include stationary nodes or mobile nodes.

For example, the second indication information may include at least one of the following: the type of the first node, whether the IAB node to which the first node belongs supports serving child nodes, whether the first node and the MT in the IAB node to which the first node belongs support simultaneous switching, and whether the first node supports having the functions of both an IAB node and a host node, so as to directly indicate the capability information of the first node.

Alternatively, the type of the first node may correspond to at least one of the following: whether its IAB node supports serving child nodes; whether the DU in the IAB node supports simultaneous switching; or whether it supports simultaneously having the functions of both an IAB node and a host node. For example, when the first node is a non-terrestrial node, the IAB node to which the first node belongs supports serving child nodes; the first node and the MT in the IAB node to which the first node belongs support simultaneous switching; and/or, the first node supports simultaneously having the functions of both an IAB node and a host node. When the first node is a terrestrial node, the IAB node to which the first node belongs does not support serving child nodes; the first node and the MT in the IAB node to which the first node belongs do not support simultaneous switching; and/or, the first node does not support simultaneously having the functions of both an IAB node and a host node. Therefore, the first indication information can indicate the type of the first node to indirectly indicate other characteristics of the first node (such as whether the IAB node to which the first node belongs supports serving child nodes; whether the first node and the MT in the IAB node to which the first node belongs support simultaneous switching; and whether the first node supports simultaneously having the functions of both an IAB node and a host node).

Specifically, the second indication information may include the type of the first node; alternatively, the first node may indirectly indicate its capability information by carrying information for requesting access during the network access process of its affiliated IAB node's MT, using resources that carry access request information. In this case, the second indication information is the access request information. For example, this access request information may be carried in the NTN SSB preamble.

For example, the implementation of the type of the first node can be referred to the relevant description of the type of IAB node mentioned above, and will not be repeated here.

For example, the IAB node to which the first node belongs can also be understood as: the IAB node where the first node is located. For example, if the first node is located in IAB node A, that is, the first node is DU (i.e., IAB-DU) in IAB node A, then the IAB node to which the first node belongs is IAB node A.

For example, the host node or core network can configure appropriate access resources for the IAB node to which the first node belongs, based on the type of the first node. Specifically, the access resources can be resources used to carry the preamble (such as RO). For instance, if the first node is a non-terrestrial node, dedicated access resources can be configured for the first node for the access process after the first node switches host nodes.

For example, the host node or core network can deploy a suitable IAB network topology based on whether the IAB node to which the first node belongs supports serving child nodes. For instance, if the IAB node to which the first node belongs supports serving child nodes, after the first node connects to the network, one or more child nodes can be connected to the IAB node to which the first node belongs, allowing these one or more child nodes to connect to the host node through the first node. If the IAB node to which the first node belongs does not support serving child nodes, there is no need to connect child nodes to the IAB node to which the first node belongs.

For example, the host node or core network can configure a suitable handover method for the first node based on whether the MTs in the first node and the IAB node to which the first node belongs support simultaneous handover. For instance, if the first node and the MTs in the IAB node to which the first node belongs support simultaneous handover, the host node or core network can configure the same handover trigger time and/or location for the first node and the MTs in the IAB node to which the first node belongs. Compared to the scheme where the host node or core network configures the handover trigger time and/or location for the first node and the MTs in the IAB node to which the first node belongs separately, if the first node and the MTs in the IAB node to which the first node belongs do not support simultaneous handover, this can reduce the signaling overhead of the host node or core network in indicating the handover trigger.

It should be understood that the function of an IAB node refers to the ability of an IAB node to serve at least one terminal device; therefore, the fact that the first node has the function of an IAB node means that the first node can serve at least one terminal device, that is, the IAB node to which the first node belongs can serve at least one terminal device.

The function of a host node refers to its ability to communicate with the core network through the NTN gateway. Therefore, the first node's host node function means that it can communicate with the core network through the NTN gateway. Thus, whether the first node supports simultaneously having the functions of an IAB node and a host node can be understood as whether the first node supports communicating with the core network through the NTN gateway while simultaneously serving at least one terminal device. Whether the first node supports simultaneously having the functions of an IAB node and a host node can also be referred to as whether the first node supports co-location of IAB nodes and host nodes.

For example, the host node or core network can deploy a suitable IAB network topology based on whether the first node supports the functions of both an IAB node and a host node. For instance, if the first node supports the functions of both an IAB node and a host node, the first node can act as a host node and communicate with the core network through the NTN gateway. At the same time, the first node can also provide services to at least one terminal device. If the first node does not support the functions of both an IAB node and a host node, and if the first node has the function of an IAB node, then the first node can only act as an IAB node in the IAB network and provide services to at least one terminal device. If the first node has the function of a host node, then the first node can only act as a host node in the IAB network and communicate with the core network through the NTN gateway.

In the IAB network topology shown in Figure 17 (as shown in Figure 17(a) and/or Figure 17(b)), if the first node has the function of an IAB node, the first node can be located at node A or node B in Figure 17(a) or Figure 17(b); if the first node has the function of a host node, the first node can be located at node C in Figure 17(b); if the first node supports the functions of both an IAB node and a host node, the first node can be located at node C in Figure 17(a).

For example, the above describes how the host node or core network processes the capability information of the first node when it includes different parameters (i.e., the type of the first node, whether the IAB node to which the first node belongs supports serving child nodes, whether the MT in the first node and the IAB node to which the first node belongs supports simultaneous switching, and whether the first node supports having the functions of both an IAB node and a host node). In practice, the above parameters can also be used in combination. The following describes in detail the processing procedure of the host node or core network when multiple parameters are included in the capability information.

For example, the host node or core network can configure the handover method for the child nodes of the first node based on whether the IAB node to which the first node belongs supports serving child nodes and the type of the first node. If the IAB node to which the first node belongs supports serving child nodes and the first node is a non-terrestrial node, the target host node or core network can configure a new trigger handover time and/or location for the IAB node to which the first node belongs, to trigger the handover of the child nodes of the first node after the handover of the IAB node to which the first node belongs.

And/or, the host node or core network may configure the triggering period and/or triggering event for the functions (such as IAB functions, host node functions, or whether any of the child nodes are supported) of the first node based on whether the first node supports the functions of both IAB node and host node, and whether it supports serving child nodes.

Specifically, the triggering event can be related to at least one of the following: the location of the first node, the services carried by the first node, or the latency between the first node and the target host node. For example, when the triggering event is related to the location of the first node, the triggering event is that the distance or angle between the location of the first node and the preset reference location is less than or equal to a third threshold. When the triggering event is related to the services carried by the first node, the triggering event is that the throughput of the services carried by the first node or the amount of traffic in the buffer is greater than a fourth threshold. When the triggering event is related to the latency between the first node and the target host node, the communication latency between the first node and the target host node is greater than a fifth threshold. For example, the third, fourth, and fifth thresholds can be configured for the first node by the host node or the core network.

Taking Node A and Node B as shown in Figure 17 (Figure 17(a) and/or Figure 17(b)) as examples, both Node A and Node B have the functions of IAB nodes and support service child nodes; Node C supports having the functions of both IAB nodes and host nodes, and also supports service child nodes. The first node can be located in any of Node A, Node B, or Node C. The relationship between the functions of the first node and the triggering time of that function can satisfy the relationship shown in Table 4.

Table 4

In Table 4 above, the host node or core network can be configured to trigger the IAB node function of node A in time period #1 (e.g., time period t1-t2, where t1 is less than t2, and both t1 and t2 are positive integers). That is, node A has the IAB node function during time period #1. Furthermore, during time period #1, node A may or may not support serving child nodes. In time period #2, node A may be configured to not support serving child nodes. That is, during time period #2, node A does not support serving child nodes. Furthermore, during time period #2, node A may or may not have the IAB node function.

Similarly, the host node or core network can be configured to trigger the IAB node function of node B in time period #3; furthermore, during time period #3, node B may or may not support serving child nodes. In time period #4, node B may or may not support serving child nodes; furthermore, during time period #4, node B may or may not possess the IAB node function.

The host node or core network can be configured to trigger the host node function of node C in time period #5. During time period #5, node C may or may not have the function of an IAB node. Furthermore, during time period #5, node C may or may not support service child nodes. The IAB node function of node C is triggered in time period #6. During time period #6, node C may or may not have the function of a host node. Furthermore, during time period #6, node C may or may not support service child nodes. The function of node C not supporting service nodes is triggered in time period #7. Furthermore, during time period #7, node C may or may not have the function of an IAB node and/or a host node. For example, time periods #1 to #7 may be the same or different, and this embodiment does not impose such limitations.

Taking the example that the first node can be located in any of node A, node B, or node C, the relationship between the function of the first node and the triggering event that triggers the function can satisfy the relationship shown in Table 5:

Table 5

In Table 5 above, when the host node or core network can be configured to trigger event #1, node A has the functionality of an IAB node, but node A does not support serving child nodes. Similarly, when the host node or core network can be configured to trigger event #2, node B has the functionality of an IAB node, but node B does not support serving child nodes. When the host node or core network can be configured to trigger event #3, node C has both the functionality of an IAB node and a host node, but node C does not support serving child nodes.

Events #1, #2, and #3 can be related to at least one of the following: the location of the first node, the services carried by the first node, or the latency between the first node and the target host node. Events #1, #2, and #3 can be the same or different. For details on the implementation of events #1, #2, and #3, please refer to the descriptions of the triggering events above; they will not be repeated here.

Alternatively, the functions of different nodes can be triggered by both the triggering time period and the triggering event, meaning that Tables 2 and 3 above can be combined into the content shown in Table 6:

Table 6

In Table 6 above, the host node or core network can be configured to trigger the IAB node function of node A during time period #1 when event #1 is triggered. Furthermore, during time period #1, node A may or may not support serving child nodes. During time period #2, node A may not support serving node functions; furthermore, during time period #2, node A may or may not possess IAB node functions. Similarly, the host node or core network can be configured to trigger the IAB node function of node B during time period #3 when event #2 is triggered. Furthermore, during time period #3, node B may or may not support serving child nodes. During time period #4, node B may or may not support serving node functions; furthermore, during time period #4, node B may or may not possess IAB node functions. When the target host node or core network is configured to trigger event #3, the host node function of node C will be triggered in time period #5. During time period #5, node C may or may not have the functions of an IAB node. Furthermore, during time period #5, node C may or may not support service child nodes. The IAB node function of node C will be triggered in time period #6. During time period #6, node C may or may not have the functions of a host node. Furthermore, during time period #6, node C may or may not support service child nodes. The service node function of node C will not be supported in time period #7. Furthermore, during time period #7, node C may or may not have the functions of an IAB node and/or a host node.

It should be noted that Tables 4 to 6 above exemplarily describe the relationship between the function of a node and the triggering time and/or triggering event that triggers that function. In reality, the correspondence between the function of a node and the triggering time and/or triggering event that triggers that function can also be any other possible relationship besides the above relationship. Its implementation is similar to the implementation of the relationship between the function of a node and the triggering time and/or triggering event that triggers that function in Tables 4 to 6 above. For details, please refer to the relevant descriptions in Tables 4 to 6 above, which will not be repeated here.

Based on this optional scheme, the first node can report its capability information to the host node, so that the host node or core network can configure appropriate configuration information for the first node according to the capability information, such as configuring appropriate handover methods and access resources for the first node, thereby improving the effectiveness of mobility management.

Optionally, the second indication information may also indicate the effective period of the first node's capability information and/or the effective area of the first node's capability information.

For example, taking the second indication information as also indicating the effective period and effective area of the first node's capability information, the capability information, effective period, and effective area of the first node can satisfy the relationship shown in Table 7:

Table 7

In Table 7 above, during time period #1, when the first node is located in region #1, the IAB node to which the first node belongs supports serving child nodes; during time period #2, when the first node is located in region #2, the MT of the first node and its IAB node to which it belongs supports simultaneous switching; during time period #3, when the first node is located in region #3, the first node supports having the functions of both an IAB node and a host node.

Specifically, time periods #1, #2, and #3 can be the same or different; furthermore, if time periods #1, #2, and #3 are different, there can be overlap between them. Similarly, regions #1, #2, and #3 can be the same or different; furthermore, if regions #1, #2, and #3 are different, there can be overlap between them.

Based on this optional scheme, the first node can also report the effective period and/or effective area of its capability information to the host node, so that the host node or core network can configure appropriate configuration information for the first node according to the effective period and/or effective area of the capability information; such as configuring appropriate triggering periods and/or triggering events for the first node to trigger its different functions, thereby improving the effectiveness of mobility management.

It is understood that, in the above embodiments, the methods and/or steps implemented by the first node can also be implemented by devices or components (e.g., processors, circuits, chips, or chip systems) that implement some or all of the functions of the first node; similarly, the methods and/or steps implemented by the second node can also be implemented by devices or components (e.g., processors, circuits, chips, or chip systems) that implement some or all of the functions of the first node. The chip system can be composed of chips, or it can include chips and other discrete devices.

It is understood that, in order to achieve the aforementioned functions, the communication device includes hardware structures and/or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

Figure 18 shows a schematic diagram of a communication device 1800. The communication device 1800 includes a processing module 1801 and a transceiver module 1802. The communication device 1800 can be used to implement the functions described in the first or second node above.

In some embodiments, the communication device 1800 may further include a storage module (not shown in FIG18) for storing program instructions and data.

In some embodiments, the transceiver module 1802, also referred to as a transceiver unit, is used to implement sending and/or receiving functions. The transceiver module 1802 may consist of a transceiver circuit, a transceiver, a transceiver unit, an input/output interface, or a communication interface.

In some embodiments, the transceiver module 1802 may include a receiving module and a sending module, respectively configured to perform receiving and sending steps performed by the first node or the second node in the above method embodiments, and/or other processes to support the technology described herein; the processing module 1801 may be configured to perform processing steps (e.g., determination) performed by the first node or the second node in the above method embodiments, and/or other processes to support the technology described herein.

When the communication device 1800 is used to implement the function of the first node mentioned above:

In some embodiments, the transceiver module 1802 is configured to receive first indication information, which indicates multiple sets of configuration information, each set of configuration information having different triggering conditions. The processing module 1801 is configured to perform communication based on the first set of configuration information, wherein the multiple sets of configuration information include the first set of configuration information.

Optionally, the transceiver module 1802 is also configured to receive first indication information from a second node, which is located on the host node, or the second node is located on a descendant node of the host node.

Optionally, the processing module 1801 is also used to communicate according to the first set of configuration information when the triggering conditions corresponding to the first set of configuration information are met.

Optionally, the transceiver module 1802 is also used to send second indication information, which indicates the capability information of the first node.

Optionally, the processing module 1801 is also used to communicate based on the first set of configuration information at a first moment; the transceiver module 1802 is also used to communicate based on the second set of configuration information at a second moment, wherein the multiple sets of configuration information include the second set of configuration information, and the second moment is located after the first moment.

When the communication device 1800 is used to implement the function of the second node mentioned above:

In some embodiments, the processing module 1801 is configured to determine first indication information, which indicates multiple sets of configuration information, each set of configuration information having different triggering conditions. The transceiver module 1802 is configured to send the first indication information.

Optionally, the transceiver module 1802 is also configured to receive first indication information from the parent node of the second node, wherein the parent node of the second node is located on the host node, or the parent node of the second node is located on a descendant node of the host node.

Optionally, the transceiver module 1802 is also used to receive second indication information, which indicates the capability information of the first node.

In combination with the two embodiments described above, optionally, the capability information of the first node includes at least one of the following: the type of the first node, which is either a non-ground node or a ground node; ground nodes include stationary nodes or mobile nodes; non-ground nodes include stationary nodes or mobile nodes; whether the IAB node to which the first node belongs supports serving child nodes; whether the MT in the first node and the IAB node to which the first node belongs supports simultaneous switching; and whether the IAB node to which the first node belongs supports simultaneously having the functions of both an IAB node and a host node.

In combination with the two embodiments described above, optionally, the second indication information may also indicate the effective segment of the capability information and/or the effective area of the capability information.

In combination with the above two embodiments, optionally, any one of the multiple sets of configuration information indicates at least one of the following: identifier, trigger condition, coverage area of the first node, information of the first path, address information of the first node, paging area of the first node, configuration information of the first type of reference signal, or configuration information of the second type of reference signal; wherein, the trigger condition is used to trigger the configuration information, the first path is the transmission path between the first node and the host node to which the first node is connected, the configuration information of the first type of reference signal is used to transmit the first reference signal, and the configuration information of the second type of reference signal is used to transmit the second reference signal.

In combination with the two embodiments described above, optionally, the triggering condition indicated by the first set of configuration information may include at least one of the following: the local clock of the first node is within a first time period; the distance between the first node and the reference position is less than or equal to a first threshold; the angle between the first node and the reference position is less than or equal to a second threshold.

In combination with the above two embodiments, optionally, the configuration information indicating the coverage of the first node includes: the first set of configuration information indicating at least one cell, the cells managed by the first node including at least one cell, and the coverage of the first node including the coverage of at least one cell.

In combination with the above two embodiments, optionally, the configuration information indicating the paging area of the first node includes: the configuration information indicating at least one TAC, and the paging area of the first node including at least one TA corresponding to at least one TAC; and/or, the configuration information indicating at least one RAC, and the paging area of the first node including at least one RA corresponding to at least one TAC.

In combination with the above two embodiments, optionally, the first reference signal and the second reference signal have different signal types.

Combining the two embodiments described above, optionally, the period of the first reference signal is a first period, and the second reference signal is an aperiodic signal, or the period of the second reference signal is a second period, and the second period is greater than the first period.

Combining the two embodiments described above, optionally, the first reference signal and the second reference signal satisfy a quasi-co-address relationship.

In combination with the above two embodiments, optionally, at least one of the time domain position, frequency domain position, or polarization mode of the first reference signal and the second reference signal is different.

Combining the two embodiments described above, optionally, the first reference signal corresponds to a predefined time-domain position; the time-domain position of the second reference signal is variable.

Combining the two embodiments described above, optionally, the first reference signal and the second reference signal are SSB signals; the first reference signal is mapped to a time-domain position of a first type, and the time-domain position of the first type satisfies a first period; the second reference signal is mapped to a time-domain position of a second type, and the time-domain position of the second type is non-periodic or satisfies a second period, the second period being greater than the first period.

Combining the two embodiments described above, optionally, the first type of time-domain location and the second type of time-domain location reuse the same SSB index.

In combination with the two embodiments described above, optionally, the first indication information is carried in any one of RRC signaling, F1-AP message, or Xn-AP message.

All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

In this application, the communication device 1800 can be presented in an integrated manner, divided into various functional modules. Here, "module" can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and/or other devices that can provide the above functions.

In some embodiments, when the communication device 1800 in FIG18 is a chip or chip system, the function/implementation process of the transceiver module 1802 can be implemented through the input/output interface (or communication interface) of the chip or chip system, and the function/implementation process of the processing module 1801 can be implemented through the processor (or processing circuit) of the chip or chip system.

Since the communication device 1800 provided in this embodiment can execute the above method, the technical effects it can achieve can be referred to the above method embodiment, and will not be repeated here.

As a possible product form, the first node or the second node described in the embodiments of this application can also be implemented using one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout this application.

As another possible product form, the first node or second node described in this application embodiment can be implemented using a general bus architecture. For ease of explanation, refer to FIG19, which is a schematic diagram of the structure of a communication device 1900 provided in an embodiment of this application. The communication device 1900 includes a processor 1901. The communication device 1900 can be a first node, or a chip or chip system therein; or, the communication device 1900 can be a second node, or a chip or module therein. FIG19 only shows the main components of the communication device 1900.

It is understood that the communication device 1900 includes means of the necessary form, such as modules, units, elements, circuits, or interfaces, to be appropriately configured together to perform the communication method described in this embodiment. The communication device 1900 may be an IAB node, host node, network device, terminal device, core network, or other device as shown in any of Figures 1 to 8 above, or it may be a component (e.g., a chip) within these devices, used to implement the communication method described in the above method embodiments. The communication device 1900 includes one or more processors 1901. The processor 1901 may be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (e.g., RAN node, terminal, or chip), execute software programs, and process data from the software programs.

Optionally, in one possible design, the processor 1901 may include a program 1903 (sometimes referred to as code or instructions) that can be run on the processor 1901 to cause the communication device 1900 to perform the communication method described in the above embodiments.

In another possible design, the communication device 1900 includes circuitry (not shown in FIG19) for implementing the functions described in the first or second node of the above embodiments.

Optionally, the communication device 1900 may include one or more memories 1902 storing a program 1904 (sometimes referred to as code or instructions), which can be run on the memory 1902 to cause the communication device 1900 to perform the communication method described in the above embodiments.

Optionally, the processor 1901 and/or memory 1902 may include AI modules 1907 and/or 1908, which are used to implement AI-related functions. The AI module may be implemented through software, hardware, or a combination of both. For example, the AI module may include a RIC module. For example, the AI module may be a near real-time RIC or a non-real-time RIC.

Optionally, the processor 1901 and/or memory 1902 may also store data. The processor and memory may be configured separately or integrated together.

Optionally, the communication device 1900 may further include a transceiver 1905 and/or an antenna 1906. The processor 1901, sometimes referred to as a processing unit, controls the communication device (e.g., a RAN node or terminal). The transceiver 1905, sometimes referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to realize the transmission and reception functions of the communication device through the antenna 1906.

In some embodiments, those skilled in the art will recognize that the above-described communication device 1800 can be implemented in the form of the communication device 1900 shown in FIG19.

As an example, the function/implementation of the processing module 1801 in Figure 18 can be achieved by the processor 1901 in the communication device 1900 shown in Figure 19 calling computer execution instructions stored in the memory 1902. The function/implementation of the transceiver module 1802 in Figure 18 can be achieved by the transceiver 1905 in the communication device 1900 shown in Figure 19.

As another possible product form, the first node or the second node in this application may adopt the composition structure shown in FIG20, or include the components shown in FIG20. FIG20 is a schematic diagram of the composition of a communication device 2000 provided in this application. The communication device 2000 may be a terminal device or a chip or system-on-a-chip in a terminal device; or, it may be a module, chip or system-on-a-chip in the first node or the second node.

As shown in Figure 20, the communication device 2000 includes at least one processor 2001 and at least one communication interface (Figure 20 is merely an example illustrating the inclusion of a communication interface 2004 and a processor 2001). Optionally, the communication device 2000 may also include a communication bus 2002 and a memory 2003.

Processor 2001 can be a general-purpose central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a graphics processing unit (GPU), an artificial intelligence processor (AI processor) or a neural processing unit (NPU), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. Processor 2001 can also be other devices with processing capabilities, such as circuits, devices, or software modules, without limitation.

The communication bus 2002 is used to connect different components in the communication device 2000, enabling communication between them. The communication bus 2002 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 20, but this does not indicate that there is only one bus or one type of bus.

Communication interface 2004 is used for communicating with other devices or communication networks. For example, communication interface 2004 can be a module, circuit, transceiver, or any device capable of communication. Optionally, communication interface 2004 can also be an input/output interface located within processor 2001, used to implement signal input and signal output for the processor.

Memory 2003 can be a device with storage function for storing instructions and/or data. Instructions can be computer programs.

For example, the memory 2003 may be a cache, read-only memory (ROM), or other type of static storage device capable of storing static information and/or instructions; it may also be random access memory (RAM) or other type of dynamic storage device capable of storing information and/or instructions; it may also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, without limitation.

It should be noted that the memory 2003 can exist independently of the processor 2001, or it can be integrated with the processor 2001. The memory 2003 can be located inside or outside the communication device 2000, without limitation. The processor 2001 can be used to execute the instructions stored in the memory 2003 to implement the methods provided in the following embodiments of this application.

As an optional implementation, the communication device 2000 may also include an output device 2005 and an input device 2006. The output device 2005 communicates with the processor 2001 and can display information in various ways. For example, the output device 2005 may be a liquid crystal display (LCD), a light-emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 2006 communicates with the processor 2001 and can receive user input in various ways. For example, the input device 2006 may be a mouse, keyboard, touchscreen device, or sensor device, etc.

In some embodiments, those skilled in the art will recognize that the communication device 1800 shown in FIG18 can take the form of the communication device 2000 shown in FIG20 in terms of hardware implementation.

As an example, the function/implementation of the processing module 1801 in Figure 18 can be achieved by the processor 2001 in the communication device 2000 shown in Figure 20 calling computer execution instructions stored in the memory 2003. The function/implementation of the transceiver module 1802 in Figure 18 can be achieved by the communication interface 2004 in the communication device 2000 shown in Figure 20.

It should be noted that the structure shown in Figure 20 does not constitute a specific limitation on the first node or the second node. For example, in other embodiments of this application, the first node or the second node may include more or fewer components than shown in the figure, or combine some components, or split some components, or have different component arrangements. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

In some embodiments, this application also provides a communication device, which includes a processor for implementing the methods in any of the above method embodiments.

As one possible implementation, the communication device also includes a memory. This memory stores necessary computer programs and data. The computer program may include instructions, which a processor can invoke to instruct the communication device to execute the methods described in any of the above method embodiments. Alternatively, the memory may not be present in the communication device.

As another possible implementation, the communication device also includes an interface circuit, which is a code/data read/write interface circuit, used to receive computer execution instructions (which are stored in memory and may be read directly from memory or may be transmitted through other devices) and transmit them to the processor.

As another possible implementation, the communication device also includes a communication interface for communicating with modules outside the communication device.

It is understood that the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete devices. This application does not specifically limit this.

This application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a computer, implements the functions of any of the above-described method embodiments.

This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

It is understood that the systems, apparatuses, and methods described in this application can also be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the couplings or direct couplings or communication connections shown or discussed may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

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

In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive (SSD)). In this embodiment, the computer may include the aforementioned apparatus.

Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of this application. Accordingly, this specification and drawings are merely illustrative descriptions of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims (29)

A communication method, characterized in that the method is executed by a first node, the first node being an integrated access backhaul-distributed unit (IAB-DU), the method comprising: Receive a first indication message, which indicates multiple sets of configuration information, and the triggering conditions of the multiple sets of configuration information are different; Communication is performed based on the first set of configuration information, wherein the multiple sets of configuration information include the first set of configuration information. The method according to claim 1, wherein receiving the first indication information includes: The first indication information is received from a second node, which is located at the host node, or the second node is located at a descendant node of the host node. The method according to claim 1 or 2, characterized in that the configuration information indicates the triggering condition, and the communication based on the first set of configuration information includes: If the triggering conditions corresponding to the first set of configuration information are met, communication is performed according to the first set of configuration information. The method according to any one of claims 1-3, characterized in that the method further comprises: Send a second indication message, which indicates the capability information of the first node. According to the method of claim 4, the capability information of the first node includes at least one of the following: The type of the first node is either a non-ground node or a ground node. The ground node includes a stationary node or a mobile node, and the non-ground node includes a stationary node or a mobile node. Does the IAB node to which the first node belongs support serving child nodes? Does the first node and the mobile terminal MT in the IAB node to which the first node belongs support simultaneous switching? Does the IAB node to which the first node belongs support the function of simultaneously being an IAB node and a host node? The method according to claim 4 or 5 is characterized in that the second indication information further indicates the effective segment of the capability information, and/or the effective area of the capability information. The method according to any one of claims 1-6, characterized in that, communication is performed according to the first set of configuration information, including: Communication is initiated based on the first set of configuration information at the first moment; The method further includes: Communication is performed at a second time based on a second set of configuration information, wherein the multiple sets of configuration information include the second set of configuration information, and the second time is after the first time. A communication method, characterized in that the method is executed by a second node, the method comprising: A first indication message is determined, which indicates multiple sets of configuration information, and the triggering conditions for the multiple sets of configuration information are different. Send the first instruction information. The method according to claim 8, wherein determining the first indication information includes: Receive the first indication information from the parent node of the second node, wherein the parent node of the second node is located on the host node, or the parent node of the second node is located on a descendant node of the host node. The method according to claim 8 or 9, characterized in that the method further comprises: Receive a second indication message, which indicates the capability information of the first node. According to the method of claim 10, the capability information of the first node includes at least one of the following: The type of the first node is either a non-ground node or a ground node. The ground node includes a stationary node or a mobile node, and the non-ground node includes a stationary node or a mobile node. Does the IAB node to which the first node belongs support serving child nodes? Does the first node and the mobile terminal MT in the IAB node to which the first node belongs support simultaneous switching? Does the IAB node to which the first node belongs support the function of simultaneously being an IAB node and a host node? The method according to claim 10 or 11 is characterized in that the second indication information further indicates the effective segment of the capability information, and/or the effective area of the capability information. The method according to any one of claims 1-12 is characterized in that any one of the multiple sets of configuration information indicates at least one of the following: identifier, triggering condition, coverage area of the first node, information of the first path, address information of the first node, paging area of the first node, configuration information of the first type of reference signal, or configuration information of the second type of reference signal. The triggering condition is used to trigger the configuration information. The first path is the transmission path between the first node and the host node accessed by the first node. The first type of reference signal configuration information is used to transmit the first reference signal, and the second type of reference signal configuration information is used to transmit the second reference signal. According to the method of claim 13, the triggering condition indicated by the first set of configuration information may include at least one of the following: The local clock of the first node is located within the first time period; The distance between the first node and the reference position is less than or equal to the first threshold; The angle between the first node and the reference position is less than or equal to the second threshold. The method according to claim 13 or 14, wherein the configuration information indicating the coverage area of the first node includes: The first set of configuration information indicates at least one cell, the cells managed by the first node include the at least one cell, and the coverage area of the first node includes the coverage area of the at least one cell. The method according to any one of claims 13-15, characterized in that, The configuration information indicates the paging area of the first node, including: The configuration information indicates at least one Tracking Area Code (TAC), and the paging area of the first node includes at least one Tracking Area (TA) corresponding to the at least one TAC; and/or, The configuration information indicates at least one Radio Access Network Area Code (RAC), and the paging area of the first node includes at least one Radio Access Network Area (RA) corresponding to the at least one TAC. The method according to any one of claims 13-16, wherein the first reference signal and the second reference signal have different signal types. The method according to any one of claims 13-17, wherein the period of the first reference signal is a first period, the second reference signal is an aperiodic signal or the period of the second reference signal is a second period, and the second period is greater than the first period. The method according to any one of claims 13-18 is characterized in that the first reference signal and the second reference signal satisfy a quasi-co-address relationship. The method according to any one of claims 13-19 is characterized in that at least one of the time domain position, frequency domain position or polarization mode of the first reference signal and the second reference signal is different. The method according to claim 20, characterized in that, The first reference signal corresponds to a predefined time-domain position; The time-domain position of the second reference signal is variable. The method according to any one of claims 13-21, characterized in that, The first reference signal and the second reference signal are synchronization signals/physical layer broadcast channel block (SSB) signals; The first reference signal is mapped to a time-domain position of a first type, and the time-domain position of the first type satisfies a first period; The second reference signal is mapped to a second type of time-domain location, which is either aperiodic or satisfies a second period, which is greater than the first period. The method according to claim 22 is characterized in that the time-domain locations of the first type and the time-domain locations of the second type reuse the same SSB index. The method according to any one of claims 1-23, wherein the first indication information is carried in any one of Radio Resource Control (RRC) signaling, F1-Radio Access Point (AP) message, or Xn-AP message. A communication device, characterized in that the communication device includes a transceiver module and a processing module. The transceiver module is used to perform the receiving or sending behavior in the method as described in any one of claims 1-7 and 13-24, or to perform the receiving or sending behavior in the method as described in any one of claims 8-24; The processing module is configured to perform the processing behavior in the method as described in any one of claims 1-7, 13-24, or to perform the processing behavior in the method as described in any one of claims 8-24. A communication device, characterized in that the communication device includes a processor; the processor is configured to run a computer program or instructions to cause the communication device to perform the method as described in any one of claims 1-7, 13-24, or to cause the communication device to perform the method as described in any one of claims 8-24. A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions or programs that, when executed on a computer, cause the method as described in any one of claims 1-7, 13-24 to be performed, or cause the method as described in any one of claims 8-24 to be performed. A computer program product, characterized in that the computer program product includes computer instructions; when some or all of the computer instructions are run on a computer, the method described in any one of claims 1-7, 13-24 is executed, and the method described in any one of claims 8-24 is executed. A chip, characterized in that it comprises: Memory is used to store computer program instructions; A processor for executing the computer program instructions, causing a communication device including the chip to perform the method as described in any one of claims 1-7, 13-24, and causing the communication device including the chip to perform the method as described in any one of claims 8-24.