This disclosure generally relates to information handling systems, and more particularly relates to personal computer and mobile phone communications through a peer-to-peer connection.
As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option is an information handling system. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes. Because technology and information handling needs and requirements can vary between different applications, information handling systems can also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information can be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems can include a variety of hardware and software components that can be configured to process, store, and communicate information and can include one or more computer systems, data storage systems, and networking systems.
It will be appreciated that for simplicity and clarity of illustration, elements illustrated in the Figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements are exaggerated relative to other elements. Embodiments incorporating teachings of the present disclosure are shown and described with respect to the drawings presented herein, in which:
The use of the same reference symbols in different drawings indicates similar or identical items.
The following description in combination with the Figures is provided to assist in understanding the teachings disclosed herein. The following discussion will focus on specific implementations and embodiments of the teachings. This focus is provided to assist in describing the teachings and should not be interpreted as a limitation on the scope or applicability of the teachings. However, other teachings can certainly be utilized in this application. The teachings can also be utilized in other applications and with several different types of architectures such as distributed computing architectures, client/server architectures, or middleware server architectures and associated components.
For purposes of this disclosure, an information handling system can include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an information handling system can be a personal computer, a PDA, a consumer electronic device, a network server or storage device, a switch router, wireless router, or other network communication device, or any other suitable device and can vary in size, shape, performance, functionality, and price. The information handling system can include memory, one or more processing resources such as a central processing unit (CPU) or hardware or software control logic. Additional components of the information handling system can include one or more storage devices, one or more communications ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system can also include one or more buses operable to transmit communications between the various hardware components.
Processor 110 is coupled to chipset 120. Chipset 120 supports processor 110, allowing processor 110 to process machine-executable code. In a particular embodiment, information handling system 100 includes one or more additional processors, and chipset 120 supports the multiple processors, allowing for simultaneous processing by each of the processors, permitting the exchange of information between the processors and the other elements of information handling system 100. Processor 110 can be coupled to chipset 120 via a unique channel, or via a bus that shares information between processor 110, chipset 120, and other elements of information handling system 100.
Memory 130 is coupled to chipset 120. Memory 130 can be coupled to chipset 120 via a unique channel, or via a bus that shares information between chipset 120, memory 130, and other elements of information handling system 100. In particular, a bus can share information between processor 110, chipset 120 and memory 130. In a particular embodiment, processor 110 is coupled to memory 130 through a unique channel. In accordance with another aspect, an information handling system can include a separate memory dedicated to each of the processors. A non-limiting example of memory 130 includes static, dynamic, or non-volatile random access memory (SRAM, DRAM, or NVRAM), read only memory (ROM), flash memory, another type of memory, or any combination thereof.
Graphics interface 140 is coupled to chipset 120. Graphics interface 140 can be coupled to chipset 120 via a unique channel, or via a bus that shares information between chipset 120, graphics interface 140, and other elements of information handling system 100. Graphics interface 140 is coupled to a video display 144. Other graphics interfaces can also be used in addition to graphics interface 140 if needed or desired. Video display 144 can include one or more types of video displays, such as a flat panel display or other type of display device.
I/O interface 150 is coupled to chipset 120. I/O interface 150 can be coupled to chipset 120 via a unique channel, or via a bus that shares information between chipset 120, I/O interface 150, and other elements of information handling system 100. Other I/O interfaces can also be used in addition to I/O interface 150 if needed or desired. I/O interface 150 is coupled to one or more add-on resources 154. Add-on resource 154 can also include another data storage system, a graphics interface, a network interface card (NIC), a sound/video processing card, another suitable add-on resource or any combination thereof.
Network interface device 170 is coupled to I/O interface 150. Network interface 170 can be coupled to I/O interface 150 via a unique channel, or via a bus that shares information between I/O interface 150, network interface 170, and other elements of information handling system 100. Other network interfaces can also be used in addition to network interface 170 if needed or desired. Network interface 170 can be a NIC disposed within information handling system 100, on a main circuit board (such as a baseboard, a motherboard, or any combination thereof), integrated onto another component such as chipset 120, in another suitable location, or any combination thereof. Network interface 170 includes a network channel 172 that provide interfaces between information handling system 100 and other devices that are external to information handling system 100. Network interface 170 can also include additional network channels.
In an embodiment, radio frequency interface device 174 is coupled to I/O interface 150. Radio frequency interface device 174 can be coupled to I/O interface 150 via a unique channel, or via a bus that shares information between I/O interface 150, radio frequency interface device 174, and other elements of information handling system 100. Radio frequency interface device 174 can provide for radio frequency communication, such as via Bluetooth, Wi-Fi Direct, or other similar communications protocol, between information handling system 100 and other devices that are external to information handling system 100.
Disk controller 160 is coupled to chipset 110. Disk controller 160 can be coupled to chipset 120 via a unique channel, or via a bus that shares information between chipset 120, disk controller 160, and other elements of information handling system 100. Other disk controllers can also be used in addition to disk controller 160 if needed or desired. Disk controller 160 can include a disk interface 162. Disk controller 160 can be coupled to one or more disk drives via disk interface 162. Such disk drives include a hard disk drive (HDD) 164 or an optical disk drive (ODD) 166 (such as a Read/Write Compact Disk (R/W-CD), a Read/Write Digital Video Disk (R/W-DVD), a Read/Write mini Digital Video Disk (R/W mini-DVD), or another type of optical disk drive), or any combination thereof. Additionally, disk controller 160 can be coupled to disk emulator 180. Disk emulator 180 can permit a solid-state drive 184 to be coupled to information handling system 100 via an external interface. The external interface can include industry standard busses (such as USB or IEEE 1384 (Firewire)) or proprietary busses, or any combination thereof. Alternatively, solid-state drive 184 can be disposed within information handling system 100.
In a particular embodiment, HDD 144, ODD 166, solid state drive 184, or a combination thereof include a computer-readable medium in which one or more sets of machine-executable instructions such as software can be embedded. For example, the instructions can embody one or more of the methods or logic as described herein. In a particular embodiment, the instructions reside completely, or at least partially, within memory 130, and/or within processor 110 during execution by information handling system 100. Memory 130 and processor 110 can also include computer-readable media.
In an embodiment, the information handling system 202 can execute a softphone. The softphone can be a software program for making telephone calls over the Internet. The softphone can communicate with the remote system 210 using one or more Internet telephony protocols, such as Skype, Google Talk, Inter-Asterisk Exchange (IAX) protocol, or session initiation protocol (SIP). The softphone can process the signaling information needed to set up a media channel for communicating audio, and optionally video, with the remote system 210. Additionally, the softphone may encode and decode the audio in a format compatible for Internet telephony.
Further, the information handling system 202 can establish a bi-directional audio connection with the portable communication device 204. The bi-directional audio connection can enable audio from the telephone call to be sent to and received from the portable communication device 204. However, the signaling and media channel setup information may not be passed from the information handling system 202 to the portable communication device 204. The bi-direction audio communication can utilize a Headset Profile (HSP) or Hands-Free Profile (HFP) over a Bluetooth link. Alternatively, the bi-directional audio communication can utilize Wi-Fi Direct, Wireless USB, or other appropriate wireless communication.
In a particular embodiment, upon receiving an incoming call, the information handling system 202 may signal the portable communication device 204 to generate a ring and may provide caller identification information for display by the portable communication device. Additionally, the portable communication device 204 can provide a phone number and signal the information handling system 202 to initiate a call to that number.
Alternatively, when the softphone fails to detect a headset, the softphone can determine if a portable communication device is present, as illustrated at 308. The portable communication device can be a cell phone, a smart phone, or other device capable of making a telephone call independent from the information handling system. When the softphone detects that a portable communication device is present, the softphone can initiate a portable communication device profile so that audio communications associated with a telephone call of the information handling system are routed through the portable communication device, as illustrated at 310. Additionally, the softphone and the portable communication device can associate to enable the audio communication to be routed through the portable communication device, as illustrated at 312.
Returning to 308, when the softphone fails to detect a portable communication device, the softphone can initiate a built-in profile, as illustrated at 314, to route audio communications associated with the telephone call can be routed through a speaker and microphone of the information handling system.
When a portable communication device is present, at 408, the information handling system can signal the portable communication device of an incoming call and the portable communication device can signal the presence of the incoming call such as by generating an audible tone or displaying information on a display of the portable communication device. For example, the portable communication device may generate a ring tone and display caller identification information on the display.
In an embodiment, the portable communication device can match caller identification information with phone numbers stored by the portable communication device to select a ring tone associated with the phone number. In another embodiment, the portable communication device can select a ring tone to indicate that the call is received through the information handling system.
At 410, the portable communication device can determine if the call is picked up by a user. When the call is picked up, the portable communication device can signal the information handling system and the call audio can be routed to the portable communication device, as illustrated at 412. Alternatively, when the call is not picked up, the call can be directed to a voicemail system, as illustrated at 414.
At 504, the user can initiate the call. For example, the user can enter a phone number or select a contact from an address book or call history. In an embodiment, once the user selects to use a softphone of the information handling system, the personal communication device may access a contact list or call history of the softphone to enable the user to select phone numbers stored by the softphone in addition to phone numbers stored by the personal communication device.
At 506, the personal communication device can decide if the call should be established using the information handling system. When the call should not be established using the information handling system, the personal communication device can establish the call, as illustrated at 508. Alternatively, the personal communication device can establish a connection with the softphone on the information handling system, as illustrated at 510. Additionally, the personal communication device can provide the phone number to the softphone. At 512, the softphone can establish the call with the called party and route the audio to the personal communication device through a bi-directional audio connection.
When referred to as a “device,” the embodiments described above can be configured as hardware, or a combination of hardware and software. For example, a portion of an information handling system device may be hardware such as, for example, an integrated circuit (such as an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a structured ASIC, or a device embedded on a larger chip), a card (such as a Peripheral Component Interface (PCI) card, a PCI-express card, a Personal Computer Memory Card International Association (PCMCIA) card, or other such expansion card), or a system (such as a motherboard, a system-on-a-chip (SoC), or a stand-alone device). Similarly, the device could further include software, including firmware embedded at a device, such as x86 class and/or ARM, MIPs or other controller based system, or software capable of operating a relevant environment of the information handling system. Note that an information handling system can include an integrated circuit or a board-level product having portions thereof that can also be any combination of hardware and software.
Devices, modules, resources, or programs that are in communication with one another need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices, modules, resources, or programs that are in communication with one another can communicate directly or indirectly through one or more intermediaries.
In a particular embodiment, an information handling system can be used to function as one or more of the network systems, or carry out one or more of the methods described above. In another embodiment, one or more of the systems described above can be implemented in the form of an information handling system.
Although only a few exemplary embodiments have been described in detail above, those skilled in the art will readily appreciate that many modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of the embodiments of the present disclosure. Accordingly, all such modifications are intended to be included within the scope of the embodiments of the present disclosure as defined in the following claims. In the claims, means-plus-function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents, but also equivalent structures.