Method and apparatus to limit wireless connectivity roaming of multi-function devices

A method for limiting wireless connectivity roaming of a multi-function device (MFD) is disclosed. For example, the method is executed by a processor and includes failing to re-authenticate on a current access point of a wireless network, accessing a list of access points within a user defined boundary, selecting an access point in the list of access points based on a parameter of the access point, and establishing a wireless communication path with the access point.

The present disclosure relates generally to multi-function devices (MFDs) and relates more particularly to limiting wireless connectivity roaming of MFDs in a wireless network.

BACKGROUND

Multi-function devices (MFDs) can be used to perform a variety of different functions. For example, MFDs can be used to copy documents, print documents, fax documents, and the like. Typically, a user may have a computing device that is communicatively coupled to the MFD. The user may create an image to be printed on the computing device and may send the image data to the MFD to be printed.

MFDs are rarely powered off and on. Rather, the MFDs typically have efficient power saving modes where the MFDs may enter a sleep mode when not in use. However, over time, the wireless connections of the MFDs may gradually roam to different access points. In some instances, the wireless connections of the MFDs may roam to access points that do not provide a very good wireless connection and cause connectivity issues with the MFDs.

SUMMARY

According to aspects illustrated herein, there are provided a method, non-transitory computer readable medium, and an apparatus for limiting wireless connectivity roaming of a multi-function device (MFD). One disclosed feature of the embodiments is a method that fails to re-authenticate on a current access point of a wireless network, accesses a list of access points within a user defined boundary, selects an access point in the list of access points based on a parameter of the access point, and establishes a wireless communication path with the access point.

Another disclosed feature of the embodiments is a non-transitory computer-readable medium having stored thereon a plurality of instructions, the plurality of instructions including instructions which, when executed by a processor, cause the processor to perform an operation that fails to re-authenticate on a current access point of a wireless network, accesses a list of access points within a user defined boundary, selects an access point in the list of access points based on a parameter of the access point, and establishes a wireless communication path with the access point.

Another disclosed feature of the embodiments is an apparatus comprising a processor and a computer readable medium storing a plurality of instructions which, when executed by the processor, cause the processor to perform an operation that fails to re-authenticate on a current access point of a wireless network, accesses a list of access points within a user defined boundary, selects an access point in the list of access points based on a parameter of the access point, and establishes a wireless communication path with the access point.

DETAILED DESCRIPTION

The present disclosure broadly discloses a method and apparatus to limit wireless connectivity roaming of MFDs. As discussed above, MFDs have very good power savings modes when not in use. However, over time the wireless connection of an MFD may roam to different access points for various reasons. For example, some access points may be shut down due to maintenance or failure. As a result, the MFD may attempt to connect to the next access point. When that access point is shut down due to maintenance or failure, the MFD may attempt to connect to another access point.

In some instances, the MFD may be prevented from re-connecting to a previous access point due to blacklisting. For example, when the MFD fails to connect to a previous access point, the MFD may blacklist that access point. Over time, many of the previously connected access points may be blacklisted by the MFD.

As a result, the MFD may eventually be connected to an access point that is located relatively far away from the MFD or that has a poor signal strength to the MFD. In some instances, the access point may be located on a different floor. As a result, the poor signal strength may cause connectivity issues with the MFD and may create a poor user experience.

The present disclosure provides a modification to the MFD to allow the MFD to limit wireless connectivity roaming. For example, the MFD may include a setting to allow a user to define a roaming boundary with a list of user selected access points. When the MFD is disconnected from an access point, the MFD may attempt to connect to another access point within the roaming boundary set by the user. If the MFD has previously connected to all of the MFDs within the roaming boundary, the MFD may then attempt to connect to the first MFD in the list of user selected access points.

In other words, rather than continuing to roam further and further away from the MFD, the user defined boundary may limit how far the MFD may roam for a wireless connection. When the boundary is reached, the list of user selected access points may be refreshed (e.g., the blacklist value for each access point may be reset to zero), and the MFD may then attempt to re-connect to the closest access point on the list.

FIG. 1illustrates an example network100of the present disclosure. In one example, an MFD104may be deployed in a location102. The location102may be a building, a floor of an enterprise location, and the like. Although a single MFD104is illustrated in the location102, it should be noted that any number of MFDs104may be located in the location102.

In one embodiment, the MFD104may be any type of device that may print, copy, fax, scan, and the like. The MFD104may include a display108that presents a user interface. The display108may be a touch screen display or may include input devices (e.g., a keyboard, a mouse, a touch pad, and the like) to allow the user to interact with the user interface and make selections, provide inputs, and the like.

In one embodiment, the location102may include a wireless network that includes a plurality of access points1061to106n(hereinafter also referred to individually as an access point106or collectively as access points106). The access points106may be wireless access points that provide wireless connectivity to the overall wireless network. The access points106may provide a local area network (LAN) within the location102. The access points106may be in communication with each other and with a gateway router that provides access to a wide area network (WAN).

The access points106may be part of the same wireless network (e.g., an SSID), but be configured with different identification numbers (e.g., also referred to as the BSSID). For example, as a mobile device moves throughout the location102, the mobile device may be connected to the overall wireless network. However, access to the overall wireless network may be provided by each access point106depending on the location of the mobile device. As the mobile device moves from a location near the access point1061to the access point1062, connection to the wireless network for the mobile device may be passed on from access point1061to access point1062.

However, the MFD104may be a stationary device. In other words, the MFD104generally does not move throughout the location102. Initially, the MFD104may be connected to the access point1061. However, over time the MFD104may begin to roam to other access points1062to106n. As noted above, the access points106may be shut down due to maintenance, failure, or any other reason and may cause the MFD104to attempt to connect to a different access point.

When the MFD104attempts to connect to the access point that is shut down and the attempt fails, the MFD104may blacklist that access point. Over time, the MFD104may be connected to an access point that provides very poor signal strength and may create connectivity issues. In some instances the MFD104may connect to access points on a different floor or a different building.

FIG. 2illustrates a block diagram of the MFD104that limits wireless connectivity roaming. In one embodiment, the MFD104may include a processor202, a wireless communication interface204, and a memory206. It should be noted that the MFD104has been simplified for ease of explanation and may include additional components that are not shown. For example, the MFD104may include other components such as a digital front end, various paper paths, a paper feeder, a print engine, printheads, a scanner, a finishing module, and the like.

In one embodiment, the processor202may be communicatively coupled to the wireless communication interface204and the memory206. The processor202may control operation of the wireless communication interface204and may execute instructions stored in the memory206to perform the functions described herein.

In one embodiment, the wireless communication interface204may be a Wi-Fi radio or any other type of wireless device that can establish a wireless communication path to the access points106. In one embodiment, the wireless communication interface204may communicate with all of the access points106to obtain information that may be presented to the user to limit the wireless connectivity roaming, as discussed in further details below.

In one embodiment, the memory206may be a non-transitory computer readable medium. The memory206may be a hard disk drive, a solid state drive, random access memory (RAM), read only memory (ROM), and the like.

In one embodiment, the memory206may include a user interface to set a wireless connectivity boundary208(also referred to herein as a user interface208) and an access point list210. In one embodiment, the user interface208may be presented to the user in the display108of the MFD104. The user interface208may allow the user create a user defined boundary. The user defined boundary may defined by the user selected access points106to limit how far the MFD104may roam for a wireless connection.

For example, the user may want to create a boundary that is no further than the access point1063illustrated inFIG. 1. As a result, the user defined boundary may include the access points1061,1062, and1063. The user selected access points1061,1062, and1063may be stored as the access point list210.

In one embodiment, the access point list210may control how far the MFD is allowed to roam in the location102for an access point106. For example, the MFD104may be initially authenticated to the access point1061. For example, the MFD104may establish a wireless connection to the access point1061with the proper security credentials (e.g., a password associated with the access point1061). At a later time, the MFD104may be disconnected from the access point1061and may attempt to re-authenticate with the access point1061. However, the re-authentication may fail (e.g., the access point1061may still be offline for maintenance), and the access point1061may be blacklisted.

As a result, the MFD104may authenticate to the next access point on the access point list210(e.g., the access point1062). Ata later time, the MFD104may be disconnected from the access point1062and re-authentication may fail again to the access point1062. As a result, the MFD104may attempt to authenticate to the next access point available on the access point list210(e.g., the access point1063). However, at a later time, the MFD104may be disconnected from the access point1063and re-authentication may fail.

Previously, the MFD104may have attempted to authenticate to an access point1064that may be far away from the MFD104and provide a weak signal strength. However, in the present disclosure, when all of the access points in the access point list210have been previously used, the access point list210may be reset to allow attempts to re-authenticate to the access points in the access point list210again.

For example, resetting the access point list210may include decrementing the blacklist counter for each access point in the access point list210back to 0. As a result, when all of the access points in the access point list210have been used, the blacklist counter for each access point may be reset to a value of 0. The MFD104may then attempt to re-authenticate with the first access point or the access point with the strongest wireless signal in the access point list210(e.g., the access point1061). In other words, the MFD104may continuously cycle through the access points in access point list210as the MFD104loses connections to access points106for various reasons and attempts to authenticate to other access points106in the location102. Said another way, the access point list210may control which access points106the MFD104may authenticate with and may limit the wireless connectivity roaming of the MFD104.

FIG. 3illustrates a screenshot302of an example of the user interface208that may be presented to the user on the display108. In one embodiment, the screenshot302may present a table that lists all available access points. The table may include columns304,306,308,310, and312. A glyph316may indicate which access point the MFD104is currently authenticated with or connected to.

In one embodiment, the column304may provide boxes to allow a user to select the access points to include in the access point list210and set the user defined boundary. The column306may provide identification information or BSSID for the access points. In one embodiment, the identification information may be the media access control (MAC) identification (ID) number of the access points. In one embodiment, the identification information may also include a label (e.g., access point in conference room, access point in hallway, 2ndfloor access point, and the like).

In one embodiment, the column308may provide a signal strength percentage associated with each access point. The signal strength percentage may also provide a location. For example, the access point with the highest signal strength percentage may also be the access point that is located closest to the MFD104. Conversely, the access point with the lowest signal strength percentage may also be the access point that is located the furthest away from the MFD104.

In one embodiment, the column310may provide a channel number being used by the access point. In one embodiment, the column312may provide the security protocol used by the access point (e.g., wired equivalent privacy (WEP), Wi-Fi protected access (WPA), WPA-2, and the like).

In one embodiment, the user may interact with the user interface shown in the screenshot302to select the access points by checking the boxes associated with each access point in the column304. In one embodiment, the user may select the access points based on signal strength or location (e.g., the closer the access point, the stronger the wireless signal strength), the channel used by the access point, or the security protocol used by the access point. For example, some access points may be closer or have a stronger signal strength percentage, but may use a channel that is not available on the MFD104. In another example, some access points may have a stronger signal strength percentage, but the access points may use a weaker security protocol.

In one embodiment, the user interface208shown in the screenshot302may also include a refresh button314. The refresh button314may cause the MFD104to re-broadcast a signal to all nearby access points. The broadcast signal may request identification information, measure signal strength, channel information, security protocols used by the access points, and the like from the access points to update the information provided in the table. The refresh button314may also allow new access points to be identified or access points that were shut down, but reactivated to reappear in the table. Thus, a user may periodically use the refresh button314to update information related to which access points are available and the information associated with the access points. The updated information may then be used to change the access points that are selected for the access point list210based on the updated information.

FIG. 4illustrates a flowchart of an example method400for limiting wireless connectivity roaming of an MFD of the present disclosure. In one embodiment, one or more blocks of the method400may be performed by the MFD104or a computer/processor that controls operation of an MFD as illustrated inFIG. 5and discussed below.

At block402, the method400begins. At block404, the method400fails to re-authenticate on a current access point of a wireless network. For example, the MFD may be connected to the current access point. However, at some point the current access point may be taken off-line or powered down for maintenance, failure, or any other reason. The MFD may attempt to re-authenticate with the access point, but fail. As a result, the blacklist value may be incremented until it exceeds a threshold (e.g., 1, 2 or any other value). When the blacklist value exceeds threshold, the MFD may no longer attempt to re-authenticate with the current access point.

At block406, the method400accesses a list of access points within a user defined boundary. When the current access point is blacklisted, the MFD may attempt to authenticate to another access point that is in the list of access points. In one embodiment, the list of access points may be those access points selected by the user to define the boundary for wireless connectivity roaming.

In one embodiment, the list of access points and the user defined boundary may be selected via a user interface of the MFD. For example, the user may select the desired access points from a list of all available access points. The list of access points may be stored in local memory of the MFD. Thus, the boundary may be predefined by the user before the method400begins.

At block408, the method400selects an access point in the list of access points based on a parameter of the access point. In one embodiment, the parameter may include a signal strength percentage, a channel that is used by the access point, a security protocol used by the access point, and the like, from the access points available in the list. In one embodiment, the access point with the next highest signal strength percentage within the list of access points may be selected by the MFD for authentication.

In one embodiment, the MFD may select the access point based on a parameter that was not previously selected. In other words, if the MFD blacklisted a previously used access point, the previously used access point may not be selected.

At block410, the method400establishes a wireless communication path with the access point. For example, the MFD may attempt to authenticate with the access point that is selected from the list of access points. After the MFD authenticates to the access point, the MFD may access the wireless network via the selected access point.

In one embodiment, the MFD may fail to re-authenticate to the selected access point (e.g., similar to the failure to authenticate to the current access point in block404). The MFD may access the list of access points again. If there are additional access points in the list of access points available for authentication that were not previously used, the MFD may select another access point and attempt to authenticate to that access point.

However, if the access point is the last access point in the list of access points, the MFD may then re-attempt to connect with the first access point in the list of access points. The “first” access point may be the access point with the highest signal strength percentage in the list of access points or the access point that the MFD is initially authenticated to after the list of access points is created. For example, the list of access points may be ordered based on the signal strength percentage, and the “first” access point may be the first access point in the ordered list. In another example, the list of access points may be ordered based on when the MFD was connected to the access point. For example, the list of access points may be ordered based on a sequence of when the MFD authenticated to each access point. Thus, the “first” access point may be the access point that the MFD was initially authenticated to after the list of access points was created.

In one embodiment, if the access point in block410is the last access point in the list of access points, the list of access points may be reset. In other words, the blacklist value associated with each access point in the list of access point may be decremented to a value of 0. As a result, the MFD may select any access point in the list of access points (e.g., the “first” access point) and authenticate to that access point. At block412, the method400ends.

FIG. 5depicts a high-level block diagram of a computer that is dedicated to perform the functions described herein. As depicted inFIG. 5, the computer500comprises one or more hardware processor elements502(e.g., a central processing unit (CPU), a microprocessor, or a multi-core processor), a memory504, e.g., random access memory (RAM) and/or read only memory (ROM), a module505for limiting wireless connectivity roaming of an MFD, and various input/output devices506(e.g., storage devices, including but not limited to, a tape drive, a floppy drive, a hard disk drive or a compact disk drive, a receiver, a transmitter, a speaker, a display, a speech synthesizer, an output port, an input port and a user input device (such as a keyboard, a keypad, a mouse, a microphone and the like)). Although only one processor element is shown, it should be noted that the computer may employ a plurality of processor elements.