Abstract:
The present multi-media communication subscriber station has battery-powered backup. A power management controller monitors the line voltage and when the line voltage falls below a predetermined voltage level, the power management controller transfers operation power from line voltage to battery. When the multi-media communication subscriber station is operating on backup battery power, non-essential functional modules may be disabled. The power management controller continues to monitor the line voltage and when line voltage resumes, operation power is transferred back to line voltage.

Description:
CROSS REFERENCE TO RELATED APPLICATIONS  
       [0001]    The present application is a continuation in part of U.S. patent application Ser. No. 09/961,532 titled Teledata Space and Docking Station with Modular and Integrated Display filed on Sep. 24, 2001 the contents of this patent application are incorporated herein. 
     
    
     
       TECHNICAL FIELD  
         [0002]    The present invention relates generally to managing multi-media communications, and more particularly to a multi-media communication subscriber station that is equipped with a power management circuit that enables the multi-media communication subscriber station to operate on battery power when a line power source (either commercial power or powered network) is unavailable or insufficient to provide operating power during periods or peak power usage.  
         BACKGROUND OF THE INVENTION  
         [0003]    In today&#39;s fast paced business world, it is common for a person to rely on a combination of communication devices, such as: desk top telephones, mobile telephones, cellular telephones, fax machines, pagers, and the like, as well as enhanced communication services, such as: voice mail, e-mail, text messaging and the like to accommodate their communication needs.  
           [0004]    In an office environment desk top telephone service is typically provided by a private telephone communication system. A contemporary private telephone communication system consists of a switching network, a plurality of desk top telephones, and a voice mail server. Each desk top telephone is coupled to the switching network by an extension line that consists of twisted pair conductors that are terminated by a telephone jack in the office. Communication between the desk top telephone and the switching network over each extension line utilizes either proprietary digital signaling or plain old telephone service (POTS) signaling. The switching network is further coupled to the public switched telephone network (PSTN) using trunk lines that are connected to a central office switch that is typically managed by the local telephone service provider. The switching network controls calls between extensions and between an extension and a remote destination via a trunk line coupled to the PSTN. The switching network also routes calls to the voice mail server when an extension remains unanswered, is busy, or is otherwise programmed to route calls to voice mail.  
           [0005]    A problem associated with such private telephone communication systems is that each desk top telephone operates from power supplied by the switching network. With all of the additional features offered on contemporary desk top telephones, the power supplied by the network may not be sufficient for operation during periods of peak power consumption. As a result, some more advanced desk top telephone devices rely on a local power source. A problem occurs when local power is interrupted or fails. Although the private telephone communication system may have battery backed power, the telephone devices connected to the private telephone communication system that operate on local power may fail. Further, the transformer units required for converting typical high voltage AC power e.g. 100V to 240V) to low voltage DC power (12V) for operating a microprocessor based device may not have additional battery backup.  
           [0006]    What is needed is a multi-media communication device that is equipped with a alternative power source such as battery power for operation when the line voltage to the communication device fails or is insufficient for peak power consumption.  
         SUMMARY OF THE INVENTION  
         [0007]    The present multi-media communication subscriber station having battery power comprises a subscriber station that communicates with a communication system that is equipped with a controller that interfaces with one or more communication medium service providers. The controller translates multi-media communications received from a multi-media service provider into the protocols required for use by the subscriber stations as well as any conventional telephone stations that may be coupled to the controller. The controller further records dynamic information relating each subscriber device to the subscriber station that is serving the subscriber device for communication and control signaling. This enables the controller to receive communication signaling for a subscriber device and translate and route communication signaling to the subscriber station serving the subscriber device. The communication and control signaling between the controller and the subscriber stations may be over a powered network (such as powered Ethernet) with the subscriber stations being powered by an internal battery to supplement power provided by the network during peak power consumption operation. And, power provided by the network may charge the internal battery during periods in which the subscriber station is dormant. The multi-media communication subscriber station is also equipped with a power management controller to manage the draw of power from the battery and the charging of the battery.  
           [0008]    The architecture of the subscriber station is modular. Multiple functional elements can be interconnected with backbone communication circuitry to form an integrated communication platform. Modular docking interfaces may be used to couple the subscriber station to portable subscriber devices and to enable integrated and coordinated communication through multiple communication medium service providers. This coordinated and integrated system architecture enables the subscriber station to merge the functionality and internal data of the various portable subscriber devices into the subscriber station, to direct the functionality and data of the subscriber station to a selected one of the portable subscriber devices, and to provide the subscriber with a simple subscriber interface.  
           [0009]    For a better understanding of the present invention, together with other and further aspects thereof, reference is made to the following description, taken in conjunction with the accompanying drawings, and its scope will be pointed out in the appended clams. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0010]    [0010]FIG. 1 is a block diagram view of a modular multi-media communication management system in accordance with one embodiment of the present invention;  
         [0011]    [0011]FIG. 2 is a perspective exploded view of a modular subscriber station in accordance with one embodiment of the present invention;  
         [0012]    [0012]FIG. 3 is a block diagram of a subscriber station in accordance with one embodiment of the present invention;  
         [0013]    [0013]FIG. 4 is a block diagram of a multi-media communication management system controller in accordance with one embodiment of the present invention;  
         [0014]    [0014]FIG. 5 illustrates in flow diagram form the operation of the present subscriber station having battery backup power;  
         [0015]    [0015]FIGS. 6A &amp; 6B illustrate table diagrams representing exemplary states of operation of a subscriber station accordance with one embodiment of the present invention;  
         [0016]    FIGS.  7  illustrate table diagrams representing exemplary states of operation of a subscriber station accordance with one embodiment of the present invention; and  
         [0017]    FIGS.  8 A- 8 D illustrate table diagrams representing an exemplary state of operation of a communication management system in accordance with one embodiment of the present invention. 
     
    
     DESCRIPTION OF THE PREFERRED EMBODIMENT  
       [0018]    It should be appreciated that many of the elements discussed in this specification may be implemented in hardware circuit(s), a processor executing software code, or a combination of a hardware circuit and a processor executing code. As such, the term circuit as used throughout this specification is intended to encompass a hardware circuit (whether discrete elements or an integrated circuit block), a processor executing code, or a combination of a hardware circuit and a processor executing code, or other combinations of the above known to those skilled in the art.  
       Subscriber Station  
       [0019]    Referring to FIGS. 1 and 2, an exemplary architecture of the multi-media communication management system  10  of the present invention is shown. The multi-media communication management system  10  includes a control unit  12  that is coupled with a plurality of local communication devices  20  over a wireless local area network  22  consisting of a plurality of wireless interface nodes  22 A,  22 B (or by a wired network connection  23  to the backbone wired network of the wireless local area network  22 ). The local communication devices  20  may include: subscriber stations  24  (subscriber stations  24 ), wireless dialog handsets  26 , traditional telephone handsets  28 , traditional fax machines  30  (both coupled through subscriber station  24 ), traditional computer systems  32 , network printers  46 , and various network appliances  34 .  
         [0020]    Each subscriber station  24  may serve one of a plurality of subscriber devices  50  that may include a subscriber data assistant  86  and a wide area network telephone  88 . Because each subscriber device  50  may be of a different size and shape than other subscriber devices, a docking interface  58  sized to the particular subscriber device  50  may be used to couple the subscriber device to the subscriber station  24 .  
         [0021]    In operation, the control unit  12  integrates and manages multi-media communication among the local communication devices  20  and between each local communication device  20  and a remote service provider (not shown) over the service provider&#39;s multi-media communication medium  18 . More specifically, the control unit  12  translates received multi-media communication signals from the multi-media communication medium  18  (or a source local device  20 ) to the protocols required for use by the destination local communication device  20  (or the multi-media communication medium  18 ).  
         [0022]    The control unit  12  includes a multi-media communication service provider bay  14  which operatively couples one of a plurality of communication medium modules  16   a - 16   d  to the control unit  12 . Each communication medium module  16   a - 16   d  is configured to interface with a service provider&#39;s multi-media communication medium  18   a - 18   d.  For purposes of illustration, communication module  16 A may be a cable modem module for communicating over coaxial cable  36  with a multi-media communication service provider such as a local cable company, communication module  16   b  may be a wide area network radio for communication over a wireless spectrum channel  38  with a wide area wireless multi-media communication service provider such as an analog or digital cellular/PCS telephone service provider, communication module  16   c  may be a customer service unit (CSU) for communication over a T 1  line  40  with a multi-media communication provider such as a local telephone service provider, and communication module  16   d  may be an optical modem for communication over a fiber channel  44  with a fiber optic multi-media communication service provider. It should be appreciated that the examples of communication modules  16   a - 16   d  are for illustrative purposes only and it is recognized that multi-media communication services may be provided by other service providers utilizing other communication technologies such as satellite RF or other. For purposes of this invention, a communication module  16  includes circuitry for interfacing between the control unit  12  and a selected multi-media communication service provider. The control unit  12  further comprises a circuit switched provider bay  25  which operatively couples one or more public switched telephone network (PSTN) channels  42 .  
         [0023]    Referring to FIG. 2, the subscriber station  24  includes a platform unit  52  that operatively couples to the control unit  12  via either a wireless communication link between a platform unit network circuit  96  and the wireless network  22  or a direct network connection  23  between the platform unit  52  and the backbone network of the wireless network  22 .  
         [0024]    A plurality of functional modules  54 ,  56 , and  60  may be coupled to the platform unit  52  to form an integrated multi-media communication platform. The platform unit  52  includes a subscriber interface docking platform  64  for coupling and optionally supporting one of a plurality of modular subscriber interface units  60  to the platform unit  52 . The modular subscriber interface unit  60   a  may include a plurality of buttons  68  in an arrangement similar to a typical telephone key pad to provide for subscriber input in a manner similar to that of a traditional telephone handset. The modular subscriber interface  60 B may include a liquid crystal touch panel display  72  to provide for subscriber input through virtual buttons visible thereon.  
         [0025]    The platform unit  52  further includes a first function specific docking platform  74   a  and a second function specific docking platform  74   b,  each of which couples to a plurality of function specific modules, such as function specific modules  54  and  56 . The first function specific docking platform  74   a  is a shallow platform for coupling to function specific modules, such as function specific module  54 , that primarily comprise function specific buttons or other circuits that may be placed within a thin module. The second function specific docking platform  74   b  is a larger platform for coupling to function specific modules, such as function specific module  56 , with more complex internal circuits requiring the additional size. In the exemplary embodiment, the function specific module  54  may include subscriber interface buttons configured for enhancing dialog communication through the subscriber station  24  such as an audio message control  76  for single button access to audio message files and dialog management controls  85  for single button control of enhanced dialog management functions. The function specific module  56  may include circuits configured for enhancing data communication through the subscriber station  24  such as an electronic message control  78  for single button access to subscriber electronic messages, a print control  80  for single button initiation of the printing of a subscriber electronic message file, and a data networking port  84 .  
         [0026]    The platform unit  52  further includes a docking bay  62  into which a modular docking interface  58  may be secured and operatively coupled to the platform unit  52 . The modular docking interface  58  supports one of a plurality of modular subscriber devices  50  within a subscriber device interface bay  66  and provides for operatively coupling the modular subscriber device  50  to the platform unit  52 . The modular docking interface further includes a plurality of control buttons  92  for single button selection of functions indicated on a display  90  on the subscriber device  50 . Exemplary configurations for the modular subscriber device  50  include a subscriber data assistant  86 , a subscriber wide area network communication device  88 , and the wireless LAN dialog handset  26 , each of which is discussed in more detail herein. While operatively coupled to the platform unit  52 , the subscriber device  50  becomes an integral part of the subscriber interface of the subscriber station  24 . A liquid crystal display  90  on the subscriber device  50  may function to display multi-media communication management information under control of the platform unit  52  and the control unit  12 . Further, programmable subscriber controls  92  positioned adjacent to the subscriber device  50  may be configured to activate platform unit  52  and control unit  12  functions in accordance with the contents of the display  90  adjacent to the controls  92 .  
         [0027]    The platform unit  52  may further include one or more of the following elements: a handset  98  similar to a traditional telephone handset to provide a subscriber voice interface, a speaker  100  and a microphone  102  to provide a hands-free subscriber voice interface, a modular battery pack  70  (which fits within a battery pack bay that is not shown) for supplementing operating power provided by the network connection  23  or line power  34  (or for operating power when the subscriber station  24  is uncoupled from such input power), an on/off hook control button (or switch), and a help control button  105 , a WAN control button  104 , and a directory control button  107 , for single button selection of certain functions such as a help function, a wide area network communication function, display of a contact directory respectively.  
       Subscriber Station Functional Diagram  
       [0028]    [0028]FIG. 3 shows a block diagram of the subscriber station  24 . The platform unit  52  includes a controller  112  operating a packet voice application, a CSS application, and applicable drivers for a plurality of peripheral controllers. The controller  112  is coupled to a local bus  116  that interconnects the application controller  112  with each of the plurality of peripheral controllers that include a wireless module  94 , a power management controller  120 , a communication controller  122 , a network switch controller  124 , a key switch controller  126 , a touch panel controller  128 , a plain old telephone service (POTS) converter  146 , a voice communication system  130 , and at least one of a wireless module  94  and a powered network interface circuit  95 .  
         [0029]    The wireless module  94  or the powered network interface circuit  95  operatively couple the platform unit  52  with the control unit  12  over the wireless LAN  22  and the wired LAN connection  23  (both of FIG. 1). The power management controller  120  selectively receives input power from the battery pack  70 , the powered network connection  23 , and external line power  134 . The power management controller  120  includes appropriate circuits for converting the input power voltage, from each of such three sources, to appropriate operating power required by each component of the subscriber station  24 . Additionally, the power management controller  120  includes appropriate circuits for charging the battery pack  70  when the platform unit  52  is coupled to the network connection  23  or the line power  134  and receiving power in excess of that required for operating the subscriber station  24  (which may include operating and/or charging the modular docking interface  58  and the modular subscriber device  50  when coupled to the platform unit  52 ).  
         [0030]    The communication controller  122  operatively couples the modular docking interface  58  and the modular subscriber device  50  to the controller  112  such that the platform  52  can exchange data with the modular subscriber device  50 . In the exemplary embodiment, the communication controller is a serial communication controller that enables the serial exchange of data with a compatible serial communication controller within the modular subscriber device  50  over a physical medium. Exemplary physical mediums include hardwired contacts, an infrared transmission, and RF transmission, however other physical mediums are envisioned and the selection of a physical medium is not critical to this invention.  
         [0031]    The network switch controller  124  provides a network data port circuit which enables the controller  112  to communicate with another network computing circuit over a network interface. The network switch controller  124  is coupled to a bus port  135  within the function specific docking platform  74   b  for coupling to a mating port  148  on the function specific module  56 .  
         [0032]    The key switch (e.g. button) controller  126  is coupled to: a connector  136   a  which in turn is coupled to a mating connector on the modular subscriber interface unit  60   a  (FIG. 2) for interconnecting the buttons  68  to the key switch controller  126 ; a connector  136   b  which in turn is coupled to a mating connector  142  on the function specific module  54  for interconnecting the buttons  76  and  85  to the key switch controller  126 ; the bus port  135  which in turn is coupled to a mating port  148  on the function specific module  56  for interconnecting the buttons  78  and  80  to the key switch controller  126 ; and the help control button  105 , the WAN control button  104 , the directory button  107 , and the on/off hook button (or switch)  109 . In the exemplary embodiment, the key switch controller  126  may drive row and column signals to the various buttons and, upon detecting a short between a row and a column (e.g. button activation) reports the button activation to the controller  112  over the bus  116 .  
         [0033]    The touch panel controller  128  is coupled to a connector  144  which in turn is coupled to a mating connector on the modular subscriber interface unit  60   b  (FIG. 2) for interconnecting the touch panel  72  to the touch panel controller  128 . In the exemplary embodiment, the touch panel controller  128  may include a separate display control circuit compatible with the resolution and color depth of the display of touch panel  72  and a separate touch panel control circuit for detecting subscriber contact with the touch panel  72 . The touch panel controller  128  is also connected to a wireless link interface  148  that communicates via a wireless link, such as infrared or a short range radio frequency, with the modular subscriber interface unit  60   b  to enable the subscriber to use the modular subscriber interface unit  60   b  as a portable hand held control unit. The touch panel controller  128  activates the wireless link interface  148  when the modular subscriber interface unit  60   b  is not connected to the connector  144  to ensure that the subscriber has uninterrupted control of the subscriber station  24 .  
         [0034]    The voice system  130  generates analog audio signals for driving the speaker  100  (or the speaker in the handset  98  of FIG. 2) and detects input form the microphone  102  (or the microphone in the handset  98 ) under the control the packet voice application  113  operated by the controller  112 .  
         [0035]    The POTS converter circuit  146  provides a standard POTS port signal (e.g. tip and ring) for operation of a traditional telephone or a traditional fax machine coupled to a POTS port  82  on the function specific module  56 . In operation the POTS converter  146  circuit interfaces between the POTS signal and the application controller  112 .  
       Control Unit  
       [0036]    [0036]FIG. 4 shows a block diagram of the control unit  12  in accordance with an exemplary embodiment of the present invention. As discussed previously, the control unit  12  includes a multi-media communication service provider bay  14  which operatively couples one of a plurality of communication medium modules  16  to the control unit  12  for providing an interface to a service provider&#39;s multi-media communication medium. The control unit  12  further includes a local area network management system  214 , a voice converter circuit  218 , a voice server  226 , a packet voice gateway  232 , a session control server  230 , messaging client  228 , a subscriber contact directory database  234 , and a network power supply  231 .  
         [0037]    The local area network management system  214  manages the communication of data between the control unit  12  and each of the local communication devices  20  (FIG. 1). The local area network management system  214  may include a network address server  220  for assigning a network address (from a block of available network addresses) to each local communication device  20  upon the local communication device subscribing to the wireless network  22  and requesting a network address. The local area network management system  214  may also include a proxy server  222  for communicating with remote devices via the service provider multi-media communication medium  18  on behalf of each of the local communication devices  20 . A port control circuit  216  may interconnect the local area network management system  214  to each of the wireless network  22 , the packet voice gateway  232 , the session control server  230 , and the messaging client  228  over standard network port connections. The messaging client  228  provides for authenticating a subscriber to a remote messaging server (not shown) coupled to the service provider multi-media communication medium  18  and copying a plurality of subscriber messages from such messaging server.  
         [0038]    The session control server  230  operates the protocols for sending multi-media content messages and control messages to each local communication device  20  over the wireless local area network  22 . In the exemplary embodiment, the communications between the session control server  230  and each local communication device occurs using tagged messages. The tag for each message identifies the content of the message to the recipient local communication device  20 .  
         [0039]    The packet voice gateway  232  provides real time voice communications between multiple local communication devices  20  and provide real time voice communications between a local communication device  20  and a remote voice communication device over either the multi-media communication service provider medium  16  or the circuit switched channel  42 .  
         [0040]    The voice converter  218  functions to convert audio signals compatible with the circuit switched channel  42  to packet voice signals compatible with the voice server  226  and the packet voice gateway  232  and, in reverse, functions to convert packet voice signals to audio signals compatible with the circuit switched channel  42 . Further, the voice converter  218  functions to convert a coded extension number (e.g. DID signal) that may be included within audio session signaling through the PSTN interface  25  to a digital format compatible with the packet voice gateway  232 .  
         [0041]    The voice mail functionality is provided by a voice server module  226 . The voice server module  226  generates audio prompts for providing a voice interface to accept an audio message from the originating device for the subscriber, store the message as a digital file, and send the digital file to the remote messaging server associated with the subscriber.  
         [0042]    In the exemplary embodiment, the packet voice gateway  232  provides a voice mail origination communication signal to the voice server module  226  and, upon the voice server module  226  responding to the voice mail origination communication signal, the packet voice gateway  232  establishes a communication session channel with the originating device, establishes a communication session channel with the voice server module  226 , and relays audio data between the two for the duration needed for accepting the audio message.  
         [0043]    The subscriber contact directory database  234  includes a contact directory for each of a plurality of subscribers. Within each contact directory are a plurality of contact files that include basic information associated with the contact, such as company name, telephone number, e-mail address, mailing address, fax number and other relevant information. The contact directory provides destination information which may be used by the packet voice gateway  232  and the session control server  230  for establishing communication channels from a subscriber station  24  to a selected contact.  
         [0044]    The voice converter  218  functions to convert audio signals compatible with the circuit switched channel  42  to packet voice signals compatible with the voice server  226  and the packet voice gateway  232  and, in reverse, functions to convert packet voice signals to audio signals compatible with the circuit switched channel  42 . Further, the voice converter  218  functions to convert a coded extension number (e.g. DID signal) that may be included within audio session signaling through the PSTN interface  25  to a digital format compatible with the packet voice gateway  232 .  
         [0045]    The power supply  231  receives local line power and generates appropriate power for provision to each subscriber station  24  over the network backbone  22  and each network connection  23 . In the exemplary embodiment the network  22  may be a Powered Ethernet network and the power supply  231  provides power with parameters in accordance with the applicable Powered Ethernet Specification. However, other powered networks are included within the scope of this invention.  
         [0046]    Each of the local area network management system  214 , the packet voice gateway  232 , the voice converter  218 , the voice server  226 , the session control server  230 , and the messaging client  228  operate as an integrated system under the control of the session control server  230 .  
       Power Management  
       [0047]    This functionality can be implemented in a number of ways, with the present description representing one of the possible implementations. There are various combinations of hardware and software elements that operate in a coordinated manner to provide the subscriber with the speed dialing functionality.  
         [0048]    Referring to the block diagram of FIG. 3, local communication device  20  platform unit  52  includes an application controller  112  that is coupled to the local bus  116  that interconnects the application controller  112  with each of the plurality of peripheral controllers including a power management controller  120 . The platform unit  52  also includes a modular battery pack  70  for operating power when the local communication device  20  is uncoupled from a line voltage. The power management controller  120  selectively receives input power from the battery pack  70  or external line power  134 . The power management controller  120  includes appropriate circuits for converting the input power voltage to appropriate operating power required by each component of the local communication device  20 . Additionally, the power management controller  120  includes appropriate circuits for charging the battery pack  70  when the platform unit  52  is coupled to the line power  134 . Power management controller  120  also generates appropriate power for operating and/or charging the modular docking interface  58  and the modular subscriber device  50  when coupled to the platform unit  52 .  
         [0049]    Operationally, the power management controller  120  includes appropriate circuitry and application software to continuously monitor the input power (from the network connection  23  and/or line power  134 ) as well as operating power of the subscriber station  24  in step  502 . When the input power falls below required operating power, the power management controller  120  provides supplemental operating power by drawing power from the battery pack  70  in step  503 . The power management controller  120  may also provide notice to the application controller  112  in step  504  of the fact that operating power is exceeding input power. In response, the application controller  112  may gradually discontinue non essential functions.  
         [0050]    In another embodiment, when the input power falls below required operating power and the charge stored within battery pack  70  falls below a predetermined threshold, then the power management controller may provide notice to the application controller  112  such that the application controller  112  may discontinue non essential functions.  
         [0051]    Non-essential functions may include such functional modules as modular docking interface  58  which couples a plurality of modular subscriber devices  50  to the platform  52 . Modular subscriber devices  50  may include devices that have an internal battery for operation. Such modular subscriber devices  50  may continue to be used by the subscriber independently via the wireless interface node  22 A and  22 B. Other nonessential functions may include functional modules that require excessive operational power such as touch panel  72 . Application controller  112  may shut down the touch panel controller  128  and the touch panel  72 . Similarly, other predetermined functional modules may be disconnected. Essential functional modules such as the wireless module  94 , the network interface circuit  95 , the voice system  130 , network switch controller  124 , and others may continue operation. The application controller  112  may monitor and record usage of the functional modules and in response to line voltage loss, disconnect non-essential functional modules in a predetermined order based on the usage of each of the non-essential functional modules.  
         [0052]    In step  509  power management controller  120  continues to monitor the input power and the operating power required. When the input power exceeds required operating power, the power management controller  120  begins transferring input power to charging circuitry to charge the battery pack  70 .  
         [0053]    In certain events, the subscriber may intentionally disconnect the subscriber station  24  from the line power  134  and from the wired network connection  23  to move the subscriber station  24  to an alternative location. When the wired network connection  23  is disconnected, the subscriber station  24  utilized the network circuit  96  for communication with the control unit  12  over the wireless network  22 . While without connection to (and drawing power from) the powered local area network connection  23  (or line power  134 ), battery pack  70  provides operational power for the subscriber station  24 .  
       Session Control Server  
       [0054]    Referring to FIG. 4 in conjunction with the tables of FIGS. 8 a - 8   d,  exemplary operation of the session management server  230  providing multi-media communication management in accordance with the present invention is shown.  
         [0055]    The session control server  230  operates as a multi-tasking event driven state machine. A separate state machine is operated by the session control server  230  for each of the local communication devices  20  (FIG. 1). During operation of each state machine, the session control server  230  receives event signals from each of the voice server  218 , the messaging client  228 , the packet switched voice gateway  232 , the multimedia communication service provider medium  18 , and the particular local communication device  20  for which the state machine is operated. Each state machine includes multiple processing states and within each processing state there are a plurality of events that may be detected by the session control server  230 . Each event has a processing state dependent processing sequence that is processed by the session control server  230 .  
         [0056]    [0056]FIGS. 8 a  through  8   d  represent tables showing exemplary operational states of the session control server  230 . Referring to the tables of FIGS. 8 a  through  8   d  in conjunction with the block diagram of FIG. 4, operation of the session control server  230  for providing exemplary multi-media communication management in accordance with the present invention is shown.  
         [0057]    The table of FIG. 8 a  represents a start up state. In the start up state, the session control server  230  is waiting for an open session request from a new subscriber station  24  on a predetermined port. When a subscriber station  24  has just operatively coupled to the local area network  22 , obtained a network address from the network address server  220 , and is ready to operate, the management client  115  (FIG. 4) sends an open session request to a predetermined network address (matching that of the session control server  230 ) on the predetermined port. Event  300  represents receipt of an open session request from the subscriber station  24 . In response to event  300 , the session control server  230  performs various steps to initiate management control of multi-media communications of the subscriber station  24  that include: establishing a session in response to the open session request; sending control messages to the subscriber station  24  that, when executed by the management client  115 , providing for the subscriber station  24  to detect its subscriber interface configuration (e.g. whether the subscriber station  24  includes a display screen and what capabilities such as vide capabilities and graphic resolution capabilities the display screen may have) and to report its subscriber interface configuration back to the session control server  230 ; obtaining the subscriber interface configuration; providing main menu display content messages and main menu layout control messages to the subscriber station  24  that are compatible with the particular display (if any) that is included in the subscriber interface reported by the subscriber station  24 ; and transitioning to a main menu state as represented by FIG. 8 b.    
         [0058]    When in the main menu state, the session control server  230  is waiting for one of a plurality of events to occur that may include an event  302  that represents a message from the subscriber station  24  indicating subscriber selection of a menu choice from the main menu, event  304  that represents receipt of a message from the subscriber station  24  indicating that the subscriber station  24  has begun a voice session between the subscriber station  24  and the packet voice gateway  232 , event  308  that represents a message from the subscriber station  24  indicating that a subscriber device  50  has been operatively coupled to, and is ready to be served by, the subscriber station  24 , and event  310  that represents a message from the subscriber station  24  indicating that the subscriber has activated a help control (for example, pressing the help button  106 ).  
         [0059]    In response to event  302 , the session control server  230  executes steps associated with the selected menu choice, and may transition to a state corresponding to the selected menu choice. For example, if one of the menu choices were to obtain stock quotes for a predetermined portfolio, obtain local weather, or obtain any other information from a predetermined Internet URL, the session control server would, in response to event  302  (e.g. the message from the subscriber station  24  indicating the menu selection) establish a TCP/IP connection with the predetermined URL, obtain the information, provide the information in the form of content messages to the subscriber station  24 , and provide control messages to the subscriber station  24  to output the content information through the audio interface or through a display screen if the subscriber station  24  is configured with a subscriber interface that includes a display screen (as determined in steps performed following event  300  of FIG. 8 a ).  
         [0060]    In response to event  304 , the session control server  230  may query the packet voice gateway  232  to obtain information regarding the voice session such as telephone number (and name or person or company associated with the telephone number) of the other device that is participating in the session through the packet voice gateway  232 , send content messages to the subscriber station  24  that includes the information regarding the voice session, and send control messages to the subscriber station  24  to output the content information on the display screen if the subscriber station  24  is configures with a subscriber interface that includes a display screen.  
         [0061]    In response to event  308  indicating that a subscriber device  50  has been coupled to the subscriber station  24 , the session control server  230  performs steps required to begin supporting the subscriber device  50  through the subscriber station  24 . Those steps may include: sending content and control messages to the subscriber station  24  that represent a script for extracting identification information from the subscriber device  50  and represent an instruction to execute the scripts, obtaining messages from the subscriber station  24  that include information about the subscriber device (such as subscriber device ID and display resolution and video capabilities) that was provided by the subscriber device in response to the subscriber station  24  executing the script, providing content messages with subscriber device main menu content and control messages for displaying the subscriber device main menu content on the subscriber device  50  display screen in accordance with the display resolution and video capabilities; and transitioning to the subscriber device main menu state as represented by FIG. 8C.  
         [0062]    In response to event  310  that represents subscriber activation of a help control such as the help button  106  while in the main menu state, the session control server  230  selects help files  233  (FIG. 2) from the database  231  that include help content (e.g. column) content that is related to the operating state of the subscriber station  24  and is in a format (e.g. row) that corresponds to the subscriber interface of the subscriber station  24  as determined during steps associated with event  300  of FIG.  8 A.  
         [0063]    More specifically (with respect to selecting help content), the session control server  233  selects the help file  233  that is matched to the most recent message received from the subscriber station  24  (except for the message indicating subscriber activation of the help control). For example, if the most recent message received from the subscriber station  24  (prior to help control activation) was a menu selection, the session control server selects the help file  233  associated with such menu selection and, if the most recent message received from the subscriber station  24  was an indication that a voice session has begun, the session control server selects the help file  233  associated with the beginning of a voice session while in the main menu state.  
         [0064]    More specifically (with respect to selecting a format, the session control server utilizes the subscriber interface configuration information provided during execution of steps related to event  300  (initial logon) to determine whether the subscriber station  24  is configured for an audio interface only, an audio interface with still image capabilities on a display screen, or an audio interface with full motion video display capabilities. The session control server then selects a file  233  that includes the content and that is either audio only, still image graphics with synchronized audio that references and explains the still image graphics, or full motion video with synchronized audio that references and explains the video images to match the subscriber interface capabilities of the subscriber station  24 .  
         [0065]    Following selection of the help file  233 , the session control server  230  will provide help content messages to the subscriber station  24  and provide subscriber interface output control messages to the subscriber station  24  to instruct the subscriber station  24  to output the help content messages through the combination of the voice interface and the still image display or video display interface as applicable.  
         [0066]    It should be appreciated that a portion of the help file  233  may include content that represents a menu of related help files. As such, after output of the help file  233  through the subscriber interface, the subscriber may select a related help file from such menu. In which case, the session control server  230  would select the related help file  233  that corresponds to the subscriber selection and execute the other steps associated with event  310 . However, if another event  310  is received indicating that the subscriber has activated the help control a second time without an intervening selection or during a during a predetermined time period following the first activation of the help control, the session control server  230  will send control messages to the subscriber station  24  instructing the subscriber station  24  to establish an audio session with the help station  25  though the packet voice gateway  232  such that the subscriber may speak with the operator of the help station  25 .  
         [0067]    The subscriber device main menu state of FIG. 8C, is similar to the main menu state of FIG. 8B except that because the subscriber station  24  is serving a subscriber device when in the subscriber device main menu state, additional functions may be available to the subscriber as menu choices. For example, a menu choice to access email messages or voice mail messages from mail boxes associated with the subscriber device may be included. When in the subscriber device main menu state, the session control server  230  is waiting for one of the events associate with the subscriber device main menu state that include event  302 , which like the main menu state, represents a message from the subscriber station  24  indicating subscriber selection of a menu choice, event  304 , which like the main menu state, represents a message from the subscriber station  24  indicating that the subscriber station  24  has begun a voice session between the subscriber station  24  and the packet voice gateway  232 , event  310 , which like the main menu state, represents a message from the subscriber station  24  indicating that the subscriber has activated a help control (for example, pressing the help button  106 ), and event  326  that represents a message from the subscriber station  24  indicating that the subscriber device  50  has been decoupled from the subscriber station  24  is no longer served by the subscriber station  24 .  
         [0068]    Events  302 ,  304 , and  310  are the same as in the main menu state and the response of the session control server  230  will be the same as discussed above with respect to FIG. 8B and are not repeated for sake of brevity. However, because of the additional functions available when the subscriber station  24  is serving a subscriber device, event  302 , which represents a message indicating subscriber selection of menu choice may include subscriber selection of a choice to obtain messages (such as by activation of the menu choice on a touch panel of the subscriber device  50  or by activation of an email button  78  as shown in FIG. 3) and may include subscriber selection of a choice to obtain voice messages (such as by activation of the menu choice on a touch panel of the subscriber device  50  or by activation of a voice mail button  76  as shown in FIG. 3).  
         [0069]    In response to these events, the session control server  230  obtains messages associated with the subscriber device  50  from a remote messaging server coupled to the service provider medium, sorts the messages in accordance with the message type selection, provide messages representing message list display content and message list display layout control in accordance with the parameters of the graphic display  90  on the subscriber device  50 , and then transitions to a message list state (FIG. 8D). In response to event  326  the control unit transitions to the main menu state (FIG. 8B).  
         [0070]    When in the message list state of FIG. 8D, the list of messages is displayed on the subscriber device  50  and the session control server  230  is waiting for one of the events associated with the message list state. The events include event  304 , which like the main menu state, represents a message from the subscriber station  24  indicating that the subscriber station  24  has begun a voice session between the subscriber station  24  and the packet voice gateway  232 , event  310 , which like the main menu state, represents a message from the subscriber station  24  indicating that the subscriber has activated a help control (for example, pressing the help button  106 ), and event  326 , which like the subscriber device main menu state, represents a message from the subscriber station  24  indicating that the subscriber device  50  has been decoupled from the subscriber station  24  is no longer served by the subscriber station  24 . The events further include event  334  that represents a message indicating that the subscriber has activated a control to obtain a voice message from the list, event  336  that represents a message indicating that the subscriber has activated a control to display a message from the list, and event  338  representing a message indicating that the subscriber has activated a control to print a message from the list.  
         [0071]    Events  304 ,  310 , and  326  are the same as in the main menu state or the subscriber device main menu state and the response of the session control server  230  will be the same as discussed above. Therefore the discussion will not be repeated for sake of brevity.  
         [0072]    In response to event  334  the session control server  230  sends the contents of the selected audio message to the subscriber station  24  and sends control messages to instruct the subscriber station  24  to output the audio content through the voice interface  130  (FIG. 4). In response to event  336  the session control server  230  provides messages representing the message display content and the message display layout control that are compatible with parameters of the graphic display  90  on the subscriber device  50 . In response to event  338 , the session control server  230  formats the selected message into a printer compatible file and sends the print file to a printer coupled to the network  22 .  
       CSS Application  
       [0073]    In the exemplary embodiment, the subscriber station (CSS) application  115  is an event driven state machine. Within each processing state various events that are generated by one of the peripheral circuits may be detected by the CSS application  115  and, upon detecting an event, a certain string of processing steps that correspond to the particular event will be performed by the CSS application  115 .  
         [0074]    Referring to the tables of FIGS. 7A and 7B in conjunction with the block diagram of FIG. 3, exemplary operational states of the CSS application  115  are shown. The start up state  346  represents the state of operation of the subscriber station  24  immediately after establishing a network connection with the control unit  12  via the network  22 . Upon establishing a connection, event  366 , the CSS application  115  initiates a session request to the session control server  230  on a predetermined port. Event  368  represents confirmation of the session from the session control server  230  and receipt of the logon script from the session control server  230 . In response to event  368 , the subscriber device processes the script which may include detecting the interface configuration of the subscriber station  24 , providing the interface configuration to the session control server  230 , and transitioning to the base state  344 .  
         [0075]    The base state  334  represents the CSS application  115  waiting for an event signal from one of the peripheral devices which may include event  354  that represents subscriber activation of touch panel  72  on the modular subscriber interface unit  60   b,  event  356  that represents subscriber activation of one of the control buttons  911 - 918  on the modular subscriber interface unit  60   b,  event  358  that represents receipt of display content and display layout control messages from the control unit  12 , event  360  that represents receipt of a message comprising a processing script from the control unit  12 , event  362  that represents a wide area network telephone signal through a wide area network subscriber device  88  (FIG. 1), event  364  that represents detecting a subscriber device  50  being coupled to the subscriber station  24 , event  350  that represents receipt of a message from the control unit  12  directed to the subscriber device  50 , and event  352  that represents receipt of a message from the subscriber device  50  directed to the control unit  12 .  
         [0076]    In response to event  356 , the CSS application  115  provides a message indicating the touch panel activation event to the session control server  230 . In response to event  358 , the CSS application  115  provides a message indicating activation of the particular control button  911 - 918  to both the packet voice application  113  and the session control server  230 . In response to event  358 , the CSS application  115  either updates the display  72  (or  72 A) on the modular subscriber interface unit  60 B (both of FIG. 2) via the touch panel controller  128  or provides the messages representing the display content and the display layout control to the subscriber device  50  via the communication controller  122  for the subscriber device  50  to update its own display. In response to event  360 , the subscriber device  50  processes the script as provided including interfacing with any of the peripheral devices as required by the script. For example, the extraction control script received from the session control server  230  may require interrogating the subscriber device  50  for identity information and providing a message representing such identification information to the session control server  230 . In response to event  362 , the subscriber device  50  may enter a wide area network communication state wherein it relays a digital representation of voice signals between the dialog system  130  and a wide area network subscriber device  88  such that a voice conversation may take through the wide area network. In response to event  364 , the subscriber station  24  may send a message indicating that a subscriber device  50  is being initialized by the subscriber station  24  (which corresponds to event  308  of FIG. 8 b ) and then returns to the base state  344 . In response to event  350 , the CSS application  115  provides the messages to the subscriber device  50  via the communication controller  122 . In response to event  352 , the CSS application  115  provides the messages to the session control server  230  via the network.  
       Packet Voice Application  
       [0077]    The packet voice application  113  also operates as an event driven state machine. Again, each state includes a plurality of events that may occur when operating in the state and a sequence of steps that the packet voice application processes in response to the event. Referring to the tables of FIGS. 6A and 6B in conjunction with the block diagram of FIG. 3, exemplary operational states of the packet voice application  113  are shown.  
         [0078]    The stand by state  280  represents the packet voice application in an inactive mode waiting for an event that may include event  388  which represents receipt of an audio session set up signal from the packet voice gateway  232 , event  390  that represents receipt of a message from the CSS application  115  that represents activation of the on/off hook button (or switch)  109 , and event  392  that represents receipt of a message from the CSS application  115  instructing the packet voice application  113  to set up an audio session with a specified destination.  
         [0079]    In response to event  388 , the packet voice application  113  transitions to a call signaling state  382  and reports the transition to the CSS application  115 . In response to event  390 , the packet voice application  113  transitions to an off hook state  384  and reports the transition to the CSS application  115 . In response to event  392 , the packet voice application  113  sends applicable call signaling messages to the packet voice gateway  232  to set up the audio session channel with the voice gateway  232  and provides for the voice gateway  232  to set up an appropriate audio session channel with the destination. The packet voice application  113  then transitions to the call signaling state  382 , and report the transition to the CSS application  115 .  
         [0080]    When in the call signaling state  382 , the packet voice application  113  is providing a ring signal to the subscriber station  24  as either a ring signal to notify the subscriber of an incoming audio session or to notify the subscriber that an audio session set up signal has been sent to the packet voice gateway  232  and a destination device is “ringing” waiting for a remote party to effectively answer the call. During the ringing state  382  the packet voice application  113  may detect events such as event  394  that represents receipt of a message that represents activation of the on/off hook button  109  (FIG. 2), event  396  that represents termination of call signaling by the packet voice gateway  232 , event  398  that represents receipt of a ready for audio session signal from the packet voice gateway  232  if the packet voice application  113  is ringing to notify the subscriber that a remote device is ringing.  
         [0081]    In response to either event  394  (and event  396  if the subscriber station  24  is currently off hook), the packet voice application  113  will return to the standby state  380  and report the state transition to the CSS application  115 . In response to event  398  (and event  396  if the subscriber station  24  is current on hook) the packet voice application will transition to an audio session state  386  and report he transition to the CSS application  115 .  
         [0082]    When in the off hook state  384 , the packet voice application  113  may be generating a dial tone through the voice system  130  as a prompt for the subscriber to use the keypad to enter a telephone number. During the off hook state  384 , the packet voice application  113  may accept events such as event  400  that represents receipt of a message that represents key pad activation, event  402  that represents validation of a number sequence as a complete telephone number that can be used to set up an audio session, and event  404  that represents receipt of a message that represents activation of the on/off hook button  109  (FIG. 2).  
         [0083]    In response event  400  the packet voice application  113  generates a DTMF tone through the voice system  130  to provide the subscriber with audio feedback and store the numeral as part of the sequence for validation. In response to event  402 , the packet voice application  113  initiates call signaling to the packet voice gateway  232  utilizing the validated number as the destination, transitions to the call signaling state  382 , and reports the transition to the CSS application  115 . In response to event  404 , the packet voice application  113  transitions to the standby state  380  and reports the transition to the CSS application  115 .  
         [0084]    When in the audio session state  386  the packet voice application  113  is relaying messages representing a real time audio dialog between the voice system  130  and the packet voice gateway  232 . When in the audio session state  386 , the packet voice application  113  may accept events such as event  406  that represents termination of the audio session by the packet voice gateway  232 , event  408  that represents receipt of a message that represents subscriber activation of a keypad numeral, and event  410  that represents receipt of a message that represents activation of the on/off hook button  109  (FIG. 2).  
         [0085]    In response to event  406 , the packet voice application  113  returns to the off hook state and reports the transition to the CSS application. In response to event  408 , the packet voice application  113  generates a DTMF tone in the audio session signals to the packet voice gateway  232 . In response to event  410 , the packet voice application  113  returns to the stand by state  380  and reports the state transition to the CSS application  115 .  
       SUMMARY  
       [0086]    It should be appreciated that the systems and methods of the present invention provide for the communication and control of multi-media messages by a central control unit and a plurality of subscriber stations operating under the control of the control unit. This coordinated and integrated system architecture enables the subscriber station to merge the functionality and internal data of various portable subscriber devices into the subscriber station, to direct the functionality and data of the subscriber station to a selected one of the portable subscriber devices, and to provide the subscriber with a simple subscriber interface.