AI & ML
AE-DISC: Automorphism Ensemble Direct-Invocation Successive Cancellation for Low-Latency Decoding
arXiv eess.SP0 views
arXiv:2611.25262v1 Announce Type: new Abstract: Emerging applications in hyper-reliable low-latency communication (HRLLC) demand channel decoders that deliver deterministic performance under stringent latency and reliability constraints. While Polar codes are well suited for this scenario due to their strong error-correction capability, conventional successive cancellation (SC) decoding exhibits inherent serial dependencies that lead to high decoding latency. This paper presents the automorphism ensemble direct-invocation successive cancellation (AE-DISC) decoder, a low-latency framework that enables the concurrent computation of the left and right decoding subtrees in the SC process, yielding substantial speed-ups. By exploiting permutation automorphisms, AE-DISC decoding further improves error-correction performance. Simulation results demonstrate that AE-DISC attains up to 1.4 dB gain over the 5G SC baseline and surpasses layered min-sum (LMS) low-density parity-check (LDPC) decoders at a frame error rate (FER) of $10^{-6}$, while maintaining fixed algorithmic complexity. Both theoretical analysis and application-specific integrated circuit (ASIC) synthesis results further show up to 2 times decoding speed-up relative to fast simplified successive cancellation (FSSC).
Source:https://arxiv.org/abs/2611.25262PreviousAdaptive Filtering With Reduced Computational Complexity Using SOPOT ArithmeticNextConditional-Hierarchical Open-Set Deep Learning for Robust Radio Signals Intelligence
Related posts
Reading project health off a download page — faster than star count
0dev.to
Best time trackers for developers, for code and for AI
0dev.to

Serving Qwen3.5-0.8B with a 0.016% weight edit: measure the loops, pin the sampling on the server
0dev.to
Design Tokens for AI: Extract a Website's Real Colours, Fonts, Shadows and Icons So an LLM Builds On Brand
0dev.to
Trying to get our Arms around AI efficiency
0Stack Overflow Blog
Why an Embedded Game Fails on Some Phones, and How to Debug It
0dev.to