US20120155454A1 - MOBILE PHONE DOCKING STATION FOR VoIP - Google Patents
MOBILE PHONE DOCKING STATION FOR VoIP Download PDFInfo
- Publication number
- US20120155454A1 US20120155454A1 US12/971,409 US97140910A US2012155454A1 US 20120155454 A1 US20120155454 A1 US 20120155454A1 US 97140910 A US97140910 A US 97140910A US 2012155454 A1 US2012155454 A1 US 2012155454A1
- Authority
- US
- United States
- Prior art keywords
- mobile phone
- docking station
- phone
- external network
- port
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- VJYFKVYYMZPMAB-UHFFFAOYSA-N ethoprophos Chemical compound CCCSP(=O)(OCC)SCCC VJYFKVYYMZPMAB-UHFFFAOYSA-N 0.000 title 1
- 238000003032 molecular docking Methods 0.000 claims abstract description 146
- 238000013519 translation Methods 0.000 claims description 8
- 230000001413 cellular effect Effects 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 10
- 230000007246 mechanism Effects 0.000 description 10
- 238000012545 processing Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 7
- 230000003068 static effect Effects 0.000 description 3
- 238000001914 filtration Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000000034 method Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
Definitions
- VoIP Voice over Internet Protocol
- PSTN Public Switched Telephone Networks
- VoIP e.g., IP packets carrying audio data
- VoIP involves a call being carried via the Internet to a point in the PSTN very close to the call destination. At that point, the call is switched to the PSTN for completion of the connection with the call destination.
- the cost of the call may be substantially reduced relative to solely using the PSTN for the entirety of the call.
- FIG. 1 is a diagram that depicts an exemplary mobile phone docking station that enables a VoIP connection between a docked mobile phone and an external network;
- FIG. 2 is a diagram that depicts an exemplary implementation of the mobile phone docking station of FIG. 1 in which the mobile phone docking station implements Network Address and Port Translation or Network Address Translation for establishing a VoIP connection between the mobile phone and the external network;
- FIG. 3 is a diagram that depicts an exemplary implementation of the mobile phone docking station of FIG. 1 in which the mobile phone docking station implements a bridging mode for establishing a VoIP connection between the mobile phone and the external network;
- FIG. 4 is a diagram that depicts exemplary components of the mobile phone docking station of FIG. 1 ;
- FIG. 5 is a diagram that depicts exemplary components of the mobile phone of FIG. 1 .
- a docking station for a mobile phone enables the mobile phone to have Ethernet/IP access to/from an external network (e.g., an Ethernet Local Area Network) for sending/receiving VoIP traffic via the docking station while the mobile phone is docked.
- the docking station may utilize Network Address Port Translation (NAPT) or Network Address Translation (NAT) for carrying VoIP traffic from the network to the mobile phone.
- NAPT Network Address Port Translation
- NAT Network Address Translation
- the docking station may provide a bridge onto the network to enable layer 2 packet forwarding of the VoIP traffic from the network to the mobile phone.
- the docking station for the mobile phone additionally includes charging mechanisms to enable the battery of the mobile phone to be charged while the mobile phone is docked in the docking station.
- the docking station for the mobile phone further includes mechanisms that enable the streaming of media (e.g., audio or video) between the mobile phone and the docking station. Therefore, audio or video generated at the docking station can be streamed to the mobile phone for playback/display, and audio or video generated at the mobile phone may be streamed to the docking station for playback/display.
- media e.g., audio or video
- FIG. 1 is a diagram that depicts an exemplary phone docking station 100 that enables a VoIP connection between a docked mobile phone 105 and an external network 110 .
- a mobile phone 105 may be docked 115 (i.e., physically inserted into a docking port) with docking station 100 .
- mobile phone 105 may exchange media (e.g., audio or video) or other data 120 with docking station 100 .
- the exchanged media 200 may include audio streamed from a microphone of docking station 100 to mobile phone 105 , or from a microphone of mobile phone 105 to docking station 100 .
- the exchanged media may further include video streamed from a camera (or memory) of docking station 100 to mobile phone 105 , or from a camera (or memory) of mobile phone 105 to docking station 100 .
- Mobile phone 105 may include, for example, a cellular telephone (e.g., a smart phone).
- Network 110 may include one or more networks that implement Ethernet protocol or Internet Protocol (IP).
- IP Internet Protocol
- Network 110 may include one or more networks of various types, including a wireless satellite network, a wireless public land mobile network (PLMN) (e.g., a Code Division Multiple Access (CDMA) 2000 PLMN, a Global System for Mobile Communications (GSM) PLMN, a Long Term Evolution (LTE) PLMN and/or other types of PLMNs), a telecommunications network (e.g., a Public Switched Telephone Network (PSTN)), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), an intranet, the Internet, or a cable network (e.g., an optical cable network).
- network 110 may include a layer 2 (Ethernet) switch connected to phone docking station 100 and to a LAN.
- Ethernet
- docking station 100 may connect to external network 110 for sending and/or receiving VoIP traffic 125 to/from phone 130 via a VoIP server 135 .
- Docking station 100 may forward VoIP traffic 125 from network 110 to mobile phone 105 , and from mobile phone 105 to network 110 via a system 140 that implements NAPT, NAT, or a bridging mode.
- system 140 may route packets associated with VoIP traffic 125 to/from mobile phone 105 .
- a side of docking station 100 facing network 110 may have a public, routable Internet Protocol (IP) address on network 110
- IP Internet Protocol
- a side of docking station 100 facing mobile phone 105 may have a statically configured private IP address.
- the routable IP address of docking station 100 facing network 110 may be statically configured, or may be obtained via the Dynamic Host Configuration Protocol (DHCP) from network 110 .
- DHCP Dynamic Host Configuration Protocol
- Mobile phone 105 may have a statically configured private IP address (e.g., on a same network as the private IP address of docking station 100 ).
- Mobile phone 105 may use the routable IP address of docking station 100 as a default gateway for sending VoIP packets to phone 130 via network 110 and VoIP server 135 .
- a physical and layer 2 connection between docking station 100 and mobile phone 105 may include Ethernet over Universal Serial Bus (USB) (e.g., Ethernet frames encapsulated in USB packets).
- Media 120 may be streamed from the private IP address associated with mobile phone 105 to the private IP address associated with docking station 100 , or may be streamed in the reverse direction.
- USB Universal Serial Bus
- system 140 may forward packets, at layer 2 , from network 110 , though docking station 100 , to mobile phone 105 . Additionally, system 140 may forward packets, at layer 2 , from mobile phone 105 , though docking station 100 , to network 110 . Docking station 100 may have an IP address, routable in network 110 , and mobile phone 105 may also have a different IP address that is routable in network 110 . System 140 , implementing the bridging mode, may forward packets received at docking station 100 from network 110 to the routable IP address of mobile phone 105 . Additionally, when implementing the bridging mode, system 140 may forward packets, received from mobile phone 105 at the routable IP address of docking station 100 , to network 110 .
- FIG. 2 is a diagram that depicts an exemplary implementation of the mobile phone docking station 100 of FIG. 1 in which mobile phone docking station 100 implements NAPT or NAT for establishing a VoIP connection between the mobile phone and the external network.
- media 200 , other data 205 , VoIP traffic 125 and other network traffic 210 may be sent to and from mobile phone 105 via a Universal Serial Bus (USB) 215 , as further shown in FIG. 2 .
- USB Universal Serial Bus
- Mobile phone 105 therefore, acts as a USB peripheral, and phone docking station 100 acts as a USB host. Ethernet over USB protocol 235 may be used as the physical and layer 2 connection between phone docking station 100 and mobile phone 105 .
- mobile phone 105 may have a statically configured IP address 220 that is non-routable from network 110 (but routable between IP address 225 of phone docking station 100 and IP address 220 of mobile phone 105 ).
- phone docking station 100 may also have a statically configured IP address 225 that is non-routable from network 110 (but routable between IP address 225 of phone docking station 100 and IP address 220 of mobile phone 105 ), where IP address 225 resides on a same private network (not shown) on which IP address 220 of mobile phone 105 resides.
- a private network (not shown in FIG. 2 ), therefore, exists between mobile phone 105 and phone docking station 100 via USB 215 .
- phone docking station 100 may have an IP address 230 that is routable from network 110 .
- Routable IP address 230 may be statically configured, or may be obtained via the DHCP protocol from network 110 .
- Phone docking station 100 may, therefore, act as a DHCP server to mobile phone 105 , thereby obtaining routable IP address 230 that may be used by network 110 to forward VoIP traffic 125 and other network traffic 210 to mobile phone 105 via NAPT/NAT system 140 .
- Non-routable, private IP address 220 on mobile phone 105 and non-routable, private IP address 225 on phone docking station 100 may be statically configured prior to the connection of mobile phone 105 to phone docking station 100 via USB 215 .
- a network administrator may manage phone docking station 100 including, for example, providing software upgrades, firewall management, etc.
- the ability to address phone docking station 100 from network 110 may not be available when phone docking station 100 acts as an IP bridge (e.g., the exemplary bridging implementation of FIG. 3 ).
- Media 200 may include audio or video data (e.g., streaming audio or video) that may be streamed from mobile phone 105 for playback on phone docking station 100 , or that may be streamed from phone docking station 100 for playback on mobile phone 105 .
- Media 200 may be streamed from mobile phone 105 IP address 220 to phone docking station IP address 225 , or from phone docking station IP address 225 to mobile phone 105 IP address 220 .
- Other data 205 may include keypad information (e.g., indications of keypad presses on phone docking station 100 ), status information (e.g., voicemail message indicator light, etc.), and other information that may be exchanged between mobile phone IP address 220 and phone docking station 100 IP address 225 .
- Other data 205 may further include data other than audio or video data, such as, for example, web traffic data.
- the transfer of media 200 and/or other data 205 may be through sockets, such as Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) sockets.
- TCP Transmission Control Protocol
- UDP User Datagram Protocol
- VoIP traffic 125 may include VoIP signaling traffic (e.g., Session Initiation Protocol (SIP) traffic) and VoIP media traffic (e.g., Real-time Transport Protocol (RTP) or RTP Control Protocol (RTCP)) and may be forwarded through phone docking station 100 via NAPT/NAT system 140 .
- VoIP signaling traffic e.g., Session Initiation Protocol (SIP) traffic
- VoIP media traffic e.g., Real-time Transport Protocol (RTP) or RTP Control Protocol (RTCP)
- RTP Real-time Transport Protocol
- RTCP Real-time Transport Protocol
- RTCP Real-time Transport Protocol
- RTCP Real-time Transport Protocol
- RTCP Real-time Transport Protocol
- RTCP Real-time Transport Protocol
- RTCP Real-time Transport Protocol
- RTCP Real-time Transport Protocol
- RTCP Real-time Transport Protocol
- RTCP Real-time Transport Protocol
- RTCP Real-time Transport Protocol
- RTCP Real-time Transport Protocol
- other network traffic 210 may be forwarded to/from mobile phone 105 through phone docking station 100 to routable network 110 by the forwarding table based on NAPT or NAT filtering.
- the forwarding table of NAPT/NAT system 140 may receive packets from IP address 220 of mobile phone 105 sent to routable IP address 230 of phone docking station 225 , and may forward the packets to an appropriate next hop IP address in network 110 (e.g., to a next hop switch).
- the forwarding table of NAPT/NAT system 140 may further receive packets from an IP address in network 110 sent to routable IP address 230 , and may forward the packets to non-routable IP address 220 of mobile phone 105 .
- a network administrator of network 110 may designate what kinds of traffic are permissible, and the forwarding table at phone docking station 100 may be configured appropriately (e.g., e-mail and web browsing may be forwarded whereas other undesirable traffic may be blocked during the forwarding process).
- a forwarding table implemented at mobile phone 105 may use routable IP address 230 of phone docking station 100 as the default gateway address for all outgoing packets.
- FIG. 3 is a diagram that depicts an exemplary implementation of the mobile phone docking station of FIG. 1 in which the mobile phone docking station implements a bridging mode for establishing a VoIP connection between the mobile phone and the external network.
- media 200 , other data 205 , VoIP traffic 125 and other network traffic 210 may be sent to and from mobile phone 105 via a Universal Serial Bus (USB) 215 , as further shown in FIG. 3 .
- USB Universal Serial Bus
- Mobile phone 105 therefore, acts as a USB peripheral, and phone docking station 100 acts as a USB host. Ethernet over USB protocol 235 may be used as the physical and layer 2 connection between phone docking station 100 and mobile phone 105 .
- mobile phone 105 may have an IP address 300 that is routable from network 110 .
- phone docking station 100 may also have a IP address 230 that is routable from network 110 .
- Routable IP addresses 300 and 230 may be statically configured, or may be obtained via the DHCP protocol from network 110 .
- Phone docking station 100 may, therefore, act as a DHCP server to mobile phone 105 , thereby obtaining routable IP addresses 300 and 230 that may be used by network 110 to forward VoIP traffic 125 and other network traffic 210 to mobile phone 105 via bridging system 140 .
- Media 200 may be streamed from mobile phone 105 for playback on phone docking station 100 , or may be streamed from phone docking station 100 for playback on mobile phone 105 .
- Media 200 may be streamed from mobile phone 105 IP address 300 to phone docking station IP address 230 , or from phone docking station IP address 230 to mobile phone 105 IP address 300 .
- Other data 205 may include keypad information, status information, and other information that may be exchanged between mobile phone IP address 300 and phone docking station 100 IP address 230 .
- VoIP traffic 125 may include VoIP signaling traffic (e.g., SIP traffic) and VoIP media traffic (e.g., RTP or RTCP) and may be forwarded through phone docking station 100 via bridging system 140 .
- Bridging system 140 may forward, at layer 2 , packets to/from mobile phone 105 through phone docking station 100 to routable network 110 .
- Bridging system 140 may “transparently” forward packets, without any NAPT or NAT filtering as performed in the implementation of FIG. 2 , from mobile phone 105 to network 110 and from network 110 to mobile phone 105 .
- network 110 includes an Ethernet Local Area Network (LAN)
- bridging system 140 may forward Ethernet frames from network 110 to mobile phone 105 based on MAC addresses contained in the Ethernet frames.
- LAN Ethernet Local Area Network
- FIG. 4 is a diagram that depicts exemplary components of phone docking station 100 .
- Phone docking station 100 may include a docking port 400 , a NAPT/NAT/Bridging system 140 , a communication interface 415 , a processing unit 420 , an audio unit 425 , a video unit 430 , a display 435 , a keypad/touch input 440 , a Near Field Communication (NFC) reader 445 , and a Bluetooth interface 450 .
- NFC Near Field Communication
- Docking port 400 may include a port that may physically engage with mobile phone 105 .
- the shape and size of docking port 400 may be different based on a different external configuration of mobile phone 105 .
- Docking port 400 may further include a USB port 405 , which also include a charging port 410 (i.e., USB port 405 may simultaneously act as a data port and a battery charging port).
- a single USB port 405 is depicted in FIG. 4
- phone docking station 100 may include multiple USB ports (not shown) and/or a USB hub.
- Charging port 405 may include an electrical connection for supplying a charging current to a battery of mobile phone 105 .
- USB port 410 may include an electrical connection for the USB that may interconnect phone docking station 100 with mobile phone 105 .
- NAPT/NAT/bridging system 140 may include, in one exemplary implementation that corresponds to FIG. 2 above, a system on a chip (SOC) that implements NAPT or NAT which modifies network address information in incoming packets for the purpose of translating one IP address space into another (e.g., remaps routable public IP addresses into private, non-routable IP addresses).
- SOC system on a chip
- NAPT/NAT/bridging system 140 when implementing NAPT or NAT, may be used to firewall and control traffic sent to mobile phone 105 via phone docking station 100 , thus, enhancing the security of, and control over, traffic carried by the docked mobile phone 105 .
- NAPT/NAT/bridging system 140 may include, in another exemplary implementation that corresponds to FIG.
- a SOC that implements a bridging mode which may forward packets, at layer 2 , from network 110 , though docking station 100 , to mobile phone 105 . Additionally, the SOC implementing the bridging mode may forward packets, at layer 2 , from mobile phone 105 , though docking station 100 , to network 110 .
- Communication interface 415 may include a transceiver for communicating with network 110 .
- Processing unit 420 may include a processor, microprocessor, or processing logic that may interpret and execute instructions.
- the instructions may be stored in memory, such as, for example, a random access memory (RAM), a Read Only Memory (ROM), or another type of dynamic or static storage device that may store information and instructions for execution by processing unit 420 .
- RAM random access memory
- ROM Read Only Memory
- Audio unit 425 may include a microphone for receiving audio input into phone docking station 100 , and may include mechanisms for playback of audio data received from the microphone, or received from mobile phone 105 .
- Video unit 430 may include a camera for capturing video, and may further include mechanisms for playback of video data received from the camera, or received from mobile phone 105 .
- Display 435 may a display device that may display video data or other types of data associated with the operation of phone docking station 100 or mobile phone 105 .
- display 430 may include a touch screen display that registers touch input at different locations upon the touch screen.
- Keypad/touch input unit 440 may include an alphanumeric keypad and mechanisms for receiving indications of touch input from display 430 .
- NFC reader 445 may include a short range, high frequency system that enables the short range (e.g., 10 cm) exchange of data with mobile phone 105 .
- NFC reader 445 may “read” phone identity information from a corresponding NFC system located in phone 105 .
- NFC reader 445 may also read phone user identity information from the corresponding NFC system located in phone 105 .
- NFC reader 445 may, thus, be used to identify different phones that may be placed in proximity to phone docking station 100 .
- Bluetooth interface 450 may include a short wavelength system for connecting with, and exchanging data over short distances, with any type of Bluetooth enabled device.
- Bluetooth interface 450 may, for example, connect with a Bluetooth enabled audio headset that permits a wearer to listen to audio from audio unit 425 .
- phone docking station 100 may include additional, fewer and/or different components than those depicted in FIG. 4 .
- phone docking station 100 may include a system(s) for implementing an Ethernet switch (not shown in FIG. 4 ), and/or for implementing Virtual Local Area Networks (VLANs).
- Phone docking station 100 may further include a magnetic sensor that may detect the insertion of mobile phone 105 into docking port 400 and may thereby initiate various functions at phone docking station 100 or at mobile phone 105 (e.g., initiate execution of a VoIP application at mobile phone 105 , etc.).
- FIG. 5 is a diagram that depicts exemplary components of mobile phone 105 .
- Mobile phone 105 may include a bus 510 , a processing unit 520 , a main memory 530 , a read only memory (ROM) 540 , a storage device 550 , an input device(s) 560 , an output device(s) 570 , a communication interface 580 , a USB interface 590 , and a NFC system 595 .
- Bus 510 may include a path that permits communication among the elements of mobile phone 105 .
- Processing unit 520 may include a processor, microprocessor, or processing logic that may interpret and execute instructions.
- Main memory 530 may include a random access memory (RAM) or another type of dynamic storage device that may store information and instructions for execution by processing unit 520 .
- ROM 540 may include a ROM device or another type of static storage device that may store static information and instructions for use by processing unit 520 .
- Storage device 550 may include a magnetic and/or optical recording medium.
- Input device 560 may include one or more mechanisms that permit an operator to input information to mobile phone 105 , such as, for example, a keypad or a keyboard, voice recognition and/or biometric mechanisms, etc.
- Output device 570 may include one or more mechanisms that output information to the operator, including a display, a speaker, etc.
- Communication interface 580 may include any transceiver mechanism that enables mobile phone 105 to communicate with other devices and/or systems.
- communication interface 580 may include a radio frequency transceiver for communicating via a PLMN or satellite network of network 110 .
- USB I/F 590 may include interconnection mechanisms to permit phone 105 to physically and electrically connect with USB port 405 of phone docking station 100 .
- NFC system 595 may include a short range, high frequency system that enables the short range exchange of data with mobile phone 105 .
- NFC system may transmit phone identity information and/or phone user identity information that may be “read” by NFC reader 445 of phone docking station 100 .
- mobile phone 105 may include additional, fewer and/or different components than those depicted in FIG. 5 .
- This logic or unit may include hardware, such as one or more processors, microprocessors, application specific integrated circuits, or field programmable gate arrays, software, or a combination of hardware and software.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
- Telephone Function (AREA)
Abstract
Description
- A recent trend for reducing service costs in telecommunications networks involves the use of Voice over Internet Protocol (VoIP) for carrying calls between source and destination phones. IP networks typically incur minimal costs to carry data from sources to destinations, as opposed to Public Switched Telephone Networks (PSTN) which typically incur much higher costs to carry phone calls from sources to destinations. By using VoIP (e.g., IP packets carrying audio data) for carrying a call for most of the distance of the call, instead of using a PSTN, the cost of the call can be reduced relative to having a PSTN carry the entirety of the call. Usually, VoIP involves a call being carried via the Internet to a point in the PSTN very close to the call destination. At that point, the call is switched to the PSTN for completion of the connection with the call destination. By minimizing the distance that the call is carried on the PSTN, the cost of the call may be substantially reduced relative to solely using the PSTN for the entirety of the call.
-
FIG. 1 is a diagram that depicts an exemplary mobile phone docking station that enables a VoIP connection between a docked mobile phone and an external network; -
FIG. 2 is a diagram that depicts an exemplary implementation of the mobile phone docking station ofFIG. 1 in which the mobile phone docking station implements Network Address and Port Translation or Network Address Translation for establishing a VoIP connection between the mobile phone and the external network; -
FIG. 3 is a diagram that depicts an exemplary implementation of the mobile phone docking station ofFIG. 1 in which the mobile phone docking station implements a bridging mode for establishing a VoIP connection between the mobile phone and the external network; -
FIG. 4 is a diagram that depicts exemplary components of the mobile phone docking station ofFIG. 1 ; and -
FIG. 5 is a diagram that depicts exemplary components of the mobile phone ofFIG. 1 . - The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. The following detailed description does not limit the invention.
- In embodiments described herein, a docking station for a mobile phone enables the mobile phone to have Ethernet/IP access to/from an external network (e.g., an Ethernet Local Area Network) for sending/receiving VoIP traffic via the docking station while the mobile phone is docked. In one implementation, the docking station may utilize Network Address Port Translation (NAPT) or Network Address Translation (NAT) for carrying VoIP traffic from the network to the mobile phone. In another implementation, the docking station may provide a bridge onto the network to enable layer 2 packet forwarding of the VoIP traffic from the network to the mobile phone. The docking station for the mobile phone additionally includes charging mechanisms to enable the battery of the mobile phone to be charged while the mobile phone is docked in the docking station. The docking station for the mobile phone further includes mechanisms that enable the streaming of media (e.g., audio or video) between the mobile phone and the docking station. Therefore, audio or video generated at the docking station can be streamed to the mobile phone for playback/display, and audio or video generated at the mobile phone may be streamed to the docking station for playback/display.
-
FIG. 1 is a diagram that depicts an exemplaryphone docking station 100 that enables a VoIP connection between a dockedmobile phone 105 and anexternal network 110. As shown inFIG. 1 , amobile phone 105 may be docked 115 (i.e., physically inserted into a docking port) withdocking station 100. Upon being docked withdocking station 100,mobile phone 105 may exchange media (e.g., audio or video) orother data 120 withdocking station 100. The exchangedmedia 200 may include audio streamed from a microphone ofdocking station 100 tomobile phone 105, or from a microphone ofmobile phone 105 todocking station 100. The exchanged media may further include video streamed from a camera (or memory) ofdocking station 100 tomobile phone 105, or from a camera (or memory) ofmobile phone 105 todocking station 100. -
Mobile phone 105 may include, for example, a cellular telephone (e.g., a smart phone). Network 110 may include one or more networks that implement Ethernet protocol or Internet Protocol (IP). Network 110 may include one or more networks of various types, including a wireless satellite network, a wireless public land mobile network (PLMN) (e.g., a Code Division Multiple Access (CDMA) 2000 PLMN, a Global System for Mobile Communications (GSM) PLMN, a Long Term Evolution (LTE) PLMN and/or other types of PLMNs), a telecommunications network (e.g., a Public Switched Telephone Network (PSTN)), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), an intranet, the Internet, or a cable network (e.g., an optical cable network). In one exemplary implementation,network 110 may include a layer 2 (Ethernet) switch connected tophone docking station 100 and to a LAN. - As further shown in
FIG. 1 ,docking station 100 may connect toexternal network 110 for sending and/or receivingVoIP traffic 125 to/fromphone 130 via aVoIP server 135.Docking station 100 may forwardVoIP traffic 125 fromnetwork 110 tomobile phone 105, and frommobile phone 105 tonetwork 110 via asystem 140 that implements NAPT, NAT, or a bridging mode. - When implementing NAPT or NAT,
system 140 may route packets associated withVoIP traffic 125 to/frommobile phone 105. A side ofdocking station 100 facingnetwork 110 may have a public, routable Internet Protocol (IP) address onnetwork 110, while a side ofdocking station 100 facingmobile phone 105 may have a statically configured private IP address. The routable IP address ofdocking station 100 facingnetwork 110 may be statically configured, or may be obtained via the Dynamic Host Configuration Protocol (DHCP) fromnetwork 110.Mobile phone 105 may have a statically configured private IP address (e.g., on a same network as the private IP address of docking station 100).Mobile phone 105 may use the routable IP address ofdocking station 100 as a default gateway for sending VoIP packets tophone 130 vianetwork 110 andVoIP server 135. A physical and layer 2 connection betweendocking station 100 andmobile phone 105 may include Ethernet over Universal Serial Bus (USB) (e.g., Ethernet frames encapsulated in USB packets).Media 120 may be streamed from the private IP address associated withmobile phone 105 to the private IP address associated withdocking station 100, or may be streamed in the reverse direction. - When implementing the bridging mode,
system 140 may forward packets, at layer 2, fromnetwork 110, thoughdocking station 100, tomobile phone 105. Additionally,system 140 may forward packets, at layer 2, frommobile phone 105, thoughdocking station 100, tonetwork 110.Docking station 100 may have an IP address, routable innetwork 110, andmobile phone 105 may also have a different IP address that is routable innetwork 110.System 140, implementing the bridging mode, may forward packets received atdocking station 100 fromnetwork 110 to the routable IP address ofmobile phone 105. Additionally, when implementing the bridging mode,system 140 may forward packets, received frommobile phone 105 at the routable IP address ofdocking station 100, tonetwork 110. -
FIG. 2 is a diagram that depicts an exemplary implementation of the mobilephone docking station 100 ofFIG. 1 in which mobilephone docking station 100 implements NAPT or NAT for establishing a VoIP connection between the mobile phone and the external network. Whenmobile phone 105 is docked 115 intophone docking station 100, as shown inFIG. 1 ,media 200,other data 205,VoIP traffic 125 andother network traffic 210 may be sent to and frommobile phone 105 via a Universal Serial Bus (USB) 215, as further shown inFIG. 2 .Mobile phone 105, therefore, acts as a USB peripheral, andphone docking station 100 acts as a USB host. Ethernet overUSB protocol 235 may be used as the physical and layer 2 connection betweenphone docking station 100 andmobile phone 105. - As shown in
FIG. 2 ,mobile phone 105 may have a statically configuredIP address 220 that is non-routable from network 110 (but routable betweenIP address 225 ofphone docking station 100 andIP address 220 of mobile phone 105). As further shown inFIG. 2 ,phone docking station 100 may also have a statically configuredIP address 225 that is non-routable from network 110 (but routable betweenIP address 225 ofphone docking station 100 andIP address 220 of mobile phone 105), whereIP address 225 resides on a same private network (not shown) on whichIP address 220 ofmobile phone 105 resides. A private network (not shown inFIG. 2 ), therefore, exists betweenmobile phone 105 andphone docking station 100 via USB 215. As further shown inFIG. 2 ,phone docking station 100 may have anIP address 230 that is routable fromnetwork 110.Routable IP address 230 may be statically configured, or may be obtained via the DHCP protocol fromnetwork 110.Phone docking station 100 may, therefore, act as a DHCP server tomobile phone 105, thereby obtainingroutable IP address 230 that may be used bynetwork 110 to forwardVoIP traffic 125 andother network traffic 210 tomobile phone 105 via NAPT/NAT system 140. Non-routable,private IP address 220 onmobile phone 105 and non-routable,private IP address 225 onphone docking station 100 may be statically configured prior to the connection ofmobile phone 105 tophone docking station 100 via USB 215. By having aroutable IP address 230 onnetwork 110, a network administrator may managephone docking station 100 including, for example, providing software upgrades, firewall management, etc. The ability to addressphone docking station 100 fromnetwork 110 may not be available whenphone docking station 100 acts as an IP bridge (e.g., the exemplary bridging implementation ofFIG. 3 ). - Media 200 may include audio or video data (e.g., streaming audio or video) that may be streamed from
mobile phone 105 for playback onphone docking station 100, or that may be streamed fromphone docking station 100 for playback onmobile phone 105. Media 200 may be streamed frommobile phone 105IP address 220 to phone dockingstation IP address 225, or from phone dockingstation IP address 225 tomobile phone 105IP address 220.Other data 205 may include keypad information (e.g., indications of keypad presses on phone docking station 100), status information (e.g., voicemail message indicator light, etc.), and other information that may be exchanged between mobilephone IP address 220 andphone docking station 100IP address 225.Other data 205 may further include data other than audio or video data, such as, for example, web traffic data. The transfer ofmedia 200 and/orother data 205 may be through sockets, such as Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) sockets. -
VoIP traffic 125 may include VoIP signaling traffic (e.g., Session Initiation Protocol (SIP) traffic) and VoIP media traffic (e.g., Real-time Transport Protocol (RTP) or RTP Control Protocol (RTCP)) and may be forwarded throughphone docking station 100 via NAPT/NAT system 140. NAPT/NAT system 140 may implement a forwarding table that forwards packets to/frommobile phone 105 throughphone docking station 100 toroutable network 110. For VoIP applications, the forwarding table may be configured to pass SIP and RTP or RTCP traffic to/frommobile phone 105 toroutable network 110. Additionally,other network traffic 210 may be forwarded to/frommobile phone 105 throughphone docking station 100 toroutable network 110 by the forwarding table based on NAPT or NAT filtering. The forwarding table of NAPT/NAT system 140 may receive packets fromIP address 220 ofmobile phone 105 sent toroutable IP address 230 ofphone docking station 225, and may forward the packets to an appropriate next hop IP address in network 110 (e.g., to a next hop switch). The forwarding table of NAPT/NAT system 140 may further receive packets from an IP address innetwork 110 sent toroutable IP address 230, and may forward the packets tonon-routable IP address 220 ofmobile phone 105. A network administrator ofnetwork 110 may designate what kinds of traffic are permissible, and the forwarding table atphone docking station 100 may be configured appropriately (e.g., e-mail and web browsing may be forwarded whereas other undesirable traffic may be blocked during the forwarding process). A forwarding table implemented atmobile phone 105 may useroutable IP address 230 ofphone docking station 100 as the default gateway address for all outgoing packets. -
FIG. 3 is a diagram that depicts an exemplary implementation of the mobile phone docking station ofFIG. 1 in which the mobile phone docking station implements a bridging mode for establishing a VoIP connection between the mobile phone and the external network. Whenmobile phone 105 is docked 115 intophone docking station 100, as shown inFIG. 1 ,media 200,other data 205,VoIP traffic 125 andother network traffic 210 may be sent to and frommobile phone 105 via a Universal Serial Bus (USB) 215, as further shown inFIG. 3 .Mobile phone 105, therefore, acts as a USB peripheral, andphone docking station 100 acts as a USB host. Ethernet overUSB protocol 235 may be used as the physical and layer 2 connection betweenphone docking station 100 andmobile phone 105. - As shown in
FIG. 3 ,mobile phone 105 may have anIP address 300 that is routable fromnetwork 110. As further shown inFIG. 3 ,phone docking station 100 may also have aIP address 230 that is routable fromnetwork 110. Routable IP addresses 300 and 230 may be statically configured, or may be obtained via the DHCP protocol fromnetwork 110.Phone docking station 100 may, therefore, act as a DHCP server tomobile phone 105, thereby obtaining routable IP addresses 300 and 230 that may be used bynetwork 110 to forwardVoIP traffic 125 andother network traffic 210 tomobile phone 105 via bridgingsystem 140. -
Media 200 may be streamed frommobile phone 105 for playback onphone docking station 100, or may be streamed fromphone docking station 100 for playback onmobile phone 105.Media 200 may be streamed frommobile phone 105IP address 300 to phone dockingstation IP address 230, or from phone dockingstation IP address 230 tomobile phone 105IP address 300.Other data 205 may include keypad information, status information, and other information that may be exchanged between mobilephone IP address 300 andphone docking station 100IP address 230. -
VoIP traffic 125 may include VoIP signaling traffic (e.g., SIP traffic) and VoIP media traffic (e.g., RTP or RTCP) and may be forwarded throughphone docking station 100 via bridgingsystem 140.Bridging system 140 may forward, at layer 2, packets to/frommobile phone 105 throughphone docking station 100 toroutable network 110.Bridging system 140 may “transparently” forward packets, without any NAPT or NAT filtering as performed in the implementation ofFIG. 2 , frommobile phone 105 to network 110 and fromnetwork 110 tomobile phone 105. For example, ifnetwork 110 includes an Ethernet Local Area Network (LAN),bridging system 140 may forward Ethernet frames fromnetwork 110 tomobile phone 105 based on MAC addresses contained in the Ethernet frames. -
FIG. 4 is a diagram that depicts exemplary components ofphone docking station 100.Phone docking station 100 may include adocking port 400, a NAPT/NAT/Bridging system 140, acommunication interface 415, aprocessing unit 420, anaudio unit 425, avideo unit 430, adisplay 435, a keypad/touch input 440, a Near Field Communication (NFC)reader 445, and aBluetooth interface 450. -
Docking port 400 may include a port that may physically engage withmobile phone 105. The shape and size of dockingport 400 may be different based on a different external configuration ofmobile phone 105.Docking port 400 may further include aUSB port 405, which also include a charging port 410 (i.e.,USB port 405 may simultaneously act as a data port and a battery charging port). Though asingle USB port 405 is depicted inFIG. 4 ,phone docking station 100 may include multiple USB ports (not shown) and/or a USB hub. Chargingport 405 may include an electrical connection for supplying a charging current to a battery ofmobile phone 105.USB port 410 may include an electrical connection for the USB that may interconnectphone docking station 100 withmobile phone 105. - NAPT/NAT/
bridging system 140 may include, in one exemplary implementation that corresponds toFIG. 2 above, a system on a chip (SOC) that implements NAPT or NAT which modifies network address information in incoming packets for the purpose of translating one IP address space into another (e.g., remaps routable public IP addresses into private, non-routable IP addresses). NAPT/NAT/bridging system 140, when implementing NAPT or NAT, may be used to firewall and control traffic sent tomobile phone 105 viaphone docking station 100, thus, enhancing the security of, and control over, traffic carried by the dockedmobile phone 105. NAPT/NAT/bridging system 140 may include, in another exemplary implementation that corresponds toFIG. 3 above, a SOC that implements a bridging mode which may forward packets, at layer 2, fromnetwork 110, thoughdocking station 100, tomobile phone 105. Additionally, the SOC implementing the bridging mode may forward packets, at layer 2, frommobile phone 105, thoughdocking station 100, to network 110. -
Communication interface 415 may include a transceiver for communicating withnetwork 110.Processing unit 420 may include a processor, microprocessor, or processing logic that may interpret and execute instructions. The instructions may be stored in memory, such as, for example, a random access memory (RAM), a Read Only Memory (ROM), or another type of dynamic or static storage device that may store information and instructions for execution by processingunit 420. -
Audio unit 425 may include a microphone for receiving audio input intophone docking station 100, and may include mechanisms for playback of audio data received from the microphone, or received frommobile phone 105.Video unit 430 may include a camera for capturing video, and may further include mechanisms for playback of video data received from the camera, or received frommobile phone 105.Display 435 may a display device that may display video data or other types of data associated with the operation ofphone docking station 100 ormobile phone 105. In some implementations,display 430 may include a touch screen display that registers touch input at different locations upon the touch screen. Keypad/touch input unit 440 may include an alphanumeric keypad and mechanisms for receiving indications of touch input fromdisplay 430. -
NFC reader 445 may include a short range, high frequency system that enables the short range (e.g., 10 cm) exchange of data withmobile phone 105. Whenmobile phone 105 is placed in proximity to phone docking station 100 (e.g.,phone 105 is inserted into docking port 400),NFC reader 445 may “read” phone identity information from a corresponding NFC system located inphone 105. In addition to phone identity information,NFC reader 445 may also read phone user identity information from the corresponding NFC system located inphone 105.NFC reader 445 may, thus, be used to identify different phones that may be placed in proximity tophone docking station 100.Bluetooth interface 450 may include a short wavelength system for connecting with, and exchanging data over short distances, with any type of Bluetooth enabled device.Bluetooth interface 450 may, for example, connect with a Bluetooth enabled audio headset that permits a wearer to listen to audio fromaudio unit 425. - The configuration of components of
phone docking station 100 illustrated inFIG. 4 is for illustrative purposes only. Other configurations may be implemented. Therefore,phone docking station 100 may include additional, fewer and/or different components than those depicted inFIG. 4 . For example,phone docking station 100 may include a system(s) for implementing an Ethernet switch (not shown inFIG. 4 ), and/or for implementing Virtual Local Area Networks (VLANs).Phone docking station 100 may further include a magnetic sensor that may detect the insertion ofmobile phone 105 into dockingport 400 and may thereby initiate various functions atphone docking station 100 or at mobile phone 105 (e.g., initiate execution of a VoIP application atmobile phone 105, etc.). -
FIG. 5 is a diagram that depicts exemplary components ofmobile phone 105.Mobile phone 105 may include a bus 510, aprocessing unit 520, amain memory 530, a read only memory (ROM) 540, astorage device 550, an input device(s) 560, an output device(s) 570, acommunication interface 580, aUSB interface 590, and aNFC system 595. Bus 510 may include a path that permits communication among the elements ofmobile phone 105. -
Processing unit 520 may include a processor, microprocessor, or processing logic that may interpret and execute instructions.Main memory 530 may include a random access memory (RAM) or another type of dynamic storage device that may store information and instructions for execution by processingunit 520.ROM 540 may include a ROM device or another type of static storage device that may store static information and instructions for use by processingunit 520.Storage device 550 may include a magnetic and/or optical recording medium. -
Input device 560 may include one or more mechanisms that permit an operator to input information tomobile phone 105, such as, for example, a keypad or a keyboard, voice recognition and/or biometric mechanisms, etc.Output device 570 may include one or more mechanisms that output information to the operator, including a display, a speaker, etc.Communication interface 580 may include any transceiver mechanism that enablesmobile phone 105 to communicate with other devices and/or systems. For example,communication interface 580 may include a radio frequency transceiver for communicating via a PLMN or satellite network ofnetwork 110. USB I/F 590 may include interconnection mechanisms to permitphone 105 to physically and electrically connect withUSB port 405 ofphone docking station 100.NFC system 595 may include a short range, high frequency system that enables the short range exchange of data withmobile phone 105. Whenmobile phone 105 is placed in proximity to phone docking station 100 (e.g.,phone 105 is inserted into docking port 400), NFC system may transmit phone identity information and/or phone user identity information that may be “read” byNFC reader 445 ofphone docking station 100. - The configuration of components of
mobile phone 105 illustrated inFIG. 5 is for illustrative purposes only. Other configurations may be implemented. Therefore,mobile phone 105 may include additional, fewer and/or different components than those depicted inFIG. 5 . - The foregoing description of implementations provides illustration and description, but is not intended to be exhaustive or to limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention.
- Certain features described above may be implemented as “logic” or a “unit” that performs one or more functions. This logic or unit may include hardware, such as one or more processors, microprocessors, application specific integrated circuits, or field programmable gate arrays, software, or a combination of hardware and software.
- No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly described as such. Also, as used herein, the article “a” is intended to include one or more items. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
- In the preceding specification, various preferred embodiments have been described with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the invention as set forth in the claims that follow. The specification and drawings are accordingly to be regarded in an illustrative rather than restrictive sense.
Claims (20)
Priority Applications (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/971,409 US9143359B2 (en) | 2010-12-17 | 2010-12-17 | Mobile phone docking station for VoIP |
US13/036,444 US9060075B2 (en) | 2010-12-17 | 2011-02-28 | Mobile phone/docking station emergency call routing |
US13/040,336 US9736665B2 (en) | 2010-12-17 | 2011-03-04 | Original calling identification with mobile phone in docked mode |
US13/047,011 US8879420B2 (en) | 2010-12-17 | 2011-03-14 | Mobile phone docking station VPNs |
US13/116,123 US9008039B2 (en) | 2010-12-17 | 2011-05-26 | Mobile phone/docking station call continuity |
US13/355,630 US9031059B2 (en) | 2010-12-17 | 2012-01-23 | Fixed mobile convergence and voice call continuity using a mobile device/docking station |
US14/519,522 US9338093B2 (en) | 2010-12-17 | 2014-10-21 | Mobile phone docking station VPNs |
US14/679,355 US9826099B2 (en) | 2010-12-17 | 2015-04-06 | Mobile phone/docking station call continuity |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/971,409 US9143359B2 (en) | 2010-12-17 | 2010-12-17 | Mobile phone docking station for VoIP |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/116,123 Continuation-In-Part US9008039B2 (en) | 2010-12-17 | 2011-05-26 | Mobile phone/docking station call continuity |
Related Child Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/036,444 Continuation-In-Part US9060075B2 (en) | 2010-12-17 | 2011-02-28 | Mobile phone/docking station emergency call routing |
US13/040,336 Continuation-In-Part US9736665B2 (en) | 2010-12-17 | 2011-03-04 | Original calling identification with mobile phone in docked mode |
US13/047,011 Continuation-In-Part US8879420B2 (en) | 2010-12-17 | 2011-03-14 | Mobile phone docking station VPNs |
US13/116,123 Continuation-In-Part US9008039B2 (en) | 2010-12-17 | 2011-05-26 | Mobile phone/docking station call continuity |
US13/355,630 Continuation-In-Part US9031059B2 (en) | 2010-12-17 | 2012-01-23 | Fixed mobile convergence and voice call continuity using a mobile device/docking station |
Publications (2)
Publication Number | Publication Date |
---|---|
US20120155454A1 true US20120155454A1 (en) | 2012-06-21 |
US9143359B2 US9143359B2 (en) | 2015-09-22 |
Family
ID=46234353
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/971,409 Active 2032-06-13 US9143359B2 (en) | 2010-12-17 | 2010-12-17 | Mobile phone docking station for VoIP |
Country Status (1)
Country | Link |
---|---|
US (1) | US9143359B2 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130028144A1 (en) * | 2011-07-29 | 2013-01-31 | Verizon Patent And Licensing Inc. | Electronic hook switch capability for a mobile device connected docking station |
US20130290746A1 (en) * | 2012-04-30 | 2013-10-31 | Samsung Electronics Co., Ltd. | System, apparatus, and method of performing charging operation in host mode |
US20140036767A1 (en) * | 2012-08-03 | 2014-02-06 | Broadcom Corporation | Proximity Based Wireless Docking |
US8904051B2 (en) | 2011-12-26 | 2014-12-02 | Kt Corporation | Controlling multiple external device coupled to user equipment |
US20150066511A1 (en) * | 2013-08-30 | 2015-03-05 | Samsung Electronics Co., Ltd. | Image processing method and electronic device thereof |
US8984110B1 (en) * | 2012-02-14 | 2015-03-17 | Sonus Networks, Inc. | Secure media address learning for endpoints behind NAPT devices |
US20150245188A1 (en) * | 2013-08-28 | 2015-08-27 | Ebay Inc. | Wireless technology bridging system |
US9514306B2 (en) | 2011-12-26 | 2016-12-06 | Kt Corporation | Restricting operation results from being transferred to coupled external device |
US9542338B2 (en) | 2011-12-23 | 2017-01-10 | Kt Corporation | Controlling applications according to connection state and execution condition |
USD788761S1 (en) | 2014-12-03 | 2017-06-06 | MerchSource, LLC | Phone docking station |
US9766785B2 (en) | 2011-12-22 | 2017-09-19 | Kt Corporation | Selectively tranferring image data from user equipment to external device |
US10015594B2 (en) | 2016-06-23 | 2018-07-03 | Microsoft Technology Licensing, Llc | Peripheral device transducer configuration |
US20220210627A1 (en) * | 2020-12-29 | 2022-06-30 | Good Way Technology Co., Ltd. | Management system and device for check in and out using beacon technology |
US11715439B2 (en) | 2011-12-23 | 2023-08-01 | Kt Corporation | Dynamically controlling display mode of external device coupled to user equipment |
Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040122651A1 (en) * | 2002-12-23 | 2004-06-24 | Samsung Electronics Co., Ltd | Apparatus and method for ethernet emulation in a 3RD generation wireless mobile station |
US20040128554A1 (en) * | 2002-09-09 | 2004-07-01 | Netrake Corporation | Apparatus and method for allowing peer-to-peer network traffic across enterprise firewalls |
US20050013103A1 (en) * | 2003-07-17 | 2005-01-20 | Adrian Chandley | Multipurpose docking apparatus for a mobile computer |
US20060187900A1 (en) * | 2005-02-22 | 2006-08-24 | Akbar Imran M | Method and system for providing private virtual secure Voice over Internet Protocol communications |
US7107360B1 (en) * | 2001-07-24 | 2006-09-12 | Cisco Technology, Inc. | Network address translation in a gateway |
US7120241B1 (en) * | 2001-07-03 | 2006-10-10 | At&T Corp. | Method and apparatus for controlling a network device |
US7143198B2 (en) * | 2003-01-24 | 2006-11-28 | Samsung Electronics Co., Ltd. | Docking station for portable computer |
US20080151875A1 (en) * | 2006-12-22 | 2008-06-26 | Pyung-Bin Lim | VoIP service system using NAT and method of processing packet therein |
US20090001173A1 (en) * | 2007-06-28 | 2009-01-01 | Sevier Mitchel P | Bar code reading terminal with video capturing mode |
US20090059907A1 (en) * | 2007-08-30 | 2009-03-05 | Texas Instruments Incorporated | System, method and device for docking station for communication device |
US20090163139A1 (en) * | 2007-12-19 | 2009-06-25 | General Instrument Corporation | Apparatus and Method of Mobile Media Presentation Docking Station for Portable Electronic Device |
US20100074247A1 (en) * | 2006-12-19 | 2010-03-25 | Bce Inc. | Method, system and apparatus for intelligently handling a request for a communication session |
US20100157990A1 (en) * | 2008-12-19 | 2010-06-24 | Openpeak, Inc. | Systems for providing telephony and digital media services |
US20100250818A1 (en) * | 2009-03-27 | 2010-09-30 | Qualcomm Incorporated | System and method of providing wireless connectivity between a portable computing device and a portable computing device docking station |
US20110053643A1 (en) * | 2009-09-01 | 2011-03-03 | Vladimir Shmunis | Dock station for mobile devices |
US20120099566A1 (en) * | 2010-10-20 | 2012-04-26 | Nokia Corporation | Wireless docking with out-of-band initiation |
US20120303476A1 (en) * | 2010-11-09 | 2012-11-29 | Openpeak Inc. | Communication devices, networks, services and accompanying methods |
Family Cites Families (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6701361B1 (en) | 1996-08-22 | 2004-03-02 | Intermec Ip Corp. | Enhanced mobility and address resolution in a wireless premises based network |
US6148074A (en) | 1997-02-10 | 2000-11-14 | Genesys Telecommunications Laboratories, Inc. | Personal desktop router |
US6327470B1 (en) | 1997-11-07 | 2001-12-04 | Ericsson Inc. | Handover between fixed and mobile networks for dual mode phones |
US7110789B1 (en) | 2001-03-07 | 2006-09-19 | Kyocera Wireless Corp. | Wireless communications device docking system and method |
CA2453069C (en) | 2001-07-06 | 2012-05-29 | General Instrument Corporation | Methods, apparatus, and systems for accessing mobile and voice over ip telephone networks with a mobile handset |
US20050090271A1 (en) | 2003-10-24 | 2005-04-28 | Nortel Networks Limited | Call routing configuration from a mobile terminal docking station |
US7400886B2 (en) | 2004-01-09 | 2008-07-15 | Siemens Communications, Inc. | Call hand-over in a wireless local area network |
EP1730883B1 (en) | 2004-02-23 | 2011-06-22 | Roamware, Inc. | Integrated cellular voip for call rerouting |
US20050227666A1 (en) | 2004-03-30 | 2005-10-13 | Cheng Steven D | Method of accessing emergency numbers for mobile station users |
US7596120B2 (en) | 2004-12-07 | 2009-09-29 | Electronics And Telecommunications Research Institute | Multiple mode terminal supporting handoff between heterogeneous networks and handoff method thereof |
US9363384B2 (en) | 2005-04-06 | 2016-06-07 | Qwest Communications International Inc. | Systems for delivering calls on dual-mode wireless handsets |
US20060242305A1 (en) | 2005-04-25 | 2006-10-26 | Telefonaktiebolaget L M Ericsson (Publ) | VPN Proxy Management Object |
CN101009854A (en) | 2006-01-27 | 2007-08-01 | 朗迅科技公司 | Proxy phone number system for communication network client |
US9699308B2 (en) | 2006-08-16 | 2017-07-04 | Google Inc. | Method and system for processing an incoming call |
US20080139222A1 (en) | 2006-12-08 | 2008-06-12 | General Instrument Corporation | Presence Detection and Location Update in Premise Gateways |
US20080278894A1 (en) | 2007-05-11 | 2008-11-13 | Miradia Inc. | Docking station for projection display applications |
US9374348B2 (en) | 2007-07-19 | 2016-06-21 | Google Technology Holdings LLC | System and method to enable unlicensed mobile access across terminals |
US20090022301A1 (en) | 2007-07-19 | 2009-01-22 | Accenture Global Services Gmbh | Mobile services |
US20090097629A1 (en) | 2007-10-10 | 2009-04-16 | Nicholas Steven Huslak | Identification of Original Destination of Forwarded Communications |
US8787898B2 (en) | 2008-06-05 | 2014-07-22 | Centurylink Intellectual Property Llc | System, method and apparatus for remotely configuring selective call features |
US8300634B2 (en) | 2008-11-24 | 2012-10-30 | 8X8, Inc. | Mobile device communications routing |
US20110040858A1 (en) | 2009-08-13 | 2011-02-17 | Qualcomm Incorporated | Location determination during network address lookup |
US20110099507A1 (en) | 2009-10-28 | 2011-04-28 | Google Inc. | Displaying a collection of interactive elements that trigger actions directed to an item |
TWI389525B (en) | 2010-02-25 | 2013-03-11 | Gemtek Technology Co Ltd | System of multiple subnet accessible data transfer and method thereof |
US8412291B2 (en) | 2010-05-19 | 2013-04-02 | Microsoft Corporation | Detection, selection and provision of external antennas for a mobile device |
US20120057565A1 (en) | 2010-09-03 | 2012-03-08 | Avaya Inc. | Dls-assisted wired to wireless handover |
-
2010
- 2010-12-17 US US12/971,409 patent/US9143359B2/en active Active
Patent Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7120241B1 (en) * | 2001-07-03 | 2006-10-10 | At&T Corp. | Method and apparatus for controlling a network device |
US7107360B1 (en) * | 2001-07-24 | 2006-09-12 | Cisco Technology, Inc. | Network address translation in a gateway |
US20040128554A1 (en) * | 2002-09-09 | 2004-07-01 | Netrake Corporation | Apparatus and method for allowing peer-to-peer network traffic across enterprise firewalls |
US20040122651A1 (en) * | 2002-12-23 | 2004-06-24 | Samsung Electronics Co., Ltd | Apparatus and method for ethernet emulation in a 3RD generation wireless mobile station |
US7143198B2 (en) * | 2003-01-24 | 2006-11-28 | Samsung Electronics Co., Ltd. | Docking station for portable computer |
US20050013103A1 (en) * | 2003-07-17 | 2005-01-20 | Adrian Chandley | Multipurpose docking apparatus for a mobile computer |
US20060187900A1 (en) * | 2005-02-22 | 2006-08-24 | Akbar Imran M | Method and system for providing private virtual secure Voice over Internet Protocol communications |
US20100074247A1 (en) * | 2006-12-19 | 2010-03-25 | Bce Inc. | Method, system and apparatus for intelligently handling a request for a communication session |
US20080151875A1 (en) * | 2006-12-22 | 2008-06-26 | Pyung-Bin Lim | VoIP service system using NAT and method of processing packet therein |
US20090001173A1 (en) * | 2007-06-28 | 2009-01-01 | Sevier Mitchel P | Bar code reading terminal with video capturing mode |
US20090059907A1 (en) * | 2007-08-30 | 2009-03-05 | Texas Instruments Incorporated | System, method and device for docking station for communication device |
US20090163139A1 (en) * | 2007-12-19 | 2009-06-25 | General Instrument Corporation | Apparatus and Method of Mobile Media Presentation Docking Station for Portable Electronic Device |
US20100157990A1 (en) * | 2008-12-19 | 2010-06-24 | Openpeak, Inc. | Systems for providing telephony and digital media services |
US20100250818A1 (en) * | 2009-03-27 | 2010-09-30 | Qualcomm Incorporated | System and method of providing wireless connectivity between a portable computing device and a portable computing device docking station |
US20110053643A1 (en) * | 2009-09-01 | 2011-03-03 | Vladimir Shmunis | Dock station for mobile devices |
US20120099566A1 (en) * | 2010-10-20 | 2012-04-26 | Nokia Corporation | Wireless docking with out-of-band initiation |
US20120303476A1 (en) * | 2010-11-09 | 2012-11-29 | Openpeak Inc. | Communication devices, networks, services and accompanying methods |
Cited By (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8879430B2 (en) * | 2011-07-29 | 2014-11-04 | Verizon Patent And Licensing Inc. | Electronic hook switch capability for a mobile device connected docking station |
US20130028144A1 (en) * | 2011-07-29 | 2013-01-31 | Verizon Patent And Licensing Inc. | Electronic hook switch capability for a mobile device connected docking station |
US9766785B2 (en) | 2011-12-22 | 2017-09-19 | Kt Corporation | Selectively tranferring image data from user equipment to external device |
US11715439B2 (en) | 2011-12-23 | 2023-08-01 | Kt Corporation | Dynamically controlling display mode of external device coupled to user equipment |
US9542338B2 (en) | 2011-12-23 | 2017-01-10 | Kt Corporation | Controlling applications according to connection state and execution condition |
US8904051B2 (en) | 2011-12-26 | 2014-12-02 | Kt Corporation | Controlling multiple external device coupled to user equipment |
US9514306B2 (en) | 2011-12-26 | 2016-12-06 | Kt Corporation | Restricting operation results from being transferred to coupled external device |
US9553792B2 (en) * | 2012-02-14 | 2017-01-24 | Sonus Networks, Inc. | Secure media address learning for endpoints behind NAPT devices |
US8984110B1 (en) * | 2012-02-14 | 2015-03-17 | Sonus Networks, Inc. | Secure media address learning for endpoints behind NAPT devices |
US20150156104A1 (en) * | 2012-02-14 | 2015-06-04 | Sonus Networks, Inc. | Secure media address learning for endpoints behind napt devices |
US20130290746A1 (en) * | 2012-04-30 | 2013-10-31 | Samsung Electronics Co., Ltd. | System, apparatus, and method of performing charging operation in host mode |
US20140036767A1 (en) * | 2012-08-03 | 2014-02-06 | Broadcom Corporation | Proximity Based Wireless Docking |
US20170142546A1 (en) * | 2013-08-28 | 2017-05-18 | Paypal, Inc. | Wireless technology bridging system |
US20150245188A1 (en) * | 2013-08-28 | 2015-08-27 | Ebay Inc. | Wireless technology bridging system |
US10117082B2 (en) * | 2013-08-28 | 2018-10-30 | Paypal, Inc. | Wireless technology bridging system |
US20190239050A1 (en) * | 2013-08-28 | 2019-08-01 | Paypal, Inc. | Wireless technology bridging system |
US10631153B2 (en) * | 2013-08-28 | 2020-04-21 | Paypal, Inc. | Wireless technology bridging system |
US9560503B2 (en) * | 2013-08-28 | 2017-01-31 | Paypal, Inc. | Wireless technology bridging system |
US20150066511A1 (en) * | 2013-08-30 | 2015-03-05 | Samsung Electronics Co., Ltd. | Image processing method and electronic device thereof |
US9413969B2 (en) * | 2013-08-30 | 2016-08-09 | Samsung Electronics Co., Ltd. | Automatic image processing method and electronic device thereof |
USD788761S1 (en) | 2014-12-03 | 2017-06-06 | MerchSource, LLC | Phone docking station |
US10015594B2 (en) | 2016-06-23 | 2018-07-03 | Microsoft Technology Licensing, Llc | Peripheral device transducer configuration |
US20220210627A1 (en) * | 2020-12-29 | 2022-06-30 | Good Way Technology Co., Ltd. | Management system and device for check in and out using beacon technology |
TWI779761B (en) * | 2020-12-29 | 2022-10-01 | 東碩資訊股份有限公司 | Management system and docking station device |
US11743701B2 (en) * | 2020-12-29 | 2023-08-29 | Good Way Technology Co., Ltd. | Management system and device for check in and out using beacon technology |
US11800338B2 (en) | 2020-12-29 | 2023-10-24 | Good Way Technology Co., Ltd. | Management system, device, and server for controlling mesh network |
US20230354001A1 (en) * | 2020-12-29 | 2023-11-02 | Good Way Technology Co., Ltd. | Management system and device for check in and out using beacon technology |
US12004062B2 (en) | 2020-12-29 | 2024-06-04 | Good Way Technology Co., Ltd. | Management system and device for access of an electronic device to a host |
US12200591B2 (en) * | 2020-12-29 | 2025-01-14 | Good Way Technology Co., Ltd. | Management system and device for check in and out using beacon technology |
Also Published As
Publication number | Publication date |
---|---|
US9143359B2 (en) | 2015-09-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9143359B2 (en) | Mobile phone docking station for VoIP | |
US9031059B2 (en) | Fixed mobile convergence and voice call continuity using a mobile device/docking station | |
US9338093B2 (en) | Mobile phone docking station VPNs | |
US9060075B2 (en) | Mobile phone/docking station emergency call routing | |
US8879430B2 (en) | Electronic hook switch capability for a mobile device connected docking station | |
US9826099B2 (en) | Mobile phone/docking station call continuity | |
US9736665B2 (en) | Original calling identification with mobile phone in docked mode | |
US9002399B2 (en) | Mobile phone docking station multi-network telephony hub | |
US8064450B2 (en) | System and method for registering IP address of wireless communication device | |
EP2494798B1 (en) | Method and system for wan/wlan unicast and multicast communication | |
US20080220813A1 (en) | Multi-service cellular phone network access device | |
US9001699B2 (en) | Systems and methods for communication setup via reconciliation of internet protocol addresses | |
US9603115B2 (en) | Method and apparatus for cellular roaming charge bypass call completion | |
CN108235823A (en) | Proxy Free Cellular Roaming | |
EP2197169A1 (en) | VoIP registration with multiple call servers | |
EP3057280A1 (en) | Multiparty call method and apparatus | |
US8457111B2 (en) | Voice communication method and system in ubiquitous robotic companion environment | |
US20130163583A1 (en) | Systems and methods for communication setup via reconciliation of internet protocol addresses | |
US9735981B2 (en) | Facilitation of session initiation protocol trunking | |
US8437321B1 (en) | Method and system for communicating fixed IP address based voice data in a dynamic IP address based network environment | |
CN105208688A (en) | Route system based on intelligent terminal |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: VERIZON PATENT AND LICENSING INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:EICHEN, ELLIOT G.;JAVAREGOWDA, GOWTHAN;GOODMAN, LEE N.;AND OTHERS;REEL/FRAME:025517/0985 Effective date: 20101217 |
|
AS | Assignment |
Owner name: VERIZON PATENT AND LICENSING INC., NEW JERSEY Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE SECOND AND FOURTH ASSIGNOR NAME PREVIOUSLY RECORDED AT REEL: 025517 FRAME: 0985. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNORS:EICHEN, ELLIOT G.;JAVAREGOWDA, GOWTHAM;GOODMAN, LEE N.;AND OTHERS;REEL/FRAME:036397/0100 Effective date: 20101217 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |