IP Library Granted Patent US 8,423,561
Granted Patent B2
US 8,423,561 · App. 12/829,680 · Granted Apr 16, 2013

Method and system for simplifying object mapping for a user interface

Inventors: Glenn William Osborne (Roswell, GA); George Ibrahim Mashini (Woodstock, GA)
Assignee: Catavolt, 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,423,561
App. No.
12/829,680
Granted
Apr 16, 2013
Kind
B2
Abstract

The exemplary embodiments of the present invention provide a system and method for simplifying object mapping for user interfaces for on a computer system. The method comprises receiving a client request for action and associating the client request to at least one logical object. The method further comprises converting the at least one logical object to at least one physical object that resides in a object relational mapping, and mapping between the at least one physical object and at least one relational database. The system includes a conceptual module that associates the client requests to at least one logical object and converts the at least one logical object to at least one physical object that resides in a object relational mapping, and a object relational mapping module for mapping between physical objects and at least one relational database.

Claims (32)

1. A method for simplifying object mapping for a user interface for a computer system, comprising:

performing processing associated with receiving a client request for action from a user interface;

performing processing associated with associating the client request to a logical object in order to minimize a representational gap between the client request and a physical object using the logical object, wherein the associating comprises accepting an entity identifier and a property name and validating that the client request is a query request, wherein the logical object comprises a dialogue process and a collection of metadata that describes an entity definition, wherein the dialogue process comprises a query subroutine comprising the query request and processing the query request to return a dialogue response, wherein the dialogue response comprises a list of dialog records of corresponding values from the physical object if a successful query occurs, and a redirection is returned if a non-successful recoverable query occurs, the dialogue response also comprises a value comprising: value, exception, or the redirection, wherein the redirection is constructed with the entity identifier to a new dialog model that can be used to recover from an error;

performing processing associated with converting the logical object to a physical object that resides in an object relational mapping using information from the query request;

performing processing associated with mapping between the physical object that resides in the object relational mapping and a relational database; and

performing processing associated with responding to the query request using the object relational mapping in order to simplify the user interface by minimizing the representational gap between the user interface and the physical object using the logical object.

2. The method of claim 1 , wherein the dialogue process further comprises a subroutine comprising: read, write, method, or navigate, or any combination thereof.

3. The method of claim 2 , wherein the subroutine further comprises:

performing processing associated with returning a dialogue response.

4. The method of claim 3 , wherein the dialogue response is a dialog record of corresponding values from the physical object if a successful read occurs; and a redirection is returned if a non-successful recoverable read occurs.

5. The method of claim 3 , wherein the dialogue response is a dialog record of corresponding values from the physical object if a successful write occurs; and a redirection is returned if a non-successful recoverable write occurs.

6. The method of claim 3 , wherein the dialogue response is a dialog record of corresponding values from the physical object if a successful method occurs; and a redirection is returned if a non-successful recoverable method occurs.

7. The method of claim 3 , wherein the dialogue response is a redirection if a successful navigate occurs; and an exception is returned if a non-successful navigate occurs.

8. The method of claim 3 , wherein the dialogue response includes a any combination of value, exception, or redirection.

9. The method of claim 1 , wherein the physical object comprises collection of data or logic.

10. A system for simplifying object mapping for a user interface for a computer system, comprising:

a memory;

a processor configured for:

performing processing associated with receiving a client request for action from a user interface;

performing processing associated with associating the client request to a logical object in order to minimize a representational gap between the client request and a physical object using the logical object, wherein the associating comprises accepting an entity identifier and a property name and validating that the client request is a query request, wherein the logical object comprises a dialogue process and a collection of metadata that describes an entity definition, wherein the dialogue process comprises a query subroutine comprising the query request and processing the query request to return a dialogue response, wherein the dialogue response comprises a list of dialog records of corresponding values from the physical object if a successful query occurs, and a redirection is returned if a non-successful recoverable query occurs, the dialogue response also comprises a value comprising: value, exception, or redirection, wherein the redirection is constructed with the entity identifier to a new dialog model that can be used to recover from an error;

performing processing associated with converting the logical object to a physical object that resides in an object relational mapping using information from the query request;

performing processing associated with mapping between the physical object that resides in the object relational mapping and a relational database; and

performing processing associated with responding to the query request using the object relational mapping in order to simplify the user interface by minimizing the representational gap between the user interface and the physical object using the logical object.

11. The system of claim 10 , wherein the dialogue process further comprises a subroutine comprising: read, write, method, or navigate, or any combination thereof.

12. The system of claim 11 , wherein the subroutine further comprises:

performing processing associated with returning a dialogue response.

13. The system of claim 12 , wherein the dialogue response is a dialog record of corresponding values from the physical object if a successful read occurs; and a redirection is returned if a non-successful recoverable read occurs.

14. The system of claim 12 , wherein the dialogue response is a dialog record of corresponding values from the physical object if a successful write occurs; and a redirection is returned if a non-successful recoverable write occurs.

15. The system of claim 12 , wherein the dialogue response is a dialog record of corresponding values from the physical object if a successful method occurs; and a redirection is returned if a non-successful recoverable write occurs.

16. The system of claim 12 , wherein the dialogue response is a redirection if a successful navigate occurs; and an exception is returned if a non-successful navigate occurs.

17. The system of claim 12 , wherein the dialogue response includes any combination of value, exception, or redirection.

18. The system of claim 10 , wherein the physical object comprises a collection of data or logic.

Assignments (6)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 3, 2025
From: HEXAGON TECHNOLOGY CENTER GMBH
To: HEXAGON INNOVATION HUB GMBH
Reel/Frame 073096/0909 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 13, 2022
From: HEXAGON XALT SOLUTIONS INC.
To: HEXAGON TECHNOLOGY CENTER GMBH
Reel/Frame 062067/0844 →
CHANGE OF NAME Recorded Jul 28, 2022
From: CATAVOLT, INC.
To: HEXAGON XALT SOLUTIONS, INC.
Reel/Frame 061003/0694 →
SECURITY INTEREST Recorded Aug 8, 2016
From: CATAVOLT, INC.
To: WESTERN ALLIANCE BANK
Reel/Frame 039364/0399 →
SECURITY INTEREST Recorded May 22, 2014
From: CATAVOLT, INC.
To: SILICON VALLEY BANK
Reel/Frame 032995/0414 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 5, 2012
From: OSBORNE, GLENN WILLIAM; MASHINI, GEORGE IBRAHIM
To: CATAVOLT, INC.
Reel/Frame 027998/0567 →
Continuity (2)
Provisional Application 61222557 · Jul 2, 2009
Related Publication 20110004603A1 · Jan 6, 2011