System for efficient routing and translation of data

• US 6,507,874 B1
• Filed: 06/30/1998
• Issued: 01/14/2003
• Est. Priority Date: 01/07/1998
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kadyk, Don, Tuniman, David, Wecker, Dave, Deo, Vinay
• Primary Examiner(s): WINDER, PATRICE L
• Application Number:
  US09/107,899
• Time in Patent Office: 1,659 Days
• Field of Search: 709/238, 709/246, 709/247, 380/259, 380/262, 380/28, 380/29
• US Class Current: 709/247
• 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 recovery system is capable of recovering a core set of data from an input set of data. The input set of data is accompanied by a translator identifier and both items are received by a receiver in the recovery system. The receiver passes the input set of data to a message router that is capable of accessing a tag list based on the translator identifier before the recovery system has translated the input set of data. The message router is also capable of routing data based on the accessed tag list.

Claims

1. A recovery system, capable of recovering a core set of data from an input set of data, the input set of data accompanied by a translator identifier, the recovery system comprising:

a receiver, for receiving the input set of data and the translator identifier; and

a message router functionally coupled to the receiver and being capable of accessing a recovery tag list that is based on the translator identifier before the recovery system has translated the input set of data and being capable of routing data based on the recovery tag list identified by the receiver.

2. The recovery system of claim 1 wherein the translator identifier is a tag list accompanying the input set of data.

3. The recovery system of claim 2 wherein the receiver is a driver capable of identifying the recovery tag list based on the translator identifier and of rejecting the input set of data if the recovery system does not include a translator required by the recovery tag list before the message router is activated.

4. The recovery system of claim 3 wherein the message router is capable of rejecting the input set of data before the message router has routed data based on a portion of the recovery tag list.

5. The recovery system of claim 2 wherein at least one translator can determine if the tag list comprises return tag values indicative of a return tag list to be used to generate an output set of data in response to the core set of data.

6. The recovery system of claim 5 wherein the message router is further capable of rejecting the input set of data if the recovery system does not include a translator required by a return tag value in the return tag list.

7. The recovery system of claim 2 further comprising a memory for storing the tag list as a stored tag list, the stored tag list capable of being used to produce an output set of data in response to the core set of data.

8. The recovery system of claim 7 further comprising at least one output translator capable of producing an output set of data.

9. The recovery system of claim 1 further comprising a macro-tag translator, the macro-tag translator being capable of receiving both a set of data and the recovery tag list.

10. The recovery system of claim 9 wherein the macro-tag translator is capable of modifying the recovery tag list.

11. The recovery system of claim 10 wherein the macro-tag translator modifies the recovery tag list based on the tag values in the recovery tag list.

12. The recovery system of claim 10 wherein the macro-tag translator modifies the recovery tag list based on the input set of data.

13. The recovery system of claim 10 wherein the macro-tag translator modifies the recovery tag list based on the available translators in the recovery system.

14. The recovery system of claim 10 wherein the macro-tag translator modifies the recovery tag list based on the input set of data and the tag values in the recovery tag list.

15. The recovery system of claim 10 wherein the macro-tag translator modifies the recovery tag list based on applications stored on a same device as the recovery system.

16. The recovery system of claim 10 wherein the macro-tag translator modifies the recovery tag list using a tag table of tag values.

17. The recovery system of claim 1 further comprising a tag table, the tag table associating a single tag value with a set of tag values.

18. The recovery system of claim 1 wherein the translator identifier is a destination address for the core set of data in the recovery system.

19. The recovery system of claim 18 wherein the destination address comprises a primary address and a sub-address.

20. The recovery system of claim 19 wherein the receiver attempts to identify a tag list associated with the sub-address.

21. The recovery system of claim 20 wherein the receiver attempts to identify a tag list associated with the primary address if it cannot identify a tag list associated with the sub-address.

22. The recovery system of claim 21 wherein the receiver identifies a default tag list if it cannot identify a tag list associated with the primary address.

23. The recovery system of claim 21 wherein the message router identifies a default tag list if it cannot identify a tag list associated with the primary address.

24. The recovery system of claim 19 wherein the message router attempts to identify a tag list associated with the sub-address.

25. The recovery system of claim 20 wherein the message router attempts to identify a tag list associated with the primary address if it cannot identify a tag list associated with the sub-address.

26. The recovery system of claim 1 wherein the receiver identifies a tag list accompanying the input set of data as the recovery tag list if a tag list accompanies the input set of data but otherwise attempts to identify a tag list based on a destination address for the core set of data.

27. The recovery system of claim 1 wherein the message router identifies a tag list accompanying the input set of data as the recovery tag list if a tag list accompanies the input set of data but otherwise attempts to identify a tag list based on a destination address for the core set of data.

28. The recovery system of claim 1 wherein the recovery system resides on a wireless device.

29. A method of forming channel data from a core set of data comprising:

performing multiple translations on the core set of data in a sequential manner to form translated data;

creating a list of translations representative of the order and types of translations performed on the core set of data; and

concatenating the translated data with the list of translations to form the channel data.

30. The method of claim 29 further comprising, before concatenation, comparing the list of translations to a destination-based list of translations associated with a destination address for the channel data and not concatenating the list of translations if the list of translations matches the destination-based list of translations.