Browse Prior Art Database

Method of Message Transport Reduction

IP.com Disclosure Number: IPCOM000021488D
Original Publication Date: 2004-Jan-21
Included in the Prior Art Database: 2004-Jan-21
Document File: 4 page(s) / 9K

Publishing Venue

IBM

Abstract

Sending data over a wireless connection can be both time consuming and expensive. This invention operates at the transport level, not the protocol or application level, to reduce the amount of data transported. The data reduction can be realized through the number of messages transported and the size of the messages transported through transporting only the selected and necessary message fields. Through transport layer data reduction, further cost savings can be realized in addition to the already known techniques of data reduction at other levels. While this invention deals with reducing the amount of data transported, this is not simple data compression, but there is nothing to preclude the use of data compression in conjunction with this invention to further realize the desired cost savings.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 35% of the total text.

Page 1 of 4

Method of Message Transport Reduction

Sending data over a wireless connection can be both time consuming and expensive. Frequently, wireless connections are billed on a per byte of data basis, so each byte that is sent over the air costs something; although each byte is relatively cheap, the number of bytes being sent can add up quickly. In addition to the costs of sending more bytes over a wireless connection, there is also a time cost associated with the additional bytes. More bytes take longer to be sent/received which slows down the users' progress and degrades overall usability of the device. To reduce or avoid all these costs, data reduction is desirable.

Known solutions operate at a different layer (protocol or application) than this invention (transport). This invention reduces the amount of data transported, but the protocol and application layer known solutions can still be used in conjunction with this invention. The currently known solutions are complements to this solution, not substitutes. Because transport layer message reduction is not currently being done, there is a chance to reduce the number of transmitted bytes at the transport layer as well as the other layers. This invention reduces the amount of data transmitted in two ways: 1) reducing the number of messages sent and 2) reducing the amount of data in each message.

The first approach to data reduction is through selective field requests. When a message is requested by the intended recipient, the intended recipient may request to only receive certain fields of the message - thereby eliminating fields/information it does not want or need for whatever process it would like to perform. Likewise, the intended recipient may request to only receive certain messages - thereby reducing the number of messages actually delivered. Instead of wasting time and money on sending information that the recipient does not want and will just ignore (whether it be certain messages or certain fields in those messages) , this invention allows the recipient to eliminate this unnecessary burden.

The transport mechanism can utilize any number of networking protocols as it operates at an abstraction layer that is higher than the networking protocols. Therefore, the networking protocol can be replaced or altered to use its own reduction mechanisms without affecting the current invention. The transport mechanism is application independent (it operates at a layer below the application layer) and can be used with any application that wants to pass messages to other applications, servers, etc.

The invention works by the intended recipient requesting the messages addressed to itself with flags indicating which fields of the messages it would like to receive. The fields can either be listed by which fields to include or which fields to exclude, presumably using whichever field list is shorter and thus saves bytes on the request for the messages. Example 1 shows how this invention can be used...