PL83220035_RFI_188-165Bv2_AMEND.pdf

PDF 258 KB Posted

Attached to
INDUSTRY DAY FOR CHANGE NOTICE TO MIL-STD-188-165B
Solicitation number
PL83220035
Issued by

About this file

Amended RFI document with highlighted change

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

REQUEST FOR INFORMATION (RFI)

PL83220035

MIL-STD-188-165B

INDUSTRY DAY

REQUIREMENT: INDUSTRY DAY FOR CHANGE NOTICE TO MIL-STD-188-165B

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. THIS IS NOT A REQUEST FOR

PROPOSALS. NO SOLICITIATION IS AVAILABLE AT THIS TIME.

1.0 GENERAL

PURPOSE: The Department of Defense (DoD) is soliciting industry to provide comments on the

MIL-STD-188-165B Draft and prepare responses to satisfy unique DoD requirements for the

Draft. Responses should include, but are not limited to, specification adjustments in the following areas of interest: 1) Baseband Interfaces; 2) Spectral Confinement; 3) Transmit

Thermal Noise; 4) Demodulator Noise Figure; and 5) Demodulator Single Carrier Minimum and

Maximum Level and Maximum Composite Level.

This RFI request is solely for gathering information and planning purposes. This RFI does not commit the U.S. Government to contract for any services or supplies whatsoever. All are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not preclude participation in any future solicitations or requests for proposal (RFPs).

2.0 ISSUES

BACKGROUND: The continuing evolution of modem capabilities presents a number of challenges to developing relevant and useful modem design requirements. When MIL-STD 188-

165 was first written, the preponderance of modems consisted of a limited set of modems with very few modulation and coding capabilities. This is no longer the case. In recognition of this, a number of adjustments have been made in the Draft for MIL-STD 188-165B. In the process of drafting the new MIL-STD, a number of areas have been identified where additional investigation is necessary to craft a useful MIL-STD. In the interest of issuing meaningful guidance as soon as possible, it has been decided to pursue issuing MIL-STD 188-165B in the near future while simultaneously investigating various areas of interest with the intent of including any updates to those areas in a future CN1.

3.0 INFORMATION REQUESTED

3.1 Baseband Interfaces: The existing 165A specifies serial interfaces and does not take into account more modern Ethernet interface designs. Integration and testing experience shows modems moving into the Ethernet interface designs over serial to allow for increased data throughput and more flexibility with baseband environments.

3.2 Spectral Confinement: The government recognizes the current requirement is not conducive to steeper roll-off factors, for example, those less than 0.20. The new requirement is intended to allow for steeper roll-offs and consequently closer carrier placement.

3.3 Transmit Thermal Noise: Terminal thermal noise EIRP density (dBm/Hz), has created unacceptable levels of interference on WGS, causing satellite G/T degradation. Changes have been made in 164B and we anticipate including a maximum modulator output thermal noise density. Currently in 165A there is no such corresponding requirement.

Is -142 dBm/Hz a reasonable value? If not what are the drivers causing this to be unreasonable?

For other IF output levels will the thermal noise power density scale e.g.

-132 dBm/Hz for a +10 dBm signal output level and -152 dBm/Hz for a -10 dBm signal output power?

3.4 Demodulator Noise Figure: Currently 164B requires the terminal to provide a noise power spectral density level to the demodulator of -103 dBm/Hz. This is a high value causing linearity performance issues for the terminal and there is interest in reducing this level to -120 dBm/Hz. There are several issues with such a change, including a concern that a poor demodulator noise figure could degrade modem performance. There is not a noise figure requirement in 165A.

Is noise figure a parameter that is regularly known and measured for a demodulator?

Is a 37 dB noise figure reasonable for an L-Band demodulator? If not what are the drivers causing the value to be unreasonable?

Is a lower noise figure achievable, without heroic efforts, such as putting in a front end LNA?

How would demodulator noise figure be measured?

3.5 Demodulator Single Carrier Minimum and Maximum Level and Maximum

Composite Level: Currently 165A requires a minimum level of -55 dBm for all carriers without regard to waveform or data rate. This leads to scenarios of very high composite power at the modem input, especially for a demodulator fed from large aperture antennas and when exposed to conditions of maximum power flux density from the satellite.

Essentially three separate requirements are intended to replace the IF input level section currently in 165A.

Minimum operating IF input level

Minimum power level = -120 dBm/Hz + 10*Log(R) + Eb/No (dB)

Where R is data rate in bits/s

Maximum operating IF input level

Maximum carrier power level = -3 dBm/MHz +10*log(SR)

Where SR is symbol rate in Msymbols/sec

Composite Power level

Maximum composite power +20 dBm

In 165A the minimum level was a fixed -55 dBm regardless of data rate. We are now suggesting a minimum level based primarily on data rate, in general is this a better approach?

Is the format of the minimum level equation optimal? For example, should the equation be based on symbol rate and Es/No?

The minimum, maximum and composite values are tied together. If for example in the minimum level equation a change to -125 dBm/Hz noise power density was made (from -120 dBm/Hz) then the maximum carrier and composite values could drop by 5 dB. However, for the -125 dBm/Hz value the noise figure would need to be reduced from 37 dB to 32 dB. We don’t have compelling rational for the -120 dBm/Hz value, but there are benefits to the terminal (as defined in 164B) in not exceeding this value. Is there a sweet spot for the noise power density value in the equation to obtain optimum balance between the various competing parameters?

The minimum level equation is open ended in terms of data rate. For example, if the data rate was 1bit/s then the minimum level would be -120 dBm + Eb/No. Is this a reasonable expectation or should the data rate be bounded?

The assumption regarding minimum carrier level is that the driving factor is maintaining C/N and provided C/N is maintained, then the demodulator will operate successfully. Is this a correct assumption, or are there situations where the carrier power can be too low for successful operation even though the C/N is acceptable?

For example, the demodulation circuitry may need some minimum power level regardless of C/N.

Are the successful behaviors of acquisition and timing, re-acquisition and synchronization retention affected by the suggested new language for receive carriers. For example, will a carrier at the minimum receive level, while in the presence of maximum composite power level, meet the various acquisition and timing performance criteria?

4.0 INDUSTRY DAY

The MIL-STD-188-165B Industry Day will occur on Monday, 18th September 2017 to Thursday

21st September 2017 from 0830 – 1630 at SSC PAC in San Diego, California. The meeting will be in the main auditorium.

SSC PAC requires all attendees without CACs vetted for access to Naval Base Point Loma/SSC

Pacific. Please complete a Visitor “Registration” Information form and send the form to Ms.

Yvonne Sanchez (Yvonne.sanchez@navy.mil). The dead line for attendees to send in Visitor

Registration Form is August 18 th

, 2017, and presenters to send in briefing materials is June 30th, 2017.

For those attendees who are Foreign Nationals, you will be required to complete a special paperwork following the Foreign Visitor Access Information attached and contact Ms. Yvonne

Sanchez as soon as possible to request your Foreign National paperwork. Please complete and submit your paperwork one month in advance before the meeting date in order for the vetting process to be completed in time.

More detailed information on Industry Day to be provided at a later date.

Jacqueline.Johnson Highlight

The Mil-Std-188-165B meeting is UNCLASSIFIED. DISA requests that all Presenters send in their briefing slides and title to the POCs below to have added in the meeting agenda, and

Presentation for each subject is not more than 20 minutes long. The meeting will begin promptly at 8:30 am. We recommend that you plan to arrive not later than 8:00 am to accommodate for check-in delays.

5.0 POINTS OF CONTACT (POCs)

Henry Tran at DISA

Phone: 301-225-7496

NIPR: henry.h.tran.civ@mail.mil

Mr. Jeremy Kozee at USASMDC/ARSTRAT

Phone: 719-554-8835

NIPR: jeremy.r.kozee.civ@mail.mil

Mr. Mike Rhoades at USASMDC/ARSTRAT

Phone: 719-554-2017

NIPR: mike.d.rhoades3.civ@mail.mil

6.0 DISCLAIMER

This RFI is issued for information and planning purposes only to identify sources that can provide comments on the MIL-STD-188-165B Draft and provide specifications to requested information noted in Section 3.0 and does not constitute a solicitation

THE GOVERNMENT DOES NOT INTEND TO AWARD A CONTRACT ON THE BASIS

OF THE RFI OR OTHERWISE PAY FOR INFORMATION RECEIVED IN RESPONSES TO

THE RFI.

Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received that is marked Proprietary will be safeguarded in accordance with the applicable Government regulations. Please be advised that all submissions become Government property and will not be returned. The Government shall not be liable for or suffer any consequential damages for any proprietary information not properly identified. All government and contractor personal reviewing RFI responses will have signed non-disclosure agreements and understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information as described 41 USC 423.

mailto:henry.h.tran.civ@mail.mil mailto:jeremy.r.kozee.civ@mail.mil mailto:mike.d.rhoades3.civ@mail.mil

File details come from the government source that posted it. Updated .