Patent Grant
12039105
The present invention relates to frameworks, devices and methods configured for enabling touch/gesture controlled display for facility information and content. Embodiments of the invention have been particularly developed for enabling gesture-based interaction between a touch/gesture controlled display and other networked devices. While some embodiments will be described herein with particular reference to that application, it will be appreciated that the invention is not limited to such a field of use, and is applicable in broader contexts.
Any discussion of the background art throughout the specification should in no way be considered as an admission that such art is widely known or forms part of common general knowledge in the field.
There are a wide range of information systems configured to provide access to information regarding facility information, for example building systems such as HVAC, access control, surveillance, and so on. These information systems tend to rely on tree-structures for navigation, and are optimized for use via a traditional PC-style interface (i.e. keyboard and mouse).
It is an object of the present invention to overcome or ameliorate at least one of the disadvantages of the prior art, or to provide a useful alternative.
One embodiment provides a computer implemented method for displaying building information to a user via a touch/gesture driven user interface that is rendered on a display screen, the method including:
One embodiment provides a computer implemented method for displaying building information to a user via a touch/gesture driven user interface that is rendered on a display screen, the method including:
One embodiment provides a computer implemented method for sharing content, the method including:
One embodiment provides a computer implemented method for sharing content, the method including:
One embodiment provides a computer implemented method for displaying building information to a user via a touch/gesture driven user interface that is rendered on a display screen, the method including:
One embodiment provides a computer program product for performing a method as described herein.
One embodiment provides a non-transitive carrier medium for carrying computer executable code that, when executed on a processor, causes the processor to perform a method as described herein.
One embodiment provides a system configured for performing a method as described herein.
Reference throughout this specification to “one embodiment”, “some embodiments” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases “in one embodiment”, “in some embodiments” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments.
As used herein, unless otherwise specified the use of the ordinal adjectives “first”, “second”, “third”, etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.
In the claims below and the description herein, any one of the terms comprising, comprised of or which comprises is an open term that means including at least the elements/features that follow, but not excluding others. Thus, the term comprising, when used in the claims, should not be interpreted as being limitative to the means or elements or steps listed thereafter. For example, the scope of the expression a device comprising A and B should not be limited to devices consisting only of elements A and B. Any one of the terms including or which includes or that includes as used herein is also an open term that also means including at least the elements/features that follow the term, but not excluding others. Thus, including is synonymous with and means comprising.
As used herein, the term “exemplary” is used in the sense of providing examples, as opposed to indicating quality. That is, an “exemplary embodiment” is an embodiment provided as an example, as opposed to necessarily being an embodiment of exemplary quality.
Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings in which:
Described herein are frameworks, devices and methods configured for enabling display for facility information and content, in some cases via touch/gesture controlled interfaces. Embodiments of the invention have been particularly developed for allowing an operator to conveniently access a wide range of information relating to a facility via, for example, one or more wall mounted displays. While some embodiments will be described herein with particular reference to that application, it will be appreciated that the invention is not limited to such a field of use, and is applicable in broader contexts.
In overview, the technologies described herein are predominately intended to facilitate provision of a rich user interface for rendering on one or more touch/gesture controlled displays, such as wall-mounted glass displays. Such displays are preferably relatively large, for example having a screen size in excess of 42 inches.
As used herein, the term “touch/gesture controlled” refers to a display/interface in respect of which the primary mode of control is either touch (for example via touchscreen input technology) or gesture (for example via a motion sensor arrangement), or by way of a combination of touch and gesture. The term “gesture” should be read sufficiently broadly to include gestures made via a touchscreen interface and gestures made for recognition by motion sensing equipment (and other such feature-recognizing equipment). There may be additional modes of control present, including the likes of voice or peripheral inputs (such as keyboards, mice, touch devices, and so on).
In some cases, aspects of the technology are described by reference to functionalities provided/observed via a user interface. In such cases, embodiments may take the form of client, server, and other computing devices (and methods performed by those devices) thereby to provide such functionalities.
Technologies described below provide for a touch/gesture controlled interface that enables an operator to access information and content relating to a facility (for example a building or a region including multiple buildings). This information and content may relate to one or more “facility systems” or “building systems” (with the term “facility” being used to describe a site defined by one or more buildings and/or other locations), being systems defined by information technology components that make available such information and/or content. Examples of such facility systems include:
Video surveillance systems, which provide access to live video data from one or more cameras located in the facility.
HVAC systems, which provide access to control and monitoring of HVAC components (such as chillers, air handling unity, thermostats, and so on). This may be provided by a broader building management system.
Access control systems, which include access control devices and associated control systems (for example to control access through doors and the like, and monitor movement through such doors).
Energy management systems, which provide access to monitoring and/or controlling of energy consumption in a building.
A general objective for technologies described herein is to provide an effective, powerful, and easy-to-use touch/gesture controlled user interface, and associated back-end framework.
Framework Overview
A first exemplary framework is illustrated in
A touch/gesture driven display 101, which is configured to enable rendering of a map-based user interface 100.
A display driver terminal 110, which is configured for driving user interface 100 (for example in terms of processing user inputs, obtaining data from remote sources, and rendering data on the display. This is either integrated with display 101, or coupled to display 101 by a HDMI cable (or other form of data cable).
A tile data server, which maintains map and layer data for the map-based user interface 100. This is configured to communicate with display driver terminal 110 via a network connection.
A set of facility system IT components which provide data underlying content accessible via interface 100. These include a surveillance system 130 (which includes a plurality of cameras 131), a building management system 132 (which includes HVAC components, sensors, etc 133), and access control system 134 (which includes access control devices, servers, etc 135) and another system 136 (which includes devices/components 137). These communicate with driver 110 via network communications, optionally via one or more intermediary servers (not shown).
An alternate multi-screen arrangement is illustrated in
Map-based navigation interface 100 includes image data representing a map, such as a floorplan. This is rendered on-screen as a map layer (for example a background map layer). Overlaid on the image data representing a map are various objects, including a plurality of content control objects (CCOs) 102. In some embodiments described herein, CCOs take the form of orbital menu objects. However other GUI components may be used, for example CCOs such as those described by reference to
Interface 100 is able to be navigated in terms of pan and zoom. For example, motion/touch gestures such as swiping, pinching, and the like may be used to effect such navigation as is customary for touch/gesture driven displays. The manner by which interface handles such navigation is dealt with in more detail below.
In this embodiment, interface 100 is provided by way of display driver 110, which may be provided via a computing device having an interface able to be coupled to display 101 (for example an HDMI output or the like). Display driver 110 includes a processor 111 that enables execution of software instructions, for example software instructions maintained on a memory module 112. Communications modules 113 (such as Ethernet network adaptors, WiFi, or the like) enable interaction with remote devices. In this regard, various software functionalities provided via interface 100 may be derived from software executing at display driver 110 and/or at other distributed terminals. For instance, whether a given functionality is provided by locally or merely executing code may be a matter of design choice, based upon optimization of resources. In this regard, any functionality/data shown in
Memory module 112 maintains software instructions for a user interface module which is configured to control rendering of interface 100. This user interface module is responsive to user inputs (via input components 114, which may include touch-based and gesture-based inputs, and the like) for controlling interface 100. Controlling display 100 includes the likes of processing inputs indicative of commands for zooming, panning, accessing content, shifting vertical levels, and so on (discussed in more detail further below), and processing those inputs thereby to provide desired functionality.
In terms of panning and zooming, in the embodiment of
User Interface Components
A background map layer 201 is illustrated, in this case being a substantially two-dimensional isometric floorplan. This shows artefacts such as walls, doors, stairs, and the like. The floorplan may show a single building, or multiple buildings (with intermediate areas). The floorplan may include multiple substantially two-dimensional images representing different vertical zones (such as floors in a building). In some cases only a single vertical zone is displayed, with a navigation interface allowing navigation between vertical zones. In other cases multiple separate map images for respective vertical zones are shown alongside one another. In such cases preferably visual features (such as colored lines) are provided thereby to indicate pathways between levels, for instance at stairwells and lifts. By way of example, in one embodiment a colored line connects a stairwell in one map image to a corresponding stairwell in another map image, thereby to visually indicate functional connection between the stairwells.
Content control objects (CCOs) 202a and 202b are shown. CCO 202a includes a camera icon, and is bound to a resource in the form of a camera managed by a surveillance system. CCO 202b is bound to the resource in the form of an access control device managed by an access control system.
CCO 202a is able to be operated by a user thereby to launch a content display object 203 (in this case being a video display object), which is configured to display a content item (in this case being streaming live video) for its bound resource (in this case being a camera). Various other forms of content display objects and content items may be present, for example depending on the nature of resources to which CCOs are bound.
Content Control Objects (CCOs)
As noted above, interface 100 includes a plurality of content control objects (CCOs) 102, which are overlaid on (or otherwise visible within) a map-based interface. For example, a CCO may be defined by menu objects, such as a radial/orbital menu object. This allows a user to interact with a CCO thereby to access content, for example to launch a display object for a desired content item (for example to view live video data from a camera). In some cases a CCO is configured to automatically launch a display object where predefined conditions are met (for example to enable automated launching of video display objects when a user navigates to a predefined pan and zoom location). These predefined conditions may include alert conditions (for instance, in one example an alert is raised for a given camera when motion is sensed, and that causes automatic launching of a video display object).
Each CCO is bound to one or more facility system components, such as one or more cameras of surveillance system 130, a sensor of a component monitored by building management system 132, and so on. This binding is configured to enable at least either or both the following: A user of interface 100 to access content made available by the facility system component (for example live video data from a camera, or a value from a sensor). For example, by clicking on a CCO, a user is able to access such content, which is preferably displayed overlaid on the map display (optionally in a content display layer).
Downstream pushing of data from the component (or supporting system) to interface 100, for example where an alarm condition has been reached. For example, a visual alarm indicator may be applied to or adjacent a CCO based on such downstream pushing of data.
Data indicative of CCOs is maintained at a server device, optionally being a server device that is additionally responsible for delivering image data for the map.
In some embodiments, a CCO is defined by data indicative of:
A position on the map at which the CCO is to be located (which may vary depending of zoom position and/or CCO aggregation rules).
A reference to the resource to which the CCO is bound (or, in some cases, resources to which the CCO is bound). This allows binding and/or other data sharing to occur.
Data indicative of display parameters. This may include data indicative of an icon for the CCO (for example a CCO bound to a camera in a surveillance system may carry a camera icon). It may also include instructions for the provision of user interface components (for example menu items that are to be displayed via an orbital menu, and how those operate) for example via JavaScript Object Notation (JSON).
This allows a CCO to be loaded in a functional manner for the purposes of interface 100. CCO processing operations (for example data handling) may be performed at a client or server side (or a combination of both) depending on matters of subjective choice in specific implementations.
Background Map Layer
As noted above, interface 100 includes a background map layer. The map may be two or three dimensional, although in the case of three dimensional maps it is preferable that it represents a region of substantially common vertical position (for example a single floor in a building). In some examples multiple maps maintained in a stackable form, thereby to allow an operator to view different vertical positions (for example a separate map for each floor of a building, with each map being defined relative to a common set of referential spatial coordinates). In the example of
Data to enable the rendering of the background map layer at a variety of resolutions is maintained in background tile data 121 of tile data server 120. In this regard, a tile-based approach is used to manage display and resolution, as shown in
In the context of the background map layer, level 301 is defined by a full mapped view of a facility (in this example represented by an oval shape), defined at a predefined resolution level. This predefined resolution level is optionally selected based on a maximum optimal resolution for display device 101 (or based on a maximum optimal resolution for an anticipated display device, based on current technological norms). Level 302 is defined by four partial views, each of which being defined at the same predefined resolution level as the entire view of level 301. That is, in terms of total number of pixels, the four tiles of level 302 define, in combination, four times the number of pixels as the single tile at level 301. In level 303 there are sixteen tiles, again each at the same predefined resolution level as the tiles at levels 301 and 302. This means that, by way of example, a much greater level of detail and granularity of the map is able to be provided in the tiles at level 303 compared with levels 302 and 301.
In terms of operation, based upon a navigation command (such as a pan or zoom), display driver 110 provides positional information to server 120. This positional information is indicative of location (for example relative to set of axis defined relative to the overall full view map in 301) and a zoom state. Based on this positional information, server 120 selectively delivers image data from one or more tiles for the background map layer.
As an example, assume level 301 represents a zoom value of 100%, level 2 represents a zoom value of 200%, and level 3 represents a zoom value of 400%. For zoom levels from 100% to <200%, a zoom operation is applied directly to the single tile of level 301. Once the zoom level reaches/surpasses 200%, tile server 120 delivers image data from one or more of the tiles of level 302 (depending on vie position relative to tile boundaries). Preferably, on transition between tiles, the preceding tile is used at non-optimal resolution as a preview during download and rendering of the new tile.
Tile-Based CCO Management
In some embodiments, CCOs displayed in response to zoom position, with an increased number of CCOs becoming visible at higher zoom levels. This may be achieved by reference to the tile-based approach discussed above that is used for the background layer. That is, CCO positions are defined for each tile, so that when a tile is loaded for the background image, CCOs for positions defined for that tile are also loaded.
Manually defining each content layer tile, by defining locations for CCOs.
A set of automated rules for CCO amalgamation, such that where a predefined CCO density is met (for example in terms of proximity, number on-screen, etc) those are automatically combined into a single CCO from which content from both constituent CCOs is accessible. By such an approach, CCOs need only be manually created at the lowest level (i.e. for each tile at level 303 in
A combination of manual definition and automated rules.
Preferably, upward amalgamation of CCOs results in a child-parent relationship (in the case of
So as to provide an example, consider a set of four level 303 tiles which correspond to a common single level 302 tile. Assume there are four camera-type CCOs across the set of four level 303 tiles (although not necessarily one in each), with each of those CCOs being bound to a respective individual camera. That is, each of those CCOs allows a user to launch a video window pop-up from its respective camera. These four CCOs at level 303 are replaced by a single camera-type CCO at level 302, with this level 302 CC) being bound to all four cameras (and being configured to allow a user to launch a video window pop-up from any of the four cameras, or in some cases a multi-camera view comprising live video from all four).
CCO Layers
In some embodiments, CCOs are defined in multiple content layers (shown in terms of layer data 121a-n in
In some embodiments, CCO aggregation may occur by combining CCOs from separate layers. For example, based on an aggregation algorithm, where two CCOs are to be displayed, and these are located within a threshold proximity, an algorithm is executed to combine their respective display parameter data (for example combining JSON data) thereby to provide a single CCO that provides all (or a selection of) the functionalities that would otherwise be provided by two separate CCOs.
CCO layers are also helpful in enabling filtering of CCO display, for example in based on user attributes and/or user-defined filters. This is discussed further below.
CCO Display Relative to Zoom Level
In various embodiments, as a result of CCO layers, tile-based management, or other approaches, logic that determines which CCOs are displayed is related to a zoom level. That is, a given CCO is visible by default only once a prerequisite zoom level is reached.
In some embodiments, this aspect of the technology is enhanced by way of rules which define circumstances in which a given CCO may be visible at a zoom level preceding its prerequisite. This includes defining conditions (for example the presence of an alarm condition) which, if satisfied, result in either (i) a given CCO being visible at all zoom levels; or (ii) a given CCO being visible at a zoom level directly or indirectly preceding its prerequisite zoom level.
CCO Display Management Based on User Attributes
In some embodiments, interface 100 is configured such that CCOs are displayed based on one or more attributes of a user (operator). That is, a user provides credentials to access interface 100, and based on these credentials (which may reference user attributes stored in a remote database), decisions are made (preferably at a server level) as to which CCOs are to be displayed in interface 100. In this regard, one embodiment provides a computer implemented method for displaying building information to a user via a touch/gesture driven user interface that is rendered on a display screen, the method including:
This method operates on the basis that the set of CCOs is selected from a collection of available CCOs based upon: (a) the current navigation data (for example defined in terms of pan and zoom position); and (b) one or more attributes of the user.
In some cases each CCO is bound to at least one building resource, the one or more attributes of the user are indicative of access rights for building resources, and the set of CCOs is selected from the collection of available CCOs based upon the user's access rights with respect to the building resources to which the CCOs are bound. For example, a certain user has access only to view surveillance footage, and so only CCOs bound to cameras are shown.
In some cases, there is a plurality of building resource categories, wherein each building resource belongs to a building resource category. The one or more attributes of the user are indicative of access rights for building resource categories, and the set of CCOs is selected from the collection of available CCOs based upon the user's access rights with respect to the building resources to which the CCOs are bound. For example, this may be used in conjunction with a layer approach as disused above. Rather than determining whether or not to show a CCO on a per-CCO basis, the decision is made on a layer basis.
The user attributes may include the likes of a tag in a user ID file, permissions in a permissions table, or substantially any other approach. Preferably, each CCO includes data of the required user attribute (e.g. access permission) required.
In some cases the user attributes additionally include filtering parameters set by the user. For example, a user with access to video CCOs and HVAC CCOs may choose to filter thereby to only show video CCOs. In some cases the technical mechanisms for determining which CCOs are displayed vary between situations where access permissions are processed and where filters are processed.
In cases where a CCO is bound to multiple resources, user-attribute display involves additional challenges. That is, the CCO may appear differently depending on the user's attributes. There are a few ways in which this is managed in embodiments, for example:
A one-to-one relationship between CCOs and resources. CCOs may be aggregated together based on a set of rules, but this aggregation is performed following a determination as to which CCOs are to be displayed. For example, in respect of one user a map position (location and zoom level) may include a video CCO and HVAC CCO aggregated together, but for another use that same map position may only include the video CCO (if the user does not have access rights for HVAC, or has filtered out HVAC).
Algorithms for enabling modification of data for a CCO that is bound to multiple resources, such that content is available only for a resource where the user has access.
Using multiple CCO definitions for multi-resource-mound CCOs, so that separate data is stored to allow loading for a reduced number of the bound resources where appropriate.
CCO display management based on user attributes is very useful in the context of interface 100, as it allows a single interface framework to server multiple purposes, based on varying operator scope of responsibilities, access rights, roles, and current tasks. Interface 100 is therefore, at the back end, able to be configured to provide a wide range of rich content, whilst at the front end only content determined to be appropriate for a given user is displayed on the map.
User-Specific Content Layer
In some embodiments a user is able to customize the location of CCOs. For example, a user is able to add a new CCO, which includes selecting a resource to which it is to be bound. The newly created CCO may reside in a user-specific content layer, which is in some cases available only to that user (and loaded automatically for that user), and in other cases published to other users.
In some embodiments a user is additionally/alternately enabled to customize menu items accessible from a given CCO. Again, in some cases these customizations are made exclusively for the user in question, and in other cases they are published for other users (for example by updating the CCO data such that updated CCO data is loaded by the next user to navigate to a position containing that CCO).
Multi-Level Map Navigation
As noted above, in some cases only a single vertical zone is displayed via the background map layer, even in the case of a multi-level facility. In such cases, a navigation interface may be provided thereby to enable navigation between vertical zones (for example between floors).
One embodiment provides a method including, displaying, in a primary region of the user interface, a first map layer, wherein the first map layer includes image data representative of a facility, wherein the user interface is navigated by way of pan and zoom operations defined with respect to the map layer. The method also includes displaying a multi-level navigation interface, wherein the multi-level navigation interface displays a series of stacked map layer previews. The stacked map layer previews are defined relative to a common origin. That is, a certain longitude-latitude coordinate set is commonly defined across all map layers, allowing those layers to be stacked in a meaningful manner. In some embodiments the navigation interface is superimposed on the map layer.
In this case, one map layer preview is representative of the first map layer and another map layer preview is representative of a second map layer. A user is enabled a user to interact with the multi-level navigation interface thereby to select a desired one of the stacked map layer previews. For example, this may include a gesture driven selection, optionally effectively scrolling upwards/downwards through the stack. In response to the user's selection of the map layer preview representative of a second map layer, the second map layer is displayed in the primary region of the user interface.
In some cases the series of stacked map layers are defined by two-dimensional isometric views stacked thereby to provide a three-dimensional representation of a building defined by floors respectively represented by the layers. This is shown in
In some cases prior to the user's selection of the map layer preview representative of a second map layer, the first map later is displayed for a region having a boundary defined in horizontal dimensions, and in response to the user's selection of the map layer preview representative of a second map layer, the second map layer is displayed in the primary region of the user interface for a region having the same boundary defined in terms of horizontal dimensions. That is, the user views the same region (in horizontal aspects) of a different level.
In some embodiments, in the case the pan and zoom location for the first map layer meet a first set of conditions, a first multi-level interface is displayed, and wherein, in the case the pan and zoom location for the first map layer meet a second set of conditions, a second multi-level interface is displayed. For example, this may be used for a multi-building facility: the multi-level interface is shown in respect of a building proximal (or defined around) the user's current navigation position.
Persistent Content Positioning
In some embodiments the user interface is configured to enable persistent display of launched content display object at a launch location. This is configured such that, following navigation away from a map position such that a given content display object is no longer on-screen, and return to that map position, which requires re-loading of map image data for that position, the given content display object remains in its launch location. That is, loaded content display objects appear to remain in persistent positions (relative to the map) as a user navigates the map. In some embodiments, in response to a user command via a content display object to launch a content item, storing context information for the launched content item, thereby to enable management of persistent display. Additionally, in the interests of conserving network and other computing resources, streaming of content by a given content display object is ceased when the given content item is not displayed on-screen.
Preferably, persistent display is able to be controlled by the user. For example, some embodiments provide a mechanism for the user to, by way of a single command, close all persistently displayed content display object. In another example, the user interface provides functionality for a user to select whether a given content display object is to be persistently displayed or, alternately, is to automatically close following navigation that causes the content item to no-longer be on-screen.
Transition of Content Between Map-Bound and Map-Unbound Layers
As discussed above, an operator is enabled to launch various content display objects within interface 100, for example a display object configured to present live video from a camera. In some cases, as noted above, the position of a content display item, once launched, is persistent, in that a user upon navigating away from, and subsequently returning to, a given map view position, content items launched for display at that position remain in place. Such content display objects may be considered as being map-bound, in that they are bound to the map in terms of pan and/or zoom operations. That is, the content display object remains the same size and position relative to the background map layer during operator-controlled navigation (for example a content display object becomes smaller during a zoom-out navigation).
In some embodiments, a user is enabled to transition content between a map-bound layer and a map-unbound layer. That is, such embodiments provide a computer implemented method including enabling the user to move a given display object between:
(i) a map bound layer, wherein the display object is bound to the map layer for pan and/or zoom operations; and
(ii) a map unbound layer, wherein the position and/or size of the display object remains constant relative to the display screen independent of pan and/or zoom operations.
In some embodiments, when in the map bound layer, the display object is bound to the map layer for pan and zoom operations. In some embodiments, in the map unbound layer, the position and/or size of the display object remains constant relative to the display screen independent of pan and zoom operations. In some embodiments, in the map unbound layer, both the position and size of the display object remains constant relative to the display screen independent of pan and/or zoom operations.
The manner by which a display object is transitioned between the map-bound layer and map-unbound layer varies between embodiments. An exemplary approach is to use a “throw” gesture for progressing a given display object from the map bound layer to the map unbound layer. That is, interface 100 is configured to recognize a “throw” gesture made in respect of a content display object as a command not only to move the object made on the “throw” attributed (e.g. velocity and trajectory), but also as a command to transition the content item to a map-unbound layer. Handling of the map-unbound layer may be achieved via data and processing at the client or a server as matter of design choice.
Sharing of Content to Networked Devices Some embodiments enable sharing of content between display 101 and other networked devices. For example, in one embodiment, in response to a “throw” gesture having predefined characteristics, the terminal providing interface 100 is configured for providing a signal to a second terminal in networked communication with the first terminal, thereby to make the content associated with a building resource. This is illustrated in
In some cases the user interface includes a plurality of peripheral throw locations, wherein each location is selectively associable with a specific remote terminal, wherein a “throw” gesture for a display object having characteristics representative of a given throw location cause the providing of a signal to the associated specific remote terminal in networked communication with the first terminal, thereby to make the content associated with a building resource. For example, a user is able to manually associate each throw location with a desired terminal.
In some embodiments sensing equipment is configured to determine the relative location of the second terminal with respect to the first terminal, thereby to enable determination of whether the “throw” gesture has a trajectory towards the second terminal. The sensing equipment may include image sensing equipment, coupled to either or both of the first terminal or the second terminal.
Multi-Modal Operation
In some embodiments a touch/gesture driven user interface is simultaneously controllable by multiple modes, including at least one gesture-driven mode, and at least voice-driven mode. Preferably, panning and zooming operations with respect to the map layer are controllable using commands including the name data for the building resources. In this regard, a voice-command processing module is optionally configured to have access to the name data, thereby to enable processing of voice commands in the at least one voice driven mode, wherein those commands are indicative of one or more aspects of the name data. The voice-command processing module is responsive to a command indicative of name data for a given one of the building resources for performing a command in respect of that building resource. This may include, in response to a predefined voice command indicative of name data for a given one of the building resources, the user interface is configured to navigate to an optimal map layer position, in terms of pan and zoom, for displaying that given one of the building resources.
By way of example, building resources may be named according to a location-specific hierarchy derived naming convention, for example: BuildingA, BuildingA/Level2, BuildingA/Level2/ConferenceRoom, and BuildingA/Level2/ConferenceRoom/Cameral. A given voice command may be matched against this name to determine whether it is likely to refer to that building resource. This need not require the full name or all aspects. For example, a voice command including “conference room” and “camera 1” may uniquely identify that resource (for example if there is only a single ConferenceRoom defined in the name data). The voice command processing is also preferably context dependent, favoring name data for resources shown on-screen. For example, if only one resource including Cameral in its name is shown on-screen, then a command including “camera 1” is inferred to relate to that resource.
Multi-Screen Implementation
In some embodiments, the user interface is provided over multiple displays. An example is illustrated in
A second screen 602 provides an object detail view, which is configured to provide a detailed view for a plurality of content items referenced by CCOs. For example, this may including displaying a plurality of video display objects, each providing a live video feed from a respective camera (with each camera being referenced by a given CCO). Other examples include display objects that provide status and/or configuration information for other facility items, such as access control devices, HVAC components, and so on.
Preferred embodiments provide a functionality whereby the system is configured to define a view on screen 602 responsive to CCOs visible on screen 601. This may occur automatically (for example following map repositioning) or responsive to a user command (for example the user clicks a button to “throw” a new view to screen 602 based on currently visible CCOs.
Screens 601, 602 and 603 are driven by processing components 604, which may include multiple processing units. A common keyboard and mouse is preferably coupled to processing components 604, and configured to enable movement of a mouse cursor between all three screens.
Alternate CCO Implementation
Further interaction expands display 702 to provide an expanded detailed display, which additionally includes object controls 704 (for example video controls, such as rewind, record, pause, PTZ, and the like) and other controls 705. In some cases the other controls enable a user to associate links to other system user interface objects/views with the CCO.
It will be appreciated that the disclosure above provides various significant systems, methods, frameworks and methodologies for enabling display of facility information and surveillance data via a map-based user interface.
Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilizing terms such as “processing,” “computing,” “calculating,” “determining”, analyzing” or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities into other data similarly represented as physical quantities.
In a similar manner, the term “processor” may refer to any device or portion of a device that processes electronic data, e.g., from registers and/or memory to transform that electronic data into other electronic data that, e.g., may be stored in registers and/or memory. A “computer” or a “computing machine” or a “computing platform” may include one or more processors.
The methodologies described herein are, in one embodiment, performable by one or more processors that accept computer-readable (also called machine-readable) code containing a set of instructions that when executed by one or more of the processors carry out at least one of the methods described herein. Any processor capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included. Thus, one example is a typical processing system that includes one or more processors. Each processor may include one or more of a CPU, a graphics processing unit, and a programmable DSP unit. The processing system further may include a memory subsystem including main RAM and/or a static RAM, and/or ROM. A bus subsystem may be included for communicating between the components. The processing system further may be a distributed processing system with processors coupled by a network. If the processing system requires a display, such a display may be included, e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT) display. If manual data entry is required, the processing system also includes an input device such as one or more of an alphanumeric input unit such as a keyboard, a pointing control device such as a mouse, and so forth. The term memory unit as used herein, if clear from the context and unless explicitly stated otherwise, also encompasses a storage system such as a disk drive unit. The processing system in some configurations may include a sound output device, and a network interface device. The memory subsystem thus includes a computer-readable carrier medium that carries computer-readable code (e.g., software) including a set of instructions to cause performing, when executed by one or more processors, one of more of the methods described herein. Note that when the method includes several elements, e.g., several steps, no ordering of such elements is implied, unless specifically stated. The software may reside in the hard disk, or may also reside, completely or at least partially, within the RAM and/or within the processor during execution thereof by the computer system. Thus, the memory and the processor also constitute computer-readable carrier medium carrying computer-readable code.
Furthermore, a computer-readable carrier medium may form, or be included in a computer program product.
In alternative embodiments, the one or more processors operate as a standalone device or may be connected, e.g., networked to other processor(s), in a networked deployment, the one or more processors may operate in the capacity of a server or a user machine in server-user network environment, or as a peer machine in a peer-to-peer or distributed network environment. The one or more processors may form a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
Note that while diagrams only show a single processor and a single memory that carries the computer-readable code, those in the art will understand that many of the components described above are included, but not explicitly shown or described in order not to obscure the inventive aspect. For example, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
Thus, one embodiment of each of the methods described herein is in the form of a computer-readable carrier medium carrying a set of instructions, e.g., a computer program that is for execution on one or more processors, e.g., one or more processors that are part of web server arrangement. Thus, as will be appreciated by those skilled in the art, embodiments of the present invention may be embodied as a method, an apparatus such as a special purpose apparatus, an apparatus such as a data processing system, or a computer-readable carrier medium, e.g., a computer program product. The computer-readable carrier medium carries computer readable code including a set of instructions that when executed on one or more processors cause the processor or processors to implement a method. Accordingly, aspects of the present invention may take the form of a method, an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of carrier medium (e.g., a computer program product on a computer-readable storage medium) carrying computer-readable program code embodied in the medium.
The software may further be transmitted or received over a network via a network interface device. While the carrier medium is shown in an exemplary embodiment to be a single medium, the term “carrier medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “carrier medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by one or more of the processors and that cause the one or more processors to perform any one or more of the methodologies of the present invention. A carrier medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical, magnetic disks, and magneto-optical disks. Volatile media includes dynamic memory, such as main memory. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise a bus subsystem. Transmission media also may also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications. For example, the term “carrier medium” shall accordingly be taken to included, but not be limited to, solid-state memories, a computer product embodied in optical and magnetic media; a medium bearing a propagated signal detectable by at least one processor of one or more processors and representing a set of instructions that, when executed, implement a method; and a transmission medium in a network bearing a propagated signal detectable by at least one processor of the one or more processors and representing the set of instructions.
It will be understood that the steps of methods discussed are performed in one embodiment by an appropriate processor (or processors) of a processing (i.e., computer) system executing instructions (computer-readable code) stored in storage. It will also be understood that the invention is not limited to any particular implementation or programming technique and that the invention may be implemented using any appropriate techniques for implementing the functionality described herein. The invention is not limited to any particular programming language or operating system.
It should be appreciated that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, FIG., or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.
Furthermore, while some embodiments described herein include some but not other features included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention, and form different embodiments, as would be understood by those skilled in the art. For example, in the following claims, any of the claimed embodiments can be used in any combination.
Furthermore, some of the embodiments are described herein as a method or combination of elements of a method that can be implemented by a processor of a computer system or by other means of carrying out the function. Thus, a processor with the necessary instructions for carrying out such a method or element of a method forms a means for carrying out the method or element of a method. Furthermore, an element described herein of an apparatus embodiment is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention.
In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it is to be noticed that the term coupled, when used in the claims, should not be interpreted as being limited to direct connections only. The terms “coupled” and “connected,” along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other. Thus, the scope of the expression a device A coupled to a device B should not be limited to devices or systems wherein an output of device A is directly connected to an input of device B. It means that there exists a path between an output of A and an input of B which may be a path including other devices or means. “Coupled” may mean that two or more elements are either in direct physical or electrical contact, or that two or more elements are not in direct contact with each other but yet still co-operate or interact with each other.
Thus, while there has been described what are believed to be the preferred embodiments of the invention, those skilled in the art will recognize that other and further modifications may be made thereto without departing from the spirit of the invention, and it is intended to claim all such changes and modifications as falling within the scope of the invention. For example, any formulas given above are merely representative of procedures that may be used. Functionality may be added or deleted from the block diagrams and operations may be interchanged among functional blocks. Steps may be added or deleted to methods described within the scope of the present invention.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2013902086 | Jun 2013 | AU | national |
| 2013902112 | Jun 2013 | AU | national |
The present application is a continuation of U.S. patent application Ser. No. 16/659,983, filed Oct. 22, 2019, entitled “FRAMEWORKS, DEVICES AND METHODS CONFIGURED FOR ENABLING TOUCH/GESTURE CONTROLLED DISPLAY FOR FACILITY INFORMATION AND CONTENT”, which is a continuation of U.S. patent application Ser. No. 14/300,072, filed Jun. 9, 2014, entitled “FRAMEWORKS, DEVICES AND METHODS CONFIGURED FOR ENABLING TOUCH/GESTURE CONTROLLED DISPLAY FOR FACILITY INFORMATION AND CONTENT”, now U.S. Pat. No. 10,474,240, which claims priority to Australian Patent Application No. 2013902086, filed on Jun. 10, 2013, entitled “FRAMEWORKS, DEVICES AND METHODS CONFIGURED FOR ENABLING TOUCH/GESTURE CONTROLLED DISPLAY FOR FACILITY INFORMATION AND CONTENT”, and Australian Patent Application No. 2013902112, filed on Jun. 11, 2013, entitled “FRAMEWORKS, DEVICES AND METHODS CONFIGURED FOR ENABLING GESTURE-BASED INTERACTION BETWEEN A TOUCH/GESTURE CONTROLLED DISPLAY AND OTHER NETWORKED DEVICES”, all of which are also incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6166716 | Kashino | Dec 2000 | A |
| 6167316 | Gloudeman et al. | Dec 2000 | A |
| 6542109 | Lloyd | Apr 2003 | B2 |
| 6542191 | Yonezawa | Apr 2003 | B1 |
| 6965376 | Tani et al. | Nov 2005 | B2 |
| 7162528 | Simonoff | Jan 2007 | B1 |
| 7477321 | Yokoyama | Jan 2009 | B2 |
| 7567844 | Thomas | Jul 2009 | B2 |
| 7587274 | Kaldewey et al. | Sep 2009 | B2 |
| 7861180 | Liu et al. | Dec 2010 | B2 |
| 7890647 | Nakamura | Feb 2011 | B2 |
| 7895599 | Muscarella | Feb 2011 | B2 |
| 7899777 | Baier et al. | Mar 2011 | B2 |
| 7900215 | Engber et al. | Mar 2011 | B2 |
| 7904209 | Podgorny et al. | Mar 2011 | B2 |
| 7908560 | Balfe et al. | Mar 2011 | B2 |
| 7954070 | Plocher et al. | May 2011 | B2 |
| 7971151 | Nixon et al. | Jun 2011 | B2 |
| 8036872 | Nasle | Oct 2011 | B2 |
| 8233008 | Jin et al. | Jul 2012 | B2 |
| 8269729 | Han et al. | Sep 2012 | B2 |
| 8270767 | Park | Sep 2012 | B2 |
| 8302029 | Makela | Oct 2012 | B2 |
| 8321898 | Yuasa | Nov 2012 | B2 |
| 8352176 | Kaldewey et al. | Jan 2013 | B2 |
| 8397177 | Barros | Mar 2013 | B2 |
| 8434029 | Albright | Apr 2013 | B2 |
| 8464181 | Bailiang | Jun 2013 | B1 |
| 8490025 | Jakobson | Jul 2013 | B2 |
| 8532962 | Zhang et al. | Sep 2013 | B2 |
| 8584030 | Laycock et al. | Nov 2013 | B2 |
| 8615396 | Grigsby et al. | Dec 2013 | B2 |
| 8681153 | Houllier et al. | Mar 2014 | B2 |
| 8712192 | Thota | Apr 2014 | B2 |
| 8775068 | Pylappan | Jul 2014 | B2 |
| 8791912 | Chen et al. | Jul 2014 | B2 |
| 8918413 | Hiestermann et al. | Dec 2014 | B2 |
| 8928657 | Bailiang | Jan 2015 | B2 |
| 8981413 | Obika | Mar 2015 | B2 |
| 9076259 | Hourie | Jul 2015 | B2 |
| 9571625 | Kim | Feb 2017 | B2 |
| 20020097322 | Monroe | Jul 2002 | A1 |
| 20020112237 | Kelts | Aug 2002 | A1 |
| 20030078677 | Hull et al. | Apr 2003 | A1 |
| 20040181443 | Horton | Sep 2004 | A1 |
| 20040254963 | Bradley | Dec 2004 | A1 |
| 20050251331 | Kreft | Nov 2005 | A1 |
| 20070101383 | Macintosh et al. | May 2007 | A1 |
| 20080309632 | Westerman | Dec 2008 | A1 |
| 20090077214 | Buster | Mar 2009 | A1 |
| 20090147011 | Buck | Jun 2009 | A1 |
| 20090210388 | Elson | Aug 2009 | A1 |
| 20090225164 | Renkis | Sep 2009 | A1 |
| 20090295918 | Horovitz | Dec 2009 | A1 |
| 20090300528 | Stambaugh | Dec 2009 | A1 |
| 20100017733 | Barros | Jan 2010 | A1 |
| 20100198663 | Nielsen | Aug 2010 | A1 |
| 20100223577 | Bennett | Sep 2010 | A1 |
| 20110013018 | Leblond | Jan 2011 | A1 |
| 20110081923 | Forutanpour | Apr 2011 | A1 |
| 20110083094 | Laycock | Apr 2011 | A1 |
| 20110087988 | Ray et al. | Apr 2011 | A1 |
| 20110161875 | Kankainen | Jun 2011 | A1 |
| 20110187704 | Chen | Aug 2011 | A1 |
| 20110187864 | Snider | Aug 2011 | A1 |
| 20110214050 | Stambaugh | Sep 2011 | A1 |
| 20110261202 | Goldstein | Oct 2011 | A1 |
| 20110299835 | Fleming | Dec 2011 | A1 |
| 20120017168 | Mason | Jan 2012 | A1 |
| 20120059818 | Phang | Mar 2012 | A1 |
| 20120072052 | Powers et al. | Mar 2012 | A1 |
| 20120109741 | Ballapragada | May 2012 | A1 |
| 20120158185 | El-Mankabady et al. | Jun 2012 | A1 |
| 20120179742 | Acharya | Jul 2012 | A1 |
| 20120194336 | Thiruvengada | Aug 2012 | A1 |
| 20120232791 | Sterkel | Sep 2012 | A1 |
| 20120266069 | Moshiri | Oct 2012 | A1 |
| 20120281095 | Trenciansky | Nov 2012 | A1 |
| 20120291068 | Khushoo | Nov 2012 | A1 |
| 20120311438 | Cranfill | Dec 2012 | A1 |
| 20120313781 | Barker | Dec 2012 | A1 |
| 20120317507 | Gutierrez | Dec 2012 | A1 |
| 20130002880 | Levinson | Jan 2013 | A1 |
| 20130033483 | Im | Feb 2013 | A1 |
| 20130036356 | Worrill | Feb 2013 | A1 |
| 20130041486 | Lee et al. | Feb 2013 | A1 |
| 20130063489 | Hourie | Mar 2013 | A1 |
| 20130083012 | Han | Apr 2013 | A1 |
| 20130083035 | Han et al. | Apr 2013 | A1 |
| 20130083055 | Piemonte et al. | Apr 2013 | A1 |
| 20130157612 | Cordero | Jun 2013 | A1 |
| 20130205257 | Albright | Aug 2013 | A1 |
| 20130208124 | Boghossian | Aug 2013 | A1 |
| 20130249812 | Ramos | Sep 2013 | A1 |
| 20130293584 | Anderson | Nov 2013 | A1 |
| 20130303247 | Wu | Nov 2013 | A1 |
| 20130321401 | Piemonte et al. | Dec 2013 | A1 |
| 20130332882 | Laycock | Dec 2013 | A1 |
| 20130335316 | Smith | Dec 2013 | A1 |
| 20140013263 | Bailiang et al. | Jan 2014 | A1 |
| 20140101601 | Tang | Apr 2014 | A1 |
| 20140123062 | Nguyen | May 2014 | A1 |
| 20140136701 | Billau | May 2014 | A1 |
| 20140137017 | Sharma et al. | May 2014 | A1 |
| 20140152698 | Kim et al. | Jun 2014 | A1 |
| 20140172184 | Schmidt | Jun 2014 | A1 |
| 20140223360 | Bailiang | Aug 2014 | A1 |
| 20140240356 | Cupitt | Aug 2014 | A1 |
| 20140245232 | Bailiang | Aug 2014 | A1 |
| 20140253538 | Bailiang | Sep 2014 | A1 |
| 20140359510 | Graf | Dec 2014 | A1 |
| 20140362112 | Morrison | Dec 2014 | A1 |
| 20140365891 | Morrison et al. | Dec 2014 | A1 |
| 20140365896 | Morrison | Dec 2014 | A1 |
| 20140365942 | Morrison | Dec 2014 | A1 |
| 20140365976 | Morrison | Dec 2014 | A1 |
| 20150186004 | Gordon | Jul 2015 | A1 |
| 20170205997 | Gold | Jul 2017 | A9 |
| 20180082402 | Gold | Mar 2018 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20220019290 A1 | Jan 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16659983 | Oct 2019 | US |
| Child | 17487840 | US | |
| Parent | 14300072 | Jun 2014 | US |
| Child | 16659983 | US |
