Now, looking at the same example using the Cellular Framework. The physical portion is the same. Now the code is more modular, with each layer using defined APIs to communicate with the layers above and below them. If the designer wants to use another cellular modem, simply change the modem driver piece. The change is smaller and more isolated, improving integration time as well as maintenance. The SSP Cellular Framework allows a developer to change to different modems with minimum code change, which is important as it allows developers to reuse code from their evaluation for production situations. AE-CLOUD2 also uses the SSP Cellular Framework module as a high-level application layer interface for the cellular modem integration on the SSP Application Framework and provides sets of APIs to provision, configure, and communicate with the cellular network for data communication. The SSP Cellular Framework uses the SSP Application Framework (console framework) to communicate with the cellular modems with a serial interface by using AT commands internally. The SSP Application Framework also creates the serial data pipe for serial interface for the data communication, leveraging the PPP WAN protocol provided by NetX. Any TCP/IP communication can be established over the wide area network (WAN) link using the sockets, NetX application protocols, and IoT protocols such as MQTT or COAP. The Cellular Framework also provides the framework-level socket APIs to communicate with the TCP/IP stack present on-chip (inside cellular hardware module) in certain cellular hardware modules; thereby, communicating with the Internet network using the socket APIs.