WO2000077687A1 - System and method for browser-based multimedia collaboration reporting - Google Patents
System and method for browser-based multimedia collaboration reporting Download PDFInfo
- Publication number
- WO2000077687A1 WO2000077687A1 PCT/US2000/015990 US0015990W WO0077687A1 WO 2000077687 A1 WO2000077687 A1 WO 2000077687A1 US 0015990 W US0015990 W US 0015990W WO 0077687 A1 WO0077687 A1 WO 0077687A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- call
- database
- information
- name
- multimedia collaboration
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
- H04L65/403—Arrangements for multi-party communication, e.g. for conferences
- H04L65/4046—Arrangements for multi-party communication, e.g. for conferences with distributed floor control
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
- H04L12/1831—Tracking arrangements for later retrieval, e.g. recording contents, participants activities or behavior, network status
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
Definitions
- the present invention relates to multimedia collaboration systems, and in particular to a multimedia collaboration event and status reporting system.
- Multimedia collaboration systems facilitate the exchange of audio, video, text, graphics, application commands and/or other types of information between users in real, near-real, or non-real time communication.
- Interpersonal communication involves a large number of subtle and complex visual cues, such as eye contact and body language, which provide additional information beyond spoken words and explicit gestures. These cues are, for the most part, processed subconsciously by the participants and often control the course of a conversation.
- Multimedia collaboration systems advantageously allow users to detect these cues and thereby enhance the communication between users.
- audio and video capture and processing capabilities have been integrated into desktop and portable personal computers and workstations. These capabilities have been used primarily in desktop multimedia authoring systems for producing CD-ROM and DVD-ROM based works. While such systems are capable of processing, combining and recording audio, video and data locally, i.e. at the desktop, they do not adequately support networked collaborative environments, principally due to the substantial bandwidth requirements for realtime transmission of high-quality, digitized audio and full-motion video which preclude conventional local area networks (LANs) from supporting more than a few workstations or personal computers. These systems do not adequately address the problems inherent in a practical implementation of a scalable collaboration system.
- LANs local area networks
- the present invention provides a scalable, evolvable, flexible, and architecturally accommodating system and method for a wide range of potential reporting functions of value in multimedia collaboration systems or other complex networked systems.
- the system and method herein are particularly advantageous in that they can be applied to a wide variety of systems of arbitrary levels of scale and decentralization and provide a wide range of information on usage, operations, costs, and failures in a wide variety of standard or custom report or query formats servicing the wide ranging needs of usage monitoring, planning, billing and accounting, maintenance, diagnostics, reconfiguration study and design.
- a multimedia collaboration reporting system for use in at least one underlying multimedia collaboration system network.
- the system includes an event monitoring module for monitoring any of internal network system events, external network system events and service events, a database module for recording the monitored events and a reporting module for receiving query parameter information and for generating a report in accordance with the query parameter information.
- the system architecture is such that any of the event monitoring module, the database module and the reporting module may be centralized to the underlying multimedia collaboration system network.
- any of the event monitoring module, the database module and the reporting module are decentralized from the underlying multimedia collaboration system network.
- the decentralization of any of the modules may result in a system architecture that reflects an architecture of the underlying multimedia collaboration system network.
- the database may comprise a plurality of localized databases, each configured to store monitored event information from a predetermined multimedia collaboration system network and a centralized database configured to centrally maintain the stored information from each of the plurality of localized databases.
- the database may comprise only a centrally located database configured to maintain the monitored event information.
- the reporting module is configured to generate either standard or customizable reports about the multimedia collaboration system network in response to database query parameter information and may include a web-based interface providing for web-based query and response interactivity such that a database query can be formulated and provided via the Internet.
- a multimedia collaboration system for conducting a conference among a plurality of participants.
- the system includes a multimedia collaboration system network having a plurality of workstations each having a monitor for displaying visual images and A/V capture and reproduction capabilities for capturing and reproducing video images and spoken audio of the participants, a data network providing a data path along which data can be shared among the plurality of the workstations a data conference manager for managing the sharing of data between the plurality of workstations.
- the system includes an independent reporting system connected with the multimedia collaboration system network and configured to provide reporting analysis of the multimedia collaboration system network.
- the independent reporting system includes a network control system configured to monitor any of internal, external or service event information affecting the multimedia collaboration system network, a database configured to store the monitored event information, a database query system configured to format a database query according to query parameter information and to query the database in accordance with the database query parameter information and a report generation system configured to generate an analysis report from the monitored event information stored in the database in accordance with the database query parameter information.
- a method for generating reports identifying multimedia collaboration system events includes monitoring any of internal network system events, external network system events and service events and recording the events to a database, querying the database with a set of query parameter information to generate an analysis report and generating the analysis report in accordance with the query parameter information.
- a reporting system including a network control system configured to monitor any of internal, external or service event information of a multimedia collaboration system network, a database configured to store the monitored event information, a database query system configured to format a database query according to query parameter information and to query the database in accordance with the database query parameter information and a report generation system configured to generate an analysis report from the monitored event information stored in the database in accordance with the database query parameter information.
- Fig. 1 is a block diagram of an exemplary multimedia collaboration system
- Fig. 2 is an illustration showing an exemplary networked organization of multimedia collaboration systems
- Fig. 3 illustrates some example general high-level call events that can be captured from within multimedia network environments
- Fig. 4 is a block diagram showing an exemplary implementation for a reporting environment in a multimedia network environment, such as that shown in Fig. 1;
- FIGs. 5A-C are respective block diagrams illustrating exemplary implementations for handling the inherent decentralization of reporting environments in multimedia network environments in accordance with the invention
- Fig. 6 is a block diagram illustrating an example of the operational interactions between various hardware, software, and database component in accordance with an embodiment of the present invention
- Figs. 7A and 7B are respective exemplary database structures showing record and field definitions for use in event logging in accordance with the invention.
- Fig. 8 depicts a general connection environment useful for defining various call types and database fields that are associated with records for such call types;
- Figs. 9A1-9C2 illustrate alternatives and evolutions of user interface implementation environments that can be utilized by the reporting system in accordance with the present invention;
- Fig. 10 is an example of a user interface for importing database records to the multimedia collaboration system in accordance with the invention.
- Fig. 11 is an example of a user interface for deleting database records from the multimedia collaboration system in accordance with the invention.
- Fig. 12 is an example of a menu of report choices selectable by a user for generating standard reports from the multimedia collaboration system in accordance with the invention
- Fig. 13A is an example of a set-up interface for determining report generation parameters for generating a calls between users report in accordance with the invention
- Fig. 13B depicts an exemplary report of calls among all or specified users in accordance with a set of reporting parameters established in the set-up interface of Fig. 13 A according to the invention
- Fig. 14A is an example of a set-up interface for determining report generation parameters for generating a user call detail report in accordance with the invention
- Fig. 14B depicts an exemplary report of user calls in accordance with a set of reporting parameters established in the set-up interface of Fig. 14A according to the invention
- Fig. 15A is an example of a set-up interface for determining report generation parameters for generating a number of calls completed by user report in accordance with the invention
- Fig. 15B depicts an exemplary report of the number of calls completed by a user in accordance with a set of reporting parameters established in the set-up interface of Fig. 15A according to the invention
- Fig. 16A is an example of a set-up interface for determining report generation parameters for generating a number of calls completed by time period report in accordance with the invention
- Fig. 16B depicts an exemplary report of the number of calls completed by time period in accordance with a set of reporting parameters established in the set-up interface of Fig. 16A according to the invention
- Fig. 17A is an example of a set-up interface for determining report generation parameters for generating a call duration report in accordance with the invention
- Figs. 17B-17D depict respective exemplary reports of call duration in accordance with a set of reporting parameters established in the set-up interface of Fig. 17A according to the invention
- Fig. 18A is an example of a user call total by time period report in accordance with a set of established reporting parameters according to the invention
- Fig. 18B is an example of a network availability by number of calls report in accordance with a set of established reporting parameters according to the invention
- Fig. 18C is an example of a network availability by percentages of calls report in accordance with a set of established reporting parameters according to the invention
- Fig. 19A is an example of a set-up interface for determining report generation parameters for generating a total device usage by number of calls report in accordance with the invention
- Fig. 19B is an example of a device usage by number of calls report in accordance with a set of reporting parameters established by the set-up interface of Fig. 19A according to the invention
- Fig. 20A is an example of a set-up interface for determining report generation parameters for generating a total device usage by duration report in accordance with the invention
- Fig. 20B depicts an exemplary device usage by duration report in accordance with a set of reporting parameters established by the set-up interface of Fig. 20A according to the invention
- Fig. 21 A is an example of a set-up interface for determining report generation parameters for generating a total device usage by time period report in accordance with the invention
- Fig. 21B depicts an exemplary total device usage by time period report in accordance with a set of reporting parameters established by the set-up interface of Fig. 21 A according to the invention
- Fig. 22A depicts an exemplary conference center usage by numbers of uses report according to the invention
- Fig. 22B depicts an exemplary conference center usage by cumulative time used report according to the invention
- Fig. 22C depicts an exemplary conference center busy by percentage of attempted uses report according to the invention.
- Fig. 22D depicts an exemplary conference call availability report according to the invention.
- Fig. 22E depicts an exemplary trunk busy report according to the invention.
- Fig. 23 is an example of a menu from which a user may select a variety of user-defined custom reports in accordance with the invention
- Fig. 24 is an example of a custom report interface for saving custom reports in accordance with the invention.
- Fig. 25 is an example of a custom report save notification interface for indicating the success or failure of a saved report request in accordance with the invention.
- the present invention provides a scalable, evolvable, flexible, and architecturally accommodating system and method for a wide range of potential reporting functions of value in multimedia collaboration systems or other complex networked systems.
- the system and method herein are particularly advantageous in that they can be applied to a wide variety of systems of arbitrary levels of scale and decentralization and provide a wide range of information on usage, operations, costs, and failures in a wide variety of standard or custom report or query formats servicing the wide ranging needs of usage monitoring, planning, billing and accounting, maintenance, diagnostics, reconfiguration study and design.
- An aspect of the present system and method is to provide a powerful framework for arbitrary degrees of standard and customized report generation and access, including web-based access, for networked systems spanning a wide range of network configurations, architectural variations, evolving technologies, evolving services, and entities attached to the networks.
- Fig. 1 is a block diagram illustrating a conventional video-oriented multimedia collaboration system 99 such as is shown and described in U.S. Patent No. 5,617,539, entitled “Multimedia Collaboration System with Separate Data Network and A/V Network Controlled by Information Transmitting on the Data Network,” and issued to Ludwig et al., on April 1, 1997, which is inco ⁇ orated herein by reference. While a video-oriented multimedia collaboration system 99 is shown in Fig. 1 , it should be noted that the present invention is applicable to any multimedia collaboration system or other networked system and the above Figure is merely exemplary and is not intended to be limiting.
- the multimedia collaboration system 99 includes a number of component entities, including a plurality of user workstations 40, a multimedia local area network (MLAN) 10, a conference bridge or center 36 (a hardware device for audibly and visually connecting multiple parties to a conference), an A V storage server 100, a LAN 20 coupled to a gateway 25 and a first wide area network (WAN) 29, and an A V codec 38 coupled to a second WAN 39.
- MLAN multimedia local area network
- AVNM A/V network manage r
- the user workstations 40 are connected with the system 99 via the A/V switch 32 resident in the MLAN 10.
- the A V switch 32 also couples the MLAN 10 to the A V storage server 100, as well as coupling the second WAN 39 to the MLAN 10 via codec 38 (an integrated circuit for performing data conversion).
- the first WAN 29 is connected to the LAN 20 via the gateway 25.
- the LAN 20 is in communication with the AVNM 34 thereby affording network management to the LAN 20.
- the LAN 20 also functions to couple additional ente ⁇ rise computers 60 and e-mail/voice-mail application functionality 50 to the system entities connected therewith.
- the A/V storage server 100 may be coupled to or otherwise in communication with the network, such as via the switch 32. Such embodiments are described in Patent Cooperation Treaty Application Numbers PCT US99/01789 and PCT/US98/23596 and are hereby inco ⁇ orated herein by reference.
- the A/V storage server 100 includes an A/V storage manager 160 for coordinating requests for the storing and playing back of video data and the like, and one or more A/V storage cells 120 configured to store video data and other supplemental information. These cells 120 may be either directly connected to the storage manager 160 (represented as reference numeral 112) or connected with the storage manager 160 via a data LAN 110 that also serves to couple external systems to the network.
- the A/V switch 32 facilitates selective coupling between user workstations 40, the LAN 20, and the codec 38.
- the A/V switch 32 may also facilitate direct coupling to one or more other multimedia collaboration systems 99. Therefore, workstation users can communicate with each other via multimedia conferencing, such as is described in U.S. Patent No. 5,617,539. Other similar network configurations are also possible and provided for by the invention.
- the AVNM 34 In operation, the AVNM 34 generates event or reporting records in response to a variety of system events. Exemplary types of events for which reporting records are generated, and information included in such reporting records, will be described in detail herein. The following exemplary events that are monitored by the system are largely oriented towards internal and external networks, but in general may also apply to connected service entities. Such events may include server startup and shutdown events. For example, each startup and shutdown record may include startup time, shutdown time, any applicable error code and any associated error string as well as other additional information.
- each user login and logout record may include a user ID, a login or logout time as appropriate, and possibly client platform, client type, client operating system version, client collaboration system software version, and other supplemental information. Additionally, aliases are provided for so that a user can associate a different login ID when desired.
- each call record may include a caller or calling party ID, a call session ID, a caller terminal port ID, a caller mode description, a caller codec ID, a caller trunk port number, a callee ID, a callee terminal port ID, a callee mode description, a callee terminal ID, a callee codec ID, a callee trunk port ID, a starting time stamp, and a completion time stamp.
- each call error record may include information detailing call failures for reasons such as trunk unavailability, gateway failures, etc., and typically may include a session and or call ID and timestamp information.
- each service record may include details specifying service resources and typically may include a session ID and timestamp information.
- Service error events may also be monitored by the system.
- each service error record may include details specifying service resource problems, operational errors and typically may include a session ID and timestamp information.
- call records affiliated with multi-party calls and multi-point broadcasts may be associated through the utilization of a common session ID.
- service records for sessions and events pertaining to services outside the scope of the network itself, such as video storage services may also be associated with corresponding calls and call events through the use of a common session ID.
- a session may be defined as a time interval that begins when system or conference center resources are allocated for a new call that is not associated with a call currently in progress. Accordingly, the session is defined to end when the resources that are allocated in association with the call are freed for others to use. It should be noted that the addition of new callers to an existing two-party call to form a multi-party call falls within the context of an already-existing session.
- the AVNM 34 creates a new session ID each time resources are allocated for a new call that is not associated with a call currently in progress. For example, in an embodiment of the invention, the AVNM 34 transfers or propagates session IDs to other AVNMs 34 and remote clients 40, 45. Thus, when a new party is added to an existing call, the AVNM 34 associated with the calling party transfers the existing session ID to the AVNM 34 associated with the callee.
- the session ID stored within each call record associates multi-step calls and/or calls made on different collaboration systems, such as when a third party is added to a two-party call.
- Fig. 2 is an illustration of an exemplary networked organization 199 of multimedia collaboration systems 99, such as that shown in Fig. 1.
- reporting functions can be utilized for usage monitoring, planning, billing and accounting, maintenance, diagnostics, reconfiguration study and design, as well for other diagnostic and application-specific pu ⁇ oses.
- the present invention provides a framework for arbitrary degrees of standard and customized report generation and access. These reports can be generated by gathering information from throughout the network 199 and from the entities connected to it. As such, the reporting system framework of the invention can accommodate the wide range of network configurations, architectural variations, evolving technologies, evolving services, and entities attached to the networks 199.
- the reporting function of the present invention can be treated as a general form of service supported and provided by a server.
- an implementation of the reporting server 210 may be centralized or decentralized and take on a variety of forms that will be explained in detail herein.
- a report server 210 working in conjunction with a report database 200 may be provided for managing the reporting functions of these systems.
- the report server 210 and the report database 200 may be added to an individual multimedia communications system 99 or also to a networked organization 199 of individual multimedia communications systems 99 so as to provide reporting services to administrative computers or user workstations 40 within one or more multimedia collaboration systems 99.
- the reporting server 210 may be coupled to one or more multimedia collaboration systems 99 directly, and/or via an intranet or even the
- reporting server 210 and a reporting database 200 may be implemented on a single computer system or in any number of decentralized fashions without departing from the invention.
- Fig. 3 illustrates some examples of high-level call events that can be captured from within multimedia network environments 199, 99 and which may be monitored by the multimedia collaboration system environments 199, 99 so that diagnostic and other informative reports may be generated.
- a two-party point-to-point WAN 281 call between two users 262, 272 each on separate local (or "internal") networks 261, 271 that are connected by the WAN 281 by means of gateways 263, 273 is illustrated in Fig. 3.
- network control entities such as AVNMs 260, 270 govern the exchange of exemplary system control messages.
- control messages may include connection request messages, remote network manager server requests, callee requests, acknowledgement messages, and connection establishment messages.
- control messages may include connection request messages, remote network manager server requests, callee requests, acknowledgement messages, and connection establishment messages.
- other control messages may be provided and the above are merely exemplary.
- a report server 210 can be provided (such as shown in Fig. 2) to retrieve the information from the multiple entities. Additional system services may be added to the architecture shown in Fig. 3.
- such additional services may include network-oriented services, such as multipoint conferencing or event video broadcast, or be provided by attached entities such networked video storage servers, such as that described in Patent Cooperation Treaty Application Numbers PCT/US99/01789 and PCT/US98/23596.
- network-oriented services such as multipoint conferencing or event video broadcast
- attached entities such networked video storage servers, such as that described in Patent Cooperation Treaty Application Numbers PCT/US99/01789 and PCT/US98/23596.
- Fig. 4 is a block diagram showing an exemplary implementation for a reporting environment in a multimedia network environment, such as that shown in Fig. 1.
- multimedia network environments include not only a "focus" or "internal” network 201 but also one or more external networks 202.
- These external networks 202 may include networks similar to the internal network 201 or they may include networks which are completely dissimilar (such as a public WAN).
- the multiple networks 201, 202 are typically used directly or indirectly to provide various services to users.
- the services (such as transport) may be provided directly by the network(s), while in other cases the services may be provided in whole or in part by external service-providing entities 203 (such as stand-alone video-on-demand systems).
- each of the networks and service entities 201, 202, 203 provides some information either directly (such as event logs) or indirectly (such as WAN call progress signals) which can be accessed as used for reporting purposes.
- This information can be provided in real-time and/or through later bulk information transfers (such as a monthly WAN report file).
- the information is then formatted by a system 204 configured to format the data into a format usable within the reporting system.
- the formatting step(s) may be performed in a centralized or a decentralized fashion.
- the resultant information formatting may be automatic, manual, or a combination of the two.
- the formatted information may then be loaded into a database 200.
- the database 200 may be centralized or decentralized, and the information loading may be automatic, manual, or a combination of the two.
- the information in the database 200 can then be queried, processed and reported in a number of ways.
- a standard report filter/formatter 206 may be provided.
- a standard report filter/formatter 206 refers to one or more fixed, conditional, or parameterized report templates 207.
- a report template 207 (and any conditional or parameterized choices therein) may be selected according to the report or reports desired by a user of the reporting system.
- report request events 220 may be driven by report request events 220. For example, these requests may be generated by users directly or automatically as part of a script and/or a calendar-driven automated procedure.
- queries can be made from the standard report filter/formatter 206 to the database 200.
- the data from the database 200 can be placed directly into fields in the template or some equivalent implementation of this action.
- the calculations may include billing operations, which involve additional information such as billing rates, billing algorithms, etc., which in turn may be part of the standard report filter/formatter 206, may be provided by the calculation module 208, by a separate repository entity 240, or explicitly provided as part of the report request event 220. In the case where a separate repository entity 240 may provide the calculations, the separate repository entity 240 may communicate directly with a calculation module 208 and/or directly with the standard report filter/formatter 206.
- the standard report filter/formatter 206 may use the queried, calculated, and conditionally-tested information to create one or more reports 209a -209n. It should be noted that a single report request 220 and/or single report template 207 could result in the generation of more than one report 209. In accordance with the invention, the reports generated in this manner may be presented to a user via a user interface (which will be described in detail herein) and/or printed (i.e., for direct human consumption) or in the form of machine-readable files (that can be subsequently processed or stored in the database 200). Further, in accordance with the invention, to the extent that aspects of the standard reports can be enabled/disabled by any parameters provided by the report requests 220, the standard report filter/formatter 206 can also be used to customize reports to various degrees.
- flexible general templates 212 may be submitted to a general filter/formatter 216.
- These templates 212 are often more parameterized and/or conditionally structured than the standard report templates 207 but need not be so structured.
- the general templates 212 may consist of strings of a combination of query, conditional, calculation, and formatting instructions.
- the general filter/formatter 216 could also be provided with additional support entities such as calculation module 208, separate repository entities 240, etc., without departing from the invention.
- the general filter/formatter 216 could also be further controlled by report request events 220 akin to those utilized by the standard report filter/formatter 206 and described above.
- an SQL interface module 226 may be provided for accepting and processing general SQL queries 215 from an external system and for providing reports 216 to an external system. It should be noted that the SQL module 226 could also be provided with additional support entities such as calculation module 208, separate repository entities 240, etc., without departing from the invention.
- the standard report filter/formatter 206 may be integrated as may prove advantageous for an implementation. Therefore, in accordance with the invention, the reporting functionality of the system may be customizable depending on the needs of a user. It should be further understood that additional support entities and functions, such as calculation modules 208 or separate information processing algorithm repositories 240 may be shared across any combination of the standard report filter/formatter 206 function, the general filter/formatter 216 function, and/or the SQL interface module 226 function as may prove advantageous for an implementation without departing from the invention.
- FIGs. 5A-C are respective block diagrams illustrating exemplary implementations for handling the inherent decentralization of reporting environments in multimedia network environments in accordance with the invention.
- multimedia network environments include a number of decentralized entities acting as event sources (shown in Figs. 5A-C as reference numerals 282a - 282k ).
- Figs. 5A and 5B illustrate exemplary implementations in which each event source may be served directly or indirectly by individual "local" databases 285a - 285k. These databases may be geographically local, or may be individual for functional reasons.
- Fig. 5A-C are respective block diagrams illustrating exemplary implementations for handling the inherent decentralization of reporting environments in multimedia network environments in accordance with the invention.
- multimedia network environments include a number of decentralized entities acting as event sources (shown in Figs. 5A-C as reference numerals 282a - 282k ).
- Figs. 5A and 5B illustrate exemplary implementations in which each event source may be served directly or indirectly by
- the individual "local" databases 285a - 285k may pass on their updated information by pull or push models, polled or event driven, to a centralized database 295 which in turn may be queried by a query/filter/format module 286 that may be designed to work with the centralized database 295.
- the individual "local" databases 285a - 285k may be queried directly by a query/filter/format module 286 that may be designed to work with multiple databases 285a - 285k.
- each event source 282a - 282k may directly provide their updated information to a centralized database 295 which in turn may be queried by a query/filter/format functions 286 that may be designed to work with the centralized database 295 .
- query/filter/format functions 286 may be designed to work with the centralized database 295 .
- Fig. 6 is a block diagram illustrating an example of the operational interactions between various hardware, software, and database components in accordance with an embodiment of the present invention in which a web-based interface implementation is utilized.
- the AVNM 34 and or the A/V Conference Center Manager (ACCM) 35 may be configured to generate and write reporting or event records into a log file 510 that is managed by a database 200.
- the database 200 may be implemented using small-scale database products such as Microsoft Access, or in larger-scale applications or where decentralization dictates, other database technologies may be utilized without departing from the invention.
- a log file export unit 520 may be configured to retrieve these stored event records from the log file 510 under the direction of one or more objects instantiated from a log class file 530.
- the log class file 530 may be configured to write records into the database 200 and may perform some preprocessing and/or initial parsing upon event record data prior to performing a database write operation.
- the log class file 530 may also control or direct periodic import operations in conjunction with a configuration file (not shown), such that event records stored in the database 200 can be retrieved and the database 200 can be updated on a regular basis.
- the web-based interface implementation depicted in Fig. 6 includes a request class file 550 having an HTML page processing unit 560, a report display unit 570, and a custom report unit 580.
- the request class file 550 pro vides HTML page templates for performing database management operations, and for generating and saving a wide variety of reports.
- the page processing unit 560 performs database management and/or database query operations in response to user requests. For example, the page processing unit 560 may retrieve database information in response to a user request including a set of report parameters. As will be described in more detail herein, users accessing the reporting system may specify report parameters via a set-up interface.
- the page processing unit 560 may filter the results of the database query operation in accordance with one or more such report parameters.
- the report display unit 570 generates a report in accordance with the user- specified report parameters.
- the custom report unit 580 facilitates the saving of user-defined reports to the database 200. It should be noted that the present invention accommodates the creation of user groups. User groups are simply aggregates of real users, aliases and other user groups. Thus, when choosing query criteria, a user can select a combination of user groups, users and/or aliases to report against.
- Figs. 7 A and 7B are respective exemplary database structures (referred to generally as reference numerals 300a (Fig. 7A) and 300b (Fig. 7B)) showing record and field definitions for use in event logging in accordance with the invention. Certain fields in the database schema are composed of data types. Those skilled in the art will recognize that other types of record structures may be used without departing from the invention and that the structures shown in Figs. 7 A and 7B are merely exemplary.
- One such exemplary field type may include a Call ID character field that uniquely identifies a call record and any hop (i.e., tandem trunk connections through additional switches) records that are associated with that call record.
- Another example of a field type may be a URL field, a character string having a general URL format (i.e.. ⁇ protocol>:// ⁇ arguments>) describing a system connection (e.g., video) address.
- Other field type examples include a Caller field identifying a user at the end point of a call chain from which a call is initiated, a Callee field identifying a user at the end point of a call chain to whom a call is placed and a Caller/Callee Name field.
- the Caller/Callee Name field identifies a service name associated with each party involved in the call.
- this aspect could exclude connections placed to specialized entities such as multi-point conference bridges and externally connected servers (such as video storage servers). Calls involving such entities may advantageously use alternate naming conventions in the service name.
- the callee name may need to be extracted from the URL, such as in the case of calling H.320 addresses.
- Another field type example is a Callee vs. Received Call field. This field is utilized for managing multi-party calls.
- the callee designated in this field may not necessarily be the user that received the call.
- the user specified by the caller field is actually the user who received the call. For example, in call forwarding situations where party A calls party B and party A forwards the call to party C, the records for the forwarded call may indicate party C as the caller and party B as the callee.
- Fig. 8 depicts a general connection environment useful for defining various call types and database fields that are associated with records for such call types.
- Fig. 8 illustrates at least six functionally different types of supported calls in a multimedia environment.
- One such call type involves a direct call between User A 800 and User B 802 on the same switch AVNM1 804 (Call Type 1).
- Another call type involves a switched call between User A 800 on switch AVNM1 804a and User C 806 on a different switch AVNM2 804b through one or more trunks 808 (Call Type 2).
- a third call type involves a call from User A 800 to Outside Caller D 810 using a gateway on the same switch AVNM1 804a (Call Type 3).
- Another call type involves a call to User A 800 from Outside Caller D 810 using a gateway on the same switch AVNM1 804a (Call Type 4). Yet another call type involves a call from User A 800 to Outside Caller E 812 using a gateway on a different switch AVNM2 804b (Call Type 5). Finally, a sixth call type involves a call to User A 800 from Outside Caller E 812 using a gateway on a different switch AVNM2 804b (Call Type 6).
- call types can be extended to include other types of connections, such as broadcast and multiple service interconnection (as in conference recording of a multi-party call which in turn includes as one of its "participants” another video service such as video-on-demand or video-mail) as may be supported by the network without departing from the invention.
- connections such as broadcast and multiple service interconnection (as in conference recording of a multi-party call which in turn includes as one of its "participants” another video service such as video-on-demand or video-mail) as may be supported by the network without departing from the invention.
- Such call type classification schemes can advantageously be used to differentiate the structure call records in accordance with the invention. For example, the number of fields necessary to characterize a call of Type 1 are far fewer than that needed to characterize a call of Types 5 or 6. Some information may be recorded similarly for all call types. For example, in all cases a global unique ID is created for each call (such as by the originating AVNM).
- Some exemplary structural variations depending on call type may include a CALL record for maintaining Caller info, Callee info, End-reason information, trunk/gateway information, and next-hop information (if the AVNM is not a destination). If a call involves more than one AVNM, then non-originating AVNMs may log a HOP record to the database 200 that may include a global unique ID, trunk/gateway information and next-hop information (if the AVNM is not a destination).
- a CONFERENCE record may be logged to the database 200 that may include a Conference Session Unique ID, Conference name information, Start time information, End time information and an AVNM ID.
- a PARTICIPANT record may also be logged to the database 200 that may include a Conference Session ID, a Call ID, Slot number information and Reason information.
- the following represent examples of database entry tables that may be utilized by the system for organizing reporting information in accordance with the invention. Some database entry tables may include call tables and the hops involved in placing calls, multi-point conference bridges and the associated conference participants, arbitrary services, arbitrary servers, sessions and logins. Of course different structures, additional tables, and additional or alternate types of information may be gathered in a variety of ways as is understood by one skilled in the art without departing from the invention.
- the following table illustrates an example of a call table described above.
- the following table illustrates an example of an associated hop table described above.
- the following table illustrates an example of a multi-point conference bridge table described above.
- the following table illustrates an example of an associated conference participant table described above.
- the following table illustrates an example of an arbitrary services table described above.
- the following table illustrates an example of an arbitrary servers table as described above.
- the following table illustrates an example of a session table as described above.
- the following table illustrates an example of a login table described above.
- Appendix A to this specification lists a series of reporting and billing algorithms that may be utilized by the present invention.
- Appendix A to this specification lists a series of reporting and billing algorithms that may be utilized by the present invention.
- those skilled in the art will understand that other implementations of the appended algorithms, as well as additional algorithmic functions relating to information processing for reporting may be utilized without departing from the invention.
- the duration of a (two-party) call is the Call Record End Time minus the Call Record Accept Time.
- the duration of a conference call is the Conference Record End Time minus the Conference Record Start Time.
- the duration of a call into a Conference Center is calculated from the Participant record (i.e., the Participant Record End Time minus the Participant Record Accept Time).
- the handling of geographic time zones are provided by the system of the invention. For example, the use of globally implemented "absolute time" (Greenwich Mean Time), or the use of context-specific local time that may be an extension of GMT, may be provided to generate a desired report and to maintain information about the MCS.
- calls generally fall into three classes: LAN, WAN Dial, and WAN Dedicated.
- a call is classified as a LAN call when the call has no associated hop records and both the In Gateway Type and Out Gateway Type fields are NULL or when its Out Gateway Type field is UTP, its Out Gateway Class is Dedicated, and all its subsequent hop records have In Gateway Type and Out Gateway Type values that are NULL or UTP. If neither of these conditions are true, then the call is classified as a WAN call.
- WAN calls are further partitioned into Dedicated and Dial calls based on the contents of the In Gateway Class and Out Gateway Class fields in the Call and Hop records. If the value of either of these fields in the Call Record or in any Hop Record is DIAL, then the call is classified as a WAN Dial call. Otherwise the call is classified as a WAN Dedicated call.
- Callers and callees can be designated as actual users or they can be designated as services, meaning that they do not represent an actual user. This designation is determined by the Caller Service and Callee Service fields. Only “User” and “Outside User” are actual users. All other values indicate services. Services can be the originator of a call only if both the caller and callee of the call are services.
- the caller in a Call Record is designated as the Receiver of the call when the caller is an Actual User and the Received Call field is TRUE, the caller and callee are services and the Received Call field is TRUE or when the callee is a service.
- the callee in a Call Record is designated as the Receiver of the call when the Callee Class is User or Outside User and the Received Call field is FALSE, the caller and callee are services and the Received Call field is FALSE or when the Caller Name is neither User nor Outside User.
- the caller in a Call Record is designated as the Originator of the call when the callee is the Receiver.
- the callee in a Call Record is designated as the Originator of the call when the caller is the Receiver.
- Call Record and Hop Record completion status can be one of three possible values: not completed due to no allocated resources; not completed due to failure; and available for completion.
- Several situations result in a Call Record or Hop Record not being completed due to no allocated resources.
- a Call Record or Hop Record is not completed due to no allocated resources if Local Error Type is "Out” and Local Error is PVW_TRUNK_NO_REMOTE (-54), PVW_TRUNK_NOT_REACHABLE (-59), PVW_NO_TRUNK (-29), PVW_TRUNK_IN_USE (-55), PVW_TRUNK_GATEWAY_RESETTING (-73), PVW_TRUNK_DOWN (-53), PVW_TRUNK_ISDN_DOWN (-63), PVW_DEDICATED_LINES_ARE_DOWN (-109), PVW_SYNC_F AILED (-110) or if Local Error Type is "Switch" and Local Error is PVW_XBAR_B
- a Call Record or Hop Record is available for completion if Local Error Type is "In” or if Local Error Type is "Out” and Local Error is PVW_OK (0), PVW_REFUSED (-8) or PVW RTNG TIMEOUT (-47).
- a Call Record or Hop Record is not completed due to failure in all other cases. Call Record and Hop Record have busy status classifications of local, remote, or none.
- Call Record and Hop Record busy status is classified as local if Local Error Type is "Out” and Local Error is PVW_TRUNK_NOT_REACHABLE (-59), PVW_NO_TRUNK (-29), PWV TRUNK NJ SE (-55), PVW_TRUNK_GATEWAY_RESETTING (-73), PVW_TRUNK_DOWN (-53), PVW_TRUNK_ISDN_DOWN (-63), PVW_DEDICATED_LINES_ARE_DOWN (-109) or PVW_SYNC_F AILED (-110).
- Call Record and Hop Record busy status is classified as remote if Local Error Type is "Out” and Local Error is PVW_TRUNK_NO_REMOTE (-54). In any other case, the busy status is classified as none.
- GUI Graphical User Interface-
- web-based communication between a reporting server 210 and a set of user workstations 40 can be implemented or facilitated through the use of a conventional Java Servlet engine, conventional web server and web browser software, conventional database driver software, and data export/transfer software.
- GUIs often involve one or more user interface implementation environments.
- stand-alone custom interactive graphical displays were utilized by systems whose software operated directly in the native window system environment of the desktop computer. These implementations are still those of choice today for applications where performance, non-web usage, or architectural factors motivate or dictate this approach.
- the conventional approach has a number of liabilities including dependence on specific details of window systems, operating systems, and other platform aspects as well as administrative complications in versioning, maintenance, upgrading, etc.
- GUIs are increasingly implemented as interactive web-based displays accessed by and operating within the environment of a web-based browser. In these situations, the GUI application software operates within the browser environment and relies on the browser environment to interface in surrogate with the native window system environment of the specific platform.
- Figs. 9A1-9C2 illustrate alternatives of user interface implementation environments that can be utilized by the present invention.
- a dotted box 601 is used to denote the window system environment of the desktop computer.
- Figs. 9A1 and 9A2 show respective implementations of application GUIs 602, 603, 604 which operate within the window system environment 601.
- the user interface may be provided by a single comprehensive GUI 602.
- Fig. 9A2 illustrates an alternative case in which one GUI 603 may serve as a principle user interface and launch secondary feature-specific GUIs 604 as needed.
- Figs. 9B1 and 9B2 illustrate hybrid interface implementations which combine windows-based GUIs (reference numbers 622 (Fig. 9B1) and 632 (Fig. 9B2)) and web-based GUIs (reference numbers 625, 626 (Fig. 9B 1) and 635, 636 (Fig. 9B2)).
- the web-based application GUIs 626, 636 shown in Figs. 9B1 and 9B2 operate in the browser environment 625, 635, respectively.
- either the windows-based GUI 622 or the browser based GUI 635 may serve as a principle user interface and launch secondary feature specific GUIs as needed.
- Fig. 9C1 With the addition of a browser 605 to the window system environment 601, it is possible to include "web-based" application GUIs 606 which operate in the browser environment 605 as described above.
- the addition of web-based GUIs 606 permits a number of additional implementation options.
- the implementation depicted in Fig. 9A1 can be modified to utilize web-based GUIs 606 as shown in Fig. 9C1.
- window-system GUIs 645, 655 and web-based GUIs 646, 656 can be used in combination with each other.
- FIGS. 9A1 and 9A2 have been used exclusively in the past, while the implementation methods of Figs. 9C1 and 9C2 are seen as the way of the not-too-distant future. In the interim, combination methods involving arrangements such as depicted in Figs. 9B1 and 9B2 have value in that they deliver or are perceived to deliver higher degrees of performance and security.
- the present invention can be implemented using any of the interface methods depicted in Figs. 9A1-9C2, as well as in variations clear to those familiar with the art.
- Fig. 10 is an example of a browser-based data management interface 1000 for importing records into the database 200 in accordance with the invention.
- the data management interface 1000 may be configured to execute on a user workstation 40, and is responsive to user-specified input for controlling conditions (indicated as reference numeral 1001) determining how the report server 210 (shown in Fig. 2) updates its associated report database 200.
- Fig. 11 is another example of a browser-based data management interface 1100 for deleting records from the database 200 in accordance with the invention.
- the data management interface 1100 is responsive to, and permits execution of, user input that specifies conditions (indicated as reference numeral 1101) under which all or some reporting records may be deleted from the database 200.
- conditions indicated as reference numeral 1101
- only a system administrator or information-privileged user can provide valid input to the data management interfaces 1000 (Fig. 10) and 1100 (Fig. 11), respectively.
- other permission schemes and/or hierarchies may be provided without departing from the invention.
- Fig. 12 is an exemplary menu 1200 from which a user may select a variety of standard reports in accordance with the invention.
- reports such as calls between users, user call detail, number of calls completed by a user, call duration, total device usage by the number of calls, total device usage by duration, and total device usage by time period may be generated by the reporting system. Examples of these reports will be described in detail herein.
- Fig. 13A is an example of a set-up interface 1300 for determining report generation parameters for generating a calls between users report 1350 (shown in Fig. 13B).
- the set-up interface 1300 provides a user with descriptive report information 1301, and facilitates user selection of user groups 1302, time ranges 1303, sort order 1304, and report display format 1305.
- Fig. 13B depicts an exemplary report 1350 of calls among all or specified users.
- the report 1350 indicates an account of calls made between users for a given time period using a sort order that consists of sorting at a first level by user and at a second level by time.
- the report 1350 identifies a call originator, a LAN call recipient and/or recipients or a WAN call recipient or recipients, a starting time, and a duration.
- Fig. 14A is an example of a set-up interface 1400 for determining report generation parameters for generating a user call detail report 1450 (shown in Fig. 14B).
- the set-up interface 1400 provides a user with descriptive report information 1401 and facilitates user input for the selection of a user group 1402, a call type 1403, a time range 1404, a sort order 1405, and a report display format 1406.
- Fig. 14B depicts an exemplary user call detail report 1450, which indicates details of calls among a group of users for originating and receiving calls spanning a particular time period. For each call, the report 1450 identifies a call originator, a LAN call recipient or recipients or a WAN call recipient or recipients, a starting time, and a duration.
- Fig. 15A is an example of a set-up interface 1500 for determining report generation parameters for generating a number of calls completed by user report 1550 (shown in Fig. 15B).
- the setup interface 1500 provides a user with descriptive report information 1501, and facilitates user input of a user group 1502, a call type 1503, a time range 1504, a sort order 1505 , and a report display format 1506.
- Fig. 15B depicts an exemplary number of calls completed by user report 1550, which graphically indicates a number of LAN calls and/or WAN calls originated and/or received by a specified user or users and/or group or groups of users within a specified time interval.
- Fig. 16A is an example of a set-up interface 1600 for determining report generation parameters for generating a number of calls completed by time period report 1650 (shown in Fig. 16B).
- the set-up interface 1600 provides a user with descriptive report information 1601 and facilitates user selection of a user group 1602, a call typ e 1603, a time range 1604, a time period 1605, a sort order 1606 and a report display format 1607.
- Fig. 16B depicts an example of a number of calls completed by time period report 1650, which indicates a number of calls using an indicated type of network connection that were originated and/or received by a specified group of users during a specified time period.
- Fig. 16A is an example of a set-up interface 1600 for determining report generation parameters for generating a number of calls completed by time period report 1650 (shown in Fig. 16B).
- the set-up interface 1600 provides a user with descriptive report information 1601 and facilitates user selection of a user group 1602, a
- FIG. 17A is an example of a set-up interface 1700 for determining report generation parameters for generating a call duration report 1750 (shown in Fig. 17B).
- the set-up interface 1700 provides descriptive report information 1701 and facilitates user input of a user group 1702, a call type 1703, a time range 1704, a sort order 1705 and a report display format 1706.
- Figs. 17B-17D depict respective examples of call duration reports 1750, which depict cumulative call durations for LAN calls and/or WAN calls associated with one or more specified groups of users and a specified time interval.
- Fig. 18A is an example of a user call total by time period report 1800 that includes a bar chart representing the cumulative minutes of use for LAN calls, WAN calls made using a dial-up connection and/or WAN calls made using a dedicated connection during a specified time range broken down by month.
- Fig. 18B is an example of a network availability by number of calls report 1825 that includes a bar chart representing the results of calls using the specified networks during a specified time period.
- possible report indicators include available for completion, not completed due to unavailable resources, and/or not completed due to network or other system error.
- Fig. 18C is an example of a network availability by percentages of calls report 1850 that includes a bar chart representing the percentages, rather than numbers, of calls available for completion, not completed due to unavailable resources, and/or not completed due to error during a specified time period.
- Fig. 19A is an example of a set-up interface 1900 for determining report generation parameters for generating a total device usage by number of calls report 1950 (shown in Fig. 19B).
- the set-up interface 1900 provides descriptive report information 1901 and facilitates user specification of a device or devices 1902, a time range 1903, a sort order 1904 and a report display format 1905.
- Fig. 19B is an exemplary device usage by number of calls report 1950 that indicates a total number of inbound and/or outbound calls for a set of specified devices during a specified time interval.
- Fig. 20A is an example of a set-up interface 2000 for determining report generation parameters for generating a total device usage by duration report 2050 (shown in Fig. 20B).
- the interface 2000 provides descriptive report information 2001, and facilitates user specification of a set of devices 2002, a time period 2003, a sort order 2004 and a report display format 2005.
- Fig. 20B depicts an exemplary device usage by duration report 2050, which indicates a cumulative inbound and outbound use time for a specified set of devices during a specified time period.
- Figure 21 A is an example of a set-up interface 2100 for determining report generation parameters for generating a total device usage by time period report 2150 (shown in Fig. 21B).
- the set-up interface 2100 provides descriptive report information 2101, and facilitates user input to specify a device set 2102, a time range 2103, a time period 2104, a sort order 2105 and a report display format 2106.
- Fig. 21B depicts an exemplary total device usage by time period report 2150, indicating a cumulative inbound and outbound usage time for a specified set of devices during a specified time period.
- Figs. 22A-22D Examples of four additional reports that may be generated according to specified parameters as described above are shown in Figs. 22A-22D.
- Fig. 22A depicts an exemplary conference center usage by numbers of uses report 2200 that includes a bar chart representing the number of uses of conference centers in the specified MCSs.
- Fig. 22B depicts an exemplary conference center usage by cumulative time used report 2225 that includes a bar chart representing the cumulative time of use of conference centers in the specified MCSs during the specified time interval.
- Fig. 22C depicts an exemplary conference center busy by percentage of attempted uses report 2250 that includes a bar chart representing the percentage of times that a conference center was busy on the specified MCS when it was called during the specified time period.
- reports of usage by number of uses and usage by cumulative time used can be provided for switches 32 and AVSSs 100, and reports of being in use can be provided for AVSSs 100.
- Fig. 22D depicts an exemplary conference call availability report 2275 that includes a bar chart representing, for specified networks during a specified time period, the number of conference calls available for completion, the number of conference calls not completed due to unavailable resources and the number of calls not completed due to network error.
- the report 2275 shown in Fig. 22D concerns a service conference call report. Accordingly, the representations in the bar chart of calls not completed due to insufficient resources represent not only cases in which conference centers 36 are unavailable, but also cases in which other network resources are unavailable, such as AVSSs 100, if those resources are utilized for the call.
- Fig. 22E depicts an exemplary trunk busy report 2290 that includes a detailed listing for networks over a specified time period, a summary of the number of busy trunks during the specified time period.
- conference centers and trunks are specifically illustrated in the above reports, those skilled in the art will recognize that any service or shared hardware resources could be designated by the reporting features of the present invention and the above illustrations are merely exemplary.
- Fig. 23 is an example of a menu 2300 from which a user may select a variety of user-defined custom reports in accordance with the invention.
- Custom reports may be derived from standard reports, such as those shown in Figs. 13A-22D, and may be defined and saved in the database 200 in accordance with specified settings or parameters. Alternatively, a user may select from a list of variables and/or parameter choices and define particular conditions to create a unique custom report.
- Fig. 24 is an example of a custom report interface 2400 for saving custom reports to the database 200 in accordance with the invention.
- Fig. 25 is an example of a custom report save notification interface 2500 in accordance with the invention for indicating the success or failure of a saved report to the database 200.
- reports described herein were illustrated according to specific embodiments, those skilled in the art will recognize that the information contained in the reports can be presented according to any presentation implementation. Moreover, the reports can be printed or otherwise output using a vast number of different kinds of media without departing from the invention. Additionally, machine readable report files can be provided in commonly read file formats, such as "comma separated values" or any other similar file format scheme.
- the database 200 may store a plurality of system events and database query and calculation commands may actually be embedded in the web page code such that the database queries may be carried out without use of network accessed report query filter format servers 206, 216 and the like. Additionally, the utilization of a database 200 may be also eliminated by in some embodiments of the invention.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU57320/00A AU5732000A (en) | 1999-06-11 | 2000-06-09 | System and method for browser-based multimedia collaboration reporting |
CA002377014A CA2377014A1 (en) | 1999-06-11 | 2000-06-09 | System and method for browser-based multimedia collaboration reporting |
EP00942737A EP1208473A4 (en) | 1999-06-11 | 2000-06-09 | System and method for browser-based multimedia collaboration reporting |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13892199P | 1999-06-11 | 1999-06-11 | |
US60/138,921 | 1999-06-11 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2000077687A1 true WO2000077687A1 (en) | 2000-12-21 |
WO2000077687A9 WO2000077687A9 (en) | 2001-10-25 |
Family
ID=22484267
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2000/015990 WO2000077687A1 (en) | 1999-06-11 | 2000-06-09 | System and method for browser-based multimedia collaboration reporting |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP1208473A4 (en) |
AU (1) | AU5732000A (en) |
CA (1) | CA2377014A1 (en) |
WO (1) | WO2000077687A1 (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6714513B1 (en) | 2001-12-21 | 2004-03-30 | Networks Associates Technology, Inc. | Enterprise network analyzer agent system and method |
US6754705B2 (en) | 2001-12-21 | 2004-06-22 | Networks Associates Technology, Inc. | Enterprise network analyzer architecture framework |
US6789117B1 (en) | 2001-12-21 | 2004-09-07 | Networks Associates Technology, Inc. | Enterprise network analyzer host controller/agent interface system and method |
US6892227B1 (en) | 2001-12-21 | 2005-05-10 | Networks Associates Technology, Inc. | Enterprise network analyzer host controller/zone controller interface system and method |
US6941358B1 (en) | 2001-12-21 | 2005-09-06 | Networks Associates Technology, Inc. | Enterprise interface for network analysis reporting |
US7062783B1 (en) | 2001-12-21 | 2006-06-13 | Mcafee, Inc. | Comprehensive enterprise network analyzer, scanner and intrusion detection framework |
US7154857B1 (en) | 2001-12-21 | 2006-12-26 | Mcafee, Inc. | Enterprise network analyzer zone controller system and method |
US7483861B1 (en) | 2001-12-21 | 2009-01-27 | Mcafee, Inc. | System, method and computer program product for a network analyzer business model |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5862325A (en) * | 1996-02-29 | 1999-01-19 | Intermind Corporation | Computer-based communication system and method using metadata defining a control structure |
US5893903A (en) * | 1996-12-20 | 1999-04-13 | At&T Corp. | Multimedia message system with revenue allocation |
US5987454A (en) * | 1997-06-09 | 1999-11-16 | Hobbs; Allen | Method and apparatus for selectively augmenting retrieved text, numbers, maps, charts, still pictures and/or graphics, moving pictures and/or graphics and audio information from a network resource |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5745693A (en) * | 1992-07-01 | 1998-04-28 | Mci Corporation | System for gathering and reporting real time data from an IDNX communications network |
US5809235A (en) * | 1996-03-08 | 1998-09-15 | International Business Machines Corporation | Object oriented network event management framework |
ATE419580T1 (en) * | 1997-11-04 | 2009-01-15 | Avistar Comm Corp | SCALABLE MULTIMEDIA NETWORK SYSTEM AND APPLICATION |
-
2000
- 2000-06-09 CA CA002377014A patent/CA2377014A1/en not_active Abandoned
- 2000-06-09 AU AU57320/00A patent/AU5732000A/en not_active Abandoned
- 2000-06-09 WO PCT/US2000/015990 patent/WO2000077687A1/en active Application Filing
- 2000-06-09 EP EP00942737A patent/EP1208473A4/en not_active Withdrawn
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5862325A (en) * | 1996-02-29 | 1999-01-19 | Intermind Corporation | Computer-based communication system and method using metadata defining a control structure |
US5893903A (en) * | 1996-12-20 | 1999-04-13 | At&T Corp. | Multimedia message system with revenue allocation |
US5987454A (en) * | 1997-06-09 | 1999-11-16 | Hobbs; Allen | Method and apparatus for selectively augmenting retrieved text, numbers, maps, charts, still pictures and/or graphics, moving pictures and/or graphics and audio information from a network resource |
Non-Patent Citations (1)
Title |
---|
See also references of EP1208473A4 * |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6714513B1 (en) | 2001-12-21 | 2004-03-30 | Networks Associates Technology, Inc. | Enterprise network analyzer agent system and method |
US6754705B2 (en) | 2001-12-21 | 2004-06-22 | Networks Associates Technology, Inc. | Enterprise network analyzer architecture framework |
US6789117B1 (en) | 2001-12-21 | 2004-09-07 | Networks Associates Technology, Inc. | Enterprise network analyzer host controller/agent interface system and method |
US6892227B1 (en) | 2001-12-21 | 2005-05-10 | Networks Associates Technology, Inc. | Enterprise network analyzer host controller/zone controller interface system and method |
US6941358B1 (en) | 2001-12-21 | 2005-09-06 | Networks Associates Technology, Inc. | Enterprise interface for network analysis reporting |
US7062783B1 (en) | 2001-12-21 | 2006-06-13 | Mcafee, Inc. | Comprehensive enterprise network analyzer, scanner and intrusion detection framework |
US7154857B1 (en) | 2001-12-21 | 2006-12-26 | Mcafee, Inc. | Enterprise network analyzer zone controller system and method |
US7483861B1 (en) | 2001-12-21 | 2009-01-27 | Mcafee, Inc. | System, method and computer program product for a network analyzer business model |
US7522531B2 (en) | 2001-12-21 | 2009-04-21 | Mcafee, Inc. | Intrusion detection system and method |
Also Published As
Publication number | Publication date |
---|---|
CA2377014A1 (en) | 2000-12-21 |
EP1208473A1 (en) | 2002-05-29 |
AU5732000A (en) | 2001-01-02 |
EP1208473A4 (en) | 2007-03-07 |
WO2000077687A9 (en) | 2001-10-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP0721725B1 (en) | Multimedia collaboration system | |
US7107312B2 (en) | Apparatus and method for use in a data/conference call system for automatically collecting participant information and providing all participants with that information for use in collaboration services | |
US6594688B2 (en) | Dedicated echo canceler for a workstation | |
EP1008258B1 (en) | Network-based conference system | |
US7299257B2 (en) | Apparatus and method for use in collaboration services | |
US6914519B2 (en) | System and method for muting alarms during a conference | |
US20050018828A1 (en) | System and method for indicating a speaker during a conference | |
US20020147777A1 (en) | Apparatus and method for use in portal service for a team utilizing collaboration services | |
EP1661328B1 (en) | System and method for generating reports in a network | |
GB2319135A (en) | Teleconferencing system having a collaboration selection facility | |
WO2000077687A1 (en) | System and method for browser-based multimedia collaboration reporting | |
CA2296187C (en) | Synchronization in video conferencing | |
CA2297940C (en) | Two monitor videoconferencing hardware | |
US20050015289A1 (en) | Reservation information reference system and method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
AK | Designated states |
Kind code of ref document: C2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: C2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
COP | Corrected version of pamphlet |
Free format text: PAGES 1/49-49/49, DRAWINGS, REPLACED BY NEW PAGES 1/47-47/47; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2377014 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2000942737 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10018441 Country of ref document: US |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWP | Wipo information: published in national office |
Ref document number: 2000942737 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: JP |