WO2021008587A1 - 由用户设备执行的方法以及用户设备 - Google Patents

由用户设备执行的方法以及用户设备 Download PDF

Info

Publication number
WO2021008587A1
WO2021008587A1 PCT/CN2020/102437 CN2020102437W WO2021008587A1 WO 2021008587 A1 WO2021008587 A1 WO 2021008587A1 CN 2020102437 W CN2020102437 W CN 2020102437W WO 2021008587 A1 WO2021008587 A1 WO 2021008587A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq
layer
information
optionally
identifier
Prior art date
Application number
PCT/CN2020/102437
Other languages
English (en)
French (fr)
Inventor
罗超
刘仁茂
赵毅男
Original Assignee
夏普株式会社
罗超
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 夏普株式会社, 罗超 filed Critical 夏普株式会社
Priority to US17/627,308 priority Critical patent/US20220247539A1/en
Publication of WO2021008587A1 publication Critical patent/WO2021008587A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/1607—Details of the supervisory signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the present invention relates to a method executed by user equipment and user equipment.
  • the downlink assignment (downlink assignment) and the uplink grant (uplink grant) respectively include and require Receive HARQ information (HARQ information) related to the data to be sent.
  • HARQ information Receive HARQ information
  • HARQ information includes new data indicator (New Data Indicator, NDI), transport block size (Transport Block Size, TBS), and HARQ process identifier (HARQ process ID) ;
  • NDI new Data Indicator
  • TBS Transport Block Size
  • HARQ process ID HARQ process ID
  • HARQ information includes NDI, TBS, HARQ process identifier (such as in asynchronous uplink HARQ), and redundancy version (Redundancy Version, RV).
  • RV redundancy Version
  • HARQ information includes NDI, TBS, RV, and HARQ process identifiers.
  • the present invention aims to solve the problem of supporting blind retransmission and/or HARQ retransmission and/or multiple source/target IDs and/or multiple source/target IDs in the physical layer of the UE in 5G V2X (see Non-Patent Document 2 and Non-Patent Document 3).
  • a propagation type how to define HARQ information and the operation related to HARQ information.
  • Non-Patent Document 1 RP-181474, Revised WID on New Radio Access Technology
  • Non-Patent Document 2 RP-181429, New SID: Study on 5G V2X
  • Non-Patent Document 3 RP-190766, New WID on 5G V2X with NR sidelink
  • the present invention provides a method executed by a user equipment and a user equipment.
  • the MAC sublayer of the UE can accurately obtain the HARQ process-related information of a TB.
  • a method executed by a user equipment is proposed, which is characterized by comprising: receiving a physical direct control channel PSCCH including direct control information SCI, the SCI being used to schedule the transmission of the physical direct shared channel PSSCH carrying the transport block TB ; Determine the HARQ information of the hybrid automatic repeat request associated with the TB; and report the HARQ information from the physical layer to the medium access control MAC sublayer.
  • the HARQ information includes one or more of the following: propagation type, layer 1 source identifier, layer 1 target identifier, HARQ process identifier, new data indicator, redundancy version, session identifier, transmission block Size, distance between sender and receiver, communication range requirements, information indicating whether the communication range requirements are met, information indicating whether HARQ feedback is required, and HARQ feedback type.
  • the transmission type includes: any one of unicast and multicast, any one of unicast and broadcast, any one of multicast and broadcast, or any one of unicast, multicast and broadcast.
  • the method further includes: reporting the SCI and/or the TB while reporting the HARQ information.
  • a method executed by a user equipment is proposed, which is characterized by comprising: receiving, from the physical layer, the hybrid automatic repeat request HARQ information associated with the transport block TB at the medium access control MAC sublayer; The TB and/or the HARQ information is allocated to the direct HARQ process.
  • the direct HARQ process to be allocated is determined according to one or more of the following included in the HARQ information: propagation type, layer 1 source identifier, layer 1 target identifier, HARQ process identifier, new data indicator , Redundancy version, session identifier, transport block size, distance between sender and receiver, communication range requirements, information indicating whether the communication range requirements are met, information indicating whether HARQ feedback is required, and HARQ feedback type.
  • a method executed by a user equipment is proposed, which is characterized by: receiving, from the physical layer, the hybrid automatic repeat request HARQ information associated with the transport block TB at the medium access control MAC sublayer; and determining whether Command the physical layer to generate a response to the data in the TB.
  • the physical layer is not instructed to generate a response to the data in the TB; if the no response condition is not established, the physical layer is instructed to generate a response to the data in the TB, wherein the The non-response condition includes one or more of the following: the propagation type in the HARQ information is broadcast, the value of "HARQ feedback is required" in the HARQ information is "No", and the "HARQ feedback" in the HARQ information Type" is "None".
  • the HARQ information includes one or more of the following: propagation type, layer 1 source identifier, layer 1 target identifier, HARQ process identifier, new data indicator, redundancy version, session identifier, transmission block Size, distance between sender and receiver, communication range requirements, information indicating whether the communication range requirements are met, information indicating whether HARQ feedback is required, and HARQ feedback type.
  • a user equipment which includes: a processor; and a memory storing instructions, wherein the instructions execute the above-mentioned method when run by the processor.
  • the MAC sublayer of the UE can accurately obtain the complete information related to the HARQ process of a TB, thereby correctly performing HARQ-related operations and ensuring that the physical layer of the UE supports In the case of blind retransmission and/or HARQ retransmission, multiple transmissions of one TB can be effectively combined, ensuring the performance of HARQ combining.
  • the propagation type in the HARQ information and other information related to the HARQ response determine whether to instruct the physical layer to generate a response to the received TB, ensuring that the HARQ process of the UE supports both transmission based on HARQ feedback and no HARQ feedback Transmission.
  • Fig. 1 is a flowchart showing a method executed by a user equipment according to the first embodiment of the present invention.
  • Fig. 2 is a flowchart showing a method executed by a user equipment according to the second embodiment of the present invention.
  • Fig. 3 is a flowchart showing a method executed by a user equipment according to the third embodiment of the present invention.
  • Fig. 4 is a block diagram schematically showing the user equipment involved in the present invention.
  • 3GPP 3rd Generation Partnership Project
  • the third generation partnership project the third generation partnership project
  • BWP Bandwidth Part, Bandwidth Part
  • CA Carrier Aggregation, carrier aggregation
  • CCE control-channel element, control channel element
  • CORESET control-resource set, control resource set
  • 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, cyclic redundancy check
  • CSI Channel-state Information, channel state information
  • DCI Downlink Control Information, downlink control information
  • DFN Direct Frame Number, direct frame number
  • DFT-s-OFDM Discrete Fourier Transformation Spread Orthogonal Frequency Division Multiplexing, Discrete Fourier Transform Spread Spectrum Orthogonal Frequency Division Multiplexing
  • DL-SCH Downlink Shared Channel, downlink shared channel
  • DM-RS Demodulation reference signal, demodulation reference signal
  • eMBB Enhanced Mobile Broadband, enhanced mobile broadband communications
  • eNB E-UTRAN Node B, E-UTRAN Node B
  • E-UTRAN Evolved UMTS Terrestrial Radio Access Network, the evolved UMTS terrestrial radio access network
  • FDRA Frequency Domain Resource Assignment, frequency domain resource allocation
  • GLONASS GLObal NAvigation Satellite System, Global Navigation Satellite System
  • gNB NR Node B, NR Node B
  • GNSS Global Navigation Satellite System, Global Navigation Satellite System
  • GPS Global Positioning System, Global Positioning System
  • ID Identity (or Identifier), identity, identifier
  • IP Internet Protocol, Internet Protocol
  • LCID Logical Channel ID, logical channel identifier
  • 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 Master Cell Group, primary cell group
  • MIB Master Information Block, master information block
  • MIB-SL Master Information Block-Sidelink, master information block-go straight
  • MIB-SL-V2X Master Information Block-Sidelink-V2X, master information block-straight-go-V2X
  • MIB-V2X Master Information Block-V2X, Master Information Block-V2X
  • mMTC Massive Machine Type Communication, large-scale machine type communication
  • NAS Non-Access-Stratum, non-access layer
  • NDI New Data Indicator, new data indicator
  • NUL Normal Uplink, normal uplink
  • OFDM Orthogonal Frequency Division Multiplexing, Orthogonal Frequency Division Multiplexing
  • PBCH Physical Broadcast Channel, physical broadcast channel
  • PDCCH Physical Downlink Control Channel, physical downlink control channel
  • PDCP Packet Data Convergence Protocol, packet data convergence protocol
  • PDSCH Physical Downlink Shared Channel, physical downlink shared channel
  • PSBCH Physical Sidelink Broadcast Channel, physical direct broadcast channel
  • PSCCH Physical Sidelink Control Channel, physical direct control channel
  • PSFCH Physical Sidelink Feedback Channel, physical direct feedback channel
  • PSSCH Physical Sidelink Shared Channel, physical direct shared channel
  • PRB Physical Resource Block, physical resource block
  • PSS Primary Synchronization Signal, the primary synchronization signal
  • PSSS Primary Sidelink Synchronization Signal, main straight line synchronization signal
  • PTAG Primary Timing Advance Group, the main timing advance group
  • PUSCH Physical uplink shared channel, physical uplink shared channel
  • PUCCH Physical uplink control channel, physical uplink control channel
  • QoS Quality of Service, quality of service
  • QZSS Quasi-Zenith Satellite System, Quasi-Zenith Satellite System
  • RAR Random Access Response, Random Access Response
  • RB Resource Block, resource block
  • REG resource-element group, resource element group
  • RF Radio Frequency, radio frequency
  • RLC Radio Link Control, radio link control protocol
  • Radio-Network Temporary Identifier Radio-Network Temporary Identifier, wireless network temporary identifier
  • RRC Radio Resource Control, radio resource control
  • RV Redundancy Version, redundant version
  • S-BWP Sidelink Bandwidth Part, straight bandwidth segment
  • S-MIB Sidelink Master Information Block, go straight to the master information block
  • S-PSS Sidelink Primary Synchronization Signal, direct main synchronization signal
  • S-SSB Sidelink SS/PBCH block, direct synchronization signal/physical broadcast channel block
  • S-SSS Sidelink Secondary Synchronization Signal, direct-travel secondary synchronization signal
  • SCG Secondary Cell Group, secondary cell group
  • SCI Sidelink Control Information, direct control information
  • SCS Subcarrier Spacing, subcarrier spacing
  • SDAP Service Data Adaptation Protocol, service data adaptation protocol
  • SFN System Frame Number, system frame number
  • SIB System Information Block, system information block
  • SL BWP Sidelink Bandwidth Part, straight bandwidth segment
  • SL MIB Sidelink Master Information Block
  • SL PSS Sidelink Primary Synchronization Signal, direct main synchronization signal
  • SL SS Sidelink Synchronization Signal, direct synchronization signal
  • SL SSID Sidelink Synchronization Signal Identity (or Sidelink Synchronization Signal Identifier), direct synchronization signal identification
  • SL SSB Sidelink SS/PBCH block, direct synchronization signal/physical broadcast channel block
  • SL SSS Sidelink Secondary Synchronization Signal, direct-travel secondary synchronization signal
  • SLSS Sidelink Synchronization Signal, direct synchronization signal
  • SLSS ID Sidelink Synchronization Signal Identity (or Sidelink Synchronization Signal Identifier), direct synchronization signal identification
  • SLSSID Sidelink Synchronization Signal Identity (or Sidelink Synchronization Signal Identifier), direct synchronization signal identification
  • SpCell Special Cell, special cell
  • SRS Sounding Reference Signal, sounding reference signal
  • SSB SS/PBCH block, synchronization signal/physical broadcast channel block
  • SSS Secondary Synchronization Signal, secondary synchronization signal
  • SSSS Secondary Sidelink Synchronization Signal, secondary direct synchronization signal
  • Timing Advance Timing Advance
  • TAG Timing Advance Group, Timing Advance Group
  • Transport Block transport block
  • TCP Transmission Control Protocol, Transmission Control Protocol
  • TDD Time Division Duplexing, time division duplex
  • TPC Transmit power control, transmission power control
  • UE User Equipment, user equipment
  • UMTS Universal Mobile Telecommunications System
  • Universal Mobile Telecommunications System Universal Mobile Telecommunications System
  • V2I Vehicle-to-Infrastructure, vehicle to infrastructure
  • V2N Vehicle-to-network, vehicle-to-network
  • V2P Vehicle-to-Pedestrian, vehicle to pedestrian
  • V2V Vehicle-to-vehicle, vehicle to vehicle
  • V2X Vehicle-to-everything, vehicle to any entity
  • ⁇ SL MIB Sidelink Master Information Block
  • S-MIB S-MIB
  • MIB-SL S-MIB
  • SL MIB refers to MIB-SL-V2X.
  • Fig. 1 is a flowchart showing a method executed by a user equipment according to the first embodiment of the present invention.
  • the steps performed by the user equipment UE include: step S101, step S103, and step S105. Wherein, optionally, one or more of the step S101, the step S103, and the step S105 can be omitted (if applicable).
  • PSCCH Physical Sidelink Control Channel
  • the "receiving PSCCH” includes: detecting (for example, trying to decode) the PSCCH on one or more PSCCH resources. among them,
  • the PSCCH resource may also be called PSCCH candidate or PSCCH candidate resource.
  • the PSCCH resource can be defined in time-domain and/or frequency-domain and/or code-domain.
  • a PSCCH resource is embodied as one or more OFDM symbols in the time domain.
  • a PSCCH resource is embodied in the frequency domain as one or more RB (Resource Block, resource block), or one or more RBG (Resource Block Group, resource block group), or one or more subchannels (subchannel) .
  • a PSCCH resource is embodied as a scrambling code sequence in the code domain.
  • the one or more PSCCH resources may be determined according to predefined information.
  • the one or more PSCCH resources may be determined according to configuration information or pre-configuration information.
  • the "receiving PSCCH” includes: receiving SCI (Sidelink Control Information) carried in the PSCCH. among them,
  • the "receiving the SCI carried in the PSCCH" includes: detecting (for example, trying to decode) the PSCCH according to one or more SCI formats. among them,
  • the one or more SCI formats can be determined according to predefined information.
  • the one or more SCI formats can be determined according to configuration information or pre-configuration information.
  • the SCI can be divided into two parts (two parts), or two stages (two stages), for example, called the first stage SCI and the second stage SCI respectively. among them,
  • the first stage SCI and the second stage SCI may correspond to the same SCI format, or may correspond to different SCI formats (for example, correspond to the first SCI format and the second SCI format respectively).
  • first-stage SCI and the second-stage SCI can be carried in the same PSCCH, or can be carried in different PSCCHs (for example, carried in the first PSCCH and the second PSCCH respectively). among them,
  • the transmission parameters of the first PSCCH may indicate that the second PSCCH and/or the second-stage SCI Relevant information, such as resource allocation information such as time and/or frequency and/or scrambling code of the second PSCCH, is also in the second SCI format.
  • the SCI can schedule a PSSCH (Physical Sidelink Shared Channel) transmission.
  • PSSCH Physical Sidelink Shared Channel
  • the PSCCH it is sometimes called the PSCCH to schedule the PSSCH transmission.
  • the PSSCH transmission corresponds to a transmission on SL-SCH (Sidelink Shared Channel).
  • SL-SCH Servicelink Shared Channel
  • the transmission on the SL-SCH corresponds to a specific MAC entity.
  • the PSSCH carries a TB (Transport Block).
  • the "receive PSCCH” can also be replaced with any of the following:
  • step S103 HARQ information (HARQ information) is determined.
  • the HARQ information may be HARQ information associated with the TB.
  • the HARQ information may be HARQ information associated with the SCI.
  • the HARQ information may be HARQ information associated with the PSSCH.
  • the HARQ information may be HARQ information associated with the PSCCH.
  • part or all of the HARQ information is provided (or indicated) by one or more of the following:
  • the SCI indicates whether the TB exists; in addition, if the TB exists, the SCI also provides part or all of the related HARQ information (for example, the HARQ information associated with the TB Part or all).
  • the TB can also be replaced with "a transmission on the SL-SCH for a specific MAC entity”.
  • the SCI not only indicates the presence of the TB, but also provides part or all of the related HARQ information (for example, part or all of the HARQ information associated with the TB).
  • the TB can also be replaced with "a transmission on the SL-SCH for a specific MAC entity”.
  • the transmission parameters of the PSCCH for example, the DMRS sequence of the PSCCH.
  • the transmission parameters of the PSSCH for example, the DMRS sequence of the PSSCH.
  • ⁇ RNTI used to scramble the CRC of the PSCCH.
  • ⁇ RNTI and/or ID used to scramble the PSSCH for example, the codeword formed by the TB carried by the PSSCH after channel coding.
  • the HARQ information may include one or more of the following:
  • the value of the propagation type can be a value in the set ⁇ unicast, multicast ⁇ , or a value in the set ⁇ unicast, broadcast ⁇ , or the set ⁇ multicast
  • a value in broadcast ⁇ can also be a value in the set ⁇ unicast, multicast/broadcast ⁇ , or a value in the set ⁇ multicast, unicast/broadcast ⁇ , or it can be a set ⁇ broadcast
  • a value in unicast/multicast ⁇ can also be a value in the set ⁇ unicast, multicast, broadcast ⁇ .
  • “multicast/broadcast” means multicast or broadcast
  • unicast/broadcast means unicast or broadcast
  • unicast/multicast means unicast or multicast.
  • the propagation type is unicast. among them,
  • the UNICAST_RNTI can be a predefined value, a configured value, or a preconfigured value.
  • the propagation type is multicast. among them,
  • the GROUPCAST_RNTI can be a pre-defined value, a configured value, or a pre-configured value.
  • the propagation type is broadcast. among them,
  • the BROADCAST_RNTI can be a predefined value, a configured value, or a pre-configured value.
  • the propagation type may be the propagation type of the PSCCH.
  • the transmission type may be the transmission type of the SCI.
  • the propagation type may be the propagation type of the PSSCH.
  • the propagation type may be the propagation type of the TB.
  • the transmission type is determined or assisted by the format of the SCI. For example, if the format of the SCI is a predefined or configured or pre-configured "broadcast SCI format", the transmission type is broadcast. For another example, if the format of the SCI is a predefined or configured or pre-configured "SCI format with HARQ feedback", the transmission type is unicast or multicast.
  • the propagation type can be indicated in the SCI.
  • some or all bits of a field in the SCI are used to indicate the propagation type.
  • the layer 1 source identifier can be an 8-bit integer, or a 10-bit integer, or a 12-bit integer, or a 14-bit integer, or a 16-bit integer
  • An integer is either an 18-bit integer, or a 20-bit integer, or a 22-bit integer, or a 24-bit integer, or a 26-bit integer, or a 28-bit integer, Either a 30-bit integer or a 32-bit integer.
  • the layer 1 source identifier may be used to identify the UE that sends the PSCCH and/or the PSSCH and/or the SCI and/or the TB at the physical layer.
  • the layer 1 source identifier may be indicated in the SCI.
  • some or all bits of a field in the SCI are used to indicate the layer 1 source identifier.
  • the layer 1 target identifier can be an 8-bit integer, or a 10-bit integer, or a 12-bit integer, or a 14-bit integer, or a 16-bit integer
  • An integer is either an 18-bit integer, or a 20-bit integer, or a 22-bit integer, or a 24-bit integer, or a 26-bit integer, or a 28-bit integer, Either a 30-bit integer or a 32-bit integer.
  • the layer 1 target identifier can be used to identify the PSCCH and/or the PSSCH and/or the SCI and/or the TB at the physical layer The target UE.
  • the layer 1 target identifier can be used to identify the PSCCH and/or the PSSCH and/or the SCI and/or the TB at the physical layer
  • the target UE group may include one or more UEs.
  • the layer 1 target identifier can be set to a predefined or configured or pre-configured value.
  • the layer 1 target identifier may be used to identify all UEs at the physical layer, for example, all 5G UEs, like all V2X UEs, and like all 5G V2X UEs.
  • the layer 1 target identifier does not exist.
  • the layer 1 target identifier may be indicated in the SCI.
  • some or all bits of a field in the SCI are used to indicate the layer 1 target identifier.
  • the HARQ process identifier can be a 1-bit integer, or a 2-bit integer, or a 3-bit integer, or a 4-bit integer, or a 5-bit integer , Or a 6-bit integer.
  • the HARQ process identifier may be used to identify the HARQ process to which the TB belongs.
  • the HARQ process identifier may be indicated in the SCI.
  • some or all bits of a field in the SCI are used to indicate the HARQ process identifier.
  • the value of the new data indicator may be a value in the set ⁇ 0, 1 ⁇ .
  • the new data indicator may be used to indicate (or to determine, or to assist in determining) whether the TB corresponds to a new transmission (new transmission) or a retransmission (retransmission).
  • the new data indicator may be indicated in the SCI.
  • some or all bits of a field in the SCI are used to indicate the new data indicator.
  • the value of the redundancy version may be a value in the set ⁇ 0, 1, 2, 3 ⁇ .
  • the redundancy version may be used to indicate the redundancy version used for the current transmission of the TB.
  • the redundancy version can be indicated in the SCI.
  • some or all bits of a field in the SCI are used to indicate the redundancy version.
  • the session identifier can be used to identify a high-level SL session.
  • a high-level broadcast session is another example of a high-level multicast session, and another example is a high-level unicast session.
  • the session identifier may be indicated in the SCI.
  • some or all bits of a field in the SCI are used to indicate the session identifier.
  • the transmission block size may be the size of the TB (for example, expressed in the number of bits, or expressed in the number of bytes).
  • the transmission block size can be indicated in the SCI.
  • some or all bits of a field in the SCI are used to indicate the transport block size.
  • the transport block size can be determined in a manner similar to that of determining the transport block size of the PDSCH in the NR downlink, or can also be determined in other manners.
  • TX-RX distance The distance between the sender and the receiver (TX-RX distance).
  • GX-RX distance the geographic distance between the sender and the receiver (geographical distance). among them,
  • the "distance between the sender and the receiver" may be determined according to the zone ID of the sender and the zone ID of the receiver.
  • the area identifier of the sender may be indicated in the SCI, or may be indicated in a high-level message; the area identifier of the receiver may be determined by the receiver according to an indication of GNSS or the like.
  • the "communication range requirement" may be included in the predefined information.
  • the "communication range requirement" may be included in the configuration information.
  • the "communication range requirement" may be included in the pre-configuration information.
  • the "communication range requirement" may be indicated in the SCI.
  • some or all bits of a field in the SCI are used to indicate the communication range requirement.
  • the value of "whether the communication range requirement is met” may be a value in the set ⁇ Yes, No ⁇ . Among them, “Yes” means that the communication range requirements are met, and “No” means that the communication range requirements are not met.
  • the value of the "whether the communication range requirement is met” is "yes”; otherwise, the " The value of "Whether the communication range requirement is met” is "No".
  • the value of "Whether HARQ feedback is required” may be a value in the set ⁇ Yes, No ⁇ . Among them, “Yes” means that HARQ feedback is required, and “No” means that HARQ feedback is not required.
  • the "whether HARQ feedback is needed” can be determined according to one or more of the following (in any combination of “and” or “or” when applicable):
  • the "whether HARQ feedback is needed" can be included in the configuration information. For example, it is determined that all SL transmissions require (or none) HARQ feedback according to configuration information. For another example, it is determined according to the configuration information that all SL transmissions whose propagation type is unicast need (or do not need) HARQ feedback. For another example, it is determined according to the configuration information that all SL transmissions whose propagation type is multicast require (or do not need) HARQ feedback.
  • the "whether HARQ feedback is needed" can be included in the pre-configuration information. For example, it is determined that all SL transmissions require (or none) HARQ feedback according to the pre-configuration information. For another example, it is determined according to the pre-configuration information that all SL transmissions whose propagation type is unicast require (or do not need) HARQ feedback. For another example, it is determined according to the pre-configuration information that all SL transmissions whose propagation type is multicast require (or do not need) HARQ feedback.
  • HARQ feedback resources such as PSFCH resources
  • PSFCH resources such as PSFCH resources
  • the value of "feedback" For example, if PSFCH resources are configured in the resource pool corresponding to the PSCCH and/or the PSSCH and/or the SCI and/or the TB, HARQ feedback is required; otherwise, HARQ feedback is not required.
  • the "whether HARQ feedback is required" can be replaced with "HARQ feedback indicator".
  • the value of the "HARQ feedback indicator” may be a value in the set ⁇ 1, 0 ⁇ . Among them, “1" indicates that HARQ feedback is required, and “0” indicates that HARQ feedback is not required.
  • the "whether HARQ feedback is required” can be replaced with "whether HARQ feedback is enabled".
  • the value of the "whether HARQ feedback is enabled” may be a value in the set ⁇ Yes, No ⁇ . Among them, “Yes” means that HARQ feedback is enabled, which corresponds to "HARQ feedback is required”; “No” means that HARQ feedback is not enabled (or disabled or prohibited), which corresponds to "HARQ feedback is not required”.
  • the "whether HARQ feedback is required” can be replaced with "whether HARQ feedback is requested”.
  • the value of the "whether to request HARQ feedback” may be a value in the set ⁇ Yes, No ⁇ . Among them, “Yes” means requesting HARQ feedback, corresponding to "HARQ feedback required”; “No” means not requesting HARQ feedback, corresponding to "No HARQ feedback required”.
  • the value "none" in the set Z may indicate that no HARQ feedback is sent to the TB (regardless of the result of processing the TB).
  • the value "ACK" in the set Z may indicate that HARQ feedback is sent only when the result of processing the TB is that ACK needs to be fed back, otherwise, no HARQ feedback is sent. For example, if the TB is decoded correctly, ACK is sent. For another example, if the TB cannot be decoded correctly, no HARQ feedback is sent.
  • the value "NACK" in the set Z may indicate that HARQ feedback is sent only when the result of processing the TB is that NACK feedback is needed, otherwise, no HARQ feedback is sent. For example, if the TB cannot be decoded correctly, a NACK is sent. For another example, if the TB is decoded correctly, no HARQ feedback is sent.
  • the value "ACK or NACK" in the set Z may indicate that HARQ feedback is sent regardless of whether the result of processing the TB requires ACK feedback or NACK feedback. For example, if the TB is decoded correctly, ACK is sent. For another example, if the TB cannot be decoded correctly, a NACK is sent.
  • the "feedback ACK or NACK” can be called “feedback ACK and NACK”.
  • the "HARQ feedback type” can be determined according to one or more of the following (if applicable, press “and” or “or” in any combination):
  • the "HARQ feedback type" can be indicated in the SCI.
  • the "HARQ feedback type" can be included in the configuration information. For example, it is determined according to the configuration information that all SL transmissions need (or do not need) feedback of ACK or NACK. For another example, it is determined according to the configuration information that all SL transmissions whose propagation type is unicast need (or do not need to) feedback ACK or NACK. For another example, it is determined according to the configuration information that all SL transmissions whose propagation type is multicast need (or do not need to) feedback ACK or NACK.
  • the "HARQ feedback type" can be included in the pre-configuration information. For example, it is determined according to the pre-configuration information that all SL transmissions need (or none) to feed back ACK or NACK. For another example, it is determined according to the pre-configuration information that all SL transmissions whose propagation type is unicast need (or do not need to) feedback ACK or NACK. For another example, it is determined according to the pre-configuration information that all SL transmissions whose propagation type is multicast need (or do not need to) feedback ACK or NACK.
  • the "HARQ feedback type" does not exist.
  • step S105 the HARQ information is reported.
  • one protocol layer (or protocol sublayer) A of the UE reports the HARQ information to another protocol layer (or protocol sublayer) B.
  • the protocol layer (or protocol sublayer) A can be the lower layer of the protocol layer (or protocol sublayer) B, or the upper layer of the protocol layer or protocol sublayer B (higher layer, or upper layer).
  • any one of the protocol layer (or protocol sublayer) A and the protocol layer (or protocol sublayer) B can be any one of the following (where applicable):
  • ⁇ MAC layer (or MAC sublayer).
  • ⁇ RLC layer (or RLC sublayer).
  • ⁇ PDCP layer (or PDCP sublayer).
  • ⁇ SDAP layer (or SDAP sublayer).
  • the SCI and/or the TB are also reported.
  • the "report” can also be replaced with "instruction” or "submission”.
  • the physical layer of the UE reports part or all of the HARQ information to a higher layer.
  • the physical layer of the UE reports part or all of the TB and the HARQ information associated with the TB to a higher layer.
  • the physical layer of the UE reports part or all of the SCI, the TB, and the HARQ information associated with the TB to a higher layer.
  • the physical layer of the UE reports the TB and part or all of the HARQ information associated with the TB to a higher layer.
  • the physical layer of the UE reports the SCI to the higher layer, where the SCI indicates whether the TB exists; in addition, if the TB exists, the physical layer of the UE reports the SCI to the higher layer TB and part or all of the HARQ information associated with the TB.
  • the physical layer of the UE reports the SCI and part or all of the HARQ information associated with the SCI to a higher layer.
  • the SCI may also be referred to as a sidelink grant, or a configured sidelink grant.
  • the PSCCH when the SCI is divided into two stages, "the PSCCH" can be replaced with “the first PSCCH”.
  • the PSCCH when the SCI is divided into two stages, "the PSCCH" can be replaced with “the second PSCCH”.
  • the PSCCH when the SCI is divided into two stages, "the PSCCH" can be replaced with “the first PSCCH and/or the second PSCCH".
  • the SCI when the SCI is divided into two stages, "the SCI" may be replaced with “the first stage SCI”.
  • the SCI when the SCI is divided into two stages, "the SCI" may be replaced with “the second stage SCI”.
  • the SCI when the SCI is divided into two stages, "the SCI" may be replaced with “the first stage SCI and/or the second stage SCI".
  • the layer 1 source identifier may also be referred to as a layer 1 source UE identifier (layer-1 source UE ID), or source identifier (source ID), or source UE identifier (source UE ID), or physical layer source identifier (physical layer source ID), or physical layer source UE identifier (physical layer source UE ID).
  • layer-1 source UE ID layer-1 source UE ID
  • source ID source identifier
  • source UE ID source identifier
  • physical layer source identifier physical layer source identifier
  • physical layer source UE identifier physical layer source UE ID
  • the layer 1 target identifier may also be referred to as a layer 1 destination UE ID, or destination ID, or destination UE identifier (destination UE ID), or physical layer destination identifier (physical layer destination ID), or physical layer destination UE identifier (physical layer destination UE ID).
  • the layer 1 destination identifier may also be referred to as a layer 1 destination group ID (layer-1 destination group ID), or Layer 1 target UE group identifier (layer-1 destination UE group ID), or target group identifier (destination group ID), or target UE group identifier (destination UE group ID), or physical layer target group identifier (physical layer destination group ID), or physical layer destination UE group ID (physical layer destination UE group ID).
  • the HARQ process ID may also be referred to as a HARQ process number (HARQ process number).
  • the session ID may also be referred to as a link ID (link ID).
  • the higher layer may be any of the following protocol layers or protocol sublayers (where applicable):
  • ⁇ MAC layer (or MAC sublayer).
  • ⁇ PDCP layer (or PDCP sublayer).
  • ⁇ SDAP layer (or SDAP sublayer).
  • the configuration information may be included in an RRC message or a PC5 RRC message.
  • it is included in the MIB, or included in the SIB, or included in the SL MIB, or included in the PSBCH payload (PSBCH payload).
  • the configuration information may be included in the MAC CE.
  • the pre-configuration information may be included in the RRC message or the PC5 RRC message.
  • the pre-configuration information is included in the SL-Preconfiguration IE, and it is also included in the SL-V2X-Preconfiguration IE.
  • the sender may refer to a UE that transmits (or transmits) the PSCCH and/or the PSSCH and/or the SCI and/or the TB.
  • the receiver may refer to the UE (that is, the UE performing the first embodiment of the present invention).
  • the HARQ information may also be referred to as SL HARQ information.
  • the NACK may also be referred to as NAK.
  • feedback may also be referred to as "response”.
  • HARQ feedback may also be referred to as “HARQ response”.
  • the MAC sublayer of the UE can accurately obtain the complete information related to the HARQ procedure (HARQ procedure) of a TB, thereby correctly performing HARQ related operating.
  • Fig. 2 is a flowchart showing a method executed by a user equipment according to the second embodiment of the present invention.
  • the steps performed by the user equipment UE include: step S201 and step S203.
  • a TB and its associated HARQ information are received.
  • one protocol layer (or protocol sublayer) B of the UE receives the TB and its associated HARQ information reported by another protocol layer (or protocol sublayer) A.
  • the "report” can also be replaced with "instruction” or "submission”.
  • the content, indication mode, associated object and all other features of the HARQ information are exactly the same as the corresponding features of the HARQ information in the first embodiment of the present invention.
  • the protocol layer (or protocol sublayer) A may be a lower layer of the protocol layer (or protocol sublayer) B, or a higher layer of the protocol layer or protocol sublayer B.
  • any one of the protocol layer (or protocol sublayer) A and the protocol layer (or protocol sublayer) B can be any one of the following (where applicable):
  • ⁇ MAC layer (or MAC sublayer).
  • ⁇ RLC layer (or RLC sublayer).
  • ⁇ PDCP layer (or PDCP sublayer).
  • ⁇ SDAP layer (or SDAP sublayer).
  • the protocol layer (or protocol sublayer) A is the physical layer
  • the protocol layer (or protocol sublayer) B is the MAC layer (or MAC sublayer).
  • the SCI for scheduling the TB is also received.
  • the MAC layer (or MAC sublayer) of the UE receives a TB and its associated HARQ information from the physical layer.
  • step S203 the TB and/or the HARQ information are allocated to an SL HARQ process (sidelink HARQ process).
  • the SL HARQ process is maintained by an SL HARQ entity (sidelink HARQ entity). among them,
  • each SL carrier (SL carrier) there is one SL HARQ entity.
  • the SL HARQ entity maintains one or more SL HARQ processes.
  • the SL HARQ entity is located in a MAC entity of the UE.
  • the SL HARQ entity is also referred to as the HARQ entity.
  • HARQ information described in the first embodiment determines the SL HARQ process to be allocated.
  • the SL HARQ entity there may be a unique SL HARQ process related to broadcasting (for example, it is called an SL broadcast HARQ process).
  • an SL broadcast HARQ process a unique SL HARQ process related to broadcasting.
  • the propagation type in the HARQ information is broadcast, the SL HARQ process to be allocated is determined as the SL broadcast HARQ process.
  • an SL HARQ process is determined according to the layer 1 source identifier in the HARQ information.
  • an SL HARQ process is determined according to the layer 1 source identifier and the HARQ process identifier in the HARQ information.
  • an SL HARQ process is determined according to the layer 1 source identifier, the layer 1 target identifier, and the HARQ process identifier in the HARQ information.
  • an SL HARQ process is determined according to the layer 1 source identifier, the layer 1 target identifier, and the HARQ process identifier in the HARQ information.
  • the SL HARQ process is referred to as the HARQ process if the context is clear.
  • the SL HARQ process is also referred to as the SL process when the context is clear.
  • the second embodiment of the present invention assigns the received TB to different SL HARQ processes according to the propagation type and each identifier in the HARQ information, ensuring that the physical layer of the UE supports blind retransmission and/ Or in the case of HARQ retransmission and/or multiple source/target IDs and/or multiple propagation types, multiple transmissions of one TB can be effectively combined to ensure the performance of HARQ combining.
  • Fig. 3 is a flowchart showing a method executed by a user equipment according to the third embodiment of the present invention.
  • the steps performed by the user equipment UE include: step S301 and step S303.
  • a TB and its associated HARQ information are received.
  • one protocol layer (or protocol sublayer) B of the UE receives the TB and its associated HARQ information reported by another protocol layer (or protocol sublayer) A.
  • the "report” can also be replaced with "instruction” or "submission”.
  • the content, indication mode, associated object and all other features of the HARQ information are exactly the same as the corresponding features of the HARQ information in the first embodiment of the present invention.
  • the protocol layer (or protocol sublayer) A can be a lower layer of the protocol layer (or protocol sublayer) B, or can be a higher layer of the protocol layer or protocol sublayer B.
  • the MAC layer (or MAC sublayer) of the UE receives a TB and its associated HARQ information from the physical layer.
  • step S303 it is determined whether the protocol layer (or protocol sublayer) C is instructed to generate a response to the data in the TB.
  • the "response to the data in the TB” may also be referred to as the "response to the TB”.
  • the response may include a positive acknowledgement (positive acknowledgement).
  • the response may include a negative acknowledgement (negative acknowledgement).
  • the protocol layer (or protocol sublayer) C is not commanded to generate a response to the data in the TB.
  • the protocol layer (or protocol sublayer) C is instructed to generate a response to the data in the TB.
  • the "no response” condition may include one or more of the following (in any combination of "and” or "or” where applicable):
  • the propagation type in the HARQ information is broadcast.
  • the "HARQ feedback type" in the HARQ information is "None".
  • the protocol layer (or protocol sublayer) A, the protocol layer (or protocol sublayer) B, and the protocol layer (or protocol sublayer) C Any one of can be any of the following (where applicable):
  • ⁇ MAC layer (or MAC sublayer).
  • ⁇ PDCP layer (or PDCP sublayer).
  • ⁇ SDAP layer (or SDAP sublayer).
  • the protocol layer (or protocol sublayer) A is the physical layer
  • the protocol layer (or protocol sublayer) B is the MAC layer (or MAC sublayer)
  • the protocol layer (or protocol sublayer) C Is the physical layer.
  • the third embodiment of the present invention determines whether to order the physical layer to generate a response to the received TB according to the propagation type in the HARQ information and other information related to the HARQ response, ensuring that the HARQ process of the UE also supports HARQ-based feedback Transmission and transmission without HARQ feedback.
  • FIG. 4 is used to illustrate a user equipment that can execute the method executed by the user equipment described in detail above in the present invention as a modified example.
  • Fig. 4 is a block diagram showing a user equipment UE related to the present invention.
  • the user equipment UE40 includes a processor 401 and a memory 402.
  • the processor 401 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 402 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories.
  • the memory 402 stores program instructions. When the instruction is run by the processor 401, it can execute the above method executed by the user equipment described in detail in the present invention.
  • the method and related equipment of the present invention have been described above in conjunction with preferred embodiments. Those skilled in the art can understand that the methods shown above are only exemplary, and 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 and sequence shown above.
  • the network nodes and user equipment shown above may include more modules, for example, may also include modules that can be developed or developed in the future and can be used for base stations, MMEs, or UEs, and so on.
  • the various identifiers shown above are only exemplary rather than restrictive, and the present invention is not limited to specific information elements as examples of these identifiers. Those skilled in the art can make many changes and modifications based on the teaching of the illustrated embodiment.
  • the foregoing embodiments of the present invention can be implemented by software, hardware, or a combination of both software and hardware.
  • the various components inside the base station and user equipment in the above embodiment can be implemented by a variety of devices, including but not limited to: analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processing Device, application specific integrated circuit (ASIC), field programmable gate array (FPGA), programmable logic device (CPLD), etc.
  • DSP digital signal processing
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • CPLD programmable logic device
  • base station may refer to a mobile communication data and control switching center with a certain transmission power and a certain coverage area, including functions such as resource allocation and scheduling, data reception and transmission.
  • User equipment may refer to a user's mobile terminal, for example, including mobile phones, notebooks, and other terminal devices that can communicate with base stations or micro base stations wirelessly.
  • the embodiments of the present invention disclosed herein can be implemented on a computer program product.
  • the computer program product is a product that has a computer-readable medium on which computer program logic is encoded, and when executed on a computing device, the computer program logic provides related operations to implement The above technical scheme of the present invention.
  • the computer program logic When executed on at least one processor of the computing system, the computer program logic causes the processor to perform the operations (methods) described in the embodiments of the present invention.
  • This arrangement of the present invention is typically provided as software, code and/or other data structures arranged or encoded on a computer-readable medium such as an optical medium (such as CD-ROM), a floppy disk or a hard disk, or as one or more Firmware or microcode on a ROM or RAM or PROM chip, or downloadable software images, shared databases, etc. in one or more modules.
  • Software or firmware or such a configuration may be installed on a computing device, so that one or more processors in the computing device execute the technical solutions described in the embodiments of the present invention.
  • each functional module or each feature of the base station device and the terminal device used in each of the foregoing embodiments may be implemented or executed by a circuit, and the circuit is usually one or more integrated circuits.
  • Circuits designed to perform the functions described in this specification can include general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC) or general-purpose integrated circuits, field programmable gate arrays (FPGA), or other Programming logic devices, discrete gates or transistor logic, or discrete hardware components, or any combination of the above devices.
  • the 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.
  • the present invention can also use integrated circuits obtained by using this advanced technology.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

根据本发明，提出了一种由用户设备执行的方法，其特征在于包括：接收包括直行控制信息SCI的物理直行控制信道PSCCH，所述SCI用于调度携带传输块TB的物理直行共享信道PSSCH传输；确定与所述TB相关联的混合自动重复请求HARQ信息；以及从物理层向介质访问控制MAC子层报告所述HARQ信息。图1

Description

由用户设备执行的方法以及用户设备 技术领域
本发明涉及一种由用户设备执行的方法以及用户设备。
背景技术
在LTE和5G NR Rel-15(参见非专利文献1，下面简称5G Rel-15，或者NR Rel-15)***中，下行指派(downlink assignment)和上行授权(uplink grant)中分别包含了和要接收和要发送的数据有关的HARQ信息(HARQ information)。
在LTE***中，对于下行共享信道(DL-SCH)，HARQ信息包括新数据指示符(New Data Indicator，NDI)、传输块大小(Transport Block Size，TBS)和HARQ进程标识符(HARQ process ID)；对于上行共享信道(UL-SCH)，HARQ信息包括NDI、TBS、HARQ进程标识符(如在异步上行HARQ中)和冗余版本(Redundancy Version，RV)。在基于LTE的LTE V2X中，由于在MAC子层和物理层不支持HARQ反馈，所以对于直行共享信道(SL-SCH)，HARQ信息中只包括TBS。
在5G Rel-15***中，对于DL-SCH和UL-SCH，HARQ信息包括NDI、TBS、RV和HARQ进程标识符。
本发明旨在解决在5G V2X(参见非专利文献2和非专利文献3)中，在UE的物理层支持盲重传和/或HARQ重传和/或多个源/目标ID和/或多种传播类型的情况下，如何定义HARQ信息以及和HARQ信息有关的操作的问题。
在先技术文献
非专利文献
非专利文献1：RP-181474，Revised WID on New Radio Access Technology
非专利文献2：RP-181429，New SID：Study on 5G V2X
非专利文献3：RP-190766，New WID on 5G V2X with NR sidelink
发明内容
为了解决上述问题中的至少一部分，本发明提供了一种由用户设备执行的方法以及用户设备，通过适当地定义HARQ信息，使得UE的MAC子层可以准确地获取一个TB的与HARQ流程有关的完整信息，从而正确地进行HARQ相关的操作，并确保了在UE的物理层支持盲重传和/或HARQ重传的情况下，一个TB的多次传输可以有效地进行合并，确保了HARQ合并的性能。
根据本发明，提出了一种由用户设备执行的方法，其特征在于包括：接收包括直行控制信息SCI的物理直行控制信道PSCCH，所述SCI用于调度携带传输块TB的物理直行共享信道PSSCH传输；确定与所述TB相关联的混合自动重复请求HARQ信息；以及从物理层向介质访问控制MAC子层报告所述HARQ信息。
优选地，所述HARQ信息包括以下一项或多项：传播类型、层1源标识符、层1目标标识符、HARQ进程标识符、新数据指示符、冗余版本、会话标识符、传输块大小、发送方和接收方的距离、通信范围要求、表示是否满足通信范围要求的信息、表示是否需要HARQ反馈的信息、以及HARQ反馈类型。
优选地，所述传播类型包括：单播和组播中的任一个、单播和广播中的任一个、组播和广播中的任一个、或者单播、组播和广播中的任一个。
优选地，所述方法还包括：在报告所述HARQ信息的同时报告所述SCI和/或所述TB。
此外，根据本发明，提出了一种由用户设备执行的方法，其特征在于包括：在介质访问控制MAC子层从物理层接收与传输块TB相关联的混合自动重复请求HARQ信息；以及将所述TB和/或所述HARQ信息分配给直行HARQ进程。
优选地，根据所述HARQ信息中包括的以下一项或多项，确定要分配的直行HARQ进程：传播类型、层1源标识符、层1目标标识符、HARQ 进程标识符、新数据指示符、冗余版本、会话标识符、传输块大小、发送方和接收方的距离、通信范围要求、表示是否满足通信范围要求的信息、表示是否需要HARQ反馈的信息、以及HARQ反馈类型。
此外，根据本发明，提出了一种由用户设备执行的方法，其特征在于包括：在介质访问控制MAC子层从物理层接收与传输块TB相关联的混合自动重复请求HARQ信息；以及确定是否命令物理层产生对所述TB中的数据的应答。
优选地，若无应答条件成立，则不命令物理层产生对所述TB中的数据的应答；若无应答条件不成立，则命令物理层产生对所述TB中的数据的应答，其中，所述无应答条件包括以下一项或多项：所述HARQ信息中的传播类型是广播、所述HARQ信息中的“是否需要HARQ反馈”的值是“否”、所述HARQ信息中的“HARQ反馈类型”是“无”。
优选地，所述HARQ信息包括以下一项或多项：传播类型、层1源标识符、层1目标标识符、HARQ进程标识符、新数据指示符、冗余版本、会话标识符、传输块大小、发送方和接收方的距离、通信范围要求、表示是否满足通信范围要求的信息、表示是否需要HARQ反馈的信息、以及HARQ反馈类型。
另外，根据本发明，提出了一种用户设备，包括：处理器；以及存储器，存储有指令，其中，所述指令在由所述处理器运行时执行上述的方法。
根据本发明，通过适当地定义HARQ信息，使得UE的MAC子层可以准确地获取一个TB的与HARQ流程有关的完整信息，从而正确地进行HARQ相关的操作，并确保了在UE的物理层支持盲重传和/或HARQ重传的情况下，一个TB的多次传输可以有效地进行合并，确保了HARQ合并的性能。另外，根据HARQ信息中的传播类型及其他与HARQ应答相关的信息，确定是否命令物理层产生对所接收到的TB的应答，确保了UE的HARQ流程同时支持基于HARQ反馈的传输和无HARQ反馈的传输。
附图说明
通过下文结合附图的详细描述，本发明的上述和其它特征将会变得更加明显，其中：
图1是示出了根据本发明的实施例一的由用户设备执行的方法的流程图。
图2是示出了根据本发明的实施例二的由用户设备执行的方法的流程图。
图3是示出了根据本发明的实施例三的由用户设备执行的方法的流程图。
图4是示意性示出本发明所涉及的用户设备的框图。
具体实施方式
下面结合附图和具体实施方式对本发明进行详细阐述。应当注意，本发明不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本发明没有直接关联的公知技术的详细描述，以防止对本发明的理解造成混淆。
下文以5G移动通信***及其后续的演进版本作为示例应用环境，具体描述了根据本发明的多个实施方式。然而，需要指出的是，本发明不限于以下实施方式，而是可适用于更多其它的无线通信***，例如5G之后的通信***以及5G之前的4G移动通信***等。
下面描述本发明涉及的部分术语，如未特别说明，本发明涉及的术语采用此处定义。本发明给出的术语在LTE、LTE-Advanced、LTE-Advanced Pro、NR以及之后的通信***中可能采用不同的命名方式，但本发明中采用统一的术语，在应用到具体的***中时，可以替换为相应***中采用的术语。
3GPP：3rd Generation Partnership Project，第三代合作伙伴计划
ACK：Acknowledgement，应答
AS：Access Stratum，接入层
BWP：Bandwidth Part，带宽片段
CA：Carrier Aggregation，载波聚合
CCE：control-channel element，控制信道元素
CORESET：control-resource set，控制资源集
CP：Cyclic Prefix，循环前缀
CP-OFDM：Cyclic Prefix Orthogonal Frequency DiVision Multiplexing，循环前缀正交频分复用
CRB：Common Resource Block，公共资源块
CRC：Cyclic Redundancy Check，循环冗余校验
CSI：Channel-state Information，信道状态信息
CSS：Common Search Space，公共搜索空间
DC：Dual Connectivity，双连接
DCI：Downlink Control Information，下行控制信息
DFN：Direct Frame Number，直接帧号
DFT-s-OFDM：Discrete Fourier Transformation Spread Orthogonal Frequency Division Multiplexing，离散傅里叶变换扩频正交频分复用
DL：Downlink，下行
DL-SCH：Downlink Shared Channel，下行共享信道
DM-RS：Demodulation reference signal，解调参考信号
eMBB：Enhanced Mobile Broadband，增强的移动宽带通信
eNB：E-UTRAN Node B，E-UTRAN节点B
E-UTRAN：Evolved UMTS Terrestrial Radio Access Network，演进的UMTS陆地无线接入网
FDRA：Frequency Domain Resource Assignment，频域资源分配
FR1：Frequency Range 1，频率范围1
FR2：Frequency Range 1，频率范围2
GLONASS：GLObal NAvigation Satellite System，全球导航卫星***
gNB：NR Node B，NR节点B
GNSS：Global Navigation Satellite System，全球导航卫星***
GPS：Global Positioning System，全球定位***
HARQ：Hybrid Automatic Repeat Request，混合自动重复请求
ID：Identity(或者Identifier)，身份，标识符
IE：Information Element，信息元素
IP：Internet Protocol，网际协议
LCID：Logical Channel ID，逻辑信道标识符
LTE：Long Term Evolution，长期演进
LTE-A：Long Term Evolution-Advanced，长期演进-升级版
MAC：Medium Access Control，介质访问控制
MAC CE：MAC Control Element，MAC控制元素
MCG：Master Cell Group，主小区组
MIB：Master Information Block，主信息块
MIB-SL：Master Information Block-Sidelink，主信息块-直行
MIB-SL-V2X：Master Information Block-Sidelink-V2X，主信息块-直行-V2X
MIB-V2X：Master Information Block-V2X，主信息块-V2X
mMTC：massive Machine Type Communication，大规模机器类通信
NACK：Negative Acknowledgement，否定应答
NAK：Negative Acknowledgement，否定应答
NAS：Non-Access-Stratum，非接入层
NDI：New Data Indicator，新数据指示符
NR：New Radio，新无线电
NUL：Normal Uplink，正常上行
OFDM：Orthogonal Frequency Division Multiplexing，正交频分复用
PBCH：Physical Broadcast Channel，物理广播信道
PDCCH：Physical Downlink Control Channel，物理下行控制信道
PDCP：Packet Data Convergence Protocol，分组数据汇聚协议
PDSCH：Physical Downlink Shared Channel，物理下行共享信道
PSBCH：Physical Sidelink Broadcast Channel，物理直行广播信道
PSCCH：Physical Sidelink Control Channel，物理直行控制信道
PSFCH：Physical Sidelink Feedback Channel，物理直行反馈信道
PSSCH：Physical Sidelink Shared Channel，物理直行共享信道
PRB：Physical Resource Block，物理资源块
PSS：Primary Synchronization Signal，主同步信号
PSSS：Primary Sidelink Synchronization Signal，主直行同步信号
PTAG：Primary Timing Advance Group，主定时提前组
PUSCH：Physical uplink shared channel，物理上行共享信道
PUCCH：Physical uplink control channel，物理上行控制信道
QCL：Quasi co-location，准共置
QoS：Quality of Service，服务质量
QZSS：Quasi-Zenith Satellite System，准天顶卫星***
RAR：Random Access Response，随机接入响应
RB：Resource Block，资源块
RE：Resource Element，资源元素
REG：resource-element group，资源元素组
RF：Radio Frequency，射频
RLC：Radio Link Control，无线链路控制协议
RNTI：Radio-Network Temporary Identifier，无线网络临时标识符
RRC：Radio Resource Control，无线资源控制
RV：Redundancy Version，冗余版本
S-BWP：Sidelink Bandwidth Part，直行带宽片段
S-MIB：Sidelink Master Information Block，直行主信息块
S-PSS：Sidelink Primary Synchronization Signal，直行主同步信号
S-SSB：Sidelink SS/PBCH block，直行同步信号/物理广播信道块
S-SSS：Sidelink Secondary Synchronization Signal，直行辅同步信号
SCG：Secondary Cell Group，次小区组
SCI：Sidelink Control Information，直行控制信息
SCS：Subcarrier Spacing，子载波间隔
SDAP：Service Data Adaptation Protocol，业务数据适配协议
SFN：System Frame Number，***帧号
SIB：System Information Block，***信息块
SL：Sidelink，直行
SL BWP：Sidelink Bandwidth Part，直行带宽片段
SL MIB：Sidelink Master Information Block，直行主信息块
SL PSS：Sidelink Primary Synchronization Signal，直行主同步信号
SL SS：Sidelink Synchronisation Signal，直行同步信号
SL SSID：Sidelink Synchronization Signal Identity(或者Sidelink Synchronization Signal Identifier)，直行同步信号标识
SL SSB：Sidelink SS/PBCH block，直行同步信号/物理广播信道块
SL SSS：Sidelink Secondary Synchronization Signal，直行辅同步信号
SLSS：Sidelink Synchronisation Signal，直行同步信号
SLSS ID：Sidelink Synchronization Signal Identity(或者Sidelink Synchronization Signal Identifier)，直行同步信号标识
SLSSID：Sidelink Synchronization Signal Identity(或者Sidelink Synchronization Signal Identifier)，直行同步信号标识
SpCell：Special Cell，特殊小区
SRS：Sounding Reference Signal，探测参考信号
SSB：SS/PBCH block，同步信号/物理广播信道块
SSS：Secondary Synchronization Signal，辅同步信号
SSSS：Secondary Sidelink Synchronization Signal，辅直行同步信号
STAG：Secondary Timing Advance Group，辅定时提前组
SUL：Supplementary Uplink，补充上行
TA：Timing Advance，定时提前
TAG：Timing Advance Group，定时提前组
TB：Transport Block，传输块
TCP：Transmission Control Protocol，传输控制协议
TDD：Time Division Duplexing，时分双工
TPC：Transmit power control，传输功率控制
UE：User Equipment，用户设备
UL：Uplink，上行
UMTS：Universal Mobile Telecommunications System，通用移动通信***
URLLC：Ultra-Reliable and Low Latency Communication，超可靠低延迟通信
USS：UE-specific Search Space，UE特定搜索空间
V2I：Vehicle-to-Infrastructure，车辆到基础设施
V2N：Vehicle-to-network，车辆到网络
V2P：Vehicle-to-Pedestrian，车辆到行人
V2V：Vehicle-to-vehicle，车辆到车辆
V2X：Vehicle-to-everything，车辆到任何实体
如未特别说明，在本发明所有实施例和实施方式中：
●SL MIB(Sidelink Master Information Block，直行主信息块)又可以称为S-MIB，或者MIB-SL。可选地，在用于V2X业务时，
SL MIB指的是MIB-SL-V2X。
[实施例一]
下面结合图1来说明本发明的实施例一的由用户设备执行的方法。
图1是示出了根据本发明的实施例一的由用户设备执行的方法的流程图。
如图1所示，在本发明的实施例一中，用户设备UE执行的步骤包括：步骤S101、步骤S103和步骤S105。其中，可选地，所述步骤S101、所述步骤S103和所述步骤S105中的一个或多个可以省略(在适用的情况下)。
具体地，在步骤S101，接收PSCCH(Physical Sidelink Control Channel，物理直行控制信道)。其中，
●可选地，所述“接收PSCCH”包括：在一个或多个PSCCH资源上检测(例如，尝试解码)PSCCH。其中，
◆可选地，所述PSCCH资源也可以称为PSCCH候选，或者PSCCH候选资源。
◆可选地，所述PSCCH资源可以在时域(time-domain)和/或频域(frequency-domain)和/或码域(code-domain)上定义。例如，一个PSCCH资源在时域上体现为一个或多个 OFDM符号。又如，一个PSCCH资源在频域上体现为一个或多个RB(Resource Block，资源块)，或者一个或多个RBG(Resource Block Group，资源块组)，或者一个或多个子信道(subchannel)。又如，一个PSCCH资源在码域上体现为一个扰码(scrambling code)序列。
◆可选地，所述一个或多个PSCCH资源可以根据预定义信息确定。
◆可选地，所述一个或多个PSCCH资源可以根据配置信息或预配置信息确定。
●可选地，所述“接收PSCCH”包括：接收PSCCH中携带的SCI(Sidelink Control Information，直行控制信息)。其中，
◆可选地，所述“接收PSCCH中携带的SCI”包括：根据一个或多个SCI格式检测(例如，尝试解码)PSCCH。其中，
○可选地，所述一个或多个SCI格式可以根据预定义信息确定。
○可选地，所述一个或多个SCI格式可以根据配置信息或预配置信息确定。
◆可选地，所述SCI可以分成两个部分(two parts)，或者说两个阶段(two stages)，例如分别称为第一阶段SCI和第二阶段SCI。其中，
○可选地，所述第一阶段SCI和所述第二阶段SCI可以对应同一个SCI格式，也可以对应不同的SCI格式(例如分别对应第一SCI格式和第二SCI格式)。
○可选地，所述第一阶段SCI和所述第二阶段SCI可以携带在同一个PSCCH中，也可以携带在不同的PSCCH中(例如分别携带在第一PSCCH和第二PSCCH中)。其中，
◇可选地，所述第一PSCCH的传输参数(例如所述第一PSCCH的DMRS序列)和/或所述第一阶段SCI可以指示与所述第二PSCCH和/或所 述第二阶段SCI有关的信息，例如所述第二PSCCH的时间和/或频率和/或扰码等资源的分配信息，又如所述第二SCI格式。
◆可选地，所述SCI可以调度一个PSSCH(Physical Sidelink Shared Channel，物理直行共享信道)传输。
○可选地，有时候又称所述PSCCH调度所述PSSCH传输。
○可选地，所述PSSCH传输对应一个在SL-SCH(Sidelink Shared Channel，直行共享信道)上的传输。其中，可选地，所述SL-SCH上的传输对应一个特定的MAC实体。
○可选地，所述PSSCH中携带一个TB(Transport Block，传输块)。
●可选地，所述“接收PSCCH”也可以替换为下面中的任意一项：
◆接收SCI。
◆接收PSCCH中携带的SCI。
◆接收PSCCH及其所携带的SCI。
此外，在步骤S103，确定HARQ信息(HARQ information)。
其中，
●可选地，所述HARQ信息可以是所述TB所关联的HARQ信息。
●可选地，所述HARQ信息可以是所述SCI所关联的HARQ信息。
●可选地，所述HARQ信息可以是所述PSSCH所关联的HARQ信息。
●可选地，所述HARQ信息可以是所述PSCCH所关联的HARQ信息。
●可选地，所述HARQ信息的部分或全部由下面中的一项或多项提供(或者说指示)：
◆所述SCI。其中，
○可选地，所述SCI指示是否存在所述TB；此外，若存在所述TB，则所述SCI还提供了相关的HARQ信 息的部分或全部(例如和所述TB所关联的HARQ信息的部分或全部)。可选地，“所述TB”也可以替换为“一个用于特定MAC实体的SL-SCH上的传输”。
○可选地，所述SCI不仅指示存在所述TB，而且提供了相关的HARQ信息的部分或全部(例如和所述TB所关联的HARQ信息的部分或全部)。可选地，“所述TB”也可以替换为“一个用于特定MAC实体的SL-SCH上的传输”。
◆所述PSCCH的传输参数(例如PSCCH的DMRS序列)。
◆所述PSSCH的传输参数(例如PSSCH的DMRS序列)。
◆所述PSCCH所占用的时域和/或频域和/或码域资源。
◆所述PSSCH所占用的时域和/或频域和/或码域资源。
◆所述PSCCH和所述PSSCH所共同占用的时域和/或频域和/或码域资源。
◆所述PSCCH所属的资源池。
◆所述PSSCH所属的资源池。
◆所述PSCCH和所述PSSCH共同所属的资源池。
◆加扰所述PSCCH的CRC所使用的RNTI。
◆加扰所述PSSCH(例如所述PSSCH所携带的TB在信道编码后所形成的码字(codeword))所使用的RNTI和/或ID。
●可选地，所述HARQ信息可以包含下面中的一项或多项：
◆传播类型(cast-type，或者casting-type)。其中，
○可选地，所述传播类型的取值可以是集合{单播，组播}中的一个值，也可以是集合{单播，广播}中的一个值，也可以是集合{组播，广播}中的一个值，也可以是集合{单播，组播/广播}中的一个值，也可以是集合{组播，单播/广播}中的一个值，也可以是集合{广播，单播/组播}中的一个值，也可以是集合{单播，组播，广播}中的一个值。其中，“组播/广播”表示组播或广播，“单播/广播”表示单播或广播，“单 播/组播”表示单播或组播。
○可选地，若加扰所述PSCCH的CRC所使用的RNTI是UNICAST_RNTI，则所述传播类型是单播。其中，
◇可选地，所述UNICAST_RNTI可以是一个预定义的值，也可以是一个配置的值，也可以是一个预配置的值。
○可选地，若加扰所述PSCCH的CRC所使用的RNTI是GROUPCAST_RNTI，则所述传播类型是组播。其中，
◇可选地，所述GROUPCAST_RNTI可以是一个预定义的值，也可以是一个配置的值，也可以是一个预配置的值。
○可选地，若加扰所述PSCCH的CRC所使用的RNTI是BROADCAST_RNTI，则所述传播类型是广播。其中，
◇可选地，所述BROADCAST_RNTI可以是一个预定义的值，也可以是一个配置的值，也可以是一个预配置的值。
○可选地，所述传播类型可以是所述PSCCH的传播类型。
○可选地，所述传播类型可以是所述SCI的传播类型。
○可选地，所述传播类型可以是所述PSSCH的传播类型。
○可选地，所述传播类型可以是所述TB的传播类型。
○可选地，所述传播类型由所述SCI的格式确定或辅助确定。例如，若所述SCI的格式是一个预定义或配置或预配置的“广播SCI格式”，则所述传播类型是广播。又如，若所述SCI的格式是一个预定义或配置或预配置的“带HARQ反馈的SCI格式”，则所述传播类型是单播或组播。
○可选地，所述传播类型可以在所述SCI中指示。例如，所述SCI中的一个字段的部分或全部比特用于指示所述传播类型。
◆层1源标识符(layer-1 source ID)。其中，
○可选地，所述层1源标识符可以是一个8比特的整数，或者是一个10比特的整数，或者是一个12比特的整数，或者是一个14比特的整数，或者是一个16比特的整数，或者是一个18比特的整数，或者是一个20比特的整数，或者是一个22比特的整数，或者是一个24比特的整数，或者是一个26比特的整数，或者是一个28比特的整数，或者是一个30比特的整数，或者是一个32比特的整数。
○可选地，所述层1源标识符可以用于在物理层标识发送所述PSCCH和/或所述PSSCH和/或所述SCI和/或所述TB的UE。
○可选地，所述层1源标识符可以在所述SCI中指示。例如，所述SCI中的一个字段的部分或全部比特用于指示所述层1源标识符。
◆层1目标标识符(layer-1 destination ID)。其中，
○可选地，所述层1目标标识符可以是一个8比特的整数，或者是一个10比特的整数，或者是一个12比特的整数，或者是一个14比特的整数，或者是一个16比特的整数，或者是一个18比特的整数，或者是一个20比特的整数，或者是一个22比特的整数，或者是一个24比特的整数，或者是一个26比特的整数，或者是一个28比特的整数，或者是一个30比特的整数，或者是一个32比特的整数。
○可选地，若所述传播类型是单播，则所述层1目标标识符可以用于在物理层标识所述PSCCH和/或所述PSSCH和/或所述SCI和/或所述TB的目标UE。
○可选地，若所述传播类型是组播，则所述层1目标标识符可以用于在物理层标识所述PSCCH和/或所述PSSCH和/或所述SCI和/或所述TB的目标UE组。其中，可选地，所述目标UE组可以包含一个或多个UE。
○可选地，若所述传播类型是广播，则所述层1目标标识符可以设置为一个预定义或配置或预配置的值。此时，可选地，所述层1目标标识符可以用于在物理层标识所有UE，例如所有5G UE，又如所有V2X UE，又如所有5G V2X UE。
○可选地，若所述传播类型是广播，则所述层1目标标识符不存在。
○可选地，所述层1目标标识符可以在所述SCI中指示。例如，所述SCI中的一个字段的部分或全部比特用于指示所述层1目标标识符。
◆HARQ进程标识符(HARQ process ID)。其中，
○可选地，所述HARQ进程标识符可以是一个1比特的整数，或者是一个2比特的整数，或者是一个3比特的整数，或者是一个4比特的整数，或者是一个5比特的整数，或者是一个6比特的整数。
○可选地，所述HARQ进程标识符可以用于标识所述TB所属的HARQ进程。
○可选地，所述HARQ进程标识符可以在所述SCI中指示。例如，所述SCI中的一个字段的部分或全部比特用于指示所述HARQ进程标识符。
◆新数据指示符(New Data Indicator，NDI)。其中，
○可选地，所述新数据指示符的取值可以是集合{0，1}中的一个值。
○可选地，所述新数据指示符可以用于指示(或用于确定、或用于辅助确定)所述TB对应一个新传(new  transmission)还是对应一个重传(retransmission)。
○可选地，所述新数据指示符可以在所述SCI中指示。例如，所述SCI中的一个字段的部分或全部比特用于指示所述新数据指示符。
◆冗余版本(Redundancy Version，RV)。其中，
○可选地，所述冗余版本的取值可以是集合{0，1，2，3}中的一个值。
○可选地，所述冗余版本可以用于指示所述TB的当前传输所使用的冗余版本。
○可选地，所述冗余版本可以在所述SCI中指示。例如，所述SCI中的一个字段的部分或全部比特用于指示所述冗余版本。
◆会话标识符(Session ID)。其中，
○可选地，所述会话标识符可以用于标识一个高层SL会话。例如一个高层广播会话，又如一个高层组播会话，又如一个高层单播会话。
○可选地，所述会话标识符可以在所述SCI中指示。例如，所述SCI中的一个字段的部分或全部比特用于指示所述会话标识符。
◆传输块大小(Transport Block Size，TBS)。其中，
○可选地，所述传输块大小可以是所述TB的大小(例如以比特个数表示，又如以字节个数表示)。
○可选地，所述传输块大小可以在所述SCI中指示。例如，所述SCI中的一个字段的部分或全部比特用于指示所述传输块大小。
○可选地，所述传输块大小可以使用类似于NR下行链路中确定PDSCH的传输块大小的方式确定，也可以用其他方式确定。
◆发送方和接收方的距离(TX-RX distance)。例如，发送方和接收方的地理距离(geographical distance)。其中，
○可选地，所述“发送方和接收方的距离”可以根据发送方的区域标识符(zone ID)和接收方的区域标识符确定。其中，所述发送方的区域标识符可以在所述SCI中指示，也可以在高层消息中指示；所述接收方的区域标识符可以由所述接收方根据GNSS等的指示确定。
◆通信范围要求(communication range requirement)。其中，
○可选地，所述“通信范围要求”可以包含在预定义信息中。
○可选地，所述“通信范围要求”可以包含在配置信息中。
○可选地，所述“通信范围要求”可以包含在预配置信息中。
○可选地，所述“通信范围要求”可以在所述SCI中指示。例如，所述SCI中的一个字段的部分或全部比特用于指示所述通信范围要求。
◆是否满足通信范围要求。其中，
○可选地，所述“是否满足通信范围要求”的取值可以是集合{是，否}中的一个值。其中，“是”表示满足通信范围要求，“否”表示不满足通信范围要求。
○可选地，若所述“发送方和接收方的距离”小于所述“通信范围要求”，则所述“是否满足通信范围要求”的取值是“是”；否则所述“是否满足通信范围要求”的取值是“否”。
○可选地，若所述“发送方和接收方的距离”小于或等于所述“通信范围要求”，则所述“是否满足通信范围要求”的取值是“是”；否则所述“是否满足通信范围要求”的取值是“否”。
◆是否需要HARQ反馈(feedback)。其中，
○可选地，所述“是否需要HARQ反馈”的取值可以 是集合{是，否}中的一个值。其中，“是”表示需要HARQ反馈，“否”表示不需要HARQ反馈。
○可选地，所述“是否需要HARQ反馈”可以根据下面中的一项或多项确定(在适用的情况下按“与”或者“或”任意组合)：
◇所述“是否需要HARQ反馈”可以在所述SCI中指示。
◇所述“是否需要HARQ反馈”可以包含在配置信息中。例如，根据配置信息确定所有SL传输都需要(或者都不需要)HARQ反馈。又如，根据配置信息确定所有传播类型为单播的SL传输都需要(或者都不需要)HARQ反馈。又如，根据配置信息确定所有传播类型为组播的SL传输都需要(或者都不需要)HARQ反馈。
◇所述“是否需要HARQ反馈”可以包含在预配置信息中。例如，根据预配置信息确定所有SL传输都需要(或者都不需要)HARQ反馈。又如，根据预配置信息确定所有传播类型为单播的SL传输都需要(或者都不需要)HARQ反馈。又如，根据预配置信息确定所有传播类型为组播的SL传输都需要(或者都不需要)HARQ反馈。
◇根据所述传播类型确定所述“是否需要HARQ反馈”的取值。例如，若所述传播类型为广播，则不需要HARQ反馈。又如，若所述传播类型为单播或组播，则根据其他条件或条件组合确定是否需要HARQ反馈(例如根据配置信息或预配置信息中的“是否需要HARQ反馈”，又如根据所述PSCCH和/或所述PSSCH和/或所述SCI和/或所述TB所对应的资源池是否配置了 HARQ反馈资源，等等)。
◇根据所述PSCCH和/或所述PSSCH和/或所述SCI和/或所述TB所对应的资源池(resource pool)是否配置了HARQ反馈资源(例如PSFCH资源)确定所述“是否需要HARQ反馈”的取值。例如，若所述PSCCH和/或所述PSSCH和/或所述SCI和/或所述TB所对应的资源池配置了PSFCH资源，则需要HARQ反馈；否则不需要HARQ反馈。
◇根据发送方和接收方的距离(例如，地理距离，geographical distance)确定所述“是否需要HARQ反馈”的取值。
◇根据是否满足通信范围要求确定所述“是否需要HARQ反馈”的取值。
◇按其他方式确定所述“是否需要HARQ反馈”的取值。
○可选地，所述“是否需要HARQ反馈”可以替换为“HARQ反馈指示器”。可选地，所述“HARQ反馈指示器”的取值可以是集合{1，0}中的一个值。其中，“1”表示需要HARQ反馈，“0”表示不需要HARQ反馈。
○可选地，所述“是否需要HARQ反馈”可以替换为“是否使能HARQ反馈”。可选地，所述“是否使能HARQ反馈”的取值可以是集合{是，否}中的一个值。其中，“是”表示使能HARQ反馈，对应“需要HARQ反馈”；“否”表示不使能(或者说去使能，或者说禁止)HARQ反馈，对应“不需要HARQ反馈”。
○可选地，所述“是否需要HARQ反馈”可以替换为“是否请求HARQ反馈”。可选地，所述“是否请 求HARQ反馈”的取值可以是集合{是，否}中的一个值。其中，“是”表示请求HARQ反馈，对应“需要HARQ反馈”；“否”表示不请求HARQ反馈，对应“不需要HARQ反馈”。
◆HARQ反馈类型。其中，
○可选地，所述“HARQ反馈类型”的取值可以是集合Z＝{无，ACK，NACK，ACK或NACK}中的一个值，或者所述集合Z的任意一个子集(如Z1＝{ACK，NACK，ACK或NACK})中的一个值。其中，
◇可选地，所述集合Z中的值“无”可以表示对所述TB不发送任何HARQ反馈(无论处理所述TB的结果是什么)。
◇可选地，所述集合Z中的值“ACK”可以表示只有当处理所述TB的结果是需要反馈ACK时才发送HARQ反馈，否则不发送任何HARQ反馈。例如，若正确解码所述TB，则发送ACK。又如，若无法正确解码所述TB，则不发送任何HARQ反馈。
◇可选地，所述集合Z中的值“NACK”可以表示只有当处理所述TB的结果是需要反馈NACK时才发送HARQ反馈，否则不发送任何HARQ反馈。例如，若无法正确解码所述TB，则发送NACK。又如，若正确解码所述TB，则不发送任何HARQ反馈。
◇可选地，所述集合Z中的值“ACK或NACK”可以表示无论处理所述TB的结果是需要反馈ACK还是需要反馈NACK都发送HARQ反馈。例如，若正确解码所述TB，则发送ACK。又如，若无法正确解码所述TB，则发送NACK。
◇可选地，在上下文清楚的情况下，所述“反馈 ACK或NACK”可以称为“反馈ACK和NACK”。
○可选地，所述“HARQ反馈类型”可以根据下面中的一项或多项确定(在适用的情况下按“与”或者“或”任意组合)：
◇所述“HARQ反馈类型”可以在所述SCI中指示。
◇所述“HARQ反馈类型”可以包含在配置信息中。例如，根据配置信息确定所有SL传输都需要(或者都不需要)反馈ACK或NACK。又如，根据配置信息确定所有传播类型为单播的SL传输都需要(或者都不需要)反馈ACK或NACK。又如，根据配置信息确定所有传播类型为组播的SL传输都需要(或者都不需要)反馈ACK或NACK。
◇所述“HARQ反馈类型”可以包含在预配置信息中。例如，根据预配置信息确定所有SL传输都需要(或者都不需要)反馈ACK或NACK。又如，根据预配置信息确定所有传播类型为单播的SL传输都需要(或者都不需要)反馈ACK或NACK。又如，根据预配置信息确定所有传播类型为组播的SL传输都需要(或者都不需要)反馈ACK或NACK。
◇根据所述传播类型确定所述“HARQ反馈类型”的取值。例如，若所述传播类型为广播，则所述“HARQ反馈类型”的取值总是“无HARQ反馈”。又如，若所述传播类型为单播或组播，则根据其他条件或条件组合确定是否需要反馈(例如根据配置信息或预配置信息中的“HARQ反馈类型”，又如根据所述PSCCH和/或所述PSSCH和/或所述SCI和/或所述TB所对应的资 源池是否配置了HARQ反馈资源，等等)。
◇根据发送方和接收方的距离(例如，地理距离，geographical distance)确定所述“HARQ反馈类型”的取值。
◇根据是否满足通信范围要求确定所述“HARQ反馈类型”的取值。
◇按其他方式确定所述“HARQ反馈类型”的取值。
○可选地，若所述传播类型是广播，则所述“HARQ反馈类型”不存在。
此外，在步骤S105，报告所述HARQ信息。例如，所述UE的一个协议层(或协议子层)A向另一个协议层(或协议子层)B报告所述HARQ信息。
其中，
●可选地，所述协议层(或协议子层)A可以是所述协议层(或协议子层)B的低层(lower layer)，也可以是所述协议层或协议子层B的高层(higher layer，或者upper layer)。
●可选地，所述协议层(或协议子层)A和所述协议层(或协议子层)B中的任意一个可以是下面中的任意一项(在适用的情况下)：
◆物理层(或者说PHY层，或者说PHY子层)。
◆MAC层(或者说MAC子层)。
◆RLC层(或者说RLC子层)。
◆PDCP层(或者说PDCP子层)。
◆SDAP层(或者说SDAP子层)。
◆RRC层。
◆AS层。
◆NAS层。
◆V2X层。
◆应用层。
●可选地，只报告所述HARQ信息的一部分。
●可选地，除了报告所述HARQ信息外，还报告所述SCI和/或所述TB。
●可选地，所述“报告”也可以替换为“指示”，或者“递交”。
例如，由所述UE的物理层向高层报告所述HARQ信息的部分或全部。
又如，由所述UE的物理层向高层报告所述TB、以及所述TB所关联的HARQ信息的部分或全部。
又如，由所述UE的物理层向高层报告所述SCI、所述TB以及所述TB所关联的HARQ信息的部分或全部。
又如，若所述SCI指示存在所述TB，则由所述UE的物理层向高层报告所述TB以及所述TB所关联的HARQ信息的部分或全部。
又如，由所述UE的物理层向高层报告所述SCI，其中，所述SCI指示是否存在所述TB；此外，若存在所述TB，则由所述UE的物理层向高层报告所述TB以及所述TB所关联的HARQ信息的部分或全部。
又如，由所述UE的物理层向高层报告所述SCI、以及所述SCI所关联的HARQ信息的部分或全部。
可选地，在本发明的实施例一中，所述SCI也可以称为直行授权(sidelink grant)，或者已配置的直行授权(configured sidelink grant)。
可选地，在本发明的实施例一中，当所述SCI分成两个阶段时，“所述PSCCH”可以替换为“所述第一PSCCH”。
可选地，在本发明的实施例一中，当所述SCI分成两个阶段时，“所述PSCCH”可以替换为“所述第二PSCCH”。
可选地，在本发明的实施例一中，当所述SCI分成两个阶段时，“所述PSCCH”可以替换为“所述第一PSCCH和/或所述第二PSCCH”。
可选地，在本发明的实施例一中，当所述SCI分成两个阶段时，“所述SCI”可以替换为“所述第一阶段SCI”。
可选地，在本发明的实施例一中，当所述SCI分成两个阶段时，“所述SCI”可以替换为“所述第二阶段SCI”。
可选地，在本发明的实施例一中，当所述SCI分成两个阶段时，“所述SCI”可以替换为“所述第一阶段SCI和/或所述第二阶段SCI”。
可选地，在本发明的实施例一中，所述层1源标识符也可以称为层1源UE标识符(layer-1 source UE ID)，或者源标识符(source ID)，或者源UE标识符(source UE ID)，或者物理层源标识符(physical layer source ID)，或者物理层源UE标识符(physical layer source UE ID)。
可选地，在本发明的实施例一中，所述层1目标标识符也可以称为层1目标UE标识符(layer-1 destination UE ID)，或者目标标识符(destination ID)，或者目标UE标识符(destination UE ID)，或者物理层目标标识符(physical layer destination ID)，或者物理层目标UE标识符(physical layer destination UE ID)。
可选地，在本发明的实施例一中，若所述传播类型为组播，则所述层1目标标识符也可以称为层1目标组标识符(layer-1 destination group ID)，或者层1目标UE组标识符(layer-1 destination UE group ID)，或者目标组标识符(destination group ID)，或者目标UE组标识符(destination UE group ID)，或者物理层目标组标识符(physical layer destination group ID)，或者物理层目标UE组标识符(physical layer destination UE group ID)。
可选地，在本发明的实施例一中，所述HARQ进程ID也可以称为HARQ进程号(HARQ process number)。
可选地，在本发明的实施例一中，所述会话ID也可以称为链路ID(link ID)。
可选地，在本发明的实施例一中，所述高层可以是下面中的任意一个协议层或协议子层(在适用的情况下)：
●MAC层(或者说MAC子层)。
●RLC层(或者说RLC子层)。
●PDCP层(或者说PDCP子层)。
●SDAP层(或者说SDAP子层)。
●RRC层。
●AS层。
●NAS层。
●V2X层。
●应用层。
可选地，在本发明的实施例一中，配置信息可以包含在RRC消息或者PC5 RRC消息中。例如包含在MIB中，又如包含在SIB中，又如包含在SL MIB中，又如包含在PSBCH有效载荷(PSBCH payload)中。
可选地，在本发明的实施例一中，配置信息可以包含在MAC CE中。
可选地，在本发明的实施例一中，预配置信息可以包含在RRC消息或者PC5 RRC消息中。例如包含在SL-Preconfiguration IE中，又如包含在SL-V2X-Preconfiguration IE中。
可选地，在本发明的实施例一中，所述发送方可以指发送(或者说传输)所述PSCCH和/或所述PSSCH和/或所述SCI和/或所述TB的UE。
可选地，在本发明的实施例一中，所述接收方可以指所述UE(即执行本发明的实施例一的UE)。
可选地，在本发明的实施例一中，所述HARQ信息也可以称为SL HARQ信息。
可选地，在本发明的实施例一中，所述NACK也可以称为NAK。
可选地，在本发明的实施例一中，“反馈”也可以称为“应答”。例如，“HARQ反馈”也可以称为“HARQ应答”。
这样，本发明的实施例一通过适当地定义5G V2X的HARQ信息，使得UE的MAC子层可以准确地获取一个TB的与HARQ流程(HARQ procedure)有关的完整信息，从而正确地进行HARQ相关的操作。
[实施例二]
下面结合图2来说明本发明的实施例二的由用户设备执行的方法。
图2是示出了根据本发明的实施例二的由用户设备执行的方法的流程图。
如图2所示，在本发明的实施例二中，用户设备UE执行的步骤包括：步骤S201和步骤S203。
具体地，在步骤S201，接收一个TB及其所关联的HARQ信息。例如，所述UE的一个协议层(或协议子层)B接收另一个协议层(或协议子层)A报告的TB及其所关联的HARQ信息。
其中，
●可选地，所述“报告”也可以替换为“指示”，或者“递交”。
●可选地，所述HARQ信息的内容、指示方式、关联对象以及所有其他方面的特征和本发明的实施例一中的HARQ信息的相应特征完全一样。
●可选地，所述协议层(或协议子层)A可以是所述协议层(或协议子层)B的低层，也可以是所述协议层或协议子层B的高层。
●可选地，所述协议层(或协议子层)A和所述协议层(或协议子层)B中的任意一个可以是下面中的任意一项(在适用的情况下)：
◆物理层(或者说PHY层，或者说PHY子层)。
◆MAC层(或者说MAC子层)。
◆RLC层(或者说RLC子层)。
◆PDCP层(或者说PDCP子层)。
◆SDAP层(或者说SDAP子层)。
◆RRC层。
◆AS层。
◆NAS层。
◆V2X层。
◆应用层。
例如，所述协议层(或协议子层)A是物理层，所述协议层(或协议子层)B是MAC层(或者说MAC子层)。
●可选地，只接收所述HARQ信息中的一部分。
●可选地，额外地，还接收调度所述TB的SCI。
例如，所述UE的MAC层(或者说MAC子层)从物理层接收一个TB及其所关联的HARQ信息。
此外，在步骤S203，将所述TB和/或所述HARQ信息分配给一个SL HARQ进程(sidelink HARQ process)。
其中，
●可选地，额外地，将所述SL HARQ进程和所述SCI关联。
●可选地，所述SL HARQ进程由一个SL HARQ实体(sidelink HARQ entity)维护。其中，
◆可选地，对每个SL载波(SL carrier)，存在一个SL HARQ实体。
◆可选地，所述SL HARQ实体维护一个或多个SL HARQ进程。
◆可选地，所述SL HARQ实***于所述UE的一个MAC实体中。
◆可选地，在上下文清楚的情况下又将SL HARQ实体称为HARQ实体。
●可选地，根据在实施例一中已描述过的HARQ信息中的一项或多项，和/或其他信息，确定要分配的SL HARQ进程。
例如，所述SL HARQ实体中可以存在一个唯一的与广播有关的SL HARQ进程(例如称为SL广播HARQ进程)。此时，若所述HARQ信息中的传播类型是广播，则将要分配的SL HARQ进程确定为所述SL广播HARQ进程。
又如，若所述HARQ信息中的传播类型是广播，则根据所述HARQ信息中的层1源标识符确定一个SL HARQ进程。
又如，若所述HARQ信息中的传播类型是广播，则根据所述HARQ信息中的层1源标识符和HARQ进程标识符确定一个SL HARQ进程。
又如，若所述HARQ信息中的传播类型是单播，则根据所述HARQ信息中的层1源标识符、层1目标标识符和HARQ进程标识符确定一个SL HARQ进程。
又如，若所述HARQ信息中的传播类型是组播，则根据所述HARQ信息中的层1源标识符、层1目标标识符和HARQ进程 标识符确定一个SL HARQ进程。
可选地，在本发明的实施例二中，在上下文清楚的情况下又将SL HARQ进程称为HARQ进程。
可选地，在本发明的实施例二中，在上下文清楚的情况下又将SL HARQ进程称为SL进程。
这样，本发明的实施例二根据HARQ信息中的传播类型及各个标识符将所接收到的TB分配给不同的SL HARQ进程，确保了在UE的物理层支持盲重传(blind retransmission)和/或HARQ重传和/或多个源/目标ID和/或多种传播类型的情况下，一个TB的多次传输可以有效地进行合并，确保了HARQ合并的性能。
[实施例三]
下面结合图3来说明本发明的实施例三的由用户设备执行的方法。
图3是示出了根据本发明的实施例三的由用户设备执行的方法的流程图。
如图3所示，在本发明的实施例三中，用户设备UE执行的步骤包括：步骤S301和步骤S303。
具体地，在步骤S301，接收一个TB及其所关联的HARQ信息。例如，所述UE的一个协议层(或协议子层)B接收另一个协议层(或协议子层)A报告的TB及其所关联的HARQ信息。
其中，
●可选地，所述“报告”也可以替换为“指示”，或者“递交”。
●可选地，所述HARQ信息的内容、指示方式、关联对象以及所有其他方面的特征和本发明的实施例一中的HARQ信息的相应特征完全一样。
●可选地，所述协议层(或协议子层)A可以是所述协议层(或协议子层)B的低层，也可以是所述协议层或协议子层B的高 层。
●可选地，只接收所述HARQ信息中的一部分。
例如，所述UE的MAC层(或者说MAC子层)从物理层接收一个TB及其所关联的HARQ信息。
此外，在步骤S303，确定是否命令(instruct)协议层(或协议子层)C产生对所述TB中的数据的应答。
其中，
●可选地，所述“对所述TB中的数据的应答”也可以称为“对所述TB的应答”。
●可选地，所述应答可以包括肯定应答(positive acknowledgement)。
●可选地，所述应答可以包括否定应答(negative acknowledgement)。
例如，若“无应答”条件成立，则不命令所述协议层(或协议子层)C产生对所述TB中的数据的应答。又如，若“无应答”条件不成立，则命令所述协议层(或协议子层)C产生对所述TB中的数据的应答。其中，所述“无应答”条件可以包括下面中的一项或多项(在适用的情况下按“与”或者“或”任意组合)：
●所述HARQ信息中的传播类型是广播。
●所述HARQ信息中的“是否需要HARQ反馈”的值是“否”。
●所述HARQ信息中的“HARQ反馈类型”是“无”。
可选地，在本发明的实施例三中，所述协议层(或协议子层)A、所述协议层(或协议子层)B、以及所述协议层(或协议子层)C中的任意一个可以是下面中的任意一项(在适用的情况下)：
●物理层(或者说PHY层，或者说PHY子层)。
●MAC层(或者说MAC子层)。
●RLC层(或者说RLC子层)。
●PDCP层(或者说PDCP子层)。
●SDAP层(或者说SDAP子层)。
●RRC层。
●AS层。
●NAS层。
●V2X层。
●应用层。
例如，所述协议层(或协议子层)A是物理层，所述协议层(或协议子层)B是MAC层(或者说MAC子层)，所述协议层(或协议子层)C是物理层。
这样，本发明的实施例三根据HARQ信息中的传播类型及其他与HARQ应答相关的信息，确定是否命令物理层产生对所接收到的TB的应答，确保了UE的HARQ流程同时支持基于HARQ反馈的传输和无HARQ反馈的传输。
[变形例]
下面，利用图4来说明作为一种变形例的可执行本发明上面所详细描述的用户设备执行的方法的用户设备。
图4是表示本发明所涉及的用户设备UE的框图。
如图4所示，该用户设备UE40包括处理器401和存储器402。处理器401例如可以包括微处理器、微控制器、嵌入式处理器等。存储器402例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器402上存储有程序指令。该指令在由处理器401运行时，可以执行本发明详细描述的由用户设备执行的上述方法。
上文已经结合优选实施例对本发明的方法和涉及的设备进行了描述。本领域技术人员可以理解，上面示出的方法仅是示例性的，而且以上说明的各实施例在不发生矛盾的情况下能够相互组合。本发明的方法并不局限于上面示出的步骤和顺序。上面示出的网络节点和用户设备可以包括更多的模块，例如还可以包括可以开发的或者将来开发的可用于基站、MME、或UE的模块等等。上文中示出的各种标识仅是示例性的而不是限制性的， 本发明并不局限于作为这些标识的示例的具体信元。本领域技术人员根据所示实施例的教导可以进行许多变化和修改。
应该理解，本发明的上述实施例可以通过软件、硬件或者软件和硬件两者的结合来实现。例如，上述实施例中的基站和用户设备内部的各种组件可以通过多种器件来实现，这些器件包括但不限于：模拟电路器件、数字电路器件、数字信号处理(DSP)电路、可编程处理器、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、可编程逻辑器件(CPLD)，等等。
在本申请中，“基站”可以指具有一定发射功率和一定覆盖面积的移动通信数据和控制交换中心，包括资源分配调度、数据接收发送等功能。“用户设备”可以指用户移动终端，例如包括移动电话、笔记本等可以与基站或者微基站进行无线通信的终端设备。
此外，这里所公开的本发明的实施例可以在计算机程序产品上实现。更具体地，该计算机程序产品是如下的一种产品：具有计算机可读介质，计算机可读介质上编码有计算机程序逻辑，当在计算设备上执行时，该计算机程序逻辑提供相关的操作以实现本发明的上述技术方案。当在计算***的至少一个处理器上执行时，计算机程序逻辑使得处理器执行本发明实施例所述的操作(方法)。本发明的这种设置典型地提供为设置或编码在例如光介质(例如CD-ROM)、软盘或硬盘等的计算机可读介质上的软件、代码和/或其他数据结构、或者诸如一个或多个ROM或RAM或PROM芯片上的固件或微代码的其他介质、或一个或多个模块中的可下载的软件图像、共享数据库等。软件或固件或这种配置可安装在计算设备上，以使得计算设备中的一个或多个处理器执行本发明实施例所描述的技术方案。
此外，上述每个实施例中所使用的基站设备和终端设备的每个功能模块或各个特征可以由电路实现或执行，所述电路通常为一个或多个集成电路。设计用于执行本说明书中所描述的各个功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)或通用集成电路、现场可编程门阵列(FPGA)或其他可编程逻辑器件、分立的门或晶体管逻辑、或分立的硬件组件、或以上器件的任意组合。通用处理器可以是微处理器，或者所述处理器可以是现有的处理器、控制器、微控制器或状态 机。上述通用处理器或每个电路可以由数字电路配置，或者可以由逻辑电路配置。此外，当由于半导体技术的进步，出现了能够替代目前的集成电路的先进技术时，本发明也可以使用利用该先进技术得到的集成电路。
尽管以上已经结合本发明的优选实施例示出了本发明，但是本领域的技术人员将会理解，在不脱离本发明的精神和范围的情况下，可以对本发明进行各种修改、替换和改变。因此，本发明不应由上述实施例来限定，而应由所附权利要求及其等价物来限定。

Claims (10)

  1. 一种由用户设备执行的方法，其特征在于包括：
    接收直行控制信息SCl；以及
    确定与所述SCl相关联的直行混合自动重复请求SL HARQ信息。
  2. 根据权利要求1所述的方法，其特征在于，
    所述SL HARQ信息包括以下一项或多项：
    传播类型、层1源标识符、层1目标标识符、HARQ进程标识符、新数据指示符、冗余版本、会话标识符、传输块大小、发送方和接收方的距离、通信范围要求、表示是否满足通信范围要求的信息、表示是否需要HARQ反馈的信息、以及HARQ反馈类型。
  3. 根据权利要求1所述的方法，其特征在于，
    所述传播类型包括：单播、组播和广播中的任一个。
  4. 根据权利要求1所述的方法，其特征在于还包括：
    在报告所述SL HARQ信息的同时报告所述SCI和/或相应的传输块TB。
  5. 一种由用户设备执行的方法，其特征在于包括：
    在介质访问控制MAC子层从物理层接收与直行控制信息SCl相关联的直行混合自动重复请求SL HARQ信息；以及
    将所述SL HARQ信息和/或相应的传输块TB分配给直行HARQ进程。
  6. 根据权利要求5所述的方法，其特征在于，
    根据所述HARQ信息中包括的以下一项或多项，确定要分配的直行HARQ进程：
    传播类型、层1源标识符、层1目标标识符、HARQ进程标识符、新数据指示符、冗余版本、会话标识符、传输块大小、发送方和接收方的距离、通信范围要求、表示是否满足通信范围要求的信息、表示是否需要HARQ反馈的信息、以及HARQ反馈类型。
  7. 一种由用户设备执行的方法，其特征在于包括：
    在介质访问控制MAC子层从物理层接收与直行控制信息SCl相关联 的直行混合自动重复请求SL HARQ信息；以及
    确定是否命令物理层产生对相应的传输块TB中的数据的应答。
  8. 根据权利要求7所述的方法，其特征在于，
    若无应答条件成立，则不命令物理层产生对所述TB中的数据的应答；若无应答条件不成立，则命令物理层产生对所述TB中的数据的应答，其中，所述无应答条件包括以下一项或多项：
    所述SL HARQ信息中的传播类型是广播、所述SL HARQ信息中的“是否需要HARQ反馈”的值是“否”、所述SL HARQ信息中的“HARQ反馈类型”是“无”。
  9. 根据权利要求7所述的方法，其特征在于，
    所述SL HARQ信息包括以下一项或多项：
    传播类型、层1源标识符、层1目标标识符、HARQ进程标识符、新数据指示符、冗余版本、会话标识符、传输块大小、发送方和接收方的距离、通信范围要求、表示是否满足通信范围要求的信息、表示是否需要HARQ反馈的信息、以及HARQ反馈类型。
  10. 一种用户设备，包括：
    处理器；以及
    存储器，存储有指令，
    其中，所述指令在由所述处理器运行时执行根据权利要求1-9中的任一项所述的方法。
PCT/CN2020/102437 2019-07-17 2020-07-16 由用户设备执行的方法以及用户设备 WO2021008587A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/627,308 US20220247539A1 (en) 2019-07-17 2020-07-16 Method performed by user equipment, and user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910648773.3A CN112242882A (zh) 2019-07-17 2019-07-17 由用户设备执行的方法以及用户设备
CN201910648773.3 2019-07-17

Publications (1)

Publication Number Publication Date
WO2021008587A1 true WO2021008587A1 (zh) 2021-01-21

Family

ID=74167494

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/102437 WO2021008587A1 (zh) 2019-07-17 2020-07-16 由用户设备执行的方法以及用户设备

Country Status (3)

Country Link
US (1) US20220247539A1 (zh)
CN (1) CN112242882A (zh)
WO (1) WO2021008587A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024055916A1 (zh) * 2022-09-13 2024-03-21 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210067290A1 (en) * 2019-08-26 2021-03-04 Mediatek Singapore Pte. Ltd. Sidelink communications with two-stage sidelink control information
US11751200B2 (en) * 2019-10-15 2023-09-05 Mediatek Singapore Pte. Ltd. Physical channel structures for sidelink communication
US11722259B2 (en) * 2019-10-30 2023-08-08 Qualcomm Incorporated Hybrid automatic repeat request (HARQ) process when using sidelink for retransmission
WO2021091340A1 (en) * 2019-11-07 2021-05-14 Lg Electronics Inc. Method and apparatus for transmitting psfch in nr v2x
US20220303055A1 (en) * 2020-05-21 2022-09-22 Apple Inc. Flexible HARQ Mechanism Adaptation for Sidelink Unicast and Groupcast
US11706752B2 (en) * 2020-07-09 2023-07-18 Qualcomm Incorporated Semi-persistent scheduling (SPS) for sidelink groupcast
CN115462018A (zh) * 2021-03-24 2022-12-09 北京小米移动软件有限公司 Harq反馈的方法、装置、通信设备及存储介质
US11930498B2 (en) * 2021-09-07 2024-03-12 Qualcomm Incorporated Techniques for scheduling sidelink communications in multiple time periods
CN115835381A (zh) * 2021-09-17 2023-03-21 展讯通信（上海）有限公司 通信方法及装置、计算机可读存储介质及计算机程序产品
US11943056B2 (en) * 2021-09-24 2024-03-26 Qualcomm Incorporated Flexible frequency domain resource allocation for sidelink
US20230254861A1 (en) * 2022-02-07 2023-08-10 Qualcomm Incorporated Multi-transport block sidelink scheduling
CN115516797A (zh) * 2022-08-12 2022-12-23 北京小米移动软件有限公司 一种harq反馈方法及其装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101924618A (zh) * 2009-06-12 2010-12-22 重庆重邮信科通信技术有限公司 一种td-hsupa中harq的实现方法
CN108923894A (zh) * 2017-03-23 2018-11-30 中兴通讯股份有限公司 一种信息传输的方法、装置和***
US20190044667A1 (en) * 2017-08-04 2019-02-07 Samsung Electronics Co., Ltd. Methods and apparatus for resource allocation and feedback in vehicle to vehicle communication
CN109792594A (zh) * 2018-12-29 2019-05-21 北京小米移动软件有限公司 直连通信的数据传输方法、装置、设备及***

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014142464A1 (en) * 2013-03-13 2014-09-18 Lg Electronics Inc. Method for transmitting and receiving information for interference cancellation, and apparatus therefor
EP3255950A1 (en) * 2016-06-06 2017-12-13 ASUSTek Computer Inc. Method and apparatus for resource allocation on d2d relay channel in a wireless communication system
US10931426B2 (en) * 2017-08-10 2021-02-23 Futurewei Technologies, Inc. System and method for sidelink feedback

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101924618A (zh) * 2009-06-12 2010-12-22 重庆重邮信科通信技术有限公司 一种td-hsupa中harq的实现方法
CN108923894A (zh) * 2017-03-23 2018-11-30 中兴通讯股份有限公司 一种信息传输的方法、装置和***
US20190044667A1 (en) * 2017-08-04 2019-02-07 Samsung Electronics Co., Ltd. Methods and apparatus for resource allocation and feedback in vehicle to vehicle communication
CN109792594A (zh) * 2018-12-29 2019-05-21 北京小米移动软件有限公司 直连通信的数据传输方法、装置、设备及***

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024055916A1 (zh) * 2022-09-13 2024-03-21 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置

Also Published As

Publication number Publication date
CN112242882A (zh) 2021-01-19
US20220247539A1 (en) 2022-08-04

Similar Documents

Publication Publication Date Title
WO2021008587A1 (zh) 由用户设备执行的方法以及用户设备
WO2020221241A1 (zh) 由用户设备执行的方法以及用户设备
US20220312388A1 (en) Method performed by user equipment, and user equipment
WO2021197204A1 (zh) 由用户设备执行的方法以及用户设备
WO2020192647A1 (zh) 由用户设备执行的方法以及用户设备
WO2021160033A1 (zh) 由用户设备执行的方法以及用户设备
WO2021057960A1 (zh) 由用户设备执行的方法以及用户设备
WO2020192695A1 (zh) 由用户设备执行的方法
WO2017078165A1 (ja) 端末装置、基地局装置、通信方法、および、集積回路
WO2022068685A1 (zh) 由用户设备执行的方法以及用户设备
WO2021204191A1 (zh) 由用户设备执行的方法以及用户设备
WO2021136373A1 (zh) 由用户设备执行的方法以及用户设备
WO2021228136A1 (zh) 由用户设备执行的方法以及用户设备
WO2022028274A1 (zh) 由用户设备执行的方法以及用户设备
WO2021160032A1 (zh) 由用户设备执行的方法以及用户设备
WO2022028328A1 (zh) 由用户设备执行的方法以及用户设备
US20220417959A1 (en) Method performed by user equipment, and user equipment
WO2021238757A1 (zh) 由用户设备执行的方法以及用户设备
WO2021197210A1 (zh) 由用户设备执行的方法以及用户设备
WO2022022377A1 (zh) 由用户设备执行的方法以及用户设备
WO2021139619A1 (zh) 由用户设备执行的方法以及用户设备
WO2021088486A1 (zh) 由用户设备执行的方法以及用户设备
WO2021027833A1 (zh) 由用户设备执行的方法以及用户设备
WO2021063337A1 (zh) 由用户设备执行的方法以及用户设备
WO2017078139A1 (ja) 端末装置、基地局装置、通信方法、および、集積回路

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20840952

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20840952

Country of ref document: EP

Kind code of ref document: A1