Wireless communication method, terminal device and network device

Abstract

A wireless communication method, a terminal device and a network device, the method comprising: when a timer corresponding to a first timing advance group TAG is overtime, the terminal device releases a resource associated with a first parameter, the first parameter being associated with the first TAG, and the first parameter being associated with the first TAG; the first parameter comprises at least one of the following: a first transmission configuration indication (TCI) state, first spatial relationship information, a first control resource set pool index, and a first uplink radio resource control (RRC) parameter.

Description

Wireless communication method, terminal device and network device Technical Field

[0001] The embodiments of the present application relate to the field of communications, and specifically to a wireless communication method, terminal device, and network device. Background Art

[0002] In some scenarios, a terminal device can be configured with a Timing Advance Group (TAG). Each TAG corresponds to a Time Alignment Timer (TA timer). When the TA timer expires, the terminal device needs to release all reserved uplink and downlink resources on the serving cell. When a serving cell is associated with multiple TAGs, how to release resources is an urgent problem that needs to be solved.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method, terminal device and network device. When the timer corresponding to the first TAG times out, the terminal device can determine the associated first parameter according to the first TAG and only release the resources associated with the first parameter.

[0005] In a first aspect, a method for wireless communication is provided, including: when a timer corresponding to a first timing advance group TAG times out, a terminal device releases resources associated with a first parameter, the first parameter is associated with the first TAG, and the first parameter includes at least one of the following: a first transmission configuration indication TCI state, first spatial relationship information, a first control resource set pool index, and a first uplink radio resource control RRC parameter.

[0006] In a second aspect, a method for wireless communication is provided, including: a network device sends first configuration information to a terminal device, the first configuration information is used to configure a first association relationship, the first association relationship is an association relationship between a timing advance group TAG and at least one of the following parameters: transmission configuration indication TCI status, spatial relationship information, control resource set pool index, uplink radio resource control RRC parameters.

[0007] In a third aspect, a terminal device is provided for executing the method in the above-mentioned first aspect or its various implementations.

[0008] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect or its various implementation modes.

[0009] In a fourth aspect, a network device is provided for executing the method in the above second aspect or its various implementations.

[0010] Specifically, the network device includes a functional module for executing the method in the above-mentioned second aspect or its various implementation modes.

[0011] In a fifth aspect, a terminal device is provided, comprising a processor and a memory, wherein 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 of the first aspect or its respective implementations.

[0012] In a sixth aspect, a network device is provided, comprising a processor and a memory, wherein 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 of the second aspect or its respective implementations.

[0013] In a seventh aspect, a chip is provided for implementing the method described in any one of the first and second aspects above, or their respective implementations. Specifically, the chip includes a processor configured to retrieve and execute a computer program from a memory, causing a device equipped with the chip to perform the method described in any one of the first and second aspects above, or their respective implementations.

[0014] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, which enables a computer to execute the method of any one of the first to second aspects or their respective implementations.

[0015] In a ninth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method of any one of the first to second aspects or their respective implementations.

[0016] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method of any one of the first to second aspects or their respective implementations.

[0017] Through the above technical solution, when the timer corresponding to the first TAG of the terminal device times out, the terminal device can determine the associated first parameter based on the first TAG, and further release the resources associated with the first parameter, instead of releasing all reserved resources on the service cell of the terminal device, which is conducive to ensuring the normal communication between the terminal device and other network nodes and avoiding the terminal device from frequently initiating random access processes. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] FIG1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

[0019] FIG2 is a schematic diagram of a format of a MAC CE for differential adjustment of a TA.

[0020] FIG3 is a schematic diagram of the format of a MAC CE indicating the absolute value of TA.

[0021] FIG4 is a schematic diagram of the format of MAC RAR signaling carrying TA.

[0022] FIG5 is a schematic diagram of timing advance for downlink reception and uplink transmission.

[0023] FIG6 is a scenario diagram of uplink transmission based on multiple TRPs and multiple DCI scheduling.

[0024] FIG7 is a schematic interaction diagram of a wireless communication method provided according to an embodiment of the present application.

[0025] FIG8 is a schematic block diagram of a terminal device provided according to an embodiment of the present application.

[0026] FIG9 is a schematic block diagram of a network device provided according to an embodiment of the present application.

[0027] FIG10 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

[0028] FIG11 is a schematic block diagram of a chip provided according to an embodiment of the present application.

[0029] FIG12 is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0030] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. With respect to the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0031] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of 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, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0032] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0033] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0034] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as an unshared spectrum.

[0035] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as 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 device, etc.

[0036] The terminal device can be a station (STA) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0037] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0038] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, 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 remote medical, 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, etc.

[0039] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0040] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0041] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0042] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0043] For example, a communication system 100 used in an embodiment of the present application is shown in FIG1 . The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices within the coverage area.

[0044] FIG1 exemplarily shows a network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited in this embodiment of the present application.

[0045] Optionally, the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

[0046] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system 100 shown in FIG1 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function. The network device 110 and the terminal device 120 may be the specific devices described above and will not be described in detail here. The communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0047] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0048] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0049] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0050] In the embodiments of the present application, "pre-defined" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device or a network device). The present application does not limit the specific implementation method. For example, pre-defined may refer to information defined in a protocol.

[0051] In the embodiments of the present application, the "protocol" may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and this application does not limit this.

[0052] To facilitate understanding of the technical solutions of the embodiments of the present application, the timing advance (TA) related to the present application is explained.

[0053] In some scenarios, in a cell group (CG), the UE can be configured with up to 4 timing advance groups (TAGs). TAG can be configured through Radio Resource Control (RRC). Optionally, a CG can include multiple serving cells, and each serving cell will be assigned a TAG identifier (Timing Advance Group Identity, TAG-Id). Each TAG will have a time alignment timer (TimeAlignmentTimer), and the UE will count the time alignment timer. When this timer times out, the UE will consider that the TAG is out of uplink synchronization. When the network device adjusts the TA value through the Media Access Control Control Element (MAC CE) or other signaling during the operation of the timer, the timer will be reset, and the UE will consider that the TAG is in uplink synchronization state. For example, if the value of TimeAlignmentTimer is configured to 500ms, that is, the network device needs to update (adjust) the UE's TA value once within 500ms. Otherwise, the UE may consider the uplink out of synchronization and may initiate a random access process when uplink data arrives.

[0054] In some scenarios, the UE's TA can be calculated according to the following formula. The UE's TA is based on the first path of the downlink channel received by the UE, that is, the first symbol of the time slot where the channel is located as the downlink reference, and early transmission is performed on this basis: (N TA +N TA,offset )*T C

[0055] In a CG, each serving cell can be pre-configured with a timing advance offset (TA offset), for example, through the high-level parameter (n-TimingAdvanceOffset), that is, N in the formula TA,offset . Among them, TA adjustment amount (N TA ) is performed based on the pre-configured TA offset. C is the minimum time unit in the NR system, T C =1 / (4096*480kHz). N TA The MAC CE of the network device can provide differential adjustment, that is, the current TA adjustment (new) is based on the previous TA (old), adjusted forward or backward in time. The calculation formula is as follows:

[0056] The MAC CE format for differential adjustment of TA is shown in Figure 2, where the adjustment of TA is based on the adjustment of T A The minimum time unit is TAG, and the granularity of TA adjustment is TAG.

[0057] In other scenarios, the network device may indicate to the UE the absolute value of the TA for uplink transmission. For example, the network device may directly indicate the absolute value of the TA N via the MAC CE command shown in FIG3. TA , its value range is 0 to 3846, and its length is 12 bits. According to the formula N TA =T A *16*64*2 μ The TA indication range can be determined. Furthermore, the MAC CE command applies to the Primary Timing Advance Group (PTAG) corresponding to the corresponding MAC entity, i.e., the PTAG is defined to include special cells (SpCells). Because the MAC CE applies only to PTAGs, it does not need to include a TAG-Id.

[0058] In some scenarios, during the UE's initial access (to a cell), after sending a Physical Random Access Channel (PRACH) to a network device, the UE expects the network device to provide the UE with a TA indication via a Media Access Control Random Access Response (MAC RAR) within a certain time window. Figure 4 shows a format for MAC RAR signaling carrying a TA. Based on the MAC RAR, the UE can obtain an initial TA absolute value of 12 bits.

[0059] If the UE operates in single TRP (sTRP) mode, the reference point of the UE timing advance is calculated from the downlink reception time point and is advanced forward (N TA +N TA,offset )*T C The uplink channel or uplink signal is sent at a specific time, as shown in Figure 5.

[0060] In some scenarios, repeated transmission of the Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH) based on multiple TRPs (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. For repeated transmission of multiple PUSCHs (multi-PUSCH) based on single downlink control information (DCI, sDCI), the UE can use one TA to sequentially send PUSCH to different TRPs; for repeated transmission of multi-PUSCH based on multiple DCI (multi-DCI, mDCI), since there may not be a sufficiently ideal backhaul as a connection between multiple TRPs, multiple TRPs independently schedule the UE. This operation may cause temporal overlap of PUSCH / PUCCH for different TRPs, so different TA updates or indications need to be supported for different TRPs.

[0061] In some scenarios, mechanisms are being considered to support PUCCH / PUSCH transmissions from multiple antenna panels to multiple TRPs simultaneously. However, even with multiple uplink transmit antenna panels and multiple TRPs configured, a UE can only use one TA for early transmission within a serving cell. This limitation should clearly be overcome by supporting TRP-specific TA acquisition and indication.

[0062] For example, in the scenario of mDCI-mTRP within a cell, TRP#1 and TRP#2 use the same PCI, as shown in Figure 6. Each TRP can schedule PDSCH / PUSCH transmission on the TRP through its own DCI. It is worth noting that in the operation of mDCI-mTRP, the control resource set (CORESET) is grouped by the RRC parameter control resource set pool index (CORESETPoolIndex). For example, a CORESET with a CORESETPoolIndex of "0" is grouped into one group, corresponding to one TRP; a CORESET with a CORESETPoolIndex of "1" is grouped into another group, corresponding to another TRP. When the network device does not configure CORESETPoolIndex for a CORESET, its default value is "0".

[0063] In the inter-cell mDCI-mTRP scenario, TRP#1 in Figure 6 can be understood as the reference TRP, that is, the TRP to which the UE initially accesses. The UE has achieved uplink and downlink synchronization, and it has a dedicated physical cell identifier (PCI) #1. As for other TRPs, since the network device can select one TRP from up to 7 TRPs to provide additional uplink transmission services for the UE, these TRPs have different PCIs from the service TRP, and often have not established uplink and downlink synchronization with the UE in advance.

[0064] In some scenarios, it is considered to support a mTRP PUSCH transmission scheme based on a single-DCI (S-DCI), such as a single frequency network (SFN) scheme or a space division multiplexing (SDM) scheme.

[0065] For SFN solutions, this means that the network device sends uplink scheduling information from one TRP, and the scheduled UE sends the same PUSCH to multiple TRPs on the same time-frequency resources. The network device can decode the PUSCHs received from multiple TRPs independently or combine them for decoding. The latter method can achieve a lower PUSCH error probability, or a lower block error rate (BLER), compared to independent decoding.

[0066] The SDM solution can be described as follows: the network device sends uplink scheduling information from one TRP, and the scheduled UE sends different PUSCHs to multiple TRPs on the same or overlapping time domain resources. For example, the UE sends PUSCH#1 of Rank 1 to TRP#1 and PUSCH#2 of Rank 2 to TRP#2. The benefit of this is that it can increase uplink throughput.

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

[0068] In some scenarios, the TCI state indication mechanism only applies to downlink channels and signals. For uplink beam indication, the concept of spatial relation is defined to express the spatial relationship between two reference signals.

[0069] In some scenarios, to provide a unified uplink and downlink beam management mechanism for the communication system, the concept of a unified TCI state is proposed based on the design of the TCI state. The important functions it adds are as follows:

[0070] 1. Three unified TCI state modes are designed. The joint TCI state applies to both uplink and downlink channels and signals; the downlink (DL) TCI state applies only to downlink channels and signals; and the uplink (DL) TCI state applies only to uplink channels and signals.

[0071] 2. Downlink channels (part of the Physical Downlink Control Channel (PDCCH), the Physical Downlink Shared Channel (PDSCH)) and signals (the aperiodic Channel State Information Reference Signal (CSI-RS)) use the same downlink transmit beam, for example, using the DL TCI state or joint TCI state.

[0072] 3. Uplink channels (e.g., PUCCH, PUSCH) and signals (e.g., Sounding Reference Signal (SRS)) use the same uplink transmit beam and use the UL TCI state or joint TCI state.

[0073] 4. Unified TCI state can be dynamically updated and indicated using MAC CE and / or DCI.

[0074] 5. Applicable to the scenario of carrier aggregation, the beam indication on a single component carrier (CC) can be applicable to multiple different CCs.

[0075] 6. The uplink beam indication can be given simultaneously with the uplink power control parameters through the UL TCI state or joint TCI state.

[0076] 7. Support beam management function between cells.

[0077] In some scenarios, a serving cell (including single-TRP and multi-TRP scenarios) has only one TAG and a corresponding TA timer. When the TA timer expires, the UE needs to release all reserved uplink and downlink resources on the serving cell. When a serving cell is configured with multiple TAGs, how to release resources is an urgent problem that needs to be solved.

[0078] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0079] FIG7 is a schematic interaction diagram of a wireless communication method 200 according to an embodiment of the present application. As shown in FIG7 , the method 200 includes at least part of the following:

[0080] S210, when the timer corresponding to the first timing advance group TAG times out, the terminal device releases the resources associated with the first parameter, where the first parameter is associated with the first TAG.

[0081] In some embodiments, the first parameter may include, but is not limited to, at least one of the following parameters:

[0082] First TCI state, first spatial relation information, first control resource set pool index (CORESETPoolIndex), and first uplink RRC parameters.

[0083] In some embodiments, the first parameter is associated with a first network node, such as a first TRP.

[0084] In some embodiments, a network device (e.g., a base station) may correspond to multiple network nodes. For example, uplink transmissions associated with different first parameters may be considered to be received by different network nodes. For another example, downlink transmissions associated with different first parameters may be considered to be sent from different network nodes.

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

[0086] In some embodiments, the service cell of the terminal device is associated with at least two TAGs, the first TAG is one of the at least two TAGs, each TAG corresponds to a TAG ID, for example, the first TAG corresponds to the first TAG ID, the timer corresponding to the first TAG may refer to the timer corresponding to the first TAG ID, and the association between the first parameter and the first TAG may refer to the association between the first TAG ID and the first parameter.

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

[0088] In some embodiments of the present application, S210 includes:

[0089] When the timer corresponding to the first TAG times out and the timers corresponding to other TAGs among the at least two TAGs except the first TAG do not time out, the terminal device only releases the resources associated with the first parameter associated with the first TAG.

[0090] That is, when only the timer corresponding to the first TAG times out and the timers corresponding to other TAGs do not time out, it indicates that the terminal device has lost uplink synchronization with the first network node, but has not lost uplink synchronization with other network nodes. Therefore, the terminal device can release uplink and downlink resources only for the first network node without releasing all reserved uplink and downlink resources on the serving cell of the terminal device. For example, the resources are released according to the first parameter associated with the first TAG, for example, the resources associated with the first parameter are released.

[0091] In some embodiments, the association relationship between the first TAG and the first parameter may be predefined, configured by the network device, or determined according to a preset rule.

[0092] For example, as shown in FIG7 , the method further includes:

[0093] S201: A network device may send first configuration information to a terminal device, where the first configuration information is used to configure a first association relationship, where the first association relationship is an association relationship between a TAG and at least one of the following parameters: TCI status, spatial relationship information, CORESETPoolIndex, or an uplink RRC parameter. The first association relationship includes an association relationship between a first TCI status and a first parameter.

[0094] In some embodiments, the first configuration information is sent via at least one of the following signaling:

[0095] System messages, RRC signaling, media access control MAC control element CE, downlink control information DCI.

[0096] For example, a first TAG ID may be added to an information element (IE) of the first parameter to establish an association relationship between the first TAG and the first parameter.

[0097] The following describes how to release the first parameter and the associated resources in conjunction with specific embodiments.

[0098] Embodiment 1: The first parameter is a first TCI state.

[0099] 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).

[0100] In some embodiments, when the timer corresponding to the first TAG times out, the terminal device can determine the associated UL / joint TCI state according to the first TAG, and further the uplink resources associated with the UL / joint TCI state. The advantage of using the UL / joint TCI state and TAG association is that, compared with the solution in which the TAG is associated with the CORESETPoolIndex, the TAG can use the downlink reference signal contained in the UL / joint TCI state as a downlink synchronization time reference, that is, the terminal device can determine the transmission time of the physical random access channel (PRACH) based on the reception time of the downlink reference signal. In addition, in the millimeter wave frequency band, the UL / joint TCI state can provide beam-level downlink and uplink synchronization, which is more accurate than the synchronization at the network node level (in which a network node uses multiple beams for coverage, and the multiple beams experience different path transmission delays).

[0101] Embodiment 1-1-1: Release the PUCCH resources or PUCCH resource group applying the first uplink TCI state (UL TCI state) or the first joint TCI state (joint TCI state).

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

[0103] For example, when the timer corresponding to the first TAG times out, the terminal device can determine the associated uplink TCI state or joint TCI state based on the first TAG, and further release the PUCCH resources or PUCCH resource group to which the uplink TCI state or joint TCI state is applied.

[0104] In some embodiments, if the PUCCH resource or PUCCH resource group to which the first TCI state is applied is a first PUCCH resource or a first PUCCH resource group, then when the timer corresponding to the first TAG expires, the first PUCCH resource or the first PUCCH resource group may be released. That is, the resources associated with the first parameter include the first PUCCH resource or the first PUCCH resource group.

[0105] In some embodiments, the network device may configure (or indicate, activate) an uplink TCI state or a joint TCI state for a PUCCH resource or a PUCCH resource group. In this case, it may be considered that the uplink TCI state or the joint TCI state is applicable to the PUCCH resource or the PUCCH resource group. For example, the network device may configure a TCI state resource pool through RRC signaling, for example, including 128 UL / joint TCI states, further activate 8 TCI states or a combination of TCI states (including two joint / UL TCI states) through MAC CE, and finally indicate the target TCI state in the TCI state activated by MAC CE through the TCI state indication field (e.g., 3 bits) in the DCI (e.g., DCI format 1_1 / 1_2). The UL / joint TCI state indicated by the DCI is applicable to all PUCCH resources / resource groups and PUSCH resources configured by the network device.

[0106] In some embodiments, the network device may configure (or indicate, activate) an uplink TCI state or joint TCI state for a PUCCH resource or a PUCCH resource group (recorded as case 1), or may configure (or indicate, activate) multiple uplink TCI states or joint TCI states for a PUCCH resource or a PUCCH resource group (recorded as case 2), such as two uplink TCI states or two joint TCI states, or a combination of one uplink TCI state and one joint TCI state, in which case the terminal device transmits PUCCH to multiple network nodes. Optionally, the PUCCH transmission of the terminal device to multiple network nodes may adopt a time-division multiplexing (TDM) scheme (such as repeated transmission of PUCCH sent to different network nodes on different time domain resources), or may adopt an SFN scheme or an SDM scheme.

[0107] For case 1, when the timer corresponding to the first TAG expires, the terminal device can determine the associated uplink TCI state or joint TCI state based on the first TAG, and further release the PUCCH resources or PUCCH resource group to which the uplink TCI state or joint TCI state is applied.

[0108] For case 2: When the timer corresponding to the first TAG times out, as an implementation method, the first PUCCH resource or the first PUCCH resource group is released. This is because the terminal device has experienced uplink desynchronization with the first network node, and the repeated transmission of the PUCCH cannot be completed. Therefore, the first PUCCH resource or the first PUCCH resource group can be released. As another implementation method, the first PUCCH resource or the first PUCCH resource group is not released. This is because the terminal device has experienced uplink desynchronization with the first network node. When the terminal device does not experience uplink desynchronization with other network nodes, it can continue to send PUCCH to other network devices.

[0109] For example, when the first TAG is associated with the first UL / joint TCI state, the network device configures only the first UL / joint TCI state for the first PUCCH resource or the first PUCCH resource group, it can be considered that the first PUCCH resource or the first PUCCH resource group only corresponds to the first UL / joint TCI state, that is, the first PUCCH resource or the first PUCCH resource group only uses 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 the first UL / joint TCI state is applied, that is, the first PUCCH resource or the first PUCCH resource group. Alternatively, if the network device configures the first UL / joint TCI state and the second UL / joint TCI state for the first PUCCH resource or the first PUCCH resource group, it can be considered that the first PUCCH resource or the first PUCCH resource group corresponds to the first UL / joint TCI state and the second UL / joint TCI state, that is, the first PUCCH resource or the 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 applying the first UL / joint TCI state, that is, the first PUCCH resource or the first PUCCH resource group.

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

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

[0112] That is, 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, and the SRS resource or SRS resource set is configured to track the uplink signal indicated by the first TCI state.

[0113] In some embodiments, when the first SRS resource or the first SRS resource set is not configured with the UL / joint TCI state, that is, the first SRS resource or the first SRS resource set is not configured to follow the uplink signal, when the timer corresponding to the first TAG expires, the terminal device may choose to release the first SRS resource or the first SRS resource set, or may not release the first SRS resource or the first SRS resource set.

[0114] Embodiment 1-1-3: Release the pre-configured PUSCH resources applying the first uplink TCI state (UL TCI state) or the first joint TCI state (joint TCI state).

[0115] For example, when the timer corresponding to the first TAG times out, the terminal device can determine the associated uplink TCI state or joint TCI state according to the first TAG, and further release the pre-configured PUSCH resources associated with the uplink TCI state or joint TCI state.

[0116] That is, the resources associated with the first parameter include pre-configured PUSCH resources to which the first TCI state is applied.

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

[0118] For dynamically scheduled PUSCH resources, when a terminal device enters an uplink out-of-sync state with respect to a network node, the network device may avoid scheduling the terminal device to perform uplink transmission to the network node.

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

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

[0121] It should be understood that the above-mentioned embodiment 1-1-1, embodiment 1-1-2 and embodiment 1-1-3 can be implemented separately or in combination.

[0122] For example, when the timer corresponding to the first TAG expires, the terminal device can determine the associated UL / joint TCI state based on the first TAG, and further release at least two of the PUCCH resources applying the UL / joint TCI state, the associated SRS resources or SRS resource group of the UL / joint TCI state, and the pre-configured PUSCH resources applying the UL / joint TCI state.

[0123] Optionally, in this embodiment 1-1, the uplink resources associated with the first UL / joint TCI state may include at least one of the following:

[0124] PUCCH resources or PUCCH resource groups applying the first UL / joint TCI state;

[0125] The SRS resource or SRS resource group associated with the first UL / joint TCI state;

[0126] Apply the pre-configured PUSCH resources of the first UL / joint TCI state.

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

[0128] For example, when the timer corresponding to the first TAG times out, the terminal device can determine the associated DL / joint TCI state according to the first TAG, and further release the downlink resources associated with the first DL / joint TCI state.

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

[0130] For example, when the timer corresponding to the first TAG times out, the terminal device can determine the associated DL / joint TCI state according to the first TAG, and further release the HARQ cache corresponding to the PDSCH to which the DL / joint TCI state is applied.

[0131] That is, the resources associated with the first parameter include the HARQ buffer corresponding to the PDSCH to which the first DL / joint TCI state is applied.

[0132] In some embodiments, the PDSCH may be transmitted via a HARQ process, and the HARQ process may correspond to a HARQ buffer at the receiving end for soft combining of the received data. When the timer corresponding to the first TAG expires, the terminal device loses uplink synchronization with the first network node, and therefore, does not need to receive or process the PDSCH of the first network node. Therefore, the HARQ buffer corresponding to the PDSCH of the first DL / joint TCI state associated with the first TAG may be released.

[0133] Example 1-2-2: Release the pre-configured PDSCH resources applying the first DL / joint TCI state.

[0134] For example, when the timer corresponding to the first TAG times out, the terminal device may determine the associated DL / joint TCI state according to the first TAG, and further release the pre-configured PDSCH resources to which the DL / joint TCI state is applied.

[0135] That is, the resources associated with the first parameter include pre-configured PDSCH resources applying the first DL / joint TCI state.

[0136] Optionally, the pre-configured PDSCH resources include configured downlink assignment (Configured DL assignment).

[0137] In some embodiments, the network device can pre-configure the DL / joint TCI state for the Configured DL assignment, and further activate or indicate the target DL / joint TCI state. Then, when the timer corresponding to the first TAG expires, the terminal device can determine that uplink desynchronization has occurred to the first network node. Therefore, there is no need to receive or process the PDSCH of the first network node, and thus the pre-configured PDSCH resources of the DL / joint TCI state associated with the first TAG can be released.

[0138] It should be understood that the above-mentioned embodiment 1-2-1 and embodiment 1-2-2 can be implemented separately or in combination.

[0139] For example, when the timer corresponding to the first TAG expires, the terminal device can determine the associated DL / joint TCI state based on the first TAG, and further release the HARQ cache corresponding to the PDSCH applying the DL / joint TCI state and the pre-configured PDSCH resources applying the DL / joint TCI state.

[0140] Optionally, in this embodiment 1-1, the downlink resources associated with the first DL / joint TCI state may include at least one of the following:

[0141] Applying the HARQ buffer corresponding to the PDSCH of the first DL / joint TCI state;

[0142] The pre-configured PDSCH resources of the first DL / joint TCI state are applied.

[0143] It should also be understood that the above-mentioned embodiment 1-1 and embodiment 1-2 can be implemented separately or in combination.

[0144] For example, when the timer corresponding to the first TAG times out, the terminal device may determine the associated UL / joint TCI state and DL / joint TCI state according to the first TAG, and may further release the uplink resources associated with the UL / joint TCI state (for example, in Embodiments 1-1-1,

[0145] The uplink resources in Example 1-1-2 and Example 1-1-3) and the downlink resources associated with the DL / joint TCI state (for example, the downlink resources in Example 1-2-1 and Example 1-2-2).

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

[0147] The advantage of associating spatial relation information with TAG is that, compared to the solution of associating TAG with CORESETPoolIndex, the TAG can use the downlink reference signal contained in the spatial relation information as a downlink synchronization time reference, that is, the terminal device can determine the PRACH transmission time based on the reception time of the downlink reference signal. In addition, in the millimeter wave frequency band, spatial relation information can provide beam-level downlink and uplink synchronization, which is more accurate than network node-level synchronization (a network node uses multiple beams for coverage, and multiple beams experience different path transmission delays).

[0148] In some embodiments, spatial relation information may be configured for an uplink channel or an uplink signal, that is, the spatial relation information and the uplink channel or the uplink signal have an associated relationship.

[0149] For example, when the timer corresponding to the first TAG times out, the terminal device may determine the associated spatial relation information according to the first TAG, and further release the uplink resources associated with the spatial relation information.

[0150] Embodiment 2-1: The first spatial relationship information includes first PUCCH spatial relationship information (PUCCH-SpatialRelationInfo).

[0151] That is, the first TAG is associated with the first PUCCH-SpatialRelationInfo.

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

[0153] In some embodiments, when the timer corresponding to the first TAG times out, the terminal device may determine the associated PUCCH-SpatialRelationInfo according to the first TAG, and further release the PUCCH resource or PUCCH resource group associated with the PUCCH-SpatialRelationInfo. For example, the resource associated with the first parameter includes a second PUCCH resource or a second PUCCH resource group, wherein the second PUCCH resource or the second PUCCH resource group is the PUCCH resource or PUCCH resource group associated with the first PUCCH-SpatialRelationInfo.

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

[0155] In some embodiments, the network device may configure (or indicate, activate) one PUCCH-SpatialRelationInfo for a PUCCH resource or a PUCCH resource group (recorded as case 1), or may configure (or indicate, activate) multiple PUCCH-SpatialRelationInfo for a PUCCH resource or a PUCCH resource group (recorded as case 2), for example, two PUCCH-SpatialRelationInfo, in which case the terminal device transmits PUCCH to multiple network nodes. Optionally, the PUCCH transmission of the terminal device to multiple network nodes may adopt a TDM scheme, or may adopt an SFN scheme or an SDM scheme.

[0156] For case 1, when the timer corresponding to the first TAG times out, the terminal device can determine the associated PUCCH-SpatialRelationInfo according to the first TAG, and further release the PUCCH resource or PUCCH resource group associated with the PUCCH-SpatialRelationInfo.

[0157] For case 2: When the timer corresponding to the first TAG times out, as an implementation method, the second PUCCH resource or the second PUCCH resource group is released. This is because the terminal device has experienced uplink desynchronization with the first network node, and the repeated transmission of the PUCCH cannot be completed. Therefore, the second PUCCH resource or the second PUCCH resource group can be released. As another implementation method, the second PUCCH resource or the second PUCCH resource group is not released. This is because the terminal device has experienced uplink desynchronization with the first network node. When the terminal device does not experience uplink desynchronization with other network nodes, it can continue to send PUCCH to other network devices.

[0158] In embodiment 2-2, the first spatial relationship information includes first SRS spatial relationship information (SRS-SpatialRelationInfo).

[0159] That is, the first TAG is associated with the first SRS-SpatialRelationInfo.

[0160] Example 2-2-1: Release the SRS resource or SRS resource group associated with the first SRS-SpatialRelationInfo.

[0161] For example, when the timer corresponding to the first TAG times out, the terminal device may determine the associated SRS-SpatialRelationInfo according to the first TAG, and further release the SRS resource or SRS resource group associated with the SRS-SpatialRelationInfo.

[0162] For example, the resource associated with the first parameter includes a second SRS resource or an SRS resource group, wherein the second SRS resource or SRS resource group is the SRS resource or SRS resource group associated with the first SRS-SpatialRelationInfo.

[0163] In some embodiments, the network device may configure an SRS-SpatialRelationInfo for an SRS resource or an SRS resource group.

[0164] Example 2-2-2: Release the pre-configured PUSCH resources associated with the first SRS-SpatialRelationInfo.

[0165] For example, when the timer corresponding to the first TAG times out, the terminal device may determine the associated SRS-SpatialRelationInfo according to the first TAG, and further release the pre-configured PUSCH resources associated with the SRS-SpatialRelationInfo.

[0166] In this embodiment, the network device may configure an SRS resource for a PUSCH resource, and may configure an SRS-SpatialRelationInfo for the SRS resource. Then, the preconfigured PUSCH resource associated with the first SRS-SpatialRelationInfo may be the PUSCH resource associated with the SRS resource associated with the first SRS-SpatialRelationInfo.

[0167] In some embodiments, the antenna ports of the PUSCH resource and the associated SRS resource are the same.

[0168] In some embodiments, the pre-configured PUSCH resources include PUSCH resources carrying configured UL grants and / or PUSCH resources for semi-persistent CSI reporting.

[0169] It should also be understood that the above-mentioned embodiment 2-1 and embodiment 2-2 can be implemented separately or in combination.

[0170] For example, when the timer corresponding to the first TAG expires, the terminal device can determine the associated PUCCH-SpatialRelationInfo and SRS-SpatialRelationInfo based on the first TAG, and further release the PUCCH resources associated with the PUCCH-SpatialRelationInfo and the uplink resources associated with the SRS-SpatialRelationInfo (for example, the uplink resources in Example 2-2-1 and Example 2-2-2).

[0171] Optionally, in this embodiment 3, the uplink resource associated with the first spatial relation information may include at least one of the following:

[0172] The PUCCH resource or PUCCH resource group associated with the first PUCCH-SpatialRelationInfo;

[0173] The SRS resource or SRS resource group associated with the first SRS-SpatialRelationInfo;

[0174] The pre-configured PUSCH resource associated with the first SRS-SpatialRelationInfo.

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

[0176] Because CORESETPoolIndex, a network node-specific index for the downlink control channel, directly expresses the relationship between the network node and the tag, the relationship between the tag and CORESETPoolIndex can be used to release resources. Furthermore, compared to spatial relation information (which only applies to FR2), CORESETPoolIndex applies to both FR1 and FR2 frequency bands, enabling multi-TA enhancement across all frequency bands.

[0177] That is, the first TAG is associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0178] In some embodiments, when the timer corresponding to the first TAG times out, the terminal device may determine the associated uplink RRC parameter or CORESETPoolIndex according to the first TAG, and further release the resources associated with the uplink RRC parameter or CORESETPoolIndex.

[0179] Example 3-1: Release the first uplink RRC parameter or the PUCCH resources associated with the first CORESETPoolIndex.

[0180] For example, when the timer corresponding to the first TAG times out, the terminal device can determine the associated uplink RRC parameter or CORESETPoolIndex according to the first TAG, and further release the PUCCH resources associated with the uplink RRC parameter or CORESETPoolIndex.

[0181] That is, the resources associated with the first parameter include the first uplink RRC parameter or the PUCCH resources associated with the first CORESETPoolIndex.

[0182] In some embodiments, the network device may configure (or indicate, activate) an uplink RRC parameter or CORESETPoolIndex for the PUCCH resource, that is, the uplink RRC parameter or CORESETPoolIndex and the PUCCH resource have an associated relationship.

[0183] Example 3-2: Release the first uplink RRC parameter or the pre-configured PUSCH resources associated with the first CORESETPoolIndex.

[0184] For example, when the timer corresponding to the first TAG times out, the terminal device can determine the associated uplink RRC parameter or CORESETPoolIndex according to the first TAG, and further release the pre-configured PUSCH resources associated with the uplink RRC parameter or CORESETPoolIndex.

[0185] That is, the resources associated with the first parameter include the pre-configured PUSCH resources associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0186] In some embodiments, the pre-configured PUSCH resources may include Type 1 Configured Grant (CG) PUSCH resources and / or Type 2 CG PUSCH resources.

[0187] In some embodiments, the preconfigured PUSCH resource associated with the first uplink RRC parameter or the first CORESETPoolIndex includes at least one of the following:

[0188] Type 1 CG PUSCH resources associated with the first uplink RRC parameter or the first CORESETPoolIndex, Type 2 CG PUSCH resources associated with the first uplink RRC parameter or the first CORESETPoolIndex, and Type 2 CG PUSCH resources activated by the DCI associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0189] In some embodiments, the network device may configure (or indicate, activate) an uplink RRC parameter or CORESETPoolIndex for Type 1 CG PUSCH resources, that is, the uplink RRC parameter or CORESETPoolIndex and the Type 1 CG PUSCH resources have an associated relationship.

[0190] In some embodiments, the network device may configure (or indicate, activate) an uplink RRC parameter or CORESETPoolIndex for Type 2 CG PUSCH resources, that is, the uplink RRC parameter or CORESETPoolIndex and the Type 2 CG PUSCH resources have an associated relationship.

[0191] In some embodiments, Type 2 CG PUSCH is related to PDCCH. For example, Type 2 CG PUSCH needs to be activated through DCI in PDCCH. The PDCCH corresponds to an uplink RRC parameter or CORESETPoolIndex. When the timer corresponding to the first TAG expires, the terminal device can determine the associated uplink RRC parameter or CORESETPoolIndex according to the first TAG, further determine the DCI associated with the uplink RRC parameter or CORESETPoolIndex, and then release the Type 2 CG PUSCH activated by the DCI.

[0192] Example 3-3: Release the first uplink RRC parameter or the SRS resource or SRS resource set associated with the first CORESETPoolIndex.

[0193] For example, when the timer corresponding to the first TAG times out, the terminal device can determine the associated uplink RRC parameter or CORESETPoolIndex according to the first TAG, and further release the SRS resource or SRS resource set associated with the uplink RRC parameter or CORESETPoolIndex.

[0194] That is, the resources associated with the first parameter include the SRS resources or SRS resource set associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0195] In some embodiments, the SRS resource or SRS resource set associated with the first uplink RRC parameter or the first CORESETPoolIndex is a periodic or semi-continuous SRS resource, and the network device can configure the uplink RRC parameter or CORESETPoolIndex for the periodic or semi-continuous SRS resource (or, configure the second uplink RRC parameter or the second CORESETPoolIndex, that is, the parameter corresponding to the second network device). Then, when the timer corresponding to the first TAG times out, the terminal device can determine the associated uplink RRC parameter or CORESETPoolIndex according to the first TAG, and further release the SRS resource or SRS resource set associated with the uplink RRC parameter or CORESETPoolIndex (or, the uplink RRC parameter CORESETPoolIndex other than the uplink RRC parameter or CORESETPoolIndex).

[0196] Example 3-4: Release the HARQ cache corresponding to the DCI-scheduled PDSCH associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0197] For example, when the timer corresponding to the first TAG times out, the terminal device can determine the associated uplink RRC parameter or CORESETPoolIndex based on the first TAG, and further release the HARQ cache corresponding to the DCI-scheduled PDSCH associated with the uplink RRC parameter or CORESETPoolIndex.

[0198] That is, the resources associated with the first parameter include the HARQ cache corresponding to the DCI-scheduled PDSCH associated with the first uplink RRC parameter or the first CORESETPoolIndex.

[0199] It should be noted that DCI is transmitted through time-frequency resources, and the association between DCI and uplink RRC parameters or CORESETPoolIndex can be reflected as: the association between DCI and time-frequency resources.

[0200] For example, DCI is sent through CORESET, and each CORESET corresponds to a CORESETPoolIndex (if not configured, the default is "0"). The association relationship between CORESETPoolIndex and DCI can be the association relationship between DCI and the CORESET that sends the DCI.

[0201] In some embodiments, the PDSCH may be transmitted through a HARQ process, and the HARQ process may correspond to a HARQ buffer at the receiving end for soft combining of the received data. When the timer corresponding to the first TAG times out, the terminal device loses uplink synchronization with the first network node, and therefore does not need to receive or process the PDSCH of the first network node. Therefore, the HARQ buffer corresponding to the PDSCH scheduled by the DCI associated with the uplink RRC parameter associated with the first TAG or the CORESETPoolIndex may be released.

[0202] Example 3-5: Release the first uplink RRC parameter or the pre-configured PDSCH resources associated with the first CORESETPoolIndex.

[0203] For example, when the timer corresponding to the first TAG times out, the terminal device can determine the associated uplink RRC parameter or CORESETPoolIndex according to the first TAG, and further release the pre-configured PDSCH resources associated with the uplink RRC parameter or CORESETPoolIndex.

[0204] That is, the resources associated with the first parameter include the first uplink RRC parameter or the pre-configured PDSCH resources associated with the first CORESETPoolIndex.

[0205] Optionally, the pre-configured PDSCH resources include a configured downlink assignment (Configured DL assignment), such as a Type 2 Configured DL assignment.

[0206] In some embodiments, the network device can activate or deactivate the Configured DL assignment through DCI, which corresponds to an uplink RRC parameter or CORESETPoolIndex. When the timer corresponding to the first TAG expires, the terminal device can determine that an uplink loss of synchronization has occurred to the first network node. Therefore, there is no need to receive or process the PDSCH of the first network node. Therefore, the terminal device can determine the associated uplink RRC parameter or CORESETPoolIndex according to the first TAG, further determine the DCI associated with the uplink RRC parameter or CORESETPoolIndex, and then release the Configured DL assignment activated by the DCI.

[0207] In some embodiments, the first uplink RRC parameter or the resource associated with the first CORESETPoolIndex may include at least one of the following:

[0208] The first uplink RRC parameter or the PUCCH resource associated with the first CORESETPoolIndex;

[0209] The first uplink RRC parameter or the pre-configured PUSCH resource associated with the first CORESETPoolIndex;

[0210] The SRS resource or SRS resource set associated with the first uplink RRC parameter or the first CORESETPoolIndex;

[0211] The HARQ buffer corresponding to the DCI-scheduled PDSCH associated with the first uplink RRC parameter or the first CORESETPoolIndex;

[0212] The first uplink RRC parameter or the pre-configured PDSCH resource associated with the first CORESETPoolIndex.

[0213] It should be understood that the above-mentioned embodiments 3-1 to 3-5 can be implemented individually or in combination.

[0214] For example, when the timer corresponding to the first TAG times out, the terminal device can determine the associated uplink RRC parameter or CORESETPoolIndex according to the first TAG, and further release the uplink resources and / or downlink resources associated with the uplink RRC parameter or CORESETPoolIndex. For example, at least two of the PUSCH resources associated with the uplink RRC parameter or CORESETPoolIndex, the pre-configured PUSCH resources, the SRS resources, the HARQ buffer corresponding to the DCI-scheduled PDSCH, and the pre-configured PDSCH resources are released.

[0215] It should also be understood that the above-mentioned embodiments 1, 2 and 3 may be implemented separately or in combination.

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

[0217] For example, when the timer corresponding to the first TAG times out, the terminal device can determine the associated TCI state and spatial relation information based on the first TAG, and further release the uplink resources associated with the TCI state and the downlink resources associated with the TCI state, as well as the uplink resources associated with the spatial relation information.

[0218] For another example, when the timer corresponding to the first TAG times out, the terminal device can determine the associated spatial relation information and CORESETPoolIndex based on the first TAG, and further release the uplink resources associated with the CORESETPoolIndex and / or the downlink resources associated with the CORESETPoolIndex, as well as the uplink resources associated with the spatial relation information and the downlink resources associated with the spatial relation information.

[0219] For another example, when the timer corresponding to the first TAG times out, the terminal device can determine the associated TCI state, spatial relation information and CORESETPoolIndex based on the first TAG, and further release the uplink resources associated with the TCI state and / or the downlink resources associated with the TCI state, as well as the uplink resources associated with the CORESETPoolIndex and / or the downlink resources associated with the CORESETPoolIndex, and the uplink resources associated with the spatial relation information.

[0220] In summary, in an embodiment of the present application, when the timer corresponding to one of the at least two TAGs configured in the service cell of the terminal device times out, the terminal device can determine the associated first parameter based on the first TAG, and further release the resources associated with the first parameter, rather than releasing all reserved resources on the service cell of the terminal device, which is conducive to ensuring the normal communication between the terminal device and other network nodes and avoiding the terminal device from frequently initiating random access procedures.

[0221] The above, in conjunction with Figure 7, describes in detail the method embodiment of the present application. The following, in conjunction with Figures 8 to 12, describes in detail the device embodiment of the present application. It should be understood that the device embodiment and the method embodiment correspond to each other, and similar descriptions can refer to the method embodiment.

[0222] FIG8 shows a schematic block diagram of a terminal device 400 according to an embodiment of the present application. As shown in FIG8 , the terminal device 400 includes:

[0223] The processing unit 410 is used to release the resources associated with the first parameter when the timer corresponding to the first timing advance group TAG times out, where the first parameter is associated with the first TAG, and the first parameter includes at least one of the following: a first transmission configuration indication TCI state, first spatial relationship information, a first control resource set pool index, and a first uplink radio resource control RRC parameter.

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

[0225] 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, wherein the first PUCCH resource or the first PUCCH resource group is a PUCCH resource or a PUCCH resource group applying the first TCI state.

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

[0227] 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. 6. The method according to claim 2, wherein the resources associated with the first parameter include a Sounding Reference Signal (SRS) resource or SRS resource set associated with the first TCI state, wherein the SRS resource or SRS resource set is configured to track the uplink signal indicated by the first TCI state.

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

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

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

[0231] In some embodiments, the resources associated with the first parameter include a HARQ buffer corresponding to the PDSCH to which the first TCI state is applied.

[0232] In some embodiments, the resources associated with the first parameter include pre-configured PDSCH resources to which the first TCI state is applied.

[0233] In some embodiments, the pre-configured PDSCH resources include a configured downlink allocation.

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

[0235] In some embodiments, the resources associated with the first parameter include a second PUCCH resource or a second PUCCH resource group, wherein the second PUCCH resource or the second PUCCH resource group is the PUCCH resource or PUCCH resource group associated with the first PUCCH spatial relationship information.

[0236] In some embodiments, the second PUCCH resource or the second PUCCH resource group is associated only with the first PUCCH spatial relationship information; or

[0237] The second PUCCH resource or the second PUCCH resource group is associated with two pieces of PUCCH spatial relationship information, and the two pieces of PUCCH spatial relationship information include the first PUCCH spatial relationship information.

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

[0239] In some embodiments, the resource associated with the first parameter includes an SRS resource or an SRS resource associated with the first SRS spatial relationship information.

[0240] In some embodiments, 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.

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

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

[0243] In some embodiments, 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.

[0244] In some embodiments, the preconfigured PUSCH resource associated with the first uplink RRC parameter or the first control resource set pool index includes at least one of the following:

[0245] The type 1 configuration authorized CG PUSCH resources associated with the first uplink RRC parameter or the first control resource pool index, the type 2 CG PUSCH resources associated with the first uplink RRC parameter or the first control resource pool index, and the type 2 CG PUSCH resources activated by the downlink control information DCI associated with the first uplink RRC parameter or the first control resource pool index.

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

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

[0248] In some embodiments, 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.

[0249] In some embodiments, the pre-configured PDSCH resources include a downlink allocation of type 2 configuration.

[0250] In some embodiments, the serving cell of the terminal device is associated with at least two TAGs, the first TAG is one of the at least two TAGs, and when the timer corresponding to the first timing advance group TAG times out, the terminal device releases the resources associated with the first parameter, including:

[0251] When the timer corresponding to the first TAG times out and the timers corresponding to other TAGs among the at least two TAGs except the first TAG do not time out, the terminal device only releases the resources associated with the first parameter associated with the first TAG.

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

[0253] In some embodiments, the terminal device further includes:

[0254] A communication unit is used to receive first configuration information sent by a network device, where the first configuration information is used to configure a first association relationship, where the first association relationship is an association relationship between a TAG and at least one of the following parameters: TCI status, spatial relationship information, control resource set pool index, and uplink RRC parameters.

[0255] In some embodiments, the first association relationship includes an association relationship between a first TCI state and a first parameter, wherein 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.

[0256] In some embodiments, the first configuration information is sent via at least one of the following signaling:

[0257] System messages, RRC signaling, media access control MAC control element CE, downlink control information DCI.

[0258] Alternatively, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0259] It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the terminal device 400 are respectively for realizing the corresponding processes of the terminal device in the method 200 shown in Figure 7. For the sake of brevity, they will not be repeated here.

[0260] FIG9 shows a schematic block diagram of a network device 500 according to an embodiment of the present application. As shown in FIG9 , the network device 500 includes:

[0261] The communication unit 510 is configured to send first configuration information to a terminal device, where the first configuration information is used to configure a first association relationship, where the first association relationship is an association relationship between a timing advance group TAG and at least one of the following parameters:

[0262] The transmission configuration indicates TCI status, spatial relationship information, control resource set pool index, and uplink radio resource control RRC parameters.

[0263] In some embodiments, the first association relationship includes an association relationship between a first TCI state and a first parameter, wherein 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.

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

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

[0266] In some embodiments, 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.

[0267] In some embodiments, the first configuration information is sent via at least one of the following signaling:

[0268] System messages, RRC signaling, media access control MAC control element CE, downlink control information DCI.

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

[0270] It should be understood that the network device 500 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the above-mentioned and other operations and / or functions of each unit in the network device 500 are respectively for implementing the corresponding processes of the network device in the method 200 shown in Figure 7. For the sake of brevity, they will not be repeated here.

[0271] Figure 10 is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. The communication device 600 shown in Figure 10 includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0272] Optionally, as shown in FIG10 , the communication device 600 may further include a memory 620. The processor 610 may call and execute a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0273] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0274] Optionally, as shown in FIG10 , the communication device 600 may further include a transceiver 630 , and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

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

[0276] Optionally, the communication device 600 may specifically be a network device in an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0277] Optionally, the communication device 600 may specifically be a mobile terminal / terminal device in an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0278] Figure 11 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 700 shown in Figure 11 includes a processor 710, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0279] Optionally, as shown in FIG11 , the chip 700 may further include a memory 720. The processor 710 may call and execute a computer program from the memory 720 to implement the method in the embodiment of the present application.

[0280] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0281] Optionally, the chip 700 may further include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0282] Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0283] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0284] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0285] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0286] FIG12 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in FIG12 , the communication system 900 includes a terminal device 910 and a network device 920 .

[0287] Among them, the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 can be used to implement the corresponding functions implemented by the first network device and / or the second network device in the above method. For the sake of brevity, they will not be repeated here.

[0288] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can 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 devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0289] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0290] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0291] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0292] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0293] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0294] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0295] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the first network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0296] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0297] The embodiment of the present application also provides a computer program.

[0298] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0299] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0300] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0301] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0302] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0304] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0305] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0306] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that: include: When the timer corresponding to the first timing advance group TAG times out, the terminal device releases the resources associated with the first parameter, where the first parameter is associated with the first TAG, and the first parameter includes at least one of the following: a first transmission configuration indicating TCI status, first spatial relationship information, a first control resource set pool index, and a first uplink radio resource control RRC parameter.

2. The method according to claim 1, characterized in that The first TCI state includes a first uplink TCI state or a first joint TCI state.

3. The method according to claim 2, characterized in that The resources associated with the first parameter include a first physical uplink control channel PUCCH resource or a first PUCCH resource group, wherein the first PUCCH resource or the first PUCCH resource group is a PUCCH resource or a PUCCH resource group applying the first TCI state.

4. The method according to claim 3, characterized in that The first PUCCH resource or the first PUCCH resource group only applies the first TCI state.

5. The method according to claim 3, characterized in that: The first PUCCH resource or the first PUCCH resource group is a PUCCH resource or a PUCCH resource group to which the first TCI state and the second TCI state are applied.

6. The method according to any one of claims 2 to 5, characterized in that: 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, and the SRS resource or the SRS resource set is configured to track the uplink signal indicated by the first TCI state.

7. The method according to any one of claims 2 to 6, characterized in that: The resources associated with the first parameter include pre-configured physical uplink shared channel PUSCH resources applying the first TCI state.

8. The method according to claim 7, characterized in that The pre-configured PUSCH resources include PUSCH resources carrying configured uplink grants and / or PUSCH resources used for semi-persistent channel state information CSI reporting.

9. The method according to any one of claims 2 to 8, characterized in that: The first TCI state includes a first downlink TCI state or a first joint TCI state.

10. The method according to claim 9, characterized in that The resources associated with the first parameter include a HARQ cache corresponding to the PDSCH to which the first TCI state is applied.

11. The method according to claim 9 or 10, characterized in that: The resources associated with the first parameter include pre-configured PDSCH resources to which the first TCI state is applied.

12. The method according to claim 11, characterized in that The pre-configured PDSCH resources include configured downlink allocations.

13. The method according to any one of claims 1 to 12, characterized in that The first spatial relationship information includes first PUCCH spatial relationship information.

14. The method according to claim 13, characterized in that The resources associated with the first parameter include second PUCCH resources or second PUCCH resource groups, wherein the second PUCCH resources or second PUCCH resource groups are PUCCH resources or PUCCH resource groups associated with the first PUCCH spatial relationship information.

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

16. The method according to any one of claims 1 to 15, characterized in that The first spatial relationship information includes first SRS spatial relationship information.

17. The method according to claim 16, characterized in that The resources associated with the first parameter include SRS resources or SRS resources associated with the first SRS spatial relationship information.

18. The method according to claim 16 or 17, characterized in that The resources associated with the first parameter include pre-configured PUSCH resources associated with the SRS resources associated with the first SRS spatial relationship information.

19. The method according to claim 18, characterized in that The pre-configured PUSCH resources include PUSCH resources carrying configured uplink grants and / or PUSCH resources used for semi-persistent channel state information CSI reporting.

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

21. The method according to any one of claims 1 to 20, characterized in that 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.

22. The method according to claim 21, characterized in that The preconfigured PUSCH resource associated with the first uplink RRC parameter or the first control resource set pool index includes at least one of the following: The type 1 configuration associated with the first uplink RRC parameter or the first control resource set pool index grants CG PUSCH resources, The type 2 CG PUSCH resources associated with the first uplink RRC parameter or the first control resource set pool index, and the type 2 CG PUSCH resources activated by the downlink control information DCI associated with the first uplink RRC parameter or the first control resource set pool index.

23. The method according to any one of claims 1 to 22, characterized in that The resources associated with the first parameter include SRS resources or SRS resource sets associated with the first uplink RRC parameter or the first control resource set pool index.

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

25. The method according to any one of claims 1 to 24, characterized in that 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.

26. The method according to claim 25, characterized in that The pre-configured PDSCH resources include downlink allocations of type 2 configuration.

27. The method according to any one of claims 1 to 26, characterized in that The serving cell of the terminal device is associated with at least two TAGs, the first TAG is one of the at least two TAGs, and when the timer corresponding to the first timing advance group TAG times out, the terminal device releases resources associated with the first parameter, including: When the timer corresponding to the first TAG times out and the timers corresponding to other TAGs among the at least two TAGs except the first TAG have not timed out, the terminal device only releases the resources associated with the first parameter associated with the first TAG.

28. The method according to any one of claims 1 to 27, characterized in that The first TAG is a primary timing advance group PTAG among the at least two TAGs.

29. A wireless communication method, characterized in that: include: The network device sends first configuration information to the terminal device, where the first configuration information is used to configure a first association relationship, where the first association relationship is an association relationship between a timing advance group TAG and at least one of the following parameters: The transmission configuration indicates TCI status, spatial relationship information, control resource set pool index, and uplink radio resource control RRC parameters.

30. The method according to claim 29, characterized in that The first association relationship includes an association relationship between a first TCI state and a first parameter, wherein 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.

31. The method according to claim 30, characterized in that The first TCI state includes a first uplink TCI state or a first joint TCI state.

32. The method according to claim 30 or 31, characterized in that The first TCI state includes a first downlink TCI state or a first joint TCI state.

33. The method according to any one of claims 30 to 32, characterized in that 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.

34. The method according to any one of claims 29 to 33, characterized in that The first configuration information is sent via at least one of the following signalings: System messages, RRC signaling, media access control MAC control element CE, downlink control information DCI.

35. A terminal device, characterized in that: include: A processing unit, used to release resources associated with a first parameter when a timer corresponding to a first timing advance group TAG times out, wherein the first parameter is associated with the first TAG, and the first parameter includes at least one of the following: a first transmission configuration indicating a TCI state, first spatial relationship information, a first control resource set pool index, and a first uplink radio resource control RRC parameter.

36. The terminal device according to claim 35, characterized in that: The first TCI state includes a first uplink TCI state or a first joint TCI state.

37. The terminal device according to claim 36, characterized in that: The resources associated with the first parameter include a first physical uplink control channel PUCCH resource or a first PUCCH resource group, wherein the first PUCCH resource or the first PUCCH resource group is a PUCCH resource or a PUCCH resource group applying the first TCI state.

38. The terminal device according to claim 37, characterized in that: The first PUCCH resource or the first PUCCH resource group only applies the first TCI state.

39. The terminal device according to claim 37, characterized in that: The first PUCCH resource or the first PUCCH resource group is a PUCCH resource or a PUCCH resource group to which the first TCI state and the second TCI state are applied.

40. The terminal device according to any one of claims 36 to 39, characterized in that: 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, and the SRS resource or the SRS resource set is configured to track the uplink signal indicated by the first TCI state.

41. The terminal device according to any one of claims 36 to 40, characterized in that: The resources associated with the first parameter include pre-configured physical uplink shared channel PUSCH resources applying the first TCI state.

42. The terminal device according to claim 41, characterized in that: The pre-configured PUSCH resources include PUSCH resources carrying configured uplink grants and / or PUSCH resources used for semi-persistent channel state information CSI reporting.

43. The terminal device according to any one of claims 36 to 42, characterized in that: The first TCI state includes a first downlink TCI state or a first joint TCI state.

44. The terminal device according to claim 43, characterized in that: The resources associated with the first parameter include a HARQ cache corresponding to the PDSCH to which the first TCI state is applied.

45. The terminal device according to claim 43 or 44, characterized in that: The resources associated with the first parameter include pre-configured PDSCH resources to which the first TCI state is applied.

46. ​​The terminal device according to claim 45, characterized in that: The pre-configured PDSCH resources include configured downlink allocations.

47. The terminal device according to any one of claims 35-46, characterized in that: The first spatial relationship information includes first PUCCH spatial relationship information.

48. The terminal device according to claim 47, characterized in that: The resources associated with the first parameter include second PUCCH resources or second PUCCH resource groups, wherein the second PUCCH resources or second PUCCH resource groups are PUCCH resources or PUCCH resource groups associated with the first PUCCH spatial relationship information.

49. The terminal device according to claim 48, characterized in that: The second PUCCH resource or the second PUCCH resource group is associated only with the first PUCCH spatial relationship information; or The second PUCCH resource or the second PUCCH resource group is a PUCCH resource or a PUCCH resource group associated with the first PUCCH spatial relationship information and the second PUCCH spatial relationship information.

50. The terminal device according to any one of claims 35 to 49, characterized in that: The first spatial relationship information includes first SRS spatial relationship information.

51. The terminal device according to claim 50, characterized in that: The resources associated with the first parameter include SRS resources or SRS resources associated with the first SRS spatial relationship information.

52. The terminal device according to claim 50 or 51, characterized in that: The resources associated with the first parameter include pre-configured PUSCH resources associated with the SRS resources associated with the first SRS spatial relationship information.

53. The terminal device according to claim 52, characterized in that: The pre-configured PUSCH resources include PUSCH resources carrying configured uplink grants and / or PUSCH resources used for semi-persistent channel state information CSI reporting.

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

55. The terminal device according to any one of claims 35 to 54, characterized in that: 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.

56. The terminal device according to claim 55, characterized in that: The preconfigured PUSCH resource associated with the first uplink RRC parameter or the first control resource set pool index includes at least one of the following: The type 1 configuration authorized CG PUSCH resources associated with the first uplink RRC parameter or the first control resource pool index, the type 2 CG PUSCH resources associated with the first uplink RRC parameter or the first control resource pool index, and the type 2 CG PUSCH resources activated by the downlink control information DCI associated with the first uplink RRC parameter or the first control resource pool index.

57. The terminal device according to any one of claims 35-56, characterized in that: The resources associated with the first parameter include SRS resources or SRS resource sets associated with the first uplink RRC parameter or the first control resource set pool index.

58. The terminal device according to any one of claims 35 to 57, characterized in that: The resources associated with the first parameter include a HARQ buffer corresponding to a DCI-scheduled PDSCH associated with the first uplink RRC parameter or the first control resource set pool index.

59. The terminal device according to any one of claims 35 to 58, characterized in that: 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.

60. The terminal device according to claim 59, characterized in that: The pre-configured PDSCH resources include downlink allocations of type 2 configuration.

61. The terminal device according to any one of claims 35 to 60, characterized in that: The serving cell of the terminal device is associated with at least two TAGs, the first TAG is one of the at least two TAGs, and when the timer corresponding to the first timing advance group TAG times out, the terminal device releases resources associated with the first parameter, including: When the timer corresponding to the first TAG times out and the timers corresponding to other TAGs among the at least two TAGs except the first TAG have not timed out, the terminal device only releases the resources associated with the first parameter associated with the first TAG.

62. The terminal device according to any one of claims 35 to 61, characterized in that: The first TAG is a primary timing advance group PTAG among the at least two TAGs.

63. A network device, characterized in that: include: A communication unit, configured to send first configuration information to a terminal device, wherein the first configuration information is used to configure a first association relationship. The first association relationship is an association relationship between the timing advance group TAG and at least one of the following parameters: The transmission configuration indicates TCI status, spatial relationship information, control resource set pool index, and uplink radio resource control RRC parameters.

64. A terminal device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 1 to 28.

65. A network device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 29 to 34.

66. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 28, or a method as claimed in any one of claims 29 to 34.

67. A computer-readable storage medium, characterized in that Used to store a computer program, the computer program causing a 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.

68. A computer program product, characterized in that The method comprises computer program instructions which cause a computer to execute the method as claimed in any one of claims 1 to 28 or the method as claimed in any one of claims 29 to 34.

69. A computer program, characterized in that The computer program causes a 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.

Images