# Patent

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

## Abstract

A system is provided 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. The system associates at least one of the remote pieces of equipment with radio communication device that emits and receives AT-type commands issued by and/or addressed to an external application which is used by the distance piece of equipment. The radio communication device is 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 the remote piece/s of equipment can be interconnected via the radio communication device without the distant pieces of equipment having to know the MQIsdp protocol.

## Background
CROSS-REFERENCE TO RELATED APPLICATION
This Application is a Section 371 National Stage Application of International Application No. PCT/FR2004/001499, filed Jun. 16, 2004 and published as WO 2004/114625 A2 on Dec. 29, 2004, not in English.
STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
None.
THE NAMES OF PARTIES TO A JOINT RESEARCH AGREEMENT
None.
FIELD OF THE DISCLOSURE
The domain of the disclosure is remote control of equipment, and particularly equipment with limited data processing resources. Thus, the disclosure is applicable for example to remote data recording systems, for example on water, gas or electricity meters, and more generally to telemetry, order monitoring and more generally Machine to Machine (M to M) systems.
BACKGROUND OF THE DISCLOSURE
Many solutions already exist for performing such operations. They have generally been developed specifically for a given application. In other words, they are “proprietary” solutions that are difficult to adapt to other applications.
There is also a protocol developed by the IBM and ARCOM Control Systems companies (registered trademarks), known as the “MQIsdp Messaging” technology. This technique proposes a communication protocol between one or several items of equipment with limited resources, and one or several servers, using a TCP/IP link.
SUMMARY OF THE DISCLOSURE
However, even with this specific protocol, special processing means (microprocessors, memories, etc.) have to be added to the equipment so as to set up a dialog with these remote servers, depending on the required MQIsdp format. The connection between the equipment and the server may use a telephone type link using a modem.
However, in many applications, it would be desirable to be able to manage without a wire telephone link. In this case, radiocommunication means could be envisaged, for example according to the GSM or GPRS standard.
In this case, radiotelephone equipment would be used to perform the modem function. However, according to prior art, it is necessary to associate special and proprietary data processing means with the equipment to set up and exchange data with the server.
This aspect is a very important limitation to the development of the applications mentioned above, and to many other applications with which the MQIsdp protocol could be used.
SUMMARY
One particular aspect of an embodiment of the invention is to overcome this disadvantage with prior art.
It should be noted that the fact that this problem has been identified is itself part of an embodiment of the invention. At least some of those skilled in the art are convinced that it is absolutely necessary to equip terminal equipment with sufficient processing means, and will never consider reducing or eliminating these processing means.
However, one aspect of an embodiment of the invention is to simplify the processing in the equipment, and to avoid the need for this equipment to have complex and expensive means such as a microprocessor.
Another aspect of an embodiment the invention is to propose a simple and generic technique to easily and efficiently set up a dialog with a server using the MQIsdp protocol.
Yet another aspect of an embodiment of the invention is to provide such a technique for setting up a connection between servers and equipment by radiotelephone link in a simple, standardised and inexpensive manner.
Another aspect of an embodiment of the invention is to provide such a technique to develop a large number of applications, without it being necessary to develop specific applications each time.
Another aspect of an embodiment of the invention is to provide such a technique in which there is no need to know the MQIsdp protocol in the developed applications.
Yet another aspect of an embodiment of the invention is to provide such a technique that is technically simple and upgradeable and adaptable to various situations (for example the amount of data to be exchanged) and to any future changes that are made.
These aspects and others that will appear more clearly in the following, are achieved using a system for remote control of equipment enabling interconnection between at least one broker and at least one remote equipment using the MQIsdp protocol.
According to an embodiment of the invention, radiocommunication means capable of sending and receiving AT type commands sent by and/or sent to an external application used by the said remote equipment are associated with at least one of the said remote equipment, the said radiocommunication means being provided with a set of special AT commands for exchanging data with at least one broker using the said MQIsdp protocol, so as to enable an interconnection between the said server(s) and the said remote equipment through the said radiocommunication means, without requiring knowledge of the said MQIsdp protocol in the said remote equipment.
Thus, it is easy and simple to manage data exchanges without the need to develop special applications or to associate important means (particularly microprocessor and memory) with a terminal. Neither the terminal nor the application needs to know the MQIsdp protocol. The radiocommunication means manage these aspects. The application only needs to know the new AT commands.
Advantageously, at least in a first mode, the said radiocommunication means only manage signalling of a data exchange, the said data being transferred directly from remote equipment to a server, or vice versa.
Preferably, at least in a second mode, the said radiocommunication means manage signalling of a data exchange and transfer of the said data, the data being temporarily stored in at least one buffer memory.
In this case, the size of the said buffer memory(ies) can advantageously be parameterable.
According to one advantageous embodiment, the said system operates in the said first mode when the size of the said buffer memory(ies) is equal to 0, and otherwise in the said second mode.
Thus, a simple and efficient means is obtained for performing two functions (mode selection and queue sizing) with a single command.
In one advantageous embodiment of the invention, the said radiocommunication means comprise a radiocommunication module comprising all radio frequency and base band processing means on the same substrate, together with means of managing the said AT commands.
In particular, the said radiocommunication means can include the said MQIsdp protocol in the form of an “open-AT” application defining the said set of special AT commands.
Advantageously, the said set of special AT commands includes commands for:

    
    
        connecting to one of the said servers;
        sending messages;
        receiving messages.
    
    


Preferably, at least some of the said special AT commands are organized so as to be able to perform at least two functions and/or to act on at least two distinct aspects, as a function of a predefined configuration.
This can strongly reduce the number of necessary commands, while performing all necessary operations taking account of any future developments.
Thus in one preferred embodiment, the said set of commands only includes 8 commands.
The said set of special AT commands advantageously includes at least one configuration command used to define communication parameters with one of the said servers.
Preferably, the system uses a single configuration command (+WSPGSET) for configuration of radiocommunication aspects and the general configuration of aspects related to the MQIsdp protocol.
In particular, the said configuration command can be used to select one of at least two transmission modes (GSM or GPRS).
Advantageously, the system uses three configuration commands:

    
    
        a general communication configuration command (+WSPGSET);
        a connection configuration command (+WSPCSET), particularly used to specify the coordinates of a server;
        a configuration command for the “will” configuration message (+WSPWMS), particularly to specify the channel to which a message will be sent.
    
    


Preferably, it also uses at least one general communication command for sending and/or receiving messages using the MQIsdp protocol.
Thus, five general communication commands can advantageously be used:

    
    
        a command for specifying an MQIsdp context (+WSPDCONT);
        a command for managing a connection with a server (+WSPCONM);
        a command for sending a message (+WSPSMSG);
        a command for receiving a message (+WSPRMSG);
        an administration command, used to do a reset and/or return to the default values of a set of parameters (+WSPPA).
    
    


Advantageously, it also uses at least one query command by an external application, preferably two query commands by an external application, on the following in turn:

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


An embodiment of invention also relates to the method for remote control of equipment used by a system as described above. It enables interconnection between at least one server and at least one remote equipment according to the MQIsdp protocol by associating at least one of the said remote items with radiocommunication means capable of sending and receiving AT type commands sent by and/or to be sent to an external application used by the said remote equipment, and by using a set of special AT commands in the said radiocommunication means for exchanging data with at least one server using the said MQIsdp protocol. This enables an interconnection between the said server(s) and the said remote equipment through the said radiocommunication means, without requiring additional processing and/or data formatting means in the said remote equipment.
An embodiment of invention also relates to radiocommunication devices and modules comprising radiocommunication means used in such an equipment remote control system.
A further embodiment of the invention relates to sets of AT commands used in an equipment remote control system, used to exchange data with at least one server using the said MQIsdp protocol.
Other special features and advantages of one or more embodiments of the invention will become clearer after reading the following description of a preferred embodiment of the invention, given as a simple illustrative and non-limitative example and appended figures.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 shows an example of a system in which an embodiment of the invention could be used;
FIG. 2 shows an example of how the MQIsdp protocol can be integrated in an Open-AT application; and
FIGS. 3A to 3L show different example embodiments of a connection according to embodiments of the invention.



DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS
1. Reminders about the MQIsdp Protocol (Registered Trademark)
The MQIsdp (WebSphere MQ Integrator SCADA device protocol) is an open standard developed by IBM and Arcom Control Systems (registered trademarks), to enable data exchanges (in the form of messages) from generally inexpensive remote devices (or terminals) with little processing power, to a WebSphere MQ Integrator by TCP/IP server, also called a broker in the following, and vice versa.
MQIsdp (also called Wavecom SCADA in the following) is a data (message) transfer protocol based on a publish/subscribe type communication model freely available on Internet. It may be described as being a simple agnostic data management layer above the TCP/IP protocol, for message management and acknowledgements of reception necessary to assure reliable delivery of the message.
In the publish/subscribe communication model, data are exchanged between a data producer/consumer (the client) and a message broker (the server). The message broker may be considered as being a multi-protocol switching hub for the application protocol that receives the messages, and it transforms them, reformats them, etc. into other structures as a function of a data model defined by the user.
Finally, any transformed messages may be sent (published) by the broker to subscriber clients (zone device, ERP, SAP, Oracle, SQL, etc.) using appropriate client cards. Obviously, the broker can also publish messages that do not originate from a client.
The message broker manages all messages input to and output from an item. A client publishes messages in/with an item or subscribes to messages from/by an item identifying the message flow from the message broker to which or from which the message is to be published.
The MQIsdp specification defines a set of very simple messages including “connect”, “disconnect”, “publish”, “subscribe”, and “unsubscribe”.
2. Principles of an Embodiment of the Invention
2.1 General
Therefore, one or more embodiments of the invention relate to a new approach for remote control of equipment, particularly based on the use of a set of special AT type commands, enabling an external application to manage data exchanges between a remote terminal and a server, through radiocommunication links (for example a Wismo type (registered trademark) module), without the application knowing the MQIsdp protocol used by the server. This aspect is managed by radiocommunication means, and for example acknowledgements described in the MQIsdp protocol.
FIG. 1 is a simplified illustration of the principle of an embodiment of the invention. The objective is to have any type of remote machine, for example measurement instruments 11, communicate with one or several applications hosted on servers 12, capable of receiving data 13 using the MQIsdp protocol, and to transform, process or transmit these data.
According to this embodiment, the remote terminals (or machines) 11 are associated with radiocommunication means 14, for example in the form of a Wismo module (registered trademark) particularly embedding development tools distributed by the applicant under the “Muse platform” trademark).
2.2 Module Concept
As a reminder, it should be noted that most radiocommunication devices conventionally comprise a set of electronic components arranged on a printed circuit. These various components are designed to perform the various necessary functions, from reception of a RF signal until generation of an audible signal (in the case of a radiotelephone) and vice versa. Some of these functions are analogue and others are digital.
Manufacturing of these radiocommunication devices is an important subject of research. Three objectives are aimed at, that are difficult to reconcile: miniaturising devices, increasing features and simplifying assembly. It is known that installation of different components on a printed circuit is a relatively complex operation, since many components have to be arranged on a very restricted surface area, due to miniaturization requirements.
Therefore, the design of these systems is complex, since it also requires a combination of various components, often from multiple sources, that have to be made to operate together, respecting the specific features of each. Furthermore, after assembling the set of components, calibration and test phases that are frequently long and complex are necessary to guarantee correct operation of the device.
Finally, despite the reduction in size of some components, the assembly occupies a certain surface area that is difficult to reduce.
The holder of this patent application has proposed a method of overcoming some of these disadvantages, consisting of grouping all or at least some of the functions of a digital radiocommunication device in a single module.
Such a module is in the form of a single compact housing, preferably shielded, that device manufacturers can integrate directly without needing to take account of a multitude of components.
This module (also sometimes called a “macro-component”) is actually formed by grouping several components on a substrate, so as to be implanted in the form of a single element. It includes essential components and software necessary for operation of a communication terminal using radio-electrical frequencies. Therefore, there is no longer a set of complex steps for the conceptual design and validation of this terminal. All that is necessary is to reserve the space necessary for the module.
Therefore, such a module can be used to easily and quickly integrate all components into wireless terminals in an optimised manner (portable telephones, modems or any other application using a wireless standard).
Furthermore, since this module contains all essential functions and has been designed as a complete unit, calibration and test problems no longer arise in the same manner, or are at least very much simplified.
Thus, modules distributed by the holder of this patent application are fully tested both in terms of hardware and software on most networks on which they could be used later. Furthermore, the module advantageously encompasses industrial proprietary aspects (since all functions have been grouped together, the module manufacturer manages the corresponding patent right aspects) and technical support aspects.
2.3 AT Commands
The principle of using AT commands is already known. For example, it is described in patent document FR-99 13645, and in various specifications distributed by the applicant and that can be referred to for further information if necessary.
2.4 New AT Commands
This module 14 is capable of managing a small number of simple AT commands, enabling a simple and efficient dialog with an external application associated with a terminal. It makes the transformation to the MQIsdp format and manages sending and receiving of data 15 using this protocol, in a manner transparent for the application.
Thus, the data exchange can be made using radio waves 16, for example according to the GSM or GPRS standard. Seen from the server 12, information is in the MQIsdp format. There is no need for terminals 11 to know this protocol, they only need to know a few AT commands. It is thus easy and inexpensive to implement an external application at low cost in (or adjacent to) a terminal without the need to provide a microprocessor and memories, and a dedicated application.
As will be seen later, the proposed AT commands may be limited to 8, although they can be upgraded.
Two data transfer modes are proposed:

    
    
        data transit through the module 14. These data are temporarily stored in buffers (buffer memories), the size of which can be configured as a function of needs;
        data are transmitted directly between the terminal and the server, without being stored in memory in the module 14, the module 14 only managing all signalling aspects (opening and closing of the connection, acknowledgements, etc.).
    
    


The first case could correspond to the most frequent case of small messages, and the second case to the transfer of large files, as is allowed for in the MQIsdp protocol. It is thus possible to manage everything through the module, without adding any external memory and intelligence, while enabling data transfers with a volume greater than the storage capacity of the module.
Advantageously, a single command can be used for sizing of buffers and changing from one mode to the other (the second mode corresponding to a zero value).
FIG. 2 shows a simplified example of a software architecture that could be used in the module 14.
Such a module 14 usually comprises:

    
    
        a basic software layer 21 (Wavecom Core SoftWare);
        an Open AT library 22;
        an ADL library 23;
        a TCP/IP library 24;
        an application layer 25 (Open AT Application).
    
    


According to an embodiment of the invention, a library 26 of special commands (Wavecom SCADA Protocol Library) is provided to communicate using the MQIsdp protocol that is above the TCP/IP library 24.
The AT commands 27 address either the base layer 21, the TCP/IP library 24 or the SCADA library 26 depending on the case.
The proposed interface using AT commands includes only 8 commands in this library 26, capable of fully controlling the MQIsdp protocol and particularly:

    
    
        possibility of sizing two internal queues for managing incoming and outgoing messages;
        possibility of outsourcing management of large messages;
        definition of connection contexts;
        management of configuration parameters;
        management of sending different types of messages by generic command.
    
    


3. Detailed Description of an Embodiment of Commands
The following describes AT commands that could be used to control the Wavecom SCADA protocol 26.
3.1 Related Documents
If necessary, the following documents provide useful information:
[1] This document should be read with the “WebSphere MQ Integrator SCADA Device Protocol” datasheet given in Appendix B of the “IBM WebSphere MQ Integrator Programming Guide” reference manual available at the following address:
http://publifp.boulder.ibm.com/epubs/odf/bipval04.pdf
[2] Wavecom AT Commands Interface Guide
Reference: WM_SW_OAT_IFS—001-revision: 009 or more recent versions.
This document describes AT commands managed by the Wavecom product to manage related GSM events or services.
[3] AT Command Interface for TCP/IP
Revision: 1.7
This document describes the parameters and the set of AT commands for configuration and control of superposition of TCP/IP and 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 managing all AT commands so that related GSM events or services can be managed.
3.2.2 Definitions
The terms MS and ME are used for mobile terminals handling GSM services. The word “product” refers to any Wavecom product (particularly a module) handling the AT commands interface.
Symbols:
<CR> carriage return character
<LP> line feed character
[ . . . ] optional parameter of an AT command
< . . . > Parameter name between angle brackets. The angle brackets do not appear on the command line.
3.3 AT Command Syntax
This section defines the format of AT commands, and mechanisms for assignment of default values of their parameters.
3.3.1 Command Line
Commands always begin with the standard “AT+WSP” prefix and finish with the <CR> character.
Optional parameters are indicated between square brackets [ ].
For example: AT+WSPCmd=<Param1>[,<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 <CR><LF> (except for the format of the ATVO DCE response) and ATQ1 commands (deletion of result code) (see the related document [2]).
If the command syntax is incorrect, the command is returned to the Wavecom central software for processing. In this case, the Wavecom central software returns the “ERROR” message.
If the command syntax is correct but incorrect parameters have been transmitted, the <CR><LF>+WSP ERROR: <Err><CR><LF> response is returned together with appropriate error codes.
If the command line was executed successfully, the <CR><LF>“OK”<CR><LF> string is returned.
3.4 Configuration Commands
Different parameters are necessary to provide the Wavecom product with all information about the initial connection:

    
    
        The support network used: GSM or GPRS
        Timeout parameters
        The functional mode of superposition of the Wavecom SCADA protocol
        All necessary information about the support network so that a TCP/IP infrastructure can be accessed
        The “Will” configuration message for the connection.
    
    


3.4.1+WSPGSET General Parameters
a—Description
This command is used to configure all parameters used to select the support network, the different timeouts and the functional mode of the Wavecom SCADA protocol.
b—Syntax











Command
Possible responses







AT + WSPGSET =
OK


<Mode>[,<Paramid> [<Value>]]
Or


Note: configures or lists all
+WSPGSET: <Paramid>, <Value>


general parameters.
OK



Or



+WSPGSET: <Paramid1>, <Value>



+WSPGSET: <Paramid2>, <Value>



. . .



+WSPGSET: <Paramid11>,



<Value> OK



Or



Error codes



+WSP ERROR: 4000



+WSP ERROR: 4001


AT + WSPGSET?
OK


Note: no action


AT + WSPGSET?
+WSPGSET: (list of <Mode> handled),


Note: possible values
(range of <Paramid> values handled)



OK









c—Defined Values














<Mode>
02
Execution mode



0
Assigns the value indicated by <Value> to the




parameter defined by <Parameterid>



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 contains the list of the




various parameters.

























Parameter



Value by


Paramid
name
Description
Format
Specifications
default




















1
(BearerSet)
Select
Numeric
0-1
0




GSM/GPRS

0 GSM (ISP






parameters






are used for a






connection)






1 GPRS






(APN






parameters






are used for a






connection)


2
<Watchdog>
Number of
Numeric
(0-1000)
0




seconds




before the




connection




is




interrupted




after a given




period with




no traffic.




The value 0




is used to




indicate that




the




exchange




monitoring




circuit is




missing.


3
<RedialCount>
Number of
Numeric
(0-5)
0




unsuccessful




connection




attempts




before




terminating




the




connection




attempts




activity


4
<NotifyLevel>
Indication
Numeric
(0-3)
3




level about

0 No




events

notification




related to

1 Notify




connnections

connection




and/or

elements




messages as

2 Notify




unsolicited

message




responses

events




(see the

3 Notify all




chapter on

events




WSP




indications)


5
<OutBoxSize>
Size of the
Numeric
(0-32787)
32787




Outbox




queue in




bytes


6
<InBoxSize>
Size of the
Numeric
(0-32787)
32787




Inbox queue




in bytes


7
<ReadyMsgMode>
This
Numeric
(0-1)




parameter is

0 End of




used when

output




the value 0 is

(by <ctrl>P>




assigned to

Ctrl>C)




the Inbox

without the




queue. All

header




messages

(DUP, Qos,




sent by the

Retain, etc.)




broker are

1 End of




automatic-

output with




ally sent to

display of




the external

header




application




(see the




chapter on




WSP




indications)


8
<WillMsgTimer>
Number of
Numeric
(1-255)
5




seconds




waiting for




the “Will”




message




configuration




command


9
<RetryMsgDelay>
Number of
Numeric
(0-255)
1




milliseconds




to retry




sending a




message


10
<RetryMsgCount>
Number of
Numeric
(1-10)
0




unsuccessful




attempts to




send a




message




before the




send attempt




activity is




cancelled


11
<RetryMsgTimer>
Number of
Numeric
(1-233)
0




seconds




waiting for




reception of




a message









d—Possible Error Codes













+WSP ERROR 4000
Non-activated function of the Wavecom



SCADA protocol. This error is returned when



the function of the Wavecom SCADA



protocol has not been activated in the



WISMO module.


+WSP ERROR 4001
Illegal operation. This error is returned when



an incorrect parameter is detected.









e—Informative Examples











Command
Responses







AT + WSPGSET = 0,1,1
OK


Note: configures the support network
Note: GPRS selected


AT + WSPGSET = 0,4,2
OK


Note: configures the <NotifyLevel>
Note: only message events are


parameter
notified


AT + WSPGSET = 0,1,2
+WSP ERROR:4001


Note: configures a parameter with an
Note: illegal operation


incorrect value


AT + WSPGSET = 1,1
+WSPGSET:1,1


Note: reads the current value of the
OK


<BearerSet> parameter


AT + WSPGSET = 2
WSPGSET:1,0


Note: reads all current values
WSPGSET:2,0



WSPGSET:3,0



WSPGSET:4,3



WSPGSET:5,32767



WSPGSET:6,32767



WSPGSET:7,0



WSPGSET:8,5



WSPGSET:9,1



WSPGSET:10,0



WSPGSET:11,0



OK


AT+WSPGSET=?
+WSPGSET:(0-2),(1-111)


Note: possible values
OK









3.4.2 Connection Parameters +WSPCSET
a—Description
This command is used to configure all connection parameters (by family).
b—Syntax











Command
Possible responses







AT + WSPCSET = <Setting_type>,
OK


<param1> [,<param2> [,<param3>
+WSP ERROR:4000


[,<param4> [,<param5>]]]]]
+WSP ERROR:4001


Note: configures all connection


parameters.


AT + WSPCSET?
+WSPCSET = <Setting_type1>,


Note: current values of parameters
<param1>, <param2>,



<param3> [, . . .



[,<paramE>]]



<CR> <LF>



+WSPCSET = <Setting_type2>,



<param1>, <param2>,



<param3>[, . . . ],<paramE>]]



OK


AT + WSPCSET = ?
+WSPCSET:


Note: possible values
(list of <Setting_type>



managed



OK









c—Defined Values














<Settings_type> (0-1)
Parameter category









0
ISP parameters



1
APN parameters




















* IPS parameters (5 parameters) - Settings_type=0


These parameters are used when the GSM support network (given by circuit


switching) is selected. See the “Other parameters” section.












Generic




Default


parameter
Parameter
Description
Format
Specifications
value





<Param1>
<PhoneNumber>
ISP
Numeric
Maximum length
**




telephone
string
61




number


<Param2>
<UserName>
ISP
Alphanumeric
Maximum length
**




account
string
32




user name


<Param3>
<Password>
ISP
Alphanumeric
Maximum length
**




account
string
32




password


<Param4>
<DNS1>
Main DNS
Alphanumeric
IP address format
**




IP address
string
(1.1.1.1-






255.255.255.255)


<Param5>
<DNS2>
Secondary
Alphanumeric
IP address format
**




DNS IP
string
(1.1.1.1-




address

255.255.255.255)



















* APN parameters (3 parameters) - Settings_type=1


These parameters are used when the GPRS support


network is selected. See the “Other parameters” section.












Generic




Default


parameter
Parameter
Description
Format
Specifications
value





<Param1>
<APN>
APN from
Alpha-
Maximum
**




the GSM
numeric
length 64




operator to
string




supply the




GPRS




access


<Param2>
<UserName>
APN user
Alpha-
Maximum
**




name from
numeric
length 32




the GSM
string




operator to




supply the




GPRS




access


<Param3>
<Password>
APN
Alpha-
Maximum
**




password
numeric
length 32




from the
string




GSM




operator to




provide




access to




the GPRS









d—Possible Error Codes













+WSP ERROR 4000
Non-activated function of the Wavecom



SCADA protocol. This error is returned when



the function of the Wavecom SCADA



protocol has not been activated in the



WISMO module.


+WSP ERROR 4001
Illegal operation. This error is returned when



an incorrect parameter is detected.









e—Informative Examples











Command
Responses







AT + WSPCSET = 0,
OK


“+33612214629”,
Note: new ISP parameters recorded


“toto”, “secret”,


“1.2.3.4”, “5.6.7.8”


Note: configures all ISP parameters


AT + WSPCSET = 0,,,,“1.2.3.4”,
OK


“1.2.3.5”
Note: new parameters recorded


Note: Only configures the DNS1


and DNS2 parameters


AT+WSPCSET=0“,+33612214829”,
+WSP ERROR:4001


“toto”,“secret”,“256.2.3.4”,“0.0.0.0”
Note: illegal operation


Note: configures all parameters with


an incorrect parameter (DNS1)


AT + WSPCSET = 1, “Orange”,
OK


“toto”, “secret”
Note: new parameters recorded


Note: configures all APN parameters


AT + WSPCSET = 1,, “toto”,
OK


“secret”
Note: new parameters recorded


Note: only configures the


“UserName”


and “Password” parameters


AT + XSPCSET = 1, “Orange.fr”,
+WSP ERROR:4001


“toto”, 1
Note: illegal operation


Note: configures all parameters with


an incorrect parameter (Password:


password)


AT + WSPCSET?
+WSPCSET:0,“+ 33612214629”,


Note: current values
“toto”, “secret”,



“1.2.3.4”,“5.6.7.8”



+WSPCSET:1, “Orange.fr”,



“toto”, “secret”



OK



Note: range of values recorded


AT + WSPCSET = ?
+WSPCSET: (0-1)


Note: possible values
OK



Note: values managed









3.4.3 Parameters for the Will+WSPWMS message
a—Description
This command configures all parameters related to the Will message. This command returns +WSP ERROR: 4013 if the value 0 is assigned to the <OutBoxSize> parameter.
b—Syntax











Command
Possible responses







AT + WSPWMS = <Topic>
>


[,<Qos>[,<Retain>
Or


[,<PayloadLength>]]]<CR>,
Error code:


Enter <PayloadLength> the number of
+WSP ERROR:4000


bytes indicated by the <MsgLength>
+WSP ERROR:4001


parameter
+WSP ERROR:4002


Or


Enter <Payload> <Ctrl>P <Ctrl>C


when the <PayloadLength> parameter


is not defined


Note: configures all parameters in the


Will message.


AT + WSPWMS?
+WSPWMS: <Topic>,


Note: returns information from the Will
<Qos>, <Retain>


message
<CR> <LF> <Payload>



OK


AT + WSPWMS = ?
+WSPWMS: (maximum length


Note: possible values
of a <Topic>, (list of <Qos>



accepted), (list of 



<Retain> accepted),



(range of <PayloadLength>



accepted)



OK









c—Defined Values
















<Topic>
This string identifies the information channel




on which text data were published.




Maximum length = 64 characters



<Qos> (0-2)
Quality of service



0
Once maximum - <Fire and Forget>



1
At least once - Delivery with




acknowledgement of reception



2
Exactly once - Delivery guaranteed




Default value = 0



<Retain> (0-1)
Informs the broker that the message must be




retained and sent to any new subscriber to




this item as the 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 0 is




assigned to the <OutBoxSize> parameter,




this value is no longer limited (see the




+WSPGSET command section for further




information about the <OutBoxSize>




parameter).










d—Possible Error Codes













+WSP ERROR 4000
Non-activated function of the Wavecom



SCADA protocol.



This error is returned when the function of the



Wavecom SCADA protocol has not been



activated in the WISMO module.


+WSP ERROR 4001
Illegal operation. This error is returned when



an incorrect parameter is detected.


+WSP ERROR 4002
Operation not accepted by the current



configuration.









e—Informative Examples











Command
Responses







AT + WSPWMS = My Will Topic”, 0, 0
>


Note: Enters will information without
Note: wait for the end of the


the body length
text defined by



<ctrl>P<ctrl>C


My body will message fr
OK


Test <ctrl>P <ctrl>C
Note: text entered


Note: enter the text


AT + WSPWMS = “My Will Topic”, 0,
+WSP ERROR: 4001


10
Note: illegal operation


Note: enters will information with an


incorrect parameter (<Retain>)


AT + WSPWMS?
+WSPWMS:


Note: Reads all information about the
“My Will Topic”, 0.0


Will message
My body will message test



OK



Note: the connection is set up



with the broker


AT+XSPWMS=?
+WSPWMS:64, (0-2), (0-1),


Note: possible values
32767



OK





Note:


if the <ctrl>P command is present in the text, the <ctrl>P <ctrl>P escape command will have to be used.






3.5—General Commands
3.5.1—Definition of the WSP+WSPDCONT Context
a—Description
This command defines 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>, is used to delete a WSP context.
b—Syntax











Command
Possible responses







AT + WSPDCONT = <WSPCid>[,
OK


[<Clientid>], [<broker_Adr>],
+WSP ERROR: 4000


[<Port>],
+WSP ERROR: 4001


[<CleanStart_Flag>],


[<KeepAliveTimer>],


[<UseLWT_Flag>]]


Note: creates a new context


AT+WSPDCONT?
+WSPDCONT: <WSPCid1>,


Note: lists all created contexts
<Clientid1>, <Broker_Addr1>,



<Port1>,



<CleanStart_Flag1>,



<KeepAliveTimer1>,



<UseLWT_Flag1>,



+WSPDCONT:<WSPCid2>,



<Clientid2>, <Broker_Addr2>,



<Port2>,



<CleanStart_Flag2>,



<KeepAliveTimer2>,



<UseLWT_Flag2>,



OK


AT+WSPCONT=?
+WSPCONT: (list of <WSPCid>


Note: possible values
accepted), (max length of <Clientid>,



(max length of<Broker_Addr>),



(range of <Port> accepted), (list of



<CleanStart_Flag> accepted), (list of



<KeepAliveTimer> accepted), (list of



<UseLWT_Flag> accepted).



OK









c—Defined Values













<WSPCid> (1-2)
WSP context identifier: numeric parameter that



indicates a definition of a given WSP context.


<Clientid>
Client identifier for the Wavecom SCADA



protocol: string parameter that identifies the



client.



Maximum length = 23 characters



Default value = unreadable


<Broker_Addr>
Parameter on string (or IP address) that



identifies the broker server and



provides a means of reaching it.



Maximum length = 255 characters



Default value = unreadable


<Port> (0-65535)
Numeric parameter (broker port) used to



reach the broker server to transfer data.



Default values = 1883


<CleanStart_Flag> (0-1)
The client continues with the previous


0
connection data.


1
The broker cancels all pending messages for



the client, deletes all client subscriptions



and reassigns the value 1 to the message ID.



Default value = 0


<KeepAliveTimer>
Maximum interval between each


(0-32767)
client message.



The value 0 indicates that no connection



holding (KeepAlive) timeout processing



is made



Default value = 0


<UseLWT_Flag> (0-1)
Indicates if the Will message is used:


0
The Will message is not used


1
The Will message is used



Default value = 0









d—Possible Error Codes













+WSP ERROR 4000
Non-activated function of the Wavecom SCADA



protocol. This error is returned when the function



of the Wavecom SCADA protocol has not been



activated in the WISMO module.


+WSP ERROR 4001
Illegal operation. This error is returned when an



incorrect parameter is detected.









e—Informative Examples











Command
Possible responses







AT + WSPDCONT =
OK


1,1.“1.2.3.4”,1883,1.0.1
Note: context created


Note: creates a new


context


AT + WSPDCONT =
OK


2,1,“5,6,7,8”
Note: context created


Note: creates a new


context with default


parameters


AT + WSPDCONT = 2
OK


Note: deletes a context
Note: context deleted


AT + WSPDCONT =
+WSP ERROR:4001


10,1,“1.2.3.4”1883
Note: illegal operation


Note: creates a new


context with an


incorrect parameter


(Cid)


AT + WSPDCONT =
OK


2,1,“5,6,7,8”
Note: context created


Note: creates a new


context with default


parameters


AT + WSPDCONT?
+WSPDCONT:1,1,“1.2.3.4”,1883,1,0,1


Note: lists all created
+WSPDCONT:2,1,“5.6.7.8”,1883,1,0,1


contexts
OK


AT+WSPDCONT?
+WSPDCONT:(1-2),23,255,


Note: possible values
(0-06535),(0-1),(0-32767),(0-1)



OK









3.5.2 +WSPCONM Connection Management
a—Description
This command manages the connection to a broker.
b—Syntax











Command
Possible responses







AT + WSPCONM = <Mode>
OK


[,<WSPCid>
Or


[,<CleanDisconnect>]]
Error codes:


Note: connection/disconnection
+WSP ERROR:4000


operations
+WSP ERROR:4001



+WSP ERROR:4003



. . .



+WSP ERROR:40010


AT+WSPCONM?
+WSPCONM:<Status> [,<WSPCid>]


Note: returns the connection status
OK


AT + WSPCONM = ?
+WSPCONM: (list of <Mode>


Note: possible values
accepted),



(list of WSPCid> accepted),



(list of <CleanDisconnect> accepted)



OK









c—Defined Values













<Mode> (0-1) 0
Disconnection of an active Wavecom SCADA



protocol session


1
Connection to the remote broker


2
Connection aborted


<WSPCid>
WSP context identifier: numeric parameter that



identifies the definition of a given WSP



context.


<CleanDisconnect> (0-1)
Disconnection mode


0
Disconnection takes place immediately, the



queue is emptied and all in-progress



transactions are deleted.


1
All queued messages (waiting or pending) are



processed before the disconnection.



Default value = 1


<Status> (0-2)
Connection status with the broker.


0
Not connected


1
Connected


2
Connection pending









d—Possible Error Codes













+WSP ERROR 4000
Non-activated function of the Wavecom



SCADA protocol. This error is returned when



the function of the Wavecom SCADA protocol



has not been activated in the WISMO module.


+WSP ERROR 4001
Illegal operation. 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 pending


+WSP ERROR 4006
Disconnection pending


+WSP ERROR 4007
Client not connected. This error is sent when a



disconnection is requested whereas the ME is



not connected


+WSP ERROR 4008
No network


+WSP ERROR 4009
No GPRS


+WSP ERROR 40010
No TCP/IP









e—Informative Examples











Command
Possible responses







AT + WSPCONM?
+WSPCONM:0


Note: obtains the current status of the
OK


connection
Note: the module is not



connected to the broker.


AT + WSPCONm=1,1
OK


Note: connection operation with WSP1
Note: connection operation


context
started


AT + WSPCONM?
+WSPCONM:2,1


Note: obtains the current status of the
OK


connection
Note: connection operation



pending


AT + WSPCONM = 1,2
+WSP ERROR: 4004


Note: another connection is requested
Note: operation not managed


AT + WSPCONM?
+WSPCONM:1,1


Note: obtains the current status of the
OK


connection
Note: the connection is set



up with the broker


AT + WSPCONM = 0,0
OK


Note: disconnection with reset of


queues


AT + WSPCONM = ?
+WSPCONM:(0-1),(1-2),(0-1)


Note: possible values
OK









3.5.3—Send Message +WSPSMSG
a—Description
This command sends or obtains the status of several message types, and particularly Publish, Subscribe and Unsubscribe.
The specification of the Wavecom SCADA protocol enables a SUBSCRIBE/UNSUBSCRIBE message to send several subscriptions/unsubscriptions. The limit for this AT command is fixed at one item per SUBSCRIBE/UNSUBSCRIBE message. In this case, an application that wants to subscribe/unsubscribe from several items will send several SUBSCRIBE/UNSUBSCRIBE requests for a single item.
b—Syntax











Command
Possible responses







AT + WSPSMSG = <ActionType>
When a message is sent


[,<Param1> [,<Param2> [,<Param3>
+WSPSMSG: <MsgHandle>


[,<Param4> [,<Param5>
OK


[,<Param6>]]]<CR>
Or


Note: configures all message parameters
When a message status is



requested



+WSPSMSG: <Status>



OK



Or



Error code:



+WSP ERROR:4000



+WSP ERROR:4001



+WSP ERROR:4007



+WSP ERROR:40011


AT + WSPSMSG?
OK


Note: no effect


AT + WSPSMSG = ?
+WSPSMSG:


Note: possible values
(list of <ActionType> managed)



OK









c—Defined Values














<ActionType>
Operation type









0
Send a message



1
Obtain the message status




















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












Generic




Default


parameter
Context parameter
Description
Format
Specifications
value





<Param1>
<MsgType>
Message
Numeric
(3, 8, 10)
NA




identifier

 3 Publish






 8 Subscribe






10 Unsubscribe


<Param2>
<Topic>
String
Alphanumeric
Maximum length
**




indicating
string
64




the




information




channel on




which text




data are




sent


<Param3>
<QoS>
Quality of
Numeric
(0-2)
0




Service

0 - Fire and






forget






1 - Delivery with






acknowledgement






of reception






2 - Delivery






guaranteed


<Param4>
<Retain>
Notifies the
Numeric
(0-1)
0




broker that




the message




must be




kept and




must be




sent as the




initial




message to




any new




subscriber




to this item


<Param5>
<DupFlag>
Double
Numeric
(0-1)
0




indicating

0 - first send




message

1 - duplicated




used only if

message




OutBoxSize =




0


<Param6>
<PayLoadLength>
Maximum
Numeric
(*)
0**




length of




the message




body





(*) Maximum length of the message body. This value is limited by the value of the <OutBoxSize> parameter. If the value 0 is assigned to the <OutBoxSize> parameter, there is no limit (see the +WSPGSET command section for further information about the <OutBoxSize> parameter).






Note: if MsgType=10 (UNSUBSCRIBE), then

    
    
        only the <Topic> parameter is compulsory.
    
    


Else, if MsgType=8 (SUBSCRIBE) then

    
    
        the <Topic> and <QoS> parameters are used. If the <QoS> parameter is activated, then the default value is used.
    
    


Else, if MsgType=3 (PUBLISH) then

    
    
        all parameters are used. If the <QoS> and <Retain> parameters are omitted, the default values are used.
    
    


Then, assign the number of bytes indicated by the <PayLoadLength> parameter to the <Payload> parameter.
Or

    
    
        Enter <PayLoad> <Ctrl >P <Ctrl >C when the <PayLoadLength> parameter is omitted.
    
    












* Obtain the status (1 parameter) - ActionType = 1












Generic
Context
Descrip-

Specifi-
Default


parameter
parameter
tion
Format
cations
value





<Param1>
<MsgHandle>
Numeric.
Numeric
(0-32767)
NA




Identifies




the




message




















<Status>
Message status







W
WAITING. The message is queued, the transaction has not



begun.


P
PENDING. The message is queued. The transaction is in



progress.


N
Message cannot be found. The message is not in the queue.



Either the transaction is terminated, or the message was



never put in a queue.









d—Possible Error Codes













+WSP ERROR 4000
Non-activated function of the Wavecom



SCADA protocol. This error is returned when



the function of the Wavecom SCADA protocol



has not been activated in the WISMO module.


+WSP ERROR 4001
Illegal operation. This error is returned when



an incorrect parameter is detected.


+WSP ERROR 4007
Client not connected.


+WSP ERROR 40011
Queue saturated









e—Informative Examples











Command
Possible responses







AT + WSPSMSG=0,3. “My Publish
>


Topic”,0,0,0
Note: waits for the end of the text


Note: publishes a message
identified by <Ctrl>P <Ctrl>C


My body publish message for test
+WSPSMSG:1


<Ctrl>P <Ctrl>C
OK


Note: enter the Payload parameter
Note: the message is in the internal



queue or has been sent (if the



internal queue is not used)


AT + WSPSMSG = 1,1
+WSPSMSG:W


Note: obtains the message 1 status
OK



Note: message


AT + WSPSMSG=0,3. “My Publish
+WSP ERROR: 4001


Topic” 0,10,0
Note: illegal operation


Note: enter the Publish message with


an incorrect <Retain> parameter


AT + WSPSMSG = 0,8. “My
+WSPSMSG:2


Subscribe Topic”
OK


Note: Subscribe message in which the
Note: the message is in the internal


default value of the <QoS> parameter
queue or has been sent (if the


is used
internal queue was not used)


AT + WSPSMSG = 0,10, “My
+WSPSMSG:3


Unsubscribe Topic”
OK


Note: Unsubscribe message
Note: the message is in the internal



queue or has been sent (if the



internal queue was not used)


AT + WSPSMSG?
OK


AT + WSPSMSG=?
+WSPSMSG:(0,1)


Note: possible values
OK





Notes:


[1] If there is a <Ctrl>P in the text, the <Ctrl>P <Ctrl>P escape command has to be used.


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






When the value 0 is assigned to the <OutBoxSize> parameter, the <MsgHandle> parameter is set equal to the value 1 each time.
3.5.4—Reception of the +WSPRMSG Message
a—Description
This command is used to read a received message. The message is received with the +WSPIMSG indication.
The broker can send a PUBLISH message to the client on any item to which the client is subscribed. This AT command is used to obtain messages arrived in the InBox queue.
This AT command is only available if the value 0 is not assigned to the <InboxSize> parameter (see general parameters, +WSPGSET command). If the value 0 is assigned to the <InboxSize> parameter, messages are displayed with the +WSPIRMSG indication.
b—Syntax











Command
Possible responses







AT + WSPRMSG = <Msgid>[,<Mode>]
+WSPRMSG:<Msgid>


Note: receives a message from the Inbox
[,<Topic> [,<Dup>


queue
[,<QoS> [,<Retain>[,



DataLength>]]]]]



<CR> <LF>



<Data>



OK



Or



Error codes:



+WSP ERROR:4000



+WSP ERROR:4001



+WSP ERROR:4002



+WSP ERROR:40012


AT + WSPRMSG?
+WSPRMSG: <Msgid1>


Note: sends the list of messages in the
. . .


Inbox queue
+WSPRMSG: <Msgidn>



OK


AT + WSPRMSG = ?
+WSPRMSG: (range of


Note: possible values
<Msgid> accepted),



(list of <Mode> accepted)



OK









c—Defined Values













<Msgid> (0-32767)
Received message identifier


<Mode> (0-1)
Reception mode


0
Output terminated (by <ctrl>P <ctrl>C)



without the header (DUP, QoS, Retain, etc.)


1
Output terminated and header displayed









d—Possible Error Codes













+WSP ERROR 4000
Non-activated function of the Wavecom



SCADA protocol. This error is returned when



the function of the Wavecom SCADA protocol



has not been activated in the WISMO module.


+WSP ERROR 4001
Illegal operation. This error is returned when



an incorrect parameter is detected.


+WSP ERROR 4002
Operation not managed by the current



configuration.


+WSP ERROR 40012
Message cannot be found









e—Informative Examples











Command
Possible responses







AT + WSPRMSG?
+WSPCONM:8


Note: obtains the list of
OK


messages appearing in the InBox
Note: there is a message in the InBox


queue


AT + WSPRMSG = 8,3
+WSP ERROR: 4001


Note: obtains the message with
Note: illegal operation


an incorrect <Mode> parameter.


AT + WSPRMSG = 8,1
+WSPRMSG=8, “Topic Test”,1,0,1,20


Note: obtains the message with
Receive Message test<CR> <LF> OK


the associated header
OK



Note: connection operation started


AT + WSPRMSG?
OK


Note: obtains the current status
Note: there is no message in the InBox


of the connection


AT + WSPRMSG = 10,2
+WSP ERROR: 4012


Note: obtains the message with
Note: message cannot be found


the associated header


AT + WSPRMSG?
+WSPRMSG: (0-32767),(0-2)


Note: possible values
OK









3.5.5 +WSPPA Protocol Administration
a—Description
This command makes a general reset in the various queues or restores the default values of all parameters.
b—Syntax











Command
Possible responses







AT + WSPPA = <ActionType>
OK


Note: performs an action
Or



Error codes:



+WSP ERROR: 4000



+WSP ERROR: 4001



+WSP ERROR: 4002


AT + WSPPA?
OK


Note: no effect.


AT + WSPPA = ?
+WSPPA: (range of <Action> handled)


Note: possible values
OK









c—Defined Values











<ActionType>(0-1)
Action type







0
RESET. Empties the queue and interrupts all



transactions in progress.


1
DEFAULT PARAMETERS. All default



values of parameters of AT commands are



restored. This action is only possible when



not connected.









d—Possible Error Codes













+WSP ERROR 4000
Non-activated function of the Wavecom



SCADA protocol. This error is returned when



the function of the Wavecom SCADA



protocol has not been activated in the



WISMO module.


+WSP ERROR 4001
Illegal operation. This error is returned when



an incorrect parameter is detected.


+WSP ERROR 4002
Operation not accepted by the current



configuration.









e—Informative Examples











Commands
Possible responses







AT + WSPPA = 0
OK


Note: empties all queues and interrupts
Note: reset done.


all transactions in progress.


AT + WSPPA = 2
+WSP ERROR: 4001


Note: perform an action with an
Note: illegal operation


incorrect <ActionType> parameter


AT + WSPPA?
OK


Note: no effect


AT + WSPPA = ?
+WSPPA: (0-1)


Note: possible values
OK









3.6 WSP Indications
This chapter describes all event responses for sent messages.
3.6.1 +WSPDCONI Connection Indications
A connection indication mechanism (+WSPCONI) is set up so that the external application can determine the connection status.
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 terminated


1
The connection with the broker is set up


2
The connection with the broker is refused


3
Protocol version not handled


4
Identifier rejected by the broker


5
Will message configuration necessary. This indication is returned



only when the +WSPWMS command was not configured before the



connection.


6
Allocated time for configuration of the Will message exceeded.



Connection not set up.









3.6.2 +WSPSMSGI Message Send Indications
A (+WSPSMSGI) message indications mechanism is set up so that the external application can determine if the message is received or if a message has been sent.
These indications are sent when the value 2 or 3 is assigned to the <NotifyLevel> parameter (see the +WSPGSET command) and if the value 32767 is assigned to the <InboxSize> parameter.












  Syntax: + WSPSMSGI: <Status>,<Msgid>


  <Status>


0 The <Msgid> message has been distributed (QoS>0)


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


  <Msgid>








  (0-32767)
Message identifier









3.6.3 +WSPRMSGI Message Reception Indications
If the Inbox size (<InboxSize>) is zero (0), messages are displayed with the +WSPRMSGI indication as soon as they are received.
These indications are sent when the value 2 or 3 is assigned to the <NotifyLevel> parameter (see +WSPGSET command) and when the value 0 is assigned to the <InboxSize> parameter.
The message header and/or the payload are displayed as a function of the +WSPGSET RecMsgMode parameter.















Syntax: +WSPRMSGI: <Status>[, <Msgid>[, <Topic>, <Dup>, <QoS>,







<Retain>, <Length> <CR> <LF>









<Data>]]



<Status>










0
<WMsgid> message received in the Inbox



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



2
Inbox saturated



3
No message reception capacity



4
Message terminated



5
Incorrect message









<Msgid>
(0-32767)
Received message identifier


<Topic>

Message item string


<Dup>
(0-1)
Double indicator (for QoS 1 and 2)


<QoS>
(0-2)
Quality of Service for this message


<Retain>
(0-1)
Memorisation indicator (Retain)








<Length>
(0-Outbox size)



Payload length


<Data>
Message data









3.7 Error Codes
This chapter describes all error codes returned by WSP AT commands.











Error code
Meaning







+WSP ERROR: 4000
Non-activated function of the Wavecom SCADA



protocol. This error is returned when the function



of the Wavecom SCADA protocol has not been



activated in the WISMO module.


+WSP ERROR: 4001
Illegal operation. This error is returned when an



incorrect parameter value has been used.


+WSP ERROR: 4002
Operation not handled by the current



configuration.


+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


+WSP ERROR: 4008
No network


+WSP ERROR: 4009
No GPRS


+WSP ERROR: 40010
No TCP/IP


+WSP ERROR: 40011
Queue saturated


+WSP ERROR: 40012
Message cannot be found


+WSP ERROR: 40013
Connection refused by the broker


+WSP ERROR: 40014
Connection refused due to a protocol version not



handled


+WSP ERROR: 40015
Connection refused: identifier rejected by the



broker









4. Examples
This section gives examples of the use of all AT commands in the Wavecom SCADA protocol described above. These examples are shown in FIGS. 3A to 3K respectively.
In these figures, the information is presented using a format well known to those skilled in the art, clearly showing data exchanges between the various entities (server or broker, module and external application). The fourth column shows which commands are used, and their meaning when applicable.
It does not seem necessary to add further comments on these figures, those skilled in the art will be capable of interpreting them directly.
The following aspects are presented:
4.1 Receiving a message with QoS 0

    
    
        4.1.1 With an Inbox (FIG. 3A)
        4.1.2 Without an Inbox (FIG. 3B)
    
    


4.2 Receiving a message with QoS 1

    
    
        4.2.1 With an Inbox (FIG. 3C)
        4.2.2 Without an Inbox (FIG. 3D)
    
    


4.3 Receiving a message with QoS 2

    
    
        4.3.1 With an Inbox (FIG. 3E)
        4.3.2 Without an Inbox (FIG. 3F)
    
    


4.4 Sending a message with QoS 0

    
    
        4.4.1 With an Outbox (FIG. 3G)
        4.4.2 Without an Outbox (FIG. 3H)
    
    


4.5 Sending a message with QoS 1

    
    
        4.5.1 With an Outbox (FIG. 3I)
        4.5.2 Without an Outbox (FIG. 3J)
    
    


4.6 Sending a message with QoS 2

    
    
        4.6.1 With an Outbox (FIG. 3K)
        4.6.2 Without an Outbox (FIG. 3L)
    
    


4.7 Comments
In these various figures, it can be seen that the external application does not need to know the MQISdp protocol (PUBLISH, PUBREC, PUBREL, PUBCOM commands, etc.), all it needs to know are the AT commands described above.
The module makes the interface transparently. Programming of the module to make this interface is obvious, firstly from the specifications given above, and secondly from the specifications for the MQIsdp protocol.
Although the present invention has been described with reference to preferred embodiments, workers skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the invention.

## Claims

1. System for remote control of equipment enabling interconnection between at least one server and at least one remote equipment, said at least one server carrying out the MQIsdp protocol, where MQIsdp represents an MQSeries Integrator SCADA Device Protocol, where SCADA represents Supervisory Control and Data Acquisition,
wherein the system associates, with said at least one remote equipment, radiocommunication means comprising:
sending and receiving means for exchanging specific Attention Commands (AT commands) sent by and/or to be sent to an external application used by said at least one remote equipment, wherein said specific AT commands comprise commands for:
connecting to said at least one server;
sending messages to said at least one server;
receiving messages from said at least one server;


communication means for exchanging data with said at least one server according to said MQIsdp protocol;
interface means for making an interface between said specific AT commands and said MQIsdp protocol, so as to enable an interconnection between said at least one server and said at least one remote equipment without requiring knowledge of said MQIsdp protocol in said at least one remote equipment;
and wherein, in at least a first mode, said radiocommunication means only manage signalling of a data exchange, said data being transferred directly from said at least one remote equipment to said at least one server, or vice versa.

2. System for remote control of equipment according to claim 1, wherein in at least a second mode, said radiocommunication means manage signalling of a data exchange and transfer of said data, the data being temporarily stored in at least one buffer memory.

3. System for remote control of equipment according to claim 2, wherein the size of said at least one buffer memory is parameterable.

4. System for remote control of equipment according to claim 3, wherein the system operates in said first mode when the size of said at least one buffer memory is equal to 0, and otherwise in said second mode.

5. System for remote control of equipment according to claim 1, wherein said radiocommunication means comprise a radiocommunication module comprising all radio frequency and base band data processing means on the same substrate, together with means of managing said specific AT commands.

6. System for remote control of equipment according to claim 1, wherein said radiocommunication means include said MQIsdp protocol in the form of an “open-AT” application defining said specific AT commands.

7. System for remote control of equipment according claim 1, wherein at least some of said specific AT commands are organized so as to be able to perform at least two functions and/or to act on at least two distinct aspects, as a function of a predefined configuration.

8. System for remote control of equipment according claim 1, wherein said specific AT commands only includes 8 commands.

9. System for remote control of equipment according to claim 1, wherein said specific AT commands includes a configuration command used to define communication parameters with said at least one server.

10. System for remote control of equipment according to claim 9, wherein the system uses a single configuration command (+WSPGSET) for configuration of radiocommunication aspects and the general configuration of aspects related to the MQIsdp protocol.

11. System for remote control of equipment according to claim 8, wherein said configuration command can be used to select one of at least two transmission modes (GSM or GPRS).

12. System for remote control of equipment according to claim 1, wherein the system uses three configuration commands:
a general communication configuration command (+WSPGSET);
a connection configuration command (+WSPCSET), particularly used to specify the coordinates of said at least one server;
a configuration command for the “will” configuration message (+WSPWMS),
particularly to specify the channel to which a message will be sent.

13. System for remote control of equipment according to claim 1, wherein the system uses at least one general communication command for sending and/or receiving messages using the MQIsdp protocol.

14. System for remote control of equipment according to claim 13, wherein the system uses five general communication commands:
a command for specifying an MQIsdp context (+WSPDCONT);
a command for managing a connection with said at least one server (+WSPCONM);
a command for sending a message (+WSPSMSG);
a command for receiving a message (+WSPRMSG);
an administration command, used to do a reset and/or return to the default values of a set of parameters (+WSPPA).

15. System for remote control of equipment according to claim 1, wherein the system uses at least one query command by an external application.

16. System for remote control of equipment according to claim 15, wherein the system uses two query commands by an external application, on the following in turn:
the current state of the connection (+WSPICON);
reception and/or sending of a message (+WSPIMSG).

17. Device for remote control of equipment enabling interconnection between at least one server and at least one remote equipment, said at least one server carrying out the MQIsdp protocol, where MQIsdp represents an MQSeries Integrator SCADA Device Protocol, where SCADA represents Supervisory Control and Data Acquisition,
wherein the device associates, with said at least one remote equipment, radiocommunication means comprising:
sending and receiving means for exchanging specific AT commands sent by and/or to an external application used by said at least one remote equipment, wherein said specific AT commands comprise commands for:
connecting to said at least one server;
sending messages to said at least one server;
receiving messages from said at least one server;

communication means for exchanging data with said at least one server according to said MQIsdp protocol;
interface means for making an interface between said specific AT commands and said MQIsdp protocol, so as to enable an interconnection between said at least one server(s) and said at least one remote equipment, without requiring additional processing and/or data formatting means in said at least one remote equipment, and

wherein, in at least a first mode, said radiocommunication means only manage signalling of a data exchange, said data being transferred directly from said at least one remote equipment to said at least one server, or vice versa.

18. A radiocommunication device comprising radiocommunication means used in a system for remote control of equipment according to claim 1.

19. A radiocommunication module comprising radiocommunication means used in a system for remote control of equipment according to claim 1.

20. The system of claim 1, wherein the specific AT commands enable data exchange with said at least one server using said MQIsdp protocol.