| Conference presence based music-on-hold suppression system and method -> Monitor Keywords |
|
|
  Conference presence based music-on-hold suppression system and methodRelated Patent Categories: Telecommunications, Wireless Distribution System, Combined With Diverse Art Device (e.g., Audio/sound Or Entertainment System)The Patent Description & Claims data below is from USPTO Patent Application 20070117508. Brief Patent Description - Full Patent Description - Patent Application Claims
BACKGROUND OF THE INVENTION [0001] 1. Field of the Invention [0002] The present invention is related to a private branch exchange (PBX) (or network hosted device) which can automatically disable a music-on-hold feature for one of it's extensions that is attached to a device (e.g., phone) which belongs to a user when that user happens to be participating in a multi-party conference call being hosted by an external conference/collaboration bridge. This is desirable because if the user places their device on-hold then no music or other sound will be injected into the multi-party conference call. [0003] 2. Description of Related Art [0004] A PBX typically has a music-on-hold feature such that if a user places their phone on-hold then the other party hears music/radio/company information etc. . . . This is fine in most situations. But, if the user is participating in a multi-party conference call that happens to be hosted by an external conference/collaboration bridge then this music-on-hold feature can be problematic. In particular, if the user places their phone on hold to take another phone call or to simply take a break from the multi-party conference call then music (or some other sound) is going to be played on the conference bridge to the annoyance of the other participants. [0005] Today, this problem can be addressed if the conference/collaboration bridge has a voice activity detection (VAD) system or a signal energy detection system which can detect the conference legs that are contributing to the call. This enables one to determine which conference leg happens to be playing the music-on-hold when a participant is no longer participating in the multi-party conference call. And, if the conference/collaboration bridge has a graphical user interface (GUI) that can be used by a conference host to mute the offending music that is flooding the conference bridge because that particular participant has placed their phone on-hold. However, this solution has several drawbacks which include: (1) the multi-party conference call is disrupted until the extension being used by the offending person is muted; (2) the conference host needs to have access to the GUI; and [0006] (3) the conference host needs to focus their attention on solving this problem which can be very disruptive especially if they are also speaking or presenting at the same time. Accordingly, there has been and is a need to solve this problem which is done by the present invention. BRIEF DESCRIPTION OF THE INVENTION [0007] The present invention includes a PBX (or network hosted device) which is capable of obtaining information (e.g., in-a-conference presence state) that a user is likely participating in a multi-party conference call which is being hosted by an external conference/collaboration bridge and is further capable of disabling a music-on-hold feature on an extension connected to a device belonging to the user such that if the user places the device on-hold then no music or other sound will be injected into the multi-party conference call. Several different ways in which the PBX (or network hosted device) can obtain this information so it can disable the music-on-hold feature are described herein. BRIEF DESCRIPTION OF THE DRAWINGS [0008] A more complete understanding of the present invention may be obtained by reference to the following detailed description when taken in conjunction with the accompanying drawings wherein: [0009] FIG. 1 is a block diagram that is used to help explain several different ways a PBX (or network hosted device) can obtain information so it knows when to disable a music-on-hold feature for a particular user in accordance with the present invention; and [0010] FIG. 2 is a flowchart that illustrates the basic steps of a method for enabling a PBX (or network hosted device) to automatically disable a music-on-hold feature for a particular user in accordance with the present invention. DETAILED DESCRIPTION OF THE DRAWINGS [0011] Referring to FIG. 1, there is illustrated a diagram which is used to help describe several different ways a PBX 100 (or network hosted device) can obtain information so it knows when to disable a music-on-hold feature for one of its users 106 when they happen to be participating in a multi-party conference call being hosted by an external conference/collaboration bridge 114a. Although the PBX 100 is used herein to describe the present invention, it should be appreciated that a network hosted device that has a music-on-hold feature like, for example, Centrex, IP-Centrex, a fixed line voice switch or a mobile voice switch . . . can implement the present invention. [0012] The PBX 100 needs to obtain information that person 106 is participating with several other people 108 and 110 (only two shown) in a multi-party conference call (shown as voice legs 112) being hosted by the external conference/collaboration bridge 114a before it can disable the music-on-hold for an extension 102 connected to the person's device 104 (e.g., office phone 104). This capability is important because if person 106 places their device 104 on-hold then no sound will be injected into the multi-party conference call. There are several ways the PBX 100 can obtain this information which indicates that person 106 is participating in a multi-party conference call being hosted by an external conference/collaboration bridge 114a. [0013] In one way, the PBX 100 obtains this information directly from the conference/collaboration bridge 114a (shown as option #1). In this case, the PBX 100 receives information 117 directly from the conference/collaboration bridge 114a that indicates person 106 is participating in a multi-party conference call. The conference/collaboration bridge 114a determines this information 117 by analyzing a phone number of a called/calling party that may be participating in a multi-party conference call and by mapping that phone number to the device 104 used by person 106. Upon receiving this information 117, the PBX 100 (in particular the processor/music-on-hold suppression unit 114b) disables the music-on-hold feature for that person's device 104. [0014] In another way, the PBX 100 determines by itself that person 106 is likely to be participating in a multi-party conference call which is being hosted by the external conference/collaboration bridge 114a (shown as option #2). In this case, the PBX 100 infers that person 106 is participating in a multi-party conference call by analyzing either a phone number called by person 106 or a phone number calling the person 106 and determining that the phone number is associated with the conference/collaboration bridge 114a. The PBX 100 (in particular the processor/music-on-hold suppression unit 114b) then disables the music-on-hold feature for that person's device 104. [0015] In yet another way, the PBX 100 obtains this information in the form of an in-a-conference presence state 116 from a presence system 118 (shown as option #3). In this case, the presence system 118 collects real-time information about the activities of person 106 and if the collected information indicates that person 106 is likely participating in a multi-party conference being hosted by an external conference/collaboration bridge 114a then it sets and publishes the in-a-conference presence state 116. To enable this way, the PBX 100 subscribes with the presence system 118 to be a watcher of person 106 so it can obtain published presence information about person 106 which includes the in-a-conference presence state 116. There are many different ways the presence system 118 can collect this real-time information about person 106 and then determine/infer that person 106 is participating in a multi-party conference call which is being hosted by the external conference/collaboration bridge 114a. Some of these different ways are described after a brief discussion is provided about the basic structure/function of the presence system 118. [0016] As shown, the presence system 118 includes a presence server 120 which is connected to a rules engine 121. Alternatively, the presence server 120 could be co-located with the rules engine 121. In either case, the presence server 120 is coupled via multiple Session Initiation Protocol (SIP) interfaces (for example) to various connectors 122a, 122b . . . 122g which in turn are coupled to various devices 114a, 114b . . . 114g. In this example, the connectors 122 include a conference/collaboration connector 122a, a telephony connector 122b, a calendar connector 122c, an IM connector 122d, a PC connector 122e, an email connector 122f and a miscellaneous connector 122g. And, the devices 114 include the conference/collaboration bridge 114a, a processor/music-on-hold suppression unit 114b (shown located in PBX 100), a calendar server 114c, an IM server 114d, a PC 114e, an email server 114f and miscellaneous devices 114g (e.g., personal digital assistant (PDA), mobile phone, PC). For clarity, the description provided herein about the presence system 118, the various connectors 122a, 122b . . . 122g and the various devices 114a, 114b . . . 114g omits those details that are well known in the industry and are not needed to understand the present invention. [0017] The presence server 120 collects a wide-variety of information about the real-time activities of person 106 and then the rules engine 121 aggregates and analyzes this presence information in view of preference rules/policies and if appropriate sets the in-a-conference presence state 116. Then, the presence server 120 publishes the in-a-conference presence state 116 so it can be received by the PBX 100. In this way, the PBX 100 knows that person 106 is likely to be participating in a multi-party conference call. Several different examples are described next to indicate how the presence server 120 and rules engine 121 can determine when to set the in-a-conference presence state 116. [0018] In the first example, the presence server 120 interfaces with the conference/collaboration connector 122a and obtains presence information via the conference/collaboration bridge 114a which indicates a phone number of a calling party (or a called party) that called (or was called by) the external conference/collaboration bridge 114a to participate in a multi-party conference call. The rules engine 121 analyzes this information (in view of other information) and determines that the phone number of the calling party (or called party) is associated with the device 104 that is used by person 106. The rules engine 121 then infers that person 106 is participating in a multi-party conference call hosted by the external conference/collaboration bridge 114a and sets the in-a-conference presence state 116. The presence server 120 publishes the in-a-conference presence state 116. And, the PBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person's device 104. [0019] In the second example, the presence server 120 interfaces with the telephony connector 122b and obtains presence information via the PBX 100 which indicates that person 106 used device 104 to call a particular phone number or to receive a call from a particular phone number. The rules engine 121 analyzes this information (in view of other information) and determines that this particular phone number is associated with the external conference/collaboration bridge 114a. The rules engine 121 then infers that person 106 is participating in a multi-party conference/collaboration call hosted by the external conference/collaboration bridge 114a and sets the in-a-conference presence state 116. The presence server 120 publishes the in-a-conference presence state 116. And, the PBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person's device 104. [0020] In the third example, the presence server 120 interfaces with the calendar connector 122c and obtains presence information via the calendar server 114c which indicates that person 106 is scheduled at a particular time to participate in a multi-party conference call. The rules engine 121 analyzes this information (in view of other information) and sets the in-a-conference presence state 116 when the multi-party conference call is scheduled to take place. The presence server 120 publishes the in-a-conference presence state 116. And, the PBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person's device 104. Continue reading... Full patent description for Conference presence based music-on-hold suppression system and method Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this Conference presence based music-on-hold suppression system and method patent application. ###  How KEYWORD MONITOR works... a FREE service from FreshPatents1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored. 3. Each week you receive an email with patent applications related to your keywords. Start now! - Receive info on patent apps like Conference presence based music-on-hold suppression system and method or other areas of interest. ### Previous Patent Application: Integrated direct conversion satellite tuner Next Patent Application: Satellite communication system Industry Class: Telecommunications ### FreshPatents.com Support Thank you for viewing the Conference presence based music-on-hold suppression system and method patent info. IP-related news and info Results in 0.12659 seconds Other interesting Feshpatents.com categories: Computers: Graphics , I/O , Processors , Dyn. Storage , Static Storage , Printers |
||
