- Depending on the underlying transport specifics and selected operation mode, NeoBand latency can vary between 50 – 70ns wire-to-wire on one device. If needed, the system may be optimized for specific use cases.
Uninterrupted delivery of customer packets.
- No packet slicing. Allocated bandwidth limits are maintained through time slot management. NeoBand imposes dynamically calculated delays after packet transmission to ensure the customer cannot send more data while their bandwidth limitation is in effect. The flexible delay algorithm allows customers to send a packet of any size as long as it does not exceed the maximum packet size allowed for the port.
No fixed bandwidth slots
- NeoBand provides high granularity in assignable bandwidth slot sizes.
Idle-time bandwidth increase
- NeoBand allows setting per-port schemas for bandwidth increase during idle time.
Short Ethernet Packet Support
- NeoBand allows sending packets shorter than 64 bytes. Minimum packet size is 16 bytes.
- Each customer port is visible to the administrator as a fully functional 10G Ethernet port. All standard Linux troubleshooting tools can be used per port: ping, tcpdump, etc.
10G and 1G Radio/Exchange Interface
- 40G support is coming soon
The timestamping support includes:
- Capability (optional) to timestamp all traffic passing through the device and output to one or more ports
- Ability to separate incoming (customer) traffic and multiplexed radio/exchange traffic into separate timestamp channels for better visibility
- Timestamp accuracy of 2.5ns with ultra-low jitter
NeoBand: Wireless Provider Edition
In the wireless provider setup, LDA NeoBand devices are connected via radio wireless link. Data goes through FPGA in both directions: muxing on the way to the radio and de-muxing on the way back.
FPGA adds 50 – 70ns latency one-way (depending on radio protocol handling) and protects against traffic bleeding.
NeoBand: Prop Trading Edition
In the prop trading setup, LDA NeoBand devices connect either directly to the radio or via wireless provider gateway.
Client data on the way out to the radio is muxed by FPGA: 50 – 70ns latency depending on radio protocol handling.
Prop shop installations do not usually need traffic bleeding protection, so the traffic that is coming from the wireless link can be distributed to clients through Layer 1 with latency under 3ns. If traffic bleeding prevention is needed, the data can be sent through FPGA in this direction as well.
NeoBand: Hosting Provider Edition
Hosting service providers can connect NeoBand to the exchange with two handoffs. Each client also gets two handoffs: for market data and order routing. Market data comes via Layer 1 with 3ns latency. Orders on the way out are muxed by FPGA with 45ns latency.
Another option for order placement is to use Layer 3 routing (MAC rewrite): with some latency penalty.