User Manual

Table Of Contents
SARA-R4/N4 series-AT Commands Manual
UBX-17003787 - R11
18Internet protocol transport layer
Page 192 of 308
Type Syntax Response Example
supported <remote_port>s),(list of
supported <length>s),"HEX data"
+USOST: (list of supported
<socket>s),"remote_host",(list of
supported <remote_port>s),(list of
supported <length>s),"data"
+USOST: (list of supported
<socket>s),"remote_host",(list of
supported <remote_port>s),(list of
supported <length>s)
OK
+USOST: (0-6),"remote_host",(1-
65535),(0-1024),"data"
+USOST: (0-6),"remote_host",(1-
65535),(0-1024)
OK
18.11.3Defined values
Parameter Type Description
<socket> Number Socket identifier. The range goes from 0 to 6
<remote_addr> String Remote host IP address or domain name of the remote host. For IP address format
reference see the IP addressing.
<remote_port> Number Remote host port, in range 1-65535
<length> Number Number of data bytes to write
Base syntax normal mode: range 1-1024
Base syntax HEX mode: range 1-512
Binary syntax mode: range 1-1024
<data> String Data bytes to be written (not all of the ASCII charset can be used)
18.11.4Notes
For base syntax:
o The value of <length> and the actual length of <data> must match
o For base syntax HEX mode, only ASCII characters 0-9, A-F and a-f are allowed. The length of the
<data> parameter must be two times the <length> parameter
For binary syntax:
o After the command is sent, the user waits for the @ prompt. When it appears the stream of bytes
can be provided. After the specified amount of bytes has been sent, the system returns with final
result code. The feed process cannot be interrupted i.e. the return in the command mode can be
effective only when the number of bytes provided is the declared one
o That binary extended syntax is the only way for the system to accept control characters as data; for
the AT command specifications [16], characters like <CR>, <CTRL-Z>, quotation marks, etc. have
a specific meaning and they cannot be used like data in the command itself. The command is so
extended with a specific acceptance state identified by the @ prompt
o This feature can be successfully used when there is need to send a byte stream which belongs to a
protocol that has any kind of characters in the ASCII range [0x00,0xFF]
o In binary mode the module does not display the echo of data bytes
o Binary syntax is not affected by HEX mode option