Digital key visual: smartphone, truck, excavator, motorcycle and a car

Marketable solutions through industry and IT alliances using the example of the Car Connectivity Consortium

Find out how industry and IT alliances are driving innovation through common standards - and how doubleSlash is helping to shape marketable, secure and interoperable solutions in the Car Connectivity Consortium.

Creating standards together - the Car Connectivity Consortium

A digital vehicle key sounds simple at first: Opening and starting a car via smartphone, perhaps even sharing it with others. In reality, there is a complex ecosystem behind this - and this is where the Car Connectivity Consortium (CCC) into play.

Car Connectivity Consortium Logo

About 300 companies work together in the CCC:
Vehicle manufacturers, smartphone and chip manufacturers, infrastructure and software product providers. Goal: to create a Create a common, global standard, so that the digital vehicle world in the digital key sector functions reliably, securely and interoperably. For us at doubleSlash, this is more than just an industry label. It is a Best Practice - and an important lever for making innovation marketable and scalable. That's why we've been on board since 2022 and are now also a Core Member.

Why do we need a consortium like the CCC and how does it work?

Proprietary solutions are emerging in many fields of technology and industry. Everyone builds „their own system“. The result: silos, breaks in the user experience - and, in the worst case, security risks.

This would also be fatal for the digital key. Here are a few examples:

  • A key should have as many Smartphones work „out of the box“ - without additional apps that require an update after every smartphone release.
  • Key sharing should also between different smartphone manufacturer ecosystems function.
  • Security and data protection requirements must globally standardized be addressed.
  • As a product provider of hardware or software, it is important to have a standardized solution that can be used as a basis.

This is precisely why the Car Connectivity Consortium was created. It was founded in March 2011. At that time, eleven leading companies from the automotive, multimedia and mobile communications/CE sectors joined forces to promote smartphone integration in vehicles. A lot has happened since then.

The basis: The digital key specifications (3.0 and 4.0)

The CCC defines the technical basis of digital key technology. The specifications, which are continuously being developed, are particularly relevant:

  • Digital Key 3.0 specification
    Provides the core functionalities for securely storing, using, sharing and deleting the key on mobile devices and defines the interaction between backend, vehicle and smartphones.
  • Digital Key 4.0 specification
    Go one step further - with topics such as server-based key management, fleet functions and extended use cases.

These specifications ensure that the „what“ is clearly defined. The implementation is still the responsibility of the individual manufacturers, but the functionality is clearly described.

Organized in working groups - with clear responsibilities

Within the CCC, specialized working groups work on individual topics, e.g:

  • Specification & technology - Further development of the digital key standards. Anyone can submit a change request to the specification, which is then discussed and voted on.
  • Testing & Certification - Verification processes, tools and certification programs for the digital key.
  • Ecosystem & Marketing - Exchange with the industry, events and market insights are the focus here.
  • Use case groups - Definition of real application scenarios for the digital key.

This structure ensures that the CCC is geared towards market requirements and remains constantly up-to-date.

PlugFests: The ultimate interoperability check

A unique selling point compared to many consortia are the so-called PlugFests, of which there have already been 15 in total.

This is where OEMs, smartphone manufacturers, chip and software providers meet physically on site - and test their solutions together and live against each other. This is how they ensure that the digital key works in the ecosystem.

Possible scenarios:

  • Vehicle (manufacturer A) + smartphone (manufacturer X)
  • Vehicle (manufacturer B) + smartphone (manufacturer Y)

This takes place on a rotational basis. This is supported by specific testing labs that help to analyze the results. All core functionalities are tested against defined test cases.

doubleSlash has also been represented at several PlugFests and was the first backend product provider to host PlugFest 15.

The aim is always to ensure that technical problems become visible before they occur at the end customer, thereby achieving a high level of quality. Furthermore, tests are carried out with pre-series products in order to be able to assess the current status at an early stage. PlugFests are therefore a decisive driver for Interoperability and quality assurance.

Certification: Creating trust through clear evidence

In addition to the PlugFests, the CCC offers a Official certification program.
Solutions can:

  • about Authorized test labs checked or
  • as part of the Plugfests be certified.

The result: manufacturers, partners and customers can rely on the fact that a digital key system compliant, compatible and safe and meets the high requirements of the CCC.

doubleSlash's Digital Key is also officially CCC-certified. The publicly visible certification underlines doubleSlash's claim to provide interoperable and future-proof solutions and is available here.

Members Meetings: exchange, roadmaps and joint learning

The members meet several times a year to Members Meetings all over the world.

Here are:

  • Roadmaps discussed
  • Proposals for further developments presented
  • Market and technology trends evaluated
  • Experience from projects shared

For us at doubleSlash, this means:
We receive Direct insights into trends, requirements and stumbling blocks - and can actively contribute our expertise and exchange ideas with hardware, chip, smartphone and vehicle manufacturers at an early stage.

Why doubleSlash is part of the CCC

We are convinced:
Only through common standards creates truly seamless, secure and scalable mobility.

As a core member, we have developed the vehicle OEM server and key tracking server in accordance with specification 3.0 as a white label product.

And at the same time we - and therefore our customers - benefit from:

  • Access to specifications and roadmaps
  • Direct exchange with OEMs and tech companies
  • Practical knowledge from PlugFests and working groups
  • Early understanding of future developments
Banner with text "Learn more about our CCC-certified digital key solution"

Conclusion: Success in the ecosystem - collaboration as a competitive advantage

The CCC does not work in isolation. It cooperates with other standardization bodies, monitors market studies, addresses security issues and positions the topic of digital keys in the wider context of connected mobility.

The Car Connectivity Consortium shows how strong the industry and its solutions can be when they are together instead of isolated works. Interoperability, security and a consistent user experience are the result not by chance - they are the result of structured cooperation - beyond the idea of competition. And we at doubleSlash are delighted to be an active part of this.

You can find out what other useful industry alliances there are and why we are involved in them in another blog post in the near future.

Markus Beller

About ME

Markus Beller has been working as a Senior IT Consultant in the area of Connected Mobility at doubleSlash. Thanks to his many years of experience in consulting projects in the automotive environment - e.g. for BMW, Porsche and ZF - he is a proven expert in the field of Connected Car Expert in requirements management and the development of "networked services". As a Product Owner (PSO), Scrum Master (PSM) and IREB Certified Professional for Requirements Engineering - Advanced Level - Requirements Modeling, he is the person to contact when it comes to designing, implementing and testing digital front-end or back-end services.

All contributions from Markus Beller

Learn more

Further information on our website and in our newsletter

Arrow up