The subject matter disclosed herein generally relates to the field of information conveyance, and more particularly to a system that facilitates information conveyance in a building.
Corkboard community message boards contain information that is often cluttered, disorganized, and outdated, so much so that the messages on community message boards are often ignored.
According to one embodiment, a method of operating a building information conveyance system is provided. The method comprising: receiving one or more posts from a first user mobile device; determining at least one display screen to display the one or more posts; and displaying the one or more posts on the display screen.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the display screen is located in an elevator car.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include displaying the one or more posts on a second user mobile device.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include: detecting a third user mobile device located in the elevator car; and filtering the one or more posts on the display screen located in the elevator car in response to user data of the third user mobile device.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the user data includes a home location of the third user mobile device.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include filtering the one or more posts on the second user mobile device in response to user data of the second user mobile device.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the user data includes a home location of the second user mobile device.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include sorting the one or more posts in the order that the one or more posts are received.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include: detecting a third user mobile device located in the elevator car; and sorting the one or more posts on the display screen located in the elevator car in response to user data of the third user mobile device.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include: transmitting the one or more posts to a manager device; receiving a remove request for the one or more posts from the manager device; and removing the one or more posts from the display screen and all user mobile devices.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include: transmitting the one or more posts to a manager device; receiving a block request for the first user mobile device from the manager device; and blocking posts received from the first user mobile device after the block request is received, wherein the blocked posts are not displayed on any user mobile device or any display screen.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include transmitting an alert to the first user mobile device indicating the block request.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the one or more posts are sent from a social media platform on the user mobile device.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include generating on a user interface an add post screen on the user mobile device, the add post screen being configured to allow entry of the post.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the post may be entered via a verbal input from a user of the user mobile device.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the display screen in the elevator car is interactive.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include: detecting a third user mobile device located proximate the display screen; and filtering the one or more posts on the display screen in response to user data of the third user mobile device.
In addition to one or more of the features described above, or as an alternative, further embodiments of the method may include where the user data includes a destination of the third user device.
According to another embodiment, a building information conveyance system is provided. The building information conveyance 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 one or more posts from a first user mobile device; determining at least one display screen to display the one or more posts; and displaying the one or more posts on the display screen.
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 one or more posts from a first user mobile device; determining at least one display screen to display the one or more posts; and displaying the one or more posts on the display screen.
Technical effects of embodiments of the present disclosure include the ability for a display screen to convey relevant information to users of an elevator system.
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.
The following descriptions should not be considered limiting in any way. With reference to the accompanying drawings, like elements are numbered alike:
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.
The elevator system 203 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 203. It is understood that the elevator system 203 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
The controller 206 may include a processor 260, memory 262 and communication module 264 as shown in
The elevator system 203 includes one or more display screens 205 (e.g., 205-1, 205-2, . . . 205-n). Although two display screens 205-1 and 205-2 are shown in
Also shown in
Also shown in
The user mobile device 208a and manager device 208b may both be referred to as a device 208 for ease of explanation. Each device 208 may have a unique identification code and/or login that identifies each device 208. The code may be a name, email, or some code linked to the device 208 or user account used for posting. The device 208 and the controller 206 communicate with one another. For example, the device 208 and the controller 206 may communicate with one another when proximate to one another (e.g., within a threshold distance). The device 208 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 device 208 using one or more communication protocols or standards. For example, the networked element may communicate with the device 208 using near field communications (NFC). In other embodiments, the controller 206 may establish communication with a device 208 that is outside of the building 202. 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 device 208 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 device 208 and controller 206, and embodiments are not limited to the examples provided in this disclosure. Communication between the device 208 and the controller 206 will allow the controller 206 to determine the location of the device 208 in relation to the elevator system 203 and/or the door system 205. Knowing the relative location of the device 208 will allow the controller 206 to determine what elevator car 204 the device 208 is currently located in and what to display on the display screen 205 in that elevator car 204.
Posts 325 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 part of a building computer system, stored offsite, remotely, or in the cloud. The database 263 may also store 326 user data 326 that may be specific to each user mobile device 208a. The user data 326 may include information including but not limited to the home location of the user, the age of the user, the gender of the user, hobbies of the user, work place of the user, and any interests of the user.
Embodiments generate a user interface on the device 208 through a community post application 255a, 255b. The community post application 255a may be used for user of the user mobile device 208a to enter posts 325. For example, a resident may report that they will be having a party and to let them know if it gets too loud.
In order to enter a post 325, a user can select the “add a post” 303 button, which will prompt the user interface 300 to generate a “new post” section 302 within the “our community” screen 301, as shown in
Referring now to
At block 508, the one or more posts 205 are displayed on a display screen 205. In an embodiment, the display screen 205 is located in an elevator car 204. In an embodiment, the display screen 205 is interactive and a user may scroll through the posts 325 displayed. For example, the user may user their user mobile device 208a to scroll through the posts 325, the display screen 205 may be a touch screen, or the display screen 205 may have a manual scroll button. In an embodiment, the controller 206 may detect when a third user mobile device 208a-3 is located in the elevator car 204 and filter the one or more posts 325 on the display screen 205 located in the elevator car 204 in response to user data 326 of the third user mobile device 208a-3 located in the elevator car 204. In an embodiment, the user data 326 includes a home location of the third user mobile device 208a-3. For example, the home location may be the floor in the building 202 on which the user of the third user mobile device 208a-3 lives. Advantageously, by filtering the posts 325 based on the user data 326, the user may only view information relevant to that user. Additionally, the posts 325 may also be sorted. In one embodiment, the posts 325 may be sorted in order of the posts 325 are received. In another embodiment, the posts 325 may be sorted in response to the user data 326. For example, based on the user data 326 some posts 325 may be more relevant to a user than other posts 325 and the relevancy may drive the sort. At block 510, the one or more posts 325 are displayed on a second user mobile device 208a-2. The posts 325 may also be filtered and/or sorted on the second user device 208a-5, as described above in relation to the display screen 205.
Further, the method 500 may also include transmitting the posts 325 to a manager device 208b. The manager using the manager device 208b may then review the posts 325 and decide whether a particular post 325 should be removed from being displayed on a display screen 205 and/or user mobile device 208a. The manager may use the manager device 208b to send a remove request to the controller 206 in order to remove a post 325. In an embodiment, the manager may be required to approve all posts 325 prior to the post 325 being displayed. Alternatively, the posts 325 may be limited to a maximum number of posts 325 from a user and/or a frequency of posts 325 form a user. The manager may also use the manager device 208b to send a block request to the controller to block a particular user of a user mobile device 208a from posting, thus the posts 325 from that user will no longer be displayed any display screen 205 and/or any user mobile device 208a. An alert may be transmitted to a user mobile device 208a when they have been blocked and/or a post 325 from the user mobile device 208a has been removed. The alert will indicate the block request or the remove request.
While the above description has described the flow process of
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.
Number | Name | Date | Kind |
---|---|---|---|
5955710 | DiFranza | Sep 1999 | A |
6288688 | Hughes et al. | Sep 2001 | B1 |
6341668 | Fayette et al. | Jan 2002 | B1 |
6349797 | Newville | Feb 2002 | B1 |
6543582 | DiFranza et al. | Apr 2003 | B2 |
6968362 | Koch et al. | Nov 2005 | B2 |
7797374 | Prince | Sep 2010 | B2 |
8743753 | Lin et al. | Jun 2014 | B2 |
8910309 | Harrison et al. | Dec 2014 | B2 |
9100454 | Holden et al. | Aug 2015 | B2 |
9177283 | Singh et al. | Nov 2015 | B2 |
9479548 | Jensen et al. | Oct 2016 | B2 |
9479549 | Pearson | Oct 2016 | B2 |
9519886 | Berger et al. | Dec 2016 | B2 |
9571443 | Borger et al. | Feb 2017 | B2 |
9592993 | Joyce et al. | Mar 2017 | B2 |
20020013144 | Waters et al. | Jan 2002 | A1 |
20020129995 | Friedli et al. | Sep 2002 | A1 |
20030177097 | Friedli et al. | Sep 2003 | A1 |
20040266403 | Boland | Dec 2004 | A1 |
20070040891 | Calloway | Feb 2007 | A1 |
20080191418 | Lutnick | Aug 2008 | A1 |
20080255870 | Butler | Oct 2008 | A1 |
20100299899 | Johnson, Jr. | Dec 2010 | A1 |
20100318921 | Trachtenberg et al. | Dec 2010 | A1 |
20110047471 | Lord et al. | Feb 2011 | A1 |
20110173549 | Hipskind | Jul 2011 | A1 |
20130024530 | Kim et al. | Jan 2013 | A1 |
20130054714 | Bedi | Feb 2013 | A1 |
20130290855 | Ashcraft et al. | Oct 2013 | A1 |
20130346867 | Woods | Dec 2013 | A1 |
20140040054 | Elhabr | Feb 2014 | A1 |
20140173461 | Shahade | Jun 2014 | A1 |
20160009525 | DePaola | Jan 2016 | A1 |
20160028781 | Bell et al. | Jan 2016 | A1 |
20160078659 | Bartkiewicz et al. | Mar 2016 | A1 |
20160110899 | Kalb | Apr 2016 | A1 |
20160125458 | Enriquez | May 2016 | A1 |
20160127875 | Zampini, II | May 2016 | A1 |
20160294572 | Shadid et al. | Oct 2016 | A1 |
20170166417 | Salmikuukka | Jun 2017 | A1 |
20180041545 | Chakra | Feb 2018 | A1 |
20180079619 | Ben Abat | Mar 2018 | A1 |
Number | Date | Country |
---|---|---|
1464382 | Dec 2003 | CN |
2922008 | Sep 2015 | EP |
2016207477 | Dec 2016 | WO |
Entry |
---|
Extended European Search Report for Application No. 18170541.9-1101; dated Jul. 18, 2018; Report Received Date: Aug. 23, 2018; 7 pages. |
Digi-Notice, “Great Content in All Different Sizes”, available at http://digi-notice.com/great-content-in-all-different-sizes/, 2017, 4 pgs. |
Hootboard, “Digitial Signage unlike any Other”, http://about.hootboard.com/digital-signage/, accessed Mar. 31, 2017, 15pgs. |
PressReader, “Out goes the bulletin board; Elevator TV informs condo owners”, available at: https://www.pressreader.com/canada/ottawa-citizen/20160903/282638917023443, accessed Mar. 31, 2017, 3 pgs. |
Number | Date | Country | |
---|---|---|---|
20180287970 A1 | Oct 2018 | US |