Codium

• opener — Project Layout
  • opener — Project Layout
    • Monorepo rationale
    • 1. Repository Root
    • 2. Zephyr Module Manifest
    • 3. include/ — Public Headers
      • 3.1 Portability of Shared RPC Headers
    • 4. subsys/opener/ — DECT NR Stack (Zephyr)
    • 5. lib/opener_rpc/ — RPC Transport Library (Zephyr Server Side)
    • 6. drivers/spi_rpc_slave/ — SPI Slave Transport Driver (Zephyr)
    • 7. boards/ and dts/ — Board Support
    • 8. samples/ — Sample Applications
    • 9. linux/ — Linux Host Side
      • 9.1 DKMS Configuration
      • 9.2 Kernel Module Makefile
      • 9.3 Adding a New Module Proxy (Host Side)
    • 10. Source Cross-Reference
    • 11. Open Questions
• opener — SPI RPC Transport: Design and Implementation
  • 1. Introduction
  • 2. Architecture Overview
  • 3. Shared Definitions
    • 3.1 Scheduler API (opener_scheduler.h)
    • 3.2 RPC Wire Protocol Constants (opener_rpc.h)
  • 4. Wire Protocol
    • 4.1 Transfer model
    • 4.2 Synchronous call flow (host → device)
    • 4.3 Asynchronous event flow (device → host)
    • 4.4 Sequence numbers
    • 4.5 CRC
  • 5. Device-Side Implementation (Zephyr)
    • 5.1 Directory layout
    • 5.2 RPC server core (opener_rpc_server.c)
    • 5.3 Scheduler RPC handler (opener_rpc_scheduler.c)
  • 6. Host-Side Implementation (Linux Kernel Module)
    • 6.1 Directory layout
    • 6.2 Private data structure (opener_priv.h)
    • 6.3 SPI driver and IRQ (opener_main.c)
    • 6.4 RPC frame I/O (opener_rpc.c)
    • 6.5 Network device (opener_netdev.c)
    • 6.6 Generic Netlink UAPI (opener_netlink.c)
    • 6.7 Scheduler proxy — kernel (opener_scheduler.c)
  • 7. Usage
    • 7.1 Network interface (standard kernel networking)
    • 7.2 Management via Generic Netlink
  • 8. Extending to Other Modules
  • 9. TUN/TAP Alternative (Investigation Note)
    • 9.1 TUN device — IPv6 profile (layer 3)
    • 9.2 TAP device — Ethernet-over-DECT profile (layer 2)
    • 9.3 Comparison
• opener — Use-Case Requirements
  • Purpose
  • Requirement notation
  • 1. Smart City — Street Infrastructure
    • 1.1 Scenario description
    • 1.2 Deployment topology
    • 1.3 Traffic profiles
    • 1.4 DECT-2020 NR features exercised
    • 1.5 Requirements
  • 2. Concert Audio Distribution — Wireless In-Ear Monitoring and Stage Management
    • 2.1 Scenario description
    • 2.2 Deployment topology
    • 2.3 Traffic profiles
    • 2.4 DECT-2020 NR features exercised
    • 2.5 Requirements
  • 3. OTA Firmware Update
    • 3.1 Scenario description
    • 3.2 Deployment topology
    • 3.3 Traffic profile
    • 3.4 DECT-2020 NR features exercised
    • 3.5 Requirements
  • 4. Stack Feature Requirements Summary
  • 5. Open Questions Derived from Use Cases
• opener — DECT-2020 NR Implementation Requirements
  • Overview
    • Dual-role FT+PT support
    • Device-only and device+host deployment models
    • SPI-based RPC transport
    • Pluggable radio scheduler with policy system
    • Modular architecture with well-defined interfaces
    • Coding standards
  • Requirement notation
  • 1. System-Level Requirements (SYS)
    • 1.1 General
    • 1.4 Deployment Models
    • 1.2 Memory and Performance
    • 1.3 Compliance and Testing
  • 2. Platform and HAL Requirements (PLT)
  • 3. SPI-based RPC Transport Requirements (RPC)
    • 3.1 Purpose and Scope
    • 3.2 Protocol
    • 3.3 Serialization
  • 4. MAC Layer Requirements (MAC)
    • 4.1 General Architecture
    • 4.2 Radio Scheduler (MAC-SCH)
    • 4.3 Spectrum Manager (MAC-SPM)
    • 4.4 Association Manager (MAC-ASC)
    • 4.5 Beacon and Broadcast Manager (MAC-BCN)
    • 4.6 HARQ Engine (MAC-HRQ)
    • 4.7 Random Access Controller (MAC-RAC)
    • 4.8 Connection Configuration Controller (MAC-CCC)
    • 4.9 MAC Security Engine (MAC-SEC)
    • 4.10 Mobility Manager (MAC-MOB)
    • 4.11 Paging Controller (MAC-PAG)
    • 4.12 MAC Multiplexer/Demultiplexer (MAC-MUX)
    • 4.13 MAC Public API (MAC-API)
  • 5. DLC Layer Requirements (DLC)
  • 6. Convergence Layer Requirements (CVG)
  • 7. Coding Standard Conventions (CODE)
  • 8. Module Interface Conventions (CONV)
  • 9. Open Questions