![]() |
User Manual, Developers Guide and API Documentation |
![]() |
#include <LTE/helper/HasModeName.hpp>#include <DLL/services/control/Association.hpp>#include <WNS/ldk/ManagementServiceInterface.hpp>#include <WNS/ldk/fun/FUN.hpp>#include <WNS/pyconfig/View.hpp>#include <WNS/pyconfig/Sequence.hpp>#include <WNS/events/PeriodicTimeout.hpp>#include <WNS/events/EventFactory.hpp>#include <WNS/logger/Logger.hpp>#include <WNS/Enum.hpp>#include <WNS/container/Registry.hpp>#include <WNS/service/dll/Address.hpp>#include <vector>#include <cstdlib>

Go to the source code of this file.
Namespaces | |
| namespace | lte |
| namespace | lte::controlplane |
| namespace | lte::controlplane::associationHandler |
| namespace | lte::timing |
| namespace | lte::timing::events |
Classes | |
| class | lte::timing::FrameStartNotificationInterface |
| class | lte::timing::SuperFrameStartNotificationInterface |
| class | lte::timing::TimingScheduler |
| The TimingScheduler takes care of the superframe timing by keeping a list of phases, for each of which an event is generated. The superframe start is notified periodically by a discrete event. More... | |
| struct | lte::timing::TimingScheduler::Friends |
| friends are rlc, macg, phyUser. We need direct access to them More... | |
| struct | lte::timing::TimingScheduler::StationTaskPhase |
| struct | lte::timing::TimingScheduler::TimingEvent |
| for event scheduling More... | |
Typedefs | |
| typedef int | lte::timing::DuplexScheme |
| typedef int | lte::timing::StationTask |
Functions | |
| lte::timing::ENUM (FDD, 2) | |
| lte::timing::ENUM (TDD, 1) | |
| lte::timing::ENUM (INVALID, 4) | |
| lte::timing::ENUM (IDLE, 3) | |
| lte::timing::ENUM (UT, 2) | |
| lte::timing::ENUM (RAP, 1) | |
| lte::timing::ENUM_BEGIN (DuplexSchemes) | |
| DuplexScheme: TDD or FDD. | |
| lte::timing::ENUM_BEGIN (StationTasks) | |
| StationTask is used for StationTaskPhase. BSs are always RAPs, UTs are always UTs, RN toggle between RAP and UT. | |
| lte::timing::ENUM_END () | |
1.5.5