Device and method for non-contiguous multiple resource unit in a wireless network
US-2024421948-A1 · Dec 19, 2024 · US
US10326574B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10326574-B2 |
| Application number | US-201415511446-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 10, 2014 |
| Priority date | Sep 15, 2014 |
| Publication date | Jun 18, 2019 |
| Grant date | Jun 18, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Provided are a method and device for configuring a pilot, wherein the method includes: configuring a user pilot according to subcarrier indexes of REs occupied by the user pilot, wherein the subcarrier indexes of the REs occupied by the user pilot are in subcarrier indexes of REs occupied by user data on PUSCH, and include the following pilot parameters: REstart and RBnumber, and further include REset and/or REinterval; and adjusting power of a pilot at a transmitting end and performing pilot resource mapping according to Powerfactor corresponding to the pilot parameters, where Powerfactor=(REset+REinterval)/REset. Through the disclosure, the problem that a pilot design scheme of the PUSCH in the related art is poor on flexibility is solved.
Opening claim text (preview).
What is claimed is: 1. A method for configuring a pilot, comprising: configuring a user pilot according to subcarrier indexes of Resource Elements (REs) occupied by the user pilot, wherein the subcarrier indexes of the REs occupied by the user pilot are in subcarrier indexes of REs occupied by user data on Physical Uplink Shared Channel (PUSCH), and comprise the following pilot parameters: REstart and RBnumber, and further comprise REset and REinterval, wherein the REstart is a subcarrier index of the first RE in the REs occupied by symbols of the user pilot; the RBnumber is a total number of Resource Blocks (RBs) of symbols of the user data; the REset is a minimum number of REs, of which positions are continuous in a frequency-domain, occupied by the user pilot; and the REinterval is the number of subcarriers in an interval between two REsets, which are closest in the frequency-domain, of the user pilot; and adjusting power of a pilot at a transmitting end and performing pilot resource mapping according to Powerfactor corresponding to the pilot parameters, where Powerfactor=(REset+REinterval)/REset. 2. The method as claimed in claim 1 , wherein when the REinterval is 0, the subcarrier indexes of the REs occupied by the user pilot do not comprise the REset, and the Powerfactor is 1. 3. The method as claimed in claim 1 , wherein configuring the user pilot according to the subcarrier indexes of the REs occupied by the user pilot comprises: in candidate pilot configuration provided by a system, choosing pilot configuration matching with time-frequency resource allocated for a user corresponding to the user data. 4. The method as claimed in claim 3 , wherein in the candidate pilot configuration provided by the system, pilot configuration, of which the REinterval is 0, corresponds to traditional time-frequency resource allocated for the user. 5. The method as claimed in claim 1 , wherein adjusting the power of the pilot at the transmitting end and performing the pilot resource mapping according to the Powerfactor corresponding to the pilot parameters comprises: according to the number of REs actually used by a user, generating, at the transmitting end, a pilot code with a length corresponding to the number of the REs actually used by the user; multiplying the pilot code by the Powerfactor to obtain a pilot code whose power is adjusted, and performing, according to a pilot pattern, the pilot resource mapping for the pilot code whose power is adjusted. 6. A device for configuring a pilot, comprising: a configuring component, configured to configure a user pilot according to subcarrier indexes of REs occupied by the user pilot, wherein the subcarrier indexes of the REs occupied by the user pilot are in subcarrier indexes of REs occupied by user data on PUSCH, and comprise the following pilot parameters: REstart and RBnumber, and further comprise REset and REinterval, wherein the REstart is a subcarrier index of the first RE in the REs occupied by symbols of the user pilot; the RBnumber is a total number of RBs of symbols of the user data; the REset is a minimum number of REs, of which positions are continuous in a frequency-domain, occupied by the user pilot; and the REinterval is the number of subcarriers in an interval between two REsets, which are closest in the frequency-domain, of the user pilot; and an adjusting component, configured to adjust power of a pilot at a transmitting end and perform pilot resource mapping according to Powerfactor corresponding to the pilot parameters, where Powerfactor=(REset+REinterval)/REset. 7. The device as claimed in claim 6 , wherein when the REinterval is 0, the subcarrier indexes of the REs occupied by the user pilot do not comprise the REset, and the Powerfactor is 1. 8. The device as claimed in claim 6 , wherein the configuring component is configured to choose, in candidate pilot configuration provided by a system, pilot configuration matching with time-frequency resource of occupied by the user data. 9. The device as claimed in claim 8 , wherein in the candidate pilot configuration provided by the system, pilot configuration, of which the REinterval is 0, corresponds to traditional time-frequency resource occupied by the user data. 10. The device as claimed in claim 6 , wherein the adjusting component comprises: a generating element, configured to, according to the number of REs actually used by a user, generate, at the transmitting end, a pilot code with a length corresponding to the number of the REs actually used by the user; and a mapping element, configured to multiply the pilot code by the Powerfactor to obtain a pilot code whose power is adjusted, and perform, according to a pilot pattern, the pilot resource mapping for the pilot code whose power is adjusted. 11. The method as claimed in claim 2 , wherein adjusting the power of the pilot at the transmitting end and performing the pilot resource mapping according to the Powerfactor corresponding to the pilot parameters comprises: according to the number of REs actually used by a user, generating, at the transmitting end, a pilot code with a length corresponding to the number of the REs actually used by the user; multiplying the pilot code by the Powerfactor to obtain a pilot code whose power is adjusted, and performing, according to a pilot pattern, the pilot resource mapping for the pilot code whose power is adjusted. 12. The method as claimed in claim 3 , wherein adjusting the power of the pilot at the transmitting end and performing the pilot resource mapping according to the Powerfactor corresponding to the pilot parameters comprises: according to the number of REs actually used by a user corresponding to the user data, generating, at the transmitting end, a pilot code with a length corresponding to the number of the REs actually used by the user; multiplying the pilot code by the Powerfactor to obtain a pilot code whose power is adjusted, and performing, according to a pilot pattern, the pilot resource mapping for the pilot code whose power is adjusted. 13. The method as claimed in claim 4 , wherein adjusting the power of the pilot at the transmitting end and performing the pilot resource mapping according to the Powerfactor corresponding to the pilot parameters comprises: according to the number of REs actually used by a user corresponding to the user data, generating, at the transmitting end, a pilot code with a length corresponding to the number of the REs actually used by the user; multiplying the pilot code by the Powerfactor to obtain a pilot code whose power is adjusted, and performing, according to a pilot pattern, the pilot resource mapping for the pilot code whose power is adjusted. 14. The device as claimed in claim 7 , wherein the adjusting component comprises: a generating element, configured to, according to the number of REs actually used by a user corresponding to the user data, generate, at the transmitting end, a pilot code with a length corresponding to the number of the REs actually used by the user; and a mapping element, configured to multiply the pilot code by the Powerfactor to obtain a pilot code whose power is adjusted, and perform, according to a pilot pattern, the pilot resource mapping for the pilot code whose power is adjusted. 15. The device as claimed in claim 8 , wherein the adjusting component comprises: a generating element, configured to, according to the number of REs actually used by a user corresponding to the user data, generate, at the transmitting end, a pilot code with a length corresponding to the number of the REs actually used by the user; and a map
the frequencies being orthogonal, e.g. OFDM(A) or DMT · CPC title
of dedicated pilots, i.e. pilots destined for a single user or terminal · CPC title
Structure of the reference signals · CPC title
Allocation of pilot signals, i.e. of signals known to the receiver (allocation of control signalling H04L5/0053; use of control signalling H04L5/0091) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.