EP1639787A2

EP1639787A2 - System and method for remote controlling equipment with the aid of at commands, and corresponding device, radiocommunication module, and set of commands

Info

Publication number: EP1639787A2
Application number: EP04767361A
Authority: EP
Inventors: Christian Amiens
Original assignee: Wavecom SA
Current assignee: Sierra Wireless SA
Priority date: 2003-06-16
Filing date: 2004-06-16
Publication date: 2006-03-29
Also published as: US7698382B2; FR2856231A1; WO2004114625A3; WO2004114625A2; US20070213042A1

Abstract

The invention relates to a system for remote controlling equipment, which allows at least one server and at least one remote piece of equipment to be interconnected according to the MQIsdp protocol. Said system associates at least one of said remote pieces of equipment with radiocommunication means that emit and receive AT-type commands issued by and/or addressed to an external application which is used by said distant piece of equipment. Said radiocommunication means are provided with a set of specific AT commands for exchanging data with at least one server that uses the MQIsdp protocol such that said server/s and said remote piece/s of equipment can be interconnected via said radiocommunication means without the distant pieces of equipment having to know the MQIsdp protocol.

Description

System and method for controlling equipment remotely using AT commands, radiocommunication device and module and corresponding command set.

The field of the invention is that of remote control of equipment, and in particular of equipment limited in data processing resources. Thus, the invention applies for example to remote data collection systems, for example on water, gas or electricity meters, and more generally to telemetry systems, order tracking, and more generally machine control (in English "M to M: machine to machine").

There are already various solutions for carrying out such operations. They have generally been developed specifically for a given application. In other words, these are “proprietary” solutions, which are difficult to adapt to other applications.

A protocol is also known, developed by the companies IBM and ARCOM Control Systems (registered trademarks), known under the name of technology "MQIsdp Messaging". This technique provides a communication protocol between one or more equipment limited in resources, and one or more servers ("brokers" in English), using a TCP / IP link.

However, even with this specific protocol, it is necessary to add specific processing means (microprocessors, memories, etc.) to the equipment, which allow dialogue to be established with these remote servers, according to the required MQIsdp format. The link between the equipment and the server can use a telephone type link, using a modem.

In many applications, it would however be desirable to be able to do without a wired telephone link. We can then consider the implementation of radio communication means, for example according to the GSM or GPRS standard. In this case, radio equipment will be used to perform the modem function. However, it remains necessary, according to the prior art, to associate with the equipment specific and proprietary means of data processing to establish and carry out the exchange of data with the server. This aspect is a very important limitation to the development of the applications mentioned above, and of many other applications that makes it possible to envisage the MQIsdp protocol.

The invention particularly aims to overcome this drawback of the prior art. It should be noted that the fact of identifying this problem is in itself a part of the invention. Indeed, a person skilled in the art is convinced that it is absolutely necessary to equip the terminal equipment with sufficient processing means, and cannot in any case envisage that it is possible to reduce or even eliminate them. However, it is an objective of the invention to make it possible to simplify the necessary processing on the side of the equipment, and to avoid that it must have complex and expensive means such as a microprocessor.

Another objective of the invention is to propose a simple and generic technique, making it possible to easily and effectively establish a dialogue with a server according to the MQIsdp protocol.

Yet another objective of the invention is to provide such a technique, making it possible to establish a link between servers and equipment by radiotelephone, in a simple, standardized and inexpensive manner.

The invention also aims to provide such a technique, making it possible to develop a large number of applications, without the need to develop specific applications each time.

Another objective of the invention is to provide such a technique, not requiring knowledge of the MQIsdp protocol in the applications developed. Yet another objective of the invention is to provide such a technique, which is both technically simple and scalable, and adaptable to various situations (for example for the size of the data to be exchanged) and to possible future developments.

These objectives, as well as others which will appear more clearly thereafter, are achieved using a remote equipment control system, allowing interconnection between at least one server and at least one remote equipment according to the MQIsdp protocol.

According to the invention, radiocommunication means capable of transmitting and receiving AT type commands issued by and / or intended for an external application implemented by said remote equipment are associated with at least one of said remote devices. being equipped with a set of specific AT commands making it possible to exchange data with at least one server implementing said MQIsdp protocol, so as to allow interconnection between said server (s) and said remote equipment (s) via said means radio communication, without requiring knowledge of said MQIsdp protocol in said remote equipment.

Thus, it is possible to easily and simply manage data exchanges, without the need to develop specific applications or to associate significant means (microprocessor and memory in particular) with a terminal. Neither the latter nor the application needs to know the protocol

MQIsdp. These are the means of radiocommunication. The only knowledge required, seen from the application, are the new AT commands of the invention.

Advantageously, at least in a first mode, said radiocommunication means manage only the signaling of a data exchange, said data being transferred directly from a remote device to a server, or vice versa.

Preferably, at least in a second mode, said radiocommunication means manage the signaling of a data exchange and the transfer of said data, the latter being temporarily stored in the minus a buffer.

In this case, the size of the said buffer memory (s) can advantageously be configured.

According to an advantageous embodiment, said system operates in said first mode when the size of said buffer memory or memories is equal to 0, and in said second mode otherwise.

This provides a simple and efficient way to perform two functions (choice of mode and sizing of queues) with a single command. In an advantageous embodiment of the invention, said radiocommunication means comprise a radiocommunication module, grouping on a same substrate all the means for processing radio frequency and baseband data, as well as the means for managing said AT commands. Said radiocommunication means can in particular integrate said MQIsdp protocol in the form of an "Open-AT" application, defining said set of specific AT commands.

Advantageously, said set of specific AT commands includes commands allowing: - connection to one of said servers;

- sending messages;

- receiving messages.

Preferably, at least some of said specific AT commands are organized so as to be able to perform at least two functions and / or act on at least two distinct aspects, according to a predefined configuration.

This makes it possible to greatly reduce the number of orders required, while ensuring all the necessary operations and making it possible to take into account any future developments. Thus, in a preferred embodiment, said set of commands includes only 8 orders.

Said set of specific AT commands advantageously comprises at least one configuration command making it possible to define the parameters of the communication with one of said servers. Preferably, the system implements a single configuration command (+ WSPGSET) for the configuration of the radiocommunication aspects and the general configuration of the aspects related to the MQIsdp protocol.

Said configuration command can in particular make it possible to select a transmission mode from at least two (GSM and GPRS).

Advantageously, the system implements three configuration commands:

- a general communication configuration command (+ WSPGSET); - a command to configure a connection (+ WSPCSET), making it possible to specify in particular the coordinates of a server;

- a command to configure the configuration message "ill" (+ WSPWMS), making it possible in particular to specify the channel for which a message is intended. Preferably, it also implements at least one general communication command, allowing the transmission and / or reception of messages according to the MQIsdp protocol.

Thus, it can advantageously implement five general communication commands: - a command for specifying an MQIsdp context

(+ WSPDCONT);

- a command to manage a connection with a server (+ WSPCONM);

- a command to send a message (+ WSPSMSG); - a command to receive a message (+ WSPRMSG); - an administration command, allowing a reset and / or a return to the default values of a set of parameters (+ WSPPA).

Advantageously, it also implements at least one interrogation command by an external application, and preferably two interrogation commands by an external application, respectively on:

- the current state of the connection (+ WSPICON);

- receiving and / or sending a message (+ WSPIMSG). The invention also relates to the remote equipment control method implemented by a system as described above. It allows interconnection between at least one server and at least one remote device according to the MQIsdp protocol, by associating at least one of said remote devices with radiocommunication means capable of transmitting and receiving AT type commands emitted by and / or intended for an external application implemented by said remote equipment, and by implementing, in said radiocommunication means, a set of specific AT commands making it possible to exchange data with at least one server implementing said MQIsdp protocol. This allows interconnection between said server (s) and said remote equipment (s) via said radiocommunication means, without requiring additional means for processing and / or formatting data in said remote equipment.

The invention also relates to radiocommunication devices and modules comprising radiocommunication means implemented in such a remote equipment control system. Finally, the invention relates to the AT command sets implemented in a remote equipment control system, and making it possible to exchange data with at least one server implementing said MQIsdp protocol.

Other characteristics and advantages of the invention will appear more clearly on reading the following description of a preferred embodiment of the invention, given by way of simple illustrative example and not limiting, and attached drawings, among which:

- Figure 1 illustrates an example of a system in which the invention can be implemented;

- Figure 2 is an example of integration of the MQIsdp protocol in an Open-AT application;

- Figures 3A to 3L illustrate different examples of implementation of a connection according to the invention.

1. Reminders on the MQIsdp protocol (registered trademark

The MQIsdp protocol ("WebSphere MQ Integrator SCADA device protocol" in English) is an open standard developed by IBM and Arcom

Control Systems (registered trademarks), aimed at enabling data exchanges

(in the form of messages) from remote devices (or terminals), generally low-end and with little processing power, to a server, also called “broker” (WebSphere MQ) Integrator by TCP / IP, and vice versa.

MQIsdp (also called Wavecom SCADA hereinafter) is a data transfer protocol (message) based on a communication model of the publish / subscribe type, available free of charge on the Internet. It can be described as a simple layer of agnostic data management over the TCP / IP protocol to provide the required message handling and acknowledgments to ensure reliable delivery of the message.

In the publish / subscribe communication model, data is exchanged between a data producer / consumer (the client) and a message broker (the server). The message broker can be considered as a multiprotocol switching hub (node) at the level of the application protocol which receives messages, transforms them, reformats them, etc. in other structures based on a user-defined data model.

Finally, messages that may have been transformed can be sent by the broker (published) to subscribed customers (zone device, ERP, SAP, Oracle, SQL, etc.) using the appropriate customer cards. The broker can, of course, also post messages not from a client.

The message broker manages all messages entering and leaving a section. A client publishes messages in / with a topic or subscribes to messages from / by a topic identifying the message flow of the message broker to or from which the message is to be posted.

The MQIsdp specification defines a very simple set of messages, including: "connect", "disconnect", "publish", "subscribe", "unsubscribe".

2. principles of the invention 2.1 general

The invention therefore relates to a new approach to remote equipment control, based in particular on the implementation of a set of specific AT type commands, allowing an external application to manage data exchanges between a remote terminal and a server, via radio communication means (for example a Wismo (registered trademark) type module), without the application knowing the MQIsdp protocol implemented by the server. It is the radiocommunication means which manage this aspect, and for example the acknowledgments provided for in the MQIsdp protocol.

Figure 1 illustrates in a simplified manner the principle of the invention. The objective is to make all types of remote machines communicate, for example measuring instruments 11 with one or more applications hosted by servers 12, capable of receiving data 13 according to the MQIsdp protocol, and of transforming, processing or transmitting it .

According to the invention, radiocommunication means 14 are associated with the remote terminals (or machines) 11, for example in the form of a module

Wismo (registered trademark), including the development tools distributed by the depositor under the brand name "Muse platform").

2.2 Concept of module

As a reminder, it is recalled that most radiocommunication devices conventionally comprise a set of electronic components installed on a printed circuit. The purpose of these various components is to provide the various necessary functions, from the reception of an RF signal to the generation of an audible signal (in the case of a radio telephone), and vice versa. Some of these functions are analog, others digital.

The manufacture of these radiocommunication devices is an important research subject. Indeed, there are at least three objectives which are difficult to reconcile: miniaturize the devices, increase the functionalities and simplify the assembly. It is known in particular that the installation of the various components on the printed circuit is a relatively complex operation, many components having to be placed on an increasingly restricted surface, due to the requirements of miniaturization.

The design of these systems is therefore complex, since it also requires combining various components, often from multiple sources, which must be operated together, while respecting the specificities of each. Furthermore, after the assembly of all the components, calibration and testing phases, often long and complex, are necessary to guarantee the proper functioning of the device.

Finally, despite the reduction in the size of certain components, the assembly occupies a certain area, which is difficult to reduce.

The owner of the present patent application has proposed an approach which overcomes a certain number of these drawbacks, consisting in grouping, in a single module, all or at least most of the functions of a digital radiocommunication device. Such a module is in the form of a single and compact housing, preferably shielded, that the device manufacturers can install directly, without having to take into account a multitude of components.

This module (also sometimes called “macro-component”) is in fact formed by a grouping of several components on a substrate, so as to be implanted as a single element. It includes the essential components and software necessary for the operation of a telecommunications terminal using radio frequencies. There are therefore no more complex stages in the design of the design, and validation of it. All you need to do is reserve the space required for the module.

Such a module therefore makes it possible to easily, quickly and optimally integrate all of the components in wireless terminals (mobile phones, modems, or any other application using a wireless standard).

In addition, this one gathering all the essential functions and having been conceived as a whole, the problems of calibration and tests do not arise any more in the same way, or are at the very least, greatly simplified.

Thus, the modules distributed by the holder of this patent application are fully tested both on the hardware ("hardware") and software ("software") on most networks on which they can be used later. In addition, the module advantageously includes the aspects of industrial property (all the functions having been grouped, it is the manufacturer of the module who manages the aspects of corresponding industrial property rights) and technical assistance.

2.3 AT commands The principle of implementing AT commands is already known. It is for example described in patent document FR-99 13645, and in the various specifications published by the applicant, which will be referred to for further information, if necessary.

2.4 new AT commands This module 14 is capable of managing simple AT commands, and in reduced number, allowing a simple and efficient dialogue with an external application associated with a terminal. It ensures the transformation to the MQIsdp format, and manages the transmission and reception of data 15 according to this protocol, in a transparent manner for the application. Data can thus be exchanged wirelessly 16, by example according to GSM or GPRS standard. Seen from server 12, the information is in MQIsdp format. For the terminals 11, it is not necessary to know this protocol, but only a few AT commands. It is thus possible to easily and inexpensively implement an external application in (or next to) a terminal, without the need to provide a microprocessor and memories, and a dedicated application.

As we will see below, the AT commands offered can be limited to the number of 8, while remaining scalable.

Two modes of data transfer are proposed: - the data pass through the module 14. They are then temporarily stored in buffers (buffers), the size of which can be configured as required;

the data are transmitted directly between the terminal and the server, without being stored in memory in the module 14, the latter managing only all of the signaling aspects (opening and closing of the connection, acknowledgments, etc.).

The first case may correspond to the most frequent case of small messages, and the second to the transfer of large files, as provided for in the MQIsdp protocol. It is thus possible to manage everything via the module, without adding external memory and intelligence, while allowing the transfer of data having a volume greater than the storage capacity of the module.

Advantageously, a single command makes it possible to size the buffers and to switch from one mode to another (the second mode corresponding to a zero value). FIG. 2 illustrates a simplified example of software architecture which can be implemented in module 14.

Such a module 14 generally comprises:

- a basic software layer 21 (“Wavecom Core Soft are”);

- an Open AT 22 library (“Open AT Library”); - an ADL 23 library ("ADL Library"); - a TCP / IP Library 24 (“TCP / IP Library”);

- an application layer 25 ("Open AT Application").

According to the invention, a library 26 of specific commands (“Wavecom SCADA Protocol Library”) is therefore also provided for communicating according to the MQIsdp protocol, which is placed above the TCP / IP library 24.

The AT commands 27 are addressed, as the case may be, to the base layer 21, to the TCP / IP library 24 or to the SCADA library 26.

The proposed AT command interface includes in this library 26 only 8 commands, allowing to fully exploit the MQIsdp protocol, and in particular:

- possibility to size two internal queues to manage incoming and outgoing messages;

- possibility of outsourcing the management of large messages; - definition of connection contexts;

- management of configuration parameters;

- management of the sending of different types of messages by generic command.

3. detailed description of an embodiment of commands We describe below the AT commands that can be used to control the Wavecom SCADA 26 protocol. 3.1 Related documents

If necessary, we can refer in particular to: [1] This document must be read with the "WepSphere MQ Integrator SCADA Device Protocol" sheet in Annex B of the "IBM WebSphere MQ Integrator Programming Guide" reference manual available at the following address: http: // publif p. boulder.ibm. com / epubs / odf / bipval04. pdf [2] Wavecom AT Commands Interface Guide Reference: WM SW OAT IFS 001 - revision: 009 or following. This document describes the AT commands supported by the Wavecom product used to manage related GSM events or services. [3] AT Command Interface for TCP / IP Revision: 1.7

This document describes the parameters and the AT command set used to configure and control the TCP / IP overlay and the protocols available on Wavecom products. 3.2 Abbreviations and definitions 3.2.1. Abbreviations

APN Access Point Name

AT Attention

DNS Domain Name System

ISP Internet Service Provider ME Mobile Equipment

SCADA Supervisory Control and Data Acquisition MS Mobile station

QoS Quality of Service Wavecom core software:

Software layer supporting all AT commands to manage related GSM events or services. 3.2.2. Definitions

The terms MS or ME are used for mobile terminals supporting GSM services. The word "product" refers to any Wavecom product (module in particular) that supports the AT command interface. Symbols:

<CR> Carriage return character

<LP> Line feed character [...] Optional parameter of an AT command <...> Parameter name put between chevrons. The chevrons do not appear on the command line.

3.3 AT command syntax

This paragraph describes the format of AT commands, as well as the mechanisms for assigning default values for their parameters.

3.3.1 Command line

Commands always start with the standard prefix "AT + WSP" and end with the character <CR>.

Optional parameters are indicated in square brackets []. Example: AT + WSPCmd = <Paraml> [, <Param2>]

In this example, <Param2> is optional. When the AT + WSPCmd command is executed without <Param2>, the default value of the <Param2> parameter is used.

3.3.2 Information responses and result codes Responses begin and end with <CRxLF> (except for the format of the ATVO DCE response) and the ATQl commands (deletion of result code) (see the related document [2] ).

• If the command syntax is incorrect, the command is returned to the central Wavecom software for processing. In this case, the "ERROR" message is returned by the central Wavecom software.

• If the command syntax is correct but erroneous parameters have been transmitted, the response <CR> <LF> + WSP ERROR: <ErrxCRxLF> is returned, accompanied by the appropriate error codes.

• If the command line has been successfully executed, a <CR> <LF "OK" <CRxLF> string is returned.

3.4 Configuration commands

Different parameters are necessary to provide the Wavecom product with all the information relating to the initial connection: The support network used: GSM or GPRS • The timeout parameters • The functional mode of the Wavecom SCADA protocol overlay

• All the necessary information relating to the support network to allow access to a TCP / IP infrastructure

• The configuration message "Will" for the connection. 3.4.1 General parameters + WSPGSET a- Description

This command allows you to configure all the parameters used to select the support network, the different timers and the functional mode of the Wavecom SCADA protocol. b - Syntax

c - Defined values

<Mode> (0-2) Execution mode

0 Sets the parameter defined by <Parameterid> to the value indicated by <Value>

1 Reads the current value of the parameter defined by <Parameterid>

2 Reads the current value of all parameters <Value> (0-32767) Value of the parameter indicated by <Paramid> <Paramid> (1-11) The following table lists the different parameters.

d - Possible error codes

+ WSP ERROR 4000 Wavecom SCADA protocol function not activated.

This error is returned when the protocol function

Wavecom SCADA has not been activated in the module

WISMO. + WSP ERROR 4001 Operation not authorized. This error is returned when an incorrect parameter is detected. e - Informative examples

3.4.2 Connection parameters + WSPCSET

a - Description

This command is used to configure all connection parameters (by family).

b - Syntax

c - Defined values <Settings_type> (0-1) Parameter categories

0 ISP settings

1 APN parameters * IPS parameters (5 parameters) - Settings_type = 0

These parameters are used when the GSM support network (data by circuit switching) is selected. See the "Other parameters" section.

* APN parameters (3 parameters) - Settings_type = T

These parameters are used when the GPRS support network is selected. See the "Other parameters" section.

d - Possible error codes + WSP ERROR 4000 Function of the Wavecom SCADA protocol not activated.

This error is returned when the Wavecom SCADA protocol function has not been activated in the WISMO module. + WSP ERROR 4001 Operation not authorized. This error is returned when an incorrect parameter is detected, e - Informative examples

3.4.3 Parameters of the Will + WSPWMS message a- Description

This command configures all the parameters relating to the message Will. This command returns + WSP ERROR: 4013 if the value 0 is assigned to the parameter <OutBoxSize>. b- Syntax

c - Defined values

<Topic> This string identifies the information channel on which the text data has been published.

Maximum length = 64 characters

<Qos> (0-2) Quality of service

0 Once maximum - "Fire and Forget" (send and forget)

1 At least once - Delivery with acknowledgment of receipt

2 Exactly once - Insured delivery default value = 0

<Retain> (0-1) Indicates to the broker that the message must be kept and sent to tonbuvel subscribed to this section as initial message. Default value = 0

<PayloadLength> Maximum length of the message body. This value is limited by the value of the <OutBoxSize> parameter.

If the value <OutBoxSize> is assigned to 0, this value is no longer limited (for more information on the <OutBoxSize> parameter, see the paragraph on the command + WSPGSET). d- Possible error codes + WSP ERROR 4000 Function of the Wavecom SCADA protocol not activated. This error is returned when the protocol function

Wavecom SCADA has not been activated in the WISMO module. + WSP ERROR 4001 Operation not authorized. This error is returned when an incorrect parameter is detected. + WSP ERROR 4002 Operation not supported by the current configuration. e - Informative examples

Note: the <ctrl> P command in the text requires the use of the <ctrl> P <ctrl> P escape command. 3.5 General orders

3.5.1 Definition of the WSP + WSPDCONT context

a - Description

This command sets the parameter values for a WSP context identified by the local context identification parameter, <WSPCid>.

A maximum of two WSP contexts can be defined.

A special form of the defined command, + WSPDCONT = <WSPCid> allows you to delete a WSP context. b - Syntax

c - Defined values <WSPCid>) (1-2 WSP context identifier: numeric parameter which indicates a definition of a given WSP context. <Clientid> Wavecom protocol client identifier

SCADA: parameter on chain which identifies the client. Maximum length = 23 characters Default value = unreadable <Broker_Addr> Parameter on chain (or IP address) which identifies the broker server and makes it possible to reach it. Maximum length = 255 characters Default values = unreadable <Port> (0-6553 ^ Numerical parameter (Broker port) which allows to reach the broker server for data transfer. Default values = 1883 <CleanStart_Flag> (0-1) 0 The client continues with the data of the previous connections.

1 The broker cancels all pending messages for the client, deletes all subscriptions from the client, and reassigns the value 1 to the message ID. Default value = 0 <KeepAliveTimer> (0-32767) Maximum interval between each message from a client. The value 0 indicates that no connection maintenance timeout processing (Keep

Alive) is not performed. Default value = 0 <UseLWT_Flag> (0-1) Indicates if the message Will is used:

0 The message Will is not used. 1 The message Will is used

Default value = 0 d - Possible error codes + WSP ERROR 4000 Function of Wavecom SCADA protocol not activated. This error is returned when the Wavecom SCADA protocol function has not been activated in the WISMO module.

+ WSP ERROR 4001 Operation not authorized. This error is returned when an incorrect parameter is detected. e - Informative examples

3.5.2 Connection management + WSPCONM

a - Description

This command manages the connection to a broker. b - Syntax

c - Defined values <Mode> (0-1) 0 Disconnection from a protocol session

Wavecom SCADA active.

1 Connection to the remote broker.

2 Drop connection.

<WSPCid> WSP context identifier: numeric parameter which identifies the definition of a given WSP context.

<CleanDisconnect> (0-1) Disconnection mode. 0 Disconnection occurs immediately, the queue is emptied and all transactions in progress are deleted.

1 All queued messages (pending or pending) are processed before disconnection. Default value = 1

<Status> (0-2) Status of the connection with the broker.

0 Not connected

1 Connected

2 Connection pending e - Possible error codes

+ WSP ERROR 4000 Wavecom SCADA protocol function not activated. This error is returned when the Wavecom SCADA protocol function has not been activated in the WISMO module.

+ WSP ERROR 4001 Operation not authorized. This error is returned when an incorrect parameter is detected.

+ WSP ERROR: 4003 WSP context not defined. + WSP ERROR: 4004 Client already connected. + WSP ERROR: 4005 Connection operation pending. + WSP ERROR: 4006 Disconnection operation pending. + WSP ERROR 4007 Client not connected. This error is returned when a disconnection is requested while the ME is not connected.

+ WSP ERROR: 4008 No network. + WSP ERROR: 4009 No GPRS. + WSP ERROR: 40010 No TCP / IP. e - Informative examples

3.5.3 Message sending + WSPSMSG

a - Description

This command allows you to send or obtain the status of several types of messages, including Publish, Subscribe and Unsubscribe.

The specification of the Wavecom SCADA protocol allows a SUBSCRIBE / UNSUBSCRIBE message to send several subscriptions / unsubscriptions. For this AT command, the limit is set at one item per SUBSCRIBE / UNSUBSCRIBE message. In this case, an application wishing to subscribe / unsubscribe from several sections will issue several SUBSCRIBE / UNSUBSCRIBE requests for a single section. b - Syntax

c - Defined values <ActionType> Type of operation

0 Sending a message

1 Get message status

* Sending a message (5 parameters) - ActionType = 0

(*) Maximum length of the message body. This value is limited by the value of the <OutBoxSize> parameter. If the value <OutBoxSize> is assigned a value of 0, there is no limit (for more information on the <OutBoxSize> parameter, see the paragraph on the command + WSPGSET). Note: if MsgType = 10 (UNSUBSCRIBE), then only the <Topic> parameter is required. Otherwise, if MsgType = 8 (SUBSCRIBE) then the <Topic> and <Qos> parameters are used. If the <Qos> parameter is enabled, then the default value is used. Otherwise, if MsgType = 3 (PUBLISH), then all parameters are used. If the parameters <Qos> and

<Retain> are omitted, the default values are used. Then assign the <Payload> parameter the number of bytes indicated by the <PayLoadLength> parameter. Or

Enter <Payload> <Ctrl> P <Ctrl> C when the parameter

<PayloadLength> is omitted. * Get status (1 parameter) - ActionType = 1

<Status> Status of a message

W WAITING. The message is queued, the transaction has not started. P PENDING. The message is queued. The transaction is in progress. N Message not found. The message is not in the queue.

Either the transaction is complete, or the message has never been queued. d - Possible error codes

+ WSP ERROR: 4007 Client not connected.

+ WSP ERROR: 40011 The queue is full. e - Informative examples

Notes:

[1] A <Ctrl> P in the text requires the escape command <Ctrl> P <Ctrl> P.

[2] The <MsgHandle> parameter is only managed if the value 32767 bytes is assigned to the <OutBoxSize> parameter (see the General parameters section, command + WSPGSET).

When the value <OutBoxSize> is assigned to the value 0, the <MsgHandle> parameter takes the value 1 each time. 3.5.4 Message reception + WSPRMSG a - Description

This command allows you to read a received message. The message is received with the indication + WSPIMSG.

The broker can send a PUBLISH message to the client on any section to which the client is subscribed. This AT command obtains messages arrived in the queue of the incoming trash.

This AT command is only available if the value 0 is not assigned to the <InboxSize> parameter (see General parameters, command + WSPGSET). If the value <InboxSize> is assigned the value 0, the messages are displayed with the indication + WSPIRMSG. b - Syntax

c - Defined values <Msgid> (0-32767) Identifier of the message received. <Mode> (0-1) Reception mode

0 Exit completed (by <ctrl> P <ctrl> C) without the header (DUP, Qos, Retain ...).

1 Exit complete and header displayed. d - Possible error codes

+ WSP ERROR 4002 Operation not supported by the current configuration.

+ WSP ERROR: 40012 Message not found. e - Informative examples

Order Possible responses

AT + WSPRMSG? + WSPCONM: 8 OK

Note: obtains the list of Note: there is a message in the messages appearing in the inbox queue. from the arriving basket.

3.5.5 Protocol administration + WSPPA

a - Description

This command is used to perform a general reset (RESET) in the different queues or to restore the default values of all parameters. b - Syntax

c- Defined values <ActionType> (0-1) Type of action.

0 RESET. Empties the queue and interrupts all transactions in progress.

1 DEFAULT PARAMETERS. All parameters of the AT command parameters are reset to their default values. Action possible only offline. d - Possible error codes + WSP ERROR 4000 Function of the Wavecom SCADA protocol not activated. This error is returned when the Wavecom SCADA protocol function has not been activated in the WISMO module. + WSP ERROR 4001 Operation not authorized. This error is returned when an incorrect parameter is detected.

+ WSP ERROR 4002 Operation not supported by the current configuration. e - Informative examples

3.6 WSP indications

This chapter describes all message event responses sent. 3.6.1 Connection indications + WSPDCONI

To allow the external application to know the status of the connection, a connection indication mechanism (+ WSPCONI) is set up. These indications are sent when a value between 1 and 3 is assigned to the <NotifyLevel> parameter (see the + WSPGSET command). Syntax: + WSPCONI: <Status><Status> 0 The requested disconnection is complete.

1 Connection with the broker is established.

2 Connection with the broker is refused.

3 Protocol version not supported.

4 Identifier rejected by the broker. 5 Will message configuration required. This indication is only returned when the + WSPWMS command has not been configured before connection. 6 Time exceeded for configuration of the Will message. Connection not established. 3.6.2 Message sending indications + WSPSMSGI

To allow the external application to know if the message has been received or if a message has been sent, a message indication mechanism (+ WSPSMSGI) is set up.

These indications are sent when the value 2 or 3 is assigned to the <NotifyLevel> parameter (see the command + WSPGSET) and if the value 32767 is assigned to the <InboxSize> parameter. Syntax: + WSPSMSGI: <Status>, <Msgid> <Status>

0 The message <Msgid> has been delivered (Qos> 0) 1 The message <Msgid> has been deleted (all attempts have failed) <Msgid>

(0-32767) Message identifier 3.6.3 Message reception indications + WSPRMSGI If the size of the incoming basket (<InboxSize>) is zero (0), messages are displayed with the indication + WSPRMSGI upon receipt.

These indications are sent when the value 2 or 3 is assigned to the <NotifyLevel> parameter (see the command + WSPGSET) and when the value 0 is assigned to the <InboxSize> parameter.

The message header and / or the payload are displayed according to the + WSPGSET RecMsgMode parameter.

Syntax: + WSPRMSGI: <Status> [, <Msgid> [, <Topic>, <Dup>, <Qos>, <Retain>, <LengthxCRxLE> <Data>]]

0 Message <Msgid> received in the inbox.

1 Message received. The message is routed directly to the output.

2 Saturated arrival basket. 3 No message reception capacity.

4 Message finished.

5 Wrong message.

<Msgid> (0-32767) Identifier of the message received.

<Topic> String of the message item. <Dup> (0-1) Double indicator (for Qos 1 and 2).

<Qos> (0-2) Quality of service for this message.

<Retain> (0-1) Memory indicator (Retain).

<Length> (0-size of the outbox (Outboxsize) Load length (Payload). <Data> Message data.

3.7. Error codes

This chapter describes all the error codes returned by AT commands

WSP.

4. Examples

This paragraph gives examples of the use of the AT command set of the Wavecom SCADA protocol described above. These examples are illustrated respectively in FIGS. 3A to 3K.

In these figures, the information is presented according to a usual formalism for those skilled in the art, showing precisely the data exchanges between the different entities (server, or broker, module and application external). The fourth column indicates the commands used, and where applicable their meaning.

It does not appear necessary to comment further on these figures, the interpretation of which is direct for those skilled in the art. The following aspects are presented:

4.1 Message reception with Qos 0

4.1.1 With an incoming basket (Figure 3 A)

4.1.2 Without incoming basket (Figure 3B)

4.2 Receiving a message with Qos 1 4.2.1 With an incoming basket (Figure 3C)

4.2.2 Without arriving basket (Figure 3D)

4.3 Message reception with Qos 2

4.3.1 With an incoming basket (Figure 3E)

4.3.2 Without incoming basket (Figure 3F) 4.4 Sending a message with Qos 0

4.4.1 With a start basket (figure 3G)

4.4.2 Without start basket (Figure 3H)

4.5 Sending a message with Qos 1

4.5.1 With a start basket (Figure 31) 4.5.2 Without a start basket (Figure 3J)

4.6 Sending a message with Qos 2

4.6.1 With a start basket (Figure 3K)

4.6.2 Without start basket (Figure 3L)

4.7 Comments We can see in these different figures that the external application does not have to know the MQIsdp protocol (PUBLISH, PUBREC, PUBREL, PUBCOM, ... commands), but only the AT commands presented above.

It is the module that provides the interface, transparently. The programming of the module to realize this interface is obvious, from the specifications given above on the one hand, and those of the MQIsdp protocol on the other hand.

Claims

1. Remote equipment control system, allowing interconnection between at least one server and at least one remote equipment according to the protocol

MQIsdp, characterized in that it associates with at least one of said remote devices radiocommunication means capable of transmitting and receiving AT type commands emitted by and / or intended for an external application implemented by said remote equipment, and in that said radiocommunication means are provided with a set of specific AT commands making it possible to exchange data with at least one server implementing said MQIsdp protocol, so as to allow interconnection between said server (s) and the or said remote equipment via said radiocommunication means, without requiring knowledge of said MQIsdp protocol in said remote equipment.

2. remote equipment control system according to claim 1, characterized in that, at least in a first mode, said radiocommunication means manage only the signaling of a data exchange, said data being transferred directly from a remote equipment to a server, or vice versa.

3. remote equipment control system according to any one of claims 1 and 2, characterized in that, at least in a second mode, said radiocommunication means manage the signaling of a data exchange and the transfer of said data, the latter being temporarily stored in at least one buffer memory.

4. Remote equipment control system according to claim 3, characterized in that the size of the said buffer memory (s) is configurable.

5. Remote equipment control system according to claims 2 and 4, characterized in that it operates in said first mode when the size of the or said buffer memories is 0, and in said second mode otherwise.

6. remote equipment control system according to any one of claims 1 to 5, characterized in that said radiocommunication means comprise a radiocommunication module, grouping on a same substrate all of the radio data processing means -frequency and baseband, as well as the means for managing said AT commands.

7. Remote equipment control system according to any one of claims 1 to 6, characterized in that said radiocommunication means integrate said MQIsdp protocol in the form of an "Open-AT" application, defining said set of specific AT commands.

8. Remote equipment control system according to any one of claims 1 to 7, characterized in that said set of specific AT commands comprises commands allowing:

- connection to one of said servers; - sending messages;

- receiving messages.

9. Remote equipment control system according to any one of claims 1 to 8, characterized in that at least some of said specific AT commands are organized so as to be able to perform at least two functions and / or act on the at least two distinct aspects, depending on a predefined setting.

10. Remote equipment control system according to any one of claims 1 to 9, characterized in that said set of commands comprises only 8 commands.

11. Remote equipment control system according to any one of claims 1 to 10, characterized in that said set of specific AT commands comprises a configuration command making it possible to define the parameters of the communication with one of said servers.

12. Remote equipment control system according to claim 11, characterized in that it implements a single configuration command. (+ WSPGSET) for the configuration of the radiocommunication aspects and the general configuration of the aspects related to the MQIsdp protocol.

13. Remote equipment control system according to any one of claims 11 and 12, characterized in that said configuration command makes it possible to select a transmission mode from at least two (GSM and

GPRS).

14. Remote equipment control system according to any one of claims 1 to 13, characterized in that it implements three configuration commands: - a command for general configuration of the communication

(+ WSPGSET);

- a command to configure a connection (+ WSPCSET), making it possible to specify in particular the coordinates of a server;

- a configuration command for the “will” configuration message (+ WSPWMS), making it possible to specify in particular the channel for which a message is intended.

15. Remote equipment control system according to any one of claims 1 to 14, characterized in that it implements at least one general communication command, allowing the transmission and / or reception of messages according to the MQIsdp protocol.

16. Remote equipment control system according to claim 15, characterized in that it implements five general communication commands:

- a command to specify an MQIsdp context (+ WSPDCONT);

- a command to manage a connection with a server (+ WSPCONM);

- a command to send a message (+ WSPSMSG);

- a command to receive a message (+ WSPRMSG); - an administration command, allowing zeroing and / or a return to the default values of a set of parameters (+ WSPPA).

17. Remote equipment control system according to any one of claims 1 to 16, characterized in that it implements at least one interrogation command by an external application.

18. Remote equipment control system according to claim 17, characterized in that it implements two interrogation commands by an external application, respectively on:

- the current state of the connection (+ WSPICON); - receiving and / or sending a message (+ WSPIMSG).

19. A method of controlling remote equipment, allowing interconnection between at least one server and at least one remote equipment according to the MQIsdp protocol, characterized in that it associates with at least one of said remote equipment radiocommunication means capable to issue and receive AT type commands issued by and / or intended for an external application implemented by said remote equipment, and in that it implements, in said radiocommunication means, a set of AT commands specific for exchanging data with at least one server implementing said MQIsdp protocol, so as to allow interconnection between said server (s) and said remote equipment (s) via said radiocommunication means, without requiring additional processing means and / or data formatting in said remote equipment.

20. Radiocommunication device characterized in that it comprises radiocommunication means implemented in a remote equipment control system according to any one of claims 1 to 18.

21. Radiocommunication module characterized in that it comprises radiocommunication means implemented in a remote equipment control system according to any one of claims 1 to 18.

22. AT command set implemented in a remote equipment control system, characterized in that it makes it possible to exchange data with at least one server implementing said MQIsdp protocol.