![]() |
User Manual, Developers Guide and API Documentation |
![]() |
#include <WNS/scheduler/harq/HARQInterface.hpp>#include <WNS/service/phy/power/PowerMeasurement.hpp>#include <WNS/ldk/harq/softcombining/Container.hpp>#include <WNS/distribution/Uniform.hpp>#include <WNS/probe/bus/ContextCollector.hpp>#include <WNS/logger/Logger.hpp>#include <WNS/container/Registry.hpp>#include <WNS/Cloneable.hpp>

Go to the source code of this file.
Namespaces | |
| namespace | wns |
| namespace | wns::scheduler |
| namespace | wns::scheduler::harq |
Classes | |
| class | wns::scheduler::harq::ChaseCombiningDecoder |
| ChaseCombining: ... More... | |
| class | wns::scheduler::harq::HARQ |
| HARQ is the instance collaborating with the scheduler. Contains a collection of HARQEntity's inside; one for each peer. More... | |
| class | wns::scheduler::harq::HARQEntity |
| There is one HARQEntity per user (link) in BS. UTs only have one. More... | |
| class | wns::scheduler::harq::HARQReceiverProcess |
| Receiving side of the HARQ protocol. Take resource block and try to decode. prepare ACK/NACK depending on result. More... | |
| class | wns::scheduler::harq::HARQReceiverProcess::Feedback |
| class | wns::scheduler::harq::HARQSenderProcess |
| Sending side of the HARQ protocol. There is one process per resource block in transit. Receives ACK/NACK by callbacks currently. More... | |
| class | wns::scheduler::harq::IDecoder |
| class | wns::scheduler::harq::SchedulingTimeSlotInfo |
| class | wns::scheduler::harq::UniformRandomDecoder |
| Very simple decoder without utilizing SINR measurements. Just for basic tests. More... | |
Typedefs | |
| typedef wns::ldk::harq::softcombining::Container < SchedulingTimeSlotInfo > | wns::scheduler::harq::SoftCombiningContainer |
Functions | |
| wns::scheduler::harq::STATIC_FACTORY_DEFINE (IDecoder, wns::PyConfigViewCreator) | |
1.5.5