Patent Application
20220261375
This disclosure relates to customizable pipeline for integrating data.
Under conventional approaches, various types of information (e.g., files) may be provided to a data analysis platform for performing myriad operations (e.g., viewing, processing, modifying, etc.). In general, the data analysis system typically needs to be able to process files that vary in type and formatting to ensure that data included in these files can accurately be integrated.
Various embodiments of the present disclosure may include systems, methods, and non-transitory computer readable media configured to determine a file to be ingested into a data analysis platform. The file type of the file may be detected. The file may be transformed based on the file type. The transformation may include applying a set of operations to the file. The set of operations may correspond to a pipeline of operations associated with the file type. The pipeline of operations may be defined by a template specification. The pipeline of operations may be customizable. The transformed file may be stored based on completion of all operations within the pipeline of operations.
In some embodiments, the pipeline of operations may include one or more serial operations, parallel operations, and one or more join operations. The join operation(s) may merge two or more results of the parallel operations. For example, data included in a single or multiple files may be operated on in parallel, and the results of the parallel operation may be joined together for use by a data analysis platform.
In some embodiments, the pipeline of operations may include a normalization operation. For example, data included in multiple files may be of different type (e.g., entered using separate scales) and the data may be normalized (e.g., into a common scale) so that the data may be joined/used together by a data analysis platform.
In some embodiments, the pipeline of operations may include an enriching operation. For example, data included in a file may be supplemented with other data from other sources to provide additional information (e.g., context) for the data.
In some embodiments, the file type of the file may be detected based on operation of one or more detectors. A given detector may be configured to detect one or more given file types. For example, a file may be passed to a first detector configured to detect a first file type. If the file type does not match the first file type, the file may be passed to a second detector configured to detect a second file type. The passing of the file between detectors may continue until the file type has been detected or no match is found from the detectors. In some embodiments, the file may be serially passed among the detectors. In some embodiments, the file may be passed to multiple detectors in parallel. In some embodiments, a detector may generate metadata for use in transforming the file.
In some embodiments, the file type of the file may be detected based on an arrangement of information within the file. For example, the file type may be detected based on a structure and/or pattern of information in the file or based on the actual information included in the file.
In some embodiments, the file may be transformed based on operation of one or more transformers. A transformer may be associated with a detector. For example, based on a file type being detected by a given detector, the file may be transformed by a given transformer associated with the given detector.
In some embodiments, the computing system may change the pipeline of operations and remove one or more effects resulting from previously applied pipeline of operations. Removing the effect(s) of prior operation pipelines may allow the computing system to resolve the pipeline against known states by atomically handling the pipeline.
In some embodiments, the transformation of the file may be case dependent, upload dependent, or user dependent. For example, one or more detectors/transformers may be associated with a given case to which the file belongs/is associated, a given upload in which the file is received, or a given user/entity that provided the file.
These and other features of the systems, methods, and non-transitory computer readable media disclosed herein, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for purposes of illustration and description only and are not intended as a definition of the limits of the invention.
Certain features of various embodiments of the present technology are set forth with particularity in the appended claims. A better understanding of the features and advantages of the technology will be obtained by reference to the following detailed description that sets forth illustrative embodiments, in which the principles of the invention are utilized, and the accompanying drawings of which:
A claimed solution rooted in computer technology overcomes problems specifically arising in the realm of computer technology. In various implementations, a computing system may determine a file to be ingested into a data analysis platform (e.g., based on user upload, system download). The file type of the file may be detected. In some embodiments, the file type of the file may be detected based on an arrangement of information within the file. For example, the file type may be detected based on a structure and/or pattern of information in the file or based on the actual information included in the file.
The file type of the file may be detected based on operation of one or more detectors. A given detector may be configured to detect one or more given file types. For example, a file may be passed to a first detector configured to detect a first file type. If the file type does not match the first file type, the file may be passed to a second detector configured to detect a second file type. The passing of the file between detectors may continue until the file type has been detected or no match is found from the detectors. For example, the file may be serially passed among the detectors. As another example, the file may be passed to multiple detectors in parallel. A detector may generate metadata for use in transforming the file.
The file may be transformed based on the file type. The transformation may include applying a set of operations to the file. The set of operations may correspond to a pipeline of operations associated with the file type. The transformed file may be stored based on completion of all operations within the pipeline of operations. The file may be transformed based on operation of one or more transformers. A transformer may be associated with a detector. For example, based on a file type being detected by a given detector, the file may be transformed by a given transformer associated with the given detector.
The transformation of the file may be case dependent, upload dependent, or user dependent. For example, one or more detectors/transformers may be associated with a given case to which the file belongs/is associated, a given upload in which the file is received, or a given user/entity that provided the file.
The pipeline of operations may be defined by a template specification. The pipeline of operations may be customizable. The pipeline of operations may include one or more serial operations, parallel operations, and/or one or more join operations. The join operation(s) may merge two or more results of the parallel operations. For example, data included in a single or multiple files may be operated on in parallel, and the results of the parallel operation may be joined together for use by a data analysis platform. The pipeline of operations may include a normalization operation. For example, data included in multiple files may be of different type (e.g., entered using separate scales) and the data may be normalized (e.g., into a common scale) so that the data may be joined/used together by a data analysis platform. The pipeline of operations may include an enriching operation. For example, data included in a file may be supplemented with other data from other sources to provide additional information (e.g., context) for the data.
The computing system may change the pipeline of operations and remove one or more effects resulting from a previously applied pipeline of operations. Removing the effect(s) of a prior pipeline of operations may allow the computing system to resolve the pipeline against known states by atomically handling the pipeline.
In various embodiments, the file engine 112 may be configured to determine a file to be ingested into a data analysis platform. A data analysis platform may refer to hardware/software components configured to provide analysis capabilities for data (e.g., database analysis tool). A data analysis platform may require data to be stored using a particular structure/format and/or include one or more particular types of information. The file to be ingested into the data analysis platform may be determined (e.g., identified) by the file engine 112 based on reception/identification of the file by the computing system 102 and/or reception/identification of the file by a network/server/computing device monitored by the computing system 102.
For example, a user may upload a given file to the computing system 102 or a network/server/computing device monitored by the computing system 102 via an interface that receives inputs for the data analysis platform. The file engine 112 may determine that the given file is to be ingested into the data analysis platform based on the user's use of the interface to upload the given file. As another example, a user may use the computing system 102 or a network/server/computing device monitored by the computing system 102 to select a particular file for ingestion into the data analysis platform. The file engine 112 may determine that the particular file is to be ingested into the data analysis platform based on the user's selection of the particular file.
In some embodiments, one or more characteristics/properties of the file relating to its ingestion into a data analysis platform may be defined when the user uploads/selects the file for ingestion. Such information may be used to (1) determine that the file is to be ingested into a data analysis platform, (2) identify the data analysis platform to which the file is to be ingested, (3) detect a file type of the file, and/or (4) determine any transformation(s) to be applied to the file. For example, such information may identify/relate to a name of the file, file type of the file, destination of the file, related files/case, source of the file, persons/organizations related to the file, content of the file, context of the file, and/or other information related to the file.
In some embodiments, the file to be ingested into a data analysis platform may include an archive file. An archive file may refer to a file that includes a collection multiple files in a single file (e.g., zip file, rar file, 7z file, tar file, jar file, war file). An archive file may provide for concatenation of files, compression of files, encryption of files, error detection of files, self-extraction of files, and/or other operations relating to archiving of files. An archive file may include information (e.g., metadata) relating to the files within the archive file and/or how the files within the archive file may be extracted.
In some embodiments, the file engine 112 may be configured to determine that the file to be ingested into a data analysis platform is an archive file. The file engine 112 may determine that the file is an archive file based on file format (e.g., file extension), analysis of the file (e.g., analysis of structure, pattern within the file), user input (e.g., user indication that the file is an archive file during file upload/selection for ingestion), information (e.g., metadata) relating to the file, and/or other information. Based on the file to be ingested into a data analysis platform being an archive file, the file engine 112 may extract the files within the archive file.
In various embodiments, the file type engine 114 may be configured to detect a file type of the file to be ingested into the data analysis platform. The file type engine 114 may detect the file type of the file based on file format (e.g., file extension), analysis of the file (e.g., analysis of structure, pattern within the file), user input (e.g., user indication that the file is a particular type of a file), information (e.g., metadata) relating to the file, and/or other information. For example, the file type of the file may be detected based on the particular arrangement of information within the file. That is, the file type may be detected based on the structure(s) and/or the pattern(s) of information in the file, and/or based on the actual information included in the file. For example, a file type may be determined to be a portable document format (PDF) based on the file extension. The file type may be determined to be a specific type of PDF file based on the file extension and the arrangement of information within the file. As another example, a file type may be determined to be a particular picture format based on the arrangement of information (e.g., information defining pictures, headers/metadata for the pictures) within the file. As another example, a file type may be determined to be an email of a particular type (e.g., accessible by particular email client(s)) based on the file extension and/or the information within the file. As another example, a file type may be determined to be a document relating to a particular type of investigation (e.g., claims demand information) based on organization of information within the file, actual information within the file (e.g., case identifier). Other detections of file types are contemplated.
In some embodiments, the file type of the file to be ingested into the data analysis platform may be detected based on operation of one or more detectors. A detector may refer to a service, a process, a plugin, an executable, and/or other software components. Individuals detectors may be configured to detect one or more individual file types. For example, a given detector may be configured to detect a given file type. The file type of the file to be ingested into the data analysis platform may be detected by passing the file to different detectors. In some embodiments, the file may be serially passed among different detectors. For example, a file may be passed to a first detector configured to detect a first file type. If the file type does not match the first file type, the file may be passed to a second detector configured to detect a second file type. The passing of the file between detectors may continue until the file type has been detected or no match is found from the detectors. In some embodiments, the file may be passed to multiple detectors in parallel. For example, a file may be passed on to a first detector configured to detect a first file type and a second detector configured to detect a second file type in parallel.
If the file type of the file is not detectable by any detectors, e.g., the file type may not match any of the file types detectable by the detectors, then the file may be designated as a non-integratable file. For example, the file may be marked as a generic file which is not configured for ingestion into the data analysis platform. In some embodiments, users may update/modify the set of detectors to include additional detectors for such generic files.
Once the file type of the file has been detected, the detector (that detected the file type) may pass the file to one or more software components (e.g., transformers) for transformation. In some embodiments, a detector may generate information for use in transforming the file. For example, the detector that detected the file type may generate metadata including information relating to the file type and/or information relating to transformation(s) to be performed based on the file type. The information generated by the detector may be passed to one or more software components performing the transformation and/or may be used to identify the software component(s) to perform the transformation. In some embodiments, a detector may provide the file/contents of the file to a data transformation platform for transformation. For example, the file/contents of the file may be streamed to a data transformation platform as one or more objects/stores.
In various embodiments, the transformation engine 116 may be configured to transform the file to be ingested into the data analysis platform based on the file type. Transformation of the file may include applying a set of operations to the file. An operation may include one or more data transformations. Such data transformations can include data extraction, data processing, data integration (e.g., with other data), and data manipulation (e.g., language/mathematical operations, deduping operations), to provide some examples. In some embodiments, the transformation engine 116 may store results of applying the set of operations to the file/contents of the file (e.g., the transformed file/contents) based on completion of all operations within the pipeline of operations. Such storage of the transformed file/contents may ensure data consistency.
The set of operations may correspond to a pipeline of operations associated with the file type. The pipeline of operations may be defined by one or more template specifications. The pipeline of operations may identify the operations and the order in which the operations are to be performed. The pipeline of operations may identify other data to be used in one or more of the operations (e.g., data to be integrated with/into the file/contents of the file). The pipeline of operations may enable dynamic selection of options for one or more operations. For example, the pipeline of operations may include one or more operations that receive inputs from users (e.g., selection of operation options) for performing the operation(s).
In some embodiments, the pipeline of operations may include one or more serial operations, parallel operations, one or more join operations, and/or other operations. Serial operations may refer to operations that are performed in a sequence. For example, a pipeline of operations may include a first operation and a second operation to be performed on the file/contents of the file. After the first operation is performed, the second operation may be performed. Parallel operations may refer to operations that are performed simultaneously/overlapping in time. For example, referring to the foregoing example of first and second operations, the first operation and the second operation may be performed at the same time on the file/contents of the file. Join operations may refer to operations that merge two or more results of parallel operations. For example, referring to the foregoing example of first and second parallel operations, the results of the first and second parallel operations on the file/contents of the file may be joined/merged together (e.g., for use by a data analysis platform, for further processing).
In some embodiments, the pipeline of operations may include one or more normalization operations. A normalization operation may refer to an operation that adjusts the values of some data (e.g., first dataset) so that it can be used with other data (e.g., second dataset). For example, a first dataset and a second dataset transformed by the transformation engine 116 may be recorded/entered using different scales (e.g., different measurement standards) or different properties (e.g., the first dataset including types of information not included in the second dataset). The first dataset and the second dataset may be included within a single file or multiple files to be ingested into a data analysis platform. The normalization operation can modify the first and/or the second datasets so that they can be used (e.g., joined, compared, operated) together by the data analysis platform. For example, the normalization operation may adjust the values of the first and/or the second dataset so that they are recorded using the same scale (e.g., same measurement standard) and/or may modify the information contained within the first and/or the second datasets so that they contain the same type of information.
In some embodiments, the pipeline of operations may include one or more enriching operations. An enriching operation may refer to an operation that enhances the information contained within the file. For example, data included in a file may be supplemented with data from other data sources to provide additional information (e.g., context) for the data.
The pipeline of operations may enable the use of multiple jobs to process a file/contents of a file for ingestion into a data analysis platform. For example, different parts of preparing the file/contents of the file for ingestion into the data analysis platform may be separated in different jobs. The jobs may be modular so that they are transferrable to different pipelines and/or modifiable within a pipeline. The jobs may enable different operations on different portions of the file/different contents of the file.
The pipeline of operations may enable the use of linear or branching pipelines of operations. A linear pipeline may refer to a pipeline including serial operations. A branching pipeline may refer to a pipeline including parallel/join operations. For example, a branching pipeline may include a pipeline that starts with one input and ends with one output along with parallel and join operations between the input and the output. A branching pipeline may include a pipeline that starts with one input and ends with multiple outputs along with parallel operations between the input and the outputs. A branching pipeline may include a pipeline that starts with multiple inputs and ends with an output along with join operations between the inputs and the output. A branching pipeline may include a pipeline that starts with multiple inputs and ends with multiple outputs along with parallel operations between the inputs and the outputs. Use of different combinations of serial, parallel, join, and/or other operations for pipelines of operations are contemplated.
Transformation of the file/contents of the file may be performed by a data transformation platform. A data transformation platform may refer to hardware/software components configured to provide transformation capabilities for data (e.g., a data manipulation tool). A data transformation platform may provide for data extraction, data processing, data integration (e.g., with other data), data manipulation, and/or other data transformations. For example, the file/contents of the file may be mapped, converted, changed, merged, aggregated, enriched, summarized, filtered, and/or otherwise transformed by the data transformation platform. A data transformation platform may ensure that data from one application/database/platform is usable by other application(s)/database(s)/platform(s). A data transformation platform may be able to transform the file/contents of the file so that the transformed file/contents (transformed to a particular structure/format and/or transformed to include one or more particular types of information) are available for use by a data analysis platform.
Using a data transformation platform for transformation of a file/contents of a file may enable the transformation engine 116 to execute the pipeline of operations without having codes for individual operations of the pipeline. Such codes may refer to codes of the data transformation platform which, when executed, provides data extraction, data processing, data integration, data manipulation, and/or other data transformations for individual operations of the pipeline. Using the data transformation platform may reduce the size and/or the complexity of the transformation engine 116 and/or one or more software components (e.g., transformers) used for transformation. For example, rather than coding the entirety of the operations within a transformer, the transformer may include codes to request one or more of the operations to be performed by the data transformation platform.
For example, to perform a join operation, the transformation engine 116 may not need to have the raw codes that perform the join operation. Instead, the transformation engine 116 may request the join operation be performed by the data transformation platform (via application programming interface(s)). By taking advantage of the capability of the data transform platform, the transformation engine 116 may be able to execute the pipeline of operations by offloading the performance of the operations to the data transform platform. The use of the data transform platform may increase the type of operations that may be included within the pipeline of operations. The pipeline of operations may include any operations enabled by the data transform platform. The use of the data transform platform may enable the transformation engine 116 to use the resources (e.g., hardware/software capabilities) of the data transform platform for performing operations on the file/contents of the file.
In some embodiments, the file may be transformed based on operation of one or more transformers. A transformer may refer to a service, a process, a plugin, an executable, and/or other software components. In some embodiments, individual transformers may be associated with individual detectors. In some embodiments, a single transformer may be associated with multiple detectors. In some embodiments, multiple transformers may be associated with a single detector. A file/contents of the file may be transformed by a given transformer based on the file type of the file being detected by a given detector. For example, based on a file type being detected by a given detector, the file may be transformed by a given transformer associated with the given detector. For example, based on a file type of a file being detected by an email detector, an email transformer may transform the file/contents of the file. The email transformer may provide integration of an email file type for use by a data analysis platform. In some embodiments, a transformer may be associated with a given pipeline of operations/a given template specification of the given pipeline. The operation of the transformer may include execution of the associated pipeline of operations to transform the file/contents of the file.
In some embodiments, one or more transformers may be activated based on user selection of the transformer(s). For example, a user may be provided with a view of the transformers identified (transformers corresponding to the detector that detected the file type) for transformation of files/contents of files. The user may select one or more of the identified transformers to activate the transformer and execute the pipeline of operations corresponding to the selected transformers.
In some embodiments, the transformation of the file may be case dependent, upload dependent, and/or user dependent. For example, one or more detectors/transformers may be associated with a given case to which the file belongs/is associated, a given upload in which the file is received, or a given user/entity that provided the file. Use of case dependent detectors/transformer allows the same/particular detectors/transformers to be used for files associated with a given case. Use of upload dependent detectors/transformer allows the same/particular detectors/transformers to be used for files uploaded together. Use of user-dependent detectors/transforms allows the same/particular detectors/transformers to be used for files provided by the same user/entity.
For example, transaction records of two different entities (first entity, second entity) may be stored using the same file extension (e.g., workbook file format). However, the transaction records of the different entities may be stored differently (e.g., include different information, include information stored using different organization) such that the transformation of the records for ingestion into a data analysis platform may require different operations/pipelines of operations. For example, the transaction records of the first entity may require different clean-up operations (e.g., filtering, deduping) than the transaction records of the second entity.
As another example, a case may include files of different types. The different types of files may require different operations/pipeline of operations for ingestion into a data analysis platform. The files may be uploaded separately, with the upload-specific detectors/transformers being used for separate uploads to transform the files/contents of the files so that they may be used together. The transformed files/contents of the files may be used together (e.g., merged, compared) using case-specific detectors/transformers. Other uses of case-dependent, upload-dependent, user-dependent detectors/transformers are contemplated.
The pipeline of operations may be customizable. Customizing a pipeline of operations may include one or more of adding a new operation to the pipeline, removing an operation from the pipeline, and/or modifying an operation within the pipeline. Customizing pipeline of operations may include changing one or more parameters of one or more operations within the pipeline. The pipeline of operations may be customized via changes to the corresponding template specifications.
In some embodiments, a pipeline of operations may be managed to resolve the pipeline of operations against known states. Managing the pipelines may include atomically handling the pipelines and removing effects of prior versions of pipelines. For example, changing a pipeline of operations may include removing one or more effects resulting from a previous version of the pipeline (e.g., removing effect(s) of previously applied operations). For example, a pipeline of operations may include operation A, followed by operation B, followed by operation C. Operation B may have an effect of storing certain information in a database. The pipeline of operations may have been used to process a file uploaded at a given time (upload A). The pipeline of operations may be modified to remove operation B from the pipeline. If upload A is unprocessed/reprocessed, a special/modified pipeline (e.g., delete pipeline) may be constructed to remove the effects of operation B (the certain information stored in the database) from the pipeline. In some embodiments, an effect of an operation may be removed by providing a null input into operation B. For example, operation B may have taken a given input to stored certain information in a database. Passing a null value to operation B may result in removal of the certain information from the database.
The pipeline of operations 300 may begin with an operation 302 that accesses one or more portions of a file. Serial operations 304, 306 may then be performed on the portion(s) of the file. Parallel to the serial operations 304, 306, a parallel operation 308 may be performed on the portion(s) of the file. The results of the serial operations 304, 306 and the parallel operation 308 may be joined by a join operation 310. The joined results may be provided to a data analysis platform.
The pipeline of operations 320 may begin with an operation 322 that accesses one or more portions of a file. An operation 324 may then be performed on the portion(s) of the file. The operation 324 may be followed by three branching/parallel operations 326, 328, 330. That is, the result of applying the operation 324 on the file may be used to perform three separate operations 326, 328, 330 in parallel. The results of the parallel operations 326, 328, 330 may be provided to a data analysis platform.
The pipeline of operations 340 may begin with operations 342, 348 that access one or more portions of one or more files. For example, the operation 342 may access one portion of a file and the operation 348 may access another portion of the file. As another example, the operation 342 may access portion(s) of a file and the operation 348 may access portion(s) of another file. The operation 342 may be followed by two branching/parallel operations 344, 346. The results of the operation 346 and the portion(s) of the file accessed by the operation 348 may be joined by a join operation 350. The results of the operation 344 and the join operation 350 may then be joined by a join operation 352. The joined results may be provided to a data analysis platform.
The pipeline of operations 360 may begin with operations 362, 370 that access one or more portions of one or more files. For example, the operation 362 may access one portion of a file and the operation 370 may access another portion of the file. As another example, the operation 362 may access portion(s) of a file and the operation 370 may access portion(s) of another file. The operation 362 may be followed by two branching/parallel operations 364, 368. The operation 364 may be followed by a serial operation 366. The operation 370 may be followed by a serial operation 372. The results of the operation 368 and the operation 372 may be joined by a join operation 374. The results of the operations 366, 374 may be provided to a data analysis platform.
At block 402, a file to be ingested into a data analysis platform may be determined. At block 404, a file type of the file may be detected. At block 406, the file may be transformed based on the file type. The transformation may include applying a set of operations to the file. The set of operations may correspond to a pipeline of operations associated with the file type. At block 408, the pipeline of operations may optionally be changed. At block 410, one or more effects of a prior pipeline of operations may optionally be removed.
The techniques described herein are implemented by one or more special-purpose computing devices. The special-purpose computing devices may be hard-wired to perform the techniques, or may include circuitry or digital electronic devices such as one or more application-specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs) that are persistently programmed to perform the techniques, or may include one or more hardware processors programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination. Such special-purpose computing devices may also combine custom hard-wired logic, ASICs, or FPGAs with custom programming to accomplish the techniques. The special-purpose computing devices may be desktop computer systems, server computer systems, portable computer systems, handheld devices, networking devices or any other device or combination of devices that incorporate hard-wired and/or program logic to implement the techniques.
Computing device(s) are generally controlled and coordinated by operating system software, such as iOS, Android, Chrome OS, Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix, Linux, SunOS, Solaris, iOS, Blackberry OS, VxWorks, or other compatible operating systems. In other embodiments, the computing device may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface functionality, such as a graphical user interface (“GUI”), among other things.
The computer system 500 also includes a main memory 506, such as a random access memory (RAM), cache and/or other dynamic storage devices, coupled to bus 502 for storing information and instructions to be executed by processor 504. Main memory 506 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 504. Such instructions, when stored in storage media accessible to processor 504, render computer system 500 into a special-purpose machine that is customized to perform the operations specified in the instructions.
The computer system 500 further includes a read only memory (ROM) 508 or other static storage device coupled to bus 502 for storing static information and instructions for processor 504. A storage device 510, such as a magnetic disk, optical disk, or USB thumb drive (Flash drive), etc., is provided and coupled to bus 502 for storing information and instructions.
The computer system 500 may be coupled via bus 502 to a display 512, such as a cathode ray tube (CRT) or LCD display (or touch screen), for displaying information to a computer user. An input device 514, including alphanumeric and other keys, is coupled to bus 502 for communicating information and command selections to processor 504. Another type of user input device is cursor control 516, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 504 and for controlling cursor movement on display 512. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane. In some embodiments, the same direction information and command selections as cursor control may be implemented via receiving touches on a touch screen without a cursor.
The computing system 500 may include a user interface module to implement a GUI that may be stored in a mass storage device as executable software codes that are executed by the computing device(s). This and other modules may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, C or C++. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices may be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, magnetic disc, or any other tangible medium, or as a digital download (and may be originally stored in a compressed or installable format that requires installation, decompression or decryption prior to execution). Such software code may be stored, partially or fully, on a memory device of the executing computing device, for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules or computing device functionality described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage.
The computer system 500 may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computer system causes or programs computer system 500 to be a special-purpose machine. According to one embodiment, the techniques herein are performed by computer system 500 in response to processor(s) 504 executing one or more sequences of one or more instructions contained in main memory 506. Such instructions may be read into main memory 506 from another storage medium, such as storage device 510. Execution of the sequences of instructions contained in main memory 506 causes processor(s) 504 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.
The term “non-transitory media,” and similar terms, as used herein refers to any media that store data and/or instructions that cause a machine to operate in a specific fashion. Such non-transitory media may comprise non-volatile media and/or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 510. Volatile media includes dynamic memory, such as main memory 506. Common forms of non-transitory media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a CD-ROM, any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge, and networked versions of the same.
Non-transitory media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between non-transitory media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 502. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
Various forms of media may be involved in carrying one or more sequences of one or more instructions to processor 504 for execution. For example, the instructions may initially be carried on a magnetic disk or solid state drive of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 500 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 502. Bus 502 carries the data to main memory 506, from which processor 504 retrieves and executes the instructions. The instructions received by main memory 506 may retrieves and executes the instructions. The instructions received by main memory 506 may optionally be stored on storage device 510 either before or after execution by processor 504.
The computer system 500 also includes a communication interface 518 coupled to bus 502. Communication interface 518 provides a two-way data communication coupling to one or more network links that are connected to one or more local networks. For example, communication interface 518 may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 518 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN (or WAN component to communicated with a WAN). Wireless links may also be implemented. In any such implementation, communication interface 518 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
A network link typically provides data communication through one or more networks to other data devices. For example, a network link may provide a connection through local network to a host computer or to data equipment operated by an Internet Service Provider (ISP). The ISP in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet”. Local network and Internet both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link and through communication interface 518, which carry the digital data to and from computer system 500, are example forms of transmission media.
The computer system 500 can send messages and receive data, including program code, through the network(s), network link and communication interface 518. In the Internet example, a server might transmit a requested code for an application program through the Internet, the ISP, the local network and the communication interface 518.
The received code may be executed by processor 504 as it is received, and/or stored in storage device 510, or other non-volatile storage for later execution.
Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The processes and algorithms may be implemented partially or wholly in application-specific circuitry.
The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and sub-combinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated. The scope of the invention should therefore be construed in accordance with the appended claims and any equivalents thereof.
Certain embodiments are described herein as including logic or a number of components, engines, or mechanisms. Engines may constitute either software engines (e.g., code embodied on a machine-readable medium) or hardware engines. A “hardware engine” is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various example embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware engines of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware engine that operates to perform certain operations as described herein.
In some embodiments, a hardware engine may be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware engine may include dedicated circuitry or logic that is permanently configured to perform certain operations. For example, a hardware engine may be a special-purpose processor, such as a Field-Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). A hardware engine may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware engine may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware engines become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware engine mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
Accordingly, the phrase “hardware engine” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. As used herein, “hardware-implemented engine” refers to a hardware engine. Considering embodiments in which hardware engines are temporarily configured (e.g., programmed), each of the hardware engines need not be configured or instantiated at any one instance in time. For example, where a hardware engine comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware engines) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware engine at one instance of time and to constitute a different hardware engine at a different instance of time.
Hardware engines can provide information to, and receive information from, other hardware engines. Accordingly, the described hardware engines may be regarded as being communicatively coupled. Where multiple hardware engines exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware engines. In embodiments in which multiple hardware engines are configured or instantiated at different times, communications between such hardware engines may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware engines have access. For example, one hardware engine may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware engine may then, at a later time, access the memory device to retrieve and process the stored output. Hardware engines may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).
The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented engines that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented engine” refers to a hardware engine implemented using one or more processors.
Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented engines. Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an Application Program Interface (API)).
The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processors or processor-implemented engines may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, the processors or processor-implemented engines may be distributed across a number of geographic locations.
Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.
Although an overview of the subject matter has been described with reference to specific example embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of embodiments of the present disclosure. Such embodiments of the subject matter may be referred to herein, individually or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single disclosure or concept if more than one is, in fact, disclosed.
The embodiments illustrated herein are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed. Other embodiments may be used and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. The Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.
It will be appreciated that an “engine,” “system,” “data store,” and/or “database” may comprise software, hardware, firmware, and/or circuitry. In one example, one or more software programs comprising instructions capable of being executable by a processor may perform one or more of the functions of the engines, data stores, databases, or systems described herein. In another example, circuitry may perform the same or similar functions. Alternative embodiments may comprise more, less, or functionally equivalent engines, systems, data stores, or databases, and still be within the scope of present embodiments. For example, the functionality of the various systems, engines, data stores, and/or databases may be combined or divided differently.
“Open source” software is defined herein to be source code that allows distribution as source code as well as compiled form, with a well-publicized and indexed means of obtaining the source, optionally with a license that allows modifications and derived works.
The data stores described herein may be any suitable structure (e.g., an active database, a relational database, a self-referential database, a table, a matrix, an array, a flat file, a documented-oriented storage system, a non-relational No-SQL system, and the like), and may be cloud-based or otherwise.
As used herein, the term “or” may be construed in either an inclusive or exclusive sense. Moreover, plural instances may be provided for resources, operations, or structures described herein as a single instance. Additionally, boundaries between various resources, operations, engines, engines, and data stores are somewhat arbitrary, and particular operations are illustrated in a context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within a scope of various embodiments of the present disclosure. In general, structures and functionality presented as separate resources in the example configurations may be implemented as a combined structure or resource. Similarly, structures and functionality presented as a single resource may be implemented as separate resources. These and other variations, modifications, additions, and improvements fall within a scope of embodiments of the present disclosure as represented by the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Although the invention has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the invention is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present invention contemplates that, to the extent possible, one or more features of any embodiment can be combined with one or more features of any other embodiment.
This application is a continuation of U.S. patent application Ser. No. 17/001,537, filed Aug. 24, 2020, which is a continuation of U.S. patent application Ser. No. 16/035,250, filed Jul. 13, 2018, now U.S. Pat. No. 10,754,820 B2, which claims the benefit under 35 U.S.C. § 119(e) of U.S. Provisional Application Ser. No. 62/545,215, filed Aug. 14, 2017, the content of which is incorporated by reference in its entirety into the present disclosure.
| Number | Date | Country | |
|---|---|---|---|
| 62545215 | Aug 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17001537 | Aug 2020 | US |
| Child | 17737805 | US | |
| Parent | 16035250 | Jul 2018 | US |
| Child | 17001537 | US |
