Conventional mobile devices may use a cellular network primarily for calling and texting, and a Wi-Fi network (under IEEE 802.11) to access data, for example, when accessing the Internet and consuming media such as music and video. Mobile devices typically express connectivity to these networks with graphics such as cellular bars and Wi-Fi glyphs. In addition, the mobile devices often display glyphs for the various network types and speeds such as LTE (Long Term Evolution), 3G (Third generation of mobile communications technology under the International Mobile Telecommunications-2000 (IMT-2000)), 4G (Fourth generation under IMT-2000), EDGE (Enhanced Data rates for GSM Evolution), etc. The user typically needs to read all of these graphics in combination when assessing the potential quality of calls and Internet access. Accordingly, while such conventional mobile devices can often provide satisfactory performance, opportunities exist to make them more effective with more comprehensive features and benefits to users.
This Background is provided to introduce a brief context for the Summary and Detailed Description that follow. This Background is not intended to be an aid in determining the scope of the claimed subject matter nor be viewed as limiting the claimed subject matter to implementations that solve any or all of the disadvantages or problems presented above.
A mobile device having capabilities to access connections to cellular and Wi-Fi portions of a hybrid telecommunications network is configured to display a variety of different icons that graphically indicate a current connection status for both data usage and voice calling on a graphical user interface (GUI). A user can put the GUI into an expanded state to show additional information about the connection status including textual descriptions of icons to instruct the user as to the specific meaning of a given icon. The textual descriptions enable an association between the iconography and the connection state to be established for the user. The icons can then quickly and effectively convey connection state to the user in a comprehensive manner while efficiently using the available display space on the device.
In various illustrative examples, the icons are displayed in an area of the GUI on the mobile device referred to as the system tray along with other elements such as date/time, battery charge status, etc. The user can interact with the touchscreen on the device, or manipulate other controls (e.g., using voice command and gesture recognition systems installed on the mobile device, and the like) to place the system tray into an expanded state to show additional information including a textual description of the icon that represents the current connection state and other information such as cellular and Wi-Fi signal strength, and mobile operator identification. The different connection states illustratively include those that support: i) Wi-Fi calling and Wi-Fi data access; ii) Cellular calling and Wi-Fi data access; iii) No calling and Wi-Fi data access; iv) Cellular calling and cellular data access; v) No calling and cellular data access; vi) Cellular calling and no data access; and, vii) No calling and no data access.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure. It will be appreciated that the above-described subject matter may be implemented as a computer-controlled apparatus, a computer process, a computing system, or as an article of manufacture such as one or more computer-readable storage media. These and various other features will be apparent from a reading of the following Detailed Description and a review of the associated drawings.
Like reference numerals indicate like elements in the drawings. Elements are not drawn to scale unless otherwise indicated.
Other types of telephony equipment may also be present in the telecommunications environment 100 such as conventional desktop phones 120 which are operatively coupled to a public switched telephone network (PSTN). Other examples may include equipment that connects to the PSTN using private branch exchanges (PBXs) and equipment coupled to call services that are accessed using telephone numbers. This other telephony equipment may still be utilized in various scenarios involving a hybrid telecommunications network connection indicator, even though it might not implement such functionality itself. For example, a mobile phone 110 may make or receive a call to a desktop phone 120 and employ voice call continuity (as described in more detail below) as the prevailing connection conditions change such as when the mobile device user moves from a car to home during a call.
The hybrid telecommunications network 115 comprises several networks 1, 2 . . . N, identified in
Each mobile device 110 will typically have a prearranged association with one or more of the networks underlying the hybrid telecommunications network 115. For example, a user 105 will typically be a subscriber to a cellular telephone service so that the user's mobile device 110 can access a given cellular network as valid and authenticated user equipment. Similarly, the mobile device 110 may include functionality and credentials to access a Wi-Fi network. The mobile devices 110 may also interoperate with a VoIP network and be capable of providing voice call continuity (VCC) across different connection types according to a prearranged association. Such mobile devices are considered “VCC-equipped” and can access the hybrid telecommunications network 115 over the different types of connections.
In some situations, a mobile device may be placed in a dock or cradle that is coupled to the PSTN and thus could employ a wireline connection for a call which is often the least expensive network connection. Typically, the mobile devices 110 use the less expensive Wi-Fi connection whenever it is available and capable of providing a reasonable level of call quality. When Wi-Fi is not available or is inadequate for the voice call, the call may be made over one of the other available network connection options after determining that the selected connection will result in acceptable call quality. Cellular voice is typically the costliest connection alternative but also the most ubiquitous and so it is used to ensure that the user has access to calling services from as wide an area as possible. In the description that follows, the mobile devices 110 are considered to be VCC equipped unless otherwise indicated.
A characteristic of the hybrid telecommunications network 115 is that two or more of the underlying networks (e.g., networks 125, 130, 135) are considered loosely coupled. That is, in one illustrative example, the VoIP network and the MO network are typically operated independently so that one network cannot exercise significant or substantial control over the operation of the other. However, as shown in
While such hybridization can provide cost-effective and high quality transport, the loose coupling has traditionally presented difficulties for voice call continuity. Voice call continuity functionality is defined here as the maintenance of ongoing voice calls for a device that is capable of placing and receiving voice calls in the face of changes in prevailing connection conditions perhaps due to user mobility or other environmental factors. For example, the connection currently being used, such as Wi-Fi under IEEE (Institute of Electrical and Electronic Engineers) 802.11 could start demonstrating worsening radio signal and/or network congestion conditions, or the user could move to a location where the Wi-Fi connection does not work at all. In addition, other connection options may become available that are lower cost, or provide a better user experience, and therefore either or both the user and network operator may wish to utilize such connection options.
For example, as shown in
If the handoff is initiated so that both the original and newly selected connections are operative simultaneously then there will be an intermediate state in which both call legs will be running in parallel. Media flows can be directed to and from the mobile device over these parallel connections, until one of the two flows is terminated. Such intermediate state enables the call to be maintained in an uninterrupted manner as perceived by the parties on both ends of the call. During the intermediate state, the mobile device can typically choose to connect to one of the two flows as it deems appropriate.
The particular elements shown in the system tray 515 are typically selected as a matter of design choice and thus can vary from what is shown in
In addition, the specific icons shown in the drawings have been simplified for sake of clarity in exposition given the inherent limitations of black and white line art. Thus, it will be appreciated that icons variously including shading, colors, shadows, transparency, animations, and the like may be utilized in particular instances of a hybrid telecommunications network connection indicator without departing from the spirit and scope of the present description.
Returning to
In this particular illustrative example, the graphical elements exposed by the expanded system tray are arranged in three rows, respectively indicated by reference numerals 1720, 1725, and 1730. As shown, the top row 1720 of graphical elements includes a hybrid telecommunications network connection icon—here, icon 600—along with a corresponding textual description 1735 for the icon. The second row 1725 of graphical elements retains the battery charge state indicator 530 and time of day indicator 535 from the normal system tray and adds new elements including a cellular connection signal strength indicator 1740 and Wi-Fi connection signal strength indicator 1745. The third row 1730 adds new graphical elements including an identification 1750 of the current MO/cellular carrier (e.g., the cellular carrier can change when the user is roaming away from his or her home cellular network), a numerical representation of the charge state 1755, and date indicator 1760.
As described above, the textual description 1735 enables an association between the iconography and the connection state to the hybrid telecommunications network to be established for the user 105. In some cases, the icon 600 and/or textual description 1735 can be highlighted in some manner, for example, using colors, animation, sounds, music, and other devices/techniques in order to attract the user's attention to further affirm and reinforce the association between the icon and its meaning for the user when the system tray is in its expanded state. In this way, the system tray supplies its own built-in “help” function to provide training to the user as to the meaning of iconography it uses to impart information when it is placed in its expanded state. As the user gains experience and familiarity with the iconography through this built in training tool, a quick glance at the icon in the normal/unexpanded system tray enables the hybrid telecommunications network connection state to be ascertained.
The hybrid telecommunications network connection indicator icons, while occupying only a relatively small space in the system tray (and in the mobile device's GUI overall), can still provide a comprehensive amount of connection state information to the user. Such information can be expected to be of great interest and value to users who typically are looking to employ their mobile devices in ways that maximize their utility while minimizing their operating costs. For example, by knowing when lower cost connections are available, the user can plan calling and data usage to minimize usage of relatively expensive cellular connections. Alternatively, the user may purposely wish to use a cellular connection for calling or data access in cases where Wi-Fi coverage is less robust/reliable or may be expected to become unavailable (e.g., the user is planning to get in the car and move out of Wi-Fi coverage at home).
The enlarged detail view 1765 shows the expanded system tray 1715 for a connection state in which cellular calling is enabled with Wi-Fi data access. In this example, the icon 700 is displayed with the corresponding textual description 1735. The enlarged detail view 1770 shows the expanded system tray 1715 for a connection state in which cellular calling is enabled but Wi-Fi data access is unavailable. In this example, the icon 1100 is displayed with the corresponding textual description 1735. Also, the Wi-Fi signal strength indicator is shown with a prohibition symbol 1775 in this scenario.
In step 1830, the mobile device displays the expanded system tray 1715 (
A number of program modules may be stored on the hard disk 1928, magnetic disk 1933, optical disk 1943, ROM 1917, or RAM 1921, including an operating system 1955, one or more application programs 1957, other program modules 1960, and program data 1963. A user may enter commands and information into the computer system 1900 through input devices such as a keyboard 1966 and pointing device 1968 such as a mouse. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, trackball, touchpad, touch screen, touch-sensitive device, voice-command module or device, user motion or user gesture capture device, or the like. These and other input devices are often connected to the processor 1905 through a serial port interface 1971 that is coupled to the system bus 1914, but may be connected by other interfaces, such as a parallel port, game port, or universal serial bus (USB). A monitor 1973 or other type of display device is also connected to the system bus 1914 via an interface, such as a video adapter 1975. In addition to the monitor 1973, personal computers typically include other peripheral output devices (not shown), such as speakers and printers. The illustrative example shown in
The computer system 1900 is operable in a networked environment using logical connections to one or more remote computers, such as a remote computer 1988. The remote computer 1988 may be selected as another personal computer, a server, a router, a network PC, a peer device, or other common network node, and typically includes many or all of the elements described above relative to the computer system 1900, although only a single representative remote memory/storage device 1990 is shown in
When used in a LAN networking environment, the computer system 1900 is connected to the local area network 1993 through a network interface or adapter 1996. When used in a WAN networking environment, the computer system 1900 typically includes a broadband modem 1998, network gateway, or other means for establishing communications over the wide area network 1995, such as the Internet. The broadband modem 1998, which may be internal or external, is connected to the system bus 1914 via a serial port interface 1971. In a networked environment, program modules related to the computer system 1900, or portions thereof, may be stored in the remote memory storage device 1990. It is noted that the network connections shown in
The architecture 2000 illustrated in
The mass storage device 2012 is connected to the CPU 2002 through a mass storage controller (not shown) connected to the bus 2010. The mass storage device 2012 and its associated computer-readable storage media provide non-volatile storage for the architecture 2000.
Although the description of computer-readable storage media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, it should be appreciated by those skilled in the art that computer-readable storage media can be any available storage media that can be accessed by the architecture 2000.
By way of example, and not limitation, computer-readable storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. For example, computer-readable media includes, but is not limited to, RAM, ROM, EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), Flash memory or other solid state memory technology, CD-ROM, DVDs, HD-DVD (High Definition DVD), Blu-ray, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the architecture 2000.
According to various embodiments, the architecture 2000 may operate in a networked environment using logical connections to remote computers through a network. The architecture 2000 may connect to the network through a network interface unit 2016 connected to the bus 2010. It should be appreciated that the network interface unit 2016 also may be utilized to connect to other types of networks and remote computer systems. The architecture 2000 also may include an input/output controller 2018 for receiving and processing input from a number of other devices, including a keyboard, mouse, or electronic stylus (not shown in
It should be appreciated that the software components described herein may, when loaded into the CPU 2002 and executed, transform the CPU 2002 and the overall architecture 2000 from a general-purpose computing system into a special-purpose computing system customized to facilitate the functionality presented herein. The CPU 2002 may be constructed from any number of transistors or other discrete circuit elements, which may individually or collectively assume any number of states. More specifically, the CPU 2002 may operate as a finite-state machine, in response to executable instructions contained within the software modules disclosed herein. These computer-executable instructions may transform the CPU 2002 by specifying how the CPU 2002 transitions between states, thereby transforming the transistors or other discrete hardware elements constituting the CPU 2002.
Encoding the software modules presented herein also may transform the physical structure of the computer-readable storage media presented herein. The specific transformation of physical structure may depend on various factors, in different implementations of this description. Examples of such factors may include, but are not limited to, the technology used to implement the computer-readable storage media, whether the computer-readable storage media is characterized as primary or secondary storage, and the like. For example, if the computer-readable storage media is implemented as semiconductor-based memory, the software disclosed herein may be encoded on the computer-readable storage media by transforming the physical state of the semiconductor memory. For example, the software may transform the state of transistors, capacitors, or other discrete circuit elements constituting the semiconductor memory. The software also may transform the physical state of such components in order to store data thereupon.
As another example, the computer-readable storage media disclosed herein may be implemented using magnetic or optical technology. In such implementations, the software presented herein may transform the physical state of magnetic or optical media, when the software is encoded therein. These transformations may include altering the magnetic characteristics of particular locations within given magnetic media. These transformations also may include altering the physical features or characteristics of particular locations within given optical media to change the optical characteristics of those locations. Other transformations of physical media are possible without departing from the scope and spirit of the present description, with the foregoing examples provided only to facilitate this discussion.
In light of the above, it should be appreciated that many types of physical transformations take place in the architecture 2000 in order to store and execute the software components presented herein. It also should be appreciated that the architecture 2000 may include other types of computing devices, including handheld computers, embedded computer systems, smartphones, PDAs, and other types of computing devices known to those skilled in the art. It is also contemplated that the architecture 2000 may not include all of the components shown in
The illustrated mobile device 110 can include a controller or processor 2110 (e.g., signal processor, microprocessor, microcontroller, ASIC (Application Specific Integrated Circuit), or other control and processing logic circuitry) for performing such tasks as signal coding, data processing, input/output processing, power control, and/or other functions. An operating system 2112 can control the allocation and usage of the components 2102, including power states, above-lock states, and below-lock states, and provides support for one or more application programs 2114. The application programs can include common mobile computing applications (e.g., image-capture applications, email applications, calendars, contact managers, web browsers, messaging applications), or any other computing application.
The illustrated mobile device 110 can include memory 2120. Memory 2120 can include non-removable memory 2122 and/or removable memory 2124. The non-removable memory 2122 can include RAM, ROM, Flash memory, a hard disk, or other well-known memory storage technologies. The removable memory 2124 can include Flash memory or a Subscriber Identity Module (SIM) card, which is well known in GSM (Global System for Mobile communications) systems, or other well-known memory storage technologies, such as “smart cards.” The memory 2120 can be used for storing data and/or code for running the operating system 2112 and the application programs 2114. Example data can include web pages, text, images, sound files, video data, or other data sets to be sent to and/or received from one or more network servers or other devices via one or more wired or wireless networks.
The memory 2120 may also be arranged as, or include, one or more computer-readable storage media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. For example, computer-readable media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, Flash memory or other solid state memory technology, CD-ROM (compact-disc ROM), DVD, (Digital Versatile Disc) HD-DVD (High Definition DVD), Blu-ray, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the mobile device 110.
The memory 2120 can be used to store a subscriber identifier, such as an International Mobile Subscriber Identity (IMSI), and an equipment identifier, such as an International Mobile Equipment Identifier (IMEI). Such identifiers can be transmitted to a network server to identify users and equipment. The mobile device 110 can support one or more input devices 2130; such as a touch screen 2132; microphone 2134 for implementation of voice input for voice recognition, voice commands and the like; camera 2136; physical keyboard 2138; trackball 2140; and/or proximity sensor 2142; and one or more output devices 2150, such as a speaker 2152 and one or more displays 2154. Other input devices (not shown) using gesture recognition may also be utilized in some cases. Other possible output devices (not shown) can include piezoelectric or haptic output devices. Some devices can serve more than one input/output function. For example, touchscreen 2132 and display 2154 can be combined into a single input/output device.
A wireless modem 2160 can be coupled to an antenna (not shown) and can support two-way communications between the processor 2110 and external devices, as is well understood in the art. The modem 2160 is shown generically and can include a cellular modem for communicating with the mobile communication network 2104 and/or other radio-based modems (e.g., Bluetooth 2164 or Wi-Fi 2162). The wireless modem 2160 is typically configured for communication with one or more cellular networks, such as a GSM network for data and voice communications within a single cellular network, between cellular networks, or between the mobile device and a public switched telephone network (PSTN).
The mobile device can further include at least one input/output port 2180, a power supply 2182, a satellite navigation system receiver 2184, such as a Global Positioning System (GPS) receiver, an accelerometer 2186, a gyroscope (not shown), and/or a physical connector 2190, which can be a USB port, IEEE 1394 (FireWire) port, and/or an RS-232 port. The illustrated components 2102 are not required or all-inclusive, as any components can be deleted and other components can be added.
Based on the foregoing, it should be appreciated that technologies for a hybrid telecommunications network connection indicator have been disclosed herein. Although the subject matter presented herein has been described in language specific to computer structural features, methodological and transformative acts, specific computing machinery, and computer-readable storage media, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features, acts, or media described herein. Rather, the specific features, acts, and mediums are disclosed as example forms of implementing the claims.
The subject matter described above is provided by way of illustration only and should not be construed as limiting. Various modifications and changes may be made to the subject matter described herein without following the example embodiments and applications illustrated and described, and without departing from the true spirit and scope of the present invention, which is set forth in the following claims.
Number | Name | Date | Kind |
---|---|---|---|
6148206 | Karanja et al. | Nov 2000 | A |
6335927 | Elliott et al. | Jan 2002 | B1 |
6343220 | Van Der Salm | Jan 2002 | B1 |
6490449 | Thibert et al. | Dec 2002 | B1 |
6518957 | Lehtinen | Feb 2003 | B1 |
6763226 | McZeal, Jr. | Jul 2004 | B1 |
7010002 | Chow et al. | Mar 2006 | B2 |
7110750 | Oishi et al. | Sep 2006 | B2 |
7411911 | Huotari et al. | Aug 2008 | B2 |
7483984 | Jonker et al. | Jan 2009 | B1 |
7631270 | Cunningham et al. | Dec 2009 | B2 |
7697479 | Metke et al. | Apr 2010 | B2 |
7706291 | Luft et al. | Apr 2010 | B2 |
7746989 | Mazor | Jun 2010 | B2 |
7796998 | Zellner et al. | Sep 2010 | B1 |
7830863 | Biage et al. | Nov 2010 | B2 |
7835751 | Ibe | Nov 2010 | B2 |
7894807 | Drennan | Feb 2011 | B1 |
7903794 | Bales et al. | Mar 2011 | B1 |
7986943 | Bumiller | Jul 2011 | B2 |
7995565 | Buckley et al. | Aug 2011 | B2 |
8000710 | Jagadeesan et al. | Aug 2011 | B2 |
8032122 | Sigmund et al. | Oct 2011 | B2 |
8126465 | Lu et al. | Feb 2012 | B2 |
8155084 | Long et al. | Apr 2012 | B2 |
8254986 | Russell | Aug 2012 | B2 |
8670405 | Lee | Mar 2014 | B1 |
8976950 | Kramarenko | Mar 2015 | B2 |
9001787 | Conant | Apr 2015 | B1 |
9408077 | David | Aug 2016 | B1 |
20020059453 | Eriksson et al. | May 2002 | A1 |
20020146000 | Jonsson et al. | Oct 2002 | A1 |
20030231759 | Bedingfield, Sr. et al. | Dec 2003 | A1 |
20040047339 | Wang et al. | Mar 2004 | A1 |
20040121761 | Tripathy et al. | Jun 2004 | A1 |
20040203607 | Satapathy | Oct 2004 | A1 |
20040240430 | Lin et al. | Dec 2004 | A1 |
20050070291 | Shi | Mar 2005 | A1 |
20050186960 | Jiang | Aug 2005 | A1 |
20050249196 | Ansari et al. | Nov 2005 | A1 |
20050286466 | Tagg et al. | Dec 2005 | A1 |
20060029049 | Kobayashi et al. | Feb 2006 | A1 |
20060030357 | McConnell et al. | Feb 2006 | A1 |
20060045069 | Zehavi et al. | Mar 2006 | A1 |
20060121902 | Jagadeesan et al. | Jun 2006 | A1 |
20060133582 | McCulloch | Jun 2006 | A1 |
20060187900 | Akbar | Aug 2006 | A1 |
20060198360 | Biage et al. | Sep 2006 | A1 |
20060245413 | Skalecki et al. | Nov 2006 | A1 |
20070067734 | Cunningham | Mar 2007 | A1 |
20070070948 | Kezys et al. | Mar 2007 | A1 |
20070081518 | Jain et al. | Apr 2007 | A1 |
20070083918 | Pearce | Apr 2007 | A1 |
20070086584 | Rossini | Apr 2007 | A1 |
20070197224 | Winkler | Aug 2007 | A1 |
20070206568 | Silver | Sep 2007 | A1 |
20070206571 | Silver | Sep 2007 | A1 |
20070217366 | Sagi et al. | Sep 2007 | A1 |
20070263613 | Hara et al. | Nov 2007 | A1 |
20080026732 | Goldfarb | Jan 2008 | A1 |
20080032695 | Zhu et al. | Feb 2008 | A1 |
20080056235 | Albina et al. | Mar 2008 | A1 |
20080096560 | Felske et al. | Apr 2008 | A1 |
20080102815 | Sengupta et al. | May 2008 | A1 |
20080113683 | Paas | May 2008 | A1 |
20080123625 | Buckley | May 2008 | A1 |
20080192900 | Liu | Aug 2008 | A1 |
20080232352 | Terrill et al. | Sep 2008 | A1 |
20080242299 | Edwards | Oct 2008 | A1 |
20080254797 | Achtari et al. | Oct 2008 | A1 |
20080261603 | Sever | Oct 2008 | A1 |
20080279176 | Cheng | Nov 2008 | A1 |
20090003316 | Lee | Jan 2009 | A1 |
20090086937 | Horn et al. | Apr 2009 | A1 |
20090097450 | Wallis et al. | Apr 2009 | A1 |
20090141682 | Zou et al. | Jun 2009 | A1 |
20090191876 | Jain et al. | Jul 2009 | A1 |
20090233602 | Hughes | Sep 2009 | A1 |
20090249247 | Tseng | Oct 2009 | A1 |
20090285175 | Nix | Nov 2009 | A1 |
20090305732 | Marcellino | Dec 2009 | A1 |
20100080128 | Hovey et al. | Apr 2010 | A1 |
20100124897 | Edge | May 2010 | A1 |
20100172323 | Rexhepi et al. | Jul 2010 | A1 |
20100172483 | Weiner | Jul 2010 | A1 |
20100226339 | Stephenson et al. | Sep 2010 | A1 |
20100246785 | Wang | Sep 2010 | A1 |
20100285785 | Wang | Nov 2010 | A1 |
20100304724 | Lawler | Dec 2010 | A1 |
20100316199 | Martin, II | Dec 2010 | A1 |
20110044293 | Nagasawa | Feb 2011 | A1 |
20110103576 | Partington et al. | May 2011 | A1 |
20120014273 | Notton et al. | Jan 2012 | A1 |
20120115490 | Nicholson | May 2012 | A1 |
20120120914 | Sedlacek et al. | May 2012 | A1 |
20120140743 | Pelletier | Jun 2012 | A1 |
20120196644 | Scherzer et al. | Aug 2012 | A1 |
20120236868 | Yan | Sep 2012 | A1 |
20120282942 | Uusitalo | Nov 2012 | A1 |
20120296963 | Lu | Nov 2012 | A1 |
20120302223 | Austin | Nov 2012 | A1 |
20130007286 | Mehta et al. | Jan 2013 | A1 |
20130035138 | Abbott | Feb 2013 | A1 |
20130064106 | Sylvain | Mar 2013 | A1 |
20130067056 | Purkayastha et al. | Mar 2013 | A1 |
20130100887 | Kim | Apr 2013 | A1 |
20130196653 | Morrison | Aug 2013 | A1 |
20130196706 | Patel et al. | Aug 2013 | A1 |
20130331101 | Thomas et al. | Dec 2013 | A1 |
20140068314 | Kim | Mar 2014 | A1 |
20140070991 | Liu | Mar 2014 | A1 |
20140171084 | Chandler | Jun 2014 | A1 |
20140229888 | Ko | Aug 2014 | A1 |
20140254491 | Lindholm | Sep 2014 | A1 |
20140269495 | Frantz | Sep 2014 | A1 |
20140365945 | Karunamuni | Dec 2014 | A1 |
20150031417 | Lee | Jan 2015 | A1 |
20150038156 | Kilpatrick, II | Feb 2015 | A1 |
20150052466 | Chun | Feb 2015 | A1 |
20150065134 | Vandemoere et al. | Mar 2015 | A1 |
20150094120 | Suh | Apr 2015 | A1 |
20150127839 | Shipley | May 2015 | A1 |
Number | Date | Country |
---|---|---|
101656922 | Feb 2010 | CN |
1432219 | Jun 2004 | EP |
1519526 | Mar 2005 | EP |
1858270 | Nov 2007 | EP |
2009887 | Dec 2008 | EP |
2096843 | Sep 2009 | EP |
2112849 | Oct 2009 | EP |
2271171 | Jan 2011 | EP |
2002-262336 | Sep 2002 | JP |
0013454 | Mar 2000 | WO |
0211475 | Feb 2002 | WO |
2004057845 | Jul 2004 | WO |
2005055626 | Jun 2005 | WO |
2005101785 | Oct 2005 | WO |
2008110664 | Sep 2008 | WO |
2009040645 | Apr 2009 | WO |
2013025698 | Feb 2013 | WO |
Entry |
---|
Ryan Whitman, “A Google Engineer Explains Why KitKat Has White Status Bar Icons and Only Shows Connectivity in Quick Settings”, available at <http://www.androidpolice.com/2013/11/18/a-google-engineer-explains-why-kitkat-has-white-status-bar-icons-and-only-shows-connectivity-in-quick-settings/>, availabe on Nov. 18, 2013, 3 pages. |
Corey Gunther, “What's this icon? Galaxy S4 notification bar icons explained”, available on Jul. 9, 2013, available at <http://androidcommunity.com/whats-this-icon-galaxy-s4-notification-bar-icons-explained-20130709/>, 3 pages. |
designyourway.com, “User Interface Design Inspiration—45 Lovely Switches”, avaible at <http://www.designyourway.net/drb/user-interface-design-inspiration-45-lovely-switches>, archived on Jul. 20, 2013 at wayback machine <http://web.archive.org>, 16 pages. |
“International Search Report and Written Opinion Issued in PCT Application No. PCT/US2015/39310”, Mailed Date: Oct. 14, 2015, (10 Pages total). |
Bellavista, et al., “An IMS Vertical Handoff Solution to Dynamically Adapt Mobile Mulitmedia Services”, IEEE Symposium on Computers and Communications, Jul. 6, 2008, pp. 764-771, 8 pages. |
Achour et al., “Inter-Domain Mobility Management Solution for Service Continuity in IMS-Based Networks”, IEEE Consumer Communications and Networking Conference, Jan. 14, 2012, pp. 559-564, 6 pages. |
Whitwam, Ryan, “Republic Wireless Moto X Review: A Great Deal with Very Few Compromises”, Published on: Dec. 4, 2013, Available at: http://www.androidpolice.com/2013/12/03/republic-wireless-moto-x-review-a-great-deal-with-very-few-compromises/ (12 pages total). |
Perenson, Melissa, “Republic Wireless: Everything You Need to Know”, Published on: Aug. 28, 2013, Available at: http://blog.laptopmag.com/republic-wireless-faq (6 pages total). |
“ip4calls-iTelHybridDialer”, Published on: Jul. 17, 2013, Available at: https://play.google.com/store/apps/details?id=com.revesoft.hybriddialer.first—united—international—general—trading—ip4calls&hl=en (2 pages total). |
Whitwam, Ryan, “A Google Engineer Explains Why KitKat has White Status Bar Icons and Only Shows Connectivity in Quick Settings”, Published on: Nov. 18, 2013, Available at: http://www.androidpolice.com/2013/11/18/a-google-engineer-explains-why-kitkat-has-white-status-bar-icons-and-only-shows-connectivity-in-quick-settings/ (9 pages total). |
Ormond, et al., “Dynamic Network Selection in Wireless LAN/MAN Heterogeneous Networks”, In Proceedings of Mobile WiMAX: Towards Broadband Wireless Metropolitan Area Networks, Dec. 10, 2007, (60 pages total). |
Alkhwlani, et al., “Access Network Selection using Combined Fuzzy Control and MCDM in Heterogeneous Networks”, In Proceedings of International Conference on Computer Engineering & Systems, Nov. 27, 2007, (6 pages total). |
Porjazoski, et al., “Radio Access Technology Selection in Heterogeneous Wireless Networks Based on Service Type and User Mobility”, In Proceedings of 18th International Conference on Systems, Signals and Image Processing, Jun. 16, 2011, (4 pages total). |
Adamopoulou, et al., “Intelligent Access Network Selection in Heterogeneous Networks”, In 2nd International Symposium on Wireless Communication Systems, Sep. 7, 2005, (5 pages total). |
Alkhawlani, et al., “Hybrid Approach for Radio Network Selection in Heterogeneous Wireless Networks”, In International Journal of Advanced Science and Technology, vol. 44, Jul. 2012, (16 pages total). |
Cai, et al., “Dynamic and User-Centric Network Selection in Heterogeneous Networks”, In Proceedings of IEEE International Performance, Computing, and Communications Conference, Apr. 11, 2007, (7 pages total). |
Gharsellaoui, et al., “Optimizing Access Point Selection in Wireless Local Area Networks”, In Proceedings of International Conference on Communications and Information Technology, Mar. 29, 2011, (6 pages total). |
Jafry, et al., “Call Handoff Initiation in Hybrid Networks”, U.S. Appl. No. 14/144,668, filed Dec. 31, 2013. |
Calhan, et al., “An Adaptive Neuro-Fuzzy Based Vertical Handoff Decision Algorithm for Wireless Heterogeneous Networks”, In IEEE 21st International Symposium Personal Indoor and Mobile Radio Communications, Sep. 26, 2010, (6 pages total). |
Yan, et al., “A Survey of Vertical Handover Decision Algorithms in Fourth Generation Heterogeneous Wireless Networks”, In Computer Networks: The International Journal of Computer and Telecommunications Networking, vol. 54, Issue 11, Aug. 2010, (16 pages total). |
Liu, et al., “Performance Analysis and Optimization of Handoff Algorithms in Heterogeneous Wireless Networks”, In IEEE Transactions on Mobile Computing, vol. 7, Issue 7, Jul. 2008, (12 pages total). |
Wong, et al., “A Pattern Recognition System for Handoff Algorithms”, In IEEE Journal on Selected Areas in Communications, vol. 18, Issue 7, Jul. 2000, (12 pages total). |
Sidhu, et al., “Call Continuity”, U.S. Appl. No. 14/026,933, filed Sep. 13, 2013. |
Kalmanek, et al., “A Network-Based Architecture for Seamless Mobility Services”, In IEEE Communications Magazine, vol. 44, Issue 6, Jun. 2006 (7 pages total). |
Salkintzis, et al., “Voice Call Handover Mechanisms in Next-Generation 3GPP Systems”, In IEEE Communications Magazine, vol. 47, Issue 2, pp. 46-56, Feb. 2009 (11 pages total). |
Voice Call Flow Overview, 2007 Cisco Systems, Inc., pp. 1-14, Retrieved from: http://www.cisco.com/en/US/docs/ios/voice/monitor/configuration/guide/vt—callflow—ov.pdf, Retrieved on: Jun. 17, 2013 (14 pages total). |
J. Rosenberg, “Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols”, IETF Trust (Apr. 2010), Retrieved from: http://www.rfc-editor.org/rfc/rfc5245.txt, Retrieved on: Sep. 12, 2013 (110 pages total). |
M. Baugher, et al., “The Secure Real-time Transport Protocol (SRTP)”, The Internet Society (Mar. 2004), Retrieved from: http://www.rfc-editor.org/rfc/rfc3711.txt, Retrieved on: Sep. 12, 2013 (53 pages total). |
J. Rosenberg, et al., “SIP: Session Initiation Protocol”, The Internet Society (Jun. 2002), Retrieved from: http://www.rfc-editor.org/rfc/rfc3261.txt, Retrieved on: Sep. 12, 2013 (252 pages total). |
H. Schulzrinne, et al., “RTP: A Transport Protocol for Real-Time Applications”, The Internet Society (Jul. 2003), Retrieved from: http://www.rfc-editor.org/rfc/rfc3550.txt, Retrieved on: Sep. 12, 2013 (98 pages total). |
Bryan, et al., “SOSIMPLE: A SIP/SIMPLE Based P2P VoIP and IM System,” Computer Science Department, College a of William and Mary, Williamsburg, VA, Retrieved from: http://www.enseirb.fr/˜kadionik/sip/paper, Retrieved Date: Sep. 16, 2013 (6 pages total). |
Rauhala, J., “Universal SIP client for consumer devices,” Helsinki University of Technology, Department of Electrical Communications Engineering, Thesis submitted May 13, 2003, Retrieved from: http://scholar.google.com/url?sa=U&q=http://antoine.fressancourt.free.fr/exjobb/BX—Universal, Retrieved Date: Sep. 16, 2013 (64 pages total). |
Santos, et al., “Deployment of a Wireless Hybrid and Mobile Network for VoIP Services Based on Open Source Software,” Universidade Federal de Campina Grande, Retrieved From: http:/www.inf.int-evry.fr/˜olberger/wfs2006/danilo, Retrieved Date: Sep. 16, 2013 (20 pages total). |
“International Search Report and Written Opinion Received for PCT Patent Application No. PCT/US2014/068685”, Mailed Date: Feb. 11, 2015, 7 Pages. |
“International Search Report and Written Opinion Issued in PCT Patent Application No. PCT/US2015/020848”, Mailed Date: Jun. 9, 2015, (11 Pages total). |
“Route to Home”, Published on: Mar. 10, 2012, Available at: http://www.inovar.com/products/RouteToHome.html (1 page total). |
“Smart Call Routing”, Retrieved on: Dec. 31, 2013, Available at: http://www.roamware.com/downloads/datasheets/Smart%20Call%20Routing.pdf (2 pages total). |
“Roaming Call Optimizer”, Published on: Mar. 22, 2011, Available at: http://www.starhome.com/call-optimization.html (1 page total). |
“Optimal Call Routing”, Retrieved on: Dec. 31, 2013, Available at: http://www.bics.com/content/ocr (2 pages total). |
“Mobile Collaboration”, Retrieved on: Dec. 31, 2013, Available at: http://www.cisco.com/en/US/docs/voice—ip—comm/cucm/srnd/collab09/mobilapp.htmln (39 pages total). |
“International Search Report & Written Opinion Received for PCT Application No. PCT/US2015/023453”, Mailed Date: Jun. 22, 2015, (12 Pages total). |
“International Preliminary Report on Patentability Issued in PCT Application No. PCT/US2014/068685”, Mailed Date: Jun. 26, 2015, (6 Pages total). |
“International Search Report and Written Opinion Issued in PCT Application No. PCT/US2015/028679”, Mailed Date: Aug. 26, 2015, (11 Pages total). |
“International Preliminary Report on Patentability Issued in PCT Application No. PCT/US2014/054633”, Mailed Date: Aug. 21, 2015, 6 Pages total. |
“Second Written Opinion Issued in PCT Application No. PCT/US2015/020848”, Mailed Date : Mar. 30, 2016, (7 Pages total). |
“International Search Report and Written Opinion Issued in PCT Application No. PCT/US2015/056290”, Mailed Date: Feb. 1, 2016, (15 Pages total). |
“Second Written Opinion Issued in PCT Application No. PCT/US2015/023453”, Mailed Date: Mar. 1, 2016, 6 Pages. |
“International Preliminary Report on Patentability Issued in PCT Application No. PCT/US2015/39310”, Mailed Date: Jun. 2, 2016, (6 Pages total). |
International Preliminary Report on Patentability issued in PCT Application No. PCT/US2015/023453, mailed date: Jun. 17, 2016 (10 pages total). |
“International Preliminary Report on Patentability Issued in PCT Application No. PCT/US2015/020848”, Mailed Date: Jun. 28, 2016, 8 Pages. |
Number | Date | Country | |
---|---|---|---|
20150271317 A1 | Sep 2015 | US |