US20070117508A1 - Conference presence based music-on-hold suppression system and method - Google Patents
Conference presence based music-on-hold suppression system and method Download PDFInfo
- Publication number
- US20070117508A1 US20070117508A1 US11/268,362 US26836205A US2007117508A1 US 20070117508 A1 US20070117508 A1 US 20070117508A1 US 26836205 A US26836205 A US 26836205A US 2007117508 A1 US2007117508 A1 US 2007117508A1
- Authority
- US
- United States
- Prior art keywords
- conference
- person
- party
- collaboration
- phone number
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/56—Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/50—Aspects of automatic or semi-automatic exchanges related to audio conference
- H04M2203/5027—Dropping a party from a conference
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42034—Calling party identification service
- H04M3/42059—Making use of the calling party identifier
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42221—Conversation recording systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42365—Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/428—Arrangements for placing incoming calls on hold
Definitions
- 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.
- PBX private branch exchange
- a device e.g., phone
- 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.
- 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.
- 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.
- 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.
- GUI graphical user interface
- 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
- 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.
- information e.g., in-a-conference presence state
- 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
- 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.
- 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 114 a .
- 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.
- 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 114 a 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 114 a.
- the PBX 100 obtains this information directly from the conference/collaboration bridge 114 a (shown as option # 1 ).
- the PBX 100 receives information 117 directly from the conference/collaboration bridge 114 a that indicates person 106 is participating in a multi-party conference call.
- the conference/collaboration bridge 114 a 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 .
- the PBX 100 (in particular the processor/music-on-hold suppression unit 114 b ) disables the music-on-hold feature for that person's device 104 .
- 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 114 a (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 114 a . The PBX 100 (in particular the processor/music-on-hold suppression unit 114 b ) then disables the music-on-hold feature for that person's device 104 .
- 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 ).
- 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 114 a then it sets and publishes the in-a-conference presence state 116 .
- 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 .
- 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 114 a . Some of these different ways are described after a brief discussion is provided about the basic structure/function of the presence system 118 .
- the presence system 118 includes a presence server 120 which is connected to a rules engine 121 .
- the presence server 120 could be co-located with the rules engine 121 .
- the presence server 120 is coupled via multiple Session Initiation Protocol (SIP) interfaces (for example) to various connectors 122 a , 122 b . . . 122 g which in turn are coupled to various devices 114 a , 114 b . . . 114 g .
- SIP Session Initiation Protocol
- the connectors 122 include a conference/collaboration connector 122 a , a telephony connector 122 b , a calendar connector 122 c , an IM connector 122 d , a PC connector 122 e , an email connector 122 f and a miscellaneous connector 122 g .
- the devices 114 include the conference/collaboration bridge 114 a , a processor/music-on-hold suppression unit 114 b (shown located in PBX 100 ), a calendar server 114 c , an IM server 114 d , a PC 114 e , an email server 114 f and miscellaneous devices 114 g (e.g., personal digital assistant (PDA), mobile phone, PC).
- PDA personal digital assistant
- the description provided herein about the presence system 118 , the various connectors 122 a , 122 b . . . 122 g and the various devices 114 a , 114 b . . . 114 g omits those details that are well known in the industry and are not needed to understand the present invention.
- 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 .
- the presence server 120 interfaces with the conference/collaboration connector 122 a and obtains presence information via the conference/collaboration bridge 114 a which indicates a phone number of a calling party (or a called party) that called (or was called by) the external conference/collaboration bridge 114 a 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 114 a and sets the in-a-conference presence state 116 .
- the presence server 120 publishes the in-a-conference presence state 116 .
- the PBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person's device 104 .
- the presence server 120 interfaces with the telephony connector 122 b 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 114 a .
- 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 114 a and sets the in-a-conference presence state 116 .
- the presence server 120 publishes the in-a-conference presence state 116 .
- the PBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person's device 104 .
- the presence server 120 interfaces with the calendar connector 122 c and obtains presence information via the calendar server 114 c 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 .
- the PBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person's device 104 .
- the presence server 120 interfaces with the IM connector 122 d and obtains presence information via the IM server 114 d which indicates that person 106 has manually set the in-a-conference presence state 116 .
- the presence server 120 publishes the in-a-conference presence state 116 .
- the PBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person's device 104 .
- the presence server 120 interfaces with the PC connector 122 e and obtains presence information via the PC 114 e which indicates that person 106 has used a GUI in their PC 114 a to call 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 114 a .
- 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 114 a and sets the in-a-conference presence state 116 .
- the presence server 120 publishes the in-a-conference presence state 116 .
- the PBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person's device 104 .
- the presence server 120 interfaces with the email connector 122 f to obtain presence information via the email server 114 f which indicates that person 106 has received and/or sent an email indicating that they are 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 .
- the PBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person's device 104 .
- the presence server 120 interfaces with the miscellaneous connector 122 g and obtains presence information via a miscellaneous device 114 g (e.g., PDA, mobile phone, PC).
- the presence information can indicate that person 106 has used a GUI, a keyboard, a keypad, a pointer, a mouse etc . . . to manually set the in-a-conference presence state 116 .
- the presence server 120 publishes the in-a-conference presence state 116 .
- the PBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person's device 104 .
- the presence server 120 can collect a wide variety of presence information about the real-time activities of person 106 and then the rules engine 121 can analyze that information and determine/infer that person 106 is likely participating in a multi-party conference call which is being hosted by the external conference/collaboration bridge 114 a .
- the presence server 120 can also collect other types of presence information which were not mentioned above but could be used by the rules engine 121 to determine/infer that person 106 is likely participating in a multi-party conference call which is being hosted by the external conference/collaboration bridge 114 a.
- the PBX 100 (in particular the processor/music-on-hold suppression unit 114 b ) obtains information that person 106 is using a device 104 (e.g., office phone 104 ) connected to the PBX's extension 102 so they can participate in a multi-party conference/collaboration session being hosted by an external conference/collaboration bridge 114 a .
- a device 104 e.g., office phone 104
- the PBX 100 can obtain this information directly from the conference/collaboration bridge 114 a (see option # 1 ).
- the PBX 100 can also determine by itself that person 106 is participating in a multi-party conference call being hosted by the conference/collaboration bridge 114 a (see option # 2 ).
- the PBX 100 can obtain this information (e.g., in-a-conference presence state 116 ) from the presence system 118 (see option # 3 ).
- the PBX 100 (in particular the processor/music-on-hold suppression unit 114 b ) after obtaining this information disables the music-on-hold feature for extension 102 which is associated with the device 104 that is being used by person 106 .
- the PBX 100 (in particular the processor/music-on-hold suppression unit 114 b ) re-enables the music-on-hold feature for extension 102 which is associated with device 104 after a predetermined amount of time has passed or when it is determined that person 106 is no longer participating in the multi-party conference call.
Abstract
Description
- 1. Field of the Invention
- 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.
- 2. Description of Related Art
- 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.
- 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
- (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.
- 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.
- 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:
-
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 -
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. - 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 itsusers 106 when they happen to be participating in a multi-party conference call being hosted by an external conference/collaboration bridge 114 a. 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. - The PBX 100 needs to obtain information that
person 106 is participating with severalother 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 114 a before it can disable the music-on-hold for anextension 102 connected to the person's device 104 (e.g., office phone 104). This capability is important because ifperson 106 places theirdevice 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 thatperson 106 is participating in a multi-party conference call being hosted by an external conference/collaboration bridge 114 a. - In one way, the PBX 100 obtains this information directly from the conference/collaboration bridge 114 a (shown as option #1). In this case, the PBX 100 receives
information 117 directly from the conference/collaboration bridge 114 a that indicatesperson 106 is participating in a multi-party conference call. The conference/collaboration bridge 114 a determines thisinformation 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 thedevice 104 used byperson 106. Upon receiving thisinformation 117, the PBX 100 (in particular the processor/music-on-hold suppression unit 114 b) disables the music-on-hold feature for that person'sdevice 104. - 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 114 a (shown as option #2). In this case, the PBX 100 infers thatperson 106 is participating in a multi-party conference call by analyzing either a phone number called byperson 106 or a phone number calling theperson 106 and determining that the phone number is associated with the conference/collaboration bridge 114 a. The PBX 100 (in particular the processor/music-on-hold suppression unit 114 b) then disables the music-on-hold feature for that person'sdevice 104. - In yet another way, the
PBX 100 obtains this information in the form of an in-a-conferencepresence state 116 from a presence system 118 (shown as option #3). In this case, thepresence system 118 collects real-time information about the activities ofperson 106 and if the collected information indicates thatperson 106 is likely participating in a multi-party conference being hosted by an external conference/collaboration bridge 114 a then it sets and publishes the in-a-conferencepresence state 116. To enable this way, thePBX 100 subscribes with thepresence system 118 to be a watcher ofperson 106 so it can obtain published presence information aboutperson 106 which includes the in-a-conferencepresence state 116. There are many different ways thepresence system 118 can collect this real-time information aboutperson 106 and then determine/infer thatperson 106 is participating in a multi-party conference call which is being hosted by the external conference/collaboration bridge 114 a. Some of these different ways are described after a brief discussion is provided about the basic structure/function of thepresence system 118. - As shown, the
presence system 118 includes apresence server 120 which is connected to arules engine 121. Alternatively, thepresence server 120 could be co-located with therules engine 121. In either case, thepresence server 120 is coupled via multiple Session Initiation Protocol (SIP) interfaces (for example) tovarious connectors various devices 114 a, 114 b . . . 114 g. In this example, theconnectors 122 include a conference/collaboration connector 122 a, atelephony connector 122 b, acalendar connector 122 c, anIM connector 122 d, aPC connector 122 e, anemail connector 122 f and amiscellaneous connector 122 g. And, thedevices 114 include the conference/collaboration bridge 114 a, a processor/music-on-hold suppression unit 114 b (shown located in PBX 100), acalendar server 114 c, anIM server 114 d, a PC 114 e, an email server 114 f andmiscellaneous devices 114 g (e.g., personal digital assistant (PDA), mobile phone, PC). For clarity, the description provided herein about thepresence system 118, thevarious connectors various devices 114 a, 114 b . . . 114 g omits those details that are well known in the industry and are not needed to understand the present invention. - The
presence server 120 collects a wide-variety of information about the real-time activities ofperson 106 and then therules engine 121 aggregates and analyzes this presence information in view of preference rules/policies and if appropriate sets the in-a-conferencepresence state 116. Then, thepresence server 120 publishes the in-a-conferencepresence state 116 so it can be received by thePBX 100. In this way, the PBX 100 knows thatperson 106 is likely to be participating in a multi-party conference call. Several different examples are described next to indicate how thepresence server 120 andrules engine 121 can determine when to set the in-a-conferencepresence state 116. - In the first example, the
presence server 120 interfaces with the conference/collaboration connector 122 a and obtains presence information via the conference/collaboration bridge 114 a which indicates a phone number of a calling party (or a called party) that called (or was called by) the external conference/collaboration bridge 114 a to participate in a multi-party conference call. Therules 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 thedevice 104 that is used byperson 106. Therules engine 121 then infers thatperson 106 is participating in a multi-party conference call hosted by the external conference/collaboration bridge 114 a and sets the in-a-conferencepresence state 116. Thepresence server 120 publishes the in-a-conferencepresence state 116. And, the PBX 100 after receiving the published in-a-conferencepresence state 116 disables the music-on-hold feature for person'sdevice 104. - In the second example, the
presence server 120 interfaces with thetelephony connector 122 b and obtains presence information via thePBX 100 which indicates thatperson 106 useddevice 104 to call a particular phone number or to receive a call from a particular phone number. Therules 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 114 a. Therules engine 121 then infers thatperson 106 is participating in a multi-party conference/collaboration call hosted by the external conference/collaboration bridge 114 a and sets the in-a-conferencepresence state 116. Thepresence server 120 publishes the in-a-conferencepresence state 116. And, the PBX 100 after receiving the published in-a-conferencepresence state 116 disables the music-on-hold feature for person'sdevice 104. - In the third example, the
presence server 120 interfaces with thecalendar connector 122 c and obtains presence information via thecalendar server 114 c which indicates thatperson 106 is scheduled at a particular time to participate in a multi-party conference call. Therules engine 121 analyzes this information (in view of other information) and sets the in-a-conferencepresence state 116 when the multi-party conference call is scheduled to take place. Thepresence server 120 publishes the in-a-conference presence state 116. And, thePBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person'sdevice 104. - In the fourth example, the
presence server 120 interfaces with theIM connector 122 d and obtains presence information via theIM server 114 d which indicates thatperson 106 has manually set the in-a-conference presence state 116. Thepresence server 120 publishes the in-a-conference presence state 116. And, thePBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person'sdevice 104. - In the fifth example, the
presence server 120 interfaces with thePC connector 122 e and obtains presence information via thePC 114 e which indicates thatperson 106 has used a GUI in their PC 114 a to call a particular phone number. Therules 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 114 a. Therules engine 121 then infers thatperson 106 is participating in a multi-party conference/collaboration call hosted by the external conference/collaboration bridge 114 a and sets the in-a-conference presence state 116. Thepresence server 120 publishes the in-a-conference presence state 116. And, thePBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person'sdevice 104. - In the sixth example, the
presence server 120 interfaces with theemail connector 122 f to obtain presence information via the email server 114 f which indicates thatperson 106 has received and/or sent an email indicating that they are scheduled at a particular time to participate in a multi-party conference call. Therules 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. Thepresence server 120 publishes the in-a-conference presence state 116. And, thePBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person'sdevice 104. - In the seventh example, the
presence server 120 interfaces with themiscellaneous connector 122 g and obtains presence information via amiscellaneous device 114 g (e.g., PDA, mobile phone, PC). The presence information can indicate thatperson 106 has used a GUI, a keyboard, a keypad, a pointer, a mouse etc . . . to manually set the in-a-conference presence state 116. Thepresence server 120 publishes the in-a-conference presence state 116. And, thePBX 100 after receiving the published in-a-conference presence state 116 disables the music-on-hold feature for person'sdevice 104. - As can be seen, the
presence server 120 can collect a wide variety of presence information about the real-time activities ofperson 106 and then therules engine 121 can analyze that information and determine/infer thatperson 106 is likely participating in a multi-party conference call which is being hosted by the external conference/collaboration bridge 114 a. Of course, it should be appreciated that thepresence server 120 can also collect other types of presence information which were not mentioned above but could be used by therules engine 121 to determine/infer thatperson 106 is likely participating in a multi-party conference call which is being hosted by the external conference/collaboration bridge 114 a. - Referring to
FIG. 2 , there is a flowchart of the basic steps of themethod 200 for enabling the PBX 100 (or network hosted device 100) to automatically disable the music-on-hold feature for auser 106 when they happen to be participating in a multi-party conference call which is being hosted by an external conference/collaboration bridge 114 a. Beginning atstep 202, the PBX 100 (in particular the processor/music-on-hold suppression unit 114 b) obtains information thatperson 106 is using a device 104 (e.g., office phone 104) connected to the PBX'sextension 102 so they can participate in a multi-party conference/collaboration session being hosted by an external conference/collaboration bridge 114 a. As discussed above, thePBX 100 can obtain this information directly from the conference/collaboration bridge 114 a (see option #1). ThePBX 100 can also determine by itself thatperson 106 is participating in a multi-party conference call being hosted by the conference/collaboration bridge 114 a (see option #2). In addition, thePBX 100 can obtain this information (e.g., in-a-conference presence state 116) from the presence system 118 (see option #3). Atstep 204, the PBX 100 (in particular the processor/music-on-hold suppression unit 114 b) after obtaining this information disables the music-on-hold feature forextension 102 which is associated with thedevice 104 that is being used byperson 106. At this time, ifperson 106 places thedevice 104 on-hold then no sound will be injected into the multi-party conference call. Atstep 206, the PBX 100 (in particular the processor/music-on-hold suppression unit 114 b) re-enables the music-on-hold feature forextension 102 which is associated withdevice 104 after a predetermined amount of time has passed or when it is determined thatperson 106 is no longer participating in the multi-party conference call. - Following are some additional features, advantages and uses of the present invention:
-
- The
PBX 100, thepresence system 118 and themethod 200 can support and monitor any number of people even though only oneperson 106 shown and described herein. - The
presence system 118 can be configured to error on the side of safety when it is determining whether or notperson 106 is participating in a multi-party conference call and set the in-a-conference presence state 116. Because, if thePBX 100 disables the music-on-hold feature andperson 106 is not participating in a multi-party conference then there is little if any harm that can be done except that another person will not hear music when they are placed on hold. - The music-on-
hold suppression unit 114 b could be located external to thePBX 100. In this case, the music-on-hold suppression unit 114 b would communicate via a computer-telephony interface (CTI) with thePBX 100. This scenario is not shown inFIG. 1 . - The
PBX 100 can obtain other types of presence information from thepresence system 118 in addition to the in-a-conference presence state 116. However, thepresence system 118 may have rules/policies that are used to decide which presence information should be sent to thePBX 100. - Even though
person 106 is described herein as participating in a multi-party conference call. It should be understood that the present invention can also be used ifperson 106 happens to be participating in a collaboration session. - The present invention can be related and coupled with another invention discussed in the following documents:
- U.S. patent application Ser. No. 11/233,987 filed on Sep. 23, 2005 and entitled “Telephony/Conference Activity Presence State”.
- U.S. patent application Ser. No.______ filed on ______ and entitled “System and Methods for using Data about who is speaking in a Communications Conference to Enhance Business use of Temporal Identification of Those Participating and of Communications Conference Archives” (Attorney Docket No. Alcatel FIT #139409).
- The
- The contents of these documents are hereby incorporated by reference herein.
-
- An external conference solution provider (customer premises based or carrier based) could provide this conference presence service and PBX enhancement system as a value added service to their customers. For example, Alcatel's eDial product can be enhanced in accordance with the present invention and then be coupled with a vendor's PBXs via a GETS-like CTI connector.
- For a more detailed discussion about the basics of the
presence system 118, reference is made to the following documents:- Jack Jachner et al. “Rich Presence: A New User Communications Experience” Technology White Paper, 8 pages, copyrighted 1st quarter 2005.
- J. Rosenberg, “A Data Model for presence”, draft-ietf-simple-data-model-05 (work in progress), Sep. 22, 2005.
- Rosenberg, J. “A presence Event package for the Session initiation protocol (SIP)”, RFC 3856, August 2004.
- H. Shulzerine et al. “RPID: Rich Presence Extensions to the presence Information Data Format (PIDF)”, draft-ietf-simple-rpid-08, (work in progress), Jul. 16, 2005.
- Rosenberg, J. “Presence Authorization Rules”, draft-ietf-simple-presence-rules-03(work in progress), Jul. 20, 2005.
- The contents of these documents are incorporated by reference herein.
- Although several embodiments of the present invention have been illustrated in the accompanying Drawings and described in the foregoing Detailed Description, it should be understood that the invention is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications and substitutions without departing from the spirit of the invention as set forth and defined by the following claims.
Claims (26)
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/268,362 US20070117508A1 (en) | 2005-11-07 | 2005-11-07 | Conference presence based music-on-hold suppression system and method |
AT06018288T ATE510402T1 (en) | 2005-11-07 | 2006-09-01 | METHOD AND SYSTEM FOR THE PRESENCE-BASED SUPPRESSION OF MUSIC ON WAIT IN A CONFERENCE |
EP06018288A EP1783995B1 (en) | 2005-11-07 | 2006-09-01 | Conference presence based music-on-hold suppression system and method |
JP2006293596A JP2007135204A (en) | 2005-11-07 | 2006-10-30 | System and method for suppressing sound-on-hold based on presence in conference |
CN2006101437976A CN1964397B (en) | 2005-11-07 | 2006-11-06 | Conference presence based music-on-hold suppression system and method |
US14/035,741 US9363382B2 (en) | 2005-11-07 | 2013-09-24 | Conference presence based music-on-hold suppression system and method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/268,362 US20070117508A1 (en) | 2005-11-07 | 2005-11-07 | Conference presence based music-on-hold suppression system and method |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/035,741 Division US9363382B2 (en) | 2005-11-07 | 2013-09-24 | Conference presence based music-on-hold suppression system and method |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070117508A1 true US20070117508A1 (en) | 2007-05-24 |
Family
ID=37762602
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/268,362 Abandoned US20070117508A1 (en) | 2005-11-07 | 2005-11-07 | Conference presence based music-on-hold suppression system and method |
US14/035,741 Active 2026-03-30 US9363382B2 (en) | 2005-11-07 | 2013-09-24 | Conference presence based music-on-hold suppression system and method |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/035,741 Active 2026-03-30 US9363382B2 (en) | 2005-11-07 | 2013-09-24 | Conference presence based music-on-hold suppression system and method |
Country Status (5)
Country | Link |
---|---|
US (2) | US20070117508A1 (en) |
EP (1) | EP1783995B1 (en) |
JP (1) | JP2007135204A (en) |
CN (1) | CN1964397B (en) |
AT (1) | ATE510402T1 (en) |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060218268A1 (en) * | 2005-03-28 | 2006-09-28 | Andre Beck | Method and apparatus for extending service mediation to intelligent voice-over-IP endpoint terminals |
US20070223673A1 (en) * | 2006-03-21 | 2007-09-27 | Pfleging Gerald W | Muting conference call hold music |
US20070223666A1 (en) * | 2006-03-27 | 2007-09-27 | Les Teague | Electronic equipment and service providing personalized call features |
US20080055263A1 (en) * | 2006-09-06 | 2008-03-06 | Lemay Stephen O | Incoming Telephone Call Management for a Portable Multifunction Device |
US20080100693A1 (en) * | 2006-10-26 | 2008-05-01 | Jobs Steven P | Method, System, and Graphical User Interface for Making Conference Calls |
US20080168361A1 (en) * | 2007-01-07 | 2008-07-10 | Scott Forstall | Portable Multifunction Device, Method, and Graphical User Interface for Conference Calling |
US20080310607A1 (en) * | 2007-06-17 | 2008-12-18 | Alcatel Lucent | Presence Based DTMF Signaling Enablement of Voice Communication Controller and Method |
US20090296910A1 (en) * | 2008-05-28 | 2009-12-03 | Bushnell William J | Enabling and disabling terminating features of a terminating switch |
US20100149307A1 (en) * | 2008-06-13 | 2010-06-17 | Polycom, Inc. | Extended Presence for Video Conferencing Systems |
US8014760B2 (en) | 2006-09-06 | 2011-09-06 | Apple Inc. | Missed telephone call management for a portable multifunction device |
CN102438183A (en) * | 2011-11-24 | 2012-05-02 | 杭州世导通讯有限公司 | Data disaster-tolerant communication maintaining method in TCAP (transaction capabilities application part) mode |
US8612211B1 (en) * | 2012-09-10 | 2013-12-17 | Google Inc. | Speech recognition and summarization |
US8819129B1 (en) * | 2006-06-09 | 2014-08-26 | Avaya Inc. | Auto join conference |
US9443518B1 (en) | 2011-08-31 | 2016-09-13 | Google Inc. | Text transcript generation from a communication session |
US9697198B2 (en) * | 2015-10-05 | 2017-07-04 | International Business Machines Corporation | Guiding a conversation based on cognitive analytics |
US9893902B2 (en) * | 2011-05-31 | 2018-02-13 | Google Llc | Muting participants in a communication session |
CN108206927A (en) * | 2016-12-20 | 2018-06-26 | 北京视联动力国际信息技术有限公司 | A kind of meeting synchronous method and device |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8300558B2 (en) * | 2009-01-19 | 2012-10-30 | Avaya Inc. | Feature interaction detection in multi-party calls and calls with bridged appearances |
US8917844B2 (en) | 2009-01-19 | 2014-12-23 | Avaya Inc. | Mid-call detection and resolution of feature interactions |
US9191234B2 (en) | 2009-04-09 | 2015-11-17 | Rpx Clearinghouse Llc | Enhanced communication bridge |
EP2433384A2 (en) | 2009-06-29 | 2012-03-28 | Avaya Inc. | Interaction detection between web-enabled and call-related features |
JP5570968B2 (en) * | 2010-12-27 | 2014-08-13 | 三洋電機株式会社 | Telephone equipment |
TWI618268B (en) * | 2012-12-07 | 2018-03-11 | 晶元光電股份有限公司 | Light emitting devive |
TWI533478B (en) * | 2013-10-14 | 2016-05-11 | 新世紀光電股份有限公司 | Flip chip light emitting diode package structure |
CN103685245B (en) * | 2013-11-29 | 2017-05-10 | 杭州华三通信技术有限公司 | Conversation music control method and device |
US10511806B2 (en) | 2017-09-30 | 2019-12-17 | International Business Machines Corporation | Mitigating effects of distracting sounds in an audio transmission of a conversation between participants |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6353662B1 (en) * | 1997-10-17 | 2002-03-05 | At&T Corp. | Method and apparatus for eliminating nuisance signals in multi-party calls |
US6556670B1 (en) * | 1998-08-21 | 2003-04-29 | Lucent Technologies Inc. | Method for solving the music-on-hold problem in an audio conference |
US6714634B1 (en) * | 2000-08-03 | 2004-03-30 | Motorola, Inc. | Method and apparatus for selecting disabling music on hold in a telecommunication system |
US6870807B1 (en) * | 2000-05-15 | 2005-03-22 | Avaya Technology Corp. | Method and apparatus for suppressing music on hold |
US20050238156A1 (en) * | 2003-12-22 | 2005-10-27 | Tod Turner | System and method for initiating a conference call |
US6978001B1 (en) * | 2001-12-31 | 2005-12-20 | Cisco Technology, Inc. | Method and system for controlling audio content during multiparty communication sessions |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1538728B (en) * | 2003-04-18 | 2011-08-17 | 杭州世导科技有限公司 | Method of inhibiting noise in multiple talking |
US7752268B2 (en) * | 2003-09-25 | 2010-07-06 | Oracle America, Inc. | Method and system for presence state assignment based on schedule information in an instant messaging system |
US20050113134A1 (en) * | 2003-11-24 | 2005-05-26 | Bushnell William J. | System for providing interoperability of a proprietary enterprise communication network with a cellular communication network |
DE102004009653A1 (en) * | 2004-02-27 | 2005-09-22 | Cycos Ag | Communication server and method for establishing and operating a conference communication connection |
US7813483B2 (en) * | 2005-04-28 | 2010-10-12 | Cisco Technology, Inc. | System and method for providing presence information to voicemail users |
-
2005
- 2005-11-07 US US11/268,362 patent/US20070117508A1/en not_active Abandoned
-
2006
- 2006-09-01 AT AT06018288T patent/ATE510402T1/en not_active IP Right Cessation
- 2006-09-01 EP EP06018288A patent/EP1783995B1/en not_active Not-in-force
- 2006-10-30 JP JP2006293596A patent/JP2007135204A/en active Pending
- 2006-11-06 CN CN2006101437976A patent/CN1964397B/en not_active Expired - Fee Related
-
2013
- 2013-09-24 US US14/035,741 patent/US9363382B2/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6353662B1 (en) * | 1997-10-17 | 2002-03-05 | At&T Corp. | Method and apparatus for eliminating nuisance signals in multi-party calls |
US6556670B1 (en) * | 1998-08-21 | 2003-04-29 | Lucent Technologies Inc. | Method for solving the music-on-hold problem in an audio conference |
US6870807B1 (en) * | 2000-05-15 | 2005-03-22 | Avaya Technology Corp. | Method and apparatus for suppressing music on hold |
US6714634B1 (en) * | 2000-08-03 | 2004-03-30 | Motorola, Inc. | Method and apparatus for selecting disabling music on hold in a telecommunication system |
US6978001B1 (en) * | 2001-12-31 | 2005-12-20 | Cisco Technology, Inc. | Method and system for controlling audio content during multiparty communication sessions |
US20050238156A1 (en) * | 2003-12-22 | 2005-10-27 | Tod Turner | System and method for initiating a conference call |
Cited By (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060218268A1 (en) * | 2005-03-28 | 2006-09-28 | Andre Beck | Method and apparatus for extending service mediation to intelligent voice-over-IP endpoint terminals |
US7929679B2 (en) * | 2006-03-21 | 2011-04-19 | Alcatel-Lucent Usa Inc. | Muting conference call hold music |
US20070223673A1 (en) * | 2006-03-21 | 2007-09-27 | Pfleging Gerald W | Muting conference call hold music |
US20070223666A1 (en) * | 2006-03-27 | 2007-09-27 | Les Teague | Electronic equipment and service providing personalized call features |
US8819129B1 (en) * | 2006-06-09 | 2014-08-26 | Avaya Inc. | Auto join conference |
US20080055263A1 (en) * | 2006-09-06 | 2008-03-06 | Lemay Stephen O | Incoming Telephone Call Management for a Portable Multifunction Device |
US8452342B2 (en) | 2006-09-06 | 2013-05-28 | Apple Inc. | Missed telephone call management for a portable multifunction device |
US11039283B2 (en) | 2006-09-06 | 2021-06-15 | Apple Inc. | User interfaces for a messaging application |
US10536819B2 (en) | 2006-09-06 | 2020-01-14 | Apple Inc. | Missed telephone call management for a portable multifunction device |
US8255003B2 (en) | 2006-09-06 | 2012-08-28 | Apple Inc. | Missed telephone call management for a portable multifunction device |
US8014760B2 (en) | 2006-09-06 | 2011-09-06 | Apple Inc. | Missed telephone call management for a portable multifunction device |
US8135389B2 (en) | 2006-09-06 | 2012-03-13 | Apple Inc. | Missed telephone call management for a portable multifunction device |
US20080100693A1 (en) * | 2006-10-26 | 2008-05-01 | Jobs Steven P | Method, System, and Graphical User Interface for Making Conference Calls |
US8090087B2 (en) | 2006-10-26 | 2012-01-03 | Apple Inc. | Method, system, and graphical user interface for making conference calls |
US20080168361A1 (en) * | 2007-01-07 | 2008-07-10 | Scott Forstall | Portable Multifunction Device, Method, and Graphical User Interface for Conference Calling |
US10999442B2 (en) | 2007-01-07 | 2021-05-04 | Apple Inc. | Portable multifunction device, method, and graphical user interface for conference calling |
US10320987B2 (en) | 2007-01-07 | 2019-06-11 | Apple Inc. | Portable multifunction device, method, and graphical user interface for conference calling |
US7975242B2 (en) | 2007-01-07 | 2011-07-05 | Apple Inc. | Portable multifunction device, method, and graphical user interface for conference calling |
US9706054B2 (en) | 2007-01-07 | 2017-07-11 | Apple Inc. | Portable multifunction device, method, and graphical user interface for conference calling |
US11405507B2 (en) | 2007-01-07 | 2022-08-02 | Apple Inc. | Portable multifunction device, method, and graphical user interface for conference calling |
US11743390B2 (en) | 2007-01-07 | 2023-08-29 | Apple Inc. | Portable multifunction device, method, and graphical user interface for conference calling |
US9325852B2 (en) | 2007-01-07 | 2016-04-26 | Apple Inc. | Portable multifunction device, method, and graphical user interface for conference calling |
US8972904B2 (en) | 2007-01-07 | 2015-03-03 | Apple Inc. | Portable multifunction device, method, and graphical user interface for conference calling |
US8498390B2 (en) | 2007-06-17 | 2013-07-30 | Alcatel Lucent | Presence based DTMF signaling enablement of voice communication controller and method |
US20080310607A1 (en) * | 2007-06-17 | 2008-12-18 | Alcatel Lucent | Presence Based DTMF Signaling Enablement of Voice Communication Controller and Method |
US8041015B2 (en) | 2007-06-17 | 2011-10-18 | Alcatel Lucent | Presence based DTMF signaling enablement of voice communication controller and method |
US20090296910A1 (en) * | 2008-05-28 | 2009-12-03 | Bushnell William J | Enabling and disabling terminating features of a terminating switch |
US8094799B2 (en) * | 2008-05-28 | 2012-01-10 | Alcatel Lucent | Enabling and disabling terminating features of a terminating switch |
US8941711B2 (en) | 2008-06-13 | 2015-01-27 | Polycom, Inc. | Extended presence for video conferencing systems |
US20100149307A1 (en) * | 2008-06-13 | 2010-06-17 | Polycom, Inc. | Extended Presence for Video Conferencing Systems |
US8330795B2 (en) * | 2008-06-13 | 2012-12-11 | Polycom, Inc. | Extended presence for video conferencing systems |
US9893902B2 (en) * | 2011-05-31 | 2018-02-13 | Google Llc | Muting participants in a communication session |
US10019989B2 (en) | 2011-08-31 | 2018-07-10 | Google Llc | Text transcript generation from a communication session |
US9443518B1 (en) | 2011-08-31 | 2016-09-13 | Google Inc. | Text transcript generation from a communication session |
CN102438183A (en) * | 2011-11-24 | 2012-05-02 | 杭州世导通讯有限公司 | Data disaster-tolerant communication maintaining method in TCAP (transaction capabilities application part) mode |
US10185711B1 (en) | 2012-09-10 | 2019-01-22 | Google Llc | Speech recognition and summarization |
US10496746B2 (en) | 2012-09-10 | 2019-12-03 | Google Llc | Speech recognition and summarization |
US10679005B2 (en) | 2012-09-10 | 2020-06-09 | Google Llc | Speech recognition and summarization |
US9420227B1 (en) | 2012-09-10 | 2016-08-16 | Google Inc. | Speech recognition and summarization |
US11669683B2 (en) | 2012-09-10 | 2023-06-06 | Google Llc | Speech recognition and summarization |
US8612211B1 (en) * | 2012-09-10 | 2013-12-17 | Google Inc. | Speech recognition and summarization |
US9697198B2 (en) * | 2015-10-05 | 2017-07-04 | International Business Machines Corporation | Guiding a conversation based on cognitive analytics |
CN108206927A (en) * | 2016-12-20 | 2018-06-26 | 北京视联动力国际信息技术有限公司 | A kind of meeting synchronous method and device |
Also Published As
Publication number | Publication date |
---|---|
ATE510402T1 (en) | 2011-06-15 |
US20140023184A1 (en) | 2014-01-23 |
CN1964397B (en) | 2010-05-12 |
JP2007135204A (en) | 2007-05-31 |
EP1783995A1 (en) | 2007-05-09 |
US9363382B2 (en) | 2016-06-07 |
EP1783995B1 (en) | 2011-05-18 |
CN1964397A (en) | 2007-05-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9363382B2 (en) | Conference presence based music-on-hold suppression system and method | |
US7570752B2 (en) | Telephony/conference activity presence state | |
US7933397B2 (en) | Telephone system that notifies caller of called party's state | |
US20070081640A1 (en) | Presence and preference enabled voice response system and method | |
US20030048880A1 (en) | Voice identification pre-screening and redirection system | |
US20070127400A1 (en) | Professional Services Communications Architecture | |
CA2958354C (en) | Customer premises call handling | |
JP2010263617A (en) | Annoying telephone-call prediction and prevention | |
US20080037446A1 (en) | Facilitating connection to a conference call | |
US8498390B2 (en) | Presence based DTMF signaling enablement of voice communication controller and method | |
TW200841694A (en) | Real-time two-way communication connection method integrated with web page | |
US8310959B2 (en) | Voice Communication with any of multiple terminals | |
KR20030063064A (en) | Method and System for Providing a CTI Service for Extention Terminal by Using an IP-PBX | |
KR100427861B1 (en) | Telephone information system in internet and the method of offer thereof | |
KR20020066893A (en) | An Escorted Browsing service method using ANI and DNIS | |
GB2424142A (en) | Call handling in a telecommunications network | |
JP2011193049A (en) | Device, method, and program for determining calling party | |
TWM431519U (en) | Broadband loop network seats partition on-duty system | |
KR20100094745A (en) | Voip based absentee call connection service method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ALCATEL, FRANCE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:JACHNER, JACK;REEL/FRAME:016792/0418 Effective date: 20051104 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:LUCENT, ALCATEL;REEL/FRAME:029821/0001 Effective date: 20130130 Owner name: CREDIT SUISSE AG, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:ALCATEL LUCENT;REEL/FRAME:029821/0001 Effective date: 20130130 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |
|
AS | Assignment |
Owner name: ALCATEL LUCENT, FRANCE Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG;REEL/FRAME:033868/0555 Effective date: 20140819 |
|
AS | Assignment |
Owner name: ALCATEL LUCENT, FRANCE Free format text: CHANGE OF NAME;ASSIGNOR:ALCATEL;REEL/FRAME:039094/0202 Effective date: 20061130 |
|
AS | Assignment |
Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NOKIA TECHNOLOGIES OY;NOKIA SOLUTIONS AND NETWORKS BV;ALCATEL LUCENT SAS;REEL/FRAME:043877/0001 Effective date: 20170912 Owner name: NOKIA USA INC., CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNORS:PROVENANCE ASSET GROUP HOLDINGS, LLC;PROVENANCE ASSET GROUP LLC;REEL/FRAME:043879/0001 Effective date: 20170913 Owner name: CORTLAND CAPITAL MARKET SERVICES, LLC, ILLINOIS Free format text: SECURITY INTEREST;ASSIGNORS:PROVENANCE ASSET GROUP HOLDINGS, LLC;PROVENANCE ASSET GROUP, LLC;REEL/FRAME:043967/0001 Effective date: 20170913 |
|
AS | Assignment |
Owner name: NOKIA US HOLDINGS INC., NEW JERSEY Free format text: ASSIGNMENT AND ASSUMPTION AGREEMENT;ASSIGNOR:NOKIA USA INC.;REEL/FRAME:048370/0682 Effective date: 20181220 |
|
AS | Assignment |
Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKETS SERVICES LLC;REEL/FRAME:058983/0104 Effective date: 20211101 Owner name: PROVENANCE ASSET GROUP HOLDINGS LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKETS SERVICES LLC;REEL/FRAME:058983/0104 Effective date: 20211101 Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOKIA US HOLDINGS INC.;REEL/FRAME:058363/0723 Effective date: 20211129 Owner name: PROVENANCE ASSET GROUP HOLDINGS LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOKIA US HOLDINGS INC.;REEL/FRAME:058363/0723 Effective date: 20211129 |
|
AS | Assignment |
Owner name: RPX CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PROVENANCE ASSET GROUP LLC;REEL/FRAME:059352/0001 Effective date: 20211129 |