Method and apparatus for uplink transmission management

Abstract

The application provides a method for uplink (UL) transmission management performed by a user equipment (UE), the method comprising: determining, by the UE, a preset spatial domain transmission filter for UL resources according to at least one quasi-co-location (QCL) parameter of a control resource; determining, by the UE, that an uplink resource is not configured with a spatial domain transmission filter and a path loss reference reference signal (RS) resource; setting, by the UE, a control resource set (CORESET) after the determination; and transmitting, by the UE, the uplink resource by applying the preset spatial domain transmission filter.

Description

TECHNICAL FIELD

[0001] This application claims priority to U.S. Provisional Application No. 62 / 888,010, filed June 26, 2019, entitled “Signaling Overhead Reduction for Uplink Beam Management” (hereinafter “‘010 Provisional Application”), the entire disclosure of which is incorporated by reference herein.

[0002] The present disclosure relates to a wireless communication, and more particularly, to a method and apparatus for uplink transmission management. BACKGROUND

[0003] With the huge increase in the number of connected devices and the rapid growth of user / network (NW) traffic, various efforts have been made to improve different aspects of wireless communication for next-generation wireless communication systems, such as 5th-Generation (5G) New Radio (NR), by increasing data rates, latency, reliability, and mobility.

[0004] The 5G NR system aims to provide flexibility and configurability to optimize NW services and types, accommodating various use cases, such as enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable and low-latency communications (URLLC).

[0005] However, as the demand for radio access continues to increase, there is a need for further improvements in wireless communication technologies for next-generation wireless communication systems. SUMMARY

[0006] The present disclosure relates to a method and apparatus for uplink transmission management.

[0007] According to one embodiment of the present disclosure, a method for uplink transmission management of a wireless communication system performed by a user equipment (UE) is provided, including: determining a preset spatial domain transmission filter of an UL resource according to at least one quasi-co-location (QCL) parameter of a control resource set (CORESET) after determining that the UL resource is not configured with a spatial domain transmission filter and a path loss reference reference signal (RS) resource; and transmitting the UL resource by applying the preset spatial domain transmission filter.

[0008] A user equipment (UE) for uplink (UL) transmission management in a wireless communication system includes a memory and at least one processor coupled to the memory, the at least one processor configured to determine a default spatial domain transmission filter of a UL resource according to at least one quasi co-location (QCL) parameter of a control resource set (CORESET) upon determining that the UL resource is not configured with a spatial domain transmission filter and a path loss reference reference signal (RS) resource, and transmit the UL resource by applying the default spatial domain transmission filter. BRIEF DESCRIPTION OF DRAWINGS

[0009] The exemplary aspects of the present application can be better understood with reference to the following detailed description when considered in connection with the accompanying drawings, in which:

[0010] Figure 1 FIG. illustrates a list of spatial relation information configured for physical UL control channel (PUCCH) operation according to an embodiment of the present application;

[0011] Figure 2 FIG. illustrates a plurality of sounding reference signal (SRS) resource sets each configured with a path loss reference RS resource according to an embodiment of the present application;

[0012] Figure 3 FIG. illustrates a flowchart of a UL transmission management method according to an embodiment of the present application;

[0013] Figure 4 FIG. illustrates a flowchart of a UL transmission management method according to an embodiment of the present application;

[0014] Figure 5 FIG. illustrates a flowchart of a UL transmission management method according to an embodiment of the present application;

[0015] Figure 6 FIG. illustrates a block diagram of a node for wireless communication according to various aspects of the present application. DETAILED DESCRIPTION

[0016] The following description contains specific information pertaining to exemplary embodiments in the present application. The drawings in the present application and their accompanying detailed description are directed to exemplary embodiments. However, the present application is not limited to these exemplary embodiments. Other variations and implementations of the present application will occur to those skilled in the art upon consideration of the specification. Like or corresponding elements in the drawings are denoted by like or corresponding reference numerals, unless otherwise specified. Furthermore, the drawings in the present application and illustrations are generally not drawn to scale, and are not intended to correspond to actual relative sizes.

[0017] The following description includes specific information relating to example implementations in the present disclosure. The drawings in the present disclosure and their accompanying detailed description are directed to example implementations. However, the present disclosure is not only limited to these example implementations. Other variations and implementations of the present disclosure will occur to those skilled in the art. Unless otherwise noted, like or corresponding elements in the figures can be denoted by like or corresponding reference numerals. Furthermore, the drawings and illustrations in the present disclosure are generally not drawn to scale, and are not intended to correspond to actual relative dimensions.

[0018] For consistency and ease of understanding, like features are identified in the example figures by like numerals (although in some examples, not shown). However, features in different implementations can differ in other respects, and should not be narrowly construed by the figures shown.

[0019] References to “one implementation”, “an implementation”, “example implementation”, “various implementations”, “some implementations”, “implementations of the present disclosure”, etc. can mean that a particular feature, structure, or characteristic described in connection with the implementations can be included in some implementations of the present disclosure but not necessarily in all implementations of the present disclosure. Furthermore, repeated use of the phrase “in one implementation” or “in an implementation” or “in one implementation” does not necessarily refer to the same implementation, although they can. In addition, any use of the term “implementation” or “invention” in the description or the claims is not intended to necessarily limit the disclosure to that implementation or invention, but is intended to be interpreted in accordance with the broadest possible interpretation of the term “including” when used in the description or claims.

[0020] The term “and / or” herein is merely descriptive and not limiting. That is, the phrase “A and / or B” herein can mean: A alone, A and B, or B alone. The phrase “A and / or B and / or C” can mean: A alone, A and B, B alone, A and C, C alone, or A and B and C.

[0021] Furthermore, for purposes of explanation, specific details are set forth in order to provide a thorough understanding of the described technology. In other instances, detailed descriptions of well-known methods, techniques, systems, architectures, and the like are omitted so as not to obscure the description with unnecessary detail.

[0022] Those skilled in the art will immediately recognize that any of the NW functions or algorithms described in the present application can be implemented by hardware, software, or a combination of software and hardware. The described functions can correspond to modules that can be software, hardware, firmware, or any combination thereof. Software implementations can include computer-executable instructions stored on a computer-readable medium such as a memory or other type of storage device. For example, one or more microprocessors or general purpose computers with communication processing capabilities can be programmed with the corresponding executable instructions and perform the described NW function(s) or algorithm(s). The microprocessor or general purpose computer can be formed by an application specific integrated circuit (ASIC), a programmable logic array, and / or using one or more digital signal processors (DSPs). While some of the example implementations described in this specification are directed toward software installed and executed on computer hardware, however, alternative example implementations that are implemented as firmware or hardware or a combination of hardware and software are within the scope of the present application.

[0023] Computer-readable media include, but are not limited to, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, compact disc read only memory (CD-ROM), tape, cassette, magnetic disk storage or any other equivalent storage medium in which computer readable instructions can be stored.

[0024] A radio communication NW architecture (e.g., a Long Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, or an LTE-Advanced Pro system) typically includes at least one base station (BS), at least one UE, and one or more optional NW elements that provide connectivity to the NW. The UE communicates with the NW (e.g., a core NW (CN), an evolved packet core (EPC) NW, an evolved universal terrestrial radio access NW (E-UTRAN), a next generation core (NGC), or the Internet) through a radio access NW (RAN) established by the BS.

[0025] It is noted that in the present application, the UE can include, but is not limited to, a mobile station, a mobile terminal or device, a user communication radio terminal. For example, the UE can be a portable radio device including, but not limited to, a mobile phone, a tablet computer, a wearable device, a sensor, or a personal digital assistant (PDA) with wireless communication capabilities. The UE is configured to receive and transmit signals to one or more cells in the RAN over an air interface.

[0026] A BS can include, but is not limited to, a Node-B (NB) in a Universal Mobile Telecommunication System (UMTS), an evolved-NodeB (eNB) in LTE-A, a Radio NW Controller (RNC) as in UMTS, a base station controller (BSC) as in a Global System for Mobile communication (GSM) / General Packet Radio Service (GPRS) radio access NW (GERAN), a next generation eNB (ng-eNB) in E-UTRA BS, a next generation NodeB (gNB) in 5GC, 5G Access Network (5G-AN), and any other device capable of controlling wireless communication and managing radio resources within a cell. A BS can be connected through a radio interface to a NW to serve one or more UEs.

[0027] A BS can be configured to provide communication services according to at least one of the following radio access technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), GSM (commonly referred to as 2G), GERAN, General Packet Radio Service (GPRS), UMTS (commonly referred to as 3G) based on Basic Wideband-Code Division Multiple Access (W-CDMA), High Speed Packet Access (HSPA), LTE, LTE-A, Enhanced LTE (eLTE), NR, and LTE-A Pro (commonly referred to as 5G). However, the scope of the application should not be limited to the above-mentioned protocols.

[0028] A BS can be used to provide radio coverage to a specific geographic region using a plurality of cells included in a RAN. A BS can support operation of a cell. Each cell can be operable to serve at least one UE within its radio coverage. More specifically, each cell (commonly referred to as a serving cell) can provide service to serve one or more UEs within its radio coverage (e.g., each cell schedules downlink (DL) and optional uplink (UL) resources to at least one UE for DL and optional UL packet transmission within its radio coverage). A BS can communicate with one or more UEs in a radio communication system through a plurality of cells. A cell can allocate sidelink (SL) resources to support Proximity Service (ProSe). Each cell can have an overlapping coverage area with other cells. In a multi-RAT dual connectivity (MR-DC) case, a master cell group (MCG) or a secondary cell group (SCG) can be referred to as a special cell (SpCell). A primary cell (PCell) can refer to a SpCell of an MCG. A PSCell can refer to a SpCell of an SCG. An MCG refers to a group of serving cells associated with a master node (MN), including a SpCell and optionally one or more secondary cells (SCells). An SCG refers to a group of serving cells associated with a secondary node (SN), including a SpCell and optionally one or more SCells.

[0029] As mentioned above, the frame structure of NR will support flexible configurations to accommodate various next generation (e.g., 5G) communication requirements, such as eMBB, mMTC, and URLLC, while achieving high reliability, high data rate, and low latency requirements. The orthogonal frequency division multiplexing (OFDM) technology agreed in the Third Generation Partnership Project (3GPP) can be used as a baseline for the NR waveform. Scalable OFDM parameters, such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP), can also be used. In addition, NR considers two coding schemes: (1) low-density parity-check (LDPC) code and (2) polar code. The coding scheme adaptation can be configured based on channel conditions and / or service applications.

[0030] In addition, it is also considered that in a transmission time interval of a single NR frame, at least DL transmission data, a guard period, and UL transmission data should be included, where each part of the DL transmission data, the guard period, and the UL transmission data should also be configurable, for example, based on the dynamic of the NR-based NW. In addition, SL resources can also be provided in the NR frame to support ProSe services.

[0031] The NR system can support beam management to achieve, but not limited to, high frequency band (e.g., millimeter wave frequency band) communication. To cope with the higher path loss in the high frequency band, beamforming technology is adopted to provide additional gain, but at the cost of reduced spatial coverage for signal transmission and reception. To compensate for the spatial coverage loss of beamforming, the beam is steered in different directions in a time-division multiplexing (TDM) manner so that the UE or gNB can still understand the environment in which it has the required spatial coverage after a certain time.

[0032] In NR, such as Release-15 (Release-15 or Rel-15), beam management is supported by the transmission configuration indication (TCI) framework and spatial relationship information for DL and UL, respectively. For DL, different types of quasi co-location (Qusai-CoLocation, QCL) assumptions are indicated. Among them, QCL-type D is related to the spatial reception characteristics that can be used by the UE to receive the target RS or channel. In the UL direction, the spatial transmission characteristics can be indicated to the UE through the spatial relationship information provided by the NW side. The UE can accordingly perform UL transmission for UL channels and signals.

[0033] For UEs with beam correspondence, the DL beam management procedure involving DL beam measurement and reporting can provide sufficient information to select a suitable UL beam for UL transmission. In this case, not only can the UL beam sweeping procedure be saved, but also the UL beam indication signaling can be saved. However, this UL operation mode has not been introduced in the NR system.

[0034] To preserve the UL beam indication signaling for e.g. UL control channel (e.g. PUCCH), UL data channel (e.g. Physical UL Shared Channel (PUSCH)) or UL SRS, the relevant UL channel / signal for which the beam correspondence UE can need to be based on DL QCL assumption. In NR Rel-15 (e.g. Technical Specification (TS) 38.214 V15.5.0), the QCL assumption of the demodulation RS (DM-RS) port of the physical DL shared channel (PDSCH) of a serving cell can determine the QCL parameter of a CORESET configured to a UE based on the following. More specifically, the QCL assumption of the DM-RS port of the PDSCH of a serving cell can determine the QCL parameter of a CORESET configured to a UE according to the following text in Table 1:

[0035] Table 1 is as follows

[0036]

[0037] However, to enable the spatial relation information of PUCCH and / or the spatial relation information of SRS to follow the QCL parameter of CORESET, at least one of the following dimensions (i) to (vi) can also be considered.

[0038] • (i) PUCCH resources can be grouped, and the pre-defined spatial relation information determination of PUCCH can be based on PUCCH resource groups.

[0039] • (ii) DL CORESETs can be grouped, one CORESET group corresponds to e.g. the same transmission-reception point (TRP). The pre-defined spatial relation information determination of PUCCH / SRS can correspond to different CORESET groups.

[0040] • (iii) SRS resource set is configured with using: {codebook, nonCodebook, antennaSwitching} can need to be distinguished.

[0041] • (iv) Pathloss reference RS for UL power control can be configured differently for PUCCH resources and SRS resources. The pre-defined spatial relation information determination can consider this part.

[0042] • (v) Periodic (P) / Semi-Persistent (SP) / Aperiodic (AP) PUCCH transmission can follow different behaviors to determine the pre-defined spatial relation information.

[0043] • (vi) The pre-defined spatial relation information determination can distinguish self-scheduling and cross-carrier scheduling.

[0044] It should be understood that spatial relationships can be conceptualized as spatial domain transmission filters or beams. Therefore, in this invention, the terms "spatial relationship," "spatial domain transmission filter," and "beam" are used interchangeably.

[0045] 1. PUCCH's default spatial relationships

[0046] For PUCCH operation, the UE can be configured with at least one spatial relation (or "spatial domain transmission filter") via Radio Resource Control (RRC) signaling (e.g., RRC configuration) from the BS. Each spatial domain transmission filter can be indicated by a corresponding spatial relation information parameter in the RRC configuration (e.g., an information element (IE) denoted as pucch-spatialRelationInfo). Furthermore, the spatial relation information parameter can also indicate a DL path loss reference RS used to estimate the DL path loss for UL PUCCH power control purposes. For example, the spatial relation information parameter can include (or may include) an IE denoted as pucch-PathlossReferenceRS.

[0047] For each PUCCH resource, its corresponding spatial transmission filter can be selected from the spatial transmission filters configured for the UE and activated by Media Access Control (MAC) - Control Element (CE) activation signaling from the BS.

[0048] Figure 1 The illustration shows a list of spatial relationship information configured for PUCCH operation according to an embodiment of the present invention.

[0049] like Figure 1 As shown, the UE can configure a list 108 containing spatial relationship information via RRC signaling from the BS. The spatial relationship information list 108 may include one or more pucch-spatialRelationInfo IEs (e.g., pucch-spatialRelationInfo#1 to pucch-spatialRelationInfo#N, where N is a natural number), where each pucch-spatialRelationInfo IE can be used to indicate or determine the spatial domain transmission filter or beam for PUCCH operation. For example, for the transmission of PUCCH resources, the UE can select one of the pucch-spatialRelationInfo IEs in list 108 to apply (e.g., based on MAC-CE activation signaling from the BS). Figure 1As shown, the UE can be instructed by the BS (e.g., through MAC-CE activation signaling) to use / apply the spatial domain transmission filter indicated by the pucch-spatialRelationInfo IE#1 for transmitting the PUCCH resource 102, and use / apply the spatial domain transmission filter indicated by the pucch-spatialRelationInfo IE#3 for transmitting the PUCCH resource 104 and the PUCCH resource 106.

[0050] In addition, each pucch-spatialRelationInfo IE in the spatial relation information list can indicate a corresponding (DL) pathloss reference RS resource (not shown). For example, each pucch-spatialRelationInfo IE in the spatial relation information list can include (or be associated with) an indication of a pathloss reference RS resource.

[0051] If the UE is configured with only one spatial domain transmission filter (e.g., only one pucch-spatialRelationInfo IE in the list 108), the current spatial domain transmission filter in the list (e.g., the list 108) can be the one used for transmission of the PUCCH resources (e.g., the PUCCH resources 102, 104, and 106) assigned to the UE without MAC-CE activation signaling.

[0052] In an implementation, the PUCCH resources can be used in P / SP / AP manner. For example, P / SP PUCCH resources can be used for P / SP channel state information (CSI) reporting, and AP PUCCH resources can be used for hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback transmission.

[0053] The AP PUCCH transmission can be triggered by a DCI from the BS. The DCI can be transmitted by the BS in a DL component carrier (CC) paired with the UL CC where the AP PUCCH transmission occurs (self-carrier scheduling), or in a DL CC not paired with the UL CC where the AP PUCCH transmission occurs (cross-carrier scheduling). In this case, the supplementary UL (SUL) operation can be considered as self-carrier scheduling.

[0054] In an implementation, the UE can determine the spatial domain transmission filter for a PUCCH resource without explicit signaling from the BS. For example, when the UE cannot acquire the pucch-spatialRelationInfo IE from the NW signaling (e.g., signaling from the BS), the UE can apply a pre-set spatial domain transmission filter for the PUCCH resource.

[0055] In an embodiment, the pre-configured spatial domain transmission filter for each PUCCH resource allocated to the UE can be determined independently.

[0056] In an embodiment, the PUCCH resources can be grouped into one or more PUCCH resource groups. In this case, the pre-configured spatial domain transmission filter can be determined independently for each PUCCH resource group.

[0057] In an embodiment, the grouping of PUCCH resources can be formed implicitly or explicitly based on NW signaling. For example, the PUCCH resources associated with different UE panels can correspond to different PUCCH resource groups.

[0058] In an embodiment, a single pre-configured spatial domain transmission filter can be used for transmission of all PUCCH resources allocated to the UE.

[0059] In an embodiment, the pre-configured spatial domain transmission filter for the PUCCH resource can follow the QCL parameters of a CORESET, where the CORESET can be used for DLPDCCH monitoring.

[0060] In an embodiment, the CORESET can be associated with a CORESET group.

[0061] In an embodiment, the CORESET group can be associated with a TRP.

[0062] In an embodiment, the CORESET can or can not correspond to a DL CC paired with the UL CC where the PUCCH resource is located. For example, the transmission on the PUCCH resource can be triggered by a DCI, where the carrier indication field in the DCI can identify the UL CC.

[0063] In an embodiment, the PUCCH resource can be associated with a CORESET by the BS via implicit / explicit signaling. For example, the PUCCH resource can be associated with (or included in) a PUCCH resource group. The BS can associate the PUCCH resource group with a CORESET group (including the CORESET) by mapping the PUCCH resource group to the CORESET group via NW signaling.

[0064] In an embodiment, the CORESET can be associated with the monitored search space with the lowest CORESET-ID in the latest slot where the associated CORESET group (including the CORESET) is monitored by the UE.

[0065] In an embodiment, the associated CORESET group can include all configured CORESETs in the active BWP of the serving cell (or CC).

[0066] In an implementation, the transmission on the PUCCH resource can correspond to an instance of a P / SP PUCCH transmission.

[0067] In an implementation, the CORESET can be associated with a search space on which the DCI triggering the transmission on the PUCCH resource is received by the UE. For example, the transmission on the PUCCH resource transmission can correspond to an AP PUCCH transmission.

[0068] In an implementation, the CORESET can be pre-configured / pre-determined. In one example, the CORESET is predetermined to have the highest or lowest CORESET-ID index in the active DL BWP in the CC.

[0069] In an implementation, the RS associated with QCL Type D in the QCL parameter of the CORESET can be used to determine the pre-configured spatial domain transmission filter. In an implementation, the RS can be a path loss reference RS. For example, when the spatial domain transmission filter for the PUCCH transmission is not provided by the NW signaling through pucch-SpatialRelationlnfo, the path loss reference RS for the UL power control of the PUCCH transmission can be determined as:

[0070] - the RS indicated by the QCL parameter of the CORESET (if there are multiple RSs indicated by the QCL parameter, the RS associated with QCL-type D can be selected); or

[0071] - a pre-configured RS.

[0072] In an implementation, when the corresponding pucch-SpatialRelationlnfo for the PUCCH resource is not provided by the NW signaling, for determining the pre-configured spatial domain transmission filter for the transmission on the PUCCH resource (or “PUCCH transmission”), the PUCCH resource can be associated with (or included in) a PUCCH resource group, where the PUCCH resource group can be associated with a CORESET group. In this case, the pre-configured spatial domain transmission filter for the transmission on the PUCCH resource can be determined based on the QCL parameter of the CORESET associated with the monitored search space having the lowest CORESET-ID in the latest slot if the PUCCH resource is used for P / SP transmission. In an implementation, the pre-configured spatial domain transmission filter for the transmission on the PUCCH resource can be determined based on the QCL parameter of the CORESET associated with the search space on which the DCI triggering the transmission on the PUCCH resource is received if the PUCCH resource is used for AP transmission.

[0073] In one implementation, if there is more than one RS associated with a QCL parameter, the RS associated with QCL Type D can be used to determine the pre-configured spatial domain transmission filter for the PUCCH resource. In one example, for power control of the transmission on the PUCCH resource, the pathloss reference RS can be used as the pre-configured spatial domain transmission filter.

[0074] 2. Pre-configured spatial relation for SRS

[0075] The usage of SRS resource set can be configured as one of {beamManagement, codebook, nonCodebook, antennaSwitching} as specified in 3GPP NR specification (e.g., TS 38.331 V15.5.0). Each SRS resource can be RRC configured by the BS with SRS-SpatialRelationlnfo IE for determining its spatial domain transmission filter for UL transmission. For each SRS resource set, a (DL) pathloss reference RS resource (e.g., indicated by the IE denoted as pathlossReferenceRS) can be provided for estimating the DL pathloss for UL SRS power control purpose.

[0076] Figure 2 Figures illustrate a plurality of SRS resource sets each configured with a (DL) pathloss reference RS resource according to an implementation of the present application.

[0077] As shown in Figure 2 A UE can be provided with (or configured) a number of SRS resource sets (e.g., including SRS resource set 210 and SRS resource set 220). Each SRS resource set can be associated with (or include) one or more SRS resources. For example, SRS resource set 210 can include M SRS resources (e.g., SRS resource #1 212, SRS resource #2 214, and SRS resource #2 216), and SRS resource set 220 can include K SRS resources (e.g., SRS resource #1 224, SRS resource #2 226, and SRS resource #2 228), where M and K are natural numbers. Each SRS resource in a SRS resource set can be configured with a spatial domain transmission filter (e.g., indicated by SRS-SpatialRelationlnfo IE). For example, if a corresponding SRS-SpatialRelationlnfo IE is provided, a SRS resource can be transmitted based on the spatial domain transmission filter indicated by the corresponding SRS-SpatialRelationlnfo IE.

[0078] In addition, each SRS resource set can be configured with a path loss reference RS resource (e.g., indicated by the pathlossReferenceRS IE). Figure 2 As shown, SRS resource set 210 can be configured with path loss reference RS resource #1 218, and SRS resource set 220 can be configured with path loss reference RS resource #2 222.

[0079] SRS resources can be used in a P / SP / AP manner. For example, an AP SRS transmission can be triggered by a DCI, where the DCI can be transmitted in either 1) a DL CC paired with a UL CC in which the AP SRS transmission occurs, or 2) a CC in which the AP PUCCH transmission occurs in a DL CC not paired with a UL. In this case, for example, an SUL operation can be considered as scenario 1 above.

[0080] The following sections provide a method for determining a preset spatial domain transmission filter for transmission over SRS resources. For ease of illustration, an SRS resource whose associated SRS resource set is configured for use as a "codebook" may be referred to as an "SRS-codebook resource," an SRS resource whose associated SRS resource set is configured for use as a "nonCodebook" may be referred to as an "SRS-nonCodebook resource," and an SRS resource whose associated SRS resource set is configured for use as an "antennaSwitching" may be referred to as an "SRS-antennaSwitching resource." For example, if Figure 2 If the use of SRS resource set 210 shown is configured as "non-codebook", then SRS resources 212, 214 and 216 associated with (or included in) SRS resource set 210 are SRS-non-codebook resources.

[0081] 2.1 SRS - Non-Codebook Resources

[0082] In one implementation, one, two, three, or four SRS-nonCodebook resources can be configured in the corresponding resource set. Furthermore, an associated CSI-RS IE may be configured in the SRS-nonCodebook resource set. In this case, the spatial domain transport filter for the SRS-nonCodebook resource can be determined based on explicit NW signaling via the associated CSI-RS IE or SRS-SpatialRelationInfo IE, but the NW may not provide both to the UE simultaneously.

[0083] In an embodiment, the spatial domain transmission filter for SRS-nonCodebook resource can be determined without NW explicit signaling. For example, when the associated CSI-RS IE and SRS-SpatialRelationlnfo IE cannot be acquired from NW signaling, e.g., the UE can apply a pre-configured spatial domain transmission filter.

[0084] In an embodiment, the pre-configured spatial domain transmission filter for each SRS-nonCodebook resource allocated to the UE can be determined independently.

[0085] In an embodiment, the SRS-nonCodebook resources allocated to the UE can be grouped into one or more SRS-nonCodebook resource sets (e.g., SRS resource sets 210 and 220 shown in FIG. 2). In this case, a pre-configured spatial domain transmission filter can be determined for a SRS-nonCodebook resource set. For example, one SRS-nonCodebook resource set can correspond to one UE panel, and multiple SRS-nonCodebook resource sets can be configured to map to multiple UE panels. Figure 2

[0086] In an embodiment, the pre-configured spatial domain transmission filter for SRS-nonCodebook resource can follow the QCL parameters of a CORESET, where the CORESET is used for DLPDCCH monitoring.

[0087] In an embodiment, the CORESET can be associated with a CORESET group.

[0088] In an embodiment, the CORESET group can be associated with a TRP.

[0089] In an embodiment, the CORESET can or can not correspond to a DL CC paired with the UL CC where the SRS-nonCodebook resource is located. For example, the transmission on SRS-nonCodebook resource can be triggered by DCI, where the carrier indication field in the DCI can identify the UL CC.

[0090] In an embodiment, the SRS-nonCodebook resource can be associated with a CORESET by NW through implicit / explicit signaling. For example, the SRS-nonCodebook resource set associated with (or including) the SRS-nonCodebook resource can be mapped to the CORESET group associated with (or including) the CORESET by NW signaling.

[0091] ​In an embodiment, a CORESET can be associated with a monitored search space with the lowest CORESET-ID in the latest slot in which the CORESET group (e.g., including the CORESET) associated is monitored by the UE.

[0092] In an embodiment, the associated CORESET group can include all configured CORESETs in the DL active BWP of the serving cell (or CC).

[0093] In an embodiment, the transmission on the SRS-nonCodebook resource can correspond to an instance of P / SP SRS transmission.

[0094] In an embodiment, a CORESET can be associated with a search space on which the DCI triggering the transmission on the SRS-nonCodebook resource is received by the UE. For example, the transmission on the SRS-nonCodebook resource transmission can correspond to an AP SRS transmission.

[0095] In an embodiment, a CORESET can be pre-configured / pre-determined. In one example, the CORESET can be predetermined / pre-configured to be the one with the highest or lowest CORESET-ID in the active DL BWP in the CC.

[0096] In an embodiment, if the UE is provided with a PathlossReferenceRS IE, the pre-set spatial domain transmission filter can follow the QCL parameters of the PathlossReferenceRS IE configured for the associated SRS-nonCodebook resource set.

[0097] In an embodiment, an RS associated with QCL Type D in the QCL parameters of a CORESET can be used to determine the pre-set spatial domain transmission filter.

[0098] In an embodiment, the pre-set spatial domain transmission filter for the SRS-nonCodebook resource can follow the PUCCH resource with the lowest PUCCH resource ID (e.g., PUCCH-ResourceId) within the active UL BWP of the serving cell in which the SRS-nonCodebook resource is located. The PUCCH resource with the lowest PUCCH-ResourceId can be selected from the PUCCH resources for which the spatial relation information is activated by MAC-CE signaling.

[0099] In an embodiment, when the PathlossReferenceRS IE is not provided by the NW signaling for the associated SRS-nonCodebook resource set (e.g., in Figure 2In the case that the SRS resource set 210 shown does not have a path loss reference RS resource configured (#1218), the path loss reference RS for UL power control of SRS-nonCodebook resource transmission can be determined as:

[0100] - The RS indicated by the QCL parameter of CORESET (if there are multiple RSs indicated by the QCL parameter, you can choose the RS associated with QCL-type D);

[0101] - The CSI-RS associated with the corresponding SRS-nonCodebook resource set (e.g., indicated by associatedCSI-RSIE); or

[0102] - Pre-configured RS.

[0103] In one implementation, a preset spatial domain transmission filter for determining transmission on SRS-nonCodebook resources is provided by NW signaling when the SRS-SpatialRelationInfoIE corresponding to the SRS-nonCodebook and the associated CSI-RS IE corresponding to the SRS-nonCodebook are not present. The set of SRS-nonCodebook resources, including the SRS-nonCodebook resources, can be associated with a CORESET group. In this case, the preset spatial domain transmission filter for transmission on SRS-nonCodebook resources can be determined based on the QCL parameter of the CORESET associated with the monitored search space having the lowest CORESET-ID in the most recent time slot. If the SRS-nonCodebook resources are used for P / SP transmission, the UE monitors the CORESET group. In one implementation, if the SRS-nonCodebook resources are used for AP transmission, the preset spatial domain transmission filter for transmission on SRS-nonCodebook resources can be determined based on the QCL parameter of the CORESET associated with the search space, on which a DCI triggering transmission on the SRS-nonCodebook resources is received.

[0104] In one implementation, if there is more than one RS associated with the QCL parameter, the RS associated with QCL type D can be used to determine the preset spatial domain transmission filter.

[0105] In an embodiment, for power control of transmission on SRS-noncodebook resources, when a UE is not configured with a pathloss reference RS for a corresponding set of SRS-noncodebook resources (e.g., in case the UE is not configured with a PathlossReferenceRS IE for the corresponding set of SRS-noncodebook resources), the pathloss reference RS can be determined as a pre-configured spatial domain transmission filter for the corresponding SRS-noncodebook resources.

[0106] 2.2 SRS-codebook resources and SRS-antenna switching resources

[0107] In an embodiment, one or two SRS-codebook resources can be configured in a corresponding resource set. A UE can determine a spatial domain transmission filter for SRS-codebook resources and SRS-antenna switching resources without explicit indication from the NW. In addition, a pre-configured spatial domain transmission filter can be applied, for example, when a UE cannot obtain an SRS-SpatialRelationInfo IE from the NW signaling. In the following, for ease of illustration, an SRS resource that is either an SRS-codebook resource or an SRS-antenna switching resource can be denoted as an “SRS-ac resource”.

[0108] In an embodiment, a pre-configured spatial domain transmission filter for each SRS-ac resource allocated to a UE can be determined independently.

[0109] In an embodiment, a pre-configured spatial domain transmission filter can be configured by a BS based on a SRS-ac resource set basis.

[0110] In an embodiment, a pre-configured spatial domain transmission filter can be applied to a subset of SRS-ac resources in a SRS-ac resource set if the subset of SRS-ac resources is not configured with an SRS-SpatialRelationInfo IE.

[0111] In an embodiment, a method for determining a pre-configured spatial domain transmission filter can only be applied when each SRS-ac resource in a SRS-ac resource set is not configured with an SRS-SpatialRelationInfo IE.

[0112] In an embodiment, a SRS-ac resource set can be associated with a UE panel.

[0113] In an embodiment, a pre-configured spatial domain transmission filter for an SRS-ac resource can follow a QCL parameter for a CORESET for DL PDCCH monitoring.

[0114] In an embodiment, a CORESET can be associated with a CORESET group.

[0115] In an embodiment, a CORESET group can be associated with a TRP.

[0116] In an embodiment, a CORESET can or can not correspond to a DL CC paired with a UL CC where the SRS-ac resource is located. For example, the transmission on the SRS-ac resource can be triggered by a DCI, where the carrier indication field in the DCI can identify the UL CC.

[0117] In an embodiment, a SRS-ac resource can be associated with a CORESET by the NW through implicit or explicit signaling. For example, a SRS-ac resource set associated with (or including) the SRS-ac resource can be mapped to a CORESET group associated with (or including) the CORESET by NW signaling.

[0118] In an embodiment, a CORESET can be associated with a monitored search space with the lowest CORESET-ID in the latest slot where the associated CORESET group (including the CORESET) is monitored by the UE.

[0119] In an embodiment, the associated CORESET group can include all configured CORESETs in the DL active BWP of the serving cell (or CC).

[0120] In an embodiment, the transmission on the SRS-ac resource can correspond to an instance of P / SP SRS transmission.

[0121] In an embodiment, a CORESET can be associated with a search space where the DCI triggering the transmission on the SRS-ac resource is received.

[0122] In an embodiment, the transmission on the SRS-ac resource can correspond to an AP SRS transmission.

[0123] In an embodiment, a CORESET can be pre-configured / pre-determined. In one example, the CORESET is predetermined to be the one with higher or lowest CORESET-ID index in the active DL BWP in the CC.

[0124] In an embodiment, a pre-set spatial domain transmission filter for a SRS-ac resource can follow the QCL parameters of the PathlossReferenceRS IE of the associated SRS-non-codebook resource set (including the SRS-ac resource) if the UE is configured with the PathlossReferenceRS IE.

[0125] In an implementation, the RS associated with QCL Type D in the QCL parameter can be used as the pre-configured spatial domain transmission filter for the SRS-ac resource.

[0126] In an implementation, the pre-configured spatial domain transmission filter for the SRS-ac resource can follow the spatial domain transmission filter (e.g., determined by the pucch-SpatialRelationInfo IE) of the PUCCH resource with the lowest PUCCH-ResourceId in the active within the UL BWP of the serving cell where the SRS-ac resource is located.

[0127] In an implementation, when the PathlossReferenceRS IE is not provided by the NW signaling for the associated SRS-ac resource set, the pathloss reference RS for the UL power control of the SRS-ac resource transmission can be determined as:

[0128] - the RS indicated by the QCL parameter of the CORESET (if there are multiple RSs indicated by the QCL parameter, the RS related to QCL-type D can be selected); or

[0129] - a pre-configured RS.

[0130] In an implementation, when the SRS-SpatialRelationInfo IE corresponding to the SRS-ac resource is not provided by the NW signaling, for determining the pre-configured spatial domain transmission filter for the transmission on the SRS-ac resource, the SRS-ac resource set (including the SRS-ac resource) can be associated with a CORESET group. In this case, the pre-configured spatial domain transmission filter for the transmission on the SRS-ac resource can be determined based on the QCL parameter of the CORESET associated with the monitored search space with the lowest CORESET-ID in the latest slot. If the SRS-nonCodebook resource is used for P / SP transmission, the UE monitors the CORESET group. In an implementation, the pre-configured spatial domain transmission filter for the transmission on the SRS-nonCodebook resource can be determined based on the QCL parameter of the CORESET associated with the search space on which the DCI triggering the transmission on the SRS-nonCodebook resource is received - if the SRS-ac resource is used for AP transmission.

[0131] In an implementation, if there are more than one RS associated with the QCL parameter, the RS associated with QCL Type D can be applied to determine the pre-configured spatial domain transmission filter.

[0132] In one implementation, when no PathlossReferenceRS IE is configured for the corresponding SRS-ac resource set, for power control of transmission on the SRS-ac resource, the pathloss reference RS can be used as a pre-configured spatial domain transmission filter for the SRS-ac resource.

[0133] Figure 3 A flowchart of a method 300 of UL transmission management according to an implementation of the present application is illustrated. As shown, the method 300 includes acts 302 and 304. Figure 3

[0134] In act 302, the UE can determine a pre-configured spatial domain transmission filter RS resource for the UL resource according to at least one QCL parameter of the CORESET after determining that the UL resource is not configured with a spatial domain transmission filter and a pathloss reference.

[0135] Two antenna ports are said to be QCL if the channel that transmits a symbol on one antenna port can be inferred from the channel that transmits a symbol on the other antenna port. The above “channel properties” can include Doppler shift, Doppler spread, average delay, delay spread, and spatial receive (Rx) parameters. In NR specification, these properties can be categorized into different QCL types / parameters (e.g., QCL-TypeA parameter, QCL-TypeB parameter, QCL-TypeC parameter, and QCL-TypeD parameter). For example, QCL-TypeD (parameter) can refer to spatial receive parameters. QCL-TypeD (parameter) can also be referred to as a beam. The UE can determine the pre-configured spatial domain transmission filter based on the QCL type / parameter of the CORESET.

[0136] In one implementation, the UL resource can be a SRS resource included in a SRS resource set that is not configured with a pathloss reference RS resource. As shown, Figure 2 the BS can configure pathloss reference RS resources based on SRS resource sets, where each SRS resource set can include one or more SRS resources. In this case, the UE can apply various implementations described in Section 2.0 to determine whether the UL resource is configured with a spatial domain transmission filter and a pathloss reference RS resource. For example, when the BS does not configure a PathlossReferenceRS IE (indicating a pathloss reference RS resource) for a SRS resource set, the UE can determine that the SRS resource set is not configured with a pathloss reference RS. In addition, when a SRS resource is not configured with a SRS-SpatialRelationInfo IE (or spatial relation information parameter) indicating a spatial domain transmission filter for SRS transmission, the UE can determine that the SRS resource is not configured with a spatial domain transmission filter. ​

[0137] In an implementation, the UL resource and the CORESET can be associated with the same CC. For example, in the case that the CORESET is associated with (or contained in) a CORESET group in the DL active BWP of a CC, and UL resource is provided in the UL counterpart of the CC (paired CC or unpaired CC), the UL resource and the CORESET can be considered to be associated with the same CC.

[0138] In an implementation, the UL resource can be a PUCCH resource. In this case, the UE can apply the various implementations described in Section 1 to determine whether the PUCCH resource is configured with a spatial domain transmission filter and a path loss reference RS resource. For example, when the PUCCH resource is not configured with a pucch-spatialRelationInfo IE or a pucch-PathlossReferenceRS IE, the UE can determine that the PUCCH resource is not configured with a path loss reference RS resource. In addition, when the PUCCH resource is not configured with a pucch-spatialRelationInfo IE (or a spatial relation information parameter) indicating a spatial domain transmission filter for PUCCH transmission, the UE can determine that the PUCCH resource is not configured with a spatial domain transmission filter.

[0139] In an implementation, the UE can determine the default path loss reference RS resource for the UL resource by selecting an RS resource with QCL Type D from a plurality of RS resources indicated by at least one QCL parameter of the CORESET. For example, if the QCL parameter of the CORESET indicates RS#1 and RS#2, where RS#1 is associated with QCL-type A and RS#2 is associated with QCL-type D, the UE can select RS#2 as the default path loss reference RS resource for the UL resource.

[0140] In Action 304, the UE can transmit the UL resource by applying the default spatial domain transmission (Tx) filter. For example, the UE can transmit the UL resource by using spatial Tx and / or Rx parameters corresponding to the default spatial domain transmission filter.

[0141] Figure 4 A flowchart of a method 400 of UL transmission management according to an implementation of the present application is illustrated. The method 400 can be performed by a UE independently or in conjunction with the various implementations described in the present application. In addition, it should be noted that while the individual actions of Actions 402, 404, and 406 are depicted as individual blocks in Figure 4 Figure 4 ​The order in which the actions are executed is not intended to be limiting, and any number of the described blocks can be combined in any order to implement the method, or an alternate method. For example, the order of action 404 and action 406 can be exchanged.

[0142] In action 402, the UE can receive a configuration (e.g., an RRC configuration) via RRC signaling.

[0143] In action 404, the UE can determine, according to the configuration, that a SRS resource set that is not configured with a pathloss reference RS resource is for non-codebook-based PUSCH transmission. For example, the UE can determine, according to the configuration, that the usage of the SRS resource set is configured as “nonCodebook”.

[0144] In action 406, the UE can determine, according to the configuration, that a SRS resource included in the SRS resource set is not associated with a CSI-RS resource. For example, the UE can determine that the SRS resource is not associated with a CSI-RS resource when no associatedCSI-RS IE (for indicating a CSI-RS resource) is configured for the SRS resource set. The SRS resource can be Figure 3 One example of the UL resource mentioned in the foregoing.

[0145] Figure 5 A flowchart of a method 500 of UL transmission management according to an embodiment of the present application is illustrated. The method 500 can be performed by a UE independently or in conjunction with various implementations described in the present application.

[0146] In action 502, the UE can receive a configuration (e.g., an RRC configuration) via RRC signaling.

[0147] In action 504, the UE can determine whether a set of spatial domain transmission filters including at least one candidate spatial domain transmission filter for PUCCH transmission is provided in the configuration. As Figure 1 As shown, the list 108 of spatial relation information can indicate a set of spatial domain transmission filters including N candidate spatial domain transmission filters (e.g., indicated by PUCCH-spatialRelationInfo#1 to PUCCH-spatialRelationInfo#N, respectively). The spatial domain transmission filter of the PUCCH resource can be selected (e.g., by MAC CE signaling from the BS) from one of the N candidate spatial domain transmission filters.

[0148] In act 506, the UE can determine that the PUCCH resource is not configured with spatial domain transmission filters when a set of spatial domain transmission filters is not provided in the configuration. For example, if the PUCCH resource is not RRC configured with a list of spatial relation information (e.g., the list of spatial relation information 108 shown in FIG. 6B), the UE can determine that the PUCCH resource is not configured with spatial domain transmission filters. The PUCCH resource can be an example of the UL resource mentioned in Figure 1 Figure 3

[0149] In an implementation, the UE can send a UE capability message to the BS indicating that the UE supports beam correspondence. If the UE supports beam correspondence, it can mean that the UE has the capability, e.g., to select a suitable beam for UL transmission based on DL measurements, whether or not relying on UL beam sweeping.

[0150] The following provides non-limiting descriptions of certain terms.

[0151] Beam failure recovery: A movement or other event in the environment can cause a currently established beam pair to fail without sufficient time for a beam reporting mechanism (which can be similar to a CSI reporting mechanism) to occur on the physical (PHY) channel. A beam failure recovery procedure can be used to handle such events with a shorter reaction time.

[0152] Beam: The term “beam” here can be replaced by “spatial domain transmission filter.” For example, when a UE reports a preferred gNB Tx beam, the UE is essentially selecting a spatial filter for the gNB to use. The term “beam information” can be used to provide information about which beam / spatial domain transmission filter is being used / selected. In an implementation, a separate RS can be transmitted by applying a separate beam (spatial domain transmission filter). Thus, in some implementations of the present disclosure, the term “beam” or “beam information” can be represented by an RS resource index.

[0153] HARQ: A function that ensures delivery between peer entities at layer 1 (e.g., the PHY layer). A single HARQ process can support one transport block (TB) when the PHY layer is not configured for DL / UL spatial multiplexing, and one or more TBs when the PHY layer is configured for DL / UL spatial multiplexing. In an implementation, there can be one HARQ entity per serving cell. Each HARQ entity can support a parallel (number) of DL and UL HARQ processes.

[0154] ​​Timer: The MAC entity can set one or more timers for individual purposes, e.g., to trigger some UL signaling retransmission or to limit some UL signaling retransmission period. A timer, once started, runs until it is stopped or expires; otherwise it is not running. A timer can be started if it is not running and restarted if it is running. A timer always starts or restarts from its initial value. The initial value can be configured by the BS (e.g., gNB) through DL RRC signaling, but not limited to.

[0155] BWP: A subset of the total cell bandwidth of a cell is referred to as a BWP. Bandwidth adaptation can be achieved by configuring a UE with BWPs and telling the UE which of the configured BWPs is the currently active one. To enable bandwidth adaptation (BA) on the PCell, the gNB can configure a UE with UL and DL BWPs. To enable BA on SCells in case of carrier aggregation (CA), the gNB can configure a UE with at least DL BWPs (e.g., none in UL). For a PCell, the initial BWP can be the BWP used for initial access. For an SCell, the initial BWP can be the BWP configured to the UE to operate first upon activation of the SCell. A UE can be configured with a first active UL BWP by the firstActiveUplinkBWP IE. If a first active UL BWP is configured for a SpCell, the firstActiveUplinkBWP IE field can contain the ID of the UL BWP to be activated upon the UE performing a RRC (re)configuration procedure. If the field is not present, the RRC (re)configuration procedure can not enforce a BWP switch. If a first active UL BWP is configured for an SCell, the firstActiveUplinkBWP IE field can contain the ID of the UL BWP to be used upon MAC activation of the SCell.

[0156] QCL: Two antenna ports are QCLed if the channel that conveys the symbols on one antenna port can be inferred from the channel that conveys the symbols on another antenna port. The above-mentioned “properties of the channel” can include at least one of Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameters. These properties can be grouped into different QCL types in NRTS. For example, QCL-type D refers to spatial Rx parameters. QCL type D can be referred to as “beam”.

[0157] TCI state: A TCI state can contain parameters for configuring a QCL relationship between one or two DL RS and a target RS set. For example, the target RS set can be the DM-RS ports of PDSCH or PDCCH.

[0158] Normal Scheduling Request (SR): A normal SR can be used to request UL shared channel (UL-SCH) resources (e.g., PUSCH resources) for new transmission. A UE can be configured with zero, one, or more than one normal SR configuration. A normal SR configuration can include a set of PUCCH resources for SR across different BWPs and cells. At most one PUCCH resource for SR per BWP can be configured for a logical channel. Each normal SR configuration can correspond to one or more logical channels. Each logical channel can be mapped to zero or one normal SR configuration. The normal SR configuration of a logical channel that triggers a buffer status report (BSR) procedure, if present, can be considered as the normal SR configuration corresponding to the triggered SR procedure. When a normal SR procedure is triggered, the normal SR procedure can be considered as pending until it is cancelled.

[0159] Beam correspondence: Beam correspondence is the ability of a UE to select a suitable beam for UL transmission based on DL measurements with or without UL beam sweeping. Alternatively, beam correspondence can be referred to as the ability of a UE to be indicated a suitable beam for DL reception based on an UL beam sweeping procedure.

[0160] Figure 6 A block diagram of a node 600 for wireless communication is shown in accordance with various aspects of the present disclosure. As shown, the node 600 can include a transceiver 606, a processor 608, a memory 602, one or more presentation components 604, and at least one antenna 610. The node 600 can also include a radio frequency (RF) spectrum band module, a BS communication module, a NW communication module, and a system communication management module, input / output (I / O) ports, I / O components, and a power supply (not explicitly shown). Each of these components can communicate with one another directly or indirectly, over one or more buses 624. In one implementation, the node 600 can be a UE or a BS performing various functions described herein, for example, with reference to Figure 6 . Figure 6 Figures 1 to 5 .

[0161] The transceiver 606, with transmitter 616 (e.g., transmit / transmit circuitry) and receiver 618 (e.g., receive / receive circuitry), can be configured to transmit and / or receive time and / or frequency resource partitioning information. In one implementation, the transceiver 606 can be configured to transmit in different types of subframes and time slots, including but not limited to, available, unavailable, and flexible available subframes and time slot formats. The transceiver 606 can be configured to receive data and control channels.

[0162] ​Node 600 may include a variety of computer-readable media. Computer-readable media can be any available media accessible to Node 600, and includes volatile (and non-volatile) media and removable (and non-removable) media. By way of example and not limitation, computer-readable media may include computer storage media and communication media. Computer storage media may include volatile (and non-volatile) and removable (and non-removable) media implemented according to any method or technology used for storing computer-readable information.

[0163] Computer storage media include RAM, ROM, EEPROM, flash memory (or other storage technologies), CD-ROM, DVD (or other optical disc storage), magnetic tape cartridges, magnetic tape, disk storage (or other magnetic storage devices), etc. Computer storage media do not include transmitted data signals. Communication media can typically embody computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and include any information transmission medium. The term "modulated data signal" can refer to a signal having one or more of its characteristics, set or altered in a manner that encodes information in the signal. By way of example and not limitation, communication media can include wired media, such as wired NW or direct wired connections, and wireless media, such as acoustic, RF, infrared, and other wireless media. Any combination of the above should also be included within the scope of computer-readable media.

[0164] Memory 602 may include computer storage media in the form of volatile and / or non-volatile memory. Memory 602 may be removable, non-removable, or a combination thereof. For example, memory 602 may include solid-state memory, hard disk drive, optical disk drive, etc. Figure 6 As shown, memory 602 may store computer-readable and / or executable instructions 614 (e.g., software code) configured to cause processor 608 to perform various functions described herein when executed, for example, referencing Figures 1 to 5 Alternatively, instruction 614 may not be directly executed by processor 608, but can be configured to cause node 600 (e.g., when compiled and executed) to perform the various functions described herein.

[0165] Processor 608 (e.g., having processing circuitry) may include intelligent hardware devices, central processing units (CPUs), microcontrollers, ASICs, etc. Processor 608 may include memory. Processor 608 can process data 612 and instructions 614 received from memory 602, as well as information transmitted via transceiver 606, baseband communication module, and / or NW communication module. Processor 608 can also process information to be transmitted to transceiver 606 for transmission via antenna 610, or to NW communication module for transmission to CN.

[0166] One or more presentation components 604 can present the data indications to humans or other devices. Examples of presentation components 604 can include display devices, speakers, printing components, vibrating components, and the like.

[0167] It will be apparent to those skilled in the art that various techniques can be used to implement the concepts described herein without departing from the scope of the concepts described in this application. Moreover, while the concepts have been described with specific reference to certain implementations, a person of ordinary skill in the art will recognize that changes can be made in form and detail without departing from the scope of those concepts. Accordingly, the described implementations are to be considered illustrative and not restrictive, and the intention is not to limit the concepts to the details illustrated, since such details can vary depending on specific implementation. It is therefore intended that the disclosure not be limited to the described implementations, but that the implementations be construed in accordance with the appended claims.

Claims

1. An uplink transmission management method for a wireless communication system performed by a user equipment, the method comprising: comprising: determining a default spatial domain transmission filter for the uplink resource based on at least one quasi co-location parameter of a control resource set configured to the user equipment upon determining that the uplink resource is not configured with a spatial domain transmission filter and a pathloss reference reference signal resource; and transmitting the uplink resource by applying the default spatial domain transmission filter, the uplink resource being a sounding reference signal resource included in a sounding reference signal resource set that is not configured with a pathloss reference reference signal resource.

2. The method of claim 1, wherein, further comprising: receiving a configuration through radio resource control signaling; determining that the sounding reference signal resource set is for non-codebook based physical uplink shared channel transmission according to the configuration; and determining that the uplink resource is not associated with a channel state information reference signal resource according to the configuration.

3. The method of claim 1, wherein: wherein the uplink resource and the control resource set are associated with a same component carrier.

4. The method of claim 1, wherein, further comprising: sending, through the transceiver, the user equipment capability message to the base station indicating that the user equipment supports beam correspondence.

5. The method of claim 1, wherein, further comprising: determining a default pathloss reference reference signal resource for the uplink resource by selecting a reference signal resource of a quasi co-location type D from a plurality of the reference signal resources indicated by at least one quasi co-location parameter of the control resource set.

6. A user equipment for uplink transmission management in a wireless communication system, c h a r a c t e r i z e d b y comprising: comprising: a transceiver; one or more non-transitory computer-readable media containing computer-executable instructions; and at least one processor coupled to the transceiver and the one or more non-transitory computer-readable media, the computer-executable instructions causing the user equipment to: determining a default spatial domain transmission filter for the uplink resource based on at least one quasi co-location parameter of a control resource set configured to the user equipment upon determining that the uplink resource is not configured with a spatial domain transmission filter and a pathloss reference reference signal resource; and transmitting the uplink resource by applying the default spatial domain transmission filter and through the transceiver, the uplink resource being a sounding reference signal resource included in a sounding reference signal resource set that is not configured with a pathloss reference reference signal resource.

7. The user device of claim 6, wherein: wherein, the computer-executable instructions further cause the user equipment to: receiving a configuration through radio resource control signaling and through the transceiver; determining that the sounding reference signal resource set is for non-codebook based physical uplink shared channel transmission according to the configuration; and determining that the uplink resource is not associated with a channel state information reference signal resource according to the configuration.

8. The user device of claim 6, wherein: wherein the uplink resource and the control resource set are associated with a same component carrier.

9. The user device of claim 6, wherein: wherein, the computer-executable instructions further cause the user equipment to: sending, through the transceiver, the user equipment capability message to the base station indicating that the user equipment supports beam correspondence.

10. The user device of claim 6, wherein: wherein, the computer-executable instructions further cause the user equipment to: determining a default pathloss reference reference signal resource for the uplink resource by selecting a reference signal resource of a quasi co-location type D from a plurality of the reference signal resources indicated by at least one quasi co-location parameter of the control resource set.

Images