Method and device for determining preset spatial relationship information

Abstract

A method performed by a user equipment (UE) includes receiving configuration signaling from a cell, the configuration signaling configuring one or more physical uplink control channel resources for the UE over an active uplink bandwidth portion, the one or more physical uplink control channel resources being not configured with physical uplink control channel-spatial relationship information, the one or more physical uplink control channel resources being not configured with physical uplink control channel-spatial relationship information, and the one or more physical uplink control channel-spatial relationship information being not configured with physical uplink control channel-spatial relationship information. And configuring a signaling to indicate to start a preset spatial relationship behavior of physical uplink shared channel transmission of downlink control information format 0 scheduling. Receiving a downlink control information format 0 on the active downlink bandwidth part from the cell, wherein the downlink control information format 0 provides scheduling information of a physical uplink shared channel; and determining a preset spatial relationship behavior of the spatial relationship according to a quasi-co-location-type D reference signal corresponding to the quasi-co-location hypothesis of the predetermined control resource set on the active downlink bandwidth part of the cell, and sending the physical uplink shared channel.

Description

[0001] This application is a divisional application of the invention patent with application number 202080074000X (PCT / CN2020 / 125455), application date of October 30, 2020, and invention title "Method and apparatus for determining preset spatial relationship information". Technical Field

[0002] This application claims priority to U.S. Provisional Application No. 62 / 929,287, filed November 1, 2019, entitled "Determination of Preset Spatial Relationship Information Based on DL Quasi-Cooperative Positioning" (hereinafter referred to as "'287 Provisional Application"). The entire disclosure of '287 Provisional Application is incorporated herein by reference.

[0003] This invention relates to wireless communication, and more specifically, to a method and apparatus for determining preset spatial relationship information. Background Technology

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

[0005] 5G NR systems are designed to provide flexibility and configurability to optimize NW services and types to suit a variety of use cases, such as enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable and low-latency communications (URLLC).

[0006] However, with the continued increase in demand for radio access, there is a need to further improve wireless communication in next-generation wireless communication systems. Summary of the Invention

[0007] This invention relates to a method and apparatus for determining preset spatial relationship information.

[0008] According to one aspect of the present invention, a user equipment is disclosed, the user equipment comprising: one or more non-transient calculator-readable media having calculator-executable instructions embedded thereon; and at least one processor coupled to the one or more non-transient calculator-readable media and configured to execute the calculator-executable instructions to: receive configuration signaling from a cell to configure one or more Physical Uplink Control Channel (PUCCH) resources for the UE on an active uplink (UL) bandwidth portion (BWP), wherein the one or more PUCCH resources are not configured with PUCCH-Spatial Relation Information (PUCCH-SpatialRelationInfo), and the configuration signaling indicates that a preset spatial relation behavior for Physical Uplink Shared Channel (PUSCH) transmission scheduled by Downlink Control Information (DCI) format 0_0 is enabled; receive DCI format 0_0 from the cell on an active downlink (DL) BWP, wherein DCI format 0_0 provides PUSCH scheduling information; and transmit PUSCH according to the preset spatial relation behavior, wherein the preset spatial relation behavior is based on the PUSCH scheduling information provided by the active DL BWP. The QCL assumptions of the predefined control resource set (CORESET) on the space determine a spatial relationship. The corresponding quasi-co-location (QCL)-type D (QCL-Type D) reference signal (RS) determines a spatial relationship.

[0009] According to another aspect of the present invention, a method performed by a user equipment (UE) is disclosed, the method comprising: receiving configuration signaling from a cell to configure one or more Physical Uplink Control Channel (PUCCH) resources for the UE on an active uplink (UL) bandwidth portion (BWP), wherein the one or more PUCCH resources are not configured with PUCCH-Spatial Relation Information (PUCCH-SpatialRelationInfo), and the configuration signaling indicates that a preset spatial relation behavior for physical uplink shared channel (PUSCH) transmission scheduled by downlink control information (DCI) format 0_0 is enabled; receiving DCI format 0_0 from the cell on an active downlink (DL) BWP, wherein DCI format 0_0 provides PUSCH scheduling information; and transmitting PUSCH according to the preset spatial relation behavior, the preset spatial relation behavior determining a spatial relation based on a quasi-cooperative positioning (QCL)-Type D (QCL-Type D) reference signal (RS) corresponding to a QCL assumption of a predetermined control resource set (CORESET) on the active DL BWP.

[0010] According to another embodiment of the present invention, a method performed by a base station is disclosed, the method comprising: receiving configuration signaling from a cell to configure one or more Physical Uplink Control Channel (PUCCH) resources for a UE on an Active Uplink (UL) Bandwidth Part (BWP), wherein the one or more PUCCH resources are not configured with PUCCH-Spatial Relation Information (PUCCH-SpatialRelationInfo), and the configuration signaling indicates that a preset spatial relation behavior for Physical Uplink Shared Channel (PUSCH) transmission scheduled by Downlink Control Information (DCI) format 0_0 is enabled; receiving DCI format 0_0 from the cell on an Active Downlink (DL) BWP, wherein DCI format 0_0 provides PUSCH scheduling information; and transmitting PUSCH according to the preset spatial relation behavior, wherein the preset spatial relation behavior determines a spatial relation based on a Quasi-Cooperative Positioning (QCL)-Type D (QCL-Type D) Reference Signal (RS) corresponding to a QCL assumption of a predetermined control resource set (CORESET) on the Active DL BWP. Attached Figure Description

[0011] The exemplary viewpoint of this case can be better understood by referring to the accompanying drawings. Note that the various features in the drawings are not drawn to scale, and their dimensions can be arbitrarily increased or decreased for clarity of discussion.

[0012] Figure 1 The illustration shows a list of spatial relationship information configured for operation of the Physical UL Control Channel (PUCCH) according to an embodiment of the present disclosure;

[0013] Figure 2 The illustration shows 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 disclosure;

[0014] Figure 3 The illustration shows a flowchart of a method for determining preset spatial relationship information by a UE according to an embodiment of the present disclosure;

[0015] Figure 4 The illustration shows a flowchart of a method for determining preset spatial relationship information using a base station according to an embodiment of the present disclosure;

[0016] Figure 5 A block diagram of a node for wireless communication according to various aspects of this disclosure is explained. Detailed Implementation

[0017] The following description contains specific information relating to exemplary embodiments of the invention. The accompanying drawings and detailed descriptions are for illustrative purposes only. However, the invention is not limited to these exemplary embodiments. Other variations and implementations of the invention will be apparent to those skilled in the art. Unless otherwise stated, similar or corresponding components in the figures may be indicated by similar or corresponding reference numerals. Furthermore, the drawings and illustrations in this invention are generally not drawn to scale and are not intended to correspond to actual relative dimensions.

[0018] The following description contains specific information relating to exemplary embodiments of the invention. The accompanying drawings and detailed descriptions are for illustrative purposes only. However, the invention is not limited to these exemplary embodiments. Other variations and implementations of the invention will be apparent to those skilled in the art. Unless otherwise stated, similar or corresponding components in the figures may be indicated by similar or corresponding reference numerals. Furthermore, the drawings and illustrations in this invention are generally not drawn to scale and are not intended to correspond to actual relative dimensions.

[0019] For consistency and ease of understanding, similar features are identified by numbers in the example figures (although not shown in some examples). However, features in different embodiments may differ in other respects, and therefore should not be narrowly limited to what is shown in the figures.

[0020] The designations “one embodiment,” “an embodiment,” “an example embodiment,” “various embodiments,” “some embodiments,” “embodiments of the invention,” etc., may indicate that the described embodiment of the invention may include a specific feature, structure, or characteristic, but not every possible embodiment of the invention must include that specific feature, structure, or characteristic. Furthermore, the repeated use of “in one embodiment,” “in an example embodiment,” or “an embodiment” does not necessarily refer to the same embodiment, although this is possible. Moreover, any use of terms such as “embodiment” alongside “the invention” is not intended to imply that all embodiments of the invention must include the stated specific feature, structure, or characteristic, but should be understood as meaning that “at least some embodiments of the invention” include the stated specific feature, structure, or characteristic. The term “coupled” is defined as a connection, whether direct or indirect through intermediate components, and is not necessarily limited to physical connections. The term “comprising” in use means “including but not limited to”; it specifically refers to an open inclusion or membership in the said combination, group, series, and equivalents.

[0021] The term "and / or" in this document describes the relationship between related objects only, indicating that there are three possible relationships. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, and B exists alone. "A and / or B and / or C" can mean that at least one of A, B, and C exists. Additionally, the character " / " used in this document generally indicates an "or" relationship between the preceding and following related objects.

[0022] Furthermore, for the purpose of non-restrictive interpretation, specific details, such as functional entities, technologies, protocols, standards, etc., are described to provide an understanding of the technologies described. In other examples, detailed descriptions of well-known methods, technologies, systems, architectures, etc., are omitted to avoid obscuring the description with unnecessary details.

[0023] Those skilled in the art will readily recognize that any NW function or algorithm described herein can be implemented by hardware, software, or a combination of software and hardware. The described functions may correspond to modules that can be software, hardware, firmware, or any combination thereof. Software implementations may include calculator-executable instructions stored on a calculator-readable medium such as memory or other types of storage devices. For example, one or more microprocessors or general-purpose calculators with communication processing capabilities may be programmed with corresponding executable instructions to execute the described NW functions(one or more) or algorithms(one or more). The microprocessor or general-purpose calculator may be formed from an application-specific integrated circuit (ASIC), a programmable logic array, and / or using one or more digital signal processors (DSPs). Although some of the exemplary embodiments described in this specification refer to software installed and executed on calculator hardware, alternative exemplary embodiments implemented in firmware or hardware, or a combination of hardware and software, are also within the scope of this invention.

[0024] Calculator-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, optical disc read-only memory (CD-ROM), magnetic cassette, magnetic tape, disk storage, or any other equivalent medium capable of storing calculator-readable instructions.

[0025] A radio communication NW architecture (e.g., a Long Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, or an LTE-Advanced Pro (LTE-Pro) system) typically includes at least one base station (BS), at least one user equipment (UE), and one or more optional NW components providing 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) via a radio access NW (RAN) established by the BS.

[0026] It should be noted that, in this invention, the UE may include, but is not limited to, a mobile station, mobile terminal or device, or a user communication radio terminal. For example, the UE may be a portable wireless device, including but not limited to a mobile phone, tablet computer, wearable device, sensor, or 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 via an air interface.

[0027] A BS may include, but is not limited to, Node Bs (NBs) in Universal Mobile Telecommunications System (UMTS), Evolved Node Bs (eNBs) in LTE-A, Radio Network Controllers (RNCs) in UMTS, Base Station Controllers (BSCs) in Global System for Mobile Communications (GSM) / GSM EDGE Radio Access Networks (GERAN), Next-Generation eNBs (ng-eNBs) in E-UTRA BSs connected to 5GC, Next-Generation Node Bs (gNBs) in 5G Access Networks (5G-AN), and any other devices capable of controlling wireless communications and managing intra-cell radio resources. A BS can serve one or more UEs via a radio interface connected to an NW.

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

[0029] A BS can be operated to provide radio coverage to a specific geographic area using multiple cells included in the RAN. The BS can support cell operation. Each cell can be operated to provide service to at least one UE within its radio coverage area. More specifically, each cell (often referred to as a serving cell) can provide services to serve one or more UEs within its radio coverage area. (For example, each cell schedules downlink (DL) and optional UL resources to at least one UE within its radio coverage area for DL ​​and optional uplink (UL) packet transmission.) A BS can communicate with one or more UEs in a radio communication system through multiple cells. Cells can allocate sidelink (SL) resources to support Pro-Se services. Each cell may have coverage areas overlapping with other cells. In the case of multiple RAT dual connectivity (MR-DC), the primary cell of a Master Cell Group (MCG) or Secondary Cell Group (SCG) can be referred to as a Special Cell (SpCell). A Primary Cell (PCell) can refer to the SpCell of an MCG. A PSCell can refer to the SpCell of an SCG. An MCG is a group of serving cells associated with a Master Node (MN), including SpCells and one or more optional Secondary Cells (SCells). An SCG is a group of serving cells associated with a Secondary Node (SN), including SpCells. And one or more optional SCells.

[0030] As mentioned above, the NR frame structure is designed to support flexible configuration to accommodate various next-generation (e.g., 5G) communication requirements, such as eMBB, mMTC, and URLLC, while achieving high reliability, high data rates, and low latency. Orthogonal Frequency Division Multiplexing (OFDM) technology, agreed upon in the 3rd Generation Partnership Project (3GPP), can be used as the baseline for the NR waveform. Scalable OFDM parameters, such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP), can also be used. Furthermore, NR considers two coding schemes: (1) Low-Density Parity-Check (LDPC) codes and (2) Polar codes. Coding scheme adaptation can be configured based on channel conditions and / or service applications.

[0031] Furthermore, it is considered that the transmission time interval of a single NR frame should include at least DL transmission data, a protection period, and UL transmission data, wherein the various parts of the DL transmission data, the protection period, and the UL transmission data should also be configurable, for example, based on NR-based NW dynamics. Additionally, SL resources can be provided in the NR frame to support ProSe services.

[0032] NR systems can support beam management for, but are not limited to, high-frequency band (e.g., millimeter-wave band) communication. To address the higher path loss in high-frequency bands, beamforming techniques provide additional gain, but at the cost of reduced spatial coverage for signal transmission and reception. To compensate for the spatial coverage loss from beamforming, the beam is redirected in different directions using time-division multiplexing (TDM) so that after a certain period, the UE or gNB can still understand its environment with the required spatial coverage.

[0033] In NR, such as Release-15 (Rel-15), beam management is supported by the Transmission Configuration Indication (TCI) framework and spatial relationship information for DL ​​and UL. For DL, different types of Qusai-CoLocation (QCL) assumptions are indicated. Specifically, QCL-type D relates to the spatial reception characteristics that the UE can use to receive target RS or channels. In the UL direction, spatial transmission characteristics can be indicated to the UE via spatial relationship information provided on the NW side. The UE can then perform UL transmissions for UL channels and signals accordingly.

[0034] For UEs with beam correspondence, the DL beam management process, which may involve DL beam measurement and reporting, can provide sufficient information to select the appropriate UL beam for UL transmission. In this case, not only the UL beam scanning process but also the UL beam indication signaling can be eliminated. However, this UL operation mode has not yet been introduced in NR Rel-15, such as in the TS 38 series specifications based on version V15.6.0.

[0035] To preserve UL beam indication signaling for, for example, UL control channels (e.g., PUCCH), UL data channels (e.g., Physical UL Shared Channel (PUSCH)), or UL (Detection Reference Signal), at least for the beam-corresponding UE, it may be necessary to enable default spatial relationship information for the relevant UL channels / signals for the beam-corresponding UE based on DLQCL assumptions. In NR Rel-15 (e.g., Technical Specification (TS) 38.214 V15.5.0), the QCL assumptions for the demodulation RS (DM-RS) port of the Physical DL Shared Channel (PDSCH) of the serving cell can be used to determine the QCL parameters configured for the UE's CORESET based on the following. More specifically, the QCL assumptions for the DM-RS port of the serving cell's PDSCH can be determined according to the following text in Table 1:

[0036] Table 1

[0037] However, in order for the spatial relation information of PUCCH and / or SRS to conform to the QCL parameters of CORESET, at least one of the following dimensions (i) to (vi) may also be considered:

[0038] • (i) PUCCH resources can be grouped, and the predefined spatial relationship information of PUCCH can be determined based on PUCCH resource groups.

[0039] • (ii) DL CORESETs can be grouped, with one CORESET group corresponding to, for example, the same transmit-receive point (TRP). Preset spatial relationship information for PUCCH / SRS can determine that they correspond to different CORESET groups.

[0040] • (iii) SRS resource sets are configured to use: {codebook, nonCodebook, antennaSwitching} which may need to be distinguished.

[0041] • (iv) Path loss reference RSs for UL power control can be allocated to PUCCH and SRS resources in different ways. This part can be considered when determining preset spatial relationship information.

[0042] • (v) Periodic (P) / semi-persistent (SP) / aperiodic (AP) PUCCH transmissions can follow different behaviors to determine preset spatial relationship information.

[0043] • (vi) Preset spatial relationship information can distinguish between self-carrier scheduling and cross-carrier scheduling.

[0044] In addition, since the spatial relationship information of PUSCH can be implicitly or explicitly indicated by the spatial relationship information of PUCCH or SRS, the spatial relationship information of PUSCH can also be modified accordingly.

[0045] It should be understood that spatial relations can be conceptualized as spatial domain transmission filters or beams. Therefore, in this disclosure, the terms "spatial relations," "spatial domain transmission filters," and "beams" are used interchangeably.

[0046] 1. PUCCH's default spatial relationships

[0047] For PUCCH operation, at least one spatial relation (or “spatial domain transmission filter”) can be configured for the UE 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.

[0048] For each PUCCH resource, its corresponding spatial transmission filter can be selected from the spatial transmission filters configured for the UE, and transmitted via the BS.

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

[0050] like Figure 1 As shown, the UE can configure a list 108 of spatial relation information via RRC signaling from the BS. The spatial relation 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 operations. 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). See figure. (Refer to...) Figure 1 The UE may use / apply the spatial domain transmission filter indicated by PUCCH-SpatialRelationInfo IE#1 to transmit PUCCH resource 102, and use / apply the spatial domain transmission filter indicated by PUCCH-SpatialRelationInfo IE#3 to transmit PUCCH resource 104 and PUCCH resource 106.

[0051] In addition, each PUCCH-SpatialRelationInfo IE in the spatial relation information list can indicate the corresponding (DL) path loss reference RS resource (not shown). For example, each PUCCH-SpatialRelationInfo IE in the spatial relation information list may include (or be associated with) an indication of a path loss reference RS resource.

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

[0053] In one implementation, PUCCH resources can be used in a P / SP / AP manner. For example, P / SP PUCCH resources can be used for P / SP Channel State Information (CSI) reporting, while AP PUCCH resources can be used for hybrid Automatic Repeat Request (HARQ)-Acknowledgement (ACK) feedback transmission.

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

[0055] In one implementation, the UE can determine the spatial domain transmission filter for the PUCCH resource without explicit signaling from the BS. For example, when the UE cannot obtain the PUCCH-SpatialRelationInfo IE from NW signaling (e.g., signaling from the BS), the UE can apply a preset spatial domain transmission filter for the PUCCH resource.

[0056] In one implementation, the preset spatial domain transmission filter for each PUCCH resource allocated to the UE can be determined independently.

[0057] In one implementation, PUCCH resources can be grouped into one or more PUCCH resource groups. In this case, a preset spatial transmission filter can be determined independently for each PUCCH resource group.

[0058] In one implementation, PUCCH resource packets can be formed implicitly or explicitly based on NW signaling.

[0059] In one implementation, PUCCH resources associated with different UE panels can correspond to different PUCCH resource groups.

[0060] In one implementation, a PUCCH resource group is associated with a CORESET group. This association can be achieved through higher-level signaling (e.g., RRC signaling). For example, a higher-level index is configured for each CORESET where applicable. The higher-level index is associated with the PUCCH resource group based on RRC signaling.

[0061] In one implementation, a single preset spatial domain transmission filter can be used for the transmission of all PUCCH resources allocated to the UE.

[0062] In one implementation, the preset spatial domain transfer filter can be a preset TCI or QCL assumption for the PDSCH:

[0063] • When one or more CORESETs are configured on CC, the CORESET with the lowest ID in the most recently monitored downlink slots;

[0064] • When no CORESET is configured on CC, the lowest active TCI state with the ID applicable to PDSCH in the active DL-BWP of CC;

[0065] • When the PDSCH associated with the scheduling cell does not have an active TCI state.

[0066] □ In one example, the same spatial domain filter as the last PRACH transmission can be used as the preset spatial domain transmission filter. This method can be applied when there is no in-band CC that is neither configured with CORESET nor activated for PDSCH TCI.

[0067] □ In another example, the same spatial domain filter as the last PUSCH transport containing msg-3 can be used as the preset spatial domain transport filter. This method can be applied when there is no in-band CC that has neither CORESET configuration nor a TCI activated for PDSCH.

[0068] □ In yet another example, the preset spatial transmission filter may correspond to the preset TCI or QCL assumption of another in-band component carrier PDSCH, for example, as the first two “in case” items mentioned above in this section.

[0069] - In one embodiment, the in-band CC with the lowest index is selected.

[0070] - In one embodiment, the in-band CC with the lowest index having CORESET configuration is selected.

[0071] - In one embodiment, the in-band CC with the lowest index of the TCI for PDSCH activation is selected.

[0072] - In one embodiment, the in-band CC with the lowest index that has CORESET configuration or is PDSCH activated is selected.

[0073] In one implementation, the preset spatial domain transmission filter of the PUCCH resource can follow the QCL parameters of CORESET, where CORESET can be used for DL ​​PDCCH monitoring.

[0074] In one implementation, CORESET can be associated with a group of CORESETs.

[0075] In one implementation, a CORESET group can be associated with a TRP (transmit-receive point).

[0076] In one implementation, CORESET may or may not correspond to a DL CC paired with the ULCC where the PUCCH resource resides. For example, a transmission on the PUCCH resource may be triggered by a DCI, where the carrier indication field in the DCI may identify the UL CC.

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

[0078] In one implementation, a CORESET can be associated with the monitored search space that has the lowest CORESET-ID in the latest timeslot monitored by the UE for the associated CORESET group (including the CORESET). In one example, the associated CORESET group can include all configured CORESETs in the active BWP of the serving cell (or CC). In another example, a transport on the PUCCH resource can correspond to an instance of a P / SP PUCCH transport.

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

[0080] In one implementation, CORESET can be pre-configured / pre-defined. In one example, CORESET is pre-determined to have a higher or lower CORESET-ID index in the active DL BWP in CC.

[0081] In one implementation, the RS associated with QCL type D in the QCL parameters of CORESET can be used to determine a preset spatial domain transmission filter. In one implementation, the RS can be a path loss reference RS. For example, when the spatial domain transmission filter used for PUCCH transmission is not provided by NW signaling via PUCCH-SpatialRelationInfo IE, the path loss reference RS for UL power control used for PUCCH transmission can be determined as:

[0082] - The RS indicated by the CORESET QCL parameter (if there are multiple RSs indicated by the QCL parameter, you can choose the RS associated with QCL-type D); or - Pre-configured RS.

[0083] In one implementation, when the NW signaling does not provide a corresponding PUCCH-SpatialRelationInfo IE for a PUCCH resource, a preset spatial domain transmission filter is used to determine a transmission (or "PUCCH transmission") on the PUCCH resource, which may be associated with (or included in) a PUCCH resource group, wherein the PUCCH resource group may be associated with a CORESET group. In this case, the preset spatial domain transmission filter for transmission on the PUCCH resource may 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 PUCCH resource is used for P / SP transmission, then the CORESET group is monitored by the UE. In one implementation, the preset spatial domain transmission filter for transmission on the PUCCH resource may be determined based on the QCL parameter of the CORESET associated with the search space where a DCI triggering the transmission on the PUCCH resource is received, if the PUCCH resource is used for AP transmission.

[0084] 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 a preset spatial domain transmission filter for the PUCCH resource. In one example, for power control of transmissions on the PUCCH resource, the path loss reference RS can be used as a preset spatial domain transmission filter.

[0085] 2. SRS Preset Spatial Relationships

[0086] The use of SRS resource sets can be configured as one of {beam management, codebook, noncodebook, antenna switching} as specified in the 3GPP NR specification (e.g., TS 38.331 V15.5.0). Each SRS resource can be RRC configured by a BS with an SRS-SpatialRelationInfo IE to determine its spatial domain transmission filter for UL transmission. For each SRS resource set, a (DL) path loss reference RS resource (e.g., indicated by an IE denoted as pathlossReferenceRS) can be provided to estimate the DL path loss for UL SRS power control purposes.

[0087] Figure 2 The illustration shows multiple SRS resource sets, each configured with a (DL) path loss reference RS resource, according to an embodiment of the present disclosure.

[0088] As shown in the figure. Figure 2 As shown, several SRS resource sets (e.g., including SRS resource set 210 and SRS resource set 220) can be provided (or configured) to the UE. Each SRS resource set can be associated with (or include) one or more SRS resources. For example, SRS resource set 210 may include M SRS resources (e.g., SRS resource #1 212, SRS resource #2 214, and SRS resource #2 216), and SRS resource set 220 may 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 the SRS resource set can be configured with a spatial domain transmission filter (e.g., indicated by an SRS-SpatialRelationInfo IE). For example, if a corresponding SRS-SpatialRelationInfo IE is provided, the SRS resource can be transmitted based on the spatial domain transmission filter indicated by the corresponding SRS-SpatialRelationInfo IE.

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

[0090] 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 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.

[0091] 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" can be referred to as an "SRS codebook resource," an SRS resource whose associated SRS resource set is configured for use as a "nonCodebook" can be referred to as an "SRS-nonCodebook resource," and an SRS resource whose associated SRS resource set is configured for use as an "antennaSwitching" can be referred to as an "SRS-antennaSwitching resource." For example, if using... Figure 2 The SRS resource set 210 is shown. Figure 2 SRS resource set 210 is configured as "non-codebook", and SRS resources 212, 214 and 216 associated with (or included in) SRS resource set 210 are SRS-non-codebook resources.

[0092] 2.1 SRS - Non-Codebook Resources

[0093] 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 resources 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.

[0094] In one implementation, a spatial domain transmission filter for SRS-non-codebook resources can be determined without explicit NW signaling. For example, when the associated CSI-RS IE and SRS-SpatialRelationInfo IE cannot be obtained from NW signaling, the UE can apply a preset spatial domain transmission filter.

[0095] In one implementation, the preset spatial domain transmission filter for each SRS-noncodebook resource allocated to the UE can be determined independently.

[0096] In one implementation, the SRS-nonCodebook resources allocated to the UE can be grouped into one or more SRS-nonCodebook resource sets (e.g., Figure 2 (SRS resource sets 210 and 220 shown). In this case, a preset spatial domain transmission filter can be determined for the 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.

[0097] In one implementation, the preset spatial domain transfer filter can be a preset TCI or QCL assumption of the PDSCH:

[0098] • When one or more CORESETs are configured on CC, the CORESET with the lowest ID in the most recently monitored downlink slots;

[0099] • When no CORESET is configured on CC, the lowest active TCI state with the ID applicable to PDSCH in the active DL-BWP of CC;

[0100] • When the PDSCH associated with the scheduling cell does not have an active TCI state.

[0101] □ In one example, the same spatial domain filter as the last PRACH transmission can be used as the preset spatial domain transmission filter. This method can be applied when there is no in-band CC that is neither configured with CORESET nor activated for PDSCH TCI.

[0102] □ In another example, the same spatial domain filter as the last PUSCH transport containing msg-3 can be used as the preset spatial domain transport filter. This method can be applied when there is no in-band CC that has neither CORESET configuration nor a TCI activated for PDSCH.

[0103] □ In yet another example, the preset spatial transmission filter may correspond to the preset TCI or QCL assumption of another in-band component carrier PDSCH, for example, as the first two “in case” items mentioned above in this section.

[0104] - In one embodiment, the in-band CC with the lowest index is selected.

[0105] - In one embodiment, the in-band CC with the lowest index having CORESET configuration is selected.

[0106] - In one embodiment, the in-band CC with the lowest index of the TCI for PDSCH activation is selected.

[0107] - In one embodiment, the in-band CC with the lowest index that has CORESET configuration or is PDSCH activated is selected.

[0108] In one implementation, the preset spatial domain transfer filter for SRS-noncodebook resources may follow the QCL parameters of CORESET, where CORESET is used for DL ​​PDCCH monitoring.

[0109] In one implementation, CORESET can be associated with a group of CORESETs.

[0110] In one implementation, the CORESET group can be associated with the TRP.

[0111] In one implementation, CORESET may or may not correspond to a DL CC paired with the UL CC containing the SRS-nonCodebook resource. For example, a transmission on an SRS-nonCodebook resource may be triggered by a DCI, where the carrier indication field in the DCI may identify the UL CC.

[0112] In one implementation, SRS-nonCodebook resources can be associated with CORESET by NW via implicit / explicit signaling. For example, a set of SRS-nonCodebook resources associated with (or including) SRS-nonCodebook resources can be mapped to a group of CORESETs associated with (or including) CORESETs via NW signaling.

[0113] In one implementation, a CORESET can be associated with the monitored search space that has the lowest CORESET-ID in the latest time slot monitored by the UE, where the associated CORESET group (e.g., including CORESETs) is monitored. In one example, the associated CORESET group can include all configured CORESETs in the DL active BWP of the serving cell (or CC). In one example, a transport on an SRS-non-codebook resource can correspond to an instance of a P / SP SRS transport.

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

[0115] In one implementation, the CORESET can be pre-configured / pre-ordered. In one example, the CORESET can be pre-ordered / pre-configured to be the one with the highest or lowest CORESET-ID among the active DL BWPs in the CC.

[0116] In one implementation, if the UE is provided with a PathlossReferenceRS IE, the preset spatial domain transmission filter may follow the QCL parameters of the PathlossReferenceRS IE configured for the associated SRS-nonCodebook resource set.

[0117] In one implementation, the RS associated with the QCL type D in the QCL parameters of CORESET can be used to determine a preset spatial domain transmission filter.

[0118] In one implementation, the preset spatial domain transmission filter for the SRS-nonCodebook resource can follow the active UL BWP of the serving cell where the SRS-nonCodebook resource resides, having the lowest PUCCH resource ID (e.g., PUCCH-ResourceId). The PUCCH resource with the lowest PUCCH-ResourceId can be selected from the PUCCH resources for which spatial relationship information is activated by MAC-CE signaling.

[0119] In one implementation, when the path loss reference RS IE is not provided by NW signaling for the associated SRS-noncodebook resource set (e.g., in...), Figure 2 In the case that the SRS resource set 210 shown is not configured with a path loss reference RS (resource #1 218), the path loss reference RS for UL power control of SRS-nonCodebook resource transmission can be determined as:

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

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

[0122] - Pre-configured RS.

[0123] In one implementation, the preset spatial domain transmission filter for transmission on SRS-nonCodebook resources, determined by NW signaling when the SRS-SpatialRelationInfo IE corresponding to the SRS-nonCodebook and the associated CSI-RS IE corresponding to the SRS-nonCodebook are not present, 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 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 the DCI triggering transmission on the SRS-nonCodebook resources is received.

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

[0125] In one implementation, for power control of transmissions on SRS-nonCodebook resources, when the UE is not configured with a path loss reference RS for the corresponding SRS-nonCodebook resource set (e.g., when the UE is not configured with a PathlossReferenceRS IE for the corresponding SRS-nonCodebook resource set), the path loss reference RS can be determined as a preset spatial transmission filter for the corresponding SRS-nonCodebook resource.

[0126] 2.2 SRS-Codebook Resources and SRS-Antenna Switching Resources

[0127] In one implementation, one or two SRS codebook resources can be configured in the corresponding resource set. The UE can determine the spatial domain transmission filter for the SRS codebook resource and the SRS antenna switching resource without explicit NW indication. Alternatively, for example, when the UE cannot obtain the SRS-SpatialRelationInfo IE from the NW signaling, a preset spatial domain transmission filter can be applied. In the following text, for ease of explanation, the SRS resource, which is an SRS-codebook resource or an SRS-antennaSwitching resource, can be referred to as the "SRS-ac resource".

[0128] In one implementation, the preset spatial domain transmission filter for each SRS-ac resource allocated to the UE can be determined independently.

[0129] In one implementation, the preset spatial domain transmission filter can be configured by the BS based on the SRS-ac resource set.

[0130] In one implementation, if a subset of SRS-ac resources in the SRS-ac resource set is not configured with SRS-SpatialRelationInfo IE, the default spatial domain transfer filter can be applied to the subset of SRS-ac resources.

[0131] In one implementation, the method for determining the preset spatial domain transmission filter may be applicable only when each SRS-ac resource in the SRS-ac resource set is not configured with an SRS-SpatialRelationInfo IE.

[0132] In one implementation, the SRS-ac resource set can be associated with the UE panel.

[0133] In one implementation, the preset spatial domain transfer filter can be a preset TCI or QCL assumption for the PDSCH:

[0134] • When one or more CORESETs are configured on CC, the CORESET with the lowest ID in the most recently monitored downlink slots;

[0135] • When no CORESET is configured on CC, the lowest active TCI state with the ID applicable to PDSCH in the active DL-BWP of CC;

[0136] • When the PDSCH associated with the scheduling cell does not have an active TCI state.

[0137] □ In one example, the same spatial domain filter as the last PRACH transmission can be used as the preset spatial domain transmission filter. This method can be applied when there is no in-band CC that is neither configured with CORESET nor activated for PDSCH TCI.

[0138] □ In another example, the same spatial domain filter as the last PUSCH transport containing msg-3 can be used as the preset spatial domain transport filter. This method can be applied when there is no in-band CC that has neither CORESET configuration nor a TCI activated for PDSCH.

[0139] □ In yet another example, the preset spatial transmission filter may correspond to the preset TCI or QCL assumption of another in-band component carrier PDSCH, for example, as the first two “in case” items mentioned above in this section.

[0140] - In one embodiment, the in-band CC with the lowest index is selected.

[0141] - In one embodiment, the in-band CC with the lowest index having CORESET configuration is selected.

[0142] - In one embodiment, the in-band CC with the lowest index of the TCI for PDSCH activation is selected.

[0143] - In one embodiment, the in-band CC with the lowest index that has CORESET configuration or is PDSCH activated is selected.

[0144] In one implementation, the preset spatial domain transfer filter of the SRS-ac resource can follow the QCL parameters of CORESET for DLPDCCH monitoring.

[0145] In one implementation, CORESET can be associated with a group of CORESETs.

[0146] In one implementation, the CORESET group can be associated with the TRP.

[0147] In one implementation, CORESET may or may not correspond to a DL CC paired with the UL CC where the SRS-ac resource resides. For example, a transmission on the SRS-ac resource may be triggered by a DCI, where the carrier indication field in the DCI may identify the UL CC.

[0148] In one implementation, SRS-ac resources can be associated with CORESET by NW via implicit or explicit signaling. For example, a set of SRS-ac resources associated with (or including) SRS-ac resources can be mapped to a group of CORESETs associated with (or including) CORESETs via NW signaling.

[0149] In one implementation, a CORESET can be associated with the monitored search space that has the lowest CORESET-ID in the latest time slot monitored by the UE among the associated CORESET groups (including CORESETs).

[0150] In one implementation, the associated CORESET group may include all configured CORESETs in the DL active BWP of the serving cell (or CC).

[0151] In one implementation, a transport on an SRS-ac resource can correspond to an instance of a P / SP SRS transport.

[0152] In one implementation, CORESET can be associated with the search space of the DCI that receives the triggering transmission on the SRS-ac resource.

[0153] In one implementation, the transmission on SRS-ac resource transport can correspond to AP SRS transport.

[0154] In one implementation, the CORESET can be pre-configured / reserved. In one example, the CORESET is reserved for the one with the higher or lower CORESET-ID index in the active DL BWP in CC.

[0155] In one implementation, the preset spatial domain transmission filter of the SRS-ac resource may follow the QCL parameters of the PathlossReferenceRS IE of the associated SRS-noncodebook resource set (including the SRS-ac resource), if the UE is configured with a PathlossReferenceRS IE.

[0156] In one implementation, the RS associated with the QCL type D in the QCL parameters can be used as a preset spatial domain transmission filter for the SRS-ac resource.

[0157] In one implementation, the preset spatial domain transmission filter of the SRS-ac resource can follow the spatial domain transmission filter of the PUCCH resource with the lowest PUCCH-ResourceId in the activity (e.g., determined by PUCCH-SpatialRelationInfo IE) of the UL BWP of the serving cell where the SRS-ac resource is located.

[0158] In one implementation, when the NW signaling does not provide a PathlossReferenceRS IE for the associated SRS-ac resource set, the path loss reference RS for UL power control used for SRS-ac resource transmission can be determined as follows:

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

[0160] - Pre-configured RS.

[0161] In one implementation, when NW signaling does not provide an SRS-SpatialRelationInfo IE corresponding to the SRS-ac resource, the SRS-ac resource set (including the SRS-ac resource) may be associated with a CORESET group to determine the preset spatial domain transmission filter for transmission on the SRS-ac resource. In this case, the preset spatial domain transmission filter for transmission on the SRS-ac 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 most recent time slot. If the SRS-nonCodebook resource is used for P / SP transmission, the UE monitors the CORESET group. In one implementation, the preset spatial domain transmission filter for 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 triggers transmission on the SRS-nonCodebook resource. If the SRS-ac resource is used for AP transmission, the SRS-ac resource is received.

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

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

[0164] 3. Preset Spatial Relationships in PUSCH

[0165] For PUSCH scheduling based on DCI format 0_0 for Rel-15 NR as specified in the TS 38 series specifications (e.g., TS 38.213 V15.6.0 and TS 38.214 V15.6.0), the spatial relation information for PUSCH transmission is not explicitly indicated in the scheduling DCI. Instead, the UE transmits PUSCH based on spatial relations (if applicable) corresponding to the dedicated PUCCH resource with the lowest ID within the cell's active UL BWP, as described in 9.2.1 TS 38.213, e.g., V15.6.0. For this reason, in RRC connection mode, the UE does not expect PUSCH scheduled by DCI format 0_0 in the BWP without configuring PUCCH-SpatialRelationInfo for PUCCH resources in frequency range 2 (FR2). This may apply to frequency ranges above frequency range 1 (FR1), but not to frequency range 2.

[0166] For PUSCH scheduling based on DCI format 0_1 ​​using Rel-15 NR as specified in the TS 38 series specifications (e.g., TS 38.213 V15.6.0 and TS 38.214 V15.6.0), the spatial relation information used for PUSCH transmission is explicitly indicated in the scheduling DCI. Specifically, the DCI field "SRS Resource Indicator" can provide the spatial relation information for the scheduled PUSCH.

[0167] 3.1 Preset Spatial Relationship of PUSCH for DCI Format 0_0 Scheduling

[0168] In the various implementations described in this section, the UE may be configured with one or more PUCCH resources, but none of the configured PUCCH resources are provided with any corresponding PUCCH-SpatialRelationInfo. When spatial relationships are determined by referencing PUCCH resources, but no PUCCH-SpatialRelationInfo IE is assigned to the PUCCH resources, this section discloses the preset spatial relationships for PUSCHs scheduled in DCI format 0_0. In a preferred example, the preset spatial relationships for PUCCHs described in this section or Section 1 may be applied. For example, the preset spatial relationships may be preset TCI or QCL assumptions for the serving cell's (CC) PDSCH:

[0169] • When CORESET is configured on CC, CORESET is associated with the monitoring search space with the lowest CORESET ID in the most recently monitored downlink slot within the active BWP of CC;

[0170] • When no CORESET is configured on the CC, the active TCI state with the lowest ID applies to the PDSCH in the active DL-BWP of the CC.

[0171] In some implementations, there may be situations where no active TCI state is available within a CC, and therefore no "active TCI state" can be referenced. For example, this may happen after the initial access procedure, before a TCI state configuration or TCI state activation MAC-CE command has been received. This situation may also occur after handover. It may also be possible that in dual-connectivity or carrier aggregation scenarios, one or more CCs do not provide a CORESET or TCI state configuration. In these cases, the preset spatial relationships of SRS or PUCCH (and therefore also applicable to PUSCHs scheduled by 0_0) can be determined as follows:

[0172] • The same spatial domain filter as the last PRACH transmission can be used as the preset spatial relation.

[0173] □ In one example, the last PRACH may come from the same CC.

[0174] In another example, the last PRACH might come from SpCell.

[0175] □ In yet another example, the last PRACH may come from an in-band CC.

[0176] • The same spatial domain filter as the last PUSCH transmission containing msg-3 can be used as the preset spatial relation.

[0177] □ In one example, the last msg-3 PUSCH may come from the same CC.

[0178] □ In another example, the last msg-3 PUSCH may come from SpCell.

[0179] □ In yet another example, the last msg-3 PUSCH may come from an in-band CC.

[0180] • The preset spatial relationship can correspond to the preset TCI or QCL assumption of another in-band component carrier (CC) PDSCH.

[0181] □ In one example, select the lowest index-band CC with CORESET(s) configuration.

[0182] □ In another example, select the lowest index-band CC with CORESET(s) configuration or TCI activated for PDSCH.

[0183] In various embodiments of this disclosure, the preset spatial relation is subject to the UE's capabilities and / or the base station's signaling (e.g., gNB signaling). The UE capabilities at least indicate NR Rel-16 compliant UEs, as specified in the 3GPP TR 38 series of specifications. This capability may further indicate support for preset spatial relations for PUCCH and / or SRS. This capability may also indicate support for preset spatial relations for PUSCH scheduled by, for example, DCI format 0_0. This capability can simply indicate support for preset spatial relations, and it can be applied to both PUCCH and SRS and PUSCH. In this sense, older Rel-15 compliant UEs may not expect DCI format 0_0 scheduling for PUSCH transmissions when no PUCCH-SpatialRelationInfo IE is allocated for PUCCH resources.

[0184] If no PUCCH-SpatialRelationInfo IE is allocated for the PUCCH resource, the following characteristics are summarized to determine the spatial relation information of the PUSCH scheduled by DCI format 0_0:

[0185] – In one implementation, the UE applies a preset spatial relationship used for PUCCH transmission to PUSCH transmission.

[0186] □ The application of preset spatial relationships may be subject to UE capabilities and / or gNB signaling.

[0187] • A UE capability at least indicates that it is an NR Rel-16 compliant UE. In one implementation, this capability may further indicate support for preset spatial relationships of PUCCH and / or SRS. In another implementation, this capability may further indicate support for preset spatial relationships of PUSCH.

[0188] • For UEs compatible with the legacy Rel-15, default spatial relationships are not expected to be applied. When no PUCCH-SpatialRelationInfo IE is allocated for PUCCH resources, Rel-15 UEs are not expected to be scheduled for PUSCH transmissions in DCI format 0_0. □ Default spatial relationships can be derived based on the methods described in Section 1.

[0189] – In one embodiment, when no PUCCH-SpatialRelationInfo IE is allocated for PUCCH resources, the UE does not expect to be scheduled for PUSCH transmission using DCI format 0_0.

[0190] Figure 3 The illustration shows a flowchart of a method 300 performed by a UE for determining preset spatial relationship information according to an embodiment of the present disclosure.

[0191] In action 302, the UE may indicate to the cell (e.g., via RRC signaling) the UE's ability to support preset spatial relationship behaviors of PUCCH transmission or SRS.

[0192] In action 304, the UE may indicate to the cell (e.g., via RRC signaling) the UE's ability to support the preset spatial relationship behavior of PUSCH.

[0193] In action 306, the UE can receive configuration signaling from the cell, which configures one or more PUCCH resources on the active UL BWP for the UE. In this embodiment, one or more PUCCH resources are not configured with beam information. For example, PUCCH-SpatialRelationInfo is not indicated in the configuration signaling from the cell. Additionally, the configuration signaling indicates to the UE that a preset spatial relation behavior for PUSCH transmissions scheduled by DCI format 0_0 is enabled.

[0194] In action 308, the UE can receive DCI format 0_0 from the active DL BWP of the cell. DCI format 0_0 provides scheduling information for PUSCH.

[0195] In action 310, the UE can send a PUSCH to the base station according to a preset spatial relationship behavior. When the preset spatial relationship behavior is enabled by the cell, the preset spatial relationship behavior determines the spatial relationship by referring to the QCL-TypeD reference signal corresponding to the QCL assumption of the predetermined CORESET on the cell's active DL BWP. In one implementation, the predetermined CORESET is configured with the lowest ID on the cell's active DL BWP. In one implementation, the predetermined CORESET is the same as the preset spatial relationship setting applied to PUCCH transmissions from the UE if at least one of the following conditions is met: (i) the UE reports beam correspondence capability to the cell; (ii) the preset spatial relationship setting for PUCCH transmissions is enabled by the cell.

[0196] Figure 4 The illustration shows a flowchart of a method 400 for determining preset spatial relationship information using a base station according to an embodiment of the present disclosure.

[0197] In action 402, the base station may receive (e.g., via RRC signaling) an indication of the UE’s ability to support PUCCH transmission or SRS preset spatial relationship behavior from the UE.

[0198] In action 404, the base station may receive from the UE (e.g., via RRC signaling) an indication of the UE's ability to support preset spatial relational behaviors of PUSCH.

[0199] In action 406, the base station may send configuration signaling to the UE, which configures one or more PUCCH resources for the UE on the active UL BWP. In this embodiment, the one or more PUCCH resources are not configured with beam information. For example, PUCCH-SpatialRelationInfo is not indicated in the configuration signaling from the cell. Additionally, the configuration signaling indicates to the UE that a preset spatial relation behavior for PUSCH transmissions scheduled by DCI format 0_0 is enabled.

[0200] In action 408, the base station can send DCI format 0_0 to the UE on the active downlink (DL) BWP. DCI format 0_0 provides scheduling information for PUSCH.

[0201] In action 410, the base station can receive PUSCH from the UE according to a preset spatial relationship behavior. When the preset spatial relationship behavior is enabled by the cell, the preset spatial relationship behavior determines the spatial relationship by referring to the QCL-TypeD reference signal corresponding to the QCL assumption of the predetermined CORESET on the cell's active DL BWP. In one implementation, the predetermined CORESET is configured with the lowest ID on the cell's active DL BWP. In one implementation, the predetermined CORESET is the same as the preset spatial relationship setting for PUCCH transmission from the UE if at least one of the following conditions is met: (1) the UE reports beam correspondence capability to the cell; (2) the preset spatial relationship setting for PUCCH transmission is enabled by the cell.

[0202] 3.2 Preset Spatial Relationship of PUSCH in DCI Format 0_1 ​​Scheduling

[0203] For DCI format 0_1 ​​scheduling of PUSCH, spatial relation information is provided through an SRS with an srs-SpatialRelationInfo configuration (e.g., in the “SRS Resource Indicator (SRI)” field). The resource set of the SRS used for SRI indication is configured as “codebook” or “nonCodebook”. In one example, an SRS with an “antennaSwitching” configuration also applies. When the SRS for SRI indication is not configured with srs-SpatialRelationInfo, the following characteristics are summarized to determine the default spatial relation information for PUSCH scheduling in DCI format 0_1:

[0204] – In one implementation, the UE can ignore the indication in the SRI field.

[0205] □ The UE applies the preset spatial relationships used for PUCCH transmission to PUSCH transmission. The preset spatial relationships can be determined according to the method described in Section 1.

[0206] • This method can be applied when there is no dedicated PUCCH resource allocation with PUCCH-SpatialRelationinfo.

[0207] □ The UE applies spatial relationships to the dedicated PUCCH resource with the lowest PUCCH resource ID in the cell's active UL BWP.

[0208] • This method can be applied when a dedicated PUCCH resource configured with PUCCH-SpatialRelationInfo exists.

[0209] – In one implementation, the UE applies a preset spatial relationship to the indicated SRS to the PUSCH transmission. The preset spatial relationship can be determined according to the method described in Section 2.

[0210] □ SRS default spatial relationships are associated with the use of "codebook" or "nonCodebook".

[0211] In various embodiments of this disclosure, methods for determining preset spatial relationships for PUCCH / SRS / PUSCH transmissions are discussed. For PUCCH preset spatial relationships, it is assumed that no PUCCH-SpatialRelationInfo is provided for PUCCH resources. For SRS preset spatial relationships, it is assumed that no srs-SpatialRelationInfo is provided. For preset spatial relationships of PUSCH associated with DCI format 0_0, it is assumed that no PUCCH-SpatialRelationInfo is provided. For preset spatial relationships of PUSCH associated with DCI format 0_1, it is assumed that no srs-SpatialRelationInfo is provided.

[0212] The determination of the preset special relationship for PUCCH and SRS addresses the situation where the TCI state is not activated and / or during multiple CC operations. In this case, the preset spatial relationship can be derived based on the CORESET of the in-band CC or the activated TCI state.

[0213] For PUSCHs associated with DCI 0_0, preset spatial relationship information can be derived from PUCCH preset spatial relationships. Such applications may be subject to UE capability signaling.

[0214] For PUSCH associated with DCI 0_1, depending on whether PUCCH-SpatialRelationInfo is provided, the preset spatial relationship information can be derived from the PUCCH preset spatial relationship or from the SRS preset spatial relationship.

[0215] In one implementation, the UE can send a UE capability message to the BS indicating that the UE supports the corresponding beam. If the UE supports the beam correspondence, it may mean that the UE has the capability, for example, to select an appropriate beam for UL transmission based on DL measurements, regardless of whether UL beam scanning is relied upon.

[0216] The following provides a non-restrictive description of certain terms.

[0217] Beam Failure Recovery: Movement or other events in the environment may cause the currently established beam pair to fail due to insufficient time for beam reporting mechanisms (which can occur on the physical (PHY) channel, similar to CSI reporting mechanisms). Beam failure recovery procedures can be used to handle such events with a shorter response time.

[0218] Beam: The term "beam" here may be replaced by "spatial domain transmission filter." For example, when a UE reports a preferred gNB Tx beam, the UE is essentially selecting the spatial filter used by the gNB. The term "beam information" can be used to provide information about which beam / spatial domain transmission filter is being used / selected. In one implementation, separate RS can be transmitted by applying separate beams (spatial domain transmission filters). Therefore, in some embodiments of this disclosure, the term "beam" or "beam information" may be represented by an RS resource index.

[0219] HARQ: This function ensures delivery between peer entities at Layer 1 (e.g., the PHY layer). When the PHY layer is not configured with DL / UL spatial multiplexing, a single HARQ process can support one transport block (TB). When the PHY layer is configured with DL / UL spatial multiplexing, a single HARQ process can support one or more TBs. In one implementation, each serving cell can have one HARQ entity. Each HARQ entity can support a number of parallel DL and UL HARQ processes.

[0220] Timers: A MAC entity can set one or more timers for individual purposes, such as triggering some UL signaling retransmissions or limiting some UL signaling retransmission cycles. Once started, a timer will run until it stops or expires; otherwise, it does not run. If a timer is not running, it can be started; if it is running, it can be restarted. Timers always start or restart from their initial value. The initial value can be configured by the BS (e.g., gNB) via DL RRC signaling, but is not limited to.

[0221] BWP: A subset of the total cell bandwidth is called a BWP. Bandwidth adaptation can be achieved by configuring a BWP for the UE and informing the UE which of the configured BWPs is currently active. To enable Bandwidth Adaptive (BA) on a PCell, the gNB can configure both a UL and DL BWP for the UE. To enable BA on a SCell in the case of Carrier Aggregation (CA), the gNB can configure at least a DL BWP for the UE (e.g., there may not be one in the UL). For a PCell, the initial BWP can be the BWP used for initial access. For a SCell, the initial BWP can be the BWP configured for the UE to operate first when the SCell is activated. The UE can be configured with a first active UL BWP by the firstActiveUplinkBWP IE. If a first active UL BWP is configured for the SCell, the firstActiveUplinkBWP IE field can contain the ID of the UL BWP to be activated when the UE performs the RRC (re)configuration procedure. If this field is not present, the RRC (re)configuration procedure may not force a BWP handover. If a first active UL BWP is configured for SCell, the firstActiveUplinkBWP IE field can contain the ID of the UL BWP to be used when SCell is MAC activated.

[0222] QCL: If the properties of the channel transmitting symbols at one antenna port can be inferred from the properties of the channel transmitting symbols at the other antenna port, then the two antenna ports are quasi-co-located. The aforementioned "channel properties" can include at least one of Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameters. These properties can be categorized into different QCL types in NR TS. For example, QCL-type D refers to the spatial Rx parameter. QCL type D can be referred to as a "beam".

[0223] TCI Status: The TCI status can contain parameters used to configure the QCL relationship between one or two DL RSs and a target RS set. For example, the target RS set can be the DM-RS ports of a PDSCH or PDCCH.

[0224] Normal Scheduling Request (SR): A normal SR can be used to request UL Shared Channel (UL-SCH) resources (e.g., PUSCH resources) for a new transmission. A UE can be configured with zero, one, or more normal SR configurations. A normal SR configuration can include a set of PUCCH resources for SRs across different BWPs and cells. For a logical channel, each BWP can be configured with at most one PUCCH resource for SR. Each normal SR configuration can correspond to one or more logical channels. Each logical channel can map to zero or one normal SR configuration. The normal SR configuration of the logical channel that triggers a Buffer Status Report (BSR) procedure (if a BSR procedure configuration exists) can be considered the normal SR configuration corresponding to the triggered SR procedure. When a normal SR procedure is triggered, the normal SR procedure can be considered pending until it is canceled.

[0225] Beam correspondence: Beam correspondence is the ability of a UE to select an appropriate beam for UL transmission based on DL measurements, with or without relying on UL beam scanning. Alternatively, beam correspondence may be referred to as the ability to indicate the appropriate beam for DL ​​reception to the UE based on the UL beam scanning procedure.

[0226] Figure 5 A block diagram of a node 500 for wireless communication according to various aspects of this disclosure is explained. As shown in the figure. Figure 5 As shown, node 500 may include a transceiver 506, a processor 508, a memory 502, one or more presentation components 504, and at least one antenna 510. Node 500 may also include a radio frequency (RF) band module, a BS communication module, an NW communication module and a system communication management module, input / output (I / O) ports, I / O components, and a power supply. Figure 5 (Not explicitly shown). Each of these components can communicate directly or indirectly with each other via one or more buses 524. In one implementation, node 500 can be a UE or BS performing the various functions described herein, for example, referring to Figures 1 to 4.

[0227] A transceiver 506, having a transmitter 516 (e.g., transmit / transmit circuitry) and a receiver 518 (e.g., receive / receive circuitry), can be configured to transmit and / or receive time and / or frequency resource allocation information. In one embodiment, the transceiver 506 can be configured to transmit in different types of subframes and time slots, including but not limited to available, unavailable, and flexibly available subframe and time slot formats. The transceiver 506 can be configured to receive data and control channels.

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

[0229] Calculator 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. Calculator storage media does not include transmitted data signals. Communication media typically embody calculator-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 calculator-readable media.

[0230] Memory 502 may include a calculator storage medium in the form of volatile and / or non-volatile memory. Memory 502 may be removable, non-removable, or a combination thereof. For example, memory 502 may include solid-state memory, hard disk drive, optical disk drive, etc. Figure 5 As shown, memory 502 may store calculator-readable and / or executable instructions 514 (e.g., software code) that, when executed, cause processor 508 to perform various functions described herein, such as references. Figure 1 and Figure 5 . refer to Figures 1 to 4 Alternatively, instruction 514 may not be executed directly by processor 508, but may be configured to cause node 500 (e.g., when compiled and executed) to perform the various functions described herein.

[0231] Processor 508 (e.g., having processing circuitry) may include intelligent hardware devices, central processing units (CPUs), microcontrollers, ASICs, etc. Processor 508 may include memory. Processor 508 can process data 512 and instructions 514 received from memory 502, as well as information transmitted via transceiver 506, baseband communication module, and / or NW communication module. Processor 508 can also process information to be transmitted to transceiver 506 for transmission via antenna 510, or to NW communication module for transmission to the CN.

[0232] One or more presentation components 504 can present data indications to a person or other device. Examples of presentation components 504 may include display devices, speakers, printing components, vibration components, etc.

[0233] As will be apparent from the above description, various techniques can be used to implement the concepts without departing from the scope of the concepts described herein. Furthermore, although these concepts have been specifically described with reference to certain embodiments, those skilled in the art will recognize that changes in form and detail can be made without departing from the scope of those concepts. Therefore, the described embodiments are to be considered illustrative rather than restrictive in all respects. It should also be understood that this application is not limited to the specific embodiments described above, and many rearrangements, modifications, and substitutions are possible without departing from the scope of the invention.

Claims

1. A user equipment, the user equipment comprising: transceiver; One or more non-transient calculator-readable media having calculator-executable instructions embedded thereon; as well as At least one processor, coupled to the transceiver and the one or more non-transient calculator-readable media, is configured to execute calculator-executable instructions to cause the user equipment to: The transceiver receives configuration signaling from the cell, which configures one or more physical uplink control channels for the user equipment. The one or more physical uplink control channels are not configured with physical uplink control channel spatial relationship information, and the configuration signaling indicates that the cell has enabled a preset spatial relationship behavior for physical uplink control channel transmission. and In response to the preset spatial relationship behavior of enabling physical uplink control channel transmission in the user equipment, the transceiver transmits the physical uplink control channel according to the spatial relationship corresponding to the quasi-co-location type D reference signal, which corresponds to the quasi-co-location assumption of a predetermined control resource set on the active downlink bandwidth portion of the cell.

2. The user equipment according to claim 1, wherein the preset spatial relationship behavior is further related to the transmit power of the physical uplink control channel.

3. The user equipment of claim 1, wherein the calculator is executable to cause the user equipment to: The transceiver transmits to the cell the user equipment's ability to support the preset spatial relationship behavior of the physical uplink shared channel.

4. The user equipment according to claim 1, wherein the predetermined control resource set is a control resource set configured with the lowest identifier on the active downlink bandwidth portion of the cell.

5. The user equipment of claim 1, wherein the calculator is executable to cause the user equipment to: The ability to instruct the user equipment to support the preset spatial relationship behavior of the probe reference signal to the cell.

6. A method performed by a user equipment, the method comprising: The configuration signaling is received from the cell, which configures one or more physical uplink control channels for the user equipment on the active uplink bandwidth portion, wherein the one or more physical uplink control channels are not configured with physical uplink control channel spatial relationship information, and the configuration signaling indicates that the cell has enabled the preset spatial relationship behavior of physical uplink control channel transmission. and In response to the preset spatial relationship behavior that enables the transmission of the physical uplink control channel in the user equipment, the physical uplink control channel is transmitted according to the spatial relationship corresponding to the quasi-co-location type D reference signal, which corresponds to the quasi-co-location assumption of a predetermined control resource set on the active downlink bandwidth portion of the cell.

7. The method according to claim 6, wherein the preset spatial relationship behavior is further related to the transmit power of the physical uplink control channel.

8. The method according to claim 6, further comprising: The ability of the user equipment to support the preset spatial relationship behavior of the physical uplink shared channel is sent to the cell.

9. The method of claim 6, wherein the predetermined control resource set is a control resource set configured with the lowest identifier on the active downlink bandwidth portion of the cell.

10. The method of claim 6, further comprising: The ability to instruct the user equipment to support the preset spatial relationship behavior of the physical uplink control channel to the cell.

11. A method performed by a base station, the method comprising: The configuration signaling is transmitted to the user equipment, which configures one or more physical uplink control channels for the user equipment on the active uplink bandwidth portion, wherein the one or more physical uplink control channels are not configured with physical uplink control channel spatial relationship information, and the configuration signaling indicates that the base station has enabled the preset spatial relationship behavior of physical uplink control channel transmission. and Based on the spatial relationship corresponding to the quasi-co-location type D reference signal, the user equipment receives a physical uplink control channel, wherein the quasi-co-location type D reference signal corresponds to the quasi-co-location assumption of a predetermined control resource set on the active downlink bandwidth portion of the cell.

12. The method according to claim 11, wherein the preset spatial relationship behavior is further related to the transmit power of the physical uplink control channel.

13. The method of claim 11, further comprising: The ability of the user equipment to receive the preset spatial relationship behavior that supports the physical uplink shared channel.

14. The method of claim 11, wherein the predetermined control resource set is a control resource set configured with the lowest identifier on the active downlink bandwidth portion of the cell.

15. The method of claim 11, further comprising: The ability of the user equipment to receive the preset spatial relationship behavior of the physical uplink control channel.

16. A base station, the base station comprising: transceiver; One or more non-transient calculator-readable media having calculator-executable instructions embedded thereon; as well as At least one processor is coupled to the transceiver and the one or more non-transient calculator-readable media, and is configured to execute calculator-executable instructions to cause the base station to: The transceiver transmits configuration signaling to the user equipment, which configures one or more physical uplink control channels for the user equipment on the active uplink bandwidth portion. The one or more physical uplink control channels are not configured with physical uplink control channel spatial relationship information, and the configuration signaling indicates that the base station has enabled the preset spatial relationship behavior of physical uplink control channel transmission. and Based on the spatial relationship corresponding to the quasi-co-location type D reference signal, the transceiver receives the physical uplink control channel from the user equipment, wherein the quasi-co-location type D reference signal corresponds to the quasi-co-location assumption of a predetermined control resource set on the active downlink bandwidth portion of the cell.

17. The base station according to claim 16, wherein the preset spatial relationship behavior is further related to the transmit power of the physical uplink control channel.

18. The base station according to claim 16, wherein the calculator is executable to cause the base station to: The transceiver receives the user equipment's ability to support the preset spatial relationship behavior of the physical uplink shared channel.

19. The base station of claim 16, wherein the predetermined control resource set is a control resource set configured with the lowest identifier on the active downlink bandwidth portion of the cell.

20. The base station according to claim 16, wherein the calculator is executable to cause the base station to: The transceiver receives the user equipment's ability to support the preset spatial relationship behavior of the physical uplink control channel.

Images