Wireless communication methods, terminal devices, and network devices

Abstract

Embodiments of this application provide a wireless communication method, a terminal device, and a network device. The wireless communication method includes the terminal device releasing a resource associated with a first parameter when a timer corresponding to a first timing advance group (TAG) expires. The first parameter is associated with a first TAG. The first parameter includes at least one of a first transmission configuration instruction (TCI) state, first spatial relationship information, a first control resource set pool index, and a first uplink radio resource control (RRC) parameter.

Description

[Technical Field]

[0001] The embodiments of this application relate to the field of communications, and more specifically to wireless communication methods, terminal devices, and network devices. [Background technology]

[0002] In some scenarios, a single terminal device can be configured with one Timing Advance Group (TAG), and one TAG corresponds to one TimeAlignmentTimer, i.e., one TA timer. After the TA timer expires, the terminal device must release all reserved uplink and downlink resources in the serving cell. When a serving cell is associated with multiple TAGs, how to implement resource release is an urgent issue that needs to be resolved. [Overview of the Initiative]

[0003] This application provides a wireless communication method, a terminal device, and a network device. The terminal device can identify an associated first parameter based on the first TAG when a timer corresponding to the first TAG expires, and release only the resources associated with the first parameter.

[0004] In a first embodiment, a wireless communication method is provided, which includes a terminal device releasing a resource associated with a first parameter when a timer corresponding to a first timing advance group (TAG) expires. The first parameter is associated with a first TAG and includes at least one of a first transmission configuration instruction (TCI) state, first spatial relationship information, a first control resource set pool index, and a first uplink wireless resource control (RRC) parameter.

[0005] In a second embodiment, a wireless communication method is provided, which includes a network device transmitting first configuration information to a terminal device. The first configuration information is used to constitute a first association, which is an association between a timing advance group (TAG) and at least one of a transmission configuration instruction (TCI) state, spatial relationship information, a control resource set pool index, and an uplink wireless resource control (RRC) parameter.

[0006] In a third embodiment, a terminal device is provided. The terminal device is configured to perform the method in the first embodiment or each embodiment thereof. Specifically, the terminal device includes a functional module, which is configured to perform the method in the first embodiment or each embodiment thereof.

[0007] In a fourth embodiment, a network device is provided, which is configured to perform the methods of the second embodiment or each embodiment thereof. Specifically, the network device includes a functional module, which is configured to perform the methods of the second embodiment or each embodiment thereof.

[0008] In a fifth embodiment, a terminal device comprising a processor and memory is provided. The memory is configured to store computer programs, and the processor is configured to call and execute the computer programs stored in the memory to perform the methods of the first embodiment or each of its embodiments.

[0009] In a sixth embodiment, a network device is provided comprising a processor and memory. The memory is configured to store computer programs, and the processor is configured to call and execute the computer programs stored in the memory to perform the methods of the second embodiment or each of its embodiments.

[0010] In a seventh embodiment, a chip is provided, configured to perform the method in either the first or second embodiment or each embodiment thereof. The chip includes a processor, configured to call and execute a computer program stored in memory to cause a device on which the chip is mounted to perform the method in either the first or second embodiment or each embodiment thereof.

[0011] In the eighth embodiment, a computer-readable storage medium is provided. The computer-readable storage medium is configured to store a computer program. The computer program causes the computer to execute one of the first and second embodiments or the methods in each embodiment.

[0012] In the ninth embodiment, a computer program product is provided which includes computer program instructions. These computer program instructions cause a computer to execute one of the first and second embodiments or the methods in each embodiment.

[0013] In the tenth embodiment, a computer program is provided. When the computer program is executed on a computer, it causes the computer to perform one of the first and second embodiments or the methods in each of those embodiments.

[0014] According to the proposed technology, when the timer corresponding to the first TAG of a terminal device expires, the terminal device can identify the associated first parameter based on the first TAG and release resources associated with the first parameter without releasing all of the reserved resources in the terminal device's serving cell. This is advantageous in ensuring that normal communication between the terminal device and other network nodes takes place reliably and in avoiding the terminal device frequently initiating random access processes. [Brief explanation of the drawing]

[0015] [Figure 1] FIG. 1 is a schematic diagram showing a communication system architecture according to an embodiment of the present application. [Figure 2] FIG. 2 is a schematic diagram showing the format of a media access control (MAC) control element (CE) for timing adjustment of TA. [Figure 3] FIG. 3 is a schematic diagram showing the format of a MAC CE indicating the TA absolute value. [Figure 4] FIG. 4 is a schematic diagram showing the format of a MAC random access response (RAR) signaling that carries TA. [Figure 5] FIG. 5 is a schematic diagram showing the timing advance between downlink reception and uplink transmission. [Figure 6] FIG. 6 is a schematic diagram showing a scenario of multi-transmission and reception point (TRP)-based uplink transmission scheduled by multi-DCI. [Figure 7] FIG. 7 is a schematic interaction diagram showing a wireless communication method according to an embodiment of the present application. [Figure 8] FIG. 8 is a block diagram showing a terminal device according to an embodiment of the present application. [Figure 9] FIG. 9 is a block diagram showing a network device according to an embodiment of the present application. [Figure 10] FIG. 10 is a block diagram showing a communication device according to an embodiment of the present application. [Figure 11] FIG. 11 is a block diagram showing a chip according to an embodiment of the present application. [Figure 12] FIG. 12 is a block diagram showing a communication system according to an embodiment of the present application.

Mode for Carrying Out the Invention

[0016] Hereinafter, the technical solutions of the embodiments of the present application will be described while referring to the drawings of the embodiments of the present application. Clearly, the described embodiments are only some of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments that can be obtained by those skilled in the art without creative efforts all belong to the protection scope of the present application.

[0017] The technical invention of the embodiment of this application can be applied to various types of communication systems. For example, global system for mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE-A (advanced long term evolution) system, new radio (NR) system, evolved new radio system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, non-terrestrial networks (NTN) system, universal mobile telecommunication system (UMTS), wireless local area networks (WLAN), internet of things (IoT), wireless fidelity Examples include fidelity (Wi-Fi), 5th generation (5G) communication systems, or other communication systems.

[0018] Generally speaking, connections supported by conventional communication systems are easily achieved, but their number is limited. However, with advancements in communication technology, mobile communication systems will not only support conventional communication, but will also be able to support device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, and V2X (Vehicle-to-everything) communication. Embodiments of this application can be applied to these communication systems.

[0019] Selectively, the communication system in the embodiments of this application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0020] Selectively, the communication system in the embodiments of this application can be applied to an unlicensed spectrum, where the unlicensed spectrum can be considered a shared spectrum. Alternatively, the communication system in the embodiments of this application can be applied to a licensed spectrum, where the licensed spectrum can be considered a non-shared spectrum.

[0021] In the embodiments of this application, each embodiment will be described by combining a network device and a terminal device. The terminal device may also be called user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment.

[0022] Terminal devices may be stations (STAs) in a WLAN, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistant (PDA) devices, handheld devices with wireless communication capabilities, computing devices, or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, next-generation communication systems, such as terminal devices in an NR network, or terminal devices in a future advanced PLMN (Public Land Mobile Network) network.

[0023] In the embodiments of this application, the terminal device may be deployed on land (handheld, wearable, in-vehicle, etc.), including indoors and outdoors; on water (e.g., on a ship); or in the air (e.g., on an airplane, balloon, satellite, etc.).

[0024] In the embodiments of this application, the terminal device may be a mobile phone, a tablet computer (Pad), a computer with wireless transmission and reception capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in telemedicine, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home.

[0025] As an example rather than an limitation, in the embodiments of this application, the terminal device may be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for wearable devices developed by intelligently designing everyday clothing such as glasses, gloves, watches, clothing, and shoes by applying wearable technology. Wearable devices are portable devices that can be worn directly on a user's body or integrated into a user's clothing or accessories. Wearable devices are not only hardware devices, but can also achieve strong functionality through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include devices that have full functionality and a large size and can achieve all or part of their functionality without relying on a smartphone (e.g., smartwatches, smart glasses, etc.), as well as devices that focus only on specific application functions and need to be used in conjunction with other devices such as smartphones (e.g., any smart bracelet for vital sign monitoring, smart jewelry, etc.).

[0026] In the embodiments of this application, the network device can be used to communicate with a mobile device. The network device may be an access point (AP) in a WLAN, a base transceiver station (BTS) in GSM or CDMA, a node B (NB) in WCDMA, an evolutionary node B (eNB or eNodeB) in LTE, a relay station, an access point, an in-vehicle device, a wearable device, a network device (gNB) (next generation node B) in an NR network, or a network device in a future advanced PLMN network, or a network device in an NTN network, etc.

[0027] As an example rather than an limitation, in embodiments of this application, the network device may have mobile characteristics; for example, the network device may be a mobile device. Optionally, the network device may be a satellite or balloon station. For example, the satellite may be a low Earth orbit (LEO) satellite, a middle Earth orbit (MEO) satellite, a geostationary Earth orbit (GEO) satellite, a highly elliptical orbit (HEO) satellite, etc. Optionally, the network device may be a base station located on land or water.

[0028] In embodiments of this application, a network device provides services to a cell, and a terminal device communicates with the network device via transmission resources (e.g., frequency domain resources or spectral resources) used by the cell. The cell may be a cell corresponding to a network device (e.g., a base station), and the cell may belong to a macro base station or to a base station corresponding to a small cell. Small cells may include metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of a small coverage area and low transmission power, making them suitable for providing high-speed data transmission services.

[0029] Exemplary, a communication system 100 applied to an embodiment of this application is shown in Figure 1. The communication system 100 may include a network device 110, which may be a device that communicates with terminal devices 120 (also called a communication terminal or terminal). The network device 110 provides communication coverage to a specific geographic area and can communicate with terminal devices within that coverage area.

[0030] Figure 1 illustrates one network device and two terminal devices. Selectively, the communication system 100 may include multiple network devices and a number of other terminal devices within the coverage area of ​​each network device. The embodiments of this application are not limited thereto.

[0031] Selectively, the communication system 100 may further include other network entities, such as a network controller or a mobile management entity. The embodiments of this application are not limited thereto.

[0032] A device having communication functions in a network / system according to the embodiment of this application may be called a communication system. The communication system 100 shown in Figure 1 will be described as an example. The communication device may include a network device 110 and a terminal device 120, both having communication functions. The network device 110 and the terminal device 120 may be the specific devices described above, and will not be repeated here. The communication device may also include other devices in the communication system 100, such as other network entities, including a network controller and a mobile management entity. The embodiments of this application are not limited thereto.

[0033] In this specification, the terms "system" and "network" are always used interchangeably. In this specification, the term "and / or" simply describes the relationship between related objects and indicates that there are three types of relationships. For example, A and / or B indicates three situations: A exists alone, A and B exist simultaneously, or B exists alone. Also in this specification, the symbol " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0034] It should be understood that the term "indicate" as used in the embodiments of this application may be direct, indirect, or indicate a related relationship. For example, A indicating B may mean that A directly indicates B (for example, that B can be obtained by A), that A indirectly indicates B (for example, that A indicates C and B can be obtained by C), or that there is a related relationship between A and B.

[0035] In the description of the embodiments of this application, the term "corresponding" may mean that there is a direct or indirect corresponding relationship between the two, or that there is a related relationship between the two, or that there is a relationship such as instruction and instruction, setting and setting.

[0036] In embodiments of this application, “predefined” can be achieved by pre-storing corresponding codes or corresponding tables in a device (including, for example, terminal devices and network devices), or by other means that can be used to indicate relevant information, and the application is not limited to such specific methods of implementation. For example, “predefined” may mean defined in a protocol.

[0037] In embodiments of this application, “protocol” may mean a standard protocol in the field of communications. Examples include LTE protocols, NR protocols, or protocols applicable to future communications systems. This application is not limited to the type of protocol.

[0038] To facilitate understanding of the technical concept in the embodiments of this application, the timing advance (TA) of this application will be explained.

[0039] In some scenarios, a cell group (CG) can have up to four Timing Advance Groups (TAGs) configured within a UE. TAGs can be configured by Radio Resource Control (RRC). Selectively, a CG can contain multiple serving cells. Each serving cell is assigned a Timing Advance Group Identity (TAG-Id). Each TAG has a TimeAlignmentTimer, which the UE operates. When the timer expires, the UE considers the TAG to be out of uplink sync. The timer is reset by the network device only if, during timer operation, the network device adjusts the TA value via a Media Access Control Element (MAC CE) or other signaling, and the UE considers the TAG to be in uplink sync. For example, if the TimeAlignmentTimer value is set to 500ms, in other words, the network device needs to update (adjust) the UE's TA value once within 500ms; otherwise, the UE may consider the TAG to be out of uplink synchronization and may initiate a random access process when uplink data arrives.

[0040] In some scenarios, the UE's Time Adaptation (TA) can be calculated based on the following formula. The UE's TA represents the first pass of the downlink channel received by the UE, i.e., the advance transmission, which uses the first symbol of the time slot in which the channel is located as the downlink reference.

[0041] JPEG2026517736000002.jpg948

[0042] In one CG, each serving cell can be preconfigured with one timing advance offset (TA offset), for example, configured by a higher layer parameter (n-TimingAdvanceOffset), that is, N in the formula TA,offset configured by. The TA adjustment amount (N TA ) is performed based on the preconfigured TA offset. T C is the minimum time unit in the NR system, and T C = 1 / (4096 * 480kHz). The timing adjustment for N TA can be provided by the MAC CE of the network device, that is, the current TA adjustment (new) is adjusted forward or backward in time based on the previous (old) TA. The calculation formula is as follows

[0043] JPEG2026517736000003.jpg1098

[0044] The format of the MAC CE for the timing adjustment of TA is shown in Figure 2. The TA adjustment is to adjust T A the number of minimum time units based on the previous TA, and the granularity of this TA adjustment is TAG

[0045] In some other scenarios, the network device can indicate the absolute value of TA for uplink transmission to the UE. For example, the network device can directly indicate the absolute value of TA N TA by the MAC CE command shown in Figure 3. The value range of N TA is 0 to 3846, and its length is 12 bits. The range indicated by TA is the formula N TA = T A * 16 * 64 * 2 μThis can be identified by [the specified method]. Furthermore, this MAC CE command can be applied to the Primary Timing Advance Group (PTAG) corresponding to the corresponding MAC entity, i.e., the PTAG is defined to include a Special Cell (SpCell). Since this MAC CE is applicable only to PTAGs, it does not need to include a TAG-Id.

[0046] In some scenarios, during initial access to a cell by the UE, after sending a Physical Random Access Channel (PRACH) to the network device, the UE expects the network device to provide a TA instruction to the UE via a Media Access Control Random Access Response (MAC RAR) within a certain time window. Figure 4 shows the format of the MAC RAR signaling that carries the TA. Based on this MAC RAR, the UE can obtain one initial 12-bit TA absolute value.

[0047] When the UE operates in Single TRP (sTRP) mode, as shown in Figure 5, the uplink channel or uplink signal is time-wise (N) from the downlink reception point, which is the reference point for the UE's timing advance. TA +N TA,offset )*T C It is sent when forward advance is performed.

[0048] In some scenarios, repetition of physical uplink control channels (PUCCH) or physical uplink shared channels (PUSCH) based on multi-TRP (mTRP) is supported to enhance uplink coverage and transmission reliability. The UE needs to send PUCCH or PUSCH carrying the same content to different TRPs. While repetition of multi-PUSCH based on single downlink control information (sDCI) is supported, the UE can use a single TA to sequentially send PUSCH to different TRPs. For multi-DCI (mDCI) based multi-PUSCH repetition, multiple TRPs schedule UEs independently, as there may not be sufficient ideal backhaul between multiple TRPs. Because such operations can result in temporal overlap of PUSCH / PUCCH for different TRPs, it is also necessary to support different TA updates or instructions for different TRPs.

[0049] In some scenarios, mechanisms are considered to support multiple antenna panels of a UE simultaneously transmitting PUCCH / PUSCH to multiple TRPs. However, similarly, under a multi-uplink transmit antenna panel and multi-TRP receive configuration, the UE can perform early transmission using only one TA within a single serving cell. Such limitations should obviously be overcome, i.e., TRP-specific, TA acquisition and instruction should be supported.

[0050] For example, in an mDCI-mTRP scenario within a cell, TRP #1 and TRP #2 use the same PCI, as shown in Figure 6. Each TRP can schedule PDSCH / PUSCH transmissions within its TRP using its respective DCI. In mDCI-mTRP operation, control resource sets (CORESETs) are grouped by the RRC parameter control resource set pool index (CORESETPoolIndex). For example, a CORESET with a CORESETPoolIndex of "0" is divided into one group and corresponds to one TRP, while a CORESET with a CORESETPoolIndex of "1" is divided into other groups and corresponds to other TRPs. If a network device has not configured a CORESETPoolIndex for a CORESET, its default value is "0".

[0051] In an inter-cell mDCI-mTRP scenario, TRP #1 in Figure 6 may be understood as the reference TRP, i.e., the TRP accessed by the UE during initial access. The UE has achieved uplink and downlink synchronization and has its own Physical Cell Identifier (PCI) #1. For the other TRPs, since a network device can select one TRP from up to seven to additionally provide uplink transmission services to the UE, these TRPs have different PCIs from the serving TRP and generally do not have pre-established uplink and downlink synchronization with the UE.

[0052] In several scenarios, transmission solutions supporting single DCI (S-DCI) based mTRP pushers are considered. For example, single-frequency network (SFN) solutions or space division multiplexing (SDM) solutions are used.

[0053] An SFN solution can mean that a network device transmits uplink scheduling information from one TRP, and a scheduled UE transmits the same PUSCH to multiple TRPs on the same time-frequency resource. The PUSCHs received by the network device from multiple TRPs may be decoded independently or integrated. Integrated decoding compared to independent decoding can result in a lower PUSCH error rate, i.e., a lower block error rate (BLER).

[0054] An SDM solution can mean that a network device sends uplink scheduling information from one TRP, and a scheduled UE sends different PUSCHs to multiple TRPs for the same or overlapping time-domain resources. For example, a UE sends Rank 1 PUSCH #1 to TRP #1 and Rank 2 PUSCH #2 to TRP #2. This has the advantage of increasing uplink throughput.

[0055] In some scenarios, the concept of a Transmission Configuration Indicator (TCI) state is proposed for the transfer of Quasi-co-located (QCL) information in the time-frequency domain and for downlink spatial domain quasi-co-location (beam) indication. Specifically, a quasi-co-location (QCL) relationship can be simply described as a large-scale fading relation from one source reference signal to one target reference signal. For beam indication, after the UE obtains two QCL relationships between the source reference signal and the target reference signal from the network device, the UE can use the received beam previously used to receive the source reference signal when receiving the target reference signal.

[0056] In some scenarios, the indicator mechanism for TCI states applies only to the downlink channel and downlink signal. The concept of spatial relation is defined for uplink beam indication and is used to describe the spatial relationship between two reference signals.

[0057] In several scenarios, to provide a unified uplink and downlink beam management mechanism to the communication system, we propose the concept of a unified TCI state based on the design of the TCI state, and examples of its increased important functions are as follows: 1: Three types of unified TCI state modes are designed. The joint TCI state applies to uplink and downlink channels, and to uplink and downlink signals. The downlink (DL) TCI state applies only to downlink channels and downlink signals. The uplink (UL) TCI state applies only to uplink channels and uplink signals. 2: Downlink channels (Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH)) and signals (Channel State Information Reference Signal (CSI-RS)) use the same downlink transmission beam, for example, using DL TCI state or joint TCI state. 3. The uplink channel (e.g., PUCCH, PUSCH) and signal (e.g., Sounding Reference Signal, SRS) use the same uplink transmission beam and use either UL TCI state or joint TCI state. 4: The Unified TCI state may be dynamically updated and indicated by MAC CE and / or DCI. 5. Can be applied to carrier aggregation scenarios. Beam direction in a single component carrier (CC) can be applied to multiple different CCs. 6: Uplink beam indication and uplink power control parameters may be given simultaneously via UL TCI state or joint TCI state. 7. Inter-cell beam management functionality is supported.

[0058] In some scenarios, a serving cell (including single-TRP and multi-TRP scenarios) has only one TAG and a corresponding single TA timer. After the TA timer expires, the UE must release all reserved uplink and downlink resources in the serving cell. When a serving cell has multiple TAGs, how to implement resource release is an urgent issue that needs to be resolved.

[0059] To facilitate understanding of the technical proposal of the embodiments of this application, the technical proposal of this application will be described in detail below with reference to specific embodiments. The above related technologies can be optionally combined with the technical proposal of the embodiments of this application, and all of them fall within the scope of protection of the embodiments of this application. The embodiments of this application include at least a part of the following.

[0060] Figure 7 is a schematic interaction diagram showing a wireless communication method 200 according to an embodiment of this application. As shown in Figure 7, this method 200 includes at least some of the following:

[0061] S210: When the timer corresponding to the first Timing Advance Group (TAG) expires, the terminal device releases the resource associated with the first parameter. The first parameter is associated with the first TAG.

[0062] In some embodiments, the first parameter includes at least one of a first TCI state, first spatial relation information, first CORESETPoolIndex, and first uplink RRC parameter.

[0063] In some embodiments, the first parameter is associated with a first network node, for example, a first TRP.

[0064] In some embodiments, a network device (e.g., a base station) can support multiple network nodes. For example, uplink transmissions associated with different first parameters may be considered to have been received by different network nodes. Similarly, downlink transmissions associated with different first parameters may be considered to have been transmitted from different network nodes.

[0065] In some embodiments, the timer corresponding to the first TAG may be a TimeAlignmentTimer. When this timer corresponding to the first TAG expires, the terminal device considers that the first TAG is out of uplink synchronization. In other words, the terminal device is out of uplink synchronization with the first network node.

[0066] In some embodiments, a serving cell of a terminal device is associated with at least two TAGs. The first TAG is one of at least two TAGs. Each TAG corresponds to one TAG ID. For example, the first TAG corresponds to the first TAG ID. A timer associated with the first TAG may refer to a timer corresponding to the first TAG ID. An association between a first parameter and a first TAG may refer to an association between the first TAG ID and the first parameter.

[0067] In some embodiments, the first TAG is a PTAG in at least two TAGs.

[0068] In some embodiments of this application, S210 includes the following: If the timer corresponding to the first TAG has expired and the timers corresponding to at least two other TAGs have not expired, the terminal device releases only the resources associated with the first parameter associated with the first TAG.

[0069] In other words, if only the timer corresponding to the first TAG has expired, and the timers corresponding to the other TAGs have not expired, it indicates that the terminal device is out of uplink synchronization with the first network node, but is not out of uplink synchronization with the other network nodes. Therefore, the terminal device can release uplink and downlink resources only to the first network node, and does not need to release all of the reserved uplink and downlink resources in the terminal device's serving cell. For example, resources can be released based on a first parameter associated with the first TAG, for example, releasing the resources associated with the first parameter.

[0070] In some embodiments, the association between the first TAG and the first parameter may be predefined, configured by a network device, or specified according to predefined rules.

[0071] For example, as shown in Figure 7, the above method further includes the following: S201: The network device can transmit first configuration information to a terminal device. The first configuration information is used to configure a first association. The first association is an association between a TCI state, spatial relationship information, CORESETPoolIndex, and at least one of the uplink RRC parameters, and a TAG. The first association includes an association between a first TCI state and a first parameter.

[0072] In some embodiments, the first configuration information is transmitted by at least one of the following: a system message, RRC signaling, a media access control (MAC) control element (CE), or downlink control information (DCI).

[0073] For example, a first TAG ID can be added to the Information Element (IE) of the first parameter to establish a relationship between the first TAG and the first parameter.

[0074] The release method for the first parameter and related resources will be described below with reference to specific embodiments.

[0075] Embodiment 1: The first parameter is the first TCI state.

[0076] Embodiment 1-1: The first TCI state includes a first uplink TCI state (UL TCI state) or a first joint TCI state (joint TCI state).

[0077] In some embodiments, when the timer corresponding to a first TAG expires, the terminal device can identify the associated UL / joint TCI state based on the first TAG, and further identify the uplink resource associated with this UL / joint TCI state. Compared to a solution where the TAG is associated with a CORESETPoolIndex, the advantage of using the association between the UL / joint TCI state and the TAG is that this TAG can use the downlink reference signal included in the UL / joint TCI state as a downlink synchronization time reference, i.e., the terminal device can determine the transmission time of the Physical Random Access Channel (PRACH) based on the reception time of this downlink reference signal. Also, in the millimeter-wave band, the UL / joint TCI state can provide beam-level downlink and uplink synchronization. This synchronization is more precise than network node-level synchronization (where one network node uses multiple beams for coverage, and multiple beams experience different path transmission delays).

[0078] Embodiment 1-1-1: Release a PUCCH resource or PUCCH resource group to which a first uplink TCI state (UL TCI state) or a first joint TCI state (joint TCI state) is applied.

[0079] In this embodiment 1-1-1, the first uplink TCI state or the first joint TCI state can be used to indicate a reference signal (or beam) corresponding to the uplink channel to which the first uplink TCI state or the first joint TCI state is applied.

[0080] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated UL TCI state or joint TCI state based on the first TAG, and can further release the PUCCH resource or PUCCH resource group to which this UL TCI state or joint TCI state applies.

[0081] In some embodiments, the PUCCH resource to which the first TCI state is applied is the first PUCCH resource, and the PUCCH resource group to which the first TCI state is applied is the first PUCCH resource group. When the timer corresponding to the first TAG expires, the first PUCCH resource or the first PUCCH resource group can be released. That is, the resources associated with the first parameter include the first PUCCH resource or the first PUCCH resource group.

[0082] In some embodiments, a network device may configure (or indicate, activate) an uplink TCI state or a joint TCI state for a PUCCH resource or PUCCH resource group. In this case, it can be considered that this uplink TCI state or joint TCI state can be applied to this PUCCH resource or PUCCH resource group. For example, a network device may configure a TCI state resource pool by RRC signaling, for example, this TCI state resource pool containing 128 UL / joint TCI states. Then, MAC CE activates eight TCI states or combinations of TCI states (including two joint / UL TCI states). Finally, a TCI state indicator field (e.g., 3 bits) in the DCI (e.g., DCI format 1_1 / 1_2) indicates the target TCI state in the TCI state activated by MAC CE. The UL / joint TCI state indicated by this DCI applies to all PUCCH resources / resource groups and PUCCH resources configured by the network device.

[0083] In some embodiments, a network device may configure (or indicate, activate) one uplink TCI state or joint TCI state for a PUCCH resource or PUCCH resource group (referred to as Case 1). Alternatively, a network device may configure (or indicate, activate) multiple uplink TCI states or joint TCI states for a PUCCH resource or PUCCH resource group (referred to as Case 2). For example, multiple uplink TCI states or joint TCI states may be two uplink TCI states or two joint TCI states, or a combination of one uplink TCI state and one joint TCI state. In this case, the terminal device transmits the PUCCH to multiple network nodes. Selectively, in the transmission of the PUCCH to multiple network nodes by this terminal device, a time-division multiplexing (TDM) scheme (e.g., repeated transmission of a PUCCH sent to different network nodes on different time-domain resources), or an SFN scheme or SDM scheme may be used.

[0084] In Case 1, when the timer corresponding to the first TAG expires, the terminal device can identify the associated uplink TCI state or joint TCI state based on the first TAG, and can further release the PUCCH resource or PUCCH resource group to which this uplink TCI state or joint TCI state applies.

[0085] In Case 2, if the timer corresponding to the first TAG expires, one embodiment releases the first PUCCH resource or the first PUCCH resource group. This is because the terminal device has already lost uplink synchronization with the first network node, and therefore cannot complete repeated PUCCH transmissions. Thus, the first PUCCH resource or the first PUCCH resource group can be released. In another embodiment, the first PUCCH resource or the first PUCCH resource group is not released. The reason is as follows: The terminal device has already lost uplink synchronization with the first network node. If the terminal device is not lost uplink synchronization with other network nodes, it can continue to send PUCCHs to other network devices.

[0086] For example, if a first TAG is associated with a first UL / joint TCI state, and a network device configures only the first UL / joint TCI state for a first PUCCH resource or first PUCCH resource group, then the first PUCCH resource or first PUCCH resource group can be considered to correspond only to the first UL / joint TCI state. In other words, the first PUCCH resource or first PUCCH resource group uses only the first UL / joint TCI state. In this case, when the timer corresponding to the first TAG expires, the terminal device can release the PUCCH resource or PUCCH resource group to which this first UL / joint TCI state applies, i.e., it can release the first PUCCH resource or first PUCCH resource group. Alternatively, if a network device configures a first UL / joint TCI state and a second UL / joint TCI state in a first PUCCH resource or first PUCCH resource group, the first PUCCH resource or first PUCCH resource group can be considered to correspond to the first UL / joint TCI state and the second UL / joint TCI state. In other words, the first PUCCH resource or first PUCCH resource group uses the first UL / joint TCI state and the second UL / joint TCI state. In this case, when the timer corresponding to the first TAG expires, the terminal device can release the PUCCH resource or PUCCH resource group to which this first UL / joint TCI state applies, i.e., it can release the first PUCCH resource or first PUCCH resource group.

[0087] Embodiment 1-1-2: Releasing SRS resources or SRS resource sets associated with a first uplink TCI state (UL TCI state) or a first joint TCI state (joint TCI state). For example, when a timer corresponding to a first TAG expires, the terminal device can identify the associated uplink TCI state or joint TCI state based on the first TAG and further release SRS resources or SRS resource sets associated with this uplink TCI state or joint TCI state.

[0088] In some embodiments, the first UL / joint TCI state is used to indicate an uplink signal. The first UL / joint TCI state can be configured in a first SRS resource or first SRS resource set. When the timer associated with the first TAG expires, the first SRS resource or first SRS resource set associated with the first UL / joint TCI state associated with the first TAG can be released. The first SRS resource or first SRS resource set is used to track the uplink signal indicated by the first UL / joint TCI state.

[0089] In other words, the resources associated with the first parameter include a Sounding Reference Signal (SRS) resource or SRS resource set associated with the first TCI state. The SRS resource or SRS resource set is configured to track the uplink signal indicated by the first TCI state.

[0090] In some embodiments, if the first SRS resource or first SRS resource set does not have a UL / joint TCI state configured, i.e., the first SRS resource or first SRS resource set is not configured to track an uplink signal, the terminal device may release the first SRS resource or first SRS resource set when the timer corresponding to the first TAG expires, or it may not release the first SRS resource or first SRS resource set.

[0091] Embodiment 1-1-3: Release a pre-configured PUSCH resource to which a first uplink TCI state (UL TCI state) or a first joint TCI state (joint TCI state) is applied.

[0092] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated uplink TCI state or joint TCI state based on the first TAG and release any pre-configured PUSCH resources associated with that uplink TCI state or joint TCI state.

[0093] In other words, the resources associated with the first parameter include pre-configured PUSCH resources to which the first TCI state is applied.

[0094] In some embodiments, PUSCH resources may be dynamically scheduled or semi-statically configured (or pre-configured).

[0095] For dynamically scheduled PUSCH resources, if a terminal device loses uplink synchronization with the network node, the network device can avoid scheduling the terminal device to perform uplink transmission to the network node.

[0096] For a pre-configured PUSCH resource, a network device can configure (or indicate, activate) one or more UL / joint TCI states for that PUSCH resource (for example, configure a first TCI state, or a second TCI state, or the first and second TCI states). When the timer corresponding to the first TAG expires, the terminal device can identify the UL / joint TCI state associated with the first TAG and release further pre-configured PUSCH resources to which the UL / joint TCI state applies.

[0097] Selectively, pre-configured PUSCH resources include PUSCH resources for carrying configured uplink grants and / or PUSCH resources for semi-persistent channel state information (CSI) reporting.

[0098] Furthermore, Embodiments 1-1-1, 1-1-2, and 1-1-3 described above may be implemented individually or in combination.

[0099] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated UL / joint TCI state based on the first TAG and release at least two of the following: the PUCCH resource to which this UL / joint TCI state applies, the SRS resource or SRS resource group associated with this UL / joint TCI state, and the pre-configured PUCCH resource to which this UL / joint TCI state applies.

[0100] Selectively, in this embodiment 1-1, the uplink resource associated with the first UL / joint TCI state may include at least one of the following: a PUCCH resource or PUCCH resource group to which the first UL / joint TCI state applies, an SRS resource or SRS resource group associated with the first UL / joint TCI state, and a pre-configured PUSCH resource to which the first UL / joint TCI state applies.

[0101] Embodiment 1-2: The first TCI state includes a first downlink TCI state or a first joint TCI state.

[0102] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated DL / joint TCI state based on the first TAG and release further downlink resources associated with the first DL / joint TCI state.

[0103] Embodiment 1-2-1: Release the Hybrid Automatic Repeat reQuest (HARQ) buffer corresponding to the PDSCH to which the first DL / joint TCI state is applied.

[0104] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated DL / joint TCI state based on the first TAG and release further HARQ buffers corresponding to the PDSCH to which this DL / joint TCI state applies.

[0105] In other words, the resource associated with the first parameter includes a HARQ buffer corresponding to the PDSCH to which the first DL / joint TCI state is applied.

[0106] In some embodiments, the PDSCH can be transmitted by a HARQ process. The HARQ process at the receiving end may correspond to a single HARQ buffer used to soft combine the received data. When the timer corresponding to the first TAG expires, the terminal device is out of uplink synchronization with the first network node. Therefore, the terminal device does not need to receive or process the PDSCH of the first network node. Thus, the HARQ buffer corresponding to the PDSCH to which the first DL / joint TCI state associated with the first TAG applies can be released.

[0107] Embodiment 1-2-2: Release a pre-configured PDSCH resource to which a first DL / joint TCI state is applied.

[0108] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated DL / joint TCI state based on the first TAG and release further pre-configured PDSCH resources to which this DL / joint TCI state applies.

[0109] In other words, the resources associated with the first parameter include pre-configured PDSCH resources to which the first DL / joint TCI state is applied.

[0110] Selectively, pre-configured PDSCH resources include configured DL assignments.

[0111] In some embodiments, a network device can pre-configure a DL / joint TCI state in a Configured DL assignment, and can further activate or indicate a target DL / joint TCI state. When the timer corresponding to the first TAG expires, the terminal device can determine that it is out of uplink synchronization with the first network node. Therefore, the terminal device does not need to receive or process the PDSCH of the first network node. Thus, it can release the pre-configured PDSCH resource to which the DL / joint TCI state associated with the first TAG applies.

[0112] Furthermore, Embodiments 1-2-1 and 1-2-2 described above may be implemented individually or in combination.

[0113] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated DL / joint TCI state based on the first TAG and release the HARQ buffer corresponding to the PDSCH to which this DL / joint TCI state applies, as well as the pre-configured PDSCH resources to which this DL / joint TCI state applies.

[0114] Selectively, in this embodiment 1-1, the downlink resource associated with the first DL / joint TCI state may include at least one of the following: a HARQ buffer corresponding to the PDSCH to which the first DL / joint TCI state is applied, or a pre-configured PDSCH resource to which the first DL / joint TCI state is applied.

[0115] Furthermore, Embodiments 1-1 and 1-2 described above may be implemented individually or in combination.

[0116] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated UL / joint TCI state and DL / joint TCI state based on the first TAG, and can further release the uplink resources associated with this UL / joint TCI state (e.g., the uplink resources in Embodiments 1-1-1, 1-1-2, and 1-1-3) and the downlink resources associated with this DL / joint TCI state (e.g., the downlink resources in Embodiments 1-2-1 and 1-2-2).

[0117] Embodiment 2: The first parameter includes first spatial relation information.

[0118] Compared to a solution where TAGs are associated with CORESETPoolIndex, the advantage of using an association between spatial relation information and TAGs is that this TAG can use the downlink reference signal contained in the spatial relation information as a downlink synchronization time reference, meaning that terminal devices can determine the PRACH transmission time based on the reception time of this downlink reference signal. Also, in the millimeter-wave band, spatial relation information can provide beam-level downlink and uplink synchronization. This synchronization is more accurate compared to network node-level synchronization (where one network node uses multiple beams for coverage, and multiple beams experience different path transmission delays).

[0119] In some embodiments, spatial relation information may be configured for an uplink channel or uplink signal. That is, the spatial relation information has a relational relationship with the uplink channel or uplink signal.

[0120] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated spatial relation information based on the first TAG and release further uplink resources associated with this spatial relation information.

[0121] Embodiment 2-1: The first spatial relation information includes the first PUCCH spatial relation information (PUCCH-SpatialRelationInfo).

[0122] In other words, the first TAG is associated with the first PUCCH-SpatialRelationInfo.

[0123] In this case, the terminal device can release a PUCCH resource or PUCCH resource group associated with the first PUCCH-SpatialRelationInfo.

[0124] In some embodiments, when the timer corresponding to the first TAG expires, the terminal device can identify the associated PUCCH-SpatialRelationInfo based on the first TAG and further release the PUCCH resource or PUCCH resource group associated with this PUCCH-SpatialRelationInfo. For example, the resource associated with the first parameter includes a second PUCCH resource or a second PUCCH resource group. The second PUCCH resource or second PUCCH resource group is a PUCCH resource or PUCCH resource group associated with the first PUCCH-SpatialRelationInfo.

[0125] In some embodiments, a network device may configure (or indicate, activate) a PUCCH-SpatialRelationInfo for a PUCCH resource or PUCCH resource group. In this case, it can be considered that this PUCCH-SpatialRelationInfo can be applied to the PUCCH resource or PUCCH resource group.

[0126] In some embodiments, a network device may configure (or indicate, activate) one PUCCH-SpatialRelationInfo for a PUCCH resource or PUCCH resource group (referred to as Case 1). Alternatively, a network device may configure (or indicate, activate) multiple PUCCH-SpatialRelationInfo for a PUCCH resource or PUCCH resource group (referred to as Case 2). For example, multiple PUCCH-SpatialRelationInfo are two PUCCH-SpatialRelationInfo. In this case, the terminal device transmits PUCCH to multiple network nodes. Selectively, the TDM scheme, or the SFN scheme or SDM scheme, may be used when this terminal device transmits PUCCH to multiple network nodes.

[0127] In Case 1, when the timer corresponding to the first TAG expires, the terminal device can identify the associated PUCCH-SpatialRelationInfo based on the first TAG and release any PUCCH resources or PUCCH resource groups associated with this PUCCH-SpatialRelationInfo.

[0128] In Case 2, if the timer corresponding to the first TAG expires, in one embodiment, the second PUCCH resource or the second PUCCH resource group is released. This is because the terminal device has already lost uplink synchronization with the first network node, and therefore cannot complete repeated PUCCH transmissions. Thus, the second PUCCH resource or the second PUCCH resource group may be released. In another embodiment, the second PUCCH resource or the second PUCCH resource group is not released. The reason is as follows: The terminal device has already lost uplink synchronization with the first network node. If the terminal device is not lost uplink synchronization with other network nodes, it can continue to send PUCCHs to other network devices.

[0129] Embodiment 2-2: The first spatial relationship information includes the first SRS spatial relationship information (SRS-SpatialRelationInfo).

[0130] In other words, the first TAG is associated with the first SRS-SpatialRelationInfo.

[0131] Embodiment 2-2-1: Release an SRS resource or SRS resource group associated with the first SRS-SpatialRelationInfo.

[0132] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated SRS-SpatialRelationInfo based on the first TAG and release the SRS resource or SRS resource group associated with this SRS-SpatialRelationInfo.

[0133] For example, the resources associated with the first parameter include a second SRS resource or a second SRS resource group. The second SRS resource or second SRS resource group is the SRS resource or SRS resource group associated with the first SRS-SpatialRelationInfo.

[0134] In some embodiments, a network device may configure one SRS-SpatialRelationInfo for an SRS resource or SRS resource group.

[0135] Embodiment 2-2-2: Release a pre-configured PUSCH resource associated with the first SRS-SpatialRelationInfo.

[0136] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated SRS-SpatialRelationInfo based on the first TAG and release any further pre-configured PUSCH resources associated with this SRS-SpatialRelationInfo.

[0137] In this embodiment, a network device can configure an SRS resource for a PUSCH resource, and can also configure an SRS-SpatialRelationInfo for an SRS resource. Therefore, a pre-configured PUSCH resource associated with a first SRS-SpatialRelationInfo may be a PUSCH resource associated with an SRS resource associated with the first SRS-SpatialRelationInfo.

[0138] In some embodiments, the PUSCH resource has the same antenna port as the associated SRS resource.

[0139] In some embodiments, a pre-configured PUSCH resource includes a PUSCH resource for carrying configured UL grants and / or a PUSCH resource for semi-persistent CSI reporting.

[0140] Furthermore, Embodiments 2-1 and 2-2 described above may be implemented individually or in combination.

[0141] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated PUCCH-SpatialRelationInfo and SRS-SpatialRelationInfo based on the first TAG, and can further release the PUCCH resource associated with this PUCCH-SpatialRelationInfo and the uplink resource associated with this SRS-SpatialRelationInfo (e.g., the uplink resource in Embodiments 2-2-1 and 2-2-2).

[0142] Selectively, in this embodiment 3, the uplink resource associated with the first spatial relation information may include at least one of the following: a PUCCH resource or PUCCH resource group associated with the first PUCCH-SpatialRelationInfo, an SRS resource or SRS resource group associated with the first SRS-SpatialRelationInfo, or a pre-configured PUSCH resource associated with the first SRS-SpatialRelationInfo.

[0143] Embodiment 3: The first parameter includes a first uplink RRC parameter or a first CORESETPoolIndex.

[0144] CORESETPoolIndex can directly represent the relationship between a network node and a TAG as an index dedicated to a single network node in a downlink control channel. Therefore, resources can be released based on the relationship between the TAG and CORESETPoolIndex. Furthermore, while spatial relation information (applicable only to FR2 (Frequency Range 2)) is applied to two frequency bands, FR1 and FR2, CORESETPoolIndex can support multi-TA enhancement across all frequency bands.

[0145] In other words, the first TAG is associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0146] In some embodiments, when the timer corresponding to the first TAG expires, the terminal device can identify the associated uplink RRC parameter or CORESETPoolIndex based on the first TAG and release the resources associated with this uplink RRC parameter or CORESETPoolIndex.

[0147] Embodiment 3-1: Release a PUCCH resource associated with a first uplink RRC parameter or a first CORESETPoolIndex.

[0148] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated uplink RRC parameter or CORESETPoolIndex based on the first TAG and release further PUCCH resources associated with this uplink RRC parameter or CORESETPoolIndex.

[0149] In other words, the resources associated with the first parameter include the PUCCH resources associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0150] In some embodiments, a network device may configure (or indicate, activate) an uplink RRC parameter or CORESETPoolIndex for a PUCCH resource. That is, this uplink RRC parameter or CORESETPoolIndex has an association with the PUCCH resource.

[0151] Embodiment 3-2: Release a pre-configured PUSCH resource associated with a first uplink RRC parameter or a first CORESETPoolIndex.

[0152] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated uplink RRC parameter or CORESETPoolIndex based on the first TAG and release any pre-configured PUSCH resources associated with that uplink RRC parameter or CORESETPoolIndex.

[0153] In other words, the resources associated with the first parameter include pre-configured PUSCH resources associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0154] In some embodiments, a pre-configured PUSCH resource may include a type 1 Configured Grant (CG) PUSCH resource and / or a type 2 CG PUSCH resource.

[0155] In some embodiments, a pre-configured PUSCH resource associated with a first uplink RRC parameter or a first CORESETPoolIndex includes at least one of the following: a type1 CG PUSCH resource associated with the first uplink RRC parameter or a first CORESETPoolIndex; a type2 CG PUSCH resource associated with the first uplink RRC parameter or a first CORESETPoolIndex; or a type2 CG PUSCH resource activated by DCI associated with the first uplink RRC parameter or a first CORESETPoolIndex.

[0156] In some embodiments, a network device may configure (or indicate, activate) an uplink RRC parameter or CORESETPoolIndex for a type1 CG PUSCH resource. That is, this uplink RRC parameter or CORESETPoolIndex has an association with the type1 CG PUSCH resource.

[0157] In some embodiments, a network device may configure (or indicate, activate) an uplink RRC parameter or CORESETPoolIndex for a type2 CG PUSCH resource. That is, this uplink RRC parameter or CORESETPoolIndex has an association with the type2 CG PUSCH resource.

[0158] In some embodiments, a type2 CG PUSCH is associated with a PDCCH. For example, a type2 CG PUSCH needs to be activated by a DCI in a PDCCH, which corresponds to an uplink RRC parameter or CORESETPoolIndex. When the timer corresponding to a first TAG expires, the terminal device can identify the associated uplink RRC parameter or CORESETPoolIndex based on the first TAG, further identify the DCI associated with the uplink RRC parameter or CORESETPoolIndex, and release the type2 CG PUSCH activated by this DCI.

[0159] Embodiment 3-3: Release an SRS resource or SRS resource set associated with a first uplink RRC parameter or a first CORESETPoolIndex.

[0160] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated uplink RRC parameter or CORESETPoolIndex based on the first TAG and release the SRS resource or SRS resource set associated with this uplink RRC parameter or CORESETPoolIndex.

[0161] In other words, the resources associated with the first parameter include the SRS resources or SRS resource sets associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0162] In some embodiments, the SRS resource or SRS resource set associated with a first uplink RRC parameter or first CORESETPoolIndex is a periodic or semi-persistent SRS resource. A network device can configure an uplink RRC parameter or CORESETPoolIndex (or a second uplink RRC parameter or second CORESETPoolIndex, i.e., a parameter corresponding to a second network device) to a periodic or semi-persistent SRS resource. When the timer corresponding to the first TAG expires, the terminal device can identify the associated uplink RRC parameter or CORESETPoolIndex based on the first TAG and may further release the SRS resource or SRS resource set associated with this uplink RRC parameter or CORESETPoolIndex (or any other uplink RRC parameter or CORESETPoolIndex).

[0163] Embodiment 3-4: Release the HARQ buffer corresponding to the PDSCH scheduled by the DCI associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0164] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated uplink RRC parameter or CORESETPoolIndex based on the first TAG and release the HARQ buffer corresponding to the DCI-scheduled PDSCH associated with the uplink RRC parameter or CORESETPoolIndex.

[0165] That is, the resource associated with the first parameter includes a HARQ buffer corresponding to a PDSCH scheduled by DCI associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0166] Furthermore, DCI is transmitted via time-frequency resources. The relationship between DCI and uplink RRC parameters or CORESETPoolIndex can be expressed as the relationship between DCI and time-frequency resources.

[0167] For example, DCI is transmitted via CORESET. Each CORESET corresponds to one CORESETPoolIndex (default is "0" if not configured). The relationship between CORESETPoolIndex and DCI may also be the relationship between a DCI and the CORESET that transmits it.

[0168] In some embodiments, the PDSCH can be transmitted by a HARQ process. At the receiving end, the HARQ process may correspond to a single HARQ buffer used for soft combining the received data. When the timer corresponding to the first TAG expires, the terminal device is out of uplink synchronization with the first network node. Therefore, it does not need to receive or process the PDSCH of the first network node. Thus, the HARQ buffer corresponding to the PDSCH scheduled by the uplink RRC parameter associated with the first TAG or the DCI associated with the CORESETPoolIndex can be released.

[0169] Embodiment 3-5: Release a pre-configured PDSCH resource associated with a first uplink RRC parameter or a first CORESETPoolIndex.

[0170] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated uplink RRC parameter or CORESETPoolIndex based on the first TAG and release further pre-configured PDSCH resources associated with this uplink RRC parameter or CORESETPoolIndex.

[0171] In other words, the resources associated with the first parameter include pre-configured PDSCH resources associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0172] Selectively, pre-configured PDSCH resources include configured downlink assignments, such as type 2 configured DL assignments.

[0173] In some embodiments, a network device can activate or deactivate a Configured DL assignment by a DCI. This DCI corresponds to an uplink RRC parameter or CORESETPoolIndex. When the timer corresponding to a first TAG expires, the terminal device can determine that it is out of uplink synchronization with the first network node. Therefore, it does not need to receive or process the PDSCH of the first network node. Thus, the terminal device can identify the associated uplink RRC parameter or CORESETPoolIndex based on the first TAG, further identify the DCI associated with the uplink RRC parameter or CORESETPoolIndex, and release the Configured DL assignment activated by this DCI.

[0174] In some embodiments, the resources associated with the first uplink RRC parameter or the first CORESETPoolIndex may include at least one of the following: a PUCCH resource associated with the first uplink RRC parameter or the first CORESETPoolIndex; a pre-configured PUSCH resource associated with the first uplink RRC parameter or the first CORESETPoolIndex; an SRS resource or SRS resource set associated with the first uplink RRC parameter or the first CORESETPoolIndex; a HARQ buffer corresponding to a DCI-scheduled PDSCH associated with the first uplink RRC parameter or the first CORESETPoolIndex; or a pre-configured PDSCH resource associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0175] Furthermore, embodiments 3-1 to 3-5 described above may be implemented individually or in combination.

[0176] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated uplink RRC parameter or CORESETPoolIndex based on the first TAG and release further uplink and / or downlink resources associated with the uplink RRC parameter or CORESETPoolIndex. For example, it can release at least two of the following associated with the uplink RRC parameter or CORESETPoolIndex: a PUSCH resource, a pre-configured PUSCH resource, an SRS resource, a HARQ buffer corresponding to a PDSCH scheduled by DCI, and a pre-configured PDSCH resource.

[0177] Furthermore, Embodiments 1, 2, and 3 described above may be implemented individually or in combination.

[0178] For example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated TCI state and CORESETPoolIndex based on the first TAG, and can further release the uplink resources and / or downlink resources associated with this TCI state, as well as the uplink resources and / or downlink resources associated with this CORESETPoolIndex.

[0179] Furthermore, for example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated TCI state and spatial relation information based on the first TAG, and can further release the uplink resources associated with this TCI state and / or the downlink resources associated with this TCI state, as well as the uplink resources associated with this spatial relation information.

[0180] Furthermore, for example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated spatial relation information and CORESETPoolIndex based on the first TAG, and can further release the uplink resources and / or downlink resources associated with this CORESETPoolIndex, as well as the uplink resources and / or downlink resources associated with this spatial relation information.

[0181] Furthermore, for example, when the timer corresponding to the first TAG expires, the terminal device can identify the associated TCI state, spatial relation information, and CORESETPoolIndex based on the first TAG, and can further release the uplink resources associated with this TCI state and / or the downlink resources associated with this TCI state, the uplink resources associated with this CORESETPoolIndex and / or the downlink resources associated with this CORESETPoolIndex, and the uplink resources associated with this spatial relation information.

[0182] In view of the above, in embodiments of the present application, when a timer corresponding to one TAG in at least two TAGs configured for the serving cell of a terminal device expires, the terminal device may, based on the first TAG, identify an associated first parameter and release resources associated with the first parameter without releasing all of the reserved resources in the serving cell of the terminal device. This is advantageous in ensuring that normal communication between the terminal device and other network nodes takes place and in avoiding the terminal device frequently initiating random access processes.

[0183] The method embodiment of this application was described in detail above with reference to Figure 7. Hereinafter, the apparatus embodiment of this application will be described in detail with reference to Figures 8 to 12. Note that the apparatus embodiment corresponds to the method embodiment, and similar descriptions can be found in the method embodiment.

[0184] Figure 8 is a block diagram showing a terminal device 400 according to an embodiment of the present application. As shown in Figure 8, the terminal device 400 includes a processing unit 410. When a timer corresponding to a first TAG expires, the processing unit 410 is configured to release a resource associated with a first parameter. The first parameter is associated with a first TAG. The first parameter includes at least one of a first transmission configuration instruction (TCI) state, first spatial relationship information, a first control resource set pool index, and a first uplink radio resource control (RRC) parameter.

[0185] In some embodiments, the first TCI state includes a first uplink TCI state or a first joint TCI state.

[0186] In some embodiments, the resources associated with the first parameter include a first physical uplink control channel (PUCCH) resource or a first PUCCH resource group. The first PUCCH resource or first PUCCH resource group is a PUCCH resource or PUCCH resource group to which a first TCI state is applied.

[0187] In some embodiments, only the first TCI state applies to the first PUCCH resource or the first PUCCH resource group.

[0188] In some embodiments, the first PUCCH resource or first PUCCH resource group is a PUCCH resource or PUCCH resource group to which the first TCI state and the second TCI state are applied.

[0189] In some embodiments, the resources associated with the first parameter include a sounding reference signal (SRS) resource or SRS resource set associated with the first TCI state. The SRS resource or SRS resource set is configured to track the uplink signal indicated by the first TCI state.

[0190] In some embodiments, the resource associated with the first parameter includes a pre-configured physical uplink shared channel (PUSCH) resource to which the first TCI state is applied.

[0191] In some embodiments, the pre-configured PUSCH resources include a PUSCH resource for carrying configured uplink grants and / or a PUSCH resource for reporting semi-persistent channel status information (CSI).

[0192] In some embodiments, the first TCI state includes a first downlink TCI state or a first joint TCI state.

[0193] In some embodiments, the resource associated with the first parameter includes a HARQ buffer corresponding to the PDSCH to which the first TCI state is applied.

[0194] In some embodiments, the resource associated with the first parameter includes a pre-configured PDSCH resource to which the first TCI state is applied.

[0195] In some embodiments, the pre-configured PDSCH resource includes configured downlink assignments.

[0196] In some embodiments, the first spatial relationship information includes the first PUCCH spatial relationship information.

[0197] In some embodiments, the resource associated with the first parameter includes a second PUCCH resource or a second PUCCH resource group. The second PUCCH resource or second PUCCH resource group is a PUCCH resource or PUCCH resource group associated with the first PUCCH spatial relation information.

[0198] In some embodiments, the second PUCCH resource or second PUCCH resource group is associated only with the first PUCCH spatial relation information, or The second PUCCH resource or second PUCCH resource group is a PUCCH resource or PUCCH resource group associated with the first PUCCH spatial relationship information and the second PUCCH spatial relationship information.

[0199] In some embodiments, the first spatial relationship information includes the first SRS spatial relationship information.

[0200] In some embodiments, the resources associated with the first parameter include an SRS resource or an SRS resource associated with the first SRS spatial relation information.

[0201] In some embodiments, the resource associated with the first parameter includes a pre-configured PUSCH resource associated with an SRS resource associated with the first SRS spatial relation information.

[0202] In some embodiments, the pre-configured PUSCH resources include a PUSCH resource for carrying configured uplink grants and / or a PUSCH resource for reporting semi-persistent channel status information (CSI).

[0203] In some embodiments, the resources associated with the first parameter include a PUCCH resource associated with a first uplink RRC parameter or a first control resource set pool index.

[0204] In some embodiments, the resources associated with the first parameter include pre-configured PUSCH resources associated with a first uplink RRC parameter or a first control resource set pool index.

[0205] In some embodiments, a pre-configured PUSCH resource associated with a first uplink RRC parameter or a first control resource set pool index includes at least one of the following: a type1 configuration grant (CG) PUSCH resource associated with the first uplink RRC parameter or the first control resource set pool index; a type2 CG PUSCH resource associated with the first uplink RRC parameter or the first control resource set pool index; or a type2 CG PUSCH resource activated by downlink control information (DCI) associated with the first uplink RRC parameter or the first control resource set pool index.

[0206] In some embodiments, the resources associated with the first parameter include an SRS resource or SRS resource set associated with a first uplink RRC parameter or a first control resource set pool index.

[0207] In some embodiments, the resource associated with the first parameter includes a HARQ buffer corresponding to a PDSCH scheduled by DCI associated with a first uplink RRC parameter or a first control resource set pool index.

[0208] In some embodiments, the resources associated with the first parameter include pre-configured PDSCH resources associated with a first uplink RRC parameter or a first control resource set pool index.

[0209] In some embodiments, the pre-configured PDSCH resource includes a type2 configured downlink assignment.

[0210] In some embodiments, a serving cell of a terminal device is associated with at least two TAGs. The first TAG is one of the at least two TAGs. When the timer corresponding to the first TAG expires, the terminal device releases the resource associated with the first parameter. This includes the terminal device releasing only the resources associated with the first parameter associated with the first TAG if the timer corresponding to the first TAG has expired and the timers corresponding to at least two other TAGs have not expired.

[0211] In some embodiments, the first TAG is a primary timing advance group (PTAG) in at least two TAGs.

[0212] In some embodiments, the terminal device further includes a communication unit, which is configured to receive first configuration information transmitted by a network device. The first configuration information is used to configure a first association, which is an association between a TAG and at least one of the following: TCI state, spatial relationship information, control resource set pool index, and uplink RRC parameter.

[0213] In some embodiments, the first association includes an association between a first TCI state and a first parameter. The first parameter includes at least one of the following: a first TCI state, first spatial relationship information, a first control resource set pool index, and a first uplink RRC parameter.

[0214] In some embodiments, the first configuration information is transmitted by at least one of the following: a system message, RRC signaling, a media access control (MAC) control element (CE), or downlink control information (DCI).

[0215] Selectively, the communication unit may be a communication interface or transceiver, or an input / output interface for a communication chip or system-on-a-chip. The processing unit may be one or more processors.

[0216] Furthermore, the terminal device 400 according to the embodiment of this application can correspond to the terminal device in the method embodiment of this application. Also, the above and other operations and / or functions of each unit in the terminal device 400 are for carrying out the corresponding process of the terminal device in method 200 shown in Figure 7. For brevity, this will not be repeated here.

[0217] Figure 9 is a block diagram showing a network device 500 according to an embodiment of the present application. As shown in Figure 9, the network device 500 includes a communication unit 510, which is configured to transmit first configuration information to a terminal device. The first configuration information is used to constitute a first association, which is an association between at least one of the following: a transmission configuration instruction (TCI) state, spatial relationship information, a control resource set pool index, and an uplink radio resource control (RRC) parameter, and a timing advance group (TAG).

[0218] In some embodiments, the first association includes an association between a first TCI state and a first parameter. The first parameter includes at least one of the following: a first TCI state, first spatial relationship information, a first control resource set pool index, and a first uplink RRC parameter.

[0219] In some embodiments, the first TCI state includes a first uplink TCI state or a first joint TCI state.

[0220] In some embodiments, the first TCI state includes a first downlink TCI state or a first joint TCI state.

[0221] In some embodiments, the first spatial relation information includes first physical uplink control channel (PUCCH) spatial relation information and / or first sounding reference signal (SRS) spatial relation information.

[0222] In some embodiments, the first configuration information is transmitted by at least one of the following: a system message, RRC signaling, a media access control (MAC) control element (CE), or downlink control information (DCI).

[0223] Selectively, in some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip.

[0224] Furthermore, the network device 500 according to the embodiment of this application can correspond to the network device in the method embodiment of this application. Also, the above and other operations and / or functions of each unit in the network device 500 are for carrying out the corresponding process of the network device in method 200 shown in Figure 7. For brevity, this will not be repeated here.

[0225] Figure 10 is a block diagram showing a communication device 600 according to an embodiment of this application. The communication device 600 shown in Figure 10 includes a processor 610. The processor 610 can realize the method according to the embodiment of this application by calling and executing a computer program stored in memory.

[0226] Selectively, as shown in Figure 10, the communication device 600 further includes a memory 620. The processor 610 can implement the method according to the embodiment of this application by calling and executing a computer program stored in the memory 620.

[0227] The memory 620 may be a standalone unit independent of the processor 610, or it may be integrated into the processor 610.

[0228] Selectively, as shown in Figure 10, the communication device 600 may further include a transceiver 630. The processor 610 can control the transceiver 630 to communicate with other devices. Specifically, the transceiver 630 can transmit information or data to other devices or receive information or data transmitted by other devices.

[0229] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include an antenna. The number of antennas may be one or more.

[0230] Selectively, the communication device 600 may specifically be a network device of an embodiment of this application. Furthermore, the communication device 600 can implement the corresponding processes realized by the network device in each method of the embodiment of this application. For brevity, this is not repeated here.

[0231] Selectively, the communication device 600 may specifically be a mobile terminal / terminal device of an embodiment of this application. Furthermore, the communication device 600 can implement the corresponding processes realized by the mobile terminal / terminal device in each method of the embodiment of this application. For brevity, this will not be repeated here.

[0232] Figure 11 is a schematic diagram showing the structure of a chip according to an embodiment of this application. The chip 700 shown in Figure 11 includes a processor 710. The processor 710 can realize the method according to the embodiment of this application by calling and executing a computer program stored in memory.

[0233] Selectively, as shown in Figure 11, the chip 700 may further include a memory 720. The processor 710 can implement the method according to the embodiment of this application by calling and executing a computer program stored in the memory 720.

[0234] The memory 720 may be a standalone unit separate from the processor 710, or it may be integrated into the processor 710.

[0235] Selectively, the chip 700 further includes an input interface 730. The processor 710 can control the input interface 730 to communicate with other devices or chips. Specifically, the input interface 730 can obtain information or data transmitted by other devices or chips.

[0236] Selectively, the chip 700 further includes an output interface 740. The processor 710 can control the output interface 740 to communicate with other devices or chips. Specifically, the output interface 740 can output information or data to other devices or chips.

[0237] Selectively, the chip can be applied to the network device of the embodiments of this application. Furthermore, the chip can implement the corresponding processes realized by the network device in each of the methods of the embodiments of this application. For brevity, this is not repeated here.

[0238] Selectively, the chip can be applied to the mobile terminal / terminal device of the embodiments of this application. Furthermore, the chip can implement the corresponding processes realized by the mobile terminal / terminal device in each of the methods of the embodiments of this application. For brevity, this will not be repeated here.

[0239] The chip according to the embodiment of this application may also be called a system-level chip, system chip, chip system, or system-on-a-chip.

[0240] Figure 12 is a block diagram showing a communication system 900 according to an embodiment of the present application. As shown in Figure 12, the communication system 900 comprises a terminal device 910 and a network device 920.

[0241] The terminal device 910 may be configured to implement the corresponding functions realized by the terminal device in the above method. The network device 920 may be configured to implement the corresponding functions realized by the first network device and / or the second network device in the above method. For brevity, this will not be repeated here.

[0242] The processor in the embodiments of this application may be an integrated circuit chip having signal processing capabilities. In the implementation process, each step of the above method embodiment may be completed by an integrated logic circuit in hardware form or by instructions in software form of the processor. The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor may implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any ordinary processor. The steps of the methods disclosed in the embodiments of this application may be executed and completed directly by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module may reside in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, or registers. The storage medium is located in memory. The processor reads the information from memory and, in conjunction with the processor hardware, completes the steps of the method described above.

[0243] To ensure understanding, the memory of the embodiments of this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM) that functions as an external high-speed cache. Examples of various RAMs available include, but are not limited to, static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus random access memory (direct rambus RAM, DRRAM). The memory in the systems and methods described in this application may include, but is not limited to, these and any other suitable types of memory.

[0244] It should be understood that the above-mentioned memories are illustrative but not limiting. For example, the memories of the embodiments of this application may include static random access memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synch-link dynamic random access memory (synch-link DRAM, SLDRAM), and direct rambus random access memory (direct rambus RAM, DRRAM). In other words, the memories of the embodiments of this application may include, but are not limited to, these and any other suitable types of memory.

[0245] Embodiments of this application further provide a computer-readable storage medium used for storing computer programs.

[0246] Selectively, the computer-readable storage medium can be applied to the network device of the embodiments of this application. Furthermore, the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiments of this application. For brevity, this is not repeated here.

[0247] Selectively, the computer-readable storage medium can be applied to the mobile terminal / terminal device of the embodiments of this application. Furthermore, the computer program causes the computer to execute the corresponding process implemented by the mobile terminal / terminal device in each method of the embodiments of this application. For brevity, this will not be repeated here.

[0248] Embodiments of this application further provide a computer program product that includes computer program instructions.

[0249] Selectively, the computer program product can be applied to the network device of the embodiment of this application. Furthermore, the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of this application. For brevity, this is not repeated here.

[0250] Selectively, the computer program product can be applied to the mobile terminal / terminal device of the embodiments of this application. Furthermore, the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiments of this application. For brevity, this will not be repeated here.

[0251] Embodiments of this application further provide computer programs.

[0252] Selectively, the computer program can be applied to the network device of the embodiment of this application. Furthermore, when the computer program is executed on a computer, the computer is made to execute the corresponding process implemented by the network device in each method of the embodiment of this application. For brevity, this is not repeated here.

[0253] Selectively, the computer program can be applied to the mobile terminal / terminal device of the embodiments of this application. Furthermore, when the computer program is executed on a computer, the computer is made to execute the corresponding process implemented by the mobile terminal / terminal device in each method of the embodiments of this application. For brevity, this will not be repeated here.

[0254] It will be apparent to those skilled in the art that, in conjunction with the exemplary units and algorithmic operations described in the embodiments disclosed herein, the present application can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software will depend on the specific application of the invention and design constraints. Those skilled in the art may implement the described functions using different methods for each specific application, but these implementations should not be considered beyond the scope of the present application.

[0255] Those skilled in the art will understand that, for the sake of easy and concise explanation, the specific operating processes of the above systems, apparatuses, and units can be described by referring to the corresponding processes in the above method embodiments. This will not be repeated here.

[0256] It should be understood that the selectively disclosed systems, apparatus, and methods in this application may be implemented in other forms. For example, the embodiments of the apparatus described above are merely illustrative. For example, the division of a unit is merely a division of a logic function and may have a different division form when actually implemented. For example, multiple units or components may be combined or integrated into another system, or some of their features may be ignored or not performed. Furthermore, the coupling, direct coupling, and communication connections between the shown or considered may be indirect coupling or communication connections by several interfaces, apparatus, or units, and may be in electrical, mechanical, or other forms.

[0257] Units described as separate components may or may not be physically separated. Components shown as units may or may not be physical units. That is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected according to actual needs to achieve the objectives of the technical proposal of this embodiment.

[0258] Furthermore, each functional unit according to each embodiment of this application may be integrated into a single processing unit, each unit may exist physically independently, or two or more units may be integrated into a single unit.

[0259] The functions may be implemented as software function units and, when sold or used as standalone products, stored on computer-readable storage media. For the purposes of this understanding, any essential part of the proposed technology of this application, or any part that contributes to the prior art, or any part of such technology, may be expressed as a software product. This computer software product is stored on a storage medium and includes a number of instructions for causing a single computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of this application. The storage medium includes various types of media capable of storing program code, such as universal serial bus (USB) flash disks, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0260] The above are merely specific embodiments of the present application, and the scope of protection of this application is not limited thereto. Any modifications or substitutions that a person skilled in the art could easily conceive within the scope of the art disclosed in this application should be included within the scope of protection of this application. Accordingly, the scope of protection of this application should be determined by the scope of protection of the claims.

Claims

1. A wireless communication method, When a timer corresponding to a first timing advance group (TAG) expires, the terminal device includes releasing a resource associated with a first parameter, the first parameter being associated with the first TAG, and the first parameter including at least one of a first transmission configuration instruction (TCI) state, first spatial relationship information, a first control resource set pool index, and a first uplink radio resource control (RRC) parameter. A wireless communication method characterized by the following:

2. The first TCI state includes a first uplink TCI state or a first joint TCI state. The method according to feature 1.

3. The resource associated with the first parameter includes a first physical uplink control channel (PUCCH) resource or a first PUCCH resource group, wherein the first PUCCH resource or first PUCCH resource group is a PUCCH resource or PUCCH resource group to which the first TCI state applies. The method according to feature 2.

4. Only the first TCI state applies to the first PUCCH resource or the first PUCCH resource group. The method according to feature 3.

5. The first PUCCH resource or the first PUCCH resource group is a PUCCH resource or PUCCH resource group to which the first TCI state and the second TCI state apply. The method according to feature 3.

6. The resources associated with the first parameter include a sounding reference signal (SRS) resource or an SRS resource set associated with the first TCI state, wherein the SRS resource or the SRS resource set is configured to track the uplink signal indicated by the first TCI state. The method according to any one of claims 2 to 5, characterized by the features described herein.

7. The resources associated with the first parameter include a pre-configured physical uplink shared channel (PUSCH) resource to which the first TCI state is applied. The method according to any one of claims 2 to 6, characterized by the features described herein.

8. The pre-configured PUSCH resources include PUSCH resources for carrying configured uplink grants, and / or PUSCH resources for reporting semi-persistent channel status information (CSI). The method according to feature 7.

9. The first TCI state includes a first downlink TCI state or a first joint TCI state. The method according to any one of claims 2 to 8, characterized by the features described above.

10. The resource associated with the first parameter includes a hybrid automatic retransmission request (HARQ) buffer corresponding to the physical downlink shared channel (PDSCH) to which the first TCI state applies. The method according to feature 9.

11. The resource associated with the first parameter includes a pre-configured PDSCH resource to which the first TCI state is applied. The method according to 9 or 10, characterized by the features described above.

12. The aforementioned pre-configured PDSCH resources include configured downlink assignments, The method according to 11, characterized by the features described above.

13. The first spatial relationship information includes the first PUCCH spatial relationship information. The method according to any one of claims 1 to 12, characterized by the features described herein.

14. The resource associated with the first parameter includes a second PUCCH resource or a second PUCCH resource group, and the second PUCCH resource or second PUCCH resource group is a PUCCH resource or PUCCH resource group associated with the first PUCCH spatial relation information. The method according to the present invention, characterized by the present invention.

15. The second PUCCH resource or second PUCCH resource group is associated only with the first PUCCH spatial relationship information, or The second PUCCH resource or second PUCCH resource group is a PUCCH resource or PUCCH resource group associated with the first PUCCH spatial relationship information and the second PUCCH spatial relationship information. The method according to feature 14.

16. The first spatial relationship information includes the first SRS spatial relationship information. The method according to any one of claims 1 to 15, characterized by the features described herein.

17. The resource associated with the first parameter includes an SRS resource, or an SRS resource associated with the first SRS spatial relationship information. The method according to 16, characterized by...

18. The resource associated with the first parameter includes a pre-configured PUSCH resource associated with the SRS resource associated with the first SRS spatial relationship information. The method according to 16 or 17, characterized by the features described herein.

19. The pre-configured PUSCH resources include PUSCH resources for carrying configured uplink grants, and / or PUSCH resources for reporting semi-persistent channel status information (CSI). The method according to the present invention, characterized by the present invention.

20. The resources associated with the first parameter include the PUCCH resource associated with the first uplink RRC parameter or the first control resource set pool index. The method according to any one of claims 1 to 19, characterized by the features described herein.

21. The resources associated with the first parameter include pre-configured PUSCH resources associated with the first uplink RRC parameter or the first control resource set pool index. The method according to any one of claims 1 to 20, characterized by...

22. A pre-configured PUSCH resource associated with the first uplink RRC parameter or the first control resource set pool index is: The system includes at least one of the following: a type1 configuration grant (CG) PUSCH resource associated with the first uplink RRC parameter or the first control resource set pool index; a type2 CG PUSCH resource associated with the first uplink RRC parameter or the first control resource set pool index; and a type2 CG PUSCH resource activated by downlink control information (DCI) associated with the first uplink RRC parameter or the first control resource set pool index. The method according to feature 21.

23. The resources associated with the first parameter include an SRS resource or SRS resource set associated with the first uplink RRC parameter or the first control resource set pool index. The method according to any one of claims 1 to 22, characterized by the features described herein.

24. The resource associated with the first parameter includes a HARQ buffer corresponding to a PDSCH scheduled by DCI associated with the first uplink RRC parameter or the first control resource set pool index. The method according to any one of claims 1 to 23, characterized by...

25. The resources associated with the first parameter include pre-configured PDSCH resources associated with the first uplink RRC parameter or the first control resource set pool index. The method according to any one of claims 1 to 24, characterized by...

26. The aforementioned pre-configured PDSCH resources include type2 configuration downlink assignments, The method according to the present invention of the present invention.

27. The serving cell of the terminal device is associated with at least two TAGs, the first TAG being one of the at least two TAGs, and when the timer corresponding to the first TAG expires, the terminal device releases the resource associated with the first parameter. If the timer corresponding to the first TAG has expired and the timers corresponding to the other TAGs in at least two of the TAGs have not expired, the terminal device releases only the resources associated with the first parameter associated with the first TAG. including, The method according to any one of claims 1 to 26, characterized by...

28. The first TAG is the primary timing advance group (PTAG) in the at least two TAGs. The method according to any one of claims 1 to 27, characterized by the features described herein.

29. A wireless communication method, The network device transmits first configuration information to a terminal device, the first configuration information is used to constitute a first association, the first association being an association between at least one of a Transmission Configuration Instruction (TCI) state, spatial relationship information, a control resource set pool index, and an uplink radio resource control (RRC) parameter and a Timing Advance Group (TAG). A wireless communication method characterized by the following:

30. The first association includes an association between a first TCI state and a first parameter, the first parameter including at least one of the first TCI state, first spatial relationship information, first control resource set pool index, and first uplink RRC parameter. The method according to feature 29.

31. The first TCI state includes a first uplink TCI state or a first joint TCI state. The method according to the present invention, characterized by the present invention.

32. The first TCI state includes a first downlink TCI state or a first joint TCI state. The method according to 30 or 31, characterized by the features described above.

33. The first spatial relationship information includes first physical uplink control channel (PUCCH) spatial relationship information and / or first sounding reference signal (SRS) spatial relationship information. The method according to any one of claims 30 to 32, characterized by...

34. The first configuration information is transmitted by at least one of the following: a system message, RRC signaling, media access control (MAC) control element (CE), and downlink control information (DCI). The method according to any one of claims 29 to 33, characterized by...

35. A terminal device including a processing unit, When the timer corresponding to the first timing advance group (TAG) expires, the processing unit is configured to release the resources associated with the first parameter, the first parameter being associated with the first TAG, and the first parameter including at least one of the following: a first transmission configuration instruction (TCI) state, first spatial relationship information, a first control resource set pool index, and a first uplink radio resource control (RRC) parameter. A terminal device characterized by the following features.

36. The first TCI state includes a first uplink TCI state or a first joint TCI state. The terminal device according to feature 35.

37. The resource associated with the first parameter includes a first physical uplink control channel (PUCCH) resource or a first PUCCH resource group, wherein the first PUCCH resource or first PUCCH resource group is a PUCCH resource or PUCCH resource group to which the first TCI state applies. The terminal device according to feature 36.

38. Only the first TCI state applies to the first PUCCH resource or the first PUCCH resource group. The terminal device according to feature 37.

39. The first PUCCH resource or the first PUCCH resource group is a PUCCH resource or PUCCH resource group to which the first TCI state and the second TCI state apply. The terminal device according to feature 37.

40. The resources associated with the first parameter include a sounding reference signal (SRS) resource or an SRS resource set associated with the first TCI state, wherein the SRS resource or the SRS resource set is configured to track the uplink signal indicated by the first TCI state. The terminal device according to any one of claims 36 to 39, characterized by the features described herein.

41. The resources associated with the first parameter include a pre-configured physical uplink shared channel (PUSCH) resource to which the first TCI state is applied. The terminal device according to any one of claims 36 to 40, characterized by...

42. The pre-configured PUSCH resources include PUSCH resources for carrying configured uplink grants, and / or PUSCH resources for reporting semi-persistent channel status information (CSI). The terminal device according to feature 41.

43. The first TCI state includes a first downlink TCI state or a first joint TCI state. A terminal device according to any one of claims 36 to 42, characterized by the above.

44. The resource associated with the first parameter includes a hybrid automatic retransmission request (HARQ) buffer corresponding to the physical downlink shared channel (PDSCH) to which the first TCI state applies. The terminal device according to feature 43.

45. The resource associated with the first parameter includes a pre-configured PDSCH resource to which the first TCI state is applied. The terminal device according to feature 43 or 44.

46. The aforementioned pre-configured PDSCH resources include configured downlink assignments, The terminal device according to feature 45.

47. The first spatial relationship information includes the first PUCCH spatial relationship information. The terminal device according to any one of claims 35 to 46.

48. The resource associated with the first parameter includes a second PUCCH resource or a second PUCCH resource group, and the second PUCCH resource or second PUCCH resource group is a PUCCH resource or PUCCH resource group associated with the first PUCCH spatial relation information. The terminal device according to feature 47.

49. The second PUCCH resource or second PUCCH resource group is associated only with the first PUCCH spatial relationship information, or The second PUCCH resource or second PUCCH resource group is a PUCCH resource or PUCCH resource group associated with the first PUCCH spatial relationship information and the second PUCCH spatial relationship information. The terminal device according to feature 48.

50. The first spatial relationship information includes the first SRS spatial relationship information. The terminal device according to any one of claims 35 to 49.

51. The resource associated with the first parameter includes an SRS resource, or an SRS resource associated with the first SRS spatial relationship information. The terminal device according to claim 50.

52. The resource associated with the first parameter includes a pre-configured PUSCH resource associated with the SRS resource associated with the first SRS spatial relationship information. The terminal device according to claim 50 or 51, characterized in that it is a terminal device according to claim 50 or 51.

53. The pre-configured PUSCH resources include PUSCH resources for carrying configured uplink grants, and / or PUSCH resources for reporting semi-persistent channel status information (CSI). The terminal device according to feature 52.

54. The resources associated with the first parameter include the PUCCH resource associated with the first uplink RRC parameter or the first control resource set pool index. The terminal device according to any one of claims 35 to 53, characterized by the features described herein.

55. The resources associated with the first parameter include pre-configured PUSCH resources associated with the first uplink RRC parameter or the first control resource set pool index. The terminal device according to any one of claims 35 to 54, characterized by the features described herein.

56. A pre-configured PUSCH resource associated with the first uplink RRC parameter or the first control resource set pool index is: The system includes at least one of the following: a type1 configuration grant (CG) PUSCH resource associated with the first uplink RRC parameter or the first control resource set pool index; a type2 CG PUSCH resource associated with the first uplink RRC parameter or the first control resource set pool index; and a type2 CG PUSCH resource activated by downlink control information (DCI) associated with the first uplink RRC parameter or the first control resource set pool index. The terminal device according to feature 55.

57. The resources associated with the first parameter include an SRS resource or SRS resource set associated with the first uplink RRC parameter or the first control resource set pool index. The terminal device according to any one of claims 35 to 56, characterized by the features described herein.

58. The resource associated with the first parameter includes a HARQ buffer corresponding to a PDSCH scheduled by DCI associated with the first uplink RRC parameter or the first control resource set pool index. The terminal device according to any one of claims 35 to 57, characterized by the features described herein.

59. The resources associated with the first parameter include pre-configured PDSCH resources associated with the first uplink RRC parameter or the first control resource set pool index. The terminal device according to any one of claims 35 to 58, characterized by the above.

60. The aforementioned pre-configured PDSCH resources include type2 configuration downlink assignments, The terminal device according to claim 59.

61. The serving cell of the terminal device is associated with at least two TAGs, the first TAG being one of the at least two TAGs, and when the timer corresponding to the first TAG expires, the terminal device releases the resource associated with the first parameter. If the timer corresponding to the first TAG has expired and the timers corresponding to the other TAGs in at least two of the TAGs have not expired, the terminal device releases only the resources associated with the first parameter associated with the first TAG. including, The terminal device according to any one of claims 35 to 60, characterized by the features described herein.

62. The first TAG is the primary timing advance group (PTAG) in the at least two TAGs. The terminal device according to any one of claims 35 to 61, characterized by the features described herein.

63. A network device including a communication unit, The communication unit is configured to transmit first configuration information to a terminal device, the first configuration information is used to constitute a first association, the first association being an association between at least one of the following: a transmission configuration instruction (TCI) state, spatial relationship information, a control resource set pool index, and an uplink radio resource control (RRC) parameter, and a timing advance group (TAG). A network device characterized by the following features.

64. A terminal device comprising a processor and memory, The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory to perform the method according to any one of claims 1 to 28. A terminal device characterized by the following features.

65. A network device comprising a processor and memory, The memory is configured to store computer programs, and the processor is configured to call and execute the computer programs stored in the memory to perform the method according to any one of claims 29 to 34. A network device characterized by the following features.

66. A chip equipped with a processor, The processor is configured to call and execute a computer program stored in memory, causing the device equipped with the chip to execute the method according to any one of claims 1 to 28 or any one of claims 29 to 34. A chip characterized by the following features.

67. A computer-readable storage medium, The computer-readable storage medium is configured to store a computer program, and the computer program causes the computer to execute the method according to any one of claims 1 to 28 or any one of claims 29 to 34. A computer-readable storage medium characterized by the following features.

68. A computer program product that includes computer program instructions, The computer program instruction causes the computer to execute the method according to any one of claims 1 to 28 or the method according to any one of claims 29 to 34. A computer program product characterized by the following features.

69. It is a computer program, The computer program causes the computer to execute the method according to any one of claims 1 to 28 or the method according to any one of claims 29 to 34. A computer program characterized by the following features.

Images