HNZ Protocol stack configuration
The HNZ protocol stack configuration specifies communication parameters and is a collection of entries containing information about OSI Transport and OSI Application layers objects.
Each entry is comprised of attributes that describe the object. All the configuration data are structured using JSON.
Each entry shall be mapped with the corresponding configuration function in the chosen implementation protocol library.
Attributes definition
| Attribute | Description | Expected values | Mandatory |
|---|---|---|---|
| name | this identifies the protocol stack | iec104client, iec104server, tase2client, tase2server, 61850client, 61850server, etc... | Yes |
| version | version number of the configuration file | 2 digits x.y => x = major change, y = minor change | Yes |
| connections | array of connections | Yes | |
| connections.srv_ip | IP address to remote IEC 104 server | IP address | Yes |
| connections.port | port number to remote IEC 104 server | default = 6001 | No |
| remote_station_addr | remote server station address | 6 bits | Yes |
| local_station_addr | local server station address | 6 bits | Yes |
| remote_addr_in_local_addr | remote address in local address | 0, 1 or 2 | Yes |
| Inacc_timeout | timeout before declaring the remote server unreachable | default = 180 (seconds) | No |
| Max_sarm | max number of SARM messages | default = 30 | No |
| To_socket | |||
| Repeat_path_A | max number of authorized repeats for path A | default = 3 | No |
| Repeat_path_B | max number of authorized repeats for path B | default = 3 | No |
| Repeat_timeout | default = 3000 | No | |
| Anticipation | max number of messages send without ACK | default = 3 | |
| Default_msg_period | |||
| Test_msg_send | Test message in sending direction | Yes | |
| Test_msg_receive | Test message in receiving direction | Yes |
Configuration JSON structure
{
"protocol_stack":{
"name":"iec104client",
"version":"1.0",
"transport_layer":{
"redundancy_groups":[
{
"connections":[
{
"srv_ip":"192.168.0.10",
"port":2404,
"conn":true,
"start":true
},
{
"srv_ip":"192.168.0.11",
"port":2404,
"conn":true,
"start":false
}
],
"rg_name":"red-group-1",
"tls":false,
"k_value":12,
"w_value":8,
"t0_timeout":10,
"t1_timeout":15,
"t2_timeout":10,
"t3_timeout":20
},
{
"connections":[
{
"srv_ip":"192.168.0.12",
"port":2404,
"conn":false,
"start":false
},
{
"srv_ip":"192.168.0.13",
"port":2404,
"conn":false,
"start":false
}
],
"rg_name":"red-group-2",
"tls":false,
"k_value":12,
"w_value":8,
"t0_timeout":10,
"t1_timeout":15,
"t2_timeout":10,
"t3_timeout":20
}
]
},
"application_layer":{
"orig_addr":0,
"ca_asdu_size":2,
"ioaddr_size":3,
"startup_time":180,
"asdu_size":0,
"gi_time":60,
"gi_cycle":false,
"gi_all_ca":false,
"gi_repeat_count":2,
"disc_qual":"NT",
"send_iv_time":0,
"tsiv":"REMOVE",
"utc_time":false,
"comm_wttag":false,
"comm_parallel":0,
"exec_cycl_test":false,
"startup_state":true,
"reverse":false,
"time_sync":false
}
}
}
HNZ datapoint representation
This is the Datapoint representation of an HNZ message.
{
"data_object":{
"do_type":"M_SP_TB_1",
"do_ca":18325,
"do_oa":0,
"do_cot":3,
"do_test":false,
"do_negative":false,
"do_ioa":6468178,
"do_value":1,
"do_quality_iv":true,
"do_quality_bl":false,
"do_quality_ov":false,
"do_quality_sb":false,
"do_quality_nt":false,
"do_ts":1653484330239,
"do_ts_iv":true,
"do_ts_su":false,
"do_ts_sub":false
}
}
Path exploration
In redundant network configuration or generally in cases where several communication paths exist between one client and one server, the path checking exploration mechanism allows the client to try all the paths one by one without making any difference between them. The client uses the first available path. On disconnection this procedure starts again from the beginning.