MULTI-TARGET DYNAMIC UI ACTION ELEMENT

BACKGROUND

The subject matter disclosed herein generally relates to the field of building system controls, and more particularly to an apparatus and method for controlling building systems through a mobile device.

Building systems typically require physical manipulation of the actual system in order to control the system.

BRIEF SUMMARY

According to one embodiment, a method of controlling building systems is provided. The method comprises: receiving a first user input; determining a building system corresponding to the first user input; receiving a second user input, the second input corresponding to one of a plurality of defined actions; and controlling the building system using the defined action.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the receiving a first input further comprises: receiving a first user sub-input; generating a list, the list including a plurality of building systems; and receiving a second user sub-input selecting a building system.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the first user sub-input is a press and hold.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the second user sub-input is a drag and hold.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include prior to the receiving a first user input: generating a user interface depicting a home control icon, the home control icon depicting a selected building system.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the first user input is a defined action corresponding to the selected building system depicted on the home control icon; and the first user input is used to satisfy the second user input.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include after controlling the building system using the defined action: generating a user interface depicting a home control icon, the home control icon depicting the selected building system.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the first user input is used to satisfy the second user input.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the defined action is user defined.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include prior to the receiving a first user input: receiving a user input; creating a defined action in response to the user input; assigning the defined action to a building system; and storing the defined action in a database.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include associating the defined action with a user of a user mobile device; and storing the association in the database.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the building system is at least one of a door system, an elevator system, a lighting system, and a climate control system.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the controlling further comprises: unlocking a door of the door system.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the controlling further comprises: calling an elevator car of the elevator system.

In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the controlling further comprises: adjusting a light of the lighting system.

According to another embodiment, a building control system is provided. The building control system comprising: a processor; a memory comprising computer-executable instructions that, when executed by the processor, cause the processor to perform operations, the operations comprising: receiving a first user input; determining a building system corresponding to the first user input; receiving a second user input, the second input corresponding to one of a plurality of defined actions; and controlling the building system using the defined action.

According to another embodiment, a computer program product tangibly embodied on a computer readable medium is provided. The computer program product including instructions that, when executed by a processor, cause the processor to perform operations comprising: receiving a first user input; determining a building system corresponding to the first user input; receiving a second user input, the second input corresponding to one of a plurality of defined actions; and controlling the building system using the defined action.

Technical effects of embodiments of the present disclosure include the ability control building systems through a multi-target dynamic user interface on a mobile device.

The foregoing features and elements may be combined in various combinations without exclusivity, unless expressly indicated otherwise. These features and elements as well as the operation thereof will become more apparent in light of the following description and the accompanying drawings. It should be understood, however, that the following description and drawings are intended to be illustrative and explanatory in nature and non-limiting.

BRIEF DESCRIPTION

The following descriptions should not be considered limiting in any way. With reference to the accompanying drawings, like elements are numbered alike:

FIG. 1 illustrates a schematic view of a building control system, in accordance with an embodiment of the disclosure;

FIG. 2 depicts a user interface on a mobile device, in accordance with an embodiment of the disclosure;

FIG. 3 depicts a user interface on a mobile device, in accordance with an embodiment of the disclosure; and

FIGS. 4a-4d depict a defined action for a user input on a mobile device, in accordance with an embodiment of the disclosure; and

FIG. 5 is a flow diagram illustrating a method of controlling building systems, according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

A detailed description of one or more embodiments of the disclosed apparatus and method are presented herein by way of exemplification and not limitation with reference to the Figures.

FIG. 1 depicts a building control system 200 in an example embodiment. The building control system 200 includes a plurality of building systems 202-205, such as for example, a climate control system 202, a lighting system 203, a door system 205, and an elevator system 204 installed at a building 201. The disclosure is not intended to be limited by these building system 202-205 and as may be appreciated by one of skill in the art, the building 201 may include other systems such as, for example, entertainment systems, security systems, window blind systems, plumbing system, and other any other building system known to one of skill in the art not mentioned herein that may be controlled by the building control system 200. In some embodiments, the building 201 may be a building or a collection of buildings that may or may not be physically located near each other. The building 201 may include any number of floors. Persons entering the building 201 may enter at a lobby floor, or any other floor, and may go to a destination floor via one or more conveyance devices, such as the elevator system 204. Persons entering the building 201 may be required to enter a door (e.g., doors 205-1, 205-2, . . . 205-n) of the door system 205. The door (e.g., doors 205-1, 205-2, . . . 205-n) may include but is not limited to a door in a wall of the building, a door on the outside of the building, a garage door, and a parking lot access gate. The climate within the building 201 is controlled by a climate control system 202. There may be one or more climate control systems 202 for the building 201, such as, for example, one climate control system (e.g., climate control systems 202-1, 202-2 . . . 202-n) for each room in the building 201. The light within the building 201 is controlled by a lighting system 203. There may be one or more lighting systems 203 for the building 201, such as, for example, one lighting system (e.g., lighting systems 203-1, 203-2 . . . 203-n) for each room and/or office space (e.g. cubical) in the building 201.

The building systems 202-205 may be operably connected to one or more computing devices, such as a controller 206. The controller 206 may be configured to control dispatching operations for one or more elevator cars (e.g., elevator cars 204-1, 204-2 . . . 204-n) associated with the elevator system 204. The controller 206 may also be configured to control access to the one or more elevator cars (e.g., elevator cars 204-1, 204-2 . . . 204-n) associated with the elevator system 204. It is understood that the elevator system 204 may utilize more than one controller 206, and that each controller may control a group of elevators cars 204-1 and 204-2. Although two elevator cars 204-1 and 204-2 are shown in FIG. 1, it is understood that any number of elevators cars 204-n may be used in the elevator system 204. The elevator cars 204-1 and 204-2 may be located in the same hoistway or in different hoistways so as to allow coordination amongst elevator cars 204-1 and 204-2 in different elevator banks serving different floors. It is understood that other components of the elevator system 204 (e.g., drive, counterweight, safeties, etc.) are not depicted for ease of illustration.

Further, the controller 206 may also be configured to control access to one or more doors (e.g., doors 205-1, 205-2 . . . 205-n). It is understood that the door system 205 may utilize more than one controller 206, and that each controller may control a group of doors 205-1 and 205-2. Although two doors 205-1 and 205-2 are shown in FIG. 1, it is understood that any number of elevators cars 205-n may be used in the door system 205. It is understood that other components of the door system 205 (e.g., locks.) are not depicted for ease of illustration.

Additionally, the controller 206 may also be configured to control operation of the climate control system 202, the lighting system 203, and any other system of the building 201 known to one of skill in the art. It is understood that the climate control system 202 and the lighting system 203 may utilize more than one controller 206, and that each controller may control each system as a whole (e.g., 202 and 203) or each separate component (e.g. 202-1-202-n, 203-1-203-n). It is understood that other components of the climate control system 202 and the lighting system 203 are not depicted for ease of illustration.

The controller 206 may include a processor 260, memory 262 and communication module 264 as shown in FIG. 1. The processor 260 can be any type or combination of computer processors, such as a microprocessor, microcontroller, digital signal processor, application specific integrated circuit, programmable logic device, and/or field programmable gate array. The memory 262 is an example of a non-transitory computer readable storage medium tangibly embodied in the controller 206 including executable instructions stored therein, for instance, as firmware. The communication module 264 may implement one or more communication protocols as described in further detail herein.

Also shown in FIG. 1 is a user mobile device 208a. The user mobile device 208a may include a device that is typically carried by a person, such as a phone, PDA, smart watch, tablet, laptop, etc. The mobile device 208a may have a touch screen 251a to allow user input. The user mobile device 208a may include a processor 250a, memory 252a and communication module 254a as shown in FIG. 1. The processor 250a can be any type or combination of computer processors, such as a microprocessor, microcontroller, digital signal processor, application specific integrated circuit, programmable logic device, and/or field programmable gate array. The memory 252a is an example of a non-transitory computer readable storage medium tangibly embodied in the user mobile device 208a including executable instructions stored therein, for instance, as firmware. The communication module 254a may implement one or more communication protocols as described in further detail herein. In a non-limiting example user mobile device 208a belongs to a resident or employee of the building 201 who currently has access to control at least one building system 202-205 of the building 201. Each user may have specific user control permissions 325 granting each user the ability to control selected building systems 202-205 through a building system control application 255a on the user mobile device 208a belonging to the user. For example, the control permissions 325 may dictate that a specific user may open a specific door. The control permissions 325 may be established by a manager of the building control system 200. Each user may have defined actions 326 to be used in controlling each building system 202-205 through the building system control application 255a, which will be discussed further below. The defined actions 326 may be user defined based on specific user inputs that are entered into the user mobile device 208a. For example, the defined action 326 may be drawing a zig-zag on the touch screen 251a of the user device 208a. The defined actions 326 may be stored in a database 263. The database 263 may be operatively connected to the controller 206 or stored within the controller 206. In one embodiment, the database 263 may be stored offsite, remotely, or in the cloud.

The user mobile device 208a and the controller 206 communicate with one another. For example, the user mobile device 208a and the controller 206 may communicate with one another when proximate to one another (e.g., within a threshold distance). The user mobile device 208a and the controller 206 may communicate over a wireless network, such as 802.11x (WiFi), short-range radio (Bluetooth), cellular, satellite, etc. In some embodiments, the controller 206 may include, or be associated with (e.g., communicatively coupled to) a networked element, such as kiosk, beacon, hall call fixture, lantern, bridge, router, network node, door lock, elevator control panel, building intercom system, etc. The networked element may communicate with the user mobile device 208a using one or more communication protocols or standards. For example, the networked element may communicate with the user mobile device 208a using near field communications (NFC). In other embodiments, the controller 206 may establish communication with a user mobile device 208a that is outside of the building 201. This connection may be established with various technologies including GPS, triangulation, or signal strength detection, by way of non-limiting example. In example embodiments, the user mobile device 208a communicates with the controller 206 over multiple independent wired and/or wireless networks. Embodiments are intended to cover a wide variety of types of communication between the user mobile device 208a and controller 206, and embodiments are not limited to the examples provided in this disclosure. Communication between the user mobile device 208a and the controller 206 will allow the controller 206 to determine the location of the user mobile device 208a in relation to each building system 202-205.

Embodiments generate a user interface on the user mobile device 208a through the building system control application 255a. The building system control application 255a may be used for users to control building systems 202-205 through a user mobile device 208a. In a few non-limiting examples, a user may use the building system control application 255a to increase the heat output of a climate control system 202-1, turn on a light 203-1, call an elevator car 204-1, and unlock a door 205-1. An identification credential on the user mobile device 208a will identify each user mobile device 208a to the controller 206.

FIGS. 2, 3, and 4
a-4d depict an example user interface 300 on user mobile device 208a. Referring to FIG. 2, when the user mobile device 208a launches the building system control application 255a, a control screen 302 may be presented as shown in FIG. 2. The control screen 302 may show a home control icon 304 for easy access to control a selected building system, such as, for example, a climate control system 202, a lighting system 203, an elevator system 204, and a door system 205. In the example of FIG. 2a, the door system 205 depicts on the home control icon 304 on the control screen 302 when the user mobile device 208a launches the building system control application 255a, thus the door system 205 is the selected building system. The selected building system displayed within the home control icon 304 may be adjusted depending on user preferences. If the user does not want to control the building system currently depicted on the home control icon 304 then the user may select an arrow 306 to open a list 308 that may be seen in FIG. 3. It is understood, that the list 308 is shown for ease of explanation and that any other method of displaying a list of options or selection interfaces may be used. The list 308 may be displayed as a textual drop-down list of building systems 202-205 (drop-down list shown in FIG. 3) or as individual icons, where each icon represents a building system (icons not shown for simplicity). In an example, another selection interface may include a pop-up/modal window with a list or grid of selections. The pop-up/modal window may be a new page state, such as a full-screen overlay. In another example, the selection interface may be a vertical or horizontal scrolling lightbox of selection options, it could be text, illustrations or photographs. In another example, the selection interface may be a long press on the arrow 306 to open a pop-up scroller/selector (e.g. a scroll-wheel picker). The arrow 306 may be selected by the user pressing on the home control icon 304 and not swiping. The arrow 306 may also be selected by pressing the arrow 306 directly.

Referring to the FIG. 3, the list 208 may contain each building system 202-205 that the user has access to as defined by the user control permissions 326. The user control permissions 326 may be set by a manager of the building control system 200. In an example, the user control permissions may allow a selected user to control a selected building system. It is understood that only four building system 202-205 are shown for simplicity and the list 208 may contain more or less options for each building system 202-205 and additional building systems not mentioned herein. Once the list 208 appears the user may select the building system 202-205 they would like to control by sliding down and pressing the desired building system.

Referring now to FIGS. 4a-4d with continued reference to FIGS. 1-3. Once the building system 202-205 is selected in the list 208 then each building system 202-205 has a defined action 326 assigned to control each building system. The defined action 326 may be established by the user of the user mobile device 208a and saved in the 263 database. The user may use user input to create the defined action 326. In an embodiment, the user input is a dynamic action, such as for example a motion while touching the touch screen 251a. The defined action 326 may also be changed by user. FIGS. 4a-4d display four non-limiting examples of defined actions 326. As seen in FIG. 4a, a user may swipe horizontally straight to unlock a door. The horizontal swipe is a defined action 326 for a door in the example of FIG. 4a. As seen in FIG. 4b, a user may zig-zag swipe to call an elevator car. The zig-zag swipe is a defined action 326 for an elevator car in the example of FIG. 4b. As seen in FIG. 4c, a user may utilize a circular swipe to adjust a climate control system. The circular swipe is a defined action 326 for a climate system in the example of FIG. 4c. As seen in FIG. 4d, a user may utilize a “w” shaped swipe to adjust a lighting system. The “w” shaped swipe is a defined action 326 for a lighting system in the example of FIG. 4d.

Referring now to FIG. 5, while referencing components of FIGS. 1-4. FIG. 5 shows a flow chart of method 500 of controlling building systems, in accordance with an embodiment of the disclosure. At block 504, a first user input is received. As described above, the first user input may be a touch and or dynamic action on the touch screen 251a on the user mobile device. At block 506, a building system corresponding to the first user input is determined. At block 508, a second user input is received. The second input corresponds to one of a plurality of defined actions. At block 510, the building system is controlled using the defined action. As mentioned above, the building system may be at least one of a door system 205, an elevator system 204, a lighting system 203, and a climate control system 202. In an embodiment, the controlling of block 510 may include unlocking a door of the door system 205. In an embodiment, the controlling of block 510 may include calling an elevator car of the elevator system 204. In an embodiment, the controlling of block 510 may include adjusting a light of the lighting system 203. In an embodiment, the controlling of block 510 may include adjusting an output of the climate control system 202.

The first user input of block 504 may be broken down into user sub-inputs. For example, a first user sub-input may result in the generation of a list 308 as shown in FIG. 3. The list 308 may include a plurality of building systems. In an embodiment, the first sub-sub input, may be a press and hold. The press and hold may on the arrow 306 as shown in FIG. 2. A second user sub-input may select a building system from the list 308. In an embodiment, the second user sub-input may be a drag in hold over the desired building system in the list 308.

Alternatively, rather than generating a list 308 to select a building system, the user may desire to control a selected building system on a home control icon 304. As mentioned above, prior to the first user input, a user interface 300 is generated depicting a home control icon 304 and the selected building system appears on the home control icon 304. If the user desires to control that selected building system then the user will perform a first user input that is a defined action 326 corresponding to the selected building system depicted on the home control icon 304. Then the first user input is used to satisfy the second user input of block 508 and the user will be able to control the building system in block 510. Regardless of the building system selected to control, the control screen 302 on the user interface 300 may default back to the home control icon 304 depicting the selected building system.

Prior to receiving the first user input, a user of a user mobile device 208a may define a defined action 326 for each building system, as mentioned above. Thus, the user may perform a user input and a defined action 326 is created in response to the user input. For instance, the user input may be a zig-zag swipe (see FIG. 4b) from which a defined action 326 is created representing the zig-zag swipe performed by the user and then the defined action 326 is assigned to a building system. The defined action 326 is then stored in a database 263 and may be assigned to the specific user of the user mobile device 208a that performed the user input to create the defined action 326. The defined action 326 may also be applied to a broad group of users.

While the above description has described the flow process of FIG. 5 in a particular order, it should be appreciated that unless otherwise specifically required in the attached claims that the ordering of the steps may be varied.

As described above, embodiments can be in the form of processor-implemented processes and devices for practicing those processes, such as a processor. Embodiments can also be in the form of computer program code containing instructions embodied in tangible media, such as network cloud storage, SD cards, flash drives, floppy diskettes, CD ROMs, hard drives, or any other computer-readable storage medium, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes a device for practicing the embodiments. Embodiments can also be in the form of computer program code, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into an executed by a computer, the computer becomes an device for practicing the embodiments. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.

The term “about” is intended to include the degree of error associated with measurement of the particular quantity based upon the equipment available at the time of filing the application. For example, “about” can include a range of ±8% or 5%, or 2% of a given value.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, element components, and/or groups thereof.

While the present disclosure has been described with reference to an exemplary embodiment or embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the present disclosure. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present disclosure without departing from the essential scope thereof. Therefore, it is intended that the present disclosure not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this present disclosure, but that the present disclosure will include all embodiments falling within the scope of the claims.

MULTI-TARGET DYNAMIC UI ACTION ELEMENT

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims