Applicant(s) hereby rescind any disclaimer of claim scope in the parent, grandparent, great-grandparent, and great-great-grandparent applications (namely U.S. application Ser. No. 13/278,923, U.S. application Ser. No. 12/391,828, U.S. application Ser. No. 11/133,030 and U.S. application Ser. No. 09/475,144) and in the prosecution histories thereof, and hereby advise the US Patent and Trademark Office (USPTO) that the claims in this continuation application may be broader than any claim in the parent, grandparent and great grandparent applications. Accordingly, Applicant(s) notify the USPTO of a need to re-visit the disclaimer of claim scope in the parent, grandparent and great grandparent applications, and to further re-visit all prior art cited in the parent, grandparent and great grandparent applications, including but not limited to cited references over which any disclaimer of claim scope was made in the parent, grandparent and great grandparent applications, and in the prosecution histories thereof. See Hakim v. Cannon Avent Group, PLC, 479 F.3d 1313 (Fed. Cir. 2007). Moreover, any disclaimer made in the current application should not be read into or against the parent, grandparent and great grandparent.
The present invention relates to communication between users in diverse communication systems, and more particularly, to providing a broadband communication system including an Internet Protocol Telephony Network and public switched telephone network.
Present day telephony voice networks, have a network built around circuit switches, end offices, a toll network, tandem switches, and twisted wires. These voice networks are referred to as a public switched telephone network (PSTN) or plain old telephone service (POTS). Due to bandwidth limitations of plain old telephone service (POTS), there is an inherent inability to efficiently integrate multiple types of media such as telephony, data communication for personal computers (PC), and television (TV) broadcasts. Accordingly, a new broadband architecture is required. This new architecture gives rise to a new array of user services.
Conventional call forwarding only allows a call to be forwarded to a single predetermined number. This is inflexible and outdated considering the increasing mobility of subscribers today. There is a need for a more flexible and useful call forwarding system that allows call forwarding to a variety of numbers depending upon different dynamic factors such as time, date, etc. There is also a need for call forwarding features in the new IP telephone architecture.
Aspects of the invention include to providing broadband access capabilities or enhanced services for use in conjunction with a packetized network such as an Internet Protocol (IP) based system infrastructure.
Other aspects of the invention include providing one or more of the following either individually, or in any combination or subcombination:
It is an object of the present invention to overcome the deficiencies cited above by allowing a subscriber to customize a call forwarding profile for controlling the forwarding of calls over an Internet Protocol Telephony Network.
According to one embodiment of the invention, a method and system for providing call forwarding in an IP telephone network is disclosed. First, when a telephone number for a first telephone from a second telephone is dialed, the call is routing to a call manager. Call setup procedures with a BRG responsible for the first telephone are then initiated. The BRG then checks stored call forwarding profiles to determine whether there is an active call forwarding profile for the first telephone. The call is connected to the first telephone if an active call forwarding profile is not found. However, if an active call forwarding profile is found, the call forwarding information is sent to the call manager. The call is routed to at least a third telephone based on the call forwarding information.
Although the invention has been defined using the appended claims, these claims are exemplary and limiting to the extent that the invention is meant to include one or more elements from the apparatus and methods described herein and in the applications incorporated by reference in any combination or subcombination. Accordingly, there are any number of alternative combinations for defining the invention, which incorporate one or more elements from the specification (including the drawings, claims, and applications incorporated by reference) in any combinations or subcombinations.
A new system is provided for broadband access and applications. Unless otherwise indicated by the appended claims, the present invention is not limited to the preferred embodiments described in this section but is applicable to other integrated multimedia communication systems.
Referring to
Again referring to
In
In exemplary embodiments, the broadband residential gateway 300 may function to couple devices within the customer premise equipment 102 to the rest of the broadband network 1 using any suitable broadband communication mechanism. In the embodiment shown in
The broadband network 1 may include any number of interconnected head-end hubs 115, IP networks 120, and/or ATM networks 185. Further, the IP network 120 and/or ATM network 185 may be connected to one or more other networks and devices such as:
The IP network 120 and/or ATM network 185 may include one or more routers and/or other devices to route, for example, telephony calls, multimedia calls, signaling messages, administrative messages, programming messages and/or computer data between the various devices in the broadband network 1 such as the head-end hub 115, the public switched telephone network 160, the private branch exchange (PBX) 146, as well as the other devices discussed above. In preferred embodiments, the information traveling in the IP network 120 may be packetized and formatted in accordance with one of the Internet protocols. The IP network 120 may also include gateways to interface with the various other networks and/or devices. For example, the gateways may be distributed at the edge of the IP network where the IP network interfaces with one of the other devices or networks. Alternatively, the gateways interfacing the IP central station 200 to, for example, the Internet 180, public switched telephone network (PSTN) 160, signaling system 7 (SS7) 170, wireless networks 144, ATM/frame/cell relay networks 185 may be provided in the IP central station 200, or in both the IP network 120 and the IP central station 200, and/or partially distributed between the IP network 120 and the IP central station 200. Where the gateways are separated by an IP network 200, an appropriate transport protocol may be utilized to logically connect the IP central station 200 to the particular gateway.
The IP central station(s) 200 may be connected to, for example, one or more FP networks 120, ATM networks 185, secure management data networks 190, and/or administration centers 155. The IP central station 200 may be variously configured to include one or more servers and/or one or more gateways. In exemplary embodiments, the servers and gateways provide the necessary intelligence and traffic management capabilities to enable information, e.g., IP telephony signals, to travel through the broadband network 1. For example, the IP central station 200 may be configured to manage voice information transfer from the public switched telephone network 160, through the IP network 120, and into and out of one or more devices such as those connected to a broadband residential gateway 300. The IP central station may be configured to store various control and system information such as location, address, and/or configurations of one or more broadband residential gateways 300, as well as other routing and call set-up information.
In exemplary embodiments, one or more administration centers 155 may be connected to the IP network 120 and provide billing and local directory number portability administration. The local number portability may be handled by one or more Local Service Management System (LSMS) which may be included in the administration center 155 and/or in the IP central station 200. Further, the Secure Management Data Network 190 may also include a mechanism for transferring various information such as billing, call tracking, and/or customer service provisioning. Various existing systems may be utilized to provide this information such as existing billing systems (OSS) 195 and/or one or more network operations center (NOC). The network operations centers may be included in the administration center 155, the EP central station 200, and/or the billing system 195. The network operations center (NOC) may be variously configured to include a translation server to allow communications with the various disparate entities (e.g., legacy systems) in the broadband network 1.
The IP network 120 and/or the ATM network 185 illustrated in
The IP central station 200 may be configured to provide connectivity for the broadband residential gateway 300 to the Internet 180 (e.g., World Wide Web (www)), as well as connectivity to other external networks such as public switched telephone network 160 and signaling system 7 (SS7) 170 for end-to-end voice, multimedia, and data applications, for example voice over IP telephony. IP packets traveling through the IP network provide for priority so that, for example, voice packets are given priority over data packets to maintain certain VoIP telephony QoS requirements and a leased line concept for packet traffic which may have an even higher priority. However, the system is sufficiently flexible so that the priority can be dynamically altered according to customer preferences, variable billing rates, traffic patterns, and/or congestion.
Referring to
Again referring now to
The IP central station 200 may also include, for example, one or more of the following gateways: a element management gateway (EMG) 238, an accounting gateway (AG) 240, an Internet (Boarder) gateway (IG) 236, a signaling system 7 (SS7)) gateway (SG) 234, a voice gateway (VG) 232, and/or a multimedia gateway (MG) 230. The IP central station 200 may utilize one or more of these gateways to provide centralized system intelligence and control of voice and/or data IP packets.
In exemplary embodiments, the dynamic host control protocol server and domain name service server 214 may operate to dynamically assign IP addresses devices in the customer premise equipment 102. Where a dynamic IP assignment scheme is used, the customer premises equipment may be provided with one or a plurality of dynamic IP assignment when activated initially, and/or at the initiation of each active secession. Where an IP address is assigned when the device is initially activated, it may be desirable to assign a single IP address to a single broadband residential gateway and assign a port address to devices connected to the broadband residential gateway 300. In other embodiments, an individual IP address may be assigned to each device coupled to the broadband residential gateway 300. For example, the broadband residential gateway may include and/or be coupled to one or more cable modems, IP phones, plain old telephone system phones, computers, wireless devices, CATV converters, video phones, and/or other devices which each may be assigned a unique static and/or dynamic IP address and/or a port of a one of these IP addresses. The particular protocol for allocating IP addresses and/or ports may be specified using protocols defined in the dynamic host control protocol server 214. In exemplary embodiments, the dynamic host control protocol and DN server 214 may be configured to assign available IP addresses from address pools based, for example, on the identity or type of requesting device, the amount of use expected for the requesting device, and/or predefined assignment protocols defined in the dynamic host control protocol and DN server 214. In centralized embodiments, it may be desirable to configure the call manager (CM) 218 to provide sufficient information such that the domain name service server 214 can distinguish between static IP devices, dynamic IP devices, registered devices, unregistered devices, and registered devices that have been assigned to a particular class of service e.g., data vs. telephony, un-provisioned, vs. provisioned, etc.
The trivial file transfer protocol (TFTP) server 214 may be configured to transfer certain information to/from one or more broadband residential gateways 300. In exemplary embodiments, the trivial file transfer protocol server provides Data Over Cable Service Interface Specifications (DOCSIS) configuration information containing QoS parameters and other information required for the broadband residential gateway 300 to operate optimally.
The time-of-day (TOD) server 212 may include a suitable facility for maintaining a real time clock such as an RFC868-compliant time server. In exemplary embodiments, the time-of-day server 212 provides system messages and/or responses to system inquiries containing a coordinated time, e.g., universal coordinated time (UCT). The universal coordinated time may be used by any of the servers and/or devices in the broadband network 1. For example, the broadband residential gateway 300 may use the universal coordinated time to calculate the local time for time-stamping error logs.
The system management (SM) server 216 may include responsibility for the overall operational state and functioning of components the broadband network 1, either alone, or in combination with other system management servers 216. The system management (SM) server 216 may be variously configured to provide monitoring and administrative functions for devices within the broadband network 1. For example, the system management server 216 may be configured to provide management of various database functions, memory buffer functions, and software utility functions within the broadband network 1. Software management includes, for example, version control, generic control, and/or module control.
The least cost server (LCS) 255 may be variously configured to enable the system to determine the least cost routing of telephone and data transmission throughout the network. The least cost server 255 may also provide one or more broadband residential gateway users capability to select between, for example, cost and Quality of Service (QoS).
The announcement service (AS) server 220 may be variously configured. In exemplary embodiments, it may store and send announcements to specified destinations and/or all destinations based on instructions received by, for example, the call manager (CM) server 218. The announcement server 220 receives, for example, Media Gateway Control Protocol (MGCP) or later signaling (e.g., H.GCP—an ITU standard Gateway Control Protocol) control messages from the call manager 218, and sends announcements to one or more voice gateways (VG) 232 and/or the one or more broadband residential gateway 300 (e.g., using Real Time Protocol (RTP) packets). The announcement server 220 may send an announcement once, a predetermined number of times, or in a continuous loop. The announcement server 220 may detect when a phone or other device has been taken off-hook and play an advertisement or other announcement to the user. Where a user has signed-up for an advertising plan whereby phone rates are reduced in return for advertising revenue generated by the advertisements, the announcement server 220 may be utilized to track the number of individuals with a particular income, age, or other profile which hear the advertisement. The announcement server 220 may respond to requests from individual system devices such as one of the broadband residential gateways 300 and/or under control of, for example, the call manager 218. Where the announcement server is under control of the call manager 218, the call manager may be configured to control various operating parameters of the announcement server. For example, the call manager 218 may request that certain announcements are sent once, a specified number of times, or in a continuous loop.
In still further embodiments, announcements may be generated elsewhere in the broadband network 1, stored as files, and distributed to one or more announcement servers via a file transfer protocol or resource such as the trivial file server 214 using one or more file transfer protocols. In many embodiments, it is desirable to store announcements in an appropriate encoding format (e.g., G.711 or G.729) within the Announcement Server. The announcement may have an audio component and/or a audio/video component. The audio/video component may be stored using a combination of an encoding format (e.g., G.711) and/or a standard file format such as wave (WAV), MPEG, and other suitable formats.
In one exemplary method of operation, a user picks up a telephone which sends a signal to the call manager 218. Subsequently, the call manager 218 may establish a connection to the announcement server 220 and play one or more pre-recorded and/or predetermined announcement (hypertext and/or audio). Signaling tones such as a busy signal may be played by the broadband residential gateway 300 or the call manager 218, but Special Information Tones (SIT) and/or messages may also be included as part of an announcement file. In this way, the user experience is enhanced such that the user receives a busy message and/or hypertext announcement providing one of several options for contacting the called party. The announcement server 220 may have information entered by a user using, for example, a broadband residential gateway to provide additional information to the called party. The additional information may include the ability to leave a message, type-in a chat note, page the called party, barge-in on the call, and/or other user or system defined call handling capabilities.
The announcement server 220 may also be programmed with various system messages such as an announcement indicating that a number dialed is incorrect or that the call did not go through as dialed, that the lines are busy, that all lines between two countries are currently busy, that the called party has changed numbers, that the called parties phone has been disconnected, that one or more system errors have occurred, and/or other announcement messages.
The call manager (CM) 218 may be variously configured. In exemplary embodiments, the call manager 218 provides a centralized call control center for supporting call set-up and tear-down in the broadband network 1. The call manager 218 may be configured to include trunk and line information maintenance, call state maintenance for the duration of a call, and/or user service features execution. The call manager 218 may also provide for call processing functions such as a standardized call model for processing the various voice connections such as voice over IP calls. In exemplary embodiments, a standardized “open” call model may be utilized which supports standardized application programming interfaces (APIs) to provide transport services and other user functions such as calling cards. An open application programming interface and call set-up interface in the call manager will enable third party applications to be loaded into the call manager 218 and broadband residential gateway 300. This will facilitate the development of third party applications for enhancing the functionality of components in the broadband network 1. For example, third parties and other equipment vendors may manufacture various broadband residential gateways 300 for use in the broadband network 1 by writing applications to support the open call model of the call manager 218. The call manager 218 and/or broadband residential gateway 300 may also be configured to execute and/or accept commands form a standardized scripting language which may generate instructions for the call manager 218 and/or broadband residential gateway 300 to execute various functions. The scripting functionality may include the ability to execute an entire call model including interfaces to the signaling system 7 (SS7) 170, public switched telephone network 160, IP network 120, ATM/frame/cell relay network 185, and/or other functions within, for example, IP central station 200 such as the multimedia server 222, announcement server 220, system management server 216, conference server 224, time of day server 212, least cost server 255, and/or domain name server 214.
The call manager 218 may also be configured to maintain the call states for each call it handles (e.g., a voice over IP call) and respond to system events created by, for example, the multimedia gateway control protocol (MGCP) messages and/or integrated services digital network user part (ISUP) messages for signaling system 7 (SS7) protocol that may occur during the processing of a call. Exemplary events handled by the call manager 218 include call state changes, call feature changes/call feature triggering events, changes in the status of lines and trunks, and/or error conditions. Further, the call manager 218 may interact with devices connected to a single circuit on the public switched telephone network 160 and/or a device connected to a port of the broadband residential gateway 300. In this manner, new devices may be added to the infrastructure and operate using the open call model contained in the call manager 218.
The call manager 218 may also include storage for subscriber and network configuration, a cache server for faster access to frequently used data, a routing engine for selecting an appropriate routing algorithm (e.g., least cost routing), and/or a service broker which provides the data and logic for specific services. In addition, the call manager 218 may include an authentication (AC) server 245 that provides authentication of various devices, objects, packets and users in the integrated multimedia system. In this manner, a user may verify the identity of the calling or called party.
The call manager 218 may interact with the signaling gateway (SG) 234, the accounting gateway (AG) 240, the element management gateway (EMG) 238, the voice gateway (VG) 232, and the multimedia gateway (MG) 230 using any suitable protocol such as IP and an interconnection mechanism such as the central router 210. In one preferred embodiment, the call manager 218 may be configured to utilize signaling messages such as: a) ISUP messages over Common Object Broker Architecture (COBRA) interface to and/or from signaling gateway 234, b) MGCP, SIP—simple internet protocol, H.GCP, and/or other suitable control messages to and/or from the announcement server 220, c) call event records in modified Radius format to the accounting gateway 240, d) Radius (or Enhanced Radius or compatible protocol) control messages to and/or from the voice gateway 232 and/or the broadband residential gateways 300, and e) signaling network management protocol (SNMP) messages to and/or from the element management gateway 238.
The call manager 218 may incorporate one or more databases. For example, the call manager 218 may include database information such as (1) a resources database that provides an identification of what resources are connected to the broadband network 1 and their current state; (2) a trunk/gateway database that indicates which gateway serves what circuits in a trunk; (3) a customer database which indicates whether a call is authorized, identifies what services a line supports and determines whether a telephone number is on or off the integrated IP communication network; (4) a numbering plan/least cost routing database which provides routing information that enables the IP central station 200 to choose the correct trunk as a function of the call number; and (5) a local number portability (LNP) database that indicates the North American Numbering Plan (NANP) and associated prefixes which are open for association with the number portability service; and (6) an address of the service control point (SCP) towards which requests for translating these local portability numbers should be routed.
In exemplary embodiments, the broadband network 1 includes equipment compatible with the COBRA standard. COBRA may be utilized to allow applications from a plurality of vendors to operate with each other. The COBRA standard allows a company, such as AT&T, to build its network using multi-vendor equipment and yet ensure seamless integration and operation. Some of the major areas covered by COBRA v. 2.2 includes: Inter-ORB Bridge Support, General Inter-ORB Protocol (GIOP) support, Internet Inter-ORB Protocol (BOP) support, and Environment Specific Inter-ORB Protocol (ESIOP) support. The call manager 218 may integrate these protocols to facilitate call set-up with diverse equipment. This is advantageous in that equipment from a plurality of vendors may interoperate over the broadband network 1 without modification.
The multimedia server (MS) 222 may be variously configured. For example, one or more multimedia servers may provide support for multimedia messaging service and/or the overall management of multimedia voice and mail messages transmitted across the broadband network 1. The multimedia server may be configured to support e-mail (e.g., html) messages, voice mail (audio) messages, and/or video mail (audio and video) messages. The multimedia messages may include standard pre-configured system messages, advertising messages, and/or user defined messages. In either event, where the messages are stored in a centralized location, the multimedia server may provide such storage. Where the multimedia server 222 provides storage for the multimedia messages, a database may be utilized for indexing, storage, and retrieval of such messages. In exemplary systems, the user may access predetermined ones of these messages. The multimedia server 222 may utilize IP as a method of communicating with other devices across the broadband network 1.
The conference server (CS) 224 may be configured to provide for multiparty conference calls using, for example, IP voice packets during an IP telephony or multimedia session call. The conference server 224 may include specialized software that runs on a computing platform having associated multiplexing and demultiplexing capability for segregating and aggregating user information packets. For example, the conference server may log several calls into a conference session. When information packets are sent from one or more phones, they are aggregated and sent to the other phones on the conference call. The conference server 224 may use any suitable communication protocol such as H.GCP or SIP. The conference server 224 may function to aggregate user information from two or more users onto a single call path. The conference server 224 may include one or more “call-in numbers” and be controlled from any location, e.g., a centralized operator location and/or one or more broadband residential gateways 300. It may be desirable to have the conference server 224 configured such that some callers simply monitor the call without voice interruption while other callers have both voice transmit and receive capabilities. Where a caller is not given the privileges associated with active participation in the call, voice packets from these users are discarded. For example, a CEO may have a conference call with a plurality of financial advisors and invite the press to listen on the call without interruption capabilities.
The gateways in the IP central station 200 may be configured to provide translation of signals to and/or from the various servers in the IP central station 200, the IP network 120, the public switched telephone network 160, the signaling system 7 (SS7) network 170, the Internet 180, and/or the secured management data (SMD) network 190. The gateways typically support one or more of the following group of functions: call processing; signaling system 7 (SS7) connectivity; billing support; OAM&P support; connection to public switched telephone network; control CoS/QoS parameters; and enhanced services.
The voice gateway (VG) 232 may be connected to the public switched telephone network 160 and operate to convert between IP based voice packets and standard public switched telephone network 160 voice traffic. Voice gateway 232 may be configured as multi-frequency (MF) or ISUP gateways on a per-T1 basis. Where multi-frequency (MF) trunks are used, one embodiment utilizes signaling between the call manager 218 and the voice gateway 232 using MGCP, SIP, H.GCP and/or other compatible protocol. Multi-frequency trunks may be compatible with Feature Group D (FGD), Operator Service (OS) Signaling protocol and/or Termination Protocol (TP).
The IP central station 200 may be variously connected to the public switched telephone network. For example, the IP central station 200 may be connected directly to the public switched telephone network using, for example a bearer channel (e.g., a T1 or T3 carrier) and/or interconnected using one or more networks such as an IP network and/or ATM/frame/cell relay network 185. Where a T1 network is utilized, it may be desirable to utilize one or more of ISUP or MF, FGD, and OS to interconnect a service bureau in the public switched telephone network 160. Alternatively, the service bureau in the public switched telephone network 160 may be interconnected using an alternative network arrangement such as an IP network 120 and/or a ATM/frame/cell relay network 185. The service bureau may coordinate with the IP central station 200 in providing operator services, directory services and provisioning for 311, 611, and 711 services. Emergency 911 services may be routed to an E911 tandem switch that has the appropriate databases and interfaces with a Public Safety Answering Position (PSAP). Emergency 911 services may be coordinated by the call manager 218 and/or public switched telephone network based service bureau.
Voice gateway 232 may be router-based and include one or more voice feature cards and/or DSP Module cards to perform voice processing. The voice gateway 232 may optionally include host processors, LAN/WAN ports, Ethernet ports, T1 or E1 telephony interface cards, Voice Feature Cards with DSP Modules providing voice compression transcoding (G.711 and G.729), carrier-quality echo cancellation with 8 ms-32 ms tail length, a de jitter buffer which adapts to delay variations in the network in order to minimize the delay, packet loss concealment that generates concealment frames for lost packets using information from previously received data, and/or tone detection and generation. This function detects Multi-Frequency (MF) tones and generates MF and call processing tones (e.g. dial tone, call-waiting tone etc.).
In exemplary embodiments, the voice gateway 232 may include T1/E1 interfaces with internal Channel Service Units (CSUs). It may also be desirable to configure the voice gateway 232 such that ISUP, MF and Centralized Attendant Services (CAS) trunks are supported with a configuration done on a per T1 basis. Additionally, multi-frequency tones and Centralized Attendant Services may utilize a “robbed bits” communication scheme where bits are “robbed” from sub-frames to transmit in-band signaling. The multi-frequency tones may be converted to and/or from, for example, simple gateway control protocol (SGCP) signal requests and events by the voice gateway 232. For example, multi-frequency tones and/or lower level signaling and timing functions may be translated to and/or from any of the following indications: simple gateway control protocol Notify functions, simple gateway control protocol Notification Requests, Connection requests, Modify Connection requests, off-hook and/or on-hook indications.
An Ethernet interface with a RJ-45 connector may be used to connect the voice gateway 232 to the central router 210 (e.g., Gigabit Switch or High Speed Router (HSR)). The multimedia gateway control protocol may be used as the interface between the voice gateway 232 and the call manager 218. For example, call control, signaling, and multimedia data stream, real time protocol (RTP) connections, IP addresses, UDP ports, codec choice etc, may be configured in any suitable manner such as by using a multimedia gateway control protocol. In exemplary embodiments, audio streams may be passed directly between customer premises equipment 102 using real time protocol connections over, for example, a user datagram protocol (UDP). Thus, the multimedia gateway control protocol may be utilized to request the voice gateway 232 to initiate, cancel, and/or otherwise modify connections in order to set up and tear down RTP media streams. A similar procedure may also be utilized to request continuity tests and results.
In exemplary embodiments, it may be desirable to adapt the IP network to carry signaling system 7 (SS7) Transaction Capabilities Application Part (TCAP) messages over the IP network 120 and/or the ATM/frame/cell relay network 185. The transport of signaling system 7 (SS7) transaction capabilities application part (TCAP) messages over the packet networks allows signaling operations to be supported by multiple connections to the same host, multiple host connections, and distributed processing of call set-up information using, for example, multiple call managers 218 in the broadband network 1. Thus, the IP network 120 and/or ATM/frame/cell relay network may be utilized to interconnect a plurality of ESS switches to transport signaling information, voice, and/or data. In embodiments where the signaling gateway (SG) 234 is configured to support signaling system 7 (SS7) signaling transport using transaction capabilities application part (TCAP) messages, it may be desirable to include a translator for converting between multimedia gateway control protocol (MGCP) messages and transaction capabilities application part (TCAP) messages and/or ISDN User Part (ISUP) messages.
The point where ISUP and TCAP messages are terminated at a signaling system 7 (SS7) signaling gateway is defined as a Service Switching Point (SSP) to the signaling system 7 (SS7) network 170. The call manager 218 may be configured with a standardized Application Programming Interface (API) to allow interaction with the signaling system 7 (SS7) by, for example, sending and/or receiving ISUP and TCAP messages from a service switching point (SSP). Full class 5 signaling system 7 (SS7) functionality may be included in the call manager 218 including the ability to provide all of the information necessary for billing as defined in the GR-246-Bellcore standard. The signaling gateway 234 may be arranged to perform: signaling system 7 (SS7) message handling (message discrimination, message distribution, and message routing); signaling link management (e.g., link activation, deactivation); signaling route management (managing Point Code [PC] route status based on route received management messages such as Transfer Prohibited, Transfer Allowed, Transfer Restricted, etc.); and signaling traffic management (diversion of traffic based on unavailability, availability, restriction of signaling link, route, and Point Code.) The signaling system 7 (SS7) architecture supports the necessary redundancy component scheme for system reliability and availability during scheduled maintenance and/or software/hardware upgrades. The signaling gateway 234 may be configured to directly provide for lower level signaling system 7 (SS7) processing.
In exemplary embodiments, the signaling gateway 234 interacts with the call manager 218 using an appropriate open interface (e.g., Common Object Request Broker Architecture (COBRA)). In these embodiments, it may be desirable for translation software in the signaling gateway 234 to add Message Transfer Part (MTP) layer information to the ISUP and/or TCAP data to create a complete signaling system 7 (SS7) message. The complete signaling system 7 message may then be sent to the Signaling Transfer Point (STP) in the external signaling system 7 (SS7) network 170. Conversely, the signaling gateway 234 may be configured to remove ISUP or TCAP application layer data from the signaling system 7 (SS7) messages received from the STP prior to converting the information to an appropriate open interface (e.g., COBRA) and forwarding the information to the call manager 218 via the central router 210.
The accounting gateway (AG) 240 may be configured to receive messages representing events from the call manager 218 via a suitable transport mechanism such as the central router 210. Typically, two messages are received for each call, the first when the call is established, and second when the call terminates. In the case of unsuccessful calls, only the failure message will be logged. The messages provide details about the calling and called parties, the timing of the call set-up, the duration and the quality of the call. Accounting gateway 240 may be duplicated using a redundant computer, with each gateway having dual-mirrored disks. The accounting gateway 240 stores usage records and may then distribute them to linked destinations (e.g., billing centers) for processing. Billing centers typically include bill processors that receive accounting information from the accounting gateway 240 and generate appropriate on-line or paper billing to customers. The accounting gateway may be configured to accommodate multiple days worth of accounting records such as the records for one day, two days, three days, four days, a week, or a month. The period in which the data is retained in the accounting gateway may be dependent on business needs, hardware restrictions, and/or the billing cycle. For example, as the end of the billing cycle nears, it may be desirable to shorten the period the accounting gateway holds the data such that calls placed the day the bills are printed are included on the bills. Further, the accounting gateway may both retain and forward data to the billing centers. In this manner, if the equipment at the billing center fails, the accounting gateway 240 may serve as a backup. Similarly, the billing center may act as a backup where the accounting gateway 240 fails.
An Automatic Message Accounting (AMA) format is typically used by circuit-switching systems, packet-switching systems, and other network elements to provide billing usage measurements data (e.g., the Bellcore® Automatic Message Accounting Format (BAF)). This data may be utilized either to permit charging the customer for use of network resources or to permit charging other carriers (e.g., InterExchange Carrier (IEC) and other Local Exchange Carrier (LEC)) for assistance in placing call connections. The accounting gateway 240 may be configured to convert this information into an Automatic Message Accounting Format (AMA) Format (e.g., BAF) records and send these records to the external billing systems using, for example, a TFTP (trivial file transfer protocol). Time-stamp accuracy is typically based on the accuracy of the call manager 218 clock which may be derived from the TOD 212 server. To create appropriate AMA records, the event information produced by the call manager 218 preferably has appropriate information for the telephone service specified such as phone number of the calling party (customer), phone number of the called party (customer), time of call, duration of the phone call, and use of any discretionary features. Different AMA structures may be generated between On-Net calls (defined as within a network service provider IP network 120) vs. Off-Net calls (defined as outside of service provider IP network—e.g. public switched telephone network) for billing purposes.
The element management gateway (EMG) 238 may provide system management functionality that includes, for example: a) status and performance monitoring for the Operation Administration, Maintenance, and Provisioning center, to gauge the ongoing operation of applications; b) extensive information exchange with a network operations center responsible for ongoing maintenance of one or more applications; c) customizable operations interface to allow the network operations center to view only information required, thus reducing the time spent filtering information; d) centralize distributed application configuration allowing for the centralized configuration of objects residing on a plurality machines; e) proactive network management capabilities to remove the need for constant operator intervention making the day-to-day operations more efficient; and/or f) intelligent display of status information to separate critical issues from low-priority problems allowing the operation center to assign resources to the right problems at the right time.
The multimedia gateway (MG) 230 may be configured to connect to the public switched telephone network 160 and to convert IP based multimedia packets into standard public switched telephone network 160 traffic. The multimedia gateway 230 may include an intelligent franking interface that communicates with the call manager 218 for automatic trunk sizing and allocation between the IP network 120 and the public switched telephone network 160. For example, when an system user at the customer premises is using a PC and/or a multimedia phone to communicate with a traditional public switched telephone network 160 user, the communication session involves the transmission of video and audio data. The bandwidth that is required for this type of communication is much greater than that required for a PSTN-to-PSTN voice call or an IP-to-PSTN voice call. The multimedia gateway 230, as the interface between two systems, may negotiate a larger bandwidth to facilitate the call if the called party is also video enabled. This bandwidth negotiation process typically occurs with a 5ESS or a Local Digital Switch within the public switched telephone network 160. Typically, a multimedia call, including live video, audio and data, will require bandwidth ranging from 56K to 1.544 Mbps. However, as the number of users sharing the same link grows, the quality of the transmission deteriorates significantly. The multimedia gateway 230 must be able to monitor bandwidth usage and make appropriate adjustments so as to maintain an acceptable quality of service. Further, it may be desirable for the call manager 218 and the multimedia gateway 230 to communicate between themselves and/or the customer premises equipment 102 to determine whether the user has authorized the additional bandwidth and hence expense of the call. For example, even where a called and/or calling party is video enabled, it may nonetheless refuse to authorize payment for the increased bandwidth necessary for video.
The Internet gateway (IG) 236 may be connected to the Internet (e.g., World Wide Web (www)) and provide a means for IP based data packets to be routed between the IP network 120 and the Internet 180. Alternatively, IP based voice packets may be routed via the Internet 180. In exemplary embodiments, the Internet gateway 236 routes data-only packets which share the same priority level with other lower priority, non-real-time traffic consistent with computer data communications presently experienced with the Internet 180. Consequently, low priority and low latency data traffic on the IP network 120 utilize the Internet gateway 236 to communicate with other IP data networks such as the www. Voice packets may be routed through another network such as the ATM/frame/cell relay network 185, a private IP network 120, and/or the public switched telephone network 160 where committed information rates may be easily obtained.
In exemplary embodiments, the broadband network 1 includes the interfaces which enable connections to existing Operation, Maintenance and Provisioning (OAM&P) 195 systems that support, billing, accounting, provisioning and/or configuration management functions. A Secured Management Data (SMD) Network 190 may be utilized to connect the OAM&P 195 to the accounting gateway 240 and element management gateway 238. The Secure Management Data network 190 may include a Network Service Division's NSD Net. The Secure Management Data network 190 helps ensure that only secure communication can occur between the IP central station 200 and the OAM&P 195. This eliminates one potential means of tampering with the billing and provisioning functions in the OAM&P. The billing systems (OSS) 195 may include the Network Operations Center (NOC). The NOC may include a translation server which includes functions for allowing communications and control of diverse networks.
Referring to
The broadband residential gateway 300 may be variously configured to, for example, provide high-speed cable modem capabilities to interconnect one or more associated PCs with each other and with the remainder of the broadband network 1, provide functionality to one or more TVs (using, for example, either an integrated or separate decoder functionality, e.g., set top box 350), one or more telephone connections such as plain old telephone service (POTS) phones and/or digital telephones, displays, wireless interfaces, voice processing, remote control interface, display interface, and/or administrative functions. In exemplary embodiments, the broadband residential gateway 300 may a) providing conversion between analog voice and IP voice packets, b) multiplexing/demultiplexing streams of IP voice packets, c) supporting multiplexing/demultiplexing of multiple incoming and outgoing signals including multiple voice, multimedia, data, system administration, and/or TV information signals.
Where the elements of the broadband residential gateway 300 are interconnected, the interconnection may be provided by one or more data buses, for example, a high speed bus (HSB) 360, processor bus 380, and/or other interconnection system. The high speed bus 360, 380 may be configured to provide a flexible conduit for transferring information between the internal hardware, processors and ports. In exemplary embodiments of the broadband residential gateway 300, the high speed bus 360 may include one or more of the following functional units a) a universal remote control receiver module 365 for receiving wireless (e.g., infrared, and/or RF) signals (e.g., keyboard signals and/or remote control signals) for control of the broadband residential gateway 300 and/or any connected devices, b) a display, display driver, touch screen logic module for driving one or more local and/or remote displays for interfacing with the broadband residential gateway 300 and/or one or more connected devices, c) one or more TV port modules 336 for interconnecting televisions, set-top devices, and/or other audiovisual devices to the broadband residential gateway 300, d) one or more data port modules 334 for connecting/interconnecting data enabled devices (e.g., personal computers, palm top devices, ect.), e) one or more telephony port modules 332 for interconnecting one or more analog and/or digital telephones, f) one or more peripheral port modules 342 for interconnecting one or more peripheral devices such as disk drives, data storage devices, video cassette recorders, DVD devices, audio devices, video devices (e.g., camcorders, digital cameras, digital video recorders, stereos, etc.), g) one or more external/internal intercom modules 344 for interconnecting remote intercom and/or security monitoring devices, h) one or more wireless interface modules 345 for interconnecting with various wireless extension devices such as wireless TVs, cordless and/or wireless telephones, wireless LANs, etc., i) one or more voice recognition/voice synthesis modules 355 for generating voice announcements, voice messages, and voice prompts and for recognizing voice generated commands and data, j) set-top box module 350 for performing the functions associated with a set-top box locally and/or for communicating with one or more remotely coupled set-top boxes, k) memory 322 (e.g., DRAM, RAM, flash, and/or other memory) for storing information and operating data within the broadband residential gateway 300, l) transceiver 302 for communicating with one or more external broadband networks m) operating program store 330 (e.g., ROM, flash, etc.) for storing at least portions of the operating programs for the broadband residential gateway 300 and/or interconnected devices, n) security processor, smart card and/or credit card interface module 340 for providing secure processing functions and/or credit card/smart card transaction functions, and/or o) distributed processing controller 306 which may be a microprocessor and/or one or more interconnected distributed processing modules for controlling the broadband residential gateway 300. Where the distributed processing controller 306 includes one or more distributed processing modules, the modules may include a telephony processing module (P1) 308, data processing module (P23) 310, video processing module (P3) 312, auxiliary processing module (P4) 314, IP processing module (P5) 316, and/or an operations administration maintenance and provisioning processing module (P6) 318 interconnected through one or more busses such as processor bus 380. The processor bus 380 and/or high speed bus 360 may include any suitable interconnect bus including intelligent bus configurations incorporating smart buffer logic (not shown in
The transceiver 302 may include circuits for converting digital signals to and from RF signals suitable for transmission across a broadband network such as the hybrid fiber-coaxial plant 112. The transceiver 302 may include one or more input/output ports such as a cable interface (e.g., an F connector cable connection) and/or a fiber optic interface connected to a communication media (e.g., hybrid fiber-coaxial Plant 112). The transceiver 302 may be compatible with the DOCSIS 1.0 or later specifications. For signaling purposes, the broadband residential gateway 300 may be compatible with the Media Gateway Control Protocol (MGCP) or other compatible signaling protocol (e.g., SIP or H.GCP) to support telephony applications. The transceiver 302 may serve as a modem, a translator and/or a multiplexor/demultiplexor. Data received from the network may be de-multiplexed and placed on the data bus for dispatch to the appropriate peripherals and/or ports. Data from the various ports and peripherals may be multiplexed together for distribution over one or more broadband networks (e.g., the hybrid fiber-coaxial (HFC) plant 112). Where a hybrid fiber-coaxial plant 112 is utilized, the data may be multiplexed onto various frequency bands of the hybrid fiber-coaxial plant 112 in a continuous data stream(s) and/or packetized data stream(s). To facilitate data transfer for various networks, the transceiver 302 may be include one or more registers for data queuing and/or IP tunneling of data packets across the broadband network.
Although the illustration of a display, display drivers, and touch screen logic device 338 suggests that the a display is integral to the broadband residential gateway 300, alternative embodiments of the broadband residential gateway 300 may provide a user interface via the TV screen, PC screen, video telephone, and/or other display device in addition to, or in lieu of, a display integral to the broadband residential gateway 300.
The peripheral ports module 342 may include a plurality of ports providing connectivity to external peripherals. Exemplary interfaces include, PCI, Firewire, USB, DB25, etc. Devices which incorporate one or more of these interfaces may utilize the broadband residential gateway 300 to interconnect to the remainder of the broadband network 1.
The external/internal Intercom Module (IM) 344 may include one or more microphones/speakers, voice CODECs, telephony processors, and/or interface ports. Where an intercom module 344 is utilized, the built-in circuitry may be configured to detect, for example, unused plain old telephone system telephone(s) and generates a special intercom tone on these unused telephones. In this manner, existing plain old telephone system telephones, digital phones, and/or other devices may serve as an intercom throughout the residence. The controller 306 (e.g., such as the P1 telephony processor 308) may function to command the intercom module 344 to determine an appropriate intercom path to select an intercom connection between various locations. In exemplary embodiments, the CODEC may be configured to convert the analog voice signal into IP packets for transmission over one or more data ports 334, TV ports 336, display modules 338, telephony ports 332, peripheral ports 342, external/internal intercom ports 344, wireless interface ports 345, and/or set-top boxes 350.
In yet further embodiments, multiple broadband residential gateways 300 may be configured through, for example, IP tunneling, to set-up an intercom connection between multiple remote broadband residential gateways 300. In this manner, an administrative assistant at the office may be contacted via an intercom connection present at the users home. Thus, one or more individuals disposed at either local and/or remote locations with diverse types of equipment may communicate as an intercom group without the need to communicate via normal dialing procedures.
In addition to intercom services, the intercom module 344 may also configure intercom services for other telephony services (e.g., extension transfer, call conferencing, internal caller ID), high speed data services (e.g., LAN connections), facsimile transmission/reception, e-mail transmission/reception, video conferencing, and/or CATV/HDTV (Cable Television/High Definition Television) using standard industry protocols such as DOCSIS 1.0 or higher and IP tunneling transmissions. These services are advantageous in that once configured, the user may simulate a work environment in his home.
Though processing may be accomplished by a single processor performing all functions (e.g., processing controller 306), in the preferred embodiment shown in
The Distributed Processing Controller 306 with its associated processors (P1-P6) may be coupled to the various elements of the broadband residential gateway 300 so as to enable proper operation of each of the individual components. For example, the distributed processing controller 306 (with any associated processors (P1-P6)) may also coupled to the security processor, smart card/credit card, and interface module 340, the peripheral port(s) module 342, and/or the External/Internal Intercom Module 344 for providing control and coordination among devices coupled to the high speed bus 360.
The display 338 may include, for example, an interactive LED/LCD module positioned in a suitable location such as within or attached to the broadband residential gateway 300. The display 338 may include an interface to notify, display and receive user inputs and processing status. The display 338 may be configured to display various informational status such as multimedia mail, called ID, call logs, call in progress and associated information, call waiting information, call conferencing, and/or other call related information. The display 338 may provide a display of real time status of the various devices connected to the broadband residential gateway 300 as well as any current connections, calls, and/or data transfers. The display 338 may also include touch screen capabilities that allow information to be input via a plurality of interrelated on-screen prompts, on-screen icons, and/or a keypad (e.g., an alphanumeric keyboard). The keypad may be a remote control, numeric keyboard, and/or alphanumeric keyboard.
In one embodiment of the display 338 operation, a user may touch an icon representing a pending voicemail and/or multimedia mail message. The panel may be configured to send an electronic signal to the processing controller 306 and/or an attached processor such as the telephony processor. On receiving the signal, the P1 telephony processor 308 may be configured to generate an IP packet via the transceiver 302 across portions of the broadband network 1 to the multimedia server 222 in IP central station 200. The multimedia server 222 may authenticate the request by, for example, verifying location of the request and/or the identity of the requesting party. Where identity of the calling party is being verified, the user enter an access password by an audio and/or keyboard request. Where an audio request is generated, the user may utilize the external/internal intercom module 344 of the broadband residential gateway 300, or via a text message entered into the display 338. The user may then enter the appropriate access code via the onscreen soft keypad, microphone, and/or keyboard. Alternatively, the message could be stored locally in the broadband residential gateways 300 memory 322 and depending on whether there is a password lock on the broadband residential gateway 300, the user may not have to enter a password to access the message. Where the message is stored locally in the broadband residential gateways 300 memory 322 rather than IP central station, the display 338 simply recalls the message from memory and presents to the user to provide one-touch instant message retrieval.
In embodiments where the broadband residential gateway 300 supports multiple mailboxes, the icons on the LCD/LED may be personalized to show the identity of the owner of the message. Each user may have a different password to ensure privacy of access. An activity log which tracks past and present messages and/or archives multimedia messages may be presented on display 338. The archive may be stored locally, or at a remote location such as IP central. The archive may be utilized by the user to recall messages which have long since been erased from local storage but may be retrieved from IP central on tape and/or disk storage. This is preferably an optional feature for those users who are less security conscious. The multimedia messages need not be displayed only on display 338. In alternate embodiments, any of the peripheral devices attached to the broadband residential gateway 300 are capable of receiving the multimedia messages.
The memory 322 may be variously configured to include one or more field-upgradeable card slots for permitting memory expansion. Certain users may wish to enable higher end applications such as near video on demand (e.g., pausing of shows via buffering in memory), video conferencing of multiple users, multi-party conferences, call waiting for multiple parties, etc. Accordingly, the use of a broadband residential gateway 300 allows the user to upgrade memory via inserting additional cards. Alternatively, the user may use system memory in IP central and buffer data remotely.
Operating program store 330 may be configured to receive updates. This may be accomplished by having the user replace one or more memory cards or automatically by the IP central station downloading new operating code into one or more residential gateways 300.
As previously indicated, smart buffer logic (SBL) may be coupled to the telephony port(s) 332, data port(s) 334, TV port(s) 336, peripheral port(s) 342, and/or the distributed processing controller (DPC) 306. Where the smart buffer logic is utilized, it may function to buffer the IP packets for delivery over the communication network such as the hybrid fiber-coaxial plant 112. In addition, the smart buffer logic may include selectable switching and routing algorithms based on services and applications associated with each port. Depending on the destination of the IP traffic, the smart buffer logic may multiplex signal from various devices to effect faster information transfer. The smart buffer logic may also allow direct memory access between memory 322 and one or more of the devices and/or ports coupled to the high speed bus 360.
The telephony port(s) 332 may include various interface circuitry (e.g., analog interface, logic and firmware for interfacing with the Plain Old Telephone (POTs) telephones). Also the telephony port(s) 332 may also be configured to include user interface logic, voice processing logic, voice activity detector logic, voice CODECs, and DTMF (dual tone multi-frequency) tone sensing logic. Echo cancellation and automatic gain control may also be utilized in the telephony port(s) 332 circuitry. In one embodiment, RJ-11 connectors for a plurality of lines (e.g., 4) are provided for connection to one or more existing plain old telephone system 110 telephone units. However, the broadband residential gateway 300 may contain any number of telephone connection ports. In this manner, any number of existing user phone may connected directly to the broadband residential gateway 300 without modification. Alternatively, the broadband residential gateway can be configured to support, in addition to or as alternative to the plain old telephone system telephone units, ISDN telephones and/or other digital phones (e.g., IP telephones) using an appropriate interface.
The data port(s) 334 interface may be variously configured. In one configuration, the data ports include high speed data service connections to, for example, a personal computer (PC) using a LAN connection. For example, the data ports 334 may include an Ethernet 802.3 connection compatible with category 5 unshielded twisted pair (UTP) cable and a RJ-45 connector. The data port(s) 334 may include the necessary interface circuitry for coupling to remote computers.
The TV port(s) 336 may include an interface for conventional television, HDTV and/or CATV services. The TV port(s) 336 typically have one or more F-connectors used for coaxial cable connection to a TV set(s). The TV ports may be configured to connect to a set top box (STB) via the F-connector or directly to a remote television. In embodiments where the settop box is co-located with the television, the data supplied over the TV ports may be either analog and/or digital information. Where the settop box is integrated into and/or comprises the broadband residential gateway 300, the TV ports may be analog or compatible with HDTV signals.
The broadband residential gateway 300 need not necessarily be limited to home use and is intended to also be utilized in business applications. In some configurations, the broadband residential gateway 300 may serve the same functions and operate as a private branch exchange (PBX). Where greater capacity is desired, one or more broadband residential gateways 300 may be disposed on a PC card and combined in a PC, rackmount, and/or server to create an expandable private branch exchange type system that enables intra-premises calling between telephones connected to various telephone connectors on the broadband residential gateway 300.
Where the broadband residential gateway 300 is coupled to the hybrid fiber-coaxial plant 112 in accordance with a preferred embodiment of the present invention, it may be configured to provide the user with both information data (e.g., through an Ethernet interface), telephony access, and TV service (e.g., HDTV, Digital TV and/or CATV services). In exemplary embodiments, the hybrid fiber-coaxial plant 112 typically includes both coaxial cable and optical fiber networks, though, where desired, the network may include only coaxial cable or optical fiber. The hybrid fiber-coaxial plant 112 may be coupled to a head-end hub (HEH) 115. The head end hub 115 may provide an interconnection point to gather and/or transform external services (e.g., off air and satellite video, public switched telephone network voice, and Internet data) into a format suitable for distribution on the hybrid fiber-coaxial plant 112 for use with the customer premise equipment 102. The head-end hub 115 may include one or more cable modem termination systems (CMTS) 116 coupled between the hybrid fiber-coaxial plant 112, a Head-end (HE) 117 and/or an Edge Router (ER) 118. The edge router 118 may be coupled to the cable modem termination system 116 and to one or more ultra high speed routers (UHR) 121. One or more ultra high speed routers 121 may be interconnected to each other and/or through a centralized mechanism such as an IP network database to form a high speed network. The high speed packet network 120n is one example of the network 120 (e.g., IP network) shown in
In the embodiment shown in
As indicated above, the broadband network 1 may include a plurality of interconnected high performance networks 120n. Each high performance network 120n may include a separate IP central station 200 and/or share a single IP central station. Having distributed IP central stations located throughout the broadband network 1 provides improved performance and quicker response time for an individual user. Although not illustrated, each high performance network 120, 120n may be connected to multiple head-end hubs 115, each head-end hub 115 may be connected to multiple hybrid fiber-coaxial plants 112, and each hybrid fiber-coaxial plant 112 may be connected to a plurality of customer premises equipment 102, each containing one or more broadband residential gateways 300. The plurality of high performance networks 120n may be configured as an interconnected network for routing packetized information from point-to-point in accordance with a desired destination.
The high performance network 120n may be configured to provide connectivity for and between a plurality of head-end hubs 115 and/or a plurality of broadband residential gateways 300 and other networks such as the Internet, e.g., www 180, the public switched telephone network (PSTN) 160 and/or various signaling systems such as the SS7 network 170 for end-to-end voice over IP applications. The IP central station 200 may be configured to provide seamless integration and control of the high performance network 120 (e.g., an IP based communication system) interface with the public switched telephone networks (PSTN) 160, signaling system seven (SS7) 170, and/or the Internet 180 so that packetized data, voice calls, and other signaling information is properly transferred between the broadband residential gateway 300 and the public switched telephone network 160 and Internet 180. In certain configurations, the hybrid fiber-coaxial 112, head-end hub 115, and high performance network 120, provide a signal conduit for packetized voice and data which may, with the coordination of the IP central station 200, be provided in the appropriate format between the broadband residential gateway 300, the public switched telephone network 160, and/or the www 180.
The typical home user is currently required to purchase multiple intelligent data conduits such as multiple set-top boxes, a plurality of conventional, DSL and/or ISDN phones, cable modems, HDTV receivers, satellite receivers, home PC LANs, etc. The integrated communication system of the present invention provides a user friendly versatile communication system that enables voice over IP telephony, information data (e.g., PC and Internet), and television services in a system with one intelligent customer premise equipment 102 interface, the broadband residential gateway 300. The broadband residential gateway 300 in conjunction with the IP central station 200 provides a flexible communication system that can provide any number of integrated communication service features and functions without requiring the user to become familiar with numerous, diverse types of equipment.
In one exemplary application of the voice over IP operations, the broadband residential gateway 300 digitizes the analog telephony signal using, for example, G.711 μ law coding (64 Kbps Pulse Code Modulation). The digital samples may then be packetized in, for example, the broadband residential gateway 300 into IP packets. The broadband residential gateway 300 may be configured to encapsulate the IP packets into, for example, DOCSIS (Data Over Cable Service Interface Specifications) frames for transmission back to the head-end hub (HEH) 115 over the hybrid fiber-coaxial plant 112. The hybrid fiber-coaxial plant 112 may then be configured to transport signals for both upstream (to head-end hub 202) and downstream (to the broadband residential gateway 300 and customer premise equipment 102) directions. Although the DOCSIS protocol is utilized in this example, any future protocol may also be used for the digitizing and packeting of data. Where the protocol changes, it may be desirable to download new operating code from, for example, IP central station 200 to the individual broadband residential gateways 300, to update the communication protocols dynamically. When new protocols are adopted, the IP central station may utilize, for example, the system management server 216 to download new protocol data into, for example, the protocol manager in the call manager 218 and the program store 330 in the broadband residential gateway 300.
Where voice packets are sent over constant bit rate (CBR) channels using unsolicited grants, additional packet data channels may be used to support signaling messages (e.g., SGCP, Simple Gateway Control Protocol), high-speed cable modem service and/or other upstream packet data services. The upstream packet data services may be sent using available bit rate (ABR) channels such that the voice channels not impacted by data traffic.
The head-end 117 may originate CATV signals for transmission over the distribution network. However, in alternate embodiments, signals may be inserted at other points in the distribution network, such as at various hubs or may arise at remote locations in the network such as IP central. Down stream channels may be utilized to facilitate the transmission of signals from the head-end or other input distribution point to the subscriber premise. Where analog RF signals arrive at the broadband residential gateway 300 of the customer premise equipment 102, typically, the transceiver circuitry 302 will detect if the signal is addressed to this broadband residential gateway 300. If so, the transceiver will allow reception of the RF signal. Upon conversion to a digital format, the signal is typically output over the high speed bus (HSB) 360 to one or more associated devices for processing. For example, where the signal is a TV signal, the signal may be output directly to the TV port 336 and/or processed by the settop box 350 prior to outputting to the TV ports 336 and/or display 338. Where user channel selection is preformed directly in the broadband residential gateway 300, channel selection may be preformed by remote control receiver 365 using an external device such as a remote control. The remote control receiver may receive a plurality of individually coded remote control commands from different receivers and process the signals for only one associated device in accordance with the received commands. Alternative channel inputs include the display 338 and/or any associated keypad. Authorization to certain channels may be controlled by security processor 340.
Where a remote settop box is utilized, the box may be coupled directly to the HFC for individual frequency tuning and/or receive a digital feed from the broadband residential gateway 300 after decoding the digital signal. For example, where hybrid fiber-coaxial plant 112 contains fiber connections to locations near the individual homes, it may be desirable to download one or more simultaneous individually requested programming stream(s) and/or digital data stream(s) to the broadband residential gateway 300. In this manner, the number of channels, movie selections, and/or entertainment options available to the user are unlimited. Cost is minimized since only a single intelligent user interface is used in the home and all televisions, phones, computers, and/or other user interface devices use the same intelligent user interface to the broadband network 1. In this manner, the broadband network 1 may offer premium television, voice and/or data services to multiple conventional televisions, phones, and PCs without the use of multiple set boxes, modems, and external connections. Thus, the users are provided a single unified interface to satisfy their external data needs.
Although the IP voice packets for these calls are typically routed over the IP network 120, the system may, where appropriate, route IP voice packets over the Internet 180.
According to one embodiment of the present invention, a subscriber can create a customized call forwarding profile for controlling the forwarding of calls to the subscriber over the IP telephony network. The subscriber can create multiple call forwarding profiles which are then stored in the BRG associated with the telephone or elsewhere in the IP telephony network. The call forwarding profiles may be created by the subscriber using a PC connected to the Broadband Residential Gateway (BRG). The BRG can pro user through the PC to select various criteria set forth below. Alternatively, the PC can have appropriate software for communicating with the BRG and setting up the call forwarding profile. Alternatively, the call forwarding profile can be created using the BRG directly. For example, the subscriber can create the call forwarding profile by entering or selecting the appropriate information displayed on the touch-sensitive screen. In addition, the call forwarding profile can be created by speaking into the microphone on the BRG. For example, the subscriber could say “Create call forwarding Profile” and then list a plurality of telephone numbers. Alternatively, the subscriber might be prompted by a series of questions from the BRG regarding the creation or modification of a call forwarding profile. In either case, the subscriber's spoken words are recognized by the BRG's voice recognition device. Alternatively, the call forwarding profile may be created and/or stored in the IP network itself such as in a database accessible by the Call Manager.
Each call forwarding profile may point to one or more (in any combination) of the following types of call forwarding services:
For example, a subscriber may wish to have calls forwarded from his home to his office during the work day, from either his home or office to his cellular phone during rush hour (while the subscriber is traveling to and from the office) and from his office to his home during the evening. The subscriber may further have all calls from the subscriber's spouse always forwarded to the subscriber's cellular phone at all times, except on weekends.
When a desired call forwarding profile is created and selected by the subscriber, the profile will remain active until the user disables/deletes the profile. Once the call forwarding profile is created, the subscriber may store the profile on the PC connected to the BRG, and the profile may be downloaded to the BRG. The BRG may be equipped with a flash memory for storing the call forwarding profile. In such an embodiment where a call forwarding profile has been activated by the subscriber, when a call arrives, the BRG first checks it's flash memory for active call forwarding features as listed in the call forwarding profile. The distributed intelligence in the PC and BRG greatly enhances the flexibility and user-friendliness for IP telephony customers. Alternatively, where the call forwarding profile is stored in the IP network, the Call Manager may refer to the call forwarding profile for activating the appropriate call forwarding features.
Optionally, an alerting parameter in the call delivery message may be used to instruct the called Broadband Residential Gateway (BRG) to generate a distinctive ringing tone on the forwarded phone to notify the subscriber that the call is a forwarded call and not a call originally directed to the forwarded phone. The alerting Parameter is inserted into the call delivery message by the Call Manager.
Although the present invention has been described in relation to particular preferred embodiments thereof, many variations, equivalents, modifications and other uses will become apparent to those skilled in the art. It is preferred, therefore, that the present invention be limited not by the specific disclosure herein, but only by the appended claims.
This application is a continuation of U.S. patent application Ser. No. 13/278,923 filed Oct. 21, 2011, which is a continuation of U.S. patent application Ser. No. 12/391,828 filed Feb. 24, 2009 and issued as U.S. Pat. No. 8,054,963, which in turn is a continuation of U.S. patent application Ser. No. 11/133,030 filed May 20, 2005 and issued as U.S. Pat. No. 7,496,190, which in turn is a continuation of U.S. patent application Ser. No. 09/475,144 filed Dec. 30, 1999 and issued as U.S. Pat. No. 6,937,713, all of which are hereby incorporated by reference herein in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
4694487 | Chang et al. | Sep 1987 | A |
4887152 | Matsuzaki et al. | Dec 1989 | A |
4893335 | Fuller et al. | Jan 1990 | A |
4922529 | Kiel | May 1990 | A |
4926462 | Ladd et al. | May 1990 | A |
4995074 | Goldman et al. | Feb 1991 | A |
5077789 | Clark, Jr. et al. | Dec 1991 | A |
5099509 | Morganstein et al. | Mar 1992 | A |
5253341 | Rozmanith et al. | Oct 1993 | A |
5260776 | Taguchi et al. | Nov 1993 | A |
5268958 | Nakano | Dec 1993 | A |
5274700 | Gechter et al. | Dec 1993 | A |
5276731 | Arbel et al. | Jan 1994 | A |
5278894 | Shaw | Jan 1994 | A |
5327486 | Wolff et al. | Jul 1994 | A |
5341425 | Wasilewski et al. | Aug 1994 | A |
5349638 | Pitroda et al. | Sep 1994 | A |
5363431 | Schull et al. | Nov 1994 | A |
5375161 | Fuller et al. | Dec 1994 | A |
5400327 | Dezonno | Mar 1995 | A |
5416842 | Aziz | May 1995 | A |
5428608 | Freeman et al. | Jun 1995 | A |
5440616 | Harrington et al. | Aug 1995 | A |
5449970 | Kumar et al. | Sep 1995 | A |
5471523 | Smith et al. | Nov 1995 | A |
5479411 | Klein | Dec 1995 | A |
5483588 | Eaton et al. | Jan 1996 | A |
5533100 | Bass et al. | Jul 1996 | A |
5533110 | Pinard et al. | Jul 1996 | A |
5533111 | Schlanger | Jul 1996 | A |
5537157 | Washino et al. | Jul 1996 | A |
5541983 | Rose | Jul 1996 | A |
5546447 | Skarbo et al. | Aug 1996 | A |
5583929 | Ardon | Dec 1996 | A |
5590184 | London | Dec 1996 | A |
5592529 | Linsker | Jan 1997 | A |
5600643 | Robrock, II | Feb 1997 | A |
5610910 | Focsaneanu et al. | Mar 1997 | A |
5612997 | Vallelonga, Sr. et al. | Mar 1997 | A |
5615252 | Sizer, II et al. | Mar 1997 | A |
5615257 | Pezzullo et al. | Mar 1997 | A |
5629978 | Blumhardt et al. | May 1997 | A |
5652789 | Miner et al. | Jul 1997 | A |
5657377 | Pinard et al. | Aug 1997 | A |
5657426 | Waters et al. | Aug 1997 | A |
5689555 | Sonnenberg | Nov 1997 | A |
5689708 | Regnier et al. | Nov 1997 | A |
5696815 | Smyk | Dec 1997 | A |
5703942 | Pinard et al. | Dec 1997 | A |
5706342 | Baeder et al. | Jan 1998 | A |
5708961 | Hylton et al. | Jan 1998 | A |
5712907 | Wegner et al. | Jan 1998 | A |
5719872 | Dubberly et al. | Feb 1998 | A |
5724412 | Srinivasan | Mar 1998 | A |
5740230 | Vaudreuil | Apr 1998 | A |
5740231 | Cohn et al. | Apr 1998 | A |
5742596 | Baratz et al. | Apr 1998 | A |
5742905 | Pepe et al. | Apr 1998 | A |
5745553 | Mirville et al. | Apr 1998 | A |
5745559 | Weir | Apr 1998 | A |
5745569 | Moskowitz et al. | Apr 1998 | A |
5751706 | Land et al. | May 1998 | A |
5761306 | Lewis | Jun 1998 | A |
5764752 | Waite et al. | Jun 1998 | A |
5768389 | Ishii | Jun 1998 | A |
5768513 | Kuthyar et al. | Jun 1998 | A |
5784444 | Snyder et al. | Jul 1998 | A |
5796394 | Wicks et al. | Aug 1998 | A |
5796424 | Ely et al. | Aug 1998 | A |
5796952 | Davis et al. | Aug 1998 | A |
5805587 | Norris et al. | Sep 1998 | A |
5809126 | Smith et al. | Sep 1998 | A |
5809128 | McMullin | Sep 1998 | A |
5809520 | Edwards et al. | Sep 1998 | A |
5814798 | Zancho | Sep 1998 | A |
5822415 | Gordon | Oct 1998 | A |
5825862 | Voit et al. | Oct 1998 | A |
5841839 | Fogg et al. | Nov 1998 | A |
5850429 | Joyce et al. | Dec 1998 | A |
5859902 | Freedman | Jan 1999 | A |
5862134 | Deng | Jan 1999 | A |
5864612 | Strauss et al. | Jan 1999 | A |
5867495 | Elliott et al. | Feb 1999 | A |
5870565 | Glitho | Feb 1999 | A |
5889844 | Kim et al. | Mar 1999 | A |
5894504 | Alfred et al. | Apr 1999 | A |
5896444 | Perlman et al. | Apr 1999 | A |
5898668 | Shaffer | Apr 1999 | A |
5905776 | Shaffer | May 1999 | A |
5907604 | Hsu | May 1999 | A |
5912962 | Bosco | Jun 1999 | A |
5916302 | Dunn et al. | Jun 1999 | A |
5917624 | Wagner | Jun 1999 | A |
5920705 | Lyon et al. | Jul 1999 | A |
5923731 | McClure | Jul 1999 | A |
5933490 | White et al. | Aug 1999 | A |
5937347 | Gordon | Aug 1999 | A |
5940598 | Strauss et al. | Aug 1999 | A |
5943397 | Gabin et al. | Aug 1999 | A |
5946381 | Danne et al. | Aug 1999 | A |
5946386 | Rogers et al. | Aug 1999 | A |
5956717 | Kraay et al. | Sep 1999 | A |
5970072 | Gammenthaler, Jr. et al. | Oct 1999 | A |
5974142 | Heer et al. | Oct 1999 | A |
5978470 | Shaffer et al. | Nov 1999 | A |
5982774 | Foladare et al. | Nov 1999 | A |
5987508 | Agraharam et al. | Nov 1999 | A |
5999525 | Krishnaswamy et al. | Dec 1999 | A |
5999602 | Yang et al. | Dec 1999 | A |
5999612 | Dunn et al. | Dec 1999 | A |
6005602 | Matthews, III | Dec 1999 | A |
6005845 | Svennesson et al. | Dec 1999 | A |
6006253 | Kumar et al. | Dec 1999 | A |
6009177 | Sudia | Dec 1999 | A |
6011909 | Newlin et al. | Jan 2000 | A |
6014379 | White et al. | Jan 2000 | A |
6023724 | Bhatia et al. | Feb 2000 | A |
6028848 | Bhatia et al. | Feb 2000 | A |
6031896 | Gardell et al. | Feb 2000 | A |
6044349 | Tolopka et al. | Mar 2000 | A |
6052444 | Ferry et al. | Apr 2000 | A |
6052725 | McCann et al. | Apr 2000 | A |
6061434 | Corbett | May 2000 | A |
6078582 | Curry et al. | Jun 2000 | A |
6094431 | Yamato et al. | Jul 2000 | A |
6104800 | Benson | Aug 2000 | A |
6108330 | Bhatia et al. | Aug 2000 | A |
6115393 | Engel et al. | Sep 2000 | A |
6118432 | Kotorov et al. | Sep 2000 | A |
6118768 | Bhatia et al. | Sep 2000 | A |
6122357 | Farris et al. | Sep 2000 | A |
6128304 | Gardell et al. | Oct 2000 | A |
6137870 | Scherer | Oct 2000 | A |
6144401 | Casemant et al. | Nov 2000 | A |
6148193 | Miska et al. | Nov 2000 | A |
6154465 | Pickett | Nov 2000 | A |
6154531 | Clapper | Nov 2000 | A |
6157708 | Gordon | Dec 2000 | A |
6160880 | Allen | Dec 2000 | A |
6163531 | Kumar | Dec 2000 | A |
6169795 | Dunn et al. | Jan 2001 | B1 |
6188760 | Oran et al. | Feb 2001 | B1 |
6192116 | Mayak | Feb 2001 | B1 |
6215585 | Yoshimura et al. | Apr 2001 | B1 |
6219045 | Leahy et al. | Apr 2001 | B1 |
6229887 | Albers et al. | May 2001 | B1 |
6233235 | Burke et al. | May 2001 | B1 |
6233313 | Farris et al. | May 2001 | B1 |
6233318 | Picard et al. | May 2001 | B1 |
6236653 | Dalton et al. | May 2001 | B1 |
6253249 | Belzile | Jun 2001 | B1 |
6259449 | Saxena et al. | Jul 2001 | B1 |
6262979 | Anderson et al. | Jul 2001 | B1 |
6263503 | Margulis | Jul 2001 | B1 |
6266405 | Madour et al. | Jul 2001 | B1 |
6285750 | Brachman et al. | Sep 2001 | B1 |
6289025 | Pang et al. | Sep 2001 | B1 |
6295298 | Hrastar et al. | Sep 2001 | B1 |
6300947 | Kanevsky | Oct 2001 | B1 |
6304566 | Schessel | Oct 2001 | B1 |
6308221 | Perlman et al. | Oct 2001 | B1 |
6324279 | Kalmanek, Jr. et al. | Nov 2001 | B1 |
6330244 | Swartz et al. | Dec 2001 | B1 |
6333931 | LaPier et al. | Dec 2001 | B1 |
6345047 | Regnier | Feb 2002 | B1 |
6351464 | Galvin et al. | Feb 2002 | B1 |
6359881 | Gerszberg et al. | Mar 2002 | B1 |
6374296 | Lim et al. | Apr 2002 | B1 |
6385305 | Gerszberg et al. | May 2002 | B1 |
6396531 | Gerzberg et al. | May 2002 | B1 |
6397080 | Viktorsson et al. | May 2002 | B1 |
6404764 | Jones et al. | Jun 2002 | B1 |
6418139 | Akhtar | Jul 2002 | B1 |
6418216 | Harrison et al. | Jul 2002 | B1 |
6426955 | Gossett et al. | Jul 2002 | B1 |
6430276 | Bouvier et al. | Aug 2002 | B1 |
6438222 | Burg | Aug 2002 | B1 |
6438223 | Eskafi et al. | Aug 2002 | B1 |
6442266 | Wu | Aug 2002 | B1 |
6445922 | Hiller et al. | Sep 2002 | B1 |
6449766 | Fleming | Sep 2002 | B1 |
6452915 | Jorgensen | Sep 2002 | B1 |
6456621 | Wada et al. | Sep 2002 | B1 |
6459783 | March et al. | Oct 2002 | B1 |
6463146 | Hartley et al. | Oct 2002 | B1 |
6466570 | Low et al. | Oct 2002 | B1 |
6466964 | Leung et al. | Oct 2002 | B1 |
6467090 | Brodigan | Oct 2002 | B1 |
6473858 | Shimomura et al. | Oct 2002 | B1 |
6490274 | Kim | Dec 2002 | B1 |
6505348 | Knowles et al. | Jan 2003 | B1 |
6519249 | Bennefeld et al. | Feb 2003 | B1 |
6522880 | Verma et al. | Feb 2003 | B1 |
6526508 | Akins, III et al. | Feb 2003 | B2 |
6543051 | Manson et al. | Apr 2003 | B1 |
6546238 | Nightingale et al. | Apr 2003 | B1 |
6546488 | Dillon et al. | Apr 2003 | B2 |
6560203 | Baser et al. | May 2003 | B1 |
6560216 | McNiff et al. | May 2003 | B1 |
6563793 | Golden et al. | May 2003 | B1 |
6563915 | Salimando | May 2003 | B1 |
6570870 | Berstis | May 2003 | B1 |
6577644 | Chuah et al. | Jun 2003 | B1 |
6577718 | Kalmanek et al. | Jun 2003 | B1 |
6594254 | Kelly | Jul 2003 | B1 |
6606744 | Mikurak | Aug 2003 | B1 |
6611531 | Chen et al. | Aug 2003 | B1 |
6633635 | Kung et al. | Oct 2003 | B2 |
6651105 | Bhagwat et al. | Nov 2003 | B1 |
6654607 | Shobatake et al. | Nov 2003 | B1 |
6690663 | Culver | Feb 2004 | B1 |
6718021 | Crockett et al. | Apr 2004 | B2 |
6736017 | Mansky | May 2004 | B2 |
20020013941 | Ward, III et al. | Jan 2002 | A1 |
20030095542 | Chang et al. | May 2003 | A1 |
20050223115 | Hanson et al. | Oct 2005 | A1 |
Number | Date | Country |
---|---|---|
5968098 | Sep 1998 | AU |
2134132 | Jul 1995 | CA |
0 794 643 | Sep 1997 | EP |
0 800 325 | Oct 1997 | EP |
0 758 175 | Dec 1997 | EP |
0 841 831 | May 1998 | EP |
0 845 894 | Jun 1998 | EP |
0 848 560 | Jun 1998 | EP |
0 856 981 | Aug 1998 | EP |
0 905 959 | Mar 1999 | EP |
0 921 659 | Jun 1999 | EP |
WO 9518501 | Jul 1995 | WO |
WO 9714238 | Apr 1997 | WO |
WO 9716007 | May 1997 | WO |
WO 9737483 | Oct 1997 | WO |
WO 9746073 | Dec 1997 | WO |
WO 9747118 | Dec 1997 | WO |
WO 9747119 | Dec 1997 | WO |
WO 9747127 | Dec 1997 | WO |
WO 9801985 | Jan 1998 | WO |
WO 9807266 | Feb 1998 | WO |
WO 9811704 | Mar 1998 | WO |
WO 9818269 | Apr 1998 | WO |
WO 9819240 | May 1998 | WO |
WO 9819448 | May 1998 | WO |
WO 9819471 | May 1998 | WO |
WO 9824224 | Jun 1998 | WO |
WO 9830002 | Jul 1998 | WO |
WO 9836551 | Aug 1998 | WO |
WO 9841032 | Sep 1998 | WO |
WO 9851063 | Nov 1998 | WO |
WO 9852332 | Nov 1998 | WO |
WO 9852339 | Nov 1998 | WO |
WO 9853617 | Nov 1998 | WO |
WO 9854871 | Dec 1998 | WO |
WO 9914924 | Mar 1999 | WO |
WO 9916201 | Apr 1999 | WO |
WO 9944352 | Sep 1999 | WO |
WO 9953719 | Oct 1999 | WO |
WO 9962242 | Dec 1999 | WO |
Entry |
---|
WO98/45999 Shaheen et al., Wireless communication system that supports multiple standards, protocol and extended services, Oct. 15, 1998. |
Holiday, Clifford R., “The Residential Gateway”, IEEE Spectrum Magazine; May 1997, pp. 29-31. |
Meggers, J. et al., “Providing Video Conferencing for the Mobile User”, Local Computer Networks, Proceedings 21st IEE Conference, 1996, pp. 526-534. |
Umehira, M., et al. “Wireless and IP Integrated System Architectures for Broadband Mobile Multimedia Services”, Wireless Communications and Networking Conference, WCNC, 1999, IEEEE, 1999, pp. 593-597. |
Albrecht, Markus, et at, “IP Services Over Bluetooth: Leading the Way to a New Mobility”, IEEE 1999, pp. 2-11. |
Perkins, Charles E., “Mobile-IP, Ad-Hoc Networking, and Nomadicity”, IEEE 1996, pp. 472-476. |
Jacobs, Stuart, “Security of Current Mobile IP Solutions”, IEEE 1997, pp. 1122-1128. |
Deering, S., Internet RFC/STD/FYI/BCP Archives, Internet Protocol, Version 6 specification, Dec. 1995, Xerorx PARC, pp. 1-28. |
Justin J. Junkus, “Cable Telephony's Oxymoron”, Communication Technology, Aug. 1999, pp. 24-26. |
Evan Bass, “!P Telephony: The Race Heats Up—Vendors, Start Your Engines”, Communications Technology, Aug. 1999, pp. 48-50 & 52-55. |
Justin J. Junkus, “SuperComm Highlights IP Telephony”, Communication Technology, Aug. 1999, pp. 72, 74, 76, 78, 79. |
Fred Dawson, “Lighting a fire under IP telephony”, CED Oct. 1999, pp. 46-56. |
Mark Komanecky, “Solving IP Provisioning Challenges”, CED, Oct. 1999, pp. 82-88. |
Brad Shewmake, “Microsoft teams With Nortel to offer Internet call waiting”, InfoWorld Media Group, Inc., Oct. 28, 1999, 1 page. |
Lee Williams, “IP-Ready Cable Telephony”, Arris Interactive brochure, Nov. 1998, 4 sheets. |
H.323, Version 2.0 “A Primer on the H.323 Series Standard”, DataBeam May 15, 1998, pp. 1-16. |
“S-A Wins Thinnovation Award”, Channel Surfing, Broadband Magazine, p. 28, Jan. 15, 2014. |
Robert Pease, “TCI Contracts for Fiber-To-The-Curb Application”, Lightwave, Nov. 1998, p. 27. |
Broadband Access Systems, Inc. web site, Broadband Access Systems, Inc. 1998. |
Samsung, “New Standard for Communications, Web Video Phone” brochure, Samsung Electronics, 1998. |
Antec, “Cornerstone: Picture Immediate Revenues for Your Network” brochure, Arris/Nortel Company, Jan. 15, 2014. |
Smart Works, “Smart Works ™Call Agent”, taken from 222.xybridge.com/ca•detailed2.htm, printed Oct. 4, 1999. |
Colin Low, “The Internet Telephony Red Herring”, Hewlett Packard, Article, 1996, pp. 1-15. |
S. Harris, et al., “Intelligent Network Realization and Evolution: CCITT Capability Set I and Beyond,” International Switching Symposium, Yokohama, Japan, Diversification and Integration of Networks and Switching Technologies Towards the 21st Century, Oct. 25-30, 1992, Proceedings vol. 2, pp. 127-131. |
IBM Technical Disclosure Bulletin, “Workstation Communications System”, vol. 37, No. 9, Sep. 1994, pp. 101-104. |
C. Yang, Memo, Internet RFC/STD/FYI/BCP Archives, RFC1789, “INETPhone: Telephone Services and Servers on Internet,” University of North Texas, Apr. 1995, 5 pages. |
N. Miller, “State of the Art Dial 1-800-Internet”, Byte, Feb. 1996, pp. 83, 84, 86 and 88. |
R. Babbage, et al., “Internet Phone—changing the telephony paradigm?”, BT Technol J, vol. 15, No. 2, Apr. 1997, pp. 145-157. |
I. Naoko, et al., Abstract, “Voice Communications System and Voice Communication Method”, Hitachi, Ltd., Application No. 05343162, filed Dec. 15, 1993. |
M. Koji, Abstract, “Conversation/Data Alternate Communication Equipment”, Oki Electric Ind. Co., Ltd., Application No. 05004142, filed Jan. 13, 1993. |
W. Voigt, Abstract, “Incoming Call Indication to Data Terminal User—by Giving Engaged Data User Visual Display on Screen Wilst calling Party Receives Announcement”, Telefonbau & Normalzeit GMBH (Teln), Jan. 15, 2014. |
K. Sultan, Abstract, “Call Waiting Method for Modem—Involves Displaying Signal Indicating Calls Waiting on User Screen, and Accepting Commands from User to Place Both Modems on Hold so User Can Answer Telephone Call”, Jan. 15, 2014. |
Edell, R. et al., “Providing Internet Access: What we Learn from INDEX Trial”, downloaded Berkeley Univ., http://www.INDEX Berkeley.EDU/reports/99-010W, pp. 1-17, Apr. 1999. |
Patel, A. et al., “A Technique for Multi-Network Access to Multimedia Messages”, Computer Communications, vol. 20, No. 5, pp. 324-337, Jul. 1997. |
Canadian Patent Application No. 2,134,132, Jul. 7, 1995, pp. 23. |
Japanese Patent Abstract Publication No. 1 0-032643, published Feb. 3, 1998, pp. 31. |
Japanese Patent Laid Open Publication No. Hei 6-334680, published Dec. 2, 1994, pp. 9. |
Japanese Patent Laid Open Publication No. Hei 10-70566, published Mar. 16, 1989, pp. 10. |
Japanese Patent Laid Open Publication No. Hei 11-225169, published Aug. 17, 1999, pp. 11. |
Altmann, et al., INDEX Project: User Support for Buying QoS with Regard to User's Preferences, IEEE, pp. 101-104, 1998. |
Dalgic, I. et al., “True Number Portability and Advanced Call Screening in a SIP-Based IP Telephony System”, IEEE Communication Magazinepp. 2-20, Jul. 1999. |
Doeringer et al., “Access architecture for a multiprotocol broadband backbone”, Computer Networks and ISDN Systems 29 (1997), Elsevier Science B.V., pp. 137-155. |
Preliminary Amendment dated Feb. 24, 2009 in U.S. Appl. No. 12/391,828, pp. 10. |
Office Action dated Dec. 6, 2010 in U.S. Appl. No. 12/391,828, pp. 9. |
Amendment dated Mar. 31, 2011 in U.S. Appl. No. 12/391,828, pp. 21. |
Terminal Disclaimer dated Mar. 31, 2011 in U.S. Appl. No. 12/391,828 over U.S. Pat. No. 7,496,190, p. 1. |
Terminal Disclaimer dated Mar. 31, 2011 in U.S. Appl. No. 12/391,828 over U.S. Pat. No. 6,937,713, p. 1. |
Notice of Allowance dated Jun. 17, 2011 in U.S. Appl. No. 12/391,828, pp. 7. |
Examiner's Interview Summary dated Jun. 17, 2011 in U.S. Appl. No. 12/391,828, pp. 2. |
Notice of Allowance dated Sep. 12, 2011 in U.S. Appl. No. 12/391,828, pp. 18. |
Applicant's Interview Summary with Examiner dated Sep. 23, 2011 in U.S. Appl. No. 12/391,828, p. 1. |
Office Action dated May 30, 2013 in U.S. Appl. No. 13/278,923, pp. 10. |
Amendment dated Sep. 27, 2013 in U.S. Appl. No. 13/278,923, pp. 12. |
Three Terminal Disclaimers, all dated Sep. 27, 2013 in U.S. Appl. No. 13/278,923, pp. 6. |
Examiner's Interview Summary dated Oct. 15, 2014 in U.S. Appl. No. 13/278,923, p. 1. |
Notice of Allowance dated Oct. 15, 2014 in U.S. Appl. No. 13/278,923, pp. 15. |
Amendment dated Jan. 10, 2014 in U.S. Appl. No. 13/278,923, pp. 7. |
Response to Amendment dated Jan. 17, 2014 in U.S. Appl. No. 13/278,923, pp. 2. |
Amendment dated Jan. 13, 2014 in U.S. Appl. No. 13/278,923, pp. 7. |
Response to Amendment dated Jan. 24, 2014 in U.S. Appl. No. 13/278,923, pp. 2. |
U.S. Appl. No. 12/391,828, filed Feb. 24, 2009 by Fen-Chung Kung et al., pp. 59. |
U.S. Appl. No. 11/133,030, filed May 20, 2005 by Fen-Chung Kung et al., pp. 59. |
Office Action dated Jul. 27, 2006 in U.S. Appl. No. 11/133,030, pp. 7. |
Amendment dated Dec. 28, 2006 in U.S. Appl. No. 11/133,030, pp. 12. |
Final Office Action dated Mar. 12, 2007 in U.S. Appl. No. 11/133,030, pp. 8. |
Amendment dated Jun. 15, 2007 in U.S. Appl. No. 11/133,030, pp. 25. |
Office Action dated Jul. 23, 2007 in U.S. Appl. No. 11/133,030, pp. 8. |
Amendment dated Nov. 23, 2007 in U.S. Appl. No. 11/133,030, pp. 13. |
Office Action dated Feb. 27, 2008 in U.S. Appl. No. 11/133,030, pp. 8. |
Amendment dated Jun. 30, 2008 in U.S. Appl. No. 11/133,030, pp. 11. |
Terminal Disclaimer dated Jun. 30, 2008 in U.S. Appl. No. 11/133,030, p. 1. |
Terminal Disclaimer Review Decision dated Aug. 7, 2008 in U.S. Appl. No. 11/133,030, p. 1. |
Notice of Allowance dated Oct. 15, 2008 in U.S. Appl. No. 11/133,030, pp. 7. |
Supplemental Notice of Allowance dated Nov. 26, 2008 in U.S. Appl. No. 11/133,030, pp. 5. |
U.S. Appl. No. 09/475,144, filed Dec. 30, 1999 by Fen-Chung Kung et al., pp. 69. |
Preliminary Amendment dated Oct. 10, 2001 in U.S. Appl. No. 09/475,144, pp. 13. |
Office Action dated Jul. 31, 2002 in U.S. Appl. No. 09/475,144, pp. 8. |
Amendment dated Oct. 31, 2002 in U.S. Appl. No. 09/475,144, pp. 14. |
Amendment dated Dec. 5, 2002 in U.S. Appl. No. 09/475,144, pp. 17. |
Final Office Action dated Feb. 26, 2003 in U.S. Appl. No. 09/475,144, pp. 8. |
Amendment dated Apr. 30, 2003 in U.S. Appl. No. 09/475,144, pp. 8. |
Office Action dated Jul. 2, 2003 in U.S. Appl. No. 09/475,144, pp. 8. |
Amendment dated Oct. 27, 2003 in U.S. Appl. No. 09/475,144, pp. 16. |
Notice of Allowance dated Mar. 24, 2005 in U.S. Appl. No. 09/475,144, pp. 6. |
Preliminary Amendment dated Jul. 23, 2009 in U.S. Appl. No. 12/391,828, pp. 10. |
Terminal Disclaimer Review Decision dated Apr. 18, 2011 in U.S. Appl. No. 12/391,828, p. 1. |
Singh, Raj K. et al., “A Programmable HIPPI Interface for a Graphics Supercomputer”, ACM Special Interest Group on Computer Architecture, 1993,0/8186-4340-4,pp. 124-132. |
Indiresan, Atri et al., “The End: A Network Adapter Design Tool”, Seventeenth Annual Joint Conference of Computer and Communications Societies, Proceedings, IEEE 0-78034383-2, 1998, pp. 756-764. |
Number | Date | Country | |
---|---|---|---|
20140126429 A1 | May 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13278923 | Oct 2011 | US |
Child | 14155871 | US | |
Parent | 12391828 | Feb 2009 | US |
Child | 13278923 | US | |
Parent | 11133030 | May 2005 | US |
Child | 12391828 | US | |
Parent | 09475144 | Dec 1999 | US |
Child | 11133030 | US |