US20150127736A1 - Systems and methods for distributed rules processing - Google Patents
Systems and methods for distributed rules processing Download PDFInfo
- Publication number
- US20150127736A1 US20150127736A1 US14/527,348 US201414527348A US2015127736A1 US 20150127736 A1 US20150127736 A1 US 20150127736A1 US 201414527348 A US201414527348 A US 201414527348A US 2015127736 A1 US2015127736 A1 US 2015127736A1
- Authority
- US
- United States
- Prior art keywords
- rules
- digital data
- data processor
- tenant
- engine
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N5/00—Computing arrangements using knowledge-based models
- G06N5/02—Knowledge representation; Symbolic representation
- G06N5/022—Knowledge engineering; Knowledge acquisition
- G06N5/025—Extracting rules from data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
Definitions
- the invention relates to digital data processing and, more particularly, for example, to distributed processing of rules bases.
- Computer systems that facilitate business operations based on information specific to an industry or enterprise are well known in the art. These typically rely on rules identifying situations that are expected to arise during enterprise operation and the applicable responses. Such systems have been used in a range of applications, from health care to automotive repair. The rules on which they rely come from experts in the field, from the collective experience of workers on the “front line,” or a combination of these and other sources.
- BPM applications arc commonly used in enterprise computing, for example, where they facilitate a range of business operations, from marketing to manufacturing to distribution to technical support.
- a BPM application can implement data-processing workflows to support the processing of transactional data ranging from customer service requests received by retail and banking enterprises to the routing and resolution of health care claims by insurance enterprises.
- enterprise software applications incorporate architectures that permit their use “in the cloud,” that is, over the Internet, with computing resources delivered up to each user on demand. In a sense, this extends the client-server model of past eras from the physical confines of the enterprise to the expanse of the world.
- a common architecture of the past might provide for software that executes on a server, e.g., located at enterprise headquarters, and that processes requests entered by support personnel at the enterprise's branch offices
- the new cloud architectures permit servicing of requests by servers located around the world.
- any given request by a user on a client device might as well be attended to by a server located in a neighboring state as in a neighboring country.
- cloud applications are often initially tested behind an enterprise firewall, they are typically architected for final deployment outside that firewall, on a dynamically changing set of third-party servers (e.g., owned by Amazon, SalesForce, Google, or other cloud-computing providers).
- BPM applications can be deployed in the cloud, like other enterprise applications.
- business process management often goes to the heart of the enterprise, chief executives, IT directors, and corporate boards have yet to fully embrace this model, mainly, for fear that storing rules bases and/or transactional data exposes them to theft or wrongful disclosure.
- An object of this invention is to provide improved systems and methods for digital data processing.
- a more particular object is to provide improved systems and methods for business process management, for example, rules processing.
- a further object is to provide such improved systems and methods as facilitate deployment of BPM and other rules-processing applications on multiple digital data processors.
- a still further object is to provide such improved systems and methods as facilitate such deployment in distributed environments, such as, for example, in cloud computing environments.
- Yet a still further object is to provide such improved systems and methods as provide better security for BPM and other rules-processing applications in such distributed environments.
- Still yet a further object is to provide such improved systems and methods as better utilize computing and networking resources in applications so distributed.
- a distributed rules processing system that includes first and second digital data processors that are coupled to one another by one or more networks.
- a rules base and a transactional data base are each coupled to one of the digital data processors; both may be coupled to the same digital data processor or otherwise.
- One or more coordination modules (e.g., “proxies”), each of which is associated with a respective one of the digital data processors, makes available to a selected one of those digital data processors from the other of those digital data processors (i) one or more selected rules from the rules base, and/or (ii) one or more data from the transactional database on which those rules are to be executed.
- the selected digital data processor executes one or more of the selected rules as a rules engine, executes one or more of the selected rules using a rules engine, and/or processes one or more data from the transactional database with rules executing using a rules engine.
- the first and second digital data processors of a distributed rules processing system can be disposed remotely from one another and can coupled for communication by the Internet, as well optionally by local area networks, wide area networks, and so forth.
- a firewall and/or other such functionality that is coupled to one or more of those networks prevents the selected digital data processor from accessing from the other digital data processor (i) the selected rules and/or (i) the data on which those rules are to be executed.
- Further related aspects of the invention provide a distributed rules processing system, e.g., of the type described above, wherein one or more of the coordination modules make the selected rules and/or data available to the selected digital data processor from the other digital data processor in response to a request from the rules engine.
- the first digital data processor can include a rules base, e.g., for processing credit card information.
- the second digital data processor can, likewise, include a data base of transactional data, e.g., pertaining to opening of credit card account, purchases against the credit cards, refunds, and so forth.
- a rules engine operating, for example, on the first digital data processor can utilize a proxy operating, for example, on the second digital data processor to access transactional data that is “behind the firewall” on the second digital data processor for processing by the rules engine with rules already accessible to the first data data processor (e.g., on account of its inclusion of and/or coupling to the rules base).
- a proxy operating, for example, on the second digital data processor to access transactional data that is “behind the firewall” on the second digital data processor for processing by the rules engine with rules already accessible to the first data data processor (e.g., on account of its inclusion of and/or coupling to the rules base).
- the coordination modules make the selected rules and/or data available to the selected digital data processor from the other digital data processor by opening one or more communications ports on that other digital data processor.
- a coordination module executing on the first data processor can respond to transactional data base access requests generated by the rules engine to determine whether that data base is coupled to the first digital data processor and, if not, to cooperate with the coordination module on the second digital data processor to make the transactional data available to the rules engine from the second digital data processor.
- a rules engine executing on the second digital data processor can utilize a proxy operating, for example, on the first digital data processor, to access rules necessary to process transactional data already accessible to the data processor (e.g., on account of its inclusion of and/or coupling to the transactional data base).
- the invention provides a distributed rules processing system, e.g., of the type described above, in which one or more of the coordination modules make the selected rules and/or data available to the selected digital data processor from the other digital data processor in response to a request from that other digital data processor.
- a request made from the other digital data processor in a distributed rules processing system is made by a rules engine executing on that other digital data processor.
- a rules engine operating on the first digital data processor can utilize the proxy operating on the second digital data processor to access some transactional data in the data base on the second digital data processor for processing by the rules engine on the first digital data processor (and/or, conversely, to store transactional data processed by that rules engine to that transactional data base). It can also effect, through use of that proxy and/or its counterpart on the first digital data processor, transfer of selected rules to the second digital data processor for execution by its rules engine, e.g., on other data stored (and/or to be stored) in the transactional database.
- FIG. 1 depicts a digital data processing system for distributed rules processing according to one practice of the invention
- FIG. 2 depicts a method of operation of a coordination module in a system of FIG. 1 ;
- FIG. 3 depicts operation of a coordination module in a system according to the invention within a multi-tenant cloud-based environment.
- FIG. 1 depicts a digital data processing system 10 for distributed processing in a rules-based system according to one practice of the invention.
- the illustrated system includes client (or “tenant”) digital data processors 12 , 14 that are coupled via network 16 for communication with server digital data processor 18 .
- the client digital data processors 12 , 14 are conventional desktop computers, workstations, minicomputers, laptop computers, tablet computers, PDAs or other digital data processing apparatus of the type that are commercially available in the marketplace and that are suitable for operation in the illustrated system as described herein, all as adapted in accord with the teachings hereof.
- the server digital data processor 18 is, likewise, a digital data processing apparatus of the type commercially available in the marketplace suitable for operation in the illustrated system as described herein, as adapted in accord with the teachings hereof.
- the server 18 is typically implemented in a server-class computer, such as a minicomputer, it may also be implemented in a desktop computer, workstation, laptop computer, tablet computer, PDA or other suitable apparatus (again, as adapted in accord with the teachings hereof).
- Network 16 comprises one or more networks suitable for supporting communications among and between illustrated digital data processors 12 , 14 , 18 .
- Illustrated network 16 comprises one or more public networks, specifically, the Internet, though, in other embodiments, it may include (instead or in addition) one or more other networks of the type known in the art, e.g., local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), and or Internet(s).
- LANs local area networks
- WANs wide area networks
- MANs metropolitan area networks
- Illustrated client computer 12 comprises central processing, memory, storage and input/output units and other constituent components (not shown) of the type conventional in the art that are configured to form application 12 a , transaction database 12 b , rules base 12 c , and coordination module 12 d , in accord with the teachings hereof.
- the digital data processor 12 may not include a rules base.
- it may include a portion of a rules base but not transaction database or it may include neither.
- it may include a coordination module 12 d (described below) but not a transaction database, rules base or an application, all by way of non-limiting example.
- the central processing, memory, storage and input/output units of client digital data processor 12 may be configured to form and/or may be supplemented by other elements of the type known in the art desirable or necessary to support elements 12 a - 12 d in accord with the teachings hereof, as well as to support other operations of the digital data processor 12 .
- These can include, by way of non-limiting example, peripheral devices (such as keyboards and monitors), operating systems, database management systems, and network interface cards and software, e.g., for supporting communications between digital data processor 12 and other devices over network 16 .
- Digital data processor 12 is coupled to network 16 via firewall 12 e .
- This is a conventional device of the type known in the art (as otherwise configured in accord with the teachings hereof) suitable for blocking unauthorized access, yet, permitting authorized access, to the digital data processor 12 , including (but not limited to) data and rules bases 12 b , 12 c.
- Firewall 12 e which is constructed and operated in the conventional manner known in the art, may comprise a “hardware” (or stand-alone) firewall and/or it may comprise a software firewall configured from the constituent and/or other components of digital data processor 12 , again, in the conventional manner known in the art.
- client digital data processor 14 may similarly be configured in accord with the teachings hereof to form application 14 a , transaction database 14 b , rules base 14 c , and coordination module 14 d . As well, they may be supplemented by other elements of the type known in the art desirable or necessary to support elements 14 a - 14 d in accord with the teachings hereof, as well as to support other operations of the digital data processor 14 .
- the client digital data processor 14 may also include a firewall 14 e , e.g., constructed and operated like device 12 e , discussed above, to block unauthorized access, yet, permit authorized access, to the digital data processor 14 , including (but not limited to) data and rules bases 14 b , 14 c.
- digital data processors 12 and 14 are depicted and described in like manner here, it will be appreciated that this is for sake of generality and convenience: in other embodiments, these devices may differ in architecture and operation from that shown and described here and/or from each other, all consistent with the teachings hereof. Moreover, it will be appreciated that although only two closely positioned client devices 12 , 14 are shown, other embodiments may have greater or fewer numbers of these devices disposed near and/or far from one another, collocated behind one or more common firewalls 12 e , 14 e or otherwise.
- server digital data processor 18 comprises central processing, memory, storage and input/output units and other constituent components (not shown) of the type conventional in the art that are configured in accord with the teachings hereof to form rules engine 18 a , transaction database 18 b , rules base 18 c , and coordination module 18 d , one or more of which (and/or portions thereof) may be absent in various embodiments of the invention.
- the digital data processor 18 may also include a firewall 18 e , e.g., constructed and operated like device 12 e , discussed above, to block unauthorized access, yet, permit authorized access, to the digital data processor 18 , including (but not limited to) data and rules bases 18 b , 18 c.
- the digital data processor 18 is configured as a server on a “cloud” platform, e.g., of the type commercially available from Amazon, SalesForce, Google, or other cloud-computing providers.
- a “cloud” platform e.g., of the type commercially available from Amazon, SalesForce, Google, or other cloud-computing providers.
- those other servers may differ in architecture and operation from that shown and described here and/or from each other, all consistent with the teachings hereof.
- Rules bases 12 c , 14 c , 18 c comprise conventional rules bases of the type known in the art (albeit configured in accord with the teachings hereof) for storing rules (e.g., scripts, logic, controls, instructions, metadata etc.) and other application-related information in tables, database records, database objects, and so forth.
- rules and rules bases are of the type described in the aforementioned incorporated-by-reference U.S. Pat. No. 5,826,250, entitled “Rules Bases and Methods of Access Thereof” and U.S. Pat. No. 7,640,222, entitled “Rules Base Systems and Methods with Circumstance Translation,” though, rules and rules bases that are architected and/or operated differently may be used as well.
- rules bases may be present in any given embodiment.
- some embodiments may utilize multiples rules bases, e.g., an enterprise-wide rules base 18 c on the server 18 and domain-specific rules bases on the client devices 12 , 14 , all by way of example.
- multiple rules bases may be of like architecture and operation as one another; though, they may be disparate in these regards, as well.
- rules may comprise meta-information structures. These are structures that can include data elements and/or method elements.
- the latter can be procedural or declarative.
- such a structure may be procedural insofar as it comprises one or more of a series or ordered steps.
- such a structure may be declarative, for example, insofar as it sets forth (declares) a relation between variables, values, and so forth (e.g., a loan rate calculation or a decision-making criterion), or it declares the desired computation and/or result without specifying how the computations should be performed or the result achieved.
- the declarative portion of a meta-information structure may declare the desired result of retrieval of a specified value without specifying the data source for the value or a particular query language (e.g., SQL, CQL, .QL etc.) to be used for such retrieval.
- a particular query language e.g., SQL, CQL, .QL etc.
- the declarative portion of a meta-information structure may comprise declarative programming language statements (e.g., SQL). Still other types of declarative meta-information structures are possible.
- rules may comprise meta-information structures that are wholly procedural and others may comprise those that are wholly declarative
- the illustrated embodiment also contemplates rules that comprise both procedural and declarative meta-information structures, i.e., rules that have meta-information structure portions that are declarative, as well as meta-information structure portions that are procedural.
- rules of the illustrated embodiment that comprise meta-information structures may also reference and/or incorporate other such rules, which themselves may, in turn, reference and/or incorporate still other such rules.
- editing such rule may affect one or more rules (if any) that incorporate it.
- meta-information structures provide users with the flexibility to apply any of code-based and model-driven techniques in the development and modification of software applications and/or computing platforms.
- meta-information structures comprise data elements that can be used to define any aspect of a complex system at a higher level of abstraction than source code written in programming languages such as Java or C++.
- users may also embed programming language statements into meta-information structures if they deem that to be the most efficient design for the system being developed or modified.
- the data elements of the meta-information structures along with programming language statements (if any) are automatically converted into executable code by a rules engine (e.g., 18 a ).
- rules may be the primary artifacts that get created, stored (e.g., in a rules base) or otherwise manipulated to define and/or modify the overall functionality of rules-based applications that may automate and/or manage various types of work in different business domains at run-time.
- a plurality of rules stored in a rules base e.g., 12 c , 14 c , 18 c
- Such a software application may include specialized software that is used within a specific industry or a business function (e.g., human resources, finance, healthcare, telecommunications etc.), or it may include a cross-industry application (e.g., a project management application), or any other type of software application.
- a digital data processor e.g. any of 12 , 14 and 18
- any portion of the rules that define the application may be retrieved from a rules bases (e.g. any of 12 c , 14 c and 18 c ) and processed/executed (e.g., using a rules engine 18 a as defined below) in response to requests/events signaled to and/or detected by the digital data processor at run-time.
- Transactional data bases 12 b , 14 b , 18 b comprise conventional data bases of the type known in the art (albeit configured in accord with the teachings hereof) for storing corporate, personal, governmental or other data that may be any of generated, stored, retrieved and otherwise processed (hereinafter, collectively referred to as “processed”) by rules in one or more of the rules bases 12 c , 14 c , 18 c .
- the data may be financial data, customer records, personal data, run-time data related to an application, or other type of data and it may be stored in tables, database records, database objects, and so forth.
- transactional data bases may be present in any given embodiment.
- some embodiments may utilize multiple transactional database bases, e.g., an enterprise-wide data base 18 b on the server 18 and branch-office specific data bases on the client devices 12 , 14 , all by way of example.
- multiple transactional data bases may be of like architecture and operation as one another; though, they be disparate in these regards, as well.
- Illustrated digital data processor 18 also includes rules engine 18 a of the type conventionally known in the art (albeit configured in accord with the teachings hereof) for use in processing/executing rules from a rules base in order to process data in (and/or for storage to) a transactional database, e.g., in connection with events signaled to and/or detected by the engine.
- rules engines are of the type described in the aforementioned incorporated-by-reference U.S. Pat. No. 5,826,250, entitled “Rules Bases and Methods of Access Thereof” and U.S. Pat. No. 7,640,222, entitled “Rules Base Systems and Methods with Circumstance Translation” and/or U.S. patent application Ser. No. 11/681,269, filed Mar. 2, 2007, entitled “Proactive Performance Management For Multi-User Enterprise Software Systems,” the teachings too of which are incorporated by reference herein—all as adapted in accord without the teachings hereof.
- the rules engine 18 a may be implemented in a single software program, in multiple software programs/modules, or a combination of software modules/programs. Moreover, it may comprise programming instructions, scripts, or rules (e.g., rules stored in rules base 18 c ) and/or a combination thereof.
- the rules engine 18 a executes on the server 18
- the techniques described herein may be employed to execute the rules engine 18 a on or over multiple digital data processors (e.g., 12 , 14 and 18 ).
- the rules engine 18 a may initially be invoked for execution on a single digital data processor (e.g., 18 ). Subsequently, portions of it (or, potentially, the entirety of it) may be apportioned, distributed and executed over multiple digital data processors using the techniques described herein.
- the rules engine 18 a can be utilized to generate a summary report that requires analysis of sensitive personnel-related data maintained in local branch offices. To that end, the engine 18 a executes rules for performing preparatory tasks, such as, zeroing out data collection variables and identifying local offices to be queried.
- the engine 18 a also retrieves from rules base 18 c or otherwise generate rules that will serve as rules engines (e.g., 12 a , 14 a ) customized or otherwise suited for execution on digital data processing equipment 12 , 14 at those offices, as well as rules for execution on those engines 12 a , 14 a to analyze (and anonymize) sensitive data from the respective offices.
- Both the rules engine-defining rules and the data analysis rules are distributed to the equipment 12 , 14 , where they perform these functions and send the requisite information back to server 18 for reporting the BPM application executing there.
- Such distributed execution has the advantage of permitting the BPM application executing using engine 18 a to generate an enterprise-wide report, without necessitating the transmission of sensitive data outside the confines of the local offices.
- the rules engine 18 a can have two distinct portions, e.g., one that embodies the algorithm for rule selection (e.g., in the manner of the rule finder disclosed in U.S. Pat. No. 5,825,260, assigned to the assignee hereof and incorporated by reference herein), and the other that generates/executes the executable code once the requisite rule has been selected.
- the rules engine 18 a (or other functionality) can apportion and distributed these portions separately as required.
- Server 18 takes, for example, an instance where server 18 gets a request for executing a “loan validation” process for a specific context.
- Server 18 stores rules for multiple versions of the “loan validation” process for different contexts. However, the server does not have the computing power to execute the ‘rule finder’ algorithm to select the right version and/or the server doesn't have the code generation portion of the engine to execute the selected rule.
- Server retrieves the rules for all versions of “loan validation” process and transmits them along with the rule selection portion of the engine to a remote digital data processor that has installed thereon the code generation portion of a rules engine. Upon receiving the rule finder portion of the engine along with the rules for all versions, the correct loan validation process is selected and executed on the target digital data processor.
- the rules engine 18 a may have additional distinct components/portions that can be apportioned and distributed separately. These may include (but are not limited to) a data access component used for processing data during rule execution, a session management component for keeping track of activity across sessions of interaction with a digital data processor and/or a performance monitoring component for monitoring and interacting with various system resources/event logs in order to manage performance thresholds. Still other types of distinct components/portions may be part of the rules engine 18 a.
- Applications 12 a and 14 a , of digital data processors 12 , 14 may too comprise rules engines of the type described above, as adapted in accord with the teachings hereof. These applications may be configured (e.g., at least partially using rules stored in a rules base as described above) as stand-alone applications and/or may be embedded in (or coupled) to other software applications, e.g., web browsers. While in some embodiments, such applications 12 a , 14 a are architected and operated similarly to rules engine 18 a , in other embodiments they embody a subset of the functionality of engine 18 a , e.g., suited to the processing resources and/or demands of the digital data processors 12 , 14 upon which they operate. Instead or in addition, such applications 12 a , 14 a can comprise other functionality than that provided in rules engine 18 a , again, for example, suited to the processing resources and/or demands of the digital data processors 12 , 14 upon which they operate.
- rules engine 18 a For sake of simplicity, the discussion that follows focuses on aspects of operation of rules engine 18 a ; it will be appreciated that other rules engines (e.g., 12 a , 14 a in certain embodiments) may operate similarly in these regards.
- rules engine 18 a processes/executes rules from a rules base in order to process data in (and/or for storage to) a transactional database.
- the engine 18 a executes rules from rules base 18 c in order to process data in (and/or store data to) database 18 b
- the engine 18 a may operate in the conventional manner known in the art.
- the rules engine 18 a works with one or more of the coordination modules to effect the desired processing.
- the rules engine 18 a may work with the coordination modules (e.g., 12 d , 14 d , 18 d ) to effect the desired processing over multiple digital data processors (e.g., for access to more computing resources/power) in accord with the teachings hereof.
- coordination modules 12 d , 14 d , 18 d comprise functionality resident on (and/or coupled to) each of the respective processors 12 , 14 , 18 that facilitate access to and transfer of rules, the rules engine or portion thereof, or data (and, preferably, all three) between the digital data processors.
- operation of the module(s) 12 d , 14 d , 18 d can include one or more of (i) obviating obstacles presented by firewalls 12 e , 14 e , 18 e or other functionality to such inter-processor accesses and transfers, (ii) effecting such access and transfers, and (iii) querying a digital data processor to determine whether it has resources (e.g., a rules base, a transactional data base, a portion of or the entire rules engine, and/or computing power) to facilitate the completion of a task (e.g., by executing a given one or more rules on a given set of data).
- resources e.g., a rules base, a transactional data base, a portion of or the entire rules engine, and/or computing power
- coordination modules 12 d , 14 d , 18 d are utilized in all embodiments.
- other embodiments may utilize additional such modules, e.g., one module per digital data processor for facilitating rules access/transfer between digital data processors, one module for facilitating transaction access/transfer, and so forth.
- some such modules could be directed to querying digital data processors for resources, while others are directed to access and transfers.
- the modules 12 d , 14 d , 18 d may comprise stand-alone functionality stored and executing within each respective digital data processors 12 , 14 18 . Alternatively, they may comprises functionality that is embedded in the rules engine 18 a and/or applications 12 a , 14 a and/or into other applications or operating system functions resident on the respective devices 12 , 14 , 18 . Moreover, in embodiments that include multiple such modules 12 d , 14 d , 18 d , functionality may be distributed and/or divided among them.
- modules 12 d , 14 d , 18 d are shown forming part of the respective digital data processors 12 , 14 , 18 in the illustrated embodiment, in other embodiments one or more of those modules may execute on still other digital data processors (not shown) that are in communication coupling with the respective processors 12 , 14 , 18 and that otherwise provide the functionality described here.
- FIG. 2 Operation of a coordination module 18 d in accord with one practice of the invention is illustrated in FIG. 2 . It will be appreciated that the sequence of steps shown in that drawing and discussed below is by way of example and that other embodiments may perform the same or different functions using alternate sequences of steps.
- the module which may be coupled to a local rules engine 18 a , responds to a request for access to a rule by determining if that rule is present in a rules base 18 c local to the digital data processor 18 —and, for example, it is therefore accessible to a local engine 18 a without crossing the firewall 12 e , 14 e of another digital data processor.
- the module 18 d can make that determination by checking for the presence of the local rules base 18 c and/or, if present, by determining if the requested rule itself is present.
- the module 18 d can make the determination by checking parameters or other indicators of rule presence, e.g., in the rule request signaled to any of the module 18 a and the engine 18 a and/or request made by the engine 18 a .
- the parameters or other indicators of rule presence may also be found in a registry of the digital data processor 18 and/or elsewhere.
- step 20 determines if data implicated by the rule (e.g., data to be processed by the rule or otherwise necessary for its execution) is present in a data base 18 b local to the digital data processor 18 —and, again, for example, it is therefore accessible to the local engine 18 a without crossing the firewall 12 e , 14 e of another digital data processor.
- the module 18 d can make that determination by checking for the presence of the local data base 18 b and/or, if present, by determining if the requested data are present.
- the module 18 d can make the determination by checking parameters or other indicators of data presence, e.g., in the rule request signaled to any of the module 18 d and the engine 18 a and/or request made by the engine 18 a .
- the parameters or other indicators of rule presence may also be found in a registry of the digital data processor 18 and/or elsewhere.
- step 22 determines if the portion of rules engine (e.g., 18 a ) that is required to execute the requested rule is present locally on digital data processor 18 .
- the module can query for local presence on digital data processor 18 of component(s)/module(s) that make up requisite portions(s) of rules engine.
- the module 18 d can determine, for example, if those rules are locally present by querying a local database/repository (e.g., rules base 18 c , transaction data base 18 b ).
- the module can check parameters or other indicators of engine presence, e.g., in the rule request signaled to any of the module 18 d and the engine 18 a and/or request made by the engine 18 a , in a registry of the digital data processor 18 and/or elsewhere.
- step 24 determines if the rule is to be executed locally, i.e., on digital data processor 18 or whether it is to be executed remotely, e.g., on digital data processors 12 , 14 .
- the module 18 d can make that determination using a variety of methods including, but not limited to, querying a local rules engine (e.g., 18 a ) and/or by checking parameters or other indicators, e.g., in the rule request signaled to any of the module 18 d and the engine 18 a and/or request made by the engine 18 a .
- the parameters or other indicators of rule presence may also be found in a registry of the digital data processor 18 and/or elsewhere.
- the module 18 d can make the determination based on load-balancing, network speed and traffic, data coherency or other factors within the ken of those of ordinary skill in the art based on the teachings hereof.
- step 28 is affirmative and the operation proceeds to step 30 , where the module 18 d defers to local engine 18 a for execution of the requested rule on the required data.
- the engine 18 a (or the required portion thereof) proceeds by accessing the rule and data in the local rules and data bases 18 b , 18 c , and by executing the rule to process the data accordingly.
- step 32 the module queries one or more other digital data processors (e.g., 12 , 14 ) to determine the location(s) of any of the requested rule, required data and engine (or portion thereof).
- the module queries one or more other digital data processors (e.g., 12 , 14 ) to determine the location(s) of any of the requested rule, required data and engine (or portion thereof).
- the module 18 d can determine the location of the requested rule (and corresponding rules base), required data and engine (or portion thereof) by checking parameters or other indicators, e.g., in the rule request signaled to any of the module 18 d and the engine 18 a and/or request made by the engine 18 a , in a registry of the digital data processor 18 and/or elsewhere.
- module 18 d can query the digital data processors 12 , 14 directly to determine if any of the required/requested resources are maintained by them.
- module 18 d is accomplished by communication between module 18 d and its counterparts 12 d , 14 d on each of digital data processors 12 , 14 —which modules 12 d , 14 d can, themselves, query the local digital data processor 12 , 14 for the requisite resource(s).
- step 32 determines whether the determination in step 32 is in the negative for any of the required/requested resources. If the determination in step 32 is in the negative for any of the required/requested resources, the operation proceeds to and terminates at step 38 where the coordination module returns an error message in response to the requested rule indicating the absence or unavailability of any of the requested rule, required data and engine (or portion thereof).
- step 32 determines whether the requested/required resources that were not already present locally at digital data processor 18 (as previously determined by steps 20 - 24 ). If the determination in step 32 is in the affirmative for any of the requested/required resources that were not already present locally at digital data processor 18 (as previously determined by steps 20 - 24 ), the operation proceeds to step 26 to make the decision of local versus remote execution of the requested rule as described above. If the determination in step 26 is affirmative, at least one of the requested rule, required data and engine (or portion thereof) that is located remotely at another digital data processor (e.g., 12 or 14 ) as identified in step 32 , is retrieved in step 40 before executing the requested rule locally on digital data processor 18 in step 30 .
- another digital data processor e.g., 12 or 14
- such retrieval is performed by the module 18 d , following a negative determination in step 28 by (i) validating that the one or more digital data processors identified in step 32 (e.g., 12 and/or 14 ) will grant access to the requested/required resource(s) and, (ii) retrieving that/those resource(s) from those one or more digital data processors (i.e., 12 and/or 14 ) to digital data processor 18 .
- the module 18 d can validate that the one or more identified digital data processors will grant access by querying the digital data processor(s) identified in step 32 accordingly. This can be done, for example, through communication with the module 12 d , 14 d of the identified digital data processor, which module can validate the presence of any of the requested/required resource (if it has not already done so).
- the validating module e.g., 12 d or 14 d
- the module 18 d retrieves and/or transfers the requested/required resource from the one or more identified digital data processors to digital data processor 18 for local execution.
- a local rules engine 18 d may access the requested/required resource (e.g., data, transaction database, rule and/or rules base) directly from the identified digital data processor, e.g., via a port opened in step 40 ( i ).
- the module 18 d may also transfer one or more requested/required resources to an identified digital data processor (e.g., 12 or 14 ) for the requested processing to be performed remotely at the identified digital data processor.
- the module 18 d may also notify the identified digital data processor (e.g., 12 or 14 ) and, preferably, its respective coordination module, identified in step 32 , passing to it the relevant information for the requested processing to be performed (e.g., identity of the rule to be executed).
- the identified digital data processor may perform the requested processing using the resources/information provided to it.
- the identified digital data processor may perform the requested processing by utilizing the methodology of FIG. 2 itself in order to access the required resources in connection therewith. The discussion that follows provides further details about this step.
- step 40 Upon completion of step 40 , control transfers to any of steps 30 , 42 or 44 depending upon the outcome of the previous steps in the operation of the coordination module 18 d , as indicated in the drawing.
- step 30 Upon completion of step 40 , control transfers to any of steps 30 , 42 or 44 depending upon the outcome of the previous steps in the operation of the coordination module 18 d , as indicated in the drawing.
- step 30 Upon completion of step 40 , control transfers to any of steps 30 , 42 or 44 depending upon the outcome of the previous steps in the operation of the coordination module 18 d , as indicated in the drawing.
- step 30 Upon completion of step 40 , control transfers to any of steps 30 , 42 or 44 depending upon the outcome of the previous steps in the operation of the coordination module 18 d , as indicated in the drawing.
- a negative determination in step 26 may be due to parameters or other indicators in a local registry of the digital data processor 18 and/or e.g., in the rule request signaled to any of the module 18 d and the engine 18 a and/or request made by the engine 18 a .
- the response to step 34 is in the negative and the operation proceeds to step 36 where the module 18 d determines if there is another digital data processor (e.g., 12 , 14 ) suited for executing the requested rule.
- the module 18 d can make the determination based on load-balancing, network speed and traffic, availability of the required/requested resources (or portions thereof) on one or more other digital data processors, data coherency or other factors within the ken of those of ordinary skill in the art based on the teachings hereof.
- a query during the operation at step 36 may reveal that an alternative digital data processor with higher computing power than processor 18 and/or another digital data processor identified in a local registry, has all of the required/requested resources.
- module 18 d may simply notify the alternative digital data processor (and/or its coordination module) to perform the requested processing as opposed to performing it locally or remotely at the other digital data processor that was identified in the local registry. More generally, this example is also reflective of some embodiments discussed throughout this document that may involve scenarios and/or steps where duplicate versions, or at least versions that are comparable in terms of functionality, of one or more requested/required resources may exist at multiple locations
- step 36 If the determination in step 36 is negative, the operation proceeds to and terminates at step 38 in the illustrated embodiment where the coordination module 18 d returns an error message indicating the absence or unavailability of a suitable digital data processor for remote execution of the requested processing/rule.
- the coordination module may ignore the negative outcome of step 26 and execute the requested rule locally as default if a suitable remote digital data processor (e.g., 12 and 14 ) is not identified in step 36 .
- coordination module 18 d any of transfers the requested/required resources from the digital data processor 18 and/or provides the relevant information to the other identified digital data processor in step 36 e.g., by employing the methodology discussed above in connection with steps 40 ( i ) and (ii). In some embodiments, coordination module 18 d may only transfer a portion of the requested/required resources if it is determined (as mentioned above) that another identified digital data processor(s) already possesses the remaining portion of the requested/required resources. Once any such transfer and/or notification is completed in step 40 from digital data processor 18 , processing is completed by executing the requested rule remotely in step 44 at the other digital data processor that is identified in step 36 .
- a negative outcome in any of steps 20 - 24 indicates that at least one of the requested/required resources is not locally present on digital data processor 18 and that one or more digital data processors (e.g., 12 and/or 14 ) may have been identified in step 32 to locate such requested/required resource as previously discussed.
- the operation proceeds to remotely execute the requested rule.
- module 18 d transfers the portion of the requested/required resources at digital data processor 18 (e.g., by employing the methodology discussed above in connection with steps 40 ( i ) and (ii)) to the single digital data processor identified in step 32 , where the remaining requested/required resources are located. Once that transfer is completed in step 40 , the requested rule/processing is performed remotely in step 42 at the location identified in step 32 .
- step 32 two or more locations may be identified in step 32 e.g., the required data may be located at digital data processor 12 and the engine may be located at digital data processor 14 .
- module 18 d may prioritize all available location options based upon various factors including, but not limited to, prioritization criteria specified in the rule request signaled to module 18 d and/or the engine 18 a , prioritization rules stored in rules base 18 c and/or elsewhere on digital data processor 18 .
- module 18 d may prioritize all available location options based upon the relative computing resources (e.g., CPU, memory etc.) at each location, network traffic or any other factors within the ken of those of ordinary skill in the art based on the teachings hereof. In any event, module 18 d will transfer the portion of the requested/required resources from digital data processor 18 to the highest priority location and once the transfer(s) is completed in step 40 , the requested rule/processing is performed remotely at that location in step 42 .
- the relative computing resources e.g., CPU, memory etc.
- a negative determination in step 26 may be followed by a negative determination in step 34 .
- an attempt is made via step 36 (as described above) to identify one or more digital data processors other than local processor 18 or the one or more digital data processors identified in step 32 .
- a request may be signaled to coordination module 18 d to execute one or more rules that define a plurality of reports.
- These report rules may be stored locally in rules base 18 c and the rules engine 18 a required to execute the requested report rules may also be locally present on server digital data processor 18 .
- the determination in step 22 may be in the negative because the data to be processed by the requested report rules is not locally present. In such an instance, operation proceeds to step 32 where the coordination module 18 d attempts to locate the one or more digital data processors that maintain the required data for reports execution.
- the coordination module 18 d identifies the location of such digital data processors (e.g., 12 , 14 ) by querying a local registry on digital data processor 18 using parameters or other indicators of data location specified in the rule request that was signaled to the coordination module 18 d .
- the query of the local registry may, for example, reveal that a portion of the required data is located in the transaction database 12 b on digital data processor 12 and the remaining portion of the required data is located in the transaction database 14 b on digital data processor 14 .
- step 26 it may be determined, for example, that the reports will not be executed locally at digital data processor 18 because a pre-requisite for such local execution is data retrieval from digital data processors 12 and 14 over a very slow network connection (e.g., 16 ).
- a negative outcome of step 26 is followed by a determination in step 34 of whether to execute the requested report rules remotely on digital data processor 12 , 14 or at both locations. This determination may be based on various factors including, but not limited to, load balancing and the correlation between the requested report rules and the required data for requested rule execution at each location.
- the operation may proceed through steps 34 , 40 and 42 such that the respective portions of the report rules along with the required engine 18 a may be transferred appropriately to digital data processors 12 and 14 for remote execution.
- the determination in step 34 may be that the requested report rules cannot be independently executed at different locations.
- the required data and/or transaction data base e.g., 12 b , 14 b
- the transfer destination may, for example, be determined based upon a higher CPU speed or any other factor.
- a retrieval and/or transfer of rules, engine or data between digital data processors 12 , 14 and 18 can be accomplished by employing the methodology discussed above in connection with steps 40 ( i ) and 40 ( ii ).
- the location(s) of the required data for the report rules may be validated (if not already done) through communication between coordination modules 12 d , 14 d and 18 d .
- the validating module e.g., 12 d or 14 d
- step 40 ii .
- module 18 d retrieves the required data portion and/or transaction data base 14 b from digital data processor 14 and transfers it to the digital data processor 12 .
- the requested report rules and the required engine 18 a are transferred from digital data processor 18 to the target digital data processor 12 . Once such retrieval and transfer is completed, the requested report rules are executed in step 42 .
- local registries, files or databases e.g., 12 b , 12 c , 14 b , 14 c , 18 b , 18 c
- local registries, files or databases are updated following the retrieval and/or transfer of rules, rule bases, engine (or any portion thereof), data and transaction data bases from/to such digital data processors.
- This allows digital data processors 12 , 14 and 18 to handle future requests for rule execution accurately and/or efficiently.
- the local registries on any of digital data processors 12 , 18 can be updated to reflect such transfer.
- the operation of coordination module 18 d is adjusted accordingly to respond to subsequent requests for execution of those report rules that are any of signaled to and received by the module and/or digital data processor 18 .
- coordination module 18 d in FIG. 2 is merely exemplary and that certain steps may be omitted, modified or re-ordered without departing from the scope of the disclosure herein.
- any of the modules 12 d , 14 d and 18 d may be configured differently based on the business and/or technical requirements that drive the use of the techniques and systems described herein.
- the systems and techniques described herein may be used for provisioning a computing platform as a service (e.g., commercially available Platform-as-a-Service or “PaaS” offerings) over the internet to multiple concurrent users (e.g., from different companies or “tenant” organizations) for application development, testing and/or deployment in a way that provides more flexibility and ease of use without sacrificing data security as compared to the conventional technology/tools available on the market today.
- PaaS Platform-as-a-Service
- the server 18 depicted in FIG. 1 is configured as a cloud-based computing platform comprising hardware and software components (e.g., business process management software) that are used by users 11 from one or more tenant organizations over the internet (e.g., network 16 ) to develop, test and/or deploy their enterprise applications.
- hardware and software components e.g., business process management software
- tenant organizations e.g., business process management software
- network 16 e.g., network 16
- Such shared use of resources among multiple tenant organizations on a cloud-based server (e.g., 18 ) allows each respective tenant to quickly develop, test and deploy their applications while avoiding the cost and complexity of buying the underlying hardware and software components and hosting them in their own data centers.
- the multi-tenant architecture have traditionally presented significant challenges related to data security and integration between cloud-based application(s) and the legacy systems/resources located within each of the respective tenants' data centers. These challenges are exacerbated by the business need of many of the tenant organizations who want to take the hybrid approach of leveraging a cloud-based platform (e.g., server 18 ) to develop/test their application(s) and eventually migrating them for deployment within the respective data centers, and vice versa.
- a cloud-based platform e.g., server 18
- one major drawback of this hybrid approach is that the integration configuration of the tenant application(s) with respect to other applications and/or systems (e.g., data bases) has to be updated each time the tenant application is migrated in/out of the tenant data center.
- enterprise software applications are typically developed and tested by tenants on a server by creating and/or modifying a plurality rules that may be stored in a rules base present on the server.
- rules can define all aspects of such tenant applications including their integration with other applications and/or systems, some of which may be located behind tenant firewalls in the tenant's data center.
- the integration rules for the tenant applications might attempt to obviate the obstacles presented by the firewalls, e.g., by opening multiple ports in the tenant firewall depending upon, e.g., the integration method (e.g., SOAP, .NET, JAVA, EJB etc.) and/or the type of tenant legacy system (e.g., SQL database, web service etc.) that is being linked to the tenant application.
- the integration method e.g., SOAP, .NET, JAVA, EJB etc.
- tenant legacy system e.g., SQL database, web service etc.
- a tenant may develop and test its application within its data center before migrating it outside its firewall for deployment on a cloud-server.
- a rules engine on the server might execute one or more of the plurality of rules that define the application in response to requests/events received by server e.g., from users within a tenant data center.
- the data processed during run-time by such rules could potentially either be stored in the database local to the server or it may be stored in remote tenant data bases that may not be accessible to server (e.g., due to firewalls) to effect the desired processing.
- the conventional prior art approach would require that the integration rules of the tenant application be reconfigured upon migration of the tenant application to the cloud-based server in order to avoid any errors/interruptions during execution of such tenant applications on cloud-based servers due to inaccessibility of the required data and/or other resources.
- FIG. 1 which are configured such that digital data processor 18 operates as a server on a “cloud” platform, e.g., of the type commercially available from Amazon, SalesForce, Google, or other cloud-computing providers.
- a “cloud” platform e.g., of the type commercially available from Amazon, SalesForce, Google, or other cloud-computing providers.
- digital data processors 12 and 14 can be, for example, different “tenant” digital data processors that are in communication with the server 18 over network(s) to access resources (e.g., rules, applications, modules, database, rules bases, data, code, scripts, hardware etc.) that may be either “generic” (i.e., available to users/systems associated with all tenants that are able to connect to the server 18 ) or “tenant-specific” (i.e., only accessible to users/systems associated with a particular tenant).
- resources e.g., rules, applications, modules, database, rules bases, data, code, scripts, hardware etc.
- embodiments of the invention configured as described herein allow tenant organizations to build seamless integration between their enterprise application(s) and the tenant legacy systems without having to reconfigure the application(s) multiple times depending upon where the application(s) is developed, tested and/or deployed. This is accomplished by establishing communication between coordination modules that are installed on the cloud-based server (or wherever the application is developed, tested and/or deployed outside the tenant firewall) as well as within each tenant's data center.
- any of the coordination module 18 d and engine 18 a first authenticate the user by e.g., matching parameters or other indicators of user identification in the request with data related to authorized tenant users previously stored in any of the local data bases (e.g., 18 b , 18 c ), registries, files and elsewhere.
- a coordination module (e.g., 12 d , 14 d ) can be transmitted back in response to their initial request.
- the coordination module that is transmitted back (e.g., 12 d , 14 d ) may be installed on any digital data processor (e.g., 12 , 14 , 11 a ) located behind/protected by the firewall of the tenant organization that the user is associated with.
- the coordination module transmitted back to the authorized tenant user may be installed in the web browser of the digital data processor being used by the tenant user to communicate with server 18 .
- the coordination module e.g., 12 d , 14 d
- the coordination module may prompt the user to provide information related to the tenant legacy systems that may need to be integrated with the tenant application(s) on server 18 . This information is then be transmitted to server 18 where it is stored in any of the local data bases (e.g., 18 b , 18 c ), registries, files and elsewhere.
- any of the authorized developers associated with that tenant organization can configure integration rules for tenant application(s) on server 18 in exactly the same way as if they were developing the integration rules on a digital data processor located within that tenant's data center.
- the legacy system information on server 18 coupled with the communication between coordination module 18 d and the coordination module located within the tenant's data center obviate the need to reconfigure the integration rules to maintain the integration links that are defined by such rules.
- FIG. 3 illustrates operation of an embodiment of the invention and particularly, for example, operation of module 18 d on digital data processor 18 at run-time within a multi-tenant cloud-based environment as described above.
- the module 18 d can be configured to omit a few steps and simplify its operation as compared to the illustrated embodiment in FIG. 2 .
- steps 20 , 24 , 34 , 36 and 44 of the operation depicted in FIG. 2 are omitted in here FIG. 3 for various reasons.
- the platform-as-a-service business model by its very nature typically requires that the service provider (e.g., salesforce.com, Google etc.) provision all required hardware and software components to its tenants.
- the service provider e.g., salesforce.com, Google etc.
- the coordination module may not need to verify the local presence of all required portions of rules engine 18 a in step 24 .
- all requests by users for rule execution on behalf of the tenants at run-time may initially be signaled to and/or received by engine 18 a .
- the rules engine 18 a may also verify the availability of the requested rule before working with module 18 d to access the required data in step 22 . Therefore, even though rules engine 18 a may employ the same techniques as step 20 illustrated in FIG. 2 to verify the local presence of the requested rule, that step 20 can be omitted from the simplified operation of module 18 d in the illustrated embodiment.
- coordination module 18 d will respond to requests for data access in substantially the same way as described previously in connection with FIG. 2 . That is, the module 18 d will verify the local presence of the required data on server 18 using the techniques discussed previously. If locally present, the module will typically defer to the local engine 18 a for local execution the rule on the required data through steps 26 - 30 . On the other hand, if the required data and/or database are not locally present, the coordination module 18 d will attempt to identify the location of the required data in step 32 by checking any of the tenant information, user information, parameters and other indicators of data presence e.g., in the request signaled to the engine 18 a and/or the module 18 d .
- the module 18 d may also check integration rules (if any) that may be referenced by or otherwise related to the requested rule and/or the tenant legacy system information that may be found in a registry, data base or elsewhere on the digital data processor 18 .
- the coordination module 18 d may retrieve the data for local execution of the requested rule(s) and/or transfer the requested rule(s) to the identified tenant location for execution, all as previously discussed in connection with steps 26 - 30 and 40 , 42 and 46 depicted FIG. 2 .
- the coordination module 18 d may only open a single port in the tenant firewall. That is a more secure approach than opening multiple ports (e.g., based on integration methods etc.) as required by the conventional approach described above.
- steps 34 , 36 and 44 from the operation depicted in FIG. 2 are also omitted from the illustrated embodiment in FIG. 3 for the sake of simplicity.
- the identified tenant location e.g., digital data processor 12
- the coordination module 18 d may work with the local coordination module (e.g., 12 d ) at the appropriate tenant data center to identify one or more other digital data processors with the necessary resources within that data center for the execution of the requested rules(s).
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Software Systems (AREA)
- Evolutionary Computation (AREA)
- Computational Linguistics (AREA)
- Artificial Intelligence (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
- The invention relates to digital data processing and, more particularly, for example, to distributed processing of rules bases.
- Computer systems that facilitate business operations based on information specific to an industry or enterprise are well known in the art. These typically rely on rules identifying situations that are expected to arise during enterprise operation and the applicable responses. Such systems have been used in a range of applications, from health care to automotive repair. The rules on which they rely come from experts in the field, from the collective experience of workers on the “front line,” or a combination of these and other sources.
- Though many computer systems of this sort incorporate application-specific knowledge directly into source code (using, for example, a sequence of “if . . . then . . . else” statements, or the like), more complex systems store that knowledge separately from the programs that access it. Some use “rules bases” that store application-specific information in tables, database records, database objects, and so forth. Examples of systems of this type arc disclosed in commonly assigned U.S. Pat. No. 5,826,250, entitled “Rules Bases and Methods of Access Thereof” and U.S. Pat. No. 7,640,222, entitled “Rules Base Systems and Methods with Circumstance Translation,” the teachings of both of which are incorporated herein by reference.
- These and other rules-based business process management (BPM) applications arc commonly used in enterprise computing, for example, where they facilitate a range of business operations, from marketing to manufacturing to distribution to technical support. By way of example, a BPM application can implement data-processing workflows to support the processing of transactional data ranging from customer service requests received by retail and banking enterprises to the routing and resolution of health care claims by insurance enterprises.
- With increasing frequency, enterprise software applications incorporate architectures that permit their use “in the cloud,” that is, over the Internet, with computing resources delivered up to each user on demand. In a sense, this extends the client-server model of past eras from the physical confines of the enterprise to the expanse of the world.
- Where a common architecture of the past might provide for software that executes on a server, e.g., located at enterprise headquarters, and that processes requests entered by support personnel at the enterprise's branch offices, the new cloud architectures permit servicing of requests by servers located around the world. In operation, any given request by a user on a client device might as well be attended to by a server located in a neighboring state as in a neighboring country. Thus, while cloud applications are often initially tested behind an enterprise firewall, they are typically architected for final deployment outside that firewall, on a dynamically changing set of third-party servers (e.g., owned by Amazon, SalesForce, Google, or other cloud-computing providers).
- BPM applications can be deployed in the cloud, like other enterprise applications. However since business process management often goes to the heart of the enterprise, chief executives, IT directors, and corporate boards have yet to fully embrace this model, mainly, for fear that storing rules bases and/or transactional data exposes them to theft or wrongful disclosure.
- Other software applications are evolving similarly. Those that traditionally ran solely on the “desktop,” are now increasingly being executed in the cloud. Word processing is one example. Microsoft, Google and other software providers would as soon enterprise (and other) customers store documents and execute word processing via the cloud, as via locally deployed desktop applications. Unfortunately, this results in uneven usage of information technology resources, with network infrastructure and desktop computers being alternately overwhelmed and underutilized, depending on the cycle of the day, month and year.
- An object of this invention is to provide improved systems and methods for digital data processing. A more particular object is to provide improved systems and methods for business process management, for example, rules processing.
- A further object is to provide such improved systems and methods as facilitate deployment of BPM and other rules-processing applications on multiple digital data processors.
- A still further object is to provide such improved systems and methods as facilitate such deployment in distributed environments, such as, for example, in cloud computing environments.
- Yet a still further object is to provide such improved systems and methods as provide better security for BPM and other rules-processing applications in such distributed environments.
- Still yet a further object is to provide such improved systems and methods as better utilize computing and networking resources in applications so distributed.
- The foregoing are among the objects attained by the invention, which provides in some aspects a distributed rules processing system that includes first and second digital data processors that are coupled to one another by one or more networks. A rules base and a transactional data base are each coupled to one of the digital data processors; both may be coupled to the same digital data processor or otherwise.
- One or more coordination modules (e.g., “proxies”), each of which is associated with a respective one of the digital data processors, makes available to a selected one of those digital data processors from the other of those digital data processors (i) one or more selected rules from the rules base, and/or (ii) one or more data from the transactional database on which those rules are to be executed. The selected digital data processor executes one or more of the selected rules as a rules engine, executes one or more of the selected rules using a rules engine, and/or processes one or more data from the transactional database with rules executing using a rules engine.
- According to related aspects of the invention, the first and second digital data processors of a distributed rules processing system, e.g., of the type described above, can be disposed remotely from one another and can coupled for communication by the Internet, as well optionally by local area networks, wide area networks, and so forth. A firewall and/or other such functionality that is coupled to one or more of those networks prevents the selected digital data processor from accessing from the other digital data processor (i) the selected rules and/or (i) the data on which those rules are to be executed.
- Further related aspects of the invention provide a distributed rules processing system, e.g., of the type described above, wherein one or more of the coordination modules make the selected rules and/or data available to the selected digital data processor from the other digital data processor in response to a request from the rules engine.
- Thus, by way of example, in a system according to the foregoing aspects of the invention, the first digital data processor can include a rules base, e.g., for processing credit card information. The second digital data processor can, likewise, include a data base of transactional data, e.g., pertaining to opening of credit card account, purchases against the credit cards, refunds, and so forth.
- According to one operational scenario of such a system (and to illustrate methods according to further aspects of the invention) a rules engine operating, for example, on the first digital data processor can utilize a proxy operating, for example, on the second digital data processor to access transactional data that is “behind the firewall” on the second digital data processor for processing by the rules engine with rules already accessible to the first data data processor (e.g., on account of its inclusion of and/or coupling to the rules base).
- To that end, by way of non-limiting example, in related aspects of the invention, the coordination modules (or proxies) make the selected rules and/or data available to the selected digital data processor from the other digital data processor by opening one or more communications ports on that other digital data processor.
- Continuing the above example, in a related operational scenario, a coordination module executing on the first data processor can respond to transactional data base access requests generated by the rules engine to determine whether that data base is coupled to the first digital data processor and, if not, to cooperate with the coordination module on the second digital data processor to make the transactional data available to the rules engine from the second digital data processor.
- Conversely, according to the operational scenario of a system paralleling those described in the examples above, a rules engine executing on the second digital data processor can utilize a proxy operating, for example, on the first digital data processor, to access rules necessary to process transactional data already accessible to the data processor (e.g., on account of its inclusion of and/or coupling to the transactional data base).
- In other related aspects, the invention provides a distributed rules processing system, e.g., of the type described above, in which one or more of the coordination modules make the selected rules and/or data available to the selected digital data processor from the other digital data processor in response to a request from that other digital data processor.
- In further related aspects of the invention, a request made from the other digital data processor in a distributed rules processing system, e.g., of type described above, is made by a rules engine executing on that other digital data processor.
- Continuing the example above (and to illustrate methods according to still further aspects of the invention), in a system according to the foregoing aspects of the invention, a rules engine operating on the first digital data processor can utilize the proxy operating on the second digital data processor to access some transactional data in the data base on the second digital data processor for processing by the rules engine on the first digital data processor (and/or, conversely, to store transactional data processed by that rules engine to that transactional data base). It can also effect, through use of that proxy and/or its counterpart on the first digital data processor, transfer of selected rules to the second digital data processor for execution by its rules engine, e.g., on other data stored (and/or to be stored) in the transactional database.
- These and other aspects of the invention are evident in the drawings and in the description that follows.
- A more complete understanding of the invention may be attained by reference to the drawings, in which
-
FIG. 1 depicts a digital data processing system for distributed rules processing according to one practice of the invention; -
FIG. 2 depicts a method of operation of a coordination module in a system ofFIG. 1 ; and -
FIG. 3 depicts operation of a coordination module in a system according to the invention within a multi-tenant cloud-based environment. -
FIG. 1 depicts a digitaldata processing system 10 for distributed processing in a rules-based system according to one practice of the invention. The illustrated system includes client (or “tenant”)digital data processors network 16 for communication with serverdigital data processor 18. - The client
digital data processors - The server
digital data processor 18 is, likewise, a digital data processing apparatus of the type commercially available in the marketplace suitable for operation in the illustrated system as described herein, as adapted in accord with the teachings hereof. Though theserver 18 is typically implemented in a server-class computer, such as a minicomputer, it may also be implemented in a desktop computer, workstation, laptop computer, tablet computer, PDA or other suitable apparatus (again, as adapted in accord with the teachings hereof). -
Network 16 comprises one or more networks suitable for supporting communications among and between illustrateddigital data processors network 16 comprises one or more public networks, specifically, the Internet, though, in other embodiments, it may include (instead or in addition) one or more other networks of the type known in the art, e.g., local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), and or Internet(s). - Illustrated
client computer 12 comprises central processing, memory, storage and input/output units and other constituent components (not shown) of the type conventional in the art that are configured to formapplication 12 a,transaction database 12 b,rules base 12 c, andcoordination module 12 d, in accord with the teachings hereof. One or more of these constituent components, and/or portions thereof, may be absent in various embodiments of the invention. Thus, for example, as suggested by dashed lines, thedigital data processor 12 may not include a rules base. Conversely, it may include a portion of a rules base but not transaction database or it may include neither. In other embodiments, it may include acoordination module 12 d (described below) but not a transaction database, rules base or an application, all by way of non-limiting example. - The central processing, memory, storage and input/output units of client
digital data processor 12 may be configured to form and/or may be supplemented by other elements of the type known in the art desirable or necessary to supportelements 12 a-12 d in accord with the teachings hereof, as well as to support other operations of thedigital data processor 12. These can include, by way of non-limiting example, peripheral devices (such as keyboards and monitors), operating systems, database management systems, and network interface cards and software, e.g., for supporting communications betweendigital data processor 12 and other devices overnetwork 16. -
Digital data processor 12 is coupled tonetwork 16 via firewall 12 e. This is a conventional device of the type known in the art (as otherwise configured in accord with the teachings hereof) suitable for blocking unauthorized access, yet, permitting authorized access, to thedigital data processor 12, including (but not limited to) data and rules bases 12 b, 12 c. - Firewall 12 e, which is constructed and operated in the conventional manner known in the art, may comprise a “hardware” (or stand-alone) firewall and/or it may comprise a software firewall configured from the constituent and/or other components of
digital data processor 12, again, in the conventional manner known in the art. - The constituent components of illustrated client
digital data processor 14 may similarly be configured in accord with the teachings hereof to formapplication 14 a,transaction database 14 b, rules base 14 c, andcoordination module 14 d. As well, they may be supplemented by other elements of the type known in the art desirable or necessary to supportelements 14 a-14 d in accord with the teachings hereof, as well as to support other operations of thedigital data processor 14. The clientdigital data processor 14 may also include a firewall 14 e, e.g., constructed and operated like device 12 e, discussed above, to block unauthorized access, yet, permit authorized access, to thedigital data processor 14, including (but not limited to) data and rules bases 14 b, 14 c. - Although
digital data processors positioned client devices - Like client
digital data processors digital data processor 18 comprises central processing, memory, storage and input/output units and other constituent components (not shown) of the type conventional in the art that are configured in accord with the teachings hereof to formrules engine 18 a,transaction database 18 b, rules base 18 c, andcoordination module 18 d, one or more of which (and/or portions thereof) may be absent in various embodiments of the invention. Thedigital data processor 18 may also include a firewall 18 e, e.g., constructed and operated like device 12 e, discussed above, to block unauthorized access, yet, permit authorized access, to thedigital data processor 18, including (but not limited to) data and rules bases 18 b, 18 c. - Although only a single server
digital data processor 18 is depicted and described here, it will be appreciated that other embodiments may have greater or fewer numbers of these devices disposed near and/or far from one another, collocated behind one or more common firewalls 18 e or otherwise. Indeed, in preferred such embodiments, thedigital data processor 18 is configured as a server on a “cloud” platform, e.g., of the type commercially available from Amazon, SalesForce, Google, or other cloud-computing providers. As above, those other servers may differ in architecture and operation from that shown and described here and/or from each other, all consistent with the teachings hereof. - Rules bases 12 c, 14 c, 18 c comprise conventional rules bases of the type known in the art (albeit configured in accord with the teachings hereof) for storing rules (e.g., scripts, logic, controls, instructions, metadata etc.) and other application-related information in tables, database records, database objects, and so forth. Preferred such rules and rules bases are of the type described in the aforementioned incorporated-by-reference U.S. Pat. No. 5,826,250, entitled “Rules Bases and Methods of Access Thereof” and U.S. Pat. No. 7,640,222, entitled “Rules Base Systems and Methods with Circumstance Translation,” though, rules and rules bases that are architected and/or operated differently may be used as well.
- As noted above, not all of these rules bases may be present in any given embodiment. Conversely, some embodiments may utilize multiples rules bases, e.g., an enterprise-wide rules base 18 c on the
server 18 and domain-specific rules bases on theclient devices - In some embodiments, rules may comprise meta-information structures. These are structures that can include data elements and/or method elements. The latter can be procedural or declarative. In the former regard, for example, such a structure may be procedural insofar as it comprises one or more of a series or ordered steps. In the latter regard, such a structure may be declarative, for example, insofar as it sets forth (declares) a relation between variables, values, and so forth (e.g., a loan rate calculation or a decision-making criterion), or it declares the desired computation and/or result without specifying how the computations should be performed or the result achieved. By way of non-limiting example, the declarative portion of a meta-information structure may declare the desired result of retrieval of a specified value without specifying the data source for the value or a particular query language (e.g., SQL, CQL, .QL etc.) to be used for such retrieval. In other cases, the declarative portion of a meta-information structure may comprise declarative programming language statements (e.g., SQL). Still other types of declarative meta-information structures are possible.
- While some rules may comprise meta-information structures that are wholly procedural and others may comprise those that are wholly declarative, the illustrated embodiment also contemplates rules that comprise both procedural and declarative meta-information structures, i.e., rules that have meta-information structure portions that are declarative, as well as meta-information structure portions that are procedural.
- Furthermore, rules of the illustrated embodiment that comprise meta-information structures may also reference and/or incorporate other such rules, which themselves may, in turn, reference and/or incorporate still other such rules. As a result, editing such rule may affect one or more rules (if any) that incorporate it.
- An advantage of rules that comprise meta-information structures over conventional rules is that they provide users with the flexibility to apply any of code-based and model-driven techniques in the development and modification of software applications and/or computing platforms. Particularly, like models in a model-driven environment, meta-information structures comprise data elements that can be used to define any aspect of a complex system at a higher level of abstraction than source code written in programming languages such as Java or C++. On the other hand, users may also embed programming language statements into meta-information structures if they deem that to be the most efficient design for the system being developed or modified. At run-time, the data elements of the meta-information structures along with programming language statements (if any) are automatically converted into executable code by a rules engine (e.g., 18 a).
- Thus, in some embodiments, rules may be the primary artifacts that get created, stored (e.g., in a rules base) or otherwise manipulated to define and/or modify the overall functionality of rules-based applications that may automate and/or manage various types of work in different business domains at run-time. By way of non-limiting example, a plurality of rules stored in a rules base (e.g., 12 c, 14 c, 18 c) may be configured to define all aspects (e.g., user interface, decision logic, integration framework, process definition, data model, reports, security settings etc.) of a software application. Such a software application may include specialized software that is used within a specific industry or a business function (e.g., human resources, finance, healthcare, telecommunications etc.), or it may include a cross-industry application (e.g., a project management application), or any other type of software application. As the software application executes on a digital data processor (e.g. any of 12, 14 and 18), any portion of the rules that define the application may be retrieved from a rules bases (e.g. any of 12 c, 14 c and 18 c) and processed/executed (e.g., using a
rules engine 18 a as defined below) in response to requests/events signaled to and/or detected by the digital data processor at run-time. -
Transactional data bases - As above, not all of the illustrated transactional data bases may be present in any given embodiment. Conversely, some embodiments may utilize multiple transactional database bases, e.g., an enterprise-
wide data base 18 b on theserver 18 and branch-office specific data bases on theclient devices - Illustrated
digital data processor 18 also includesrules engine 18 a of the type conventionally known in the art (albeit configured in accord with the teachings hereof) for use in processing/executing rules from a rules base in order to process data in (and/or for storage to) a transactional database, e.g., in connection with events signaled to and/or detected by the engine. Preferred such rules engines are of the type described in the aforementioned incorporated-by-reference U.S. Pat. No. 5,826,250, entitled “Rules Bases and Methods of Access Thereof” and U.S. Pat. No. 7,640,222, entitled “Rules Base Systems and Methods with Circumstance Translation” and/or U.S. patent application Ser. No. 11/681,269, filed Mar. 2, 2007, entitled “Proactive Performance Management For Multi-User Enterprise Software Systems,” the teachings too of which are incorporated by reference herein—all as adapted in accord without the teachings hereof. - The
rules engine 18 a may be implemented in a single software program, in multiple software programs/modules, or a combination of software modules/programs. Moreover, it may comprise programming instructions, scripts, or rules (e.g., rules stored in rules base 18 c) and/or a combination thereof. - Though, in the illustrated embodiment in
FIG. 1 , therules engine 18 a executes on theserver 18, in other embodiments, the techniques described herein may be employed to execute therules engine 18 a on or over multiple digital data processors (e.g., 12, 14 and 18). For instance, therules engine 18 a may initially be invoked for execution on a single digital data processor (e.g., 18). Subsequently, portions of it (or, potentially, the entirety of it) may be apportioned, distributed and executed over multiple digital data processors using the techniques described herein. - Such distributed execution of the rules engine can be advantageous, by way of non-limiting example, when execution of an enterprise-wide BPM application necessitates access to sensitive corporate or personal data during intermediate processing steps. For example, in an enterprise with decentralized record-keeping, the
rules engine 18 a can be utilized to generate a summary report that requires analysis of sensitive personnel-related data maintained in local branch offices. To that end, theengine 18 a executes rules for performing preparatory tasks, such as, zeroing out data collection variables and identifying local offices to be queried. Theengine 18 a also retrieves from rules base 18 c or otherwise generate rules that will serve as rules engines (e.g., 12 a, 14 a) customized or otherwise suited for execution on digitaldata processing equipment engines equipment server 18 for reporting the BPM application executing there. Such distributed execution has the advantage of permitting the BPM application executing usingengine 18 a to generate an enterprise-wide report, without necessitating the transmission of sensitive data outside the confines of the local offices. - By way of further example, the
rules engine 18 a can have two distinct portions, e.g., one that embodies the algorithm for rule selection (e.g., in the manner of the rule finder disclosed in U.S. Pat. No. 5,825,260, assigned to the assignee hereof and incorporated by reference herein), and the other that generates/executes the executable code once the requisite rule has been selected. Therules engine 18 a (or other functionality) can apportion and distributed these portions separately as required. - Take, for example, an instance where
server 18 gets a request for executing a “loan validation” process for a specific context.Server 18 stores rules for multiple versions of the “loan validation” process for different contexts. However, the server does not have the computing power to execute the ‘rule finder’ algorithm to select the right version and/or the server doesn't have the code generation portion of the engine to execute the selected rule. Server retrieves the rules for all versions of “loan validation” process and transmits them along with the rule selection portion of the engine to a remote digital data processor that has installed thereon the code generation portion of a rules engine. Upon receiving the rule finder portion of the engine along with the rules for all versions, the correct loan validation process is selected and executed on the target digital data processor. - The foregoing are examples those skilled in the art will appreciate that still other ways of implementing/executing the
rules engine 18 a are possible. By way of non-limiting example, therules engine 18 a may have additional distinct components/portions that can be apportioned and distributed separately. These may include (but are not limited to) a data access component used for processing data during rule execution, a session management component for keeping track of activity across sessions of interaction with a digital data processor and/or a performance monitoring component for monitoring and interacting with various system resources/event logs in order to manage performance thresholds. Still other types of distinct components/portions may be part of therules engine 18 a. -
Applications digital data processors such applications rules engine 18 a, in other embodiments they embody a subset of the functionality ofengine 18 a, e.g., suited to the processing resources and/or demands of thedigital data processors such applications rules engine 18 a, again, for example, suited to the processing resources and/or demands of thedigital data processors - For sake of simplicity, the discussion that follows focuses on aspects of operation of
rules engine 18 a; it will be appreciated that other rules engines (e.g., 12 a, 14 a in certain embodiments) may operate similarly in these regards. - As noted above,
rules engine 18 a processes/executes rules from a rules base in order to process data in (and/or for storage to) a transactional database. In instances where theengine 18 a executes rules from rules base 18 c in order to process data in (and/or store data to)database 18 b, theengine 18 a may operate in the conventional manner known in the art. However, where any of (i) the data to be accessed (or stored) is resident in adata base rules engine 18 a or a portion thereof) are contained in a rules base 12 c, 14 c of another of those digital data processors, and (iii) the rules (again, potentially, those defining therules engine 18 a or a portion thereof) are to be executed using therules engine rules engine 18 a works with one or more of the coordination modules to effect the desired processing. Even in instances where the rules, portions of the engine, and/or data required to effect the desired processing is local todigital data processor 18, therules engine 18 a may work with the coordination modules (e.g., 12 d, 14 d, 18 d) to effect the desired processing over multiple digital data processors (e.g., for access to more computing resources/power) in accord with the teachings hereof. - In this regard,
coordination modules respective processors - As above, not all of the
coordination modules - The
modules digital data processors rules engine 18 a and/orapplications respective devices such modules - Still further, although the
modules digital data processors respective processors - Operation of a
coordination module 18 d in accord with one practice of the invention is illustrated inFIG. 2 . It will be appreciated that the sequence of steps shown in that drawing and discussed below is by way of example and that other embodiments may perform the same or different functions using alternate sequences of steps. - In
step 20, the module, which may be coupled to alocal rules engine 18 a, responds to a request for access to a rule by determining if that rule is present in a rules base 18 c local to thedigital data processor 18—and, for example, it is therefore accessible to alocal engine 18 a without crossing the firewall 12 e, 14 e of another digital data processor. Themodule 18 d can make that determination by checking for the presence of the local rules base 18 c and/or, if present, by determining if the requested rule itself is present. Alternatively, or in addition, themodule 18 d can make the determination by checking parameters or other indicators of rule presence, e.g., in the rule request signaled to any of themodule 18 a and theengine 18 a and/or request made by theengine 18 a. The parameters or other indicators of rule presence may also be found in a registry of thedigital data processor 18 and/or elsewhere. - If the determination of
step 20 is in the affirmative, operation proceeds to step 22, where themodule 18 d determines if data implicated by the rule (e.g., data to be processed by the rule or otherwise necessary for its execution) is present in adata base 18 b local to thedigital data processor 18—and, again, for example, it is therefore accessible to thelocal engine 18 a without crossing the firewall 12 e, 14 e of another digital data processor. Themodule 18 d can make that determination by checking for the presence of thelocal data base 18 b and/or, if present, by determining if the requested data are present. Alternatively, or in addition, themodule 18 d can make the determination by checking parameters or other indicators of data presence, e.g., in the rule request signaled to any of themodule 18 d and theengine 18 a and/or request made by theengine 18 a. The parameters or other indicators of rule presence may also be found in a registry of thedigital data processor 18 and/or elsewhere. - If the determination of
step 22 is affirmative, operation proceeds to step 24, where themodule 18 d determines if the portion of rules engine (e.g., 18 a) that is required to execute the requested rule is present locally ondigital data processor 18. To this end, the module can query for local presence ondigital data processor 18 of component(s)/module(s) that make up requisite portions(s) of rules engine. In other embodiments, e.g., where those requisite portion(s) are implemented using rules, themodule 18 d can determine, for example, if those rules are locally present by querying a local database/repository (e.g., rules base 18 c,transaction data base 18 b). Alternatively, or in addition, the module can check parameters or other indicators of engine presence, e.g., in the rule request signaled to any of themodule 18 d and theengine 18 a and/or request made by theengine 18 a, in a registry of thedigital data processor 18 and/or elsewhere. - If the determination of
step 24 is in the affirmative, operation proceeds to step 26, where themodule 18 d determines if the rule is to be executed locally, i.e., ondigital data processor 18 or whether it is to be executed remotely, e.g., ondigital data processors module 18 d can make that determination using a variety of methods including, but not limited to, querying a local rules engine (e.g., 18 a) and/or by checking parameters or other indicators, e.g., in the rule request signaled to any of themodule 18 d and theengine 18 a and/or request made by theengine 18 a. The parameters or other indicators of rule presence may also be found in a registry of thedigital data processor 18 and/or elsewhere. Alternatively, or in addition, themodule 18 d can make the determination based on load-balancing, network speed and traffic, data coherency or other factors within the ken of those of ordinary skill in the art based on the teachings hereof. - If the determination in
steps digital data processor 18 and the rule is to be executed there, the determination instep 28 is affirmative and the operation proceeds to step 30, where themodule 18 d defers tolocal engine 18 a for execution of the requested rule on the required data. Theengine 18 a (or the required portion thereof) proceeds by accessing the rule and data in the local rules anddata bases - If the determination in any of
steps digital data processor 18, the operation proceeds to step 32, where the module queries one or more other digital data processors (e.g., 12, 14) to determine the location(s) of any of the requested rule, required data and engine (or portion thereof). By way of non-limiting example, themodule 18 d can determine the location of the requested rule (and corresponding rules base), required data and engine (or portion thereof) by checking parameters or other indicators, e.g., in the rule request signaled to any of themodule 18 d and theengine 18 a and/or request made by theengine 18 a, in a registry of thedigital data processor 18 and/or elsewhere. Alternatively, or in addition,module 18 d can query thedigital data processors module 18 d and itscounterparts digital data processors modules digital data processor - If the determination in
step 32 is in the negative for any of the required/requested resources, the operation proceeds to and terminates atstep 38 where the coordination module returns an error message in response to the requested rule indicating the absence or unavailability of any of the requested rule, required data and engine (or portion thereof). - If the determination in
step 32 is in the affirmative for any of the requested/required resources that were not already present locally at digital data processor 18 (as previously determined by steps 20-24), the operation proceeds to step 26 to make the decision of local versus remote execution of the requested rule as described above. If the determination instep 26 is affirmative, at least one of the requested rule, required data and engine (or portion thereof) that is located remotely at another digital data processor (e.g., 12 or 14) as identified instep 32, is retrieved instep 40 before executing the requested rule locally ondigital data processor 18 in step 30. As indicated by the callout 46, such retrieval is performed by themodule 18 d, following a negative determination instep 28 by (i) validating that the one or more digital data processors identified in step 32 (e.g., 12 and/or 14) will grant access to the requested/required resource(s) and, (ii) retrieving that/those resource(s) from those one or more digital data processors (i.e., 12 and/or 14) todigital data processor 18. - In regard to step 40(i), the
module 18 d can validate that the one or more identified digital data processors will grant access by querying the digital data processor(s) identified instep 32 accordingly. This can be done, for example, through communication with themodule - In regard to step 40(ii), the
module 18 d retrieves and/or transfers the requested/required resource from the one or more identified digital data processors todigital data processor 18 for local execution. In some embodiments, alocal rules engine 18 d (if already present) may access the requested/required resource (e.g., data, transaction database, rule and/or rules base) directly from the identified digital data processor, e.g., via a port opened in step 40(i). In other embodiments, themodule 18 d may also transfer one or more requested/required resources to an identified digital data processor (e.g., 12 or 14) for the requested processing to be performed remotely at the identified digital data processor. Alternatively, or in addition, themodule 18 d may also notify the identified digital data processor (e.g., 12 or 14) and, preferably, its respective coordination module, identified instep 32, passing to it the relevant information for the requested processing to be performed (e.g., identity of the rule to be executed). The identified digital data processor may perform the requested processing using the resources/information provided to it. In other embodiments where the required resources are not transferred along with the relevant information, the identified digital data processor may perform the requested processing by utilizing the methodology ofFIG. 2 itself in order to access the required resources in connection therewith. The discussion that follows provides further details about this step. - Upon completion of
step 40, control transfers to any ofsteps coordination module 18 d, as indicated in the drawing. Thus, continuing with the current example of retrieving requested/required resources instep 40 from one or more identified digital data processors (e.g., 12 and/or 14) for local execution atdigital data processor 18, control transfers to step 30 to complete the requested processing. However, if the determination instep 26 is in the negative—that is, it is determined that the requested rule is to be executed remotely, then the appropriate location for the completion of such remote processing is based upon a combination of steps 34-44 as well as the outcome of previous steps 20-24. - By way of non-limiting example, despite the local presence of all the requested/required resources on digital data processor 18 (i.e., affirmative responses in steps 20-24), a negative determination in
step 26 may be due to parameters or other indicators in a local registry of thedigital data processor 18 and/or e.g., in the rule request signaled to any of themodule 18 d and theengine 18 a and/or request made by theengine 18 a. In this case, there is no previously identified location fromstep 32. Thus, the response to step 34 is in the negative and the operation proceeds to step 36 where themodule 18 d determines if there is another digital data processor (e.g., 12, 14) suited for executing the requested rule. In some embodiments, it makes that determination by querying thelocal rules engine 18 a and/or by checking the parameters or other indicators as mentioned above. Alternatively, or in addition, themodule 18 d can make the determination based on load-balancing, network speed and traffic, availability of the required/requested resources (or portions thereof) on one or more other digital data processors, data coherency or other factors within the ken of those of ordinary skill in the art based on the teachings hereof. For example, a query during the operation at step 36 (or at a prior step) may reveal that an alternative digital data processor with higher computing power thanprocessor 18 and/or another digital data processor identified in a local registry, has all of the required/requested resources. In that case,module 18 d may simply notify the alternative digital data processor (and/or its coordination module) to perform the requested processing as opposed to performing it locally or remotely at the other digital data processor that was identified in the local registry. More generally, this example is also reflective of some embodiments discussed throughout this document that may involve scenarios and/or steps where duplicate versions, or at least versions that are comparable in terms of functionality, of one or more requested/required resources may exist at multiple locations - If the determination in step 36 is negative, the operation proceeds to and terminates at
step 38 in the illustrated embodiment where thecoordination module 18 d returns an error message indicating the absence or unavailability of a suitable digital data processor for remote execution of the requested processing/rule. In other embodiments, if the requested/required resources are present locally, the coordination module may ignore the negative outcome ofstep 26 and execute the requested rule locally as default if a suitable remote digital data processor (e.g., 12 and 14) is not identified in step 36. - If the determination in step 36 is in the affirmative,
coordination module 18 d any of transfers the requested/required resources from thedigital data processor 18 and/or provides the relevant information to the other identified digital data processor in step 36 e.g., by employing the methodology discussed above in connection with steps 40(i) and (ii). In some embodiments,coordination module 18 d may only transfer a portion of the requested/required resources if it is determined (as mentioned above) that another identified digital data processor(s) already possesses the remaining portion of the requested/required resources. Once any such transfer and/or notification is completed instep 40 fromdigital data processor 18, processing is completed by executing the requested rule remotely instep 44 at the other digital data processor that is identified in step 36. - Preceding the negative determination in
step 26, a negative outcome in any of steps 20-24 indicates that at least one of the requested/required resources is not locally present ondigital data processor 18 and that one or more digital data processors (e.g., 12 and/or 14) may have been identified instep 32 to locate such requested/required resource as previously discussed. In situations where (i) at least one but not all of the determinations in steps 20-24 are in the affirmative, (ii) the determination instep 26 is in the negative, and (iii) the determination in step 34 is affirmative, the operation proceeds to remotely execute the requested rule. If only one digital data processor was identified instep 32, thenmodule 18 d transfers the portion of the requested/required resources at digital data processor 18 (e.g., by employing the methodology discussed above in connection with steps 40(i) and (ii)) to the single digital data processor identified instep 32, where the remaining requested/required resources are located. Once that transfer is completed instep 40, the requested rule/processing is performed remotely instep 42 at the location identified instep 32. - In other embodiments, two or more locations may be identified in
step 32 e.g., the required data may be located atdigital data processor 12 and the engine may be located atdigital data processor 14. In such embodiments, where thestep 26 response is negative and the step 34 response is affirmative,module 18 d may prioritize all available location options based upon various factors including, but not limited to, prioritization criteria specified in the rule request signaled tomodule 18 d and/or theengine 18 a, prioritization rules stored in rules base 18 c and/or elsewhere ondigital data processor 18. Alternatively, or in addition,module 18 d may prioritize all available location options based upon the relative computing resources (e.g., CPU, memory etc.) at each location, network traffic or any other factors within the ken of those of ordinary skill in the art based on the teachings hereof. In any event,module 18 d will transfer the portion of the requested/required resources fromdigital data processor 18 to the highest priority location and once the transfer(s) is completed instep 40, the requested rule/processing is performed remotely at that location instep 42. - A negative determination in
step 26 may be followed by a negative determination in step 34. Following the combined negative determinations, an attempt is made via step 36 (as described above) to identify one or more digital data processors other thanlocal processor 18 or the one or more digital data processors identified instep 32. - By way of example, a request may be signaled to
coordination module 18 d to execute one or more rules that define a plurality of reports. These report rules may be stored locally in rules base 18 c and therules engine 18 a required to execute the requested report rules may also be locally present on serverdigital data processor 18. However, the determination instep 22 may be in the negative because the data to be processed by the requested report rules is not locally present. In such an instance, operation proceeds to step 32 where thecoordination module 18 d attempts to locate the one or more digital data processors that maintain the required data for reports execution. In one embodiment, thecoordination module 18 d identifies the location of such digital data processors (e.g., 12, 14) by querying a local registry ondigital data processor 18 using parameters or other indicators of data location specified in the rule request that was signaled to thecoordination module 18 d. The query of the local registry may, for example, reveal that a portion of the required data is located in thetransaction database 12 b ondigital data processor 12 and the remaining portion of the required data is located in thetransaction database 14 b ondigital data processor 14. Next, operation proceeds to step 26 where it may be determined, for example, that the reports will not be executed locally atdigital data processor 18 because a pre-requisite for such local execution is data retrieval fromdigital data processors step 26 is followed by a determination in step 34 of whether to execute the requested report rules remotely ondigital data processor digital data processors 12, 14 (e.g., as determined by the registry query mentioned above) and the requested rules can be apportioned to be separately executed at both locations, the operation may proceed throughsteps engine 18 a may be transferred appropriately todigital data processors engine 18 a, to a single digital data processor for execution. In that case, the transfer destination may, for example, be determined based upon a higher CPU speed or any other factor. - As previously mentioned, a retrieval and/or transfer of rules, engine or data between
digital data processors coordination modules - Once the ports are opened, the
digital data processors digital data processor 12 is to execute the requested report rules,module 18 d retrieves the required data portion and/ortransaction data base 14 b fromdigital data processor 14 and transfers it to thedigital data processor 12. Furthermore, the requested report rules and the requiredengine 18 a are transferred fromdigital data processor 18 to the targetdigital data processor 12. Once such retrieval and transfer is completed, the requested report rules are executed instep 42. - In some embodiments, local registries, files or databases (e.g., 12 b, 12 c, 14 b, 14 c, 18 b, 18 c) on any of
digital data processors digital data processors engine 18 a are transferred fromdigital data processor 18 todigital data processor 12 in the example above, the local registries on any ofdigital data processors coordination module 18 d is adjusted accordingly to respond to subsequent requests for execution of those report rules that are any of signaled to and received by the module and/ordigital data processor 18. - It will be appreciated that the illustrated embodiment of the operation of
coordination module 18 d inFIG. 2 is merely exemplary and that certain steps may be omitted, modified or re-ordered without departing from the scope of the disclosure herein. In some embodiments, for example, any of themodules - By way of non-limiting example, the systems and techniques described herein may be used for provisioning a computing platform as a service (e.g., commercially available Platform-as-a-Service or “PaaS” offerings) over the internet to multiple concurrent users (e.g., from different companies or “tenant” organizations) for application development, testing and/or deployment in a way that provides more flexibility and ease of use without sacrificing data security as compared to the conventional technology/tools available on the market today.
- In one such embodiment, the
server 18 depicted inFIG. 1 is configured as a cloud-based computing platform comprising hardware and software components (e.g., business process management software) that are used byusers 11 from one or more tenant organizations over the internet (e.g., network 16) to develop, test and/or deploy their enterprise applications. Such shared use of resources among multiple tenant organizations on a cloud-based server (e.g., 18) allows each respective tenant to quickly develop, test and deploy their applications while avoiding the cost and complexity of buying the underlying hardware and software components and hosting them in their own data centers. - Despite its many benefits, the multi-tenant architecture have traditionally presented significant challenges related to data security and integration between cloud-based application(s) and the legacy systems/resources located within each of the respective tenants' data centers. These challenges are exacerbated by the business need of many of the tenant organizations who want to take the hybrid approach of leveraging a cloud-based platform (e.g., server 18) to develop/test their application(s) and eventually migrating them for deployment within the respective data centers, and vice versa. Given the prior state of the technology, one major drawback of this hybrid approach is that the integration configuration of the tenant application(s) with respect to other applications and/or systems (e.g., data bases) has to be updated each time the tenant application is migrated in/out of the tenant data center.
- Thus, for example, enterprise software applications are typically developed and tested by tenants on a server by creating and/or modifying a plurality rules that may be stored in a rules base present on the server. These rules can define all aspects of such tenant applications including their integration with other applications and/or systems, some of which may be located behind tenant firewalls in the tenant's data center. Thus, in order to enable communication between a tenant application on server and other applications, systems and/or functionality located behind tenant firewalls (hereinafter collectively referred to as “tenant legacy systems”), the integration rules for the tenant applications might attempt to obviate the obstacles presented by the firewalls, e.g., by opening multiple ports in the tenant firewall depending upon, e.g., the integration method (e.g., SOAP, .NET, JAVA, EJB etc.) and/or the type of tenant legacy system (e.g., SQL database, web service etc.) that is being linked to the tenant application. If that same tenant application is then subsequently deployed within the tenant's data center (i.e., within the tenant firewalls), the integration rules for that application must be reconfigured to establish the direct link between the tenant application and the tenant legacy systems without any intermediate firewall.
- Similarly, a tenant may develop and test its application within its data center before migrating it outside its firewall for deployment on a cloud-server. At run-time of the application, a rules engine on the server might execute one or more of the plurality of rules that define the application in response to requests/events received by server e.g., from users within a tenant data center. The data processed during run-time by such rules could potentially either be stored in the database local to the server or it may be stored in remote tenant data bases that may not be accessible to server (e.g., due to firewalls) to effect the desired processing. In such a system, the conventional prior art approach would require that the integration rules of the tenant application be reconfigured upon migration of the tenant application to the cloud-based server in order to avoid any errors/interruptions during execution of such tenant applications on cloud-based servers due to inaccessibility of the required data and/or other resources.
- Systems and techniques described herein overcome these drawbacks, for example, when configured as described below, by allowing tenant organizations to simulate their data center environment on an external cloud-based infrastructure (e.g., server 18), thus obviating the need to reconfigure the integration framework of the tenant application(s) upon migration.
- This and other benefits of the systems and techniques described herein become apparent in embodiments of the type illustrated
FIG. 1 which are configured such thatdigital data processor 18 operates as a server on a “cloud” platform, e.g., of the type commercially available from Amazon, SalesForce, Google, or other cloud-computing providers. In such embodiments,digital data processors server 18 over network(s) to access resources (e.g., rules, applications, modules, database, rules bases, data, code, scripts, hardware etc.) that may be either “generic” (i.e., available to users/systems associated with all tenants that are able to connect to the server 18) or “tenant-specific” (i.e., only accessible to users/systems associated with a particular tenant). - As a departure from the conventional approach mentioned above, embodiments of the invention configured as described herein allow tenant organizations to build seamless integration between their enterprise application(s) and the tenant legacy systems without having to reconfigure the application(s) multiple times depending upon where the application(s) is developed, tested and/or deployed. This is accomplished by establishing communication between coordination modules that are installed on the cloud-based server (or wherever the application is developed, tested and/or deployed outside the tenant firewall) as well as within each tenant's data center.
- Accordingly, for example, the first time a
user 11 signals/sends a request (e.g., HTTP request or otherwise) using digital data processor (e.g., 12, 14, 11 a) to access any of the resources that are located on theserver 18, any of thecoordination module 18 d andengine 18 a first authenticate the user by e.g., matching parameters or other indicators of user identification in the request with data related to authorized tenant users previously stored in any of the local data bases (e.g., 18 b, 18 c), registries, files and elsewhere. If the user is authenticated/verified as an authorized user who is able to access resources onserver 18 on behalf of a tenant organization, a coordination module (e.g., 12 d, 14 d) can be transmitted back in response to their initial request. The coordination module that is transmitted back (e.g., 12 d, 14 d) may be installed on any digital data processor (e.g., 12, 14, 11 a) located behind/protected by the firewall of the tenant organization that the user is associated with. In one embodiment, the coordination module transmitted back to the authorized tenant user may be installed in the web browser of the digital data processor being used by the tenant user to communicate withserver 18. Upon installation, the coordination module (e.g., 12 d, 14 d) may prompt the user to provide information related to the tenant legacy systems that may need to be integrated with the tenant application(s) onserver 18. This information is then be transmitted toserver 18 where it is stored in any of the local data bases (e.g., 18 b, 18 c), registries, files and elsewhere. - Thus, when an authorized user starts to develop and test applications on
server 18 on behalf of tenant organizations and stores the legacy system information for that tenant on theserver 18, any of the authorized developers associated with that tenant organization can configure integration rules for tenant application(s) onserver 18 in exactly the same way as if they were developing the integration rules on a digital data processor located within that tenant's data center. Similarly, even if the integration rules were first built within that tenant's data center and then later migrated toserver 18, the legacy system information onserver 18 coupled with the communication betweencoordination module 18 d and the coordination module located within the tenant's data center (e.g., 12 d, 14 d) obviate the need to reconfigure the integration rules to maintain the integration links that are defined by such rules. -
FIG. 3 illustrates operation of an embodiment of the invention and particularly, for example, operation ofmodule 18 d ondigital data processor 18 at run-time within a multi-tenant cloud-based environment as described above. In one such embodiment, themodule 18 d can be configured to omit a few steps and simplify its operation as compared to the illustrated embodiment inFIG. 2 . Namely steps 20, 24, 34, 36 and 44 of the operation depicted inFIG. 2 are omitted in hereFIG. 3 for various reasons. For example, the platform-as-a-service business model by its very nature typically requires that the service provider (e.g., salesforce.com, Google etc.) provision all required hardware and software components to its tenants. Thus, the coordination module may not need to verify the local presence of all required portions ofrules engine 18 a instep 24. In fact, all requests by users for rule execution on behalf of the tenants at run-time may initially be signaled to and/or received byengine 18 a. After the authentication/verification process (as described above) for the user making the request, therules engine 18 a may also verify the availability of the requested rule before working withmodule 18 d to access the required data instep 22. Therefore, even thoughrules engine 18 a may employ the same techniques asstep 20 illustrated inFIG. 2 to verify the local presence of the requested rule, that step 20 can be omitted from the simplified operation ofmodule 18 d in the illustrated embodiment. - Once the verification process related to user authentication and local rule presence is completed,
coordination module 18 d will respond to requests for data access in substantially the same way as described previously in connection withFIG. 2 . That is, themodule 18 d will verify the local presence of the required data onserver 18 using the techniques discussed previously. If locally present, the module will typically defer to thelocal engine 18 a for local execution the rule on the required data through steps 26-30. On the other hand, if the required data and/or database are not locally present, thecoordination module 18 d will attempt to identify the location of the required data instep 32 by checking any of the tenant information, user information, parameters and other indicators of data presence e.g., in the request signaled to theengine 18 a and/or themodule 18 d. In addition or instead, themodule 18 d may also check integration rules (if any) that may be referenced by or otherwise related to the requested rule and/or the tenant legacy system information that may be found in a registry, data base or elsewhere on thedigital data processor 18. Once the appropriate tenant location of the required data is identified instep 32, thecoordination module 18 d may retrieve the data for local execution of the requested rule(s) and/or transfer the requested rule(s) to the identified tenant location for execution, all as previously discussed in connection with steps 26-30 and 40, 42 and 46 depictedFIG. 2 . - It will be appreciated that while effecting any of notifications, transfers and retrieval of data and/or rules in
step 40 of the illustrated embodiment, thecoordination module 18 d may only open a single port in the tenant firewall. That is a more secure approach than opening multiple ports (e.g., based on integration methods etc.) as required by the conventional approach described above. - It will be appreciated that
steps 34, 36 and 44 from the operation depicted inFIG. 2 are also omitted from the illustrated embodiment inFIG. 3 for the sake of simplicity. It is entirely possible, for example, that the identified tenant location (e.g., digital data processor 12) instep 32 may not have the required resources (e.g., computing power and/or rules engine) for the requested rule(s) execution. In that case, thecoordination module 18 d may work with the local coordination module (e.g., 12 d) at the appropriate tenant data center to identify one or more other digital data processors with the necessary resources within that data center for the execution of the requested rules(s). - Described above are systems and methods meeting the foregoing objects. It will be appreciated that the embodiment illustrated and described herein are merely examples of the invention and other embodiments incorporating changes thereto fall within the scope thereof.
Claims (5)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/527,348 US9270743B2 (en) | 2011-02-18 | 2014-10-29 | Systems and methods for distributed rules processing |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/031,097 US8880487B1 (en) | 2011-02-18 | 2011-02-18 | Systems and methods for distributed rules processing |
US14/527,348 US9270743B2 (en) | 2011-02-18 | 2014-10-29 | Systems and methods for distributed rules processing |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/031,097 Continuation US8880487B1 (en) | 2011-02-18 | 2011-02-18 | Systems and methods for distributed rules processing |
Publications (2)
Publication Number | Publication Date |
---|---|
US20150127736A1 true US20150127736A1 (en) | 2015-05-07 |
US9270743B2 US9270743B2 (en) | 2016-02-23 |
Family
ID=51798319
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/031,097 Active US8880487B1 (en) | 2011-02-18 | 2011-02-18 | Systems and methods for distributed rules processing |
US14/527,348 Active US9270743B2 (en) | 2011-02-18 | 2014-10-29 | Systems and methods for distributed rules processing |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/031,097 Active US8880487B1 (en) | 2011-02-18 | 2011-02-18 | Systems and methods for distributed rules processing |
Country Status (1)
Country | Link |
---|---|
US (2) | US8880487B1 (en) |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9658735B2 (en) | 2006-03-30 | 2017-05-23 | Pegasystems Inc. | Methods and apparatus for user interface optimization |
US9678719B1 (en) | 2009-03-30 | 2017-06-13 | Pegasystems Inc. | System and software for creation and modification of software |
US10467200B1 (en) | 2009-03-12 | 2019-11-05 | Pegasystems, Inc. | Techniques for dynamic data processing |
US10469396B2 (en) | 2014-10-10 | 2019-11-05 | Pegasystems, Inc. | Event processing with enhanced throughput |
EP3611616A1 (en) | 2018-08-14 | 2020-02-19 | Pegasystems Inc. | Software code optimizer and method |
US10572236B2 (en) | 2011-12-30 | 2020-02-25 | Pegasystems, Inc. | System and method for updating or modifying an application without manual coding |
US10698599B2 (en) | 2016-06-03 | 2020-06-30 | Pegasystems, Inc. | Connecting graphical shapes using gestures |
US10698647B2 (en) | 2016-07-11 | 2020-06-30 | Pegasystems Inc. | Selective sharing for collaborative application usage |
US11038967B2 (en) * | 2017-01-26 | 2021-06-15 | Verizon Patent And Licensing Inc. | Enabling hypertext transfer protocol (HTTP) connect in association with a toll-free data service |
WO2021234474A1 (en) * | 2020-05-19 | 2021-11-25 | International Business Machines Corporation | Rule distribution across instances of rules engine |
US11567945B1 (en) | 2020-08-27 | 2023-01-31 | Pegasystems Inc. | Customized digital content generation systems and methods |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8250525B2 (en) | 2007-03-02 | 2012-08-21 | Pegasystems Inc. | Proactive performance management for multi-user enterprise software systems |
US8880487B1 (en) | 2011-02-18 | 2014-11-04 | Pegasystems Inc. | Systems and methods for distributed rules processing |
CN104067258A (en) * | 2012-04-26 | 2014-09-24 | 惠普发展公司,有限责任合伙企业 | Platform runtime abstraction |
US9621554B2 (en) * | 2012-06-26 | 2017-04-11 | Cisco Technology, Inc. | Method for propagating access policies |
US9684597B1 (en) * | 2014-08-07 | 2017-06-20 | Chelsio Communications, Inc. | Distributed cache coherent shared memory controller integrated with a protocol offload network interface card |
WO2016054661A1 (en) * | 2014-10-03 | 2016-04-07 | Jingit Holdings, Llc | Fpga based data and currency exchange |
US11381662B2 (en) * | 2015-12-28 | 2022-07-05 | Sap Se | Transition of business-object based application architecture via dynamic feature check |
US10613919B1 (en) | 2019-10-28 | 2020-04-07 | Capital One Services, Llc | System and method for data error notification in interconnected data production systems |
US11082487B1 (en) * | 2020-09-22 | 2021-08-03 | Vignet Incorporated | Data sharing across decentralized clinical trials using customized data access policies |
US12007870B1 (en) | 2022-11-03 | 2024-06-11 | Vignet Incorporated | Monitoring and adjusting data collection from remote participants for health research |
US11790107B1 (en) | 2022-11-03 | 2023-10-17 | Vignet Incorporated | Data sharing platform for researchers conducting clinical trials |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6098172A (en) * | 1997-09-12 | 2000-08-01 | Lucent Technologies Inc. | Methods and apparatus for a computer network firewall with proxy reflection |
US6810429B1 (en) * | 2000-02-03 | 2004-10-26 | Mitsubishi Electric Research Laboratories, Inc. | Enterprise integration system |
US20070130130A1 (en) * | 2005-12-02 | 2007-06-07 | Salesforce.Com, Inc. | Systems and methods for securing customer data in a multi-tenant environment |
US20120041921A1 (en) * | 2010-08-16 | 2012-02-16 | Salesforce.Com, Inc. | Mechanism for facilitating efficient business rules management and data processing |
Family Cites Families (591)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4344142A (en) | 1974-05-23 | 1982-08-10 | Federal-Mogul Corporation | Direct digital control of rubber molding presses |
US4047059A (en) | 1976-05-24 | 1977-09-06 | Rca Corporation | Comparator circuit |
US4602168A (en) | 1984-03-28 | 1986-07-22 | National Semiconductor Corporation | Low offset CMOS comparator circuit |
US4701130A (en) | 1985-01-11 | 1987-10-20 | Access Learning Technology Corporation | Software training system |
US4607232A (en) | 1985-04-01 | 1986-08-19 | Raytheon Company | Low voltage amplifier circuit |
US4659944A (en) | 1985-04-08 | 1987-04-21 | Motorola, Inc. | High voltage detection circuit |
US5267175A (en) | 1986-09-12 | 1993-11-30 | Digital Equipment Corporation | Data base access mechanism for rules utilized by a synthesis procedure for logic circuit design |
US5062060A (en) | 1987-01-05 | 1991-10-29 | Motorola Inc. | Computer human interface comprising user-adjustable window for displaying or printing information |
US4930071A (en) | 1987-06-19 | 1990-05-29 | Intellicorp, Inc. | Method for integrating a knowledge-based system with an arbitrary database system |
US4866634A (en) | 1987-08-10 | 1989-09-12 | Syntelligence | Data-driven, functional expert system shell |
US4884217A (en) | 1987-09-30 | 1989-11-28 | E. I. Du Pont De Nemours And Company | Expert system with three classes of rules |
US4895518A (en) | 1987-11-02 | 1990-01-23 | The University Of Michigan | Computerized diagnostic reasoning evaluation system |
US5136523A (en) | 1988-06-30 | 1992-08-04 | Digital Equipment Corporation | System for automatically and transparently mapping rules and objects from a stable storage database management system within a forward chaining or backward chaining inference cycle |
US5228116A (en) | 1988-07-15 | 1993-07-13 | Aicorp., Inc. | Knowledge base management system |
US4953106A (en) | 1989-05-23 | 1990-08-28 | At&T Bell Laboratories | Technique for drawing directed graphs |
US5119465A (en) | 1989-06-19 | 1992-06-02 | Digital Equipment Corporation | System for selectively converting plurality of source data structures through corresponding source intermediate structures, and target intermediate structures into selected target structure |
US5129043A (en) | 1989-08-14 | 1992-07-07 | International Business Machines Corporation | Performance improvement tool for rule based expert systems |
US5093794A (en) | 1989-08-22 | 1992-03-03 | United Technologies Corporation | Job scheduling system |
CA2284250C (en) | 1989-09-01 | 2001-12-04 | Amdahl Corporation | Computer method for implementing a get instruction |
US5204939A (en) | 1989-12-14 | 1993-04-20 | Fujitsu Limited | Rule base processing system and rule evaluation control method therein |
US5301270A (en) | 1989-12-18 | 1994-04-05 | Anderson Consulting | Computer-assisted software engineering system for cooperative processing environments |
US5140671A (en) | 1990-01-26 | 1992-08-18 | International Business Machines Corporation | Expert system debugger |
JP3245655B2 (en) | 1990-03-05 | 2002-01-15 | インキサイト ソフトウェア インコーポレイテッド | Workspace display processing method |
US6185516B1 (en) | 1990-03-06 | 2001-02-06 | Lucent Technologies Inc. | Automata-theoretic verification of systems |
US5262941A (en) | 1990-03-30 | 1993-11-16 | Itt Corporation | Expert credit recommendation method and system |
US5761493A (en) | 1990-04-30 | 1998-06-02 | Texas Instruments Incorporated | Apparatus and method for adding an associative query capability to a programming language |
US5297279A (en) | 1990-05-30 | 1994-03-22 | Texas Instruments Incorporated | System and method for database management supporting object-oriented programming |
US5291394A (en) | 1990-06-01 | 1994-03-01 | Motorola, Inc. | Manufacturing control and capacity planning system |
US5311422A (en) | 1990-06-28 | 1994-05-10 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | General purpose architecture for intelligent computer-aided training |
SE9002558D0 (en) | 1990-08-02 | 1990-08-02 | Carlstedt Elektronik Ab | PROCESSOR |
US5077491A (en) | 1990-11-30 | 1991-12-31 | Motorola, Inc. | Low standby current comparator having a zero temperature coefficient with hysterisis |
US5291583A (en) | 1990-12-14 | 1994-03-01 | Racal-Datacom, Inc. | Automatic storage of persistent ASN.1 objects in a relational schema |
US5295256A (en) | 1990-12-14 | 1994-03-15 | Racal-Datacom, Inc. | Automatic storage of persistent objects in a relational schema |
US5199068A (en) | 1991-01-22 | 1993-03-30 | Professional Achievement Systems, Inc. | Computer-based training system with student verification |
US5193056A (en) | 1991-03-11 | 1993-03-09 | Signature Financial Group Inc. | Data processing system for hub and spoke financial services configuration |
US5481647A (en) | 1991-03-22 | 1996-01-02 | Raff Enterprises, Inc. | User adaptable expert system |
US5276885A (en) | 1991-04-18 | 1994-01-04 | Carnegie Group | Single step mapping in topological order of the queued class and instance frames of a semantic network to a static working memory |
US5270920A (en) | 1991-05-13 | 1993-12-14 | Hughes Training, Inc. | Expert system scheduler and scheduling method |
US5136184A (en) | 1991-05-24 | 1992-08-04 | Analog Devices, Incorporated | Fast-acting current comparator |
US5326270A (en) | 1991-08-29 | 1994-07-05 | Introspect Technologies, Inc. | System and method for assessing an individual's task-processing style |
US5395243A (en) | 1991-09-25 | 1995-03-07 | National Education Training Group | Interactive learning system |
US5333254A (en) | 1991-10-02 | 1994-07-26 | Xerox Corporation | Methods of centering nodes in a hierarchical display |
US5421730A (en) | 1991-11-27 | 1995-06-06 | National Education Training Group, Inc. | Interactive learning system providing user feedback |
US5381332A (en) | 1991-12-09 | 1995-01-10 | Motorola, Inc. | Project management system with automated schedule and cost integration |
US5259766A (en) | 1991-12-13 | 1993-11-09 | Educational Testing Service | Method and system for interactive computer science testing, anaylsis and feedback |
US5421011A (en) | 1991-12-20 | 1995-05-30 | International Business Machines Corporation | Method and system for access and accounting control in a data processing system by using a single resource account for a user or a group of users |
US5267865A (en) | 1992-02-11 | 1993-12-07 | John R. Lee | Interactive computer aided natural learning method and apparatus |
JP2882163B2 (en) | 1992-02-26 | 1999-04-12 | 日本電気株式会社 | Comparator |
US5310349A (en) | 1992-04-30 | 1994-05-10 | Jostens Learning Corporation | Instructional management system |
US5446885A (en) | 1992-05-15 | 1995-08-29 | International Business Machines Corporation | Event driven management information system with rule-based applications structure stored in a relational database |
US5689663A (en) | 1992-06-19 | 1997-11-18 | Microsoft Corporation | Remote controller user interface and methods relating thereto |
US5542024A (en) | 1992-07-09 | 1996-07-30 | Johnson & Johnson | Graphically used expert system tool background of the invention |
US5504879A (en) | 1992-07-16 | 1996-04-02 | International Business Machines Corporation | Resolution of relationship source and target in a versioned database management system |
US5386559A (en) | 1992-07-16 | 1995-01-31 | International Business Machines Corporation | Variant domains and variant maps in a versioned database management system |
US5890166A (en) | 1992-07-16 | 1999-03-30 | International Business Machines Corporation | Versioned-database management system in which tasks are associated with promote groups which comprise a set of parts whose changes are to be promoted |
US5450480A (en) | 1992-08-25 | 1995-09-12 | Bell Communications Research, Inc. | Method of creating a telecommunication service specification |
US5463682A (en) | 1992-08-25 | 1995-10-31 | Bell Communications Research, Inc. | Method of creating user-defined call processing procedures |
US5412756A (en) | 1992-12-22 | 1995-05-02 | Mitsubishi Denki Kabushiki Kaisha | Artificial intelligence software shell for plant operation simulation |
US5579223A (en) | 1992-12-24 | 1996-11-26 | Microsoft Corporation | Method and system for incorporating modifications made to a computer program into a translated version of the computer program |
US5579486A (en) | 1993-01-14 | 1996-11-26 | Apple Computer, Inc. | Communication node with a first bus configuration for arbitration and a second bus configuration for data transfer |
US5649192A (en) | 1993-01-15 | 1997-07-15 | General Electric Company | Self-organized information storage system |
US5379366A (en) | 1993-01-29 | 1995-01-03 | Noyes; Dallas B. | Method for representation of knowledge in a computer as a network database system |
US5276359A (en) | 1993-02-02 | 1994-01-04 | Chiang Ting Chi | Current-input type interface circuit of a mouse |
WO1994020918A1 (en) | 1993-03-11 | 1994-09-15 | Fibercraft/Descon Engineering, Inc. | Design and engineering project management system |
TW239190B (en) | 1993-04-30 | 1995-01-21 | Philips Electronics Nv | |
DE69417622T2 (en) | 1993-04-30 | 1999-09-09 | Stmicroelectronics | Voltage comparator with a summation of direct currents based on the bandgap principle and supply voltage switch containing them |
US5911138A (en) | 1993-06-04 | 1999-06-08 | International Business Machines Corporation | Database search facility having improved user interface |
US5809212A (en) | 1993-07-12 | 1998-09-15 | New York University | Conditional transition networks and computational processes for use interactive computer-based systems |
US6684261B1 (en) | 1993-07-19 | 2004-01-27 | Object Technology Licensing Corporation | Object-oriented operating system |
US5374932A (en) | 1993-08-02 | 1994-12-20 | Massachusetts Institute Of Technology | Airport surface surveillance system |
US5519618A (en) | 1993-08-02 | 1996-05-21 | Massachusetts Institute Of Technology | Airport surface safety logic |
US5537590A (en) | 1993-08-05 | 1996-07-16 | Amado; Armando | Apparatus for applying analysis rules to data sets in a relational database to generate a database of diagnostic records linked to the data sets |
US5632009A (en) | 1993-09-17 | 1997-05-20 | Xerox Corporation | Method and system for producing a table image showing indirect data representations |
US5522025A (en) | 1993-10-25 | 1996-05-28 | Taligent, Inc. | Object-oriented window area display system |
US5473732A (en) | 1993-11-02 | 1995-12-05 | Chang; Hou-Mei H. | Relational artificial intelligence system |
EP0668558B1 (en) | 1994-01-14 | 2002-04-17 | Sun Microsystems, Inc. | Method and apparatus for automating the localization of a computer program |
US5586311A (en) | 1994-02-14 | 1996-12-17 | American Airlines, Inc. | Object oriented data access and analysis system |
US5477170A (en) | 1994-02-17 | 1995-12-19 | Nec Corporation | Comparator capable of preventing large noise voltage |
US5548506A (en) | 1994-03-17 | 1996-08-20 | Srinivasan; Seshan R. | Automated, electronic network based, project management server system, for managing multiple work-groups |
US5655118A (en) | 1994-03-21 | 1997-08-05 | Bell Communications Research, Inc. | Methods and apparatus for managing information on activities of an enterprise |
US5597312A (en) | 1994-05-04 | 1997-01-28 | U S West Technologies, Inc. | Intelligent tutoring method and system |
US6513018B1 (en) | 1994-05-05 | 2003-01-28 | Fair, Isaac And Company, Inc. | Method and apparatus for scoring the likelihood of a desired performance result |
US5862321A (en) | 1994-06-27 | 1999-01-19 | Xerox Corporation | System and method for accessing and distributing electronic documents |
US6341293B1 (en) | 1994-07-13 | 2002-01-22 | Object Technology Licensing Corp | Real-time computer “garbage collector” |
US5627979A (en) | 1994-07-18 | 1997-05-06 | International Business Machines Corporation | System and method for providing a graphical user interface for mapping and accessing objects in data stores |
JPH0876680A (en) | 1994-09-02 | 1996-03-22 | Fujitsu Ltd | Management education system |
US5611076A (en) | 1994-09-21 | 1997-03-11 | Micro Data Base Systems, Inc. | Multi-model database management system engine for databases having complex data models |
DE4434180A1 (en) | 1994-09-24 | 1996-03-28 | Teves Gmbh Alfred | Circuit arrangement for evaluating the output signal of an active sensor |
US5542078A (en) | 1994-09-29 | 1996-07-30 | Ontos, Inc. | Object oriented data store integration environment for integration of object oriented databases and non-object oriented data facilities |
US5678039A (en) | 1994-09-30 | 1997-10-14 | Borland International, Inc. | System and methods for translating software into localized versions |
US5768480A (en) | 1994-10-21 | 1998-06-16 | Lucent Technologies Inc. | Integrating rules into object-oriented programming systems |
JP2840923B2 (en) | 1994-11-11 | 1998-12-24 | 富士通株式会社 | Production system |
US5732192A (en) | 1994-11-30 | 1998-03-24 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Global qualitative flow-path modeling for local state determination in simulation and analysis |
US5561740A (en) | 1994-12-13 | 1996-10-01 | International Business Machines Corporation | Method and system for providing multiple instances in a single multiple-instance object |
US5499293A (en) | 1995-01-24 | 1996-03-12 | University Of Maryland | Privacy protected information medium using a data compression method |
JP2765506B2 (en) | 1995-01-30 | 1998-06-18 | 日本電気株式会社 | Logic circuit delay information retention method |
US5918222A (en) | 1995-03-17 | 1999-06-29 | Kabushiki Kaisha Toshiba | Information disclosing apparatus and multi-modal information input/output system |
US5675753A (en) | 1995-04-24 | 1997-10-07 | U.S. West Technologies, Inc. | Method and system for presenting an electronic user-interface specification |
US5701451A (en) | 1995-06-07 | 1997-12-23 | International Business Machines Corporation | Method for fulfilling requests of a web browser |
US5907837A (en) | 1995-07-17 | 1999-05-25 | Microsoft Corporation | Information retrieval system in an on-line network including separate content and layout of published titles |
US5781449A (en) | 1995-08-10 | 1998-07-14 | Advanced System Technologies, Inc. | Response time measurement apparatus and method |
US5715450A (en) | 1995-09-27 | 1998-02-03 | Siebel Systems, Inc. | Method of selecting and presenting data from a database using a query language to a user of a computer system |
US5788504A (en) | 1995-10-16 | 1998-08-04 | Brookhaven Science Associates Llc | Computerized training management system |
US5875334A (en) | 1995-10-27 | 1999-02-23 | International Business Machines Corporation | System, method, and program for extending a SQL compiler for handling control statements packaged with SQL query statements |
US6546406B1 (en) | 1995-11-03 | 2003-04-08 | Enigma Information Systems Ltd. | Client-server computer system for large document retrieval on networked computer system |
US5765140A (en) | 1995-11-17 | 1998-06-09 | Mci Corporation | Dynamic project management system |
US5832483A (en) | 1995-12-15 | 1998-11-03 | Novell, Inc. | Distributed control interface for managing the interoperability and concurrency of agents and resources in a real-time environment |
US5920717A (en) | 1995-12-20 | 1999-07-06 | Nec Corporation | Method and apparatus for automated program-generation |
US5815415A (en) | 1996-01-19 | 1998-09-29 | Bentley Systems, Incorporated | Computer system for portable persistent modeling |
US5831607A (en) | 1996-01-25 | 1998-11-03 | International Business Machines Corporation | Method for adapting multiple screens of information for access and use on a single graphical panel in a computer system |
US5761673A (en) | 1996-01-31 | 1998-06-02 | Oracle Corporation | Method and apparatus for generating dynamic web pages by invoking a predefined procedural package stored in a database |
DE19605569A1 (en) | 1996-02-15 | 1997-08-21 | Daimler Benz Aerospace Ag | Directional coupler for the high frequency range |
US5873096A (en) | 1997-10-08 | 1999-02-16 | Siebel Systems, Inc. | Method of maintaining a network of partially replicated database system |
US5795155A (en) | 1996-04-01 | 1998-08-18 | Electronic Data Systems Corporation | Leadership assessment tool and method |
US6366930B1 (en) | 1996-04-12 | 2002-04-02 | Computer Associates Think, Inc. | Intelligent data inventory & asset management systems method and apparatus |
GB9609189D0 (en) | 1996-05-02 | 1996-07-03 | Philips Electronics Nv | Adaptive process modelling and control |
JPH09297768A (en) | 1996-05-07 | 1997-11-18 | Fuji Xerox Co Ltd | Management device and retrieval method for document data base |
US5826250A (en) | 1996-06-19 | 1998-10-20 | Pegasystems Inc. | Rules bases and methods of access thereof |
KR100218306B1 (en) | 1996-06-27 | 1999-09-01 | 구본준 | Voltage-current converter |
US5826252A (en) | 1996-06-28 | 1998-10-20 | General Electric Company | System for managing multiple projects of similar type using dynamically updated global database |
US6457004B1 (en) | 1997-07-03 | 2002-09-24 | Hitachi, Ltd. | Document retrieval assisting method, system and service using closely displayed areas for titles and topics |
GB2315139A (en) | 1996-07-06 | 1998-01-21 | Ibm | Selecting operations in an object-oriented user interface |
US5978566A (en) | 1996-07-12 | 1999-11-02 | Microsoft Corporation | Client side deferred actions within multiple MAPI profiles |
FR2751488B1 (en) | 1996-07-16 | 1998-10-16 | Sgs Thomson Microelectronics | POWER AMPLIFIER IN BICMOS TECHNOLOGY WITH OUTPUT STAGE IN MOS TECHNOLOGY |
US5841435A (en) | 1996-07-26 | 1998-11-24 | International Business Machines Corporation | Virtual windows desktop |
US6047264A (en) | 1996-08-08 | 2000-04-04 | Onsale, Inc. | Method for supplying automatic status updates using electronic mail |
DE19638087C2 (en) | 1996-09-18 | 1999-09-02 | Siemens Ag | CMOS comparator |
US6526457B1 (en) | 1996-10-30 | 2003-02-25 | Computer Associates Think, Inc. | Systems utility object interface for facilitating software portability |
US6023717A (en) | 1996-10-30 | 2000-02-08 | Qualcomm Incorporated | Method and apparatus for polyphase digital filtering in a mobile telephone |
US7165020B2 (en) | 1998-05-29 | 2007-01-16 | Citicorp Development Center, Inc. | Multi-language phrase editor and method thereof |
US6137797A (en) | 1996-11-27 | 2000-10-24 | International Business Machines Corporation | Process definition for source route switching |
US5826239A (en) | 1996-12-17 | 1998-10-20 | Hewlett-Packard Company | Distributed workflow resource management system and method |
US5822780A (en) | 1996-12-31 | 1998-10-13 | Emc Corporation | Method and apparatus for hierarchical storage management for data base management systems |
US5930795A (en) | 1997-01-21 | 1999-07-27 | International Business Machines Corporation | Supporting dynamic tables in SQL query compilers |
US5819257A (en) | 1997-01-31 | 1998-10-06 | Lucent Technologies Inc. | Process for providing transitive closure using fourth generation structure query language (SQL) |
US5818463A (en) | 1997-02-13 | 1998-10-06 | Rockwell Science Center, Inc. | Data compression for animated three dimensional objects |
AU6336698A (en) | 1997-02-26 | 1998-09-29 | Siebel Systems, Inc. | Distributed relational database |
WO1998038587A1 (en) | 1997-02-26 | 1998-09-03 | Siebel Systems, Inc. | Method of using a cache to determine the visibility to a remote database client of a plurality of database transactions |
WO1998038583A1 (en) | 1997-02-26 | 1998-09-03 | Siebel Systems, Inc. | Method of determining visibility to a remote database client of a plurality of database transactions having variable visibility strengths |
AU6654798A (en) | 1997-02-26 | 1998-09-18 | Siebel Systems, Inc. | Method of determining visibility to a remote database client of a plurality of database transactions using a networked proxy server |
AU6183798A (en) | 1997-02-27 | 1998-09-29 | Siebel Systems, Inc. | Method of migrating to a successive level of a software distribution incorporating local modifications |
WO1998040805A2 (en) | 1997-02-27 | 1998-09-17 | Siebel Systems, Inc. | Method of synchronizing independently distributed software and database schema |
AU6669198A (en) | 1997-02-28 | 1998-09-18 | Siebel Systems, Inc. | Partially replicated distributed database with multiple levels of remote clients |
US5995958A (en) | 1997-03-04 | 1999-11-30 | Xu; Kevin Houzhi | System and method for storing and managing functions |
US5864865A (en) | 1997-03-24 | 1999-01-26 | Novell, Inc. | Management information base listing viewer |
US6023714A (en) | 1997-04-24 | 2000-02-08 | Microsoft Corporation | Method and system for dynamically adapting the layout of a document to an output device |
US5907490A (en) | 1997-06-10 | 1999-05-25 | Electronic Data Systems Corporation | System and method for project management and assessment |
US20010054064A1 (en) | 1997-07-02 | 2001-12-20 | Pallipuram V. Kannan | Method system and computer program product for providing customer service over the world-wide web |
US6122632A (en) | 1997-07-21 | 2000-09-19 | Convergys Customer Management Group Inc. | Electronic message management system |
US6038601A (en) | 1997-07-21 | 2000-03-14 | Tibco, Inc. | Method and apparatus for storing and delivering documents on the internet |
US6338074B1 (en) | 1997-07-23 | 2002-01-08 | Filenet Corporation | System for enterprise-wide work flow automation |
US6052685A (en) | 1997-08-13 | 2000-04-18 | Mosaix, Inc. | Integration of legacy database management systems with ODBC-compliant application programs |
US5983267A (en) | 1997-09-23 | 1999-11-09 | Information Architects Corporation | System for indexing and displaying requested data having heterogeneous content and representation |
US9197599B1 (en) | 1997-09-26 | 2015-11-24 | Verizon Patent And Licensing Inc. | Integrated business system for web based telecommunications management |
US5974443A (en) | 1997-09-26 | 1999-10-26 | Intervoice Limited Partnership | Combined internet and data access system |
US6044373A (en) | 1997-09-29 | 2000-03-28 | International Business Machines Corporation | Object-oriented access control method and system for military and commercial file systems |
US6037890A (en) | 1997-09-30 | 2000-03-14 | Intel Corporation | Ultra high speed, low power, flash A/D converter utilizing a current mode regenerative comparator |
US6108004A (en) | 1997-10-21 | 2000-08-22 | International Business Machines Corporation | GUI guide for data mining |
JPH11143724A (en) | 1997-11-13 | 1999-05-28 | Sharp Corp | Information processor and computer readable recording medium for recording information processing program |
US5995948A (en) | 1997-11-21 | 1999-11-30 | First Usa Bank, N.A. | Correspondence and chargeback workstation |
US6167441A (en) | 1997-11-21 | 2000-12-26 | International Business Machines Corporation | Customization of web pages based on requester type |
US6044466A (en) | 1997-11-25 | 2000-03-28 | International Business Machines Corp. | Flexible and dynamic derivation of permissions |
JPH11163644A (en) | 1997-11-26 | 1999-06-18 | Fujitsu Ltd | Output circuit using differential amplifier circuit |
US6769019B2 (en) | 1997-12-10 | 2004-07-27 | Xavier Ferguson | Method of background downloading of information from a computer network |
KR100293446B1 (en) | 1997-12-30 | 2001-07-12 | 김영환 | Main amplifier |
US6008808A (en) | 1997-12-31 | 1999-12-28 | Nortel Network Corporation | Tools for data manipulation and visualization |
US6807632B1 (en) | 1999-01-21 | 2004-10-19 | Emc Corporation | Content addressable information encapsulation, representation, and transfer |
US6023704A (en) | 1998-01-29 | 2000-02-08 | International Business Machines Corporation | Apparatus and method for swapping identities of two objects to reference the object information of the other |
US6636901B2 (en) | 1998-01-30 | 2003-10-21 | Object Technology Licensing Corp. | Object-oriented resource lock and entry register |
US6151624A (en) | 1998-02-03 | 2000-11-21 | Realnames Corporation | Navigating network resources based on metadata |
US6304259B1 (en) | 1998-02-09 | 2001-10-16 | International Business Machines Corporation | Computer system, method and user interface components for abstracting and accessing a body of knowledge |
US6105035A (en) | 1998-02-17 | 2000-08-15 | Lucent Technologies, Inc. | Method by which notions and constructs of an object oriented programming language can be implemented using a structured query language (SQL) |
US6012098A (en) | 1998-02-23 | 2000-01-04 | International Business Machines Corp. | Servlet pairing for isolation of the retrieval and rendering of data |
US6732111B2 (en) | 1998-03-03 | 2004-05-04 | Siebel Systems, Inc. | Method, apparatus, system, and program product for attaching files and other objects to a partially replicated database |
EP1073955B1 (en) | 1998-03-03 | 2008-04-16 | Siebel Systems, Inc. | Method, system, apparatus and program product for distribution and instantiation of software upgrades |
US6493399B1 (en) | 1998-03-05 | 2002-12-10 | University Of Delaware | Digital wireless communications systems that eliminates intersymbol interference (ISI) and multipath cancellation using a plurality of optimal ambiguity resistant precoders |
JP2947256B1 (en) | 1998-03-12 | 1999-09-13 | 日本電気株式会社 | Voltage determination circuit and battery pack including the same |
US6560592B1 (en) * | 1998-03-19 | 2003-05-06 | Micro Data Base Systems, Inc. | Multi-model computer database storage system with integrated rule engine |
US6185534B1 (en) | 1998-03-23 | 2001-02-06 | Microsoft Corporation | Modeling emotion and personality in a computer user interface |
US6078982A (en) | 1998-03-24 | 2000-06-20 | Hewlett-Packard Company | Pre-locking scheme for allowing consistent and concurrent workflow process execution in a workflow management system |
US6154738A (en) | 1998-03-27 | 2000-11-28 | Call; Charles Gainor | Methods and apparatus for disseminating product information via the internet using universal product codes |
US6125363A (en) | 1998-03-30 | 2000-09-26 | Buzzeo; Eugene | Distributed, multi-user, multi-threaded application development method |
US6085188A (en) | 1998-03-30 | 2000-07-04 | International Business Machines Corporation | Method of hierarchical LDAP searching with relational tables |
US5963953A (en) | 1998-03-30 | 1999-10-05 | Siebel Systems, Inc. | Method, and system for product configuration |
US5945852A (en) | 1998-03-31 | 1999-08-31 | Motorola, Inc. | CMOS comparator output circuit with high gain and hysteresis |
US6281896B1 (en) | 1998-03-31 | 2001-08-28 | International Business Machines Corporation | Data processor controlled interface with multiple tree of elements views expandable into individual detail views |
US6369819B1 (en) | 1998-04-17 | 2002-04-09 | Xerox Corporation | Methods for visualizing transformations among related series of graphs |
US6151595A (en) | 1998-04-17 | 2000-11-21 | Xerox Corporation | Methods for interactive visualization of spreading activation using time tubes and disk trees |
US6509898B2 (en) | 1998-04-17 | 2003-01-21 | Xerox Corporation | Usage based methods of traversing and displaying generalized graph structures |
US6389460B1 (en) | 1998-05-13 | 2002-05-14 | Compaq Computer Corporation | Method and apparatus for efficient storage and retrieval of objects in and from an object storage device |
US6020768A (en) | 1998-05-13 | 2000-02-01 | Oak Technology, Inc. | CMOS low-voltage comparator |
US7031901B2 (en) | 1998-05-13 | 2006-04-18 | Abu El Ata Nabil A | System and method for improving predictive modeling of an information system |
US6772350B1 (en) | 1998-05-15 | 2004-08-03 | E.Piphany, Inc. | System and method for controlling access to resources in a distributed environment |
US6344862B1 (en) | 1998-05-29 | 2002-02-05 | Hewlett-Packard Company | User interface mechanism for manipulating context in computer management applications |
US6092036A (en) | 1998-06-02 | 2000-07-18 | Davox Corporation | Multi-lingual data processing system and system and method for translating text used in computer software utilizing an embedded translator |
US6233332B1 (en) | 1998-06-03 | 2001-05-15 | Avaya Technology Corp. | System for context based media independent communications processing |
US6085198A (en) | 1998-06-05 | 2000-07-04 | Sun Microsystems, Inc. | Integrated three-tier application framework with automated class and table generation |
US6094652A (en) | 1998-06-10 | 2000-07-25 | Oracle Corporation | Hierarchical query feedback in an information retrieval system |
US6594662B1 (en) | 1998-07-01 | 2003-07-15 | Netshadow, Inc. | Method and system for gathering information resident on global computer networks |
US6300947B1 (en) | 1998-07-06 | 2001-10-09 | International Business Machines Corporation | Display screen and window size related web page adaptation system |
US6583800B1 (en) | 1998-07-14 | 2003-06-24 | Brad Ridgley | Method and device for finding, collecting and acting upon units of information |
US6430571B1 (en) | 1998-07-16 | 2002-08-06 | International Business Machines Corporation | Multi-frame output form that facilitates internet search and update in a hierarchical database |
US6177932B1 (en) | 1998-08-21 | 2001-01-23 | Kana Communications, Inc. | Method and apparatus for network based customer service |
US6243713B1 (en) | 1998-08-24 | 2001-06-05 | Excalibur Technologies Corp. | Multimedia document retrieval by application of multimedia queries to a unified index of multimedia data for a plurality of multimedia data types |
US6282547B1 (en) | 1998-08-25 | 2001-08-28 | Informix Software, Inc. | Hyperlinked relational database visualization system |
US6473748B1 (en) | 1998-08-31 | 2002-10-29 | Worldcom, Inc. | System for implementing rules |
US6225237B1 (en) | 1998-09-01 | 2001-05-01 | Micron Technology, Inc. | Method for forming metal-containing films using metal complexes with chelating O- and/or N-donor ligands |
US6351734B1 (en) | 1998-09-09 | 2002-02-26 | Unisys Corporation | System and method for resource allocation and planning |
US6349238B1 (en) | 1998-09-16 | 2002-02-19 | Mci Worldcom, Inc. | System and method for managing the workflow for processing service orders among a variety of organizations within a telecommunications company |
US6377973B2 (en) | 1998-09-30 | 2002-04-23 | Emrys Technologies, Ltd. | Event management in a system with application and graphical user interface processing adapted to display predefined graphical elements resides separately on server and client machine |
US6415283B1 (en) | 1998-10-13 | 2002-07-02 | Orack Corporation | Methods and apparatus for determining focal points of clusters in a tree structure |
US6691230B1 (en) | 1998-10-15 | 2004-02-10 | International Business Machines Corporation | Method and system for extending Java applets sand box with public client storage |
US8006177B1 (en) | 1998-10-16 | 2011-08-23 | Open Invention Network, Llc | Documents for commerce in trading partner networks and interface definitions based on the documents |
JP2000138573A (en) | 1998-10-30 | 2000-05-16 | Fujitsu Ltd | Differential input circuit |
US6546381B1 (en) | 1998-11-02 | 2003-04-08 | International Business Machines Corporation | Query optimization system and method |
US6314415B1 (en) | 1998-11-04 | 2001-11-06 | Cch Incorporated | Automated forms publishing system and method using a rule-based expert system to dynamically generate a graphical user interface |
US7505827B1 (en) | 1998-11-06 | 2009-03-17 | Honeywell International Inc. | Automated finite capacity scheduler |
US6502239B2 (en) | 1998-11-12 | 2002-12-31 | Computer Associates Think, Inc | Method and apparatus for round-trip software engineering |
US6341277B1 (en) | 1998-11-17 | 2002-01-22 | International Business Machines Corporation | System and method for performance complex heterogeneous database queries using a single SQL expression |
US6393605B1 (en) | 1998-11-18 | 2002-05-21 | Siebel Systems, Inc. | Apparatus and system for efficient delivery and deployment of an application |
WO2000030232A1 (en) | 1998-11-19 | 2000-05-25 | X/Net Associates, Inc. | Method and system for external notification and/or resolution of software errors |
US6313834B1 (en) | 1998-11-23 | 2001-11-06 | Ibm | Multi-format and multi-view synchronized data editor |
AU2035600A (en) | 1998-11-30 | 2000-06-19 | Siebel Systems, Inc. | Development tool, method, and system for client server appications |
EP1208482A4 (en) | 1998-11-30 | 2002-05-29 | Siebel Systems Inc | Client server system with thin client architecture |
JP2002531899A (en) | 1998-11-30 | 2002-09-24 | シーベル システムズ,インコーポレイティド | State model for process monitoring |
EP1196882A1 (en) | 1998-11-30 | 2002-04-17 | Siebel Systems, Inc. | Smart scripting call centers |
EP1163604A4 (en) | 1998-11-30 | 2002-01-09 | Siebel Systems Inc | Assignment manager |
US6396885B1 (en) | 1998-12-02 | 2002-05-28 | Nortel Networks Limited | Co-channel interference reduction in wireless communications systems |
US6356286B1 (en) | 1998-12-10 | 2002-03-12 | International Business Machines Corporation | User-interactive computer display interface with a tree having a plurality of user selectable nodes representing a plurality of search queries to a tabular database |
US7526468B2 (en) | 1999-01-08 | 2009-04-28 | Computer Associates Think, Inc. | System and method for recursive path analysis of DBMS procedures |
WO2000042563A2 (en) | 1999-01-13 | 2000-07-20 | Computer Associates Think, Inc. | Signature recognition system and method |
US6529900B1 (en) | 1999-01-14 | 2003-03-04 | International Business Machines Corporation | Method and apparatus for data visualization |
US6370537B1 (en) | 1999-01-14 | 2002-04-09 | Altoweb, Inc. | System and method for the manipulation and display of structured data |
US6359633B1 (en) | 1999-01-15 | 2002-03-19 | Yahoo! Inc. | Apparatus and method for abstracting markup language documents |
US6941321B2 (en) | 1999-01-26 | 2005-09-06 | Xerox Corporation | System and method for identifying similarities among objects in a collection |
US6493731B1 (en) | 1999-01-27 | 2002-12-10 | Xerox Corporation | Document management system for recording and viewing the history of document use |
US6560649B1 (en) | 1999-02-10 | 2003-05-06 | Avaya Technology Corp. | Hierarchical service level remediation for competing classes based upon achievement of service level goals |
JP2000235493A (en) | 1999-02-12 | 2000-08-29 | Fujitsu Ltd | Trading device |
US6246320B1 (en) | 1999-02-25 | 2001-06-12 | David A. Monroe | Ground link with on-board security surveillance system for aircraft and other commercial vehicles |
US20020072951A1 (en) | 1999-03-03 | 2002-06-13 | Michael Lee | Marketing support database management method, system and program product |
US6574635B2 (en) | 1999-03-03 | 2003-06-03 | Siebel Systems, Inc. | Application instantiation based upon attributes and values stored in a meta data repository, including tiering of application layers objects and components |
JP3484096B2 (en) | 1999-03-03 | 2004-01-06 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Logical zoom method in logical zoom device for directed graph |
US6448964B1 (en) | 1999-03-15 | 2002-09-10 | Computer Associates Think, Inc. | Graphic object manipulating tool |
US6308163B1 (en) | 1999-03-16 | 2001-10-23 | Hewlett-Packard Company | System and method for enterprise workflow resource management |
US6584464B1 (en) | 1999-03-19 | 2003-06-24 | Ask Jeeves, Inc. | Grammar template query system |
US6469715B1 (en) | 1999-03-19 | 2002-10-22 | Corel Inc. | System and method for controlling the operation of a graphical object using a project |
US6469716B1 (en) | 1999-03-19 | 2002-10-22 | Corel Inc. | System and method for processing data for a graphical object |
US6405251B1 (en) | 1999-03-25 | 2002-06-11 | Nortel Networks Limited | Enhancement of network accounting records |
US6625657B1 (en) | 1999-03-25 | 2003-09-23 | Nortel Networks Limited | System for requesting missing network accounting records if there is a break in sequence numbers while the records are transmitting from a source device |
US6446200B1 (en) | 1999-03-25 | 2002-09-03 | Nortel Networks Limited | Service management |
US6751663B1 (en) | 1999-03-25 | 2004-06-15 | Nortel Networks Limited | System wide flow aggregation process for aggregating network activity records |
US6691067B1 (en) | 1999-04-07 | 2004-02-10 | Bmc Software, Inc. | Enterprise management system and method which includes statistical recreation of system resource usage for more accurate monitoring, prediction, and performance workload characterization |
US6463440B1 (en) | 1999-04-08 | 2002-10-08 | International Business Machines Corporation | Retrieval of style sheets from directories based upon partial characteristic matching |
US7526481B1 (en) | 1999-04-19 | 2009-04-28 | Oracle International Corporation | Web servers with queryable dynamic caches |
US6192371B1 (en) | 1999-04-28 | 2001-02-20 | Lucent Technologies, Inc | Object morphing in an object oriented computing environment using relational database query procedure |
US6564197B2 (en) | 1999-05-03 | 2003-05-13 | E.Piphany, Inc. | Method and apparatus for scalable probabilistic clustering using decision trees |
US6430539B1 (en) | 1999-05-06 | 2002-08-06 | Hnc Software | Predictive modeling of consumer financial behavior |
US6530079B1 (en) | 1999-06-02 | 2003-03-04 | International Business Machines Corporation | Method for optimizing locks in computer programs |
US6606613B1 (en) | 1999-06-03 | 2003-08-12 | Microsoft Corporation | Methods and apparatus for using task models to help computer users complete tasks |
US6539374B2 (en) | 1999-06-03 | 2003-03-25 | Microsoft Corporation | Methods, apparatus and data structures for providing a uniform representation of various types of information |
US6330554B1 (en) | 1999-06-03 | 2001-12-11 | Microsoft Corporation | Methods and apparatus using task models for targeting marketing information to computer users based on a task being performed |
US6778971B1 (en) | 1999-06-03 | 2004-08-17 | Microsoft Corporation | Methods and apparatus for analyzing computer-based tasks to build task models |
US6326988B1 (en) | 1999-06-08 | 2001-12-04 | Monkey Media, Inc. | Method, apparatus and article of manufacture for displaying content in a multi-dimensional topic space |
US6529217B1 (en) | 1999-06-15 | 2003-03-04 | Microsoft Corporation | System and method for graphically displaying a set of data fields |
US7844594B1 (en) | 1999-06-18 | 2010-11-30 | Surfwax, Inc. | Information search, retrieval and distillation into knowledge objects |
US6549904B1 (en) | 1999-06-25 | 2003-04-15 | Amazon.Com, Inc. | Auction notification system |
US6446256B1 (en) | 1999-06-30 | 2002-09-03 | Microsoft Corporation | Extension of parsable structures |
US6678882B1 (en) | 1999-06-30 | 2004-01-13 | Qwest Communications International Inc. | Collaborative model for software systems with synchronization submodel with merge feature, automatic conflict resolution and isolation of potential changes for reuse |
US20020120627A1 (en) | 1999-07-07 | 2002-08-29 | Mankoff Jeffrey W. | Virtual document organizer system and method |
US6405211B1 (en) | 1999-07-08 | 2002-06-11 | Cohesia Corporation | Object-oriented representation of technical content and management, filtering, and synthesis of technical content using object-oriented representations |
US6415259B1 (en) | 1999-07-15 | 2002-07-02 | American Management Systems, Inc. | Automatic work progress tracking and optimizing engine for a telecommunications customer care and billing system |
US6381738B1 (en) | 1999-07-16 | 2002-04-30 | International Business Machines Corporation | Method for optimizing creation and destruction of objects in computer programs |
US6380947B1 (en) | 1999-07-22 | 2002-04-30 | At&T Corp. | Method and apparatus for displaying and tree scrolling a hierarchical data structure |
US6430574B1 (en) | 1999-07-22 | 2002-08-06 | At&T Corp. | Method and apparatus for displaying and header scrolling a hierarchical data structure |
US6556985B1 (en) | 1999-07-23 | 2003-04-29 | Teleran Technologies, Inc. | Rule construction and application |
US6597381B1 (en) | 1999-07-24 | 2003-07-22 | Intelligent Reasoning Systems, Inc. | User interface for automated optical inspection systems |
US6275790B1 (en) | 1999-07-28 | 2001-08-14 | International Business Machines Corporation | Introspective editor system, program, and method for software translation |
US20020054152A1 (en) | 1999-08-23 | 2002-05-09 | Murugan Palaniappan | Menu infrastructure apparatus and method |
US7139999B2 (en) | 1999-08-31 | 2006-11-21 | Accenture Llp | Development architecture framework |
US6577769B1 (en) | 1999-09-18 | 2003-06-10 | Wildtangent, Inc. | Data compression through adaptive data size reduction |
US6598043B1 (en) | 1999-10-04 | 2003-07-22 | Jarg Corporation | Classification of information sources using graph structures |
US6463346B1 (en) | 1999-10-08 | 2002-10-08 | Avaya Technology Corp. | Workflow-scheduling optimization driven by target completion time |
US7574494B1 (en) | 1999-10-15 | 2009-08-11 | Thomson Licensing | User interface for a bi-directional communication system |
US20030050927A1 (en) | 2001-09-07 | 2003-03-13 | Araha, Inc. | System and method for location, understanding and assimilation of digital documents through abstract indicia |
US7035808B1 (en) | 1999-10-20 | 2006-04-25 | Avaya Technology Corp. | Arrangement for resource and work-item selection |
US6851089B1 (en) | 1999-10-25 | 2005-02-01 | Amazon.Com, Inc. | Software application and associated methods for generating a software layer for structuring semistructured information |
US6496833B1 (en) | 1999-11-01 | 2002-12-17 | Sun Microsystems, Inc. | System and method for generating code for query object interfacing |
AU3438401A (en) | 1999-11-04 | 2001-05-14 | Jp Morgan Chase Bank | System and method for automated financial project management |
US20020177232A1 (en) | 2001-05-23 | 2002-11-28 | Melker Richard J. | Method and apparatus for detecting illicit substances |
US6714952B2 (en) | 1999-11-10 | 2004-03-30 | Emc Corporation | Method for backup and restore of a multi-lingual network file server |
US6324568B1 (en) | 1999-11-30 | 2001-11-27 | Siebel Systems, Inc. | Method and system for distributing objects over a network |
US6418448B1 (en) | 1999-12-06 | 2002-07-09 | Shyam Sundar Sarkar | Method and apparatus for processing markup language specifications for data and metadata used inside multiple related internet documents to navigate, query and manipulate information from a plurality of object relational databases over the web |
US6614903B1 (en) | 1999-12-15 | 2003-09-02 | Avaya Technology Corp. | Methods and apparatus for service state-based processing of communications in a call center |
US7064241B2 (en) | 2000-01-05 | 2006-06-20 | The United States Of America As Represented By The Secretary Of The Navy | Chemical and biological warfare decontaminating solution using peracids and germinants in microemulsions, process and product thereof |
US6556983B1 (en) | 2000-01-12 | 2003-04-29 | Microsoft Corporation | Methods and apparatus for finding semantic information, such as usage logs, similar to a query using a pattern lattice data space |
US6529899B1 (en) | 2000-01-12 | 2003-03-04 | International Business Machines Corporation | System and method for registering and providing a tool service |
US6678773B2 (en) | 2000-01-13 | 2004-01-13 | Motorola, Inc. | Bus protocol independent method and structure for managing transaction priority, ordering and deadlocks in a multi-processing system |
US6643652B2 (en) | 2000-01-14 | 2003-11-04 | Saba Software, Inc. | Method and apparatus for managing data exchange among systems in a network |
AU2001226401A1 (en) | 2000-01-14 | 2001-07-24 | Saba Software, Inc. | Method and apparatus for a business applications server |
US6721747B2 (en) | 2000-01-14 | 2004-04-13 | Saba Software, Inc. | Method and apparatus for an information server |
AU2001229464A1 (en) | 2000-01-14 | 2001-07-24 | Saba Software, Inc. | Method and apparatus for a web content platform |
US6661889B1 (en) | 2000-01-18 | 2003-12-09 | Avaya Technology Corp. | Methods and apparatus for multi-variable work assignment in a call center |
EP1166133B1 (en) | 2000-01-19 | 2005-12-14 | Koninklijke Philips Electronics N.V. | Circuit for voltage level detection |
US6701314B1 (en) | 2000-01-21 | 2004-03-02 | Science Applications International Corporation | System and method for cataloguing digital information for searching and retrieval |
US6925609B1 (en) | 2000-01-31 | 2005-08-02 | International Business Machines Corporation | Hybrid task and file oriented user interface |
AU2001233141A1 (en) | 2000-02-04 | 2001-08-14 | America Online Incorporated | Methods and systems of automated client-server data validation |
US6867789B1 (en) | 2000-02-15 | 2005-03-15 | Bank One, Delaware, National Association | System and method for generating graphical user interfaces |
US6366299B1 (en) | 2000-02-21 | 2002-04-02 | Verizon Laboratories Inc. | Multidimensional information visualization using attribute rods |
CA2400442A1 (en) | 2000-02-25 | 2001-08-30 | Yet Mui | Method for enterprise workforce planning |
US6586972B2 (en) | 2000-02-28 | 2003-07-01 | Valorbec, Limited Partnership | Transistor-mismatch-insensitive current comparator cell |
US6421571B1 (en) | 2000-02-29 | 2002-07-16 | Bently Nevada Corporation | Industrial plant asset management system: apparatus and method |
EP1269286B1 (en) | 2000-03-03 | 2008-11-19 | International Business Machines Corporation | System for determining web application vulnerabilities |
DE60113073T2 (en) | 2000-03-10 | 2006-08-31 | Smiths Detection Inc., Pasadena | CONTROL FOR AN INDUSTRIAL PROCESS WITH ONE OR MULTIPLE MULTIDIMENSIONAL VARIABLES |
US20030037145A1 (en) | 2000-03-15 | 2003-02-20 | Michael Fagan | Apparatus and method of allocating communications resources |
WO2001069455A2 (en) | 2000-03-16 | 2001-09-20 | Poly Vista, Inc. | A system and method for analyzing a query and generating results and related questions |
US20020091677A1 (en) | 2000-03-20 | 2002-07-11 | Sridhar Mandayam Andampikai | Content dereferencing in website development |
US6473467B1 (en) | 2000-03-22 | 2002-10-29 | Qualcomm Incorporated | Method and apparatus for measuring reporting channel state information in a high efficiency, high performance communications system |
EP1311992A2 (en) | 2000-03-23 | 2003-05-21 | The Johns Hopkins University | Method and system for bio-surveillance detection and alerting |
US6643638B1 (en) | 2000-03-25 | 2003-11-04 | Kevin Houzhi Xu | System and method for storing and computing data and functions |
US6493331B1 (en) | 2000-03-30 | 2002-12-10 | Qualcomm Incorporated | Method and apparatus for controlling transmissions of a communications systems |
US7266502B2 (en) | 2000-03-31 | 2007-09-04 | Siebel Systems, Inc. | Feature centric release manager method and system |
EP1277119A4 (en) | 2000-03-31 | 2006-09-06 | Siebel Systems Inc | Thin client method and system for generating page delivery language output from applets, views, and screen definitions |
US6336137B1 (en) | 2000-03-31 | 2002-01-01 | Siebel Systems, Inc. | Web client-server system and method for incompatible page markup and presentation languages |
WO2001075747A1 (en) | 2000-03-31 | 2001-10-11 | Siebel Systems, Inc. | Workflow processes method and system |
US6577726B1 (en) | 2000-03-31 | 2003-06-10 | Siebel Systems, Inc. | Computer telephony integration hotelling method and system |
US6732100B1 (en) | 2000-03-31 | 2004-05-04 | Siebel Systems, Inc. | Database access method and system for user role defined access |
US6820082B1 (en) | 2000-04-03 | 2004-11-16 | Allegis Corporation | Rule based database security system and method |
US6831668B2 (en) | 2000-04-03 | 2004-12-14 | Business Objects, S.A. | Analytical reporting on top of multidimensional data model |
US7343295B2 (en) | 2000-04-05 | 2008-03-11 | Brenda Pomerance | Automated complaint resolution system |
AU2001257605A1 (en) | 2000-04-14 | 2001-10-30 | Savvion Incorporated | System and method for dynamically managing electronic business process |
US6865546B1 (en) | 2000-04-19 | 2005-03-08 | Amazon.Com, Inc. | Methods and systems of assisting users in purchasing items |
US6389510B1 (en) | 2000-04-25 | 2002-05-14 | Lucent Technologies Inc. | Method and apparatus for caching web-based information |
AU2001259690A1 (en) | 2000-05-09 | 2001-11-20 | Hnc Software, Inc. | Approach for generating rules |
US6496812B1 (en) | 2000-05-13 | 2002-12-17 | Object Power, Inc. | Method and system for measuring and valuing contributions by group members to the achievement of a group goal |
WO2001093157A1 (en) | 2000-05-26 | 2001-12-06 | Exitexchange Corporation | Post-session internet advertising system |
US7865358B2 (en) | 2000-06-26 | 2011-01-04 | Oracle International Corporation | Multi-user functionality for converting data from a first form to a second form |
US6728852B1 (en) | 2000-06-30 | 2004-04-27 | Sun Microsystems, Inc. | Method and apparatus for reducing heap size through adaptive object representation |
US6865575B1 (en) | 2000-07-06 | 2005-03-08 | Google, Inc. | Methods and apparatus for using a modified index to provide search results in response to an ambiguous search query |
US7103173B2 (en) | 2001-07-09 | 2006-09-05 | Austin Logistics Incorporated | System and method for preemptive goals based routing of contact records |
US6756994B1 (en) | 2000-08-07 | 2004-06-29 | Canon Kabushiki Kaisha | Method and apparatus for handling secondary dependencies |
US20020042831A1 (en) | 2000-08-16 | 2002-04-11 | Jeffrey Capone | System and method for building applications that adapt for multiple device and protocol standards |
US20020059566A1 (en) | 2000-08-29 | 2002-05-16 | Delcambre Lois M. | Uni-level description of computer information and transformation of computer information between representation schemes |
US6957199B1 (en) | 2000-08-30 | 2005-10-18 | Douglas Fisher | Method, system and service for conducting authenticated business transactions |
US7007299B2 (en) * | 2000-08-30 | 2006-02-28 | Citibank, N.A. | Method and system for internet hosting and security |
US20020029154A1 (en) | 2000-09-07 | 2002-03-07 | Hnc Software, Inc. | Mechanism and method for dynamic question handling through an electronic interface |
AU2001290646A1 (en) | 2000-09-08 | 2002-03-22 | The Regents Of The University Of California | Data source integration system and method |
US6567419B1 (en) | 2000-09-11 | 2003-05-20 | Yahoo! Inc. | Intelligent voice converter |
US6597775B2 (en) | 2000-09-29 | 2003-07-22 | Fair Isaac Corporation | Self-learning real-time prioritization of telecommunication fraud control actions |
US6678679B1 (en) | 2000-10-10 | 2004-01-13 | Science Applications International Corporation | Method and system for facilitating the refinement of data queries |
US6782091B1 (en) | 2000-10-13 | 2004-08-24 | Dunning Iii Emerson C | Virtual call distribution system |
US6748422B2 (en) | 2000-10-19 | 2004-06-08 | Ebay Inc. | System and method to control sending of unsolicited communications relating to a plurality of listings in a network-based commerce facility |
US20020118688A1 (en) | 2000-10-25 | 2002-08-29 | Ravi Jagannathan | Generation of fast busy signals in data networks |
US20020070972A1 (en) | 2000-10-27 | 2002-06-13 | Helmut Windl | Industrial automation display arrangement and method |
EP1364313A2 (en) | 2000-10-31 | 2003-11-26 | Michael Philip Kaufman | System and method for automatically generating user interfaces for arbitrarily complex or large databases |
US7885981B2 (en) | 2000-10-31 | 2011-02-08 | Michael Philip Kaufman | System and method for generating automatic user interface for arbitrarily complex or large databases |
WO2002044947A2 (en) | 2000-11-28 | 2002-06-06 | Asera, Inc. | Workflow driven rules-based generation of personalizable web pages |
US6920615B1 (en) | 2000-11-29 | 2005-07-19 | Verizon Corporate Services Group Inc. | Method and system for service-enablement gateway and its service portal |
US7020869B2 (en) | 2000-12-01 | 2006-03-28 | Corticon Technologies, Inc. | Business rules user interface for development of adaptable enterprise applications |
US7290061B2 (en) | 2000-12-05 | 2007-10-30 | Citrix Systems, Inc. | System and method for internet content collaboration |
US7596791B2 (en) | 2000-12-19 | 2009-09-29 | Emc Corporation | Methods and techniques for delivering rich Java applications over thin-wire connections with high performance and scalability |
US7363308B2 (en) | 2000-12-28 | 2008-04-22 | Fair Isaac Corporation | System and method for obtaining keyword descriptions of records from a large database |
US6636850B2 (en) | 2000-12-28 | 2003-10-21 | Fairisaac And Company, Inc. | Aggregate score matching system for transaction records |
US7254773B2 (en) | 2000-12-29 | 2007-08-07 | International Business Machines Corporation | Automated spell analysis |
US20020091678A1 (en) | 2001-01-05 | 2002-07-11 | Miller Nancy E. | Multi-query data visualization processes, data visualization apparatus, computer-readable media and computer data signals embodied in a transmission medium |
US20020133502A1 (en) | 2001-01-05 | 2002-09-19 | Rosenthal Richard Nelson | Method and system for interactive collection of information |
US7406475B2 (en) | 2001-01-09 | 2008-07-29 | British Telecommunications Public Limited Company | Software tool for heuristic search methods |
US6380910B1 (en) | 2001-01-10 | 2002-04-30 | Lucent Technologies Inc. | Wireless communications device having a compact antenna cluster |
US6801227B2 (en) | 2001-01-16 | 2004-10-05 | Siemens Medical Solutions Health Services Inc. | System and user interface supporting user navigation and concurrent application operation |
US7904595B2 (en) | 2001-01-18 | 2011-03-08 | Sdl International America Incorporated | Globalization management system and method therefor |
US6426723B1 (en) | 2001-01-19 | 2002-07-30 | Nortel Networks Limited | Antenna arrangement for multiple input multiple output communications systems |
US7174534B2 (en) | 2001-01-22 | 2007-02-06 | Symbol Technologies, Inc. | Efficient system and method for running and analyzing multi-channel, multi-modal applications |
US6526440B1 (en) | 2001-01-30 | 2003-02-25 | Google, Inc. | Ranking search results by reranking the results based on local inter-connectivity |
US7581230B2 (en) | 2001-02-06 | 2009-08-25 | Siebel Systems, Inc. | Adaptive communication application programming interface |
US6983238B2 (en) | 2001-02-07 | 2006-01-03 | American International Group, Inc. | Methods and apparatus for globalizing software |
WO2002069086A2 (en) | 2001-02-22 | 2002-09-06 | Accenture Global Services Gmbh | Distributed development environment for building internet applications by developers at remote locations |
US6804677B2 (en) | 2001-02-26 | 2004-10-12 | Ori Software Development Ltd. | Encoding semi-structured data for efficient search and browsing |
GB2373073A (en) | 2001-03-08 | 2002-09-11 | Escher Technologies Ltd | Process and system for developing validated and optimised object-oriented software |
US7194454B2 (en) | 2001-03-12 | 2007-03-20 | Lucent Technologies | Method for organizing records of database search activity by topical relevance |
US6771706B2 (en) | 2001-03-23 | 2004-08-03 | Qualcomm Incorporated | Method and apparatus for utilizing channel state information in a wireless communication system |
US7174514B2 (en) | 2001-03-28 | 2007-02-06 | Siebel Systems, Inc. | Engine to present a user interface based on a logical structure, such as one for a customer relationship management system, across a web site |
US7363388B2 (en) | 2001-03-28 | 2008-04-22 | Siebel Systems, Inc. | Method and system for direct server synchronization with a computing device |
US6829655B1 (en) | 2001-03-28 | 2004-12-07 | Siebel Systems, Inc. | Method and system for server synchronization with a computing device via a companion device |
US20030206192A1 (en) | 2001-03-31 | 2003-11-06 | Mingte Chen | Asynchronous message push to web browser |
US20030018705A1 (en) | 2001-03-31 | 2003-01-23 | Mingte Chen | Media-independent communication server |
US7930196B2 (en) | 2001-04-11 | 2011-04-19 | Fair Isaac Corporation | Model-based and data-driven analytic support for strategy development |
US6732095B1 (en) | 2001-04-13 | 2004-05-04 | Siebel Systems, Inc. | Method and apparatus for mapping between XML and relational representations |
US7257820B2 (en) | 2001-04-14 | 2007-08-14 | Siebel Systems, Inc. | Method and system for using integration objects with enterprise business applications |
GB0110326D0 (en) | 2001-04-27 | 2001-06-20 | Ibm | Method and apparatus for interoperation between legacy software and screen reader programs |
US7761288B2 (en) | 2001-04-30 | 2010-07-20 | Siebel Systems, Inc. | Polylingual simultaneous shipping of software |
US7171415B2 (en) | 2001-05-04 | 2007-01-30 | Sun Microsystems, Inc. | Distributed information discovery through searching selected registered information providers |
US6934702B2 (en) | 2001-05-04 | 2005-08-23 | Sun Microsystems, Inc. | Method and system of routing messages in a distributed search network |
US7000199B2 (en) | 2001-05-09 | 2006-02-14 | Fairisaac And Company Inc. | Methodology for viewing large strategies via a computer workstation |
US7089193B2 (en) | 2001-05-09 | 2006-08-08 | Prochain Solutions, Inc. | Multiple project scheduling system |
US7073177B2 (en) | 2001-05-10 | 2006-07-04 | Sun Microsystems, Inc. | Resource managing system for changing resource consumption state of the lower priority resource entity to more restrictive state when resource reached critical level |
US6832248B1 (en) | 2001-05-10 | 2004-12-14 | Agami Systems, Inc. | System and method for managing usage quotas |
US6785341B2 (en) | 2001-05-11 | 2004-08-31 | Qualcomm Incorporated | Method and apparatus for processing data in a multiple-input multiple-output (MIMO) communication system utilizing channel state information |
US6856992B2 (en) | 2001-05-15 | 2005-02-15 | Metatomix, Inc. | Methods and apparatus for real-time business visibility using persistent schema-less data storage |
US8572059B2 (en) | 2001-05-15 | 2013-10-29 | Colin P. Britton | Surveillance, monitoring and real-time events platform |
US6925457B2 (en) | 2001-07-27 | 2005-08-02 | Metatomix, Inc. | Methods and apparatus for querying a relational data store using schema-less queries |
US7058637B2 (en) | 2001-05-15 | 2006-06-06 | Metatomix, Inc. | Methods and apparatus for enterprise application integration |
US6766013B2 (en) | 2001-06-05 | 2004-07-20 | Avaya Technology Corp. | Timely shut-down of a real-time work center |
US6728702B1 (en) | 2001-06-18 | 2004-04-27 | Siebel Systems, Inc. | System and method to implement an integrated search center supporting a full-text search and query on a database |
US6711565B1 (en) | 2001-06-18 | 2004-03-23 | Siebel Systems, Inc. | Method, apparatus, and system for previewing search results |
US6782383B2 (en) | 2001-06-18 | 2004-08-24 | Siebel Systems, Inc. | System and method to implement a persistent and dismissible search center frame |
US6763351B1 (en) | 2001-06-18 | 2004-07-13 | Siebel Systems, Inc. | Method, apparatus, and system for attaching search results |
US20030001894A1 (en) | 2001-06-29 | 2003-01-02 | International Business Machines Corporation | Method and apparatus for dynamically determining actions to perform for an object |
US20030004934A1 (en) | 2001-06-29 | 2003-01-02 | Richard Qian | Creating and managing portable user preferences for personalizion of media consumption from device to device |
US6792420B2 (en) | 2001-06-29 | 2004-09-14 | International Business Machines Corporation | Method, system, and program for optimizing the processing of queries involving set operators |
US7130861B2 (en) | 2001-08-16 | 2006-10-31 | Sentius International Corporation | Automated creation and delivery of database content |
US7580871B2 (en) | 2001-08-31 | 2009-08-25 | Siebel Systems, Inc. | Method to generate a customizable product configurator |
US20030050834A1 (en) | 2001-09-07 | 2003-03-13 | Sergio Caplan | System and method for dynamic customizable interactive portal active during select computer time |
US7103875B1 (en) | 2001-09-21 | 2006-09-05 | Siebel Systems, Inc. | Methods and apparatus for integrated, automatic pseudo localization of software |
US7028225B2 (en) | 2001-09-25 | 2006-04-11 | Path Communications, Inc. | Application manager for monitoring and recovery of software based application processes |
AUPR796801A0 (en) | 2001-09-27 | 2001-10-25 | Plugged In Communications Pty Ltd | Computer user interface tool for navigation of data stored in directed graphs |
AUPR796701A0 (en) | 2001-09-27 | 2001-10-25 | Plugged In Communications Pty Ltd | Database query system and method |
US6966033B1 (en) | 2001-09-28 | 2005-11-15 | Emc Corporation | Methods and apparatus for graphically managing resources |
US6724399B1 (en) | 2001-09-28 | 2004-04-20 | Siebel Systems, Inc. | Methods and apparatus for enabling keyboard accelerators in applications implemented via a browser |
US20030065544A1 (en) | 2001-09-28 | 2003-04-03 | Elzinga C. Bret | Method and system for performing dynamic scheduling |
US6993712B2 (en) | 2001-09-28 | 2006-01-31 | Siebel Systems, Inc. | System and method for facilitating user interaction in a browser environment |
US6978445B2 (en) | 2001-09-28 | 2005-12-20 | Siebel Systems, Inc. | Method and system for supporting user navigation in a browser environment |
US6901595B2 (en) | 2001-09-29 | 2005-05-31 | Siebel Systems, Inc. | Method, apparatus, and system for implementing a framework to support a web-based application |
US8359335B2 (en) | 2001-09-29 | 2013-01-22 | Siebel Systems, Inc. | Computing system and method to implicitly commit unsaved data for a world wide web application |
US7146617B2 (en) | 2001-09-29 | 2006-12-05 | Siebel Systems, Inc. | Method, apparatus, and system for implementing view caching in a framework to support web-based applications |
US7962565B2 (en) | 2001-09-29 | 2011-06-14 | Siebel Systems, Inc. | Method, apparatus and system for a mobile web client |
US20030084401A1 (en) | 2001-10-16 | 2003-05-01 | Abel Todd J. | Efficient web page localization |
US7064766B2 (en) | 2001-10-18 | 2006-06-20 | Microsoft Corporation | Intelligent caching data structure for immediate mode graphics |
US6954737B2 (en) | 2001-11-05 | 2005-10-11 | Johnsondiversey, Inc. | Method and apparatus for work management for facility maintenance |
JP4018900B2 (en) | 2001-11-22 | 2007-12-05 | 株式会社日立製作所 | Virtual computer system and program |
US20040054610A1 (en) | 2001-11-28 | 2004-03-18 | Monetaire | Monetaire wealth management platform |
US7289793B2 (en) | 2001-12-03 | 2007-10-30 | Scott Gilbert | Method and apparatus for displaying real-time information objects between a wireless mobile user station and multiple information sources based upon event driven parameters and user modifiable object manifest |
US7458015B2 (en) | 2001-12-12 | 2008-11-25 | Nec Corporation | Electronic document reading system and method |
US20030115281A1 (en) | 2001-12-13 | 2003-06-19 | Mchenry Stephen T. | Content distribution network server management system architecture |
US20070203756A1 (en) | 2001-12-17 | 2007-08-30 | Siebel Systems, Inc. | Configuration of employee benefit plans |
US6804330B1 (en) | 2002-01-04 | 2004-10-12 | Siebel Systems, Inc. | Method and system for accessing CRM data via voice |
US7536294B1 (en) | 2002-01-08 | 2009-05-19 | Oracle International Corporation | Method and apparatus for translating computer programs |
US7334039B1 (en) | 2002-02-01 | 2008-02-19 | Oracle International Corporation | Techniques for generating rules for a dynamic rule-based system that responds to requests for a resource on a network |
US6892309B2 (en) | 2002-02-08 | 2005-05-10 | Enterasys Networks, Inc. | Controlling usage of network resources by a user at the user's entry point to a communications network based on an identity of the user |
US7058890B2 (en) | 2002-02-13 | 2006-06-06 | Siebel Systems, Inc. | Method and system for enabling connectivity to a data system |
US7813937B1 (en) | 2002-02-15 | 2010-10-12 | Fair Isaac Corporation | Consistency modeling of healthcare claims to detect fraud and abuse |
US7263492B1 (en) | 2002-02-15 | 2007-08-28 | Fair Isaac Corporation | Sequencing models of healthcare related states |
US7076558B1 (en) | 2002-02-27 | 2006-07-11 | Microsoft Corporation | User-centric consent management system and method |
US6928436B2 (en) | 2002-02-28 | 2005-08-09 | Ilog Sa | Interactive generation of graphical visualizations of large data structures |
US7249013B2 (en) | 2002-03-11 | 2007-07-24 | University Of Southern California | Named entity translation |
US7162715B1 (en) | 2002-03-16 | 2007-01-09 | I-Squared, Inc. | Method and apparatus for preemptive monitoring of software binaries by instruction interception and dynamic recompilation |
US7131071B2 (en) | 2002-03-29 | 2006-10-31 | Siebel Systems, Inc. | Defining an approval process for requests for approval |
US7672853B2 (en) | 2002-03-29 | 2010-03-02 | Siebel Systems, Inc. | User interface for processing requests for approval |
US6898645B2 (en) | 2002-04-17 | 2005-05-24 | Canon Kabushiki Kaisha | Dynamic generation of a user interface based on automatic device detection |
US6707905B2 (en) | 2002-04-18 | 2004-03-16 | Avaya Technology Corp. | Location enhanced automatic work distribution |
US6724329B2 (en) | 2002-04-24 | 2004-04-20 | Intel Corporation | Decision feedback equalization employing a lookup table |
TW574660B (en) | 2002-05-16 | 2004-02-01 | Ind Tech Res Inst | Method targeting at range search and for information search complying with specified rule |
US6791372B2 (en) | 2002-06-04 | 2004-09-14 | Intel Corporation | Active cascode differential latch |
US7941348B2 (en) | 2002-06-10 | 2011-05-10 | Ebay Inc. | Method and system for scheduling transaction listings at a network-based transaction facility |
US20070208553A1 (en) | 2002-06-20 | 2007-09-06 | Mark Hastings | Visual context for translation |
US7110937B1 (en) | 2002-06-20 | 2006-09-19 | Siebel Systems, Inc. | Translation leveraging |
US7640548B1 (en) | 2002-06-21 | 2009-12-29 | Siebel Systems, Inc. | Task based user interface |
JP4528116B2 (en) | 2002-06-25 | 2010-08-18 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Method and system for monitoring application performance in a distributed environment |
US7594181B2 (en) | 2002-06-27 | 2009-09-22 | Siebel Systems, Inc. | Prototyping graphical user interfaces |
US8639542B2 (en) | 2002-06-27 | 2014-01-28 | Siebel Systems, Inc. | Method and apparatus to facilitate development of a customer-specific business process model |
US7437720B2 (en) | 2002-06-27 | 2008-10-14 | Siebel Systems, Inc. | Efficient high-interactivity user interface for client-server applications |
US6754475B1 (en) | 2002-06-28 | 2004-06-22 | Motorola, Inc. | Transmission performance measurement and use thereof |
US20040133416A1 (en) | 2002-07-18 | 2004-07-08 | Norio Fukuoka | Information terminal device, method of acquiring information corresponding to language identification information from server and program thereof, network system, additional function purchasing progam, and program function adding method |
AU2003252065A1 (en) | 2002-07-22 | 2004-02-09 | Thought, Inc. | Dynamic object- driven database manipulation and mapping system |
US7194413B2 (en) | 2002-07-31 | 2007-03-20 | Deere & Company | Method of providing localized information from a single global transformation source |
US6940917B2 (en) | 2002-08-27 | 2005-09-06 | Qualcomm, Incorporated | Beam-steering and beam-forming for wideband MIMO/MISO systems |
US6847970B2 (en) | 2002-09-11 | 2005-01-25 | International Business Machines Corporation | Methods and apparatus for managing dependencies in distributed systems |
US7058660B2 (en) | 2002-10-02 | 2006-06-06 | Bank One Corporation | System and method for network-based project management |
US20040139021A1 (en) | 2002-10-07 | 2004-07-15 | Visa International Service Association | Method and system for facilitating data access and management on a secure token |
GB2394548B (en) | 2002-10-21 | 2005-12-14 | Abb Offshore Systems Ltd | Monitoring a microseismic event |
US20040088199A1 (en) | 2002-10-31 | 2004-05-06 | Childress Allen B. | Method of forming a business rule |
EP1561178A4 (en) | 2002-11-15 | 2009-08-12 | Fair Isaac Corp | Fraud and abuse detection and entity profiling in hierarchical coded payment systems |
US8332828B2 (en) | 2002-11-20 | 2012-12-11 | Purenative Software Corporation | System for translating diverse programming languages |
US20040103014A1 (en) | 2002-11-25 | 2004-05-27 | Teegan Hugh A. | System and method for composing and constraining automated workflow |
US9396473B2 (en) | 2002-11-27 | 2016-07-19 | Accenture Global Services Limited | Searching within a contact center portal |
US7024141B2 (en) | 2002-12-13 | 2006-04-04 | Ricoh Company, Ltd. | Developing device and process cartridge for an image forming apparatus |
US7818506B1 (en) | 2002-12-13 | 2010-10-19 | Vignette Software Llc | Method and system for cache management |
US7509251B2 (en) | 2002-12-23 | 2009-03-24 | International Business Machines Corporation | Mock translating software applications at runtime |
WO2004061815A1 (en) | 2002-12-31 | 2004-07-22 | Siebel Systems, Inc. | A method and apparatus for an integrated process modeller |
US7610575B2 (en) | 2003-01-08 | 2009-10-27 | Consona Crm Inc. | System and method for the composition, generation, integration and execution of business processes over a network |
US7519541B2 (en) | 2003-01-29 | 2009-04-14 | Cerner Innovation, Inc. | System and method in a computer system for managing a number of attachments associated with a patient |
US7058367B1 (en) | 2003-01-31 | 2006-06-06 | At&T Corp. | Rate-adaptive methods for communicating over multiple input/multiple output wireless systems |
US20040162822A1 (en) | 2003-02-13 | 2004-08-19 | Khachatur Papanyan | Method and apparatus for converting in-line database queries to stored procedures |
GB0304639D0 (en) | 2003-02-28 | 2003-04-02 | Kiq Ltd | Classification using re-sampling of probability estimates |
US6927728B2 (en) | 2003-03-13 | 2005-08-09 | Motorola, Inc. | Method and apparatus for multi-antenna transmission |
US7904340B2 (en) | 2003-03-24 | 2011-03-08 | Siebel Systems, Inc. | Methods and computer-readable medium for defining a product model |
WO2004086197A2 (en) | 2003-03-24 | 2004-10-07 | Siebel Systems, Inc. | Custom common object |
WO2004086198A2 (en) | 2003-03-24 | 2004-10-07 | Siebel Systems, Inc. | Common common object |
US8762415B2 (en) | 2003-03-25 | 2014-06-24 | Siebel Systems, Inc. | Modeling of order data |
US7124145B2 (en) | 2003-03-27 | 2006-10-17 | Millennium It (Usa) Inc. | System and method for dynamic business logic rule integration |
US20040220792A1 (en) | 2003-04-30 | 2004-11-04 | Gallanis Peter Thomas | Performance modeling for information systems |
US6976144B1 (en) | 2003-05-06 | 2005-12-13 | Pegasystems, Inc. | Methods and apparatus for digital data processing with mutable inheritance |
US7269544B2 (en) | 2003-05-20 | 2007-09-11 | Hewlett-Packard Development Company, L.P. | System and method for identifying special word usage in a document |
US7177877B2 (en) | 2003-05-29 | 2007-02-13 | Electronic Data Systems Corporation | Method and system for externalizing conditional logic for collecting multi-purpose objects |
WO2005001627A2 (en) | 2003-06-04 | 2005-01-06 | Rulespower, Inc. | Relational logic management system |
US7409336B2 (en) | 2003-06-19 | 2008-08-05 | Siebel Systems, Inc. | Method and system for searching data based on identified subset of categories and relevance-scored text representation-category combinations |
US20040260659A1 (en) | 2003-06-23 | 2004-12-23 | Len Chan | Function space reservation system |
EP1492232A1 (en) | 2003-06-27 | 2004-12-29 | Dialog Semiconductor GmbH | Comparator with high-voltage inputs in an extended CMOS process for higher voltage levels |
US7237227B2 (en) | 2003-06-30 | 2007-06-26 | Siebel Systems, Inc. | Application user interface template with free-form layout |
JP4400126B2 (en) | 2003-08-08 | 2010-01-20 | 株式会社日立製作所 | Centralized disk usage control method in virtual centralized network storage system |
US7178109B2 (en) | 2003-08-12 | 2007-02-13 | Chordiant Software, Inc. | Process/viewer interface |
US7596504B2 (en) | 2003-08-20 | 2009-09-29 | International Business Machines Corporation | Management of support center calls |
US20050049924A1 (en) | 2003-08-27 | 2005-03-03 | Debettencourt Jason | Techniques for use with application monitoring to obtain transaction data |
US8635218B2 (en) | 2003-09-02 | 2014-01-21 | International Business Machines Corporation | Generation of XSLT style sheets for different portable devices |
US6918222B2 (en) | 2003-09-09 | 2005-07-19 | Illinois Tool Works Inc. | Fastener for spacing object from substrate |
US8094804B2 (en) | 2003-09-26 | 2012-01-10 | Avaya Inc. | Method and apparatus for assessing the status of work waiting for service |
US7318020B1 (en) | 2003-10-08 | 2008-01-08 | Microsoft Corporation | Methods and systems for external localization |
JP2005149126A (en) | 2003-11-14 | 2005-06-09 | Sony Corp | Information acquiring system and method, and information processing program |
JP3971368B2 (en) | 2003-11-18 | 2007-09-05 | 株式会社東芝 | A signal intensity detection circuit and an amplification factor control system using the same. |
US7412388B2 (en) | 2003-12-12 | 2008-08-12 | International Business Machines Corporation | Language-enhanced programming tools |
US8140691B2 (en) | 2003-12-12 | 2012-03-20 | International Business Machines Corporation | Role-based views access to a workflow weblog |
US8417682B2 (en) | 2003-12-12 | 2013-04-09 | International Business Machines Corporation | Visualization of attributes of workflow weblogs |
US7433350B2 (en) | 2003-12-24 | 2008-10-07 | At&T Intellectual Property Ii, L.P. | Methods and apparatus for directory enabled network services |
US7321897B2 (en) | 2004-01-22 | 2008-01-22 | Microsoft Corporation | Binary dependency database |
US7779395B1 (en) | 2004-03-05 | 2010-08-17 | Adobe Systems Incorporated | System and method for routing data |
US7010465B2 (en) | 2004-03-29 | 2006-03-07 | Microsoft Corporation | Scalability test and analysis |
US20050228875A1 (en) | 2004-04-13 | 2005-10-13 | Arnold Monitzer | System for estimating processing requirements |
US20050234882A1 (en) | 2004-04-20 | 2005-10-20 | Calpont Corporation | Data structure for a hardware database management system |
US20050267770A1 (en) | 2004-05-26 | 2005-12-01 | International Business Machines Corporation | Methods and apparatus for performing task management based on user context |
US7665063B1 (en) | 2004-05-26 | 2010-02-16 | Pegasystems, Inc. | Integration of declarative rule-based processing with procedural programming |
US7076493B2 (en) | 2004-05-28 | 2006-07-11 | Metadata, Llc | Defining a data dependency path through a body of related data |
US7424485B2 (en) | 2004-06-03 | 2008-09-09 | Microsoft Corporation | Method and apparatus for generating user interfaces based upon automation with full flexibility |
US8738412B2 (en) | 2004-07-13 | 2014-05-27 | Avaya Inc. | Method and apparatus for supporting individualized selection rules for resource allocation |
AR051014A1 (en) | 2004-08-24 | 2006-12-13 | Geneva Software Technologies Ltd | SYSTEM AND METHOD FOR MIGRATION OF A PRODUCT IN VARIOUS LANGUAGES |
US20060092467A1 (en) | 2004-09-01 | 2006-05-04 | Dumitrescu Tiberiu A | Print job workflow system |
US20060063138A1 (en) | 2004-09-16 | 2006-03-23 | Sap Aktiengesellschaft | Methods and systems for adapting data from a user interface |
US20060064481A1 (en) | 2004-09-17 | 2006-03-23 | Anthony Baron | Methods for service monitoring and control |
US20060064667A1 (en) | 2004-09-20 | 2006-03-23 | Freitas Jose D | System and method of model-driven development using a transformation model |
US8276099B2 (en) | 2004-09-28 | 2012-09-25 | David Arthur Yost | System of GUI text cursor, caret, and selection |
US7496642B2 (en) | 2004-09-29 | 2009-02-24 | International Business Machines Corporation | Adaptive vicinity prefetching for filesystem metadata |
US20060075360A1 (en) | 2004-10-04 | 2006-04-06 | Edwards Systems Technology, Inc. | Dynamic highlight prompting apparatus and method |
US8024703B2 (en) | 2004-10-22 | 2011-09-20 | International Business Machines Corporation | Building an open model driven architecture pattern based on exemplars |
US7376933B2 (en) | 2004-10-22 | 2008-05-20 | International Business Machines Corporation | System and method for creating application content using an open model driven architecture |
US7577561B2 (en) | 2004-11-09 | 2009-08-18 | Sony Online Entertainment Llc | System and method for generating a target language markup language text template |
US7983895B2 (en) | 2004-11-09 | 2011-07-19 | Sony Online Entertainment Llc | System and method for generating grammatically correct text strings |
US9070104B2 (en) | 2004-11-12 | 2015-06-30 | Sap Se | Cross-context task management |
US20070226031A1 (en) | 2004-11-30 | 2007-09-27 | Manson Nicholas R | Methods and apparatuses for grouped option specification |
US7554522B2 (en) | 2004-12-23 | 2009-06-30 | Microsoft Corporation | Personalization of user accessibility options |
US20060149751A1 (en) | 2004-12-30 | 2006-07-06 | Sripad Jade | Custom templates |
US7555645B2 (en) | 2005-01-06 | 2009-06-30 | Oracle International Corporation | Reactive audit protection in the database (RAPID) |
US8335704B2 (en) | 2005-01-28 | 2012-12-18 | Pegasystems Inc. | Methods and apparatus for work management and routing |
JP2006244451A (en) | 2005-02-01 | 2006-09-14 | Seiko Epson Corp | Resource management system, resource management program, and resource management method |
US7653528B2 (en) | 2005-03-08 | 2010-01-26 | Microsoft Corporation | Resource authoring incorporating ontology |
JP2006252049A (en) | 2005-03-09 | 2006-09-21 | Fuji Xerox Co Ltd | Translation system, translation method and program |
US7302417B2 (en) | 2005-05-02 | 2007-11-27 | Synopsys, Inc. | Method and apparatus for improving efficiency of constraint solving |
US20060271920A1 (en) | 2005-05-24 | 2006-11-30 | Wael Abouelsaadat | Multilingual compiler system and method |
US8583827B2 (en) | 2005-05-26 | 2013-11-12 | Citrix Systems, Inc. | Dynamic data optimization in data network |
US7460884B2 (en) | 2005-06-29 | 2008-12-02 | Microsoft Corporation | Data buddy |
US20070005623A1 (en) | 2005-06-30 | 2007-01-04 | Microsoft Corporation | Process oriented message driven workflow programming model |
US8140362B2 (en) | 2005-08-30 | 2012-03-20 | International Business Machines Corporation | Automatically processing dynamic business rules in a content management system |
US20070055938A1 (en) | 2005-09-07 | 2007-03-08 | Avaya Technology Corp. | Server-based method for providing internet content to users with disabilities |
CN1936849A (en) | 2005-09-19 | 2007-03-28 | 国际商业机器公司 | Resource dynamic regulation method and apparatus |
US7787609B1 (en) | 2005-10-06 | 2010-08-31 | Avaya Inc. | Prioritized service delivery based on presence and availability of interruptible enterprise resources with skills |
US7689447B1 (en) | 2005-10-26 | 2010-03-30 | At&T Intellectual Property Ii, L.P. | Worklist integration of logical and physical tasks |
JP2007141123A (en) | 2005-11-22 | 2007-06-07 | Internatl Business Mach Corp <Ibm> | Link of same character strings in different files |
US20070136068A1 (en) | 2005-12-09 | 2007-06-14 | Microsoft Corporation | Multimodal multilingual devices and applications for enhanced goal-interpretation and translation for service providers |
US20070143163A1 (en) | 2005-12-16 | 2007-06-21 | Sap Ag | Systems and methods for organizing and monitoring data collection |
US20070143851A1 (en) | 2005-12-21 | 2007-06-21 | Fiberlink | Method and systems for controlling access to computing resources based on known security vulnerabilities |
US7640222B2 (en) | 2006-03-03 | 2009-12-29 | Pegasystems Inc. | Rules base systems and methods with circumstance translation |
US7647417B1 (en) | 2006-03-15 | 2010-01-12 | Netapp, Inc. | Object cacheability with ICAP |
US20070233902A1 (en) | 2006-03-30 | 2007-10-04 | Alan Trefler | User interface methods and apparatus for rules processing |
US8924335B1 (en) | 2006-03-30 | 2014-12-30 | Pegasystems Inc. | Rule-based user interface conformance methods |
US20090132232A1 (en) | 2006-03-30 | 2009-05-21 | Pegasystems Inc. | Methods and apparatus for implementing multilingual software applications |
US8516193B1 (en) | 2006-03-30 | 2013-08-20 | Pegasystems Inc. | Techniques for content-based caching in a computer system |
US20080208785A1 (en) | 2006-03-30 | 2008-08-28 | Pegasystems, Inc. | User interface methods and apparatus for rules processing |
US7827155B2 (en) | 2006-04-21 | 2010-11-02 | Microsoft Corporation | System for processing formatted data |
US8331549B2 (en) | 2006-05-01 | 2012-12-11 | Verint Americas Inc. | System and method for integrated workforce and quality management |
US7937690B2 (en) | 2006-05-23 | 2011-05-03 | Hewlett-Packard Development Company, L.P. | Evaluating performance of software application |
EP1870804A1 (en) | 2006-06-22 | 2007-12-26 | Microsoft Corporation | Dynamic software localization |
US20080077384A1 (en) | 2006-09-22 | 2008-03-27 | International Business Machines Corporation | Dynamically translating a software application to a user selected target language that is not natively provided by the software application |
US20080085502A1 (en) | 2006-10-04 | 2008-04-10 | Ecollege.Com | Web service api for student information and course management systems |
US20080109467A1 (en) | 2006-11-03 | 2008-05-08 | Microsoft Corporation | Data entity centric approach for designing workflows |
US7996850B2 (en) | 2006-12-28 | 2011-08-09 | Sap Ag | Dynamic business object properties for SOA architectures |
US8037329B2 (en) | 2007-01-31 | 2011-10-11 | Hewlett-Packard Development Company, L.P. | Systems and methods for determining power consumption profiles for resource users and using the profiles for resource allocation |
US20080189679A1 (en) | 2007-02-05 | 2008-08-07 | Jared Rodriguez | Method and system for creating, deploying, and utilizing a service |
JP4396994B2 (en) | 2007-02-09 | 2010-01-13 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Resource file translation verification method, apparatus, and program |
US8250525B2 (en) | 2007-03-02 | 2012-08-21 | Pegasystems Inc. | Proactive performance management for multi-user enterprise software systems |
JP4412674B2 (en) | 2007-04-18 | 2010-02-10 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Apparatus and method for supporting model-driven development |
US7971180B2 (en) | 2007-06-13 | 2011-06-28 | International Business Machines Corporation | Method and system for evaluating multi-dimensional project plans for implementing packaged software applications |
US8001519B2 (en) | 2007-06-27 | 2011-08-16 | International Business Machines Corporation | Model driven development including aspect integration tool |
US8112434B2 (en) | 2007-07-09 | 2012-02-07 | International Business Machines Corporation | Performance of an enterprise service bus by decomposing a query result from the service registry |
US20090083697A1 (en) | 2007-09-21 | 2009-03-26 | Honeywell International Inc. | Integration of User Interface Design and Model Driven Development |
US8095570B2 (en) | 2007-11-26 | 2012-01-10 | International Business Machines Corporation | Decorated model architecture for efficient model-driven application development |
US20090158407A1 (en) | 2007-12-13 | 2009-06-18 | Fiberlink Communications Corporation | Api translation for network access control (nac) agent |
US7975217B2 (en) | 2007-12-21 | 2011-07-05 | Google Inc. | Embedding metadata with displayable content and applications thereof |
US7984035B2 (en) | 2007-12-28 | 2011-07-19 | Microsoft Corporation | Context-based document search |
US20090282384A1 (en) | 2008-05-12 | 2009-11-12 | Raytheon Company | Framework-Based Model-Driven Software Development |
US8271935B2 (en) | 2008-07-09 | 2012-09-18 | International Business Machines Corporation | Methods and tools for data-driven application engineering |
US8386960B1 (en) | 2008-08-29 | 2013-02-26 | Adobe Systems Incorporated | Building object interactions |
US20100217737A1 (en) | 2009-02-20 | 2010-08-26 | Ajay Shama | Method and system for business rules management |
US8843435B1 (en) | 2009-03-12 | 2014-09-23 | Pegasystems Inc. | Techniques for dynamic data processing |
US8468492B1 (en) | 2009-03-30 | 2013-06-18 | Pegasystems, Inc. | System and method for creation and modification of software applications |
US8880487B1 (en) | 2011-02-18 | 2014-11-04 | Pegasystems Inc. | Systems and methods for distributed rules processing |
-
2011
- 2011-02-18 US US13/031,097 patent/US8880487B1/en active Active
-
2014
- 2014-10-29 US US14/527,348 patent/US9270743B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6098172A (en) * | 1997-09-12 | 2000-08-01 | Lucent Technologies Inc. | Methods and apparatus for a computer network firewall with proxy reflection |
US6810429B1 (en) * | 2000-02-03 | 2004-10-26 | Mitsubishi Electric Research Laboratories, Inc. | Enterprise integration system |
US20070130130A1 (en) * | 2005-12-02 | 2007-06-07 | Salesforce.Com, Inc. | Systems and methods for securing customer data in a multi-tenant environment |
US20120041921A1 (en) * | 2010-08-16 | 2012-02-16 | Salesforce.Com, Inc. | Mechanism for facilitating efficient business rules management and data processing |
Cited By (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9658735B2 (en) | 2006-03-30 | 2017-05-23 | Pegasystems Inc. | Methods and apparatus for user interface optimization |
US10838569B2 (en) | 2006-03-30 | 2020-11-17 | Pegasystems Inc. | Method and apparatus for user interface non-conformance detection and correction |
US10467200B1 (en) | 2009-03-12 | 2019-11-05 | Pegasystems, Inc. | Techniques for dynamic data processing |
US9678719B1 (en) | 2009-03-30 | 2017-06-13 | Pegasystems Inc. | System and software for creation and modification of software |
US10572236B2 (en) | 2011-12-30 | 2020-02-25 | Pegasystems, Inc. | System and method for updating or modifying an application without manual coding |
US11057313B2 (en) | 2014-10-10 | 2021-07-06 | Pegasystems Inc. | Event processing with enhanced throughput |
US10469396B2 (en) | 2014-10-10 | 2019-11-05 | Pegasystems, Inc. | Event processing with enhanced throughput |
US10698599B2 (en) | 2016-06-03 | 2020-06-30 | Pegasystems, Inc. | Connecting graphical shapes using gestures |
US10698647B2 (en) | 2016-07-11 | 2020-06-30 | Pegasystems Inc. | Selective sharing for collaborative application usage |
US11038967B2 (en) * | 2017-01-26 | 2021-06-15 | Verizon Patent And Licensing Inc. | Enabling hypertext transfer protocol (HTTP) connect in association with a toll-free data service |
EP3611616A1 (en) | 2018-08-14 | 2020-02-19 | Pegasystems Inc. | Software code optimizer and method |
US11048488B2 (en) | 2018-08-14 | 2021-06-29 | Pegasystems, Inc. | Software code optimizer and method |
WO2021234474A1 (en) * | 2020-05-19 | 2021-11-25 | International Business Machines Corporation | Rule distribution across instances of rules engine |
GB2610769A (en) * | 2020-05-19 | 2023-03-15 | Ibm | Rule distribution across instances of rules engine |
US11727283B2 (en) | 2020-05-19 | 2023-08-15 | International Business Machines Corporation | Rule distribution across instances of rules engine |
US11567945B1 (en) | 2020-08-27 | 2023-01-31 | Pegasystems Inc. | Customized digital content generation systems and methods |
Also Published As
Publication number | Publication date |
---|---|
US8880487B1 (en) | 2014-11-04 |
US9270743B2 (en) | 2016-02-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9270743B2 (en) | Systems and methods for distributed rules processing | |
US10620944B2 (en) | Cloud-based decision management platform | |
US10176337B2 (en) | Method and system for allowing access to developed applications via a multi-tenant on-demand database service | |
US10079905B2 (en) | Cross domain in-browser proxy | |
US7580946B2 (en) | Smart integration engine and metadata-oriented architecture for automatic EII and business integration | |
US9779252B2 (en) | Crowd-sourced security analysis | |
US9544327B1 (en) | Prioritizing security findings in a SAST tool based on historical security analysis | |
US9697377B2 (en) | On-demand database service system, method and computer program product for conditionally allowing an application of an entity access to data of another entity | |
US20160098298A1 (en) | Methods and apparatus for integrated work management | |
US8630969B2 (en) | Systems and methods for implementing business rules designed with cloud computing | |
US11875288B2 (en) | Discovering and using application deployment dependencies to augment governance and compliance policy | |
US20220237202A1 (en) | Canonical data model for distributed data catalog and metadata exchange | |
Park et al. | Approach for selecting and integrating cloud services to construct hybrid cloud | |
US11748686B1 (en) | Automated onboarding service | |
Schneider | Performance Benchmarking of Open-Source Service Meshes Using Load Testing | |
Sehgal | Cloud Based Cab Booking Service | |
Järnstedt | Design of an Enterprise Resource Planning System Using Service-Oriented Architecture | |
Moreno | Advanced Design Frameworks for Modern, Scalable Applications: Strategic Approaches to Building High-Performance, Resilient, and Modular Architectures in Distributed Systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: PEGASYSTEMS INC., MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CLINTON, JOHN W.;TREFLER, ALAN;FRENKEL, BENJAMIN;REEL/FRAME:035337/0194 Effective date: 20110602 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: SURCHARGE FOR LATE PAYMENT, LARGE ENTITY (ORIGINAL EVENT CODE: M1554); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: PNC BANK, NATIONAL ASSOCIATION, MASSACHUSETTS Free format text: SECURITY INTEREST;ASSIGNOR:PEGASYSTEMS INC.;REEL/FRAME:051016/0631 Effective date: 20191105 |
|
FEPP | Fee payment procedure |
Free format text: 7.5 YR SURCHARGE - LATE PMT W/IN 6 MO, LARGE ENTITY (ORIGINAL EVENT CODE: M1555); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |