Information display system with occupancy detector

A system for displaying content includes a display visible to viewers present in a viewing zone and an occupancy detector for providing occupancy data indicative of how many viewers are present in the viewing zone. A processing system associates this occupancy data with content provided on the display.

BACKGROUND OF THE INVENTION

This invention relates to providing information in an elevator and other such personnel transport vehicles.

The impetus for constructing skyscrapers and other high-rise structures lies in providing a more efficient use of real estate, particularly in urban areas where the value of real estate is at a premium. The primary mode of transportation in such structures is the elevator, particularly in buildings having many floors.

Visual information provided in an elevator is generally limited to floor information and passenger instructions in the event of an emergency or assistance is required. An elevator may also include a static placard posting the day's present and their locations.

SUMMARY OF THE INVENTION

This invention features a system for displaying video information to passengers of an elevator in accordance with a play list defining a sequence of messages. The video information messages can include combinations of digital advertising, “real-time” general information, as well as, building-related information.

In one aspect of the invention, the system includes an elevator display unit having a display monitor for displaying video information to the passengers, and a local server which, receives scheduling information associated with the video information over a data communication path and, in accordance with the scheduling information, generates a play list used to display at the elevator display unit.

In another aspect of the invention, a method of providing general information and commercial information within an elevator includes the steps of: a) providing to a local server, scheduling information associated with video information to be displayed; b) generating, from the scheduling information, a play list associated with the video information; and c) generating a display for viewing at the elevator display unit within the elevator, the video information at predetermined times in accordance with the scheduling information.

By “video information”, it is meant any combination of general, commercial, and building-related information. By “commercial information”, it is meant any information relating to commerce and trade including advertisements. “General information” is used here to mean information of general interest, including news (recent happenings, sports, entertainment, etc.) and weather. General information can also include information associated with the building within which the elevator is a part, for example, 1) events associated with the building; 2) traffic; 3) transportation schedules (e.g., train/shuttle services). By “building-related information”, it is meant that information specifically related to the particular building where the elevators transport residents, tenants, and visitors of the building. The building-related information may include certain types of commercial information, such as advertising for businesses within or local to the building (e.g., coffee, shop, parking, florist), as well as announcements by building management for available space within the building. The building-related information can also include forms of general information, particularly relevant to the building and its elevator passengers. For example, such information can include building activities (e.g., holiday events, fire alarm testing), public address/emergency messages, traffic information, and other information useful to the elevator's passengers. In general, the building-related information is less limited by the type of information, and more by its geography.

With this system, advertisers, online content providers, and building management/owners can interact with a specific, well-defined, and targeted audience in an elevator, a setting where passengers often feel uncomfortable being confined with complete strangers. Elevator passengers often seek ways to avoid making eye contact with fellow passengers during what feels like an endless, unnerving duration of time. Passengers no longer need to stare aimlessly at the floor or ceiling, but have an informative media resource to watch.

Occupants of high-rise office buildings are typically business people with understood interests and buying tendencies. These people are ideal recipients for targeted content and advertising. The system allows content providers (e.g., local and national news sources) and advertisers to selectively target audiences based on the demographics of a building, city, region, business segment, etc. Similarly, national, regional, and local online content providers are afforded an opportunity to provide elevator passengers with information of general interest. The system also provides building owners and managers the ability to provide video information particularly relevant and useful to tenants and visitors of their buildings.

Embodiments of these aspects of the invention may include one or more of the following features. The local server receives the scheduling information from the production server over a data communication network (e.g., the Internet).

The system also includes a production server which generates scheduling information associated with the general and commercial information. Thus, the production server serves as a central distribution site where, among other things, the scheduling information (e.g., building play lists or scripts) are generated. The production server includes a production server database for storing building-related data, general information-related data, and commercial information-related data. This database includes, for example, building characterization data, as well as the addresses from where the general and commercial information can be retrieved over the data communication path.

The production server includes a scheduling module, which retrieves the data from the production server database and generates the scheduling information and a building loader interface through which data is passed between the production server and the local server. The building loader interface encrypts the data passed between the production server and the local server and authenticates that the local server is one associated with the system.

The production server includes a billing module, which generates documentation relating to the duration of time the general information and commercial information is displayed at elevator display unit. A database maintenance module is also included within the production server to update the production center database with information relating to elevator occupancy as a function of time.

The local server communicates with the elevator display unit via a local area network including local and general information databases and a scheduling information parser. General information and commercial information retrieved over the data communication path are cached in respective ones of the local and general information databases. The scheduling information parser generates a local building play list from the scheduling information retrieved from the production server.

The local area network includes an Ethernet path for connection to the elevator display unit. The elevator display unit further includes an occupancy detector for determining, at predetermined intervals, the number of occupants riding within a particular elevator.

Generating the elevator play list is performed with a graphical user interface.

For the BOM interface, the video information includes a text message (e.g., in HTML format) and the play list includes a start date on which the text message is displayed on the display monitor; an end date on which the text message is displayed on the display monitor; and a day segment indicating a portion of a day the text message is displayed on the display monitor.

The user interface is remote from said local server and communicates with said local server over a data communications path, such as the Internet, a dial-up modem, or a local area network. The play list is a building operations play list, with the video information and scheduling information for generating the building operations play list relating to building operations.

The local server further receives a production server play list from a production server, remote from said local server, over a data communication network, said production server play list associated with general and commercial information for display on the display unit. The local server includes a parser, which generates a local building play list from the production server play list and the building operations play.

Other features of the invention will be apparent from the following description and from the claims.

DESCRIPTION

Referring toFIG. 1, an information distribution system1provides a media outlet for distributing general information along with digital advertising to elevator display units10mounted in elevators12of high rise office buildings14(represented by dashed-line boxes). System1includes a production center20which—among other important tasks described below—reates and distributes elevator display data by merging advertising with the “real time” general information. The general information is considered “real time” because the information is relatively current (refreshed at defined periodic intervals) with system1collecting, formatting, and displaying the information without human intervention. The general information is provided by any number of sources22(e.g., websites) connected via a distribution channel, here the Internet24.

Each building14includes a building server28which interfaces with production center20via Internet24to develop presentations of merged advertising and general information to be exhibited on elevator display units. As is described in greater detail below, each building server provides the general and advertising information to each elevator display unit10of associated elevators12through a local area network (LAN)30.

Information distribution system1utilizes a concept called “micro-demographics” which allows advertisers and online providers to target a highly desirable demographic, business population. The desired audience targeted by a particular advertiser or on-line provider may vary greatly and depend on a number of factors. As will be discussed below, system1collects or otherwise determines the demographics associated with a particular building as well as the occupants of that building. Thus, the geographical location and elevator traffic patterns of the building, and the nature of the business of the building occupants are determined by and stored at production center20so that a building script or play list68(FIG. 5) of advertisements and general (“real time”) content can be matched to the building.

Referring toFIG. 2, buildings14are shown encircled to represent that they belong to a particular geographical region. Smaller encircled groups7a-7frepresent, for example, buildings14within a city (e.g., Boston) are also shown encircled by larger geographical regions8a-8b(e.g., New England). Geography is generally a very important demographic factor, however, as important may be the particular business segment which is targeted. Thus, several buildings14a-14cwhich are from different geographical regions, but associated with the same business segment population (e.g., financial) may be grouped together (shown bounded by the cross hatched area). The ability to partition demographics by both geography and business segment provides tremendous value to content providers and advertisers.

In an example of one application of the system, assume an advertiser wishes to distribute an advertisement targeted specifically at the financial community in the northeast region of the United States. The advertisement needs to appear over a two week period during morning prime time hours. Production center20provides the advertiser with an automated request entry process for capturing this pertinent information representative of the target demographic. Production center20creates, from the target demographic, building play list68of potential building candidates for the advertisement and defines possible run time slots for when the advertisement is to be displayed. Several factors affecting which of a number of buildings are candidates and which time slots are available include: the target demographic (e.g., financial community in northeast United States), the number of advertisement impressions (i.e., the number of times an advertisement is viewed) purchased, the advertisement start and end dates (e.g., start and end of a two week period), prime time requirements (i.e., prime time morning), the advertisement format (280×90 animated GIF file) and advertisement locator (where GIF file is located). Once the advertisement time slots are identified, production center20determines the general information (e.g., news article, weather update) provided by an online provider that is to be merged and displayed with the advertisement. Building play list68specifies the format and content of the elevator displays for every instant of the day. Thus, in the example, production center20schedules the advertisement to be played at 9:00 a.m. and 15 seconds simultaneously with a local news article in one building play list while running the same advertisement at 8:15 a.m. and 0 seconds with a weather update in another building play list. It is important to note that building play list68defines what gets displayed and when, but does not contain the actual display content. Instead, building play list68provides pointers for obtaining the information over Internet24.

With information relating to the advertisement imbedded in the building play list, production center20must then present the advertisement to elevator occupants. Building server28is responsible for downloading the building play list from production center20, retrieving over Internet24, the specified advertisement and general information, followed by assembling and distributing the advertisement and information within displays which are to be viewed in elevator display units10. Building server28uses the pointers in play list68to retrieve the content and store it locally to a particular building14. This allows building server28to create a very high performance broadcast channel within building14. In the example, building server28uses an advertisement locator embedded in play list68to retrieve and store locally the animated GIF file for the advertisement. With the content stored locally, building server28reads play list68, assembles displays at the times indicated by the list and distributes them to the individual elevators12. Thus, in the example, at 9:00 a.m. and 15 seconds, building server28assembles the advertisement with the specified local news story and displays it in elevators12.

Details relating to the major components of information distribution system1follow.

Referring toFIG. 3, elevator display unit (EDU)10receives and processes data provided by building server28to create display presentations. Elevator display unit10includes a display13controlled by a single-board computer34and a network interface card (NIC)36. Display13includes an LCD controller, a back light assembly, a power converter, and a flat panel display (none shown). Computer34manages the operation of elevator display unit10including system setup and monitoring, network overhead, display data routing, and elevator occupancy. Network interface card36interacts with local area network30and is configured by computer34during system startup. Display data being broadcast downstream from building server28to elevator display units10represents the majority of the network traffic. In the downstream direction (from building server28to elevator display unit10), network traffic is mostly comprised of display broadcast data. There is a limited amount of control information in the downstream direction, however this is negligible. Network interface card36routes display data directly to display13. Control information will generate an interrupt to computer34to request service. In the upstream direction (from elevator display unit10to building server28), network traffic includes occupancy information and system monitoring data. All upstream data is generated by computer34and passes to network interface card36for transmission.

Data from building server28is transmitted to each elevator display unit10via local area network30(shown enclosed by dashed lines). In particular, data is transmitted through copper twisted pair lines38via an Ethernet network switch40for managing data flow.

One important feature of system5not yet discussed, is its closed-loop nature. Advertising is measured based on impressions (i.e., the number of times an advertisement is viewed). To quantify the number of impressions delivered by system1requires system feedback which is generated using elevator occupancy measurements.

To provide feedback to system1, each elevator display unit10includes an occupancy detector42for determining the number of occupants in a particular elevator throughout the day at predetermined time intervals (e.g., every 5 seconds). This information is summarized on a per building basis and uploaded via building server28to production center20once a day, typically during downtime periods. Production center20uses the feedback for billing and maintenance of a production center database60(FIG.5). In articular, this feedback is used to update the advertisement impressions which are still to be displayed and for creating statistical traffic information for each building. This data is critical to the scheduling and advertisement sales process.

Occupancy detector42utilizes sensors (not shown) to generate a pair of pulses when a passenger enters or leaves the elevator. The sensors are, for example, imbedded in the elevator doors. The pulse characteristics of the sensors define whether the passenger is entering or departing the elevator. Occupancy detector42maintains an occupancy count based on these sensors. Computer34samples the occupancy count periodically. Each elevator display unit10, therefore, generates a daily occupancy history which is used in the advertisement billing process.

Referring toFIG. 4, under the control of building server28, display13is segmented so that specific types of information are exhibited within particular regions of the display. Display13includes an advertising banner section44for displaying advertising and other commercial information and a “real time” content section46for viewing general information. “Real time” content section48may, in turn, be divided into other sections, for example, exhibit story excerpts50, one or more pictures52related to the excerpt, and descriptions of the pictures54. For example, as shown here, elevator passengers are provided, in banner section44, the day's breakfast specials from a cafe located, for example, in the first level of building14. Simultaneously, news text of general interest is displayed within a story excerpt50along with a related picture54.

As stated above, a primary function of production center20is to create and distribute the elevator display data. Creation of the elevator display data includes merging of news, information, and advertising to produce the building-specific play lists68. Distribution of the play lists is accomplished using the connectivity provided via Internet24.

Another important function of production center20is management and maintenance of a website for system1. The website provides management of building14and a central location where potential advertisers can request information relating to advertising on the system. Elevator occupants can also access the website for additional information relating to both the displayed “real time” information or advertising information viewed on display13in elevator12. For example, an occupant may not remember details of a particular advertisement (e.g., today's specials at one of the building's dining facilities) or may want to learn more about breaking a news story displayed in “real time” content section48.

Production Center

Referring toFIG. 5, production center20includes a production center database60, scheduling module62, building loader64, and billing and database maintenance module66. In general, production center database60stores data related to advertising, “real time” content, and building parameters.

Scheduling module62uses the data to produce play lists68for each building14. As discussed above, a building play list68(FIG. 5) serves as the recipe used by building server28to create display presentations exhibited throughout the day. Scheduling module62also provides advertising and content usage information to billing and database maintenance module66which generates billing summaries and invoices70for each advertiser and “real time” content supplier. Billing summaries and invoices70are also stored for later retrieval in the production center database60.

Production Center Database

Building characterization data is generated to establish a particular building's micro-demographic profile. Creating a micro-demographic begins with a building characterization process. The building characterization process consists of three components: 1) building geography—where is the building (city, state, region(s), etc.); 2) business segments—the building population is categorized into business segments (banking, insurance, financial services, law, advertising, real estate, etc.); 3) self learned—the system is able to learn building characteristics once installed. Peak travel periods (used to establish prime time periods) and average elevator occupancy (important in scheduling) are examples of self-learned characteristics.

The results of the characterization process are stored as building characterization data in production center database60for use in the scheduling process and includes the information listed in Table I below.

The results of the characterization process are stored in production center database60. The format of this data is described in the building characterization data section. Online content providers and advertisers create associations between their target audience and the buildings by specifying audience micro-demographics. The micro-demographics choices for the advertisers map one-to-one with the characterization categories for the buildings, shown in Table I therefore ensuring an association. As will be described below, a scheduling module maps the advertisements to the buildings via these associations

As stated above, “real time” information (general information) is the data which is merged with advertising data to create elevator display data. To accomplish this, the content of the “real time” information must adhere to specific formats which represent segment sections44,46of display13and describe the content50,52,54contained within those segments (FIG.4).

For example, for each “real time” content source22(FIG.1), production center database60contains an entry describing the format type and locations for each content segment within that format. The format determines the number of segments for each entry. Locations are described using Universal Resource Locators (URLs). The database parameters maintained for each “real time” content source are shown below in Table II below.

Advertising content data consists of two components. The first component defines when the advertisement must be run, the locations it is run, and for how long it runs. The second component describes where the advertisement is retrieved from and how it is inserted into the display. Consider the run parameters first. Advertisers will purchase advertising time on the system in units of Cost Per Thousand Impressions (CPM). Advertisers may further target specific demographics by requesting the advertising be distributed nationally, regionally, locally, or at a specific business segment. In addition, an advertisement campaign is likely to have time parameters as well. For example, the campaign may run for only two weeks with exposure required to be made between 10:00 AM and 1:00 PM each day. These concerns constitute the advertising run parameters. Equally important is the actual advertising content and how it is integrated into the system and displayed. The parameters that describe this information are the content parameters which include the advertising locator and format type. The database parameters maintained for each Advertising content source are shown below in Table III.

Scheduling module62has the primary function of creating building play lists by generating both advertising and “real-time” content from production center database60and then merging the content.

Referring toFIG. 6, scheduling module62performs a first parsing step (100) to determine which buildings are potential targets for each advertisement in production center database60. Scheduling module62utilizes information provided by the advertiser in an automated request entry process to generate an initial list72of buildings and advertisements which can be paired together. The entry process is available to advertisers using the production center website which provides an electronic entry form for allowing the advertisers to enter the required information needed to schedule an advertisement for viewing by a targeted demographic, business population. Alternatively, advertisers may provide the pertinent information through a phone interview, an application form, or a third party representative. Initial list72is further pruned in a second parsing step (102) using secondary criteria, such as advertisement start/finish dates, prime time requirements, delivery times, and impression parameters. The result of these pairing steps is an advertisement building-specific list68indicating advertisements and time intervals for when those advertisements could potentially be displayed.

Next, scheduler module62considers “real time” content preferences for each building as set forth by building characterization data (see Table I) associated with that building (104). Using this information, a “real time” building specific list76of “real time” content is generated.

With both the advertising content and “real time” content specified for a particular building, scheduler module62merges lists74and76to provide a building play list68(106). In particular, when merging the advertising and “real time” content for each building14, scheduler module62considers the content format, time intervals, and advertisement distribution. Time intervals and advertisement distribution are considered first because they determine when an advertisement will be displayed and what “real time” content will accompany it. “Real time” content is presented at fixed intervals (e.g., every 30 seconds). As a result, scheduler module62will place the “real time” content first.

Advertising placement is also subject to distribution and occupancy considerations. The commuting patterns of the network audience is always an important distribution consideration in effectively distributing a particular advertisement. For example, most people arrive to work, take lunch, and leave work within 30 minutes of the same time each day. Scheduler module62ensures therefore, that the same advertisement does not run within 30 minutes of when it ran the previous day for any given building. The result is a more uniform advertisement distribution within a building demographic. Advertising occupancy is another important consideration. Advertisements can be rotated quickly (e.g., every 15 seconds). Without a fully populated advertisement schedule however, system1would constantly rotate the same advertisement or a limited set of advertisements. This could be a potentially unattractive annoyance for elevator passengers. To eliminate this possible annoyance, scheduler module62lengthens the display period for each advertisement to make the transitions less noticeable.

Once advertising and “real time” content has been defined for each time slot, scheduler module62creates the display. The format of the advertising and “real time” content is critical because it determines which of a variety of templates is selected to create the overall display. As has been described, both the advertising and “real time” content must adhere to one of a set of predefined formats. When both are merged together they are placed into a frame. Frames represent the template from which the final display is generated. Since content formats can vary, scheduler module62selects the appropriate frame type in order to merge them. The number of content formats is intentionally limited to simplify the merging process. With the time slot and frame type information defined, scheduler module62is able to construct building play list68.

Referring toFIG. 7, the format of a building play list68used to manage the assembly of both “real time” content data and advertising content is shown. Play list78includes a “real time” content section80which is generated directly from “real time” data within production center database60and defines refresh periods for the “real time” content. Play list78also includes an advertising content section82which defines the time as well as frame type used for the advertising content.

Referring again toFIG. 5, production center20also includes a building loader64which serves as the interface between production center20and buildings14within system1. Because communication with the buildings occurs over Internet24, an inexpensive, yet broad distribution mechanism is provided. Unfortunately, Internet24also represents a path for potential system corruption. In consideration of this risk, system1is designed to require that each building server28request information from production center20, rather than having production center20broadcast data. Building loader64performs an authentication procedure to ensure that the request is being made from a server associated with and recognized by system1for each building requesting a play list. Before being distributed, building loader64encrypts the play list to further protect the information from potential corruption.

Billing and Database Maintenance Module

Billing and database maintenance are also critical to the closed loop nature of system1. As discussed above, scheduling module62generates building play lists based on micro-demographic parameters and the statistical probability a number of advertisement impression are made at a given time within a specific building. To close the system loop, elevator occupancy information is accumulated for each 14 building on a daily basis. This allows system1to adapt to changes in building characteristics to better distribute the advertising and content. A billing and database maintenance module66is used to provide this feedback to system1. The two operations, billing and database maintenance, leverage the same processes, but deliver different outputs. The feedback process involves overlaying building play lists68onto the building occupancy numbers. From this process, the actual number of impressions can be calculated for each advertisement. The billing operation will use the information to create reports and invoices70for the advertisers. The database maintenance operation uses this data to update production center database60with the impressions for each advertisement yet to be delivered. That is, the number of “Undelivered Impressions” (see Table III) is updated. In addition, billing and database maintenance module66will further alter the building occupancy numbers to update the building characterization data. For example, billing and database maintenance module66may update fields labeled “Building hours”, “Prime time periods” and “Average elevator occupancy” (see Table I). Important feedback here is defining dead zones (times when there are few elevator passengers), peak viewing periods, and average elevator occupancy. These are important parameters used by scheduling module62in the scheduling process.

Building Server

In general, building server28interfaces with production center20, caches advertising and “real time” content, develops elevator displays, and manages local area network30.

With reference toFIG. 8, building server28includes a production center/WAN (PCWAN) interface90which is responsible for communicating with production center20and the Internet24. As previously described, each building14receives from production center20a play list68which defines the display content and time interval the display content is to be presented. Internet24is used to capture the “real time” content and transport the advertising information. “Real time” output from interface90is deposited into a local “real time” database92while advertising output retrieved from Internet24is cached in an advertising database94. These represent local copies of the information retrieved via the Internet. Local copies are maintained in order to avoid latency problems which would realistically prohibit creating high performance display presentations including, for example, animation, streaming video, and movie effects. Updates to the databases are performed as needed as defined by the building play list.

Assembly and display of the content is performed by an Display Generator/LAN (DGLAN) Interface96which interprets building play list68and assembles the specified content. The result is an HTML file, served via local area network30to each elevator display unit10.

Building server28also includes an occupancy database98for storing information relating to occupancy of the individual elevators12in the building.

Production Center/WAN Interface

Referring toFIG. 9, PCWAN interface90manages the interaction with Internet24. Interaction with the wide area network (WAN) is generally initiated from the buildings in order to increase security within the system. PCWAN interface90includes a play list parser110, which performs a translation to create local references for the advertising and “real time” content. The translation is required because all content displayed within building14is cached locally within databases92,94. Thus, the WAN-based URLs contained in the original play list are invalid. Parser110also interacts with an advertising content accumulator112. Since advertisements are stored locally to the building, an accumulation process must take place to create this local store. Parser110initiates advertisement accumulation when it determines the play list contains an advertisement not currently available in the advertisement content database. The accumulator function will interface with the WAN to retrieve the missing content and store it in the database. The local URL for the advertisement is returned, which the parser writes to the local building play list. A similar operation takes place for “real time” content. In this case however, updates are performed based on a refresh period. The refresh period for “real time” content is defined in the building play list. Play list parser110passes the refresh period, the WAN based URL, and the “real time” database address to the “real time” proxy module116. Proxy module116schedules the refresh cycles and interfaces with the WAN interface control109to retrieve the “real time” content. The content is stored based on the locator provided by parser110.

Display Generator/LAN Interface

Referring toFIG. 10, Display Generator/LAN (DGLAN) interface96performs two distinct operations: 1) assembly and transfer of the display, and 2) occupancy data collection.

With respect to the second of these operations, occupancy calculations play a very important role in the system. Advertising is measured in cost per thousand (CPM) impression increments. An impression is defined as someone being exposed to the advertisement. In system1, advertisement exposures occur in elevators12. To quantify the number of advertisement impressions displayed using system1, a method for measuring elevator occupancy is required. The DGLAN Interface96accumulates measured information from each elevator and creates occupancy database98for each of buildings14. An occupancy accumulator130extracts the measured data from each elevator during system downtime (typically at the end of the day). This information provides the elevator occupancy at constant intervals throughout the day. Occupancy accumulator130summarizes this information into a single list, which is passed to production center20for billing.

Display assembly and transfer is the primary function of DGLAN Interface96. Display assembly is dictated by local building play list114which uses the same format as building play list68ofFIG. 5, except that the “real time” control parameters are deleted and all content locators (e.g., URLs) have been replaced by local equivalents. DGLAN Interface96includes a display format parser120and a display assembler122. Display format parser120uses Hyper Text Markup Language (HTML) to build the framework for the display. HTML is used extensively on Internet24to develop display information and is easily understood by modern browser technology. Display format parser120generates the HTML template that is used, once it is populated, to create the actual display. Local building play list114defines the frame type. Display parser120interprets the frame type and generates an HTML file, specifying the physical attributes of the display. These attributes include the absolute position, size, and definition of each content segment. Missing from the template are the pointers to these content segments. Content segment pointers are generated by display assembler122.

Display assembler122is used in the final step of the display generation cycle. Display assembly is initiated based on the time intervals defined in the play lists. Each display is assembled and passed to a display server124as defined by its time indicator. Display assembler122parses the HTML template generated by the display format parser120to find the content segment definitions. The template will match the content segment definitions specified in play list114. As a result, display assembler122inserts the location pointer for each content segment. When each content segment pointer has been inserted, the HTML file is ready to be passed to elevator display units10.

Elevator display units10are connected to the building server28via local area network30. Display server124manages local area network30by retrieving the HTML file from display assembler122along with the “real time” and advertising content specified by the HTML. Display server124then translates this data into a display format compliant with elevator display units10, encapsulates the translated data with a file transfer protocol and passes the encapsulated data to network switch40(FIG. 3) for broadcast. The task of retrieving the data from display assembler122is made more difficult by the great distances (e.g., >1500 feet) that separate building server28from elevator display units11.

Referring toFIG. 11, display server124and elevator display units10form networked host/display pairs, where elevator display13is merely an extension of the server display. The HTML file is interpreted by a browser136(e.g., Internet Explorer 4.0, a product of Microsoft Corporation®). Browser136, within the operating system (e.g., Microsoft Windows NT a product of Microsoft Corporation®) used by building server28, interfaces with a display driver138to communicate with hardware associated with display13. Display data is extracted by a translator140, which re-targets the data to elevator display unit10and display13. This data is cached local to server28to reduce the effects of browser refresh delay. A network protocol encapsulation software module142extracts the data from the cache and adds a TCP/IP communication layer. The encapsulated data is passed to the network interface and transmitted through network switch30(FIG. 3) to the LAN.

Further embodiments are supported by the following claims. For example, the distribution channel used by information distribution system1described above is the Internet24. The Internet, or “web” provides a growing and existing infrastructure for obtaining information and establishing communication between computers. However, information distribution system1can also be implemented using other communication channels including cable modem, satellite, XDSL.

Twisted pair lines38, discussed above in conjunction withFIG. 4, can be replaced with other forms of transport media including fiber optic, coaxial lines, RF transmission). Moreover, in certain applications an asymmetrical digital subscriber line (ADSL) can be substituted for the Ethernet connection in local area network30in FIG.3.

Building Owner Manager (BOM) Interface

The information distribution system1shown inFIG. 1was described above as including a production center20which interfaces with building servers28to develop presentations of merged advertising and general information for display on elevator display units10. As also stated above, system1can provide building owners and managers the ability to communicate with tenants resident in their building. As will be described immediately below, this capability is provided to building managers through a Building Owner Manager (BOM) interface.

Referring toFIG. 12, for example, a BOM interface200is shown to include BOM interfaces (BOMGUI)202which communicate with one or more building subsystems204via distribution channel24. Building subsystem204is shown to include building server28, building LAN30, and building display units206including elevator display units10mounted in elevators12. Distribution channel24, as shown inFIG. 1was represented, for example, by the Internet. In this case, distribution channel24is shown to include other interconnection approaches, such as, a direct or indirect connection via a public building LAN208, a dial-up modem210, as well as an Internet Service Provider209. It is important to note the distinction between public building LAN208and building LAN30of building subsystem204. In particular, public building LAN208represents building management's own local area network for inter-office communication. Building LAN30, on the other hand, is a private local area network, used exclusively for information distribution system1.

In general BOM interface200allows building managers to deliver messages to building tenants who can view the messages on the display units10mounted in elevators12as well as other displays206positioned throughout the building. Messages generated using a BOMGUI200are merged at the building server without interaction from production center20. Thus, building managers are able to control the creation of the messages and deploy and modify the messages quickly.

Examples of the wide variety of message types deliverable using BOM interface200include:Time critical messages including fire alarm testing, parking garage closures, changes to building hours, building-specific traffic information;special Events such as holiday events, building activities;New building features/services including health club, cafeteria facilities, parking, coffee shop, florist;Public Address/Emergency messages including instructions for stuck elevator passengers, storm warnings, fire information; andAdvertising messages such as announcements for available space, description of the management organization and their capabilities.
BOM User Interface (BOMGUI)

BOMGUI200represents the user portion of BOM interface200for providing an environment to building management to create, modify, and send messages to display units from literally anywhere in the world via nearly any of a wide variety of interconnection means.

Referring toFIG. 13, BOMGUI202uses a template212to define message structure and format. Template212is based on HTML, thus providing a flexible and rich environment for its development. In one embodiment, template212fits in a 640×480 pixel format and utilizes a comment field <!—message text—>inserted where the message information is to be placed. The message text that populates the selected template is entered using BOMGUI202. Text entry fields are provided which allow for tabs, carriage returns, and spaces, along with plain text information.

BOMGUI202is also able to import already completed html files. This enables building owners and managers the ability to create special announcements and display them on the information system without using the template structure discussed immediately above.

Message Creation

The message creation process requires that each of the fields of the template be populated. Within BOMGUI202this is accomplished in one of two ways. The first way uses a message creation wizard, a user-friendly program that takes the user through each step of the message creation process by prompting them for the required input as they populate each field. The second way uses a message entry form which may have been previously generated by the wizard and pre-stored to serve as a pattern for creating messages. This form contains all the message fields the user must populate and is typically used to edit an existing message. Using either approach, the result of the entry process is a valid message which can be displayed on the system. BOMGUI202converts the information from template212into a file, capable of being read and displayed on the display units of the system.

As will be described below, BOMGUI202includes parsers for parsing the selected template file. A first group of parsers searches for the comment field <!—message text—>. When this field is located, a second group of parsers operates on the message text to convert this information into an HTML format. The result is an HTML output file with the name <message name>.htm. This file is submitted to building server28for display on the system. BOMGUI202also allows managers the ability to preview messages prior to being displayed within the elevator or other displays in the building. This process is repeated for each message that is created by BOMGUI202.

BOM Play List Creation

BOMGUI202allows building managers to create multiple messages for display in the building. These messages may be programmed to appear simultaneously or distributed throughout the week/month/year.

Referring toFIG. 14, a BOM play list220includes a series of building messages221, each of which is comprised of several elements: start date, stop date, period of day, message template, and message text. The start and stop dates determine when the message is first displayed by the system and when it will be removed from the system. The period during the day a message can be displayed is also selectable within BOMGUI202. In one embodiment, the day is divided into four segments: AM Segment, Lunch Time (LT) Segment, PM Segment, and Sleep (SLP) Segment. These represent time slots within the day, and are system programmable. For example, the AM Segment may be defined as the time from 6:00 AM to 11:00 AM each day. The building manager may select a specific time period for the message to run or they can choose to have the message run all day. Thus, BOM play list220defines time periods when each message is displayed and for how long (e.g., month, year). The format of BOM play list220is similar to the building play list68created by Production Center20described above in conjunction withFIGS. 5-9. However, BOM play list210includes additional start and stop fields.

BOM Play List220is created using BOMGUI220and is generated by individually stepping through each HTML output file message to determine the period of day and start and stop dates. The period of day is used to define in which time segments the message will appear. The start and stop dates are transformed directly into the BOM play list format. For example, the sample BOM play list shown inFIG. 14indicates that bom_message 1.htm is programmed to run in only the AM Segment between Jun. 12, 1998 and Jun. 13, 1998 while bom_message2.htm is programmed to run all day between Jun. 12, 1998 and Jun. 14, 1998.

As stated above, BOMGUI202allows building management to send messages to displays from literally anywhere in the world. This is accomplished using off-the-shelf LAN and WAN technology available in most computers today. BOMGUI202includes a connection setup menu. The connection setup menu allows the user to define the method(s) for interfacing with the building subsystem through the distribution channel24. Using the setup menu, the user can create multiple paths to send messages to building subsystem204. For example, when residing in the building, the building manager may send messages via public building LAN208. This same building manager may also need to use BOM interface200to send messages to the system from a remote location via a dial-up modem210connection or Internet Service Provider (ISP)209. In each case, the building manager would simply define the connection information within BOMGUI202, save it, and then choose the appropriate connection setup each time a message is sent. BOMGUI202automatically attends to establishing the connection, sending the message information, and disabling the connection each time messages are submitted.

Building Subsystem

BOM interface200utilizes a BOM play list parser to parse BOM play list220in a manner similar to the manner used by play list parser110to parse building play list68, as described above in conjunction with FIG.9. Specifically, play list parser translates the BOM play list220to create local references for advertising or “real time”content.

BOM interface200is also configured to permit building owners and building managers to create and deliver messages through building server28and building LAN30to a specific one or more of elevator display units10. This flexibility is particularly useful, for example, for providing instructions to elevator passengers in a stuck elevator. As a result, building management can maintain communication with the stuck elevator passengers without alarming passengers riding in other elevators.

In some embodiments, BOM interface works in concert with the production center/WAN interface90described above in conjunction with FIG.9.

Play List Parsing/Development

Referring toFIG. 15, in this case, the local building play list parsing function of building server28must be modified to receive messages from both a play list assembled by production center20and BOM play list220.

As described above in conjunction withFIG. 9, the operation of the play list parser110in the absence of a BOM Interface was to remap the URLs to the building database. With the addition of the BOM Interface, a play list parser222must now perform both a remapping and an interleave operation.

Referring toFIG. 16, play list parser222is initiated (230) by an update to either Production Center (PC) building play list68or the BOM play list (232). If an update has not been made to either play list, parser222will await a predetermined period of time and then poll to determine a change in the update status of the play lists. On the other hand, if either play list has been updated, parser222then queries whether PC play list68has been updated (234). PC building play list68represents the baseline version of the local building play list114. That is, local building play list114is derived from the starting point created from PC building play list68. If building PC play list has been updated, parser222performs the URL remapping (236) described above with reference to FIG.9. Following the URL remapping, parser222performs a second pass to interleave information from the BOM play list220into the updated PC building play list68(238).

In other applications, BOM interface200is used independently by building managers as a means for communicating with their tenants without any interaction with a production center. In these applications, there is no PC play list within which the BOM play list interleaved. Thus, with reference toFIG. 16, play list222simply determines whether the BOM play list has been updated232and derives a local building play list114solely from BOM play list220.

The goal of the interleave function is to insert a programmed number of building manager messages every minute during the designated time period using a round robin priority scheme. The number of messages inserted per minute can be programmed from 0 to all available slots. Of course, prior to inserting a message parser222will verify that the current date and time fall within the start/stop dates and time period parameters of the message.

An example will help illustrate the manner in which parser222functions. Assume a building manager has created and downloaded the BOM Play List shown inFIG. 14, via BOMGUI (202). If the current date is Jun. 12, 1998, and the slots per minute is set to 1-, the parsers would produce a local building play list114shown in FIG.17.

Note that during the AM Segment, both bom_message1.htm and bom_message2.htm are interleaved into the PC building play list68. Also note that these messages alternate in “round-robin” fashion within the AM time segment. During the LT, PM, and SLP time periods only bom_message2.htm is displayed. In these time segments, this message will appear every minute.

Unlike the Production Center path for content assembly described above in conjunction withFIG. 10, the pages created by BOMGUI202do not require modification by the building subsystem. However, the advertising component of the page will be subject to automatic assembly within the building.

Referring toFIG. 18, BOMGUI202will deposit message files into a BOM Message Store240. As display assembler122interprets the local building play list114it will look in the BOM Message Store240for all building messages. The advertisement associated with the message is defined by the play list and is inserted by display assembler122before being passed to Display Server124.

In embodiments in which building subsystem204interfaces with production center20, a dial-up modem connection is typically used to establish the connection. To add the functionality of BOM Interface200, system1may need to be equipped with a network card to allow interaction with private building LAN30. If the BOM Interface physical interconnect is via dial-up modem210or ISP209, a single modem interface is sufficient. This is accomplished via software running on both the BOMGUI202and at the production center20which performs retries and allows data multiplexing. The result is a minimal hardware implementation.

BOM Interface Security

BOM Interface200represents a direct path into information system1. As such, security for this interface is important to insure that inappropriate or unauthorized use is not allowed. The security procedures for the system are performed at three levels: BOMGUI password protection, secure connections, and password/access protection at the building subsystem. BOMGUI202performs a username and password check procedure prior to invoking the user interface. The passwords and usernames are encrypted and stored in a protected file. Only individuals with root privileges are allowed to manipulate this information. At the physical interconnect level, the path names and dial up properties are encrypted and only accessible by authorized personnel. Lastly, building subsystem204provides two layers of protection. First, user name and password verification is performed on every message request to the system. This insures that the security monitor of system1is aware of all licensed users. Secondly, the BOM message information is kept in a separate partition on the building server28. This insures that an unauthorized user of the system is precluded from accessing other functions not associated with the system. This three phased approach should make it very difficult for any unauthorized access to the system to occur.

Still further embodiments are within the claims.