Source: http://www.google.com/patents/US8233491?dq=%22frederick+douglis%22
Timestamp: 2016-10-25 14:50:25
Document Index: 606932250

Matched Legal Cases: ['Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 200780023103', 'Application No. 200780023103', 'Application No. 07', 'Application No. 07', 'Application No. 07']

Patent US8233491 - Embedded media terminal adapter (EMTA) endpoint redirect mode - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsSystems and methods are disclosed for enabling an embedded media terminal adapter (EMTA) with included MIB objects to redirect a received telephone call. Based on the MIB objects, the EMTA communicates with a cable modem termination system (CMTS) to set up two service flows where one flow is set up between...http://www.google.com/patents/US8233491?utm_source=gb-gplus-sharePatent US8233491 - Embedded media terminal adapter (EMTA) endpoint redirect modeAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS8233491 B2Publication typeGrantApplication numberUS 11/536,024Publication dateJul 31, 2012Priority dateSep 28, 2006Fee statusPaidAlso published asCA2664706A1, CA2664706C, EP2074750A2, US20080080690, WO2008039719A2, WO2008039719A3Publication number11536024, 536024, US 8233491 B2, US 8233491B2, US-B2-8233491, US8233491 B2, US8233491B2InventorsJames M. Burns, JR.Original AssigneeBurns Jr James MExport CitationBiBTeX, EndNote, RefManPatent Citations (84), Non-Patent Citations (49), Referenced by (6), Classifications (13), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetEmbedded media terminal adapter (EMTA) endpoint redirect mode
US 8233491 B2Abstract
Systems and methods are disclosed for enabling an embedded media terminal adapter (EMTA) with included MIB objects to redirect a received telephone call. Based on the MIB objects, the EMTA communicates with a cable modem termination system (CMTS) to set up two service flows where one flow is set up between two EMTAs and one flow is set up between the endpoint EMTA and the NOC.
downloading, to a computing device, management information base (MIB) objects, wherein a first MIB object specifies a redirect address and a second MIB object specifies enabling a redirect mode;
storing the MIB objects a MIB objects table, wherein each MIB object is stored with an associated operation identification number, wherein the operation identification number associated with the first MIB object is a numerical representation of the redirect address and the operation identification number associated with the second MIB object is a numerical representation of the redirect mode;
receiving a redirect enable signal and the redirected address at a desired endpoint;
receiving a call signal at the desired endpoint;
based on the redirect enable signal, redirecting voice packets associated with the call signal to the redirected address according the redirect mode, and
receiving a redirect disable signal at the desired endpoint, wherein receiving the redirect disable signal at the desired endpoint comprises:
receiving a third MIB object at the desired endpoint, wherein the third MIB object specifies the disabling of the redirect mode, and
replacing the second MIB object with the third MIB object.
2. The method of claim 1, further comprising the steps of: setting up two service flows for the voice packets, wherein a first service flow is between the desired endpoint and the redirected address and a second service flow is between the desired endpoint and an originating endpoint.
receiving a hang up signal from the redirected endpoint; and
terminating the two service flows.
4. The method of claim 2, wherein the originating endpoint is one of a telephone, computer softphone, and wireless telephone.
5. The method of claim 1, further comprising the step of transmitting the call signal from the desired endpoint to at least one of a coupled telephone and computer softphone of the call signal.
6. The method of claim 1, further comprising the step of creating a connection between an originating endpoint and the desired endpoint.
7. The method of claim 6, further comprising the step of deleting the connection upon receiving a hang up signal.
8. An embedded media terminal adapter (EMTA) comprising:
management information base (MIB) objects, wherein a first MIB object specifies a redirect address, a second MIB object specifies enabling a redirect mode, and a third MIB object specifies disabling of the redirect mode, wherein the MIB objects are stored in a MIB objects table, wherein each MIB object is stored with an associated operation identification number, wherein the operation identification number associated with the first MIB object is a numerical representation of the redirect address and the operation identification number associated with the second MIB object is a numerical representation of the redirect mode; and
receiving a call signal from an originating endpoint and for redirecting voice packets associated with the call signal to the redirected address according the redirect mode, and
replacing the second MIB object with the third MIB object for disabling the redirect mode.
9. The EMTA of claim 8, wherein the processor is further configured for transmitting a signal to a cable modem termination system (CMTS) for setting up two service flows.
10. The EMTA of claim 9, wherein the CMTS responds to the EMTA with the two service flows, wherein a first service flow is between the EMTA and the redirected address and a second service flow is between the EMTA and the originating endpoint.
11. The EMTA of claim 9, wherein the voice packets associated with the call signal freely flow across the two service flows.
12. The EMTA of claim 9, wherein upon receiving a hang up signal, the EMTA for transmitting a hang up signal to the CMTS for deleting the two service flows.
13. The EMTA of claim 8, wherein upon receiving a MIB object specifying normal call processing, the processor for receiving voice packets from a call and for forwarding the voice packets to at least one of a coupled telephone, computer softphone, and wireless telephone.
an embedded media terminal adapter (EMTA) for:
receiving management information base (MIB) objects from an operations center, wherein a first MIB object specifies a redirect address, a second MIB object specifies enabling a redirect mode, and a third MIB object specifies disabling the redirect mode,
receiving a call signal from an originating endpoint,
redirecting voice packets associated with the call signal to the redirected address, wherein the MIB objects are stored in a MIB objects table, wherein each MIB object is stored with an associated operation identification number, wherein the operation identification number associated with the first MIB object is a numerical representation of the redirect address and the operation identification number associated with the second MIB object is a numerical representation of the redirect mode, and
15. The communications system of claim 14, further comprising: a CMTS for setting up two service flows in response to an EMTA dynamic service add signal, wherein a first service flow is between the EMTA and the redirected address and a second service flow is between the EMTA and the originating endpoint.
16. The communications system of claim 15, wherein the voice packets associated with the call signal freely flow across the two service flows.
17. The communications system of claim 14, wherein upon receiving a hang up signal, the EMTA for transmitting a hang up signal to the CMTS for deleting the two service flows.
18. The communications system of claim 14, wherein analysis of the voice packets received by the redirected address is performed.
19. The communications system of claim 14, the EMTA for transmitting the voice packets to at least one of a coupled telephone, computer softphone, and wireless telephone, and for transmitting voice packets received from the at least one of the coupled telephone, computer softphone, and wireless telephone to the redirected address and the originating endpoint.
20. The communications system of claim 14, the EMTA for receiving a MIB object specifying normal call processing, wherein the EMTA receives voice packets from a call and forwards the voice packets to a coupled telephone, and wherein the EMTA forwards voice packets received from the coupled telephone to the originating endpoint. Description
This invention relates in general to voice over Internet Protocol systems over broadband, more specifically broadband over coaxial cable, and more particularly, to the field of enabling a media terminal adapter to redirect a telephone call to a second endpoint.
Multiple services operators (MSOs) are now capable of providing many services in addition to broadcast audio/video signals over their existing systems. Some advanced services in a broadband communications system provide conventional cable television signals along with other telephony services, such as high-speed data and telephone. To support these additional services, cable modems and media terminal adapters (MTAs), which is also known as embedded media terminal adapters (EMTAs) when the cable modem is included in an MTA, are used in the subscriber's premises and have typically been coupled with coaxial cable to a communications network. U.S. Pat. No. 6,161,011 to Loveless, the disclosure and teachings of which are incorporated herein by reference, shows an example of a hybrid fiber/coaxial (HFC) communications network that could be used to implement the present invention.
Public switched telephone networks (PSTNs) traditionally carry voice signals using a circuit-switched infrastructure. This infrastructure lends itself easily to a Network Operation Center (NOC) intercepting a call that is in progress at multiple points throughout the network to assess the voice quality. On the other hand, a Voice over Internet Protocol (VoIP) network in a broadband communications system uses IP packets to route telephone calls. Due to the nature of IP packet routing, which can take many different paths in the system, it is extremely difficult to intercept a call and determine possible problems.
Thus, there exists a need for a more efficient system and method of intercepting a telephone call in a VoIP communications system.
FIG. 1 is a block diagram of a PSTN and a VoIP communications system that are suitable for transmitting voice and data signals.
FIG. 2 is a block diagram of the VoIP communications system of FIG. 1 including call routing equipment that is suitable for use in the present invention.
FIG. 3 is a block diagram of a subscriber's premise including an EMTA coupled to telephones and a computer that is suitable for use in the system of FIG. 2.
FIG. 4 is a block diagram of the EMTA of FIG. 3.
FIG. 5 is a table illustrating management information base (MIB) objects table in accordance with the present invention.
FIG. 6 is a block diagram illustrating a conventional call flow throughout the VoIP communications system of FIG. 2.
FIG. 7 is an abridged illustration of steps included in the conventional call flow of FIG. 6.
FIG. 8 is a block diagram illustrating a redirected call flow throughout the VoIP communications system of FIG. 2 in accordance with the present invention.
FIG. 9 is an abridged illustration of steps included in the redirected call flow of FIG. 8 in accordance with the present invention.
The present invention is directed towards enabling a destination EMTA, i.e., an endpoint EMTA, to redirect a received telephone call in a VoIP communication system. MIB objects are downloaded to the endpoint EMTA specifying a redirected endpoint address, e.g., a NOC or other customer service department, and a control function, which enables the redirect mode. Accordingly, a technician in the NOC is able to receive the redirected voice packets of a phone call. In this manner, a technician is able to troubleshoot the call in order to determine any quality problems.
FIG. 1 is a block diagram of a PSTN 105 and a VoIP communications system 110 that are suitable for transmitting voice and data signals. The VoIP communications system 110 typically includes a managed Internet Protocol (IP) network 115 and a plurality of HFC networks, where only one HFC network 120 is shown. A headend facility 125 transmits, receives, and manages video, audio, and data signals with a plurality of headend equipment. In a VoIP communications system 110, voice packets are routed throughout the IP network 115 to various HFC networks via a connected hub 130 depending upon a destination address(es). Optical fiber 135 transports the voice packets to an optical node 140 for conversion into electrical signals. Coaxial cable 145 then delivers the converted electrical signal containing voice packets to an intended subscriber 150 a-d. As mentioned, operators are generally able to intercept voice packets at multiple points throughout the PSTN 105 due to the nature of the circuit-switched environment. In contrast, operators are not able to intercept voice packets as readily in a VoIP system 110 due to the many different routes voice packets may take throughout the system 110, as well as far-end echo that prohibits proper analyzing of the voice packets.
FIG. 2 is a block diagram of the VoIP communications system 110 of FIG. 1 including call routing equipment that is suitable for use in the present invention. Routing equipment includes a plurality of CMTSs 205 a-b that connects to all cable modems or EMTAs in the system 110. The CMTSs 205 a-b are also the connectivity point between the IP network 115 and an HFC network 120 a-b. A call management server (CMS) 210, also known as a softswitch, controls the video and audio call connections. Additionally, a NOC 215, or other customer service organization, includes people and other technical equipment in order to service the VoIP communications system 110.
FIG. 3 is a block diagram of a subscriber's premise 150 a including an EMTA 320 coupled to telephones 325 and a computer 330 that is suitable for use in the system of FIG. 2. A radio frequency (RF) splitter 310 receives the incoming signals and routes the signals to a DHCT 315 and an EMTA 320. The DHCT 315 processes cable television packets for display subsequent display on a television. The EMTA 320 processes and routes all received voice and data packets to an appropriate endpoint telephone 325 and/or computer 330.
FIG. 4 is a more detailed block diagram of the EMTA of FIG. 3. A coaxial F connector 410 connects the EMTA 320 to the VoIP communications system 110. A tuner 415 then receives and filters data intended for the EMTA 320 and routes the data to a processor 420. If the data is intended for a coupled computer, the processor 420 routes the data to either an Ethernet connector 435 or a USB connector 440 depending upon the application. If the data is telephony data, the data is routed to a telephony digital signal processor (DSP) 445 for further processing, such as code decoding, packetization, echo cancellation, or other telephone signal processing. The telephony data is then routed to a connected telephone 325 and/or computer softphone 330 via a subscriber line interface chip (SLIC) 450. The telephone 325 and computer 330 are typically connected to the EMTA 320 with CAT-3 or CAT-5 wiring and an RJ11 telephone jack 455. The EMTA 320 also includes a power supply 460 for powering the telephony DSP 445 and the SLICs 450 as well as memory 425, such as SDRAM and Flash memory, for system storage purposes.
FIG. 5 is a table illustrating management information base (MIB) objects table 500 in accordance with the present invention. The MIB objects table 500 generally may be included in non-volatile memory of the EMTA 320 or it may be a downloadable configuration file. In the present invention, a subscriber 150 b that may be experiencing audio problems may have a MIB objects downloaded to their EMTA 320. The downloaded MIB objects and the associated operation identification number (OID) 510, i.e., the object's numbering scheme, are stored in the MIB objects table 500. Accordingly, a first MIB object 515 designating an EMTA redirect address is given an IP address of the NOC. A second MIB object 520 enables redirected mode. The redirect mode may be disabled by downloading another MIB object returning the control function 520 to normal call processing.
FIG. 6 is a block diagram illustrating a conventional call flow throughout the VoIP communications system 110, and FIG. 7 is an abridged illustration of steps included in the conventional call flow of FIG. 6. Referencing FIGS. 6 and 7, when an originating subscriber 150 a initiates placing a call from either a telephone 325 or a computer softphone in step 705, the subscriber's EMTA 320 a may identify and verify a dialed valid number by an included digit map. Alternatively, the CMS 210 may perform this function. Once verified, the EMTA 320 a builds a packet that contains information about the EMTA 320 a and the number dialed. Also included in the packet is a destination IP address of the CMS 210. Accordingly, the packet is routed to the subscriber's CMTS 205 a and then on to the CMS 210. The CMS 210 searches a database to determine the CMTS that serves the destination dialed telephone and then routes the voice packets through the IP network 115 to the correct hub 130 b, which routes the voice packets to the determined CMTS 205 b. The CMS 210 then creates a connection (CRCX) in step 710 with the destination EMTA 150 b, i.e., endpoint EMTA, in step 710. The endpoint EMTA 150 b sets up a dynamic service add (DSA) in step 715, which sets up a service flow with its associated CMTS 205 b. The CMTS 205 b sends a response in step 720 that is acknowledged by the endpoint EMTA 150 b in step 725. The endpoint EMTA 150 b then sends an acknowledgement of the last command in step 730 to the CMS 210, and an open line of communication is then set up between the callers 150 a, 150 b allowing for the voice packets to be freely transmitted using real time protocol (RTP) in step 735.
In step 740, when the call is over, a notify hang up signal is sent from the endpoint EMTA 150 b to the CMS 210. The CMS 210 in steps 745 and 750 acknowledges the command and deletes the connection (DLCX). The endpoint EMTA 150 b acknowledges the DLCX command in step 755 and, in step 760, sends a dynamic service delete (DSD) to the CMTS 250 b deleting the service. The CMTS 250 b responds in step 765, and the endpoint EMTA 150 b acknowledges in step 770, thereby ending the call.
FIG. 8 is a block diagram illustrating a redirected call flow throughout the VoIP communications system of FIG. 2, and FIG. 9 is an abridged illustration of steps included in the redirected call flow of FIG. 8 in accordance with the present invention. Referencing FIGS. 8 and 9, an originating subscriber 150 a initiates a call in step 905. After verifying the dialed number, the subscriber's EMTA 320 a builds a packet that contains information about the EMTA 320 a and the number dialed. Also included in the packet is a destination IP address of the CMS 210. Accordingly, the packet is routed to the subscriber's CMTS 205 a and then on to the CMS 210. The CMS 210 searches a database to determine the CMTS that serves the destination dialed telephone and then routes the voice packets through the IP network 115 to the correct hub 130 b, which routes the voice packets to the determined CMTS 205 b. The CMS 210 then creates a connection (CRCX) in step 910 with the endpoint EMTA 150 b in step 710.
In accordance with the present invention, MIB object enabling the redirected mode along with the NOC address are downloaded to the endpoint EMTA 150 b. Accordingly, the endpoint EMTA 150 b relays the CRCX command to the NOC 215 in step 915, and the NOC sends an acknowledgement in step 920. The endpoint EMTA 150 b then sets up two dynamic service adds (DSAs) in step 925, which sets up two separate service flows with its associated CMTS 205 b first with the calling endpoint 150 a and a second service flow with the NOC 215. The CMTS 205 b sends a response for the two service flows in step 930 that is acknowledged by the endpoint EMTA 150 b in step 935. The endpoint EMTA 150 b then sends an acknowledgement of the last command in step 940 to the CMS 210. In steps 945 and 950, an open line of communication is then set up between the endpoint EMTA 150 b and the NOC 215 to route RTP voice packets; in addition, a relay is set up allowing for the voice packets to be relayed between the endpoint EMTA 150 b and the originator 150 a. In this manner, the NOC 215 receives all voice packets for analyzing.
In step 960, when the call is over, a notify hang up signal is sent from the endpoint EMTA 150 b to the CMS 210. The CMS 210 in steps 965 and 970 acknowledges the command and deletes the connection (DLCX). The endpoint EMTA 150 b acknowledges the DLCX command in step 975 and, in step 980, the NOC 215 sends an acknowledgement signal. The endpoint EMTA 150 b sends a dynamic service delete (DSD) to the CMTS 250 b deleting the two services in step 985. The CMTS 250 b responds in step 990, and the endpoint EMTA 150 b acknowledges in step 995, thereby ending the call.
It will be appreciated that a solution to redirecting a call cannot be accomplished with conventional call forwarding. Call forwarding instructions are handled with the CMS 210, not with the EMTA 150 a-d. Accordingly, a call initiated by a subscriber with an initiating EMTA 150 a is routed to the appropriate endpoint by the CMS 210. The CMS 210 determines that the desired endpoint subscriber 150 b has enabled call forwarding and immediately responds to the initiating EMTA 150 a to route the call to the forwarded number not the endpoint EMTA 150 b. At this point, the NOC 215 cannot determine any issues that the endpoint EMTA 150 b may be experiencing since the call is not routed to that point.
Accordingly, systems and methods have been provided that enables an EMTA to redirect calls in order for reasons such as testing and troubleshooting. It is understood that though the examples described in the description are directed towards an on-net call, i.e., calls within the VoIP communications system 110, the system and methods described also apply to an off-net call, i.e., a call received from the PSTN 105. Additionally, careful attention to security should be required due to the redirecting of telephone calls. It will be appreciated that further embodiments are envisioned that implement the invention, for example, using all software or adding modes for additional features and services.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5544235Nov 23, 1994Aug 6, 1996At&T Corp.Identification of called directory number at multiple directory number per line premises prior to ringing signal receptionUS5546447Jun 29, 1994Aug 13, 1996Intel CorporationDisplaying caller identification information in a computer systemUS5666399 *Mar 31, 1995Sep 9, 1997Lucent Technologies Inc.Software architecture for providing communication features to different types of wireless telephones via different communication switching systemsUS5684988 *Jul 22, 1994Nov 4, 1997Bay Networks, Inc.MIB database and generic popup window architectureUS5699419Dec 20, 1994Dec 16, 1997Lucent Technologies Inc.Analog multibutton telephone keysetsUS5799060May 16, 1996Aug 25, 1998Harris CorporationMulti-port caller ID-based telephone ringback test deviceUS5937034Jun 6, 1997Aug 10, 1999Harris CorporationMethod for testing call waiting, caller ID functionality of telephone lineUS6005921Aug 28, 1997Dec 21, 1999Harris CorporationTelephone ringback test device and methodUS6324263Aug 31, 1998Nov 27, 2001Dialogic CorporationDigital telephone system with automatic routing based upon caller IDUS6898274Sep 21, 1999May 24, 2005Nortel Networks LimitedMethod and apparatus for adaptive time-based call routing in a communications systemUS6937713 *Dec 30, 1999Aug 30, 2005At&T Corp.IP call forward profileUS6940866Apr 3, 2000Sep 6, 2005TekelecEdge device and method for interconnecting SS7 signaling points(SPs) using edge deviceUS6985492Nov 3, 2000Jan 10, 2006Broadcom CorporationVoice gateway with voice synchronizationUS7002995Jun 14, 2001Feb 21, 2006At&T Corp.Broadband network with enterprise wireless communication system for residential and business environmentUS7006479 *Nov 28, 2000Feb 28, 2006Cisco Technology, Inc.System and method of a wireless network operation and maintenanceUS7010002Jun 14, 2001Mar 7, 2006At&T Corp.Broadband network with enterprise wireless communication method for residential and business environmentUS7068757Apr 24, 2000Jun 27, 2006Agilent Technologies, Inc.Apparatus and method for automated testing of the quality of voice communications over data networksUS7103067Dec 21, 2001Sep 5, 2006Cisco Technology, Inc.Mechanism for translating between two different voice-over-IP protocolsUS7116771Mar 6, 2003Oct 3, 2006General Instrument CorporationMethod for generalization of telephone signaling requirements to support multiple international marketplaces in a single customer premises deviceUS7123692Sep 15, 2003Oct 17, 2006Atkinson Douglas ACraft menu system using caller ID functionality for installation and testingUS7145887 *Jul 2, 2001Dec 5, 20063Com CorporationCommunication of packet arrival times to cable modem termination system and uses thereofUS7263111 *Aug 5, 2002Aug 28, 2007Alcatel LucentSystem and method for interconnecting different SS7 network domainsUS7280532Jul 3, 2002Oct 9, 2007Lg Electronics Inc.Call set-up method using SIP-T overlap signalingUS7295566 *May 9, 2003Nov 13, 2007Nortel Networks Ltd.SVC signaling system and methodUS7333492Aug 31, 2004Feb 19, 2008Innomedia Pte LtdFirewall proxy system and methodUS7447780May 11, 2004Nov 4, 2008Time Warner Cable, Inc.Technique for communicating information over a broadband communications networkUS7502457Feb 28, 2002Mar 10, 2009At&T Intellectual Property I, L.P.Outbound call rules routingUS7505759Jun 21, 1999Mar 17, 2009Alcatel-Lucent Usa Inc.System for message control and redirection in a wireless communications networkUS7701954May 12, 2004Apr 20, 2010Broadcom CorporationGateway with voiceUS7860230Dec 13, 2004Dec 28, 2010Martin Bradley JTelephone call screening and routing device and related methodUS20010055376May 17, 2001Dec 27, 2001Gregg KarasNo caller ID call blockUS20020106017Feb 2, 2001Aug 8, 2002Dombkowski Kevin EugeneMethod for transmitting signals over a cable protocolUS20020114431Aug 1, 2001Aug 22, 2002Mcbride Mark A.Caller control systemUS20020150081 *Apr 12, 2001Oct 17, 2002General Instrument CorporationMethod and apparatus for monitoring voice conversations from customer premises equipmentUS20030007617Jul 5, 2001Jan 9, 2003Mcalinden PaulDelivering calls using calendar informationUS20030046427 *Apr 22, 2002Mar 6, 2003Goringe Christopher M.Topology discovery by partitioning multiple discovery techniquesUS20030097438 *Oct 15, 2002May 22, 2003Bearden Mark J.Network topology discovery systems and methods and their use in testing frameworks for determining suitability of a network for target applicationsUS20030108176 *Dec 30, 1999Jun 12, 2003Fen-Chung KungPersonal ip follow-me serviceUS20040008724 *May 2, 2003Jan 15, 2004Geoffrey DevineCommunications switching architectureUS20040028208Aug 6, 2002Feb 12, 2004Carnazza James M.System and method for dynamically routing communicationsUS20040066913Jun 27, 2003Apr 8, 2004Harris CorporationDynamic, automated double-ended system and method for testing and qualifying metallic telecommunication loopsUS20040090968Nov 8, 2002May 13, 2004Gary KimberMethod and apparatus for associating a media terminal adapter with a cable modem in an HFC networkUS20040114747 *Jun 13, 2003Jun 17, 2004Trandal David S.Systems and methods for call processingUS20040151202 *Jan 31, 2003Aug 5, 2004Mandavilli Swamy J.Method and apparatus for discovering topology information in a networkUS20040170268 *Dec 5, 2003Sep 2, 2004Shigeaki HakusuiVirtual PBX based on SIP and feature serversUS20040208177 *May 4, 2004Oct 21, 2004Tetsuo OgawaSemiconductor circuit device, packet processing method, management system, management method and packet processing methodUS20040249927 *Jul 1, 2004Dec 9, 2004David PezuttiIntelligent network providing network access services (INP-NAS)US20050018651Jul 22, 2003Jan 27, 2005Innomedia Pte Ltd.Stand alone multi-media terminal adapter with network address translation and port partitioningUS20050047423Aug 29, 2003Mar 3, 2005Kaul Bharat B.Protocol interworking frameworkUS20050078689 *Oct 10, 2003Apr 14, 2005Adc Broadband Access Systems, Inc.Providing multimedia services over a cable networkUS20050114518 *May 11, 2004May 26, 2005Mcmahon Stephen J.Technique for communicating information over a broadband communications networkUS20050180393Feb 17, 2004Aug 18, 2005Skubisz Michael A.Providing advanced call features to an analog telephone using a media gatewayUS20050190891 *Feb 27, 2004Sep 1, 2005Idt CorporationSystems and methods for quality measurements of digital networksUS20050198391Feb 13, 2004Sep 8, 2005Coldren Rex A.Method and apparatus for transmitting frequency shift key data in a packetized formatUS20050216949Mar 23, 2005Sep 29, 2005Ray CandeloraSystems and methods for a universal media server with integrated networking and telephonyUS20060285487 *Sep 20, 2005Dec 21, 2006Fujitsu LimitedApparatus and method for detecting network failureUS20060291643Jun 9, 2005Dec 28, 2006John PfaffDial plan generatorUS20070133516Dec 14, 2005Jun 14, 2007General Instrument CorporationMethod and apparatus for selecting a codec in a packet-switched communication networkUS20070133776Dec 13, 2005Jun 14, 2007Cisco Technology, Inc.Communication system with configurable shared line privacy featureUS20070140445Dec 18, 2006Jun 21, 2007Brother Kogyo Kabushiki KaishaCommunication ApparatusUS20070198681Feb 17, 2006Aug 23, 2007TekelecMethods, systems, and computer program products for transaction-based internet protocol (IP) telephony call processingUS20070201473Sep 29, 2006Aug 30, 2007Medhavi BhatiaQuality of Service Prioritization of Internet Protocol Packets Using Session-Aware ComponentsUS20070201481Sep 29, 2006Aug 30, 2007Medhavi BhatiaMultistage Prioritization of Packets Within a Session Over Internet Protocol (SOIP) NetworkUS20070218866Mar 15, 2006Sep 20, 2007Maciver William GInstallation of a personal emergency response systemUS20070274213 *Sep 7, 2004Nov 29, 2007France TelecomMethod and System For the Transfer of Communication Network Administration InformationUS20070297384Jun 22, 2006Dec 27, 2007Burns James MMedia terminal adapter (mta) initialization process display by use of an embedded caller name and caller identificationUS20080043927Oct 26, 2007Feb 21, 2008Verizon Communications Inc.Automated telephone line test apparatus with intelligent diagnostic functionUS20080043970Aug 1, 2006Feb 21, 2008Scholes Bryan WMedia terminal adapter (mta) routing of telephone calls based on caller identification informationUS20080080680Sep 29, 2006Apr 3, 2008Burns James MMedia terminal adapter (mta) local ringback optionUS20080123627Sep 26, 2006May 29, 2008Moreman Charles SMedia terminal adapter with session initiation protocol (sip) proxyUS20080168517Mar 13, 2008Jul 10, 2008Allen James DSystem and method for evaluating callback functionality in a satellite television networkUS20090143013Sep 19, 2006Jun 4, 2009Matsushita Electric Industrial Co., Ltd.Communication deviceUS20090185665Jul 23, 2009Nokia CorporationMethod and server/module for service configurations testCN1108449AMar 1, 1994Sep 13, 1995美国电话电报公司System and method to identify the terminating directory number at the customer premisesCN1711744ANov 12, 2003Dec 21, 2005汤姆森特许公司Method and apparatus for generating and playing diagnostic messages indicative of MTA provisioning statusWO2003028355A1Sep 24, 2001Apr 3, 2003Fish & Associates, LlpAutomatic routing of telephone calls using a caller id numberWO2003077509A1Mar 6, 2003Sep 18, 2003General Instrument CorporationMethod for generalization of telephone signaling requirements to support multiple internationalWO2004045130A2Nov 12, 2003May 27, 2004Thomson Licensing S.A.Method and apparatus for generating and playing diagnostic messages indicative of mta provisioning statusWO2006015013A2Jul 27, 2005Feb 9, 2006Sprint Spectrum, L.P.Method and system for extending ip pbx services to cellular wireless communication devicesWO2007149708A2Jun 8, 2007Dec 27, 2007Scientific-Atlanta, Inc.Media terminal adapter (mta) initialization process display by use of an embedded caller name and caller identificationWO2008016864A1Jul 30, 2007Feb 7, 2008Scientific-Atlanta, Inc.Media terminal adapter (mta) routing of telephone calls based on caller identification informationWO2008039719A2Sep 24, 2007Apr 3, 2008Scientific-Atlanta, Inc.Embedded media terminal adapter (emta) endpoint redirect modeWO2008039721A2Sep 24, 2007Apr 3, 2008Scientific-Atlanta, Inc.Media terminal adapter with session initiation protocol (sip) proxyWO2008042636A2Sep 24, 2007Apr 10, 2008Scientific-Atlanta, Inc.Media terminal adapter (mta) local ringback option* Cited by examinerNon-Patent CitationsReference1"Access and Terminals (AT); IPCablecom Access Network; End to End Provisioning for the IPAT Architecture (Between the eMTA to the V5.2 Interface); ETSI TR 102 305," ETSI Standards, European Telecommunications Standards Institute, Sophia-Antipo, FR, vol. AT-Digital, No. V111, Mar. 2004, XPO14015619 ISSN: 0000-0001; p. 15-17, line 18, p. 31.2Canadian Office Action dated Feb. 10, 2012 cited in Application No. 2,659,639, 3 pgs.3Canadian Office Action dated Jan. 27, 2011 cited in Application No. 2,655,422.4Canadian Office Action dated Jan. 31, 2012 cited in Application No. 2,655,422.5Canadian Office Action dated Mar. 25, 2011 cited in Application No. 2,659,639.6Canadian Office Action dated May 22, 2012 cited in Application No. 2,664,793, 2 pgs.7Canadian Office Action dated May 4, 2012 cited in Application No. 2,664,578, 5 pgs.8Canadian Office Action dated Sep. 8, 2011 cited in Application No. 2,655,422.9Chinese First Office Action dated Mar. 16, 2011 cited in Application No. 200780023103.8.10Chinese Second Office Action dated Feb. 13, 2012 cited in Application No. 200780023103.8, 10 pgs.11Eugene Nechamkin Broadcom Corp, Jean-Francois Mule Cablelabs: "Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable and IPCablecom compliant devices; draft-ietf-ipcdn-pktc-mtamib-06.txt," IETF Standard-Working-Draft, Internet Engineering Task Force, IETF, CH, vol. ipcdn, No. 6, Jan. 21, 2005, XP015019952, ISSN: 0000-0004, pp. 5-7, p. 28, line 29.12European Communication dated Apr. 9, 2010 cited in Application No. 07 853 608.3.13European Communication dated Jun. 4, 2009 cited in Application No. 07 798 275 9.14European Communication dated Sep. 30, 2009 cited in Application No. 07 853 604.2.15F. Baker, "Cisco Lawful Intercept Control MIB draft-baker-slem-mib-00," Cisco Systems, Internet-Draft, Sep. 30, 2003, XP015000178 ISSN: 0000-0004, 39 pgs.16F. Cuervo et al., "Megaco Protocol Version 1.0," RFC 3015, Lucent Technologies, Nov. 2000, 220 pgs.17Fred Baker et al., "Cisco Architecture for Lawful Intercept In IP Networks," Internet Engineering Task Force, Internet Draft, No. 2, Oct. 2003, XP015010527 ISSN: 0000-0004, 17 pgs.18Gordon Beacham Motorola et al., "Network Control Signaling (NCS) Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs); draft-ietf-ipcdn-pktc-signaling-02.txt;" IETF Standard-Working Draft; Internet Engineering Task Force, IETF, CH, vol. ipcdn, No. 2, Oct. 2003, XP015019953 ISSN: 0000-0004; p. 3, p. 27.19International Preliminary Report on Patentability mailed Mar. 10, 2010 cited in PCT/US2007/079313.20International Search Report and Written Opinion dated Mar. 10, 2008 cited in PCT/US2007/079313.21International Search Report and Written Opinion mailed Dec. 28, 2007 cited in Application No. PCT/US2007/070692.22International Search Report and Written Opinion mailed Dec. 28, 2007 cited in Application No. PCT/US2007/074688.23International Search Report and Written Opinion mailed Mar. 18, 2008 cited in PCT/US2007/079309.24International Search Report and Written Opinion mailed Mar. 25, 2008 cited in PCT/US2007/079307.25James Dahl, "Draft new ITU-T Recommendation J.ipc2arch-IPCablecom 2 Architecture Framework," COM 9-C 37-E, Aug. 2005, International Telecommunication Union, Telecommunication Standardization Sector Study Period 2005-2008, 38 pgs.26James Dahl, "Draft new ITU-T Recommendation J.ipc2arch—IPCablecom 2 Architecture Framework," COM 9-C 37-E, Aug. 2005, International Telecommunication Union, Telecommunication Standardization Sector Study Period 2005-2008, 38 pgs.27Luan Dang, Cullen Jennings, David Kelly-Practical VOIP using VOCAL, 2002, 28 pgs.28Luan Dang, Cullen Jennings, David Kelly—Practical VOIP using VOCAL, 2002, 28 pgs.29M. Handley et al., "SIP: Session Initiation Protocol," RFC 2543, Bell Labs, Mar. 1999, 187 pgs.30U.S. Appl. No. 11/461,487, filed Aug. 1, 2006, Entitled "Media Terminal Adapter Routing of Telephone Calls Based on Caller Identification Information," Inventors: Scholes et al.31U.S. Appl. No. 11/461,487, filed Jun. 22, 2006, Entitled "Media Terminal Adapter Initialization Process Display by Use of an Embedded Caller Name and Caller Identification," Inventors: Burns et al.32U.S. Appl. No. 11/535,201, filed Sep. 26, 2006, Entitled "Media Terminal Adapter with Session Initiation Protocol (SIP) Proxy," Inventors: Moreman, et al.33U.S. Appl. No. 11/536,727, filed Sep. 29, 2006, Entitled "Media Terminal Adapter Local Ringback Option," Inventors: Burns, James M.34U.S. Final Office Action dated Aug. 11, 2011 cited in U.S. Appl. No. 11/536,727.35U.S. Final Office Action dated Nov. 16, 2010 cited in U.S. Appl. No. 11/536,727.36U.S. Final Office Action dated Sep. 2, 2011 cited in U.S. Appl. No. 11/461,487.37U.S. Office Action dated Apr. 12, 2012 cited in U.S. Appl. No. 11/425,862, 16 pgs.38U.S. Office Action dated Apr. 28, 2011 cited in U.S. Appl. No. 11/461,487.39U.S. Office Action dated Dec. 10, 2009 cited in U.S. Appl. No. 11/461,487.40U.S. Office Action dated Dec. 20, 2007 cited in U.S. Appl. No. 11/535,201.41U.S. Office Action dated Jun. 13, 2008 cited in U.S. Appl. No. 11/535,201.42U.S. Office Action dated Jun. 7, 2010 cited in U.S. Appl. No. 11/536,727.43U.S. Office Action dated Mar. 17, 2010 cited in U.S. Appl. No. 11/425,862.44U.S. Office Action dated Mar. 4, 2011 cited in U.S. Appl. No. 11/536,727.45U.S. Office Action dated Mar. 5, 2009 cited in U.S. Appl. No. 11/535,201.46U.S. Office Action dated May 24, 2010 cited in U.S. Appl. No. 11/461,487.47U.S. Office Action dated Oct. 16, 2008 cited in U.S. Appl. No. 11/535,201.48U.S. Office Action dated Sep. 30, 2009 cited in U.S. Appl. No. 11/425,862.49U.S. Office Action dated Sep. 4, 2009 cited in U.S. Appl. No. 11/535,201.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8363805Jan 29, 2013Burns Jr James MMedia terminal adapter (MTA) initialization process display by use of an embedded caller name and caller identificationUS8526583 *Sep 29, 2006Sep 3, 2013James M. Burns, JR.Media terminal adapter (MTA) local ringback optionUS8675856Aug 1, 2006Mar 18, 2014Cisco Technology, Inc.Media terminal adapter (MTA) routing of telephone calls based on caller identification informationUS20070297384 *Jun 22, 2006Dec 27, 2007Burns James MMedia terminal adapter (mta) initialization process display by use of an embedded caller name and caller identificationUS20080043970 *Aug 1, 2006Feb 21, 2008Scholes Bryan WMedia terminal adapter (mta) routing of telephone calls based on caller identification informationUS20080080680 *Sep 29, 2006Apr 3, 2008Burns James MMedia terminal adapter (mta) local ringback option* Cited by examinerClassifications U.S. Classification370/395.54, 370/466, 379/211.02, 700/223International ClassificationH04L12/28, H04L12/56Cooperative ClassificationH04L65/1059, H04M7/006, H04M3/2281, H04M7/0069European ClassificationH04M3/22T, H04L29/06M2N7, H04M7/00MLegal EventsDateCodeEventDescriptionOct 12, 2006ASAssignmentOwner name: SCIENTIFIC-ATLANTA, INC., GEORGIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BURNS, JAMES M., JR.;REEL/FRAME:018392/0577Effective date: 20060928Jul 27, 2009ASAssignmentOwner name: SCIENTIFIC-ATLANTA, LLC, GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;REEL/FRAME:023012/0703Effective date: 20081205Owner name: SCIENTIFIC-ATLANTA, LLC,GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;REEL/FRAME:023012/0703Effective date: 20081205Nov 19, 2014ASAssignmentOwner name: SCIENTIFIC-ATLANTA, LLC, GEORGIAFree format text: CHANGE OF NAME;ASSIGNOR:SCIENTIFIC-ATLANTA, INC.;REEL/FRAME:034299/0440Effective date: 20081205Owner name: CISCO TECHNOLOGY, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SCIENTIFIC-ATLANTA, LLC;REEL/FRAME:034300/0001Effective date: 20141118Feb 1, 2016FPAYFee paymentYear of fee payment: 4RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services