Application-level, persistent packeting apparatus and method

• US 5,946,467 A
• Filed: 11/07/1996
• Issued: 08/31/1999
• Est. Priority Date: 09/20/1996
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Lowry, Dale A., Fletcher, Samuel F., Pathakis, Scott W.
• Primary Examiner(s): Rinehart, Mark H.
• Application Number:
  US08/745,900
• Time in Patent Office: 1,027 Days
• Field of Search: 370/474, 370/389, 395/200.58, 395/200.54, 395/200.3, 395/200.6, 395/200.66
• US Class Current: 709/236
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC
• 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

Abstract

A persistent packet provides a wrapper that may be interpretable by an application, a packeting process, a database engine, or a device intermediate a sending device and a receiving device. Accordingly, the packet may be transferred and stored without changing the packet structure. The wrapper contains a header for rapid transfer of the packet with no need for any machine or process to open the packet and access the substantive data contained therein. The wrapper also contains application-specific data that may be interpreted by the packeting process or the application, or both. The application-specific data pertains to the substantive data contained in the packet and may be used by an application in determining how to dispose of a packet. For example an application may determine whether to store, open, discard, etc. the packet. The application-specific data may also be used by an application in a process of disposition of a packet. Both the header and application-specific data in the wrapper may be persistent across processes and apparatus. An application may "sub-contract" packeting to a separate packeting process, yet the application remains the "owner" of the packet.

Claims

1. An apparatus for transferring and storing data in a packet adapted to be persistent throughout transfer, the apparatus comprising:

a processor hosting an application containing a first process providing substantive data;

the processor executing a packeting module distinct from the first process, to create a packet having a wrapper and adapted to be persistent throughout transfer, the wrapper including a header and application-specific data, the application-specific data being distinct from the header and relating to the substantive data;

a memory device operably connected to the processor to store the packet with an application-specific data block storing the application-specific data independently from the substantive data; and

a destination device operably connected to the memory device to receive the packet from the application, the application receiving the packet from the packeting module in response to a request from the application.

2. The apparatus of claim 1 wherein the header contains an identification corresponding to a packet determined by the application and provided to the packeting module.

3. The apparatus of claim 2 wherein the identification is interpretable by the application and the packeting module.

4. The apparatus of claim 1 further comprising an intermediary device hosting a related application and connected to receive the packet from the processor and to selectively determine disposition of the substantive data, and wherein the wrapper contains sufficient processing information interpretable by the related application to enable the intermediary device to determine how to dispose of the packet.

5. The apparatus of claim 4 wherein disposition is selected from forwarding the packet to the destination device, processing the substantive data, and destroying the packet.

6. The apparatus of claim 5 wherein the related application is the application executing on the intermediary device.

7. The apparatus of claim 1 wherein the processor further comprises a first processor executing the first process, and a second processor executing the packeting process.

8. The apparatus of claim 1 wherein the destination device is associated with a computer that is remote from the first processor and connected thereto across a network.

9. The apparatus of claim 1 wherein the destination device is a memory device.

10. The apparatus of claim 1 wherein the destination device is a non-volatile storage device.

11. The apparatus of claim 10 wherein the non-volatile storage device contains a persistent storage location for storing thereto and retrieving therefrom the packet.

12. The apparatus of claim 11 wherein the retrievable storage location is a database.

13. The apparatus of claim 12 wherein the substantive data corresponds to a binary large object.

14. The apparatus of claim 1 wherein the substantive data corresponds to a binary large object.

15. The apparatus of claim 11 wherein the substantive data includes only a portion of a binary large object.

16. The apparatus of claim 1 wherein the packeting module further comprises an alteration process effective to selectively alter the substantive data, the alteration process being selected from an encryption process, a compression process, and an integrity verification process.

17. A memory device storing executables and data to transfer and store data in a packet adapted to be persistent throughout transfer, the memory device comprising:

an application block storing an application containing a first process effective to provide substantive data when executed on a processor;

a packeting module block storing a packeting module distinct from the first process, and effective to be executed on a processor to create a packet adapted to be persistent throughout transfer;

a packet buffer for storing a packet, the packet buffer containing a substantive data block containing substantive data;

the packet buffer storing a wrapper block, distinct from the substantive data block, containing wrapper data interpretable by the application and the packeting process.

18. The memory device of claim 17 wherein the wrapper includes a header and application-specific data, the application-specific data being distinct from the header and relating to the substantive data.

19. The memory device of claim 18 wherein the application-specific data further comprises application-specific heading data effective to direct the destination device on how to dispose of the packet.

20. The memory device of claim 17 wherein the wrapperblock contains an identification corresponding to a packet type determined by the application and provided to the packeting module when executing, the identification being interpretable by the application and the packeting module.

21. The memory device of claim 17 further comprising a raw data buffer for containing the substantive data received from the process and providing the substantive data to the packeting module.

22. The memory device of claim 17 further comprising a callback block storing a callback module executable on the processor and effective to transfer the packet between the application and the packeting module.

23. A method of packetizing data in a packet adapted to be persistent throughout transfer, the method comprising:

providing a processor hosting an application containing a first process providing substantive data;

providing a packeting module distinct from the first process;

creating a packet adapted to be persistent throughout transfer by the packeting module, including creating a wrapper comprising a header and an application-specific data block, the application-specific data block being distinct from the header, and relating to, but stored independently from, the substantive data in the packet;

providing to the packet the substantive data;

transferring the packet to the application; and

transferring the packet from the application to a destination device.

24. The method of claim 23 wherein the wrapper contains an identification corresponding to a packet type determined by the application and provided to the packeting module.

25. The method of claim 24 wherein the identification is interpretable by the application and the packeting module.

26. The method of claim 23 wherein the application-specific data is stored in a format interpretable by the application and the packeting module.

27. The method of claim 23 wherein the application-specific data block is accessible directly only by the packeting process, and is interpretable only by the application upon receipt of the application-specific data from the packeting module.

28. The method of claim 23 wherein the packet is persistent after transferring to the destination device.

29. The method of claim 23 further comprising providing a non-volatile storage device as the destination device, and wherein the packet is selectively retrievable from the storage device.

30. The method of claim 23 wherein the packet is selectively persistent after transferring to the destination device, and wherein the application is effective to determine the disposition of the packet.

31. The method of claim 23 wherein the application-specific data block is stored in a format effective to be interpretable exclusively by the packeting process.

32. The method of claim 23 wherein the destination device is the processor, the packet being transferred to a second process executing on the processor.

33. The method of claim 23 further comprising providing a remote computer and a network operably connecting the processor to the remote computer, and wherein the destination device is associated with the remote computer.

34. The method of claim 23 further comprising selectively encrypting, by the packeting process, the substantive data to be placed in the packet.

35. The method of claim 34 further comprising providing by the application to the packeting process an encryption key to be used for encryption.

36. The method of claim 23 wherein the application-dependent data is selected from data effective to provide an encryption key;

further describe the substantive data;

further annotate the substantive data;

summarize the substantive data;

define a method of operating on the substantive data;

identify a source of the substantive data;

provide file identification data associated with the substantive data;

identify a sender of the packet;

identify access rights associated with the packet; and

identify a network role of the application running on the processor.

37. The method of claim 23, wherein the header data includes a packet length and a packet type describing the substantive data to the application and the packeting module.

38. The method of claim 23 wherein the packeting module is programmed to provide selective encryption, compression, and validation data for the packet in response to an instruction from the application.

39. The method of claim 38 further comprising receiving the packet by the destination device, and wherein the packeting module is programmed to provide selective decryption, decompression, and validation ofthe packet in response to an instruction from the destination device.