# US 2009/0276451 A1 · Method and apparatus for processing messages

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2009/0276451 A1
- Document ID: US20090276451A1
- Status: Published application
- Kind: A1
- Application number: 12/121,193
- Filed: 2008-05-15
- Published: 2009-11-05
- Earliest claimed: 2008-05-05
- Assignees: Sensinode Oy
- Inventors: Zach SHELBY; Mikko Saarnivala
- Web page: https://patentgrep.com/patent/US20090276451A1

## CPC

- H04L 67/56: Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54)
- H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561)
- H04L 69/085: specially adapted for interworking of IP-based networks with other networks
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An apparatus and a method for transforming Simple Object Access Protocol (SOAP) messages is provided. The method comprises receiving and transmitting Extensible Markup Language (XML) format SOAP messages by using an application protocol and TCP/IP, a message comprising message elements and receiving and transmitting binary messages comprising binary message elements. A transformation is performed between an XML format message and a binary message by replacing (316-320) each message element of a given format with a message element in the other format. When transforming an XML message to binary format, the application protocol packet type and TCP/IP acknowledgement data are included (312) in the binary header. When transforming a binary format message to XML format, the application protocol packet type is selected on the basis of the information in the binary header of the binary format message.

## Claims

### Claim 1

An apparatus, configured to
receive and transmit Extensible Markup Language (XML) format Simple Object Access Protocol (SOAP) messages by using an application protocol and transmission control protocol/internet protocol (TCP/IP), a message comprising message elements;
receive and transmit binary messages comprising a binary header and binary message elements;
perform a transformation between an XML/SOAP format message and a binary message by replacing each message element of a given format with a message element in the other format;
include, when transforming an XML/SOAP message to binary format, the application protocol packet type and TCP/IP acknowledgement data in the binary header; and
select, when transforming a binary format message to XML/SOAP format, the application protocol packet type and response code on the basis of the information in the binary header of the binary format message.

### Claim 2 (depends on 1)

The apparatus of claim 1, further configured to include, when transforming an XML/SOAP message to binary format, the namespace used and the version number of the encoding in the binary message.

### Claim 3 (depends on 1)

The apparatus of claim 1, further configured to utilize lookup tables in the transformation.

### Claim 4 (depends on 3)

The apparatus of claim 3, further configured to
determine a SOAP namespace used in the message and select lookup tables on the basis of the SOAP namespace.

### Claim 5

The apparatus of any preceding claim, further configured to transmit the transformed message to a desired destination.

### Claim 6

The apparatus of any preceding claim, further configured to
receive an XML format Simple Object Access Protocol (SOAP) messages comprising message elements;
compress the XML format message to a binary SOAP message by encoding the namespace used and the version number of the encoding in a binary header, encoding the application protocol packet type and TCP/IP acknowledgement data in the binary header, replacing each XML message element with a binary message element indicated by a lookup table, and
transmit the binary SOAP message comprising binary message element to a desired destination.

### Claim 7 (depends on 6)

The apparatus of claim 6, further configured to
compress headers of the XML format message to binary {header type, value} tuples, wherein the values for the header type of the tuples are selected on the basis of lookup tables and the value fields of the tuples are selected on the basis of the values in the XML format message.

### Claim 8 (depends on 6)

The apparatus of claim 6, further configured to
indicate the number of message elements of the SOAP message as a binary number after the compressed headers in the binary message.

### Claim 9 (depends on 6)

The apparatus of claim 6, further configured to
compress each message element by
indicating the message element code, number of tags in the message element and the length of the message element and
compressing each tag as tuples comprising tag code, data type and data value.

### Claim 10

The apparatus of any preceding claim, further configured to
receive a binary SOAP message comprising binary message elements;
decode the namespace used and the version number of the encoding from the binary header of the message;
decompress the binary SOAP message to an XML format message by replacing each binary message element with an XML message element indicated by a lookup table;
select the application protocol packet type and response code on the basis of the information in the binary header of the binary SOAP message; and
transmit the XML format SOAP messages comprising message elements.

### Claim 11

The apparatus of any preceding claim, further configured to respond to a binary format SOAP put message by sending a binary acknowledgement message to the sender of the binary message.

### Claim 12

The apparatus of any preceding claim, further configured to respond to a binary format SOAP message which is to be decompressed by sending a binary acknowledgement message to the sender of the binary message.

### Claim 13

The apparatus of any preceding claim, further configured to transmit the binary SOAP message by using User Datagram Protocol (UDP).

### Claim 14

The apparatus of any preceding claim, further configured to transmit the binary SOAP message by utilising one of the following transmission technologies:
IEEE 802.15.4 with Internet Protocol v6 (6lowpan),
IEEE 802.15.4 with ZigBee,
Bluetooth
Bluetooth Ultra Low Power
Low Power Wireless Local Area Network.

### Claim 15 (depends on 4)

The apparatus of claim 4, the apparatus comprising a memory for storing lookup tables.

### Claim 16 (depends on 15)

The apparatus of claim 15, further configured to update lookup tables from a remote server if a lookup table for the determined namespace is not stored in the memory of the apparatus.

### Claim 17

The apparatus of any preceding claim, configured to receive and transmit Extensible Markup Language (XML) format Simple Object Access Protocol (SOAP) messages by using the Hypertext Transfer Protocol (HTTP).

### Claim 18 (depends on 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16)

The apparatus of any preceding claim 1 to 16, configured to receive and transmit Extensible Markup Language (XML) format Simple Object Access Protocol (SOAP) messages by using Session Initiation Protocol (SIP).

### Claim 19

The apparatus of any preceding claim, further configured to include, when transforming an XML/SOAP message to binary format, the namespace used and the version number of the encoding in the binary header.

### Claim 20

A method, comprising
receiving and transmitting Extensible Markup Language (XML) format Simple Object Access Protocol (SOAP) messages by using an application protocol and transmission control protocol/internet protocol (TCP/IP), a message comprising message elements;
receiving and transmitting binary messages comprising binary message elements;
performing a transformation between an XML/SOAP format message and a binary message by replacing each message element of a given format with a message element in the other format;
including, when transforming an XML/SOAP message to binary format, the application protocol packet type and TCP/IP acknowledgement data in the binary header; and
selecting, when transforming a binary format message to XML/SOAP format, the application protocol packet type and response code on the basis of the information in the binary header of the binary format message.

### Claim 21 (depends on 20)

The method of claim 20, further comprising: including, when transforming an XML/SOAP message to binary format, the namespace used and the version number of the encoding in the binary message.

### Claim 22 (depends on 20)

The method of claim 20, further comprising: utilizing lookup tables in the transformation.

### Claim 23 (depends on 22)

The method of claim 22, further comprising:
determining a SOAP namespace used in the message and selecting lookup tables on the basis of the SOAP namespace.

### Claim 24

The method of any preceding claim, further comprising:
transmitting the transformed message to a desired destination.

### Claim 25

The method of any preceding claim, further comprising
receiving an XML format Simple Object Access Protocol (SOAP) messages comprising message elements;
compressing the XML format message to a binary SOAP message by encoding the namespace used and the version number of the encoding in a binary header, encoding the application protocol packet type and TCP/IP acknowledgement data in the binary header, replacing each XML message element with a binary message element indicated by a look up table, and
transmitting the binary SOAP message comprising a binary message element to a desired destination.

### Claim 26

The method of any preceding claim, further comprising
compressing headers of the XML format message to binary {header type, value} tuples, wherein the values for the header type of the tuples are selected on the basis of lookup tables and the value fields of the tuples are selected on the basis of the values in the XML format message.

### Claim 27

The method of any preceding claim, further comprising
receiving a binary SOAP message comprising binary message elements;
decoding the namespace used and the version number of the encoding from the binary header of the message;
decompressing the binary SOAP message to an XML format message by replacing each binary message element with an XML message element indicated by a look up table;
selecting the application protocol packet type and response code on the basis of the information in the binary header of the binary SOAP message; and
transmitting the XML format SOAP messages comprising message elements.

### Claim 28

The method of any preceding claim, further comprising:
responding to a binary format SOAP put message by sending a binary acknowledgement message to the sender of the binary message.

### Claim 29

The method of any preceding claim, further comprising:
responding to a binary format SOAP message which is to be decompressed by sending a binary acknowledgement message to the sender of the binary message.

### Claim 30

The method of any preceding claim, further comprising: storing lookup tables in a memory.

### Claim 31 (depends on 30)

The method of claim 30, further comprising: updating lookup tables from a remote server if a lookup table for the determined namespace is not stored in the memory.

### Claim 32

The method of any preceding claim, wherein the application protocol is Session Initiation Protocol (SIP).

### Claim 33 (depends on 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31)

The method of any preceding claim 20 to 31, wherein the application protocol is the Hypertext Transfer Protocol (HTTP).

### Claim 34 (depends on 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31)

A computer program product encoding a computer program of instructions for executing a computer process carrying out the method according to any of claims 20 to 31.

### Claim 35 (depends on 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29)

A computer program distribution medium readable by a computer and encoding a computer program of instructions for executing a computer process carrying out the method according to any of claims 18 to 29.

### Claim 36 (depends on 35)

The computer program distribution medium of claim 35, the distribution medium including at least one of the following media: a computer readable medium, a program storage medium, a record medium, a computer readable memory, a computer readable software distribution package, a computer readable signal, a computer readable telecommunication signal, and a computer readable compressed software package.

### Claim 37

An apparatus, comprising:
means for receiving and transmitting Extensible Markup Language (XML) format Simple Object Access Protocol (SOAP) messages by using an application protocol and transmission control protocol/internet protocol (TCP/IP), a message comprising message elements;
means for receiving and transmitting binary messages comprising a binary header and binary message elements;
means for performing a transformation between an XML/SOAP format message and a binary message by replacing each message element of a given format with a message element in the other format;
means for including, when transforming an XML/SOAP message to binary format, the application protocol packet type and TCP/IP acknowledgement data in the binary header; and
means for selecting, when transforming a binary format message to XML/SOAP format, the application protocol packet type and response code on the basis of the information in the binary header of the binary format message.

### Claim 38

An apparatus, configured to
receive and transmit binary Simple Object Access Protocol (SOAP) messages comprising a binary header and binary message elements, the binary header comprising an application protocol packet type and transmission control protocol/internet protocol (TCP/IP) acknowledgement data.
