Patent Application
20230309028
The subject matter disclosed herein generally relates to wireless communications, and more particularly relates to downlink (DL) power allocation for NBIoT.
The following abbreviations are herewith defined, at least some of which are referred to within the following description: Third Generation Partnership Project (3GPP), European Telecommunications Standards Institute (ETSI), Frequency Division Duplex (FDD), Frequency Division Multiple Access (FDMA), Long Term Evolution (LTE), New Radio (NR), Very Large Scale Integration (VLSI), Random Access Memory (RAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM or Flash Memory), Compact Disc Read-Only Memory (CD-ROM), Local Area Network (LAN), Wide Area Network (WAN), Personal Digital Assistant (PDA), User Equipment (UE), Uplink (UL), Evolved Node B (eNB), Next Generation Node B (gNB), Downlink (DL), Central Processing Unit (CPU), Graphics Processing Unit (GPU), Field Programmable Gate Array (FPGA), Dynamic RAM (DRAM), Synchronous Dynamic RAM (SDRAM), Static RAM (SRAM), Liquid Crystal Display (LCD), Light Emitting Diode (LED), Organic LED (OLED), Orthogonal Frequency Division Multiplexing (OFDM), Radio Resource Control (RRC), Reference Signal (RS), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time-Division Duplex (TDD), Time Division Multiplex (TDM), User Entity/Equipment (Mobile Terminal) (UE), Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), Internet-of-Things (IoT), Narrowband Internet-of-Things (NB-IoT or NBIoT), Long Term Evolution (LTE), Narrowband (NB), Physical Downlink Shared Channel (PDSCH), Narrowband Physical Downlink Shared Channel (NPDSCH), Physical Resource Block (PRB), Universal Mobile Telecommunications System (UMTS), Evolved-UMTS Terrestrial Radio Access (E-UTRA or EUTRA), Quadrature Phase Shift Keying (QPSK), Quadrature Amplitude Modulation (QAM), Cyclic Prefix (CP), resource element (RE), Cell Reference Signal (CRS), energy per resource element (EPRE), Multi-User Multiple-Input Multiple-Output (MU MIMO), Automatic Gain Control (AGC), Narrowband reference signal (NRS).
The downlink (DL) power allocation for LTE is described as a background.
There are two types of OFDM symbols for LTE downlink power allocation. In the following description, OFDM symbol is abbreviated as symbol for simplicity. In condition of normal CP (Cyclic Prefix), one slot has 7 symbols; and in condition of extended CP, one slot has 6 symbols.
Depending on the presence or non-presence of CRS RE in symbols, the symbols in one slot are divided into two types (Type A symbol and Type B symbol). If all REs in a symbol, which do not contain any CRS RE (indicated as R0 in
The EPRE (energy per resource element) of CRS RE (i.e. CRS EPRE, abbreviated as E_RS) is constant across downlink system bandwidth, and is configured by a higher layer parameter referenceSignalPower. The CRS EPRE (E_RS) is cell-specific. The ratio of PDSCH EPRE to cell-specific CRS EPRE among PDSCH REs (not applicable to PDSCH REs with zero EPRE) for each OFDM symbol (e.g., including Type A symbol and Type B symbol) is denoted by either ρA or ρB according to the OFDM symbol index as given by the following Table 1.
Detailed explanations are given. Each type A symbol is comprised only of PDSCH REs (e.g. in
ρA, which is UE-specific, is determined by PA, and in particular, PA[dB]=10 lgρA except for 4TX diversity and MU MIMO. PA is UE-specific configured by a higher layer parameter p-a from a set of {−6, −4.77, −3, −1.77, 0, 1, 2, 3}[dB]. Accordingly, PA is a number chosen from a set of {¼, ⅓, ½, ⅔, 1, 1.2589, 1.5849, 2}.
ρB is determined by PB. In particular, ρB/ρA is determined by the value of PB. PB is the PDSCH EPRE power index, and is cell-specific configured by a higher layer parameter p-b from a set of {0, 1, 2, 3}.
In summary, the eNB can configure the downlink power allocation with three parameters: referenceSignalPower, PA and PB.
Take one PRB PDSCH transmission as an example. S_A denotes the total power of one type A symbol which is comprised of 12 PDSCH REs, i.e. S_A=12*E_A. S_B denotes the total power of one type B symbol. For example, in the example of
Some examples of the power efficiency in different configurations of PA and PB are shown in
There are a number of factors that are necessary to be considered when the eNB configures PA and PB, e.g. total power for each OFDM, EPRE, RS power boosting for converge, power saving, interference. For example, the eNB may offload some PRB(s) (which means that only “CRS” REs are transmitted while no PDSCH REs are transmitted in those PRB(s)) or may boost CRS power to adjust the configuration of PA and PB. When two types of symbols have different powers (i.e. S_A*S_B), eNB will clip the higher power symbols or use less power. In this condition, the UE will adjust AGC (Automatic Gain Control) based on peak power or averaging power or lowest power, which would degrade the detection performance. Anyway, UE is expected to receive almost same power for each symbol.
As a matter of fact, only some of configurations of PA and PB may lead to the same power of the two types of symbols, which achieves the highest power efficiency (100%). Examples of such configurations of PA and PB may be as follows: (PA[dB], PB)=(0, 0), (−3, 1), (−4.77, 2), (−6, 3). From operator (eNB) point of view, most of the configurations of PA and PB combination will not be configured, e.g., (PA[dB], PB)=(3, 3), (2, 3), (−6, 0) due to lower power efficiency.
As described above, in LTE, due to the presence of CRS REs in type B symbols, the EPRE of each PDSCH RE in type A symbols (E_A) and the EPRE of each PDSCH RE in type B symbols (E_B) can be configured by the eNB by configuring PA and PB to implement the downlink power allocation.
In case of NBIoT, the downlink power allocation is different.
In NBIoT (inband deployment or standalone deployment or guardband deployment), the downlink REs can be NPDSCH REs or NRS (Narrowband reference signal) REs. In case of inband deployment, the downlink REs may alternatively be CRS REs.
The UE may assume that the EPRE of NRS REs (NRS EPRE) is constant across the downlink NBIoT system bandwidth and constant across all subcarriers that contain NRS.
The UE may assume the ratio of NPDSCH EPRE to NRS EPRE among NPDSCH REs (not applicable to NPDSCH REs with zero EPRE) is 0 dB for an NBIoT cell with one NRS antenna port and −3 dB for an NBIoT cell with two NRS antenna ports.
If higher layer parameter operationModelnfo indicates ‘00’ or samePCI-Indicator indicates ‘samePC’ for a cell, the ratio of NRS EPRE to CRS EPRE is given by the parameter nrs-CRS-PowerOffset if the parameter nrs-CRS-PowerOffset is provided by higher layers.
It can be seen that each type of REs (NRS RE, NPDSCH RE, CRS RE) is associated with a specific EPRE (NRS EPRE, NPDSCH EPRE, CRS EPRE), which means that the eNB transmits each type of REs with the power indicated by each specific EPRE while the UE assumes the same. In Release 13 NBIoT, the actual EPRE of NBIoT (e.g. NPDSCH EPRE) except the NRS EPRE is up to eNB implementation. In Release 13 NBIoT, only QPSK is supported (i.e. 16QAM is not supported). The UE does not need to know the exact value of powers (ERPEs) to perform the demodulation. Therefore, eNB can transmit NPDSCH with any power, so long as the NRS power is constant.
Although any EPRE of NBIoT PDSCH is detectable (can be demodulated), UE is expected to receive almost same power for each PRB to adjust the AGC.
In Release 17 NBIoT, 16QAM will be supported. Therefore, the UE needs to know the transmission powers (EPRE) of NPDSCH to correctly perform the demodulation. It is an object of the present invention to propose methods and apparatuses for NBIoT downlink power allocation, especially when 16QAM is supported in Release 17 NBIoT.
It might be straight forward to use the LTE downlink power allocation as a baseline for NBIoT downlink power allocation in Release 17 NBIoT. However, it is not possible to directly use the LTE downlink power allocation at least due to the following differences between LTE and NBIoT.
First, as described above, for NBIoT inband deployment, downlink REs can be three types: PDSCH REs or NRS REs or CRS REs. Accordingly, there are three types of OFDM symbols (e.g., OFDM symbols with NRS, OFDM symbols with CRS, and OFDM symbols without NRS or CRS). So, it is not appropriate to only define two types of symbols as in LTE downlink power allocation.
Secondly, UE of LTE system receives the downlink signal with a bandwidth of 20 MHz and the PDSCH bandwidth can be determined by eNB scheduling. However, UE of NBIoT receives the downlink signal with bandwidth of 1 PRB and PDSCH bandwidth is fixed as 1 PRB at least for inband deployment.
For example, as shown in
Therefore, in NBIoT, it has to design the power to be the same per PRB per symbol.
Methods and apparatuses for downlink power allocation for NBIoT are disclosed.
In one embodiment, a method comprises receiving a first reference signal (NRS), a first data and a second data, wherein the first reference signal is associated with a first transmission power (E_NRS); the first data is in a symbol without the first reference signal, and the first data is associated with a second transmission power (E_A); and the second data is in a symbol in which the first reference signal is received; and the second data is associated with a third transmission power (E_B). The second transmission power (E_A) may be determined by the first transmission power (E_NRS) and a first power ratio (ρA). The third transmission power (E_B) may be determined by the first transmission power (E_NRS) and a second power ratio (ρB). The second power ratio (ρB) may be determined by a first power ratio (ρA) and the number of antenna ports of the first reference signal (NRS).
In one embodiment, the method further comprises receiving a second reference signal (CRS) and a third data, wherein the second reference signal is associated with a fourth transmission power (E_CRS); and the third data is in a symbol in which the second reference signal is received; and the third data is associated with a fifth transmission power (E_C). The fourth transmission power (E_CRS) may be determined by the first transmission power (E_NRS) and a third power ratio (ρCRS). The fifth transmission power (E_C) may be determined by the first transmission power (E_NRS) and a fourth power ratio (ρC).
In another embodiment, the fourth power ratio (ρC) may be determined by at least one of the number of antenna ports of the first reference signal (NRS), the number of antenna ports of the second reference signal (CRS), a first power ratio (ρA), a second power ratio (ρB), a third power ratio (ρCRS) and a predefined power ratio value (M).
In some embodiment, the fourth power ratio (ρC) is determined by the first power ratio (ρA) and the number of antenna ports of the second reference signal (CRS). In other embodiment, the fourth power ratio (ρC) is determined by at least one of a first power ratio value (ρC1) determined by the first power ratio (ρA) and the third power ratio (ρCRS), a second power ratio value (ρC2) determined by the second power ratio (ρB) and the third power ratio (ρCRS), and the predefined power ratio value (M).
In some embodiment, the fourth power ratio (ρC) is determined by a larger or smaller value of at least two of the first power ratio value (ρC1), the second power ratio value (ρC2) and the predefined power ratio value (M). The fourth power ratio (ρC) ma be indicated by higher layer signaling from the first power ratio value (ρC1) and the second power ratio value (ρC2). The fourth power ratio (ρC) may alternatively be a value chosen from a predefined power ratio set, the value is the smallest value of the set that is larger than one of the first power ratio value (ρC1) and the second power ratio value (ρC2), or the largest value of the set that is smaller than said one of the first power ratio value (ρC1) and the second power ratio value (ρC2).
In one embodiment, a remote unit comprises a receiver that receives a first reference signal (NRS), a first data and a second data, wherein the first reference signal is associated with a first transmission power (E_NRS); the first data is in a symbol without the first reference signal, and the first data is associated with a second transmission power (E_A); and the second data is in a symbol in which the first reference signal is received; and the second data is associated with a third transmission power (E_B). The second transmission power (E_A) may be determined by the first transmission power (E_NRS) and a first power ratio (ρA). The third transmission power (E_B) may be determined by the first transmission power (E_NRS) and a second power ratio (ρB). The second power ratio (ρB) may be determined by a first power ratio (ρA) and the number of antenna ports of the first reference signal (NRS).
In another embodiment, a method comprises transmitting a first reference signal (NRS), a first data and a second data, wherein the first reference signal is associated with a first transmission power (E_NRS); the first data is in a symbol without the first reference signal, and the first data is associated with a second transmission power (E_A); and the second data is in a symbol in which the first reference signal is transmitted; and the second data is associated with a third transmission power (E_B).
In yet another embodiment, a base unit comprises a transmitter that transmits a first reference signal (NRS), a first data and a second data, wherein the first reference signal is associated with a first transmission power (E_NRS); the first data is in a symbol without the first reference signal, and the first data is associated with a second transmission power (E_A); and the second data is in a symbol in which the first reference signal is transmitted; and the second data is associated with a third transmission power (E_B).
A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings.
Understanding that these drawings depict only some embodiments, and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
As will be appreciated by one skilled in the art that certain aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may generally all be referred to herein as a “circuit”, “module” or “system”. Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine-readable code, computer readable code, and/or program code, referred to hereafter as “code”. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
Certain functional units described in this specification may be labeled as “modules”, in order to more particularly emphasize their independent implementation. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but, may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.
Indeed, a module of code may contain a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. This operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.
Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but need not necessarily be, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
A non-exhaustive list of more specific examples of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash Memory), portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
Code for carrying out operations for embodiments may include any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and/or machine languages such as assembly languages. The code may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the very last scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Reference throughout this specification to “one embodiment”, “an embodiment”, or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment”, “in an embodiment”, and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including”, “comprising”, “having”, and variations thereof mean “including but are not limited to”, unless otherwise expressly specified. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, otherwise unless expressly specified. The terms “a”, “an”, and “the” also refer to “one or more” unless otherwise expressly specified.
Furthermore, described features, structures, or characteristics of various embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid any obscuring of aspects of an embodiment.
Aspects of different embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may 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 the instructions, which are executed via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the schematic flowchart diagrams and/or schematic block diagrams for the block or blocks.
The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices, to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices, to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code executed on the computer or other programmable apparatus provides processes for implementing the functions specified in the flowchart and/or block diagram block or blocks.
The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).
It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may substantially be executed concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, to the illustrated Figures.
Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.
The description of elements in each Figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.
As described in the background part, UE of NBIoT receives the downlink signal with bandwidth of 1 PRB and PDSCH bandwidth is fixed as 1 PRB for inband deployment. Therefore, it is necessary to determine the time domain power (EPRE) of NBIoT in one carrier or one PRB bandwidth (i.e. 12 subcarriers).
In NBIoT, the downlink REs can be NPDSCH REs or NRS REs.
In the example of
If all of 12 REs in a symbol, which do not contain any NRS (narrowband reference signal) RE (indicated as NO in
If the 12 REs in a symbol contain NPDSCH REs, e.g. contain both NRS REs and NPDSCH REs, the symbol belongs to type B symbol. Symbols 5 and 6 in
It can be seen from
Incidentally, the EPRE of the NRS REs of another NRS antenna port is zero (0).
S_A denotes the total power of one type A symbol within 1 PRB or 1 carrier which includes 12 PDSCH REs, i.e. S_A=12*E_A. S_B denotes the total power of one type B symbol within 1 PRB or 1 carrier. In
In case of inband deployment, the downlink REs may alternatively be CRS REs. Therefore, in case of inband deployment, the downlink REs can be NPDSCH REs or NRS REs or CRS REs.
In the example of
If all of 12 REs in a symbol, which do not contain any NRS RE (indicated as NO in
If the 12 REs in a symbol contain NRS REs, e.g., contain both NRS REs and NPDSCH REs, the symbol belongs to type B symbol. Symbols 5 and 6 in
If the 12 REs in a symbol contain CRS REs, e.g., contain both CRS REs and NPDSCH REs, the symbol belongs to type C symbol. Symbols 0 and 3 in
It can be seen from
S_A denotes the total power of one type A symbol within 1 PRB or 1 carrier which includes 12 PDSCH REs, i.e. S_A=12*E_A. S_B denotes the total power of one type B symbol within 1 PRB or 1 carrier. In
As can be seen from
EPREs in the PRB or carrier of
The EPRE of the NRS REs (e.g., NRS antenna port 0) is E_NRS. The EPRE of the CRS REs (e.g., CRS antenna port 0) is E_CRS. Accordingly, in the example of
As a whole, each NRS RE, each NPDSCH RE in type A symbols, each NPDSCH RE in type B symbols, each NPDSCH RE in type C symbols and each CRS RE are respectively associated with E_NRS, E_A, E_B, E_C and E_CRS. This means that eNB transmits data or reference signal in each NRS RE, each NPDSCH RE in type A symbols, each NPDSCH RE in type B symbols, each NPDSCH RE in type C symbols and each CRS RE with the powers of E_NRS, E_A, E_B, E_C and E_CRS, respectively, while the UE assumes the same (i.e. the UE assumes that the eNB transmits NBIoT reference signal in each NRS RE with the power of E_NRS, transmits data in each NPDSCH RE in type A symbols with the power of E_A, transmits data in each NPDSCH RE in type B symbols with the power of E_B, transmits data in each NPDSCH RE in type C symbols with the power of E_C, and transmits cell specific reference signal in each CRS RE with the power of E_CRS).
The NRS EPRE (E_NRS) is constant across downlink system bandwidth (i.e. 1 PRB), and is configured by higher layers. For example, the downlink NRS EPRE (E_NRS) can be derived from the downlink narrowband reference-signal transmit power given by nrs-Power+nrs-PowerOffsetNonAnchor, where the parameter nrs-Power is provided by higher layers and nrs-PowerOffsetNonAnchor is zero if it is not provided by higher layers.
The first embodiment is related to the configuration of the EPRE of each NPDSCH RE in type A symbols (E_A) and the EPRE of each NPDSCH RE in type B symbols (E_B).
The ratio of E_A to E_NRS is denoted by ρA=E_A/E_NRS. ρA is determined by PA, and in particular, PA[dB]=10 lgρA. PA is configured by higher layer parameter p-a from a set of {−6, −4.77, −3, −1.77, 0, 1, 2, 3}[dB]. According to PA[dB]=10 lgρA, ρA is a number chosen from a set of {¼, ⅓, ½, ⅔, 1, 1.2589, 1.5849, 2}.
The ratio of E_B to E_NRS is denoted by ρB=E_B/E_NRS.
ρB may be determined by PB. In particular, ρB/ρA is determined by the value of PB. PB is the NPDSCH EPRE power index, and is configured by a higher layer parameter p-b from a set of {0, 1, 2, 3}.
On the other hand, to facilitate the AGC by UE and at least for standalone deployment (to make sure that the power of type A symbol and type B symbol within 1 PRB or 1 carrier are same), ρB may be alternatively determined directly by ρA. For example, ρB=6 ρA/5−⅕ for one NRS antenna port, and ρB=3 ρA/2 −¼ for two NRS antenna ports.
The second embodiment is related to the configuration of the EPRE of each NPDSCH RE in type C symbols (E_C) and the EPRE of CRS RE (E_CRS).
The EPRE of CRS RE (E_CRS) is determined by a higher layer parameter nrs-CRS-PowerOffset (pCRS) on the basis of the NRS EPRE (E_NRS). That is, pCRS=E_CRS/E_NRS.
The E_C may be derived by introducing a parameter PC. In particular, the ratio of E_C to E_NRS is denoted by ρC=E_C/E_NRS. ρC is determined by PC, and in particular, PC[dB]=10 lgρC. PC is configured by a higher layer parameter p-c from a set of {−6, −4.77, −3, −1.77, 0, 1, 2, 3}[dB]. According to PC[dB]=10 lgρC, ρC is a number chosen from a set of {¼, ⅓, ½, ⅔, 1, 1.2589, 1.5849, 2}. When E_C is determined by the parameter PC, there is no constraint for the value of E_C by E_A and/or E_B and/or E_CRS. That is, if the power of S_C is larger than a larger one of S_A and S_B or smaller than a smaller one of S_A and S_B, the power efficiency will be reduced, such that the detection performance of the UE will be degraded due to inaccurate AGC.
In view of the above, the E_C may be alternatively derived by configuring the parameter PC in a different manner. In particular, the ratio of E_C to E_NRS is denoted by ρC=E_C/E_NRS. ρC may be determined by PC. In particular, ρC/ρA is determined by the value of PC. PC is configured by a higher layer parameter p-c from a set of {0, 1, 2, 3}.
The CRS port number is determined by the NRS antenna port number and some other higher layer parameters.
If the higher layer indicates that the PCID of LTE is the same as PCID of NBIoT, UE shall assume the number of CRS antenna ports is the same as the number of NRS antenna ports.
Otherwise, the number of CRS antenna ports is obtained from the higher layer parameter eutra-NumCRS-Ports. The higher layer parameter eutra-NumCRS-Ports can have a value “Same” (which means that the number of CRS antenna ports is the same as the number of NRS antenna ports) or “four” (which means that the number of CRS antenna ports is 4). As a whole, when the number of NRS antenna ports is 1, the number of CRS antenna ports can be 1 or 4; and when the number of NRS antenna ports is 2, the number of CRS antenna ports can be 2 or 4.
According to the second embodiment, the ratio of the EPRE of each NPDSCH RE in type C symbols (E_C) to NRS EPRE (E_NRS) is denoted by ρC, which seems to provide eNB with more configuration flexibility. However, the eNB is hard to configure all of the parameters PA, PB and PC to improve the power efficiency. Actually, some of the parameters are useless. For example, when S_A and S_B are determined by parameters PA and PB, the power range of S_C is almost determined (i.e. PC is also almost determined) if we don't want to even degrade the power efficiency and affect the UE AGC. In other words, there is no need to configure the parameter PC. If we force the eNB to configure the parameter PC, it will increase the load of network optimizations.
An example is illustrated in
In this condition, E_C should be boosted due to lower power of E_CRS. However, E_C can only be configured maximally as 40 dBm (when ρC/ρA=1 which is the maximum value for 1 CRS antenna port). In view of the above, even the configurations of PA, PB and PC are flexible, the power efficiency is still not high. No matter which value (power of 420 dBm or 480 dBm or 560 dBm) is selected by the UE to adjust the AGC, the performance of demodulation is largely degraded.
According to a third embodiment, the ratio of E_C to E_NRS is denoted by ρC=E_C/E_NRS. ρC is derived by existing parameters PA and/or PB and/or ρCRS or existing parameters ρA and/or ρB and/or ρCRS. The power of type C symbol (S_C) can be easily derived by referring to the power of type A symbol (S_A) and/or the power of type B symbol (S_B). eNB can configure PA and/or PB (or configure ρA and/or ρB) and/or ρCRS to indirectly configure ρC.
In a first sub-embodiment, the power of S_C is the same as power of S_A (S_C=S_A).
S_A=12*E_A=12*ρA*E_NRS.
For one CRS antenna port, S_C is denoted as S_C1=2*E_CRS+10*E_C=2*ρCRS*E_NRS+10*ρC*E_NRS. For two or four CRS antenna ports, S_C is denoted as S_C2=2*E_CRS+8*E_C=2*ρCRS*E_NRS+8*ρC*E_NRS.
Therefore, in condition of one CRS antenna port, S_A=S_C1−>12*ρA*E_NRS=2*ρCRS*E_NRS+10*ρC*E_NRS−>ρC=6ρA/5−ρCRS/5. In condition of two or four CRS antenna ports, S_A=S_C2−>12*ρA*E_NRS=2*ρCRS*E_NRS+8*ρC*E_NRS−>ρC=3ρA/2−ρCRS/4.
According to the first sub-embodiment, ρC is denoted as ρC1 and can be determined as the following table 2.
In a second sub-embodiment, the power of S_C is the same as power of S_B (S_C=S_B).
For one NRS antenna port, S_B is denoted as S_B1=2*E_NRS+10*E_B=2*E_NRS+10*ρB*E_NRS. For two NRS antenna ports, S_B is denoted as S_B2=2*E_NRS+8*E_B=2*E_NRS+8*ρB*E_NRS.
For one CRS antenna port, S_C is denoted as S_C1=2*E_CRS+10*E_C=2*ρCRS*E_NRS+10*ρC*E_NRS. For two or four CRS antenna ports, S_C is denoted as S_C2=2*E_CRS+8*E_C=2*ρCRS*E_NRS+8*ρC*E_NRS.
In the condition of one NRS antenna port and one CRS antenna port, S_B1=S_C1−>2*ENRS+10*ρB*E_NRS=2*ρCRS*E_NRS+10*ρC*E_NRS−>ρC=⅕+ρB−ρCRS/5.
In the condition of one NRS antenna port and two or four CRS antenna ports, S_B1=S_C2−>2*E_NRS+10*ρB*E_NRS=2*ρCRS*E_NRS+8*ρC*E_NRS−>ρC=¼+5ρB/4−ρCRS/4.
In the condition of two NRS antenna ports and two or four CRS antenna ports, S_B2=S_C2−>2*E_NRS+8*ρB*E_NRS=2*ρCRS*E_NRS+8*ρC*E_NRS−>ρC=¼+ρB−ρCRS/4.
According to the second sub-embodiment, ρC is denoted as ρC2 and can be determined as the following table 3
In a third sub-embodiment, the power of S_C is respectively determined according to the first sub-embodiment and the second sub-embodiment. In particular, ρC1 is determined according to the first sub-embodiment and ρC2 is determined according to the second sub-embodiment. According to the third sub-embodiment, ρC is denoted as ρC3 and can be determined as one of ρC1 and ρC2. The eNB may indicate ρC3 by a higher layer signaling based its implementation. For example, 1 bit can be used to indicate whether ρC1 or ρC2 would be applied.
In a fourth sub-embodiment, the eNB may choose a value from a predefined set of {−6, −4.77, −3, −1.77, 0, 1, 2, 3} that is closest to one of the above-determined ρC1, ρC2 and ρC3. The value chosen from the set (referred to as ρC4) that is closest to one of the above-determined ρC1, ρC2 and ρC3 (referred to as ρC0) means the smallest value chosen from the set that is larger than ρC0, or the largest value chosen from the set that is smaller than ρC0. For example, if ρC0 (one of the above-determined ρC1, ρC2 and ρC3, i.e. one of the above-determined ρC1 and ρC2 as ρC3 is one of ρC1 and ρC2) is −1, ρC4 may be −1.77 (the largest value in the set that is smaller than −1) or 0 (the smallest value in the set that is larger than −1).
In a fifth sub-embodiment, a predefined value M can be introduced to limit the value of ρC. In one implementation, the predefined value M may refer to the minimum value of ρC. For example, M is predefined value of 0.25 (i.e. −6 dB). In this implementation, ρC1 can be determined as the following table 4.
And, ρC2 can be determined as the following table 5.
In another implementation, the predefined value M may refer to the maximum value of ρC. For example, M is predefined value of 4 (i.e. 6 dB). In such implementation, ρC1 can be determined as the following table 6.
And, ρC2 can be determined as the following table 7:
The fifth sub-embodiment can be used together with the third sub-embodiment or together with the fourth sub-embodiment. For example, when used together with the third sub-embodiment, ρC1 is determined according table 4 or 6, and ρC2 is determined according to table 5 or 7. Then, the eNB may indicate ρC3 (i.e., ρC1 or ρC2) by a higher layer signaling (e.g., 1 bit).
When used together with the fourth embodiment, ρC1 is determined according table 4 or 6, and ρC2 is determined according to table 5 or 7. Then, a value (the smallest value that is larger than ρC1 or ρC2, or the largest value that is smaller than ρC1 or ρC2) is chosen from the predefined set.
It thus can be seen from the third embodiment that ρC1 is determined from ρA and ρCRS (the first sub-embodiment) or from ρA, ρCRS and a predefined value M (the fifth sub-embodiment). Depending on different numbers of CRS antenna ports, ρC1 is determined differently. ρC2 is determined from ρB and ρCRS (the second sub-embodiment) or from ρB, ρCRS and a predefined value M (the fifth sub-embodiment). Depending on different numbers of CRS antenna ports and/or different numbers of NRS antenna ports, ρC2 is determined differently. Therefore, ρC is determined by at least one of ρC1, ρC2, and the predefined value M. In particular, when M refers to a minimum value of ρC, ρC is determined by a larger value of at least two of ρC1, ρC2 and M; and when M refers to a maximum value of ρC, ρC is determined by a smaller value of at least two of ρC1, ρC2 and M. ρC3 is determined as one of ρC1 and ρC2. ρC4 is determined from a predefined set by referring to one of ρC1 and ρC2.
The method 900 may include receiving a first reference signal (NRS), a first data and a second data, wherein the first reference signal is associated with a first transmission power (E_NRS); the first data is in a symbol without the first reference signal, and the first data is associated with a second transmission power (E_A); and the second data is in a symbol in which the first reference signal is received; and the second data is associated with a third transmission power (E_B).
The method 1000 may include transmitting a first reference signal (NRS), a first data and a second data, wherein the first reference signal is associated with a first transmission power (E_NRS); the first data is in a symbol without the first reference signal, and the first data is associated with a second transmission power (E_A); and the second data is in a symbol in which the first reference signal is received; and the second data is associated with a third transmission power (E_B).
Referring to
The memories may be positioned inside or outside the processors and connected with the processors by various well-known means.
In the embodiments described above, the components and the features of the embodiments are combined in a predetermined form. Each component or feature should be considered as an option unless otherwise expressly stated. Each component or feature may be implemented not to be associated with other components or features. Further, the embodiment may be configured by associating some components and/or features. The order of the operations described in the embodiments may be changed. Some components or features of any embodiment may be included in another embodiment or replaced with the component and the feature corresponding to another embodiment. It is apparent that the claims that are not expressly cited in the claims are combined to form an embodiment or be included in a new claim.
The embodiments may be implemented by hardware, firmware, software, or combinations thereof. In the case of implementation by hardware, according to hardware implementation, the exemplary embodiment described herein may be implemented by using one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, and the like.
Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects to be only illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CN2020/097087 | 6/19/2020 | WO |
