| Patent application number | Description | Published |
|---|
| 20080225741 | Monitor for Multi-Protocol Label Switching (MPLS) Networks - In one embodiment, a method includes receiving label data that indicates all interface labels that belong to each path ID of multiple path IDs associated with corresponding multiple paths between provider edge nodes in a Multi-Protocol Label Switching (MPLS) network. Each interface label is associated with a network interface on a node in the MPLS network. Based on the label data, an untested list that holds data that indicates all unique interface labels is generated. A tested interface selected from the untested list is scheduled for testing. After scheduling, the interface label of the tested interface is removed from the untested list. It is determined whether the untested list still includes data for at least one interface label. If not, then a test of the MPLS network is completed without testing every path end to end, thus conserving network resources. | 09-18-2008 |
| 20110019569 | MONITOR FOR MULTI-PROTOCOL LABEL SWITCHING (MPLS) NETWORKS - In one embodiment, a method includes receiving label data that indicates all interface labels that belong to each path ID of multiple path IDs associated with corresponding multiple paths between provider edge nodes in a Multi-Protocol Label Switching (MPLS) network. Each interface label is associated with a network interface on a node in the MPLS network. Based on the label data, an untested list that holds data that indicates all unique interface labels is generated. A tested interface selected from the untested list is scheduled for testing. After scheduling, the interface label of the tested interface is removed from the untested list. It is determined whether the untested list still includes data for at least one interface label. If not, then a test of the MPLS network is completed without testing every path end to end, thus conserving network resources. | 01-27-2011 |
| 20110268289 | GROUND LOOP NOISE REJECTION FOR A HEADSET SUBSYSTEM - For headphone subsystems that employ common ground switches for speaker outputs (for example), there can be a significant issue with cross-talk and ground noise. Here, configurations for an amplifier and switch network are provided, which generally cancel noise from the “ground switch,” so as to provide an improvement over conventional configurations with little overhead. Additionally, the cross-talk for these configurations are not generally dependent on the “ground switch” or speaker impedance. | 11-03-2011 |
| Patent application number | Description | Published |
|---|
| 20100085419 | Systems and Methods for Selecting Videoconferencing Endpoints for Display in a Composite Video Image - In some embodiments, a videoconferencing endpoint may be an MCU (Multipoint Control Unit) or may include embedded MCU functionality. In various embodiments, the endpoint may thus conduct a videoconference by receiving/compositing video and audio from multiple videoconference endpoints. The endpoint may select a subset of endpoints and form a composite video image from the subset of the videoconference endpoints to send to the other videoconference endpoints. In some embodiments, the subset of endpoints that are selected for compositing into the composite video image may be selected according to criteria such as the last N talking participants. In some embodiments, the master endpoint may request the non-talker endpoints to stop sending video to help conserve the resources on the master endpoint. In some embodiments, the master endpoint may ignore video from endpoints that are not being displayed. | 04-08-2010 |
| 20100225736 | Virtual Distributed Multipoint Control Unit - A virtual distributed multipoint control unit in a videoconference may be implemented using a master endpoint, one or more facilitator endpoints, and one or more leaf endpoints. The facilitator endpoint(s) may receive video and/or audio from the leaf endpoints (which may provide/receive videoconference audio and video to one or more local participants). The master endpoint may receive video and/or audio from one or more facilitator endpoints (which may include cumulative video stream from multiple leaf endpoints) and/or directly from one or more leaf endpoints. The master endpoint may arrange received video and/or audio and provide cumulative video and/or audio streams to the leaf endpoints (e.g., directly and/or through the facilitator endpoints). The virtual distributed multipoint control unit may support a conference with more leaf endpoints than the master endpoint has input ports and/or decoders. | 09-09-2010 |
| 20100332598 | Routing Videoconference Signals Based on Network Configurations - Performing a videoconference based on network locality. The method may determine if a first endpoint and a second endpoint is within a same network, e.g., based on the address of the first and second endpoints. The videoconference may be established or performed based on the determination. For example, an external communication server may be used if the second endpoint is not within the same network as the first endpoint. However, the external communication server may be bypassed if the second endpoint is within the same network as the first endpoint. | 12-30-2010 |
| 20110074910 | Supporting Multiple Videoconferencing Streams in a Videoconference - Supporting a plurality of videoconferencing streams in a videoconference. The method may include receiving the plurality of videoconferencing streams and may include decoding a first videoconferencing stream of the plurality of videoconferencing streams. The method may also include selecting, for decoding, a second videoconferencing stream of the plurality of videoconferencing streams. The second videoconferencing stream may not be the first videoconferencing stream. The method may further include decoding, in response to said selecting, the second videoconferencing stream of the plurality of videoconferencing streams. | 03-31-2011 |
| 20110074913 | Videoconferencing Using a Precoded Bitstream - Sharing computer video in a videoconference. The method may include acquiring video on a computer. The method may also include coding the acquired video on the computer. Transmitting the coded video from the computer to a videoconferencing unit may also be included in the method. Also, the method may include packaging the transmitted video coded on the videoconferencing unit. Furthermore, the method may include transmitting the packaged video to a videoconferencing destination. | 03-31-2011 |
| 20110102540 | Filtering Auxiliary Audio from Vocal Audio in a Conference - Filtering auxiliary audio from vocal audio in a conference. Audio may be received during a conference. The audio may include vocal audio from a first participant as well as auxiliary audio that is not vocal audio from the first participant. The auxiliary audio may result from use of a computer input device at the location. The audio may be filtered to remove the auxiliary audio from the audio. The filtered audio may be provided, e.g., over a network to other participant locations of the conference. | 05-05-2011 |
| 20110261142 | Providing Separate Video and Presentation Streams to a Recording Server - A videoconference may be initiated between a plurality of endpoints. At least one of the endpoints may be coupled to a recording server, which may be configured to record the videoconference. A configuration may be selected (e.g., automatically or manually) for performing the recording. The endpoint (e.g., acting as an MCU) may transmit information to endpoints and may transmit recording information to the recording server. The recording information may be different from the videoconference information. For example, it may be in a “streaming friendly” format, at a different bit rate, encoded differently, have different inputs, etc. The manner in which the videoconference is stored and/or recorded may be based on the selected configuration. Clients may be configured to receive and display the videoconference from the recording server and may be configured to change the provided layout to different layouts, e.g., based on user input. | 10-27-2011 |
| 20110261145 | Determining Buffer Size Based on Forward Error Correction Rate - Determining a buffer size in a videoconference. In some embodiments, one or more of various different error correction methods may be used in a videoconference. For example, forward error correction (FEC) may be used and/or retransmission of lost packets (ReTxLP) may be used, e.g., based on a packet loss threshold. Where FEC is used, a buffer size of a receiving videoconferencing device may be determined based on the FEC rate. Where ReTxLP is used, a buffer size of the receiving videoconferencing device may be determined based on a retransmission latency. | 10-27-2011 |
| 20110261146 | Determining Buffer Size Based on Retransmission Latency - Determining a buffer size in a videoconference. In some embodiments, one or more of various different error correction methods may be used in a videoconference. For example, forward error correction (FEC) may be used and/or retransmission of lost packets (ReTxLP) may be used, e.g., based on a packet loss threshold. Where FEC is used, a buffer size of a receiving videoconferencing device may be determined based on the FEC rate. Where ReTxLP is used, a buffer size of the receiving videoconferencing device may be determined based on a retransmission latency. | 10-27-2011 |
| 20110261147 | Recording a Videoconference Using a Recording Server - A videoconference may be initiated between a plurality of endpoints. At least one of the endpoints may be coupled to a recording server, which may be configured to record the videoconference. A configuration may be selected (e.g., automatically or manually) for performing the recording. The endpoint (e.g., acting as an MCU) may transmit information to endpoints and may transmit recording information to the recording server. The recording information may be different from the videoconference information. For example, it may be in a “streaming friendly” format, at a different bit rate, encoded differently, have different inputs, etc. The manner in which the videoconference is stored and/or recorded may be based on the selected configuration. Clients may be configured to receive and display the videoconference from the recording server and may be configured to change the provided layout to different layouts, e.g., based on user input. | 10-27-2011 |
| 20110261148 | Recording a Videoconference Based on Recording Configurations - A videoconference may be initiated between a plurality of endpoints. At least one of the endpoints may be coupled to a recording server, which may be configured to record the videoconference. A configuration may be selected (e.g., automatically or manually) for performing the recording. The endpoint (e.g., acting as an MCU) may transmit information to endpoints and may transmit recording information to the recording server. The recording information may be different from the videoconference information. For example, it may be in a “streaming friendly” format, at a different bit rate, encoded differently, have different inputs, etc. The manner in which the videoconference is stored and/or recorded may be based on the selected configuration. Clients may be configured to receive and display the videoconference from the recording server and may be configured to change the provided layout to different layouts, e.g., based on user input. | 10-27-2011 |
| 20110261149 | Initiating Recording of a Videoconference via a Single User Interaction - A videoconference may be initiated between a plurality of endpoints. At least one of the endpoints may be coupled to a recording server, which may be configured to record the videoconference. A configuration may be selected (e.g., automatically or manually) for performing the recording. The endpoint (e.g., acting as an MCU) may transmit information to endpoints and may transmit recording information to the recording server. The recording information may be different from the videoconference information. For example, it may be in a “streaming friendly” format, at a different bit rate, encoded differently, have different inputs, etc. The manner in which the videoconference is stored and/or recorded may be based on the selected configuration. Clients may be configured to receive and display the videoconference from the recording server and may be configured to change the provided layout to different layouts, e.g., based on user input. | 10-27-2011 |
| 20110261150 | Selective Audio Combination for a Conference - Selective audio combination for a conference. The conference may be initiated between a plurality of participants at respective participant locations. The conference may be performed using a plurality of conferencing endpoints at each of the participant locations. Audio may be received from each of the plurality of conferencing endpoints. Audio level information may also be received from each of the plurality of conferencing endpoints. The audio may be combined from a plural subset of the plurality of conferencing endpoints to produce conference audio. The plural subset is less than all of the plurality of conferencing endpoints. The audio may be combined based on the audio level information. The conference audio may be provided to the plurality of conferencing endpoints. | 10-27-2011 |
| 20110279631 | Automatically Customizing a Conferencing System Based on Proximity of a Participant - Customizing a conferencing system based on proximity of a participant. A first participant may be detected as being proximate to a first conferencing system. For example, the first participant may provide user input to check in to the first conferencing system. Alternatively, the conferencing system may automatically detect the first participant (e.g., by automatically detecting a personal device of the first participant). In response to detecting the proximate participant, the first conferencing system may be automatically customized for the participant. | 11-17-2011 |
| Patent application number | Description | Published |
|---|
| 20080275874 | Supplier Deduplication Engine - Disclosed herein is a method of grouping similar supplier names together in a database. The syntactical errors in the supplier names are corrected. The supplier names are grouped after correcting the syntactical errors. The abbreviations in the supplier names are captured. The ordering, pronunciation and stemming errors in the supplier names are corrected. A matching algorithm that matches and compares two supplier names is applied that comprises the steps of grouping supplier names based on first set of characters in the supplier names and calculating a matching score between the two supplier using Levenshtein distance between the two supplier names, along with the supplier names' sound codes obtained from a modified metaphone algorithm, length of each word, position of matching and mismatching characters, and stem of words in the supplier names. The matching scores are compared with set thresholds in order to further group the supplier names into clusters. | 11-06-2008 |
| 20080306788 | Spen Data Clustering Engine With Outlier Detection - Disclosed herein is a computer implemented method and system for grouping spend items in a list of said spend items, and for detecting outliers. The spend items entered into the spend database are phonetically sorted and grouped into second level clusters by the spend data clustering engine. In the first level of clustering, first level clusters are created by matching the spend items using generated word tokens and sorted sound codes. The unique spend items, in the list generated after first level clustering, are further matched to create second level clusters. The first level clusters are updated based on the second level of clustering. In order to determine discrepancies in clustering and spend, statistically deviating outliers are detected in each second level cluster. This engine provides clustering at configurable levels of accuracy. The engine's specific combination of word token and sound code matching provides accurate results for spend items. | 12-11-2008 |
| 20100125596 | Fuzzy Search Using Progressive Relaxation Of Search Terms - Disclosed herein is a computer implemented method and system that progressively relaxes search terms provided by a user. Data of predefined types is stored in a database. The data is obtained by uniquely modifying data previously stored in the database, based on the predefined types. Search terms of predefined types are accepted from the user. The search terms are compared with the stored data to find exact matches, if length of the search terms exceeds a predefined value. On not finding exact matches, the accepted search terms are modified uniquely based on the predefined types to structure first alternative queries. The first alternative queries are compared with the stored data to find exact matches. On not finding exact matches, the first alternative queries are modified based on the predefined types to structure second alternative queries. The second alternative queries are compared with the stored data to find approximate matches. | 05-20-2010 |
