PlatformsFaststream SiliconFaststream RadioFaststream VisionConnected EdgeFaststream SecureMobility & Rail
ProductsSemiconductor IPWireless & RANEdge & GatewaysTracking & IdentificationSoftware & FrameworksConnected Systems
Technology5G protocol stackWireless and RF architectureBaseband and low PHYForward error correctionControl and data planeHigh-speed interfacesFirmware and bootSilicon root of trustSoftware-defined vehicleAutomotive OTAFunctional safety
AIAI Engineering ServicesEdge AI & Embedded MLComputer Vision EngineeringSensor Fusion & PerceptionAI Silicon & AccelerationMLOps for DevicesAI Visual InspectionPredictive MaintenanceDriver MonitoringVideo Analytics & Safety
SolutionsSemiconductorIndustrial AIConnected ProductsAsset TrackingBluetooth AoA RTLSWearable TrackingAutomotive & MobilitySmart InfrastructureSecure IdentityWireless & SatellitePrivate 5GSmart WashroomsFuel ManagementSmart BuildingsWorker SafetyEnergy MonitoringSmart AgricultureSmart CityAutonomous PlatformsAssembly AutomationLiDAR Rail SafetyHardware Wallet
IndustriesSemiconductorTelecommunicationsIndustrial & ManufacturingAutomotive & MobilityTransportation & RailAerospace & DefenceHealthcare & MedicalEnergy & UtilitiesOil & GasRetailConsumer ElectronicsMedia & EntertainmentSmart Infrastructure & IoT
ServicesSystem Integration overviewASIC & SoC DesignRTL to GDSIIVerification methodologyDFT and silicon testLow-power designMixed-signal integrationDesign enablementFPGA DesignFPGA-to-ASIC ConversionAnalog, Mixed-Signal & RFHardware & High-Speed PCBEmbedded SoftwareCloud, OTA & Device ManagementManufacturing TransitionHow we engage
CompanyAbout FaststreamEngineering ExcellenceLeadership & OrganisationHow We EngageQuality & ComplianceStandards & EcosystemPartners & EcosystemTrust CentreLocations & DeliveryNewsroom & MediaCareersCase StudiesKnowledge CenterWhite PapersGlossaryNewsletterResources & Support
ContactStart a projectHow we engage
Talk to us
ENGINEERING INSIGHT · WIRELESS

The MAC: turning a raw radio into a shared, efficient link.

The physical layer can send bits; the MAC decides who sends them, when, with how much power, and when the radio can sleep. It is the control layer that turns a raw PHY into an efficient, shared and — for a battery device — long-lived link.

October 20268 minute readMAC
What the MAC controls between the upper layers and the PHY.
FASTSTREAM TECHNOLOGIESFIG. 01 · THE MAC: TURNING A RAW RADIO INTO A SHARED, EFFICIENT LINK.RLC / upper layers — data to sendMAC — RADIO RESOURCE CONTROLSchedulerwho transmits whenHARQretransmit on NACKPower controljust enough powerDRXsleep to save batteryPHY — the radio it schedules ontoCHANNEL ACCESSscheduled —a controller grants slotscontention —listen-before-talk / ALOHADRX — DUTY CYCLEwakesleepthe device listens briefly, then sleeps — battery lifeThe MAC decides who gets the radio and when (scheduled or contention access), retransmits what the PHY could not deliver (HARQ), sets each device's transmit power to just enough, and puts the radio tosleep between bursts (DRX) so a battery device lasts years. It is the control layer that turns a raw PHY into an efficient, shared, low-power link.

Channel access: who gets the radio.

A radio channel is shared, so the first job of the MAC is deciding who may transmit and when. Two families. Scheduled access: a controller (a base station) grants each device specific time and frequency resources, so there are no collisions and quality of service can be guaranteed — the cellular approach. Contention access: devices listen and transmit opportunistically (listen-before-talk, CSMA, slotted ALOHA), which is simple and needs no coordinator but collides under load — the Wi-Fi and LPWA approach.

The choice shapes everything else. Scheduled access buys determinism at the cost of signalling and a scheduler; contention buys simplicity at the cost of collisions and unpredictable latency. Many systems blend them — contention to get on the channel, then a grant for the real traffic.

Retransmission and power control.

The PHY will sometimes fail to deliver a block, so the MAC owns retransmission. In modern systems this is HARQ — the receiver keeps the failed copy and combines it with the retransmission rather than discarding it — and the MAC runs the acknowledgement loop and several HARQ processes in parallel so the link does not stall waiting for one answer.

It also owns power control: setting each device's transmit power to just enough to be heard reliably, no more. Too much power wastes battery and interferes with neighbouring cells; too little drops the link. In a cell full of devices at different distances, power control is what lets them share the channel without the near ones drowning out the far ones.

Sleep: the MAC and battery life.

For a battery device the dominant cost is keeping the radio on, and the MAC is what turns it off. Discontinuous reception (DRX) lets a device sleep between brief listening windows, waking only on a schedule the network agrees — so a sensor that talks for milliseconds a day can sleep for the other 86,399 seconds. The MAC negotiates the DRX cycle, balancing how long the device sleeps against how quickly it can be reached.

This is where the MAC decides battery life. A longer sleep cycle means years on a coin cell but higher latency to reach the device; a shorter one means responsiveness at the cost of power. Getting that trade-off right for the use case is a core MAC design decision, not an afterthought.

Why it is the hard, quiet layer.

The MAC is where a radio becomes a usable network. It is also where a lot of real-world performance lives: a scheduler that is fair and efficient under load, HARQ timing that keeps the pipe full, power control that converges quickly without oscillating, and a DRX scheme that hits the battery and latency targets together. None of it shows up in a datasheet peak rate, but all of it decides how the system behaves when it is busy.

For anyone building a modem or a stack, the MAC is where the PHY's raw capability is turned into throughput, latency, fairness and battery life that the application actually sees. It is unglamorous, tightly coupled to the PHY's timing, and decisive.

QUESTIONS THIS RAISES

What engineers ask next.

01

What does the MAC layer do?

It sits between the upper layers and the physical layer and controls how the shared radio is used: channel access (who transmits when), scheduling, retransmission (HARQ), transmit power control, and discontinuous reception (DRX) for low power. It turns a raw PHY into an efficient, shared link.

02

What is the difference between scheduled and contention access?

Scheduled access has a controller grant each device specific resources, avoiding collisions and guaranteeing quality of service (cellular). Contention access has devices listen and transmit opportunistically (CSMA, ALOHA), which is simple and coordinator-free but collides under load (Wi-Fi, LPWA).

03

How does the MAC handle retransmissions?

Through HARQ: the receiver keeps a failed block and combines it with the retransmission instead of discarding it, and the MAC runs the acknowledgement loop and several HARQ processes in parallel so the link does not stall waiting for one answer.

04

What is power control and why does it matter?

Setting each device's transmit power to just enough to be heard reliably. Too much wastes battery and interferes with other cells; too little drops the link. In a cell with devices at different distances, it is what stops near devices drowning out far ones.

05

What is DRX and how does it save power?

Discontinuous reception lets a device sleep between brief listening windows, waking only on an agreed schedule. A sensor can listen for milliseconds and sleep the rest of the time, which is what makes years of battery life possible. The MAC negotiates the cycle, trading sleep depth against latency.

06

Why is the MAC important if the PHY sends the bits?

Because the PHY only sends bits; the MAC turns that raw capability into throughput, latency, fairness and battery life. A good scheduler, HARQ timing, power control and DRX scheme are what decide how the system behaves under load, none of which appears in a peak-rate datasheet.

KEEP READING

Related work.

BUILDING A MAC?

Bring us the traffic and the battery target.

A scheduler that is fair under load, HARQ timing that keeps the pipe full, power control that converges, and a DRX scheme that hits battery and latency together are the real work. Tell us the use case.