Patent Application
20220277093
The present technology pertains in general to data visualization and more specifically, to providing spaces configurable for access control for various data analysis, visualization, and exploration.
This summary is provided to introduce a selection of concepts in a simplified form that are further described in the Detailed Description below. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
The present disclosure provides various embodiments of systems and methods for providing spaces (also referred to as workspaces) configurable for various data visualization and analysis. Various embodiments enable the organizing and access controlling of dashboards, visualizations, and other saved data objects into spaces that are containers
An exemplary computer-implemented method includes providing a user interface for enabling the user to select, as a current space, a default space or one of one or more other spaces of a plurality of spaces; and in response to the user selecting the current space, automatically saving new objects generated by the user into the current space; wherein each of the one or more other spaces is organized and configured to provide access to certain data objects only or access to certain applications of a plurality of applications only. In some embodiments, the method further includes, based on at least one role of the user, automatically controlling access to the user to the default space and to the one or more other spaces of a plurality of spaces, such that the only ones of the plurality of spaces that the user can access are the default space and the one or more other spaces.
One of the many advantages of various embodiments of the present technology is that spaces need not be organized by teams, but instead can be organized by common purpose. In addition, access can be controlled to limit a user's access to certain applications. In addition, an example method can automatically generate a default space for a user; and automatically place some or all of the user's saved data objects that existed before the default space was generated, into the default space. In some embodiments, each of the plurality of spaces is independent, such that the saved objects unique to one of the spaces do not appear in any of the other ones of the plurality of spaces. The method can further provide a user interface for selectively deleting a first space of the plurality of spaces, wherein in response to the selectively deleting, the deletion selection is cascaded to all saved objects within the first space.
Embodiments are illustrated by way of example, and not by limitation, in the figures of the accompanying drawings, in which like references indicate similar elements and in which:
While this technology is susceptible of embodiment in many different forms, there is shown in the drawings and will herein be described in detail several specific embodiments with the understanding that the present disclosure is to be considered as an exemplification of the principles of the technology and is not intended to limit the technology to the embodiments illustrated. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the technology. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes,” and/or “including,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that like or analogous elements and/or components, referred to herein, may be identified throughout the drawings with like reference characters. It will be further understood that several of the figures are merely schematic representations of the present technology. As such, some of the components may have been distorted from their actual scale for pictorial clarity.
The present disclosure is related to various embodiments of systems and methods for providing spaces configurable for various data visualization, analysis and exploration.
Each of client application 110A and one or more nodes 1201-120X can be a container, physical computing system, virtual machine, and the like. Generally, client application 110A can run on the same or different physical computing system, virtual machine, container, and the like as each of one or more nodes 1201-120X. Each of one or more nodes 1201-120X can run on the same or different physical computing system, virtual machine, container, and the like as the others of one or more nodes 1201-120X. A physical computing system is described further in relation to the exemplary computer system 1300 of
When client application 110A runs on a different physical server from a node (e.g., of one or more nodes 1201-120X), connections 140 can be a data communications network (e.g., various combinations and permutations of wired and wireless networks such as the Internet, local area networks (LAN), metropolitan area networks (MAN), wide area networks (WAN), and the like using Ethernet, Wi-Fi, cellular networks, and the like). When a node (of one or more nodes 1201-120X) runs on a different physical computing system from another node (of one or more nodes 1201-120X), connections 140 can be a data communications network. Further details regarding the distributed application structure can be found in commonly assigned U.S. patent application Ser. No. 16/047,959, filed Jul. 27, 2018 and incorporated by reference herein.
Having provided the above details of certain concepts of the distributed application structure described above, the description now turns to further detailing aspects of the present technology according to various embodiments.
Although various example embodiments are described herein with respect to KIBANA and other elements of an integration solution called ELASTIC STACK, the present technology is not so limited.
KIBANA provides for data visualization and exploration, for example, for log and time-series data analytics, application monitoring, and other use cases regarding a user's data on its servers, cloud-based services used, etc.
KIBANA can provide a powerful and easy-to-use visual interface with features such as histograms, line graphs, pie charts, sunbursts and the can enable a user to design their own visualization, e.g., leveraging the full aggregation capabilities of the ELASTICSEARCH (a distributed, multitenant-capable full-text analytics and search engine). In that regard, KIBANA can provide tight integration with ELASTICSEARCH for visualizing data stored in ELASTICSEARCH. KIBANA may also leverage the Elastic Maps Service to visualize geospatial data, or get creative and visualize custom location data on a schematic of the user's choosing. Regarding time series data, KIBANA can also perform advanced time series analysis on a company or other user's ELASTICSEARCH data with provide curated time series user interfaces (UI)s. Queries, transformations, and visualizations can be described with powerful, easy-to-learn expressions. Relationships can be analyzed with graph exploration.
With KIBANA, a user may take the relevance capabilities of a search engine, combine them with graph exploration, and uncover the uncommonly common relationships in the user's ELASTICSEARCH data. In addition, KIBANA can enable a user to detect the anomalies hiding in a user's ELASTICSEARCH data and explore the properties that significantly influence them with unsupervised machine learning features. A user could also, e.g., using CANVAS, infuse their style and creativity into presenting the story of their data, including live data, with the logos, colors, and design elements that make their brand unique. This covers just an exemplary subset of the capabilities of KIBANA.
Some embodiments provide for the user to share visualizations and dashboards (e.g., KIBANA or other visualizations and dashboards), with others, e.g., a user's team members, the user's boss, their boss, a user's customers, compliance managers, contractors, while having access controlled.
Various embodiments of the methods and systems of the present technology enable a user to organize their dashboards and visualizations into spaces, e.g., KIBANA spaces. In various embodiments, a user can invite other users into certain spaces (and not others) using role-based access control or attribute-based access control. Spaces can allow users to organize their dashboards, visualizations, and other saved objects into meaningful categories based on team, use case, individual, etc. Using role-based access control, security can be layered in to control who can (and cannot) view and/or edit which space. If an organization has a shared KIBANA instance with hundreds of dashboards and visualizations, for example, spaces can allow the organization to deliver a more organized and secure experience to the end users. Spaces can also be configured to not allow certain applications to be used in the particular space as will be described further herein.
Each space can be a secure container for a user to put in many different saved objects in KIBANA—dashboards, visualizations, saved objects, index patterns (to indicate which search engine indices a user wants to explore), advance settings, timeline expressions, etc. that would normally get bundled into one KIBANA index with access to everyone. These spaces can be isolated into individual containers in the UI. This can allow a user to do any sort of grouping they desire,
When a user logs in, if it is determined that the user's role(s) and/or attribute(s) has access to the particular space, then the method and system can prompt the user with the ability to select that space. In the example in
The particular spaces that a user can select can be determined by an administrator based on the user's roles and/or attributes. If the methods and systems according to various embodiments determine that the user does not have access to a particular space, then that particular space will not be visible or selectable by the user in the UI, e.g., the user will not see it and won't even know the other spaces exist or the existence of saved objects within those other inaccessible spaces.
Each space may be independent in the sense that objects unique to a first space do not appear in a different, second space.
In some embodiments, a dashboard only mode is configurable on a space by space basis. For example, one of the selectable spaces may be configured to provide a dashboard-only mode, where based on the role and/or attributes of a particular user, that particular user may only be given read only access to marketing dashboards and operational dashboards, while other selectable spaces may be configured to provide fuller access.
In various embodiments, many discrete sets of data can be made secure from each other. In an example common use case, it may be desired to have read only access to KIBANA and to also have many discrete sets of data that are secure from each other. To achieve this prior to the present technology, a large number of KIBANA instances would have to be deployed and managed separately which can be burdensome and cumbersome. In various embodiments, the user need not have to do that in order to manage, e.g., discrete data sets, etc.
The ability can be provided to select which space is a default space. For the default space, in response to the user logging in, the system can immediately drop the user into a particular default space. For example, a user on the engineering team, may want to always be logged into the engineering space first and just have the option to switch to the other ones if the user desires.
As described herein, the methods and systems in various embodiments provide the spaces functionality in such a way to enable a user to incrementally begin using spaces for their saved objects, and incrementally add security aspects, described herein. In various embodiments, a user on the search engine platform who is new to the spaces functionality can take advantage of the capability of spaces without any migration or backwards compatibility impediments.
Regarding the default space, the methods and systems in various embodiments will put saved objects that were created before the spaces feature was enabled, into the default space. In various embodiments, the default space is where saved objects that were created before spaces are enabled will go; and where dashboards, visualizations, etc. that are imported via BEATS will be created, until their workflows are augmented to allow the user to choose a space. An optional/space/path if present, is modified and if not present, a default space will be used. For example, uniform resource locators (URLs) for saved objects that were created before the spaces functionality was enabled will work, in various embodiments, as long as the respective saved object continues to exist within the default space. In some embodiments, if the saved object is moved to another workspace, in various embodiments the previous URLs (including short URLs) will no longer work and the user will get an error message.
Further regarding the provided seamless transition default space, in various embodiments, when a user creates a data object in the space, for example a user creates a dashboard within the engineering space, some changes are applied to the underlying data model for that dashboard. The identifier for the space can be stored on the saved object, e.g., the dashboard in this example. All objects in the default space have no identifier, according to various embodiments. The absence of any sort of space identified can then indicate that the saved object actually belongs to the default space. Thus, when a user updates to add the spaces functionality, all of the user's existing saved objects that the user might have previously created are now actually inside this default space that the user can select like any other space. Thus in various embodiments, a user's whole existing installation is essentially the default space which that user can just add on to.
In some embodiments, the URL that the user will see in a browser user interface implementation will also include the unique space identifier for that space in the URL. The URL may further include an identifier for the associated dashboard being accessed. Various embodiments allow the user to choose to take saved objects from a space and add them to a different space, unless access control security may otherwise limit the transfer.
In various embodiments, a user can choose to have access control security, as described herein, for their new spaces, providing an incremental and gradual way to adopt spaces within an organization without having to start over or do some huge migration of their existing data objects, e.g., already in KIBANA.
In another example, if the user was a salesperson and the only space the user had access to was the sales team space, e.g., 306, the salesperson would be brought directly to that space on login.
In some embodiments, the methods and systems enable a user and organization to organize spaces not so much around teams, but instead around a purpose within the company. For example, data around the company's public website if anyone is interested to run that data; data could be around all of the activity for their GitHub repositories, to name a few examples.
Data can be existing saved objects on the platform such as visualizations, dashboards and index patterns (a way to cache configuration details about how one searches for data). Data can also be another type including data ingested into ELASTICSEARCH and are performing search requests against it. This other type of data could be log data, ingesting GitHub activity, to name a few. In various embodiments, a user is not forced to restrict access to their own data of this other type. So, for example, using access control security, various embodiments enable restricting access to dashboards and other saved objects outside the space boundary; and theoretically, a user could simultaneously be given permission in ELASTICSEARCH, for instance, to search all of the user's own data including logs, etc. This means that in various embodiments, the access control for spaces (and saved objects therewithin) is not coupled to access control on the user's own data that the user is ingesting into ELASTICSEARCH and trying to analyze. On the other hand, the role based access control can be configured in such a way that a user only has access to the engineering space and only has access to the data in ELASTICSEARCH that is relevant to the engineering space.
For example, the engineering and security teams might be interested in the same raw log data, but for different reasons (e.g., debugging and security anomaly detection). In various embodiments, a dashboard related to the log data cannot exist in both the engineering space and the security space. Theoretically, there could be two distinct dashboards, however, one in the engineering space and the other in the security space where although the dashboards are distinct saved objects, each dashboard can create the same visualization in two different spaces and each dashboard's query, can make the same request to the search engine. That configuration of dashboards is theoretically possible even though there may not be in some embodiments an explicit sharing mechanism on the underlying dashboard saved object to indicated belonging to multiple spaces.
It should be clear that in various embodiments, the present technology goes far beyond merely having a feature where, for example, the security team gets their own space to put objects into and the sales team gets their own space. Among other things described herein, spaces in various embodiments are not necessarily team specific and instead are inherently flexible enough to be team oriented if the user desires (along with providing all the associated functionality discussed herein) or the spaces can be configured in a totally different and unique way to organize an organization's data. Spaces can be configured according to whatever common thread or purpose binds different individuals or teams. For one of the many examples further described herein, a production website could create their own space for which there could be a dozen teams having access to that space. The security team may want to access the website space because they are using a machine learning application within that space to identify anomalies in traffic to the website, e.g., to prevent denial of service (DOS) attacks, etc. Other teams may be given access to the production website space because they have other specific things they may want to do with that data, to organize for their particular analysis purposes. The sales team might want access to the production website space since they may be interested in knowing which countries get the most traffic on the website, to track like a sales funnel. Other teams may have other use cases for features for the data at the production website space and rather than inefficiently separating those features across several teams, a user could put them all in one space for the production website. Each organization can be different insofar as how it organizes its workflow, and spaces can help enhance people's workflows, e.g., across teams, having commonality in teams, or commonality in purposes, etc.
Certain aspects such as, for example, machine learning (ML), application performance monitoring (APM), other monitoring, and reporting may exist outside of the context of spaces, and continue to use cluster-wide settings and indices. These particular applications may include an indicator signifying that those particular applications are not within a space, so the user is aware that those particular applications are available cluster-wide. In some embodiments, a space may be exposed on a request from an ML application so the ML application can read the objects within that space.
Certain saved objects can exist within a single space. In some embodiments, sharing is not permitted between multiple workspaces.
In some embodiments, in response to a space being deleted, the deletion is cascaded to all saved objects within the space. Additionally, user interface settings can be space specific, and the settings from the default space are copied to the new space when it's created, according to various embodiments. Based on roles and/or attributes, read-only/write access can be granted to different spaces.
In some embodiments, in response to saved objects being exported, e.g., outside the system, the space in which they currently belong is omitted. In response to object being imported, the imported objects may be assigned to the currently selected space.
According to another example, there may be a sales team, an operations team, and a security team. These teams may differ in how they visualize data and in which data they care about, e.g., the sales team may not care about the log data that the operations team is aggregating and the operations team may not have the need for access to sales data. Various embodiments answer the question who can do what and who has access to what set of features and the underlying data models that empower them. For example, an organization may have organizational concerns regarding who can do what and who has access to what set of features and the underlying data models that empower them. Various embodiments can address these organizational concerns.
For a very small number of people in the entire group, access control may not be an issue, but it certainly is where there is a team of people or multiple teams that want to access only certain particular dashboards, access only certain visualizations, and/or access only certain index patterns which describe, for example, how to query and where to query the search engine for data.
Although some examples have been given for teams, some uses are not team oriented. For example, a company or user may want to have a number of different data sets that are all related to their production website. The company is keenly interested in keeping the website up and running, not buggy, etc. All of the data sets pertaining to the production website and all of the dashboards, visualizations, index patterns, CANVAS work pads, etc. may be organized into a workspace. In addition, separate groups may want their own workspaces for their data, separate and apart from other groups. Access control security permissions can be set up to determine who can access what workspaces.
In some embodiments, methods and systems allow the user to customize which applications are available to users, by controlling access on a space by space basis. For example, it can be determined that the sales team should not have access to the CANVAS application at all. This may occur, for example, when it is clear that a particular team's (e.g., the sales team) data is not CANVAS related, and that team should be constrained to a certain set of dashboards, for example, that have been created. In some embodiments, that particular team would not even be given access to the features of certain applications, e.g., CANVAS, to take advantage of when the sales team is within their sales space. This can provide more control and prevent unnecessary or undesirable use of certain applications by certain teams.
A production website is another example, which is not team specific, because there are multiple teams that need access to the data, but if it may not be desired and/or needed for the production website data to take advantage of a code search product. Since in this example, if the code search product is not important for the production website data, then that code search application can be removed entirely from the production website space. As a result, those having access to the production website space cannot use the code search product within that space, according to various embodiments. That way, the application may not be an impediment to the production website data development, and not make the space include unneeded applications that can cause inefficiency or complications since they are not needed and should not be used for that space.
In some embodiments, for security reasons, access control is enforced such that a user cannot circumvent spaces and access a dashboard directly, e.g., at the application programming interface (API) level, that the user cannot access in spaces. In various embodiments, access control would have to give the user access, based on roles and/or attributes for the user, to the space to which the particular dashboard belongs in order for the user to retrieve that dashboard or interact with its data.
The spaces functionality may be at the API level or the user interface level in some embodiments.
In various embodiments, role management provides the ability to apply access control on top of spaces with defined security boundaries around those spaces. An administrator can select which roles would only be able to access the objects that are within a particular space. In various embodiments, underlying methods and systems determine which spaces are presented to a particular user for selection, based, for example, on a user's attributes and/or roles. For example, to view a person's private health information, a number of conditions must be met to include a recent, valid Health Insurance Portability and Accountability Act (HIPAA) training certificate. Since everyone can take the training on different dates, no single role can take into account a person's training status, thus an attribute is reviewed to make the determination of which spaces can be selectable by a particular user, and presented accordingly in according to various embodiments. In addition to role-based access control there can also be attribute-based access control. Further details on attribute-based access control are included in U.S. patent application Ser. No. 16/212,475, filed Dec. 6, 2018. Attributes could include, for example, projects they work on, team memberships, certifications, years of service, and physical location, to name just several possibilities. For a thing (i.e., resource), attributes could be sensitivity level, personally identifying information (PII) status, protected health information (PHI), time-to-live (TTL), or physical location. An attribute, for example, can be having certain specialized training and certification required for accessing certain data. Since everyone can take the training on different dates, no single role can take into account a person's training status. In addition to HIPAA, other security policies may be involved for financial or other sensitive information.
Referring back to
In various embodiments, a user can delete a space if the user has sufficient privileges.
As discussed herein, a user can move saved objects from one space to another via import/export, if the user has sufficient access.
In some embodiments, the methods and systems enable a user to secure access to spaces, as described further herein. A user may control which roles have access to each space. In other embodiments, the user may control which roles or which attributes have the access. Access to spaces may be governed by a concept called “minimum privilege” with three provided options. In some embodiments, for an “all” minimum privilege setting, users will have read/write access to all spaces (in the platform such as KIBANA, etc.) Additionally, this privilege can enable the user to be able to create, edit, and delete any space, and this can extend to spaces created in the future. In some embodiments, for a “read” minimum privilege setting, users will have read-only access to all spaces, which privilege extends to spaces created in the future. Another minimum privilege can be “none” which indicates that the user cannot access any space. In some embodiments, once a minimum privilege is set, a user can customize access to specific spaces.
Operation 1202 includes based on at least one role of the user, automatically controlling the user's access to a default space and to other spaces of a plurality of spaces, such that the only spaces that the user can access are the default space and the one or more other spaces, each space containing a number of saved objects. The saved object may be dashboards, visualizations, or other objects, as described further herein
Operation 1204 includes providing a user interface for enabling the user to select, as a current space, the default space or one of the one or more other spaces, as described further herein.
Operation 1206 includes, in response to the user selecting the current space, automatically saving new objects generated by the user into the current space, as described further herein.
Operation 1208 includes, wherein each of the one or more other spaces is organized and configured to provide access to certain data objects only or access to certain applications of a plurality of applications only.
The components shown in
Mass data storage 1330, which can be implemented with a magnetic disk drive, solid state drive, or an optical disk drive, is a non-volatile storage device for storing data and instructions for use by processor unit(s) 1310. Mass data storage 1330 stores the system software for implementing embodiments of the present disclosure for purposes of loading that software into main memory 1320.
Portable storage device 1340 operates in conjunction with a portable non-volatile storage medium, such as a flash drive, floppy disk, compact disk, digital video disc, or Universal Serial Bus (USB) storage device, to input and output data and code to and from the computer system 1300 in
User input devices 1360 can provide a portion of a user interface. User input devices 1360 may include one or more microphones, an alphanumeric keypad, such as a keyboard, for inputting alphanumeric and other information, or a pointing device, such as a mouse, a trackball, stylus, or cursor direction keys. User input devices 1360 can also include a touchscreen. Additionally, the computer system 1300 as shown in
Graphics display system 1370 include a liquid crystal display (LCD) or other suitable display device. Graphics display system 1370 is configurable to receive textual and graphical information and processes the information for output to the display device. Peripheral device(s) 1380 may include any type of computer support device to add additional functionality to the computer system.
Some of the components provided in the computer system 1300 in
Some of the above-described functions may be composed of instructions that are stored on storage media (e.g., computer-readable medium). The instructions may be retrieved and executed by the processor. Some examples of storage media are memory devices, tapes, disks, and the like. The instructions are operational when executed by the processor to direct the processor to operate in accord with the technology. Those skilled in the art are familiar with instructions, processor(s), and storage media.
In some embodiments, the computing system 1300 may be implemented as a cloud-based computing environment, such as a virtual machine operating within a computing cloud. In other embodiments, the computing system 1300 may itself include a cloud-based computing environment, where the functionalities of the computing system 1300 are executed in a distributed fashion. Thus, the computing system 1300, when configured as a computing cloud, may include pluralities of computing devices in various forms, as will be described in greater detail below.
In general, a cloud-based computing environment is a resource that typically combines the computational power of a large grouping of processors (such as within web servers) and/or that combines the storage capacity of a large grouping of computer memories or storage devices. Systems that provide cloud-based resources may be utilized exclusively by their owners or such systems may be accessible to outside users who deploy applications within the computing infrastructure to obtain the benefit of large computational or storage resources.
The cloud is formed, for example, by a network of web servers that comprise a plurality of computing devices, such as the computing system 1300, with each server (or at least a plurality thereof) providing processor and/or storage resources. These servers manage workloads provided by multiple users (e.g., cloud resource customers or other users). Typically, each user places workload demands upon the cloud that vary in real-time, sometimes dramatically. The nature and extent of these variations typically depends on the type of business associated with the user.
It is noteworthy that any hardware platform suitable for performing the processing described herein is suitable for use with the technology. The terms “computer-readable storage medium” and “computer-readable storage media” as used herein refer to any medium or media that participate in providing instructions to a CPU for execution. Such media can take many forms, including, but not limited to, non-volatile media, volatile media and transmission media. Non-volatile media include, e.g., optical, magnetic, and solid-state disks, such as a fixed disk. Volatile media include dynamic memory, such as system random-access memory (RAM). Transmission media include coaxial cables, copper wire and fiber optics, among others, including the wires that comprise one embodiment of a bus. Transmission media can also take the form of acoustic or light waves, such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media include, e.g., a floppy disk, a flexible disk, a hard disk, magnetic tape, any other magnetic medium, a CD-ROM disk, digital video disk (DVD), any other optical medium, any other physical medium with patterns of marks or holes, a RAM, a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a Flash memory, any other memory chip or data exchange adapter, a carrier wave, or any other medium from which a computer can read.
Various forms of computer-readable media may be involved in carrying one or more sequences of one or more instructions to a CPU for execution. A bus carries the data to system RAM, from which a CPU retrieves and executes the instructions. The instructions received by system RAM can optionally be stored on a fixed disk either before or after execution by a CPU.
Computer program code for carrying out operations for aspects of the present technology may be written in any combination of one or more programming languages, including an object oriented programming language such as JAVASCRIPT, JAVA, SMALLTALK, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (e.g., through the Internet using an Internet Service Provider).
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present technology has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. Exemplary embodiments were chosen and described in order to best explain the principles of the present technology and its practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
Aspects of the present technology are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present technology. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The description of the present technology has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. Exemplary embodiments were chosen and described in order to best explain the principles of the present technology and its practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
The present application is a continuation of U.S. patent application Ser. No. 16/226,138, filed Dec. 19, 2018, entitled “Methods and Systems for Access Controlled Spaces for Data Analytics and Visualization,” which is hereby incorporated herein by reference in its entirety, including all references and appendices cited therein, for all purposes, as if fully set forth herein.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16226138 | Dec 2018 | US |
| Child | 17748964 | US |
