## 1 Introduction
This is possible to be done even for such small devices by relying power efficient physical layer and Internet Engineering Task Force (IETF) IPv6 Low Power wireless Area Networks (6 LowPAN) adaptation layer enabling universal Internet connectivity, the IETF Routing Over Low power and Lossy networks (ROLL) routing protocol enabling availability, and IETF Constrained Application Protocol (CoAP) enabling seamless transport and support of Internet applications [7, 8, 9, 10, 11, 12, 13, 14, 15]. However, the challenge is that also the embedded devices which are not Internet capable would be required to connect into the Internet. M2M gateway based approach may enable also their connectivity, however, the challenge may be dynamic behavior of wireless systems and need to adapt with different kinds of service back-end systems. For example, M2M service capability layer aims to solve the heterogeneity challenge of the service systems by providing a standard based set of M2M service capabilities, which could be applied by multiple application domains [16, 17, 18]. In this model, devices and applications communicate via an M2M service platform, exposing a number of services which, in addition to boosting interoperability, will simplify and reduce the cost of M2M applications development. However, there is heterogeneity also in the technologies related to communication, information layers, security and device management. For example, there are standards such as Open Mobile Alliance Device Management (OMA-DM) [19], Device data model of Broadband Forum (BBF-069) [20], Universal Plug and Play (UPnP) [21], Device Profile for Web Services (DPWS) [22], Open Building for information exchange (oBix) [23], Open productivity and connectivity (OPC) [24], Web Ontology language (OWL) [25], and Open Geospatial Consortium Sensor Web Enablement (OGC-SWE) [26, 27, 28, 29, 30, 31] dealing with M2M information, service and devices. There are communication technologies, such as e.g., Simple mail transfer protocol (SMTP), Extensible Messaging and Presence Protocol (XMPP) [32, 33, 34], MQ Telemetry Transport (MQTT), and Session Initiation Protocol (SIP). Security is often addressed using proprietary solutions and the business party in charge of the application deployment is typically assuming the task of credential distribution. There are separate solutions for security in Local Area Network (LAN) device domains, network security to enable secure network access and security technologies applicable for application layer [35, 36, 37]. In addition, there are a number of forums focused to specify means to be applied within a single application domain and/or with specific type of devices, e.g., video devices, sensors, smart energy meters, medical devices, user interfaces, building automation, automation in the smart grids, _etc._ And different kinds of approaches for autonomic computing are discussed in e.g., [38, 39, 40]. A detailed comparison of the referred technologies has been provided in [5]. As the result of the referred comparison, it is seen that principles for the architecture are needed in order to establish a solid basis for multiple stakeholder system for M2M service networks. It is assumed in this work, that both end-to-end Internet approach, and M2M gateway based approach are needed to enable horizontally capable M2M service networks. In addition, architecture principles for solving the heterogeneity of technologies are needed to enable communication between objects and applications, which are not initially been designed to communicate together.