US5884097A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Data structure and methods for defining and using attribute data blocks to instantiate objects and describe changes to objects
Assignee: Intertop Corp
•
Filing: 1997-05-17
•
Granted: 1999-03-16
•
Expires: 2017-05-17
Abstract
Abstract A data structure and method are disclosed for transferring object attributes between platforms in a distributed computing environment. The method includes creating an application description file. The application description file includes a type ID and an object name. The type ID references a type information file. The application file includes an attribute data block and the attribute data block contains data for attributes that are included in the object. The attribute description file is transferred to a platform that includes the type information file and the type information file includes a memory offset map that determines a sequence of attribute data storage in the attribute data block. Thus, the object attributes are received by the platform and the type information file provides a memory offset map for individual attributes in the attribute description file.
Inventors
- 👤 Shih-Gong Li
- 👤 Yun-Yong Shen
- 👤 Sing Ban Robert Tien
- 👤 Tu-Hsin Tsai
- 👤 Ching-Yun Yang
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-01 23:09
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/465
Claims Analysis
Total Claims: 19
Claim 1
Independent Claim
129 words
A method of transferring object attributes between platforms in a distributed computing environment comprising: creating an application description file, the application description file including a type ID and an object name, wherein the type ID references a type information file, the application file further including an attribute data block, wherein the attribute data block contains data for attributes that are included in the object; transferring the attribute description file to a platform, the platform including the type information file wherein the type information file includes a memory offset map that determines a sequence of attribute data storage in the attribute data block; whereby the object attributes are received by the platform and the type information file provides a memory offset map for individual attributes in the attribute description file.
Claim 2
Independent Claim
129 words
A method of transferring object attributes between platforms in a distributed computing environment comprising: creating an application description file, the application description file including a type ID and an object name, wherein the type ID references a type information file, the application file further including an attribute data block, wherein the attribute data block contains data for attributes that are included in the object; transferring the attribute description file to a platform, the platform including the type information file wherein the type information file includes a memory offset map that determines a sequence of attribute data storage in the attribute data block; whereby the object attributes are received by the platform and the type information file provides a memory offset map for individual attributes in the attribute description file.
Claim 3
Dependent Claim
40 words
A method as recited in claim 1 further including: instantiating a type information object corresponding to the type information file and generating an index/name table that indicates a memory offset for one or more attributes in the type information object.
Claim 4
Dependent Claim
28 words
A method as recited in claim 2 further including: instantiating an application object according to the type information file and including attribute data from the attribute description file.
Claim 5
Dependent Claim
36 words
A method as recited in claim 3 wherein the index/name table generated for the type information object is used to determine a memory offset for data stored by a set command associated with the application object.
Claim 6
Dependent Claim
36 words
A method as recited in claim 3 wherein the index/name table generated for the type information object is used to determine a memory offset for data retrieved by a get command associated with the application object.
Claim 7
Dependent Claim
19 words
A method as recited in claim 1 wherein the type information file includes a plurality of attributed definition blocks.
Claim 8
Dependent Claim
26 words
A method as recited in claim 6 wherein the attribute definition blocks include a memory map block, a default value block, and an upper-lower value block.
Claim 9
Dependent Claim
20 words
A method as recited in claim 7 wherein the plurality of attribute definition blocks includes a common attribute definition block.
Claim 10
Dependent Claim
20 words
A method as recited in claim 7 wherein the plurality of attribute definition blocks includes a customized attribute definition block.
Claim 11
Dependent Claim
20 words
A method as recited in claim 7 wherein the plurality of attribute definition blocks includes a data attribute definition block.
Claim 12
Dependent Claim
44 words
A method as recited in claim 7 wherein attribute data that is associated with the data attribute definition block is included in the application description file and data that is associated with the customized attribute definition block is excluded from the application description file.
Claim 13
Dependent Claim
44 words
A method as recited in claim 7 wherein attribute data that is associated with the data attribute definition block is included in the application description file and data that is associated with the common attribute definition block is excluded from the application description file.
Claim 14
Dependent Claim
136 words
A type information data structure for storing information associated with an object type that is used to instantiate objects of the object type comprising: an attribute definition block including a memory map block, a default value block, and an upper-lower value block, wherein the memory map block includes a list of attribute ID blocks, the attribute ID blocks including a name and type block, a default offset block, and an upper-lower offset block; wherein the default value block includes a default value associated with an attribute ID block at a location specified by the default offset block; wherein the upper-lower value block includes an upper-lower limit associated with an attribute ID block at a location specified by the default offset block; whereby type information is stored so that objects of the object type may be instantiated.
Claim 15
Dependent Claim
136 words
A type information data structure for storing information associated with an object type that is used to instantiate objects of the object type comprising: an attribute definition block including a memory map block, a default value block, and an upper-lower value block, wherein the memory map block includes a list of attribute ID blocks, the attribute ID blocks including a name and type block, a default offset block, and an upper-lower offset block; wherein the default value block includes a default value associated with an attribute ID block at a location specified by the default offset block; wherein the upper-lower value block includes an upper-lower limit associated with an attribute ID block at a location specified by the default offset block; whereby type information is stored so that objects of the object type may be instantiated.
Claim 16
Dependent Claim
16 words
A data structure as recited in claim 13 further including a plurality of attribute definition blocks.
Claim 17
Dependent Claim
32 words
A data structure as recited in claim 14 wherein the plurality of attribute definition blocks includes a common attribute definition block, a customized attribute definition block, and a data attribute definition block.
Claim 18
Dependent Claim
17 words
A computer readable medium on which data is stored according to the data structure of claim 13.
Claim 19
Dependent Claim
21 words
A network communication line on which data is transmitted, the data being organized according to the data structure of claim 13.
References Cited (Backward Citations)
US5129083A
Cited
US5410702A
Cited
US5313636A
Cited
US5432936A
Cited
US5481718A
Cited
US5778227A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2002-03-15 | 2002-09-14 | 2003-03-16 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2006-03-15 | 2006-09-14 | 2007-03-16 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2010-03-15 | 2010-09-14 | 2011-03-16 | $7700.00 | Window Closed / Lapsed |