8.3 Charge Point Network Profiles
Each network profile entry defines a complete connection profile, including:
- OCPP URL
- Security profile
- Certificate paths
- Timeout settings
- Network interface
- VPN configuration
- APN configuration
Multiple profiles can be configured for different environments:
- Slot 0: Production CSMS
- Slot 1: Plugfest or test environment
- Slot 2: OCTT cloud
- Slot 3: Backup CSMS
The following example shows configurationSlot 0:
{
"configurationSlot": 0,
"connectionData": {
"ocppVersion": "OCPP20",
"ocppTransport": "JSON",
"ocppCsmsUrl": "ws://497877863b54bfd9.octt.openchargealliance.org:16968/MCHP00002",
"messageTimeout": 30,
"securityProfile": 0,
"ocppInterface": "Wired0",
"vpn": { ... },
"apn": { ... }
},
"caFile": "/path/.../cert.pem",
"clientCertFile": "/path/.../client.pem",
"clientKeyFile": "/path/.../private.key"
}
| Field | Description |
|---|---|
configurationSlot | Unique index used to select the connection profile |
ocppVersion | OCPP protocol version |
ocppTransport | Transport encoding for OCPP messages, such as JSON over WebSocket |
ocppCsmsUrl |
The full WebSocket endpoint. It must include the charge point ID, which must match the value configured in OCTT. Unencrypted WebSocket:
TLS-encrypted WebSocket:
|
messageTimeout | Timeout, in seconds, for request-response pairs |
securityProfile |
|
ocppInterface | Network interface to use, such as
Wired0 or Wireless0 |
vpn | Optional VPN settings, including the server, authentication, and tunnel type |
apn | Optional APN and cellular-modem settings |
caFile | Root CA certificate used to validate the CSMS certificate during the TLS handshake |
clientCertFile | Client certificate required for Security Profile 3 |
clientKeyFile | Private key associated with the client certificate |
