Simplfy M2M Integration with a SOA Gateway
Description
Integrate between M2M stakeholders with an API management-enabled SOA Gateway Embedded device communication has been a critical component of business operations in a number of industries, for several years. However, recent innovations in micro-computing and wireless technology have created a new field of communication — machine-to-machine (M2M) — which introduces paradigm-shifting capabilities for real-time business execution.
Shared by: Layer7Tech
-
Stats
- views:
- 1
- posted:
- 4/4/2012
- language:
- pages:
- 2
Document Sample


Simplify M2M Integration with a SOA Gateway
The M2M Revolution
Embedded device communication has been a critical component of business operations in a number of industries,
for several years. However, recent innovations in micro‐computing and wireless technology have created a new
field of communication — machine‐to‐machine (M2M) — which introduces paradigm‐shifting capabilities for real‐
time business execution. M2M creates a vast “Internet of things” comprised of smart devices that produce data,
networks that transmit data and applications that turn data into meaningful information. This revolutionary
approach to computing is impacting all industries: smart meters in energy and utilities (the “smart grid”);
connected vehicles in automotive and logistics; heart monitors in healthcare; RFID‐tagged inventory in retail and
manufacturing; digital signage in media and communications.
The Building Blocks of M2M
M2M services often involve three different stakeholder roles:
1. The enterprise (the business operator that is the client of the M2M services)
2. The device operator that manages the smart devices
3. The network operator that connects the smart devices into the enterprise
Multiple roles can be fulfilled by a single technology provider. For example, a single vendor could be both device
and network operator or the enterprise could also own the devices. In most cases however, the enterprise and the
network operator will be distinct.
Within the topology of an M2M solution, there are a number of discrete areas:
Smart Devices Embedded and equipped for two‐way communication
Often SIM‐enabled for wireless communication
Hardened O/S for rugged deployment
M2M Data Lightweight payloads, compressed and filtered data
Correlated to device ID, for data enrichment
New security methods for minimizing data transmission, including Elliptic Curve
Cryptography and OAuth
M2M Network Predominantly wireless and IP‐based
Varying qualities of service
Often includes value‐added capabilities such as data aggregation and auditing
Network Services Telecommunications services such as geo‐fencing, location determination, SMS, network
management and connection profiling
Often exposed through network‐addressable REST APIs
Callable by smart devices or enterprise M2M endpoints
Enterprise Core business logic and data assets that power the enterprise
Applications, High scalability, security and availability SLAs
Services & Data Accessible through interfaces such as REST APIs, Web services, messaging sub‐systems
and SQL
To tie these stakeholders and solution areas together, consider an example from the smart grid. An energy
distributor would be the enterprise, a meter provider would be the device operator and a telecommunications
company would be the network operator. Smart meters would provide usage data at frequent intervals to the
collectors in the “head end” of the network, which would rely on Meter Data Management network services to
integrate with the energy distributor’s core systems.
Why SOA Gateways in M2M?
Integrating these areas and stakeholders is fundamental to the success of the M2M service. Due to the critical
nature of the integrated data and the complexity of multiple stakeholders, this integration must be as simple,
secure and scalable as possible. On top of these non‐functional requirements, it is worth noting that many of the
data formats and protocols most readily available in enterprise applications are too bulky for M2M.
A SOA Gateway with API management functionality can be used in the M2M solution to address these challenges
and deliver several benefits:
Single Access Point For unified data integration, monitoring and policy management
Through cryptographic functions, state‐of‐the‐art standards like OAuth and re‐use of back‐end
Secure Connectivity
security sub‐systems
High Scalability Optimized message‐processing engine for high concurrency and low latency
Support for data transformation, validation and filtering as well as API protocols (REST, JSON, XML),
Flexible Integration
enterprise protocols (SOAP, JMS, MQ, SQL) and service orchestration
Developer Manage the enrollment and administration of internal and external developers, for building M2M
Management value‐add applications
API‐Ready SOA Gateway from Layer 7
Layer 7 Technologies is the industry leader in integration Gateway solutions and offers robust, enterprise‐grade
Gateways for API management and SOA. Each of the following components delivers unique value for M2M:
SOA Gateway To provide a carrier‐grade M2M integration and security control point
To allow the API owners (enterprise and network) to set and enforce SLAs and to provide
API Portal
comprehensive information to users of the APIs (smart device developers, network operators)
To configure access‐control policies that are fit for M2M and able to leverage back‐end
OAuth Toolkit
infrastructure
Enterprise Service To provide a deployment and configuration management platform for the Gateway and to deliver
Manager API‐oriented monitoring and management
For more information on Layer 7 Technologies, please visit our Web site: http://www.layer7.com/
Get documents about "