M2M communication is needed before a user can use a service. Some examples are shown below: File transfer, e.g. machine-machine information when taking back-up copies of a sys- tem content or when system upgrades are done. Another example is when a user orders download of music files, like Napster or download of 'video on demand' content. 'Intelligent' M2M communication and interaction for 'autonomous' systems. One ex- ample is telecom networks with switches, routers and communication links handling fluctuating traffic streams, overload situations and correction of malfunctions. Remote control data, e.g. when an operating system controls traffic systems in the example above. The 'manual' variant has already become hype, i.e. 'control your toaster, house heating/cooling and light from wherever you are' Remote notifications, for example transmitting alarms, responses and other status infor- mation for autonomous or manual actions. The media types are transported as 'data' except for 'classical telephony', which is treated explicitly as voice communication. This is slowly replaced by packet-oriented transportation, i.e. 'IP telephony' or 'voice over IP'. The typical development goes from large communicating machines towards smaller ones. The first wave was a network of IP-addressed computers that swelled to encompass End-User Needs and Demands hundreds of millions of systems. The Internet connected machines and people tapped in when they could. The second wave is the one we are riding now. It could be described as a network of things that embed computers. It is mainly made up of wireless phones and other handsets, game-players, teller machines and cars. The number of possible connections is more than a billion. An example of application is remote control of ventilation plants, which saves energy. The third wave is on the way. More or less all things (and animals) might be involved: light bulbs, sensors, notes, beer glasses, bees. Miniature tags are added to all kinds of products, and can tell the story of the thing,