Wavecom W-RCI (Remote Control) V8.7.0 - Manual (Page 63)

XML SDK V8.7.0 Remote Control Interface TCP/IP Interface

55
build time
length of sw release
software release
length of card type
card type String
DWORD
String
DWORD
String
Label Permissions Bit Pattern
Connection Info Read (from Card) Permission Bit
Write (to Card) Permission Bit
Configure (Server) Permission Bit
Message Content Encryption Bit
Message Content Compression Bit 0x00000001
0x00000002
0x00000004
0x00000010
0x00000020
The server informs the client about the connection, the versions of the server and which card is used. The
connection information specifies which permissions the client have and how data is transferred. At present
there are no restrictions, though all the permission bits should be set except the encryption and compres-
sion bits, which should not be set. If they are set the server must be configured to no compression and no
encryption.
Error (Server

Client)
Label Data Data Type
Message ID 0x00100003
Data Length 292 Bytes
Data Content Error ID
Error Short Description
Error Description DWORD
32 Byte
256 Byte
Initialize (Client

Server)
Label Data Data Type
Message ID 0x00200000
Data Length > 28 Bytes
Data Content Length of user name
User name
Length of password
Password hashed
Major server version
Minor server version
Server build id
XML format
Minor XML version
Major XML version DWORD
STRING
DWORD
STRING
BYTE
BYTE
signed int (32 bit)
10 BYTE
WORD
WORD
XML format Header
Indent
Encoding
End-of-line type BYTE
BYTE
int (enum) (4 Bytes)
int (enum) (4 Bytes)
In a future release it is planned to implement authorization on the server, therefore the client has to au-
thorize itself during initialization. Currently an empty string has to be passed for user name and password,
which will be recognized as user “everyone”.
A check is done to ensure the client is compatible with the server. The actual check depends on the value
passed in the build id parameter. If the build id is less than zero a check is done for major and minor
server version compatibility, otherwise the check is done for build id equality. The client is considered
compatible with the server if the major versions are the same and the minor version of the server is high-
er than that of the client. The server recognizes and supports messages, which were defined in the same
major and the minor version up to and including the actual version. The same is true for the XML protocol
version.
The XML format parameter is used by the client to define how the XML messages from the server will be
formatted.
Header