*For any information that you desire not accessable here, do not hesitate in contacting us by email: info@amplia.es or send us a fax: +34 917 160 173 with the name /title of your request in the fax heading.

OpenGate Agents allow devices to exchange information efficiently and reliably with M2M applications while introducing capabilities like automatic communication link management, message transmission, file transfer management, etc.
A list of the tested devices that run OpenGate communications management API is shown next:

Manufacturer	Model	Programming language
OWASYS	OWA22x	C++
OWASYS	OWA21x	C++
Wavecom	Wismo Quick Q2406B / Q26	OpenAT (C)
Siemens	TC65	Java Micro Edition
Motorola	G24	Java Micro Edition

Apart from these M2M devices, OpenGate communications management API is also available for mobile devices (PDAs, Pocket PCs, etc.) that run Microsoft .NET compact framework.

OpenGate Agent is responsible for all communication flows between OpenGate Core and the device, regardless of the communication channel used. To do this the following components are used:
Link Manager

• Complex communication link dependences model. Communication links are hierarchically organised to reflect protocol dependence (e.g. TCP depends on GPRS availability) on the device.
• Management policies for communication link hierarchies.
• Management policies for communication link error recovery.
• Management policies to control complex features present on devices:
  • Low power modes
  • Session stability

Router
This is the module that communicates directly with the wireless network, choosing from the available bearers (GPRS, WiFi, etc.) the one configured as default. Some of the features of the message router are:

• Support for simultaneous bearers. Currently available Agent Connectors are:
  • TCP/IP Connector
  • SMS Connector
  • USSD Connector (only available for telecom operators)
  • Offline Connector: Buffers messages in low or no connectivity scenarios.
• Bearer and protocol transparent.
• Applications/messages are not aware of the network communications used.
• Restricted bearers. Messages can be routed through a limited set of bearers.
• Automatic optimal bearer selection. Selects the best bearer available.

Message transmission

• OpenGate API provides message delivering functions.
• These functions have been developed having in mind most common use cases in data transmission for M2M devices.
• These possibilities allow greater flexibility in data transmission as well as M2M command execution.
• Syncronous[3] and asyncronous event, command, answer and exception sending and receiving capabilities.
• Both message delivery and message transit notifications.
• Message buffering in low or no connectivity scenarios.

Control Services
OpenGate device API provides the following control services:

• Communication check service: allows device activity checking from the Server.
• Time synchronization service: allows the Server to query devices for current time. This service gives users the possibility of establishing a device’s instantaneous time value and obtain a highly precise device time synchronization.

File Transfer
Eases file transfer tasks to and from devices. More information on this feature available on:
http://www.opengate.es/esp/caracteristicas/file_trans.htm