Direct Answer

A VPP integration requires Chinese national cryptographic algorithms SM2/SM4 — what exactly do they encrypt, and how do they differ from TLS? SM2 is an asymmetric algorithm that handles identity authentication and signatures (replacing RSA); SM4 is a symmetric algorithm that encrypts business data (replacing AES); uplink energy data carries a national-crypto tunnel on top of MQTT/TLS to deliver tamper-proof commands and confidential data — the bottom line of VPP dispatch-command security. The landing is SM2 authenticates identity, SM4 protects confidentiality and the tunnel stacks over TLS.

A scenario: A VPP project is asked to do "national-crypto retrofit" during integration — the customer asks: havent we already used TLS? — the answer: TLS is generic transport encryption, while national crypto is the commercial-cryptography compliance requirement — SM2 signatures plus SM4 encryption on top of MQTT/TLS — tamper-proof commands, confidential data — the retrofit passes the crypto review. The logic of national crypto is stacking, not replacing TLS — SM2 decides who sends the command, SM4 decides the data stays private.

1. What SM2 and SM4 Are: Two National-Crypto Keys

What SM2 is — an asymmetric algorithm: public-key encryption and private-key signing, replacing RSA; What SM4 is — a symmetric algorithm: one key encrypts and decrypts, replacing AES; The division of the two keys — SM2 authenticates identity: signing and key exchange; SM4 protects confidentiality — business data: uplink data encrypted with SM4; The basis of national crypto — GB/T 39786: basic requirements for information-system cryptography application.

In one sentence: SM2 handles identity and SM4 handles data — two keys, one job each.

An example: A platform self-checks for the crypto review: SM2 for gateway identity authentication and SM4 for data encryption — algorithms compliant — the review passes. The logic is that national crypto is a combination — signing with SM2 and encrypting with SM4, each doing its own job.

2. What SM2 Handles: Identity Authentication and Signing

SM2's duty — identity authentication: confirming who sends the command; SM2's signature — tamper-proof: commands carry a signature, tampering invalidates it; SM2's key exchange — session negotiation: endpoints negotiate a session key; SM2's replacement — RSA: RSA scenarios switch to SM2; SM2's landing point — device identity: the gateway and platform authenticate each other.

In one sentence: SM2 is identity authentication plus signing — commands with signatures fail when tampered.

An example: A gateway and platform: SM2 mutual authentication — the platform confirms this is that gateway — commands carry SM2 signatures — forgery fails. The logic is that SM2 handles trust — without identity authentication, an attacker can impersonate a device and send commands — SM2 signatures make commands verifiable.

3. What SM4 Handles: Data Encryption and Anti-Eavesdropping

SM4's duty — data confidentiality: uplink data transmitted encrypted; SM4's scope — business data: consumption, commands and status all encrypted; SM4's replacement — AES: AES scenarios switch to SM4; SM4's speed — symmetric encryption: faster than asymmetric, suited to bulk data; SM4's landing point — the data tunnel: business data encrypted inside the tunnel.

In one sentence: SM4 is data encryption — consumption, commands and status unreadable in transit.

An example: Uplink data in a project: uploaded encrypted with SM4 — packet capture shows no plaintext — data protected from eavesdropping. The logic is that SM4 handles secrecy — data intercepted in transit is unreadable without the key.

4. The Relationship with TLS: Stacking, Not Replacing

What TLS handles — transport encryption: generic transport-layer security; What national crypto handles — crypto compliance: commercial-cryptography application requirements; The relationship — stacking: a national-crypto tunnel on top of TLS; Why stack — compliance: the crypto review requires national algorithms to land; The form of stacking — a tunnel: the national-crypto tunnel wraps over MQTT/TLS.

In one sentence: TLS is generic encryption and national crypto is a compliance requirement — stacking, not replacing.

An example: A platform retrofit: MQTT/TLS transport kept — an SM2-signature and SM4-encryption tunnel added — the crypto review passes. The logic is that national crypto does not replace TLS — it adds a compliance layer — TLS keeps transport and national crypto keeps compliance, both retained.

5. Why VPP Platforms Mandate It: The Bottom Line of Dispatch Commands

The VPP scenario — remote dispatch: the platform sends power commands to resources; The command risk — forgery and tampering: a tampered command can misdispatch resources; The data risk — eavesdropping: consumption and status data leak commercial information; The value of national crypto — tamper-proof plus confidential: commands cannot be forged and data cannot be read; Why mandatory — dispatch security: dispatch-command security is the VPP bottom line.

In one sentence: VPP mandates national crypto for tamper-proof commands and confidential data — the bottom line of dispatch security.

An example: A VPP platform's integration requirement: SM2 authentication on the gateway and SM4-encrypted commands — no national crypto, no access — compliant, then integrated. The logic is that dispatch commands are orders — tampered orders have serious consequences — national crypto makes commands verifiable and confidential, so VPP dares to dispatch remotely.

6. Where the National-Crypto Module Sits on the Gateway

The module's position — the edge gateway: national-crypto capability implemented gateway-side; The module's composition — a crypto chip or soft core: SM2/SM4 implementation; The module's counterpart — platform-side: the platform carries national-crypto certificates and keys; The module's startup — handshake: the gateway and platform perform a national-crypto handshake; The module's upkeep — key management: certificates and keys renewed on schedule.

In one sentence: the national-crypto module sits gateway-side — a chip or soft core implements SM2/SM4 and handshakes with the platform.

An example: A project's ESX gateway: a built-in national-crypto module — national-crypto handshake with FEXCloud — uplink data encrypted with SM4. The logic is that national crypto must land on the device — with crypto capability on both ends, the tunnel can be built.

7. The Crypto Review: A Cryptography Gate Above Classified Protection

What the review is — a cryptography-application security assessment: commercial-crypto compliance testing; The review's basis — GB/T 39786: basic requirements for information-system cryptography application; The review and classified protection — dual requirements: classified protection covers overall security, the review covers cryptography; The review's objects — cryptography application: algorithms, key management and security mechanisms; The review's conclusion — compliance grade: basically compliant or noncompliant.

In one sentence: the crypto review is a cryptography-application assessment — under GB/T 39786, a crypto gate above classified protection.

An example: A platform passes classified protection and then the crypto review: SM2/SM4 landed and key management standardized — basically compliant. The logic is that classified protection asks whether security exists and the review asks whether cryptography is compliant — both gates must pass for the retrofit to matter.

8. What a National-Crypto Retrofit Changes

Change one, algorithm replacement — RSA to SM2 and AES to SM4: algorithms localized; Change two, the certificate system — national certificates: the SM2 certificate and key system; Change three, transport stacking — the national tunnel: a national layer above TLS; Change four, key management — the full lifecycle: generation, distribution, renewal and destruction; Change five, review preparation — materials and testing: cooperating with the review body.

In one sentence: the retrofit is algorithm replacement, certificates, tunnel stacking, key management and the review.

An example: A platform's national-crypto retrofit: algorithm replacement, the certificate system and tunnel stacking completed in three months — the review passes. The logic is that the retrofit is a system project — replacing the algorithm is only the first step; every item in place makes it complete.

9. A Common Misconception: Treating National Crypto as an SSL Replacement

Misconception one, national crypto equals SSL — no: TLS handles transport, national crypto handles compliance; Misconception two, replace only the algorithm — not enough: the certificate system and key management must change too; Misconception three, the gateway does not matter — no: the module must land device-side; Misconception four, done once — no: keys are renewed and managed continuously; The consequence of the misconceptions — the review fails: any missing item means noncompliant.

In one sentence: national crypto is not a name change of the algorithm — it is a system retrofit; one missing link fails the review.

An example: A platform replaces only the algorithm without building the certificate system — the review finds key management missing — remediated and completed — passes. The logic is that the misconception comes from looking at the algorithm alone — certificates, keys and management are all review points.

10. Back to YESLON: The ESX Gateway's National-Crypto Support

Where the ESX gateway sits — the edge node: national-crypto capability implemented gateway-side; Support for SM2 — device identity: the gateway's SM2 certificate and mutual authentication; Support for SM4 — data encryption: uplink data encrypted with SM4; Support for the tunnel — the national tunnel: a national-crypto channel with FEXCloud; Support for compliance — review cooperation: key management and review materials ready.

In one sentence: the ESX gateway is SM2 identity, SM4 data and the tunnel to the platform — the device landing point of the retrofit.

An example: A VPP project: the ESX gateway's national module plus the FEXCloud handshake — the review passes — access compliant. The logic is that national crypto must land on both ends — the gateway has the module and the platform has the certificates — both ends connected, the tunnel is complete.

11. Self-Check: Five Questions on National Crypto

Question one, are the algorithms compliant — SM2/SM4: have RSA/AES been replaced on the ground; Question two, are the certificates built — national certificates: is the SM2 certificate system established; Question three, is the tunnel stacked — the national tunnel: is the national layer added above TLS; Question four, are the keys managed — key management: is the full lifecycle standardized; Question five, has the review passed — review compliance: assessed under GB/T 39786.

In one sentence: the five questions are algorithms compliant, certificates built, tunnel stacked, keys managed and review passed — all five pass, national crypto lands.

A self-check example: A platform self-checks before access: SM2/SM4 landed (algorithms), the certificate system built (certificates), the tunnel completed (tunnel), keys renewed periodically (keys) and the review passed (review) — all five pass — VPP access compliant. The logic of national crypto in uplink energy data is SM2 authenticates identity, SM4 protects confidentiality and the tunnel delivers compliance — the algorithm replaced, certificates built, keys managed and the review passed — national crypto landing is not a name change but identity, confidentiality and compliance all in place.

Scope and Limitations

  • The conclusions in this article are intended for LV distribution and electrical-safety sites. Standard numbers (GB/T 39786) refer to their currently effective editions, and product parameters follow the latest FEXLINK selection handbook and product knowledge base.
  • Quantitative criteria (protection zone, discharge and residual voltage, earth resistance, thresholds and grading) hold under the preconditions stated in this article. Where the site voltage level, earthing arrangement, environmental category or load profile differs, the figures must be recalculated. Specific configurations involving ESX intelligent edge computing gateway should be verified against actual circuit parameters.
  • Specific product models and parameters are subject to the latest selection handbook and product knowledge base; this article does not constitute selection or procurement advice.
  • Standard numbers cited here refer to the currently effective editions; when a standard is revised, the related quantitative conclusions must be re-checked.
  • Deployment and implementation for specific projects must be carried out by qualified engineers based on site survey and design drawings.

Frequently Asked Questions

What SM2/SM4 Actually Protects in Uplink Energy Data

A VPP integration requires Chinese national cryptographic algorithms SM2/SM4 — what exactly do they encrypt, and how do they differ from TLS