Apparatus and method for irregular resource element mapping

Abstract

Apparatuses, methods, and systems are disclosed for irregular resource element mapping. An apparatus (800) includes a transceiver (825) operable to communicate with a radio access network ("RAN"). The apparatus (800) includes a processor (805) that receives (1005), via the transceiver (825), a resource element mapping configuration including an indication of an irregular subcarrier spacing for a plurality of subcarriers of a UE. The resource element mapping configuration can be defined by the RAN based on a carrier frequency. The processor (805) applies (1010) the indicated irregular subcarrier spacing to resource elements ("REs") of the UE in accordance with the resource element mapping configuration for communication with the RAN.

Description

Technical Field

[0001] The topics disclosed in this article generally relate to wireless communication, and more specifically to the mapping of irregular resource elements. Background Technology

[0002] In some wireless communication systems, communication is supported on high-frequency radio bands with spacing between subcarriers. Summary of the Invention

[0003] Solutions for mapping irregular resource elements, such as those for handling high-frequency phase noise, are disclosed. These solutions can be implemented by apparatus, systems, methods, or computer program products.

[0004] In some embodiments, the radio access network (“RAN”) supports new resource element mapping to the time / frequency grid for high-frequency phase noise effect processing by allowing the system to use low subcarrier spacing (“SCS”) based on carrier frequency, allocated bandwidth (“BW”), and quality of service (“QoS”) requirements in a network-based configuration.

[0005] In some embodiments, resource element mapping includes mapping subcarriers close to baseband DC (“DC”) with a lower density than subcarriers at the edges of the spectrum. In some embodiments, resource element mapping includes dividing resource blocks (“RBs”) into different sets with different subcarrier offsets. In some embodiments, resource element mapping includes squelching the set of RBs close to DC and maintaining a default spacing for the rest of the RBs. In some embodiments, resource element mapping includes puncturing data subcarriers for RBs close to DC and configuring the SCS. μ The default configuration of the reference signal is maintained when the value is above a certain threshold. Attached Figure Description

[0006] A more specific description of the embodiments briefly described above will be presented with reference to the specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only a few embodiments and should therefore not be considered as limiting the scope; the embodiments will be described and explained with additional specificity and detail using the drawings, in which:

[0007] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for mapping irregular resource elements;

[0008] Figure 2A This is a diagram illustrating the spacing between active subcarriers and inter-carrier interference;

[0009] Figure 2B This is a diagram illustrating an embodiment of irregular spacing between active subcarriers;

[0010] Figure 3 This is a diagram illustrating one embodiment of the spacing between active subcarriers with frequency offset;

[0011] Figure 4 This is a diagram illustrating one embodiment using two artificial subcarrier spacings;

[0012] Figure 5 This is a diagram illustrating one embodiment of maintaining empty resource blocks around a DC;

[0013] Figure 6 This is a diagram illustrating an embodiment of reference signal transmission using empty resource blocks;

[0014] Figure 7 The new radio protocol stack is described;

[0015] Figure 8 This is a block diagram illustrating one embodiment of a user equipment device that can be used for mapping irregular resource elements;

[0016] Figure 9 This is a block diagram illustrating one embodiment of a network device apparatus that can be used for mapping irregular resource elements;

[0017] Figure 10 This is a flowchart illustrating one embodiment of a method for mapping irregular resource elements; and

[0018] Figure 11 This is a flowchart illustrating an embodiment of another method for mapping irregular resource elements. Detailed Implementation

[0019] As those skilled in the art will understand, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, embodiments can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects.

[0020] For example, the disclosed embodiments can be implemented as hardware circuitry, including custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments can also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may, for example, be organized as objects, procedures, or functions.

[0021] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device uses only signals for accessing the code.

[0022] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof.

[0023] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable optical disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0024] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and traditional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer via any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or it can be connected to an external computer (e.g., via the Internet provided by an Internet service provider).

[0025] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of these specific details or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0026] Throughout this specification, references to "an embodiment," "embodiment," or similar language mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly stated otherwise, the phrases "in an embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless expressly stated otherwise, the list of enumerated items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms "an," "a," and "the" also mean "one or more".

[0027] As used herein, a list containing the conjunction “and / or” includes any single item in the list or a combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term “one or more of…” includes any single item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term “one of…” includes one and only one of any single item in the list. For example, “one of A, B, and C” includes only A, only B, or only C and excludes combinations of A, B, and C. As used herein, “selected from the group consisting of A, B, and C” includes one and only one of A, B, or C and excludes combinations of A, B, and C. As used in this article, “selecting members of a group consisting of A, B, and C and their combinations” includes only A, only B, only C, combinations of A and B, combinations of B and C, combinations of A and C, or combinations of A, B, and C.

[0028] The following description of various aspects of the embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that individual blocks in the schematic flowcharts and / or schematic block diagrams, as well as combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that instructions executable by the processor of the computer or other programmable data processing apparatus create means for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0029] The code can also be stored in a storage device that can instruct a computer, other programmable data processing device or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art including instructions that implement the functions / actions specified in the flowchart and / or block diagram.

[0030] The code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device, thereby producing a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the flowchart and / or block diagram.

[0031] The flowcharts and / or block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the flowcharts and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

[0032] It should also be noted that in some alternative implementations, the functions marked in the boxes may not appear in the order shown in the figures. For example, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods that are equivalent in function, logic, or effect to one or more boxes or portions thereof shown in the figures can be contemplated.

[0033] While various arrow and line types may be used in flowcharts and / or block diagrams, they are not intended to limit the scope of the corresponding embodiments. In practice, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of a depicted embodiment. It will also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0034] The description of the elements in each figure can be referenced to the elements in the preceding figures. In all figures, the same reference numerals refer to the same elements, including alternative embodiments of the same elements.

[0035] In general, this disclosure describes systems, methods, and apparatuses for mapping irregular resource elements. In various embodiments, existing NR DL and UL waveforms can be adapted to support operation between 52.6 GHz and 71 GHz. For example, applicable parameter sets (including subcarrier spacing) and channel bandwidths (including maximum bandwidth) can be adapted to operate at higher frequency ranges. In various embodiments, physical layer aspects can be adjusted, including using one or more new parameter sets (μ values ​​in 38.211) to operate within this frequency range.

[0036] In the following description, the terms antenna, panel, antenna panel, device panel, and UE panel are used interchangeably. An antenna panel can be hardware used to transmit and / or receive radio signals at frequencies below 6 GHz (e.g., frequency range 1 (FR1)) or above 6 GHz (e.g., frequency range 2 (FR2) or millimeter wave (mmWave)). In some embodiments, the antenna panel may include an array of antenna elements, wherein each antenna element is connected to hardware such as a phase shifter, which allows a control module to apply spatial parameters for signal transmission and / or reception. The resulting radiation pattern can be referred to as a beam, which may be single-peaked or non-single-peaked and may allow the device to amplify signals transmitted or received from a spatial direction.

[0037] In some embodiments, the antenna panel may or may not be virtualized as an antenna port in the specification. The antenna panel can be connected to the baseband processing module via radio frequency (RF) chains for each of the transmission (egress) and reception (ingress) directions. The device's capabilities regarding the number of antenna panels, its duplex capability, its beamforming capability, etc., may or may not be transparent to other devices. In some embodiments, capability information may be transmitted via signaling, or in some embodiments, capability information may be provided to the device without signaling. Where such information is available to other devices, it can be used for signaling or local decision-making.

[0038] In some embodiments, (e.g., of a UE or RAN node) a device antenna panel may be a physical or logical antenna array comprising a collection of antenna elements or antenna ports (e.g., in-phase / quadrature (I / Q) modulators, analog-to-digital (A / D) converters, local oscillators, phase-shift networks) that share a common or significant portion of the RF chain. A device antenna panel, or “device panel,” may be a logical entity having physical device antennas mapped to logical entities. The mapping from physical device antennas to logical entities may vary depending on the device implementation. Communication (receiving or transmitting) on ​​at least a subset of the antenna elements or antenna ports (also referred to herein as active elements) of the antenna panel that are active for radiating energy requires biasing or energizing the RF chain, which generates current consumption or power consumption (including power amplifier / low-noise amplifier (LNA) power consumption associated with the antenna elements or antenna ports) in the device associated with the antenna panel. The phrase “active for radiating energy” as used herein is not intended to be limited to transmitting functionality but also includes receiving functionality. Therefore, the active antenna elements used for radiating energy can be coupled simultaneously or sequentially to a transmitter to transmit radio frequency energy or to a receiver to receive radio frequency energy, or generally to a transceiver to perform their intended functionality. Communication on the active elements of the antenna panel enables the generation of radiation patterns or beams.

[0039] In some embodiments, depending on the device's own implementation, the "device panel" can have at least one of the following functionalities as an operational role for independently controlling its Tx beam, independently controlling its transmit power, and independently controlling its transmit timing. The "device panel" can be transparent to the gNB. Under certain conditions, the gNB or network can assume that the mapping between the device's physical antennas and the logical entity "device panel" may not change. For example, the conditions may include the duration until the next update or report from the device, or the duration under which the gNB assumes the mapping will not change.

[0040] The device can report its capabilities to the gNB or network regarding the "device panel". Device capabilities may include at least the number of "device panels". In one implementation, the device may support UL transmission from one beam within the panel; in the case of multiple panels, more than one beam (one beam per panel) may be used for UL transmission. In another implementation, more than one beam per panel may be supported / used for UL transmission.

[0041] In some of the described embodiments, an antenna port is defined such that a channel through which a symbol on the antenna port is transmitted can be inferred from a channel through which another symbol on the same antenna port is transmitted. Two antenna ports are said to be quasi-co-located (QCL) if the large-scale properties of a channel through which a symbol on one antenna port is transmitted can be inferred from a channel through which a symbol on another antenna port is transmitted. Large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. Two antenna ports can be quasi-located relative to a subset of large-scale properties, and different subsets of large-scale properties can be indicated by the QCL type. For example, qcl-Type can take one of the following values:

[0042] 'QCL-TypeA': {Doppler frequency shift, Doppler spread, average delay, delay spread}

[0043] 'QCL-TypeB': {Doppler frequency shift, Doppler diffusion}

[0044] 'QCL-TypeC': {Doppler shift, average delay}

[0045] 'QCL-TypeD': {space Rx parameter}.

[0046] Spatial Rx parameters may include one or more of the following: Angle of Arrival (AoA), Main AoA, Average AoA, Angle Spread, Power Angle Spectrum (PAS) of AoA, Average AoD (Departure Angle), PAS of AoD, Transmit / Receive Channel Correlation, Transmit / Receive Beamforming, Spatial Channel Correlation, etc.

[0047] According to embodiments, an "antenna port" can be a logical port that corresponds to a beam (generated by beamforming) or a physical antenna on the device. In some embodiments, a physical antenna can be directly mapped to a single antenna port, wherein the antenna port corresponds to an actual physical antenna. Alternatively, after applying complex weights, cyclic delays, or both to the signal on each physical antenna, a set or subset of physical antennas, or an antenna set or antenna array or antenna subarray, can be mapped to one or more antenna ports. A set of physical antennas can have antennas from a single module or panel or from multiple modules or panels. Weights can be fixed, as in antenna virtualization schemes such as cyclic delay diversity ("CDD"). The process for deriving antenna ports from physical antennas can be specific to the device implementation and transparent to other devices.

[0048] In some of the described embodiments, the TCI state associated with the target transmission can indicate parameters for configuring the quasi-co-location relationship between the target transmission (e.g., the target RS of the DM-RS port of the target transmission during the transmission timing) and the source reference signal (e.g., SSB / CSI-RS / SRS) relative to the quasi-co-location type parameters indicated in the corresponding TCI state. The device can receive configurations for multiple transmission configuration indicator states for the serving cell to enable transmission on the serving cell.

[0049] In some of the described embodiments, spatial relation information associated with the target transmission can indicate parameters for configuring the spatial settings between the target transmission and a reference RS (e.g., SSB / CSI-RS / SRS). For example, the device may transmit the target transmission using the same spatial domain filter used for receiving the reference RS (e.g., a DL RS such as an SSB / CSI-RS). In another example, the device may transmit the target transmission using the same spatial domain filter used for transmitting the reference RS (e.g., a UL RS such as an SRS). The device is capable of receiving configurations for multiple spatial relation information configurations for the serving cell for transmission on the serving cell.

[0050] This paper discloses solutions for mitigating the impact of high subcarrier spacing (“SCS”) on system design. High subcarrier spacing is required to handle inter-carrier interference (“ICI”) caused by high-frequency phase noise. However, increasing the subcarrier spacing impacts the physical layer channel structure and signaling. For example, when the symbol length is halved to double the SCS, increased cyclic prefix (“CP”) overhead is needed to cope with multipath effects in certain scenarios. Furthermore, the number of Hybrid Automatic Repeat Request (“HARQ”) procedures will increase due to the shortened Transmission Time Interval (“TTI”) length (e.g., scheduling units).

[0051] As shown in Table 1, multiple sets of Orthogonal Frequency Division Multiplexing (“OFDM”) parameters are supported, among which, for the downlink or uplink bandwidth portion... μ The cyclic prefix and the loop prefix are respectively from higher-level parameters subcarrierSpacing and cyclicPrefix Obtained.

[0052]

[0053] Table 1: Supported set of transmission parameters.

[0054] Regarding the resource grid, for each parameter set and carrier, it originates from the common resource block (“RB”) indicated by higher-layer signaling. Start defining Subcarriers and A resource grid of OFDM symbols. A set of resource grids exists for each transmission direction (uplink, downlink, or sidelink), where the index... x These are configured for DL, UL, and SL, respectively, for downlink, uplink, and sidelink. The subscripts can be discarded when there is no risk of obfuscation. x For a given antenna port Subcarrier spacing configuration There exists a resource grid in the transmission direction (downlink, uplink, or sidelink).

[0055] For uplink and downlink, subcarrier spacing configuration carrier bandwidth Depend on SCS- Specific Carrier Higher-level parameters in IE carrierBandwidth Provided. Subcarrier spacing configuration. starting position Depend on SCS-Specific Carrier Higher-level parameters in IE offsetToCarrier Provided.

[0056] The frequency position of a subcarrier refers to its center frequency.

[0057] For the downlink SCS-Specific Carrier Higher-level parameters in IE txDirectCurrentLocation For each set of parameters configured in the downlink, the location of the transmitter baseband DC (“DC”) subcarriers in the downlink is indicated. Values ​​in the range 0-3299 represent the number of DC subcarriers, and a value of 3300 indicates that the DC subcarriers are located outside the resource grid.

[0058] For the uplink UplinkTxDirectCurrentBWP Higher-level parameters in IE txDirectCurrentLocation For each configuration, the bandwidth portion indicates the position of the transmitter's DC subcarrier in the uplink, including whether the DC subcarrier position is offset by 7.5 kHz relative to the center of the indicated subcarrier. Values ​​in the range 0-3299 represent the number of DC subcarriers, value 3300 indicates that the DC subcarrier is outside the resource grid, and value 3301 indicates that the position of the DC subcarrier in the uplink is undetermined.

[0059] Regarding resource elements, specifically for antenna ports and subcarrier spacing configuration Each element in the resource grid is called a resource element and is composed of... Uniquely identified, among which, k It is an index in the frequency domain and l This refers to the sign position in the time domain relative to a reference point. (Resource element) Corresponding to physical resources and complex values If there is no risk of confusion, or if a specific antenna port or subcarrier spacing is not specified, the index can be discarded. and Thus producing or .

[0060] Regarding the mapping from Physical Resource Blocks (“PRBs”) to Virtual Resource Blocks, the User Equipment (“UE”) assumes complex-valued symbols for each antenna port used for transmission on the physical channel. The block conforms to downlink power allocation and from Begin mapping sequentially to resource elements that satisfy all of the following criteria within the virtual resource blocks assigned for transport. 1) They are in virtual resource blocks assigned for transmission; 2) the corresponding physical resource blocks are declared as available for use in the Physical Downlink Shared Channel (“PDSCH”); and 3) the corresponding resource elements in the corresponding physical resource blocks are: a) not used for transmission of the associated demodulation reference signal (“DM-RS”) or DM-RS intended for use in other co-scheduled UEs; b) if the corresponding physical resource block is for a PDSCH scheduled by a Physical Downlink Control Channel (“PDCCH”) with Cyclic Redundancy Check (“CRC”) scrambled by a Cell Radio Network Temporary Identifier (“C-RNTI”), a Modulation Coded Scheme C-RNTI (“MCS-C-RNTI”), and a Configured Scheduling RNTI (“CS-RNTI”), or a PDSCH with Semi-Persistent Scheduling (“SPS”), not used for the Non-Zero Power Channel State Information Reference Signal (“CSI-RS”), unless the Non-Zero Power CSI-RS is transmitted via a physical downlink control channel (“PDCCH”) with a Cell Radio Network Temporary Identifier (“C-RNTI”), a Modulation Coded Scheme C-RNTI (“MCS-C-RNTI”), or a PDSCH with a Configured Scheduling RNTI (“CS-RNTI”), then not used for the Non-Zero Power Channel State Information Reference Signal (“CSI-RS”), unless the Non-Zero Power CSI-RS is transmitted via a physical downlink control channel (“PDCCH”) with a Cyclic Redundancy Check (“CRC”). MeasObjectNR Higher-level parameters in IE CSI-RS-Resource-Mobility The configured CSI-RS or unless the non-zero power CSI-RS is an aperiodic non-zero power CSI-RS resource; c) not used for phase tracking reference signals (“PT-RS”); and d) not declared as unavailable for PDSCH.

[0061] As is customary, resource elements allocated to PDSCH and not reserved for other purposes. The mapping should be indexed on the assigned virtual resource block first. Then index l The increasing order, where, It is the first subcarrier in the lowest-numbered virtual resource block assigned for transmission.

[0062] Figure 1A wireless communication system 100 for directional LBT according to embodiments of the present disclosure is depicted. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a radio access network (“RAN”) 120, and a mobile core network 140. The RAN 120 and the mobile core network 140 form a mobile communication network. The RAN 120 may consist of a base station unit 110, and the remote unit 105 communicates with the base station unit 110 using a wireless communication link 115. Although in Figure 1 The document depicts a specific number of remote units 105, base station units 110, wireless communication links 115, RAN 120, and mobile core network 140, but those skilled in the art will recognize that any number of remote units 105, base station units 110, wireless communication links 115, RAN 120, and mobile core network 140 can be included in the wireless communication system 100.

[0063] In one implementation, RAN 120 conforms to a 5G system as defined in the 3GPP specification. In another implementation, RAN 120 conforms to an LTE system as defined in the 3GPP specification. However, more generally, the wireless communication system 100 can implement other open or proprietary communication networks, such as WiMAX, and other networks. This disclosure is not intended to limit implementation to any particular wireless communication system architecture or protocol.

[0064] In one embodiment, remote unit 105 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., TVs connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), etc. In some embodiments, remote unit 105 may include wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 105 may be referred to as a UE, subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transceiver unit (“WTRU”), device, or other terms used in the art.

[0065] Remote unit 105 can communicate directly with one or more base station units 110 in RAN 120 via uplink (“UL”) and downlink (“DL”) communication signals. Additionally, UL and DL communication signals can be carried on wireless communication link 115. Here, RAN 120 is an intermediate network providing access to mobile core network 140 to remote unit 105. As described above, wireless communication link 115 can employ higher frequency radio, for example, in the range of 52.6 GHz to 71 GHz.

[0066] In some embodiments, remote unit 105 communicates with application server 151 via a network connection to mobile core network 140. For example, application 107 in remote unit 105 (e.g., web browser, media client, telephone / VoIP application) can trigger remote unit 105 to establish a PDU session (or other data connection) with mobile core network 140 via RAN 120. Mobile core network 140 then uses the PDU session to relay services between remote unit 105 and application server 151 in packet data network 150. Note that remote unit 105 can establish one or more PDU sessions (or other data connections) with mobile core network 140. Therefore, remote unit 105 can simultaneously have at least one PDU session for communicating with packet data network 150 and at least one PDU session for communicating with another data network (not shown).

[0067] Base station unit 110 may be distributed across a geographical area. In some embodiments, base station unit 110 may also be referred to as an access terminal, access point, base station, base station, node B, eNB, gNB, home node B, relay node, or any other term used in the art. Base station unit 110 is typically part of a radio access network (“RAN”) such as RAN 120, which may include one or more controllers communicatively coupled to one or more corresponding base station units 110. These and other elements of the radio access network are not shown, but are generally known to those skilled in the art. Base station unit 110 is connected to mobile core network 140 via RAN 120.

[0068] Base station unit 110 can serve multiple remote units 105 within its service area, such as a cell or cell sector, via wireless communication link 115. Base station unit 110 can communicate directly with one or more remote units 105 via communication signals. Typically, base station unit 110 transmits DL communication signals to serve remote units 105 in the time, frequency, and / or spatial domains. Furthermore, DL communication signals can be carried on wireless communication link 115. Wireless communication link 115 can be any suitable carrier in the licensed or unlicensed radio spectrum. Wireless communication link 115 facilitates communication between one or more remote units 105 and / or one or more base station units 110.

[0069] In one embodiment, the mobile core network 140 is a 5G core (“5GC”) or an evolved packet core (“EPC”), which may be coupled to a packet data network 150, such as the Internet and private data networks, as well as other data networks. The remote unit 105 may have a subscription or other account with respect to the mobile core network 140. Each mobile core network 140 belongs to a single Public Land Mobile Network (“PLMN”). This disclosure is not intended to limit implementation to any particular wireless communication system architecture or protocol.

[0070] Mobile core network 140 includes several network functions (“NFs”). As depicted, mobile core network 140 includes multiple user plane functions (“UPFs”) 141. Mobile core network 140 also includes multiple control plane functions, including but not limited to access and mobility management functions (“AMFs”) 143, session management functions (“SMFs”) 145, policy control functions (“PCFs”) 147, and unified data management functions (“UDMs”) 149 serving RAN 120. In some embodiments, mobile core network 140 may also include authentication server functions (“AUSFs”), network repository functions (“NRFs”) (used by various NFs to discover and communicate with each other via APIs), or other NFs defined for 5GC.

[0071] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a "network slice" refers to a portion of the mobile core network 140 optimized for a specific service type or communication service. Network instances may be identified by S-NSSAI, while the set of network slices authorized for use by the remote unit 105 is identified by NSSAI. In some embodiments, various network slices may include individual instances of network functions, such as SMF 145 and UPF 141. In some embodiments, different network slices may share some common network functions, such as AMF 143. For illustration purposes, in Figure 1Different network slices are not shown, but their support is assumed.

[0072] Despite Figure 1 The document describes a specific number and type of network functions, but those skilled in the art will recognize that any number and type of network functions can be included in the mobile core network 140. Furthermore, in the case where the mobile core network 140 is an EPC, the described network functions can be replaced by appropriate EPC entities, such as MME, S-GW, P-GW, HSS, etc. In some embodiments, the mobile core network 140 may include an AAA server.

[0073] Although Figure 1 The components of the 5G RAN and 5G core network are described, but the described embodiments for mapping irregular resource elements are applicable to other types of communication networks and RATs, including IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfoxx, etc. For example, in LTE variants involving EPC, AMF 143 can be mapped to MME, SMF to the control plane portion of PGW and / or MME, UPF to the SGW and user plane portion of PGW, UDM / UDR to HSS, and so on.

[0074] In the following description, the term "gNB" is used for base station, but it can be replaced by any other radio access node, such as RAN node, eNB, BS, eNB, gNB, AP, NR, etc. Furthermore, these operations are primarily described in the context of 5G NR. However, the proposed solution / method is equally applicable to other mobile communication systems that support radio communication at higher frequency ranges.

[0075] like Figure 2A As shown, the ICI effect decreases with increasing frequency offset from the center frequency. For example, in the case of UL, the ICI 208 observed on subcarriers positioned at the edge of the UL allocation close to the UE is slightly smaller than the ICI 206 near the baseband DC 202 due to the different number of surrounding subcarriers contributing to the ICI. This prompts the use of irregular or staggered baseband subcarrier mapping with a lower SCS, such that subcarriers near the baseband DC 202 are mapped using frequency offset, for example, by leaving empty or unoccupied RE 204 to generate a higher spacing between carriers than that produced by the default SCS. The spacing between subcarriers decreases, for example, as we move away from the baseband DC 202, as... Figure 2B As shown in the diagram.

[0076] Phase noise is a multiplication noise process with time-domain signals, and the expected ICI (Inter-Capacity Interference) created on OFDM subcarriers with a sufficient number of adjacent subcarriers (depending on the subcarrier spacing) is similar. At or near band / carrier edges or resource allocation edges (e.g., in the uplink), the expected ICI is lower due to fewer surrounding subcarriers. Therefore, subcarriers closer to the center of a band / carrier / allocation can use larger spacing between subcarriers compared to subcarriers near band / carrier / allocation edges. In one embodiment, irregular subcarrier mapping can produce lower overhead compared to staggered / equally spaced subcarrier mapping.

[0077] Figure 3 An embodiment of a resource grid 300 with intervals (e.g., empty / unoccupied REs 302) between non-empty / active / occupied REs 304 with subcarriers having frequency offsets is depicted, thereby illustrating an example of a first solution. According to the first solution, resource elements are allocated for PDSCH / PUSCH and not reserved for other purposes. (in, It is a carrier index. l It is a symbol index. p It is the antenna port, and μ The mapping of the SCS index (used to generate signals) on the assigned resource block is indexed first. Post-index l The increasing order. In subcarriers k + Distribute elements ,in, Artificial SCSs are generated between subcarriers in the lowest-numbered resource block assigned for transmission. A frequency offset of 306. In some embodiments, the frequency offset decreases with the RB index. .

[0078] Figure 4 An embodiment of a resource grid 400 with intervals (e.g., empty / unoccupied REs 402) between non-empty / active / occupied REs 404 with subcarriers having frequency offsets is depicted, thereby illustrating an example of a second solution. According to the second solution, the gNB / UE is configured by a higher layer to perform RE / subcarrier mapping for DL / UL, such that subcarriers in the first set of RBs are assigned frequency offsets. ,in, With artificial SCS 408 is associated, and the REs of other RBs are assigned frequency offsets. ,in, With artificial SCS 406 is associated, where the RBs closest to the baseband DC are allocated based on a higher artificial SCS. This refers to resource elements allocated for PDSCH and not reserved for other purposes. The mapping is indexed first on the assigned resource block. The increasing order of elements, where elements Subcarriers in the first set of RB And in the second set of subcarriers of RB Of which, and Is it separate from and Frequency offset between associated subcarriers and Higher than .

[0079] Figure 5 An embodiment of a resource grid 500 with intervals (e.g., empty / unoccupied REs 502) between non-empty / active / occupied REs 506 with subcarriers having frequency offsets is depicted, thus illustrating an example of a third solution. According to the third solution, the gNB / UE is configured by higher layers to perform RE / subcarrier mapping for DL / UL such that the first set of RBs configured close to the baseband DC does not carry active data subcarriers, such as empty REs 502, but instead uses empty / zero-power subcarriers. The REs of the second set of RBs are based on the default configured SCS. μ 504 assigned. Resource elements allocated for PDSCH / PUSCH and not reserved for other purposes. The mapping is indexed first on the assigned resource block. Then l The increasing order, where, It is the first subcarrier in the lowest-numbered resource block of the second set of RBs assigned for transmission.

[0080] Figure 6 An embodiment of a resource grid 600 with intervals (e.g., empty / unoccupied REs 602) between non-empty / active / occupied REs 606 with frequency-offset subcarriers is depicted, thus illustrating an example of a fourth solution. According to the fourth solution, the gNB / UE is configured by higher layers to perform RE / subcarrier mapping for DL / UL such that the first set of RBs configured close to the baseband DC does not carry active data subcarriers, but instead allocates reference signals 606 on some subcarriers. The REs of the second set of RBs are based on the default configured SCS. μ 604. Resource elements allocated for PDSCH / PUSCH and not reserved for other purposes. The mapping is indexed first on the assigned resource block. Then l The increasing order, where, It is the first subcarrier in the lowest-numbered resource block of the second set of RBs assigned for transmission.

[0081] In one embodiment of the fourth solution, when the configured SCS μ Above a certain threshold, only RS606 signals, such as demodulation reference signals (“DM-RS”), phase tracking reference signals (“PT-RS”), channel state information reference signals (“CSI-RS”), and sounding reference signals (“SRS”), are transmitted in the first set of RBs configured close to the baseband DC according to the instructions of the corresponding RS 606, and the data subcarriers within the first set of configured RBs are punctured. In this configuration, RS transmission remains unchanged, while the number of data subcarriers is reduced.

[0082] In another embodiment of the fourth solution, when the configured SCS μ If the threshold is exceeded, then DM-RS will not be transmitted in the first set of RBs configured close to the baseband DC. DM-RS can be transmitted only in RBs in which data is still being transmitted partially or completely. The different modes of DM-RS transmission in the first set of RBs configured close to the baseband DC, as described in the fourth solution, can be configured via downlink control information (“DCI”) using higher-level signaling such as radio resource control (“RRC”) or dynamic signaling, or can be configured according to predefined rules / tables.

[0083] According to the fifth solution, the number of RBs affected by the default transmission of data subcarriers is configured as a function of the SCS shown in Table 2 below. Additionally, the offset in terms of the number of subcarriers between corresponding data subcarriers in the RBs can also be configured as shown in Table 3. In another embodiment, the two tables can be configured to the UE as a single configuration.

[0084] In another implementation, the ' 'Offset and / or have' The number of RBs offset is also specified as an information element ("IE") in the dedicated configuration of the RRC bandwidth portion ("BWP") and the PDSCH / PUSCH allocation in the BWP follows the specified offset.

[0085]

[0086] Table 2: Functions of SCS with fixed offsets The number of RBs

[0087]

[0088] Table 3: Functions of SCS with variable offsets The number of RBs

[0089] The above solution has been generally described as involving which REs / RBs are sent by the gNB. There are two general features to this implementation that are particularly relevant to the handling of transport blocks and the mapping of resource elements.

[0090] Feature 1—Rate Matching

[0091] In this feature, only resources intended for transmission are considered for processing transport blocks. Specifically, for rate matching purposes, only available REs are considered to determine the number of bits and symbols that can be transmitted in the assigned time / frequency (“T / F”) resources. Therefore, regarding, for example... Figure 5 Only non-empty (black) RE 506 is counted, while empty RE (gray) RE 502 is ignored. Therefore, in Figure 5 In this configuration, a total of 6 x 16 (empty) + 6 x 38 (non-empty) = 324 REs are assigned, and only the non-empty (black) 6 x 38 = 228 REs are used, which, for example, produces 912 bits that can be carried in 16-QAM. In one embodiment, this feature achieves optimal performance because rate matching or its inversion is using information corresponding to the utilization of radio resources.

[0092] Information regarding which REs were used for the transmission of a transport block or, alternatively, which UEs were not used for the transmission of a transport block needs to be available at the UE; this is referred to herein as “auxiliary information.” If the UE is a receiver, in one embodiment, auxiliary information is required to correctly reverse the rate matching process employed by the transmitting entity. If the UE is a transmitter, in one embodiment, auxiliary information is required to complete the rate matching process with the correct parameters. Auxiliary information may be communicated as part of resource assignment (e.g., in the PDCCH / DCI carrying the resource assignment), or it may be included in multicast / broadcast signals (e.g., carried by DCI format 2_0) via uplink control information (“UCI”) or by means of higher-layer signaling such as RRC configuration or media access control (“MAC”) elements.

[0093] Feature 2—RE perforation, RE noise suppression, and / or zero-power RE

[0094] In this feature, in one embodiment, all assigned resources are considered for the processing of transport blocks. Specifically, for rate matching purposes, all assigned REs are considered to determine the number of bits and symbols that can be transmitted in the assigned T / F resources. Therefore, regarding, for example... Figure 5Empty RE 502 and non-empty RE 506 (marked in black and gray respectively) are counted. Therefore, in Figure 5 In this configuration, a total of 6 x 16 (empty) + 6 x 38 (non-empty) = 324 REs are assigned, which, for example, generates 1296 bits that can be carried for 16-QAM. However, in one embodiment, only symbols carried by non-empty (black) REs are actually transmitted. This can be interpreted as puncturing empty (grey) REs, squashing empty (grey) REs, or transmitting empty (grey) REs with zero power. In one embodiment, feature 2 achieves suboptimal performance because rate matching or its inversion is using information that does not accurately correspond to the utilization of radio resources.

[0095] Compared to the information already available as part of the resource allocation, no additional auxiliary information is required at the UE, which is referred to herein as "Feature 2a". In the case of downlink transmission, in one embodiment, the receiving UE will still process empty (grey) REs as usual, which generally implies that only noise / interference is included in the corresponding symbol, which will slightly degrade decoding performance but is still technically possible (albeit at a higher error probability due to noise / interference). Similarly, if the UE is the transmitter and mutes the REs, the same applies to the gNB receiver with the necessary modifications.

[0096] However, performance can be improved in this feature if some auxiliary information regarding squelch or non-squelch REs is available; this is referred to herein as "Feature 2b". In such an embodiment, the receiver is able to ignore the corresponding RE during processing, so that additional noise / interference is not picked up by the receiver. In this way, only suboptimal rate-matching performance degrades decoding compared to the first feature. Auxiliary information regarding squelch REs, or alternatively non-squelch REs, used for the transmission of transport blocks can be conveyed as part of resource assignment (e.g., in the PDCCH / DCI carrying resource assignments), or it can be included in multicast / broadcast signals (e.g., carried by DCI format 2_0) via uplink control information (UCI) or by means of higher-level signaling such as RRC configuration or MAC control elements.

[0097] In one embodiment, the advantage of feature 2b over feature 2a is improved decoding performance achieved at the cost of the required auxiliary information by not picking up noise / interference from the squelch RE.

[0098] In one embodiment, the advantage of feature 2b over feature 1 is the simplified processing, as rate matching and its inversion can be performed as if all assigned resources were available, while the squelching / emptying of REs can be very easily implemented in the processing chain by setting the corresponding input values ​​in the IFFT stage. In some embodiments, the disadvantage is the suboptimal performance of rate matching and its inversion.

[0099] In one embodiment, the advantage of feature 2a over feature 1 is the simplified processing, as rate matching and its inversion can be performed as if all assigned resources were available, while the squelching / emptying of REs can be implemented very simply in the processing chain by setting the corresponding input values ​​in the IFFT stage. Additionally, in some embodiments, feature 2a does not require any auxiliary information, thus avoiding additional signaling overhead. In some embodiments, the disadvantages are poor decoding performance due to suboptimal rate matching and its inversion, and the picking up of noise / interference from the squelched REs.

[0100] In another implementation, one or more of the above features can also be configured as part of the IE in the RRC BWP-specific configuration.

[0101] In some embodiments, the frequency separation / offset between (candidate) occupied (e.g., data / control / reference signal RE) subcarriers (e.g., in terms of the number of subcarriers; at least one frequency separation / offset with irregular subcarrier mapping) is determined based on at least one of the following: operating frequency range, frequency band, subcarrier spacing, modulation order, regulatory requirements (e.g., regarding bandwidth occupancy requirements), transmit DC subcarrier position (for each DL carrier in the parameter set configured for downlink, for each of the configured bandwidth portions in uplink), whether the baseband DC subcarrier position is offset from the center of the indicated transmit DC subcarrier position, for example, 7.5 kHz, etc.

[0102] In one example embodiment, a first frequency separation value is used when the baseband DC subcarrier is offset from the center of the transmitted DC subcarrier (e.g., 7.5 kHz), and a second frequency separation value is used when the baseband DC subcarrier is not offset from the center of the transmitted DC subcarrier. In another example embodiment, the location of the occupied subcarrier is selected such that when the location of the transmitted DC subcarrier is within a resource grid or carrier, at least one of the empty or zero subcarriers (e.g., subcarriers between occupied subcarriers) coincides with the location of the transmitted DC subcarrier. In other words, in one embodiment, when the location of the transmitted DC subcarrier is within a resource grid or carrier, the location of the unoccupied subcarrier coincides with the location of the transmitted DC subcarrier. In one embodiment, this is advantageous because it reduces the impact of local oscillator leakage or baseband DC offset effects due to direct-switching transceivers on subcarriers near the baseband DC subcarrier.

[0103] In one example embodiment, the occupied subcarrier positions are determined based on the transmitted DC subcarrier positions (e.g., relative to the transmitted DC subcarrier positions). In one example, the two occupied subcarriers closest to the transmitted DC subcarrier are selected such that they are spaced approximately equally from the transmitted DC subcarrier positions. For example, for an odd number of N zero / empty subcarriers between two occupied subcarriers, floor(N / 2) zero / empty subcarriers are located between each occupied subcarrier and the transmitted DC subcarrier; while for an even number of N zero / empty subcarriers between two occupied subcarriers, N / 2 zero / empty subcarriers are located between the first occupied subcarrier and the transmitted DC subcarrier, and N / 2-1 zero / empty subcarriers are located between the second occupied subcarrier and the transmitted DC subcarrier. In some examples, the occupied subcarrier positions are determined based on a common reference point A of the resource block grid (e.g., relative to a common reference point A), and point 0 is the center of subcarrier 0 of common resource block 0, which coincides with "point A".

[0104] In some embodiments, zero / empty subcarriers can provide phase noise tracking functionality for the receiver. In another example, PT-RS can occupy a subset of empty / zero subcarriers. In one example, utilizing irregular subcarrier mapping, phase noise (e.g., common phase error) can be estimated based on locations with larger intervals between subcarriers (e.g., using at least one of the zero / empty subcarriers or PT-RS between subcarriers), and phase noise tracking / suppression can be applied to occupied subcarriers, especially when the intervals between subcarriers are reduced. In some examples with irregular subcarrier mapping, a first interval between subcarriers is used in a first portion of the transmit signal bandwidth or resource block grid, while a second interval between subcarriers is used in a second portion of the transmit signal bandwidth or resource block grid.

[0105] In one embodiment, the proposed solution helps to handle high-frequency phase noise effects by using a low SCS, allowing for greater system flexibility in the trade-offs between desired system performance in the presence of phase noise, CP and its overhead requirements for handling multipathing, HARQ timing, and the number of HARQ procedures. Furthermore, a higher signal-to-noise ratio (“SNR”) is achieved by using a lower SCS due to the longer OFDM symbols.

[0106] On the other hand, in one embodiment, using empty REs between active subcarriers with lower SCS can reduce the peak data rate of the system. Therefore, in some embodiments, the offset between subcarriers can be applied only to a few RBs close to the baseband DC, and thus the spectral efficiency of the system can be improved.

[0107] Table 3 below shows examples of peak data rates for different combinations of artificial SCS with interleaved subcarriers compared to the default SCS. RS and other overheads are not considered in this table.

[0108]

[0109] Table 4: Peak data rates for different subcarrier spacing configurations

[0110] Figure 7 An NR protocol stack 700 according to an embodiment of this disclosure is depicted. Although Figure 7 Remote unit 105, base station unit 121, and mobile core network 130 are shown, but these represent a collection of UEs interacting with RAN nodes and NFs (e.g., AMFs) in the mobile core network. As depicted, protocol stack 700 includes user plane protocol stack 705 and control plane protocol stack 710. User plane protocol stack 705 includes a physical (“PHY”) layer 715, a media access control (“MAC”) sublayer 720, a radio link control (“RLC”) sublayer 725, a packet data convergence protocol (“PDCP”) sublayer 730, and a service data adaptation protocol (“SDAP”) layer 735. Control plane protocol stack 710 also includes a physical layer 715, a MAC sublayer 720, an RLC sublayer 725, and a PDCP sublayer 730. Control plane protocol stack 710 also includes a radio resource control (“RRC”) layer 740 and a non-access stratum (“NAS”) layer 745.

[0111] The AS protocol stack for the control plane protocol stack 710 consists of at least RRC, PDCP, RLC, and MAC sublayers, as well as a physical layer. The AS protocol stack for the user plane protocol stack 705 consists of at least SDAP, PDCP, RLC, and MAC sublayers, as well as a physical layer. Layer 2 (“L2”) is divided into SDAP, PDCP, RLC, and MAC sublayers. Layer 3 (“L3”) includes the RRC sublayer 740 and NAS layer 745 for the control plane and includes, for example, the Internet Protocol (“IP”) layer or PDU layer (note the depiction) for the user plane. L1 and L2 are referred to as “lower layers”, such as PUCCH / PUSCH or MAC CE, while L3 and higher layers (e.g., transport layer, application layer) are referred to as “higher layers” or “upper layers”, such as RRC.

[0112] Physical layer 715 provides a transport channel to MAC sublayer 720. MAC sublayer 720 provides a logical channel to RLC sublayer 725. RLC sublayer 725 provides an RLC channel to PDCP sublayer 730. PDCP sublayer 730 provides radio bearers to SDAP sublayer 735 and / or RRC layer 740. SDAP sublayer 735 provides QoS flows to the mobile core network (e.g., 5GC). RRC layer 740 provides the addition, modification, and release of carrier aggregation and / or dual connectivity. RRC layer 740 also manages the establishment, configuration, maintenance, and release of signaling radio bearers (“SRBs”) and data radio bearers (“DRBs”). In some embodiments, the RRC entity is used to detect and recover from radio link failures.

[0113] Figure 8 User equipment device 800, which can be used for mapping irregular resource elements according to embodiments of the present disclosure, is depicted. In various embodiments, user equipment device 800 is used to implement one or more of the solutions described above. User equipment device 800 may be an embodiment of a UE such as remote unit 105 and / or UE 205 as described above. Furthermore, user equipment device 800 may include processor 805, memory 810, input device 815, output device 820, and transceiver 825. In some embodiments, input device 815 and output device 820 are combined into a single device, such as a touchscreen. In some embodiments, user equipment device 800 may not include any input device 815 and / or output device 820. In various embodiments, user equipment device 800 may include one or more of the following: processor 805, memory 810, and transceiver 825, and may not include input device 815 and / or output device 820.

[0114] As depicted, transceiver 825 includes at least one transmitter 830 and at least one receiver 835. Here, transceiver 825 communicates with one or more base station units 121. Additionally, transceiver 825 may support at least one network interface 840 and / or application interface 841. Application interface 841 may support one or more APIs. Network interface 840 may support 3GPP reference points such as Uu and PC5. Other network interfaces 840 may be supported, as will be understood by those skilled in the art.

[0115] In one embodiment, processor 805 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 805 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), digital signal processor (“DSP”), coprocessor, dedicated processor, or similar programmable controller. In some embodiments, processor 805 executes instructions stored in memory 810 to perform the methods and routines described herein. Processor 805 is communicatively coupled to memory 810, input device 815, output device 820, and transceiver 825. In some embodiments, processor 805 may include an application processor (also referred to as a “main processor”) that manages application domain and operating system (“OS”) functions, and a baseband processor (also referred to as a “baseband radio processor”) that manages radio functions.

[0116] In various embodiments, processor 805 controls user equipment device 800 to implement the aforementioned UE behavior for irregular resource element mapping. In one embodiment, transceiver 825 is operable to communicate with a radio access network (“RAN”). In yet another embodiment, processor 805 receives via transceiver 825 a resource element mapping configuration including an indication of irregular subcarrier spacing for a plurality of subcarriers for the UE, the resource element mapping configuration being defined by the RAN based on carrier frequencies. In one embodiment, processor 805 applies the indicated irregular subcarrier spacing to resource elements (“REs”) of the UE according to the resource element mapping configuration for communication with the RAN.

[0117] In one embodiment, memory 810 is a computer-readable storage medium. In some embodiments, memory 810 includes volatile computer storage media. For example, memory 810 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 810 includes non-volatile computer storage media. For example, memory 810 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 810 includes both volatile and non-volatile computer storage media.

[0118] In some embodiments, memory 810 stores data related to CSI enhancements for higher frequencies. For example, memory 810 may store parameters, configurations, resource assignments, policies, etc., as described above. In some embodiments, memory 810 also stores program code and related data, such as an operating system or other controller algorithms running on user equipment device 800, and one or more software applications.

[0119] In one embodiment, input device 815 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. In some embodiments, input device 815 may be integrated with output device 820, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 815 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 815 includes two or more different devices, such as a keyboard and a touch panel.

[0120] In one embodiment, output device 820 is designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 820 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, output device 820 may include, but is not limited to, LCD displays, LED displays, OLED displays, projectors, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, output device 820 may include a wearable display, such as a smartwatch, smart glasses, head-up display, etc., that is separate from but communicatively coupled to the rest of user equipment device 800. Furthermore, output device 820 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0121] In some embodiments, output device 820 includes one or more speakers for generating sound. For example, output device 820 may generate an auditory alarm or notification (e.g., a beep or ringtone). In some embodiments, output device 820 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of output device 820 may be integrated with input device 815. For example, input device 815 and output device 820 may form a touchscreen or similar touch-sensitive display. In other embodiments, output device 820 may be located near input device 815.

[0122] Transceiver 825 includes at least a transmitter 830 and at least one receiver 835. Transceiver 825 can be used to provide UL communication signals to base station unit 121 and to receive DL communication signals from base station unit 121, as described herein. Similarly, transceiver 825 can be used to transmit and receive SL signals (e.g., V2X communication), as described herein. Although only one transmitter 830 and one receiver 835 are illustrated, user equipment device 800 can have any suitable number of transmitters 830 and receivers 835. Furthermore, transmitters 830 and receivers 835 can be of any suitable type. In one embodiment, transceiver 825 includes a first transmitter / receiver pair for communicating with a mobile communication network on licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network on unlicensed radio spectrum.

[0123] In some embodiments, a first transmitter / receiver pair for communicating with a mobile communication network on licensed radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network on unlicensed radio spectrum may be combined into a single transceiver unit, such as a single chip performing functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, certain transceivers 825, transmitters 830, and receivers 835 may be implemented as physically separate components that access shared hardware and / or software resources, such as, for example, a network interface 840.

[0124] In various embodiments, one or more transmitters 830 and / or one or more receivers 835 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an ASIC, or other types of hardware components. In some embodiments, one or more transmitters 830 and / or one or more receivers 835 may be implemented and / or integrated into a multi-chip module. In some embodiments, other components such as network interface 840 or other hardware components / circuitets may be integrated into a single chip along with any number of transmitters 830 and / or receivers 835. In such embodiments, transmitters 830 and receivers 835 may be logically configured as a transceiver 825 using a plurality of common control signals or as modular transmitters 830 and receivers 835 implemented in the same hardware chip or multi-chip module.

[0125] Figure 9This description depicts one embodiment of a network device 900 that can be used for mapping irregular resource elements according to embodiments of the present disclosure. In some embodiments, the network device 900 may be an embodiment of a RAN node and its supporting hardware, such as base station unit 121 and / or gNB as described above. Furthermore, the network device 900 may include a processor 905, a memory 910, an input device 915, an output device 920, and a transceiver 925. In some embodiments, the network device 900 does not include any input device 915 and / or output device 920.

[0126] As depicted, transceiver 925 includes at least one transmitter 930 and at least one receiver 935. Here, transceiver 925 communicates with one or more remote units 105. Additionally, transceiver 925 may support at least one network interface 940 and / or application interface 945. Application interface 945 may support one or more APIs. Network interface 940 may support 3GPP reference points, such as Uu, N1, N2, N3, N5, N6, and / or N7 interfaces. Other network interfaces 940 may be supported, as will be understood by those skilled in the art.

[0127] In one embodiment, processor 905 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 905 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), digital signal processor (“DSP”), coprocessor, dedicated processor, or similar programmable controller. In some embodiments, processor 905 executes instructions stored in memory 910 to perform the methods and routines described herein. Processor 905 is communicatively coupled to memory 910, input device 915, output device 920, and transceiver 925. In some embodiments, processor 905 may include an application processor (also referred to as a “main processor”) that manages application domain and operating system (“OS”) functions, and a baseband processor (also referred to as a “baseband radio processor”) that manages radio functions.

[0128] In various embodiments, processor 905 controls network device 900 to implement the aforementioned network entity behavior for irregular resource element mapping (e.g., gNB). In one embodiment, transceiver 925 is operable to communicate with user equipment (“UE”) devices. In a further embodiment, processor 905 generates a resource element mapping configuration based on carrier frequencies, including an indication of irregular subcarrier spacing for multiple subcarriers used by the UE device. In one embodiment, processor 905 transmits the resource element mapping configuration to the UE device via transceiver 925.

[0129] In one embodiment, memory 910 is a computer-readable storage medium. In some embodiments, memory 910 includes volatile computer storage media. For example, memory 910 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 910 includes non-volatile computer storage media. For example, memory 910 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 910 includes both volatile and non-volatile computer storage media.

[0130] In some embodiments, memory 910 stores data related to higher frequency CSI enhancements. For example, memory 910 may store parameters, configurations, resource assignments, policies, etc., as described above. In some embodiments, memory 910 also stores program code and related data, such as an operating system (“OS”) or other controller algorithms running on network device 900, and one or more software applications.

[0131] In one embodiment, input device 915 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. In some embodiments, input device 915 may be integrated with output device 920, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 915 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 915 includes two or more different devices, such as a keyboard and a touch panel.

[0132] In one embodiment, output device 920 may include any known electronically controllable display or display device. Output device 920 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, output device 920 includes an electronic display capable of outputting visual data to a user. Furthermore, output device 920 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0133] In some embodiments, the output device 920 includes one or more speakers for generating sound. For example, the output device 920 may generate an auditory alarm or notification (e.g., a beep or ringtone). In some embodiments, the output device 920 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of the output device 920 may be integrated with the input device 915. For example, the input device 915 and the output device 920 may form a touchscreen or similar touch-sensitive display. In other embodiments, all or part of the output device 920 may be located near the input device 915.

[0134] As discussed above, transceiver 925 can communicate with one or more remote units and / or with one or more interoperability functions that provide access to one or more PLMNs. Transceiver 925 can also communicate with one or more network functions (e.g., in mobile core network 80). Transceiver 925 operates under the control of processor 905 to transmit and receive messages, data, and other signals. For example, processor 905 can selectively activate the transceiver (or a portion thereof) at specific times to transmit and receive messages.

[0135] Transceiver 925 may include one or more transmitters 930 and one or more receivers 935. In some embodiments, one or more transmitters 930 and / or one or more receivers 935 may share transceiver hardware and / or circuitry. For example, one or more transmitters 930 and / or one or more receivers 935 may share antennas, antenna tuners, amplifiers, filters, oscillators, mixers, modulators / demodulators, power supplies, etc. In one embodiment, transceiver 925 implements multiple logical transceivers using different communication protocols or protocol stacks while using common physical hardware.

[0136] Figure 10 This is a flowchart of a method 1000 for mapping irregular resource elements. Method 1000 can be executed by a user device such as remote unit 105 and / or user equipment device 800. In some embodiments, method 1000 can be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0137] In one embodiment, method 900 receives at the UE device 1005 a resource element mapping configuration including an indication of irregular subcarrier spacing for a plurality of subcarriers of the UE device. The resource element mapping configuration may be defined by the radio access network (“RAN”) based on carrier frequencies. In another embodiment, method 1000 applies the indicated irregular subcarrier spacing 1010 to the resource elements (“REs”) of the UE device according to the resource element mapping configuration for communication with the RAN, and method 1000 terminates.

[0138] Figure 11 This is a flowchart of a method 1100 for mapping irregular resource elements. Method 1100 can be executed by a RAN node such as base station unit 110 and / or network device device 1100. In some embodiments, method 1100 can be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0139] In one embodiment, method 1100 generates, at a radio access network (“RAN”) device, a resource element mapping configuration based on carrier frequencies, 1105 including an indication of irregular subcarrier spacing for a plurality of subcarriers used by a user equipment (“UE”) device. Method 1100 sends the resource element mapping configuration to the UE device, and method 1100 terminates.

[0140] This document discloses a first apparatus for irregular resource element mapping according to embodiments of the present disclosure. The first apparatus may be implemented by a user equipment such as remote unit 105 and / or user equipment apparatus 800. In one embodiment, the first apparatus includes a transceiver operable to communicate with a radio access network (“RAN”). In a further embodiment, the first apparatus includes a processor that receives, via the transceiver, a resource element mapping configuration including an indication of irregular subcarrier spacing for a plurality of subcarriers for a UE, the resource element mapping configuration being defined by the RAN based on carrier frequencies. In one embodiment, the processor applies the indicated irregular subcarrier spacing to resource elements (“REs”) of the UE according to the resource element mapping configuration for communication with the RAN.

[0141] In one embodiment, the indication of irregular subcarrier spacing includes a parameter indicating the frequency offset between multiple subcarriers. In some embodiments, the offset between two subcarriers closer to the baseband DC (“DC”) is a higher frequency offset than the frequency offset between two different subcarriers farther from the baseband DC. In various embodiments, the frequency offset is determined based on at least one of the following: frequency range, bandwidth, default subcarrier spacing, modulation and coding scheme, regulatory requirements, and whether the baseband DC subcarrier position is offset by 7.5 kHz relative to the center of the indicated subcarrier. In one embodiment, each RE is centered on a subcarrier and the multiple REs are centered in the frequency domain at the default subcarrier spacing, with the irregular subcarrier spacing including the frequency offset realizing the subcarrier spacing between REs offset from the default subcarrier spacing.

[0142] In some embodiments, resource blocks (“RBs”) of the UE device are divided into different sets with different subcarrier offsets according to a resource element mapping configuration. In various embodiments, the indication of irregular subcarrier spacing includes a parameter indicating the frequency offset between subcarriers in each set of RBs of the UE device, such that for each set of RBs, the offset between two subcarriers closer to the baseband DC (“DC”) is a higher frequency offset than the frequency offset between two different subcarriers farther from the baseband DC.

[0143] In some embodiments, the set of RBs within a threshold frequency of DC is muted, while different sets of RBs outside the threshold frequency use a default subcarrier spacing, and the muted set of RBs does not carry any data. In one embodiment, the muted set of RBs is configured to transmit a phase tracking reference signal (“PTRS”), which is used for common phase error (“CPE”) / inter-carrier interference (“ICI”) estimation and for eliminating CPE / ICI on data subcarriers transmitted using the default SCS.

[0144] In one embodiment, the resource element mapping configuration for subcarriers of the set of RBs for the queued REs includes at least one queued RE that coincides with the location of the transmitted DC subcarrier when the location of the transmitted DC subcarrier is within the resource grid of the UE device. In another embodiment, the processor receives auxiliary information via a transceiver, which includes information about the location of punched bits corresponding to the queued REs of the set of RBs, such that the punched bits of the queued REs are ignored during decoding.

[0145] In one embodiment, the processor receives rate matching parameters via a transceiver that take into account irregular mapping of REs. These parameters include an indication of the number and location of empty subcarriers used for rate matching calculations. In some embodiments, in response to the failure to receive rate matching parameters and in response to the lack of use of empty REs, the UE performs normal reception and decoding of a transport block (“TB”).

[0146] This document discloses a first method for irregular resource element mapping according to embodiments of the present disclosure. The first method can be performed by a user equipment, such as remote unit 105 and / or user equipment device 800. The first method includes receiving at the user equipment (“UE”) a resource element mapping configuration including an indication of irregular subcarrier spacing for a plurality of subcarriers for the UE, the resource element mapping configuration being defined by a radio access network (“RAN”) based on carrier frequencies. In another embodiment, the first method includes applying the indicated irregular subcarrier spacing to resource elements (“REs”) of the UE device according to the resource element mapping configuration for communication with the RAN.

[0147] In one embodiment, the indication of irregular subcarrier spacing includes a parameter indicating the frequency offset between multiple subcarriers. In some embodiments, the offset between two subcarriers closer to the baseband DC (“DC”) is a higher frequency offset than the frequency offset between two different subcarriers farther from the baseband DC. In various embodiments, the frequency offset is determined based on at least one of the following: frequency range, bandwidth, default subcarrier spacing, modulation and coding scheme, regulatory requirements, and whether the baseband DC subcarrier position is offset by 7.5 kHz relative to the center of the indicated subcarrier. In one embodiment, each RE is centered on a subcarrier and the multiple REs are centered in the frequency domain at the default subcarrier spacing, with the irregular subcarrier spacing including the frequency offset realizing the subcarrier spacing between REs offset from the default subcarrier spacing.

[0148] In some embodiments, resource blocks (“RBs”) of the UE device are divided into different sets with different subcarrier offsets according to a resource element mapping configuration. In various embodiments, the indication of irregular subcarrier spacing includes a parameter indicating the frequency offset between subcarriers in each set of RBs of the UE device, such that for each set of RBs, the offset between two subcarriers closer to the baseband DC (“DC”) is a higher frequency offset than the frequency offset between two different subcarriers farther from the baseband DC.

[0149] In some embodiments, the set of RBs within a threshold frequency of DC is muted, while different sets of RBs outside the threshold frequency use a default subcarrier spacing, and the muted set of RBs does not carry any data. In one embodiment, the muted set of RBs is configured to transmit a phase tracking reference signal (“PTRS”), which is used for common phase error (“CPE”) / inter-carrier interference (“ICI”) estimation and for eliminating CPE / ICI on data subcarriers transmitted using the default SCS.

[0150] In one embodiment, the resource element mapping configuration for subcarriers of the set of RBs for the queued REs includes at least one queued RE that coincides with the location of the transmitted DC subcarrier when the location of the transmitted DC subcarrier is within the resource grid of the UE device. In another embodiment, the first method includes receiving auxiliary information at the UE device, the auxiliary information including information about the location of punched bits corresponding to the queued REs of the set of RBs, such that the punched bits of the queued REs are ignored during decoding.

[0151] In one embodiment, the first method includes receiving rate matching parameters at the UE device that take into account irregular mapping of REs, including an indication of the number and location of empty subcarriers used for rate matching calculation. In some embodiments, in response to not receiving rate matching parameters and in response to not using empty REs, the UE device performs normal reception and decoding of a transport block (“TB”).

[0152] This document discloses a second apparatus for irregular resource element mapping according to embodiments of the present disclosure. The second apparatus may be implemented by a RAN node such as base station unit 110 and / or network equipment apparatus 900. The second apparatus includes a transceiver, in one embodiment operable to communicate with a user equipment (“UE”) device. In another embodiment, the second apparatus includes a processor that generates a resource element mapping configuration based on a carrier frequency, including an indication of irregular subcarrier spacing for a plurality of subcarriers for the UE device. In one embodiment, the processor transmits the resource element mapping configuration to the UE device via the transceiver.

[0153] In one embodiment, the indication of irregular subcarrier spacing includes a parameter indicating the frequency offset between multiple subcarriers. In some embodiments, the offset between two subcarriers closer to the baseband DC (“DC”) is a higher frequency offset than the frequency offset between two different subcarriers farther from the baseband DC. In various embodiments, the frequency offset is determined based on at least one of the following: frequency range, bandwidth, default subcarrier spacing, modulation and coding scheme, regulatory requirements, and whether the baseband DC subcarrier position is offset by 7.5 kHz relative to the center of the indicated subcarrier. In one embodiment, each RE is centered on a subcarrier and the multiple REs are centered in the frequency domain at the default subcarrier spacing, with the irregular subcarrier spacing including the frequency offset realizing the subcarrier spacing between REs offset from the default subcarrier spacing.

[0154] In some embodiments, resource blocks (“RBs”) of the UE device are divided into different sets with different subcarrier offsets according to a resource element mapping configuration. In various embodiments, the indication of irregular subcarrier spacing includes a parameter indicating the frequency offset between subcarriers in each set of RBs of the UE device, such that for each set of RBs, the offset between two subcarriers closer to the baseband DC (“DC”) is a higher frequency offset than the frequency offset between two different subcarriers farther from the baseband DC.

[0155] In some embodiments, the set of RBs within a threshold frequency of DC is muted, while different sets of RBs outside the threshold frequency use a default subcarrier spacing, and the muted set of RBs does not carry any data. In one embodiment, the muted set of RBs is configured to transmit a phase tracking reference signal (“PTRS”), which is used for common phase error (“CPE”) / inter-carrier interference (“ICI”) estimation and for eliminating CPE / ICI on data subcarriers transmitted using the default SCS.

[0156] In one embodiment, the resource element mapping configuration for subcarriers of the set of RBs for the queued REs includes at least one queued RE that coincides with the location of the transmitted DC subcarrier when the location of the transmitted DC subcarrier is within the resource grid of the UE device. In another embodiment, the processor transmits auxiliary information to the UE device via a transceiver, the auxiliary information including information about the location of the punched bits corresponding to the queued REs of the set of RBs, such that the punched bits of the queued REs are ignored during decoding.

[0157] In one embodiment, the processor sends rate matching parameters, taking into account irregular mapping of REs, to the UE via a transceiver. These parameters include an indication of the number and location of empty subcarriers used for rate matching calculations.

[0158] This document discloses a second method for irregular resource element mapping according to embodiments of the present disclosure. The second method can be performed by a network device apparatus 900. The second method includes generating a resource element mapping configuration at a radio access network (“RAN”) device, based on a carrier frequency, including an indication of irregular subcarrier spacing for a plurality of subcarriers used by a user equipment (“UE”) device. In another embodiment, the second method includes sending the resource element mapping configuration to the UE device.

[0159] In one embodiment, the indication of irregular subcarrier spacing includes a parameter indicating the frequency offset between multiple subcarriers. In some embodiments, the offset between two subcarriers closer to the baseband DC (“DC”) is a higher frequency offset than the frequency offset between two different subcarriers farther from the baseband DC. In various embodiments, the frequency offset is determined based on at least one of the following: frequency range, bandwidth, default subcarrier spacing, modulation and coding scheme, regulatory requirements, and whether the baseband DC subcarrier position is offset by 7.5 kHz relative to the center of the indicated subcarrier. In one embodiment, each RE is centered on a subcarrier and the multiple REs are centered in the frequency domain at the default subcarrier spacing, with the irregular subcarrier spacing including the frequency offset realizing the subcarrier spacing between REs offset from the default subcarrier spacing.

[0160] In some embodiments, resource blocks (“RBs”) of the UE device are divided into different sets with different subcarrier offsets according to a resource element mapping configuration. In various embodiments, the indication of irregular subcarrier spacing includes a parameter indicating the frequency offset between subcarriers in each set of RBs of the UE device, such that for each set of RBs, the offset between two subcarriers closer to the baseband DC (“DC”) is a higher frequency offset than the frequency offset between two different subcarriers farther from the baseband DC.

[0161] In some embodiments, the set of RBs within a threshold frequency of DC is muted, while different sets of RBs outside the threshold frequency use a default subcarrier spacing, and the muted set of RBs does not carry any data. In one embodiment, the muted set of RBs is configured to transmit a phase tracking reference signal (“PTRS”), which is used for common phase error (“CPE”) / inter-carrier interference (“ICI”) estimation and for eliminating CPE / ICI on data subcarriers transmitted using the default SCS.

[0162] In one embodiment, the resource element mapping configuration for subcarriers of the set of RBs for the queued REs includes at least one queued RE that coincides with the location of the transmitted DC subcarrier when the location of the transmitted DC subcarrier is within the resource grid of the UE device. In another embodiment, the second method includes sending auxiliary information to the UE device, the auxiliary information including information about the location of punched bits corresponding to the queued REs of the set of RBs, such that the punched bits of the queued REs are ignored during decoding.

[0163] In one embodiment, the second method includes sending rate matching parameters to the UE device that take into account the irregular mapping of REs, including an indication of the number and location of empty subcarriers used for rate matching calculation.

[0164] The embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects as illustrative rather than restrictive. Therefore, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All variations within the equivalent meaning and scope of the claims should be covered within their scope.

Claims

1. A method executed by a user equipment (UE), comprising: Receives a resource element mapping configuration including an indication of irregular subcarrier spacing of multiple subcarriers, wherein the resource element mapping configuration is based on carrier frequency, and wherein the resource element mapping configuration defines a set of different resource blocks (RBs) with different subcarrier offsets; and The indicated irregular subcarrier spacing is applied to the resource element RE according to the resource element mapping configuration. Wherein, the offset between two subcarriers that are closer to the baseband DC is a higher frequency offset than the frequency offset between two different subcarriers that are farther from the baseband DC.

2. The method according to claim 1, wherein, The indication of the irregular subcarrier spacing includes a parameter indicating the frequency offset between the plurality of subcarriers.

3. The method according to claim 1, wherein, The frequency offset is determined based on at least one of the following: frequency range, bandwidth, default subcarrier spacing, modulation and coding scheme, regulatory requirements, and whether the baseband DC subcarrier position is offset by 7.5 kHz relative to the center of the indicated subcarrier.

4. The method according to claim 2, wherein, Each RE is centered on a subcarrier, and the plurality of REs are centered in the frequency domain on a default subcarrier spacing, including the irregular subcarrier spacing with frequency offset, which realizes the subcarrier spacing between REs offset from the default subcarrier spacing.

5. The method according to claim 1, wherein, The indication of the irregular subcarrier spacing includes a parameter indicating the frequency offset between subcarriers in each set of RBs of the UE, such that for each set of RBs, the offset between two subcarriers closer to the baseband DC is a higher frequency offset than the frequency offset between two different subcarriers farther from the baseband DC.

6. The method according to claim 4, wherein, The set of RBs within the threshold frequency of the baseband DC is muted, while different sets of RBs outside the threshold frequency use the default subcarrier spacing SCS, and the muted set of RBs does not carry any data.

7. The method according to claim 6, wherein, The squeuing set of the RBs is configured to transmit a phase tracking reference signal PTRS, which is used for common phase error (CPE) / inter-carrier interference (ICI) estimation and for eliminating CPE / ICI on data subcarriers transmitted using the default SCS.

8. The method according to claim 6, wherein, The resource element mapping configuration for the subcarriers of the set of RBs includes at least one squeezed RE that coincides with the location of the transmitted DC subcarrier when the location of the transmitted DC subcarrier is within the resource grid.

9. The method of claim 6, further comprising receiving auxiliary information, the auxiliary information including information about the position of the punched bit corresponding to the set of RBs in a squashed RE, such that the punched bit of the squashed RE is ignored during decoding.

10. The method of claim 1, further comprising receiving rate matching parameters taking into account the irregular subcarrier spacing of the RE, the parameters including an indication of the number and location of empty subcarriers for rate matching calculation.

11. The method of claim 10, further comprising performing normal reception and decoding of the transport block TB in response to the absence of a rate matching parameter and in response to the absence of an empty RE.

12. A user equipment (UE), comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured to cause the UE to: Receives a resource element mapping configuration including an indication of irregular subcarrier spacing of multiple subcarriers, wherein the resource element mapping configuration is based on carrier frequency, and wherein the resource element mapping configuration defines a set of different resource blocks (RBs) with different subcarrier offsets; and The indicated irregular subcarrier spacing is applied to the resource element RE according to the resource element mapping configuration. Wherein, the offset between two subcarriers that are closer to the baseband DC is a higher frequency offset than the frequency offset between two different subcarriers that are farther from the baseband DC.

13. The UE according to claim 12, wherein, The indication of the irregular subcarrier spacing includes a parameter indicating the frequency offset between the plurality of subcarriers.

14. The UE according to claim 12, wherein, The indication of the irregular subcarrier spacing includes a parameter indicating the frequency offset between subcarriers in each set of RBs, such that for each set of RBs, the offset between two subcarriers closer to the baseband DC is a higher frequency offset than the frequency offset between two different subcarriers farther from the baseband DC.

15. The UE according to claim 14, wherein, The set of RBs within the threshold frequency of the baseband DC is muted, while different sets of RBs outside the threshold frequency use the default subcarrier spacing, and the muted set of RBs does not carry any data.

16. The UE according to claim 12, wherein, The at least one processor is configured to cause the UE to: receive rate matching parameters taking into account the irregular subcarrier spacing of the RE, the parameters including an indication of the number and location of empty subcarriers for rate matching calculation.

17. A network device NE, comprising: At least one memory; as well as At least one processor, said at least one processor being coupled to said at least one memory, and configured to cause the NE: Determine a resource element mapping configuration that includes an indication of irregular subcarrier spacing comprising multiple subcarriers, wherein the resource element mapping configuration is based on carrier frequency, and wherein the resource element mapping configuration defines a set of different resource blocks (RBs) with different subcarrier offsets; and Send the resource element mapping configuration, wherein the offset between two subcarriers closer to the baseband DC is a higher frequency offset than the frequency offset between two different subcarriers farther from the baseband DC.

18. A method performed by a network device NE, the method comprising: Determine a resource element mapping configuration that includes an indication of irregular subcarrier spacing comprising multiple subcarriers, wherein the resource element mapping configuration is based on carrier frequency, and wherein the resource element mapping configuration defines a set of different resource blocks (RBs) with different subcarrier offsets; and Send the resource element mapping configuration. Wherein, the offset between two subcarriers that are closer to the baseband DC is a higher frequency offset than the frequency offset between two different subcarriers that are farther from the baseband DC.

Images