WO1998034391A2 - Architecture d'un systeme de communication - Google Patents

Architecture d'un systeme de communication Download PDF

Info

Publication number
WO1998034391A2
WO1998034391A2 PCT/US1998/001868 US9801868W WO9834391A2 WO 1998034391 A2 WO1998034391 A2 WO 1998034391A2 US 9801868 W US9801868 W US 9801868W WO 9834391 A2 WO9834391 A2 WO 9834391A2
Authority
WO
WIPO (PCT)
Prior art keywords
network
call
information
service
data
Prior art date
Application number
PCT/US1998/001868
Other languages
English (en)
Other versions
WO1998034391A9 (fr
WO1998034391A3 (fr
WO1998034391A8 (fr
Inventor
Guido M. Eastep
Paul R. Litzenberger
Shannon R. Orebaugh
Isaac K. Elliott
Rick Stelle
Bruce Schrage
Craig A. Baxter
Wesley Atkinson
Chuck Knostman
Bing Chen
Kristan Vandersluis
Fang Jun
Original Assignee
Mci Worldcom, Inc.
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
Priority claimed from US08/795,270 external-priority patent/US6731625B1/en
Priority to BR9809561-7A priority Critical patent/BR9809561A/pt
Priority to CA002289455A priority patent/CA2289455A1/fr
Priority to EP19980904802 priority patent/EP1000500A4/fr
Priority to IL13110298A priority patent/IL131102A0/xx
Priority to AU62592/98A priority patent/AU6259298A/en
Application filed by Mci Worldcom, Inc. filed Critical Mci Worldcom, Inc.
Priority to APAP/P/1999/001611A priority patent/AP9901611A0/en
Priority to NZ336939A priority patent/NZ336939A/xx
Priority to JP53313598A priority patent/JP2001520820A/ja
Publication of WO1998034391A2 publication Critical patent/WO1998034391A2/fr
Publication of WO1998034391A3 publication Critical patent/WO1998034391A3/fr
Priority to NO993733A priority patent/NO993733L/no
Publication of WO1998034391A9 publication Critical patent/WO1998034391A9/fr
Publication of WO1998034391A8 publication Critical patent/WO1998034391A8/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/0024—Services and arrangements where telephone services are combined with data services
    • H04M7/003—Click to dial services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/165—Combined use of TCP and UDP protocols; selection criteria therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/169—Special adaptations of TCP, UDP or IP for interworking of IP based networks with other networks 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
    • H04M3/493—Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/128—Details of addressing, directories or routing tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0029—Provisions for intelligent networking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0062—Provisions for network management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
    • H04M2201/60—Medium conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2203/00—Aspects of automatic or semi-automatic exchanges
    • H04M2203/50—Aspects of automatic or semi-automatic exchanges related to audio conference
    • H04M2203/5063—Centrally initiated conference, i.e. Conference server dials participants
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0176—Billing arrangements using internet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/48—Arrangements for recalling a calling subscriber when the wanted subscriber ceases to be busy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H04M3/5166—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing in combination with interactive voice response systems or voice portals, e.g. as front-ends
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H04M3/5183—Call or contact centers with computer-telephony arrangements
    • H04M3/5191—Call or contact centers with computer-telephony arrangements interacting with the Internet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
    • H04M3/523—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing with call distribution or queueing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/56—Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities
    • H04M3/567—Multimedia conference systems

Definitions

  • the present invention relates to the marriage of the Internet with telephony systems, and more specifically, to a system, method and article of manufacture for using the Internet as the communication backbone of a communication system architecture while maintaining a rich array of call processing features.
  • the present invention relates to the interconnection of a communication network including telephony capability with the Internet.
  • the Internet has increasingly become the communication network of choice for the user marketplace.
  • software companies have begun to investigate the transfer of telephone calls across the Internet.
  • the system features that users demand of normal call processing are considered essential for call processing on the Internet.
  • those features are not available on the Internet.
  • the Internet has increasingly become the communication network of choice for the consumer e-mail marketplace. Recently, software companies have begun to investigate the transfer of telephone calls across the Internet.
  • International callback refers to a user being able to dial a number to connect to a switch overseas.
  • the caller allows the phone to ring twice and hangs up.
  • the switch then utilizes the ANI and/ or called number information to query a database of profile information stored on the switch to determine billing and other information on the caller. Then, the switch initiates a call to the caller and when the caller goes offhook, the switch provides a dialtone allowing the caller to access any number available to the switch.
  • international or other long distance callers can obtain low cost long distance services so long as they are pre-registered for the service. This service still requires the caller to be responsible for all of the overhead associated with initiating call processing, requires a caller to learn the protocol of interfacing with the switch, does not provide reservation of such services such as conferencing and it does not allow operator assistance on the calls.
  • AOn-Line Teleconference® capability allows teleconference customers to use an on-line interface to allow customers to pre-arrange an AT&T Teleconference call through the World Wide Web.
  • Aall voice connections are established over the existing telephone network® and require all parties to contact a common number to establish the conference call (AT&T Teleconference Service: On- Line Trial Information, 2/7/97).
  • What is needed is a method, system and article of manufacture for facilitating callback service, providing operation assist on Internet telephony operations, allowing a caller to reserve a time for a call, facilitating Internet telephony operations to be added to a callback service, adding a multidimensional conferencing feature to existing telephony networking and providing an expert system to provide self-regulation of a call system. Further, the method and system is required which is reliable, responsive and effective in interfacing with existing telecommunication networks.
  • telephone calls, data and other multimedia information is routed through a switched network which includes transfer of information across the Internet which may utilize telephony routing information and Internet protocol address information.
  • a telephony order entry procedure captures complete user profile information for a user. This profile information is used by the system throughout the telephony experience for routing, billing, monitoring, reporting and other telephony control functions. Users can manage more aspects of a network than previously possible and control network activities from a central site, while still allowing the operator of the telephone system to maintain quality and routing selection.
  • a hybrid telecommunications system in another aspect of a preferred embodiment of the invention, includes a switched communications network.
  • a packet transmission network is coupled to the switched communications network.
  • a call router is coupled to the switched communications network and the packet transmission network.
  • a memory is coupled to the call router and having stored therein a call parameter database.
  • the call router is configured to route a telephone call over the switched communications network and the packet transmission network based on at least one call parameter from the call parameter database.
  • the call router is further configured to provide an intelligent service platform.
  • the intelligent service platform includes an automated response unit with a plurality of functions available from a single connection.
  • a method for directing calls in a hybrid telecommunications system including a switched communications network and a packet transmission network stores a call parameter database in a memory.
  • a call is received on the system.
  • the call parameter database is accessed to determine at least one call parameter.
  • the call is routed over the switched communications network and the packet transmission network based on the at least one call parameter.
  • An automated response unit is provided. A plurality of functions is made available from a single connection to the automated response unit.
  • a computer program embodied on a computer-readable medium for directing calls in a hybrid telecommunications system including a switched communications network and a packet transmission network has first software that stores a call parameter database in a memory. Second software accesses the call parameter database when the system receives a call to determine at least one call parameter. Third software routes the call over the switched communications network and the packet transmission network based on the at least one call parameter. Fourth software provides an automated response unit. Fifth software makes a plurality of functions available from a single connection to the automated response unit.
  • telephone calls, data and other multimedia information is routed through a switched network which includes transfer of information across the Internet to provide multi-routed and multidimensional callback processing.
  • a telephony order entry procedure captures complete user profile information for a callback operation. This profile information is used by the system throughout the telephony experience for routing, billing, monitoring, reporting and other telephony control functions. Users can manage more aspects of telephony experience and as necessary can specify a date and time for a callback telephony experience to occur. Operator assistance may also be included in the system.
  • a display may also be included in the system. The display may include status information. The display can be provided via a web page. The status information can include information pertaining to a callback session.
  • Figure 1A is a block diagram of a representative hardware environment in accordance with a preferred embodiment
  • Figure IB is a block diagram illustrating the architecture of a typical
  • FIG. IC is a block diagram of an internet telephony system in accordance with a preferred embodiment
  • Figure ID is a block diagram of a hybrid switch in accordance with a preferred embodiment
  • Figure IE is a block diagram of the connection of a hybrid switch in accordance with a preferred embodiment
  • Figure IF is a block diagram of a hybrid (internet-telephony) switch in accordance with a preferred embodiment
  • Figure IG is a block diagram showing the software processes involved in the hybrid internet telephony switch in accordance with a preferred embodiment
  • FIG. 2 is a block diagram illustrating the use of PMUs in a typical SS7 network in accordance with a preferred embodiment
  • Figure 3 is a block diagram illustrating the systems architecture of the preferred embodiment
  • Figure 4 is a high-level process flowchart illustrating the logical system components in accordance with a preferred embodiment
  • FIGS. 5 - 9 are process flowcharts illustrating the detailed operation of the components illustrated in Figure 4 in accordance with a preferred embodiment
  • FIG. 10A illustrates a Public Switched Telephone Network (PSTN) 1000 comprising a Local Exchange Carrier (LEC) 1020 through which a calling party uses a telephone 1021 or computer 1030 to gain access to a switched network in accordance with a preferred embodiment;
  • PSTN Public Switched Telephone Network
  • LEC Local Exchange Carrier
  • Figure 10B illustrates an internet routing network in accordance with a preferred embodiment
  • FIG. 11 illustrates a VNET Personal Computer (PC) to PC Information call flow in accordance with a preferred embodiment
  • Figure 12 illustrates a VNET Personal Computer (PC) to out-of-network PC Information call flow in accordance with a preferred embodiment
  • Figure 13 illustrates a NNET Personal Computer (PC) to out-of-network Phone Information call flow in accordance with a preferred embodiment
  • Figure 14 illustrates a VNET Personal Computer (PC) to in-network Phone Information call flow in accordance with a preferred embodiment
  • Figure 15 illustrates a personal computer to personal computer internet telephony call in accordance with a preferred embodiment
  • Figure 16 illustrates a phone call that is routed from a PC through the Internet to a phone in accordance with a preferred embodiment
  • Figure 17 illustrates a phone to PC call in accordance with a preferred embodiment
  • Figure 18 illustrates a phone to phone call over the internet in accordance with a preferred embodiment
  • Figure 19A and 19B illustrate an Intelligent Network in accordance with a preferred embodiment
  • Figure 19C illustrates a Video-Conferencing Architecture in accordance with a preferred embodiment
  • Figure 19D illustrates a Video Store and Forward Architecture in accordance with a preferred embodiment
  • Figure 19E illustrates an architecture for transmitting video telephony over the Internet in accordance with a preferred embodiment
  • Figure 19F is a block diagram of an internet telephony system in accordance with a preferred embodiment
  • Figure 19G is a block diagram of a prioritizing access/ router in accordance with a preferred embodiment
  • Figure 20 is a high level block diagram of a networking system in accordance with a preferred embodiment
  • Figure 21 is a functional block diagram of a portion of the system shown in Figure 20 in accordance with a preferred embodiment
  • Figure 22 is another high level block diagram in accordance with a preferred embodiment of Figure 21;
  • FIG. 23 is a block diagram of a switchless network system in accordance with a preferred embodiment
  • Figure 24 is a hierarchy diagram illustrating a portion of the systems shown in Figures 20 and 23 in accordance with a preferred embodiment
  • Figure 25 is a block diagram illustrating part of the system portion shown in Figure 24 in accordance with a preferred embodiment
  • Figure 26 is a flow chart illustrating a portion of a method in accordance with a preferred embodiment
  • Figures 27-39 are block diagrams illustrating further aspects of the systems of Figures 20 and 23 in accordance with a preferred embodiment
  • Figure 40 is a diagrammatic representation of a web server logon in accordance with a preferred embodiment
  • Figure 41 is a diagrammatic representation of a server directory structure used with the logon of Figure 40 in accordance with a preferred embodiment
  • Figure 42 is a more detailed diagrammatic representation of the logon of Figure 40 in accordance with a preferred embodiment
  • Figures 43-50 are block diagrams illustrating portions of the hybrid network in accordance with a preferred embodiment
  • FIG 51 illustrates a configuration of the Data Management Zone (DMZ) 5105 in accordance with a preferred embodiment
  • Figures 52A-52C illustrate network block diagrams in connection with a dial-in environment in accordance with a preferred embodiment
  • Figure 53 depicts a flow diagram illustrating the fax tone detection in accordance with a preferred embodiment
  • Figures 54A through 54E depict a flow diagram illustrating the VFP Completion process for fax and voice mailboxes in accordance with a preferred embodiment
  • Figures 55A and 55B illustrate the operation of the Pager Termination processor in accordance with a preferred embodiment
  • Figure 56 depicts the GetCallback routine called from the pager termination in accordance with a preferred embodiment
  • Figure 57 shows a user login screen for access to online profile management in accordance with a preferred embodiment
  • Figure 58 shows a call routing screen, used to set or change a user's call routing instructions in accordance with a preferred embodiment
  • Figure 59 shows a guest menu configuration screen, used to set up a guest menu for presentation to a caller who is not an account owner in accordance with a preferred embodiment
  • Figure 60 shows an override routing screen, which allows a user to route all calls to a selected destination in accordance with a preferred embodiment
  • Figure 61 shows a speed dial numbers screen, used to set up speed dial in accordance with a preferred embodiment
  • Figure 62 shows a voicemail screen, used to set up voicemail in accordance with a preferred embodiment
  • Figure 63 shows a faxmail screen, used to set up faxmail in accordance with a preferred embodiment
  • Figure 64 shows a call screening screen, used to set up call screening in accordance with a preferred embodiment
  • Figures 65-67 show supplemental screens used with user profile management in accordance with a preferred embodiment
  • Figure 68 is a flow chart showing how the validation for user entered speed dial numbers is carried out in accordance with a preferred embodiment
  • FIGS 69A-69AI are automated response unit (ARU) call flow charts showing software implementation in accordance with a preferred embodiment
  • Figures 70A-70R are console call flow charts further showing software implementation in accordance with a preferred embodiment
  • Figure 71 illustrates a typical customer configuration for a VNET to VNET system in accordance with a preferred embodiment
  • Figure 72 illustrates the operation of DAPs in accordance with a preferred embodiment
  • Figure 73 illustrates the process by which a telephone connects to a release link trunk for 1-800 call processing in accordance with a preferred embodiment
  • Figure 74 illustrates the customer side of a DAP procedure request in accordance with a preferred embodiment
  • Figure 75 illustrates operation of the switch 10530 to select a particular number or "hotline" for a caller in accordance with a preferred embodiment
  • Figure 76 illustrates the operation of a computer-based voice gateway for selectively routing telephone calls through the Internet in accordance with a preferred embodiment
  • Figure 77 illustrates the operation of the VRU of figure 76 deployed in a centralized architecture in accordance with a preferred embodiment
  • Figure 78 illustrates the operation of the VRU of figure 76 deployed in a distributed architecture in accordance with a preferred embodiment
  • Figure 79A and 79B illustrate the operation of sample applications for Internet call routing in accordance with a preferred embodiment
  • Figure 79B illustrates a number of applications for caller-initiated consumer transactions in accordance with a preferred embodiment
  • Figure 80 illustrates a configuration of a switching network offering voice mail and voice response unit services, as well as interconnection into a service provider, in accordance with a preferred embodiment
  • Figure 81 illustrates an inbound shared Automated Call Distributor (ACD) call with data sharing through a database in accordance with a preferred embodiment
  • Figure 82 is a block diagram of an exemplary telecommunications system in accordance with a preferred embodiment
  • Figure 83 is a block diagram of an exemplary computer system in accordance with a preferred embodiment
  • Figure 84 illustrates the CDR and PNR call record formats in accordance with a preferred embodiment
  • Figures 85(A) and 85(B) collectively illustrate the ECDR and EPNR call record formats in accordance with a preferred embodiment
  • Figure 86 illustrates the OSR and POSR call record formats in accordance with a preferred embodiment
  • Figures 87(A) and 87(B) collectively illustrate the EOSR and EPOSR call record formats in accordance with a preferred embodiment
  • Figure 88 illustrates the SER call record format in accordance with a preferred embodiment
  • Figures 89(A) and 89(B) are control flow diagrams illustrating the conditions under which a switch uses the expanded record format in accordance with a preferred embodiment
  • Figure 90 is a control flow diagram illustrating the Change Time command in accordance with a preferred embodiment
  • Figure 91 is a control flow diagram illustrating the Change Daylight Savings Time command in accordance with a preferred embodiment
  • Figure 92 is a control flow diagram illustrating the Network Call Identifier (NCID) switch call processing in accordance with a preferred embodiment
  • Figure 93 is a control flow diagram illustrating the processing of a received Network Call Identifier in accordance with a preferred embodiment
  • Figure 94(A) is a control flow diagram illustrating the generation of a Network Call Identifier in accordance with a preferred embodiment
  • Figure 94(B) is a control flow diagram illustrating the addition of a Network Call Identifier to a call record in accordance with a preferred embodiment
  • Figure 95 is a control flow diagram illustrating the transport of a call in accordance with a preferred embodiment
  • Figure 96 shows a hardware component embodiment for allowing a video operator to participate in a video conferencing platform, providing services including but not limited to monitoring, viewing and recording any video conference call and assisting the video conference callers in accordance with a preferred embodiment
  • Figure 97 shows a system for enabling a video operator to manage video conference calls which includes a video operator console system in accordance with a preferred embodiment
  • Figure 98 shows a system for enabling a video operator to manage video conference calls which includes a video operator console system in accordance with a preferred embodiment
  • Figure 99 shows how a video conference call initiated by the video operator in accordance with a preferred embodiment
  • Figure 100 shows the class hierarchy for video operator software system classes in accordance with a preferred embodiment
  • Figure 101 shows a state transition diagram illustrating the state changes that may occur in the VOCall object's m_state variable in accordance with a preferred embodiment
  • Figure 102 shows a state transition diagram illustrating the state changes that may occur in the VOConnection object's m_state variable ("state variable") in accordance with a preferred embodiment
  • Figure 103 shows a state transition diagram illustrating the state changes that may occur in the VOConference object's m_state variable ("state variable") in accordance with a preferred embodiment
  • Figure 104 shows a state transition diagram illustrating the state changes that may occur in the VORecorder object's m_state variable ("state variable") in accordance with a preferred embodiment
  • Figure 105 shows a state transition diagram illustrating the state changes that may occur in the VORecorder object's m_state variable ("state variable") in accordance with a preferred embodiment
  • FIG 106 shows the class hierarchy for the video operator graphics user interface ("GUI") classes in accordance with a preferred embodiment
  • Figure 107 shows a database schema for the video operator shared database in accordance with a preferred embodiment
  • Figure 108 shows one embodiment of the Main Console window in accordance with a preferred embodiment
  • Figure 109 shows one embodiment of the Schedule window in accordance with a preferred embodiment
  • FIG 110 shows one embodiment of the Conference window 41203, which is displayed when the operator selects a conference or playback session in the Schedule window in accordance with a preferred embodiment
  • Figure 111 shows one embodiment of the Video Watch window 41204, which displays the H.320 input from a selected call of a conference connection or a separate incoming or outgoing call in accordance with a preferred embodiment
  • Figure 112 shows one embodiment of the Console Output window 41205 which displays all error messages and alerts in accordance with a preferred embodiment
  • Figure 113 shows a Properties dialog box in accordance with a preferred embodiment.
  • Figure 114A is a block diagram of an access/router system in accordance with a preferred embodiment.
  • Figure 114B is a block diagram of the architecture in accordance with a preferred embodiment.
  • Figure 115 is a block diagram of an internet based callback architecture in accordance with a preferred embodiment.
  • ITU-T Standardization Sector
  • ISN Intelligent Services Network
  • Service Interactions 80 7. Service Monitoring 81 I. ISP Data Management Model 82
  • LRM Local Resource Manager
  • Token Servers 454 132 Profile Management Application Servers 133
  • Hardware 159 2. Object-Oriented Software Tools 159
  • VNET Call Processing 195 Descriptions of Block Elements 198
  • VNET PC connects to a corporate intranet and logs in to a directory service 203
  • VNET PC queries a directory service for a VNET translation 207
  • ITG connects to a PC 210
  • Video Mail Server 251 5. Video Content Engine 251
  • Video Content Engine 258 5. Conference Reservation Engine 258
  • Multipoint Control Unit 265
  • Gateway 266 Support Service Units 266
  • the ARU (Audio Response Unit) 502 389 2.
  • the VFP (Voice Fax Platform) 504 389
  • VFP Voice Fax Platform
  • the Internet is a method of interconnecting physical networks and a set of conventions for using networks that allow the computers they reach to interact. Physically, the Internet is a huge, global network spanning over 92 countries and comprising 59,000 academic, commercial, government, and military networks, according to the Government Accounting Office (GAO), with these numbers expected to double each year. Furthermore, there are about 10 million host computers, 50 million users, and 76,000 World-Wide Web servers connected to the Internet.
  • the backbone of the Internet consists of a series of high-speed communication links between major supercomputer sites and educational and research institutions within the U.S. and throughout the world.
  • Internet is a generic term used to refer to an entire class of networks.
  • An "internet” (lowercase “i”) is any collection of separate physical networks, interconnected by a common protocol, to form a single logical network, whereas the "Internet” (uppercase “I”) is the worldwide collection of interconnected networks that uses Internet Protocol to link the large number of physical networks into a single logical network.
  • TCP/IP Transmission Control Protocol/ Internet Protocol
  • RRCs Requests for Comments
  • ITU-T International Telecommunication Union- Telecommunication Standardization Sector
  • ITU-T International Telecommunication Union-Telecommunication Standardization Sector
  • ITU G.711 Recommendation for Pulse Code Modulation of 3kHz Audio Channels.
  • ITU G.722 Recommendation for 7kHz Audio Coding within a 64kbit/s channel.
  • ITU G.723 Recommendation for dual rate speech coder for multimedia communication transmitting at 5.3 and 6.3 kbits.
  • ITU G.728 Recommendation for coding of speech at 16kbit/s using low- delay code excited linear prediction (LD-CELP)
  • ITU H.223 Multiplexing Protocols for Low Bitrate Multimedia Terminals
  • ITU H.225 ITU Recommendation for Media Stream Packetization
  • ITU H.243 System for Establishing Communication Between Three or More
  • Audiovisual Terminals Using Digital Channels up to 2 Mbit/s ITU H.245 Recommendation for a control protocol for multimedia communication
  • ITU H.261 Recommendation for Video Coder-Decoder for audiovisual services supporting video resolutions of 352x288 pixels and 176x144 pixels.
  • ITU H.323 ITU Recommendation for Visual Telephone Systems and Equipment for Local Area Networks which provide a non-guaranteed quality of service.
  • ITU H.324 Recommendation for Terminals and Systems for low bitrate(28.8 Kbps) multimedia communication on dial-up telephone lines.
  • ISDN Integrated Services Digital Network the digital communication standard for transmission of voice, video and data on a single communications link.
  • RTP Real-Time Transport Protocol an Internet Standard Protocol for transmission of real-time data like voice and video over unicast and multicast networks.
  • IP Internet Protocol an Internet Standard Protocol for transmission and delivery of data packets on a packet switched network of interconnected computer systems.
  • TCP/IP Open protocol standards, freely available and developed independently of any hardware or operating system. Thus, TCP/IP is capable of being used with different hardware and software, even if Internet communication is not required.
  • TCP/IP can be used over an Ethernet, a token ring, a dial-up line, or virtually any other kinds of physical transmission media.
  • the traditional type of communication network is circuit switched.
  • the U.S. telephone system uses such circuit switching techniques.
  • the switching equipment within the telephone system seeks out a physical path from the originating telephone to the receiver's telephone.
  • a circuit-switched network attempts to form a dedicated connection, or circuit, between these two points by first establishing a circuit from the originating phone through the local switching office, then across trunk lines, to a remote switching office, and finally to the destination telephone. This dedicated connection exists until the call terminates.
  • the establishment of a completed path is a prerequisite to the transmission of data for circuit switched networks.
  • the microphone captures analog signals, and the signals are transmitted to the Local Exchange Carrier (LEC) Central Office (CO) in analog form over an analog loop.
  • LEC Local Exchange Carrier
  • CO Central Office
  • the analog signal is not converted to digital form until it reaches the LEC Co, and even then only if the equipment is modern enough to support digital information.
  • the analog signals are converted to digital at the device and transmitted to the LEC as digital information.
  • the circuit guarantees that the samples can be delivered and reproduced by maintaining a data path of 64 Kbps (thousand bits per second). This rate is not the rate required to send digitized voice per se. Rather, 64Kbps is the rate required to send voice digitized with the Pulse Code Modulated (PCM) technique. Many other methods for digitizing voice exist, including ADPCM (32Kbps), GSM ( 13 Kbps), TrueSpeech 8.5 (8.5 Kbps), G.723 (6.4 Kbps or 5.3 Kbps) and Voxware RT29HQ (2.9 Kbps). Furthermore, the 64 Kbps path is maintained from LEC Central Office (CO) Switch to LEC CO, but not from end to end. The analog local loop transmits an analog signal, not 64 Kbps digitized audio. One of these analog local loops typically exists as the "last mile" of each of the telephone network circuits to attach the local telephone of the calling party.
  • PCM Pulse Code Modulated
  • circuit switching has two significant drawbacks.
  • the entire circuit switching infrastructure is built around 64 Kbps circuits.
  • the infrastructure assumes the use of PCM encoding techniques for voice.
  • very high quality codecs are available that can encode voice using less than one-tenth of the bandwidth of PCM.
  • the circuit switched network blindly allocates 64 Kbps of bandwidth for a call, end-to-end, even if only one-tenth of the bandwidth is utilized.
  • each circuit generally only connects two parties.
  • Circuit switching has no multicast or multipoint communication capabilities, except when used in combination with conference bridging equipment.
  • Packet switched networks which predominate the computer network industry, divide data into small pieces called packets that are multiplexed onto high capacity intermachine connections.
  • a packet is a block of data with a strict upper limit on block size that carries with it sufficient identification necessary for delivery to its destination.
  • Such packets usually contain several hundred bytes of data and occupy a given transmission line for only a few tens of milliseconds. Delivery of a larger file via packet switching requires that it be broken into many small packets and sent one at a time from one machine to the other.
  • the network hardware delivers these packets to the specified destination, where the software reassembles them into a single file.
  • Packet switching is used by virtually all computer interconnections because of its efficiency in data transmissions. Packet switched networks use bandwidth on a circuit as needed, allowing other transmissions to pass through the lines in the interim. Furthermore, throughput is increased by the fact that a router or switching office can quickly forward to the next stop any given packet, or portion of a large file, that it receives, long before the other packets of the file have arrived. In message switching, the intermediate router would have to wait until the entire block was delivered before forwarding. Today, message switching is no longer used in computer networks because of the superiority of packet switching. To better understand the Internet, a comparison to the telephone system is helpful. The public switched telephone network was designed with the goal of transmitting human voice, in a more or less recognizable form.
  • the Internet is composed of a great number of individual networks, together forming a global connection of thousands of computer systems. After understanding that machines are connected to the individual networks, we can investigate how the networks are connected together to form an internetwork, or an internet. At this point, internet gateways and internet routers come into play.
  • gateways and routers provide those links necessary to send packets between networks and thus make connections possible. Without these links, data communication through the Internet would not be possible, as the information either would not reach its destination or would be incomprehensible upon arrival.
  • a gateway may be thought of as an entrance to a communications network that performs code and protocol conversion between two otherwise incompatible networks. For instance, gateways transfer electronic mail and data files between networks over the internet.
  • IP Routers are also computers that connect networks and is a newer term preferred by vendors. These routers must make decisions as to how to send the data packets it receives to its destination through the use of continually updated routing tables. By analyzing the destination network address of the packets, routers make these decisions. Importantly, a router does not generally need to decide which host or end user will receive a packet; instead, a router seeks only the destination network and thus keeps track of information sufficient to get to the appropriate network, not necessarily the appropriate end user. Therefore, routers do not need to be huge supercomputing systems and are often just machines with small main memories and little disk storage. The distinction between gateways and routers is slight, and current usage blurs the line to the extent that the two terms are often used interchangeably. In current terminology, a gateway moves data between different protocols and a router moves data between different networks. So a system that moves mail between TCP/IP and OSI is a gateway, but a traditional IP gateway (that connects different networks) is a router.
  • the telephone system is organized as a highly redundant, multilevel hierarchy. Each telephone has two copper wires coming out of it that go directly to the telephone company's nearest end office, also called a local central office. The distance is typically less than 10 km; in the U.S. alone, there are approximately 20,000 end offices.
  • the concatenation of the area code and the first three digits of the telephone number uniquely specify an end office and help dictate the rate and billing structure.
  • the two-wire connections between each subscriber's telephone and the end office are called local loops. If a subscriber attached to a given end office calls another subscriber attached to the same end office, the switching mechanism within the office sets up a direct electrical connection between the two local loops. This connection remains intact for the duration of the call, due to the circuit switching techniques discussed earlier.
  • each end office has a number of outgoing lines to one or more nearby switching centers, called toll offices. These lines are called toll connecting trunks. If both the caller's and the receiver's end offices happen to have a toll connecting trunk to the same toll office, the connection may be established within the toll office. If the caller and the recipient of the call do not share a toll office, then the path will have to be established somewhere higher up in the hierarchy.
  • TCP/IP In addition to the data transfer functionality of the Internet, TCP/IP also seeks to convince users that the Internet is a solitary, virtual network. TCP/IP accomplishes this by providing a universal interconnection among machines, independent of the specific networks to which hosts and end users attach. Besides router interconnection of physical networks, software is required on each host to allow application programs to use the Internet as if it were a single, real physical network. D. Datagrams and Routing
  • IP Internet Protocol/IP
  • datagrams The basis of Internet service is an underlying, connectionless packet delivery system run by routers, with the basic unit of transfer being the packet.
  • TCP/IP such as the Internet backbone
  • these packets are called datagrams. This section will briefly discuss how these datagrams are routed through the Internet.
  • routing is the process of choosing a path over which to send packets.
  • routers are the computers that make such choices. For the routing of information from one host within a network to another host on the same network, the datagrams that are sent do not actually reach the Internet backbone. This is an example of internal routing, which is completely self-contained within the network. The machines outside of the network do not participate in these internal routing decisions.
  • Direct delivery is the transmission of a datagram from one machine across a single physical network to another machine on the same physical network. Such deliveries do not involve routers. Instead, the sender encapsulates the datagram in a physical frame, addresses it, and then sends the frame directly to the destination machine.
  • Indirect delivery is necessary when more than one physical network is involved, in particular when a machine on one network wishes to communicate with a machine on another network. This type of communication is what we think of when we speak of routing information across the Internet backbone.
  • routers are required. To send a datagram, the sender must identify a router to which the datagram can be sent, and the router then forwards the datagram towards the destination network. Recall that routers generally do not keep track of the individual host addresses (of which there are millions), but rather just keeps track of physical networks (of which there are thousands). Essentially, routers in the Internet form a cooperative, interconnected structure, and datagrams pass from router to router across the backbone until they reach a router that can deliver the datagram directly.
  • ATM Asynchronous Transfer Mode
  • ATM incorporates features of both packet switching and circuit switching, as it is designed to carry voice, video, and television signals in addition to data. Pure packet switching technology is not conducive to carrying voice transmissions because such transfers demand more stable bandwidth. JB. Frame Relay
  • Frame relay systems use packet switching techniques, but are more efficient than traditional systems. This efficiency is partly due to the fact that they perform less error checking than traditional X.25 packet- switching services. In fact, many intermediate nodes do little or no error checking at all and only deal with routing, leaving the error checking to the higher layers of the system. With the greater reliability of today's transmissions, much of the error checking previously performed has become unnecessary. Thus, frame relay offers increased performance compared to traditional systems.
  • An Integrated Services Digital Network is an "international telecommunications standard for transmitting voice, video, and data over digital lines," most commonly running at 64 kilobits per second. The traditional phone network runs voice at only 4 kilobits per second.
  • an end user or company must upgrade to ISDN terminal equipment, central office hardware, and central office software. The ostensible goals of ISDN include the following:
  • the MCI Intelligent Network is a call processing architecture for processing voice, fax and related services.
  • the Intelligent Network comprises a special purpose bridging switch with special capabilities and a set of general purpose computers along with an Automatic Call Distributor (ACD).
  • ACD Automatic Call Distributor
  • the call processing including number translation services, automatic or manual operator services, validation services and database services are carried out on a set of dedicated general purpose computers with specialized software. New value added services can be easily integrated into the system by enhancing the software in a simple and cost-effective manner.
  • the Intelligent Network Architecture has a rich set of features and is very flexible. Addition of new features and services is simple and fast. Features and services are extended utilizing special purpose software running on general purpose computers. Adding new features and services involves upgrading the special purpose software and is cost-effective.
  • FIG 19A illustrates an Intelligent Network in accordance with a preferred embodiment.
  • the MCI Intelligent Network is comprised of a large number of components.
  • Major components of the MCI Intelligent Network include the
  • NCS Network Control System
  • DAP Data Access Point
  • MCI Switching Network The MCI switching network is comprised of special purpose bridging switches 2. These bridging switches 2 route and connect the calling and the called parties after the call is validated by the intelligent services network 4.
  • the bridging switches have limited programming capabilities and provide the basic switching services under the control of the Intelligent Services Network (ISN) 4.
  • ISN Intelligent Services Network
  • NCS/DAP Network Control System/Data Access Point
  • the NCS/DAP 3 is an integral component of the MCI Intelligent Network.
  • the DAP offers a variety of database services like number translation and also provides services for identifying the switch ID and trunk ID of the terminating number for a call.
  • NCS/DAP 3 The different services offered by NCS/DAP 3 include:
  • Range Restrictions to restrict toll calling options and advanced parametric routing including Time of Day, Day of Week/ Month,
  • ISN Intelligent Services Network
  • the ISN 4 includes an Automatic Call Distributor (ACD) for routing the calls.
  • ACD Automatic Call Distributor
  • the ACD communicates with the Intelligent Switch Network Adjunct
  • ISNAP Intelligent Network Processor
  • the ISN includes the ISNAP 5 and the Operator Network Center (ONC).
  • ISNAP 5 is responsible for Group Select and Operator Selection for call routing.
  • the ISNAP communicates with the ACD for call delivery to the different agents.
  • the ISNAP is also responsible for coordinating data and voice for operator-assisted calls.
  • the ONC is comprised of Servers, Databases and Agents including Live Operators or Audio Response Units (ARU) including Automated Call Processors (ACP)s, MTOCs and associated NAS 7. These systems communicate with each other on an Ethernet LAN and provide a variety of services for call processing.
  • the different services offered by the ONC include:
  • Enhanced Voice Services offer menu-based routing services in addition to a number of value-added features.
  • the EVS system prompts the user for an input and routes calls based on customer input or offers specialized services for voice mail and fax routing.
  • the different services offered as a part of the EVS component of the MCI Intelligent Network include:
  • Intelligent Call Routing (ICR) services are offered for specialized call routing based on information obtained from the calling party either during the call or at an earlier time. Routing is also based on the knowledge of the physical and logical network layout. Additional intelligent routing services based on time of day, alternate routing based on busy routes are also offered.
  • Billing is a key component of the MCI Intelligent Network.
  • the billing component provides services for customer billing based on call type and call duration. Specialized billing services are additionally provided for value added services like the 800 Collect calls.
  • Fraud Monitoring component is a key component of the MCI Intelligent Network providing services for preventing loss of revenue due to fraud and illegal usage of the network.
  • Operational Measurements include information gathering for analysis of product performance. Analysis of response to advertising campaigns, calling patterns resulting in specialized reports result from operational measurements. Information gathered is also used for future product planning and predicting infrastructure requirements.
  • Usage Statistics Reporting includes gathering information from operational databases and billing information to generate reports of usage. The usage statistics reports are used to study call patterns, load patterns and also demographic information. These reports are used for future product plans and marketing input.
  • the MCI Call Processing architecture is built upon a number of key components including the MCI Switch Network, the Network Control System, the Enhanced Voice Services system and the Intelligent Services Network. Call processing is entirely carried out on a set of general purpose computers and some specialized processors thereby forming the basis for the MCI Intelligent Network.
  • the switch is a special purpose bridging switch with limited programming capabilities and complex interface. Addition of new services on the switch is very difficult and sometimes not possible.
  • a call on the MCI Switch is initially verified if it needs a number translation as in the case of an 800 number. If a number translation is required, it is either done at the switch itself based on an internal table or the request is sent to the DAP which is a general purpose computer with software capable of number translation and also determining the trunk ID and switch ID of the terminating number.
  • the call can be routed to an ACD which delivers calls to the various call processing agents like a live operator or an ARU.
  • the ACD communicates with the ISNAP which does a group select to determine which group of agents are responsible for this call and also which of the agents are free to process this call.
  • the agents process the calls received by communicating with the NIDS (Network Information Distributed Services) Server which are the Validation or the Database Servers with the requisite databases for the various services offered by ISN.
  • NIDS Network Information Distributed Services
  • the agent communicates the status back to the ACD.
  • the ACD in turn dials the terminating number and bridges the incoming call with the terminating number and executes a Release Link Trunk (RLT) for releasing the call all the way back to the switch.
  • RLT Release Link Trunk
  • the agent also generates a Billing Detail Record (BDR) for billing information.
  • BDR Billing Detail Record
  • OSR Operation Services Record
  • the addition of new value added services is very simple and new features can be added by additional software and configuration of the different computing systems in the ISP. A typical call flow scenario is explained below.
  • the Call Flow example illustrates the processing of an 800 Number Collect Call from phone 1 in Figure 19A to phone 10.
  • the call is commenced when a calling party dials 1-800-COLLECT to make a collect call to phone 10 the Called Party.
  • the call is routed by the Calling Party's Regional Bell Operating Company (RBOC), which is aware that this number is owned by MCI, to a nearest MCI Switch Facility and lands on an MCI switch 2.
  • RBOC Regional Bell Operating Company
  • the switch 2 detects that it is an 800 Number service and performs an 800 Number Translation from a reference table in the switch or requests the Data Access Point (DAP) 3 to provide number translation services utilizing a database lookup.
  • DAP Data Access Point
  • the call processing is now delegated to a set of intelligent computing systems through an Automatic Call Distributor (ACD) 4.
  • ACD Automatic Call Distributor
  • ACD 4 Automatic Call Distributor
  • the call from the switch is transferred to an ACD 4 which is operational along with an Intelligent Services Network Adjunct Processor (ISNAP) 5.
  • the ISNAP 5 determines which group of Agents are capable of processing the call based on the type of the call. This operation is referred to as Group Select.
  • the agents capable of call processing include Manual Telecommunications Operator Console (MTOC)s 6 or Automated Call Processors (ACP)s 7 with associated Network Audio Servers (NAS)s 7a.
  • MTOC Manual Telecommunications Operator Console
  • ACP Automated Call Processors
  • NAS Network Audio Servers
  • the Agents are built with sophisticated call processing software.
  • the Agent gathers all the relevant information from the Calling Party including the telephone number of the Called Party.
  • the Agent then communicates with the database servers with a set of database lookup requests.
  • the database lookup requests include queries on the type of the call, call validation based on the telephone numbers of both the calling and the called parties and also call restrictions, if any, including call blocking restrictions based on the called or calling party's telephone number.
  • the Agent then signals the ISNAP-ACD combination to put the Calling Party on hold and dial the called party and to be connected to the Called Party.
  • the Agent informs the called party about the Calling Party and the request for a Collect Call.
  • the Agent gathers the response from the Called Party and further processes the call.
  • the Agent then signals the ISNAP-ACD combination to bridge the Called Party and the Calling Party.
  • the Agent then cuts a BDR which is used to match with a respective OSR generated by the switch to create complete billing information.
  • the ISNAP- ACD combination then bridges the Called Party and the Calling Party and then releases the line back to the switch by executing a Release Trunk (RLT).
  • RLT Release Trunk
  • the Calling Party and the Called Party can now have a conversation through the switch.
  • the switch At the termination of the call by either party, the switch generates a OSR which will be matched with the BDR generated earlier to create complete billing information for the call.
  • the Agent If the Called Party declines to accept the collect call, the Agent signals the ACD -ISNAP combination to reconnect the Calling Party which was on hold back to the Agent. Finally, the Agent informs the Calling Party about the Called Party's response and terminates the call in addition to generating a BDR.
  • MCI Intelligent Network is a scaleable and efficient network architecture for call processing and is based on a set of intelligent processors with specialized software, special purpose bridging switches and ACD's.
  • the Intelligent Network is an overlay network coexisting with the MCI Switching Network and is comprised of a large number of specialized processors interacting with the switch network for call processing.
  • One embodiment of Intelligent Network is completely audio-centric. Data and fax are processed as voice calls with some specialized, dedicated features and value-added services.
  • the Intelligent Network is adapted for newly emerging technologies, including POTS-based video-phones and internet telephony for voice and video.
  • newly emerging technologies including POTS-based video-phones and internet telephony for voice and video.
  • the ISP is composed of several disparate systems. As ISP integration proceeds, formerly independent systems now become part of one larger whole with concomitant increases in the level of analysis, testing, scheduling, and training in all disciplines of the ISP.
  • Broadband Access A range of high bandwidth services are supported by a preferred embodiment. These include: Video on Demand, Conferencing, Distance Learning, and Telemedicine.
  • ATM asynchronous transfer mode pushes network control to the periphery of the network, obviating the trunk and switching models of traditional, circuit-based telephony. It is expected to be deployed widely to accommodate these high bandwidth services.
  • the Internet Telephony System offers easy customer access, widespread commercial opportunities, and fosters a new role for successful telecommunications companies.
  • the ISP platform offers many features which can be applied or reapplied from telephony to the Internet. These include access, customer equipment, personal accounts, billing, marketing (and advertising) data or application content, and even basic telephone service.
  • the telecommunication industry is a major transmission provider of the Internet.
  • a preferred embodiment which provides many features from telephony environments for Internet clients is optimal.
  • Figure 19F is a block diagram of an internet telephony system in accordance with a preferred embodiment.
  • a number of computers 1900, 1901, 1902 and 1903 are connected behind a firewall 1905 to the Internet 1910 via an Ethernet or other network connection.
  • a domain name system 1906 maps names to IP addresses in the Internet 1910.
  • Individual systems for billing 1920, provisioning 1922, directory services 1934, messaging services 1930, such as voice messaging 1932 are all attached to the internet 1910 via a communication link.
  • Another communication link is also utilized to facilitate communications to a satellite device 1940 that is used to communicate information to a variety of set top devices 1941-1943.
  • a web server 1944 provides access for an order entry system 1945 to the Internet 1910.
  • the order entry system 1945 generates complete profile information for a given telephone number, including, name, address, fax number, secretary's number, wife's phone number, pager, business address, e-mail address, IP address and phonemail address. This information is maintained in a database that can be accessed by everyone on the network with authorization to do so.
  • the order entry system utilizes a web interface for accessing an existing directory service database 1934 to provide information for the profile to supplement user entered information.
  • the Internet 1910 is tied to the Public Switched Network (PSTN) 1960 via a gateway 1950.
  • the gateway 1950 in a preferred embodiment provides a virtual connection from a circuit switched call in the PSTN 1960 and some entity in the Internet 1910.
  • the PSTN 1960 has a variety of systems attached, including a direct-dial input 1970, a Data Access Point (DAP) 1972 for facilitating 800 number processing and Virtual NETwork (VNET) processing to facilitate for example a company tieline.
  • DAP Data Access Point
  • VNET Virtual NETwork
  • a Public Branch Exchange (PBX) 1980 is also attached via a communication link for facilitating communication between the PSTN 1960 and a variety of computer equipment, such as a fax 1981, telephone 1982 and a modem 1983.
  • An operator 1973 can also optionally attach to a call to assist in placing a call or conference call coming into and going out of the PSTN 1960 or the internet 1910.
  • ISN Intelligent Services Network
  • DAP Dynamic Access Protocol
  • FIG 19G is a block diagram of a Prioritizing Access/ Router in accordance with a preferred embodiment.
  • a prioritizing access router is designed to combine the features of an internet access device and an Internet Protocol (IP) Router. It enables dial-up modem access to the internet by performing essential modem and PPP/ SLIP to IP and the reverse IP to PPP/ SLIP conversion. It also analyzes IP packet source/ destination addresses and UPD or TCP ports and selects appropriate outgoing network interfaces for each packet. Lastly, it uses a priority routing technique to favor packets destined for specific network interfaces over packets destined for other network interfaces.
  • IP Internet Protocol
  • the design goal of the prioritizing access/router is to segregate real-time traffic from the rest of the best- effort data traffic on internet networks.
  • Real-time and interactive multimedia traffic is best segregated from traffic without real-time constraints at the access point to the internet, so that greater control over quality of service can be gained.
  • the process that a prioritizing access/ router utilizes is presented below with reference to Figure 19G.
  • a computer dials up the PAR via a modem.
  • the computer modem negotiates a data transfer rate and modem protocol parameters with the PAR modem.
  • the computer sets up a Point to Point Protocol (PPP) session with the PAR using the modem to modem connection over a Public Switched Telephone Network (PSTN) connection.
  • PSTN Public Switched Telephone Network
  • the computer transfers Point-to-Point (PPP) packets to the PAR using the modem connection.
  • the PAR modem 2010 transfers PPP packets to the PPP to IP conversion process 2020 via the modem to host processor interface 2080.
  • the modem to host processor interface can be any physical interface presently available or yet to be invented. Some current examples are ISA, EISA, VME, SCbus, MVIP bus, Memory Channel, and TDM buses. There is some advantage in using a multiplexed bus such as the Time Division Multiplexing buses mentioned here, due to the ability to devote capacity for specific data flows and preserve deterministic behavior.
  • the PPP to IP conversion process 2020 converts PPP packets to IP packets, and transfers the resulting IP packets to the packet classifier 2050 via the process to process interface 2085.
  • the process to process interface can be either a physical interface between dedicated processor hardware, or can be a software interface. Some examples of process to process software interfaces include function or subroutine calls, message queues, shared memory, direct memory access (DMA), and mailboxes.
  • the packet classifier 2085 determines if the packet belongs to any special prioritized group.
  • the packet classifier keeps a table of flow specifications, defined by destination IP Address source IP address combined source/destination IP Address combined destination IP Address/ UDP Port combined destination IP Address/TCP Port combined source IP address/UDP Port combined source IP Address/TCP Port combined source IP Address and TCP or UDP port with destination IP address combined destination IP Address and TCP or UDP port with source IP address combined source IP Address and TCP or UDP port with destination IP address and TCP/UDP Port.
  • the packet classifier checks its table of flow specifications against the IP addresses and UDP or TCP ports used in the packet. If any match is found, the packet is classified as belonging to a priority flow and labeled as with a priority tag. Resource Reservation Setup Protocol techniques may be used for the packet classifier step.
  • the packet classifier 2050 hands off priority tagged and non-tagged packets to the packet scheduler 2060 via the process to process interface (90) .
  • the process to process interface 2090 need not be identical to the process to process interface 2085, but the same selection of techniques is available.
  • the packet scheduler 2060 used a priority queuing technique such as Weighted Fair Queueing to help ensure that prioritized packets (as identified by the packet classifier) receive higher priority and can be placed on an outbound network interface queue ahead of competing best-effort traffic.
  • the packet scheduler 2060 hands off packets in prioritized order to any outbound network interface (2010, 2070, 2071 or 2072) via the host processor to peripheral bus 2095. Any number of outbound network interfaces may be used.
  • IP packets can arrive at the PAR via non-modem interfaces (2070, 2071 and 2072). Some examples of these interfaces include Ethernet, fast Ethernet, FDDI, ATM, and Frame Relay. These packets go through the same steps as IP packets arriving via the modem PPP interfaces.
  • the priority flow specifications are managed through the controller process 2030.
  • the controller process can accept externally placed priority reservations through the external control application programming interface 2040.
  • the controller validates priority reservations for particular flows against admission control procedures and policy procedures, and if the reservation is admitted, the flow specification is entered in the flow specification table in the packet classifier 2050 via the process to process interface 2065.
  • the process to process interface 2065 need not be identical to the process to process interface 2085, but the same selection of techniques is available.
  • FIG 20 there is shown an architectural framework for an Intelligent Services Platform (ISP) 2100, used in the present invention.
  • the architecture of the ISP 2100 is intended to define an integrated approach to the provision and delivery of intelligent services to the MCI network across all the components of the ISP.
  • the architecture of the ISP 2100 defines a single cohesive architectural framework covering these areas. The architecture is focused on achieving the following goals:
  • the target capabilities of the ISP 2100 are envisioned to provide the basic building blocks for very many services. These services are characterized as providing higher bandwidth, greater customer control or personal flexibility, and much reduced , even instantaneous, provisioning cycles.
  • the ISP 2100 has a reach that is global and ubiquitous. Globally, it will reach every country through alliance partners' networks. In breadth, it reaches all business and residential locales through wired or wireless access.
  • Powerful data services including enhanced private networks; and • Software and equipment to enable end users to gain complete control over their services.
  • Services provided by the ISP 2100 will span those needed in advertising, agriculture, education, entertainment, finance, government, law, manufacturing, medicine, network transmission, real estate, research, retailing, shipping, telecommunications, tourism, wholesaling, and many others.
  • Customizable customer is able to tailor the service offerings to their own needs.
  • Customer managed customer has direct (network-side) access for the administration and control of their service.
  • the following section describes the role of the ISP Platform 2100 in providing customer services.
  • the ISP 2100 provides customer services through an intelligent services infrastructure, including provider network facilities 2102, public network facilities 2104, and customer equipment 2106.
  • the services infrastructure ensures the end-to-end quality and availability of customer service.
  • the following section describes the relationship of the ISP platform 2100 to various external systems both within and outside a provider.
  • the provider components 2108 in Figure 20 are: • Intelligent Services 2110 - responsible for service provisioning, service delivery, and service assurance, including the internal data communications networks 2102. This represents the ISP's role.
  • Product Management 2116 responsible for the creation and marketing of customer services.
  • Networks 2104- this represents all the network connections and access methods used by customers 2106 for service. This includes a provider's circuit switched network, packet switched networks, internal extended wide area network, the internet, a provider's wireless partners' networks, a provider's global alliance and national partner networks, broadband networks, as well as the customer premises equipment 2118 attached to these networks.
  • 3rd party Service Providers 2120 - this represents those external organizations which deliver services to customers via the provider's Intelligent Services Platform 2100.
  • Service Resellers 2122 this represents those organizations which have customers using the facilities 2100.
  • ISP Functional Framework Figure 21 shows components of the ISP 2100 in more detail. Shown is the set of logical components comprising the ISP 2100 architecture. None of these components is a single physical entity; each typically occurs multiple times in multiple locations. The components work together to provide a seamless Intelligent Services 2110 environment. This environment is not fixed; it is envisioned as a flexible evolving platform capable of adding new services and incorporating new technologies as they become available. The platform components are linked by one or more network connections which include an internal distributed processing infrastructure.
  • the ISP 2100 Functional Components are:
  • Inbound and Outbound Gateways 2126 allows access to services provided by other providers, and allows other providers to access the provider's services.
  • Management Service Gateway 2130 - illustrates that service creation concepts apply to management of the platform as well as service logic.
  • Management services are deployed and managed through the Management Service Gateway 2130. Also, interfaces with management systems external to ISP 2100 are realized by the Management Service Gateway 2130. Some examples of management services include the collection, temporary storage, and forwarding of (billable) network events. Other services include collection and filtering of alarm information from the ISP 2100 before forwarding to network management 2132.
  • Service Engines 2134 A Service Logic Execution Environment for either marketable or management services.
  • the Service Engines 2134 execute the logic contained in customer-specific profiles in order to provide unique customized service features.
  • Service Creation Environment 2136 Creates and deploys management services as well as marketable services, and their underlying features and capabilities.
  • Data Management 2138 Where all customer and service profile data is deployed. Data is cached on Service Engines 2134, Statistics Servers 2140, Call Context servers 2142, Analysis Servers 2144, and other specialized applications or servers 2146 requiring ISP 2100 data.
  • Service Select 2148 Whether the services are accessed via a narrowband or broadband network, circuit-switched, packet-switched, or cell-switched, the services are accessed via a Service Select function 2148.
  • Service Select 2148 is a specialized version of a service engine 2134, designed specifically to choose a service or services to execute.
  • Resource Managers 2150 manages all resources, including specialized resources 2152 and service instances running on service engines 2134, and any other kind of resource in the ISP 2100 that needs management and allocation.
  • Specialized Resources 2152 Special network-based capabilities (Internet to voice conversion, DTMF-detection, Fax, Voice Recognition, etc) are shown as specialized resources 2152.
  • Call Context Server 2142 accepts network event records and service event records in real time, and allows queries against the data. Once all events for a call (or any other kind of network transaction) are generated, the combined event information is delivered en masse to the Revenue Management function 2154. Data is stored short-term.
  • Statistics Server 2140 accepts statistics events from service engines, performs rollups, and allows queries against the data. Data is stored short- term.
  • Analysis Services 2144- a special kind of service engine that isn't based on network access, but is based on adding value based upon network statistics or call context information in real time or near real time. Examples include fraud detection and customer traffic statistics.
  • FIG 22 shows how the ISP architecture 2100 supplies services via different networks.
  • the networks shown include Internet 2160, the public switched telephony network (PSTN) 2162, Metro access rings 2164, and Wireless 2166. Additionally, it is expected that new "switchless" broadband network architectures 2168 and 2170 such as ATM or ISOEthernet may supplant the current PSTN networks 2162.
  • PSTN public switched telephony network
  • the architecture accommodates networks other than basic PSTNs 2162 due to the fact that these alternative network models support services which cannot be offered on a basic PSTN, often with an anticipated reduced cost structure. These Networks are depicted logically in Figure 22.
  • Each of these new networks are envisioned to interoperate with the ISP 2100 in the same way.
  • Calls (or transactions) will originate in a network from a customer service request, the ISP will receive the transaction and provide service by first identifying the customer and forwarding the transaction to a generalized service-engine 2174.
  • the service engine determines what service features are needed and either applies the necessary logic or avails itself of specialized network resources for the needed features.
  • the ISP 2100 itself is under the control of a series of Resource managers and Administrative and monitoring mechanisms.
  • a single system image is enabled through the concurrent use of a common information base.
  • the information base holds all the Customer, Service, Network and Resource information used or generated by the ISP.
  • Other external applications (from within MCI and in some cases external to MCI) are granted access through gateways, intermediaries, and sometimes directly to the same information base.
  • each entity depicts a single logical component of the ISP. Each of these entities is expected to be deployed in multiple instances at multiple sites.
  • App 2178- an internal ISP application (such as Fraud Analysis);
  • Dc 2180- Data client a client to the ISP information base which provides a local data copy
  • Ds 2182- Data server one of the master copies of ISP information
  • Mon 2186 the ISP monitoring functions (for fault, performance, and accounting); GRM 2188- the global resource management view for selected resources;
  • SR 2192- the pools of specialized resources (such as video servers, ports, speech recognition);
  • the switchless network 2168 is a term used for the application of cell- switching or packet-switching techniques to both data and isochronous multimedia communications services.
  • circuit switching was the only viable technology for transport of time-sensitive isochronous voice.
  • Asynchronous Transfer Mode cell switching networks which provide quality of service guarantees, a single network infrastructure which serves both isochronous and bursty data services is achievable.
  • the switchless network is expected to provide a lower cost model than circuit switched architectures due to:
  • Figure 23 illustrates a sample switchless network 2168 in accordance with a preferred embodiment.
  • the Service Model must support seamless integration of new and existing services.
  • SCE Service Creation Environment
  • SEE common service logic execution environments
  • All services are created from one or more service features.
  • Data stored in a single customer profile in the ISP Data Servers may be used to drive multiple services.
  • the Service Model must support the specification and fulfillment of quality of service parameters for each service. These quality of service parameters, when taken together, constitute a service level agreement with each customer. Service deployment must take into account specified quality of service parameters.
  • Service features are not deployed into the network by themselves. A service feature is only deployed as part of a service logic program which invokes the service feature (see Figure 21). Thus, service features linked into service logic programs statically, while capabilities are linked to service logic programs dynamically. This is where the loose coupling of resources to services is achieved.
  • Capability Principles Capabilities are defined completely independent from consideration of any physical or logical implementation (network implementation independent).
  • Each capability should have a unified and stable interface.
  • the interface is described as a set of operations, and the data required and provided by each operation.
  • Capabilities may be combined to form high-level capabilities.
  • An operation on a capability defines one complete activity.
  • An operation on a capability has one logical starting point and one or more logical ending points.
  • Capabilities may be realized in one or more piece of physical hardware or software in the network implementation.
  • Data required by each capability operation is defined by the capability operation support data parameters and user instance data parameters.
  • Capabilities are deployed into the network independent of any service. 10. Capabilities are global in nature and their location need not be considered by the service designer, as the whole network is regarded as a single entity from the viewpoint of the service designer. 11. Capabilities are reusable. They are used without modification for other services.
  • Each Service Engine 2134 supports a subset of the customer base.
  • the list of customers supported by a service engine is driven by configuration data, stored on the ISP Data Server 2182.
  • Each Service Engine 2134 obtains its configuration data from the ISP data servers 2152 at activation time.
  • Service Engines 2134 use ISP database clients 2180 (see the data management section of this description) to cache the data necessary to support the customers configured for that service engine 2134, as needed. Caching can be controlled by the ISP database server 2182, or controlled by the database of the ISP database server 2182. Data may be cached semi-permanently (on disk or in memory) at a service engine 2134 if it is deemed to be too much overhead to load data from the data server 2182 on a frequent basis.
  • Service Engines 2134 may be expected to execute all of a customer's services, or only a subset of the customer's services. However, in the case of service interactions, one Service Engine 2134 must always be in control of the execution of a service at any given time. Service Engines may hand-off control to other service engines during the course of service execution. 5. Service Engines do not own any data, not even configuration data.
  • Service Engines 2134 are not targets for deployment of data.
  • Data Servers 2182 are targets for deployment of data.
  • Resource Management Model 2150 Principles 1. Resources 2152 should be accessible from anywhere on the network. 2. Resources are not service-specific and can be shared across all services if desired.
  • the Resource Management Model 2150 should be flexible enough to accommodate various management policies, including: Least Cost,
  • the Resource Management Model 2150 should optimize the allocation of resources and, if possible, honoring a selected policy. 6.
  • the RM 2150 must allow for a spectrum of resource allocation techniques ranging from static configuration to fully dynamic allocation of resources on a transaction by transaction basis.
  • the Resource Management Model 2150 must allow for the enforcement of resource utilization policies such as resource time out and preemptive reallocation by priority.
  • the Resource Management Model 2150 must be able to detect and access the status, utilization and health of resources in a resource pool.
  • All Resources 2152 must be treated as managed objects. 10. All resources must be able to register with the RM 2150 to enter a pool, and de-register to leave a pool.
  • the only way to request, acquire and release a resource 2152 is through the RM 2150.
  • the relationship between resources should not be fixed, rather individual instances of a given resource should be allocated from a registered pool in response to need or demand.
  • All specialized resources 2152 must offer SNMP or CMIP agent functionality either directly or through a proxy.
  • Every specialized resource 2152 shall be represented in a common management information base. 16. All specialized resources shall support a standard set of operations to inquire, probe, place in or out of service, and test the item.
  • All specialized resources shall provide a basic set of self- test capabilities which are controlled through the standard SNMP or CMIP management interfaces.
  • Data access should conform to a single set of access methods which is standardized across the ISP 2100.
  • Private data is allowed at a local database, but cannot be shared or distributed.
  • Private formats for a shared data item are allowed at the local database.
  • Transactional capabilities can be relaxed at end-user discretion if allowed within the business rules.
  • Rules-based logic and other meta-data controls provide a flexible means to apply policy.
  • Data Replication provides reliability through duplication of data sources.
  • Database Partitioning provides scalability by decreasing the size of any particular data store, and by decreasing the transaction rate against any particular data store.
  • Data Management 2138 must allow both static and dynamic configuration of data resources.
  • Logical application views of data are insulated from physical data operations such as relocation of files, reloading of databases, or reformatting of data stores. 19. Audit trails, and event histories, are required for adequate problem resolutions.
  • Data Management 2138 mechanisms must scale for high levels of growth.
  • Data Management 2138 mechanisms must provide cost effective solutions for both large-scale and small-scale deployments.
  • Data items are the lowest set of persistent objects; these objects encapsulate a single data value.
  • Data items may have a user defined type.
  • Data items may be created and deleted.
  • the internal value of a data item is constrained by range restrictions and rules.
  • a distributed managed object has a single representation at the ISP Operational Support User Interfaces, and the distribution is automatically.
  • OS/ DM Domain - Data within the Operational support domain should be managed with the ISP Data Management 2138 Mechanisms.
  • Global MIB There is a logical Global MIB which represents resources in the entire ISP.
  • MIBs - Embedded MIBs that are part of a managed component are outsider of Operational Support and Data Management. Such MIBs will be represented to the OS by a Mediation Device.
  • Operational Functions Operational personnel handle the Network Layer & Element Management for physical & logical resources.
  • Administration Functions - Administration personnel handle the Planning & Service Management.
  • Profile Domain - Service & customer profile data bases are managed by administration personnel under the domain of the Data Management system.
  • Telecommunication Management Network (TMN) compliance - TMN compliance will be achieved through a gateway to any TMN system.
  • Scaleable The physical network model is scaleable to accommodate a wide range of customer populations and service requirements.
  • Transparent Network elements is transparent to the underlying network redundancy. In case of a failure, the switchover to redundant links is automatic. 5.
  • Graceful Degradation The physical network model is able to provide available services in a gradual reduction of capacity in the face of multiple network failures.
  • the physical network model provides well-defined interfaces and access methods for monitoring the traffic on the network. Security (see above) is integrated to prevent unauthorized access to sensitive data.
  • the physical network model is (logically) partitionable to form separate administrative domains.
  • Quality of Service The physical network model provides QOS provisions such as wide range of qualities, adequate QOS for legacy applications, congestion management and user-selectable QOS.
  • the physical network model does not prevent access to a network element due to its location in the network. A service is able to access any resource on the network. 12. Regulatory awareness: The physical network model is amenable at all levels to allow for sudden changes in the regulatory atmosphere. 13. Cost Effective: The physical network model allows for cost effective implementations by not being reliant on single vendor platforms or specific standards for function.
  • the ISP Service Model establishes a framework for service development which supports: rapid service creation and deployment; • efficient service execution; • complete customization control over services for customers; total service integration for a seamless service view for customers;
  • the ISP Service Model supports all activities associated with Services, including the following aspects: provisioning; creation; deployment; ordering; updating; monitoring; execution; testing or simulation; customer support and troubleshooting; billing; trouble ticket handling; and operations support.
  • the Service Model also defines interactions with other parts of the ISP Architecture, including Data Management, Resource Management, and Operational Support. 3. Service Model Overview
  • Services are the most critical aspect in a telecommunication service provider's ability to make money.
  • the following definition of services is used throughout this service model:
  • a service 2200 is a set of capabilities combined with well-defined logic structures and business processes which, when accessed through a published interface, results in a desired and expected outcome on behalf of the user.
  • a Service 2200 includes the business processes that support the sale, operation, and maintenance of the Service.
  • the critical task in developing a Service is defining what can be automated, and clearly delineating how humans interact with the Service.
  • a service 2200 is an object in a sense of an object-oriented object as described earlier in the specification.
  • An instance of a service 2200 contains other objects, called service features 2202.
  • a service feature 2202 provides a well defined interface which abstracts the controlled interaction of one or more capabilities 2204 in the ISP Service Framework, on behalf of a service.
  • Service features 2202 use various capability 2204 objects.
  • Capabilities 2204 are standard, reusable, network-wide building blocks used to create service features 2202. The key requirement in Service Creation is for the engineers who are producing basic capability objects to insure each can be reused in many different services as needed.
  • Services 2200 are described by "service logic,” which is basically a program written in a veiy high-level programming language or described using a graphical user interface. These service logic programs identify: what service features 2202 are used; the order in which service features are invoked; the source of input service data; the destination for output service data; error values and error handling; invocation of other services 2200; interaction with other services; and the interactions with other services;
  • the service logic itself is generally not enough to execute a service 2200 in the network.
  • customer data is needed to define values for the points of flexibility defined in a service, or to customize the service for the customer's particular needs.
  • Management and Marketable Services are part of the same service model.
  • Management and Marketable Services allow capabilities to be shared. Also, Management and Marketable Services represent two viewpoints of the same network: Management Services represent and operational view of the network, and Marketable Services represent an external end-user or customer view of the network. Both kinds of services rely on network data which is held in common.
  • Every Marketable Service has a means for a customer to order the service, a billing mechanism, some operational support capabilities, and service monitoring capabilities.
  • the Management Services provide processes and supporting capabilities for the maintenance of the platform. b) Service Features 2202
  • Service features 2202 provide a well-defined interface of function calls. Service features can be reused in many different services 2200, just as capabilities 2204 are reused in many different service features 2202. Service features have specific data input requirements, which are derived from the data input requirements of the underlying capabilities. Data output behavior of a service feature is defined by the creator of the service feature, based upon the data available from the underlying capabilities. Service Features 2202 do not rely on the existence of any physical resource, rather, they call on capabilities 2204 for these functions, as shown in Figure 25.
  • Some examples of service features are: 'Time-based Routing - based on capabilities such as a calendar, date/time, and call objects, this feature allows routing to different locations based upon time.
  • Authentication - based upon capabilities such as comparison and database lookup, this function can be used to validate calling card use by prompting for a card number and/ or an access number (pin number), or to validate access to a virtual private network.
  • Automated User Interaction - based upon capabilities such as voice objects (for recording and playback of voice), call objects (for transferring and bridging calls to specialized resources), DTMF objects (for collection or outpulsing of DTMF digits), vocabulary objects (for use with speech recognition), this feature allows automated interaction with the user of a service.
  • This service feature object can be extended to include capabilities for video interaction with a user as well.
  • a capability 2204 is an object, which means that a capability has internal, private state data, and a well-defined interface for creating, deleting, and using instances of the capability. Invoking a capability 2204 is done by invoking one of its interface operations. Capabilities 2204 are built for reuse. As such, capabilities have clearly defined data requirements for input and output structures. Also, capabilities have clearly defined error handling routines.
  • Capabilities may be defined in object-oriented class hierarchies whereby a general capability may be inherited by several others.
  • network-based capability objects Some examples of network-based capability objects are:
  • Fax (for receive, send, or broadcast).
  • Some capabilities are not network-based, but are based purely on data that has been deployed into our platform. Some examples of these capabilities are:
  • calendar to determine what day of the week or month it is
  • comparison to compare strings of digits or characters
  • translation to translate data types to alternate formats
  • Static Data defined in the service template, which include default values for a given service invocation.
  • Interactive Data obtained as the service executes, which may be explicit user inputs or derived from the underlying network connections.
  • Custom Data defined in User Profiles, which is defined by customers or their representatives when the service is requested (i.e. at creation time) .
  • Services 2200 execute in Service Logic Execution Environments (SLEEs).
  • SLEE Service Logic Execution Environments
  • a SLEE is executable software which allows any of the services deployed into the ISP 2100 to be executed.
  • Service Engines 2134 Figure 21
  • Service Engines 2134 simply execute the services 2200 that are deployed to them.
  • Service templates and their supporting profiles are deployed onto database servers 2182 ( Figure 22).
  • a SLEE When a SLEE is started on a Service Engine 2134, it retrieves its configuration from the database server 2182. The configuration instructs the SLEE to execute a list of services 2200. The software for these services is part of the service templates deployed on the database servers. If the software is not already on the Service Engine 2134, the software is retrieved from the database server 2182. The software is executed, and service 200 begins to run.
  • a service 2200 will first invoke a service feature 2202 ( Figure 24) which allows the service to register itself with a resource manager 2188 or 2190. Once registered, the service can begin accepting transactions. Next, a service 2200 will invoke a service feature 2202 which waits on an initiating action. This action can be anything from an internet logon, to an 800 call, to a point of sale card validation data transaction. Once the initiating action occurs in the network, the service select function 2148 ( Figure 21) uses the Resource Manager 2150 function to find an instance of the executing service 2200 to invoke. The initiating action is delivered to the service 2200 instance, and the service logic (from the service template) determines subsequent actions by invoking additional service features 2202.
  • profile data is used to determine the behavior of service features 2202.
  • some or all of the profile data needed by a service may be cached on a service engine 2134 from the ISP 2100 database server 2182 to prevent expensive remote database lookups.
  • information may generated by service features 2202 and deposited into the Context Database. This information is uniquely identified by a network transaction identifier. In the case of a circuit-switched call, the already- defined Network Call Identifier will be used as the transaction identifier. Additional information may be generated by network equipment and deposited into the Context Database as well, also indexed by the same unique transaction identifier. The final network element involved with the transaction deposits some end-of-transaction information into the Context Database.
  • a linked list strategy is used for determining when all information has been deposited into the Context Database for a particular transaction. Once all information has arrived, an event is generated to any service which has subscribed to this kind of event, and services may then operate on the data in the Context Database. Such operations may include extracting the data from the Context Database and delivering it to billing systems or fraud analysis systems.
  • VNET caller has a service which does not allow the caller to place international calls.
  • the VNET caller dials the number of another VNET user who has a service which allows international dialing, and the called VNET user places an international call, then bridges the first caller with the international call.
  • the original user was able to place an international call through a third party, in defiance of his company's intention to prevent the user from dialing internationally. In such circumstances, it may be necessary to allow the two services to interact with each other to determine if operation of bridging an international call should be allowed.
  • the ISP service model must enable services 2200 to interact with other services. There are several ways in which a service 2200 must be able to interact with other services (see Figure 26):
  • Asynchronous Interaction 2214 where a service invokes another service, performs some other actions, then waits for the other service to complete and reply; or One Way Interaction 2216: where a service invokes another service but does not wait for a reply.
  • the terminating VNET service could have queried the originating VNET service using the synchronous service interaction capability.
  • service logic can be deployed onto both network-based platforms and onto customer premises equipment. This means that service interaction must take place between network-based services and customer-based services.
  • Services 2200 must be monitored from both the customer's viewpoint and the network viewpoint. Monitoring follows one of two forms:
  • the service 2200 can generate detailed event-by-event information for delivery to the transaction context database
  • the service can generate statistical information for delivery periodically to a statistics database, or for retrieval on demand by a statistics database.
  • Analysis services can use the Statistics Database or the Context Database to perform real time or near real time data analysis services.
  • the Context Database collects all event information regarding a network transaction. This information will constitute all information necessary for network troubleshooting, billing, or network monitoring.
  • This section describes the Data Management 2138 aspects of the Intelligent Services Platform (ISP) 2100 Target Architecture.
  • ISP Intelligent Services Platform
  • the ISP Data Management 2138 Architecture is intended to establish a model which covers the creation, maintenance, and use of data in the production environment of the ISP 2100, including all transfers of information across the ISP boundaries.
  • the Data Management 2138 Architecture covers all persistent data, any copies or flows of such data within the ISP, and all flows of data across the ISP boundaries. This model defines the roles for data access, data partitioning, data security, data integrity, data manipulation, plus database administration. It also outlines management policies when appropriate.
  • the objectives of this architecture are to: • Create a common ISP functional model for managing data;
  • the Data Management Architecture is a framework describing the various system components, how the systems interact, and the expected behaviors of each component.
  • data is stored at many locations simultaneously, but a particular piece of data and all of its replicated copies are viewed logically as a single item.
  • the user or end-point dictates what data is downloaded or stored locally.
  • Data and data access are characterized by two domains 2220 and 2222, as shown in Figure 27. Each domain can have multiples copies of data within it. Together, the domains create a single logical global database which can span international boundaries. The key aspect to the domain definitions below is that all data access is the same. There is no difference in an Order Entry feed from a Call Processing lookup or Network side data update.
  • Central domain 2220 controls and protects the integrity of the system. This is only a logical portrayal, not a physical entity. Satellite domain 2222 provides user access and update capabilities. This is only a logical portrayal, not a physical entity.
  • Data is stored at many locations simultaneously.
  • a particular piece of data and all of its replicated copies are viewed logically as a single item. Any of these copies may be partitioned into physical subsets so that not all data items are necessarily at one site. However partitioning preserves the logical view of only one, single database.
  • the architecture is that of distributed databases and distributed data access with the following functionality:
  • Figure 28 shows logical system components and high-level information flows. None of the components depicted is physical. Multiple instances of each occur in the architecture. The elements in Figure 28 are: • NETWK 2224 - external access to the ISP 2100 from the network side;
  • SYSTMS 2228 external application such as Order Entry
  • G/W 2230 a gateway to the ISP 2100 for external applications
  • dbAppl 2232 a role requiring data access or update capabilities
  • Satellite domains 2222 of Data Management 2138 encompass:
  • the Central domain for Data Management 2138 encompasses: • Monitoring (dbMon) 2240;
  • ISP applications which require database access. Examples are the ISN NIDS servers, and the DAP Transaction Servers, The applications obtain their required data from the dbClient 2234 by attaching to the desired databases, and providing any required policy instructions. These applications also provide the database access on behalf of the external systems or network element such as Order Entry or Switch requested translations.
  • Data applications support the following functionality: • Updates: allow an application to insert, update, or delete data in an ISP database.
  • Access requests allow an application to search for data, list multiple items, select items from a list or set, or iterate through members of a set.
  • Client Databases ( dbClient) 2234 The dbClients represent satellite copies of data. This is the only way for an application to access ISP data. Satellite copies of data need not match the format of data as stored on the dbServer 2236.
  • the dbClients register with master databases (dbServer) 2236 for Subscriptions or Cache Copies of data. Subscriptions are automatically maintained by dbServer 2236, but Cache Copies must be refreshed when the version is out of date.
  • a critical aspect of dbClient 2234 is to ensure that data updates by applications are serialized and synchronized with the master copies held by dbServer 2236. However, it is just as reasonable for the dbClient to accept the update and only later synchronize the changes with the dbServer (at which time exception notifications could be conveyed back to the originating application). The choice to update in lock-step, or not, is a matter of application policy not Data Management 2138.
  • a dbClient 2234 If a dbClient 2234 becomes inactive or loses communications with the dbServer; it must resynchronize with the master. In severe cases, operator intervention may be required to reload an entire database or selected subsets.
  • the dbClient 2234 offers the following interface operations: • Attach by an authorized application to a specified set of data;
  • the dbServers 2236 play a central role in the protection of data. This is where data is 'owned' and master copies maintained. At least two copies of master data are maintained for reliability. Additional master copies may be deployed to improve data performance.
  • the dbServer 2236 includes the layers of business rules which describe or enforce the relationships between data items and which constrain particular data values or formats. Every data update must pass these rules or is rejected. In this way dbServer ensures all data is managed as a single copy and all business rules are collected and applied uniformly.
  • the dbServer 2236 tracks when, and what kind of, data changes are made, and provides logs and summary statistics to the monitor (dbMon) 2240. Additionally these changes are forwarded to any active subscriptions and Cache-copies are marked out of date via expiration messages.
  • the dbServer also provides security checks and authorizations, and ensures that selected items are encrypted before storage.
  • the dbServer supports the following interface operations:
  • Data Administration (dbAdmin) 2238 involves setting data policy, managing the logical and physical aspect of the databases, and sec iring and configuring the functional components of the Data Management 2138 domain.
  • Data Management policies include security, distribution, integrity rules, performance requirements, and control of replications and partitions.
  • dbAdmin 2238 includes the physical control of data resources such as establishing data locations, allocating physical storage, allocating memory, loading data stores, optimizing access paths-, and fixing database problems.
  • dbAdmin 2238 also provides for logical control of data such as auditing, reconciling, migrating, cataloguing, and converting data.
  • the dbAdmin 2238 supports the following interface operations:
  • the dbMon 2240 represents a monitoring function which captures all data- related events and statistical measurements from the ISP boundary gateways, dbClients 2234 and dbServers 2236.
  • the dbMon 2240 mechanisms are used to create audit trails and logs.
  • the dbMon typically presents a passive interface; data is fed to it. However monitoring is a hierarchical activity and further analysis and roll-up (compilation of data collected at intervals, such as every minute, into longer time segments, such as hours or days) occurs within dbMon. Additionally dbMon will send alerts when certain thresholds or conditions are met.
  • QOS quality of Service
  • data performance data performance
  • other service level agreements All exceptions and date errors are logged and flow to the dbMon for inspection, storage, and roll-up.
  • dbMon 2240 supports the following interface operations: • Setting monitor controls, filters, and thresholds;
  • the Operations consoles (Ops) 2244 provide the workstation-interface for the personnel monitoring, administering, and otherwise managing the system.
  • the Ops consoles provide access to the operations interfaces for dbMon 2240, dbAdmin 2238, and dbServer 2236 described above.
  • the Ops consoles 2244 also support the display of dynamic status through icon based maps of the various systems, interfaces, and applications within the Data management domain 2138.
  • Each of the sites shown in Figure 29 is typically linked with one or more of the other sites by wide area network (WAN) links.
  • WAN wide area network
  • the exact network configuration and sizing is left to a detailed engineering design task. It is not common for a database copy to be distributed to the Order Entry (OE) sites 2251, however in this architecture, entry sites are considered equivalent to satellite sites and will contain the dbClient functionality.
  • OE Order Entry
  • Satellite sites 2252 each contain the dbClient 2234 too. These sites typically operate local area networks (LANs)
  • LANs local area networks
  • the dbClients act as local repositories for network or system applications such as the ISN operator consoles, ARUs, or NCS switch requested translations.
  • the Central sites 2254 provide redundant data storage and data access paths to the dbClients 2234. Central sites 2254 also provide roll-up monitoring (dbMon) functions although dbMon components 2240 could be deployed at satellite sites 2252 for increased performance.
  • dbMon roll-up monitoring
  • the administrative functions are located at any desired operations or administration site 2254 but not necessarily in the same location as the dbMon. Administrative functions require the dbAdmin 2238, plus an operations console 2244 for command and control. Remote operations sites are able to access the dbAdmin nodes 2238 from wide-area or local-area connections. Each of the sites is backed-up by duplicate functional components at other sites and are connected by diverse, redundant links.
  • Figure 30 depicts a set of technologies which are able to provide a very-high performance environment. Specific application requirements will determine the minimum level of acceptable performance. Three general environments are shown.
  • a multi-protocol routed network 2260 connects external and remote elements with the central data sites. Administrative terminals, and smaller mid-range computers are shown, plus a high- availability application platform such as Order Entry.
  • Security ISP data is a protected corporate resource. Data access is restricted and authenticated. Data related activity is tracked and audited. Data encryption is required for all stored passwords, PINS (personal identification numbers), private personnel records, and selected financial, business, and customer information. Secured data must not be transmitted in clear- text forms. 9. Meta-Data
  • Meta-data is a form of data which comprises the rules for data driven logic. Meta-data is used to describe and manage (i.e. manipulate) operational forms of data. Under this architecture, as much control as possible is intended to be driven by meta-data. Meta-data (or data-driven logic) generally provides the most flexible run-time options. Meta-data is typically under the control of the system administrators.
  • This section describes the Resource Management 2150 Model as it relates to the ISP 2100 Architecture.
  • the Resource Management Model covers the cycle of resource allocation and de-allocation in terms of the relationships between a process that needs a resource, and the resource itself. This cycle starts with Resource Registration and De-registration and continues to Resource Requisition, Resource Acquisition, Resource Interaction and Resource Release.
  • the Resource Management 2150 Model is meant to define common architectural guidelines for the ISP development community in general, and for the ISP Architecture in particular.
  • the objectives of the Resource Management Model are designed to allow for network- wide resource management and to optimize resource utilization, to enable resource sharing across the network:
  • Resource Management 2150 Model governs the relationships and interactions between the resources and the processes that utilize them.
  • the Resource Management 2150 Model governs the relationships and interactions between the resources and the processes that utilize them.
  • Resource A basic unit of work that provides a specific and well- defined capability when invoked by an external process. Resources can be classified as logical, like a service engine and a speech recognition algorithm, or physical, like CPU, Memory and Switch ports. A resource may be Shared like an ATM link bandwidth or Disk space, or Dedicated like a VRU or a Switch port.
  • Resource Pool A set of registered resource members that share common capabilities.
  • Service A logical description of all activities and the interaction flow between the user of the network resources and the resources themselves.
  • Policy A set of rules that governs the actions taken on resource allocation and de-allocation, resource pool size thresholds and resource utilization thresholds.
  • the Resource Management Model is a mechanism which governs and allows a set of functions to request, acquire and release resources to/from a resource pool through well-defined procedures and policies.
  • the resource allocation and de-allocation process involves three phases:
  • Resource Requisition is the phase in which a process requests a resource from the Resource Manager 2150.
  • Resource Acquisition If the requested resource is available and the requesting process has the privilege to request it, the Resource
  • Resource Manager 2150 will grant the resource and the process can utilize it. Otherwise, the process has the choice to either abandon the resource allocation process and may try again later, or it may request that the Resource Manager 2150 grant it the resource whenever it becomes available or within a specified period.
  • Resource Release The allocated resource should be put back into the resource pool once the process no longer needs it. Based on the resource type, the process either releases the resource and the resource informs the Resource Manager of its new status, or the process itself informs the Resource Manager that the resource is available. In either case, the Resource Manager will restore the resource to the resource pool.
  • the Resource Management Model allows for the creation of resource pools and the specification of the policies governing them.
  • Management Model allows resources to register and de-register as legitimate members of resource pools.
  • Resource Management Model policies enforce load balancing, failover and least cost algorithms and prevent services from monopolizing resources.
  • the Resource Management Model tracks resource utilization and automatically takes corrective action when resource pools are not sufficient to meet demand. Any service should be able to access and utilize any available resource across the network as long as it has the privilege to do so.
  • Each resource is represented by a Managed Object (MO).
  • MO Managed Object
  • Each MO is defined in terms of the following aspects: Attributes: The attributes of a MO represent its properties and are used to describe its characteristics and current states. Each attribute is a associated with a value, for example the value CURRENT_STATE attribute of a MO could be IDLE.
  • Each MO has a set of operations that are allowed to be performed on it. These operations are: • Create: to create a new MO
  • Each MO can report or notify its status to the management entity. This could be viewed as triggers or traps.
  • Behavior The behavior of an MO is represented by how it reacts to a specific operation and the constraints imposed on this reaction. The MO may react to either external stimuli or internal stimuli. An external stimuli is represented by a message that carries an operation. The internal stimuli, however, is an internal event that occurred to the MO like the expiration of a timer. A constraint on how the MO should react to the expired timer may be imposed by specifying how many times the timers has to expire before the MO can report it.
  • the Resource Management Model is hierarchical with at least two levels of management: Local Resource Manager (LRM) 2190 and Global Resource Manager (GRM) 2188. Each RM, Local and Global, has its own domain and functionality. 2.
  • LRM Local Resource Manager
  • the domain of the LRM is restricted to a specific resource pool (RP) that belongs to a specific locale of the network. Multiple LRMs could exist in a single locale, each LRM may be responsible for managing a specific resource pool.
  • RP resource pool
  • the main functionality of the LRM is to facilitate the resource allocation and de-allocation process between a process and a resource according the Resource Management Model guidelines.
  • the domain of the GRM 2188 covers all registered resources in all resource pools across the network.
  • Function The main function of the GRM is to help the LRM 2190 locate a resource that is not available in the LRM domain.
  • Figure 31 illustrates the domains of the GRM 2188 and LRM 2190 within network 2270.
  • the Resource Management Model is based on the concept of Dynamic Resource Allocation as opposed to Static Configuration.
  • the Dynamic Resource Allocation concept implies that there is no pre-defined static relationship between resources and the processes utilizing them.
  • the allocation and de-allocation process is based on supply and demand.
  • the Resource Managers 2150 will be aware of the existence of the resources and the processes needing resources can acquire them through the Resource Managers 2150.
  • Static Configuration implies a pre- defined relationship between each resource and the process that needs it. In such a case, there is no need for a management entity to manage these resources. The process dealing with the resources can achieve that directly.
  • Dynamic Resource Allocation and Static Configuration represent the two extremes of the resource management paradigms. Paradigms that fall between these extremes may exist.
  • the Resource Management Model describes the behavior of the LRM 2190 and GRM 2188 and the logical relationships and interactions between them. It also describes the rules and policies that govern the resource allocation and de-allocation process between the LRM /GRM and the processes needing the resources.
  • a process 2271 requests the resource 2173 from the resource manager 2150.
  • the resource manager 2150 allocates the resource 2173.
  • the resource manager 2150 grants the allocated resource 2173 to the requesting process 2271.
  • the process 2271 interacts with the resource 2273.
  • the Resource Management Model is represented by a set of logical elements that interact and co-operate with each other in order to achieve the objectives mentioned earlier. These elements are shown in Figure 33 and include: Resource Pool (RP) 2272, LRM 2190, GRM 2188 and Resource Management Information Base (RMIB) 2274.
  • RP Resource Pool
  • LRM 2190 LRM 2190
  • GRM 2188 Resource Management Information Base
  • Resource Pool (RP) 2272 All resources that are of the same type, share common attributes or provide the same capabilities, and are located in the same network locale may be logically grouped together to form a Resource Pool (RP) 2272. Each RP will have its own LRM 2190.
  • the LRM 2190 is the element that is responsible for the management of a specific RP 2272. All processes that need to utilize a resource from a RP that is managed by a LRM should gain access to the resource through that LRM and by using the simple Resource Management Model described above.
  • the GRM 2188 is the entity that has a global view of the resource pools across the network.
  • the GRM gains this global view through the LRMs 2190.
  • All LRMs update the GRM with RP 2272 status and statistics. There are cases where a certain LRM can not allocate a resource because all local resources are busy or because the requested resource belongs to another locale. In such cases, the LRM can consult with the GRM to locate the requested resource across the network.
  • the RMIB 2274 is the database that contains all the information about all MOs across the network. MO information includes object definition, status, operation, etc.
  • the RMIB is part of the ISP Data Management Model. All LRMs and the GRM can access the RMIB and can have their own view and access privileges of the MO's information through the ISP Data Management Model.
  • Resource Management Model elements To perform their tasks, the Resource Management Model elements must interact and co-operate within the rules, policies and guidelines of the Resource Management Model. The following sections explain how these entities interact with each other.
  • each rectangle represents one entity
  • the verb between the " ⁇ >” implies the relationship between two entities
  • the square brackets "[]” imply that the direction of the relationship goes from the bracketed number to the non bracketed one.
  • the numbers imply is the relationship is 1-to- l
  • One LRM 2190 manages one RP 2272. 2. Many LRMs 2190 access the RMIB 2274.
  • Resource registration and de-registration applies only on the set of resources that have to be dynamically managed. There are some cases where resources are statically assigned.
  • LRMs 2190 operate on resource pools 2272 where each resource pool contains a set of resource members. In order for the LRM to manage a certain resource, the resource has to inform the LRM of its existence and status. Also, the GRM 2188 needs to be aware of the availability of the resources across the network in order to be able to locate a certain resource. The following registration and de-registration guidelines should be applied on all resources that are to be dynamically managed: • All resources must register to their LRM 2190 as members of a specific resource pool 2272. All resources must de-register from their LRM 2190 if, for any reason, they need to shutdown or be taken out of service. All resources must report their availability status to their LRM 2190. All LRMs must update the GRM 2188 with the latest resource availability based on the registered and de-registered resources.
  • Every RP 2272 will be managed by an LRM -2190.
  • Each process that needs a specific resource type will be assigned an LRM that will facilitate the resource access.
  • the process needs a resource it must request it through its assigned LRM.
  • the LRM receives a request for a resource, two cases may occur:
  • Resource is available: In this case, the LRM allocates a resource member of the pool and passes a resource handle to the process. The process interacts with the resource until it is done with it. Based on the resource type, once the process is done with the resource, it either informs the resource that it is done with it, and the resource itself informs its LRM that it is available, or it releases the resource and informs the LRM that it is no longer using the resource.
  • the LRM 2190 consults with the GRM 2188 for an external resource pool that contains the requested resource. If no external resource is available, the LRM informs the requesting process that no resources are available. In this case, the requesting process may: • give up and try again, ' request that the LRM allocate the resource whenever it becomes available, or
  • the GRM 2188 passes location and access information to the LRM 2190. Then the LRM either:
  • the RMIB 2274 contains all information and status of all managed resources across the network.
  • Each LRM 2190 will have a view of the RMIB 274 that maps to the RP 2272 it manages.
  • the GRM 2188 has a total view of all resources across the network. This view consists of all LRMs views. The GRM's total view enables it to locate resources across the network.
  • each LRM 2190 must update the RMIB with the latest resource status. This includes adding resources, removing resources and updating resource states.
  • Both the LRM 2190 and GRM 2188 can gain their access and view of the RMIB 2274 through the ISP Data Management entity.
  • the actual management of the RMIB data belongs to the ISP Data Management entity.
  • the LRM and GRM are only responsible for updating the RMIB.
  • the Operational Support Model defines a framework for implementation of management support for the ISP 2100.
  • the OSM described here provides for the distributed management of ISP physical network elements and the services that run on them.
  • the management framework described herein could also be extended to the management of logical (software) resources.
  • the architecture presented here will help map utilization and faults on physical resources to their resulting impact on services.
  • the management services occur within four layers • Planning,
  • Managed Object A resource that is monitored, and controlled by one or more management systems Managed objects are located within managed systems and may be embedded in other managed objects.
  • a managed object may be a logical or physical resource, and a resource may be represented by more than one managed object (more than one view of the object).
  • Managed System One or more managed objects.
  • Management Sub-Domain A Management domain that is wholly located within a parent management domain.
  • Management System An application process within a managed domain which effects monitoring and control functions on managed objects and /or management sub-domains.
  • Management Information Base A MIB contains information about managed objects.
  • Management Domain A collection of one or more management systems, and zero or more managed systems and management sub-domains.
  • the Telecommunications network consist of many types of analog and digital telecommunications equipment and associated support equipment, such as transmission systems, switching systems, multiplexes, signaling terminals, front-end processors, mainframes, cluster controllers, file servers, LANs, WANs, Routers, Bridges, Gateways, Ethernet Switches,
  • NE network element
  • the management environment may be partition in a number a ways such as functionally (fault, service....), geographical, organizational structure, etc.
  • Figure 34 shows the four management layers 2300, 2302, 2304 and 2306 of the Operational Support Model 2308 over the network elements 2310.
  • the Operational Support Model 2308 supports the day to day management of the ISP 2100.
  • the model is organized along three dimensions. Those dimensions are the layers 2300-2306, the functional area within those layers, and the activities that provide the management services. Managed objects (a resource) are monitored, controlled, and altered by the management system.
  • the ISP Planning Layer 2300 is the repository for data collected about the ISP 2100, and the place where that data is to provide additional value.
  • Configuration Management 2312 Setting of policy, and goals.
  • • Fault Management 2314 Predicting of mean time to failure.
  • Resource Measurement 2316 Predicting future resource needs (trending, capacity, service agreement compliance, maintenance agreement, work force) .
  • the Service Ordering, Deployment, Provisioning, Quality of Service agreements, and Quality of service monitoring are in the ISP Service Management layer 2302.
  • Customers will have a restricted view of the SM layer 2302 to monitor and control their services.
  • the SM layer provides a manager(s) that interacts with the agents in the NLMs.
  • the SM layer also provides an agent(s) that interacts with the manager(s) in the Planning layer 2300. Managers within the SM layer may also interact with other managers in the SM layer. In that case there are manager-agent relationships at the peer level.
  • Configuration Management 2320 Service Definition, Service Activation, Customer Definition, Customer Activation, Service Characteristics, Customer Characteristics, hardware provisioning, software provisioning, provisioning of other data or other resources.
  • Resource Measurement 2324 Predict the violation of a service agreement and flag potential resource shortages. Predict the needs of current and future (trending) services.
  • Accounting 2326 Process and forward Accounting information.
  • the ISP Network Layer Management (NLM) Layer 2304 has the responsibility for the management of all the network elements, as presented by the Element Management, both individually and as a set. It is not concerned with how a particular element provides services internally.
  • the NLM layer 2304 provides a manager(s) that interacts with the agents in the EMs 2306.
  • the NLM layer also provides an agent(s) that interacts with the manager(s) in the SM layer 2302. Managers within the NLM layer 2304 may also interact other managers in the NLM layer. In that case there are manager agent relationships at the peer level.
  • Configuration Management 2328 provides functions to define the characteristics of the local and remote resources and services from a network wide perspective.
  • Fault Management 2330 provides functions to detect, report, isolate, and correct faults that occur across multiple NEs.
  • Resource Measurement 2332 provides for the network wide measurement, analysis, and reporting of resource utilization from a capacity perspective.
  • Accounting 2334 consolidates Accounting information from multiple sources.
  • the Element Management Layer 2306 is responsible for the NEs 2310 on an individual basis and supports an abstraction of the functions provided by the NEs
  • the EM layer 2306 provides a manager(s) that interact with the agents in the NEs.
  • the EM layer also provides an agent(s) that interact with the manager(s) in the NLM layer 2304. Managers within the EM layer 2306 may also interact other managers in the EM layer. In that case there are manager agent relationships at the peer level.
  • Configuration Management 2336 provides functions to define the characteristics of the local and remote resources and services.
  • Fault Management 2338 provides functions to detect, report, isolate, and correct faults.
  • Resource Measurement 2340 provides for the measurement, analysis, and reporting of resource utilization from a capacity perspective.
  • Accounting 2342 provides for the measurement and reporting of resource utilization from an accounting perspective.
  • NEs provide agents to perform operations on the behalf of the Element Management Layer 2306.
  • Telecommunications network management is a distributed information application process. It involves the interchange of management information between a distributed set of management application processes for the purpose of monitoring and controlling the network resources (NE) 2310.
  • the management processes take on the role of either manager 2350 or agent 2352.
  • the manager 2350 role is to direct management operation requests to the agent 2352, receive the results of an operation, receive event notification, and process the received information.
  • the role of the agent 2352 is to respond to the manager's request by performing the appropriate operation on the managed objects 2354, and directing any responses or notifications to the manager.
  • One manager 2350 may interact with many agents 2352, and the agent may interact with more than one manager. Managers may be cascaded in that a higher level manager acts on managed objects through a lower level manager. In that case the lower level manager acts in both manager and agent roles. 3.
  • TMN which offers a good model, uses the Common Management Information Services (CMIS) and Common Management Information Protocol (CMIP) as defined in Recommendations X.710, and X.71 1.
  • CMIS Common Management Information Services
  • CMIP Common Management Information Protocol
  • This provides a peer-to-peer communications protocol based on ITU's Application Common Service Element (X.217 service description & X.227 protocol description) and Remote Operation Service Element (X.219 service description & X.229 protocol description).
  • FTAM is also supported as an upper layer protocol for file transfers. The use of these upper layer protocols is described in Recommendation X.812.
  • the transport protocols are described in Recommendation X.81 1.
  • Recommendation X.81 1 also describes the interworking between different lower layer protocols. This set of protocols is referred to as Q3.
  • ASN. l (X.209) with BER could be used to develop this common understanding for all PDU exchanged between the management processes (manager/ agent) .
  • the following identifies the minimum services required of the service layer and is modeled after the TMN CMIS services.
  • CANCEL-GET To cancel a previously issued GET.
  • ACTION To request an object to perform a certain action.
  • CREATE To create an object.
  • DELETE To remove an object.
  • EVENT-REPORT Allows the network resource to announce an event.
  • the Physical Model Figure 36 shows the ISP 2100 physical model.
  • Mediation Device 2360 provides conversion from one information model to the ISP information model.
  • Gateways 2362 are used to connect to management systems outside of the ISP. These gateways will provide the necessary functions for operation with both ISP compliant systems, and non-compliant systems.
  • the gateways may contain mediation devices 2360.
  • Figure 36 identifies nine interface points. The protocols associated with those interface points are:
  • the protocol for communications with the workstation and the ISP upper layer for all other operational support communications The lower layer is TCP/IP over Ethernet.
  • the upper layer is the protocol for communications with workstation 2364, and the lower layer is TCP/IP over Ethernet.
  • the upper layer is the ISP upper layer, and the lower layer is TCP/IP over Ethernet. 5.
  • the proprietary protocols are the of legacy systems that are not compatible with the supported interfaces. Equipment that provides a Simple Network Management Protocol (SNMP) interface will be supported with Mediation Devices.
  • SNMP Simple Network Management Protocol
  • Gateways by their nature will support ISP compliant and non- compliant interfaces. Gateways to enterprise internal systems could include such as the Order Entry system, or an enterprise wide TMN system.
  • Figure 37 shows operational support realization.
  • FIG. 37 represents an ISP realization of this conceptual model. In this implementation of that model all the ISP Network Elements would be represented to the Operational Support System by a Management Information Base (MIB) 2370 and the agent process that acts upon the objects in the MIB.
  • MIB Management Information Base
  • the Network Layers Manager 2372 gives field support a picture of the ISP as a whole. The process of detecting, isolating, and correcting problems begins from there. From that layer, problems could be isolated to a single Network Element. Individual Network Elements are accessible from the Network Element Managers 2374 and would allow a more detailed level of monitoring, control, configuration, and testing. The centralized view of the ISP is missing from today's ISP, but many recognize its importance.
  • the Network Layers Manager 2370 provides an ISP-wide view, and interacts with the Network Element Managers 2374 to configure Network Elements in a consistent manner. This will help insure that the ISP configuration is consistent across all platforms. The ability to change a piece of information in one place and have it automatically distributed ISP- wide is a powerful tool that has not been possible with the current ISP management framework.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)
  • Meter Arrangements (AREA)

Abstract

La présente invention a trait à un procédé et à un système destinés à acheminer des appels téléphoniques, des données et d'autres informations multimédia à travers un réseau hybride qui peut inclure le transfert d'informations par Internet. Les informations de profil sont utilisées par le système pendant toute la vie du support, notamment pour l'acheminement, la facturation, la surveillance, la transmission des données ainsi que pour d'autres fonctions de commande du support. Le système peut comprendre l'acheminement à priorité et peut également faciliter les sessions de rappels et présenter un affichage pour l'abonné demandeur via une page web qui renferme des informations d'état en rapport avec la session de rappel. Les appels et les rappels peuvent également être acheminés à travers le réseau hybride. En employant ce système, les utilisateurs peuvent gérer beaucoup plus d'aspects relatifs au réseau qu'il n'était possible auparavant, et peuvent aussi contrôler les activités du réseau depuis un site central.
PCT/US1998/001868 1997-02-03 1998-02-03 Architecture d'un systeme de communication WO1998034391A2 (fr)

Priority Applications (9)

Application Number Priority Date Filing Date Title
JP53313598A JP2001520820A (ja) 1997-02-03 1998-02-03 通信システム構造
NZ336939A NZ336939A (en) 1997-02-03 1998-02-03 Multimedia communication via telephony (circuit switched) and packet switched (internet) networks
EP19980904802 EP1000500A4 (fr) 1997-02-03 1998-02-03 Architecture d'un systeme de communication
IL13110298A IL131102A0 (en) 1997-02-03 1998-02-03 A communication system architecture
AU62592/98A AU6259298A (en) 1997-02-03 1998-02-03 A communication system architecture
BR9809561-7A BR9809561A (pt) 1997-02-03 1998-02-03 Arquitetura de sistema de comunicações
APAP/P/1999/001611A AP9901611A0 (en) 1997-02-03 1998-02-03 A communication system architecture.
CA002289455A CA2289455A1 (fr) 1997-02-03 1998-02-03 Architecture d'un systeme de communication
NO993733A NO993733L (no) 1998-02-03 1999-08-02 Kommunikasjonssystem tilpasset verdensomspennende nett av typen Internett

Applications Claiming Priority (22)

Application Number Priority Date Filing Date Title
US79411497A 1997-02-03 1997-02-03
US79468997A 1997-02-03 1997-02-03
US79455597A 1997-02-03 1997-02-03
US08/794,114 1997-02-03
US08/794,689 1997-02-03
US08/794,555 1997-02-03
US79835097A 1997-02-10 1997-02-10
US80713097A 1997-02-10 1997-02-10
US79744597A 1997-02-10 1997-02-10
US79820897A 1997-02-10 1997-02-10
US80024397A 1997-02-10 1997-02-10
US79736097A 1997-02-10 1997-02-10
US79796497A 1997-02-10 1997-02-10
US08/807,130 1997-02-10
US08/798,208 1997-02-10
US08/800,243 1997-02-10
US08/795,270 1997-02-10
US08/795,270 US6731625B1 (en) 1997-02-10 1997-02-10 System, method and article of manufacture for a call back architecture in a hybrid network with support for internet telephony
US08/798,350 1997-02-10
US08/797,445 1997-02-10
US08/797,964 1997-02-10
US08/797,360 1997-02-10

Publications (4)

Publication Number Publication Date
WO1998034391A2 true WO1998034391A2 (fr) 1998-08-06
WO1998034391A3 WO1998034391A3 (fr) 1998-12-23
WO1998034391A9 WO1998034391A9 (fr) 1999-09-10
WO1998034391A8 WO1998034391A8 (fr) 2000-01-20

Family

ID=27582812

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1998/001868 WO1998034391A2 (fr) 1997-02-03 1998-02-03 Architecture d'un systeme de communication

Country Status (9)

Country Link
EP (1) EP1000500A4 (fr)
KR (1) KR20000071228A (fr)
CN (1) CN1262836A (fr)
AP (1) AP9901611A0 (fr)
CA (1) CA2289455A1 (fr)
IL (1) IL131102A0 (fr)
NZ (1) NZ336939A (fr)
TR (1) TR199901842T2 (fr)
WO (1) WO1998034391A2 (fr)

Cited By (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0999687A2 (fr) * 1998-11-03 2000-05-10 Nortel Networks Corporation Intégration de systèmes de communication à protocole de signalisation de stimuli et systèmes de communication à protocole de message
EP1001597A2 (fr) * 1998-11-10 2000-05-17 International Business Machines Corporation Méthode et système pour réduire les frais téléphoniques pour des appels vers des fournisseurs de services
JP2000175278A (ja) * 1998-12-03 2000-06-23 Roehm Properties Bv 通信システム
WO2000074337A2 (fr) * 1999-06-02 2000-12-07 Ac Properties B.V. Systeme, procede et article manufacture destines a un serveur de base de donnees de regles dans une architecture de systeme de communication hybride
ES2151864A1 (es) * 1999-05-18 2001-01-01 Amper Sa Sistema de distribucion, almacenamiento y reprudccion de musica digit alizada
WO2001053961A1 (fr) * 2000-01-19 2001-07-26 Gentor.Com Inc. Serveur de liaison de canal d'emissions et procede correspondant
WO2002028077A2 (fr) * 2000-09-25 2002-04-04 National Notification Center, Llc Systeme de traitement d'appel au moyen de reponse vocale interactive
GB2368930A (en) * 2000-10-17 2002-05-15 Hewlett Packard Co Establishment of a deferred network communication session
US6442169B1 (en) 1998-11-20 2002-08-27 Level 3 Communications, Inc. System and method for bypassing data from egress facilities
US6614781B1 (en) 1998-11-20 2003-09-02 Level 3 Communications, Inc. Voice over data telecommunications network architecture
WO2003085537A1 (fr) * 2002-04-04 2003-10-16 Seung-Kee Mo Terminal commandant l'utilisation d'un ordinateur
WO2003088591A1 (fr) * 2002-04-17 2003-10-23 Veselov Andrei Anatol Evich Systeme de communication pour entreprise
US6731625B1 (en) 1997-02-10 2004-05-04 Mci Communications Corporation System, method and article of manufacture for a call back architecture in a hybrid network with support for internet telephony
DE102007047632A1 (de) * 2007-10-04 2009-04-09 T-Mobile International Ag Interconnection virtueller Welten mit mobilen Nachrichtendiensten
US7542761B2 (en) * 2004-10-06 2009-06-02 At&T Mobility Ii Llc Voice quality on a communication link based on customer feedback
US7715371B2 (en) 1995-12-11 2010-05-11 Comcast Ip Holdings I, Llc Method and apparatus for accessing communication data relevant to a target entity identified by a number string
US7987492B2 (en) 2000-03-09 2011-07-26 Gad Liwerant Sharing a streaming video
US8213587B2 (en) 2007-09-28 2012-07-03 Ringcentral, Inc. Inbound call identification and management
US8275110B2 (en) 2007-09-28 2012-09-25 Ringcentral, Inc. Active call filtering, screening and dispatching
WO2014062258A1 (fr) * 2012-10-19 2014-04-24 Innovation Software, Llc Enregistreur de clics manuels
US8792118B2 (en) 2007-09-26 2014-07-29 Ringcentral Inc. User interfaces and methods to provision electronic facsimiles
US9083719B2 (en) 2000-05-04 2015-07-14 Focal Ip, Llc Controller for the intelligent interconnection of two communication networks, and method of use for same
US9084186B2 (en) 2008-11-24 2015-07-14 Ringcentral, Inc. Call management for location-aware mobile devices
US9191505B2 (en) 2009-05-28 2015-11-17 Comcast Cable Communications, Llc Stateful home phone service
US9258673B2 (en) 2007-09-28 2016-02-09 RingControl, Inc. Centralized status server for call management of location-aware mobile devices
US9602369B2 (en) 2010-11-03 2017-03-21 Google Inc. Data delivery
US9806988B2 (en) 1996-10-31 2017-10-31 Patentmarks Communications, Llc Multi-protocol telecommunications routing optimization
RU2647637C1 (ru) * 2017-06-20 2018-03-16 Федеральное государственное бюджетное учреждение "16 Центральный научно-исследовательский испытательный ордена Красной Звезды институт имени маршала войск связи А.И. Белова" Министерства обороны Российской Федерации Автоматизированное рабочее место оператора аппаратуры передачи данных
EP3280099A4 (fr) * 2015-03-31 2018-12-19 Nec Corporation Système de réseau, procédé de commande de réseau, et appareil de commande
US10225584B2 (en) 1999-08-03 2019-03-05 Videoshare Llc Systems and methods for sharing video with advertisements over a network
CN111949422A (zh) * 2020-08-26 2020-11-17 南京云灿信息科技有限公司 基于mq和异步io的数据多级缓存与高速传输记录方法
US10869196B2 (en) 2015-08-12 2020-12-15 Tencent Technology (Shenzhen) Company Limited Internet access authentication method and client, and computer storage medium
US10885543B1 (en) 2006-12-29 2021-01-05 The Nielsen Company (Us), Llc Systems and methods to pre-scale media content to facilitate audience measurement
US11877028B2 (en) 2018-12-04 2024-01-16 The Nielsen Company (Us), Llc Methods and apparatus to identify media presentations by analyzing network traffic

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6137869A (en) 1997-09-16 2000-10-24 Bell Atlantic Network Services, Inc. Network session management
US7272604B1 (en) 1999-09-03 2007-09-18 Atle Hedloy Method, system and computer readable medium for addressing handling from an operating system
US6745011B1 (en) * 2000-09-01 2004-06-01 Telephia, Inc. System and method for measuring wireless device and network usage and performance metrics
US6958992B2 (en) 2001-03-16 2005-10-25 Mitel Corporation Registering an IP phone with an IP phone switch
FI20021314A0 (fi) 2002-07-03 2002-07-03 Nokia Corp Tiedonsiirtomenetelmä ja järjestely
AU2003211358A1 (en) * 2003-02-27 2004-09-17 Yukio Kubo Speech communication system, server used for the same, and reception relay device
US7577659B2 (en) * 2003-10-24 2009-08-18 Microsoft Corporation Interoperable credential gathering and access modularity
KR100839650B1 (ko) * 2004-06-09 2008-06-20 가부시키가이샤 엔티티 도코모 무선주파수 할당장치, 무선통신시스템 및 무선주파수할당방법
US7380711B2 (en) * 2004-07-23 2008-06-03 Checkpoint Systems, Inc. Self-check system and method for protecting digital media
US7600044B2 (en) 2006-06-13 2009-10-06 Inter-Tel, Inc. System and method for networked endpoint registration
US8850012B2 (en) * 2006-08-21 2014-09-30 Nokia Corporation Mechanism for charging and session handling supporting forking
AU2008255067A1 (en) 2007-05-15 2008-11-27 Social Project, Inc. System and method for creating a social-networking online community
KR101143040B1 (ko) * 2009-08-21 2012-05-11 삼성에스디에스 주식회사 Ｔｃｐ/ｉｐ 기반 ｘ.25 프로토콜 회선의 이중화 시스템 및 방법
US8817777B2 (en) * 2011-08-10 2014-08-26 Microsoft Corporation Hybrid unified communications deployment between cloud and on-premise
TW201601407A (zh) 2014-06-24 2016-01-01 萬國商業機器公司 電源分配單元與用於其之警示方法
CN105225388A (zh) * 2014-06-28 2016-01-06 陈娇 一种视网膜识别报警系统
US10462073B2 (en) * 2015-01-06 2019-10-29 The Boeing Company Aircraft control domain communication framework
CN105975852A (zh) * 2015-12-31 2016-09-28 武汉安天信息技术有限责任公司 一种基于标签传播的样本关联性检测方法及系统
CN107147475B (zh) * 2017-06-28 2020-04-14 京信通信系统（中国）有限公司 一种调制编码方式的调整方法及基站
WO2019237364A1 (fr) * 2018-06-15 2019-12-19 Oppo广东移动通信有限公司 Procédé de transfert séquentiel de données, dispositif de réseau et dispositif terminal
US11281830B2 (en) * 2019-03-11 2022-03-22 Intel Corporation Method and apparatus for performing profile guided optimization for first in first out sizing
CN110457142B (zh) * 2019-07-10 2023-05-09 创新先进技术有限公司 业务处理方法、系统、机房、架构及电子设备
CN111654547B (zh) * 2020-06-04 2022-07-05 中国建设银行股份有限公司 数据传输方法、装置、设备及存储介质

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
BOHN R ET AL: "MITIGATING THE COMING INTERNET CRUCH: MULTIPLE SERVICE LEVELS VIA PRECEDENCE" JOURNAL OF HIGH SPEED NETWORK, vol. 3, no. 4, 1994, pages 335-349, XP002055271 *
DIEHL S: "DATA'S NEW VOICE" BYTE, vol. 21, no. 9, September 1996, page 129/130, 132, 134/135 XP000641466 *
LI C -S ET AL: ""TIME-DRIVEN PRIORITY" FLOW CONTROL FOR REAL-TIME HETEROGENEOUS INTERNETWORKING" PROCEEDINGS OF IEEE INFOCOM 1996. CONFERENCE ON COMPUTER COMMUNICATIONS, FIFTEENTH ANNUAL JOINT CONFERENCE OF THE IEEE COMPUTER AND COMMUNICATIONS SOCIETIES. NETWORKING THE NEXT GENERATION SAN FRANCISCO, MAR. 24 - 28, 1996, vol. VOL. 1, no. CONF. 15, 24 March 1996, INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS, pages 189-197, XP000622310 *
MATTA I ET AL: "PROCEEDINGS OF THE CONFERENCE ON COMPUTER COMMUNICATIONS (INFOCOM), TORONTO, JUNE 12 - 16, 1994" PROCEEDINGS OF THE CONFERENCE ON COMPUTER COMMUNICATIONS (INFOCOM), TORONTO, JUNE 12 - 16, 1994, vol. VOL. 3, 12 June 1994, INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS, pages 492-499, XP000496559 *
See also references of EP1000500A2 *

Cited By (59)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8938062B2 (en) 1995-12-11 2015-01-20 Comcast Ip Holdings I, Llc Method for accessing service resource items that are for use in a telecommunications system
US7903641B2 (en) 1995-12-11 2011-03-08 Comcast Ip Holdings, I, Llc Method and apparatus for accessing communication data relevant to a target entity identified by a number string
US7804816B2 (en) 1995-12-11 2010-09-28 Comcast Ip Holdings I, Llc Method and apparatus for accessing communication data relevant to a target entity identified by a number string
US7715371B2 (en) 1995-12-11 2010-05-11 Comcast Ip Holdings I, Llc Method and apparatus for accessing communication data relevant to a target entity identified by a number string
US8170008B2 (en) 1995-12-11 2012-05-01 Comcast Ip Holdings I, Llc Method and apparatus for accessing communication data relevant to a target entity identified by a number string
US8189565B2 (en) 1995-12-11 2012-05-29 Comcast Ip Holdings I, Llc Method and apparatus for accessing communication data relevant to a target entity identified by a number string
US8223752B2 (en) 1995-12-11 2012-07-17 Comcast Ip Holdings I, Llc Method for accessing service resource items that are for use in a telecommunications system
US8204046B2 (en) 1995-12-11 2012-06-19 Comcast Ip Holdings I, Llc Method and apparatus for accessing service resource items that are for use in a telecommunications system
US9806988B2 (en) 1996-10-31 2017-10-31 Patentmarks Communications, Llc Multi-protocol telecommunications routing optimization
US6731625B1 (en) 1997-02-10 2004-05-04 Mci Communications Corporation System, method and article of manufacture for a call back architecture in a hybrid network with support for internet telephony
EP0999687A2 (fr) * 1998-11-03 2000-05-10 Nortel Networks Corporation Intégration de systèmes de communication à protocole de signalisation de stimuli et systèmes de communication à protocole de message
EP0999687A3 (fr) * 1998-11-03 2003-09-24 Nortel Networks Limited Intégration de systèmes de communication à protocole de signalisation de stimuli et systèmes de communication à protocole de message
EP1001597A3 (fr) * 1998-11-10 2003-09-03 International Business Machines Corporation Méthode et système pour réduire les frais téléphoniques pour des appels vers des fournisseurs de services
EP1001597A2 (fr) * 1998-11-10 2000-05-17 International Business Machines Corporation Méthode et système pour réduire les frais téléphoniques pour des appels vers des fournisseurs de services
US6614781B1 (en) 1998-11-20 2003-09-02 Level 3 Communications, Inc. Voice over data telecommunications network architecture
US6442169B1 (en) 1998-11-20 2002-08-27 Level 3 Communications, Inc. System and method for bypassing data from egress facilities
EP2317710A3 (fr) * 1998-11-20 2012-04-11 Level 3 Communications, LLC Architecture de réseau de télécommunication voix-données
JP2000175278A (ja) * 1998-12-03 2000-06-23 Roehm Properties Bv 通信システム
ES2151864A1 (es) * 1999-05-18 2001-01-01 Amper Sa Sistema de distribucion, almacenamiento y reprudccion de musica digit alizada
WO2000074337A3 (fr) * 1999-06-02 2001-07-26 Ac Properties Bv Systeme, procede et article manufacture destines a un serveur de base de donnees de regles dans une architecture de systeme de communication hybride
WO2000074337A2 (fr) * 1999-06-02 2000-12-07 Ac Properties B.V. Systeme, procede et article manufacture destines a un serveur de base de donnees de regles dans une architecture de systeme de communication hybride
US10225584B2 (en) 1999-08-03 2019-03-05 Videoshare Llc Systems and methods for sharing video with advertisements over a network
US10362341B2 (en) 1999-08-03 2019-07-23 Videoshare, Llc Systems and methods for sharing video with advertisements over a network
WO2001053961A1 (fr) * 2000-01-19 2001-07-26 Gentor.Com Inc. Serveur de liaison de canal d'emissions et procede correspondant
US7987492B2 (en) 2000-03-09 2011-07-26 Gad Liwerant Sharing a streaming video
US10277654B2 (en) 2000-03-09 2019-04-30 Videoshare, Llc Sharing a streaming video
US10523729B2 (en) 2000-03-09 2019-12-31 Videoshare, Llc Sharing a streaming video
US9083719B2 (en) 2000-05-04 2015-07-14 Focal Ip, Llc Controller for the intelligent interconnection of two communication networks, and method of use for same
WO2002028077A3 (fr) * 2000-09-25 2003-07-03 Nat Notification Ct Llc Systeme de traitement d'appel au moyen de reponse vocale interactive
WO2002028077A2 (fr) * 2000-09-25 2002-04-04 National Notification Center, Llc Systeme de traitement d'appel au moyen de reponse vocale interactive
US7000019B2 (en) 2000-10-17 2006-02-14 Hewlett-Packard/Development Company L.P. Establishment of a deferred network communication session
GB2368930B (en) * 2000-10-17 2005-04-06 Hewlett Packard Co Establishment of a deferred network communication session
GB2368930A (en) * 2000-10-17 2002-05-15 Hewlett Packard Co Establishment of a deferred network communication session
WO2003085537A1 (fr) * 2002-04-04 2003-10-16 Seung-Kee Mo Terminal commandant l'utilisation d'un ordinateur
WO2003088591A1 (fr) * 2002-04-17 2003-10-23 Veselov Andrei Anatol Evich Systeme de communication pour entreprise
US7542761B2 (en) * 2004-10-06 2009-06-02 At&T Mobility Ii Llc Voice quality on a communication link based on customer feedback
US11928707B2 (en) 2006-12-29 2024-03-12 The Nielsen Company (Us), Llc Systems and methods to pre-scale media content to facilitate audience measurement
US10885543B1 (en) 2006-12-29 2021-01-05 The Nielsen Company (Us), Llc Systems and methods to pre-scale media content to facilitate audience measurement
US8792118B2 (en) 2007-09-26 2014-07-29 Ringcentral Inc. User interfaces and methods to provision electronic facsimiles
US9948775B2 (en) 2007-09-28 2018-04-17 Ringcentral, Inc. Techniquest for bypassing call screening in a call messaging system
US8213587B2 (en) 2007-09-28 2012-07-03 Ringcentral, Inc. Inbound call identification and management
US9258673B2 (en) 2007-09-28 2016-02-09 RingControl, Inc. Centralized status server for call management of location-aware mobile devices
US8885809B2 (en) 2007-09-28 2014-11-11 Ringcentral, Inc. Techniques for bypassing call screening in a call messaging system
US9736756B2 (en) 2007-09-28 2017-08-15 Ringcentral, Inc. Centralized status server for call management of location-aware mobile devices
US8275110B2 (en) 2007-09-28 2012-09-25 Ringcentral, Inc. Active call filtering, screening and dispatching
US8681968B2 (en) 2007-09-28 2014-03-25 Ringcentral, Inc. Techniques for bypassing call screening in a call messaging system
US8670545B2 (en) 2007-09-28 2014-03-11 Ringcentral, Inc. Inbound call identification and management
DE102007047632A1 (de) * 2007-10-04 2009-04-09 T-Mobile International Ag Interconnection virtueller Welten mit mobilen Nachrichtendiensten
US9084186B2 (en) 2008-11-24 2015-07-14 Ringcentral, Inc. Call management for location-aware mobile devices
US9191505B2 (en) 2009-05-28 2015-11-17 Comcast Cable Communications, Llc Stateful home phone service
US10284441B2 (en) 2010-11-03 2019-05-07 Google Llc Data delivery
US9602369B2 (en) 2010-11-03 2017-03-21 Google Inc. Data delivery
WO2014062258A1 (fr) * 2012-10-19 2014-04-24 Innovation Software, Llc Enregistreur de clics manuels
EP3280099A4 (fr) * 2015-03-31 2018-12-19 Nec Corporation Système de réseau, procédé de commande de réseau, et appareil de commande
US10869196B2 (en) 2015-08-12 2020-12-15 Tencent Technology (Shenzhen) Company Limited Internet access authentication method and client, and computer storage medium
RU2647637C1 (ru) * 2017-06-20 2018-03-16 Федеральное государственное бюджетное учреждение "16 Центральный научно-исследовательский испытательный ордена Красной Звезды институт имени маршала войск связи А.И. Белова" Министерства обороны Российской Федерации Автоматизированное рабочее место оператора аппаратуры передачи данных
US11877028B2 (en) 2018-12-04 2024-01-16 The Nielsen Company (Us), Llc Methods and apparatus to identify media presentations by analyzing network traffic
CN111949422A (zh) * 2020-08-26 2020-11-17 南京云灿信息科技有限公司 基于mq和异步io的数据多级缓存与高速传输记录方法
CN111949422B (zh) * 2020-08-26 2024-04-16 南京云灿信息科技有限公司 基于mq和异步io的数据多级缓存与高速传输记录方法

Also Published As

Publication number Publication date
WO1998034391A9 (fr) 1999-09-10
EP1000500A4 (fr) 2002-02-05
IL131102A0 (en) 2001-01-28
CN1262836A (zh) 2000-08-09
WO1998034391A3 (fr) 1998-12-23
KR20000071228A (ko) 2000-11-25
CA2289455A1 (fr) 1998-08-06
EP1000500A2 (fr) 2000-05-17
TR199901842T2 (xx) 2000-10-23
NZ336939A (en) 2001-04-27
AP9901611A0 (en) 1999-09-30
WO1998034391A8 (fr) 2000-01-20

Similar Documents

Publication Publication Date Title
AU725933C (en) A communication system architecture
US6731625B1 (en) System, method and article of manufacture for a call back architecture in a hybrid network with support for internet telephony
US7145898B1 (en) System, method and article of manufacture for selecting a gateway of a hybrid communication system architecture
US6335927B1 (en) System and method for providing requested quality of service in a hybrid network
US5867494A (en) System, method and article of manufacture with integrated video conferencing billing in a communication system architecture
US6754181B1 (en) System and method for a directory service supporting a hybrid communication system architecture
US6909708B1 (en) System, method and article of manufacture for a communication system architecture including video conferencing
AU738963B2 (en) A system, method and article of manufacture for switched telephony communication
US5999525A (en) Method for video telephony over a hybrid network
US5867495A (en) System, method and article of manufacture for communications utilizing calling, plans in a hybrid network
WO1998034391A2 (fr) Architecture d'un systeme de communication
US7945592B2 (en) XML based transaction detail records
JP2001520820A (ja) 通信システム構造
JP2002505043A (ja) 通信システム構造
AU6259298A (en) A communication system architecture
MXPA99007165A (en) A communication system architecture
AU2002252424A1 (en) XML based transaction detail records
MXPA00012574A (en) Closed user network billing

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 131102

Country of ref document: IL

Ref document number: 98803987.7

Country of ref document: CN

AK Designated states

Kind code of ref document: A2

Designated state(s): AU CA GM GW ID JP MX

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

Designated state(s): AU CA GM GW ID JP MX

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 62592/98

Country of ref document: AU

ENP Entry into the national phase

Ref document number: 2289455

Country of ref document: CA

Ref document number: 2289455

Country of ref document: CA

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 336939

Country of ref document: NZ

WWE Wipo information: entry into national phase

Ref document number: 1998904802

Country of ref document: EP

Ref document number: 1999/01842

Country of ref document: TR

WWE Wipo information: entry into national phase

Ref document number: PA/a/1999/007165

Country of ref document: MX

Ref document number: 1019997007009

Country of ref document: KR

WWW Wipo information: withdrawn in national office

Ref document number: 1019997007009

Country of ref document: KR

AK Designated states

Kind code of ref document: C2

Designated state(s): AU CA GM GW ID JP MX

AL Designated countries for regional patents

Kind code of ref document: C2

Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE

COP Corrected version of pamphlet

Free format text: PAGES 588-687, DESCRIPTION, REPLACED BY NEW PAGES 588-687; PAGES 688-701, CLAIMS, REPLACED BY NEW PAGES 688-709; PAGES 1/195-195/195; DRAWINGS, REPLACED BY NEW PAGES 1/134-134/134; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)

Free format text: (EXCEPT US)

AK Designated states

Kind code of ref document: C1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH GM GW HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: C1

Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN ML MR NE SN TD TG

CFP Corrected version of a pamphlet front page
CR1 Correction of entry in section i

Free format text: PAT. BUL. 31/98 UNDER (81) ADD "AL, AM, AT, AZ, BA, BB, BG, BR, BY, CH, CN, CU, CZ, DE, DK, EE, ES, FI, GB, GE, GH, HU, IL, IS, KE, KG, KP, KR, KZ, LC, LK, LR, LS, LT, LU, LV, MD, MG, MK, MN, MW, NO, NZ, PL, PT, RO, RU, SD, SE, SG, SI, SK, SL, TJ, TM, TR, TT, UA, UG, US, UZ, VN, YU, ZW; AP (GH, GM, KE, LS, MW, SD, SZ, UG, ZW); EA (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM); OA (BF, BJ, CF, CG, CI, CM, GA, GN, ML, MR, NE, SN, TD, TG)"; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

WWE Wipo information: entry into national phase

Ref document number: 1019997012638

Country of ref document: KR

WWP Wipo information: published in national office

Ref document number: 1998904802

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 1019997012638

Country of ref document: KR

WWW Wipo information: withdrawn in national office

Ref document number: 1998904802

Country of ref document: EP

WWR Wipo information: refused in national office

Ref document number: 1019997007009

Country of ref document: KR

WWR Wipo information: refused in national office

Ref document number: 1019997012638

Country of ref document: KR