Skip to main content

ICS Form Inconsistencies for Inter-Layer Dependencies

Bluetooth Support
  • Updated

Introduction

Qualification Workspace enforces Inter-Layer Dependencies (ILDs) of designs used in the Qualification Process. Enforcing ILDs promotes product compliance and interoperability.

Members using Option 2b to specify their design (see QPRD Section 3.2.2.2) may encounter inconsistencies reported by the Consistency Check during the ICS Selection step in Qualification Workspace.

Options to address inconsistencies

When there are inconsistencies, a member has the following options to address the issue:

  • Provide a Test Coverage Waiver (TCW) that addresses the inconsistencies.
    • TCWs are filed in the Bluetooth® SIG Errata System. You can search for existing TCWs in the Bluetooth SIG Errata System.
    • If a TCW does not exist and you believe one or more inconsistencies are being enforced incorrectly, you can submit a new TCW. The TCW will be reviewed and approved or denied by the Bluetooth Test and Interoperability Committee (BTI).
  • Request your supplier to submit an ICS Correction Request. If the inconsistency is due to an error in the ICS Form of your supplier's design, ask them to submit an ICS Correction Request via a support request.
  • Request your supplier to create a subset design that you can include in your submission. If the inconsistency requires you to remove optional capabilities in a locked layer, ask your supplier to create a subset Design Number (DN) that removes the optional capabilities. See Create a Subset of a Design for details.
  • Make changes to the ICS Form and resolve the inconsistencies. These changes will require assessing/testing any new and unlocked layers against the latest TCRL package requirements.

TCWs that may be applicable

Review the scope of each waiver below to determine if it is applicable to your submission.

TCW Description
TCW ES-25736 Ignore Qualification Workspace invalids due to ATT 4/30 ILD
TCW ES-25780 Waive Qualification Workspace invalids about missing TBS layer when only GTBS was supported in a referenced QDID
TCW ES-25781 Waive Qualification Workspace invalids about missing MCS layer when only GMCS was supported in a referenced QDID
TCW ES-25802 TCW for ignoring incorrect BAP invalids from Table 85 due to Client/Server role error mismatch
TCW ES-25871 Waive ILD check invalid for qualification project with included design which did not show RFPHY 1/15 in locked RFPHY layer
TCW ES-25897 Allow devices to qualify without Erroneous Data Reporting for eSCO when supporting SWB speech in LC3
TCW ES-26007 TCW for X2Core only modification/addition to waive Core invalids where no changes were made to referenced QDIDs/DNs of Core Host Configuration plus Core Controller Configuration
TCW ES-26010 TCW for X2Core only modification/addition to waive Core invalids where no change was made to Core Layers of referenced single QDID with "End Product" type or single DN with "Core Complete" configuration
TCW ES-26108 Ignore "LE Core-Complete Configuration requirements are not met" when Host Subsystem and Controller Subsystem QDIDs are LE Only
TCW ES-26149 Waive consistency check invalids related to CS features in GAP.ICS if CS (Channel Sounding) is not supported

Still need help

If you have questions or need further assistance, please contact Bluetooth SIG Support.

This KBA is intended to provide Bluetooth SIG members with helpful information and address frequently asked questions. Governing documents, membership agreements, policies, and other Bluetooth SIG rules and guidelines can be found on the Bluetooth SIG Governing Documents page.

Related articles