User Equipment and Method for Configuring PUCCH Resources

Abstract

A user equipment and method for configuring Physical Uplink Control Channel (PUCCH) resources are provided. The method includes: receiving a first Bandwidth Part (BWP) configuration associated with a first Uplink (UL) BWP, the first BWP configuration including a PUCCH configuration list having a first PUCCH configuration and a second PUCCH configuration, the first PUCCH configuration indicating a first set of PUCCH resource identifiers (IDs), and the second PUCCH configuration indicating a second set of PUCCH resource IDs; and receiving a second BWP configuration associated with a second UL BWP, the second BWP configuration including a third PUCCH configuration, the third PUCCH configuration indicating a third set of PUCCH resource IDs. The first set of PUCCH resource IDs and the second set of PUCCH resource IDs do not have a common PUCCH resource ID.

Description

[0001] Cross - reference to related applications

[0002] This disclosure claims the benefit and priority of U.S. Provisional Patent Application Serial No. 62 / 958,164, filed on January 7, 2020, entitled "PUCCH Carrier Aggregation Enhancement" (hereinafter referred to as the "'164 provisional case"). For all purposes, the disclosure of the '164 provisional case is hereby incorporated by reference in its entirety into this disclosure. Technical Field

[0003] This disclosure relates to wireless communication, and more particularly, to physical uplink control channel (PUCCH) configuration in a cellular wireless communication network. Background Art

[0004] Abbreviations used in this disclosure include:

[0005] AbbreviationFull name

[0006] 3GPPThird Generation Partnership Project (3 rd Generation Partnership Project)

[0007] 5G5th Generation (5 th Generation)

[0008] ACKAcknowledgment

[0009] BSBase Station

[0010] BWPBandwidth Part

[0011] CORESETControl Resource Set

[0012] CSICHannel State Information

[0013] CSI - RSChannel State Information Reference Signal

[0014] DCIDownlink Control Information

[0015] DLDownlink

[0016] E-UTRA Evolved Universal Terrestrial Radio Access

[0017] eMBB enhanced Mobile Broadband

[0018] HARQ Hybrid Automatic Repeat Request

[0019] HARQ-ACK HARQ Acknowledgement

[0020] ID Identifier

[0021] IE Information Element

[0022] LTE Long Term Evolution

[0023] MAC Medium Access Control

[0024] MAC CE MAC Control Element

[0025] NACK Negative Acknowledgment

[0026] NR New Radio

[0027] NW Network

[0028] PBCH Physical Broadcast Channel

[0029] PDCCH Physical Downlink Control Channel

[0030] PDSCH Physical Downlink Shared Channel

[0031] PHY Physical(layer)

[0032] PUCCH Physical Uplink Control Channel

[0033] PUSCH Physical Uplink Shared Channel

[0034] QCL Quasi Co-Location

[0035] RAN Radio Access Network

[0036] RF Radio Frequency

[0037] RNTI Radio Network Temporary Identifier

[0038] RRC Radio Resource Control

[0039] RS Reference Signal

[0040] SRS Sounding Reference Signal

[0041] SS Synchronization Signal

[0042] SSB Synchronization Signal Block

[0043] TB Transport Block

[0044] TCI Transmission Configuration Indication

[0045] TS Technical Specification

[0046] UE User Equipment

[0047] UL Uplink

[0048] URLLC Ultra-Reliable and Low-Latency Communication

[0049]

[0049] Various efforts have been made to improve different aspects of wireless communication in a cellular wireless communication system (such as 5G NR) by increasing data rate, latency, reliability, and mobility. The 5G NR system is designed to provide flexibility and configurability to optimize network services and types to adapt to different usage scenarios, such as enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC). However, as the demand for radio access continues to increase, there is a need for further improvement in this field. Summary of the Invention

[0050] This disclosure relates to PUCCH configuration in cellular wireless communication.

[0051] According to one aspect of the present invention, a UE for configuring PUCCH resources is provided. The UE includes a memory and a processor coupled to the memory. The memory stores a computer-executable program that, when executed by the processor, causes the processor to: receive a first BWP configuration associated with a first UL BWP, the first BWP configuration including a PUCCH configuration list having a first PUCCH configuration and a second PUCCH configuration, the first PUCCH configuration indicating a first set of PUCCH resource IDs, and the second PUCCH configuration indicating a second set of PUCCH resource IDs; and receive a second BWP configuration associated with a second UL BWP, the second BWP configuration including a third PUCCH configuration, the third PUCCH configuration indicating a third set of PUCCH resource IDs. The first set of PUCCH resource IDs and the second set of PUCCH resource IDs do not have a common PUCCH resource ID.

[0052] According to another aspect of the present disclosure, a method for configuring PUCCH resources performed by a UE is provided. The method includes: receiving a first BWP configuration associated with a first UL BWP, the first BWP configuration including a PUCCH configuration list having a first PUCCH configuration and a second PUCCH configuration, the first PUCCH configuration indicating a first set of PUCCH resource IDs, and the second PUCCH configuration indicating a second set of PUCCH resource IDs; and receiving a second BWP configuration associated with a second UL BWP, the second BWP configuration including a third PUCCH configuration, the third PUCCH configuration indicating a third set of PUCCH resource IDs. The first set of PUCCH resource IDs and the second set of PUCCH resource IDs do not have a common PUCCH resource ID. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] When read in conjunction with the accompanying Figure 1 drawings, aspects of the present disclosure are best understood from the following detailed disclosure. The various features are not drawn to scale. For purposes of discussion, the size of various features may be increased or decreased arbitrarily.

[0054] Figure 1 Illustrates PUCCH transmissions related to different HARQ-ACK codebooks according to an exemplary embodiment of the present disclosure.

[0055] Figure 2 Illustrates enhanced PUCCH spatial relation activation / deactivation MAC CE according to an exemplary embodiment of the present disclosure.

[0056] Figure 3 Illustrates enhanced PUCCH spatial relation activation / deactivation MAC CE according to another exemplary embodiment of the present disclosure.

[0057] Figure 4 Illustrates enhanced PUCCH spatial relation activation / deactivation MAC CE according to yet another exemplary embodiment of the present disclosure.

[0058] Figure 5 Illustrates a method for configuring PUCCH resources according to an exemplary embodiment of the present disclosure.

[0059] Figure 6 Illustrates a method for configuring PUCCH resources according to another exemplary embodiment of the present disclosure.

[0060] Figure 7 Is a block diagram of a node for wireless communication according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0061] The following contains specific information related to the embodiments in the present disclosure. The accompanying drawings and their detailed disclosure are only for the embodiments. However, the present disclosure is not limited to these embodiments. Other variations and embodiments of the present disclosure will be apparent to those skilled in the art.

[0062] Unless otherwise specified, the same or corresponding elements in the drawings may be represented by the same or corresponding reference numerals. Moreover, the drawings and diagrams in the present disclosure are generally not drawn to scale and are not intended to correspond to actual relative sizes.

[0063] For the purposes of consistency and ease of understanding, similar features may be identified by the same numerals in the drawings (although not shown in some examples). However, the features in different embodiments may differ in other respects and should not be narrowly limited to what is shown in the drawings.

[0064] The phrases “In one embodiment,” or “In some embodiments,” may each refer to one or more of the same or different embodiments. The term “coupled” is defined as connected, whether directly or indirectly through intervening components, and is not necessarily limited to physical connections. The term “comprising” means “including but not necessarily limited to”; it specifically indicates an open inclusion or membership in the combinations, groups, series, or equivalents so disclosed. The expressions “at least one of A, B, and C” or “at least one of the following: A, B, and C” mean: “only A, or only B, or only C, or any combination of A, B, and C.”

[0065] The terms “system” and “network” may be used interchangeably. The term “and / or” is only used to describe the associative relationship of associated objects and indicates that there may be three relationships, that is, A and / or B may represent that A exists alone, A and B exist simultaneously, or B exists alone. The character “ / ” generally indicates that the associated objects are in an “or” relationship.

[0066] For purposes of explanation and not limitation, specific details such as functional entities, technologies, protocols, and standards are set forth to provide an understanding of the disclosed technology. In other examples, detailed disclosure of well-known methods, technologies, systems, and architectures is omitted so as not to obscure the disclosure with unnecessary details.

[0067] Those skilled in the art will immediately recognize that any network function or algorithm disclosed can be implemented by hardware, software, or a combination of software and hardware. The described functions may correspond to modules, which can be software, hardware, firmware, or any combination thereof.

[0068] Software implementations may include computer-executable instructions stored on a computer-readable medium such as a memory or other type of storage device. One or more microprocessors or general-purpose computers having communication processing capabilities may be programmed with the corresponding executable instructions and perform the disclosed network functions or algorithms.

[0069] These microprocessors or general-purpose computers may include application specific integrated circuitry (ASIC), programmable logic arrays, and / or use one or more digital signal processors (DSP). Although several disclosed implementations are directed to software installed and executed on computer hardware, alternative implementations implemented as firmware or hardware or a combination of hardware and software are also fully within the scope of the present disclosure. Computer-readable media includes, but is 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), cassette tapes, magnetic tapes, disk storage, or any other equivalent medium capable of storing computer-readable instructions.

[0070] A radio communication network architecture such as a Long Term Evolution (LTE) system, an LTE-Advanced (LTE-A) system, an LTE-Advanced Pro system, or a 5G New Radio (NR) radio access network (RAN) generally includes at least one base station (BS), at least one user equipment (UE), and one or more optional network elements providing network connectivity. The UE communicates through a RAN established by one or more BSs with a network such as a core network (CN), an evolved packet core (EPC) network, an evolved universal terrestrial radio access network (E-UTRAN), a 5G core (5GC), or the Internet.

[0071] The UE may include, but is not limited to, a mobile station, a mobile terminal or device, a user communication radio terminal. The UE may be a portable radio device, which includes, but is not limited to, a mobile phone with wireless communication capabilities, a tablet computer, a wearable device, a sensor, a vehicle, or a personal digital assistant (PDA). The UE is configured to receive signals via an air interface and transmit signals to one or more cells in the RAN.

[0072] The BS may be configured to provide communication services according to at least one of the following radio access technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM), which is commonly referred to as 2G, GSM EDGE Radio Access Network (GERAN) for the evolution of GSM, General Packet Radio Service (GPRS), Universal Mobile Telecommunication System (UMTS), which is commonly referred to as 3G, based on Wideband-Code Division Multiple Access (W-CDMA), High-Speed Packet Access (HSPA), LTE, LTE-A, evolved LTE (eLTE, i.e., LTE connected to 5GC), NR (commonly referred to as 5G), and / or LTE-A Pro. However, the scope of the present disclosure is not limited to these protocols.

[0073] The BS may include, but is not limited to: Node B (NB) in UMTS, evolved Node B (eNB) in LTE or LTE-A, Radio Network Controller (RNC) in UMTS, BS Controller (BSC) in GSM / GERAN, ng-eNB in Evolved Universal Terrestrial Radio Access (E-UTRA) BS connected to 5GC, next-generation Node B (gNB) in 5G-RAN, and any other device capable of controlling radio communication and managing radio resources within a cell. The BS may serve one or more UEs via a radio interface.

[0074] The BS is operable to provide radio coverage to a specific geographical area using a plurality of cells that form a RAN. The BS supports the operation of the cells. Each cell is operable to serve at least one UE within its radio coverage.

[0075] Each cell (commonly referred to as a serving cell) provides service to serve one or more UEs within its radio coverage, such that each cell schedules DL and optional UL resources to at least one UE within its radio coverage for DL and optional UL packet transmission. The BS may communicate with one or more UEs in a radio communication system via a plurality of cells.

[0076] The cell may allocate sidelink (SL) resources to support Proximity Service (ProSe) or Vehicle to Everything (V2X) services. Each cell may have a coverage area that overlaps with other cells.

[0077] In the case of Multi-RAT Dual Connectivity (MR-DC), the primary cell of the Master Cell Group (MCG) or the Secondary Cell Group (SCG) can be referred to as a Special Cell (SpCell). The Primary Cell (PCell) can refer to the SpCell of the MCG. The Primary SCG Cell (PSCell) can refer to the SpCell of the SCG. The MCG can refer to the serving cell group associated with the Master Node (MN), including the SpCell and optionally one or more Secondary Cells (SCells). The SCG can refer to the serving cell group associated with the Secondary Node (SN), including the SpCell and optionally one or more SCells.

[0078] As previously disclosed, the frame structure for NR supports flexible configurations to accommodate various next-generation (e.g., 5G) communication requirements, such as enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), while meeting high-reliability, high-data-rate, and low-latency requirements. Orthogonal Frequency Division Multiplexing (OFDM) technology in 3GPP can be used as the baseline for the NR waveform. Scalable OFDM digital schemes, such as adaptive subcarrier spacing, channel bandwidth, and Cyclic Prefix (CP), can also be used.

[0079] Two coding schemes are considered for NR, specifically, Low-Density Parity-Check (LDPC) codes and polar codes. The coding scheme adaptation can be configured based on the channel condition and / or the service application.

[0080] At least DL transmission data, guard period, and UL transmission data should be included in the transmission time interval (TTI) of a single NR frame. The respective parts of the DL transmission data, guard period, and UL transmission data should also be configurable, configured based on, for example, the network dynamics of NR. SL resources can also be provided in the NR frame to support ProSe services or V2X services.

[0081] Examples of some terms are provided below.

[0082] HARQ: A function that ensures delivery between peer entities at layer 1 (e.g., the PHY layer). When the PHY layer is not configured for DL / UL spatial multiplexing, a single HARQ process can support one TB. When the PHY layer is configured for DL / UL spatial multiplexing, a single HARQ process can support one or more TBs. Each serving cell can have one HARQ entity. Each HARQ entity can support parallel processing of (e.g., multiple) DL and UL HARQ processes.

[0083] HARQ-ACK: HARQ-ACK can include a 1-bit indicator, where when the bit value of the indicator is set to a first value (e.g., "0"), HARQ-ACK can be a negative acknowledgment (NACK), and when the bit value of the indicator is set to a second value (e.g., "1"), HARQ-ACK can be an affirmative acknowledgment (ACK).

[0084] To meet the low latency requirements, at least two HARQ-ACK codebooks can be constructed simultaneously to support different service types for the UE. Since the HARQ-ACK codebooks sent on different PUCCH resources correspond to different service types, separately configuring the parameters in the PUCCH configuration (e.g., the PUCCH-Config IE) can bring high flexibility in scheduling. Thus, the PUCCH spatial relation information (e.g., the PUCCH-SpatialRelationInfo IE) and the sub-slot configuration can be separately configured for different HARQ-ACK codebooks. The PUCCH-SpatialRelationInfo provides information about the spatial domain filter of the PUCCH used by the UE (e.g., for the reception of SS / PBCH blocks, the reception of CSI-RS, or the transmission of SRS).

[0085] If the UE is configured with a single value of the PUCCH spatial relation information ID (e.g., the pucch-SpatialRelationInfoId IE), the spatial settings for PUCCH transmission can be provided through the PUCCH-SpatialRelationInfo; otherwise, if the UE is provided with multiple values for the PUCCH-SpatialRelationInfo, the UE can determine the spatial settings for PUCCH transmission through the PUCCH spatial relation activation / deactivation MAC CE. In addition, only a single PUCCH spatial relation information can be activated for one PUCCH resource at a time.

[0086] After determining the spatial setting for PUCCH transmission, the UE may apply the corresponding setting to the spatial domain filter, where the spatial setting is for the PUCCH that the UE transmits 3 ms after receiving a PDSCH corresponding to the provision of HARQ-ACK information with an ACK value and providing PUCCH-SpatialRelationInfo.

[0087] Figure 1 PUCCH transmission 100 related to different HARQ-ACK codebooks according to an exemplary embodiment of the present disclosure is shown. The PUCCH resource 102 with PUCCH resource ID #1 in slot #0 is for eMBB HARQ-ACK transmission. The PUCCH resource 104 with PUCCH resource ID #2 in slot #0 is for URLLC HARQ-ACK transmission. The PUCCH resource 112 with PUCCH resource ID #1 in slot #1 is for URLLC HARQ-ACK transmission. The PUCCH resources 102 and 112 corresponding to HARQ-ACKs for different service types are transmitted in PUCCHs with the same PUCCH resource ID. When different HARQ-ACK codebooks corresponding to the same PUCCH resource ID are constructed to support different service types, since the spatial relationship of the PUCCH resource for the serving cell is activated or deactivated by a MAC CE received from the network, it may not be possible to immediately switch between different spatial relationship settings. For example, the PUCCH resource 102 and the PUDCCH resource 112 are separated by 1 slot, and it may take 3 slots from receiving to applying the PUCCH spatial relationship activation / deactivation MAC CE.

[0088] In other words, even if spatial settings can be configured separately for different HARQ-ACK codebooks, timing-related limitations may still be imposed. In addition, it takes time to apply the determined spatial setting to the PUCCH resource. Therefore, when the spatial setting for the PUCCH resource cannot be properly changed or scheduled, there may be an adverse impact on the reliability of the PUCCH resource (such as the PUCCH resource 112) for transmitting the URLLC HARQ-ACK codebook.

[0089] The embodiments disclosed subsequently relate to improved methods, systems, devices, and apparatuses for supporting separate spatial settings for different HARQ-ACK codebooks. Additionally, any two or more of the following disclosed in this disclosure: embodiments, situations, paragraphs, (sub)item numbers, points, actions, behaviors, terms, or claims can be logically and reasonably combined to form a specific method.

[0090] Scenario 1: More than one PUCCH configuration (e.g., PUCCH-Config) or more than one configuration corresponding to PUCCH transmission is configured for the UE

[0091] Scenario 1-1: The UE can receive PUCCH spatial relation activation / deactivation MAC CE corresponding to Rel-16.

[0092] In other words, for Rel-16, there may be new PUCCH spatial relation activation / deactivation MAC CE. The new PUCCH spatial relation activation / deactivation MAC CE can be identified by a new logical channel ID (LCID: Logical Channel ID).

[0093] In one embodiment, the content field in the Rel-16 MAC CE can be the same as the content field in Rel-15. When the PUCCH transmission is indicated as high priority or a service type different from Rel-15, the UE can activate the PUCCH spatial relation information through the Rel-16 PUCCH spatial relation activation / deactivation MAC CE.

[0094] In one embodiment, the content field in the Rel-16 MAC CE can include an index corresponding to the priority, such as a priority index, a PUCCH-Config index, or any other index indicating different service types.

[0095] Scenario 1-2: The UE can receive PUCCH spatial relation activation / deactivation MAC CE including a content field with an index for identifying the PUCCH configuration.

[0096] The index (or identifier) of the PUCCH configuration can correspond to the service type. In one embodiment, according to the configuration for the service type, the index (or identifier) of the PUCCH configuration can be an index associated with the service type. In one embodiment, the index (or identifier) of the PUCCH configuration can be an index corresponding to the priority indicator. In other words, the first PUCCH configuration can refer to the PUCCH with low priority, and the second PUCCH configuration can refer to the PUCCH with high priority. Alternatively, the first PUCCH configuration can refer to the PUCCH with high priority, and the second PUCCH configuration can refer to the PUCCH with low priority.

[0097] Figure 2Shows an enhanced PUCCH spatial relation activation / deactivation MAC CE 200 according to an exemplary embodiment of the present disclosure. The PUCCH spatial relation activation / deactivation MAC CE 200 may have a fixed size of 24 bits (3 octets), including oct1, oct2, and oct3.

[0098] The serving cell ID field indicates the identity of the serving cell to which the MAC CE 200 applies. The length of the serving cell ID field is 5 bits.

[0099] The BWP ID field indicates the UL BWP to which the MAC CE 200 applies, as a code point of the DCI bandwidth part indicator field specified in TS38.212. The length of the BWP ID field is 2 bits.

[0100] The PUCCH resource ID field contains an identifier of the PUCCH resource ID identified by PUCCH-ResourceId as specified in TS38.331. The length of the PUCCH resource ID field is 7 bits;

[0101] S i field (i is an integer, shown in Figure 2 as S7 - S0): If there is PUCCH spatial relation information with PUCCH-SpatialRelationInfoId specified in TS38.331 configured for the UL BWP indicated by the BWP ID field, then S i indicates the activation status of the PUCCH spatial relation information with a PUCCH-SpatialRelationInfoId equal to i + 1. Otherwise, the MAC entity may ignore this field. S i field can be set to 1 to indicate that the PUCCH spatial relation information with a PUCCH-SpatialRelationInfoId equal to i + 1 should be activated. S i field can be set to 0 to indicate that the PUCCH spatial relation information with a PUCCH-SpatialRelationInfoId equal to i + 1 should be deactivated. Only a single PUCCH spatial relation information can be activated for one PUCCH resource at a time. Oct 3 including S7 - S0 can also be referred to as a bitmap.

[0102] The R field is a reserved bit, which can be set to 0.

[0103] In one embodiment, the P field shown in Figure 2 can be a content field for identifying the index of the PUCCH configuration in case 1 - 2.

[0104] In one embodiment, the index may be a PUCCH configuration index (e.g., PUCCH-ConfigId: 0, PUCCH-ConfigId: 1) in a PUCCH configuration list (e.g., PUCCH-ConfigList).

[0105] In one embodiment, the index may correspond to a PUCCH configuration (e.g., PUCCH-Config) for Rel-15 or Rel-16 (e.g., 0 for Rel-15 and 1 for Rel-16).

[0106] In one embodiment, the index may correspond to an index in PUCCH-Config.

[0107] Table 1 shows an exemplary data structure of a BWP configuration associated with a UL BWP, and the BWP configuration includes a PUCCH configuration list.

[0108] Table 1

[0109]

[0110] In one embodiment, the index may be a priority index provided for PUCCH transmission. The priority index may correspond to an indication in the DCI that schedules the PUCCH transmission. The priority index may be provided in the PUCCH configuration.

[0111] In one embodiment, the index may be a group index configured for PUCCH transmission. The group index may be configured in the PUCCH configuration. The group index may be configured in a PUCCH-Config that configures PUCCH resources. The group index may be indicated in the DCI that schedules the PUCCH transmission and / or configured in a CORESET configuration associated with the DCI that schedules the PUCCH transmission, where the DCI is monitored / received in a search space indicated by the CORESET configuration.

[0112] Case 1-3: The UE may receive a PUCCH spatial relation activation / deactivation MAC CE that does not include a content field for identifying the index of the PUCCH configuration.

[0113] In one embodiment, the PUCCH spatial relation information may be configured with the same index (e.g., the same pucch-SpatialRelationInfoId) in a first PUCCH-Config indicated as having a low priority and a second PUCCH-Config indicated as having a high priority. More specifically, different PUCCH configurations may correspond to different priorities. The PUCCH-Config including the PUCCH spatial relation information to be applied may be indicated by a priority indication in the DCI scheduling the PDSCH that includes the PUCCH spatial relation activation / deactivation MAC CE.

[0114] In one embodiment, in a first PUCCH-Config indicated as having a low priority and a second PUCCH-Config indicated as having a high priority, the PUCCH resources may be configured with the same PUCCH resource ID. The PUCCH-Config including the PUCCH resource to be applied may be indicated by a priority indication in the DCI scheduling the PDSCH that includes the PUCCH spatial relation activation / deactivation MAC CE.

[0115] In one embodiment, the PUCCH spatial relation information may be configured only in the PUCCH-Config indicated as having a low priority, or only in the Rel-15 PUCCH-Config. There may be two configured spatialRelationInfoToAddModList, and the indexes (e.g., pucch-SpatialRelationInfoId) of the PUCCH spatial relation information configured in different spatialRelationInfoToAddModList may be the same. The index of the spatialRelationInfoToAddModList associated with the PUCCH spatial relation information to be applied may be indicated by a priority indication in the DCI scheduling the PDSCH that includes the PUCCH spatial relation activation / deactivation MAC CE.

[0116] In one embodiment, the MAC CE may activate more than one PUCCH spatial relation information for one PUCCH resource at a time. The same PUCCH resource ID may be configured in a first PUCCH-Config indicated as having a low priority and a second PUCCH-Config indicated as having a high priority.

[0117] If the PUCCH spatial relation information is configured with the same index in a first PUCCH-Config indicated as low priority and a second PUCCH-Config indicated as high priority, the PUCCH spatial relation information with low priority and the PUCCH spatial relation information with high priority can be respectively configured in the first PUCCH-Config and the second PUCCH-Config. If the PUCCH spatial relation information is configured with the same index in a first spatialRelationInfoToAddModList and a second spatialRelationInfoToAddModList in the PUCCH-Config, the PUCCH spatial relation information with low priority and the PUCCH spatial relation information with high priority can be respectively configured in the first spatialRelationInfoToAddModList and the second spatialRelationInfoToAddModList.

[0118] In one embodiment, the PUCCH-SpatialRelationInfo IE may include multiple sets of referenceSignal, pucch-PathlossReferenceRS-Id, p0-PUCCH-Id, and closedLoopIndex. Each set may correspond to a specific PUCCH-Config index or a specific priority level (e.g., high priority or low priority).

[0119] Case 1-4: The UE may receive a PUCCH spatial relation activation / deactivation MAC CE including a content field for identifying the state of the PUCCH spatial relation information.

[0120] The state of the PUCCH spatial relation information may include the activation state of the PUCCH spatial relation information.

[0121] In one embodiment, for a PUCCH resource, more than one PUCCH spatial relation information may be activated simultaneously (e.g., activated by a MAC CE).

[0122] The PUCCH spatial relation information applied for PUCCH transmission may correspond to a priority index provided for PUCCH transmission. For example, the activated PUCCH spatial relation information with a low index may indicate a PUCCH transmission of low priority, and the activated PUCCH spatial relation information with a high index may indicate a PUCCH transmission of high priority. Alternatively, the activated PUCCH spatial relation information with a low index may refer to a PUCCH transmission indicated as high priority, and the activated PUCCH spatial relation information with a high index may refer to a PUCCH transmission indicated as low priority. More specifically, if both S0 and S2 are set to 1 in the PUCCH spatial relation activation / deactivation MAC CE, when the PUCCH resource indicated by DCI corresponds to high priority or the PUCCH transmission configured by PUCCH-Config is identified as high priority (e.g., PUCCH-Config-Rel16), the UE may determine that the spatial setting applied to the PUCCH transmission is the PUCCH spatial relation information with a pucch-SpatialRelationInfoId equal to 1 (corresponding to S0). Similarly, when the PUCCH resource indicated by DCI corresponds to low priority or the PUCCH transmission configured by PUCCH-Config is identified as low priority, the UE may determine that the spatial setting applied to the PUCCH transmission is the PUCCH spatial relation information with a pucch-SpatialRelationInfoId equal to 3 (corresponding to S2).

[0123] Note that the PUCCH spatial relation activation / deactivation MAC CE indicating more than one active state can be used to indicate PUCCH resource IDs configured in more than one PUCCH-Config within the same BWP. The UE may apply the PUCCH spatial relation information with a smaller PUCCH-SpatialRelationInfoID indicated as active in the MAC CE to the PUCCH resources indicated as high priority by the DCI message, and apply the PUCCH spatial relation information with a larger PUCCH-SpatialRelationInfoID indicated as active in the MAC CE to the PUCCH resources indicated as low priority by the DCI message. Alternatively, the UE may apply the PUCCH spatial relation information with a smaller PUCCH-SpatialRelationInfoID indicated as active in the MAC CE to the PUCCH resources indicated as low priority by the DCI message, and apply the PUCCH spatial relation information with a larger PUCCH-SpatialRelationInfoID indicated as active in the MAC CE to the PUCCH resources indicated as high priority by the DCI message.

[0124] Note that even if PUCCH resources with the same PUCCH resource ID are configured in a first PUCCH-Config of low priority and a second PUCCH-Config of high priority, the PUCCH resources in the first PUCCH-Config and the PUCCH resources in the second PUCCH-Config may not have the same PUCCH resource configuration (e.g., using the same PUCCH format).

[0125] Note that in the case where the PUCCH spatial relation activation / deactivation MAC CE indicates only one active PUCCH spatial relation information S i for the PUCCH resource ID of the BWP, it may be implied that S i is activated for the PUCCH resource ID configured in each PUCCH-Config of the BWP.

[0126] In one embodiment, the active PUCCH spatial relation information may be specified by an index instead of a bitmap. The activation state of the PUCCH spatial relation information may correspond to the index PUCCH-SpatialRelationInfoId.

[0127] The PUCCH spatial relation information applied to PUCCH transmission may be indicated by a priority index and a PUCCH-SpatialRelationInfoID. Figure 3Shows the enhanced PUCCH spatial relation activation / deactivation MAC CE 300 according to an exemplary embodiment of the present disclosure. The PUCCH spatial relation activation / deactivation MAC CE 300 may have 24 bits, including Oct1, Oct2, and Oct3. It can be indicated by the SRI i field (i is an integer, SRI0 and SRI1 shown in Figure 3 ) the index of the PUCCH spatial relation information to be activated, and i is equal to 0 or 1. It can be indicated by the P i field (i is an integer, P0 and P1 shown in Figure 3 ) the priority index associated with the SRI i field.

[0128] The PUCCH spatial relation information with PUCCH-SpatialRelationInfoId equal to SRI0 is applied to the PUCCH transmission indicated by the priority index P0 (the value of P0 is 0 or 1), and the PUCCH spatial relation information with PUCCH-SpatialRelationInfoId equal to SRI1 is applied to the PUCCH transmission indicated by the priority index P1 (the value of P1 is 0 or 1). It should be noted that the position of each field in Figure 3 is exemplary and not restrictive. In one embodiment, it can be P0 first and P1 second. In addition, the UE can associate the priority index shown in Figure 3 with the priority indicator in the DCI or the PUCCH-Config index. For example, PUCCH-Config 0 can correspond to P0, and PUCCH-Config 1 can correspond to P1.

[0129] Case 1-5: The UE may receive a PUCCH configuration including an indicator of PUCCH spatial relation information associated with the service type.

[0130] The PUCCH configuration may indicate a set of PUCCH spatial relation information IDs (e.g., pucch-SpatialRelationInfoId). In one embodiment, the number of pucch-SpatialRelationInfoId may be different from that in Rel-15 (e.g., more than 8). The number of IDs in a set of PUCCH spatial relation information IDs may be maxNrofSpatialRelationInfos. The value of maxNrofSpatialRelationInfo in the PUCCH configuration may be greater than 8 (e.g., 16).

[0131] In one embodiment, the PUCCH resources configured in different PUCCH configurations may be different. For example, if there are 16 pucch-SpatialRelationInfoIds configured for a UE, half of the configured PUCCH spatial relation information IDs (e.g., 0-7) may be configured in a PUCCH-Config indicated as having a high priority, and the other half of the configured PUCCH spatial relation information IDs (e.g., 8-15) may be configured in another PUCCH-Config indicated as having a low priority.

[0132] Figure 4 An enhanced PUCCH spatial relation activation / deactivation MAC CE 400 according to an exemplary embodiment of the present disclosure is shown. The PUCCH spatial relation activation / deactivation MAC CE 400 may have 32 bits, including Oct1, Oct2, Oct3, and Oct4. The description of each field may refer to the MAC CE 200 shown in Figure 2 Since there are 16 pucch-SpatialRelationInfoIds configured for the UE, the length of the S i field (i is an integer, the S shown in Figure 4 in 15 -S0) is increased to 16.

[0133] Case 1-6: The UE may receive a PUCCH spatial relation activation / deactivation MAC CE that indicates deactivating all PUCCH spatial relation information for the PUCCH resource ID in the BWP.

[0134] In this example, the UE may apply the default spatial relation to the PUCCH resource corresponding to the PUCCH resource ID in the BWP.

[0135] In one embodiment, if the PUCCH resource ID indicated in the MAC CE is configured in more than one PUCCH-Config, the PUCCH resources corresponding to the PUCCH resource IDs configured in different PUCCH-Configs may have separate default spatial relations. The default spatial relation for a PUCCH resource may be the PUCCH spatial relation information having the smallest PUCCH-SpatialRelationInfoID in the spatialRelationInfoToAddModList associated with the PUCCH resource in the BWP.

[0136] When each PUCCH-Config contains only one spatialRelationInfoToAddModList, the PUCCH-Config may explicitly or implicitly indicate the correlation between the PUCCH resource and the spatialRelationInfoToAddModList. Alternatively, the spatialRelationInfoToAddModList may be configured with priorities, and the PUCCH spatial relation information in the spatialRelationInfoToAddModList is associated with the PUCCH resources of the configured priorities.

[0137] In one embodiment, if the PUCCH resource ID indicated in the MAC CE corresponds to more than one priority level (e.g., high priority or low priority), the PUCCH resources with PUCCH resource IDs corresponding to different priorities may have separate default spatial relations. The default spatial relation for a PUCCH resource may be the PUCCH spatial relation information with the smallest PUCCH-SpatialRelationInfoID in the associated spatialRelationInfoToAddModList of the PUCCH resource in the BWP.

[0138] When each PUCCH-Config contains only one spatialRelationInfoToAddModList, the PUCCH-Config may explicitly or implicitly indicate the correlation between the PUCCH resource and the spatialRelationInfoToAddModList. Alternatively, the spatialRelationInfoToAddModList may be configured with priorities, and the PUCCH spatial relation information in the spatialRelationInfoToAddModList is associated with the PUCCH resources of the configured priorities.

[0139] In one embodiment, if the PUCCH resource ID indicated in the MAC CE is configured in more than one PUCCH-Config, and each PUCCH-Config is associated with a set of CORESET configurations, the PUCCH resources corresponding to the PUCCH resource IDs configured in different PUCCH-Configs may have separate default spatial relationships. The CORESET configuration includes a group index for identifying which group the CORESET belongs to. The default spatial relationship for the PUCCH resource may be the TCL state or QCL assumption of the CORESET with the lowest CORESET ID in the CORESET group associated with the PUCCH resource scheduled in the BWP.

[0140] In one embodiment, the PUCCH resources configured in different PUCCH-Configs may be different. More specifically, different PUCCH resource IDs may be configured in different PUCCH configurations.

[0141] For example, the UE is configured with 128 PUCCH resources and two PUCCH configurations, including a first PUCCH-Config and a second PUCCH-Config. Although the UE may select PUCCH resources from 128 PUCCH resource candidates (e.g., the range of PUCCH-ResourceId is from 0 to 127) for the first PUCCH-Config and the second PUCCH-Config, the PUCCH-ResourceIds of the PUCCH resources included in the resourceToAddModList in their respective PUCCH-Configs may not be the same.

[0142] For example, if the first PUCCH-Config includes PUCCH resources with PUCCH-ResourceID of {0, 2, 4, 6}, the PUCCH resources included in the second PUCCH-Config may not be selected from PUCCH-ResourceIDs equal to 0, 2, 4, or 6. The second PUCCH-Config may include PUCCH resources with PUCCH-ResourceID of {1, 3, 5, 7}.

[0143] For example, if the maximum number of PUCCH resources is 128, the PUCCH resources configured in the first PUCCH-Config may be configured with PUCCH-ResourceIds equal to 0 - 63, and the PUCCH resources configured in the second PUCCH-Config may be configured with PUCCH-ResourceIds equal to 64 - 127.

[0144] In one embodiment, the first PUCCH-Config and the second PUCCH-Config may correspond to different service types. For example, the first PUCCH-Config may correspond to eMBB service, while the second PUCCH-Config may correspond to URLLC service. In other words, the first PUCCH-Config may correspond to a low priority, while the second PUCCH-Config may correspond to a high priority.

[0145] Case 1-7: The PUCCH-Config, PUCCH-ResourceSet, and PUCCH-Resource may be mapped to a specific priority level (e.g., high priority or low priority).

[0146] In one embodiment, the PUCCH-Config IE may indicate the priority level to which the configured PUCCH-Config is mapped. For example, if there are two PUCCH configurations in the PUCCH configuration list, the first PUCCH-Cong may correspond to a low priority, and the second PUCCH-Config may correspond to a high priority.

[0147] In one embodiment, the PUCCH-ResourceSet IE may indicate the priority level to which the configured PUCCH-Config is mapped. For example, if there are two PUCCH resource sets, the first PUCCH resource set may correspond to a low priority, and the second PUCCH resource set may correspond to a high priority.

[0148] In one embodiment, the PUCCH-Resource IE may indicate the priority level to which the configured PUCCH-Config is mapped. For example, if there are two PUCCH resources, the first PUCCH resource may correspond to a low priority, and the second PUCCH resource may correspond to a high priority.

[0149] Case 1-8: The DCI message may include an indicator of the PUCCH configuration.

[0150] In one embodiment, the PUCCH resources indicated by the DCI message may correspond to different PUCCH configurations. For example, the PUCCH transmission indicated by a DCI with a high-priority index (e.g., PUCCH resource indicator) may correspond to the PUCCH-Config for Rel-16. More specifically, the DCI for scheduling PUCCH transmission may include a priority index. If the priority index refers to a high priority, the PUCCH resources may be configured in the PUCCH-Config for Rel-16. In other words, there are two HARQ-ACK codebooks scheduled by DCIs with different priorities among two PUCCH resources, and these two PUCCH resources are respectively configured in the PUCCH-Config for Rel-15 and the PUCCH-Config for Rel-16.

[0151] In one embodiment, the corresponding PUCCH configuration index may be indicated by a field in the DCI message. For example, the field for indicating the PUCCH configuration index may have a bit length of 1, where a value of 0 refers to the PUCCH-Config for Rel-15 and a value of 1 refers to the PUCCH-Config for Rel-16. Alternatively, a value of 0 may refer to the PUCCH-Config for Rel-16, and a value of 1 may refer to the PUCCH-Config for Rel-15.

[0152] Case 1-9: Each configured PUCCH configuration is associated with a set of CORESET configurations.

[0153] In one embodiment, the CORESET configuration includes a group index for identifying which CORESET group the CORESET belongs to.

[0154] In one embodiment, the PUCCH spatial relation activation / deactivation MAC CE may include a group index, and the UE may apply the identified PUCCH spatial relation information to the PUCCH resources in the indicated PUCCH-Config.

[0155] In one embodiment, the PUCCH spatial relation activation / deactivation MAC CE may not include a group index, and the UE may apply the identified PUCCH spatial relation information to the PUCCH resources in the PUCCH-Config associated with the CORESET group, and the DCI scheduling the PDSCH including the PUCCH spatial relation activation / deactivation MAC CE is transmitted in that CORESET group.

[0156] Case 2: Only a single PUCCH configuration or a single configuration corresponding to the PUCCH transmission is configured for the UE

[0157] It should be noted that the embodiments may include combinations of the embodiments disclosed in Case 1. For example, the index corresponding to the "different PUCCH-Config" in Case 1 may be associated with the index corresponding to the "different spatial relation information list" (or "different list") in Case 2. The "list" in Case 2 refers to the "spatial relation information list".

[0158] Case 2-1: The UE may receive an identifier of the PUCCH spatial relation information corresponding to the service type.

[0159] The PUCCH spatial relation activation / deactivation MAC CE may include a content field that indicates the identifier of the spatial relation information corresponding to the service type. The identifier of the PUCCH spatial relation information may be an index of the PUCCH spatial relation information list. In other words, there may be more than one spatialRelationInfoToAddModList in the PUCCH configuration (for example, spatialRelationInfoToAddModList1, spatialRelationInfoToAddModList2). And different lists may correspond to different service types.

[0160] In one embodiment, the UE may receive a MAC CE that includes indices corresponding to different spatial relation information lists. In one embodiment, the PUCCH-SpatialRelationInfoId of the PUCCH spatial relation information in different lists may have the same value. In one embodiment, the PUCCH-SpatialRelationInfoId of the PUCCH spatial relation information in different lists may have different values.

[0161] In one embodiment, the PUCCH spatial relation information configured in one list may be replaced with the PUCCH spatial relation information configured in another list. For example, if the first PUCCH spatial relation information configured in the first list and the second PUCCH spatial relation information configured in the second list are activated or indicated for the same PUCCH transmission, the UE may apply the PUCCH spatial relation information in the list with a higher priority.

[0162] In one embodiment, the PUCCH resource ID corresponding to the first list and the PUCCH resource ID corresponding to the second list may be different. For example, PUCCH-ResourceId 0-63 may be indicated as the PUCCH spatial relation information applied in the first list, and PUCCH-ResourceId 64-127 may be indicated as the PUCCH spatial relation information applied in the second list.

[0163] In one embodiment, there may be a Rel-16 PUCCH spatial relation activation / deactivation MAC CE corresponding to the PUCCH spatial relation in a list that can be used for different service types. For example, the Rel-16 PUCCH spatial relation activation / deactivation MAC CE may correspond to the first list. Alternatively, the Rel-16 PUCCH spatial relation activation / deactivation MAC CE may correspond to the second list.

[0164] Case 2-2: If there is no different list in PUCCH-Config, then for one PUCCH resource, more than one PUCCH spatial relation information can be active at a time.

[0165] The PUCCH spatial relation activation / deactivation MAC CE may include a content field indicating the activation state of the PUCCH spatial relation information. The activation state of the PUCCH spatial relation information may be indicated as the index of PUCCH-SpatialRelationInfoId.

[0166] In one embodiment, there may be more than one bit equal to '1' in the S i field of the PUCCH spatial relation activation / deactivation MAC CE. In one embodiment, the UE may apply the PUCCH spatial relation information with the lowest index in the MAC CE for PUCCH transmission corresponding to the high priority. In an alternative embodiment, the UE may apply the PUCCH spatial relation information with the highest index in the MAC CE for PUCCH transmission corresponding to the high priority.

[0167] In one embodiment, the PUCCH resource may be configured with more than one PUCCH resource ID, each ID associated with the priority or service type for PUCCH transmission. The UE may apply the active PUCCH spatial relation information to the PUCCH resource with the PUCCH resource ID indicated in the PUCCH spatial relation activation / deactivation MAC CE.

[0168] Table 2 shows an exemplary data structure of a PUCCH resource configuration including more than one PUCCH resource ID associated with different priorities or different service types. The PUCCH resource ID includes pucch-ResourceId and pucch-ResourceIdForHighPriority.

[0169] Table 2

[0170]

[0171]

[0172] There may be only one bit equal to ‘1’ in the S i field of the PUCCH spatial relation activation / deactivation MAC CE.

[0173] In the S i field of the PUCCH spatial relation activation / deactivation MAC CE, there may be only one bit equal to ‘1’.

[0174] The priority or service type for PUCCH transmission and the associated PUCCH resource ID can be indicated in the DCI message that schedules the PUCCH transmission. When the DCI message indicates high priority for PUCCH transmission, the pucch-ResourceIdForHighPriority value can be used.

[0175] For a PUCCH resource, the PUCCH resource IDs associated with different priorities or different service types can have different values. If both pucch-ResourceId and pucch-ResourceIdForHighPriority are configured for the PUCCH resource, then for the PUCCH resource, more than one PUCCH spatial relation information can be activated.

[0176] For a PUCCH resource, the PUCCH resource IDs associated with different priorities or service types can be configured as the following examples:

[0177] Case 2-3: The UE can receive the identification of the PUCCH resource group.

[0178] In one embodiment, the identification of the PUCCH resource group can be an explicit group index. In one embodiment, the identification of the PUCCH resource group can be the index of the associated CORESET configuration.

[0179] In one embodiment, the PUCCH resource group may be configured as the following example:

[0180] Table 3 shows an exemplary data structure of the PUCCH resource configuration including the PUCCH resource ID and the PUCCH resource group ID.

[0181] Table 3

[0182]

[0183]

[0184] In one embodiment, the PUCCH spatial relation activation / deactivation MAC CE may include the group index of the PUCCH resource.

[0185] If the UE receives the PUCCH spatial relation activation / deactivation MAC CE including the group index of the PUCCH resource, the UE may apply the PUCCH spatial relation information to all PUCCH resources in the group.

[0186] If the UE receives both the PUCCH spatial relation activation / deactivation MAC CE including the group index of the PUCCH resource and the PUCCH spatial relation activation / deactivation MAC CE without the group index of the PUCCH resource, the UE may apply the PUCCH spatial relation information indicated in the MAC CE without the group index to the indicated PUCCH resources.

[0187] Figure 5 Fig. 500 shows a method for configuring PUCCH resources according to an exemplary embodiment of the present disclosure. In operation 502, the UE receives a first BWP configuration associated with a first UL BWP. The first BWP configuration includes a PUCCH configuration list having a first PUCCH configuration and a second PUCCH configuration. The first PUCCH configuration indicates a first set of PUCCH resource IDs. The second PUCCH configuration indicates a second set of PUCCH resource IDs.

[0188] An exemplary BWP configuration including a PUCCH configuration list may refer to Table 1. The PUCCH configuration list (e.g., PUCCH-ConfigList IE) may include a first PUCCH configuration (e.g., PUCCH-Config0) and a second PUCCH configuration (e.g., PUCCH-Config1).

[0189] In operation 504, the UE receives a second BWP configuration associated with a second UL BWP. The second BWP configuration includes a third PUCCH configuration. The third PUCCH configuration indicates a third set of PUCCH resource IDs. The first set of PUCCH resource IDs and the second set of PUCCH resource IDs do not have a common PUCCH resource ID.

[0190] The data structure of the second BWP configuration associated with the second UL BWP may be similar to the data structure of the first BWP configuration associated with the first UL BWP. In one embodiment, the first BWP configuration may include two PUCCH configurations (a first and a second PUCCH configuration), while the second BWP configuration may include a single PUCCH configuration (a third PUCCH configuration).

[0191] In one embodiment, the PUCCH resources in the first PUCCH configuration and the PUCCH resources in the second PUCCH configuration may not be the same. In other words, the first set of PUCCH resource IDs and the second set of PUCCH resource IDs do not have a common PUCCH resource ID. The relevant disclosure may refer to the embodiments in cases 1-6.

[0192] In one embodiment, there may be no specific restrictions on how to configure PUCCH resources for different BWP configurations. For example, the PUCCH resources in the first PUCCH configuration associated with the first UL BWP and the PUCCH resources in the third PUCCH configuration associated with the second UL BWP may have the same PUCCH resource ID. In other words, the first set of PUCCH resource IDs may have at least one common PUCCH resource ID with the third set of PUCCH resource IDs.

[0193] In one embodiment, there may also be restrictions on how to configure PUCCH resources for different BWP configurations. For example, the PUCCH resources in the first PUCCH configuration and the PUCCH resources in the third PUCCH configuration may not be the same. In other words, the first set of PUCCH resource IDs and the third set of PUCCH resource IDs do not have a common PUCCH resource ID.

[0194] In one embodiment, the first PUCCH configuration and the second PUCCH configuration may correspond to different service types. Different service types may correspond to different priorities. For example, the first PUCCH configuration may correspond to eMBB service, while the second PUCCH configuration may correspond to URLLC service. For example, the first PUCCH configuration may correspond to a low priority, while the second PUCCH configuration may correspond to a high priority.

[0195] In one embodiment, a first PUCCH resource selected from a first set of PUCCH resource IDs for transmitting a first HARQ-ACK codebook and a second PUCCH resource selected from a second set of PUCCH resource IDs for transmitting a second HARQ-ACK codebook correspond to different priorities. For example, the first HARQ-ACK codebook can be used for eMBB services (which may have a low priority), while the second HARQ-ACK codebook can be used for URLLC services (which may have a high priority).

[0196] In one embodiment, the first PUCCH configuration further indicates a first set of PUCCH spatial relation information IDs. The second PUCCH configuration further indicates a second set of PUCCH spatial relation information IDs. The relevant disclosures can refer to the embodiments in cases 1-5. The maximum number of IDs in the first set of PUCCH spatial relation information IDs (e.g., maxNrofSpatialRelationInfo) can be greater than the number specified in Rel-15.

[0197] Figure 6 A method 600 for configuring PUCCH resources according to an exemplary embodiment of the present disclosure is shown. Action 602 and action 604 respectively correspond to Figure 5 action 502 and action 504 shown in. In action 606, the UE receives a DCI message scheduling PDSCH reception, and the DCI message includes a priority indicator. The relevant disclosures can refer to the embodiments in cases 1-8. The PDSCH reception scheduled by the DCI message may include a PUCCH spatial relation activation / deactivation MAC CE.

[0198] In action 608, the UE applies one of the first PUCCH configuration and the second PUCCH configuration according to the priority indicator to transmit HARQ-ACK information associated with the PDSCH reception in the first UL BWP. The first PUCCH configuration corresponds to a low priority, and the second PUCCH configuration corresponds to a high priority. For example, when determining that the priority indicator in the DCI message indicates a low priority, the UE can apply the first PUCCH configuration to transmit the eMBB HARQ-ACK codebook; when determining that the priority indicator in the DCI message indicates a high priority, the UE can apply the second PUCCH configuration to transmit the URLLC HARQ-ACK codebook.

[0199] In one embodiment, in operation 608, the UE may simultaneously generate first HARQ-ACK information corresponding to a first PUCCH configuration and second HARQ-ACK information corresponding to a second PUCCH configuration. The first HARQ-ACK information and the second HARQ-ACK information may correspond to different priorities. The UE may transmit one of the first HARQ-ACK information and the second HARQ-ACK information according to a priority indicator. The first HARQ-ACK information associated with the first PUCCH configuration may refer to a low-priority transmission, and the second HARQ-ACK information associated with the second PUCCH configuration may refer to a high-priority transmission. In one embodiment, the HARQ-ACK information transmitted in operation 608 is in response to PDSCH reception scheduled by the DCI message received in operation 606.

[0200] See Figure 1 For the PUCCH transmission 100 shown in, if the UE is instructed to generate two HARQ-ACK codebooks, namely the PUCCH resource 102 in slot #0 for eMBB HARQ-ACK transmission (e.g., low-priority PUCCH) and the PUCCH resource 104 in slot #0 for URLLC HARQ-ACK transmission (e.g., high-priority PUCCH). As disclosed in Figure 5 In operations 502 and 504 shown in, since the first set of PUCCH resource IDs and the second set of PUCCH resource IDs do not have a common PUCCH resource ID, the PUCCH spatial relation information for the first PUCCH configuration and the PUCCH spatial relation information for the second PUCCH configuration may be configured separately.

[0201] The PUCCH spatial relation information ID for the eMBB HARQ-ACK codebook (PUCCH resource 102) may be independent of the PUCCH spatial relation information ID for the URLLC HARQ-ACK codebook (PUCCH resource 104). Therefore, even if the PUCCH resource 102 and the PUCCH resource 104 are scheduled in the same slot, the UE can apply different PUCCH spatial relation information to the PUCCH resource 102 and the PUCCH resource 104.

[0202] See Figure 1 For the PUCCH transmission 100 shown in, the PUCCH resource 102 in slot #0 is used for eMBB HARQ-ACK transmission (e.g., low-priority PUCCH), and the PUCCH resource 112 in slot #1 is used for URLLC HARQ-ACK transmission (e.g., high-priority PUCCH). As in Figure 5As disclosed in operations 502 and 504 shown, since the first PUCCH resource ID set and the second PUCCH resource ID set do not have a common PUCCH resource ID, the PUCCH spatial relation information for the first PUCCH configuration and the PUCCH spatial relation information for the second PUCCH configuration can be configured separately.

[0203] The PUCCH spatial relation information ID for the eMBB HARQ-ACK codebook (PUCCH resource 102) can be independent of the PUCCH spatial relation information ID for the URLLC HARQ-ACK codebook (PUCCH resource 112). Therefore, even if PUCCH resource 102 and PUCCH resource 112 are separated by only 1 time slot, the UE can apply different PUCCH spatial relation information to PUCCH resource 102 and PUCCH resource 112.

[0204] All embodiments in this disclosure are not limited to solving the problems identified in this disclosure. For example, the disclosed embodiments can be applied to solve any problems existing in the RAN of a cellular wireless communication system.

[0205] All the numbers in the embodiments of this disclosure are merely exemplary and not restrictive. The numbers are provided as examples to better illustrate how the method is executed.

[0206] Figure 7 is a block diagram of a node 700 for wireless communication according to an exemplary embodiment of the present disclosure. As Figure 7 shown, node 700 may include a transceiver 720, a processor 728, a memory 734, one or more presentation components 738, and at least one antenna 736. Node 700 may also include a radio frequency (RF) spectrum band module, a base station communication module, a network communication module, a system communication management module, an input / output (I / O) port, an I / O component, or a power supply (not Figure 7 shown).

[0207] Each component may communicate with each other directly or indirectly through one or more buses 740. Node 700 may be a UE or a BS that performs various functions disclosed with reference to Figures 1 to 6 the present disclosure.

[0208] A transceiver 720 having a transmitter 722 (e.g., a transmitting / transmission circuit) and a receiver 724 (e.g., a receiving / reception circuit) may be configured to transmit and / or receive time and / or frequency resource partitioning information. The transceiver 720 may 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 720 may be configured to receive data and control channels.

[0209] Node 700 may include a variety of computer-readable media. Computer-readable media can be any available media accessible by node 700 and includes both volatile (and non-volatile) media, removable (and non-removable) media.

[0210] Computer-readable media may include computer storage media and communication media. Computer storage media includes both volatile and non-volatile media, removable and non-removable media, implemented in any method or technology for information such as computer-readable instructions, data structures, program modules, or data.

[0211] Computer storage media includes RAM, ROM, EEPROM, flash memory (or other storage technologies), CD-ROM, digital versatile disc (DVD), or other optical disc storage devices, magnetic tape cartridges, tapes, magnetic disk storage, or other magnetic storage devices. Computer storage media does not include propagated data signals. Communication media may typically include computer-readable instructions, data structures, program modules, or other data in a modulated data signal (such as a carrier wave or other transmission mechanism) and includes any information delivery media.

[0212] The term "modulated data signal" refers to a signal having one or more characteristics set or changed in such a manner as to encode information in the signal. Communication media includes wired media (such as a wired network or a direct wired connection) and wireless media (such as acoustic, RF, infrared, and other wireless media). A combination of any of the previously listed components should also be included within the scope of computer-readable media.

[0213] Memory 734 may include computer storage media in the form of volatile and / or non-volatile memory. Memory 734 may be removable, non-removable, or a combination thereof. Exemplary memories may include solid-state memory, hard disk drives, optical disk drives, etc.

[0214] As Figure 7As shown, the memory 734 may store computer-readable and computer-executable instructions 732 (e.g., software code), and the instructions 632 are configured to cause the processor 728 to perform various functions disclosed herein when executed, with reference to Figures 1 to 6 . Optionally, the instructions 732 may not be directly executed by the processor 728, but are configured to cause the node 700 (e.g., when compiled and executed) to perform various functions disclosed herein.

[0215] The processor 728 (e.g., having processing circuitry) may include intelligent hardware devices, such as a central processing unit (CPU), a microcontroller, an ASIC, etc. The processor 728 may include a memory. The processor 728 may process data 730 and instructions 732 received from the memory 734, as well as information transmitted and received through the transceiver 720, the baseband communication module, and / or the network communication module. The processor 728 may also process information to be sent to the transceiver 720 for transmission through the antenna 736, and information to be sent to the network communication module for transmission to the core network.

[0216] One or more presentation components 738 may present data indications to a person or other device. Examples of the presentation component 738 may include a display device, a speaker, a printing component, a vibrating component, etc.

[0217] According to the present disclosure, it is obvious that various techniques may be utilized to implement the concepts of the present disclosure without departing from the scope of these concepts. In addition, although the concepts have been disclosed by specifically referring to certain embodiments, those skilled in the art may recognize that changes may be made in form and detail without departing from the scope of these concepts. Therefore, the disclosed embodiments should be considered illustrative rather than restrictive in all respects. It should also be understood that the present disclosure is not limited to the specific embodiments disclosed, and many rearrangements, modifications, and substitutions are possible without departing from the scope of the present disclosure.

Claims

1. A user equipment (UE) for configuring physical uplink control channel (PUCCH) resources, the UE comprising: at least one processor; and at least one memory coupled to the at least one processor, wherein the at least one memory stores computer-executable programs, and the computer-executable programs, when executed by the at least one processor, cause the UE to: receive a first bandwidth part (BWP) configuration associated with a first uplink (UL) BWP, the first BWP configuration including a PUCCH configuration list having a first PUCCH configuration and a second PUCCH configuration, the first PUCCH configuration indicating a first set of PUCCH resource identifier (ID), and the second PUCCH configuration indicating a second set of PUCCH resource IDs; and receive a second BWP configuration associated with a second UL BWP, the second BWP configuration including a third PUCCH configuration, the third PUCCH configuration indicating a third set of PUCCH resource IDs, wherein: the first PUCCH configuration corresponds to a low priority; the second PUCCH configuration corresponds to a high priority; a first PUCCH resource corresponds to a PUCCH resource ID selected from the first set of PUCCH resource IDs for transmitting a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook associated with the first PUCCH configuration; a second PUCCH resource corresponds to a PUCCH resource ID selected from the second set of PUCCH resource IDs for transmitting a second HARQ-ACK codebook associated with the second PUCCH configuration; the first set of PUCCH resource IDs and the second set of PUCCH resource IDs do not have a common PUCCH resource ID; and the first set of PUCCH resource IDs shares at least one PUCCH resource ID with the third set of PUCCH resource IDs.

2. The UE according to claim 1, wherein the first PUCCH configuration and the second PUCCH configuration correspond to different service types.

3. The UE according to claim 1, wherein the first PUCCH configuration further indicates a first set of PUCCH spatial relation information IDs; and the second PUCCH configuration further indicates a second set of PUCCH spatial relation information IDs.

4. The UE according to claim 1, wherein The computer-executable programs, when executed by the at least one processor, further cause the UE to: receive a downlink control information (DCI) message scheduling the reception of a physical downlink shared channel (PDSCH), the DCI message including a priority indicator; and apply one of the first PUCCH configuration and the second PUCCH configuration according to the priority indicator to transmit hybrid automatic repeat request acknowledgement (HARQ-ACK) information associated with the PDSCH reception on the first UL BWP.

5. A method for configuring physical uplink control channel (PUCCH) resources performed by a user equipment (UE), the method comprising: Receive a first BWP configuration associated with a first uplink (UL) bandwidth part (BWP), the first BWP configuration including a list of physical uplink control channel (PUCCH) configurations having a first PUCCH configuration and a second PUCCH configuration, the first PUCCH configuration indicating a first set of PUCCH resource identifier (ID) and the second PUCCH configuration indicating a second set of PUCCH resource IDs; And Receive a second BWP configuration associated with a second UL BWP, the second BWP configuration including a third PUCCH configuration, the third PUCCH configuration indicating a third set of PUCCH resource IDs, Wherein: The first PUCCH configuration corresponds to a low priority, The second PUCCH configuration corresponds to a high priority, A first PUCCH resource corresponds to a PUCCH resource ID selected from the first set of PUCCH resource IDs for transmitting a first hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook associated with the first PUCCH configuration, A second PUCCH resource corresponds to a PUCCH resource ID selected from the second set of PUCCH resource IDs for transmitting a second HARQ-ACK codebook associated with the second PUCCH configuration, The first set of PUCCH resource IDs and the second set of PUCCH resource IDs do not have a common PUCCH resource ID, and The first set of PUCCH resource IDs shares at least one PUCCH resource ID with the third set of PUCCH resource IDs.

6. The method according to claim 5, wherein The first PUCCH configuration and the second PUCCH configuration correspond to different service types.

7. The method according to claim 5, wherein The first PUCCH configuration further indicates a first set of PUCCH spatial relation information IDs; and The second PUCCH configuration further indicates a second set of PUCCH spatial relation information IDs.

8. The method according to claim 5, further comprising: Receiving a downlink control information (DCI) message for scheduling a physical downlink shared channel (PDSCH) reception, the DCI message including a priority indicator; And Applying one of the first PUCCH configuration and the second PUCCH configuration according to the priority indicator to transmit hybrid automatic repeat request acknowledgement (HARQ-ACK) information associated with the PDSCH reception on the first UL BWP.

Images