CN114070486A - Method performed by user equipment and user equipment - Google Patents

Method performed by user equipment and user equipment Download PDF

Info

Publication number
CN114070486A
CN114070486A CN202010775345.XA CN202010775345A CN114070486A CN 114070486 A CN114070486 A CN 114070486A CN 202010775345 A CN202010775345 A CN 202010775345A CN 114070486 A CN114070486 A CN 114070486A
Authority
CN
China
Prior art keywords
psfch
transmission
harq
occasion
ack
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010775345.XA
Other languages
Chinese (zh)
Inventor
罗超
刘仁茂
赵毅男
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sharp Corp
Original Assignee
Sharp Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sharp Corp filed Critical Sharp Corp
Priority to CN202010775345.XA priority Critical patent/CN114070486A/en
Priority to PCT/CN2021/108596 priority patent/WO2022028274A1/en
Publication of CN114070486A publication Critical patent/CN114070486A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829Arrangements specially adapted for the receiver end
    • H04L1/1854Scheduling and prioritising arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829Arrangements specially adapted for the receiver end
    • H04L1/1864ARQ related signaling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/1887Scheduling and prioritising arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/1896ARQ related signaling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation

Abstract

According to the invention, a method performed by a user equipment is proposed, characterized by comprising: determining a PSSCH transmission occasion associated with a PSFCH slot that can be used for candidate PSSCH transmission based on a PSFCH slot that satisfies a HARQ-ACK timing configuration from PSFCH to PUCCH, and if N corresponding to the HARQ-ACK information bit is absent due to a first omissionoccasionAnd if a first SL operation is executed at each SL opportunity, generating a NACK for the PSSCH transmission opportunity, and determining the priority value of the NACK as a maximum priority value.

Description

Method performed by user equipment and user equipment
Technical Field
The present invention relates to a method performed by a user equipment and a user equipment.
Background
In 5G V2X (see non-patent document 4), the network side (e.g., a base station, etc.) can allocate one or more pschs transmission resources to a UE by configuring and/or activating an "SL configuration grant" for the UE, or by DCI. In addition, the network side (e.g., base station, etc.) may provide uplink resources (e.g., PUCCH resources, such as PUSCH resources) for the UE to report HARQ-ACK information related to the psch transmission. In the mechanism for reporting HARQ-ACK information, the problem to be solved includes that it is necessary to ensure that each HARQ-ACK information bit reported is correctly set with a HARQ-ACK value and/or priority value in all cases.
Prior art documents
Non-patent document
Non-patent document 1: RP-152293, New WI propofol: support for V2V services based on LTE sidelink
Non-patent document 2: RP-170798, New WID on 3GPP V2X Phase 2
Non-patent document 3: RP-170855, New WID on New Radio Access Technology
Non-patent document 4: RP-190766, New WID on 5G V2X with NR sidelink
Disclosure of Invention
In order to solve at least part of the above problems, the present invention provides a method performed by a user equipment and the user equipment, which enable the reported HARQ-ACK information to completely reflect the HARQ-ACK feedback condition of the direct link by setting the HARQ-ACK value and the priority value of the HARQ-ACK information bit in the default condition (e.g. when DCI scheduling psch transmission is not detected), and enable the priority of the uplink channel carrying the HARQ-ACK information to accurately reflect the priority of data transmission on the direct link.
According to the invention, a method performed by a user equipment is proposed, characterized by comprising: determining a PSSCH transmission occasion associated with a PSFCH slot that can be used for candidate PSSCH transmission based on a PSFCH slot that satisfies a HARQ-ACK timing configuration from PSFCH to PUCCH, and if N corresponding to the HARQ-ACK information bit is absent due to a first omissionoccasionAnd if a first SL operation is executed at each SL opportunity, generating a NACK for the PSSCH transmission opportunity, and determining the priority value of the NACK as a maximum priority value.
Preferably, the first omission reason may be that a corresponding DCI format is not detected, or that at the NoccasionThere may be other higher priority transmission or reception operations on some or all of the SL opportunities, or no data from higher layer protocols to transmit.
Preferably, the first SL operation may be, at the NoccasionThe PSSCH is transmitted for every PSSCH transmission opportunity.
Furthermore, according to the present invention, there is provided a user equipment comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the method described above.
Therefore, the invention provides a method, which enables the reported HARQ-ACK information to completely reflect the HARQ-ACK feedback condition of the direct link and the priority of the uplink channel carrying the HARQ-ACK information to accurately reflect the priority of data transmission on the direct link by setting the HARQ-ACK value and the priority value of the HARQ-ACK information bit under the default condition (such as when DCI for scheduling PSSCH transmission is not detected).
Drawings
The above and other features of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which:
fig. 1 is a flowchart illustrating a method performed by a user equipment according to a first embodiment of the present invention.
Fig. 2 shows a block diagram of a user equipment UE to which the present invention relates.
Detailed Description
The invention is described in detail below with reference to the figures and the detailed description. It should be noted that the present invention should not be limited to the specific embodiments described below. In addition, for the sake of brevity, detailed descriptions of well-known technologies not directly related to the present invention are omitted to prevent confusion of understanding of the present invention.
Embodiments according to the present invention are described in detail below with a 5G mobile communication system and its subsequent evolution as an example application environment. However, it is to be noted that the present invention is not limited to the following embodiments, but is applicable to more other wireless communication systems, such as a communication system after 5G and a 4G mobile communication system before 5G, and the like.
Some terms to which the present invention relates will be described below, and the terms to which the present invention relates are defined herein, unless otherwise specified. The terms given in the invention may adopt different naming manners in LTE, LTE-Advanced Pro, NR and the following communication systems, but the unified terms adopted in the invention can be replaced by the terms adopted in the corresponding systems when being applied to the specific systems.
3 GPP: 3rd Generation partnershift Project, third Generation Partnership Project
AGC: automatic Gain Control
AL: aggregation Level, Aggregation Level
AMF: access and Mobility Management Function
AS: access Stratum, Access Stratum
BWP: bandwidth Part, Bandwidth fragment
CA: carrier Aggregation, Carrier Aggregation
CBR: channel Busy Ratio, Channel Busy Ratio
CCE: control-channel element, control-channel element
CORESET: control-resource set, control resource set
And (3) CP: cyclic Prefix, Cyclic Prefix
CP-OFDM: cyclic Prefix Orthogonal Frequency Division Multiplexing, Cyclic Prefix Orthogonal Frequency Division Multiplexing
CRB: common Resource Block, Common Resource Block
CRC: cyclic Redundancy Check (crc)
CSI: channel-state Information, Channel state Information
CSS: common Search Space, Common Search Space
DC: dual Connectivity, Dual Connectivity
DCI: downlink Control Information, Downlink Control Information
DFN: direct Frame Number, Direct Frame Number
DFT-s-OFDM: discrete Fourier transform Spread Orthogonal Frequency Division Multiplexing
DL: downlink, Downlink
DL-SCH: downlink Shared Channel, Downlink Shared Channel
DM-RS: demodulation reference signal (DMRS)
eMBB: enhanced Mobile Broadband communications
eNB: E-UTRAN Node B, E-UTRAN Node B
E-UTRAN: evolved UMTS Terrestrial Radio Access Network
FDD: frequency Division Duplex, Frequency Division Duplex
FDRA: frequency Domain Resource Assignment, Frequency Domain Resource allocation
FR 1: frequency Range 1, Frequency Range 1
FR 2: frequency Range 1, Frequency Range 2
GLONASS: global NAvigation Satellite System (GNSS)
And g NB: NR Node B, NR Node B
GNSS: global Navigation Satellite System (GNSS)
GPS: global Positioning System (GPS)
HARQ: hybrid Automatic Repeat Request (HARQ)
HARQ-ACK: HARQ Acknowledgement, HARQ Acknowledgement
ID: identity, Identifier
IE: information Element, Information Element
IP: internet Protocol (IP)
LCID: logical Channel ID, Logical Channel identifier
LSB: least Significant Bit of the Least Significant Bit
LTE: long Term Evolution, Long Term Evolution
LTE-A: long Term Evolution-Advanced, Long Term Evolution-upgraded version
MAC: medium Access Control, Medium Access Control
MAC CE: MAC Control Element, MAC Control Element
MCG (calcium carbonate): master Cell Group, Master Cell Group
MIB: master Information Block, Master Information Block
MIB-SL: master Information Block-Sidelink, Master Information Block-Linked
MIB-SL-V2X: master Information Block-Sidelink-V2X, Master Information Block-go-vehicle to any entity
MIB-V2X: master Information Block-V2X, Master Information Block-vehicle to any entity
MME: mobility Management Entity
MSB: most Significant Bit of Most Significant Bit
mMTC: massive Machine Type Communication
NAS: Non-Access-Stratum, Non-Access Stratum
NDI: new Data Indicator, New Data Indicator
NR: new Radio, New Radio
NUL: normal Uplink, Normal Uplink
OFDM: orthogonal Frequency Division Multiplexing, Orthogonal Frequency Division Multiplexing
PBCH: physical Broadcast Channel, Physical Broadcast Channel
PCell: primary Cell, Primary Cell
PDCCH: physical Downlink Control Channel, Physical Downlink Control Channel
PDCP: packet Data Convergence Protocol (PDMP)
PDSCH: physical Downlink Shared Channel (pdcch)
PSBCH: physical Sidelink Broadcast Channel, Physical direct Broadcast Channel
PSCCH: physical Sidelink Control Channel, a Physical direct Control Channel
PSFCH: physical Sidelink Feedback Channel, Physical direct Feedback Channel
PSSCH: physical Sidelink Shared Channel, a Physical direct Shared Channel
PRB: physical Resource Block, Physical Resource Block
PSCell: primary SCG Cell, Primary SCG Cell
PSS: primary Synchronization Signal, Primary Synchronization Signal
PSS-SL: primary Synchronization Signal for Sidelink, Primary Synchronization Signal
PSSS: primary Sidelink Synchronization Signal, Primary inline Synchronization Signal
PTAG: primary Timing Advance Group, Primary Timing Advance Group
PUSCH: physical uplink shared channel (PRCH)
PUCCH: physical uplink control channel, Physical uplink control channel
QCL: quasi co-location of Quasi co-location
QoS: quality of Service
QZSS: Quasi-Zenith Satellite System, Quasi-Zenith Satellite System
An RAR: random Access Response (RANDOM ACCESS RESPONSE)
RB: resource Block, Resource Block
RE: resource Element, Resource Element
REG: resource-element group, resource element group
RF: radio Frequency, Radio Frequency
RLC: radio Link Control, Radio Link Control protocol
RNTI: Radio-Network Temporary Identifier (RNTI)
RRC: radio Resource Control, Radio Resource Control
RV: redundancy Version of Reduncyny Version
S-BWP: sidelink Bandwidth Part, straight-forward Bandwidth fragment
S-MIB: sidelink Master Information Block, straight-row Master Information Block
S-PSS: sidelink Primary Synchronization Signal, straight Primary Synchronization Signal
S-SSB: sidelink SS/PBCH block, inline Sync Signal/physical broadcast channel Block
S-SSS: sidelink Secondary Synchronization Signal, direct auxiliary Synchronization Signal
SCell: secondary Cell, sub-Cell
SCG: secondary Cell Group, subcell Group
SCI: sidelink Control Information, straight-line Control Information
SCS: subcarrier Spacing, Subcarrier Spacing
SDAP: service Data Adaptation Protocol
SFN: system Frame Number, System Frame Number
SIB: system Information Block
SL: sidelink, straight
SL BWP: sidelink Bandwidth Part, straight-forward Bandwidth fragment
SL MIB: sidelink Master Information Block, straight-row Master Information Block
SL PSS: sidelink Primary Synchronization Signal, straight Primary Synchronization Signal
SL SS: sidelink synchronization Signal, direct line synchronization Signal
SL SSID: sidelink Synchronization Signal Identity, direct line Synchronization Signal Identity
SL SSB: sidelink SS/PBCH block, inline Sync Signal/physical broadcast channel Block
SL SSS: sidelink Secondary Synchronization Signal, direct auxiliary Synchronization Signal
SL-SCH: sidelink Shared Channel, straight-ahead Shared Channel
SLSS: sidelink synchronization Signal, direct line synchronization Signal
SLSS ID: sidelink Synchronization Signal Identity, direct line Synchronization Signal Identity
SLSSID: sidelink Synchronization Signal Identity, direct line Synchronization Signal Identity
SpCell: special Cell, Special Cell
SRS: sounding Reference Signal
And (3) SSB: SS/PBCH block, Sync Signal/physical broadcast channel Block
SSB-SL: SS/PBCH block for Sidelink, inline Sync Signal/physical broadcast channel Block
SSS: secondary Synchronization Signal, Secondary Synchronization Signal
SSS-SL: secondary Synchronization Signal for Sidelink, direct auxiliary Synchronization Signal
SSSB: sidelink SS/PBCH block, inline Sync Signal/physical broadcast channel Block
SSSS: secondary Sidelink Synchronization Signal, Secondary inline Synchronization Signal
STAG: secondary Timing Advance Group, Secondary Timing Advance Group
Sub-channel: sub-channels
SUL: supplement Uplink, supplement Uplink
S-GW: serving Gateway, Serving Gateway
TA: timing Advance, Timing Advance
TAG: timing Advance Group, Timing Advance Group
TB: transport Block
TCP: transmission Control Protocol, Transmission Control Protocol
TDD: time Division Duplex, Time Division Duplex
TPC: transmit power control, transmission power control
UE: user Equipment, User Equipment
UL: uplink, Uplink
UMTS: universal Mobile Telecommunications System, Universal Mobile communications System
UPF: user Plane Function
URLLC: Ultra-Reliable and Low latency Communication
And (3) USS: UE-specific Search Space, UE-specific Search Space
V2I: Vehicle-to-Infrastructure, Vehicle-to-Infrastructure
V2N: vehicle-to-network, Vehicle-to-network
V2P: Vehicle-to-Pedestrian
V2V: Vehicle-to-Vehicle
V2X: vehicle-to-aircraft, Vehicle to any entity
VRB: virtual Resource Block, Virtual Resource Block
In all examples and embodiments of the invention, unless otherwise specified:
optionally, a parameter Z defined in an information element I may also be referred to as a "data unit" (or "field") in the information element I, and accordingly, the information element Z corresponding to the parameter Z may also be referred to as the type of the "data unit" (or "field") Z.
Optionally, a sequence of N elements x (0), x (1),.. and x (N-1) may be abbreviated as x (0),.. and x (N-1) in the clear context.
Optionally, a sequence of N elements is N in length (or size N).
Optionally, where applicable, "V2X communication", "V2X SL communication" and "SL V2X communication" may be interchanged.
Optionally, where applicable, the "V2X communication" may be an NR SL based V2X communication.
Optionally, where applicable, the "V2X communication" may be LTE SL based V2X communication.
Optionally, in case of clear context, it can be considered that one TDD cell can configure one DL carrier, one UL carrier, and, optionally, one SUL carrier. The UL carrier may also be referred to as a "non-SUL carrier".
Alternatively, in the clear context, a "non-SUL carrier" may be considered to be a "UL carrier" in a TDD cell. For example, one TDD cell may configure one UL carrier, referred to as a "non-SUL carrier. As another example, one TDD cell may configure two UL carriers, one of which is a "non-SUL carrier" and the other of which is a "SUL carrier".
Optionally, where applicable, "send" and "transmit" may be interchanged.
Optionally, any two of "within XX", "in XX" and "on XX" may be interchanged where applicable (e.g. when an operation(s) is/are performed on a resource (s)). Where XX may be one or more carriers (e.g., SL carrier), or one or more BWPs (e.g., SL BWPs), or one or more resource pools, or one or more links (e.g., UL, DL, SL), or one or more channels (e.g., psch), or one or more subchannels, or one or more RBGs, or an RB, or an arbitrary "opportunity" (e.g., PDCCH listening opportunity, psch transmission opportunity, psch reception opportunity), or an arbitrary time and/or frequency domain and/or code domain and/or spatial domain resource, etc.
Optionally, if S1Is a set, then S1May be S1A set of zero or one or more (including all) elements in the list.
Optionally, if S1And S2Are two sets, then S1-S2Representation set S1And set S2Is the "difference set", i.e. set S1In a set S2The set of elements of (1).
Optionally, if S1And S2Is two sets, then
Figure BDA0002617605070000091
Optionally, on the set S1The elements in (A) are operated (e.g. screened, transformed, etc.) to obtain a set S2Can be equivalent to directly in the original set S1Get the updated set S1
Alternatively, "higher layer" may refer to one or more protocol layers or protocol sub-layers above the physical layer. E.g. the MAC layer, such as the RLC layer, such as the PDCP layer, such as the PC5 RRC layer, such as the PC5-S layer, such as the RRC layer, such as the V2X layer, such as the application layer, such as the V2X application layer, etc.
Alternatively, "pre-configuration" may be pre-configuration in a higher layer protocol. Such as presetting (e.g., per specification of a higher layer protocol) at a particular memory location in the UE, or presetting (e.g., per specification of a higher layer protocol) at a particular memory location accessible by the UE.
Alternatively, "configuration" may be in a higher layer protocol through signaling. For example configured for the UE through RRC signaling.
Optionally, "configured" may be replaced with "preconfigured".
Optionally, "configured" may be replaced with "configured or preconfigured".
Alternatively, "a parameter has been configured" may be replaced with "a parameter has been provided".
Alternatively, "some parameter has been configured" may be replaced with "some parameter has been indicated (signaled)".
Optionally, "unconfigured" may be replaced with "unconfigured".
Optionally, "unconfigured" may be replaced with "unconfigured and/or unconfigured".
Alternatively, "unconfigured" may be replaced with "unconfigured" (pre-) configured ".
Optionally, suffixes in the parameter names such as "-r 8", "-r 9", "-r 10", "-r 11", "-r 12", "-r 13", "-r 14", "-r 15", "-r 16" and the like may be removed, where the context is clear. For example, "pdsch-HARQ-ACK-codebook" may be used to refer to the parameter pdsch-HARQ-ACK-codebook-r 16.
Alternatively, a time-domain resource may also be referred to as a time (time) resource.
Alternatively, the frequency-domain resource may also be referred to as a frequency resource.
Alternatively, "symbol" refers to an "OFDM symbol".
Alternatively, the numbering of the OFDM symbols may start from 0 within one slot. For example, for normal CP, the set of numbers of OFDM symbols within a slot may be 0, 1. As another example, for extended CP, the set of numbers of OFDM symbols within a slot may be {0, 1.
Alternatively, a resource block may refer to a Virtual Resource Block (VRB), a Physical Resource Block (PRB), a Common Resource Block (CRB), or a resource block defined in other manners.
Optionally, the numbering of the sub-channels (sub-channels) may start from 0. For example, if the number of sub-channels configured in the resource pool is equal to
Figure BDA0002617605070000111
The set of numbers of the sub-channels may be
Figure BDA0002617605070000112
Alternatively, within a resource block, the numbering of the subcarriers may start from 0. For example, the number set of subcarriers within a resource block may be {0, 1.., 11 }.
Optionally, a value of a parameter (e.g. RRC parameter) with a size of L bits may be represented by an integer value (e.g. 0, 1, 2, etc.), or may be represented by a bit string (e.g. a bit string with a length of L, such as 'b') corresponding to the integer value0b1...bL-1') is used. Wherein the content of the first and second substances,
optionally, the bit string' b0b1...bL-1' in, the first (i.e., leftmost) bit (i.e., b)0) Is the most significant bit, the last (i.e., rightmost) bit (i.e., b)L-1) Is the least significant bit. For example, if L is 3 and the value of the parameter is represented by a bit string as '011', the parameter is represented by L ═ 3 and the bit string represents a bit string of the parameterThe most significant bit of the number has a value of 0 and the corresponding integer value of the parameter is 3.
Optionally, the bit string' b0b1...bL-1' in, the first (i.e., leftmost) bit (i.e., b)0) Is the least significant bit, the last (i.e., rightmost) bit (i.e., b)L-1) Is the most significant bit. For example, if L is 3 and the value of the parameter is represented by a bit string as '011', the least significant bit of the parameter has a value of 0 and the integer value corresponding to the parameter is 6.
Alternatively, ACK may correspond to the integer 0 and NACK may correspond to the integer 1.
Alternatively, ACK may correspond to the integer 1 and NACK may correspond to the integer 0.
Alternatively, "DCI" may refer to one applicable DCI format. For example DCI format 3_ 0.
In communication based on D2D (Device to Device) technology, an interface between devices (also referred to as User Equipment, UE) may be referred to as a PC5 interface, and a corresponding transmission link may be referred to as a "straight" or "sidelink" (SL) link at a physical layer to distinguish the Uplink (UL) link and the Downlink (DL) link. The communication based on the SL link may be referred to as SL communication (sidelink communication). SL links based on LTE technology may be referred to as LTE SL links. SL links based on NR technology may be referred to as NR SL links. The 5G V2X communication may be based on LTE SL as well as NR SL. Hereinafter, unless otherwise specified, "SL" refers to NR SL, and "SL communication" refers to NR SL communication.
The physical layer of the SL link may support one or more modes of transmission in one or more of an in-coverage (in-coverage), out-of-coverage (out-of-coverage) and partial-coverage (partial-coverage) scenarios, such as broadcast (broadcast) transmission, multicast (groupcast) transmission, unicast (unicast) transmission, and so on.
For FR1(Frequency Range 1), SCS (subcarrier spacing, denoted as Δ f, in kHz) corresponding to SL link may be 15kHz (normal C) for FR1(Frequency Range 1)P), or 30kHz (normal CP), or 60kHz (normal CP or extended CP); for FR2(Frequency Range 2), the SCS for the SL link may be 60kHz (normal CP or extended CP), or 120kHz (normal CP). Each SCS corresponds to one SCS configuration (μ), for example, Δ f 15kHz corresponds to μ 0, Δ f 30kHz corresponds to μ 1, Δ f 60kHz corresponds to μ 2, Δ f 120kHz corresponds to μ 3, and so on; as another example, for any given μ, Δ f is 2μ15 kHz. μ may be the SCS configuration of SL carriers; for example, all SL transmissions in one SL carrier use the same SCS configuration and/or the same CP. μ may be SCS configuration of SL BWP (Sidelink Bandwidth Part, straight-going Bandwidth segment, alternatively referred to as S-BWP, alternatively referred to as SBWP, alternatively referred to as SL-BWP, alternatively referred to as BWP-SL, or simply BWP); for example, all SL transmissions in one SL BWP use the same SCS configuration and/or the same CP. μ may be the SCS configuration of a resource pool (resource pool); for example, all SL transmissions in one resource pool use the same SCS configuration and/or the same CP.
Signals and channels related to SL operation may include:
SL PSS (Primary Linear Synchronization Signal), alternatively called S-PSS, alternatively called SPSS, alternatively called SL-PSS, alternatively called PSS-SL, alternatively called PSS (Primary Linear Synchronization Signal), and so on.
An SL SSS (direct Synchronization Signal), which is alternatively referred to as an S-SSS, or an SSSs (direct Synchronization Signal), or an SL-SSS, or an SSS-SL, or an SSSs (direct Synchronization Signal), or an auxiliary direct Synchronization Signal), and the like.
PSBCH (Physical Sidelink Broadcast Channel).
PSCCH (Physical downlink Control Channel).
PSSCH (Physical Sidelink Shared Channel).
PSFCH (Physical Sidelink Feedback Channel).
The SL PSS, SL SSS and PSBCH together may be organized in block form on time/frequency resources, for example called S-SSB (Single Synchronization Signal/PSBCH block, or SSS/PSBCH block, inline Synchronization Signal/physical inline broadcast channel 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 (e.g., 11 resource blocks) of the S-SSB may be located within a corresponding SL carrier (e.g., within one SL BWP configured within the SL carrier). The SL PSS and/or the SL SSS may carry a SL SSID (Sidelink Synchronization Identity, or Sidelink Synchronization Identifier, a direct Synchronization Identity, or Sidelink Synchronization Signal Identity, or a direct Synchronization Signal Identity, or a SLSED-SSID, or a SSID-SL, or a BCH SID, or a SLSS ID, or a S-SSID, etc.), the PSS may carry a SL MIB (Sidelink Master Information Block, a direct Master Information Block, or a SL-MIB, or a S-MIB, or a MIB-SL, or a Master Information Block Sidelink), for example configured by a parameter Master Information Block.
On the SL link, the time and/or frequency domain resources for transmission of the S-SSB may be configured by higher layer parameters. For example, in the frequency domain, the location of the S-SSB in the frequency domain may be configured by the parameter absoluteFrequency SSB-SL (or the parameter SL-absoluteFrequency SSB). As another example, in the time domain, one or more synchronization configuration items may be configured by a parameter SL-SyncConfigList, where in each synchronization configuration item, the synchronization configuration item may be configured by a parameter numSBwithPeriod-SL (or a parameter SL-NumSSB-WithPeriod) within an S-SSB period with a length of 16 frames
Figure BDA0002617605070000141
An S-SSB, wherein the number (or index) is
Figure BDA0002617605070000142
Figure BDA0002617605070000143
The index of the slot (slot) in which the S-SSB is located in a period of length 16 frames may be
Figure BDA0002617605070000144
Wherein
Figure BDA0002617605070000145
May be configured by a parameter timeOffsetSSB-SL (or parameter SL-timeOffsetSSB),
Figure BDA0002617605070000146
may be configured by a parameter timelntervalssb-SL (or a parameter SL-TimeInterval).
Sometimes, the time domain resource and/or the frequency domain resource configured for the S-SSB in the SL carrier may be considered to correspond to a candidate (candidate) S-SSB (or referred to as an S-SSB candidate). One or more S-SSB transmissions may be present (e.g., from different UEs, respectively) at the same time or none at all on the time and/or frequency domain resources corresponding to a candidate S-SSB.
Sometimes, a time slot configured with S-SSB (or configured with S-SSB resources, or configured with candidate S-SSB resources) may also be referred to as a time slot configured with SLSS (or configured with SLSS resources). And vice versa.
A synchronization source (synchronization source) related to SL synchronization may include a GNSS (Global navigation satellite system), a gNB, an eNB, and a UE (e.g., an NR UE, also an LTE UE, also an NR UE or an LTE UE). One UE that is the synchronization source (e.g., the UE transmitting the S-SSB) may be referred to as a SyncRefUE.
Examples of the GNSS may include GPS (Global Positioning System), GLONASS (Global NAvigation Satellite System), BeiDou (BeiDou NAvigation Satellite System), Galileo (Galileo NAvigation Satellite System), QZSS (Quasi-Zenith Satellite System), and the like.
One or more (e.g., one) SL BWPs may be configured within the SL carrier. For each SL BWP, a starting symbol that may be used for SL transmission (e.g., noting that symbol is numbered as SL-StartSymbol within a slot) may be configured by a parameter startSLsymbols (or parameter SL-StartSymbol)
Figure BDA0002617605070000151
) And configuring the number of symbols that can be used for SL transmission (for example, noting that the number of symbols is the number of symbols) by a parameter length slsymbols (or parameter SL-length symbols)
Figure BDA0002617605070000152
) Wherein said
Figure BDA0002617605070000153
The individual symbols may be consecutive symbols.
Figure BDA0002617605070000154
Can be recorded as
Figure BDA0002617605070000155
For example
Figure BDA0002617605070000156
Figure BDA0002617605070000157
Can be recorded as
Figure BDA0002617605070000158
For example
Figure BDA0002617605070000159
The "symbol that can be used for SL transmission" may be referred to as "SL symbol". Set of SL symbols (chronologically) as
Figure BDA00026176050700001510
Then
Figure BDA00026176050700001511
Figure BDA00026176050700001512
For example, if
Figure BDA00026176050700001513
The set of SL symbols is 7, 8, 9, 10, 11, 12, 13.
Only slots that satisfy certain conditions may be used for SL transmission. E.g. at least a symbol in said slot
Figure BDA00026176050700001514
(symbol)
Figure BDA00026176050700001515
(symbol)
Figure BDA00026176050700001516
Is an uplink symbol (e.g., a time slot configured by tdd-UL-DL-configuration common in servingCellConfigCommon in SIB1 that satisfies the condition). As another example, the timeslot must be in a timeslot set of a configured resource pool (resource pool).
One or more resource pools may be configured within one SL BWP, wherein, within each resource pool,
in the frequency domain, the position of the starting resource block of the starting sub-channel of the resource pool within the SL BWP may be configured by a parameter startRB-Subchannel (or SL-startRB-Subchannel).
In the frequency domain, each subchannel may be composed of one or more resource blocks, a specific number of resource blocks (called the size of the subchannel, e.g. denoted as n)subChannelSize) Can be configured by a parameter subchannel size (or sl-subchannel size). N issubChannelSizeThe resource blocks may be contiguous in the frequency domain.
In the frequency domain, the frequency of the signal,the number of sub-channels (denoted as "numSubchannel") occupied by the resource pool can be configured by a parameter numSubchannel (or a parameter sl-numSubchannel)
Figure BDA0002617605070000161
). The above-mentioned
Figure BDA0002617605070000162
The subchannels may be contiguous in the frequency domain.
In the frequency domain, the Number of PRBs occupied by the resource pool (denoted as "PRB") can be configured by a parameter sl-RB-Number
Figure BDA0002617605070000163
). Alternatively, the UE may assume the stated
Figure BDA0002617605070000164
Last in PRB
Figure BDA0002617605070000165
One PRB is not used.
In the frequency domain, the sub-channels in a resource pool can be numbered as
Figure BDA0002617605070000166
Wherein the subchannel numbered i may be referred to as "subchannel i"
Figure BDA0002617605070000167
In the time domain, a time slot bitmap may be configured with a parameter timeresourcepool (or parameter sl-TimeResource) for indicating which time slot or slots in a candidate time slot set belong to the resource pool. It can be seen that two consecutive slots within one resource pool may not be contiguous in time (e.g., slot 0 and slot 6 within one frame may be two consecutive slots in one resource pool). For convenience, the set of timeslots in a resource pool may be denoted as { r0,r1,r2,...}。
The allocation of resources (e.g., time domain resources, such as frequency domain resources, such as code domain resources) related to SL operation can be classified as follows:
mode 1(Mode 1): the base station schedules resources for SL transmission.
Mode 2(Mode 2): the UE determines resources for SL transmission (i.e., the base station does not participate in scheduling of resources for SL transmission). For example, a UE performing a SL transmission operation autonomously determines resources for SL transmission.
The UE may schedule transmission of data through SCI (Sidelink Control Information). SL operations may support a "two-stage SCI" (two-stage SCI), where the first stage SCI (1)stA stage SCI) may contain information of resource reservation and/or resource allocation to facilitate detection (sensing) of resource reservation and/or resource allocation by all UEs monitoring (monitor) SL links; second stage SCI (2)ndStage SCI) may contain other information, such as information related to HARQ feedback, etc. Hereinafter, when "SCI" is referred to individually, it may refer to the first-stage SCI, or the second-stage SCI, or both the first-stage SCI and the second-stage SCI, where applicable, unless otherwise specified.
The format of the first stage SCI may be SCI format 1-a (or written as "SCI format 1_ a"). The following are some examples of information that may be contained in SCI format 1-a:
priority (Priority).
Frequency resource allocation (Frequency resource allocation).
Time resource allocation (Time resource assignment).
Resource reservation period (Resource reservation period).
DMRS pattern (DMRS pattern).
Second stage SCI Format (2)nd-stage SCI format)。
The format of the second-stage SCI may be SCI format 2-a (or written as "SCI format 2_ a"), or SCI format 2-B (or written as "SCI format 2_ B"). The following are some examples of information that may be contained in SCI format 2-a and/or SCI format 2-B:
source Layer one identifier (Source Layer-1ID, alternatively referred to as Layer-1Source ID, Layer one Source identifier, alternatively referred to as Physical Layer Source ID, Physical Layer Source identifier, or (where the context is clear) Source ID, Source identifier).
A Destination Layer-one identifier (Destination Layer-1ID, alternatively referred to as Layer-1Destination ID, Layer-one Destination identifier, alternatively referred to as Physical Layer Destination ID, Physical Layer Destination identifier, alternatively referred to (where context is clear) as Destination ID, Destination identifier).
HARQ Process identification (HARQ Process ID), or HARQ Process Number (HARQ Process Number).
New Data Indicator (NDI).
Redundancy Version (Redundancy Version, RV).
The first stage SCI may be carried on the PSCCH. The second stage SCI may be multiplexed on the PSCCH associated with (or scheduled to) the PSCCH with the data to be transmitted. The PSCCH and its associated PSCCH may be multiplexed in some manner on the time and/or frequency domain resources allocated for SL transmissions (e.g., the starting resource block of the PSCCH is the starting sub-channel of its associated PSCCH. In addition, the first-stage SCI and/or the corresponding second-stage SCI may be considered to schedule the psch (or to schedule transmission of the psch, or to schedule transmission of the TBs carried in the psch).
A "psch transmission occasion" may be one or more time and/or frequency and/or code domain resources related to (e.g., used by) psch transmission and/or reception. For example, one of the following:
one slot in one resource pool.
One or more symbols related to PSSCH transmission in a slot in a resource pool.
One or more time slots in a resource pool.
One or more symbols related to PSSCH transmission in one or more slots in a resource pool.
The "PSCCH transmission occasion" may also be referred to as a "PSCCH-PSCCH transmission occasion".
The definition of "psch transmission occasion" may apply to only one resource pool (i.e., the "psch transmission occasion" is defined separately within each resource pool), or may apply to multiple resource pools (e.g., one "psch transmission occasion" may include time and/or frequency and/or code domain resources within multiple resource pools).
A "psch reception occasion" may be one or more time and/or frequency and/or code domain resources related to psch transmission and/or reception (e.g., used by one or more psch transmissions and/or receptions). For example, one of the following:
one slot in one resource pool.
One or more symbols related to psch transmission and/or reception in a slot in a resource pool.
One or more time slots in a resource pool.
One or more symbols related to psch transmission and/or reception in one or more slots in a resource pool.
The "PSCCH reception timing" may also be referred to as a "PSCCH-PSCCH reception timing".
The definition of "psch reception occasion" may apply to only one resource pool (i.e., the "psch reception occasion" is defined separately within each resource pool), or may apply to multiple resource pools (e.g., one "psch reception occasion" may include time and/or frequency and/or code domain resources within multiple resource pools).
For a SL transmission containing PSCCH and/or PSCCH, the transmitter may be referred to as TX UE and the receiver may be referred to as RX UE. If HARQ feedback is enabled, the RX UE may feed back information related to PSCCH and/or PSCCH reception (e.g., referred to as "HARQ-ACK information") through the PSFCH. For example, when an RX UE receives a PSSCH in a resource pool and a value of "HARQ feedback enabled/disabled indicator" in a corresponding SCI is 1, the RX UE provides HARQ-ACK information through a PSFCH transmission in the resource pool. Such HARQ-ACK information may be referred to as "HARQ-ACK information related to SL transmission reported on SL". In some configurations, HARQ-ACK information reported on a SL relating to SL transmissions may indicate a Positive Acknowledgement (ACK, Acknowledgement, or Positive Acknowledgement), e.g., indicating that data carried by the corresponding PSCCH and/or PSCCH may be correctly decoded, or a Negative Acknowledgement (NACK, or NAK), e.g., indicating that data carried by the corresponding PSCCH and/or PSCCH may not be correctly decoded; in other configurations, HARQ-ACK information reported on the SL related to SL transmission may indicate only a NACK (e.g., no HARQ feedback is sent when data carried by the corresponding PSCCH and/or PSCCH can be correctly decoded; a NACK is sent when data carried by the corresponding PSCCH and/or PSCCH cannot be correctly decoded). "ACK" and "NACK" may be referred to as HARQ-ACK value.
The "psch transmission occasion" and the "psch reception occasion" may be considered to be defined from the perspective of the TX UE and the RX UE, respectively, e.g., one "psch transmission occasion" may be considered to be one "psch reception occasion" from the perspective of the RX UE and one "psch reception occasion" may be considered to be one "psch transmission occasion" from the perspective of the TX UE.
In the time domain, the PSFCH resource may occur periodically in a resource pool, such as a corresponding period (e.g., referred to as a "PSFCH period" or a "PSFCH resource period," e.g., noted as "PSFCH period")
Figure BDA0002617605070000191
E.g., in number of slots) may be configured, e.g., as a function of parameter Period psfchreresource (or parameter sl-PSFCH-Period)
Figure BDA0002617605070000192
Or
Figure BDA0002617605070000193
Or
Figure BDA0002617605070000194
Or
Figure BDA0002617605070000195
). Wherein the content of the first and second substances,
Figure BDA0002617605070000201
may be used to indicate that no PSFCH resources are configured in the corresponding resource pool. For example, if a resource pool is not configured with a PSFCH related parameter (e.g., a parameter configured through sl-PSFCH-Config) or a PSFCH period configured in the parameter sl-PSFCH-Config is 0, it indicates that the resource pool is not configured with a PSFCH resource. For another example, if a resource pool has configured the parameter sl-PSFCH-Config and the PSFCH period configured in the parameter sl-PSFCH-Config is greater than 0 time slot, it indicates that the resource pool has configured the PSFCH resource.
One slot in which the PSFCH resources are configured may be referred to as a "PSFCH slot. Within a PSFCH slot, the symbols related to the transmission of the PSFCH may be the last SL symbol or symbols of the slot, e.g. for a PSFCH format 0, the last three SL symbols (e.g. symbols)
Figure BDA0002617605070000202
(symbol)
Figure BDA0002617605070000203
And symbols
Figure BDA0002617605070000204
Figure BDA0002617605070000205
Wherein, the symbol
Figure BDA0002617605070000206
Can be used for AGC and, in addition, the content transmitted on the symbol can be copied from the symbol
Figure BDA0002617605070000207
Up-transmittingContent); symbol
Figure BDA0002617605070000208
May be used for PSFCH transmission; symbol
Figure BDA0002617605070000209
May be used as a GAP symbol, or a GUARD (GUARD) symbol. Other symbols of one PSFCH slot may be used to transmit other SL signals/channels, such as PSCCH, etc.
In a resource pool with PSFCH resources configured,
Figure BDA00026176050700002010
a slot (e.g., such a slot is referred to as a "pscch slot") may be associated with a PSFCH slot. For example, the association may be as follows:
a said
Figure BDA00026176050700002011
The PSSCH slots are consecutive slots in the resource pool.
For said
Figure BDA00026176050700002012
Each one of PSSCH in which the PSFCH slot is located at least in the resource pool
Figure BDA00026176050700002013
The first PSFCH slot after a slot. Wherein the content of the first and second substances,
Figure BDA00026176050700002014
it may be configured by the parameter sl-MinTimeGapPSFCH.
For example, if
Figure BDA00026176050700002015
And time slot rn+5If it is a PSFCH time slot in the resource pool, the time slot r in the resource poolnTime slot rn+1Time slot rn+2And time slot rn+3Is associated to the PSFCH time slot rn+5
In the frequency domain, a PSFCH resource in a resource pool may correspond to a size of a PSFCH resource
Figure BDA0002617605070000211
E.g., a set of contiguous PRBs, such as a set of partially or fully non-contiguous PRBs. Wherein the content of the first and second substances,
Figure BDA0002617605070000212
the configuration may be performed by the parameter rbSetSFCH, or by the parameter sl-PSFCH-RB-Set.
In code domain, PSFCH resources within a resource pool may correspond to
Figure BDA0002617605070000213
A cyclic shift pair (cyclic shift pair). Wherein the content of the first and second substances,
Figure BDA0002617605070000214
may be configured or indicated by a higher layer protocol (e.g., configured by a parameter sl-NumMuxCS-Pair).
In a resource pool with allocated PSFCH resources, recording the associated PSFCH time slot in a PSFCH time slot
Figure BDA0002617605070000215
Each PSSCH time slot is a time slot
Figure BDA0002617605070000216
Figure BDA0002617605070000217
Of the resource pool
Figure BDA0002617605070000218
The number of the sub-channels is respectively
Figure BDA0002617605070000219
The resource pool is configured
Figure BDA00026176050700002110
The PRBs used for the PSFCH are respectively numbered as
Figure BDA00026176050700002111
The time slot i and the sub-channel j may correspond to a PRB (or set of PRBs, where the number of PRBs is indicated by an interval)
Figure BDA00026176050700002112
Figure BDA00026176050700002113
Wherein
Figure BDA00026176050700002114
Figure BDA00026176050700002115
For occupation in time slot i starting from sub-channel j
Figure BDA00026176050700002116
One PSSCH transmission for several consecutive sub-channels, and the corresponding PSFCH resource can occupy
Figure BDA00026176050700002117
A PRB, wherein,
Figure BDA00026176050700002118
the value of (d) may be an integer. For example,
Figure BDA00026176050700002119
(e.g., when the parameter sl-PSFCH-CandidateResourceType is configured to "startSubCH"). In another example of this application, a,
Figure BDA00026176050700002120
(e.g., when the parameter sl-PSFCH-CandidateResourceType is configured to "allocSubCH"), at this point in time, the
Figure BDA00026176050700002121
Each PRB can be composed of a PRB range corresponding to a time slot i and a sub-channel j, a PRB range corresponding to a time slot i and a sub-channel j +1, … …, a time slot i and a sub-channel
Figure BDA00026176050700002122
Corresponding PRB range components.
The above-mentioned
Figure BDA00026176050700002123
One PRB may correspond to
Figure BDA00026176050700002124
Figure BDA00026176050700002125
The index (or number) of the "PSFCH resource" (PSFCH resource) can be according to
Figure BDA00026176050700002126
The PRB indexes (or numbers) of the PRBs are indexed (or numbered) in an increasing order, and then the indexes (or numbers) are indexed according to the PRB indexes (or numbers) of the PRBs
Figure BDA00026176050700002127
The cyclic shift pairs of the cyclic shift pairs index (or number) in increasing order. It can be seen that a "PSFCH resource" may correspond to a particular combination of time domain resources, frequency domain resources, and code domain resources.
A "PSFCH transmission occasion" (PSFCH transmission occasion) may be one or more time and/or frequency and/or code domain resources related to (e.g., used by) a PSFCH transmission and/or reception, such as one of the following:
one slot configured with PSFCH resources.
One PSFCH slot.
One slot in a resource pool in which PSFCH resources are configured.
One PSFCH slot in one resource pool.
One or more symbols associated with a PSFCH transmission (e.g., the last three SL symbols in a PSFCH slot, as well as symbols used to transmit PSFCH in a PSFCH slot (e.g., the second-to-last SL symbol) and symbols used for AGC (e.g., the third-to-last SL symbol), etc.).
One or more symbols associated with a PSFCH reception (e.g., the last three SL symbols in a PSFCH slot, as well as symbols used to transmit PSFCH in a PSFCH slot (e.g., the second-to-last SL symbol) and symbols used for AGC (e.g., the third-to-last SL symbol), etc.).
One PSFCH resource.
Time domain resources corresponding to one PSFCH resource.
Frequency domain resources corresponding to one PSFCH resource.
Code domain resources corresponding to one PSFCH resource.
Time domain resources and frequency domain resources corresponding to one PSFCH resource.
Time domain resources and code domain resources corresponding to one PSFCH resource.
Frequency domain resources and code domain resources corresponding to one PSFCH resource.
Time domain resources, frequency domain resources, and code domain resources corresponding to one PSFCH resource.
One or more PSFCH resources.
Time domain resources corresponding to one or more PSFCH resources.
Frequency domain resources corresponding to one or more PSFCH resources.
Code domain resources corresponding to one or more PSFCH resources.
Time domain resources and frequency domain resources corresponding to one or more PSFCH resources.
Time domain resources and code domain resources corresponding to one or more PSFCH resources.
Frequency domain resources and code domain resources corresponding to one or more PSFCH resources.
Time domain resources, frequency domain resources, and code domain resources corresponding to one or more PSFCH resources.
The definition of "PSFCH transmission occasion" may apply to only one resource pool (i.e. the "PSFCH transmission occasion" is defined separately in each resource pool), or may apply to multiple resource pools (e.g. one "PSFCH transmission occasion" may comprise time domain and/or frequency domain and/or code domain resources in multiple resource pools).
A "PSFCH reception occasion" may be one or more time and/or frequency and/or code domain resources related to (e.g., used by) a PSFCH transmission and/or reception, e.g., one or more PSFCH transmissions and/or receptions, e.g., one of the following:
one slot configured with PSFCH resources.
One PSFCH slot.
One slot in a resource pool in which PSFCH resources are configured.
One PSFCH slot in one resource pool.
One or more symbols associated with a PSFCH transmission (e.g., the last three SL symbols in a PSFCH slot, as well as symbols used to transmit PSFCH in a PSFCH slot (e.g., the second-to-last SL symbol) and symbols used for AGC (e.g., the third-to-last SL symbol), etc.).
One or more symbols associated with a PSFCH reception (e.g., the last three SL symbols in a PSFCH slot, as well as symbols used to transmit PSFCH in a PSFCH slot (e.g., the second-to-last SL symbol) and symbols used for AGC (e.g., the third-to-last SL symbol), etc.).
One PSFCH resource.
Time domain resources corresponding to one PSFCH resource.
Frequency domain resources corresponding to one PSFCH resource.
Code domain resources corresponding to one PSFCH resource.
Time domain resources and frequency domain resources corresponding to one PSFCH resource.
Time domain resources and code domain resources corresponding to one PSFCH resource.
Frequency domain resources and code domain resources corresponding to one PSFCH resource.
Time domain resources, frequency domain resources, and code domain resources corresponding to one PSFCH resource.
One or more PSFCH resources.
Time domain resources corresponding to one or more PSFCH resources.
Frequency domain resources corresponding to one or more PSFCH resources.
Code domain resources corresponding to one or more PSFCH resources.
Time domain resources and frequency domain resources corresponding to one or more PSFCH resources.
Time domain resources and code domain resources corresponding to one or more PSFCH resources.
Frequency domain resources and code domain resources corresponding to one or more PSFCH resources.
Time domain resources, frequency domain resources, and code domain resources corresponding to one or more PSFCH resources.
The definition of "PSFCH reception occasion" may be applied to only one resource pool (i.e. the "PSFCH reception occasion" is defined separately in each resource pool), or may be applied to multiple resource pools (e.g. one "PSFCH reception occasion" may comprise time domain and/or frequency domain and/or code domain resources in multiple resource pools).
The "PSFCH transmission occasion" and the "PSFCH reception occasion" may be considered to be defined from the perspective of the TX UE and the RX UE, respectively, e.g., one "PSFCH transmission occasion" may be considered to be one "PSFCH reception occasion" from the perspective of the RX UE and one "PSFCH reception occasion" may be considered to be one "PSFCH transmission occasion" from the perspective of the TX UE.
The network side (e.g., a base station, etc.) may configure one or more "SL configuration grants" (or SL grants in short if the context is clear) for a UE (e.g., a TX UE), for example, by using a parameter SL-configuredgontlist. Each SL configuration grant may be associated with periodic psch transmission resources (or may schedule periodic psch transmissions), where the corresponding period may be configured via a parameter SL-PeriodCG, and one or more psch transmission resources may be allocated (or one or more psch transmissions may be scheduled) for each period. The SL configuration grant may be divided into a SL configuration grant type-1 and a SL configuration grant type-2, where the former associated resource may be configured and/or activated and/or deactivated through semi-static signaling (e.g., RRC signaling), the latter associated resource may be configured through semi-static signaling (e.g., RRC signaling), and the configured resource may be dynamically activated and/or deactivated (e.g., through DCI).
The network side (e.g., base station, etc.) may allocate one or more psch transmission resources (or schedule one or more psch transmissions) to a UE (e.g., TX UE) via DCI (e.g., DCI format 3_ 0). Such a resource allocation may be referred to as "dynamic grant" (dynamic grant) to distinguish it from "configured grant" (configured grant).
The network side (e.g., a base station, etc.) may provide (e.g., via RRC configuration, as indicated by DCI) uplink resources (e.g., PUCCH resources, as indicated by PUSCH resources) for a UE (e.g., a TX UE) to report HARQ-ACK information related to SL transmission, e.g., to indicate transmission and/or reception of data and/or control information on SL resources allocated by SL configuration grant or DCI. Such HARQ-ACK information may be referred to as "HARQ-ACK information related to SL transmission reported on UL".
Specifically, HARQ-ACK information reported on the UL relating to SL transmissions may come from (or be based on) one or more reception and/or transmission operations of the UE on the direct link, including, for example, one or more of the following:
PSFCH reception (or PSFCH receptions). For example, after the base station transmits the PSSCH on the SL resource indicated by the DCI, the TX UE receives the PSFCH transmitted by the RXUE on the PSFCH slot associated with the slot where the PSSCH is located, acquires HARQ-ACK information related to SL transmission reported on the SL, and thereby determines corresponding HARQ-ACK information related to SL transmission reported on the UL.
PSFCH-free reception (absence of PSFCH reception, or absence of PSFCH reception). For example, the reception of the PSFCH cannot be performed in the time slot in which it would otherwise be needed due to performing other higher priority tasks (e.g., performing higher priority UL transmissions). As another example, the SCI of a scheduled data transmission on the direct link indicates that a UE that does not need to receive the data transmission sends a HARQ-ACK (e.g., a HARQ-ACK carried over the PSFCH). As another example, the PSCCH and/or PSCCH is not transmitted due to not detecting DCI (e.g., DCI format 3_0) scheduling the corresponding PSCCH and/or PSCCH transmission, and accordingly the PSFCH is also not received. As another example, the PSFCH resource is not configured in the corresponding resource pool. As another example, a PSFCH is not detected at the corresponding PSFCH reception opportunity.
PSCCH and/or PSCCH transmissions. For example, the TX UE transmits PSCCH and/or PSCCH on SL resources indicated by the base station through DCI.
No PSCCH and/or PSCCH transmission. For example, transmission of the PSCCH and/or PSCCH cannot be performed in a slot that would otherwise require transmission of the PSCCH and/or PSCCH due to performing other higher priority tasks, such as performing higher priority UL transmissions. As another example, the PSCCH and/or PSCCH is not transmitted because a DCI (e.g., DCI format 3_0) scheduling the corresponding PSCCH and/or PSCCH transmission is not detected.
In contrast, the UE may also report HARQ-ACK information related to DL transmission on uplink resources (e.g., PUCCH, also like PUSCH) (and accordingly, use HARQ-ACK codebook related to DL transmission) for feeding back transmission and/or reception conditions (e.g., transmission and/or reception status; also like transmission and/or reception result; also like no transmission is performed; also like no reception is performed; and so on) of data and/or control information on the downlink. Such HARQ-ACK information may be referred to as "HARQ-ACK information related to DL transmission reported on UL". In particular, HARQ-ACK information reported on the UL relating to DL transmissions may come from (or be based on) some reception operations of the UE on the downlink, including for example one or more of the following:
PDSCH reception with corresponding PDCCH reception.
PDSCH reception without corresponding PDCCH reception (e.g., SPS PDSCH reception).
PDCCH reception. For example, an "SPS PDSCH release" indication is indicated in DCI carried by the PDCCH. As another example, an "SCell dormant" (SCell dormant) is indicated in DCI carried by PDCCH.
In all embodiments and implementations of the present invention, "HARQ-ACK information" refers to HARQ-ACK information related to SL transmission reported on UL, as not particularly described.
For end in time slot n
Figure BDA0002617605070000261
One PSFCH reception opportunity (e.g., the time slot n is the
Figure BDA0002617605070000262
The last one of the slots corresponding to each of the PSFCH reception occasions), the UE reports (or provides) the corresponding HARQ-ACK information in one UL transmission in slot n + k. At this time, the offset between the timeslot n to the timeslot n + k may be said to satisfy "timing relationship between PSFCH and uplink HARQ feedback". Wherein the content of the first and second substances,
optionally, the system may be adapted to,
Figure BDA0002617605070000263
is an integer, and
Figure BDA0002617605070000264
for example,
Figure BDA0002617605070000265
in another example
Figure BDA0002617605070000266
In another example of this application, a,
Figure BDA0002617605070000267
optionally, the time slot n and the time slot n + k are numbered according to the time slot used for the UL transmission (i.e. according to the SCS and/or CP used for the UL transmission). Or, the SCS and/or CP corresponding to the time slot n and the time slot n + k are the SCS and/or CP used for the UL transmission, respectively.
Optionally, the
Figure BDA0002617605070000271
A PSFCH reception opportunity (or the PSFCH reception opportunity
Figure BDA0002617605070000272
Time slot where each PSFCH receiving opportunity is located) is respectively associated with the same DCI format (e.g., DCI format 3_0) scheduling
Figure BDA0002617605070000273
A PSSCH transmission. Wherein the content of the first and second substances,
alternatively, the value of the offset "k" may be one of the set configured by the parameter sl-PSFCH-topcch, indicated by a "PSFCH-to-HARQ feedback timing indicator" field in the DCI.
Alternatively, the first phase may be performed,
Figure BDA0002617605070000274
equal to the number of PSSCH transmissions scheduled by the DCI format.
Alternatively, the first phase may be performed,
Figure BDA0002617605070000275
is a predefined integer. For example
Figure BDA0002617605070000276
Optionally, at this time, the
Figure BDA0002617605070000277
The one psch transmission may be any one psch transmission scheduled by the DCI format.
Optionally, the
Figure BDA0002617605070000278
A PSFCH reception opportunity (or the PSFCH reception opportunity
Figure BDA0002617605070000279
Time slot in which one PSFCH reception opportunity is located) respectively associated with scheduling of the same SL configuration grant in the same cycle
Figure BDA00026176050700002710
A PSSCH transmission.
Alternatively, the offset "k" may be configured by a parameter sl-PSFCH-ToPUCCH-CG-type.
Alternatively, the value of the offset "k" may be one of the set configured by the parameter SL-PSFCH-topcch, indicated by a "PSFCH-to-harq feedback timing" field in one DCI format (e.g., a DCI format that activates the SL configuration grant).
Alternatively, the first phase may be performed,
Figure BDA00026176050700002711
equal to the number of PSSCH transmissions scheduled by the DCI format.
Alternatively, the first phase may be performed,
Figure BDA00026176050700002712
is a predefined integer. For example
Figure BDA00026176050700002713
Optionally, at this time, the
Figure BDA00026176050700002714
The one psch transmission may be any one psch transmission scheduled by the DCI format.
Optionally, the UL transmission may be one PUCCH transmission.
Optionally, the UL transmission may be one PUSCH transmission.
One or more HARQ-ACK information bits generated (or provided, or reported) by the UE in slot n + k may be included in a "HARQ-ACK codebook" (or, alternatively, an instance of a "HARQ-ACK codebook") in a certain order and/or structure and/or organization. One or more HARQ-ACK information bits in one HARQ-ACK codebook may be multiplexed on one PUCCH transmission or on one PUSCH transmission. In all embodiments and implementations of the present invention, the "HARQ-ACK codebook" refers to a HARQ-ACK codebook containing "HARQ-ACK information related to SL transmission reported on UL", as not particularly described.
The UE may be configured to report the HARQ-ACK information in a Type-1 (Type-1) HARQ-ACK codebook (codebook) or in a Type-2 (Type-2) HARQ-ACK codebook. The size of the type-1 HARQ-ACK codebook may depend only on semi-static configuration information (e.g., configuration information of the RRC layer); the size of the type-2 HARQ-ACK codebook may be dynamically varied (e.g., based on the number of detected DCI formats associated with the HARQ-ACK codebook, etc.), e.g., the number of HARQ-ACK information bits in the type-2 HARQ-ACK based codebook transmitted on two different PUCCH slots may be different. If there is a PUSCH transmission on the slot where the PUCCH resource is located, the UE may multiplex the HARQ-ACK information on the PUSCH transmission.
The HARQ-ACK information within the HARQ-ACK codebook may be associated with one or more SL configuration grants.
The HARQ-ACK information within the HARQ-ACK codebook may be associated with one or more DCI formats (e.g., DCI format 3_ 0). Wherein each of the one or more DCI formats may be used for one or more purposes related to data and/or control information transmitted on a direct uplink, including, for example, one or more of:
scheduling PSCCH and/or PSCCH transmissions. At this time, the CRC of the DCI format is optionally scrambled using SL-RNTI or SL-CS-RNTI.
Indicate SL configuration license (e.g., SL configuration license type-2) activation.
Indicate release of the SL configuration license (e.g., SL configuration license type-2).
[ example one ]
A method performed by a user equipment according to a first embodiment of the present invention is described below with reference to fig. 1.
Fig. 1 is a flowchart illustrating a method performed by a user equipment according to a first embodiment of the present invention.
As shown in fig. 1, in a first embodiment of the present invention, a user equipment UE performs steps including: step S101 and step S103.
Specifically, in step S101, N is determinedoccasionSL opportunities.
Optionally, the NoccasionAny one of the SL opportunities may be one of the following:
psch transmission occasions. Wherein the content of the first and second substances,
alternatively, one psch transmission occasion may be used for one "candidate psch transmission", where one "candidate psch transmission" may represent any one actual psch transmission on the corresponding psch transmission occasion.
PSFCH reception opportunity. Wherein the content of the first and second substances,
alternatively, one PSFCH reception opportunity may be used for one "candidate PSFCH reception", wherein one "candidate PSFCH reception" may represent any one actual PSFCH reception on the corresponding PSFCH reception opportunity.
Psch reception timing. Wherein the content of the first and second substances,
alternatively, one psch reception occasion may be used for one "candidate psch reception", where one "candidate psch reception" may represent any one actual psch reception at the corresponding psch reception occasion.
PSFCH transmission opportunity. Wherein the content of the first and second substances,
alternatively, one PSFCH transmission opportunity may be used for one "candidate PSFCH transmission", wherein one "candidate PSFCH transmission" may represent any one actual PSFCH transmission on the corresponding PSFCH transmission opportunity.
Alternatively, NoccasionIs a predefined integer. E.g. Noccasion1 as another example Noccasion2 as another example Noccasion=3。
Alternatively, NoccasionRelated to the configuration of the search space.
Alternatively, NoccasionRelated to controlling the configuration of resource sets.
Alternatively, NoccasionRelated to the configuration of PDCCH monitoring occasion (PDCCH monitoring occasion).
Alternatively, NoccasionRelating to DCI detection operations (e.g. determining N from detected DCI)occasionValue of (d). E.g. NoccasionIs equal to the number of PSSCH transmissions scheduled by one DCI format (e.g., DCI format 3_0) detected at one PDCCH monitoring occasion (e.g., Noccasion1 as another example Noccasion2 as another example Noccasion3). Wherein the content of the first and second substances,
optionally, the NoccasionEach SL opportunity is N scheduled by the DCI formatoccasionThe PSSCH transmission occasion on which the PSSCH transmission is located.
Optionally, if the DCI format is not detected at the PDCCH monitoring occasion, it is assumed that there is no SL occasion corresponding to the PDCCH monitoring occasion.
Optionally, if the DCI format is not detected at the PDCCH monitoring occasion, the corresponding Noccasion=0。
Alternatively, NoccasionAssociated with one or more SL configuration permissions. E.g. NoccasionEqual to the number of PSSCH transmissions scheduled in one period for one SL configuration grant (e.g., N)occasion1 as another example Noccasion2 as another example Noccasion3). Wherein the content of the first and second substances,
optionally, the NoccasionEach SL opportunity is N scheduled by the SL configuration permission in one periodoccasionThe PSSCH transmission occasion on which the PSSCH transmission is located.
Optionally, the NoccasionA given time slot n may be associated with a SL opportunityUOne UL transmission in (2). Wherein the content of the first and second substances,
optionally, the UL transmission may be one PUCCH transmission.
Optionally, the UL transmission may be one PUSCH transmission.
Optionally, the NoccasionOne SL occasion corresponds to one HARQ-ACK information bit. Wherein the HARQ-ACK information bits are carried in the UL transmission.
Optionally, the NoccasionMultiple SL opportunities may belong to a set of SL opportunities. Wherein the content of the first and second substances,
optionally, the set of SL occasions have corresponding HARQ-ACK information (e.g., every N in the set of SL occasionsoccasionOne SL occasion for one HARQ-ACK information bit), which is multiplexed on the UL transmission.
Optionally, the set of SL occasions may correspond to a HARQ-ACK codebook (e.g., a type-1 HARQ-ACK codebook, such as a type-2 HARQ-ACK codebook).
Optionally, the NoccasionSL timing is NoccasionOne psch transmission opportunity. Wherein the content of the first and second substances,
alternatively, the NoccasionNumber of PSSCH Transmission occasions (or the NoccasionThe psch slots in which the respective psch transmission occasions are located) are associated to the same pscfh slot (e.g., denoted as slot n)S,1) And said time slot nS,1To said time slot nUThe offset between them satisfies "timing relationship between PSFCH to uplink HARQ feedback". Alternatively, Noccasion=1。
Alternatively, the NoccasionThe PSSCH transmission occasions are determined by one PDCCH monitoring occasion. For example, the NoccasionThe PSSCH transmission occasions are respectively N scheduled by one DCI format (e.g. DCI format 3_0) detected at the PDCCH monitoring occasionoccasionPSSCH transmission occasion at which each PSSCH transmission is located, and corresponding NoccasionThe slot in which the last of the PSFCH receive opportunities is located (e.g., denoted as slot n)S,2) To said time slot nUThe offset between them satisfies "timing relationship between PSFCH to uplink HARQ feedback".
Optionally, the NoccasionSL timing is NoccasionOne PSFCH receive opportunity. Wherein the content of the first and second substances,
alternatively, the NoccasionFor one PSFCH reception opportunityThe last slot (or the NoccasionLast one of the PSFCH slots in which one PSFCH reception opportunity is respectively located) to the slot nUThe offset between them satisfies "timing relationship between PSFCH to uplink HARQ feedback". Alternatively, Noccasion=1。
Further, in step S103, the N is determinedoccasionOne HARQ-ACK information bit corresponding to one SL occasion.
Optionally, the HARQ-ACK information bit is NACKOne HARQ-ACK information bit (e.g., respectively denoted as
Figure BDA0002617605070000321
) One of them. Wherein the content of the first and second substances,
optionally, the NACKOne HARQ-ACK information bit
Figure BDA0002617605070000322
Is one or more of the UE multiplexed on one PUCCH transmission or one PUSCH transmission (e.g., denoted as O)ACKNumber) of HARQ-ACK information bits (i.e., N)ACK<0ACKOr N isACK=OACK)。
Optionally, the NACKOne HARQ-ACK information bit
Figure BDA0002617605070000323
Contained in the type-1 HARQ-ACK codebook.
Optionally, the NACKOne HARQ-ACK information bit
Figure BDA0002617605070000324
Contained in the type-2 HARQ-ACK codebook.
Optionally, determining that the HARQ-ACK information bits include one or more of:
determining a HARQ-ACK value for the HARQ-ACK information bits. Wherein the content of the first and second substances,
optionally, the set of values of HARQ-ACK values may be one of:
ο{ACK,NACK}。
ο{ACK}。
ο{NACK}。
optionally, where applicable, the "determining HARQ-ACK values for the HARQ-ACK information bits" may also be expressed as "generating HARQ-ACK values for the HARQ-ACK information bits", or "generating one HARQ-ACK value for the HARQ-ACK information bits", or "generating N HARQ-ACK values for the HARQ-ACK information bitsoccasionOne HARQ-ACK value is generated at each SL opportunity, or the value is' N corresponding to the HARQ-ACK information bitoccasionOne of the SL occasions (e.g., the last one) generates one HARQ-ACK value ". For example, one ACK is generated for the HARQ-ACK information bits. As another example, a NACK may be generated for the HARQ-ACK information bits.
Determining a priority value (priority value) of the HARQ-ACK information bits, e.g., as
Figure BDA0002617605070000331
Wherein the content of the first and second substances,
optionally, the priority value
Figure BDA0002617605070000332
For determining a priority value (e.g., noted as
Figure BDA0002617605070000333
). Wherein the content of the first and second substances,
optionally, the priority value
Figure BDA0002617605070000334
For prioritizing between the UL transmission and one SL transmission (e.g., when the UL transmission and the SL transmission overlap in time). For example, if the UE cannot perform the UL transmission and the SL transmission simultaneously or cannot perform the UL transmission and the SL transmission simultaneously in one serving cell, the UE transmits only the higher priority of the two. Wherein the content of the first and second substances,
optionally, the Priority of the corresponding SL transmission is determined by the "Priority" field in the SCI with which it is associated. For example, a Priority value of the SL transmission is determined as the value of the "Priority" field. As another example, the Priority value of the SL transmission is determined as the value of the "Priority" field plus 1.
Optionally, the higher priority value of the UL transmission and the SL transmission is prioritized higher.
Optionally, the higher priority value of the UL transmission and the SL transmission is prioritized lower.
Optionally, the UL transmission may be one PUCCH transmission.
Optionally, the UL transmission may be a PUSCH transmission.
Optionally, the priority value
Figure BDA0002617605070000341
Is the minimum of the priority values of all HARQ-ACK information bits multiplexed on the UL transmission.
Optionally, the priority value
Figure BDA0002617605070000342
Is the maximum of the priority values of all HARQ-ACK information bits multiplexed on the UL transmission.
Optionally, the priority value
Figure BDA0002617605070000343
The set of values of (a) may be one of the following:
ο{0,1,2,3,4,5,6,7}。
ο{1,2,3,4,5,6,7,8}。
optionally, different protocol layers pair the priority values
Figure BDA0002617605070000344
May be different, in which case the priority value is different
Figure BDA0002617605070000345
The fat is a priority value defined in the applicable protocol layer. For example, a value set of priority values defined by a first protocol layer (e.g., a physical layer) is {0, 1, 2, 3, 4, 5, 6, 7}, and a value set of priority values defined by a second protocol layer (e.g., a MAC layer, such as an RRC layer, etc.) is {1, 2, 3, 4, 5, 6, 7, 8}, where a priority value 0 of the first protocol layer corresponds to a priority value 1 of the second protocol layer, a priority value 1 of the first protocol layer corresponds to a priority value 2, … … of the second protocol layer, and a priority value 7 of the first protocol layer corresponds to a priority value 8 of the second protocol layer.
Alternatively, the "determining the priority value of the HARQ-ACK information bit" may also be expressed as "generating the priority value of the HARQ-ACK information bit", or "generating one priority value for the HARQ-ACK information bit". For example, a priority value of 0 is generated for the HARQ-ACK information bit. As another example, a priority value of 7 is generated for the HARQ-ACK information bits.
Optionally, the priority of the HARQ-ACK information bits is dependent on the corresponding priority value
Figure BDA0002617605070000351
Is increased and decreased.
Optionally, the priority of the HARQ-ACK information bits is dependent on the corresponding priority value
Figure BDA0002617605070000352
Is increased.
Alternatively, if Noccasion1, and said NoccasionIf the SL opportunity is a psch transmission opportunity (e.g., referred to as a first psch transmission opportunity) and the first psch transmission opportunity is a psch transmission opportunity in which one of one or more psch transmissions (e.g., referred to as a first psch transmission) is scheduled by one DCI format (or one SL configuration grant is scheduled in one cycle), the HARQ-ACK value and/or the priority value of the HARQ-ACK information bit is determined as follows:
determining a HARQ-ACK value for the HARQ-ACK information bits according to PSFCH reception on one or more PSFCH reception occasions associated with the first PSSCH transmission. For example, if the first psch transmission is a unicast transmission and an "ACK" is received on the PSFCH reception occasion associated with the first psch transmission, the HARQ-ACK value for the HARQ-ACK information bit is determined to be an "ACK". For another example, if the first psch transmission is a unicast transmission and a "NACK" is received at a pscch reception occasion associated with the first psch transmission, the HARQ-ACK value of the HARQ-ACK information bit is determined to be a "NACK".
Determining the Priority of the HARQ-ACK information bits according to a "Priority" field in the SCI (e.g. first stage SCI) with which the first psch transmission is associated. For example, the Priority value of the HARQ-ACK information bit is determined as the value of the "Priority" field in the SCI (e.g., first stage SCI) with which the first psch transmission is associated. As another example, the Priority value of the HARQ-ACK information bit is determined as the value of the "Priority" field in the SCI (e.g., first stage SCI) associated with the first psch transmission plus 1.
Alternatively, if the first SL operation is not performed due to the first miss (e.g., at the NoccasionA first SL operation is performed on several SL occasions), the HARQ-ACK value and/or priority of the HARQ-ACK information bits is determined in a first determined manner. Wherein the content of the first and second substances,
optionally, the first missing cause may include one or more of the following (in any combination of and or, where applicable):
no corresponding DCI format (e.g., DCI format 30) is detected. Wherein the content of the first and second substances,
optionally, the "corresponding DCI format" shall schedule NoccasionRespectively at the NoccasionPscch transmission on several SL occasions. For example, if Noccasion1, said NoccasionIf there is one psch transmission occasion for SL, then the "corresponding DCI format" should schedule one psch transmission on the psch transmission occasion.
Optionally, said corresponding DCI Format "scheduled PSSCH Transmission or PSSCH Transmission should include NoccasionRespectively at the NoccasionPscch transmission on several SL occasions. For example, if Noccasion1, said NoccasionIf the SL occasion is a psch transmission occasion, then the one or more psch transmissions scheduled by the "corresponding DCI format" should include a psch transmission on the psch transmission occasion.
Optionally, one or more PSSCH transmissions scheduled by the "corresponding DCI format" should be triggered to include the NoccasionPSFCH reception on one SL occasion. For example, if Noccasion1, said NoccasionIf SL occasion is a PSFCH reception occasion, then one or more PSSCH transmissions scheduled by the "corresponding DCI format" should trigger a PSFCH reception on the reception occasion comprising the PSFCH.
Priority reasons (e.g. at the N)occasionThere may be other higher priority SL (or UL) transmission or reception operations on some or all of the SL opportunities).
No data (e.g. data from higher layer protocols) needs to be transmitted. For example, the UE does not have any newly generated or yet unacknowledged transport blocks to transmit on the corresponding direct link.
The first SL operation may be one of the following:
in the NoccasionThe PSSCH is transmitted for several SL occasions. Wherein the content of the first and second substances,
o optionally, at this point, the NoccasionSL timing is NoccasionMultiple PSSCH Transmission opportunity (e.g., N)occasion=1)。
In the NoccasionOne SL opportunity receives the PSFCH. Wherein the content of the first and second substances,
o optionally, at this point, the NoccasionSL timing is NoccasionOne PSFCH reception opportunity (e.g., N)occasion=1)。
In the NoccasionThe PSSCH is received at several SL occasions. Wherein the content of the first and second substances,
o optionally, at this point, the NoccasionSL timing is NoccasionMultiple PSSCH reception occasions (e.g., N)occasion=1)。
In the NoccasionOne SL opportunity transmits PSFCH. Wherein the content of the first and second substances,
o optionally, at this point, the NoccasionSL timing is NoccasionOne PSFCH transmission opportunity (e.g., N)occasion=1)。
Optionally, the "determining HARQ-ACK values and/or priorities of the HARQ-ACK information bits in a first determined manner" comprises one or more of:
determining the HARQ-ACK value of the HARQ-ACK information bit as a predefined value, e.g. ACK, again as NACK.
Determining a HARQ-ACK value of the HARQ-ACK information bit as a pre-configured or configured value.
Determining the priority value of the HARQ-ACK information bit to be a predefined value, for example, 0, as well as 1, as well as 2, as well as 3, as well as 4, as well as 5, as well as 6, as well as 7, as well as 8, as well as a maximum priority value (i.e., the value of the largest element in the set of values of the priority value, for example, 7 in {0, 1, 2, 3, 4, 5, 6, 7}, as well as 8 in {1, 2, 3, 4, 5, 6, 7, 8 }), as well as a minimum priority value (i.e., the value of the smallest element in the set of values of the priority value, for example, 0 in {0, 1, 2, 3, 4, 5, 6, 7}, as well as 1 in {1, 2, 3, 4, 5, 6, 7, 8 }).
Determining a priority value of the HARQ-ACK information bits as a pre-configured or configured value.
Optionally, in the first embodiment of the present invention, the "SL transmission" may refer to a PSCCH transmission.
Optionally, in the first embodiment of the present invention, the "SL transmission" may refer to a psch transmission.
Optionally, in the first embodiment of the present invention, the "SL transmission" may refer to PSCCH and/or PSCCH transmission.
Optionally, in the first embodiment of the present invention, the "SL transmission" may refer to PSFCH transmission.
Optionally, in the first embodiment of the present invention, the "PSCCH transmission" may be replaced with "PSCCH and/or PSCCH transmission".
Alternatively, embodiment one of the present invention may be applied to an SL BWP in a serving cell (e.g., PCell, also like PSCell, also like SpCell, also like SCell, also like other serving cells).
Alternatively, the first embodiment of the present invention may be applied to an UL BWP (e.g. currently activated UL BWP, active UL BWP) in a serving cell (e.g. PCell, also like PSCell, also like SpCell, also like SCell, also like other serving cells).
Optionally, the UE may determine the "N" by performing embodiment one of the present invention one or more timesoccasionAll SL occasions in the set of SL occasions to which the SL occasions "belong, and the HARQ-ACK values and/or priority values of the corresponding HARQ-ACK information bits.
Thus, according to the first embodiment, the present invention provides a method, by setting the HARQ-ACK value and the priority value of the HARQ-ACK information bit in the default condition (e.g. when the DCI scheduling the psch transmission is not detected), the reported HARQ-ACK information completely reflects the HARQ-ACK feedback condition of the direct link, and the priority of the uplink channel carrying the HARQ-ACK information accurately reflects the priority of data transmission on the direct link.
[ modified examples ]
As a modification, a user equipment capable of executing the method performed by the user equipment described in detail above of the present invention is explained below with reference to fig. 2.
Fig. 2 is a block diagram showing a user equipment UE according to the present invention.
As shown in fig. 2, the user equipment UE20 includes a processor 201 and a memory 202. The processor 201 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like. The memory 202 may include, for example, volatile memory (e.g., random access memory RAM), a Hard Disk Drive (HDD), non-volatile memory (e.g., flash memory), or other memory, among others. The memory 202 has stored thereon program instructions. Which when executed by the processor 201 may perform the above-described method performed by the user equipment as described in detail in the present invention.
The method of the invention and the apparatus involved have been described above in connection with preferred embodiments. It will be appreciated by those skilled in the art that the above illustrated approaches are exemplary only, and that the various embodiments described above can be combined with each other without conflict. The method of the present invention is not limited to the steps or sequence shown above. The network nodes and user equipment shown above may comprise further modules, e.g. modules that may be developed or developed in the future, available for a base station, AMF, UPF, MME, S-GW or UE, etc. The various identifiers shown above are exemplary only and not limiting, and the invention is not limited to the specific information elements that are examples of these identifiers. Many variations and modifications may occur to those skilled in the art in light of the teachings of the illustrated embodiments. It will be understood by those skilled in the art that some or all of the mathematical expressions or mathematical equations or mathematical inequalities may be simplified or transformed or rewritten to some extent, such as by combining constant terms, exchanging two additive terms, exchanging two multiplicative terms, shifting a term from the left to the right of an equation or inequality after changing the sign, shifting a term from the right to the left of an equation or inequality after changing the sign, and so on; simplifying or transforming or rewriting the mathematical expressions or mathematical equations or mathematical inequalities before and after may be considered equivalent.
It should be understood that the above-described embodiments of the present invention can be implemented by software, hardware, or a combination of both software and hardware. For example, various components within the base station and the user equipment in the above embodiments may be implemented by various means, including but not limited to: analog circuit devices, Digital Signal Processing (DSP) circuits, programmable processors, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), programmable logic devices (CPLDs), and the like.
In the present invention, a "base station" may refer to a mobile communication data and/or control switching center having a certain transmission power and a certain coverage area, and for example, includes functions of resource allocation scheduling, data receiving and sending, and the like. "user equipment" may refer to a user mobile terminal, including, for example, a mobile phone, a notebook, etc., which may wirelessly communicate with a base station or a micro base station.
Furthermore, embodiments of the invention disclosed herein may be implemented on a computer program product. More specifically, the computer program product is one of the following: there is a computer readable medium having computer program logic encoded thereon that, when executed on a computing device, provides related operations for implementing the above-described aspects of the present invention. When executed on at least one processor of a computing system, the computer program logic causes the processor to perform the operations (methods) described in embodiments of the present invention. Such arrangements of the invention are typically provided as downloadable software images, shared databases, etc. arranged or encoded in software, code and/or other data structures on a computer readable medium such as an optical medium (e.g., CD-ROM), floppy or hard disk or other medium such as firmware or microcode on one or more ROM or RAM or PROM chips or in one or more modules. The software or firmware or such configurations may be installed on a computing device to cause one or more processors in the computing device to perform the techniques described in embodiments of the present invention.
Further, each functional block or respective feature of the base station device and the terminal device used in each of the above embodiments may be implemented or executed by a circuit, which is typically one or more integrated circuits. Circuitry designed to perform the various functions described in this specification may include a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC) or a general purpose integrated circuit, a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, or discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, or the processor may be an existing processor, controller, microcontroller, or state machine. The general-purpose processor or each circuit described above may be configured by a digital circuit, or may be configured by a logic circuit. Further, when advanced technology capable of replacing the current integrated circuit is developed due to the advancement of semiconductor technology, the present invention can also use the integrated circuit obtained by the advanced technology.
Although the present invention has been described in conjunction with the preferred embodiments thereof, it will be understood by those skilled in the art that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention. Accordingly, the present invention should not be limited by the above-described embodiments, but should be defined by the appended claims and their equivalents.

Claims (4)

1. A method performed by a user equipment, UE, comprising:
determining a PSSCH transmission occasion for a candidate PSSCH transmission associated with a PSFCH slot based on a PSFCH slot satisfying a HARQ-ACK timing configuration from PSFCH to PUCCH, and
if N corresponding to the HARQ-ACK information bit is not existed due to the first omissionoccasionAnd if a first SL operation is executed at each SL opportunity, generating a NACK for the PSSCH transmission opportunity, and determining the priority value of the NACK as a maximum priority value.
2. The method of claim 1,
the first omission reason is that the corresponding DCI format is not detected, or
In said NoccasionSome or all of the SL opportunities have other higher priority transmission or reception operations, or
No data from the higher layer protocol needs to be transmitted.
3. The method of claim 1,
the first SL operation is at the NoccasionThe PSSCH is transmitted for every PSSCH transmission opportunity.
4. A user equipment, comprising:
a processor; and
a memory having stored therein instructions that, when executed,
wherein the instructions, when executed by the processor, perform the method of any of claims 1-3.
CN202010775345.XA 2020-08-04 2020-08-04 Method performed by user equipment and user equipment Pending CN114070486A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010775345.XA CN114070486A (en) 2020-08-04 2020-08-04 Method performed by user equipment and user equipment
PCT/CN2021/108596 WO2022028274A1 (en) 2020-08-04 2021-07-27 Method executed by user equipment, and user equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010775345.XA CN114070486A (en) 2020-08-04 2020-08-04 Method performed by user equipment and user equipment

Publications (1)

Publication Number Publication Date
CN114070486A true CN114070486A (en) 2022-02-18

Family

ID=80119929

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010775345.XA Pending CN114070486A (en) 2020-08-04 2020-08-04 Method performed by user equipment and user equipment

Country Status (2)

Country Link
CN (1) CN114070486A (en)
WO (1) WO2022028274A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023179502A1 (en) * 2022-03-25 2023-09-28 中兴通讯股份有限公司 Information transmission method and device, and storage medium

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3672338B1 (en) * 2017-09-29 2022-11-30 LG Electronics Inc. Method for transmitting v2x message by terminal in wireless communication system, and terminal using same method
US11405144B2 (en) * 2018-09-21 2022-08-02 Kt Corporation Method and apparatus for transmitting sidelink HARQ feedback information
EP3858021A4 (en) * 2018-09-26 2022-06-22 Lenovo (Beijing) Limited Method and apparatus for sidelink communication
CN110311762B (en) * 2019-07-16 2021-04-16 北京紫光展锐通信技术有限公司 Feedback information transmission method, device, terminal and storage medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023179502A1 (en) * 2022-03-25 2023-09-28 中兴通讯股份有限公司 Information transmission method and device, and storage medium

Also Published As

Publication number Publication date
WO2022028274A1 (en) 2022-02-10

Similar Documents

Publication Publication Date Title
US20230124535A1 (en) Method performed by user equipment, and user equipment
US20220361204A1 (en) Method performed by user equipment, and user equipment
CN111867092A (en) Method performed by user equipment and user equipment
WO2022068685A1 (en) Method executed by user equipment, and user equipment
CN113114438A (en) Method performed by user equipment and user equipment
US20230069535A1 (en) Method performed by user equipment, and user equipment
WO2022028274A1 (en) Method executed by user equipment, and user equipment
WO2022028328A1 (en) Method executed by user equipment and user equipment
CN113518099A (en) Method performed by user equipment and user equipment
US20230189302A1 (en) Method performed by user equipment, and user equipment
EP4319216A1 (en) Method executed by user equipment, and user equipment
US20240080866A1 (en) Method performed by user equipment, and user equipment
US20230156745A1 (en) Method performed by user equipment, and user equipment
US20230276473A1 (en) Method performed by user equipment, and user equipment
WO2021136373A1 (en) Method executed by user equipment, and user equipment
US20220417959A1 (en) Method performed by user equipment, and user equipment
WO2021160032A1 (en) Method executed by user equipment and user equipment
US20230309177A1 (en) Method performed by user equipment, and user equipment
WO2021197210A1 (en) Method executed by user equipment, and user equipment
WO2021238757A1 (en) Method executed by user equipment, and user equipment
US20230379121A1 (en) Method performed by user equipment, and user equipment
US20230107902A1 (en) Method performed by user equipment, and user equipment
WO2022206948A1 (en) Method executed by user equipment, and user equipment
WO2021057838A1 (en) Method executed by user equipment, and user equipment
US20230039007A1 (en) Method performed by user equipment, and user equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
WD01 Invention patent application deemed withdrawn after publication
WD01 Invention patent application deemed withdrawn after publication

Application publication date: 20220218