WO2017107054A1

WO2017107054A1 - Dual mode sounding reference signal (srs) scheme for wireless communications

Info

Publication number: WO2017107054A1
Application number: PCT/CN2015/098273
Authority: WO
Inventors: Wenting CHANG; Yuan Zhu; Yushu Zhang; Xu Zhang; Qinghua Li
Original assignee: Intel IP Corporation
Priority date: 2015-12-22
Filing date: 2015-12-22
Publication date: 2017-06-29

Abstract

A wireless communication system may use a dual mode sounding reference signal (SRS) scheme to improve both beam tracking and uplink channel measurements. An eNB may transmit control signals directing user equipment (UE) to transmit either a first type of SRS or a second type of SRS. The UE may transmit a first SRS of the first type over an omnidirectional beam and transmit a second SRS of the second type over a directional beam based on the control signals. The UE also may use the first SRS for beamforming calculations, use the second SRS for uplink channel measurements, and transmit data over a physical uplink shared channel (PUSCH) based on the calculations and measurements.

Description

DUAL MODE SOUNDING REFERENCE SIGNAL (SRS) SCHEME FOR WIRELESS COMMUNICATIONS

Technical Field

The present invention relates in general to wireless communications and in particular to a dual mode sounding reference signal (SRS) scheme.

Description of the Related Art

The current long term evolution (LTE) standard may use sounding reference signals (SRS) for channel quality measurements and for downlink beamforming matrix calculations. User equipment (UE) may transmit the SRS to an evolved node B element (eNB) in an evolved universal mobile telecommunications system (UMTS) radio access network (E-UTRAN) . The LTE standard may support two SRS transmission methods that either transmit a wideband SRS during one symbol or transmit several frequency hopped narrowband SRS in different subframes.

LTE mobile communication networks may implement mobile communication technologies, such as millimeter wave (mmWave) . The mmWave technology may use large bandwidths to provide high data rates. The eNB may calculate a channel quality index (CQI) or modulation coding scheme (MCS) based on an array gain estimation from the SRS. However, the eNB may inaccurately estimate array gain from the SRS due to severe pathloss exhibited by the mmWave technology. As a result, the eNB may find it hard and slow to converge the MCS into an appropriate value using out loop power adjustments.

BRIEF DESCRIPTION OF THE DRAWINGS

The described embodiments are to be read in conjunction with the accompanying drawings.

FIG. 1 depicts example sounding reference signals (SRS) transmitted over a directional beam.

FIG. 2 depicts an example dual mode SRS transmission scheme.

FIG. 3 depicts example signaling used in the dual mode SRS transmission scheme.

FIG. 4 depicts an example base station process for the dual mode SRS transmission scheme.

FIG. 5 depicts an example UE process for the dual mode SRS transmission scheme.

FIG. 6 depicts example frequency shift signaling used in the dual mode SRS transmission scheme.

FIG. 7 depicts example electronic device circuitry, such as user equipment (UE) circuitry and/or evolved Node B (eNB) circuitry.

FIG. 8 schematically illustrates a computer-readable media in accordance with some embodiments.

DETAILED DESCRIPTION

Various aspects of the illustrative embodiments will be described using terms commonly employed by those skilled in the art to convey the substance of their work to others skilled in the art. However, it will be apparent to those skilled in the art that alternate embodiments may be practiced with only some of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth in order to provide a thorough understanding of the illustrative embodiments. However, it will be apparent to one skilled in the art that alternate embodiments may be practiced without the specific details. In other instances, well-known features are omitted or simplified in order not to obscure the illustrative embodiments.

Further, various operations will be described as multiple discrete operations, in turn, in a manner that is most helpful in understanding the illustrative embodiments； however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.

The phrase “in some embodiments” is used repeatedly. The phrase generally does not refer to the same embodiments； however, it may. The terms “comprising, ” “having, ” and “including” are synonymous, unless the context dictates otherwise.

The phrases “A or B, ” “A/B, ” and “A and/or B” mean (A) , (B) , or (A and B) .

As used herein, the term “circuitry” refers to, is part of, or includes hardware components such as an application specific integrated circuit (ASIC) , an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware, to perform the described operations.

FIG. 1 schematically illustrates a wireless communication environment 90 in accordance with various embodiments. Environment 90 may include user equipment (UE) 100 and an eNB 110. The eNB 110 may be an access node of a 3rd Generation Partnership Project (3GPP) LTE network. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein. For example, environment 90 also may operate in conjunction with future or next generation LTE specifications such as fifth generation (5G) and future generation millimeter wave (mmWave) communication systems.

The eNB 110 may be part of a radio access network (RAN) of the LTE network, such as an evolved universal terrestrial radio access network (E-UTRAN) . While embodiments of the present disclosure are described with respect to LTE networks, similar concepts may also be applicable to other networks, for example, universal mobile telecommunications system (UMTS) networks, GSM networks, etc.

The E-UTRAN may be coupled with components of a core network, for example, an evolved packet core (EPC) that performs various management and control functions of the LTE network and further provides a communication interface between various RANs and other networks.

UE 100 may be any type of computing device equipped with wireless communication circuitry and adapted to communicate through a RAN according to, for example, one or more 3GPP Technical Specifications. The UE 100 may include, but is not limited to, a phone, a computer, a sensor, or any other device that is configured for wireless communication through a RAN. UE 100 may include control circuitry 102, communication circuitry 103, radio transceiver 105, and one or more antennas in an antenna array 104.

Communication circuitry 103 may interface with radio transceiver 105 to receive radio frequency (RF) signals from and/or send RF signals to one or more components, for example, eNB 110, over an air interface via the one or more antennas in antenna array 104. The air interface between UE 100 and eNB 110 may be referred to as a Uu interface in 3GPP Technical Specifications. In various embodiments, communication circuitry 103 may use evolved universal terrestrial radio access (E-UTRA) protocols for communications over the air interface. Communication circuitry 103 may use orthogonal frequency division multiple access (OFDMA) for downlink communications and single carrier-frequency division multiple access (SC-FDMA) for uplink communications on the Uu interface.

Communication circuitry 103 may include signal-construction circuitry including, but not limited to, an encoder to encode input data, and a modulator to modulate a carrier signal to include the encoded input data to be transmitted. Communication circuitry 103 may further include signal-deconstruction circuitry including, but not limited to, a demodulator to provide encoded data from a modulated carrier signal, and a decoder to provide data from encoded data.

Radio transceiver 105 may provide for the transmission and reception of the RF signals. Radio transceiver 105 may have RF transmit circuitry such as, but not limited to, an up-converter to convert baseband signals to radio-frequency signals, and a power amplifier (PA) to amplify the RF signals for transmission. Radio transceiver 105 may further have RF receive circuitry such as, but not limited to, a low-noise amplifier to amplify a received RF signal, a filter to filter a received RF signal, and a downconverter to convert an RF signal to a baseband signal.

Control circuitry 102 may be coupled to communication circuitry 103, and may be configured to perform higher layer operations, for example, operations at layers in a communication protocol stack that are higher than layers of the communication protocol stack that perform the operations of communication circuitry 103 for radio transceiver 105.

In some embodiments, communication circuitry 103 and the control circuitry 102 may, collectively, provide the majority or all of the operations related to the communication protocol stack. Communication circuitry 103 and control circuitry 102 may include, or be a part of, baseband circuitry (for example, a baseband chipset) , a PC card, a connect card, a mobile broadband modem, etc.

The eNB 110 may include communication circuitry 113 to interface with a transceiver 115 to communicate over the air interface to, for example, receive uplink RF signals from UE 100 via one or more antennas in an antenna array 104 and transmit downlink RF signals to UE 100 via the one or more antennas in array 114. In some embodiments, communication circuitry 113 may have signal- construction circuitry and signal-deconstruction circuitry that complement the corresponding circuitry in communication circuitry 103. Similarly, transceiver 115 may include RF transmit circuitry and RF receive circuitry that complement the corresponding circuitry in radio transceiver 105.

The eNB 110 may also include control circuitry 112 coupled with communication circuitry 113. Control circuitry 112 may be configured to perform higher layer operations to control aspects of wireless communications in the cell provided by eNB 110.

In addition to communication over the air interface, the components of UE 100 and eNB 110 may include circuitry to communicate over one or more additional wired or wireless interfaces. For example, in some embodiments, transceiver 115 may include an Ethernet interface to support S1-AP signaling over Ethernet networks such as, but not limited to, fiber-optic gigabit and 10 Gigabit Ethernet, to provide the S1-MME interface.

It should also be noted that the term “channel” as used herein may refer to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. Additionally, the term “channel” may be synonymous with and/or equivalent to “communications channel, ” “data communications channel, ” “transmission channel, ” “data transmission channel, ” “access channel, ” “data access channel, ” “link, ” “data link, ” “carrier, ” “radiofrequency carrier, ” and/or any other like term denoting a pathway or medium through which data is communicated.

UE 100 may transmit single, periodic, or aperiodic sounding reference signals (SRS) 118 that eNB 110 uses for deriving uplink channel information. For example, eNB 110 may use SRS 118 to calculate beamforming coefficient matrices and to measure channel quality. The UE 100 may use the coefficient matrices sent back from eNB 100 to send signals in a particular beam direction to eNB 110. The eNB 110 also may direct UE 100 to send more bits via modulation coding scheme (MCS) feedback based on channel quality determinations, such as a signal to noise ratio (SNR) .

The eNB 110 may use radio resource control (RRC) signaling to configure UE 100 for periodic and/or aperiodic SRS transmissions and use downlink control information (DCI) to trigger the SRS transmissions. In addition to UE specific SRS configurations, cell specific SRS configurations may define subframes containing SRS transmissions as well as the set of SRS bandwidths available in the cell.

Channel clusters 116A-116N may represent different channel signal paths between UE 100 and eNB 110. The arrival power of SRS 118 at eNB 110 may be based on the combination of channel cluster power and a degree of matching between clusters 116 and the direction of beams 119A-119N.

Channel clusters 116 with high power levels may be diminished due to mismatches with the directional SRS 118. For example, channel cluster 116B may be located at the side lobes of

beams

119B and 119C and therefore have reduced power not observable by eNB 110.

FIG. 2 shows a dual mode SRS scheme 120 that transmits SRS using both an omnidirectional beam 130 and a direction beam 132. Dual mode SRS scheme 120 may improve both beam tracking and uplink channel measurements by eNB 110 for high frequency bands and may compensate for low SRS power levels produced on directional beams 132. UE 100 may generate omnidirectional beam 130 by activating one or more antennas in antenna array 104 at the same time. The UE 100 may generate directional beam 132 by applying a transmission (Tx) beam forming matrix similar to that used in a physical uplink shared channel (PUSCH) . UE 100 and eNB 110 may operate dual mode SRS scheme 120 in any wireless communication system, such as a LTE communication system.

UE 100 may transmit a first type of SRS 124 over 360-degree omnidirectional beam 130 releasing the coherence between channel clusters 116 and the beam direction of SRS 118 shown above in FIG. 1. Omnidirectional SRS 124 may have no preference on any particular channel cluster enabling eNB 110 to observe more channel clusters and more accurately adjust directional beam 132. In one example, eNB 110 may use the first type of SRS 124 for beam forming measurements. When channel reciprocity exists, eNB 110 may use omnidirectional SRS 124 to calculate both uplink and downlink transmission beamforming weights.

UE 100 may transmit a second type of SRS 126 over directional beam 132 to align with the strongest channel cluster so the equivalent channel frequency response becomes flat compared with the channel frequency response of SRS 124 transmitted over omnidirectional beam 130. The second type of SRS 126 may provide accurate channel quality measurement while reducing resource allocation by narrowing the bandwidth occupied by SRS 126 or sparsely interleaving SRS 126. Omnidirectional SRS 124 may occupy a wider bandwidth then directional SRS 126 and cover multiple different directions within a given period of time.

In one example, eNB 110 may send control signals 122 to UE 100 to configure the first type of SRS 124 and/or the second type of SRS 126. Control signals 122 may include any signaling protocol used by eNB 110 for configuring UE 100, such as radio resource control (RRC) , system information block (SIB) , downlink control information (DCI) , etc. Of course eNB 110 also may use other signaling protocols for configuring UE 100.

The eNB 110 may trigger UE 100 to transmit

SRS

124 or 126 at different times. For example, eNB 110 may trigger UE 100 to transmit SRS 124 over omnidirectional beam 130 during initial signaling before determining channel cluster information. In another example, eNB 110 may trigger UE 100 to transmit SRS 124 when tracking is lost with directional beam 132. Of course eNB 110 may enable either

SRS

124 or 126 at any time based on any signaling condition.

In one example, eNB 110 may determine beamforming weights from SRS 124. The eNB 110 may select a beamforming codebook index based on the beamforming weights and send the beamforming codebook to UE 100. UE 100 may use the beamforming code book to configure directional beam 132 for PUSCH transmissions. UE 100 may interleave the second type of SRS 126 with the PUSCH transmissions. The eNB 110 then may use SRS 126 to measure channel quality during the PUSCH transmissions. For example, eNB 110 may calculate a CQI from SRS 126 and select a modulation and coding scheme (MCS) based on the CQI. The eNB 110 may send the MCS to UE 100 and UE 100 may use the MCS to adjust modulation and coding rates.

FIG. 3 shows example signaling used in the dual mode SRS scheme. An x-axis 136 in a signal diagram 134 represents time and a y-axis 138 represents frequency. The UE may transmit the first type of SRS 124 (also referred to as “Type-I SRS 124” ) in all directions on one or a plurality of subframes 140. Since the preferred beam direction may change slowly, the eNB may assign a longer period to SRS 124 to reduce bandwidth usage.

The UE may transmit the second type of SRS 126 (also referred to as “Type-II SRS 126” ) more frequently than SRS 124 with reduced power, since SRS 126 may use a same UE-specific beamforming matrix as PUSCH 144. In one example, the UE may transmit SRS 126 over an OFDM symbol 142 in-between PUSCH transmissions 144. OFDM symbol 142 may be reserved for transmitting SRS 126.

As mentioned above, the eNB may use SRS 124 for beamforming tracking and refinement and use SRS 126 for measuring channel quality. However, the eNB may use either

SRS

124 or 126 for deriving any signaling metric.

FIG. 4 shows example operations performed by eNB 110 in FIG. 2. The eNB may send control signals that configure the UE for transmitting either the first type of SMS over an omnidirectional beam or transmitting the second type of SMS over a directional beam.

In operation 150, the eNB may select one of the two types of SRS for receiving from the UE. For example, the eNB may select the first type of SRS to perform a beamforming measurement or select the second type of SRS to perform a channel quality measurement. In operation 152, the eNB may select the first type of SRS and in operation 154 may send control signals configuring the UE to transmit the omnidirectional SRS at a specified frequency, period, time offset, and/or power level. In operation 156, the eNB may use the first type of SRS received over the omnidirectional beam for the beamforming measurements.

Alternatively, the eNB in operation 152 may select the second type of directional SRS. In operation 158, the eNB may send control signals configuring the UE to transmit the second type of SRS over the directional beam. In operation 159, the eNB may use the second type of SRS received over the directional beam for channel quality measurements.

FIG. 5 shows example operations performed by UE 100 in FIG. 2. In operation 160, the UE may receive control signals from the eNB. As mentioned above, the eNB may use any type of signaling to identify and/or configure UE. In operation 162, the UE may receive control signals associated the first type of omnidirectional SRS. For example, the control signals may include a bit value associating SRS configuration messages with the first type of SRS.

In operation 164, the UE may transmit the first type of SRS over an omnidirectional beam based on the control signals received from the eNB. For example, the UE may transmit the first type of SRS based on a first trigger, period indicator, frequency offset, and/or power indicator identified in the control signals. The UE then may activate some or all of the antenna elements in the antenna array to transmit the first type of SRS over the omnidirectional beam.

Otherwise, the UE in operation 162 may receive control signals associated with the second type of SRS. In operation 166, the UE may transmit the second type of directional SRS based on the control signals. For example, the UE may transmit the second type of SRS over a directional beam based on a second trigger, period indicator, frequency offset, and/or power indicator identified in the control signals.

The eNB may use signaling protocols to configure SRS transmissions similar to those described in 3GPP TS 36.211 v12.7.0, published 2015-09, Release 12； and/or 3GPP TS 36.331 v12.7.0, published 2015-09, Release 12. These protocols are known to those skilled in the art and therefore are not described in further detail. However, the eNB may add additional signaling and/or modify the existing protocols to implement the dual mode SRS scheme described above.

For example, the eNB may add one bit into radio resource control (RRC) signaling SoundingRS-UL-ConfigDedicated and SoundingRS-UL-ConfigDedicatedAperiodic-r10 to indicate whether the configuration parameters are applicable to the first type of SRS or applicable to the second type of SRS.

In another example, the eNB may add one bit into a SRS-related downlink control information (DCI) format, such as DCI formats 0/4/1A for time division duplex (TDD) , to indicate whether a trigger for SRS transmission is applicable for the first type of SRS or the second type of SRS.

In another example, the eNB may add one bit to RRC signaling SoundingRS-UL-ConfigDedicated-v1020, to indicate whether an antenna port number configuration is for the first type of SRS or the second type of SRS.

In another example, the eNB may add one bit to higher layer RRC signaling to concurrently indicate SoundingRS-UL-ConfigDedicated, ConfigDedicatedAperiodic-r10, and SoundingRS-UL-ConfigDedicated-v1020 configurations are applicable to the first type of SRS or the second type of SRS.

In another example, the eNB may transmit one additional bit together with a SRS power offset P_{SRS_OFFSET} to indicate association with the first type of SRS or the second type of SRS. The power values may be different since the occupied resource block number and array gain of the two types of SRS may be different.

In another example, the eNB may send a 1-bit indicator in a higher layer SIB or UE specific RRC signaling for collision avoidance between the first type of SRS and the second type of SRS. For example, a 0 bit may indicate the first type of SRS is punctured, and a 1 but may indicate the second type of SRS is punctured.

In another example, the eNB may add 1-priority bit into a SRS related trigger. For example, a “1” bit may indicate a higher priority and trigger transmission for the first type of SRS. The 1 bit may cause the UE to puncture the second type of SRS or PUSCH to reserve resources for the triggered SRS. A “0” bit may trigger the second type of SRS and puncture the first type of SRS.

FIG. 6 shows another example dual mode SRS scheme for a time divisional multiplexed (TDM) transmission. In one example, the eNB may send control signals to the UE specifying a period, offset, and frequency position for transmitting the first type of SRS 124.

In this example, the first type of omnidirectional SRS 124 is transmitted in different subband frequency positions 172 in different OFDM symbols 170 within a subframe 174. The second type of SRS 126 is transmitted in one or more subbands within a same OFDM symbol 171 interleaved in between PUSCH transmissions 142.

The eNB may use higher layer signaling, such as SRS related DCI or SIB, to configure the UE with a NOFDM parameter. The NOFDM parameter may represent a number of OFDM symbols 170 occupied by SRS 124. The NOFDM parameter may cause the UE to transmit SRS 124 in multiple OFDM symbols 170 in a same subframe 174 enabling the eNB to sweep all beam forming candidates from the multiple OFDM symbols 170 as the same time.

In another example, the eNB may send higher layer DCI or SIB signaling that includes a NOFDM-offset parameter representing a cell-specific OFDM symbol offset. The UE may use the OFDM offset to avoid inter-cell SRS interference.

The array gain of SRS 124 may be reduced compared with SRS 126. However, the UE may concentrate transmit power in relatively narrow subbands to ensure the entire band is scanned by the eNB.

In this example, the UE may shift subband frequency positions 172 among different OFDM symbols 170, as follows:

where i_ofdm is the OFDM symbol index, n_RRC, max symbol index is the maximum value of n_RRC, which is equal to 24 at the current standard. Refer to 3GPP TS 36.211 v12.7.0, 2015-09, Release 12 for the meaning of other parameters.

FIG. 7 illustrates, for one embodiment, example components of a device 700, which may be a UE (for example, UE 100) or an eNB (for example, eNB 110) . Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software. In some embodiments, device 700 may include application circuitry 702, baseband circuitry 704, radio frequency (RF) circuitry 706, front-end module (FEM) circuitry 708 and one or more antennas 710, coupled together at least as shown.

The application circuitry 702 may include one or more application processors. For example, the application circuitry 702 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor (s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc. ) . The processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

The baseband circuitry 704 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 704 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 706 and to generate baseband signals for a transmit signal path of the RF circuitry 706. Baseband circuity 704 may interface with the application circuitry 702 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 706. For example, in some embodiments, the baseband circuitry 704 may include a second generation (2G) baseband processor 704a, third generation (3G) baseband processor 704b, fourth generation (4G) baseband processor 704c, fifth generation baseband processor 704d, and/or other baseband processor (s) for other existing generations, generations in development or to be developed in the future (e.g., 6G, etc.) .

The baseband circuitry 704 (e.g., one or more of baseband processors 704a-e) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 706. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 704 may include Fast-Fourier Transform (FFT) , precoding, and/or constellation mapping/demapping functionality.

In some embodiments, encoding/decoding circuitry of the baseband circuitry 704 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry 704 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY) , MAC, radio link control (RLC) , packet data convergence protocol (PDCP) , and/or radio resource control (RRC) elements. A central processing unit (CPU) 704e of the baseband circuitry 704 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processor (s) (DSP) 704f. The audio DSP (s) 704f may include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.

The baseband circuitry 704 may further include memory/storage 704g. The memory/storage 704g may be used to load and store data and/or instructions for operations performed by the processors of the baseband circuitry 704. Memory/storage for one embodiment may include any combination of suitable volatile memory and/or non-volatile memory. The memory/storage 704g may include any combination of various levels of memory/storage including, but not limited to, read-only memory (ROM) having embedded software instructions (e.g., firmware) , random access memory (e.g., dynamic random access memory (DRAM) ) , cache, buffers, etc. The memory/storage 704g may be shared among the various processors or dedicated to particular processors. In some embodiments, the memory/storage 704g may be external to the baseband circuitry 704 and, for example, shared with other circuitry such as, but not limited to, application circuitry 702 or RF circuitry 706.

Components of the baseband circuitry 704 may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 704 and the application circuitry 702 may be implemented together, such as, for example, on a system on a chip (SOC) .

In some embodiments, the baseband circuitry 704 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 704 may support communication with an evolved universal terrestrial radio access network (E-UTRAN) and/or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) . Embodiments in which the baseband circuitry 704 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

In embodiments in which the device 700 is a UE, for example, UE 100, the baseband circuitry 704 may perform, for example, operations such as, but not limited to, generating and transmitting grantless uplink transmissions as described herein. In some embodiments, the baseband circuitry 704 may encompass some or all of the control circuitry 102 and communication circuitry 103 described above with respect to FIGS. 1 and 2.

In embodiments in which the device is an eNB, the baseband circuitry 704 may perform, for example, the configuration of MTC UEs and resource pools and receipt and processing of grantless uplink tranmissions. In some embodiments, the baseband circuitry 704 may encompass some or all of control circuitry 112 and communication circuitry 113 described above with respect to FIGS. 1 and 2.

RF circuitry 706 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 706 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 706 may include a receive signal path that may include circuitry to down-convert RF signals received from the FEM circuitry 708 and provide baseband signals to the baseband circuitry 704. RF circuitry 706 may also include a transmit signal path that may include circuitry to up-convert baseband signals provided by the baseband circuitry 704 and provide RF output signals to the FEM circuitry 708 for transmission.

In some embodiments, the RF circuitry 706 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 706 may include mixer circuitry 706a, amplifier circuitry 706b and filter circuitry 706c. The transmit signal path of the RF circuitry 706 may include filter circuitry 706c and mixer circuitry 706a. RF circuitry 706 may also include synthesizer circuitry 706d for synthesizing a frequency for use by the mixer circuitry 706a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 706a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 708 based on the synthesized frequency provided by synthesizer circuitry 706d. The amplifier circuitry 706b may be configured to amplify the down-converted signals and the filter circuitry 706c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 704 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 706a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 706a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 706d to generate RF output signals for the FEM circuitry 708. The baseband signals may be provided by the baseband circuitry 704 and may be filtered by filter circuitry 706c. The filter circuitry 706c may include a low-pass filter (LPF) , although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 706a of the receive signal path and the mixer circuitry 706a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively. In some embodiments, the mixer circuitry 706a of the receive signal path and the mixer circuitry 706a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection) . In some embodiments, the mixer circuitry 706a of the receive signal path and the mixer circuitry 706a of the transmit signal path may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 706a of the receive signal path and the mixer circuitry 706a of the transmit signal path may be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 706 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 704 may include a digital baseband interface to communicate with the RF circuitry 706.

In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 706d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 706d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer circuitry 706d may be configured to synthesize an output frequency for use by the mixer circuitry 706a of the RF circuitry 706 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 706d may be a fractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO) , although that is not a requirement. Divider control input may be provided by either the baseband circuitry 704 or the application circuitry 702 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 702.

Synthesizer circuitry 706d of the RF circuitry 706 may include a divider, a delay-locked loop (DLL) , a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA) . In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 706d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO) . In some embodiments, the RF circuitry 706 may include an IQ/polar converter.

In some embodiments, the RF circuitry 706 may encompass or include parts of

radio transceivers

105 and 115 located in UE 100 and eNB 110, respectively, as described above with respect to FIGS. 1 and 2.

FEM circuitry 708 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 710, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 706 for further processing. FEM circuitry 708 may also include a transmit signal path that may include circuitry configured to amplify signals for transmission provided by the RF circuitry 706 for transmission by one or more of the one or more antennas 710.

In some embodiments, the FEM circuitry 708 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 706) . The transmit signal path of the FEM circuitry 708 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 706) , and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 710.

In some embodiments, the device 700 may include additional elements such as, for example, display (for example, a touchscreen display) , camera, sensor, and/or input/output (I/O) interface.

FIG. 8 illustrates an example computer-readable media 804 that may be suitable for use to store instructions that cause an apparatus, in response to execution of the instructions by the apparatus, to practice selected aspects of the present disclosure. In some embodiments, the computer-readable media 804 may be non-transitory. As shown, computer-readable storage medium 804 may include programming instructions 808. Programming instructions 808 may be configured to enable a device, e.g., eNB 110, UE 100, and/or similar computing devices, in response to execution of the programming instructions 808, to implement (aspects of) any of the methods and/or elements described throughout this disclosure, including the methods described in relation to the eNB 110 and UE 100, the circuitry , or the eNB and UE operations of FIGS. 1-7. In some embodiments, programming instructions 808 may be disposed on computer-readable media 804 that is transitory in nature, such as signals.

Any combination of one or more computer-usable or computer-readable media may be utilized. The computer-usable or computer-readable media may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable media would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a transmission media such as those supporting the Internet or an intranet, or a magnetic storage device. Note that the computer-usable or computer-readable media could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory. In the context of this document, a computer-usable or computer-readable media may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-usable media may include a propagated data signal with the computer-usable program code embodied therewith, either in baseband or as part of a carrier wave. The computer-usable program code may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc.

Computer program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute 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 latter 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) .

Examples

Some non-limiting examples are provided below.

Example 1 may include user equipment circuitry, comprising:

a processing unit；

a memory device coupled to the processing unit, the memory device having instructions stored thereon that, in response to execution by the processing unit, are operable to:

process control signals to configure a first type of sounding reference signal (SRS) and a second type of SRS；

generate a first SRS of the first type over an omnidirectional beam；

generate a second SRS of the second type over a directional beam； and

generate a physical uplink shared channel (PUSCH) transmission over the directional beam.

Example 2 may include the user equipment circuitry of example 1, wherein the processing unit is further to generate the first SRS to provide as a basis for beamforming measurements and generate the second SRS to provide a basis for uplink channel measurements.

Example 3 may include the user equipment circuitry of any of examples 1 and 2, wherein the processing unit is further to generate the first SRS over different frequency positions of different orthogonal frequency divisional multiplex (OFDM) symbols in a same subframe.

Example 4 may include the user equipment circuitry of any of examples 1-3, wherein the processing unit is further to generate the second SRS over a same OFDM symbol in between physical uplink shared channels (PUSCH) .

Example 5 may include the user equipment circuitry of any of examples 1-4, wherein the control signals comprise radio resource control (RRC) signaling or downlink control information (DCI) .

Example 6 may include the user equipment circuitry of any of examples 1-5, wherein the processing unit is further to:

generate the first SRS with a first antenna port configuration identified in the control signals； and

generate the second SRS with a second antenna port configuration identified in the control signals.

Example 7 may include the user equipment circuitry of any of examples 1-6, wherein the processing unit is further to:

generate the first SRS at a first output power level identified in the control signals； and

generate the second SRS at a second output power level identified in the control signals, the second output power level being less than the first output power level.

Example 8 may include the user equipment circuitry of any of examples 1-7, wherein the processing unit includes:

radio frequency (RF) circuitry to receive a priority value in the control signals； and

baseband circuitry to generate one of the first SRS and the second SRS based on the priority value.

Example 9 may include the user equipment circuitry of any of examples 1-8, wherein the processing unit includes baseband circuitry to:

generate the first SRS at a first period and a first frequency position identified in the control signals； and

generate the second SRS at a second period and a second frequency position identified in the control signals.

Example 10 may include the user equipment circuitry of any of examples 1-9, wherein the processing unit includes baseband circuitry to:

generate the first SRS over a first number of symbols and at a first symbol offset identified in the control signals； and

generate the second SRS over a second number of symbols and at a second symbol offset identified in the control signals.

Example 11 may include a method for operating user equipment (UE) , comprising:

receiving control signals to configure a first type of sounding reference signal (SRS) and a second type of SRS；

transmitting a first SRS of the first type over an omnidirectional beam；

transmitting a second SRS of the second type over a directional beam； and

transmitting a physical uplink shared channel (PUSCH) transmission over the directional beam.

Example 12 may include the method of example 11, further comprising transmitting the first SRS to provide as a basis for beamforming measurements and transmit the second SRS to provide a basis for uplink channel measurements.

Example 13 may include the method of any of examples 11 and 12, further comprising transmitting the first SRS over different frequency positions of different orthogonal frequency divisional multiplex (OFDM) symbols in a same subframe.

Example 14 may include the method of any of examples 11-13, further comprising transmitting the second SRS over a same OFDM symbol in between physical uplink shared channels (PUSCH) .

Example 15 may include the method of any of examples 11-14, wherein the control signals comprise radio resource control (RRC) signaling or downlink control information (DCI) .

Example 16 may include the method of any of examples 11-15, further comprising:

transmitting the first SRS with a first antenna port configuration identified in the control signals； and

transmitting the second SRS with a second antenna port configuration identified in the control signals.

Example 17 may include the method of any of examples 11-16, further comprising:

transmitting the first SRS at a first output power level identified in the control signals； and

transmitting the second SRS at a second output power level identified in the control signals, the second output power level being less than the first output power level.

Example 18 may include the method of any of examples 11-17, further comprising:

receiving a priority value in the control signals； and

transmitting one of the first SRS and the second SRS based on the priority value.

Example 19 may include the method of any of examples 11-18, further comprising:

transmitting the first SRS at a first period and a first frequency position identified in the control signals； and

transmitting the second SRS at a second period and a second frequency position identified in the control signals.

Example 20 may include the method of any of examples 11-19, further comprising:

transmitting the first SRS over a first number of symbols and at a first symbol offset identified in the control signals； and

transmitting the second SRS over a second number of symbols and at a second symbol offset identified in the control signals.

Example 21 may include one or more computing device-readable media comprising computing device-executable instructions to be included in user equipment ( “UE” ) , wherein the instructions, in response to execution by the UE, cause the UE to:

identify a first setting for a first type of sounding reference signal (SRS) transmission to support downlink transmission reception beamforming calculations；

generate a first SRS of the first type in a millimeter (mm) wave communication based on the first setting；

identify a second setting for a second type of SRS to support channel quality measurements； and

generate a second SRS of the second type in the mmwave communication based on the second setting.

Example 22 may include the one or more computing device-readable media of example 21, wherein the instructions are further to cause the UE to:

generate the first SRS over an omindirectional beam； and

generate the second SRS over a directional beam.

Example 23 may include the one or more computing device-readable media of any of examples 21 and 22, wherein the instructions are further to cause the UE to receive a first message from a base station including the first setting and receive a second message from the base system including the second setting.

Example 24 may include the one or more computing device-readable media of any of examples 21-23, wherein the instructions are further to cause the UE to:

generate the first SRS in different symbols of a same subframe； and

generate the second SRS in a same symbol interleaved with physical uplink shared channel (PUSCH) transmissions.

Example 25 may include the one or more computing device-readable media of any of examples 21-24, wherein the instructions are further to cause the UE to:

generate the first SRS at a first period and a first frequency position； and

generate the second SRS at a second period and a second frequency position.

Example 26 may include the one or more computing device-readable media of any of examples 21-25, wherein the instructions are further to cause the UE to:

generate the first SRS at a first power level； and

generate the second SRS at a second power level, the second power level being less than the first power level.

Example 27 may include the one or more computing device-readable media of any of examples 21-26, wherein the instructions are further to cause the UE to generate the first SRS according to:

where i_ofdm is an orthogonal frequency divisional multiplex (OFDM) symbol index,

p is an antenna port number,

n_RRCis a symbol index,

Nis a constant, and

n_RRC, max is a maximum value of symbol indexn_RRC.

Example 28 may include evolved node B element (eNB) circuitry, comprising:

a processing device；

a memory device coupled to the processing device, the memory device having instructions stored thereon that, in response to execution by the processing device, are operable to:

receive a first type of sounding reference signal (SRS) over a first type of transmission beam；

determine beamforming information based on the first type of SRS received over the first type of transmission beam；

receive a second type of SRS over a second type of transmission beam； and

determine channel quality information based on the second type of SRS received over the second type of transmission beam.

Example 29 may include the eNB circuitry of example 28, wherein the first type of transmission beam is an omnidirectional transmission beam and the second type of transmission beam is a directional transmission beam.

Example 30 may include the eNB circuitry of any of examples 28 and 29, wherein the processing device is further to:

determine beamforming weights from the beamforming information；

select a beamforming codebook index based on the beamforming weights；

transmitthe beamforming codebook index to user equipment (UE) ；

determine a channel quality index (CQI) from the channel quality information；

select a modulation and coding scheme (MCS) based on the CQI； and

transmitthe MCS to the UE.

Example 31 may include the eNB circuitry of any of examples 28-30, wherein the processing device is further to include a bit in radio resource control (RRC) signaling to indicate whether SoundingRS-UL-ConfigDedicated configuration parameters and SoundingRS-UL-ConfigDedicatedAperiodic-r10 configuration parameters are applicable to the first type of SRS or the second type of SRS.

Example 32 may include the eNB circuitry of any of examples 28-31, wherein the processing device is further to include a bit in radio resource control (RRC) signaling to indicate whether an antenna port number configuration is applicable to the first type of SRS or the second type of SRS.

Example 33 may include the eNB circuitry of any of examples 28-32, wherein the processing device is further to generate a bit to indicate whether a P_{SRS_OFFSET} SRS power setting is applicable to the first type of SRS or the second type of SRS.

Example 34 may include the eNB circuitry of any of examples 28-33, wherein the processing device is further to include a collision avoidance bit with a system information block (SIB) , or with UE specific radio resource control (RRC) signaling, to identify an association with one of the first type of SRS or the second type of SRS to puncture.

Example 35 may include the eNB circuitry of any of examples 28-34, wherein the processing device is further to include a priority bit with a SRS trigger to indicate an association with a first one of the first and second type of SRS and indicate a second one of the first and second type of SRS or a physical uplink shared channel (PUSCH) to puncture.

Example 36 may include the eNB circuitry of any of examples 28-35, wherein the processing device is further to transmit control signals to user equipment (UE) including:

a first period, first timing offset, and first frequency position for the first type of SRS； and

transmit the UE a second period, second timing offset, and second frequency position for the second type of SRS.

Example 37 may include the eNB circuitry of any of examples 28-36, wherein the processing device is further to identify in radio resource control (RRC) , downlink control information (DCI) , or system information block (SIB) signaling a number of orthogonal frequency divisional multiplex (OFDM) symbols (N_OFDM) for association with one of the first type of SRS or second type of SRS.

Example 38 may include the eNB circuitry of any of examples 28-37, wherein the processing device is further to identify in the RRC, DCI, or SIB a timing offset (N_OFDM-offset) for the OFDM symbols.

Example 39 may include the eNB circuitry of any of examples 28-38, wherein the processing device is further to include a bit in downlink control information (DCI) having DCI format 0/4/1A for time division duplex (TDD) to indicate whether a trigger for a SRS transmission is applicable to the first type of SRS or the second type of SRS.

Example 40 may include the eNB circuitry of any of examples 28-39, wherein the processing device is further to include a bit in radio resource control (RRC) signaling to indicate whether concurrent SoundingRS-UL-ConfigDedicated, ConfigDedicatedAperiodic-r10, SoundingRS-UL-ConfigDedicated-v1020 messages are applicable to the first type of SRS or the second type of SRS.

Example 41 may include one or more computing device-readable media comprising computing device-executable instructions to be included in an evolved node B element (eNB) , wherein the instructions, in response to execution by the eNB, cause the eNB to:

receive a first type of sounding reference signal (SRS) over an omnidirectional transmission beam；

determine beamforming information based on the first type of SRS received over the omnidirectional transmission beam；

receive a second type of SRS over a directional transmission beam； and

determine channel quality information based on the second type of SRS received over the directional transmission beam.

Example 42 may include the one or more computing device-readable media of example 41, wherein the instructions are further to cause the eNB to:

determine beamforming weights from the beamforming information；

select a beamforming codebook index based on the beamforming weights；

transmit the beamforming codebook index to user equipment (UE) ；

determine a channel quality index (CQI) from the channel quality information；

select a modulation and coding scheme (MCS) based on the CQI； and

transmit the MCS to the UE.

Example 43 may include the one or more computing device-readable media of any of examples 41 and 42, wherein the instructions are further to cause the eNB to:

transmit user equipment (UE) a first period, first timing offset, and first frequency position for the first type of SRS； and

transmit to the UE a second period, second timing offset, and second frequency position for the second type of SRS.

The description herein of illustrated implementations, including what is described in the Abstract, is not intended to be exhaustive or to limit the present disclosure to the precise forms disclosed. While specific implementations and examples are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. These modifications may be made to the disclosure in light of the above detailed description.

Claims

User equipment circuitry, comprising:

a processing unit；

a memory device coupled to the processing unit, the memory device having instructions stored thereon that, in response to execution by the processing unit, are operable to:

process control signals to configure a first type of sounding reference signal (SRS) and a second type of SRS；

generate a first SRS of the first type over an omnidirectional beam；

generate a second SRS of the second type over a directional beam； and

generate a physical uplink shared channel (PUSCH) transmission over the directional beam.
The user equipment circuitry of claim 1, wherein the processing unit is further to generate the first SRS to provide a basis for beamforming measurements and generate the second SRS to provide a basis for uplink channel measurements.
The user equipment circuitry of any of claims 1 and 2, wherein the processing unit is further to generate the first SRS over different frequency positions of different orthogonal frequency divisional multiplex (OFDM) symbols in a same subframe.
The user equipment circuitry of claim 3, wherein the processing unit is further to generate the second SRS over a same OFDM symbol in between physical uplink shared channels (PUSCHs) .
The user equipment circuitry of any of claims 1 and 2, wherein the control signals comprise radio resource control (RRC) signaling or downlink control information (DCI) .
The user equipment circuitry of any of claims 1 and 2, wherein the processing unit is further to:

generate the first SRS with a first antenna port configuration identified in the control signals； and

generate the second SRS with a second antenna port configuration identified in the control signals.
The user equipment circuitry of any of claims 1 and 2, wherein the processing unit is further to:

generate the first SRS at a first output power level identified in the control signals； and

generate the second SRS at a second output power level identified in the control signals, the second output power level being less than the first output power level.
The user equipment circuitry of claim 1, wherein the processing unit includes:

RF circuitry to process a priority value in the control signals； and

baseband circuitry to generate one of the first SRS and the second SRS based on the priority value.
The user equipment circuitry of any of claims 1 and 2, wherein the processing unit includes baseband circuitry to:

generate the first SRS at a first period and a first frequency position identified in the control signals； and

generate the second SRS at a second period and a second frequency position identified in the control signals.
The user equipment circuitry of any of claims 1 and 2, wherein the processing unit includes baseband circuitry to:

generate the first SRS over a first number of symbols and at a first symbol offset identified in the control signals； and

generate the second SRS over a second number of symbols and at a second symbol offset identified in the control signals.
One or more computing device-readable media comprising computing device-executable instructions to be included in user equipment ( “UE” ) , wherein the instructions, in response to execution by the UE, cause the UE to:

identify a first setting for a first type of sounding reference signal (SRS) transmission to support downlink transmission reception beamforming calculations；

transmit a first SRS of the first type in a millimeter (mm) wave communication based on the first setting；

identify a second setting for a second type of SRS to support channel quality measurements； and

transmit a second SRS of the second type in the mmwave communication based on the second setting.
The one or more computing device-readable media of claim 11, wherein the instructions are further to cause the UE to:

transmit the first SRS over an omindirectional beam； and

transmit the second SRS over a directional beam.
The one or more computing device-readable media of any of claims 11 and 12, wherein the instructions are further to cause the UE to receive a first message from a base station including the first setting and receive a second message from the base system including the second setting.
The one or more computing device-readable media of any of claims 11 and 12, wherein the instructions are further to cause the UE to:

transmit the first SRS in different symbols of a same subframe； and

transmit the second SRS in a same symbol interleaved with physical uplink shared channel (PUSCH) transmissions.
The one or more computing device-readable media of any of claims 11 and 12, wherein the instructions are further to cause the UE to:

transmit the first SRS at a first period and a first frequency position； and

transmit the second SRS at a second period and a second frequency position.
Evolved node B element (eNB) circuitry, comprising:

a processing device；

a memory device coupled to the processing device, the memory device having instructions stored thereon that, in response to execution by the processing device, are operable to:

process a first type of sounding reference signal (SRS) over a first type of transmission beam；

determine beamforming information based on the first type of SRS processed over the first type of transmission beam；

process a second type of SRS over a second type of transmission beam； and

determine channel quality information based on the second type of SRS processed over the second type of transmission beam.
The eNB circuitry of claim 16, wherein the first type of transmission beam is an omnidirectional transmission beam and the second type of transmission beam is a directional transmission beam.
The eNB circuitry of any of claims 16 and 17, wherein the processing device is further to:

determine beamforming weights from the beamforming information；

select a beamforming codebook index based on the beamforming weights；

transmit the beamforming codebook index to user equipment (UE) ；

determine a channel quality index (CQI) from the channel quality information；

transmit a modulation and coding scheme (MCS) based on the CQI； and

transmit the MCS to the UE.
The eNB circuitry of any of claims 16 and 17, wherein the processing device is further to include a bit in radio resource control (RRC) signaling to indicate whether SoundingRS-UL-ConfigDedicated configuration parameters and SoundingRS-UL-ConfigDedicatedAperiodic-r10 configuration parameters are applicable to the first type of SRS or the second type of SRS.
The eNB circuitry of any of claims 16 and 17, wherein the processing device is further to include a bit in radio resource control (RRC) signaling to indicate whether an antenna port number configuration is applicable to the first type of SRS or the second type of SRS.
The eNB circuitry of any of claims 16 and 17, wherein the processing device is further to generate a bit to indicate whether a P_{SRS_OFFSET} SRS power setting is applicable to the first type of SRS or the second type of SRS.
The eNB circuitry of any of claims 16 and 17, wherein the processing device is further to include a collision avoidance bit with a system information block (SIB) , or with UE specific radio resource control (RRC) signaling, to identify an association with one of the first type of SRS or the second type of SRS to puncture.
One or more computing device-readable media comprising computing device-executable instructions to be included in an evolved node B element (eNB) , wherein the instructions, in response to execution by the eNB, cause the eNB to:

receive a first type of sounding reference signal (SRS) over an omnidirectional transmission beam；

determine beamforming information based on the first type of SRS received over the omnidirectional transmission beam；

receive a second type of SRS over a directional transmission beam； and

determine channel quality information based on the second type of SRS received over the directional transmission beam.
The one or more computing device-readable media of claim 23, wherein the instructions are further to cause the eNB to:

transmit to user equipment (UE) a first period, first timing offset, and first frequency position for the first type of SRS； and

transmit to the UE a second period, second timing offset, and second frequency position for the second type of SRS
The one or more computing device-readable media of any of claims 23 and 24, wherein the instructions are further to cause the eNB to identify in radio resource control (RRC) , downlink control information (DCI) , or system information block (SIB) signaling a number of orthogonal frequency divisional multiplex (OFDM) symbols (N_OFDM) for association with one of the first type of SRS or second type of SRS.