Information sending method, information receiving method, repeater and network equipment

Abstract

Provided in an embodiment of the present application are an information sending method, an information receiving method, a repeater and a network device, the information receiving method comprising: a repeater receiving first indication information for indicating an access link beam, the first indication information comprising an information domain for indicating an access link beam and an information domain for indicating a time domain resource; the transponder adopts a first backhaul link beam to forward in the first time domain resource, and / or adopts a second backhaul link beam to forward in the second time domain resource, and / or adopts a third backhaul link beam to forward in the third time domain resource, and / or does not forward in the fourth time domain resource.

Description

Information sending method, information receiving method, repeater and network device Technical Field

[0001] The present application relates to the field of communication technology. Background Art

[0002] Compared with traditional 3G (third generation mobile communication technology) and 4G (fourth generation mobile communication technology) systems, 5G (fifth generation mobile communication technology) systems can provide larger bandwidth and higher data rates, and can support more types of terminals and vertical services.

[0003] To this end, in addition to traditional telecom spectrum, 5G systems are also being deployed on new spectrum with significantly higher frequencies than the traditional telecom spectrum used by 3G and 4G systems. For example, 5G systems can be deployed in millimeter wave bands (28 GHz, 38 GHz, 60 GHz, and above).

[0004] According to the propagation laws of wireless signals, the higher the carrier frequency, the more severe the signal fading during propagation. Therefore, in actual deployment, 5G systems require cell coverage enhancement methods even more than previous 3G and 4G systems, especially 5G systems deployed in the millimeter wave frequency band. How to better enhance 5G system cell coverage has become a pressing issue.

[0005] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0006] Summary of the Invention

[0007] To better address coverage issues in actual cellular mobile communication system deployments, RF relays (RF repeaters) are commonly used to amplify and forward communication signals between terminal devices and network equipment. RF repeaters are widely used in the deployment of 3G and 4G systems. Generally speaking, an RF repeater is a device that amplifies and forwards signals between devices in the RF domain. In other words, an RF repeater is a non-regenerative relay node that simply amplifies and forwards all received signals.

[0008] The inventors have found that one of the feasible solutions to the coverage problems encountered in the deployment of 5G systems is to use traditional radio frequency repeaters to enhance coverage. However, since the forwarding behavior of traditional radio frequency repeaters is not controlled by network devices, on the one hand, the effect of amplifying and forwarding the target signal may not be ideal, and on the other hand, it may cause significant interference to other devices in the network, increase the noise and interference level of the system, and thus reduce network throughput. Specifically, taking the antenna direction as an example, compared with 2G, 3G and 4G systems, the 5G system adopts a more advanced and complex MIMO (multiple input and multiple output) technology. In the 5G system, especially for higher carrier frequencies, directional antennas become basic components of network equipment and terminal equipment, and sending and receiving signals based on beamforming technology is the basic signal transmission method in the 5G system. The (analog) beam direction, width, etc. of network equipment and terminal equipment may change dynamically due to factors such as position changes (that is, beam switching). However, the antennas of traditional RF repeaters cannot dynamically adjust their direction and have relatively wide beams. The beam direction and beam width of their transceiver antennas cannot flexibly match the locations of base stations and terminal devices, as well as the dynamic changes in the beam direction and width of the transceiver antennas. When such RF repeaters are deployed in 5G systems, on the one hand, they may not significantly amplify or enhance the target signal due to the mismatch between the beam direction and beam width of their transceiver antennas and the dynamic changes in the beam direction and width of the transceiver antennas of network devices and terminal devices. On the other hand, the use of a wider transmit beam may also cause significant interference to other devices within a larger range (e.g., network devices or terminal devices), increasing the noise and interference level of the entire system, thereby reducing network throughput.

[0009] To enhance NR coverage, 3GPP Release 18 proposes a network-controlled repeater (NCR) solution to forward signals between network devices and terminal devices. The NCR can communicate directly with network devices via a control link to assist in NCR forwarding operations.

[0010] The inventors found that how the repeater indicates / determines the backhaul link beam has become a problem that needs to be solved urgently.

[0011] In response to at least one of the above problems, embodiments of the present application provide an information sending method, an information receiving method, a repeater, and a network device.

[0012] According to one aspect of an embodiment of the present application, a network device is provided, including:

[0013] A sending unit, which sends the first indication information and / or the second indication information and / or the third indication information and / or the fourth indication information to the forwarder, wherein:

[0014] The first indication information is used to indicate an access link beam;

[0015] The second indication information is used to indicate a backhaul link beam;

[0016] The third indication information is used to indicate a control link beam;

[0017] The fourth indication information is used to configure the first TCI state set or the second TCI state set or the first SRI set.

[0018] According to another aspect of an embodiment of the present application, a repeater is provided, including:

[0019] A mobile terminal receiving first indication information for indicating an access link beam, wherein the first indication information includes an information field for indicating the access link beam and an information field for indicating a time domain resource;

[0020] A forwarding unit that forwards using a first return link beam in a first time domain resource, and / or forwards using a second return link beam in a second time domain resource, and / or forwards using a third return link beam in a third time domain resource, and / or does not forward in a fourth time domain resource.

[0021] According to another aspect of an embodiment of the present application, a communication system is provided, comprising: the repeater of the aforementioned aspect and / or the network device of the aforementioned aspect.

[0022] One of the beneficial effects of the embodiments of the present application is that: through the indication information sent by the network device to the forwarder, the beam of the NCR during forwarding can be matched with the beam of the terminal device receiving the forwarded signal, thereby improving the effect of amplifying / enhancing the signal, while reducing interference to other devices in the network and improving network throughput.

[0023] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0024] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0025] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0027] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

[0028] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0029] FIG2 is a schematic diagram of an information receiving method according to an embodiment of the present application;

[0030] 3A to 3F are schematic diagrams of a first MAC CE according to an embodiment of the present application;

[0031] 4A to 4D are schematic diagrams of a first MAC CE according to an embodiment of the present application;

[0032] FIG5A is a schematic diagram of a fourth MAC CE according to an embodiment of the present application;

[0033] FIG5B is a schematic diagram of a fifth MAC CE according to an embodiment of the present application;

[0034] FIG6 is a schematic diagram of each DL BWP according to an embodiment of the present application;

[0035] FIG7 is a schematic diagram of each UL BWP according to an embodiment of the present application;

[0036] 8A and 8B are schematic diagrams of time domain resources according to an embodiment of the present application;

[0037] FIG9 is a schematic diagram of an information receiving method according to an embodiment of the present application;

[0038] FIG10 is a schematic diagram of an information receiving method according to an embodiment of the present application;

[0039] FIG11 is a schematic diagram of an information receiving method according to an embodiment of the present application;

[0040] FIG12 is a schematic diagram of a method for sending information according to an embodiment of the present application;

[0041] FIG13 is a schematic diagram of a transponder according to an embodiment of the present application;

[0042] FIG14 is a schematic diagram of a network device according to an embodiment of the present application;

[0043] FIG15 is a schematic diagram of an electronic device according to an embodiment of the present application;

[0044] FIG16 is a schematic diagram of a network device and an NCR forwarding signal according to an embodiment of the present application. DETAILED DESCRIPTION

[0045] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0046] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0047] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0048] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0049] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), etc., and / or other currently known or future communication protocols to be developed.

[0050] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0051] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), 5G base stations (gNB), IAB hosts, and the like. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0052] In the embodiments of the present application, the term "user equipment" (UE) refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be referred to as "terminal equipment" (TE). Terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, user, subscriber station (SS), access terminal (AT), station, etc.

[0053] Terminal devices may include, but are not limited to, cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, and the like.

[0054] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0055] In the embodiments of the present application, existing services or future services can be transmitted between the network device and the terminal device. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable low-latency communication (URLLC), and vehicle-to-everything (V2X) communication, etc.

[0056] FIG1 is a schematic diagram of an NCR according to an embodiment of the present application. As shown in FIG1 , NCR 102 is configured between network device 101 and terminal device 103. NCR 102 may include the following two modules / components: a mobile terminal (NCR-MT) of the transponder and a forwarding unit (NCR-Fwd) of the transponder; NCR-Fwd may also be referred to as a routing unit (NCR-RU) of the NCR. NCR-MT is used to communicate with network devices (exchange information), and NCR-Fwd is used to forward signals between network devices and terminal devices. NCR-MT and NCR-Fwd are functional entities, and their functions may be implemented by the same or different hardware modules.

[0057] As shown in Figure 1, the NCR of an embodiment of the present application may have three links: a control link (C-link), a backhaul link (or backhaul link, BH link) for forwarding, and an access link (AC link, also known as NCR-UE link). Among them, the C-link is used for communication between the NCR and the network device. The BH link is used for the forwarder to receive a signal to be forwarded from the network device, or to forward a signal from the terminal device to the network device. The AC link is used for the forwarder to forward a signal from the network device to the terminal device, or to receive a signal to be forwarded from the terminal device. Specifically, the NCR-MT communicates with the network device through the C-link; the NCR-Fwd forwards signals through the BH link and the AC link.

[0058] In an embodiment of the present application, a repeater can communicate with a network device. The repeater can receive a communication channel / signal sent by the network device and demodulate / decode the channel / signal to obtain information sent by the network device to the repeater. This signal processing process is hereinafter referred to as "communication". The repeater can also forward a channel / signal transmitted between a network device and a terminal device. The repeater does not demodulate / decode the channel / signal, but can perform amplification and other processing. This signal processing process is hereinafter referred to as "forwarding". "Communication" and "forwarding" are collectively referred to as "transmission". In addition, "sending or receiving on an AC (or BH) link" can be equivalent to "forwarding on an AC (or BH) link", and "sending or receiving on a control link" can be equivalent to "communicating on a control link". The above terms are for convenience of explanation only and do not constitute a limitation of this application. In some cases, "forwarding unit" can be interchangeable with "forwarding behavior".

[0059] In the embodiments of the present application, the repeater can also be expressed as a network controlled repeater (NCR), a repeater, a radio frequency repeater, a repeater, a radio frequency repeater; or it can also be expressed as a repeater node, a repeater node, a repeater node; or it can also be expressed as an intelligent repeater, an intelligent repeater, an intelligent repeater, an intelligent repeater node, an intelligent repeater node, an intelligent repeater node, etc., but the present application is not limited to this.

[0060] In an embodiment of the present application, the network device can be a device of the service cell of the terminal device, a device of the cell where the repeater is located, a device of the service cell of the repeater, or a parent node of the repeater. The present application does not impose any restrictions on the name of the repeater. As long as the device can realize the above functions, it is included in the scope of the repeater of the present application.

[0061] In the embodiment of the present application, the high-layer signaling may be, for example, radio resource control (RRC) signaling; RRC signaling may include, for example, an RRC message, such as a master information block (MIB), system information, or a dedicated RRC message; or an RRC information element (RRC information element, RRC IE); or an information field included in an RRC message or an RRC information element (or an information field included in an information field). The high-layer signaling may also be, for example, medium access control (MAC) signaling; or a MAC control element (MAC control element, MAC CE). However, the present application is not limited thereto.

[0062] In the embodiments of the present application, a plurality refers to at least two, or two or more.

[0063] In the embodiments of the present application, predefined means specified in the protocol or determined according to the rules specified in the protocol, and no additional configuration is required. Configuration / indication refers to direct or indirect configuration / indication by the network device through high-layer signaling and / or physical layer signaling. Physical layer signaling refers to, for example, control information (DCI) carried by the physical control channel or control information carried by the sequence, but is not limited to this. Configuration / indication can be achieved by introducing high-layer parameters in the high-layer signaling. High-layer parameters refer to information fields (fields) and / or information elements (IEs) in the high-layer signaling.

[0064] Rel-15 / 16 beam pointing framework:

[0065] For a serving cell, a UE can be configured with up to M TCI-State configurations in the PDSCH-Config to decode the PDSCH based on the detected PDCCH with DCI for the UE. Where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI-State includes parameters for configuring the quasi co-location relationship between the downlink reference signal and the DMRS port of the PDSCH, the DMRS port of the PDCC HD, or the CSI-RS port of the CSI-RS resource.

[0066] The UE receives an activation command (TCI States Activation / Deactivation for UE-specific PDSCH MAC CE, described below as the fourth MAC CE) for one CC / BWP or one set of CCs / BWPs. The activation command is used to map up to eight TCI states to the codepoints of the DCI field 'Transmission Configuration Indication'. When only one TCI state is activated (that is, the activation command maps the TCI-State to only one TCI codepoint), the UE shall apply the indicated TCI-State to one CC / BWP or one set of CCs / BWPs.

[0067] If only one TCI state is configured by RRC signaling, the UE directly applies that TCI state to receive PDSCH, etc., without the need for activation by the fourth MAC CE. If only one TCI state is activated by the fourth MAC CE, the UE directly applies that TCI state to receive PDSCH, etc., without the need for DCI to further indicate the TCI state for the scheduled PDSCH, etc.

[0068] Rel-17 beam pointing framework:

[0069] The UE can be configured with up to 128 TCI-State configurations by the higher-layer parameter dl-OrJoint-TCIStateList in PDSCH-Config to provide QCL for DMRS of PDSCH and DMRS of PDCCH in one BWP / CC, reference signals for CSI-RS, and a reference for determining UL TX spatial filter for PUSCH and PUCCH resources based on dynamic-grant and configured-grant, and SRS in one BWP / CC.

[0070] If TCI-State or UL-TCI-State configurations do not exist for a BWP of a CC, the UE applies the TCI-State or UL-TCI-State configurations of the reference BWP of a reference CC.

[0071] The UE receives an activation command (Unified TCI States Activation / Deactivation MAC CE (sixth MAC CE)) for one CC / BWP or for a set of CCs / BWPs, which is used to map up to 8 TCI states and / or TCI state pairs to the codepoints of the DCI field 'Transmission Configuration Indication'. When only one TCI state and / or UL-TCI-State is activated (that is, the activation command maps the TCI-State and / or UL-TCI-State to only one TCI codepoint), the UE shall apply the indicated TCI-State to one CC / BWP or for one CCs / DL BWPs set, and, where applicable, to one CC / UL BWP or one CCs / UL BWPs set.

[0072] If only one TCI state is configured by RRC signaling, the UE directly uses that TCI state to receive PDSCH, etc., without the need for activation by the sixth MAC CE. If only one TCI state is activated by the sixth MAC CE, the UE directly uses that TCI state to receive PDSCH, etc., without the need for DCI to further indicate the TCI state for the scheduled PDSCH, etc.

[0073] Currently, the standard has agreed that the NCR-Fwd's "ON" state is (implicitly) indicated by the access link beam indication. That is, during the time domain resource (time period) indicating the access link beam, the NCR-Fwd is in the ON state and can forward signals. However, the prerequisite for NCR-Fwd to forward signals during a time period is that, for that time period, the NCR has not only an indicated / determined access link beam, but also an indicated / determined return link beam, and an indicated / determined forwarding direction. If the NCR-Fwd does not have an indicated / determined return link beam and / or forwarding direction for the time domain resource indicated (implicitly) by the access link beam indication, the NCR-Fwd will essentially be unable to forward. However, how to determine and / or indicate the return link beam remains to be resolved.

[0074] In particular, when determining the backhaul link beam, there is currently no solution for how to determine the CORESET with the smallest ID and the PUCCH with the smallest (PUCCH resource) ID;

[0075] How / whether to determine the default beam when no backhaul link beam is indicated under the beam indication framework in Rel-17;

[0076] How to use MAC CE to indicate the backhaul link beam.

[0077] To address at least one of the above issues, various implementations of the present application are described below with reference to the accompanying drawings. These implementations are merely illustrative and are not intended to limit the present application.

[0078] Embodiments of the first aspect

[0079] An embodiment of the present application provides an information receiving method, which is described from the perspective of a transponder.

[0080] FIG2 is a schematic diagram of an information receiving method according to an embodiment of the present application. As shown in FIG2 , the method includes:

[0081] 201. The forwarder receives first indication information for indicating an access link beam, where the first indication information includes an information field for indicating the access link beam and an information field for indicating time domain resources.

[0082] 202. The forwarder forwards using the first return link beam in the first time domain resource, and / or forwards using the second return link beam in the second time domain resource, and / or forwards using the third return link beam in the third time domain resource, and / or does not forward in the fourth time domain resource.

[0083] It is worth noting that FIG2 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG2 above.

[0084] In some embodiments, the first indication information includes first beam indication information and / or second beam indication information, the first beam indication information is periodic access link beam indication information, and / or is carried by RRC signaling, the second beam indication information is non-periodic access link beam indication information, and / or is carried by DCI, and the following second beam indication information and DCI (carrying the second beam indication information) can be interchangeable.

[0085] (1) First beam indication information

[0086] In some embodiments, the first beam indication information may be a newly introduced information field (high-layer parameter) in RRC signaling, which includes one or more periodic beam indications (first beam indications) for an access link. Each first beam indication includes a forwarding resource list, each of which includes a fourth information field indicating an access link beam and a fifth information field for indicating time domain resources. The sixth information field includes duration information and / or offset information for time domain resources within a period. In addition, the first beam indication may also include period information (for all time domain resources indicated by the first beam indication information) and / or priority information. In addition, the first beam indication information may also include a sixth information field for indicating a first subcarrier spacing. The indicated first subcarrier spacing is for all time domain resources indicated by the first beam indication information. For example, all time domain resources indicated by the first beam indication information are associated with the first subcarrier spacing. The association includes that the duration information and / or offset information of each time domain resource is associated with the first subcarrier spacing. The time unit of the duration information and / or offset information may be milliseconds, time slots, or symbols, and its length is associated with the first subcarrier spacing. This embodiment of the present application is not limited to this.

[0087] In some embodiments, the network device may send one or more first beam indication information to the NCR, each first beam indication information including one or more of the fourth information field, the fifth information field, the sixth information field, the period information, and the priority information. For example, by configuring in a ToAddModList or other lists manner, one or more lists may be configured, wherein one list includes the above-mentioned first beam indication information, thereby supporting one or more first beam indication information.

[0088] In some embodiments, the RRC signaling includes an RRC Reconfiguration message, and / or an RRC Release message, and / or a first RRC message, where the first RRC message is an NCR-dedicated RRC message.

[0089] In some embodiments, in addition to the above-mentioned first beam indication information, the first RRC message may also include other information, such as configuration information related to the second beam indication information, such as the relevant configuration of the fourth information field and the fifth information field in the DCI in (2) (such as the time domain resource list configuration described below, etc.), but the embodiments of the present application are not limited to this.

[0090] In some embodiments, after the NCR receives the first beam indication information, it needs to receive another indication before it can start forwarding using the corresponding access link beam in the corresponding indicated time domain resources according to the first beam indication information. Alternatively, after the NCR receives the first beam indication information, it can forward using the corresponding access link beam in the corresponding indicated time domain resources according to the first beam indication information without receiving another indication.

[0091] In some embodiments, whether the NCR supports the first beam indication information is optional (may be supported or not), or mandatory (supported), or conditionally mandatory (for example, supported when conditions (for example, working frequency band FR2) are met).

[0092] (2) Second beam indication information

[0093] In some embodiments, the second beam indication information (DCI) may include one or more fourth information fields for indicating the beam and one or more fifth information fields for indicating the time domain resources. The DCI may be downlink control information having / adopting a first DCI format, and the first DCI format is used for access link beam indication. The downlink control information of the first DCI format is not used for scheduling PDSCH or PUSCH, or the downlink control information of the first DCI format may also be used for scheduling PDSCH or PUSCH. The first DCI format may be a newly introduced DCI format (egDCI format 2_8, or 2_9 or 2_10, etc.), or it may be an existing DCI format (eg1_1, or 2_0, etc.) (the existing DCI format currently also supports the functions in the embodiments of the present application), and the embodiments of the present application are not limited thereto.

[0094] In some embodiments, "downlink control information in the first DCI format" or "downlink control information using the first DCI format" or "DCI in the first DCI format" or "second beam indication information" or "DCI" can also be replaced with "first DCI format".

[0095] In some embodiments, a fourth information field is used to indicate an access link beam index, or at most one access link beam index, or multiple access link beam indexes. The access link beam index may include a beam index corresponding to an access link beam (or (actual) physical beam) and / or a beam index that does not correspond to a beam (or (actual) physical beam).

[0096] In some embodiments, the beam index range is predefined and / or configured / indicated by higher-layer signaling. For example, all beam indexes within the beam index range are predefined or configured / indicated by higher-layer signaling, or some beam indexes are predefined and some are configured / indicated by higher-layer signaling. Regarding the latter, for example, beam indexes corresponding to beams are predefined, while beam indexes not corresponding to beams are configured / indicated by higher-layer signaling, but the present invention is not limited thereto.

[0097] In some embodiments, a fifth information field is used to indicate a time domain resource index, or at most one time domain resource index, or multiple time domain resource indexes. The index may also be replaced by a sequence number.

[0098] In some embodiments, the fifth information field corresponds to a time domain resource table. The time domain resource table is predefined and / or configured by the aforementioned first RRC message or other RRC messages. The time domain resource table includes one or more time domain resource configurations. The time domain resource (TDRA) table (or simply referred to as the TDRA table) includes at least one row (column). Hereinafter, for convenience of description, a row (column) is referred to as a TDRA configuration. A TDRA configuration includes one time domain resource, multiple time domain resources, or no time domain resource. A time domain resource is continuous or discontinuous.

[0099] In some embodiments, a time domain resource is defined, for example, by one or more of the following parameters: a time slot offset K3, a symbol offset S, a length L (duration) for determining the time domain resource, and a subcarrier spacing. These parameters are predefined and / or configured by higher-layer signaling. The time slot offset K3 refers to the offset value between the starting time slot of the time domain resource or a first time slot corresponding to / overlapping / associated with the starting time slot of the time domain resource and a reference point. The reference point may be determined based on at least the time slot or symbol in which the DCI carrying the second beam indication information is located, or the time slot or symbol in which the PUCCH / PUSCH of the HARQ feedback of the DCI or PDCCH carrying the second beam indication information is located. If a time domain resource configuration includes multiple time domain resources, the reference points of the time slot offsets of different time domain resources may be the same (e.g., all determined based on at least the time slot or symbol in which the DCI carrying the second beam indication information is located) or different (e.g., for the first time domain resource: determined based on at least the time slot or symbol in which the DCI carrying the second beam indication information is located; for subsequent time domain resources, determined based on at least the time slot or symbol in which the previous time domain resource is located). The symbol offset S refers to the offset value between the first symbol of the time domain resource and the boundary / starting symbol / first symbol of the aforementioned starting time slot, or relative to the starting symbol / first symbol of the DCI or PDCCH / PDCCH MO that carries the second beam indication information. The length L of the time domain resource, for example, represents the number of symbols contained in the time domain resource. The symbol offset S and / or the length L of the time domain resource, for example, must ensure that the configured time domain resources are within the same time slot, or the configured time domain resources can be within the same time slot or across time slots. Each configuration in the time domain resource table includes the same or different number of time domain resources.

[0100] In some embodiments, the time domain resources in a configuration can be defined in the form of a list or sequence. For example, an IE is introduced, which includes the parameters for defining a time domain resource as described above. A configuration includes a list or sequence, which includes one or more fields corresponding to the above IE.

[0101] In some embodiments, the fifth information field may indicate one time domain resource, multiple time domain resources, or no time domain resource by indicating a configuration in the time domain resource table.

[0102] In some embodiments, the time domain resource index may include a time domain resource index corresponding to a time domain resource and / or a time domain resource index not corresponding to a time domain resource. For example, the time domain resource index is an index or serial number of a column (row) configuration in the time domain resource table corresponding to the fifth information field. If all configurations in the time domain resource table include time domain resources, the time domain resource index only includes the time domain resource index corresponding to the time domain resource; if the time domain resource table includes configurations that include time domain resources and configurations that do not include time domain resources, the time domain resource index includes the time domain resource index corresponding to the time domain resource and the time domain resource index not corresponding to the time domain resource. For another example, if all configurations in the time domain resource list include time domain resources, if all values ​​in the time domain resource index correspond to configurations in the time domain resource table, the time domain resource index only includes the time domain resource index corresponding to the time domain resource; if some values ​​in the time domain resource index correspond to configurations in the time domain resource table and some values ​​do not correspond to any configuration in the time domain resource table, the time domain resource index includes the time domain resource index corresponding to the time domain resource and the time domain resource index not corresponding to the time domain resource. The time domain index not corresponding to the time domain resource is, for example, predefined and / or configured by high-layer signaling.

[0103] In some embodiments, the first time domain resource and / or the second time domain resource and / or the third time domain resource and / or the fourth time domain resource are the time domain resources indicated by the first indication information, and the forwarding performed by the forwarder includes downlink forwarding and uplink forwarding. The control link performs downlink reception or uplink transmission in the first time domain resource, does not perform downlink reception and / or uplink transmission in the second time domain resource and / or the third time domain resource, and performs downlink reception or uplink transmission or does not perform downlink reception and / or uplink transmission in the fourth time domain resource.

[0104] In some embodiments, the first time domain resource and / or the second time domain resource and / or the third time domain resource and / or the fourth time domain resource have no overlap or no overlap or partially overlap with the semi-statically configured flexible symbols.

[0105] In some embodiments, the first time domain resource, the second time domain resource, the third time domain resource, and / or the fourth time domain resource overlap, completely overlap, or partially overlap with the semi-statically configured downlink symbol, and the forwarding unit of the forwarder performs downlink forwarding on all or part of the first time domain resource, the second time domain resource, the third time domain resource, and / or the fourth time domain resource. Downlink forwarding refers to receiving a downlink signal from the network (network device / gNB) (backhaul link), amplifying the signal, and transmitting it to the UE (access link).

[0106] In some embodiments, the first time domain resource and / or the second time domain resource and / or the third time domain resource and / or the fourth time domain resource overlap, completely overlap, or partially overlap with the semi-statically configured uplink symbol, and the forwarding unit of the forwarder performs uplink forwarding on all or part of the first time domain resource and / or the second time domain resource and / or the third time domain resource and / or the fourth time domain resource. Uplink forwarding refers to: receiving an uplink signal from a UE (on an access link), amplifying it, and sending it to the network (network device / gNB) (on a backhaul link).

[0107] The above semi-static configuration includes a first TDD configuration (e.g., TDD-UL-DL-ConfigCommon), and / or a second TDD configuration (e.g., TDD-UL-DL-ConfigDedicated). For example, the first and / or second TDD configuration can flexibly configure the transmission direction type for time domain resources, wherein the transmission direction type includes uplink, downlink, and flexible, wherein the second TDD configuration cannot rewrite the downlink or uplink configured by the first TDD configuration. That is, if the first TDD configuration configures a time slot or symbol as downlink (or uplink), the second TDD configuration cannot reconfigure the time slot or symbol as uplink or flexible (or downlink or flexible). Even if the second TDD configuration is configured as uplink or flexible (or downlink or flexible), it will still be based on the configuration in the first TDD configuration (still downlink (or uplink)). The second TDD configuration can rewrite the flexible configuration of the first TDD configuration to downlink or uplink. That is, if the first TDD configuration configures a time slot or symbol as flexible, or does not configure it as uplink or downlink, the second TDD configuration may configure it as downlink or uplink, and of course, may also configure it as flexible.

[0108] In some embodiments, the forwarder forwards in the first time domain resources and / or the second time domain resources and / or the third time domain resources and / or the fourth time domain resources, including forwarding in all time domain resources or part of the time domain resources of the first time domain resources and / or the second time domain resources and / or the third time domain resources and / or the fourth time domain resources.

[0109] The first backhaul link beam, the second backhaul link beam, and the third backhaul link beam are described below respectively.

[0110] In some embodiments, the first backhaul link beam, the second backhaul link beam, and the third backhaul link beam respectively include a downlink beam and an uplink beam. The downlink beam is used for downlink forwarding to receive downlink signals (to be amplified) from the network (network device / gNB), and the uplink beam is used for uplink forwarding to send uplink signals (amplified) to the network (network device / gNB).

[0111] In some embodiments, the first backhaul link beam is the same as the control link beam. For example, for a time domain resource (first time domain resource) with simultaneous downlink reception or uplink transmission in the control link and backhaul link, the backhaul link beam (first backhaul link beam) is the same as the control link beam (regardless of whether there is signaling dedicated to indicating the backhaul link beam, or whether the backhaul link beam is indicated and / or the indicated backhaul link beam is applied). The forwarder uses the first backhaul link beam for downlink reception or uplink transmission in the first time domain resource.

[0112] As previously mentioned, the current standard has agreed that NCR-Fwd should be "ON" on the time domain resources indicated by the access link beam indication (the first indication information mentioned above). This means that NCR should forward on the time domain resources indicated by the access link beam indication. However, the inventors have discovered that according to existing methods for determining / indicating backhaul link beam indication / determination, when the Rel-17 beam indication framework is used for the control link, the backhaul link beam used for forwarding is indicated by the network device, either by traditional signaling for indicating a unified TCI, or by a new MAC CE dedicated to indicating backhaul link beams. Therefore, for the Rel-17 beam indication framework, the time domain resource indicated by the access link beam indication may be located before the NCR is indicated as a backhaul link beam (or before receiving traditional signaling indicating a unified TCI and / or a new MAC CE specifically for indicating a backhaul link beam) or before the NCR applies the indicated unified TCI and / or backhaul link beam (or before applying traditional signaling indicating a unified TCI and / or an indication of a new MAC CE specifically for indicating a backhaul link beam). If the time domain resource does not have simultaneous downlink reception or uplink transmission of the control link and the backhaul link (or the time domain resource does not have downlink reception or uplink transmission of the control link), the NCR cannot perform forwarding on the time domain resource because it does not have an applicable backhaul link beam, which conflicts with the agreed-upon NCR "ON" status for the time domain resource indicated by the access link beam indication. That is, there is currently no method for how the NCR operates or how to avoid this situation. Regarding issue (I), as shown in Figure 16, the network device first sends an RRC message to the NCR, including a periodic access link beam indication and a configured unified TCI state list. After a period of time, the NCR can apply the periodic access link beam indication (time domain resources and access link beam). According to the protocol, the NCR can forward traffic on the time domain resources indicated by the access link beam indication (ON state). The network device then sends a MAC CE carrying the activation of the unified TCI and a DCI indicating the TCI state to the NCR, allowing the NCR to determine the backhaul / control link beam based on the TCI state. After a period of time, the backhaul / control link beam can be applied. In other words, the time domain resource indicated by the access link beam indication is located before the TCI state indicated for the NCR. If the NCR does not have an applicable backhaul link beam for this time domain resource, it cannot forward traffic on the time domain resource. This conflicts with the agreed-upon NCR "ON" state for the time domain resource indicated by the access link beam indication.

[0113] In order to solve the problem (1), the embodiment of the present application proposes a method for determining / indicating the return link beam (second return link beam) in this case.

[0114] In some embodiments, the second backhaul link beam is a predefined default beam including:

[0115] The beam determined by the QCL hypothesis of the CORESET with the lowest ID; and / or,

[0116] A beam determined by the spatial relationship of the PUCCH with the lowest PUCCH resource ID; and / or,

[0117] The same beam as the beam used for reception and / or transmission of the most recent / last control link; and / or,

[0118] Beam determined based on the SSB identified / selected during initial access; and / or,

[0119] The beam is determined based on the SSB identified / selected during the random access process.

[0120] For example, for a beam determined by the QCL assumption of the CORESET with the lowest ID: the CORESET with the lowest ID is the CORESET with an ID at the first DL BWP and / or the first time position. The CORESET may be CORESET#0, the first DL BWP is in the Pcell, and / or the first DL BWP is the initial DL BWP or the default DL BWP or the activated DL BWP, and the first time position includes: the latest / latter time slot in which one or more CORESETs are monitored by the NCR-MT (e.g., within the activated BWP of the serving cell (e.g., Pcell) / within the above-mentioned first DL BWP) (the latest slot in which one or more CORESETs are monitored by the NCR-MT, or the time slot in which the latest / last NCR-MT monitors (one or more) CORESETs).

[0121] For example, for the beam determined by the spatial relationship of the PUCCH with the lowest PUCCH resource ID: the PUCCH with the lowest PUCCH resource ID is the PUCCH with the lowest PUCCH resource ID at the first UL BWP and / or the second time position, the first UL BWP is in the Pcell, and / or, the first UL BWP is the initial UL BWP or the default UL BWP or the activated UL BWP, and the second time position includes: the latest / latter time slot in which PUCCH is transmitted by the NCR-MT (for example, within the activated BWP of the serving cell) (the latest slot in which PUCCH is transmitted by the NCR-MT, or the time slot in which the latest / last NCR-MT sends PUCCH).

[0122] For example, for the same beam as the beam used for receiving and / or sending the most recent / last control link, receiving the most recent / last control link includes: most recently monitoring PDCCH and / or receiving PDSCH and / or CSI-RS and / or SSB. Sending the most recent / last control link includes: most recently sending PUSCH and / or PUCCH and / or SRS.

[0123] For example, for a beam determined according to an SSB identified / selected during the initial access process or a beam determined according to an SSB identified / selected during the random access process: for downlink, determined according to the SSB identified / selected by the NCR during the initial access process or the random access process, including: the QCL assumption is based on the SSB identified / selected during the initial access process, or in other words, the same as the beam for receiving RAR during the initial access process, and / or receiving DCI / PDCCH for scheduling PUSCH (Msg.3), and / or receiving DCI / PDCCH for scheduling PDSCH (Msg.4), and / or receiving Msg.4 (or, for downlink, the above-mentioned second backhaul link (uplink) beam) and the beam for receiving RAR during the initial access process, and / or receiving DCI / PDCCH for scheduling PUSCH (Msg.3), and / or receiving DCI / PDCCH for scheduling PDSCH (Msg.4), and / or receiving Msg.4). For the uplink, the UL TX spatial filter is the same as that for the PUSCH scheduled by RAR during the initial access process or the random access process, and / or the PUSCH (Msg.3) and / or PUCCH scheduled by DCI / PDCCH (or, for the uplink, the second backhaul link (uplink) beam is the same as that used for receiving RAR during the initial access process, and / or receiving DCI / PDCCH for scheduling PUSCH (Msg.3), and / or for receiving DCI / PDCCH for scheduling PDSCH (Msg.4), and / or for receiving Msg.4). The random access process is used for initial access or beam failure recovery or RRC connection reestablishment or RRC connection recovery.

[0124] In some embodiments, different from the default defined second return link beam, the third return link beam is indicated by the second indication information for indicating the return link beam or is determined according to the third indication information for indicating the control link beam (for example, the same as the control link beam indicated by the third indication information. In this case, it can also be said that the third indication information is also used to indicate the return link beam).

[0125] For example, the second indication information is MAC signaling. The second indication information indicates the TCI state for the backhaul link from the first TCI state set, or indicates the TCI state for the backhaul link from the second TCI state set, or indicates the SRI for the backhaul link from the first SRI set. For example, when the control link applies the Rel-15 / 16 beam indication framework, for a downlink beam, the second indication information indicates the TCI state for the backhaul link from the first TCI state set, and for an uplink beam, the second indication information indicates the SRI for the backhaul link from the first SRI set. When the control link applies the Rel-17 beam indication framework, the second indication information indicates the TCI state for the backhaul link from the second TCI state set.

[0126] The second indication information is described in detail below.

[0127] In some embodiments, the second indication information includes one or more MAC CEs, such as a first MAC CE, a second MAC CE, and a third MAC CE. The first MAC CE, the second MAC CE, and the third MAC CE are different. Alternatively, the information fields or functions included in the first MAC CE, the second MAC CE, and the third MAC CE can be implemented by the same MAC CE, that is, the first MAC CE, the second MAC CE, and the third MAC CE are the same MAC CE.

[0128] For the first MAC CE

[0129] In some embodiments, a first MAC CE is used to indicate a downlink beam of a backhaul link. When the control link applies the Rel-15 / 16 beam indication framework, for the downlink beam, the second indication information indicates a TCI state for the backhaul link from a first TCI state set. The first TCI state set, for example, includes TCI states configured by all (configured) DL BWPs of a serving cell (e.g., Pcell), that is, the union of TCI States (TCI state lists) of all BWPs, for example, configured by tci-StatesToAddModList and tci-StatesToReleaseList in PDSCH-Config (i.e., configured for PDSCH) and / or configured by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList (i.e., configured for PDCCH). Alternatively, the first TCI state set, for example, includes the TCI states of one DL BWP of a serving cell (e.g., Pcell), that is, the TCI states (TCI state list) of the DL BWP configured by, for example, tci-StatesToAddModList and tci-StatesToReleaseList in PDSCH-Config (i.e., configured for PDSCH) and / or configured by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList (i.e., configured for PDCCH), that is, equal to the TCI States (TCI state list) configured by tci-StatesToAddModList and tci-StatesToReleaseList in PDSCH-Config of the DL BWP and / or configured by tci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList. The following description takes the second case as an example.

[0130] In some embodiments, the first MAC CE includes at least a first information field for indicating the TCI state (eg, TCI state ID), and includes or does not include a second information field for indicating the serving cell (eg, serving cell ID) and / or a third information field for indicating the downlink BWP (eg, BWP ID).

[0131] For example, the first MAC CE does not include the second information field for indicating the serving cell: that is, the predefined or indicated downlink BWP and / or the TCI state indicated (in the first information field) is for a predefined / default serving cell. In other words, the first MAC CE / first information field selects a TCI state or TCI state ID from the TCI state list for (specific to) the predefined / default serving cell (configuration) (that is, the first TCI state set belongs to the TCI state list for (specific to) the predefined / default serving cell (configuration)). For example, by default, the serving cell is the PCell.

[0132] For example, the first MAC CE does not include the third information field for indicating the downlink BWP: that is, the TCI state indicated by the (first information field) is predefined or a predefined / default downlink BWP of the serving cell indicated by the (second information field), or in other words, the first MAC CE / first information field selects a TCI state or TCI state ID from the TCI state list (for) the predefined / default downlink BWP (configuration) (that is, the first TCI state set belongs to the TCI state list (for) the predefined / default downlink BWP (configuration)). For example, by default, the downlink BWP is the initial downlink BWP, the default downlink BWP, the activated downlink BWP, or another specific downlink BWP.

[0133] For example, in the case where the first MAC CE includes the second information field and the third information field: the TCI state indicated by the (first information field) is the DL BWP indicated by the (third information field) in the serving cell indicated by the (second information field), or in other words, the first MAC CE / first information field selects a TCI state or TCI state ID from the TCI state list of the downlink BWP (configuration) indicated by the (third information field) in the serving cell indicated by the (second information field) (that is, the first TCI state set belongs to the TCI state list of the DL BWP indicated by the (third information field) in the serving cell indicated by the (second information field)).

[0134] In some embodiments, the first MAC CE has a variable or fixed bit size. The fixed size includes that the information field included in the first MAC CE and the number of bits included in each information field are fixed. The variable size includes that the information field included in the first MAC CE and / or the number of bits included in one or more information fields are variable. The first MAC CE may or may not include reserved bits.

[0135] The first MAC CE is illustrated below with reference to FIG. 3A to FIG. 3F . In the following examples, it is assumed that the first MAC CE includes a first information field, a second information field, and a third information field.

[0136] As shown in FIG3A , the second information field is 5 bits, the third information field is 2 bits, and the number of the first information field is variable, for example, determined by the number of TCI states in the TCI state list of the downlink BWP (configured) indicated by the (second information field) in the serving cell indicated by the (first information field). i Corresponding to the TCI state with TCI-StateId i (in the above TCI state list). i Set to 1, the corresponding TCI state is indicated, that is, the first MAC CE indicates that the backhaul link beam for the NCR is the beam corresponding to the TCI state. i Set to 0, the corresponding TCI state is not indicated. Or, when T i Set to 0, the corresponding TCI state is indicated. i If set to 1, the corresponding TCI state is not indicated. This embodiment of the present application is not limited to this. The first MAC CE can only indicate one TCI state. R is the reserved bit Reserve bit(s).

[0137] As shown in Figure 3B , the difference from Figure 3A is that the third information field is 3 bits but does not include a reserved bit. As shown in Figure 3C , the difference from Figure 3A is that the third information field is 3 bits and the first information field is 7 bits, which are used to indicate the TCI state identified by TCI-StateId. As shown in Figure 3D , the difference from Figure 3C is that the third information field is 2 bits and the reserved bits are 2 bits. As shown in Figure 3E , the difference from Figure 3C is that the first information field is 8 bits and does not include a reserved bit. As shown in Figure 3F , the difference from Figure 3E is that the third information field is 2 bits and includes a reserved bit.

[0138] In the above example, when the second information field includes 2 bits, whether the initial downlink BWP is or is not a configured downlink BWP, it is used to indicate one of the configured downlink BWPs. Therefore, if the initial downlink BWP is not a configured downlink BWP, the second information field cannot indicate the initial downlink BWP. When the second information field includes 3 bits, it is used to indicate the initial downlink BWP and / or the configured downlink BWP. Therefore, even if the initial downlink BWP is not a configured downlink BWP, the second information field can indicate the initial downlink BWP.

[0139] The following describes the first MAC CE with reference to Figures 4A to 4D . In the following examples, it is assumed that the first MAC CE does not include the second information field, but includes the first information field and the third information field. As shown in Figures 4A to 4D , the difference from Figures 3A to 3F is that the second information field is replaced with reserved bits, i.e., includes at least 5 reserved bits.

[0140] In some embodiments, the NCR also receives (one or more) TCI States activation / deactivation user-specific PDSCH MAC CEs (referred to as the fourth MAC CE). For the NCR, this MAC CE includes an information field (CORESET Pool ID) for indicating a CORESET pool, but the NCR does not expect any CORESET to be configured with a CORESET pool index coresetPoolIndex and / or the NCR ignores this information field; or, for the NCR, this MAC CE does not include an information field (CORESET Pool ID) for indicating a CORESET Pool (that is, the NCR does not expect this MAC CE to include an information field for indicating a CORESET Pool).

[0141] In some embodiments, the NCR also receives (one or more) TCI state indication user-specific PDCCH MAC CE (referred to as the fifth MAC CE). Figures 5A and 5B are schematic diagrams of the fourth MAC CE and the fifth MAC CE of an embodiment of the present application. As shown in Figures 5A and 5B, the fourth MAC CE and the fifth MAC CE include an information field (CORESET Pool ID) for indicating the CORESET pool (pool), as well as an information field for the activated TCI state and / or the indicated TCI state. Optionally, it may also include an information field for indicating the serving cell or an information field for indicating the downlink BWP ID.

[0142] In some embodiments, the TCI state indicated by the first MAC CE is or is not the TCI state activated (by the legacy MAC CE) and / or the indicated TCI state. For example, the protocol requires that the TCI state indicated by the first MAC CE must be the TCI state activated (by the fourth MAC CE, TCI States Activation / Deactivation for UE-specific PDSCH MAC CE), or the TCI state indicated by the first MAC CE must be the TCI state indicated (by the fifth MAC CE, TCI State Indication for UE-specific PDCCH MAC CE), or the TCI state indicated by the first MAC CE must be both the TCI state activated (by the fourth and fifth MAC CEs) and the indicated TCI state. Without limitation, the TCI state indicated by the first MAC CE may also be a TCI state other than the TCI state(s) activated (by the second MAC CE described later) and / or the TCI state(s) indicated (by the third MAC CE described later).

[0143] In some embodiments, the NCR (NCR-MT) is not expected to be configured with multiple serving cells. That is, the NCR is configured with only one serving cell, the Pcell. In this case, the first MAC CE may or may not include the second information field. If the first MAC CE includes an information field for indicating the serving cell, it must indicate the Pcell. That is, the value of this information field must be 0.

[0144] In some embodiments, the NCR (NCR-MT) can be configured with multiple downlink BWPs. Alternatively, the NCR does not desire multiple downlink BWPs; that is, the NCR is configured with only one downlink BWP, the initial downlink BWP. In this case, the first MAC CE may or may not include the aforementioned third information field. If the first MAC CE includes an information field for indicating the downlink BWP, it must indicate the initial downlink BWP; that is, the value of this information field must be 0.

[0145] In some embodiments, considering the case where the first MAC CE does not include the third information field, by default, the downlink BWP is, for example, an initial downlink BWP, a default downlink BWP, or an activated downlink BWP. If the downlink BWP is activated, considering the possibility of DL BWP switching, it is necessary to further determine which downlink BWP is used. Otherwise, the NCR may not correctly understand the instructions / configurations of the network device.

[0146] In some embodiments, the PDSCH carrying the first MAC CE and the DCI / PDCCH scheduling the PDSCH are transmitted in the same or different downlink BWPs. That is, the activated downlink BWP when receiving the PDSCH is the same as or different from the downlink activated BWP when receiving the DCI / PDCCH scheduling the PDSCH. If they are different, a BWP switch must have occurred during this period. If they are the same, a BWP switch may have occurred during this period. As shown in Figure 6, the PDSCH and PDCCH are in different downlink BWPs: DL BWP 0 and DL BWP 1, respectively.

[0147] In some embodiments, the DL BWP of the PDSCH carrying the first MAC CE (i.e., the active DL BWP when the PDSCH is received) is the same as or different from the active DL BWP when the TCI state indicated by the first MAC CE is applied. If they are different, a DL BWP switch must have occurred during this period. If they are the same, a DL BWP switch may have occurred during this period. As shown in Figure 6, the active DL BWPs for the PDSCH and the TCI state indicated by the first MAC CE are different, namely DL BWP 1 and DL BWP 2, respectively.

[0148] In addition, the inventors believe that if the TCI state lists configured for the different downlink BWPs are different, the TCI state determined by the NCR based on the TCI state ID indicated by the first MAC CE and the different downlink BWPs may be different (for example, the reference signals included in the TCI state are different). In other words, there is ambiguity as to which TCI state the network device indicates, and the NCR cannot uniquely determine which TCI state or reference signal to use. To address this issue, the method may further include:

[0149] NCR expects that the configured TCI state list for all DL BWPs (of the first serving cell) is the same. Or,

[0150] The NCR expects that no DL and / or UL BWP switching will occur between receiving the above-mentioned PDSCH and DCI / PDCCH, and / or, the NCR expects that no DL and / or UL BWP switching will occur between receiving the above-mentioned PDSCH and the TCI state indicated by the application, and / or the NCR expects that no DL and / or UL BWP switching will occur between receiving the above-mentioned DCI / PDCCH and the TCI state indicated by the application. Or,

[0151] (When the PDSCH and DCI / PDCCH are in different DL BWPs and / or the PDSCH and the TCI state indicated by the first MAC CE are different when the activated DL BWP is different), the TCI state is determined based on the DL BWP where the PDSCH is located, or based on the DL BWP where the DCI / PDCCH is located. In other words, the activated DL BWP refers to the activated DL BWP when receiving the PDSCH, or the activated DL BWP when receiving the DCI / PDCCH, or,

[0152] (In the case where the activated DL BWP when the above-mentioned PDSCH and the TCI state indicated by the first MAC CE are different), the TCI state is determined based on the DL BWP where the PDSCH is located, or based on the activated DL BWP when the TCI state indicated by the first MAC CE is applied. In other words, the above-mentioned activated DL BWP refers to the activated DL BWP when the PDSCH is received, or the activated DL BWP when the TCI state is applied.

[0153] Specifically, (for the case where the first MAC CE includes or does not include the third information field) if a DL BWP switch occurs after the TCI state indicated by the (first MAC CE) is applied, the NCR continues to use the TCI state for forwarding, or the NCR re-determines the TCI state based on the switched DL BWP for forwarding. For example, before the DL BWP switch, the NCR determines the TCI state based on DL BWP 0 (indicated by the third information field or determined according to the above method (when the third information field is not included), and after the DL BWP switch, the NCR re-determines the TCI state based on DL BWP 1 (the activated DL BWP after the switch) (assuming that the first information field in the above-mentioned first MAC CE indicates the corresponding TCI state ID (for) DL BWP 1 (configured)). Alternatively, the NCR expects that the above-mentioned situation (BWP switch occurs after applying the above-mentioned TCI state) will not occur, or the NCR expects that a BWP switch will not occur before receiving a new first MAC CE (or corresponding PDSCH) or receiving the DCI / PDCCH for scheduling the PDSCH.

[0154] For the second MAC CE

[0155] In some embodiments, the second MAC CE is used to indicate the uplink beam of the backhaul link. When the control link applies the Rel-15 / 16 beam indication framework, for the uplink beam, the second indication information indicates the SRI used for the backhaul link from the first SRI set. The first SRI set, for example, includes the SRIs configured by all (configured) UL BWPs of a serving cell (e.g., Pcell), that is, the union of the SRIs of all UL BWPs configured by, for example, spatialRelationInfoToAddModList and spatialRelationInfoToReleaseList (that is, configured for PUCCH). Alternatively, the first SRI set, for example, includes the SRIs configured by one UL BWP of a serving cell (e.g., Pcell), that is, the SRIs of the one UL BWP configured by, for example, spatialRelationInfoToAddModList and spatialRelationInfoToReleaseList (that is, configured for PUCCH). The following description takes the second case as an example.

[0156] In some embodiments, the second MAC CE includes a first information field for indicating an SRI (e.g., SRI ID), and may include or exclude a second information field for indicating a serving cell (e.g., serving cell ID) and / or a third information field for indicating a UL BWP (e.g., BWP ID). The second MAC CE is based on an SRI list indication configured for the PUCCH. For example, the first information field indicates the SRI for the backhaul link by indicating pucch-SpatialRelationInfoId.

[0157] For example, the second MAC CE does not include the second information field for indicating the serving cell: that is, the predefined or indicated UL BWP and / or the SRI indicated (in the first information field) is for a predefined / default serving cell. In other words, the second MAC CE / first information field selects an SRI from a first SRI set for (or for) the predefined / default serving cell (configuration) (that is, the first SRI set is for (or for) the predefined / default serving cell (configuration)). For example, by default, the serving cell is the PCell.

[0158] For example, the second MAC CE does not include the third information field for indicating the UL BWP: that is, the SRI indicated by the (first information field) is predefined or a predefined / default UL BWP of the serving cell indicated by the (second information field). In other words, the second MAC CE / first information field selects an SRI from a first SRI set for (for) the predefined / default uplink BWP (configuration) (that is, the first SRI set is for (for) the predefined / default uplink BWP (configuration)). For example, by default, the UL BWP is the initial UL BWP, or the default UL BWP, or the activated UL BWP, or another specific UL BWP.

[0159] For example, the second MAC CE includes the second information field and the third information field: the SRI indicated by the (first information field) is the UL BWP indicated by the (third information field) in the service cell indicated by the (second information field), or in other words, the second MAC CE / first information field selects an SRI from the first SRI set of the uplink BWP (configuration) indicated by the (third information field) in the service cell indicated by the (second information field) (that is, the first SRI set is the UL BWP indicated by the (third information field) in the service cell indicated by the (second information field)).

[0160] In some embodiments, the second MAC CE has a variable or fixed bit size. The fixed size includes that the information field included in the second MAC CE and the number of bits included in each information field are fixed. The variable size includes that the information field included in the second MAC CE and / or the number of bits included in one or more information fields are variable. The second MAC CE may or may not include reserved bits.

[0161] In some embodiments, the NCR (NCR-MT) is not expected to be configured with multiple serving cells. That is, the NCR is configured with only one serving cell, the Pcell. In this case, the second MAC CE may or may not include the second information field. If the second MAC CE includes an information field for indicating the serving cell, it must indicate the Pcell. That is, the value of this information field must be 0.

[0162] In some embodiments, an NCR (NCR-MT) may be configured with multiple UL BWPs. Alternatively, the NCR may not be configured with multiple UL BWPs; that is, the NCR may be configured with only one UL BWP, the initial UL BWP. In this case, the second MAC CE may or may not include the third information field. If the second MAC CE includes an information field for indicating the UL BWP, it must indicate the initial UL BWP; that is, the value of this information field must be 0.

[0163] In some embodiments, the second MAC CE may not include the third information field. By default, the UL BWP is, for example, the initial UL BWP, the default UL BWP, or the activated UL BWP. If the UL BWP is activated, considering the possibility of UL BWP switching, it is necessary to further determine the UL BWP to be used. Otherwise, the NCR may not correctly understand the instructions / configurations of the network device.

[0164] In some embodiments, the PDSCH carrying the second MAC CE and the DCI / PDCCH scheduling the PDSCH may correspond to the same or different UL BWPs. That is, the active UL BWP upon receiving the PDSCH may be the same or different from the active UL BWP corresponding to the DCI / PDCCH scheduling the PDSCH. If they are different, a UL BWP switch must have occurred during this period. If they are the same, a UL BWP switch may have occurred during this period. As shown in Figure 7, the PDSCH and PDCCH correspond to different UL BWPs: UL BWP 0 and BWP 1, respectively.

[0165] In some embodiments, the UL BWP corresponding to the PDSCH used to carry the second MAC CE may be the same as or different from the active UL BWP when the TCI state indicated by the second MAC CE is applied. If they are different, a UL BWP switch must have occurred during this period. If they are the same, a UL BWP switch may have occurred during this period. As shown in Figure 7, the active UL BWPs for the PDSCH and the SRI indicated by the second MAC CE are different, namely UL BWP 1 and UL BWP 2.

[0166] In addition, the inventors believe that if the first SRI sets configured for the different uplink BWPs are different, the SRIs determined by the NCR based on the SRI indicated by the second MAC CE and the different uplink BWPs may be different. In other words, there is ambiguity as to which SRI the network device indicates, and the NCR cannot uniquely determine which SRI to use. To address this issue, the method may further include:

[0167] NCR expects that the first SRI set configured for all UL BWPs (of the first serving cell) is the same. Or,

[0168] The NCR expects that no DL and / or UL BWP switching will occur between receiving the above-mentioned PDSCH and DCI / PDCCH, and / or, the NCR expects that no DL and / or UL BWP switching will occur between receiving the above-mentioned PDSCH and SRI indicated by the application, and / or the NCR expects that no DL and / or UL BWP switching will occur between receiving the above-mentioned DCI / PDCCH and SRI indicated by the application. Or,

[0169] (In the case where the PDSCH and DCI / PDCCH correspond to different UL BWPs (i.e., the activated UL BWPs when receiving the PDSCH and the DCI / PDCCH are different) and / or the UL BWP corresponding to the PDSCH (i.e., the activated UL BWP when receiving the PDSCH) and the activated UL BWP when the SRI indicated by the second MAC CE is applied are different), the SRI is determined based on the UL BWP corresponding to the PDSCH (i.e., the activated UL BWP when receiving the PDSCH) or based on the UL BWP corresponding to the DCI / PDCCH (i.e., the activated UL BWP when receiving the DCI / PDCCH). In other words, the activated UL BWP refers to the activated UL BWP when receiving the PDSCH, or the activated UL BWP when receiving the DCI / PDCCH, or,

[0170] (In the case where the above-mentioned PDSCH and the activated UL BWP when the SRI indicated by the second MAC CE are different), the SRI is determined based on the UL BWP corresponding to the PDSCH, or based on the activated UL BWP when the SRI indicated by the second MAC CE is applied, or in other words, the above-mentioned activated UL BWP refers to the activated UL BWP when the PDSCH is received, or the activated UL BWP when the SRI is applied.

[0171] In particular, (for the case where the second MAC CE includes or does not include the third information field) if UL BWP switching occurs after the SRI indicated by the (second MAC CE) is applied, the NCR continues to use the beam corresponding to the SRI for forwarding, or the NCR re-determines the SRI based on the UL BWP after the switch for forwarding. For example, before the UL BWP switch, the NCR determines the SRI based on UL BWP 0 (indicated by the third information field or determined according to the above method (when the third information field is not included), and after the UL BWP switch, the SRI is re-determined based on UL BWP 1 (the activated UL BWP after the switch). Alternatively, the NCR expects the above situation not to occur (BWP switching occurs after the above-indicated SRI is applied), or the NCR expects that BWP switching does not occur before receiving a new second MAC CE (or corresponding PDSCH) or receiving the DCI / PDCCH for scheduling the PDSCH.

[0172] For the third MAC CE

[0173] In some embodiments, the third MAC CE is used to indicate the uplink beam and / or downlink beam of the backhaul link. When the Rel-17 beam indication framework is applied to the control link, the second indication information indicates the TCI state for the backhaul link from a second TCI state set. The second TCI state set, for example, includes TCI states configured by all (configured) DL BWPs of a serving cell (e.g., Pcell), that is, the union of TCI States (TCI state list) configured by dl-OrJointTCI-StateToAddModList-r17 and dl-OrJointTCI-StateToReleaseList-r17 of dl-OrJointTCI-StateList in PDSCH-Config for all DL BWPs. Alternatively, the second TCI state set, for example, includes the TCI state configured by one of the DL BWPs of a serving cell (e.g., Pcell), that is, the TCI states (TCI state list) configured by dl-OrJointTCI-StateToAddModList-r17 and dl-OrJointTCI-StateToReleaseList-r17 in the PDSCH-Config of the DL BWP, that is, equal to the TCI States (TCI state list) configured by dl-OrJointTCI-StateToAddModList-r17 and dl-OrJointTCI-StateToReleaseList-r17 in the PDSCH-Config of the DL BWP. The (Unified) TCI state configured in the above dl-OrJointTCI-StateList or can be used for uplink and / or downlink, and the (unified) TCI state can be used to determine the uplink beam and / or downlink beam of the backhaul link.

[0174] In some embodiments, the third MAC CE includes a first information field for indicating the TCI state (e.g., TCI state ID), and may or may not include a second information field for indicating the serving cell (e.g., serving cell ID) and / or a third information field for indicating the DL BWP (e.g., BWP ID). Unlike the first information field of the first MAC CE, the first information field of the third MAC CE indicates the Unified TCI state, for example, indicating the TCI state for the backhaul link from the dl-OrJointTCI-StateList. Furthermore, the implementation of whether the third MAC CE includes or does not include the serving cell and BWP in the second information field and / or the third information field may refer to the first MAC CE.

[0175] In some embodiments, the third MAC CE has a variable or fixed bit size. The fixed size includes that the information field included in the third MAC CE and the number of bits included in each information field are fixed. The variable size includes that the information field included in the third MAC CE and / or the number of bits included in one or more information fields are variable. The third MAC CE may or may not include reserved bits.

[0176] In some embodiments, the TCI state indicated by the third MAC CE is or is not the TCI state activated (by the legacy MAC CE) and / or the indicated TCI state. For example, the protocol requires that the TCI state indicated by the third MAC CE must be the TCI state activated (by the fourth MAC CE, TCI States Activation / Deactivation for UE-specific PDSCH MAC CE), or the TCI state indicated by the third MAC CE must be the TCI state indicated (by the fifth MAC CE, TCI State Indication for UE-specific PDCCH MAC CE), or the TCI state indicated by the third MAC CE must be both the TCI state activated (by the fourth and fifth MAC CEs) and the indicated TCI state, or is not limited thereto.

[0177] In some embodiments, the NCR (NCR-MT) is not expected to be configured with multiple serving cells. That is, the NCR is configured with only one serving cell, the Pcell. In this case, the third MAC CE may or may not include the second information field. If the third MAC CE includes an information field for indicating the serving cell, it must indicate the Pcell. That is, the value of this information field must be 0.

[0178] In some embodiments, the NCR (NCR-MT) can be configured with multiple DL BWPs. Alternatively, the NCR does not desire multiple DL BWPs; that is, the NCR is configured with only one DL BWP, the initial DL BWP. In this case, the third MAC CE may or may not include the third information field. If the third MAC CE includes an information field for indicating the downlink BWP, it must indicate the initial DL BWP; that is, the value of this information field must be 0.

[0179] In some embodiments, to account for the possibility of downlink BWP switching, the third MAC CE does not include a third information field. By default, the DL BWP is, for example, an initial DL BWP, a default DL BWP, or an activated DL BWP. If the activated DL BWP is used, further determination of the DL BWP is necessary to account for the possibility of DL BWP switching. Otherwise, the NCR may not correctly understand the instructions / configurations of the network device.

[0180] In some embodiments, the PDSCH used to carry the third MAC CE is transmitted at the same or different DL BWP as the DCI / PDCCH that schedules the PDSCH. That is, the active BWP when receiving the PDSCH is the same as or different from the active DL BWP when receiving the DCI / PDCCH that schedules the PDSCH. And / or the BWP where the PDSCH used to carry the third MAC CE is located is the same as or different from the active DL BWP when applying the TCI state indicated by the first MAC CE.

[0181] In addition, the inventors believe that if the TCI state lists configured for the different DL BWPs are different, the TCI state determined by the NCR based on the TCI state ID indicated by the third MAC CE may be different based on the different DL BWPs (for example, the reference signals included in the TCI state are different). In other words, there is ambiguity as to which TCI state the network device indicates, and the NCR cannot uniquely determine which TCI state or reference signal to use. To address this issue, the method may further include:

[0182] NCR expects that the TCI state list configured for all BWPs (of the first serving cell) is the same. Or,

[0183] The NCR expects that no DL and / or ULBWP switching will occur between receiving the above-mentioned PDSCH and DCI / PDCCH, and / or, the NCR expects that no DL and / or ULBWP switching will occur between receiving the above-mentioned PDSCH and the TCI state indicated by the application, and / or the NCR expects that no DL and / or ULBWP switching will occur between receiving the above-mentioned DCI / PDCCH and the TCI state indicated by the application. Or,

[0184] (In the case where the PDSCH and DCI / PDCCH correspond to different DL and / or UL BWPs and / or the DL and / or UL BWPs corresponding to the PDSCH and the TCI state indicated by the third MAC CE are activated, the TCI state is determined based on the DL and / or UL BWPs corresponding to the PDSCH, or based on the DL and / or UL BWPs corresponding to the DCI / PDCCH. Or,

[0185] (In the case where the activated DL and / or UL BWPs are different between the PDSCH and the TCI state indicated by the third MAC CE, the TCI state is determined based on the DL and / or UL BWP corresponding to the PDSCH, or based on the activated BWP when the TCI state indicated by the third MAC CE is applied. In other words, the activated DL and / or UL BWP refers to the activated DL and / or UL BWP when receiving the PDSCH, or the activated DL and / or UL BWP when the TCI state is applied.

[0186] In particular, (for the case where the third MAC CE includes or does not include the third information field) if DL and / or UL BWP switching occurs after applying the TCI state indicated by the (third MAC CE), the NCR continues to use the TCI state for forwarding, or the NCR re-determines the TCI state based on the switched DL and / or UL BWP and then forwards. For example, before the DL and / or UL BWP is switched, the NCR determines the TCI state according to DL and / or UL BWP 0 (indicated by the third information field or determined according to the above method (when the third information field is not included), and after the DL and / or UL BWP is switched, the NCR re-determines the TCI state according to DL and / or UL BWP 1 (the activated DL and / or UL BWP after the switch) (assuming that the first information field in the above third MAC CE indicates the corresponding TCI state ID (for) DL and / or UL BWP 1 (configured)). Alternatively, the NCR expects that the above situation does not occur (DL and / or UL BWP switching occurs after applying the above indicated TCI state), or the NCR expects that DL and / or UL BWP switching does not occur before receiving a new third MAC CE (or corresponding PDSCH) or receiving the DCI / PDCCH for scheduling the PDSCH.

[0187] In some embodiments, the second TCI set includes, for example, an uplink TCI state configured for a serving cell. For example, it includes all (configured) UL BWPs of a serving cell (e.g., a PCell) or one of the UL BWPs, for example, UL TCI states configured by ul-TCI-ToAddModList. This application is not limited to this. The third MAC CE may also indicate a TCI state for the backhaul link from the second TCI set including the uplink TCI state. The specific indication method is similar to that in the aforementioned embodiment and is not further described here.

[0188] As mentioned above, the third return link beam can also be determined based on the third indication information used to indicate the control link beam, and the third indication information indicates the Unified TCI state. For example, for NCR, the unified TCI State type must indicate uplink and downlink joint (joint) or can indicate uplink and downlink joint (joint) or independent (separate), where independent indicates that the serving cell is configured with the dl-OrJointTCI-StateList of the downlink TCI state and the ul-TCI-ToAddModList of the uplink TCI state. Joint indicates that the serving cell is configured with the dl-OrJointTCI-StateList of the uplink and downlink joint TCI state.

[0189] In some embodiments, in 202, the second time domain resource is forwarded using the second backhaul link beam, including: before the second time domain resource is indicated or determined to have the third backhaul link beam and / or the third backhaul link is applied, or when the second time domain resource does not have the third backhaul link beam, the second time domain resource is forwarded using the second backhaul link beam.

[0190] For example, for the Rel-17 beam indication framework: for (time domain resources) that do not have a third backhaul link beam, the second backhaul link beam is used for forwarding in the second time domain resource. Not having a third backhaul link beam means that there is no available third backhaul link beam. The time domain resource is indicated or determined before the third backhaul link beam and / or the third backhaul link is applied. If the NCR does not support the second indication information, the second backhaul link beam is used for forwarding before the TCI state is indicated by (the third indication information) and / or the indicated TCI state is applied. If the NCR supports the second indication information, the second backhaul link beam is used for forwarding before the third backhaul link beam and / or the indicated third backhaul link beam is indicated by (the second indication information) and / or the indicated third backhaul link beam is applied and before the TCI state and / or the indicated TCI state is indicated by (the third indication information) (or before the third backhaul link is determined according to the third indication information).

[0191] In some embodiments, in 202, the third time domain resource using a third backhaul link beam for forwarding includes: after the third time domain resource is indicated or determined to have the third backhaul link beam and / or the third backhaul link is applied, or when the third time domain resource has the third backhaul link beam, the third time domain resource using the third backhaul link beam for forwarding. The first time domain resource is forwarded whether or not the third backhaul link beam is indicated or determined to have the third backhaul link beam and / or the third backhaul link is applied.

[0192] Figures 8A and 8B are schematic diagrams of time domain resources of an embodiment of the present application. As shown in Figure 8A, for the first beam indication, PDSCH1 carries an access link beam indication, indicating the second time domain resources and the third time domain resources, and uses the second backhaul link beam forwarding on the second time domain resources. PDSCH2 carries a backhaul link beam indication, and on the third time domain resources, the backhaul link beam forwarding indicated by PDSCH2 is used; as shown in Figure 8B, for the second beam indication, DCI1 carries an access link beam indication, indicating the second time domain resources and the third time domain resources, and uses the second backhaul link beam forwarding on the second time domain resources. PDSCH2 carries a backhaul link beam indication, and on the third time domain resources, the backhaul link beam forwarding indicated by PDSCH2 is used.

[0193] In some embodiments, after the NCR receives an initial higher-layer configuration dl-OrJoint-TCIStateList with multiple TCI states, and before applying the indicated TCI from the configured TCI state: the NCR assumes that the DL signal / channel (e.g., the DM-RS of the PDSCH and the DM-RS of the PDCCH and the CSI-RS to which the indicated TCI state is applied) is quasi-co-located with the SS / PBCH block identified by the UE during the initial access process.

[0194] In some embodiments, after the NCR receives an initial higher layer configuration dl-OrJoint-TCIStateList with multiple DL TCI states and multiple UL TCI states, and before applying the indicated TCI from the configured TCI states: the NCR assumes that the UL TX spatial filters (of the spatial link and / or backhaul link) are the same as the spatial filters of the PUSCH transmissions scheduled by the RAR UL grant during the initial access procedure.

[0195] In some embodiments, in 202, not forwarding in the fourth time domain resource includes: not forwarding in the fourth time domain resource before the third backhaul link beam is indicated or determined and / or the third backhaul link is applied, or when the fourth time domain resource does not have the third backhaul link beam. The control link performs downlink reception or uplink transmission or does not perform downlink reception and / or uplink transmission in the fourth time domain resource.

[0196] Therefore, the indication information sent by the network device to the repeater enables the beam of the NCR during forwarding to match the beam of the terminal device receiving the forwarded signal, thereby improving the effect of amplifying / enhancing the signal, while reducing interference to other devices in the network and improving network throughput.

[0197] The above problem (1) can be solved by defining a default second backhaul link beam. The embodiment of the present application also provides a method for solving this problem. FIG9 is a schematic diagram of the information receiving method of the embodiment of the present application. As shown in FIG9, from the perspective of the forwarder, the method includes:

[0198] 901. A forwarder receives first indication information for indicating an access link beam, where the first indication information includes an information field for indicating a beam and / or an information field for indicating a time domain resource.

[0199] 902. Before being instructed to use the third backhaul link beam and / or applying the third backhaul link beam, the forwarder does not forward.

[0200] In some embodiments, for the Rel-17 beam indication framework: no forwarding is performed for time domain resources that do not have a third backhaul link beam.

[0201] For example, if the NCR does not support the second indication information, no forwarding is performed before the TCI state and / or the TCI state indicated by the application is indicated by the (third indication information). If the NCR supports the second indication information, no forwarding is performed before the third backhaul link beam and / or the third backhaul link beam indicated by the (second indication information) and before the TCI state and / or the TCI state indicated by the application is indicated by the (third indication information) (or before the third backhaul link is determined according to the third indication information).

[0202] In some embodiments, before being instructed about the third backhaul link beam and / or applying the third backhaul link beam, not forwarding includes: the NCR not applying the first indication information.

[0203] An embodiment of the present application also provides an information processing method, which is described from the forwarder side. The method includes: the forwarder does not (expects to) receive the first indication information and / or apply the first indication information before being instructed to use the third return link beam and / or apply the third return link beam.

[0204] Thus, the time domain resources indicated by the access link beam indication may be located before the time domain resources corresponding to the backhaul link beam indicated by the network device or the NCR applying the backhaul link beam indicated by the network device. The forwarder does not forward the signal, or does not receive the first indication information and / or apply the first indication information, which can avoid conflict with the "ON" state protocol of the NCR Fwd.

[0205] The present application also provides an information receiving method, which is described from the perspective of a transponder. FIG10 is a schematic diagram of the information receiving method according to the present application. As shown in FIG10 , the method includes:

[0206] 1001. The forwarder receives first indication information for indicating an access link beam, and / or receives second indication information for indicating a backhaul link beam, wherein the second indication information indicates a TCI state for the backhaul link from a first TCI state set, or indicates a TCI state for the backhaul link from a second TCI state set, or indicates an SRI for the backhaul link from a first SRI set.

[0207] In some embodiments, the implementation of the first indication information and the second indication information may refer to the above embodiments. The application time / switching delay of the first indication information and the second indication information is described below.

[0208] In some embodiments, for the first indication information (first beam indication) carried by RRC signaling, the first indication information is applied from a third time position.

[0209] For example, the NCR (NCR-Fwd) (is expected / should) (can be able to) apply the (first) beam indicated by the (first beam indication) from the third time position (forward), or apply the beam indication. Before this, the NCR needs or does not need to forward.

[0210] The third time position is described below: the third time position is related to the RRC processing delay (RRC processing delay) (used to carry / send the RRC message of the indication) and / or the time domain resources indicated (first indication information) and / or HARQ (HARQ-ACK feedback, confirmation message), or depends on the RRC processing delay and / or the indicated time domain resources.

[0211] For example, the third time position is:

[0212] Time slot slot n+T RRC_processing / NR slot length or or the first time slot after the next time slot between the first two, or

[0213] Time slot slot n+T RRC_processing / NR slot length or or the first time domain resource indicated by (first indication information) after the next time slot between the first two, or

[0214] Time slot slot n+T RRC_processing / NR slot length or Or the first time slot after the latter time slot between the first two including the time domain resources indicated by (the first indication information).

[0215] in, Indicates the number of time slots of subcarrier u included in a subframe, that is, the length is equivalent to the length of 1 subframe, T RRC_processing RRC processing delay (RRC processing delay of the RRC message used to carry / send the indication). HARQThe time between downlink data transmission and acknowledgment. The downlink data transmission refers to the PDSCH used to carry the RRC message or indication, and the acknowledgment refers to the HARQ-ACK for that PDSCH. THARQ extends to the time until the next HARQ feedback transmission and retransmission opportunity, until the time of successful transmission.

[0216] Slot n is the (last) timeslot in which the PDSCH carrying the RRC message resides, or the (last) (uplink / downlink) timeslot that overlaps with the PDSCH carrying the RRC message. In the latter case, the subcarrier spacing of Slot n and the PDSCH carrying the RRC message are the same or different. The subcarrier spacing of Slot n is the same or different from the subcarrier spacing of the NR slot (in NR slot length).

[0217] The subcarrier spacing of the above-mentioned time slot (Slot n / NR slot) is the following subcarrier spacing or is related to the following subcarrier spacing (for example, determined based on the following subcarrier spacing):

[0218] The subcarrier spacing of the PDSCH used to send / carry the above RRC message or indication, and / or,

[0219] The subcarrier spacing of the PUSCH / PUSCH used for sending / carrying the HARQ-ACK of the PDSCH indicated by the RRC message or indication.

[0220] When T HARQ Greater than T RRC_processing When , a longer switching delay is allowed.

[0221] In some embodiments, for the first indication information (second beam indication) carried by the DCI, the first indication information is applied from a fourth time position.

[0222] For example, the NCR (NCR-Fwd) (is expected / should) (can be able to) apply the (first) beam indicated by the (second beam indication) from the fourth time position (forwarding), or apply the beam indication.

[0223] The fourth time position is described below:

[0224] slot n+timeDurationForQCL or The first time slot after, or

[0225] slot n+timeDurationForQCL or The first time domain resource indicated by (the second indication information) after

[0226] slot n+timeDurationForQCL or The first time slot after that includes the time domain resources indicated by (the first indication information).

[0227] The processing time timeDurationForQCL represents the time required by the UE to perform PDCCH reception and applying the indication / AC-link beams received in DCI for forwarding.

[0228] Time slot Slot n is the (last) time slot in which the PDCCH / DCI carrying the first indication information is located, or time slot Slot n is the (last) (downlink / uplink) time slot overlapping with the PDCCH / DCI carrying the first indication information. In the latter case, the subcarrier spacing of time slot Slot n and the PDSCH carrying the RRC message is the same as or different from that of the PDSCH.

[0229] The subcarrier spacing of the above-mentioned time slot (Slot n / NR slot) is the following subcarrier spacing or is related to the following subcarrier spacing (for example, determined based on the following subcarrier spacing):

[0230] The subcarrier spacing of the PDSCH used to transmit / carry the above RRC message, and / or,

[0231] The subcarrier spacing of the PUSCH / PUSCH used for the HARQ-ACK of the PDSCH that sends / carries the above RRC message,

[0232] In some embodiments, the backhaul link beam indicated by the second indication information is applied from a fifth time position.

[0233] For example, the NCR (NCR-Fwd) (is expected / should) (can be able to) apply the backhaul link beam indicated by (the second indication information) (forward) from the fifth time position, or apply the beam indication.

[0234] The fifth time position is described below: or or The first time slot after, or

[0235] or or The first time domain resource indicated by (the second indication information) after

[0236] or or The first time slot after that includes the time domain resources indicated by (the first indication information).

[0237] in, and T HARQ As previously mentioned, when the target TCI state is known, upon receiving the PDSCH carrying the MAC CE activation command in time slot n, the NCR can receive the PDCCH with the target TCI state of the serving cell, where the TCI state switch occurs in time slot The first time slot after

[0238] T first-SSB is the time of the first SSB transmission opportunity after MAC CE; T SSB It is the SSB sending period of the serving cell;

[0239] L MAC,known ≤L MAC,known,max is the number of corresponding SSB opportunities that are unavailable at the NCR; where L MAC,known,max =2, T SSB ≤40ms; or, L MAC,known,max =1, T SSB >40ms.

[0240] Wherein, when the target TCI state is unknown, upon receiving the PDSCH carrying the MAC CE activation command in time slot n, the NCR can receive the PDCCH with the target TCI state of the serving cell, wherein the TCI state switching occurs in time slot The first time slot after

[0241] By clarifying the application time of the first indication information and the second indication information, the time when the NCR forwards can match the time of the terminal device receiving the forwarded signal, thereby improving the effect of amplifying / enhancing the signal, while reducing interference to other devices in the network and improving network throughput.

[0242] The present application also provides an information receiving method, which is described from the perspective of a transponder. FIG11 is a schematic diagram of the information receiving method according to the present application. As shown in FIG11 , the method includes:

[0243] 1101. A forwarder receives fourth indication information for configuring a first TCI state set, a second TCI state set, or a first SRI set.

[0244] When the first TCI state set or the second TCI state set or the first SRI set includes only one TCI state or SRI, the third indication information for indicating the backhaul link beam is received or not received.

[0245] In some embodiments, the NCR supports the third indication information. Regarding how the fourth indication information configures the first TCI state set or the second TCI state set or the first SRI set, please refer to the aforementioned embodiment and will not be repeated here.

[0246] In some embodiments, the method may further include: 1102, the NCR uses the beam corresponding to the one TCI state and / or SRI for forwarding.

[0247] At least for the above problem (I)

[0248] The embodiment of the present application further provides the following forwarding control method (not shown), which includes:

[0249] When the NCR is indicated with a return link beam and there is no indicated / determined / available access link beam, the indicated return link beam and / or the indication command for indicating the return link beam are invalid or ineffective, and / or the NCR (NCR-Fwd) turns off or does not forward or ignores the indication command for indicating the return link beam, or,

[0250] After the NCR receives an indication command for indicating a return link beam and is then indicated to indicate an access link beam, or before the received access link beam indication is applied / valid, the indication command is not valid / applied, and / or the NCR (NCR-Fwd) closes or does not forward or ignores the indication command; or,

[0251] For a time domain resource, when the NCR determines the return link beam and there is no available access link beam, the determined return link beam is invalid or ineffective, and / or the NCR (NCR-Fwd) is closed or not forwarded, and / or the NCR does not determine the return link beam corresponding to the time domain resource; or,

[0252] For a time domain resource, when the NCR is indicated an access link beam, the NCR must / should have an indicated or determined backhaul link beam, or the NCR expects to receive a backhaul link beam indication indicating a backhaul link beam for the time domain resource, and / or the NCR determines the backhaul link beam; or,

[0253] When the NCR receives an access link beam indication command, and the access link beam indicated by the indication command is related to a time domain resource, when the NCR cannot determine the return link beam related to the time domain resource, the NCR (NCR-Fwd) closes or does not forward or consider the access link beam indication command.

[0254] In some embodiments, if the NCR is indicated with a BH-link beam (for example, by an indication command indicating a backhaul link beam, such as a MAC CE, which may be the aforementioned second indication information), (for a time domain resource), if there is no indicated / determined / available access link beam (in the time domain resource), then the indicated BH-link beam (or the corresponding indication command) is invalid or ineffective, and / or the NCR (NCR-Fwd) is closed or not forwarded or the indication command is ignored.

[0255] In some embodiments, if the NCR receives an indication command indicating a return link beam, such as a MAC CE, and is then indicated an access link beam (or has not yet received (periodic / semi-static ((dedicated) RRC signaling, such as the aforementioned first beam indication information) or non-periodic / dynamic (DCI), such as the aforementioned second beam indication information) access link beam indication), or, before the received access link beam indication is applied / takes effect, the indication command indicating the return link beam is not effective / is not applied, and / or, the NCR (NCR-Fwd) turns off or does not forward or ignores the indication command.

[0256] In some embodiments, for a time domain resource, if the NCR determines the BH-link beam (according to predefined rules), if there is no available access link beam (indicated / determined access link beam), the determined BH-link beam is invalid or ineffective, and / or the NCR (NCR-Fwd) is closed or not forwarded, and / or the NCR does not determine the BH link beam corresponding to the time domain resource (for example, determined in accordance with predefined rules or determined based on the received BH link beam indication).

[0257] In some embodiments, for a time domain resource (where C-link is transmitting or not transmitting), if the NCR is indicated with an access link beam, the NCR must / should have a BH-link beam indicated or determined (according to predefined rules). That is, for the above-mentioned time domain resource where an access link beam is indicated, the NCR (supporting BH-link beam indication) expects to receive a BH-link beam indication (BH-link beam command, MAC CE, such as the aforementioned second indication information) for indicating the BH-link beam for the time domain resource, and / or (in the event that the above-mentioned BH-link beam indication is not received or the NCR does not support BH-link beam indication or C-link is transmitting or receiving), the NCR (must / is expected) to determine (according to predefined rules) the BH-link beam (for the time domain resource).

[0258] In some embodiments, if the NCR receives an AC-link beam indication command (DCI and / or MAC CE and / or RRC signaling, such as the aforementioned first beam indication information or second beam indication information), the AC-link beam indicated by the command is associated with a time domain resource. If the NCR cannot determine the BH link beam associated with the time domain resource (for example, determined by signaling used to indicate the BH link beam (such as the second indication information), or determined according to a predefined rule), the NCR (NCR-Fwd) closes or does not forward or consider the AC-link beam indication command.

[0259] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0260] Embodiments of the second aspect

[0261] An embodiment of the present application provides an information sending method, which is explained from the perspective of a network device, and the contents that are the same as those in the embodiment of the first aspect will not be repeated.

[0262] FIG12 is a schematic diagram of a method for sending information according to an embodiment of the present application. As shown in FIG12 , the method includes:

[0263] 1201. The network device sends first indication information and / or second indication information and / or third indication information and / or fourth indication information to the forwarder. For the implementation of each information, reference may be made to the embodiment of the first aspect, and no further details will be given here.

[0264] In some embodiments, when the first TCI state set or the second TCI state set or the first SRI set includes only one TCI state or SRI, the third indication information for indicating the backhaul link beam is sent or not sent.

[0265] In some embodiments, the first indication information is not sent before the third backhaul link beam is indicated and / or the third backhaul link beam is applied.

[0266] It is worth noting that FIG12 above merely illustrates an embodiment of the present application and is not intended to be limiting. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be omitted. Those skilled in the art may make appropriate modifications based on the above description and are not limited to the description in FIG12 above.

[0267] The above only describes the steps or processes related to the present application, but the present application is not limited thereto. The method of the embodiment of the present application may also include other steps or processes. For the specific content of these steps or processes, reference may be made to the relevant art.

[0268] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0269] Therefore, the indication information sent by the network device to the repeater enables the beam of the NCR during forwarding to match the beam of the terminal device receiving the forwarded signal, thereby improving the effect of amplifying / enhancing the signal, while reducing interference to other devices in the network and improving network throughput.

[0270] Embodiments of the third aspect

[0271] An embodiment of the present application provides a forwarder, which may be, for example, the aforementioned NCR, or a network device or terminal device with a forwarding function, or one or more parts or components configured in the NCR, network device or terminal device.

[0272] Figure 13 is a schematic diagram of a repeater according to an embodiment of the present application. Since the principle of solving the problem by the repeater is the same as the method of the embodiment of the first aspect, its specific implementation can refer to the embodiment of the first aspect, and the same contents will not be repeated.

[0273] As shown in FIG13 , the forwarder 1300 further includes:

[0274] A mobile terminal 1301 receives first indication information for indicating an access link beam, where the first indication information includes an information field for indicating the access link beam and an information field for indicating time domain resources;

[0275] The forwarding unit 1302 uses the first return link beam for forwarding in the first time domain resource, and / or uses the second return link beam for forwarding in the second time domain resource, and / or uses the third return link beam for forwarding in the third time domain resource, and / or does not forward in the fourth time domain resource.

[0276] or,

[0277] A mobile terminal 1301 receives first indication information for indicating an access link beam, where the first indication information includes an information field for indicating a beam and / or an information field for indicating a time domain resource;

[0278] The forwarding unit 1302 adopts the second backhaul link beam for forwarding, or does not forward, before being instructed to use the third backhaul link beam and / or applying the third backhaul link beam.

[0279] or,

[0280] The mobile terminal 1301 does not (expects to) receive the first indication information and / or apply the first indication information before being instructed about the third backhaul link beam and / or applying the third backhaul link beam.

[0281] or,

[0282] Mobile terminal 1301 receives first indication information for indicating an access link beam, and / or receives second indication information for indicating a return link beam, wherein the second indication information indicates a TCI state for the return link from a first TCI state set, or indicates a TCI state for the return link from a second TCI state set, or indicates an SRI for the return link from a first SRI set.

[0283] or,

[0284] The mobile terminal 1301 receives fourth indication information for configuring the first TCI state set or the second TCI state set or the first SRI set;

[0285] When the first TCI state set or the second TCI state set or the first SRI set includes only one TCI state or SRI, the third indication information for indicating the backhaul link beam is received or not received.

[0286] In addition, for the sake of simplicity, FIG13 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0287] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0288] Embodiments of the fourth aspect

[0289] An embodiment of the present application provides a network device.

[0290] Figure 14 is a schematic diagram of a network device according to an embodiment of the present application. Since the principle of solving the problem by the network device is the same as the method of the embodiment of the second aspect, its specific implementation can refer to the embodiment of the second aspect, and the same contents will not be repeated.

[0291] As shown in FIG14 , the network device 1400 of the embodiment of the present application includes:

[0292] The sending unit 1401 sends the first indication information and / or the second indication information and / or the third indication information and / or the fourth indication information to the forwarder. For the implementation of each information, reference can be made to the embodiment of the first aspect, which will not be repeated here.

[0293] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The network device 1400 of the embodiment of the present application may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0294] In addition, for the sake of simplicity, FIG14 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0295] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0296] Embodiments of the fifth aspect

[0297] An embodiment of the present application provides a communication system. Figure 1 is a schematic diagram of the communication system of the embodiment of the present application. As shown in Figure 1, the communication system includes a network device 101, a repeater 102 and a terminal device 103. For simplicity, Figure 1 only uses one network device, one repeater and two terminal devices as an example for illustration, but the embodiment of the present application is not limited to this.

[0298] In an embodiment of the present application, existing services or future services can be transmitted between the network device 101 and the terminal device 103. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable and low-latency communication (URLLC), and vehicle-to-everything (V2X) communication, etc. The forwarder 102 is configured to execute the information receiving method described in the embodiment of the first aspect, and the network device 101 is configured to execute the information sending method described in the embodiment of the second aspect, the contents of which are incorporated herein and will not be repeated here.

[0299] An embodiment of the present application further provides an electronic device, which may be, for example, a repeater or a network device.

[0300] Figure 15 is a schematic diagram of the electronic device according to an embodiment of the present application. As shown in Figure 15 , electronic device 1500 may include a processor 1510 (e.g., a central processing unit (CPU)) and a memory 1520 ; the memory 1520 is coupled to the processor 1510 . The memory 1520 may store various data and may also store an information processing program 1530 , which is executed under the control of the processor 1510 .

[0301] For example, the processor 1510 may be configured to execute a program to implement the information sending method as described in the embodiment of the second aspect.

[0302] For another example, the processor 1510 may be configured to execute a program to implement the information receiving method as described in the embodiment of the first aspect.

[0303] In addition, as shown in FIG15 , electronic device 1500 may further include: a transceiver 1540 and an antenna 1550; wherein, the functions of the above components are similar to those in the prior art and are not further described here. It is worth noting that electronic device 1500 does not necessarily include all the components shown in FIG15 ; in addition, electronic device 1500 may also include components not shown in FIG15 , and reference may be made to the prior art for details.

[0304] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a network device, the program enables the computer to execute the information sending method described in the embodiment of the second aspect in the network device.

[0305] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the information sending method described in the embodiment of the second aspect in a network device.

[0306] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a repeater, the program enables a computer to execute the information receiving method described in the embodiment of the first aspect in the repeater.

[0307] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the information receiving method described in the embodiment of the first aspect in a repeater.

[0308] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The logic component is, for example, a field programmable logic component, a microprocessor, a processor used in a computer, etc. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0309] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0310] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0311] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0312] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0313] Regarding the above implementation methods disclosed in this embodiment, the following additional notes are also disclosed:

[0314] 1. A method for receiving information, applied to a transponder, characterized in that the method comprises:

[0315] The forwarder receives first indication information for indicating an access link beam, where the first indication information includes an information field for indicating the access link beam and an information field for indicating a time domain resource;

[0316] The forwarder forwards using the first backhaul link beam in the first time domain resource, and / or forwards using the second backhaul link beam in the second time domain resource, and / or forwards using the third backhaul link beam in the third time domain resource, and / or does not forward in the fourth time domain resource.

[0317] 2. According to the method described in Note 1, the first time domain resource and / or the second time domain resource and / or the third time domain resource and / or the fourth time domain resource are the time domain resources indicated by the first indication information.

[0318] 3. The method according to Note 1 or 2, wherein the forwarding includes downlink forwarding and uplink forwarding.

[0319] 4. The method according to any one of Notes 1 to 3, wherein the first return link beam is the same as the control link beam.

[0320] 5. The method according to Note 1, wherein the control link performs downlink reception or uplink transmission in the first time domain resource, the control link does not perform downlink reception and / or uplink transmission in the second time domain resource and / or the third time domain resource, and the control link performs downlink reception or uplink transmission or does not perform downlink reception and / or uplink transmission in the fourth time domain resource.

[0321] 6. The method according to any one of Notes 1 to 4, wherein the second backhaul link includes:

[0322] The beam determined by the QCL hypothesis of the CORESET with the lowest ID; and / or,

[0323] A beam determined by the spatial relationship of the PUCCH with the lowest PUCCH resource ID; and / or,

[0324] The same beam as the beam used for reception and / or transmission of the most recent / last control link; and / or,

[0325] Beam determined based on the SSB identified / selected during initial access; and / or,

[0326] The beam is determined based on the SSB identified / selected during the random access process.

[0327] 6a. The method according to Note 6, wherein the most recent / last control link reception includes: the most recent / last monitoring of PDCCH and / or reception of PDSCH and / or CSI-RS and / or SSB. The most recent / last control link transmission includes: the most recent / last transmission of PUSCH and / or PUCCH and / or SRS.

[0328] 7. The method according to Note 6, wherein the random access process is used for initial access or beam failure recovery or RRC connection reestablishment or RRC connection recovery.

[0329] 8. The method according to Supplement 6, wherein the CORESET with the lowest ID is a CORESET with an ID at the first DL BWP and / or the first time position.

[0330] 9. The method according to Note 6, wherein the PUCCH with the lowest PUCCH resource ID is the PUCCH with the lowest PUCCH resource ID at the first UL BWP and / or the second time position.

[0331] 10. The method according to supplementary note 8, wherein the first DL BWP is in a Pcell, and / or the first DL BWP is an initial DL BWP, a default DL BWP, or an activated DL BWP.

[0332] 11. The method according to Note 8, wherein the first time position includes: the mobile terminal of the repeater monitors the latest / latter time slot of one or more CORESETs.

[0333] 12. The method according to Note 9, wherein the first UL BWP is in a Pcell, and / or the first UL BWP is an initial UL BWP, a default UL BWP, or an activated UL BWP.

[0334] 13. According to the method described in Note 9, the second time position includes: the latest / latter time slot in which the mobile terminal of the repeater sends PUCCH.

[0335] 14. The method according to any one of Notes 1 to 13, wherein the third return link beam is indicated by second indication information for indicating a return link beam or is determined according to third indication information for indicating a control link beam.

[0336] 15. The method according to Note 14, wherein the second indication information is MAC signaling.

[0337] 16. The method according to Note 14, wherein the second indication information indicates a TCI state for the backhaul link from the first TCI state set, or indicates a TCI state for the backhaul link from the second TCI state set, or indicates an SRI for the backhaul link from the first SRI set.

[0338] 17. According to the method described in Note 14, the third indication information indicates the Unified TCI state.

[0339] 18. The method according to any one of Notes 1 to 17, wherein forwarding using a second backhaul link beam in the second time domain resource comprises:

[0340] The second time domain resource is before the third backhaul link beam is indicated or determined and / or the third backhaul link is applied, or,

[0341] In a case where the second time domain resource does not have the third backhaul link beam, the second time domain resource is forwarded using the second backhaul link beam.

[0342] 19. The method according to any one of Notes 1 to 17, wherein not forwarding in the fourth time domain resource comprises:

[0343] The fourth time domain resource is before the third backhaul link beam is indicated or determined and / or the third backhaul link is applied, or,

[0344] When the fourth time domain resource does not have the third backhaul link beam, no forwarding is performed on the fourth time domain resource.

[0345] 20. The method according to Note 19, wherein the control link performs downlink reception or uplink transmission or does not perform downlink reception and / or uplink transmission in the fourth time domain resource.

[0346] 21. The method according to any one of Notes 1 to 20, wherein the forwarding using a third backhaul link beam in the third time domain resource comprises:

[0347] The third time domain resource is after the third backhaul link beam is indicated or determined and / or the third backhaul link is applied, or,

[0348] In a case where the third time domain resource has a third backhaul link beam, the third time domain resource is forwarded using the third backhaul link beam.

[0349] 22. According to the method according to any one of Notes 1 to 20, the first time domain resource is or is not before the third backhaul link beam is indicated or determined and / or the third backhaul link is applied.

[0350] 23. According to the method described in any one of Notes 1 to 21, the NCR supports or does not support the second indication information.

[0351] 24. An information receiving method, applied to a transponder, characterized in that the method comprises:

[0352] The forwarder receives first indication information for indicating an access link beam, the first indication information including an information field for indicating a beam and / or an information field for indicating a time domain resource; before being instructed to use a third backhaul link beam and / or applying the third backhaul link beam, the forwarder uses the second backhaul link beam for forwarding, or does not forward; or

[0353] The forwarder does not (expects to) receive the first indication information and / or apply the first indication information before being instructed to use the third backhaul link beam and / or applying the third backhaul link beam.

[0354] 25. The method according to Note 24, wherein the not forwarding before being instructed about the third backhaul link beam and / or applying the third backhaul link beam includes: the NCR not applying the first indication information.

[0355] 26. An information receiving method, applied to a transponder, characterized in that the method comprises:

[0356] The repeater receives first indication information for indicating an access link beam, and / or,

[0357] The forwarder receives second indication information for indicating a backhaul link beam, where the second indication information indicates a TCI state for the backhaul link from the first TCI state set, or indicates a TCI state for the backhaul link from the second TCI state set, or indicates an SRI for the backhaul link from the first SRI set.

[0358] 27. The method according to Note 26, wherein, for the first indication information carried by RRC signaling, the first indication information is applied from a third time position.

[0359] 28. The method according to Note 26, wherein, for the first indication information carried by the DCI, the first indication information is applied from a fourth time position.

[0360] 29. The method according to Note 26, wherein the return link beam indicated by the second indication information is applied from a fifth time position.

[0361] 30. The method according to Note 26, wherein the second indication information is carried by MAC signaling.

[0362] 31. An information receiving method, applied to a transponder, characterized in that the method comprises:

[0363] The forwarder receives fourth indication information for configuring the first TCI state set or the second TCI state set or the first SRI set;

[0364] In a case where the first TCI state set or the second TCI state set or the first SRI set includes only one TCI state or SRI, the forwarder receives or does not receive the third indication information for indicating the backhaul link beam.

[0365] 32. The method according to Note 31, wherein the NCR supports the third indication information.

[0366] 33. The method according to Note 31, wherein the method further comprises: the NCR uses the beam corresponding to the TCI state and / or SRI for forwarding.

[0367] 34. A forwarding control method, applied to a forwarder, characterized in that the method comprises:

[0368] When the NCR is indicated with a return link beam and there is no indicated / determined / available access link beam, the indicated return link beam and / or the indication command for indicating the return link beam are invalid or ineffective, and / or the NCR (NCR-Fwd) turns off or does not forward or ignores the indication command for indicating the return link beam, or,

[0369] After the NCR receives an indication command for indicating a return link beam and is then indicated to indicate an access link beam, or before the received access link beam indication is applied / valid, the indication command is not valid / applied, and / or the NCR (NCR-Fwd) closes or does not forward or ignores the indication command; or,

[0370] For a time domain resource, when the NCR determines the return link beam and there is no available access link beam, the determined return link beam is invalid or ineffective, and / or the NCR (NCR-Fwd) is closed or not forwarded, and / or the NCR does not determine the return link beam corresponding to the time domain resource; or,

[0371] For a time domain resource, when the NCR is indicated an access link beam, the NCR must / should have an indicated or determined backhaul link beam, or the NCR expects to receive a backhaul link beam indication indicating a backhaul link beam for the time domain resource, and / or the NCR determines the backhaul link beam; or,

[0372] When the NCR receives an access link beam indication command, and the access link beam indicated by the indication command is related to a time domain resource, when the NCR cannot determine the return link beam related to the time domain resource, the NCR (NCR-Fwd) closes or does not forward or consider the access link beam indication command.

[0373] 35. A repeater comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 1 to 34.

[0374] 36. A method for sending information, applied to a network device, characterized in that the method comprises:

[0375] The network device sends first indication information and / or second indication information and / or third indication information and / or fourth indication information to the forwarder, wherein:

[0376] The first indication information is used to indicate an access link beam;

[0377] The second indication information is used to indicate a backhaul link beam;

[0378] The third indication information is used to indicate a control link beam;

[0379] The fourth indication information is used to configure the first TCI state set or the second TCI state set or the first SRI set.

[0380] 37. A method according to Note 36, wherein the second indication information indicates a TCI state for the backhaul link from the first TCI state set, or indicates a TCI state for the backhaul link from the second TCI state set, or indicates an SR for the backhaul link from the first SRI set.

[0381] 38. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in Note 36 or 37.

Claims

1. A repeater, characterized in that: The repeater comprises: A mobile terminal, which receives first indication information for indicating an access link beam, wherein the first indication information includes an information field for indicating the access link beam and an information field for indicating time domain resources; A forwarding unit that forwards using a first return link beam in a first time domain resource, and / or forwards using a second return link beam in a second time domain resource, and / or forwards using a third return link beam in a third time domain resource, and / or does not forward in a fourth time domain resource. 2 . The repeater according to claim 1 , wherein the first time domain resource and / or the second time domain resource and / or the third time domain resource and / or the fourth time domain resource are time domain resources indicated by the first indication information.

3. The repeater according to claim 1, wherein: The first backhaul link beam is the same as the control link beam.

4. The repeater according to claim 1, wherein: The control link performs downlink reception or uplink transmission in the first time domain resources, the control link does not perform downlink reception and / or uplink transmission in the second time domain resources and / or the third time domain resources, and the control link performs downlink reception or uplink transmission or does not perform downlink reception and / or uplink transmission in the fourth time domain resources.

5. The repeater according to claim 1, wherein: The second backhaul link includes: The beam determined by the QCL hypothesis of the CORESET with the lowest ID; and / or, A beam determined by the spatial relationship of the PUCCH with the lowest PUCCH resource ID; and / or, The same beam as the beam used for reception and / or transmission of the most recent / last control link; and / or, Beam determined based on the SSB identified / selected during initial access; and / or, The beam is determined based on the SSB identified / selected during the random access process.

6. The repeater according to claim 5, wherein: The random access procedure is used for initial access or beam failure recovery or RRC connection reestablishment or RRC connection recovery.

7. The repeater according to claim 5, wherein: The CORESET with the lowest ID is the CORESET with an ID at the first DL BWP and / or the first time position.

8. The repeater according to claim 5, wherein: The PUCCH with the lowest PUCCH resource ID is the PUCCH with the lowest PUCCH resource ID at the first UL BWP and / or the second time position.

9. The repeater according to claim 7, wherein: The first DL BWP is in the Pcell, and / or the first DL BWP is an initial DL BWP, a default DL BWP, or an activated DL BWP.

10. The repeater according to claim 7, wherein: The first time position includes: the mobile terminal of the repeater monitors the latest / latter time slot of one or more CORESETs.

11. The repeater according to claim 8, wherein: The first UL BWP is in the Pcell, and / or the first UL BWP is an initial UL BWP, a default UL BWP, or an activated UL BWP.

12. The repeater of claim 8, wherein the second time position comprises: The mobile terminal of the repeater sends the latest / latter time slot of PUCCH.

13. The repeater according to claim 1, wherein: The third backhaul link beam is indicated by second indication information used to indicate the backhaul link beam or is determined according to third indication information used to indicate the control link beam.

14. The repeater according to claim 13, wherein: The second indication information indicates a TCI state for the backhaul link from the first TCI state set, or indicates a TCI state for the backhaul link from the second TCI state set, or indicates an SRI for the backhaul link from the first SRI set.

15. The repeater according to claim 1, wherein: The second backhaul link beam is used for forwarding in the second time domain resource, including: The second time domain resource is before the third backhaul link beam is indicated or determined and / or the third backhaul link is applied, or, In a case where the second time domain resource does not have the third backhaul link beam, the second time domain resource is forwarded using the second backhaul link beam.

16. The repeater according to claim 1, wherein: In the fourth time domain, resources are not forwarded, including: The fourth time domain resource is before the third backhaul link beam is indicated or determined and / or the third backhaul link is applied, or, When the fourth time domain resource does not have the third backhaul link beam, no forwarding is performed on the fourth time domain resource.

17. The repeater according to claim 16, wherein: The control link performs downlink reception or uplink transmission or does not perform downlink reception and / or uplink transmission in the fourth time domain resource.

18. The repeater according to claim 1, wherein: The third time domain resource is forwarded using a third backhaul link beam, including: The third time domain resource is after the third backhaul link beam is indicated or determined and / or the third backhaul link is applied, or, In a case where the third time domain resource has a third backhaul link beam, the third backhaul link beam is used to perform forwarding in the third time domain resource.

19. A network device, characterized in that: The network equipment includes: A sending unit, which sends the first indication information and / or the second indication information and / or the third indication information and / or the fourth indication information to the forwarder, wherein: The first indication information is used to indicate an access link beam; The second indication information is used to indicate a backhaul link beam; The third indication information is used to indicate a control link beam; The fourth indication information is used to configure the first TCI state set or the second TCI state set or the first SRI set.

20. A communication system, characterized in that: The communication system comprises the repeater according to claim 1 and / or the network device according to claim 19.

Images