of some of these organizations are described in more depth in the following sections. 3GPP Standardization Work The 3GPP http://www.3gpp.org is working on significant systems improvements for IoT, referred to as Machine-Type Communications (MTC) in 3GPP vocabulary. The continu- ously evolving work was ongoing, at the time of writing, in multiple 3GPP areas (see 3GPP organization in Section 2.1.1). Hence, this section should be read with caution and just to see what kinds of issues IoT is causing for many aspect of 3GPP standards. On the System Aspects area, the SA1 working group is working on requirements, such as: service requirements for MTC [61], studies for enhancements for MTC [62], studies for alternatives to £.164 [63], and more. The SA2 working group is working on architectural issues such as: architecture enhancements [64], system improvements for MTC [65], and also analyzing implications caused to other areas such as to packet radio service (from 2nd Generation (2G) to LTE), architectural requirements, and SO on. As usually is the case with major features, security aspects of MTC requires special attention from the SA3 working group [66]. The MTC has implications also for charging, to the SA5 working group's telecom management, for example: Charging Data Record (CDR) parameters [67], packet switched domain charging [68], and diameter charging applications [69]. The charging aspects are handled by the SA5 working group. At least four of the Core Network and Terminals area working groups are involved in the MTC work as well. The CT1, responsible of defining UE - the core network layer-3 radio protocols, is working on updates to NAS configuration management object [70], although the set of CTI's other documents will also be affected. Quite obviously the smart objects on 3GPP networks need interworking with external networks and hence CT3 is working on MTC interworking function and service capability server [71] alongside lesser updates to their other specifications. The CT4 is working for system improvemen