 also be providing Internet connec- tivity to IoT nodes 'below' it. Effectively, the UE is performing tethering of the cellular connection to any type of LAN technology, for example to WLAN or to some low-power radio technology. Deploying IPv6 in 3GPP Networks ((Q)) ((g)) Sensors and actuators ((g)) ((g)) ((g)) ((g)) networks Civil networks networks Routers Internet ((g)) ((g)) ((p)) ((g)) Local Industrial networks ((g)) networks Cloud services 'Other networks' Figure 6.6 Illustration of the world of IoT. The IoT domain very often comes with cloud-based services, also illustrated in Figure 6.6. These cloud servers can act as rendezvous points, data collection servers, social networking sites, and command and control centers to name a few. From the 3GPP point of view the most interesting things are the IoT nodes directly accessing through 3GPP networks, the nodes using 3GPP access through UEs, services that the 3GPP network may provide to IoT nodes, and of course accessing local and remote IoT nodes, and cloud services, by the UEs. 6.5.4 Implications to UEs The implications of the world of IoT to UEs depends fully on the level that a UE wants to participate, or contribute, to IoT. If the UE is a smart object itself, then obviously it needs to support IoT/M2M/MTC standards from the organizations it is compliant with. The UE may need to implement CoAP and be compliant with REST APIs defined by IPSO Alliance, the ones defined by 3GPP, or, for example, the gateway role of OMA CPNS. If this sounds unclear - it currently is. As the competing standardization landscape is fast evolving in this area, the requirements and expectations that real markets will place for UEs are not yet clear. UEs of mobile handset type, however, do not necessarily need to be aware of IoT at all. The handsets can perfectly well continue to exist and ignore IoT. However, in some scenarios a mobile handset may want to provide Internet connectivity to nearby, often inexpensive, but usually connectivity-limited IoT nodes. Such smart objects could b