text:
Telephone calls, data and other multimedia information is routed through a hybrid network which includes transfer of information across the internet. A media order entry captures complete user profile information for a user. This profile information is utilized by the system throughout the media experience for routing, billing, monitoring, reporting and other media control functions. Users can manage more aspects of a network than previously possible, and control network activities from a central site. The hybrid network also contains logic for responding to requests for quality of service and reserving the resources to provide the requested services.
1. A method for media communication over a hybrid network which includes a switched network and a packet switched network, comprising:
receiving a request for a media communication by a resource management processor connected to the hybrid network;
determining an amount of resources in the hybrid network necessary to obtain a requested quality of service;
allocating necessary resources to provide the requested quality of service on the hybrid network; and
releasing the necessary resources upon termination of the media communication.
2. The method for media communication in
transmitting the bill detail record to a call server connected to the hybrid network.
3. The method for media communication in
transmitting a message to the call server with a third entry indicative of time of termination of the medial communication.
4. The method for media communication in
creating an additional entry in the bill detail record indicative of a type of service provided by the hybrid network.
5. The method for media communication in
determining the requested quality of service by parsing a field from the request for a media communication.
6. The method for media communication in
determining the requested quality of service from profile information associated with a caller of the media communication.
[0001] This application is a continuation of U.S. patent application Ser. No. 08/751,917, filed on Nov. 18, 1996, which is hereby incorporated by reference in its entirety.
[0002] 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.
[0003] 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. Recently, software companies have begun to investigate the transfer of telephone calls across the internet. However, the system features that users demand of normal call processing are considered essential for call processing on the Internet. Today, those features are not available on the internet.
[0004] According to a broad aspect of a preferred embodiment of the invention, telephone calls, data and other multimedia information is routed through a hybrid network which includes transfer of information across the internet utilizing 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. The hybrid network also contains logic for responding to requests for quality of service and reserving the resources to provide the requested services.
[0005] The foregoing and other objects, aspects and advantages are better understood from the following detailed description of a preferred embodiment of the invention, with reference to the drawings, in which:
[0006]FIG. 1A is a block diagram of a representative hardware environment in accordance with a preferred embodiment;
[0007]FIG. 1B is a block diagram illustrating the architecture of a typical Common Channel Signaling System #7 (SS7) network in accordance with a preferred embodiment;
[0008]FIG. 1C is a block diagram of an internet telephony system in accordance with a preferred embodiment;
[0009]FIG. 1D is a block diagram of a hybrid switch in accordance with a preferred embodiment;
[0010]FIG. 1E is a block diagram of the connection of a hybrid switch in accordance with a preferred embodiment;
[0011]FIG. 1F is a block diagram of a hybrid (internet-telephony) switch in accordance with a preferred embodiment;
[0012]FIG. 1G is a block diagram showing the software processes involved in the hybrid internet telephony switch in accordance with a preferred embodiment;
[0013]FIG. 2 is a block diagram illustrating the use of Protocol Monitoring Units(PMUs) in a typical SS7 network in accordance with a preferred embodiment;
[0014]FIG. 3 is a block diagram illustrating the systems architecture of the preferred embodiment;
[0015]FIG. 4 is a high-level process flowchart illustrating the logical system components in accordance with a preferred embodiment;
[0016] FIGS. 5-9 are process flowcharts illustrating the detailed operation of the components illustrated in FIG. 4 in accordance with a preferred embodiment;
[0017]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;
[0018]FIG. 10B illustrates an internet routing network in accordance with a preferred embodiment;
[0019]FIG. 11 illustrates a Virtual Network (VNET) Personal Computer (PC) to PC Information call flow in accordance with a preferred embodiment;
[0020]FIG. 12 illustrates a VNET Personal Computer (PC) to out-of-network PC Information call flow in accordance with a preferred embodiment;
[0021]FIG. 13 illustrates a VNET Personal Computer (PC) to out-of-network Phone Information call flow in accordance with a preferred embodiment;
[0022]FIG. 14 illustrates a VNET Personal Computer (PC) to in-network Phone Information call flow in accordance with a preferred embodiment;
[0023]FIG. 15 illustrates a personal computer to personal computer internet telephony call in accordance with a preferred embodiment;
[0024]FIG. 16 illustrates a phone call that is routed from a PC through the Internet to a phone in accordance with a preferred embodiment;
[0025]FIG. 17 illustrates a phone to PC call in accordance with a preferred embodiment;
[0026]FIG. 18 illustrates a phone to phone call over the internet in accordance with a preferred embodiment;
[0027]FIG. 19A and 19B illustrate an Intelligent Network in accordance with a preferred embodiment;
[0028]FIG. 19C illustrates a Video-Conferencing Architecture in accordance with a preferred embodiment;
[0029]FIG. 19D illustrates a Video Store and Forward Architecture in accordance with a preferred embodiment;
[0030]FIG. 19E illustrates an architecture for transmitting video telephony over the Internet in accordance with a preferred embodiment;
[0031]FIG. 19F is a block diagram of an internet telephony system in accordance with a preferred embodiment;
[0032]FIG. 19G is a block diagram of a prioritizing access/router in accordance with a preferred embodiment;
[0033]FIG. 20 is a high level block diagram of a networking system in accordance with a preferred embodiment;
[0034]FIG. 21 is a functional block diagram of a portion of the system shown in FIG. 20 in accordance with a preferred embodiment;
[0035]FIG. 22 is another high level block diagram in accordance with a preferred embodiment of FIG. 21;
[0036]FIG. 23 is a block diagram of a switchless network system in accordance with a preferred embodiment;
[0037]FIG. 24 is a hierarchy diagram illustrating a portion of the systems shown in FIGS. 20 and 23 in accordance with a preferred embodiment;
[0038]FIG. 25 is a block diagram illustrating part of the system portion shown in FIG. 24 in accordance with a preferred embodiment;
[0039]FIG. 26 is a flow chart illustrating a portion of a method in accordance with a preferred embodiment;
[0040] FIGS. 27-39 are block diagrams illustrating further aspects of the systems of FIGS. 20 and 23 in accordance with a preferred embodiment;
[0041]FIG. 40 is a diagrammatic representation of a web server logon in accordance with a preferred embodiment;
[0042]FIG. 41 is a diagrammatic representation of a server directory structure used with the logon of FIG. 40 in accordance with a preferred embodiment;
[0043]FIG. 42 is a more detailed diagrammatic representation of the logon of FIG. 40 in accordance with a preferred embodiment;
[0044] FIGS. 43-50 are block diagrams illustrating portions of the hybrid network in accordance with a preferred embodiment;
[0045]FIG. 51 illustrates a configuration of the Data Management Zone (DMZ) 5105 in accordance with a preferred embodiment;
[0046] FIGS. 52A-52C illustrate network block diagrams in connection with a dial-in environment in accordance with a preferred embodiment;
[0047]FIG. 53 depicts a flow diagram illustrating the fax tone detection in accordance with a preferred embodiment;
[0048]FIGS. 54A through 54E depict a flow diagram illustrating the VFP Completion process for fax and voice mailboxes in accordance with a preferred embodiment;
[0049]FIGS. 55A and 55B illustrate the operation of the Pager Termination processor in accordance with a preferred embodiment;
[0050]FIG. 56 depicts the GetCallback routine called from the pager termination in accordance with a preferred embodiment;
[0051]FIG. 57 shows a user login screen for access to online profile management in accordance with a preferred embodiment;
[0052]FIG. 58 shows a call routing screen, used to set or change a user's call routing instructions in accordance with a preferred embodiment;
[0053]FIG. 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;
[0054]FIG. 60 shows an override routing screen, which allows a user to route all calls to a selected destination in accordance with a preferred embodiment;
[0055]FIG. 61 shows a speed dial numbers screen, used to set up speed dial in accordance with a preferred embodiment;
[0056]FIG. 62 shows a voicemail screen, used to set up voicemail in accordance with a preferred embodiment;
[0057]FIG. 63 shows a faxmail screen, used to set up faxmail in accordance with a preferred embodiment;
[0058]FIG. 64 shows a call screening screen, used to set up call screening in accordance with a preferred embodiment;
[0059] FIGS. 65-67 show supplemental screens used with user profile management in accordance with a preferred embodiment;
[0060]FIG. 68 is a flow chart showing how the validation for user entered speed dial numbers is carried out in accordance with a preferred embodiment;
[0061] FIGS. 69A-69AI are automated response unit (ARU) call flow charts showing software implementation in accordance with a preferred embodiment;
[0062] FIGS. 70A-70R are console call flow charts further showing software implementation in accordance with a preferred embodiment;
[0063]FIG. 71 illustrates a typical customer configuration for a VNET to VNET system in accordance with a preferred embodiment;
[0064]FIG. 72 illustrates the operation of DAPs in accordance with a preferred embodiment;
[0065]FIG. 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;
[0066]FIG. 74 illustrates the customer side of a DAP procedure request in accordance with a preferred embodiment;
[0067]FIG. 75 illustrates operation of the switch 10530 to select a particular number or "hotline" for a caller in accordance with a preferred embodiment;
[0068]FIG. 76 illustrates the operation of a computer-based voice gateway for selectively routing telephone calls through the Internet in accordance with a preferred embodiment;
[0069]FIG. 77 illustrates the operation of the VRU of FIG. 76 deployed in a centralized architecture in accordance with a preferred embodiment;
[0070]FIG. 78 illustrates the operation of the VRU of FIG. 76 deployed in a distributed architecture in accordance with a preferred embodiment;
[0071]FIGS. 79A and 79B illustrate the operation of sample applications for Internet call routing in accordance with a preferred embodiment;
[0072]FIG. 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;
[0073]FIG. 81 illustrates an inb ound shared Automated Call Distributor (ACD) call with data sharing through a database in accordance with a preferred embodiment;
[0074]FIG. 82 is a block diagram of an exemplary telecommunications system in accordance with a preferred embodiment;
[0075]FIG. 83 is a block diagram of an exemplary computer syslem in accordance with a preferred embodiment;
[0076]FIG. 84 illustrates the Call Detail Record (CDR) and Private Network Record (PNR) call record formats in accordance with a preferred embodiment;
[0077]FIGS. 85A and 85B collectively illustrate the Expanded Call Detail Record (ECDR) and Expanded Private Network Record (ECDR) call record formats in accordance with a preferred embodiment;
[0078]FIG. 86 illustrates the Operator Service Record (OSR) and Private Operator Service Record (POSR) call record formats in accordance with a preferred embodiment;
[0079]FIGS. 87A and 87B collectively illustrate the Expanded Operator Service Record (OSR) and Expanded Private Operator Service Record (EPOSR) call record formats in accordance with a preferred embodiment;
[0080]FIG. 88 illustrates the Switch Event Record (SER) call record format in accordance with a preferred embodiment;
[0081]FIGS. 89A and 89B are control flow diagrams illustrating the conditions under which a switch uses the expanded record format in accordance with a preferred embodiment;
[0082]FIG. 90 is a control flow diagram illustrating the Change Time command in accordance with a preferred embodiment;
[0083]FIG. 91 is a control flow diagram illustrating the Change Daylight Savings Time command in accordance with a preferred embodiment;
[0084]FIG. 92 is a control flow diagram illustrating the Network Call Identifier (NCID) switch call processing in accordance with a preferred embodiment;
[0085]FIG. 93 is a control flow diagram illustrating the processing of a received Network Call Identifier in accordance with a preferred embodiment;
[0086]FIG. 94A is a control flow diagram illustrating the generation of a Network Call Identifier in accordance with a preferred embodiment;
[0087]FIG. 94B is a control flow diagram illustrating the addition of a Network Call Identifier to a call record in accordance with a preferred embodiment;
[0088]FIG. 95 is a control flow diagram illustrating the transport of a call in accordance with a preferred embodiment;
[0089]FIG. 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;
[0090]FIG. 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;
[0091]FIG. 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;
[0092]FIG. 99 shows how a video conference call initiated by the video operator in accordance with a preferred embodiment;
[0093]FIG. 100 shows the class hierarchy for video operator software system classes in accordance with a preferred embodiment;
[0094]FIG. 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;
[0095]FIG. 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;
[0096]FIG. 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;
[0097]FIG. 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;
[0098]FIG. 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;
[0099]FIG. 106 shows the class hierarchy for the video operator graphical user interface ("GUI") classes in accordance with a preferred embodiment;
[0100]FIG. 107 shows a database schema for the video operator shared database in accordance with a preferred embodiment;
[0101]FIG. 108 shows one embodiment of the Main Console window in accordance with a preferred embodiment;
[0102]FIG. 109 shows one embodiment of the Schedule window in accordance with a preferred embodiment;
[0103]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;
[0104]FIG. 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;
[0105]FIG. 112 shows one embodiment of the Console Output window 41205 which displays all error messages and alerts in accordance with a preferred embodiment; and
[0106]FIG. 113 shows a Properties dialog box in accordance with a preferred embodiment.
[0109] A. Internet Protocols . . . 31
[0110] B. International Telecommunication Union-Telecommunication Standardization Sector ("ITU-T") Standards . . . 31
[0113] A. Switching Techniques . . . 35
[0114] B. Gateways and Routers . . . 40
[0115] C. Using Network Level Communication for Smooth User Connection . . . 42
[0116] D. Datagrams and Routing . . . 43
[0119] B. Frame Relay . . . 45
[0122] A. Components of the MCI Intelligent Network . . . 48
[0123] 1. MCI Switching Network . . . 48
[0124] 2. Network Control System/Data Access Point (NCS/DAP) . . . 48
[0125] 3. Intelligent Services Network (ISN) 4 . . . 49
[0126] 4. Enhanced Voice Services (EVS) 9 . . . 50
[0127] 5. Additional Components . . . 50
[0128] B. Intelligent Network System Overview . . . 52
[0129] C. Call Flow Example . . . 53
[0131] A. Background . . . 56
[0132] 1. Broadband Access . . . 56
[0133] 2. Internet Telephony System . . . 56
[0134] 3. Capacity . . . 63
[0135] 4. Future Services . . . 63
[0136] B. ISP Architecture Framework . . . 64
[0137] C. ISP Functional Framework . . . 65
[0138] D. ISP Integrated Network Services . . . 69
[0139] E. ISP Components . . . 70
[0140] F. Switchless Communications Services . . . 71
[0141] G. Governing Principles . . . 72
[0142] 1. Architectural Principles . . . 72
[0143] 2. Service Feature Principles . . . 73
[0144] 3. Capability Principles . . . 73
[0145] 4. Service Creation, Deployment, and Execution Principles . . . 75
[0146] 5. Resource Management Model 2150 Principles . . . 76
[0147] 6. Data Management 2138 Principles . . . 77
[0148] 7. Operational Support Principles . . . 80
[0149] 8. Physical Model Principles . . . 81
[0150] H. ISP Service Model . . . 82
[0151] 1. Purpose . . . 82
[0152]2. Scope of Effort . . . 83
[0153] 3. Service Model Overview . . . 84
[0154] 4. Service Structure . . . 84
[0155] 5. Service 2200 Execution . . . 88
[0156] 6. Service Interactions . . . 90
[0157] 7. Service Monitoring . . . 92
[0158] I. ISP Data Management Model . . . 92
[0159] 1. Scope . . . 92
[0160] 2. Purpose . . . 93
[0161] 3. Data management Overview . . . 93
[0162] 4. Logical Description . . . 97
[0163] 5. Physical Description . . . 102
[0164] 6. Technology Selection . . . 104
[0165] 7. Implementations . . . 105
[0166] 8. Security . . . 105
[0167] 9. Meta-Data . . . 105
[0168] 10. Standard Database Technologies . . . 106
[0169] J. ISP Resource Management Model . . . 106
[0170] 2. The Local Resource Manager (LRM): . . . 111
[0171] 3. The Global Resource Manager (GRM) 2188: . . . 111
[0172] 4. The Resource Management Model (RMM) . . . 112
[0173] 5. Component Interactions . . . 115
[0174] K. Operational Support Model . . . 118
[0175] 1. Introduction . . . 118
[0176] 2. The Operational Support Model . . . 121
[0177] 3. The Protocol Model . . . 125
[0178] 4. The Physical Model . . . 126
[0179] 5. Interface Points . . . 126
[0180] 6. General . . . 128
[0181] L. Physical Network Model . . . 129
[0182] 1. Introduction . . . 129
[0183] 2. Information Flow . . . 130
[0184] 3. Terminology . . . 132
[0185] 4. Entity Relationships . . . 133
[0187] A. Network Management . . . 134
[0188] B. Customer Service . . . 135
[0189] C. Accounting . . . 137
[0190] D. Commissions . . . 137
[0191] E. Reporting . . . 137
[0192] F. Security . . . 138
[0193] G. Trouble Handling . . . 138
[0195] A. Web Server Architecture . . . 139
[0196] 1. Welcome Server 450 . . . 139
[0197] 2. Token Server 454 . . . 141
[0198] 3. Application Servers . . . 143
[0199] B. Web Server System Environment . . . 144
[0200] 1. Welcome Servers . . . 145
[0201] 2. Token Servers 454 . . . 149
[0202] 3. Profile Management Application Servers . . . 150
[0203] C. Security . . . 150
[0204] D. Login Process . . . 151
[0205] E. Service Selection . . . 153
[0206] F. Service Operation . . . 153
[0207] 1. NIDS Server . . . 154
[0208] 2. TOKEN database service . . . 155
[0209] 3. SERVERS database service . . . 156
[0210] 4. HOSTILE_IP database service . . . 156
[0211] 5. TOKEN_HOSTS database service . . . 157
[0212] 6. SERVER_ENV database service . . . 158
[0213] 7. Chron Job(s) . . . 159
[0214] G. Standards . . . 159
[0215] H. System Administration . . . 160
[0216] I. Product/Enhancement . . . 161
[0217] J. Interface Feature Requirements (Overview) . . . 162
[0218] 1. The User Account Profile . . . 163
[0219] 2. The Database of Messages . . . 164
[0220] K. Automated Response Unit (ARU) Capabilities . . . 165
[0221] 1. User Interface . . . 165
[0222] L. Message Management . . . 168
[0223] 1. Multiple Media Message Notification . . . 168
[0224] 2. Multiple Media Message Manipulation . . . 168
[0225] 3. Text to Speech . . . 168
[0226] 4. Email Forwarding to a Fax Machine . . . 169
[0227] 5. Pager Notification of Messages Received . . . 170
[0228] 6. Delivery Confirmation of Voicemail . . . 170
[0229] 7. Message Prioritization . . . 170
[0230] M. Information Services . . . 170
[0231] N. Message Storage Requirements . . . 172
[0232] O. Profile Management . . . 172
[0233] P. Call Routing Menu Change . . . 173
[0234] Q. Two-way Pager Configuration Control and Response to Park and Page . . . 174
[0235] R. Personalized Greetings . . . 174
[0236] S. List Management . . . 174
[0237] T. Global Message Handling . . . 175
[0239] A. System Environment for Internet Media . . . 178
[0240] 1. Hardware . . . 178
[0241] 2. Object-Oriented Software Tools . . . 179
[0242] B. Telephony Over The Internet . . . 188
[0243] 1. Introduction . . . 189
[0244] 2. IP Phone as a Commercial Service . . . 192
[0245] 3. Phone Numbers in the Internet . . . 203
[0246] 4. Other Internet Telephony Carriers . . . 204
[0247] 5. International Access . . . 204
[0248] C. Internet Telephony Services . . . 212
[0249] D. Call Processing . . . 220
[0250] 1. VNET Call Processing . . . 220
[0251] 2. Descriptions of Block Elements . . . 224
[0252] E. Re-usable Call Flow Blocks . . . 22 9
[0253] 1. VNET PC connects to a corporate intranet and logs in to a directory service . . . 229
[0254] 2. VNET PC queries a directory service for a VNET translation234
[0255] 3. PC connects to an ITG . . . 237
[0256] 4. ITG connects to a PC . . . 238
[0257] 5. VNET PC to PC Call Flow Description . . . 239
[0258] 6. Determining best choice for Internet client selection of an Internet Telephony Gateway server on the Internet: . . . 240
[0259] 7. Vnet Call Processing . . . 249
[0261] A. SNMS Circuits Map . . . 279
[0262] B. SNMS Connections Map . . . 279
[0263] C. SNMS Nonadjacent Node Map . . . 279
[0264] D. SNMS LATA Connections Map . . . 279
[0265] E. NPA-NXX Information List . . . 280
[0266] F. End Office Information List . . . 280
[0267] G. Trunk Group Information List . . . 280
[0268] H. Filter Definition Window . . . 281
[0269] I. Trouble Ticket Window . . . 281
[0271] A. Components of Video Telephony System . . . 283
[0272] 1. DSP modem pools with ACD . . . 283
[0273] 2. Agent . . . 284
[0274] 3. Video on Hold Server . . . 284
[0275] 4. Video Mail Server . . . 284
[0276] 5. Video Content Engine . . . 284
[0277] 6. Reservation Engine . . . 285
[0278] 7. Video Bridge . . . 285
[0279] B. Scenario . . . 285
[0280] C. Connection Setup . . . 285
[0281] D. Calling the Destination . . . 287
[0282] E. Recording Video-Mail, Store & Forward Video and Greetings . . . 288
[0283] F. Retrieving Video-Mail and Video On Demand . . . 288
[0284] G. Video-conference Scheduling . . . 289
[0286] A. Components . . . 291
[0287] L. Directory and Registry Engine . . . 291
[0288] 2. Agents . . . 292
[0289] 3. Video Mail Server . . . 292
[0290] 4. Video Content Engine . . . 292
[0291] 5. Conference Reservation Engine . . . 292
[0292] 6. MCI Conference Space . . . 293
[0293] 7. Virtual Reality Space Engine . . . 293
[0294] B. Scenario . . . 293
[0295] C. Connection Setup . . . 293
[0296] D. Recording Video-Mail, Store & Forward Video and Greetings . . . 294
[0297] E. Retrieving Video-Mail and Video On Demand . . . 295
[0298] F. Video-conference Scheduling . . . 295
[0299] G. Virtual Reality . . . 296
[0301] A. Features . . . 296
[0302] B. Components . . . 297
[0303] 1. End-User Terminals . . . 297
[0304] 2. LAN Interconnect System . . . 298
[0305] 3. ITU H.323 Server . . . 298
[0306] 4. Gatekeeper . . . 299
[0307] 5. Operator Services Module . . . 299
[0308] 6. Multipoint Control Unit (MCU) . . . 300
[0309] 7. Gateway . . . 300
[0310] 8. Support Service Units . . . 301
[0311] C. Overview . . . 301
[0312] D. Call Flow Example . . . 302
[0313] 1. Point-to-Point Calls . . . 303
[0314] 2. Multipoint Video-Conference Calls . . . 308
[0315] E. Conclusion . . . 308
[0317] A. Features . . . 309
[0318] B. Architecture . . . 309
[0319] C. Components . . . 310
[0320] 1. Content Creation and Transcoding . . . 310
[0321] 2. Content Management and Delivery . . . 310
[0322] 3. Content Retrieval and Display . . . 311
[0323] D. Overview . . . 311
[0325] A. Hardware Architecture . . . 314
[0326] B. Video Operator Console . . . 318
[0327] C. Video Conference Call Flow . . . 323
[0328] D. Video Operator Software System . . . 324
[0329] 1. Class Hierarchy . . . 324
[0330] 2. Class and Object details . . . 327
[0331] E. Graphical User Interface Classes . . . 373
[0332] 1. Class Hierarchy . . . 373
[0333] 2. Class and Object details . . . 376
[0334] F. Video Operator Shared Database . . . 399
[0335] 1. Database Schema . . . 399
[0336] G. Video Operator Console Graphical User Interface Windows . . . 400
[0337] 1. Main Console Window . . . 400
[0338] 2. Schedule Window . . . 401
[0339] 3. Conference Window . . . 401
[0340] 4. Video Watch Window . . . 404
[0341] 5. Console Output Window . . . 405
[0342] 6. Properties Dialog Box . . . 405
[0344] A. User Interface . . . 406
[0345] B. Performance . . . 407
[0346] C. Personal Home Page . . . 408
[0347] 1. Storage Requirements . . . 410
[0348] 2. On Screen Help Text . . . 411
[0349] 3. Personal Home Page Directory . . . 411
[0350] 4. Control Bar . . . 412
[0351] 5. Home Page . . . 412
[0352] 6. Security Requirements . . . 413
[0353] 7. On Screen Help Text . . . 414
[0354] 8. Profile Management . . . 415
[0355] 9. Information Services Profile Management . . . 417
[0356] 10. Personal Home Page Profile Management . . . 419
[0357] 11. List Management . . . 420
[0358] 12. Global Message Handling . . . 422
[0359] D. Message Center . . . 423
[0360] 1. Storage Requirements . . . 426
[0361] E. PC Client Capabilities . . . 427
[0362] 1. User Interface . . . 427
[0363] 2. Security . . . 428
[0364] 3. Message Retrieval . . . 429
[0365] 4. Message Manipulation . . . 430
[0366] F. Order Entry Requirements . . . 431
[0367] 1. Provisioning and Fulfillment . . . 434
[0368] G. Traffic Systems . . . 435
[0369] H. Pricing . . . 435
[0370] I. Billing . . . 435
[0372] A. Overview . . . 437
[0373] 1. The ARU (Audio Response Unit) 502 . . . 437
[0374] 2. The VFP (Voice Fax Platform) 504 . . . 437
[0375] 3. The DDS (Data Distribution Service) 506 . . . 438
[0376] B. Rationale . . . 438
[0377] C. Detail . . . 438
[0378] 1. Call Flow Architecture 520 . . . 439
[0379] 2. Network Connectivity . . . 439
[0380] 3. Call Flow . . . 441
[0381] 4. Data Flow Architecture . . . 443
[0382] D. Voice Fax Platform (VFP) 504 Detailed Architecture . . . 444
[0383] 1. Overview . . . 444
[0384] 2. Rationale . . . 444
[0385] 3. Detail . . . 446
[0386] E. Voice Distribution Detailed Architecture . . . 451
[0387] 1. Overview . . . 451
[0388] 2. Rationale . . . 451
[0389] F. Login Screen . . . 474
[0390] G. Call Routing Screen . . . 475
[0391] H. Guest Menu Configuration Screen . . . 477
[0392] I. Override Routing Screen . . . 480
[0393] J. Speed Dial Screen . . . 481
[0396] A. Introduction . . . 597
[0397] B. Details . . . 597
[0399] A. An Embodiment . . . 601
[0400] B. Another Embodiment . . . 613
[0402] A. An Embodiment . . . 622
[0403] 1. Call Record Format . . . 622
[0404] 2. Network Call Identifier . . . 623
[0405] B. Another Embodiment . . . 626
[0406] 1. Call Record Format . . . 626
[0407] 2. Network Call Identifier . . . 636
[0409] 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.
[0410] Before progressing further, a common misunderstanding regarding the usage of the term "internet" should be resolved. Originally, the term was used only as the name of the network based upon the Internet Protocol, but now, 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.
[0412] A. Internet Protocols
[0413] Protocols govern the behavior along the Internet backbone and thus set down the key rules for data communication. Transmission Control Protocol/Internet Protocol (TCP/IP) has an open nature and is available to everyone, meaning that it attempts to create a network protocol system that is independent of computer or network operating system and architectural differences. As such, TCP/IP protocols are publicly available in standards documents, particularly in Requests for Comments (RFCs). A requirement for Internet connection is TCP/IP, which consists of a large set of data communications protocols, two of which are the Transmission Control Protocol and the Internet Protocol. An excellent description of the details associated with TCP/IP and UDP/IP is provided in TCP/IP Illustrated, W. Richard Stevens, Addison-Wesley Publishing Company (1996).
[0414] B. International Telecommunication Union-Telecommunication Standardization Sector ("ITU-T") Standards
[0415] The International Telecommunication Union-Telecommunication Standardization Sector ("ITU-T") has established numerous standards governing protocols and line encoding for telecommunication devices. Because many of these standards are referenced throughout this document, summaries of the relevant standards are listed below for reference.
[0416] ITUG. 711 Recommendation for Pulse Code Modulation of 3 kHz Audio Channels.
[0417] ITUG. 722 Recommendation for 7kHz Audio Coding within a 64 kbit/s channel.
[0418] ITUG. 723 Recommendation for dual rate speech coder for multimedia communication transmitting at 5.3 and 6.3 kbits.
[0419] ITUG. 728 Recommendation for coding of speech at 16 kbit/s using low-delay code excited linear prediction (LD-CELP)
[0420] ITU H.221 Frame Structure for a 64 to 1920 kbit/s Channel in Audiovisual Teleservices
[0421] ITU H.223 Multiplexing Protocols for Low Bitrate Multimedia Terminals
[0422] ITU H.225 ITU Recommendation for Media Stream Packetization and Synchronization on non-guaranteed quality of service LANs.
[0423] ITU H.230 Frame-synchronous Control and Indication Signals for Audiovisual Systems
[0424] ITU H.231 Multipoint Control Unit for Audiovisual Systems Using Digital Channels up to 2 Mbit/s
[0425] ITU H.242 System for Establishing Communication Between Audiovisual Terminals Using Digital Channels up to 2 Mbits
[0426] ITU H.243 System for Establishing Communication Between Three or More Audiovisual Terminals Using Digital Channels up to 2 Mbit/s
[0427] ITU H.245 Recommendation for a control protocol for multimedia communication
[0428] ITU H.261 Recommendation for Video Coder-Decoder for audiovisual services supporting video resolutions of 352�288 pixels and 176�144 pixels.
[0429] ITU H.263 Recommendation for Video Coder-Decoder for audiovisual services supporting video resolutions of 128�96 pixels, 176�144 pixels, 352�288 pixels, 704�576 pixels and 1408�1152 pixels.
[0430] ITU H.320 Recommendation for Narrow Band ISDN visual telephone systems.
[0431] ITU H.321 Visual Telephone Terminals over ATM
[0432] ITU H.322 Visual Telephone Terminals over Guaranteed Quality of Service LANs
[0433] ITU H.323 ITU Recommendation for Visual Telephone Systems and Equipment for Local Area Networks which provide a non-guaranteed quality of service.
[0434] ITU H.324 Recommendation for Terminals and Systems for low bitrate(28.8 Kbps) multimedia communication on dial-up telephone lines.
[0435] ITU T.120 Transmission Protocols for Multimedia Data.
[0436] In addition, several other relevant standards are referenced in this document:
[0437] ISDN Integrated Services Digital Network, the digital communication standard for transmission of voice, video and data on a single communications link.
[0438] RTP Real-Time Transport Protocol, an Internet Standard Protocol for transmission of real-time data like voice and video over unicast and multicast networks.
[0439] IP Internet Protocol, an Internet Standard Protocol for transmission and delivery of data packets on a packet switched network of interconnected computer systems.
[0440] PPP Point-to-Point Protocol
[0441] MPEG Motion Pictures Expert Group, a standards body under the International Standards Organization(ISO), Recommendations for compression of digital Video and Audio including the bit stream but not the compression algorithms.
[0442] SLIP Serial Line Internet Protocol
[0443] RSVP Resource Reservation Setup Protocol
[0444] UDP User Datagram Protocol
[0446] The popularity of the TCP/IP protocols on the Internet grew rapidly because they met an important need for worldwide data communication and had several important characteristics that allowed them to meet this need. These characteristics, still in use today, include:
[0447] A common addressing scheme that allows any device running TCP/IP to uniquely address any other device on the Internet. 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.
[0448] Independence from any specific physical network hardware, allows TCP/IP to integrate many different kinds of networks. TCP/IP can be used over an Ethernet, a token ring, a dial-up line, or virtually any other kinds of physical transmission media.
[0450] A. Switching Techniques
[0451] An understanding of how information travels in communication systems is required to appreciate the recent steps taken by key players in today's Internet backbone business. The traditional type of communication network is circuit switched. The U.S. telephone system uses such circuit switching techniques. When a person or a computer makes a telephone call, 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.
[0452] The establishment of a completed path is a prerequisite to the transmission of data for circuit switched networks. After the circuit is in place, 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. 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. In an ISDN embodiment, however, the analog signals are converted to digital at the device and transmitted to the LEC as digital information.
[0453] Upon connection, 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, 64 Kbps is the rate required to send voice digitized with the Pulse Code Modulated (PCM) technique. Many other methods for digitizing voice exist, including ADPCM (32 Kbps), 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.
[0454] This guarantee of capacity is the strength of circuit-switched networks. However, circuit switching has two significant drawbacks. First, the setup time can be considerable, because the call signal request may find the lines busy with other calls; in this event, there is no way to gain connection until some other connection terminates. Second, utilization can be low while costs are high. In other words, the calling party is charged for the duration of the call and for all of the time even if no data transmission takes place (i.e. no one speaks). Utilization can be low because the time between transmission of signals is unable to be used by any other calls, due to the dedication of the line. Any such unused bandwidth during the connection is wasted.
[0455] Additionally, the entire circuit switching infrastructure is built around 64 Kbps circuits. The infrastructure assumes the use of PCM encoding techniques for voice. However, very high quality codecs are available that can encode voice using less than one-tenth of the bandwidth of PCM. However, 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. Furthermore, each circuit generally only connects two parties. Without the assistance of conference bridging equipment, an entire circuit to a phone is occupied in connecting one party to another party. Circuit switching has no multicast or multipoint communication capabilities, except when used in combination with conference bridging equipment.
[0456] Other reasons for long call setup time include the different signaling networks involved in call setup and the sheer distance causing propagation delay. Analog signaling from an end station to a CO on a low bandwidth link can also delay call setup. Also, the call setup data travels great distances on signaling networks that are not always transmitting data at the speed of light. When the calls are international, the variations in signaling networks grows, the equipment handling call setup is usually not as fast as modem setup and the distances are even greater, so call setup slows down even more. Further, in general, connection-oriented virtual or physical circuit setup, such as circuit switching, requires more time at connection setup time than comparable connectionless techniques due to the end-to-end handshaking required between the conversing parties.
[0457] Message switching is another switching strategy that has been considered. With this form of switching, no physical path is established in advance between the sender and receiver; instead, whenever the sender has a block of data to be sent, it is stored at the first switching office and retransmitted to the next switching point after error inspection. Message switching places no limit on block size, thus requiring that switching stations must have disks to buffer long blocks of data; also, a single block may tie up a line for many minutes, rendering message switching useless for interactive traffic.
[0458] 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.
[0459] 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, itthroughput 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.
[0460] 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. Their suitability has been improved for computer-to-computer communications but remains far from optimal. A cable running between two computers can transfer data at speeds in the hundreds of megabits, and even gigabits per second. A poor error rate at these speeds would be only one error per day. In contrast, a dial-up line, using standard telephone lines, has a maximum data rate in the thousands of bits per second, and a much higher error rate. In fact, the combined bit rate times error rate performance of a local cable could be 11 orders of magnitude better than a voice-grade telephone line. New technology, however, has been improving the performance of these lines.
[0461] B. Gateways and Routers
[0462] 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.
[0463] In terms of architecture, two given networks are connected by a computer that attaches to both of them. Internet 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.
[0464] 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.
[0465] Now, it is useful to take a simplified look at routing in traditional telephone systems. 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.
[0466] 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.
[0467] If the subscriber attached to a given end office calls a user attached to a different end office, more work has to be done in the routing of the call. First, 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. There are sectional and regional offices that form a network by which the toll offices are connected. The toll, sectional, and regional exchanges communicate with each other via high bandwidth inter-toll trunks. The number of different kinds of switching centers and their specific topology varies from country to country, depending on its telephone density.
[0468] C. Using Network Level Communication for Smooth User Connection
[0469] 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.
[0470] D. Datagrams and Routing
[0471] The basis of Internet service is an underlying, connectionless packet delivery system run by routers, with the basic unit of transfer being the packet. In intemets running 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.
[0472] In packet switching systems, routing is the process of choosing a path over which to send packets. As mentioned before, 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.
[0473] At this stage, a distinction should be made between direct delivery and indirect delivery. 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.
[0474] 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. In indirect delivery, 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.
[0476] The changing face of the internet world causes a steady inflow of new systems and technology. The following three developments, each likely to become more prevalent in the near future, serve as an introduction to the technological arena:
[0478] Asynchronous Transfer Mode (ATM) is a networking technology using a high-speed, connection-oriented system for both local area and wide area networks. ATM networks require modern hardware including:
[0479] High speed switches that can operate at gigabit (trillion bit) per second speeds to handle the traffic from many computers;
[0480] Optical fibers (versus copper wires) that provide high data transfer rates, with host-to-ATM switch connections running at 100 or 155 Mbps (million bits per second);
[0481] Fixed size cells, each of which includes 53 bytes. 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.
[0482] B. Frame Relay
[0483] 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.
[0485] 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. To adopt ISDN, 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:
[0486] 1. To provide an internationally accepted standard for voice, data and signaling;
[0487] 2. To make all transmission circuits end-to-end digital;
[0488] 3. To adopt a standard out-of-band signaling system; and To bring significantly more bandwidth to the desktop.
[0490] 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). 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.
[0491] Before proceeding further, it will be helpful to establish some terms.
[0492] 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.
[0493] Intelligent Network Features and Services include
[0494] Call type identification;
[0495] Call Routing and selective termination;
[0496] Operator selection and call holding;
[0497] Manual and Automated Operator;
[0498] Voice Recognition and automated, interactive response;
[0499] Customer and customer profile verification and validation;
[0500] Voice Mail;
[0501] Call validation and database;
[0502] Audio Conference reservation;
[0503] Video Conference reservation;
[0504] Fax delivery and broadcasting;
[0505] Customer Billing;
[0506] Fraud Monitoring;
[0507] Operational Measurements and Usage Statistics reporting; and Switch interface and control.
[0508] A. Components of the MCI Intelligent Network
[0509]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
[0510] MCI Switching Network 2
[0511] Network Control System (NCS)/Data Access Point(DAP) 3
[0512] ISN—Intelligent Services Network 4
[0513] EVS—Enhanced Voice Services 9
[0514] 1. MCI Switching Network
[0515] 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.
[0516] 2. Network Control System/Data Access Point (NCS/DAP)
[0517] 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.
[0518] The different services offered by NCS/DAP 3 include:
[0519] Number Translation for 800, 900, VNET Numbers;
[0520] Range Restrictions to restrict toll calling options and advanced parametric routing including Time of Day, Day of Week/Month, Point of Origin and percentage allocation across multiple sites;
[0521] Information Database including Switch ID and Trunk ID of a terminating number for a given call;
[0522] Remote Query to Customer Databases;
[0523] VNET/950 Card Validation Services; and
[0524] VNET ANI/DAL Validation Services.
[0525] 3. Intelligent Services Network (ISN) 4
[0526] The ISN 4 includes an Automatic Call Distributor (ACD)4 a for routing the calls. The ACD4 a communicates with the Intelligent Switch Network Adjunct Processor (ISNAP) 5 and delivers calls to the different manual or automated agents. 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 aiid Agents including Live Operators or Audio Response Units (ARU) including Automated Call Processors (ACPs)7, MTOCs6 and associated NAS 7 a. These systems communicate with each other on an Ethernet LAN and provide a variety of services for call processing.
[0527] The different services offered by the ONC include:
[0528] Validation Services including call-type identification, call verification and call restrictions if any;
[0529] Operator Services, both manual and automated, for customer assistance;
[0530] Database Services for a variety of database lookups;
[0531] Call Extending Capabilities;
[0532] Call Bridging Capabilities;
[0533] Prompt for User Input; and
[0534] Play Voice Messages.
[0535] 4. Enhanced Voice Services (EVS) 9
[0536] 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:
[0537] Play Customer Specific Voice Messages;
[0538] Prompt for User Input;
[0539] User Input based Information Access;
[0540] Call Extending Capabilities;
[0541] Call Bridging Capabilities;
[0542] Audio Conference Capabilities;
[0543] Call Transfer Capabilities;
[0544] Record User Voice Messages;
[0545] Remote Update of Recorded Voice; and
[0546] Send/Receive Fax.
[0547] 5. Additional Components
[0548] In addition to the above mentioned components, a set of additional components are also architected into the MCI Intelligent Network. These components are:
[0549] 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.
[0550] 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.
[0551] 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.
[0552] Operational Measurements include information gathering for analysis of product performance. Analysis of response to advertising campaigns, calling patterns resulti ig in specialized reports result from operational measurements. Information gathered is also used for future product planning and predicting infrastructure requirements.
[0553] 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.
[0554] B. Intelligent Network System Overnew
[0555] 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.
[0556] The call can be routed to an ACD 4 a which delivers calls to the various call processing agents like a live operator or an ARU. The ACD 4 a 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.
[0557] 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. Once the call is validated by processing of the call on the server, the agent communicates the status back to the ACD 4 a. The ACD 4 a 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. The agent also generates a Billing Detail Record (BDR) for billing information. When the call is completed, the switch generates an Operation Services Record (OSR) which is later matched with the corresponding BDR to create total billing information. 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.
[0558] C. Call Flow Example
[0559] The Call Flow example illustrates the processing of an 800 Number Collect Call from phone 1 in FIG. 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.
[0560] 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.
[0561] The call processing is now delegated to a set of intelligent computing systems through an Automatic Call Distributor (ACD) 4 a. In this example, since it is a collect call, the calling party has to reach a Manual or an Automated Operator before the call can be processed further. The call from the switch is transferred to an ACD 4 a 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 7 a. The ISNAP 5 determines which of the Agents is free to handle the call and routes the voice call to a specific Agent.
[0562] 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 resti ictions 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.
[0563] If the Called Party has agreed to receive 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.
[0564] 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). The Calling Party and the Called Party can now have a conversation through 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. 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.
[0565] 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.
[0566] In another embodiment, the Intelligent Network is adapted for newly emerging technologies, including POTS-based video-phones and internet telephony for voice and video. The following sections describe in detail the architecture, features and services based on the emerging technologies.
[0567] The following sections describe in detail the architecture, features and services based on several emerging technologies, all of which can be integrated into the Intelligent Network.
[0568] VlI. ISP FRAMEWORK
[0569] A. Background
[0570] 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.
[0571] 1. Broadband Access
[0572] A range of high bandwidth services are supported by a preferred embodiment. These include: Video on Demand, Conferencing, Distance Learning, and Telemedicine.
[0573] 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.
[0574] 2. Internet Telephony System
[0575] The Internet and with it, the World Wide Web, 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.
[0576] 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.
[0577]FIG. 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.
[0578] In an embodiment, 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. In an alternate embodiment, 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.
[0579] 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.
[0580] 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. 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.
[0581] Various services are attached to the PSTN through individual communication links including an attachment to the Intelligent Services Network (ISN) 1990, direct-dial plan, provisioning 1974, order entry 1975, billing 1976, directory services 1977, conferencing services 1978, and authorization/authentication services 1979. All of these services can communicate between themselves using the PSTN 1960 and the Internet 1910 via a gateway 1950. The functionality of the ISN 1990 and the DAP 1972 can be utilized by devices attached to the Internet 1910.
[0582]FIG. 19G is a block diagram of a Prioritizing Access/Router in accordance with a preferred embodiment. A prioritizing access router (PAR) 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.
[0583] 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 FIG. 19G.
[0584] First, at 2010, 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. 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.
[0585] 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.
[0586] 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
[0587] destination IP Address
[0588] source IP address
[0589] combined source/destination IP Address
[0590] combined destination IP Address! UDP Port
[0591] combined destination IP Address/TCP Port
[0592] combined source IP address/UDP Port
[0593] combined source IP Address/TCP Port
[0594] combined source IP Address and TCP or UDP port with destination IP address
[0595] combined destination IP Address and TCP or UDP port with source IP address
[0596] combined source IP Address and TCP or UDP port with destination IP address and TCP/UDP Port.
[0597] The packet classifier checks its table of flow specifications against Lhe 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.
[0598] The packet classifier 2050 hands off priority tagged and non-tagged packets to the packet scheduler 2060 via the process to process interface 2090. 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.
[0599] 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.
[0600] 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.
[0601] 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.
[0602] Turning now to 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 deliverv of intelligent services to the MCI network across all the components of the ISP.
[0603] Each of the existing communication network systems has its own way of providing service management, resource management, data management, security, distributed processing, network control, or operations support. The architecture of the ISP 2100 defines a single cohesive architectural framework covering these areas. The architecture is focused on achieving the following goals:
[0604] Develop global capabilities;
[0605] Deliver enhanced future services;
[0606] Make efficient use of resources;
[0607] Improve time to market;
[0608] Reduce maintenance and operations costs;
[0609] Increase overall product quality; and
[0610] Introduce scalability both upward and downward capabilities.
[0611] 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.
[0612] 3. Capacity
[0613] 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.
[0614] 4. Future Services
[0615] The above capabilities will be used to deliver:
[0616] Telephony and messaging services beyond what we have today;
[0617] Emerging video and multi-media offerings;
[0618] Powerful data services, including enhanced private networks; and
[0619] Software and equipment to enable end users to gain complete control over their services.
[0620] 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.
[0621] Services:
[0622] Customizable: customer is able to tailor the service offerings to their own needs.
[0623] Customer managed: customer has direct (inetwork-side) access for the administration and control of their service.
[0624] Loosely Coupled: services obtain and use network resources only when needed; customers pay for only what they use.
[0625] Bandwidth is available on demand, and without pre-allocation.
[0626] Secure & Private: customer privacy and confidentiality is paramount in the networked world. Commercial interests are guaranteed safe, secure transactions. Users and customers are identified and authenticated, and the network protected from tampering or corruption.
[0627] B. ISP Architecture Framework
[0628] The following section describes the role of the ISP Platform 2100 in providing customer services.
[0629] 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.
[0630] The following section describes the relationship of the ISP platform 2100 to various external systems both within and outside a provider.
[0631] The provider components 2108 in FIG. 20 are:
[0632] 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.
[0633] Revenue Management 2112—responsible for financial aspects of customer services.
[0634] Network Management 2114—responsible for the development and operation of the physical networks 2102.
[0635] Product Management 2116—responsible for the creation and marketing of customer services. The entities external to the ISP 2100 depicted in FIG. 20 are:
[0636] 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.
[0637] 3rd party Service Providers 2120—this represents those external organizations which deliver services to customers via the provider's Intelligent Services Platform 2100.
[0638] Service Resellers 2122—this represents those organizations which have customers using the facilities 2100.
[0639] Global Alliance Partners 2124—organizations which have shared facilities and exchange capabilities of their networks and service infrastructures.
[0640] C. ISP Functional Framework
[0641]FIG. 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 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.
[0642] The ISP 2100 Functional Components are:
[0643] Inbound and Outbound Gateways 2126—allows access to services provided by other providers, and allows other providers to access the provider's services.
[0644] Marketable Service Gateway 2128—interface to a three-tier service creation environment for services the provider sells. Services are deployed and updated through the Marketable Service Gateway 2128. This is actually no different than the Management Service Gateway 2130, except that the services created and deployed through here are for external customers.
[0645] 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.
[0646] 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.
[0647] Service Creation Environment 2136—Creates and deploys management services as well as marketable services, and their underlying features and capabilities.
[0648] 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.
[0649] Service Select 2148—Whether the services are accessed via a narrowban(i 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.
[0650] 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.
[0651] Specialized Resources 2152—Special network-based capabilities (Internet to voice conversion, DTMF-detection, Fax, Voice Recognition, etc) are shown as specialized resources 2152.
[0652] 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 2112. Data is stored short-term.
[0653] Statistics Server 2140—accepts statistics events from service engines, performs rollups, and allows queries against the data. Data is stored short-term.
[0654] Customer Based Capabilities 2156—software and specialized hardware on the customer premises that enables customer-premises based capabilities, such as ANI screening, Internet access, compression, interactive gaming, videoconferencing, retail access, you name it.
[0655] 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.
[0656] Other Special Services 2146—entail other specialized forms of applications or servers that may or may not be based on the Service Engine model. These components provide other computing resources and lower-level functional capabilities which may be used in Service delivery, monitoring, or management.
[0657] D. ISP Integrated Network Servtces
[0658]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 ISO Ethernet may supplant the current PSTN networks 2162.
[0659] 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 FIG. 22.
[0660] 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 2134. 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.
[0661] 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.
[0662] In FIG. 22, 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.
[0663] E. ISP Components
[0664] Ext App 2176—an external application;
[0665] App 2178—an internal ISP application (such as Fraud Analysis);
[0666] Dc 2180—Data client, a client to the ISP information base which provides a local data copy;
[0667] Ds 2182—Data server, one of the master copies of ISP information;
[0668] Admin 2184—the ISP administrative functions (for configurations, and maintenance);
[0669] Mon 2186—the ISP monitoring functions (for fault, performance, and accounting);
[0670] GRM 2188—the global resource management view for selected resources;
[0671] LRM 2190—the local resource management view for selected resources;
[0672] SR 2192—the pools of specialized resources (such as video servers, ports, speech recognition);
[0673] SE 2134—the generalized service engines which execute the desired service logic; and
[0674] Service Select 2194—the function which selects the service instance (running on a service engine 2134) which should process transactions offered from the networks.
[0675] F. Switchless Communications Seruices
[0676] 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. In the past, circuit switching was the only viable technology for transport of time-sensitive isochronous voice. Now, with the development of 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.
[0677] The switchless network is expected to provide a lower cost model than circuit switched architectures due to:
[0678] Flexibility to provide exactly the bandwidth required for each application, saving bandwidth when no data is being transferred. A minimum 56 Kbps circuit will not automatically be allocated for every call.
[0679] Adaptability to compression techniques, further reducing bandwidth requirements for each network session.
[0680] Lower costs for specialized resource equipment, due to the fact that analog ports do not have to be supplied for access to special DSP capabilities such as voice recognition or conferencing. A single high- bandwidth network port can serve hundreds of "calls" simultaneously.
[0681] Applicability and ease of adaptation of the switchless networks to advanced high-bandwidth services such as videoconferencing, training on demand, remote expert, integrated video/voice/fax/electronic mail, and information services. FIG. 23 illustrates a sample switchless network 2168 in accordance with a preferred embodiment.
[0682] G. Governing Principles
[0683] 1. Architectural Principles
[0684] This section contains a listing of architectural principles which provide the foundation of the architecture which follows.
[0685] Service Principles
[0686] 1. The Service Model must support seamless integration of new and existing services.
[0687] 2. Services are created from a common Service Creation Environment (SCE) which provides a seamless view of services.
[0688] 3. All services execute in common service logic execution environments (SLEEs), which do not require software changes when new services are introduced.
[0689] 4. All services are created from one o0 more service features.
[0690] 5. Data stored in a single customer profile in the ISP Data Servers may be used to drive multiple services.
[0691] 6. 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.
[0692] 2. Service Feature Principles
[0693] 1. All service features are described by a combination of one or more capabilities.
[0694] 2. All service features can be defined by a finite number of capabilities.
[0695] 3. Individual service features must be defined using a standard methodology to allow service designers to have a common understanding of a capability. Each service feature must document their inputs, outputs, error values, display behaviors, and potential service applications.
[0696] 4. Interaction of physical entities in the network implementation shall not be visible to the user of the service feature through the service feature interfaces.
[0697] 5. Each service feature should have a unified and stable external interface. The interface is described as a set of operations, and the data required and provided by each operation.
[0698] 6. 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 FIG. 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.
[0699] 3. Capability Principles
[0700] 1. Capabilities are defined completely independent from consideration of any physical or logical implementation (network implementation independent).
[0701] 2. 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.
[0702] 3. Individual capabilities must be defined using a standard methodology to allow service designers to have a common understanding of a capability. Each capability must document their inputs, outputs, error values, display behaviors, and potential service applications.
[0703] 4. Interaction of physical entities in the network implementation shall not be visible to the user of the capability through the capability interfaces.
[0704] 5. Capabilities may be combined to form high-level capabilities.
[0705] 6. 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.
[0706] 7. Capabilities may be realized in one or more piece of physical hardware or software in the network implementation.
[0707] 8. Data required by ea(-h capability operation is defined by the capability operation support data parameters and user instance data parameters.
[0708] 9. Capabilities are deployed into the network independent of any service.
[0709] 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.
[0710] 11. Capabilities are reusable. They are used without modification for other services.
[0711] 4. Service Creation, Deployment, and Execution Principles
[0712] 1. 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.
[0713] 2. Each Service Engine 2134 obtains its configuration data from the ISP data servers 2152 at activation time.
[0714] 3. 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.
[0715] 4. 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.
[0716] 5. Service Engines do not own any data, not even configuration data.
[0717] 6. Service Engines 2134 are not targets for deployment of data. Data Servers 2182 are targets for deployment of data.
[0718] 5. Resource Management Model 2150 Principles
[0719] 1. Resources 2152 should be accessible from anywhere on the network.
[0720] 2. Resources are not service-specific and can be shared across all services if desired.
[0721] 3. Resources of the same type should be managed as a group.
[0722] 4. The Resource Management Model 2150 should be flexible enough to accommodate various management policies, including: Least Cost, Round Robin, Least Recently Used, Most Available, First Encountered, Use Until Failure and Exclusive Use Until Failure.
[0723] 5. The Resource Management Model 2150 should optimize the allocation of resources and, if possible, honoring a selected policy.
[0724] 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.
[0725] 7. The Resource Management Model 2150 must allow for the enforcement of resource utilization policies such as resource time out and preemptive reallocation by priority.
[0726] 8. The Resource Management Model 2150 must be able to detect and access the status, utilization and health of resources in a resource pool.
[0727] 9. All Resources 2152 must be treated as managed objects.
[0728] 10. All resources must be able to register with the RM 2150 to enter a pool, and de-register to leave a pool.
[0729] 11. The only way to request, acquire and release a resource 2152 is through the RM 2150.
[0730] 12. 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.
[0731] 13. All specialized resources 2152 must be manageable from a consistent platform-wide viewpoint.
[0732] 14. All specialized resources 2152 must offer SNMP or CMIP agent functionality either directly or through a proxy.
[0733] 15. Every specialized resource 2152 shall be represented in a common management information base.
[0734] 16. All specialized resources shall support a standard set of operations to inquire, probe, place in or out of service, and test the item.
[0735] 17. All specialized resources shall provide a basic set of self-test capabilities which are controlled through the standard SNMP or CMIP management interfaces.
[0736] 6. Data Management 2138 Principles
[0737] 1. M4ultiple copies of any data item are allowed.
[0738] 2. Multiple versions of the value of a data item are possible, but one view is considered the master.
[0739] 3. Master versions of a given data item are under a single jurisdiction.
[0740] 4. Multiple users are allowed to simultaneously access the same data.
[0741] 5. Business rules must be applied uniformly across the ISP 2100 to ensure the validity of all data changes.
[0742] 6. Users work on local copies of data; data access is location independent and transparent.
[0743] 7. From the data management point of view, users are applications or other software components.
[0744] 8. Data access should conform to a single set of access methods which is standardized across the ISP 2100.
[0745] 9. Private data is allowed at a local database, but cannot be shared or distributed.
[0746] 10. Only master data can be shared or distributed.
[0747] 11. Private formats for a shared data item are allowed at the local database.
[0748] 12. Transactional capabilities can be relaxed at end-user discretion if allowed within the business rules.
[0749] 13. Rules-based logic and other meta-data controls provide a flexible means to apply policy.
[0750] 14. Data Replication provides reliability through duplication of data sources.
[0751] 15. Database Partitioning provides scalability by decreasing the size of any particular data store, and by decreasing the transaction rate against any particular data store.
[0752] 16. Data Management 2138 must allow both static and dynamic configuration of data resources.
[0753] 17. Common data models and common schemas should be employed.
[0754] 18. Logical application views of data are insulated from physical data operations such as relocation of files, reloading of databases, or reformatting of data stores.
[0755] 19. Audit trails, and event histories, are required for adequate problem resolutions.
[0756] 20. On-line data audits and reconciliation are required to ensure data integrity.
[0757] 21. Data recovery of failed databases is needed in real time.
[0758] 22. Data metrics are needed for monitoring, trending, and control purposes.
[0759] 23. 7 by 24 operation with 99.9999 availability is required.
[0760] 24. Data Management 2138 mechanisms must scale for high levels of growth.
[0761] 25. Data Management 2138 mechanisms must provide cost effective solutions for both large-scale and small-scale deployments.
[0762] 26. Data Management mechanisms must handle overload conditions gracefully.
[0763] 27. Data processing and data synchronization must occur in real-time to meet our business needs.
[0764] 28. Trusted order entry and service creation should work directly on the ISP databases rather than through intermediary applications whenever possible.
[0765] 29. All data must be protected; additionally customer data is private and must retain its confidentiality.
[0766] 30. Configurations, operational settings, and run-time parameters are mastered in the ISP MIB (management information base).
[0767] 31. Wherever possible, off the shelf data solutions should be used to meet Data Management needs.
[0768] The following principles are stated from an Object-oriented view:
[0769] 32. Data items are the lowest set of persistent objects; these objects encapsulate a single data value.
[0770] 33. Data items may have a user defined type.
[0771] 34. Data items may be created and deleted.
[0772] 35. Data items have only a single get and set method.
[0773] 36. The internal value of a data item is constrained by range restrictions and rules.
[0774] 37. Data items in an invalid state should be inaccessible to users.
[0775] 7. Operational Support Principles
[0776] 1. Common View—All ISP 2100 Operational Support User Interfaces should have the same look & feel.
[0777] 2. Functional Commonality—The management of an object is represented in the same manner throughout the ISP Operational support environment.
[0778] 3. Single View—A distributed managed object has a single representation at the ISP Operational Support User Interfaces, and the distribution is automatic.
[0779] 4. OS/DM Domain—Data within the Operational support domain should be managed with the ISP Data Management 2138 Mechanisms.
[0780] 5. Global MIB—There is a logical Global MIB which represents resources in the entire ISP.
[0781] 6. External MIBs—Embedded MIBs that are part of a managed component are outside of Operational Support and Data Management. Such MIBs will be represented to the OS by a Mediation Device.
[0782] 7. System Conformance—System conformance to the ISP OS standards will be gained through Mediation Layers.
[0783] 8. Operational Functions—Operational personnel handle the Network Layer & Element Management for physical & logical resources.
[0784] 9. Administration Functions—Administration personnel handle the Planning & Service Management.
[0785] 10. Profile Domain—Service & customer profile data bases are managed by administration personnel under the domain of the Data Management system.
[0786] 11. Telecommunication Management Network (TMN) compliance - TMN compliance will be achieved through a gateway to any TMN system.
[0787] 12. Concurrent—Multiple Operators &, Administrators must be able to simultaneously perform operations from the ISP OS Interfaces.
[0788] 8. Physical Model Principles
[0789] 1. Compatibility: The physical network model provides backward compatibility for existing telecommunications hardware and software.
[0790] 2. Scaleable: The physical network model is scaleable to accommodate a wide range of customer populations and service requirements.
[0791] 3. Redundant: The physical network model provides multiple paths of information flow across two network elements. Single points of failure are eliminated.
[0792] 4. Transparent: Network elements are transparent to the underlying network redundancy. In case of a failure, the switchover to redundant links is automatic.
[0793] 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.
[0794] 6. Interoperable: The physical network model allows networks with different characteristics to interoperate with different network elements.
[0795] 7. Secure: The physical network model requires and provides secure transmission of information. It also has capabilities to ensure secure access to network elements.
[0796] 8. Monitoring: 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.
[0797] 9. Partitionable: The physical network model is (logically) partitionable to form separate administrative domains.
[0798] 10. 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.
[0799] 11. Universal Access: 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.
[0800] 12. Regulatory awareness: The physical network model is amenable at all levels to allow for sudden changes in the regulatory atmosphere.
[0801] 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.
[0802] H. ISP Seruvce Model
[0803] This section describes the Service model of the Intelligent Services Platform Architecture Framework.
[0804] 1. Purpose
[0805] The ISP Service Model establishes a framework for service development which supports:
[0806] rapid service creation and deployment;
[0807] efficient service execution;
[0808] complete customization control over services for customers;
[0809] total service integration for a seamless service view for customers;
[0810] improved reuse of ISP capabilities through loose coupling of those capabilities;
[0811] reduced cost of service implementation; and
[0812] vendor-independence.
[0813] 2. Scope of Effort
[0814] The ISP Service Model supports all activities associated with Services, including the following aspects:
[0815] provisioning;
[0816] creation;
[0817] deployment;
[0818] ordering;
[0819] updating;
[0820] monitoring;
[0821] execution;
[0822] testing or simulation;
[0823] customer support and troubleshooting;
[0824] billing;
[0825] trouble ticket handling; and
[0826] operations support.
[0827] This model covers both marketable services and management services.
[0828] Marketable services are the services purchased by our customers
[0829] Management services are part of the operation of the MCI network, and are not sold to customers.
[0830] The Service Model also defines interactions with other parts of the ISP Architecture, including Data Management, Resource Management, and Operational Support.
[0831] 3. Service Model Overview
[0832] Central to the Intelligent Services Platform is the delivery of Services 2200 (FIG. 24). 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.
[0833] One of the major differences between a Service 2200 and an Application 2176 or 2178 (FIG. 22) is that 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.
[0834] 4. Service Structure
[0835] The vocabulary we will use for describing services includes the services themselves, service features, and capabilities. These are structured in a three-tier hierarchy as shown in FIG. 24.
[0836] 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.
[0837] Service features 2202, in turn, 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.
[0838] a) Services 2200
[0839] Services 2200 are described by "service logic," which is basically a program written in a very high-level programming language or described using a graphical user interface. These service logic programs identify:
[0840] what service features 2202 are used;
[0841] the order in which service features are invoked;
[0842] the source of input service data;
[0843] the destination for output service data;
[0844] error values and error handling;
[0845] invocation of other services 2200;
[0846] interaction with other services; and
[0847] the interactions with other services;
[0848] The service logic itself is generally not enough to execute a service 2200 in the network. Usually, 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. Both Management and Marketable Services are part of the same service model. The similarities between Management and Marketable Services allow capabilities to be shared. Also, Management and Marketable Services represent two viewpoints of the same network: Management Services represent an 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.
[0849] 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.
[0850] b) Service Features 2202
[0851] 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 FIG. 25.
[0852] Some examples of service features are:
[0853] 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.
[0854] 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.
[0855] 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.
[0856] c) Capabilities 2204
[0857] 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.
[0858] Some examples of network-based capability objects are:
[0859] voice (for recording or playback),
[0860] call (for bridging, transferring, forwarding, dial-out, etc),
[0861] DTMF (for collection or outpulsing), and
[0862] Fax (for receive, send, or broadcast).
[0863] 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:
[0864] calendar (to determine what day of the week or month it is),
[0865] comparison (to compare strings of digits or characters),
[0866] translation (to translate data types to alternate formats), and
[0867] distribution (to choose a result based on a percentage distribution).
[0868] d) Service Data
[0869] There are three sources for data while a service executes:
[0870] Static Data defined in the service template, which include default values for a given service invocation.
[0871] Interactive Data obtained as the service executes, which may be explicit user inputs or derived from the underlying network connections.
[0872] Custom Data defined in User Profiles, which is defined by customers or their representatives when the service is requested (i.e. at creation time).
[0873] 5. Service 2200 Execution
[0874] Services 2200 execute in Service Logic Execution Environments (SLEEs). A SLEE is executable software which allows any of the services deployed into the ISP 2100 to be executed. In the ISP Architecture, Service Engines 2134 (FIG. 21) provide these execution environments. Service Engines 2134 simply execute the services 2200 that are deployed to them.
[0875] Service templates and their supporting profiles are deployed onto database servers 2182 (FIG. 22). 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.
[0876] In most cases a service 2200 will first invoke a service feature 2202 (FIG. 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 (FIG. 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.
[0877] During service 2200 execution, profile data is used to determine the behavior of service features 2202. Depending on service performance requirements, 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. As the service executes, information may be 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.
[0878] 6. Service Interactions
[0879] In the course of a network transaction, more than one service can be invoked by the network. Sometimes, the instructions of one service may conflict with the instructions of another service. Here's an example of such a conflict: a 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.
[0880] 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 FIG. 26):
[0881] Transfer of Control 2210: where a service has completed its execution path and transfers control to another service;
[0882] Synchronous Interaction 2212: where a service invokes another service and waits for a reply;
[0883] Asynchronous Interaction 2214: where a service invokes another service, performs some other actions, then waits for the other service to complete and reply; or
[0884] One Way Interaction 2216: where a service invokes another service but does not wait for a reply.
[0885] In the example of interacting VNET services above, the terminating VNET service could have queried the originating VNET service using the synchronous service interaction capability. The interesting twist to this idea is that 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.
[0886] 7. Service Monitoring
[0887] Services 2200 must be monitored from both the customer's viewpoint and the network viewpoint. Monitoring follows one of two forms:
[0888] The service 2200 can generate detailed event-by-event information for delivery to the transaction context database
[0889] The service can generate statistical information for delivery periodically to a statistics database, or for retrieval on demand by a statistics database.
[0890] Analysis services can use the Statistics Database or the Context Database to perform real time or near real time data analysis services.
[0891] 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.
[0892] I ISP Data Management Model
[0893] This section describes the Data Management 2138 aspects of the Intelligent Services Platform (ISP) 2100 Target Architecture.
[0894] 1. Scope
[0895] 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.
[0896] 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.
[0897] 2. Purpose
[0898] The objectives of this architecture are to:
[0899] Create a common ISP functional model for managing data;
[0900] Separate data from applications;
[0901] Establish patterns for the design of data systems;
[0902] Provide rules for systems deployment;
[0903] Guide future technology selections; and
[0904] Reduce redundant developments and redundant data storage.
[0905] Additional goals of the target architecture are:
[0906] Ensure data flexibility;
[0907] Facilitate data sharing;
[0908] Institute ISP-wide data control and integrity;
[0909] Establish data security and protection;
[0910] Enable data access and use;
[0911] Provide high data performance and reliability;
[0912] Implement data partitioning; and
[0913] Achieve operational simplicity.
[0914] 3. Data management Overview
[0915] In one embodiment, the Data Management Architecture is a framework describing the various system components, how the systems interact, and the expected behaviors of each component. In this embodiment 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. A key difference in this embodiment is that the user (or end-point) dictates what data is downloaded or stored locally.
[0916] a) Domains
[0917] Data and data access are characterized by two domains 2220 and 2222, as shown in FIG. 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.
[0918] 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.
[0919] b) Partitions
[0920] In general, 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.
[0921] c) Architecture
[0922] The architecture is that of distributed databases and distributed data access with the following functionality:
[0923] Replication and Synchronization;
[0924] Partitioning of Data Files;
[0925] Concurrency Controls;
[0926] Transactional Capability; and
[0927] Shared common Schemas.
[0928]FIG. 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 FIG. 28 are:
[0929] NETWK 2224—external access to the ISP 2100 from the network side;
[0930] SVC I/F 2226—the network interface into ISP;
[0931] SYSTMS 2228—external application such as Order Entry;
[0932] G/W 2230—a gateway to the ISP 2100 for external applications;
[0933] dbAppl 2232—a role requiring data access or update capabilities;
[0934] dbClient 2234—the primary role of the satellite domain;
[0935] dbServer 2236—the primary role of the central domain;
[0936] dbAdmin 2238—an administrative role for Data;
[0937] dbMon 2240—a monitoring role;
[0938] I/F Admin 2242 administrative role for interfaces; and
[0939] Ops 2244—operations console.
[0940] d) Information Flow
[0941] The flows depicted in FIG. 28 are logical abstractions; they are intended to characterize the type of information passing between the logical components.
[0942] Thc flows shown above are:
[0943] Reqst—data requests to the ISP from external systems;
[0944] Resp—responses from the ISP to external requests;
[0945] Access—data retrieval by applications within the ISP;
[0946] Updates—data updates from applications within ISP;
[0947] Evts—data related events sent to the monitor;
[0948] Meas—data related metrics sent to the monitor;
[0949] New Data—additions to ISP master data;
[0950] Changed Data—changes to ISP master data;
[0951] Views—retrieving ISP master data;
[0952] Subscriptions—asynchronous stream of ISP master data;
[0953] Cache copies—a snapshot copy of ISP master data;
[0954] Actions—any control activity; and
[0955] Controls any control data.
[0956] e) Domain Associations
[0957] In general the Satellite domains 2222 of Data Management 2138 encompass:
[0958] ISP Applications;
[0959] External systems;
[0960] Network interfaces 2226 and system gateways 2230; and
[0961] Database client (dbClient) 2234.
[0962] The Central domain for Data Management 2138 encompasses:
[0963] Monitoring (dbMon) 2240;
[0964] Administration (dbAdmin) 2238; and
[0965] Database masters (dbServer) 2236
[0966] 4. Logical Description
[0967] The behavior of each Architecture component is described separately below:
[0968] a) Data Applications (dbAppl) 2232
[0969] This includes any 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:
[0970] Updates: allow an application to insert, update, or delete data in an ISP database.
[0971] 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.
[0972] Events and Measurements are special forms of updates which are directed to the monitoring function (dbMon) 2240.
[0973] b) Data Management 2138
[0974] (1) Client Databases (dbclient) 2234
[0975] 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.
[0976] 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.
[0977] 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.
[0978] Only changes made to the dbServer master copies are forwarded to other dbClients.
[0979] 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.
[0980] The dbClient 2234 offers the following interface operations:
[0981] Attach by an authorized application to a specified set of data;
[0982] Policy preferences to be set by an authorized application;
[0983] Select a specified view of the local copy of data;
[0984] Insert, Update, or Delete of the local copy of data;
[0985] Synchronize subscripted data with the dbServer; and
[0986] Expiration notifications from dbServer for cached data.
[0987] Additionally, the dbClients submit Logs or Reports and signal problems Lo the monitor (dbMon) 2240.
[0988] (2) Data Masters (dbServer) 2236
[0989] 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.
[0990] These copies are synchronized in lock-step. That is each update is required to obtain a corresponding master-lock in order to prevent update conflicts. The strict implementation policies may vary, but in general, all master copies must preserve serial ordering of updates, and provide the same view of data and same integrity enforcement as any other master copy. The internal copies of date are transparent to the dbClients 2234.
[0991] 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.
[0992] 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.
[0993] The dbServer also provides security checks and authorizations, and ensures that selected items are encrypted before storage. The dbServer supports the following interface operations:
[0994] View selected data from dbServer;
[0995] Subscribe to selected data from dbServer;
[0996] Copy selected data into a cache-copy at a dbClient 2234;
[0997] Refresh a dbClient cache with the current copy on demand;
[0998] New data insertion across all dbServer copies of the master;
[0999] Change data attributes across all dbServer copies; and
[1000] Cancel previous subscriptions and drop cache-copies of data.
[1001] (3) Data Administration (dbAdmin) 2238
[1002] Data Administration (dbAdmin) 2238 involves setting data policy, managing the logical and physical aspect of the databases, and securing 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.
[1003] The dbAdmin 2238 supports the following interface operations:
[1004] Define the characteristics of a data type;
[1005] Create logical containers of given dimensions;
[1006] Relate two or more containers through an association;
[1007] Constrain data values or relations through conditional triggers and actions;
[1008] Place physical container for data in a given location;
[1009] Move physical containers for data to new locations;
[1010] Remove physical containers and their data;
[1011] Load data from one container to another;
[1012] Clear the data contents of a container; and
[1013] Verify or reconcile the data contents of a container.
[1014] (4) Data Monitoring (dbMon) 2240
[1015] 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.
[1016] 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.
[1017] The rate and count of various metrics are used for evaluating quality of Service (QOS) , data performance, and 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:
[1018] Setting monitor controls, filters, and thresholds;
[1019] Logging of data related activity;
[1020] Reports of status, metrics, or audit results; and
[1021] Signaling alarms, or alerts.
[1022] (5) Data Management operations (Ops) 2244
[1023] 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.
[1024] 5. Physical Description
[1025] This section describes the Data Management 2138 physical architecture. It describes how a set of components could be deployed. A generalized deployment view is shown in FIG. 29. In FIG. 29:
[1026] circles are used to represent physical sites,
[1027] boxes or combined boxes are computer nodes, and
[1028] functional roles are indicated by abbreviations.
[1029] The abbreviations used in FIG. 29 are:
[1030] OE—order entry systems 2250;
[1031] GW—ISP gateway 2230;
[1032] APP—application (dbAppl) 2232;
[1033] CL—a dbClient 2234;
[1034] SVR—a dbServer 2236;
[1035] ADM—a dbAdmin component 2238;
[1036] MON—a dbMon component 2240; and
[1037] Ops—operations console.
[1038] The functional roles of these elements were described above (see Logical Description of the Target Architecture) in connection with FIG. 28.
[1039] Each of the sites shown in FIG. 29 is typically linked with one or more of the other sites by wide area network (WAN) links. 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.
[1040] On the network-side of the ISP 2100, Satellite sites 2252 each contain the dbClient 2234 too. These sites typically operate local area networks (LANs). The dbClients act as local repositories for network or system applications such as the ISN operator consoles, ARUs, or NCS switch requested translations.
[1041] 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.
[1042] 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.
[1043] 6. Technology Selection
[1044] The following section describes the various technology options which should be considered. The Data Management 2138 architecture does not require any particular technology to operate; however different technology choices will impact the resulting performance of the system.
[1045]FIG. 30 depicts a set of technologies which are able to provide a very-high perfornitance environment. Specific application requirements will determine the minimum level of acceptable performance. Three general environments are shown.
[1046] In the upper part, 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.
[1047] In the center are large-scale high-performance machines 2262 with large data-storage devices; these would be typical of master databases and data processing, and data capture/tracking functions such as dbServer 2236 and dbMon 2240.
[1048] In the lower part of the diagram are local area processing and network interfaces 2264, such as the ISN operator centers or DAP sites.
[1049] 7. Implementations
[1050] While much is known of the current ISP data systems, additional detailed requirements are necessary before any final implementations are decided. These requirements must encompass existing ISN, NCS, EVS, NIA, and TMN system needs, plus all of the new products envisioned for Broadband, Internet, and Switchless applications.
[1051] 8. Security
[1052] 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.
[1053] 9. Meta-Data
[1054] 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.
[1055] 10. Standard Database Technologies
[1056] Implementation of the proposed Data Management Architecture should take advantage of commercially available products whenever possible. Vendors offer database technology, replication services, Rules systems, Monitoring facilities, Console environments, and many other attractive offerings.
[1057] J. ISP Resource Management Model
[1058] This section describes the Resource Management 2150 Model as it relates to the ISP 2100 Architecture.
[1059] a) Scope
[1060] 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.
[1061] b) Purpose
[1062] 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.
[1063] c) Objectives
[1064] In the existing traditional ISP architecture, services control and manage their own physical and logical resources. Migration to an architecture that abstracts resources from services requires defining a management functionality that governs the relationships and interactions between resources and services. This functionality is represented by the Resource Management 2150 Model. 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:
[1065] Abstract resources from services;
[1066] Provide real-time access to resource status;
[1067] Simplify the process of adding and removing resources;
[1068] Provide secure and simple resource access; and
[1069] Provide fair resource acquisition, so that no one user of resources may monopolize the use of resources.
[1070] d) Background Concepts
[1071] Generally, the Resource Management 2150 Model governs the relationships and interactions between the resources and the processes that utilize them. Before the model is presented, a solid understanding of the basic terminology and concepts used to explain the model should be established. The following list presents these terms and concepts:
[1072] (1) Definitions
[1073] 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.
[1074] Resource Pool: A set of registered resource members that share common capabilities.
[1075] Service: A logical description of all activities and the interaction flow between the user of the network resources and the resources themselves.
[1076] Policy: A set of rules that governs the actions taken on resource allocation and de-allocation, resource pool size thresholds and resource utilization thresholds.
[1077] (2) Concepts
[1078] 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:
[1079] Resource Requisition is the phase in which a process requests a resource from the Resource Manager 2150.
[1080] Resource Acquisition: If the requested resource is available and the requesting process has the privilege to request it, the 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.
[1081] Resource Release: The allocated resource should be put back inito 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.
[1082] The Resource Management Model allows for the creation of resource pools and the specification of the policies governing them. The Resource Management Model allows resources to register and de-register as legitimate members of resource pools.
[1083] 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.
[1084] The Resource Management Model adopted the OSI Object Oriented approach for modeling resources. Under this model, each resource is represented by a Managed Object (MO). Each MO is defined in terms of the following aspects:
[1085] Attributes: The attributes of a MO represent its properties and are used to describe its characteristics and current states. Each attribute is associated with a value, for example the value CURRENT_STATE attribute of a MO could be IDLE.
[1086] Operations: Each MO has a set of operations that are allowed to be performed on it. These operations are:
[1087] Create: to create a new MO
[1088] Delete: to delete an existing MO
[1089] Action: to perform a specific operation such as SHUTDOWN.
[1090] Get Value: to obtain a specific MO attribute value
[1091] Add Value: to add specific MO attribute value
[1092] Remove Value: to delete a specific MO attribute value from a set of values.
[1093] Replace Value: to replace an existing MO attribute value(s) with a new one.
[1094] Set Value: to set a specific MO attribute to its default value.
[1095] Notification: Each MO can report or notify its status to the management entity. This could be viewed as triggers or traps.
[1096] 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.
[1097] All elements that need to utilize, manipulate or monitor a resource need to treat it as a MO and need to access it through the operations defined above. Concerned elements that need to know the status of a resource need to know how to receive and react to events generated by that resource.
[1098] Global and Local Resource Management:
[1099] 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.
[1100] 2. The Local Resource Manager (LRM):
[1101] Domain: 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.
[1102] Function: The main functionality of the LRM is to facilitate the resource allocation and de-allocation process between a process and a resource according to the Resource Management Model guidelines.
[1103] 3. The Global Resource Manager (GRM) 2188:
[1104] Domain: The domain of the GRM 2188 covers all registered resources in all resource pools across the network.
[1105] Function: The main function of the GRM is to help the LRM 2190 locate a resource that is not available in the LRM domain.
[1106]FIG. 31 illustrates the domains of the GRM 2188 and LRM 2190 within network 2270.
[1107] 4. The Resource Management Model (RMM)
[1108] 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. On the other hand, 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.
[1109] 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.
[1110] a) Simple Resource Management Model
[1111] Realizing that resource allocation and de-allocation could involve a complex process, a simple form of this process is presented here as an introduction to the actual model. Simple resource allocation and de-allocation is achieved through six steps. FIG. 32 depicts these steps.
[1112] 1. A process 2271 requests the resource 2273 from the resource manager 2150.
[1113] 2. The resource manager 2150 allocates the resource 2273.
[1114] 3. The resource manager 2150 grants the allocated resource 2273 to the requesting process 2271.
[1115] 4. The process 2271 interacts with the resource 2273.
[1116] 5. When the process 2271 is finished with the resource 2273, it informs the resource.
[1117] 6. The resource 2273 releases itself back to the resource manager 2150.
[1118] b) The Resource Management Model Logical Elements:
[1119] 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 FIG. 33 and include: Resource Pool (RP) 2272, LRM 2190, GRM 2188 and Resource Management Information Base (RMIB) 2274.
[1120] (1) Resource Pool (RP) 2272
[1121] 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.
[1122] (2) The Local Resource Manager (LRM) 2190
[1123] 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.
[1124] (3) The Global Resource Manager (GRM) 2188
[1125] 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.
[1126] (4) The Resource Management Information Base (RMIB) 2274
[1127] As mentioned above, all resources will be treated as managed objects (MO). 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.
[1128] 5. Component Interactions
[1129] 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.
[1130] a) Entity Relationship (ER) Diagram (FIG. 33):
[1131] In FIG. 33, each rectangle represents one entity, the verb between the "<>a implies the relationship between two entities and 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-1, 1-to-many or many-to-many. FIG. 33 can be read as follows:
[1132] 1. One LRM 2190 manages one RP 2272.
[1133] 2. Many LRMs 2190 access the RMIB 2274.
[1134] 3. Many LRMs 2190 access the GRMs 2188.
[1135] 4. Many GRMs 2188 access the RMIB 2274.
[1136] b) Registration and De-registration
[1137] 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.
[1138] 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:
[1139] All resources must register to their LRM 2190 as members of a specific resource pool 2272.
[1140] All resources must de-register from their LRM 2190 if, for any reason, they need to shutdown or be taken out of service.
[1141] All resources must report their availability status to their LRM 2190.
[1142] All LRMs must update the GRM 2188 with the latest resource availability based on the registered and de-registered resources.
[1143] c) GRM, LRM and RP Interactions
[1144] 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. When the process needs a resource it must request it through its assigned LRM. When the LRM receives a request for a resource, two cases may occur:
[1145] 1. 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.
[1146] 2. Resource is not available: In this case, 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:
[1147] give up and try again,
[1148] request that the LRM allocate the resource whenever it becomes available, or
[1149] request that the LRM allocates the resource if it becomes available within a specified period of time.
[1150] If an external resource is available, the GRM 2188 passes location and access information to the LRM 2190. Then the LRM either:
[1151] allocates the resource on the behalf of the requesting process and passes a resource handle to it (In this case the resource allocation through the GRM is transparent to the process), or
[1152] advises the requesting process to contact the LRM that manages the located resource.
[1153] d) GRM, LRM and RMIB Interactions
[1154] 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 2274 that maps to the RP 2272 it manages. The GRM 2188, on the other hand, 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.
[1155] In order for the RMIB 2274 to keep accurate resource information, each LRM 2190 must update the RMIB with the latest resource status. This includes adding resources, removing resources and updating resource states.
[1156] 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.
[1157] K. Operational Support Model
[1158] 1. Introduction
[1159] Most of the existing ISP service platforms were developed independently, each with it's own set of Operational Support features. The amount of time required to learn how to operate a given set of platforms increases with the number of platforms. The ISP service platforms need to migrate to an architecture with a common model for all of its Operational Support features across all of its products. This requires defining a model that M"ill support current needs and will withstand or bend to the changes that will occur in the future. The Operational Support Model (OSM) defines a framework for implementation of management support for the ISP 2100.
[1160] a) Purpose
[1161] The purpose of the Operational Support Model is to:
[1162] achieve operational simplicity by integrating the management platform for ISP resources;
[1163] reduce the learning curve for operational personnel by providing a common management infrastructure;
[1164] reduce the cost of management systems by reducing overlapping management system development;
[1165] improve time to market for ISP services by providing a common management infrastructure for all of the ISP services and network elements; and
[1166] provide a framework for managing ISP physical resources (hardware) and logical resources (software).
[1167] b) Scope
[1168] 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. However, the architecture presented here will help map utilization and faults on physical resources to their resulting impact on services.
[1169] The management services occur within four layers
[1170] Planning,
[1171] Service Management,
[1172] Network Layers, and
[1173] Network Elements.
[1174] Information within the layers falls into four functional areas:
[1175] Configuration Management,
[1176] Fault Management,
[1177] Resource Measurement, and
[1178] Accounting.
[1179] The use of a common Operational Support Model for all of the ISP will enhance the operation of the ISP, and simplify the designs of future products and services within the ISP. This operational support architecture is consistent with the ITU Telecommunications Management Network (TMN) standards.
[1180] c) Definitions
[1181] 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).
[1182] Managed System: One or more managed objects.
[1183] Management Sub-Domain: A Management domain that is wholly located within a parent management domain.
[1184] 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.
[1185] Management Domain: A collection of one or more management systems, and zero or more managed systems and management sub—domains.
[1186] Network Element: 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, Hubs, X.25 links, SS7 links, etc. When managed, such equipment is generally referred to as a network element (NE).
[1187] Domain: The management environment may be partitioned in a number of ways such as functionally (fault, service . . . ), geographical, organizational structure, etc.
[1188] Operations Systems: The management functions are resident in the Operations System.
[1189] 2. The Operational Support Model
[1190]FIG. 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 four 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.
[1191] a) The Functional Model
[1192] The following sections describe the functional areas as they occur within the management layers 2300-2306.
[1193] (1) Planning
[1194] The JSP Planning Layer 2300 is the repository for data collected about the ISP 2100, and the place where that data is to provide additional value.
[1195] Configuration Management 2312: Setting of policy, and goals.
[1196] Fault Management 2314: Predicting of mean time to failure.
[1197] Resource Measurement 2316: Predicting future resource needs (trending, capacity, service agreement compliance, maintenance agreement, work force).
[1198] Accounting 2318: Determine cost of providing services in order to support service pricing decisions.
[1199] (2) Service Management
[1200] 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.
[1201] 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.
[1202] Fault Management 2322: Monitor and report violations of service agreement. Testing.
[1203] Resource Measurement 2324: Predict the violation of a service agreement and flag potential resource shortages. Predict the needs of current and future (trending) services.
[1204] Accounting 2326: Process and forward Accounting information.
[1205] Network Layer Management:
[1206] 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 with other managers in the NLM layer. In that case there are manager agent relationships at the peer level.
[1207] Configuration Management 2328 provides functions to define the characteristics of the local and remote resources and services from a network wide perspective.
[1208] Fault Management 2330 provides functions to detect, report, isolate, and correct faults that occur across multiple NEs.
[1209] Resource Measurement 2332 provides for the network wide measurement, analysis, and reporting of resource utilization from a capacity perspective.
[1210] Accounting 2334 consolidates Accounting information from multiple sources.
[1211] (3) Element Management
[1212] 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.
[1213] 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.
[1214] b) Network Element
[1215] The computers, processes, switches, VRUs, internet gateways, and other equipment that provide the network capabilities are Network Elements 2310. NEs provide agents to perform operations on the behalf of the Element Management Layer 2306.
[1216] c) Information Model
[1217]FIG. 35 shows manager agent interaction. 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. For the purpose of this exchange of information 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 Lhe 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.
[1218] 3. The Protocol Model
[1219] a) Protocols
[1220] The exchange of information between manager and agent relies on a set of communications protocols. TMN, which offers a good model, uses the Common Management Information Services (CMIS) and Common Management Information Protocol (CMIP) as defined in Recoirmendations X.710, and X.711. 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.811. Recommendation X.811 also describes the interworking between different lower layer protocols. This set of protocols is referred to as Q3.
[1221] b) Common context
[1222] In order to share information between processes there needs to be a common understanding of the interpretation of the information exchanged. ASN. 1 (X.209) with BER could be used to develop this common understanding for all PDU exchanged between the management processes (manager/agent).
[1223] c) Services of the upper layer
[1224] 4. The Physical Model
[1225]FIG. 36 shows the ISP 2100 physical model.
[1226] 5. Interface Points
[1227] 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. FIG. 36 identifies nine interface points. The protocols associated with those interface points are:
[1228] 1. There are two upper layer protocols. 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.
[1229] 2. The upper layer is the protocol for communications with workstation 2364, and the lower layer is TCP/IP over Ethernet.
[1230] 3,4. The upper layer is the ISP upper layer, and the lower layer is TCP/IP over Ethernet.
[1231] 5. The proprietary protocols are those 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.
[1232] 6,7,8,9. Gateways by their nature will support ISP compliant and non-compliant interfaces. Gateways to enterprise internal systems could include gateways such as the Order Entry system, or an enterprise wide TMN system.
[1233] The ISP Realization of the Operational Support Model
[1234]FIG. 37 shows operational support realization.
[1235] 6. General
[1236] The Operational Support Model provides a conceptual framework for building the Operational Support System. 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.
[1237] Field support personnel have two levels from which the ISP 2100 will be managed.
[1238] 1. For trouble-shooting, 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.
[1239] For configuration the Network Layers Manager 2372 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.
[1240] Once a service definition has been created from the Service Creation Environment, the Service Manager 2378 is used to place it in the ISP network, and provision the network for the new service. Customers for a service are provisioned through the Service Manager 2378. As a part of provisioning customers the Service Manager predicts resource utilization, and determines if new resources need to be added to handle the customer's use of a service. It uses the current utilization statistics as a basis for that determination. Once a customer is activated, the Service Manager monitors the customer's usage of the service to determine if the quality of service agreement is being met. As customer utilization of the services increases the Service Manager 2378 predicts the need to add resources to the ISP network. This Service Management, with appropriate restrictions, can be extended to customers as another service. While Service Creation is the talk of the IN world, it needs a Service Manager that is integrated with the rest of the system, and that is one of the purposes of this model.
[1241] Finally, for planning personnel (non-field support), the Planning Manager 2380 analyzes the ISP-wide resource utilization to determine future needs, and to allocate cost to different services to determine the cost of a service as the basis for future service pricing.
[1242] L. Physical Network Model
[1243] 1. Introduction
[1244] This section describes the Physical Network aspects of the Intelligent Services Platform (ISP) 2100 Architecture.
[1245] a) Purpose
[1246] The Physical Network Model covers the:
[1247] Logical Architecture Mapping;
[1248] Information Flows; and
[1249] Platform Deployment in the production environment of the architecture.
[1250] b) Scope
[1251] This model defines the terminology associated with the physical network, describes the interactions between various domains and provides examples of realizations of the architecture.
[1252] c) Objectives
[1253] The objectives of this model are to:
[1254] Create a model for identifying various network platforms;
[1255] Classify Information Flow;
[1256] Provide standard nomenclature;
[1257] Provide rules for systems deployment; and
[1258] Guide future technology selections.
[1259] 2. Information Flow
[1260] One of the key aspects of the intelligent network (IN) is the Information Flow across various platforms installed in the network. By identifying types of information and classifying them, the network serves the needs of IN.
[1261] Customers interact with IN in a series of call flows. Calls may be audio-centric (as in the conventional ISP products), multimedia- based (as in internetMCI user using the web browser), video-based (as in video-on-demand) or a combination of contents.
[1262] Information can be classified as follows:
[1263] Content;
[1264] Signaling; or
[1265] Data.
[1266] Normally, a customer interacting with the intelligent network will require all three types of information flows.
[1267] a) Content
[1268] Content flows contain the primary information being transported. Examples of this are analog voice, packet switched data, streamed video and leased line traffic. This is customer's property that IN must deliver with minimum loss, minimum latency and optimal cost. The IN elements are standardized such that the transport fabric supports more connectivity suites, in order to allow content to flow in the same channels with flow of other information.
[1269] b) Signaling
[1270] Signaling flows contain control information used by network elements. ISUP RLT/IMT, TCP/IP domain name lookups and ISDN Q.931 are all instances of this. The IN requires, uses and generates this information. Signaling information coordinates the various network platforms and allows intelligent call flow across the network. In fact, in a SCE-based IN, service deployment will also require signaling information flowing across the fabric.
[1271] c) Data
[1272] Data flows contain information produced by a call flow, including crucial billing data records often produced by the fabric and certain network platforms.
[1273] 3. Terminology
[1274] Network: A set of interconnected network elements capable of transporting content, signaling and/or data. MCI's IXC switch fabric, the ISP extended WAN, and the Internet backbone are classic examples of networks. Current installations tend to carry different contents on different networks, each of which is specialized for specific content transmission. Both technology and customer requirements (for on-demand high bandwidth) will require carriers to use more unified networks for the majority of the traffic. This will require the fabric to allow for different content characteristics and protocols along the same channels. Another aspect of this will be more uniform content-independent signaling.
[1275] Site: A set of physical elitities collocated in a geographically local area. In the current ISP architecture, instances of sites are Operator Center, ISNAP Site (which also has ARU's) and an EVS site. By the very definition, the NT and DSC switches are NOT part of the site. They are instead part of the Transport Network (see below). In the architecture, a group of (geographically collocated) Service Engines (SE), Special Resources (SR), Data Servers (DS) along with Network Interfaces and Links form a site.
[1276] Network Element: A physical entity connecting to the Transport Networks through Network Interfaces. Examples of this are ACP, EVS SIP, MTOC, Videoconference Reservation Server, DAP Transaction Server, and NAS. In the next few years, elements such as web servers, voice authentication servers, video streamers and network call record stores will join the present family of network elements.
[1277] Network Interface: Equipment enabling connectivity of Network Elements to the Transport Networks. DS1 CSU/DSU, 10 BaseT Ethernet interface card and ACD ports are network interfaces. With the architecture of the preferred embodiment, network interfaces will provide a well-understood uniform set of API's for communication.
[1278] Link: Connection between 2 or more Network Interfaces which are at different sites. A link may be a segment of OC-12 SONET Fiber or 100 mbps dual ring FDDI section. In the coming years, IN must handle network links such as ISO Ethernet WAN hub links and gigabit rate OC-48's.
[1279] Connection: an attachment of two or more Network Interfaces which are at the same site.
[1280]FIG. 38 shows a representation of a physical network 2400 schematic. Networks 2401 contain network elements 2402 at sites 2404 are interconnected through network interfaces 2406 and one or more gateways 2408.
[1281] 4. Entity Relationships
[1282] Entity relationships as shown in FIG. 39 have been arrived at as part of the physical network modeling rules. Some of these rules allow for generalities that future demands and some will constrain definitions to avoid conflicts.
[1283] 1. A Network 2401 spans one or more sites 2404, and contains one or more network elements 2402.
[1284] 2. A Site 2404 contains one or more network elements 2402.
[1285] 3. A Network Element 2402 is located in only one Site 2404.
[1286] 4. A Link 2420 connects two or more Sites 2404.
[1287] 5. A Connection 2422 connects two or more Network Elements.
[1288] 6. A Network Element 2402 contains one or more Network Interfaces 2406.
[1289] The preferred embodiment integrates product anid service offerings for MCI's business customers. The initial embodiment focuses on a limited product set. Requirements for an interface have been identified to capitalize on the integration of these services. The interface provides user-manageability of features, distribution list capabilities, and a centralized message database.
[1291] All of the platform's support services have been consolidated onto one platform. The consolidation of platforms enables shared feature/functionality of services to create a common look and feel of features.
[1292] A. Network Management
[1293] The architecture is designed such that it can be remotely monitored by an MCI operations support group. This remote monitoring capability provides MCI the ability to:
[1294] Identify degraded or broken connectivity between:
[1295] platforms, servers or nodes that must pass information (i.e., objects) to the "universal inbox",
[1296] platforms, servers or nodes responsible for retrieving messages and delivering messages,
[1297] the "universal inbox" and the PC Client messaging interface,
[1298] the "universal inbox" and the Message Center interface,
[1299] platforms, servers or nodes that must pass profile information to Profile, and
[1300] platforms, servers or nodes that must pass profile information to the ARU;
[1301] a Identify degraded application processes and isolate the process that is degraded;
[1302] Identify hardware failure; and
[1303] Generate alarms that can be detected and received by an internal MCI monitoring group for all application process, hardware or interface failures.
[1304] In addition, remote access to system architecture components is provided to the remote monitoring and support group such that they can perform remote diagnostics to isolate the cause of the problem.
[1305] B. Customer Service
[1306] Customer Service teams support all services. Customer support is provided to customers in a seamless manner and encompasses the complete product life cycle including:
[1307] Alpha tests;
[1308] Beta tests;
[1309] Commercial release; and
[1310] Identification of enhancements to address customer feedback or additional customer support requirements
[1311] Comprehensive and coordinated support procedures ensure complete customer support from inception to termination. Customer service is provided from the time the Account Team submits the order until the customer cancels the account. Comprehensive and coordinated customer support entails the following:
[1312] A one-stop, direct access, customer service group to support ARU or VRU problems, WWW Browser problems or PC Client problems.
[1313] A staff that is well trained on diagnosing problems associated with access (ARU, WWW Browser or PC Client), the user interface (ARU, WWW Browser or PC Client), the application (Message Center or Profile Management) or the back-end system interfaces (universal inbox, directlineMCI voicemail/faxmail platform, Fax Broadcast System, SkyTel Paging server, order entry systems, billing systems, etc.)
[1314] A staff that has on-line access to databases with information about ARU or VRU capabilities, WWW Browser capabilities, identified hardware issues and identified application issues
[1315] 7�24 customer support
[1316] a single toll free number (800 or 888) with direct access to the customer service group
[1317] seamless first, second and third level support for most troubles where:
[1318] Level 1 support is the first support representative answering the telephone. They are expected to be able to resolve the most commonly asked questions or problems reported by customers. These questions or problems typically deal with access type (ARU, WWW Browser, PC Client), dial-up communication for the WWW Browser or PC Client, installation or basic computer (PC, workstation, terminal) hardware questions. Additionally they are able to open and update trouble tickets, and reactivate customers' passwords.
[1319] Level 2 support is provided within the customer support group when referrals to more experienced technical experts is necessary.
[1320] Level 3 support may involve an outside vendor for on-site hardware support for the customer or an internal MCI engineering or support group depending on the nature of the problem. The customer support group will be able to track the status of the customer visit and add the identified problem to both the customer support databases.
[1321] Level 4 support will continue to be provided by the Systems Engineering programmers.
[1322] Staffing levels to provide acceptable customer hold times and abandon rates.
[1323] A staff that has on-line access to the order entry and billing systems.
[1324] Automatically generate weekly reports that detail volume of calls made, received, average hold-time of calls and number of trouble tickets opened/closed/escalated.
[1325] C. Accounting
[1326] Accounting is supported according to current MCI procedures.
[1327] D. Commissions
[1328] Commissions are supported according to current MCI procedures.
[1329] E. Reporting
[1330] Reporting is required for revenue tracking, internal and external customer installation/saes, usage and product/service performance. Weekly and monthly fulfillment reports are required from the fulfillment house(s). These fulfillment reports correlate the number of orders received and number of orders delivered. In addition, reporting identifies the number of different subscribers accessing Profile Management or the Message Center through the WWW Site.
[1331] F. Security
[1332] Security is enforced in accordance with MCI's published policies and procedures for Internet security. In addition, security is designed into the WWW Browser and ARU interface options to verify and validate user access to directlineMCI profiles, Message Center, Personal Home Page calendars and Personal Home Page configurations.
[1333] G. Trouble Handling
[1334] Trouble reporting of problems is documented and tracked in a single database. All troubles are supported according to the Network Services Trouble Handling System (NSTHS" guidelines. Any Service Level Agreements (SLAs) defined between MCI organizations are structured to support NSTHS.
[1335] Any troubles that require a software fix are closed in the trouble reporting database and opened as a Problem Report (PR) in the Problem Tracking System. This Problem Tracking System is used during all test phases of and is accessible by all engineering and support organizations.
[1337] Throughout this description, the following terms will be used:
[1338] The Web Servers running as Welcome Servers will be running the Netscape Commerce Server HTTP Daemon in secure as well as normal mode. The Web Servers operating as various application servers will run this daemon in secure mode only. The Secure Mode uses SSLv2.
[1339] A. Web Server Architecture
[1340] The Web Servers are located in a DMZ. The DMZ houses the Web Servers and associated Database Clients as required. The database clients do not hold any data, but provide an interface to the data repositories behind the corporate fir(wall.
[1341] The Web space uses Round-Robin addressing for name resolution. The Domain name is registered with the administrators of mci.com domain, with a sub-netted (internally autonomous) address space allocated for galileo.mci.com domain.
[1342]FIG. 40 shows the sequence of events leading to a successful login.
[1343] 1. Welcome Server 450
[1344] This Web Server runs both the secure and normal HTTP daemons. The primary function of this server is to authenticate user 452 at login time. The authentication requires the use of Java and a switch from normal to secure mode operation. There are one or more Welcome servers 450 in the DMZ. The information provided by the Welcome server 450 is stateless. The statelessness means that there is no need to synchronize multiple Welcome Servers 450.
[1345] The Welcome server's first task is to authenticate the user. This requires the use of single use TOKENS, Passcode authentication and Hostile IP filtering. The first is done using a Token Server 454, while the other two will be done using direct database 456 access.
[1346] In case of failed authentication, the user 452 is shown a screen that mentions all the reasons (except Hostile-IP) why the attempt may have failed. This screen automatically leads the users back to the initial login screen.
[1347] Welcome server's 450 last task, after a successful authentication, is to send a service selection screen to the user 452. The Service Selection screen directs the user to an appropriate Application Server. The user selects the Application, but an HTML file in the Server Section page determines the Application Server. This allows the Welcome Servers 450 to do rudimentary load balancing.
[1348] All the Welcome Servers 450 in the DMZ are mapped to www.galileo.mci.com. The implementation of DNS also allows galileo.mci.com to map to www.galileo.mci.com.
[1349] 2. Token Server 454
[1350] This is a database client and not a Web Server. The Token servers 454 are used by Welcome Servers 450 to issue a TOKEN to login attempts. The issued TOKEN, once validated, is used to track the state information for a connection by the Application Servers. The TOKEN information is maintained in a database on a database server 456 (repository) behind the corporate firewall. The Token Servers 454 do the following tasks:
[1351] 1. Issue single use TOKEN during authentication phase.
[1352] 2. Validate single use TOKEN (mark it for multi use).
[1353] 3. Validate multi-use TOKEN.
[1354] 4. Re-validate multi-use TOKEN.
[1355] The Token Servers 454 are required to issue a unique TOKEN on every new request. This mandates a communication link between multiple Token Servers in order to avoid conflict of TOKEN values issued. This conflict is eliminated by assigning ranges to each Token Server 454.
[1356] The TOKEN is a sixteen character quantity made up of 62 possible character values in the set [0-9A-Za-z]. The characters in positions 0, 1 and 2 for each TOKEN issued by the Token Server are fixed. These character values are assigned to each Token Server at configuration time. The character at position 0 is used as physical location identifier. The character at position 1 identifies the server at the location while the character at position 2 remains fixed at '0'. This character could be used to identify the version number for the Token Server.
[1357] The remaining 13 characters of the TOKEN are generated sequentially using the same 62 character set described above. At startup the TOKEN servers assign the current system time to the character positions 15-10, and set positions 9-3 to '0'. The TOKEN values are then incremented sequentially on positions 15-3 with position 3 being least significant. The character encoding assumes the following order for high to low digit values: 'z'-'a', 'Z'-'A', '9'-'0'.
[1358] The above scheme generates unique tokens if the system time is computed in 4 byte values, which compute to 6 base-62 characters in positions 15-10. The other assumption is that the scheme does not generate more than 62A7 (35*10A12) TOKENS in one second on any given Token Server in any embodiment.
[1359] The use of TOKEN ranges allows the use of multiple Token Servers in the Domain without any need for explicit synchronization. The method accommodates a maximum 62 sites, each having no more than 62 Token Servers. An alternate embodiment would accommodate more sites.
[1360] All of the Token Servers in the DMZ are mapped to token.galileo.mci.com. The initial embodiment contains two Token Servers 454. These Token Servers 454 are physically identical to the Welcome Servers 450, i.e., the Token Service daemon will run on the same machine that also runs the HTTP daemon for the Welcome service. In another embodiment, the two run on different systems.
[1361] The Welcome Server(s) 450 use the Token Server(s) 454 to get a single use TOKEN during the authentication phase of the connection. Once authenticated, the Welcome Server 450 marks the TOKEN valid and marks it for multiple use. This multi-use TOKEN accompanies the service selection screen sent to the user by the Welcome Server. The design of TOKEN database records is discussed in detail below.
[1362] 3. Application Servers
[1363] The Application servers are Web servers that do the business end of the user transaction. The Welcome Server's last task, after a successful authentication, is to send a service selection screen to the user. The service selection screen contains the new multi-use TOKEN.
[1364] When the user selects a service, the selection request, with its embedded TOKEN, is sent to the appropriate Application Server. The Application Server validates the TOKEN using the Token Server 454 and, if valid, serves the request. A Token Server can authenticate a TOKEN issued by any one of the Token Servers on the same physical site. This is possible because the Token Servers 454 are database clients for the data maintained on a single database repository behind the corporate firewall.
[1365] An invalid TOKEN (or a missing TOKEN) always leads to the "Access Denied" page. This page is served by the Welcome Server(s) 450. All denial of access attempts are logged.
[1366] The actual operation of the Application Server depends on the Application itself. The Application Servers in the DMZ are mapped to <appName><num>.galileo.mci.com. Thus, in an embodiment with multiple applications (e.g., Profile Management, Message Center,
[1367] Start Card Profile, Personal Web Space etc.), the same Welcome and Token servers 450 and 454 are used and more Applications servers are added as necessary.
[1368] Another embodiment adds more servers for the same application. If the work load on an application server increases beyond its capacity, another Application Server is added without any changes to existing systems. The SERVERS and TOKEN_HOSTS databases (described below) are updated to add the record for the new server. The <num>part of the host name is used to distinguish the Application Servers.
[1369] There is no need to use DNS Round-robin on these names. The Welcome server 450 uses a configuration table (The SERVERS database loaded at startup) to determine the Application Server name prior to sending the service selection screen.
[1370] B. Web Server System Environment
[1371] All the Web servers run the Netscape Commerce Server HTTP daemon. The Welcome Servers 450 run the daemon in normal as well, as secure mode, while the Application Servers only run the secure mode daemon.
[1372] The Token Server(s) run a TCP service that runs on a well known port for ease of connection from within the DMZ. The Token Service daemon uses tcp~wapper to deny access to all systems other than Welcome and Application server(s). In order to speed this authentication process, the list of addresses is loaded by these servers at configuration time, instead of using reverse name mapping at every request. The use of tcp_wrapper also provides the additional tools for logging Token Service activity.
[1373] The Application servers mostly work as front-ends for database services behind Lhe firewall. Their main task is to validate the access by means of the TOKEN, and then validate the database request. The database requests are to Create, Read, Update or Delete exiting records or data fields on behalf of the user. The Application Servers do the necessary validation and authority checks before serving the request.
[1374] 1. Welcome Servers
[1375] The Welcome Servers serve the HTML pages described below to the user at appropriate times. The pages are generated using Perl-based Common Gateway Interface (CGI) scripts. The Scripts reside in a directory which is NOT in the normal document-root directory of the HTTP daemon. The normal precautions regarding disabling directory listing and removing all backup files etc. are taken to ensure that CGI scripts are not readable to the user. FIG. 41 shows the directory structure 455 on the Welcome Server 450 (of FIG. 40 and referred to throughout this following paragraphs).
[1376]FIG. 41 shows that the <document_root>456 is separated from the <server_root>458. It also shows that the <document_root>directory holds only the welcome and access failure HTML pages.
[1377] The HTTP Server maps all requests to the "cgi" directory 460 based on the URL requested. The CGI scripts use the HTML templates from the "template" directory 462 to create and send the HTML output to the users on the fly.
[1378] The use of the URL to map to a CGI script out of the <document_root>456 blocks access to the <document_root>directory 456 by a malicious user. Since every access to the Welcome Server 450 maps to a CGI script in the cgi directory 460 of the Welcome Server 450, security is ensured by calling the authentication function at start of every script.
[1379] The user Authentication libraries are developed in Perl to authenticate the user identity. NSAPI's authentication phase routines also add features for TOKEN verification and access mode detection in the servers themselves.
[1380] The Welcome Servers 450 read their operating parameters into their environment from the database 456 at startup. It is necessary to keep this information in the common database in order to maintain the same environment on multiple Welcome Servers 450.
[1381] a) Welcome Page
[1382] The welcome page is sent as the default page when the Welcome Server 450 is first accessed. This is the only page that is not generated using a cgi script, and it is maintained in the <document_root>directory 456. This page does the following:
[1383] Confirms that the browser can display Frames. If the browser fails to display Frames correctly, this page will display an appropriate error message and direct the user to down load Microsoft Internet Explorer V3.O or later.
[1384] Confirms that the browser can run Java. A failure will result in the user being directed to Microsoft Internet Explorer V3.0 or later.
[1385] If the browser successfully displays Frames and runs Java, then this page will automatically request the Welcome Server 450 to send a login page.
[1386] The last action by the Welcome page is done using the Java applet embedded in the page. This also switches the user's browser from normal to secure mode.
[1387] b) Login Page
[1388] The Login Page is a cgi-generated page that contains an embedded single use TOKEN, a Java applet, and form fields for the user to enter a User Id and Passcode. The page may display a graphic to emphasize service. The processing of this page is padded to introduce an artificial delay. In the initial embodiment, this padding is set to) zero.
[1389] The response from this page contains the TOKEN, a scrambled TOKEN value generated by the applet, User Id and Passcode. This information is sent to the Welcome server using a POST HTTP request by the Java applet. The POST request also contains the Applet signature.
[1390] If the login process is successful the response to this request is the Server Selection page. A failure at this stage results in an Access Failed page.
[1391] c) Server Selection Page
[1392] The Server Selection Page is a cgi-generated page which contains an embedded multi-use TOKEN. This page also shows one or more graphics to indicate the types of services available to the user. Some services are not accessible by our users. In other embodiments, when more than one service exists, a User Services Database keyed on the User Id is used to generate this page.
[1393] The Welcome server uses its configuration information to embed the names of appropriate Application Servers with the view to sharing the load among all available Application Servers. This load sharing is done by using the configuration data read by the Welcome Server(s) during startup.
[1394] The Welcome Server selects an Application Server based upon entries in its configuration file for each of the services. These entries list the names of Application Server(s) for each application along with their probability of selection. This configuration table is loaded by the Welcome Servers at startup.
[1395] d) Access Failed Page
[1396] The Access Failed Page is a static pagethat displays a message indicating that the login failed because of an error in User Id, Passcode or both. This page automatically loads the Login Page after a delay of 15 seconds.
[1397] e) Access Denied Page
[1398] The Access Denied Page is a static page that displays a message indicating that an access failed due to authentication error. This page automatically loads the Login Page after a delay of 15 seconds. The Access Denied page is called by the Application Servers when their authentication service fails to recognize a TOKEN. All loads of this page will be logged and monitored.
[1399] 2. Token Servers 454
[1400] The TOKEN service on the Web site is the only source of TOKEN generation and authentication. The Tokens themselves are stored in a shared Database. This database can be shared among all Token servers. The Token Database is behind the firewall out of the DMZ. The Token service provides the services over a well-known (>1024) TCP port. These services are provided only to a trusted host. The list of trusted hosts is maintained in a configuration database. This database is also maintained behind the firewall outside of the DMZ.
[1401] The Token servers read their configuration database only on startup or when they receive a signal to refresh. The Token services are:
[1402] Grant a single use TOKEN for login attempt.
[1403] Validate a single use TOKEN.
[1404] Validate a TOKEN.
[1405] Re-Validate a TOKEN.
[1406] TOKEN aging is implemented by a separate service to reduce the work load on the Token servers.
[1407] All access to the Token Server(s) is logged and monitored. The Token Service itself is written using the tcp_wrapper code available from MCI's internal security groups.
[1408] 3. Profile Management Application Servers
[1409] The profile management application server(s) are the only type of Application servers implemented in the first embodiment. These servers have the same directory layout as the Welcome Servers. This allows the same system to be used for both services if necessary.
[1410] C. Security
[1411] The data trusted by subscribers to the Web server is sensitive to them. They would like to protect it as much as possible. The subscribers have access to this sensitive information via the Web selver(s). This information may physically reside on one or more database servers, but as far as the subscribers are concerned it is on Server(s) and it should be protected.
[1412] Presently only the following information needs to be protected in an embodiment:
[1413] In other embodiments, profile information for directline account additional information is protected, including Email, Voice Mail, Fax Mail, and Personal Home Page information.
[1414] The protection is offered against the following type of attackers:
[1415] People with access to Web;
[1416] Other subscribers;
[1417] MCI personnel;
[1418] People with access to Subscriber's network;
[1419] People with access to Subscriber's system;
[1420] People looking over the shoulder of the Subscriber; and
[1421] Other systems pretending to be Server(s).
[1422] The project implements the security by using the following schemes:
[1423] Single use TOKENS for login attempts;
[1424] Validated TOKENS will accompany all transactions;
[1425] TOKEN aging to invalidate a TOKEN if it has not been used for ten minutes;
[1426] TOKEN is associated with the IP Address of the calling machine, so TOKEN stealing is not an easy option;
[1427] Use of SSL prevents TOKEN or DATA stealing without having physical access to the customer's display;
[1428] Use of TOKEN in a form analogous to the Netscape Cookie gives us the option to switch to cookies at a later date. Cookies offer us the facility to hide the TOKEN even further into the document for one extra layer of security; and
[1429] Use of Hostile-IP table to block multiple offenders without detection by them.
[1430] In addition to the security implemented by TOKEN as described above, the Web Server(s) are in a Data Management Zone for further low level security. The DMZ security is discussed below.
[1431] D. Login Process
[1432]FIG. 42 shows the Login Process. The sequence of events leading to a successful login is:
[1433] 1. The user requests a connection to www.galileo.mci.com.
[1434] 2. A server is selected from a set using DNS Round-robin.
[1435] 3. An HTML Page is sent to the user's browser.
[1436] 4. The Page checks the browser for JAVA Compliance and displays a welcome message.
[1437] 5. If the browser is not Java compliant, the process stops with an appropriate message.
[1438] 6. If the browser is Java compliant, it automatically issues a "GET Login Screen" request to the www.galileo.mci.com server. This request also switches the browser to SSL v2. It will fail if the Browser is not SSL compliant.
[1439] 7. The Web Server does the following:
[1440] A. The Web server gets a Single Use Token from its internal Token service.
[1441] B. The Web server picks one applet from a large set.
[1442] C. The Web server Records the Applet, Token, and Client IP address in a Database.
[1443] D. The Web server sends back the Login Screen, with Applet & Token.
[1444] 8. User fills in the Login Screen fields—User Id and Passcode.
[1445] A. The User Id is the user's Directline number (printed on User's Business cards and is in public domain).
[1446] B. The Passcode is a Six digit number known only to the User.
[1447] 9. When the User presses Enter (or clicks on the LOGIN button) the Java Applet sends the UserId, Passcode, Token, and Scrambled Token back. The Scrambling Algorithm is specific to the Applet that was sent in Step 7D.
[1448] 10. If the browser's IP address is in the Hostile-IP table, the server goes back to Step 7.
[1449] 11. The Web server authenticates the Login request against what it recorded in Step 7C.
[1450] 12. If the test is invalid: if this is the third successive failed attempts from the same IP address server records the Address in Hostile-IP table.
[1451] 13. The server goes back to Step 7.
[1452] 14. If the test is valid; The server sends a selecl services screen to the Browser with an embedded Token. The Token is still associated with the Browser's IP address, but it now has an expiration time.
[1453] E. Service Selection
[1454] When the user selects an option from the Service selection screen, the request is accompanied by the Token. The token is validated before the service is accessed, as shown in FIG. 42.
[1455] F. Service Operation
[1456] The screens generated by the Application Servers all contain the Token issued to the user when the Login process was started. This Token has an embedded expiration time and a valid source IP Address. All operation requests include this token as a part of the request.
[1457] The service requests are sent by the browser as HTML forms, APPLET based forms or plain Hyper Links. In the first two instances, the Token is sent back as a Hidden field using the HTTP-POST method. The Hyper-Links use either the HTTP-GET method with embedded Token or substitute the Cookie in place of a Token. The format of the Token is deliberately chosen to be compatible with this approach.
[1458] 1. NIDS Server
[1459] The NIDS server in the system is isolated from the Web Servers by a router-based firewall. The NIDS server runs the NIDSCOMM and ASCOMM services that allow TCP clients access to databases on the NIDS server. The NIDSCOMM and ASCOMM services do not allow connectivity to databases not physically located on the NIDS Server.
[1460] The following databases (C-tree services) on the NIDS server are used by the Welcome Server, Token Server and Profile Management Application Server:
[1461]800_PIN —1CALL (this is a partitioned database);
[1465] COUNTRY2 (maybe);
[1466] COUNTRY_CITY (maybe);
[1468] NPACITY _OA300 (maybe); and
[1470] In addition to the C Tree services named above the following new C tree services will be defined in the SERVDEF and used only on the NIDS server dedicated to the system:
[1474] TOKEN_HOSTS; and
[1476] The following descriptions for these databases do not show the filler field required at the first byte of each record, nor do they attempt to show any other filler fields that may be required for structure alignment along the 4-byte boundaries. This omission is made only for clarity. The numbers in parentheses next to the field definitions are the number of bytes required to hold the field value.
[1477] 2. TOKEN database service.
[1478] The TOKEN database service is accessed by the Token Servers. The primary operations on this service are Create a new record, read a record for a given Token value and update a record for the given Token value.
[1479] A separate chron job running on the NIDS Server itself also accesses this database and deletes obsolete records on a periodic basis. This chron job runs every hour. It does a sequential scan of the database and deletes records for expired tokens.
[1480] The TOKEN database service contains the TOKEN records. The TOKEN records use a single key (the TOKEN) and have the following fields:
[1481] 1. Version (1);
[1482] 2. Use Flag (Single/Multi) (1);
[1483] 3. Token Value (16);
[1484] 4. IP Address (16);
[1485] 5. User Id (16);
[1486] 6. Time Granted (4); and
[1487] 7. Time expires (4).
[1488] The key field is the Token Value.
[1489] 3. SERVERS database service.
[1490] The Servers Database Service is accessed by the Welcome Server at configuration time. The records in this database contain the following fields:
[1491] 1. Application Name (16);
[1492] 2. Application Server Host Name (32);
[1493] 3. Application Server Domain Name (32);
[1494] 4. Weight (1);
[1495] 5. Application Icon File URL (64); and
[1496] 6. Application Description File URL (64).
[1497] The key field is the combination of Application Name, Server Host Name, and Server Domain Name. This database is read by the Welcome Servers sequentially. This database is also accessed by the Web Administrators to Create, Read, Update and Delete records. This access is via the ASCOMM interface. The Web Administrators use the a HTML form and CGI script for their administration tasks.
[1498] 4. HOSTILE IP database service.
[1499] This database is accessed by the Welcome servers to create new records or read existing records based on IP address as the key. The read access is very frequent. This database contains the following fields:
[1500] 1. IP Address (16);
[1501] 2. Time entered (4); and
[1502] 3. Time expires (4).
[1503] The key field is the IP Address. All three values are set by the Welcome Server when creating this record. If the entry is to be overridden, the service doing the over-ride will only be allowed to change the Time expires value to <epoch-start>, thus flagging the entry as over-ride.
[1504] This database is also accessed by the Web Adniinistrators to Create, Read, Update, and Delete records. Access is via the ASCOMM interface. The Web Administrators use the HTML form and CGI script for their administration tasks.
[1505] Customer Service uses a specially developed tool to access this database and access is allowed only from within the corporate firewall.
[1506] A chron job running on the NIDS server also accesses this database and deletes all obsolete records from this database. This job logs all its activity. The log of this job is frequently examined by the Web Administrators all the time.
[1507] 5. TOKEN HOSTS database service.
[1508] This database service lists IP Addresses of the hosts trusted by the Token Servers. This database is read by the Token Service at configuration time. The records in this database contain the following fields:
[1509] 1. IP Address (16);
[1510] 2. Authority (1);
[1511] 3. Host Name (32);
[1512] 4. Host Domain Name (32); and
[1513] 5. Host description (64).
[1514] The key field is the IP Address. The Authority binary flag determines the access level. The low access level only allows validate/re-validate commands on an existing TOKEN; the high access level additionally allows Grant and Validate single use TOKEN commands as well. This database is also accessed by the Web Administrators to Create, Read, Update and Delete records. Access is via the ASCOMM interface. The Web Administrators use the HTML form and CGI script for their administration tasks.
[1515] 6. SERVER_ENV database service.
[1516] This database is read by the Welcome and Application servers at startup. It defines the starting environment for these servers. In one embodiment, only one field (and only for the Welcome Servers) is designed to be used. This is expanded in other embodiments.
[1517] The records in this database contain the following fields:
[1518] 1. Sequence Number (4);
[1519] 2. Application Name (16);
[1520] 3. Environment Name (32); and
[1521] 4. Environment Value (64).
[1522] The key field is Sequence Number. Environment values may refer to other environment variables by name. The values are evaluated at run time by the appropriate CGI scripts. The Welcome Servers are assigned the pseudo Application Name of WELCOME.
[1523] This database is also accessed by the Web Administrators to Create, Read, Update and Delete records. This access is via the ASCOMM interface. The Web Administrators use the HTML form and CGI script for their administration tasks.
[1524] 7. Chron Job(s)
[1525] The NIDS Server runs a cleanup chron job. This job is scheduled to run every hour. The main tasks for this job are the following:
[1526] 1. Scan the HOSTILE_IP database and report on all records. This report contains all records. The aim is to track repeat offenders based on this report.
[1527] 2. Scan the HOSTILE_IP database and report on records with <epoch-time>as their expiration time.
[1528] 3. Scan the HOSTILE IP database and delete obsolete records.
[1529] 4. Scan the TOKEN database and report on all records. This report format will be geared towards traffic reporting rather than scanning each entry.
[1530] 5. Scan the TOKEN databbase to delete obsolete records.
[1531] G. Standards
[1532] The following coding standards have been developed:
[1533] 1. HTML Look and Feel standards;
[1534] 2. Java Look and Feel standards (derived from the HTML look and feel standards, these are the new class libraries used in development to force a common look and feel on the site's pages); and
[1535] 3. HTML Programming standards.
[1536] H. System Administration
[1537] The system administration tasks require reporting of at least the following System Operating Parameters to the System Administrators:
[1538] System stats and disk usage with time stamps;
[1539] Network operating parameters with time stamps;
[1540] Web page usage and access statistics with time stamps;
[1541] TOKEN usage statistics;
[1542] Hostile IP alarms and statistics;
[1543] The following tools and utilities are on the Servers in DMZ;
[1544] Time synchronization;
[1545] Domain Name Servers;
[1546] System Log Monitoring;
[1547] Alarm reporting; and
[1548] Secure Shell.
[1549] The system generates alarms for the following conditions:
[1550] Incorrect use of TOKENS;
[1551] Hostile IP table changes;
[1552] TOKEN Expiration; and
[1553] Login attempts
[1554] The alarms will be generated at different levels. The Web Servers use the following broad guidelines:
[1555] 1. The servers run in a root environment.
[1556] 2. The administrators are able to start a staging server on a non- standard port to test a new (staged) service.
[1557] 3. The staging server is accessible from Internet during the staging run.
[1558] 4. The Administrators have the option to move the staging software from staging area to production area with a single command.
[1559] There are suitable checks to make sure this is not done accidentally.
[1560] L Product/Enhancement
[1561] A preferred embodiment enables directlineMCI customers additional control over their profile by providing a graphical user interface, and a common messaging system. The capability to access the power of a preferred embodiment exists in the form of a directlineMCI profile and common messaging system. The user is able to modify his account, customizing his application by making feature/functionality updates. The application enables the power of the future capabilities that a preferred embodiment integration will provide by allowing the user to run his application.
[1562] The user is able to access all of his messages by connecting with just one location. FAX, email, page and voice messages will be accessed through a centralized messaging interface. The user is able to call into the centralized messaging interface through his message center interface to retrieve messages. A centralized message interface provides the user the capability to manage his communications easily and effectively.
[1563] The user interface has two components, the user's application profile and message center. The interface is accessible through PC software (i.e., PC Client messaging interface), an ARU or a VRU, and a World Wide Web (WWW) Browser. The interface supports the customization of applications and the management of messages.
[1564] The feature/functionality requirements for an embodiment will be presented below. The first piece to be described is the ARU interface and its requirements for the user interface, message management and profile management. Following the ARU requirements, requirements are also provided for the WWW Browser and PC Clieit interfaces.
[1565] J. Interface Feature Requirements (Overuiew)
[1566] A front-end acts as an interface between the user and a screen display server in accordance with a preferred embodiment. The user is able to access the system and directly access his profile and messages. The user interface is used to update his profile and to access his messages. The user's profile information and the user's messages may reside in different locations, so the interface is able to connect to both places. Profile and messaging capabilities are separate components of the interface and have different requirements.
[1567] Through his interface, the user is able to update his profile in real- time through profile management. The application profile is the front-end to the user account directory, which is where all of the user account information resides in a virtual location. Also, a user is able to manage his messages (voicemail, faxmail, email, pager recall) through his message center. The message center is the front-end to the centralized messaging database, which is where all of the user's messages may reside, regardless of message content.
[1568] Three user interfaces are supported: —DTMF access to an ARU or VRU;
[1569] WWW Browser access to a WWW Site; and
[1570] PC Client access to a Messaging Server.
[1571] From the ARU, the users are able to update their profiles (directlineMCI only), retrieve voicemail messages and pager recall messages, and retrieve message header (sender, subject, date/time) information for faxmail and email messages. Through the PC Client, the user is limited to message retrieval and message manipulation. The WWW Browser provides the user a comprehensive interface for profile management and message retrieval. Through the WWW Browser, the users are able to update their profiles (directlineMCI, Information Services, List Management, Global Message Handling and Personal Home Pages) and retrieve all message types.
[1572] 1. The User Account Profile
[1573] The user is able to access account information through the application profile. The application profile provides an intelligent interface between the user and his account information, which resides in the user account directory. The User Account Directory accesses the individual account information of users. Users are able to read and write to the directory, making updates to their accounts. The directory allows search capabilities, enabling customer service representatives to search for a specific account when assisting a customer.
[1574] When a customer obtains a phone number, the user account directory reflects the enrollment, and the user is able to access and update features through his user account profile. If a customer withdraws, the user directory will reflect the deactivation, and the service will be removed from the user's application profile.
[1575] In summary, the user account directory provides account information for each of the user's services. However, the user account directory is limited to: directlineMCI profile, Information Services profile, Global Message Handling, List Management and Personal Home Page profiles. This information determines the feature/functionality of the user's application and provides the user with the flexibility that is necessary to customize his application, allowing MCI to meet his continuously changing communication needs.
[1576] 2. The Database of Messages
[1577] An important feature that is offered is the integration of messages. Messages of similar and dissimilar content are consolidated in one virtual location. Through a call, the message center provides the user with a review of all of his messages, regardless of content or access. Through the interface messaging capabilities, the user is also able to maintain an address book and distribution lists.
[1578] This message database is a centralized information store, housing messages for users. The message database provides common object storage capabilities, storing data files as objects. By accessing the message database, users retrieve voicemail, faxmail, email and pager recall messages from a single virtual location. In addition, by using common object storage capabilities, message distribution is extremely efficient.
[1579] K. Automated Response Unit (ARU) Capabilities
[1580] 1. User Interface
[1581] The ARU interface is able to perform directlineMCI Profile Management, Information Services Profile Management, message retrieval and message distribution. The DTMF access provided through the ARU is applied consistently across different components within the system. For example, entering alphabetic characters through the DTMF keypad is entered in the same manner regardless if the user is accessing Stock Quote information or broadcasting a fax message to a distribution list.
[1582] Voicemail Callback Auto Redial provides the capability to prompt for and collect a DTMF callback number from a guest leaving a voicemail and automatically launch a return call to the guest call back number when retrieving messages. Upon completing the callback, the subscriber will be able to return to the same place where they left off in the mailbox.
[1583] Music On-Hold provides music while a guest is on-hold.
[1584] Park and Page provides a guest an option to page a directlineMCI subscriber, through the directlineMCI gateway, then remain on-hold while the subscriber is paged. The subscriber receives the page and calls their directlineMCI number, where they can select to be connected with the guest on hold. Should the subscriber fail to connect a call with the guest, the guest will receive an option to be forwarded to voicemail. If the subscriber does not have voicemail as a defined option, then the guest a final message will be played for the guest.
[1585] Note: The guest has the ability to press an option to be forwarded to voicemail at any time while on hold.
[1586] Call Screening with Park and Page An embodiment provides the subscriber with functionality for responding to a park and page, the identity of the calling party (i.e., guest). This provides the subscribers the ability to choose whether they wish to speak to the guest or transfer the guest to voicemail, prior to connecting the call. Specifically, guests are ARU prompted to record their names when they select the park and page option. When the subscriber respond to the park and page, they will hear an ARU prompt stating, "You have a call from RECORDED NAME", then be presented with the option to connect with the calling party or transfer the party to voicemail. If the subscriber does not have voicemail as a defined option, then the guest will be deposited to a final message. The guest also will have the ability to press an option to be forwarded to voicemail at any time while on hold.
[1587] Two-way Pager Configuration Control and Response to Park and Page
[1588] The system also allows a subscriber to respond to a park and page notification by instructing the ARU to route the call to voicemail or final message or continue to hold, through a command submitted by a two-way pager.
[1589] Text Pager Support
[1590] The system allows a subscriber to page a directlineMCI subscriber, through the directlineMCI gateway, and a leave a message to be retrieved by a text pager. Specifically, upon choosing the appropriate option, the guest will be transferred to either the networkMCI Paging or the SkyTel message center where an operator will receive and submitcreate a text-based message to be retrieved by the subscriber's text pager.
[1591] Forward to the Next Termination Number
[1592] The system provides the capability for the party answering the telephone, to which a directlineMCI call has been routed, to have the option to have the call routed to the next termination number in the directlineMCI routing sequence. Specifically, the called party will receive a prompt from the directlineMCI ARU gateway, which indicates that the call has been routed to this number by directlineMCI and providing the called party with the option to receive the incoming call or have the call routed to the next termination number or destination in the routing sequence. The options presented to a called party include:
[1593] Press an option to accept the call
[1594] Press an option to send the call to the next termination
[1595] Let the call time-out (i.e., no action taken) and then proceed to the next termination.
[1596] Less Than 2 Second # Reorigination
[1597] An embodiment also provides the capability to reoriginate an outbound call, from the directlineMCI gateway, by pressing the pound (#) key for less than two seconds. Currently, directlineMCI requires the # key to be depressed for two seconds or more before the subscriber can reoriginate a call.
[1598] L. Message Management
[1599] 1. Multiple Media Message Notification
[1600] The subscriber can receive an accounting of current messages across a number of media, to include voicemail, faxmail, email, paging. Specifically, the subscriber will hear an ARU script stating, for example, "You have 3 new voicemail messages, 2 new faxmail messages, and 10 new email messages."
[1601] 2. Multiple Media Message Manipulation
[1602] A subscriber is allowed to access the Universal Inbox to perform basic message manipulation, of messages received through multiple media (voicemail, faxmail, email, paging), through the directlineMCI ARU gateway. Subscribers are able to retrieve voicemail messages and pager messages, and retrieve message header (priority, sender, subject, date/time, size) information for faxmail and email messages. In addition, subscribers are able to save, forward or delete messages reviewed from the ARU interface. The forward feature is limited to distributing messages as either voicemails or faxmails. Only voicemail messages can be forwarded as voicemails. Email, faxmail and pager messages can be forwarded as faxmails; however, it may be necessary to convert email and pager messages to a G3 format. When forwarding messages as faxmails, subscribers have the ability to send messages to distribution lists and Fax Broadcast lists.
[1603] 3. Text to Speech
[1604] The system converts text messages, received as email, faxmail or pager messages, into audio, which can be played back through the directlineMCI gateway. Initially, the text-to-speech capability will be limited to message header (priority, sender, subject, date/time, size) information.
[1605] Subscribers are provided the option to select whether they want to hear message headers first and then select which complete message they want to be played. The only message type that does not support a text-to-speech capability for the complete message will be faxmail messages. The capability only exists to play faxmail headers. FAXmail header information includes sender's ANI, date/time faxmail was received and size of faxmail.
[1606] 4. Email Forwarding to a Fax Machine
[1607] Subscribers can forward an email, retrieved and reviewed through the directlineMCI ARU gateway, to a subscriber-defined termination nunmber. Specifically, the subscriber has the ability to review an email message through the directlineMCI ARU. After reviewing the message, the subscriber receives, among the standard prompts, a prompt requesting Whether he would like to forward the email message to a specified termination number or have the option to enter an impromptu number. Upon selecting this option and indicating the termination number, the email message is converted to a G3 format and transmitted to the specified termination number. Email attachments that are binary files are supported. If an attachment cannot be delivered to the terminating fax machine, a text message must be provided to the recipient that the binary attachment could not be forwarded. Forwarding of emails to a fax machine does not result in the message being deleted from the "universal inbox".
[1608] 5. Pager Notification of Messages Received
[1609] A subscriber can receive a pager notification, on a subscriber-defined interval, indicating the number of messages, by message media, that currently reside in the subscriber's "universal inbox". Specifically, the subscriber will have the ability to establish a notification schedule, through the directlineMCI ARU, to receive a pager message which indicates the number of voicemail, faxmail, email and pager messages that reside in the subscriber's "universal inbox".
[1610] 6. Delivery Confirmation of Voicemail
[1611] The system provides the subscriber the ability to receive a confirmation voicemail message when a subscriber-initiated voicemail message was not successfully delivered to the terminating party(s).
[1612] 7. Message Prioritization
[1613] The system provides the guest the ability to assign either regular or urgent priority to a message. When the subscriber receives an accounting of messages, the prioritization will be indicated, and all urgent messages will be indexed before regular messages. This requirement only applies to voicemails, not faxmails. This will require that the "universal inbox" present the proper message priority for directlineMCI voicemails.
[1614] M. Information Services
[1615] Through the ARU interface, users will be able to receive content from information services which are configurable through the WWW Browser interface. Information content will be provided as an inbound service and an outbound service. The information content that is defined through the WWW Browser (i.e., Profile Management) is defined as the inbound information content and will be limited to:
[1616] Stock Quotes and Financial News
[1617] Headline News.
[1618] Subscribers also have the ability to access additional information content through the ARU interface; however, this information is not configurable through the WWW Browser (i.e., Profile Management). This additional information content will be referred to as outbound information content and will consist of:
[1619] Stock Quotes and Financial News;
[1620] Headline News;
[1621] Weather;
[1622] Sports News and Scores;
[1623] Soap Opera Updates;
[1624] Horoscopes;
[1625] Lottery Results;
[1626] Entertainment News; and
[1627] Traveler's Assist.
[1628] The configurable parameters of the inbound information content is defined below. Retrieval of outbound information content will support the entry of alphabetic characters through a DTMF keypad. Entering of alphabetic characters must be consistent with the manner that alphabetic characters are entered through DTMF for list management.
[1629] Access to Traveler's Assist will be bundled with the other outbound information services such that the subscriber only has to dial a single 800/8XX number. The 800/8XX call may extend to different termination depending upon the information content selected.
[1630] N. Message Storage Requirements
[1631] The message storage requirements are consistent with the message storage requirements defined below.
[1632] O. Profile Management
[1633] directlineMCI Profile Management
[1634] Subscribers can also review, update and invoke their directlineMCI account profiles. The directlineMCI profile management capabilities through the ARU interface are consistent with the presentation provided through the WWW Browser and support the following requirements:
[1635] Create new directlineMCI profiles and assign names to the profile;
[1636] Invoke directlineMCI profiles;
[1637] Voice annotate directlineMCI profile names;
[1638] Update existing directlineMCI profiles;
[1639] Support the rules-based logic of creating and updating directlineMCI profiles (e.g., selection of only one call routing option, like voicemail, will invoke override routing to voicemail; and updates made in one parameter must ripple through all affected parameters, like paging notification);
[1640] Enable a directlineMCI number;
[1641] Enable and define override routing number; and
[1642] Enable and define FollowMe routing.
[1643] Enable and define final routing (formerly called alternate routing) to:
[1644] Voicemail and pager;
[1645] Voicemail only;
[1646] Pager only;
[1647] Final message;
[1648] Invoke menu routing if two or more of the call routing options (FollowMe, voicemail, faxmail or pager) are enabled;
[1649] Define the default number for faxmail delivery;
[1650] Activate paging notification for voicemail;
[1651] Activate paging notification for faxmail; and
[1652] Provide guest option to classify voicemails for urgent delivery;
[1653] Define call screening parameters for:
[1654] Name and ANI;
[1655] ANI only;
[1656] Name only; and
[1657] Enable or disable park and page.
[1658] P. Call Routin Menu Change
[1659] The system also provides the capability for subscribers to modify their call routing termination numbers without havir_g to re-enter termination numbers which they do not wish to change. Specifically, the directlineMCI routing modification capability requires the subscriber to re-enter all termination numbers in a routing sequence should they wish to change any of the routing numbers. This capability permits the subscriber to change only the termination numbers they wish to change, and indicate by pressing the "#" key when they do not wish to change a specific number in the routing sequence.
[1660] Q. Two-way Pager Configuration Control and Response to Park and Page
[1661] The system can also enable or disable predefined directlineMCI profiles through a command submitted by a two-way pager.
[1662] R. Personalized Greetings
[1663] The system provides subscribers the ability to review and update the personalized greeting that will be played from the ARU or displayed from their Personal Home Page. Each greeting is maintained separately and customized to the features available through each interface (ARU or Personal Home Page).
[1664] S. List Management
[1665] The system also provides the subscriber the ability to create and update lists, and create a voice annotation name for a list. Fax Broadcast list management capabilities are integrated with directlineMCI list management capabilities to provide a single database of lists. From the ARU interface, subscribers have the ability to review, update, add or delete members on a list. In addition, subscribers are able to delete or create lists. The ARU interface is able to use the lists to distribute voicemail and faxmail messages.
[1666] Access to distribution lists supports alphabetic list names such that lists are not limited to list code names. Entering of alphabetic characters through DTMF to the ARU for list names is consistent with the manner that alphabetic characters are entered through DTMF for Information Services. The List Management requirements are discussed in greater detail below.
[1667] In addition to providing message manipulation capabilities, the PC Client also provides an address book and access to lists. The user is able to make modifications to the address book and manage distribution lists for voice, fax, email and paging messages. In one embodiment, lists created or maintained through the PC Client interface are not integrated with lists created or maintained through the WWW Browser or ARU interfaces, but such integration can be implemented in an alternative embodiment. The subscriber is able to send a message to a distribution list from the PC Client. This requires a two-way interface between the PC Client and the List Management database whereby the PC Client can export a comma delimited or DBF formatted file to the database of lists.
[1668] The user is able to create and modify recipient address information through his interface PC software. The user is able to record multiple types of addresses in his address book, including 10 digit ANIs, voice mailbox ids, fax mailbox ids, paging nut_,bers and email addresses (MCIMail and Internet). This information is saved onto the PC. The address information retained on the PC Client is classified and sorted by recipient's name.
[1669] T. Global Message Handling
[1670] From the ARU interface, subscribers are able to d e fine which message types can be acc essed from the—universa l inbox". The global message handling requirements are consistent with the requirements defined below.
[1672] The discussion thus far has provided an introduction to the Internet, and therefore Internet telephony, but Internet telephony encompasses quite a few areas of development. The following is a summary of Internet telephony, divided into seven key areas. The first area consists of access to Internet telephony services. This area involves accessing and utilizing the Internet using such mechanisms as satellites, dialup services, T1, T3, DS3, OC3, and OC12 dedicated lines, SMDS networks, ISDN B-channels, ISDN D-channels, multirate ISDN, multiple B-channel bonded ISDN systems, Ethernet, token ring, FDDI GSM, LMDS, PCS, cellular networks, frame relay, and X.25.
[1673] The second area involves sharing Internet telephony. Multimedia data can utilize circuit-switched networks quite readily due to the high reliability and throughput potential. Issues include shared data, pushing URL data between parties, data conferencing, shared whiteboarding, resource collaboration, and ISDN user-user signaling.
[1674] The third area deals with routing Internet telephony. Issues include the time-of-day, the day-of-week, the day-of-month, and the day-of- year, in addition to geographic points of origin, network point of origin, and time zone of origin. Analysis of routing also includes user data, destination parties, telephone numbers, lines of origin, types of bearer service, presubscribed feature routing, ANI, and IP addresses. Also, VNET plans, range privileges, directory services, and Service Control Points (SCP)s fall into routing Internet telephony.
[1675] The fourth category deals with quality of service. Analysis must include switched networks, ISDN, dynamic modifications, Internet telephony, RSVP, and redundant network services. In addition, this category includes hybrid Internet/telephony switches, Ethernet features, ISDN features, analog local loops and public phones, and billing for reserved and/or utilized services.
[1676] The fifth category is composed of directory services, profiles, and notifications. Examples are distributed directories, finding-me and follow-me services, directory management of telephony, and user interfaces. Calling party authentication security is also included. Hierarchical and object-oriented profiles exist, along with directory service user profiles, network profile data structures, service profiles, and order entry profiles.
[1677] The sixth category consists of hybrid Internet telephony services. Areas include object directed messaging, Internet telephony messaging, Internet conferencing, Internet faxing, information routing (IMMR), voice communications, and intranets (such as those that exist within a company). Other services include operator services, management service, paging services, billing services, wireless integration, message broadcasts, monitoring and reporting services, card services, video-mail services, compression, authorization, authentication, encryption, telephony application builders, billing, and data collection services.
[1678] The seventh category consists of hybrid Internet media services, which include areas of collaborative work which involve a plurality of users. Users can collaborate on Audio, Data and Video. This area includes media conferencing within the Hybrid network. Then there is a broadly related area of Reservations mechanism, Operator-assisted conferencing, and the introduction of content into conferences. The Virtual locations of these conferences will assume importance in the future. The next-generation Chat Rooms will feature virtual conference spaces with simulated Office Environments.
[1679] A. System Envtronment for Internet Media
[1680] 1. Hardware
[1681] A preferred embodiment of a system in accordance with the present invention is preferably practiced in the context of a personal computer such as the IBM PS/2, Apple Macintosh computer or UNIX based workstation. A representative hardware environment is depicted in FIG. 1A, which illustrates a typical hardware configuration of a workstation 99 in accordance with a preferred embodiment having a central processing unit 10, such as a microprocessor, and a number of other units interconnected via a system bus 12. The workstation shown in FIG. 1A includes a Random Access Memory (RAM) 14, Read Only Memory (ROM) 16, an I/O adapter 18 for connecting peripheral devices such as a communication network (e.g., a data processing network) 81, printer 30 and a disk storage unit 20 to the bus 12, a user interface adapter 22 for connecting a keyboard 24, a mouse 26, a speaker 28, a microphone 32, and/or other user interface devices such as a touch screen (not shown) to the bus 12, and a display adapter 36 for connecting the bus 12 to a display device 38. The workstation typically has resident thereon an operating system such as the Microsoft Windows NT or Windows/95 Operating System (OS), the IBM OS/2 operating system, the MAC System/7 OS, or UNIX operating system. Those skilled in the art will appreciate that the present invention may also be implemented on platforms and operating systems other than those mentioned.
[1682] 2. Object-Oriented Software Tools
[1683] A preferred embodiment is written using JAVA, C, and the C++language and utilizes object oriented programming methodology. Object oriented programming (OOP) has become increasingly used to develop complex applications. As OOP moves toward the mainstream of software design and development, various software solutions require adaptation to make use of the benefits of OOP. A need exists for these principles of OOP to be applied to a messaging interface of an electronic messaging system such that a set of OOP classes and objects for the messaging interface can be provided.
[1684] OOP is a process of developing computer software using objects, including the steps of analyzing the problem, designing the system, and constructing the program. An object is a software package that contains both data and a collection of related structures and procedures. Since it contains both data and a collection of structures and procedures, it can be visualized as a self-sufficient component that does not require other additional structures, procedures or data to perform its specific task. OOP, therefore, views a computer program as a collection of largely autonomous components, called objects, each of which is responsible for a specific task. This concept of packaging data, structures, and procedures together in one component or module is called encapsulation.
[1685] In general, OOP components are reusable software modules which present an interface that conforms to an object model and which are accessed at run-time through a component integration architecture. A component integration architecture is a set of architectural mechanisms which allow software modules in different process spaces to utilize each other's capabilities or functions. This is generally done by assuming a common component object model on which to build the architecture.
[1686] It is worthwhile to differentiate between an object and a class of objects at this point. An object is a single instance of the class of objects, which is often just called a class. A class of objects can be viewed as a blueprint, from which many objects can be formed.
[1687] OOP allows the programmer to create an object that is a part of another object. For example, the object representing a piston engine is said to have a composition-relationship with the object representing a piston. In reality, a piston engine comprises a piston, valves and many other components; the fact that a piston is an element of a piston engine can be logically and semantically represented in OOP by two objects.
[1688] OOP also allows creation of an object that "derived from" another object. If there are two objects, one representing a piston engine and the other representing a piston engine wherein the piston is made of ceramic, then the relationship between the two objects is not that of composition. A ceramic piston engine does not make up a piston engine. Rather it is merely one kind of piston engine that has one more limitation than the piston engine; its piston is made of ceramic. In this case, the object representing the ceramic piston engine is called a derived object, and it inherits all of the aspects of the object representing the piston engine and adds further limitation or detail to it. The object representing the ceramic piston engine "derives from" the object representing the piston engine. The relationship between these objects is called inheritance.
[1689] When the object or class representing the ceramic piston engine inherits all of the aspects of the objects representing the piston engine, it inherits the thermal characteristics of a standard piston defined in the piston engine class. However, the ceramic piston engine object overrides these ceramic specific thermal characteristics, which are typically different from those associated with a metal piston. It skips over the original and uses new functions related to ceramic pistons. Different kinds of piston engines have different characteristics, but may have the same underlying functions associated with them (e.g., number of pistons in the engine, ignition sequences, lubrication, etc.). To access each of these functions in any piston engine object, a prograrmmer would identify the same functions with the same names, but each type of piston engine may have different/overriding implementations of functions behind the same name. This ability to hide different implementations of a function behind the same name is called polymorphism and it greatly simplifies communication among objects.
[1690] With the concepts of composition-relationship, encapsulation, inheritance and polymorphism, an object can represent just about anything in the real world. In fact, our logical perception of the reality is the only limit on determining the kinds of things that can become objects in object-oriented software. Some typical categories are as follows:
[1691] ? Objects can represent physical objects, such as automobiles in a traffic-flow simulation, electrical components in a circuit- design program, countries in an economics model, or aircraft in an air-traffic-control system.
[1692] ? Objects can represent elements of the computer-user environment such as windows, menus or graphics objects.
[1693] ? An object can represent an inventory, such as a personnel file or a table of the latitudes and longitudes of cities.
[1694] ? An object can represent user-defined data types such as time, angles, and complex numbers, or points on the plane.
[1695] With this enormous capability of an object to represent just about any logically separable matters, OOP allows the software developer to design and implement a computer program that is a model of some aspects of reality, whether that reality is a physical entity, a process, a system, or a composition of matter. Since the object can represent anything, the software developer can create an obkect which can be used as a component in a larger software project in the future.
[1696] If 90% of a new OOP software program consists of proven, existing components made from preexisting reusable objects, then only the remaining 10% of the new software project has to be written and tested from scratch. Since 90% already came from an inventory of extensively tested reusable objects, the potential domain from which an error could originate is 10% of the program. As a result, OOP enables software developers to build objects out of other, previously built, objects.
[1697] This process closely resembles complex machinery being built out of assemblies and sub-assemblies. OOP technology, therefore, makes software engineering more like hardware engineering in that software is built from existing components, which are available to the developer as objects. All this adds up to an improved quality of the software as well as an increased speed of its development.
[1698] Programming languages are beginning to fully support the OOP principles, such as encapsulation, inheritance, polymorphism, and composition-relationship. With the advent of the C++ language, many commercial software developers have embraced OOP. C++ is an OOP language that offers a fast, machine-executable code. Furthermore, C++ is suitable for both commercial-application and systems-programming projects. For now, C++ appears to be the most popular choice among many OOP programmers, but there is a host of other OOP languages, such as Smalltalk, common lisp object system (CLOS), and Eiffel. Additionally, OOP capabilities are being added to more traditional popular computer programming languages such as Pascal.
[1699] The benefits of object classes can be summarized, as follows:
[1700] ? Objects and their corresponding classes break down complex programming problems into many smaller, simpler problems.
[1701] ? Encapsulation enforces data abstraction through the organization of data into small, independent objects that can communicate with each other. Encapsulation also protects the data in an object from accidental damage, but allows other objects to interact with that data by calling the object's member functions and structures.
[1702] ? Subclassing and inheritance make it possible to extend and modify objects through deriving new kinds of objects from the standard classes available in the system. Thus, new capabilities are created without having to start from scratch.
[1703] ? Polymorphism and multiple inheritance make it possible for different programmers to mix and match characteristics of many different classes and create specialized objects that can still work with related objects in predictable ways.
[1704] ? Class hierarchies and containment hierarchies provide a flexible mechanism for modeling real-world objects and the relationships among them.
[1705] ? Libraries of reusable classes are useful in many situations, but they also have some limitations. For example:
[1706] ? Complexity. In a complex system, the class hierarchies for related classes can become extremely confusing, with many dozens or even hundreds of classes.
[1707] ? Flow of control. A program written with the aid of class libraries is still responsible for the flow of control (i.e., it must control the interactions among all the objects created from a particular library). The programmer has to decide which functions to call at what times for which kinds of objects.
[1708] ? Duplication of effort. Although class libraries allow programmers to use and reuse many small pieces of code, each programmer puts those pieces together in a different way. Two different programmers can use the same set of class libraries to write two programs that do exactly the same thing but whose internal structure (i.e., design) may be quite different, depending on hundreds of small decisions each programmer makes along the way. Inevitably, similar pieces of code end up doing similar things in slightly different ways and do not work as well together as they should.
[1709] Class libraries are very flexible. As programs grow more complex, more programmers are forced to reinvent basic solutions to basic problems over and over again. A relatively new extension of the class library concept is to have a framework of class libraries. This framework is more complex and consists of significant collections of collaborating classes that capture both the small scale patterns and major mechanisms that implement the common requirements and design in a specific application domain. They were first developed to free application programmers from the chores involved in displaying menus, windows, dialog boxes, and other standard user interface elements for personal computers.
[1710] Frameworks also represent a change in the way programmers think about the interaction between the code they write and code written by others. In the early days of procedural programming, the programmer called libraries provided by the operating system to perform certain tasks, but basically the program executed down the page from start to finish, and the programmer was solely responsible for the flow of control. This was appropriate for printing out paychecks, calculating a mathematical table, or solving other problems with a program that executed in just one way.
[1711] The development of graphical user interfaces began to turn this procedural programming arrangement inside out. These interfaces allow the user, rather than program logic, to drive the program and decide when certain actions should be performed. Today, most personal computer software accomplishes this by means of an event loop which monitors the mouse, keyboard, and other sources of external events and calls the appropriate parts of the programmer's code according-to actions that the user performs. The programmer no longer determines the order in which events occur. Instead, a program is divided into separate pieces that are called at unpredictable times and in an unpredictable order. By relinquishing control in this way to users, the developer creates a program that is much easier to use. Nevertheless, individual pieces of the program written by the developer still call libraries provided by the operating system to accomplish certain tasks, and the programmer must still determine the flow of control within each piece after it's called by the event loop. Application code still "sits on top of" the system.
[1712] Even event loop programs require programmers to write a lot of code that should not need to be written separately for every application. The concept of an application framework carries the event loop concept further. Instead of dealing with all the nuts and bolts of constructing basic menus, windows, and dialog boxes and then making these things all work together, programmers using application frameworks start with working application code and basic user interface elements in place. Subsequently, they build from there by replacing some of the generic capabilities of the framework with the specific capabilities of the intended application.
[1713] Application frameworks reduce the total amount of code that a programmer must write from scratch. However, because the framework is really a generic application that displays windows, supports copy and paste, and so on, the programmer can also relinquish control to a greater degree than event loop programs permit. The framework code takes care of almost all event handling and flow of control, and the programmer's code is called only when the framework needs it (e.g., to create or manipulate a data structure).
[1714] A programmer writing a framework program not only relinquishes control to the user (as is also true for event loop programs), but also relinquishes the detailed flow of control within the program to the framework. This approach allows the creation of more complex systems that work together in interesting ways, as opposed to isolated programs with custom code being created over and over again for similar problems.
[1715] Thus, as explained above, a framework basically is a collection of cooperating classes that make up a reusable design solution for a given problem domain. It typically provides objects that define default behavior (e.g., for menus and windows), and programmers use it by inheriting some of that default behavior and overriding other behavior so that the framework calls application code at the appropriate times. There are three main differences between frameworks and class libraries:
[1716] ? Behavior versus protocol. Class libraries are essentially collections of behaviors that you can call when you want those individual behaviors in your program. A framework, on the other hand, provides not only behavior but also the protocol or set of rules that govern the ways in which behaviors can be combined, including rules for what a programmer is supposed to provide versus what the framework provides.
[1717] ? Call versus override. With a class library, the code the programmer instantiates objects and calls their member functions. It's possible to instantiate and call objects in the same way with a framework (i.e., to treat the framework as a class library), but to take full advantage of a framework's reusable design, a programmer typically writes code that overrides and is called by the framework. The framework manages the flow of control among its objects. Writing a program involves dividing responsibilities among the various pieces of software that are called by the framework rather than specifying how the different pieces should work together.
[1718] ? Implementation versus design. With class libraries, programmers reuse only implementations, whereas with frameworks, they reuse design. A framework embodies the way a family of related programs or pieces of software work. It represents a generic design solution that can be adapted to a variety of specific problems in a given domain. For example, a single framework can embody the way a user interface works, even though two different user interfaces created with the same framework might solve quite different interface problems.
[1719] B. Telephony Over The Internet
[1720] Voice over the Internet has become an inexpensive hobbyist commodity. Several firms are evolving this technology to include interworking with the PSTN. This presents both a challenge and an opportunity for established carriers like MCI and BT especially in the International Direct Distance Dialing (IDDD) arena. This discussion explores how a carrier class service could be offered based on this evolving technology. Of particular interest are ways to permit interworking between the PSTN and the Internet using 1 plus dialing.
[1721] The introductory discussion considers the technical requirements to support PC to PC connectivity in a more robust manner than presently offered, in addition to the technical requirements for a PSTN to Internet voice gateway. Consideration is given to how calls can be placed from PCs to a PSTN destination and visa versa. The case of PSTN to PSTN communications, using the Internet as a long distance network is also explored.
[1722] It is shown how such services can be offered in a way that will complement existing PSTN services, offering lower prices for a lower quality of service. At issue in the longer term is the steady improvement in quality for Internet telephony and whether this will ultimately prove competitive with conventional voice services.
[1723] 1. Introduction
[1724] In the mid-late 1970s, experiments in the transmission of voice over the Internet were conducted as part of an ongoing program of research sponsored by the US Defense Advanced Research Projects Agency. In the mid-1980s, UNIX-based workstations were used to conduct regular audio/video conferencing sessions, in modest quantities, over the Internet. These experimental applications were extended in the late 1980s with larger scale, one-way multicasting of voice and video. In 1995 a small company, VocalTec (www.vocaltec.com), introduced an inexpensive software package that was capable of providing two way voice communications between multi-media PCs connected to the Internet. Thus was born a new generation of telephony over the Internet.
[1725] The first software package, and its immediate followers, provided a hobbyist tool. A meeting place based on a Internet Relay Chat "room" (IRC) was used to establish point to point connections between end stations for the voice transfer. This resulted in chance meetings, as is common in chat rooms, or a prearranged meeting, if the parties coordinated ahead of time, by email or other means.
[1726] a) How it Works
[1727] A user with a multi-media PC and an Internet connection can add the Internet Telephony capability by loading a small software package. In the case of VocalTec, the package makes a connection to the meeting place (IRC server), based on a modified chat server. At the IRC the user sees a list of all other users connected to the IRC.
[1728] The user calls another user by clicking on his name. The IRC responds by sending the IP address of the called party. For dial in users of the Internet, an IP address is assigned at dial in time, and consequently will change between dial in sessions. If the destination is not already engaged in a voice connection, its PC beeps a ring signal. The called user can answer the phone with a mouse click, and the calling party then begins sending traffic directly to the IP address of the called party. A multi-media microphone and speakers built into or attached to the PC are used as a speakerphone. The speaker's voice is digitized, compressed and packetized for transmission across the Internet. At the other end it is decompressed and converted to sound through the PC's speakers.
[1729] b) Implications
[1730] Telephony over the Internet offers users a low cost service, that is distance and border insensitive. For the current cost of Internet access (at low hourly rates, or in some cases unlimited usage for a flat fee) the caller can hold a voice conversation with another PC user connected to the Internet. The called party contributes to the cost of the conversation by paying for his Internet access. In the case that one or both ends are LAN connected to the Internet by leased lines the call is free of additional charges. All of this is in contrast to the cost of a conventional long distance, possibly international, call.
[1731] c) Quality of Service
[1732] The voice quality across the Internet is good, but not as good as typical telephone toll quality. In addition, there are significant delays experienced during the conversation. Trying to interrupt a speaker in such an environment is problematic. Delay and quality variations are as much a consequence of distance and available capacity as they are a function of compression, buffering and packetizing time.
[1733] Delays in the voice transmission are attributable to several factors. One of the biggest contributors to delays is the sound card used. The first sound cards were half duplex and were designed for playback of recorded audio. Long audio data buffers which helped ensure uninterrupted audio playback introduced real time delays. Sound card based delays are being reduced over time as full duplex cards designed for "speakerphone" applications are brought to the market.
[1734] Other delays are inherent in the access line speeds (typically 14.4-28.8 kbps for dial-up internet access) and in the packet forwarding delays in the Internet. Also there is delay inherent in filling a packet with digitized encoded audio. For example, to fill a packet with 90 ms of digitized audio, the application must wait at least 90 ms to receive the audio to digitize. Shorter packets reduce packet-filling delays, but increase overhead by increasing the packet header to packet payload data ratio. The increased overhead also increases the bandwidth demands for the application, so that an application which uses short packets may not be able to operate on a 14.4 kbps dial-up connection. LAN-based PCs suffer less delay, but everyone is subject to variable delays which can be annoying.
[1735] Lastly, there are delays inherent in audio codecs. Codec delays can vary from 5 to 30 ms for encoding or decoding. Despite the higher latencies associated with internet telephony, the price is right, and this form of voice communication appears to be gaining in popularity.
[1736] 2. IP Phone as a Commercial Service
[1737] IP telephony technology is here whether the established carriers like it or not. Clearly the use of the Internet to provide international voice calls is a potential threat to the traditional International Direct Distance Dialing (IDDD) revenue stream. Although it may be several years before there is an appreciable revenue impact, it cannot be stopped, except perhaps within national borders on the basis of regulation. The best defense by the carriers is to offer the service themselves in an industrial strength fashion. To do this requires an improved call setup facility and an interface to the PSTN.
[1738] Facilitating PC to PC connections is useful for cases in which the voice conversation needs to be conducted during a simultaneous Internet data packet communication, and the parties don't have access to separate telephone facilities. Dial-up Internet subscribers with only one access circuit might find themselves in that position. Cost considerations may also play a role in dictating the use of PC to PC telephony. The larger use of this technology will occur when the Internet can be used in place of the long distance network to interconnect ordinary telephone hand sets. The number of multi- media Internet connected PCs in the world (estimated at 10 million) is minuscule compared to the number of subscriber lines worldwide (estimated at 660 million). This service is in the planning stages of several companies.
[1739] In the sections below we look at each of the end point combinations possible in a full Internet telephony service. The most important aspects relate to the PSTN to Internet gateway capabilities. Of particular interest is the possibility of providing the PSTN caller with one-step dialing to his called party. The one-step dialing solutions discussed below are in the context of the North American numbering plan. There are essentially four cases:
[1740] 1. PC to PC;
[1741] 2. PC to PSTN;
[1742] 3. PSTN to PC; and
[1743] 4. PSTN to PSTN.
[1744] The first case is addressed by today's IP Phone software. The second and third case are similar but not identical and each requires a gateway between the PSTN and the Internet. The last case uses the Internet as a long distance network for two PSTN telephones.
[1745] a) PC to PC
[1746] (1) Directory Service
[1747] To facilitate PC to PC Internet Telephony a directory service is needed to find the IP address of the called party based on a name presented by the calling party Early internet telephony software utilized a modified internet chat server as a meeting place. More recently, internet telephony software is replacing the chat server with a directory service which will uniquely identify internet telephone users (perhaps by email address). To receive calls, customers would register with the directory service (for a fee, with recurring charges) and would make their location (IP address) known to the directory system whenever they connect to the Internet and want to be available for calls. The best way to accomplish automatic notification is to get agreement between the vendors of IP phone software on a protocol to notify the directory service whenever the software is started (automatic presence notification). It would also be desirable, as as at option, to find a way to automatically invoke the IP phone software when the IP stack is started.
[1748] The directory service is envisioned as a distributed system, somewhat like the Internet Domain Name System, for scalability. This is not to imply, necessarily, the usergfoo.com format for user identification. Theoretically only the called parties need to be registered. If the calling party is not registered, then the charge for the call (if there is one) could be made to the called party (a collect call). Alternatively, we can insist that the caller also be registered in the directory and billed through that mechanism (this is desirable since we charge for the registration and avoid the complications that collect calls require). A charge for the call setup is billed, but not for the duration, over and above the usual Internet charges. Duration charges already apply to the dial up Internet user and Internet usage charges, both for dial up and dedicated usage, are probably not too far away.
[1749] Collect calls from a registered user may be required to meet market demand. A scheme for identifying such calls to the called party must be devised, along with a mechanism for the called party to accept or reject the collect call. The directory service will track the ability of the called software to support this feature by version number (or, alternatively, this could be a matter for online negotiation between the IP telephony software packages). In the event of collect calls (assuming the caller is not registered), the caller could claim to be anyone she chooses. The directory service will force the caller to take on a temporary "assigned" identity (for the duration of the call) so the called party will know this is an unverified caller. Since IP addresses are not necessarily fixed, one cannot rely on them to identify parties.
[1750] (2) Interoperability
[1751] Nearly all IP phone software packages on the market today use different voice encoding and protocols to exchange the voice information. To facilitate useful connections the directory will store the type and version (and possibly options) of Internet phone software being used. To make this work effectively software vendors will report this information automatically to the directory service. This information will be used to determine interoperability when a call is placed. If the parties cannot interoperate, an appropriate message must be sent to the caller. As an alternative, or in addition to registration of software type, a negotiation protocol could be devised to determine interoperability on the fly, but all packages would have to "speak" it.
[1752] There is a question of whether translations between IP phone encoding can be performed with acceptable quality to the end user. Such a service could have a duration and or volume fee associated with it, which might limit the desirability of its use. Also, after a shake out period we expect only a few different schemes to exist and they will have interoperability, perhaps through an industry agreed lowest common denominator compression and signaling protocol. So far, all the IP phone software vendors we have contacted are in favor of an Esperanto that will permit interoperability. If this comes to pass the life span of the translation services will be short, probably making them not economically attractive.
[1753] We can help the major software vendors seek consensus on a "common" compression scheme and signaling protocol that will provide the needed interoperability. Once the major vendors support this method the others will follow. This is already happening, with the recent announcements from Intel, Microsoft, Netscape, and VocalTec that they will all support the H.323 standard in coming months. This can be automatically detected at call setup time. The directory service would keep track of which versions of which software can interoperate. To facilitate this functionality the automatic notification of presence should include the current software version. This way upgrades can be dynamically noted in the directory service. Some scheme must also be defined to allow registration information to be passed between software packages so if a user switches packages she is able to move the registration information to the new application. There is no reason to object if the user has two applications each with the same registration information. The directory service will know what the user is currently running as part of the automatic presence notification. This will cause a problem only if the user can run more than one IP phone package at the same time. If the market requires this ability the directory service could be adapted to deal with it. The problem could also be overcome through the use of negotiation methods between interacting IP phone software packages.
[1754] (3) Call Progress Signaling
[1755] If the user is reachable through the directory system, but is currently engaged in a voice connection, then a call waiting message (with caller ID, something which is not available in the PSTN call waiting service) is sent to the called party and a corresponding message is sent back to the caller.
[1756] If the user is reachable through the directory system, but is currently not running his voice software (IP address responds, but not the application—see below for verification that this is the party in question) then an appropriate message is returned to the caller. (As an option an email could be sent to the called party to alert him to the call attempt. An additional option would be to allow the caller to enter a voice message and attach the "voice mail" to the email. The service could also signal the caller to indicate: busy, unreachable, active but ignored call waiting, etc. Other notification methods to the called party can also be offered, such as FAX or paging. In each case, the notification can include the caller's identity, when known.) Once the directory system is distributed it will be necessary to query the other copies if contact cannot be made based on local information. This system provides the ability to have various forms of notification, and to control the parameters of those forms.
[1757] (4) Party Identification
[1758] A critical question is how will the directory service know that a called party is no longer where she was last reported (i.e., has "gone away"). The dialed in party might drop off the network in a variety of ways (dialed line dropped, PC hung, Terminal Server crashed) without the ability to explicitly inform the directory service of his change in status. Worse yet, the user might have left the network and another user with a voice application might be assigned the same IP address. (This is OK if the new caller is a registered user with automatic presence notification; the directory service could then detect the duplicate IP address. There may still be some timing problems between distributed parts of the directory service.) Therefore, some scheme must exist for the directory service to determine that the customer is still at the last announced location.
[1759] One approach to this is to implement a shared secret with the application, created at registration time. Whenever the directory system is contacted by the software (such as automatic presence notification or call initialization) or attempts to contact the called party at the last known location, it can send a challenge (like CHAP) to the application and verify the response. Such a scheme eliminates the need for announcing "I am no longer here", or wasteful keep alive messages. A customer can disconnect or turn off his IP phone application at any time without concern for notification to the directory system. If multiple IP phone applications are supported, by the directory service, each may do the challenge differently.
[1760] (5) Other Services
[1761] Encrypted internet telephone conversations will require a consensus from the software vendors to minimize the number of encryption setup mechanisms. This will be another interoperability resolution function for the directory service. The directory service can provide support for public key applications and can provide public key certificates issued by suitable certificate authorities.
[1762] The user can also specify on the directory service, that his PC be called (dial out) if she is not currently on-line. Charges for the dial out can be billed to the called party, just as would happen for call forwarding in POTS. The call detail record (CDR) for the dial out needs to be associated with the call detail of an entity in the IP Phone system (the called party). Note that this is different than the PC to PSTN case in that no translation of IP encoded voice to PCM is required, indeed the dial out will use TCP/IP over PPP. If the dial out fails an appropriate message is sent back.
[1763] The dial out could be domestic or international. It is unlikely that the international case will exist in practice due to the cost. However, there is nothing to preclude that case and it requires no additional functionality to perform.
[1764] b) PC to PSTN
[1765] The PSTN to Internet gateway must support translating PCM to multiple encoding schemes to interact with software from various vendors. Alternatively the common compression scheme could be used once it is implemented. Where possible, the best scheme, from a quality stand point, should be used. In many cases it will be the software vendor's proprietary version. To accomplish that, telcos will need to license the technology from selected vendors. Some vendors will do the work needed to make their scheme work on telco platforms.
[1766] (1) Domestic PSTN Destination
[1767] The PC caller needs to be registered to place calls to the PSTN. The only exception to this would be if collect calls from the Internet are to be allowed. This will add complications with respect to billing. To call a PSTN destination the PC caller specifies a domestic E. 164 address. The directory system maps that address to an Internet dial out unit based on the NPA-NXX. The expectation is that the dial out unit will be close to the destination and therefore will be a local call. One problem is how to handle the case where there is no "local" dial out unit. Another problem is what to do if the "local" out dial unit is full or otherwise not available. Three approaches are possible. One approach is to offer the dial out service only when local calls are possible. A second approach is to send a message back to the caller to inform him that a long distance call must be placed on his behalf and request permission to incur these charges. A third approach is to place the call regardless and with no notification. Each of these cases requires a way to correlate the cost of the dial out call (PSTN CDR) with the billing record of the call originator (via the directory service).
[1768] The third approach will probably add to the customer support load and result in unhappy customers. The first approach is simple but restrictive. Most users are expected to be very cost conscious, and so might be satisfied with approach one. Approach two affords flexibility for the times the customer wants to proceed anyway, but it adds complexity to the operation. A possible compromise is to use approach one, which will reject the call for the reason that no local out dial is available. We could also add an attribute in the call request that means "I don't care if this ends up as a long distance call." In this case the caller who was rejected, but wants to place the call anyway makes a second call attempt with this attribute set. For customers with money to spare, all PSTN calls could be made with that attribute set.
[1769] Placing domestic PSTN calls supports the international calling requirement for Internet originated calls from Internet locations outside the US.
[1770] (2) International PSTN Destinations
[1771] Calls to an international PSTN station can be done in one of two ways. First, an international call could be placed from a domestic dial out station. This is not an attractive service since it saves no money over the customer making an international telephone call himself. Second, the Internet can be used to carry the call to the destination country and a "local" dial out can be made there. This situation is problematic for it must be agreed to by the carrier at the international destination. This case may be viable in one of two ways. Both ways require a partner at the international destination. One option would be to use a local carrier in the destination country as the partner. A second option would be to use an Internet service provider, or some other service provider connected to the Internet in the destination country.
[1772] c) PSTN to PC
[1773] This case appears to be of least interest, although it has some application and is presented here for completeness.
[1774] As noted in the PC to PSTN case the PSTN to Internet gateway will need to support translating PCM to multiple encoding schemes to interwork with software from various vendors. The directory service is required to identify the called PC. Automatic notification of presence is important to keep the called party reachable. The PSTN caller need not be registered with the directory service, for caller billing will be based on PSTN information. The caller has an E.164 address that is "constant" and can be used to return calls as well as to do billing. Presumably we can deliver the calling number to the called party as an indication of who is calling. The calling number will not always be available, for technological or privacy reasons. It must be possible to signal the PC software that this is a PSTN call and provide the E.164 number or indicate that it is unavailable. The service can be based on charging the calling phone. This can be done as if the Internet were the long distance portion of the call.
[1775] This is possible with a second dial tone. If an 800 or local dial service is used it is necessary for the caller to enter billing information. Alternatively a 900 service will allow PSTN caller-based billing. In either case the caller will need to specify the destination "phone number" after the billing information or after dialing the 900 number.
[1776] A major open issue is how the caller will specify the destination at tne second dial tone. Only touch tones are available at best. To simplify entry we could assign an E.164 address to each directory entry. To avoid confusion with real phone numbers (the PSTN to PSTN case) the numbers need to be under directory control. Perhaps 700 numbers could be used, if there are enough available. Alternatively a special area code could be used. Spelling using the touch tone PAD is a less "user friendly" approach.
[1777] 3. Phone Numbers in the Internet
[1778] The best approach is to have an area code assigned. Not only will this keep future options open, but it allows for simpler dialing from day one. Given a legitimate area code the PSTN caller can directly dial the E.164 address of the PC on the Internet. The telephone system will route the call to an MCI POP where it will be further routed to a PSTN-to-Internet voice gateway. The called number will be used to place the call to the PC, assuming it is on-line and reachable. This allows the PSTN caller to dial the Internet as if it were part of the PSTN. No second dial tone is required and no billing information needs to be entered. The call will be billed to the calling PSTN station, and charges will accrue only if the destination PC answers. Other carriers would be assigned unique area codes and directories should be kept compatible.
[1779] For domestically originated calls, all of the billing information needed to bill the caller is available and the intelligent network service functionality for third party or other billing methods is available via the second dial tone.
[1780] 4. Other Internet Telephony Carriers
[1781] All this will get more complicated when number portability becomes required. It may be desirable to assign a country code to the Internet. Although this would make domestic dialing more complex (it appears that dialing anything other than 1 plus a ten digit number significantly reduces the use of the service) it may have some desirable benefits. In any event the assignment of an area code (or several) and the assignment of a country code are not mutually exclusive. The use of a country code would make dialing more geographically uniform.
[1782] 5. International Access
[1783] It is unlikely that an international call will be made to the US to eni-;er the Internet in the US. If it happens, however, the system will have enough information to do the caller-based billing for this case without any additional functionality.
[1784] Another possibility is that we will (possibly in partnership) set up to handle incoming calls outside the US and enter the Internet in that country to return to the US, or go anywhere else on the Internet. If the partner is a local carrier, then the partner will have the information needed for billing the PSTN caller.
[1785] a) Collect Calls
[1786] PSTN to PC collect calls require several steps. First, the call to the PSTN to Internet gateway must be collect. The collect call could then be signaled in the same way as PC to PC calls. It will be necessary to indicate that the caller is PSTN based and include the calling E.164 address if it is available.
[1787] b) PSTN to PSTN
[1788] The choice of voice compression and protocol scheme for passing voice between PSTN to Internet gateways is entirely under the carrier's control. Various service levels could be offered by varying the compression levels offered. Different charges could be associated with each level. The caller would select a quality level; perhaps by dialing different 800 number services first.
[1789] (1) Domestic Destination
[1790] Neither the calling nor the called parties need be registered with the directory service to place calls across the Internet. The caller dials a PSTN-to-Internet gateway and receives a second dial tone and specifies, using touch tones, the billing information and the destination domestic E.164 address. 900 service could be used as well. The directory service (this could be separate system, but the directory service already has mapping functionality to handle the PC to PSTN dial out case) will be used to map the call to an out dialer to place a local call, if possible. Billing is to the caller and the call detail of the out dial call needs to be associated with the call detail of the inbound caller.
[1791] An immediate question is how to deal with the case where the nearest dial out unit to the number called results in a long distance or toll call, as discussed in PC to PSTN case. The situation here is different to the extent that notification must be by voice, and authorization to do a long distance, or toll call dial out must be made by touch tones. In the event of a long distance dial out the Internet could be skipped altogether and the call could go entirely over the PSTN. It is not clear that there is any cost savings by using the Internet in this case.
[1792] (2) One Step Dialing
[1793] The problem is that the destination PSTN number needs to be entered and, somehow, it needs to be indicated that the destination is to be reached via the Internet rather than the conventional long distance network. This selection criteria can be conveyed according to the following alternatives:
[1794] 1. Assign a new 1OXXX number that is the carrier's I;iternet.
[1795] 2. By subscription.
[1796] The first method allows the caller to select the Internet as the long distance carrier on a call by call basis. The second method makes the Internet the default long distance network. In the second case a customer can return to the carrier's conventional long distance network by dialing the carrier's 1OXXX code.
[1797] The first method has the draw back that the caller must dial an extra five digits. Although many will do this to save money, requiring any extra dialing will reduce the total number of users of the service. The second method avoids the need to dial extra digits, but requires a commitment by the subscriber to predominately use the Internet as his long distance network. The choice is a lower price with a lower quality of service.
[1798] In the PSTN to PSTN case it is possible to consider offering several grades of service at varying prices. These grades will be based on a combination of the encoding scheme and the amount of compression (bandwidth) applied, and will offer lower cost for lower bandwidth utilization.
[1799] To signal the grade of service desired three 1OXXX codes could be used. By subscription a particular grade would be the default and other service grades would be selected by a 1OXXX code.
[1800] (3) Service Quality
[1801] The service quality will be measured by two major factors. First, sound quality, the ability to recognize the caller's voice, and second by the delays that are not present in the PSTN.
[1802] On the first point we can say that most of the offerings available today provide an acceptable level of caller recognition. Delay, however, is another story. PC to PC users experience delays of a half second to two seconds. As noted in the introduction much of the delay can be attributed to the sound cards and the low speed dial access. In the case of PSTN to PSTN service both these factors are removed.
[1803] The use of DSPs in the PSTN to Internet voice gateway will keep compression and protocol processing times very low. The access to the gateway will be at a full 64 kbps on the PSTN side and likely Ethernet on the Internet side. Gateways will typically be located close to the backbone so the router on the Ethernet will likely be connected to the backbone by a T3 line. This combination should provide a level of service with very low delays. Some buffering will be needed to mask the variable delays in the backbone, but that can likely be kept to under a quarter of a second in the domestic carrier backbone.
[1804] The main differentiation of quality of service will be voice recognition which will be related to bandwidth usage. If needed, the proposed IETF Resource reSerVation setup Protocol (RSVP) can be used to assure lower delay variation, but the need for the added complexity of RSVP is yet to be established. Also, questions remain regarding the scalability of RSVP for large-scale internet telephony.
[1805] (4) Costs
[1806] An open question is whether using the Internet for long distance voice in place of the switched telephone network is actually cheaper. Certainly it is priced that way today, but do current prices reflect real costs? Routers are certainly cheaper than telephone switches, and the 10 kbps (or so) that the IP voice software uses (essentially half duplex) is certainly less than the dedicated 128 kbps of a full duplex 64 kbps DS0. Despite these comparisons the question remains.
[1807] Although routers are much cheaper than telephone switches, they have much less capacity. Building large networks with small building blocks gets not only expensive, but quickly reaches points of diminishing returns. We already have seen the Internet backbone get overloaded with the current crop of high end routers, and they are yet to experience the significant traffic increase that a successful Internet Telephony offering would bring. We are saying two things here.
[1808] 1. It is unlikely that the current Internet backbone can support a major traffic increase associated with a successful internet telephony service. We need to wait for the technology of routers to improve.
[1809] 2. The second issue raised above was that of bandwidth usage. Indeed 10 kbps half duplex (a little more when both parties occasionally speak at the same time, but much less during periods of silence) is considerably less than 64 kbps full duplex dedicated capacity. Two points should be noted on this argument.
[1810] First, bandwidth is cheap, at least, when there is spare fiber in the ground. Once the last strand is used the next bit per second is very expensive. Second, on transoceanic routes, where bandwidth is much more expensive, we are already doing bandwidth compression of voice to 9.6 kbps. This is essentially equivalent to the 10 kbps of Internet Telephony.
[1811] Why is IP capacity priced so much cheaper than POTS? The answer is that the pricing difference is partly related to the subsidized history of the Internet. There is a process in motion today, by the Internet backbone providers, to address some of the cost issues of the Internet. The essence of the process is the recognition that the Internet requires a usage charge. Such charges already apply to some dial up users, but typically do not apply to users with dedicated connections.
[1812] If PC to PC Internet Telephony becomes popular, users will tend to keep their PCs connected for long periods. This will make them available to receive calls. It will also drive up hold times on dial in ports. This will have a significant effect on the capital and recurring costs of the Internet.
[1813] (5) Charges
[1814] A directory service must provide the functions described above and collect enough information to bill for the service. A charge can be made for directory service as well as for registration (a one time fee plus a monthly fee), call setup, but probably not for duration. Duration is already charged for the Internet dial in user and is somewhat bundled for the LAN-attached user. Usage charges for Internet service may be coming soon (as discussed above). Duration charges are possible for the incoming and outgoing PSTN segments.
[1815] Incoming PSTN calls may be charged as the long distance segment by using a special area code. Other direct billing options are 900 calls and calling card (or credit card) billing options (both require a second dial tone).
[1816] Requiring all callers (except incoming PSTN calls) to be registered with the directory service will eliminate the immediate need for most collect calling. This will probably not be a great impediment since most users of the IP Phone service will want to receive as well as originate calls, and registration is required for receiving calls. Callers could have unlisted entries which would be entries with an E.164 address, but no name. People given this E.164 address could call the party (from the PSTN or from a PC), as is the case in the present phone system.
[1817] Different compression levels can be used to provide different quality of voice reproduction and at the same time use more or less Internet transit resources. For PC to PC connections the software packages at both ends can negotiate the amount of bandwidth to be used. This negotiation might be facilitated through the directory service.
[1818] (6) Technical Issues
[1819] It will be necessary to coordinate with IP Phone vendors to implement the registration, automatic presence notification, and verification capabilities. We will also need to add the ability to communicate service requests. These will include authorization for collect calls specifying attributes such as "place a dial out call to the PSTN even if it is long distance" and others to be determined.
[1820] Registration with a directory is a required feature that will be illuminated below. Using the DNS model for the distributed directory service will likely facilitate this future requirement. Assignment of a pseudo E.164 number to directory entries will work best if a real area code is used. If each carrier has an area code it will make interworking between the directory systems much easier. An obvious complication will arise when number portability becomes required.
[1821] IP Telephony, in accordance with a preferred embodiment, is here and will stay for at least the near future. A combination of a carrier level service, based on this technology, and a growth in the capacity of routers may lead to the Internet carrying a very significant percentage of future long distance traffic.
[1822] The availability of higher speed Internet access from homes, such as cable modems, will make good quality consumer IP Telephony service more easily attained. The addition of video will further advance the desirability of the service.
[1823] More mundane, but of interest, is FAX services across the Internet. This is very similar to the voice service discussed above. Timing issues related to FAX protocols make this a more difficult offering in some ways.
[1824] Conferencing using digital bridges in the Internet make voice and video services even more attractive. This can be done by taking advantage of the multi-casting technology developed in the Internet world. With multi-casting the cost of providing such services will be reduced.
[1825] C. Internet Telephony Seruices
[1826]FIG. 1C is a block diagram of an internet telephony system in accordance with a preferred embodiment. Processing commences when telephone 200 is utilized to initiate a call by going off hook when a party dials a telephone number. Telephone 200 is typically connected via a conventional two-wire subscriber loop through which analog voice signals are conducted in both directions. One of ordinary skill in the art will readily realize that a phone can be connected via fiber, ISDN or other means without departing from the teaching of the invention. Alternatively, a person could dial a phone number from a computer 210, paging system, video conferencing system or other telephony capable devices. The call enters a Local Exchange Carrier (LEC) 220 which is another name for a Regional Bell Operating Company (RBOC) central switch. The call is terminated by a LEC at a leased Common Business Line (CBL) of an interchange carrier such as MCI. As a result of the termination to the CBL, the MCI Switch 221 receives an offhook indication.
[1827] The Switch 221 responds to the offhook by initiating a DAL Hotline procedure request to the Network Control System (NCS) which is also referred to as a Data Access Point (DAP) 240. The switch 221 is simplified to show it operating on a single DS1 line, but it will be understood that switching among many lines actually occurs so that calls on thousands of individual subscriber lines can be routed through the switch on their way to ultimate destinations. The DAP 240 returns a routing response to the originating switch 221 which instructs the originating switch 221 to route the call to the destination switch 230 or 231. The routing of the call is performed by the DAP 240 translating the transaction information into a specific SWitch ID (SWID) and a specific Terminating Trunk Group (TTG) that corresponds to the route out of the MCI network necessary to arrive at the appropriate destination, in this case either switch 230 or 231. An alternative embodiment of the hybrid network access incorporates the internet access facility into a switch 232. This integrated solution allows the switch 232 to attach directly to the internet 295 which reduces the number of network ports necessary to connect the network to the internet 295. The DAP sends this response information to the originating switch 221 which routes the original call to the correct Terminating Switch 230 or 231. The terminating switch 230 or 23 1then finds the correct Terminating
[1828] Trunk Group (TTG) as indicated in the original DAP response and routes the call to the ISN 250 or directly to the modem pool 270 based on the routing information from the DAP 240. If the call were destined for the Intelligent Services Network (ISN) 250, the DAP 240 would instruct the switch to terminate at switch 230.
[1829] Based upon analysis of the dialed digits, the ISN routes the call to an Audio Response Unit (ARU) 252. The ARU 252 differentiates voice, fax, and modem calls. If the call is a from a modem, then the call is routed to a modem pool 271 for interfacing to an authentication server 291to authenticate the user. If the call is authenticated, then the call is forwarded through the UDP/IP or TCP/IP LAN 281 or other media communication network to the Basic Internet Protocol Platform (BIPP) 295 for further processing and ultimate delivery to a computer or other media capable device.
[1830] If the call is voice, then the ARU prompts the caller for a card number and a terminating number. The card number is validated using a card validation database. Assuming the card number is valid, then if the terminating number is in the US (domestic), then the call would be routed over the current MCI voice lines as it is today. If the terminating number is international, then the call is routed to a CODEC 260 that converts the voice to TCP/IP or UDP/IP and sends it via the LAN 280 to the internet 295. The call is routed through a gateway at the terminating end and ultimately to a phone or other telephony capable device.
[1831]FIG. 1D is a block diagram of a hybrid switch in accordance with a preferred embodiment. Reference numbers have been conserved from FIG. 1C, and an additional block 233 has been added. Block 233 contains the connecting apparatus for attaching the switch directly to the internet or other communication means. The details of the connecting apparatus are presented in FIG. 1E. The principal difference between the hybrid switch of FIG. 1D and the switches presented in FIG. iC is the capability of switch 221 attaching directly to the Internet 295.
[1832]FIG. 1E is a block diagram of the connecting apparatus 233 illustrated in FIG. 1D in accordance with a preferred embodiment. A message bus 234 connects the switch fabric to an internal network 236 and 237. The internal network in turn receives input from a Dynamic Telephony Connection (DTC) 238 and 239 which in turn provides demuxing for signals originating from a plurality of DS1 lines 242, 243, 244 and 245. DS1 lines, described previously, refer to the conventional bit format on the T1 lines.
[1833] To accommodate the rapidly diversifying telephony/media environment, a preferred embodiment utilizes a separate switch connection for the other internal network 237. A Spectrum Peripheral Module (SPM) 247 is utilized to handle telephony/media signals received from a pooled switch matrix 248, 249, 251, 254, 261-268. The pooled switch matrix is managed by the SPM 247 through switch commands through control lines. The SPM 247 is in communication with the service provider's call processing system which determines which of the lines require which type of hybrid switch processing. For example, fax transmissions generate a tone which identifies the transmission as digital data rather than digitized voice. Upon detecting a digital data transmission, the call processing system directs the call circuitry to allow the particular input line to connect through the pooled switch matrix to a corresponding line with the appropriate processing characteristics. Thus, for example, an internet connection would be connected to a TCP/IP Modem line 268 to assure proper processing of the signal before it was passed on through the internal network 237 through the message bus 234 to the originating switch 221 of FIG. 1D.
[1834] Besides facilitating direct connection of a switch to the internet, the pooled switch matrix also increases the flexibility of the switch for accommodating current communication protocols and future communication protocols. Echo cancellation means 261 is efficiently architected into the switch in a manner which permits echo cancellation on an as-needed basis. A relatively small number of echo cancellers can effectively service a relatively large number of individual transmission lines. The pooled switch matrix can be configured to dynamically route either access-side transmissions or network-side transmissions to OC3 demux, DSP processing or other specialized processing emanating from either direction of the switch.
[1835] Moreover, a preferred embodiment as shown in FIG. 1E provides additional system efficiencies such as combining multiplexer stages in a port device on one side of a voice or data circuit switch to enable direct connection of a fiber-optic cable to the multiplexed output of the port device. Moreover, redundancy is architected into the switch through the alternate routes available over CEM 248/249 and RM 251/254 to alternate paths for attaching various communication ports.
[1836] When the switch 221 of FIG. 1D, is connected to the internet 295, the processing is provided as follows. A line from the internet 295 enters the switch through a modem port 268 and enters the pooled switch matrix where demux and other necessary operations are performed before the information is passed to the switch 221 through the internal network 237 and the message bus 234. The modules 261-268 provide plug and play capability for attaching peripherals from various communication disciplines.
[1837]FIG. 1F is a block diagram of a hybrid (internet-telephony) switch in accordance with a preferred embodiment. The hybrid switch 221 switches circuits on a public switched telephone network (PSTN) 256 with TCP/IP or UDP/IP ports on an internet network 295. The hybrid switch 221 is composed of PSTN network interfaces (247, 260), high-speed Internet network interfaces (271, 272, 274), a set of Digital Signal Processor (DSP)s (259, 263), a time-division multiplexed bus 262, and a high-speed data bus 275.
[1838] The hybrid internet telephony switch 221 grows out of the marriage of router architectures with circuit switching architectures. A call arriving on the PSTN interface 257 is initiated using ISDN User Part (ISUP) signaling, with an Initial Address Message (IAM), containing a called party number and optional calling party number. The PSTN interface 257 transfers the IAM to the host processor 270. The host processor 270 examines the PSTN network interface of origin, the called party number and other IAM parameters, and selects an outgoing network interface for the call. The selection of the outgoing network interface is made on the basis of routing tables. The switch 221 may also query an external Service Control Point (SCP) 276 on the internet to request routing instructions. Routing instructions, whether derived locally on the switch 221 or derived from the SCP 276, may be defined in terms of a subnet to use to reach a particular destination.
[1839] Like a router, each of the network interfaces in the switch 221 is labeled with a subnet address. Internet Protocol (IP) addresses contain the subnet address on which the computer is located. PSTN addresses do not contain IP subnet addresses, so subnets are mapped to PSTN area codes and exchanges. The switch 221 selects routes to IP addresses and PSTN addresses by selecting an interface to a subnet which will take the packets closer to the destination subnet or local switch.
[1840] The call can egress the switch via another PSTN interface 258, or can egress the switch via a high-speed internet network interface 273. If the call egresses the switch via the PSTN interface 258, the call can egress as a standard PCM Audio call, or can egress the switch as a modem call carrying compressed digital audio.
[1841] In the case where the call egresses the switch 221 as a standard PCM audio call, the PCM audic is switched from PSTN Interface 257 to PSTN Interface 258 using the TDM bus 260. Similarly, PCM audio is switched from PSTN Interface 258 to PSTN Interface 257 using the TDM bus 260.
[1842] In the case where the call egresses the switch 221 as a modem call carrying compressed digital audio, the switch 221 can initiate an outbound call to a PSTN number through a PSTN interface 258, and attach across the TDM Bus 260 a DSP resource 259 acting as a modem. Once a modem session is established with the destination, the incoming PCM audio on PSTN interface 257 can be attached to a DSP Resource 263 acting as an audio codec to compress the audio. Example audio formats include ITUG. 729 and G.723. The compressed audio is packetized into Point to Point Protocol (PPP) packets on the DSP 263, and transferred to DSP 259 for modem delivery over the PSTN Interface 258.
[1843] In the case where the call egresses the switch 221 on a high speed internet interface 272, the switch 221 attaches the PSTN Interface 257 to the DSP resource 263 acting as an audio codec to compress the PCM audio, and packetize the audio into UDP/IP packets for transmission over the Internet network. The UDP/IP packets are transferred from the DSP resource 263 over the high-speed data bus 275 to the high-speed internet network interface 272.
[1844]FIG. 1G is a block diagram showing the software processes involved in the hybrid internet telephony switch 221. Packets received on the internet network interface 296 are transferred to the packet classifier 293. The packet classifier 293 determines whether the packet is a normal IP packet, or is part of a routing protocol (ARP, RARP, RIP, OSPF, BGP, CIDR) or management protocol (ICMP). Routing and management protocol packets are handed off to the Routing Daemon 294. The Routing Daemon 294 maintains routing tables for the use of the packet classifier 293 and packet scheduler 298. Packets classified as normal IP packets are transferred either to the packetizer/depacketizer 292 or to the packet scheduler 298. Packets to be converted to PCM audio are transferred to the packetizer/depacketizer 292. The packetizer/depacketizer takes packet contents and hands them to the codec 291, which converts compressed audio into PCM Audio, then transfers PCM audio to the PSTN Interface 290.
[1845] Normal IP packets to be sent to other internet devices are handed by the packet classifier 293 to the packet scheduler 298, which selects the outgoing network interface for the packet based on the routing tables. The packets are placed upon an outbound packet queue for the selected outgoing network interface, and the packets are transferred to the high speed network interface 296 for delivery across the internet 295.
[1846] D. Call Processing
[1847] This section describes how calls are processed in the context of the networks described above.
[1848] 1. VNET Call Processing
[1849]FIG. 10A illustrates a Public Switched Network (PSTN) 1000 comprising a local exchange (LEC) 1020 through which a calling party uses a telephone 1021 or computer 1030 to gain access to a switched network including a plurality of MCI switches 1011, 1010. Directory services for routing telephone calls and other information is provided by the directory services 1031 which is shared between the Public Branch Exchanges 1041, 1040 and the PSTN. This set of scenarios allows a subscriber to use either a PC, telephone or both to make or receive VNET calls. In this service, the subscriber may have the following equipment:
[1850] A telephone that uses VNET routing is available today in MCI's network. In this case, VNET calls arriving in the MCI PSTN network using the subscriber's VNET number are routed with the assistance of the DAP just as they are routed today.
[1851] A PC that is capable of Internet telephony. Calls are routed into and out of this PC with the assistance of an Internet or Intranet Directory Service that tracks the logged-in status and current IP address of the VNET user.
[1852] A PC and a telephone is used to receive and make calls. In this case, a user profile will contain information that allows the DAP and Directory Service to make a determination whether to send an incoming call to the PC or to the telephone. For example, the user may always want calls to go to their PC when they are logged-in and to their phone at all other times. Or, they may want their calls to always go to their PC during normal work hours and to their phone at other times. This type of control over the decision to send incoming calls to a phone or PC may be controlled by the subscriber.
[1853] The following scenarios apply to this type of service.
[1854] 1. A PC to PC call where the Directory service is queried for the location of the terminating PC:
[1855] PCs connected to an Intranet using the Intranet as transport.
[1856] Both PC's connected to a corporate Intranet via dial up access.
[1857] Both PCs on separate Intranets with the connection made through the Internet.
[1858] Both PCs on the Internet through a dial-up connection.
[1859] One PC directly connected to a corporate Intranet and the other PC using a dial-up connection to the Internet.
[1860] One PC using a dial up connection to a corporate Intranet and the other PC using a dial-up connection to the Internet.
[1861] Both PCs on separate Intranets with the connection made through the PSTN.
[1862] One or both PCs connected to a corporate Intranet using dial-up access.
[1863] One or both of the PCs connected to an Internet Service Provider.
[1864] One or both of the ITGs as an in-network element.
[1865] 2. A PC to phone call where a directory service is queried to determine that the terminating VNET is a phone. The PC then contacts an Internet Telephony Gateway to place a call to the terminating phone.
[1866] PC on an intranet using a private ITG connected to the PSTN with the ITG as an out of network element. The destination phone is connected to a PBX.
[1867] The PC may also be using a public ITG that must be access through the Internet.
[1868] The PC may be connected to the corporate Intranet using dial-up access.
[1869] PC on an intranet using a private ITG connected to the PSTN with the ITG as an in-network element. The destination phone is connected to a PBX.
[1870] The PC may also be using a public ITG that must be accessed through the Internet.
[1871] The PC may be connected to the corporate Intranet using dial-up access.
[1872] PC on an intranet using a private ITG connected to the PSTN with the ITG as an in-network element. The destination phone is connected to the PSTN.
[1873] The PC may also be using a public ITG that must be accessed through the Internet.
[1874] The PC may be connected to the corporate Intranet using dial-up access.
[1875] The ITG may be an in-network element.
[1876] PC on an intranet using a private ITG connected to a PBX with the traffic carried over the Intranet.
[1877] PC is at a different site than the destination phone with the traffic carried over the Internet or intranet.
[1878] The PC may be using a dial-up connection to the corporate Intranet.
[1879] 1. A phone to PC call where the DAP or PBX triggers out to the Internet Directory Service to identify the terminating IP address and ITG for routing the call. The call is then routed through the PSTN to an ITG and a connection is made from the ITG to the destination PC. Possible Variations: Same variations as the PC to phone.
[1880] 2. A Phone to Phone call where the DAP or PBX must query the Directory Service to determine whether the call should be terminated to the subscriber's phone or PC.
[1881] Possible Variations:
[1882] Both Phones are on a PBX;
[1883] One phone is on a PBX and the other phone is on the PSTN; and
[1884] Both phones are on the PSTN.
[1885] For each of these variations, the DAP and Directory Service may be a Hsingle entity or they may be separate entities. Also, the directory service may be a private service or it may be a shared service. Each of the scenarios will be discussed below with reference to a call flow description in accordance with a preferred embodiment. A description of the block elements associated with each of the call flow diagrams is presented below to assist in understanding the embodiments.
[1886] E. Re-usable Call Flow Blocks
[1887] 1. The user for a PC connects their computer to an IP network, turns on the computer and starts an IP telephony software package. The software package sends a message to a directory service to register the computer as "on-line" and available to receive calls. This on- line registration message would most likely be sent to the directory service in an encrypted format for security. The encryption would be based upon an common key shared between the PC and the directory service. This message contains the following information:
[1888] Some sort of identification of the computer or virtual private network number that may be used to address this computer. In this VNET scenario, this is the VNET number assigned to the individual using this PC. This information will be used to identify the customer profile associated with this user. It may also be some identification such as name, employee id, or any unique ID which the directory service can associate with a VNET customer profile.
[1889] A password or some other mechanism for authenticating the user identified by the VNET number.
[1890] The IP address identifying the port that is being used to connect this computer to the network. This address will be used by other IP telephony software packages to establish a connection to this computer.
[1891] The message may contain additional information about the specifics of the software package or PC being used for IP telephony and the configuration/capabilities of the software or PC. As an example it might be important for a calling PC to know what type of compression algorithms are being used, or other capabilities of the software or hardware that might affect the ability of other users to connect to them or use special features during a connection. The location of the directory service to receive this "on-line" message will be determined by the data distribution implementation for this customer. In some cases this may be a private database for a company or organization subscribing to a VNET service, in other cases it might be a national or worldwide database for all customers of a service provider (MCI). This location is configured in the telephony software package running on the PC.
[1892] 2. When the directory service receives this message from the PC, it validates the user by using the VNET number to look up a user profile and comparing the password in the profile to the password received. Once the user has been validated, the directory service will update the profile entry associated with the VNET number (or other unique ID) to indicate that the user is "on-line" and is located at the specified IP address. The directory service will also update the profile with the configuration data sent during the login request. Upon successful update of theprofile directory service sends a response back to the specified IP address indicating that the message was received and processed. This acknowledgment message may also contain some sort of security or encryption key to guarantee secure communication with the directory service when issuing additional commands. When the PC receives this response message it may choose to notify the user via a visual or audible indicator.
[1893] Variation for On-line registration
[1894] The call flow segment shown earlier in this section showed a PC on-line registration where the PC simply sends a password to the directory service to log-on. A variation for this log-on procedure would be the following call flow segment where the directory service presents a challenge and the PC user must respond to the challenge to complete the log-in sequence. This variation on the log-in sequence is not shown in any of the call flows contained within this document, but it could be used in any of them.
[1895] 1. The user for a PC connects their computer to an lP network, turns on the computer and starts an IP telephony software package. The software package sends a message to a directory service to register the computer as "on-line" and available to receive calls. This on-line registration message would most likely be sent to the directory service in an encrypted format for security. The encryption would be based upon an common key shared between the PC and the directory service. This message contains the following information:
[1896] Some sort of identification of the computer or virtual private network number that may be used to address this computer. In this VNET scenario, this is the VNET number assigned to the individual using this PC. This information will be used to identify the customer profile associated with this user. It may also be some identification such as name, employee id, or any unique ID which the directory service can associate with a VNET customer profile.
[1897] The IP address identifying the port that is being used to connect this computer to the network. This address will be used by other IP telephony software packages to establish a connection to this computer.
[1898] The message may contain additional information about the specifics of the software package or PC being used for IP telephony and the configuration/capabilities of the software or PC. As an example it might be important for a calling PC to know what type of compression algorithms are being used, or other capabilities of the software or hardware that might affect the ability of other users to connect to them or use special features during a connection.
[1899] The location of the directory service to receive this "on-line" message will be determined by the data distribution implementation for this customer. In some cases this may be a private database for a company or organization subscribing to a VNET service, in other cases it might be a national or worldwide database for all customers of a service provider (MCI). This location is configured in the telephony software package running on the PC.
[1900] 2. In this scenario the PC did not provide a password in the initial registration message. This is because the directory service uses a challenge/response registration process. In this case, the directory service will use a shared key to calculate a challenge that will be presented to the PC
[1901] 3. The PC receives this challenge and presents it to the user of the PC. The PC user uses the shared key to calculate a response to the challenge and send the response back to the directory service.
[1902] 4. When the directory service receives this response from the PC, it validates the user. Once the user has been validated, the directory service will update the profile entry associated with the VNET number (or other unique ID) to indicate that the user is "on-line" and is located at the specified IP address. The directory service will also update the profile with the configuration data sent during the login request. Upon successful update of theprofile directory service sends a response back to the specified IP address indicating that the message was received and processed. This acknowledgment message may also contain some sort of security or encryption key to guarantee secure communication with the directory service when issuing additional commands. When the PC receives this response message it may choose to notify the user via a visual or audible indicator.
[1903] 1. A PC uses an Internet telephony software package to attempt to connect to a VNET number. To establish this connection, the user of the PC dials the VNET number (or other unique ID such as name, employee ID, etc). Once the telephony software package has identified this call as a VNET type call, it will send a translation request to the directory service. At a minimum, this translation request will contain the following information:
[1904] The IP address of the computer sending this request
[1905] The VNET number of the PC sending this request.
[1906] The Vnet number (or other ID) of the computer to be dialed.
[1907] A requested configuration for the connection. For example, the calling PC might want to use white-board capabilities within the telephony software package and may wish to verify this capability on the destination PC before establishing a connection. If the VNET number does not translate to a PC, this configuration information may not provide any benefit, but at the time of sending this request the user does not know whether the VNET number will translate to a PC or phone.
[1908] 2. When the directory service receives this message, it uses the Vnet number (or other ID) to determine if the user associated with that VNET number (or other ID) is "on-line" and to identify the IP address of the location where the computer may be contacted. This directory service may also contain and make use of features like time of day routing, day of week routing, ANI screening, etc. If the VNET number translates into a PC that is "on-line", the directory service will compare the configuration information in this request to the configuration information available in the profile for the destination PC. When the directory service returns the response to the translation request from the originating PC, the response will include
[1909] The registered "on-line" IP address of the destination PC. This is the IP address that the originating PC may use to contact the destination PC
[1910] Configuration information indicating the capabilities of the destination PC and maybe some information about which capabilities are compatible between the origination and destination PC.
[1911] If the VNET number translates to a number that must be dialed through the PSTN, the response message to the PC will contain the following
[1912] An IP address of an Internet Telephony gateway that may be used to get this call onto MCI's PSTN. The selection of this gateway may be based upon a number of selection algorithms. This association between the caller and the ITG to be used is made based upon information in the profile contained within the directory service.
[1913] A VNET number to be dialed by the ITG to contact the destination phone. In the case of this call flow this is the VNET number of the destination phone. This allows the call to use the existing VNET translation and routing mechanisms provided by the DAP.
[1914] If the VNET number translates to a phone which is reachable through a private ITG connected to the customer's PBX, the directory service will return the following.
[1915] The VNET number of an ITG gateway that is connected to the PBX serving the destination phone. This association between the destination phone the ITG connected to its serving PBX is made by the directory service.
[1916] The VNET number to be dialed by the ITG when it offers the call to the PBX. In most cases this will just be an extension number.
[1917] 1. A PC uses its telephony software package to send a "connection" message to an ITG. This IP address is usually returned from the directory service in response to a VNET translation. The specific format and contents of this message is dependent upon the software sending the message or the ITG software to receive the message. This message may contain information identifying the user of the PC or it may contain information specifying the parameters associated with the requested connection.
[1918] 2. The ITG responds to the connect message by responding to the message with an acknowledgment that a call has been received. This step of call setup may not be necessary for a PC calling an ITG, but it is shown here in an attempt to maintain a consistent call setup procedure that is independent of whether the PC is connecting to an ITG or to another PC. When connecting to a PC, this step of the procedure allows the calling PC to know that the destination PC is ringing.
[1919] 3. The ITG accepts the call.
[1920] 4. A voice path is established between the ITG and the PC.
[1921] 1. An ITG uses its telephony software to send a "connection" message to a PC. The ITG must know the IP address of the PC to which it is connecting. The specific format and contents of this message is dependent upon the ITG software sending the message or the PC software to receive the message. This message may contain information identifying this call as one being offered from an ITG, or it may contain information specifying the requested configuration for the call (i.e. voice only call).
[1922] 2. The message from step 1 is received by the PC and the receipt of this message is acknowledged by sending a message back to the ITG indicating that the PC is offering the call to the user of the PC
[1923] 3. The user of the PC answers to call and a message is sent back to the originating PC indicating that the call has been accepted.
[1924] 4. A voice path is established between the ITG and the PC.
[1925] 5. VNET PC to PC Call Flow Description
[1926] The user for PC12 1051 connects the computer to an Internet Protocol (IP) network 1071, turns on the computer and starts an IP telephony software protocol system. The system software transmits a message to a directory service 1031 to register the computer as "on-line" and available to receive calls. This message contains IP address identifying the connection that is being used to connect this computer to the network. This address may be used by other IP telephony software packages to establish a connection to this computer. The address comprises an identification of the computer or virtual private network number that may be used to address this computer 1051. In this VNET scenario, the address is a VNET number assigned to the individual using this PC. VNET refers to a virtual network in which a particular set of telephone numbers is supported as a private network of numbers that can exchange calls. Many corporations currently buy communication time on a trunk that is utilized as a private communication channel for placing and receiving inter-company calls. The address may also be some identification such as name, employee id, or any other unique ID.
[1927] The message may contain additional information regarding the specifics of the system software or the hardware configuration of PC11 1051 utilized for IP telephony. As an example, it is important for a calling PC to know what type of compression algorithms are supported and active in the current communication, or other capabilities of the software or hardware that might affect the ability of other users to connect or use special feature during a connection.
[1928] 6. Determining best choice for Internet client selection of an Internet Telephony Gateway server on the Internet:
[1929]FIG. 10B illustrates an internet routing network in accordance with a preferred embodiment. If a client computer 1080 on the Internet needs to connect to an Internet Telephony Gateway 1084, the ideal choice for an Gateway to select can fall into two categories, depending on the needs of the client:
[1930] If the client 1080 needs to place a telephone call to a regular PSTN phone, and PSTN network usage is determined to be less expensive or higher quality than Internet network usage, it is the preferred choice to select a gateway that allows the client to access the PSTN network from a point "closest" to the point of internet access. This is often referred to as Head- End Hop-Off (HEHO), where the client hops off the internet at the "head end" or "near end" of the internet.
[1931] If the client 1080 needs to place a telephone call to a regular PSTN phone, and the PSTN network is determined to be more expensive than Internet network usage, it is the preferred choice to select a gateway that allows the client to access the PSTN from the Internet at a point closest to the destination telephone. This is often referred to as Tail-End Hop-Off (TEHO), where the client hops off the internet at the "tail end" or "far end" of the internet.
[1932] a) Head-End Hop-Off Methods
[1933] (1) Client Ping Method
[1934] This method selects the best choice for a head-end hop-off internet telephony gateway by obtaining a list of candidate internet telephony gateway addresses, and pinging each to determine the best choice in terms of latency and number of router hops. The process is as follows:
[1935] Client Computer 1080 queries a directory service 1082 to obtain a list of candidate internet telephony gateways.
[1936] The directory service 1082 looks in a database of gateways and selects a list of gateways to offer the client as candidates. Criteria for selecting gateways as candidates can include
[1937] last gateway selected.
[1938] matching 1, 2, or 3 octets in the 1Pv4 address.
[1939] last client access point, if known.
[1940] selection of at least one gateway from all major gateway sites, if practical.
[1941] The directory service 1082 returns a list of "n" candidate IP addresses to the client 1080 in a TCP/IP message.
[1942] The client 1080 simultaneously uses the IP ping to send an echo-type message to each candidate Internet Telephony Gateway, 1084, 1081, 1086. The "-r" option will be used with the ping command to obtain a trace route.
[1943] Based upon the ping results for each Internet Telephony Gateway, the client 1080 will rank order the ping results as follows:
[1944] If any Internet Telephony Gateways are accessible to the client 1080 without traveling through any intervening router as revealed by the ping trace route, they are ranked first.
[1945] The remaining Internet Telephony Gateways are ranked in order of lowest latency of round-trip ping results.
[1946] Using the Client Ping Method with the Sample Network Topology above, the Client Computer 1080 queries the Directory Service 1082 for a list of Internet Telephony Gateways to ping. The Directory Service 1082 returns the list:
[1947] 126.96.36.199
[1948] 184.108.40.206
[1949] 188.8.131.52
[1950] The Client Computer 1080 issues the following three commands simultaneously:
[1951] ping 18.104.22.168 -r 1
[1952] ping 220.127.116.11 -r 1
[1953] ping 184.108.40.206 -r 1
[1954] The results of the ping commands are as follows:
[1955] Pinging 220.127.116.11 with 32 bytes of data:
[1956] Reply from 22.214.171.124: bytes=32 time=3 ms TTL=30 Route: 126.96.36.199
[1957] Reply from 220.127.116.11: bytes=32 time=2 ms TTL=30 Route: 184.108.40.206
[1958] Reply from 184.108.40.206: bytes=32 time=2 ms TTL=31 Route: 22.214.171.124
[1959] Reply from 18.104.22.168: bytes=32 time=2 ms TTL=30 Route: 22.214.171.124
[1960] Pinging 188.8.131.52 with 32 bytes of data:
[1961] Reply from 188.8.131.52: bytes=32 time=14 ms TTL=30 Route: 22.214.171.124
[1962] Reply from 188.8.131.52: bytes=32 time=2 ms TTL=30 Route: 220.127.116.11
[1963] Reply from 22.214.171.124: bytes=32 time=3 ms TTL=31 Route: 126.96.36.199
[1964] Reply from 18.104.22.168: bytes=32 time=4 ms TTL=30 Route: 126.96.36.199
[1965] Pinging 126.96.36.199 with 32 bytes of data:
[1966] Reply from 18.104.22.168: bytes=32 time=1 ms TTL=126 Route: 18.104.22.168
[1967] Reply from 18.104.22.168: bytes=32 time=1 ms TTL=126 Route: 18.104.22.168
[1968] Reply from 184.108.40.206: bytes=32 time=1 ms TTL=126 Route: 22.214.171.124
[1969] Reply from 126.96.36.199: bytes=32 time=1 ms TTL=126 Route: 18.104.22.168
[1970] Since the route taken to 22.214.171.124 went through no routers (route and ping addresses are the same), this address is ranked first. The remaining Internet Telephony Gateway Addresses are ranked by order of averaged latency. The resulting preferential ranking of Internet Telephony Gateway addresses is
[1971] 188.8.131.52
[1972] 126.96.36.199
[1973] 18.104.22.168
[1974] The first choice gateway is the gateway most likely to give high quality of service, since it is located on the same local area network. This gateway will be the first the client will attempt to use.
[1975] (2) Access Device Location Method
[1976] The method for identifying the most appropriate choice for an Internet Telephony Gateway utilizes a combination of the Client Ping Method detailed above, and the knowledge of the location from which the Client Computer 1080 accessed the Internet. This method may work well for clients accessing the Internet via a dial-up access device.
[1977] A client computer 1080 dials the Internet Access Device. The Access Device answers the call and plays modem tone. Then, the client computer and the access device establishes a PPP session. The user on the Client Computer is authenticated (username/password prompt, validated by an authentication server). Once the user passes authentication, the Access Device can automatically update the User Profile in the Directory Service for the user who was authenticated, depositing the following information
[1978] "User Name" "Account Code" "online timestamp"
[1979] "Access Device Site Code"
[1980] Later, when the Client Computer requires access through an Internet Telephony Gateway, it queries the Directory Service 1082 to determine the best choice of Internet Telephony Gateway. If an Access Device Site Code is found in the User's Profile on the Directory Service, the Directory Service 1082 selects the Internet Telephony Gateway 1084, 1081 and 1086 at the same site code, and returns the IP address to the Client Computer 1080. If an Internet Telephony Gateway 1084, 1081 and 1086 is unavailable at the same site as the Access Device Site Code, then the next best choice is selected according to a network topology map kept on the directory server.
[1981] If no Access Device Site Code is found on the directory server 1082, then the client 1080 has accessed the network through a device which cannot update the directory server 1082. If this is the case, the Client Ping Method described above is used to locate the best alternative internet telephony gateway 1084.
[1982] (3) User Profile Method
[1983] Another method for selection of an Internet Telephony Gateway 1084, 1081 and 1086 is to embed the information needed to select a gateway in the user profile as stored on a directory server. To use this method, the user must execute an internet telephony software package on the client computer. The first time the package is executed, registration information is gathered from the user, including name, email address, IP Address (for fixed location computers), site code, account code, usual internet access point, and other relevant information. Once this information is entered by the user, the software package deposits the information on a directory server, within the user's profile.
[1984] Whenever the Internet Telephony software package is started by the user, the IP address of the user is automatically updated at the directory service. This is known as automated presence notification. Later, when the user needs an Internet Telephony Gateway service, the user queries the directory service for an Internet Telephony Gateway to use. The directory service knows the IP address of the user and the user's usual site and access point into the network. The directory service can use this information, plus the network map of all Internet Telephony Gateways 1084, 1081 and 1086, to select the best Internet Telephony Gateway for the client computer to use.
[1985] (4) Gateway Ping Method
[1986] The last method selects the best choice for a head-end hop-off internet telephony gateway by obtaining a list of candidate internet telephony gateway addresses, and pinging each to determine the best choice in terms of latency and number of router hops. The process is as follows:
[1987] Client Computer queries a directory service to obtain a best-choice internet telephony gateway.
[1988] The directory service looks in a database of gateways and selects a lis—of candidate gateways. Criteria for selecting gateways as candidates can include
[1989] last gateway selected.
[1990] matching 1, 2, or 3 octets in the IPv4 address.
[1991] last client access point, if known.
[1992] selection of at least one gateway from all major gateway sites, if practical.
[1993] The directory sends a message to each candidate gateway, instructing each candidate gateway to ping the client computer's IP Address.
[1994] Each candidate gateway simultaneously uses the IP ping to send an echo-type message to the client computer. The "-r" option will be used with the ping command to obtain a trace route. The ping results are returned from each candidate gateway to the directory service.
[1995] Based upon the ping results for each Internet Telephony Gateway, the directory service will rank order the ping results as follows:
[1996] If any Internet Telephony Gateways are accessible to the client without traveling through any intervening router as revealed by the ping trace route, they are ranked first.
[1997] The remaining Internet Telephony Gateways are ranked in order of lowest averaged latency of round-trip ping results.
[1998] The Client Ping Method and Gateway Ping Method may use the traceroute program as an alternative to the ping program in determining best choice for a head-end hop-off gateway.
[1999] b) Tail-End Hop-Off Methods
[2000] Tail-End Hop-Off entails selecting a gateway as an egress point from the internet where the egress point is closest to the terminating PSTN location as possible. This is usually desired to avoid higher PSTN calling rates. The internet can be used to bring the packetized voice to the local calling area of the destination telephone number, where lower local rates can be paid to carry the call on the PSTN.
[2001] (1) Gateway Registration
[2002] One method for Tail-End Hop-Off service is to have Internet Telephony Gateways 1084, 1081 and 1086 register with a directory service. Each Internet Telephony Gateway will have a profile in the directory service which lists the calling areas it serves. These can be listed in terms of Country Code, Area Code, Exchange, City Code, Line Code, Wireless Cell, LATA, or any other method which can be used to subset a numbering plan. The gateway, upon startup, sends a TCP/IP registration message to the Directory Service 1082 to list the areas it serves.
[2003] When a Client Computer wishes to use a TEHO service, it queries the directory service for an Internet Telephony Gateway 1084 serving the desired destination phone number. The directory service 1082 looks for a qualifying Internet Telephony Gateway, and if it finds one, returns the IP address of the gateway to use. Load-balancing algorithms can be used to balance traffic across multiple Internet Telephony Gateways 1084, 1081 and 1086 serving the same destination phone number.
[2004] If no Internet Telephony Gateways 1084, 1081 and 1086 specifically serve the calling area of the given destination telephone number, the directory service 1082 returns an error TCP/IP message to the Client Computer 1080. The Client 1080 then has the option of querying the Directory Service for any Internet Telephony Gateway, not just gateways serving a particular destination telephone number.
[2005] As a refinement of this Gateway Registration scheme, Gateways can register calling rates provided for all calling areas. For example, if no gateway is available in Seattle, it may be less expensive to call Seattle from the gateway in Los Angeles, than to call Seattle from the gateway in Portland. The rates registered in the directory service can enable the directory service the lowest cost gateway to use for any particular call.
[2006] 7. Vnet Call Processing
[2007]FIG. 11 is a callflow diagram in accordance with a preferred embodiment. Processing commences at 1101 where the location of the directory service to receive this "on-line" message will be determined by the data distribution implementation for this customer. In some cases this may be a private database for a company or organization subscribing to a VNET service, in other cases it might be a national or worldwide database for all customers of a service provider (MCI). When the directory service receives this message from PC12 1051, it will update a profile entry associated with the unique ID to indicate that the user is "on-line" and is located at the specified IP address. Then, at 1102, after successful update of the profile associated with the ID, the directory service sends a response (ACK) back to the specified IP address indicating that the message was received and processed. When the computer (PC12) receives this response message it may choose to notify the user via a visual or audible indicator.
[2008] At 1103, a user of PC11 1052 connects a computer to an IP network, turns on the computer and starts telephony system software. The registration process for this computer follows the same procedures as those for PC12 1051. In this scenario it is assumed that the directory service receiving this message is either physically or logically the same directory service that received the message from PC12 1051.
[2009] At 1104, when the directory service 1031 receives a message from PC11 1052, it initiates a similar procedure as it followed for a message for PC12 1051. However, in this case it will update the profile associated with the identifier it received from PC11 1052, and it will use the IP address it received from PC11 1052. Because of the updated profile information, when the acknowledgment message is sent out from the directory service, it is sent to the IP address associated with PC11 1052. At this point both computers (PC12 1051 and PC11 1052) are "on-line" and available to receive calls.
[2010] At 1105, PC12 1051 uses its telephony system software to connect to computer PC11 1052. To establish this connection, the user of PC12 1051 dials the VNET number (or other unique ID such as name, employee ID, etc). Depending upon the implementation of the customer's network, and software package, a unique network identifier may have to be placed in this dial string. As an example, in a telephony implementation of a VNET, a subscriber may be required to enter the number 8 prior to dialing the VNET number to signal a PBX that they are using the VNET network to route the call. Once the telephony software package has identified this call as a VNET type call, it will send a translation request to the directory service. At a minimum, this translation request will contain the following information:
[2011] The IP address of the computer (PC12 1051) sending this request, and
[2012] The VNET number (or other ID) of tile computer to be dialed.
[2013] At 1106, when the directory service receives this message, it uses the VNET number (or other ID) to determine if the user associated with the VNET number (or other ID) is "on-line" and to identify the IP address of the location where the computer may be contacted. Any additional information that is available about the computer being contacted (PC11 1052), such as compression algorithms or special hardware or software capabilities, may also be retrieved by the directory service 1031. The directory service 1031 then returns a message to PC12 1051 with status information for PC11 1052, such as whether the computer is "on-line," its IP address if it is available and any other available information about capabilities of PC11 1052. When PC12 1051 receives the response, it determines whether PC11 1052 may be contacted. This determination will be based upon the "on-line" status of PC11 1052, and the additional information about capabilities of PC11 1052. If PC12 1051 receives status information indicating that PC11 1052 may not be contacted, the call flow stops here, otherwise it continues.
[2014] The following steps 1107 through 1111 are "normal" IP telephony call setup and tear-down steps. At 1107, PC12 1051 transmits a "ring" message to PC11 1052. This message is directed to the IP address received from the directory service 1031 in step 1106. This message can contain information identifying the user of PC12 1051, or it may contain information specifying the parameters associated with the requested connection.
[2015] At 1108, the message from step 1107 is received by PC11 1052 and the receipt of this message is acknowledged by sending a message back to PC12 1051 indicating that the user of PC11 1052 is being notified of an incoming call. This notification may be visible or audible depending upon the software package and its configurations on PC11 1052.
[2016] At 1109, if the user of PC11 1052 accepts the call, a message is sent back to PC12 1051 confirming "answer" for the call. If the user of PC11 1052 does not answer the call or chooses to reject the call, a message will be sent back to PC12 1051 indicative of the error condition. If the call was not answered, the call flow stops here, otherwise it continues.
[2017] At 1110, the users of PC12 1051 and PC11 1052 can communicate using their telephony software. Communication progresses until at 1111 a user of either PC may break the connection by sending a disconnect message to the other call participant. The format and contents of this message is dependent upon the telephony software packages being used by PC12 1051 and PC11 1052. In this scenario, PC 1 1052 sends a disconnect message to PC12 1051, and the telephony software systems on both computers discontinue transmission of voice.
[2018]FIG. 12 illustrates a VNET Personal Computer (PC) to out-of-network PC Information call flow in accordance with a preferred embodiment. In this flow, the Internet telephony gateway is an out-of-network element. This means that the Internet Telephony Gateway cannot use SS7 signaling to communicate with the switch, it must simply outpulse the VNET number to be dialed. An alternate embodiment facilitates directory services to do a translation of the VNET number directly to a Switch/Trunk and outpulse the appropriate digits. Such processing simplifies translation in the switching network but would require a more sophisticated signaling interface between the internet gateway and the switch. This type on "in-network" internet gateway scenario will be covered in another call flow.
[2019] This scenario assumes that there is no integration between the internet and a customer premises Public Branch Exchange (PBX). If there were integration, it might be possible for the PC to go through the Internet (or intranet) to connect to an ITG on the customers PBX, avoiding the useof the PSTN. FIG. 12 is a callflow diagram in accordance with a preferred embodiment. Processing commences at 1201 where the location of the directory service to receive this "on-line" message will be determined by the data distribution implementation for this customer. In some cases this may be a private database for a company or organization subscribing to a VNET service, in other cases it might be a national or worldwide database for all customers of a service provider (MCI).
[2020] When the directory service receives this message from PC12 1051, it will update a profile entry associated with the unique ID to indicate that the user is "on-line" and is located at the specified IP address. Then, at 1202, after successful update of the profile associated with the ID, the directory service sends a response (ACK) back to the specified IP address indicating that the message was received and processed. When the computer (PC12) receives this response message it may choose to notify the user via a visual or audible indicator.
[2021] At 1203, a VNET translation request is then sent to the directory services to determine the translation for the dial path to the out of network internet gateway phone. A response including the IP address and the DNIS is returned at 1204. The response completely resolves the phone addressing information for routing the call. Then, at 1205, an IP telephony dial utilizing the DNIS information occurs. DNIS refers to Dialed Number Information Services which is definitive information about a call for use in routing the call. At 1206 an ACK is returned from the IP telephony, and at 1207 an IP telephony answer occurs and a call path is established at 1208.
[2022]1209 a shows the VNET PC going offhook and sending a dial tone 1209 b, and outpulsing digits at 1210. Then, at 1211, the routing translation of the DNIS information is used by the routing database to determine how to route the call to the destination telephone. A translation response is received at 1212 and a switch to switch outpulse occurs at 1213. Then, at 1215, a ring is transmitted to the destination phone, and a ringback to the PC occurs. The call is transmitted out of the network via the internet gateway connection and answered at 1216. Conversation ensues at 1217, until one of the parties hangs up at 1218.
[2023]FIG. 13 illustrates a VNET Personal Computer (PC) to out-of-network Phone Information call flow in accordance with a preferred embodiment. In this call flow, the use of the PSTN is avoided by routing the call from the PC to the Internet/Intranet to an internet gateway directly connected to a PBX.
[2024]FIG. 14 illustrates a VNET Personal Computer (PC) to in-network Phone Information call flow in accordance with a preferred embodiment. In this call flow, the internet telephony gateway is an in-network element. This requires that the internet gateway can behave as if it were a switch and utilize SS7 signaling to hand the call off to a switch. This allows the directory service to return the switch/trunk and outpulse digits on the first VNET lookup. This step avoids an additional lookup by the switch. In this case the directory service must have access to VNET routing information.
[2025] a) PC to PC
[2026]FIG. 15 illustrates a personal computer to personal computer internet telephony call in accordance with a preferred embodiment. In step 1501, a net phone user connects through the internet via an IP connection to the step 1502 MCI directory service where a look up is performed to determine how to route the call. In step 1503, the call is terminated in the Intelligent System Platform (ISP) to determine where to send the call. IP Router is the gateway that goes into the MCI ISP to determine via the Intelligent Services Network (ISN) feature engine how to get the call through the network. In step 1504, the call is connected through the Internet to the Net Phone user. In alternative scenario step 1504 the person at the phone is unavailable, so the calling party desired to speak with an MCI operator and the IP Router goes through the Net-Switch (interface to the voice world.) In step 1505, the netswitch queries the call processing engine to do DSP Engine functions. In step 1506, the call is routed through the WAN Hub to a MCI switch to an MCI Operator or voicemail in step 1507. This preferred embodiment utilizes the existing infrastructure to assist the call.
[2027] b) PCTO PHONE
[2028]FIG. 16, illustrates a phone call that is routed from a PC through the Internet to a phone. In step 1602, the MCI Directory is queried to obtain ISN information for routing the call. Then the call is redirected in step 1603 to the ISP Gateway and routed utilizing the IP router to the call processing engine in steps 1604 and 1605. Then, in step 1606, the call is routed to the WAN and finally to the RBOC where Mainframe billing is recorded for the call.
[2029] c) Phone to PC
[2030]FIG. 17 illustrates a phone to PC call in accordance with a preferred embodiment. In step 1701, a phone is routed into a special net switch where in step 1702, a call processing engine determines the DTMF tones utilizing a series of digital signal processors. Then, at step 1703, the system looks up directory information and connects the call. If the caller is not there, or busy, then at step 1704, the call is routed via an IP router over the switch utilizing the call processing engine in step 1705.
[2031] d) Phone to Phone
[2032]FIG. 18 illustrates a phone to phone call over the internet in accordance with a preferred embodiment. A call comes into the switch at step 1801, and is processed by the call logic program running in the call processing engine in step 1802. In step 1803, a lookup is performed in the directory information database to determine routing of the call as described above. The routing includes storing a billing record in the mainframe billing application 1808. All of the ISN features are available to the call even thought the call is routed through the internet. An IP router is used at each end of the internet to facilitate routing of the call through the internet 1804 and into the network switch. From the network switch the call is routed to a call processing engine through a WAN hub 1806 through the RBOC 1807 to the target telephone. Various DSP Engines 1803 are utilized to perform digital transcoding, DTMF detection, voice recognition, call progress, VRU functions and Modem functions.
[2034] A preferred embodiment utilizes a network management system for a telecommunication network for analyzing, correlating, and presenting network events. Modern telecommunications networks utilize data signaling networks, which are distinct from the call-bearing networks, to carry the signaling data that are required for call setup, processing, and clearing. These signaling networks use an industry-standard architecture and protocol, collectively referred to as Common Channel Signaling System #7, or Signaling System #7 (SS7) for short. SS7 is a significant advancement over the previous signaling method, in which call signaling data were transmitted over the same circuits as the call. SS7 provides a distinct and dedicated network of circuits for transmitting call signaling data. Utilizing SS7 decreases the call setup time (perceived by the caller as post-dial delay) and increases capacity on the call-bearing network. A detailed description of SS7 signaling is provided in Signaling System #7, Travis Russell, Mcgraw Hill (1995).
[2035] The standards for SS7 networks are established by ANSI for domestic (U.S.) networks, by ITU for international connections, and are referred to as ANSI SS7 and ITU C7, respectively. A typical SS7 network is illustrated in FIG. 1B. A call-bearing telecommunications network makes use of matrix switches 102 a/102 b for switching customer traffic. These switches 102 a/102 b are conventional, such as a DMS-250 manufactured by Northern Telecom or a DEX-600 manufactured by Digital Switch Corporation. These switches 102 a/102 b are interconnected with voice-grade and data-grade call-bearing trunks. This interconnectivity, which is not illustrated in FIG. 1B, may take on a large variety of configurations.
[2036] Switches in telecommunications networks perform multiple functions. In addition to switching circuits for voice calls, switches must relay signaling messages to other switches as part of call control. These signaling messages are delivered through a network of computers, each of which is called a Signaling Point (SP) 102 a/102 b. There are three kinds of SPs in an SS7 network:
[2037] Service Switching Point (SSP)
[2038] Signal Transfer Point (STP)
[2039] Service Control Point (SCP)
[2040] The SSPs are the switch interface to the SS7 signaling network.
[2041] Signal Transfer Points (STPs) 104 a . . . 104 f (collectively referred to as 104) are packet-switching communications devices used to switch and route SS7 signals. They are deployed in mated pairs, known as clusters, for redundancy and restoration. For example, in FIG. 1B, STP 104 a is mated with STP 104 b in Regional Cluster 1, STP 104 c is mated with STP 104 d in Regional Cluster 2, and STP 104 e is mated with STP 104 f in Regional Cluster 3. A typical SS7 network contains a plurality of STP clusters 104; three are shown in FIG. 1 for illustrative purposes. Each STP cluster 104 serves a particular geographic region of SSPs 102. A plurality of SSPs 102 have primary SS7 links to each of two STPs 104 in a cluster. This serves as a primary homing arrangement. Only two SSPs 102 are shown homing to Regional Cluster 2 in FIG. 1B for illustrative purposes; in reality, several SSPs 102 will home on a particular STP cluster 104. SSPs 102 will also generally have a secondary SS7 link to one or both STPs 104 in another cluster. This serves as a secondary homing arrangement.
[2042] The SS7 links that connect the various elements are identified as follows:
[2043] A links connect an SSP to each of its primary STPs (primary homing).
[2044] B links connect an STP in one cluster to an STP in another cluster.
[2045] C links connect one STP to the other STP in the same cluster.
[2046] D links connect STPs between different carrier networks (not illustrated).
[2047] E links connect an SSP to an STP that is not in its cluster (secondary homing).
[2048] F links connect two SSPs to each other.
[2049] To interface two different carriers' networks, such as a Local Exchange Carrier (LEC) network with an Interchange Carrier (IXC) network, STP clusters 104 from each carriers' network may be connected by D links or A links. SS7 provides standardized protocol for such an interface so that the signaling for a call that is being passed between an LEC and an IXC may also be transmitted.
[2050] When a switch receives and routes a customer call, the signaling for that call is received (or generated) by the attached SSP 102. While intermachine trunks that connect the switches carry the customer's call, the signaling for that call is sent to an STP 104. The STP 104 routes the signal to either the an SSP 102 for the call-terminating switch, or to another STP 104 that will then route the signal to the SSP 102 for the call-terminating switch. Another element of an SS7 network are Protocol Monitoring Units (PMU) 106, shown in FIG. 2. PMUs 106 are deployed at switch sites and provide an independent monitoring tool for SS7 networks. These devices, such as those manufactured by INET Inc. of Richardson, TX., monitor the A, E, and F links of the SS7 network, as shown in FIG. 2. They generate fault and performance information for SS7 links.
[2051] As with any telecommunications network, an SS7 network is vulnerable to fiber cuts, other transmission outages, and device failures. Since an SS7 network carries all signaling required to deliver customer traffic, it is vital that any problems are detected and corrected quickly. Therefore, there is an essential need for a system that can monitor SS7 networks, analyze fault and performance information, and manage corrective actions.
[2052] Prior art SS7 network management systems, while performing these basic functions, have several shortcomings. Many require manual configuration of network topology, which is vulnerable to human error and delay topology updates. Configuration of these systems usually requires that the system be down for a period of time. Many systems available in the industry are intended for a particular vendor's PMU 106, and actually obtain topology data from their PMUs 106, thereby neglecting network elements not connected to a PMU 106 and other vendors' equipment.
[2053] Because prior art systems only operate with data received from proprietary PMUs 106, they do not provide correlation between PMU events and events generated from other types of SS7 network elements. They also provide inflexible and proprietary analysis rules for event correlation.
[2054] A system and method for providing enhanced SS7 network management functions are provided by a distributed client/server platform that can receive and process events that are generated by various SS7 network elements. Each network event is parsed and standardized to allow for the processing of events generated by any type of element. Events can also be received by network topology databases, transmission network management systems, network maintenance schedules, and system users. Referring to FIG. 3, the systems architecture of the preferred embodiment of the present invention, referred to as an SS7 Network Management System (SNMS), is illustrated. SNMS consists of four logical servers 302/304/306/308 and a plurality of client workstations 312 a/312 b/312 c connected via a Network Management Wide Area Network (WAN) 310. The four logical SNMS servers 302/304/306/308 may all reside on a single or a plurality of physical units. In the preferred embodiment, each logical server resides on a distinct physical unit, for the purpose of enhancing performance. These physical units may be of any conventional type, such as IBM RS6000 units running with AIX operating system.
[2055] The client workstations 312 may be any conventional PC running with Microsoft Windows or IBM OS/2 operating systems, a dumb terminal, or a VAX VMS workstation. In actuality, client workstations may be any PC or terminal that has an Internet Protocol (IP) address, is running with X- Windows software, and is connected to the WAN 310. No SNMS-specific software runs on the client workstations 312.
[2056] SNMS receives events from various SS7 network elements and other network management systems (NMS) 338. It also receives network topology, configuration, and maintenance data from various external systems, as will be described. The various network elements that generate events include Network Controllers 314, International and Domestic SPs 316/102, STPs 104, and PMUs 106. Network Controllers 314 are devices that switch circuits based on external commands. They utilize SS7 signaling in the same manner as an SSP 102, but are not linked to any STPs 104. International SPs 316 support switches that serve as a gateway between a domestic and international telecommunications network. The STPs 104 may be domestic or international.
[2057] The PMUs 106 scan all the SS7 packets that pass across the SS7 circuits, analyze for fault conditions, and generate network events that are then passed onto SNMS. The PMUs 106 also generate periodic statistics on the performance of the SS7 circuits that are monitored.
[2058] All SPs 102/316, STPs 104, PMU 106, and SS7 Network Controllers 314 transmit network events to SNMS via communications networks. This eliminates the need for SNMS to maintain a session with each of the devices. In one typical embodiment, as illustrated in FIG. 3, an Asynchronous Data Communications Network 320 is used to transport events from Network Controllers 314 and International SPs 316. An IBM mainframe Front End Processor (FEP) 324, such as IBM's 3708, is used to convert the asynchronous protocol to SNA so it can be received by a IBM mainframe-based Switched Host Interface Facilities Transport (SWIFT) system 326. SWIFT 326 is a communications interface and data distribution application that maintains a logical communications session with each of the network elements.
[2059] In this same embodiment, an X.25 Operational Systems Support (OSS) Network 328 is used to transport events from STPs 104, SPs 102, and PMUs 106. These events are received by a Local Support Element (LSE) system 330. The LSE 330, which may be a VAX/VMS system, is essentially a Packet Assembler/Disassembler (PAD) and protocol converter used to convert event data from the X.25 OSS Network 328 to the SNMS servers 302/304. It also serves the same function as SWIFT 326 in maintaining communication sessions with each network element, thus eliminating the need for SNMS to do so. The need for both SWIFT 326 and LSE 330 illustrates one embodiment of a typical telecommunications network in which different types of elements are in place requiring different transport mechanisms. SNMS supports all these types of elements.
[2060] All network events are input to the SNMS Alarming Server 302 for analysis and correlation. Some events are also input to the SNMS Reporting Server 304 to be stored for historical purposes. A Control system 332, which may be a VAX/VMS system, is used to collect topology and configuration data from each of the network elements via the X.25 OSS Network 328. Some elements, such as STPs 104 and SPs 102, may send this data directly over the X.25 OSS Network 328. Elements such as the International SSP 316, which only communicates in asynchronous mode, use a Packet Assembler/Disassembler (PAD) 318 to connect to the X.25 OSS Network 328. The Control system 332 then feeds this topology and configuration data to the SNMS Topology Server 306.
[2061] Network topology information is used by SNMS to perform alarm correlation and to provide graphical displays. Most topology information is received from Network Topology Databases 334, which are created and maintained by order entry systems and network engineering systems in the preferred embodiment. Topology data is input to the SNMS Topology Server 306 from both the Network Topology Databases 334 and the Control System 332. An ability to enter manual overrides through use of a PC 336s also provided to the SNMS Topology Server 306.
[2062] The SNMS Alarming Server 302 also receives events, in particular DS-3 transmission alarms, from other network management systems (NMS) 338. Using topology data, SNMS will correlate these events with events received from SS7 network elements. The SNMS Alarming Server 302 also receives network maintenance schedule information from a Network Maintenance Schedule system 340. SNMS uses this information to account for planned network outages due to maintenance, thus eliminating the need to respond to maintenance-generated alarms. SNMS also uses this information to proactively warn maintenance personnel of a network outage that may impact a scheduled maintenance activity.
[2063] The SNMS Alarming Server 302 has an interface with a Trouble Management System 342. This allows SNMS users at the client workstations 312 to submit trouble tickets for SNMS-generated alarms. This interface, as opposed to using an SNMS-internal trouble management system, can be configured to utilize many different types of trouble management systems. In the preferred embodiment, the SNMS Graphics Server 308 supports all client workstations 312 at a single site, and are therefore a plurality of servers. The geographical distribution of SNMS Graphics Servers 308 eliminates the need to transmit volumes of data that support graphical presentation to each workstation site from a central location. Only data from the Alarming Server 302, Reporting Server 304, and Topology Server 306 are transmitted to workstation sites, thereby saving network transmission bandwidth and improving SNMS performance. In alternative embodiments, the Graphics Servers 308 may be centrally located.
[2064] Referring now to FIG. 4, a high-level process flowchart illustrates the logical system components of SNMS. At the heart of the process is Process Events 402. This component serves as a traffic cop for SNMS processes. Process Events 402, which runs primarily on the SNMS Alarming Server 302, is responsible for receiving events from other SNMS components, processing these events, storing events, and feeding processed event data to the Reporting and Display components. The Process Events process 402 is shown in greater detail in FIG. 5.
[2065] The Receive Network Events component 404, which runs primarily on the Alarming Server 302, receives network events from the various SS7 network elements (STPs 104, SPs 102, PMUs 106, etc.) via systems such as SWIFT 326 and LSE 330. This component parses the events and sends them to Process Events 402 for analysis. The Receive Network Events process 404 is shown in greater detail in FIG. 6.
[2066] The Process Topology component 406, which runs primarily on the Topology Server 306, receives network topology and configuration data from the Network Topology Databases 334, from the SS7 network elements via the Control System 332, and from Manual Overrides 336. This data is used to correlate network events and to perform impact assessments on such events. It is also used to provide graphical presentation of events. Process Topology 406 parses these topology and configuration data, stores them, and sends them to Process Events 402 for analysis. The Process Topology process 406 is shown in greater detail in FIG. 7.
[2067] The Define Algorithms component 408, which runs primarily on the Alarming Server 302, defines the specific parsing and analysis rules to be used by SNMS. These rules are then loaded into Process Events 402 for use in parsing and analysis. The algorithms are kept in a software module, and are defined by programmed code. A programmer simply programs the pre-defined algorithm into this software module, which is then used by Process Events 402. These algorithms are procedural in nature and are based on network topology. They consist of both simple rules that are written in a proprietary language and can be changed dynamically by an SNMS user, and of more complex rules which are programmed within SNMS software code.
[2068] The Receive NMS Data component 410, which runs primarily on the Alarming Server 302, receives events from other network management systems (NMS) 338. Such events include DS-3 transmission alarms. It also receives network maintenance events from a Network Maintenance Schedule system 340. It then parses these events and sends them to Process Events 402 for analysis. The Display Alarms component 412, which runs primarily on the Graphics Server 308 and the Alarming Server 302, includes the Graphical User Interface (GUI) and associated software which supports topology and alarm presentation, using data supplied by Process Events 402. It also supports user interactions, such as alarm clears, acknowledgments, and trouble ticket submissions. It inputs these interactions to Process Events 402 for storing and required data updates. The Display Alarms process 412 is shown in greater detail in Fig,-re 8.
[2069] The Report On Data component 414, which runs primarily on the Reporting Server 304, supports the topology and alarm reporting functions, using data supplied by Process Events 402. The Report On Data process 414 is shown in greater detail in FIG. 9.
[2070] Referring now to FIG. 5, the detailed process of the Process Events component 402 is illustrated. This is the main process of SNMS. It receives generalized events from other SNMS components, parses each event to extract relevant data, and identifies the type of event. If it is an SS7-related event, Process Events 402 applies a selected algorithm, such as create alarm or correlate to existing alarm.
[2071] The first three steps 502-506 are an initialization process that is run at the start of each SNMS session. They establish a state from which the system may work. Steps 510-542 are then run as a continuous loop.
[2072] In step 502, current topology data is read from a topology data store on the Topology Server 306. This topology data store is created in the Process Topology process 406 and input to Process Events 402, as reflected in FIG. 4. The topology data that is read has been parsed in Process Topology 406, so it is read in step 502 by Process Events 402 as a standardized event ready for processing.
[2073] In step 504, the algorithms which are created in the Define Algorithms component 408 are read in. These algorithms determine what actions SNMS will take on each alarm. SNMS has a map of which algorithms to invoke for which type of alarm.
[2074] In step 506, alarms records from the Fault Management (FM) reporting database, which is created in the Report on Data process 414, are read in. All previous alarms are discarded. Any alarm that is active against a node or circuit that does not exist in the topology (read in step 502) is discarded. Also, any alarm that does not map to any existing algorithm (read in step 504) is discarded. The alarms are read from the FM reporting database only within initialization. To enhance performance of the system, future alarm records are retrieved from a database internal to the Process Events 402 component. Step 506 concludes the initialization process; once current topology, algorithms, and alarms are read, SNMS may begin the continuous process of reading, analyzing, processing, and storing events.
[2075] This process begins with step 510, in which the next event in queue is received and identified. The queue is a First In/First Out (FIFO) queue that feeds the Process Events component 402 with network events, topology events, and NMS events. To reiterate, the topology data that are read in step 502 and the alarm data that are read in step 504 are initialization data read in at startup to create a system state. In step 510, ongoing events are read in continuously from process components 404, 406, and 410. These events have already been parsed, and are received as standardized SNMS events. SNMS then identifies the type of event that is being received. If the event is found to be older than a certain threshold, for example one hour, the event is discarded.
[2076] In steps 512, 520, 524, and 534 SNMS determines what to do with the event based on the event type identification made in step 510.
[2077] In step 512, if the event is determined to be topology data, SNMS updates the GUI displays to reflect the new topology in step 514. Then in step 516, SNMS performs a reconciliation with active alarms to discard any alarm not mapping to the new topology. In step 518, the new topology data is recorded in a topology data store, which is kept in the SNMS Topology Server 306.
[2078] In step 520, if the event is determined to be NMS data, such as DS-3 alarms 338, it is stored in the FM reporting database on the SNMS Reporting Server 304 for future reference by SNMS rules.
[2079] In step 524, if the event is determined to be a defined SS7 network event, then in step 526 one or more algorithms will be invoked for the event. Such algorithms may make use of data retrieved from Network Management
[2080] Systems 338, Network Maintenance Schedules 340, and Network Topology 334.
[2081] For example, when each circuit level algorithm generates an alarm, it performs a check against the Network Maintenance Schedule 340 and NMS 338 records. Each alarm record is tagged if the specified circuit is within a maintenance window (Network Maintenance Schedule 340) or is transported on-a DS-3 that has a transmission alarm (NMS 338). While SS7 circuits run at a DS-0 level, the Network Topology Databases 334 provide a DS-3 to DS-0 conversion table. Any DS-0 circuit within the DS-3 is tagged as potentially contained within the transmission fault. Clear records from NMS 338 will cause active SNMS circuit level alarms to be evaluated so that relevant NMS 338 associations can be removed. SNMS clear events will clear the actual SNMS alarm. GUI filters allow users to mask out alarms that fit into a maintenance window or contained within a transmission fault since these alarms do not require SNMS operator actions.
[2082] In step 523, active alarms are reconciled with new alarm generations and clears resulting from step 526. In step 530, the GUI displays are updated. In step 532, the new alarm data is stored in the FM reporting database.
[2083] In step 534, the event may be determined to be a timer. SNMS algorithms sometimes need to delay further processing of specific conditions for a defined period of time, such as for persistence and rate algorithms. A delay timer is set for this condition and processing of new SNMS events continues. When the time elapses, SNMS treats the time as an event and performs the appropriate algorithm.
[2084] For example, an SS7 link may shut down momentarily with the possibility of functioning again within a few seconds, or it may be down for a much greater period of time due to a serious outage that requires action. SNMS, when it receives this event, will assign a timer of perhaps one minute to the event. If the event clears within one minute, SNMS takes no action on it. However, if after the one minute timer has elapsed the event is unchanged (SS7 link is still down), SNMS will proceed to take action.
[2085] In step 536, the appropriate algorithm is invoked to take such action. In step 538, active alarms are reconciled with those that were generated or cleared in step 536. In step 540, the GUI displays are updated. In step 542, the new alarm data is stored in the FM reporting database. As stated previously, SNMS operates in a continuous manner with respect to receiving and processing events. After the data stores in steps 518, 522, 532, and 542. the process returns to step 510.
[2086] Referring now to FIG. 6, the detailed process of the Receive Network Events component 404 is illustrated. This component collects events from the SS7 network elements via data transport mechanisms, such as the Async Data Network 320, SWIFT 326, X.25 OSS network 328, and the LSE 330. These events are received by the SNMS Alarming Server 302 in a First In/First Out (FIFO) queue. In steps 602 and 604, events from the SS7 network elements are collected by mainframe applications external to SNMS, such as SWIFT 326 and LSE 330, and the protocol of the event data is converted from the network element-specific protocol to SNA or TCP/IP. In one embodiment, SNMS may also have software running on the mainframe that converts the protocol to that recognizable by the SNMS Alarming Server 302. The event data is then transmitted via SNA or TCP/IP to the SNMS
[2087] Alarming Server 302. SNMS maintains a Signaling Event List 608 of all SS7 event types that is to be processed. In step 606, SNMS checks the Signaling Event List 608 and if the current event is found in the list, SNMS traps the event for processing. If the event is not found in the list, SNMS discards it.
[2088] In step 610, the event is parsed according to defined parsing rules 614. The parsing rules 614 specify which fields are to be extracted from which types of events, and are programmed into the SNMS code. The parsing of events in step 610 extracts only those event data fields needed within the alarm algorithms or displays. Also input to step 610 are scheduled events 612 from the Network Maintenance Schedule 340. Scheduled events 612 are used to identify each network event collected in step 602 that may be a result of scheduled network maintenance. This allows SNMS operators to account for those SS7 network outages that are caused by planned maintenance.
[2089] In step 616, the parsed event data is used to create standardized event objects in SNMS resident memory for use by other SNMS processes. Such event objects are read into the main process, Process Events 402, in step 510.
[2090] Referring now to FIG. 7, the detailed process of the Process Topology component 406 is illustrated. This process component retrieves network topology and configuration data from three types of sources, creates standardized topology data records, and stores this data for use by other SNMS processes. In particular, it feeds active topology data to Process Events 402, running on the Alarming Server 302, in step 502.
[2091] In step 702, the SNMS Topology server 306 collects topology data from three different sources. It collects current connectivity and configuration data generated by the SS7 network elements via the Control system 332. It collects topology data that has been entered into order entry and engineering systems and stored in Network Topology Databases 334. It also accepts manual overrides 336 via workstation. The collection of data from the Topology Database 334 and the Control system 332 occurs on a periodic basis, and is performed independently of the SNMS Alarming server 302. Unlike prior art systems that use data retrieved from PMUs 106, SNMS receives topology data from all types of network elements, including those that are not connected to a PMU 106 such as that of FIG. 2. SNMS also uses data reflecting the topology of foreign networks, such as those of a Local Exchange Carrier (LEC) or an international carrier. This data is used to perform impact assessments that will allow the SNMS user to determine facts such as which end customers may be impacted by an SS7 link outage. The type of topology data collected and used by SNMS, and for example, for the SS7 linkage of an STP 104 with a Switch/SSP 102, data is received by network order entry and engineering systems. The data and a brief description of its contents is provided below.
[2092] For the switched voice network supported by SS7, data is received by network order entry and engineering systems and used to perform SS7 event impact assessments:
[2093] For the SS7 linkage of a domestic STP 104 g to an international STP 104 h, data is received by network order entry and engineering systems:
[2094] For the purpose of performing impact assessments, Local Exchange Carrier (LEC) NPA/NXX assignments and End Office to Access Tandem homing arrangements are received by a calling area database that is populated by Bellcore's Local Exchange Routing Guide (LERG).
[2095] Foreign network STP 104 clustering and SSP 102 homing arrangements are received by SS7 network elements via a control system.
[2096] Data identifying certain aspects of each network element are received by a Switch Configuration File, which resides in an external system.
[2097] Data mapping each network DS-0 onto a DS-3 is received by Network Topology Databases. This data is used to assign DS-3 alarms received by NMS to DS-0 level circuits.
[2098] Data needed to overwrite data acquired through automated processes are provided by manual overrides.
[2099] Referring now back to FIG. 7 in step 704, the various topology data are parsed to extract the data fields that are needed by SNMS algorithms. The data are then standardized into event records that can be processed by Process Events 402.
[2100] In step 706, the standardized data records are validated against other data. For example, circuit topology records are validated against node topology records to ensure that end nodes are identified and defined.
[2101] In step 708, the topology data are stored on the Topology server 306 of FIG. 3 in a relational database, such as that offered by Sybase.
[2102] In step 710, the new topology records are passed from the Topology server 306 to the main SNMS process running on the Alarming server 302 and compared against the active configuration (i.e. configuration that is currently loaded into memory). Active alarm and GUI displays are reconciled to remove alarms that pertain to non-existent topology entries.
[2103] In step 712, the topology is stored on the Alarming Server 302 (for use by Process Events 402) in the form of flat files for performance reasons. At this time the flat file mirrors the Topology server 306 database from step 708. This flat file is only accessible by the main process. In step 714, the new topology records are loaded into active SNMS memory and new processes which require topology data now use the new configuration.
[2104] Referring now to FIG. 8, the detailed process of the Display Alarms component 412 is illustrated. This process component provides the results of SNMS processing to the user (referred to as the "operator"), and accepts operator input as actions to be performed within SNMS. Therefore, the process between Display Alarms 412 and Process Events 402 is two-way. It is important to note that while there is a single Process Events process 402 running for the entire SNMS system, there is a different instance of the Display Alarms process 412 running for each operator that is logged onto SNMS. That is, each operator instigates a separate execution of Display Alarms 412.
[2105] When an operator logs on SNMS, the first four steps, 802—808, execute as an initialization. From there, steps 810-838 operate as a continuous loop. The initialization provides each operator with a system state from which to work. In step 802, the current topology is read in and displayed via Graphical User Interface (GUI). Each operator has its own GUI process that is initialized and terminated based upon an operator request. Each GUI process manages its displays independently. Any status change is handled by the individual processes.
[2106] In step 804, a filter that defines the specific operator view is read in. Each operator can define the view that his/her GUI process will display. Filter parameters include:
[2107] 1. Traffic Alarms, Facility alarms, or both
[2108] 2. Acknowledged Alarms, Unacknowledged Alarms, or both
[2109] 3. Alarms on circuits within maintenance windows, Alarms on circuits that are not within a maintenance window, or both.
[2110] 4. Alarms on circuits that have associated transmission alarms (DS-3 alarms via outage ids), Alarms on circuits that do not have associated transmission alarms, or both.
[2111] 5. Alarms with a specified severity.
[2112] 6. Alarms on nodes/circuits owned by a specified customer id.
[2113] 7. Alarms on International circuits, Alarms on Domestic circuits, or both.
[2114] The operator's GUI displays are updated both upon initialization in step 804 and when filter changes are requested in steps 828 and 830. Each specific operator's instance of the Display Alarms 412 process opens a connection with Process Events 402 so that only alarm records relevant to the specific operator's filter are transmitted. In step 806, the specific operator's process registers itself with Process Events 402 to identify which alarms are to be sent. Ill step 808, the GUI display is presented to the operator.
[2115] The continuous execution of Display Alarms 412 begins in step 810. Each event that is to be retrieved and presented, as defined by the operator filter, is received and identified. In steps 812, 816, 820, 826, and 836 SNMS determines what to do with the event based on the event type identification made in step 810. In steps 812 and 816, if the event is determined to be an alarm update or a topology update, the operator's GUI display is updated to reflect this, in steps 814 and 818, respectively. Then the next event is received, in step 810.
[2116] In step 820, if the event is determined to be an operator action, two activities are required. First, in step 822, the operator's GUI display is updated to reflect the status change. Then, in step 824, a status change update is sent to the main process, Process Events 402, so that the status change may be reflected in SNMS records and other GUI processes (for other operators) can receive and react to the status changes.
[2117] In step 826, if the event is determined to be an operator display action, then it is determined if the action is a filter change request or a display request. In step 828, if it is determined to be a filter change request, then in step 830 the GUI process registers with Process Events 402 so that the appropriate alarms records are transmitted. In step 832, if it is determined to be an operator display request, then in step 834 the requested display is presented to the operator. Display requests may include:
[2118] 1. node detail and connection
[2119] 2. circuit connection
[2120] 3. linkset connection
[2121] 4. unknown topology alarms (alarms on objects that are not defined in the topology databases)
[2122] 5. STP pair connections
[2123] 6. Nodes contained within a LATA
[2124] 7. Home/Mate connections (for non-adjacent nodes)
[2125] 8. NPA/NXX lists
[2126] 9. trunk group lists
[2127] 10. end office access tandem
[2128] 11. rules definition help screens (aid the operator in understanding the actual algorithm used in generating the alarm
[2129] 12. recommended actions (operator defined actions that should be taken when a specific alarm is received)
[2130] In step 836, if the event is determined to be a termination request, then the specific operator's GUI process is terminated in step 838. Otherwise, the next event is received in step 810. Within the Display Alarm process, SNMS provides several unique display windows which support fault isolation, impact assessments, and trouble handling. All of the GUI displays which contain node and circuit symbols are "active" windows within SNMS (i.e. screens are dynamically updated when alarm status of the node or circuit change). All the displays are possible due to the set of MCI topology sources used within SNMS. SNMS has extensive topology processing of SNMS which is used in operator displays.
[2131] A. SNMS Circuits Map
[2132] This window displays topology and alarm status information for a selected linkset. As network events are received, SNMS recognizes the relationships between endpoints and isolates the fault by reducing generated alarms. This display allows the operator to monitor a linkset as seen from both sides of the signaling circuit (from the perspective of the nodes).
[2133] B. SAMS Connections Map
[2134] This window presents a cluster view of MCI's signaling network. All MCI and non-MCI nodes connected to the MCI STPs in the cluster are displayed along with the associated linksets. A cluster view is important since a single STP failure/isolation is not service impacting, but a cluster failure is since all MCI SPs have connectivity to both MCI STPs in the cluster.
[2135] C. SMWS Nonadjacent Node Map
[2136] This window presents a STP pair view of a selected LEC signaling network. All LEC SPs, STPs, and SCPs (with signaling relationships to the MCI network) connected LEC STP pair are displayed. MCI's area of responsibility does not include the LEC STP to LEC SSP signaling links, so no linksets are displayed here. This display allows the SNMS operator to monitor a LEC signaling network as seen by the MCI nodes.
[2137] D. SNMS LATA Connections Map
[2138] This window presents a map of all LEC owned nodes that are located within a specified LATA. As well, the MCI STP pair that serves the LATA is also displayed along with the associated linksets (where applicable). This display allows the operator to closely monitor a specific LATA if/when problems surface within the LATA. LATA problems, while outside MCI's domain of control, can introduce problems within the MCI network since signaling messages are shared between the networks. As well, MCI voice traffic which terminates in the specified LATA can be affected by LATA outages.
[2139] E. NPA-NXX Information List
[2140] This window presents a list of NPX-NXX's served by a specified LEC switch. This display is very valuable during impact assessment periods (i.e. if the specified LEC switch is isolated, which NPA-NXX's are unavailable).
[2141] F. End Office Information List
[2142] This window presents a list of LEC end office nodes which are homed to the specific LEC access tandem. This display is very valuable during impact assessment periods (i.e. if the specified LEC tandem switch is isolated, which end offices are unavailable).
[2143] G. Trunk Group Information List
[2144] This window presents a list of MCI voice trunks, connected to a specified MCI switch, and the LEC end office switches where they terminate. This display is very valuable during impact assessment periods (i.e. what end offices are impacted when a MCI switch is isolated). This display is also available for selected LEC end office switches.
[2145] H. Filter Definition Window
[2146] The SNMS operator can limited the scope of his displays to:
[2147] type of alarms that should be presented
[2148] severity of alarms that should be presented
[2149] acknowledged alarms, unacknowledged alarms, or both
[2150] alarms on circuits inside a planned outage window, alarms on circuits outside a planned outage window or both
[2151] alarms that are not the result of a specified transmission network outage
[2152] alarms on specified customer nodes or alarms on circuits connected to specified customer
[2153] I. Trouble Ticket Window
[2154] The SNMS operator can open trouble tickets on signaling alarms. These trouble tickets are opened in MCI's trouble ticketing system. Operators can also display the status of existing trouble tickets.
[2155] Referring now to FIG. 9, the detailed process of the Report On Data component 414 is illustrated. This process component, which runs on the Reporting server 304, stores SNMS-processed data and provides reports.
[2156] Standardized Network Element (NE) Event Records 914 are received with location specific time stamps. In step 902, the time stamps are converted into Greenwich Mean Time (GMT) so that standardized reports can be produced.
[2157] In step 904, all data received are stored in individual database tables. Data may also be archived for long-term storage to tape or disk. This data includes SNMS-generated alarms 916, standardized topology records 918, and performance statistics from PMUs 920. It may also include non-processed data, such as DS-3 alarms from NMS 338 and network maintenance schedule data 340.
[2158] In step 906, reports are produced. These reports may be custom or form reports. They may also be produced on demand, or per a schedule. These reports may be presented in a number of ways, including but not limited to electronic mail 908, X-terminal displays 910, and printed reports 912.
[2160] The next logical step from voice over the POTS is video. Today, computers are capable of making video "calls" to each other when connected to some type of computer network. However, most people only have access to a computer network by making a call from their modem on the POTS with another modem on a computer connected to a network, so that they can then "call" another computer on the network, which is in turn connected by a modem to another network computer. It is much simpler (and efficient) to call another person directly on the POTS and have the modems communicate with each other, without network overhead. ITU recommendation H.324 describes terminals for low bitrate (28.8 kbps modem) multimedia communication, utilizing V.34 modems operating over the POTS. H.324 terminals may carry real-time voice, data, and video, or any combination, including video telephony. H.324 terminals may be integrated into personal computers or implemented in stand-alone devices such as videotelephones and televisions. Support for each media type (voice, data, video) is optional, but if supported, the ability to use a specified common mode of operation is required, so that all terminals supporting that media type can interwork. H.324 allows more than one channel of each type to be in use. Other Recommendations in the H.324 series include the H.223 multiplex (combination of voice, data and video), H.245 control, H.263 video codec (digital encoder and decoder), and G.723.1.1 audio codec.
[2161] H.324 makes use of the logical channel signaling procedures of ITU Recommendation H.245, in which the content of each logical channel is described when the channel is opened. Procedures are provided for allowing each caller to utilize only the multimedia capabilities of their machine. For example a person trying to make a video (and audio) call to someone who only has audio and not video capabilities can still communicate with the audio method (G.723.1.1)
[2162] H.324 by definition is a point-to-point protocol. To conference with more than one other person an MCU (Multipoint Control Unit) is needed to act as a video-call bridge. H.324 computers may interwork with H.320 computers on the ISDN, as well as with computers on wireless networks.
[2163] A. Components of Video Telephony System
[2164] 1. DSP modem pools with ACD.
[2165] A Digital Signal Processor (DSP) modem pool is a modem bank, with each modem having the ability to be programmed for extra functions (like new V. modem protocols, DTMF detection, etc.) A call is routed from the MCI switch to an ACD. The ACD keeps a matrix of which DSP modems are available. The ACD also 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. In an alternative embodiment, DSP resources can be deployed without an ACD, directly connected to a switch. In this embodiment, the DSP resources are managed using an NCS-based routing step.
[2166] 2. Agent
[2167] An Agent can be a human Video Operator (video capable MTOC), or an Automated program (video ARU). The ACD knows which Agent ports are available and connects an Agent to an Agent Port.
[2168] 3. Video on Hold Server
[2169] If the ACD has no Agent ports available, then the caller is connected to the Video On Hold Server, which has the ability to play advertisements and other non-interactive video, until the ACD finds a free Agent port.
[2170] 4. Video Mail Server
[2171] Video-mail messages are stored here. Customers can manage their mail and record greetings to be stored on this server.
[2172] 5. Video Content Engine
[2173] Video On Demand content resides on the Video Content Engine. Video stored here can be previously recorded video-conferences, training videos, etc.
[2174] 6. Reservation Engine
[2175] When people want to schedule a multi-party video-conference, they can specify the participants and time of the conference on this system. Configuration can be done with the help of a human Video Operator or by some other form entry method.
[2176] 7. Video Bridge
[2177] Because H.324 is a point-to-point protocol, a Multi-point Conferencing Unit (MCU) needs to manage each participants call and re-direct the video streams appropriately. MCU conferencing will be available for customers with H.324 and H.320 compliant systems.
[2178] B. Scenario
[2179] A computer or set-top TV has H.324 compliant software, and a modem for use over POTS, most likely to be 28.8 kbps (V.34) or higher. One objective is to call another party. If they do not answer or are busy, the originator lias the option of leaving video-mail for the destination party. Another objective is to schedule and participate in a conference with more than two participants.
[2180] C. Connection Setup
[2181]FIG. 19B illustrates a call connection setup in accordance with a preferred embodiment. There are three methods for making a video-call to someone.
[2182] The first method is to simply call them (from 1 and 7 of FIG. 19B. If the destination is busy or doesn't answer, th en the caller can make another call to 1 800 VID MAIL and perform the appropriate procedures as follows.
[2183] When a user dials "1 800 VID MAIL" at 1, the ACD on the DSP modem pool will connect a switch to a modem 2 and a port to an Agent 3. Then the user logs-in to the system with a special, custom terminal program that utilizes the data stream part of the H.324 bandwidth (using the ITU T.120 standard), called the V-mail Data Interface (VMDI). From a graphical user interface, icon or other menu, the caller can choose to:
[2184] browse and search a directory of video-capable MCI customers,
[2185] call another H.324 compliant software program,
[2186] create a video-mail for Store &, Forward for later delivery,
[2187] personalize and record their video-mail greeting messages,
[2188] view and manage their video-mail, or
[2189] view selections from a library of recordings (Video On Demand).
[2190] In an alternate embodiment, a user can dial "1 800 324 CALL" to call a number. Then, if the destination number was 1 319 375 1772, the modem dial string would be "ATDT 1 800 324 CALL,,, 1 319 375 1772" (the comma ',' tells the modem to do a short pause while dialing.) When the connection to 1 800 324 CALL is made, a connection is made from the originator, to an MCI switch 1, to an ARU 5 a, selected by an ACD 2 a, 3 a.
[2191] The ARU 5 a detects DTMF tones entered through a telephone keypad or other device for generating DTMF tones to get the destination number. The originator remains on hold while the ARU 5 a makes a separate call to the destination number 5 a, 6 a and 7. If the destination answers, the originator is connected to the destination, both party's modems can connect, and the ARU 5 a is released. If the destination is busy or does not answer, the call is transferred to 1 800 VID MAIL or an Agent through the DSP modem pool 2. If there are no DTMF tones detected, the call is transferred to an Agent through the DSP modem pool 2. The Agent will make an H.324 connection with the caller and ask for their destination number (or provide help.) The architecture for this alternative is similar to how faxes are detected and transmitted in the directlineMCI system as discussed with respect to an alternative embodiment.
[2192] D. Calling the Destination
[2193] When the destination number is known, the Video On Hold Server provides the video input for the H.324 connection 4. A new call is made from the Agent 5, 6 to the destination number 7. One concern that required analysis while working out a detailed embodiment required determining if modems could re-synchronize after a switch operation without going off-line. If the destination number answers and is a modem, a connection MUST be made at the same speed as the originator modem speed. After modem handshaking is performed, the ACD instructs the switch to release the agent 3, 5 and releases the modems 2 and 6 and connects the originator to the destination 1 and 7. The destination PC realizes that the connection is an H.324 call (not a fax or otherwise) and the video-call proceeds. In an alternate embodiment, if the destination answers and is a modem, a connection is made. Then, two H.324 calls are using two DSP modems. The Agent can be released from both calls 3 and 5. The incoming data from each call is copied to the other call 2 and 6. This way, an Agent can monitor the video call for Video Store &, Forward 9. When one connection drops carrier, the video-call is complete, and the modem carrier for the remaining call is dropped.
[2194] E. Recording Video-Mail, Store & Forward Video and Greetings
[2195] If a destination number does not answer or is busy, the Video Mail Server will play the appropriate Video-Mail greeting for the owner of the destination number 8. The caller then leaves a video-message, which is stored on the Video Mail Server. The recording of video for Store &, Forward Video is exactly the same as leaving a video-message, described above. Parameters such as destination number, forwarding time, and any other audio S&F features currently available are entered through the VMDI or communicated with a human video operator (or automated video ARU.)
[2196] To record a personalized greeting for playback when someone cannot reach you because you are busy or do not answer, is similar to leaving Video-Mail. The option to do this is done through the VMDI or communicated with a human video operator.
[2197] F. Retrieving VideoMail and Video On Demand
[2198] Users have the choice of periodically polling their video-mail for new messages, or have the video-mail server call them periodically when they have a new message waiting. Configuration is done through the VMDI or human video operator. Managing and checking video-mail is also performed through the VMDI or communicated with a human video operator.
[2199] Choice of video to view for Video On Demand (VOD) is through the VMDI. These videos can be previously recorded video-conferences, training videos, etc. and are stored on the Video Content Engine 9.
[2200] G. Video-conference Scheduling
[2201] A user can navigate through the VMDI or Internet 10 WWW forms, or communicate with a human video operator to schedule a multi-point conference. This information is stored on the Reservation Engine 11. The other conference participants are notified of the schedule with a video-mail, e-mail message or otherwise. There will be an option to remind all registered conference participants at a particular time (e.g. 1 hour before the conference), through video-mail (or e-mail, voice-mail, paging service or any other available notification method). The MCU (video bridge) can call each participant 12, or H.324 users can dial In to the MCU at the scheduled time 12.
[2203]FIG. 19E illustrates an architecture for transmitting video telephony over the Internet in accordance with a preferred embodiment. Real-time Transmission Protocol (RTP) based video-conferencing refers to the transmission of audio, video and data encapsulated as RTP messages. For a RTP-based video-conferencing session, a end-user station first establishes a dial-up Point-to-Point (PPP) connection with the Internet which is then used to transport the RTP messages. Audio information is compressed as per G.723.1.1 audio codec (coder-decoder) standards, Video is compressed in accordance with ITU H.263 video codec standards and data is transmitted as per ITU-T.120 standards.
[2204] RTP is a protocol providing support for applications with real-time properties. While UDP/IP is its initial target networking environment, RTP is transport-independent so that it can be used over IPX or other protocols.
[2205] RTP does not address the issue of resource reservation or quality of service control; instead, it relies on resource reservation protocols such as RSVP. The transmission service with which most network users are familiar is point-to-point, or unicast service. This is the standard form of service provided by networking protocols such as HDLC and TCP.
[2206] Somewhat less commonly used (on wire-based networks, at any rate) is broadcast service. Over a large network, broadcasts are unacceptable (because they use network bandwidth everywhere, regardless of whether individual sub-nets are interested in them or not), and so they are usually restricted to LAN-wide use (broadcast services are provided by low-level network protocols such as IP). Even on LANs, broadcasts are often undesirable because they require all machines to perform some processing in order to determine whether or not they are interested in the broadcast data.
[2207] A more practical transmission service for data that is intended for a potentially wide audience is multicast. Under the multicast model on a WAN, only hosts that are actively interested in a particular multicast service will have such data routed to them; this restricts bandwidth consumption to the link between the originator and the receiver of multicast data. On LANs, many interface cards provide a facility whereby they will automatically ignore multicast data in which the kernel has not registered an interest; this results in an absence of unnecessary processing overhead on uninterested hosts.
[2208] A. Components
[2209] RSVP Routers with MBONE capability for broadcast of video from the Video Content Engine and the MCI Conference Space network. MCI will have an MBONE network that multicasts locally and transmits many unicasts out the Internet.
[2210] RSVP is a network control protocol that will allow Internet applications to obtain special qualities-of-service (QOS's) for their data flows. This will generally (but not necessarily) require reserving resources along the data path(s) either ahead of time or dynamically. RSVP is a component of the future "integrated services" Internet, which provides both best-effort and real-time qualities of service. An embodiment is presented in the detailed specification that follows.
[2211] When an application in a host (end system) requests a specific QOS for its data stream, RSVP is used to deliver the request to each router along the path(s) of the data stream and to maintain router and host state to provide the requested service. Although RSVP was developed for setting up resource reservations, it is readily adaptable to transport other kinds of network control information along data flow paths.
[2212] 1. Directory and Registry Engine
[2213] When people are connected to the Internet (whether through modem dial- up, direct connection or otherwise), they can register themselves in this directory. The directory is used to determine if a particular person is available for conferencing.
[2214] 2. Agents
[2215] An Agent can be a human Video Operator (video capable MTOC), or an Automated program (video ARU). An Internet ACD in accordance with a preferred embodiment is designed so that Agent ports can be managed. The ACD will know which Agent ports are available and connects an Agent to an available Agent Port. If the ACD has no Agent ports available, then the caller is connected to the Video On Hold Server, which has the ability to play advertisements and other non-interactive video,—until the ACD finds a free Agent port.
[2216] 3. Video Mail Server
[2217] Video-mail messages are stored here. Customers can manage their mail and record greetings to be stored on this server.
[2218] 4. Video Content Engine
[2219] Video On Demand content resides on the Video Content Engine. Video stored here may be previously recorded video-conferences, training videos, etc.
[2220] 5. Conference Reservation Engine
[2221] When people want to schedule a multi-party video-conference, they can specify the participants and time of the conference on this system. Configuration can be done with the help of a human Video Operator or by some other form entry method.
[2222] 6. MCI Conference Space
[2223] This is the virtual reality area that customers can be present in. Every participant is personified as an "avatar". Each avatar has many abilities and features, such as visual identity, video, voice, etc. Avatars interact with each other by handling various objects that represent document sharing, file transferring, etc., and can speak to each other as well as see each other.
[2224] 7. Virtual Reality Space Engine
[2225] The Conference Spaces are generated and managed by the Virtual Reality Engine. The virtual reality engine manages object manipulation and any other logical descriptions of the conference spaces.
[2226] B. Scenario
[2227] If a user has a current connection to the Internet. The user will utilize H.263 compliant system software utilizing RTP (as opposed to TCP) over the Internet. If the user also desires to participate in VR MCI confe-ence-space, and create/view video-mail, the user can join a VR session.
[2228] C. Connection Setup
[2229] The simplest way to make a video call to another person on the Internet is to simply make the call without navigating through menus and options as an initial telephone call. However, if the destination is busy or not answering, MCI provides services for depositing messages.
[2230] A customer can login to a telnet server (e.g. telnet vmail.mci.com), or use a custom-made client, or the WWW (e.g. http://vmail.mci.com). The services menu is referred to as the V-Mail Data Interface (VMDI), similar to the VMDI available when dialing through POTS as described above.
[2231] From a menu, the caller can choose to:
[2232] browse and search a directory of video-capable MCI customers,
[2233] call another H.263 compliant software program,
[2234] create a video-mail for Store & Forward for later delivery,
[2235] personalize and record their video-mail greeting messages,
[2236] view and manage their video-mail, and
[2237] view selections from a library of recordings (Video On Demand).
[2239] D. Recording Video-Mail, Store & Forward Video and Greetings
[2240] If an Agent determines that a destination party is not available (off-line, busy, no answer, etc.), the Video Mail Server plays an appropriate Video- Mail greeting for the owner of the destination number 8. The caller then leaves a video-message, which is stored on the Video Mail Server. The recording of video for Store &, Forward (S &F) Video is exactly the same as leaving a video-message, described above. Parameters such as destination number, forwarding time, and any other audio S&,F features currently available are entered through the VMDI or communicated with a human video operator (or automated video ARU.)
[2241] Customers may record their own personalized greetings to greet callers that cannot reach them because they are busy or do not answer. This is accomplished in a manner similar to leaving Video-Mail, through the VMDI or communicated with a human video operator.
[2242] E. Retrieving Video-Mail and Video On Demand
[2243] Users have the choice of periodically polling their video-mail for new messages, or having the video-mail server call them periodically when they have a new message waiting. Configuration is done through the VMDI or human video operator. Managing and checking video-mail is also performed through the VMDI or communicated with a human video operator. A choice of video to view for Video On Demand (VOD) is provided through the VMDI. These videos can be previously recorded video-conferences, training videos, etc. and are stored on the Video Content Engine.
[2244] F. Video-conference Scheduling
[2245] A user can navigate through the VMDI or Internet 10 WWW forms, or communicate with a human video operator to schedule a conference in the Conference Space. The information is stored on the Conference Reservation Engine 8. The other conference participants are notified of the schedule with a video-mail, e-mail message or otherwise. An optional reminder is provided for all registered conference participants at a particular time (e.g. 1 hour before the conference), through video—mail (or e-mail, voice-mail, paging service or any other available notification method).
[2246] G. Virtual Reality
[2247] For multiple party conferences, a virtual meeting place can be generated by the Virtual Reality Space Engine. The implementation of the interface includes an embodiment based on VRML. Each person is in control of an "avatar." Each avatar can have many different features such as visual representation (static representation or live video "head") and audio (voice or music). Data exchange and collaboration are all actions that can be performed in each VR conference room. The private MBONE network allows the multi-casting of conference member's data streams. Since everyone has a different view when interacting in VR-space, the VR Space Engine can optimize the broadcast of everyone's incoming H.263 streams to everyone else by multi-casting only those avatar streams in view for each particular avatar.
[2249] MCI Video-Conferencing describes an architecture for multimedia communications including real-time voice, video and data, or any combination, including video telephony. The architecture also defines inter-operation with other video-conferencing standards. The architecture also defines multipoint configurations and control, directory services and video mail services.
[2250] A. Features
[2251] Video-Conferencing architecture is a multimedia services system and is designed to provide a number of features and functions including,
[2252] Point-to-Point Video Telephony
[2253] Multimedia video-conferencing with a MCU for control and multimedia information processing
[2254] Support for Gateways for interworking with other video-conferencing systems based on ITU H.320 and ITU H.324 standards
[2255] Support for real-time voice, video and data or any combination
[2256] Multimedia information streams are transported between the end-user terminals using standard transport protocol RTP
[2257] Support for dynamic capability exchange and mode preferences, like ITU H.263 video and ITUG.723 audio, between end-user terminals FIG. 19C illustrates a Video-Conferencing Architecture in accordance with a preferred embodiment. The components and details of the video-conferencing architecture are detailed below.
[2258] B. Components
[2259] The Video-Conferencing System is comprised of a set of components including,
[2260] End-User Terminals
[2261] LAN Interconnect System
[2262] ITU H.323 Server
[2263] Support Service Units
[2264] 1. End-User Terminals
[2265] The end-user terminals are the end points of communication. Users communicate and participate in video conferences using the end-user terminals. End-user terminals, including ITU H.323 terminals 1 & 8, ITU H.320 terminal 9 and ITU H.324 terminal 10, are interconnected through the ITU H.323 Server which provides the call control, multi-point control and gateway functions. End-User terminals are capable of multimedia input and output and are equipped with telephone instruments, microphones, video cameras, video display monitors and keyboards.
[2266] 2. LAN Interconnect System
[2267] The LAN Interconnect System 3 is the interface system between the MCI Switch Network 2 and the different H.323 Systems including H.323 Server 4, Video Content Engine 5, Video Mail Server 6 and also the H.323 Directory Server 7. End-User terminals participating in video-telephony sessions or video- conferencing sessions establish communication links with the MCI switch network and communicate with the H.323 Server through the LAN Interconnect System. The LAN Interconnect system provides ACD-like functionality for the H.323 video-conferencing system.
[2268] 3. ITU H.323 Server
[2269] The H.323 Server 4 provides a variety of services including call control, multipoint control, multipoint processing, and gateway services for interworking between terminals supporting different video-conferencing standards like ITU H.320 and ITU H.324.
[2270] The H.323 Server is comprised of a set of individual components which communicate with each other and with the other external systems like end- user terminals, video mail server and H.323 directory server. The different components of the H.323 Server include:
[2271] H.323 Gatekeeper
[2272] Operator Services Module
[2273] H.323 Multipoint Control Unit (MCU)
[2274] H.323 Gateway
[2275] 4. Gatekeeper
[2276] The H.323 Gatekeeper provides call control services to the H.323 terminals and Gateway units. The Gatekeeper provides a variety of services including:
[2277] Call Control Signaling with terminals, gateways and MCU;
[2278] Admissions Control for access to the video-conferencing system;
[2279] Call Authorization;
[2280] Bandwidth control and management;
[2281] Transport Address Translation for translating addresses between different kinds of interworking video-conferencing systems;
[2282] Call Management of on-going calls;
[2283] Interfaces with the Directory Server[7] to provide directory services; and
[2284] Interfaces with the Video Mail Server[6] for video mail services.
[2285] The Gatekeeper uses the ITU H.225 stream packetization and synchronization procedures for the different services, and is tightly integrated with the Operator Services Module for offering manual operator services.
[2286] 5. Operator Services Module
[2287] The Operator Services Module offers manual/automatic operator services and is tightly integrated with the gatekeeper. The manual or the automatic operator terminal, located elsewhere on the LAN, interacts with the gatekeeper through the Operator Services Module to provide all the required operator services.
[2288] 6. Multipoint Control Unit (MCU)
[2289] The MCU is comprised of the Multipoint Controller and the Multipoint Processor and together provides multipoint control and processing services for video-conferences. The multipoint controller provides control functions to support conferences between three or more terminals. The multipoint controller carries out capabilities exchange with each terminal in a multipoint conference. The multipoint processor provides for the processing of audio, video and/or data streams including mixing, switching and other required processing under the control of the multipoint controller. The MCU uses ITU H.245 messages and methods to implement the features and functions of the multipoint controller and the multipoint processor.
[2290] 7. Gateway
[2291] The H.323 Gateway provides appropriate translation between the various transmission formats. The translation services include,
[2292] Call Signaling message translation between H.225 and H.221 which is the part of the H.320 system;
[2293] Communication procedures translation between H.245 and H.242; and
[2294] Translation between the video, audio and data formats like H.263, H.261, G.723, G.728 and T.120.
[2295] The H.323 Gateway provides conversion functions for transmission format, call setup and control signals and procedures.
[2296] 8. Support Service Units
[2297] The Support Service Units include the H.323 Directory Server 7, the Video-Mail Server 6 and the Video Content Engine 5 which interact with the H.323 Server for providing different services to the end-user terminals. The H.323 Directory Server provides directory services and interacts with the gatekeeper unit of the H.323 Server. The Video Mail Server is the repository of all the video mail generated by the H.323 system and interacts with the gatekeeper unit of the H.323 server for the creation and playback of video mail. The Video Content Engine is the repository of all other types of video content which can be served to the end-user terminals. The Video Content Engine interacts with the gatekeeper unit of the H.323 Server.
[2298] C. Overview
[2299] The H.323 based video-conferencing architecture completely describes an architecture for multimedia communications including real-time voice, video and data, or any combination including video telephony. Users with H.323 terminals can participate in a multimedia video-conferencing session, a point-to-point video telephony session, or an audio only session with other terminal users not equipped with video facilities. The architecture also includes gateways for interworking with other video-conferencing terminals based on standards like ITU H.320 and ITU H.324.
[2300] The architecture includes a directory server for offering complete directory services including search facilities. A video mail server is an integral part of the architecture providing for the recording and playback of video mail. A video content engine is also part of the overall architecture for offering multimedia content delivery services.
[2301] H.323 terminals participating in a video-conferencing or a video telephony session communicate with the H.323 server through the MCI switch network. The H.323 server offers a variety of services including call control, information stream delivery, multi-point control and also gateway services for interworking with H.320 or H.324 terminals. The server also offers directory services and video mail services.
[2302] A H.323 terminal initiating a video call establishes a communication link with the H.323 Server through the MCI switch network. On admission to the network by the H.323 server, the server offers a directory of other available terminals to the call initiating terminal which selects a destination terminal or a destination group to participate in a video conference. The server then sets up a communication link with the selected destination terminal or terminals and finally bridges the calling terminal and the called terminal/terminals. If the destination terminal is unavailable or busy, the server offers the calling terminal an option to deposit a video mail. The server also notifies the recipient of the video mail and offers the recipient services for retrieval of the video mail on-demand. Additional services like content delivery on-demand to H.323 terminals are also offered and controlled by the H.323 server.
[2303] D. Call Flow Example
[2304] The Call Flow for the H.323 architecture based video-conferencing is explained in detail for different call types including, Point-to-Point Calls including calls to other H.323, H.320 and H.324 terminals; and Multipoint Video-Conference Calls.
[2305]FIG. 19C illustrates various call flows in accordance with a preferred embodiment.
[2306] 1. Point-to-Point Calls
[2307] a) Case 1: H.323 Terminal to another H.323 Terminal
[2308] A call initiating H.323 terminal 1 initiates a call to another H.323 terminal[8] through the MCI Switch Network. The gatekeeper is involved in controlling the session including call establishment and call control. The Terminal end-user interface is any commercially available Web-browser.
[2309] Calling terminal 1 initiates a dial-up call to the MCI Switch network;
[2310] the call is terminated on the H.323 Gatekeeper module of the H.323 Server 4 through the LAN Interconnect 3 system;
[2311] a PPP link is established between the calling terminal and the Gatekeeper 4 on a well-know unreliable transport address/port;
[2312] Calling terminal sends a admission request message to the Gatekeeper[4]
[2313] The Gatekeeper 4 sends an admission confirm message and communicates with the Directory Server 7 and sends back directory information to calling terminal for display at the calling terminal, and the directory information is displayed as a web-page along with a choice of calling modes including Point-to-Point or Conference mode;
[2314] the admissions exchange is followed by the setting up of a reliable connection for H.225 call control messaging on a well known port;
[2315] the terminal user chooses the point-to-point mode and also chooses the destination of the call. This is the setup request message;
[2316] the gatekeeper 4 together with the operator services module/operator proceeds with calling the called terminal 8 with a setup request;
[2317] if setup request fails, the gatekeeper 4 informs the calling terminal 1 of the failure and provides an option for the calling terminal 1 to leave a video mail;
[2318] if the user at calling terminal 1 chooses to leave a video mail for user at the destination terminal 8, the gatekeeper 4 establishes a connection with the Video Mail Server 6 and receives a reliable port address from the mail server 6 for a H.245 connection;
[2319] the gatekeeper 4 additionally establishes a connection for H.225 call control with the video mail server 6.
[2320] the gatekeeper 4 in-turn sends a reliable port address to calling terminal 1 for H.245 control channel. The gatekeeper 4 may be involved in H.245 control channel communications;
[2321] the calling terminal 1 establishes a reliable connection for H.245 control channel and H.245 procedures like capability exchange, mode preferences, etc. are carried out;
[2322] after the capabilities exchange, H.245 procedures will be used to establish logical channels for the different media streams;
[2323] the capabilities exchange also involves determination of dynamic port addresses for the transport of the different media streams;
[2324] the media streams are transported over the dynamic ports in the various logical channels;
[2325] once the terminal has completed the video mail, it closes the logical channel for video after stopping transmission of the video stream;
[2326] data transmission is stopped and logical channel for data is closed;
[2327] audio transmission is stopped and logical channel for audio is closed;
[2328] H.245 call clearing message is sent to the peer entity;
[2329] calling terminal 1 transmits a disconnect message on the H.225 port to the gatekeeper 7 which in turn sends the disconnect message to the video mail server 6;
[2330] the disconnect messages are acknowledged and the call is disconnected;
[2331] if the setup request is a success, called terminal 8 responds with a connect message which include a reliable port address for H.245 connection;
[2332] the gatekeeper 4 responds to the calling terminal 1 with the connect message along with the port address for the H.245 control channel communications;
[2333] calling terminal 1 sets up a connection for H.225 call control signaling with the gateway 4, establishes another connection for H.245 control channel communications and responds to the gateway 4 with connect acknowledgment message;
[2334] the gatekeeper 4 in-turn sends the connect acknowledgment message to called terminal 8.
[2335] called terminal 8 now sets up a H.225 call control connection and also establishes another connection for H.245 with the gatekeeper 4 for control channel communications;
[2336] the terminals, having established a H.245 control channel for reliable communication, exchange capabilities and other initial procedures of H.245, and an audio channel may be optionally opened before the capabilities exchange;
[2337] following the capabilities exchange, logical channels over dynamic ports are established for each of the media streams;
[2338] once the media logical channels are open over dynamic ports, media information can be exchanged;
[2339] during the session, H.245 control procedures may be invoked for changing the channel structure like mode control, capability, etc.;
[2340] also H.225 control channel is for specific procedures as requested by the gatekeeper[4] including call status, bandwidth allocation, etc.;
[2341] for termination, either terminal may initiate a stop video message, discontinue video transmission and then close the logical channel for video;
[2342] data transmission is discontinued and the logical channel for data is closed;
[2343] audio transmission is discontinued and logical channel for audio is closed;
[2344] H.245 end session message is sent and transmission on the control channel is stopped and the control channel is closed;
[2345] terminal receiving the end session message will repeat the closing procedures and then H.225 call signaling channel is used for call clearing; and
[2346] terminal initiating the termination will send a disconnect message on the H.225 control channel to the gatekeeper 4 which in turn sends a disconnect message to the peer terminal. The peer terminal acknowledges the disconnect which is forwarded to the initiating terminal and the call is finally released.
[2347] b) Case 2: H.323 Terminal to H.320 Terminal
[2348] A call initiated from a H.323 terminal 1 invokes a call to a H.320 terminal 9 through an MCI Switch Network. The gatekeeper along with the gateway is involved in controlling the session including call establishment and call control. A terminal end-user interface is any of the commercially available Web-browsers or a similar interface.
[2349] The call flow is similar to a H.323 terminal calling another H.323 terminal as explained in the previous case except that a gateway 4 component is introduced between the gatekeeper 4 and the called terminal 9. The gateway transcodes H.323 messages including audio, video, data and control to H.320 messages and vice-versa. If the H.320 terminal 9 initiates a call to a H.323 terminal[1], the initial dial-up routine is performed by the gateway and then the gatekeeper takes over the call control and the call proceeds as explained in the previous case.
[2350] c) Case 3: H.323 Terminal to H.324 Terminal
[2351] Call initiating H.323 terminal 1 initiates a call to a H.324 terminal 10 through the MCI Switch Network. The gatekeeper along with the gateway is involved in controlling the session including call establishmenit and call control. The Terminal end-user interface is a Web-browser or a similar interface.
[2352] The call flow is similar to a H.323 terminal calling another H.323 terminal as explained in the previous case except that a gateway 4 component is introduced between the gatekeeper 4 and the called terminal 9. The gateway 4 transcodes H.323 messages including audio, video, data and control to H.324 messages and vice-versa.
[2353] If the H.324 terminal 10 initiates a call to a H.323 terminal 1, the initial dial-up routine is performed by the gateway and then the gatekeeper takes over the call control and the call proceeds as explained in the previous case.
[2354] 2. Multipoint Video-Conference Calls
[2355] In the case of multipoint video-conference, all the terminals exchange initial call signaling and setup messages with the gatekeeper 4 and then are connected to the Multipoint Controller 4 for the actual conference including H.245 control channel messaging through the gatekeeper 4.
[2356] The following are the considerations for setting up a conference:
[2357] After the initial admission control message exchange, the users are presented with a web page with information about conference type and a dynamic list of participants.
[2358] Participants joining later are presented with a web page with conference information and also are requested to enter authentication information
[2359] All users get connected to the multipoint controller[4] through the gatekeeper[4]
[2360] The multipoint controller[4] distributes information among the various participants
[2361] E. Conclusion
[2362] The video-conferencing architecture is a total solution for multimedia communications including real-time voice, video and data, or any combination, including point-to-point video telephony. The architecture defines interworking with other systems utilizing ITU recommendations. Additional services including directory services and video mail services are also part of the overall architecture.
[2364] The Video Store and Forward Architecture describes a video-on-demand content delivery system. The content may include video and audio or audio only. Input source for the content is from the existing video-conferencing facility of MCI or from any video/audio source. Input video is stored in a Digital Library in different standard formats like ITU H.320, ITU H.324, ITU H.263 or MPEG and delivered to the clients in the requested format. Delivery is at different speeds to the clients either on the Internet or on dial-up lines including ISDN and with a single storage for each of the different formats.
[2365] A. Features
[2366] The Video Store and Forward Architecture is designed with a rich set of features and functionality including:
[2367] Delivers Video and Audio on demand;
[2368] Supports different compression and transmission standards including ITU H.320, ITU H.324, MPEG and ITU H.263 on both IP (Internet Protocol) and RTP (Real Time Transport Protocol);
[2369] Supports content delivery on the Internet, by dial-up ISDN lines and by low speed (28.8 kbps) Analog Telephone lines;
[2370] Supports single source of content and multiple storage and delivery formats and multiple delivery speeds; and
[2371] Supports Content Management and Archival in multiple formats.
[2372] B. Architecture
[2373]FIG. 19D is a Video Store and Forward Architecture in accordance with a preferred embodiment.
[2374] C. Components
[2375] The Video Store and Forward architecture can be completely described by the following components.
[2376] Content Creation and Transcoding.
[2377] Content Management and Delivery.
[2378] Content Retrieval and Display.
[2379] 1. Content Creation and Transcoding
[2380] Input sources include analog video, video from Multi-Point Control Unit (MCU) and other video sources 1 a and 1 b. Input content is converted to standard formats like ITU H.261, ITU H.263, ITU H.320, ITU H.263, ITU H.324, MPEG and also formats to support delivery of H.263 over RTP and H.263 over an Internet Protocol 2 and 3. Input can initially be coded as H.263 and optionally transcoded into the various other formats and stored 2. The transcoded content is stored on different servers, one for each Content type to serve the various clients each supporting a different format 5 a, 5 b, 5 c, 5 d, 5 e and 5 f.
[2381] 2. Content Management and Delivery
[2382] Content is stored on different servers with each server supporting a specific format and is managed by a Digital Library consisting of:
[2383] Index Server for managing the indexes and archival of content 4,
[2384] Object Servers for storage of content 5 a, 5 b, 5 c, 5 d, 5 e and 5 f,
[2385] Proxy Client as a front end to the Index and Object Server and interacting with the different clients requesting for content 6.
[2386] Content Delivery is by:
[2387] Internet,
[2388] Dial-up ISDN lines,
[2389] Dial-up Analog Telephone lines at 28.8 kbps, and
[2390] Content format is either a MPEG Stream, H.320 Stream, H.324 Stream, or a H.263 Stream transported over IP or RTP.
[2391] 3. Content Retrieval and Display
[2392] Content Retrieval is by clients supporting various formats:
[2393] MPEG Client—7 a;
[2394] ITU H.263 Client supporting RTP—7 b;
[2395]13 ITU H.263 Client supporting IP—7 c;
[2396] ITU H.320 Client—7 d; and
[2397] ITU H.324 Client—7 e.
[2398] Content is retrieved by the different clients on demand and displayed on a local display.
[2399] Clients support VCR like functions like fast-forward, re-wind, etc.
[2400] D. Overview
[2401] Analog Video from different sources and H.320 video from an MCU is received as input and transcoded into various formats as required like ITU H.324, ITU H.261, ITU H.263 or MPEG and stored on the different Object Servers dedicated for each of the formats. The Object Servers are in turn managed by the Index Server and are together called a Digital Library. Any request from the clients for content is received by the Index Server and in turn serviced by the Object Server through a Proxy Client.
[2402] The Index Server or the Library Server respond to requests from the proxy client and store, update and retrieve objects like H.261, H.263 or MPEG multimedia information on the object servers. Then they direct the object server to deliver the retrieved information back to the proxy client. The Index Server has the complete index information of all the different objects stored on the object servers and also information on which of the object server the information is residing on. The index information available on the Index Server is accessible by the proxy client for retrieval of multimedia content from the different object servers. Security and access control is also part of the index server functionality.
[2403] The Object Servers are an integral part of the Digital Library providing physical storage and acting as the repository for the multimedia content, including the video-conferencing information stream from the conferencing facilities. The multimedia content is stored in standard formats which can be retrieved by the proxy client on demand. Each of the Object Servers are dedicated for a specific format of multimedia content like H.261, H.263, MPEG, etc. The organization and index information of the multimedia content including information about the specific object server dedicated for a multimedia format is managed by the index server. The Object Server delivers the stored multimedia content to the proxy client upon receiving specific instructions from the index server.
[2404] The Proxy Client is the front end of the digital library and is accessed by all the clients through the Internet for on-demand multimedia content. The Proxy Client also is a World Wide Web (WWW) Server and delivers a page to the clients when accessed. The clients interact with the Proxy Client and thereby with the Digital Library through the WWW pages. Clients request multimedia content by interacting with the WWW pages. The Proxy Client receives the request from the clients through the WWW pages and processes the request. The Proxy Client then communicates with the index server with object queries as requested by the client. The index server then communicates with one of the object servers dedicated to the requested multimedia format and, based on the index information available at the index server, directs the object servers to deliver the requested multimedia content to the Proxy Client. The Proxy Client receives the multimedia content from the object server and delivers it to the client making the request.
[2405] The Clients connect to the Servers either through the Internet or by dial-up connections on an ISDN line or an Analog line at 28.8 Kbps depending on the video format requested and the client capabilities. A H.320 client connects by an ISDN line and a H.324 client requests services on an analog telephone line at 28.8 Kbps. A MPEG client or a H.263 client using RTP or a H.263 client using IP request services through the Internet. The front-ends for multimedia content query and display like the WWW browsers are integrated as a part of the Client and provide an easy-to-use interface for the end-users.
[2406] A request for video from the client is received by the proxy client which routes the request to the Index Server which is turn processes the request and communicates with a specific Object Server in addition to indexing the content for delivery. The Object Server delivers the requested content to the client through the Internet. In the case of the dial-up links, the content is delivered back on the already established link.
[2407] In sum, the Video Store and Forward architecture describes a comprehensive system for the creation, transcoding, storage, archiving, management and delivery of video and audio or audio on demand. The delivery of video and audio or audio will be on the Internet or by ISDN or Analog Telephone dial-up lines. Content including video and audio or audio is delivered at various data rates from individual storage locations, each serving a different delivery speed.
[2409] A. Hardware Architecture
[2410]FIG. 96 shows the system hardware for allowing a video operator to participate in a video conference or video call, providing numerous services to the video callers. Among the services provided are: answering incoming video calls or dialing out to customer sites; accessing a system for maintaining video conference schedules, joining callers using Bandwidth on Demand Interoperability Group ("BONDING") calls or International Telecommunication Union-Telecommunication Standardization Sector ("ITU-T") standard H.320 Multi-rate Bearer Service (MRBS) Integrated Services Digital Network ("ISDN") calls into a video conference or video call; monitoring, viewing and recording any video conference or video call; playing back video conferences or video calls recorded earlier; and offering assistance to or responding to inquiries from video conference callers during video conferences or video calls.
[2411] The system hardware is comprised of a Video Operator Terminal 40001, a Call Server 40002, a multimedia hub ("MM Hub") 40003, wide area network hubs ("WAN Hubs") 40004, a multi-point conferencing unit ("MCU") 40005, a BONDING Server 40006, a Client Terminal 40007, and a switching network ("MCI") 40008.
[2412] In one embodiment, the Video Operator Terminal 40001 is a Pentium-based personal computer with a processing speed of 90 MHz or greater, 32 MB RAM, and a hard disk drive with at least 1.0 GB storage space. The operating system in this embodiment is Microsoft's Windows 95. Special features include Incite Multimedia Communications Program ("MCP") software, an H.320 video coder/decoder ("codec") card for audio and video compression (e.g. Zydacron's Z240 codec), and an isochronous Ethernet ("isoEthernet") network interface card. Incite's MCP manages the isoEthernet network interface card to create the equivalent of 96 ISDN B-channels in isochronous channels for transmission of video signals.
[2413] The Call Server 40002 in this embodiment is a Pentium-based personal computer with a processing speed of 90 MHz or greater, 32 MB RAM, and a hard disk drive with at least 1.0 GB storage space. The operating system is Microsoft's Windows NT Server. Special features include the Incite Call Server services and an Ethernet network interface card.
[2414] Different embodiments of the system accommodate any model of MM Hub 40003 and any model of WAN Hub 40004. In one embodiment, the MM Hub 40003 is the Incite Multimedia Hub, and the WAN Hub is the Incite WAN Hub. The MM Hub 40003 is a local area network ("LAN") hub that connects, via numerous ports supporting isoEthernet interfaces each with a bandwidth consisting of 96 full-duplex B-channels, to personal computers such as the Video Operator Terminal 40001 and the BONDING Server 40006, to WAN Hubs 40004, or to other cascaded MM Hubs. In addition, the MM Hub 40003 can accept up to ten Mbps of Ethernet data via an Ethernet interface such as the one from the Call Server 40002. The WAN Hub 40004 acts as an interface between an MM Hub 40003 and a public or private switched network such as MCI 40008, enabling video conferencing to extend beyond the WAN or LAN containing the MM Hub 40003 and WAN Hub 40004.
[2415] Different embodiments of the system also accommodate various manufacturers' MCU 40005 devices. The function of an MCU 40005 is to allow video conference callers using a variety of different devices, possibly communicating over different circuit-based digital networks, to communicate with one another in a single video conference. For example, one embodiment employs VideoServer's Multimedia Conference Server ("MCS"), which mixes audio to allow any one video conference caller to hear the complete video conference discussion and processes video to allow each video conference caller to see all other callers simultaneously.
[2416] In one embodiment, the BONDING Server 40006 is a Pentium-based personal computer with a processing speed of 90 MHz or greater, 32 MB RAM, and a hard disk drive with at least 1.0 GB storage space. The operating system in this embodiment is Microsoft's Windows 95. Special features include Incite BONDING Server software, a Digital Signal Processor ("DSP") card (such as Texas Instrument's "TMS320C80" DSP), and an isoEthernet network interface card. Where a Client Terminal 40007 makes BONDING or Aggregated video calls, the BONDING Server 40006 converts the calls to multi-rate ISDN calls used within the video operator platform.
[2417] In a preferred embodiment, the Client Terminal a Pentium—based personal computer with a processing speed of 90 MHz or greater, 32 MB RAM, and a hard disk drive with at least 1.0 GB storage space. The operating system is Microsoft's Windows 95 in this embodiment, and the Client Terminal 40007 is equipped with audio and video equipment making it compatible with ITU- T standard H.320.
[2418] In this embodiment, the switching network is an integrated services digital network ("ISDN") provided by MCI 40008.
[2419] The Video Operator Terminal 40001 is connected to the MM Hub 40003 via an isoEthernet interface with a bandwidth of 96 full-duplex B-channels, which allows each video operator to manage up to eight video conferencing clients, each client employing a Client Terminal 40007. The MM Hub 40003 is connected to WAN Hubs 40004 via similar isoEthernet local area network ("LAN") connections. One WAN Hub 40004 connects through MCI 40008 to an MCU 40005 via multi-rate ISDN interfaces. Another WAN Hub 40004 connects to MCI 40008 via a multi-rate ISDN interface, and MCI connects to each Client Terminal 40007 via a BONDING or multi-rate ISDN interface. In a three-way connection, the MCU 40005, the Call Server 40002 and the MM Hub 40003 are connected to one another through an Ethernet wide area network ("WAN") 40009. The MM Hub 40003 is also connected to a BONDING Server 40006 via an isoEthernet interface with a bandwidth of 248 B-channels in full "iso" mode.
[2420] B. Video Operator Console
[2421]FIG. 97 shows one embodiment of the system for enabling a video operator to manage video conference calls, which includes a Video Operator Console system 40101 and external systems and interfaces 40108 through 40117.
[2422] The Video Operator Console system 40101 is comprised of a Graphical User Interface ("GUI") 40102, a Software System 40103 and a Media Control system 40107. The GUI 40102 interacts with both the Software System 40103 and the Media Control system 40107 to allow a video operator to perform all functions of the video operator invention from the Video Operator Terminal [40001 FIG. 96] using the Video Operator Console system 40101.
[2423] The Software System 40103 implements the following systems: a Scheduling system 40104 which manages the video operator's schedule; a Recording and Playback system 40105 which records the audio and video input from any call and plays back audio and video input through any call, and a Call System Interface 40106 which acts as an application program interface with the Incite MCP application to manage individual calls by performing switching functions such as dial and hold.
[2424] The Scheduling system 40104 is connected via an Open Database Connectivity ("ODBC") interface 40108 to a Video Operator Shared Database 40111, which is in turn connected via an interface between VOSD and VRS 40114 to a Videoconference Reservation System ("VRS") 40115. The VRS 40115 submits video conference schedules, conference definitions and site definitions to the Video Operator Shared Database 40111 via the interface 40114 either on a regular basis or on demand by a database agent system within the Video Operator Shared Database 40111. The Video Operator Shared Database 40111, residing in a different computer from that containing the Video Operator Console 40101 in a preferred embodiment, stores all conference and site information such that each Video Operator Console 40101 can retrieve the necessary conference and site configurations for any video conference call. In an alternative embodiment of the external systems associated with the internal Scheduling system 40104, the Video Operator Shared Database 40111 and VRS 40115 may be merged into a single system.
[2425] The Recording and Playback system 40105 communicates via a Dynamic Data Exchange ("DDE"), Object Linking and Embedding ("OLE") or Dynamic Link Library ("DLL") interface 40109 with a Video Operator Storage and Playback system 40112 located locally in the Video Operator Terminal [40007 FIG. 96]. The Video Operator Storage and Playback system is comprised of a uni-directional recording device 40116 conforming to ITU-T standard H.320 and a uni-directional playback device 40117 conforming to ITU-T standard H.320. Conference calls are recorded by transmitting the digitized audio and video signals from the Video Operator Console 40101 to the H.320 recorder 40116. Conference calls are played back by retrieving a previously recorded conference call from disk storage and transmitting the audio and video signals from the H.320 playback device 40117 to the Video Operator Console.
[2426] The Call System Interface system 40106 communicates via a DDE interface 40110 with the Incite MCP application 40113 to manage switching functions such as dial, hold, etc.
[2427] The Media Control system 40107 allows the GUI 40102 to communicate directly with external components to manage the GUI 40102 presentation of audio and video. In the embodiment shown in FIG. 97, the Media Control system 40107 communicates via a DDE interface 40110 with the Incite MCP application 40113. The Incite MCP application 40113 provides all necessary call setup features and multimedia features such as video window placement and audio control through the DDE interface 40110 to the internal Media Control system 40107, and on to the GUI 40102.
[2428]FIG. 98 shows a second embodiment of the system for enabling a video operator to manage video conference calls, which includes a Video Operator Console system 40101 and external systems and interfaces 40108 through 40117 and 40203 through 40216. In this embodiment, however, the Software System 40103 is compatible with not only VideoServer's "MCS" 40215 MCU, but also other manufacturers' MCU applications. Thus the internal software system MCU control 40201, the external software system MCU Control System 40208, the MCUs themselves 40214 and 40215, and the interfaces between them 40206, 40210 and 40211, appear in FIG. 98. In addition, because not only the Incite MCP 40113 application but also "Other programs with call control interfaces" 40216 may provide necessary call setup and multimedia features in this embodiment, the external Call Control System 40209 is necessary, as are the intervening DDE, OLE or DLL interfaces 40207, 40212 and 40213. This embodiment also includes a Video Store and Forward system 40204 and its DDE, OLE or DLL interface 40203. Finally, the second embodiment adds the internal software system Call Monitor 40202.
[2429] As in the first embodiment, the Video Operator Console system 40101 is comprised of a GUI 40102 and a Software System 40103. However, in addition to the Scheduling system 40104, the Recording and Playback system 40105 and the Call System Interface 40106, the software system in the second embodiment includes the MCU control 40201 and the Call Monitor 40202.
[2430] The Scheduling system 40104 and associated external systems 40108, 40111, 40114 and 40115 are identical to the those in the first embodiment, pictured in FIG. 97 and described above.
[2431] The internal MCU control 40201 communicates via a DDE, OLE or DLL interface 40206 with the external MCU Control System 40208 to manage resources and features specific to various different MCU systems. The MCU Control System 40208 communicates either via a ConferenceTalk interface 40211 with the VideoServer MCS 40215 or via another vendor-specific interface 40210 with some Other MCU vendors' MCU 40214.
[2432] The Recording and Playback system 40105 communicates via DDE, OLE or DLL interfaces 40109, 40203 with both the Storage and Retrieval system 40205 and the Video Store and Forward system 40204. The Storage and Retrieval system 40205 and Video Store and Forward system 40204 communicate via another DDE, OLE or DLL interface 40207 with the Call Control System 40209. The Call Control System 40209 communicates via another DDE, OLE or DLL interface 40212 with a uni-directional H.320 recorder 40116 and a uni-directional H.320 playback device 40117. Conference calls recorded by transmitting the digitized audio and video signals from the Video Operator Console 40101 through the Storage and Retrieval system 40205 and Call Control System 40209 to the H.320 recorder 40116. Conference calls are played back by retrieving a previously recorded conference call from disk storage and transmitting the audio and video signals from the H.320 playback device 40117 through the Call Control System 40209 and Storage and Retrieval system 40205 to the Video Operator Console 40101. The Video Store and Forward system 40204 operates in a manner similar to the Storage and Retrieval system 40205, communicating between the Recording and Playback system 40105 and the Call Control System 40209.
[2433] The call monitor 40202 monitors the state of calls and connections by regularly polling the Call System Interface 40106 within the Video Operator Console Software System 40103. The Call System Interface 40106 communicates via a DDE, OLE or DLL interface 40207 with the Call Control System 40209 to manage call data, including switching functions such as dial, hold, etc., translating between the Video Operator Console 40101 internal data structures and the Call Control System 40209 data. The Call Control System, in turn, manages either the Incite MCP 40113 or Other programs with call control interfaces 40216.
[2434] The Media Control system 40107 communicates via a DDE, OLE or DLL interface with the Call Control System 40209, which communicates via a DDE interface 40110 with the Incite MCP application 40113 or with Other programs with call control interfaces 40216. The Incite MCP application 40113 provides all necessary call setup features and multimedia features such as video window placement and audio control either directly through a DDE interface 40110 to the internal Media Control system 40102 or via the Call Control System 40209. If Other programs with call control interfaces 40216 are used to provide call setup and multimedia features, they communicated with the Media Control system 40107 via the Call Control System 40209.
[2435] C. Video Conference Call Flow
[2436]FIG. 99 shows how a video conference call initiated by the video operator is connected through the system pictured in FIG. 96. In the first step, illustrated by call flow path 40301, the video operator initiates a call from the Video Operator Terminal 40001 through the MM Hub 40003 to the BONDING Server 40006, where the BONDING Server 40006 converts the call to a BONDING call. In the second step, illustrated by call flow path 40302, the BONDING Server 40006 transmits the BONDING call through the MM Hub 40003 once again, through a WAN Hub 40004, through MCI 40008, and to the Client Terminal 40007. This step is repeated for each Client Terminal 40007 that will participate in the video conference. In the third step, illustrated by call flow path 40303, the video operator initiates a call from the Video Operator Terminal 40001 through the MM Hub 40003, through a WAN Hub 40004, through MCI 40008, and to the MCU 40005. In the fourth step, illustrated by call flow path 40304, the video operator uses the Video Operator Terminal 40001 to bridge the connections to the Client Terminal 40007 and MCU 40005. Each time the video operator calls a conference call client at its Client Terminal 40007, the MCU's ANI for the particular conference site is passed in the Calling Party Field to identify each client participating in the conference call with the correct conference site. When the MCU is called, the clients' ANI are passed. The MCU can then identify the correct conference site for each call.
[2437] In an alternate embodiment, the client initiates a BONDING call from the Client Terminal 40007 through MCI 40005, through a WAN Hub 40004, through the MM Hub 40003, through the BONDING Server 40006, and through the MM Hub 40003 once again to the Video Operator Terminal 40001. The video operator then places a call to the MCU as illustrated in call flow path 40303 and finally bridges the two calls as illustrated in call flow path 40304. To determine the correct conference site for the client-initiated call, the initiating client's ANI is passed to the MCU when the connection is made by the video operator.
[2438] While a conference call is in progress, the video operator monitors each of the calls from the Video Operator Terminal 40001. Functions of the video operator include monitoring which calls remain connected, reconnecting disconnected calls, adding new clients to the conference, or joining the conference to inform the clients regarding conference status.
[2439] All calls are disconnected to end a conference, and the video operator shared database [40214 in FIG. 98] reflects an updated conference schedule.
[2440] D. Video Operator Software System
[2441] 1. Class Hierarchy
[2442]FIG. 100 shows the class hierarchy for video operator software system classes. In one embodiment using the Visual C++ programming language, the VOObject 40401 class is extended from the Visual C++ base class CObject. VOObject 40401 is a Superclass to all classes of objects in the internal software system for the video operator console system, such that all objects in the internal software system inherit attributes from VOObject 40401.
[2443] VOOperator 40402 is an assembly class associated with one VOSchedule 40403 Part-1 Class object and one VOUserPreferences 40404 Part-2 Class object, such that exactly one VOSchedule 40403 object and exactly one VOUserPreferences 40404 object are associated with each VOOperator 40402 object. VOSchedule 40403, in turn, is an Assembly Class associated with zero or more VOSchedulable 40405 Part-1 Class objects, such that any number of VOSchedulable 40405 objects may be associated with each VOSchedule 40403 object.
[2444] VOSchedulable 40405 is a Superclass to the VOConference 40406 Subclass-i and the VOPlaybackSession 40407 Subclass-2, such that the VOConference 40406 object and the VOPlaybackSession 40407 object inherit attributes from the VOSchedulable 40405 object. VOConference 40406 is an Assembly Class associated with two or more VOConnection 40412 Part-1 Class objects and zero or one VOPlaybackCall 40415 Part-2 Class objects, such that at least two VOConnection 40412 objects and possibly one VOPlaybackCall 40415 object are associated with each VOConference 40406 object. VOPlaybackSession 40407 is an Assembly Class associated with one VOPlaybackCall 40415 Part-1 Class object, such that exactly one VOPlaybackCall 40415 object is associated with each VOPlaybackSession 40407 object.
[2445] VOCallObjMgr 40408 is an Assembly Class for zero or more VOCall 40410 Part-1 Class objects, such that any number of VOCall 40410 objects may be associated with each VOCal10bjMgr 40408 object. Similarly, VOConnObjMgr 40409 is an Assembly Class for zero or more VOConnection 40412 Part-1 Class objects, such that any number of VOConnection 40412 objects may be associated with each VOConnObjMgr 40409 object. VOConnection 40412 is an Assembly class for two VOCall 40410 Part-1 Class objects, such that exactly two VOCall 40410 objects are associated with each VOConnection 40412 object. VOCall 40410 is a Superclass to the VOPlaybackCall 40415 Subclass-1, such that VOPlaybackCall 40415 objects inherit attributes from the VOCall 40410 object. VOCall 40410 is also an Assembly Class associated with two VOSite 40413 Part-1 Class objects, such that exactly two VOSite 40413 objects are associated with each VOCall 40410 object. Finally, the VOCall 40410 class object uses the VORecorder 40411 class object.
[2446] VOSite 40413 is a Superclass to the VOMcuPortSite 40417 Subclass-1, the VOParticipantSite 40418 Subclass-2, and the VOOperatorSite 40419 Subclass-3, such that VOMcuPortSite 40417 objects, VOParticipantSite 40418 objects and VOOperatorSite 40419 objects inherit attributes from the VOSite 40413 object.
[2447] VOPlaybackCall 40415 is an Assembly Class associated with one VOMovie 40416, such that exactly one VOMovie 40416 object is associated with each VOPlaybackCall 40415 object. The VOPlaybackCall 40415 class object also uses the VOPlayer 40414 class object.
[2448] VOMessage 40420 object has no associations other than inheriting the attributes of VOObject 40401, the Superclass to all objects in the internal software system.
[2449] 2. Class and Object details
[2450] a) VOObject
[2451] All Internal Software System classes will inherit from the following base class. This base class is extended from the Visual C++ base class CObject.
[2453] (3) Methods
[2454] (ii) Description
[2455] Use this function to create error, warning, debug, logging and notification messages. It will create a VOMessage object, which will then perform the appropriate actions as specified by the delivery flags.
[2456] (b) GetErrorString
[2457] virtual CString GetErrorString (int errorcode);
[2458] Return Value: returns a CString object having the error string corresponding to the error code passed. errorcode parameter: the error code for which you want the error string. Error strings are stored as resources.
[2459] This function is called to get a textual description corresponding to an error code.
[2460] b) Core Classes
[2461] (1) Class List
[2462] Site
[2463] Participant Site
[2464] MCU Port Site
[2465] Video Operator Site
[2466] Call
[2467] Playback Call
[2468] Movie
[2469] Call Object Manager
[2470] Connection
[2471] Connection Object Manager
[2472] Message
[2473] Video Operator
[2474] (2) Class Descriptions
[2475] (a) Site
[2476] This is a base class from which classes such as the Participant Site and MCU Port Site classes can be derived from. It's main purpose is to function as a data structure containing pertinent information about who or what is taking part in a Call.
[2478] (b) Participant Site
[2479] Inherits from VOSite base class.
[2480] All customers or conference participants will have their information stored in the VO shared database.
[2482] (c) MCUPort Site
[2483] Inherits from VOSite base class.
[2484] All conferences take place on an MCU. Each Participant Site needs to connect with a logical "port" on an MCU.
[2486] (d) Video Operator Site
[2487] Inherits from VOSite base class.
[2488] All calls will have the Video Operator Site as one of the sites in a point-to-point call. This structure contains the real ANI of the video operator.
[2490] (e) Call
[2491] A Call is defined as a full duplex H.320 stream between two sites. In all Calls, the Video Operator Site will be one of the sites. A Joined pair of Calls is called a Connection.
[2493] (iii) Methods
[2494] Disconnection(); is called when the other end of the line hangs up or the line goes dead. The member variable m_expectHangup should be FALSE. Otherwise, the Call Object Manager's Hangup () operation would have been called.
[2495] Reset(); resets the call state to an inactive state
[2496] RecordingStart(); starts recording the H.320 input pipe of the Call.
[2497] RecordingStop(); stops the recording of the Call.
[2498] setState(callOperation e operation); operation parameter: indicates an operation that has been performed which will result in a change of state
[2499] Operations that affect the state of the Call should call the setState function after the operation has been performed. This function will change the state of the Call by referencing the current state and the operation in the state-transition table. A VOMessage object will be created, with a type of STATUS_UPDATE and sent to the application queue. The GUI and any other component that reads the application queue will therefore be informed of the status update.
[2500] (f) Playback Call
[2501] Inherits from VOCall base class.
[2502] In this special case of a Call, the Video Operator audio and video output is replaced with the H.320 stream from the playback of a movie by the Video Operator Storage and Playback external system component.
[2503] (i) Aftributes
[2504] (ii) Methods
[2505] PlaybackStart; starts playback
[2506] Playbackstop stops playback
[2507] (g) Movie
[2508] A Movie is a recording of an H.320 Call. For Phase 1, the Video Operator Storage and Playback System manages files and H.320 data streams for recording and playback of movies, as well as storage and retrieval.
[2510] (h) Call Object Mlanager
[2511] By having a Call Object Manager to perform the construction and destruction of Call objects, a list of all calls on the video operator's machine can be maintained. This includes calls that are not part of any Conference or Playback Sessions, including incoming calls and general purpose dial-out calls. Operations that affect a Call but do not create or destroy it can be performed by the Call object itself.
[2512] Classes
[2513] (ii) Methods
[2514] Dial();
[2515] Dial(VOCall*pcalling);
[2516] pCalling parameter: If not NULL, this pointer will be used for the Call object. This is necessary when creating or re-using a Call object that is in an inactive or disconnected state.
[2517] Dial performs dial out. The number(s) to Dial are in the m_pSite Call member structure.
[2518] Answer();
[2519] Answer (VOCall*pIncoming);
[2520] pIncoming parameter: If not NULL, this pointer will be used for the Call object. This is necessary when creating or re-using a Call object that is in an inactive or disconnected state.
[2521] Answer answers an incoming call.
[2522] Hangup(VOCall
[2523] pCall);
[2524] pCall parameter: pointer to the call
[2525] Hangup hangs up the call pointed to by pCall
[2526] Hold(VOCall* pCall);
[2527] pcall parameter: pointer to the call
[2528] Hold puts the call pointed to on hold.
[2529] VOCall* CallCreate();
[2530] VOCall* CallCreate creates a Call object.
[2531] VOPlaybackCall* PlaybackCallCreate();
[2532] VOPlaybackCall* PlaybackCallCreate() creates a Playback Call object.
[2533] VOCall* GetCallPtr(ID_t idCall);
[2534] idCall parameter: call ID
[2535] VOCall* GetCallPtr gets the pointer to the call object identified by idCall
[2536] (i) Connection
[2537] A Connection is defined as a pair of Call objects that maintain a Join state, and each Call has the Video Operator Site as a common point for the Join to be implemented.
[2538] (i) Data Types
[2539] enum StateConnection_e { ERROR, UNJOINED, JOINED, BROKEN, lastConnectionStates };
[2540] enum ConnectionOperation_e { ERROR, JOIN, UNJOIN, BREAK, RESET, lastConnectionOperations };
[2541] (ii) Attributes
[2542] (iii) Methods
[2543] Join ();joins tlhe Participant and MCU Port Calls.
[2544] Unjoin ();unjoins the Participant and MCU Port Calls.
[2545] SetParticipantCall (VOCall* participantcall);
[2546] participantcall parameter: pointer to a Call object
[2547] SetParticipantCall sets the Call to be the Participant Call. This is useful when managing unknown incoming calls or for last minute participant substitution.
[2548] SetMCUPortCall(VOCall* mcuPortCall);
[2549] mcuPortCall parameter: pointer to a Call
[2550] SetMCUrPortCall sets the Call to be the MCU Port Call. This is useful when managing unknown incoming calls or for last minute call site substitution.
[2551] DoParticipantCall(); calls the Participant Site and sets it as the Participant Call.
[2552] DoMCUPortCall(); calls the MCU Port Site and sets it as the MCU Port Call.
[2553] setState ( ConnectionOperation_e operation);
[2554] operation parameter: the operation that has been performed which will result in a change of state.
[2555] Operations that affect the state of the Connection should call the setState function Eifter the operation has been performed. This function will change the state of the Connection by referencing the current state and the operation in the state-transition table. A VOMessage object will be created, with a type of STATUS_UPDATE and sent to the application queue. The GUI and any other component that reads the application queue will therefore be informed of the status update.
[2556] protected Break(); is called when a Joined Connection becomes Un- joined. If the member variable m_expectBreak is FALSE then one of the Calls must have unexpectedly been disconnected. Otherwise, the Connection's Unjoin() operation would have been called.
[2557] protected Reset(); resets the state of the Connection to UNJOINED.
[2558] (j) Connection Object Manager
[2559] Similarly with the Call Object Manager, a list of all Connections in operation on the video operator's machine must be maintained. All operations that result in the creation or deletion of a Connection must use the Connection Object Manager.
[2560] (i) Aftributes
[2561] (ii) Methods
[2562] VOConnection* Create();
[2563] Return Value: pointer to Connection object
[2564] VOConnection* Create creates a new Connection object and adds it to the list.
[2565] Remove (VOConnection* oldconnection();
[2566] oldConnection parameter: connection object to be removed
[2567] Return Value: returns TRUE if operation successful.
[2568] Remove deletes a Connection object and removes it from the list.
[2569] VOConnection* GetconnectionPtr( ID_t idConnection();
[2570] Return Value: a pointer to the connection object
[2571] idConnection parameter: ID of the Connection
[2572] VOConnection* GetConnectionPtr returns the pointer to a Connection object identified by its ID.
[2573] (k) Message
[2574] All one-way communication from the Internal System Software to the rest of the Video Operator application, i.e. the Graphical User Interface, is sent as messages that get placed on the Application Queue. The function to create and post a Message is in the base class VOObject, which all Internal System Software classes inherit from. All run-time errors or debugging information is put into a Message object, and posted to the application queue so that an appropriate object will process it according to its type and severity. Therefore all class functions that do not return a specific type will post a Message if something goes wrong, e.g. out of memory, or debugging information to be displayed by the GUI or logged to a file.
[2576] (ii) Attributes
[2577] (iii) Methods
[2578] Post(); posts a message to the application message queue
[2579] private static AppendLog();
[2580] Return Value: returns TRUE if the operation is successful.
[2581] This method is called by VOObject: PostMessage() when the flag for DELIVER_LOG_FILE is set.
[2582] (l) Video Operator
[2583] Generally there will be only one Video Operator per machine. Each Video Operator has a Schedule, and a list of customer Participant Sites to manage. The Call Object Manager and Connection Object Manager are also part of the Video Operator.
[2584] (i) Attributes
[2585] (ii) Methods
[2586] protected ScheduleStarto(); initiates the schedule for the video operator.
[2587] protected CallobjMgrStart();initiates the call object manager.
[2588] protected ConnectionobjMgrStart();initiates the connection object manager.
[2589] protected Call Systemlnterf acestart();initiates the Call System Interface.
[2590] (m) User Preferences
[2591] The Video Operator Console application will have a set of default application preferences which may be modified and saved. The values of these variables are taken from the following sources, in order of increasing preference: hard-coded default values, saved VO. INI file, command-line invocation arguments, GUI entry and run-time modifications saved to VO. INI file.
[2592] (i) Attributes
[2593] (ii) Methods
[2594] SavePref s(); saves all values to VO. INI.
[2595] LoadPrefs(); loads all values from VO. INI.
[2596] (n) MCU
[2597] All MCU Port Sites correspond to a particular MCU. This class is used for MCU Port Site storage only. For Phase 2, MCU specific operations and interfaces would be implemented here.
[2598] (i) Attributes
[2599] (ii) Methods
[2600] VOMCUPortSite* GetPortPtr( ID_t idport);
[2601] Return Value: a pointer to the MCU Port Site object.
[2602] IdPort pararneter: ID of the MCU Port Site
[2603] VOMCUPortSite* GetPortPtr returns the pointer to a MCU Port Site object identified by its ID.
[2604] VOMCUPortSite* CreatePort();
[2605] Return Value: a pointer to a new MCU Port Site object
[2606] VOMCUPortSite* CreatePort returns the pointer to a newly created MCU Port Site object identified by its ID.
[2607] (3) State Variable Transition Diagrams for Core Classes FIG. 101 shows a state transition diagram illustrating the state changes that may occur in the VOCall object's m_state variable ("state variable"). The state variable starts 40501 in Inactive 40502 state.
[2608] If the VOCall object receives a Dial 40503 input while in Inactive 40502 state, the state variable changes to Dialing 40504 state. In the Dialing 40504 state, the state variable changes to Inactive 40502 state upon receiving a Busy 40505 input or to Active 40507 state upon receiving an Answer 40506 input. In the Active 40507 state, the state variable changes to Held 40510 state upon receiving a Hold 40509 input, to Disconnected 40515 state upon receiving a Disconnection 40514 input, or to Inactive 40502 state upon receiving a Hangup 40508 input. In the Held 40510 state, the state variable changes to Active 40507 state upon receiving a Pickup 40511 input, to Disconnected 40515 state upon receiving a Disconnection 40513 input, or to Inactive 40502 state upon receiving a Hangup 40512 input. In the Disconnected 40515 state, the state variable changes to Inactive 40502 state upon receiving a Reset 40516 input.
[2609] If the VOCall object receives an Incoming Call 40517 input while in Inactive 40502 state, the state variable changes to Incoming 40518 state. In the Incoming 40518 state, the state variable changes to Inactive 40502 state upon receiving a Reject 40520 input or to Active 40507 state upon receiving an Answer 40519 input.
[2610]FIG. 102 shows a state transition diagram illustrating the state changes that may occur in the VOConnection object's m_state variable ("state variable"). The state variable starts 40601 in Unjoined 40602 state. In the Unjoined 40602 state, the state variable changes to Joined 40604 state upon receiving a Join 40603 input. In the Joined 40604 state, the state variable changes to Unjoined 40602 state upon receiving an Unjoin 40605 input or to Broken 40607 state upon receiving a Break 40606 input. In the Broken 40607 state, the state variable changes to Joined 40604 state upon receiving a Join 40608 input.
[2611] c) Scheduling System Classes
[2612] (1) Class List
[2613] Playback Session
[2614] Conference
[2615] Schedule
[2616] Schedulable
[2617] (2) Class Descriptions
[2618] (a) Playback Session
[2619] Like Conferences, Playback Sessions need to be scheduled. A Call is made with a Participant Site and the Video Operator Site. The Video Operator Storage and Playback external component system will playback a scheduled and pre-selected movie, replacing the AV output to the Participant Site. No MCU is used for a Playback Session, and only one Participant Site is involved in one embodiment.
[2620] (i) Data Types
[2621] enum StatePlaybackSession_e { ERROR, INACTIVE, SETUP, ACTIVE, ENDING, FINISHED, lastPBSessionStates };
[2622] enum playbackSessionoperation_e { ERROR, PREPARE, START, CLOSE, FINISH, lastPBSessionoperations};
[2623] (ii) Attributes
[2624] (iii) Methods
[2625] public boolean Setup();
[2626] Return Value: returns TRUE if operation successful.
[2627] public boolean Setup() sets up the Playback Call by calling the
[2628] Participant Site and initialize a VOPlayer object. This function may be called by the Scheduler.
[2629] Public boolean Start();
[2630] Return Value: returns TRUE if operation successful.
[2631] Public boolean Start starts the Player to play to the Playback Call. This function may be called by the Scheduler.
[2632] Public boolean Close();
[2633] Return Value: returns TRUE if operation successful.
[2634] Public boolean Close sends messages to the Video Operator and maybe the Participant that the Playback Session will end soon.
[2635] Public boolean Finish();
[2636] Return Value: returns TRUE if operation successful.
[2637] Public boolean Finish stops the Player and Hangup the Playback Call. This function may be called by the Scheduler.
[2638] public StatePlaybackSession_e StateGet();
[2639] Return Value: returns the playback session's state.
[2640] Use the public StatePlaybackSession_e StateGet; function to find out the state of the Playback Session.
[2641] protected boolean StateSet(playbackSessionOperation e operation();
[2642] Return Value: returns TRUE if operation successful.
[2643] operation parameter: the operation that has been performed which will result in a change of state
[2644] Operations that affect the state of the Playback Session should call the protected boolean StateSet function after the operation has been performed. This function will change the state of the Playback Session by referencing the current state and the operation in the state-transition table. A VOMessage object will be created, with a type of STATUS_UPDATE and sent to the application queue. The GUI and any other component that reads the application queue will therefore be informed of the status update.
[2645] (b) Conference
[2646] The main function of the Video Operator is to manage conferences. The scheduler system creates the Conference objects, which in turn create a list of Connections (or Participant-MCU Port Site Call pairs). In the special case of a movie being played back to a conference, an extra call is made to an MCU Port and the movie is played back to the MCU in a similar way as a Playback Session. This of course requires an extra MCU Port site to be available, and must be scheduled before the start of the conference.
[2648] (ii) Attributes
[2649] (iii) Methods
[2650] public boolean Setup();
[2651] Return Value: returns TRUE if operation successful.
[2652] public boolean Setup sets up each Connection in the connection list (and the Playback Call if required) by calling each Participant Site and MCU Port Site as appropriate, and perform the Join operations to create the Connections. This function may be called by the Scheduler.
[2653] Public boolean Start();
[2654] Return Value: returns TRUE if operation successful.
[2655] Public boolean Start starts the Conference. This function may be called by the Scheduler.
[2656] Public boolean End();
[2657] Return Value: returns TRUE if operation successful.
[2658] Public boolean End starts tea-rng down the Connections in the conference or issues warnings that the conference will end soon. This function may be called by the Scheduler.
[2659] Public boolean Finish();
[2660] Return Value: returns TRUE if operation successful.
[2661] Public boolean Finish stops the Conference and hangs up all Calls in the Conference. This function may be called by the Scheduler. public StateConference_e StateGet();
[2662] Return Value: returns the Conference state
[2663] Use the public StateConference_e StateGet function to find out the state of the Conference.
[2664] protected boolean StateSet(conferenceOperation_e operation();
[2665] Return Value: returns TRUE if operation successful. operation parameter: the operation that has been performed which will result in a change of state
[2666] Operations that affect the state of the Conference should call the protected boolean StateSet function after the operation has been performed. This function will change the state of the Conference by referencing the current state and the operation in the state-transition table. A VoMessage object will be created, with a type of STATUS_UPDATE and sent to the application queue. The GUI and any other component that reads the application queue will therefore be informed of the status update.
[2667] (c) Schedule
[2668] The Scheduling System maintains a list of Conferences and Playback Sessions. Each Conference and Playback Session is created at a particular time interval before its starting time. The Schedule in memory and the Schedule stored in the Video Operator Shared Database for the current Video Operator should always be synchronized.
[2669] (i) Attributes
[2670] (ii) Methods
[2671] SynchWithDb(); synchronizes with the VO shared database for the schedule.
[2672] AddSchedulable(VOSchedulable* pSchedulable);
[2673] pschedulable parameter: pointer to schedulable object to be added to list
[2674] AddSchedulable adds a Schedulable object to the list
[2675] DeleteSchedulable(ID_t aschedulable);
[2676] aSchedulable parameter: schedulable object to be removed from list
[2677] DeleteSchedulable deletes a Schedulable object and remove from list.
[2678] (d) Schedulable
[2679] Items or Objects that are schedulable in Phase 1 are Conferences and Playback Sessions. This class allows us to create a schedule for any type of event.
[2680] (i) Attributes
[2681] (ii) Methods
[2682] public SetAlarm(Ctime time, LPTIMECALLBACK func );
[2683] time parameter: time for alarm to be triggered func parameter: pointer to callback function when alarm is triggered Return Value: returns TRUE if operation successful.
[2684] public SetAlarm sets an alarm to be triggered at a specified time. When the alarm is triggered, the callback function will be called. This is useful for time dependant events such as 15 minutes before a Conference starts, 5 minutes before a Conference ends, and 30 minutes after a Conference has finished.
[2685] public KillAlarm();
[2686] Return Value: returns TRUE if operation successful.
[2687] public KillAlarm kills the last alarm that has been set by SetAlarm(). This would be used in the case of aborting a Conference, etc.
[2688] (3) State Variable Transition Diagram for Schedule System Classes
[2689]FIG. 103 shows a state transition diagram illustrating the state changes that may occur in the VOConference object's m_state variable ("state variable"). The state variable starts 40701 in Inactive 40702 state. In the Inactive 40702 state, the state variable changes to ConnectionSetup 40704 state upon receiving a "15 minutes before scheduled time" 40703 input. In the ConnectionSetup 40704 state, the state variable changes to Active 40706 state upon receiving a Start Conference 40705 input. In the Active 40706 state, the state variable remains in Active 40706 state upon receiving an Extend Conference 40707 input or changes to Ending 40707 state upon receiving a CloseConference (Proper Termination) 40708 input. In the Ending 40707 state, the state variable changes to Finished 40711 state upon receiving a Finish 40710 input.
[2690] d) Recording and Playback Classes
[2691] (1) Class List
[2692] Recorder
[2693] Player
[2694] (2) Class Details
[2695] (a) Recorder
[2696] A recorder communicates with whatever external components performs the actual movie creation and recording of the input pipe of a Call. This external component is known as the Video Operator Storage and Playback system.
[2697] (I) Data Types
[2698] enum StateRecorder_e { ERROR, IDLE, RECORDING, PAUSED, FINISHED, lastRecorderStates};
[2699] enum recorderoperation_e { ERROR, BEGIN, PAUSE, RESUME, STOP, lastRecorderOps }
[2700] (ii) Attributes
[2701] (iii) Methods
[2702] InitMovie();VOSP initializes a recording. This will tell the VOSP to prepare to record.
[2703] start();VOSP starts a recording.
[2704] stop(); VOSP stops a recording.
[2705] setState(recorderOperation_e operation();
[2706] operation parameter: the operation that has been performed which will result in a change of state.
[2707] Operations that affect the state of the Recorder should call the setState function after the operation has been performed. This function will change the state of the Recorder by referencing the current state and the operation in the state-transition table. A VOMessage object will be created, with a type of STATUS_UPDATE and sent to the application queue. The GUI and any other component that reads the application queue will therefore be informed of the status update.
[2708] (h) Player
[2709] A Player communicates with whatever external component performs the actual playback of a movie to the output pipe of a Call. For Phase 1, this external component is known as the Video Operator Storage and Playback system.
[2710] (i) Data Types
[2711] enum StatePlayer_e { ERROR, IDLE, PLAYING, PAUSED, FINISHED, nPlayerStates}; enum playeroperation_e { ERROR, BEGIN, PAUSE, RESUME, STOP, RESET, nPlayerOps}
[2712] (ii) Aftributes
[2713] (iii) Methods
[2714] public InitMovie();
[2715] Return Value: returns TRUE if operation successful.
[2716] public InitMovie VOSP initializes playback. This will tell the VOSP to prepare for playback.
[2717] public Start();
[2718] Return Value: returns TRUE if operation successful.
[2719] public Start VOSP starts playback.
[2720] public Stop();
[2721] Return Value: returns TRUE if operation successful.
[2722] public Stop VOSP stops playback.
[2723] setstate(playerOperation_e operation();
[2724] Return Value: returns TRUE if operation successful. operation parameter: the operation that has been performed which will result in a change of state.
[2725] Operations that affect the state of the Player should call the setstate function after the operation has been performed. This function will change the state of the Player by referencing the current state and the operation in the state-transition table. A VOMessage object will be created, with a type of STATUS_UPDATE and sent to the application queue. The GUI and any other component that reads the application queue will therefore be informed of the status update.
[2726] (3) State Transition Diagrams for Recording and Playback Classes
[2727]FIG. 104 shows a state transition diagram illustrating the state changes that may occur in the VORecorder object's m_state variable ("state variable"). The state variable starts 40801 in Idle 40802 state. In the Idle 40802 state, the state variable changes to Recording 40804 state upon receiving a Begin Recording 40803 input. In the Recording 40804 state, the state variable changes to Paused 40806 state upon receiving a Pause 40805 input or to Finished 40810 state upon receiving a Stop 40808 input. In the Paused 40806 state, the state variable changes to Recording 40804 state upon receiving a Resume 40807 input or to Finished 40810 state upon receiving a Stop 40809 input.
[2728]FIG. 105 shows a state transition diagram illustrating the state changes that may occur in the VOPlayer object's m_state variable ("state variable"). The state variable starts 40901 in Idle 40902 state. In the Idle 40902 state, the state variable changes to Playing 40904 state upon receiving a Begin Playing 40903 input. In the Playing 40904 state, the state variable changes to Paused 40906 state upon receiving a Pause 40905 input or to Finished 40910 state upon receiving a Stop 40908 input. In the Paused 40906 state, the state variable changes to Playing 40904 state upon receiving a Resume 40907 input or to Finished 40910 state upon receiving a Stop 40909 input. In the Finished 40910 state, the state variable changes to Playing 40904 state upon receiving a Replay 40911 input.
[2729] e) Call System Interface Class Description
[2730] The Call Control System will manage all calls that a Video Operator can manage. This includes incoming and outgoing H.320 call management and low level operations on a call, such as recording and playback. The Video Operator Application uses its Call System Interface to communicate with the Call Control System external component which manages all calls in a uniform way. This allows the video operator to manage calls that require different external programs, adding an extra codec to the machine, or even managing calls on a remote machine.
[2731] (1) Data Types
[2732] enum Bandwidth_e {MULTIRATE, BONDING, AGGREGATED, H0}
[2733] Q.931 UserInfo for a call using BONDING:
[2734] 0�00 0�01 0�07 0�44 0�79 0�00 0�00 0 1 7 447-9000
[2735] Bonded, 1 number, 7 digits long, 447-9000
[2736] Q.931 UserInfo for Aggregation:
[2738] Aggregated, 2 numbers, 7 digits long, 447-9000, 447-9001
[2739] (2) Attributes
[2740] (3) Methods
[2741] public Dial(Bandwidth_e calltype, CString destination();
[2742] public Dial(Bandwidth_e calltype, CString destination, CString origination();
[2743] Return Value: returns TRUE if operation successful. calltype parameter: specifies the type of call to make. destination parameter: specifies the destination number to be dialed. origination parameter: specifies an origination number to be used, instead of the real number of the operator's console.
[2744] public Dial dials out.
[2745] public Answer(ID_t call); call parameter: The Call ID of a Call waiting to be answered.
[2746] public Answer answers an incoming call.
[2747] public Hangup(ID_t call);
[2748] Return Value: returns TRUE if operation successful. call parameter: the Call ID of a Call to Hangup
[2749] public Hangup hangs up a call.
[2750] public Hold(ID_t call);
[2751] Return Value: returns TRUE if operation successful.
[2752] call parameter: the Call ID of a Call to Hold
[2753] public Hold puts the call on hold.
[2754] public Join(ID_t calll, ID_t call2);
[2755] Return Value: returns TRUE if operation successful.
[2756] calli parameter: the Call ID of a Call.
[2757] ca 112 parameter: the Call ID of a Call.
[2758] public Join joins two Calls.
[2759] (ID_t connection);
[2760] Return Value: returns TRUE if operation successful.
[2761] connection parameter: he ID of a Connection to Unjoin
[2762] public Unjoin un-joins the specified Connection.
[2763] public S_ateCall_e CallStatus(ID_t call);
[2764] Return Value: returns the state of a Call connection parameter: the ID of a Connection to Unjoin
[2765] public StateCall_e CallStatus reports status of the specified Call.
[2766] public StateConnection_e JoinStatus(ID_t connection();
[2767] Return Value: returns the state of a Connection connection parameter: the ID of a Connection to Unjoin
[2768] public StateConnection_e JoinStatus reports status of the specified Join.
[2769] protected LaunchMCP();
[2770] Return Value: returns TRUE if operation successful.
[2771] protected LaunchMCP launches Incite's MCP application.
[2772] E. Graphical User Interface Clcasses
[2773] 1. Class Hierarchy
[2774]FIG. 106 shows the class hierarchy for the video operator graphics user interface {"GUI"} classes. In general, the video conference operator will perform all the features of the video conferencing operator system described herein by interacting with the video operator console GUI ("console GUI"). The main components of the console GUI are the Main Console Window, Schedule and Connection List Windows, Conference and Connection Windows, a message area, audio and video controls, dialog boxes presenting timely information, and menu items for actions that may be performed infrequently. MCU operations and features will not be implemented in the video operator console GUI, so as to allow different embodiments of the video operator system employing different MCU model types. Vendor-specific MCU operations will be performed by the vendor's software that comes with the MCU application. In one embodiment employing VideoServer's MCS, the MCS Workstation Software can be used to implement features such as conference finish time extension, audio and video blocking, conference director control, etc. This software can run in parallel to the video operator GUI.
[2775] Described in object-oriented programming terms, the GUI has a main application object which creates and maintains all the windows and views within. The main window is the VOMainFrame 41009 which is created by the VOConsoleApp 41008. This mainframe window creates the VOScheduleWnd 41016, VOAlertWnd 41015, VOConferenceVw 41014 and the VOVideoWatchVw 41013. The VOScheduleWnd 41016 and the VOAlertWnd are dockable windows meaning that they can be attached to one of the sides of their parent window. In this case the parent window is the VOMainFrame 41009 window. The dockable windows can also be separated from the border by dragging them away. In such a situation they will act like normal tool windows.
[2776] The function of each class of object can be summarized as follows. VOConsoleApp 41008 is the main application class, and VOMainFrame 41009 is the main window which contains all the other windows. VOScheduleWnd 41016 is a window displaying the operator's schedule, and VOAlertWnd 41015 is a window where the error messages and alerts are displayed. VOChildFrame 41010 is a frame window for the multiple document interface ("MDI") windows. VOChildFrame 41010 will act like the mainframe window for each of the views. VOConferenceFrame 41018, derived from the VOChildFrame 41010, is the frame window for the conference view, and VOConferenceVw 41014 is the window displaying the conference information. VOConferenceDoc 41012 is the document class corresponding to the VOConferenceVw 41014. VOVideoWatchFrame 41017, derived from the VOChildFrame 41010, is the frame window for the Video Watch view, and VOVideoWatchVw 41013 is the window displaying the video stream and controls for making calls. VOVideoWatchDoc 41011 is the document class corresponding to the VideoWatch view.
[2777] In one embodiment using Visual C++ as the programming language, CWnd 41001 is a Superclass to the CMDIFrameWnd 41005 Subclass-i, CMDIChildWnd 41006 Subclass-2, CFromView 41007 Subclass-3, and CDialogBar 41002 Subclass-4, such that CMDIFrameWnd 41005 class objects, CMDIChildWnd 41006 class objects, CFromView 41007 class objects, and CDialogBar 41002 class objects inherit attributes from the CWnd 41001 class. CMDIFrameWnd 41005 is a Superclass to VOMainFrame 41009 Subclass-1; CMDIChildWnd 41006 is a Superclass to VOChildFrame 41010 Subclass-1; CFromView 41007 is a Superclass to both VOVideoWatchVw 41013 Subclass-1 and VOConferenceVw 41014 Subclass-2; and CDialogBar 41002 is a Superclass to both VOAlertWnd 41015 Subclass-1 and VOScheduleWnd 41016 Subclass-2. VOChildFrame 41010 is a Superclass to both VOVideoWatchFrame 41017 Subclass-1 and VOConferenceFrame 41018 Subclass-2. CWinApp 41003 is a Superclass to VOConsoleApp 41008 Subclass-1, and CDocument 41004 is a Superclass to both VOVideoWatchDoc 41011 Subclass-1 and VOConferenceDoc 41012 Subclass-2.
[2778] VOConsoleApp 41008 is an Assembly Class associated with one VOMainFrame 41009 Part-1 Class object, such that exactly one VOMainFrame 41009 object is associated with each VOConsoleApp 41008 object. VOMainFrame 41009 is an Assembly Class associated with one VOVideoWatchFrame 41017 Part-1 Class object, one VOConferenceFrame 41018 Part-2 Class object, one VOAlertWnd 41015 Part-3 Class object, and one VOScheduleWnd 41016 Part-4 Class object, such that exactly one VOVideoWatchFrame 41017 object, exactly one VOConferenceFrame 41018 object, exactly one VOAlertWnd 41015 object, and exactly one VOScheduleWnd 41016 object are associated with each VOMainFrame 41009 object.
[2779] VOVideoWatchFrame 41017 is an Assembly Class associated with one VOVideoWatchDoc 41011 Part-1 Class object and one VOVideoWatchVw 41013 Part-2 Class object, such that exactly one VOVideoWatchDoc 41011 object and exactly one VOVideoWatchVw 41013 object are associated with each VOVideoWatchFrame 41017 object. Each VOVideoWatchDoc 41011 object, extended from the CDocument 41004 class object as discussed above, uses a VOVideoWatchVw 41013 object, extended from the CFormView 41007 class object.
[2780] Similarly, VOConferenceFrame 41018 is an Assembly Class associated with one VOConferenceDoc 41012 Part-1 Class object and one VOConferenceVw 41014 Part-2 Class object, such that exactly one VOConferenceDoc 41012 object and exactly one VOConferenceVw 41014 object are associated with each VOConferenceFrame 41018 object. VOConferenceDoc 41012 uses VOConferenceVw 41014.
[2781] 2. Class and Object details
[2782] a) User Interface Classes
[2783] (1) Class List
[2784] VOConsoleApp The main application class
[2785] VOMainFrame The main window which has all the other windows
[2786] VOScheduleWnd Window displaying the operator's schedule
[2787] VOOutputWnd Window where the error messages and alerts are displayed
[2788] VOChildFrame Frame window for the MDI windows. This will act like the mainframe window for each of the views.
[2789] VOConferenceFrameThe frame window for the conference view. This is derived from the VOChildFrame
[2790] VOConferenceVw The window displaying the conference information
[2791] VOConferenceDoc The document class corresponding to the VOConferenceVw
[2792] VOVideoWatchFrame The frame window for the Video Watch view. This is derived from the VOChildFrame
[2793] VOVideoWatchVw The window displaying the video stream and controls for making calls.
[2794] VOVideoWatchDoc Document class corresponding to the VideoWatch view.
[2795] (2) Class Details
[2796] (a) VOConsoleApp
[2797] (i) Attributes
[2798] (ii) Methods
[2799] Retcode CreateVideoOperator(CString login, CString password);
[2800] Return Value: returns a non-zero value if successful, zero otherwise.
[2801] login parameter: login id for the operator
[2802] password parameter: operator's password
[2803] The Retcode CreateVideoOperator function is initially called during the application instantiation.
[2804] Retcode InitializeCallSystemComponents();
[2805] Return Value: returns a non-zero value if successful, zero otherwise
[2806] The Retcode InitializeCallSystemComponents function is initially called during the application initiation, after the creation of the video operator, which makes a local copy of the pointers to the VOCallSystemlnterface, VOCallObjMgr and the VOConnectionObjMgr objects, initiated by the internal software system.
[2807] void OnGetVOMessage(VOMsg voMsg);
[2808] voMsg parameter: the message object passed by the internal software system
[2809] The void OnGetVOMessage function is called when the application receives a message from the internal software system to redirect the message to the appropriate windows. In the initial implementation, the message will be passed on to the VOMainFrame, which interprets the message. Depending on the type of the message it is either displayed in the V00utputWnd, displayed in a message box, or passed on to the VOConferenceVw and the VOVideoWatch windows.
[2810] (b) VOMainFrame
[2811] (i) Attributes
[2812] (ii) Methods
[2813] Retcode SynchWithDb();
[2814] Return Value: returns a non-zero value if successful. zero otherwize
[2815] login parameter: login id for the operator
[2816] password parameter: operator's password
[2817] The Retcode SynchWithDb function is called if the schedule has changed and the needs to be synchronized with the database.
[2818] Retcode DisplayMessage(VOMsg voMsg);
[2819] Return Value: returns a non-zero successful, zero otherwise voMsg parameter: the VOMsg object received from the internal software system
[2820] The Retcode DisplayMessage function displays the content of the voMsg object in the output window. Based on the severity, an alert message box is also displayed.
[2821] void OnConferenceStatusChanged(VOConference* pConference);
[2822] pConference parameter: pointer to the conference object whose status has changed
[2823] The void OnConferenceStatusChanged function is called when the status of a particular conference has changed.
[2824] (c) VOScheduleWnd
[2825] (i) Attributes
[2826] (ii) Methods
[2827] Retcode DisplaySchedule(BOOL filter =0);
[2828] Return Value: returns a non-zero value if successful. zero otherwise filter parameter: the filter to be applied for display of the schedule. filter =0 displays the entire schedule. filter =1 displays only the active conferences and playback calls
[2829] The Retcode DisplaySchedule function is called to display the list of conferences and playback calls in the schedule window.
[2830] Retcode DisplayConfSites(VOConference* pconference);
[2831] Return Value: returns a non-zero value if successful. zero otherwise pCon-Lerence parameter: pointer to the conference object for which the sites have to be displayed in the sites list box of the schedule window.
[2832] The Retcode DisplayConfSites function is called to display the list of sites in a site list box of the schedule window.
[2833] Retcode OnClickScheduledItem();
[2834] Return Value: returns a non-zero value if the selection is different from the previous selection. zero otherwise
[2835] The Retcode OnClickScheduledItem function is called when the user clicks on an item in the schedule list box. The initial implementation displays the corresponding sites in the conference or the site and the movie details in the playback call.
[2836] Retcode OnDblClickScheduledItem();
[2837] Return Value: returns a non-zero value if a conference window is opened. zero otherwise
[2838] The Retcode OnDblClickScheduledItem function is called when the user double clicks on an item in the schedule list box. The initial implementation creates a new VOConferenceVw for the scheduled item.
[2839] Retcode OnClickSite();
[2840] Return Value: returns a non-zero value if the selection is different from the previous selection. zero otherwise
[2841] The Re-code OnClickSite function is called when the user clicks on an item in the site list box of the Schedule window.
[2842] (d) VOOutputWnd
[2843] (i) Attributes
[2844] (ii) Methods
[2845] Retcode DisplayMessage(CString info, VOMsg* pVoMsg=NULL);
[2846] Return Value: returns a non-zero value if successful. zero otherwise info parameter: additional information to be displayed pVoMsg parameter: a pointer to a VOMsg object
[2847] Retcode DisplayMessage displays a message text in the output window. If pVoMsg=NULL, only the info will be displayed.
[2849] (ii) constructor(s)
[2850] protected VoConferneceVw();
[2851] VoconferenceVw(VoConference* pconference);
[2852] VOConferenceVw (VOplaybackSession* pPbSession);
[2853] pconference parameter: a pointer to the conference object for which the view is to be created.
[2854] pPbSession parameter: a pointer to the playback session object for which the view is to be created.
[2855] The conference view is used to display the information about any conference or a scheduled playback session. This view is created only by the mainframe when the user double clicks on a conference/playback session in the schedule window.
[2856] (iii) Methods
[2857] (VOConference* pconference);
[2858] PConference parameter: a pointer to the conference object whose status has changed.
[2859] void OnConferencestatuschanged is called when the conference status has changed so that the UI can be updated accordingly.
[2860] void OnPbSessionStatusChanged(VoPlaybackSession* pPbSession);
[2861] pPbSession parameter: a pointer to the playback session object whose status has changed.
[2862] void OnPbSessionStatusChanged is called when the playback session's status has changed so that the UI can be updated accordingly.
[2863] void OnConnStatusChanged(VOConnection* pConnection);
[2864] pconnection parameter: a pointer to the connection object whose status has changed.
[2865] void OnConnStatusChanged is called when a connecion's status has changed so that the UI can be updated accordingly.
[2866] void OnCallStatusChanged(VOCall* pCall);
[2867] pCall parameter: a pointer to the playback session object whose status has changed.
[2868] void OnCallStatusChanged is called when the status of a call in the current conference/playback session has changed so that the UI can be updated accordingly.
[2869] void OnPbCallStatusChanged(VOPbCall* pPbCall);
[2870] pPbCall parameter: a pointer to the playback session object whose status has changed.
[2871] void OnPbCallStatusChanged is called when the playback session's status has changed so that the UI can be updated accordingly.
[2872] (VOConnection* pconnection);
[2873] pconnection parameter: a pointer to the Connection object whose status has changed.
[2874] void DisplayConnectionStatus is called to display a connection's status.
[2875] void DisplayCallstatus(VOCall* pCall);
[2876] pCall parameter: pointer to the call object whose status has changed.
[2877] void DisplayCallStatus is called to display a call's status (participant or MCU).
[2878] void DisplayRecordingStatus(); is called to display the recording status if any call in a conference is being recorded.
[2879] void DisplayWatchStatus(); is called to display the indication as to which call is being monitored, in the current conference or playback session.
[2880] void DisplayPlaybackStatus();is called to display the playback status.
[2881] Retcode OnDialSite();
[2882] Return Value: returns a nonzero value if the operation has been initiated successfully, zero otherwise.
[2883] Retcode OnDialSite is called when the Dial button on the participant side is clicked. This will dial the participant of selected connection.
[2884] Retcode OnDialMCU();
[2885] Return Value: returns a nonzero value if the operation has been initiated successfully, zero otherwise.
[2886] Retcode OnDiaIMCU is called when the Dial button on the MCU side is clicked. This will dial the MCU port assigned to the selected participant.
[2887] Retcode OnHangupSite();
[2888] Return Value: returns a nonzero value if the operation has been initiated successfully, zero otherwise.
[2889] Retcode OnHangupSite hangs up the call to the participant.
[2890] Retcode OnHangupMCU();
[2891] Return Value: returns a nonzero value if the operation has been initiated successfully, zero otherwise.
[2892] Retcode OnHangupMCu hangs up the call to the MCU.
[2893] Retcode OnHoldSite();
[2894] Return Value: returns a nonzero value if the operation has been initiated successfully, zero otherwise.
[2895] The Retcode OnHoldSite function puts the participant on hold (if the call is active).
[2896] Retcode OnHoldMCU();
[2897] Return Value: returns a nonzero value if the operation has been initiated successfully, zero otherwise.
[2898] The Retcode OnHoldMCU function puts the MCU on hold (if the call is active).
[2899] Retcode OnWatchSite();
[2900] Return Value: returns a nonzero value if successful, zero otherwise.
[2901] The Retcode OnWatchSite function will monitor the current participant. The video stream corresponding to the participant will be displayed in the video watch window.
[2902] Retcode OnWatchMCU();
[2903] Return Value: returns a nonzero value if successful, zero otherwise.
[2904] Retcode OnWatchMCU starts monitoring the MCU leg corresponding to a participant in a conference. The video stream is displayed in the video watch window.
[2905] Retcode OnRecordMCU();
[2906] Return Value: returns a nonzero value if the operation has been initiated successfully, zero otherwise.
[2907] Retcode OnRecordmcu starts recording the MCU stream. If the recording is already on, this function,;will pause/stop the recording.
[2908] Retcode OnRecordSite();
[2909] Return Value: returns a nonzero value if the operation has been initiated successfully, zero otherwise.
[2910] Retcode OnRecordSite starts recording the stream corresponding the selected participant. If recording is already on, recording will pause/stop.
[2911] Retcode MakeAutoConnection();
[2912] Return Value: returns a nonzero value if the operation has been initiated successfully, zero otherwise.
[2913] Retcode MakeAutoConnection is called to automatically connect the participant and the MCU and when successful, join them.
[2914] Retcode MakeAutoDisconnection();
[2915] Return Value: returns a nonzero value if the operation has been initiated successfully, zero otherwise.
[2916] Retcode MakeAutoDisconnection is called to automatically un-join the connection and disconnect the calls to the participant and the mcu.
[2917] Retcode ConnectAll();
[2918] Return Value: returns a nonzero value if the operation has been initiated successfully, zero otherwise.
[2919] Retcode ConnectAll is called to automatically make all the connection one by one.
[2920] Retcode DisconnectAll();
[2921] Return Value: returns a nonzero value if the operation has been initiated successfully, zero otherwise.
[2922] Retcode DisconnectAll is called to automatically break all the conference connections.
[2923] (f) VOVideoWatchVw
[2924] (i) Attributes
[2925] (ii) constructor(s)
[2926] VOvideoWatchVwo();
[2927] (iii) Methods
[2928] void OnDial();dials the number in the destination edit box.
[2929] void OnTransfer(); transfers the current call to a number. This will initially display a dialog box where the user enters the number top which the call is to be transferred.
[2930] void OnAnswer(); is called when the Answer button is clicked.
[2931] void OnForward(); is called when the forward button is clicked. All the call will be forwarded to the forwarding number provided.
[2932] void OnMute(); is called when the mute button is clicked. Turns the mute on/off.
[2933] void OnHangup(); is called when the hang-up button is clicked. Hangs up the current call.
[2934] void OnHold((); is called when the hold button is clicked. Puts the current call on hold.
[2935] void OnPickup(); is called when the pickup button is clicked. Picks up the call on hold.
[2936] void OnPrivacy(); is called when the privacy button is clicked. Turns the privacy on or off.
[2937] void OnPlayMovie(); is called when the Play button is clicked. This will display a dialog box with a list of movies to choose from. Once a movie is selected, the movie will be played.
[2938] void OnRecordCall(); is called when the record button is clicked.
[2939] void OnJoinToConference(); is called when the Join Conf button is clicked. This will display the list of active conferences and sites OR playback sessions. The operator will select the site corresponding to the current call and the call will be joined to the conference.
[2940] void WatchVideo(BOOL selection();
[2941] Return Value: returns a non-zero value if successful. zero otherwise selection parameter: specifies what to watch.
[2942] selection=VDOWATCH_CONFERENCE displays the video from the site/MCU selected for watching
[2943] selection=VDOWATCH_SELF displays the output of the video operator's camera
[2944] selection=VDOWATCH_CALL displays video from the call selected from the listbox provided in the video watch window OR the video from the incoming call, if any.
[2945] Call the void WatchVideo function to select the video stream to watch.
[2946] void OnDisplayCallsWindow(); is called when the � Calls' button is clicked.
[2947] void OnSelfView(); is called when the 'SelfView' check box is checked or unchecked. When the self view is checked, the video operator's camera output is displayed in a separate small window.
[2948] void OnLocalVolume();is called when the local volume slide bar position is changed. This will adjust the local volume.
[2949] void OnRemoteVolume(); is called when the remote volume slide bar position is changed. This will adjust the remote volume signal.
[2950] b) Media Control Class Description
[2951] (1) VOMediaControl
[2952] (a) Atttlbutes
[2953] (b) Constructor(s)
[2954] VOMediaControl();
[2955] (c) Methods
[2956] public void SetVolume(short rightVolume, short leftvolume);
[2957] rightvolume parameter: an integer between 0-1000.
[2958] leftvolume parameter: an integer between 0-1000.
[2959] public void SetVolume sets the volume control.
[2960] public short GetVolume(short channel);
[2961] Return Value: returns the volume for the specified channel channel parameter: set channel=PORT_CHANNEL_RIGHT for the right volume setting, and set channel=PORT_CHANNEL-LEFT for the left volume setting.
[2962] public short GetVolume returns the current volume for the specified channel
[2963] public void SetSelfView(long flags);
[2964] flags parameter: sets the properties of the self view. The valid flag values are:
[2965] SELFVIEW_ON Displays the self view;
[2966] SELFVIEW_OFF Hides the self view; and
[2967] SELFVIEW_MIRRORED Mirrors the self view.
[2968] public void SetSelfview sets the self view properties.
[2969] public long GetSelfView();
[2970] Return Value: returns the self view settings
[2971] The public long GetSelfView function returns the self view settings which can be used to find out if the self view is visible or hidden, or if it is mirrored.
[2972] public void SetSelfViewSize(short size);
[2973] size parameter: one of the predefined sizes for the self view
[2974] public void SetSelfViewSize sets the size of the self view window. The
[2975] valid values are FULL_CIF, HALF_CIF and QUARTER_CIF.
[2976] public short GetSelfViewSize();
[2977] Return Value: returns Current self view size.
[2978] The public short GetSelfViewSize function returns the current self view window size. The values will be one of the predefined sized. See SetSelfViewSize for the description of the sizes.
[2979] public void SetAutoGain(BOOL autoGain=TRUE);
[2980] autoGain parameter: should be TRUE to enable auto gain, FALSE to disable
[2981] The public void SetAutoGain function enables or disables the auto gain depending on the autoGain value.
[2982] public BOOL GetAutoGain();
[2983] Return Value: returns The current auto gain setting.
[2984] The public BOOL GetAutoGain function returns the current auto gain setting. TRUE if auto gain is on, FALSE otherwise.
[2985] public void SetEchoCancellation (bool bCancel);
[2986] bCancel parameter: if bCancel is TRUE cancellation is enabled; if FALSE cancellation is disabled.
[2987] public void SetEchoCancellation enables or disables echo cancellation.
[2988] public BOOL GetEchoCancellation();
[2989] Return Value: returns the current echo cancellation state.
[2990] public BOOL GetEchoCancellation gets the current state of the current echo cancellation.
[2991] public short GetVideoMode(short mode=MODE_RX);
[2992] Return Value: returns the video mode
[2993] mode parameter: indicates receive or transmit mode.
[2994] public short GetVideoMode gets the audio mode for receive or transmit, depending on the value of mode. mode=MODE_RX for receive mode and MODE_TX for transmit.
[2995] public short GetAudioMode(short mode=MODE_RX);
[2996] Return Value: returns the audio mode mode parameter: indicates receive or transmit mode. public short GetAudioMode gets the audio mode for receive or transmit, depending on the value of mode. mode=MODE_RX for receive mode and MODE_TX for transmit.
[2997] public void SetVideoWnd(HWND hwnd);
[2998] hWnd parameter: pointer to the window where the video is to be displayed.
[2999] The public void SetVideownd function displays the video in the window identified by hWnd.
[3000] public HWND GetVideoWnd();
[3001] Return Value: returns the window handle in which the video is being displayed. If no window is set, NULL is returned.
[3002] The public HWND GetVideoWnd function is called to retrieve the window handle in which the video is being displayed.
[3003] public void MakeVideoWndResizeable(BOOL bResize=TRUE);
[3004] bRe size parameter: if bResize is TRUE, the video window is resizeable; if FALSE, it is not resizeable.
[3005] The public void MakeVideoWndResizeable function makes the video window resizable with bResize=TRUE. To make the window fixed size, make bResize FALSE.
[3006] public BOOL IsVideoWndResizeable();
[3007] Return Value: returns TRUE if the video window is resizeable, FALSE otherwise.
[3008] Call the public BOOL IsVideoWndResizeable function to determine if the video window is resizeable.
[3009] F. Video Operator Shared Database
[3010] 1. Database Schema
[3011]FIG. 107 shows a database schema for the video operator shared database (see 40214 FIG. 98). In one embodiment, the database contains the following tables. CONFERENCE 41104 lists details about a scheduled conference, PARTICIPANT 41105 lists the participants of conferences, and CONF_PARTICIPANT 41108 contains the keys from the CONFERENCE 41104 and PARTICIPANT 41105 tables, which are used to determine the participants in any given conference. MCU 41102 contains the characteristics of different MCU's from various suppliers, and MCUPORT 41106 contains the MCU identification number from the MCU 41102 table as well as the ports of the MCU used by the participants to connect to a conference. VOPERATOR lists video operator attributes; VOTYPES lists all the types (e.g., protocols, bandwidths) used to define a conference or participant; and VOTYPEVALUES 41107 lists the values for each of the defined types.
[3012] Each video operator record in the VDO_OPERATOR 41101 table contains a unique identification number in its ID field, which number may appear in the CONFERENCE 41104 table's operatorID field, assigning each video operator to particular conferences profiled in the CONFERENCE 41104 table. Each conference record in the CONFERENCE 41104 table, in turn, contains a unique identification number in its ID field, which number may appear in the CONF_PARTICIPANT 41108 table's conffD field. Similarly, each participant record in the PARTICIPANT 41105 table contains a unique identification number in its ID field, which number may appear in the CONF_PARTICIPANT 41108 table's participantID field. Finally, each MCU record in the MCU 41102 table contains a unique identification number in its ID field, which number may appear in the MCUPORT 41106 table's mcuID field, identifying the set of MCU ports associated with the MCU. Each MCU port record in the MCUPORT 41106 table, in turn, contains a unique identification number in its ID field, which number may appear in the CONF_PARTICIPANT 41108 table's mcuPortID field. Within the CONF_PARTICIPANT 41108 table, the conflD, participantID, and mcuPortID values are used as cross-referencing keys to define a particular conference with a given conference profile, a set of participants, and an MCU port.
[3013] In addition, each VOType record in the VOTYPE 41103 table contains a unique identification number in its ID field, which number may appear in the VOTYPEVALUES 41107 table's typeID field, identifying a set of values associated with the VOType.
[3014] G. Video Operator Console Graphical User Interface Windows
[3015] 1. Main Console Window
[3016]FIG. 108 shows one embodiment of the Main Console window 41201 as it would appear on a Video Operator Terminal [1 FIG. 96], showing possible placements of a Schedule window 41202, a Conference window 41203, a Video Watch window 41204 and a Console Output window 41205. The Main Console window 41201 enables the video operator to manage video conferences.
[3017] 2. Schedule Window
[3018]FIG. 109 shows one embodiment of the Schedule window 41202, which displays all the conferences 41305 and playback sessions 41306 to be handled by the current video operator for the next 8 hours. In one embodiment, the list is updated upon application startup, at 15 minute intervals, and every time a conference ends.
[3019] The Schedule window will have two scrolled text areas—one area for conferences 41301, and the other for sites 41302 participating in the selected conference. If a conference name is double-clicked, the appropriate Conference Window [41203 FIGS. 108, 110] will appear.
[3020] 3. Conference Window
[3021]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 41202. The display of the Conference Window 41203 is dependent on whether a Conference or a Playback Session has been selected from the Schedule Window 41202. Only one conference window is displayed at a time. When a new conference window is opened, the existing one is hidden. While a Conference Window is hidden, the status of the conference and connections are still monitored. FIG. 110 shows a Conference Session 41401. The Conference window 41203 displays the list of conference Participants 41415 and radio buttons to selectively operate on individual connections, including call setup, viewing, playback and recording.
[3022] Information about the conference such as the duration, start time, end time, playback and recording status, and conference type are displayed at the bottom of the window. If the operator double clicks inside the Conference Window 41203 where there is no action associated with the clicking location, the Properties Box [41701 FIG. 113] is displayed with the conference settings.
[3023] A conference is ended by pressing the End Conference button. This will disconnect all calls associated with the conference.
[3024] The Conference Window 41203 displays the connections in the conference and their connection status 41417, including any free MCU Port slots reserved for a not yet joined connection 41421. Each Connection listing contains a radio button 41422, the participant site name 41423 and status lights 41418-41420. The status of the two calls and the join are monitored and displayed with the site name in the Conference window 41203. The status squares 41418-41420 are colored boxes, with different colors representing different call statuses (e.g., no call, call in progress, active call, or active call that has been disconnected).
[3025] The Conference Window 41203 provides buttons to click 41417 that define the sequence in which a participant site gets connected to an MCU Port site, routed through the video operator. Other features available from this part of the window are watching the video input from a call, recording video input from either call, and making a normal video call to the participant site or to the MCU.
[3026] The color of the arrows 41424 represents the status of each call. The color of the arrows is also duplicated in the status lights 41418-41420 in the list of connections.
[3027] If there is a Playback Connection 41425 associated with the Conference, only one Call is necessary to an MCU Port site. The normal Participant Site call setup interface will be inaccessible, and the Join control 41405 will become the Start and Stop switch for playback.
[3028] Free MCU ports can be reached only when an MCU Port call for a defined Connection is inactive (or disconnected). This allows the operator to join a conference as if the operator were a participant. This is done by selecting the Connection with the free MCU port call. When connected, the operator can inform the rest of the participants that the operator is attempting to contact or restore a connection.
[3029] There are some functional limitations that the Conference Window 41203 will reflect. The Conference Window 41203 should not allow access to functions that cannot be performed, for example:
[3030] The video operator can only view one call at a time.
[3031] The video operator can record any call at any time with software unidirectional decoder.
[3032] Playback connection selection changes the call setup buttons appropriately.
[3033] The video operator can participate in a conference only when a MCU port call is inactive.
[3034] The video operator can talk to participant site only when the participant is disconnected.
[3035] To clarify, a simple connection setup using the Conference Window proceeds as follows. By pressing the Call button near the participant site box 41402, the operator calls Adam (or, alternatively, Adam may call the operator), and then the operator places the call on Hold 41407. By pressing the Call button near the MCU Port site box 41403, the operator calls the MCU and then places the call on Hold 41408. By pressing the Join button 41405, the two calls are joined. In another embodiment, this can be an automated rather than a manual process. Adam and the MCU are now connected as H.320 video call. All three arrows 41424 will be green.
[3036] 4. Video Watch Window
[3037]FIG. 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. The Video Watch window 41204 also has controls for making normal calls 41512 and media control such as audio control 41509-41510.
[3038] The Video Watch window is the display for the unidirectional H.320 decode of the video output of a selected call. By default, the MCU call of the first active site will be displayed. To watch any other call, the appropriate View button must be pressed in the Conference Windows. The video and audio controls for this window such as volume control 41509-41510, picture size 41511, etc., are managed from the Video Control Panel.
[3039] When the operator chooses to make a normal H.320 video call (point to point), to a site or an available slot in an active conference, the Video Watch window 41204 is used for viewing the video. A small self-view video window should appear nearby when the operator selects the Self View button 41506.
[3040] 5. Console Output Window
[3041]FIG. 112 shows one embodiment of the Console Output window 41205 which displays all error messages and alerts 41601. The window is scrollable so that the video operator can see all errors that have occurred in the current session. These messages are also logged to a text file for future reference.
[3042] 6. Properties Dialog Box
[3043]FIG. 113 shows a Properties dialog box 41701. Dialog boxes are windows that are transitional and only displayed temporarily. They are usually used for entering data or displaying information that requires immediate attention. This will be a modeless dialog box displaying the properties of a particular conference or site. There will be only one such window open at any time. If the user focuses on another Conference Window or Connection Window, the same dialog box is updated with the appropriate properties. FIG. 113 pictures the properties associated with a particular site, including the site coordinator 41702, the site phone number 41703, the time 41704, connection type 41705 and terminal type 41706. A Close button 41707 closes the Properties dialog box 41701.
[3045] A. User Interface
[3046] The graphical user interface is designed such that only a single IP connection from the workstation to the server is required. This single IP connection supports both the Internet connection between the WWW Browser and the WWW Site, and the messaging connection between the PC Client and the universal inbox (i.e., Message Center). The PC Client interface is integrated with the WWW Browser interface such that both components can exist on the same workstation and share a single IP connection without causing conflicts between the two applications.
[3047] WWW Browser access is supported from any of the commercially available WWW Browser interfaces:
[3048] Microsoft Internet Explorer;
[3049] Netscape Navigator (1.2, 2.X); or
[3050] Spyglass Mosaic.
[3051] In addition, the WWW Browser interface is optimized to support Windows 95; however, Windows 3.1 and Windows 3.11 are supported as well.
[3052] The WWW Browser interface detects the display characteristics of the user's workstation (or terminal) and adapts the presentation to support the display settings of the workstation. The presentation optimized around a 640�480 pixel display but is also capable of taking advantage of enhanced resolution and display qualities of 800�600 (and greater) monitors.
[3053] To improve performance, the user is able to select between 'minimal graphics' or 'full graphics' presentation. The WWW browser will detect whether a user has selected 'minimal graphics' or 'full graphics' and send only the appropriate graphics files.
[3054] B. Performance
[3055] Response time for downloading of information from the WWW Site or the Personal Home Page to the user's workstation or terminal meets the following benchmarks. Workstation Configuration:
[3056] Processor:486DX-33 MHz;
[3057] Memory: 12 MB;
[3058] Monitor: VGA, Super VGA, or XGA;
[3059] Access: Dialup;
[3060] Windows 95;
[3061] Presentation Option: Full Graphics; and
[3062] Peripherals: Audio Card, Audio Player Software, 14.4 Kbps Modem.
[3063] After a screen or page has been downloaded from the WWW Site to the workstation, the cursor is pre-positioned onto the first required field or field that can be updated.
[3064] C. Personal Home Page
[3065] The system provides subscribers the ability to establish a Personal Home Page which provides a vehicle for people to communicate with or schedule meetings with the subscriber. A person accessing a subscriber's Personal Home Page is referred to as the guest and the user that 'owns' the Personal Home Page is referred to as the subscriber. Guest-access to Personal Home Pages will support the following features:
[3066] Create and send a text-based pager message through networkMCI Paging;
[3067] Create and send an email message to the email (MCI Mail or internetMCI) account; and
[3068] Access the subscriber's calendar to schedule a meeting.
[3069] Messages generated through the subscriber's Personal Home Page are directed to the subscriber's networkMCI or SkyTel Pager, or MCI email account.
[3070] Email messages composed by guests will:
[3071] Present the subscriber's name, not the subscriber's email address, in the email header;
[3072] Provide a field in the email header for the:
[3073] Sender's name (required field),
[3074] Sender's email address (optional field), and
[3075] Subject (optional field).
[3076] Guests 'request' appointments on a subscriber's Personal Home Page.
[3077] Requested appointments on a subscriber's Personal Home Page will be prefaced with "(R)".
[3078] Approved appointments will be prefaced with "(A)".
[3079] Subscribers are responsible for routinely checking their calendars and approving "(A)" or deleting requested appointments, and initiating the necessary follow-up communications to the requesting party. Approved appointments will be prefaced by "(A)".
[3080] Security Requirements
[3081] Calendar access from the Personal Home Page is designed to support two-levels of security:
[3082] No PIN Access:
[3083] Times Only, or
[3084] Times & Events;
[3085] PIN Access:
[3086] Times Only; or
[3087] Times & Events.
[3088] 1. Storage Requirements
[3089] The system stores and maintains past and future appointments in the following manner:
[3090] Current month plus past six months of historical calendar appointments
[3091] Current month plus next twelve months of future calendar appointments.
[3092] A subscriber is provided the option to download the contents of the months appointments that are scheduled to be overwritten in the database. The calendar information that will be downloaded to the subscriber is in a comma delimited or DBF format and capable of being imported into Microsoft Schedule+, ACT or Ascend.
[3093] 2. On Screen Help Text
[3094] On screen help text provides guest and subscriber icon access to field specific "Help" instructions to operate within the Personal Home Page. The Help Text must provide information describing:
[3095] How to Send the subscriber a text-based pager message from the Personal Home Page through networkMCI Paging;
[3096] How to Send the subscriber an email message from the Personal Home Page to an MCI email account;
[3097] How to Access and update a subscriber's Calendar;
[3098] How to Locate a user's Personal Home Page; and
[3099] How to Order your own Personal Home Page through MCI.
[3100] 3. Personal Home Page Directory
[3101] The system provides the guest the ability to access to a Personal Home Page directors through the existing MCI Home Page. This directory allows the guest to search all established Personal Home Page accounts for a specific Personal Home Page address, by specifying Last Name (required); First Name (optional), Organization (optional), State (optional) and/or Zip Code (optional). Results from the Personal Home Page directory search return the following information: Last Name, First Name, Middle Initial, Organization, City, State and Zip Code. Although City is not requested in search criteria it is provided in search results.
[3102] Another means for a guest to locate a Personal Home Page is through the WWW Browser. Many WWW Browsers have built in search capabilities for 'Net Directory.' Users' Personal Home Pages are listed within the directories of Internet addresses presented by the WWW Browser. The benefit to conducting your search from the MCI Home Page is that only Personal Home Pages are indexed (and searched). Conducting the search through the WWW Browser menu option will not limit the search to Personal Home Pages and therefore will conduct a search through a larger list of URLs. In addition, guests have the capability to enter the specific URL (i.e., Open Location) for the Personal Home Page rather than performing a search. This is especially important for those subscribers that have their Personal Home Page "unlisted" in the directory.
[3103] 4. Control Bar
[3104] A Control Bar is presented at the bottom of the Personal Home Page. The Control Bar is presented after the guest has selected Personal Home Pages from the MCI Home Page. The Control Bar provides the guest access to the following features:
[3105] Help Text
[3106] MCI Home Page
[3107] Personal Home Page Directory
[3108] Feedback.
[3109] 5. Home Page
[3110] The Home Page is the point of entry for the subscriber to perform message retrieval and exercise profile management from a WWW Browser. The Home Page is designed to provide the user easy access to the Message Center or Profile Management.
[3111] 6. Security Requirements
[3112] Access to the Message Center or Profile Management is limited to authorized users. Users are prompted to enter their User ID and Password before accessing the Message Center or Profile Management. After three unsuccessful attempts, the user is blocked from accessing the Message Center or Profile Management and a WARNING message advises the subscriber to contact the MCI Customer Support Group. The account is deactivated until an MCI Customer Support representative restores the account. After the account is restored, the subscriber is required to update his or her Password.
[3113] A successful logon to the Message Center enables the user to access Profile Management without being challenged for another (i.e., the same) User ID and Password. The same is also true for users that successfully access Profile Management—they are allowed to access the Message Center without being challenged for another (i.e., the same) User ID and Password. Passwords are valid for one month. Users are prompted to update their password if it has expired. Updates to passwords require the user to enter the expired password, and the new password twice.
[3114] 7. On Screen Help Text
[3115] Provide the subscriber icon access to field specific "Help" instructions to operate within the Home Page. The Help Text provides information describing:
[3116] How to Access Message Center;
[3117] How to Access Profile Management;
[3118] How to Access the MCI Home Page;
[3119] How to Access Personal Home Pages;
[3120] How to Send (i.e. Create or Forward) Messages through Message Center;
[3121] How to File Messages through Message Center;
[3122] How to Update the directlineMCI Profile;
[3123] How to Update the Information Services Profile;
[3124] How to Update their Personal Home Page;
[3125] How to Provide Feedback on the Home Page; and
[3126] How to Order the User's Guide.
[3127] Control Bar
[3128] A Control Bar is presented at the bottom of the Home Page. The Control Bar provides the guest access to the following features:
[3129] Help Text;
[3130] MCI Home Page;
[3131] Personal Home Page Directory; and
[3132] Feedback.
[3133] 8. Profile Management
[3134] In addition to the On-Screen Help Text and Control Bar discussed above, the Profile Management screen presents a Title Bar. The Title Bar provides the subscriber easy access to the Profile Management components and quick access to the Message Center. Access to the Profile Management components is provided through the use of tabs which will include:
[3135] directlineMCI;
[3136] Information Services;
[3137] Personal Home Page;
[3138] List Management; and
[3139] Message Handling.
[3140] The directlineMCI tab includes additional tabs for the underlying components of directlineMCI which are:
[3141] Voicemail;
[3142] FAXmail;
[3143] Paging.
[3144] The directlineMCI Profile Management system provides subscribers a Profile Management page from which account profile information can be manipulated to:
[3145] Create new directlineMCI profiles and assign names to the profile;
[3146] Update existing directlineMCI profiles;
[3147] Support the rules-based logic of creating and updating directlineMCI profiles (e.g., selection of only one call routing option, like voicemail, invokes override routing to voicemail; and updates made in one screen ripple through all affected screens, like paging notification();
[3148] Enable a directlineMCI number;
[3149] Enable and define override routing number;
[3150] Enable and define FollowMe routing; and
[3151] Define RNA parameters for each number in the directlineMCI FollowMe routing sequence
[3152] Enable and define final routing (formerly called alternate routing) to:
[3153] Voicemail and pager,
[3154] Voicemail only,
[3155] Pager only, and
[3156] Final message;
[3157] Invoke menu routing if two or more of the call routing options (FollowMe, voicemail, faxmail or pager) are enabled;
[3158] Enable voicemail;
[3159] Enable faxmail;
[3160] Enable paging;
[3161] Define the default number for faxmail delivery;
[3162] Activate paging notification for voicemail;
[3163] Activate paging notification for faxmail;
[3164] Define schedules to activate/deactivate different directlineMCI profiles;
[3165] Provide guest option to classify voicemails for urgent delivery;
[3166] Configure the time zone for all message types that will be used to identify the time a message is received;
[3167] Define call screening parameters for:
[3168] Name and ANI,
[3169] ANI only, and
[3170] Name only; and
[3171] Enable or disabling park and page.
[3172] 9. Information Services Profile Management
[3173] Information Services Profile Management provides subscribers the ability to select the information source, delivery mechanism (voicemail, pager, email) and the delivery frequency depending upon the information source and content. Specifically, the subscriber has the ability configure any of the following information sources:
[3174] Stock Quotes and Financial News; and
[3175] Headline News.
[3176] Stock Quotes and Financial News provides the subscriber the following:
[3177] Business News Headlines;
[3178] Stock Quotes (delay less than or equal to 10 minutes);
[3179] Stock Market Reports (hourly, AM/PM or COB);
[3180] Currency and Bond Reports (hourly, AM/PM or COB);
[3181] Precious Metal Reports (hourly, AM/PM or COB); and
[3182] Commodities Reports (hourly, AM/PM or COB).
[3183] Business News Headlines are delivered via email once per day. Reports (Stock Market, Currency and Bond, Precious Metal and Commodities) are delivered at the interval specified by the subscriber. Hourly reports require that email message is time stamped at 10 minutes after the hour. AM/PM reports require that one email message is transmitted in the morning (11:10 am ET) and one email message is transmitted in the evening (5:10 PM ET), with COB reports transmitted at 5:10 PM ET.
[3184] The content of the Stock Market Report contains:
[3185] Stock or mutual fund ticker symbol;
[3186] Stock or mutual fund opening price;
[3187] Stock or mutual fund closing price;
[3188] Last recorded bid price for the stock or mutual fund;
[3189] Last recorded ask price for the stock or mutual fund;
[3190] Stock or mutual fund's 52-week high; and
[3191] Stock or mutual fund 52 -week low.
[3192] Stock Quotes and Financial News also provide the subscriber the ability to select from a list of available stocks and mutual funds and define criteria whereby a voicemail or text-based page is provided. The definable criteria are referred to as 'trigger points' and can be any or all of the following conditions:
[3193] Stock or mutual fund reaches a 52-week high value;
[3194] Stock or mutual fund reaches a 52-week low value;
[3195] Stock or mutual fund reaches a user-defined high point; and
[3196] Stock or mutual fund reaches a user-defined low-point.
[3197] After a 'trigger point' condition has been satisfied, a message (voicemail or text-based pager) is transmitted within 1 minute to the subscriber. Voicemail messages are directed to the subscriber's mailbox defined in the user's directlineMCI account. The information content for Stock Quotes and Financial News is no older-than 10-minutes old.
[3198] 10. Personal Home Page Profile Management
[3199] Personal Home Page Profile Management provides subscribers the ability to customize their Personal Home Page and define how guests can communicate with them (email or text-based pager). In addition, Profile Management also enables subscribers to control guest access to their calendar. Specifically, the subscriber is able to:
[3200] Establish and maintain a greeting message;
[3201] Establish and maintain a contact information (i.e., address information();
[3202] Establish and maintain a personal calendar;
[3203] Enable or disable guest access to paging, email or calendar;
[3204] Control guest access to calendar by defining PINs for standard or privileged access; and
[3205] Incorporate an approved subscriber submitted graphic, such as a personal photo or corporate logo, on a predefined location on the Personal Home Page.
[3206] Upon creation of the Personal Home Page, the contact information is populated with the subscriber's delivery address information. The subscriber has the capability to update that address information contained within the contact information.
[3207] 11. List Management
[3208] List Management provides the subscriber the ability to create and update lists. Profile Management provides subscribers the ability to define lists accessible through the Message Center for message distribution. In one embodiment, list management is centralized such that Fax Broadcast list management capabilities are integrated with directlineMCI list management capabilities to provide a single database of lists. In an alternate embodiment, the two list management systems are separate, so the user may access either database for lists.
[3209] Lists are maintained through an interface similar to an address book on the PC Client whereby subscriber are able to add or remove names to lists. Associated with each person's name are the email address, faxmail address (i.e., ANI), voicemail address (i.e., ANI), and pager number. As messages populate the Message Center inbox (i.e., universal inbox), the address book is updated with the source address of the associated message type.
[3210] When a subscriber chooses to create a distribution list, she is prompted to select a name, type and identifier name for the list. All created lists are available in alphabetical order by name. The type of the list (voice, fax, email, page) accompanies the list name. In addition, list identifiers may consist of alphabetic characters.
[3211] The subscriber is then prompted for recipient names and addresses to create a distribution list. The subscriber is able to access his address book for recipient information. The subscriber is not be restricted to recording the same address types in his list; if a list is created with a fax type, the subscriber is able to include ANI) email and paging addresses in the list. The subscriber is able to manage his distribution lists with create, review, delete, edit (add and delete recipients) and rename capabilities.
[3212] When the user chooses to modify a list through the WWW Browser interface, she is prompted to select the address type (voice, fax, fax, paging, email) and a list of the user's distribution lists should be provided for that address type. The user is also able to enter the List Name to locate it. Users are able to modify lists through create, review, edit (add and remove recipients), delete and rename commands.
[3213] Whenever a subscriber modifies a list with a recipient addition, removal or address change, she is able to make the modification a global change. For example, a user changes the voice mailbox address for Mr. Brown in one list. she is able to make this a global change, changing that address for Mr. Brown in all of his distribution lists. While the subscriber is able to create and modify distribution lists through the ARU and VRU in addition to the PC, enhanced list maintenance capabilities are supported through the WWW Browser interface.
[3214] The subscriber is able to search and sort lists by name or by the different address fields. For example, a user is able to search for all lists containing 'DOLE' by using the *DOLE* command within the search function. In addition, users are able to search lists using any of the address fields. For example, a user could search based on a recipient number, 'to' name or zip code. A user is able to sort lists by list names, identifiers and types or by any address field.
[3215] In addition to search capabilities, the distribution list software enables the user to copy and create sub-lists from existing distribution list records. The user is able to import and export recipient data from external database structures.
[3216] The capability to share lists among users and upload lists to a host also exists.
[3217] 12. Global Message Handling
[3218] Global Message Handling provides subscribers the ability to define the message types that will appear in the "universal inbox" or accessed through the Message Center. The following message types are selectable:
[3219] directlineMCI voicemail;
[3220] directlineMCI faxmail;
[3221] networkMCI and SkyTel Paging; and
[3222] Email from an MCI email account (i.e., MCI Mail or intemetMCI).
[3223] If a subscriber is not enrolled in a specific service then that option will be grayed-out and therefore not selectable within Global Message Handling. Any updates to Global Message Handling result in a real-time update to the Message Center. An example is that a subscriber may choose to allow voicemail messages to appear in the Message Center. The Message Center automatically retrieves all voicemail message objects that exist within the voicemail database.
[3224] D. Message Center
[3225] The Message Center functions as the "universal inbox" for retrieving and manipulating message objects. The "universal inbox" consists of folders containing messages addressed to the user. Access to the Message Center is supported from all WWW Browsers, but content contained in the "universal inbox" only presents the following message types:
[3226] Voicemail: addressed to user's directlineMCI account;
[3227] Email: addressed to the user's MCI email (i.e., MCI Mail or internetMCI) account;
[3228] FAXmail: addressed to the user's directlineMCI account; and
[3229] Paging: addressed to the user's networkMCI Paging account (or SkyTel Paging account).
[3230] In addition to the On-Screen Help Text and Control Bar discussed in the previous sections, the Message Center screen presents a Title Bar. The Title Bar provides the subscriber easy access to the Message Center functions and quick access to Profile Management. The Message Center functions that are supported through the Title Bar are:
[3231] File: lists user's defined folders and allows user to select folder;
[3232] Create: compose a new email message;
[3233] Forward: voicemails will be forwarded as email attachments;
[3234] Search: provide ability to search based on message type, sender's name or address, subject or date/time; and
[3235] Save: allows users to save messages to a folder on the universal inbox, to a file on the workstation or to a diskette.
[3236] When composing or forwarding messages through the Message Center, the user has the ability to send a message as either an email or a faxmail. The only limitation is that voicemails may only be forw,%.-ded as voicemails or as email attachments. All other message types may be interchanged such that emails may be forwarded to a fax machine, or pager messages may be forwarded as an email text message. Messages that are sent out as faxmail messages are generated in a G3 format, and support distribution to Fax Broadcast lists.
[3237] The presentation layout of the Message Center is consistent with the presentation layout of the PC Client such that they have the same look and feel. The Message Center is designed to present a Message Header Frame and a Message Preview Frame, similar to the presentation that is supported by nMB v3.x. The user will have the ability to dynamically re-size the height of the Message Header Frame and the Message Preview Frame. The Message Header Frame will display the following envelope information:
[3238] Message type (email, voice, fax, page);
[3239] Sender's name, ANI or email address;
[3240] Subject;
[3241] Date/time; and
[3242] Message size.
[3243] The Message Preview Frame displays the initial lines of the body of the email message, the initial lines of the first page of the faxmail message, the pager message, or instructions on how to play the voicemail message. Playing of voicemail messages through an WWW Browser is supported as a streaming audio capability such that the subscriber is not required to download the audio flle to their workstation before playing it. The streaming audio is initiated after the user has selected (single left-mouse click) on the voicemail header in the Message Header Frame. Displaying of faxmail messages is initiated immediately after the user has selected (single left-mouse click) on the faxmail header in the Message Header Frame.
[3244] The Message Center also allows the subscriber to use distribution lists that have been created in Profile Management. The distribution lists support sending messages across different message types.
[3245] In addition to the basic message retrieval and message distribution, the Message Center supports the creation and maintenance of message folders (or directories) within the universal inbox. Initially users are limited to the following folders:
[3246] Draft: retains all saved messages that have NOT been sent;
[3247] Inbox: retains all messages received by the "universal inbox" and it will be the default folder presented when the user accesses Message Center;
[3248] Sent: retains all messages that have been sent; and
[3249] Trash: retains for 7 days all messages marked for delete. Subscribers will eventually be able to create (and rename) folders (and folders within folders).
[3250] 1. Storage Requirements
[3251] Initially, users are allotted a limited amount of storage space for directlineMCI voicemail and directlineMCI faxmail. Pager recall messages and email messages are not limited based upon amount of storage space consumed, but rather the date/time stamp of the message received. Ultimately, storage requirements will be enforced based upon a common measurement unit, like days. This will provide users an easier approach to knowing when messages will be deleted from the database, and when guests will be prevented from depositing a message (voicemail, faxmail) to their "universal inbox". To support this, the following are storage requirements for messages retained in the inbox:
[3252] directlineMCI voicemail: 60 minutes;
[3253] directlineMCI faxmail: 50 pages;
[3254] networkMCI pages: 99 hours; and
[3255] Email: 6 months.
[3256] The subscriber is provided the option to download the messages that are scheduled to be overwritten in the database except for messages that are retained in the trash folder.
[3257] E. PC Client Capabilities
[3258] 1. User Interface
[3259] The PC Client interface supports subscribers that want to operate in a store & forward environment. These users want to download messages to either manipulate or store locally. The PC Client is not designed to support Profile Management and the PC Client interface only presents messages (voicemail, faxmail, email, text-page). Access to Profile Management capabilities only is available through the ARU interface or the WWW Browser interface. The PC Client interface is integrated with the WWW Browser interface such that both components can exist on the same workstation and share a single IP connection.
[3260] The PC Client interface is optimized to support Windows 95; however, Windows 3.1 is supported as well.
[3261] The graphical user interface is designed to present a Message Header Window and a Message Preview Window, similar to the presentation that is supported by nMB v3.x and is supported by the WWW Browser. The user has the ability to dynamically re-size the height of the Message Header Window and the Message Preview Window. The Message Header Window displays the following envelope information:
[3262] Message type (email, voice, fax, page);
[3263] Sender's name, ANI or email address;
[3264] Subject;
[3265] Date/time; and
[3266] Message size.
[3267] The Message Preview Window displays the initial lines of the body of email messages or pager messages, or instructions on how to display the faxmail message or play the voicemail message. Playing of voicemail messages from the PC Client requires an audio card be present on the PC. Displaying of faxmail messages invokes the faxmail reader within the PC Client.
[3268] The Message Center also allows the user to use distribution lists that have been created in Profile Management. The distribution lists support sending messages across different message types.
[3269] 2. Security
[3270] User authentication between the PC Client and the server is negotiated during the dial-up logon session. Security is supported such that the User ID and Password information is imbedded in the information that is passed between the PC Client and server when establishing the interface. Subscribers are not required to manually enter their User ID and Password. In addition, updates made to the password are communicated to the PC Client.
[3271] 3. Message Retrieval
[3272] Message Retrieval provides subscribers the ability to selectively retrieve voicemail, faxmail, pages and email messages that reside in the "universal inbox". Message types that are displayed or played from the PC Client include:
[3273] directlineMCI voicemail;
[3274] directlineMCI faxmail; networkMCI paging; and
[3275] Email from an MCI email account;
[3276] The PC Client initiates a single communication session to retrieve all message types from the "universal inbox". This single communication session is able to access the upstream databases containing voicemails, faxmails, emails and pages.
[3277] The PC Client also is able to perform selective message retrieval such that the user is able to:
[3278] Retrieve all messages;
[3279] Retrieve full text (or body) for selected message header(s);
[3280] Retrieve messages based upon editable search criteria:
[3281] priority messages;
[3282] email messages;
[3283] pager messages;
[3284] faxmail messages (complete or header only);
[3285] voicemail messages (complete or header only);
[3286] sender name, address or ANI;
[3287] date/time stamp on message; and
[3288] message size.
[3289] Header-only faxmail messages retrieved from the "universal inbox" are retained in the "universal inbox" until the message body is retrieved. Voicemail messages are retained in the "universal inbox" until the subscriber accesses the "universal inbox" via the WWW Browser (i.e., Message Center) or ARU and deletes the message. Messages retrieved from the "universal inbox" are moved to the desktop folder.
[3290] In addition, the PC Client is able to support background and scheduled polling such that users are able to perform message manipulation (create, edit, delete, forward, save, etc.) while the PC Client is retrieving messages.
[3291] 4. Message Manipulation
[3292] Message Manipulation provides subscribers the ability to perform many standard messaging client actions, like:
[3293] Compose (or create) email, faxmail or pager messages;
[3294] Forward all message types;
[3295] Save;
[3296] Edit;
[3297] Delete;
[3298] Distribute;
[3299] Attach;
[3300] Search; and
[3301] Display or play messages.
[3302] F. Order Entry Requirements
[3303] directlineMCI or networkMCI Business customers are provided additional interface options to perform profile management and message management functions. Both directlineMCI and networkMCI Business customers are automatically provided accounts to access the features and functions available through the different interface types. The ability to provide accounts to networkMCI Business customers is also supported; however not all networkMCI Business customers are provided accounts. Order entry is flexible enough to generate accounts for networkMCI Business customers, as needed.
[3304] Order entry is designed such that directlineMCI customers or networkMCI Business customers are automatically provided access to the additional interface types and services provided in the system. For example, a customer that orders directlineMCI (or networkMCI Business) is provided an account to access the Home Page for Profile Management or Message Center. Checks are in place to prevent a customer from being configured with two accounts—one from directlineMCI and one from networkMCI Business. In order to accomplish this, integration between the two order entry procedures is established.
[3305] An integrated approach to order entry requires a single interface. The interface integrates order entry capabilities such that the order entry appears to be housed in one order entry system and does not require the order entry administrator to establish independent logon sessions to multiple order entry systems. This integrated order entry interface supports a consistent order entry methodology for all of the services and is capable of pulling information from the necessary order entry systems. In addition, the interface supports the capability to see the services associated with the user's existing application.
[3306] The specific requirements of the integrated order interface system are:
[3307] Automated feeds to define an MCI email (MCI Mail or internetMCI) account;
[3308] Automated feeds to define a networkMCI paging account(or Skylevel Paging) account;
[3309] Automated feeds to define a directlineMCI account;
[3310] Automated feeds to enable Fax Broadcast capabilities;
[3311] Ability to manually enter MCI email account, networkMCI paging account or directlineMCI account information;
[3312] Ability to enable or disable access to inbound information services; and
[3313] Ability to enable or disable access to outbound information services.
[3314] These abilities give order entry administrators the flexibility to add a user based upon preexisting MCI service (email, paging, directlineMCI) account information. Alternatively, the order administrator may add a user while specifying the underlying services.
[3315] The order entry systems provide the necessary customer account and service information to the downstream billing systems. They also track the initial customer order and all subsequent updates so that MCI can avoid sending duplicate platform software (i.e., PC Client) and documentation (i.e., User Guide). In addition, order entry processes enable an administrator to obtain the following information:
[3316] Record customer delivery and name:
[3317] support USA and Canadian addresses, and
[3318] provide ability to prevent delivery to P.O. boxes;
[3319] Record customer's billing address, phone number and contact name;
[3320] Record the order date and all subsequent updates;
[3321] Record the name, phone number and division of the Ac .ount Representative that submitted the order;
[3322] Record or obtain the user's directlineMCI number;
[3323] Record or obtain the user's networkMCI paging PIN;
[3324] Record or obtain the user's MCI email account ID;
[3325] Generate a daily Fulfillment Report that is electronically sent to fulfillment house; and
[3326] Generate a daily Report that tracks:
[3327] number of orders received;
[3328] number of orders to create networkMCI Paging (or SkyTel Paging) account;
[3329] number of orders to create MCI email account, and
[3330] number of orders to create a directlineMCI account.
[3331] Personal home pages can be ordered for a customer. The customer delivery information recorded during order entry is the default address information that is presented from the user's Personal Home Page. In addition, the order entry processes support the installation of and charging for special graphics.
[3332] The capability to turn existing feature/functionality 'on' and 'off' for a specific service exists. Features that can be managed by the user are identified within the order entry systems. These features are then activated for management within the user's directory account.
[3333] There are real-time access capabilities between order entry systems and the user's directory account. This account houses all of the user's services, product feature/functionality, and account information, whether user- managed or not. Those items that are not identified as user-managed are not accessible through the user's interface.
[3334] 1. Provisioning and Fulfillment
[3335] Access requirements have been defined in terms of inbound access to the system and outbound access from the system. Inbound access includes the methods through which a user or a caller may access the system. Outbound access includes the methods through which users are handled by the system in accordance with a preferred embodiment. Internet support exists for both inbound and outbound processing.
[3336] The following components may provide inbound access:
[3337] directlineMCI: 800/8XX;
[3338] MCIMail: 800/8XX, email addresses;
[3339] networkMCI Paging: 800/8XX; and
[3340] internetMCI mail: 800/8XX, POP3 email address.
[3341] The following components have been identified for outbound access:
[3342] directlineMCI: Dial 1;
[3343] Fax Broadcast: 800/8XX, local;
[3344] MCI Mail: 800/8XX, email address; and
[3345] internetMCI mail: 800/8XX, POP3 email address.
[3346] G. Traffic Systems
[3347] Traffic is supported according to current MCI procedures.
[3348] H. Pricing
[3349] Initially, the features are priced according to, the existing pricing structure defined for the underlying components. In addition, taxing and discounting capabilities are supported for the underlying components as they are currently being supported. Discounting is also supported for customers that subscribe to multiple services.
[3350] I. Billing
[3351] The billing system:
[3352] Supports charges for directlineMCI enhanced services (voicemail, faxmail, both);
[3353] Supports charges for peak and off-peak rates;
[3354] Supports discounts for multiple services (directlineMCI, networkMCI Business, networkMCI Paging, networkMCI Cellular) which will vary based upon number of services;
[3355] Supports ability to suppress networkMCI Cellular charges for directlineMCI calls (originating and terminating);
[3356] Supports charges for monthly fees sensitive to directlineMCI usage;
[3357] Supports promotions in the form of free minutes based on directlineMCI usage;
[3358] Supports charges for Personal Home Pages;
[3359] Supports ability to suppress charges for Personal Home Pages; and
[3360] Supports SCA Pricing.
[3361] In one embodiment, the billing system supports the current invoicing procedures that exist for each of the underlying components. In an alternative embodiment, the billing provides a consolidated invoice that includes all of the underlying components. In addition to invoicing, directed billing is supported for all of the underlying components that are currently supporting directed billing.
[3363] The following is a description of the architecture of the directline MCI system, as modified for use with the system. This document covers the general data and call flows in the directlineMCI platform, and documents the network and hardware architecture necessary to support those flows. Billing flows in the downstream systems are covered at a very high level. Order Entry (OE) flows in the upstream systems are covered at a very high level. Certain portions of the directlineMCI architecture reuse existing components (e.g. the Audio Response Unit (ARU)). Those portions of the directliiieMCI architecture which are new are covered in more detail.
[3364] A. Overview
[3365] In addition to billing, order entry, and alarming, the directlineMCI system is made up of three major components, as shown in FIG. 43:
[3366] ARU (Audio Response Unit) 502
[3367] VFP (Voice Fax Platform) 504
[3368] DDS (Data Distribution Service) 506
[3369] The subsections below describe each of the major components at a high level.
[3370]FIG. 43 shows the high-level relationships between the major system components.
[3371] 1. The ARU (Audio Response Unit) 502
[3372] The ARU 502 handles all initial inbound calls for directlineMCI. Some features (such as find me/follow me) are implemented entirely on the ARU. Inbound faxes are tone-detected by the ARU and extended to the VFP 504. Menuing provided by the ARU can be used to request access to the voicemail/faxmail features, in which case the call is also extended to the VFP.
[3373] 2. The VFP (Voice Fax Platform) 504
[3374] The VFP provides the menuing for the voicemail/faxmail features as well as outbound fax and voice forwarding and pager notifications. The VFP is also the central data store for the customized subscriber prompts which are played and recorded by the ARU 502.
[3375] 3. The DDS (Data Distribution Service) 506
[3376] The DDS is a central data repository for OE profiles and Billing Details Records (BDRs). OE profiles are deposited with DDS, which is responsible for distributing the profiles to all of the appropriate systems. DDS 506 collects BDRs and ships them to the downstream billing systems.
[3377] B. Rationale
[3378] The requirement for the directlineMCI service is to integrate a variety of service components into a single service accessed by a single 800 number. A number of these service components had been previously developed on the ISN ARU platform. The services not present in the ARU were mailbox services and fax services. The ARU 502 of the system incorporates a voicemail/faxmail platform purchased from Texas Instruments (TI). Portions of that software are ported to run on DEC Alpha machines for performance, reliability, and scalability. Another requirement for the directlineMCI implementation is integration with the mainstream (existing MCI) billing and order entry systems. The DDS provides the inbound and outbound interfaces between directlineMC1 and the mainstream order entry systems.
[3379] C. Detail
[3380]FIG. 43 shows the relationships between the major system components. The OE system 508 generates subscriber profiles which are downloaded via DDS 506 to the ARU 502 and the Voice Fax Platform (VFP) 504. BDRs generated by the ARU 502 and VFP 504 are fed to the billing systems 510 via DDS 506. The ARU 502 handles all inbound calls. If faxtone is detected, or if a voicemail/faxmail feature is requested, the call is extended from the ARU 502 to the VFP 504. For mailbox status (e.g. "You have three messages"), the ARU 502 queries the VFP 504 for status and plays the prompt.
[3381] Subscribers' customized prompts are stored on the VFP 504. When the ARU plays the customized prompt, or records a new prompt, the prompt is accessed on the VFP 504. Alarms from the ARU 502 and VFP 504 are sent to the Local Support Element (LSE).
[3382] 1. Call Flow Architecture 520
[3383] The call flow architecture for directlineMCI is shown in FIG. 44. The top part of the figure shows the network 522 connectivity used to transport the calls. The bottom part of the figure shows the call direction for different call types. The subsections below provide the text description to accompany the figure.
[3384] 2. Network Connectivity
[3385] All inbound ISN calls are received at an Automatic Call Distributor (ACD) 524 connected to the MCI network 522. The Access Control Point (ACP) receives notice of an inbound call from the Integrated Services Network Application Processor (ISNAP) 526, which is the control/data interface to the ACD 524. The Network Audio System (NAS) plays and records voice under the control of the ACP via a T1 interface to the ACD. In the United States, a digital multiplexing system is employed in which a first level of multiplexed transmission, known as T1, combines 24 digitized voice channels over a four-wire cable (one-pair of wires for "send" signals and one pair of wires for "creceive" signals). The conventional bit format on the T1 carrier is known as DS1 (i.e., first level multiplexed digital service or digital signal format), which consists of consecutive frames, each frame having 24 PCM voice channels (or DS0 channels) of eight bits each. Each frame has an additional framing bit for control purposes, for a total of 193 bits per frame. The T1 transmission rate is 8000 frames per second or 1.544 megabits per second (Mbps). The frames are assembled for Ti transmission using a technique known as time division multiplexing (TDM), in which each DS0 channel is assigned one of 24 sequential time slots within a frame, each time slot containing an 8-bit word.
[3386] Transmission through the network of local, regional and long distance service providers involves sophisticated call processing through various switches and hierarchy of multiplexed carriers. At the pinnacle of conventional high-speed transmission is the synchronous optical network (SONET), which utilizes fiber-optic media and is capable of transmission rates in the gigabit range (in excess of one-billion bits per second). After passing through the network, the higher level multiplexed carriers are demultiplexed ("demuxed") back down to individual DS0 lines, decoded and coupled to individual subscriber telephones.
[3387] Typically, multiple signals are multipexed over a single line. For example, DS3 transmission is typically carried by a coaxial cable and combines twenty-eight DS1 signals at 44.736 Mbps. An OC3 optical fiber carrier, which is at a low level in the optical hierarchy, combines three DS3 signals at 155.52 Mbps, providing a capacity for 2016 individual voice channels in a single fiber-optic cable. SONET transmissions carried by optical fiber are capable of even higher transmission rates.
[3388] The NAS/ACP combination is referred to as the ARU 502. if the ARU 502 determines that a call must be extended to the VFP 504, it dials out to the VFP 504. The VFP media servers are connected to the MCI network 522 via T1. Data transfer from the ARU 502 to the VFP 504 is accomplished via is Dual Tone Multi-Frequency (DTMF) on each call.
[3389] 3. Call Flow
[3390] The call scenarios shown in FIG. 44 are detailed below. At the start of any of the inbound calls, the ARU 502 has already received the call and performed an application select to determine whether the call is a directlineMCI call or not.
[3391] a) Inbound FAX:
[3392] An inbound FAX call is delivered to the ARU 502. The ARU performs a faxtone detect and extends the call to the VFP 504. Account number and mode are delivered to the VFP utilizing DTMF signaling.
[3393] b) Inbound Voice, ARU only:
[3394] An inbound voice call is made in either subscriber or guest mode, and only those features which use the ARU 502 are accessed. The ARU determines mode (subscriber or guest). In subscriber mode, the ARU queries the VFP 504 to determine the number of messages. No additional network accesses are made.
[3395] c) Inbound/Outbound Voice, ARU only:
[3396] A call is made to the ARU 502, and either pager notification or find me/follow me features are accessed. The ARU 502 dials out via the ACD 524 to the outside number.
[3397] d) Inbound Voice, VFP features:
[3398] A call is made to the ARU 502, and the call is extended to the VFP 504. Account number and mode (subscriber or guest) are sent to the VFP via DTMF. The guest modes are:
[3399] 1. Deposit voicemail.
[3400] 2. Deposit fax mail.
[3401] 3. Collect fax mail.
[3402] The subscriber modes are:
[3403] 1. Retrieve or send mail.
[3404] 2. Maintain broadcast lists.
[3405] 3. Modify mailbox name recording.
[3406] The VFP 504 continues prompting the user during the VFP session.
[3407] e) Outbound Fax/Voice/Pager, VFP only:
[3408] For FAX or voice delivery or pager notification, the VFP dials out on the MCI network 522 directly.
[3409] f) Reoriginate/Takeback:
[3410] While an inbound subscriber call is connected to the VFP 504, the user may return to the top level of the ARU 502 directlineMCI menus by pressing the pound key for two seconds. The network 522 takes the call back from the VFP 504 and reorginates the call to the ARU 502.
[3411] 4. Data Flow Architecture
[3412]FIG. 45 depicts the primary data flows in the directlineMCI architecture 520:
[3413] OE records (customer profiles) are entered in an upstream system and are downloaded at 530 to the DDS mainframe 532. The DDS mainframe downloads the OE records to the Network Information Distributed Services (NIDS) servers 534 on the ARU/ACP and the VFP/Executive Server 536. These downloads are done via the ISN token ring network 538. On the executive server 536, the OE records are stored in the local Executive Server database (not shown).
[3414] BDRs are cut by both the Executive Server 536 and the ACP 540. These BDRs are stored in an Operator Network Center (ONC) server 542 and are uploaded to the DDS mainframe 532. The uploads from the ONC servers 542 to the DDS mainframe are done via the ISN token ring network 538.
[3415] The ARU 502 prompts subscribers with their number of voicemail/faxmail messages. The number of messages a subscriber has is obtained from the VFP 504 by the ACP 540 over the ISNAP Ethernet 544. Note that the ACPs 540 may be at any of the ISN sites.
[3416] The user-recorded ad hoc prompts played by the NAS 546 are stored on the VFP 504 and are played over the network on demand by the NAS 546. The NFS protocol 548 is used over the ISNAP Local Area Network (LAN) 544 and Wide Area network (WAN) 550.
[3417] D. Voice Fax Platformn (VFP) 504 Detailed Architecture
[3418] 1. Overview
[3419]FIG. 46 shows the hardware components of the Voice Fax Portion 504 of the directlineMCI system for the first embodiment. The main components in this system are:
[3420] The TI MultiServe 4000 media server 560.
[3421] The DEC 8200 executive servers 536.
[3422] The Cabletron MMAC+hubs 562.
[3423] The AlphaStation 200 console manager and terminal servers 564.
[3424] The Bay Networks 5000 hubs 566.
[3425] In another embodiment, the Cabletron hubs will be removed from the configuration, and the Bay Networks hubs will then carry all the network traffic.
[3426] 2. Rationale
[3427] The TI MultiServe 4000 560 was selected by MCI for the voicemail/faxmail portion of the directlineMCI platform. The MultiServe 4000 is a fairly slow 68040 machine on a fairly slow Nubus backplane. The 68040/Nubus machines are used by TI as both media servers (T1 interface, DSPs for voice and fax) and also for the executive server (database and object storage).
[3428] Although this hardware is adequate for media server use, it was inadequate as an executive server to serve hundreds or even thousands of gigabytes of voice and fax data and thousands of media server ports. Additionally, there is no clustering (for either performance or redundancy) available for the media server hardware. Thus, the executive server portion of the TI implementation was ported by MCI to run on a DEC Alpha 8200 cluster 536, described below. This clustering provides both failover and loadsharing (thus scalability).
[3429] Likewise, the gigabytes that must be moved from the high speed 8200 platforms must be moved across a network to the TI media servers. Cabletron Hubs 562 with both Fiber Distribution Data Interface (FDDI) and switched 10 bT connectivity provide the backbone for the implementation. Each media server 560 is attached to a redundant pair of switched Ethernet ports. Because each port is a switched port, each media server gets a dedicated 10 Mb of bandwidth to the hub. The 8200 servers 536 each need a large network pipe to serve the many smaller 10Mb Ethernet pipes. For the first embodiment, the FDDI interfaces 568 will be used. However, traffic projections show that the necessary traffic will exceed FDDI capacity by several times, so an embodiment in accordance with a preferred embodiment will use higher speed networking technology such as ATM. The hub 562 configuration is fully redundant.
[3430] The AlphaStation 200 workstation 564 is needed for operations support. The AlphaStation 200 provides console management via DEC's Polycenter Console Manager for each of the directlineMCI VFP 504 components. It also runs the DEC Polycenter Performance Analyzer software. The performance analyzer software collects and analyzes data from the 8200s for tuning purposes.
[3431] 3. Detail
[3432]FIG. 47 shows the production installation of the VFP 504 at the production site. Notes about FIG. 47 and its relationship to FIG. 46: The DEC Alpha 8200s 536 are in a failover configuration. The center rack is a shared disk array.
[3433] The TI MultiServe 4000 560 is actually compound of four separate media servers in a single cabinet. The diagrams after this one show each "quadrant" (one of the four media servers in a MultiServe 4000) as a separate entity. Four each of the 16 FGD T1s are connected to each quadrant.
[3434] The AlphaStation 200 workstation 564 and the terminal servers are used to provide console and system management. The Cabletron hubs 562 provide the network between the media servers 560 and the executive servers 536.
[3435] The Bay Networks hubs 566 provide the network between the VFP 504 and the network routers 569.
[3436] a) Internal Hardware Network
[3437]FIGS. 48A and 48B show the VFP internal hardware/network architecture:
[3438] General notes about FIGS. 47-49:
[3439] The left DEC 8200 machine 536 is shown with all of its ATM and FDDI connections 570 drawn in. The right DEC 8200 is shown with its Ethernet connections 572 drawn in. In actual deployment, both machines have all of the ATM, FDDI, token ring, and Ethernet connections 570 and 572 shown. The Cabletron hubs 562 show fewer connections into ports than actually occur because each 8200 536 is drawn with only half its network connectivity. Also, only one of the four media servers 560 is shown connected to the Ethernet ports. In fact, there is a transceiver and two Ethernet connects for each media server.
[3440] The Bay Hubs 566 are not shown in FIG. 48. They are shown in FIG. 49, directlineMCI VFP External LAN Network Connectivity.
[3441] Starting from the top of FIG. 48 of the DEC 8200s 536: The top unit contains three 4GB drives 574 for operating system, swap, etc. The system CD drive 576 is also located here. This unit is controlled by the Single-Ended Small Computer Systems Interface (SCSI) ("SES" on the diagram) interface 578 from the main system 579.
[3442] The tape stacker 580 is a 140GB tape unit with a single drive and a 10 tape stack. This unit is controlled from a Fast-Wide SCSI ("FWS" on the diagram) interface 582 from the main system 579.
[3443] The main system unit 579 utilizes three of five available slots. Slot 1 has the main CPU card 584. This card has one 300MHz CPU and can be upgraded to two CPUs. Slot 2 has a 512 MB memory card 586. This card can be upgraded to 2GB, or another memory card can be added. System maximum memory is 4 GB.
[3444] Slots 3 and 4 are empty, but may be used for additional CPU, memory, or I/O boards. Slot 5 has the main I/O card 588. This card has eight I/O interfaces:
[3445] One Fast-Wide SCSI interface 582 controls the tape stacker.
[3446] Two Fast-Wide SCSI interfaces 590-592 are unused.
[3447] The Single-Ended SCSI interface 578 controls the local system drives.
[3448] The FDDI interface 594 connects to one of the hubs.
[3449] The PCI slot 596 connects to a PCI expansion chassis 598.
[3450] One port is a 10baseT Ethernet card 600 that is connected to the corresponding card in the other 8200 536 via a private thinnet Ethernet. This network is required for one of the system failover heartbeats.
[3451] An embodiment utilizes nine of the ten available slots in the PCI/EISA expansion chassis 598. Slots 1 and 2 have disk adapters 602. Each disk adapter 602 is connected to a RAID disk controller 604 that has another disk controller 604 (on the other machine) chained, which in turn is connected to a disk controller 604 on that machine. Thus, each of the 8200 machines 536 has two disk controllers 604 attached off of each disk adapter 602. This is the primary clustering mechanism, since either machine can control all of the disks located in FIG. 48 beneath the PCI chassis 598. Slot 3 has a Prestoserve board 606. This is a Network File Server (NFS) accelerator.
[3452] Slot 4 has an FDDI board 608. This FDDI connection is made to the hub other than the FDDI connection made from main slot 5 above.
[3453] Slots 5 and 6 have ATM boards 610. It has a 10baseT Ethernet card 612 that is connected to the corresponding card in the other 8200 536 via a private thinnet Ethernet. This network is required for one of the system failover heartbeats. Slot 10 is empty.
[3454] The two units beneath the PCI chassis are Redundant Array of Inexpensive Disks (RAID) disk controllers 604. Each disk controller 604 is on a SCSI chain with two disk controllers 604 in the middle and a disk adapter 602 (one per machine) on each end. Thus there are two chains, each with two disk controllers 604 and two disk adapters 602. This is the connectivity to the main system 579. Each disk controller 604 supports six single-ended SCSI chains. In this configuration, each of the two chains has one disk controller with two SES connections, and one disk controller with three connections. Each chain has five sets 614 (or "drawers") of disk drives as pictured in the center rack. Note the redundant power supply in the drawer with the RAID Disk Controller.
[3455] The Cabletron MMAC+ hubs 562 (FIG. 47) are configured in a redundant pair. Both the 8200s 536 and the TI media servers 560 connect to both hubs 562, and ahe two hubs 562 are also connected to each other. Starting from the left side of the hubs: The FDDI concentrator card 616 provides an eight port FDDI ring. Each 8200 has one connection into the FDDI card 616 on each hub 562. The 24 port Ethernet card 618 provides connectivity to the TI media servers 560. Each media server 560 connects into one Ethernet port 618 on each hub. There are eight empty slots 620 in each hub which can be used for additional FDDI, ATM, or Ethernet expansion. There are four TI media servers 560 mounted in a single rack called a "MultiServe 4000". Each media server in the rack is identical. Starting from the top unit, and then proceeding left to right for the main slots: The top unit 622 is a drawer that contains two 1GB disk drives, and a removable/hot-insertable tape drive. There are two tape drives that can be shared among the four media servers. The left seven boards 624 labeled "DSP xxx" are TI MPB boards which can each support six incoming or fifteen outgoing channels, as labeled. These boards 624 are grouped together into three sets. There is a right group of three boards, a middle group of three boards, and a single board on the left. Each group has one T1. The T1 terminates at the interface marked "TiM". This is the master T1 interface. T1 channels may be shared by the set of boards delimited by the master/slave T1 boards, and chained together by the bridge modules. The rightmost board 626 is the main CPU/IO board. This board supports an SCSI interface 628 to the disk drawer, an Ethernet connection 630 to a special transceiver 632, and a serial port for the console (not shown).
[3456] The transceiver 632 to the right of the CPU/10 board connects to Ethernet ports on each of the two main hubs 562. The transceiver senses if one of its Ethernet connections has failed, and routes traffic to the other port.
[3457] b) External Hardware/Network Connections
[3458]FIGS. 49A and 49B show the hardware and network connections from the VFP 504 to the external network. Notes about FIG. 49: Each 8200 536 is connected onto the ISN token ring 640 through the Bay Hubs for DDS access over SNA and BDR access over IP. A pair of terminal servers 642 has a connection to the console port of each machine and hub. A DEC AlphaStation 200 564 runs console manager software to access the ports connected to the terminal servers 642. The DECNIS routers are all on an FDDI ring 568 (FIG. 46), connected between the Bay Hubs 566 and the two DEC 8200s 536.
[3459] The Bay Hubs 566 connect the VFP system 504 to the external network through the seven routers 644 shown.
[3460] E. Voice Distribution Detailed Architecture
[3461] 1. Overview
[3462] Voice Distribution refers to the portion of the architecture in which the NAS 546 (FIG. 45) reads and writes the subscriber's ad hoc prompts across the LAN or WAN from/to the VFP 504 using the NFS protocol.
[3463] 2. Rationale
[3464] In one embodiment, voice distribution is implemented by placing a server at each ISN site and replicating the data via complex batch processes from each server to every other server.
[3465] The "Large Object Management" (LOM) project defines a network-based approach. It was decided to use the directlineMCI VFP 504 as the network- based central object store for the NAS 546 to read and write customer prompts.
[3466]FIG. 50 shows a network architecture to support Voice distribution traffic in accordance with a preferred embodiment. FIG. 51 depicts a configuration of the Data Management Zone 5105 of the present invention. The Data Management Zone (DMZ) is a firewall between Internet dial-1n platforms (although not the actual Internet itself) and the ISN production networks. Its purpose is to provide dial-1n access to data for ISN customers while maintaining security for the ISN network as well as privacy and integrity of customer data in a production ISN network.
[3467] The DMZ permits a customer to receive periodically generated data, such as DDS data down feeds from a mainframe database. Such data is periodically extracted from the database and placed in a user account directory on a secure File Transfer Protocol (FTP) host for subsequent retrieval by a customer.
[3468] Data access for customers is through dedicated ports at dial-1n gateways, which are owned, operated and maintained by the Internet provider. Dial-1n user authentication is through the use one of time passwords via secure identification cards, as is more fully described below. The cards are distributed and administered by Internet provider personnel.
[3469] The DMZ provides a screened subnet firewall that uses a pa-ket filtering router to screen traffic from the outside unsecured network and the internal private network. Only selected packets are authorized through the router, and other packets are blocked. The use of multiple firewalling techniques ensures that no single point of failure or error in DMZ configuration puts the ISN production network at risk.
[3470] The DMZ 5105 is intended to conform to several security standards. First, individuals who are not authorized employees cannot be allowed access to internal production networks. Therefore IP connectivity through the gateway is not allowed. Second, access and use of DMZ services is restricted to authenticated and authorized users for specific purposes. Therefore all other utilities and services normally found on a general purpose machine are disabled. Third, use of DMZ services and facilities must be carefully monitored to detect problems encountered by authorized users and to detect potentially fraudulent activity.
[3471] The centerpiece of the DMZ is the DMZ Bastion host 5110. Bastion host 5110 runs an FTP server daemon that implements a modified FTP protocol, as will be described in further detail below. Bastion host 5110 is a highly secured machine used as the interface to the outside world. Bastion host 5110 allows only restricted access from the outside world. It typically acts as an application-level gateway to interior hosts in ISN 5115, to which it provides access via proxy services. Generally, critical information is not placed on Bastion host 5110, so that, even if the host is compromised, no access is made to critical data without additional integrity compromise at the ISN 5115.
[3472] Bastion host 5110 is connected to both interior and exterior users as shown in FIG. 52A. Bastion host 5115 may be a UNIX-based computer such as an IBM RS/6000 model 580 running the AIX operating system.
[3473] An interior user is a user connected to the ISN production token ring 5115. Token ring 5115 is connected to an interior packet filter 5120 such as a Cisco model 4500 modular router. Packet filter 5120 is connected to token ring LAN 5125, which in turn is connected to bastion host 5110. Token ring LAN 5125 is a dedicated token ring that is isolated from all components other than bastion host 5110 and interior packet filter 5120, thereby preventing any access to bastion host 5110 through token ring LAN 5125 except as allowed by packet filter 5120.
[3474] Exterior users connect through exterior packet filter 5130, such as a Cisco model 4500 modular router. Packet filter 5130 is connected to bastion host 5110 through an isolated Ethernet LAN segment 5135. Ethernet LAN segment 5135 is a dedicated segment that is isolated from all components other than bastion host 5110 and exterior packet filter 5130. Because of the configuration, no user can access bastion host 5110 except through interior packet filter 5120 or exterior packet filter 5130.
[3475]FIG. 51 depicts the DMZ 5105 in connection with dial-in environment 5205. In dial-in environment 5205, the customer PC 5210 is connected to public switched telephone network (PSTN) 5220 through the use of modem 5215. Modem bank 5230 assigns a modem to answer incoming calls from PSTN 5220. Modem bank 5230 comprises a set of high-speed modems 5233 such as U.S Robotics V.34 Kbps modems. Incoming calls are authenticated by authentication server 5235. Authentication server 5235 may be implemented using a server such as the Radius/Keystone server running on a Sun Sparcstation model 20.
[3476] The Bastion host 5110 resides within a firewall, but is logically outside both the ISN 5115 and the gateway site 5205.
[3477] Following authentication, the selected modem 5233 is connected to incoming call router 5240 using Point-to-Point Protocol (PPP). PPP is a protocol that provides a standard method of transporting multi-protocol datagrams over point-to-point links. PPP is designed for simple links that transport packets between two peers. These links provide full-duplex simultaneous bidirectional operation, and are assumed to deliver packets in order. PPP provides a common solution for easy connection of a wide variety of hosts, bridges and routers. PPP is fully described in RFC 1661: The Point-to-Point Protocol (PPP), W. Simpson, Ed. (1994) ("RFC 1661"), the disclosure of which is hereby incorporated by reference.
[3478] Incoming call router 5240 selectively routes incoming requests to the exterior packet filter 5130 of DMZ 5105 over a communications link such as T1 line 5250, which is connected to exterior packet filter 5130 via a channel service unit (not shown). Incoming call router 5240 may be implemented using, for example, a Cisco 7000 series multiprotocol router. Incoming call router 5240 is optionally connected to Internet 5280. However, router 5240 is configured to block traffic from Internet 5280 to Exterior packet filter 5130, and to block traffic from exterior packet filter 5130 to Internet 5280, thereby disallowing access to DMZ 5105 from Internet 5280.
[3479] Bastion host 5110 runs a File Transfer Protocol (FTP) server daemon that implements a modified FTP protocol based on release 2.2 of the wu-ftpd FTP daemon, from Washington University. Except as noted herein, the FTP protocol is compliant with RFC 765: File Transfer Protocol, by J. Postel (June 1980) ("RFC 765"), the disclosure of which is hereby incorporated by reference. RFC 765 describes a known protocol for transmission of files using a TCP/IP-based telnet connection, in which the server responds to user-initiated commands to send or receive files, or to provide status information. The DMZ FTP implementation excludes the send command which is used to send a file from a remote user to an FTP server, and any other FTP command that transfers files to the FTP host. A restricted subset of commands including the get (or recv), help, is, and quit commands are supported.
[3480] The get command is used to transfer a file from host server 5110 to remote user 5210. The recv command is a synonym for get. The help command provides terse online documentation for the commands supported by host server 5110. The is command provides a list of the files in the current directory of the server, or of a directory specified by the user. The quit command terminates an FTP session. Optionally, the cd command, which specifies a named directory as the current directory, and the pwd command, to display the name of the current directory, may be implemented.
[3481] By disallowing send and other commands that transfer files to the server, a potential intruder is prevented from transferring a "Trojan horse" type of computer program that may be used to compromise system security. As an additional benefit, the unidirectional data flow prevents a user from inadvertently deleting or overwriting one of his files resident on the Bastion server.
[3482] When the FTP daemon initiates a user session, it uses the UNIX chroot(2) service to specify the root of the user's directory tree as the apparent root of the filesystem that the user sees. This restricts the user from visibility to UNIX system directories such as/etc and/bin, and from visibility to other users' directories, while permitting the desired visibility and access to the files within the user's own directory tree. To further assure a secured environment, the FTP daemon executes at the user-id ("uid") of the user level, rather than as root, and allows access only to authorized users communicating from a set of predetermined IP addresses known to be authorized. In particular, the standard non-authenticated accounts of anonymous and guest are disabled.
[3483] In order to further secure Bastion server 5110, a number of daemons that are ordinarily started by the UNIX Internet server process inetd are disabled. The disabled daemons are those that are either not needed for Bastion server operation, or that are known to have security exposures. These daemons include rcp, rlogin, rlogiud, rsh, rshd, tftp, and tftpd These daemons are disabled by removing or commenting out their entries in the AIX/etc/inetd.conf file. The/etc/inetd.conf file provides a list of servers that are invoked by inetd when it receives an Internet request over a socket. By removing or commenting out the corresponding entry, the daemon is prevented from executing in response to a received request.
[3484] As a further assurance of security a number of daemons and utilities are disallowed from execution by changing their associated file permissions to mark them as non-executable (e.g., having a file mode of 000). This is performed by a DMZ Utility Disabler (DUD) routine that executes at boot time. The DUD routine marks as non-executable the above-identified files (rcp, rlogin, rlogind, rsh, rshd, tftp, and tftpd), as well as a number of other daemons and utilities not ordinarily invoked by inetd. This set of daemons and utilities includes sendmail, gated, routed, fingerd, rexecd, uucpd, bootpd, and talkd. In addition, DUD disables the telnet and ftp clients to prevent an intruder from executing those clients to access an interior host in the event of a break-in. The telnet and fip clients may be temporarily marked as executable during system maintenance activities.
[3485] Bastion host 5110 has IP forwarding disabled. This ensures that IP traffic cannot cross the DMZ isolated subnet 5115 by using Bastion host 5110 as a router.
[3486] The limited level of ftp service provided by Bastion server 5110 provides a secure ftp session but makes it difficult to perform typical system maintenance. In order to perform system maintenance, maintenance personnel must connect +o Bastion host 5110 from an interior host within ISN 5115 using a telnet client. The FTP client program in Bastion is then changed from non-executable (e.g., 000) to executable (e.g., 400), using the AIX chmod command. Maintenance personnel may then execute the ftp client program to connect to a desired host on ISN 5115. During this procedure, control of transfers is therefore from within Bastion host 5110 via the FTP client program executing within that host, rather than from a client outside of the host. At the end of a maintenance session the FTP session is terminated, and the chmod command is executed again to revert the ftp client program to a non-executable state (e.g., 000), after which the ISN-initiated telnet session may be terminated.
[3487] To provide logging, Bastion server 5110 implements a TCP daemon wrapper, such as the TCPwrappers suite from Wietse Venema. The TCP wrapper directs inetd to run a small wrapper program rather than the named daemon. The wrapper program logs the client host name or address and performs some additional checks, then executes the desired server program on behalf of inetd. After termination of the server program, the wrapper is removed from memory. The wrapper programs have no interaction with the client user or with the client process, and do not interact with the server application. This provides two major advantages. First, the wrappers are application-independent, so that the same program can protect many kinds of network services. Second, the lack of interaction means that the wrappers are invisible from outside.
[3488] The wrapper programs are active only when the initial contact between client and server is established. Therefore, there is no added overhead in the client-server session after the wrapper has performed its logging functions. The wrapper programs send their logging information to the syslog daemon, syslogd. The disposition of the wrapper logs is determined by the syslog configuration file, usually/etc/syslog.conf.
[3489] Dial-in access is provided through dial-in environment 5105. The use of authentication server 5235 provides for authentication of users to prevent access from users that are not authorized to access the DMZ. The authentication method implemented uses a one-time password scheme. All internal systems and network elements are protected with one-time password generator token cards, such as the SecurID secure identification token cards produced by Security Dynamics, using an internally developed authentication client/server mechanism called Keystone. Keystone clients are installed on each element that receive authentication requests from users. Those requests are then securely submitted to the Keystone Servers deployed throughout the network.
[3490] Each user is assigned a credit card sized secure identification card with a liquid crystal display on the front. The display displays a pseudo-randomly generated six-digit number that changes every 60 seconds. For an employee to gain access to a Keystone protected system, the user must enter their individually assigned PIN number followed by the number currently displayed on the secure identification card. Such authentication prevents unauthorized access that employ the use of programs that attempt to "sniff" or intercept passwords, or Trojan horse programs designed to capture passwords from users.
[3491] Authentication information collected by the Keystone clients is encrypted with an RSA and DES encryption key, and is dispatched to one of many Keystone Servers. The Keystone Server evaluates the information to verify the user's PIN and the access code that should be displayed on that user's card at that moment. After the system verifies that both factors for that user were entered correctly, the authorized user is granted access to the system, or resource requested.
[3492] In order to assure security from the point of entry of the external network, no external gateway machine has a general access account and all provide controlled access. Each gateway machine ensures that all gateway services generate logging information, and each external gateway machine maintains an audit trail of connections to the gateway. All of the external gateway machines have all non-essential services disconnected.
[3493] The authentication server 5235 serves as a front end to all remote access dial up, and is programmed to disallow pass-through. All network authentication mechanisms provide for logging of unsuccessful access attempts. Preferably, the logs generated are reviewed daily by designated security personnel.
[3494]FIG. 53 depicts a flow diagram showing the fax tone detection methodology. In step 5305, the fax tone detection system allocates a null linked-list; that is, a linked list having no entries. In step 5310, the fax tone detection system starts the asynchronous routine auCheckForFaxAsync 5315. The auCheckForFaxAsync routine 5315 is an asynchronous program that executes concurrently with the main line program, rather than synchronously returning control to the calling program. The auCheckForFax routine evaluates the tone of the incoming call to see whether the call is originated by a facsimile machine, and generates an auCheckForFax response 5318 if and when a facsimile tone is detected.
[3495] After starting auCheckForFaxAsync routine 5315, control proceeds to step 5320. In step 5320, the fax tone detection system adds an entry to the linked list allocated in step 5305. The added entry represents a unique identifier associated with the message being processed. In step 5330, the fax tone detection system starts the asynchronous routine auPlayFileAsync 5335. The auPlayFileAsync routine 5335 is an asynchronous program that executes concurrently with the main line program, rather than synchronously returning control to the calling program. The auPlayFileAsync routine 5335 accesses previously stored digitally recorded sound files and plays them to the originating caller. The sound files played may be used, for example, to instruct the originating caller on sequences of key presses that may be used to perform particular functions, e.g., to record a message, to retrieve a list of previously recorded messages, etc.
[3496] In step 5340, the fax tone detection system starts the asynchronous routine auInputDataAsync 5340. The auInputDataAsync routine 5340 is an asynchronous program that executes concurrently with the main line program, rather than synchronously returning control to the calling program. The auInputDataAsync routine 5340 monitors the originating call to detect key presses by the user, in order to invoke the routines to execute the tasks associated with a particular key press sequence.
[3497] As has been noted, the auCheckForFaxAsync routine 5315 executes concurrently with the main program, and generates a auCheckForFax response 5318 if and when a facsimile tone is detected. In step 5350, the fax tone detection system checks to see whether an auCheckForFax response 5318 response has been received. If a response has been received, this indicates that the originating call is a facsimile transmission, and the fax tone detection system extends the incoming call to Voice/Fax processor (VFP) 5380. If no auCheckForFax response 5318 is received within a predetermined time (e.g., 7 seconds), the fax tone detection system concludes that the originator of the call is not a facsimile device, and terminates the auCheckForFaxAsync routine 5315. In an implementation, it may be preferable to implement this check through an asynchronous interruption-handling process. In such an implementation, an execution-time routine may be set up to gain control when an auCleckForFax response 5318 event occurs. This may be implemented using, for example, the C++ catch construct to define an exception handler to handle an auCheckForFax response 5318 event.
[3498] Following the decision in step 5350, the fax tone detection system in step 5360 waits for the next incoming call.
[3499]FIGS. 54A through 54E depict a flow diagram showing the VFP Completion process for fax and voice mailboxes. As depicted in FIG. 54A, the VFP completion routine in step 5401 searches the database for a record corresponding to the addressed mailbox. In step 5405, the VFP completion routine checks to see if a mailbox record was successfully retrieved. If no mailbox record was found, in step 5407, the VFP completion routine generates a VCS alarm indicating that the desired mailbox record was not found. Because the mailbox record was not found, the VFP completion processor will be unable to test the attributes of the mailbox address. However, regardless of whether the mailbox record is found, control proceeds to step 5409. In step 5409, the VFP completion processor tests the contents of the mailbox record, if any, to determine whether the addressed mailbox is full. If the addressed mailbox is full, in step 5410, the VFP completion routine plays an error message indicating that the addressed mailbox is at capacity and is unable to store additional messages, and exits in step 5412.
[3500] In step 5414, the VFP completion processor obtains the mode of the VFP call. The mode is derived from the dial string provided by the originating caller, and is stored in the enCurrentNum field of the pstCalllState structure. The dial string has the following format:
[3501] The mode has one of the following values:
[3502] In step 5416, the VFP completion processor retrieves the route number associated with the addressed mailbox from the database. In step 5418, the route number is passed to the SIS layer.
[3503] As depicted in FIG. 54B, execution continues with step 5420. In step 5420, the VFP completion processor initialized an answer supervision flag that is used to determine whether the VFP is accepting transfer of the call. In step 5422, the VFP completion processor calls the SisCollectCall routine to process the call. If the call is unsuccessful, Step 5424 causes the SisCollectCall invocation of step 5422 to be repeated up to a predetermined number of retries.
[3504] In step 5426, the VFP completion processor obtains a predetermined timer expiration value from the otto.cfg file. The timer expiration value is set to the amount of time in which, if an answer is not received, the VFP completion processor may conclude that the VFP is not currently reachable. In step 5428, the VFP completion processor sets the timer according to the value from step 5426. In step 5430, the VFP completion processor check to see whether answer supervision occurred prior to the expiration of the timer set in step 5424. If so, control proceeds to step 5430 to transfer control to the VFP.
[3505]FIG. 54C depicts the operation of transferring control to the VFP in response to an affirmative decision in step 5430. In step 5440, any pending timers set in step 5428 are canceled. In step 5442, the VFP completion processor calls routine sisOnHoldTermo to put the VFP on hold. In step 5444, the VFP completion processor calls routine sisOffl-oldOrig