US20130036453A1 - System, method and user interface for network status reporting - Google Patents
System, method and user interface for network status reporting Download PDFInfo
- Publication number
- US20130036453A1 US20130036453A1 US13/647,276 US201213647276A US2013036453A1 US 20130036453 A1 US20130036453 A1 US 20130036453A1 US 201213647276 A US201213647276 A US 201213647276A US 2013036453 A1 US2013036453 A1 US 2013036453A1
- Authority
- US
- United States
- Prior art keywords
- state
- network
- authentication
- connection
- address
- 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.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
- H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/75—Indicating network or usage conditions on the user display
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
Definitions
- a fairly common problem when using a network is to experience a problem getting to a network resource because the computer did not obtain an IP address, or timed out getting an IP address and assigned an “automatic private IP address.”
- the status of the IP address is not used to determine whether the computer is “connected” when the system (as opposed to an application) reports connectivity.
- connectivity is determined by whether the interface (the network device) has “media” connected to it, which in wired-Ethernet terms means that a cable is plugged in, or in wireless terms means that the device has “associated” with the access point.
- a system, methods, and user interface for reporting the status of a network connection are provided.
- an icon is used to inform the user that the network connection is not connected, connecting, connected (routable IP address obtained), or in a warning state.
- the warning state indicates that a non-routable IP address (e.g. autonet address) has been obtained, which will likely be unsatisfactory to the user.
- a non-routable IP address e.g. autonet address
- One embodiment of the invention is directed at a method of informing the user of a network connection status.
- the method comprises attempting to join a network; detecting a state of the attempt; if the computer system is not connected to a network medium, determining the attempt to be in a first state; if the computer system has acquired a routable network address, determining the state of the attempt to be in a second state; if the computer system has acquired a non-routable network address, determining the state of the attempt to be in a third state; if the attempt is not in one of the first, second and third states, determining the state of the attempt to be in a fourth state; and informing the user of the state of the attempt.
- Attempting to join a network further comprises undergoing an authentication procedure, and if the authentication procedure fails, determining the state of the attempt to be in the third state.
- the first state is a disconnected state
- the second state is a connected state
- the third state is a warning state
- the fourth state is a connecting state.
- the network may be a wired network, wherein the computer system is connected to a network medium if a wired physical connection to the network is detected.
- the network may be a wireless network, wherein the computer system is connected to a network medium if the computer system has detected a wireless network.
- the network is a TCP/IP network and the network address is an IPv4 address.
- a user may be informed of the state by displaying an icon on a desktop of an operating system.
- the icon is different for each state.
- a detected change in the state of the attempt is reported to the user by changing the icon.
- the user interface includes a first icon that is displayed to signify that the network connection is in a first state, wherein the first state is a state of not being connected to a network medium; a second icon that is displayed to signify that the network connection is in a second state, wherein the second state is a state of having acquired a routable IP address; a third icon that is displayed to signify that the network connection is in a third state, wherein the third state is a state of having acquired a non-routable IP address; and a fourth icon that is displayed to signify that the network connection is in a fourth state, wherein the fourth state is a state of attempting to connecting to a network.
- the icon may be displayed in the notification area (sometimes referred to as the “system tray”). Clicking the icon launches a dialog box.
- FIG. 1A is a schematic generally illustrating an exemplary network environment across which reporting the status of a network connection operates.
- FIG. 1B is a block diagram generally illustrating an exemplary computer system for reporting the status of a network connection.
- FIG. 2 is a block diagram illustrating a network status checking system of reporting the status of a network connection.
- FIG. 3 is a diagram illustrating the segmentation of network connectivity, as performed reporting the status of a network connection.
- FIG. 4 is a flow diagram illustrating a method for detecting whether IP status checking is enabled, in accordance with reporting the status of a network connection.
- FIG. 5 is a flow diagram illustrating a method for determining whether a valid IP address was assigned, in accordance with reporting the status of a network connection.
- FIG. 6 is an overview flow diagram of a network status detecting method of reporting the status of a network connection.
- FIG. 7 is a detailed flow diagram of a network status detecting method of reporting the status of a network connection.
- FIG. 8 illustrates the icons associated with the network connectivity segmentation performed by reporting the status of a network connection.
- FIG. 9 is a diagram illustrating the segmentation of network connectivity as it pertains to the user interface of reporting the status of a network connection.
- FIG. 10 is a screen shot of a status dialog box of reporting the status of a network connection.
- FIG. 11 is a screen shot of a support dialog box of reporting the status of a network connection.
- FIG. 12 is a screen shot of an extended error dialog box of reporting the status of a network connection.
- reporting the status of a network connection is illustrated as being implemented in a suitable computing environment.
- the following description is based on embodiments of reporting the status of a network connection and should not be taken as limiting, with regard to alternative embodiments that are not explicitly described herein.
- the example network includes several computers 110 communicating with one another over a network 111 , represented by a cloud.
- Network 111 may include many well-known components, such as routers, gateways, hubs, etc. and allows the computers 110 to communicate via wired and/or wireless media.
- one or more of the computers may act as clients, network servers, or peers with respect to other computers. Accordingly, the various embodiments of the invention may be practiced on clients, network servers, peers, or combinations thereof, even though specific examples contained herein do not refer to all of these types of computers.
- FIG. 1B illustrates an example of a suitable computing system environment 100 on which the invention may be implemented.
- the computing system environment 100 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the computing environment 100 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary computing environment 100 .
- the invention is operational with numerous other general-purpose or special-purpose computing system environments or configurations.
- Examples of well known computing systems, environments, and configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
- the invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer.
- program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types.
- the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
- program modules may be located in both local and remote computer-storage media including memory-storage devices.
- an exemplary system for implementing the invention includes a general-purpose computing device in the form of a computer 110 , which may act as a client, network server, quarantine server, or peer within the context of the invention.
- Components of the computer 110 may include, but are not limited to, a processing unit 120 , a system memory 130 , and a system bus 121 that couples various system components including the system memory 130 to the processing unit 120 .
- the system bus 121 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
- such architectures include Industry Standard Architecture bus, Micro Channel Architecture bus, Enhanced ISA bus, Video Electronics Standards Associate local bus, and Peripheral Component Interconnect bus, also known as Mezzanine bus.
- the computer 110 typically includes a variety of computer-readable media.
- Computer-readable media can be any available media that can be accessed by the computer 110 and include both volatile and nonvolatile media, removable and non-removable media.
- Computer-readable media may include computer storage media.
- Computer storage media include both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for the storage of information such as computer-readable instructions, data structures, program modules, or other data.
- Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks or other optical disk 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 computer 110 .
- Communication media typically embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and include any information-delivery media.
- modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communication media include wired media such as a wired network or direct-wired connection and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of the any of the above should also be included within the scope of computer-readable media.
- the system memory 130 includes computer storage media in the form of volatile and nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132 .
- ROM read only memory
- RAM random access memory
- BIOS basic input/output system
- RAM 132 typically contains data and program modules that are immediately accessible to or presently being operated on by the processing unit 120 .
- FIG. 1B illustrates an operating system 134 , application programs 135 , other program modules 136 , and program data 137 .
- the computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media.
- FIG. 1B illustrates a hard disk drive 141 that reads from or writes to non-removable, nonvolatile, magnetic media, a magnetic disk drive 151 that reads from or writes to a removable, nonvolatile, magnetic disk 152 , and an optical disk drive 155 that reads from or writes to a removable, nonvolatile optical disk 156 such as a CD ROM or other optical media.
- removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary computing environment 100 include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like.
- the hard disk drive 141 is typically connected to the system bus 121 through a non-removable memory interface such as the interface 140
- the magnetic disk drive 151 and the optical disk drive 155 are typically connected to the system bus 121 by a removable memory interface, such as the interface 150 .
- the drives and their associated computer storage media discussed above and illustrated in FIG. 1B provide storage of computer-readable instructions, data structures, program modules, and other data for the computer 110 .
- the hard disk drive 141 is illustrated as storing an operating system 144 , application programs 145 , other program modules 146 , and program data 147 .
- these components can either be the same as or different from the operating system 134 , application programs 135 , other program modules 136 , and program data 137 .
- the operating system 144 , application programs 145 , other program modules 146 , and program data 147 are given different numbers to illustrate that, at a minimum, they are different copies.
- a user may enter commands and information into the computer 110 through input devices such as a keyboard 162 and a pointing device 161 , commonly referred to as a mouse, trackball, or touch pad.
- Other input devices may include a microphone, joystick, game pad, satellite dish, scanner, or the like.
- These and other input devices are often connected to the processing unit 120 through a user input interface 160 that is coupled to the system bus 121 , but may be connected by other interface and bus structures, such as a parallel port, game port, or a universal serial bus.
- a monitor 191 or other type of display device is also connected to the system bus 121 via an interface, such as a video interface 190 .
- the computer 110 may also include other peripheral output devices such as speakers 197 and a printer 196 which may be connected through an output peripheral interface 195 .
- the computer 110 operates in a networked environment using logical connections to one or more remote computers, such as a remote computer 180 .
- the remote computer 180 may be a 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 personal computer 110 although only a memory storage device 181 has been illustrated in FIG. 1B .
- the logical connections depicted in FIG. 1B include a local area network (LAN) 171 and a wide area network (WAN) 173 but may also include other networks.
- LAN 171 includes both wired and wireless connections.
- the personal computer 110 When used in a LAN networking environment, the personal computer 110 is connected to the LAN 171 through a network interface or adapter 170 .
- the computer 110 When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications over the WAN 173 , such as the Internet.
- the modem 172 which may be internal or external, may be connected to the system bus 121 via the user input interface 160 or other appropriate mechanism.
- program modules depicted relative to the personal computer 110 may be stored in the remote memory storage device 181 .
- FIG. 1B illustrates the remote application programs 185 as residing on the memory device 181 . It will be appreciated that the network connections shown are exemplary, and other means of establishing a communications link between the computers may be used.
- the invention relates to methods and user interfaces for reporting the status network connections to a user.
- the methods and user interfaces are included in a computer operating system (OS).
- OS computer operating system
- the invention is included in the Microsoft Windows XP OS.
- the invention is provided as a stand-alone utility that may be installed on top of an OS.
- FIG. 2 illustrates a system diagram of an embodiment of the invention.
- NUI Networking User Interface
- NCSU Network Connection State Utility
- the NCSU 220 detects the device-specific, authentication-specific, and IP-specific states for each installed network adapter.
- NCSU 220 uses the Microsoft Windows “SetupDi” call to enumerate the network adapters installed, and finds Ethernet network adapter 230 and wireless network adapter 240 . Both Ethernet network adapter 230 and wireless adapter 240 include a Network Driver Interface Specification (NDIS) miniport driver (not shown). NCSU 220 calls NDIS API 270 to detect the device-specific states of Ethernet network adapter 230 and wireless adapter 240 . NCSU 220 calls on an API provided by authentication client 250 to obtain the authentication-specific states. NCSU 220 calls on an API provided by the TCP/IP client 260 to obtain the IP-specific states.
- NDIS Network Driver Interface Specification
- the authentication client 250 is an 802.1x client and the TCP/IP client 260 is a Dynamic Host Control Protocol (DHCP) client.
- NCSU 220 can then determine an overall state of each network connection managed by the OS using the methods disclosed herein.
- DHCP Dynamic Host Control Protocol
- the network connectivity state segmentation is described with reference to FIG. 3 .
- the device-specific states include three states: disabled, network media disconnected, and enabled.
- the device state When a device (network adapter) is installed, but the driver is stopped, the device state is “Device State 0 : Disabled.”
- the device state When the device reports no media connection, the device state is “Device State 1 : Media Disconnected.” For wired network connections this state is reported as: “Network cable unplugged.” For wireless network connections, this state is reported as: “Not connected.”
- the device state is “Device State 2 : Enabled.”
- the authentication-specific states include validating identity, authenticating, authentication failed, and authentication successful. These states exist only when an authentication protocol is enabled for the connection, or, in the case of wireless, enabled for the specific network being to which the supplicant is connecting.
- the authentication protocol is the IEEE 802.1x protocol.
- An adapter must be in Device State 2 (Enabled) for these states to be used.
- the authentication state is “Authentication State 1 : Validating Identity.” While the authenticator is authenticating the credentials of the user/computer, the device state is “Authentication State 2 : Authenticating.” If the credentials are invalid or the authentication otherwise fails, the authentication state is “Authentication State 3 : Authentication Failed.” In the case of wireless networks, this state is short-lived because the authenticator will terminate the connection immediately. In the case of wired networks, this state is considered an error state. When the authenticator reports that authentication was successful, the authentication state is “Authentication State 4 : Authentication Successful.”
- the IP address-specific states include acquiring an IP address, invalid IP address assigned, and valid IP address assigned. These states exist only when IP Status Checking is enabled for an adapter.
- FIG. 4 illustrates a method of one embodiment of the invention for determining whether IP Status Checking is enabled for each network adapter.
- a network adapter For the IP-specific states to be used, a network adapter must be in Device State 2 (enabled) and either (a) have 802.1x disabled or (b) be in Authentication State 4 (authentication successful). If the network adapter is attempting to acquire an IP address, the IP-specific state is “IP State 1 : Attempting to acquire an IP address.” In an exemplary embodiment, the network adapter includes a DHCP client that is attempting to contact a DHCP server to get an IP address. When an IP address has been acquired, if the IP address is invalid then the IP-specific state is “IP State 2 : Invalid IP address assigned.” When an IP address has been acquired, if the IP address is valid then the IP-specific state is “IP State 3 : Valid IP Address Assigned.”
- IP address may be valid or invalid depending on the network configuration settings of the computer and the type of network to which the computer is connected. If DHCP is enabled on the computer, the network adapter is in IP State 3 : Valid IP Address Assigned if a routable network address has been assigned by the DHCP server. In an exemplary embodiment, the routable network address is an IPv4 address routable outside the subnet of that address. If a routable network address is not assigned, but an alternate static IP configuration is available, then the network adapter is also in IP State 3 .
- the network adapter is in IP State 2 : Invalid IP Address Assigned, unless the network connection is an ad-hoc wireless connection.
- the non-routable IP address is an IPv4 link-local address that is not routable outside the subnet of the address.
- the IPv4 link-local address is assigned by AutoNet in the Microsoft Windows OS, and is assigned to the 169.254.0.0 network. Though, if DHCP is not enabled, then any IP address is valid, routable or not, and the network adapter is in IP State 3 .
- FIG. 5 A method of an embodiment of the invention for determining whether an IP address is valid is illustrated in FIG. 5 .
- step 510 it is determined whether DHCP is enabled for the network adapter. If not, the IP address is valid. However if DHCP is enabled, it is determined whether a non-routable IP address has been assigned at step 520 . If not, then IP address is valid. But if so, it is determined whether the network connection is a wired connection at step 530 . If so, then the IP address is invalid. However if the connection is wireless, it is determined whether the network adapter is connected to a wireless Infrastructure-type network at step 540 . If so, then the IP address is invalid. Otherwise, the IP address is valid.
- FIG. 6 illustrates an overview of a method for determining the overall state of a network connection. This method is described in greater detail with reference to FIG. 7 .
- a network connection is initially presumed to be in the “Disabled” state until the NDIS driver for the connection reports whether network media are connected to the network adapter. No icon is shown in the system tray of the OS while in the “Disabled” state.
- a network medium is found if a physical connection to a network (for example, an Ethernet) is detected.
- a network medium is found if a wireless network adapter is able to associate with a wireless access point or another wireless device (in the case of ad-hoc networks). If a network medium is not found for the connection, the connection is considered to be in the “Not Connected” state, and the “Not Connected” icon is displayed in the system tray. If a network medium is found, the connection is considered to be in the “Connecting” state, and the “Connecting” icon is displayed in the system tray.
- step 720 it is determined whether 802.1x protocol is enabled for the connection. If not, the method proceeds to step 750 . If 802.1x protocol is enabled, the credentials of the user or machine are authenticated at step 730 . At step 740 , it is determined whether the authentication was successful. If the authentication failed, the connection is considered to be in the “Warning” state, and the “Warning” icon is displayed in the system tray. If authentication was successful, it is determined at step 750 whether IP Status Checking is enabled, as illustrated in FIG. 4 . If not, the connection is considered to be in the “Connected” state, and the “Connection” icon is displayed in the system tray. If IP status checking is enabled, an IP is acquired at step 760 .
- step 770 it is determined whether the assigned IP address is valid, as illustrated in FIG. 6 . If not, the connection is considered to be in a “Warning” state, and the “Warning” icon is displayed in the system tray. If the IP address is valid, then the connection is considered to be in the “Connected” state, and the “Connected” icon is displayed in the system tray.
- Another embodiment of the invention includes waiting for a predetermined time period before retrying to acquire an IP address, and delaying informing the user of a warning state until after retry is attempted.
- the DHCP client is constantly engaged in trying to contact a DHCP server during first connects, during lease renewals, on subnet changes, and so on. Much of this behavior is designed to be “behind the scenes” and does not need to be exposed to the user.
- the UI needs to interpret the DHCP client state in such a way that the (a) the user is aware what is going if it is relevant to their usage of the network and (b) they are told as quickly as possible what is going on.
- the state of the IP address may be 1) assigned an automatic private IP address (APIPA) (e.g. a non-routable IP address such as an auto net address), which is an address that has been assigned automatically due to a failure to contact a DHCP server; 2) assigned a non-APIPA, which is a routable IP address (e.g. an address that has been assigned by a DHCP server) or an alternate static configuration; or 3) no address configured (signified as an IPv4 address of 0.0.0.0).
- APIPA automatic private IP address
- the current state of the DHCP client with respect to whether or not is actively attempting to get an IP address or not can be of 1) Done, signifying that the client is not actively doing anything to attempt to change the current IP address (attempting to get a new address, for example); 2) Acquiring, signifying that the DHCP client is getting a new IP address; and 3) Renewing, signifying that the DHCP client is renewing the lease on an existing IP address.
- the combination of the current IP address state and the DHCP client state are enough to figure out what to show the user. For example, if the IP address is zero, and the status is “acquiring”—that means that the UI should show “acquiring”. However, if the IP address is zero, and the Status is “done”, that is considered a failure state.
- the DHCP client sometimes “sleeps” for varying periods of time and then wakes up and tries again. For example, if it fails to find a DHCP server, it will assign an APIPA address and then go to sleep for 2 seconds before trying again. Failing again, it will try again after 5 minutes. In some embodiments, there are delays of 10 seconds or 1 second between retry periods. In order to fulfill the goals of being both timely and relevant, the present invention is aware of these time periods in order to decide how to treat them.
- An embodiment of the invention accomplishes this by further providing an additional piece of information called RetryTime indicating to the UI how long the DHCP client intends to wait before trying again. Depending on how long this delay is, the UI may “gloss” over the wait period by staying in the acquiring state, or choose to indicate an error. Accordingly, spurious errors are not shown are not shown to the user. Thus, if the DHCP client has acquired an APIPA or zero IP address, an embodiment of the invention delays informing the user of the warning state until after the RetryTime has elapsed and the retry is unsuccessful. In one embodiment of the invention, the period for RetryTime is 2 seconds, though it will be appreciated by those skilled in the art that period could be chosen.
- FIG. 8 illustrates the notification area icons and which overall states they report to the user.
- An icon is shown for each state, and for each type of connection, wired or wireless.
- FIG. 9 further illustrates when these icons are displayed.
- Not Connected/Network Cable Unplugged Icon this icon is used when the device reports media disconnected.
- Connecting Icon this icon is displayed once the connection reaches the “Connecting” state, as shown in FIG. 7 , and is displayed until the connection enters another state. Notably, this icon is displayed while the authentication client prompts for credentials.
- Warning Icon this icon is displayed when authentication has failed or when an invalid IP address has been assigned.
- Connected Icon this icon is used when the connection reaches the “Connected” state, as shown in FIG. 7 .
- FIG. 9 further illustrates the status labels associate with each network connection as shown in the Network Connections folder of the OS, as well as the Wireless Networks UI.
- the balloon notifications of the UI of the invention are discussed with reference to FIG. 6 .
- the Connected Balloon appears with the Connected Icon. If the connection is wired then the balloon states that the named connection is connected. If the connection is wireless with no post-connection procedure enabled, then the balloon states that the named connection is connected, along with the name of the network and signal strength. Clicking on these balloons produces a status dialog box, discussed later. If the connection is wireless with a post-connection procedure enabled, then the balloon states that the named connection is connected, along with the name of the network, signal strength, and post-connection procedure text. Clicking on this balloon produces a post-connection procedure web page.
- the Warning Balloon is displayed along with the Warning Icon.
- the Warning Balloon states that the named connection is not connected due to an invalid IP address, and clicking on this balloon produces a Support section of status dialog box where the user can attempt to remedy the problem.
- connection When the connection reaches the “Not Connected” state, if the connection is a wired connection a balloon is displayed stating that the cable is unplugged. If the connection is a wireless connection, the displayed balloon depends upon whether there are visible networks, whether there are visible networks on that are on a list of preferred networks, and whether there are manual networks. If the device tried to connect to all the networks in range, but failed, there are no more networks to try (i.e. none of them are manual), and there is only one network in range, then the balloon states that the device was unable to connect to the found wireless network but it will keep trying to connect. Clicking on this balloon launches an extended error dialog. If the device tried to connect to all the networks in range, but failed, there are no more networks to try (i.e.
- VAN View Available Networks
- the balloon states that the device is unable to connect to a preferred wireless network but it will keep trying to connect.
- this balloon launches the VAN UI. If there are networks in range, but none of them are in the preferred list (but there are networks in the preferred list), then the balloon states that one or more wireless networks are in range of this computer. When clicked this balloon launches the VAN UI. If there are networks in range, and the preferred list is empty, then the balloon states that one or more wireless networks are in range of this computer. When clicked this balloon launches the VAN UI. If there are no visible wireless networks, then the balloon states that a wireless network is not available. When clicked this balloon opens the Network Connections folder.
- FIGS. 10 , 11 , and 12 illustrate the status dialog and extended error dialog boxes of the UI of the invention.
- the General tab of the status dialog box in FIG. 10 includes the overall network connection status for that connection, as well as the name of the network to which the connection is made.
- FIG. 11 illustrates the Support tab of the status dialog box, which gives the user the opportunity to explore the details of a “Not Connected” or “Warning” state connection, as well the opportunity to repair the problem.
- FIG. 12 illustrates the extended error dialog box that explains to the user in more detail the cause of failed connection where the failure was due to an invalid IP address, failed authentication, or failed association with a wireless network.
- FIG. 13 illustrates screenshots of a wireless UI comprised in the invention.
- the wireless UI displays each wireless connection along with the overall connection status and signal strength. If an invalid IP address was assigned, authentication failed, or association failed (connection failed), then the overall connection status indicates the failure and links to an extended error dialog box.
- Table 1 indicates the test use for various states in the Network Connections folder and the wireless UI.
- Wireless UI Manual, Automatic or On demand Enabled Folder: Standard connected tool-tip (media Enabled (name, speed, network and signal connected) Main Wireless UI: strength) Connected Auth- Credentials Validating identity Validating identity, + speed, specific required network and signal strength states Authenticating Attempting to authenticate Attempting to authenticate, + speed, network and signal strength Authentication Authentication did not succeed Authentication did not succeed, + failed speed, network and signal strength Authentication Connected Standard connected tool-tip success IP- Attempting to Acquiring network address Acquiring a network address, + specific acquire an IP speed, network and signal strength address address states Autonet IP Limited or no connectivity No public network address, + address speed, network and signal strength assigned IP address Connected Standard connected tool-tip assigned
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A method and user interface for informing a user of the status of a network connection are provided. Conventionally, the “connected” icon in the system tray only informs the user that the computer is linked to a network medium, such as an Ethernet or wireless access point. This icon does not indicate whether a routable IP address has been obtained. In this invention, an icon is used to inform the user that the network connection is disabled, connecting, connected (routable IP address obtained), or in a warning state. The warning state indicates that a non-routable IP address (e.g. auto net address) has been obtained, which will likely be unsatisfactory to the user. However, when connected to an 802.11 ad-hoc network, or when IP status checking is disabled, a non-routable IP address is deemed acceptable, and thus the “connected” icon is displayed.
Description
- This application is a continuation of and claims priority to U.S. patent application Ser. No. 11/067,016 filed Feb. 28, 2005, which claims priority to U.S. Provisional Application No. 60/592,526 filed Aug. 2, 2004. The disclosures of these applications are incorporated by reference herein in their entirety.
- A fairly common problem when using a network is to experience a problem getting to a network resource because the computer did not obtain an IP address, or timed out getting an IP address and assigned an “automatic private IP address.” Conventionally, the status of the IP address is not used to determine whether the computer is “connected” when the system (as opposed to an application) reports connectivity. Currently, connectivity is determined by whether the interface (the network device) has “media” connected to it, which in wired-Ethernet terms means that a cable is plugged in, or in wireless terms means that the device has “associated” with the access point. These are literally the first steps in a several step process leading to a state where a user can actually make use of the network. Despite this, as soon as the media connect state has been achieved, a user is informed that the computer is “Connected.”
- This mismatch between the system's notion of “connected” and the user's notion of “connected” is the cause of a number of problems. The difficulties include the fact that some IP addresses are better than others—an address assigned by a DHCP server is far more likely to allow access to the resources the user cares about that one assigned by the computer itself in the absence of a DHCP server (a non-routable IP address such as a link-local IPv4 address). However, the link-local address is itself not necessarily a “bad” thing. There are significant complexities that make it difficult to determine when a particular IP address is good or not. Accordingly, there is a need to provide more robust reporting of network connection states to a user.
- 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 to limit the scope of the claimed subject matter.
- A system, methods, and user interface for reporting the status of a network connection are provided. In an embodiment, an icon is used to inform the user that the network connection is not connected, connecting, connected (routable IP address obtained), or in a warning state. The warning state indicates that a non-routable IP address (e.g. autonet address) has been obtained, which will likely be unsatisfactory to the user. However, when connected to an 802.11 ad-hoc network, or when IP status checking is disabled (by the user or administrator), a non-routable IP address is deemed acceptable, and thus the “connected” icon is displayed.
- One embodiment of the invention is directed at a method of informing the user of a network connection status. The method comprises attempting to join a network; detecting a state of the attempt; if the computer system is not connected to a network medium, determining the attempt to be in a first state; if the computer system has acquired a routable network address, determining the state of the attempt to be in a second state; if the computer system has acquired a non-routable network address, determining the state of the attempt to be in a third state; if the attempt is not in one of the first, second and third states, determining the state of the attempt to be in a fourth state; and informing the user of the state of the attempt. Attempting to join a network further comprises undergoing an authentication procedure, and if the authentication procedure fails, determining the state of the attempt to be in the third state. In keeping with features of the invention, the first state is a disconnected state, the second state is a connected state, the third state is a warning state, and the fourth state is a connecting state.
- When the state of the attempt is in the warning state, one embodiment of the invention informs the user how to repair a problem causing the attempt to be in the warning start. The network may be a wired network, wherein the computer system is connected to a network medium if a wired physical connection to the network is detected. The network may be a wireless network, wherein the computer system is connected to a network medium if the computer system has detected a wireless network. In one embodiment, the network is a TCP/IP network and the network address is an IPv4 address. When one of IP status checking is disabled on the computer system, or the type of 802.11 network is determined to be an “ad-hoc” network, the state of the attempt is determined to be in the second state if the computer system is connected to a network medium.
- A user may be informed of the state by displaying an icon on a desktop of an operating system. The icon is different for each state. A detected change in the state of the attempt is reported to the user by changing the icon.
- Another embodiment of the invention is directed at a user interface for informing a user of a computer system of a status of a network connection. The user interface includes a first icon that is displayed to signify that the network connection is in a first state, wherein the first state is a state of not being connected to a network medium; a second icon that is displayed to signify that the network connection is in a second state, wherein the second state is a state of having acquired a routable IP address; a third icon that is displayed to signify that the network connection is in a third state, wherein the third state is a state of having acquired a non-routable IP address; and a fourth icon that is displayed to signify that the network connection is in a fourth state, wherein the fourth state is a state of attempting to connecting to a network. The icon may be displayed in the notification area (sometimes referred to as the “system tray”). Clicking the icon launches a dialog box.
- Additional features and advantages of the invention are made apparent from the following detailed description of illustrative embodiments that proceeds with reference to the accompanying figures.
- The accompanying drawings incorporated in and forming a part of the specification illustrate several aspects of the present invention, and together with the description serve to explain the principles of the invention. In the drawings:
-
FIG. 1A is a schematic generally illustrating an exemplary network environment across which reporting the status of a network connection operates. -
FIG. 1B is a block diagram generally illustrating an exemplary computer system for reporting the status of a network connection. -
FIG. 2 is a block diagram illustrating a network status checking system of reporting the status of a network connection. -
FIG. 3 is a diagram illustrating the segmentation of network connectivity, as performed reporting the status of a network connection. -
FIG. 4 is a flow diagram illustrating a method for detecting whether IP status checking is enabled, in accordance with reporting the status of a network connection. -
FIG. 5 is a flow diagram illustrating a method for determining whether a valid IP address was assigned, in accordance with reporting the status of a network connection. -
FIG. 6 is an overview flow diagram of a network status detecting method of reporting the status of a network connection. -
FIG. 7 is a detailed flow diagram of a network status detecting method of reporting the status of a network connection. -
FIG. 8 illustrates the icons associated with the network connectivity segmentation performed by reporting the status of a network connection. -
FIG. 9 is a diagram illustrating the segmentation of network connectivity as it pertains to the user interface of reporting the status of a network connection. -
FIG. 10 is a screen shot of a status dialog box of reporting the status of a network connection. -
FIG. 11 is a screen shot of a support dialog box of reporting the status of a network connection. -
FIG. 12 is a screen shot of an extended error dialog box of reporting the status of a network connection. - Turning to the drawings, wherein like reference numerals refer to like elements, reporting the status of a network connection is illustrated as being implemented in a suitable computing environment. The following description is based on embodiments of reporting the status of a network connection and should not be taken as limiting, with regard to alternative embodiments that are not explicitly described herein.
- In the description that follows, reporting the status of a network connection is described with reference to acts and symbolic representations of operations that are performed by one or more computing devices, unless indicated otherwise. As such, it will be understood that such acts and operations, which are at times referred to as being computer-executed, include the manipulation by the processing unit of the computing device of electrical signals representing data in a structured form. This manipulation transforms the data or maintains them at locations in the memory system of the computing device, which reconfigures or otherwise alters the operation of the device in a manner well understood by those skilled in the art. The data structures where data are maintained are physical locations of the memory that have particular properties defined by the format of the data. However, while the invention is being described in the foregoing context, it is not meant to be limiting as those of skill in the art will appreciate that the various acts and operations described hereinafter may also be implemented in hardware.
- An example of a networked environment in which the invention may be used will now be described with reference to
FIG. 1A . The example network includesseveral computers 110 communicating with one another over anetwork 111, represented by a cloud.Network 111 may include many well-known components, such as routers, gateways, hubs, etc. and allows thecomputers 110 to communicate via wired and/or wireless media. When interacting with one another over thenetwork 111, one or more of the computers may act as clients, network servers, or peers with respect to other computers. Accordingly, the various embodiments of the invention may be practiced on clients, network servers, peers, or combinations thereof, even though specific examples contained herein do not refer to all of these types of computers. -
FIG. 1B illustrates an example of a suitablecomputing system environment 100 on which the invention may be implemented. Thecomputing system environment 100 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should thecomputing environment 100 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in theexemplary computing environment 100. - The invention is operational with numerous other general-purpose or special-purpose computing system environments or configurations. Examples of well known computing systems, environments, and configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
- The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer-storage media including memory-storage devices.
- With reference to
FIG. 1B , an exemplary system for implementing the invention includes a general-purpose computing device in the form of acomputer 110, which may act as a client, network server, quarantine server, or peer within the context of the invention. Components of thecomputer 110 may include, but are not limited to, aprocessing unit 120, asystem memory 130, and asystem bus 121 that couples various system components including thesystem memory 130 to theprocessing unit 120. Thesystem bus 121 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture bus, Micro Channel Architecture bus, Enhanced ISA bus, Video Electronics Standards Associate local bus, and Peripheral Component Interconnect bus, also known as Mezzanine bus. - The
computer 110 typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by thecomputer 110 and include both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable media may include computer storage media. Computer storage media include both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for the storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks or other optical disk 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 thecomputer 110. Communication media typically embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and include any information-delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of the any of the above should also be included within the scope of computer-readable media. - The
system memory 130 includes computer storage media in the form of volatile and nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements within thecomputer 110, such as during start-up, is typically stored inROM 131.RAM 132 typically contains data and program modules that are immediately accessible to or presently being operated on by theprocessing unit 120. By way of example, and not limitation,FIG. 1B illustrates anoperating system 134, application programs 135,other program modules 136, andprogram data 137. - The
computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only,FIG. 1B illustrates ahard disk drive 141 that reads from or writes to non-removable, nonvolatile, magnetic media, amagnetic disk drive 151 that reads from or writes to a removable, nonvolatile,magnetic disk 152, and anoptical disk drive 155 that reads from or writes to a removable, nonvolatileoptical disk 156 such as a CD ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in theexemplary computing environment 100 include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. Thehard disk drive 141 is typically connected to thesystem bus 121 through a non-removable memory interface such as theinterface 140, and themagnetic disk drive 151 and theoptical disk drive 155 are typically connected to thesystem bus 121 by a removable memory interface, such as theinterface 150. - The drives and their associated computer storage media discussed above and illustrated in
FIG. 1B provide storage of computer-readable instructions, data structures, program modules, and other data for thecomputer 110. InFIG. 1B , for example, thehard disk drive 141 is illustrated as storing anoperating system 144,application programs 145,other program modules 146, andprogram data 147. Note that these components can either be the same as or different from theoperating system 134, application programs 135,other program modules 136, andprogram data 137. Theoperating system 144,application programs 145,other program modules 146, andprogram data 147 are given different numbers to illustrate that, at a minimum, they are different copies. - A user may enter commands and information into the
computer 110 through input devices such as akeyboard 162 and apointing device 161, commonly referred to as a mouse, trackball, or touch pad. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to theprocessing unit 120 through auser input interface 160 that is coupled to thesystem bus 121, but may be connected by other interface and bus structures, such as a parallel port, game port, or a universal serial bus. Amonitor 191 or other type of display device is also connected to thesystem bus 121 via an interface, such as avideo interface 190. In addition to themonitor 191, thecomputer 110 may also include other peripheral output devices such asspeakers 197 and aprinter 196 which may be connected through an outputperipheral interface 195. - The
computer 110 operates in a networked environment using logical connections to one or more remote computers, such as aremote computer 180. Theremote computer 180 may be a 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 thepersonal computer 110 although only amemory storage device 181 has been illustrated inFIG. 1B . The logical connections depicted inFIG. 1B include a local area network (LAN) 171 and a wide area network (WAN) 173 but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet. Furthermore,LAN 171 includes both wired and wireless connections. - When used in a LAN networking environment, the
personal computer 110 is connected to theLAN 171 through a network interface oradapter 170. When used in a WAN networking environment, thecomputer 110 typically includes amodem 172 or other means for establishing communications over theWAN 173, such as the Internet. Themodem 172, which may be internal or external, may be connected to thesystem bus 121 via theuser input interface 160 or other appropriate mechanism. In a networked environment, program modules depicted relative to thepersonal computer 110, or portions thereof, may be stored in the remotememory storage device 181. By way of example, and not limitation,FIG. 1B illustrates theremote application programs 185 as residing on thememory device 181. It will be appreciated that the network connections shown are exemplary, and other means of establishing a communications link between the computers may be used. - The invention relates to methods and user interfaces for reporting the status network connections to a user. In one embodiment of the invention, the methods and user interfaces are included in a computer operating system (OS). In an exemplary embodiment, the invention is included in the Microsoft Windows XP OS. In other embodiments, the invention is provided as a stand-alone utility that may be installed on top of an OS.
- Through the invention, the status of a network connection is segmented into device-specific states, authentication-specific states, and internet protocol (IP)-specific states. These states are then combined, in view of the computer's network settings configuration and the network properties, to determine an overall state that is reported to the user.
FIG. 2 illustrates a system diagram of an embodiment of the invention. A Networking User Interface (NUI) 210 reports the overall state of network connections to a user through notification area icons, pop-up balloons, and dialog boxes. The overall state of network connections is provided to theNUI 210 by the Network Connection State Utility (NCSU) 220. TheNCSU 220 detects the device-specific, authentication-specific, and IP-specific states for each installed network adapter. By way of example,NCSU 220 uses the Microsoft Windows “SetupDi” call to enumerate the network adapters installed, and findsEthernet network adapter 230 andwireless network adapter 240. BothEthernet network adapter 230 andwireless adapter 240 include a Network Driver Interface Specification (NDIS) miniport driver (not shown).NCSU 220 callsNDIS API 270 to detect the device-specific states ofEthernet network adapter 230 andwireless adapter 240.NCSU 220 calls on an API provided byauthentication client 250 to obtain the authentication-specific states.NCSU 220 calls on an API provided by the TCP/IP client 260 to obtain the IP-specific states. In an exemplary embodiment, theauthentication client 250 is an 802.1x client and the TCP/IP client 260 is a Dynamic Host Control Protocol (DHCP) client.NCSU 220 can then determine an overall state of each network connection managed by the OS using the methods disclosed herein. - The network connectivity state segmentation is described with reference to
FIG. 3 . The device-specific states include three states: disabled, network media disconnected, and enabled. When a device (network adapter) is installed, but the driver is stopped, the device state is “Device State 0: Disabled.” When the device reports no media connection, the device state is “Device State 1: Media Disconnected.” For wired network connections this state is reported as: “Network cable unplugged.” For wireless network connections, this state is reported as: “Not connected.” When a device reports a network media connection, the device state is “Device State 2: Enabled.” - The authentication-specific states include validating identity, authenticating, authentication failed, and authentication successful. These states exist only when an authentication protocol is enabled for the connection, or, in the case of wireless, enabled for the specific network being to which the supplicant is connecting. In one embodiment of the invention, the authentication protocol is the IEEE 802.1x protocol. An adapter must be in Device State 2 (Enabled) for these states to be used. When the authenticator is asking the user or computer for information, the authentication state is “Authentication State 1: Validating Identity.” While the authenticator is authenticating the credentials of the user/computer, the device state is “Authentication State 2: Authenticating.” If the credentials are invalid or the authentication otherwise fails, the authentication state is “Authentication State 3: Authentication Failed.” In the case of wireless networks, this state is short-lived because the authenticator will terminate the connection immediately. In the case of wired networks, this state is considered an error state. When the authenticator reports that authentication was successful, the authentication state is “Authentication State 4: Authentication Successful.”
- The IP address-specific states include acquiring an IP address, invalid IP address assigned, and valid IP address assigned. These states exist only when IP Status Checking is enabled for an adapter.
FIG. 4 illustrates a method of one embodiment of the invention for determining whether IP Status Checking is enabled for each network adapter. Atstep 410, it is determined whether a group policy is present. If so, it is determined whether the group policy blocks the IP status checking feature for the user or machine atstep 420. If so, then IP Status Checking is not enabled. Otherwise, if no group policy is present, or if the group policy does not block IP Status Checking, then it is determined whether IP Status Checking has been manually disabled by the user through the Network UI atstep 430. If so, then IP Status Checking is not enabled. Otherwise, it is determined whether that TCP/IP is installed and bound for the network adapter atstep 440. If so, IP Status Checking is enabled. Otherwise, IP Status Checking is not enabled. - For the IP-specific states to be used, a network adapter must be in Device State 2 (enabled) and either (a) have 802.1x disabled or (b) be in Authentication State 4 (authentication successful). If the network adapter is attempting to acquire an IP address, the IP-specific state is “IP State 1: Attempting to acquire an IP address.” In an exemplary embodiment, the network adapter includes a DHCP client that is attempting to contact a DHCP server to get an IP address. When an IP address has been acquired, if the IP address is invalid then the IP-specific state is “IP State 2: Invalid IP address assigned.” When an IP address has been acquired, if the IP address is valid then the IP-specific state is “IP State 3: Valid IP Address Assigned.”
- An IP address may be valid or invalid depending on the network configuration settings of the computer and the type of network to which the computer is connected. If DHCP is enabled on the computer, the network adapter is in IP State 3: Valid IP Address Assigned if a routable network address has been assigned by the DHCP server. In an exemplary embodiment, the routable network address is an IPv4 address routable outside the subnet of that address. If a routable network address is not assigned, but an alternate static IP configuration is available, then the network adapter is also in IP State 3. However, if a non-routable network address is assigned, and no alternate static IP configuration exists, then the network adapter is in IP State 2: Invalid IP Address Assigned, unless the network connection is an ad-hoc wireless connection. In an exemplary embodiment, the non-routable IP address is an IPv4 link-local address that is not routable outside the subnet of the address. In an exemplary embodiment of the invention, the IPv4 link-local address is assigned by AutoNet in the Microsoft Windows OS, and is assigned to the 169.254.0.0 network. Though, if DHCP is not enabled, then any IP address is valid, routable or not, and the network adapter is in IP State 3.
- A method of an embodiment of the invention for determining whether an IP address is valid is illustrated in
FIG. 5 . Atstep 510, it is determined whether DHCP is enabled for the network adapter. If not, the IP address is valid. However if DHCP is enabled, it is determined whether a non-routable IP address has been assigned atstep 520. If not, then IP address is valid. But if so, it is determined whether the network connection is a wired connection atstep 530. If so, then the IP address is invalid. However if the connection is wireless, it is determined whether the network adapter is connected to a wireless Infrastructure-type network atstep 540. If so, then the IP address is invalid. Otherwise, the IP address is valid. -
FIG. 6 illustrates an overview of a method for determining the overall state of a network connection. This method is described in greater detail with reference toFIG. 7 . A network connection is initially presumed to be in the “Disabled” state until the NDIS driver for the connection reports whether network media are connected to the network adapter. No icon is shown in the system tray of the OS while in the “Disabled” state. Thus, atstep 710, it is determined whether network media have been found. In the case of a wired network connection, a network medium is found if a physical connection to a network (for example, an Ethernet) is detected. In the case of a wireless network, a network medium is found if a wireless network adapter is able to associate with a wireless access point or another wireless device (in the case of ad-hoc networks). If a network medium is not found for the connection, the connection is considered to be in the “Not Connected” state, and the “Not Connected” icon is displayed in the system tray. If a network medium is found, the connection is considered to be in the “Connecting” state, and the “Connecting” icon is displayed in the system tray. - At
step 720, it is determined whether 802.1x protocol is enabled for the connection. If not, the method proceeds to step 750. If 802.1x protocol is enabled, the credentials of the user or machine are authenticated atstep 730. Atstep 740, it is determined whether the authentication was successful. If the authentication failed, the connection is considered to be in the “Warning” state, and the “Warning” icon is displayed in the system tray. If authentication was successful, it is determined atstep 750 whether IP Status Checking is enabled, as illustrated inFIG. 4 . If not, the connection is considered to be in the “Connected” state, and the “Connection” icon is displayed in the system tray. If IP status checking is enabled, an IP is acquired atstep 760. Atstep 770, it is determined whether the assigned IP address is valid, as illustrated inFIG. 6 . If not, the connection is considered to be in a “Warning” state, and the “Warning” icon is displayed in the system tray. If the IP address is valid, then the connection is considered to be in the “Connected” state, and the “Connected” icon is displayed in the system tray. - Another embodiment of the invention includes waiting for a predetermined time period before retrying to acquire an IP address, and delaying informing the user of a warning state until after retry is attempted. The DHCP client is constantly engaged in trying to contact a DHCP server during first connects, during lease renewals, on subnet changes, and so on. Much of this behavior is designed to be “behind the scenes” and does not need to be exposed to the user. The UI needs to interpret the DHCP client state in such a way that the (a) the user is aware what is going if it is relevant to their usage of the network and (b) they are told as quickly as possible what is going on.
- In this embodiment, three pieces of information are made available to the UI by the DHCP client. That information includes the state of the currently assigned IP address, the current state of the DHCP client, and a RetryTime. The state of the IP address may be 1) assigned an automatic private IP address (APIPA) (e.g. a non-routable IP address such as an auto net address), which is an address that has been assigned automatically due to a failure to contact a DHCP server; 2) assigned a non-APIPA, which is a routable IP address (e.g. an address that has been assigned by a DHCP server) or an alternate static configuration; or 3) no address configured (signified as an IPv4 address of 0.0.0.0).
- The current state of the DHCP client, with respect to whether or not is actively attempting to get an IP address or not can be of 1) Done, signifying that the client is not actively doing anything to attempt to change the current IP address (attempting to get a new address, for example); 2) Acquiring, signifying that the DHCP client is getting a new IP address; and 3) Renewing, signifying that the DHCP client is renewing the lease on an existing IP address.
- Typically, the combination of the current IP address state and the DHCP client state are enough to figure out what to show the user. For example, if the IP address is zero, and the status is “acquiring”—that means that the UI should show “acquiring”. However, if the IP address is zero, and the Status is “done”, that is considered a failure state. In one embodiment of the invention, the DHCP client sometimes “sleeps” for varying periods of time and then wakes up and tries again. For example, if it fails to find a DHCP server, it will assign an APIPA address and then go to sleep for 2 seconds before trying again. Failing again, it will try again after 5 minutes. In some embodiments, there are delays of 10 seconds or 1 second between retry periods. In order to fulfill the goals of being both timely and relevant, the present invention is aware of these time periods in order to decide how to treat them.
- An embodiment of the invention accomplishes this by further providing an additional piece of information called RetryTime indicating to the UI how long the DHCP client intends to wait before trying again. Depending on how long this delay is, the UI may “gloss” over the wait period by staying in the acquiring state, or choose to indicate an error. Accordingly, spurious errors are not shown are not shown to the user. Thus, if the DHCP client has acquired an APIPA or zero IP address, an embodiment of the invention delays informing the user of the warning state until after the RetryTime has elapsed and the retry is unsuccessful. In one embodiment of the invention, the period for RetryTime is 2 seconds, though it will be appreciated by those skilled in the art that period could be chosen.
- A UI of an embodiment of the invention will now be described in greater detail.
FIG. 8 illustrates the notification area icons and which overall states they report to the user. An icon is shown for each state, and for each type of connection, wired or wireless.FIG. 9 further illustrates when these icons are displayed. Not Connected/Network Cable Unplugged Icon: this icon is used when the device reports media disconnected. Connecting Icon: this icon is displayed once the connection reaches the “Connecting” state, as shown inFIG. 7 , and is displayed until the connection enters another state. Notably, this icon is displayed while the authentication client prompts for credentials. Warning Icon: this icon is displayed when authentication has failed or when an invalid IP address has been assigned. Connected Icon: this icon is used when the connection reaches the “Connected” state, as shown inFIG. 7 . -
FIG. 9 further illustrates the status labels associate with each network connection as shown in the Network Connections folder of the OS, as well as the Wireless Networks UI. - The balloon notifications of the UI of the invention are discussed with reference to
FIG. 6 . Once the connection reaches the “Connected” state, the Connected Balloon appears with the Connected Icon. If the connection is wired then the balloon states that the named connection is connected. If the connection is wireless with no post-connection procedure enabled, then the balloon states that the named connection is connected, along with the name of the network and signal strength. Clicking on these balloons produces a status dialog box, discussed later. If the connection is wireless with a post-connection procedure enabled, then the balloon states that the named connection is connected, along with the name of the network, signal strength, and post-connection procedure text. Clicking on this balloon produces a post-connection procedure web page. However, once the connection reaches the “Warning” state due to an invalid IP address, the Warning Balloon is displayed along with the Warning Icon. The Warning Balloon states that the named connection is not connected due to an invalid IP address, and clicking on this balloon produces a Support section of status dialog box where the user can attempt to remedy the problem. - When the connection reaches the “Not Connected” state, if the connection is a wired connection a balloon is displayed stating that the cable is unplugged. If the connection is a wireless connection, the displayed balloon depends upon whether there are visible networks, whether there are visible networks on that are on a list of preferred networks, and whether there are manual networks. If the device tried to connect to all the networks in range, but failed, there are no more networks to try (i.e. none of them are manual), and there is only one network in range, then the balloon states that the device was unable to connect to the found wireless network but it will keep trying to connect. Clicking on this balloon launches an extended error dialog. If the device tried to connect to all the networks in range, but failed, there are no more networks to try (i.e. none of them are manual), and there is more than one network in range, then the balloon states that the device was unable to connect to a wireless network and that the device could not connect to any of the preferred wireless networks but it will keep trying to connect. When clicked this balloon launches the View Available Networks (VAN) UI.
- If the device tried to connect to all the networks that it could, but failed, there are more networks to try (but they aren't in the preferred list), and none of them are manual, then the balloon states that the device is unable to connect to a preferred wireless network but it will keep trying to connect. When clicked this balloon launches the VAN UI. If there are networks in range, but none of them are in the preferred list (but there are networks in the preferred list), then the balloon states that one or more wireless networks are in range of this computer. When clicked this balloon launches the VAN UI. If there are networks in range, and the preferred list is empty, then the balloon states that one or more wireless networks are in range of this computer. When clicked this balloon launches the VAN UI. If there are no visible wireless networks, then the balloon states that a wireless network is not available. When clicked this balloon opens the Network Connections folder.
-
FIGS. 10 , 11, and 12 illustrate the status dialog and extended error dialog boxes of the UI of the invention. The General tab of the status dialog box inFIG. 10 includes the overall network connection status for that connection, as well as the name of the network to which the connection is made.FIG. 11 illustrates the Support tab of the status dialog box, which gives the user the opportunity to explore the details of a “Not Connected” or “Warning” state connection, as well the opportunity to repair the problem.FIG. 12 illustrates the extended error dialog box that explains to the user in more detail the cause of failed connection where the failure was due to an invalid IP address, failed authentication, or failed association with a wireless network. -
FIG. 13 illustrates screenshots of a wireless UI comprised in the invention. The wireless UI displays each wireless connection along with the overall connection status and signal strength. If an invalid IP address was assigned, authentication failed, or association failed (connection failed), then the overall connection status indicates the failure and links to an extended error dialog box. - Table 1 indicates the test use for various states in the Network Connections folder and the wireless UI.
-
TABLE 1 State name Status in folder & in Wireless UI Icon Tooltip Device- Disabled Folder: N/A specific Disabled states Main Wireless UI: N/A Enabled - Folder/Wired: Wired: Network cable unplugged. Media Network cable unplugged. Wireless: Not connected. Right- disconnected Folder/Wireless: click here for more options. Not connected Wireless UI: Manual, Automatic or On demand Enabled Folder: Standard connected tool-tip (media Enabled (name, speed, network and signal connected) Main Wireless UI: strength) Connected Auth- Credentials Validating identity Validating identity, + speed, specific required network and signal strength states Authenticating Attempting to authenticate Attempting to authenticate, + speed, network and signal strength Authentication Authentication did not succeed Authentication did not succeed, + failed speed, network and signal strength Authentication Connected Standard connected tool-tip success IP- Attempting to Acquiring network address Acquiring a network address, + specific acquire an IP speed, network and signal strength address address states Autonet IP Limited or no connectivity No public network address, + address speed, network and signal strength assigned IP address Connected Standard connected tool-tip assigned - The foregoing description of various embodiments of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise embodiments disclosed. Numerous modifications or variations are possible in light of the above teachings. The embodiments discussed were chosen and described to provide the best illustration of the principles of the invention and its practical application to thereby enable one of ordinary skill in the art to utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. All such modifications and variations are within the scope of the invention as determined by the appended claims when interpreted in accordance with the breadth to which they are fairly, legally, and equitably entitled.
Claims (20)
1. A method comprising:
initiating a connection attempt to form a network connection between a computing device and a communications network;
ascertaining a device-specific state, an authentication-specific state, and an internet protocol (IP)-specific state for the connection attempt; and
reporting an overall state of the connection attempt that combines the device-specific state, the authentication-specific state, and the IP-specific state.
2. A method as recited in claim 1 , wherein ascertaining the device-specific state for the connection attempt comprises making a call to an application programming interface (API) configured to detect the device-specific state from a network adapter that is being used by the computing device to connect to the communications network.
3. A method as recited in claim 1 , wherein ascertaining the authentication-specific state for the connection attempt comprises making a call to an API that corresponds to an authentication client to obtain the authentication-specific state, the authentication client configured to authenticate the network connection.
4. A method as recited in claim 1 , wherein ascertaining the IP-specific state for the connection attempt comprises making a call to an API that corresponds to a TCP/IP client to obtain the IP-specific state, the TCP/IP client configured to assign an IP-address for the network connection.
5. A method as recited in claim 1 , wherein the device-specific state for the connection attempt comprises one of:
a disabled state, which indicates that a network adapter being used by the computing device to connect to the communications network is installed, but a driver corresponding to the network adaptor is stopped;
a network media disconnected state, which indicates that a network cable is unplugged if the network connection is a wired connection and that the network adaptor has not formed an association with a wireless device that corresponds to the communications network if the network connection is a wireless connection; and
an enabled state, which indicates that an association is formed between the network adaptor and the communications network.
6. A method as recited in claim 1 , wherein the authentication-specific state for the connection attempt comprises one of:
a validating identity state, which indicates that an authenticator is gathering credentials to authenticate the computing device for connection to the communications network;
an authenticating state, which indicates that the authenticator is authenticating the gathered credentials;
an authentication failed state, which indicates that the authenticator determines the gathered credentials to be invalid or that said authenticating failed; and
an authentication successful state, which indicates that the authenticator determines the computing device to be authenticated.
7. A method as recited in claim 6 , wherein the validating identity state, the authenticating state, the authentication failed state, and the authentication successful state are useable for the authentication-specific state when an authentication protocol is enabled for the connection attempt and when a network adapter being used by the computing device to connect to the communications network is connected to the communications network.
8. A method as recited in claim 1 , wherein the IP-specific state for the connection attempt comprises one of:
an acquiring an IP address state, which indicates that a network adapter being used by the computing device to connect to the communications network is attempting to acquire an IP address;
an invalid IP address assigned state, which indicates that an acquired IP address is invalid; and
a valid IP address state, which indicates that the acquired IP address is valid.
9. A method as recited in claim 1 , wherein ascertaining the IP-specific state includes determining whether IP Status Checking is enabled for a network adapter being used by the computing device to connect to the communications network.
10. A method as recited in claim 1 , wherein reporting the overall state of the connection attempt comprises causing a user interface to display at least one of a notification area icon, a pop-up balloon, and a dialog box.
11. A method as recited in claim 1 , further comprising detecting a change in at least one of the device-specific state, the authentication-specific state, and the IP-specific state that causes the overall state of the connection attempt to change, and reporting the change of the overall state.
12. A method as recited in claim 1 , wherein the computing device comprises multiple network adapters configured to connect to the communications network, and the attempting, ascertaining, and reporting are performed for each of the multiple network adapters.
13. One or more computer-readable media comprising computer-executable instructions that, when executed, cause one or more processing devices to:
attempt to form a network connection with a communications network;
ascertain device-specific, authentication-specific, and internet protocol (IP)-specific states that correspond to the attempt;
determine an overall state of the attempt based on a combination of the ascertained states; and
display a graphical user interface to indicate the overall state of the attempt.
14. One or more computer-readable media as recited in claim 13 , wherein the device-specific, authentication-specific, and IP-specific states are ascertained by making calls to one or more application programming interfaces (APIs).
15. One or more computer-readable media as recited in claim 13 , wherein the computer-executable instructions further cause the one or more processing devices to withhold an indication that a procedure associated with forming the network connection is initially unsuccessful.
16. One or more computer-readable media as recited in claim 13 , wherein the computer-executable instructions further cause the one or more processing devices to delay indicating that acquiring a valid IP address, performed in association with forming the network connection, is unsuccessful until at least two attempts to acquire the valid IP address are performed.
17. One or more computer-readable media as recited in claim 13 , wherein the computer-executable instructions further cause the one or more computing devices to detect a change in at least one of the device-specific, the authentication-specific, and the IP-specific states that causes the overall state of the attempt to change, and update the graphical user interface to indicate the change to the overall state.
18. A system comprising:
one or more processors;
a networking user interface, operable via the one or more processors, that is configured to report overall states for attempts to form a network connection between a computing device and a communications network; and
a network connection state utility (NCSU), operable via the one or more processors, that is configured to detect a device-specific state, an authentication-specific state, and an IP-specific state for each of the attempts, and determine the overall states for the attempts by combining the device-specific state, the authentication-specific state, and the IP-specific state for each of the attempts.
19. A system as recited in claim 18 , wherein the NCSU is configured to detect the device-specific state, the authentication-specific state, and the IP-specific state for each of multiple network adapters used by the computing device to connect to the communications network.
20. A system as recited in claim 18 , wherein the NCSU is further configured to make one or more application programming interface (API) calls to detect the device-specific state, the authentication-specific state, and the IP-specific state.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/647,276 US20130036453A1 (en) | 2004-08-02 | 2012-10-08 | System, method and user interface for network status reporting |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US59252604P | 2004-08-02 | 2004-08-02 | |
US11/067,016 US8285855B2 (en) | 2004-08-02 | 2005-02-28 | System, method and user interface for network status reporting |
US13/647,276 US20130036453A1 (en) | 2004-08-02 | 2012-10-08 | System, method and user interface for network status reporting |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/067,016 Continuation US8285855B2 (en) | 2004-08-02 | 2005-02-28 | System, method and user interface for network status reporting |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130036453A1 true US20130036453A1 (en) | 2013-02-07 |
Family
ID=35733693
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/067,016 Active 2027-12-17 US8285855B2 (en) | 2004-08-02 | 2005-02-28 | System, method and user interface for network status reporting |
US13/647,276 Abandoned US20130036453A1 (en) | 2004-08-02 | 2012-10-08 | System, method and user interface for network status reporting |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/067,016 Active 2027-12-17 US8285855B2 (en) | 2004-08-02 | 2005-02-28 | System, method and user interface for network status reporting |
Country Status (1)
Country | Link |
---|---|
US (2) | US8285855B2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100040059A1 (en) * | 2006-05-03 | 2010-02-18 | Trapeze Networks, Inc. | System and method for restricting network access using forwarding databases |
US10404827B2 (en) * | 2016-06-22 | 2019-09-03 | Cisco Technology, Inc. | Client network information service |
US10992523B2 (en) * | 2017-05-01 | 2021-04-27 | Canon Kabushiki Kaisha | Information processing apparatus, peripheral apparatus, control method thereof, storage medium, and system |
US11474767B1 (en) * | 2014-05-28 | 2022-10-18 | Amazon Technologies, Inc. | Print from web services platform to local printer |
Families Citing this family (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8285855B2 (en) | 2004-08-02 | 2012-10-09 | Microsoft Corporation | System, method and user interface for network status reporting |
US7385935B2 (en) * | 2004-12-17 | 2008-06-10 | Alpha Networks Inc | IP address parameter setting method of remote network apparatus |
DE602005015366D1 (en) * | 2005-03-29 | 2009-08-20 | Research In Motion Ltd | METHOD AND DEVICES FOR USE IN THE MANUFACTURING OF MEETING INTRODUCTION PROTOCOL TRANSMISSIONS FOR VIRTUAL PRIVATE NETWORKING |
US7631270B2 (en) * | 2005-09-16 | 2009-12-08 | Microsoft Corporation | Network connectivity and wireless status in a notification area |
US9319967B2 (en) * | 2006-05-15 | 2016-04-19 | Boingo Wireless, Inc. | Network access point detection and use |
US8504100B2 (en) * | 2006-05-23 | 2013-08-06 | Connectsoft, Inc. | System and method for multi-radio control |
KR20080006770A (en) * | 2006-07-13 | 2008-01-17 | 삼성전자주식회사 | Method and apparatus for transmitting and receiving of link condition |
US8767686B2 (en) * | 2006-07-25 | 2014-07-01 | Boingo Wireless, Inc. | Method and apparatus for monitoring wireless network access |
US8196188B2 (en) * | 2006-09-06 | 2012-06-05 | Devicescape Software, Inc. | Systems and methods for providing network credentials |
US8194589B2 (en) * | 2006-09-06 | 2012-06-05 | Devicescape Software, Inc. | Systems and methods for wireless network selection based on attributes stored in a network database |
US8554830B2 (en) * | 2006-09-06 | 2013-10-08 | Devicescape Software, Inc. | Systems and methods for wireless network selection |
US8549588B2 (en) * | 2006-09-06 | 2013-10-01 | Devicescape Software, Inc. | Systems and methods for obtaining network access |
US9326138B2 (en) * | 2006-09-06 | 2016-04-26 | Devicescape Software, Inc. | Systems and methods for determining location over a network |
US8191124B2 (en) * | 2006-09-06 | 2012-05-29 | Devicescape Software, Inc. | Systems and methods for acquiring network credentials |
US8667596B2 (en) | 2006-09-06 | 2014-03-04 | Devicescape Software, Inc. | Systems and methods for network curation |
US8743778B2 (en) * | 2006-09-06 | 2014-06-03 | Devicescape Software, Inc. | Systems and methods for obtaining network credentials |
US8243611B2 (en) * | 2006-12-04 | 2012-08-14 | International Business Machines Corporation | Method and system for configuring a device that has failed to obtain network address |
US8948046B2 (en) * | 2007-04-27 | 2015-02-03 | Aerohive Networks, Inc. | Routing method and system for a wireless network |
CN101304363B (en) * | 2007-05-12 | 2011-12-07 | 华为技术有限公司 | Method for managing conversation connection as well as apparatus and system |
US20090055517A1 (en) * | 2007-08-21 | 2009-02-26 | D-Link Corporation | Method for a plug-and-play network device to acquire dual internet protocol addresses |
US8209719B2 (en) * | 2007-08-29 | 2012-06-26 | At&T Intellectual Property I, Lp | System for presenting status information associated with a media content processor |
US20090063978A1 (en) * | 2007-09-05 | 2009-03-05 | Sony Corporation | Network status icon in navigable toolbar |
US8218502B1 (en) | 2008-05-14 | 2012-07-10 | Aerohive Networks | Predictive and nomadic roaming of wireless clients across different network subnets |
JP4334602B1 (en) * | 2008-06-17 | 2009-09-30 | 任天堂株式会社 | Information processing apparatus, information processing system, and information processing program |
US8972893B2 (en) | 2008-06-27 | 2015-03-03 | Microsoft Technology Licensing, Llc | Notification area that persistently rearranges elements |
US20100073160A1 (en) * | 2008-09-25 | 2010-03-25 | Microsoft Corporation | Alerting users using a multiple state status icon |
US20100263022A1 (en) * | 2008-10-13 | 2010-10-14 | Devicescape Software, Inc. | Systems and Methods for Enhanced Smartclient Support |
EP2340477B1 (en) * | 2008-10-13 | 2014-08-06 | Devicescape Software, INC. | Systems and methods for identifying a network |
US9674892B1 (en) | 2008-11-04 | 2017-06-06 | Aerohive Networks, Inc. | Exclusive preshared key authentication |
US8483194B1 (en) | 2009-01-21 | 2013-07-09 | Aerohive Networks, Inc. | Airtime-based scheduling |
US11115857B2 (en) | 2009-07-10 | 2021-09-07 | Extreme Networks, Inc. | Bandwidth sentinel |
US9900251B1 (en) | 2009-07-10 | 2018-02-20 | Aerohive Networks, Inc. | Bandwidth sentinel |
CN101640923A (en) * | 2009-08-20 | 2010-02-03 | 深圳华为通信技术有限公司 | Method and device for acquiring network configuration information |
US8671187B1 (en) | 2010-07-27 | 2014-03-11 | Aerohive Networks, Inc. | Client-independent network supervision application |
US9002277B2 (en) | 2010-09-07 | 2015-04-07 | Aerohive Networks, Inc. | Distributed channel selection for wireless networks |
US10091065B1 (en) | 2011-10-31 | 2018-10-02 | Aerohive Networks, Inc. | Zero configuration networking on a subnetted network |
KR101863197B1 (en) | 2012-01-31 | 2018-05-31 | 삼성전자주식회사 | Apparatus and method for informing of available devices in contents sharing network |
CN104769864B (en) | 2012-06-14 | 2018-05-04 | 艾诺威网络有限公司 | It is multicasted to unicast conversion technology |
US9413772B2 (en) | 2013-03-15 | 2016-08-09 | Aerohive Networks, Inc. | Managing rogue devices through a network backhaul |
US9948626B2 (en) | 2013-03-15 | 2018-04-17 | Aerohive Networks, Inc. | Split authentication network systems and methods |
US10389650B2 (en) | 2013-03-15 | 2019-08-20 | Aerohive Networks, Inc. | Building and maintaining a network |
US9690676B2 (en) | 2013-03-15 | 2017-06-27 | Aerohive Networks, Inc. | Assigning network device subnets to perform network activities using network device information |
US9628395B1 (en) * | 2013-06-05 | 2017-04-18 | X Development Llc | Interfaces for service requests in a balloon network |
US9152782B2 (en) | 2013-12-13 | 2015-10-06 | Aerohive Networks, Inc. | Systems and methods for user-based network onboarding |
CN104080086B (en) * | 2014-07-18 | 2018-09-04 | 北京智谷睿拓技术服务有限公司 | Wireless connecting establishment method and wireless connection establish device |
CN106612189B (en) * | 2015-10-22 | 2019-11-22 | 鸿富锦精密电子(天津)有限公司 | Computer techno-stress property setting method |
US11909719B1 (en) * | 2021-11-24 | 2024-02-20 | Amazon Technologies, Inc. | Managing the allocations and assignments of internet protocol (IP) addresses for computing resource networks |
Citations (33)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5261044A (en) * | 1990-09-17 | 1993-11-09 | Cabletron Systems, Inc. | Network management system using multifunction icons for information display |
US5295244A (en) * | 1990-09-17 | 1994-03-15 | Cabletron Systems, Inc. | Network management system using interconnected hierarchies to represent different network dimensions in multiple display views |
US5301348A (en) * | 1989-03-20 | 1994-04-05 | International Business Machines Corporation | Dynamic progress marking icon |
US5436909A (en) * | 1990-09-17 | 1995-07-25 | Cabletron Systems, Inc. | Network management system using status suppression to isolate network faults |
US5559955A (en) * | 1990-09-17 | 1996-09-24 | Cabletron Systems, Inc. | Method and apparatus for monitoring the status of non-pollable device in a computer network |
US5630081A (en) * | 1995-09-07 | 1997-05-13 | Puma Technology, Inc. | Connection resource manager displaying link-status information using a traffic light iconic representation |
US5751933A (en) * | 1990-09-17 | 1998-05-12 | Dev; Roger H. | System for determining the status of an entity in a computer network |
US6112015A (en) * | 1996-12-06 | 2000-08-29 | Northern Telecom Limited | Network management graphical user interface |
US6211858B1 (en) * | 1997-09-26 | 2001-04-03 | Ericsson Inc. | Method and apparatus for displaying a rotating meter icon on a portable intelligent communications device |
US20010035881A1 (en) * | 2000-04-06 | 2001-11-01 | Microsoft Corporation | Method and system for reducing notification area clutter |
US20020051017A1 (en) * | 2000-07-13 | 2002-05-02 | Clayton Wishoff | Notification device for a graphical user environment |
US20020140725A1 (en) * | 1999-03-26 | 2002-10-03 | Hitoshi Horii | Status display unit using icons and method therefor |
US20030061322A1 (en) * | 1997-02-03 | 2003-03-27 | Toshiaki Igarashi | Network data base control device and method thereof |
US20030135593A1 (en) * | 2001-09-26 | 2003-07-17 | Bernard Lee | Management system |
US20040039827A1 (en) * | 2001-11-02 | 2004-02-26 | Neoteris, Inc. | Method and system for providing secure access to private networks with client redirection |
US20040049586A1 (en) * | 2002-09-11 | 2004-03-11 | Wholepoint Corporation | Security apparatus and method for local area networks |
US6718378B1 (en) * | 1999-04-30 | 2004-04-06 | Canon Kabushiki Kaisha | Device management information processing apparatus method and storage medium |
US20040119756A1 (en) * | 2002-12-18 | 2004-06-24 | International Business Machines Corporation | Apparatus and method for dynamically building a context sensitive composite icon |
US20040153530A1 (en) * | 1999-04-30 | 2004-08-05 | Canon Kabushiki Kaisha | Data processing apparatus, data processing method, and storage medium storing computer-readable program |
US20040204133A1 (en) * | 2002-11-12 | 2004-10-14 | Microsoft Corporation | Connectivity notification displaying path to connection |
US20040255192A1 (en) * | 2003-01-30 | 2004-12-16 | Hiroyuki Watanabe | Information processing apparatus and network connection diagnostic method used in the same apparatus |
US20050055641A1 (en) * | 1999-04-30 | 2005-03-10 | Canon Kabushiki Kaisha | Data processing apparatus, data processing method, and storage medium storing computer-readable program |
US20050198583A1 (en) * | 2000-02-25 | 2005-09-08 | Martinez Jesus A. | State/activity indication using icons on an LCD |
US20060059265A1 (en) * | 2002-08-27 | 2006-03-16 | Seppo Keronen | Terminal connectivity system |
US20070067734A1 (en) * | 2005-09-16 | 2007-03-22 | Microsoft Corporation | Network connectivity and wireless status in a notification area |
US20080046973A1 (en) * | 2003-08-28 | 2008-02-21 | Jens-Christian Jorgensen | Preventing Unauthorized Access of Computer Network Resources |
US20090063978A1 (en) * | 2007-09-05 | 2009-03-05 | Sony Corporation | Network status icon in navigable toolbar |
US20100315994A1 (en) * | 2007-01-10 | 2010-12-16 | Smart Technologies Ulc | Participant response system with facilitated communications bandwidth |
US20100325610A1 (en) * | 2009-06-23 | 2010-12-23 | Canon Kabushiki Kaisha | Connection information generation method and information processing apparatus |
US20110078605A1 (en) * | 2009-09-29 | 2011-03-31 | Charles Griep | Method and apparatus for displaying a monitored state with no explicit connection |
US8195245B2 (en) * | 2009-05-11 | 2012-06-05 | Compal Electronics, Inc. | Method and user interface apparatus for managing functions of wireless communication components |
US20140194089A1 (en) * | 2013-01-10 | 2014-07-10 | Samsung Electronics Co., Ltd. | Method of displaying icons according to service usage states and mobile terminal supporting the same |
US20140344475A1 (en) * | 2013-05-15 | 2014-11-20 | Media Tek Inc. | Enhanced dhcp method |
Family Cites Families (64)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4953159A (en) * | 1989-01-03 | 1990-08-28 | American Telephone And Telegraph Company | Audiographics conferencing arrangement |
JP2938104B2 (en) * | 1989-11-08 | 1999-08-23 | 株式会社日立製作所 | Shared resource management method and information processing system |
JP3160017B2 (en) * | 1991-08-28 | 2001-04-23 | 株式会社日立製作所 | Network management display device |
US6456306B1 (en) * | 1995-06-08 | 2002-09-24 | Nortel Networks Limited | Method and apparatus for displaying health status of network devices |
JP3734051B2 (en) * | 1995-09-28 | 2006-01-11 | 日立ソフトウエアエンジニアリング株式会社 | Network management system |
US5758070A (en) * | 1995-10-06 | 1998-05-26 | Canon Kabushiki Kaisha | System for dynamically determining a network media type of a LAN using frame type identifying value from a configuration table |
US5751965A (en) * | 1996-03-21 | 1998-05-12 | Cabletron System, Inc. | Network connection status monitor and display |
US5764913A (en) * | 1996-04-05 | 1998-06-09 | Microsoft Corporation | Computer network status monitoring system |
US5794206A (en) * | 1996-05-06 | 1998-08-11 | Sterling Commerce, Inc. | Method and system for displaying electronic data interchanges in a computer |
US6337699B1 (en) * | 1996-06-27 | 2002-01-08 | Sun Microsystems, Inc. | Visualizing degrees of information object attributes |
US6040834A (en) * | 1996-12-31 | 2000-03-21 | Cisco Technology, Inc. | Customizable user interface for network navigation and management |
US6182225B1 (en) * | 1997-02-03 | 2001-01-30 | Canon Kabushiki Kaisha | Network data base control device and method thereof |
US6563914B2 (en) * | 1997-02-26 | 2003-05-13 | Call Sciences Limited | Personal web-based teleconferencing method and system |
JP3832937B2 (en) * | 1997-08-26 | 2006-10-11 | キヤノン株式会社 | Control device |
US5987430A (en) * | 1997-08-28 | 1999-11-16 | Atcom, Inc. | Communications network connection system and method |
US5847981A (en) * | 1997-09-04 | 1998-12-08 | Motorola, Inc. | Multiply and accumulate circuit |
US6125369A (en) * | 1997-10-02 | 2000-09-26 | Microsoft Corporation | Continuous object sychronization between object stores on different computers |
US6628965B1 (en) * | 1997-10-22 | 2003-09-30 | Dynamic Mobile Data Systems, Inc. | Computer method and system for management and control of wireless devices |
FI108477B (en) * | 1998-02-27 | 2002-01-31 | Nokia Corp | Method for creating an icon |
US6157965A (en) * | 1998-02-27 | 2000-12-05 | Intel Corporation | System and method for binding a virtual device driver to a network driver interface |
US6353614B1 (en) * | 1998-03-05 | 2002-03-05 | 3Com Corporation | Method and protocol for distributed network address translation |
US6836483B1 (en) * | 1998-06-24 | 2004-12-28 | Research Investment Network, Inc. | Message system for asynchronous transfer |
US6738809B1 (en) * | 1998-08-21 | 2004-05-18 | Nortel Networks Limited | Network presence indicator for communications management |
US6229538B1 (en) * | 1998-09-11 | 2001-05-08 | Compaq Computer Corporation | Port-centric graphic representations of network controllers |
US20030158932A1 (en) * | 1998-10-02 | 2003-08-21 | Haruo Machida | System for displaying connection condition of device provided on network |
JP4497580B2 (en) * | 1999-04-30 | 2010-07-07 | キヤノン株式会社 | Data processing apparatus, data processing method, and storage medium storing computer-readable program |
US6463468B1 (en) * | 1999-06-01 | 2002-10-08 | Netzero, Inc. | Targeted network video download interface |
GB2350983B (en) * | 1999-06-10 | 2001-10-03 | 3Com Corp | Network problem indication |
US7693042B1 (en) * | 1999-06-23 | 2010-04-06 | At&T Mobility Ii Llc | Intelligent presentation network management system |
US6463457B1 (en) * | 1999-08-26 | 2002-10-08 | Parabon Computation, Inc. | System and method for the establishment and the utilization of networked idle computational processing power |
US7123608B1 (en) * | 1999-09-10 | 2006-10-17 | Array Telecom Corporation | Method, system, and computer program product for managing database servers and service |
JP4428844B2 (en) * | 1999-10-01 | 2010-03-10 | キヤノン株式会社 | Information processing apparatus, data processing method, and recording medium |
JP2001175576A (en) * | 1999-10-04 | 2001-06-29 | Canon Inc | Device, system and method for processing information, and storage medium |
US6600499B1 (en) * | 2000-04-13 | 2003-07-29 | International Business Machines Corp. | Method and system for displaying status of critical indicators on diverse display devices and indicating changes in status |
US7051087B1 (en) * | 2000-06-05 | 2006-05-23 | Microsoft Corporation | System and method for automatic detection and configuration of network parameters |
US6546263B1 (en) * | 2000-06-12 | 2003-04-08 | Ericsson Inc. | Apparatus and method for compact icon display |
US7278103B1 (en) * | 2000-06-28 | 2007-10-02 | Microsoft Corporation | User interface to display and manage an entity and associated resources |
US7089335B2 (en) * | 2000-10-30 | 2006-08-08 | Microsoft Corporation | Bridging multiple network segments and exposing the multiple network segments as a single network to a higher level networking software on a bridging computing device |
US6957390B2 (en) * | 2000-11-30 | 2005-10-18 | Mediacom.Net, Llc | Method and apparatus for providing dynamic information to a user via a visual display |
JP2002183202A (en) * | 2000-12-18 | 2002-06-28 | Nec Corp | Terminal device, and system and method for collecting information |
US7120129B2 (en) * | 2001-03-13 | 2006-10-10 | Microsoft Corporation | System and method for achieving zero-configuration wireless computing and computing device incorporating same |
US7197561B1 (en) * | 2001-03-28 | 2007-03-27 | Shoregroup, Inc. | Method and apparatus for maintaining the status of objects in computer networks using virtual state machines |
JP2003110564A (en) * | 2001-09-28 | 2003-04-11 | Toshiba Corp | Information processor and network setting method |
US20030069954A1 (en) * | 2001-10-05 | 2003-04-10 | Adc Telecommunications, Inc. | Subnet pooling |
US7483984B1 (en) * | 2001-12-19 | 2009-01-27 | Boingo Wireless, Inc. | Method and apparatus for accessing networks by a mobile device |
US20030232598A1 (en) * | 2002-06-13 | 2003-12-18 | Daniel Aljadeff | Method and apparatus for intrusion management in a wireless network using physical location determination |
US7721216B2 (en) * | 2002-06-18 | 2010-05-18 | Microsoft Corporation | Visual group interface for group connectivity |
TW591398B (en) * | 2002-09-26 | 2004-06-11 | Tatung Co | Method of implementing a plurality of system tray areas |
US7287252B2 (en) * | 2002-09-27 | 2007-10-23 | The United States Of America Represented By The Secretary Of The Navy | Universal client and consumer |
US20050050196A1 (en) * | 2003-08-25 | 2005-03-03 | Lucent Technologies Inc. | Method and apparatus for managing and graphically representing elements in a network |
JP3891167B2 (en) * | 2003-10-24 | 2007-03-14 | ブラザー工業株式会社 | Network device management system, network device management device, and network device management program |
US20050132360A1 (en) * | 2003-12-11 | 2005-06-16 | Chu Simon C. | Network boot sequence in the absence of a DHCP server |
JP2005191833A (en) * | 2003-12-25 | 2005-07-14 | Fujitsu Ltd | Display method of call termination histories of a plurality of kinds |
US7876775B2 (en) * | 2004-02-12 | 2011-01-25 | At&T Intellectual Property I, L.P. | Connection management for data networks |
JP4540377B2 (en) * | 2004-03-25 | 2010-09-08 | パナソニック株式会社 | UI display device and UI display method |
EP1738251A2 (en) * | 2004-04-16 | 2007-01-03 | Cascade Basic Research Corp. | Modelling relationships within an on-line connectivity universe |
US7761607B2 (en) * | 2004-04-23 | 2010-07-20 | Microsoft Corporation | User based communication mode selection on a device capable of carrying out network communications |
US8285855B2 (en) | 2004-08-02 | 2012-10-09 | Microsoft Corporation | System, method and user interface for network status reporting |
US20060168530A1 (en) * | 2005-01-21 | 2006-07-27 | International Business Machines Corporation | Task weaver |
JP2006270863A (en) * | 2005-03-25 | 2006-10-05 | Toshiba Corp | Network compatible device and ip address setting method |
US20080134046A1 (en) * | 2006-12-05 | 2008-06-05 | Microsoft Corporation | Aggregated computer health |
US20090055517A1 (en) * | 2007-08-21 | 2009-02-26 | D-Link Corporation | Method for a plug-and-play network device to acquire dual internet protocol addresses |
US20100125663A1 (en) * | 2008-11-17 | 2010-05-20 | Donovan John J | Systems, methods, and devices for detecting security vulnerabilities in ip networks |
US7954010B2 (en) * | 2008-12-12 | 2011-05-31 | At&T Intellectual Property I, L.P. | Methods and apparatus to detect an error condition in a communication network |
-
2005
- 2005-02-28 US US11/067,016 patent/US8285855B2/en active Active
-
2012
- 2012-10-08 US US13/647,276 patent/US20130036453A1/en not_active Abandoned
Patent Citations (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5301348A (en) * | 1989-03-20 | 1994-04-05 | International Business Machines Corporation | Dynamic progress marking icon |
US5812750A (en) * | 1990-09-17 | 1998-09-22 | Cabletron Systems, Inc. | Method and apparatus for monitoring the status of non-pollable devices in a computer network |
US6049828A (en) * | 1990-09-17 | 2000-04-11 | Cabletron Systems, Inc. | Method and apparatus for monitoring the status of non-pollable devices in a computer network |
US5436909A (en) * | 1990-09-17 | 1995-07-25 | Cabletron Systems, Inc. | Network management system using status suppression to isolate network faults |
US5504921A (en) * | 1990-09-17 | 1996-04-02 | Cabletron Systems, Inc. | Network management system using model-based intelligence |
US5559955A (en) * | 1990-09-17 | 1996-09-24 | Cabletron Systems, Inc. | Method and apparatus for monitoring the status of non-pollable device in a computer network |
US6374293B1 (en) * | 1990-09-17 | 2002-04-16 | Aprisma Management Technologies, Inc. | Network management system using model-based intelligence |
US5295244A (en) * | 1990-09-17 | 1994-03-15 | Cabletron Systems, Inc. | Network management system using interconnected hierarchies to represent different network dimensions in multiple display views |
US5261044A (en) * | 1990-09-17 | 1993-11-09 | Cabletron Systems, Inc. | Network management system using multifunction icons for information display |
US5751933A (en) * | 1990-09-17 | 1998-05-12 | Dev; Roger H. | System for determining the status of an entity in a computer network |
US5630081A (en) * | 1995-09-07 | 1997-05-13 | Puma Technology, Inc. | Connection resource manager displaying link-status information using a traffic light iconic representation |
US6112015A (en) * | 1996-12-06 | 2000-08-29 | Northern Telecom Limited | Network management graphical user interface |
US20030061322A1 (en) * | 1997-02-03 | 2003-03-27 | Toshiaki Igarashi | Network data base control device and method thereof |
US6211858B1 (en) * | 1997-09-26 | 2001-04-03 | Ericsson Inc. | Method and apparatus for displaying a rotating meter icon on a portable intelligent communications device |
US6496209B2 (en) * | 1999-03-26 | 2002-12-17 | Mitsubishi Denki Kabushiki Kaisha | Status display unit using icons and method therefor |
US20020140725A1 (en) * | 1999-03-26 | 2002-10-03 | Hitoshi Horii | Status display unit using icons and method therefor |
US20040205169A1 (en) * | 1999-04-30 | 2004-10-14 | Canon Kabushiki Kaisha | Data processing apparatus, data processing method, and storage medium storing computer-readable program |
US20050055641A1 (en) * | 1999-04-30 | 2005-03-10 | Canon Kabushiki Kaisha | Data processing apparatus, data processing method, and storage medium storing computer-readable program |
US7593983B2 (en) * | 1999-04-30 | 2009-09-22 | Canon Kabushiki Kaisha | Data processing apparatus, data processing method, and storage medium storing computer-readable program |
US7412498B2 (en) * | 1999-04-30 | 2008-08-12 | Canon Kabushiki Kaisha | Data processing apparatus, data processing method, and storage medium storing computer-readable program |
US8019853B2 (en) * | 1999-04-30 | 2011-09-13 | Canon Kabushiki Kaisha | Data processing apparatus, data processing method, and storage medium storing computer-readable program |
US6718378B1 (en) * | 1999-04-30 | 2004-04-06 | Canon Kabushiki Kaisha | Device management information processing apparatus method and storage medium |
US20040153530A1 (en) * | 1999-04-30 | 2004-08-05 | Canon Kabushiki Kaisha | Data processing apparatus, data processing method, and storage medium storing computer-readable program |
US20050198583A1 (en) * | 2000-02-25 | 2005-09-08 | Martinez Jesus A. | State/activity indication using icons on an LCD |
US7249326B2 (en) * | 2000-04-06 | 2007-07-24 | Microsoft Corporation | Method and system for reducing notification area clutter |
US20010035881A1 (en) * | 2000-04-06 | 2001-11-01 | Microsoft Corporation | Method and system for reducing notification area clutter |
US20020051017A1 (en) * | 2000-07-13 | 2002-05-02 | Clayton Wishoff | Notification device for a graphical user environment |
US20030135593A1 (en) * | 2001-09-26 | 2003-07-17 | Bernard Lee | Management system |
US7631084B2 (en) * | 2001-11-02 | 2009-12-08 | Juniper Networks, Inc. | Method and system for providing secure access to private networks with client redirection |
US7958245B2 (en) * | 2001-11-02 | 2011-06-07 | Juniper Networks, Inc. | Method and system for providing secure access to private networks with client redirection |
US20100057845A1 (en) * | 2001-11-02 | 2010-03-04 | Juniper Networks, Inc. | Method and system for providing secure access to private networks with client redirection |
US20040039827A1 (en) * | 2001-11-02 | 2004-02-26 | Neoteris, Inc. | Method and system for providing secure access to private networks with client redirection |
US20110208838A1 (en) * | 2001-11-02 | 2011-08-25 | Juniper Networks, Inc. | Method and system for providing secure access to private networks with client redirection |
US20060059265A1 (en) * | 2002-08-27 | 2006-03-16 | Seppo Keronen | Terminal connectivity system |
US20040049586A1 (en) * | 2002-09-11 | 2004-03-11 | Wholepoint Corporation | Security apparatus and method for local area networks |
US20040204133A1 (en) * | 2002-11-12 | 2004-10-14 | Microsoft Corporation | Connectivity notification displaying path to connection |
US7369850B2 (en) * | 2002-11-12 | 2008-05-06 | Microsoft Corporation | Connectivity notification displaying path to connection |
US20040119756A1 (en) * | 2002-12-18 | 2004-06-24 | International Business Machines Corporation | Apparatus and method for dynamically building a context sensitive composite icon |
US7231611B2 (en) * | 2002-12-18 | 2007-06-12 | International Business Machines Corporation | Apparatus and method for dynamically building a context sensitive composite icon |
US20040255192A1 (en) * | 2003-01-30 | 2004-12-16 | Hiroyuki Watanabe | Information processing apparatus and network connection diagnostic method used in the same apparatus |
US20080046973A1 (en) * | 2003-08-28 | 2008-02-21 | Jens-Christian Jorgensen | Preventing Unauthorized Access of Computer Network Resources |
US7631270B2 (en) * | 2005-09-16 | 2009-12-08 | Microsoft Corporation | Network connectivity and wireless status in a notification area |
US20070067734A1 (en) * | 2005-09-16 | 2007-03-22 | Microsoft Corporation | Network connectivity and wireless status in a notification area |
US20100315994A1 (en) * | 2007-01-10 | 2010-12-16 | Smart Technologies Ulc | Participant response system with facilitated communications bandwidth |
US20090063978A1 (en) * | 2007-09-05 | 2009-03-05 | Sony Corporation | Network status icon in navigable toolbar |
US8195245B2 (en) * | 2009-05-11 | 2012-06-05 | Compal Electronics, Inc. | Method and user interface apparatus for managing functions of wireless communication components |
US20100325610A1 (en) * | 2009-06-23 | 2010-12-23 | Canon Kabushiki Kaisha | Connection information generation method and information processing apparatus |
US8495563B2 (en) * | 2009-06-23 | 2013-07-23 | Canon Kabushiki Kaisha | Connection information generation method and information processing apparatus |
US20110078605A1 (en) * | 2009-09-29 | 2011-03-31 | Charles Griep | Method and apparatus for displaying a monitored state with no explicit connection |
US20140194089A1 (en) * | 2013-01-10 | 2014-07-10 | Samsung Electronics Co., Ltd. | Method of displaying icons according to service usage states and mobile terminal supporting the same |
US20140344475A1 (en) * | 2013-05-15 | 2014-11-20 | Media Tek Inc. | Enhanced dhcp method |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100040059A1 (en) * | 2006-05-03 | 2010-02-18 | Trapeze Networks, Inc. | System and method for restricting network access using forwarding databases |
US8964747B2 (en) * | 2006-05-03 | 2015-02-24 | Trapeze Networks, Inc. | System and method for restricting network access using forwarding databases |
US11474767B1 (en) * | 2014-05-28 | 2022-10-18 | Amazon Technologies, Inc. | Print from web services platform to local printer |
US10404827B2 (en) * | 2016-06-22 | 2019-09-03 | Cisco Technology, Inc. | Client network information service |
US10911567B2 (en) * | 2016-06-22 | 2021-02-02 | Cisco Technology, Inc. | Client network information service |
US10992523B2 (en) * | 2017-05-01 | 2021-04-27 | Canon Kabushiki Kaisha | Information processing apparatus, peripheral apparatus, control method thereof, storage medium, and system |
Also Published As
Publication number | Publication date |
---|---|
US8285855B2 (en) | 2012-10-09 |
US20060026289A1 (en) | 2006-02-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8285855B2 (en) | System, method and user interface for network status reporting | |
US7418486B2 (en) | Automatic discovery and configuration of external network devices | |
US7814531B2 (en) | Detection of network environment for network access control | |
US8447865B2 (en) | Optimal source interface selection | |
JP4647096B2 (en) | Method and system for configuring a computer to connect to a network using a network connection object | |
US7881231B2 (en) | Detection of home network configuration problems | |
US20070111568A1 (en) | Network device setup utility | |
US7734738B2 (en) | Automatic configuration of client and server networking | |
WO2021088254A1 (en) | Dual-stack access method, apparatus and device for user-mode network file system | |
US8775623B2 (en) | Automatic port conflict resolution during application deployment | |
US20150271130A1 (en) | Systems and methods for provisioning, configuring, diagnosing, and maintaining out-of-band management of computing devices | |
KR20080027266A (en) | Efficient formation of ad hoc networks | |
US10841154B1 (en) | Systems and methods for network discovery for zero configuration based-clustered systems | |
US10200239B2 (en) | Normalized management network | |
US20070130468A1 (en) | Network connection identification | |
JP2011044955A (en) | Setting change method by network manager equipment and program, control method and program of network equipment, network manager equipment, and network equipment | |
EP2294868B1 (en) | Seamless location aware network connectivity | |
CN107911494B (en) | Method, device, computer equipment and storage medium for accessing IPv6 network | |
US10841163B2 (en) | Autoinitialization of clustered storage | |
US7209481B2 (en) | System and method for automated network address cloning for routers | |
US7590762B2 (en) | API for network discovery | |
CN114285668B (en) | Gate testing method and device, storage medium and electronic equipment | |
Cisco | Release Notes for Cisco Aironet Access Points and 350 Series Bridges | |
US8271623B2 (en) | Performing configuration in a multimachine environment | |
JP5706289B2 (en) | COMMUNICATION DEVICE, COMMUNICATION METHOD, AND PROGRAM |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034544/0541 Effective date: 20141014 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |