US20070033247A1 - Methods and system for distributing data to technical computing workers - Google Patents

Methods and system for distributing data to technical computing workers Download PDF

Info

Publication number
US20070033247A1
US20070033247A1 US11195927 US19592705A US2007033247A1 US 20070033247 A1 US20070033247 A1 US 20070033247A1 US 11195927 US11195927 US 11195927 US 19592705 A US19592705 A US 19592705A US 2007033247 A1 US2007033247 A1 US 2007033247A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
data
task
interface
technical computing
step
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.)
Abandoned
Application number
US11195927
Inventor
Jocelyn Martin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
MathWorks Inc
Original Assignee
MathWorks Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/465Distributed object oriented systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/50Indexing scheme relating to G06F9/50
    • G06F2209/5017Task decomposition

Abstract

A method and system is disclosed for providing a distributed technical computing environment for distributing technical computing tasks from a technical computing client to technical computing workers for execution of the tasks on one or more computers systems. Tasks can be defined on a technical computing client, and the tasks organized into jobs. The technical computing client can directly distribute tasks to one or more technical computing workers. Furthermore, the technical computing client can submit tasks, or jobs comprising tasks, to an automatic task distribution mechanism that distributes the tasks automatically to one or more technical computing workers providing technical computing services. The technical computing worker performs technical computing of tasks and the results of the execution of tasks may be provided to the technical computing client. Data associated with the tasks is managed by a programmable interface associated with a data storage repository. The interface allows the various entities of the distributed technical computing environment to access data services performable by the interface or by a file system or a database and database management system associated with the data.

Description

    TECHNICAL FIELD
  • The present invention generally relates to technical computing, and more particularly distributing technical computing processing to multiple computers in a network in a distributed technical computing environment.
  • BACKGROUND INFORMATION
  • MATLAB® is a product of The MathWorks, Inc. of Natick, Mass., which provides engineers, scientists, mathematicians, and educators across a diverse range of industries with an environment for technical computing applications. MATLAB® is an intuitive high performance language and technical computing environment that provides mathematical and graphical tools for mathematical computation, data analysis, visualization, and algorithm development. MATLAB® integrates numerical analysis, matrix computation, signal processing, and graphics in an easy-to-use environment where problems and solutions are expressed in familiar mathematical notation, without traditional programming. MATLAB® is used to solve complex engineering and scientific problems by developing mathematical models that simulate the problem. A model is prototyped, tested and analyzed by running the model under multiple boundary conditions, data parameters, or just a number of initial guesses. In MATLAB®, one can easily modify the model, plot a new variable or reformulate the problem in a rapid interactive fashion that is typically not feasible in a non-interpreted programming such as Fortran or C.
  • As a desktop application, MATLAB® allows scientists and engineers to interactively perform complex analysis and modeling in their familiar workstation environment. However, a single workstation can be limiting to the size of the problem that can be solved, because of the relationship of the computing power of the workstation to the computing power necessary to execute computing intensive iterative processing of complex problems in a reasonable time.
  • For example, a simulation of a large complex aircraft model may take a reasonable time to run with a single computation with a specified set of parameters. However, the analysis of the problem may also require the model be computed multiple times with a different set of parameters, e.g., at one-hundred different altitude levels and fifty different aircraft weights, to understand the behavior of the model under varied conditions. This would require five-thousand computations to analyze the problem as desired and the single computer would take an unreasonable or undesirable amount of time to perform these simulations. In this case, the single computer would be allocated full-time to performing the computation while many computer resources on the network may be idle. Additionally, the benefit of the interactive features of the software is reduced as the computation time increases.
  • With many engineering and scientific problems requiring larger and more complex modeling, computations accordingly become more resource intensive and time-consuming. When a computation becomes so large and complex that it cannot be completed in a reasonable amount of time on a single computer, distributed computing in a distributed technical computing environment, for example Distributed Computing Toolbox for MATLAB® and MATLAB® Distributed Computing Engine, provides a solution to decrease the computation time as needed.
  • In such distributed technical computing environments, a scheduler, such as a load sharing facility (LSF), a portable batch system (PBS), a high-throughput computing (HTC) environment, such as Condor, Microsoft Cluster Manager, and the like, manage distribution of tasks within the distributed technical computing environment. Although such schedulers distribute tasks to the various computational devices in the distributed technical computing environment, the data associated with such tasks is stored in a shared file system accessible to those computational devices. This severely limits the types of clients and workers that can work with Distributed Computing Toolbox. Moreover, this limits the abilities of programs using the scheduler, to the capabilities of the file system with respect to being informed of changes and other events. Still further, it requires the data validation occur in the process generating the file. Accordingly, there exists a need to improve the management and handling of data associated with distributed tasks in the distributed technical computing environment.
  • SUMMARY OF THE INVENTION
  • The present invention provides methods and a system for managing distribution of data associated with distributed technical computing tasks in a distributed technical computing environment. A technical computing client may define a job comprising one or more tasks. The technical computing client through an intermediary such as a scheduler can distribute these tasks to technical computing workers for technical computing of the task. The technical computing workers perform technical computing of the task and may provide a result of the task for the technical computing client. An interface associated with a data repository holding the data allows programmatic control of the interface and provides a mechanism for informing interested entities of desired data events and for performing other data operations, for example, ensuring data integrity. As such, the present invention improves the ability of a scheduler associated with the distributed technical computing environment to manage and distribute tasks amongst multiple computing resources to perform technical computing of tasks. Further, the present invention is well suited for use with a number of different data repository types. Suitable data repository types include, but are not limited to a file system, a database, a remote storage array, memory, and the like.
  • In one illustrative embodiment of the present invention, a method of transferring data from a first computational engine to a second computational engine in a distributed environment having a plurality of computational engines is disclosed. Performance of the method instructs an interface associated with a data repository to transfer to the second of the computational engines data associated with a task distributed from the first of the computational engines. Upon processing of the instructions, the interface transfers the data from the interface to the second of the computational engines. Performance of the method communicates with the interface to establish a communications channel with the data repository.
  • Instructing the interface can invoke a method of the interface to perform a pre-defined operation. The method can take an action to notify an entity of receipt of the data by the interface. The method can take an action to maintain integrity of the data. The method can also take an action to update a data structure held by the data repository.
  • The method of taking an action to update a data structure can include the step of sending a query language command to a database management system managing the data structure. Additionally, the method of taking an action to update a data structure can include the step of calling a function associated with the interface.
  • The distributed environment can be a distributed technical computing environment.
  • In another illustrative embodiment of the present invention, a system for distributing data in a distributed environment is disclosed. The system includes amongst other items, a first computational engine, a data storage mechanism, and an interface. The first computational engine is configured to submit a task to distribute for processing in the computing environment. The task includes at least one action to perform by the computing environment. The data storage mechanism is configured to hold data associated with the task in communication with the computing environment. The interface is configured to manage transfer of the data associated with the task between the data storage mechanism and a second computational engine performing the processing in the computing environment.
  • The system can further include an automatic task distribution mechanism in communication with the first computational engine. The automatic task distribution mechanism receives the task submitted by the first computational engine and makes the task available to one or more other computational engines associated with the computing environment.
  • In one embodiment of the system, the interface can manage transfer of the data by notifying selected entities associated with the computing environment of an event relating to the data, the task, or both. The event can include one of a change in a data value, a change in a data type, a change in a dimension of the data, receipt of the data by the interface, transfer of the data from the interface to one of the computational engines, or other like events.
  • In another embodiment of the system, the interface can manage transfer of the data by providing data integrity. In other embodiments, the interface performs other management operations and functions to manage distribution of data in the computing environment. In one embodiment of the system, the computing environment is a distributed technical computing environment.
  • In one embodiment of the present invention, a computer readable medium holding computer executable instructions for performing a method of transferring data from a first computational engine to a second computational engine in a distributed environment having a plurality of computational engines is disclosed. Execution of the instructions instructs an interface associated with a data repository to transfer to the second of the computational engines data associated with a task distributed from the first of the computational engines. The interface in turn transfers the data from the interface to the second of the computational engines.
  • Additionally, execution of the instructions causes a computer to communicate with the interface to establish a communications channel with the data repository.
  • In one embodiment of the present invention, instructing the interface invokes a method of the interface to perform a pre-defined operation. In one instance, the method performs the step of taking an action to notify an entity of receipt of the data by the interface. In another instance, the method performs the step of taking an action to maintain integrity of the data. In still another instance, the method performs the step of taking an action to update a data structure held by the data repository.
  • The step of taking an action to update the data structure held by the data repository includes the step of sending a query language command to a database management system managing the data structure. In another instance, the step of taking an action to update the data structure held by the data repository includes the step of calling a function associated with the interface. The distributed environment can include a distributed technical computing environment.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The foregoing and other objects, aspects, features, and advantages of the invention will become more apparent and may be better understood by referring to the following description taken in conjunction with the accompanying drawings, in which:
  • FIG. 1A is a block diagram of a computing device for practicing an embodiment of the present invention;
  • FIG. 1B is a block diagram of a distributed computing system for practicing an illustrative embodiment of the present invention;
  • FIG. 2A is a block diagram of the components of an alternative embodiment of the present invention in a multi-tier networked computer system;
  • FIG. 2B is a block diagram of the components of an exemplary embodiment of the present invention in a distributed network computer system.
  • FIG. 3A is a block flow diagram illustrating steps taken to practice an exemplary embodiment of the present invention.
  • FIG. 3B is a continuation of the block flow diagram in FIG. 3A illustrating steps taken to practice an exemplary embodiment of the present invention.
  • FIG. 3C is a continuation of the block flow diagram in FIGS. 3A and 3B illustrating steps taken to practice an exemplary embodiment of the present invention.
  • FIG. 3D is a continuation of the block flow diagram in FIGS. 3A, 3B, and 3C illustrating steps taken to practice an exemplary embodiment of the present invention.
  • DETAILED DESCRIPTION
  • The illustrative embodiment of the present invention provides programmatic control of an interface connecting computational devices in a distributed technical computing environment to data held by a data repository associated with the distributed technical computing environment. Programmatic control of the interface allows the distributed technical computing environment to improve management of distributed tasks and associated data. The interface provides the distributed technical computing environment with the capability of, amongst other things, notifying entities of the distributed technical computing environment when a predefined data event occurs with data associated with a task in the distributed technical computing environment. Consequently, the interface improves the ability of a scheduler associated with the distributed technical computing environment to manage distribution of tasks and associated data amongst the computational devices of the distributed technical computing environment.
  • Moreover, the illustrative embodiment of the present invention is configurable to work with a variety of data repositories such as, a database, a storage array, and the like. It is not limited to a shared file system. Further, the programmatic control of an interface connecting computational devices in a distributed technical computing environment to data held by a data repository associated with the distributed technical computing environment provided by the illustrative embodiment of the present invention is well suited to work with a number of different schedulers. For example, schedulers such as LSF, PBS, HTC type schedulers, such as Condor, Microsoft Cluster Manager, and the like.
  • Before continuing with the discussion below, it is helpful to first define a few terms used herein.
  • The term “task” or “tasks” can be declared on a computational device in a distributed environment and defines a command, such as a MATLAB® command, to be executed, and the number of arguments and any input data to the arguments. A task can be directly distributed by the technical computing client to one or more technical computing workers. A technical computing worker performs technical computing on a task and may return a result to the technical computing client. Additionally, a task or a group of tasks, in a job, can be submitted to an automatic task distribution mechanism to distribute the one or more tasks automatically to one or more technical computing workers providing technical computing services. The technical computing client does not need to specify or have knowledge of the technical computing workers in order for the task to be distributed to and computed by a technical computing worker. Tasks can be organized into jobs.
  • The term “job” refers to a logical unit of activities, or tasks that are processed and/or managed collectively, such as a group of one or more tasks.
  • The term “automatic task distribution mechanism” or “scheduler” refers to a mechanism that can distribute tasks to technical computing workers that are anonymous to any technical computing clients. The technical computing workers perform the task and may return as a result the output data generated from the execution of the task. The result may be returned to a data repository, which, in turn, the interface of the present invention may provide the result to the technical computing client.
  • As used herein, the term “data repository” refers to a data structure suitable for holding data. Such suitable structures include, but are not limited to, a file system, a database and associated database management system (DBMS), memory, and the like.
  • As used herein, the term “pre-defined data event” or “data event” refers to an action, occurrence or non-occurrence to data of concern to a member or entity of the distributed technical computing environment and to an action, occurrence, or non-occurrence to a task or job. Such actions, occurrences, or non-occurrence can include, but are not limited to a read operation to read the data from the data repository, a write operation to write the data to the data repository, a save operation to save the data to the data repository, receipt of the data by an entity of the distributed technical computing environment, forwarding or transmission of the data by entity of the distributed technical computing environment, an operation performed on or with the data by an entity of the distributed technical computing environment, reporting on the progress of a task or job, and the like.
  • As used herein, the term “storage device” refers to a server or other electronic device capable of storing data. The storage device can store the data in any type of memory, on a magnetic disk or tape, on an optical type disk, or any combination thereof.
  • As used herein the term “computational engine” refers to a hardware device or multiple hardware devices capable of performing instructions in a defined manner. A computational engine or computational engines may be co-located on a single hardware device such as a microprocessor or controller having multiple cores or multiple threads or may be configured as multiple hardware devices interconnected by a serial or parallel bus interconnection structure.
  • As used herein the term “computational device” refers to a system on which a computational engine or computational engines reside. A computational device can include one or more computational engines. The illustrative embodiment of the present invention is described solely for illustrative purposes relative to a distributed computing with MATLAB® technical computing environment, which includes Distributed Computing Toolbox for MATLAB® and MATLAB® Distributed Computing Engine. Those skilled in the art will appreciate the Distributed Computing Toolbox for MATLAB® and a client and client machine can be used to define and submit a task, tasks, job or jobs for execution and the MATLAB® Distributed Computing Engine executes the task, tasks, job or jobs on a worker machine such as a technical computing worker. Although the illustrative embodiment of the present invention is described relative to a distributed computing with MATLAB® based application, one of ordinary skill in the art will appreciate that the present invention may be applied to distributing the processing of technical computing tasks with other technical computing environments, such as technical computing environments using software products of LabView®0 or MATRIXx from National Instruments, Inc., or Mathematica® from Wolfram Research, Inc., or MathCAD of Mathsoft Engineering & Education Inc., or Maple™ from Maplesoft, a division of Waterloo Maple Inc., or Octave.
  • FIG. 1A depicts a client machine suitable for practicing an illustrative embodiment of the present invention. The client machine 102 includes memory 106, on which software according to one embodiment of the present invention may be stored, a processor (CPU) 104 for executing software stored in the memory 106, and other programs for controlling system hardware. Although an illustrative embodiment of the present invention is discussed below in relation to, a distributed environment associated with a network this is not limiting of the present invention for the concepts and technical features discussed herein are equally applicable to distributed environments that may not be associated with a network. That is, the client machine 102 is configurable as a tightly coupled multiple processor system or the processor 104 can be a processor type having multiple cores. As such, in a tightly coupled environment, a task or tasks are distributed amongst the multiple processors or amongst the multiple cores using a bus or multiple bus structures. Accordingly, as discussed below a network 140 and a network communication channel 130 are analogous to multiple processors and a bus or other interconnection structure, such as conductive paths formed in or on a printed circuit board, that interconnect the multiple processors or interconnect multiple cores of a processor.
  • The memory 106 may comprise a computer system memory or random access memory such as DRAM, SRAM, EDO RAM, etc. The memory 106 may comprise other types of memory as well, or combinations thereof. A human user may interact with the client machine 102 through a visual display device 114 such as a computer monitor, which may render a graphical user interface (GUI). The client machine 102 may include other I/O devices such a keyboard 110 and a pointing device 112, for example a mouse, for receiving input from a user. Optionally, the keyboard 110 and the pointing device 112 may be connected to the visual display device 1 14. The client machine 102 may include other suitable conventional I/O peripherals. The client machine 102 may support any suitable installation medium 116, a CD-ROM, floppy disks, tape device, USB device, hard-drive or any other device suitable for installing software programs such as Distributed computing with MATLAB® 120. The client machine 102 may further comprise a storage device 108, such as a hard-drive or CD-ROM, for storing an operating system and other related software, and for storing application software programs such as Distributed computing with MATLAB® 120 of the present invention. Additionally, the client machine 102 may include a network interface 118 to interface to a Local Area Network (LAN), Wide Area Network (WAN) or the Internet through a variety of connections including, but not limited to, standard telephone lines, LAN or WAN links (e.g., 802.11, T1, T1, 56 kb, X.25), broadband connections (e.g., ISDN, Frame Relay, ATM), wireless connections, or some combination of any or all of the above. The network interface 118 may comprise a built-in network adapter, network interface card, PCMCIA network card, card bus network adapter, wireless network adapter, USB network adapter, modem or any other device suitable for interfacing the computing device 118 to any type of network capable of communication and performing the operations described herein. Moreover, the client machine 102 may be any computer system such as a workstation, desktop computer, server, laptop, handheld computer or other form of computing or telecommunications device that is capable of communication and that has sufficient processor power and memory capacity to perform the operations described herein.
  • FIG. 1B depicts an environment suitable for practicing an illustrative embodiment of the present invention, where the functionality of Distributed computing with MATLAB® 120 is distributed across multiple client machines (102′, 102″ and 102′″). In a broad overview, the system 100 depicts a multiple-tier or “n-tier” networked computer system for performing distributed software applications such as the distributed technical computing environment of the present invention. The system 100 includes a client 150 (e.g., a first client machine 102′) in communications through a network communication channel 130 with a server computer 160, also known as a server, (e.g., a second client machine 102″) over a network 140 and the server in communications through a network communications channel 130 with a workstation (e.g., a third client machine 102′″) over the network 140′. The client 150, the server 160, and the workstation 170 can be connected 130 to the networks 140 and/or 140′ through a variety of connections including, but not limited to, standard telephone lines, LAN or WAN links (e.g., 802.11, T1, T3, 56 kb, X.25), broadband connections (e.g., ISDN, Frame Relay, ATM), wireless connections, or some combination of any or all of the above. Each of the client 150, server 160 and workstation 170 can be any type of client machine (102′, 102″ and 102′″) as described above and respectively configured to be capable of computing and communicating the operations described herein.
  • In one embodiment, each of the client 150, server 160 and workstation 170 are configured to and capable of running at least a portion of the Distributed computing with MATLAB® 120. As a distributed software application, Distributed computing with MATLAB® has one or more software components that run on each of the client 150, server 160, and workstation 170, respectively, and work in communication and in collaboration with each other to meet the functionality of the overall application. For example, the client 150 may hold a graphical modeling environment that is capable of specifying block diagram models and technical computing tasks to analyze the model. The client 150 may have software components configured to and capable of submitting the tasks to the server 160(i.e., Distributed Computing Toolbox for MATLAB®). The server 160 may have software components configured to and capable of receiving the tasks submitted by the client 150 and for determining a workstation 170 to assign the task for technical computing. The workstation 170 may hold software components capable of providing a technical computing environment to perform technical computing of the tasks assigned from the server 160 and submitted by the client 150 (i.e., MATLAB® Distributed Computing Engine). In summary, the technical computing environment and software components of the Distributed computing with MATLAB® 120 application may be deployed across one or more different computing devices in various network topologies and configurations.
  • FIG. 2A depicts an illustrative embodiment of the Distributed computing with MATLAB® system suitable for use in connection with the present invention in a multi-tier distributed computer system. The technical computing client 250 can be a technical computing software application that provides a technical computing and graphical modeling environment for generating block diagram models and to define mathematical algorithms for simulating models. The technical computing client 250 can be a Distributed Computing Toolbox for MATLAB® client, which may include all or a portion of the functionality provided by the standalone desktop application of MATLAB®. Additionally, the technical computing client 250 can be any of the software programs available in the MATLAB® product family. Furthermore, the technical computing client 250 can be a custom software program or other software that accesses Distributed Computing Toolbox for MATLAB® functionality via an interface, such as an application programming interface, or by other means. One ordinarily skilled in the art will appreciate the various combinations of client types that may access the functionality of the system.
  • With an application programming interface and/or programming language of the technical computing client 250, functions can be defined representing a technical computing task to be executed by either a technical computing environment local to the client computer 150, or remote on the workstation 270. The local technical computing environment may be part of the technical computing client 250, or a technical computing worker running on the client computer 150. The programming language includes mechanisms, described below in more detail, to define a task to be distributed to a technical computing environment and to communicate the task to the technical computing worker 270 on the workstation 170, or alternatively, on the client 150. For example, the technical computing client 250 may declare a function to generate a random set of ten numbers and further delegate that the technical computing worker 270 running on the workstation 170 execute the function. Also, the application programming interface and programming language of the Distributed Computing Toolbox for MATLAB® running on technical computing client 250 includes mechanisms, described in more detail below, to receive a result from the execution of technical computing of the task from another technical computing environment. For example, the technical computing client 250 may declare a variable to hold a result returned from the technical computing worker 270 performing technical computing of the random generation function or the technical computing client 250 can identify one or more locations within a file system or database to hold the results returned from the technical computing worker 270.
  • The distributed functionality features of the programming languages of Distributed Computing Toolbox for MATLAB® on the technical computing client 250 allows the technical computing client 250 to use the computing resources that may be available from a technical computing worker 270 on the workstation 170 to perform technical computing of the task. This frees up the technical computing client 250 to perform other tasks, or the client computer 150 to execute other software applications.
  • The technical computing worker 270 of the system 200 can be a technical computing software application that provides a technical computing environment for performing technical computing of tasks, such as those tasks defined or created by the technical computing client 250. The technical computing worker 270 can be a MATLAB® Distributed Computing Engine application, module, service, software component, or a session, which includes support for technical computing of functions defined in the programming language of MATLAB®. A session is an instance of a running technical computing worker 270 by which a technical computing client can connect and access its functionality. The technical computing worker 270 can include all the functionality and software components of the technical computing client 250, or it can just include those software components it may need to perform technical computing of tasks it receives for execution. The technical computing worker 270 may be configured to and capable of running any of the modules, libraries, or software components of the MATLAB® product family. As such, the technical computing worker 270 may have all or a portion of the software components of MATLAB® installed on the workstation 170, or alternatively, accessible on another system in the network 140. The technical computing worker 270 has mechanisms, described in detail later, to receive a task distributed from the technical computing client 250. The technical computing worker 270 is capable of performing technical computing of the task as if the technical computing client 250 was performing the technical computing in its own technical computing environment. The technical computing worker 270 also has mechanisms, to return a result generated by the technical computing of the task to the technical computing client 250.
  • The technical computing worker 270 can be available on an as needed basis to the technical computing client 250. When not performing technical computing of tasks from the technical computing client 250, the workstation 170 of the technical computing worker 270 can be executing other software programs, or the technical computing worker 270 can perform technical computing of tasks from other technical computing clients. The multi-tier distributed system 205 includes a technical computing client 250 running on a client computer 150 in communications over a network communication channel 130 to a server 160 and to a storage device 180 on a network 140. The server 160 comprises an automatic task distribution mechanism 260. The storage device 180 includes an interface 190, and a file system 192, a database management system 194 and an associate database 196, or both. The interface 190 receives communications, such as data and instructions from the technical computing client 250, the automatic task distribution mechanism 260, and the technical computing worker 270, to connect each entity to the file system 192 and the database management system 194. The technical computing client 250, the automatic task distribution mechanism 260, and the technical computing worker 270 can communicate with the interface 190 on a dedicated communication line 132 or via network 140, or network 140′, over the network communication channel 130. The interface 190 can also send or forward communications, such as data and instructions to the technical computing client 250, the automatic task distribution mechanism 260, and the technical computing worker 270 to, amongst other things, connect each entity to the file system 192 and the database management system 194.
  • The automatic task distribution mechanism 260 communicates over a network communication channel 130 on the network 140 to the technical computing worker 270 on the workstation 170.
  • The automatic task distribution mechanism 260 comprises one or more software components to provide for the automatic distribution of tasks from the technical computing client 250 to the technical computing worker 270. The automatic task distribution mechanism 260 allows the technical computing client 250 to delegate the management of task distribution to the automatic task distribution mechanism 260. For example, with the programming language of Distributed Computing Toolbox for MATLAB®, a task can be defined and submitted to the automatic task distribution mechanism 260 without specifying which technical computing worker 270 is to perform the technical computing of the task. The technical computing client 250 does not need to know the specifics of the technical computing worker 270.
  • The technical computing client can define a function to submit the task to the automatic task distribution mechanism 260 and get a result of the task from the automatic task distribution mechanism 260. As such, the automatic task distribution mechanism provides a level of indirection between the technical computing client 250 and the technical computing worker 270.
  • The interface 190 includes one or more software components to provide connectivity between the technical computing client 250, the technical computing worker 270, the automatic task distribution 260, the file system 192, and the database management system 194. The interface 190 is able to monitor and manage the transfer of data associated with tasks between any or all of the technical computing client 250, the technical computing worker 270, and the storage device 180. The associated data can be a result or results from a task performed by the technical computing worker 270, or data needed by the technical computing worker 270 to complete a task requested by the technical computing client 250.
  • The interface 190 can operate and perform tasks in a platform-independent manner using the concept of a virtual machine to help avoid cross-platform compatibility issues should the client 150 be a first platform and the workstation 170 a second platform different from the first. For example, the client 150 can be a Windows-based platform, and the workstation 170 can be a UNIX-based platform. Those skilled in the art will appreciate that other suitable platforms exist, for example, DOS-based platform, Solaris-based platform, Mac-based platform, Linux-based platform, and the like.
  • The platform-independent nature of the interface 190 allows the technical computing client 250, the technical computing worker 270 and if desired the automatic task distribution mechanism 260 to access the file system 192 and the database 196 either directly or indirectly, for example, through the database management system 194 regardless of cross-platform compatibility issues that may exist between the various entities in the distributed technical computing environment 205. In one embodiment of the present invention, the interface 190 encodes access request statements in structured query language (SQL), and passes them to the database management system 190 to perform a desired method. Such methods can include, but are not limited to, creating tables, modifying tables, reading data, writing data, comparing data to earlier data versions, providing data integrity to ensure the entities of the distributed technical computing environment 205 perform tasks in a manner to avoid the use of or creation of corrupted data and other like methods. In another embodiment of the present invention, the interface 190 abstracts file system dependencies associated with file system 192 to provide data from the file system 192 in a format understandable by the technical computing client 250 or the technical computing worker 270. Further, the technical computing client 250 and the technical computing worker 270 are each able to interact with the file system 192 and the database 196 with API calls to the interface 190.
  • The interface 190 can include a registry 191 to allow entities of the distributed technical computing environment 205 to register with the interface 190 to receive notice of an occurrence of one or more pre-defined data events. Such pre-defined data events include, but are not limited to, receipt of data at the interface 190 from the technical computing client 250; receipt of data at interface 190 from the technical computing worker 270; transmission of data from the interface 190 to the technical computing worker 270; transmission of data from the interface 190 to the technical computing client 250; notice that one or more values in a data structure have changed; notice that the interface 190 did not receive data from the technical computing client 250; notice that the interface 190 did not receive data from the technical computing worker 270; notice that the interface 190 received incomprehensible data from the technical computing worker 270, for example, data of a wrong data type, format, length, and the like; notice that the interface 190 received incomprehensible data from the technical computing client 250; notice that the file system 192 or the database 196 is nearing storage capacity, and the like.
  • Entities of the distributed technical computing environment 205 can include, but are not limited to, the technical computing client 250, the automatic task distribution mechanism 260, and the technical computing worker 270. Further, entities can be software based or hardware based. The interface 190 eases the distributed programming and integration burden on the distributed technical computing environment 205. The interface 190 allows the automatic task distribution mechanism 260 to improve its ability of monitoring, managing, and distributing tasks among the computational devices of the distributed technical computing environment 205. Typically the tasks distributed by the automatic task distribution mechanism 260 identify a location in either the file system 192 or the database 196 of the data needed, to perform the task, or the location to place a result of the task. The automatic task distribution mechanism 260 manages distribution of tasks, but does not manage and monitor the distribution of data associated with the tasks. As such, with the addition of the interface 190, the automatic task distribution mechanism 260 can register with the registry 191 to help determine when tasks are complete and help determine which tasks are still being performed in an effort to improve load balancing of tasks among the various computational devices performing in the distributed technical computing environment 205.
  • Further, the interface 190 in combination with the automatic task distribution mechanism 260 eases the distributed programming and integration burden on the technical computing client 250. The technical computing client 250 does not need to have prior knowledge of the availability of the technical computing worker 270. For multiple task submissions from the technical computing client 250, the automatic task distribution mechanism 260 can manage and handle the delegations of the tasks to the same technical computing worker 270, or to other technical computing workers, and the storage device 180 can hold the results of the tasks on behalf of the technical computing client 250 for retrieval after the completion of technical computing of all the distributed tasks.
  • Referring now to FIG. 2B, an exemplary embodiment of the present invention is shown with multiple technical computing workers 270A-270N hosted on a plurality of workstations 170A-170N. The technical computing client 250 may be in communication through the network communication channel 130 on the network 140 with one, some, or all of the technical computing workers 270A-270N. In a similar manner, the interface 190 and the automatic task distribution mechanism 260 may be in communication through the network communication channel 130 on the network 140 with one, some, or all of the technical computing workers 270A-270N. As such, the technical computing client 250, the interface 190, and the automatic task distribution mechanism 260 can distribute tasks and associated data to multiple technical computing workers 270A-270N to scale the distributed system and decrease computation time of tasks. As also shown in FIG. 2C, the technical computing workers 270A-270B can be hosted on the same workstation 170A, or a single technical computing worker 270C can have a dedicated workstation 170B. Alternatively, one or more of the technical computing workers 270A-270N can be hosted on either the client 150 or the server 160.
  • The client machines (102, 102′, 102″, 102″) depicted in FIGS. 1A and 1B can be running any operating system such as any of the versions of the Microsofto Windows operating systems, the different releases of the Solaris, Unix and Linux operating systems, any version of the Mac OSO for Macintosh computers, any embedded operating system, any real-time operating system, any open source operating system, any proprietary operating system, any operating systems for mobile computing devices, or any other operating system capable of running on the computing device and performing the operations described herein. Furthermore, the software components of Distributed Computing Toolbox for MATLAB® and MATLAB® Distributed Computing Engine can be capable of and configured to operate on the operating system that may be running on any of the client or worker machines, respectively (e.g., 102, 102′, 102″, 102′″).
  • Additionally, each of the client 150, the server 160, and the workstation 170 can be running the same or different operating systems. For example, the client 150 can be running Microsoft® Windows, the server 160 can be running a version of UNIX, and the workstation a version of Linux. Alternatively, each of the client 150, the server 160, and the workstation 170 can be running Microsoft® Windows. Additionally, the software components of Distributed Computing Toolbox for MATLAB® and MATLAB® Distributed Computing Engine can be capable of and configured to operate on and take advantage of different processors of any of the client or worker machines, respectively (e.g., 102, 102′, 102″, 102′″). For example, Distributed Computing Toolbox for MATLAB® or MATLAB® Distributed Computing Engine can run on a 32 bit processor of one computing device 102 and a 64 bit processor of another computing device 102′. In a distributed system, such as the system depicted in FIG. 1B, Distributed Computing Toolbox for MATLAB® and MATLAB® Distributed Computing Engine can operate on client or worker machines, respectively (102, 102′, 102″, 102″) that can be running on different processor architectures in addition to different operating systems. One ordinarily skilled in the art will recognize the various combinations of operating systems and processors that can be running on any of the client or worker machines (102, 102′, 102″, and 102′″).
  • As such, the interface 190 is configurable as an object-oriented interface that can provide or be programmed to define a set of object-oriented classes that allow a programmer to configure the interface to translate the request of the technical computing client 250 and the technical computing worker 270 into commands understandable by the database management system 194 or the file system 192. Alternatively, the set of object-oriented classes provided by the interface 190 or defined by a programmer allow the programmer to generate source code executable by an interpreter.
  • Although the present invention is discussed above in terms of distributing data and software components of Distributed Computing Toolbox for MATLAB® and MATLAB® Distributed Computing Engine across the computing devices of a client 150, server 160 and workstation 170, any other system and/or deployment architecture that combines and/or distributes one or more of the technical computing client 250, automatic task distribution mechanism 260 and technical computing worker 270 across any other computing devices and operating systems available in the network 140 may be used. Alternatively, all the software components of Distributed Computing Toolbox for MATLAB® can run on a single client machine 102, such as the client 150, server 160, or the workstation 170.
  • Those skilled in the art will appreciate the distribution of tasks and associated data among the computing devices forming the distributed computing environment can occur in a number of suitable manners. One suitable methodology is referred to as a direct distribution mode, which is intended for those users, who desire a high level of control over which technical computing worker 270 executes a particular task. Another suitable manner to distribute tasks and associated data among the computational devices of the distributed technical computing environment is often referred to as an automatic distribution mode. The automatic distribution mode provides a configuration and methodology suitable for use by a user that does not want to control which computational device of the distributed technical computing environment executes a particular task. Another suitable manner for distributing data and associated tasks is known as a batch-mode or automated distribution. The batch-mode or automated distribution allows the automatic distribution mechanism 260 to be configured to allow a user to specify a group of related tasks as a job, and to provide the batch of tasks, or the job, to the automatic task distribution mechanism 260. Those skilled in the art will also appreciate that whichever task distribution mode is selected in the distributed technical computing environment, the interface 190 connects the technical computing client 250, and the technical computing worker 270 to the file system 192 and the database 196 to manage distribution of data associated with the distributed tasks.
  • Referring now to FIGS. 3A-3D, an illustrative flow chart depicts steps taken by one embodiment of the present invention to distribute a task from a technical computing client 250 to a technical computing worker 270 in a distributed technical computing environment. A technical computing worker 270 registers to receive notification of one or more tasks (step 300) becoming available, or appearing, in the automatic task distribution mechanism 260. In turn, the automatic task distribution mechanism 260 registers the technical computing worker as an available worker (step 302). The technical computing client 250 defines a task comprising an operation for technical computing (step 304). The technical computing client 250 then submits the task to the automatic task distribution mechanism 260 (step 306). The automatic task distribution mechanism 260 receives the task and makes the task available for distribution to a technical computing worker 270 (step 308).
  • The technical computing client 250 registers with the registry 191 of the interface 190 for notification of desired data events (step 310). Such data events can include, but are not limited to, a change in a value of data held at a specified location in the file system 192 or the database 196, receipt of a request from a technical computing worker 270 to retrieve data, receipt of a request from a technical computing worker 270 to store data, and the like, in this manner, the technical computing client 250 is better able to track, and if desired, predict the progress and stage of a job or task. Other data events, which the technical computing client 250 can register for include, but are not limited to, notification of an occurrence of a time out in communications between the interface 190 and a technical computing worker 270; the receipt by interface 190 of corrupted data from the technical computing worker 270; notification from the interface 190 that certain data is inaccessible because another technical computing worker 270 or another technical computing client 250 is using or is intending to use the data, and the like. Other data events can indicate the interface 190 is in receipt of a request from a technical computing client 250 to register with the registry 191 for notification of certain data events. In turn, the interface 190 registers the technical computing client 250 with the registry 191 (step 312). Those skilled in the art will appreciate that the technical computing client 250 can register with the interface 190 before a task is defined, or at any time thereafter. Further, those skilled in the art will appreciate that the registry 191 can be physically or logically located outside the interface 190.
  • Likewise, the automatic task distribution mechanism 260 can register with the interface 190 for notification of certain data events (step 314). The data events of concern to the automatic task distribution mechanism 260 include but are not limited to those data events discussed above in relation to step 310. The interface 190 in turn registers the task distribution mechanism 260 for notification of the certain pre-defined data events (step 316). Those skilled in the art will appreciate the automatic task distribution mechanism 260 can register with the interface 190 at any time after initialization of the distributed technical computing environment. Additionally, those skilled in the art will appreciate the automatic task distribution mechanism 260 to register with the interface 190 on a per-task or per-job basis, and can register for a one-time occurrence of a task or a job or register in a manner that carries over to each current task or current job associated with the data of concern.
  • The automatic task distribution mechanism 260 provides the task to the technical computing worker 270 (step 318). In turn, the technical computing worker 270 receives the task from the automatic task distribution mechanism 260 (step 320). The technical computing worker 270 examines or interrogates the received task to determine what, if any, data is required for the technical computing worker 270 to perform the received task. Upon determining the data necessary to perform the received task, the technical computing worker 270 requests the interface 190 to provide the necessary data (step 322). The interface 190 upon receipt of the request from the technical computing worker 270 (step 324) retrieves the requested data from either the file system 192 or the database 196 by invoking a method or calling a function identified in the request. The method or function can encode access request statements identified by the request into a format understandable by the file system 192 or the database management system 194 (step 326). Once the requested data is retrieved, the interface 190 forwards the requested data to the technical computing worker 270 (step 328). The technical computing worker 270 in turn receives the requested data (step 330). At this point, the interface 190 can take an action to notify those entities registered with the registry 191 to receive notification of a data request from the technical computing worker 270, or to receive notification of the forwarding of the requested data to the technical computing worker 270 and other like data events associated with receipt of a request for data from a technical computing worker, taking steps to retrieve the requested data, and forwarding the requested data to the requestor (step 332). The registered entities include any entity of the distributed technical computing environment, including, but not limited to, software components, hardware components, the technical computing client 250, the automatic task distribution mechanism 260, the technical computing worker 270, and the like.
  • The technical computing worker 270 can request the interface 190 to retrieve or perform another operation on the desired data in a number of suitable manners. One suitable example for the technical computing worker 270 to request the interface 190 to retrieve or perform another operation on the desired data is through a remote method invocation (RMI) that include one or more objects past along with the request that include information for retrieving the desired data. The information included in the one or more objects can include a method with statements to send or construct structured query language (SQL) statements to the database management system 194. Another suitable method for the technical computing worker 270 to request the interface 190 to retrieve the desired data is through a remote procedure called (RPC). Another suitable method for the technical computing worker 270 to request the interface 190 to retrieve or perform another operation with the desired data is via a function call to a function associated with the interface 190. Those skilled in the art will appreciate that other entities of the distributed technical computing environment, for example the technical computing client 150 and the automatic task distribution mechanism 260 can communicate with the interface 190 in any of the just described manners.
  • The technical computing worker 270 performs the requested technical computing on the function or command as defined by the task (step 334). In performing the technical computing on the task, an associated result is likely generated (step 336). Those skilled in the art will appreciate that in some instances, either no result is generated or the result is not required to be returned to the technical computing client 250.
  • After generating the result from computing the task, the technical computing worker 270 forwards data associated with the task or the result of the task or both to the interface 190 with a request to store the data or perform some other operation on the data, in either the file system 192 or the database 196 (step 338). The interface 190 receives the data and the request from the technical computing worker 270 (step 340). If configured to do so, the interface 190 performs data validation on the received data to at least validate the data has a proper format and is comprehensible (step 348). That is, the interface 190 can be configured to interrogate the received data to determine which values changed since forwarding the data to the technical computing worker 270, and to further determine if the data received from the technical computing worker 270 conforms to the requirement specified for that data. For example, the interface 190 can determine if the data is the appropriate data type, is of the appropriate length, and the like. If the interface 190 determines the data is valid (step 350), the interface 190 stores the data in either the file system 192 or the database 196 at the appropriate storage location (step 352). If the interface 190 determines the data is not valid, for example, the data is considered corrupted because it does not conform to a pre-defined format for the data (step 350), the interface 190 can notify entities registered with the registry 191 to receive notification if such a data event occurs (step 354). Those skilled in the art will appreciate that he interface 190 can perform other data validation operations such as verification of a checksum or a CRC, and other like data validation operations.
  • After generating the result from computing the task, the technical computing worker 270 provides the result to the automatic task distribution mechanism 260 (step 342). After obtaining the result from the technical computing worker 270, the automatic task distribution mechanism 260 can hold the result until the interface 190 validates the data (step 344). As such, the automatic task distribution mechanism 260 is configurable to hold the result until the interface 190 validates the data. If the automatic task distribution mechanism is configured in this manner, it holds the result until notified by the interface 190 the data is valid (step 346). Otherwise, the automatic task distribution mechanism 260 provides the result to the technical computing client 250 (step 360). The technical computing client 250 receives the result provided by the automatic task distribution mechanism 260 (step 362).
  • The technical computing client 250 requests the interface 190 to retrieve the data associated with the results from either the file system 192 or the database 196 (step 364). The interface 190 receives the request (step 366), and in response retrieves the requested data (step 368). The interface 190 after retrieving the requested data forwards the data to the technical computing client 250 (step 370), and the technical computing client 250, in turn, receives the requested data (step 372).
  • Many alterations and modifications may be made by those having ordinary skill in the art without departing from the spirit and scope of the invention. For example, the present invention is well suited for use with any scheduler or job manager including, but not limited to schedulers such as, LSF, PBS, HTC type schedulers, such as Condor, Microsoft Cluster Manager, and the like Therefore, it must be expressly understood that the illustrated embodiments have been shown only for the purposes of example and should not be taken as limiting the invention, which is defined by the following claims. These claims are to be read as including what they set forth literally and also those equivalent elements which are insubstantially different, even though not identical in other respects to what is shown and described in the above illustrations.

Claims (62)

  1. 1. In a distributed environment having a plurality of computational engines, a method of transferring data from a first of the computational engines to a second of the computational engines, the method comprising the steps of:
    instructing an interface associated with a data repository to transfer to the second of the computational engines data associated with a task distributed from the first of the computational engines; and
    transferring the data from the interface to the second of the computational engines,
    whereby the interface in response to the instructions sends a request to the data repository to retrieve the data associated with the task and when the data repository returns the requested data the interface transfers the data in a format understandable by the second of the computational engines.
  2. 2. The method of claim 1, further comprising the step of communicating with the interface to establish a communications channel with the data repository.
  3. 3. The method of claim 1, wherein the step of instructing invokes a method of the interface to perform a pre-defined operation.
  4. 4. The method of claim 3, wherein the method performs the step of taking an action to notify an entity of receipt of the data by the interface.
  5. 5. The method of claim 3, wherein the method performs the step of taking an action to maintain integrity of the data.
  6. 6. The method of claim 3, wherein the method performs the step of taking an action to update a data structure held by the data repository.
  7. 7. The method of claim 6, wherein the step of taking an action includes the step of sending a query language command to a database management system managing the data structure.
  8. 8. The method of claim 6, wherein the step of taking an action includes the step of calling a function associated with the interface.
  9. 9. The method of claim 1, wherein the distributed environment comprises a distributed technical computing environment
  10. 10. A system for distributing data in a computing environment, the system comprising:
    a first computational engine submitting a task to distribute for processing in a computing environment, the task comprising at least one action to perform by the computing environment;
    a data storage mechanism for holding data associated with the task in communication with the computing environment; and
    An interface configured to manage transfer of the data associated with the task between the data storage mechanism and a second computational performing the processing in the distributed environment.
  11. 11. The system of claim 10, further comprising an automatic task distribution mechanism in communication with the technical computing client, the automatic task distribution mechanism receiving the task submitted by the first computational engine and making the task available to one or more computational engines associated with the distributed technical computing environment.
  12. 12. The system of claim 10, wherein the interface manages transfer of the data by notifying selected entities associated with the distributed environment of an event relating to the task.
  13. 13. The system of claim 12, wherein the event comprises one of a change in a data value, a change in a data type, a change in a dimension of the data, receipt of the data by the interface, or transfer of the data from the interface to one of the computational engines.
  14. 14. The system of claim 13, wherein the interface manages transfer of the data by providing data integrity.
  15. 15. The system of claim 1 1, wherein the computing environment comprises a distributed technical computing environment.
  16. 16. A computer readable medium holding computer executable instructions for performing a method of transferring data from a first computational engine to a second computational engine in a distributed environment having a plurality of computational engines, the method comprising the steps of:
    instructing an interface associated with a data repository to transfer to the second of the computational devices data associated with a task distributed from the first of the computational devices; and
    transferring the data from the interface to the second of the computational devices
    whereby the interface in response to the instructions sends a request to the data repository to retrieve the data associated with the task and when the data repository returns the requested data the interface transfers the data in a format understandable by the second of the computational devices.
  17. 17. The medium of claim 15, further comprising the step of communicating with the interface to establish a communications channel with the data repository.
  18. 18. The medium of claim 15, wherein the step of instructing invokes a method of the interface to perform a pre-defined operation.
  19. 19. The medium of claim 15, wherein the method performs the step of taking an action to notify an entity of receipt of the data by the interface.
  20. 20. The medium of claim 15, wherein the method performs the step of taking an action to maintain integrity of the data.
  21. 21. The medium of claim 15, wherein the method performs the step of taking an action to update a data structure held by the data repository.
  22. 22. The medium of claim 21, wherein the step of taking an action includes the step of sending a query language command to a database management system managing the data structure.
  23. 23. The medium of claim 21, wherein the step of taking an action includes the step of calling a function associated with the interface.
  24. 24. The medium of claim 11, wherein the distributed environment comprises a distributed technical computing environment.
  25. 25. In a distributed environment having a plurality of computational engines, a method of managing data transferred between a data repository associated with the distributed environment and one of the plurality of computational engines, the method comprising the steps of:
    registering with a registry associated with the data repository to receive notification when a predefined action occurs with a task distributed from a first of the computational engines to a second of the computational engines; and
    receiving notification when the predefined action occurs.
  26. 26. The method of claim 25, wherein a scheduler of the distributed environment registers with the registry to receive the notification.
  27. 27. The method of claim 25, wherein an interface associated with the data repository constructs the notification.
  28. 28. The method of claim 25 further comprising the step of, controlling the transfer of data between the data repository associated with the distributed environment and one of the plurality of computational engines based on content of the notification received.
  29. 29. The method of claim 25, wherein the predefined action relates to data associated with the task.
  30. 30. The method of claim 26, wherein the distributed environment comprises a distributed technical computing environment.
  31. 31. A device readable medium holding device readable instructions for performing a method in a distributed environment having a plurality of computational engines, the method manages data transferred between a data repository associated with the distributed environment and one of the plurality of computational engines, the method comprising the steps of:
    registering with a registry associated with the data repository to receive notification when a predefined action occurs with a task distributed from a first of the computational engines to a second of the computational engines; and
    receiving notification when the predefined action occurs.
  32. 32. The medium of claim 31, wherein a scheduler of the distributed technical computing environment registers with the registry to receive the notification.
  33. 33. The medium of claim 31, wherein an interface associated with the data repository constructs the notification.
  34. 34. The medium of claim 31 further comprising the step of, controlling the transfer of data between the data repository associated with the distributed environment and one of the plurality of computational engines based on content of the notification received.
  35. 35. The medium of claim 31, wherein the predefined action relates to data associated with the task.
  36. 36. The medium of claim 31, wherein the distributed environment comprises a distributed technical computing environment.
  37. 37. A system for managing data in a distributed environment, the system comprising:
    a first computational engine submitting a task to distribute for processing in a computing environment, the task comprising at least one action to perform by the computing environment;
    a data storage mechanism for holding data associated with the task in communication with the computing environment; and
    an interface configured to notify an entity of the computing environment when an event occurs with the task,
    wherein notification of the event from the interface provides the entity with an indication of a state of the task or a state of data associated with the task.
  38. 38. The system of claim 37, further comprising an automatic task distribution mechanism in communication with the computational engine, the automatic task distribution mechanism receiving the task submitted by the computational engine , and making the task available to one or more other computational engines associated with the computing environment.
  39. 39. The system of claim 38, wherein the event comprises one of a change in a data value, a change in a data type, a change in a dimension of the data, receipt of the data by the interface, transfer of the data from the interface to one of the computational engines, or a state of the processing of the task.
  40. 40. The system of claim 37, wherein the distributed environment comprises a distributed technical computing environment.
  41. 41. In a distributed environment having a plurality of computational engines, a method of managing distribution of tasks amongst the plurality of computational engines in the distributed environment, the method comprising the steps of:
    receiving a task from a first of the computational engines, forwarding the task to a second of the computational engines,
    receiving notification from an interface to a data repository for holding data associated with the task a predefined event occurred that concerns the task, and
    taking an action to manage the distribution of tasks amongst the plurality of computational engines based on the content of the notification.
  42. 42. The method of claim 41, wherein the step of taking an action comprises the step of forwarding the task to the second of the computational engines a second time.
  43. 43. The method of claim 41, wherein the step of taking an action comprises the step of forwarding the task to a third of the computation engines.
  44. 44. The method of claim 41, wherein the step of taking an action comprises the step of sending a result of the task to the first of the computational engines.
  45. 45. The method of claim 41, wherein the step of taking an action comprises the step of forwarding other tasks to a third of the computational engines.
  46. 46. The method of claim 41, wherein the step of taking an action comprises the step of forwarding other tasks to other computational engines from the plurality of the computational engines.
  47. 47. The method of claim 41, wherein the distributed environment comprises a distributed technical computing environment.
  48. 48. A device readable medium holding device executable instructions for performing a method in a distributed environment having a plurality of computational engines, the method for managing distribution of tasks amongst the plurality of computational engines in the distributed environment, the method comprising the steps of:
    receiving a task from a first of the computational engines, forwarding the task to a second of the computational engines,
    receiving notification from an interface to a data repository for holding data associated with the task a predefined event occurred that concerns the task, and
    taking an action to manage the distribution of tasks amongst the plurality of computational devices based on the content of the notification.
  49. 49. The medium of claim 48, wherein the step of taking an action comprises the step of forwarding the task to the second of the computational engines a second time.
  50. 50. The medium of claim 48, wherein the step of taking an action comprises the step of forwarding the task to a third of the computation engines.
  51. 51. The medium of claim 48, wherein the step of taking an action comprises the step of sending a result of the task to the first of the computational engines.
  52. 52. The medium of claim 48, wherein the step of taking an action comprises the step of forwarding other tasks to a third of the computational engines.
  53. 53. The medium of claim 48, wherein the step of taking an action comprises the step of forwarding other tasks to other computational devices from the plurality of the computational engines.
  54. 54. The method of claim 48, wherein the distributed environment comprises a distributed technical computing environment.
  55. 55. A system for managing distribution of tasks in a distributed environment, the system comprising:
    a first computational engine submitting a task to distribute for processing in a computing environment, the task comprising at least one action to perform by the computing environment;
    a data storage mechanism for holding data associated with the task in communication with the computing environment;
    an automatic task distribution mechanism in communication with the first computational engine, the automatic task distribution mechanism receiving the task submitted by the technical computing client, and making the task available to one or more other computational engines associated with the computing environment; and
    an interface configured to notify an automatic task distribution mechanism of the distributed environment when an event occurs with the task;
    wherein the automatic task distribution mechanism in response to content contained in the notice form the interface takes an action to manage distribution of tasks in the computing environment.
  56. 56. The system of claim 55, wherein the event comprises one of a change in a data value, a change in a data type, a change in a dimension of the data, receipt of the data by the interface, transfer of the data from the interface to one of the computational engines or a state of the processing of the task.
  57. 57. The system of claim 55, wherein the interface takes an action to forward the task to the second of the computational engines a second time.
  58. 58. The system of claim 55, wherein the interface takes an action to forward the task to a third of the computation engines.
  59. 59. The system of claim 55, wherein the interface takes an action to send a result of the task to the first of the computational engines.
  60. 60. The system of claim 55, wherein the interface takes an action to forward other tasks to a third of the computational engines.
  61. 61. The system of claim 55, wherein the interface takes an action to forward other tasks to other computational engines from the plurality of the computational engines.
  62. 62. The method of claim 55, wherein the distributed environment comprises a distributed technical computing environment.
US11195927 2005-08-02 2005-08-02 Methods and system for distributing data to technical computing workers Abandoned US20070033247A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11195927 US20070033247A1 (en) 2005-08-02 2005-08-02 Methods and system for distributing data to technical computing workers

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US11195927 US20070033247A1 (en) 2005-08-02 2005-08-02 Methods and system for distributing data to technical computing workers
EP20060789281 EP1910924A2 (en) 2005-08-02 2006-08-01 Methods and system for distributing data to technical computing workers
PCT/US2006/030225 WO2007016657A3 (en) 2005-08-02 2006-08-01 Methods and system for distributing data to technical computing workers
US11891462 US8032582B2 (en) 2005-08-02 2007-08-10 Methods and system for distributing data to technical computing workers
US12481301 US8688765B2 (en) 2005-08-02 2009-06-09 Methods and system for distributing data to technical computing workers
US12481322 US9582330B2 (en) 2005-08-02 2009-06-09 Methods and system for distributing data to technical computing workers

Related Child Applications (3)

Application Number Title Priority Date Filing Date
US11891462 Continuation US8032582B2 (en) 2005-08-02 2007-08-10 Methods and system for distributing data to technical computing workers
US12481301 Division US8688765B2 (en) 2005-08-02 2009-06-09 Methods and system for distributing data to technical computing workers
US12481322 Division US9582330B2 (en) 2005-08-02 2009-06-09 Methods and system for distributing data to technical computing workers

Publications (1)

Publication Number Publication Date
US20070033247A1 true true US20070033247A1 (en) 2007-02-08

Family

ID=37402696

Family Applications (4)

Application Number Title Priority Date Filing Date
US11195927 Abandoned US20070033247A1 (en) 2005-08-02 2005-08-02 Methods and system for distributing data to technical computing workers
US11891462 Active 2026-04-19 US8032582B2 (en) 2005-08-02 2007-08-10 Methods and system for distributing data to technical computing workers
US12481301 Active 2026-11-01 US8688765B2 (en) 2005-08-02 2009-06-09 Methods and system for distributing data to technical computing workers
US12481322 Active 2026-11-05 US9582330B2 (en) 2005-08-02 2009-06-09 Methods and system for distributing data to technical computing workers

Family Applications After (3)

Application Number Title Priority Date Filing Date
US11891462 Active 2026-04-19 US8032582B2 (en) 2005-08-02 2007-08-10 Methods and system for distributing data to technical computing workers
US12481301 Active 2026-11-01 US8688765B2 (en) 2005-08-02 2009-06-09 Methods and system for distributing data to technical computing workers
US12481322 Active 2026-11-05 US9582330B2 (en) 2005-08-02 2009-06-09 Methods and system for distributing data to technical computing workers

Country Status (3)

Country Link
US (4) US20070033247A1 (en)
EP (1) EP1910924A2 (en)
WO (1) WO2007016657A3 (en)

Cited By (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070050484A1 (en) * 2005-08-26 2007-03-01 Roland Oertig Enterprise application server system and method
US20070101019A1 (en) * 2005-11-03 2007-05-03 Cromer Daryl C Apparatus, system, and method for managing response latency
US20080154916A1 (en) * 2006-11-10 2008-06-26 Bally Gaming, Inc. Package manager service in gaming system
US20080153600A1 (en) * 2006-11-10 2008-06-26 Bally Gaming, Inc. Gaming system configuration change reporting
US20080162729A1 (en) * 2006-11-10 2008-07-03 Bally Gaming, Inc. Gaming system download network architecture
US20080200255A1 (en) * 2006-11-10 2008-08-21 Bally Gaming, Inc. Networked gaming environment employing different classes of gaming machines
US20090118001A1 (en) * 2007-11-02 2009-05-07 Bally Gaming, Inc. Game related systems, methods, and articles that combine virtual and physical elements
US20090131163A1 (en) * 2006-11-10 2009-05-21 Bally Gaming, Inc. Assignment template and assignment bundle in a gaming configuration and download system
US20090131144A1 (en) * 2007-11-12 2009-05-21 Bally Gaming, Inc. Meta-option
US20090183243A1 (en) * 2007-11-12 2009-07-16 Bally Gaming, Inc. User authorization system and methods
US20090275402A1 (en) * 2008-04-30 2009-11-05 Bally Gaming, Inc. Information distribution in gaming networks
US20090275401A1 (en) * 2008-04-30 2009-11-05 Bally Gaming, Inc. Method, system, apparatus, and article of manufacture for profile-driven configuration for electronic gaming machines (egms)
US20090276715A1 (en) * 2008-04-30 2009-11-05 Bally Gaming, Inc. User interface for managing network download and configuration tasks
US20090275395A1 (en) * 2008-04-30 2009-11-05 Bally Gaming, Inc. Systems and methods for out-of-band gaming machine management
US20090275374A1 (en) * 2008-04-30 2009-11-05 Bally Gaming, Inc. Tournament play in a gaming property
US20090298583A1 (en) * 2008-05-30 2009-12-03 Bally Gaming, Inc. Web pages for gaming devices
US20100016068A1 (en) * 2008-05-24 2010-01-21 Bally Gaming, Inc. Networked gaming system with enterprise accounting methods and apparatus
US20100093441A1 (en) * 2008-07-11 2010-04-15 Bally Gaming, Inc. Integration gateway
US20100125851A1 (en) * 2008-11-14 2010-05-20 Bally Gaming, Inc. Apparatus, method, and system to provide a multi-core processor for an electronic gaming machine (egm)
US20100332593A1 (en) * 2009-06-29 2010-12-30 Igor Barash Systems and methods for operating an anti-malware network on a cloud computing platform
US8052519B2 (en) 2006-06-08 2011-11-08 Bally Gaming, Inc. Systems, methods and articles to facilitate lockout of selectable odds/advantage in playing card games
CN102467701A (en) * 2010-11-12 2012-05-23 甲骨文国际公司 Event-based orchestration in distributed order orchestration system
US8266213B2 (en) 2008-11-14 2012-09-11 Bally Gaming, Inc. Apparatus, method, and system to provide a multiple processor architecture for server-based gaming
US20130060832A1 (en) * 2007-11-22 2013-03-07 Telefonaktiebolaget L M Ericsson (Publ) Method and device for agile computing
US8423790B2 (en) 2008-11-18 2013-04-16 Bally Gaming, Inc. Module validation
US8631501B2 (en) 2006-11-10 2014-01-14 Bally Gaming, Inc. Reporting function in gaming system environment
US8667457B2 (en) 2006-11-13 2014-03-04 Bally Gaming, Inc. System and method for validating download or configuration assignment for an EGM or EGM collection
US8721431B2 (en) 2008-04-30 2014-05-13 Bally Gaming, Inc. Systems, methods, and devices for providing instances of a secondary game
US8870647B2 (en) 2006-04-12 2014-10-28 Bally Gaming, Inc. Wireless gaming environment
US9058716B2 (en) 2011-06-06 2015-06-16 Bally Gaming, Inc. Remote game play in a wireless gaming environment
US9082258B2 (en) 2006-11-13 2015-07-14 Bally Gaming, Inc. Method and system for providing download and configuration job progress tracking and display via host user interface
US9101820B2 (en) 2006-11-09 2015-08-11 Bally Gaming, Inc. System, method and apparatus to produce decks for and operate games played with playing cards
US20150237137A1 (en) * 2014-02-19 2015-08-20 Snowflake Computing Inc. Resource management systems and methods
US9120007B2 (en) 2012-01-18 2015-09-01 Bally Gaming, Inc. Network gaming architecture, gaming systems, and related methods
US20160036886A1 (en) * 2014-07-31 2016-02-04 Istreamplanet Co. Method and system for coordinating stream processing at a video streaming platform
US9466172B2 (en) 2006-11-13 2016-10-11 Bally Gaming, Inc. Download and configuration management engine for gaming system
US9686576B2 (en) 2015-05-08 2017-06-20 Istreamplanet Co. Coordination of video stream timing in cloud-based video streaming system
US9792770B2 (en) 2012-01-18 2017-10-17 Bally Gaming, Inc. Play for fun network gaming system and method
US9912707B2 (en) 2014-07-31 2018-03-06 Istreamplanet Co. Method and system for ensuring reliability of unicast video streaming at a video streaming platform

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120254965A1 (en) * 2011-04-04 2012-10-04 Lansing Arthur Parker Method and system for secured distributed computing using devices
US8887128B2 (en) * 2012-12-17 2014-11-11 Sas Institute Inc. Computer-implemented systems and methods for automated generation of a customized software product
US10038771B2 (en) * 2014-04-30 2018-07-31 Entit Software Llc Extending features of one device to another
US9952908B2 (en) * 2014-09-11 2018-04-24 Cisco Technology, Inc. Crowd sourced cloud computing

Citations (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4980857A (en) * 1987-04-15 1990-12-25 Allied-Signal Inc. Operations controller for a fault tolerant multiple node processing system
US6282697B1 (en) * 1998-09-18 2001-08-28 Wylci Fables Computer processing and programming method using autonomous data handlers
US6330572B1 (en) * 1998-07-15 2001-12-11 Imation Corp. Hierarchical data storage management
US20020019844A1 (en) * 2000-07-06 2002-02-14 Kurowski Scott J. Method and system for network-distributed computing
US6418474B1 (en) * 1999-04-16 2002-07-09 Peerless Systems Corporation Data transfer protocol flow controller and method
US20020095459A1 (en) * 2000-12-22 2002-07-18 Laux Thorsten O. Method and apparatus for providing a client by a server with an instruction data set in a predetermined format in response to a content data request message by a client
US20020116248A1 (en) * 2000-12-08 2002-08-22 Microsoft Corporation Reliable, secure and scalable infrastructure for event registration and propagation in a distributed enterprise
US6622268B2 (en) * 2000-11-29 2003-09-16 Intel Corporation Method and apparatus for propagating error status over an ECC protected channel
US20040088401A1 (en) * 2002-10-31 2004-05-06 Ashutosh Tripathi Method and apparatus for providing a highly available distributed event notification mechanism
US20040098447A1 (en) * 2002-11-14 2004-05-20 Verbeke Jerome M. System and method for submitting and performing computational tasks in a distributed heterogeneous networked environment
US20040133670A1 (en) * 2003-01-04 2004-07-08 International Business Machines Corporation Distributed notification and action mechanism for mirroring-related events
US20040181522A1 (en) * 2003-01-16 2004-09-16 Jardin Cary A. Shared memory router system and method for node communication in a distributed system
US20040205048A1 (en) * 2003-03-28 2004-10-14 Pizzo Michael J. Systems and methods for requesting and receiving database change notifications
US6839748B1 (en) * 2000-04-21 2005-01-04 Sun Microsystems, Inc. Synchronous task scheduler for corba gateway
US20050050151A1 (en) * 2003-08-29 2005-03-03 Accenture Global Services Gmbh Scalable instant messaging architecture
US7047475B2 (en) * 2003-02-04 2006-05-16 Hewlett-Packard Development Company, L.P. CRC encoding scheme for conveying status information
US7085835B2 (en) * 2001-05-09 2006-08-01 International Business Machines Corporation Apparatus, system and method for subscription computing using spare resources of subscriber computing platforms
US7165097B1 (en) * 2000-09-22 2007-01-16 Oracle International Corporation System for distributed error reporting and user interaction
US7231437B2 (en) * 2002-05-21 2007-06-12 Sun Microsystems, Inc. Task submission systems and methods for a distributed test framework
US7234142B1 (en) * 1999-06-09 2007-06-19 Nec Corporation Task processing system
US7406632B2 (en) * 2002-06-26 2008-07-29 Fujitsu Siemens Computers, Llc Error reporting network in multiprocessor computer
US7433898B1 (en) * 2004-06-01 2008-10-07 Sanbolic, Inc. Methods and apparatus for shared storage journaling
US7457914B2 (en) * 2005-03-25 2008-11-25 Emc Corporation Asynchronous event notification
US7480725B2 (en) * 2004-09-16 2009-01-20 Invensys Systems, Inc. Transparent relocation of an active redundant engine in supervisory process control data acquisition systems
US7509244B1 (en) * 2004-12-22 2009-03-24 The Mathworks, Inc. Distributed model compilation
US7516360B2 (en) * 2003-09-12 2009-04-07 International Business Machines Corporation System and method for execution of a job in a distributed computing architecture
US7533141B2 (en) * 2003-01-24 2009-05-12 Sun Microsystems, Inc. System and method for unique naming of resources in networked environments
US7640547B2 (en) * 2002-02-08 2009-12-29 Jpmorgan Chase & Co. System and method for allocating computing resources of a distributed computing system
US7707580B2 (en) * 2004-01-28 2010-04-27 Kabushiki Kaisha Toshiba Parallel computing method, parallel computing program and computer
US7730015B1 (en) * 2004-10-15 2010-06-01 Oracle America, Inc. Stackable storage access mechanism for file systems
US7827283B2 (en) * 2003-02-19 2010-11-02 International Business Machines Corporation System for managing and controlling storage access requirements
US7848834B2 (en) * 2003-03-28 2010-12-07 Gm Global Technology Operations, Inc. Computerized system for network-based management of engineering projects
US7908313B2 (en) * 2004-07-21 2011-03-15 The Mathworks, Inc. Instrument-based distributed computing systems

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5414845A (en) * 1992-06-26 1995-05-09 International Business Machines Corporation Network-based computer system with improved network scheduling system
US7917259B2 (en) * 1997-05-16 2011-03-29 Snap-On Technologies, Inc. Distributed vehicle service method and system
WO2001014961A3 (en) * 1999-08-26 2001-08-02 Parabon Computation System and method for the establishment and utilization of networked idle computational processing power
US7103628B2 (en) * 2002-06-20 2006-09-05 Jp Morgan Chase & Co. System and method for dividing computations
US7114106B2 (en) * 2002-07-22 2006-09-26 Finisar Corporation Scalable network attached storage (NAS) testing tool
US20050132089A1 (en) * 2003-12-12 2005-06-16 Octigabay Systems Corporation Directly connected low latency network and interface
CA2493732A1 (en) * 2004-01-23 2005-07-23 Gridiron Software, Inc. Authentication in a distributed computing environment

Patent Citations (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4980857A (en) * 1987-04-15 1990-12-25 Allied-Signal Inc. Operations controller for a fault tolerant multiple node processing system
US6330572B1 (en) * 1998-07-15 2001-12-11 Imation Corp. Hierarchical data storage management
US6282697B1 (en) * 1998-09-18 2001-08-28 Wylci Fables Computer processing and programming method using autonomous data handlers
US6418474B1 (en) * 1999-04-16 2002-07-09 Peerless Systems Corporation Data transfer protocol flow controller and method
US7234142B1 (en) * 1999-06-09 2007-06-19 Nec Corporation Task processing system
US6839748B1 (en) * 2000-04-21 2005-01-04 Sun Microsystems, Inc. Synchronous task scheduler for corba gateway
US20020019844A1 (en) * 2000-07-06 2002-02-14 Kurowski Scott J. Method and system for network-distributed computing
US7165097B1 (en) * 2000-09-22 2007-01-16 Oracle International Corporation System for distributed error reporting and user interaction
US6622268B2 (en) * 2000-11-29 2003-09-16 Intel Corporation Method and apparatus for propagating error status over an ECC protected channel
US20020116248A1 (en) * 2000-12-08 2002-08-22 Microsoft Corporation Reliable, secure and scalable infrastructure for event registration and propagation in a distributed enterprise
US20020095459A1 (en) * 2000-12-22 2002-07-18 Laux Thorsten O. Method and apparatus for providing a client by a server with an instruction data set in a predetermined format in response to a content data request message by a client
US7085835B2 (en) * 2001-05-09 2006-08-01 International Business Machines Corporation Apparatus, system and method for subscription computing using spare resources of subscriber computing platforms
US7640547B2 (en) * 2002-02-08 2009-12-29 Jpmorgan Chase & Co. System and method for allocating computing resources of a distributed computing system
US7231437B2 (en) * 2002-05-21 2007-06-12 Sun Microsystems, Inc. Task submission systems and methods for a distributed test framework
US7406632B2 (en) * 2002-06-26 2008-07-29 Fujitsu Siemens Computers, Llc Error reporting network in multiprocessor computer
US20040088401A1 (en) * 2002-10-31 2004-05-06 Ashutosh Tripathi Method and apparatus for providing a highly available distributed event notification mechanism
US20040098447A1 (en) * 2002-11-14 2004-05-20 Verbeke Jerome M. System and method for submitting and performing computational tasks in a distributed heterogeneous networked environment
US20040133670A1 (en) * 2003-01-04 2004-07-08 International Business Machines Corporation Distributed notification and action mechanism for mirroring-related events
US20040181522A1 (en) * 2003-01-16 2004-09-16 Jardin Cary A. Shared memory router system and method for node communication in a distributed system
US7533141B2 (en) * 2003-01-24 2009-05-12 Sun Microsystems, Inc. System and method for unique naming of resources in networked environments
US7047475B2 (en) * 2003-02-04 2006-05-16 Hewlett-Packard Development Company, L.P. CRC encoding scheme for conveying status information
US7827283B2 (en) * 2003-02-19 2010-11-02 International Business Machines Corporation System for managing and controlling storage access requirements
US20040205048A1 (en) * 2003-03-28 2004-10-14 Pizzo Michael J. Systems and methods for requesting and receiving database change notifications
US7848834B2 (en) * 2003-03-28 2010-12-07 Gm Global Technology Operations, Inc. Computerized system for network-based management of engineering projects
US20050050151A1 (en) * 2003-08-29 2005-03-03 Accenture Global Services Gmbh Scalable instant messaging architecture
US7516360B2 (en) * 2003-09-12 2009-04-07 International Business Machines Corporation System and method for execution of a job in a distributed computing architecture
US7707580B2 (en) * 2004-01-28 2010-04-27 Kabushiki Kaisha Toshiba Parallel computing method, parallel computing program and computer
US7433898B1 (en) * 2004-06-01 2008-10-07 Sanbolic, Inc. Methods and apparatus for shared storage journaling
US7908313B2 (en) * 2004-07-21 2011-03-15 The Mathworks, Inc. Instrument-based distributed computing systems
US7480725B2 (en) * 2004-09-16 2009-01-20 Invensys Systems, Inc. Transparent relocation of an active redundant engine in supervisory process control data acquisition systems
US7730015B1 (en) * 2004-10-15 2010-06-01 Oracle America, Inc. Stackable storage access mechanism for file systems
US7509244B1 (en) * 2004-12-22 2009-03-24 The Mathworks, Inc. Distributed model compilation
US7457914B2 (en) * 2005-03-25 2008-11-25 Emc Corporation Asynchronous event notification

Cited By (68)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070050484A1 (en) * 2005-08-26 2007-03-01 Roland Oertig Enterprise application server system and method
US8332479B2 (en) * 2005-08-26 2012-12-11 Hewlett-Packard Development Company, L.P. Enterprise application server system and method
US20070101019A1 (en) * 2005-11-03 2007-05-03 Cromer Daryl C Apparatus, system, and method for managing response latency
US8870647B2 (en) 2006-04-12 2014-10-28 Bally Gaming, Inc. Wireless gaming environment
US9786123B2 (en) 2006-04-12 2017-10-10 Bally Gaming, Inc. Wireless gaming environment
US8052519B2 (en) 2006-06-08 2011-11-08 Bally Gaming, Inc. Systems, methods and articles to facilitate lockout of selectable odds/advantage in playing card games
US9101820B2 (en) 2006-11-09 2015-08-11 Bally Gaming, Inc. System, method and apparatus to produce decks for and operate games played with playing cards
US20090131163A1 (en) * 2006-11-10 2009-05-21 Bally Gaming, Inc. Assignment template and assignment bundle in a gaming configuration and download system
US8784212B2 (en) 2006-11-10 2014-07-22 Bally Gaming, Inc. Networked gaming environment employing different classes of gaming machines
US20080200255A1 (en) * 2006-11-10 2008-08-21 Bally Gaming, Inc. Networked gaming environment employing different classes of gaming machines
US8631501B2 (en) 2006-11-10 2014-01-14 Bally Gaming, Inc. Reporting function in gaming system environment
US20080162729A1 (en) * 2006-11-10 2008-07-03 Bally Gaming, Inc. Gaming system download network architecture
US9111078B2 (en) 2006-11-10 2015-08-18 Bally Gaming, Inc. Package manager service in gaming system
US20080153600A1 (en) * 2006-11-10 2008-06-26 Bally Gaming, Inc. Gaming system configuration change reporting
US9275512B2 (en) 2006-11-10 2016-03-01 Bally Gaming, Inc. Secure communications in gaming system
US20080171598A1 (en) * 2006-11-10 2008-07-17 Bally Gaming, Inc. Secure communications in gaming system
US20080154916A1 (en) * 2006-11-10 2008-06-26 Bally Gaming, Inc. Package manager service in gaming system
US9508218B2 (en) 2006-11-10 2016-11-29 Bally Gaming, Inc. Gaming system download network architecture
US8920233B2 (en) 2006-11-10 2014-12-30 Bally Gaming, Inc. Assignment template and assignment bundle in a gaming configuration and download system
US9082258B2 (en) 2006-11-13 2015-07-14 Bally Gaming, Inc. Method and system for providing download and configuration job progress tracking and display via host user interface
US9466172B2 (en) 2006-11-13 2016-10-11 Bally Gaming, Inc. Download and configuration management engine for gaming system
US8667457B2 (en) 2006-11-13 2014-03-04 Bally Gaming, Inc. System and method for validating download or configuration assignment for an EGM or EGM collection
US20090118001A1 (en) * 2007-11-02 2009-05-07 Bally Gaming, Inc. Game related systems, methods, and articles that combine virtual and physical elements
US8734245B2 (en) 2007-11-02 2014-05-27 Bally Gaming, Inc. Game related systems, methods, and articles that combine virtual and physical elements
US9613487B2 (en) 2007-11-02 2017-04-04 Bally Gaming, Inc. Game related systems, methods, and articles that combine virtual and physical elements
US20090115133A1 (en) * 2007-11-02 2009-05-07 Bally Gaming, Inc. Game related systems, methods, and articles that combine virtual and physical elements
US8920236B2 (en) 2007-11-02 2014-12-30 Bally Gaming, Inc. Game related systems, methods, and articles that combine virtual and physical elements
US8616958B2 (en) 2007-11-12 2013-12-31 Bally Gaming, Inc. Discovery method and system for dynamically locating networked gaming components and resources
US20090183243A1 (en) * 2007-11-12 2009-07-16 Bally Gaming, Inc. User authorization system and methods
US8201229B2 (en) 2007-11-12 2012-06-12 Bally Gaming, Inc. User authorization system and methods
US20090131144A1 (en) * 2007-11-12 2009-05-21 Bally Gaming, Inc. Meta-option
US8819124B2 (en) 2007-11-12 2014-08-26 Bally Gaming, Inc. System and method for one-way delivery of notifications from server-to-clients using modified multicasts
US20130060832A1 (en) * 2007-11-22 2013-03-07 Telefonaktiebolaget L M Ericsson (Publ) Method and device for agile computing
US8959210B2 (en) * 2007-11-22 2015-02-17 Telefonaktiebolaget L M Ericsson (Publ) Method and device for agile computing
US9005034B2 (en) 2008-04-30 2015-04-14 Bally Gaming, Inc. Systems and methods for out-of-band gaming machine management
US8856657B2 (en) * 2008-04-30 2014-10-07 Bally Gaming, Inc. User interface for managing network download and configuration tasks
US20090275402A1 (en) * 2008-04-30 2009-11-05 Bally Gaming, Inc. Information distribution in gaming networks
US20090275401A1 (en) * 2008-04-30 2009-11-05 Bally Gaming, Inc. Method, system, apparatus, and article of manufacture for profile-driven configuration for electronic gaming machines (egms)
US8721431B2 (en) 2008-04-30 2014-05-13 Bally Gaming, Inc. Systems, methods, and devices for providing instances of a secondary game
US20090276715A1 (en) * 2008-04-30 2009-11-05 Bally Gaming, Inc. User interface for managing network download and configuration tasks
US20090275395A1 (en) * 2008-04-30 2009-11-05 Bally Gaming, Inc. Systems and methods for out-of-band gaming machine management
US20090275374A1 (en) * 2008-04-30 2009-11-05 Bally Gaming, Inc. Tournament play in a gaming property
US9483911B2 (en) 2008-04-30 2016-11-01 Bally Gaming, Inc. Information distribution in gaming networks
US20100016068A1 (en) * 2008-05-24 2010-01-21 Bally Gaming, Inc. Networked gaming system with enterprise accounting methods and apparatus
US20100016067A1 (en) * 2008-05-24 2010-01-21 Bally Gaming, Inc. Networked gaming system with enterprise accounting methods and apparatus
US8382584B2 (en) 2008-05-24 2013-02-26 Bally Gaming, Inc. Networked gaming system with enterprise accounting methods and apparatus
US8366542B2 (en) 2008-05-24 2013-02-05 Bally Gaming, Inc. Networked gaming system with enterprise accounting methods and apparatus
US20090298583A1 (en) * 2008-05-30 2009-12-03 Bally Gaming, Inc. Web pages for gaming devices
US9443377B2 (en) 2008-05-30 2016-09-13 Bally Gaming, Inc. Web pages for gaming devices
US8412768B2 (en) 2008-07-11 2013-04-02 Ball Gaming, Inc. Integration gateway
US20100093441A1 (en) * 2008-07-11 2010-04-15 Bally Gaming, Inc. Integration gateway
US8851988B2 (en) 2008-11-14 2014-10-07 Bally Gaming, Inc. Apparatus, method, and system to provide a multiple processor architecture for server-based gaming
US8266213B2 (en) 2008-11-14 2012-09-11 Bally Gaming, Inc. Apparatus, method, and system to provide a multiple processor architecture for server-based gaming
US20100125851A1 (en) * 2008-11-14 2010-05-20 Bally Gaming, Inc. Apparatus, method, and system to provide a multi-core processor for an electronic gaming machine (egm)
US8347303B2 (en) 2008-11-14 2013-01-01 Bally Gaming, Inc. Apparatus, method, and system to provide a multi-core processor for an electronic gaming machine (EGM)
US8423790B2 (en) 2008-11-18 2013-04-16 Bally Gaming, Inc. Module validation
US20100332593A1 (en) * 2009-06-29 2010-12-30 Igor Barash Systems and methods for operating an anti-malware network on a cloud computing platform
EP2453357A3 (en) * 2010-11-12 2012-06-27 Oracle International Corporation Event-based orchestration in distributed order orchestration system
CN102467701A (en) * 2010-11-12 2012-05-23 甲骨文国际公司 Event-based orchestration in distributed order orchestration system
US9898889B2 (en) 2011-06-06 2018-02-20 Bally Gaming, Inc. Remote game play in a wireless gaming environment
US9058716B2 (en) 2011-06-06 2015-06-16 Bally Gaming, Inc. Remote game play in a wireless gaming environment
US9792770B2 (en) 2012-01-18 2017-10-17 Bally Gaming, Inc. Play for fun network gaming system and method
US9120007B2 (en) 2012-01-18 2015-09-01 Bally Gaming, Inc. Network gaming architecture, gaming systems, and related methods
US20150237137A1 (en) * 2014-02-19 2015-08-20 Snowflake Computing Inc. Resource management systems and methods
US9826011B2 (en) * 2014-07-31 2017-11-21 Istreamplanet Co. Method and system for coordinating stream processing at a video streaming platform
US9912707B2 (en) 2014-07-31 2018-03-06 Istreamplanet Co. Method and system for ensuring reliability of unicast video streaming at a video streaming platform
US20160036886A1 (en) * 2014-07-31 2016-02-04 Istreamplanet Co. Method and system for coordinating stream processing at a video streaming platform
US9686576B2 (en) 2015-05-08 2017-06-20 Istreamplanet Co. Coordination of video stream timing in cloud-based video streaming system

Also Published As

Publication number Publication date Type
US8688765B2 (en) 2014-04-01 grant
US9582330B2 (en) 2017-02-28 grant
WO2007016657A3 (en) 2007-06-21 application
US8032582B2 (en) 2011-10-04 grant
WO2007016657A2 (en) 2007-02-08 application
US20100325121A1 (en) 2010-12-23 application
US20070276899A1 (en) 2007-11-29 application
US20090240762A1 (en) 2009-09-24 application
EP1910924A2 (en) 2008-04-16 application

Similar Documents

Publication Publication Date Title
Buyya et al. Gridsim: A toolkit for the modeling and simulation of distributed resource management and scheduling for grid computing
Casanova Simgrid: A toolkit for the simulation of application scheduling
US7634388B2 (en) Providing policy-based operating system services in an operating system on a computing system
US6810364B2 (en) Automated testing of computer system components
US6119174A (en) Methods and apparatus for implementing quality-of-service guarantees in data storage systems
US7035786B1 (en) System and method for multi-phase system development with predictive modeling
US20110083131A1 (en) Application Profile Based Provisioning Architecture For Virtual Remote Desktop Infrastructure
US20040243692A1 (en) Policy-based, autonomically allocated storage
US20070233838A1 (en) Method for workload management of plural servers
US20060075407A1 (en) Distributed system interface
US20040003063A1 (en) Procedure for dynamic reconfiguration of resources of logical partitions
Yigitbasi et al. C-meter: A framework for performance analysis of computing clouds
US7093247B2 (en) Installation of a data processing solution
US20040167765A1 (en) System and method for improving predictive modeling of an information system
US8032899B2 (en) Providing policy-based operating system services in a hypervisor on a computing system
US7454749B2 (en) Scalable parallel processing on shared memory computers
US20050034130A1 (en) Balancing workload of a grid computing environment
Swamy et al. OO-VHDL. Object-oriented extensions to VHDL
US20070074203A1 (en) Deployment, maintenance and configuration of complex hardware and software systems
Liu et al. Design-level performance prediction of component-based applications
US5455952A (en) Method of computing based on networks of dependent objects
Huedo et al. A modular meta-scheduling architecture for interfacing with pre-WS and WS Grid resource management services
US20060070067A1 (en) Method of using scavenger grids in a network of virtualized computers
US20060235664A1 (en) Model-based capacity planning
Deelman et al. Pegasus: A framework for mapping complex scientific workflows onto distributed systems

Legal Events

Date Code Title Description
AS Assignment

Owner name: MATHWORKS, INC., THE, MASSACHUSETTS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MARTIN, JOCELYN LUKE;REEL/FRAME:016874/0018

Effective date: 20050922