A state configuration method and device

By using the original TCI state for data transmission and reception when the TCI state changes, the problem of data scheduling failure caused by TCI state updates in 5G NR technology is solved, and the accuracy and continuity of data transmission are achieved.

CN114124330BActive Publication Date: 2026-11-10HUAWEI TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202111217317.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2019-02-14
Publication Date
2026-11-10
Estimated Expiration
2039-02-14

AI Technical Summary

Technical Problem

In 5G NR technology, the existing TCI status update scheme causes data scheduling failure, which cannot effectively update the beam information between terminal devices and network devices, resulting in inaccurate data transmission.

Method used

When the TCI state changes, the terminal device continues to use the original TCI state for data transmission and reception until the new TCI state is activated, ensuring the accuracy and continuity of data transmission.

Benefits of technology

By using the original TCI state for data transmission and reception, the accuracy and continuity of data transmission are ensured, and the problem of data scheduling failure is avoided.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114124330B_ABST
    Figure CN114124330B_ABST
Patent Text Reader

Abstract

This application discloses a state configuration method and device for updating the TCI state and ensuring correct data transmission and reception. An embodiment of this application provides a state configuration method, comprising: a terminal device determining that the Transmission Configuration Indicator (TCI) state configured by a network device has changed; the terminal device acquiring a first TCI state configured by the network device before the TCI state changed; the terminal device configuring a second TCI state that is the same as the first TCI state, wherein when the second TCI state and the first TCI state are the same TCI state, the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable; and the terminal device using the second TCI state for data transmission and reception before the third TCI state configured by the network device is activated after the TCI state changes.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a state configuration method and device. Background Technology

[0002] The New Radio (NR) technology in fifth-generation wireless mobile telecommunications technology (5G) is similar to the Long Term Evolution (LTE) technology in fourth-generation wireless mobile telecommunications technology (4G) in that both require beam information to enable the transmission and reception of information between network devices and terminal devices.

[0003] In current NR technology, network devices send transmission configuration indicators (TCIs) to terminal devices. Different TCI states indicate the quasi-co-located (QCL) relationship between the corresponding reference signal and the configured reference signal. That is, based on the reference signal pointed to by the TCI state, the terminal device can assume that the beam pattern used by the network device when transmitting is the same as the reference signal it is pointing to.

[0004] In the prior art, before the TCI state configured by the network device for the terminal device is activated by the medium access control control element (MAC CE), the terminal device should assume that the reference signal pointed to by the TCI state is the synchronous signal block (SSB) determined when initially accessing the cell.

[0005] In the aforementioned prior art, when the reference signal pointed to by the TCI state has a QCL relationship with the SSB defined by the cell, it can only be used when the terminal device initially accesses the cell and has not yet received MAC CE activation. However, it cannot be used after the terminal device has already accessed the cell because the SSB transmission beam may be different from the actual data scheduling after the terminal device has accessed the cell, or the time since the terminal device last measured the SSB may be too long. Therefore, the TCI state update scheme given in the current technology is not feasible. If the reference signal is determined based on the TCI state update scheme of the existing technology, it will lead to data scheduling failure. Summary of the Invention

[0006] This application provides a state configuration method and device for updating the TCI state and ensuring the correct transmission and reception of data.

[0007] To address the aforementioned technical problems, this application provides the following technical solutions:

[0008] In a first aspect, embodiments of this application provide a state configuration method, comprising: a terminal device determining that a Transmission Configuration Indicator (TCI) state configured by a network device has changed; the terminal device acquiring a first TCI state configured by the network device before the TCI state changed; the terminal device configuring a second TCI state that is the same as the first TCI state, wherein when the second TCI state is the same as the first TCI state, the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable; and the terminal device using the second TCI state for data transmission and reception before the third TCI state configured by the network device is activated after the TCI state changes.

[0009] In this embodiment, the first TCI state is the TCI state before the TCI state changes, and the third TCI state is the TCI state after the TCI state changes. Before the third TCI state is activated, the second TCI state configured above can be used for data transmission and reception in this embodiment. Since the second TCI state is the same as the first TCI state, the terminal device uses the reference signal pointed to by the first TCI state before the TCI state changes and no longer uses the existing technology. Before the new TCI state (i.e., the third TCI state) is activated by the network device, the terminal device can use the old TCI state (i.e., the first TCI state) as the currently available TCI state (i.e., the second TCI state). Using the reference signal pointed to by the old TCI state is more accurate and timely, which makes the data transmission performance better and thus can ensure the correct transmission and reception of data.

[0010] In one possible design of the first aspect, the terminal device determines that the Transmission Configuration Indicator (TCI) state configured by the network device has changed, including: the terminal device receiving Radio Resource Configuration (RRC) signaling sent by the network device, the RRC signaling instructing the terminal device to perform uplink or downlink bandwidth segment (BWP) handover, wherein the BWP handover causes a change in the TCI state configured by the network device; and the terminal device determining that the TCI state has changed based on the received RRC signaling. The network device can send RRC signaling, which can trigger the terminal device to perform a BWP handover, causing a change in the TCI state configured by the network device. Therefore, if the terminal device receives the aforementioned RRC signaling from the network device, the terminal device can determine that the TCI state has changed based on this RRC signaling.

[0011] In one possible design of the first aspect, the terminal device acquiring the first TCI state configured by the network device before the TCI state changes includes: the terminal device acquiring the first TCI state corresponding to the first downlink control channel that schedules the RRC signaling, wherein the first downlink control channel is the downlink control channel before the TCI state changes. The RRC signaling is scheduled by the first downlink control channel, which may specifically be a physical downlink control channel (PDCCH). Since this first downlink control channel is the downlink control channel before the TCI state changes, the terminal device determines the TCI state corresponding to this first downlink control channel as the aforementioned first TCI state.

[0012] In one possible design of the first aspect, the terminal device configures the second TCI state to be the same as the first TCI state, including: the terminal device configures the second TCI state corresponding to the second downlink control channel to be the same as the first TCI state corresponding to the first downlink control channel, wherein the second downlink control channel is the downlink control channel after the TCI state changes. Specifically, the second downlink control channel is the downlink control channel after the TCI state changes, meaning the second downlink control channel is the downlink control channel that the terminal device needs to use before the third TCI state is activated. The terminal device configures the second TCI state corresponding to the second downlink control channel to be the same as the first TCI state corresponding to the first downlink control channel, meaning the terminal device uses the first TCI state corresponding to the first downlink control channel of the scheduling RRC signaling.

[0013] In one possible design of the first aspect, when there are multiple second downlink control channels after the TCI state changes, all the second downlink control channels correspond to the same second TCI state; or, the number of second downlink control channels is the same as the number of first downlink control channels, and the second downlink control channels with the same channel identifier correspond to the same TCI state as the first downlink control channels; or, when there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

[0014] When the TCI state configured in the network device changes, the terminal device can use multiple second downlink control channels, for example, three. All the second downlink control channels correspond to the same TCI state. As explained in the foregoing embodiments, since the second TCI state is the same as the first TCI state, when multiple second downlink control channels exist after the TCI state changes, all of them continue to use the reference signal pointed to by the first TCI state for data transmission and reception. By configuring multiple second downlink control channels with the same second TCI state, the TCI state configuration of multiple second downlink control channels can be simplified, and correct data transmission and reception on multiple second downlink control channels can be guaranteed.

[0015] In some other embodiments of this application, the number of downlink control channels remains unchanged before and after the TCI state changes. That is, the number of second downlink control channels is the same as the number of first downlink control channels. For example, if there are 3 first downlink control channels before the TCI state changes, then there are also 3 second downlink control channels after the TCI state changes. Second downlink control channels with the same channel identifier correspond to the same TCI state as first downlink control channels, which simplifies the TCI state configuration of the second downlink control channels and ensures that data transmission and reception can be performed correctly on the second downlink control channels.

[0016] In other embodiments of this application, before the TCI state configured by the network device changes, the terminal device may use multiple first downlink control channels, for example, the terminal device may use three first downlink control channels. When there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel. That is, when there are multiple first downlink control channels, the first TCI state corresponding to the predefined downlink control channel can be used for the configuration of the second TCI state.

[0017] In one possible design of the first aspect, the terminal device acquiring the first TCI state configured by the network device before the TCI state changes includes: the terminal device acquiring the first TCI state corresponding to the first downlink shared channel carrying the RRC signaling, wherein the first downlink shared channel is the downlink shared channel before the TCI state changes. The RRC signaling can be carried by the first downlink shared channel, for example, the first downlink shared channel can be a physical downlink shared channel (PDSCH). Since this first downlink shared channel is the downlink shared channel before the TCI state changes, the terminal device determines the TCI state corresponding to this first downlink shared channel as the aforementioned first TCI state.

[0018] In one possible design of the first aspect, the terminal device configures the second TCI state to be the same as the first TCI state, including: the terminal device configures the second TCI state corresponding to the second downlink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, where the second downlink shared channel is the downlink shared channel after the TCI state changes; or, the terminal device configures the second TCI state corresponding to the first uplink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, where the first uplink shared channel is the uplink shared channel after the TCI state changes. Wherein, the second downlink shared channel is the downlink shared channel after the TCI state changes, that is, the second downlink shared channel is the downlink shared channel that the terminal device needs to use before the third TCI state is activated. The terminal device configures the second TCI state corresponding to the second downlink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, that is, the terminal device uses the first TCI state corresponding to the first downlink shared channel of the scheduling RRC signaling.

[0019] The preceding content explained the configuration of the second TCI state corresponding to the PDCCH and PDSCH used by the terminal device. Next, the configuration method for the second TCI state corresponding to the uplink physical shared channel (PUSCH) will be explained. For example, the first uplink shared channel is the uplink shared channel after the TCI state changes; that is, the first uplink shared channel is the uplink shared channel that the terminal device needs to use before the third TCI state is activated. The terminal device configures the second TCI state corresponding to the first uplink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel; that is, the terminal device uses the first TCI state corresponding to the first downlink shared channel of the RRC signaling.

[0020] In one possible design of the first aspect, the terminal device determines that the TCI state configured by the network device has changed, including: the terminal device receiving a DCI sent by the network device, the DCI being used to instruct the terminal device to perform uplink or downlink BWP handover, wherein the BWP handover causes a change in the TCI state configured by the network device; and the terminal device determining that the TCI state has changed based on the received DCI. Specifically, the network device can send a DCI, which can trigger the terminal device to perform a BWP handover, causing a change in the TCI state configured by the network device. Therefore, if the terminal device receives the aforementioned DCI from the network device, the terminal device can determine that the TCI state has changed based on this DCI.

[0021] In one possible design of the first aspect, the terminal device acquiring the first TCI state configured by the network device before the TCI state changes includes: the terminal device acquiring the first TCI state corresponding to the third downlink control channel carrying the DCI, wherein the third downlink control channel is the downlink control channel before the TCI state changes. The DCI is carried by the third downlink control channel, which may specifically be a PDCCH. Since this third downlink control channel is the downlink control channel before the TCI state changes, the terminal device determines the TCI state corresponding to this third downlink control channel as the aforementioned first TCI state.

[0022] In one possible design of the first aspect, the terminal device configures the second TCI state to be the same as the first TCI state, including: the terminal device configures the second TCI state corresponding to the fourth downlink control channel to be the same as the first TCI state corresponding to the third downlink control channel, wherein the fourth downlink control channel is the downlink control channel after the TCI state changes. Specifically, the fourth downlink control channel is the downlink control channel after the TCI state changes, meaning it is the downlink control channel that the terminal device needs to use before the third TCI state is activated. The terminal device configures the second TCI state corresponding to the fourth downlink control channel to be the same as the first TCI state corresponding to the third downlink control channel, meaning the terminal device uses the first TCI state corresponding to the third downlink control channel used for scheduling RRC signaling.

[0023] In one possible design of the first aspect, when there are multiple fourth downlink control channels after the TCI state changes, all fourth downlink control channels correspond to the same second TCI state; or, the number of fourth downlink control channels is the same as the number of third downlink control channels, and the fourth downlink control channels and the third downlink control channels with the same channel identifier correspond to the same TCI state; when there are multiple third downlink control channels after the TCI state changes, the third downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel. The description of the fourth downlink control channel is analogous to the description of the second downlink control channel described above, and the description of the third downlink control channel is analogous to the description of the first downlink control channel described above, and will not be elaborated further here.

[0024] In one possible design of the first aspect, the terminal device is configured to have the same TCI state as the first TCI state, including: the terminal device is configured to have the same second TCI state corresponding to the third downlink shared channel as the first TCI state corresponding to the third downlink control channel, wherein the third downlink shared channel is the downlink shared channel after the TCI state changes; or, the terminal device is configured to have the same second TCI state corresponding to the second uplink shared channel as the first TCI state corresponding to the third downlink control channel, wherein the second uplink shared channel is the uplink shared channel after the TCI state changes.

[0025] The third downlink shared channel is the downlink shared channel after the TCI state changes; that is, the third downlink shared channel is the downlink shared channel that the terminal device needs to use before the third TCI state is activated. The terminal device configures the second TCI state corresponding to the third downlink shared channel to be the same as the first TCI state corresponding to the third downlink control channel, that is, the terminal device uses the first TCI state corresponding to the third downlink control channel of the scheduling RRC signaling.

[0026] The preceding content explained the configuration of the second TCI state corresponding to the PDCCH and PDSCH used by the terminal device. Next, the configuration method for the second TCI state corresponding to the PUSCH will be explained. For example, the second uplink shared channel is the uplink shared channel after the TCI state changes; that is, the second uplink shared channel is the uplink shared channel that the terminal device needs to use before the third TCI state is activated. The terminal device configures the second TCI state corresponding to the second uplink shared channel to be the same as the first TCI state corresponding to the third downlink control channel; that is, the terminal device uses the first TCI state corresponding to the third downlink control channel of the RRC signaling.

[0027] In one possible design of the first aspect, the terminal device acquiring the first TCI state configured by the network device before the TCI state changes includes: the terminal device acquiring the first TCI state corresponding to a fourth downlink shared channel or a third uplink shared channel, wherein the fourth downlink shared channel is the downlink shared channel before receiving the DCI, and the third uplink shared channel is the uplink shared channel before receiving the DCI. The first TCI state acquired by the terminal device can correspond to either the fourth downlink shared channel or the third uplink shared channel.

[0028] In one possible design of the first aspect, the terminal device is configured to have the same TCI state as the first TCI state, including: the terminal device configuring the second TCI state corresponding to the fifth downlink shared channel to be the same as the first TCI state corresponding to the fourth downlink shared channel, wherein the fifth downlink shared channel is the downlink shared channel after the TCI state has changed; or, the terminal device configuring the second TCI state corresponding to the fifth downlink shared channel to be the same as the first TCI state corresponding to the third uplink shared channel; or, the terminal device configuring the second TCI state corresponding to the fourth uplink shared channel to be the same as the first TCI state corresponding to the fourth downlink shared channel, wherein the fourth uplink shared channel is the uplink shared channel after the TCI state has changed; or, the terminal device configuring the second TCI state corresponding to the fourth uplink shared channel to be the same as the first TCI state corresponding to the third uplink shared channel.

[0029] In this embodiment, the fifth downlink shared channel is the downlink shared channel after the TCI state changes. The second TCI state corresponding to the fifth downlink shared channel can be configured based on the first TCI state corresponding to the fourth downlink shared channel, and the second TCI state corresponding to the fifth downlink shared channel can also be configured based on the first TCI state corresponding to the third uplink channel. Similarly, the fourth uplink shared channel is the uplink shared channel after the TCI state changes. The second TCI state corresponding to the fourth uplink shared channel can be configured based on the first TCI state corresponding to the fourth downlink shared channel, and the second TCI state corresponding to the fourth uplink shared channel can also be configured based on the first TCI state corresponding to the third uplink channel. Therefore, in this embodiment, the terminal device can use the first TCI state configured by the network device before the TCI state change when configuring the second TCI state corresponding to the fifth downlink shared channel and the second TCI state corresponding to the fourth uplink shared channel, thereby ensuring that data transmission and reception can be performed correctly on the fifth downlink shared channel and the fourth uplink shared channel.

[0030] In one possible design of the first aspect, the terminal device determines that the Transmission Configuration Indicator (TCI) state configured by the network device has changed, including at least one of the following steps: when a timer jointly maintained by the terminal device and the network device times out, the terminal device performs an uplink or downlink BWP handover; or, when a random access procedure is triggered, the terminal device performs an uplink or downlink BWP handover to perform a random access procedure; wherein the BWP handover causes a change in the TCI state configured by the network device, and the TCI state configured by the network device is used for data transmission and reception between the terminal device and the network device.

[0031] In one possible design of the first aspect, the terminal device acquires the first TCI state configured by the network device before the TCI state changes, including: when the duration corresponding to the timer is less than or a preset threshold, the terminal device acquires the first TCI state before the timer starts; or, when the duration is greater than the preset threshold, the terminal device measures a reference signal and sends an SSB identifier or a CSI-RS identifier to the network device, and the terminal device acquires the first TCI state corresponding to the SSB identifier or CSI-RS identifier. Here, the threshold is a value pre-configured by the network device, and its specific value is not limited here. Different methods are used to acquire the first TCI state based on the relationship between the duration corresponding to the timer and the threshold.

[0032] In one possible design of the first aspect, the terminal device configures the second TCI state to be the same as the first TCI state, including: the terminal device configures the second TCI state corresponding to the fifth downlink control channel to be the same as the first TCI state before the timer started, and the fifth downlink control channel is the downlink control channel after the TCI state changes; or, the terminal device configures the second TCI state corresponding to the sixth downlink shared channel to be the same as the first TCI state before the timer started, and the sixth downlink shared channel is the downlink shared channel after the TCI state changes; or, the terminal device configures the second TCI state corresponding to the fifth uplink shared channel to be the same as the first TCI state before the timer started, and the fifth uplink shared channel is the uplink shared channel after the TCI state changes. In the above embodiments of this application, the terminal device can use the first TCI state configured by the network device before the TCI state changes when configuring the second TCI state corresponding to the sixth downlink shared channel and the second TCI state corresponding to the fifth uplink shared channel, thereby ensuring that data transmission and reception can be performed correctly on the sixth downlink shared channel and the fifth uplink shared channel.

[0033] In one possible design of the first aspect, the terminal device is configured to have a second TCI state that is the same as the first TCI state, including: the terminal device configuring the second TCI state corresponding to the fifth downlink control channel to be the same as the first TCI state corresponding to the SSB identifier or CSI-RS identifier, wherein the fifth downlink control channel is the downlink control channel after the TCI state changes; or, the terminal device configuring the second TCI state corresponding to the sixth downlink sharing channel to be the same as the first TCI state corresponding to the SSB identifier or CSI-RS identifier, wherein the sixth downlink sharing channel is the downlink sharing channel after the TCI state changes; or, the terminal device configuring the second TCI state corresponding to the fifth uplink sharing channel to be the same as the first TCI state corresponding to the SSB identifier or CSI-RS identifier, wherein the fifth uplink sharing channel is the uplink sharing channel after the TCI state changes.

[0034] In the above embodiments of this application, the terminal device can use the first TCI state configured by the network device before the TCI state changes when configuring the second TCI state corresponding to the sixth downlink shared channel and the second TCI state corresponding to the fifth uplink shared channel, thereby ensuring that data can be correctly transmitted and received on the sixth downlink shared channel and the fifth uplink shared channel.

[0035] In some embodiments of this application, step S11, in which the terminal device obtains the first TCI state configured by the network device before the TCI state changes, includes: when the terminal device is in a connected state, the terminal device obtains a random access trigger instruction, which is used to instruct the terminal device to obtain random access channel (RACH) resources; the terminal device obtains the first TCI state corresponding to the reference signal associated with the RACH resources.

[0036] In one possible design of the first aspect, the terminal device configures the second TCI state to be the same as the first TCI state, including: the terminal device configures the second TCI state corresponding to the sixth downlink control channel to be the same as the first TCI state corresponding to the reference signal associated with the RACH resource, wherein the sixth downlink control channel is the downlink control channel after the TCI state changes; or, the terminal device configures the second TCI state corresponding to the seventh downlink shared channel to be the same as the first TCI state corresponding to the reference signal associated with the RACH resource, wherein the seventh downlink shared channel is the downlink shared channel after the TCI state changes; or, the terminal device configures the second TCI state corresponding to the sixth uplink shared channel to be the same as the first TCI state corresponding to the reference signal associated with the RACH resource, wherein the sixth uplink shared channel is the uplink shared channel after the TCI state changes. In the above embodiments of this application, the terminal device can use the first TCI state configured by the network device before the TCI state changes when configuring the second TCI state corresponding to the seventh downlink shared channel and the second TCI state corresponding to the sixth uplink shared channel, thereby ensuring that data transmission and reception can be performed correctly on the seventh downlink shared channel and the sixth uplink shared channel.

[0037] In one possible design of the first aspect, the terminal device determines that the Transmission Configuration Indicator (TCI) state configured by the network device has changed, including: during the activation of the secondary cell, the terminal device determines that the first reference signal used for channel quality indicator (CQI) measurement on the secondary cell is not configured with a TCI state.

[0038] In one possible design of the first aspect, the terminal device obtains the first TCI state configured by the network device before the TCI state changes, including: the terminal device determining the first TCI state corresponding to the second reference signal reported by the terminal device to the network device.

[0039] In one possible design of the first aspect, the terminal device is configured to have the same TCI state as the first TCI state, including: the terminal device configuring the second TCI state corresponding to the first reference signal to be the same as the first TCI state corresponding to the second reference signal; or, the terminal device configuring the second TCI state corresponding to the seventh downlink control channel to be the same as the first TCI state corresponding to the second reference signal, wherein the seventh downlink control channel is the downlink control channel after the TCI state changes; or, the terminal device configuring the second TCI state corresponding to the eighth downlink shared channel to be the same as the first TCI state corresponding to the second reference signal, wherein the eighth downlink shared channel is the downlink shared channel after the TCI state changes.

[0040] Secondly, embodiments of this application provide a state configuration method, comprising: when the Transmission Configuration Indicator (TCI) state configured by a network device changes, the network device acquires a first TCI state configured by the network device before the TCI state changes; the network device configures a second TCI state that is the same as the first TCI state, and when the second TCI state is the same as the first TCI state, the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable; before the third TCI state configured by the network device is activated after the TCI state changes, the network device uses the second TCI state for data transmission and reception.

[0041] In one possible design of the second aspect, the network device determines that the Transmission Configuration Indicator (TCI) state configured by the network device has changed, including: the network device sending Radio Resource Configuration (RRC) signaling to the terminal device, the RRC signaling being used to instruct the terminal device to perform uplink or downlink bandwidth segment (BWP) handover, wherein the BWP handover causes a change in the TCI state configured by the network device; the network device determines that the TCI state has changed based on the sent RRC signaling.

[0042] In one possible design of the second aspect, the network device obtains the first TCI state configured by the network device before the TCI state changes, including: the network device obtains the first TCI state corresponding to the first downlink control channel that schedules the RRC signaling, wherein the first downlink control channel is the downlink control channel before the TCI state changes.

[0043] In one possible design of the second aspect, the network device is configured to have the same TCI state as the first TCI state, including: the network device is configured to have the same TCI state as the second downlink control channel as the first TCI state corresponding to the first downlink control channel, wherein the second downlink control channel is the downlink control channel after the TCI state has changed.

[0044] In one possible design of the second aspect, when there are multiple second downlink control channels after the TCI state changes, all the second downlink control channels correspond to the same second TCI state; or, the number of second downlink control channels is the same as the number of first downlink control channels, and the second downlink control channels with the same channel identifier correspond to the same TCI state as the first downlink control channels; or, when there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

[0045] In one possible design of the second aspect, the network device obtains the first TCI state configured by the network device before the TCI state changes, including: the network device obtains the first TCI state corresponding to the first downlink shared channel carrying the RRC signaling, wherein the first downlink shared channel is the downlink shared channel before the TCI state changes.

[0046] In one possible design of the second aspect, the network device configures the second TCI state to be the same as the first TCI state, including: the network device configures the second TCI state corresponding to the second downlink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the second downlink shared channel is the downlink shared channel after the TCI state changes; or, the network device configures the second TCI state corresponding to the first uplink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the first uplink shared channel is the uplink shared channel after the TCI state changes.

[0047] In one possible design of the second aspect, the network device determines that the TCI state configured in the network device has changed, including: the network device sending a DCI to the terminal device, the DCI instructing the terminal device to perform an uplink or downlink BWP handover, wherein the BWP handover causes a change in the TCI state configured in the network device; the network device determines that the TCI state has changed based on the received DCI. Specifically, the network device can send a DCI that triggers the terminal device to perform a BWP handover, which causes a change in the TCI state configured in the network device. Therefore, if the network device sends the aforementioned DCI to the terminal device, the network device can determine that the TCI state has changed based on this DCI. For example, the network device sends a DCI to the terminal device, the DCI format being 0_1 or 1_1, instructing the terminal device to switch to another BWP.

[0048] In one possible design of the second aspect, the network device acquires a first TCI state configured by the network device before the TCI state changes, including: the network device acquires the first TCI state corresponding to a third downlink control channel carrying the DCI, wherein the third downlink control channel is the downlink control channel before the TCI state changes. The DCI is carried by the third downlink control channel, for example, the third downlink control channel can be a PDCCH. Since this third downlink control channel is the downlink control channel before the TCI state changes, the network device determines the TCI state corresponding to this third downlink control channel as the aforementioned first TCI state.

[0049] In one possible design of the second aspect, the network device configures the second TCI state to be the same as the first TCI state, including: the network device configures the second TCI state corresponding to the fourth downlink control channel to be the same as the first TCI state corresponding to the third downlink control channel, wherein the fourth downlink control channel is the downlink control channel after the TCI state changes. Specifically, the fourth downlink control channel is the downlink control channel after the TCI state changes, meaning it is the downlink control channel that the network device needs to use before the third TCI state is activated. The network device configures the second TCI state corresponding to the fourth downlink control channel to be the same as the first TCI state corresponding to the third downlink control channel, meaning the network device uses the first TCI state corresponding to the third downlink control channel used for scheduling RRC signaling.

[0050] In one possible design of the second aspect, when there are multiple fourth downlink control channels after the TCI state changes, all fourth downlink control channels correspond to the same second TCI state; or, the number of fourth downlink control channels is the same as the number of third downlink control channels, and the fourth downlink control channels and the third downlink control channels with the same channel identifier correspond to the same TCI state; when there are multiple third downlink control channels after the TCI state changes, the third downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel. The description of the fourth downlink control channel is analogous to the description of the second downlink control channel described above, and the description of the third downlink control channel is analogous to the description of the first downlink control channel described above, and will not be elaborated further here.

[0051] In one possible design of the second aspect, the network device configures the second TCI state to be the same as the first TCI state, including: the network device configures the second TCI state corresponding to the third downlink shared channel to be the same as the first TCI state corresponding to the third downlink control channel, wherein the third downlink shared channel is the downlink shared channel after the TCI state changes; or, the network device configures the second TCI state corresponding to the second uplink shared channel to be the same as the first TCI state corresponding to the third downlink control channel, wherein the second uplink shared channel is the uplink shared channel after the TCI state changes. Wherein, the third downlink shared channel is the downlink shared channel after the TCI state changes, that is, the third downlink shared channel is the downlink shared channel that the network device needs to use before the third TCI state is activated. The network device configures the second TCI state corresponding to the third downlink shared channel to be the same as the first TCI state corresponding to the third downlink control channel, that is, the network device uses the first TCI state corresponding to the third downlink control channel of the scheduled RRC signaling.

[0052] The preceding content explained the configuration of the second TCI state corresponding to the PDCCH and PDSCH used by the network device. Next, the configuration method for the second TCI state corresponding to the PUSCH will be explained. For example, the second uplink shared channel is the uplink shared channel after the TCI state changes; that is, the second uplink shared channel is the uplink shared channel that the network device needs to use before the third TCI state is activated. The network device configures the second TCI state corresponding to the second uplink shared channel to be the same as the first TCI state corresponding to the third downlink control channel; that is, the network device uses the first TCI state corresponding to the third downlink control channel of the RRC signaling.

[0053] In one possible design of the second aspect, the network device acquires a first TCI state configured by the network device before the TCI state changes, including: the network device acquiring the first TCI state corresponding to a fourth downlink shared channel or a third uplink shared channel, wherein the fourth downlink shared channel is the downlink shared channel before receiving the DCI, and the third uplink shared channel is the uplink shared channel before receiving the DCI. The first TCI state acquired by the network device can correspond to either the fourth downlink shared channel or the third uplink shared channel.

[0054] In one possible design of the second aspect, the network device configures the second TCI state to be the same as the first TCI state, including: the network device configures the second TCI state corresponding to the fifth downlink shared channel to be the same as the first TCI state corresponding to the fourth downlink shared channel, wherein the fifth downlink shared channel is the downlink shared channel after the TCI state changes; or, the network device configures the second TCI state corresponding to the fifth downlink shared channel to be the same as the first TCI state corresponding to the third uplink shared channel; or, the network device configures the second TCI state corresponding to the fourth uplink shared channel to be the same as the first TCI state corresponding to the fourth downlink shared channel, wherein the fourth uplink shared channel is the uplink shared channel after the TCI state changes; or, the network device configures the second TCI state corresponding to the fourth uplink shared channel to be the same as the first TCI state corresponding to the third uplink shared channel.

[0055] In this embodiment, the fifth downlink shared channel is the downlink shared channel after the TCI state changes. The second TCI state corresponding to the fifth downlink shared channel can be configured based on the first TCI state corresponding to the fourth downlink shared channel, and the second TCI state corresponding to the fifth downlink shared channel can also be configured based on the first TCI state corresponding to the third uplink channel. Similarly, the fourth uplink shared channel is the uplink shared channel after the TCI state changes. The second TCI state corresponding to the fourth uplink shared channel can be configured based on the first TCI state corresponding to the fourth downlink shared channel, and the second TCI state corresponding to the fourth uplink shared channel can also be configured based on the first TCI state corresponding to the third uplink channel. Therefore, in this embodiment, the network device can use the first TCI state configured before the TCI state change when configuring the second TCI state corresponding to the fifth downlink shared channel and the second TCI state corresponding to the fourth uplink shared channel, thereby ensuring that data transmission and reception can be performed correctly on the fifth downlink shared channel and the fourth uplink shared channel.

[0056] In one possible design of the second aspect, the network device obtains the first TCI state configured by the network device before the TCI state changes, including: when the duration corresponding to the timer is less than or a preset threshold, the network device obtains the first TCI state before the timer starts; or, when the duration is greater than the preset threshold, the network device receives the SSB identifier or CSI-RS identifier reported by the terminal device, and the network device obtains the first TCI state corresponding to the SSB identifier or CSI-RS identifier. Here, the threshold is a value pre-configured by the network device, and its specific value is not limited here. Different methods are used to obtain the first TCI state based on the relationship between the duration corresponding to the timer and the threshold.

[0057] In one possible design of the second aspect, the network device configures the second TCI state to be the same as the first TCI state, including: the network device configures the second TCI state corresponding to the fifth downlink control channel to be the same as the first TCI state before the timer started, and the fifth downlink control channel is the downlink control channel after the TCI state changes; or, the network device configures the second TCI state corresponding to the sixth downlink shared channel to be the same as the first TCI state before the timer started, and the sixth downlink shared channel is the downlink shared channel after the TCI state changes; or, the network device configures the second TCI state corresponding to the fifth uplink shared channel to be the same as the first TCI state before the timer started, and the fifth uplink shared channel is the uplink shared channel after the TCI state changes. In the above embodiments of this application, the network device can use the first TCI state configured by the network device before the TCI state changes when configuring the second TCI state corresponding to the sixth downlink shared channel and the second TCI state corresponding to the fifth uplink shared channel, thereby ensuring that data transmission and reception can be performed correctly on the sixth downlink shared channel and the fifth uplink shared channel.

[0058] In one possible design of the second aspect, the network device configures the second TCI state to be the same as the first TCI state, including: the network device configures the second TCI state corresponding to the fifth downlink control channel to be the same as the first TCI state corresponding to the SSB identifier or CSI-RS identifier, wherein the fifth downlink control channel is the downlink control channel after the TCI state changes; or, the network device configures the second TCI state corresponding to the sixth downlink sharing channel to be the same as the first TCI state corresponding to the SSB identifier or CSI-RS identifier, wherein the sixth downlink sharing channel is the downlink sharing channel after the TCI state changes; or, the network device configures the second TCI state corresponding to the fifth uplink sharing channel to be the same as the first TCI state corresponding to the SSB identifier or CSI-RS identifier, wherein the fifth uplink sharing channel is the uplink sharing channel after the TCI state changes.

[0059] In the above embodiments of this application, the network device can use the first TCI state configured before the TCI state changed when configuring the second TCI state corresponding to the sixth downlink shared channel and the second TCI state corresponding to the fifth uplink shared channel, thereby ensuring that data can be correctly transmitted and received on the sixth downlink shared channel and the fifth uplink shared channel.

[0060] In one possible design of the second aspect, the network device acquires a first TCI state configured by the network device before the TCI state changes, including: the network device sending a random access trigger instruction to the terminal device, the random access trigger instruction being used to instruct the terminal device to acquire RACH resources; and the network device acquiring the first TCI state corresponding to the reference signal associated with the RACH resources.

[0061] In one possible design of the second aspect, the network device configures the second TCI state to be the same as the first TCI state, including: the network device configures the second TCI state corresponding to the sixth downlink control channel to be the same as the first TCI state corresponding to the reference signal associated with the RACH resource, wherein the sixth downlink control channel is the downlink control channel after the TCI state changes; or, the network device configures the second TCI state corresponding to the seventh downlink shared channel to be the same as the first TCI state corresponding to the reference signal associated with the RACH resource, wherein the seventh downlink shared channel is the downlink shared channel after the TCI state changes; or, the network device configures the second TCI state corresponding to the sixth uplink shared channel to be the same as the first TCI state corresponding to the reference signal associated with the RACH resource, wherein the sixth uplink shared channel is the uplink shared channel after the TCI state changes.

[0062] In the above embodiments of this application, the network device can use the first TCI state configured before the TCI state changed when configuring the second TCI state corresponding to the seventh downlink shared channel and the second TCI state corresponding to the sixth uplink shared channel, thereby ensuring that data can be correctly transmitted and received on the seventh downlink shared channel and the sixth uplink shared channel.

[0063] In one possible design of the second aspect, the network device obtains a first TCI state configured by the network device before the TCI state changes, including: the network device determining the first TCI state corresponding to a second reference signal reported by the network device to the network device.

[0064] In one possible design of the second aspect, the network device configures the second TCI state to be the same as the first TCI state, including: the network device configuring the second TCI state corresponding to the first reference signal to be the same as the first TCI state corresponding to the second reference signal; or, the network device configuring the second TCI state corresponding to the seventh downlink control channel to be the same as the first TCI state corresponding to the second reference signal, wherein the seventh downlink control channel is the downlink control channel after the TCI state changes; or, the network device configuring the second TCI state corresponding to the eighth downlink shared channel to be the same as the first TCI state corresponding to the second reference signal, wherein the eighth downlink shared channel is the downlink shared channel after the TCI state changes.

[0065] In the second aspect, the configuration and use of TCI state by network devices are similar to those on the terminal device side. Only when network devices and terminal devices adopt the same second TCI state configuration method can network devices and terminal devices send and receive data to each other.

[0066] Thirdly, embodiments of this application also provide a terminal device, including: a processing unit, configured to determine that a Transmission Configuration Indicator (TCI) state configured by a network device has changed; the processing unit is further configured to acquire a first TCI state configured by the network device before the TCI state changed; the processing unit is further configured to configure a second TCI state to be the same as the first TCI state, wherein when the second TCI state is the same as the first TCI state, the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable;

[0067] The transceiver unit is used to transmit and receive data using the second TCI state before the third TCI state configured by the network device is activated after the TCI state changes.

[0068] In one possible design of the third aspect, the transceiver unit is further configured to receive Radio Resource Configuration (RRC) signaling sent by the network device, the RRC signaling being used to instruct the terminal device to perform uplink or downlink bandwidth segment (BWP) switching, wherein the BWP switching causes a change in the TCI state configured by the network device; the processing unit is specifically configured to determine the change in the TCI state based on the received RRC signaling.

[0069] In one possible design of the third aspect, the processing unit is specifically used to obtain the first TCI state corresponding to the first downlink control channel that schedules the RRC signaling, wherein the first downlink control channel is the downlink control channel before the TCI state changes.

[0070] In one possible design of the third aspect, the processing unit is specifically configured to configure the second TCI state corresponding to the second downlink control channel to be the same as the first TCI state corresponding to the first downlink control channel, wherein the second downlink control channel is the downlink control channel after the TCI state changes.

[0071] In one possible design of the third aspect, when there are multiple second downlink control channels after the TCI state changes, all the second downlink control channels correspond to the same second TCI state; or, the number of second downlink control channels is the same as the number of first downlink control channels, and the second downlink control channels with the same channel identifier correspond to the same TCI state as the first downlink control channels; or, when there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

[0072] In one possible design of the third aspect, the processing unit is specifically used to obtain the first TCI state corresponding to the first downlink shared channel carrying the RRC signaling, wherein the first downlink shared channel is the downlink shared channel before the TCI state changes.

[0073] In one possible design of the third aspect, the processing unit is specifically configured to configure the second TCI state corresponding to the second downlink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the second downlink shared channel is the downlink shared channel after the TCI state changes; or, the processing unit is specifically configured to configure the second TCI state corresponding to the first uplink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the first uplink shared channel is the uplink shared channel after the TCI state changes.

[0074] Fourthly, embodiments of this application also provide a network device, including: a processing unit, configured to acquire a first TCI state configured by the network device before the change of the TCI state when the Transmission Configuration Indicator (TCI) state configured by the network device changes; the processing unit is further configured to configure a second TCI state to be the same as the first TCI state, wherein when the second TCI state and the first TCI state are the same TCI state, the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable; and a transceiver unit, configured to use the second TCI state to transmit and receive data before the third TCI state configured by the network device is activated after the change of the TCI state.

[0075] In one possible design of the fourth aspect, the transceiver unit is further configured to send Radio Resource Configuration (RRC) signaling to the terminal device, the RRC signaling being used to instruct the terminal device to perform uplink or downlink bandwidth segment (BWP) switching, wherein the BWP switching causes a change in the TCI state configured by the network device; the processing unit is specifically configured to determine the change in the TCI state based on the sent RRC signaling.

[0076] In one possible design of the fourth aspect, the processing unit is specifically used to obtain the first TCI state corresponding to the first downlink control channel that schedules the RRC signaling, wherein the first downlink control channel is the downlink control channel before the TCI state changes.

[0077] In one possible design of the fourth aspect, the processing unit is specifically configured to configure the second TCI state corresponding to the second downlink control channel to be the same as the first TCI state corresponding to the first downlink control channel, wherein the second downlink control channel is the downlink control channel after the TCI state changes.

[0078] In one possible design of the fourth aspect, when there are multiple second downlink control channels after the TCI state changes, all the second downlink control channels correspond to the same second TCI state; or, the number of second downlink control channels is the same as the number of first downlink control channels, and the second downlink control channels with the same channel identifier correspond to the same TCI state as the first downlink control channels; or, when there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

[0079] In one possible design of the fourth aspect, the processing unit is specifically used to obtain the first TCI state corresponding to the first downlink shared channel carrying the RRC signaling, wherein the first downlink shared channel is the downlink shared channel before the TCI state changes.

[0080] In one possible design of the fourth aspect, the processing unit is specifically configured to configure the second TCI state corresponding to the second downlink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the second downlink shared channel is the downlink shared channel after the TCI state changes; or, the processing unit is specifically configured to configure the second TCI state corresponding to the first uplink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the first uplink shared channel is the uplink shared channel after the TCI state changes.

[0081] The various possible designs of the communication equipment in the third and fourth aspects achieve the same effect as the corresponding possible designs of the methods in the first and second aspects, and will not be described in detail here.

[0082] Fifthly, a communication device is provided, including a processor and a transceiver, wherein the processor performs the methods described in the first to second aspects above.

[0083] A sixth aspect provides a communication device, including a processor and an interface. The processor performs the methods of the first to second aspects.

[0084] A seventh aspect provides a communication device, including a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the methods of the first to second aspects. It should be noted that the memory may be non-volatile or volatile, and its location may be inside or outside the communication device.

[0085] Eighthly, a communication device is provided that can use the methods of the first to second aspects. The communication device may be a network device, a terminal device, or hardware that implements similar functions.

[0086] Ninthly, a communication system is provided, which includes the aforementioned terminal equipment and network equipment.

[0087] In a tenth aspect, a computer-readable storage medium is provided for storing a computer program including instructions for performing a method in any of the possible implementations of the first to second aspects.

[0088] Eleventhly, a computer program product is provided, the computer program product comprising: computer program code, which, when run on a computer, causes the computer to perform the method in any of the possible implementations of the first to second aspects described above. Attached Figure Description

[0089] Figure 1 A schematic diagram of the communication system architecture used in a state configuration method provided in an embodiment of this application;

[0090] Figure 2 A schematic diagram illustrating an interaction process between network devices, terminal devices, and core network devices provided in an embodiment of this application;

[0091] Figure 3a A flowchart illustrating a state configuration method executed by a terminal device according to an embodiment of this application;

[0092] Figure 3bA flowchart illustrating another state configuration method performed by a terminal device according to an embodiment of this application;

[0093] Figure 4a A flowchart illustrating a state configuration method performed by a network device according to an embodiment of this application;

[0094] Figure 4b A flowchart illustrating another state configuration method performed by a network device according to an embodiment of this application;

[0095] Figure 5a A flowchart illustrating another state configuration method performed by a terminal device according to an embodiment of this application;

[0096] Figure 5b A flowchart illustrating another state configuration method performed by a terminal device according to an embodiment of this application;

[0097] Figure 6a A flowchart illustrating another state configuration method performed by a network device according to an embodiment of this application;

[0098] Figure 6b A flowchart illustrating another state configuration method performed by a network device according to an embodiment of this application;

[0099] Figure 7a A flowchart illustrating another state configuration method performed by a terminal device according to an embodiment of this application;

[0100] Figure 7b A flowchart illustrating another state configuration method performed by a terminal device according to an embodiment of this application;

[0101] Figure 8a A flowchart illustrating another state configuration method performed by a network device according to an embodiment of this application;

[0102] Figure 8b A flowchart illustrating another state configuration method performed by a network device according to an embodiment of this application;

[0103] Figure 9 A flowchart illustrating another state configuration method performed by a terminal device according to an embodiment of this application;

[0104] Figure 10 A flowchart illustrating another state configuration method performed by a network device according to an embodiment of this application;

[0105] Figure 11 This is a schematic diagram of the composition structure of a terminal device provided in an embodiment of this application;

[0106] Figure 12 This is a schematic diagram of the composition structure of another terminal device provided in an embodiment of this application;

[0107] Figure 13 This is a schematic diagram of the composition structure of another terminal device provided in an embodiment of this application;

[0108] Figure 14 This is a schematic diagram of the composition structure of another terminal device provided in an embodiment of this application;

[0109] Figure 15 This is a schematic diagram of the composition structure of a network device provided in an embodiment of this application;

[0110] Figure 16 This is a schematic diagram of the composition structure of another network device provided in an embodiment of this application;

[0111] Figure 17 This is a schematic diagram of the composition structure of another network device provided in an embodiment of this application;

[0112] Figure 18 This is a schematic diagram of the composition structure of another network device provided in an embodiment of this application. Detailed Implementation

[0113] This application provides a state configuration method and device for updating the TCI state and ensuring the correct transmission and reception of data.

[0114] The embodiments of this application will now be described with reference to the accompanying drawings.

[0115] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of elements is not necessarily limited to those elements, but may include other elements not explicitly listed or inherent to those processes, methods, products, or apparatuses.

[0116] The technical solutions of this application can be applied to various data processing communication systems, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single-carrier frequency division multiple access (SC-FDMA), and other systems. The term "system" can be used interchangeably with "network." CDMA systems can implement wireless technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. UTRA can include wideband CDMA (WCDMA) technology and other CDMA variants. CDMA2000 can cover interim standard (IS) 2000 (IS-2000), IS-95, and IS-856 standards. TDMA systems can implement wireless technologies such as Global System for Mobile Communication (GSM). OFDMA systems can implement wireless technologies such as Evolved Universal Radio Terrestrial Access (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash OFDMA. UTRA and E-UTRA are UMTS and its evolved versions, respectively. 3GPP's Long Term Evolution (LTE) and various versions based on LTE are newer versions of UMTS using E-UTRA. Fifth Generation (5G) communication systems and New Radio (NR) are next-generation communication systems currently under research. Furthermore, the communication systems described can also be applied to future-oriented communication technologies, all of which are applicable to the technical solutions provided in the embodiments of this application.The system architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0117] Figure 1 This diagram illustrates a possible structure of a radio access network (RAN) according to an embodiment of this application. The RAN can be a base station access system for a 2G network (i.e., the RAN includes base stations and base station controllers), a base station access system for a 3G network (i.e., the RAN includes base stations and RNCs), a base station access system for a 4G network (i.e., the RAN includes eNBs and RNCs), or a base station access system for a 5G network.

[0118] The RAN includes one or more network devices. These network devices can be any device with wireless transceiver capabilities, or chips embedded within a device with specific wireless transceiver capabilities. The network devices include, but are not limited to: base stations (e.g., base stations BS, NodeB, evolved NodeB or eNB, gNodeB or gNB in ​​5G communication systems, base stations in future communication systems, access nodes in WiFi systems, wireless relay nodes, wireless backhaul nodes, etc.). Base stations can be: macro base stations, micro base stations, pico base stations, small cells, relay stations, etc. Multiple base stations can support networks using one or more of the technologies mentioned above, or future evolved networks. The core network can support networks using one or more of the technologies mentioned above, or future evolved networks. Base stations can contain one or more co-located or non-co-located transmission receiving points (TRPs). Network devices can also be radio controllers, centralized units (CUs), or distributed units (DUs) in cloud radio access network (CRAN) scenarios. Network devices can also be servers, wearable devices, or vehicle-mounted devices, etc. The following explanation uses network devices as base stations as an example. These multiple network devices can be base stations of the same type or different types. The base station can communicate with terminal devices 1-6, or it can communicate with terminal devices 1-6 through a relay station. Terminal devices 1-6 can support communication with multiple base stations using different technologies. For example, a terminal device can support communication with a base station supporting LTE networks, or it can support communication with a base station supporting 5G networks, and it can also support dual connections with both LTE and 5G network base stations. For example, connecting the terminal to the RAN node of a wireless network. Currently, some examples of RAN nodes include: gNB, transmission reception point (TRP), evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved Node B, or home Node B, HNB), base band unit (BBU), or wireless fidelity (Wi-Fi) access point (AP), etc.In a network architecture, network devices may include centralized unit (CU) nodes, distributed unit (DU) nodes, or RAN devices that include both CU and DU nodes.

[0119] Terminal devices 1-6, also known as user equipment (UE), mobile station (MS), mobile terminal (MT), or terminal, are devices that provide voice and / or data connectivity to users, or chips embedded within such devices. Examples include handheld devices and in-vehicle devices with wireless connectivity capabilities. Currently, some examples of terminal devices include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving cars, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes. The terminal device provided in this application embodiment may be a low-complexity terminal device and / or a terminal device in coverage enhancement A mode.

[0120] In this embodiment of the application, the base station and UE1 to UE6 form a communication system. In this communication system, the base station sends one or more of system information, RAR messages and paging messages to one or more UEs among UE1 to UE6. In addition, UE4 to UE6 also form a communication system. In this communication system, UE5 can function as a base station and can send one or more of system information, control information and paging messages to one or more UEs among UE4 and UE6.

[0121] In this invention, the TCI state refers not only to the TCI configuration behavior and content performed by the network device on the terminal device, but also to the situation where the terminal device's control channel or data channel demodulation reference signal (DMRS) port has a quasi-co-address relationship with a specific reference signal when performing data transmission and reception. If a specific reference signal is the reference signal pointed to by the TCI state, then the terminal device's control channel or data channel DMRS port is quasi-co-addressed with that reference signal when performing data transmission and reception.

[0122] In existing technologies, when the reference signal pointed to by the TCI state has a QCL relationship with the SSB defined by the cell, it can only be used when the terminal device initially accesses the cell and has not yet received MAC CE activation. However, it cannot be used after the terminal device has already accessed the cell because the SSB transmission beam may differ from the actual data scheduling after the terminal device has accessed the cell, or the time since the terminal device last measured the SSB may be too long. Therefore, the TCI state update scheme given in the current technology is not feasible. Determining the reference signal based on the existing TCI state update scheme will lead to data scheduling failure.

[0123] For example, in NR technology, terminal devices operate on a bandwidth part (BWP). From a radio frequency perspective, in NR, a frequency band is divided into several BWPs, allowing terminal devices to be configured by the network to operate on at least one BWP simultaneously. Network devices configure parameters related to the physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH) on the BWP. At this point, beam information can be transmitted on different channels according to the configured TCI states, based on the TCI states.

[0124] Therefore, in order for the terminal device to correctly receive and send information transmitted by the network device on the PDCCH and PDSCH channels before the TCI state is activated by MAC CE, the terminal device usually assumes in advance that the receiving beam corresponds to the transmitting beam of the network device. In other words, the terminal device assumes in advance that the reference signal pointed to by the TCI state is the same as the SSB when the terminal device initially accesses the cell.

[0125] However, after the terminal device initially accesses the cell, if a BWP handover is required, before the TCI state configured by the network device for the new BWP is activated by the MAC CE, the terminal device is unaware of the reference signal pointing to the corresponding TCI state of the new BWP. Furthermore, since the reference signal pointed to by the TCI state during initial cell access has lost its timeliness or the terminal device has failed to save it, the terminal device cannot continue to use the reference signal pointed to by the TCI state during initial cell access. As a result, before the TCI state corresponding to the new BWP is activated, it is impossible to correctly send and receive the corresponding information of PDCCH and PDSCH on the new BWP.

[0126] To address the aforementioned problems in the prior art, this application provides a new scheme for updating the TCI state, thereby avoiding data transmission and reception failures caused by assuming that the reference signal pointed to by the TCI state is the same as the SSB when the terminal device initially accesses the cell in the prior art.

[0127] This application proposes a state configuration method applicable to scenarios involving TCI state updates, such as when the TCI state changes due to uplink or downlink BWP switching of the terminal device. Please refer to... Figure 2 The diagram illustrates an interaction process between a network device and a terminal device according to an embodiment of this application. The state configuration method provided in this embodiment mainly includes the following steps S01 to S04 and steps S11 to S13:

[0128] S01, The terminal device determines that the TCI status of the network device configuration has changed.

[0129] In this embodiment, the TCI state configured by the network device is used for data transmission and reception between the terminal device and the network device. The terminal device first determines whether the TCI state configured by the network device has changed. For example, if the beam used for data transmission between the terminal device and the network device changes, the TCI state configured by the network device can be considered to have changed. When the TCI state configured by the network device changes, the terminal device triggers the execution of subsequent step S02. When the TCI state configured by the network device does not change, the terminal device does not execute subsequent step S02.

[0130] In the embodiments of this application, there are several situations in which the TCI state configured by the network device changes. For example, when the network device instructs the terminal device to perform an uplink or downlink BWP handover, the TCI state configured by the network device will change. Another example is that during the activation of a secondary cell, if the network device has not configured a TCI state for the channel state indicator-reference signal (CSI-RS) used for channel quality indicator (CQI) measurement on the secondary cell, the network device needs to configure a TCI state for this CSI-RS. In this case, the change from no TCI state to TCI state configuration can also be considered a change in the TCI state. In practical applications, the specific situations included in the change of the TCI state configured by the network device are not limited to the examples above.

[0131] In some embodiments of this application, such as Figure 3a and Figure 3b As shown, step S01, where the terminal device determines that the TCI status configured in the network device has changed, includes:

[0132] 301. The terminal device receives radio resource configuration (RRC) signaling sent by the network device. The RRC signaling is used to instruct the terminal device to perform uplink or downlink BWP handover. During BWP handover, the TCI state configured by the network device changes.

[0133] 302. The terminal device determines that the TCI status has changed based on the received RRC signaling.

[0134] Specifically, network devices can send RRC signaling, which can trigger a BWP handover on the terminal device. During a BWP handover, the TCI state configured on the network device changes. Therefore, if a terminal device receives the aforementioned RRC signaling from the network device, it can determine that the TCI state has changed based on this RRC signaling.

[0135] S02. The terminal device obtains the first TCI state configured by the network device before the TCI state changes.

[0136] In this embodiment, when the terminal device determines that the TCI state configured by the network device has changed, the terminal device first obtains a first TCI state, which is a TCI state configured by the network device before the change. For example, the first TCI state may be the most recently configured TCI state of the network device before the change. The first TCI state obtained by the terminal device will be different in different scenarios where the TCI state changes. The first TCI state obtained by the terminal device will be described in detail below.

[0137] In some embodiments of this application, such as Figure 3a As shown, in a scenario where the terminal device receives RRC signaling from the network device, step S02, where the terminal device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0138] 303a. The terminal device obtains the first TCI state corresponding to the first downlink control channel of the scheduling RRC signaling. The first downlink control channel is the downlink control channel before the TCI state changes.

[0139] The RRC signaling is scheduled by the first downlink control channel, which may be the physical downlink control channel (PDCCH). This first downlink control channel is the downlink control channel before the TCI state changes, and the terminal device determines the TCI state corresponding to this first downlink control channel as the aforementioned first TCI state.

[0140] In some embodiments of this application, such as Figure 3b As shown, in a scenario where the terminal device receives RRC signaling from the network device, step S02, where the terminal device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0141] 303b. The terminal device obtains the first TCI state corresponding to the first downlink shared channel carrying RRC signaling. The first downlink shared channel is the downlink shared channel before the TCI state changes.

[0142] The RRC signaling can be carried by the first downlink shared channel, which may specifically be the physical downlink shared channel (PDSCH). This first downlink shared channel is the downlink shared channel before the TCI state changes, and the terminal device determines the TCI state corresponding to this first downlink shared channel as the aforementioned first TCI state.

[0143] S03. The terminal device is configured to have the same TCI state as the first TCI state. When the second TCI state and the first TCI state are the same TCI state, the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable.

[0144] In this embodiment, the terminal device first obtains the first TCI state configured by the network device before the TCI state changes, and then configures the second TCI state in the same way based on the first TCI state. The second TCI state refers to the TCI state that the terminal device can use before the third TCI state configured by the network device is activated after the TCI state changes. The reference signal pointed to by the second TCI state can be used for data transmission and reception between the terminal device and the network device.

[0145] In this embodiment, a TCI state where the second TCI state is the same as the first TCI state means that the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable, i.e., the reference signal pointed to by the second TCI state is configured according to the reference signal pointed to by the first TCI state. Quasi-co-addressability can include the second TCI state pointing to the same reference signal as the first TCI state. For example, when configuring the reference signal pointed to by the second TCI state, if the terminal device first obtains a reference signal with ID#0 as the reference signal pointed to by the first TCI state, the terminal device can configure the second TCI state to also point to the reference signal with ID#0. In this embodiment, by configuring the second TCI state to be the same as the first TCI state before the TCI state change, the data transmission failure caused by using the reference signal when the terminal device initially accesses the cell to configure the current TCI state in the prior art is avoided, enabling the reference signal pointed to by the second TCI state in this embodiment to be used for correct data transmission and reception.

[0146] In some embodiments of this application, such as Figure 3a As shown, in the scenario where the terminal device performs the aforementioned step 303a, step S03, configuring the terminal device to have the same TCI state as the first TCI state, includes:

[0147] 304. The terminal device is configured such that the second TCI state corresponding to the second downlink control channel is the same as the first TCI state corresponding to the first downlink control channel. The second downlink control channel is the downlink control channel after the TCI state changes.

[0148] The second downlink control channel is the downlink control channel used after the TCI state changes; that is, the second downlink control channel is the downlink control channel that the terminal device needs to use before the third TCI state is activated. The terminal device configures the second TCI state corresponding to the second downlink control channel to be the same as the first TCI state corresponding to the first downlink control channel, that is, the terminal device uses the first TCI state corresponding to the first downlink control channel of the scheduling RRC signaling.

[0149] Furthermore, in some embodiments of this application, when there are multiple second downlink control channels after the TCI state changes, the second TCI state corresponding to all the second downlink control channels is the same; or,

[0150] The number of second downlink control channels is the same as the number of first downlink control channels, and the second downlink control channels with the same channel identifier correspond to the same TCI state as the first downlink control channels; or,

[0151] When there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

[0152] When the TCI state configured in the network device changes, the terminal device can use multiple second downlink control channels, for example, three. All the second downlink control channels correspond to the same TCI state. As explained in the foregoing embodiments, since the second TCI state is the same as the first TCI state, when multiple second downlink control channels exist after the TCI state changes, all of them continue to use the reference signal pointed to by the first TCI state for data transmission and reception. By configuring multiple second downlink control channels with the same second TCI state, the TCI state configuration of multiple second downlink control channels can be simplified, and correct data transmission and reception on multiple second downlink control channels can be guaranteed.

[0153] For example, taking the change of TCI state caused by BWP handover as an example, before the new TCI state is activated after the BWP handover, the UE assumes that the second TCI state corresponding to all downlink control channels is the same on the new BWP and points to the same set of reference signals (RS) pointed to by the first TCI state.

[0154] In some other embodiments of this application, the number of downlink control channels remains unchanged before and after the TCI state changes. That is, the number of second downlink control channels is the same as the number of first downlink control channels. For example, if there are 3 first downlink control channels before the TCI state changes, then there are also 3 second downlink control channels after the TCI state changes. Second downlink control channels with the same channel identifier correspond to the same TCI state as first downlink control channels, which simplifies the TCI state configuration of the second downlink control channels and ensures that data transmission and reception can be performed correctly on the second downlink control channels.

[0155] For example, if a BWP handover causes a change in the TCI state, and the number of downlink control channels in all BWPs configured in the network device is the same, and the TCI states of downlink control channels with the same channel ID before and after the BWP handover correspond, then the UE can assume that the TCI state of the corresponding downlink control channel is the same before and after the handover, before the new TCI state is activated after the BWP handover.

[0156] In other embodiments of this application, before the TCI state configured by the network device changes, the terminal device may use multiple first downlink control channels, for example, the terminal device may use three first downlink control channels. When there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel. That is, when there are multiple first downlink control channels, the first TCI state corresponding to the predefined downlink control channel can be used for the configuration of the second TCI state.

[0157] For example, taking the change in TCI state caused by BWP handover as an example, the second TCI state used after the BWP handover is the same as the TCI state of one of the downlink control channels in the original BWP. This downlink control channel can be a predefined downlink control channel or one of the downlink control channels used by the UE to receive RRC signaling. The predefined downlink control channel can be the downlink control channel corresponding to Physical Layer 1 ACKnowledgment, or another downlink control channel with a predefined ID, such as PDCCH#0 being a predefined downlink control channel.

[0158] In some embodiments of this application, such as Figure 3b As shown, in the scenario where the terminal device performs the aforementioned step 303b, step S03, configuring the terminal device to have the same TCI state as the first TCI state, includes:

[0159] 305. The terminal device is configured such that the second TCI state corresponding to the second downlink shared channel is the same as the first TCI state corresponding to the first downlink shared channel, and the second downlink shared channel is the downlink shared channel after the TCI state changes; or,

[0160] 306. The terminal device is configured such that the second TCI state corresponding to the first uplink shared channel is the same as the first TCI state corresponding to the first downlink shared channel, and the first uplink shared channel is the uplink shared channel after the TCI state changes.

[0161] The second downlink shared channel is the downlink shared channel after the TCI state changes; that is, the second downlink shared channel is the downlink shared channel that the terminal device needs to use before the third TCI state is activated. The terminal device configures the second TCI state corresponding to the second downlink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, that is, the terminal device uses the first TCI state corresponding to the first downlink shared channel of the scheduling RRC signaling.

[0162] The preceding content explained the configuration of the second TCI state corresponding to the PDCCH and PDSCH used by the terminal device. Next, the configuration method for the second TCI state corresponding to the uplink physical shared channel (PUSCH) will be explained. For example, the first uplink shared channel is the uplink shared channel after the TCI state changes; that is, the first uplink shared channel is the uplink shared channel that the terminal device needs to use before the third TCI state is activated. The terminal device configures the second TCI state corresponding to the first uplink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel; that is, the terminal device uses the first TCI state corresponding to the first downlink shared channel of the RRC signaling.

[0163] S04. Before the third TCI state configured by the network device is activated after the TCI state changes, the terminal device uses the second TCI state for data transmission and reception.

[0164] In this embodiment, the first TCI state is the TCI state before the TCI state changes, and the third TCI state is the TCI state after the TCI state changes. Before the third TCI state is activated, the second TCI state configured above can be used for data transmission and reception in this embodiment. Since the second TCI state is the same as the first TCI state, the terminal device uses the reference signal pointed to by the first TCI state before the TCI state changes and no longer uses the prior art, thereby ensuring that the terminal device can correctly transmit and receive data when using the second TCI state.

[0165] In the prior art, when the TCI state changes, the reference signal pointed to by the TCI state is the reference signal when the terminal device initially accesses the cell. In this application embodiment, a completely different approach is adopted. That is, in this application embodiment, the second TCI state is configured according to the first TCI state configured by the network device before the TCI state changes. Before the new TCI state (i.e., the third TCI state) is activated by the network device, the terminal device can use the old TCI state (i.e., the first TCI state) as the currently available TCI state (i.e., the second TCI state). Using the reference signal pointed to by the old TCI state is more accurate and timely, which makes the data transmission performance better and thus can ensure the correct transmission and reception of data.

[0166] The foregoing embodiments based on steps S01 to S04 illustrate how the terminal device configures and uses the second TCI state. Next, we will explain how to configure and use the second TCI state from the network device side. It is understood that the configuration and use of the TCI state by the network device is similar to that by the terminal device. Only when the network device and the terminal device adopt the same second TCI state configuration method can the network device and the terminal device perform mutual data transmission and reception.

[0167] S11. When the Transmission Configuration Indicator (TCI) state configured by the network device changes, the network device obtains the first TCI state configured by the network device before the TCI state changes.

[0168] In this embodiment, the TCI state configured by the network device is used for data transmission and reception between the terminal device and the network device. The network device first determines whether its configured TCI state has changed. For example, a change in the beam used for data transmission between the terminal device and the network device can be considered a change in the configured TCI state. When the configured TCI state changes, the network device triggers the execution of subsequent step S12. When the configured TCI state does not change, the network device does not execute subsequent step S12.

[0169] In some embodiments of this application, such as Figure 4a and Figure 4b As shown, step S11, where the network device determines that the Transmission Configuration Indicator (TCI) state configured by the network device has changed, includes:

[0170] 401. The network device sends RRC signaling to the terminal device. The RRC signaling is used to instruct the terminal device to perform uplink or downlink bandwidth segment BWP handover. During BWP handover, the TCI state configured by the network device changes.

[0171] 402. The network device determines that the TCI status has changed based on the sent RRC signaling.

[0172] Specifically, network devices can send RRC signaling, which can trigger a BWP handover on the terminal device. During a BWP handover, the TCI state configured on the network device changes. Therefore, if a network device sends the aforementioned RRC signaling to a terminal device, the network device can determine that the TCI state has changed based on this RRC signaling.

[0173] In this embodiment, when the network device determines that its configured TCI state has changed, the network device first obtains a first TCI state, which is a TCI state configured by the network device before the change. For example, the first TCI state could be the most recently configured TCI state of the network device before the change. The first TCI state obtained by the network device will be different in different scenarios where the TCI state changes. The first TCI state obtained by the network device will be described in detail below.

[0174] In some embodiments of this application, such as Figure 4a As shown, in the scenario where the network device sends RRC signaling to the terminal device, step S11, where the network device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0175] 403a. The network device obtains the first TCI state corresponding to the first downlink control channel of the scheduling RRC signaling. The first downlink control channel is the downlink control channel before the TCI state changes.

[0176] The RRC signaling is scheduled by the first downlink control channel, which may be the PDCCH. This first downlink control channel is the downlink control channel before the TCI state changes, and the network device determines the TCI state corresponding to this first downlink control channel as the aforementioned first TCI state.

[0177] In some embodiments of this application, such as Figure 4b As shown, in the scenario where the network device sends RRC signaling to the terminal device, step S11, where the network device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0178] 403b. The network device obtains the first TCI state corresponding to the first downlink shared channel carrying RRC signaling. The first downlink shared channel is the downlink shared channel before the TCI state changes.

[0179] The RRC signaling can be carried by the first downlink shared channel, which may specifically be the PDSCH. This first downlink shared channel is the downlink shared channel before the TCI state changes, and the network device determines the TCI state corresponding to this first downlink shared channel as the aforementioned first TCI state.

[0180] S12. The network device is configured to have the same TCI state as the first TCI state. When the second TCI state and the first TCI state are the same TCI state, the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable.

[0181] In this embodiment, the network device first obtains the first TCI state configured by the network device before the TCI state changes, and then configures the second TCI state in the same way based on the first TCI state. The second TCI state refers to the TCI state that the network device can use before the third TCI state configured by the network device is activated after the TCI state changes. The reference signal pointed to by the second TCI state can be used by the network device and the terminal device for data transmission and reception.

[0182] In this embodiment, a TCI state where the second TCI state is the same as the first TCI state means that the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable, i.e., the reference signal pointed to by the second TCI state is configured according to the reference signal pointed to by the first TCI state. Quasi-co-addressability can include the second TCI state pointing to the same reference signal as the first TCI state. For example, when configuring the reference signal pointed to by the second TCI state, if the network device first obtains the reference signal pointed to by the first TCI state as ID#0, then the network device can configure the second TCI state to also point to the reference signal of ID#0. In this embodiment, by configuring the second TCI state to be the same as the first TCI state before the TCI state change, the data transmission failure caused by using the reference signal when the network device initially accesses the cell to configure the current TCI state in the prior art is avoided, enabling the reference signal pointed to by the second TCI state in this embodiment to be used for correct data transmission and reception.

[0183] In some embodiments of this application, such as Figure 4a As shown, in the scenario where the network device performs the aforementioned step 403a, step S12, where the network device configures the second TCI state to be the same as the first TCI state, includes:

[0184] 404. The network device is configured such that the second TCI state corresponding to the second downlink control channel is the same as the first TCI state corresponding to the first downlink control channel. The second downlink control channel is the downlink control channel after the TCI state changes.

[0185] The second downlink control channel is the downlink control channel used after the TCI state changes; that is, the second downlink control channel is the downlink control channel that the terminal device needs to use before the third TCI state is activated. The network device configures the second TCI state corresponding to the second downlink control channel to be the same as the first TCI state corresponding to the first downlink control channel, that is, the network device uses the first TCI state corresponding to the first downlink control channel of the scheduling RRC signaling.

[0186] Furthermore, in some embodiments of this application, when there are multiple second downlink control channels after the TCI state changes, the second TCI state corresponding to all the second downlink control channels is the same; or,

[0187] The number of second downlink control channels is the same as the number of first downlink control channels, and the second downlink control channels with the same channel identifier correspond to the same TCI state as the first downlink control channels; or,

[0188] When there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

[0189] When the TCI state configured in a network device changes, the network device can use multiple second downlink control channels, for example, three. All the second downlink control channels correspond to the same TCI state. As explained in the preceding embodiments, since the second TCI state is the same as the first TCI state, when multiple second downlink control channels exist after the TCI state changes, all of them continue to use the reference signal pointed to by the first TCI state for data transmission and reception. By configuring multiple second downlink control channels with the same second TCI state, the TCI state configuration of multiple second downlink control channels can be simplified, and correct data transmission and reception on multiple second downlink control channels can be guaranteed.

[0190] For example, taking the change of TCI state caused by BWP handover as an example, before the new TCI state is activated after the BWP handover, the UE assumes that the second TCI state corresponding to all downlink control channels is the same on the new BWP and points to the same set of reference signals (RS) pointed to by the first TCI state.

[0191] In some other embodiments of this application, the number of downlink control channels remains unchanged before and after the TCI state changes. That is, the number of second downlink control channels is the same as the number of first downlink control channels. For example, if there are 3 first downlink control channels before the TCI state changes, then there are also 3 second downlink control channels after the TCI state changes. Second downlink control channels with the same channel identifier correspond to the same TCI state as first downlink control channels, which simplifies the TCI state configuration of the second downlink control channels and ensures that data transmission and reception can be performed correctly on the second downlink control channels.

[0192] For example, if a BWP handover causes a change in the TCI state, and the number of downlink control channels in all BWPs configured in the network device is the same, and the TCI states of downlink control channels with the same channel ID before and after the BWP handover correspond, then the UE can assume that the TCI state of the corresponding downlink control channel is the same before and after the handover, before the new TCI state is activated after the BWP handover.

[0193] In other embodiments of this application, before the TCI state configured in the network device changes, the network device may use multiple first downlink control channels, for example, the network device may use three first downlink control channels. When there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel. That is, when there are multiple first downlink control channels, the first TCI state corresponding to the predefined downlink control channel can be used for the configuration of the second TCI state.

[0194] For example, taking the change in TCI state caused by BWP handover as an example, the second TCI state used after the BWP handover is the same as the TCI state of one of the downlink control channels in the original BWP. This downlink control channel can be a predefined downlink control channel or one of the downlink control channels used by the UE to receive RRC signaling. The predefined downlink control channel can be the downlink control channel corresponding to Physical Layer 1 ACKnowledgment, or another downlink control channel with a predefined ID, such as PDCCH#0 being a predefined downlink control channel.

[0195] In some embodiments of this application, such as Figure 4b As shown, in the scenario where the network device performs the aforementioned step 403b, step S12, where the network device configures the second TCI state to be the same as the first TCI state, includes:

[0196] 405. The network device is configured such that the second TCI state corresponding to the second downlink shared channel is the same as the first TCI state corresponding to the first downlink shared channel, and the second downlink shared channel is the downlink shared channel after the TCI state changes; or,

[0197] 406. The network device is configured such that the second TCI state corresponding to the first uplink shared channel is the same as the first TCI state corresponding to the first downlink shared channel. The first uplink shared channel is the uplink shared channel after the TCI state changes.

[0198] The second downlink shared channel is the downlink shared channel used after the TCI state changes; that is, the second downlink shared channel is the downlink shared channel that the network device needs to use before the third TCI state is activated. The network device configures the second TCI state corresponding to the second downlink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, that is, the network device uses the first TCI state corresponding to the first downlink shared channel of the scheduling RRC signaling.

[0199] The preceding content explained the configuration of the second TCI state corresponding to the PDCCH and PDSCH used by the network device. Next, the configuration method for the second TCI state corresponding to the PUSCH will be explained. For example, the first uplink shared channel is the uplink shared channel after the TCI state changes; that is, the first uplink shared channel is the uplink shared channel that the network device needs to use before the third TCI state is activated. The network device configures the second TCI state corresponding to the first uplink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel; that is, the network device uses the first TCI state corresponding to the first downlink shared channel of the RRC signaling.

[0200] S13. Before the third TCI state configured by the network device is activated after the TCI state changes, the network device uses the second TCI state for data transmission and reception.

[0201] In this embodiment, the first TCI state is the TCI state before the TCI state changes, and the third TCI state is the TCI state after the TCI state changes. Before the third TCI state is activated, the second TCI state configured above can be used for data transmission and reception in this embodiment. Since the second TCI state is the same as the first TCI state, the network device uses the reference signal pointed to by the first TCI state before the TCI state changes and no longer uses the prior art, thereby ensuring that the network device can correctly transmit and receive data when using the second TCI state.

[0202] It should be noted that the aforementioned steps S01 to S04 are executed by the terminal device, and the subsequent steps S11 to S13 are executed by the network device. There is no sequential relationship between the method steps executed by the terminal device and the method steps executed by the network device.

[0203] As can be seen from the examples in the foregoing embodiments, in this application embodiment, the second TCI state is configured based on the first TCI state configured by the network device before the TCI state changes. Before the new TCI state (i.e., the third TCI state) is activated by the network device, the network device can use the old TCI state (i.e., the first TCI state) as the currently available TCI state (i.e., the second TCI state). The reference signal pointed to by the old TCI state is more accurate and timely, which makes the data transmission performance better and thus can ensure the correct transmission and reception of data.

[0204] In the aforementioned embodiment, the BWP handover was triggered by the network device sending RRC signaling, resulting in a change in the TCI state. The following example illustrates this, using the network device sending downlink control information (DCI) to trigger the BWP handover and thus change the TCI state. The explanation will begin from the terminal device side.

[0205] In some embodiments of this application, such as Figure 5a and Figure 5b As shown, step S01, where the terminal device determines that the TCI status configured in the network device has changed, includes:

[0206] 501. The terminal device receives the DCI sent by the network device. The DCI is used to instruct the terminal device to perform uplink or downlink BWP handover. During BWP handover, the TCI state configured by the network device changes.

[0207] 502. The terminal device determines that the TCI status has changed based on the received DCI.

[0208] The network device can send a DCI (Distributed Control Interface) that triggers a BWP (Browser-Based Device) handover on the terminal device. This handover causes a change in the TCI (Tracking Control Interface) state configured on the network device. Therefore, if the terminal device receives the aforementioned DCI from the network device, it can determine that the TCI state has changed based on this DCI. For example, the network device sends a DCI to the terminal device, using a DCI format of 0_1 or 1_1, instructing the terminal device to switch to another BWP.

[0209] In some embodiments of this application, such as Figure 5aAs shown, step S02, where the terminal device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0210] 503a. The terminal device obtains the first TCI state corresponding to the third downlink control channel carrying the DCI, wherein the third downlink control channel is the downlink control channel before the TCI state changes.

[0211] The DCI is carried by a third downlink control channel, which may be a PDCCH. This third downlink control channel is the downlink control channel before the TCI state changes, and the terminal device determines the TCI state corresponding to this third downlink control channel as the aforementioned first TCI state.

[0212] In some embodiments of this application, such as Figure 5a As shown, step S03, configuring the terminal device to have a second TCI state that is the same as the first TCI state, includes:

[0213] 504. The terminal device is configured such that the second TCI state corresponding to the fourth downlink control channel is the same as the first TCI state corresponding to the third downlink control channel, and the fourth downlink control channel is the downlink control channel after the TCI state changes.

[0214] The fourth downlink control channel is the downlink control channel used after the TCI state changes; that is, the fourth downlink control channel is the downlink control channel that the terminal device needs to use before the third TCI state is activated. The terminal device configures the second TCI state corresponding to the fourth downlink control channel to be the same as the first TCI state corresponding to the third downlink control channel, that is, the terminal device uses the first TCI state corresponding to the third downlink control channel of the scheduling RRC signaling.

[0215] Furthermore, in some embodiments of this application, when there are multiple fourth downlink control channels after the TCI state changes, the second TCI state corresponding to all fourth downlink control channels is the same.

[0216] Alternatively, the number of fourth downlink control channels is the same as that of the third downlink control channels, and the fourth downlink control channels and the third downlink control channels with the same channel identifier correspond to the same TCI state;

[0217] When there are multiple third downlink control channels after the TCI state changes, the third downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

[0218] The description of the fourth downlink control channel is analogous to the description of the second downlink control channel, and the description of the third downlink control channel is analogous to the description of the first downlink control channel. They will not be described in detail here.

[0219] In some embodiments of this application, such as Figure 5a As shown, step S03, configuring the terminal device to have a second TCI state that is the same as the first TCI state, includes:

[0220] 505. The terminal device is configured such that the second TCI state corresponding to the third downlink shared channel is the same as the first TCI state corresponding to the third downlink control channel, and the third downlink shared channel is the downlink shared channel after the TCI state changes; or,

[0221] 506. The terminal device is configured such that the second TCI state corresponding to the second uplink shared channel is the same as the first TCI state corresponding to the third downlink control channel, and the second uplink shared channel is the uplink shared channel after the TCI state changes.

[0222] The third downlink shared channel is the downlink shared channel after the TCI state changes; that is, the third downlink shared channel is the downlink shared channel that the terminal device needs to use before the third TCI state is activated. The terminal device configures the second TCI state corresponding to the third downlink shared channel to be the same as the first TCI state corresponding to the third downlink control channel, that is, the terminal device uses the first TCI state corresponding to the third downlink control channel of the scheduling RRC signaling.

[0223] The preceding content explained the configuration of the second TCI state corresponding to the PDCCH and PDSCH used by the terminal device. Next, the configuration method for the second TCI state corresponding to the PUSCH will be explained. For example, the second uplink shared channel is the uplink shared channel after the TCI state changes; that is, the second uplink shared channel is the uplink shared channel that the terminal device needs to use before the third TCI state is activated. The terminal device configures the second TCI state corresponding to the second uplink shared channel to be the same as the first TCI state corresponding to the third downlink control channel; that is, the terminal device uses the first TCI state corresponding to the third downlink control channel of the RRC signaling.

[0224] In some embodiments of this application, such as Figure 5b As shown, step S02, where the terminal device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0225] 503b. The terminal device acquires the first TCI state corresponding to the fourth downlink shared channel or the third uplink shared channel, wherein the fourth downlink shared channel is the downlink shared channel before receiving the DCI, and the third uplink shared channel is the uplink shared channel before receiving the DCI.

[0226] The first TCI state obtained by the terminal device can correspond to the fourth downlink shared channel, and the first TCI state can also correspond to the third uplink shared channel.

[0227] In some embodiments of this application, such as Figure 5b As shown, step S03, configuring the terminal device to have a second TCI state that is the same as the first TCI state, includes:

[0228] 507. The terminal device is configured such that the second TCI state corresponding to the fifth downlink shared channel is the same as the first TCI state corresponding to the fourth downlink shared channel, and the fifth downlink shared channel is the downlink shared channel after the TCI state changes; or,

[0229] 508. The terminal device is configured such that the second TCI state corresponding to the fifth downlink shared channel is the same as the first TCI state corresponding to the third uplink shared channel; or,

[0230] 509. The terminal device is configured such that the second TCI state corresponding to the fourth uplink shared channel is the same as the first TCI state corresponding to the fourth downlink shared channel, and the fourth uplink shared channel is the uplink shared channel after the TCI state changes; or,

[0231] 510. The terminal device is configured such that the second TCI state corresponding to the fourth uplink shared channel is the same as the first TCI state corresponding to the third uplink shared channel.

[0232] In this embodiment, the fifth downlink shared channel is the downlink shared channel after the TCI state changes. The second TCI state corresponding to the fifth downlink shared channel can be configured based on the first TCI state corresponding to the fourth downlink shared channel, and the second TCI state corresponding to the fifth downlink shared channel can also be configured based on the first TCI state corresponding to the third uplink channel. Similarly, the fourth uplink shared channel is the uplink shared channel after the TCI state changes. The second TCI state corresponding to the fourth uplink shared channel can be configured based on the first TCI state corresponding to the fourth downlink shared channel, and the second TCI state corresponding to the fourth uplink shared channel can also be configured based on the first TCI state corresponding to the third uplink channel. Therefore, in this embodiment, the terminal device can use the first TCI state configured by the network device before the TCI state change when configuring the second TCI state corresponding to the fifth downlink shared channel and the second TCI state corresponding to the fourth uplink shared channel, thereby ensuring that data transmission and reception can be performed correctly on the fifth downlink shared channel and the fourth uplink shared channel.

[0233] In the foregoing embodiment, an example was given of a BWP handover triggered by a terminal device receiving a DCI sent by a network device, which caused a change in the TCI state. The following explanation will focus on the network device side.

[0234] In some embodiments of this application, such as Figure 6a and Figure 6b As shown, step S11, where the network device determines that the TCI status configured on the network device has changed, includes:

[0235] 601. The network device sends a DCI to the terminal device. The DCI is used to instruct the terminal device to perform uplink or downlink BWP handover. During BWP handover, the TCI state configured by the network device changes.

[0236] 602. The network device determines that the TCI status has changed based on the received DCI.

[0237] Network devices can send DCIs (Distributed Control Interfaces), which can trigger a BWP (Browser-Based Device) handover on the terminal device. This BWP handover causes a change in the TCI (Tracking Control Interface) state configured on the network device. Therefore, if a network device sends a DCI to a terminal device, it can determine that the TCI state has changed based on this DCI. For example, a network device sends a DCI to a terminal device, using a DCI format of 0_1 or 1_1, instructing the terminal device to switch to another BWP.

[0238] In some embodiments of this application, such as Figure 6a As shown, step S11, in which the network device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0239] 603a. The network device obtains the first TCI state corresponding to the third downlink control channel carrying the DCI, wherein the third downlink control channel is the downlink control channel before the TCI state changes.

[0240] The DCI is carried by a third downlink control channel, which may specifically be a PDCCH. This third downlink control channel is the downlink control channel before the TCI state changes, and the network device determines the TCI state corresponding to this third downlink control channel as the aforementioned first TCI state.

[0241] In some embodiments of this application, such as Figure 6a As shown, step S12, configuring the network device to have the same TCI state as the first TCI state, includes:

[0242] 604. The network device is configured such that the second TCI state corresponding to the fourth downlink control channel is the same as the first TCI state corresponding to the third downlink control channel, and the fourth downlink control channel is the downlink control channel after the TCI state changes.

[0243] The fourth downlink control channel is the downlink control channel used after the TCI state changes; that is, it is the downlink control channel that the network device needs to use before the third TCI state is activated. The network device configures the second TCI state corresponding to the fourth downlink control channel to be the same as the first TCI state corresponding to the third downlink control channel, meaning the network device uses the first TCI state corresponding to the third downlink control channel of the scheduling RRC signaling.

[0244] Furthermore, in some embodiments of this application, when there are multiple fourth downlink control channels after the TCI state changes, the second TCI state corresponding to all fourth downlink control channels is the same.

[0245] Alternatively, the number of fourth downlink control channels is the same as that of the third downlink control channels, and the fourth downlink control channels and the third downlink control channels with the same channel identifier correspond to the same TCI state;

[0246] When there are multiple third downlink control channels after the TCI state changes, the third downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

[0247] The description of the fourth downlink control channel is analogous to the description of the second downlink control channel, and the description of the third downlink control channel is analogous to the description of the first downlink control channel. They will not be described in detail here.

[0248] In some embodiments of this application, such as Figure 6a As shown, step S12, configuring the network device to have the same TCI state as the first TCI state, includes:

[0249] 605. The network device is configured such that the second TCI state corresponding to the third downlink shared channel is the same as the first TCI state corresponding to the third downlink control channel, and the third downlink shared channel is the downlink shared channel after the TCI state changes; or,

[0250] 606. The network device is configured such that the second TCI state corresponding to the second uplink shared channel is the same as the first TCI state corresponding to the third downlink control channel, and the second uplink shared channel is the uplink shared channel after the TCI state changes.

[0251] The third downlink shared channel is the downlink shared channel used after the TCI state changes; that is, the third downlink shared channel is the downlink shared channel that the network device needs to use before the third TCI state is activated. The network device configures the second TCI state corresponding to the third downlink shared channel to be the same as the first TCI state corresponding to the third downlink control channel, that is, the network device uses the first TCI state corresponding to the third downlink control channel of the scheduling RRC signaling.

[0252] The preceding content explained the configuration of the second TCI state corresponding to the PDCCH and PDSCH used by the network device. Next, the configuration method for the second TCI state corresponding to the PUSCH will be explained. For example, the second uplink shared channel is the uplink shared channel after the TCI state changes; that is, the second uplink shared channel is the uplink shared channel that the network device needs to use before the third TCI state is activated. The network device configures the second TCI state corresponding to the second uplink shared channel to be the same as the first TCI state corresponding to the third downlink control channel; that is, the network device uses the first TCI state corresponding to the third downlink control channel of the RRC signaling.

[0253] In some embodiments of this application, such as Figure 6b As shown, step S11, in which the network device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0254] 603b. The network device acquires the first TCI state corresponding to the fourth downlink shared channel or the third uplink shared channel, wherein the fourth downlink shared channel is the downlink shared channel before receiving the DCI, and the third uplink shared channel is the uplink shared channel before receiving the DCI.

[0255] The first TCI state obtained by the network device can correspond to the fourth downlink shared channel, and the first TCI state can also correspond to the third uplink shared channel.

[0256] In some embodiments of this application, such as Figure 6b As shown, step S12, configuring the network device to have the same TCI state as the first TCI state, includes:

[0257] 607. The network device is configured such that the second TCI state corresponding to the fifth downlink shared channel is the same as the first TCI state corresponding to the fourth downlink shared channel, and the fifth downlink shared channel is the downlink shared channel after the TCI state changes; or,

[0258] 608. The network device configures the second TCI state corresponding to the fifth downlink shared channel to be the same as the first TCI state corresponding to the third uplink shared channel; or,

[0259] 609. The network device is configured such that the second TCI state corresponding to the fourth uplink shared channel is the same as the first TCI state corresponding to the fourth downlink shared channel, and the fourth uplink shared channel is the uplink shared channel after the TCI state changes; or,

[0260] 610. The network device is configured such that the second TCI state corresponding to the fourth uplink shared channel is the same as the first TCI state corresponding to the third uplink shared channel.

[0261] In this embodiment, the fifth downlink shared channel is the downlink shared channel after the TCI state changes. The second TCI state corresponding to the fifth downlink shared channel can be configured based on the first TCI state corresponding to the fourth downlink shared channel, and the second TCI state corresponding to the fifth downlink shared channel can also be configured based on the first TCI state corresponding to the third uplink channel. Similarly, the fourth uplink shared channel is the uplink shared channel after the TCI state changes. The second TCI state corresponding to the fourth uplink shared channel can be configured based on the first TCI state corresponding to the fourth downlink shared channel, and the second TCI state corresponding to the fourth uplink shared channel can also be configured based on the first TCI state corresponding to the third uplink channel. Therefore, in this embodiment, the network device can use the first TCI state configured before the TCI state change when configuring the second TCI state corresponding to the fifth downlink shared channel and the second TCI state corresponding to the fourth uplink shared channel, thereby ensuring that data transmission and reception can be performed correctly on the fifth downlink shared channel and the fourth uplink shared channel.

[0262] The foregoing embodiments have provided a detailed description of BWP handover triggered by RRC signaling and DCI. Next, other scenarios that trigger BWP handover will be described.

[0263] In some embodiments of this application, such as Figure 7a and Figure 7b As shown, step S01, where the terminal device determines that the Transmission Configuration Indicator (TCI) state configured by the network device has changed, includes:

[0264] 701. When the timer jointly maintained by the terminal device and the network device expires, the terminal device performs uplink or downlink BWP handover.

[0265] The BWP handover causes a change in the TCI state configured on the network device, which is used for data transmission and reception between the terminal device and the network device.

[0266] In some embodiments of this application, such as Figure 7a As shown, step S02, where the terminal device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0267] 702a. When the duration corresponding to the timer is less than or equal to a preset threshold, the terminal device acquires the first TCI state before the timer was started; or,

[0268] 702b. When the duration exceeds a preset threshold, the terminal device measures the reference signal and sends an SSB identifier or a CSI-RS identifier to the network device. The terminal device then obtains the first TCI state corresponding to the SSB identifier or CSI-RS identifier.

[0269] The threshold is a pre-configured value for the network device, and its specific value is not limited here. Different methods are used to obtain the first TCI state based on the relationship between the timer duration and the threshold.

[0270] In some embodiments of this application, such as Figure 7a As shown, step S03, configuring the terminal device to have a second TCI state that is the same as the first TCI state, includes:

[0271] 703. The terminal device configures the second TCI state corresponding to the fifth downlink control channel to be the same as the first TCI state before the timer starts, and the fifth downlink control channel is the downlink control channel after the TCI state changes; or,

[0272] 704. The terminal device configures the second TCI state corresponding to the sixth downlink shared channel to be the same as the first TCI state before the timer starts, and the sixth downlink shared channel is the downlink shared channel after the TCI state changes; or,

[0273] 705. The terminal device is configured such that the second TCI state corresponding to the fifth uplink shared channel is the same as the first TCI state before the timer is started, and the fifth uplink shared channel is the uplink shared channel after the TCI state changes.

[0274] In the above embodiments of this application, the terminal device can use the first TCI state configured by the network device before the TCI state changes when configuring the second TCI state corresponding to the sixth downlink shared channel and the second TCI state corresponding to the fifth uplink shared channel, thereby ensuring that data can be correctly transmitted and received on the sixth downlink shared channel and the fifth uplink shared channel.

[0275] In some embodiments of this application, such as Figure 7b As shown, step S03, configuring the terminal device to have a second TCI state that is the same as the first TCI state, includes:

[0276] 706. The terminal device is configured such that the second TCI state corresponding to the fifth downlink control channel is the same as the first TCI state corresponding to the SSB identifier or CSI-RS identifier, and the fifth downlink control channel is the downlink control channel after the TCI state changes; or,

[0277] 707. The terminal device configures the second TCI state corresponding to the sixth downlink shared channel to be the same as the first TCI state corresponding to the SSB identifier or CSI-RS identifier, wherein the sixth downlink shared channel is the downlink shared channel after the TCI state changes; or,

[0278] 708. The terminal device is configured such that the second TCI state corresponding to the fifth uplink shared channel is the same as the first TCI state corresponding to the SSB identifier or CSI-RS identifier, and the fifth uplink shared channel is the uplink shared channel after the TCI state changes.

[0279] In the above embodiments of this application, the terminal device can use the first TCI state configured by the network device before the TCI state changes when configuring the second TCI state corresponding to the sixth downlink shared channel and the second TCI state corresponding to the fifth uplink shared channel, thereby ensuring that data can be correctly transmitted and received on the sixth downlink shared channel and the fifth uplink shared channel.

[0280] In some embodiments of this application, such as Figure 8a and Figure 8b As shown, step S11, in which the network device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0281] 801. When the duration corresponding to the timer is less than or equal to a preset threshold, the network device acquires the first TCI state prior to the timer's start; or,

[0282] 802. When the duration exceeds a preset threshold, the network device receives the SSB identifier or CSI-RS identifier reported by the terminal device, and the network device obtains the first TCI status corresponding to the SSB identifier or CSI-RS identifier.

[0283] The threshold is a pre-configured value for the network device, and its specific value is not limited here. Different methods are used to obtain the first TCI state based on the relationship between the timer duration and the threshold.

[0284] In some embodiments of this application, such as Figure 8a As shown, step S12, configuring the network device to have the same TCI state as the first TCI state, includes:

[0285] 803. The network device configures the second TCI state corresponding to the fifth downlink control channel to be the same as the first TCI state before the timer starts, and the fifth downlink control channel is the downlink control channel after the TCI state changes; or,

[0286] 804. The network device configures the second TCI state corresponding to the sixth downlink shared channel to be the same as the first TCI state before the timer starts, and the sixth downlink shared channel is the downlink shared channel after the TCI state changes; or,

[0287] 805. The network device configures the second TCI state corresponding to the fifth uplink shared channel to be the same as the first TCI state before the timer is started, and the fifth uplink shared channel is the uplink shared channel after the TCI state changes.

[0288] In the above embodiments of this application, the network device can use the first TCI state configured before the TCI state changed when configuring the second TCI state corresponding to the sixth downlink shared channel and the second TCI state corresponding to the fifth uplink shared channel, thereby ensuring that data can be correctly transmitted and received on the sixth downlink shared channel and the fifth uplink shared channel.

[0289] In some embodiments of this application, such as Figure 8b As shown, step S12, configuring the network device to have the same TCI state as the first TCI state, includes:

[0290] 806. The network device is configured such that the second TCI state corresponding to the fifth downlink control channel is the same as the first TCI state corresponding to the SSB identifier or CSI-RS identifier, and the fifth downlink control channel is the downlink control channel after the TCI state changes; or,

[0291] 807. The network device configures the second TCI state corresponding to the sixth downlink shared channel to be the same as the first TCI state corresponding to the SSB identifier or CSI-RS identifier, and the sixth downlink shared channel is the downlink shared channel after the TCI state changes; or,

[0292] 808. The network device is configured such that the second TCI state corresponding to the fifth uplink shared channel is the same as the first TCI state corresponding to the SSB identifier or CSI-RS identifier, and the fifth uplink shared channel is the uplink shared channel after the TCI state changes.

[0293] In the above embodiments of this application, the network device can use the first TCI state configured before the TCI state changed when configuring the second TCI state corresponding to the sixth downlink shared channel and the second TCI state corresponding to the fifth uplink shared channel, thereby ensuring that data can be correctly transmitted and received on the sixth downlink shared channel and the fifth uplink shared channel.

[0294] In some embodiments of this application, such as Figure 9 As shown, step S01, where the terminal device determines that the Transmission Configuration Indicator (TCI) state configured by the network device has changed, includes:

[0295] 901. When a random access procedure is triggered, the terminal device performs uplink or downlink BWP switching to perform the random access procedure;

[0296] The BWP handover causes a change in the TCI state configured on the network device, which is used for data transmission and reception between the terminal device and the network device.

[0297] In some embodiments of this application, such as Figure 9 As shown, step S11, in which the terminal device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0298] 902. When the terminal device is in a connected state, the terminal device obtains a random access trigger instruction, which is used to instruct the terminal device to obtain random access channel (RACH) resources.

[0299] 903. The terminal device obtains the first TCI state corresponding to the reference signal associated with the RACH resource.

[0300] In some embodiments of this application, such as Figure 9 As shown, step S03, configuring the terminal device to have a second TCI state that is the same as the first TCI state, includes:

[0301] 904. The terminal device is configured such that the second TCI state corresponding to the sixth downlink control channel is the same as the first TCI state corresponding to the reference signal associated with the RACH resource, and the sixth downlink control channel is the downlink control channel after the TCI state changes; or,

[0302] 905. The terminal device is configured such that the second TCI state corresponding to the seventh downlink shared channel is the same as the first TCI state corresponding to the reference signal associated with the RACH resource, and the seventh downlink shared channel is the downlink shared channel after the TCI state changes; or,

[0303] 906. The terminal device is configured such that the second TCI state corresponding to the sixth uplink shared channel is the same as the first TCI state corresponding to the reference signal associated with the RACH resource, and the sixth uplink shared channel is the uplink shared channel after the TCI state changes.

[0304] In the above embodiments of this application, the terminal device can use the first TCI state configured by the network device before the TCI state changes when configuring the second TCI state corresponding to the seventh downlink shared channel and the second TCI state corresponding to the sixth uplink shared channel, thereby ensuring that data can be correctly transmitted and received on the seventh downlink shared channel and the sixth uplink shared channel.

[0305] In some embodiments of this application, such as Figure 10 As shown, step S11, in which the network device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0306] 1001. The network device sends a random access trigger instruction to the terminal device, the random access trigger instruction being used to instruct the terminal device to acquire RACH resources;

[0307] 1002. The network device obtains the first TCI state corresponding to the reference signal associated with the RACH resource.

[0308] In some embodiments of this application, such as Figure 10 As shown, step S12, configuring the network device to have the same TCI state as the first TCI state, includes:

[0309] 1003. The network device is configured such that the second TCI state corresponding to the sixth downlink control channel is the same as the first TCI state corresponding to the reference signal associated with the RACH resource, and the sixth downlink control channel is the downlink control channel after the TCI state changes; or,

[0310] 1004. The network device configures the second TCI state corresponding to the seventh downlink shared channel to be the same as the first TCI state corresponding to the reference signal associated with the RACH resource, and the seventh downlink shared channel is the downlink shared channel after the TCI state changes; or,

[0311] 1005. The network device is configured such that the second TCI state corresponding to the sixth uplink shared channel is the same as the first TCI state corresponding to the reference signal associated with the RACH resource, and the sixth uplink shared channel is the uplink shared channel after the TCI state changes.

[0312] In the above embodiments of this application, the network device can use the first TCI state configured before the TCI state changed when configuring the second TCI state corresponding to the seventh downlink shared channel and the second TCI state corresponding to the sixth uplink shared channel, thereby ensuring that data can be correctly transmitted and received on the seventh downlink shared channel and the sixth uplink shared channel.

[0313] In some embodiments of this application, step S01, in which the terminal device determines that the Transmission Configuration Indicator (TCI) state configured by the network device has changed, includes:

[0314] During the activation of the secondary cell, the terminal device determines that the first reference signal used for channel quality indicator (CQI) measurement on the secondary cell is not configured with a TCI state.

[0315] In some embodiments of this application, step S02, in which the terminal device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0316] The terminal device determines the first TCI state corresponding to the second reference signal reported by the terminal device to the network device.

[0317] In some embodiments of this application, step S03, which involves configuring the terminal device to have the same TCI state as the first TCI state, includes:

[0318] The terminal device is configured such that the second TCI state corresponding to the first reference signal is the same as the first TCI state corresponding to the second reference signal; or...

[0319] The terminal device is configured such that the second TCI state corresponding to the seventh downlink control channel is the same as the first TCI state corresponding to the second reference signal, and the seventh downlink control channel is the downlink control channel after the TCI state changes; or...

[0320] The terminal device is configured such that the second TCI state corresponding to the eighth downlink shared channel is the same as the first TCI state corresponding to the second reference signal, and the eighth downlink shared channel is the downlink shared channel after the TCI state changes.

[0321] In some embodiments of this application, step S11, in which the network device obtains the first TCI state configured by the network device before the TCI state changes, includes:

[0322] The network device determines the first TCI state corresponding to the second reference signal reported by the network device to the network device.

[0323] In some embodiments of this application, step S12, in which the network device configures the second TCI state to be the same as the first TCI state, includes:

[0324] The network device is configured such that the second TCI state corresponding to the first reference signal is the same as the first TCI state corresponding to the second reference signal; or...

[0325] The network device is configured such that the second TCI state corresponding to the seventh downlink control channel is the same as the first TCI state corresponding to the second reference signal, and the seventh downlink control channel is the downlink control channel after the TCI state changes; or...

[0326] The network device is configured such that the second TCI state corresponding to the eighth downlink shared channel is the same as the first TCI state corresponding to the second reference signal, and the eighth downlink shared channel is the downlink shared channel after the TCI state changes.

[0327] For example, during the activation process of a secondary cell, if the CSI-RS used for Channel Quality Indicator (CQI) measurement on the secondary cell is not configured with a TCI state, the terminal device reports the SSB identifier or CSI-RS identifier representing the TCI state on the secondary cell to the network device during the activation process. After reporting, before receiving the TCI state of the CSI-RS used for CQI measurement configured by the network device, the terminal device considers the CSI-RS used for CQI measurement and the reported SSB or CSI-RS to be quasi-co-located, that is, the CSI-RS used for CQI measurement and the reported SSB or CSI-RS correspond to the same TCI state. After the activation process is completed, before receiving the TCI state configured or activated by the network device for PDCCH and PDSCH reception, the terminal device considers the PDCCH and PDSCH to be quasi-co-located with the reported SSB or CSI-RS, that is, the CSI-RS of the PDCCH and PDSCH correspond to the same TCI state as the reported SSB or CSI-RS.

[0328] In the above embodiments of this application, the terminal device determines the SSB identifier or CSI-RS identifier representing the TCI state through the L1-RSRP measurement process of the secondary cell activation process, or the terminal device determines the SSB identifier or CSI-RS identifier representing the TCI state through the cell detection or automatic gain control (AGC) adjustment process before or during the secondary cell activation process.

[0329] To facilitate a better understanding and implementation of the above-described solutions in the embodiments of this application, specific examples of corresponding application scenarios are provided below.

[0330] This embodiment of the application uses the example of a change in the TCI state configured by the network device when the network device instructs the terminal device to perform a BWP handover. Specifically, the network device is a base station, and the terminal device is a UE. In this embodiment, after the BWP handover but before the TCI state is activated, the UE and the network device need to determine the transmission beams of the scheduling PDCCH and PDSCH through a predefined method, that is, the method for determining the target reference signal of the quasi-co-located (QCL) relationship of the corresponding DMRS ports.

[0331] In the embodiments of this application, the types of BWP handover can include the following four: BWP handover caused by RRC signaling, BWP handover triggered by DCI, BWP handover to default BWP after timer timeout, and BWP activated during random access without RACH resources, requiring the UE to switch BWP to initial uplink BWP, etc.

[0332] In this embodiment of the application, after BWP handover and before the TCI state activation command is issued, in order to ensure that the UE can correctly send and receive data, the RS that the TCI state of the DMRS port of the PDCCH or PDSCH assumed by the UE should point to can include the following three implementation methods:

[0333] 1. After the UE performs a BWP handover triggered by RRC signaling or DCI, before the network activates a new TCI state, the UE assumes that the DMRS ports of PDCCH, PDSCH, and PUSCH are quasi-co-addressable with the PDCCH or PDSCH used when receiving RRC or DCI on the original BWP.

[0334] 2. After a timer-triggered BWP handover, if the timer's duration is less than a certain threshold, the UE assumes that the DMRS ports of the PDCCH, PDSCH, and PUSCH are quasi-co-located with the PDCCH, PDSCH, or PUSCH before the BWP handover. If the timer's duration exceeds the threshold, the UE needs to perform L1-RSRP measurement and reporting. At this time, the UE and the network device determine, based on the reported reference signal ID, that after the BWP handover, before the network device activates a new TCI state, the DMRS ports of the UE's PDCCH, PDSCH, and PUSCH are quasi-co-located with the reference signal corresponding to the reported reference signal ID.

[0335] 3. After a MAC layer-triggered BWP handover or a random access-triggered BWP handover, the UE assumes that the DMRS ports of the PDCCH, PDSCH, and PUSCH are quasi-co-located with the SSB or CSI-RS associated with the UE's RACH resources. Random access will be associated with a reference signal, and RACH triggered by beam failure (BF) will be associated with the CSI-RS.

[0336] In this embodiment of the application, both the UE and the base station need to ensure the TCI correspondence of the control channel resources set (CORESET) before and after the BWP handover.

[0337] If all BWPs configured on the network device have the same number of CORESETs and the CORESETs with the same ID have corresponding TCI states, then the UE can assume that the TCI states on the corresponding CORESETs are the same before and after the BWP switch and before the new TCI state is activated.

[0338] Before the new TCI state is activated after the BWP handover, the UE assumes that all CORESETs have the same TCI state and point to the same set of TCI RS on the new BWP. This TCI state is the same as one of the CORESET TCI states in the original BWP. This CORESET can be a predefined CORESET or one of the CORESETs used by the UE to receive RRC signaling and DCI. The predefined CORESET is the CORESET and its TCI state corresponding to L1 ACK; or another predefined CORESET ID, such as CORESET#0.

[0339] In this embodiment, both the UE and the base station need to ensure the TCI correspondence of the PDSCH before and after the BWP handover, requiring the UE to continue using the TCI state corresponding to the PDSCH used to receive RRC signaling on the old BWP. If the handover is triggered by DCI, the UE continues to use the TCI state corresponding to the PDCCH used to receive DCI on the old BWP. Alternatively, the UE continues to use the TCI state corresponding to the PDSCH before the DCI.

[0340] The first embodiment of this application's solution is described in detail below. For BWP handover triggered by RRC signaling, after the handover, the UE assumes that the network device schedules the transmission beams of PDSCH and PDCCH on the new BWP to be the same as the RRC signaling for BWP handover sent on the old BWP. That is, the TCI states of PDCCH and PDSCH on the new BWP point to the target reference signal corresponding to the TCI state of the RRC signaling. The following explanation uses the UE configuring the TCI state as an example. The configuration method of the network device for the TCI state is similar to that performed by the UE, and will not be repeated here. This embodiment mainly includes the following steps:

[0341] Step S21: The network device configures a new first active downlink bandwidth segment identifier (firstActiveDownlinkBWP-Id) to the UE to instruct the UE to switch BWP to this BWP. This RRC signaling is scheduled by the corresponding CORESET, that is, scheduled by PDCCH and carried by the corresponding PDSCH.

[0342] Step S22: The UE receives PDCCH according to the candidate reference signal pointed to by the TCI state in the CORESET configuration and the TCI state reference signal activated by MAC CE, and receives PDSCH data according to the candidate reference signal pointed to by the PDSCH configuration, the candidate reference signal pointed to by the MAC CE activated, and the reference signal indicated by DCI.

[0343] For the TCI state corresponding to PDCCH, the network device first configures up to 64 candidate target reference signals using higher-layer parameters, and then activates one of them through MAC CE. For the TCI state corresponding to PDSCH, the network device first configures 64 candidate target reference signals using higher-layer parameters, then semi-dynamically activates eight of them using MAC CE, and finally uses DCI to determine which reference signal the UE will use before each transmission.

[0344] Step S23: The UE performs BWP handover according to RRC signaling.

[0345] During the BWP switch, the TCI status of the PDCCH and PDSCH on the new BWP has not yet been activated by the corresponding MAC CE.

[0346] Step S24a: The UE assumes that all CORESETs on the new BWP have the same TCI state and are the same as one of the CORESETs that the UE used to schedule the BWP handover RRC signaling on the old BWP. If multiple CORESETs simultaneously schedule the RRC message carrying the command, the UE assumes that the CORESET corresponding to the L1 ACK is the one that is being fed back.

[0347] Step S24b: The UE assumes that all CORESETs on the new BWP have the same TCI status and are the same as one of the CORESETs on the old BWP. This CORESET can be CORESET#0 or a common search space, such as the CORESET with the smallest ID number.

[0348] Step S24c: The UE assumes that the TCI status of each CORESET on the new BWP is the same as the TCI status of the corresponding CORESET with the same CORESET ID number on the old BWP.

[0349] Step S25: After determining the TCI state of the PDCCH, the UE needs to assume the TCI state of the corresponding PDSCH to receive data, including the corresponding data of the bearer MAC CE.

[0350] Step S26: The UE assumes that the TCI state of the PDSCH on the new BWP is the same as the TCI state of the PDSCH on the old BWP that carries the RRC signaling indicating the BWP handover.

[0351] Step S27: After the UE uses the above-mentioned TCI state assumptions of PDCCH and PDSCH, and successfully receives the new BWP's TCI state activation MAC CE, it uses the newly activated TCI state to send and receive data.

[0352] It should be noted that the above steps S24a, S24b and S24c are related by OR, and may involve different signaling transmission methods.

[0353] As illustrated by the foregoing examples, the UE can correctly assume the QCL relationship and correctly receive the PDCCH and PDSCH after a BWP handover triggered by RRC signaling but before the TCI state is activated. Compared to the existing technology where the TCI state is configured to point to the SSB, the TCI state target reference signal using the old BWP scheduling data is more accurate and timely, resulting in better performance. Using the SSB may require the UE to remeasure the SSB for beam management, or its performance may be poor due to the long recording time.

[0354] The second embodiment of this application's solution is described below, focusing on DCI-triggered BWP handover. The following explanation uses UE configuration of TCI state as an example. The configuration method for TCI state by the network device is similar to that performed by the UE, and will not be repeated here. This embodiment mainly includes the following steps:

[0355] Step S31: The network device sends a DCI format 0_1 ​​or 1_1 to the UE, instructing the UE to switch to another BWP.

[0356] Step S32: The UE receives the DCI according to the candidate reference signal pointed to by the TCI state in the CORESET configuration and the TCI state reference signal activated by the MAC CE.

[0357] Step S33: The UE performs BWP handover based on the DCI.

[0358] During the BWP switch, the TCI status of the PDCCH and PDSCH on the new BWP has not yet been activated by the corresponding MAC CE.

[0359] Step S34a: The UE assumes that the TCI status of all CORESETs on the new BWP is the same and that the CORESET of the DCI used by the UE to schedule the BWP handover on the old BWP is the same.

[0360] Step S34b: The UE assumes that all CORESETs on the new BWP have the same TCI status and are the same as one of the CORESETs on the old BWP. This CORESET can be CORESET#0 or a general search space, such as the CORESET with the smallest ID number.

[0361] Step S34c: The UE assumes that the TCI status of each CORESET on the new BWP is the same as the TCI status of the corresponding CORESET with the same CORESET ID number on the old BWP.

[0362] Step S35: After determining the TCI state of the PDCCH, the UE needs to assume the TCI state of the corresponding PDSCH to receive data, including the corresponding data of the bearer MAC CE.

[0363] Step S36a: The UE assumes that the TCI state of the PDSCH on the new BWP is the same as the TCI state of the DCI that the UE receives and sends the BWP handover command on the old BWP.

[0364] Step S36b: The UE assumes that the TCI state of the PDSCH on the new BWP is the same as the TCI state of the UE when receiving the PDSCH or sending the PUSCH on the old BWP. The PDSCH was scheduled in the subframe, time slot or symbol preceding the DCI of the BWP handover command.

[0365] Step S37: After the UE uses the above-mentioned TCI state assumptions of PDCCH and PDSCH, and successfully receives the new BWP's TCI state activation MAC CE, it uses the newly activated TCI state to send and receive data.

[0366] It should be noted that steps S34a, S34b, and S34c are related by OR, and may involve different signaling transmission methods. Steps S36a and S36b are also related by OR, and may involve different signaling transmission methods.

[0367] This second embodiment is similar to the first embodiment described above, except that RRC signaling has not only PDCCH scheduling but also PDSCH carrying data, while DCI only has PDCCH and no PDSCH data.

[0368] As illustrated by the examples above, the UE can correctly assume the QCL relationship and correctly receive the PDCCH and PDSCH after the BWP handover triggered by DCI and before the TCI state is activated.

[0369] The third embodiment of this application's scheme is described in detail below. For BWP handover triggered by timer expiration, if the timer length is less than a certain threshold, the UE assumes the same TCI state as the original BWP. If the timer length is greater than or equal to the threshold, the UE needs to perform L1 RSRP measurement and reporting, and determine the new TCI state. The following explanation uses UE TCI state configuration as an example. The configuration method of the network device for the TCI state is similar to that performed by the UE, and will not be repeated here. This embodiment mainly includes the following steps:

[0370] Step S41: The inactivity timer maintained by both the network device and the UE for BWP handover times out. At this point, the UE needs to switch its uplink and downlink BWPs to the default BWP. The value of this timer represents the duration for which the UE has not been scheduled by the network.

[0371] Step S42a: When the value of the timer is less than or equal to a threshold, if the UE needs to send and receive data after switching to the default BWP, before the TCI state is activated, it can be assumed that the TCI state is the same as the TCI state used for sending and receiving data in the last subframe / slot / symbol before the timer was started on the old BWP.

[0372] Step S42b: When the value of the timer is greater than the threshold, if the UE needs to send or receive data after switching to the default BWP, it needs to perform an RSRP measurement and report.

[0373] Step S43: After the UE uses the above-mentioned TCI state assumptions of PDCCH and PDSCH, and successfully receives the new BWP's TCI state activation MAC CE, it uses the newly activated TCI state to send and receive data.

[0374] It should be noted that steps S42a and S42b mentioned above are OR relationships, which may involve different signaling transmission methods. The relationship between the timer and the threshold means that when the UE has not been scheduled for a relatively long period of time, the UE should not be required to retain the beam information used during scheduling and transmission before that time. There are various specific values ​​or calculation methods for this threshold, which are not limited here.

[0375] As illustrated by the foregoing examples, in the embodiments of this application, the UE can correctly assume the QCL relationship and correctly receive the PDCCH and PDSCH after the BWP handover triggered by the timer timeout and before the TCI state is activated.

[0376] The fourth embodiment of this application is described in detail below. For RACH-triggered BWP handover, the UE's assumed TCI state should point to the SSB or CSI-RS associated with the PRACH resource. The following explanation uses UE TCI state configuration as an example. The network device's TCI state configuration method is similar to the UE's configuration method, and will not be repeated here. This embodiment mainly includes the following steps:

[0377] Step S51: After the RACH in the connected state is triggered, the UE needs to switch BWP for random access. Before the TCI state is activated, the UE needs to assume that the TCI state points to the reference signal associated with the PRACH resource, which may be SSB or CSI-RS.

[0378] Step S52a: When the reference signal associated with the above PRACH resource configuration is a certain SSB, before the TCI state is activated, the UE can assume that the TCI state of the DMRS port of PDCCH and PDSCH points to the SSB.

[0379] Step S52b: When the reference signal associated with the above PRACH resource configuration is a certain CSI-RS, before the TCI state is activated, the UE can assume that the TCI state of the DMRS port of PDCCH and PDSCH points to the CSI-RS.

[0380] Step S53: After the UE uses the TCI state assumptions of the PDCCH and PDSCH as described above, it sends message 1 (msg1) to access the network. After successfully accessing the network and receiving the TCI state activation MAC CE of the new BWP, it uses the newly activated TCI state to send and receive data.

[0381] It should be noted that steps S52a and S52b mentioned above are OR relationships, which may involve different signaling transmission methods. In the PRACH configuration based on the NR system, PRACH resources based on non-contention-based random access can be associated with SSB or CSI-RS, but contention-based RACH can only be associated with SSB.

[0382] As illustrated by the foregoing examples, in the embodiments of this application, the UE can correctly assume the QCL relationship and correctly perform random access after the BWP handover triggered by RACH and before the TCI state is activated.

[0383] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0384] To facilitate better implementation of the above-described solutions in the embodiments of this application, related apparatus for implementing the above-described solutions is also provided below.

[0385] This application also provides a terminal device that performs the aforementioned... Figure 2 , Figure 3a , Figure 3b , Figure 5a , Figure 5b , Figure 7a , Figure 7b , Figure 9 The state configuration method executed by the terminal device, such as Figure 11 As shown, the terminal device 1100 provided in this embodiment includes:

[0386] Processing unit 1101 is used to determine that the Transmission Configuration Indicator (TCI) status of the network device configuration has changed;

[0387] The processing unit 1101 is further configured to obtain the first TCI state configured by the network device before the TCI state changes;

[0388] The processing unit 1101 is further configured to configure the second TCI state to be the same TCI state as the first TCI state. When the second TCI state is the same TCI state as the first TCI state, the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable.

[0389] Transceiver unit 1102 is used to transmit and receive data using the second TCI state before the third TCI state configured by the network device is activated after the TCI state changes.

[0390] In some embodiments of this application, the transceiver unit 1102 is further configured to receive Radio Resource Configuration (RRC) signaling sent by the network device, wherein the RRC signaling is used to instruct the terminal device to perform uplink or downlink bandwidth segment (BWP) switching, wherein the BWP switching causes a change in the TCI state configured by the network device.

[0391] The processing unit 1101 is specifically used to determine that the TCI state has changed based on the received RRC signaling.

[0392] In some embodiments of this application, the processing unit 1101 is specifically used to obtain the first TCI state corresponding to the first downlink control channel that schedules the RRC signaling, wherein the first downlink control channel is the downlink control channel before the TCI state changes.

[0393] In some embodiments of this application, the processing unit 1101 is specifically configured to configure the second TCI state corresponding to the second downlink control channel to be the same as the first TCI state corresponding to the first downlink control channel, wherein the second downlink control channel is the downlink control channel after the TCI state changes.

[0394] In some embodiments of this application, when there are multiple second downlink control channels after the TCI state changes, the second TCI state corresponding to all the second downlink control channels is the same; or,

[0395] The number of second downlink control channels is the same as that of the first downlink control channels, and the second downlink control channels with the same channel identifier and the first downlink control channels correspond to the same TCI state; or,

[0396] When there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

[0397] In some embodiments of this application, the processing unit 1101 is specifically used to obtain the first TCI state corresponding to the first downlink shared channel carrying the RRC signaling, wherein the first downlink shared channel is the downlink shared channel before the TCI state changes.

[0398] In some embodiments of this application, the processing unit 1101 is specifically configured to configure the second TCI state corresponding to the second downlink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the second downlink shared channel is the downlink shared channel after the TCI state changes; or,

[0399] The processing unit 1101 is specifically configured to configure the second TCI state corresponding to the first uplink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the first uplink shared channel is the uplink shared channel after the TCI state changes.

[0400] The terminal device in this embodiment can be referred to as... Figure 12 The device shown includes a processor 1201, an application processor, memory, a user interface, and other components (including a power supply, etc., not shown). Figure 12 In this embodiment, the processing unit can be the processor 1201, which performs the corresponding functions. The transmitting unit and / or receiving unit can be the wireless transceiver 1203 shown in the figure, which performs the corresponding functions through an antenna. It is understood that the various components shown in the figure are only schematic and are not essential components for completing this embodiment.

[0401] The terminal device in this embodiment can be referred to as... Figure 13 The device shown. As an example, this device can perform similar tasks. Figure 12 The functions of the processor. Figure 13 The device includes a processor 1301, a data transmitting processor 1303, and a data receiving processor 1305. Figure 13 In this context, the aforementioned processing unit can be the processor 1301, and it performs the corresponding functions. The sending unit can be... Figure 13 The data transmission processor 1303 in the middle, the receiving unit may be Figure 13 The receiving data processor 1305 is included. Although the channel encoder and channel decoder are shown in the figure, it is understood that these modules are not intended to limit this embodiment and are merely illustrative.

[0402] Figure 14This illustrates another form of the embodiment. The processing device 1400 includes modules such as a modulation subsystem, a central processing subsystem, and a peripheral subsystem. The terminal device in this embodiment can serve as the modulation subsystem. Specifically, the modulation subsystem may include a processor 1403 and an interface 1404. The processor 1403 performs the functions of the aforementioned processing unit, and the interface 1404 performs the functions of the aforementioned transmitting unit and / or receiving unit. As another variation, the modulation subsystem includes a memory 1406, a processor 1403, and a program stored in the memory and executable on the processor. When the processor executes the program, it implements the method embodiment executed by the aforementioned terminal device. It should be noted that the memory 1406 may be non-volatile or volatile, and its location may be inside the modulation subsystem or within the processing device 1400, as long as the memory 1406 can be connected to the processor 1403.

[0403] As another embodiment of this invention, a computer-readable storage medium is provided, on which instructions are stored, when executed, to perform the method executed by a terminal device.

[0404] It should be noted that the information interaction and execution process between the modules / units of the above-mentioned device are based on the same concept as the method embodiments of this application, and the resulting technical effects are the same as those of the method embodiments of this application. For details, please refer to the description in the method embodiments shown above in this application, and will not be repeated here.

[0405] This application also provides a network device that performs the aforementioned functions. Figure 2 , Figure 4a , Figure 4b , Figure 6a , Figure 6b , Figure 8a , Figure 8b , Figure 10 The state configuration methods executed by network devices, such as Figure 15 As shown, the network device 1500 provided in this application embodiment includes:

[0406] Processing unit 1501 is configured to obtain the first TCI state of the network device before the change of the TCI state when the Transmission Configuration Indicator (TCI) state configured by the network device changes.

[0407] The processing unit 1501 is further configured to configure the second TCI state to be the same as the first TCI state. When the second TCI state is the same as the first TCI state, the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable.

[0408] Transceiver unit 1502 is used to transmit and receive data using the second TCI state before the third TCI state configured by the network device is activated after the TCI state changes.

[0409] In some embodiments of this application, the transceiver unit 1502 is further configured to send Radio Resource Configuration (RRC) signaling to the terminal device, wherein the RRC signaling is used to instruct the terminal device to perform uplink or downlink bandwidth segment (BWP) switching, wherein the BWP switching causes a change in the TCI state configured by the network device.

[0410] The processing unit 1501 is specifically used to determine that the TCI status has changed based on the sent RRC signaling.

[0411] In some embodiments of this application, the processing unit 1501 is specifically used to obtain the first TCI state corresponding to the first downlink control channel that schedules the RRC signaling, wherein the first downlink control channel is the downlink control channel before the TCI state changes.

[0412] In some embodiments of this application, the processing unit 1501 is specifically configured to configure the second TCI state corresponding to the second downlink control channel to be the same as the first TCI state corresponding to the first downlink control channel, wherein the second downlink control channel is the downlink control channel after the TCI state changes.

[0413] In some embodiments of this application, when there are multiple second downlink control channels after the TCI state changes, the second TCI state corresponding to all the second downlink control channels is the same; or,

[0414] The number of second downlink control channels is the same as that of the first downlink control channels, and the second downlink control channels with the same channel identifier and the first downlink control channels correspond to the same TCI state; or,

[0415] When there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

[0416] In some embodiments of this application, the processing unit 1501 is specifically used to obtain the first TCI state corresponding to the first downlink shared channel carrying the RRC signaling, wherein the first downlink shared channel is the downlink shared channel before the TCI state changes.

[0417] In some embodiments of this application, the processing unit 1501 is specifically configured to configure the second TCI state corresponding to the second downlink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the second downlink shared channel is the downlink shared channel after the TCI state has changed; or,

[0418] The processing unit 1501 is specifically configured to configure the second TCI state corresponding to the first uplink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the first uplink shared channel is the uplink shared channel after the TCI state changes.

[0419] It should be noted that the information interaction and execution process between the modules / units of the above-mentioned device are based on the same concept as the method embodiments of this application, and the resulting technical effects are the same as those of the method embodiments of this application. For details, please refer to the description in the method embodiments shown above in this application, and will not be repeated here.

[0420] The network device in this embodiment can be referred to as... Figure 16 The device shown includes a processor 1601, an application processor, memory, a user interface, and other components (including a power supply, etc., not shown). Figure 16 In this embodiment, the processing unit may be the processor 1601, which performs the corresponding functions. The transmitting unit and / or receiving unit may be the wireless transceiver 1603 shown in the figure, which performs the corresponding functions through an antenna. It is understood that the various components shown in the figure are only schematic and are not essential components for completing this embodiment.

[0421] The network device in this embodiment can be referred to as... Figure 17 The device shown. As an example, this device can perform similar tasks. Figure 16 The functions of the processor. Figure 17 The device includes a processor 1701, a data transmitting processor 1703, and a data receiving processor 1705. Figure 17 In this context, the aforementioned processing unit can be the processor 1701, and it performs the corresponding functions. The sending unit can be... Figure 17 The data transmission processor 1703 in the middle, the receiving unit may be Figure 17 The receiving data processor 1705 is included. Although the channel encoder and channel decoder are shown in the figure, it is understood that these modules are not intended to limit this embodiment and are merely illustrative.

[0422] Figure 18This illustrates another form of the embodiment. The processing device 1800 includes modules such as a modulation subsystem, a central processing subsystem, and a peripheral subsystem. In this embodiment, the network device can serve as the modulation subsystem. Specifically, the modulation subsystem may include a processor 1803 and an interface 1804. The processor 1803 performs the functions of the aforementioned processing unit, and the interface 1804 performs the functions of the aforementioned transmitting unit and / or receiving unit. As another variation, the modulation subsystem includes a memory 1806, a processor 1803, and a program stored in the memory and executable on the processor. When the processor executes the program, it implements the method embodiment executed by the aforementioned network device. It should be noted that the memory 1806 can be non-volatile or volatile, and its location can be inside the modulation subsystem or within the processing device 1800, as long as the memory 1806 can be connected to the processor 1803.

[0423] As another embodiment of this invention, a computer-readable storage medium is provided that stores instructions which, when executed, perform the method performed by a network device.

[0424] It should be noted that the information interaction and execution process between the modules / units of the above-mentioned device are based on the same concept as the method embodiments of this application, and the resulting technical effects are the same as those of the method embodiments of this application. For details, please refer to the description in the method embodiments shown above in this application, and will not be repeated here.

[0425] In another possible design, when the device is an in-device chip, the chip includes a processing unit and a communication unit. The processing unit may be, for example, a processor, and the communication unit may be, for example, an input / output interface, pins, or circuitry. The processing unit can execute computer-executable instructions stored in a storage unit to cause the chip within the device to perform any of the wireless communication methods described in the first aspect above. Optionally, the storage unit may be an in-device storage unit, such as a register or cache. Alternatively, the storage unit may be an external storage unit located within the device, such as read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, such as random access memory (RAM).

[0426] The processor mentioned above can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of a program for the wireless communication method described in the first aspect.

[0427] It should also be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. In addition, in the device embodiment drawings provided in this application, the connection relationship between modules indicates that they have a communication connection, which can be implemented as one or more communication buses or signal lines.

[0428] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware, or it can be implemented by special-purpose hardware including application-specific integrated circuits, special-purpose CPUs, special-purpose memory, special-purpose components, etc. Generally, any function performed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be diverse, such as analog circuits, digital circuits, or special-purpose circuits. However, for this application, software program implementation is more often the preferred implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium, such as a computer floppy disk, USB flash drive, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0429] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.

[0430] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

Claims

1. A state configuration method, characterized in that, include: The terminal device receives Radio Resource Configuration (RRC) signaling sent by the network device. The RRC signaling is used to instruct the terminal device to perform uplink or downlink bandwidth segment (BWP) handover. The BWP handover causes a change in the TCI state configured by the network device. The terminal device determines that the Transmission Configuration Indicator (TCI) status configured by the network device has changed based on the received RRC signaling. The terminal device obtains the first TCI state configured by the network device before the TCI state changes. The terminal device is configured with a second TCI state that is the same as the first TCI state. When the second TCI state is the same as the first TCI state, the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable. After the TCI state changes and before the third TCI state configured by the network device is activated, the terminal device uses the second TCI state to send and receive data.

2. The method according to claim 1, characterized in that, The terminal device obtains the first TCI state configured by the network device before the TCI state changes, including: The terminal device obtains the first TCI state corresponding to the first downlink control channel that schedules the RRC signaling, and the first downlink control channel is the downlink control channel before the TCI state changes.

3. The method according to claim 2, characterized in that, The terminal device is configured with a second TCI state that is the same as the first TCI state, including: The terminal device is configured such that the second TCI state corresponding to the second downlink control channel is the same as the first TCI state corresponding to the first downlink control channel, and the second downlink control channel is the downlink control channel after the TCI state changes.

4. The method according to claim 3, characterized in that, When there are multiple second downlink control channels after the TCI state changes, all second downlink control channels have the same second TCI state; or... The number of second downlink control channels is the same as that of the first downlink control channels, and the second downlink control channels with the same channel identifier and the first downlink control channels correspond to the same TCI state; or, When there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

5. The method according to claim 1, characterized in that, The terminal device obtains the first TCI state configured by the network device before the TCI state changes, including: The terminal device obtains the first TCI state corresponding to the first downlink shared channel carrying the RRC signaling, wherein the first downlink shared channel is the downlink shared channel before the TCI state changes.

6. The method according to claim 5, characterized in that, The terminal device is configured with a second TCI state that is the same as the first TCI state, including: The terminal device is configured such that the second TCI state corresponding to the second downlink shared channel is the same as the first TCI state corresponding to the first downlink shared channel, and the second downlink shared channel is the downlink shared channel after the TCI state changes; or... The terminal device is configured such that the second TCI state corresponding to the first uplink shared channel is the same as the first TCI state corresponding to the first downlink shared channel, and the first uplink shared channel is the uplink shared channel after the TCI state changes.

7. A state configuration method, characterized in that, include: The network device sends Radio Resource Configuration (RRC) signaling to the terminal device. The RRC signaling is used to instruct the terminal device to perform uplink or downlink bandwidth segment (BWP) handover. The BWP handover causes a change in the TCI state configured by the network device. The network device determines that the Transmission Configuration Indicator (TCI) status configured by the network device has changed based on the sent RRC signaling; The network device acquires the first TCI state configured by the network device before the TCI state changes. The network device is configured with a second TCI state that is the same as the first TCI state. When the second TCI state is the same as the first TCI state, the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable. After the TCI state changes and before the third TCI state configured by the network device is activated, the network device uses the second TCI state for data transmission and reception.

8. The method according to claim 7, characterized in that, The network device acquires the first TCI state configured by the network device before the TCI state changes, including: The network device acquires the first TCI state corresponding to the first downlink control channel that schedules the RRC signaling, and the first downlink control channel is the downlink control channel before the TCI state changes.

9. The method according to claim 8, characterized in that, The network device is configured with a second TCI state that is the same as the first TCI state, including: The network device is configured such that the second TCI state corresponding to the second downlink control channel is the same as the first TCI state corresponding to the first downlink control channel, and the second downlink control channel is the downlink control channel after the TCI state changes.

10. The method according to claim 9, characterized in that, When there are multiple second downlink control channels after the TCI state changes, all second downlink control channels have the same second TCI state; or... The number of second downlink control channels is the same as that of the first downlink control channels, and the second downlink control channels with the same channel identifier and the first downlink control channels correspond to the same TCI state; or, When there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

11. The method according to claim 7, characterized in that, The network device acquires the first TCI state configured by the network device before the TCI state changes, including: The network device obtains the first TCI state corresponding to the first downlink shared channel carrying the RRC signaling, wherein the first downlink shared channel is the downlink shared channel before the TCI state changes.

12. The method according to claim 11, characterized in that, The network device is configured with a second TCI state that is the same as the first TCI state, including: The network device is configured such that the second TCI state corresponding to the second downlink shared channel is the same as the first TCI state corresponding to the first downlink shared channel, and the second downlink shared channel is the downlink shared channel after the TCI state changes; or... The network device is configured such that the second TCI state corresponding to the first uplink shared channel is the same as the first TCI state corresponding to the first downlink shared channel, and the first uplink shared channel is the uplink shared channel after the TCI state changes.

13. A terminal device, characterized in that, include: The transceiver unit is used to receive Radio Resource Configuration (RRC) signaling sent by the network device. The RRC signaling is used to instruct the terminal device to perform uplink or downlink bandwidth segment (BWP) switching. The BWP switching causes a change in the TCI state configured by the network device. The processing unit is configured to determine, based on the received RRC signaling, that the Transmission Configuration Indicator (TCI) status of the network device has changed; The processing unit is further configured to obtain the first TCI state of the network device configuration before the TCI state changes; The processing unit is further configured to configure the second TCI state to be the same as the first TCI state. When the second TCI state is the same as the first TCI state, the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable. The transceiver unit is further configured to use the second TCI state for data transmission and reception after the TCI state changes and before the third TCI state configured by the network device is activated.

14. The terminal device according to claim 13, characterized in that, The processing unit is specifically used to obtain the first TCI state corresponding to the first downlink control channel that schedules the RRC signaling, wherein the first downlink control channel is the downlink control channel before the TCI state changes.

15. The terminal device according to claim 14, characterized in that, The processing unit is specifically configured to configure the second TCI state corresponding to the second downlink control channel to be the same as the first TCI state corresponding to the first downlink control channel, wherein the second downlink control channel is the downlink control channel after the TCI state changes.

16. The terminal device according to claim 15, characterized in that, When there are multiple second downlink control channels after the TCI state changes, all second downlink control channels have the same second TCI state; or... The number of second downlink control channels is the same as that of the first downlink control channels, and the second downlink control channels with the same channel identifier and the first downlink control channels correspond to the same TCI state; or, When there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

17. The terminal device according to claim 13, characterized in that, The processing unit is specifically used to obtain the first TCI state corresponding to the first downlink shared channel carrying the RRC signaling, wherein the first downlink shared channel is the downlink shared channel before the TCI state changes.

18. The terminal device according to claim 17, characterized in that, The processing unit is specifically configured to configure the second TCI state corresponding to the second downlink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the second downlink shared channel is the downlink shared channel after the TCI state has changed; or... The processing unit is specifically configured to configure the second TCI state corresponding to the first uplink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the first uplink shared channel is the uplink shared channel after the TCI state changes.

19. A network device, characterized in that, include: The transceiver unit is used to send Radio Resource Configuration (RRC) signaling to the terminal device. The RRC signaling is used to instruct the terminal device to perform uplink or downlink bandwidth segment (BWP) handover. The BWP handover causes a change in the TCI state configured by the network device. The processing unit is configured to determine, based on the transmitted RRC signaling, that the Transmission Configuration Indicator (TCI) state of the network device configuration has changed. The processing unit is further configured to obtain the first TCI state of the network device configuration before the TCI state changes; The processing unit is further configured to configure the second TCI state to be the same as the first TCI state. When the second TCI state is the same as the first TCI state, the reference signal pointed to by the second TCI state and the reference signal pointed to by the first TCI state are quasi-co-addressable. The transceiver unit is further configured to use the second TCI state for data transmission and reception after the TCI state changes and before the third TCI state configured by the network device is activated.

20. The network device according to claim 19, characterized in that, The processing unit is specifically used to obtain the first TCI state corresponding to the first downlink control channel that schedules the RRC signaling, wherein the first downlink control channel is the downlink control channel before the TCI state changes.

21. The network device according to claim 20, characterized in that, The processing unit is specifically configured to configure the second TCI state corresponding to the second downlink control channel to be the same as the first TCI state corresponding to the first downlink control channel, wherein the second downlink control channel is the downlink control channel after the TCI state changes.

22. The network device according to claim 21, characterized in that, When there are multiple second downlink control channels after the TCI state changes, all second downlink control channels have the same second TCI state; or... The number of second downlink control channels is the same as that of the first downlink control channels, and the second downlink control channels with the same channel identifier and the first downlink control channels correspond to the same TCI state; or, When there are multiple first downlink control channels before the TCI state changes, the first downlink control channel corresponding to the first TCI state that is the same as the second TCI state is a predefined downlink control channel.

23. The network device according to claim 19, characterized in that, The processing unit is specifically used to obtain the first TCI state corresponding to the first downlink shared channel carrying the RRC signaling, wherein the first downlink shared channel is the downlink shared channel before the TCI state changes.

24. The network device according to claim 23, characterized in that, The processing unit is specifically configured to configure the second TCI state corresponding to the second downlink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the second downlink shared channel is the downlink shared channel after the TCI state has changed; or... The processing unit is specifically configured to configure the second TCI state corresponding to the first uplink shared channel to be the same as the first TCI state corresponding to the first downlink shared channel, wherein the first uplink shared channel is the uplink shared channel after the TCI state changes.

25. A communication device, characterized in that, include: Memory, used to store instructions; A processor for retrieving and executing the instructions from the memory, causing the communication device to perform the method as described in any one of claims 1-6.

26. A communication device, characterized in that, include: Memory, used to store instructions; A processor for retrieving and executing the instructions from the memory, causing the communication device to perform the method as described in any one of claims 7-12.

27. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when invoked and executed on a computer, cause the computer to perform the method as described in any one of claims 1-6.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when invoked and executed on a computer, cause the computer to perform the method as described in any one of claims 7-12.

29. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1-12.

Citation Information

Patent Citations

  • Unified beam management in a wireless network

    WO2018232090A1