System and method for enabling multi-line mobile telephone service capabilities on a single-line mobile telephone

Information

  • Patent Application
  • 20070206569
  • Publication Number
    20070206569
  • Date Filed
    August 24, 2006
    17 years ago
  • Date Published
    September 06, 2007
    16 years ago
Abstract
A system, server, and method of DTMF detection in a VoIP network.
Description

BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram of an independently managed and controlled wireless carrier network, and an independently managed corporate enterprise network;



FIG. 2 is a diagram of a conventional enterprise network gateway server connected to a wireless carrier network;



FIG. 3 is a diagram of a gateway server system accordingly to one preferred embodiment of the present invention;



FIG. 4A is a diagram of an enterprise data and voice network operably connected using the gateway server system using pure enterprise call control according to one preferred embodiment;



FIG. 4B is a diagram of an enterprise data and voice network operably connected using the gateway server system using split call control according to one preferred embodiment;



FIG. 5 depicts a network architecture according to another preferred embodiment using VoIP systems;



FIG. 6 is a call flow diagram for call origination according to one embodiment of the present invention;



FIG. 7 is a call flow diagram for effecting call delivery using VoIP system according to another preferred embodiment of the present invention;



FIG. 8 is a call flow diagram for effecting mobile termination using VoIP according to another preferred embodiment of the present invention;



FIG. 9 is a diagram of a network architecture for a Legacy (TDM) network according to another preferred embodiment of the present invention;



FIG. 10 is a diagram of a next generation IMS architecture that is backwards compatible with legacy cellular networks based on existing cellular protocols;



FIG. 11 is a diagram of a conventional legacy network architecture that does not support IM;;



FIG. 12 depicts a Packet Engine according to another preferred embodiment of the present invention allowing a call server to detect DTMF digit events on the call path;



FIG. 13 depicts one embodiment of the Packet Engine consisting of a user space;



FIG. 14 depicts a Linux kernel module of the Packet Engine;



FIG. 15 depicts the current IMS standard definition;;



FIG. 16 depicts one exemplary embodiment of the invention for IMS service;



FIG. 17 and FIG. 18 depict a gateway server carrier (GS-C) configured as an IMS standard-compliant SIP, and associated algorithm; and



FIG. 19 depicts an algorithm for receiving incoming calls on various lines that are to be directed to a subscribers mobile phone.


Claims
  • 1. A method for DTMF detection in a VoIP network, comprising the steps of: a VoIP call server anchoring a bearer stream within a VoIP call path of an active two party session to facilitate detection of DTMF digits in an RTP media stream of packets.
  • 2. The method as specified in claim 1 further comprising the step of the VoIP call server using Linux IPTables port mapping to anchor the bearer stream.
  • 3. The method as specified in claim 1 wherein the VoIP call server provides a mid-call service to an end client in the call based on the DTMF digits.
  • 4. The method as specified in claim 1 wherein the call server detects DTMF digit events on the call path of the active two party call session using a software only solution operable as a packet engine.
  • 5. The method as specified in claim 4 wherein the packet engine is deployed on the same hardware platform as the VoIP call server.
  • 6. The method as specified in claim 4 wherein the packet engine is deployed on a separate hardware platform from the VoIP call server.
  • 7. The method as specified in claim 4 wherein the packet engine is statically linked into a process of the VoIP call server.
  • 8. The method as specified in claim 4 wherein the packet engine is scalable.
  • 9. The method as specified in claim 4 wherein the packet engine supports control by multiple servers in the VoIP network.
  • 10. The method as specified in claim 4 wherein the VoIP server controls multiple said packet engines in the VoIP network.
  • 11. The method as specified in claim 4 wherein the packet engine comprises a user space process and a Linux kernel module.
  • 12. The method as specified in claim 11 wherein the user space process receives and sends commands to/from the VoIP call server, the user space process utilizing Linux utility IPTables to create port mappings within an IP stack.
  • 13. The method as specified in claim 12 wherein the Linux kernel module determines which RTP packets being forwarded by the IP stack contain DTMF digits.
  • 14. The method as specified in claim 13 wherein the Linux kernel examines headers of each RTP packet and checks a Payload Type field, wherein the Payload Type field indicates whether the RTP packet contains a DTMF event.
  • 15. The method as specified in claim 14 wherein the DTMF event is encoded per IETF RFC 2833, and the Linux kernel module sends the RTP packet up to the user space process for further application level processing.
  • 16. The method as specified in claim 15 wherein the Linux kernel module operates as an extension (plugin) to the Linux kernel and facilitates incoming RTP packets to be examined.
  • 17. A packet engine operable in a VoIP network, comprising: a user space module configured to receive and send commands to/from the VoIP network, the user space module configured to utilize Linux IPTables to create port mappings within an IP stack.
  • 18. The method as specified in claim 17 wherein the packet engine further comprises a Linux kernel module configured to determine which RTP packets forwarded by the IP stack contain DTMF digits.
  • 19. The method as specified in claim 18 wherein the Linux kernel examines the headers of each RTP packet and checks a Payload Type field, wherein the Payload Type field indates whether the RTP packet contains a DTMF event.
  • 20. The method as specified in claim 19 wherein the DTMF event is encoded per IETF RFC 2833, and the Linux kernel module sends the RTP packet up to the user space module for further application level processing.
  • 21. The method as specified in claim 20 wherein the Linux kernel module operates as an extension (plugin) to the Linux kernel and facilitates incoming RTP packets to be examined.
  • 22. A VoIP call server, comprising: a module configured to establish a VoIP call session; anda module configured to detect DTMF digit events within a bearer stream of an active VoIP call session.
  • 23. The call server as specified in claim 22 wherein the VoIP call server is configured to operate as an intermediate node on a signaling path of the call session.
  • 24. The call server as specified in claim 23 wherein the VoIP call server is further configured to provide mid-call services as a function of the detected DTMF digit events originated by a party to the call session.
  • 25. The call server as specified in claim 24 wherein the VoIP call server comprises a packet engine, comprising a user space module configured to receive and send commands to/from the VoIP network, the user space module configured to utilize Linux IPTables to create port mappings within an IP stack.
  • 26. The method as specified in claim 25 wherein the packet engine further comprises a Linux kernel module configured to determine which RTP packets forwarded by the IP stack contain DTMF digits.
  • 27. The method as specified in claim 26 wherein the Linux kernel examines headers of each RTP packet and checks a Payload Type field, wherein the Payload Type field indates whether the RTP packet contains a DTMF event.
  • 28. The method as specified in claim 27 wherein the DTMF event is encoded per IETF RFC 2833, and the Linux kernel module sends the RTP packet up to the user space module for further application level processing.
  • 29. The method as specified in claim 28 wherein the Linux kernel module operates as an extension (plugin) to the Linux kernel and facilitates incoming RTP packets to be examined.
Provisional Applications (4)
Number Date Country
60778252 Mar 2006 US
60778276 Mar 2006 US
60778443 Mar 2006 US
60797724 May 2006 US