Taurnet 1.0 Multipath Bonding API

Overview

Use this service when you need to bond multiple network paths under a single session, apply hybrid quantum/classical security, and audit path-selection decisions for maritime, remote, and enterprise connectivity workloads.

• Session bonding with configurable user_id sandbox
• Live bonding status and laboratory telemetry snapshots
• Bell-state path optimisation for multipath selection
• BB84 QKD key-generation workflow for session protection
• Same-origin proxy at /api/taurnet

Four-plane architecture

The Quantum Multipath Bonding programme separates concerns across data, control, security, and intelligence planes. See the research page for figures and the Zenodo engineering report by Muskan Sharma.

Same-origin proxy

Browser clients call /api/taurnet/<path> on www.data-t.uk. Next.js forwards JSON to TAURNET_BACKEND_URL (default laboratory host). Static JSON fallbacks in public/investor-relations/research/multiple-path-bonding/media/ support demos when the backend is unreachable.

Check health

GET /api/taurnet/health

Returns service readiness for the bonding laboratory backend.

Start bonding session

GET  /api/taurnet/api/bonding/status
POST /api/taurnet/api/bonding/start?user_id=1

Query current bonding state, then start a session for the sandbox user. The Taurnet 1.0 console wraps these calls in the operator dashboard.

Optimise paths

POST /api/taurnet/api/quantum/optimize
Content-Type: application/json

{ "paths": [...], "constraints": {...} }

Bell-state path recommendation for bonded interfaces. Payload shape matches the CDNER-X laboratory API.

Generate QKD keys

POST /api/taurnet/api/qkd/generate
Content-Type: application/json

{ "session_id": "...", "bits": 256 }

BB84 sifting workflow for hybrid session protection alongside classical PQC fallbacks.

API endpoints

Errors

When the laboratory backend is unreachable, the proxy returns 502 with a JSON error message. The console may load static media JSON from the public folder for offline demonstration.