METHOD, APPARATUS, AND COMPUTER PROGRAM PRODUCT FOR REDUCING SESSION RELATED MESSAGE SIZE
First Claim
1. A method comprising steps of:
- identifying data a first field and a second field for a message header of a message to be sent in a protocol in which the first field is for data identifying a message sequence associated with the message and the second field is for a tag associated with an identifier of a source or a recipient of the message; and
generating the message such that at least one of the first or second fields of the message header for the message is without data, and data is included in a third field of the message header, the data in the third field comprising at least a domain-wide unique identifier that is based at least in part on the data identified for the at least one of the first or second fields that is without data.
1 Assignment
0 Petitions
Accused Products
Abstract
An apparatus for reducing session related message size includes a processing element. The processing element may be configured to determine a domain-wide unique identifier and generate a message including a first field for identifying a message sequence associated with the message and a second field including a tag. The second field including the tag may be associated with an identifier of a source or recipient of the message. At least one of the first and second fields may be without data. The processing element may be further configured to include, in the message, a third field comprising at least the domain-wide unique identifier. The third field may be associated with data otherwise intended for the first and second fields.
5 Citations
28 Claims
-
1. A method comprising steps of:
-
identifying data a first field and a second field for a message header of a message to be sent in a protocol in which the first field is for data identifying a message sequence associated with the message and the second field is for a tag associated with an identifier of a source or a recipient of the message; and generating the message such that at least one of the first or second fields of the message header for the message is without data, and data is included in a third field of the message header, the data in the third field comprising at least a domain-wide unique identifier that is based at least in part on the data identified for the at least one of the first or second fields that is without data. - View Dependent Claims (2, 3, 4, 5, 17, 18, 19)
-
-
6-11. -11. (canceled)
-
12. A method comprising steps of:
-
receiving a message in a protocol in which a header includes a first field for an identifier of a message sequence associated with the message and a second field for a tag associated with an identifier of a source or a recipient of the message; and when at least one of the first or second fields of the header of the received message is without data; extracting a domain-wide unique identifier from a third field of the header of the received message, the domain-wide unique identifier being associated with an identifier of the message sequence associated with the message and a tag associated with an identifier of the source or the recipient of the message otherwise intended for the first and second fields, respectively, of the header of the received message; and interpreting the header of the received message by inserting the domain-wide unique identifier into each of the first and second fields of the header of the message that is received without data. - View Dependent Claims (13, 14, 20, 21, 22, 23, 24)
-
-
15-16. -16. (canceled)
-
25. An apparatus comprising:
-
communication interface; and a processor coupled to the communication interface, wherein the processor is configured to control operation of the apparatus to implement functions, including functions to; identify data for a first field and a second field for a message header of a message to be sent in a protocol in which the first field is for data identifying a message sequence associated with the message and the second field is for a tag associated with an identifier of a source or a recipient of the message; generate the message such that at least one of the first or second fields of the message header for the message is without data, and data is included in a third field of the message header, the data in the third field comprising at least a domain-wide unique identifier that is based at least in part on the data identified for at least one of the first or second fields that is without data; and send the generated message via the communication interface. - View Dependent Claims (26, 27, 28)
-
Specification