FCC Logo - Return to the FCC Home Page
Office of Engineering and Technology


Print This Window
There have been 2 comment(s) made on this document:
  • Cinnamon Rogers commented on 2017-06-30 16:40:56.273:
    Attached, please find comments of the Telecommunications Industry Association on Draft KDB 285076 D01 HAC Guidance v05. View attachment associated with this comment

  • Justin Chao commented on 2017-06-30 11:17:56.21:
    1. In regard to Appendix B on page 10 and the example air interfaces table: a) Please clarify if the name of voice services for non-VoIP modes that need to be listed as well. b) Please clarify if OTT voice services (e.g. Skype, Hangouts, etc) would be a “VD” type air interface for 3G data services (e.g. EDGE, HSPA, EVDO) if supported. c) Please clarify if ‘Wi-Fi Calling’ should be referenced with a double or triple asterisk to indicate the -20dBm0 signal level or KDB inquiry level. d) PCTEST suggests updating this table to add missing entries for HSPA in the ‘ANSI C63.19 Tested’ and ‘Name of Voice Service’ columns. e) PCTEST suggests including an example air interfaces table with an example device can best illustrate the requirements in the air interfaces table. 2. In regard to the example codec investigation table on page 14, PCTEST suggests updating the ‘S/N (dB)’ row to ‘S+N/N (dB)’ to be consistent with the measurement required of ANSI C63.19. 3. PCTEST suggests updating section 3.C to reference section D.7 instead of section in ANSI C63.19. D.7 outlines the necessary test method for determining MIF values of a device. 4. In regard to the codec investigation requirement, is this requirement only applicable to VoIP operations (ie VoLTE, VoWIFI and OTT services), or is it applicable to all operations with multiple codec rates (ie UMTS AMR voice services)? We assumed it incorporates any with multiple code rates, not limited to VOIP. Furthermore, does each air interface need to have all their respective codecs investigated? The current wording implies that only the overall worst-case codec per device needs to be evaluated but this implies the test lab checking all of them to some degree. Thank you for your consideration.

Note: It is important to understand that the staff guidance provided in the KDB is intended to assist the public in following Commission requirements and does not constitute rules. Accordingly, the guidance is not binding on the Commission and will not prevent the Commission from making a different decision in any matter that comes to its attention for resolution.