Method performed by a user equipment and user equipment

Abstract

According to the application, a method executed by a user equipment is provided, characterized in that it comprises: acquiring configuration information related to a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook, including one or more of parameters pdsch-HARQ-ACK-Codebook, pdsch-HARQ-ACK-Codebook-r16 and pdsch-HARQ-ACK-CodebookList-r16, and determining the type of a first HARQ-ACK codebook related to a straight line (SL) transmission according to the configuration information related to the HARQ-ACK codebook. Wherein, if a first type condition is met, the type of the first HARQ-ACK codebook is determined as "type-1". And if a second type condition is met, the type of the first HARQ-ACK codebook is determined as "type-2".

Description

TECHNICAL FIELD

[0001] The present application relates to a method performed by a user equipment and a user equipment. BACKGROUND

[0002] In 5G V2X (see Non-Patent Literature 4), in resource allocation mode 1, UE can report HARQ-ACK information related to SL transmission through uplink resource (e.g. PUCCH resource). How to determine the corresponding HARQ-ACK codebook of the HARQ-ACK information is a problem to be solved.

[0003] PRIOR ART DOCUMENTS

[0004] NON-PATENT LITERATURE

[0005] Non-Patent Literature 1: RP-152293, New WI proposal: Support for V2V services based on LTE sidelink

[0006] Non-Patent Literature 2: RP-170798, New WID on 3GPP V2X Phase 2

[0007] Non-Patent Literature 3: RP-170855, New WID on New Radio Access Technology

[0008] Non-Patent Literature 4: RP-190766, New WID on 5G V2X with NR sidelink SUMMARY

[0009] In order to solve at least part of the above problems, the present application provides a method performed by a user equipment and a user equipment, by determining the HARQ-ACK codebook related to SL transmission according to the configuration information related to the HARQ-ACK codebook, so that the same set of parameters related to the HARQ-ACK codebook can be used to determine the HARQ-ACK codebook related to DL transmission and the HARQ-ACK codebook related to SL transmission, improving the efficiency of system parameter configuration.

[0010] According to the application, a method performed by a user equipment is provided, comprising: obtaining configuration information related to a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook, including one or more of parameters pdsch-HARQ-ACK-Codebook, pdsch-HARQ-ACK-Codebook-r16 and pdsch-HARQ-ACK-CodebookList-r16, and determining a type of a first HARQ-ACK codebook related to a sidelink (SL) transmission according to the configuration information related to the HARQ-ACK codebook. Wherein, if a first type condition is met, the type of the first HARQ-ACK codebook is determined as "type-1". And, if a second type condition is met, the type of the first HARQ-ACK codebook is determined as "type-2".

[0011] Preferably, the first type condition is that the parameter pdsch-HARQ-ACK-Codebook or pdsch-HARQ-ACK-Codebook-r16 or pdsch-HARQ-ACK-CodebookList-r16 (one of the three is applicable) is configured with a value of only "semiStatic".

[0012] Preferably, the second type condition is that the parameter pdsch-HARQ-ACK-Codebook or pdsch-HARQ-ACK-Codebook-r16 or pdsch-HARQ-ACK-CodebookList-r16 (one of the three is applicable) is configured with a value of at least one not "semiStatic".

[0013] In addition, according to the application, a user equipment is provided, comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the above-mentioned method.

[0014] Therefore, the application provides a method, by determining the HARQ-ACK codebook related to the SL transmission according to the configuration information related to the HARQ-ACK codebook, the same set of parameters related to the HARQ-ACK codebook can be used to determine the HARQ-ACK codebook related to the DL transmission and the HARQ-ACK codebook related to the SL transmission, improving the efficiency of system parameter configuration. BRIEF DESCRIPTION OF DRAWINGS

[0015] The above and other features of the present application will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which:

[0016] Figure 1is a flow chart illustrating a method performed by a user equipment according to an embodiment of the present application.

[0017] Figure 2 is a block diagram illustrating a user equipment UE to which the present application pertains. DETAILED DESCRIPTION

[0018] The present application will now be described in detail with reference to the accompanying drawings and specific embodiments. It should be noted that the present application should not be limited to the specific embodiments described below. In addition, for the sake of brevity, detailed descriptions of well-known technology related to the present application will be omitted so as not to obscure the understanding of the present application.

[0019] The following describes in detail a plurality of embodiments according to the present application, taking a 5G mobile communication system and its subsequent evolved versions as an example application environment. However, it should be noted that the present application is not limited to the following embodiments, but can be applied to more other wireless communication systems, such as 5G after the communication system and 4G mobile communication system before 5G, etc.

[0020] The following describes some terms related to the present application. If not specifically stated, the terms related to the present application are defined herein. The terms given in the present application can be named differently in LTE, LTE-Advanced, LTE-Advanced Pro, NR and subsequent communication systems, but uniform terms are used in the present application, and when applied to a specific system, the terms used in the corresponding system can be replaced.

[0021] 3GPP: 3rd Generation Partnership Project, 3rd Generation Partnership Project

[0022] AGC: Automatic Gain Control, Automatic Gain Control

[0023] AL: Aggregation Level, Aggregation Level

[0024] AMF: Access and Mobility Management Function, Access and Mobility Management Function

[0025] AS: Access Stratum, Access Stratum

[0026] BWP: Bandwidth Part, Bandwidth Part

[0027] CA: Carrier Aggregation, Carrier Aggregation

[0028] CBR: Channel Busy Ratio

[0029] CCE: control-channel element

[0030] CORESET: control-resource set

[0031] CP: Cyclic Prefix

[0032] CP-OFDM: Cyclic Prefix Orthogonal Frequency Division Multiplexing

[0033] CRB: Common Resource Block

[0034] CRC: Cyclic Redundancy Check

[0035] CSI: Channel-state Information

[0036] CSS: Common Search Space

[0037] DC: Dual Connectivity

[0038] DCI: Downlink Control Information

[0039] DFN: Direct Frame Number

[0040] DFT-s-OFDM: Discrete Fourier Transformation Spread Orthogonal Frequency Division Multiplexing

[0041] DL: Downlink

[0042] DL-SCH: Downlink Shared Channel

[0043] DM-RS: Demodulation reference signal, also known as DMRS

[0044] eMBB: Enhanced Mobile Broadband

[0045] eNB: E-UTRAN Node B

[0046] E-UTRAN: Evolved UMTS Terrestrial Radio Access Network

[0047] FDD: Frequency Division Duplex

[0048] FDRA: Frequency Domain Resource Assignment

[0049] FR1: Frequency Range 1

[0050] FR2: Frequency Range 1

[0051] GLONASS: GLObal NAvigation Satellite System

[0052] gNB: NR Node B

[0053] GNSS: Global Navigation Satellite System

[0054] GPS: Global Positioning System

[0055] HARQ: Hybrid Automatic Repeat Request

[0056] HARQ-ACK: HARQ Acknowledgement

[0057] ID: Identity (or Identifier)

[0058] IE: Information Element

[0059] IP: Internet Protocol

[0060] LCID: Logical Channel ID

[0061] LSB: Least Significant Bit

[0062] LTE: Long Term Evolution

[0063] LTE-A: Long Term Evolution-Advanced

[0064] MAC: Medium Access Control

[0065] MAC CE: MAC Control Element

[0066] MCG: Master Cell Group

[0067] MIB: Master Information Block

[0068] MIB-SL: Master Information Block-Sidelink

[0069] MIB-SL-V2X: Master Information Block-Sidelink-V2X

[0070] MIB-V2X: Master Information Block-V2X

[0071] MME: Mobility Management Entity

[0072] MSB: Most Significant Bit

[0073] mMTC: massive Machine Type Communication

[0074] NAS: Non-Access-Stratum, non-access stratum

[0075] NDI: New Data Indicator, new data indicator

[0076] NR: New Radio, new radio

[0077] NUL: Normal Uplink, normal uplink

[0078] OFDM: Orthogonal Frequency Division Multiplexing, orthogonal frequency division multiplexing

[0079] PBCH: Physical Broadcast Channel, physical broadcast channel

[0080] PDCCH: Physical Downlink Control Channel, physical downlink control channel

[0081] PDCP: Packet Data Convergence Protocol, packet data convergence protocol

[0082] PDSCH: Physical Downlink Shared Channel, physical downlink shared channel

[0083] PSBCH: Physical Sidelink Broadcast Channel, physical sidelink broadcast channel

[0084] PSCCH: Physical Sidelink Control Channel, physical sidelink control channel

[0085] PSFCH: Physical Sidelink Feedback Channel, physical sidelink feedback channel

[0086] PSSCH: Physical Sidelink Shared Channel, physical sidelink shared channel

[0087] PRB: Physical Resource Block, physical resource block

[0088] PSS: Primary Synchronization Signal, primary synchronization signal

[0089] PSS-SL: Primary Synchronization Signal for Sidelink

[0090] PSSS: Primary Sidelink Synchronization Signal

[0091] PTAG: Primary Timing Advance Group

[0092] PUSCH: Physical uplink shared channel

[0093] PUCCH: Physical uplink control channel

[0094] QCL: Quasi co-location

[0095] QoS: Quality of Service

[0096] QZSS: Quasi-Zenith Satellite System

[0097] RAR: Random Access Response

[0098] RB: Resource Block

[0099] RE: Resource Element

[0100] REG: resource-element group

[0101] RF: Radio Frequency

[0102] RLC: Radio Link Control

[0103] RNTI: Radio-Network Temporary Identifier

[0104] RRC: Radio Resource Control

[0105] RV: Redundancy Version

[0106] S-BWP: Sidelink Bandwidth Part

[0107] S-MIB: Sidelink Master Information Block

[0108] S-PSS: Sidelink Primary Synchronization Signal

[0109] S-SSB: Sidelink SS / PBCH block

[0110] S-SSS: Sidelink Secondary Synchronization Signal

[0111] SCG: Secondary Cell Group

[0112] SCI: Sidelink Control Information

[0113] SCS: Subcarrier Spacing

[0114] SDAP: Service Data Adaptation Protocol

[0115] SFN: System Frame Number

[0116] SIB: System Information Block

[0117] SL: Sidelink

[0118] SL BWP: Sidelink Bandwidth Part

[0119] SL MIB: Sidelink Master Information Block

[0120] SL PSS: Sidelink Primary Synchronization Signal

[0121] SL SS: Sidelink Synchronisation Signal

[0122] SL SSID: Sidelink Synchronization Signal Identity (or Sidelink Synchronization Signal Identifier)

[0123] SL SSB: Sidelink SS / PBCH block

[0124] SL SSS: Sidelink Secondary Synchronization Signal

[0125] SL-SCH: Sidelink Shared Channel

[0126] SLSS: Sidelink Synchronisation Signal

[0127] SLSS ID: Sidelink Synchronization Signal Identity (or Sidelink Synchronization Signal Identifier)

[0128] SLSSID: Sidelink Synchronization Signal Identity (or Sidelink Synchronization Signal Identifier)

[0129] SpCell: Special Cell

[0130] SRS: Sounding Reference Signal

[0131] SSB: SS / PBCH block

[0132] SSB-SL: SS / PBCH block for Sidelink

[0133] SSS: Secondary Synchronization Signal

[0134] SSS-SL: Secondary Synchronization Signal for Sidelink

[0135] SSSB: Sidelink SS / PBCH block

[0136] SSSS: Secondary Sidelink Synchronization Signal

[0137] STAG: Secondary Timing Advance Group

[0138] Sub-channel: sub-channel

[0139] SUL: Supplementary Uplink

[0140] S-GW: Serving Gateway

[0141] TA: Timing Advance

[0142] TAG: Timing Advance Group

[0143] TB: Transport Block

[0144] TCP: Transmission Control Protocol

[0145] TDD: Time Division Duplex

[0146] TPC: Transmit power control

[0147] UE: User Equipment

[0148] UL: Uplink

[0149] UMTS: Universal Mobile Telecommunications System

[0150] UPF: User Plane Function

[0151] URLLC: Ultra-Reliable and Low Latency Communication

[0152] USS: UE-specific Search Space

[0153] V2I: Vehicle-to-Infrastructure

[0154] V2N: Vehicle-to-network

[0155] V2P: Vehicle-to-Pedestrian

[0156] V2V: Vehicle-to-vehicle

[0157] V2X: Vehicle-to-everything

[0158] VRB: Virtual Resource Block

[0159] In all embodiments and implementations of the present application, unless specifically stated otherwise:

[0160] • Optionally, a parameter z defined in one information element I can also be referred to as a "data unit" (or "field") in said information element I, accordingly, the information element Z corresponding to said parameter z can also be referred to as the type of said "data unit" (or "field") z.

[0161] • Optionally, a sequence x(0), x(1),..., x(N-1) of N elements can be simply written as x(0),..., x(N-1) if it is clear from the context.

[0162] • Optionally, a sequence of N elements has a length of N (or in other words, a size of N).

[0163] • Optionally, “V2X communication”, “V2X SL communication” and “SL V2X communication” can be interchangeable, where applicable.

[0164] • Optionally, “V2X communication” can be NR SL based V2X communication, where applicable.

[0165] • Optionally, “V2X communication” can be LTE SL based V2X communication, where applicable.

[0166] • Optionally, it can be considered that one DL carrier, one UL carrier and, optionally, one SUL carrier can be configured in one TDD cell, where the context is clear. The UL carrier can also be referred to as “non-SUL carrier”.

[0167] • Optionally, it can be considered that the “non-SUL carrier” is a kind of “UL carrier” in one TDD cell, where the context is clear. For example, one TDD cell can be configured with one UL carrier, which is referred to as “non-SUL carrier”. For another example, one TDD cell can be configured with two UL carriers, one of which is “non-SUL carrier” and the other is “SUL carrier”.

[0168] • Optionally, “sending” and “transmitting” can be interchangeable, where applicable.

[0169] • Optionally, any two of “in XX”, “in XX” and “on XX” can be interchangeable, where applicable. XX can be one or more carriers (e.g. SL carrier), or one or more BWPs (e.g. SL BWP), or one or more resource pools, or one or more links (e.g. UL, and DL, and SL), or one or more channels (e.g. PSSCH), or one or more sub-channels, or one or more RBGs, or one RB, etc.

[0170] • Optionally, if S1 is a set, a subset of S1 can be a set of zero or one or more (including all) elements in S1.

[0171] • Optionally, if S1 and S2 are two sets, S1-S2 represents the “difference set” of set S1 and set S2, i.e. the set of elements in set S1 that do not belong to set S2.

[0172] • Optionally, if S1 and S2 are two sets, S1-S2 = {x | x ∈ S1 and x ∉ S2}.

[0173] ​• Optionally, operating on (e.g., filtering, transforming, etc.) elements in set S1 to obtain set S2 can be equivalent to operating directly on the original set S1 to obtain an updated set S1.

[0174] • Optionally, “higher layer” can refer to one or more protocol layers or protocol sub-layers above the physical layer. For example, MAC layer, or RLC layer, or PDCP layer, or PC5 RRC layer, or PC5-S layer, or RRC layer, or V2X layer, or application layer, or V2X application layer, etc.

[0175] • Optionally, “pre-configure” can be pre-configure through higher layer protocol / signaling. For example, pre-configure (e.g., pre-configure according to the specification of the higher layer protocol) in a specific storage location in the UE, or pre-configure (e.g., pre-configure according to the specification of the higher layer protocol) in a specific storage location accessible by the UE.

[0176] • Optionally, “configure” can be configure through higher layer protocol / signaling. For example, configure for the UE through RRC signaling.

[0177] • Optionally, “configured” can be replaced by “pre-configured”.

[0178] • Optionally, “configured” can be replaced by “configured or pre-configured”.

[0179] • Optionally, “configured with a parameter” can be replaced by “provided with a parameter”.

[0180] • Optionally, “configured with a parameter” can be replaced by “signaled with a parameter”.

[0181] • Optionally, “not configured” can be replaced by “not pre-configured”.

[0182] • Optionally, “not configured” can be replaced by “not configured and / or not pre-configured”.

[0183] • Optionally, “not configured” can be replaced by “not (pre-)configured”.

[0184] • Optionally, the suffix “-r8”, “-r9”, “-r10”, “-r11”, “-r12”, “-r13”, “-r14”, “-r15”, “-r16”, etc. in the parameter name can be removed if the context is clear. For example, “pdsch-HARQ-ACK-CodebookList” can be used to refer to the parameter pdsch-HARQ-ACK-CodebookList-r16.

[0185] • Optionally, a time-domain resource can also be referred to as a time resource.

[0186] • Optionally, a frequency-domain resource can also be referred to as a frequency resource.

[0187] • Optionally, a symbol refers to an OFDM symbol.

[0188] • Optionally, the number of an OFDM symbol within a slot can start from 0. For example, for normal CP, the set of numbers of OFDM symbols within a slot can be {0, 1,..., 13}. For example, for extended CP, the set of numbers of OFDM symbols within a slot can be {0, 1,..., 11}.

[0189] • Optionally, a resource block can refer to a virtual resource block (VRB), can refer to a physical resource block (PRB), can refer to a common resource block (CRB), or can refer to a resource block defined in other ways.

[0190] • Optionally, the number of a subchannel can start from 0. For example, if the number of subchannels configured in a resource pool is then the set of numbers of subchannels can be

[0191] • Optionally, the number of a subcarrier within a resource block can start from 0. For example, the set of numbers of subcarriers within a resource block can be {0, 1,..., 11}.

[0192] • Optionally, the value of a parameter (e.g., an RRC parameter) with a size of L bits can be represented by an integer value (e.g., 0, 1, 2, etc.) or by a bit string corresponding to the integer. For example, the bit string can have a length of L (e.g., ‘b0b1...b L-1 ’).

[0193] • Optionally, in the bit string ‘b0b1...b L-1 ’, the first (i.e., leftmost) bit (i.e., b0) is the most significant bit, and the last (i.e., rightmost) bit (i.e., b L-1) is the least significant bit. For example, if L = 3 and the value of the parameter is represented by the bit string ‘011’, the value of the most significant bit of the parameter is 0, and the integer value corresponding to the parameter is 3.

[0194] ◆ Optionally, in the bit string ‘b0b1...b L-1 ’ the first (i.e. leftmost) bit (i.e. b0) is the least significant bit, and the last (i.e. rightmost) bit (i.e. b L-1 ) is the most significant bit. For example, if L = 3 and the value of the parameter is represented by the bit string ‘011’, the value of the least significant bit of the parameter is 0, and the integer value corresponding to the parameter is 6.

[0195] In D2D (Device to Device) technology based communication, the interface between devices (also referred to as User Equipment, UE) can be referred to as PC5 interface, and the corresponding transmission link can be referred to as “straight” or “sidelink” (SL) link in the physical layer, to distinguish from uplink (UL) link and downlink (DL) link. SL link based communication can be referred to as SL communication. LTE technology based SL link can be referred to as LTE SL link. NR technology based SL link can be referred to as NR SL link. 5G V2X communication can be based on LTE SL or NR SL. In the following, unless otherwise specified, “SL” refers to NR SL, and “SL communication” refers to NR SL communication.

[0196] The physical layer of the SL link can support one or more modes of transmission, such as broadcast transmission, groupcast transmission, unicast transmission, etc., in one or more of the following scenarios: in-coverage, out-of-coverage, and partial-coverage scenarios.

[0197] The SCS (subcarrier spacing, denoted as Δf, in kHz) for a SL link corresponding to FR1 (Frequency Range 1) can be 15 kHz (normal CP), or 30 kHz (normal CP), or 60 kHz (normal CP or extended CP); the SCS for a SL link corresponding to FR2 (Frequency Range 2) can be 60 kHz (normal CP or extended CP), or 120 kHz (normal CP). Each SCS corresponds to one SCS configuration (denoted as μ) respectively, for example, Δf = 15 kHz corresponds to μ = 0, Δf = 30 kHz corresponds to μ = 1, Δf = 60 kHz corresponds to μ = 2, Δf = 120 kHz corresponds to μ = 3, and so on; for another example, for any given μ, Δf = 2 μ 15 kHz. μ can be the SCS configuration of a SL carrier; for example, all SL transmissions in one SL carrier use the same SCS configuration and / or the same CP. μ can be the SCS configuration of a SL BWP (Sidelink Bandwidth Part, or S-BWP, or SBWP, or SL-BWP, or BWP-SL, or BWP for short); for example, all SL transmissions in one SL BWP use the same SCS configuration and / or the same CP. μ can be the SCS configuration of a resource pool; for example, all SL transmissions in one resource pool use the same SCS configuration and / or the same CP.

[0198] The signals and channels related to SL operation can include:

[0199] SL PSS (Sidelink Primary Synchronization Signal), or S-PSS, or SPSS, or SL-PSS, or PSS-SL, or PSSS (Primary Sidelink Synchronization Signal), and so on.

[0200] • SL SSS (Sidelink Secondary Synchronization Signal), or S-SSS, or SSSS (Sidelink Secondary Synchronization Signal), or SL-SSS, or SSS-SL, or SSSS (Secondary Sidelink Synchronization Signal), etc.

[0201] • PSBCH (Physical Sidelink Broadcast Channel).

[0202] • PSCCH (Physical Sidelink Control Channel).

[0203] • PSSCH (Physical Sidelink Shared Channel).

[0204] • PSFCH (Physical Sidelink Feedback Channel).

[0205] SL PSS, SL SSS and PSBCH together can be organized in a block-like form on time / frequency resources, e.g., referred to as S-SSB (Sidelink Synchronization Signal / PSBCH block, or SSS / PSBCH block, or SS / PSBCH block, or S-SS / PSBCH block, or SL SSB, or SSSB, or SL-SSB, or SSB-SL). The transmission bandwidth of a S-SSB (e.g., 11 resource blocks) can be located within a corresponding SL carrier (e.g., within a configured SL BWP of the SL carrier). SL PSS and / or SL SSS can carry a SL SSID (Sidelink Synchronization Identity, or Sidelink Synchronization Identifier, or Sidelink Synchronization Signal Identity, or Sidelink Synchronization Signal Identifier, or referred to as SL-SSID, or SSID-SL, or SLSSID, or SLSS ID, or S-SSID, etc.), and PSBCH can carry a SL MIB (Sidelink Master Information Block, or SL-MIB, or S-MIB, or MIB-SL, or Master Information Block Sidelink), e.g., configured by parameter masterInformationBlockSidelink.

[0206] On a SL link, the time and / or frequency domain resources used for transmission of a S-SSB can be configured by higher layer parameters. For example, in frequency domain, the location of a S-SSB in frequency domain can be configured by parameter absoluteFrequencySSB-SL (or parameter sl-AbsoluteFrequencySSB). For another example, in time domain, one or more synchronization configuration entries can be configured by parameter sl-SyncConfigList, and in each synchronization configuration entry, the number of S-SSBs within a S-SSB period of 16 frames can be configured by parameter numSSBwithinPeriod-SL (or parameter sl-NumSSB-WithinPeriod). one S-SSB, where the number (or index) is The index of the slot where the S-SSB of where may be configured by the parameter timeOffsetSSB-SL (or the parameter sl-TimeOffsetSSB), may be configured by the parameter timeIntervalSSB-SL (or the parameter sl-TimeInterval).

[0207] Sometimes, the time-domain and / or frequency-domain resources configured for an S-SSB in a SL carrier can be considered as corresponding to a candidate S-SSB (or S-SSB candidate). On the time-domain and / or frequency-domain resources corresponding to one candidate S-SSB, there can be one or more S-SSB transmissions (e.g., from different UEs, respectively) or there can be no S-SSB transmission.

[0208] Sometimes, a slot configured with an S-SSB (or configured with S-SSB resources, or configured with a candidate S-SSB, or configured with candidate S-SSB resources) can also be referred to as a slot configured with an SLSS (or configured with SLSS resources). Vice versa.

[0209] Synchronization sources (or synchronization references, or synchronization reference sources) related to SL synchronization can include GNSS (Global Navigation Satellite System), gNB, eNB, and UE (e.g., NR UE, or LTE UE, or NR UE or LTE UE). A UE (e.g., a UE transmitting an S-SSB) acting as a synchronization source can be referred to as a SyncRef UE.

[0210] Examples of GNSS can include GPS (Global Positioning System), GLONASS (GLObal NAvigation Satellite System), BeiDou, Galileo, QZSS (Quasi-Zenith Satellite System), etc.

[0211] One or more (e.g., one) SL BWP can be configured within a SL carrier. For each SL BWP, a starting symbol (e.g., denoted as ) that can be used for SL transmission can be configured by parameter startSLsymbols (or parameter sl-StartSymbol), and a number of symbols (e.g., denoted as ) that can be used for SL transmission can be configured by parameter lengthSLsymbols (or parameter sl-LengthSymbols), where the symbols can be consecutive symbols. The value set of may be denoted as The value set of may be denoted as The “symbols that can be used for SL transmission” can be referred to as “SL symbols”. Denote the set of SL symbols (in time sequence) as Then For example, if the set of SL symbols is {7, 8, 9, 10, 11, 12, 13}.

[0212] Only slots that satisfy certain conditions can be used for SL transmission. For example, at least symbol symbol …, symbol is an uplink symbol (e.g., slots that satisfy the condition are configured by tdd-UL-DL-ConfigurationCommon in servingCellConfigCommon in SIB1). For another example, the slot must be in the set of slots of one configured resource pool.

[0213] One or more resource pools can be configured within a SL BWP, where in each resource pool,

[0214] • In frequency domain, the location of the starting resource block of the starting subchannel of the resource pool within the SL BWP can be configured by parameter startRB-Subchannel (or parameter sl-StartRB-Subchannel).

[0215] • In frequency domain, each subchannel can consist of one or more resource blocks, and the specific number of resource blocks (referred to as the size of the subchannel, for example, denoted as n subChannelSize ) can be configured by parameter subchannelsize (or parameter sl-SubchannelSize). The n subChannelsize resource blocks can be consecutive in frequency domain.

[0216] • In frequency domain, the number of subchannels (denoted as ) occupied by the resource pool can be configured by parameter numSubchannel (or parameter sl-NumSubchannel). The subchannels can be consecutive in frequency domain.

[0217] • In frequency domain, the number of PRBs (denoted as ) occupied by the resource pool can be configured by parameter sl-RB-Number. Optionally, the UE can assume that the last PRBs of the PRBs are not used.

[0218] • In frequency domain, the subchannels within a resource pool can be numbered as 0, 1, …, in ascending order of frequency, respectively, where the subchannel numbered i can be referred to as “subchannel i”

[0219] • In time domain, one or more time slots (for example, in the form of a time slot bitmap) that can be used for (or belong to) the resource pool can be configured by parameter timeresourcepool (or parameter sl-TimeResource), where the size of the period can be a predefined value, or configured by parameter periodResourcePool (or parameter sl-Period).

[0220] The allocation mode of the resources (for example, time domain resources, for example, frequency domain resources, for example, code domain resources) related to SL operation can be classified as follows:

[0221] • Mode 1: The base station schedules SL resources for SL transmission.

[0222] • Mode 2: UE determines SL resources for SL transmission (i.e., base station does not participate in scheduling of SL resources). For example, a UE performing SL transmission operation autonomously determines SL resources for SL transmission.

[0223] A UE can schedule transmission of data through SCI (Sidelink Control Information). SL operation can support “two-stage SCI”, where a first stage SCI (1 st -stage SCI) can contain information such as resource reservation and / or resource allocation, to facilitate sensing by all UEs that are monitoring the SL link, for resource reservation and / or resource allocation; a second stage SCI (2 nd -stage SCI) can contain other information, such as information related to HARQ feedback, etc. Hereinafter, unless specifically stated otherwise, when referring to “SCI” alone, it can refer to first stage SCI, or second stage SCI, or both first stage SCI and second stage SCI, as applicable.

[0224] The format of first stage SCI can be SCI format 1-A (or written as “SCI format 1_A”). Below are some examples of information that can be contained in SCI format 1-A:

[0225] • Priority.

[0226] • Frequency resource assignment.

[0227] • Time resource assignment.

[0228] • Resource reservation period.

[0229] • DMRS pattern.

[0230] • Second stage SCI format (2 nd -stage SCI format).

[0231] The format of second stage SCI can be SCI format 2-A (or written as “SCI format 2_A”), or SCI format 2-B (or written as “SCI format 2_B”). Below are some examples of information that can be contained in SCI format 2-A and / or SCI format 2-B:

[0232] • Source Layer-1 ID (or Layer-1 Source ID, or Physical Layer Source ID, or (in context) Source ID).

[0233] • Destination Layer-1 ID (or Layer-1 Destination ID, or Physical Layer Destination ID, or (in context) Destination ID).

[0234] • HARQ Process ID (or HARQ Process Number).

[0235] • New Data Indicator (NDI).

[0236] • Redundancy Version (RV).

[0237] The first-stage SCI can be carried on a PSCCH. The second-stage SCI can be multiplexed with the data to be transmitted on a PSSCH associated with (or scheduled by) the PSCCH. The PSCCH and its associated PSSCH can be multiplexed on the time-domain and / or frequency-domain resources allocated for SL transmission in a certain manner (e.g., the starting resource block of the PSCCH is the starting subchannel of the PSSCH associated with it. For another example, the starting resource block of the PSCCH is the starting resource block of the starting subchannel of the PSSCH associated with it). In addition, it can be considered that the first-stage SCI and / or the corresponding second-stage SCI schedules the PSSCH (or schedules the transmission of the PSSCH, or schedules the transmission of the TB carried in the PSSCH).

[0238] For a specific SL transmission containing PSCCH and / or PSSCH, the sender can be referred to as the TX UE, and the receiver can be referred to as the RX UE. With HARQ feedback enabled, the RX UE can carry feedback information (e.g., "HARQ-ACK information") related to the reception of PSCCH and / or PSSCH in the PSFCH transmission. In some configurations, the HARQ-ACK information can be a positive acknowledgment (ACK), indicating that the data carried by the corresponding PSCCH and / or PSSCH can be correctly decoded, or a negative acknowledgment (NACK, or NAK, Negative Acknowledgment), indicating that the data carried by the corresponding PSCCH and / or PSSCH cannot be correctly decoded. In other configurations, the HARQ-ACK information can simply be a NACK (e.g., no HARQ-ACK information is sent when the data carried by the corresponding PSCCH and / or PSSCH can be correctly decoded; a NACK is sent when the data carried by the corresponding PSCCH and / or PSSCH cannot be correctly decoded). HARQ-ACK feedback can be applied to multicast transmissions or unicast transmissions.

[0239] In the time domain, PSFCH resources can appear periodically in a resource pool, for example, a corresponding period (e.g., called a "PSFCH period" or "PSFCH resource period," denoted as...). For example, the unit (number of time slots) can be configured through the parameter periodPSFCHresource (or the parameter sl-PSFCH-Period). For example For example ). This can be used to indicate that no PSFCH resources are configured in the corresponding resource pool, and / or to indicate that HARQ feedback is disabled in the corresponding resource pool. For example, if a resource pool does not configure PSFCH-related parameters (e.g., parameters configured via sl-PSFCH-Config) or the PSFCH period configured in sl-PSFCH-Config is 0, it indicates that the resource pool has no PSFCH resources configured. Conversely, if a resource pool has configured the parameter sl-PSFCH-Config and the PSFCH period configured in sl-PSFCH-Config is greater than 0 slots, it indicates that the resource pool has PSFCH resources configured.

[0240] In the frequency domain, PSFCH resources can be configured in a set of RBs (e.g., a set of consecutive PRBs, or a set of partially or entirely discontinuous PRBs), for example, through the parameter sl-PSFCH-RB-Set.

[0241] In resource allocation mode 1, a base station can configure one or more SL configured grants for a UE, e.g., through the parameter sl-ConfiguredGrantConfigList. Each SL configured grant can be associated with periodic resources for SL transmission, e.g., the periodicity of the resources can be configured through the parameter sl-PeriodCG. SL configured grants can be classified into SL configured grant Type-1 and SL configured grant Type-2, where the former is associated with resources that can be configured and / or activated and / or deactivated through semi-static signaling (e.g., RRC signaling), and the latter is associated with resources that can be activated and / or deactivated dynamically (e.g., through DCI).

[0242] In resource allocation mode 1, a base station can allocate one or more resources for SL transmission to a UE through DCI (e.g., DCI format 3_0). This way of resource allocation can be referred to as “dynamic grant” to distinguish from “configured grant”.

[0243] In resource allocation mode 1, a base station can indicate a UE to report HARQ-ACK information related to SL transmission (e.g., the SL transmission scheduled by the same DCI format 3_0) on a given (e.g., indicated in DCI format 3_0) uplink resource (e.g., PUCCH resource). The HARQ-ACK information can be used to feedback the transmission and / or reception status (e.g., transmission and / or reception status; or, e.g., transmission and / or reception result; or, e.g., no transmission performed; or, e.g., no reception performed; etc.) of data and / or control information on the sidelink. Specifically, the HARQ-ACK information can be from (or, said in another way, based on) one or more of the following:

[0244] • PSFCH reception (or PSFCH receptions).

[0245] • absence of PSFCH reception. For example, the UE is unable to perform the reception of PSFCH in a time slot where the UE is supposed to receive PSFCH due to performing other higher priority tasks (e.g., performing a higher priority UL transmission). For another example, the SCI scheduling a data transmission on a sidelink indicates that the UE receiving the data transmission does not need to send HARQ-ACK (e.g., HARQ-ACK carried by PSFCH). For another example, the UE does not send PSCCH and / or PSSCH due to not detecting a DCI (e.g., DCI format 3_0) scheduling the PSCCH and / or PSSCH transmission, and accordingly, there is no PSFCH to receive. For another example, there is no PSFCH resource configured in the corresponding resource pool.

[0246] • PSCCH and / or PSSCH transmission.

[0247] • TB transmission. For example, one TB carried by PSSCH.

[0248] • PSCCH and / or PSSCH reception.

[0249] • PSFCH transmission.

[0250] The UE can be configured to report the HARQ-ACK information in a Type-1 HARQ-ACK codebook or in a Type-2 HARQ-ACK codebook. The size of a Type-1 HARQ-ACK codebook can only depend on semi-static configuration information (e.g., RRC layer configuration information); the size of a Type-2 HARQ-ACK codebook can dynamically change (e.g., based on the number of DCI formats detected to be associated with the HARQ-ACK codebook, etc.), for example, the number of HARQ-ACK information bits in a Type-2 HARQ-ACK codebook transmitted on two different PUCCH slots can be different. If there is PUSCH transmission on the slot where the PUCCH resource is located, the UE can multiplex the HARQ-ACK information on the PUSCH transmission.

[0251] The HARQ-ACK information in a HARQ-ACK codebook can be associated with one or more SL configured grants.

[0252] The HARQ-ACK information within the HARQ-ACK codebook can be associated with one or more DCI formats (e.g., DCI format 3_0). Among them, each of the one or more DCI formats can be used for one or more purposes related to the data and / or control information transmitted on the sidelink, for example, including one or more of the following:

[0253] • Scheduling PSCCH and / or PSSCH transmission. At this time, optionally, the CRC of the DCI format is scrambled using SL-RNTI or SL-CS-RNTI.

[0254] • Indicating SL configured grant (e.g., SL configured grant Type-2) activation.

[0255] • Indicating SL configured grant (e.g., SL configured grant Type-2) release.

[0256] In addition, as a comparison, the UE can also report HARQ-ACK information related to DL transmission (correspondingly, using a HARQ-ACK codebook related to DL transmission) on uplink resources (e.g., PUCCH, and also e.g., PUSCH) for feeding back the transmission and / or reception status (e.g., transmission and / or reception status; and also e.g., transmission and / or reception result; and also e.g., not performing transmission; and also e.g., not performing reception; etc.) of the data and / or control information on the downlink. Specifically, these HARQ-ACK information can come from (or be based on) one or more of the following:

[0257] • PDSCH reception with corresponding PDCCH reception.

[0258] • PDSCH reception without corresponding PDCCH reception (e.g., SPS PDSCH reception).

[0259] • PDCCH reception. For example, an indication of “SPS PDSCH release” indication in the DCI carried by the PDCCH. And also e.g., an indication of “SCell dormancy” in the DCI carried by the PDCCH.

[0260] In all embodiments and implementations of the present application, unless specifically stated otherwise, “HARQ-ACK information” refers to HARQ-ACK information related to SL transmission, and “HARQ-ACK codebook” refers to a HARQ-ACK codebook containing HARQ-ACK information related to SL transmission.

[0261] [Embodiment One]

[0262] The method performed by the user equipment of embodiment one of the present application will be described below in conjunction with Figure 1 ​

[0263] Figure 1 is a flow chart showing a method performed by a user equipment according to an embodiment one of the present application.

[0264] As shown in Figure 1 , in the embodiment one of the present application, the steps performed by the user equipment UE include: step S101 and step S103.

[0265] Specifically, in step S101, configuration information related to HARQ-ACK codebook is acquired.

[0266] Optionally, the “configuration information related to HARQ-ACK codebook” can come from a base station (e.g. gNB, and e.g. eNB), can come from other UE, and can come from the UE.

[0267] Optionally, the “configuration information related to HARQ-ACK codebook” can be predefined.

[0268] Optionally, the “configuration information related to HARQ-ACK codebook” can be preconfigured.

[0269] Optionally, the “configuration information related to HARQ-ACK codebook” can be configured through signaling (e.g. between base station and UE, and e.g. between UE and UE).

[0270] Optionally, the “configuration information related to HARQ-ACK codebook” can be contained in RRC message and / or PC5 RRC message (e.g. MIB, and e.g. SIB1, and e.g. SIB12, and e.g. SIB13, and e.g. SIB14, and e.g. other SIB, and e.g. MasterInformationBlockSidelink, and e.g. other RRC message and / or PC5 RRC message).

[0271] Optionally, the “configuration information related to HARQ-ACK codebook” can be contained in MAC CE.

[0272] Optionally, the “configuration information related to HARQ-ACK codebook” can be contained in downlink control information (DCI).

[0273] Optionally, the “configuration information related to HARQ-ACK codebook” can be contained in sidelink control information (SCI).

[0274] Optionally, the “configuration information related to HARQ-ACK codebook” can include one or more parameters in the following:

[0275] • pdsch-HARQ-ACK-Codebook. Wherein,

[0276] ◆ Optionally, the parameter pdsch-HARQ-ACK-Codebook can take a value, which is one element of a set A101. Wherein, the set A101 can be one of the following:

[0277] o {semiStatic, dynamic}.

[0278] o {semiStatic, dynamic, enhancedDynamic}.

[0279] ◆ Optionally, the parameter pdsch-HARQ-ACK-Codebook can be defined in the information element PhysicalCellGroupConfig, e.g.

[0280]

[0281] • pdsch-HARQ-ACK-Codebook-r16. Wherein,

[0282] ◆ Optionally, the parameter pdsch-HARQ-ACK-Codebook-r16 can take a value, which is one element of a set A102. Wherein, the set A102 can be one of the following:

[0283] o {enhancedDynamic}.

[0284] o {semiStatic, dynamic}.

[0285] o {semiStatic, dynamic, enhancedDynamic}.

[0286] ◆ Optionally, the parameter pdsch-HARQ-ACK-Codebook-r16 can be defined in the information element PhysicalCellGroupConfig, e.g.

[0287]

[0288] • pdsch-HARQ-ACK-CodebookList-r16. Wherein,

[0289] ◆ Optionally, the parameter pdsch-HARQ-ACK-CodebookList-r16 can be defined in the information element PhysicalCellGroupConfig, e.g.

[0290]

[0291] wherein,

[0292] o Optionally, the definition of the information element PDSCH-HARQ-ACK-CodebookList-r16 can be as follows

[0293] o Optionally, the definition of the information element PDSCH-HARQ-ACK-CodebookList-r16 can be as follows

[0294] Optionally, if the parameter pdsch-HARQ-ACK-Codebook is configured, the parameter pdsch-HARQ-ACK-Codebook-r16 is ignored.

[0295] Optionally, if the parameter pdsch-HARQ-ACK-Codebook is configured, the parameter PDSCH-HARQ-ACK-CodebookList-r16 is ignored.

[0296] Optionally, if the parameter pdsch-HARQ-ACK-Codebook-r16 is configured, the parameter pdsch-HARQ-ACK-Codebook is ignored.

[0297] Optionally, if the parameter pdsch-HARQ-ACK-Codebook-r16 is configured,

[0298] • Optionally, for a HARQ-ACK codebook related to a DL transmission (e.g. when determining the type of HARQ-ACK codebook related to a DL transmission), the parameter pdsch-HARQ-ACK-Codebook is ignored.

[0299] • Optionally, for a HARQ-ACK codebook related to a SL transmission (e.g. when determining the type of HARQ-ACK codebook related to a SL transmission),

[0300] • Optionally, the parameter pdsch-HARQ-ACK-Codebook is ignored.

[0301] • Optionally, the parameter pdsch-HARQ-ACK-Codebook-r16 is ignored.

[0302] • Optionally, the parameter pdsch-HARQ-ACK-Codebook is applied.

[0303] • Optionally, apply the parameter pdsch-HARQ-ACK-Codebook-r16 if the parameter pdsch-HARQ-ACK-Codebook is not configured.

[0304] • Optionally, apply the parameter pdsch-HARQ-ACK-Codebook if the parameter pdsch-HARQ-ACK-Codebook-r16 is configured.

[0305] • Optionally, apply the parameter pdsch-HARQ-ACK-Codebook-r16 if the parameter pdsch-HARQ-ACK-Codebook is not configured.

[0306] • Optionally, ignore the parameter pdsch-HARQ-ACK-Codebook-r16 if the parameter pdsch-HARQ-ACK-Codebook-r16 is configured.

[0307] • Optionally, ignore the parameter pdsch-HARQ-ACK-Codebook if the parameter pdsch-HARQ-ACK-Codebook-r16 is configured.

[0308] • Optionally, if the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured,

[0309] • Optionally, ignore the parameter pdsch-HARQ-ACK-Codebook for a HARQ-ACK codebook related to a DL transmission (e.g. when determining the type of HARQ-ACK codebook related to a DL transmission).

[0310] • Optionally, ignore the parameter pdsch-HARQ-ACK-Codebook for a HARQ-ACK codebook related to a SL transmission (e.g. when determining the type of HARQ-ACK codebook related to a SL transmission),

[0311] • Optionally, ignore the parameter pdsch-HARQ-ACK-Codebook.

[0312] • Optionally, ignore the parameter pdsch-HARQ-ACK-Codebook-r16.

[0313] • Optionally, apply the parameter pdsch-HARQ-ACK-Codebook.

[0314] • Optionally, apply the parameter pdsch-HARQ-ACK-Codebook-r16.

[0315] ◆ Optionally, if the parameter pdsch-HARQ-ACK-Codebook is configured, apply the parameter pdsch-HARQ-ACK-Codebook.

[0316] ◆ Optionally, if the parameter pdsch-HARQ-ACK-Codebook is not configured, apply the parameter pdsch-HARQ-ACK-CodebookList-r16.

[0317] Optionally, if the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, ignore the parameter pdsch-HARQ-ACK-Codebook-r16.

[0318] Optionally, if the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, assume that the parameter pdsch-HARQ-ACK-Codebook-r16 will not be configured.

[0319] Optionally, if the parameter pdsch-HARQ-ACK-Codebook-r16 is configured, assume that the parameter pdsch-HARQ-ACK-CodebookList-r16 will not be configured.

[0320] Optionally, if the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and the parameter pdsch-HARQ-ACK-Codebook-r16 is configured, each element in the parameter pdsch-HARQ-ACK-CodebookList-r16 is considered to take the value indicated by the parameter pdsch-HARQ-ACK-Codebook-r16. For example, if the length (or size) of the parameter pdsch-HARQ-ACK-CodebookList-r16 is 2, the first element and the second element take the value of “semiStatic” and “dynamic” respectively, and the parameter pdsch-HARQ-ACK-Codebook-r16 is configured as “enhancedDynamic”, the first element and the second element of the parameter pdsch-HARQ-ACK-CodebookList-r16 are considered to take the value of “enhancedDynamic” and “enhancedDynamic” respectively (i.e. the value of each element in the parameter pdsch-HARQ-ACK-CodebookList-r16 is replaced by the value of the parameter pdsch-HARQ-ACK-Codebook-r16).

[0321] Optionally, “pdsch-HARQ-ACK-Codebook” can be used to refer to the parameter pdsch-HARQ-ACK-Codebook, or the parameter pdsch-HARQ-ACK-Codebook-r16 (whichever is applicable) if the context is clear.

[0322] Optionally, “pdsch-HARQ-ACK-Codebook” can be used to refer to any element in the parameter pdsch-HARQ-ACK-CodebookList-r16, or the parameter pdsch-HARQ-ACK-Codebook (whichever is applicable) if the context is clear.

[0323] wherein,

[0324] • Optionally, if the parameter pdsch-HARQ-ACK-Codebook is applicable, it is considered that one “pdsch-HARQ-ACK-Codebook” is configured, and the “pdsch-HARQ-ACK-Codebook” is used to refer to the parameter pdsch-HARQ-ACK-Codebook.

[0325] • Optionally, if the parameter pdsch-HARQ-ACK-CodebookList-r16 contains only one element, it can be considered that one "pdsch-HARQ-ACK-Codebook" is configured, and the "pdsch-HARQ-ACK-Codebook" is used to refer to the element contained in the parameter pdsch-HARQ-ACK-CodebookList-r16.

[0326] • Optionally, if the parameter pdsch-HARQ-ACK-CodebookList-r16 contains two elements, it can be considered that two "pdsch-HARQ-ACK-Codebook" are configured, and the two "pdsch-HARQ-ACK-Codebook" are used to refer to the two elements contained in the parameter pdsch-HARQ-ACK-CodebookList-r16, respectively.

[0327] Optionally, "pdsch-HARQ-ACK-Codebook" can be used to refer to any one of the elements in the parameter pdsch-HARQ-ACK-CodebookList-r16, or the parameter pdsch-HARQ-ACK-Codebook-r16, or the parameter pdsch-HARQ-ACK-Codebook (any one of the three is applicable), if the context is clear.

[0328] • Optionally, if the parameter pdsch-HARQ-ACK-Codebook is applicable, it can be considered that one "pdsch-HARQ-ACK-Codebook" is configured, and the "pdsch-HARQ-ACK-Codebook" is used to refer to the parameter pdsch-HARQ-ACK-Codebook.

[0329] • Optionally, if the parameter pdsch-HARQ-ACK-Codebook-r16 is applicable, it can be considered that one "pdsch-HARQ-ACK-Codebook" is configured, and the "pdsch-HARQ-ACK-Codebook" is used to refer to the parameter pdsch-HARQ-ACK-Codebook-r16.

[0330] • Optionally, if any one of the parameter pdsch-HARQ-ACK-CodebookList-r16 is applicable, and the parameter pdsch-HARQ-ACK-CodebookList-r16 contains only one element, it can be considered that one "pdsch-HARQ-ACK-Codebook" is configured, and the "pdsch-HARQ-ACK-Codebook" is used to refer to this element contained in the parameter pdsch-HARQ-ACK-CodebookList-r16.

[0331] • Optionally, if any one of the parameter pdsch-HARQ-ACK-CodebookList-r16 is applicable, and the parameter pdsch-HARQ-ACK-CodebookList-r16 contains two elements, it can be considered that two "pdsch-HARQ-ACK-Codebook" are configured, and the two "pdsch-HARQ-ACK-Codebook" are used to refer to the two elements in the parameter pdsch-HARQ-ACK-CodebookList-r16, respectively.

[0332] Further, in step S103, the number and / or type of the HARQ-ACK codebooks is determined according to the configuration information related to the HARQ-ACK codebook. For convenience, if the number of the determined HARQ-ACK codebooks is N, the N HARQ-ACK codebooks can be referred to as a first HARQ-ACK codebook, a second HARQ-ACK codebook,..., and an Nth HARQ-ACK codebook, respectively.

[0333] Optionally, the step S103 can be described as "determining the number and / or type of the HARQ-ACK codebooks to be generated according to the configuration information related to the HARQ-ACK codebook".

[0334] Optionally, the N is always equal to 1. In this case, optionally, the step S103 can be described as "determining the type of the HARQ-ACK codebook according to the configuration information related to the HARQ-ACK codebook", or "determining the type of the first HARQ-ACK codebook according to the configuration information related to the HARQ-ACK codebook", or "determining the type of the HARQ-ACK codebook to be generated according to the configuration information related to the HARQ-ACK codebook", or "determining the type of the first HARQ-ACK codebook to be generated according to the configuration information related to the HARQ-ACK codebook".

[0335] Optionally, the N satisfies N≥1. In this case, optionally, each HARQ-ACK codebook can have respective configuration information, at this time, the type of the first HARQ-ACK codebook is determined according to the configuration information related to the first HARQ-ACK codebook, the type of the second HARQ-ACK codebook is determined according to the configuration information related to the second HARQ-ACK codebook, …, the type of the Nth HARQ-ACK codebook is determined according to the configuration information related to the Nth HARQ-ACK codebook; the method of determining the type of each HARQ-ACK codebook other than the first HARQ-ACK codebook according to the corresponding configuration information can be the same as the method of determining the type of the first HARQ-ACK codebook.

[0336] Optionally, if the first type condition is satisfied, the type of the first HARQ-ACK codebook is determined as “Type-1”. Wherein,

[0337] Optionally, the first type condition can be any combination (where applicable) of one or more of the following in the manner of “and” or “or”:

[0338]

[0339] ◆The parameter pdsch-HARQ-ACK-Codebook is not configured.

[0340] ◆The parameter pdsch-HARQ-ACK-Codebook is configured as “semiStatic”.

[0341] ◆The parameter pdsch-HARQ-ACK-Codebook is configured, and it is not configured as “dynamic”.

[0342] ◆The parameter pdsch-HARQ-ACK-Codebook is configured, and it is not configured as “enhancedDynamic”.

[0343] ◆The parameter pdsch-HARQ-ACK-Codebook is not ignored.

[0344] ◆The parameter pdsch-HARQ-ACK-Codebook is ignored.

[0345] ◆The parameter pdsch-HARQ-ACK-Codebook-r16 is not configured.

[0346] ◆The parameter pdsch-HARQ-ACK-Codebook-r16 is configured as “semiStatic”.

[0347] ​◆ The parameter pdsch-HARQ-ACK-Codebook-r16 is configured and it is not configured as "dynamic".

[0348] ◆ The parameter pdsch-HARQ-ACK-Codebook-r16 is configured and it is not configured as "enhancedDynamic".

[0349] ◆ The parameter pdsch-HARQ-ACK-Codebook-r16 is not ignored.

[0350] ◆ The parameter pdsch-HARQ-ACK-Codebook-r16 is ignored.

[0351] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is not configured.

[0352] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured as a sequence of size 1.

[0353] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured as a sequence of size 2.

[0354] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured and its first element is configured as "semiStatic".

[0355] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured and its first element is not configured as "dynamic".

[0356] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured and its first element is not configured as "enhancedDynamic".

[0357] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured and its last element is configured as "semiStatic".

[0358] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured and its last element is not configured as "dynamic".

[0359] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and its last element is not configured as "enhancedDynamic".

[0360] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and all of its elements are configured as "semiStatic".

[0361] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and all of its elements are not configured as "dynamic".

[0362] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and all of its elements are not configured as "enhancedDynamic".

[0363] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and at least one of its elements is configured as "semiStatic".

[0364] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and at least one of its elements is not configured as "dynamic".

[0365] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and at least one of its elements is not configured as "enhancedDynamic".

[0366] • Optionally, the first type of condition can be any of the following:

[0367] ◆ The parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is configured with a value of only "semiStatic".

[0368] ◆ The parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is configured with a value of no "dynamic".

[0369] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is neither "dynamic" nor "enhancedDynamic".

[0370] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is neither "dynamic" nor "enhancedDynamic".

[0371] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is at least one "semiStatic".

[0372] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is at least one not "dynamic".

[0373] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is at least one not "enhancedDynamic".

[0374] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is at least one neither "dynamic" nor "enhancedDynamic".

[0375] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is only "semiStatic".

[0376] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is not "dynamic".

[0377] ◆ The value configured by "pdsch-HARQ-ACK-Codebook" or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is neither "dynamic" nor "enhancedDynamic".

[0378] ◆ The value configured by "pdsch-HARQ-ACK-Codebook" or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is neither "dynamic" nor "enhancedDynamic".

[0379] ◆ The value configured by "pdsch-HARQ-ACK-Codebook" or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is at least one "semiStatic".

[0380] ◆ The value configured by "pdsch-HARQ-ACK-Codebook" or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is at least one not "dynamic".

[0381] ◆ The value configured by "pdsch-HARQ-ACK-Codebook" or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is at least one not "enhancedDynamic".

[0382] ◆ The value configured by "pdsch-HARQ-ACK-Codebook" or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is at least one neither "dynamic" nor "enhancedDynamic".

[0383] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is only "semiStatic".

[0384] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is not “dynamic”.

[0385] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is not “enhancedDynamic”.

[0386] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is neither “dynamic” nor “enhancedDynamic”.

[0387] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) has at least one as “semiStatic”.

[0388] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) has at least one not as “dynamic”.

[0389] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) has at least one not as “enhancedDynamic”.

[0390] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is at least one of neither “dynamic” nor “enhancedDynamic”.

[0391] ◆ For each configured HARQ-ACK codebook, the value configured by the corresponding “pdsch-HARQ-ACK-Codebook” is “semiStatic”.

[0392] ◆ For each configured HARQ-ACK codebook, the value configured by the corresponding “pdsch-HARQ-ACK-Codebook” is not “dynamic”.

[0393] ◆ For each configured HARQ-ACK codebook, the value configured by the corresponding “pdsch-HARQ-ACK-Codebook” is not “enhancedDynamic”.

[0394] ◆ For each configured HARQ-ACK codebook, the value configured by the corresponding “pdsch-HARQ-ACK-Codebook” is neither “dynamic” nor “enhancedDynamic”.

[0395] ◆ For at least one configured HARQ-ACK codebook, the value configured by the corresponding “pdsch-HARQ-ACK-Codebook” is “semiStatic”.

[0396] ◆ For at least one configured HARQ-ACK codebook, the value configured by the corresponding “pdsch-HARQ-ACK-Codebook” is not “dynamic”.

[0397] ◆ For at least one configured HARQ-ACK codebook, the value configured by the corresponding “pdsch-HARQ-ACK-Codebook” is not “enhancedDynamic”.

[0398] ◆ For at least one configured HARQ-ACK codebook, the value configured by the corresponding “pdsch-HARQ-ACK-Codebook” is neither “dynamic” nor “enhancedDynamic”.

[0399] ◆ The value of each configured "pdsch-HARQ-ACK-Codebook" is "semiStatic".

[0400] ◆ The value of each configured "pdsch-HARQ-ACK-Codebook" is not "dynamic".

[0401] ◆ The value of each configured "pdsch-HARQ-ACK-Codebook" is not "enhancedDynamic".

[0402] ◆ The value of each configured "pdsch-HARQ-ACK-Codebook" is neither "dynamic" nor "enhancedDynamic".

[0403] ◆ At least one configured "pdsch-HARQ-ACK-Codebook" has a value of "semiStatic".

[0404] ◆ At least one configured "pdsch-HARQ-ACK-Codebook" has a value that is not "dynamic".

[0405] ◆ At least one configured "pdsch-HARQ-ACK-Codebook" has a value that is not "enhancedDynamic".

[0406] ◆ At least one configured "pdsch-HARQ-ACK-Codebook" has a value that is neither "dynamic" nor "enhancedDynamic".

[0407] Optionally, if a second type condition is satisfied, the type of the first HARQ-ACK codebook is determined to be "Type-2". Wherein,

[0408] • Optionally, the second type condition can be one or more of the following in any combination (as applicable) in an "and" or "or" fashion:

[0409] ◆ The parameter pdsch-HARQ-ACK-Codebook is not configured.

[0410] ◆ The parameter pdsch-HARQ-ACK-Codebook is configured and it is not configured as "semiStatic".

[0411] ◆ The parameter pdsch-HARQ-ACK-Codebook is configured as "dynamic".

[0412] ◆ The parameter pdsch-HARQ-ACK-Codebook is configured to be "enhancedDynamic".

[0413] ◆ The parameter pdsch-HARQ-ACK-Codebook is not ignored.

[0414] ◆ The parameter pdsch-HARQ-ACK-Codebook is ignored.

[0415] ◆ The parameter pdsch-HARQ-ACK-Codebook-r16 is not configured.

[0416] ◆ The parameter pdsch-HARQ-ACK-Codebook-r16 is configured, and it is not configured to be "semiStatic".

[0417] ◆ The parameter pdsch-HARQ-ACK-Codebook-r16 is configured to be "dynamic".

[0418] ◆ The parameter pdsch-HARQ-ACK-Codebook-r16 is configured to be "enhancedDynamic".

[0419] ◆ The parameter pdsch-HARQ-ACK-Codebook-r16 is not ignored.

[0420] ◆ The parameter pdsch-HARQ-ACK-Codebook-r16 is ignored.

[0421] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is not configured.

[0422] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured to be a sequence of size 1.

[0423] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured to be a sequence of size 2.

[0424] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and its first element is not configured to be "semiStatic".

[0425] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and its first element is configured to be "dynamic".

[0426] ◆ the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and its first element is configured as "enhancedDynamic".

[0427] ◆ the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and its last element is not configured as "semiStatic".

[0428] ◆ the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and its last element is configured as "dynamic".

[0429] ◆ the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and its last element is configured as "enhancedDynamic".

[0430] ◆ the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and all of its elements are not configured as "semiStatic".

[0431] ◆ the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and all of its elements are configured as "dynamic".

[0432] ◆ the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and all of its elements are configured as "enhancedDynamic".

[0433] ◆ the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and all of its elements are configured as "dynamic" or "enhancedDynamic".

[0434] ◆ the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and at least one of its elements is not configured as "semiStatic".

[0435] ◆ the parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and at least one of its elements is configured as "dynamic".

[0436] ◆ The parameter pdsch-HARQ-ACK-CodebookList-r16 is configured, and at least one of its elements is configured as "enhancedDynamic".

[0437] • Optionally, the second type of condition can be any of the following:

[0438] ◆ The parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is configured with a value that is not "semiStatic".

[0439] ◆ The parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is configured with a value that is only "dynamic".

[0440] ◆ The parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is configured with a value that is only "enhancedDynamic".

[0441] ◆ The parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is configured with a value that is only "dynamic" and "enhancedDynamic".

[0442] ◆ The parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is configured with a value that is at least one is not "semiStatic".

[0443] ◆ The parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is configured with a value that is at least one is "dynamic".

[0444] ◆ The parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is configured with a value that is at least one is "enhancedDynamic".

[0445] ◆ At least one of the values configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is “dynamic” or “enhancedDynamic”.

[0446] ◆ None of the values configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is “semiStatic”.

[0447] ◆ Only the value “dynamic” is configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable).

[0448] ◆ Only the value “enhancedDynamic” is configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable).

[0449] ◆ Only the values “dynamic” or “enhancedDynamic” are configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable).

[0450] ◆ Only the values “dynamic” and “enhancedDynamic” are configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable).

[0451] ◆ At least one of the values configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is not “semiStatic”.

[0452] ◆ At least one of the values configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is “dynamic”.

[0453] • At least one of the values configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is “enhancedDynamic”.

[0454] • At least one of the values configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is “dynamic” or “enhancedDynamic”.

[0455] • None of the values configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is “semiStatic”.

[0456] • Only one of the values configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is “dynamic”.

[0457] • Only one of the values configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is “enhancedDynamic”.

[0458] • Only one of the values configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is “dynamic” or “enhancedDynamic”.

[0459] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is only “dynamic” and “enhancedDynamic”.

[0460] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is at least one not “semiStatic”.

[0461] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is at least one “dynamic”.

[0462] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is at least one “enhancedDynamic”.

[0463] ◆ The value configured by the parameter pdsch-HARQ-ACK-Codebook or the parameter pdsch-HARQ-ACK-Codebook-r16 or the parameter pdsch-HARQ-ACK-CodebookList-r16 (whichever is applicable) is at least one “dynamic” or “enhancedDynamic”.

[0464] ◆ For each configured HARQ-ACK codebook, the value configured by the corresponding “pdsch-HARQ-ACK-Codebook” is not “semiStatic”.

[0465] ◆ For each configured HARQ-ACK codebook, the value configured by the corresponding “pdsch-HARQ-ACK-Codebook” is “dynamic”.

[0466] ◆ For each configured HARQ-ACK codebook, the corresponding value of "pdsch-HARQ-ACK-Codebook" is "enhancedDynamic".

[0467] ◆ For each configured HARQ-ACK codebook, the corresponding value of "pdsch-HARQ-ACK-Codebook" is "dynamic" or "enhancedDynamic".

[0468] ◆ For at least one configured HARQ-ACK codebook, the corresponding value of "pdsch-HARQ-ACK-Codebook" is not "semiStatic".

[0469] ◆ For at least one configured HARQ-ACK codebook, the corresponding value of "pdsch-HARQ-ACK-Codebook" is "dynamic".

[0470] ◆ For at least one configured HARQ-ACK codebook, the corresponding value of "pdsch-HARQ-ACK-Codebook" is "enhancedDynamic".

[0471] ◆ For at least one configured HARQ-ACK codebook, the corresponding value of "pdsch-HARQ-ACK-Codebook" is "dynamic" or "enhancedDynamic".

[0472] ◆ The value of each configured "pdsch-HARQ-ACK-Codebook" is not "semiStatic".

[0473] ◆ The value of each configured "pdsch-HARQ-ACK-Codebook" is "dynamic".

[0474] ◆ The value of each configured "pdsch-HARQ-ACK-Codebook" is "enhancedDynamic".

[0475] ◆ The value of each configured "pdsch-HARQ-ACK-Codebook" is "dynamic" or "enhancedDynamic".

[0476] ◆ At least one configured "pdsch-HARQ-ACK-Codebook" has a value that is not "semiStatic".

[0477] ◆ At least one of the configured values of "pdsch-HARQ-ACK-Codebook" is "dynamic".

[0478] ◆ At least one of the configured values of "pdsch-HARQ-ACK-Codebook" is "enhancedDynamic".

[0479] ◆ At least one of the configured values of "pdsch-HARQ-ACK-Codebook" is "dynamic" or "enhancedDynamic".

[0480] Optionally, in the embodiment one of the application, the PSSCH can be a dynamically scheduled (e.g. scheduled by SCI) PSSCH.

[0481] Optionally, in the embodiment one of the application, the PSSCH can be a non-dynamically scheduled (e.g. scheduled by straight-line configured grant) PSSCH.

[0482] Optionally, in the embodiment one of the application, if the first type condition is not established, the first HARQ-ACK codebook type is determined as "Type-2".

[0483] Optionally, in the embodiment one of the application, if the second type condition is not established, the first HARQ-ACK codebook type is determined as "Type-1".

[0484] Optionally, in the embodiment one of the application, "semiStatic" can be replaced by "semi-static".

[0485] Optionally, in the embodiment one of the application, "enhancedDynamic" can be replaced by "enhancedDynamic-r16".

[0486] Optionally, in the embodiment one of the application, "one of the two is applicable" can be that, when only one of the two is configured, the configured one is determined as the applicable one; when both of the two are configured, one of the two is ignored, and the non-ignored one is determined as the applicable one.

[0487] Optionally, in the embodiment one of the application, "one of the three is applicable" can be that, when only one of the three is configured, the configured one is determined as the applicable one; when two of the three are configured, one of the two is ignored, and the non-ignored one is determined as the applicable one; when all of the three are configured, two of the three are ignored, and the non-ignored one is determined as the applicable one.

[0488] Optionally, in Embodiment One of the present application, one parameter (or variable) (e.g., denoted as X) can be configured with one or more values.

[0489] For example, the X can be an integer or a decimal or a string, etc. type of parameter (or variable), which can be configured with an integer or a decimal or a string, etc. type of value, respectively. For example, the parameter pdsch-HARQ-ACK-Codebook defined below can be configured with a value, which equals to semiStatic or dynamic.

[0490]

[0491] For another example, the X can be an integer or a decimal or a string, etc. type of list or set with size N x (N x ≥ 1), where each list element or set element can be configured with an integer or a decimal or a string, etc. type of value, respectively, and the X can be configured with N x values. Wherein,

[0492] Optionally, "the X is configured with values only v" means that all the N x values equal to v.

[0493] Optionally, "the X is configured with values without v" means that none of the N x values equal to v.

[0494] Optionally, "the X is configured with values at least one of which is v" means that at least one of the N x values equals to v.

[0495] Optionally, "the X is configured with values at least one of which is not v" means that at least one of the N x values does not equal to v.

[0496] Optionally, "the X is configured with values at least one of which is neither v1 nor v2" means that at least one of the N x values is neither equal to v1 nor equal to v2.

[0497] Optionally, "the X is configured with values at least one of which is v1 or v2" means that at least one of the N x values equals to v1 or v2.

[0498] Optionally, "the X is configured with values only v1 and v2" means that any one of the N x values equals to v1 or v2.

[0499] ◆ Optionally, "the value configured by the X is neither v1 nor v2" means that none of the N values is equal to v1 or v2. x

[0500] ◆ Optionally, "the value configured by the X is neither v1 nor v2" means that none of the N values is equal to v1 or v2. x

[0501] For example, the parameter pdsch-HARQ-ACK-CodebookList-r16 defined below can configure one value (N x = 1) or two values (N x = 2), where each value can be equal to semiStatic or dynamic.

[0502]

[0503] Thus, according to the embodiment one, the present application provides a method, by determining the HARQ-ACK codebook related to SL transmission according to the configuration information related to the HARQ-ACK codebook properly, so that the same set of parameters related to the HARQ-ACK codebook can be used to determine the HARQ-ACK codebook related to DL transmission and the HARQ-ACK codebook related to SL transmission, which improves the efficiency of system parameter configuration.

[0504] [Modified example]

[0505] Below, a user device which can execute the method performed by the user device described in detail above of the present application will be explained as a modified example. Figure 2

[0506] Figure 2 is a block diagram representing the user device UE involved in the present application.

[0507] As shown in Figure 2 , the user device UE 20 includes a processor 201 and a memory 202. The processor 201 can include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 202 can include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory, etc. The memory 202 stores program instructions thereon. The instructions, when executed by the processor 201, can execute the above-mentioned method performed by the user device described in detail above of the present application.

[0508] ​​​The method and the apparatus involved in the present application have been described above in connection with preferred embodiments. It is understood by those skilled in the art that the method shown above is only exemplary, and the embodiments described above can be combined with each other without contradiction. The method of the present application is not limited to the steps and the order shown above. The network nodes and the user equipment shown above can include more modules, for example, modules that can be developed or will be developed in the future for base stations, AMFs, UPFs, MMEs, S-GWs or UEs, etc. The various identifiers shown above are only exemplary and not limiting, and the present application is not limited to the specific information elements as examples of these identifiers. Those skilled in the art can make many changes and modifications according to the teachings of the embodiments shown above. Those skilled in the art should understand that part or all of the mathematical expressions or mathematical equations or mathematical inequalities can be simplified or transformed or rewritten to a certain extent, for example, combining constant terms, for example, exchanging two addition terms, for example, exchanging two multiplication terms, for example, moving an item from the left side of the equation or inequality to the right side after changing its sign, for example, moving an item from the right side of the equation or inequality to the left side after changing its sign, etc.; the mathematical expressions or mathematical equations or mathematical inequalities before and after the simplification or transformation or rewriting can be considered equivalent.

[0509] It should be understood that the above embodiments of the present application can be implemented by software, hardware or a combination of software and hardware. For example, various components inside the base station and the user equipment in the above embodiments can be implemented by various devices, including but not limited to: analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), programmable logic devices (CPLDs), etc.

[0510] In the present application, "base station" can refer to a mobile communication data and / or control switching center with certain transmission power and certain coverage area, for example, including resource allocation scheduling, data reception and transmission, etc. "User equipment" can refer to user mobile terminals, for example, including mobile phones, notebooks, etc. terminal equipment that can communicate wirelessly with base stations or micro base stations.

[0511] Furthermore, embodiments of the present application disclosed herein can be implemented on a computer program product. More specifically, the computer program product is a product having a computer readable medium having encoded thereon computer program logic, which, when executed on an computing device, provides related operations to implement the above described technical solutions of the present application. The computer program logic, when executed on at least one processor of the computing system, causes the processor to perform the operations (methods) described in the embodiments of the present application. This arrangement of the present application is typically provided as software, code and / or other data structures arranged on a computer readable medium such as an optical medium (e.g., CD-ROM), floppy disk, or hard disk, or other media, or as firmware or microcode in one or more ROM or RAM or PROM chips, or as software downloadable into the memory of the computing device from a network or other source, or as one or more modules of downloadable software images, shared databases, etc. The software or firmware or such configuration can be installed onto the computing device to cause one or more processors in the computing device to perform the technical solutions described in the embodiments of the present application.

[0512] Furthermore, each functional module or each feature used in each of the above described embodiments of the base station device and the terminal device can be realized or performed by a circuitry, which is typically one or more integrated circuits. The circuitry designed to perform the functions described in the present specification can include a general-purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or discrete hardware components, or a combination of the above, which are configured to perform the various functions described in the present specification. The general-purpose processor can be a microprocessor, or the processor can be a controller, a microcontroller, or a state machine. The above described general-purpose processor or each circuitry can be configured by one or combination of a digital circuitry and a logical circuitry. Further, when an advanced technology replacing the existing integrated circuitry is developed in the future, the advanced technology can be used to configure the integrated circuitry.

[0513] While the present application has been shown and described with reference to the preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details can be made therein without departing from the spirit and scope of the application. Therefore, the present application should not be defined with the only above described embodiments but with the appended claims and their equivalents.

Claims

1.A method performed by a user equipment, comprising the steps of: receiving configuration information of a first RRC parameter and a second RRC parameter, wherein, the first RRC parameter is a pdsch-HARQ-ACK-Codebook parameter, a value of the pdsch-HARQ-ACK-Codebook parameter is an element in a set {semiStatic, dynamic}; and the second RRC parameter is a pdsch-HARQ-ACK-Codebook-r16 parameter, a value of the pdsch-HARQ-ACK-Codebook-r16 parameter is an element in a set {enhancedDynamic}; and determining each of a type of a first HARQ-ACK codebook for HARQ-ACK information of downlink and a type of a second HARQ-ACK codebook for HARQ-ACK information of uplink based on the first RRC parameter or the second RRC parameter, wherein, for the type of the first HARQ-ACK codebook, the user equipment ignores the first RRC parameter; and for the type of the second HARQ-ACK codebook, the user equipment ignores the second RRC parameter and applies the first RRC parameter. 2.A user equipment, comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, cause the user equipment to perform the steps of: receiving configuration information of a first RRC parameter and a second RRC parameter, wherein, the first RRC parameter is a pdsch-HARQ-ACK-Codebook parameter, a value of the pdsch-HARQ-ACK-Codebook parameter is an element in a set {semiStatic, dynamic}; and the second RRC parameter is a pdsch-HARQ-ACK-Codebook-r16 parameter, a value of the pdsch-HARQ-ACK-Codebook-r16 parameter is an element in a set {enhancedDynamic}; and determining each of a type of a first HARQ-ACK codebook for HARQ-ACK information of downlink and a type of a second HARQ-ACK codebook for HARQ-ACK information of uplink based on the first RRC parameter or the second RRC parameter, wherein, for the type of the first HARQ-ACK codebook, the user equipment ignores the first RRC parameter; and for the type of the second HARQ-ACK codebook, the user equipment ignores the second RRC parameter and applies the first RRC parameter. 3.A base station, comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, cause the base station to perform the steps of: sending configuration information of a first RRC parameter and a second RRC parameter, wherein, ​ ​ The first RRC parameter is a pdsch-HARQ-ACK-Codebook parameter, a value of the pdsch-HARQ-ACK-Codebook parameter is an element in a set {semiStatic, dynamic}; and The second RRC parameter is a pdsch-HARQ-ACK-Codebook-r16 parameter, a value of the pdsch-HARQ-ACK-Codebook-r16 parameter is an element in a set {enhancedDynamic}; wherein, The configuration information causes the user equipment to determine each of a type of a first HARQ-ACK codebook for HARQ-ACK information of a downlink and a type of a second HARQ-ACK codebook for HARQ-ACK information of a straight line based on the first RRC parameter or the second RRC parameter, wherein, For the type of the first HARQ-ACK codebook, the first RRC parameter is ignored; and For the type of the second HARQ-ACK codebook, the second RRC parameter is ignored, and the first RRC parameter is applied.

Images