Data Visualization Objects in Virtual Environments

The method addresses the limitations of traditional data visualization by using a 3D line graph with movable cameras and interactive visualization components to enhance understanding of complex data sets, particularly time-series data, through immersive virtual environments.

JP7580373B2Active Publication Date: 2024-11-11ORACLE INT CORP
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2021521460
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2018-10-21
Filing Date
2019-10-21
Publication Date
2024-11-11
Estimated Expiration
2039-10-21

AI Technical Summary

Technical Problem

Existing data visualization techniques, particularly for complex multidimensional data, often fail to effectively highlight and emphasize key aspects of data collection, making it difficult to gain a complete understanding of the underlying information.

Method used

A method for visualizing time-series data in an interactive virtual environment using a 3D line graph with movable virtual cameras, allowing for dynamic views and interactions through client devices, and enabling the use of visualization components that can be bound to enterprise data sets for immersive data exploration.

Benefits of technology

Enables intuitive and interactive data visualization in a 3D virtual environment, allowing users to manipulate and understand complex data sets through immersive interactions, enhancing the comprehension of time-dependent data patterns.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007580373000001
    Figure 0007580373000001
  • Figure 0007580373000002
    Figure 0007580373000002
  • Figure 0007580373000003
    Figure 0007580373000003
Patent Text Reader

Abstract

Multiple visualization objects may be provided to represent one or more datasets in a virtual 3D space. Visualization objects may include funnels, containers, name cards, etc. The visualization objects may be arranged in a circular carousel that can rotate around a virtual camera or user's position in the VR / AR environment. Individual data points within a visualization object may be rotated, sized, positioned, colored, or otherwise characterized based on attributes of the corresponding data point. Individual data points may also be animated as transitions between visualization objects in a unified view. Voice commands may be interpreted as part of an interactive environment that can provide views of visualization objects to multiple devices simultaneously.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application is a nonprovisional application of U.S. Provisional Application No. 62 / 748,504, filed on October 21, 2018, entitled "3D VISUALIZATION SERVICES INTEGRATING VARIOUS DATA SOURCES AND DISPLAY DEVICES," which claims the benefit of and priority under 35 U.S.C. § 119(e), and is hereby incorporated by reference in its entirety for all purposes.

[0002] This application is also related to the following four U.S. patent applications: No. 16 / 658,162, entitled “INTERACTIVE DATA EXPLORER AND 3-D DASHBOARD ENVIRONMENT,” by Moroze et al., filed on October 21, 2019 (Attorney Docket No. 088325-1142774), which is incorporated by reference in its entirety. No. 16 / 658,165, entitled “FUNNEL VISUALIZATION WITH DATA POINT ANIMATIONS AND PATHWAYS,” by Moroze et al., filed on October 21, 2019 (Attorney Docket No. 088325-1142775), which is incorporated by reference in its entirety. No. 16 / 658,169, entitled “OPTIMIZING VIRTUAL DATA VIEWS USING VOICE COMMANDS AND DEFINED PERSPECTIVES,” filed on October 21, 2019 by Moroze et al. (Attorney Docket No. 088325-1142776), which is incorporated herein by reference in its entirety. No. 16 / 658,177, entitled “ANIMATION BETWEEN VISUALIZATION OBJECTS IN A VIRTUAL DASHBOARD,” filed on October 21, 2019 by Moroze et al. (Attorney Docket No. 088325-1142782), which is incorporated by reference in its entirety. [Background technology]

[0003] background One of the most effective ways to communicate information is through visualization. Capturing and categorizing information is typically not enough to gain a full understanding of the conclusions that can be drawn from the data. Two-dimensional data visualization dominates many of our communication techniques, but many of these visualization techniques are not optimized for highlighting or emphasizing aspects of the data collection. Effective data visualization involves creating informative, visually appealing representations that communicate aspects of the data very quickly. Sometimes, a simple visualization is sufficient. However, with complex, multi-dimensional data, the complexity of the dataset itself can make proper visualization difficult and limit the dimensional space. Summary of the Invention [Means for solving the problem]

[0004] overview A method for visualizing time series data in an interactive virtual environment may include receiving one or more datasets including a plurality of time series sequences of data points, plotting each of the plurality of time series sequences of data points on a three-dimensional (3D) line graph in a virtual environment, generating one or more views of the 3D line graph with one or more virtual cameras configured to move around the 3D line graph in the virtual environment, and transmitting the one or more views of the 3D line graph to one or more client devices, which may correspond to the one or more virtual cameras.

[0005] A non-transitory computer-readable medium may comprise instructions that, when executed by one or more processors, cause the one or more processors to perform operations that may include receiving one or more data sets including a plurality of time series sequences of data points, plotting each of the plurality of time series sequences of data points on a three-dimensional (3D) line graph in a virtual environment, generating one or more views of the 3D line graph with one or more virtual cameras configured to move around the 3D line graph in the virtual environment, and transmitting the one or more views of the 3D line graph to one or more client devices, which may correspond to the one or more virtual cameras.

[0006] The system may comprise one or more processors and one or more memory devices comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform operations, the operations may include receiving one or more data sets including a plurality of time series sequences of data points, plotting each of the plurality of time series sequences of data points on a three-dimensional (3D) line graph in a virtual environment, generating one or more views of the 3D line graph using one or more virtual cameras configured to move around the 3D line graph in the virtual environment, and transmitting the one or more views of the 3D line graph to one or more client devices, which may correspond to the one or more virtual cameras.

[0007] In any embodiment, any of the following features may be implemented in any combination, without limitation: Plotting each of the plurality of time series sequences of data points on a 3D line graph in a virtual environment may include plotting a position of each data point in the plurality of time series sequences of data points in a coordinate system of the virtual environment and connecting each of the positions with a 3D line object. The method / operation may also further include transforming a coordinate system of the 3D line graph to the coordinate system of the virtual environment. The coordinate system of the 3D line graph may include a first horizontal axis corresponding to time, a second horizontal axis corresponding to an index in the plurality of time series sequences of data points, and a vertical axis corresponding to a value of the data point. The one or more data sets may include test failure data over time for different systems. The method / operation may also include loading a visualization component with parameterized inputs, binding the one or more data sets to the parameterized inputs, and plotting each of the plurality of time series sequences of data points on the 3D line graph in the virtual environment according to the visualization component. A client device in the one or more client devices may include a virtual reality device.

[0008] BRIEF DESCRIPTION OF THE DRAWINGS A further understanding of the nature and advantages of the present invention may be realized by reference to the remaining portions of the specification and drawings, in which like reference numerals are used to refer to like components throughout the several views. In some cases, a sub-label is associated with a reference numeral to indicate one of multiple similar components. When referring to a reference numeral without specification to an existing sub-label, it is intended to refer to all such multiple similar components. [Brief description of the drawings]

[0009] [Figure 1]1 illustrates a system for authoring, providing, and using an interactive data display, according to some embodiments. [Diagram 2] 1 illustrates an example of a virtual object bound to an enterprise dataset, according to some embodiments. [Diagram 3] FIG. 2 illustrates a user interface for importing a component from a component exchange into an application. [Figure 4] 1 illustrates a block diagram of a process for downloading and instantiating components in an application according to some embodiments. [Diagram 5] 1 illustrates a virtual dashboard created in a virtual environment, according to some embodiments. [Figure 6] 1 illustrates how various types of client device systems and input devices can all simultaneously interface with the same virtual environment in the EDIE environment, according to some embodiments. [Figure 7] 1 illustrates a view of a virtual environment through a 2D screen interface, according to some embodiments. [Figure 8] 1 illustrates a view of a virtual environment in which multiple users interact with a virtual dashboard, according to some embodiments. [Figure 9] 1 illustrates a view of a real-world environment that may be used to interact with a virtual environment, according to some embodiments. [Figure 10] 1 illustrates a flowchart of a method for displaying data in a multidimensional dashboard, according to some embodiments. [Figure 11] 1 illustrates a diagram of a visualization component for displaying a time series sequence of data points in a virtual environment, according to some embodiments. [Figure 12] 12 illustrates a view of a line graph object from a different perspective than FIG. 11 according to some embodiments. [Figure 13]1 illustrates a line graph object being rendered by a virtual environment in accordance with some embodiments. [Figure 14] 1 illustrates how a user can interact with data in a virtual environment, according to some embodiments. [Figure 15] 13 illustrates a circular bar chart component that can be used to visualize the same data bound to the line chart component, according to some embodiments. [Figure 16] 1 illustrates a pie chart that operates similarly to a line chart, according to some embodiments. [Figure 17] 1 illustrates a flowchart of a method for visualizing time series data in an interactive virtual environment, according to some embodiments. [Figure 18] 1 is a simplified diagram of a distributed system for implementing some of the embodiments; [Figure 19] FIG. 1 is a simplified block diagram of one or more components of a system environment in which services provided by one or more components of an embodiment system may be offered as cloud services, according to some embodiments. [Figure 20] FIG. 1 illustrates an example computer system upon which various embodiments may be implemented. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Detailed Description Described herein are embodiments for immersive user interface (EGI) experiences. The immersive user interface experiences may be wrapped as individual components that application or service developers can insert into a component exchange or clearinghouse that can then be used to add interactive EGI components to their applications or services. These EGI components can be used to provide user-friendly, interactive, immersive experiences that differentiate applications in a crowded marketplace and provide detailed and intuitive data visualizations for many different data types on many different user devices.

[0011] FIG. 1 illustrates a system for authoring, providing, and using interactive data displays, according to some embodiments. The system may include a component exchange 124. The component exchange 124 may be part of an application development suite that allows a user to develop applications and / or services using a custom development environment and a library of predefined tools and / or interfaces. The application development suite may be a cloud-hosted development environment that may be accessible as a Software as a Service (SaaS) model for many different client devices. The development environment may be configured to develop and / or deploy many different types of applications, including cloud-based services or microservices, web applications, mobile device applications, enterprise applications, and the like. Applications designed in the application development suite may be integrated with other SaaS applications via a representational state transfer (REST) ​​interface.

[0012] The development environment in an application development suite may include several user-friendly tools that may be used by developers to streamline the development process and make the overall application development cycle more efficient. These tools may include WYSIWYG tools and other graphical interfaces that allow developers to drag and drop various pre-packaged components into the application development space. Various components may be provided by the development environment, such as reusable business objects, processes, web controls, user interface controls, themes, templates, and other aspects of the application.

[0013] Developers can use the development environment to design and test applications, which can then be deployed to various operating environments. When the application is deployed to an operating environment, the development environment can also deploy any additional code or libraries required by the application so that the application can run in the target environment. Thus, the flexibility and reusable components provided by the development environment can be ported to any operating environment without losing any of the functionality provided by the development environment.

[0014] In this example, the development environment can include a component exchange. For example, the development environment can be implemented using any commercially available development environment, such as Visual Builder® from Oracle®. The development environment can include various toolkits, such as a collection of proprietary and / or open source JavaScript libraries that can be used to build applications. For example, the development environment can include components from the JavaScript Extension Toolkit (JET)® from Oracle®. The components in these toolkits can include a rich set of user interface (UI) components, including data models, view models, and ports for binding data to the components. In some embodiments, the development environment can provide a unified component plug-in mechanism based on standard components, such as the W3C Web Components standard, but still allow custom components to work together with standard components.

[0015] The component exchange 124 may allow component developers to upload components to the component exchange 124 for use by application developers. This allows component developers to provide a flexible component architecture that can be maintained and upgraded throughout the component lifecycle. For example, these components may include standard web components such as a checkbox component 116 or a slider component 114 that may be used in various user interfaces. These components 114, 116 may be uploaded to the component exchange 124 and then updated and maintained throughout their lifecycle by the component development team. They may then be provided as components 121, 122 in the component exchange 124 for application developers.

[0016] In addition to standard web components, the embodiments described herein allow users to develop special visualization objects that can be used in an Enterprise Data Interactive Explorer (EDIE) environment. These visualization objects provide a multidimensional view of an enterprise data set that can be viewed simultaneously by multiple client devices through separate network connections. These visualization objects can be imported into the component exchange 124 in the same way that standard web components are imported into the component exchange 124. These visualization objects can then be imported into individual applications under development. In these applications, developers can bind various enterprise data sets from any number of different sources to parameterized inputs on the visualization objects. The visualization objects can then be used to generate rendered views of virtual objects that represent and visualize the enterprise data in a multidimensional environment.

[0017] Various examples of these visualization objects may be described in more detail below in this disclosure. FIG. 1 illustrates some examples of visualization objects that may be imported into the component exchange 124 as regular objects. For example, the funnel object 112 may include a rotating funnel object that shows the progression of data points in an enterprise dataset over time. Various visual effects may be provided with the funnel object 112 that may be used to highlight various aspects of the dataset bound to the funnel object 112. For example, a user may explore the dataset along various dimensions, modify individual data points, view data point paths over time, view visual representations of the data as it accelerates over time along various dimensions, etc.

[0018] FIG. 1 also illustrates a three-dimensional histogram or bar graph object 110 that may be used to represent various enterprise data sets. In the component exchange 124, the graph object 110 may not be connected from any underlying dataset. However, when imported into a real application, the graph object 110 may be bound to an enterprise dataset and various bars in the graph may be resized based on the data binding. The visualization objects may be used to generate three-dimensional (3D) virtual objects that can be viewed by various client devices in a virtual environment. For example, the graph object 110 may be realized as multiple three-dimensional cylinders, each representing a bar in the graph. A user may enter the virtual environment, walk around the virtual objects, interact with the objects, change values ​​in the objects, manipulate portions of the objects, and have the changed values ​​viewed by other users and saved to an underlying database that stores the dataset.

[0019] The visualization objects 110, 112 described above are provided as examples and are not intended to be limiting. Any multidimensional object that can be used to visualize an enterprise data set may be used as a visualization object in this disclosure. Other visualization objects may include charts, animations, pictures, graphs, etc.

[0020] In the component exchange 124, the visualization objects may be represented as components 118, 120 that can be selected by a developer and imported into an application during development. For example, a developer may drag and drop the component 118 for a funnel object 112 into the application. This visualization object can then be bound to a dataset in either the development environment or the deployment environment, depending on the embodiment.

[0021] In some embodiments, an application including one or more visualization objects may be deployed to various environments. These environments may include web applications, mobile applications, client-side applications, applications running on gaming systems, applications running on desktop or laptop computers, applications for virtual environments such as virtual reality or augmented reality systems, and / or any other computing environment. Once the application is deployed to an environment, the component exchange 124 may deploy any required libraries, third-party libraries, or other software components or libraries required to run the visualization objects. For example, some visualization objects that operate in a 3D environment may include OpenGL libraries or other 3D visualization libraries required for their operation.

[0022] Applications can be deployed in an environment 102, collectively referred to herein as the EDIE environment, which can include several standard components along with one or more visualization objects as described above. The environment 102 can include a virtual environment 104 in which the visualization objects can be instantiated. When the visualization objects are instantiated, they can be bound to one or more underlying datasets. These datasets can be obtained from a variety of sources, such as database tables, multidimensional data cubes, web services, server-side applications, API interfaces, etc. In the example of FIG. 1, a corporate database 108 can provide values ​​from one or more database tables to the environment 102 for use with at least one of the visualization objects. In this example, a funnel object 112 can be deployed in the environment 102, within the virtual environment 104. The funnel object 112 can include a set of inputs, such as parameterized inputs, that can be individually and / or collectively bound to tables or rows in a corporate dataset from the corporate database 108. The bindings 106 between dataset values ​​and parameterized inputs of visualization objects may be created in the development environment, in the deployment environment 102, and / or at any other time. The bindings 106 may also be dynamically adjusted or modified with different datasets at run time or prior to running the application.

[0023] Once a dataset is bound to a visualization object, the visualization object may be used to generate a virtual object in the virtual environment 104. This may include using values ​​from the dataset to size or dimension various portions of the virtual object. Values ​​from the dataset may also be used to generate animation speeds or motion vectors for objects within the virtual object. Values ​​from the dataset may also be used to color or otherwise affect the visual representation of objects in the virtual object. For example, data points may rotate around a virtual funnel generated by the funnel object 112. The data points may have a color determined by one dimension, a size or radius determined by a second dimension, a rotation speed determined by a third dimension, a trajectory or motion vector direction determined by a fourth dimension, etc.

[0024] The visualization objects generated in the virtual environment 104 may be viewed and / or interacted with by a number of different client devices 126, 128, 130, 132. These client devices may include laptop computers, desktop computers, workstations, tablet computers, smartphones, smart watches, smart TVs, video game consoles, digital home assistants, smart glasses, virtual reality headsets, augmented reality headsets, and any other computing devices. Each of these client devices 126, 128, 130, 132 may receive a unique view into the virtual environment 104, corresponding to a uniquely positioned virtual camera for each client device 126, 128, 130, 132. Users may then interact with the virtual objects 105 within the virtual environment 104 to view, manipulate, edit, and / or update the underlying data set with the virtual objects 105. As described below, each user may be provided with a unique, specific view of the virtual objects 105, and with different settings, the user may modify the underlying data, causing the virtual objects 105 to change in the view provided to the other client devices. Automatic hardware detection may be used at each client device 126, 128, 130, 132 to provide the correct view of the virtual environment 104. For example, if client device 126 is implemented by a desktop computer, the environment 102 may provide a two-dimensional (2D) view of the virtual environment 104. In contrast, if client device 128 is implemented by a virtual reality headset, the environment 102 may provide a 3D view of the virtual environment 104 to allow a user of client device 128 to be immersed in and interact within the virtual environment 104.

[0025] 2 illustrates an example of a virtual object 202 bound to an enterprise dataset, according to some embodiments. As described above, the virtual object 202 may correspond to the funnel object 112 uploaded as a component 118 in the component exchange 124 of FIG. 1. The virtual object 202 may include a 3D funnel object, where the funnel is formed by a number of individual data points. The individual data points from the dataset may be used to define the position, color, trajectory, movement, speed, size, shape, and / or any other visual characteristics of each of the individual data points.

[0026] The underlying data set may be sourced from a database table, a multi-dimensional data cube, and / or any other data structure. The data set may include data points represented by rows in a database table, or points in a multi-dimensional data cube. Individual columns in the database or dimensions in the data cube may be used to define the properties of each of the spheres in the virtual object 202. For example, a first dimension or a first column in the database may be used to determine the size or circumference of each sphere. A second dimension or column value may be used to define a color or texture that is applied to each of the spheres in the virtual environment. A third dimension or column value may be used to define the position of each sphere in the funnel. A fourth dimension or column value may be used to define the speed at which the spheres rotate around the central axis of the funnel. A fifth dimension or column value may be used to define a trajectory or path of motion as it moves through various levels of the funnel, etc.

[0027] The data may remain bound to each of the elements of the virtual object 202 as the application is executed. For example, while wearing a virtual reality headset, a user may approach the virtual object 202 in the virtual environment 200. Using a virtual selection handheld device, the user may reach out and "grab" one of the spheres 204 that rotate around the funnel axis. The user may invoke a user interface that displays additional information about the underlying data represented by the sphere 204. The user may change values ​​in the user interface to change the underlying values ​​in the corresponding database. The user may also "place" the sphere 204 back at a location within the virtual object 202. If the new position of the sphere 204 differs from the old position, the dimensions used to determine the position of the sphere 204 in the virtual object 202 may be updated in the underlying database.

[0028] 3 illustrates a user interface 300 for importing components from a component exchange into an application. The user interface 300 may include a list 302 of available components that may be imported into a project. By selecting one of the components in the list 302, the component exchange may display additional information for downloading, instantiating, and / or using the component. In this example, the user has selected the aforementioned funnel object component. Once this selection is made from the list 302, the right side of the interface 300 may display additional information for using the funnel object component.

[0029] The additional information may include a description 306 of the component. This description 306 may describe the operation of the component, how the component may be used, how the component may interact with other components, typical usage scenarios, tips and advice for using the component, and / or other information that may be useful to new and / or experienced users of the component. The description 306 may be accompanied by example code 308 that shows how the component may be integrated into the code of an application. The example code 308 may be provided in a variety of programming languages ​​and may be copied and pasted from the example code 308 into the code of the application.

[0030] In addition, some embodiments may provide an install button 304. The install button may execute a process for installing the component into the user's application. Selection of the install button 304 may launch additional windows, wizards, and / or interfaces that walk the user through the process of installing the component into the application. For example, the install button 304 may trigger one or more web forms to be generated that allow the user to select a data set that may be bound to the parameterized interface of the component. For example, the install button 304 may generate an interface that allows the user to bind spheres in a funnel object to individual columns in a database. The install button 304 may also automatically download any code required to operate the component. This code may include third party databases, graphic libraries, function libraries, and / or other shared code that may be required to perform operations provided by the component.

[0031] FIG. 4 shows a block diagram for a process of downloading and instantiating components in an application, according to some embodiments. Using the user interface described above in FIG. 3, a user can select a funnel object 402 to use as part of an application under development. Code for the funnel object 402 can be downloaded to an operating environment on a client device configured to utilize this type of component. For example, the funnel object 402 can be downloaded to an EDIE environment 102 running on any of the client devices described above. The EDIE environment 102 can include a virtual environment 104 that can provide an environment in which three-dimensional (3D) components can be instantiated for both two-dimensional (2D) and 3D viewing.

[0032] In addition to downloading the code for the funnel object 402, the component exchange 124 may also provide any additional code necessary for the component to run in the EDIE environment 102. This additional code may be stored in a code library 404 that is stored and made available by the component exchange 124. The additional code may also include libraries 406 from third parties that are not hosted and / or provided by the component exchange 124. For example, the component exchange 124 may cause a library of graphic manipulation code to be downloaded from a third party website as part of the installation process for the funnel object 402. All of this code may be downloaded into the EDIE environment 102 to enable the funnel object 402, with all of its required functionality, to be manipulated in an independent manner.

[0033] When the funnel object 402 is downloaded to the EDIE environment 102 and instantiated in the virtual environment 104, the EDIE environment 102 can create bindings between the parameterized inputs of the funnel object 104 and one or more data sources. For example, the EDIE environment 102 can present a user interface to the user to allow the user to select from one of multiple available data sources. The selection of a data source may require the user to bind individual fields in the data source to individual parameterized inputs. For example, the user can select a particular column in a database such that values ​​in that column determine the color that corresponds to a sphere in the funnel object in the virtual environment 104. The bindings between the parameterized inputs and the individual data sources can be stored as part of the application such that whenever the application is launched by the user, the funnel object 402 retrieves data from the underlying data sources and generates a display of the funnel object in the virtual environment 104. This binding can be dynamically updated and / or changed when the application is launched or as the application runs to visualize different data sets in the virtual environment 104.

[0034] The example of FIG. 4 illustrates an enterprise data store 108 that may be used to bind enterprise data to parameterized inputs of various visualization objects. In other examples, different data sources may be bound to different aspects of a visualization object. For example, some embodiments may allow binding columns or fields from multiple databases and multiple locations to parameterized inputs of the same virtualization object. Some embodiments may use online data sources that provide real-time data to visualization components. Based on the requirements of an individual application designer, any combination of data sources may be provided to the parameterized inputs of a virtualization object.

[0035] The use of the funnel object 402 in Figures 3-4 is provided by way of example only and is not intended to be limiting. It will be appreciated that any visualization object designed to operate in the EDIE environment 102 may be implemented in the EDIE environment 102 using a similar procedure.

[0036] FIG. 5 illustrates a virtual dashboard created in the virtual environment 104 according to some embodiments. The visualization components described herein may be used in any type of application, but may be particularly well suited for designing virtual dashboards. As used herein, the term dashboard may include visualizations that aggregate, analyze, and / or display information from one or more data sources in a user interface. A dashboard may be provided on a home page of an organization's website. A dashboard may also be displayed as an entry screen in an application or mobile app. A dashboard generally displays "widgets" or other graphical representations of data in a two-dimensional environment. A user can often select individual widgets on a dashboard to display additional information. For example, a user may click on a widget that displays summary sales information for the current month. The widgets may be configured to provide additional information regarding the summary sales information displayed on the dashboard. Some dashboards may include multiple widgets that may be configured to display up-to-date information from the underlying data sources when the dashboard is visited by various user client devices.

[0037] The embodiments described herein use the visualization components described above to realize a dashboard in a 3D virtual environment 104. For example, instead of displaying 2D widgets on a computer screen, a user can use a client device that is enabled for interaction with the 3D virtual environment and provides a 3D visualization experience for viewing and manipulating the dashboard data. Some embodiments can use a virtual reality headset or an augmented reality device that allows a user to enter the virtual environment 104 and perform live interactions with the visualization objects that display the dashboard data. In the virtual environment 104, a user can walk around the visualization objects, "grab" and manipulate parts of the visualization objects, interact with other users, and have the manipulation of the visualization objects update the underlying data sources. This changes the traditional 2D dashboard experience to an interactive, immersive virtual reality experience where data can be viewed in an interactive, live manner.

[0038] The virtual environment may include multiple visualization objects. Instead of multiple 2D widgets, the 3D dashboard may include visualization objects that are placed in the virtual 3D environment 104. When a user enters or views the 3D virtual environment, the user can move around the virtualized objects, view them from any angle, and manipulate them from any position. Additional examples of user interactions with the virtual environment 104 to interact with visualization objects are described in more detail below.

[0039] As mentioned above, a visualization object may refer to a software object represented by a body of code and / or its associated libraries. What is displayed in the virtual environment 104 may be referred to as a view of the visualization object. Each visualization object may be associated with several different views, and each view may provide a different look and feel for the visualization object. For example, a funnel object may include a traditional business view that displays data in a more specified manner appropriate for a business environment. A funnel object may also include additional views that display data in a less formal manner, including brighter, more vibrant colors, more playful shapes, and / or other variations on how to view the funnel object. For simplicity, the remainder of this disclosure does not distinguish between the underlying visualization object represented by executable code and the view of the visualization object displayed in the virtual environment 104. Instead, a visualization object (e.g., a funnel object) may be uniformly referred to as a visualization object to encompass both code and display in the virtual environment 104.

[0040] In this example, the virtual environment 104 may include a dashboard with three visualization objects. The funnel object 508 may be linked to the enterprise data store 502 described above. The graph object 510 may be linked to a multi-dimensional data cube 504, with the dimensions of the data cube being bound to the individual elements of the graph object 510. The personnel object 512 may include an overview representation of individuals in a three-dimensional grid in the virtual environment 104 (e.g., similar to a virtual business card display). The personnel object may be bound to a web service 506 such that the personnel object can download information from the web service 504 and populate the individual overview representations with individual items. These visualization objects may be rendered in various locations (e.g., a semicircle) within the virtual environment 104. When the user enters the virtual environment 104, the user may see the visualization objects 508, 510, 512 as objects in the area in front of the user. To begin using the virtual dashboard, a user can approach a visualization object 508, 510, 512, view the visualization object, and / or manipulate elements of the visualization object as desired.

[0041] FIG. 6 illustrates how various types of client device systems and input devices can all interface with the same virtual environment simultaneously in the EDIE environment 102, according to some embodiments. The EDIE environment 102 can include a 3D data exploration platform that serves several different purposes and provides several different benefits. For example, the EDIE environment 102 can serve as a nexus for integration between important and converging new technologies that can make the exploration of enterprise data more immersive and fluid. These technologies can include conversational UI (e.g., voice-based or chat-based) 610, virtual reality (VR) 608, augmented reality (AR) 604, and many other interactive technologies. Users can also access these visualization technologies with traditional 2D computing tools, such as apps on a mobile device 606, a web browser 612 on a display screen, etc. The EDIE environment 102 can provide visualizations that shift seamlessly through transitions between devices. For example, a user can view a 3D visualization in a 2D environment, such as on the screen of a mobile device 606. The user may then don a pair of virtual reality goggles and transition into a virtual reality space containing visualized objects displayed in a 2D manner on the screen of the mobile device 606. In the virtual environment, the user can interact with the visualized objects using hand controllers that are typically included in VR systems as described below.

[0042] The EDIE environment 102 may include a hardware detection process 620 that detects the type of user input device used by the client device. For example, if the client device uses a traditional 2D display screen with a web browser 612, the hardware detection process 620 may detect that the 2D environment is interfacing with the virtual environment 104. The EDIE environment 102 may include interface code for each of these different types of input devices shown in FIG. 6. The hardware detection process 620 may identify the various input options available and load the interface code into the EDIE environment 102 accordingly. The interface code may then generate a view of the virtual environment 104 that is compatible with the corresponding input device on the client device.

[0043] As described in more detail below, the EDIE environment 102 may operate in a networked mode such that the virtual environment 104 may be accessed by multiple different client devices simultaneously. This allows users to interact with each other in the virtual environment 104 while viewing visualization objects bound to the underlying enterprise data. The hardware detection module 620 allows users to interact together in the virtual environment 104 based on their visual experience on their client devices. For example, a user who enters the virtual environment 104 using a virtual reality device 608 may be visible in the virtual environment 104 as a displayed avatar for another user who views the virtual environment 104 from a 2D screen interface of a web browser 612.

[0044] 7 illustrates a view of the virtual environment 104 through a 2D screen interface, according to some embodiments. A user 702 may access the EDIE environment 102 through a desktop computer, laptop computer, or other computing device with a 2D screen interface. When viewing the virtual environment 104 on the 2D screen 704, a virtual camera may be placed in the virtual environment 104 and a view of the virtual environment 104 may be rendered from the perspective of the virtual camera. The rendered image may be displayed on a screen 704 for the user 702. The user may interact with various objects in the virtual environment 104 using a mouse or touch screen as the objects are displayed on the screen 704.

[0045] The virtual environment may include multiple visualization objects arranged on the dashboard display as described above. These visualization objects may include funnel object 508, graph object 510, and / or any other visualization object. Additionally, the images captured by the virtual cameras and displayed on screen 704 may include the locations of other users in the virtual environment. Each user's view may be captured by a corresponding virtual camera in virtual environment 104. Instead of displaying virtual cameras, these camera locations may include the display of avatars or other representations of the other users. An example of this includes the visualization of user 708 in virtual environment 104. User 702 can interact and communicate with user 708 through virtual environment 104 as if both were within virtual environment 104. When user 708 points their virtual camera at user 702's virtual camera, they can see a corresponding visualization or avatar representing user 702 in virtual environment 104.

[0046] As described above, the EDIE environment 102 can automatically determine that the screen 704 should display a 2D view of the virtual environment 104. The user 708 is wearing a pair of virtual reality goggles, and the EDIE environment 102 running on the client device can provide a 3D view of a virtual dashboard in the virtual environment 104. Thus, the users can all interact together using various devices in the same virtual environment. The type of device used by some users may not be readily apparent to other users in the virtual environment 104. For example, the user 708 may see a virtual camera for display on the screen 704 for the user 702, and instead of seeing the virtual camera, the users may see an avatar in the virtual environment 104. The user 708 may not be able to distinguish whether the user 702 is using a virtual reality headset or a 2D display screen 704.

[0047] FIG. 8 shows a diagram of a virtual environment 104 with multiple users interacting with a virtual dashboard, according to some embodiments. In this example, users 804, 806 are represented by avatars with human appearance. Users can select avatars that look like themselves or any other virtual character. These avatars can move within the virtual environment 104 as the user moves within the real-world environment using a virtual reality headset. The virtual camera can move, rotate, pan, tilt, etc. as the user moves their head in the real-world environment. This allows the user to "walk around" on the virtual dashboard within the virtual environment 104 and see different visualization objects from different perspectives.

[0048] Various user movements may be represented in the virtual environment 104 for visibility to other users. For example, a compatible virtual reality equipment includes a virtual reality headset and a selection device that is held in the user's hand. When the selection device or virtual reality headset is moved in the real-world environment, the movement may be used to drive the movement of an avatar in the virtual environment 104. For example, when the user 408 lifts his or her hand in the real-world environment, the avatar's hand may also be lifted in the virtual environment 104 for visibility to the user 806. This allows the user to gesture and point to visualization objects in the virtual dashboard and have those movements visible to other users.

[0049] 8 also shows a virtual camera 802 that may be used to capture a view of the virtual environment 104 so that the image is displayed on the 2D screen. As mentioned above, a representation of the virtual camera 802 may be substituted with an avatar for the user 702 viewing the screen 704. Alternatively, the virtual camera 802 may be substituted by any visual indicator that has no visual equivalent in the virtual environment 104 or as a 3D object that may be rendered for other users to view.

[0050] A user using both the 2D and 3D views described above can interact with elements of the visualization objects in the virtual dashboard. For example, the user 804 may approach the funnel object 508 and select one of the spheres revolving around the funnel object 508. From the 2D view, the sphere may be selected using a finger tap or mouse click. From the 3D view, the sphere may be selected using one of the handheld virtual reality devices held by the user 804 by reaching out and "grabbing" one of the spheres as it revolves around the funnel object 508. The sphere may be bound to a data object in a data store, as described above. For example, the sphere may represent a row in a database, and the position, color, speed, trajectory, etc. of the sphere in the funnel object 508 may be determined by different values ​​in columns of the database row. When the user 804 holds the sphere, additional information about the sphere may be displayed in a user interface or a heads-up display (HUD). For example, each of the column values ​​of the database row may be displayed to the user 804. The sphere can be passed back and forth between user 804 and end user 806 so that both users 804, 806 can see details of the underlying data object.

[0051] When the user 804 is finished inspecting the sphere, the user 804 may place the sphere back into the funnel object 508. In some embodiments, the user 804 may "put" the sphere back into the funnel object 508, and the sphere may automatically return to its previous position / rotation within the funnel object 508. In other embodiments, the user 804 may place the sphere in a different location within the funnel object than where it was originally removed. As discussed above, the location of the sphere within the funnel object 508 may be determined by values ​​in the underlying dataset that is bound to the funnel object 508. Note that if the location of the sphere in the funnel object 508 is changed, the value corresponding to the location may also be changed. In some embodiments, the value corresponding to the new location within the funnel object 508 may be written back to the underlying dataset. This allows the user to manipulate elements of virtualized objects in the virtual environment 104 and change values ​​in the dataset to which the visualization object is bound.

[0052] In some embodiments, the view of the visualization objects provided to each of the users 804, 806 may be the same. For example, if the user 804 pulls the sphere out of the funnel object 508 as described above, the user 806 will see the sphere exiting the funnel object 508. Similarly, if the user 804 puts the sphere back into the funnel object 508, the user 806 will be able to see the sphere's new position in the funnel object 508. Thus, changes to the visualization objects and their underlying datasets may be common to each of the users using the virtual dashboard in the virtual environment 104.

[0053] In other embodiments, each of the users 804, 806 may be provided with their own view of the visualization object. In these embodiments, the state of each visualization object may be stored uniquely for each user 804, 806. For example, when user 804 pulls the sphere out of the funnel object 508 as described above, user 806 will continue to see the sphere spinning within the funnel object 508. Thus, changes made to elements of the visualization object by one user 804 will only be seen by that particular user 804. Other users 806 will continue to see the visualization object in an unmodified state. Embodiments may handle changes made to the underlying dataset by one user according to stored preferences. For example, some embodiments may propagate the changes to the underlying dataset, while other embodiments may provide the dataset in a "read-only" configuration such that changes to the visualization object are not reflected in the underlying dataset. Some embodiments may present the changes to all users present in the virtual environment 104 for approval before the changes are written to the underlying dataset.

[0054] As described above, each visualization object may have one or more views or view models associated with it. These view models may control the look and feel of the visualization object when it is rendered in the virtual environment 104. The EDIE environment 102 allows each user to select an individual view model for the same visualization object. For example, user 804 may select to view funnel object 508 using a business view model that uses muted colors and smaller spheres. User 806 may select to view funnel object 508 using an information view model that uses brighter colors and larger spheres. This allows each individual user to adjust the look and feel of the visualization object in the virtual dashboard without changing the view models for other users.

[0055] 9 illustrates a view of a real-world environment 908 that may be used to interact with a virtual environment 104, according to some embodiments. A user 902 may use a virtual reality device that includes a virtual reality headset 904 and / or one or more handheld selection devices 906. As the user 902 moves through the real-world environment 908, a virtual camera in the virtual environment 104 may move through the virtual environment 104 in a corresponding manner. The virtual camera may capture a view of the virtual environment 104 that is displayed to the user 902 through the virtual reality headset 904. As the user 902 moves their hand holding the selection device 906, the hand of a corresponding avatar in the virtual environment 104 may also move within the virtual environment 104 to select an object, as described above.

[0056] FIG. 10 shows a flowchart 1000 of a method for displaying data in a multidimensional dashboard, according to some embodiments. The method may include accessing (1002) a plurality of 3D visualization components. Each of the 3D visualization components may include a parameterized input for receiving a data set. The 3D visualization components may be downloaded or otherwise received from a component exchange that allows a developer to provide 3D visualization components for use in multiple applications under development. The 3D visualization components may be downloaded to a client device or to an operating environment, such as the EDIE environment described above. For example, the 3D visualization components may include a funnel object, a graph object, and / or other visualization components described herein.

[0057] The method may also include receiving one or more data sets (1004). The data sets may represent enterprise data received from enterprise applications and / or databases. For example, the data sets may include customer relationship management (CRM) databases, human capital management (HCM) databases, financial software databases, and / or any other type of enterprise data available to the operating environment.

[0058] The method may further include binding the parameterized inputs of the plurality of 3D visualization components with one or more datasets (1006). For example, for each of the 3D visualization components, the corresponding parameterized inputs may be bound to one of the one or more datasets. The parameterized inputs of the 3D visualization components may make the 3D visualization components generic such that the appearance and behavior of the 3D visualization components may be adjusted by the datasets to which they are bound. The datasets may be bound to the corresponding 3D visualization components at design time when the components are placed in an application. The datasets may alternatively or additionally be bound when the 3D visualization components are instantiated at run time. During run time, the system may receive input (e.g., from a user) that changes the dataset binding to a different dataset. Some 3D visualization components may be bound to multiple different datasets, each of which may define a visual or behavioral aspect of the 3D visualization component.

[0059] The method may further include rendering a plurality of 3D virtual objects in the virtual environment based on the plurality of 3D visualization components and the one or more datasets (1008). Each of the 3D visualization components may include a view model, an animation model, a wireframe skeleton, and / or other graphical constructs that may be used to generate the 3D virtual objects in the virtual environment. The virtual environment may be implemented in the EDIE operating environment to create a 3D virtual scene that includes the objects in addition to the 3D virtual objects from the 3D visualization components. For example, the virtual environment may be configured as a carousel of 3D virtual objects. In another example, the virtual environment may be configured as an enterprise dashboard that displays the 3D objects as virtual "widgets" that the user can view in the virtual environment. Each of the 3D virtual objects in the dashboard may be bound to different enterprise datasets from different databases and / or different applications. For example, the dashboard may provide summary data for finances, employees, operations, customers, etc., all in one unified view in a single virtual environment.

[0060] The method may also include receiving (1010) connections to the virtual environment from a plurality of client devices. Some embodiments may include a client device having installed thereon a hardware detection process configured to detect a type of display and / or input device used with the client device. The hardware detection process may automatically configure interaction with the virtual environment to match the type of client device. For example, if the client device includes a virtual reality headset, the hardware detection process may be configured to provide an immersive view and / or interaction with the virtual environment such that the user feels as if they are operating within the virtual environment rather than a real-world environment. If the client device includes a 2D screen (e.g., a monitor, laptop computer, etc.), the hardware detection process may be configured to place a virtual camera within the virtual environment to capture a 2D image of the virtual environment at a position to be displayed on the 2D screen.

[0061] The method may further include providing a plurality of client devices with a plurality of views of a plurality of 3D virtual objects in the virtual environment (1012). Each of the client devices may be provided with an individual view of the virtual environment. Additionally, each of the client devices may be configured to allow a user to interact with the 3D virtual objects in the virtual environment and change their display. For example, a user may remove an element from a virtual object that corresponds to an individual element in a corresponding data set. The user may see a display that includes summary information about data points in that data element and may be permitted to change certain data points. These changes may be updated in the underlying data source to which the 3D virtual object is bound. In some embodiments, the changes may be immediately seen by other users in the virtual environment. Alternatively, some changes may be visible only to the user who makes the change, and each user may be provided with an individualized view of the virtual environment.

[0062] It should be appreciated that the specific steps illustrated in FIG. 10 provide a particular way of displaying data in a multidimensional dashboard according to various embodiments. Other sequences of steps may also be performed according to alternative embodiments. For example, alternative embodiments of the invention may perform the steps outlined above in a different order. Additionally, individual steps illustrated in FIG. 10 may include multiple sub-steps that may be performed in various orders as appropriate for the individual step. Additionally, additional steps may be added or removed depending on the particular application. Those skilled in the art will recognize many variations, modifications, and alternatives.

[0063] Alternative time series visualization components Many different visualization components may be used with the virtual environments described above. Multiple visualization components may be used in the same application to create interactive environments that present data in many different ways. For example, a single virtual environment may include visualization components corresponding to funnel objects, bar graph objects, representations of beakers filled with liquid volumes, profile layouts of a person's profile, and / or other visualization components that may be rendered in 3D space to be viewed and manipulated by users on multiple client devices. Depending on the type of data, some visualization components may be tailored to highlight aspects of the data more than others. The designer of the virtual environment may determine which visualization components best highlight aspects of the data to the intended audience.

[0064] In embodiments described herein, a particular type of visualization component is described that highlights data that includes a time component. For example, some data sets may include a time series sequence of data points. Multiple values ​​may be recorded and stored as data points in a data table or other data structure. Each value may be sampled or recorded at regular time intervals. For example, five consecutive data values ​​may be assumed to have been recorded with the same time delay between each value. The sequence of data points may also include a value indicating a sampling rate or interval between each of the data points. In some embodiments, each of the data points in the time series may include both a value and a timestamp indicating when the value was obtained or recorded by the system. This allows for irregular intervals between data points. A data set may include two or more time series sequences of data points. For example, data may be sampled simultaneously for different systems, or data may be sampled repeatedly and sequentially in different sampling sessions for the same system.

[0065] Regardless of how a time series sequence of data points is stored, it may be beneficial to display these data points with a visualization component that can portray the time-dependent nature of the data. Loading a time series sequence of data points into a visualization component with limited dimensionality may obscure the time-dependent nature of the data points or cause multiple time series sequences to be displayed together in a single dimension, thereby obscuring the differences between different time sequences. Thus, some visualization components may include a dimension dedicated to time, along with another dimension, for each time series sequence of data points in the dataset.

[0066] FIG. 11 illustrates a diagram of a visualization component for displaying a time series sequence of data points in a virtual environment, according to some embodiments. This visualization component may be referred to as a line graph component. When the line graph component is instantiated or loaded in the virtual environment, it may receive one or more data sets to be bound to parameterized inputs, as described above. Each data set may include one or more time series sequences of data points. For example, each data set may include one or more data tables, where each row in the data table corresponds to a data value in the time series sequence, and each column in each row includes attribute values ​​or characteristics of that data value. These attribute values ​​may include timestamps, user IDs, session IDs, other data values, client devices, test procedures, and / or any other metadata that may describe or be associated with the data values ​​recorded for the rows in the data tables. Rows that do not include a timestamp or other sampling rate identifier may be assumed to have regular intervals between each data value, and the sampling rate or interval between data values ​​may be specified separately. The parameterized input may receive each of these time sequences of data points as vectors, arrays, lists, sequences, and / or any other data structure that contains a variable or fixed number of data values.

[0067] When the line graph component receives and processes an input of a time series sequence of data points through a parameterized input, the line graph component can generate a line graph object 1100 in the virtual environment. The line graph object 1100 can include a multi-dimensional line graph designed to show different dimensions of the time series data so that the user can clearly distinguish them. Different dimensions or axes in the line graph can be assigned to different dimensions for each data value in the display.

[0068] In the example of FIG. 11, the line graph object 1100 includes a vertical axis 1102 that may be associated with a value of each data point. The line graph object 1100 may also include a first horizontal axis 1106 that corresponds to time. The line graph object 1100 may also include a second horizontal axis 1104 that corresponds to an index in multiple chronological sequences of data points. For example, if one or more data sets include multiple chronological sequences of data points, each chronological sequence of data points may be assigned a particular index along the horizontal axis 1104. This spreads out the individual chronological sequences such that they are visibly distinguishable from one another.

[0069] As an example, the embodiment described below uses test data to show how time series data is displayed by the line graph object 1100. This test data may include several faults received from a particular machine over time. Each index along the horizontal axis 1104 may correspond to a different machine under test. The time along the horizontal axis 1106 may correspond to the time at which the fault was detected. Finally, the values ​​along the horizontal axis 1102 may correspond to the severity of the fault, the number of faults detected, and / or any other way of characterizing the hardware / software fault. This test data is used as an example because it shows the advantage of separating various time series sequences of data points from each other. It also shows the advantage of using a time axis 1106 that is orthogonal to the other horizontal axes 1104 that separate each time series sequence.

[0070] Each time series sequence of data points may be plotted in the line graph object 1100 along a different index of the horizontal axis 1104. In some embodiments, each time series sequence of data points may be represented with a continuous line using a different color so that it may be visually distinguished from adjacent lines. Alternatively or additionally, each time series sequence of data points may be represented with a different line style (e.g., dashed, dotted, solid, etc.). In some embodiments, each of the values ​​in the time series sequence of data points may be compared to a threshold, and the line style, line color, line transparency, and / or other visual features or effects of each line may be changed to indicate that the threshold has been exceeded. For example, the line 1108 includes a relatively high value that may exceed a threshold of failure data. The line 1108 may be highlighted or colored differently. The line 1108 may also include a different line style, such as a thicker point value, to indicate that the threshold has been exceeded. This may help a user visually distinguish time series sequences of data of interest according to a threshold (e.g., to identify machines with widespread failures).

[0071] FIG. 12 shows a view of the line graph object 1100 from a different perspective than FIG. 11, according to some embodiments. As described in detail above, the virtual environment in which the line graph object 1100 is generated may be a 3D virtual environment that allows user interaction from multiple client devices. Users may each be assigned a corresponding virtual camera that moves in the virtual environment according to user inputs. These inputs may depend on the type of client device being used by each user. For example, a desktop computer may include a virtual camera that renders images from the virtual environment that are displayed on a two-dimensional display screen in the real-world environment. Inputs to "move through" the virtual environment may be received from a mouse, keyboard, touch screen display, voice commands, etc. These inputs may move the virtual camera in the virtual environment to provide different perspectives of a 3D view of the line graph object 1100.

[0072] When a user accesses the virtual environment through a virtual reality device, such as a virtual reality headset, a corresponding virtual camera in the virtual environment can provide images such that the user feels as if they have entered the virtual environment. The user's physical movements in the real-world environment can correspond to the movements of the virtual camera in the virtual environment. This allows the user to "walk around" in different visualization objects in the virtual environment. As mentioned above, this also allows the user to interact with individual data points in the visualization objects as they are rendered in the virtual environment.

[0073] For example, a user may stand in front of the line graph object 1100 in FIG. 11. As the user moves from left to right across the user's view frustrum, the user may see a difference line representing a time series sequence of data points. This position may be represented in FIG. 11 as position 1122. If the user wishes to view the time series sequence of data points from a different angle, the user may generate input (e.g., movement) in the real-world environment to move the virtual camera to a new position in the virtual environment. For example, the user may walk around to the right of the line graph object 1100 so that the user can "look down" on each line of the line graph object 1100 to see the data from a different perspective. This perspective is shown in FIG. 12. This new position may correspond to position 1120 in FIGS. 11 and 12. When the user walks to the new position 1120, it may appear as if the user is walking through a solid object in the virtual environment. Thus, a user can walk around or within the line graph object 1100 to view the data from any desired angle or position.

[0074] Note that the perspective of the data from location 1120 in FIG. 12 is different from the perspective of the data from location 1122 in FIG. 11. For example, the lines representing the time series of data points are relatively small in FIG. 11 compared to the size of those lines in FIG. 12. In addition to moving through the virtual environment, the user can also control the scale at which the virtual environment is viewed. When using a virtual reality device such as a virtual reality headset, this may correspond to scaling the virtual "size" of the user. Making the user bigger / taller allows them to see the line graph object 1100 from a front / top view as shown in FIG. 11. On the other hand, making the user smaller / shorter allows them to see the line graph object 1100 from a more ground level position as shown in FIG. 12. When using a 2D interface, the user can scale the view by moving the position of the virtual camera and zooming in / out.

[0075] FIG. 13 illustrates a line graph object being rendered by a virtual environment, according to some embodiments. To render a view of the line graph object 1100, a 3D object may first be instantiated and placed in the virtual environment. The line graph object 1100 may include multiple lines, each corresponding to an individual time series sequence of data points in one or more data sets that are bound to parameterized inputs of the line graph component. To generate the line graph object, the virtual environment sets a coordinate system for the line graph object, transforms that coordinate system to the virtual environment's coordinate system, plots individual data points for each time series, and connects these data points with a visible line so that the user can see how each time series sequence progresses along the time axis.

[0076] The coordinate system of the 3D line graph may correspond to the units of the different axes mentioned above. The vertical axis, which corresponds to the value of the data points, may be scaled based on the maximum value in the data points. The first and second horizontal axes, which correspond to time and index in the multiple time series sequences, may be scaled based on the total time and / or number of time series sequences represented. To convert this coordinate system to the coordinate system of the virtual environment, the overall dimensions of the line graph object 1100 may be specified. Each of these dimensions may be expressed in units expressed in the virtual environment, such as inches, feet, etc. The total length in any dimension may then be divided by the number of divisions in the line graph coordinate system to convert those units to units in the virtual environment. For example, if the time axis includes 20 divisions each corresponding to 5 minutes, and the length of the time dimension in the virtual environment is 10 virtual feet, the coordinate conversion may be scaled by 5 minutes for every 6 inches. A similar procedure may be performed for each dimension in the line graph object.

[0077] After establishing a scale between the coordinate systems of the line graph object 1100, the individual data points can be plotted for each chronological sequence. For example, the chronological sequence of data points represented by the line 1302 in FIG. 13 can be plotted as follows: Each of the individual data points can be plotted in the virtual environment at a corresponding coordinate. For example, the data point 1304 can be plotted based on its corresponding time and value. Once each of the data points has been plotted for a particular chronological sequence, each of the data points can be sequentially connected by a line object in the virtual environment. This can correspond to a line, a ray, a polygon bar, and / or any other 3D construct that can represent these connections in the line graph object 1100. This same procedure can be performed for each of the chronological sequences in the dataset provided to the visualization component. These may be plotted sequentially and / or simultaneously, depending on the embodiment.

[0078] 14 illustrates how a user can interact with data in a virtual environment, according to some embodiments. As described above, a user equipped with a virtual reality device and / or a corresponding virtual camera in the virtual environment can move within the virtual environment. This may include allowing the user to move over, through, and / or pass through portions of the line graph object 1100 in the virtual environment.

[0079] In this example, two users may be present in the virtual environment. These users may be represented in the virtual environment by virtual cameras. Instead of displaying a representation of the virtual camera in the virtual environment, some embodiments may instead generate avatars 1402, 1404 corresponding to the individual users. Thus, as one user moves through the virtual environment by moving the virtual camera, other users in the virtual environment may see the avatars 1402, 1404 moving through the virtual environment in an animated manner. When the user of the avatar 1402 looks at the virtual environment, from the perspective of the avatar 1402 shown in FIG. 14, the user of the avatar 1402 may see the virtual environment including the line graph object 1100 and the other users' avatars 1404.

[0080] The user may scale themselves in the virtual environment to a level that allows them to interact with the time series sequence of the desired data. For example, in this example, the user has scaled down their avatars 1402, 1404 so that they can interact with the time series sequence represented by the line 1302. In some embodiments, as the user gets closer to the line 1302, the individual data points are highlighted on the line 1302 to make it easier to interact with them. For example, as the avatar 1402 moves next to the line 1302, the data points 1304 may become visible as spheres to allow the user to interact with the data points 1304. These spheres may be hidden when the user is not in close proximity to the data point locations to avoid cluttering the view of the trajectory of the line representing the time series sequence.

[0081] A user may have their avatar 1402 interact with a data point 1304 by "grabbing" the corresponding sphere in the virtual environment. This may be done using the hand controls of the virtual reality system described above. The user may then have additional information displayed for that data point, such as attribute values ​​for that data point 1304. The user may then modify any of those attribute values ​​via a pop-up user interface to replace the data point 1304 in the line 1302 of the time series sequence.

[0082] Some embodiments may also allow a user to change the position of a data point. For example, a user may have their avatar 1402 "grab" the sphere of a data point 1304 and move its position up or down. The corresponding value and / or time of the data point 1304 may be changed accordingly. These changes may be visible to both users via their avatars 1402, 1404. These changes may be restricted to only the user making these changes. In some embodiments, these changes may also be written back to the underlying data source, while other embodiments may simply reflect the changes in the virtual environment without writing back to the underlying data source.

[0083] As mentioned above, many different visualization components can be used to display time series sequences that have a time-dependent component in the data. The example line graph component discussed above is provided merely as an example and is not intended to be limiting. Other embodiments can use any type of visualization component that includes a dimension that corresponds to time.

[0084] 15 shows a circular bar graph component that can be used to visualize the same data bound to the line graph component, according to some embodiments. The circular bar graph component can be used to generate a circular bar graph object 1500 in a virtual environment. As with other visualization components, the circular bar graph object 1500 can be bound to one or more data sets used to generate the object 1500.

[0085] As described above, multiple visualization components can be instantiated or generated in the virtual environment to form a virtual dashboard of information. A story data structure may be used to animate and transition data between various visualization components. In this example, a time series sequence from a line graph object is transitioned or animated into a circular bar graph object 1500 to display the same data in a different manner.

[0086] The circular bar graph object 1500 may include individual lines emanating from the center of the graph 1500. Each of these lines may represent a single time series sequence of data points. The time dimension may be represented with each of these lines emanating from the center of the circle divided into regularly spaced sectors. The value of each of these data points may be represented by vertical bars extending from the edge of the circle. Each of these bars may be spaced to represent an individual time series sequence. Thus, the circular bar graph 1500 may represent a time and / or value dimension while still visually grouping the individual time series sequences together to the user.

[0087] The circular bar graph 1500 may form part of a virtual environment occupied by a user, as described above. For example, a user represented by an avatar 1402, 1404 may walk along the top of the circular bar graph object 1500 in the virtual environment. The user may highlight different time sequences and / or values ​​by stepping on or otherwise touching corresponding sections on the circle.

[0088] The circular bar graph 1500 may be used to display any type of data, not just the time series data described above. The lines emanating from the center of the circle may represent groupings of data, and the sectors split off from these lines may represent subgroupings of data. The vertical bars extending downward may represent any value in any dimension. Thus, the time series sequence of data points represented by the circular bar graph 1500 is presented by way of example only and is not intended to limit the operation of the circular bar graph 1500.

[0089] FIG. 16 illustrates a pie chart 1500 that operates similarly to the line chart 1100, according to some embodiments. In this example, each circle in the pie chart 1500 may correspond to a single time series sequence of data points. The radial lines extending from the center of the circle may correspond to divisions in the time dimension. The vertical bars extending upward correspond to the value of each data point in the time series. The pie chart 1600 may be plotted in a manner similar to how the line chart 1100 described above is plotted. For example, the line chart 1100 may be wrapped around itself to form the pie chart 1600.

[0090] Pie chart 1600 may be advantageous for viewing periodic data. For example, as data is repeated (e.g., repeated tests, repeated input data, etc.), these data may form a repeating pattern that may be represented by repeated crossings of the circle in pie chart 1600. Each cycle around the graph may aggregate the new data with the data at its previous position such that the vertical bars form a histogram representation of the data in the vertical dimension.

[0091] The pie chart 1600 may be used with any type of data, and the radial lines extending from the center of the circle do not necessarily represent divisions in the time dimension. Any other type of data may be represented by the pie chart 1600. Additionally, the pie chart 1600 may be part of a virtual dashboard that includes other visualization components, such as the circular bar chart 1500 and / or the line chart 1100. The virtual dashboard may also include visualization components, such as the funnel object described above.

[0092] 17 illustrates a flowchart 1700 of a method for visualizing time series data in an interactive virtual environment, according to some embodiments. The method may include receiving one or more datasets including a plurality of time series sequences of data points (1702). The datasets may include test data, enterprise data, data from an enterprise application or database, data received from a web service or any other data source, etc. Each of the time series sequences of data points may include a time dimension such that each data point is associated with a timestamp and / or is received at regular time intervals.

[0093] The method may also include plotting (1704) each of the multiple time series sequences of the data points on a 3D line graph in the virtual environment. As described above, this may include generating a coordinate system for the line graph, transforming that coordinate system into dimensions found in the virtual environment, and plotting individual data points on those coordinates. Some embodiments may join these coordinates together with lines or other 3D constructs to represent the time series sequence of the data points as they move through the time dimension. Some embodiments may also separate each of the time series sequences along another dimension so that the time series sequences are easily distinguished in the virtual environment.

[0094] The method may further include generating one or more views of the 3D line graph with one or more virtual cameras configured to move around the 3D line graph in the virtual environment (1706). Each of the virtual cameras may generate the views by capturing a view of the 3D line graph in the virtual environment and rendering a 2D view of the image to be displayed on a display device. Each of the virtual cameras may correspond to a client device operated by a user. These client devices may include devices with 2D screens (e.g., laptop computers, desktop computers, etc.) or devices with 3D display capabilities (e.g., augmented reality glasses, virtual reality headsets, etc.).

[0095] The method may further include transmitting one or more views of the 3D line graph to one or more client devices (1708). The views may be transmitted in real time to be displayed at an interactive frame rate on each of the client devices. This allows users of the client devices to interact with one another in the virtual environment. This may also allow any of the users to interact with individual data points in the 3D line graph. For example, a user may manipulate individual data points in the 3D line graph in the virtual environment to change their values. These changes may cause changes in the underlying data bound to the visualization component.

[0096] It should be appreciated that the specific steps illustrated in FIG. 17 provide a particular method of visualizing time series data in an interactive virtual environment according to various embodiments. Other sequences of steps may also be performed according to alternative embodiments. For example, alternative embodiments of the present invention may perform the steps outlined above in a different order. Additionally, the individual steps illustrated in FIG. 17 may include multiple sub-steps that may be performed in various sequences as appropriate for the individual step. Additionally, additional steps may be added or removed depending on the particular application. Those skilled in the art will recognize many variations, modifications, and alternatives.

[0097] Each of the methods described herein may be implemented by a computer system. Each of the steps of these methods may be performed automatically by the computer system and / or may be provided with input / output involving a user. For example, a user may provide inputs for each step of the method, and each of these inputs may be responsive to a particular output that requests such input, which output is generated by the computer system. Each input may be received in response to a corresponding requested output. Furthermore, inputs may be received from a user, from another computer system as a data stream, retrieved from a memory location, retrieved over a network, requested from a web service, etc. Similarly, outputs may be provided to a user, to another computer system as a data stream, stored in a memory location, transmitted over a network, provided to a web service, etc. In short, each of the steps of the methods described herein may be performed by a computer system and may include any number of inputs, outputs, and / or requests to and from the computer system, which may or may not involve a user. Those steps that do not involve a user are said to be performed automatically by the computer system without human intervention. Thus, in light of this disclosure, it will be understood that each step of each method described herein may be modified to include inputs to and outputs from a user, or may be performed automatically by a computer system without human intervention, where any decisions are made by a processor. Additionally, some embodiments of each of the methods described herein may be implemented as a set of instructions stored on a tangible, non-transitory storage medium to form a tangible software product.

[0098] 18 is a simplified diagram illustrating a distributed system 1800 for implementing one of the embodiments. In the illustrated embodiment, the distributed system 1800 includes one or more client computing devices 1802, 1804, 1806, and 1808 configured to execute and operate client applications, such as web browsers, proprietary clients (e.g., Oracle Forms), etc., via one or more networks 1810. A server 1812 may be communicatively coupled to the remote client computing devices 1802, 1804, 1806, and 1808 via the network 1810.

[0099] In various embodiments, server 1812 may be adapted to execute one or more services or software applications provided by one or more of the system's components. In some embodiments, these services may be provided to users of client computing devices 1802, 1804, 1806, and / or 1808 as web-based or cloud services, or under a Software as a Service (SaaS) model. Users operating client computing devices 1802, 1804, 1806, and / or 1808 may then utilize one or more client applications to interact with server 1812 to utilize the services provided by these components.

[0100] In the illustrated configuration, the software components 1818, 1820, and 1822 of the system 1800 are shown implemented on the server 1812. Also, in other embodiments, one or more of the components of the system 1800 and / or the services provided by these components may be implemented by one or more of the client computing devices 1802, 1804, 1806, and / or 1808. A user operating a client computing device may then utilize one or more client applications to use the services provided by these components. These components may be implemented in hardware, firmware, software, or a combination thereof. It should be understood that a variety of different system configurations are possible that may differ from the distributed system 1800. Thus, the illustrated embodiment is an example of a distributed system for implementing the system of the embodiment and is not intended to be limiting.

[0101] Client computing devices 1802, 1804, 1806, and / or 1808 may be handheld mobile devices (e.g., iPhone, mobile phone, iPad, computing tablet, personal digital assistant (PDA)) or wearable devices (e.g., Google Glass head mounted display) running software such as Microsoft Windows Mobile and / or various mobile operating systems such as iOS, Windows Phone, Android, BlackBerry 10, Palm OS, and Internet, email, short message service (SMS), BlackBerry, or other communication protocols available. Client computing devices may be general purpose personal computers including, by way of example, personal and / or laptop computers running various versions of Microsoft Windows, Apple Macintosh, and / or Linux operating systems. The client computing devices may be workstation computers running any of a variety of commercially available UNIX or UNIX-like operating systems, including, but not limited to, various GNU / Linux operating systems such as Google Chrome OS. Alternatively, or additionally, the client computing devices 1802, 1804, 1806, and 1808 may be thin client computers, Internet-enabled gaming systems (e.g., Microsoft Xbox gaming consoles with or without Kinect gesture input devices), and / or other electronic devices such as personal messaging devices capable of communicating over the network 1810.

[0102] Although the exemplary distributed system 1800 is shown having four client computing devices, any number of client computing devices may be supported. Other devices, such as devices with sensors, may interact with the server 1812.

[0103] Network 1810 in distributed system 1800 may be any type of network familiar to those skilled in the art capable of supporting data communications using any of a variety of commercially available protocols, including but not limited to TCP / IP (Transmission Control Protocol / Internet Protocol), SNA (Systems Network Architecture), IPX (Internet Packet Exchange), AppleTalk, etc. By way of example only, network 1810 may be a local area network (LAN), such as one based on Ethernet, Token Ring, etc. Network 1810 may also be a wide area network and the Internet. Network 1810 may include a virtual network, including, but not limited to, a virtual private network (VPN), an intranet, an extranet, a public switched telephone network (PSTN), an infrared network, a wireless network (e.g., a network operating under any of the Institute of Electrical and Electronics (IEEE) 802.11 suite of protocols, Bluetooth, and / or other wireless protocols), and / or any combination thereof, and / or other networks.

[0104] Servers 1812 may be comprised of one or more general purpose computers, dedicated server computers (including, by way of example only, PC (personal computer) servers, UNIX servers, mid-range servers, mainframe computers, rack-mounted servers, etc.), server farms, server clusters, or other suitable configurations and / or combinations. In various embodiments, servers 1812 may be adapted to execute one or more services or software applications described in the above disclosure. For example, servers 1812 may correspond to servers for executing the above processes according to embodiments of the present disclosure.

[0105] Server 1812 may run an operating system, including any of those listed above, as well as any commercially available server operating system. Server 1812 may also run any of a variety of additional server and / or middle tier applications, including an HTTP (Hypertext Transfer Protocol) server, an FTP (File Transfer Protocol) server, a CGI (Common Gateway Interface) server, a JAVA server, a database server, etc. Exemplary database servers include, but are not limited to, those commercially available from Oracle, Microsoft, Sybase, IBM (International Business Machines), etc.

[0106] In some implementations, server 1812 may include one or more applications for analyzing and consolidating data feeds and / or event updates received from users of client computing devices 1802, 1804, 1806, and 1808. By way of example, the data feeds and / or event updates may include, but are not limited to, Twitter feeds, Facebook updates, or real-time updates received from one or more third party information sources and continuous data streams, including real-time events related to sensor data applications, financial tickers, network performance measurement tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, and the like. Server 1812 may also include one or more applications for displaying the data feeds and / or real-time events via one or more display devices of client computing devices 1802, 1804, 1806, and 1808.

[0107] The distributed system 1800 may also include one or more databases 1814 and 1816. The databases 1814 and 1816 may reside in a variety of locations. As an example, one or more of the databases 1814 and 1816 may reside on a non-transitory storage medium local to (and / or present on) the server 1812. Alternatively, the databases 1814 and 1816 may be remote from the server 1812 and communicate with the server 1812 via a network-based or dedicated connection. In one set of embodiments, the databases 1814 and 1816 may reside on a storage-area network (SAN). Similarly, any necessary files to perform functions attributed to the server 1812 may be stored locally and / or remotely on the server 1812, as appropriate. In one set of embodiments, the databases 1814 and 1816 may include relational databases, such as those provided by Oracle Corporation, adapted to store, update, and retrieve data in response to SQL-formatted commands.

[0108] 19 is a simplified block diagram of one or more components of a system environment 1900 in which services provided by one or more components of an embodiment system can be delivered as cloud services, according to an embodiment of the disclosure. In the embodiment shown, the system environment 1900 includes one or more client computing devices 1904, 1906, and 1908 that can be used by a user to interact with a cloud infrastructure system 1902 that provides cloud services. The client computing devices can be configured to run client applications, such as a web browser, a proprietary client application (e.g., Oracle Forms), or other applications, that can be used by a user of the client computing device to interact with the cloud infrastructure system 1902 to use services provided by the cloud infrastructure system 1902.

[0109] It should be understood that the cloud infrastructure system 1902 depicted in the figure may have other components than those shown. Additionally, the illustrated embodiment is only one example of a cloud infrastructure system that may incorporate embodiments of the present invention. In some other embodiments, the cloud infrastructure system 1902 may have more or fewer components than those depicted in the figure, may combine two or more components, or may have a different configuration or arrangement of components.

[0110] The client computing devices 1904, 1906, and 1908 may be devices similar to those described above for 1802, 1804, 1806, and 1808.

[0111] Although the exemplary system environment 1900 is shown having three client computing devices, any number of client computing devices may be supported. Other devices, such as devices having sensors, etc., may interact with the cloud infrastructure system 1902.

[0112] Network 1910 may facilitate communication and exchange of data between clients 1904, 1906, and 1908 and cloud infrastructure system 1902. Each network may be any type of network familiar to those skilled in the art capable of supporting data communications using any of a variety of commercially available protocols, including those described above for network 1810.

[0113] Cloud infrastructure system 1902 may comprise one or more computers and / or servers, which may include those described above for server 1812.

[0114] In certain embodiments, the services provided by the cloud infrastructure system may include numerous services available on demand to users of the cloud infrastructure system, such as online data storage and backup solutions, web-based email services, hosted office suites and document collaboration services, database processing, managed technical support services, and the like. The services provided by the cloud infrastructure system are dynamically scalable to meet the needs of its users. A specific instantiation of a service provided by the cloud infrastructure system is referred to herein as a "service instance." In general, any service available to users from a cloud service provider's system over a communications network such as the Internet is referred to as a "cloud service." Typically, in a public cloud environment, the servers and systems that make up the cloud service provider's system are distinct from the customer's own on-premise servers and systems. For example, the cloud service provider's system may host an application, which a user may order and use on demand over a communications network such as the Internet.

[0115] In some examples, services in a computer network cloud infrastructure may include storage, hosted databases, hosted web servers, protected computer network access to software applications, or other services provided to users by cloud vendors or otherwise known in the art. For example, services may include password-protected access to remote storage on the cloud over the Internet. As another example, services may include web-services-based hosted relational databases and scripting language middleware engines for private use by networked developers. As another example, services may include access to email software applications hosted on the cloud vendor's website.

[0116] In particular embodiments, cloud infrastructure system 1902 may include a suite of application, middleware, and database service offerings delivered to customers in a self-service, subscription-based, elastically scalable, reliable, highly available, and secure manner. One example of such a cloud infrastructure system is the Oracle Public Cloud offered by the present assignee.

[0117] In various embodiments, cloud infrastructure system 1902 may be adapted to automatically provision, manage, and track customer subscriptions to services provided by cloud infrastructure system 1902. Cloud infrastructure system 1902 may provide cloud services through various deployment models. For example, services may be provided under a public cloud model, where cloud infrastructure system 1902 is owned by an organization that sells cloud services (e.g., owned by Oracle Corporation) and the services are available to the general public or various industry enterprises. As another example, services may be provided under a private cloud model, where cloud infrastructure system 1902 operates solely for a single organization and may provide services to one or more entities within that organization. Cloud services may also be provided under a community cloud model, where cloud infrastructure system 1902 and the services provided by cloud infrastructure system 1902 are shared by several organizations within an associated community. Cloud services may also be provided under a hybrid cloud model, which is a combination of two or more different models.

[0118] In some embodiments, the services provided by cloud infrastructure system 1902 may include one or more services provided under the Software as a Service (SaaS) category, the Platform as a Service (PaaS) category, the Infrastructure as a Service (IaaS) category, or other categories of services including hybrid services. A customer may order one or more services provided by cloud infrastructure system 1902 via a subscription order. Cloud infrastructure system 1902 then performs processing to provide the services in the customer's subscription order.

[0119] In some embodiments, the services provided by the cloud infrastructure system 1902 may include, but are not limited to, application services, platform services, and infrastructure services. In some examples, application services may be provided by the cloud infrastructure system through a SaaS platform. The SaaS platform may be configured to provide cloud services that fall into the SaaS category. For example, the SaaS platform may provide functionality for building and delivering a suite of on-demand applications on a unified development and deployment platform. The SaaS platform may manage and control the underlying software and infrastructure for providing the SaaS services. By utilizing the services provided by the SaaS platform, customers can utilize applications that run on the cloud infrastructure system. Customers can obtain application services without the customer having to purchase separate licenses and support. A variety of different SaaS services may be provided. Examples include, but are not limited to, services that provide solutions for sales performance management, enterprise integration, and business flexibility for large organizations.

[0120] In some embodiments, platform services may be provided by the cloud infrastructure system through a PaaS platform. The PaaS platform may be configured to provide cloud services that fall under the PaaS category. Examples of platform services may include, but are not limited to, services that allow an organization (such as Oracle) to integrate existing applications on a shared common architecture, and the ability to build new applications that leverage shared services provided by the platform. The PaaS platform may manage and control the underlying software and infrastructure to provide the PaaS services. Customers may obtain the PaaS services provided by the cloud infrastructure system without the customer having to purchase separate licenses and support. Examples of platform services include, but are not limited to, Oracle Java Cloud Service (JCS), Oracle Database Cloud Service (DBCS), etc.

[0121] By utilizing the services provided by the PaaS platform, customers can utilize programming languages ​​and tools supported by the cloud infrastructure system and also control the deployed services. In some embodiments, the platform services provided by the cloud infrastructure system may include database cloud services, middleware cloud services (e.g., Oracle Fusion middleware services), and Java cloud services. In one embodiment, the database cloud services may support a shared service deployment model that allows organizations to pool database resources and provide database-as-a-service to customers in the form of a database cloud. The middleware cloud services may provide customers with a platform for developing and deploying various business applications in the cloud infrastructure system, and the Java cloud services may provide customers with a platform for deploying Java applications in the cloud infrastructure system.

[0122] A variety of different infrastructure services may be provided by the IaaS platform in a cloud infrastructure system. The infrastructure services facilitate management and control of basic computing resources such as storage, network, and other underlying computing resources for customers who use the services provided by the SaaS and PaaS platforms.

[0123] Also, in particular embodiments, cloud infrastructure system 1902 may include infrastructure resources 1930 for providing resources used to provide various services to customers of the cloud infrastructure system. In one embodiment, infrastructure resources 1930 may include a pre-integrated optimized combination of hardware, such as servers, storage, and networking resources, for running the services offered by the PaaS and SaaS platforms.

[0124] In some embodiments, resources in cloud infrastructure system 1902 may be shared by multiple users and dynamically reallocated on a demand basis. Resources may also be allocated to users in different time periods. For example, cloud infrastructure system 1930 may maximize resource utilization by allowing a first set of users in a first time period to utilize resources of the cloud infrastructure system for a defined period of time and allowing reallocation of the same resources to another set of users located in a different time period.

[0125] In particular embodiments, several internal shared services 1932 may be provided that are shared by various components or modules of, and services provided by, cloud infrastructure system 1902. These internal shared services may include, but are not limited to, security and identity services, integration services, enterprise repository services, enterprise manager services, virus scanning and whitelist services, high availability, backup and recovery services, services to enable cloud support, email services, notification services, file transfer services, etc.

[0126] In particular embodiments, cloud infrastructure system 1902 may provide comprehensive management of cloud services (e.g., SaaS, PaaS, and IaaS services) in the cloud infrastructure system. In one embodiment, cloud management functionality may include functionality for provisioning, managing, tracking, etc., customer subscriptions received by cloud infrastructure system 1902.

[0127] In one embodiment, as shown in the figure, cloud management functionality may be provided by one or more modules, such as an order management module 1920, an order orchestration module 1922, an order provisioning module 1924, an order management and monitoring module 1926, and an identity management module 1928. These modules may include or be provided using one or more computers and / or servers, which may be general purpose computers, dedicated server computers, server farms, server clusters, or any other suitable configuration and / or combination.

[0128] In example operation 1934, a customer using a client device, such as client device 1904, 1906, or 1908, may interact with cloud infrastructure system 1902 by requesting one or more services offered by cloud infrastructure system 1902 and placing an order for a subscription to one or more services provided by cloud infrastructure system 1902. In particular embodiments, the customer may access cloud user interfaces (UIs), namely cloud UI 1912, cloud UI 1914, and / or cloud UI 1916, and place a subscription order via these UIs. Order information received by cloud infrastructure system 1902 in response to the customer placing an order may include information identifying the customer and the one or more services offered by cloud infrastructure system 1902 to which the customer intends to subscribe.

[0129] After an order is placed by a customer, the order information is received via the cloud UI 1912, 1914 and / or 1916.

[0130] In operation 1936, the order is stored in an order database 1918. The order database 1918 may be one of several databases operated by the cloud infrastructure system 1918 and in conjunction with other system elements.

[0131] At operation 1938, the order information is forwarded to the order management module 1920. In some examples, the order management module 1920 may be configured to perform billing and accounting functions related to the order, such as confirming the order and booking the order upon confirmation.

[0132] At operation 1940, information regarding the order is communicated to the order orchestration module 1922. The order orchestration module 1922 may utilize the order information to orchestrate the provisioning of services and resources for the order placed by the customer. In some examples, the order orchestration module 1922 may orchestrate the provisioning of resources to support the subscribed service using the services of the order provisioning module 1924.

[0133] In certain embodiments, the order orchestration module 1922 enables management of business processes associated with each order and applies business logic to determine whether the order should proceed to provisioning. In operation 1942, upon receiving an order for a new subscription, the order orchestration module 1922 sends a request to the order provisioning module 1924 to allocate resources and configure those resources required to fulfill the subscription order. The order provisioning module 1924 enables the allocation of resources for services ordered by a customer. The order provisioning module 1924 provides a level of abstraction between the cloud services provided by the cloud infrastructure system 1900 and the physical implementation layer used to provision resources to provide the requested services. Thus, the order orchestration module 1922 can be decoupled from implementation details such as whether services and resources are actually provisioned on the fly or pre-provisioned and only allocated / allocated when requested.

[0134] In operation 1944 , once the services and resources have been provisioned, a notification of the rendered services may be sent to the customer on the client devices 1904 , 1906 and / or 1908 by the order provisioning module 1924 of the cloud infrastructure system 1902 .

[0135] At operation 1946, the customer's subscription order may be managed and tracked by the order management and monitoring module 1926. In some examples, the order management and monitoring module 1926 may be configured to collect usage statistics for the services in the subscription order, such as the amount of storage used, the amount of data transferred, the number of users, and system up and down times.

[0136] In particular embodiments, cloud infrastructure system 1900 may include identity management module 1928. Identity management module 1928 may be configured to provide identity services, such as access management and authorization services in cloud infrastructure system 1900. In some embodiments, identity management module 1928 may control information about customers who wish to utilize services provided by cloud infrastructure system 1902. Such information may include information authenticating the identities of such customers and information describing what actions those customers are authorized to perform on various system resources (e.g., files, directories, applications, communication ports, memory segments, etc.). Identity management module 1928 may also include management of descriptive information about each customer, as well as information about how and by whom this descriptive information may be accessed and modified.

[0137] 20 illustrates an exemplary computer system 2000 on which various embodiments of the present invention may be implemented. The system 2000 may be used to implement any of the computer systems described above. As shown in the figure, the computer system 2000 includes a processing unit 2004 that communicates with several peripheral subsystems via a bus subsystem 2002. These peripheral subsystems may include a processing acceleration unit 2006, an I / O subsystem 2008, a storage subsystem 2018, and a communication subsystem 2024. The storage subsystem 2018 includes a tangible computer readable storage medium 2022 and a system memory 2010.

[0138] Bus subsystem 2002 provides a mechanism for allowing the various components and subsystems of computer system 2000 to communicate with one another as intended. Although bus subsystem 2002 is shown diagrammatically as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses. Bus subsystem 2002 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. For example, such architectures may include an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus, which may be implemented as a mezzanine bus manufactured to the IEEE P1386.1 standard.

[0139] Processing unit 2004, which may be implemented as one or more integrated circuits (e.g., conventional microprocessors or microcontrollers), controls the operation of computer system 2000. Processing unit 2004 may include one or more processors. These processors may include single-core or multi-core processors. In particular embodiments, processing unit 2004 may be implemented as one or more independent processing units 2032 and / or 2034 with single-core or multi-core processors included in each processing unit. In other embodiments, processing unit 2004 may be implemented as a quad-core processing unit formed by incorporating two dual-core processors on a single chip.

[0140] In various embodiments, the processing unit 2004 may execute various programs in response to program code and may maintain multiple programs or processes running simultaneously. At any given time, some or all of the program code to be executed may reside in the processor 2004 and / or the storage subsystem 2018. Through suitable programming, the processor 2004 may provide the various functions described above. The computer system 2000 may also additionally include a processing acceleration unit 2006, which may include a digital signal processor (DSP), special purpose processor, etc.

[0141] The I / O subsystem 2008 may include user interface input devices and user interface output devices. User interface input devices may include keyboards, pointing devices such as mice or trackballs, touch pads or touch screens, which are integrated with displays, scroll wheels, click wheels, dials, buttons, switches, keypads, audio input devices, along with voice command recognition systems, microphones, and other types of input devices. User interface input devices may include motion sensing and / or gesture recognizers, such as the Microsoft Kinect motion sensor, which allows a user to control and interact with an input device, such as a Microsoft Xbox 360 game controller, through a natural user interface using gestures and spoken commands. User interface input devices may also include eye gesture recognizers, such as the Google Glass blink detector, which detects eye movements from a user (e.g., "blinking" while taking pictures and / or making menu selections) and translates the eye gestures as input to the input device. The user interface input devices may also include a voice recognition sensing device that allows a user to interact with a voice recognition system (eg, the Siri® navigator) via voice commands.

[0142] User interface input devices may also include, but are not limited to, three-dimensional (3D) mice, joysticks or pointing sticks, game pads and graphic tablets, audio / visual devices such as speakers, digital cameras, digital camcorders, portable media players, webcams, image scanners, fingerprint scanners, barcode readers 3D scanners, 3D printers, laser range finders, and eye gaze detection devices. User interface input devices may also include medical imaging input devices such as, for example, computed tomography, magnetic resonance imaging, position emission tomography, and medical ultrasound equipment. User interface input devices may also include audio input devices such as, for example, MIDI keyboards, digital musical instruments, and the like.

[0143] User interface output devices may include display subsystems, indicator lights, or non-visual displays such as audio output devices, etc. Display subsystems may be flat panel displays such as those using cathode ray tubes (CRT), liquid crystal displays (LCD) or plasma displays, projection devices, touch screens, etc. In general, use of the term "output device" is intended to include all possible types of devices and mechanisms for outputting information from computer system 2000 to a user or to another computer. For example, user interface output devices may include, but are not limited to, various display devices that visually convey text, graphics, and audio / video information, such as monitors, printers, speakers, headphones, automobile navigation systems, plotters, voice output devices, and modems.

[0144] Computer system 2000 may include a storage subsystem 2018 that comprises software elements currently shown as located in system memory 2010. The system memory 2010 may store program instructions loadable and executable on the processing unit 2004, as well as data generated during the execution of these programs.

[0145] Depending on the configuration and type of computer system 2000, the system memory 2010 may be volatile (such as random access memory (RAM)) and / or non-volatile (such as read-only memory (ROM), flash memory, etc.). RAM typically contains data and / or program modules that are immediately accessible to the processing unit 2004 and / or that are currently being operated on and executed by the processing unit 2004. In some implementations, the system memory 2010 may include a number of different types of memory, such as static random access memory (SRAM) or dynamic random access memory (DRAM). In some implementations, a basic input / output system (BIOS), containing the basic routines that help to transfer information between elements within the computer system 2000, such as during start-up, may typically be stored in ROM. By way of example and not limitation, system memory 2010 also illustrates application programs 2012, program data 2014, and an operating system 2016, which may include client applications, a web browser, a mid-tier application, a relational database management system (RDBMS), and the like.As an example, operating systems 2016 may include various versions of Microsoft Windows, Apple Macintosh, and / or Linux operating systems, various commercially available UNIX or UNIX-like operating systems (including, but not limited to, various GNU / Linux operating systems, Google Chrome OS, etc.), and / or mobile operating systems such as iOS, Windows Phone, Android OS, BlackBerry 10 OS, and Palm OS operating systems.

[0146] The storage subsystem 2018 may also provide a tangible computer-readable storage medium for storing the basic programming and data constructs that provide the functionality of some embodiments. Software (programs, code modules, instructions) that, when executed by a processor, provide the above-described functionality may be stored in the storage subsystem 2018. These software modules or instructions may be executed by the processing unit 2004. The storage subsystem 2018 may also provide a repository for storing data used in accordance with the present invention.

[0147] The storage subsystem 2000 may also include a computer readable storage medium reader 2020 further connectable to a computer readable storage medium 2022. Together and optionally in combination with the system memory 2010, the computer readable storage medium 2022 may comprehensively represent remote, local, fixed and / or removable storage devices, as well as storage media for temporarily and / or permanently containing, storing, transmitting and retrieving computer readable information.

[0148] The computer readable storage medium 2022 containing the code or portions of the code may include any suitable medium known or used in the art. Such media includes storage media and communication media, such as, but not limited to, volatile and non-volatile, removable and non-removable media implemented in any manner or technology for storing and / or transmitting information. This may include tangible computer readable storage media, such as RAM, ROM, Electronically Erasable Programmable ROM (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disk (DVD), or other optical storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage, or other tangible computer readable media. This may also include intangible computer readable media, such as data signals, data transmissions, or any other media that can be used to transmit the desired information and that is accessible by the computing system 2000.

[0149] By way of example, computer readable storage medium 2022 may include hard disk drives that read from or write to non-removable, non-volatile magnetic media, magnetic disk drives that read from or write to removable, non-volatile magnetic disks, and optical disk drives that read from or write to removable, non-volatile optical disks, such as CD ROMs, DVDs and Blu-ray disks or other optical media. Computer readable storage medium 2022 may include, but is not limited to, Zip drives, flash memory cards, universal serial bus (USB) flash drives, secure digital (SD) cards, DVD disks, digital video tapes, and the like. Also, the computer-readable storage medium 2022 may include flash memory-based SSDs, enterprise flash drives, solid-state drives (SSDs) based on non-volatile memory such as solid-state ROM, SSDs based on volatile memory such as solid-state RAM, dynamic RAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs using a combination of DRAM and flash memory-based SSDs. Disk drives and their associated computer-readable media may provide computer-readable instructions, data structures, program modules, and other data to the computer system 2000.

[0150] The communications subsystem 2024 provides an interface with other computer systems and networks. The communications subsystem 2024 serves as an interface for receiving data from other systems and transmitting data from the computer system 2000 to other systems. For example, the communications subsystem 2024 may enable the computer system 2000 to connect to one or more devices via the Internet. In some embodiments, the communications subsystem 2024 may include a radio frequency (RF) transceiver component for accessing wireless voice and / or data networks (e.g., using cellular technology, advanced data network technologies such as 3G, 4G, or EDGE (enhanced data rates for global evolution)), a WiFi (IEEE 1902.11 family of standards or other mobile communications technologies or any combination thereof), a global positioning system (GPS) receiver component, and / or other components. In some embodiments, the communications subsystem 2024 may provide a wired network connection (e.g., Ethernet) in addition to or instead of a wireless interface.

[0151] Also, in some embodiments, the communications subsystem 2024 may receive incoming communications in the form of structured and / or unstructured data feeds 2026, event streams 2028, event updates 2030, etc., on behalf of one or more users who may be using the computer system 2000.

[0152] As an example, the communications subsystem 2024 may be configured to receive data feeds 2026, such as web feeds, such as Twitter® feeds, Facebook® updates, Rich Site Summary (RSS) feeds, in real time from users of social networks and / or other communications services, and / or receive real-time updates from one or more third party sources.

[0153] Additionally, the communications subsystem 2024 may be configured to receive data in the form of a continuous data stream. The data may include an event stream 2028 of real-time events and / or event updates 2030 that may be continuous or may be unbounded with essentially no clear ends. Examples of applications that generate continuous data may include, for example, sensor data applications, financial tickers, network performance measurement tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, and the like.

[0154] The communications subsystem 2024 may also be configured to output structured and / or unstructured data feeds 2026, event streams 2028, event updates 2030, etc. to one or more databases that may be in communication with one or more streaming data source computers coupled to the computer system 2000.

[0155] The computer system 2000 may be one of a variety of types, including a handheld mobile device (e.g., an iPhone® mobile phone, an iPad® computing tablet, a PDA), a wearable device (e.g., a Google Glass® head mounted display), a PC, a workstation, a mainframe, a kiosk, a server rack or other data processing system.

[0156] Due to the ever-changing nature of computers and networks, the description of the computer system 2000 shown in the figure is intended only as a specific example. Many other configurations are possible having more or fewer components than the system shown in the figure. For example, customized hardware may be used and / or particular elements may be implemented in hardware, firmware, software (including applets), or a combination. Additionally, connections to other computing devices, such as network input / output devices, may be utilized. Based on the disclosure and teachings provided herein, one of ordinary skill in the art will appreciate other means and / or methods for implementing the various embodiments.

[0157] In the preceding description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of various embodiments of the present invention. However, it will be apparent to one skilled in the art that embodiments of the present invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form.

[0158] The above description provides only exemplary embodiments and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of exemplary embodiments will provide those skilled in the art with an enabling description for implementing the exemplary embodiments. It should be understood that various changes can be made in the function and arrangement of elements without departing from the spirit and scope of the invention as set forth in the claims.

[0159] In the above description, specific details are given to provide a thorough understanding of the embodiments. However, it will be understood by those skilled in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form so as not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail so as to avoid obscuring the embodiments.

[0160] It is further noted that particular embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe operations as a sequential process, many of the operations may be performed in parallel or simultaneously. Additionally, the order of operations may be rearranged. A process is terminated when the operations are completed, but may include additional steps not included in the diagram. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or to the main function.

[0161] The term "computer-readable medium" includes, but is not limited to, portable or fixed storage devices, optical storage devices, wireless channels, and various other media capable of storing, containing, or carrying instructions and / or data. A code segment or machine-executable instructions may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

[0162] Furthermore, the embodiments may be implemented in hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware, or microcode, the program code or code segments to perform the necessary tasks may be stored on a machine-readable medium. A processor may perform the necessary tasks.

[0163] In the above specification, aspects of the invention are described with reference to specific embodiments thereof, but those skilled in the art will recognize that the invention is not limited thereto. The various features and aspects of the above invention may be used individually or together. Moreover, the embodiments can be utilized in a variety of environments and applications beyond those described herein without departing from the broader spirit and scope of the specification. The specification and drawings should therefore be regarded as illustrative rather than restrictive.

[0164] Furthermore, for purposes of illustration, the methods have been described in a particular order. It should be understood that in alternative embodiments, the methods may be performed in an order different from that described. It should also be understood that the methods described above may be performed by hardware components or embodied in a sequence of machine-executable instructions that, when used, cause a machine, such as a general-purpose or special-purpose processor or logic circuitry programmed with such instructions, to perform the method. These machine-executable instructions may be stored on one or more machine-readable media, such as a CD-ROM or other type of optical disk, floppy disk, ROM, RAM, EPROM, EEPROM, magnetic or optical card, flash memory, or other type of machine-readable medium suitable for storing electronic instructions. Alternatively, the methods may be performed by a combination of hardware and software.

Claims

1. 1. A method for visualizing time series data in an interactive virtual environment, comprising: Receiving one or more data sets comprising a plurality of time series sequences of data points; plotting each of the plurality of time series sequences of data points on a three-dimensional (3D) line graph in a virtual environment; generating one or more views of the 3D line graph using one or more virtual cameras configured to move around the 3D line graph in the virtual environment; transmitting the one or more views of the 3D line graph to one or more client devices, the one or more client devices corresponding to the one or more virtual cameras, the method further comprising: Loading a visualization component with parameterized input; binding the one or more datasets to the parameterized input; plotting each of the plurality of time series sequences of data points on the 3D line graph in the virtual environment according to the visualization component; receiving an operation on the visualization component in the virtual environment; and modifying a dataset bound to the visualization component based on the manipulation.

2. Plotting each of the plurality of time series sequences of data points in a 3D line graph in a virtual environment includes: plotting a position of each data point in the plurality of time series sequences of data points in a coordinate system of the virtual environment; and connecting each of the locations to a 3D line object.

3. The method of claim 2 , further comprising transforming a coordinate system of the 3D line graph to the coordinate system of the virtual environment.

4. The coordinate system of the 3D line graph is: a first horizontal axis corresponding to time; a second horizontal axis corresponding to an index in the time series sequence of the data points; and a vertical axis corresponding to the values ​​of the data points.

5. The method of any of claims 1 to 4, wherein the one or more data sets comprise test failure data over time for different systems.

6. The method of any preceding claim, wherein a client device in the one or more client devices comprises a virtual reality device.

7. The operation on the visualization component includes touching the visualization component, 7. The method of claim 1, wherein modifying the dataset comprises modifying a value or time corresponding to a touched location in the visualization component, or displaying the dataset differently than other datasets.

8. A program for causing one or more processors to execute the method according to any one of claims 1 to 7.

9. one or more processors; A system comprising: a memory storing a program for causing said one or more processors to execute a method according to any one of claims 1 to 7.

Citation Information

Patent Citations

  • Graph processor and storage medium

    JP1999031185A

  • Graph display method and graph display device

    JP2003067760A

  • Device and method for totaling human resources data

    JP2004355167A

  • Systems and Methods for Data Visualization Using Three-Dimensional Displays

    US20170092008A1