Deprecated and withdrawn specifications are no longer maintained by the Bluetooth SIG and are not updated with any further error corrections, clarifications, or feature enhancements. Creating qualifications/declarations for a product that uses a new Bluetooth design implementing deprecated or withdrawn specifications will not be permitted. Please learn more here.
Members integrating Components containing one or more layers claiming deprecated or withdrawn specification versions will need to either remove those specifications external to the Core or update the affected specifications external to the Core in the resulting End Product or Subsystem to an active version.
Members choosing to update specifications external to the Core from a deprecated or withdrawn version to an active version can do this by:
- Obtaining a new Qualified Design ID (QDID) by requesting the existing qualification owner to update the Component to an active specification version, or
- Claim support for the active specification version in the End Product or Subsystem listing. Active specification versions available may be type X.Y or X.Y.Z, where Y is the major version and Z is the minor version. Minor version increments to the specifications are done to release errata and do not include any new functionality, whereas new major version specifications may introduce additional mandatory features required in the implementation.
- Updates to newer specification versions require implementing applicable errata (including TSEs) and performing required testing. Test evidence from a previously qualified design may be reused if members have access to the prior test results, the qualification requirements have remained unchanged, and the evidence is not affected by the updates.
Members can update to a new minor version (e.g., HFP 1.7 to HFP 1.7.2) by:
- Determine the errata incorporated between the deprecated or withdrawn version and the errata release version of the specification.
- Implement any changes needed due to the errata.
- Change the ICS in Launch Studio for that layer to the new version.
- Generate a test plan.
- Run all tests required for that layer unless test evidence can be reused.
- Submit the updated test evidence.
Members can update to a new major version (e.g., HFP 1.7 to HFP 1.8) by…
- Perform the steps from the minor version update and additionally…
- Determine if there are any new feature requirements mandated by the more recent specification version and implement them.
- For BR/EDR layers, changes to SDP records will be needed.
- When changing the ICS in Launch Studio for that layer to the new version, add any required feature ICS and their dependencies and resolve any invalids.
If you have any questions or concerns about your particular qualification scenario, you can submit a support request or contact a Bluetooth Qualification Consultant.