IP Library Granted Patent US 8,799,351
Granted Patent B1
US 8,799,351 · App. 11/015,619 · Granted Aug 5, 2014

Communicating multiple files in markup language documents

Inventors: William D. Compton (Huntington Beach, CA); David J. Trott (El Segundo, CA); Navin Goel (Torrance, CA); Randall Ehler (Culver City, CA)
Assignee: Glovia International, Inc.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,799,351
App. No.
11/015,619
Granted
Aug 5, 2014
Kind
B1
Abstract

A communication system includes a number of devices interconnected by a communication network and each operable to communicate with each other using a text-based communication protocol that provides for the exchange of markup language documents. Each of the devices includes a document interface capable of generating, transmitting, receiving, and processing markup language documents including multiple files.

Claims (74)

1. A method for communicating multiple files in a single markup language document, comprising:

receiving electronic data for delivery to a destination address;

receiving an electronic file associated with the electronic data;

generating a first markup language document including the electronic data;

storing both the first markup language document and the electronic file in a payload of a second markup language document;

generating a header for the second markup language document, the header identifying the existence of both the first markup language document and the electronic file in the payload, the header comprising at least one parameter indicative of one or more relationships between the first markup language document and the electronic file in the payload; and

transmitting the second markup language document including the header and the payload to the destination address using a communication network.

2. The method of claim 1 , further comprising:

receiving a second electronic file associated with the electronic data;

storing the second electronic file in the payload;

modifying the header to identify the existence of the second electronic file in the payload; and

transmitting the second markup language document including the modified header and the payload to the destination address using the communication network.

3. The method of claim 1 , further comprising:

generating a pointer for the first markup language document, the pointer identifying a key stored in the second markup language document;

generating the key for the second markup language document, the key identifying data in the electronic file;

storing the pointer in the first markup language document; and

storing the key in the second markup language document.

4. The method of claim 1 , further comprising:

receiving a first inbound markup language document including an inbound header and an inbound payload;

determining that the inbound header identifies both a second inbound markup language document and an inbound electronic file in the inbound payload;

accessing the second inbound markup language document in the inbound payload; and

accessing the inbound electronic file in the inbound payload.

5. The method of claim 4 , further comprising:

extracting inbound electronic data from the second inbound markup language document;

identifying a first application for processing the inbound electronic data;

transmitting the inbound electronic data to the first application for processing;

identifying a second application for processing the inbound electronic file; and

transmitting the inbound electronic file to the second application for processing.

6. The method of claim 1 , wherein both the first markup language document and the second markup language document conform to a public standard for text-based markup language communications.

7. The method of claim 6 , wherein the standard is an extensible markup language (XML) standard.

8. The method of claim 1 , wherein the electronic file conforms to a public or private format for sharing information.

9. The method of claim 8 , wherein the format is portable document format (PDF).

10. A device for communicating multiple files in a single markup language document, comprising:

one or more processors for executing a document interface, the document interface operable to receive electronic data for delivery to a destination address, to receive an electronic file associated with the electronic data, to generate a first markup language document including the electronic data, to store both the first markup language document and the electronic file in a payload of a second markup language document, to generate a header for the second markup language document, the header identifying the existence of both the first markup language document and the electronic file in the payload, the header comprising at least one parameter indicative of one or more relationships between the first markup language document and the electronic file in the payload, and to transmit the second markup language document including the header and the payload to the destination address using a communication network.

11. The device of claim 10 , the document interface further operable to receive a second electronic file associated with the electronic data, to store the second electronic file in the payload, to modify the header to identify the existence of the second electronic file in the payload, and to transmit the second markup language document including the modified header and the payload to the destination address using the communication network.

12. The device of claim 10 , the document interface further operable to generate a pointer for the first markup language document, the pointer identifying a key stored in the second markup language document, to generate the key for the second markup language document, the key identifying data in the electronic file, to store the pointer in the first markup language document, and to store the key in the second markup language document.

13. The device of claim 10 , the document interface further operable to receive a first inbound markup language document including an inbound header and an inbound payload, to determine that the inbound header identifies both a second inbound markup language document and an inbound electronic file in the inbound payload, to access the second inbound markup language document in the inbound payload, and to access the inbound electronic file in the inbound payload.

14. The device of claim 13 , the document interface further operable to extract inbound electronic data from the second inbound markup language document, to identify a first application for processing the inbound electronic data, to transmit the inbound electronic data to the first application for processing, to identify a second application for processing the inbound electronic file, and to transmit the inbound electronic file to the second application for processing.

15. The device of claim 10 , wherein both the first markup language document and the second markup language document conform to a public standard for text-based markup language communications.

16. The device of claim 15 , wherein the standard is an extensible markup language (XML) standard.

17. The device of claim 10 , wherein the electronic file conforms to a public or private format for sharing information.

18. The device of claim 17 , wherein the format is portable document format (PDF).

19. A non-transitory computer readable medium encoding logic for communicating multiple files in a single markup language document, the logic operable when executed to:

receive electronic data for delivery to a destination address;

receive an electronic file associated with the electronic data;

generate a first markup language document including the electronic data;

store both the first markup language document and the electronic file in a payload of a second markup language document;

generate a header for the second markup language document, the header identifying the existence of both the first markup language document and the electronic file in the payload, the header comprising at least one parameter indicative of one or more relationships between the first markup language document and the electronic file in the payload; and

transmit the second markup language document including the header and the payload to the destination address using a communication network.

20. The non-transitory computer readable storage medium of claim 19 , further operable when executed to:

receive a second electronic file associated with the electronic data;

store the second electronic file in the payload;

modify the header to identify the existence of the second electronic file in the payload; and

transmit the second markup language document including the modified header and the payload to the destination address using the communication network.

21. The non-transitory computer readable storage medium of claim 19 , further operable when executed to:

generate a pointer for the first markup language document, the pointer identifying a key stored in the second markup language document;

generate the key for the second markup language document, the key identifying data in the electronic file;

store the pointer in the first markup language document; and

store the key in the second markup language document.

22. The non-transitory computer readable storage medium of claim 19 further operable when executed to:

receive a first inbound markup language document including an inbound header and an inbound payload;

determine that the inbound header identifies both a second inbound markup language document and an inbound electronic file in the inbound payload;

access the second inbound markup language document in the inbound payload; and

access the inbound electronic file in the inbound payload.

23. The non-transitory computer readable storage medium of claim 22 , further operable when executed to:

extract inbound electronic data from the second inbound markup language document;

identify a first application for processing the inbound electronic data;

transmit the inbound electronic data to the first application for processing;

identify a second application for processing the inbound electronic file; and

transmit the inbound electronic file to the second application for processing.

24. The non-transitory computer readable storage medium of claim 19 , wherein both the first markup language document and the second markup language document conform to a public standard for text-based markup language communications.

25. The non-transitory computer readable storage medium of claim 24 , wherein the standard is an extensible markup language (XML) standard.

26. The non-transitory computer readable storage medium of claim 19 , wherein the electronic file conforms to a public or private format for sharing information.

27. The non-transitory computer readable storage medium of claim 26 , wherein the format is portable document format (PDF).

Assignments (4)
CORRECTIVE ASSIGNMENT TO CORRECT THE RECEIVING PARTY DATA TO CORRECT ADDRESS PREVIOUSLY RECORDED AT REEL: 058812 FRAME: 0589. ASSIGNOR(S) HEREBY CONFIRMS THE CHANNGE OF NAME. Recorded Feb 7, 2022
From: FUJITSU GLOVIA, INC.
To: CRESCENTONE INC.
Reel/Frame 058960/0940 →
CHANGE OF NAME Recorded Jan 21, 2022
From: FUJITSU GLOVIA, INC.
To: CRESCENTONE INC.
Reel/Frame 058812/0589 →
CHANGE OF NAME Recorded Oct 6, 2016
From: GLOVIA INTERNATIONAL, INC.
To: FUJITSU GLOVIA, INC.
Reel/Frame 040242/0010 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 17, 2004
From: COMPTON, WILLIAM D.; TROTT, DAVID J.; GOEL, NAVIN; EHLER, RANDALL
To: GLOVIA INTERNATIONAL, INC.
Reel/Frame 016110/0547 →