CoAP,DTLS Java 实现.zip

 # Californium (Cf) - Cloud CoAP-S3-Proxy Server ## SCADA (supervisory control and data acquisition) ## - Reliable - Efficient - Encrypted -  Cloud CoAP-S3-Proxy Server for device communication with CoAP/DTLS 1.2 CID. Based on the [Eclipse/Californium CoAP/DTLS 1.2 CID java library](https://github.com/eclipse-californium/californium). Fill the missing link between the device and cloud. The server supports DTLS 1.2 CID with **P**re**S**hared**K**ey (similar to username/password) and **R**aw**P**ublic**Key** (a public key as certificate without additional information like subject or validity) authentication for device communication. X509 certificate based device authentication may be added to the cloud demo server in the future. Californium (Cf) itself does already support it. The sent data is forwarded with the proxy function to a **S**imple**S**torage**S**ervice (**S3**) to persist it. Your backend may either fetch the data from that S3 or you may use a included simple Web-Browser javascript **S**ingle**P**age**A**pplication to display the data and to visualize that in simple charts. Example message sent by device: ``` 22-03:02:30 [d-hh:mm:ss], nRF9160 feather/scale v0.9.0+0, 0*1061, 1*0, 2*0, 3*1, failures 0 NCS: 2.5.1, HW: B1A, MFW: 1.3.5, IMEI: 350457799486418 !3836 mV 56% (104 days left) Last code: 2024-01-30T19:59:07Z update Restart: Power-On ICCID: ?????280666074879390, eDRX cycle: off, HPPLMN 26201 interval: 2 [h] IMSI: ?????5107487939 Network: CAT-M1,roaming,Band 20,PLMN 26201,TAC 26553,Cell 30157572,EARFCN 6400 PDN: ???.???,???.???.???.??? PSM: TAU 86400 [s], Act 0 [s], no RAI, Released: 10823 ms !CE: down: 8, up: 1, RSRP: -93 dBm, CINR: 5 dB, SNR: 6 dB Stat: tx 1032 kB, rx 72 kB, max 1003 B, avg 529 B Cell updates 162, Network searchs 1 (1 s), PSM delays 0 (0 s) Modem Restarts 0, Sockets 1, DTLS handshakes 1 Wakeups 1062, 428 s, connected 12371 s, asleep 72 s Last calibration: A 2024-02-28T20:10:11Z, B 2024-02-28T20:19:55Z !CHA 37.20 kg, 31.1°C, CHB 34.55 kg, 31.9°C !26 C ``` **Note:** the previous implementation uses the lines starting with an `!` for a accumulated data file named "series-date-time". That has changed and the current version accumulates the complete data into a "arch-date" file obsoleting the leading `!`. Use "`https://<hostname>/v2`" to use the web UI with the archive files. Web-Browser application login page:  Web-Browser application device list page:  Web-Browser application chart page:  Web-Browser application device status page (data from device):  Web-Browser application device configuration page (data to device):  Web-Browser application server diagnose page:  Some more details about the web-UI can be found in [web-UI documentation](./docs/web-ui.md). ## Performance and Resources [<img src="./docs/quadrant.svg" width="65%" />](./docs/quadrant.svg) - The footprint of the OS and Java VM, around 800 MB RAM, requires to use at least 2 GB RAM. - The maximum number of devices depends mainly on the available RAM. Per PSK around 3K per device, for certificate based devices 5K per device. - The maximum number of requests per second also depends on the available RAM and CPU for processing. Usually the backend slows down the processing a lot. Without backend, a 4x3GHz System with 16 GB RAM runs 50000 requests/s. With backends, that’s usually much less. - If S3 is used as backend, usually the write preformance of S3 limits then the number of requests/s. 300 requests/s up to 3000 requests/s could be found. - The Javascript Web App is considered only for first steps, Therefore it may handle 100-200 device, it’s not expected to be used with more. ## General Usage Cloud CoAP-S3-Proxy Server is available at the eclipse repository and can be downloaded [cf-s3-proxy-server-3.13.0.jar](https://repo.eclipse.org/content/repositories/californium-releases/org/eclipse/californium/cf-s3-proxy-server/3.13.0/cf-s3-proxy-server-3.13.0.jar). Start the cf-s3-proxy-server with: ``` java -jar cf-s3-proxy-server-4.0.0-SNAPSHOT.jar -h Usage: S3ProxyServer [-h] [--diagnose] [--[no-]coap] [--wildcard-interface | [[--[no-]loopback] [--[no-]external] [--[no-]ipv4] [--[no-] ipv6] [--interfaces-pattern=<interfacePatterns>[, <interfacePatterns>...]]...]] [--coaps-credentials=<credentials> [--coaps-password64=<password64>]] [--device-file=<file> [--device-file-password64=<password64>]] [--store-file=<file> --store-max-age=<maxAge> [--store-password64=<password64>]] [--provisioning [--replace]] ([--domain-file=<file> [--domain-file-password64=<password64>]] | [[[--s3-endpoint=<endpoint>] [--s3-region=<region>] [--s3-bucket=<bucket>] [--s3-acl=<acl>] [--s3-concurrency=<concurrency>] [--s3-external-endpoint=<externalEndpoint>] [--s3-redirect] (--s3-config=<s3ConfigFile> | [--s3-access-key=<accessKey> --s3-secret=<secret>])] [--user-file=<file> [--user-file-password64=<password64>]] [--config-file=<file> [--config-file-password64=<password64>]] [--http-forward=<httpForward> [--http-authentication=<httpAuthentication>] [--http-device-identity-mode=<httpDeviceIdentityMode>]]]) [[--https-port=<port>] --https-credentials=<credentials> [--https-password64=<password64>] [--spa-script=<singlePageApplicationScript>] [--spa-css=<singlePageApplicationCss>] [--spa-reload] [--spa-s3] [--spa-script-v2=<singlePageApplicationScriptV2>]] --coaps-credentials=<credentials> Folder containing coaps credentials in 'privkey. pem' and 'pubkey.pem' --coaps-password64=<password64> Password for device store. Base 64 encoded. --config-file=<file> Filename of configs-store. --config-file-password64=<password64> Password for configs-store. Base 64 encoded. --device-file=<file> Filename of device store for coap. --device-file-password64=<password64> Password for device store. Base 64 encoded. --diagnose enable 'diagnose'-resource. --domain-file=<file> Filename of domain-store. --domain-file-password64=<password64> Password for domain-store. Base 64 encoded. -h, --help display a help message --http-authentication=<httpAuthentication> Http authentication for forward device data (coap-requests). Supports 'Bearer <access-token>', 'PreBasic <username:password' and '<username:password>' --http-device-identity-mode=<httpDeviceIdentityMode> Http device identity mode for forwarding device data (coap-requests) . Supported values: NONE, HEADLINE and QUERY_PARAMETER. Default: NONE --http-forward=<httpForward> Http destination to forward device data (coap-requests). --https-credentials=<credentials>