I would love to learn how the device learns the server has a message for it. I tried to find information on it, but I obviously don't know what to search for.
It's less magical than it sounds, but a lot of work goes into it. Depending on the system, hardware can partially wake at fixed intervals to check for incoming traffic, and fully wake to process that traffic.
Notably, most of the stack can stay asleep almost all the time, and wake up only when actual traffic is coming in.
Application-level polling can eat up the power savings as the whole hardware stack must wake up and process an application-level transaction taking anywhere from several tens of milliseconds to several full seconds. Compared to the "napping" state, this eats huge amounts of power.
Comments
Powered down doesn't mean turned off. It powers back up when it knows the server would like to push something.
I would love to learn how the device learns the server has a message for it. I tried to find information on it, but I obviously don't know what to search for.
It's less magical than it sounds, but a lot of work goes into it. Depending on the system, hardware can partially wake at fixed intervals to check for incoming traffic, and fully wake to process that traffic.
Notably, most of the stack can stay asleep almost all the time, and wake up only when actual traffic is coming in.
Application-level polling can eat up the power savings as the whole hardware stack must wake up and process an application-level transaction taking anywhere from several tens of milliseconds to several full seconds. Compared to the "napping" state, this eats huge amounts of power.