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

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

Info

Publication number
WO2020164452A1
WO2020164452A1 PCT/CN2020/074607 CN2020074607W WO2020164452A1 WO 2020164452 A1 WO2020164452 A1 WO 2020164452A1 CN 2020074607 W CN2020074607 W CN 2020074607W WO 2020164452 A1 WO2020164452 A1 WO 2020164452A1
Authority
WO
WIPO (PCT)
Prior art keywords
size
bwp
dci format
rbs
frequency domain
Prior art date
Application number
PCT/CN2020/074607
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/430,986 priority Critical patent/US20220140968A1/en
Publication of WO2020164452A1 publication Critical patent/WO2020164452A1/zh

Links

Images

Classifications

    • 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/0091—Signaling for the administration of the divided path
    • H04L5/0096—Indication of changes in allocation
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • 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/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • 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/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • 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

Definitions

  • the present invention relates to the field of wireless communication technology, and in particular to methods executed by user equipment and corresponding user equipment.
  • Non-Patent Document 2 a new research project on 5G technical standards (see Non-Patent Document 1) was approved.
  • the purpose of this research project is to develop a new radio (New Radio: NR) access technology to meet all 5G application scenarios, requirements and deployment environments.
  • NR has three main application scenarios: Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC) and Ultra-Reliable and Low Latency Communications: URLLC) .
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • URLLC Ultra-Reliable and Low Latency Communications
  • 5G uses DCI (Downlink Control Information, Downlink Control Information) to schedule downlink transmission on PDSCH (Physical Downlink Shared Channel) and uplink transmission on PUSCH (Physical Uplink Shared Channel).
  • DCI Downlink Control Information, Downlink Control Information
  • 5G supports multiple DCI formats, as shown in Table 1. After channel coding of each DCI format, its CRC can be scrambled with an RNTI (Radio-Network Temporary Identifier) to indicate a specific use and/or one or more target UEs. For example, the CRC used to indicate the DCI format of paging may be scrambled with P-RNTI.
  • RNTI Radio-Network Temporary Identifier
  • the 5G DCI is carried on the PDCCH (Physical Downlink Control Channel).
  • a PDCCH is composed of one or more CCEs (control-channel elements, control channel elements), and a CCE is composed of multiple (for example, 6) REGs (resource-element groups), and REGs are It is defined in CORESET (control-resource set).
  • a CORESET contains multiple resource blocks in the frequency domain (each resource block is composed of 12 consecutive sub-carriers in the frequency domain), and contains one or more (for example, 1, or 2, or 3) in the time domain ) OFDM symbol.
  • the UE monitors the PDCCH transmission of the base station on one or more search space sets (search space sets), where each search space set may correspond to a set of PDCCH candidates (PDCCH candidates).
  • search space sets search space sets
  • the UE performs blind detection (blind detection) at the time and frequency position of the PDCCH candidate to be monitored to determine whether there is a PDCCH sent to itself.
  • the search space collection can be divided into CSS (Common Search Space) collection and USS (UE-specific search space, UE-specific search space) collection, for example:
  • ⁇ Type 0-PDCCH CSS collection For example, it is configured through the pdcch-ConfigSIB1 parameter in the MIB, or through the searchSpaceSIB1 parameter in the PDCCH-ConfigCommon IE, or through the searchSpaceZero parameter in the PDCCH-ConfigCommon IE.
  • the CRC of the corresponding DCI format can be scrambled with SI-RNTI.
  • ⁇ Type 0A-PDCCH CSS collection For example, it is configured through the searchSpaceOtherSystemInformation parameter in the PDCCH-ConfigCommon IE.
  • the CRC of the corresponding DCI format can be scrambled with SI-RNTI.
  • ⁇ Type 1-PDCCH CSS collection For example, it is configured through the ra-SearchSpace parameter in PDCCH-ConfigCommon IE.
  • the CRC of the corresponding DCI format can be scrambled with RA-RNTI or TC-RNTI.
  • ⁇ Type 2-PDCCH CSS collection For example, it is configured through the pagingSearchSpace parameter in PDCCH-ConfigCommon IE.
  • the CRC of the corresponding DCI format can be scrambled with P-RNTI.
  • the result is one or more type 3-PDCCH CSS configured through the SearchSpace IE, and the searchSpaceType parameter of each of them is configured as common.
  • the CRC of the corresponding DCI format can use INT-RNTI, or SFI-RNTI, or TPC-PUSCH-RNTI, or TPC-PUCCH-RNTI, or TPC-SRS-RNTI, or C-RNTI, or MCS-C-RNTI, Or CS-RNTI scrambling.
  • the result is one or more USS configured through the SearchSpace IE, and the searchSpaceType parameter of each of them is configured as ue-Specific.
  • the CRC of the corresponding DCI format can be scrambled with C-RNTI, or MCS-C-RNTI, or SP-CSI-RNTI, or CS-RNTI.
  • the UE needs to assume a DCI size (DCI size) when blindly detecting PDCCH candidates. Due to the limitation of processing capacity, the UE can only monitor a certain number of DCI sizes in each time slot.
  • Table 2 summarizes the types of search space sets classified according to the DCI size, their corresponding DCI formats, and the RNTI used to scramble DCI and CRC. among them,
  • All rows of the same "DCI size category" (for example, a combination of all search space set types, DCI formats, and RNTI corresponding to 1_0_css) correspond to the same DCI size.
  • the "DCI size" column is just an example of possible DCI sizes.
  • the actual DCI size depends on system configuration information and/or UE-specific configuration information.
  • the DCI format associated with a given USS set can only be 0_0 and 1_0, or 0_1 and 1_1.
  • FDRA Frequency Domain Resource Assignment, frequency domain resource assignment
  • DCI formats 1_0 and 1_1 the size of FDRA and Relevant (for example, the size of FDRA can be Bits); in DCI formats 0_0 and 0_1, the size of FDRA and related. among them, with The value of depends on the DCI format and the type of the corresponding search space set, and may be adjusted to meet the limitation of the DCI size.
  • the search space set, DCI format, and RNTI configured by the network for the UE must meet all the following conditions:
  • the existing 3GPP 5G standard defines a DCI size alignment process as follows:
  • Step 0 (determine 0_0_css and 1_0_css, and align the size of 0_0_css to the size of 1_0_css):
  • the size of the frequency domain resource allocation field in DCI format 0_0 and Related (for example, the size of the frequency domain resource allocation field is Bits), It is equal to the size of the initial uplink BWP (for example, configured through the parameter initialUplinkBWP).
  • the size of the frequency domain resource allocation field in DCI format 1_0 and Related (for example, the size of the frequency domain resource allocation field is Bits). If CORESET 0 has been configured in the cell, then Equal to the size of CORESET 0; if CORESET 0 is not configured in the cell, then It is equal to the size of the initial downlink BWP (for example, configured through the parameter initialDownlinkBWP).
  • the UE is configured to monitor the DCI format 0_0 in the CSS, and the number of information bits of the 0_0_css before filling is less than the load size of the 1_0_css used to schedule the same serving cell, then zero filling is performed on the 0_0_css until the The load size of 0_0_css is equal to the load size of 1_0_css.
  • the 0_0_css IF resource allocation field is truncated To reduce the bit width of the frequency domain resource allocation field, the number of most significant bits at the beginning of, so that the size of 0_0_css is equal to the size of 1_0_css.
  • Step 1 (determine 0_0_uss and 1_0_uss, and align the smaller to the larger):
  • the size of the frequency domain resource allocation field in DCI format 0_0 and Related (for example, the size of the frequency domain resource allocation field is Bits), Equal to the size of the effective upstream BWP.
  • the size of the frequency domain resource allocation field in DCI format 1_0 and Related (for example, the size of the frequency domain resource allocation field is Bits). Equal to the size of the effective downlink BWP.
  • the UE If the UE is configured to monitor the DCI format 0_0 in the USS, and the number of information bits of the 0_0_uss before filling is less than the load size of the 1_0_uss used to schedule the same serving cell, then perform zero filling on the 0_0_uss until the The load size of 0_0_uss is equal to the load size of 1_0_uss.
  • the UE If the UE is configured to monitor the DCI format 1_0 in the USS, and the number of information bits of the 1_0_uss before filling is less than the load size of the 0_0_uss used to schedule the same serving cell, then perform zero filling on the 1_0_uss until the The load of 1_0_uss is equal to the load of 0_0_uss.
  • Step 2 (If necessary, fill 0_1_uss and/or 1_1_uss with 0 so that the size of either of them is not equal to the size of 0_0_uss/1_0_uss):
  • Step 3 (if the DCI size limit is met, the process ends):
  • Step 4 (otherwise step 2 is cancelled, 1_0_uss and 0_0_uss are re-determined, and the sizes of 1_0_uss and 0_0_uss are aligned to 1_0_css/0_0_css):
  • the size of the frequency domain resource allocation field in DCI format 1_0 is Related (for example, the size of the frequency domain resource allocation field is Bits). If CORESET 0 has been configured in the cell, then Equal to the size of CORESET 0; if CORESET 0 is not configured in the cell, then It is equal to the size of the initial downlink BWP (for example, configured by the parameter initialDownlinkBWP).
  • the size of the frequency domain resource allocation field in DCI format 0_0 is Related (for example, the size of the frequency domain resource allocation field is Bits), It is equal to the size of the initial uplink BWP (for example, configured by the parameter initialUplinkBWP).
  • the most significant bits at the beginning of the frequency domain resource allocation field in the 0_0_css are truncated to reduce
  • the bit width of the frequency domain resource allocation field is such that the size of 0_0_uss is equal to the size of 1_0_uss.
  • the size of 1_0_uss is determined by the size of 1_0_css.
  • the size of the frequency domain resource allocation field in 1_0_uss is also determined by the size of the initial downlink BWP or CORESET 0.
  • the frequency domain resources allocated by 1_0_uss are on the effective downlink BWP. Therefore, if the size of the effective downlink BWP and the size of the initial downlink BWP or CORESET 0 are quite different, the frequency domain resources that can be allocated by 1_0_uss may be very affected. limit.
  • the effective downlink BWP size is 100 PRBs
  • the initial downlink BWP size is 20 PRBs (CORESET 0 is not configured in the cell, so the size of the frequency domain allocation field of 1_0_css is determined by the initial downlink BWP), then the frequency domain resource allocation of 1_0_uss
  • the field can only allocate a part of the PRB in the valid downlink BWP. Therefore, the existing 3GPP standards for 5G have introduced "scaling" for frequency domain resource allocation.
  • the resource indicator value can be defined as follows:
  • L' RBs L RBs /K
  • RB' start RB start /K
  • the uplink frequency domain resource allocation also needs to be similarly scaled.
  • the FDRA field contains a RIV (Resource Indication Value). Value), each RIV corresponds to a starting resource block RB start and the length of a continuously allocated resource block L RBs .
  • the resource indicator value can be defined as follows:
  • L RBs ⁇ 1 and not more than If the DCI corresponding to the FDRA field is 1_0_css (0_0_css), otherwise,
  • the value range of RB start and L RBs is always Defined by reference; if Then the value range of RB start and L RBs will fall outside the effective downlink BWP.
  • the DCI corresponding to the FDRA field is 1_0_css but the effective downlink BWP is not the initial downlink BWP, the range of values for RB start and L RBs is also It is defined for reference, so there will be similar problems.
  • the value range of RB start and L RBs is always Defined by reference; if Then the value range of RB start and L RBs will fall outside the effective uplink BWP.
  • the DCI corresponding to the FDRA field is 0_0_css but the effective uplink BWP is not the initial uplink BWP, the range of values for RB start and L RBs is also It is defined for reference, so there will be similar problems.
  • V2X communication refers to the communication between a vehicle and any entity that may affect the vehicle.
  • Typical V2X communication includes V2I (Vehicle-to-Infrastructure), V2N (Vehicle-to-network, vehicle-to-network), V2V (Vehicle-to-vehicle, vehicle-to-vehicle), V2P (Vehicle-to -Pedestrian, vehicle to pedestrian) etc.
  • V2X (Rel-16) research project the interface between UE and UE used to implement V2X communication is called PC5, and is also called sidelink at the physical layer (referred to as "straight line” or “side line” in this disclosure, or Abbreviated as SL) link, to distinguish it from uplink and downlink.
  • SL sidelink at the physical layer
  • the signals and channels used for SL synchronization in V2X include:
  • ⁇ SL PSS Sidelink Primary Synchronization Signal, direct primary synchronization signal
  • S-PSS S-PSS
  • PSSS Primary Sidelink Synchronization Signal, primary direct synchronization signal
  • ⁇ SL SSS Sidelink Secondary Synchronization Signal
  • S-SSS S-SSS
  • SSSS Secondary Sidelink Synchronization Signal, secondary direct synchronization signal
  • ⁇ PSBCH Physical Sidelink Broadcast Channel, physical direct broadcast channel
  • SL PSS, SL SSS, and PSBCH are organized into blocks on the time-frequency resource grid, called SL SSB (Sidelink SS/PBCH block, direct synchronization signal/physical broadcast channel block), or S-SSB.
  • the transmission bandwidth of the SL SSB is within the SL BWP (Sidelink Bandwidth Part) configured for the UE.
  • ⁇ PSSCH Physical Sidelink Shared Channel, physical direct shared channel
  • ⁇ PSCCH Physical Sidelink Control Channel, physical direct control channel
  • ⁇ PSFCH Physical Sidelink Feedback Channel, physical direct feedback channel
  • the scrambling sequence between the SL channels sent by different UEs may conflict.
  • ⁇ UE IDs determined by different UEs may conflict, resulting in failure to correctly identify the source and/or destination UE ID at the physical layer.
  • the UE implemented according to the old version of the standard protocol may not be able to recognize the SCI format implemented according to the new version of the standard protocol, and thus cannot read the resource reservation field in the new SCI format, and thus cannot understand the reservation of the new UE Resources, leading to resource reservation conflicts.
  • the UE may not be able to recognize at the physical layer whether the received PSCCH/PSSCH transmission is for unicast, multicast or broadcast communication.
  • Non-Patent Document 1 RP-160671, New SID Proposal: Study on New Radio Access Technology
  • Non-Patent Document 2 RP-170855, New WID on New Radio Access Technology
  • Non-Patent Document 3 RP-181429, New SID: Study on NR V2X
  • the present invention provides a method executed by a user equipment and a user equipment, which can ensure that the frequency domain resources allocated in the DCI fall within the effective downlink BWP, and avoid the frequency domain resources allocated due to the frequency domain resources. Inter-user interference caused by falling outside the effective downlink BWP.
  • a method executed by a user equipment including: receiving downlink control information DCI for scheduling transmission of a physical downlink shared channel PDSCH; and allocating an FDRA field according to the frequency domain resources in the received DCI , Determine the resource indicator value RIV, and determine the allocated starting resource block RB start and the length of the continuously allocated resource block L RBs according to the RIV, where if the frequency domain resource allocation scaling condition is not met, then according to the RIV Determine RB start and L RBs directly.
  • the frequency domain resource allocation scaling conditions are met, first determine the starting resource block RB' start obtained by dividing RB start by the scaling factor K according to the RIV, and dividing L RBs by the length L 'RBs, then according RB' continuous resource blocks allocated after determining the scaling factor K obtained L RBs start and the RB start and L 'RBs, in accordance with the scaling factor K versus To determine the ratio of Indicates the size of the initial downlink bandwidth segment BWP, Indicates the size of the effective downstream BWP.
  • RB' start and L' RBs satisfy one or more of the following relationships:
  • the frequency domain resource allocation scaling condition includes: the size of the DCI format is derived from a first reference size,
  • the first reference size can be defined in any of the following ways:
  • the control resource set CORESET with ID 0 is the size of CORESET 0;
  • the first reference size is equal to the size of CORESET 0; if CORESET 0 is not configured in the cell, the first reference size is equal to the size of the initial downlink BWP;
  • the frequency domain resource allocation scaling condition includes: the size of the DCI format is applied to a reference BWP that meets a reference BWP condition,
  • the reference BWP can be any of the following:
  • a method executed by a user equipment including: receiving downlink control information DCI for scheduling transmission of a physical uplink shared channel PUSCH; and allocating frequency domain resources according to the received DCI FDRA field, determine the resource indicator value RIV, and determine the starting resource block RB start allocated and the length of the continuously allocated resource block L RBs according to the RIV. If the frequency domain resource allocation scaling condition is not met, then The RIV directly determines RB start and L RBs .
  • the frequency domain resource allocation scaling condition is met, first determine the start resource block RB' start obtained by dividing RB start by the scaling factor K according to the RIV and dividing L RBs by after the scaling factor K to give continuous assigned a length L 'RBs, then according RB' determines resource blocks RB start and L RBs start and L 'RBs, in accordance with the scaling factor K versus To determine the ratio of Indicates the size of the initial uplink bandwidth segment BWP, Indicates the size of the effective upstream BWP.
  • RB' start and L' RBs satisfy one or more of the following relationships:
  • the frequency domain resource allocation scaling condition includes: the size of the DCI format is derived from a third reference size,
  • the third reference size can be defined in any of the following ways:
  • the frequency domain resource allocation scaling condition includes: the size of the DCI format is applied to a reference BWP that meets a reference BWP condition,
  • the reference BWP can be any of the following:
  • a user equipment including: a processor; and a memory storing instructions, wherein the instructions execute the above-mentioned method when run by the processor.
  • the present invention it can be ensured that the frequency domain resources allocated in the DCI fall within the effective downlink BWP, and the inter-user interference caused by the allocated frequency domain resources falling outside the effective downlink BWP is avoided.
  • 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 flowchart showing a method executed by a user equipment according to the fourth embodiment of the present invention.
  • Fig. 5 is a flowchart showing a method executed by a user equipment according to the fifth embodiment of the present invention.
  • Fig. 6 is a flowchart showing a method executed by a user equipment according to the sixth embodiment of the present invention.
  • Fig. 7 is a block diagram schematically showing a 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
  • DCI Downlink Control Information, downlink control information
  • 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
  • FDRA Frequency Domain Resource Assignment, frequency domain resource allocation
  • IP Internet Protocol, Internet Protocol
  • LCID Logical Channel ID, logical channel identifier
  • LTE-A Long Term Evolution-Advanced, an upgraded version of long-term evolution technology
  • 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
  • mMTC Massive Machine Type Communication, large-scale machine type communication
  • 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
  • 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
  • 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
  • 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 PSS Sidelink Primary Synchronization Signal, direct main synchronization signal
  • SL SSB Sidelink SS/PBCH block, direct synchronization signal/physical broadcast channel block
  • SL SSS Sidelink Secondary Synchronization Signal, direct-travel secondary synchronization signal
  • 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 Advanced Group, timing advance group
  • 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
  • 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
  • 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 and step S103.
  • step S101 downlink control information (DCI) is received.
  • DCI downlink control information
  • the DCI can be used to schedule PDSCH transmission (for example, using DCI format 1_0), and can also be used for other purposes.
  • the DCI may be a DCI monitored in a user-specific search space (UE-specific Search Space, USS).
  • UE-specific Search Space USS
  • the DCI may also be a DCI monitored in a common search space (Common Search Space, CSS).
  • a common search space Common Search Space, CSS
  • the CRC of the DCI can be scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI, or other RNTI.
  • the DCI may include a frequency domain resource assignment (Frequency Domain Resource Assignment, FDRA) field.
  • FDRA Frequency Domain Resource Assignment
  • the frequency domain resource allocation method used by the DCI can be downlink resource allocation type 1 (type 1), or other downlink resource allocation types (if applicable).
  • the allocated frequency domain resources are determined according to the DCI.
  • a Resource Indication Value (RIV) is determined according to the FDRA field in the DCI.
  • the RIV is equal to the value corresponding to some bits of the FDRA field, and for example, the RIV is equal to the The value corresponding to all bits of the FDRA field.
  • Each value of the RIV corresponds to a starting resource block (denoted as RB start ) and the length of a continuously allocated resource block (denoted as L RBs ).
  • the resource block may be a virtual resource block (Virtual Resource Block, VRB) or a physical resource block (Physical Resource Block, PRB).
  • the definition and/or value range of the RIV and/or the L RBs and/or the RB start may be related to frequency domain resource allocation scaling conditions.
  • the RIV may be defined as follows:
  • ⁇ L′ RBs can be equal to L RBs /K.
  • ⁇ RB' start can be equal to RB start /K.
  • ⁇ RB' start and/or L' RBs can satisfy one or more of the following relationships (any combination of "and” or “or” when applicable):
  • K can be satisfied
  • the maximum value of ⁇ 1, 2, 4, 8 ⁇ ; otherwise, K can be equal to 1.
  • K can also be defined in other ways.
  • ⁇ The value range of RB start can be any of the following:
  • L RBs can be any of the following:
  • ⁇ RB start and/or L RBs can satisfy one or more of the following relationships (any combination of "and” or “or” when applicable):
  • the RIV can be defined as follows:
  • the definition of is related to DCI format conditions. For example, when the DCI format conditions are met, When the DCI format conditions are not met, For another example, when the DCI format conditions are not met, When the DCI format conditions are met,
  • ⁇ RB start and/or L RBs can satisfy one or more of the following relationships (any combination of "and” or “or” when applicable):
  • RB start and/or L RBs are related to DCI format conditions. For example, any of the following is true:
  • ⁇ The value range of RB start can be any of the following:
  • RB start is related to DCI format conditions. For example, any of the following is true:
  • L RBs can be any of the following:
  • L RBs The value range of L RBs is related to DCI format conditions. For example, any of the following is true:
  • the frequency domain resource allocation scaling conditions may have one or more (any combination of "and” or “or” when applicable), each of which is All can be one or more of the following (any combination of "and” or “or” when applicable):
  • the size of the DCI format is derived from the first reference size. For example, the size of the DCI format is equal to the first reference size. For another example, when determining the size of the DCI format, the size of one or more fields in the DCI format is adjusted (for example, one or more bits are filled with 0 in the specified position of the field; The specified position of the field begins to cut one or more bits in the specified direction), or one or more bits 0 are filled before the first field or after the last field of the DCI format, so that the size of the DCI format Equal to the first reference size.
  • the first reference size can be defined in any of the following ways:
  • ⁇ CORESET 0 that is, the size of CORESET with ID 0.
  • the first reference size is equal to the size of CORESET 0; if CORESET 0 is not configured in the cell, the first reference size is equal to the size of the initial downlink BWP.
  • ⁇ A value of a parameter obtained from, for example, a base station (for example, obtained through DCI or MAC CE or RRC signaling), or when the parameter is not configured, the default value is used.
  • the size of the DCI format is applied to the reference BWP meeting the reference BWP condition.
  • the PDCCH is monitored according to the DCI format and the size of the DCI format derived from the first reference size, where the PDCCH is used to schedule the PDSCH on the reference BWP.
  • the reference BWP can be any of the following:
  • BWP indicated in the DCI format For example, the BWP indicated by the BWP indicator (Bandwidth part indicator) field.
  • the reference BWP condition can be any one of the following (where applicable):
  • a valid downlink BWP that satisfies the reference BWP condition refers to a valid downlink BWP, and there are no other restrictions.
  • the reference BWP is not the initial downstream BWP.
  • the reference BWP is not a valid downstream BWP.
  • the reference BWP is not the BWP indicated in the DCI format.
  • the reference BWP is not a predefined or pre-configured BWP.
  • the reference BWP is not a BWP configured with a parameter obtained from, for example, a base station (for example, obtained through DCI or MAC CE or RRC signaling), or when the parameter is not configured, the reference BWP is not the default BWP corresponding to the parameter.
  • the size of the reference BWP satisfies the second reference size.
  • the second reference size can be defined in any of the following ways:
  • the second reference size is equal to the size of CORESET 0; if CORESET 0 is not configured in the cell, the second reference size is equal to the size of the initial downlink BWP.
  • the size of the reference BWP does not meet the second reference size.
  • the reference BWP is "effective downlink BWP" and the reference BWP condition is "reference BWP is not an initial downlink BWP"
  • the reference BWP condition is "reference BWP is not an initial downlink BWP”
  • the frequency domain resource allocation scaling conditions may also be defined in other ways.
  • the DCI format condition may be one or more of the following (any combination of "and” or “or” when applicable):
  • the DCI format is the DCI format 1_0 monitored in the CSS.
  • the DCI format is the DCI format 1_0 monitored in the USS.
  • the DCI format is the DCI format 1_1 monitored in the USS.
  • the "monitoring” can also be replaced with "decoding”.
  • the DCI format conditions may also be defined in other ways.
  • RIV is appropriately defined, and the value ranges of RB start and/or L RBs and/or RB' start and L' RBs are set, and the frequency domain resource allocation scaling conditions and/or DCI are defined. Format conditions, etc., ensure that the frequency domain resources allocated in the DCI fall within the effective downlink BWP, and avoid inter-user interference caused by the allocated frequency domain resources falling outside the effective downlink BWP.
  • 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.
  • step S201 downlink control information (DCI) is received.
  • DCI downlink control information
  • the DCI can be used for scheduling PUSCH transmission (for example, using DCI format 0_0), and can also be used for other purposes.
  • the DCI may be a DCI monitored in a user-specific search space (UE-specific Search Space, USS).
  • UE-specific Search Space USS
  • the DCI may also be a DCI monitored in a common search space (Common Search Space, CSS).
  • a common search space Common Search Space, CSS
  • the CRC of the DCI can be scrambled with C-RNTI, MCS-C-RNTI, CS-RNTI, or other RNTI.
  • the DCI may include a frequency domain resource assignment (Frequency Domain Resource Assignment, FDRA) field.
  • FDRA Frequency Domain Resource Assignment
  • the frequency domain resource allocation method used by the DCI can be uplink resource allocation type 1 (type 1), or other uplink resource allocation types (if applicable).
  • the allocated frequency domain resources are determined according to the DCI.
  • a Resource Indication Value (RIV) is determined according to the FDRA field in the DCI.
  • the RIV is equal to the value corresponding to some bits of the FDRA field, and for example, the RIV is equal to the The value corresponding to all bits of the FDRA field.
  • Each value of the RIV corresponds to a starting resource block (denoted as RB start ) and the length of a continuously allocated resource block (denoted as L RBs ).
  • the resource block may be a virtual resource block (Virtual Resource Block, VRB) or a physical resource block (Physical Resource Block, PRB).
  • the definition and/or value range of the RIV and/or the L RBs and/or the RB start may be related to frequency domain resource allocation scaling conditions.
  • the RIV may be defined as follows:
  • ⁇ L′ RBs can be equal to L RBs /K.
  • ⁇ RB' start can be equal to RB start /K.
  • ⁇ RB' start and/or L' RBs can satisfy one or more of the following relationships (any combination of "and” or “or” when applicable):
  • K can be satisfied
  • the maximum value of ⁇ 1, 2, 4, 8 ⁇ ; otherwise, K can be equal to 1.
  • K can also be defined in other ways.
  • ⁇ The value range of RB start can be any of the following:
  • L RBs can be any of the following:
  • ⁇ RB start and/or L RBs can satisfy one or more of the following relationships (any combination of "and” or “or” when applicable):
  • the RIV can be defined as follows:
  • the definition of is related to DCI format conditions. For example, when the DCI format conditions are met, When the DCI format conditions are not met, For another example, when the DCI format conditions are not met, When the DCI format conditions are met,
  • ⁇ RB start and/or L RBs can satisfy one or more of the following relationships (any combination of "and” or “or” when applicable):
  • RB start and/or L RBs are related to DCI format conditions. For example, any of the following is true:
  • ⁇ The value range of RB start can be any of the following:
  • RB start is related to DCI format conditions. For example, any of the following is true:
  • L RBs can be any of the following:
  • L RBs The value range of L RBs is related to DCI format conditions. For example, any of the following is true:
  • the frequency domain resource allocation scaling conditions may have one or more (any combination of "and” or “or” when applicable), each of which is All can be one or more of the following (any combination of "and” or “or” when applicable):
  • the size of the DCI format is derived from the third reference size. For example, the size of the DCI format is equal to the third reference size.
  • the size of one or more fields in the DCI format is adjusted (for example, one or more bits are filled with 0 in the specified position of the field; The specified position of the field begins to cut one or more bits in the specified direction), or one or more bits 0 are filled before the first field or after the last field of the DCI format, so that the size of the DCI format Equal to the third reference size.
  • the third reference size can be defined in any of the following ways:
  • ⁇ A value of a parameter obtained from, for example, a base station (for example, obtained through DCI or MAC CE or RRC signaling), or when the parameter is not configured, the default value is used.
  • the size of the DCI format is applied to the reference BWP meeting the reference BWP condition.
  • the PDCCH is monitored according to the DCI format and the size of the DCI format derived from the third reference size, where the PDCCH is used to schedule the PUSCH on the reference BWP.
  • the reference BWP can be any of the following:
  • BWP indicated in the DCI format For example, the BWP indicated by the BWP indicator (Bandwidth part indicator) field.
  • the reference BWP condition can be any one of the following (where applicable):
  • a valid uplink BWP that meets the reference BWP condition refers to a valid uplink BWP, and there are no other restrictions.
  • the reference BWP is not the initial upstream BWP.
  • the reference BWP is not a valid upstream BWP.
  • the reference BWP is not the BWP indicated in the DCI format.
  • the reference BWP is not a predefined or pre-configured BWP.
  • the reference BWP is not a BWP configured with a parameter obtained from, for example, a base station (for example, obtained through DCI or MAC CE or RRC signaling), or when the parameter is not configured, the reference BWP is not the default BWP corresponding to the parameter.
  • the fourth reference size can be defined in any of the following ways:
  • the size of the reference BWP does not satisfy the fourth reference size.
  • the reference BWP is "effective uplink BWP" and the reference BWP condition is "reference BWP is not the initial uplink BWP"
  • the reference BWP condition is "reference BWP is not the initial uplink BWP”
  • the frequency domain resource allocation scaling conditions may also be defined in other ways.
  • the DCI format condition may be one or more of the following (any combination of "and” or “or” if applicable):
  • the DCI format is the DCI format 0_0 monitored in the CSS.
  • the DCI format is the DCI format 0_0 monitored in the USS.
  • the DCI format is the DCI format 0_1 monitored in the USS.
  • the "monitoring” can also be replaced with "decoding”.
  • the DCI format conditions may also be defined in other ways.
  • the second embodiment of the present invention appropriately defines RIV, and sets the value range of RB start and/or L RBs and/or RB' start and L' RBs , and defines the frequency domain resource allocation scaling conditions and/or DCI. Format conditions, etc., ensure that the frequency domain resources allocated in the DCI fall within the effective uplink BWP, and avoid inter-user interference caused by the allocated frequency domain resources falling outside the effective uplink BWP.
  • 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.
  • step S301 the configuration information of the parameter related to the mapping of the channel raster to the resource element (such as whether the parameter has been configured or the value configured by the parameter) is obtained. For example, obtaining the configuration information of the parameter from predefined information or pre-configuration information, or obtaining the configuration information of the parameter from the base station, or obtaining the configuration information of the parameter from other UEs, or when the parameter is not configured Use the default configuration information.
  • the parameters may include:
  • rf-subcarrierSpacing ⁇ Reference subcarrier spacing configuration (denoted as rf-subcarrierSpacing). For example, rf-subcarrierSpacing equal to 0, 1, 2, 3, and 4 indicates that the corresponding reference subcarrier spacing is 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz, respectively.
  • the configuration information of the parameter rf-subcarrierSpacing is obtained through DCI.
  • the configuration information of the parameter rf-subcarrierSpacing is obtained through MAC CE.
  • the configuration information of the parameter rf-subcarrierSpacing is obtained through RRC signaling (for example, one or more fields in MIB or SIB1).
  • the value of the parameter rf-subcarrierSpacing is a predefined or pre-configured value.
  • the parameter rf-subcarrierSpacing is equal to any value in ⁇ 0, 1, 2, 3, 4 ⁇ .
  • the configuration information of the parameter rf-subcarrierSpacing can be configured separately for frequency range 1 (frequency range 1, FR1) and frequency range 2 (frequency range 2, FR2).
  • the parameter rf-subcarrierSpacing can take any value in ⁇ 0, 1, 2 ⁇ (for example, 0); in FR2, the parameter rf-subcarrierSpacing can take the value in ⁇ 2, 3, 4 ⁇ Any value (for example, 2).
  • step S303 according to the reference subcarrier spacing configuration, and/or other configuration information, the mapping of the channel grid to the resource element, and/or the bandwidth and/or location of the RF channel is determined.
  • N RB may be the transmission bandwidth configuration (transmission bandwidth configuration) corresponding to the reference subcarrier spacing configuration.
  • the interval configuration rf-subcarrierSpacing (for example, the parameters subcarrierSpacing and rf-subcarrierSpacing are both equal to 0, that is, both correspond to a subcarrier interval of 15kHz).
  • the maximum transmission bandwidth configuration (maximum transmission bandwidth configuration) corresponding to N RB is equal to the minimum value greater than or equal to 20 in the set of maximum transmission bandwidth configuration values corresponding to the reference subcarrier spacing configuration, that is, 25 ,
  • the corresponding channel bandwidth is 5MHz.
  • ⁇ N RB may also be the maximum transmission bandwidth configuration corresponding to the reference subcarrier spacing configuration. For example, if the subcarrier spacing configuration configured by the parameter subcarrierSpacing in the SCS-SpecificCarrier IE and the reference subcarrier spacing configuration rf-subcarrierSpacing are both equal to 0 (that is, the corresponding subcarrier spacing is 15kHz), and the carrier configured by the parameter carrierBandwidth The bandwidth is 20 RBs, then N RB is equal to the minimum value greater than or equal to 20 in the set of maximum transmission bandwidth configuration values corresponding to the reference subcarrier spacing configuration, that is, 25 (corresponding to a channel bandwidth of 5 MHz).
  • the subcarrier spacing configuration configured by the parameter subcarrierSpacing in the SCS-SpecificCarrier IE and the reference subcarrier spacing configuration rf-subcarrierSpacing are both equal to 0 (that is, the corresponding subcarrier spacing is 15kHz), and the parameter carrierBandwidth is configured If the carrier bandwidth is 40 RBs, then N RB is equal to the minimum value greater than or equal to 40 in the set of maximum transmission bandwidth configuration values corresponding to the reference subcarrier spacing configuration, that is, 52 (corresponding to a channel bandwidth of 10 MHz).
  • ⁇ n CRB is the number of the common resource block (Common Resource Block, CRB) corresponding to the channel grid.
  • ⁇ k is the number of subcarriers in n CRB corresponding to the channel grid.
  • the channel grid corresponds to an RF reference frequency, and the RF reference frequency is used to identify the location of the RF channel.
  • the third embodiment of the present invention defines the reference subcarrier interval configuration, so that the UE can still uniquely determine the mapping of the channel grid to the resource element and/or the RF channel when the base station is configured with multiple subcarrier intervals.
  • the bandwidth and/or location ensure that the signal transmitted by the UE is consistent with the frequency configured and/or indicated by the base station.
  • Fig. 4 is a flowchart showing a method executed by a user equipment according to the fourth embodiment of the present invention.
  • the steps performed by the user equipment UE include: step S401, step S403, and step S405.
  • step S401 configuration information of parameters related to scrambling of the SL channel (such as whether the parameter has been configured, or the value configured by the parameter) is obtained. For example, obtaining the configuration information from predefined information or pre-configuration information, or obtaining the configuration information from a base station (for example, obtaining the configuration information through DCI or MAC CE or RRC signaling), or obtaining the configuration information from other UEs Configuration information, or when the parameter is not configured, use a default value, or a combination of the above methods.
  • the SL channel can be a channel related to SL synchronization, or a channel related to SL communication, or other channels transmitted on the SL carrier.
  • the channel may be PSBCH, PSCCH, PSSCH, PSFCH, or other SL channels.
  • ⁇ The parameters can include:
  • the ID may be a UE ID used to identify a source UE or a destination UE when SL synchronization, SL communication or other channels are transmitted on the SL carrier.
  • the high-level that is, higher than the physical layer, such as the application layer, the TCP/IP layer, the SDAP layer, the RRC layer, the PDCP layer, the RLC layer, and the MAC layer
  • the physical layer UE ID (optionally, also referred to as layer 1UE ID, layer 1UE ID).
  • the UE ID can be used to identify a UE or a group of UEs (including one or more UEs); when the UE ID is used to identify a group of UEs, it can also be used to identify a group of UEs.
  • the UE ID is called group ID (group ID) or UE group ID (UE group ID), correspondingly, the source UE ID may be called source group ID or source UE group ID, and the target UE ID may be called target Group ID or target UE group ID.
  • the UE ID or the group ID when referring to the UE ID or the group ID, it can refer to a part of the UE ID or the group ID (such as 8 least significant bits, or 8 most significant bits, or 16 The integer corresponding to the least significant bit (or 16 most significant bits) may also refer to the integer corresponding to all the bits of the UE ID or the group ID.
  • the ID can be a predefined or pre-configured constant, or a value configured through DCI or MAC CE or RRC signaling. For example, 0, 65535, or 4294967295.
  • the ID may be an SL synchronization ID, such as an ID carried in SL PSS and/or SL SSS.
  • the value range set of the SL synchronization ID can be ⁇ 0,1,...,83 ⁇ , it can also be ⁇ 0,1,...,167 ⁇ , or it can be ⁇ 0,1,...
  • ,251 ⁇ it can also be ⁇ 0,1,...,335 ⁇ , it can also be ⁇ 0,1,...,419 ⁇ , it can also be ⁇ 0,1,...,503 ⁇ , also It can be ⁇ 0,1,...,587 ⁇ , it can be ⁇ 0,1,...,671 ⁇ , it can be ⁇ 0,1,...,755 ⁇ , it can also be ⁇ 0, 1,...,839 ⁇ , it can also be ⁇ 0,1,...,923 ⁇ , it can also be ⁇ 0,1,...,1007 ⁇ , it can also be ⁇ 0, 1,... , 1091 ⁇ , can also be other integer sets.
  • the ID may be a SCI ID.
  • the SCI ID may be used to identify the SCI format, for example, SCI format 0 uses SCI ID0, SCI format 1 uses SCI ID1, and SCI ID0 is not equal to SCI ID1.
  • the ID can be configured for one or more of unicast, groupcast, and broadcast.
  • the ID can be configured for one or more of PSBCH, PSCCH, PSSCH, and PSFCH.
  • the ID may be for different resource allocation modes used by the SL channel (for example, mode 1, that is, the base station schedules SL resources for the UE's SL transmission; another example is mode 2, that is, the UE determines that it is used for the UE
  • mode 1 that is, the base station schedules SL resources for the UE's SL transmission
  • mode 2 that is, the UE determines that it is used for the UE
  • the SL resources of the SL transmission are configured separately.
  • the ID may be equal to C 1 ⁇ ID 0 +C 2 ⁇ sl 0 +C 3 ⁇ sym 0 +C 4 .
  • C 1 , C 2 , C 3 and C 4 are constants
  • ID 0 is the source UE ID, target UE ID, source group ID, target group ID, SL synchronization ID, SCI ID, predefined or pre-configured constants
  • sl 0 is the time slot in which the transmission of the SL channel is located (or when the transmission of the SL channel occupies more than one time slot, the SL channel
  • the first time slot where the transmission is located) is the number within the subframe or frame
  • sym 0 is the number within the time slot or subframe or the frame of the first symbol where the SL channel is transmitted.
  • one or more of C 1 , C 2 , C 3 and C 4 may be equal to zero.
  • the ID may be the ID of the target UE in the unicast communication (for example, the ID of the high-level UE, or the ID of the physical layer UE).
  • the ID may be the target group ID in the multicast communication (for example, the high-level UE ID, or the physical-layer UE ID).
  • the ID may be a special (such as predefined or pre-configured, or configured through DCI or MAC CE or RRC signaling) UE ID or group ID (for example, high-level UE ID is another example of physical layer UE ID) or SL synchronization ID.
  • the ID may be SCI ID.
  • step S403 the scrambling sequence of the SL channel is determined according to the configuration information of the parameters related to the scrambling of the SL channel and/or other configuration information.
  • the scrambling sequence may be a pseudo-random sequence (pseudo-random sequence).
  • the pseudo-random sequence c(n) can be defined as follows:
  • x 1 (n+31) (x 1 (n+3)+x 1 (n))mod 2
  • x 2 (n+31) (x 2 (n+3)+x 2 (n+2)+x 2 (n+1)+x 2 (n))mod 2
  • ⁇ x 2 (n) is initialized to Among them, c init can be A function of, for example Another example Where C 5 and C 6 are constants.
  • the scrambling sequence may also be part or all of the bits corresponding to the ID. For example, if Is a 32-bit integer, the scrambling sequence can be Some or all of the bits in Yes The most significant bit of Yes The second most significant bit of , whil, Yes The least significant bit.
  • step S405 the information transmitted on the SL channel is scrambled.
  • the information may be part or all of the bits transmitted on the SL channel after channel coding.
  • the "post-channel coding" may refer to the last step of channel coding, such as after rate matching, or after code block concatenation, or data and control multiplexing (data and control multiplexing). )Rear. For example, if the bit block corresponding to the codeword q is After scrambling among them Is the number of bits transmitted by the codeword q on the SL channel, the scrambling process may be as follows:
  • the information can also be one or more CRCs generated in the CRC attachment process, such as transport block CRC, or one or more code block CRCs, or SCI CRC of the load calculation.
  • CRCs generated in the CRC attachment process such as transport block CRC, or one or more code block CRCs, or SCI CRC of the load calculation.
  • the SCI load bit sequence is a 0 , a 1 ,..., a A-1
  • the fourth embodiment of the present invention by using a special scrambling ID when initializing the scrambling sequence of the SL channel, the conflict of the scrambling sequence between the SL channels sent by different UEs is at least partially avoided, thereby greatly The possible mutual interference between different SL channels is reduced.
  • using a longer ID to scramble the SL channel also greatly reduces or even completely avoids the inability to correctly identify the source and/or destination UE at the physical layer due to potential conflicts of short IDs (such as physical layer IDs). ID and other issues.
  • Fig. 5 is a flowchart showing a method executed by a user equipment according to the fifth embodiment of the present invention.
  • the steps performed by the user equipment UE include: step S501 and step S503.
  • step S501 configuration information of one or more parameters related to the SCI (Sidelink Control Information) format (such as whether the parameter has been configured or the value configured by the parameter) is obtained. For example, obtaining the configuration information from predefined information or pre-configuration information, or obtaining the configuration information from a base station (for example, obtaining the configuration information through DCI or MAC CE or RRC signaling), or obtaining the configuration information from other UEs Configuration information, or when the parameter is not configured, use a default value, or a combination of the above methods.
  • SCI Servicelink Control Information
  • the parameter may indicate information related to one or more SCI formats; for each SCI format, the parameter may include one or more of the following:
  • the SCI ID defined in the fourth embodiment.
  • it is used to identify the SL transmission/communication type (for example, unicast, multicast, or broadcast) corresponding to the SCI.
  • the SCI format identifier defined in other ways.
  • the size of the SCI may be bits, and the value range may be any subset of ⁇ 8, 9, ..., 200 ⁇ .
  • step S503 according to the configuration information of the parameters related to the SCI format and/or other configuration information, the PSCCH carrying the SCI is sent or received.
  • the fifth embodiment of the present invention configures some general parameters related to the SCI format, such as the size of the SCI, so that after the standard protocol related to the SCI is enhanced (for example, new fields are added for the SCI format), the UEs manufactured before the enhancement of the standard protocol can still decode the enhanced SCI format and correctly interpret at least some of the fields (for example, fields related to resource reservation), thereby greatly improving the compatibility of the SCI design and/or the resource reservation mechanism.
  • the standard protocol related to the SCI for example, new fields are added for the SCI format
  • the UEs manufactured before the enhancement of the standard protocol can still decode the enhanced SCI format and correctly interpret at least some of the fields (for example, fields related to resource reservation), thereby greatly improving the compatibility of the SCI design and/or the resource reservation mechanism.
  • Fig. 6 is a flowchart showing a method executed by a user equipment according to the sixth embodiment of the present invention.
  • the steps performed by the user equipment UE include: step S601 and step S603.
  • step S601 configuration information of one or more parameters related to the UE ID (such as whether the parameter has been configured, or the configured value of the parameter) is obtained. For example, obtaining the configuration information from predefined information or pre-configuration information, or obtaining the configuration information from a base station (for example, obtaining the configuration information through DCI or MAC CE or RRC signaling), or obtaining the configuration information from other UEs Configuration information, or when the parameter is not configured, use a default value, or a combination of the above methods.
  • the UE ID can be used to identify a source UE or a destination UE during SL synchronization, SL communication, or transmission of other signals or channels on the SL carrier.
  • the purpose of the SL synchronization, SL communication, or transmission of other signals or channels on the SL carrier is to carry V2X-related services. Accordingly, the UE may be referred to as a V2X UE.
  • the UE ID can be used to identify a UE or a group of UEs (including one or more UEs); when the UE ID is used to identify a group of UEs, it can also be used
  • the UE ID is called a group ID (group ID) or a UE group ID (UE group ID).
  • group ID group ID
  • UE group ID UE group ID
  • the source UE ID may be called a source group ID or a source UE group ID
  • the target UE ID may be called Target group ID or target UE group ID.
  • the UE ID can be a higher layer (that is, higher than the physical layer, for example, the application layer, for example, the TCP/IP layer, for example, the SDAP layer, for example, the RRC layer, for example, the PDCP layer, for example, the RLC layer,
  • the MAC layer UE ID which can also be the physical layer UE ID.
  • the physical layer UE ID may also be referred to as layer 1 UE ID (layer 1UE ID).
  • the one or more parameters can respectively indicate the value set of the UE ID corresponding to each type of SL transmission/communication (where each set contains one or more integers), for example, by One or more of:
  • the parameter unicast-IDs is used to configure the value set of UE ID used in unicast communication, for example, any subset of ⁇ 0, 1, ..., 255 ⁇ . Another example is any subset of ⁇ 0, 1, ..., 511 ⁇ . Another example is any subset of ⁇ 0, 1, ..., 1023 ⁇ . Another example is any subset of ⁇ 0, 1, ..., 2047 ⁇ . Another example is any subset of ⁇ 0, 1, ..., 4095 ⁇ .
  • the parameter groupcast-IDs is used to configure the value set of the UE ID used in multicast communication. For example, any subset of ⁇ 0, 1,..., 255 ⁇ . Another example is any subset of ⁇ 0, 1, ..., 511 ⁇ . Another example is any subset of ⁇ 0, 1, ..., 1023 ⁇ . Another example is any subset of ⁇ 0, 1, ..., 2047 ⁇ . Another example is any subset of ⁇ 0, 1, ..., 4095 ⁇ .
  • the parameter broadcast-IDs is used to configure the value set of the UE ID used in broadcast communication. For example, any subset of ⁇ 0, 1,..., 255 ⁇ . Another example is any subset of ⁇ 0, 1, ..., 511 ⁇ . Another example is any subset of ⁇ 0, 1, ..., 1023 ⁇ . Another example is any subset of ⁇ 0, 1, ..., 2047 ⁇ .
  • Another example is any subset of ⁇ 0, 1, ..., 4095 ⁇ .
  • the set of values of the UE ID configured by the parameters unicast-IDs, groupcast-IDs, and broadcast-IDs do not overlap with each other.
  • the value set of the UE ID used in broadcast communication can be derived.
  • the value sets of the UE ID used in unicast, multicast and broadcast communications are A (configured by the parameter unicast-IDs), B (configured by the parameter groupcast-IDs), and C respectively.
  • A, B, and C do not overlap each other, and the union of sets A, B, and C is ⁇ 0, 1, ..., 255 ⁇ , then set C is equal to ⁇ 0, 1, ..., 255 ⁇ -AB.
  • the value set of the UE ID used in multicast communication can be derived according to the configuration of the parameters unicast-IDs and broadcast-IDs.
  • the value sets of the UE ID used in unicast, multicast, and broadcast communications are A (configured by the parameter unicast-IDs), B and C (configured by the parameter broadcast-IDs), if the set A, B, and C do not overlap each other, and the union of sets A, B, and C is ⁇ 0, 1, ..., 255 ⁇ , then set B is equal to ⁇ 0, 1, ..., 255 ⁇ -AC.
  • the value set of the UE ID used in unicast communication can be derived according to the configuration of the parameters broadcast-IDs and groupcast-IDs.
  • the set of values of UE ID used in unicast, multicast, and broadcast communications are A, B (configured by the parameter groupcast-IDs) and C (configured by the parameter broadcast-IDs), if the set A, B, and C do not overlap each other, and the union of sets A, B, and C is ⁇ 0, 1, ..., 255 ⁇ , then set A is equal to ⁇ 0, 1, ..., 255 ⁇ -CB.
  • step S603 the PSCCH is received according to the configuration information of one or more parameters related to the UE ID and/or other configuration information.
  • the target UE ID in the SCI carried in the PSCCH is in the set configured by the parameter unicast-IDs, it can be considered that the PSCCH and the scheduled PSSCH are used for unicast communication.
  • the target UE ID in the SCI carried in the PSCCH is in the set configured by the parameter groupcast-IDs, it can be considered that the PSCCH and the scheduled PSSCH are used for multicast communication.
  • the target UE ID in the SCI carried in the PSCCH is in the set configured by the parameter broadcast-IDs, it can be considered that the PSCCH and the scheduled PSSCH are used for broadcast communication.
  • the target UE ID in the SCI carried in the PSCCH is equal to the source UE ID, it can be considered that the PSCCH and the scheduled PSSCH are used for multicast communication.
  • the sixth embodiment of the present invention configures the value set of the UE ID corresponding to each type of SL transmission/communication (for example, unicast communication and/or multicast communication and/or broadcast communication), so that the UE can be based on the SCI
  • the UE ID (for example, target UE ID) field in the field determines the transmission/communication type to which a given SL transmission (for example, PSCCH transmission, and/or its scheduled PSSCH transmission) belongs. For example, when the UE only needs to monitor one of the transmission/communication types (for example, broadcast communication), the received PSCCH/PSSCH that does not belong to the SL transmission/communication type can be filtered out efficiently.
  • FIG. 7 is used to describe 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. 7 is a block diagram showing a user equipment UE related to the present invention.
  • the user equipment UE70 includes a processor 701 and a memory 702.
  • the processor 701 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 702 may include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memories.
  • the memory 702 stores program instructions. When the instruction is executed by the processor 701, 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 larger transmission power and wider 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

本发明提出了一种由用户设备执行的方法，包括：接收用于调度物理下行共享信道PDSCH的传输的下行控制信息DCI；以及根据接收到的所述DCI中的频域资源分配FDRA字段，确定资源指示值RIV，并根据所述RIV确定所分配的起始资源块RB start以及连续分配的资源块的长度L RBs，其中，若不满足频域资源分配缩放条件，则根据所述RIV直接确定RB start以及L RBs，若满足频域资源分配缩放条件，则根据所述RIV先确定将RB start除以缩放因子K后得到的起始资源块RB' start以及将L RBs除以所述缩放因子K后得到的连续分配的资源块的长度L' RBs，然后再根据RB' start和L' RBs确定RB start以及L RBs，所述缩放因子K根据NBWP active与NBWP initial的比值来确定，NBWP initial表示初始下行带宽片段BWP的大小，NBWP active表示有效下行BWP的大小。

Description

由用户设备执行的方法以及用户设备 技术领域
本发明涉及无线通信技术领域，具体涉及由用户设备执行的方法以及相应的用户设备。
背景技术
2016年3月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#71次全会上，一个关于5G技术标准的新的研究项目(参见非专利文献1)获得批准。该研究项目的目的是开发一个新的无线(New Radio：NR)接入技术以满足5G的所有应用场景、需求和部署环境。NR主要有三个应用场景：增强的移动宽带通信(Enhanced Mobile Broadband：eMBB)、大规模机器类通信(massive Machine Type Communication：mMTC)和超可靠低延迟通信(Ultra-Reliable and Low Latency Communications：URLLC)。2017年6月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#75次全会上，相应的5G NR的工作项目(参见非专利文献2)获得批准。
5G通过DCI(Downlink Control Information，下行控制信息)调度PDSCH(Physical Downlink Shared Channel，物理下行共享信道)上的下行传输以及PUSCH(Physical Uplink Shared Channel，物理上行共享信道)上的上行传输。
5G支持多种DCI格式，如表1所示。每种DCI格式在进行信道编码后，其CRC可以用一个RNTI(Radio-Network Temporary Identifier，无线网络临时标识符)加扰，以指示一个特定的用途和/或一个或多个目的UE。例如，用于指示寻呼(paging)的DCI格式的CRC可以用P-RNTI加扰。
表1 5G支持的DCI格式
Figure PCTCN2020074607-appb-000001
5G的DCI承载在PDCCH(Physical Downlink Control Channel，物理下行控制信道)上。一个PDCCH由一个或者多个CCE(control-channel element，控制信道元素)组成，而一个CCE又由多个(例如，6个)REG(resource-element group，资源元素组)组成，而REG则在CORESET(control-resource set，控制资源集)内定义。一个CORESET在频域包含多个资源块(每个资源块由频域上12个连续的子载波组成)，在时域上包含一个或者多个(例如，1个，或者2个，或者3个)OFDM符号。
UE在一个或者多个搜索空间集合(search space set)上监听基站的PDCCH传输，其中，每个搜索空间集合可以对应一组PDCCH候选(PDCCH candidate)。UE通过在所要监听的PDCCH候选的时间和频率位置进行盲检(blind detection)以确定是否存在发给自己的PDCCH。
搜索空间集合可以分为CSS(Common Search Space，公共搜索空间)集合和USS(UE-specific search space，UE特定搜索空间)集合，例如：
●类型0-PDCCH CSS集合。例如通过MIB中的pdcch-ConfigSIB1参数进行配置，或者通过PDCCH-ConfigCommon IE中的searchSpaceSIB1参数进行配置，或者通过PDCCH-ConfigCommon IE中的searchSpaceZero参数进行配置。
相应的DCI格式的CRC可以用SI-RNTI加扰。
●类型0A-PDCCH CSS集合。例如通过PDCCH-ConfigCommon IE 中的searchSpaceOtherSystemInformation参数进行配置。相应的DCI格式的CRC可以用SI-RNTI加扰。
●类型1-PDCCH CSS集合。例如通过PDCCH-ConfigCommon IE中的ra-SearchSpace参数进行配置。相应的DCI格式的CRC可以用RA-RNTI或者TC-RNTI加扰。
●类型2-PDCCH CSS集合。例如通过PDCCH-ConfigCommon IE中的pagingSearchSpace参数进行配置。相应的DCI格式的CRC可以用P-RNTI加扰。
●类型3-PDCCH CSS集合。例如通过PDCCH-Config IE中的searchSpacesToAddModList和searchSpacesToReleaseList参数进行配置，其结果是一个或者多个通过SearchSpace IE配置的类型3-PDCCH CSS，其中每一个的searchSpaceType参数都配置为common。相应的DCI格式的CRC可以用INT-RNTI，或者SFI-RNTI，或者TPC-PUSCH-RNTI，或者TPC-PUCCH-RNTI，或者TPC-SRS-RNTI，或者C-RNTI，或者MCS-C-RNTI，或者CS-RNTI加扰。
●USS集合。例如通过PDCCH-Config IE中的searchSpacesToAddModList和searchSpacesToReleaseList参数进行配置，其结果是一个或者多个通过SearchSpace IE配置的USS，其中每一个的searchSpaceType参数都配置为ue-Specific。相应的DCI格式的CRC可以用C-RNTI，或者MCS-C-RNTI，或者SP-CSI-RNTI，或者CS-RNTI加扰。
UE在盲检PDCCH候选时需要假定一个DCI大小(DCI size)。由于处理能力的限制，UE在每个时隙只能监听一定数量的DCI大小。表2总结了根据DCI大小进行分类后的搜索空间集合的类型及其对应的DCI格式以及用于加扰DCI CRC的RNTI。其中，
●同一个“DCI大小类别”的所有行(例如对应1_0_css的所有搜索空间集合类型、DCI格式以及RNTI的组合)对应同样的DCI大小。
●“DCI大小”一列只是列出了可能的DCI大小的例子。对有些 DCI格式来说，实际的DCI大小取决于***配置信息和/或UE特定的配置信息。
●一个给定的USS集合所关联的DCI格式只能是0_0和1_0，或者0_1和1_1。
●UE实际监听的搜索空间集合类型、DCI格式以及RNTI(对于某些DCI格式)取决于***配置信息和/或UE特定的配置信息。●FDRA(Frequency Domain Resource Assignment，频域资源分配)是部分DCI格式中定义的一个字段，其大小取决于与频域资源分配有关的配置信息。例如，在DCI格式1_0和1_1中，FDRA的大小和
Figure PCTCN2020074607-appb-000002
有关(例如，FDRA的大小可以是
Figure PCTCN2020074607-appb-000003
比特)；在DCI格式0_0和0_1中，FDRA的大小和
Figure PCTCN2020074607-appb-000004
有关。其中，
Figure PCTCN2020074607-appb-000005
和
Figure PCTCN2020074607-appb-000006
的取值取决于DCI格式及其所对应的搜索空间集合的类型，并且可能会为满足DCI大小的限制而做调整。
●网络给UE配置的搜索空间集合、DCI格式以及RNTI必须满足下面中所有的条件：
◆小区中给UE配置的不同DCI大小的个数不能超过4个。
◆小区中给UE配置的用于C-RNTI的不同DCI大小的个数不能超过3个。
◆0_0_uss的大小不能等于0_1_uss的大小。
◆1_0_uss的大小不能等于1_1_uss的大小。
表2 搜索空间集合类型、DCI格式和大小以及RNTI的对应关系
Figure PCTCN2020074607-appb-000007
为满足DCI大小的限制，现有3GPP关于5G的标准规范中定义了一个DCI大小对齐(DCI size alignment)流程如下：
步骤0(确定0_0_css和1_0_css，并将0_0_css的大小向1_0_css的大小对齐)：
●确定0_0_css。其中，
◆DCI格式0_0中频域资源分配字段的大小与
Figure PCTCN2020074607-appb-000008
有关(例 如，所述频域资源分配字段的大小是
Figure PCTCN2020074607-appb-000009
比特)，
Figure PCTCN2020074607-appb-000010
等于初始上行BWP(例如通过参数initialUplinkBWP进行配置)的大小。
◆所述0_0_css的大小不包括填充比特。
●确定1_0_css。其中，
◆DCI格式1_0中频域资源分配字段的大小与
Figure PCTCN2020074607-appb-000011
有关(例如，所述频域资源分配字段的大小是
Figure PCTCN2020074607-appb-000012
比特)。若小区中已配置CORESET 0，则
Figure PCTCN2020074607-appb-000013
等于CORESET 0的大小；若小区中未配置CORESET 0，则
Figure PCTCN2020074607-appb-000014
等于初始下行BWP(例如通过参数initialDownlinkBWP进行配置)的大小。
●若UE配置为在CSS中监听DCI格式0_0，且所述0_0_css在填充前的信息比特的数量小于用于调度同一个服务小区的1_0_css的负荷大小，则对所述0_0_css执行零填充直至所述0_0_css的负荷大小等于所述1_0_css的负荷大小。
●若UE配置为在CSS中监听DCI格式0_0，且所述0_0_css在截断前的信息比特的数量大于用于调度同一个服务小区的1_0_css的负荷大小，则通过截断所述0_0_css中频域资源分配字段的开始的若干个最高有效位以减小所述频域资源分配字段的位宽，以使得0_0_css的大小等于1_0_css的大小。
步骤1(确定0_0_uss和1_0_uss，并将两者中小的向大的对齐)：
●确定0_0_uss。其中，
◆DCI格式0_0中频域资源分配字段的大小与
Figure PCTCN2020074607-appb-000015
有关(例如，所述频域资源分配字段的大小是
Figure PCTCN2020074607-appb-000016
比特)，
Figure PCTCN2020074607-appb-000017
等于有效上行BWP的大小。
◆所述0_0_uss的大小不包括填充比特(padding bits)。
●确定1_0_uss。其中，
◆DCI格式1_0中频域资源分配字段的大小与
Figure PCTCN2020074607-appb-000018
有关(例如，所述频域资源分配字段的大小是
Figure PCTCN2020074607-appb-000019
比特)。
Figure PCTCN2020074607-appb-000020
等于有效下行BWP的大小。
●若UE配置为在USS中监听DCI格式0_0，且所述0_0_uss在填充前的信息比特的数量小于用于调度同一个服务小区的1_0_uss的负荷大小，则对所述0_0_uss执行零填充直至所述0_0_uss的负荷大小等于所述1_0_uss的负荷大小。
●若UE配置为在USS中监听DCI格式1_0，且所述1_0_uss在填充前的信息比特的数量小于用于调度同一个服务小区的0_0_uss的负荷大小，则对所述1_0_uss执行零填充直至所述1_0_uss的负荷大小等于所述0_0_uss的负荷大小。
步骤2(若有必要，为0_1_uss和/或1_1_uss填充0以使得这两者中任何一个的大小都不等于0_0_uss/1_0_uss的大小)：
●若0_1_uss的大小等于0_0_uss/1_0_uss(经过步骤1后0_0_uss和1_0_uss的大小相等)，则在所述0_1_uss的最后一个字段的后面添加(append)1个零填充比特。
●若1_1_uss的大小等于0_0_uss/1_0_uss，则在所述1_1_uss的最后一个字段的后面添加1个零填充比特。
步骤3(若满足DCI大小的限制则流程结束)：
●若以下两个条件都满足，则DCI大小对齐流程结束：
◆小区中给UE配置的不同DCI大小的总数不超过4个。
◆小区中给UE配置的用于C-RNTI的不同DCI大小的总数不超过3个。
步骤4(否则撤销步骤2，重新确定1_0_uss和0_0_uss，并将1_0_uss和0_0_uss的大小对齐到1_0_css/0_0_css)：
●否则，
◆移除步骤2中引入的填充比特(如果有的话)。
◆确定1_0_uss。其中，
○DCI格式1_0中频域资源分配字段的大小与
Figure PCTCN2020074607-appb-000021
有关(例如，所述频域资源分配字段的大小是
Figure PCTCN2020074607-appb-000022
比特)。若小区中已配 置CORESET 0，则
Figure PCTCN2020074607-appb-000023
等于CORESET 0的大小；若小区中未配置CORESET 0，则
Figure PCTCN2020074607-appb-000024
等于初始下行BWP(例如通过参数initialDownlinkBWP配置)的大小。
◆确定0_0_uss。其中，
○DCI格式0_0中频域资源分配字段的大小与
Figure PCTCN2020074607-appb-000025
有关(例如，所述频域资源分配字段的大小是
Figure PCTCN2020074607-appb-000026
比特)，
Figure PCTCN2020074607-appb-000027
等于初始上行BWP(例如通过参数initialUplinkBWP配置)的大小。
○所述0_0_uss的大小不包括填充比特。
◆若所述0_0_uss在填充前的信息比特的数量小于用于调度同一个服务小区的1_0_uss的负荷大小，则对所述0_0_uss执行零填充直至所述0_0_uss的负荷大小等于所述1_0_uss的负荷大小。
◆若所述0_0_uss在截断前的信息比特的数量大于用于调度同一个服务小区的1_0_uss的负荷大小，则通过截断所述0_0_css中频域资源分配字段的开始的若干个最高有效位以减小所述频域资源分配字段的位宽，以使得0_0_uss的大小等于1_0_uss的大小。
可以看出，若上述DCI大小对齐流程执行到步骤4，则1_0_uss的大小是由1_0_css的大小决定的。相应地，1_0_uss中频域资源分配字段的大小也由初始下行BWP或者CORESET 0的大小决定。另一方面，通过1_0_uss分配的频域资源在有效下行BWP上，所以，若有效下行BWP的大小和初始下行BWP或CORESET 0的大小相差比较大，则1_0_uss能够分配的频域资源就可能非常受限。比如有效下行BWP的大小是100个PRB，初始下行BWP的大小是20个PRB(小区中未配置CORESET 0所以1_0_css的频域分配字段的大小由初始下行BWP决定)，则1_0_uss的频域资源分配字段只能分配有效下行BWP中的一部分PRB。所以，现有的3GPP关于5G的标准规范中引入了对频域资源分配的“缩放”(scaling)。
在现有的3GPP关于5G的标准规范中，当1_0_uss的大小派生于 1_0_css但是应用于不同于初始下行BWP的有效下行BWP时，则在做频域资源分配时需要做缩放。具体地，当1_0_uss的大小派生于1_0_css且应用于另一个有效下行BWP(例如不是初始下行BWP的有效下行BWP时，记其大小为
Figure PCTCN2020074607-appb-000028
)时，下行频域资源分配类型1中，FDRA字段包含一个RIV(Resource Indication Value，资源指示值)，每个RIV对应一个起始资源块
Figure PCTCN2020074607-appb-000029
以及一个连续分配的资源块的长度
Figure PCTCN2020074607-appb-000030
其中，若小区中CORESET 0已配置，则
Figure PCTCN2020074607-appb-000031
等于CORESET 0的大小；若小区中CORESET 0未配置，则
Figure PCTCN2020074607-appb-000032
等于初始下行BWP的大小。
所述资源指示值可以定义如下：
若
Figure PCTCN2020074607-appb-000033
则
Figure PCTCN2020074607-appb-000034
否则
Figure PCTCN2020074607-appb-000035
其中，L′ RBs＝L RBs/K，RB′ start＝RB start/K，L′ RBs不超过
Figure PCTCN2020074607-appb-000036
若
Figure PCTCN2020074607-appb-000037
则K是满足
Figure PCTCN2020074607-appb-000038
的{1，2，4，8}中的最大值；否则K＝1。
同样地，若上述DCI大小对齐流程执行到步骤4，上行的频域资源分配也需要做类似的缩放。
在现有的3GPP关于5G的标准规范中，当不需要对所分配的频域资源做缩放时，下行(上行)频域资源分配类型1中，FDRA字段包含一个RIV(Resource Indication Value，资源指示值)，每个RIV对应一个起始资源块RB start以及一个连续分配的资源块的长度L RBs。其中，所述资源指示值可以定义如下：
若
Figure PCTCN2020074607-appb-000039
则
Figure PCTCN2020074607-appb-000040
否则
Figure PCTCN2020074607-appb-000041
其中，L RBs≥1且不超过
Figure PCTCN2020074607-appb-000042
若所述FDRA字段所对应的DCI是1_0_css(0_0_css)时，
Figure PCTCN2020074607-appb-000043
否则，
Figure PCTCN2020074607-appb-000044
在现有的3GPP关于5G的标准规范中，与频域资源分配有关的机制至少存在如下问题：
●在下行频域资源分配类型1中，当需要对所分配的频域资源做缩放时，RB start和L RBs的取值范围总是以
Figure PCTCN2020074607-appb-000045
为参考定义的；若
Figure PCTCN2020074607-appb-000046
则RB start和L RBs的取值范围会落在有效下行BWP之外。当不需要对所分配的频域资源做缩放，且FDRA字段所对应的DCI是1_0_css但有效下行BWP不是初始下行BWP时，RB start和L RBs的取值范围也是以
Figure PCTCN2020074607-appb-000047
为参考定义的，所以也会存在类似的问题。
●在上行频域资源分配类型1中，当需要对所分配的频域资源做缩放时，RB start和L RBs的取值范围总是以
Figure PCTCN2020074607-appb-000048
为参考定义的；若
Figure PCTCN2020074607-appb-000049
则RB start和L RBs的取值范围会落在有效上行BWP之外。当不需要对所分配的频域资源做缩放，且FDRA字段所对应的DCI是0_0_css但有效上行BWP不是初始上行BWP时，RB start和L RBs的取值范围也是以
Figure PCTCN2020074607-appb-000050
为参考定义的，所以也会存在类似的问题。
另外，在现有的3GPP关于5G的标准规范中，在确定信道栅格到资源元素的映射，和/或RF信道的带宽和/或位置的过程中至少存在如下问题：
●用于标识RF信道的位置的RF参考频率所对应的子载波的子载波间隔存在歧义。
另外，随着3GPP识别出更多高级的V2X(Vehicle-to-everything)业务需求，基于5G的V2X的标准化开始提上日程。V2X通信是指车辆(vehicle)和任何可能影响车辆的实体之间的通信。典型的V2X通信包括V2I(Vehicle-to-Infrastructure，车辆到基础设施)、V2N(Vehicle-to-network，车辆到网络)、V2V(Vehicle-to-vehicle，车辆到车辆)、V2P(Vehicle-to-Pedestrian，车辆到行人)等。2018年6月， 在3GPP RAN#80次全会上，一个关于3GPP NR V2X的新的研究项目(参见非专利文献3，下面简称V2X(Rel-16)研究项目，或者V2X Phase 3研究项目)获得批准。在V2X(Rel-16)中，用于实现V2X通信的UE和UE间的接口称为PC5，在物理层也称为sidelink(在本公开中称为“直行”或者说“侧行”，或者简称为SL)链路，以区别于上行(uplink)链路和下行(downlink)链路。V2X(Rel-16)研究项目的目标之一就是研究新的基于NR的SL接口的设计。
V2X(Rel-16)中用于SL同步的信号和信道包括：
●SL PSS(Sidelink Primary Synchronization Signal，直行主同步信号)，又称为S-PSS，或者PSSS(Primary Sidelink Synchronization Signal，主直行同步信号)。
●SL SSS(Sidelink Secondary Synchronization Signal，直行辅同步信号)，又称为S-SSS，或者SSSS(Secondary Sidelink Synchronization Signal，辅直行同步信号)。
●PSBCH(Physical Sidelink Broadcast Channel，物理直行广播信道)。
SL PSS、SL SSS和PSBCH在时频资源格上组织成块状的形式，称为SL SSB(Sidelink SS/PBCH block，直行同步信号/物理广播信道块)，或者S-SSB。SL SSB的传输带宽在给UE所配置的SL BWP(Sidelink Bandwidth Part，直行带宽片段)内。
V2X(Rel-16)中的其他信道至少包括：
●PSSCH(Physical Sidelink Shared Channel，物理直行共享信道)。
●PSCCH(Physical Sidelink Control Channel，物理直行控制信道)。
●PSFCH(Physical Sidelink Feedback Channel，物理直行反馈信道)。
在V2X(Rel-16)中，SL链路的设计可能面临的问题至少包括：
●不同UE发送的SL信道之间的加扰序列可能存在冲突。
●不同UE所确定UE ID(特别是短ID，如物理层ID)可能存在冲突，导致无法在物理层正确识别源和/或目的UE ID。
●按照老版本的标准协议实现的UE可能无法识别按照新版本的标准协议实现的SCI格式，从而也无法读取新的SCI格式中的资源 预留字段，进而无法理解新的UE所预留的资源，导致资源预留冲突。
●UE可能无法在物理层识别所接收的PSCCH/PSSCH传输是用于单播，组播还是广播通信。
现有技术文献
非专利文献
非专利文献1：RP-160671，New SID Proposal：Study on New Radio Access Technology
非专利文献2：RP-170855，New WID on New Radio Access Technology
非专利文献3：RP-181429，New SID：Study on NR V2X
发明内容
为了解决上述问题中的至少一部分，本发明提供了一种由用户设备执行的方法以及用户设备，能够确保DCI中分配的频域资源落在有效下行BWP内，避免了由于所分配的频域资源落在有效下行BWP外而引起的用户间干扰。
根据本发明，提出了一种由用户设备执行的方法，包括：接收用于调度物理下行共享信道PDSCH的传输的下行控制信息DCI；以及根据接收到的所述DCI中的频域资源分配FDRA字段，确定资源指示值RIV，并根据所述RIV确定所分配的起始资源块RB start以及连续分配的资源块的长度L RBs，其中，若不满足频域资源分配缩放条件，则根据所述RIV直接确定RB start以及L RBs，若满足频域资源分配缩放条件，则根据所述RIV先确定将RB start除以缩放因子K后得到的起始资源块RB′ start以及将L RBs除以所述缩放因子K后得到的连续分配的资源块的长度L′ RBs，然后再根据RB′ start和L′ RBs确定RB start以及L RBs，所述缩放因子K根据
Figure PCTCN2020074607-appb-000051
与
Figure PCTCN2020074607-appb-000052
的比值来确定，
Figure PCTCN2020074607-appb-000053
表示初始下行带宽片段BWP的大小，
Figure PCTCN2020074607-appb-000054
表示有效下行BWP的大小。
优选地，若满足频域资源分配缩放条件，则
RB′ start和L′ RBs满足以下关系中的一项或多项：
◆L′ RBs≥1
◆
Figure PCTCN2020074607-appb-000055
◆
Figure PCTCN2020074607-appb-000056
◆
Figure PCTCN2020074607-appb-000057
◆
Figure PCTCN2020074607-appb-000058
◆
Figure PCTCN2020074607-appb-000059
◆
Figure PCTCN2020074607-appb-000060
◆
Figure PCTCN2020074607-appb-000061
◆
Figure PCTCN2020074607-appb-000062
◆
Figure PCTCN2020074607-appb-000063
◆
Figure PCTCN2020074607-appb-000064
◆
Figure PCTCN2020074607-appb-000065
◆
Figure PCTCN2020074607-appb-000066
◆
Figure PCTCN2020074607-appb-000067
◆
Figure PCTCN2020074607-appb-000068
◆
Figure PCTCN2020074607-appb-000069
◆
Figure PCTCN2020074607-appb-000070
◆
Figure PCTCN2020074607-appb-000071
◆
Figure PCTCN2020074607-appb-000072
◆
Figure PCTCN2020074607-appb-000073
◆
Figure PCTCN2020074607-appb-000074
◆若
Figure PCTCN2020074607-appb-000075
则
Figure PCTCN2020074607-appb-000076
否则
Figure PCTCN2020074607-appb-000077
◆若
Figure PCTCN2020074607-appb-000078
则
Figure PCTCN2020074607-appb-000079
否则
Figure PCTCN2020074607-appb-000080
◆若
Figure PCTCN2020074607-appb-000081
则
Figure PCTCN2020074607-appb-000082
否则
Figure PCTCN2020074607-appb-000083
◆若
Figure PCTCN2020074607-appb-000084
则
Figure PCTCN2020074607-appb-000085
否则
Figure PCTCN2020074607-appb-000086
◆若
Figure PCTCN2020074607-appb-000087
则
Figure PCTCN2020074607-appb-000088
否则
Figure PCTCN2020074607-appb-000089
◆若K＞1，则
Figure PCTCN2020074607-appb-000090
否则
Figure PCTCN2020074607-appb-000091
Figure PCTCN2020074607-appb-000092
◆若K＞1，则
Figure PCTCN2020074607-appb-000093
否则
Figure PCTCN2020074607-appb-000094
Figure PCTCN2020074607-appb-000095
◆若K＞1，则
Figure PCTCN2020074607-appb-000096
否则
Figure PCTCN2020074607-appb-000097
Figure PCTCN2020074607-appb-000098
◆若K＞1，则
Figure PCTCN2020074607-appb-000099
否则
Figure PCTCN2020074607-appb-000100
Figure PCTCN2020074607-appb-000101
◆若K＞1，则
Figure PCTCN2020074607-appb-000102
否则
Figure PCTCN2020074607-appb-000103
Figure PCTCN2020074607-appb-000104
优选地，所述频域资源分配缩放条件包括：所述DCI格式的大小派生自第一参考大小，
所述第一参考大小可以按下面中的任意一种方式定义：
◆在CSS中监听的DCI格式1_0的大小；
◆在CSS中监听的DCI格式0_0的大小；
◆在CSS中监听的DCI格式1_0和DCI格式0_0的共同大小；
◆ID为0的控制资源集CORESET即CORESET 0的大小；
◆初始下行BWP的大小；
◆有效下行BWP的大小；
◆若小区中CORESET 0已配置，则所述第一参考大小等于CORESET 0的大小；若小区中CORESET 0未配置，则所述第一参考大小等于初始下行BWP的大小；
◆预定义的常数；
◆预配置的值；
◆从基站获取的参数的值，或者当所述参数未配置时，使用缺省的值。
优选地，所述频域资源分配缩放条件包括：所述DCI格式的大小应用于满足参考BWP条件的参考BWP，
所述参考BWP可以是下面中的任意一个：
○有效下行BWP；
○初始下行BWP；
○所述DCI格式中指示的BWP；
○预定义或者预配置的BWP；
○从基站获取的参数配置的BWP，或者当所述参数未配置时，使用缺省的BWP。
此外，根据本发明，提出了一种由用户设备执行的方法，包括：接收用于调度物理上行共享信道PUSCH的传输的下行控制信息DCI；以及根据接收到的所述DCI中的频域资源分配FDRA字段，确定资源指示值RIV，并根据所述RIV确定所分配的起始资源块RB start以及连续分配的资源块的长度L RBs，其中，若不满足频域资源分配缩放条件，则根据所述RIV直接确定RB start以及L RBs，若满足频域资源分配缩放条件，则根据所述RIV先确定将RB start除以缩放因子K后得到的起始资源块RB′ start以及将L RBs除以所述缩放因子K后得到的连续分配的资源块的长度L′ RBs，然后再根据RB′ start和L′ RBs确定RB start以及L RBs，所述缩放因子K根据
Figure PCTCN2020074607-appb-000105
与
Figure PCTCN2020074607-appb-000106
的比值来确定，
Figure PCTCN2020074607-appb-000107
表示初始上行带宽片段BWP的大小，
Figure PCTCN2020074607-appb-000108
表示有效上行BWP的大小。
优选地，若满足频域资源分配缩放条件，则
RB′ start和L′ RBs满足以下关系中的一项或多项：
◆L′ RBs≥1
◆
Figure PCTCN2020074607-appb-000109
◆
Figure PCTCN2020074607-appb-000110
◆
Figure PCTCN2020074607-appb-000111
◆
Figure PCTCN2020074607-appb-000112
◆
Figure PCTCN2020074607-appb-000113
◆
Figure PCTCN2020074607-appb-000114
◆
Figure PCTCN2020074607-appb-000115
◆
Figure PCTCN2020074607-appb-000116
◆
Figure PCTCN2020074607-appb-000117
◆
Figure PCTCN2020074607-appb-000118
◆
Figure PCTCN2020074607-appb-000119
◆
Figure PCTCN2020074607-appb-000120
◆
Figure PCTCN2020074607-appb-000121
◆
Figure PCTCN2020074607-appb-000122
◆
Figure PCTCN2020074607-appb-000123
◆
Figure PCTCN2020074607-appb-000124
◆
Figure PCTCN2020074607-appb-000125
◆
Figure PCTCN2020074607-appb-000126
◆
Figure PCTCN2020074607-appb-000127
◆
Figure PCTCN2020074607-appb-000128
◆若
Figure PCTCN2020074607-appb-000129
则
Figure PCTCN2020074607-appb-000130
否则
Figure PCTCN2020074607-appb-000131
◆若
Figure PCTCN2020074607-appb-000132
则
Figure PCTCN2020074607-appb-000133
否则
Figure PCTCN2020074607-appb-000134
◆若
Figure PCTCN2020074607-appb-000135
则
Figure PCTCN2020074607-appb-000136
否则
Figure PCTCN2020074607-appb-000137
◆若
Figure PCTCN2020074607-appb-000138
则
Figure PCTCN2020074607-appb-000139
否则
Figure PCTCN2020074607-appb-000140
◆若
Figure PCTCN2020074607-appb-000141
则
Figure PCTCN2020074607-appb-000142
否则
Figure PCTCN2020074607-appb-000143
◆若K＞1，则
Figure PCTCN2020074607-appb-000144
否则
Figure PCTCN2020074607-appb-000145
Figure PCTCN2020074607-appb-000146
◆若K＞1，则
Figure PCTCN2020074607-appb-000147
否则
Figure PCTCN2020074607-appb-000148
Figure PCTCN2020074607-appb-000149
◆若K＞1，则
Figure PCTCN2020074607-appb-000150
否则
Figure PCTCN2020074607-appb-000151
Figure PCTCN2020074607-appb-000152
◆若K＞1，则
Figure PCTCN2020074607-appb-000153
否则
Figure PCTCN2020074607-appb-000154
Figure PCTCN2020074607-appb-000155
◆若K＞1，则
Figure PCTCN2020074607-appb-000156
否则
Figure PCTCN2020074607-appb-000157
Figure PCTCN2020074607-appb-000158
优选地，所述频域资源分配缩放条件包括：所述DCI格式的大小派生自第三参考大小，
所述第三参考大小可以按下面中的任意一种方式定义：
◆在CSS中监听的DCI格式1_0的大小；
◆在CSS中监听的DCI格式0_0的大小；
◆在CSS中监听的DCI格式1_0和DCI格式0_0的共同大小；
◆初始上行BWP的大小；
◆有效上行BWP的大小；
◆预定义的常数；
◆预配置的值；
◆从基站获取的参数的值，或者当所述参数未配置时，使用缺省的值。
优选地，所述频域资源分配缩放条件包括：所述DCI格式的大小应用于满足参考BWP条件的参考BWP，
所述参考BWP可以是下面中的任意一个：
○有效上行BWP；
○初始上行BWP；
○所述DCI格式中指示的BWP；
○预定义或者预配置的BWP；
○从基站获取的参数配置的BWP，或者当所述参数未配置时，使用缺省的BWP。
另外，根据本发明，还提出了一种用户设备，包括：处理器；以及存储器，存储有指令，其中，所述指令在由所述处理器运行时执行上述的方法。
发明效果
根据本发明，能够确保DCI中分配的频域资源落在有效下行BWP内，避免了由于所分配的频域资源落在有效下行BWP外而引起的用户间干扰。
附图说明
通过下文结合附图的详细描述，本发明的上述和其它特征将会变得更加明显，其中：
图1是示出了根据本发明的实施例一的由用户设备执行的方法的流程图。
图2是示出了根据本发明的实施例二的由用户设备执行的方法的流程图。
图3是示出了根据本发明的实施例三的由用户设备执行的方法的流程图。
图4是示出了根据本发明的实施例四的由用户设备执行的方法的流程图。
图5是示出了根据本发明的实施例五的由用户设备执行的方法的流程图。
图6是示出了根据本发明的实施例六的由用户设备执行的方法的流程图。
图7是示意性示出本发明所涉及的用户设备的框图。
具体实施方式
下面结合附图和具体实施方式对本发明进行详细阐述。应当注意，本发明不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本发明没有直接关联的公知技术的详细描述，以防止对本发明的理解造成混淆。
下文以5G移动通信***及其后续的演进版本作为示例应用环境，具体描述了根据本发明的多个实施方式。然而，需要指出的是，本发明不限于以下实施方式，而是可适用于更多其它的无线通信***，例如5G之后的通信***以及5G之前的4G移动通信***等。
下面描述本发明涉及的部分术语，如未特别说明，本发明涉及的术语采用此处定义。本发明给出的术语在LTE、LTE-Advanced、LTE-Advanced Pro、NR以及之后的通信***中可能采用不同的命名方式，但本发明中 采用统一的术语，在应用到具体的***中时，可以替换为相应***中采用的术语。
3GPP：3rd Generation Partnership Project，第三代合作伙伴计划
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，循环冗余校验
CSS：Common Search Space，公共搜索空间
DC：Dual Connectivity，双连接
DCI：Downlink Control Information，下行控制信息
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，增强的移动宽带通信
FDRA：Frequency Domain Resource Assignment，频域资源分配
FR1：Frequency Range 1，频率范围1
FR2：Frequency Range 1，频率范围2
IE：Information Element，信息元素
IP：Internet Protocol，网际协议
LCID：Logical Channel ID，逻辑信道标识符
LTE-A：Long Term Evolution-Advanced，长期演进技术升级版
MAC：Medium Access Control，介质访问控制
MAC CE：MAC Control Element，MAC控制元素
MCG：Master Cell Group，主小区组
MIB：Master Information Block，主信息块
mMTC：massive Machine Type Communication，大规模机器类通信
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，物理直行控制信道
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，准共置
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，无线资源控制
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 PSS：Sidelink Primary Synchronization Signal，直行主同步信号
SL SSB：Sidelink SS/PBCH block，直行同步信号/物理广播信道块
SL SSS：Sidelink Secondary Synchronization Signal，直行辅同步信号
SpCell：Special Cell，特殊小区
SRS：Sounding Reference Signal，探测参考信号
SSB：SS/PBCH block，同步信号/物理广播信道块
SSS：Secondary Synchronizaion Signal，辅同步信号
SSSS：Secondary Sidelink Synchronization Signal，辅直行同步信号
STAG：Secondary Timing Advance Group，辅定时提前组
SUL：Supplementary Uplink，补充上行
TA：Timing Advance，定时提前
TAG：Timing Advanced Group，定时提前组
TCP：Transmission Control Protocol，传输控制协议
TDD：Time Division Duplexing，时分双工
TPC：Transmit power control，传输功率控制
UE：User Equipment，用户设备
UL：Uplink，上行
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，车辆到任何实体
[实施例一]
下面结合图1来说明本发明的实施例一的由用户设备执行的方法。
图1是示出了根据本发明的实施例一的由用户设备执行的方法的流程图。
如图1所示，在本发明的实施例一中，用户设备UE执行的步骤包括：步骤S101和步骤S103。
具体地，在步骤S101，接收下行控制信息(DCI)。
其中，
●所述DCI可以用于调度PDSCH的传输(例如使用DCI格式1_0)，也可以用于其他目的。
●所述DCI可以是在用户特定搜索空间(UE-specific Search Space，USS)中监听的DCI。例如通过SearchSpace IE配置的搜索空间集合中的搜索空间，其中searchSpaceType参数配置为ue-Specific。
●所述DCI也可以是在公共搜索空间(Common Search Space，CSS)中监听的DCI。例如通过SearchSpace IE配置的搜索空间集合中的搜索空间，其中searchSpaceType参数配置为common；又如通过pdcch-ConfigSIB1参数配置的搜索空间；又如通过searchSpaceSIB1参数配置的搜索空间；又如通过searchSpaceZero参数配置的搜索空间；又如通过searchSpaceOtherSystemInformation参数配置的搜索空间；又如通过ra-SearchSpace参数配置的搜索空间；又如通过pagingSearchSpace参数配置的搜索空间。
●所述DCI的CRC可以用C-RNTI加扰，也可以用MCS-C-RNTI加扰，也可以用CS-RNTI加扰，也可以用其他RNTI加扰。
●所述DCI可以包含一个频域资源分配(Frequency Domain Resource Assignment，FDRA)字段。
●所述DCI使用的频域资源分配方式可以是下行资源分配类型1 (type 1)，也可以是其他下行资源分配类型(在适用的情况下)。
此外，在步骤S103，根据所述DCI，确定所分配的频域资源。例如，根据所述DCI中的FDRA字段确定一个资源指示值(Resource Indication Value，RIV)，例如，所述RIV等于所述FDRA字段的部分比特所对应的值，又如，所述RIV等于所述FDRA字段的全部比特所对应的值。所述RIV的每一个值对应一个起始资源块(记为RB start)以及一个连续分配的资源块的长度(记为L RBs)。其中，所述资源块可以是虚拟资源块(Virtual Resource Block，VRB)，也可以是物理资源块(Physical Resource Block，PRB)。所述RIV和/或所述L RBs和/或所述RB start的定义和/或取值范围可以与频域资源分配缩放条件有关。
例如，若满足频域资源分配缩放条件，则所述RIV可以定义如下：
若
Figure PCTCN2020074607-appb-000159
则
Figure PCTCN2020074607-appb-000160
否则
Figure PCTCN2020074607-appb-000161
其中，可选地，下面中的一项或多项成立：
●L′ RBs可以等于L RBs/K。
●RB′ start可以等于RB start/K。
●RB′ start和/或L′ RBs可以满足以下关系中的一项或多项(在适用的情况下按“与”或者“或”的方式任意组合)：
◆L′ RBs≥1
◆
Figure PCTCN2020074607-appb-000162
◆
Figure PCTCN2020074607-appb-000163
◆
Figure PCTCN2020074607-appb-000164
◆
Figure PCTCN2020074607-appb-000165
◆
Figure PCTCN2020074607-appb-000166
◆
Figure PCTCN2020074607-appb-000167
◆
Figure PCTCN2020074607-appb-000168
◆
Figure PCTCN2020074607-appb-000169
◆
Figure PCTCN2020074607-appb-000170
◆
Figure PCTCN2020074607-appb-000171
◆
Figure PCTCN2020074607-appb-000172
◆
Figure PCTCN2020074607-appb-000173
◆
Figure PCTCN2020074607-appb-000174
◆
Figure PCTCN2020074607-appb-000175
◆
Figure PCTCN2020074607-appb-000176
◆
Figure PCTCN2020074607-appb-000177
◆
Figure PCTCN2020074607-appb-000178
◆
Figure PCTCN2020074607-appb-000179
◆
Figure PCTCN2020074607-appb-000180
◆
Figure PCTCN2020074607-appb-000181
◆若
Figure PCTCN2020074607-appb-000182
则
Figure PCTCN2020074607-appb-000183
否则
Figure PCTCN2020074607-appb-000184
◆若
Figure PCTCN2020074607-appb-000185
则
Figure PCTCN2020074607-appb-000186
否则
Figure PCTCN2020074607-appb-000187
◆若
Figure PCTCN2020074607-appb-000188
则
Figure PCTCN2020074607-appb-000189
否则
Figure PCTCN2020074607-appb-000190
◆若
Figure PCTCN2020074607-appb-000191
则
Figure PCTCN2020074607-appb-000192
否则
Figure PCTCN2020074607-appb-000193
◆若
Figure PCTCN2020074607-appb-000194
则
Figure PCTCN2020074607-appb-000195
否则
Figure PCTCN2020074607-appb-000196
◆若K＞1，则
Figure PCTCN2020074607-appb-000197
否则
Figure PCTCN2020074607-appb-000198
Figure PCTCN2020074607-appb-000199
◆若K＞1，则
Figure PCTCN2020074607-appb-000200
否则
Figure PCTCN2020074607-appb-000201
Figure PCTCN2020074607-appb-000202
◆若K＞1，则
Figure PCTCN2020074607-appb-000203
否则
Figure PCTCN2020074607-appb-000204
Figure PCTCN2020074607-appb-000205
◆若K＞1，则
Figure PCTCN2020074607-appb-000206
否则
Figure PCTCN2020074607-appb-000207
Figure PCTCN2020074607-appb-000208
◆若K＞1，则
Figure PCTCN2020074607-appb-000209
否则
Figure PCTCN2020074607-appb-000210
Figure PCTCN2020074607-appb-000211
●若
Figure PCTCN2020074607-appb-000212
则K可以是满足
Figure PCTCN2020074607-appb-000213
的{1，2，4，8}中的最大值；否则K可以等于1。K也可以按其他方式定义。
●RB start的取值范围可以是下面中的任意一项：
◆
Figure PCTCN2020074607-appb-000214
◆
Figure PCTCN2020074607-appb-000215
◆
Figure PCTCN2020074607-appb-000216
◆
Figure PCTCN2020074607-appb-000217
◆若
Figure PCTCN2020074607-appb-000218
则
Figure PCTCN2020074607-appb-000219
Figure PCTCN2020074607-appb-000220
否则
Figure PCTCN2020074607-appb-000221
◆若
Figure PCTCN2020074607-appb-000222
则
Figure PCTCN2020074607-appb-000223
Figure PCTCN2020074607-appb-000224
否则
Figure PCTCN2020074607-appb-000225
◆若K＞1，则
Figure PCTCN2020074607-appb-000226
否则
Figure PCTCN2020074607-appb-000227
◆若K＞1，则
Figure PCTCN2020074607-appb-000228
否则
Figure PCTCN2020074607-appb-000229
●L RBs的取值范围可以是下面中的任意一项：
◆
Figure PCTCN2020074607-appb-000230
◆
Figure PCTCN2020074607-appb-000231
◆
Figure PCTCN2020074607-appb-000232
◆
Figure PCTCN2020074607-appb-000233
◆若
Figure PCTCN2020074607-appb-000234
则
Figure PCTCN2020074607-appb-000235
否则
Figure PCTCN2020074607-appb-000236
◆若
Figure PCTCN2020074607-appb-000237
则
Figure PCTCN2020074607-appb-000238
否则
Figure PCTCN2020074607-appb-000239
◆若K＞1，则
Figure PCTCN2020074607-appb-000240
否则
Figure PCTCN2020074607-appb-000241
◆若K＞1，则
Figure PCTCN2020074607-appb-000242
否则
Figure PCTCN2020074607-appb-000243
●RB start和/或L RBs可以满足以下关系中的一项或多项(在适用的情况下按“与”或者“或”的方式任意组合)：
◆L RBs≥1
◆
Figure PCTCN2020074607-appb-000244
◆
Figure PCTCN2020074607-appb-000245
◆
Figure PCTCN2020074607-appb-000246
◆
Figure PCTCN2020074607-appb-000247
◆若
Figure PCTCN2020074607-appb-000248
则
Figure PCTCN2020074607-appb-000249
否则
Figure PCTCN2020074607-appb-000250
◆若K＞1，则
Figure PCTCN2020074607-appb-000251
否则
Figure PCTCN2020074607-appb-000252
Figure PCTCN2020074607-appb-000253
又如，若不满足频域资源分配缩放条件，则所述RIV可以定义如下：
若
Figure PCTCN2020074607-appb-000254
则
Figure PCTCN2020074607-appb-000255
否则
Figure PCTCN2020074607-appb-000256
其中，可选地，下面中的一项或多项成立：
●
Figure PCTCN2020074607-appb-000257
可以按下面中的任意一项定义：
◆
Figure PCTCN2020074607-appb-000258
◆
Figure PCTCN2020074607-appb-000259
◆
Figure PCTCN2020074607-appb-000260
◆
Figure PCTCN2020074607-appb-000261
◆
Figure PCTCN2020074607-appb-000262
的定义与DCI格式条件有关。例如，当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000263
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000264
又如，当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000265
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000266
●RB start和/或L RBs可以满足以下关系中的一项或多项(在适用的情况下按“与”或者“或”的方式任意组合)：
◆L RBs≥1
◆
Figure PCTCN2020074607-appb-000267
◆
Figure PCTCN2020074607-appb-000268
◆
Figure PCTCN2020074607-appb-000269
◆
Figure PCTCN2020074607-appb-000270
◆
Figure PCTCN2020074607-appb-000271
◆
Figure PCTCN2020074607-appb-000272
◆
Figure PCTCN2020074607-appb-000273
◆
Figure PCTCN2020074607-appb-000274
◆
Figure PCTCN2020074607-appb-000275
◆RB start和/或L RBs满足的关系与DCI格式条件有关。例如，下面中的任意一项成立：
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000276
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000277
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000278
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000279
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000280
Figure PCTCN2020074607-appb-000281
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000282
Figure PCTCN2020074607-appb-000283
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000284
Figure PCTCN2020074607-appb-000285
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000286
Figure PCTCN2020074607-appb-000287
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000288
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000289
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000290
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000291
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000292
当DCI格式条 件满足时，
Figure PCTCN2020074607-appb-000293
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000294
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000295
●RB start的取值范围可以是下面中的任意一项：
◆
Figure PCTCN2020074607-appb-000296
◆
Figure PCTCN2020074607-appb-000297
◆
Figure PCTCN2020074607-appb-000298
◆
Figure PCTCN2020074607-appb-000299
◆
Figure PCTCN2020074607-appb-000300
◆
Figure PCTCN2020074607-appb-000301
◆
Figure PCTCN2020074607-appb-000302
◆
Figure PCTCN2020074607-appb-000303
◆
Figure PCTCN2020074607-appb-000304
◆RB start的取值范围与DCI格式条件有关。例如，下面中的任意一项成立：
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000305
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000306
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000307
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000308
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000309
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000310
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000311
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000312
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000313
当DCI 格式条件满足时，
Figure PCTCN2020074607-appb-000314
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000315
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000316
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000317
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000318
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000319
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000320
●L RBs的取值范围可以是下面中的任意一项：
◆
Figure PCTCN2020074607-appb-000321
◆
Figure PCTCN2020074607-appb-000322
◆
Figure PCTCN2020074607-appb-000323
◆
Figure PCTCN2020074607-appb-000324
◆
Figure PCTCN2020074607-appb-000325
◆
Figure PCTCN2020074607-appb-000326
◆
Figure PCTCN2020074607-appb-000327
◆
Figure PCTCN2020074607-appb-000328
◆
Figure PCTCN2020074607-appb-000329
◆L RBs的取值范围与DCI格式条件有关。例如，下面中的任意一项成立：
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000330
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000331
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000332
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000333
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000334
当DCI格式条件不 满足时，
Figure PCTCN2020074607-appb-000335
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000336
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000337
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000338
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000339
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000340
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000341
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000342
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000343
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000344
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000345
可选地，在本发明的实施例一中，所述频域资源分配缩放条件可以有一个或多个(在适用的情况下按“与”或者“或”的方式任意组合)，其中每一个都可以是下面中的一项或多项(在适用的情况下按“与”或者“或”的方式任意组合)：
●所述DCI格式的大小派生自第一参考大小。例如，所述DCI格式的大小等于所述第一参考大小。又如，在确定所述DCI格式的大小时，通过对所述DCI格式中的一个或者多个字段的大小进行调整(例如在所述字段的指定位置填充一个或多个比特0；又如从所述字段的指定位置开始按指定方向截断一个或多个比特)，或者在所述DCI格式的第一个字段之前或最后一个字段之后填充一个或多个比特0，使得所述DCI格式的大小等于所述第一参考大小。
其中，所述第一参考大小可以按下面中的任意一种方式定义：
◆在CSS中监听的DCI格式1_0的大小。
◆在CSS中监听的DCI格式0_0的大小。
◆在CSS中监听的DCI格式1_0和DCI格式0_0的共同大小。
◆CORESET 0(即ID为0的CORESET)的大小。
◆初始下行BWP的大小。
◆有效下行BWP的大小。
◆若小区中CORESET 0已配置，则所述第一参考大小等于CORESET 0的大小；若小区中CORESET 0未配置，则所述第一参考大小等于初始下行BWP的大小。
◆一个预定义的常数。
◆一个预配置的值。
◆一个从例如基站获取(例如通过DCI或者MAC CE或者RRC信令获取)的参数的值，或者当所述参数未配置时，使用缺省的值。
●所述DCI格式的大小应用于满足参考BWP条件的参考BWP。例如，根据所述DCI格式、以及派生自所述第一参考大小的所述DCI格式的大小来监听PDCCH，其中所述PDCCH用于调度在所述参考BWP上的PDSCH。
其中，
◆所述参考BWP可以是下面中的任意一个：
○有效下行BWP。
○初始下行BWP。
○所述DCI格式中指示的BWP。例如通过BWP指示器(Bandwidth part indicator)字段指示的BWP。
○预定义或者预配置的BWP。
○从例如基站获取(例如通过DCI或者MAC CE或者RRC信令获取)的参数配置的BWP，或者当所述参数未配置时，使用缺省的BWP。
◆所述参考BWP条件可以是下面中的任意一个(在适用的情况下)：
○无任何条件(即所述参考BWP条件总是可以满足)。 例如，此时，“满足参考BWP条件的有效下行BWP”指的是有效下行BWP，且无其他限制条件。
○参考BWP不是初始下行BWP。
○参考BWP不是有效下行BWP。
○参考BWP不是所述DCI格式中指示的BWP。
○参考BWP不是预定义或者预配置的BWP。
○参考BWP不是从例如基站获取(例如通过DCI或者MAC CE或者RRC信令获取)的参数配置的BWP，或者当所述参数未配置时，参考BWP不是对应所述参数的缺省的BWP。
○参考BWP的大小满足第二参考大小。其中，所述第二参考大小可以按下面中的任意一种方式定义：
◇在CSS中监听的DCI格式1_0的大小。
◇在CSS中监听的DCI格式0_0的大小。
◇在CSS中监听的DCI格式1_0和DCI格式0_0的共同大小。
◇CORESET 0(即ID为0的CORESET)的大小。
◇初始下行BWP的大小。
◇有效下行BWP的大小。
◇若小区中CORESET 0已配置，则所述第二参考大小等于CORESET 0的大小；若小区中CORESET 0未配置，则所述第二参考大小等于初始下行BWP的大小。
◇一个预定义的常数。
◇一个预配置的值。
◇一个从例如基站获取(例如通过DCI或者MACCE或者RRC信令获取)的参数的值，或者当所述参数未配置时，使用缺省的值。
○参考BWP的大小不满足所述第二参考大小。
例如，若所述参考BWP是“有效下行BWP”，所述参考BWP 条件是“参考BWP不是初始下行BWP”，则当所述DCI格式的大小应用于不是初始下行BWP的有效下行BWP时，条件“所述DCI格式的大小应用于满足参考BWP条件的参考BWP”成立。
可选地，在本发明的实施例一中，所述频域资源分配缩放条件也可以按其他方式定义。
可选地，在本发明的实施例一中，所述DCI格式条件可以是下面中的一个或多个(在适用的情况下按“与”或者“或”的方式任意组合)：
●所述DCI格式是在CSS中监听的DCI格式1_0。
●所述DCI格式是在USS中监听的DCI格式1_0。
●所述DCI格式是在USS中监听的DCI格式1_1。
其中，可选地，所述“监听”也可以替换为“解码”。
可选地，在本发明的实施例一中，所述DCI格式条件也可以按其他方式定义。
这样，本发明的实施例一通过恰当地定义RIV，以及设置RB start和/或L RBs和/或RB′ start和L′ RBs的取值范围，以及定义频域资源分配缩放条件和/或DCI格式条件等，确保了DCI中分配的频域资源落在有效下行BWP内，避免了由于所分配的频域资源落在有效下行BWP外而引起的用户间干扰。
[实施例二]
下面结合图2来说明本发明的实施例二的由用户设备执行的方法。
图2是示出了根据本发明的实施例二的由用户设备执行的方法的流程图。
如图2所示，在本发明的实施例二中，用户设备UE执行的步骤包括： 步骤S201和步骤S203。
具体地，在步骤S201，接收下行控制信息(DCI)。
其中，
●所述DCI可以用于调度PUSCH的传输(例如，使用DCI格式0_0)，也可以用于其他目的。
●所述DCI可以是在用户特定搜索空间(UE-specific Search Space，USS)中监听的DCI。例如通过SearchSpace IE配置的搜索空间集合中的搜索空间，其中searchSpaceType参数配置为ue-Specific。
●所述DCI也可以是在公共搜索空间(Common Search Space，CSS)中监听的DCI。例如通过SearchSpace IE配置的搜索空间集合中的搜索空间，其中searchSpaceType参数配置为common；又如通过ra-SearchSpace参数配置的搜索空间。
●所述DCI的CRC可以用C-RNTI加扰，也可以用MCS-C-RNTI加扰，也可以用CS-RNTI加扰，也可以用其他RNTI加扰。
●所述DCI可以包含一个频域资源分配(Frequency Domain Resource Assignment，FDRA)字段。
●所述DCI使用的频域资源分配方式可以是上行资源分配类型1(type 1)，也可以是其他上行资源分配类型(在适用的情况下)。
此外，在步骤S203，根据所述DCI，确定所分配的频域资源。例如，根据所述DCI中的FDRA字段确定一个资源指示值(Resource Indication Value，RIV)，例如，所述RIV等于所述FDRA字段的部分比特所对应的值，又如，所述RIV等于所述FDRA字段的全部比特所对应的值。所述RIV的每一个值对应一个起始资源块(记为RB start)以及一个连续分配的资源块的长度(记为L RBs)。其中，所述资源块可以是虚拟资源块(Virtual Resource Block，VRB)，也可以是物理资源块(Physical Resource Block，PRB)。所述RIV和/或所述L RBs和/或所述RB start的定义和/或取值范围可以与频域资源分配缩放条件有关。
例如，若满足频域资源分配缩放条件，则所述RIV可以定义如下：
若
Figure PCTCN2020074607-appb-000346
则
Figure PCTCN2020074607-appb-000347
否则
Figure PCTCN2020074607-appb-000348
其中，可选地，下面中的一项或多项成立：
●L′ RBs可以等于L RBs/K。
●RB′ start可以等于RB start/K。
●RB′ start和/或L′ RBs可以满足以下关系中的一项或多项(在适用的情况下按“与”或者“或”的方式任意组合)：
◆L′ RBs≥1
◆
Figure PCTCN2020074607-appb-000349
◆
Figure PCTCN2020074607-appb-000350
◆
Figure PCTCN2020074607-appb-000351
◆
Figure PCTCN2020074607-appb-000352
◆
Figure PCTCN2020074607-appb-000353
◆
Figure PCTCN2020074607-appb-000354
◆
Figure PCTCN2020074607-appb-000355
◆
Figure PCTCN2020074607-appb-000356
◆
Figure PCTCN2020074607-appb-000357
◆
Figure PCTCN2020074607-appb-000358
◆
Figure PCTCN2020074607-appb-000359
◆
Figure PCTCN2020074607-appb-000360
◆
Figure PCTCN2020074607-appb-000361
◆
Figure PCTCN2020074607-appb-000362
◆
Figure PCTCN2020074607-appb-000363
◆
Figure PCTCN2020074607-appb-000364
◆
Figure PCTCN2020074607-appb-000365
◆
Figure PCTCN2020074607-appb-000366
◆
Figure PCTCN2020074607-appb-000367
◆
Figure PCTCN2020074607-appb-000368
◆若
Figure PCTCN2020074607-appb-000369
则
Figure PCTCN2020074607-appb-000370
否则
Figure PCTCN2020074607-appb-000371
◆若
Figure PCTCN2020074607-appb-000372
则
Figure PCTCN2020074607-appb-000373
否则
Figure PCTCN2020074607-appb-000374
◆若
Figure PCTCN2020074607-appb-000375
则
Figure PCTCN2020074607-appb-000376
否则
Figure PCTCN2020074607-appb-000377
◆若
Figure PCTCN2020074607-appb-000378
则
Figure PCTCN2020074607-appb-000379
否则
Figure PCTCN2020074607-appb-000380
◆若
Figure PCTCN2020074607-appb-000381
则
Figure PCTCN2020074607-appb-000382
否则
Figure PCTCN2020074607-appb-000383
◆若K＞1，则
Figure PCTCN2020074607-appb-000384
否则
Figure PCTCN2020074607-appb-000385
Figure PCTCN2020074607-appb-000386
◆若K＞1，则
Figure PCTCN2020074607-appb-000387
否则
Figure PCTCN2020074607-appb-000388
Figure PCTCN2020074607-appb-000389
◆若K＞1，则
Figure PCTCN2020074607-appb-000390
否则
Figure PCTCN2020074607-appb-000391
Figure PCTCN2020074607-appb-000392
◆若K＞1，则
Figure PCTCN2020074607-appb-000393
否则
Figure PCTCN2020074607-appb-000394
Figure PCTCN2020074607-appb-000395
◆若K＞1，则
Figure PCTCN2020074607-appb-000396
否则
Figure PCTCN2020074607-appb-000397
Figure PCTCN2020074607-appb-000398
●若
Figure PCTCN2020074607-appb-000399
则K可以是满足
Figure PCTCN2020074607-appb-000400
的{1，2，4，8}中的最大值；否则K可以等于1。K也可以按其他方式定义。
●RB start的取值范围可以是下面中的任意一项：
◆
Figure PCTCN2020074607-appb-000401
◆
Figure PCTCN2020074607-appb-000402
◆
Figure PCTCN2020074607-appb-000403
◆
Figure PCTCN2020074607-appb-000404
◆若
Figure PCTCN2020074607-appb-000405
则
Figure PCTCN2020074607-appb-000406
Figure PCTCN2020074607-appb-000407
否则
Figure PCTCN2020074607-appb-000408
◆若
Figure PCTCN2020074607-appb-000409
则
Figure PCTCN2020074607-appb-000410
Figure PCTCN2020074607-appb-000411
否则
Figure PCTCN2020074607-appb-000412
◆若K＞1，则
Figure PCTCN2020074607-appb-000413
否则
Figure PCTCN2020074607-appb-000414
◆若K＞1，则
Figure PCTCN2020074607-appb-000415
否则
Figure PCTCN2020074607-appb-000416
●L RBs的取值范围可以是下面中的任意一项：
◆
Figure PCTCN2020074607-appb-000417
◆
Figure PCTCN2020074607-appb-000418
◆
Figure PCTCN2020074607-appb-000419
◆
Figure PCTCN2020074607-appb-000420
◆若
Figure PCTCN2020074607-appb-000421
则
Figure PCTCN2020074607-appb-000422
否则
Figure PCTCN2020074607-appb-000423
◆若
Figure PCTCN2020074607-appb-000424
则
Figure PCTCN2020074607-appb-000425
否则
Figure PCTCN2020074607-appb-000426
◆若K＞1，则
Figure PCTCN2020074607-appb-000427
否则
Figure PCTCN2020074607-appb-000428
◆若K＞1，则
Figure PCTCN2020074607-appb-000429
否则
Figure PCTCN2020074607-appb-000430
●RB start和/或L RBs可以满足以下关系中的一项或多项(在适用的情况下按“与”或者“或”的方式任意组合)：
◆L RBs≥1
◆
Figure PCTCN2020074607-appb-000431
◆
Figure PCTCN2020074607-appb-000432
◆
Figure PCTCN2020074607-appb-000433
◆
Figure PCTCN2020074607-appb-000434
◆若
Figure PCTCN2020074607-appb-000435
则
Figure PCTCN2020074607-appb-000436
否则
Figure PCTCN2020074607-appb-000437
◆若K＞1，则
Figure PCTCN2020074607-appb-000438
否则
Figure PCTCN2020074607-appb-000439
Figure PCTCN2020074607-appb-000440
又如，若不满足频域资源分配缩放条件，则所述RIV可以定义如下：
若
Figure PCTCN2020074607-appb-000441
则
Figure PCTCN2020074607-appb-000442
否则
Figure PCTCN2020074607-appb-000443
其中，可选地，下面中的一项或多项成立：
●
Figure PCTCN2020074607-appb-000444
可以按下面中的任意一项定义：
◆
Figure PCTCN2020074607-appb-000445
◆
Figure PCTCN2020074607-appb-000446
◆
Figure PCTCN2020074607-appb-000447
◆
Figure PCTCN2020074607-appb-000448
◆
Figure PCTCN2020074607-appb-000449
的定义与DCI格式条件有关。例如，当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000450
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000451
又如，当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000452
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000453
●RB start和/或L RBs可以满足以下关系中的一项或多项(在适用的情况下按“与”或者“或”的方式任意组合)：
◆L RBs≥1
◆
Figure PCTCN2020074607-appb-000454
◆
Figure PCTCN2020074607-appb-000455
◆
Figure PCTCN2020074607-appb-000456
◆
Figure PCTCN2020074607-appb-000457
◆
Figure PCTCN2020074607-appb-000458
◆
Figure PCTCN2020074607-appb-000459
◆
Figure PCTCN2020074607-appb-000460
◆
Figure PCTCN2020074607-appb-000461
◆
Figure PCTCN2020074607-appb-000462
◆RB start和/或L RBs满足的关系与DCI格式条件有关。例如，下面中的任意一项成立：
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000463
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000464
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000465
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000466
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000467
Figure PCTCN2020074607-appb-000468
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000469
Figure PCTCN2020074607-appb-000470
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000471
Figure PCTCN2020074607-appb-000472
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000473
Figure PCTCN2020074607-appb-000474
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000475
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000476
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000477
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000478
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000479
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000480
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000481
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000482
●RB start的取值范围可以是下面中的任意一项：
◆
Figure PCTCN2020074607-appb-000483
◆
Figure PCTCN2020074607-appb-000484
◆
Figure PCTCN2020074607-appb-000485
◆
Figure PCTCN2020074607-appb-000486
◆
Figure PCTCN2020074607-appb-000487
◆
Figure PCTCN2020074607-appb-000488
◆
Figure PCTCN2020074607-appb-000489
◆
Figure PCTCN2020074607-appb-000490
◆
Figure PCTCN2020074607-appb-000491
◆RB start的取值范围与DCI格式条件有关。例如，下面中的任意一项成立：
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000492
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000493
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000494
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000495
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000496
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000497
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000498
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000499
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000500
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000501
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000502
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000503
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000504
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000505
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000506
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000507
●L RBs的取值范围可以是下面中的任意一项：
◆
Figure PCTCN2020074607-appb-000508
◆
Figure PCTCN2020074607-appb-000509
◆
Figure PCTCN2020074607-appb-000510
◆
Figure PCTCN2020074607-appb-000511
◆
Figure PCTCN2020074607-appb-000512
◆
Figure PCTCN2020074607-appb-000513
◆
Figure PCTCN2020074607-appb-000514
◆
Figure PCTCN2020074607-appb-000515
◆
Figure PCTCN2020074607-appb-000516
◆L RBs的取值范围与DCI格式条件有关。例如，下面中的任意一项成立：
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000517
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000518
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000519
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000520
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000521
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000522
○当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000523
当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000524
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000525
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000526
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000527
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000528
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000529
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000530
○当DCI格式条件不满足时，
Figure PCTCN2020074607-appb-000531
当DCI格式条件满足时，
Figure PCTCN2020074607-appb-000532
可选地，在本发明的实施例二中，所述频域资源分配缩放条件可以有一个或多个(在适用的情况下按“与”或者“或”的方式任意组合)，其中每一个都可以是下面中的一项或多项(在适用的情况下按“与”或者“或”的方式任意组合)：
●所述DCI格式的大小派生自第三参考大小。例如，所述DCI格式的大小等于所述第三参考大小。又如，在确定所述DCI格式的大小时，通过对所述DCI格式中的一个或者多个字段的大小进行调整(例如在所述字段的指定位置填充一个或多个比特0；又如从所述字段的指定位置开始按指定方向截断一个或多个比特)，或者在所述DCI格式的第一个字段之前或最后一个字段之后填充一个或多个比特0，使得所述DCI格式的大小等于所述第三参考大小。
其中，所述第三参考大小可以按下面中的任意一种方式定义：
◆在CSS中监听的DCI格式1_0的大小。
◆在CSS中监听的DCI格式0_0的大小。
◆在CSS中监听的DCI格式1_0和DCI格式0_0的共同大小。
◆初始上行BWP的大小。
◆有效上行BWP的大小。
◆一个预定义的常数。
◆一个预配置的值。
◆一个从例如基站获取(例如通过DCI或者MAC CE或者RRC信令获取)的参数的值，或者当所述参数未配置时，使用缺省的值。
●所述DCI格式的大小应用于满足参考BWP条件的参考BWP。例如，根据所述DCI格式、以及派生自所述第三参考大小的所述DCI格式的大小来监听PDCCH，其中所述PDCCH用于调度 在所述参考BWP上的PUSCH。
其中，
◆所述参考BWP可以是下面中的任意一个：
○有效上行BWP。
○初始上行BWP。
○所述DCI格式中指示的BWP。例如通过BWP指示器(Bandwidth part indicator)字段指示的BWP。
○预定义或者预配置的BWP。
○从例如基站获取(例如通过DCI或者MAC CE或者RRC信令获取)的参数配置的BWP，或者当所述参数未配置时，使用缺省的BWP。
◆所述参考BWP条件可以是下面中的任意一个(在适用的情况下)：
○无任何条件(即所述参考BWP条件总是可以满足)。例如，此时，“满足参考BWP条件的有效上行BWP”指的是有效上行BWP，且无其他限制条件。
○参考BWP不是初始上行BWP。
○参考BWP不是有效上行BWP。
○参考BWP不是所述DCI格式中指示的BWP。
○参考BWP不是预定义或者预配置的BWP。
○参考BWP不是从例如基站获取(例如通过DCI或者MAC CE或者RRC信令获取)的参数配置的BWP，或者当所述参数未配置时，参考BWP不是对应所述参数的缺省的BWP。
○参考BWP的大小满足第四参考大小。其中，所述第四参考大小可以按下面中的任意一种方式定义：
◇在CSS中监听的DCI格式1_0的大小。
◇在CSS中监听的DCI格式0_0的大小。
◇在CSS中监听的DCI格式1_0和DCI格式0_0的共同大小。
◇初始上行BWP的大小。
◇有效上行BWP的大小。
◇一个预定义的常数。
◇一个预配置的值。
◇一个从例如基站获取(例如通过DCI或者MACCE或者RRC信令获取)的参数的值，或者当所述参数未配置时，使用缺省的值。
○参考BWP的大小不满足所述第四参考大小。
例如，若所述参考BWP是“有效上行BWP”，所述参考BWP条件是“参考BWP不是初始上行BWP”，则当所述DCI格式的大小应用于不是初始上行BWP的有效上行BWP时，条件“所述DCI格式的大小应用于满足参考BWP条件的参考BWP”成立。
可选地，在本发明的实施例二中，所述频域资源分配缩放条件也可以按其他方式定义。
可选地，在本发明的实施例二中，所述DCI格式条件可以是下面中的一个或多个(在适用的情况下按“与”或者“或”的方式任意组合)：
●所述DCI格式是在CSS中监听的DCI格式0_0。
●所述DCI格式是在USS中监听的DCI格式0_0。
●所述DCI格式是在USS中监听的DCI格式0_1。
其中，可选地，所述“监听”也可以替换为“解码”。
可选地，在本发明的实施例二中，所述DCI格式条件也可以按其他方式定义。
这样，本发明的实施例二通过恰当地定义RIV，以及设置RB start和/或L RBs和/或RB′ start和L′ RBs的取值范围，以及定义频域资源分配缩放条件和/或DCI格式条件等，确保了DCI中分配的频域资源落在有效上行BWP 内，避免了由于所分配的频域资源落在有效上行BWP外而引起的用户间干扰。
[实施例三]
下面结合图3来说明本发明的实施例三的由用户设备执行的方法。
图3是示出了根据本发明的实施例三的由用户设备执行的方法的流程图。
如图3所示，在本发明的实施例三中，用户设备UE执行的步骤包括：步骤S301和步骤S303。
具体地，在步骤S301，获取与信道栅格(channel raster)到资源元素(resource element)的映射有关的参数的配置信息(如所述参数是否已配置，或所述参数所配置的值)。例如，从预定义信息或预配置信息中获取所述参数的配置信息，或者从基站获取所述参数的配置信息，或者从其他UE获取所述参数的配置信息，或者当所述参数未配置时使用缺省的配置信息。
其中，所述参数可以包括：
●参考子载波间隔配置(记为rf-subcarrierSpacing)。例如，rf-subcarrierSpacing等于0、1、2、3和4分别表示相应的参考子载波间隔为15kHz、30kHz、60kHz、120kHz和240kHz。
例如，通过DCI获取所述参数rf-subcarrierSpacing的配置信息。
又如，通过MAC CE获取所述参数rf-subcarrierSpacing的配置信息。
又如，通过RRC信令(例如MIB或者SIB1中的一个或多个字段)获取所述参数rf-subcarrierSpacing的配置信息。
又如，所述参数rf-subcarrierSpacing的取值是一个预定义或预配置的值。例如，所述参数rf-subcarrierSpacing等于{0，1，2，3，4}中的任意一个值。
可选地，所述参数rf-subcarrierSpacing的配置信息对于频率范围1(frequency range 1，FR1)和频率范围2(frequency range 2，FR2)可以分别进行配置。例如，在FR1，所述参数rf-subcarrierSpacing可以取{0，1，2}中的任意一个值(例如0)；在FR2，所述参数rf-subcarrierSpacing 可以取{2，3，4}中的任意一个值(例如2)。
此外，在步骤S303，根据所述参考子载波间隔配置，和/或其他配置信息，确定信道栅格到资源元素的映射，和/或RF信道的带宽和/或位置。
例如，若N RBmod 2＝0，则
Figure PCTCN2020074607-appb-000533
k＝0；若N RBmod 2＝1，则
Figure PCTCN2020074607-appb-000534
k＝6。其中，
●N RB可以是所述参考子载波间隔配置所对应的传输带宽配置(transmission bandwidth configuration)。例如，N RB等于通过SCS-SpecificCarrier IE中的参数carrierBandwidth所配置的载波带宽(例如，N RB＝20)，其中，可选地，所述SCS-SpecificCarrier IE中的参数subcarrierSpacing等于所述参考子载波间隔配置rf-subcarrierSpacing(例如，所述参数subcarrierSpacing和rf-subcarrierSpacing都等于0，即都对应子载波间隔为15kHz)。另外，可选地，N RB所对应的最大传输带宽配置(maximum transmission bandwidth configuration)等于所述参考子载波间隔配置所对应的最大传输带宽配置值的集合中大于或等于20的最小值，即25，对应信道带宽为5MHz。
●N RB也可以是所述参考子载波间隔配置所对应的最大传输带宽配置。例如，若通过SCS-SpecificCarrier IE中的参数subcarrierSpacing所配置的子载波间隔配置和所述参考子载波间隔配置rf-subcarrierSpacing都等于0(即对应子载波间隔为15kHz)，且参数carrierBandwidth所配置的载波带宽为20个RB，则N RB等于所述参考子载波间隔配置所对应的最大传输带宽配置值的集合中大于或等于20的最小值，即25(对应信道带宽为5MHz)。又如，若通过SCS-SpecificCarrier IE中的参数subcarrierSpacing所配置的子载波间隔配置和所述参考子载波间隔配置rf-subcarrierSpacing都等于0(即对应子载波间隔为15kHz)，且参数carrierBandwidth所配置的载波带宽为40个RB，则N RB等于所述参考子载波间隔配置所对应的最大传输带宽配置值的集合中大于或等于40的最小值，即52(对应信道带宽为10MHz)。
●n CRB是所述信道栅格所对应的公共资源块(Common Resource Block，CRB)的编号。
●k是所述信道栅格所对应的n CRB内的子载波的编号。
●所述信道栅格对应一个RF参考频率(RF reference frequency)，所述RF参考频率用于标识RF信道的位置。
这样，本发明的实施例三通过定义参考子载波间隔配置，使得UE可以在基站配置了多个子载波间隔的情况下任然能够唯一确定信道栅格到资源元素的映射，和/或RF信道的带宽和/或位置，确保了UE所发射的信号和基站配置和/或指示的频率一致。
[实施例四]
下面，结合图4来说明本发明的实施例四的由用户设备执行的方法。
图4是示出了根据本发明的实施例四的由用户设备执行的方法的流程图。
如图4所示，在本发明的实施例四中，用户设备UE执行的步骤包括：步骤S401、步骤S403和步骤S405。
具体地，在步骤S401，获取与SL信道的加扰(scrambling)有关的参数的配置信息(如所述参数是否已配置，或所述参数所配置的值)。例如，从预定义信息或预配置信息中获取所述配置信息，或者从基站获取所述配置信息(例如通过DCI或者MAC CE或者RRC信令获取所述配置信息)，或者从其他UE获取所述配置信息，或者当所述参数未配置时，使用一个缺省的值，或者上述方式的组合。
其中，
●所述SL信道可以是与SL同步有关的信道，也可以是与SL通信有关的信道，也可以是在SL载波上传输的其他信道。具体地，所述信道可以是PSBCH，也可以是PSCCH，也可以是PSSCH，也可以是PSFCH，也可以是其他SL信道。
●所述参数可以包括：
◆与SL信道的加扰有关的ID(记为
Figure PCTCN2020074607-appb-000535
)。其中，
○可选地，所述ID可以是在SL同步、SL通信或在SL载波上传输其他信道时用于标识源(source)UE或目标(destination)UE的UE ID。例如，高层(即高于物理层，例如应用层，又如TCP/IP层，又如SDAP层，又如RRC层，又如PDCP层，又如RLC层，又如MAC层)UE ID，又如，物理层UE ID(可选地，又称为层1UE ID，layer 1UE ID)。可选地，所述UE ID可以用于标识一个UE，也可以用于标识一组UE(其中包含一个或多个UE)；当所述UE ID用于标识一组UE时，也可以将所述UE ID称为组ID(group ID)或UE组ID(UE group ID)，相应地，所述源UE ID可以称为源组ID或源UE组ID，所述目标UE ID可以称为目标组ID或目标UE组ID。可选地，当提及所述UE ID或所述组ID时，既可以指所述UE ID或所述组ID的一部分比特(如8个最低有效位，或8个最高有效位，或16个最低有效位，或16个最高有效位)所对应的整数，也可以指所述UE ID或所述组ID的全部比特所对应的整数。
○可选地，所述ID可以是一个预定义或者预配置的常数，或者通过DCI或者MAC CE或者RRC信令配置的数值。例如0，又如65535，又如4294967295。
○可选地，所述ID可以是SL同步ID，例如在SL PSS和/或SL SSS中携带的ID。所述SL同步ID的取值范围集合可以是{0，1，...，83}，也可以是{0，1，...，167}，也可以是{0，1，...，251}，也可以是{0，1，...，335}，也可以是{0，1，...，419}，也可以是{0，1，...，503}，也可以是{0，1，...，587}，也可以是{0，1，...，671}，也可以是{0，1，...，755}，也可以是{0，1，...，839}，也可以是{0，1，...，923}，也可以是{0，1，...，1007}，也可以是{0， 1，...，1091}，也可以是其他整数集合。
○可选地，所述ID可以是SCI ID。所述SCI ID可以用于标识SCI格式，例如SCI格式0使用SCI ID0，SCI格式1使用SCI ID1，且SCI ID0不等于SCI ID1。
○可选地，所述ID可以针对单播(unicast)、组播(groupcast)和广播(broadcast)中的一个或多个分别进行配置。
○可选地，所述ID可以针对PSBCH、PSCCH、PSSCH和PSFCH中的一个或多个分别进行配置。
○可选地，所述ID可以针对所述SL信道所使用的不同资源分配模式(例如模式1，即基站调度用于UE的SL传输的SL资源；又如模式2，即UE确定用于UE的SL传输的SL资源)分别进行配置。
○可选地，所述ID可以等于C 1·ID 0+C 2·sl 0+C 3·sym 0+C 4。其中，C 1、C 2、C 3和C 4是常数，ID 0是源UE ID、目标UE ID、源组ID、目标组ID、SL同步ID、SCI ID、预定义或者预配置的常数、通过DCI或者MAC CE或者RRC信令配置的数值中的一个，sl 0是所述SL信道的传输所在的时隙(或者当所述SL信道的传输占用多于一个时隙时，所述SL信道的传输所在的第一个时隙)在子帧或帧内的编号，sym 0是所述SL信道的传输所在的第一个符号在时隙或子帧或帧内的编号。可选地，C 1、C 2、C 3和C 4中的一个或多个可以等于0。
例如，对于单播通信中传输的PSSCH，所述ID可以是所述单播通信中的目标UE ID(例如高层UE ID，又如物理层UE ID)。又如，对于组播通信中传输的PSSCH，所述ID可以是所述组播通信中的目标组ID(例如高层UE ID，又如物理层UE ID)。又如，对于广播通信中传输的PSSCH，所述ID可以是一个特殊的(如预定义或者预配置的，或者通过DCI或者MAC CE或者RRC信令配置的)UE ID或者组ID(例如高层UE ID， 又如物理层UE ID)，或者是SL同步ID。又如，对于PSCCH，所述ID可以是SCI ID。
此外，在步骤S403，根据所述与SL信道的加扰有关的参数的配置信息，和/或其他配置信息，确定所述SL信道的加扰序列。
其中，
●所述加扰序列可以是一个伪随机序列(pseudo-random sequence)。例如，所述伪随机序列c(n)可以定义如下：
c(n)＝(x 1(n+N C)+x 2(n+N C))mod 2
x 1(n+31)＝(x 1(n+3)+x 1(n))mod 2
x 2(n+31)＝(x 2(n+3)+x 2(n+2)+x 2(n+1)+x 2(n))mod 2
其中，
◆N C＝1600。
◆x 1(n)初始化为x 1(0)＝1，x 1(n)＝0，n＝1，2，...，30。
◆x 2(n)初始化为
Figure PCTCN2020074607-appb-000536
其中，c init可以是
Figure PCTCN2020074607-appb-000537
的一个函数，例如
Figure PCTCN2020074607-appb-000538
又如
Figure PCTCN2020074607-appb-000539
其中C 5和C 6是常数。
●所述加扰序列也可以是所述ID所对应的部分或全部比特。例如，若
Figure PCTCN2020074607-appb-000540
是一个32位的整数，则所述加扰序列可以是
Figure PCTCN2020074607-appb-000541
中的部分或全部比特，其中
Figure PCTCN2020074607-appb-000542
是
Figure PCTCN2020074607-appb-000543
的最高有效位，
Figure PCTCN2020074607-appb-000544
是
Figure PCTCN2020074607-appb-000545
的次高有效位，……，
Figure PCTCN2020074607-appb-000546
是
Figure PCTCN2020074607-appb-000547
的最低有效位。
此外，在步骤S405，对在所述SL信道上传输的信息进行加扰。
其中，
●所述信息可以是在所述SL信道上传输的、信道编码(channel coding)后的部分或全部比特。其中，所述“信道编码后”可以指信道编码的最后一个步骤之后，例如速率匹配(rate matching)后，或者码块连接(code block concatenation)后，或者数据与控制复用(data and control multiplexing)后。例如，若码字q所对应的比特块在加扰前为
Figure PCTCN2020074607-appb-000548
在加扰后为
Figure PCTCN2020074607-appb-000549
Figure PCTCN2020074607-appb-000550
其中
Figure PCTCN2020074607-appb-000551
是所述码字q在所述SL信道上传输的比特个数，则所述加扰过程可以如下：
Figure PCTCN2020074607-appb-000552
●所述信息也可以是CRC附着(CRC attachment)过程中生成的一个或多个CRC，例如传输块(transport block)CRC，又如一个或多个码块(code block)CRC，又如为SCI的负荷计算的CRC。
例如，若SCI负荷比特序列为a 0，a 1，...，a A-1，加扰前的CRC序列为p 0，p 1，...，p L-1，且L＝24，则
◆在CRC附着后的比特序列为b 0，b 1，...，b A+23，其中对于k＝0，1，...，A-1，b k＝a k；对于k＝A，A+1，...，A+23，b k＝a k-A。
◆在对CRC加扰后的比特序列为c 0，c 1，...，C A+23，其中对于k＝0，1，...，A-1，c k＝b k；对于k＝A，A+1，...，A+23，
Figure PCTCN2020074607-appb-000553
其中，F是个常数，例如F＝0，又如F＝8。
这样，本发明的实施例四通过在进行SL信道的加扰序列的初始化时使用一个特殊的加扰ID，至少部分避免了不同UE发送的SL信道之间的加扰序列的冲突，从而极大减少了不同SL信道之间的可能存在的互相干扰。另外，使用一个较长的ID对SL信道进行加扰也极大减少、甚至完全避免了由于短ID(如物理层ID)的潜在冲突而导致的无法在物理层正确识别源和/或目的UE ID等问题。
[实施例五]
下面，结合图5来说明本发明的实施例五的由用户设备执行的方法。
图5是示出了根据本发明的实施例五的由用户设备执行的方法的流程图。
如图5所示，在本发明的实施例五中，用户设备UE执行的步骤包括：步骤S501和步骤S503。
具体地，在步骤S501，获取与SCI(Sidelink Control Information)格式有关的一个或多个参数的配置信息(如所述参数是否已配置，或所述参数所配置的值)。例如，从预定义信息或预配置信息中获取所述配置信息，或者从基站获取所述配置信息(例如通过DCI或者MAC CE或者RRC信令获取所述配置信息)，或者从其他UE获取所述配置信息，或者当所述参数未配置时，使用一个缺省的值，或者上述方式的组合。
其中，所述参数可以指示与一个或多个SCI格式(SCI format)有关的信息；对每个SCI格式，所述参数可以包括下面中的一个或多个：
●SCI格式的标识符。例如，实施例四所定义的SCI ID。又如，用于标识SCI所对应的SL传输/通信类型(例如单播，组播，或者广播)。又如，按其他方式定义的SCI格式的标识符。
●用于加扰SCI格式的RNTI。
●SCI的大小(size)。例如，所述SCI的大小的单位可以是比特，取值范围可以是{8，9，...，200}的任意一个子集。
●SCI的聚合级别(aggregation level)。
●SCI的重复次数。
此外，在步骤S503，根据所述与SCI格式有关的参数的配置信息，和/或其他配置信息，发送或接收携带SCI的PSCCH。
这样，本发明的实施例五通过配置一些通用的与SCI格式有关的参数，例如SCI的大小，使得在SCI相关的标准协议增强后(例如，为SCI格式增加了新的字段)，在所述标准协议增强前制造的UE仍然能够解码增强后的SCI格式并正确解读其中至少一部分字段(例如与资源预留有关的字段)，从而极大地改进SCI设计和/或资源预留机制的兼容性。
[实施例六]
下面，结合图6来说明本发明的实施例六的由用户设备执行的方法。
图6是示出了根据本发明的实施例六的由用户设备执行的方法的流程图。
如图6所示，在本发明的实施例六中，用户设备UE执行的步骤包括：步骤S601和步骤S603。
具体地，在步骤S601，获取与UE ID有关的一个或多个参数的配置信息(如所述参数是否已配置，或所述参数所配置的值)。例如，从预定义信息或预配置信息中获取所述配置信息，或者从基站获取所述配置信息(例如通过DCI或者MAC CE或者RRC信令获取所述配置信息)，或者从其他UE获取所述配置信息，或者当所述参数未配置时，使用一个缺省的值，或者上述方式的组合。
其中，
●可选地，所述UE ID可以在SL同步、SL通信或在SL载波上传输其他信号或信道时用于标识源(source)UE或目标(destination)UE。可选地，所述SL同步、SL通信或在SL载波上传输其他信号或信道的目的是承载V2X相关的业务，相应地，所述UE可以称为V2X UE。
●可选地，所述UE ID可以用于标识一个UE，也可以用于标识一组UE(其中包含一个或多个UE)；当所述UE ID用于标识一组UE时，也可以将所述UE ID称为组ID(group ID)或UE组ID(UE group ID)，相应地，所述源UE ID可以称为源组ID或源UE组ID，所述目标UE ID可以称为目标组ID或目标UE组ID。
●可选地，所述UE ID可以是高层(即高于物理层，例如应用层，又如TCP/IP层，又如SDAP层，又如RRC层，又如PDCP层，又如RLC层，又如MAC层)UE ID，也可以是物理层UE ID。所述物理层UE ID也可以称为层1UE ID(layer 1UE ID)。
●可选地，所述一个或多个参数可以分别指示每种SL传输/通信 的类型所对应的UE ID的取值集合(其中每个集合中包含一个或多个整数)，例如，通过下面中的一项或多项：
○参数unicast-IDs用于配置单播通信中使用的UE ID的取值集合，例如，{0，1，...，255}中的任意一个子集。又如，{0，1，...，511}中的任意一个子集。又如，{0，1，...，1023}中的任意一个子集。又如，{0，1，...，2047}中的任意一个子集。又如，{0，1，...，4095}中的任意一个子集。
○参数groupcast-IDs用于配置组播通信中使用的UE ID的取值集合。例如，{0，1，...，255}中的任意一个子集。又如，{0，1，...，511}中的任意一个子集。又如，{0，1，...，1023}中的任意一个子集。又如，{0，1，...，2047}中的任意一个子集。又如，{0，1，...，4095}中的任意一个子集。
○参数broadcast-IDs用于配置广播通信中使用的UE ID的取值集合。例如，{0，1，...，255}中的任意一个子集。又如，{0，1，...，511}中的任意一个子集。又如，{0，1，...，1023}中的任意一个子集。又如，{0，1，...，2047}中的任意一个子集。
又如，{0，1，...，4095}中的任意一个子集。
●可选地，所述参数unicast-IDs和groupcast-IDs和broadcast-IDs所分别配置的UE ID的取值集合互不重合。
●可选地，可以根据所述参数unicast-IDs和groupcast-IDs的配置推导出广播通信中使用的UE ID的取值集合。例如，记单播、组播和广播通信中使用的UE ID的取值集合分别为A(由所述参数unicast-IDs配置)、B(由所述参数groupcast-IDs配置)和C，若集合A、B和C互不重合，且集合A、B和C的并集是{0，1，...，255}，则集合C等于{0，1，...，255}-A-B。
●可选地，可以根据所述参数unicast-IDs和broadcast-IDs的配置推导出组播通信中使用的UE ID的取值集合。例如，记单播、组播和广播通信中使用的UE ID的取值集合分别为A(由所述参数unicast-IDs配置)、B和C(由所述参数broadcast-IDs配置)，若集合A、B和C互不重合，且集合A、B和C的并集 是{0，1，...，255}，则集合B等于{0，1，...，255}-A-C。
●可选地，可以根据所述参数broadcast-IDs和groupcast-IDs的配置推导出单播通信中使用的UE ID的取值集合。例如，记单播、组播和广播通信中使用的UE ID的取值集合分别为A、B(由所述参数groupcast-IDs配置)和C(由所述参数broadcast-IDs配置)，若集合A、B和C互不重合，且集合A、B和C的并集是{0，1，...，255}，则集合A等于{0，1，...，255}-C-B。
此外，在步骤S603，根据所述与UE ID有关的一个或多个参数的配置信息，和/或其他配置信息，接收PSCCH。
例如，若所述PSCCH中携带的SCI中的目标UE ID在所述参数unicast-IDs所配置的集合中，则可以认为所述PSCCH及其所调度的PSSCH用于单播通信。
又如，若所述PSCCH中携带的SCI中的目标UE ID在所述参数groupcast-IDs所配置的集合中，则可以认为所述PSCCH及其所调度的PSSCH用于组播通信。
又如，若所述PSCCH中携带的SCI中的目标UE ID在所述参数broadcast-IDs所配置的集合中，则可以认为所述PSCCH及其所调度的PSSCH用于广播通信。
又如，若所述PSCCH中携带的SCI中的目标UE ID等于源UE ID，则可以认为所述PSCCH及其所调度的PSSCH用于组播通信。
这样，本发明的实施例六通过配置每种SL传输/通信的类型(例如单播通信和/或组播通信和/或广播通信)所对应的UE ID的取值集合，使得UE可以根据SCI中的UE ID(例如目标UE ID)字段，确定一个给定的SL传输(例如PSCCH传输，和/或其所调度的PSSCH传输)所属的传输/通信类型。例如，当UE只需要监听其中一种传输/通信类型(例如广播通信)时，可以高效地过滤掉所接收的、不属于所述SL传输/通信类型的PSCCH/PSSCH。
[变形例]
下面，利用图7来说明作为一种变形例的可执行本发明上面所详细描述的用户设备执行的方法的用户设备。
图7是表示本发明所涉及的用户设备UE的框图。
如图7所示，该用户设备UE70包括处理器701和存储器702。处理器701例如可以包括微处理器、微控制器、嵌入式处理器等。存储器702例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器702上存储有程序指令。该指令在由处理器701运行时，可以执行本发明详细描述的由用户设备执行的上述方法。
上文已经结合优选实施例对本发明的方法和涉及的设备进行了描述。本领域技术人员可以理解，上面示出的方法仅是示例性的，而且以上说明的各实施例在不发生矛盾的情况下能够相互组合。本发明的方法并不局限于上面示出的步骤和顺序。上面示出的网络节点和用户设备可以包括更多的模块，例如还可以包括可以开发的或者将来开发的可用于基站、MME、或UE的模块等等。上文中示出的各种标识仅是示例性的而不是限制性的，本发明并不局限于作为这些标识的示例的具体信元。本领域技术人员根据所示实施例的教导可以进行许多变化和修改。
应该理解，本发明的上述实施例可以通过软件、硬件或者软件和硬件两者的结合来实现。例如，上述实施例中的基站和用户设备内部的各种组件可以通过多种器件来实现，这些器件包括但不限于：模拟电路器件、数字电路器件、数字信号处理(DSP)电路、可编程处理器、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、可编程逻辑器件(CPLD)，等等。
在本申请中，“基站”可以指具有较大发射功率和较广覆盖面积的移动通信数据和控制交换中心，包括资源分配调度、数据接收发送等功能。“用户设备”可以指用户移动终端，例如包括移动电话、笔记本等可以与基站或者微基站进行无线通信的终端设备。
此外，这里所公开的本发明的实施例可以在计算机程序产品上实现。 更具体地，该计算机程序产品是如下的一种产品：具有计算机可读介质，计算机可读介质上编码有计算机程序逻辑，当在计算设备上执行时，该计算机程序逻辑提供相关的操作以实现本发明的上述技术方案。当在计算***的至少一个处理器上执行时，计算机程序逻辑使得处理器执行本发明实施例所述的操作(方法)。本发明的这种设置典型地提供为设置或编码在例如光介质(例如CD-ROM)、软盘或硬盘等的计算机可读介质上的软件、代码和/或其他数据结构、或者诸如一个或多个ROM或RAM或PROM芯片上的固件或微代码的其他介质、或一个或多个模块中的可下载的软件图像、共享数据库等。软件或固件或这种配置可安装在计算设备上，以使得计算设备中的一个或多个处理器执行本发明实施例所描述的技术方案。
此外，上述每个实施例中所使用的基站设备和终端设备的每个功能模块或各个特征可以由电路实现或执行，所述电路通常为一个或多个集成电路。设计用于执行本说明书中所描述的各个功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)或通用集成电路、现场可编程门阵列(FPGA)或其他可编程逻辑器件、分立的门或晶体管逻辑、或分立的硬件组件、或以上器件的任意组合。通用处理器可以是微处理器，或者所述处理器可以是现有的处理器、控制器、微控制器或状态机。上述通用处理器或每个电路可以由数字电路配置，或者可以由逻辑电路配置。此外，当由于半导体技术的进步，出现了能够替代目前的集成电路的先进技术时，本发明也可以使用利用该先进技术得到的集成电路。
尽管以上已经结合本发明的优选实施例示出了本发明，但是本领域的技术人员将会理解，在不脱离本发明的精神和范围的情况下，可以对本发明进行各种修改、替换和改变。因此，本发明不应由上述实施例来限定，而应由所附权利要求及其等价物来限定。

Claims (10)

  1. 一种由用户设备执行的方法，包括：
    接收用于调度物理下行共享信道PDSCH的传输的下行控制信息DCI；以及
    根据接收到的所述DCI中的频域资源分配FDRA字段，确定资源指示值RIV，并根据所述RIV确定所分配的起始资源块RB start以及连续分配的资源块的长度L RBs，
    其中，若不满足频域资源分配缩放条件，则根据所述RIV直接确定RB start以及L RBs，若满足频域资源分配缩放条件，则根据所述RIV先确定将RB start除以缩放因子K后得到的起始资源块RB′ start以及将L RBs除以所述缩放因子K后得到的连续分配的资源块的长度L′ RBs，然后再根据RB′ start和L′ RBs确定RB start以及L RBs，
    所述缩放因子K根据
    Figure PCTCN2020074607-appb-100001
    与
    Figure PCTCN2020074607-appb-100002
    的比值来确定，
    Figure PCTCN2020074607-appb-100003
    表示初始下行带宽片段BWP的大小，
    Figure PCTCN2020074607-appb-100004
    表示有效下行BWP的大小。
  2. 根据权利要求1所述的方法，其特征在于，
    若满足频域资源分配缩放条件，则
    RB′ start和L′ RBs满足以下关系中的一项或多项：
    Figure PCTCN2020074607-appb-100005
    Figure PCTCN2020074607-appb-100006
    Figure PCTCN2020074607-appb-100007
    Figure PCTCN2020074607-appb-100008
    Figure PCTCN2020074607-appb-100009
    Figure PCTCN2020074607-appb-100010
    Figure PCTCN2020074607-appb-100011
    Figure PCTCN2020074607-appb-100012
    Figure PCTCN2020074607-appb-100013
    Figure PCTCN2020074607-appb-100014
    Figure PCTCN2020074607-appb-100015
    Figure PCTCN2020074607-appb-100016
    Figure PCTCN2020074607-appb-100017
    Figure PCTCN2020074607-appb-100018
    Figure PCTCN2020074607-appb-100019
    Figure PCTCN2020074607-appb-100020
    Figure PCTCN2020074607-appb-100021
    Figure PCTCN2020074607-appb-100022
    Figure PCTCN2020074607-appb-100023
    Figure PCTCN2020074607-appb-100024
    Figure PCTCN2020074607-appb-100025
    ◆若
    Figure PCTCN2020074607-appb-100026
    则
    Figure PCTCN2020074607-appb-100027
    否则
    Figure PCTCN2020074607-appb-100028
    ◆若
    Figure PCTCN2020074607-appb-100029
    则
    Figure PCTCN2020074607-appb-100030
    否则
    Figure PCTCN2020074607-appb-100031
    ◆若
    Figure PCTCN2020074607-appb-100032
    则
    Figure PCTCN2020074607-appb-100033
    否则
    Figure PCTCN2020074607-appb-100034
    ◆若
    Figure PCTCN2020074607-appb-100035
    则
    Figure PCTCN2020074607-appb-100036
    否则
    Figure PCTCN2020074607-appb-100037
    ◆若
    Figure PCTCN2020074607-appb-100038
    则
    Figure PCTCN2020074607-appb-100039
    否则
    Figure PCTCN2020074607-appb-100040
    ◆若K＞1，则
    Figure PCTCN2020074607-appb-100041
    否则
    Figure PCTCN2020074607-appb-100042
    Figure PCTCN2020074607-appb-100043
    ◆若K＞1，则
    Figure PCTCN2020074607-appb-100044
    否则
    Figure PCTCN2020074607-appb-100045
    Figure PCTCN2020074607-appb-100046
    ◆若K＞1，则
    Figure PCTCN2020074607-appb-100047
    否则
    Figure PCTCN2020074607-appb-100048
    Figure PCTCN2020074607-appb-100049
    ◆若K＞1，则
    Figure PCTCN2020074607-appb-100050
    否则
    Figure PCTCN2020074607-appb-100051
    Figure PCTCN2020074607-appb-100052
    ◆若K＞1，则
    Figure PCTCN2020074607-appb-100053
    否则
    Figure PCTCN2020074607-appb-100054
    Figure PCTCN2020074607-appb-100055
  3. 根据权利要求1所述的方法，其特征在于，
    所述频域资源分配缩放条件包括：所述DCI格式的大小派生自第一参考大小，
    所述第一参考大小可以按下面中的任意一种方式定义：
    ◆在CSS中监听的DCI格式1_0的大小；
    ◆在CSS中监听的DCI格式0_0的大小；
    ◆在CSS中监听的DCI格式1_0和DCI格式0_0的共同大小；
    ◆ID为0的控制资源集CORESET即CORESET 0的大小；
    ◆初始下行BWP的大小；
    ◆有效下行BWP的大小；
    ◆若小区中CORESET 0已配置，则所述第一参考大小等于CORESET 0的大小；若小区中CORESET 0未配置，则所述第一参考大小等于初始下行BWP的大小；
    ◆预定义的常数；
    ◆预配置的值；
    ◆从基站获取的参数的值，或者当所述参数未配置时，使用缺省的值。
  4. 根据权利要求1所述的方法，其特征在于，
    所述频域资源分配缩放条件包括：所述DCI格式的大小应用于满足参考BWP条件的参考BWP，
    所述参考BWP可以是下面中的任意一个：
    ο有效下行BWP；
    ο初始下行BWP；
    ο所述DCI格式中指示的BWP；
    ο预定义或者预配置的BWP；
    ο从基站获取的参数配置的BWP，或者当所述参数未配置时，使用缺省的BWP。
  5. 一种由用户设备执行的方法，包括：
    接收用于调度物理上行共享信道PUSCH的传输的下行控制信息DCI；以及
    根据接收到的所述DCI中的频域资源分配FDRA字段，确定资源指 示值RIV，并根据所述RIV确定所分配的起始资源块RB start以及连续分配的资源块的长度L RBs，
    其中，若不满足频域资源分配缩放条件，则根据所述RIV直接确定RB start以及L RBs，若满足频域资源分配缩放条件，则根据所述RIV先确定将RB start除以缩放因子K后得到的起始资源块RB′ start以及将L RBs除以所述缩放因子K后得到的连续分配的资源块的长度L′ RBs，然后再根据RB′ start和L′ RBs确定RB start以及L RBs，
    所述缩放因子K根据
    Figure PCTCN2020074607-appb-100056
    与
    Figure PCTCN2020074607-appb-100057
    的比值来确定，
    Figure PCTCN2020074607-appb-100058
    表示初始上行带宽片段BWP的大小，
    Figure PCTCN2020074607-appb-100059
    表示有效上行BWP的大小。
  6. 根据权利要求5所述的方法，其特征在于，
    若满足频域资源分配缩放条件，则
    RB′ start和L′ RBs满足以下关系中的一项或多项：
    Figure PCTCN2020074607-appb-100060
    Figure PCTCN2020074607-appb-100061
    Figure PCTCN2020074607-appb-100062
    Figure PCTCN2020074607-appb-100063
    Figure PCTCN2020074607-appb-100064
    Figure PCTCN2020074607-appb-100065
    Figure PCTCN2020074607-appb-100066
    Figure PCTCN2020074607-appb-100067
    Figure PCTCN2020074607-appb-100068
    Figure PCTCN2020074607-appb-100069
    Figure PCTCN2020074607-appb-100070
    Figure PCTCN2020074607-appb-100071
    Figure PCTCN2020074607-appb-100072
    Figure PCTCN2020074607-appb-100073
    Figure PCTCN2020074607-appb-100074
    Figure PCTCN2020074607-appb-100075
    Figure PCTCN2020074607-appb-100076
    Figure PCTCN2020074607-appb-100077
    Figure PCTCN2020074607-appb-100078
    Figure PCTCN2020074607-appb-100079
    Figure PCTCN2020074607-appb-100080
    ◆若
    Figure PCTCN2020074607-appb-100081
    则
    Figure PCTCN2020074607-appb-100082
    否则
    Figure PCTCN2020074607-appb-100083
    ◆若
    Figure PCTCN2020074607-appb-100084
    则
    Figure PCTCN2020074607-appb-100085
    否则
    Figure PCTCN2020074607-appb-100086
    ◆若
    Figure PCTCN2020074607-appb-100087
    则
    Figure PCTCN2020074607-appb-100088
    否则
    Figure PCTCN2020074607-appb-100089
    ◆若
    Figure PCTCN2020074607-appb-100090
    则
    Figure PCTCN2020074607-appb-100091
    否则
    Figure PCTCN2020074607-appb-100092
    ◆若
    Figure PCTCN2020074607-appb-100093
    则
    Figure PCTCN2020074607-appb-100094
    否则
    Figure PCTCN2020074607-appb-100095
    ◆若K＞1，则
    Figure PCTCN2020074607-appb-100096
    否则
    Figure PCTCN2020074607-appb-100097
    Figure PCTCN2020074607-appb-100098
    ◆若K＞1，则
    Figure PCTCN2020074607-appb-100099
    否则
    Figure PCTCN2020074607-appb-100100
    Figure PCTCN2020074607-appb-100101
    ◆若K＞1，则
    Figure PCTCN2020074607-appb-100102
    否则
    Figure PCTCN2020074607-appb-100103
    Figure PCTCN2020074607-appb-100104
    ◆若K＞1，则
    Figure PCTCN2020074607-appb-100105
    否则
    Figure PCTCN2020074607-appb-100106
    Figure PCTCN2020074607-appb-100107
    ◆若K＞1，则
    Figure PCTCN2020074607-appb-100108
    否则
    Figure PCTCN2020074607-appb-100109
    Figure PCTCN2020074607-appb-100110
  7. 根据权利要求5所述的方法，其特征在于，
    所述频域资源分配缩放条件包括：所述DCI格式的大小派生自第三参考大小，
    所述第三参考大小可以按下面中的任意一种方式定义：
    ◆在CSS中监听的DCI格式1_0的大小；
    ◆在CSS中监听的DCI格式0_0的大小；
    ◆在CSS中监听的DCI格式1_0和DCI格式0_0的共同大小；
    ◆初始上行BWP的大小；
    ◆有效上行BWP的大小；
    ◆预定义的常数；
    ◆预配置的值；
    ◆从基站获取的参数的值，或者当所述参数未配置时，使用缺省的值。
  8. 根据权利要求5所述的方法，其特征在于，
    所述频域资源分配缩放条件包括：所述DCI格式的大小应用于满足参考BWP条件的参考BWP，
    所述参考BWP可以是下面中的任意一个：
    ο有效上行BWP；
    ο初始上行BWP；
    ο所述DCI格式中指示的BWP；
    ο预定义或者预配置的BWP；
    ο从基站获取的参数配置的BWP，或者当所述参数未配置时，使用缺省的BWP。
  9. 一种用户设备，包括：
    处理器；以及
    存储器，存储有指令，
    其中，所述指令在由所述处理器运行时执行根据权利要求1-4中的任一项所述的方法。
  10. 一种用户设备，包括：
    处理器；以及
    存储器，存储有指令，
    其中，所述指令在由所述处理器运行时执行根据权利要求5-8所述的方法。
PCT/CN2020/074607 2019-02-14 2020-02-10 由用户设备执行的方法以及用户设备 WO2020164452A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/430,986 US20220140968A1 (en) 2019-02-14 2020-02-10 Method executed by user equipment, and user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910116786.6 2019-02-14
CN201910116786.6A CN111565461A (zh) 2019-02-14 2019-02-14 由用户设备执行的方法以及用户设备

Publications (1)

Publication Number Publication Date
WO2020164452A1 true WO2020164452A1 (zh) 2020-08-20

Family

ID=72044030

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/074607 WO2020164452A1 (zh) 2019-02-14 2020-02-10 由用户设备执行的方法以及用户设备

Country Status (3)

Country Link
US (1) US20220140968A1 (zh)
CN (1) CN111565461A (zh)
WO (1) WO2020164452A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6861891B2 (ja) * 2017-09-11 2021-04-21 エルジー エレクトロニクス インコーポレイティド 無線通信システムにおけるダウンリンク制御情報を送信する方法及び装置
CN114157403B (zh) * 2020-09-07 2023-09-22 维沃移动通信有限公司 资源确定方法、装置、终端及网络侧设备
US20220116929A1 (en) * 2020-10-09 2022-04-14 Qualcomm Incorporated Techniques for indicating a configuration using a resource allocation indication
CN114640430A (zh) * 2020-12-15 2022-06-17 夏普株式会社 由用户设备执行的方法以及用户设备
CN114765868A (zh) * 2021-01-14 2022-07-19 夏普株式会社 由用户设备执行的方法以及用户设备
US11943056B2 (en) * 2021-09-24 2024-03-26 Qualcomm Incorporated Flexible frequency domain resource allocation for sidelink
CN117560124A (zh) * 2022-08-02 2024-02-13 大唐移动通信设备有限公司 资源确定方法、装置、终端及网络侧设备
WO2024098417A1 (zh) * 2022-11-11 2024-05-16 深圳传音控股股份有限公司 资源处理方法、通信设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018030864A1 (en) * 2016-08-11 2018-02-15 Samsung Electronics Co., Ltd. Method and apparatus of data transmission in next generation cellular networks
CN108307518A (zh) * 2017-01-13 2018-07-20 华硕电脑股份有限公司 用于控制信道与数据信道之间的时序关系的方法和设备
CN108702267A (zh) * 2015-09-30 2018-10-23 诺基亚技术有限公司 短物理上行链路共享信道布置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019182423A1 (en) * 2018-03-23 2019-09-26 Samsung Electronics Co., Ltd. Method and apparatus for transmitting downlink control information in wireless communication system
JP7198832B2 (ja) * 2018-04-06 2023-01-04 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 帯域幅部分の切り替え

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108702267A (zh) * 2015-09-30 2018-10-23 诺基亚技术有限公司 短物理上行链路共享信道布置
WO2018030864A1 (en) * 2016-08-11 2018-02-15 Samsung Electronics Co., Ltd. Method and apparatus of data transmission in next generation cellular networks
CN108307518A (zh) * 2017-01-13 2018-07-20 华硕电脑股份有限公司 用于控制信道与数据信道之间的时序关系的方法和设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Summary of 7.1.3.1.4 (DCI contents and formats)", 3GPP DRAFT; R1-1805572, 20 April 2018 (2018-04-20), Sanya, China, pages 1 - 18, XP051427616 *
ERICSSON: "Summary of offline discussion on 7.1.3.1.4 (DCI contents and formats) part II", 3GPP DRAFT; R1-1805638, 20 April 2018 (2018-04-20), Sanya, China, pages 1 - 3, XP051427675 *
WILUS INC: "Remaining Issues on DCI contents and formats", 3GPP DRAFT; R1-1807233, 25 May 2018 (2018-05-25), Busan, Korea, pages 1 - 9, XP051462973 *

Also Published As

Publication number Publication date
US20220140968A1 (en) 2022-05-05
CN111565461A (zh) 2020-08-21

Similar Documents

Publication Publication Date Title
WO2020164452A1 (zh) 由用户设备执行的方法以及用户设备
EP3641456B1 (en) Control information transmission method and device
WO2020147775A1 (zh) 由用户设备执行的方法以及用户设备
WO2021008587A1 (zh) 由用户设备执行的方法以及用户设备
US20210227540A1 (en) Mobile communications network, communications device and methods
WO2020221241A1 (zh) 由用户设备执行的方法以及用户设备
WO2020135417A1 (zh) 由用户设备执行的方法以及用户设备
WO2020029863A1 (zh) 由用户设备执行的方法以及用户设备
WO2012149848A1 (zh) 一种数据传输的方法、***和设备
WO2020253770A1 (zh) 由用户设备执行的方法以及用户设备
WO2020088514A1 (zh) 由用户设备执行的方法以及用户设备
WO2020169067A1 (zh) 由用户设备执行的方法以及用户设备
WO2020135320A1 (zh) 由用户设备执行的方法以及用户设备
WO2021057960A1 (zh) 由用户设备执行的方法以及用户设备
WO2021160033A1 (zh) 由用户设备执行的方法以及用户设备
WO2020192695A1 (zh) 由用户设备执行的方法
WO2020029228A1 (zh) 解调参考信号的资源分配方法和基站
WO2022068685A1 (zh) 由用户设备执行的方法以及用户设备
WO2021204191A1 (zh) 由用户设备执行的方法以及用户设备
WO2020063478A1 (zh) 由用户设备执行的方法以及用户设备
WO2021228136A1 (zh) 由用户设备执行的方法以及用户设备
WO2021160032A1 (zh) 由用户设备执行的方法以及用户设备
WO2022151620A1 (zh) 资源调度的方法和通信设备
WO2021238757A1 (zh) 由用户设备执行的方法以及用户设备
WO2021088486A1 (zh) 由用户设备执行的方法以及用户设备

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: 20755779

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: 20755779

Country of ref document: EP

Kind code of ref document: A1