Comparison of Credential Management Systems Based on the Standards of IEEE, ETSI, and YD/T 3957-2021

arXiv:2603.03376 · cs.CR, cs.NI, cs.PF · Submitted 2026-03-03 · Read on arXiv

Listen

Radio episode about this paper

Transcript

Introduction to the show: ident: Security Radio. Generated commentary on the latest security and cryptography papers.

Nadia: I'm Nadia.

Elias: And I'm Elias, here with Priya.

Nadia: We're looking at the paper: "Comparison of Credential Management Systems Based on the Standards of IEEE, ETSI, and YD/T 3957-2021".

Title and authors: Nadia: So, we've talked about what the paper is titled and why it matters—it’s about comparing IEEE, ETSI, and YD/T three thousand nine hundred fifty-seven-two thousand twenty-one to find compatibility issues <ref:2603.03376#pg1,IEEE, ETSI, and YD/T 3957-2021>. Now let's look at what the actual summary of this work says.

Elias: The summary boils down to analyzing three main things: the certificate formats, the signed message formats, and how those requests are handled between different standards. It sets up a baseline for developing a secure system that can handle all three environments simultaneously.

Priya: That sounds like the core challenge for anyone trying to deploy V2X technology across different regions or partners; you need a way to make sure your device works everywhere, right?

Nadia: Exactly. The paper explains that they're not just listing standards side-by-side; they are actively comparing how the structure of those signed messages looks and what cryptographic methods are being used underneath them.

Elias: They specifically look at the Ieee1609 Dot2 Data format for signed messages, and how different systems use things like SHA256 with ECDSA versus SM2 with SM2-two hundred fifty-six <ref:2603.03376#pg1>. That’s a lot of detail packed into that comparison.

The paper's summary: Nadia: To break down the summary, the authors show how they categorize certificates into enrollment and authorization types, and they explain that in both SCMS and C-SCMS, you use an enrollment certificate to ask an Authorization Certificate Authority for a signed message key.

Elias: That's a key point. Then they highlight that the way this request is made—whether it’s through SCMS or CCMS—can default to using implicit certificates or explicit certificates, which changes how verification happens later on.

Priya: I wonder if that difference in certificate type is important for privacy or security testing? If one system defaults to explicit and another to implicit, that means the verification steps are fundamentally different.

Nadia: It definitely matters because it affects how much data is exposed during the request process. And they also look at the cryptographic efficiency of the methods used, like comparing NIST P-two hundred fifty-six against SM2-two hundred fifty-six for signing speed and computation time <ref:2603.03376#pg1>.

Elias: They found that while key generation times might be similar between curves like NIST P-two hundred fifty-six and SM2-two hundred fifty-six the actual signature creation takes more time with SM2 because it needs an extra hashing calculation <ref:2603.03376#pg1,NIST P-256 and SM2-256>.

The paper's improvements: Nadia: So, what do the authors suggest to make this comparison better than just a simple list? They propose looking at how the standards themselves evolve and what changes they are making to their protocols.

Elias: They suggest that future work could focus on implementing implicit certificates in both CCMS and C-SCMS so they can compare systems using that same default certificate type across all three standards.

Priya: That would give us a much more complete picture of the actual performance trade-offs when you are trying to deploy these systems in the real world, not just theoretical comparisons.

Nadia: Right. They also hint that they should look at how different cryptographic methods scale with different message sizes, which is a big practical concern for V2X devices handling everything from small safety messages to larger data packets.

Elias: And they point out that the variations in parameters—like using SM4-one hundred twenty-eight versus AES-one hundred twenty-eight for encryption—show that efficiency isn't just about the curve, but about which specific algorithm you pick for different tasks <ref:2603.03376#pg1>.

Conclusion: Nadia: So, to wrap up this look at the paper "Comparison of Credential Management Systems Based on the Standards of IEEE, ETSI, and YD/T three thousand nine hundred fifty-seven-two thousand twenty-one" it seems the main finding is that while standards are moving toward compatibility in certificate formats, the differences really boil down to those specific cryptographic choices and how they handle request processes <ref:2603.03376#pg1,Comparison of Credential Management Systems Based on the Standards of IEEE, ETSI>.

Elias: That's right. The paper shows that when you look at efficiency, things like SM3-two hundred fifty-six actually show better computational performance than standard SHA-two hundred fifty-six for hashing tasks <ref:2603.03376#pg1>.

Priya: So, for a system designer looking at this, the implication is that choosing the right cryptographic method isn't just about what looks secure on paper; it’s about how fast the device can actually process those signatures in real time while maintaining a certain level of security.

Nadia: Right. And they also noted that SCMS uses implicit certificates by default, which requires an extra step involving the Authorization Certificate Authority public key reconstruction, leading to longer computation times when verifying packets.

Elias: That's the practical catch for those systems—the implicit certificate model introduces a dependency on a pre-existing public key that adds latency during verification.

Priya: So, ultimately, this research gives us a reference point to decide which system structure is best suited for our deployment goals based on performance metrics and security requirements.

Nadia: That’s the gist of it. We looked at how IEEE one thousand six hundred nine ETSI, and YD/T three thousand nine hundred fifty-seven-two thousand twenty-one stack up in terms of certificates, messages, and crypto efficiency using this paper as our guide <ref:2603.03376#pg1,ETSI, and YD/T 3957-2021>.

Elias: It's a solid comparison for anyone building cross-standard V2X solutions who needs to understand the performance cost of choosing one cryptographic signature over another.

Chunghwa Telecom Laboratorie

cs.CR, cs.NI, cs.PF

Submitted: 2026-03-03

Updated: 2026-03-03

DOI: 10.1007/978-3-032-28532-4_10

License: http://arxiv.org/licenses/nonexclusive-distrib/1.0/

Importance score: 76/100

The gist: Comparison of Credential Management Systems Based on the Standards of IEEE, ETSI, and YD/T 3957-2021 is a study that analyzes and compares three major credential management standards—IEEE 1609…

Key concepts

Certificate Structures
This refers to the format used to identify V2X devices. The study notes that the CertificateBase format from IEEE 1609 is adopted, categorizing certificates into enrollment (for legal ID) and authorization (for sending signed messages).
Signed Message Formats
This describes how data packets are secured for V2X communication. Standards like Ieee1609Dot2Data-Signed define fields such as hashId, tbsData, signer, and signature. Different systems use different signing algorithms (e.g., ECDSA or SM2) to create these secure messages.
Cryptographic Method Efficiency
This evaluates how fast different mathematical operations are when used for security tasks like signing and encryption. The analysis shows that SM2-256 can be slower than NIST P-256 for signing, while SM3-256 is computationally faster than SHA-256 for hashing.
Certificate Application Processes
This examines how systems handle the process of using certificates. A key difference found is that SCMS uses implicit certificates, which requires reconstructing an ACA public key and takes longer to verify packets compared to CCMS or C-SCMS which use explicit certificates.

Terminology

Summary

Comparison of Credential Management Systems Based on the Standards of IEEE, ETSI, and YD/T 3957-2021 is a study that analyzes and compares three major credential management standards—IEEE 1609 series, ETSI series, and YD/T 3957-2021—to achieve compatibility across V2X networks by examining certificate formats, signed message formats, request processes, and cryptographic method efficiencies. p. 0 This research provides a reference for developing a secure certificate management system for V2X networks through implementation and comparison. p. 0

Standard Comparison of Certificate Structures

The study analyzes the structure of certificates to ensure compatibility between different standards, noting the adoption of the CertificateBase format defined by IEEE 1609.2 [1]. Certificates are categorized into two main types based on their issuer: enrollment certificates and authorization certificates. p. 0 Enrollment certificates are issued by the Enrollment Certificate Authority (ECA) to serve as the legal identification for a V2X device, while authorization certificates are requested using the enrollment certificate from an Authorization Certificate Authority (ACA) for sending signed messages. p. 0

Analysis of Signed Message Formats

To ensure compatibility among V2X packets, various standards have adopted the Ieee1609Dot2Data format in recent years. The structure of signed messages is defined by Ieee1609Dot2Data-Signed, which mainly includes four fields: hashId, tbsData, signer, and signature. p. 1 In SCMS, the EE sets the hashId to SHA256 and generates the signature using ECDSA with NIST P-256. p. 1 Conversely, in C-SCMS, the EE uses the SM2 signature algorithm with SM2-256 for signing. p. 1

Evaluation of Cryptographic Method Efficiency

The paper evaluates the computational efficiency of various cryptographic methods by implementing them on a laptop with specified hardware and software. Key comparisons include:

  1. NIST P-256 and SM2-256 for signing show that SM2 requires an additional hashing calculation, resulting in more computation time for signature creation compared to ECDSA. p. 3

  2. ECIES with elliptic curve NIST P-256 and elliptic curve SM2-256 show no significant difference in key generation time, key encapsulation time, or key extraction time. p. 3

  3. SHA-256 and SM3-256 show that SM3-256 has higher computational efficiency with a significantly lower computation time compared to SHA-256. p. 3

  4. AES-128 and SM4-128 demonstrate similar computational efficiencies for both encryption and decryption, although SM4-128 has slightly lower computation times. p. 4

Performance Comparison in V2X Devices

Implementation on Clientron’s OnBoard Units (OBUs) compares the performance of the standards when sending and verifying Basic Safety Messages (BSMs). In signature generation, C-SCMS takes longer to produce packets containing BSM information because it uses the SM2 signature algorithm which requires more computation time. p. 4 During verification, CCMS and C-SCMS use explicit certificates by default, resulting in shorter computation times compared to SCMS which uses implicit certificates and requires ACA public key reconstruction. p. 4

Conclusion on Standard Compatibility

The research findings indicate that international standards are gradually becoming compatible, with certificate formats and signed message packet formats aligning. The main differences lie in the certificate application processes and the packets used for certificate requests, as well as the cryptographic methods and their parameters. p. 5 Future work could implement implicit certificates in CCMS and C-SCMS to allow for a more comprehensive comparison based on implicit certificates. p. 5

ACKNOWLEDGMENT

The RCA certificate developed in this study has successfully undergone interoperability testing at the OmniAir Plugfest conference and has been officially listed in the Test Certificate Trust List (CTL) by the SCMS Manager, available at: https://www.scmsmanager. p. 5org/publications/. p. 5 Additionally, this certificate has also been recognized and included in the European Certificate Trust List (ECTL), maintained by the EU C-ITS Point of Contact (CPOC), which can be accessed at: https://cpoc. p. 5jrc.ec.europa.eu/ECTL.html.

Green — the paper says it, and the page is printed. Red — no passage carries it, so treat that sentence as unverified. The same check runs on your own text: check a summary against its source, $5.

Improvements for AI systems

  1. Improved AI systems can be designed to handle cross-standard compatibility by analyzing the similarities and differences between the three major standards (IEEE 1609 series, ETSI series, and YD/T 3957-2021) to ensure seamless communication across different national environments.

  2. Improved AI systems can perform comparative efficiency analysis of cryptographic methods by measuring the key generation time, signature generation time, and signature verification time for NIST P-256 versus SM2-256 and AES-128 versus SM4-128 to select the most computationally efficient algorithms for real-time V2X operations.

  3. Improved AI systems can optimize message signing processes by utilizing the findings that ECDSA outperforms SM2 in signing efficiency and SM3 demonstrates better performance than SHA in hash computation efficiency, leading to faster packet creation on resource-constrained V2X devices.

  4. Improved AI systems can enhance security verification speed by prioritizing the use of explicit certificates, as CCMS and C-SCMS use explicit certificates by default, which results in higher efficiency in verifying secure packets compared to SCMS.

  5. Improved AI systems can predict performance bottlenecks during signature verification by accounting for certificate type differences, noting that SCMS uses implicit certificates by default, which only include the reconstruction value, requiring a subsequent step involving the ACA public key and leading to longer computation times.

Related papers