Skip to content

GitLab

Last edited by Mark Stevens
Page history

qbert implementation

Hardware:

  • RK3288 level board
  • 4Gb RAM (game server, background processing)

  • 128Gb eMMC ( content servicing )

  • Ethernet
  • Wifi 2.4Ghz / 5Ghz multi (mesh comm/provisioning/positioning)
  • HDMI out
  • HDMI in ? (future ad embed/signage)
  • internal display (development)
  • NFC (provisioning)
  • Bluetooth/BLE (provisioning/positioning)
  • compass/magnetometer (positioning/loss prevention)
  • cpu/board temperature sensors (device health monitoring)

Core Capabilities

  • persistent connection (ICC) to backend/cust support
  • manifest acquisition
  • content cache (tablet & qbert)
  • ad management
  • game scheduling
  • apk cache (tablet & qbert)
  • DB / analytics logging & sync
  • Hive commands & management
  • Diagnostics
  • WAP configuration & management
  • downstream Qbert distribution, configuration, mgmt, reporting,
  • HTTP dashboard/ with reverse websocket connection (UI design and develop tbd)

Connecting implementation:

  • ICC backend replacement
  • Game Schedule delivery
  • AD Content delivery
  • Build CI for QBert (fw & sw)
  • Scheduled Build Deployment system
  • Broadcast Director replacement
  • Support Diagnostics