I85PREP
⌘ K
Engineer Information Communications study materials
Engineer Information Communications study resources

Engineer Information Communications: Communication Law and Standards

Engineer Information Communications · Work through your exam, one topic at a time.

All guide sections

Communication Law and Standards

This domain tests the legal and standards framework around communications: which body produces which standard, how spectrum is allocated, what equipment approval and privacy obligations apply, and how standards interact with regulation. Jurisdiction-specific rules vary, so identify the governing authority before applying a rule.

Core rules

  • ITU has three sectors: ITU-T for telecommunications standards (for example SDH and optical transport recommendations), ITU-R for radio spectrum and satellite matters, and ITU-D for development. The Radio Regulations divide the world into three regions: Region 1 (Europe, Africa, Middle East), Region 2 (Americas), and Region 3 (Asia-Pacific).
  • IEEE produces LAN standards such as IEEE 802.3 Ethernet and IEEE 802.11 Wi-Fi. IETF publishes Internet RFCs, including RFC 791 (IPv4), RFC 8200 (IPv6), RFC 9293 (TCP), and RFC 8446 (TLS 1.3). 3GPP produces LTE and 5G NR specifications. ISO/IEC publishes the OSI reference model and many security standards.
  • Spectrum is generally licensed, with licence-exempt bands subject to power and duty-cycle limits. Equipment typically requires type approval or certification before sale or connection.
  • Privacy and interception rules restrict handling of communications metadata and content; lawful interception requires legal authority.

Worked example

A vendor advertises a device supporting "5G NR Release 15, Wi-Fi 6, and TLS 1.3." Identify the bodies: 5G NR is specified by 3GPP; Wi-Fi 6 is IEEE 802.11ax; TLS 1.3 is IETF RFC 8446. A compliance claim must cite the correct standard and version, not a marketing label. A national regulator may still require spectrum licensing and equipment approval before the device can be operated.

Traps

  • Confusing ITU-T (telecom standards) with ITU-R (radio spectrum).
  • Assuming a globally harmonized band or power limit; regional allocations differ.
  • Treating an industry standard as automatically legally binding.
  • Citing a protocol name without its RFC or release number.
  • Ignoring type approval and licence conditions when assessing lawful deployment.