FCC Web Documents citing 2.944

as compiled by hallikainen.com/FccRules on 2012 07 01

• http://fcc.gov/pshs/techtopics/techtopics4.html
  • GNU General Public License, the source code for Linux is freely available to everyone. ^10 The SDR-1000 from FlexRadio Systems was the first complete Software Defined Radio (SDR) transceiver interface to a personal computer for amateur radio use. See QST Magazine, October 2005, Vol. 89, Number 10, page 66, and [81]http://www.flex-radio.com/. ^11 See [82]http://e2r.motlabs.com/project_overview/. ^12 See, e.g., 47 C.F.R. Section 2.944. ^13 See FCC Approves First Software Defined Radio, News Release (rel. Nov. 19, 2004), available at [83]http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-254463A1.doc. Tech Topics * [84]About the Author - Bill Lane * [85]Topic 1: Interoperability * [86]Topic 2: Internet Protocol (IP) Based Interoperability * [87]Topic 3: Physical Layer Interoperability * [88]Topic 4: Software Defined Radio * [89]Topic 5: Issues of Software Defined Radio Implementations for
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-07-4605A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-07-4605A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DA-07-4605A1.txt
  • n.54; 47 C.F.R. � 90.1333. ), the grant of equipment certification may indicate both UR and RS, in which case the status of each licensee's equipment will depend on the version of the radio transmitter installed at each site. See 2007 MO&O at � 36; 47 C.F.R. � 90.1319(c). See 2007 MO&O at � 36. See also 47 C.F.R. �� 2.944 (Software defined radios) and 2.1043(Changes in certificated equipment) which describe the certification requirements for modified equipment. Section 2.1043(a) sets out the conditions under which a new grant of certification is required, and Section 2.1043(b) sets out three categories of permissive changes that may be made without the application for and grant of a new certification. In two of the three
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-284321A2.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-284321A2.txt
  • Liechtenstein $14,635,377 0.4 7.2 0.0 3.3 89.1 $21,346 0.0 0.0 0.0 0.0100.0 $546 0.0 0.0 0.0 0.0100.0 22,510,318 0.7 9.7 0.021.6 68.0 Luxembourg $2,323,606 0.037.1 0.418.3 44.2 $136,943 0.029.4 0.024.4 46.1 $273,701 0.0 0.0 0.0 0.0100.0 24,653,403 0.021.5 0.434.5 43.6 Malta $942,668 1.8 6.6 1.324.9 65.4 $84,613 0.0 0.0 0.0 5.2 94.8 $2,829 0.0 0.0 0.0 0.0100.0 5,334,174 0.7 5.6 2.944.6 46.3 Netherlands $50,465,900 0.019.5 0.4 9.8 70.4 $6,645,802 0.0 0.1 0.064.5 35.4 $4,624,161 0.0 0.0 0.0 0.1 99.9 580,189,179 0.013.7 0.339.9 46.2 Norway $13,490,830 0.025.0 0.318.1 56.6 $836,925 0.023.9 0.019.3 56.9 $2,538,915 0.0 0.0 0.0 0.0100.0 164,594,720 0.019.5 0.630.2 49.8 Portugal $16,390,237 0.015.4 1.424.4 58.7 $1,499,178 0.010.9 0.024.9 64.2 $692,194 0.0 0.0 0.0 0.5 99.5 275,602,651 0.018.1 2.422.4 57.1 Spain
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-264A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-264A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-264A1.txt
  • can be loaded into such a radio. The software must not allow the user to operate the transmitter with frequencies, output power, modulation types or other parameters outside of those that were approved. Manufacturers may use authentication codes or any other means to meet these requirements, and must describe the methods in their application for equipment authorization. A new Section 2.944 is added to read as follows: � 2.944 Submission of radio software The grantee or other party responsible for compliance of a software defined radio, or the applicant for authorization of a software defined radio shall submit a copy of the software that controls the radio frequency operating parameters upon request by the Commission. Failure to comply with such a
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-322A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-322A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-03-322A1.txt
  • Advocacy of the Small Business Administration. . FEDERAL COMMUNICATIONS COMMISSION Marlene H. Dortch Secretary APPENDIX A: PROPOSED RULE CHANGES Part 2 of Title 47 of the Code of Federal Regulations is proposed to be amended as follows: The authority citation for Part 2 continues to read as follows: AUTHORITY: 47 U.S.C. 154, 302a, 303 and 336, unless otherwise noted. Section 2.944 is proposed to be revised to read as follows. � 2.944 Submission of radio software description. Applications for certification of software defined radios must include a description and flow diagram of the software that controls the radio frequency operating parameters. Section 2.1033 is proposed to be revised by adding new paragraphs (b)(12) and (c)(18) � 2.1033 Application for certification. *
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-57A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-57A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-05-57A1.txt
  • equipment with robust security features, especially where more secure features add cost to a device. However, the Commission may consider compliance with industry security standards as a factor in determining the responsible party's liability. We are simplifying the structure of the rules for software defined radios by moving the security requirements for software defined radios from Section 2.932(e) into Section 2.944. Section 2.944 currently contains a requirement for parties to submit a copy of radio software to the Commission upon request. As discussed below, we are changing that requirement as well as the applicability of the security requirements for software defined radios. We are placing the requirements for software defined radios into a single rule section, Section 2.944, for easier reference.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-56A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-56A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-56A1.txt
  • at 7. Consumer Electronics Association comments at 9 and Intel comments at 5. Hewlett Packard comments at 8, IEEE 802 comments at 6, and Wi-Fi Alliance comments at 7. We will consider changes to either part of an approved split module consistent with the variations permitted under the permissive change rules. See 47 C.F.R. � 2.1043(b). See 47 C.F.R. � 2.944(a). See 5 U.S.C. � 603. The RFA, see 5 U.S.C. � 601-612, has been amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA), Pub. L. No. 104-121, Title II, 110 Stat. 857 (1996). See 5 U.S.C. 603, Title II, 110 Stat 857 (1996). See U.S.C. � 603(b)(3). Id. � 601(3). Id. � 632. NAICS code 334220. Id.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-66A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-66A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-07-66A1.txt
  • SDRs than the rules are intended to require. We find that the appropriate solution to Cisco's concern is to add an additional sentence following the definition of SDR to indicate the class of radios that must be certified as SDRs. We are therefore clarifying the rules by adding the following statement to the definition of SDR: ``In accordance with � 2.944 of this part, only radios in which the software is designed or expected to be modified by a party other than the manufacturer and would affect the above-listed operating parameters or circumstances under which the radio transmits must be certified as software defined radios.'' This action clarifies the intent of the rules adopted in the Cognitive Radio Report and Order.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-12A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-12A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-12A1.txt
  • Commission: 1) clarified that its rules did not require the submission of radio software source code; 2) clarified the rules concerning the certification of software defined amateur radio equipment; and 3) declined to initiate a further proceeding to adopt regulatory requirements for high-power, high-speed digital-to-analog (D/A) converters. See MO&O at 8056. See 47 C.F.R. � 1.429(b). See 47 C.F.R. � 2.944. See 47 C.F.R. �0.457(d)(1)(ii). (...continued from previous page) (continued....) Federal Communications Commission FCC 10-12 Federal Communications Commission FCC 10-12 � � F 0 0 t" �Tru 5() bars Macros" etToolba�rs() _'� Exit �- r� ule1" �.E � �.E c5Œ�� �.E ID="{E0CFFC47-261C-4C48-85D4-3E4018BD17B2}" Document=ThisDocument/&H00000000 Module=NewMacros Module=Module1 Name="TemplateProject" HelpContextID="0" VersionCompatible32="393222000" CMG="A0A2498F4D8F4D8F4D8F4D" DPB="FFFD16B92A478848884888" GC="5E5CB71A4926A927A92756" [Host Extender Info] &H00000001={3832D640-CF90-11CF-8E43-00A0C911005A};VBE;&H00000000 &H00000002={000209F2-0000-0000-C000-000000000046};Word8.0;&H00000000 [Workspace] ThisDocument=110, 110, 520, 455,
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-145A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-145A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-145A1.txt
  • FCC Rcd at 16771, 16774 �� 44, 49. We also discussed the availability of technology that could be incorporated into phones to enable them to meet the standards. Id. at 16772-74, �� 45-48. 47 U.S.C. � 610(b)(3). See 47 C.F.R. �� 2.909, 2.932, 2.1043. We note that unless a phone is approved as a Software Defined Radio (SDR) under Section 2.944(b) of our rules, third party software cannot modify ``the circumstances under which the transmitter operates in accordance with Commission rules.'' 47 C.F.R � 2.944(b). As an interim measure, such handsets may be considered hearing aid-compatible but must be labeled as not having been tested for all operations. See supra, Section IV A 3. 2003 Hearing Aid Compatibility Order, 18 FCC
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-145A1_Rcd.pdf
  • Rcd at 16771, 16774 �� 44, 49. We also discussed the availability of technology that could be incorporated into phones to enable them to meet the standards. Id. at 16772- 74, �� 45-48. 18547 U.S.C. � 610(b)(3). 186See 47 C.F.R. �� 2.909, 2.932, 2.1043. 187We note that unless a phone is approved as a Software Defined Radio (SDR) under Section 2.944(b) of our rules, third party software cannot modify "the circumstances under which the transmitter operates in accordance with Commission rules." 47 C.F.R � 2.944(b). 188As an interim measure, such handsets may be considered hearing aid-compatible but must be labeled as not having been tested for all operations. See supra, Section IV A 3. 11198 Federal Communications Commission FCC 10-145 capabilities.
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-174A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-174A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-10-174A1.txt
  • software change. See 47 C.F.R. � 2.1. A transmitter in which the software is designed or expected to be modified by a party other than the manufacturer must be certified as a software defined radio and must incorporate measures to ensure that only software that has been approved with the transmitter can be loaded into it. See 47 C.F.R. � 2.944. A manufacturer can obtain approval to expand the frequency range of a previously approved software defined radio through a Class III permissive change, which is a modification to an existing certification. See 47 C.F.R. � 2.1043(b). See ex parte letter of July 19, 2010 to Julius Knapp, Chief of the Commission's Office of Engineering and Technology from Atheros Communications, Broadcom
• http://transition.fcc.gov/Bureaus/Engineering_Technology/Orders/2001/fcc01264.doc http://transition.fcc.gov/Bureaus/Engineering_Technology/Orders/2001/fcc01264.pdf http://transition.fcc.gov/Bureaus/Engineering_Technology/Orders/2001/fcc01264.txt
  • can be loaded into such a radio. The software must not allow the user to operate the transmitter with frequencies, output power, modulation types or other parameters outside of those that were approved. Manufacturers may use authentication codes or any other means to meet these requirements, and must describe the methods in their application for equipment authorization. A new Section 2.944 is added to read as follows: � 2.944 Submission of radio software The grantee or other party responsible for compliance of a software defined radio, or the applicant for authorization of a software defined radio shall submit a copy of the software that controls the radio frequency operating parameters upon request by the Commission. Failure to comply with such a
• http://transition.fcc.gov/pshs/techtopics/techtopics4.html
  • GNU General Public License, the source code for Linux is freely available to everyone. ^10 The SDR-1000 from FlexRadio Systems was the first complete Software Defined Radio (SDR) transceiver interface to a personal computer for amateur radio use. See QST Magazine, October 2005, Vol. 89, Number 10, page 66, and [81]http://www.flex-radio.com/. ^11 See [82]http://e2r.motlabs.com/project_overview/. ^12 See, e.g., 47 C.F.R. Section 2.944. ^13 See FCC Approves First Software Defined Radio, News Release (rel. Nov. 19, 2004), available at [83]http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-254463A1.doc. Tech Topics * [84]About the Author - Bill Lane * [85]Topic 1: Interoperability * [86]Topic 2: Internet Protocol (IP) Based Interoperability * [87]Topic 3: Physical Layer Interoperability * [88]Topic 4: Software Defined Radio * [89]Topic 5: Issues of Software Defined Radio Implementations for
• http://www.fcc.gov/Bureaus/Engineering_Technology/Orders/2001/fcc01264.doc http://www.fcc.gov/Bureaus/Engineering_Technology/Orders/2001/fcc01264.pdf http://www.fcc.gov/Bureaus/Engineering_Technology/Orders/2001/fcc01264.txt
  • can be loaded into such a radio. The software must not allow the user to operate the transmitter with frequencies, output power, modulation types or other parameters outside of those that were approved. Manufacturers may use authentication codes or any other means to meet these requirements, and must describe the methods in their application for equipment authorization. A new Section 2.944 is added to read as follows: � 2.944 Submission of radio software The grantee or other party responsible for compliance of a software defined radio, or the applicant for authorization of a software defined radio shall submit a copy of the software that controls the radio frequency operating parameters upon request by the Commission. Failure to comply with such a
• http://www.fcc.gov/ib/sand/mniab/traffic/files06/CREPOR06.PDF
  • Liechtenstein $14,635,377 0.4 7.2 0.0 3.3 89.1 $21,346 0.0 0.0 0.0 0.0100.0 $546 0.0 0.0 0.0 0.0100.0 22,510,318 0.7 9.7 0.021.6 68.0 Luxembourg $2,323,606 0.037.1 0.418.3 44.2 $136,943 0.029.4 0.024.4 46.1 $273,701 0.0 0.0 0.0 0.0100.0 24,653,403 0.021.5 0.434.5 43.6 Malta $942,668 1.8 6.6 1.324.9 65.4 $84,613 0.0 0.0 0.0 5.2 94.8 $2,829 0.0 0.0 0.0 0.0100.0 5,334,174 0.7 5.6 2.944.6 46.3 Netherlands $50,465,900 0.019.5 0.4 9.8 70.4 $6,645,802 0.0 0.1 0.064.5 35.4 $4,624,161 0.0 0.0 0.0 0.1 99.9 580,189,179 0.013.7 0.339.9 46.2 Norway $13,490,830 0.025.0 0.318.1 56.6 $836,925 0.023.9 0.019.3 56.9 $2,538,915 0.0 0.0 0.0 0.0100.0 164,594,720 0.019.5 0.630.2 49.8 Portugal $16,390,237 0.015.4 1.424.4 58.7 $1,499,178 0.010.9 0.024.9 64.2 $692,194 0.0 0.0 0.0 0.5 99.5 275,602,651 0.018.1 2.422.4 57.1 Spain
• http://www.fcc.gov/pshs/techtopics/techtopics4.html
  • GNU General Public License, the source code for Linux is freely available to everyone. ^10 The SDR-1000 from FlexRadio Systems was the first complete Software Defined Radio (SDR) transceiver interface to a personal computer for amateur radio use. See QST Magazine, October 2005, Vol. 89, Number 10, page 66, and [81]http://www.flex-radio.com/. ^11 See [82]http://e2r.motlabs.com/project_overview/. ^12 See, e.g., 47 C.F.R. Section 2.944. ^13 See FCC Approves First Software Defined Radio, News Release (rel. Nov. 19, 2004), available at [83]http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-254463A1.doc. Tech Topics * [84]About the Author - Bill Lane * [85]Topic 1: Interoperability * [86]Topic 2: Internet Protocol (IP) Based Interoperability * [87]Topic 3: Physical Layer Interoperability * [88]Topic 4: Software Defined Radio * [89]Topic 5: Issues of Software Defined Radio Implementations for