Method performed by a user equipment and the user equipment
By improving the DCI size alignment process, user equipment can efficiently and unambiguously determine the DCI size related to 5G V2X, solving the problem of difficulty in aligning different DCI format sizes in 5G, and achieving the correct processing and reception of DCI information.
Patent Information
- Application Number
- CN202010091898.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-02-13
- Publication Date
- 2025-06-13
- Estimated Expiration
- 2040-02-13
AI Technical Summary
In 5G, how to effectively handle size alignment of different DCI formats, especially the introduction of new DCI formats in 5G V2X, resulting in size alignment difficulties.
By improving the DCI size alignment process, user equipment can efficiently and unambiguously determine the DCI size associated with 5G V2X. The specific method includes determining the DCI format size in the DCI format collection and filling the DCI format if necessary to make its load size aligned with other DCI formats.
It realizes efficient and unambiguous DCI size alignment in 5G V2X, ensuring that user equipment can correctly process and receive DCI information.
Smart Images

Figure CN113259998B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a method executed by a user equipment and the user equipment. Background Art
[0002] There are problems to be solved regarding how to align the sizes of different DCI formats in 5G.
[0003] In addition, in 5G V2X, due to the introduction of new DCI formats (such as DCI format 3_0 and DCI format 3_1), how to handle the sizes of the new DCI formats (such as whether the sizes of the new DCI formats need to be aligned with the sizes of the existing DCI formats in 5G and how to perform the alignment, etc.) is a problem to be solved.
[0004] Prior Art Documents
[0005] Non-Patent Documents
[0006] Non-Patent Document 1: RP-152293, New WI proposal: Support for V2V services based on LTE sidelink
[0007] Non-Patent Document 2: RP-170798, New WID on 3GPP V2X Phase 2
[0008] Non-Patent Document 3: RP-170855, New WID on New Radio Access Technology
[0009] Non-Patent Document 4: RP-190766, New WID on 5G V2X with NR sidelink Summary of the Invention
[0010] To solve at least part of the above problems, the present invention provides a method executed by a user equipment and the user equipment, which improves the DCI size alignment process so that the UE can efficiently and unambiguously determine the sizes of DCIs related to 5G V2X.
[0011] According to the present invention, a method executed by a user equipment is proposed, which is characterized by including:
[0012] Determining the sizes of one or more DCI formats in the DCI format set S and receiving DCIs.
[0013] Preferably, the DCI format set S includes at least one of DCI format 3_0 and DCI format 3_1.
[0014] Preferably, the UE is configured with at least one of SL-RNTI, SL-CS-RNTI, SL-L-CS-RNTI, and SL SPS V-RNTI.
[0015] Preferably, if the UE is configured to monitor DCI format 3_0 and DCI format 3_1, and the number of information bits of DCI format 3_1 is less than the payload size of DCI format 3_0, then zeros are added to DCI format 3_1 until its payload size is equal to the payload size of DCI format 3_0.
[0016] Preferably, if the DCI format 3_0 padding condition is satisfied, a DCI format 3_0 padding operation is performed.
[0017] Preferably, the DCI format 3_0 padding condition is that the UE is configured to monitor DCI format 3_0 and d is not equal to any value of the elements in set T others in the set.
[0018] Preferably, the DCI format 3_0 padding operation is to add zeros to DCI format 3_0 until its payload size is equal to the value of the smallest element in set T others that is greater than d.
[0019] Preferably, if the DCI format 3_1 padding condition is satisfied, a DCI format 3_1 padding operation is performed.
[0020] Preferably, the DCI format 3_1 padding condition is that the UE is configured to monitor DCI format 3_1 and d is not equal to any value of the elements in set T others in the set.
[0021] Preferably, the DCI format 3_1 padding operation is to add zeros to DCI format 3_1 until its payload size is equal to the value of the smallest element in set T others that is greater than d.
[0022] Preferably, if the UE is configured to monitor DCI format 3_0, then d is the size of DCI format 3_0 before resizing.
[0023] Preferably, if the UE is not configured to monitor DCI format 3_0 and the UE is configured to monitor DCI format 3_1, then d is the size of DCI format 3_1 before resizing.
[0024] Preferably, the set T others is a set of the sizes of all other DCI formats in the DCI format set S except DCI format 3_0 (if it exists) and DCI format 3_1 (if it exists).
[0025] In addition, according to the present invention, a user equipment is provided, including: a processor; and a memory storing instructions, wherein the instructions, when run by the processor, execute the above-mentioned method.
[0026] Therefore, the present invention provides a method, by improving the DCI size alignment process, enabling the UE to efficiently and unambiguously determine the size of the DCI related to 5G V2X. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] Through the following detailed description in conjunction with the drawings, the above and other features of the present invention will become more obvious, wherein:
[0028] Figure 1 is a flowchart showing a method executed by a user equipment according to Embodiment 1 of the present invention.
[0029] Figure 2 shows a block diagram of a user equipment UE involved in the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0030] The present invention will be elaborated in detail below in conjunction with the drawings and specific embodiments. It should be noted that the present invention should not be limited to the specific embodiments described below. In addition, for the sake of simplicity, the detailed description of well-known technologies not directly related to the present invention is omitted to prevent confusion in the understanding of the present invention.
[0031] The following takes the 5G mobile communication system and its subsequent evolved versions as an example application environment, and specifically describes multiple embodiments according to the present invention. However, it should be pointed out that the present invention is not limited to the following embodiments, but is applicable to more other wireless communication systems, such as communication systems after 5G and 4G mobile communication systems before 5G, etc.
[0032] Some terms related to the present invention are described below. Unless otherwise specified, the terms related to the present invention adopt the definitions herein. The terms given by the present invention may adopt different naming methods in LTE, LTE-Advanced, LTE-Advanced Pro, NR, and subsequent communication systems, but the present invention adopts unified terms, which can be replaced by the terms adopted in the corresponding systems when applied to specific systems.
[0033] 3GPP: 3rd Generation Partnership Project, the Third Generation Partnership Project
[0034] AGC: Automatic Gain Control, Automatic Gain Control
[0035] AL: Aggregation Level, aggregation level
[0036] AS: Access Stratum, access stratum
[0037] BWP: Bandwidth Part, bandwidth part
[0038] CA: Carrier Aggregation, carrier aggregation
[0039] CCE: control-channel element, control channel element
[0040] CORESET: control-resource set, control resource set
[0041] CP: Cyclic Prefix, cyclic prefix
[0042] CP-OFDM: Cyclic Prefix Orthogonal Frequency Division Multiplexing, cyclic prefix orthogonal frequency division multiplexing
[0043] CRB: Common Resource Block, common resource block
[0044] CRC: Cyclic Redundancy Check, cyclic redundancy check
[0045] CSI: Channel-state Information, channel state information
[0046] CSS: Common Search Space, common search space
[0047] DC: Dual Connectivity, dual connectivity
[0048] DCI: Downlink Control Information, downlink control information
[0049] DFN: Direct Frame Number, direct frame number
[0050] DFT-s-OFDM: Discrete Fourier Transformation Spread OrthogonalFrequency Division Multiplexing, discrete Fourier transform spread orthogonal frequency division multiplexing
[0051] DL: Downlink, downlink
[0052] DL-SCH: Downlink Shared Channel, downlink shared channel
[0053] DM-RS: Demodulation reference signal, demodulation reference signal
[0054] eMBB: Enhanced Mobile Broadband, enhanced mobile broadband communication
[0055] eNB: E-UTRAN Node B, E-UTRAN Node B
[0056] E-UTRAN: Evolved UMTS Terrestrial Radio Access Network, evolved UMTS terrestrial radio access network
[0057] FDD: Frequency Division Duplex, frequency division duplex
[0058] FDRA: Frequency Domain Resource Assignment, frequency domain resource assignment
[0059] FR1: Frequency Range 1, frequency range 1
[0060] FR2: Frequency Range 1, frequency range 2
[0061] GLONASS: GLObal NAvigation Satellite System, global navigation satellite system
[0062] gNB: NR Node B, NR Node B
[0063] GNSS: Global Navigation Satellite System, global navigation satellite system
[0064] GPS: Global Positioning System, global positioning system
[0065] HARQ: Hybrid Automatic Repeat Request, hybrid automatic repeat request
[0066] ID: Identity (or Identifier), identity, identifier
[0067] IE: Information Element, information element
[0068] IP: Internet Protocol, Internet protocol
[0069] LCID: Logical Channel ID, logical channel identifier
[0070] LTE: Long Term Evolution, long term evolution
[0071] LTE-A: Long Term Evolution-Advanced, long term evolution-advanced
[0072] MAC: Medium Access Control, medium access control
[0073] MAC CE: MAC Control Element, MAC control element
[0074] MCG: Master Cell Group, master cell group
[0075] MIB: Master Information Block, master information block
[0076] MIB-SL: Master Information Block-Sidelink, master information block-sidelink
[0077] MIB-SL-V2X: Master Information Block-Sidelink-V2X, master information block-sidelink-vehicle to everything
[0078] MIB-V2X: Master Information Block-V2X, master information block-vehicle to everything
[0079] mMTC: massive Machine Type Communication, massive machine type communication
[0080] NAS: Non-Access-Stratum, non-access stratum
[0081] NDI: New Data Indicator, new data indicator
[0082] NR: New Radio, new radio
[0083] NUL: Normal Uplink, normal uplink
[0084] OFDM: Orthogonal Frequency Division Multiplexing, orthogonal frequency division multiplexing
[0085] PBCH: Physical Broadcast Channel, physical broadcast channel
[0086] PDCCH: Physical Downlink Control Channel, physical downlink control channel
[0087] PDCP: Packet Data Convergence Protocol, packet data convergence protocol
[0088] PDSCH: Physical Downlink Shared Channel, physical downlink shared channel
[0089] PSBCH: Physical Sidelink Broadcast Channel, physical sidelink broadcast channel
[0090] PSCCH: Physical Sidelink Control Channel, physical sidelink control channel
[0091] PSFCH: Physical Sidelink Feedback Channel, physical sidelink feedback channel
[0092] PSSCH: Physical Sidelink Shared Channel, physical sidelink shared channel
[0093] PRB: Physical Resource Block, physical resource block
[0094] PSS: Primary Synchronization Signal, primary synchronization signal
[0095] PSS-SL: Primary Synchronization Signal for Sidelink, primary synchronization signal for sidelink
[0096] PSSS: Primary Sidelink Synchronization Signal, primary sidelink synchronization signal
[0097] PTAG: Primary Timing Advance Group, the primary timing advance group
[0098] PUSCH: Physical uplink shared channel, the physical uplink shared channel
[0099] PUCCH: Physical uplink control channel, the physical uplink control channel
[0100] QCL: Quasi co-location, quasi co-location
[0101] QoS: Quality of Service, quality of service
[0102] QZSS: Quasi-Zenith Satellite System, the quasi-zenith satellite system
[0103] RAR: Random Access Response, random access response
[0104] RB: Resource Block, resource block
[0105] RE: Resource Element, resource element
[0106] REG: resource-element group, resource element group
[0107] RF: Radio Frequency, radio frequency
[0108] RLC: Radio Link Control, radio link control protocol
[0109] RNTI: Radio-Network Temporary Identifier, radio network temporary identifier
[0110] RRC: Radio Resource Control, radio resource control
[0111] RV: Redundancy Version, redundancy version
[0112] S-BWP: Sidelink Bandwidth Part, sidelink bandwidth part
[0113] S-MIB: Sidelink Master Information Block, sidelink master information block
[0114] S-PSS: Sidelink Primary Synchronization Signal, the direct main synchronization signal
[0115] S-SSB: Sidelink SS / PBCH block, the direct synchronization signal / physical broadcast channel block
[0116] S-SSS: Sidelink Secondary Synchronization Signal, the direct secondary synchronization signal
[0117] SCG: Secondary Cell Group, the secondary cell group
[0118] SCI: Sidelink Control Information, the direct control information
[0119] SCS: Subcarrier Spacing, the subcarrier spacing
[0120] SDAP: Service Data Adaptation Protocol, the service data adaptation protocol
[0121] SFN: System Frame Number, the system frame number
[0122] SIB: System Information Block, the system information block
[0123] SL: Sidelink, the direct link
[0124] SL BWP: Sidelink Bandwidth Part, the direct link bandwidth part
[0125] SL MIB: Sidelink Master Information Block, the direct link master information block
[0126] SL PSS: Sidelink Primary Synchronization Signal, the direct link primary synchronization signal
[0127] SL SS: Sidelink Synchronisation Signal, the direct link synchronization signal
[0128] SL SSID: Sidelink Synchronization Signal Identity (or Sidelink Synchronization Signal Identifier), Sidelink Synchronization Signal Identity
[0129] SL SSB: Sidelink SS / PBCH block, Sidelink Synchronization Signal / Physical Broadcast Channel Block
[0130] SL SSS: Sidelink Secondary Synchronization Signal, Sidelink Secondary Synchronization Signal
[0131] SLSS: Sidelink Synchronisation Signal, Sidelink Synchronization Signal
[0132] SLSS ID: Sidelink Synchronization Signal Identity (or Sidelink Synchronization Signal Identifier), Sidelink Synchronization Signal Identity
[0133] SLSSID: Sidelink Synchronization Signal Identity (or Sidelink Synchronization Signal Identifier), Sidelink Synchronization Signal Identity
[0134] SpCell: Special Cell, Special Cell
[0135] SRS: Sounding Reference Signal, Sounding Reference Signal
[0136] SSB: SS / PBCH block, Synchronization Signal / Physical Broadcast Channel Block
[0137] SSB-SL: SS / PBCH block for Sidelink, Sidelink Synchronization Signal / Physical Broadcast Channel Block
[0138] SSS: Secondary Synchronization Signal, Secondary Synchronization Signal
[0139] SSS-SL: Secondary Synchronization Signal for Sidelink, Sidelink Secondary Synchronization Signal
[0140] SSSB: Sidelink SS / PBCH block, Sidelink Synchronization Signal / Physical Broadcast Channel block
[0141] SSSS: Secondary Sidelink Synchronization Signal, Secondary Sidelink Synchronization Signal
[0142] STAG: Secondary Timing Advance Group, Secondary Timing Advance Group
[0143] Sub-channel: Sub-channel
[0144] SUL: Supplementary Uplink, Supplementary Uplink
[0145] TA: Timing Advance, Timing Advance
[0146] TAG: Timing Advance Group, Timing Advance Group
[0147] TB: Transport Block, Transport Block
[0148] TCP: Transmission Control Protocol, Transmission Control Protocol
[0149] TDD: Time Division Duplex, Time Division Duplex
[0150] TPC: Transmit power control, Transmit power control
[0151] UE: User Equipment, User Equipment
[0152] UL: Uplink, Uplink
[0153] UMTS: Universal Mobile Telecommunications System, Universal Mobile Telecommunications System
[0154] URLLC: Ultra-Reliable and Low Latency Communication, Ultra-Reliable and Low Latency Communication
[0155] USS: UE-specific Search Space, UE-specific Search Space
[0156] V2I: Vehicle-to-Infrastructure, Vehicle-to-Infrastructure
[0157] V2N: Vehicle-to-network, vehicle to network
[0158] V2P: Vehicle-to-Pedestrian, vehicle to pedestrian
[0159] V2V: Vehicle-to-vehicle, vehicle to vehicle
[0160] V2X: Vehicle-to-everything, vehicle to any entity
[0161] VRB: Virtual Resource Block, virtual resource block
[0162] In all embodiments and implementations of the present invention, unless otherwise specified:
[0163] · Optionally, in applicable cases, "send" can be replaced by "transmit".
[0164] · Optionally, "higher layer" can refer to one or more protocol layers or protocol sub-layers above the physical layer. For example, the MAC layer, the RLC layer, the PDCP layer, the PC5 RRC layer, the PC5-S layer, the RRC layer, the V2X layer, the application layer, the V2X application layer, and so on.
[0165] · Optionally, "pre-configuration" can be pre-configured through higher layer protocols / signaling. For example, pre-set (e.g., pre-set according to the specifications of higher layer protocols) in a specific storage location in the UE, or pre-set (e.g., pre-set according to the specifications of higher layer protocols) in a specific storage location accessible by the UE.
[0166] · Optionally, "configuration" can be configured through higher layer protocols / signaling. For example, configured for the UE through RRC signaling.
[0167] · Optionally, time-domain resources can also be referred to as time resources.
[0168] · Optionally, frequency-domain resources can also be referred to as frequency resources.
[0169] · Optionally, "symbol" refers to "OFDM symbol".
[0170] · Optionally, within a time slot, the numbering of OFDM symbols can start from 0. For example, for normal CP, the set of numbers of OFDM symbols within a time slot can be {0, 1, ..., 13}. Another example is that for extended CP, the set of numbers of OFDM symbols within a time slot can be {0, 1, ..., 11}.
[0171] · Optionally, a resource block can refer to a virtual resource block (VRB), or a physical resource block (PRB), or a common resource block (CRB), or a resource block defined in other ways.
[0172] · Optionally, within a resource block, the numbering of subcarriers can start from 0. For example, the set of numbers of subcarriers within a resource block can be {0, 1, ..., 11}.
[0173] · Optionally, "DCI format" refers to the DCI format in the same serving cell configured for the UE.
[0174] · Optionally, "the size of the DCI format" can also be referred to as the payload size of the DCI format, and vice versa.
[0175] · Optionally, "the size of the DCI format" refers to the size of the corresponding DCI format when referring to "the size of the DCI format". For example, in step a, "if the size of DCI format X is equal to the size of DCI format Y, then add a zero-padding bit to the DCI format X", where the "size of DCI format X" mentioned is the size of DCI format X before adding a zero-padding bit to the DCI format X.
[0176] In communication based on D2D (Device to Device) technology, the interface between devices (also known as user equipment, UE) can be called the PC5 interface, and the corresponding transmission link can be called the "direct" or "sidelink" (SL) link at the physical layer to distinguish it from the uplink (UL) link and the downlink (DL) link. Communication based on the SL link can be called SL communication. The SL link based on LTE technology can be called the LTE SL link. The SL link based on NR technology can be called the NR SL link. 5G V2X communication can be based on LTE SL or NR SL. Unless otherwise specified in the following text, "SL" refers to NR SL.
[0177] The physical layer of the SL interface can support one or more modes of transmission in one or more scenarios among in-coverage, out-of-coverage, and partial-coverage scenarios, such as broadcast transmission, groupcast transmission, unicast transmission, and so on.
[0178] For FR1 (Frequency Range 1), the SCS (subcarrier spacing, denoted as Δf, unit: kHz) corresponding to the SL link can be 15 kHz (normal CP), 30 kHz (normal CP), or 60 kHz (normal CP or extended CP); for FR2 (Frequency Range 2), the SCS corresponding to the SL link can be 60 kHz (normal CP or extended CP), or 120 kHz (normal CP). Each SCS corresponds to an SCS configuration (denoted as μ). For example, Δf = 15 kHz corresponds to μ = 0, Δf = 30 kHz corresponds to μ = 1, Δf = 60 kHz corresponds to μ = 2, Δf = 120 kHz corresponds to μ = 3, and so on; another example, for any given μ, Δf = 2 μ.15 kHz. μ can be the SCS configuration of the SL carrier; for example, all SL transmissions in one SL carrier use the same SCS configuration and / or the same CP. μ can be the SCS configuration of the SL BWP (Sidelink Bandwidth Part); for example, all SL transmissions in one SL BWP use the same SCS configuration and / or the same CP. μ can be the SCS configuration of the resource pool; for example, all SL transmissions in one resource pool use the same SCS configuration and / or the same CP.
[0179] Signals and channels related to SL operations can include:
[0180] · SL PSS (Sidelink Primary Synchronization Signal), or S-PSS, or SPSS, or SL-PSS, or PSS-SL, or PSSS (Primary Sidelink Synchronization Signal), etc.
[0181] · SL SSS (Sidelink Secondary Synchronization Signal), or S-SSS, or SSSS (Sidelink Secondary Synchronization Signal), or SL-SSS, or SSS-SL, or SSSS (Secondary Sidelink Synchronization Signal), etc.
[0182] · PSBCH (Physical Sidelink Broadcast Channel).
[0183] · PSCCH (Physical Sidelink Control Channel).
[0184] · PSSCH (Physical Sidelink Shared Channel).
[0185] · PSFCH (Physical Sidelink Feedback Channel).
[0186] The SL PSS, SL SSS, and PSBCH can be organized in a block form in time / frequency resources, such as being called SL SSB (Sidelink Synchronization Signal / PSBCH block, or SSS / PSBCH block, or S-SS / PSBCH block, or S-SSB, or SSB, or SL-SSB, or SSB-SL). The transmission bandwidth of the SL SSB (e.g., 11 resource blocks) can be located within the corresponding SL carrier (e.g., within an SL BWP configured within the SL carrier). The SL PSS and / or SL SSS can carry an SL SSID (Sidelink Synchronization Identity, or Sidelink Synchronization Identifier, or Sidelink Synchronization Signal Identity, or Sidelink Synchronization Signal Identifier, or SL-SSID, or SSID-SL, or SLSSID, or SLSS ID, or S-SSID, etc.), and the PSBCH can carry an SL MIB (Sidelink Master Information Block, or SL-MIB, or S-MIB, or MIB-SL). The SL MIB can contain configuration information of the SL link, such as information related to the direct frame number (or frame number) or direct half-frame number (or half-frame number) or direct sub-frame number (or sub-frame number) or direct time slot number (or time slot number) where the PSBCH (or the corresponding SL SSB) carrying the SL MIB is located.
[0187] On the SL link, the time domain and / or frequency domain resources for transmitting the SL SSB can be configured through high-layer parameters. For example, in the frequency domain, the position of the SL SSB in the frequency domain can be configured through the parameter absoluteFrequencySSB-SL. Another example is that in the time domain, within a period of 16 frames, the number of SL SSBs (e.g., denoted as ) It can be set through the parameter numSSBwithinPeriod-SL. Among them, the index of the slot where the SL SSB with the number (or index) of i S-SSB in a period of 16 frames can be where It can be configured through the parameter timeOffsetSSB-SL, It can be through the parameter configured.
[0188] Sometimes, it can be considered that the time-domain resources and / or frequency-domain resources configured for the SL SSB in the SL carrier correspond to the candidate SL SSB (or called the SL SSB candidate). On the time-domain and / or frequency-domain resources corresponding to a candidate SL SSB, there may be one or more SL SSB transmissions at the same time (for example, from different UEs respectively), or there may be no SL SSB transmission.
[0189] The synchronization source related to SL synchronization (or called synchronization reference, or called synchronization reference source) can include GNSS (Global Navigation Satellite System), gNB, eNB and UE (such as NR UE, such as LTE UE, such as NR UE or LTE UE). A UE as a synchronization source (for example, the UE transmitting the SL SSB) can be called SyncRefUE.
[0190] Examples of GNSS can include GPS (Global Positioning System), GLONASS (Global Navigation Satellite System), BeiDou (Beidou Navigation Satellite System), Galileo (Galileo Navigation Satellite System), QZSS (Quasi-Zenith Satellite System), etc.
[0191] One or more (for example, one) SL BWPs can be configured within the SL carrier. Within each SL BWP, the starting symbol of the SL time-domain resources within a slot can be configured through the parameter startSLsymbols (or the parameter sl-StartSymbol-r16) (for example, record the number of the symbol within a slot as ) The number of symbols of the SL time-domain resource within a time slot can be configured by the parameter lengthSLsymbols (or the parameter sl-LengthSymbols-r16) (for example, denoting the number of symbols as ). The symbols of the SL time-domain resource within a time slot can be referred to as "SL symbols". Denote the set of SL symbols within a time slot as Then For example, if Then the set of SL symbols within a time slot is {7, 8, 9, 10, 11, 12, 13}.
[0192] SL transmission can be performed in a specific resource pool. One or more resource pools can be configured within an SL BWP. Among them, within each resource pool,
[0193] · In the frequency domain, the position of the starting resource block of the starting subchannel of the resource pool within the SL BWP can be configured by the parameter startRB-Subchannel (or the parameter sl-StartRB-Subchannel-r16).
[0194] · In the frequency domain, the number of subchannels occupied by the resource pool (denoted as ) can be configured by the parameter numSubchannel (or the parameter sl-NumSubchannel-r16). The subchannels can be continuous in the frequency domain.
[0195] · In the frequency domain, each subchannel can be composed of one or more resource blocks. The specific number of resource blocks (referred to as the size of the subchannel, for example, denoted as n subChannelsize ) can be configured by the parameter subchannelsize (or the parameter sl-SubchannelSize-r16). The n subChannelSize resource blocks can be continuous in the frequency domain.
[0196] · In the frequency domain, in ascending order of frequency, the subchannels within a resource pool can be numbered 0, 1, ……, where the subchannel numbered i can be referred to as "subchannel i"
[0197] · In the time domain, one or more time slots that periodically appear and are available for (or belong to) the resource pool can be configured through the parameter timeresourcepool (or the parameter sl-TimeResource-r16) (e.g., in the form of a time slot bitmap), where the size of the period can be configured through the parameter periodResourcePool.
[0198] The allocation methods of resources related to SL operations (such as time domain resources, frequency domain resources, and code domain resources) can be classified as follows:
[0199] · Mode 1: The base station schedules the SL resources for SL transmission.
[0200] · Mode 2: The UE determines the SL resources for SL transmission (i.e., the base station does not participate in the scheduling of SL resources). For example, the UE performing the SL transmission operation independently determines the SL resources for SL transmission.
[0201] The UE can schedule the transmission of data through SCI (Sidelink Control Information). SL operations can support "two-stage SCI", where the first-stage SCI can include information such as resource reservation and / or resource allocation, so that all UEs monitoring the SL link can detect the resource reservation and / or resource allocation situation; the second-stage SCI can include other information, such as information related to HARQ feedback, etc. Unless otherwise specified in the following text, when "SCI" is mentioned alone, it can include only the first-stage SCI, only the second-stage SCI, or both the first-stage SCI and the second-stage SCI. st -stage SCI) can include information such as resource reservation and / or resource allocation to facilitate the detection (sensing) of resource reservation and / or resource allocation by all UEs monitoring the SL link; the second-stage SCI (2 nd -stage SCI) can include other information, such as information related to HARQ feedback, etc. Unless otherwise specified in the following text, when "SCI" is mentioned alone, it can include only the first-stage SCI, only the second-stage SCI, or both the first-stage SCI and the second-stage SCI.
[0202] The format of the first-stage SCI can be SCI format 0-1 (or written as "SCI format 0_1"). The following are some examples of the information that can be included in SCI format 0-1:
[0203] · Priority.
[0204] · Frequency resource assignment.
[0205] · Time resource assignment.
[0206] · Resource reservation period.
[0207] · Second-stage SCI format (2 nd -stage SCI format).
[0208] The format of the second-stage SCI can be SCI format 0 - 2 (or written as "SCI format 0_2"). The following are some examples of the information that can be included in SCI format 0 - 2:
[0209] · Source Layer-1 ID (or Layer-1 Source ID, layer-1 source identifier, or Physical Layer Source ID, physical layer source identifier, or (when the context is clear) Source ID, source identifier).
[0210] · Destination Layer-1 ID (or Layer-1 Destination ID, layer-1 destination identifier, or Physical Layer Destination ID, physical layer destination identifier, or (when the context is clear) Destination ID, destination identifier).
[0211] · HARQ Process ID, or HARQ Process Number.
[0212] · New Data Indicator (NDI).
[0213] · Redundancy Version (RV).
[0214] The first-stage SCI can be carried on the PSCCH. The second-stage SCI can be multiplexed with the data to be transmitted on the PSSCH associated with (or scheduled by) the PSCCH. The PSCCH and its associated PSSCH can be multiplexed in the time domain and / or frequency domain resources allocated for SL transmission in a certain way (for example, the subchannel where the starting resource block of the PSCCH is located is the starting subchannel of its associated PSSCH. Another example is that the starting resource block of the PSCCH is the starting resource block of the starting subchannel of its associated PSSCH). In addition, it can be considered that the first-stage SCI and / or the corresponding second-stage SCI schedules the PSSCH (or schedules the transmission of the PSSCH, or schedules the transmission of the TB carried in the PSSCH).
[0215] For a specific SL transmission including PSCCH and / or PSSCH, the sender can be referred to as the TX UE, and the receiver can be referred to as the RX UE. If the SL transmission is a groupcast transmission or a unicast transmission, and HARQ feedback is enabled, the PSFCH sent by the RX UE can carry feedback on the PSCCH and / or PSSCH sent by the TX UE, where the feedback can be referred to as "HARQ-ACK information". In some configurations, the HARQ-ACK information can be an affirmative acknowledgement (ACK) or a negative acknowledgement (NACK, or NAK, Negative Acknowledgement); in other configurations, the HARQ-ACK information can only contain NACK.
[0216] In the time domain, PSFCH resources can appear periodically in a resource pool, for example, configured by the parameter sl-PSFCH-Period-r16 (for example, configured as 1 time slot, or 2 time slots, or 4 time slots). A special value of the parameter sl-PSFCH-Period-r16 (for example, 0) can be used to indicate that there are no PSFCH resources configured in the corresponding resource pool and / or to indicate that HARQ feedback is disabled in the corresponding resource pool. The time slots related to the PSFCH period can be "logical time slots", that is, only including the time slots belonging to the corresponding resource pool; for example, if time slot 0 and time slot 5 in a certain frame belong to the time domain resources of a certain resource pool, and time slots 1, 2, 3, and 4 do not belong to the time domain resources of this resource pool, then sl-PSFCH-Period-r16 = 1 can indicate the existence of PSFCH resources in the above-mentioned time slot 0 and time slot 5.
[0217] In the frequency domain, PSFCH resources can be configured in an RB set (for example, a set of consecutive PRBs, or a set of partially or fully discontinuous PRBs), for example, configured by the parameter sl-PSFCH-RB-Set.
[0218] On the other hand, 5G (or referred to as NR, or 5G NR) can schedule downlink transmissions on the PDSCH (Physical Downlink Shared Channel) and uplink transmissions on the PUSCH (Physical Uplink Shared Channel) through DCI (Downlink Control Information). In 5G V2X, the transmissions of PSCCH and PSSCH can also be scheduled additionally through DCI.
[0219] 5G supports multiple DCI formats. For example, it may include the DCI formats shown in Table 1. The CRC of each DCI format 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 of the DCI format used to indicate paging can be scrambled with a P-RNTI.
[0220] Table 1 Examples of DCI Formats Supported by 5G
[0221]
[0222] 5G's DCI can be carried on the PDCCH (Physical Downlink Control Channel). A PDCCH can be composed of one or more CCEs (control-channel elements), and a CCE can in turn be composed of multiple (e.g., 6) REGs (resource-element groups), and REGs are defined within a CORESET (control-resource set). A CORESET contains multiple resource blocks in the frequency domain (each resource block consists of 12 consecutive subcarriers in the frequency domain) and one or more (e.g., 1, or 2, or 3) OFDM symbols in the time domain.
[0223] A UE can monitor the PDCCH transmissions of a base station on one or more search space sets, where each search space set can correspond to a set of PDCCH candidates. The UE determines whether there is a PDCCH sent to itself by performing blind detection on the time-frequency resources corresponding to the PDCCH candidates to be monitored.
[0224] Search space sets can be divided into CSS (Common Search Space) sets and USS (UE-specific search space) sets. For example, specifically, one or more of the following search space sets can be defined:
[0225] · Type 0 - PDCCH CSS set. For example, it is configured by the pdcch-ConfigSIB1 parameter in the MIB, or by the searchSpaceSIB1 parameter in PDCCH-ConfigCommon, or by the searchSpaceZero parameter in PDCCH-ConfigCommon. The RNTI used to scramble the CRC of the corresponding DCI format may include SI-RNTI. It can be used for the primary cell of the MCG (Master Cell Group).
[0226] · Type 0A - PDCCH CSS set. For example, it is configured by the searchSpaceOtherSystemInformation parameter in PDCCH-ConfigCommon. The RNTI used to scramble the CRC of the corresponding DCI format may include SI-RNTI. It can be used for the primary cell of the MCG.
[0227] · Type 1 - PDCCH CSS set. For example, it is configured by the ra-SearchSpace parameter in PDCCH-ConfigCommon. The RNTI used to scramble the CRC of the corresponding DCI format may include RA-RNTI, TC-RNTI. It can be used for the primary cell.
[0228] · Type 2 - PDCCH CSS set. For example, it is configured by the pagingSearchSpace parameter in PDCCH-ConfigCommon. The RNTI used to scramble the CRC of the corresponding DCI format may include P-RNTI. It can be used for the primary cell of the MCG.
[0229] · Type 3 - PDCCH CSS set. For example, it is configured by the SearchSpace in PDCCH-Config, where searchSpaceType = common. The RNTI used to scramble the CRC of the corresponding DCI format may include INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, C-RNTI, MCS-C-RNTI, and CS-RNTI, where C-RNTI, MCS-C-RNTI, and CS-RNTI can only be used for the primary cell.
[0230] · USS set. For example, it is configured through the SearchSpace in PDCCH-Config, where searchSpaceType = ue-Specific. The RNTI used to scramble the CRC of the corresponding DCI format may include C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, CS-RNTI, SL-RNTI, SL-CS-RNTI, and SL-L-CS-RNTI.
[0231] Sometimes, the concept of "search space" can be used. A search space can be associated with a search space set. For example, a search space can be defined as a part of a search space set, or a subset (e.g., corresponding to PDCCH candidates with the same aggregation level in a group of PDCCH candidates); another example is that a search space is equivalent to a search space set; or the relationship between the search space and the search space set can be defined in other ways.
[0232] Since the UE listens for DCI in a specific search space, the definition of "DCI format" can be considered related to the search space where the DCI is listened for. For example, sometimes (e.g., when calculating the number of DCI sizes that need to be listened for), "DCI format x listened for in search space 1" and "DCI format x listened for in search space 2" can be considered two different DCI formats.
[0233] There can be certain restrictions on the DCI formats that can be listened for in a search space. For example, a UE-specific search space can be configured to listen for DCI format 0_0 and DCI format 1_0, or configured to listen for DCI format 0_1 and DCI format 1_1, but cannot be configured to listen for DCI format 0_0, DCI format 1_0, DCI format 0_1, and DCI format 1_1.
[0234] Some DCI formats (such as DCI format 3_0, and DCI format 3_1, etc.) are only configured to be listened for in the user-specific search space and not in the common search space. For such a DCI format (denoted as DCI format X), "the UE is configured to listen for DCI format X" is equivalent to "the UE is configured to listen for DCI format X in a user-specific search space".
[0235] When the UE blindly detects PDCCH candidates, it needs to assume a DCI size. Due to processing capacity limitations, the UE can only listen for a certain number of DCI sizes in each time slot. For example, the total number of different DCI sizes configured in the cell does not exceed 4; another example is that the total number of different DCI sizes related to C-RNTI (e.g., the CRC of the corresponding DCI format is scrambled by C-RNTI) configured in the cell does not exceed 3.
[0236] The definitions of the various fields in a DCI format (e.g., whether the field appears, and the size of the field, etc.) can vary depending on the RNTI that scrambles the CRC of the DCI format. On the other hand, the DCI format can be designed such that when scrambling the CRC of a DCI format with two or more or all applicable RNTIs respectively, the size of the DCI format is the same. For example, Table 2 and Table 3 respectively show an example of the definitions of the various fields in DCI format 1_0 when scrambling its CRC with SI-RNTI and RA-RNTI; it can be seen that by defining different sizes of the "reserved bit" fields for these two cases respectively, the size of DCI format 1_0 can be uniformly written as 28 + d FDRA , where d FDRA is the size of the frequency-domain resource allocation field. The value of d FDRA can be related to the search space for monitoring the DCI format.
[0237] The definitions of the various fields in a DCI format can also be related to other predefined, configured, or preconfigured information. To determine the size of a DCI format (e.g., denoted as DCI format X), it is first necessary to "determine DCI format X", that is, determine each field that appears in the DCI format X according to the predefined, preconfigured, or configured information (e.g., determine whether the field appears, and the size of the field, etc.). Optionally, after "determining DCI format X", the size of the DCI format X can be referred to as the "number of information bits" of the DCI format X. Optionally, after any DCI size alignment operation (e.g., adding zero-padding bits) is performed on the DCI format X, the size of the DCI format X is no longer referred to as its "number of information bits".
[0238] To minimize the number of total DCI sizes in a cell, the DCI format can be designed such that the size of the same DCI format monitored in two or more common search spaces is the same, and / or such that the size of the same DCI format monitored in two or more user-specific search spaces is the same. At this time, optionally, when referring to the size of a DCI format x, the specific search space can be ignored, for example, it can be said "the size of DCI format x monitored in the common search space", or it can be said "the size of DCI format x monitored in the UE-specific search space".
[0239] An example of the definition of DCI format 1_0 with its CRC scrambled by SI-RNTI in Table 2
[0240]
[0241] An example of the definition of DCI format 1_0 with its CRC scrambled by RA-RNTI
[0242]
[0243] To further reduce the number of total DCI sizes in a cell, DCI size alignment can be performed when necessary, for example, by performing any one or more of the following steps or sub-steps or sub-sub-steps or sub-sub-sub-steps:
[0244]
[0245]
[0246]
[0247]
[0248]
[0249]
[0250]
[0251]
[0252]
[0253] Among them,
[0254] · Optionally, step 0 includes sub-steps 0-0, 0-1, 0-2, and 0-3.
[0255] · Optionally, step 1 includes sub-steps 1-0, 1-1, 1-2, 1-3, and 1-4.
[0256] · Optionally, step 2 includes sub-steps 2-0, 2-1, 2-2, 2-3, and 2-4.
[0257] · Optionally, step 2A includes sub-steps 2A-0, 2A-1, 2A-2, 2A-3, and 2A-4.
[0258] · Optionally, step 3 includes sub-step 3-0.
[0259] · Optionally, step 4 includes sub-steps 4A, 4B, and 4C. Among them,
[0260] ◆Optionally, sub-step 4A includes sub-sub-steps 4A-0, 4A-1, 4A-2, 4A-3, 4A-4, and 4A-5.
[0261] ◆Optionally, sub-step 4B includes sub-sub-step 4B-0. Among them,
[0262] ο Optionally, sub-sub-step 4B-0 includes sub-sub-sub-steps 4B-0-0 and 4B-0-1.
[0263] ◆Optionally, sub-step 4C includes sub-sub-step 4C-0,
[0264] ο Optionally, sub-sub-step 4C-0 includes sub-sub-sub-steps 4C-0-0 and 4C-0-1.
[0265] · Optionally, the execution order of each step or sub-step or sub-sub-step or sub-sub-sub-step can be adjusted. For example, sub-step 4A-1 can be adjusted to be placed after any one of the sub-steps or sub-sub-steps or sub-sub-sub-steps included in step 4, and sub-step 4A-2 can be adjusted to be placed after any one of the sub-steps or sub-sub-steps or sub-sub-sub-steps included in step 4.
[0266] · Optionally, sub-sub-step 4A-1 can be described as "repeat sub-step 2-2".
[0267] · Optionally, sub-sub-step 4A-2 can be described as "repeat sub-step 2A-2".
[0268] [Embodiment 1]
[0269] The following combines Figure 1 to illustrate the method executed by the user equipment in Embodiment 1 of the present invention.
[0270] Figure 1 is a flowchart showing the method executed by the user equipment according to Embodiment 1 of the present invention.
[0271] As Figure 1 shown, in Embodiment 1 of the present invention, the steps executed by the user equipment UE include: step S101 and step S103.
[0272] Specifically, in step S101, determine the size of one or more DCI formats in the DCI format set S.
[0273] Among them,
[0274] · Optionally, the DCI format set S includes all DCI formats configured for the UE to monitor. Among them,
[0275] Optionally, at least one of DCI format 3_0 and DCI format 3_1 is included in all DCI formats configured for the UE to monitor.
[0276] · Optionally, the set S of DCI formats includes at least one of DCI format 3_0 and DCI format 3_1.
[0277] · Optionally, the set S of DCI formats only includes the DCI formats configured for the UE to monitor. For example, if the UE is not configured to monitor DCI format 3_1, then the set S of DCI formats does not include DCI format 3_1.
[0278] · Optionally, the set S of DCI formats includes any one or more of the following DCI formats:
[0279] ◆ DCI format 0_0.
[0280] ◆ DCI format 0_1.
[0281] ◆ DCI format 0_2.
[0282] ◆ DCI format 1_0.
[0283] ◆ DCI format 1_1.
[0284] ◆ DCI format 1_2.
[0285] ◆ DCI format 2_0.
[0286] ◆ DCI format 2_1.
[0287] ◆ DCI format 2_2.
[0288] ◆ DCI format 2_3.
[0289] ◆ DCI format 2_4.
[0290] ◆ DCI format 3_0.
[0291] . DCI format 3_1.
[0292] · Optionally, one or more DCI formats in the set S of DCI formats are configured to be monitored in the common search space.
[0293] · Optionally, one or more DCI formats in the set S of DCI formats are configured to be monitored in the user-specific search space.
[0294] · Optionally, one or more DCI formats in the set S of DCI formats are configured to be monitored both in the common search space and in the user-specific search space. Among them,
[0295] Optionally, if a DCI format (e.g., denoted as DCI format X) is configured to be monitored in both the common search space and the UE-specific search space, the DCI format X monitored in the common search space and the DCI format X monitored in the UE-specific search space can be considered as two different DCI formats (e.g., at least from the perspective of calculating the DCI format size).
[0296] · Optionally, for a DCI format (e.g., denoted as DCI format X) in the DCI format set S, if the "condition for monitoring DCI format X" is satisfied, it can be determined that the UE is configured to monitor DCI format X.
[0297] ◆ For example, optionally, the "condition for monitoring DCI format 3_0" may include any one or more of the following (any combination in the "AND" or "OR" manner as applicable):
[0298] ο The UE is configured with configuration information for SL communication for network scheduling.
[0299] ο The UE is configured with the value of SL-RNTI.
[0300] ο The UE is configured with the value of SL-CS-RNTI.
[0301] ο The DCI format set configured in one or more search spaces (or one or more search space sets) configured by the UE contains DCI format 3_0 (e.g., the value of the parameter dci-FormatsSL-r16 is "formats3-0", or the value of the parameter dci-FormatsSL-r16 is "formats3-0-And-3-1").
[0302] ◆ For another example, optionally, the "condition for monitoring DCI format 3_1" may include any one or more of the following (any combination in the "AND" or "OR" manner as applicable):
[0303] ο The UE is configured with configuration information for SL communication for network scheduling.
[0304] ο The UE is configured with the value of SL-L-CS-RNTI.
[0305] ο The UE is configured with the value of SL Semi-Persistent Scheduling V-RNTI (or referred to as SL SPS V-RNTI).
[0306] ο The set of DCI formats configured in one or more search spaces (or one or more sets of search spaces) configured by the UE includes DCI format 3_1 (for example, the value of the parameter dci-FormatsSL-r16 is "formats3-1", or the value of the parameter dci-FormatsSL-r16 is "formats3-0-And-3-1").
[0307] · Optionally, the "determining the size of one or more DCI formats in the set of DCI formats S" includes any one or more of the following:
[0308] ◆ Step 0, or one or more sub-steps of Step 0.
[0309] ◆ Step 1, or one or more sub-steps of Step 1.
[0310] ◆ Step 2, or one or more sub-steps of Step 2.
[0311] ◆ Step 2A, or one or more sub-steps of Step 2A.
[0312] ◆ Step 3, or one or more sub-steps of Step 3.
[0313] ◆ Step 4, or one or more sub-steps of Step 4, where
[0314] ο Optionally, for each sub-step, it includes one or more sub-sub-steps. Where
[0315] ◇ Optionally, for each sub-sub-step, it includes one or more sub-sub-sub-steps.
[0316] ◆ Step S101-0: If the DCI format 3_1 filling condition 1 is satisfied, perform the DCI format 3_1 filling operation 1. Where
[0317] ο Optionally, the "DCI format 3_1 filling condition 1" can be "none", that is, always perform the "DCI format 3_1 filling operation 1".
[0318] ο Optionally, the "DCI format 3_1 filling condition 1" can include any one or more of the following (in the applicable case, combined by "AND" or "OR" as appropriate):
[0319] ◇ The UE is configured to monitor DCI format 3_0.
[0320] ◇ The UE is configured to monitor DCI format 3_0 in a user-specific search space.
[0321] ◇ The UE is configured to monitor DCI format 3_1.
[0322] ◇ The UE is configured to monitor DCI format 3_1 in a user-specific search space.
[0323] ◇ The UE is configured to monitor DCI format 3_0 and / or DCI format 3_1.
[0324] ◇ The number of information bits of DCI format 3_1 is less than the number of information bits of DCI format 3_0.
[0325] ◇ The number of information bits of DCI format 3_1 is less than the payload size of DCI format 3_0.
[0326] ◇ The payload size of DCI format 3_1 is less than the payload size of DCI format 3_0.
[0327] ο Optionally, the "DCI format 3_1 padding operation 1" may include: adding zeros to the DCI format 3_1 (e.g., adding a number of zero-padding bits after the last field of the DCI format 3_1) until its payload size is equal to the payload size of the DCI format 3_0.
[0328] ◆ Step S101-1: If the DCI format 3_0 padding condition 1 is satisfied, perform the DCI format 3_0 padding operation 1. Wherein,
[0329] ο Optionally, the "DCI format 3_0 padding condition 1" may be "none", that is, always perform the "DCI format 3_0 padding operation 1".
[0330] ο Optionally, the "DCI format 3_0 padding condition 1" may include any one or more of the following (in the case of applicability, combined by "AND" or "OR" arbitrarily):
[0331] ◇ The UE is configured to monitor DCI format 3_0.
[0332] ◇ The UE is configured to monitor DCI format 3_0 in a user-specific search space.
[0333] ◇ The UE is configured to monitor DCI format 3_1.
[0334] ◇ The UE is configured to monitor DCI format 3_1 in a user-specific search space.
[0335] ◇ The UE is configured to monitor DCI format 3_0 and / or DCI format 3_1.
[0336] ◇ The number of information bits of DCI format 3_0 is less than the number of information bits of DCI format 3_1.
[0337] ◇ The number of information bits in DCI format 3_0 is less than the payload size of DCI format 3_1.
[0338] ◇ The payload size of DCI format 3_0 is less than the payload size of DCI format 3_1.
[0339] ο Optionally, the "DCI format 3_0 padding operation 1" may include: adding zeros to the DCI format 3_0 (for example, adding a number of zero-padding bits after the last field of the DCI format 3_0) until its payload size is equal to the payload size of the DCI format 3_1.
[0340] ◆ Step S101-2: If the DCI format 3_0 padding condition 2 is satisfied, perform the DCI format 3_0 padding operation 2. Among them,
[0341] ο Optionally, the "DCI format 3_0 padding condition 2" may be "none", that is, always perform the "DCI format 3_0 padding operation 2".
[0342] ο Optionally, the "DCI format 3_0 padding condition 2" may include any one or more of the following (in the applicable case, combined by "AND" or "OR" arbitrarily):
[0343] ◇ The UE is configured to monitor DCI format 3_0.
[0344] ◇ The UE is configured to monitor DCI format 3_0 in a user-specific search space.
[0345] ◇ The UE is configured to monitor DCI format 3_1.
[0346] ◇ The UE is configured to monitor DCI format 3_1 in a user-specific search space.
[0347] ◇ The UE is not configured to monitor DCI format 3_1.
[0348] ◇ The UE is configured to monitor DCI format 3_0 and / or DCI format 3_1.
[0349] ◇ d 1o12 is not equal to any element value in the set T others in.
[0350] ◇ d 1o12 is less than the value of the element with the largest value in the set T others in.
[0351] ο Optionally, the "DCI format 3_0 padding operation 2" may include any one or more of the following:
[0352] ◇Add zeros to the DCI format 3_0 (e.g., add a number of zero-padding bits after the last field of the DCI format 3_0) until its payload size is equal to the value of the smallest element in the set T others greater than d 1012 in
[0353] ◇Add zeros to the DCI format 3_0 (e.g., add a number of zero-padding bits after the last field of the DCI format 3_0) until its payload size is equal to the value of the largest element in the set T others in
[0354] where, optionally, d 1012 can be determined according to any one or more of the following:
[0355] ο If the UE is configured to monitor the DCI format 3_0 and the UE is configured to monitor the DCI format 3_1, then d 1012 = max(D 30 , D 31 ).
[0356] ο If the UE is configured to monitor the DCI format 3_0 and the UE is configured to monitor the DCI format 3_1, then d 1012 = D 30 .
[0357] ο If the UE is configured to monitor the DCI format 3_0 and the UE is configured to monitor the DCI format 3_1, then d 1012 = D 31 .
[0358] ο If the UE is configured to monitor the DCI format 3_0 and the UE is not configured to monitor the DCI format 3_1, then d 1012 = D 30 .
[0359] ο If the UE is configured to monitor the DCI format 3_0, then d 1012 = D 30 .
[0360] ο If the UE is configured to monitor the DCI format 3_0, then d 1012 = D 31 .
[0361] ο d 1012 = D 30 .
[0362] ο d 1012 = D 31 .
[0363] ο d 1012 = D 3031 .
[0364] ◆ Step S101-3: If the DCI format 3_1 filling condition 2 is satisfied, perform the DCI format 3_1 filling operation 2. Among them,
[0365] ο Optionally, the "DCI format 3_1 filling condition 2" can be "none", that is, always perform the "DCI format 3_1 filling operation 2".
[0366] ο Optionally, the "DCI format 3_1 filling condition 2" can include any one or more of the following (in the applicable case, combined by "AND" or "OR" arbitrarily):
[0367] ◇ The UE is configured to monitor DCI format 3_0.
[0368] ◇ The UE is configured to monitor DCI format 3_0 in a user-specific search space.
[0369] ◇ The UE is not configured to monitor DCI format 3_0.
[0370] ◇ The UE is configured to monitor DCI format 3_1.
[0371] ◇ The UE is configured to monitor DCI format 3_1 in a user-specific search space.
[0372] ◇ The UE is configured to monitor DCI format 3_0 and / or DCI format 3_1.
[0373] ◇ d 1013 is not equal to the value of any element in the set T others in.
[0374] ◇ d 1o13 is less than the value of the element with the largest value in the set T others in.
[0375] ο Optionally, the "DCI format 3_1 filling operation 2" can include any one or more of the following:
[0376] ◇ Add zeros to the DCI format 3_1 (for example, add a number of zero-padding bits after the last field of the DCI format 3_1) until its payload size is equal to the smallest element value in the set T others in that is greater than d 1013 in.
[0377] ◇ Add zeros to the DCI format 3_1 (for example, add a number of zero-padding bits after the last field of the DCI format 3_1) until its payload size is equal to the largest element value in the set T others in.
[0378] Optionally, d 1013 can be determined according to any one or more of the following:
[0379] ο If the UE is configured to monitor DCI format 3_1 and the UE is configured to monitor DCI format 3_0, then d 1013 = max(D 31 , D 30 ).
[0380] ο If the UE is configured to monitor DCI format 3_1 and the UE is configured to monitor DCI format 3_0, then d 1013 = D 31 .
[0381] ο If the UE is configured to monitor DCI format 3_1 and the UE is configured to monitor DCI format 3_0, then d 1013 = D 30 .
[0382] ο If the UE is configured to monitor DCI format 3_1 and the UE is not configured to monitor DCI format 3_0, then d 1013 = D 31 .
[0383] ο If the UE is configured to monitor DCI format 3_1, then d 1013 = D 31 .
[0384] ο If the UE is configured to monitor DCI format 3_1, then d 1013 = D 30 .
[0385] ο d 1013 = D 31 .
[0386] ο d 1013 = D 30 .
[0387] ο d 1013 = D 3031 .
[0388] ◆ Step S101-4: If the DCI format 3_0 / 3_1 filling condition 1 is satisfied, perform the DCI format 3_0 / 3_1 filling operation 1. Among them,
[0389] ο Optionally, the "DCI format 3_0 / 3_1 filling condition 1" can be "none", that is, always perform the "DCI format 3_0 filling operation 1".
[0390] Optionally, the "DCI format 3_0 / 3_1 filling condition 1" may include any one or more of the following (in any combination of "AND" or "OR" as applicable):
[0391] ◇ The UE is configured to monitor DCI format 3_0.
[0392] ◇ The UE is configured to monitor DCI format 3_0 in a user-specific search space.
[0393] ◇ The UE is not configured to monitor DCI format 3_0.
[0394] ◇ The UE is configured to monitor DCI format 3_1.
[0395] ◇ The UE is configured to monitor DCI format 3_1 in a user-specific search space.
[0396] ◇ The UE is not configured to monitor DCI format 3_1.
[0397] ◇ The UE is configured to monitor DCI format 3_0 and / or DCI format 3_1.
[0398] ◇ d 1014 is not equal to the value of any element in the set T others in the set T.
[0399] ◇ d 1014 is less than the value of the element with the largest value in the set T others in the set T.
[0400] Optionally, the "DCI format 3_0 / 3_1 filling operation 1" may include any one or more of the following:[[]]END]]
[0401] ◇ Add zeros to the DCI format 3_0 (e.g., add a number of zero-padding bits after the last field of the DCI format 3_0) until its payload size is equal to the smallest element in the set T others in the set T that is greater than d 1014 in the set T.
[0402] ◇ Add zeros to the DCI format 3_0 (e.g., add a number of zero-padding bits after the last field of the DCI format 3_0) until its payload size is equal to the largest element in the set T others in the set T.
[0403] ◇ Add zeros to the DCI format 3_1 (e.g., add a number of zero-padding bits after the last field of the DCI format 3_1) until its payload size is equal to the smallest element in the set T others in the set T that is greater than d 1014 in the set T.
[0404] ◇ Add zeros to the DCI format 3_1 (e.g., add a number of zero-padding bits after the last field of the DCI format 3_1) until its payload size is equal to the value of the largest element in set T others in the set T.
[0405] Optionally, d 1014 can be determined by any one or more of the following:
[0406] ο If the UE is configured to monitor DCI format 3_0 and the UE is configured to monitor DCI format 3_1, then d 1014 = max(D 30 , D 31 ).
[0407] ο If the UE is configured to monitor DCI format 3_0 and the UE is configured to monitor DCI format 3_1, then d 1014 = D 30 .
[0408] ο If the UE is configured to monitor DCI format 3_0 and the UE is configured to monitor DCI format 3_1, then d 1014 = D 31 .
[0409] ο If the UE is configured to monitor DCI format 3_0 and the UE is not configured to monitor DCI format 3_1, then d 1014 = D 30 .
[0410] ο If the UE is not configured to monitor DCI format 3_0 and the UE is configured to monitor DCI format 3_1, then d 1014 = D 31 .
[0411] ο If the UE is configured to monitor DCI format 3_0, then d 1014 = D 30 .
[0412] ο If the UE is configured to monitor DCI format 3_1, then d 1014 = D 31 .
[0413] ο d 1014 = D 30 .
[0414] ο d 1014 = D 31 .
[0415] ο d 1014 = D 3031 .
[0416] Among them,
[0417] ◆ Optionally, T others is a set of sizes of "other DCI formats". Among them,
[0418] ο Optionally, the "other DCI formats" can be defined in any of the following ways:
[0419] ◇ In the DCI format set S, DCI formats other than DCI format 3_0 (if DCI format 3_0 is included in the DCI format set S) and DCI format 3_1 (if DCI format 3_1 is included in the DCI format set S).
[0420] ◇ In the DCI format set S, DCI formats other than DCI format 3_0 (if DCI format 3_0 is included in the DCI format set S) and DCI format 3_1 (if DCI format 3_1 is included in the DCI format set S) that are related to C-RNTI.
[0421] ◇ In the DCI format set S, DCI formats other than DCI format 3_0 and DCI format 3_1.
[0422] ◇ In the DCI format set S, DCI formats other than DCI format 3_0 and DCI format 3_1 that are related to C-RNTI.
[0423] ◇ In the DCI format set S, DCI formats related to C-RNTI.
[0424] ◇ In the DCI formats configured for the UE to monitor, DCI formats other than DCI format 3_0 (if the UE is configured to monitor DCI format 3_0) and DCI format 3_1 (if the UE is configured to monitor DCI format 3_1, for example, monitoring DCI format 3_1 in a user-specific search space).
[0425] ◇ In the DCI formats configured for the UE to monitor, DCI formats other than DCI format 3_0 (if the UE is configured to monitor DCI format 3_0) and DCI format 3_1 (if the UE is configured to monitor DCI format 3_1, for example, monitoring DCI format 3_1 in a user-specific search space) that are related to C-RNTI.
[0426] ◇ In the DCI formats configured for the UE to monitor, DCI formats other than DCI format 3_0 and DCI format 3_1.
[0427] ◇Among the DCI formats configured for the UE to monitor, DCI formats related to C-RNTI other than DCI format 3_0 and DCI format 3_1.
[0428] ◇Among the DCI formats configured for the UE to monitor, DCI formats related to C-RNTI.
[0429] ◇DCI formats other than DCI format 3_0 and DCI format 3_1.
[0430] ◇DCI formats related to C-RNTI other than DCI format 3_0 and DCI format 3_1.
[0431] ◇DCI formats related to C-RNTI.
[0432] ο Optionally, due to DCI format alignment operations, the sizes of one or more DCI formats in the "other DCI formats" may be different in different steps (or sub-steps, or sub-sub-steps, or sub-sub-sub-steps), so T others may be different in different steps (or sub-steps, or sub-sub-steps, or sub-sub-sub-steps).
[0433] ◆ Optionally, D 30 is the size of DCI format 3_0. Among them,
[0434] ο Optionally, due to DCI format alignment operations, D 30 may be different in different steps (or sub-steps, or sub-sub-steps, or sub-sub-sub-steps).
[0435] ο Optionally, D only exists when the UE is configured to monitor DCI format 3_0. 30 exists only then.
[0436] ◆ Optionally, D 31 is the size of DCI format 3_1. Among them,
[0437] ο Optionally, due to DCI format alignment operations, D 31 may be different in different steps (or sub-steps, or sub-sub-steps, or sub-sub-sub-steps).
[0438] ο Optionally, D only exists when the UE is configured to monitor DCI format 3_1. 31 exists only then.
[0439] ◆ Optionally, D 3031 is the size of DCI format 3_0 / 3_1. Among them,
[0440] Optionally, if the UE is configured to monitor DCI format 3_0 and the UE is configured to monitor DCI format 3_1, the "size of DCI format 3_0 / 3_1" refers to the common size of DCI format 3_0 and DCI format 3_1 (e.g., after performing step S101-0; or after performing step S101-1).
[0441] Optionally, if the UE is configured to monitor DCI format 3_0 and the UE is configured to monitor DCI format 3_1, the "size of DCI format 3_0 / 3_1" refers to the larger of the size of DCI format 3_0 and the size of DCI format 3_1.
[0442] Optionally, if the UE is configured to monitor DCI format 3_0 and the UE is not configured to monitor DCI format 3_1, the "size of DCI format 3_0 / 3_1" refers to the size of DCI format 3_0.
[0443] Optionally, if the UE is not configured to monitor DCI format 3_0 and the UE is configured to monitor DCI format 3_1, the "size of DCI format 3_0 / 3_1" refers to the size of DCI format 3_1.
[0444] Optionally, if the UE is configured to monitor DCI format 3_0, the "size of DCI format 3_0 / 3_1" refers to the size of DCI format 3_0 (e.g., according to the definitions of DCI format 3_0 and DCI format 3_1, the size of DCI format 3_1 is always less than (or less than or equal to) the size of DCI format 3_0, so as long as the UE is configured to monitor DCI format 3_0, DCI format 3_0 can be used as a reference size in further DCI size alignment operations).
[0445] Optionally, if the UE is configured to monitor DCI format 3_1, the "size of DCI format 3_0 / 3_1" refers to the size of DCI format 3_1 (e.g., according to the definitions of DCI format 3_1 and DCI format 3_0, the size of DCI format 3_0 is always less than (or less than or equal to) the size of DCI format 3_1, so as long as the UE is configured to monitor DCI format 3_1, DCI format 3_1 can be used as a reference size in further DCI size alignment operations).
[0446] Optionally, due to DCI format alignment operations, D 3031 can be different in different steps (or sub-steps, or sub-sub-steps, or sub-sub-sub-steps).
[0447] Optionally, D exists only when the UE is configured to monitor DCI format 3_0 or the UE is configured to monitor DCI format 3_1. 3031 Only then does it exist.
[0448] ◆ Optionally, the execution order among step S101-0 (if it exists), step S101-1 (if it exists), step S101-2 (if it exists), step S101-3 (if it exists), and step S101-4 (if it exists) can be adjusted in any way.
[0449] ◆ Optionally, the time points of step S101-0 and / or step S101-1 and / or step S101-2 and / or step S101-3 and / or step S101-4 can be determined in one of the following ways:
[0450] ο After step 2 and before step 3 (for example, when step 2A does not exist).
[0451] ο After step 2A and before step 3.
[0452] ο After the step (or sub-step or sub-sub-step or sub-sub-sub-step) immediately preceding step 3 and before step 3.
[0453] ο After step 4.
[0454] ο After step 4A (for example, when step 4B does not exist).
[0455] ο After step 4B.
[0456] ο After the "DCI size alignment process".
[0457] ◆ Optionally, step S101-0 and / or step S101-1 and / or step S101-2 and / or step S101-3 and / or step S101-4 can occur once or multiple times.
[0458] In addition, at step S103, receive DCI. For example, receive DCI according to one or more DCI formats in the DCI format set S.
[0459] Optionally, in Embodiment 1 of the present invention, in applicable cases (for example, for a certain or certain DCI formats), the "configured" in "UE is configured to monitor DCI format X" can be replaced with "predefined".
[0460] Optionally, in Embodiment 1 of the present invention, in applicable cases (for example, for a certain or certain DCI formats), the "configured" in "UE is configured to monitor DCI format X" can be replaced with "pre-configured".
[0461] Thus, according to the first embodiment, the present invention provides a method, by improving the DCI size alignment process, enabling the UE to efficiently and unambiguously determine the size of the DCI related to 5G V2X.
[0462] [Variant Example]
[0463] Next, use Figure 2 to illustrate a user equipment that can execute the method performed by the user equipment described in detail above of the present invention as a variant example.
[0464] Figure 2 is a block diagram showing the user equipment UE related to the present invention.
[0465] As Figure 2 shown, the user equipment UE20 includes a processor 201 and a memory 202. The processor 201 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 202 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories, etc. Program instructions are stored on the memory 202. When executed by the processor 201, these instructions can execute the above method performed by the user equipment described in detail in the present invention.
[0466] The method and the related equipment of the present invention have been described above in conjunction with the preferred embodiments. Those skilled in the art can understand that the methods shown above are merely exemplary, and the above-described embodiments can be combined with each other without conflict. The method of the present invention is not limited to the steps and sequences 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 will be developed and can be used for base stations, MMEs, or UEs, etc. The various identifiers shown above are merely exemplary and not restrictive, and the present invention is not limited to the specific information elements that are examples of these identifiers. Those skilled in the art can make many changes and modifications according to the teachings of the shown embodiments. Those skilled in the art should understand that part or all of a mathematical expression or a mathematical equation or a mathematical inequality can be simplified to a certain extent (such as combining constant terms) or transformed or rewritten; the mathematical expressions or mathematical equations or mathematical inequalities before and after the simplification or transformation or rewriting can be considered equivalent.
[0467] It should be understood that the above embodiments of the present invention can be implemented by software, hardware, or a combination of both software and hardware. For example, various components inside the base station and user equipment in the above embodiments 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 processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), complex programmable logic devices (CPLDs), and so on.
[0468] In this application, a "base station" may refer to a mobile communication data and control switching center with a certain transmission power and a certain coverage area, including functions such as resource allocation and scheduling, data reception and transmission. A "user equipment" may refer to a user mobile terminal, such as a mobile phone, a notebook, or other terminal devices that can communicate wirelessly with a base station or a micro base station.
[0469] In addition, the embodiments of the present invention disclosed herein can be implemented on a computer program product. More specifically, the computer program product is a product with a computer-readable medium encoded with computer program logic. When executed on a computing device, the computer program logic provides related operations to implement the above technical solutions of the present invention. When executed on at least one processor of a computing system, the computer program logic causes the processor to perform the operations (methods) described in the embodiments of the present invention. Such a setting of the present invention is typically provided as software, code, and / or other data structures set or encoded on a computer-readable medium such as an optical medium (e.g., CD-ROM), a floppy disk, or a hard disk, or other media such as firmware or microcode on one or more ROMs or RAMs or PROM chips, or a downloadable software image, a shared database, etc. in one or more modules. The software or firmware or such a configuration can be installed on a computing device so that one or more processors in the computing device perform the technical solutions described in the embodiments of the present invention.
[0470] In addition, each functional module or each feature of the base station device and the terminal device used in each of the above embodiments can be implemented or executed by a circuit, and the circuit is generally one or more integrated circuits. The circuit designed to execute each function described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or a general integrated circuit, a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate 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 above general-purpose processor or each circuit may be configured by a digital circuit or may be configured by a logic circuit. In addition, when an advanced technology capable of replacing the current integrated circuit appears due to the progress of semiconductor technology, the present invention may also use the integrated circuit obtained by using this advanced technology.
[0471] Although the present invention has been shown above in conjunction with the preferred embodiments of the present invention, those skilled in the art will understand that various modifications, substitutions, and changes can be made to the present invention without departing from the spirit and scope of the present invention. Therefore, the present invention should not be limited by the above embodiments, but should be defined by the appended claims and their equivalents.
Claims
1. A user equipment (UE), characterized in that it includes: a processor; and a memory storing instructions, wherein, based on the instructions, the processor is configured to: perform a first DCI size alignment process for a first set of downlink control information (DCI) formats, wherein if at least one of DCI format 3_0 and DCI format 3_1 is configured to be monitored on a cell, the first set of DCI formats includes all DCI formats configured to be monitored for the cell except the at least one of DCI format 3_0 and DCI format 3_1; and if at least one of DCI format 3_0 and DCI format 3_1 is configured to be monitored on the cell, perform a second DCI size alignment process for the at least one of DCI format 3_0 and DCI format 3_1 that is monitored, wherein in the second DCI size alignment process, the processor is configured to: if a) both DCI format 3_0 and DCI format 3_1 are configured to be monitored on the cell and b) the number of information bits in one of DCI format 3_0 and DCI format 3_1 is less than the payload in the other of DCI format 3_0 and DCI format 3_1, add zeros to the one of DCI format 3_0 and DCI format 3_1 until the payload size is equal to the payload size of the other of DCI format 3_0 and DCI format 3_1, and in the second DCI size alignment process, the processor is configured to: add zeros to the at least one of DCI format 3_0 and DCI format 3_1 that is monitored until the payload size of the at least one of DCI format 3_0 and DCI format 3_1 that is monitored is equal to the minimum size among the payload sizes of the DCI formats in the first set of DCI formats that is greater than the payload size of the at least one of DCI format 3_0 and DCI format 3_1 that is monitored.
2. A method performed by a user equipment (UE), characterized in that it includes the following steps: perform a first DCI size alignment process for a first set of downlink control information (DCI) formats, wherein if at least one of DCI format 3_0 and DCI format 3_1 is configured to be monitored on a cell, the first set of DCI formats includes all DCI formats configured to be monitored for the cell except the at least one of DCI format 3_0 and DCI format 3_1; and if at least one of DCI format 3_0 and DCI format 3_1 is configured to be monitored on the cell, perform a second DCI size alignment process for the at least one of DCI format 3_0 and DCI format 3_1 that is monitored, wherein In the second DCI size alignment process, if a) both DCI format 3_0 and DCI format 3_1 are configured to be monitored on the cell and b) the number of information bits in one of the DCI formats of DCI format 3_0 and DCI format 3_1 is less than the payload in the other DCI format of DCI format 3_0 and DCI format 3_1, zeros are added to the one DCI format of DCI format 3_0 and DCI format 3_1 until the payload size is equal to the payload size of the other DCI format of DCI format 3_0 and DCI format 3_1, and In the second DCI size alignment process, zeros are added to the at least one monitored DCI format of DCI format 3_0 and DCI format 3_1 until the payload size of the at least one monitored DCI format of DCI format 3_0 and DCI format 3_1 is equal to the respective payload sizes of the DCI formats in the first DCI format set that are greater than the minimum size of the at least one monitored DCI format of DCI format 3_0 and DCI format 3_1.
Citation Information
Patent Citations
Method for transmitting downlink control information in wireless communication system and device using same
CN109644487A
Transmission Downlink Control Information for New Radio (NR) System
US20190223160A1