Computer-readable data structure for efficient routing and translation of data

• US 20030056011A1
• Filed: 10/11/2002
• Published: 03/20/2003
• Est. Priority Date: 01/07/1998
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Dave Wecker, David Tuniman, Don Kadyk, Vinay Deo
• Inventors: Deo, Vinay, Kadyk, Don, Tuniman, David, Wecker, Dave
• Granted Patent: US 7,143,192 B2
• Time in Patent Office: Days
• US Class Current: 709/246
• CPC Class Codes: G06F 1/3209 Monitoring remote activity, e.g. over telephone lines or network connections
• CPC Class Codes: G06F 40/103 Formatting, i.e. changing of presentation of documents automatic justification G06F40/189; automatic line break hyphenation G06F40/191
• CPC Class Codes: G06F 40/117 Tagging; Marking up details of markup languages G06F40/143; Designating a block; Setting of attributes style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154
• CPC Class Codes: G06F 40/123 Storage facilities
• CPC Class Codes: G06F 40/149 Adaptation of the text data for streaming purposes, e.g. Efficient XML Interchange [EXI] format
• CPC Class Codes: G06F 40/151 Transformation
• CPC Class Codes: G06F 40/197 Version control for software G06F8/71
• CPC Class Codes: H04L 49/90 Buffering arrangements
• CPC Class Codes: H04L 49/901 using storage descriptor, e.g. read or write pointers
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 63/02 for separating internal from external traffic, e.g. firewalls
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/0263 Rule management
• CPC Class Codes: H04L 63/04 for providing a confidential data exchange among entities communicating through data packet networks
• CPC Class Codes: H04L 63/064 Hierarchical key distribution, e.g. by multi-tier trusted parties
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 1/2757 : by data transmission, e.g. downloading
• CPC Class Codes: H04M 1/72406 : by software upgrading or downloading
• CPC Class Codes: H04M 1/72412 : using two-way short-range wireless interfaces
• CPC Class Codes: H04W 12/03 : Protecting confidentiality, e.g. by encryption
• CPC Class Codes: H04W 28/06 : Optimizing the usage of the radio link, e.g. header compression, information sizing , discarding information system modifying transmission characteristic according to link quality by modifying frame length H04L1/0007; dynamic adaptation of the packet size for flow control or congestion control H04L47/365
• CPC Class Codes: H04W 4/12 : Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 88/023 : with message or information receiving capability

Abstract

A data structure in a computer-readable form is provided that includes a string construct and a data construct. The string construct is formed by translations of a string of values. The tag construct is concatenated to the string construct and includes at least one tag value. The tag construct represents at least two translations that were performed on the string of values to produce the string construct.

Claims

1. A data structure in a computer readable form, the data structure comprising:

a string construct formed by translations of a string of values; and

a tag construct concatenated with the string construct, the tag construct comprising at least one tag value, the tag construct representing at least two translations performed in translating the string of values into the string construct.

2. The data structure of claim 1 wherein each translation is represented by a separate tag value.

3. The data structure of claim 1 wherein a single tag value represents multiple translations.

4. The data structure of claim 1 wherein the tag construct further comprises return tag values, the return tag values together representing at least two translations performed in translating a return string of values into a return string construct.

5. The data structure of claim 4 wherein at least one tag value indicates that the tag construct includes return tag values.

6. The data structure of claim 1 wherein one tag value represents the number of tag values in the tag construct.

7. The data structure of claim 1 wherein a tag value is one byte long.

8. The data structure of claim 1 wherein a tag value comprises multiple bytes, the first byte of the tag having a value indicating the number of bytes in the tag value, all of the tag'"'"'s bytes including the fist byte, together representing the complete tag value.

9. The data structure of claim 8 wherein at least one tag value is two bytes long.

10. The data structure of claim 8 wherein at least one tag value is three bytes long.

11. The data structure of claim 1 wherein at least one tag value comprises a first byte that indicates that the tag value includes a description of the tag value'"'"'s length, and a second byte that describes the tag value'"'"'s length.