Connect public, paid and private patent data with Google Patents Public Datasets

Integrated interface for real time web based viewing of telecommunications network call traffic

Info

Publication number
WO1999016198A1
WO1999016198A1 PCT/US1998/020146 US9820146W WO1999016198A1 WO 1999016198 A1 WO1999016198 A1 WO 1999016198A1 US 9820146 W US9820146 W US 9820146W WO 1999016198 A1 WO1999016198 A1 WO 1999016198A1
Authority
WO
Grant status
Application
Patent type
Prior art keywords
system
server
call
subscriber
mts
Prior art date
Application number
PCT/US1998/020146
Other languages
French (fr)
Inventor
Curtis T. Comber
Carol Y. Devine
Robert A. Pfister
Original Assignee
Comber Curtis T
Devine Carol Y
Pfister Robert A
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0709Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766Error or fault reporting or storing
    • G06F11/0769Readable error formats, e.g. cross-platform generic formats, human understandable formats
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766Error or fault reporting or storing
    • G06F11/0775Content or structure details of the error report, e.g. specific table structure, specific error fields
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766Error or fault reporting or storing
    • G06F11/0781Error filtering or prioritizing based on a policy defined by the user or on a policy defined by a hardware/software module, e.g. according to a severity level
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766Error or fault reporting or storing
    • G06F11/0784Routing of error reports, e.g. with a specific transmission path or data flow
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/32Monitoring with visual or acoustical indication of the functioning of the machine
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/32Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324Display of status information
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/32Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324Display of status information
    • G06F11/327Alarm or error message display
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/34Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466Performance evaluation by tracing or monitoring
    • G06F11/3495Performance evaluation by tracing or monitoring for systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F17/00Digital computing or data processing equipment or methods, specially adapted for specific functions
    • G06F17/30Information retrieval; Database structures therefor ; File system structures therefor
    • G06F17/30861Retrieval from the Internet, e.g. browsers
    • G06F17/3089Web site content organization and management, e.g. publishing, automatic linking or maintaining pages
    • G06F17/30893Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31User authentication
    • G06F21/41User authentication where a single sign-on provides access to a plurality of computers
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/55Detecting local intrusion or implementing counter-measures
    • G06F21/552Detecting local intrusion or implementing counter-measures involving long-term monitoring or reporting
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation, e.g. computer aided management of electronic mail or groupware; Time management, e.g. calendars, reminders, meetings or time accounting
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation, e.g. computer aided management of electronic mail or groupware; Time management, e.g. calendars, reminders, meetings or time accounting
    • G06Q10/107Computer aided management of electronic mail
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102Bill distribution or payments
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/382Payment protocols; Details thereof insuring higher security of transaction
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce, e.g. shopping or e-commerce
    • G06Q30/02Marketing, e.g. market research and analysis, surveying, promotions, advertising, buyer profiling, customer management or rewards; Price estimation or determination
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce, e.g. shopping or e-commerce
    • G06Q30/06Buying, selling or leasing transactions
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce, e.g. shopping or e-commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce, e.g. shopping or e-commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping
    • G06Q30/0609Buyer or seller confidence or verification
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce, e.g. shopping or e-commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping
    • G06Q30/0633Lists, e.g. purchase orders, compilation or processing
    • G06Q30/0635Processing of requisition or of purchase orders
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q99/00Subject matter not provided for in other groups of this subclass
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Metering, charging or billing arrangements specially adapted for data wireline or wireless communications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Metering, charging or billing arrangements specially adapted for data wireline or wireless communications
    • H04L12/1428Invoice generation, e.g. customization, lay-out, database processing, algorithms for calculating the bill or formatting invoices as WWW pages
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/02Communication control; Communication processing contains provisionally no documents
    • H04L29/06Communication control; Communication processing contains provisionally no documents characterised by a protocol
    • H04L29/0602Protocols characterised by their application
    • H04L29/06027Protocols for multimedia communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/02Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization
    • H04L41/0213Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization using standardized network management protocols, e.g. simple network management protocol [SNMP] or common management interface protocol [CMIP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/02Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization
    • H04L41/0233Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization using object oriented techniques, e.g. common object request broker architecture [CORBA] for representation of network management data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/02Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization
    • H04L41/024Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/02Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization
    • H04L41/0246Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization exchanging or transporting network management information using Internet, e.g. aspects relating to embedding network management web servers in network elements, web service for network management purposes, aspects related to Internet applications or services or web-based protocols, simple object access protocol [SOAP]
    • H04L41/0253Arrangements for maintenance or administration or management of packet switching networks involving integration or standardization exchanging or transporting network management information using Internet, e.g. aspects relating to embedding network management web servers in network elements, web service for network management purposes, aspects related to Internet applications or services or web-based protocols, simple object access protocol [SOAP] involving a browser or web-pages for accessing management information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/08Configuration management of network or network elements
    • H04L41/0803Configuration setting of network or network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/08Configuration management of network or network elements
    • H04L41/0876Aspects of the degree of configuration automation
    • H04L41/0879Manual configuration through operator
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/14Arrangements for maintenance or administration or management of packet switching networks involving network analysis or design, e.g. simulation, network model or planning
    • H04L41/142Arrangements for maintenance or administration or management of packet switching networks involving network analysis or design, e.g. simulation, network model or planning using statistical or mathematical methods
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/18Arrangements involving CNM [Customer Network Management]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/22Arrangements for maintenance or administration or management of packet switching networks using GUI [Graphical User Interface]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/28Security in network management, e.g. restricting network management access
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/5019Ensuring SLA
    • H04L41/5022Ensuring SLA by giving priorities, e.g. assigning classes of service
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/5035Measuring contribution of individual network components to actual service level
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/5061Customer care
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/5061Customer care
    • H04L41/5064Customer relationship management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/5061Customer care
    • H04L41/5067Customer-centric quality of service [QoS] measurement
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/5061Customer care
    • H04L41/5074Handling of trouble tickets
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/508Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer based on type of value added network service under agreement
    • H04L41/5083Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer based on type of value added network service under agreement wherein the managed service relates to web hosting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/508Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer based on type of value added network service under agreement
    • H04L41/5096Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/02Arrangements for monitoring or testing packet switching networks involving a reduction of monitoring data
    • H04L43/022Arrangements for monitoring or testing packet switching networks involving a reduction of monitoring data using sampling of monitoring data, i.e. storing only a selection of packets
    • H04L43/024Arrangements for monitoring or testing packet switching networks involving a reduction of monitoring data using sampling of monitoring data, i.e. storing only a selection of packets using adaptive sampling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/06Report generation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/08Monitoring based on specific metrics
    • H04L43/0805Availability
    • H04L43/0817Availability functioning
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/08Monitoring based on specific metrics
    • H04L43/0823Errors
    • H04L43/0829Packet loss
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0209Architectural arrangements, e.g. perimeter networks or demilitarized zones
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0227Filtering policies
    • H04L63/0236Filtering by address, protocol, port number or service, e.g. IP-address or URL
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0272Virtual private networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0281Proxies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0442Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0464Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network
    • H04L63/0807Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network using tickets, e.g. Kerberos
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network
    • H04L63/0823Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network using certificates
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network
    • H04L63/083Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network using passwords
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/16Implementing security features at a particular protocol layer
    • H04L63/162Implementing security features at a particular protocol layer at the data link layer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/16Implementing security features at a particular protocol layer
    • H04L63/166Implementing security features at a particular protocol layer at the transport layer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/16Implementing security features at a particular protocol layer
    • H04L63/168Implementing security features at a particular protocol layer above the transport layer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/18Network architectures or network communication protocols for network security using different networks or paths for security, e.g. using out of band channels
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements or protocols for real-time communications
    • H04L65/40Services or applications
    • H04L65/4007Services involving a main real-time session and one or more additional parallel sessions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements or protocols for real-time communications
    • H04L65/80QoS aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/41Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/43Billing software details
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/44Augmented, consolidated or itemized billing statement or bill presentation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/49Connection to several service providers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/51Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for resellers, retailers or service providers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/58Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on statistics of usage or network monitoring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70Administration or customization aspects; Counter-checking correct charges
    • H04M15/705Account settings, e.g. limits or numbers or payment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70Administration or customization aspects; Counter-checking correct charges
    • H04M15/72Administration or customization aspects; Counter-checking correct charges by the user
    • H04M15/721Administration or customization aspects; Counter-checking correct charges by the user using the Internet
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70Administration or customization aspects; Counter-checking correct charges
    • H04M15/745Customizing according to wishes of subscriber, e.g. friends or family
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80Rating or billing plans; Tariff determination aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80Rating or billing plans; Tariff determination aspects
    • H04M15/8044Least cost routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83Notification aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83Notification aspects
    • H04M15/835Time or frequency of notifications, e.g. Advice of Charge [AoC]
    • H04M15/8351Time or frequency of notifications, e.g. Advice of Charge [AoC] before establishing a communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/83Notification aspects
    • H04M15/84Types of notifications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/50Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H04M3/5175Call or contact centers supervision arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/50Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H04M3/5183Call or contact centers with computer-telephony arrangements
    • H04M3/5191Call or contact centers with computer-telephony arrangements interacting with the Internet
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0751Error or fault detection not based on redundancy
    • G06F11/0754Error or fault detection not based on redundancy by exceeding limits
    • G06F11/0757Error or fault detection not based on redundancy by exceeding limits by exceeding a time limit, i.e. time-out, e.g. watchdogs
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16Error detection or correction of the data by redundancy in hardware
    • G06F11/20Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/32Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324Display of status information
    • G06F11/328Computer systems status display
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F2201/00Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/81Threshold
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F2201/00Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/86Event-based monitoring
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F2201/00Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/875Monitoring of systems including the internet
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2137Time limited access, e.g. to a computer or data
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2149Restricted operating environment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/06Arrangements for maintenance or administration or management of packet switching networks involving management of faults or events or alarms
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/06Arrangements for maintenance or administration or management of packet switching networks involving management of faults or events or alarms
    • H04L41/0681Arrangements for maintenance or administration or management of packet switching networks involving management of faults or events or alarms involving configuration of triggering conditions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/08Configuration management of network or network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/5003Managing service level agreement [SLA] or interaction between SLA and quality of service [QoS]
    • H04L41/5009Determining service level performance, e.g. measuring SLA quality parameters, determining contract or guarantee violations, response time or mean time between failure [MTBF]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/5029Service quality level based billing, e.g. dependent on measured service level customer is charged more or less
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/5032Generating service level reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/04Processing of captured monitoring data
    • H04L43/045Processing of captured monitoring data for graphical visualization of monitoring data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/06Report generation
    • H04L43/062Report generation for traffic related reporting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/06Report generation
    • H04L43/065Report generation for device related reporting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/06Report generation
    • H04L43/067Report generation for time frame related reporting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/08Monitoring based on specific metrics
    • H04L43/0805Availability
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/08Monitoring based on specific metrics
    • H04L43/0805Availability
    • H04L43/0811Connectivity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/08Monitoring based on specific metrics
    • H04L43/0823Errors
    • H04L43/0847Transmission error
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/08Monitoring based on specific metrics
    • H04L43/0852Delays
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/08Monitoring based on specific metrics
    • H04L43/0876Network utilization
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/08Monitoring based on specific metrics
    • H04L43/0876Network utilization
    • H04L43/0888Throughput
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/08Monitoring based on specific metrics
    • H04L43/0876Network utilization
    • H04L43/0894Packet rate
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/10Arrangements for monitoring or testing packet switching networks using active monitoring, e.g. heartbeat protocols, polling, ping, trace-route
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/10Arrangements for monitoring or testing packet switching networks using active monitoring, e.g. heartbeat protocols, polling, ping, trace-route
    • H04L43/106Arrangements for monitoring or testing packet switching networks using active monitoring, e.g. heartbeat protocols, polling, ping, trace-route by adding timestamps to packets
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/16Arrangements for monitoring or testing packet switching networks using threshold monitoring
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0209Architectural arrangements, e.g. perimeter networks or demilitarized zones
    • H04L63/0218Distributed architectures, e.g. distributed firewalls
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network
    • H04L63/0815Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network providing single-sign-on or federations
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0104Augmented, consolidated or itemised billing statement, e.g. additional billing information, bill presentation, layout, format, e-mail, fax, printout, itemised bill per service or per account, cumulative billing, consolidated billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0108Customization according to wishes of subscriber, e.g. customer preferences, friends and family, selecting services or billing options, Personal Communication Systems [PCS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0152General billing plans, rate plans, e.g. charge rates, numbering plans, rate centers, customer accounts
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0164Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0168On line or real-time flexible customization or negotiation according to wishes of subscriber
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0176Billing arrangements using internet
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/018On-line real-time billing, able to see billing information while in communication, e.g. via the internet
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01Details of billing arrangements
    • H04M2215/0188Network monitoring; statistics on usage on called/calling number
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/42Least cost routing, i.e. provision for selecting the lowest cost tariff
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/46Connection to several service providers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/54Resellers-retail or service providers billing, e.g. agreements with telephone service operator, activation, charging/recharging of accounts
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/70Administration aspects, modify settings or limits or counter-check correct charges
    • H04M2215/7009Account settings, e.g. users, terminals, limits, numbers or payment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/70Administration aspects, modify settings or limits or counter-check correct charges
    • H04M2215/7036Administer via user
    • H04M2215/7045Using Internet or WAP
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/74Rating aspects, e.g. rating parameters or tariff determination apects
    • H04M2215/745Least cost routing, e.g. Automatic or manual, call by call or by preselection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/81Notifying aspects, e.g. notifications or displays to the user
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/81Notifying aspects, e.g. notifications or displays to the user
    • H04M2215/8104Time or frequency of notification
    • H04M2215/8108Time or frequency of notification before establishing a communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/81Notifying aspects, e.g. notifications or displays to the user
    • H04M2215/8129Type of notification
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2215/00Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/82Advice-of-Charge [AOC], i.e. notify subscriber of charges/cumulative charge; meter at the substation
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S379/00Telephonic communications
    • Y10S379/90Internet, e.g. Internet phone, webphone, internet-based telephony
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99937Sorting
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99938Concurrency, e.g. lock management in shared database
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99939Privileged access
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99944Object-oriented database structure
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S715/00Data processing: presentation processing of document, operator interface processing, and screen saver display processing
    • Y10S715/961Operator interface with visual structure or function dictated by intended use
    • Y10S715/965Operator interface with visual structure or function dictated by intended use for process control and configuration
    • Y10S715/969Network layout and operation interface

Abstract

A system and method for providing both telecommunications network statistical reporting functions and reporting on a call by call detail basis, over the public Internet. A 'TRAFFICVIEW' Server (TVS) system (32) and Real time monitoring system is integrated with a web/Internet based reporting system infrastructure and is responsive to instructions provided by subscribers over the internet (15) so that reports may be provided on a given time period, at a given frequency and in a particular format. Standard traffic call detail reports are delivered to the subscriber via a browser based GUI. The GUI provides all reporting functions the subscriber is entitled to. A subscriber may obtain a static view of the traffic for a special service call number by communicating with the TVS (32). Moreover, a remote subscriber may be provided via a browser based workstation GUI with data files containing raw call details and statistics in a predetermined format.

Description

INTEGRATED INTERFACE FOR REAL TIME WEB BASED VIEWING OF TELECOMMUNICATIONS NETWORK CALL TRAFFIC

The present invention relates generally to special service telephone call processing such as 800/8xx, 900 and "VNET" calls in a telecommunications network, and more particularly, to a World Wide Web/Internet enabled apparatus and methodology for viewing network call traffic information and call statistics in real-time.

Commonly assigned U.S. Patent No. 5,537,611 issued July 10, 1996 discloses a network management scheme for special service calls which allows the management of a telecommunications network to oversee the network to ascertain traffic surges and provide traffic controls to alleviate network congestion. In particular, the '230 application discloses the utilization of a Data Access Point (DAP) for storing information relating to different special service call numbers, information relating to subscribers who subscribe to the various services, and translation tables that provide the data needed to translate a special service call number into a real call number associated with a particular network switch. A processor associated with the DAP, referred to as a DAP Traffic Statistics (DTS) , converts the collected traffic data into statistics data and forwards the same to a compiler processor of an Integrated Network Management System (INMS) . The INMS provides reports containing the compiled statistics data for the special service call number to subscribers and the management of the telecommunications network. With the information from the INMS, a subscriber could read just

-V

SUBST1TUTE SHEET (RULE 26) the parameters for a special service call number and reallocate the calls made to the call number to different destination stations. The management of the network, at the same time, can review the information from the DTS and reroute traffic in the network to avoid congestion or call blocking caused by any one of the special service call numbers.

Conventionally, subscribers' access to their telecommunications network call traffic information is made via a dial-up connection to the INMS mid range computer server from a customer owned personal computer or work station. This connection frequently, although not always, emulates a terminal addressable by the mid range computer system. The dial-up access requires custom software on the customer workstation to provide dial-up services, communication services, emulation and/or translation services and generally some resident custom form of the INMS mid range computer application to enable the interface therewith. There are several problems associated with this approach:

First, the aforementioned software is very hardware specific, and customers generally have a wide range of workstation vendors, which requires extensive inventory for distribution, and generally, intensive customer hand holding through initial setup and installation before reliable and secure sessions are possible. If the customer hardware platform changes through an upgrade, most of these issues need renegotiation.

Secondly, dial-up, modem, and communications software interact with each other in many ways which are not always predicable to a custom application, requiring extensive trouble shooting and problem solving for an enterprise desiring to make the legacy system available to the customer, particularly where various telephone exchanges, dialing standards or signal standards are involved.

Third, when an enterprise desires to make more than one system available to the customer, the custom application for one legacy system or mid range application is not able to connect to a different legacy system, and the customer must generally logoff and logon to switch from one to the other. The delivery technology used by the two legacy systems may be different, requiring different interface standards, and different machine level languages may be used by the two systems, as for example, the 96 character EBSDIC language used by IBM, and the 127 character ASCII language used by contemporary personal computers.

Finally, the security and entitlement features of the various legacy systems may be completely different, and vary from system to system and platform to platform.

As subscriber's desire an open access route to their 800/900 and VNET call traffic information and related statistics, it is desired to provide connectivity to enterprise mid range or legacy systems over the public Internet, as the Internet provides access connectivity world wide via the TCP/IP protocol, without need to navigate various telephone exchanges, dialing standards or signal standards. The present invention is one component of an integrated suite of customer network management and report applications using the internet and a World Wide Web ("WWW" or "Web") Web browser paradigm. Introduced to the communications industry as "nMCI Interact" the integrated suite of Web -based applications provides an invaluable tool for enabling customers of a telecommunications enterprise to manage their telecommunication assets, quickly and securely, from anywhere in the world.

The popularity of the public Internet provides a measure of platform independence for the customer, as the customer can run their own Internet web -browser and utilize their own platform connection to the Internet to enable service. This resolves many of the platform hardware and connectivity issues in the customers favor, and lets the customer choose their own platform and operating system. Web -based programs can minimize the need for training and support since they utilize existing client software which the user has already installed and already knows how to use. Further, if the customer later changes that platform, then, as soon as the new platform is Internet enabled, service is restored to the customer. The connectivity and communications software burden is thus resolved in favor of standard and readily available hardware and the browser and dialup software used by the public Internet connection. An Internet delivered paradigm obviates many of the installation and configuration problems involved with initial setup and configuration of a customer workstation, since the custom application required to interface with the legacy system can be delivered via the public Internet and run within a standard web- browser, reducing application compatibility issues to browser compatibility issues. For the enterprise, the use of off-the-shelf web browsers by the customer significantly simplifies the enterprise burden by limiting the client development side to screen layouts and data presentation tools that use a common interface enabled by the web browser. Software development and support resources are thus available for the delivery of the enterprise legacy services and are not consumed by a need for customer support at the work station level. The present invention thus satisfies the above mentioned needs by providing an internet enabled and Web -based remote interface that allows a customer to open and monitor trouble tickets relating to network events on the enterprise network. The TrafficView System server ("TVS") comprises an integration of the existing DTS system and an MCI Traffic Statistics (MTS) system which is a service that provides subscribers with insight into their call attempts and completions, beyond current DTS reporting capabilities. The TVS system is thus comprehensive, providing subscribers with information related to their special service calls, for example 800/900, call disposition statistics and call detail information. The source of data for the MTS system is

800/900 Call Detail Records (CDRs) generated by the various network switches. These CDRs are collected by network Adjunct Processors (APs) , associated with corresponding ones of the network switches. Once collected, the CDRs are delivered to the MTS system for immediate processing. Upon receipt of the CDRs from the APs, the MTS system will forward periodically, for example hourly, the call statistics to the TVS. The MTS system stores multiple hourly CDRs for each of the special service numbers.

For call by call details, the TVS system is supplied with Enhanced Call Detail Records (ECDR) by the MTS system. For the current embodiment of the instant invention, the statistical data is sent to the TVS system on an hourly basis, and the ECDR data is sent to the TVS system in near real time. These records are used to generate additional different call detail reports, known as "unpriced data" reports. In addition, these ECDRs are the source of a Real Time Traffic Monitor (RTM) system that enables a subscriber of the system to view in real time the operation of the network, i.e. the statistics relating to the calls directed to the special service call number (s) of the subscriber. In particular, upon signing onto the RTM service, a subscriber is given a password by the management of the network so that through a web browser, the subscriber may access directly the TVS system via the public Internet. The ECDR data sent to the TVS system can then be accessed directly by the subscriber in substantially real time so that the ongoing operation of the network, at least with respect to the subscriber's special service call number(s), can be monitored by the subscriber. The subscriber can accordingly reallocate his resources, for example redirecting calls to his special service call number to different locations where the operators of the subscriber are located. The present invention provides an Internet enabled and Web-based remote interface that allows a customer to retrieve their unpriced call traffic detail information and call disposition statistics in the form

-6-

SUBST1TUTE SHEET (RULE 26) of reports, as well as access and view their real-time call traffic details relating to their special service call numbers.

To access their unpriced call traffic data and/or real-time call traffic details at a user's remote customer workstation, a user first logs on to the internet through any internet access route, and then logs on to the enterprise Web- server. After verification of the customer's entitlements to use the system, the Web -server downloads an available suite of services for that customer, which includes the TrafficView system tool, which is offered by the assignee of the present invention as the "Traffic Monitor" service or "Unpriced Reporting." This service is provided to the customer through a service object that is invoked and maintained by a browser based backplane, and which calls, as needed, other objects, including objects to enable graphical displays of data to the customer. From the opening screen, the customer may select the opportunity to view their real-time traffic, and the Web- server will then download the service program object to enable this.

At the time of customer verification, the enterprise customer service management system has obtained certain information relating to an RTM profile maintained on a TVS server. This RTM profile information automatically prepopulates at least one field in a dialog involved in the opening of a unpriced data reporting screen or traffic monitor screen. In this prepopulation process, data included within the customer profile is automatically entered into a field of a particular dialog. Through this prepopulation, the amount of required user input is minimized, thereby increasing customer usability.

In the preferred embodiment, a number of different unpriced call detail reports may be generated which are delivered via a novel web -based report generation and delivery system integrated within nMCI Interact.

A feature of the report generation and delivery system for unpriced reporting, is the ability to customize the reports a subscriber is entitled to receive. For example, a subscriber can obtain the call details of a special service call subscribed by him for a particular period of time instead of real time. Furthermore, the subscriber can download a data file comprising the raw call details of the special service call for a particular period of time.

The present invention thus provides a web/Internet based reporting tool for generating traffic statistics data as specialized reports and/or data files to subscribers who subscribe to the special service call processing service provided by the network; and, via the public internet: i) provides the ability to download call statistics from a database of the TVS system so that a subscriber can format and design his own reports; ii) provides a subscriber with the ability to instruct the system to provide reports on a particular given time through a particular method; iii) provides reports to subscribers that include greater call details of their subscribed special service calls than other previous systems and methods; and iv) provides real time enhanced call detail records to subscribers so that a subscriber can monitor in real time the operation of the network, so as to be able to effect the necessary changes expeditiously. The above-mentioned aspects and advantages of the present invention will become more apparent and the invention itself will be best understood by reference to the following description of the invention taken in conjunction with the accompanying drawings, wherein: Figure 1 illustrates the software architecture component comprising a three- tiered structure;

Figure 2 is a diagrammatic overview of the software architecture of the networkMCI Interact system;

Figure 3 is an illustrative example of a backplane architecture schematic;

Figure 4 illustrates an example client GUI presented to the client/customer as a browser web page; Figure 5 is a diagram depicting the physical networkMCI Interact system architecture;

Figure 6 is an overall view of the "TRAFFICVIEW" system of the instant invention;

Figure 7 is a block diagram depicting the physical architecture of the StarWRS component of the networkMCI Interact system;

Figure 8 is a diagram illustrating the functions of the MCI traffic statistics system of the present invention "TRAFFICVIEW" system; Figure 9 is a diagram illustrating the different functions of the MCI Traffic Statistics (MTS) system, in receiving data and transmitting that data to the "TRAFFICVIEW" Server (TVS) of the "TRAFFICVIEW" system of the present invention;

Figure 10 is a diagram illustrating the functional relationships between the TVS system and the various systems connected thereto in the "TRAFFICVIEW" system of the present invention;

Figure 11 is a functional diagram illustrating the major functional areas of the TVS system; Figure 12 is a diagram illustrating the various reports being provided by the process report function of the TVS system;

Figure 13 is a diagram illustrating the major functional processes of the RTM system of the instant invention;

Figure 14 is a diagram showing the interrelationship between the various screens of the RTM system;

Figure 15 (a) is an exemplar profile selection screen;

Figure 15 (b) is an exemplar adding profile screen;

Figure 15 (c) is an exemplar delete a profile screen; Figure 15 (d) is an exemplar adding a single

800 number screen;

Figure 15 (e) is an exemplar top five number selection screen;

Figure 15(f) is an exemplar changing polling interval screen;

Figure 15 (g) is an exemplar changing poll start time screen; Figure 15 (h is an exemplar summary statistics screen;

Figure 15 (i is an exemplar incomplete summary screen;

Figure 15 (j is an exemplar other summary screen;

Figure 15 (k is an exemplar call detail inquiry screen;

Figure 15 (1 is an exemplar call disposition selection screen;

Figure 15 (m is an exemplar call detail record display screen; and,

Figure 16 is a block diagram illustrating the logon procedure for Internet access to the TrafficView and real-time traffic monitoring systems of the present invention.

The popularity and wide spread adoption of the public Internet provides a measure of platform independence for customers who desire to connect to an enterprise system, as the customer can run their own Internet web -browser and utilize their own platform connection to the Internet to enable service. This resolves many of the platform hardware and connectivity issues in the customers favor, and lets the customer choose their own workstation platform and operating system. Web-based programs can minimize the need for training and support since they utilize existing customer browser software which the user has already installed and already knows how to use. Any issues relating to connectivity and communications have already been resolved in favor of standard and readily available hardware and the browser and dialup software used by the public Internet connection. An Internet delivered paradigm for customer services obviates many of the installation and configuration problems involved with initial setup and configuration of a dial-up customer workstation, since the custom application required to interface with the legacy system can be delivered via the public Internet and run within a standard web-browser, reducing application compatibility issues to browser compatibility issues.

Architectural Overview of The Web -enabled System

The web -enabled system in which the present

"Traffic View and Real Time Monitor Service" invention is found is a suite of customer network management and report applications using a Web browser paradigm.

Known as the networkMCI Interact system ( "nMCI

Interact") such an integrated suite of Web-based applications provides an invaluable tool for enabling customers to manage their telecommunication assets, quickly and securely, from anywhere in the world. The nMCI Interact system architecture is basically organized as a set of common components comprising the following: 1) an object-oriented software architecture detailing the client and server based aspect of nMCI

Interact;

2) a network architecture defining the physical network needed to satisfy the security and data volume requirements of the networkMCI System;

3) a data architecture detailing the application, back-end or legacy data sources available for networkMCI Interact; and

-12-

SUBST1TUTE SHEET (RULE 26) 4) an infrastructure covering security, order entry, fulfillment, billing, self -monitoring, metrics and support.

Each of these common component areas will be generally discussed hereinbelow.

Figure 1 is a diagrammatic illustration of the software architecture component in which the present invention functions. A first or client tier 10 of software services are resident on a customer work station 10 and provides customer access to the enterprise system, having one or more downloadable application objects directed to front end business logic, one or more backplane service objects for managing sessions, one or more presentation services objects for the presentation of customer options and customer requested data in a browser recognizable format and a customer supplied browser for presentation of customer options and data to the customer and for internet communications over the public Internet. Additionally applications are directed to front end services such as the presentation of data in the form of tables and charts, and data processing functions such as sorting and summarizing in a manner such that multiple programs are combined in a unified application suite.

A second or middle tier 12, is provided having secure web servers and back end services to provide applications that establish user sessions, govern user authentication and their entitlements, and communicate with adaptor programs to simplify the interchange of data across the network.

A third or back end tier 15 having applications directed to legacy back end services including database storage and retrieval systems and one or more database servers for accessing system resources from one or more legacy hosts.

Generally, the customer workstation includes client software capable of providing a platform- independent, browser-based, consistent user interface implementing objects programmed to provide a reusable and common GUI abstraction and problem- domain abstractions. More specifically, the client- tier software is created and distributed as a set of Java classes including the applet classes to provide an industrial strength, object-oriented environment over the Internet. Application- specific classes are designed to support the functionality and server interfaces for each application with the functionality delivered through the system being of two -types: 1) cross-product, for example, inbox and reporting functions, and 2) product specific, for example, toll free network management or Call Manager functions. The system is capable of delivering to customers the functionality appropriate to their product mix.

Figure 2 is a diagrammatic overview of the software architecture of the networkMCI Interact system including: the Customer Browser (a.k.a. the Client) 20; the Demilitarized Zone (DMZ) 17 comprising a Web

Servers cluster 24; the MCI Intranet Dispatcher Server 26; and the MCI Intranet Application servers 30, and the data warehouses, legacy systems, etc. 40.

The Customer Browser 20, is browser enabled and includes client applications responsible for presentation and front -end services. Its functions include providing a user interface to various MCI services and supporting communications with MCI's Intranet web server cluster 24. As illustrated in Figure 3, the client tier software is responsible for presentation services to the customer and generally includes a web browser 14 and additional object - oriented programs residing in the client workstation platform 20. The client software is generally organized into a component architecture with each component generally comprising a specific application, providing an area of functionality. The applications generally are integrated using a "backplane" services layer 12 which provides a set of services to the application objects which provide the front end business logic and manages their launch. The networkMCI Interact common set of objects provide a set of services to each of the applications such as: 1) session management; 2) application launch; 3) inter - application communications; 4) window navigation among applications; 5) log management; and 6) version management . The primary common object services include: graphical user interface (GUI); communications; printing; user identity, authentication, and entitlements; data import and export; logging and statistics; error handling; and messaging services. Figure 3 is a diagrammatic example of a backplane architecture scheme illustrating the relationship among the common objects. In this example, the backplane services layer 12 is programmed as a Java applet which can be loaded and launched by the web browser 14. With reference to Figure 3, a typical user session starts with a web browser 14 creating a backplane 12, after a successful logon. The backplane 12, inter alia, presents a user with an interface for networkMCI Interact application management. A typical user display provided by the backplane 12 may show a number of applications the user is entitled to run, each application represented by buttons depicted in Figure 3 as buttons 58a, b,c selectable by the user. As illustrated in Figure 3, upon selection of an application, the backplane 12 launches that specific application, for example, Service Inquiry 54a or Alarm Monitor 54b, by creating the application object. In processing its functions, each application in turn, may utilize common object services provided by the backplane 12. Figure 3 shows graphical user interface objects 56a, b created and used by a respective application 54a, b for its own presentation purposes.

Figure 4 illustrates an example client GUI presented to the client/customer as a browser web page 80 providing, for example, a suite 70 of network management reporting applications including: MCI Traffic Monitor 72; an alarm monitor 73; a Network Manager 74 and Intelligent Routing 75. Access to network functionality is also provided through Report Requester 76, which provides a variety of detailed priced and unpriced call detail data reports for the client/customer and a Message Center 77 for providing enhancements and functionality to traditional e-mail communications .

As shown in Figures 3 and 4, the browser resident GUI of the present invention implements a single object, COBackPlane which keeps track of all the client applications, and which has capabilities to start, stop, and provide references to any one of the client applications.

-16-

SUBST1TUTE SHEET (RULE 26) The backplane 12 and the client applications use a browser 14 such as the Microsoft Explorer versions 4.0.1 or higher for an access and distribution mechanism. Although the backplane is initiated with a browser 14, the client applications are generally isolated from the browser in that they typically present their user interfaces in a separate frame, rather than sitting inside a Web page.

The backplane architecture is implemented with several primary classes. These classes include COBackPlane, COApp, COAppImpl , COParm. and COAppFrame classes. COBackPlane 12 is an application backplane which launches the applications 54a, 54b, typically implemented as COApp. COBackPlane 12 is generally implemented as a Java applet and is launched by the Web browser 14. This backplane applet is responsible for launching and closing the COApps .

When the backplane is implemented as an applet, it overrides standard Applet methods init(), start (), stop() and run ( ) . In the initO method, the backplane applet obtains a COUser user context object. The COUser object holds information such as user profile applications and their entitlements. The user's configuration and application entitlements provided in the COUser context are used to construct the application toolbar and Inbox applications. When an application toolbar icon is clicked, a particular COApp is launched by launchAppO method. The launched application then may use the backplane for inter- application communications, including retrieving Inbox data.

The COBackPlane 12 includes methods for providing a reference to a particular COApp, for

-17-

SUBST1TUTE SHEET (RULE 26) interoperation. For example, the COBackPlane class provides a getApp ( ) method which returns references to application objects by name. Once retrieved in this manner, the application object's public interface may be used directly.

As shown in Figure 2, the aforesaid objects will communicate the data by establishing a secure TCP messaging session with one of the DMZ networkMCI Interact Web servers 24 via an Internet secure communications path 22 established, preferably, with a secure sockets SSL version of HTTPS . The DMZ networkMCI Interact Web servers 24 function to decrypt the client message, preferably via the SSL implementation, and unwrap the session key and verify the users session. After establishing that the request has come from a valid user and mapping the request to its associated session, the DMZ Web servers 24 will re- encrypt the request using symmetric encryption and forward it over a second socket connection 23 to the dispatch server 26 inside the enterprise Intranet.

A networkMCI Interact session is designated by a logon, successful authentication, followed by use of server resources, and logoff. However, the worldwide web communications protocol uses HTTP, a stateless protocol, each HTTP request and reply is a separate TCP/IP connection, completely independent of all previous or future connections between the same server and client. The nMCI Interact system is implemented with a secure version of HTTP such as S-HTTP or HTTPS, and preferably utilizes the SSL implementation of HTTPS. The preferred embodiment uses SSL which provides a cipher spec message which provides server authentication during a session. The preferred

-18-

SUBST1TUTE SHEET (RULE 26) embodiment further associates a given HTTPS request with a logical session which is initiated and tracked by a "cookie jar server" 28 to generate a "cookie" which is a unique server -generated key that is sent to the client along with each reply to a HTTPS request. The client holds the cookie and returns it to the server as part of each subsequent HTTPS request. As desired, either the Web servers 24, the cookie jar server 28 or the Dispatch Server 26, may maintain the "cookie jar" to map these keys to the associated session. A separate cookie jar server 28, as illustrated in Figure 2 has been found desirable to minimize the load on the dispatch server 26. This form of session management also functions as an authentication of each HTTPS request, adding an additional level of security to the overall process.

As illustrated in Figure 2, after one of the DMZ Web servers 24 decrypts and verifies the user session, it forwards the message through a firewall 25b over a TCP/IP connection 23 to the dispatch server 26 on a new TCP socket while the original socket 22 from the browser is blocking, waiting for a response. The dispatch server 26 will unwrap an outer protocol layer of the message from the DMZ services cluster 24, and will reencrypt the message with symmetric encryption and forward the message to an appropriate application proxy via a third TCP/IP socket 27. While waiting for the proxy response all three of the sockets 22, 23, 27 will be blocking on a receive. Specifically, once the message is decrypted, the wrappers are examined to reveal the user and the target middle- tier (Intranet application) service for the request. A first -level validation is performed, making sure that the user is

-19-

SUBST1TUTE SHEET (RULE 26) entitled to communicate with the desired service. The user's entitlements in this regard are fetched by the dispatch server 26 from a system administration ("StarOE") server 49 at logon time and cached. If the requestor is authorized to communicate with the target service, the message is forwarded to the desired service's proxy. Each application proxy is an application specific daemon which resides on a specific Intranet server, shown in Figure 2 as a suite of mid- range servers 30. Each Intranet application server of suite 30 is generally responsible for providing a specific back-end service requested by the client, and, is additionally capable of requesting services from other Intranet application servers by communicating to the specific proxy associated with that other application server. Thus, an application server not only can offer its browser a client to server interface through the proxy, but also may offer all its services from its proxy to other application servers. In effect, the application servers requesting service are acting as clients to the application servers providing the service. Such mechanism increases the security of the overall system as well as reducing the number of interfaces. The network architecture of Figure 2 may also include a variety of application specific proxies having associated Intranet application servers including: a StarOE proxy for the StarOE application server 39 for handling authentication order entry/billing; an Inbox proxy for the Inbox application server 31, which functions as a container for completed reports, call detail data and marketing news messages, a Report Manager Proxy capable of communicating with a system- specific Report Manager server 32 for generating, managing and scheduling the transmission of customized reports including, for example: call usage analysis information provided from the StarODS server 33; network traffic analysis/monitor information provided from the Traffic view server 34; virtual data network alarms and performance reports provided by Broadband server 35; trouble tickets for switching, transmission and traffic faults provided by Service Inquiry server 36; and toll free routing information provided by Toll Free Network Manager server 37. As partially shown in Figure 2, it is understood that each Intranet server of suite 30 communicates with one or several consolidated network databases which include each customer's network management information and data. In the present invention the Services Inquiry server 36 includes communication with MCI's Customer Service Management legacy platform 40 (a) . Such network management and customer network data is additionally accessible by authorized MCI management personnel. As shown in Figure 2, other legacy platforms 40(b), 40(c) and 40(d) may also communicate individually with the Intranet servers for servicing specific transactions initiated at the client browser. The illustrated legacy platforms 40 (a) - (d) are illustrative only and it is understood other legacy platforms may be integrated into the network architecture illustrated in Figure 2 through an intermediate midrange server 30. Each of the individual proxies may be maintained on the dispatch server 26, the related application server, or a separate proxy server situated between the dispatch server 26 and the midrange server

-21-

SUBST1TUTE SHEET (RULE 26) 30. The relevant proxy waits for requests from an application client running on the customer's workstation 10 and then services the request, either by handling them internally or forwarding them to its associated Intranet application server 30. The proxies additionally receive appropriate responses back from an Intranet application server 30. Any data returned from the Intranet application server 30 is translated back to client format, and returned over the internet to the client workstation 10 via the Dispatch Server 26 and at one of the web servers in the DMZ Services cluster 24 and a secure sockets connection. When the resultant response header and trailing application specific data are sent back to the client browser from the proxy, the messages will cascade all the way back to the browser 14 in real time, limited only by the transmission latency speed of the network.

The networkMCI Interact middle tier software includes a communications component offering three (3) types of data transport mechanisms: 1) Synchronous; 2) Asynchronous; and 3) Bulk transfer. Synchronous transaction is used for situations in which data will be returned by the application server 40 quickly. Thus, a single TCP connection will be made and kept open until the full response has been retrieved.

Asynchronous transaction is supported generally for situations in which there may be a long delay in application server 40 response. Specifically, a proxy will accept a request from a customer or client 10 via an SSL connection and then respond to the client 10 with a unique identifier and close the socket connection. The client 10 may then poll repeatedly on a periodic basis until the response is ready. Each poll will occur on a new socket connection to the proxy, and the proxy will either respond with the resultant data or, respond that the request is still in progress. This will reduce the number of resource consuming TCP connections open at any time and permit a user to close their browser or disconnect a modem and return later to check for results.

Bulk transfer is generally intended for large data transfers and are unlimited in size. Bulk transfer permits cancellation during a transfer and allows the programmer to code resumption of a transfer at a later point in time.

Figure 5 is a diagram depicting the physical networkMCI Interact system architecture 10. As shown in Figure 5, the system is divided into three major architectural divisions including: 1) the customer workstation 20 which include those mechanisms enabling customer connection to the Secure web servers 24; 2) a secure network area 17, known as the DeMilitarized Zone "DMZ" set aside on MCI premises double firewalled between both the public Internet 25 and the MCI Intranet to prevent potentially hostile customer attacks; and, 3) the MCI Intranet Midrange Servers 30 and Legacy Mainframe Systems 40 which comprise the back end business logic applications.

As illustrated in Figure 5, the present invention includes a double or complex firewall system that creates a "demilitarized zone" (DMZ) between two firewalls 25a, 25b. In the preferred embodiment, one of the firewalls 29 includes port specific filtering routers, which may only connect with a designated port on a dispatch server within the DMZ. The dispatch

-23-

SUBSTΓΓUTE SHEET (RULE 26) server connects with an authentication server, and through a proxy firewall to the application servers. This ensures that even if a remote user ID and password are hijacked, the only access granted is to one of the web servers 24 or to intermediate data and privileges authorized for that user. Further, the hijacker may not directly connect to any enterprise server in the enterprise intranet, thus ensuring internal company system security and integrity. Even with a stolen password, the hijacker may not connect to other ports, root directories or applications within the enterprise system.

The DMZ acts as a double firewall for the enterprise intranet because the web servers located in the DMZ never store or compute actual customer sensitive data. The web servers only put the data into a form suitable for display by the customer's web browser. Since the DMZ web servers do not store customer data, there is a much smaller chance of any customer information being jeopardized in case of a security breach.

As previously described, the customer access mechanism is a client workstation 20 employing a Web browser 14 for providing the access to the networkMCI Interact system via the public Internet 15. When a subscriber connects to the networkMCI Interact Web site by entering the appropriate URL, a secure TCP/IP communications link 22 is established to one of several Web servers 24 located inside a first firewall 29a in the DMZ 17. Preferably at least two web servers are provided for redundancy and failover capability. In the preferred embodiment of the invention, the system employs SSL encryption so that communications in both directions between the subscriber and the networkMCI Interact system are secure.

In the preferred embodiment, all DMZ Secure Web servers 24 are preferably DEC 4100 systems having

Unix or NT-based operating systems for running services such as HTTPS, FTP, and Telnet over TCP/IP. The web servers may be interconnected by a fast Ethernet LAN running at 100 Mbit/sec or greater, preferably with the deployment of switches within the Ethernet LANs for improved bandwidth utilization. One such switching unit included as part of the network architecture is a HydraWEB™ unit 45, manufactured by HydraWEB Technologies, Inc., which provides the DMZ with a virtual IP address so that subscriber HTTPS requests received over the Internet will always be received. The Hydraweb unit 45 implements a load balancing algorithm enabling intelligent packet routing and providing optimal reliability and performance by guaranteeing accessibility to the "most available" server. It particularly monitors all aspects of web server health from CPU usage, to memory utilization, to available swap space so that Internet/Intranet networks can increase their hit rate and reduce Web server management costs. In this manner, resource utilization is maximized and bandwidth (throughput) is improved. It should be understood that a redundant Hydraweb unit may be implemented in a Hot/Standby configuration with heartbeat messaging between the two units (not shown) . Moreover, the networkMCI Interact system architecture affords web server scaling, both in vertical and

-25-

SUBST1TUTE SHEET (RULE 26) horizontal directions. Additionally, the architecture is such that new secure web servers 24 may be easily added as customer requirements and usage increases. The use of the HydraWEB™ enables better load distribution when needed to match performance requirements .

As shown in Figure 5, the most available Web server 24 receives subscriber HTTPS requests, for example, from the HydraWEB™ 45 over a connection 44a and generates the appropriate encrypted messages for routing the request to the appropriate MCI Intranet midrange web server over connection 44b, router 55 and connection 23. Via the Hydraweb unit 45, a TCP/IP connection 38 links the Secure Web server 24 with the MCI Intranet Dispatcher server 26.

Further as shown in the DMZ 17 is a second real time monitor ("RTM") server 52 having its own connection to the public Internet via a TCP/IP connection 48. As described herein, this RTM server provides real-time session management for subscribers of the networkMCI Interact Real Time Monitoring system. At least one additional TCP/IP connection 48 links the RTM Web server 52 with the MCI Intranet Dispatcher server 26. With more particularity, as further shown in

Figure 5, the networkMCI Interact physical architecture includes three routers: a first router 49 for routing encrypted messages from the Public Internet 15 to the HydraWeb 45 over a socket connection 44; a second router 55 for routing encrypted subscriber messages from a Secure Web server 24 to the Dispatcher server 26 located inside the second firewall 25b; and, a third router 65 for routing encrypted subscriber messages from the RTM Web server 52 to the Dispatcher server 26 inside the second firewall. Although not shown, each of the routers 55, 65 may additionally route signals through a series of other routers before eventually being routed to the nMCI Interact Dispatcher server 26. In operation, each of the Secure servers 24 function to decrypt the client message, preferably via the SSL implementation, and unwrap the session key and verify the users session from the COUser object authenticated at Logon.

After establishing that the request has come from a valid user and mapping the request to its associated session, the Secure Web servers 24 will re- encrypt the request using symmetric RSA encryption and forward it over a second secure socket connection 23 to the dispatch server 26 inside the enterprise Intranet. As described herein, the data architecture component of the networkMCI Interact reporting system is focused on the presentation of real time (un-priced) call detail data, such as provided by MCI's TrafficView Server 34, and priced call detail data and reports, such as provided by MCI's StarODS Server 33 in a variety of user selected formats.

The Infrastructure component of the nMCI Reporting system includes means for providing secure communications regardless of the data content being communicated. The nMCI Interact system security infrastructure includes: 1) authentication, including the use of passwords and digital certificates; 2) public key encryption, such as employed by a secure

-27-

SUBSTTTUTE SHEET (RULE 26) sockets layer (SSL) encryption protocol; 3) firewalls, such as described above with reference to the network architecture component; and 4) non- repudiation techniques to guarantee that a message originating from a source is the actual identified sender. One technique employed to combat repudiation includes use of an audit trail with electronically signed one-way message digests included with each transaction. Another component of the nMCI Interact infrastructure includes order entry, which is supported by the StarOE server 49. The general categories of features to be ordered include: 1) Priced Reporting; 2) Real-time reporting; 3) Priced Call Detail; 4) Real Time Call Detail; 5) Broadband SNMP Alarming; 6) Broadband Reports; 7) Inbound RTM; 8) Outbound RTM; 9) Toll Free Network Manager; and 10) Call Manager. The order entry functionality is extended to additionally support 11) Event Monitor; 12) Service Inquiry; 13) Outbound Network Manager; 14) Portfolio; and, 15) Client View.

The Self -monitoring infrastructure component for nMCI Interact is the employment of mid- range servers that support SNMP alerts at the hardware level. In addition, all software processes must generate alerts based on process health, connectivity, and availability of resources (e.g., disk usage, CPU utilization, database availability) .

The Metrics infrastructure component for nMCI Interact is the employment of means to monitor throughput and volumes at the Web servers, dispatcher server, application proxies and mid- range servers. Metrics monitoring helps in the determination of hardware and network growth.

-28-

SUBST1TUTE SHEET (RULE 26) To provide the areas of functionality described above, the client tier 10 is organized into a component architecture, with each component providing one of the areas of functionality. The client -tier software is organized into a "component" architecture supporting such applications as inbox fetch and inbox management, report viewer and report requestor, TFNM, Event Monitor, Broadband, Real -Time Monitor, and system administration applications. Further functionality integrated into the software architecture includes applications such as Outbound Network Manager, Call Manager, Service Inquiry and Client View. The functionality of these applications are further enhanced by the adoption of: a CGI program interface to networkMCI Interact that allows HTML and CGI -based systems to access a subset of NMCI Interacts middle - tier services; a Java interface for non-NMCI Interacts Java applets; and, a Common Object Request Broker Architecture ("CORBA") interface to nMCI Interact which allows Web- enabled systems built in C++ and Smalltalk, etc. to use the middle tier services of the network. Implementation of these added systems includes the employment of digital signature/client certificates technology and Java objects. Particularly, the use of a distributed object technology such as provided by CORBA provides increased functionality.

All reporting is provided through a Report Requestor GUI application interface which support spreadsheet, a variety of graph and chart type, or both simultaneously. For example, the spreadsheet presentation allows for sorting by any arbitrary set of columns . The report viewer may also be launched from the inbox when a report is selected.

A common database may be maintained to hold the common configuration data which can be used by the GUI applications and by the mid- range servers. Such common data will include but not be limited to: customer security profiles, billing hierarchies for each customer, general reference data (states, NPA's, Country codes), and customer specific pick lists: e.g., ANI's, calling cards, etc.. An MCI Internet StarOE server will manage the data base for the common configuration of data.

Report management related data is also generated which includes 1) report profiles defining the types of reports that are available, fields for the reports, default sort options and customizations allowed; and 2) report requests defining customer specific report requests including report type, report name, scheduling criteria, and subtotal fields. This type of data will be resident in an Inbox server database and managed by the Inbox server.

By associating each set of report data which is downloaded via the inbox with a small report description object, it is possible to present most reports without report- specific presentation code (the report- specific code is in the construction of the description object). These description objects are referred to as "metadata," or "data about data." At one level, they function like the catalog in a relational database, describing each row of a result set returned from the middle tier as an ordered collection of columns. Each column has a data type, a name, and a desired display format, etc. Column descriptive information will be stored in an object, and the entire result set will be described by a list of these objects, one for each column, to allow for a standard viewer to present the result set, with labeled columns. Nesting these descriptions within one another allows for breaks and subtotaling at an arbitrary number of levels.

In the TrafficView System ("TVS") of the present invention, the customer workstation 10 is equipped with a Web browser for remotely requesting reports of unpriced call detail and statistical data and/or real time access to monitor the state of special service call networks from the traffic view server 34, as shown in Figure 2. This report request process will be described with respect to Figure 6 which is a high- level description of the TVS system 100 integrated within the nMCI Interact architecture 200.

With greater particularity, an overall view of the TVS system 100 of the present invention is discussed with reference to Fig. 6. As shown in Fig. 6, the architecture basically starts with a plurality of switching means, such as a number of switches represented by switch 102, in the telecommunications network. Associated with each switch, for example, switch 102, is an Adjunct Processor (AP) 104. One of the main functions of the AP is to perform billing. For each call routed through switch 102, AP 104 generates a Call Detail Record (CDR) . The CDR is routed to an Operator Services System (OSS) network 106, which otherwise may be referred to as a X.25 network. Network 106 in turn is connected to a series of processors commonly referred to as Central Retransmitters (CR) 108. The outputs of the respective CRs 108 are provided to a Fiber Distributed Data Interface (FDDI) ring 110. The output of FDDI ring 110 in turn is connected to a MCI Traffic Statistics (MTS) system 112, which is situated in a platform to which another system, namely a DAP Traffic Statistics (DTS) , may also reside.

DAP refers to a data access point such as DAP 114 shown in the dotted box of Fig. 6. In particular, DAP 114 is a processor system that provides routing information to switch 102. In addition, DAP 114 also provides information to the MTS (or the combination DTS/MTS system) for the traffic statistics monitoring mentioned in the background of the invention section, supra. A more detailed discussion of a DAP and the DTS is given in the aforenoted issued U.S. Patent

Application No. 5,537,611 assigned to the same assignee as the present invention, and whose disclosure is incorporated by reference herein. For the instant invention, it suffices to note that the platform to which both DTS and MTS reside is referred to only as the MTS system 112.

MTS system 112 is a system for counting the number of calls through the various switches. For the telecommunications network of the instant invention, calls are understood to be special service calls including but not limited to 800/8xx, 900 and "Vnet." For the discussion of Fig. 6, it is assumed that MTS system 112 counts only 800/900 calls, or traffic.

On a periodic basis, MTS system 112 provides statistics data, also referred to as rolled up statistics, via line 115 to a TrafficView system (TVS) 116. As shown, MTS system 112 also receives orders, via line 118, from TVS system 116. For the embodiment of Fig. 6, rolled up statistics are output from MTS system 112 to TVS system 116 at predetermined time intervals such as every 60 minutes. It should however be understood that the time intervals in which statistics are rolled up from MTS system 112 to TVS system 116 may be varied. Such periodic rolling up of statistics enables the system to provide periodic outputs to subscribers who request only periodic reports. In instances where a subscriber requests the real time option, the statistics are rolled up from MTS system 112 to TVS system 116 in real time so that a subscriber can access TVS system 116 to monitor in real time the operation of the network via the public Internet via second RTM server 52 (Figure 2) . The process by which rolled up statistics are periodically provided from MTS system 112 to TVS system 116 basically occurs as follows. For a given time period, for example every hour, statistics for customers (subscribers) who have subscribed to the service of the present invention system are accumulated and a customer rolled up peg count message is produced. For the embodiment of Fig. 6, the accumulations are for hourly intervals, with the understanding that future intervals may be set to any time period, for example 20 minute increments. A MTS stats compiler (to be discussed with reference to Fig. 8) writes the customer peg count messages into a "TRAFFICVIEW" server queue. In the case of real time transfer of statistics from MTS system 112 to TVS system 116, the MTS stats compiler writes the customer peg count message directly to TVS system 116, which may be partitioned into two portions, one for receiving the rolled up statistics that are fed periodically while the other for receiving in real time the data from MTS system 112. Real time access is gained through the RTM system 117, as will be described.

For the Fig. 6 embodiment, for example, rolled up statistics corresponding to an 800 number for a given subscriber may include the following data: that 500 call attempts were made to that 800 number of the subscriber, that 400 of those calls were completed, 50 were not completed (incompletes) and 50 of those calls were blocked. Additional rolled up statistics data may include the destination terminations and the originating Numbering Plan Area (NPA) of the calls. These statistics are stored as records in the TVS system 116. In further view of Fig. 6, the TVS system 116 comprises a number of processors represented for example by a main frame host system 119. Connected to processor system 119 is a storage means, for example a database system 120 which comprises a plurality of memory disks or other storage mechanisms. A more detailed discussion of the hardware components of TVS system 116 and its database system is given, infra. As further shown in Figure 6, there are a number of systems communicatively coupled to TVS system 116. In particular, connected to TVS system 116 to receive its outputs, e.g., reports, via line 122, is a first data distribution system, referred to as "MCI MAIL" host 124. Mail host system 124 is a proprietary system of the MCI Communications Corporation (MCI) and is capable of sending out E-Mails, via line 126, to a conventional PC equipped with a modem and appropriate communications software. Mail host 124 may further distribute reports, or data files, from TVS system 116 to a fax machine (not shown) or as a hard copy message, to a printer (not shown) .

Further, in accordance with the invention there is provided a TCP/IP connection 125 for connecting the TVS system 116 with nMCI Interact' s web/Internet based reporting system, referred to herein as StarWRS system 300, for providing customers with their priced and unpriced telecommunications call detail data reports, as will be described in further detail herein with regard to Figure 7.

Another TCP/IP connection 123 from the RTM process system 117 of the TVS system 116, to the RTM web server 52 to provide for the real time traffic monitoring capability via the Internet. Thus, the various subscribers to the RTM service, represented by customer workstation 10 equipped with a Web browser, can monitor in real time, or substantially real time, the operation of the network as it relates to the calls directed to that subscriber's special service call number (s) . Thus, instead of viewing a past event, using the RTM system 117, a subscriber may retrieve web pages comprising real time data and statistics that present an ongoing picture relating to any, or all, of his special service call numbers. For example, the subscriber can see in real time how many calls are being attempted minute by minute, how many calls are being allowed through the network, how many calls are incompletes, how many calls are blocked, etc. This ability to monitor the operation of the network gives the subscriber the ability to decide in real time the specific actions that need to be taken. For instance, if there is an abnormal number of incompletes for a given period, the subscriber can look at the specific call records that made up those incomplete calls. If needed, the subscriber can request the management of the network to restructure the network so as to reroute the incoming calls of the subscriber to different locations where they may better be handled. The different modules of the RTM system are shown and described herein with reference to Fig. 13.

Also connected to TVS server 116 is a Calling Area Database (CADB) 138 which periodically provides TVS, and, more specifically, database 120 of TVS system 116, mapping data to correlate NPAs to the different states and localities within the states, and country codes to the different countries for further adding call details for the CDRs. Also shown connected to TVS system 116 is a

Circuit Order Management System (COMS) 140 whose function, for the Fig. 1 embodiment, is to provide a file of maps of the service locations, and the ncodes to switches, trunks, or regular telephone numbers. Further connected to TVS system 116 is a

Corporate Order Entry (CORE) system 142 which receives its input from subscribers via a CORE system data entry system such as a workstation or PC 144. In particular, a subscriber can input instructions to CORE system 142 which in turn inputs the instructions as order entries via line 146 to TVS system 116. Some of the data provided by the subscribers to CORE system 142 may include the type of reports the subscribers like to receive, the number of reports the subscribers want, the frequency and how the reports should be sent, and where the reports should be delivered to. With respect to one method in which reports may be delivered, the CORE system 142 sends instructions to a "MCI MAIL" order entry system 148, which in turn forwards the instructions to mail host system 124. Consequently, a subscriber may receive data or reports in a E-Mail format from the TVS system 116. The order entry function may be performed by a StarOE server 26, as will be described in greater detail herein.

The transmission of data between APs, such as AP 104, and MTS system 112 is described with reference to Fig. 8. As shown in Figure 8, 800 and 900 CDRs are collected from APs 104 and routed to central retransmitters 108, which are protocol conversion processors. In essence, CRs 108 convert the data from APs 104, which are VAX OSI Transport System (VOTS) messages that are delivered on the X.25 network, into a multi-cast M messages. (OSI is Open System Interconnection) .

The MTS system 112 collects CDRs from all APs. The CDRs are collected and buffered at each AP, and sent to MTS system 112 using the OSI class 4 Transport Service (OSI TP4) . The CDRs (per buffer) are received at MTS system 112 by a process called the AP OSI communication manager, or AP OSI CM. The AP OSI CM process is responsible for communication between MTS system 112 and the APs. This process runs simultaneously on all of the processors (to be discussed subsequently) of MTS system 112 where each CM receives CDRs from a specific number of APs over OSI transport connections on the OSS NET. This involves establishing and maintaining sessions to receive 800/900 number CDRs from the APs. As each CDR buffer is received from the APs, it is forwarded to the application being run on the processors of MTS system 112. This is done by transferring each buffer (of

-37-

SUBST1TUTE SHEET (RULE 26) CDRs) to an Ethernet transmit process, also running on the MTS communication servers. The Ethernet transmit process then uses the Ethernet multi-cast protocol to send the buffer to the application running in MTS system 112.

In terms of the external interfaces, the AP OSI CM process receives CDR messages from the APs by establishing a transport connection via the Packet Net System Interface (PSI) , which is used to establish Shared Virtual Circuits (SVCs) over the OSSI NET 106.

The CM interfaces to the Ethernet transmit process over a Virtual Memory System (VMS) mailbox where the CM puts the AP CDR message to be multi-casted on the MTS Ian. The AP OSI CM maintains a VMS global section where various statuses and performance statistics are kept and updated.

Each AP, as was discussed earlier, is collocated with a switch 102. The AP receives all CDRs generated by switch 102. The records generated by a switch can be in many different categories: for example Call Detail Records (CDRs) , Private Network Records (PNRs) , Operator Services Records (OSRs) , Private Network Operator Services Records (POSRs) , and Switch Event Records (SCRs) . For the understanding of the instant invention as exemplified by the embodiment of Fig. 6, the only records that are forwarded to MTS system 112 by each AP 104 are the originating switch 800 and 900 CDRs. A filtering algorithm is employed at each AP for filtering the appropriate CDRs. In sum, Transport Service Data Units (TSDUs) are received by the AP OSI CM. Each of the TSDUs includes CDRs from the AP in a format whereby it includes a AP MTS header which may be for example 16 bytes long. The AP MTS header may include a switch ID identifying the switch where the CDR is from, the CDR count and a filler for filling unused bytes. The AP MTS header is followed by up to 23 CDRs, each of which is 64 bytes long. These multi-cast 800 and 900 CDRs are forwarded by CRs 108 to FDDI ring 110.

The process performed by FDDI 110 is as follows. The FDDI 110 receives the CDRs for MTS 112, and buffers Application Data Field (ADF) message pairs, fraud messages and call detail records from the CRs

108. These CDR messages are put in a queue 152 for the MTS peg counter 154. The CDRs from queue 152 are then forwarded to a MTS peg counter 154 in MTS system 112. The outputs from MTS peg counter 154 are provided to a MTS customer service database 160 and also MTS peg counts buffer 156. The process under which MTS peg counter 154 operates is as follows:

First, the MTS peg counter enhances the call detail record by performing data look-ups on the feature group C, virtual trunk, direct termination overflow and international SAC databases. For the received call records, the MTS peg counter does a database look-up using the pre- translated dialed digits as the key. The look-up will yield the virtual memory address of the necessary peg count storage areas for each 800 number, and a list of counting services to provide for the CDR. There is a linked list header for each possible kind of peg count that an 800 number can have. MTS peg counts are stored as a virtual memory address of a linked list header. There are two linked list headers per 800 number and peg count type -- one for current peg count statistics and the other for the inactive peg count statistics reporting by an MTS statistics compiler 158. Actual peg counts are stored in linked lists, indexed by hour. Call record time points are normalized to Universal Coordinated Time (UCT) based on the switch/AP time. Because of the call record transfer delay between the switch, AP and MTS, MTS needs to store peg counts for multiple hourly intervals for each 800 number. Hourly intervals are sorted in reverse chronological order to expedite peg count storage searches. The peg counter continues to store peg counts for each hourly interval for a configurable interval after the reporting interval. Assuming the initial setting to this configurable interval is 10 minutes, the MTS peg counter continues to store peg counts for each hourly interval unit 10 minutes after the reporting interval is over.

Dynamic allocation is done by the MTS peg counter with a "Doggie Bag" for temporary storage of incoming call records that require a database update before processing. When an 800 number or a termination is not found, the call record is stored in the MTS Doggie Bag. The MTS peg counter requests the database lock, with asynchronous notification through an AST routine. When the lock is granted the AST routine sets a flag indicating the lock is granted. After each buffer of incoming call records have been processed, the MTS peg counter makes the necessary database updates, then processes the record normally, bumping up the appropriate 800 number peg counts. MTS total call counts provide a summary of total minutes and call completions broken down by the 800 number. These counts can be rolled up to TVS

-40-

SUBST1TUTE SHEET (RULE 26) system 116 to provide total minutes and the call completion ratio by customer ID. Total counts include:

Total Completions Total Call Duration

Total Attempts

Total Switch Controlled Calls (No Action Code Received) Total NCS Blocked (Action Code 30 Received)

Total NCS Rejected (NCS Failure Action Code Received)

Total Network Blocked (All Routes Busy) Total Supp Code Blocked

Total Out of Band Blocked

The call completion ratio can be determined for a given 800 number and rolled up under the customer ID to provide call completion statistics, and total call minutes on a customer by customer basis.

800 Call Completion Ratio = Completions

Attempts - (Switch Controls + NCS Blocks + NCS Failures + ARBs)

MTS NPA counts are compiled and stored hourly as a block of 160 NPAs . The NPA counts include:

Originating NPA

Total Attempts per NPA

Total Completed Calls per NPA

Total Calls Not Delivered (Blocked) per NPA • Total Attempts for International

Originations

Total Completed Calls for International

Originations

Total Calls Not Delivered (Blocked) for International Originations MTS NPA-NXX counts are compiled and stored hourly as a block of 160 NPAs with their associated NXXs. The NPA-NXX counts include:

Attempts from International Originations

For each Originating NPA... Attempts for each unknown NXX (for FG-C Originations)

For each NXX of Origination Attempts from that NXX

MTS counts for an 800 number are broken down by termination and compiled hourly. Call statistics for terminations include:

Termination Type Termination Address Total Completions Total Call Duration Call Disposition

Call dispositions indicate the cause of an incomplete call. Terminating call dispositions include: Total Short Calls. Short calls are calls lasting less than 4 switch ticks with no answer detected. This typically indicates a busy condition. (Each Switch tick is presumed to be 3 seconds) .

Total Didn't Wait. Didn't Wait calls are calls lasting from 4 through 8 switch ticks with no answer detected. This typically indicates a call is not answered within 4 ringing cycles.

Total Didn't Answer. Didn't Answer calls are calls lasting beyond 8 switch ticks with no answer detected. This typically indicates a call is not answered within 6 ringing cycles. Every hour, the MTS peg counter wakes up MTS statistics compiler 158, which then performs sequential traversal of MTS customer service database 160 to generate statistics for every 800 number. The MTS service type (a field in the MTS customer service record) informs the statistics compiler which statistics are being kept for this 800 number (i.e. 800 totals, termination counts, NPA counts, NPA-NXX Counts) . A data driven MTS statistics compiler records the services a particular 800 number is registered for; including reporting interval (hourly) , statistics destination (MTS server) , priority (real time, non-real time) , and time offset (usually zero) for statistics delivery.

MTS statistics compiler 158 reads MTS customer service database 160 in priority order, so statistics are processed for all real time 800 numbers first, followed by statistics for the non- real time 800 numbers. The priority feature allows MCI 800 "TRAFFICVIEW" subscribers who are signed up for hourly data to gather their data first, while subscribers who only want daily, weekly or monthly reports from the TV server of TVS system 116 will get their data later. The TVS system may also be referred to as "TARS" (Traffic Analysis Reporting System) server.

For each 800 number found in the MTS customer service database 160, MTS statistics compiler 158 finds the matching peg counts in memory and constructs an "MTS Peg Counts Message for an 800/900 Number." A MTS send out routine is invoked to send each message to TVS system 116. The "MTS Peg Counts Message for an 800/900 Number" comprises a fixed message part and a variable number of optional parameters. The fixed message part identifies the 800/900 number for which the statistics are being reported, the time interval the statistics are from and other key information. The optional parameters that are reported for a given 800 number depend upon the service identified for the 800 number in MTS database 160. The following table identifies the service types and their corresponding optional parameters:

Service Type

Optional Parameters in B.l Message

1. Total Service EF - MTS Totals Counts

2. Termination Service EF - MTS Totals Counts

EC - MTS Counts by Termination

Standard Service EF - MTS Totals Counts

EE - MTS Counts by NPA

EC - MTS Counts by Termination

4. Demographic Service EF - MTS Totals Counts

EE - MTS Counts by NPA

ED - MTS Counts by NPA-NXX EC - MTS Counts by Termination

MTS statistics compiler 158 does not begin reporting on an hour until a configurable interval (default 5 minutes) after the hour. As each statistics message for a given hour is constructed and sent, MTS statistics compiler 158 frees any memory used to hold peg counts for the current

800/900 number. This memory is returned to a common pool of free memory, available for use by the peg counter as needed.

After sending all of the required statistics messages for a given hour, MTS statistics compiler 158 sends an "MTS Switch/AP Report Status Checkpoint Message" to the server. This message serves two purposes: (1) it informs TVS system 116 that all messages for an interval have been sent; and (2) it shows the TVS system 116 how accurate the 800/900 number data it received is, by showing how far behind each Switch/AP is in sending statistics messages to the MTS.

Ideally, the "Last Call Record Disconnect" time point for each Switch/AP is sent after the end time of the hourly interval . That means that the Switch/AP is keeping up with traffic levels, but does not necessarily mean that the data reported for an 800 number is entirely complete. There is still the possibility that long duration calls have not disconnected, and therefore will not be reported until the next hour.

Also after generating the 800 number statistics messages, MTS statistics compiler 158 generates an "MTS Network Statistics Message." This message is not sent to TVS system 116 but is only written to the test files or the test multi-cast address. The message is useful for network management purposes, for gauging traffic levels throughout the day and for determining the transition mix at intelligent network platforms such as Network Control System (NCS) .

After all statistics messages are generated for an hour, MTS statistics compiler 158 hibernates, waiting to be awakened again by the MTS peg counter 154 for the next hour. Note that although "hourly interval" has been described as the basis on which MTS statistics compiler 158 runs, in actuality, the interval is completely configurable to be any reasonable time period. In fact, the interval for MTS statistics compiler 158 may be set to five minute intervals such that statistics messages are generated every five minutes and forwarded to MTS system 112. By shortening the "interval" to such a short time period, the statistics provided to TVS system 116, and therefore to RTM system 117 (Figure 6) through which a subscriber can log on, becomes substantially in real time. For those subscribers who continue to want only periodic reports or updates, the five minute interval statistics can be summed to achieve the desired duration. For example, if a subscriber only wants hourly updates, statistics for 12 consecutive five minute intervals are summed to provide the hourly updates .

Fig. 9 provides a more comprehensive view of the different operations of MTS system 112, and the relation of those operations to the exchange of information between MTS system 112 and TVS system 116. In particular, as shown in Fig. 9, the hourly peg counts, stored in buffer 162 from MTS statistics compiler 158, are monitored in Monitor AP Traffic process 164. Process 164 is responsible for sending alarms to the Network Management Interface (NMI) and the Local Support Element (LSE) whenever an AP fails to send messages to MTS system 112 within a pre- configured time period. For the embodiment of this invention, the time period is assumed to have a default setting of 5 minutes. This process continues to send alarms every 5 minutes as long as no messages are received from an AP. Also with respect to the instant embodiment, the first two alarm messages are assumed to be sent as warnings. Further assume the third alarm message is sent to indicate that there is in fact an error.

Data is exchanged from MTS database 160 to a Transaction Processing Library (TPL) 166. The TPL 166 is a centralized, table driven set of software routines that are callable by any process for modifying or searching through its associated memory or disk database 168. TPL 166 is called through a TPL interface by the MTS administration processes. The MTS Statistics compiler 158 and peg counter 154 call hash routines directly to perform database searches. All other functions performed by those processes and all of the other processes access TPL 166 directly through a TPL controller. The TPL 166 also allows a transaction to back out from the database when any part of the transaction fails.

-47-

SUBST1TUTE SHEET (RULE 26) With respect to MTS system 112, TPL 166 maintains these databases:

Customer Definition,

Monitored Customer,

Termination by 800/900 number,

Termination counts by originating

NPA,

MTS Customer Service,

MTS 800 Service Types,

MTS Network Service Types,

MTS Destinations,

MTS Network Service.

TLP 166 maintains these lists

Real time customer list; and Non- real time customer list.

TPL 166 maintains these arrays:

Switch/ARU Array

DAP Transaction Server Array

NPA/Location descriptions

TPL 166 maintains MTS control block.

For MTS system 112, among other functions, TPL 166 supports the following:

Add an 800/900 number

Delete an 800/900 number

Search the Customer Definition file for a record Add a termination to an 800/900 number

Delete a termination for an 800/900 number

Search the "Termination of an 800/900 number" file for a record

Update a "Termination of an 800/900 number" record Add a switch/ARU

Delete a switch/ARU

Add a transaction server

Delete a transaction server

Initialize TPL

Search the Termination by 800/900 number file (TRMN00)

Update an NPA

Update a switch

Search for a switch

Update the MTS control block settings

Update an MTS monitored 800/900 number

Search for an MTS monitored 800/900 number

Add an MTS feature group C record

Delete an MTS feature group C record

Search for an MTS feature group C record

In addition to corresponding with MTS database 160 and its associated disk database 168, TPL 166 also corresponds with an order entry process, such as that represented by line 146 (Fig. 6) performed by CORE system 142. Specifically, order entry process 146 is responsible for taking MTS transactions received from the TVS system 116, and applying the appropriate updates to MTS database 120. As shown in Fig. 9, the TVS transactions are received from the TVS server process 170 via a TVS server output queue 172. The order entry process 146 then invokes an application from TPL 166 to execute the transaction. A response is received from TPL 166 and a MTS transaction response message is constructed and sent back to TVS server interface 170 via a TVS server input queue 174.

The MTS/TVS server interface process 170 is responsible for detecting link outages between the MTS system 112 and the MTS server. Upon link failure, MTS server interface 170 archives MTS

-49-

SUBST1TUTE SHEET (RULE 26) statistics messages in a safe stored queue. The archive messages are sent in a First In First Out (FIFO) order when the link resumes normal operation. If failover occurs during statistics compilation on a primary MTS node, MTS/TVS server interface process 170 begins to read messages from MTS statistics compiler 158 and send the messages to MTS system 112. If failover occurs when statistics compilation is complete, there should be little or no data in the MTS/TVS server queue for MTS server interface process 170 to read.

The MTS/TVS server interface 170 also is responsible for receiving MTS transaction messages from the server in MTS system 112. Incoming MTS transaction messages are placed in TVS server output queue 172 for the order entry process 146 to read and process .

Further with respect to Fig. 9, note that the TVS server input queue 174 has provided as one of its inputs MTS statistics messages from a MTS send out process 176. The MTS send out process 176 is a central routine that sends out all MTS output messages. MTS send out process 176 is able to send messages to the TVS server, multi-cast to a MTS display subsystem (not shown) and to MTS test output files 178. Moreover, as was mentioned previously, any failover messages are sent via MTS send out process 176 to a MTS failover queue 180.

The different types of MTS statistics are listed hereinbelow.

MTS incoming statistics: The number of call detail records received broken down by, message type, messages with invalid transaction IDs, and counts of the message buffers that are dropped. (Each buffer has a sequence number. When a buffer is received out of sequence this count is incremented) Total current MTS TPS, MTS Monitored 800/900 numbers TPS, Peak MTS TPS since monitoring was initiated,

A real time bar graph showing the current MTS TPS, and

A count of the number of TVS server transactions received, a count of how many of them caused failure responses, and a count of how many of them caused success responses .

MTS system statistics:

Total current MTS TPS; MTS monitored number TPS; Output messages sent to TVS server; Output messages sent to NMI;

Number of MTS monitored numbers broken down by service subscription: 800 totals counts 800 termination counts - 800 NPA counts

800 NPA/NXX counts How much memory has been allocated, used, and is available for each of the databases, files and peg count areas.

MTS outgoing statistics:

Output configuration:

800 number and termination dynamic allocation flag

Termination dynamic allocation only flag

Send output to TVS server

Send output to MDS - Send output to test output file Send output to remaining 5 alternate destinations

Output to the TVS server broken down by message type,

Dynamic allocation alarms broken down by database type.

MTS current peg counts

Monitored 800/900 numbers

Termination for a specific 800/900 number

NXX counts for a specific 800/900 number

AP Statistics counts

Network statistics counts

With reference to Fig. 10, the operation of TVS system 116, as represented by its TVS server, is discussed. As shown, TVS server 116 interfaces with a number of systems, among which include MTS system 112. The interfacing between MTS system 112 and TVS server 116 is of import, and a discussion thereof is given hereinafter.

In particular, the MTS and TVS systems, more specifically their respective servers, exchange information via a pair of communications managers (CM) . These are the MTS send CM and TVS receive CM. The processes performed by the two communications managers implement a client/server arrangement between the MTS and the TVS systems. Together, the two communications managers (processes) provide a bidirectional data transfer path between the MTS and TVS systems. Each CM has an input and output queue. A message written to the input queue of one CM is

-52-

SUBST1TUTE SHEET (RULE 26) transmitted to the other CM and placed in that CM's output queue.

The MTS send CM accesses the client in the client/server arrangement, as it is responsible for establishing a transport connection between the two processes. The TVS receive CM acts as the server, as it accepts transport connections from one or more MTS send CM clients.

The communication mechanism between the MTS and TVS systems is via an OSI class 4 (or OSI TP4) , an error detection and recovery transport server that provides reliable full -duplex, connection oriented data transfer between OSI- compliant systems. For the connection, VLTS is used.

There are two data flows between the two systems, namely a call completion statistics and call detail data flow from the MTS to TVS system, and administrative control messages flow from the TVS to MTS system. The call completion statistics messages and call detail messages make up the great bulk of the traffic. Since there is a large volume of call statistics and call detail to be quickly transferred and the destination queue on the TVS system is of finite size, a sliding window protocol is used on top of the transport layer to allow rapid data transfer and to avoid overfilling the output queue of the TVS server. The administrative control message volume and timing requirements are such that a windowing mechanism is not employed from the TVS CM to the MTS CM.

Thus, the MTS send CM functions as follows : 1. A transport connection is established to the TVS receive CM.

2. An asynchronous read is posted on the transport connection.

3. A series of asynchronous reads, determined by the window size, is posted on the input queue.

4. When a message is placed in the input queue, it is removed from the queue and written to the transport connection.

5. When an acknowledgment message is received from the TVS receive CM over the transport connection, another read is posted to the input queue and the read is reposted to the transport connection.

6. When an order entry message is received from the TVS receive CM, it is placed in the output queue and another read is posted on the transport connection.

The TVS receive CM functions as follows:

1. The receive CM accepts a transport connection from the send CM, and posts an asynchronous read to the connection.

2. An asynchronous read is posted to the input queue.

3. Messages are read from the transport connection, placed in the output queue, and an acknowledgement message is written back to the transport connection.

4. Messages are read from the input queue and written to the transport connection.

Both CMs keep link status information and transaction peg counts in a global section. A monitor program is supplied with each CM to map to this global section and display the status and transaction information.

As shown in Figure 10, the server of MTS system 112 sends a plurality of MTS messages to the server of TVS system 116 via the MTS Message line 182. Specifically, for the instant embodiment, the MTS server provides 800/900 call dispositions and call detail statistics to the TVS server. The following are the type of call dispositions sent: total short calls (including busy calls) , total did not wait calls, and total did not answer calls. The following call detail statistics are extracted from the switch call record information elements: total completions (answered calls) , total call duration (call minutes), total attempts, totals by terminating address, totals by NPA, totals by NPA- NXX, total switch controlled blocks, total network block calls. The following noninclusive information for

Enhanced Call Detail Records (ECDR) are also sent from the MTS system 112 to TVS system 116 in a steady stream: dialed number, calling number, output digits, originating switch, originating trunk, call origination time (TP1) , connect time (TP3) , answer time (TP6) , disconnect time (DP7) , call duration, ring duration, originating MPA, disposition, intended termination type/address, actual termination type/address, corporate ID, origination country code, originating port ID. In addition to providing call details to TVS system 116, MTS system 112 also sends messages to TVS system 116 via line 182. Some of these messages may include a message that the system is falling over from one node to another. It could also be a response message to an order entry message that was sent to the TVS system 116 by CORE system 142. It could further be a check point message sent at the end of every hour after the MTS server has sent all of the' statistics, and that those statistics are indeed all of the statistics to be received from the past hour.

A second link connecting MTS system 112 and TVS system 116 is a MTS order entry message line, designated 184. This is when the TVS system has received an order from CORE system 142, and the TVS server has to send a message to the MTS server to instruct MTS system 112 to gather the data

-56-

SUBST1TUTE SHEET (RULE 26) required, for example, for a specific 800 number. In other words, the message from the TVS server requests the MTS server to capture data for the specific 800 number at a specific level, of which there are four for the instant invention.

The first level is a capture statistics only level which provides information on call attempts. It is a summary information level that indicates, for example, that there are these many calls, these many calls were completed, these many calls were incomplete calls, and these many calls were blocked. The second level provides all of the information provided in the first level, and information relating to the terminations where the completed calls went. The third level is a combination of the first and second levels and the addition of the originating NPA. The fourth level includes the information of all of the first to third levels plus the NXX (exchange code) for origination.

A third link 186 that connects the MTS server to the TVS server is the MTS failover response message line. This is the connection used by the MTS system 112 to inform TVS system 116 that there has been a failover from a first processor of MTS system 112 to its backup processor. In essence, MTS system 112 in actuality comprises two processors that are mirror images of each other. Thus, if one of the processors breaks down, the other processor takes over. Link 186 provides an indication from the MTS system 112 to the TVS system 116 that the backup system has taken over. Also communicating with the TVS server is the mail host 124. As was discussed previously, mail host 124 in essence is a system through which the reports from TVS system 16 may be sent to the different subscribers, e.g., via E-Mail, fax or as hard copies. A request for mail is sent by mail host 124 to the TVS server via line 188.

The Circuit Availability Database (CADB) 138 is additionally connected to the TVS server by means of line 192. In essence, CADB 138 provides the TV server a file on a periodic basis that includes information which allows the TV server to map the NPAs to states, NPNX to cities and other localities within the states. The file also provides mapping information to the TVS server to map country codes to country names, for example 144 being representative of the United Kingdom. It is this information from CADB 138 that the TVS server uses for outputing reports that provides answers to the subscriber on where calls to his special service call number come from.

Also shown connecting CADB 138 to the TVS server is a dotted line 194 which in Fig. 10 represents a trigger to indicate that something has happened. For example, line 194 indicates that the file from CADB 138 has arrived at the TVS server and that the TVS server needs to process it.

The CORE system 142 is connected to the TVS server of TVS system 116 via lines 196, 198 and 200. Line 198 represents a customer information line through which files containing orders for reports, or orders to turn off reports as the case may be, are provided from CORE system 142 to the TVS server. Line 196 is a trigger that shows that a CORE file has arrived and that the TVS server should begin to process it. Line 200, on the other hand, is a CORE error message line from the TVS server to CORE system 142. This line is used by the TVS server to transmit to CORE system 142 an indication that a record of a file being processed by the TVS server has been rejected. For example, the TVS server may reject a record because it has an incorrect address or does not have any phone number with it.

In sum, the interaction between TVS system 116 and CORE system 142 is as follows. A file is sent from CORE system 142 to TVS system 116. A trigger is then sent by CORE system 142 to the TVS server to inform the latter that the file has arrived. The TVS server then processes the file, looks for any error, and if an error is found, sends a message back to CORE system 142 to inform it of the error. At approximately the same time, the order entry information is sent by the TVS server to MTS system 112 via line 184.

The TVS server also interacts with Circuit Order Management System (COMS) 140. It does so via lines 202 and 204. COMS system 140, in essence, provides an ncode or service location data to the TVS server via line 202. An ncode is an eight digit character, the first character of which being always N and the remaining seven characters being always numbers. It is also referred to as a service location by which a subscriber can determine the termination point of a call. For example, when a subscriber sees a bill for an 800 number, he usually

-59-

SUBST1TUTE SHEET (RULE 26) does not see the termination point from which the call originates. Rather, he will see that his 800 number (for example N 555-1111) had received so many call attempts. The termination report provided to a subscriber allows the subscriber to compare the report with his invoice for any discrepancies. For example, if the telecommunications network company has billed the subscriber for 500 calls while the report indicates that only 495 calls were made, the subscriber can then find out from the company why there is a discrepancy of 5 calls. Line 204 is a trigger that informs the TVS server that the file from COMS system 140 has arrived.

The TVS server is also connected to a Report Manager server (RM) 350 which is a component of the "nMCI Interact" StarWRS reporting system 300. It is broken out in Fig. 10 to show that reports actually go to an interface from the TVS server, via line 208. To elaborate, the TVS creates the report and knows which subscriber is supposed to get the report. As will be described herein, a metadata request message is sent to RM 350 requesting a desired unpriced traffic call detail data report. The RM server processes the metadata request and forwards the message to the TARS 116 via TCP/IP connection 208 which generates the requested report for subsequent transport via TCP/IP connection 209 to an Inbox server, i.e., StarWRS message center 370. As will be described, the Inbox server 370 supports report retrieval via the subscriber's web browser .

The next system that communicates with the TVS server is a host system 210, which is the TVS system itself. Host system 210 in essence is the operating system where certain information required for operation of the TVS server is provided. For Fig. 10, it is assumed that the TVS server is in fact an application being performed by host system 210. Host system 210 provides a number of triggers to the TVS server for further processing. For example, via line 212, host system 210 provides a system time to the TVS server so that the TVS server can generate a time stamped report. Via line 214, host system 210 provides the TVS server a trigger of a particular time when the TVS server needs to perform some function. For instance, the system time from line 214 may trigger the TVS server to automatically generate a number of reports, some of which may be generated hourly, daily, or weekly. This is a background process that schedules the generating of reports on a periodic basis.

Line 214 is a system time line trigger by which host system 210 informs the TVS server that it is time to provide a nightly maintenance of the database itself, such as database 220 in Fig. 6.

The process termination trigger from line 218 by host system 210 informs the TVS server that one of its processors has terminated operation. As was mentioned previously, TVS system 116 comprises a number of processors each mirroring the operation of the others. The system knows which processors should be running at any given time. Thus, should one of the processors terminate its operation, notification is received by the host system that operation at that processor has been terminated so that the host system can instruct the operating system to transfer the process to one of the other backup processors, or to restart the process. Host system 210 is thus an automatic failure recovery system, the process termination trigger informing the system that the process has terminated, at which time the operator of the system needs to determine what type of system error has occurred.

A system operator, designated 220, actually watches over the TVS system to make sure that it is operational . Typical error messages are provided to the operator from the TVS server via line 222. A trigger is provided by the operator to cause the system to perform some function, for example a backup process, if an error is noted, via line 224. The trigger provided to the TVS server may in fact be from the keyboard of the operator. The TVS server may also communicate with other computer workstations or PCs, represented simply as 228 in Fig. 10. Some of the PCs 228 in actuality connect to the TVS server via a mail host 124.

Those PCs that gather and retrieve perspective data such as rolled up statistics or CDR flat files, may be connected directly to the TVS server. This is indicated by the remote output line 226. Line 228, on the other hand, enables the TVS server to communicate directly with the remote PCs. Through line 228, the TVS server can validate PC 228 so as to communicate therewith. Data can then be downloaded from a PC 228 to the TVS server. The six major functions performed by the

TVS server are discussed with reference to Fig. 11. Mapping feeds process 230 processes feeds from CADB system 138 and COMS system 140. As shown, a country

-62-

SUBST1TUTE SHEET (RULE 26) mapping feed, designated 232, is provided by CADB system 138 to map the different country codes. A second input provided to mapping feeds process 230 is the ncode data, via line 202 from COMS system 140. Switch mapping data is also provided by COMS system 140 as an input via line 234. There are two triggers provided to mapping feeds process 230. One of the triggers is from COMS system 140 to indicate that the file from COMS system 140 has arrived. This is indicated by line 204. The other trigger, via line 194, informs mapping feeds process 230 that the file has been provided by CADB system 138. Mapping feeds process 230 then maps the different representations of the switch name and provides that as an operator message, via line 222, to the operator. From this, errors may be generated. Furthermore, the data is provided to a store or a memory entitled state country mapping, designated as 236. Store 236 is a database file in database 120. The next process that the TVS server performs is the reports process, designated 238 in Fig. 11. As its name implies, process 238 generates, upon request, on a periodic basis, a number of reports. The different functions performed by the reports process 238 will be further elaborated in Fig. 12. It should be noted that there are a number of inputs, namely a system time provided by host system 210, via line 212, and a mail request provided by CADB system 238, via line 188, to the reports process 238. Also provided from an ncode map store 240 is an ncode map and from a CDR store 242 the requisite CDRs. Ncode map store 240 is a file which stores the different ncode maps as processed by the mapping feeds process 230. CDR store 242 is a file that includes CDRs that were fed thereto by the process performed by MTS system 112, as indicated per MTS data process 244. Also provided as inputs to reports process

238 are data from a customer information store 246 and a TVS report queue 248. Customer information store 246 provides information about the subscribers, the type of reports that they have ordered, the special service numbers that should be on the report and the frequency that the report should be generated, etc. TVS report queue 248 provides a buffer whereby the requested reports may be processed one at a time. Not shown, but should be understood being provided to reports process 238, is a call statistics store which allows process 238 to generate reports directly from call statistics as well as the CDR records retrieved from CDR store 242. When a report is generated, process 238 outputs the report, via line 209, to the StarWRS Inbox 370, in the format requested by the subscriber. Instead of reports, call statistics and CDR records may be retrieved and displayed, as screen formats, for subscribers of RTM system 117 in real time.

Fig. 12 illustrates the different types of reports processes that are performed in report process 238. As shown, scheduled reports are generated by subprocess 1381. It is by this process that regularly scheduled reports are generated, per input of system time by the host system via line 212. Shown also being provided as an input to the scheduled report generation subprocess 1381 is the information from the subscriber fed from customer information store 246. An output from the scheduled reports subprocess 1381 is the CDR reports which are fed via line 250 to a CDR report queue 252. A standard TVS report request is routed via line 251 to TVS report queue 248.

The next subprocess under report process 238 is the mail request process 1382. In addition to receiving mail request via line 188, note that subprocess 1382 may also receive retransmission requests, discussed earlier. Further shown being provided as an input to mail request subprocess 1382 is the customer information from customer store 246 and a mail report response from a probe request subprocess 1384, via line 256. If there is more than one probe request, the additional requests are provided via line 258 to a TVS probe queue 260, which in turn forwards the queued request via line 262 to probe request subprocess 1384. A standard TVS report request from the mail request subprocess 1382 is fed via line 251 to the TVS report queue 248. A response is then provided by mail request subprocess 1382 to mail host 24 via line 190. Any call detail TVS report request is provided by mail request subprocess 1382 via line 250 to retransmit stored report subprocess 1383.

The stored reports may be sent to the CDR report queue 252, so that the reports are transmitted one at a time, via line 208, to StarWRS Inbox 370 for delivery to the various subscribers. The report being retransmitted per store report retransmit subprocess 1383 obtains its data from a customer information store 246, a report retransmission store 262 with information pertaining to where the report is to be retransmitted, and a report archive 264 from which a previously prepared report may be retrieved. The format of the report is generated in accordance with the envelope provided by envelope body store 266.

In the probe request subprocess 1384, to send a report response to mail request subprocess 1382, probe request subprocess 1384 retrieves data from the customer information store 246 and call statistics store 254.

In report request subprocess 1385, to perform the report request, subprocess 1385 retrieves the next TVS report request from TVS report queue 248, subscriber data from customer information store 246, call statistics data from call statistics store 254 and ncode map data from ncode map store 240. The generated TVS report is routed via line 209 to StarWRS Inbox 370. The call detail reports subprocess 1386 is the last subprocess of report process 238. For this subprocess, data is retrieved from CDR store 242 and customer information store 246. Upon receipt of the latest TVS report request via line 250 from CDR report queue 252, call detail report subprocess 1386 generates the call detail report and sends it as comma delimited text, via line 266, to the host system for logging. In addition, the call detail report generated from subprocess 1386 is routed to StarWRS Inbox 370 via line 208, for further transmission to the requesting subscriber.

In further view of Figure 11, an MTS data process 244 receives an MTS message from MTS system 112. It is here that data from MTS system 112 is processed to generate the CDRs and call statistics, which are fed via lines 284 to CDR store 242 and call statistics store 254, both residing in MTS system 112. Any MTS failover response message generated by MTS data process 244 is fed via line 286 to MTS system 112. The MTS order entry response message from MTS data process 244 is loaded to a MTS response queue 268, before the message is fed one at a time to call message process 270.

Call message process 270 retrieves subscriber information from customer information store 246 via line 272 and any additional subscriber information provided by the subscriber via the client workstation, such as PC 144 shown in Fig. 6, via line 198. Any CORE error message produced by CORE message process 270 is provided via line 299 to CORE system 142. The MTS order entry message is provided via line 284 to MTS system 112. Another process performed by the TVS server is the bulk download process 274. Here data is retrieved from CDR store 242, CORE statistics store 254, customer information store 246, state country mapping store 136 and ncode map store 240. All of that information is retrieved in response to the remote input via line 228 from a remote subscriber at a computer workstation. Bulk download process 274 begins its operation upon receipt of the trigger 224 from the operator 220. Output from process 274 is provided via line 209 to the Inbox server 370 (Figure 7) . Note that this bulk download of a statistics file from the TVS server is different from the real time communications process between a subscriber workstation and RTM system 117. For the former, a single file comprising the requested information which spans a given period of time is downloaded. On the other hand, if the subscriber workstation is linked up with RTM system 117, a real time display of the statistics relating to the calls of the subscriber is provided.

One last function performed by the TVS server that is a stand alone function is the perform periodic processing process 276. Process 276 performs predetermined maintenance and housekeeping chores. As inputs, it retrieves data from CDR store 242 and call statistics store 254, as well as system time from host system 210. Upon receipt of the triggers from lines 216 and 214, for example each night, the data retrieved from CDR store 242 and call statistics store 254 are updated and restored in the respective stores. A message is provided to the operator via line 222. System time 214 notifies process 276 to clean up the files of the system, while DB time 216 informs processing 276 to begin the database maintenance operation.

In the preferred embodiment, when a subscriber subscribes to the RTM option, he/she is given a password which enables him to log onto RTM system 117. Once logged on, a subscriber can retrieve various statistics and view in real time those statistics and therefore the operation of the network, at least with respect to his special service call number (s) .

With respect to RTM system 117 and particularly the retrieval of call detail records statistics therefrom by a remote subscriber work station, refer to Fig. 13. Assume the remote subscriber's computer is equipped with a modem and the I/O ports of RTM system 117 are likewise equipped. With reference to Fig. 13, the functional processes that take place in RTM system 117, or the real time monitoring (RTM) system, are shown to comprise five major functions. They are: select and maintain profiles process 1171, get call detail statistics process 1172, inquire call detail process 1173, serve RTM reference data 1174 and serve RTM CDR data 1175. A number of inputs and outputs connect the different processes together to provide the operation of RTM system 117. As will be shown later, some of the processes interact with databases of the system.

Shown connected to select and maintain profiles process 1171 is a RTM profile request input 1711, a launch ACMS task input 1712, a RTM call detail profile output 1713 and a RTM profile messages output 1714. Also shown to be connected to process 1171 are a gatekeeper waiter array store 1715 and an ACMS task information store 1716. In addition, outputting from process 1171 are a RTM controller and profile output 1717 to inquire call detail process 1173, a RTM reference request output 1718 to serve RTM reference data process 1174 and a RTM control and profile output 1719 to get call detail statistics process 1172. A RTM reference data line 1720 connects process 1171 to serve RTM reference data process 1174.

Although not shown, input 1711, as well as outputs 1713 and 1714 are routed to or from the RTM Web server 52 (Fig. 6) . In other words, RTM profile requests are input to select and maintain profile process 1171 via line 1711 while outputs from process 1171 are provided as RTM call detail profiles and RTM profile messages to the user's terminal via line 1713 and 1714, respectively. Line 1712 provides to process 1171 an application control and management system (ACMS) that acts as an operating environment for the system. Specifically, when a RTM profile request is input to select and maintain profiles process 1171, a list of profiles for that subscriber is displayed to the subscriber. This is provided from process 1171 to either of outputs 1713 or 1714. When a RTM profile request is made, an ACMS task is launched from line 1712 to create an ACMS environment overlaying the operating system of RTM system 117. The ACMS environment provides the user with specific attributes that facilitate the operation of the system. For example, the environment may limit the system to no more than 50 users in order to be able to keep track of what the various users are doing. It moreover provides coordination for the system in order to enable the system to better handle the various inputs/outputs.

A subscriber accessing the system over the Internet via RTM web server 52 logs on to the RTM system via an Internet service provider. Once an RTM profile request is made by a subscriber, as mentioned before, the system is enveloped by the ACMS environment in response to the particular identifier associated with the RTM request. Specific information such as a particular profile information is retrieved from gatekeeper waiter array store 1715 for responding to an input request. Thus, gatekeeper waiter array store 1715 includes information of the RTM subscribers and allocates a unique identifier for each of the subscribers of the RTM system. Additional data is retrieved by process 1171 from an ACMS task information store 1716 for identifying the type of device used by the subscriber so that a particular output format may be provided to the subscriber. The ACMS environment in effect handles or controls the user's sign- in and how they are handled once they are logged on.

Once a subscriber has logged on, his input device having been identified and the profile request received, process 1171 may output to the subscriber RTM profile messages via line 1714. These RTM profile messages present the user with a list of the actual profiles that the user has created and stored. In the instance where a user has not stored any profiles, the RTM profile messages presented to the user will request the user to create a new profile. Thus, as its name implies, process 1171 enables a subscriber to manage all of his profiles by either adding, deleting or changing any of his profiles.

As shown, RTM reference data is requested by select and maintain profiles process 1171 from serve RTM reference data process 1174 via line 1718. Upon receipt of a RTM request, process 1174 will retrieve from its reference database store 1741 the requested reference data and provide this reference data, which relates to the subscriber who requested the data, to process 1171 as RTM reference data via RTM reference data line 1720. As will be discussed subsequently, reference database store 1741 is responsive to both storing and retrieving requests from processes other than process 1171. Some of the information that are stored in reference database store 1741 include the order entry information for a particular customer or subscriber, and all of the 800 number information relating to a subscriber such as which 800 (s) a subscriber has ordered. Note that the actual 800 call information, in the form of call detail records, are stored in the CDR database store 1751, which will be discussed, infra. Thus, process 1174 in essence maintains RTM reference data, by either updating or deleting it, and storing any updated or new RTM reference data into reference database store 1741.

If a subscriber wants to activate a given profile and to monitor the actual CDR records, a RTM control and profile request is sent from process 1171 to get call detail statistics process 1172. Process 1172, upon receipt of the RTM control and profile request, communicates with serve RTM CDR data process 1175 by outputting a RTM CDR request via line 1721. Serve RTM CDR data process 1175, in response to the RTM CDR request from process 1172, retrieves the appropriate data from the appropriate database of CDR database stores 1751. The thus retrieved CDRs stored in CDR database store 1751 for the particular 800 number are counted for the time frame that has been requested. The profile for the particular 800 that a subscriber wants to see is then retrieved by process 1175 and routed to process 1172 as RTM CDR data by means of line 1722. This

-72-

SUBST1TUTE SHEET (RULE 26) retrieved RTM CDR data is next displayed to the subscriber as either RTM statistics messages via line 1723 if a RTM statistics request from line 1724 is received, or as RTM call detail statistics output to line 1725. The call detail statistics are displayed to the subscriber in a substantial real time basis, insofar as the polling interval can be set to vary from one minute to sixty minutes in increments of one minute. In other words, a subscriber, when viewing the call detail statistics, will see continuous changes for every polling time interval .

If a RTM inquiry request is input to RTM system 117 such as from line 1731, given the RTM control and profile provided from process 1171 via line 1717, the inquiry call detail process 1173 will request the RTM reference data from service RTM reference data process 1174 via line 1732. The relevant reference data is retrieved from reference database store 1741 and provided by process 1174 as RTM reference data to inquire call detail process 1173 via line 1733. Given the RTM reference data and the appropriate RTM control and profile, process 1173 sends a RTM CDR request to service RTM CDR data process 1175 via line 1734. Process 1175, upon receipt of the RTM CDR request, similar to its response to such request from process 1172, retrieves from CDR database store 1751 the CDR statistics for the particular profile and routes this as RTM CDR data to process 1173 via line 1735. Process 1173, upon receipt of the RTM CDR data, displays it as a call detail screen to the subscriber. This output is provided as either a RTM

-73-

SUBST1TUTE SHEET (RULE 26) call detail inquiry screen to the subscriber via line 1736 or as RTM inquiry messages via line 1737. For RTM system 117, therefore, different outputs may be provided to a subscriber, depending on what the subscriber requests. If the subscriber requests call details, then a web page comprising a call detail statistics screen is provided by process 1173 to the subscriber. On the other hand, if the subscriber wants to monitor the real time operation of the network, he will request such and get call detail statistics process 1172 will provide call detail statistics screen to the subscriber. By observing the various screens, a subscriber can therefore monitor whether any trend has occurred with the operation of the network. If there is, appropriate actions may be taken to rectify the problem or alter the trend.

As was mentioned previously, the call detail records are stored in CDR database store 1751. The reason that there are multiple CDR database stores is that each subscriber, irrespective of however many special service call numbers that he subscribes to, is assigned a specific CDR database. This is found to enhance the adding or changing of the special service call numbers, and the detail information for each of those numbers. These database stores are the same as the above mentioned relational databases disclosed in the aforenoted co-pending '186 application.

For RTM system 117, in operation, when a subscriber or user has selected a specific profile, that profile is initially associated with an inquire call detail or get call detail statistics. Either the get call detail statistics or the inquire call detail may be viewed by the subscriber at one time by either requesting from process 1172 or 1173, respectively. Thus, if a subscriber activates or selects a specific profile, that profile (or rather the designation or name associated with that profile) and a few other pieces of information are routed to get call detail statistics process 1172. Process 1172, upon receipt of the request, sends a RTM reference request to serve RTM reference data process 1174, which retrieves the RTM reference for that profile from reference database 1741. The RTM reference request from process 1172 is sent to process 1174 via line 1726. Once retrieved, the RTM reference data is sent by process 1174 to process

1172 via line 1727. Now that process 1172 has all of the reference information, it sends a RTM CDR request to serve RTM CDR data process 1175 requesting RTM CDR statistics. Process 1175, upon receipt of the request from process 1172, retrieves the appropriate information from CDR database store 1751 and transmits that RTM CDR data via line 1722 to process 1172 to be displayed for the user. On the other hand, if the subscriber selects a profile that is initially associated with inquire call detail process 1173, the exact same thing as mentioned before occurs. That is, process

1173 requests the requisite RTM reference from process 1174. Upon retrieval of the appropriate reference data from reference database store 1741, process 1174 transmits that RTM reference data to process 1173. Thereafter, process 1173 sends the RTM CDR request to process 1175. The appropriate RTM CDR data is retrieved from the appropriate CDR database store 1751 and transmitted to process 1173. This retrieved RTM CDR data is then displayed to the subscriber.

As described, the present invention is integrated with a client and middle- tier service and application proxy component that enables customers to request, specify, customize, schedule and receive their telecommunications network call detail data in the form of reports that are generated by the various back-end application servers. Referred to as StarWRS, this WWW/Internet Reporting System 300, as shown in Figure 7, comprises the following components and messaging interfaces :

1) those components associated with the Client GUI front end including a report requestor client application 312, a report viewer client application 315 and, an Inbox client application 310 which implement the logical processes associated with a "Java Client," i.e., employs Java applets launched from the backplane (Figure 3) that enable the display and creation of reports and graphs based on the fields of the displayed reports, and, allows selection of different reporting criteria and options for a given report; and,

2) those middle- tier server components enabling the above-mentioned reporting functionality including: a Report Manager server 350, a Report scheduler server 360, and an Inbox Server 370. Also shown in Figure 7 are the system Order Entry client application 380 and a corresponding Order Entry

-76-

SUBST1TUTE SHEET (RULE 26) Server 385 supporting the StarWRS reporting functionality as will be described.

Each of these components will now be described with greater particularity hereinbelow. The Report Manager ("RM") server 350 is an application responsible for the synchronization of report inventory with back-end "Fulfilling" servers, i.e., TVS server 116; retrieval of entitlements, i.e., a user's security profiles, and report pick list information, i.e., data for user report customization options, from the system Order Entry server 380; the transmission of report responses or messages to the Dispatcher server 26 (Figure 2) ; the maintenance of the reporting databases; and, the management of metadata used for displaying reports. In the preferred embodiment, the RM server 350 employs a Unix daemon that passively listens for connect requests from the GUI client applications and other back-end servers and deploys the TCP/IP protocol to receive and route requests and their responses. Particularly, Unix stream sockets using the TCP/IP protocol suite are deployed to listen for client connections on a well-known port number on the designated host machine. Client processes, e.g., report requestor 312, desiring to submit requests connect to RM 350 via the dispatcher 26 by providing the port number and host name associated with RM 350. Request messages received by the RM server are translated into a "metadata" format and are validated by a parser object built into a report manager proxy 350' that services requests that arrive from the GUI front -end. If the errors are found in the metadata input, the RM 350 will return an error message to the requesting client. If the metadata passes the validation tests, the request type will be determined and data will be retrieved in accordance with the metadata request after which a standard response will be sent back to the requesting client. As shown in Figure 7, interface sockets 352 are shown connecting the Dispatcher server 26 and the RM server 350 and, other socket connections 208, 356 are shown interfacing the RM 350 with respective back end servers 116 and 400. For instance, in one embodiment, fulfilling server 400 provides a customer's priced billing data through a Talarian smart socket messaging interface 356 to the Report Manager. Additionally, as part of the StarWRS web reporting system 300 shown in Figure 7, unpriced traffic data may be sent directly to the report manager 350 from the Traffic View server 116, as described herein. Although not shown in Figure 7, it should be understood that the RM 350 server may manage reporting data for customer presentation from other back-end and legacy servers including, e.g., Broadband, Toll Free Network Management, and Event Monitor servers, etc. in order to present to a customer these types of billing/management data. The report manager server additionally utilizes a database 358, such as provided by Informix, to provide accounting of metadata and user report inventory. Preferably, an SQL interface is utilized to access stored procedures used in processing requests and tracking customer reports. A variety of C++ tools and other tools such as Rogue Wave's tools. h++ are additionally implemented to perform metadata message parsing validation and translation functions.

The Report Manager server 350 additionally includes the scheduling information which is passed to the back-end fulfilling servers 116, 400 and stored by them. At times, the Report Manager will request this information from the fulfilling servers in order to reconcile.

The Report Scheduler ("RS") server component 360 is, in the preferred embodiment, a perpetually running Unix daemon that deploys the TCP/IP protocol to send requests to the back-end fulfilling servers such as the StarODS (Perspective) server 400, or TVS server 116, and receive their responses. More particularly, the RS server 360 is a Unix server program that is designed to handle and process report requests to the fulfilling servers by deploying Unix stream sockets using the TCP/IP protocol suite, and sending the report request to client connections on a well-known port number on the designated host machine. As shown in Figure 7, interface TCP/IP connections 364, 366 are shown interfacing with respective back end servers 400 and 116. In the case of priced billing data from Perspective Host 400, report requests are published by the RS server 360 to a pre-defined subject on the Talarian Server. When handling other incoming messages published by back end servers using Talarian SmartSockets 4.0, another daemon process may be necessary that uses Talarian C++ objects to connect their message queue and extract all messages for a given subject for storage in a database table included in database 363. Each message includes the track number of the report that was requested from the fulfilling server.

From the report scheduler interface, the user may specify the type of reporting, including an indication of the scheduling for the report, e.g., hourly, daily, weekly or monthly. For priced data the user has the option of daily, weekly, or monthly. For real-time, or unpriced data, the user has the option of hourly, daily, weekly or monthly. The report scheduler interface additionally may enable a user to specify a page or E-mail account so that an e-mail or page message may be sent to indicate when a requested report is in the Inbox server 370. As shown in Figure 7, the report scheduler server 360 interfaces directly with the Report Manager server 350 to coordinate report request processing. It should be understood that the respective report management and scheduling functions could be performed in a single server.

The Inbox Server component 370 serves as the repository where the completed user report data is stored, maintained, and eventually deleted and is the source of data that is uploaded to the client user via the dispatcher over a secure socket connection 372. It is also a Unix program that is designed to handle and process user requests submitted in metadata format using an Informix database. Once report results are received from the TVS server 116 or any other back-end or fulfilling servers (not shown) , the Inbox server 370 requests the metadata from the Report Manager server 350 as indicated by the socket connection 372 in Figure 7. The metadata is stored in the Inbox server database 373 along with the report results. Thus, if the metadata is required to be changed, it will not interfere with the information needed to display the reports included in the Inbox. Additionally, as shown in Figure 7, the Inbox server interfaces with the report scheduler to coordinate execution and presentation of reports.

The StarOE server 380 is the repository of user pick lists and user reporting entitlements as shown in database 383. Particularly, it is shown interfacing with the Inbox server 370 and report scheduler servers 360. The Report Manager does not interface with or include metadata for StarOE. It will, however, include information in the report metadata that will tell the Report Requestor it needs to get information (i.e., Pick Lists) from StarOE server 385. Particularly, the StarOE server supports pick lists for the selection of priced data based on the following list: Date, Time (Provide in GMT offset), ID Accounting Code (IDAC)/Supp code, Access Type, Corp ID, Service Location w/Service Location Names, Bill Payer w/Bill Payer Names, 8XX Number, City, State/Province, Numbering Plan Area (NPA), NXX (Exchange code where N=2-9 and X=0-9), and Country Code.

With regard to the front -end client GUI components, the above-mentioned Inbox client application 310 functions as an interface between the client software and the Inbox server 370 for presenting to the customer the various type of reports and messages received at the Inbox including all completed reports, call detail, alarms, and flashes. Preferably, the messages for the user in the inbox is sorted by type (e.g., report, call detail, alarms) and then by report type, report name, date, and time.

Particularly, the Inbox client application uses the services of the backplane (Figure 3) to launch other applications as needed to process report messages. The inbox will also use the services of the data export objects to provide a save/load feature for inbox messages, and, is used to provide a user- interface for software upgrade/download control. Inbox messages are generated by the versioning services of the backplane; actual downloads will be accomplished by a request through the inbox. In the preferred embodiment, the inbox client is able to receive information on multiple threads to allow a high priority message to get through even if large download is in progress. Typically, the browser is configured to allow more than one network connection simultaneously, i.e., the polling thread on the client uses a separate

-82-

SUBST1TUTE SHEET (RULE 26) connection to check for new messages, and start a new thread on a new connection when a new message was detected. In this way, multiple messages may be downloaded simultaneously. The Report Requestor application 312 is a

GUI Applet enabling user interaction for managing reports and particularly includes processes supporting: the creation, deletion, and editing of the user's reports; the retrieval and display of selected reports; the display of selected option data; and the determination of entitlements which is the logical process defining what functionality a user can perform on StarWRS. In the preferred embodiment, a Report request may be executed immediately, periodically, or as "one- shots" to be performed at a later time. As described herein, the report scheduler service maintains a list of requested reports for a given user, and forwards actual report requests to the appropriate middle - tier servers at the appropriate time. Additional functionality is provided to enable customers to manage there inventory, e.g., reschedule, change, or cancel (delete) report requests.

The Report Viewer application 315 is a GUI Applet enabling a user to analyze and display the data and reports supplied from the fulfilling servers such as StarODS (perspective) 400, Traffic View 116, and other systems such as Broadband and toll free network manager. Particularly, the Report Manager 350 includes and provides access to the metadata which is used to tell the Report Requestor what a standard report should look like and the "pick- list" options the user has in order for them to customize the standard report. It is used to tell the Report Viewer client how to display the report, what calculations or translations need to be performed at the time of display, and what further customization options the user has while viewing the report. It additionally includes a common report view by executing a GUI applet that is used for the display and graphing of report data and particularly, is provided with spreadsheet management functionality that defines what operations can be performed on the spreadsheet including the moving of columns, column hiding, column and row single and multiple selection, import and export of spreadsheet data, and printing of spreadsheet, etc. It is also provided with report data management functionality by defining what operations can be performed on the data displayed in a spreadsheet including such dynamic operations as sorting of report data, sub- totaling of report data, etc.. Furthermore, the report viewer 315 is provided with functionality enabling the interpretation of metadata; and, functionality enabling communication with the Backplane (Figure 3) . The report viewer application 315 is able to accept messages telling it to display an image or text that may be passed by one of the applications in lieu of report data (e.g., Invoice, Broadband report, etc.) All reporting is provided through the Report Viewer interface which supports spreadsheet, a variety of graphic and chart types, or both types simultaneously. The spreadsheet presentation allows for sorting by any arbitrary set of columns. The report viewer 315 is launched from the inbox client 310 when a report is selected and may also be launched from the inbox when a report is selected. By associating each set of report data which is downloaded via the Inbox server 370 with a "metadata" report description object, reports can be presented without report- specif ic presentation code. At one level, these metadata descriptions function like the catalog in a relational database, describing each row of a result set returned from the middle tier as an ordered collection of columns. Each column has a data type, a name, and a desired display format, etc. Column descriptive information will be stored in an object, and the entire result set will be described by a list of these objects, one for each column, to allow for a standard viewer to present the result set, with labeled columns. Nesting these descriptions within one another allows for breaks and subtotaling at an arbitrary number of levels. The same metadata descriptions can be used to provide common data export and report printing services. When extended to describe aggregation levels of data within reporting dimensions, it can even be used for generic rollup/drilldown spreadsheets with "just- in- time" data access. The metadata data type may include geographic or telecommunications -specific information, e.g., states or NPAs. The report viewer may detect these data types and provide a geographic view as one of the graph/chart types .

The following list provides the types of requests that may be initiated by the Report Requestor 312 and the responses performed by the Report Manager 350: 1) Get/Send report template list - which request retrieves the list of all standard report templates for all products and is used only to obtain general report information, e.g., report title, description, etc.; 2) Get/Send report template detail - which request retrieves the details of a specific standard report template; 3) Get/Send user report list - which request retrieves the list of all user reports for the report format selected from a user report table and is used only as a request for general report information, e.g., report title, status, etc.; 4) Get/Send user report detail - which request retrieves the details of a specific user's report; 5) Add report definition/Acknowledgment - which requests addition of a user- created report to a user report table. If the report is a scheduled report, this request is also communicated to the fulfilling server at the time the report is due; 6) Delete report definition/Acknowledgment - which request deletes a user -created report from the user table; 7) Copy report definition/Acknowledgment - which request creates a duplication of the report the user is editing (other than the report title) and creates a new report ID for it; 8) Update Reporting

-86-

SUBST1TUTE SHEET (RULE 26) Schedule/Acknowledgment - which request updates the scheduling information on a report without having to send a Delete and Add request; and, 9) Get Pick List/Acknowledgment - which request enables the Report Requestor 312 to get a pick list provided by StarOE server.

As mentioned herein with respect to Figures 6 and 7, the TVS component 116 interfaces with StarWRS web reporting tool 300 for specific customer reporting requirements. As described, the Report Requester 360 communicates with the user client 301 and controls navigation and requests for customization criteria via the Web browser. The Report Requestor receives from StarOE any billing hierarchies and static pick lists needed by the client to customize report requests. Report request customizations are then passed to the Report Manager, which acts as repository of report requests, both ad hoc and recurring, that are submitted for processing by the client. Along with the necessary customization criteria selected for report customization, the Report Manager 350 stores metadata about the report request, including report format information, sort, and display specifics. The Report Manager is responsible for passing report requests to the back end DSS and data marts for processing, and provides the entity against which the list of report requests known to the data marts are validated. The Inbox server component 370 is the store and forward repository of all completed reporting requests, requests for call detail data, and any communications to the customer. The TVS server call detail report process 1386 ships formatted data in a compressed comma delimited format ("CDF") to the Inbox. Customers are then responsible for retrieving their report data held in the Inbox.

As shown in the logon process flow diagram of Figure 16, a customer first establishes communication with the DMZ Web server at step 602 and logs on to the nMCI Interact reporting system by entering the user's name and password onto a logon dialog box, as indicated at step 604. Having accessed the web page and logged in, a user Common Object is created. As indicated at step 606, an application running on the backplane directs a "Validate User Message" to the StarOE server 380 via the web server (Figure 7) to direct the StarOE server 380 to perform security validation and authenticate the user ID and password. It is understood that all communication to the StarOE server is via TCP/IP with a Unix process listening on a known TCP port. All data and security information is accessed by direct queries to a StarOE server database 283, such as provided by Informix.

Once the customer is validated, at steps 607a, b, the backplane objects request a list of all the authorized applications from the StarOE server, as indicated at step 608. Particularly, a "Get User Application Request" message is communicated to the StarOE server via the backplane which queries the Informix database to obtain a list of authorized applications, i.e., services, for the user and which determines which buttons on the home page are active, thus controlling their access to products. At steps 610 and 612 respectively, a networkMCI

Interact applet is downloaded to the customer's Web Browser via the established TCP/IP connection, and the browser presents the customer with the networkMCI Interact system home page, such as the exemplary home page 80 shown in Figure 4. It should be understood that in the preferred embodiment, the icons for applications the user has security access to are shown bolded. Thus, it should be understood that if the customer subscribes to Unpriced Reporting, an Unpriced Reporting icon is automatically enabled when the home page appears.

Referring back to Figure 16, at step 614, the customer selects the Unpriced Reporting application from the home page by clicking on a Report Requestor icon 76 (Fig. 4) after StarOE validates the user's id and password. The backplane object allows the user access to the Report Requestor front end if the user is so authorized. As shown at step 615, a client unpriced reporting application is downloaded to the customer who is presented with the unpriced reporting screen (not shown) , as indicated at step 616. It is from this screen that the user has the option to create or modify the types and specify the frequency at which reports are to be delivered. The subscriber may also retrieve completed TVS reports residing in the Inbox by clicking on the Message center icon 77 (Fig. 4) . Furthermore, the subscriber may access

-89-

SUBSTΪTUTE SHEET (RULE 26) real-time traffic monitoring capability, e.g, viewing real-time network traffic statistics, by clicking on the traffic monitor icon 72 (Fig. 4) .

In the preferred embodiment, for the real- time monitoring function, there are a number of web page display screens generated by the RTM system 117 that, in combination, provide the subscriber with the real time traffic statistics he/she desires. As shown in Fig. 14, these various screens are interconnected and, as will be shown later, are selectable by the subscriber. In particular, there is a summary statistics screen 1210, an incomplete statistics screen 1212, an other statistics screen 1214, an inquiry screen 1216, a profile selection screen 1218, a polling interval screen 1220, an exit screen 1222 and a new polling start time screen 1224. There are furthermore a real time statistics subscreen 1226, a call disposition subscreen 1228 and a CDR display screen 1230 emanating from inquiry screen 1216.

To illustrate the interrelationship between the screens, note that summary statistics screen 1210, incomplete statistics screen 1212 and other statistics screen 1214 are interconnected, by a bus 1232. At the same time, those screens are also interrelated, per another bus 1234, to profile selection screen 1218, polling interval screen 1220, exit screen 1222, new polling start time screen 1224 and inquiry screen 1216. These screens, or subscreens (po -up screens) , are provided to the subscriber as web pages via a Web browser, e.g., Internet Explorer 4.0 or greater, which is part of

-90-

SUBST1TUTE SHEET (RULE 26) the client Report viewer component of the StarWRS web reporting system as shown in Figure 7.

RTM system 117 basically provides a subscriber the ability to see in near real time how the network is performing. The subscriber can see how many calls (directed to his call number (s) ) are being attempted on a predetermined time period, as for example minute by minute. The subscriber furthermore can see how many of those calls are being allowed through the network, how many are incompletes, how many are blocked, etc. Furthermore, RTM system 117 provides subscribers the ability, if they decide to do so, to look up specific call records that made up a specific type of call. For example, if a subscriber sees an abnormal number of incompletes, assuming that ordinarily 5% of calls are incompletes, he can retrieve the call records that made up those incomplete calls to find out why those calls were incompletes. A screen for showing the various statistics is shown in Fig. 15(h).

The screen of Fig. 15(h) shows both current and total number of calls to a subscriber. This exemplar web page display screen of Fig. 15(h) shows that a subscriber started viewing in near real time the statistics of calls directed to his call numbers at 00:43, and that the current time is 19:38. The polling time interval is five minutes. Thus, the next screen that the subscriber sees will be at 19:43. As further shown in the exemplar screen of Fig. 15(h), the subscriber "DANTEST" has two special service call numbers, i.e. 123-4567 and 345-8789. It is assumed for this discussion that

-91-

SUBST1TUTE SHEET (RULE 26) those numbers are 800 numbers. Both the current (C) and total (T) figures are shown. Thus, during the time period that the subscriber views the summary statistics screen, there were three attempts that were incompletes; and those incomplete calls were directed to call number 123-4567. Given the five minute interval, the next screen that the subscriber sees will be a screen that shows what occurred between 19:38 and 19:43. Note that even though only two special service call numbers are shown, a subscriber can in actuality subscribe to a much greater number of special service call numbers. Note further that in addition to showing the number of attempts and incompletes, the Fig. 15(h) screen also shows

"OTHER" which may be calls that were blocked or didn't get through because of the insufficient capacity in the network purchased by the subscriber, and "DTO" which is direct termination overflow that shows how many of the calls are rerouted when the network capacity for a specific route is either busy or over capacity. The DTO feature may be ordered by the subscriber. There is also a "DURATION" portion which shows the average and total durations, both in minutes and seconds .

At the bottom of the Fig. 15(h) screen, there are a number of options provided to the subscriber for exiting the exemplar screen of Fig. 15(h) and going to some other screen. For example, given that there are three incompletes shown on the summary statistics screen of Fig. 15(h), a subscriber may want to next view the incompletes statistics summary screen of Fig. 15 (i). Upon activation, incomplete statistics screen 1212 shows retrieved call detail records of the special service call numbers associated with the subscriber on the exemplar screen of Fig. 15 (i) . As before, a total of three incompletes are shown.

These incompletes are further categorized as "short calls", which are calls that last less than three seconds. In other words, incomplete calls are in all likelihood calls directed to call number 123- 4567 while that number was busy. The other two categories further elaborating incomplete calls are "didn't wait" and "didn't answer." A "didn't wait" call is chosen to be from 3-15 seconds which means that the phone rang for a while before the customer hung-up. A "didn't answer" incomplete call is one that lasts more than 15 seconds and means that there was probably no operator available to answer that incoming call. When a large number of blocks are shown in the incomplete summary web page display having an exemplar screen of Fig. 15 (i) , the subscriber can next proceed to another web page having a summary screen of Fig. 15 (j) to determine the reason why a call is blocked.

As shown in Fig. 15 (j), one of the reasons that a call is blocked is due to its ID codes. This is also known as subcode blocking and it is a type of call that a subscriber has configured. For example, a subscriber may require that a PIN (personal identification number) be required before a call is to be completed. Thus, an ID code blocked call is a blockage defined by the subscriber. The next type of blockage is a "tailor call coverage," also known as an out of band blockage. This is

-93-

SUBST1TUTE SHEET (RULE 26) where a subscriber has purchased a special service call number such as a 800 number for only a given area in the country. For example assume a subscriber has subscribed to a 800 number only in the state of New Jersey. Anyone calling from outside that state is considered out of band and not in the "tailor call coverage."

There is also an "equipment/network congestion" blockage. These are blocks defined by the management of the telecommunications network. For example, a switch may be congested, a line has failed, etc.

To determine where the incomplete calls are coming from, a subscriber can go to a call detail inquiry screen such as that shown in Fig.

15 (k) . The exemplar screen of Fig. 15 (k) provides a list of all of the calls made to a particular special service number at a particular time range specified by the subscriber. It provides details about the call so that the subscriber can find out where the incomplete calls came from. An advantage provided by this screen is that the subscriber may call his customers back to find out additional information than what is displayed. Fig. 15 (k) further shows that the time range requested by the subscriber is between 00:00 to 23:59, i.e. substantially the whole day. The call detail inquiry pertains to an 800 number, namely 123-4567. The calling number from which the incomplete call originated is (719) 282-1860. The country code of one designates the United States. The time it was connected to the network is shown to be August 31, 1994 at 04:00 hour. The duration of the call was 12

-94-

SUBST1TUTE SHEET (RULE 26) seconds. The disposition of the call was that there was no answer. The DNIS designates a specific termination from a customer PBX, which is shown to be 123-3589. There is no DTO. There are a number of call dispositions that are available to a subscriber. One of those is shown in Fig. 15 (j ) . To select another call disposition or multiple call dispositions, the subscriber can select a call disposition selection screen such as that shown in Fig. 15(1) . For the instant invention, there are 10 available call dispositions that a call can have. These include: answered, short call, didn't wait, didn't answer, ID codes, tailor call coverage, NCS reject, NCS blocked, switch control and network block. A subscriber can asterisk or highlight any one, a multiple or all of the call dispositions, for viewing. In other words, a subscriber selects the criteria for what is to be displayed on the screen. For the example shown in Fig. 15(1), a subscriber has chosen answer (completed calls) , short calls, didn't wait, didn't answer, tailor call coverage, NCS reject and switch control calls. By selecting the different call dispositions, a subscriber sees different information relating to the calls.

One of such detailed displays is shown in the CDR detail display of Fig. 15 (m) . A pop-up screen thereat shows that the call was made from Colorado Springs, Colorado and that it was a short call. Additional information relating to each of the call dispositions may be added as seen fit.

So far, discussion has been had with the various screens which a subscriber can view with respect to calls directed to one or more of his special service call numbers. But before a subscriber can view the various screens, he needs to sign up with the TVS system 116, and more particularly subscribe to the RTM option.

When a subscriber first signs up with the network, a profile is established for him. Such profile selection screen is shown in Fig. 15(a) . The subscriber can have as many profiles as he desires. Putting it differently, he may have one for monitoring all of his 800 numbers, one that monitors only one specific 800 number, one that monitors only five of his 800 numbers, etc. By inputting to the profile selection screen, a subscriber can select a given profile that he wants to use which defines the numbers that will be shown. In addition, the type of statistics look-up, or call inquires, that the subscriber wants may also be selected. New profiles may be created, while existing profiles can be updated.

Fig. 15(b) illustrates a screen by which a subscriber can add a profile. Suppose the subscriber has logged onto the system. He is prompted for his profile name which is shown by the exemplar Fig. 15(b) to be "testuser." The screen shows to the subscriber the polling interval, which for this example is five minutes. A description of the profile may also be provided. For example, the exemplar Fig. 15(b) profile screen shows that it is a test profile. So, too, a list of all of the special service numbers, for example 800 numbers, for the subscriber is shown. Selective 800 numbers shown on the screen of Fig. 15(b) can be monitored in greater details. See for example the four asterisked numbers of Fig. 15(b). To delete the display, the asterisk next to the number can be removed by simply toggling the number once the number has been highlighted with a cursor.

A profile may be deleted as shown in Fig. 15 (c) . Specifically, after the profile selection screen of Fig. 15(a) is retrieved, a key, for example CTRL-D is selected so that a pop -up screen appears. By moving the cursor, a particular profile would be deleted. As shown in Fig. 15(c), given that the subscriber has five different profiles, if he were to delete the profile "DANTEST" , four other profiles remain. To add a special call number, the exemplar screen shown in Fig. 15(d) is used. The add/delete profile phone numbers pop- screen is retrieved after the subscriber has entered into the adding a profile screen of Fig. 15(b). In addition to adding, special service phone numbers may also be deleted. If the number of special service call numbers exceeds the capacity of the screen, a subscriber can roll the screen to view the numbers outside of the view of Fig. 15(d) . A so-called top five numbers may be selected. This is shown in Fig. 15(e) . The specific details and statistics relating to those numbers, once selected, are displayed on the statistics screens. Although only five numbers are shown to be selectable in Fig. 15(e) , a higher or smaller number may also be selected. Once selected, those numbers are continuously displayed on the screen. The polling interval may be changed. For example, the discussion so far pertains to a polling interval of 5 minutes. However, such polling period may be changed to 10 minutes, as shown in Fig. 15(f), or to a smaller predetermined period of time.

The start time for the polling interval likewise can be changed. This is shown in Fig. 15 (g) in which the start time has been changed to 19:40. By thus being able to monitor in substantially real time the operation of the network with respect to calls directed to call numbers the subscriber has subscribed to, a subscriber can quickly identify how efficiently his 800 numbers are being utilized. For example, suppose between 9:00 am and 10:00 am, an average of 100 calls per minute were received. Further assume that there were 200 operators on duty for the subscriber. Accordingly, half of those operators were not busy during that time period. On the other hand, between 3:00 pm and 4:00 pm there were only 50 operators on duty. Yet there were, on average, 400 calls per minute received during that period of time, resulting in a large number of incomplete calls. Once having that information, the subscriber can reallocate his resources, for example decreasing the number of operators in the morning and increasing the active operators in the afternoon. If it is found that there is a lot of blockage occurring, the subscriber can purchase additional capacity from the network.

Inasmuch as the present invention is subject to many variations, modifications and changes in detail, it is intended that all matter described throughout this specification and shown in the accompanying drawings be interpreted as illustrative only and not a limiting sense. Accordingly, it is intended that the invention be limited only by the spirit and scope of the appended claims .

Claims

1. A system for enabling an Internet enabled subscriber of a telecommunications network to monitor in substantially real time the operation of the telecommunications network, said system comprising: a) an Internet enabled subscriber work station to enable secure IP communications between said subscriber and a network of a telecommunications service provider; b) a server for authenticating said subscriber as being entitled to receive real time telecommunications network operation data; c) processor device for determining the call details of special service calls routed through said network; d) a traffic statistics apparatus including database device into which records of the call details determined from calls of various subscribers routed through said network are stored; and e) connection device in communication with said traffic statistics apparatus for downloading stored call detail records to said subscriber work station via said secure IP communications; whereby said subscriber work station displays to said subscriber the operation of said network as it relates to any special service number of said subscriber in substantial real time.
2. The system as claimed in claim 1, wherein the operation of said network being displayed by said subscriber workstation comprises traffic statistics relating to said any special service call of said each subscriber.
3. The system as claimed in claim 1, further comprising: process for creating a profile for said each subscriber, said process communicating said user profile information to said traffic statistics apparatus so that operation of said network is displayed to said each subscriber in accordance with said input profile.
4. The system as claimed in claim 1, wherein the operation of said network is displayed to said each subscriber as web pages presenting displays having a number of reporting options that a subscriber can choose.
5. The system as claimed in claim 1, wherein the operation of said network being displayed at said subscriber workstation comprises a summary statistics screen, an incomplete statistics screen, another statistics screen and an inquiry screen that displays real time statistics and call detail records of any special service call for said subscriber.
6. A method for enabling a subscriber to monitor in substantially real time the operation of a telecommunications network at a subscriber workstation over the Internet, said method comprising the steps of: enabling secure Internet access between said subscriber and an enterprise server receiving a subscribers call detail data pertaining to the routing of special service calls throughout the subscriber's telecommunications network, said call detail data being provided to said enterprise server according to subscriber's entitlements; authenticating said subscriber entitlement at the time of subscriber access to said enterprise server; retrieving and determining the call details of special service calls routed through said network; storing into a database device of said enterprise server records of the call details determined from calls of various subscribers routed through said network; downloading from said database the call details of special service calls routed through said network to a subscriber workstation via the Internet; and displaying to said subscriber the operation of said network as it relates to any special service number of said subscriber in substantial real time.
7. The method of claim 6, wherein said displaying step further comprises the step of displaying to said subscriber traffic statistics relating to said any special service call of said each subscriber.
8. The method of claim 6, further comprising the step of: creating an entitlement profile for said subscriber so that the operation of said network is displayed to said subscriber in accordance with said profile.
9. The method of claim 6, wherein said displaying step further comprises the step of displaying the operation of said network to said subscriber as web pages presenting a number of options that said subscriber can choose.
10. The method of claim 6, wherein said displaying step further comprises the step of: displaying the operation of said network to said subscriber as a web page including any of a summary statistics screen, an incomplete statistics screen, an other statistics screen and an inquiry screen that displays real time statistics and call detail records of any special service call for said subscriber.
11. A method for enabling a subscriber of a telecommunications service provider to monitor the traffic of calls to at least one special service call number of said subscriber through the communications network of said telecommunications service provider, the monitoring being enabled at a subscriber workstation over the Internet, said method comprising the steps of:
-103-
SUBST1TUTE SHEET (RULE 26) enabling secure Internet access between said subscriber and an enterprise server receiving a subscribers call detail data pertaining to the routing of call traffic throughout the subscriber's telecommunications network, said call detail data being provided to said enterprise server according to subscriber's entitlements; authenticating said subscriber entitlement at the time of subscriber access to said enterprise server; generating call detail records of special service calls routed through said network; storing the call detail records of said calls in a database device; downloading from said database device the call details relating to stored call detail records of calls directed to any special service call number subscribed by said subscriber; and displaying said downloaded data at said subscriber workstation as various web pages, each web page capable of portraying a representation of the status of said calls being routed through said network in response to a particular request by said subscriber.
12. The method of claim 11, further comprising the steps of: creating a profile for said subscriber; said displaying step further comprising the step of displaying to said subscriber said data in accordance with said customer's profile.
13. The method of claim 11, wherein said displaying step further comprises the step of: displaying said retrieved data to said subscriber as traffic statistics relating to calls directed to said any special service call number of said subscriber.
14. The method of claim 11, wherein said displaying step further comprises the step of: displaying said retrieved data to said subscriber as one or more web pages having screens comprising a number of options that said subscriber can choose.
15. The method of claim 14, wherein said screens include: a summary statistics screen, an incomplete statistics screen, an other statistics screen and an inquiry screen that displays real time statistics and call detail records of any special service call for said subscriber.
PCT/US1998/020146 1997-09-26 1998-09-25 Integrated interface for real time web based viewing of telecommunications network call traffic WO1999016198A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US6065597 true 1997-09-26 1997-09-26
US60/060,655 1997-09-26

Publications (1)

Publication Number Publication Date
WO1999016198A1 true true WO1999016198A1 (en) 1999-04-01

Family

ID=22030944

Family Applications (21)

Application Number Title Priority Date Filing Date
PCT/US1998/020146 WO1999016198A1 (en) 1997-09-26 1998-09-25 Integrated interface for real time web based viewing of telecommunications network call traffic
PCT/US1998/020148 WO1999016207A1 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based data management reports
PCT/US1998/020159 WO1999015989A9 (en) 1997-09-26 1998-09-25 Authentication and entitlement for users of web based data management programs
PCT/US1998/020095 WO1999015984A1 (en) 1997-09-26 1998-09-25 Graphical user interface for web enabled applications
PCT/US1998/020155 WO1999016002A1 (en) 1997-09-26 1998-09-25 Web based integrated customer interface for invoice reporting
PCT/US1998/020157 WO1999016218A1 (en) 1997-09-26 1998-09-25 Integrated customer web station for web-based call management
PCT/US1998/020171 WO1999016202A2 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based telecommunications management tools
PCT/US1998/020136 WO1999015960A3 (en) 1997-09-26 1998-09-25 Integrated customer interface for web-based data management
PCT/US1998/020173 WO1999019803A1 (en) 1997-09-26 1998-09-25 Integrated customer interface for web based communications network management
PCT/US1998/020158 WO1999016099A3 (en) 1997-09-26 1998-09-25 Secure customer interface for web-based data management
PCT/US1998/020149 WO1999015988A3 (en) 1997-09-26 1998-09-25 Secure server architecture for web based data management
PCT/US1998/020138 WO1999015974A1 (en) 1997-09-26 1998-09-25 Integrated interface for web based customer care and trouble management
PCT/US1998/020137 WO1999016230A1 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based telecommunication toll-free network management
PCT/US1998/020170 WO1999015979A9 (en) 1997-09-26 1998-09-25 Integrated business system for web based telecommunications management
PCT/US1998/020141 WO1999016206A1 (en) 1997-09-26 1998-09-25 Data warehousing infrastructure for web based reporting tool
PCT/US1998/020150 WO1999015996A3 (en) 1997-09-26 1998-09-25 Multi-threaded web based user inbox for report management
PCT/US1998/020160 WO1999015978A1 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based broadband telecommunications management
PCT/US1998/020147 WO1999015977A1 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based telecommunications network management
PCT/US1998/020180 WO1999016203A3 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based data management reports
PCT/US1998/020156 WO1999015950A1 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based alarm management tools
PCT/US1998/020139 WO1999015975A1 (en) 1997-09-26 1998-09-25 Integrated interface for web based customer care and trouble management

Family Applications After (20)

Application Number Title Priority Date Filing Date
PCT/US1998/020148 WO1999016207A1 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based data management reports
PCT/US1998/020159 WO1999015989A9 (en) 1997-09-26 1998-09-25 Authentication and entitlement for users of web based data management programs
PCT/US1998/020095 WO1999015984A1 (en) 1997-09-26 1998-09-25 Graphical user interface for web enabled applications
PCT/US1998/020155 WO1999016002A1 (en) 1997-09-26 1998-09-25 Web based integrated customer interface for invoice reporting
PCT/US1998/020157 WO1999016218A1 (en) 1997-09-26 1998-09-25 Integrated customer web station for web-based call management
PCT/US1998/020171 WO1999016202A2 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based telecommunications management tools
PCT/US1998/020136 WO1999015960A3 (en) 1997-09-26 1998-09-25 Integrated customer interface for web-based data management
PCT/US1998/020173 WO1999019803A1 (en) 1997-09-26 1998-09-25 Integrated customer interface for web based communications network management
PCT/US1998/020158 WO1999016099A3 (en) 1997-09-26 1998-09-25 Secure customer interface for web-based data management
PCT/US1998/020149 WO1999015988A3 (en) 1997-09-26 1998-09-25 Secure server architecture for web based data management
PCT/US1998/020138 WO1999015974A1 (en) 1997-09-26 1998-09-25 Integrated interface for web based customer care and trouble management
PCT/US1998/020137 WO1999016230A1 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based telecommunication toll-free network management
PCT/US1998/020170 WO1999015979A9 (en) 1997-09-26 1998-09-25 Integrated business system for web based telecommunications management
PCT/US1998/020141 WO1999016206A1 (en) 1997-09-26 1998-09-25 Data warehousing infrastructure for web based reporting tool
PCT/US1998/020150 WO1999015996A3 (en) 1997-09-26 1998-09-25 Multi-threaded web based user inbox for report management
PCT/US1998/020160 WO1999015978A1 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based broadband telecommunications management
PCT/US1998/020147 WO1999015977A1 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based telecommunications network management
PCT/US1998/020180 WO1999016203A3 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based data management reports
PCT/US1998/020156 WO1999015950A1 (en) 1997-09-26 1998-09-25 Integrated proxy interface for web based alarm management tools
PCT/US1998/020139 WO1999015975A1 (en) 1997-09-26 1998-09-25 Integrated interface for web based customer care and trouble management

Country Status (5)

Country Link
US (22) US6490620B1 (en)
JP (3) JP2003526126A (en)
CA (3) CA2304543A1 (en)
EP (3) EP1015970A4 (en)
WO (21) WO1999016198A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001081829A1 (en) * 2000-04-27 2001-11-01 Brio Technology, Inc. Method and apparatus for processing jobs on an enterprise-wide computer system

Families Citing this family (2365)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7849393B1 (en) 1992-12-09 2010-12-07 Discovery Communications, Inc. Electronic book connection to world watch live
US7865567B1 (en) * 1993-12-02 2011-01-04 Discovery Patent Holdings, Llc Virtual on-demand electronic book
US8073695B1 (en) 1992-12-09 2011-12-06 Adrea, LLC Electronic book with voice emulation features
US9053640B1 (en) 1993-12-02 2015-06-09 Adrea, LLC Interactive electronic book
CA2151456C (en) 1992-12-09 2004-03-02 John S. Hendricks Reprogrammable terminal for suggesting programs offered on a television program delivery system
US7835989B1 (en) 1992-12-09 2010-11-16 Discovery Communications, Inc. Electronic book alternative delivery systems
US7509270B1 (en) 1992-12-09 2009-03-24 Discovery Communications, Inc. Electronic Book having electronic commerce features
US7861166B1 (en) 1993-12-02 2010-12-28 Discovery Patent Holding, Llc Resizing document pages to fit available hardware screens
US8095949B1 (en) 1993-12-02 2012-01-10 Adrea, LLC Electronic book with restricted access features
US6744894B1 (en) * 1994-04-01 2004-06-01 Mitsubishi Corporation Data management system
US7036019B1 (en) 1994-04-01 2006-04-25 Intarsia Software Llc Method for controlling database copyrights
JPH07271865A (en) 1994-04-01 1995-10-20 Mitsubishi Corp Method for managing copyright of data base
US8595502B2 (en) 1995-09-29 2013-11-26 Intarsia Software Llc Data management system
US7302415B1 (en) 1994-09-30 2007-11-27 Intarsia Llc Data copyright management system
US7801817B2 (en) 1995-10-27 2010-09-21 Makoto Saito Digital content management system and apparatus
EP0715241B1 (en) 1994-10-27 2004-01-14 Mitsubishi Corporation Apparatus for data copyright management system
DE69535013D1 (en) 1994-10-27 2006-07-06 Intarsia Software Llc Copyright data management system
US6424715B1 (en) 1994-10-27 2002-07-23 Mitsubishi Corporation Digital content management system and apparatus
US6515968B1 (en) 1995-03-17 2003-02-04 Worldcom, Inc. Integrated interface for real time web based viewing of telecommunications network call traffic
US6240450B1 (en) * 1995-10-16 2001-05-29 British Telecommunications Public Limited Company Network data visualization system and method for downloading visualization software to a user station after user authentication
US6473407B1 (en) 1997-09-05 2002-10-29 Worldcom, Inc. Integrated proxy interface for web based alarm management tools
CN1543611A (en) * 2001-03-02 2004-11-03 电脑联合想象公司 Method and apparatus for generating context-descriptive messages
US7249344B1 (en) 1996-10-31 2007-07-24 Citicorp Development Center, Inc. Delivery of financial services to remote devices
US7502752B1 (en) 1997-08-07 2009-03-10 Citicorp Development Center, Inc. System and method for delivering financial services
US8112330B1 (en) 1997-08-07 2012-02-07 Citibank Development Center, Inc. System and method for delivering financial services
US7668781B2 (en) 1996-10-31 2010-02-23 Citicorp Development Center, Inc. Global method and system for providing enhanced transactional functionality through a customer terminal
US7272627B2 (en) * 1997-02-06 2007-09-18 Genesys Telecommunications Laboratories, Inc. System and apparatus for pre-routing network events
US7031442B1 (en) 1997-02-10 2006-04-18 Genesys Telecommunications Laboratories, Inc. Methods and apparatus for personal routing in computer-simulated telephony
US6480600B1 (en) 1997-02-10 2002-11-12 Genesys Telecommunications Laboratories, Inc. Call and data correspondence in a call-in center employing virtual restructuring for computer telephony integrated functionality
USRE46528E1 (en) 1997-11-14 2017-08-29 Genesys Telecommunications Laboratories, Inc. Implementation of call-center outbound dialing capability at a telephony network level
USRE46243E1 (en) 1997-02-10 2016-12-20 Genesys Telecommunications Laboratories, Inc. In-band signaling for routing
US6104802A (en) 1997-02-10 2000-08-15 Genesys Telecommunications Laboratories, Inc. In-band signaling for routing
US7366900B2 (en) * 1997-02-12 2008-04-29 Verizon Laboratories, Inc. Platform-neutral system and method for providing secure remote operations over an insecure computer network
US7062781B2 (en) * 1997-02-12 2006-06-13 Verizon Laboratories Inc. Method for providing simultaneous parallel secure command execution on multiple remote hosts
ES2290986T3 (en) 1997-03-12 2008-02-16 Nomadix, Inc. Nomada transmitter or router.
US20010048738A1 (en) 1997-04-03 2001-12-06 Sbc Technology Resourses, Inc. Profile management system including user interface for accessing and maintaining profile data of user subscribed telephony services
US6778651B1 (en) * 1997-04-03 2004-08-17 Southwestern Bell Telephone Company Apparatus and method for facilitating service management of communications services in a communications network
US7290288B2 (en) * 1997-06-11 2007-10-30 Prism Technologies, L.L.C. Method and system for controlling access, by an authentication server, to protected computer resources provided via an internet protocol network
US6052726A (en) * 1997-06-30 2000-04-18 Mci Communications Corp. Delay calculation for a frame relay network
US6453352B1 (en) * 1997-07-14 2002-09-17 Electronic Data Systems Corporation Integrated electronic commerce system and method
JPH1185651A (en) * 1997-09-01 1999-03-30 Yamatake Honeywell Co Ltd Communication interface device, object equipment and communication method
CA2246130C (en) * 1997-09-04 2003-01-14 Debbie Pinard Web based help desk
US6782087B1 (en) 1997-09-19 2004-08-24 Mci Communications Corporation Desktop telephony application program for a call center agent
US6490620B1 (en) 1997-09-26 2002-12-03 Worldcom, Inc. Integrated proxy interface for web based broadband telecommunications management
US6745229B1 (en) 1997-09-26 2004-06-01 Worldcom, Inc. Web based integrated customer interface for invoice reporting
US6714979B1 (en) 1997-09-26 2004-03-30 Worldcom, Inc. Data warehousing infrastructure for web based reporting tool
US6763376B1 (en) * 1997-09-26 2004-07-13 Mci Communications Corporation Integrated customer interface system for communications network management
US7058600B1 (en) * 1997-09-26 2006-06-06 Mci, Inc. Integrated proxy interface for web based data management reports
US7225249B1 (en) * 1997-09-26 2007-05-29 Mci, Llc Integrated systems for providing communications network management services and interactive generating invoice documents
US20040193512A1 (en) * 1998-09-24 2004-09-30 Parmeshwar Gobin Web based integrated customer interface for invoice reporting
US6381644B2 (en) * 1997-09-26 2002-04-30 Mci Worldcom, Inc. Integrated proxy interface for web based telecommunications network management
US6466663B1 (en) 1997-09-30 2002-10-15 Don Ravenscroft Monitoring system client for a call center
US6490350B2 (en) * 1997-09-30 2002-12-03 Mci Communications Corporation Monitoring system for telephony resources in a call center
JP4312954B2 (en) * 1997-10-21 2009-08-12 ブリティッシュ・テレコミュニケーションズ・パブリック・リミテッド・カンパニーBritish Telecommunications Public Limited Company Information management system
US6097887A (en) * 1997-10-27 2000-08-01 Kla-Tencor Corporation Software system and method for graphically building customized recipe flowcharts
US20020194084A1 (en) * 1997-11-14 2002-12-19 Anita Surles Method and use of point-of sale terminal, which receives, transmits, stores, authorizes, reconciles, and calculates transactions electronically
US6789080B1 (en) * 1997-11-14 2004-09-07 Adobe Systems Incorporated Retrieving documents transitively linked to an initial document
US6415278B1 (en) * 1997-11-14 2002-07-02 Adobe Systems Incorporated Retrieving documents transitively linked to an initial document
US6681227B1 (en) * 1997-11-19 2004-01-20 Ns Solutions Corporation Database system and a method of data retrieval from the system
EP1031105A2 (en) * 1997-11-20 2000-08-30 Xacct Technologies, Inc. Network accounting and billing system and method
US6065120A (en) * 1997-12-09 2000-05-16 Phone.Com, Inc. Method and system for self-provisioning a rendezvous to ensure secure access to information in a database from multiple devices
US7055173B1 (en) 1997-12-19 2006-05-30 Avaya Technology Corp. Firewall pooling in a network flowswitch
US6038597A (en) * 1998-01-20 2000-03-14 Dell U.S.A., L.P. Method and apparatus for providing and accessing data at an internet site
US6363077B1 (en) * 1998-02-13 2002-03-26 Broadcom Corporation Load balancing in link aggregation and trunking
US9008075B2 (en) 2005-12-22 2015-04-14 Genesys Telecommunications Laboratories, Inc. System and methods for improving interaction routing performance
US7907598B2 (en) 1998-02-17 2011-03-15 Genesys Telecommunication Laboratories, Inc. Method for implementing and executing communication center routing strategies represented in extensible markup language
US7194757B1 (en) 1998-03-06 2007-03-20 Starguide Digital Network, Inc. Method and apparatus for push and pull distribution of multimedia
JPH11261556A (en) * 1998-03-16 1999-09-24 Fujitsu Ltd Information distribution receiving system, information distributing device, information receiver and information distribution/receiving method
US7584505B2 (en) * 2001-10-16 2009-09-01 Microsoft Corporation Inspected secure communication protocol
US6434619B1 (en) * 1998-04-29 2002-08-13 Alcatel Canada Inc. Internet-enabled service management system and method
US6339826B2 (en) 1998-05-05 2002-01-15 International Business Machines Corp. Client-server system for maintaining a user desktop consistent with server application user access permissions
US7389284B1 (en) 2000-02-29 2008-06-17 Oracle International Corporation Method and mechanism for efficient processing of remote-mapped queries
US7089331B1 (en) 1998-05-29 2006-08-08 Oracle International Corporation Method and mechanism for reducing client-side memory footprint of transmitted data
US6363421B2 (en) * 1998-05-31 2002-03-26 Lucent Technologies, Inc. Method for computer internet remote management of a telecommunication network element
US6892300B2 (en) * 1998-06-04 2005-05-10 International Business Machines Corporation Secure communication system and method of operation for conducting electronic commerce using remote vault agents interacting with a vault controller
US6718470B1 (en) * 1998-06-05 2004-04-06 Entrust Technologies Limited System and method for granting security privilege in a communication system
US20030191717A1 (en) * 1998-06-05 2003-10-09 Johnson Teddy C. High performance server data delivery system and method
US7870239B1 (en) * 1998-06-30 2011-01-11 Emc Corporation Method and system for securing network access to dynamically updateable data stored in a data storage system
US6829242B2 (en) * 1998-06-30 2004-12-07 Cisco Technology, Inc. Method and apparatus for associating PVC identifiers with domain names of home gateways
US6650342B1 (en) * 1998-06-30 2003-11-18 Samsung Electronics Co., Ltd. Method for operating network management system in a graphic user interface enviroment and network management system
US6490624B1 (en) * 1998-07-10 2002-12-03 Entrust, Inc. Session management in a stateless network system
US6665702B1 (en) 1998-07-15 2003-12-16 Radware Ltd. Load balancing
US20010037400A1 (en) * 1998-07-22 2001-11-01 Uri Raz Method and system for decreasing the user-perceived system response time in web-based systems
US20020138640A1 (en) * 1998-07-22 2002-09-26 Uri Raz Apparatus and method for improving the delivery of software applications and associated data in web-based systems
US6311221B1 (en) * 1998-07-22 2001-10-30 Appstream Inc. Streaming modules
US20010044850A1 (en) 1998-07-22 2001-11-22 Uri Raz Method and apparatus for determining the order of streaming modules
US7197570B2 (en) 1998-07-22 2007-03-27 Appstream Inc. System and method to send predicted application streamlets to a client device
DE69937242T2 (en) * 1998-08-10 2008-06-26 British Telecommunications P.L.C. Anrufleitweglenklung in an intelligent network
USRE46387E1 (en) 1998-09-11 2017-05-02 Genesys Telecommunications Laboratories, Inc. Method and apparatus for extended management of state and interaction of a remote knowledge worker from a contact center
US6874119B2 (en) * 1998-09-11 2005-03-29 Genesys Telecommunications Laboratories, Inc. Stored-media interface engine providing an abstract record of stored multimedia files within a multimedia communication center
US6985943B2 (en) 1998-09-11 2006-01-10 Genesys Telecommunications Laboratories, Inc. Method and apparatus for extended management of state and interaction of a remote knowledge worker from a contact center
US6401111B1 (en) * 1998-09-11 2002-06-04 International Business Machines Corporation Interaction monitor and interaction history for service applications
USRE46153E1 (en) 1998-09-11 2016-09-20 Genesys Telecommunications Laboratories, Inc. Method and apparatus enabling voice-based management of state and interaction of a remote knowledge worker in a contact center environment
US6711611B2 (en) 1998-09-11 2004-03-23 Genesis Telecommunications Laboratories, Inc. Method and apparatus for data-linking a mobile knowledge worker to home communication-center infrastructure
US6332154B2 (en) 1998-09-11 2001-12-18 Genesys Telecommunications Laboratories, Inc. Method and apparatus for providing media-independent self-help modules within a multimedia communication-center customer interface
US6324569B1 (en) * 1998-09-23 2001-11-27 John W. L. Ogilvie Self-removing email verified or designated as such by a message distributor for the convenience of a recipient
US6711608B1 (en) 1998-09-23 2004-03-23 John W. L. Ogilvie Method for including a self-removing code in a self-removing message
US7478142B1 (en) * 1998-09-29 2009-01-13 Netscape Communications Corporation Self-contained applications that are applied to be received by and processed within a browser environment and that have a first package that includes a manifest file and an archive of files including a markup language file and second package
US7882247B2 (en) * 1999-06-11 2011-02-01 Netmotion Wireless, Inc. Method and apparatus for providing secure connectivity in mobile and other intermittent computing environments
US6560611B1 (en) * 1998-10-13 2003-05-06 Netarx, Inc. Method, apparatus, and article of manufacture for a network monitoring system
US6341352B1 (en) * 1998-10-15 2002-01-22 International Business Machines Corporation Method for changing a security policy during processing of a transaction request
JP3935276B2 (en) * 1998-10-21 2007-06-20 キヤノン株式会社 Network device management method, apparatus, storage medium, and delivery device
US7131069B1 (en) * 1998-10-22 2006-10-31 Made2 Manage Systems, Inc. Navigational interface for ERP system
US6981222B2 (en) * 1998-10-22 2005-12-27 Made2Manage Systems, Inc. End-to-end transaction processing and statusing system and method
JP4545317B2 (en) 1998-10-28 2010-09-15 ヤフー! インコーポレイテッド Method of controlling the Internet browser interface, and can be controlled browser interface
US7010604B1 (en) 1998-10-30 2006-03-07 Science Applications International Corporation Agile network protocol for secure communications with assured system availability
US6502135B1 (en) 1998-10-30 2002-12-31 Science Applications International Corporation Agile network protocol for secure communications with assured system availability
US7418504B2 (en) 1998-10-30 2008-08-26 Virnetx, Inc. Agile network protocol for secure communications using secure domain names
US7188180B2 (en) * 1998-10-30 2007-03-06 Vimetx, Inc. Method for establishing secure communication link between computers of virtual private network
US6360269B1 (en) * 1998-11-02 2002-03-19 Nortel Networks Limited Protected keepalive message through the internet
US6453348B1 (en) * 1998-11-06 2002-09-17 Ameritech Corporation Extranet architecture
US7031963B1 (en) * 1998-11-09 2006-04-18 Unisys Corporation Green ice printout sorting and delivery program
US6691165B1 (en) * 1998-11-10 2004-02-10 Rainfinity, Inc. Distributed server cluster for controlling network traffic
US7506033B2 (en) * 1998-11-12 2009-03-17 International Business Machines Corporation System and method for remotely accessing a client in a client server environment
US8554932B1 (en) 1999-11-12 2013-10-08 Jpmorgan Chase Bank, N.A. Data exchange management system and method
US6886047B2 (en) * 1998-11-13 2005-04-26 Jp Morgan Chase Bank System and method for managing information retrievals for integrated digital and analog archives on a global basis
US6980631B1 (en) * 1998-11-17 2005-12-27 Callvision, Inc. System and method for reporting calls
JP2002531890A (en) 1998-11-30 2002-09-24 シーベル システムズ,インコーポレイティド Development tools, methods and systems in a client-server application
US6985953B1 (en) * 1998-11-30 2006-01-10 George Mason University System and apparatus for storage and transfer of secure data on web
US6266661B1 (en) * 1998-11-30 2001-07-24 Platinum Technology Ip, Inc. Method and apparatus for maintaining multi-instance database management systems with hierarchical inheritance and cross-hierarchy overrides
US6532463B1 (en) * 1998-12-01 2003-03-11 University Of Florida Web page accessing of data bases and mainframes
US6571245B2 (en) * 1998-12-07 2003-05-27 Magically, Inc. Virtual desktop in a computer network
US8266266B2 (en) 1998-12-08 2012-09-11 Nomadix, Inc. Systems and methods for providing dynamic network authorization, authentication and accounting
US7194554B1 (en) 1998-12-08 2007-03-20 Nomadix, Inc. Systems and methods for providing dynamic network authorization authentication and accounting
US6477565B1 (en) * 1999-06-01 2002-11-05 Yodlee.Com, Inc. Method and apparatus for restructuring of personalized data for transmission from a data network to connected and portable network appliances
US7672879B1 (en) 1998-12-08 2010-03-02 Yodlee.Com, Inc. Interactive activity interface for managing personal data and performing transactions over a data packet network
US20030191832A1 (en) * 1999-06-01 2003-10-09 Ramakrishna Satyavolu Method and apparatus for controlled establishment of a turnkey system providing a centralized data aggregation and summary capability to third party entities
US7085997B1 (en) 1998-12-08 2006-08-01 Yodlee.Com Network-based bookmark management and web-summary system
US8713641B1 (en) 1998-12-08 2014-04-29 Nomadix, Inc. Systems and methods for authorizing, authenticating and accounting users having transparent computer access to a network using a gateway device
US6636894B1 (en) * 1998-12-08 2003-10-21 Nomadix, Inc. Systems and methods for redirecting users having transparent computer access to a network using a gateway device having redirection capability
US8069407B1 (en) 1998-12-08 2011-11-29 Yodlee.Com, Inc. Method and apparatus for detecting changes in websites and reporting results to web developers for navigation template repair purposes
US7752535B2 (en) 1999-06-01 2010-07-06 Yodlec.com, Inc. Categorization of summarized information
US6510466B1 (en) * 1998-12-14 2003-01-21 International Business Machines Corporation Methods, systems and computer program products for centralized management of application programs on a network
US6324578B1 (en) 1998-12-14 2001-11-27 International Business Machines Corporation Methods, systems and computer program products for management of configurable application programs on a network
US6523172B1 (en) * 1998-12-17 2003-02-18 Evolutionary Technologies International, Inc. Parser translator system and method
US7356482B2 (en) * 1998-12-18 2008-04-08 Alternative Systems, Inc. Integrated change management unit
US6269395B1 (en) * 1998-12-21 2001-07-31 Nortel Networks Limited Method and system in a computer-based system for providing access to services associated with different access points
US7152070B1 (en) * 1999-01-08 2006-12-19 The Regents Of The University Of California System and method for integrating and accessing multiple data sources within a data warehouse architecture
JP2003526230A (en) * 1999-01-09 2003-09-02 ヒート タイマー コーポレーション Electronic message delivery system and method that can be used when monitoring device
US20020023207A1 (en) * 1999-01-14 2002-02-21 Olik Zbigniew T. Secure data transfer between a client and a back-end resource via an intermediary
US6442600B1 (en) * 1999-01-15 2002-08-27 Micron Technology, Inc. Method and system for centralized storage and management of electronic messages
US7320001B1 (en) * 1999-01-15 2008-01-15 Hon Hai Precision Industry, Ltd. Method for visualizing information in a data warehousing environment
US7233952B1 (en) * 1999-01-15 2007-06-19 Hon Hai Precision Industry, Ltd. Apparatus for visualizing information in a data warehousing environment
US7007029B1 (en) * 1999-01-15 2006-02-28 Metaedge Corporation System for visualizing information in a data warehousing environment
US6807632B1 (en) * 1999-01-21 2004-10-19 Emc Corporation Content addressable information encapsulation, representation, and transfer
US20010012346A1 (en) * 1999-01-29 2001-08-09 Alex Terry Interactive billing system utilizing a thin web client interface
US6898636B1 (en) * 1999-02-04 2005-05-24 Intralinks, Inc. Methods and systems for interchanging documents between a sender computer, a server and a receiver computer
JP3833409B2 (en) * 1999-02-05 2006-10-11 株式会社日立製作所 The proxy server device
US6658571B1 (en) * 1999-02-09 2003-12-02 Secure Computing Corporation Security framework for dynamically wrapping software applications executing in a computing system
US6687877B1 (en) 1999-02-17 2004-02-03 Siemens Corp. Research Inc. Web-based call center system with web document annotation
CA2264321A1 (en) * 1999-03-02 2000-09-02 Cognos Incorporated Method and apparatus for generating reports
US20030208641A1 (en) * 1999-03-09 2003-11-06 Wesemann Darren L. Software components as virtual processors
EP1037155A3 (en) * 1999-03-18 2003-11-26 Siemens Aktiengesellschaft Method for mediating between communication participants and device for implementing the method
US6388682B1 (en) * 1999-03-18 2002-05-14 International Business Machines Corporation Adaptive computer display screen window accommodating user or human factor input
US6907566B1 (en) 1999-04-02 2005-06-14 Overture Services, Inc. Method and system for optimum placement of advertisements on a webpage
US7317787B2 (en) * 2000-11-21 2008-01-08 At&T Knowledge Ventures, L.P. Voice enhancing for advance intelligent network services
US6801949B1 (en) 1999-04-12 2004-10-05 Rainfinity, Inc. Distributed server cluster with graphical user interface
DE19916490A1 (en) * 1999-04-13 2000-10-26 Alcatel Sa Monitoring the transmission quality in a digital transmission network
US6278694B1 (en) * 1999-04-16 2001-08-21 Concord Communications Inc. Collecting and reporting monitoring data from remote network probes
CA2301435C (en) * 1999-04-16 2006-10-10 At&T Corp. Method for reducing congestion in packet-switched networks
EP1186184B1 (en) * 1999-04-20 2006-07-12 Telenokia Oy Information collection method and system
US6701368B1 (en) * 1999-04-26 2004-03-02 Cisco Technology, Inc. Providing a stream of data to a browser to update properties on a page
US7756967B1 (en) 1999-04-26 2010-07-13 Mainstream Scientific, Llc Apparatus and method of hosting internet content
US20040111471A1 (en) * 1999-04-27 2004-06-10 Worldcom, Inc. Alarm monitoring system for a telecommunications network
JP3451981B2 (en) * 1999-04-30 2003-09-29 日本電気株式会社 Home data collection method of the Internet
US7016951B1 (en) * 1999-04-30 2006-03-21 Mantech Ctx Corporation System and method for network security
US6684248B1 (en) * 1999-05-03 2004-01-27 Certifiedmail.Com, Inc. Method of transferring data from a sender to a recipient during which a unique account for the recipient is automatically created if the account does not previously exist
FI107488B (en) * 1999-05-10 2001-08-15 Nokia Networks Oy The method and system of the telephone exchange system,
EP1183617A4 (en) * 1999-05-11 2007-11-14 Newsnet Ltd Signalling apparatus and method
WO2000070838A3 (en) * 1999-05-14 2002-01-10 Pivia Inc Client-server independent intermediary mechanism
US6718388B1 (en) * 1999-05-18 2004-04-06 Jp Morgan Chase Bank Secured session sequencing proxy system and method therefor
WO2000071321A3 (en) * 1999-05-21 2002-01-17 Microsoft Corp Shared views for browsing content
US6920608B1 (en) 1999-05-21 2005-07-19 E Numerate Solutions, Inc. Chart view for reusable data markup language
US7421648B1 (en) * 1999-05-21 2008-09-02 E-Numerate Solutions, Inc. Reusable data markup language
US9262383B2 (en) 1999-05-21 2016-02-16 E-Numerate Solutions, Inc. System, method, and computer program product for processing a markup document
US7249328B1 (en) * 1999-05-21 2007-07-24 E-Numerate Solutions, Inc. Tree view for reusable data markup language
US9268748B2 (en) 1999-05-21 2016-02-23 E-Numerate Solutions, Inc. System, method, and computer program product for outputting markup language documents
US9262384B2 (en) 1999-05-21 2016-02-16 E-Numerate Solutions, Inc. Markup language system, method, and computer program product
US6282544B1 (en) * 1999-05-24 2001-08-28 Computer Associates Think, Inc. Method and apparatus for populating multiple data marts in a single aggregation process
US7730172B1 (en) * 1999-05-24 2010-06-01 Computer Associates Think, Inc. Method and apparatus for reactive and deliberative service level management (SLM)
US20020023057A1 (en) * 1999-06-01 2002-02-21 Goodwin Johnathan David Web-enabled value bearing item printing
US20050080799A1 (en) * 1999-06-01 2005-04-14 Abb Flexible Automaton, Inc. Real-time information collection and distribution system for robots and electronically controlled machines
US7146505B1 (en) 1999-06-01 2006-12-05 America Online, Inc. Secure data exchange between date processing systems
US6463468B1 (en) * 1999-06-01 2002-10-08 Netzero, Inc. Targeted network video download interface
US6807549B2 (en) 1999-06-03 2004-10-19 B.I.S. Advanced Software Systems Ltd. General purpose interpreter and database for accessing enterprise servers over an internet protocol network
JP4150131B2 (en) * 1999-06-10 2008-09-17 東芝テック株式会社 Image processing system
US6889260B1 (en) * 1999-06-10 2005-05-03 Ec Enabler, Ltd Method and system for transferring information
EP1264223A4 (en) * 1999-06-11 2004-04-07 Honeywell Ltd Method and system for remotely monitoring time variant data
US6560609B1 (en) * 1999-06-14 2003-05-06 International Business Machines Corporation Delegating instance management functions to underlying resource managers
US7065785B1 (en) * 1999-06-15 2006-06-20 Siemens Communications, Inc. Apparatus and method for TOL client boundary protection
US7606760B2 (en) * 1999-06-18 2009-10-20 Echarge Corporation Method and apparatus for ordering goods, services and content over an internetwork using a virtual payment account
US7249097B2 (en) * 1999-06-18 2007-07-24 Echarge Corporation Method for ordering goods, services, and content over an internetwork using a virtual payment account
US6606657B1 (en) * 1999-06-22 2003-08-12 Comverse, Ltd. System and method for processing and presenting internet usage information
US6601088B1 (en) * 1999-06-23 2003-07-29 International Business Machines Corporation User controlled e-mail deletion
GB2368692B (en) * 1999-06-25 2003-02-12 Jacobs Rimell Ltd Automated provisioning system
US7539749B2 (en) * 2000-04-20 2009-05-26 Amdocs (Israel) Ltd. Method and apparatus for session reconstruction
US9632503B2 (en) 2001-04-18 2017-04-25 Space Data Corporation Systems and applications of lighter-than-air (LTA) platforms
US6670973B1 (en) * 1999-06-29 2003-12-30 Electronic Data Systems Corporation System and method for representing the information technology infrastructure of an organization
US6470390B1 (en) * 1999-06-29 2002-10-22 Cisco Technology, Inc. Method and apparatus for a dual connection communication session
US9643706B2 (en) 2001-04-18 2017-05-09 Space Data Corporation Systems and applications of lighter-than-air (LTA) platforms
US7356390B2 (en) 1999-06-29 2008-04-08 Space Data Corporation Systems and applications of lighter-than-air (LTA) platforms
US9053500B2 (en) * 1999-06-30 2015-06-09 Blackboard Inc. Internet-based education support system and method with multi-language capability
US20040181668A1 (en) * 1999-06-30 2004-09-16 Blew Edwin O. Methods for conducting server-side encryption/decryption-on-demand
WO2001002964A1 (en) * 1999-06-30 2001-01-11 Suntory Limited Web application system having session management/distributed management function and mechanism for operating the same
US6938081B1 (en) * 1999-06-30 2005-08-30 Level 3 Communications, Inc. Methods and systems for managing network infrastructure change including obtaining approval for the network infrastructure changes
US6628654B1 (en) * 1999-07-01 2003-09-30 Cisco Technology, Inc. Dispatching packets from a forwarding agent using tag switching
US6662223B1 (en) * 1999-07-01 2003-12-09 Cisco Technology, Inc. Protocol to coordinate network end points to measure network latency
US7058817B1 (en) 1999-07-02 2006-06-06 The Chase Manhattan Bank System and method for single sign on process for websites with multiple applications and services
US7346695B1 (en) 2002-10-28 2008-03-18 F5 Networks, Inc. System and method for performing application level persistence
US7644366B1 (en) * 1999-07-30 2010-01-05 Computer Associates Think, Inc. Method and system for displaying a plurality of discrete files in a compound file
US7100195B1 (en) * 1999-07-30 2006-08-29 Accenture Llp Managing user information on an e-commerce system
US6880126B1 (en) 1999-08-03 2005-04-12 International Business Machines Corporation Controlling presentation of a GUI, using view controllers created by an application mediator, by identifying a destination to access a target to retrieve data
US6286104B1 (en) * 1999-08-04 2001-09-04 Oracle Corporation Authentication and authorization in a multi-tier relational database management system
US7929978B2 (en) 1999-12-01 2011-04-19 Genesys Telecommunications Laboratories, Inc. Method and apparatus for providing enhanced communication capability for mobile devices on a virtual private network
US7130879B1 (en) 1999-08-10 2006-10-31 Alexandre Dayon System for publishing, organizing, accessing and distributing information in a computer network
US6859834B1 (en) * 1999-08-13 2005-02-22 Sun Microsystems, Inc. System and method for enabling application server request failover
US6879995B1 (en) * 1999-08-13 2005-04-12 Sun Microsystems, Inc. Application server message logging
US7146233B2 (en) * 2000-02-11 2006-12-05 Sun Microsystems, Inc. Request queue management
US6779016B1 (en) 1999-08-23 2004-08-17 Terraspring, Inc. Extensible computing system
US7142530B1 (en) * 1999-08-27 2006-11-28 Bellsouth Intellectual Property Corp. Methods and systems of network management
US6772333B1 (en) * 1999-09-01 2004-08-03 Dickens Coal Llc Atomic session-start operation combining clear-text and encrypted sessions to provide id visibility to middleware such as load-balancers
US7483967B2 (en) * 1999-09-01 2009-01-27 Ximeta Technology, Inc. Scalable server architecture based on asymmetric 3-way TCP
US6493745B1 (en) * 1999-09-03 2002-12-10 Microsoft Corporation Message processing technique to improve client computer response to user input
WO2001018714A8 (en) * 1999-09-08 2001-11-15 Wizard Technologies Inc Transaction and account management system
US6687745B1 (en) * 1999-09-14 2004-02-03 Droplet, Inc System and method for delivering a graphical user interface of remote applications over a thin bandwidth connection
US9092535B1 (en) 1999-09-21 2015-07-28 Google Inc. E-mail embedded textual hyperlink object
US6360221B1 (en) 1999-09-21 2002-03-19 Neostar, Inc. Method and apparatus for the production, delivery, and receipt of enhanced e-mail
US7840639B1 (en) * 1999-09-21 2010-11-23 G&H Nevada-Tek Method and article of manufacture for an automatically executed application program associated with an electronic message
FI109165B (en) * 1999-09-24 2002-05-31 Elisa Comm Oyj A method for controlling computer network traffic
US6877036B1 (en) * 1999-09-24 2005-04-05 Akamba Corporation System and method for managing connections between a client and a server
US7206833B1 (en) * 1999-09-30 2007-04-17 Intel Corporation Platform independent alert detection and management
US7318089B1 (en) 1999-09-30 2008-01-08 Intel Corporation Method and apparatus for performing network-based control functions on an alert-enabled managed client
US6922722B1 (en) 1999-09-30 2005-07-26 Intel Corporation Method and apparatus for dynamic network configuration of an alert-based client
US6633851B1 (en) 1999-10-01 2003-10-14 B-50.Com, Llc Systems and methods for generating custom reports based on point-of-sale data
US6874010B1 (en) 1999-10-01 2005-03-29 Accenture Llp Base service architectures for netcentric computing systems
US6988249B1 (en) 1999-10-01 2006-01-17 Accenture Llp Presentation service architectures for netcentric computing systems
WO2001025964A3 (en) 1999-10-01 2001-11-29 Accenture Llp Base service architectures for netcentric computing systems
US7068680B1 (en) 1999-10-01 2006-06-27 Accenture Llp Communication service architectures for netcentric computing systems
US7020697B1 (en) * 1999-10-01 2006-03-28 Accenture Llp Architectures for netcentric computing systems
US7610289B2 (en) * 2000-10-04 2009-10-27 Google Inc. System and method for monitoring and analyzing internet traffic
US7904569B1 (en) * 1999-10-06 2011-03-08 Gelvin David C Method for remote access of vehicle components
US7366696B1 (en) * 1999-10-08 2008-04-29 Checkfree Corporation Electronic billing with flexible biller controlled electronic bill presentment
WO2001028212A1 (en) * 1999-10-08 2001-04-19 Nortel Networks Limited Method, apparatus, and article of manufacture for web-based control of a call server
US6522333B1 (en) * 1999-10-08 2003-02-18 Electronic Arts Inc. Remote communication through visual representations
US7519905B2 (en) * 1999-10-12 2009-04-14 Webmd Corp. Automatic formatting and validating of text for a markup language graphical user interface
JP3274441B2 (en) * 1999-10-13 2002-04-15 エヌ・ティ・ティ・コムウェア株式会社 Call detail collection device, call detail processing apparatus, call detail processor, call detail management device, call detail processing system, call detail collection method, call detail processing method, call detail processing method and call detail managing
US6798753B1 (en) * 1999-10-14 2004-09-28 International Business Machines Corporation Automatically establishing conferences from desktop applications over the Internet
US7467211B1 (en) * 1999-10-18 2008-12-16 Cisco Technology Inc. Remote computer system management through an FTP internet connection
US7233929B1 (en) 1999-10-18 2007-06-19 Stamps.Com Postal system intranet and commerce processing for on-line value bearing system
US7216110B1 (en) * 1999-10-18 2007-05-08 Stamps.Com Cryptographic module for secure processing of value-bearing items
WO2001029779A1 (en) * 1999-10-18 2001-04-26 Stamps.Com Secure and recoverable database for on-line value-bearing item system
EP1224629A1 (en) 1999-10-18 2002-07-24 Stamps.Com Role assignments in a cryptographic module for secure processing of value-bearing items
US6633312B1 (en) 1999-10-19 2003-10-14 Nortel Networks Limited Method and apparatus for selecting network entities
US6496977B1 (en) * 1999-10-21 2002-12-17 International Business Machines Corporation Method and system for implementing network filesystem-based aid for computer operating system upgrades
WO2001031885A3 (en) * 1999-10-22 2002-01-17 Nomadix Inc Gateway device having an xml interface and associated method
US6851089B1 (en) * 1999-10-25 2005-02-01 Amazon.Com, Inc. Software application and associated methods for generating a software layer for structuring semistructured information
US6978381B1 (en) * 1999-10-26 2005-12-20 International Business Machines Corporation Enhancement to a system for automated generation of file access control system commands
US6714977B1 (en) * 1999-10-27 2004-03-30 Netbotz, Inc. Method and system for monitoring computer networks and equipment
US8271626B2 (en) 2001-01-26 2012-09-18 American Power Conversion Corporation Methods for displaying physical network topology and environmental status by location, organization, or responsible party
WO2001031874A3 (en) * 1999-10-28 2002-01-24 Chase Manhattan Bank Nat Ass Secured session sequencing proxy system supporting multiple applications and method therefor
US6779177B1 (en) 1999-10-28 2004-08-17 International Business Machines Corporation Mechanism for cross channel multi-server multi-protocol multi-data model thin clients
US6886103B1 (en) * 1999-10-28 2005-04-26 Lucent Technologies Inc. Method and apparatus for extending network address translation for unsupported protocols
US6862686B1 (en) 1999-10-29 2005-03-01 International Business Machines Corporation Method and apparatus in a data processing system for the separation of role-based permissions specification from its corresponding implementation of its semantic behavior
US7181686B1 (en) 1999-10-29 2007-02-20 International Business Machines Corporation Selecting screens in a GUI using events generated by a set of view controllers
US6675193B1 (en) * 1999-10-29 2004-01-06 Invensys Software Systems Method and system for remote control of a local system
US20050149559A1 (en) * 1999-11-01 2005-07-07 Oppedahl & Larson Llp Status monitoring system
WO2002041597A3 (en) * 2000-11-17 2002-11-21 Ipwireless Inc Use of internet web technology for wireless internet access
US7571131B1 (en) * 1999-11-05 2009-08-04 Ford Motor Company Method of conducting online competitive price quoting events
JP3565490B2 (en) * 1999-11-09 2004-09-15 インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Maschines Corporation Client-server system, a server, a client, a proxy server control method, proxy server function provides a method and storage medium
US20040193695A1 (en) * 1999-11-10 2004-09-30 Randy Salo Secure remote access to enterprise networks
US7370004B1 (en) * 1999-11-15 2008-05-06 The Chase Manhattan Bank Personalized interactive network architecture
US6948175B1 (en) * 1999-11-16 2005-09-20 Ricoh Company, Ltd. Method and system of remote diagnostic, control and information collection using a dynamic linked library
US6931111B1 (en) * 1999-11-24 2005-08-16 Netgen Communications, Inc. Methods and systems for providing communications services
US6782425B1 (en) * 1999-11-24 2004-08-24 Unisys Corporation Session based security profile for internet access of an enterprise server
JP3395896B2 (en) * 1999-11-25 2003-04-14 株式会社ジャストシステム Information providing system and method, the client device and the intermediary device
JP2001216226A (en) * 1999-11-26 2001-08-10 Mitsubishi Electric Corp Inter-application data transmission/reception system and method threfor, and computer-readable recording medium having program for making computer operate inter-application data transmission/reception method recording thereon
US6813278B1 (en) * 1999-11-30 2004-11-02 Accenture Llp Process for submitting and handling a service request in a local service management system
US6961778B2 (en) * 1999-11-30 2005-11-01 Accenture Llp Management interface between a core telecommunication system and a local service provider
US6836803B1 (en) 1999-11-30 2004-12-28 Accenture Llp Operations architecture to implement a local service activation management system
US6732167B1 (en) * 1999-11-30 2004-05-04 Accenture L.L.P. Service request processing in a local service activation management environment
US7966259B1 (en) 1999-12-09 2011-06-21 Amazon.Com, Inc. System and methods for facilitating transactions on, and personalizing web pages of, third party web sites
US7506358B1 (en) * 1999-12-09 2009-03-17 Cisco Technology, Inc. Method and apparatus supporting network communications through a firewall
US7765581B1 (en) * 1999-12-10 2010-07-27 Oracle America, Inc. System and method for enabling scalable security in a virtual private network
US7336790B1 (en) 1999-12-10 2008-02-26 Sun Microsystems Inc. Decoupling access control from key management in a network
US6977929B1 (en) 1999-12-10 2005-12-20 Sun Microsystems, Inc. Method and system for facilitating relocation of devices on a network
US6938169B1 (en) 1999-12-10 2005-08-30 Sun Microsystems, Inc. Channel-specific file system views in a private network using a public-network infrastructure
US6970941B1 (en) 1999-12-10 2005-11-29 Sun Microsystems, Inc. System and method for separating addresses from the delivery scheme in a virtual private network
DE20020773U1 (en) * 1999-12-10 2001-04-19 Firstgate Internet Ag Server means for transmitting electronic data sets
US20010044840A1 (en) * 1999-12-13 2001-11-22 Live Networking, Inc. Method and system for real-tme monitoring and administration of computer networks
US6668275B1 (en) * 1999-12-17 2003-12-23 Honeywell International Inc. System and method for multiprocessor management
US6823452B1 (en) * 1999-12-17 2004-11-23 International Business Machines Corporation Providing end-to-end user authentication for host access using digital certificates
US6775658B1 (en) * 1999-12-21 2004-08-10 Mci, Inc. Notification by business rule trigger control
US7447509B2 (en) 1999-12-22 2008-11-04 Celeritasworks, Llc Geographic management system
US8452776B2 (en) * 1999-12-22 2013-05-28 Celeritasworks, Llc Spatial data portal
US6343290B1 (en) * 1999-12-22 2002-01-29 Celeritas Technologies, L.L.C. Geographic network management system
US7523190B1 (en) * 1999-12-23 2009-04-21 Bickerstaff Cynthia L Real-time performance assessment of large area network user experience
US6934723B2 (en) * 1999-12-23 2005-08-23 International Business Machines Corporation Method for file system replication with broadcasting and XDSM
US6912567B1 (en) * 1999-12-27 2005-06-28 International Business Machines Corp. Broadband multi-service proxy server system and method of operation for internet services of user's choice
US20010034842A1 (en) * 1999-12-30 2001-10-25 Chacko Matthew Kochumalayil Common network security
US20010047385A1 (en) * 1999-12-30 2001-11-29 Jeffrey Tuatini Passthru to shared service funtionality
US6721786B1 (en) * 2000-01-06 2004-04-13 International Business Machines Corporation Method and apparatus for balancing bandwidth usage in a browser
US20050207444A1 (en) * 2001-01-12 2005-09-22 Eci Telecom Ltd. Hybrid network element for a multi-protocol layered transmissions network and a graphical representation of the network
DE60140499D1 (en) * 2000-01-14 2009-12-31 Eci Telecom Ltd A method for generating a client / server model in a layered multi - protocol transmission network
US7188176B1 (en) * 2000-01-20 2007-03-06 Priceline.Com Incorporated Apparatus, system, and method for maintaining a persistent data state on a communications network
US6795859B2 (en) * 2000-01-21 2004-09-21 Dennis Parker Scalable server architecture systems and methods
US20010047261A1 (en) * 2000-01-24 2001-11-29 Peter Kassan Partially automated interactive dialog
EP1250637A1 (en) * 2000-01-27 2002-10-23 Hummingbird Ltd. A method and system for implementing a common user logon to multiple applications
US20040205473A1 (en) * 2000-01-27 2004-10-14 Gwyn Fisher Method and system for implementing an enterprise information portal
US6877023B1 (en) * 2000-01-28 2005-04-05 Softwired, Inc. Messaging system for delivering data in the form of portable message formats between message clients
GB0002019D0 (en) * 2000-01-29 2000-03-22 Ibm Data migration tool
US7379981B2 (en) * 2000-01-31 2008-05-27 Kenneth W. Garrard Wireless communication enabled meter and network
US7003571B1 (en) * 2000-01-31 2006-02-21 Telecommunication Systems Corporation Of Maryland System and method for re-directing requests from browsers for communication over non-IP based networks
US8019836B2 (en) * 2002-01-02 2011-09-13 Mesh Comm, Llc Wireless communication enabled meter and network
US7739362B1 (en) * 2000-02-02 2010-06-15 Cisco Technology, Inc. Method and apparatus for browsing a management information base
US6883032B1 (en) * 2000-02-02 2005-04-19 Lucent Technologies Inc. Method and system for collecting data on the internet
US6647392B1 (en) * 2000-02-04 2003-11-11 International Business Machines Corporation Method and apparatus for the request brokering of standardized reports
US7249155B1 (en) * 2000-02-09 2007-07-24 International Business Machines Corporation Method for processing a request to multiple instances of a server program
US8392578B1 (en) * 2000-02-09 2013-03-05 Charles Schwab & Co., Inc. Method and apparatus for controlling access to a website
US6931419B1 (en) * 2000-02-11 2005-08-16 Hallmark Cards Incorporated Data management system for automatically accessing, maintaining, propagating user data among plurality of communities, each of which contains plurality of members
US8290809B1 (en) 2000-02-14 2012-10-16 Ebay Inc. Determining a community rating for a user using feedback ratings of related users in an electronic environment
US7257542B2 (en) * 2000-02-16 2007-08-14 Stamps.Com Secure on-line ticketing
US7024457B1 (en) * 2000-02-17 2006-04-04 J2 Global Communications, Inc. E-mail synchronization between heterogeneous mail servers
WO2001061568A9 (en) 2000-02-17 2002-04-11 Numerate Solutions Inc E Rdl search engine
US6671728B1 (en) * 2000-02-18 2003-12-30 G.E. Information Services, Inc. Abstract initiator
JP2001237991A (en) * 2000-02-23 2001-08-31 Kansai Nippon Denki Tsushin System Kk Caller no-charge communication system and method
WO2001063946A1 (en) * 2000-02-23 2001-08-30 Nexterna, Inc. System and method for dynamically routing messages transmitted from mobile platforms
US20020156860A1 (en) * 2000-02-25 2002-10-24 Finke Alan D. Personal server system
US6584465B1 (en) * 2000-02-25 2003-06-24 Eastman Kodak Company Method and system for search and retrieval of similar patterns
US9614934B2 (en) 2000-02-29 2017-04-04 Paypal, Inc. Methods and systems for harvesting comments regarding users on a network-based facility
US7428505B1 (en) 2000-02-29 2008-09-23 Ebay, Inc. Method and system for harvesting feedback and comments regarding multiple items from users of a network-based transaction facility
JP2001243182A (en) * 2000-02-29 2001-09-07 Nec Corp Server system, and method for interlocking web contents with the server system
US8843617B2 (en) * 2000-03-01 2014-09-23 Printeron Inc. Multi-stage polling mechanism and system for the transmission and processing control of network resource data
US6760750B1 (en) * 2000-03-01 2004-07-06 Polycom Israel, Ltd. System and method of monitoring video and/or audio conferencing through a rapid-update web site
CA2299824C (en) * 2000-03-01 2012-02-21 Spicer Corporation Network resource control system
JP3926963B2 (en) * 2000-03-03 2007-06-06 富士通株式会社 State setting system and method
US7139686B1 (en) * 2000-03-03 2006-11-21 The Mathworks, Inc. Report generator for a mathematical computing environment
WO2001067355A2 (en) 2000-03-07 2001-09-13 American Express Travel Related Services Company, Inc. System for facilitating a transaction
WO2001067304A1 (en) * 2000-03-07 2001-09-13 Hotlens.Com Inc. Server-side web browsing and multiple lens system, method and apparatus
US7281040B1 (en) 2000-03-07 2007-10-09 Cisco Technology, Inc. Diagnostic/remote monitoring by email
US7340532B2 (en) * 2000-03-10 2008-03-04 Akamai Technologies, Inc. Load balancing array packet routing system
CA2301996A1 (en) * 2000-03-13 2001-09-13 Spicer Corporation Wireless attachment enabling
JP4290309B2 (en) * 2000-03-13 2009-07-01 シャープ株式会社 Information communication apparatus, information communication method, and remote management system
US8645137B2 (en) 2000-03-16 2014-02-04 Apple Inc. Fast, language-independent method for user authentication by voice
US6971086B2 (en) * 2000-03-16 2005-11-29 Silicon Graphics, Inc. Common user interface development toolkit for a system administration program
US7739334B1 (en) * 2000-03-17 2010-06-15 Visto Corporation System and method for automatically forwarding email and email events via a computer network to a server computer
US7624172B1 (en) * 2000-03-17 2009-11-24 Aol Llc State change alerts mechanism
US9736209B2 (en) 2000-03-17 2017-08-15 Facebook, Inc. State change alerts mechanism
US7080035B1 (en) * 2000-03-20 2006-07-18 Bellsouth Intellectual Property Corp. System and method for notifying an electronic billing vendor of a customer status change
US7082471B2 (en) * 2000-03-20 2006-07-25 International Business Machines Corporation Method and system of dispatching socks traffic using type of service (TOS) field of IP datagrams
WO2001071523A1 (en) * 2000-03-20 2001-09-27 Hotlens.Com Inc. Transparent user and session management for web applications
US20060288212A1 (en) * 2001-03-20 2006-12-21 Gutenberg Printing Llc Transparent user and session management for web applications
WO2001071992A3 (en) * 2000-03-22 2002-04-04 Omnipod Inc Integrated system and method of providing online access to files and information
US6963875B2 (en) * 2000-03-23 2005-11-08 General Atomics Persistent archives
US7177901B1 (en) * 2000-03-27 2007-02-13 International Business Machines Corporation Method, system, and computer program product to redirect requests from content servers to load distribution servers and to correct bookmarks
US20020004850A1 (en) * 2000-03-29 2002-01-10 Krishna Sudarshan System and method of providing a messaging engine for an enterprise javabeans enabled server to achieve container managed asynchronous functionality
US6917961B2 (en) * 2000-03-30 2005-07-12 Kettera Software, Inc. Evolving interactive dialog box for an internet web page
US8621001B2 (en) 2000-03-30 2013-12-31 Ebay Inc. System and method for dynamically changing the content of an information display
US6965880B2 (en) * 2000-03-30 2005-11-15 Fujitsu Limited Transaction number management method in network commodity sales
CA2404014A1 (en) * 2000-03-30 2001-10-11 Cygent, Inc. System and method for establishing electronic business systems for supporting communications services commerce
US20020059216A1 (en) * 2000-03-31 2002-05-16 Gowen Richard C. Decision support system and method
US6950857B1 (en) * 2000-03-31 2005-09-27 Palmsource, Inc. Secure server-based indentification for simplified online transaction processing with palmtop computer
US6779039B1 (en) 2000-03-31 2004-08-17 Avaya Technology Corp. System and method for routing message traffic using a cluster of routers sharing a single logical IP address distinct from unique IP addresses of the routers
US6880089B1 (en) * 2000-03-31 2005-04-12 Avaya Technology Corp. Firewall clustering for multiple network servers
US6738811B1 (en) * 2000-03-31 2004-05-18 Supermicro Computer, Inc. Method and architecture for monitoring the health of servers across data networks
US6970931B1 (en) * 2000-04-03 2005-11-29 International Business Machines Corporation Method for translucent online interaction
JP4654407B2 (en) * 2000-04-08 2011-03-23 オラクル・アメリカ・インコーポレイテッド A method and apparatus for dealing with the events received by the server socket
US7814208B2 (en) * 2000-04-11 2010-10-12 Science Applications International Corporation System and method for projecting content beyond firewalls
WO2001080114A1 (en) * 2000-04-13 2001-10-25 Worldlink Information Technology Systems Limited Apparatus and a method for supplying information
US7509274B2 (en) 2000-04-17 2009-03-24 Kam Kendrick W Internet-based system for identification, measurement and ranking of investment portfolio management, and operation of a fund supermarket, including “best investor” managed funds
US6732115B2 (en) * 2000-04-27 2004-05-04 Hyperion Solutions Corporation Chameleon measure and metric calculation
EP1410248A2 (en) * 2000-04-17 2004-04-21 Medical Software Solutions, Inc. Method and apparatus for applet-generated screen displays using computer database and programming language
US6941311B2 (en) 2000-04-27 2005-09-06 Hyperion Solutions Corporation Aggregate navigation system
US7072897B2 (en) * 2000-04-27 2006-07-04 Hyperion Solutions Corporation Non-additive measures and metric calculation
US6662174B2 (en) * 2000-04-17 2003-12-09 Brio Software, Inc. Analytical server including metrics engine
CA2404258A1 (en) * 2000-04-17 2001-10-25 Marketocracy Inc. Internet-based system for identification, measurement and ranking of investment portfolio management, and operation of a fund supermarket, including "best investor" managed funds
US6748394B2 (en) 2000-04-27 2004-06-08 Hyperion Solutions Corporation Graphical user interface for relational database
US7080090B2 (en) 2000-04-27 2006-07-18 Hyperion Solutions Corporation Allocation measures and metric calculations in star schema multi-dimensional data warehouse
US7167859B2 (en) * 2000-04-27 2007-01-23 Hyperion Solutions Corporation Database security
WO2001080033A3 (en) * 2000-04-17 2002-10-03 Circadence Corp System and method for implementing application -independent functionality within a network infrastructure
US7478403B1 (en) * 2000-04-21 2009-01-13 Sun Microsystems, Inc. Secure access to managed network objects using a configurable platform-independent gateway providing individual object-level access control
US8239445B1 (en) * 2000-04-25 2012-08-07 International Business Machines Corporation URL-based sticky routing tokens using a server-side cookie jar
US6615201B1 (en) * 2000-04-25 2003-09-02 Lucent Technologies Computer network management
US7814011B1 (en) * 2000-04-27 2010-10-12 Accenture Llp System for calculating a support payment in a network-based child support framework
US7716059B1 (en) * 2000-04-27 2010-05-11 Accenture Global Services Gmbh Network-based child support framework
US20020065673A1 (en) * 2000-04-28 2002-05-30 Rooke William Armstrong Business intelligence system
US7343310B1 (en) 2000-04-28 2008-03-11 Travelers Property Casualty Corp. System and method for providing web-based user interface to legacy, personal-lines insurance applications
JP2001312509A (en) * 2000-04-28 2001-11-09 Fujitsu Ltd System and recording medium for distributing electronic data
US7016858B1 (en) * 2000-05-02 2006-03-21 Ford Motor Company Integrated supplier secondary characteristic reporting method
US6874084B1 (en) * 2000-05-02 2005-03-29 International Business Machines Corporation Method and apparatus for establishing a secure communication connection between a java application and secure server
JP2001318897A (en) * 2000-05-02 2001-11-16 Nec Corp User authentication method, network system to be used for the method, and recording medium recorded with its control program
US20020057803A1 (en) * 2000-05-05 2002-05-16 Loos Michael T. System and method for communicating in a mobile domain across non-persistent data links
US6785713B1 (en) 2000-05-08 2004-08-31 Citrix Systems, Inc. Method and apparatus for communicating among a network of servers utilizing a transport mechanism
US6883019B1 (en) * 2000-05-08 2005-04-19 Intel Corporation Providing information to a communications device
US6785726B1 (en) 2000-05-08 2004-08-31 Citrix Systems, Inc. Method and apparatus for delivering local and remote server events in a similar fashion
US6789112B1 (en) * 2000-05-08 2004-09-07 Citrix Systems, Inc. Method and apparatus for administering a server having a subsystem in communication with an event channel
US7426558B1 (en) 2000-05-11 2008-09-16 Thomson Licensing Method and system for controlling and auditing content/service systems
US7421541B2 (en) * 2000-05-12 2008-09-02 Oracle International Corporation Version management of cached permissions metadata
GB0011599D0 (en) * 2000-05-15 2000-07-05 Ridgeway Systems & Software Lt Direct slave addressing to indirect slave addressing
US7640580B1 (en) * 2000-05-17 2009-12-29 F5 Networks, Inc. Method and apparatus for accessing a computer behind a firewall
US7490050B2 (en) * 2000-05-19 2009-02-10 Travelers Property Casualty Corp. Method and system for furnishing an on-line quote for an insurance product
US8176145B1 (en) 2000-05-19 2012-05-08 The Travelers Indemnity Company System and method for providing insurance data processing services via a user interface
US20020046064A1 (en) * 2000-05-19 2002-04-18 Hector Maury Method and system for furnishing an on-line quote for an insurance product
US6934749B1 (en) * 2000-05-20 2005-08-23 Ciena Corporation Tracking distributed data retrieval in a network device
US7693976B2 (en) * 2000-07-11 2010-04-06 Ciena Corporation Granular management of network resources
US7266595B1 (en) * 2000-05-20 2007-09-04 Ciena Corporation Accessing network device data through user profiles
US20020116282A1 (en) * 2000-05-23 2002-08-22 Martin Jeffrey W. Methods and systems for correlating consumption information with distribution entities
US7120629B1 (en) * 2000-05-24 2006-10-10 Reachforce, Inc. Prospects harvester system for providing contact data about customers of product or service offered by business enterprise extracting text documents selected from newsgroups, discussion forums, mailing lists, querying such data to provide customers who confirm to business profile data
US7096220B1 (en) 2000-05-24 2006-08-22 Reachforce, Inc. Web-based customer prospects harvester system
US7003517B1 (en) * 2000-05-24 2006-02-21 Inetprofit, Inc. Web-based system and method for archiving and searching participant-based internet text sources for customer lead data
US7082427B1 (en) 2000-05-24 2006-07-25 Reachforce, Inc. Text indexing system to index, query the archive database document by keyword data representing the content of the documents and by contact data associated with the participant who generated the document
US7650314B1 (en) 2001-05-25 2010-01-19 American Express Travel Related Services Company, Inc. System and method for securing a recurrent billing transaction
CN1878180A (en) * 2000-05-29 2006-12-13 诺基亚有限公司 Synchronization method
US6870331B2 (en) * 2000-05-31 2005-03-22 Sarnoff Corporation Space-saving cathode ray tube employing a non-self-converging deflection yoke
US7103664B1 (en) * 2000-05-31 2006-09-05 International Business Machines Corporation Method, system and program products for ordering lists of service addresses to provide load balancing of a clustered environment
US7136913B2 (en) * 2000-05-31 2006-11-14 Lab 7 Networks, Inc. Object oriented communication among platform independent systems across a firewall over the internet using HTTP-SOAP
US20030229524A1 (en) * 2000-06-01 2003-12-11 Eran Reuveni System for workflow analysis and response
US6539384B1 (en) 2000-06-02 2003-03-25 Bellsouth Intellectual Property Corporation Browser on test equipment
US7523191B1 (en) * 2000-06-02 2009-04-21 Yahoo! Inc. System and method for monitoring user interaction with web pages
US7962603B1 (en) 2000-06-06 2011-06-14 Nobuyoshi Morimoto System and method for identifying individual users accessing a web site
US7130853B2 (en) * 2000-06-06 2006-10-31 Fair Isaac Corporation Datamart including routines for extraction, accessing, analyzing, transformation of data into standardized format modeled on star schema
JP2001350720A (en) * 2000-06-06 2001-12-21 Sony Corp System, device and method for providing information and program storage medium
US7280971B1 (en) * 2000-06-09 2007-10-09 At&T Bls Intellectual Property, Inc. Method and system for server-based error processing in support of legacy-based usage and billing systems
US20020087884A1 (en) * 2000-06-12 2002-07-04 Hovav Shacham Method and apparatus for enhancing network security protection server performance
US20020039420A1 (en) * 2000-06-12 2002-04-04 Hovav Shacham Method and apparatus for batched network security protection server performance
US7426530B1 (en) * 2000-06-12 2008-09-16 Jpmorgan Chase Bank, N.A. System and method for providing customers with seamless entry to a remote server
GB0014325D0 (en) * 2000-06-12 2000-08-02 Koninkl Philips Electronics Nv Computer profile update system
WO2001097452A1 (en) * 2000-06-13 2001-12-20 Telefonaktiebolaget Lm Ericsson (Publ) Authentication process for an event management system
US7069434B1 (en) * 2000-06-13 2006-06-27 Hewlett-Packard Development Company, L.P. Secure data transfer method and system
US6732101B1 (en) * 2000-06-15 2004-05-04 Zix Corporation Secure message forwarding system detecting user's preferences including security preferences
DE10028842A1 (en) * 2000-06-15 2002-01-03 Ralf Mimoun Operation surface generating method involves converting position and function of individual components on operation surface into standard code so that browser will return inputs of user in demanded format
US8972717B2 (en) * 2000-06-15 2015-03-03 Zixcorp Systems, Inc. Automatic delivery selection for electronic content
US7673045B1 (en) * 2000-06-15 2010-03-02 Microsoft Corporation Multiple site automated logout
US20020093527A1 (en) * 2000-06-16 2002-07-18 Sherlock Kieran G. User interface for a security policy system and method
US7917647B2 (en) 2000-06-16 2011-03-29 Mcafee, Inc. Method and apparatus for rate limiting
US20040073617A1 (en) 2000-06-19 2004-04-15 Milliken Walter Clark Hash-based systems and methods for detecting and preventing transmission of unwanted e-mail
US9444785B2 (en) * 2000-06-23 2016-09-13 Cloudshield Technologies, Inc. Transparent provisioning of network access to an application
US6768984B2 (en) * 2000-06-27 2004-07-27 Metapower Llc Method and apparatus for process design
CA2312656A1 (en) * 2000-06-27 2001-12-27 Raymond Morin Real time management software with alarm and interactive dashboard
US20020078131A1 (en) * 2000-06-28 2002-06-20 Qwest Communications International Inc. Method and system for presenting operational data by geographical location
US8447967B1 (en) 2000-06-29 2013-05-21 Datamotion, Inc. Controlled message distribution
US7051209B1 (en) * 2000-06-29 2006-05-23 Intel Corporation System and method for creation and use of strong passwords
WO2002003604A3 (en) * 2000-06-29 2002-08-01 Cachestream Corp Digital rights management
US6882730B1 (en) * 2000-06-29 2005-04-19 Intel Corporation Method for secure distribution and configuration of asymmetric keying material into semiconductor devices
US7076534B1 (en) * 2000-06-30 2006-07-11 Microsoft Corporation Server-side scripting that enables creation of customized documents for clients
US6978232B1 (en) * 2000-06-30 2005-12-20 Interland, Inc. Method and system of demonstrating a service that provides computerized transactions using a computer network
US7032110B1 (en) 2000-06-30 2006-04-18 Landesk Software Limited PKI-based client/server authentication
US7281046B1 (en) * 2000-06-30 2007-10-09 Covad Communications Company Application program interface for automating high speed network access ordering and provisioning processes
US20020007382A1 (en) * 2000-07-06 2002-01-17 Shinichi Nojima Computer having character input function,method of carrying out process depending on input characters, and storage medium
US7194764B2 (en) 2000-07-10 2007-03-20 Oracle International Corporation User authentication
JP4386634B2 (en) * 2000-07-10 2009-12-16 富士通株式会社 Network integrated management system
US9038170B2 (en) * 2000-07-10 2015-05-19 Oracle International Corporation Logging access system events
US7249369B2 (en) * 2000-07-10 2007-07-24 Oracle International Corporation Post data processing
US7124203B2 (en) 2000-07-10 2006-10-17 Oracle International Corporation Selective cache flushing in identity and access management systems
US6986038B1 (en) * 2000-07-11 2006-01-10 International Business Machines Corporation Technique for synchronizing security credentials from a master directory, platform, or registry
US6766353B1 (en) * 2000-07-11 2004-07-20 Motorola, Inc. Method for authenticating a JAVA archive (JAR) for portable devices
US7234060B1 (en) * 2000-07-11 2007-06-19 Amdur Eugene Generation and use of digital signatures
US7099933B1 (en) * 2000-07-11 2006-08-29 Nortel Networks Limited System and method for regulating web site access
US6986039B1 (en) * 2000-07-11 2006-01-10 International Business Machines Corporation Technique for synchronizing security credentials using a trusted authenticating domain
US6785666B1 (en) * 2000-07-11 2004-08-31 Revenue Science, Inc. Method and system for parsing navigation information
US7774790B1 (en) * 2000-07-18 2010-08-10 Apple Inc. Event logging and performance analysis system for applications
US6976164B1 (en) * 2000-07-19 2005-12-13 International Business Machines Corporation Technique for handling subsequent user identification and password requests with identity change within a certificate-based host session
US6891940B1 (en) * 2000-07-19 2005-05-10 Sbc Technology Resources, Inc. System and method for providing remote access to telecommunications services
US6839745B1 (en) * 2000-07-19 2005-01-04 Verizon Corporate Services Group Inc. System and method for generating reports in a telecommunication system
JP2002032216A (en) * 2000-07-19 2002-01-31 Fujitsu Ltd Hosting device for application
US6934848B1 (en) * 2000-07-19 2005-08-23 International Business Machines Corporation Technique for handling subsequent user identification and password requests within a certificate-based host session
US7085927B1 (en) * 2000-07-20 2006-08-01 Ge Medical Systems, Inc. Secure data report preparation and delivery
US7333939B1 (en) 2000-07-21 2008-02-19 Travelers Property Casualty Corp. Method for providing web-based insurance data processing services to users
GB0018547D0 (en) 2000-07-28 2000-09-13 Ridgeway Systems & Software Lt Audio-video telephony with port address translation
US20060031456A1 (en) * 2000-07-31 2006-02-09 Marcos Della Method and apparatus for transmitting data between devices in a web networking environment
US7130822B1 (en) * 2000-07-31 2006-10-31 Cognos Incorporated Budget planning
US7287095B2 (en) * 2000-08-03 2007-10-23 Fujitsu Limited Processing method, processing apparatus and storage medium
US20040015725A1 (en) * 2000-08-07 2004-01-22 Dan Boneh Client-side inspection and processing of secure content
US7137143B2 (en) 2000-08-07 2006-11-14 Ingrian Systems Inc. Method and system for caching secure web content
WO2002013035A1 (en) * 2000-08-07 2002-02-14 Active Data Exchange, Inc. Syndication methodology to dynamically place digital assets on non-related web sites
US6904598B2 (en) * 2000-08-08 2005-06-07 International Business Machines Corporation COBOL metamodel
US6948174B2 (en) * 2000-08-08 2005-09-20 International Business Machines Corporation IMS MFS (message format service) metamodel
US7559066B2 (en) * 2000-08-08 2009-07-07 International Business Machines Corporation CICS BMS (basic message service) meta model
US7275079B2 (en) * 2000-08-08 2007-09-25 International Business Machines Corporation Common application metamodel including C/C++ metamodel
US6912719B2 (en) * 2000-08-08 2005-06-28 International Business Machines Corporation Type descriptor metamodel
US6915523B2 (en) * 2000-08-08 2005-07-05 International Business Machines Corporation PL/I metamodel
US6910216B2 (en) * 2000-08-08 2005-06-21 International Business Machines Corporation IMS transaction messages metamodel
US7617114B1 (en) 2000-08-10 2009-11-10 Wellpoint Inc. Health care reimbursement
WO2002015080A2 (en) * 2000-08-10 2002-02-21 Lumenos Managing health care resources
GB2408368B (en) * 2000-08-18 2005-07-06 Smart Media Ltd Apparatus, system and method for enhancing data security
US7711790B1 (en) 2000-08-24 2010-05-04 Foundry Networks, Inc. Securing an accessible computer system
US6785729B1 (en) * 2000-08-25 2004-08-31 International Business Machines Corporation System and method for authorizing a network user as entitled to access a computing node wherein authenticated certificate received from the user is mapped into the user identification and the user is presented with the opprtunity to logon to the computing node only after the verification is successful
US7035912B2 (en) * 2000-08-28 2006-04-25 Abaco.P.R., Inc. Method and apparatus allowing a limited client device to use the full resources of a networked server
US6957257B1 (en) * 2000-08-29 2005-10-18 At&T Corp. Customer service maintenance automation
WO2002019642A1 (en) * 2000-08-30 2002-03-07 Citibank, N.A. Method and system for internet hosting and security
US20020026507A1 (en) * 2000-08-30 2002-02-28 Sears Brent C. Browser proxy client application service provider (ASP) interface
US6754470B2 (en) * 2000-09-01 2004-06-22 Telephia, Inc. System and method for measuring wireless device and network usage and performance metrics
WO2002019097A1 (en) * 2000-09-01 2002-03-07 International Interactive Commerce, Ltd. System and method for collaboration using web browsers
US6745011B1 (en) * 2000-09-01 2004-06-01 Telephia, Inc. System and method for measuring wireless device and network usage and performance metrics
US20020052913A1 (en) * 2000-09-06 2002-05-02 Teruhiro Yamada User support apparatus and system using agents
US7149798B2 (en) * 2000-09-06 2006-12-12 Xanboo, Inc. Method and system for adaptively setting a data refresh interval
DE10044246A1 (en) * 2000-09-07 2002-04-04 Siemens Ag Managing messages relating to operating states e.g. of alarm system by selecting budget after number of valid messages output has reached threshold
US6965938B1 (en) * 2000-09-07 2005-11-15 International Business Machines Corporation System and method for clustering servers for performance and load balancing
US20020032793A1 (en) * 2000-09-08 2002-03-14 The Regents Of The University Of Michigan Method and system for reconstructing a path taken by undesirable network traffic through a computer network from a source of the traffic
US20020032871A1 (en) * 2000-09-08 2002-03-14 The Regents Of The University Of Michigan Method and system for detecting, tracking and blocking denial of service attacks over a computer network
US8037492B2 (en) * 2000-09-12 2011-10-11 Thomson Licensing Method and system for video enhancement transport alteration
US7272643B1 (en) 2000-09-13 2007-09-18 Fortinet, Inc. System and method for managing and provisioning virtual routers
US7389358B1 (en) 2000-09-13 2008-06-17 Fortinet, Inc. Distributed virtual system to support managed, network-based services
US7574495B1 (en) 2000-09-13 2009-08-11 Fortinet, Inc. System and method for managing interworking communications protocols
US7487232B1 (en) * 2000-09-13 2009-02-03 Fortinet, Inc. Switch management system and method
US7444398B1 (en) * 2000-09-13 2008-10-28 Fortinet, Inc. System and method for delivering security services
US8972590B2 (en) * 2000-09-14 2015-03-03 Kirsten Aldrich Highly accurate security and filtering software
US6757262B1 (en) * 2000-09-15 2004-06-29 Motorola, Inc. Service framework supporting remote service discovery and connection
US7406427B1 (en) * 2000-09-22 2008-07-29 Accenture Llp Capture highly refined claim evaluation information across multiple web interfaces
US7165097B1 (en) * 2000-09-22 2007-01-16 Oracle International Corporation System for distributed error reporting and user interaction
US7099620B2 (en) * 2000-09-22 2006-08-29 Medical Council Of Canada Method and apparatus for administering an internet based examination to remote sites
US7171487B2 (en) * 2000-09-22 2007-01-30 International Business Machines Corporation Method and system for application specific packet forwarding
US20020078173A1 (en) * 2000-09-25 2002-06-20 Horn Paul H. Data acquisition system and method
US7051315B2 (en) 2000-09-26 2006-05-23 Appstream, Inc. Network streaming of multi-application program code
US7774455B1 (en) * 2000-09-26 2010-08-10 Juniper Networks, Inc. Method and system for providing secure access to private networks
US8392552B2 (en) 2000-09-28 2013-03-05 Vig Acquisitions Ltd., L.L.C. System and method for providing configurable security monitoring utilizing an integrated information system
US7627665B2 (en) 2000-09-28 2009-12-01 Barker Geoffrey T System and method for providing configurable security monitoring utilizing an integrated information system
WO2002027438A3 (en) * 2000-09-28 2002-06-27 Vigilos Inc Method and process for configuring a premises for monitoring
US7139792B1 (en) * 2000-09-29 2006-11-21 Intel Corporation Mechanism for locking client requests to a particular server
US7457948B1 (en) * 2000-09-29 2008-11-25 Lucent Technologies Inc. Automated authentication handling system
DE10048731A1 (en) * 2000-09-29 2002-04-11 Deutsche Telekom Ag Billing procedures with the use of SSL / TLS
US6650890B1 (en) * 2000-09-29 2003-11-18 Postini, Inc. Value-added electronic messaging services and transparent implementation thereof using intermediate server
US7330850B1 (en) 2000-10-04 2008-02-12 Reachforce, Inc. Text mining system for web-based business intelligence applied to web site server logs
US6999992B1 (en) 2000-10-04 2006-02-14 Microsoft Corporation Efficiently sending event notifications over a computer network
US7043531B1 (en) 2000-10-04 2006-05-09 Inetprofit, Inc. Web-based customer lead generator system with pre-emptive profiling
DE10049610A1 (en) * 2000-10-05 2002-04-18 Alcatel Sa Network Management Client
US7007092B2 (en) * 2000-10-05 2006-02-28 Juniper Networks, Inc. Connection management system and method
US7263550B1 (en) 2000-10-10 2007-08-28 Juniper Networks, Inc. Agent-based event-driven web server architecture
US6871213B1 (en) * 2000-10-11 2005-03-22 Kana Software, Inc. System and method for web co-navigation with dynamic content including incorporation of business rule into web document
US8127132B2 (en) * 2000-10-12 2012-02-28 Abb Ab Method and apparatus for executing industrial manufacture
US7254619B2 (en) * 2000-10-13 2007-08-07 Matsushita Electric Industrial Co., Ltd. Apparatus for outputting individual authentication information connectable to a plurality of terminals through a network
US7685036B1 (en) * 2000-10-13 2010-03-23 Ubs Financial Services, Inc. System and method for delivering a financial message
GB2368930B (en) * 2000-10-17 2005-04-06 Hewlett Packard Co Establishment of a deferred network communication session
EP1199643A1 (en) * 2000-10-17 2002-04-24 Sun Microsystems, Inc. Method and apparatus for providing data adapted to a user environment
US8799463B1 (en) * 2000-10-19 2014-08-05 Ariba, Inc. Method and apparatus for processing information related to interactive web sites
US7401115B1 (en) 2000-10-23 2008-07-15 Aol Llc Processing selected browser requests
US7606898B1 (en) 2000-10-24 2009-10-20 Microsoft Corporation System and method for distributed management of shared computers
US6915338B1 (en) * 2000-10-24 2005-07-05 Microsoft Corporation System and method providing automatic policy enforcement in a multi-computer service application
US6907395B1 (en) * 2000-10-24 2005-06-14 Microsoft Corporation System and method for designing a logical model of a distributed computer system and deploying physical resources according to the logical model
US6886038B1 (en) 2000-10-24 2005-04-26 Microsoft Corporation System and method for restricting data transfers and managing software components of distributed computers
US7093288B1 (en) 2000-10-24 2006-08-15 Microsoft Corporation Using packet filters and network virtualization to restrict network communications
US9143477B2 (en) * 2000-10-25 2015-09-22 Syniverse Icx Corporation Address recognition database
US7330830B1 (en) * 2000-10-25 2008-02-12 Thomson Financial Inc. Distributed commerce system
US7606733B2 (en) * 2000-10-27 2009-10-20 Sandisk Il Ltd. Account portability for computing
US20020162009A1 (en) * 2000-10-27 2002-10-31 Shimon Shmueli Privacy assurance for portable computing
US20020106070A1 (en) * 2000-10-27 2002-08-08 Elsey Nicholas J. Technique for effectively capturing and processing event data
US7127492B1 (en) * 2000-10-31 2006-10-24 International Business Machines Corporation Method and apparatus for distributed application acceleration
US7353289B2 (en) 2000-11-06 2008-04-01 Telecommunication Systems, Inc. System for an open architecture development platform with centralized synchronization
US7299259B2 (en) 2000-11-08 2007-11-20 Genesys Telecommunications Laboratories, Inc. Method and apparatus for intelligent routing of instant messaging presence protocol (IMPP) events among a group of customer service representatives
US7929562B2 (en) 2000-11-08 2011-04-19 Genesis Telecommunications Laboratories, Inc. Method and apparatus for optimizing response time to events in queue
US7254833B1 (en) * 2000-11-09 2007-08-07 Accenture Llp Electronic security system and scheme for a communications network
EP1734722A3 (en) * 2000-11-09 2007-03-07 Accenture LLP Electronic security system and scheme for a communication network
US7206804B1 (en) * 2000-11-10 2007-04-17 Sharp Laboratories Of America, Inc. Methods and systems for transmitting digital images
JP2002157202A (en) * 2000-11-17 2002-05-31 Square Co Ltd Information processor, message communication method, recording medium and computer program
US6910128B1 (en) * 2000-11-21 2005-06-21 International Business Machines Corporation Method and computer program product for processing signed applets
US7957509B2 (en) * 2002-04-30 2011-06-07 At&T Intellectual Property I, L.P. Voice enhancing for advance intelligent network services
JP3692290B2 (en) * 2000-11-24 2005-09-07 株式会社エヌ・ティ・ティ・ドコモ Data acquisition method and terminal
JP4600709B2 (en) * 2000-11-30 2010-12-15 ソニー株式会社 Network management device, a network management method, an information processing apparatus, information processing method, and recording medium
US7093008B2 (en) * 2000-11-30 2006-08-15 Intel Corporation Communication techniques for simple network management protocol
GB0029179D0 (en) * 2000-11-30 2001-01-17 Ridgeway Systems & Software Lt Communications system
CA2327078C (en) * 2000-11-30 2005-01-11 Ibm Canada Limited-Ibm Canada Limitee Secure session management and authentication for web sites
JP2002170158A (en) * 2000-12-01 2002-06-14 Koshin Shoji Kk Information service system
US20040168100A1 (en) * 2000-12-04 2004-08-26 Thottan Marina K. Fault detection and prediction for management of computer networks
US7062486B2 (en) * 2000-12-05 2006-06-13 International Business Machines Corporation Method, system and program product for enabling authorized access and request-initiated translation of data files
US20020073048A1 (en) * 2000-12-07 2002-06-13 Ibm Corporation Account charge approval system
US7085744B2 (en) * 2000-12-08 2006-08-01 International Business Machines Corporation Method and system for conducting a transaction over a network
EP2138945A3 (en) * 2000-12-11 2011-08-31 NTT DoCoMo, Inc. Terminal device
DE60131683D1 (en) 2000-12-11 2008-01-10 Microsoft Corp A method and system for managing a plurality of network resources
WO2002048830A9 (en) * 2000-12-11 2003-04-24 Phlair Inc System and method for detecting and reporting online activity using real-time content-based network monitoring
US20020073211A1 (en) * 2000-12-12 2002-06-13 Raymond Lin System and method for securely communicating between application servers and webservers
US8099669B2 (en) 2000-12-14 2012-01-17 Nortel Networks Limited Enhanced unified messaging system with a quick view facility
US20020078165A1 (en) * 2000-12-14 2002-06-20 International Business Machines Corporation System and method for prefetching portions of a web page based on learned preferences
US20020120841A1 (en) * 2000-12-15 2002-08-29 International Business Machines Corporation Dynamic PKI architecture
US6760772B2 (en) 2000-12-15 2004-07-06 Qualcomm, Inc. Generating and implementing a communication protocol and interface for high data rate signal transfer
US7099834B2 (en) * 2000-12-15 2006-08-29 International Business Machines Corporation Method, system, and program for transferring data between servers through a client computer over a network
US7305461B2 (en) * 2000-12-15 2007-12-04 International Business Machines Corporation Method and system for network management with backup status gathering
US7480713B2 (en) * 2000-12-15 2009-01-20 International Business Machines Corporation Method and system for network management with redundant monitoring and categorization of endpoints
WO2002051113A1 (en) * 2000-12-19 2002-06-27 British Telecommunications Public Limited Company Call distribution
US20020078152A1 (en) 2000-12-19 2002-06-20 Barry Boone Method and apparatus for providing predefined feedback
US6912563B1 (en) * 2000-12-19 2005-06-28 Digi-Net Technologies Methods and systems for proactive on-line communications
US6785678B2 (en) * 2000-12-21 2004-08-31 Emc Corporation Method of improving the availability of a computer clustering system through the use of a network medium link state function
US20020116454A1 (en) * 2000-12-21 2002-08-22 William Dyla System and method for providing communication among legacy systems using web objects for legacy functions
US20010054097A1 (en) * 2000-12-21 2001-12-20 Steven Chafe Monitoring and reporting of communications line traffic information
US6961776B1 (en) * 2000-12-22 2005-11-01 Nortel Networks Limited Architecture for multiple channel access to applications
US6874025B2 (en) * 2000-12-22 2005-03-29 Intel Corporation System and method of application input validation
US7660754B1 (en) 2000-12-26 2010-02-09 At&T Delaware Intellectual Property Inc. Technician communications system with automated claims processing
US7286994B1 (en) 2000-12-26 2007-10-23 At&T Bls Intellectual Property, Inc. System for facilitating technician sales referrals
US6745185B2 (en) * 2000-12-26 2004-06-01 Hon Hai Precision Ind. Co., Ltd. System and method for online agency service of data mining and analyzing
US6643747B2 (en) * 2000-12-27 2003-11-04 Intel Corporation Processing requests to efficiently access a limited bandwidth storage area
US6779033B1 (en) * 2000-12-28 2004-08-17 Networks Associates Technology, Inc. System and method for transacting a validated application session in a networked computing environment
US7028033B2 (en) * 2001-01-02 2006-04-11 Hall Aluminum Llc Method and apparatus for simplified access to online services
US7757278B2 (en) * 2001-01-04 2010-07-13 Safenet, Inc. Method and apparatus for transparent encryption
US6965939B2 (en) * 2001-01-05 2005-11-15 International Business Machines Corporation Method and apparatus for processing requests in a network data processing system based on a trust association between servers
US20020089716A1 (en) * 2001-01-05 2002-07-11 David Funk Network management
US8495728B2 (en) 2001-01-11 2013-07-23 International Business Machines Corporation Internet appliance integrating telephone function security and guidance features
US7580971B1 (en) 2001-01-11 2009-08-25 Oracle International Corporation Method and apparatus for efficient SQL processing in an n-tier architecture
US20050138398A1 (en) * 2001-01-11 2005-06-23 Igor Hansen System of databases of personal data and a method of governing access to databases of personal data
US7334031B2 (en) * 2001-01-12 2008-02-19 Siemens Medical Solutions Health Services Corporation System and user interface supporting processing and activity management for concurrently operating applications
US7127609B2 (en) * 2001-01-12 2006-10-24 Siemens Medical Solutions Health Services Corporation System and user interface for adaptively processing and communicating URL data between applications
US7254237B1 (en) * 2001-01-12 2007-08-07 Slt Logic, Llc System and method for establishing a secure connection
US7062649B2 (en) * 2001-01-12 2006-06-13 Hewlett-Packard Development Company, L.P. System and method for categorizing security profile rules within a computer system
US7127608B2 (en) * 2001-01-12 2006-10-24 Siemens Medical Solutions Health Services Corporation System and user interface supporting URL processing and concurrent application operation
US7103666B2 (en) * 2001-01-12 2006-09-05 Siemens Medical Solutions Health Services Corporation System and user interface supporting concurrent application operation and interoperability
US7143437B2 (en) 2001-01-12 2006-11-28 Siemens Medical Solutions Health Services Corporation System and user interface for managing user access to network compatible applications
US7043752B2 (en) * 2001-01-12 2006-05-09 Siemens Medical Solutions Health Services Corporation System and user interface supporting concurrent application initiation and interoperability
US20020133624A1 (en) * 2001-01-16 2002-09-19 Tony Hashem System and process for routing information in a data processing system
US6842706B1 (en) * 2001-01-17 2005-01-11 Smart Disaster Response Technologies, Inc. Methods, apparatus, media, and signals for managing utility usage
US6961773B2 (en) 2001-01-19 2005-11-01 Esoft, Inc. System and method for managing application service providers
US20140089185A1 (en) * 2005-10-06 2014-03-27 C-Sam, Inc. Isolating distinct service provider widgets within a wallet container
US9600842B2 (en) 2001-01-24 2017-03-21 E-Numerate Solutions, Inc. RDX enhancement of system and method for implementing reusable data markup language (RDL)
FR2819967B1 (en) * 2001-01-24 2003-03-14 Bull Sa Method and communication system of a certificate from a securisation module and a server
GB2386726B (en) * 2001-01-24 2005-06-15 Ericsson Telefon Ab L M An arrangement and a method relating to session management in a portal structure
US6965994B1 (en) * 2001-01-30 2005-11-15 Microsoft Corporation Security mechanism for computer processing modules
US7171681B1 (en) * 2001-01-31 2007-01-30 Secure Computing Corporation System and method for providing expandable proxy firewall services
US7089311B2 (en) * 2001-01-31 2006-08-08 International Business Machines Corporation Methods, systems and computer program products for resuming SNA application-client communications after loss of an IP network connection
US20020123996A1 (en) * 2001-02-06 2002-09-05 O'brien Christopher Data mining system, method and apparatus for industrial applications
GB2377784B (en) * 2001-02-12 2003-11-05 Altio Ltd A presentation server which enables a client device to run a network based application
US7277878B2 (en) * 2001-02-13 2007-10-02 Ariba, Inc. Variable length file header apparatus and system
CA2372647C (en) * 2001-02-20 2010-05-04 Research In Motion Limited System and method for administrating a wireless communication network
JP3631681B2 (en) * 2001-02-23 2005-03-23 株式会社ビーコンインフォメーションテクノロジー Data management system, data management method and computer program
US20020120743A1 (en) * 2001-02-26 2002-08-29 Lior Shabtay Splicing persistent connections
US8798251B2 (en) 2001-02-27 2014-08-05 Verizon Data Services Llc Methods and systems for computer enhanced conference calling
US8472428B2 (en) 2001-02-27 2013-06-25 Verizon Data Services Llc Methods and systems for line management
US7903796B1 (en) 2001-02-27 2011-03-08 Verizon Data Services Llc Method and apparatus for unified communication management via instant messaging
US8873730B2 (en) 2001-02-27 2014-10-28 Verizon Patent And Licensing Inc. Method and apparatus for calendared communications flow control
US7912193B2 (en) 2001-02-27 2011-03-22 Verizon Data Services Llc Methods and systems for call management with user intervention
US8774380B2 (en) 2001-02-27 2014-07-08 Verizon Patent And Licensing Inc. Methods and systems for call management with user intervention
US9392120B2 (en) 2002-02-27 2016-07-12 Verizon Patent And Licensing Inc. Methods and systems for call management with user intervention
US8494135B2 (en) 2001-02-27 2013-07-23 Verizon Data Services Llc Methods and systems for contact management
US8488761B2 (en) 2001-02-27 2013-07-16 Verizon Data Services Llc Methods and systems for a call log
US8488766B2 (en) 2001-02-27 2013-07-16 Verizon Data Services Llc Methods and systems for multiuser selective notification
US8761363B2 (en) 2001-02-27 2014-06-24 Verizon Data Services Llc Methods and systems for automatic forwarding of communications to a preferred device
US8467502B2 (en) 2001-02-27 2013-06-18 Verizon Data Services Llc Interactive assistant for managing telephone communications
US8750482B2 (en) 2001-02-27 2014-06-10 Verizon Data Services Llc Methods and systems for preemptive rejection of calls
US8503650B2 (en) 2001-02-27 2013-08-06 Verizon Data Services Llc Methods and systems for configuring and providing conference calls
US8503639B2 (en) 2001-02-27 2013-08-06 Verizon Data Services Llc Method and apparatus for adaptive message and call notification
US8751571B2 (en) 2001-02-27 2014-06-10 Verizon Data Services Llc Methods and systems for CPN triggered collaboration
US8472606B2 (en) 2001-02-27 2013-06-25 Verizon Data Services Llc Methods and systems for directory information lookup
US6976017B1 (en) 2001-02-27 2005-12-13 Verizon Data Services Inc. Method and apparatus for context based querying
US7243077B2 (en) 2001-03-02 2007-07-10 International Business Machines Corporation Method and computer program product for managing an internet trading network
US6961938B1 (en) * 2001-03-03 2005-11-01 Brocade Communications Systems, Inc. Management of multiple network devices using unsigned Java applets
US7400879B2 (en) * 2001-03-04 2008-07-15 Adomo, Inc. Method for conducting mobile communications for a network
US7296066B2 (en) * 2001-03-04 2007-11-13 Adomo, Inc. Mobile communication system for a network
JP4700204B2 (en) * 2001-03-07 2011-06-15 株式会社日立製作所 Storage management data control system
WO2002086768A3 (en) * 2001-03-08 2004-04-01 Tririga Inc Data storage and access system employing clustering of servers
US7720958B2 (en) * 2001-03-09 2010-05-18 International Business Machines Corporation Method and system for embedding correlated performance measurements for distributed application performance decomposition
JP2002271356A (en) * 2001-03-12 2002-09-20 Oki Electric Ind Co Ltd Network communication system
US20020133473A1 (en) * 2001-03-15 2002-09-19 International Business Machines Corporation System and method for on-demand pricing for differentiated services computer networks
US7882555B2 (en) * 2001-03-16 2011-02-01 Kavado, Inc. Application layer security method and system
US8195738B2 (en) * 2001-03-20 2012-06-05 Verizon Business Global Llc Systems and methods for communicating from an integration platform to a profile management server
US8200577B2 (en) * 2001-03-20 2012-06-12 Verizon Business Global Llc Systems and methods for retrieving and modifying data records for rating and billing purposes
US7185364B2 (en) * 2001-03-21 2007-02-27 Oracle International Corporation Access system interface
US6760694B2 (en) * 2001-03-21 2004-07-06 Hewlett-Packard Development Company, L.P. Automatic information collection system using most frequent uncommon words or phrases
US6782421B1 (en) * 2001-03-21 2004-08-24 Bellsouth Intellectual Property Corporation System and method for evaluating the performance of a computer application
JP4254071B2 (en) * 2001-03-22 2009-04-15 コニカミノルタビジネステクノロジーズ株式会社 Printer, server, monitoring apparatus, printing system, and monitoring program
US7155403B2 (en) 2001-03-22 2006-12-26 International Business Machines Corporation System and method for leveraging procurement across companies and company groups
US7386495B2 (en) 2001-03-23 2008-06-10 International Business Machines Corporation System and method for processing tax codes by company group
US8095687B1 (en) * 2001-03-26 2012-01-10 Microsoft Corporation Systems and methods for managing state in a cluster of servers
US7051319B1 (en) * 2001-03-27 2006-05-23 Siebel Systems, Inc. Method, system, and product for upgrading software objects using inherency
US7082465B1 (en) * 2001-03-27 2006-07-25 Cisco Technology, Inc. Web based management of host computers in an open protocol network
US8027892B2 (en) 2001-03-28 2011-09-27 International Business Machines Corporation System and method for automating invoice processing with positive confirmation
US20020143523A1 (en) * 2001-03-30 2002-10-03 Lakshmi Balaji System and method for providing a file in multiple languages
US6912582B2 (en) * 2001-03-30 2005-06-28 Microsoft Corporation Service routing and web integration in a distributed multi-site user authentication system
US20030074400A1 (en) * 2001-03-30 2003-04-17 David Brooks Web user profiling system and method
JP2002297900A (en) * 2001-03-30 2002-10-11 Ibm Japan Ltd Control system for reception by businesses, user side terminal device, reception side terminal device, management server queue monitoring device, method of allocating reception side terminals, and storage medium
US7007169B2 (en) * 2001-04-04 2006-02-28 International Business Machines Corporation Method and apparatus for protecting a web server against vandals attacks without restricting legitimate access
FI20010724A (en) * 2001-04-06 2002-10-07 Ajatuspaja Oy Method and apparatus for distributed database and the application utilizing the use of the terminal device independently
US6959336B2 (en) * 2001-04-07 2005-10-25 Secure Data In Motion, Inc. Method and system of federated authentication service for interacting between agent and client and communicating with other components of the system to choose an appropriate mechanism for the subject from among the plurality of authentication mechanisms wherein the subject is selected from humans, client applications and applets
CA2417178C (en) * 2001-04-09 2007-10-30 Ntt Docomo, Inc. Communication data amount measurement system
US7237257B1 (en) * 2001-04-11 2007-06-26 Aol Llc Leveraging a persistent connection to access a secured service
US7015949B1 (en) 2001-04-12 2006-03-21 Ipix Corporation Method and apparatus for hosting a network camera with refresh degradation
US7024488B1 (en) 2001-04-12 2006-04-04 Ipix Corporation Method and apparatus for hosting a network camera
US7177448B1 (en) 2001-04-12 2007-02-13 Ipix Corporation System and method for selecting and transmitting images of interest to a user
US7076085B1 (en) * 2001-04-12 2006-07-11 Ipix Corp. Method and apparatus for hosting a network camera including a heartbeat mechanism
US8026944B1 (en) 2001-04-12 2011-09-27 Sony Corporation Method and apparatus for hosting a network camera with image degradation
WO2002084507A1 (en) * 2001-04-13 2002-10-24 Netiq Corporation User-side tracking of multimedia application usage within a web page
US7200679B2 (en) * 2001-04-13 2007-04-03 Telefonaktiebolaget Lm Ericsson (Publ) Creating distributed proxy configurations
US7000008B2 (en) * 2001-04-16 2006-02-14 Sun Microsystems, Inc. Method, system, and program for providing data updates to a page including multiple regions of dynamic content
WO2002087112A3 (en) 2001-04-18 2003-02-06 Eric A Frische Unmanned lighter-than-air safe termination and recovery methods
EP1384351B1 (en) * 2001-04-20 2011-05-18 General Instrument Corporation Graphical user interface for a transport multiplexer
US8849716B1 (en) 2001-04-20 2014-09-30 Jpmorgan Chase Bank, N.A. System and method for preventing identity theft or misuse by restricting access
US20020154635A1 (en) * 2001-04-23 2002-10-24 Sun Microsystems, Inc. System and method for extending private networks onto public infrastructure using supernets
US6961766B2 (en) * 2001-04-24 2005-11-01 Oracle International Corp. Method for extracting personalization information from web activity
US20020194217A1 (en) * 2001-04-26 2002-12-19 International Business Machnies Corporation Metadata graphial user interface
WO2002088998A1 (en) * 2001-04-27 2002-11-07 W. Quinn, Inc. System for active reports with drill down capability
US6782350B1 (en) * 2001-04-27 2004-08-24 Blazent, Inc. Method and apparatus for managing resources
US20020191014A1 (en) * 2001-04-30 2002-12-19 Hsieh Vivian G. Graphical user interfaces for software management in an automated provisioning environment
US20030078949A1 (en) * 2001-04-30 2003-04-24 Scholz Bernhard J. Automatic generation of forms with input validation
US20020198931A1 (en) * 2001-04-30 2002-12-26 Murren Brian T. Architecture and process for presenting application content to clients
US20020194263A1 (en) * 2001-04-30 2002-12-19 Murren Brian T. Hierarchical constraint resolution for application properties, configuration, and behavior
US20030009433A1 (en) * 2001-04-30 2003-01-09 Murren Brian T. Automatic identification of computer program attributes
US7346921B2 (en) * 2001-04-30 2008-03-18 Ge Capital Corporation Definition of low-level security rules in terms of high-level security concepts
US7519546B2 (en) * 2001-04-30 2009-04-14 General Electric Company Maintaining synchronization of information published to multiple subscribers
US20020165902A1 (en) * 2001-05-03 2002-11-07 Robb Mary Thomas Independent log manager
US20020169863A1 (en) * 2001-05-08 2002-11-14 Robert Beckwith Multi-client to multi-server simulation environment control system (JULEP)
US20040060073A1 (en) * 2001-05-08 2004-03-25 Bialk Harvey R. Method and system for provisioning broadband network resources
US6952729B2 (en) * 2001-05-08 2005-10-04 At&T Corp. Network management method and system for managing a broadband network providing multiple services
US7543328B2 (en) * 2001-05-08 2009-06-02 At&T Corp. Method and system for providing an efficient use of broadband network resources
US7802287B2 (en) * 2001-05-08 2010-09-21 At&T Intellectual Property Ii, L.P. Method and system for generating geographic visual displays of broadband network data
US20020169984A1 (en) * 2001-05-09 2002-11-14 Kumar Gopikrishna T. Session management for wireless E-commerce
US20020169967A1 (en) * 2001-05-14 2002-11-14 Sangeeta Varma Method and apparatus for multiple token access to thin client architecture session
US20030051142A1 (en) * 2001-05-16 2003-03-13 Hidalgo Lluis Mora Firewalls for providing security in HTTP networks and applications
US20020174039A1 (en) * 2001-05-18 2002-11-21 Mitac International Corp. Virtual hub
US20020184337A1 (en) * 2001-05-21 2002-12-05 Anders Hyldahl Method and computer system for constructing references to virtual data
FI112140B (en) * 2001-05-23 2003-10-31 Nokia Corp information communication
US6704406B1 (en) * 2001-05-29 2004-03-09 Cisco Technology, Inc. Automated route plan generation
US20030005308A1 (en) * 2001-05-30 2003-01-02 Rathbun Paul L. Method and system for globally restricting client access to a secured web site
US7072957B2 (en) * 2001-05-31 2006-07-04 International Business Machines Corporation Remote administration and monitoring of a service component in a service logic execution environment
US20020184319A1 (en) * 2001-05-31 2002-12-05 Willner Barry E. Systems and methods for facilitating access to an information address
US7428752B2 (en) * 2001-06-01 2008-09-23 Applications In Internet Time, Llc Secure data accessing system and method
US8392527B2 (en) * 2001-06-04 2013-03-05 Hewlett-Packard Development Company L.P. System and method for requesting computer resources
US7231519B2 (en) * 2001-06-06 2007-06-12 International Business Machines Corporation Secure inter-node communication
WO2002099598A3 (en) 2001-06-07 2004-03-25 First Usa Bank Na System and method for rapid updating of credit information
US7072810B2 (en) * 2001-06-08 2006-07-04 Tata Consultancy Services Limited Method and apparatus for pattern based generation of graphical user interfaces (GUI)
US7392546B2 (en) * 2001-06-11 2008-06-24 Bea Systems, Inc. System and method for server security and entitlement processing
US20020188730A1 (en) * 2001-06-12 2002-12-12 Wenting Tang Method and system for a modular transmission control protocol (TCP) frequent-handoff design in a streams based transmission control protocol internet protocol (TCP/IP) implementation
US20050198379A1 (en) 2001-06-13 2005-09-08 Citrix Systems, Inc. Automatically reconnecting a client across reliable and persistent communication sessions
US20020194289A1 (en) * 2001-06-18 2002-12-19 Engel Glenn R. Configuring devices using server responses
US6996602B2 (en) * 2001-06-18 2006-02-07 Ford Global Technologies, Llc Server-side page table framework for client application definition and execution
US7103606B2 (en) * 2001-06-18 2006-09-05 International Business Machines Corporation Method and apparatus for removing information from a server
US20020191020A1 (en) * 2001-06-18 2002-12-19 International Business Machines Corporation Method and apparatus for removing confindential information from a history
US7925616B2 (en) 2001-06-19 2011-04-12 Microstrategy, Incorporated Report system and method using context-sensitive prompt objects
US7356758B1 (en) 2001-06-19 2008-04-08 Microstrategy Incorporated System and method for run-time report resolution of reports that include prompt objects
US7861161B1 (en) * 2001-06-19 2010-12-28 Microstrategy, Inc. Report system and method using prompt objects
US7302639B1 (en) 2001-06-19 2007-11-27 Microstrategy, Inc. Report system and method using prompt in prompt objects
US20020198850A1 (en) * 2001-06-26 2002-12-26 International Business Machines Corporation System and method for dynamic price determination in differentiated services computer networks
US20020198965A1 (en) * 2001-06-26 2002-12-26 Kraft Matthew J. Method and apparatus to facilitate establishing a distributed internet application platform
US7219137B1 (en) 2001-06-28 2007-05-15 Bellsouth Intellectual Property Corp Technician wireline and wireless intranet access via systems interface to legacy systems
US8831949B1 (en) 2001-06-28 2014-09-09 At&T Intellectual Property I, L.P. Voice recognition for performing authentication and completing transactions in a systems interface to legacy systems
US7401144B1 (en) * 2001-06-28 2008-07-15 At&T Delaware Intellectual Property, Inc. Technician intranet access via systems interface to legacy systems
US7606712B1 (en) 2001-06-28 2009-10-20 At&T Intellectual Property Ii, L.P. Speech recognition interface for voice actuation of legacy systems
US7181547B1 (en) * 2001-06-28 2007-02-20 Fortinet, Inc. Identifying nodes in a ring network
US6961758B2 (en) * 2001-06-29 2005-11-01 Hewlett-Packard Development Company, L.P. Personalized internet content server system
US7295522B2 (en) * 2001-06-29 2007-11-13 Microsoft Corporation System and method for continuously provisioning a mobile device
US20030069982A1 (en) * 2001-07-03 2003-04-10 Colby Harper Method and system for generating privacy-specified internet session content records in a communications network
US8200818B2 (en) * 2001-07-06 2012-06-12 Check Point Software Technologies, Inc. System providing internet access management with router-based policy enforcement
US7853781B2 (en) * 2001-07-06 2010-12-14 Juniper Networks, Inc. Load balancing secure sockets layer accelerator
US7149892B2 (en) 2001-07-06 2006-12-12 Juniper Networks, Inc. Secure sockets layer proxy architecture
US20030078890A1 (en) * 2001-07-06 2003-04-24 Joachim Schmidt Multimedia content download apparatus and method using same
US7908472B2 (en) * 2001-07-06 2011-03-15 Juniper Networks, Inc. Secure sockets layer cut through architecture
US7590684B2 (en) * 2001-07-06 2009-09-15 Check Point Software Technologies, Inc. System providing methodology for access control with cooperative enforcement
US7228412B2 (en) * 2001-07-06 2007-06-05 Juniper Networks, Inc. Bufferless secure sockets layer architecture
US8284025B2 (en) 2001-07-10 2012-10-09 Xatra Fund Mx, Llc Method and system for auditory recognition biometrics on a FOB
US7746215B1 (en) 2001-07-10 2010-06-29 Fred Bishop RF transactions using a wireless reader grid
US9454752B2 (en) 2001-07-10 2016-09-27 Chartoleaux Kg Limited Liability Company Reload protocol at a transaction processing entity
US7889052B2 (en) * 2001-07-10 2011-02-15 Xatra Fund Mx, Llc Authorizing payment subsequent to RF transactions
US9024719B1 (en) 2001-07-10 2015-05-05 Xatra Fund Mx, Llc RF transaction system and method for storing user personal data
US7668750B2 (en) 2001-07-10 2010-02-23 David S Bonalle Securing RF transactions using a transactions counter
US8548927B2 (en) 2001-07-10 2013-10-01 Xatra Fund Mx, Llc Biometric registration for facilitating an RF transaction
USRE45416E1 (en) 2001-07-10 2015-03-17 Xatra Fund Mx, Llc Processing an RF transaction using a routing number
US7239226B2 (en) 2001-07-10 2007-07-03 American Express Travel Related Services Company, Inc. System and method for payment using radio frequency identification in contact and contactless transactions
US9031880B2 (en) 2001-07-10 2015-05-12 Iii Holdings 1, Llc Systems and methods for non-traditional payment using biometric data
US7735725B1 (en) 2001-07-10 2010-06-15 Fred Bishop Processing an RF transaction using a routing number
US8001054B1 (en) 2001-07-10 2011-08-16 American Express Travel Related Services Company, Inc. System and method for generating an unpredictable number using a seeded algorithm
US20040236699A1 (en) 2001-07-10 2004-11-25 American Express Travel Related Services Company, Inc. Method and system for hand geometry recognition biometrics on a fob
US7266839B2 (en) 2001-07-12 2007-09-04 J P Morgan Chase Bank System and method for providing discriminated content to network users
US6950847B2 (en) * 2001-07-12 2005-09-27 Sun Microsystems, Inc. Service provider system for delivering services in a distributed computing environment
EP1276062A1 (en) * 2001-07-12 2003-01-15 Hewlett-Packard Company, A Delaware Corporation A method of providing user-specific data to an information source, a data carrier and a method of personalising a user's internet experience
US7409420B2 (en) * 2001-07-16 2008-08-05 Bea Systems, Inc. Method and apparatus for session replication and failover
US20030033379A1 (en) * 2001-07-20 2003-02-13 Lemur Networks Intelligent central directory for soft configuration of IP services
US20030020753A1 (en) * 2001-07-25 2003-01-30 Asa Kling Product cost control graphical user interface
US7406524B2 (en) * 2001-07-26 2008-07-29 Avaya Communication Isael Ltd. Secret session supporting load balancer
US20030023717A1 (en) * 2001-07-26 2003-01-30 Lister Michael L. Method and apparatus to reveal the usability of an internet web site
US6996601B1 (en) * 2001-07-26 2006-02-07 Sprint Communications Company L.P. Process for managing change within an enterprise
US7584425B2 (en) * 2001-07-31 2009-09-01 Verizon Business Global Llc Systems and methods for generating reports
US7051046B2 (en) * 2001-08-01 2006-05-23 Roy F. Weston, Inc. System for managing environmental audit information
US7426553B1 (en) * 2001-08-02 2008-09-16 At&T Intellectual Property I, L.P. Provisioning data link connection identifiers in a communications network
EP1283466A1 (en) * 2001-08-06 2003-02-12 Hewlett-Packard Company (a Delaware corporation) Management system for a cluster
US20030055668A1 (en) * 2001-08-08 2003-03-20 Amitabh Saran Workflow engine for automating business processes in scalable multiprocessor computer platforms
US7243374B2 (en) 2001-08-08 2007-07-10 Microsoft Corporation Rapid application security threat analysis
WO2003015330A3 (en) * 2001-08-08 2003-10-09 Flash Networks Ltd A system and a method for accelerating communication of tcp/ip based content
US20030074448A1 (en) * 2001-08-10 2003-04-17 Tadashi Kinebuchi Multimedia information system and computer program
US20030030664A1 (en) * 2001-08-13 2003-02-13 Parry Travis J. Customizable control panel software
US7113999B2 (en) * 2001-08-14 2006-09-26 International Business Machines Corporation Method, computer readable media and apparatus for the selection and rendering of audio files in a networked environment
US20030054806A1 (en) * 2001-08-15 2003-03-20 Raymond Ho System and method for defining, creating and deploying wireless applications
US8346848B2 (en) * 2001-08-16 2013-01-01 Juniper Networks, Inc. System and method for maintaining statefulness during client-server interactions
US7356558B2 (en) * 2001-08-21 2008-04-08 Hbi Branded Apparel Enterprises, Llc Systems and methods for manufacturing
EP1419441A2 (en) * 2001-08-23 2004-05-19 Sphera Corporation A method and system for balancing the load of a computer resource among computers
US7005441B2 (en) * 2001-08-24 2006-02-28 Ohio University Compositions that bind antiterminator RNA and assay for screening such compositions
US7103590B1 (en) 2001-08-24 2006-09-05 Oracle International Corporation Method and system for pipelined database table functions
US8090617B1 (en) * 2001-08-27 2012-01-03 Renesas Electronics America Inc. Determining if a potential customer is a desirable customer
US7219109B1 (en) * 2001-08-27 2007-05-15 Palmsource, Inc. Time zone management
US7003090B2 (en) * 2001-08-28 2006-02-21 International Business Machines Corporation Method of establishing a communication channel to intelligent support for ebusiness applications
US7089304B2 (en) * 2001-08-30 2006-08-08 Microsoft Corporation Metered Internet usage
US7031979B2 (en) * 2001-08-31 2006-04-18 Hewlett-Packard Development Company, L.P. Report generation system and method
US7327673B1 (en) * 2001-08-31 2008-02-05 At&T Delaware Intellectual Property, Inc. Asymmetric digital subscriber line provision flow control on digital subscriber line access multiplexer switches
US6990495B1 (en) * 2001-09-05 2006-01-24 Bellsouth Intellectual Property Corporation System and method for finding persons in a corporate entity
US8812706B1 (en) 2001-09-06 2014-08-19 Qualcomm Incorporated Method and apparatus for compensating for mismatched delays in signals of a mobile display interface (MDDI) system
US20030074606A1 (en) * 2001-09-10 2003-04-17 Udi Boker Network-based control center for conducting performance tests of server systems
JP2003087693A (en) * 2001-09-11 2003-03-20 Sony Corp Processor, method, and program for information processing
US6973567B1 (en) * 2001-09-14 2005-12-06 Cisco Technology, Inc. Early authentication during modem training
US20030055911A1 (en) * 2001-09-17 2003-03-20 Peterson Erik Lawrence System and method for retrieving data over a network
US7155439B2 (en) * 2001-09-20 2006-12-26 Wellogix, Inc. Modular and customizable process and system for capturing field documentation data in a complex project workflow system
US20030074358A1 (en) * 2001-09-24 2003-04-17 Siamak Sarbaz Integration, management and processing of network data from disparate sources
US8055555B2 (en) * 2001-09-25 2011-11-08 Emc Corporation Mediation device for scalable storage service
US7552056B2 (en) 2001-09-25 2009-06-23 Emc Corporation Scalable storage service registration application
US7237108B2 (en) 2001-09-26 2007-06-26 General Instrument Corporation Encryption of streaming control protocols and their headers
US20030059053A1 (en) * 2001-09-26 2003-03-27 General Instrument Corporation Motorola, Inc. Key management interface to multiple and simultaneous protocols
US8255989B2 (en) 2001-09-26 2012-08-28 General Instrument Corporation Access control and key management system for streaming media
US6724399B1 (en) * 2001-09-28 2004-04-20 Siebel Systems, Inc. Methods and apparatus for enabling keyboard accelerators in applications implemented via a browser
US7313617B2 (en) 2001-09-28 2007-12-25 Dale Malik Methods and systems for a communications and information resource manager
US7472187B2 (en) * 2001-09-28 2008-12-30 At&T Intellectual Property I, L.P. Communications and information resource manager
US20030065727A1 (en) * 2001-09-28 2003-04-03 Capital One Financial Corporation Systems and methods for providing secured electronic messaging
US7941520B1 (en) * 2001-09-28 2011-05-10 Bellsouth Intellectual Property Corp. System and method for tracking telephone network capacity and equipment
US7885996B2 (en) * 2001-09-29 2011-02-08 Siebel Systems, Inc. Method, apparatus, and system for implementing notifications in a framework to support web-based applications
US7146617B2 (en) 2001-09-29 2006-12-05 Siebel Systems, Inc. Method, apparatus, and system for implementing view caching in a framework to support web-based applications
US6907451B1 (en) * 2001-09-29 2005-06-14 Siebel Systems, Inc. Method, apparatus, and system for immediate posting of changes in a client server environment
US7203948B2 (en) * 2001-09-29 2007-04-10 Siebel Systems, Inc. Method, apparatus, and system for implementing caching of view custom options in a framework to support web-based applications
US8359335B2 (en) 2001-09-29 2013-01-22 Siebel Systems, Inc. Computing system and method to implicitly commit unsaved data for a world wide web application
US20030065949A1 (en) * 2001-10-01 2003-04-03 Madeleine Le International trade system
US20040268214A1 (en) * 2001-10-01 2004-12-30 Gabriele Zinssmeister Transaction monitoring system
JP2003108558A (en) * 2001-10-02 2003-04-11 Ricoh Co Ltd Data retrieving system
US7870492B2 (en) 2001-10-02 2011-01-11 Siebel Systems, Inc. Method, apparatus, and system for managing commands in a client server environment
JP3864743B2 (en) * 2001-10-04 2007-01-10 株式会社日立製作所 Firewall apparatus, communication method information devices and information equipment
US7287274B1 (en) * 2001-10-04 2007-10-23 Perot Systems Corporation Method and system for providing security to a client server operating a browser
JP3901484B2 (en) * 2001-10-05 2007-04-04 株式会社ジェイテクト Electric power steering system
US20030069956A1 (en) * 2001-10-05 2003-04-10 Gieseke Eric James Object oriented SNMP agent
US20030070087A1 (en) * 2001-10-05 2003-04-10 Dmitry Gryaznov System and method for automatic updating of multiple anti-virus programs
US20040049655A1 (en) * 2001-10-12 2004-03-11 Allison David S. Method and apparatus for communication to threads of control through streams
US7457883B2 (en) * 2001-10-12 2008-11-25 Cisco Technology, Inc. Mechanism for implementing network discovery in a cable network
US7003575B2 (en) * 2001-10-15 2006-02-21 First Hop Oy Method for assisting load balancing in a server cluster by rerouting IP traffic, and a server cluster and a client, operating according to same
US20030088714A1 (en) * 2001-10-15 2003-05-08 Scott Madlener User internet interface
US7194553B2 (en) 2001-10-16 2007-03-20 Microsoft Corporation Resolving virtual network names
US7676540B2 (en) * 2001-10-16 2010-03-09 Microsoft Corporation Scoped referral statements
US8015204B2 (en) * 2001-10-16 2011-09-06 Microsoft Corporation Scoped access control metadata element
US20030074579A1 (en) * 2001-10-16 2003-04-17 Microsoft Corporation Virtual distributed security system
US7536712B2 (en) * 2001-10-16 2009-05-19 Microsoft Corporation Flexible electronic message security mechanism
US20030079039A1 (en) * 2001-10-16 2003-04-24 Forkner Damien R. Web server utilizing a state machine and user token
EP1303097A3 (en) 2001-10-16 2005-11-30 Microsoft Corporation Virtual distributed security system
US20030074482A1 (en) * 2001-10-16 2003-04-17 Christensen Erik B. Composable messaging protocol
US7899047B2 (en) 2001-11-27 2011-03-01 Microsoft Corporation Virtual network with adaptive dispatcher
US7552203B2 (en) * 2001-10-17 2009-06-23 The Boeing Company Manufacturing method and software product for optimizing information flow
US7080092B2 (en) 2001-10-18 2006-07-18 Bea Systems, Inc. Application view component for system integration
US7403986B1 (en) * 2001-10-18 2008-07-22 Network Equipment Technologies, Inc. Method for synchronizing circuit related objects between network management systems and network control processors
US7047484B1 (en) * 2001-10-18 2006-05-16 Microsoft Corporation Method, system, and apparatus for providing access to asynchronous data in a spreadsheet application program
US7552222B2 (en) 2001-10-18 2009-06-23 Bea Systems, Inc. Single system user identity
US7454750B2 (en) * 2001-10-19 2008-11-18 Amberpoint, Inc. Integrator adaptor and proxy based composite application provisioning method and apparatus
US7155001B2 (en) 2001-10-24 2006-12-26 Sbc Properties, L.P. System and method for restricting and monitoring telephone calls
US7337220B2 (en) * 2001-10-24 2008-02-26 At&T Labs, Inc. Unified interface for managing DSL services
US20030084423A1 (en) * 2001-10-26 2003-05-01 Dai Clegg Automatic source code generation
JP4055393B2 (en) 2001-10-30 2008-03-05 ソニー株式会社 Data processing apparatus and method and program
US7216160B2 (en) * 2001-10-31 2007-05-08 Sun Microsystems, Inc. Server-based application monitoring through collection of application component and environmental statistics
US20030140089A1 (en) * 2001-11-01 2003-07-24 Hines Kenneth J. Inter-applet communication using an applet agent
US20030093435A1 (en) * 2001-11-05 2003-05-15 Bandekar Vijay R. Method and system for application level data object synchronization between two or more processes
GB0126908D0 (en) * 2001-11-09 2002-01-02 Ibm Method and system for display of activity of users
US7149809B2 (en) * 2001-11-13 2006-12-12 One Touch Systems System for reducing server loading during content delivery
EP1456752A1 (en) * 2001-11-14 2004-09-15 Exegesys, Inc. Method and system for software application development and customizable runtime environment
US7243366B2 (en) * 2001-11-15 2007-07-10 General Instrument Corporation Key management protocol and authentication system for secure internet protocol rights management architecture
US20030097445A1 (en) * 2001-11-20 2003-05-22 Stephen Todd Pluggable devices services and events for a scalable storage service architecture
EP1315064A1 (en) * 2001-11-21 2003-05-28 Sun Microsystems, Inc. Single authentication for a plurality of services
US20030101269A1 (en) * 2001-11-26 2003-05-29 Eastman Kodak Company Device interface agent
US7734793B2 (en) * 2001-11-27 2010-06-08 Accenture Global Services Gmbh Service control framework for seamless transfer of a multimedia conference over different media
WO2003046790A1 (en) * 2001-11-27 2003-06-05 Accenture Llp Context sensitive advertisement delivery framework
EP1461688A4 (en) * 2001-11-27 2006-02-08 Accenture Llp Service control architecture
US7072881B1 (en) * 2001-11-27 2006-07-04 Bellsouth Intellectual Property Corporation Method and system for managing telecommunications reports
US7225256B2 (en) 2001-11-30 2007-05-29 Oracle International Corporation Impersonation in an access system
US7987501B2 (en) 2001-12-04 2011-07-26 Jpmorgan Chase Bank, N.A. System and method for single session sign-on
US7155608B1 (en) * 2001-12-05 2006-12-26 Bellsouth Intellectual Property Corp. Foreign network SPAM blocker
US7240089B2 (en) * 2001-12-10 2007-07-03 International Business Machines Corporation Message queuing method, system, and program product with reusable pooling component
US7092378B1 (en) * 2001-12-10 2006-08-15 At & T Corp. System for utilizing a genetic algorithm to provide constraint-based routing of packets in a communication network