Remote device management interface

Information

  • Patent Grant
  • 10976891
  • Patent Number
    10,976,891
  • Date Filed
    Thursday, November 10, 2016
    7 years ago
  • Date Issued
    Tuesday, April 13, 2021
    3 years ago
Abstract
A network for remotely managing a plurality of remote devices that are each individually configurable to have selected operating characteristics includes a server connected to the network and to the plurality of remote devices, and a display coupled to a computer which is connected to the network. Also included are means for assigning a common icon to each remote device of the same type and displaying the icons on the server display, and means for coloring each icon to indicate a current configuration status of each remote device and for displaying the color on the icon on the display.
Description
FIELD OF THE INVENTION

This invention relates to the management of remote devices such as portable data terminals (PDTs), and more particularly to an interface for managing the remote devices.


BACKGROUND

Remote devices, such as portable data terminals (PDTs), portable data assistants (PDAs), and other devices used for automatic identification and data collection (AIDC) generally provide data at remote locations back to a central office. Sometimes these devices have the ability to monitor the operation of the device and to provide device status information to the central office. Such a remote device is described in U.S. Patent Publication No. 2008/0185432 A1 to Caballo et al. which is hereby incorporated by reference.


The remote devices can have the ability to have their configuration changed or to have a new application program installed while away from the central office. U.S. Patent Publication No. 2009/0044003 A1 to Berthiaume et al. teaches such a method, and is hereby incorporated by reference.


The remote devices can be managed by Remote Device Management (RDM) systems that allow an RDM user to manage the remote devices including updating configurations and device software, and to track problems which may be common to several devices, and provide fixes for these problems where feasible.


However, some RDM systems accumulate vast amounts of diagnostic and performance data. Organizing the data in a clear, concise, meaningful, and intuitive way on the graphical user interface of a computer display is a problem. Either too much data is presented so as to be cluttered and confusing, or the user has to navigate through multiple, sometimes non-intuitive, dialogs to access desired information.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a diagram of a system of remote devices in communication with a server and a remote device management terminal in accordance with at least one embodiment of the present invention;



FIGS. 2A-2I are user interface screens showing displayed information, screen configuration options, and control commands for monitoring and controlling the configuration of the remote devices shown in FIG. 1; and



FIG. 3 is a flow chart of a method for recognizing a problem with one of the remote devices shown in FIG. 1, and resolving the problem, if possible, using data received from other remote devices.





It will be appreciated that for purposes of clarity and where deemed appropriate, reference numerals have been repeated in the figures to indicate corresponding features.


DETAILED DESCRIPTION

Reference will now be made to exemplary embodiments of the invention which are illustrated in the accompanying drawings. This invention, however, may be embodied in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these representative embodiments are described in detail so that this disclosure will be thorough and complete, and will fully convey the scope, structure, operation, functionality, and potential of applicability of the invention to those skilled in the art.


Referring to FIG. 1, a diagram 10 of a system of remote devices 12, 14, 16, and 18 in communication with a server 20 and a remote device management terminal 22 through a Wide Area Network (WAN) 24 in accordance with at least one embodiment of the present invention is shown. Those skilled in the art will understand that the WAN 24 may comprise the internet, cellular phone communication, other RF communication systems, etc. and combinations thereof. The remote device management terminal 22 includes a data processing unit 26, a keyboard 28, a pointing device 30 with at least two buttons for left and right clicks, and a display 32. The server 20 may have connected thereto a data storage module 34.


The remote devices 12-16 are data collection devices (DCDs) which may be portable data terminals (PDTs), portable data assistants (PDAs), etc. Data collection devices are a class of devices used to collect, process, and transfer data to a data processing system.


In operation, the remote devices 12-16 have the ability to monitor the operation of the respective devices and to provide device status and performance information to the central office as described in U.S. Patent Publication No. 2008/0185432 A1. The server 20 receives the data from remote devices, such as the remote devices 12-16 and provides configuration update information to the remote devices. The terminal 22 interacts with the server 20 to provide interface screens on the display 32 allowing a user of the remote devices to locate each remote device, determine the configuration of each remote device, analyze the performance of the remote devices, and send updated configuration information to the remote devices as necessary. The server 20 may also have error detection and configuration software, stored in a hard drive in the data processing unit 26 or the data storage module 34, which operates independently of the interface screens on the display 32.



FIG. 2A is one embodiment of a user interface screen 50, in the form of a Graphical User Interface (GUI), which might be shown on the display 32. The screen has a title “Remote Device Management” and has three main sections: a menu section 52, which has drop down lists (File, Selection Panel, Map Panel, Detail Panel, Window, and Help) for configuring the screen 50, a remote device interaction menu section 54 which has drop down lists (Configuration Update, Application Update, Diagnostics, and Security) for updating or querying one or more remote devices such as the remote devices 12-16, and a graphical presentation section 56 for providing graphical information that a user can view and manipulate.



FIG. 2A shows a map 60 of a geographical region with remote devices indicated by icons 62 (each associated with a number 1-9 in the map 60) representing the types of remote devices, some of which are colored (numbers 1, 6, 8, and 9) to indicate configuration information about the devices. A user can select the type of icon which represent different configuration information, the color, and other variables which may make up each icon using the “Map Panel” button in the menu section 52. Complete configuration information for each of the remote devices may be stored in the data storage module 34. The location of each remote device may be determined from the longitude and latitude detected by each remote device using an internal GPS module and sent to the server 20. A user can zoom in on sections of the map using a zoom control 64, and the area covered in the map is indicated by a scale on the right side of the map 60.


In one embodiment of the present invention a double left click on the pointing device 30 with the pointing device arrow over an icon, for example the icon of remote device numbered 3, causes a detail panel window 70 and a chart panel window 72 to pop up as shown in FIG. 2B. The detail window 70 may have an icon grouping 74 representing the particular remote device 62 with the same number as that shown in the map. Each grouping 74 may also include the icon 62 representing the type of device and icon 76 representing the type of symbology that the particular remote device is configured to recognize along with more configuration information in a configuration box 78 below the icon 62. For example a camera icon 76 may indicate a remote device with a picture taking capability. The application software (App Software) which is used in the remote device may be shown along with the software configuration (Config.). In addition, a list of the monitored data, labeled “Metrics” in FIG. 2B, that has been sent to the server 30 may be shown. Each metric may be described in a box 80 with the current value on a line 82 for the metric shown below each box 80. There may also be a section 86 for the user to enter notes on the selected device.


The chart panel 72 is shown with a graph of the average scan time versus time which the selected remote device has reported which is data of one of the metrics 80 shown in the detail panel. The data contained in both the detail panel 70 and the chart panel 72 can be customized using the Detail Panel button and the Chart Panel button, respectively, in the menu section 52. Each of the panels, which include the map panel, the detail panel, the chart panel, and the selection panel in the embodiment shown in the drawings, can be moved, sized, enabled, disabled, and hidden by the user.



FIG. 2C is FIG. 2B in which the arrow controlled by the pointing device 30 is hovering over the icon 62 for remote device number 8. A box 90 containing configuration information is produced to allow a user to quickly determine more detailed configuration information about the remote device.



FIG. 2D is another configuration of the user interface screen which has a selection panel on the left side and the map panel on the right side. The selection panel may have icon groupings 74 for each of the remote devices shown in the map panel. Each icon grouping 74 may have the combination of icons 62 and 76 and configuration information box 78 shown in the left side of the detail panel shown in FIG. 2B. The hover and double click capabilities of the pointing device with regard to the map panel also apply to the selection panel. A configuration box 92 may have colored text indicating a particular type of configuration. The colored text in the configuration box 92 allows the user to quickly identify remote devices 62 that have a particular configuration.



FIG. 2E is FIG. 2D after a right click of the pointing device 30 on the icon in the selection box representing the number 8 remote device. A box 94 may be formed around the device number 8 icon and a selection box 96 is presented to the user. Hovering the pointing device over any of the items listed in the selection box 96 may cause a further list (not shown) of choices for the user. In the embodiment shown in FIG. 2E the first four items, Configuration, Application, Diagnostics, and Security, may provide the same items as clicking the respective boxes in the menu section 54. The four items Selection, Map, Detail, and Chart may provide the same options as clicking each of the corresponding items in the menu section 52. Additional items, indicated by the vertical bullets, may be included in the selection box 96. These additional items may be commands to the selected remote devices to send certain data to the server 20 so that the data would be available to the user for further analysis and comparison.



FIG. 2F is FIG. 2D after four of the remote device icons have been dragged to a new position in the selection pane, a box 100 drawn around the four icons using the pointing device 30, and the selection box 96 made to appear by a right click on the pointing device 30 inside the box 84 away from any of the icon groups 74. By dragging selected icons corresponding to selected remote devices to one region, drawing a box around the selected icons, and right clicking on the box 100 a user can perform the same operation on several remote devices at once. For example, all of the devices within the box 100 can be upgraded with a new configuration by a user using the user interface screen shown in FIG. 2F. Hovering over an area of the box that is not filed with icon grouping 74 may bring up a configuration box which shows only the configuration parameters that are common to all of the remote devices inside the box. Thus, in FIG. 2F, hovering over an area of the box 100 that is not occupied by one of icon groupings 74 will produce a configuration box showing the common model numbers of the remote devices 3, 4, 5, and 6 if they are the same models, plus any other common configuration parameters.



FIG. 2G is FIG. 2F after the user has expanded a section around a selected location in the map 60 to form a more detailed map 102. The user has also elected to hide the remote devices other than the four remote devices inside the box 100 in both the selection panel and the map panel. Also, one of the icon groupings, 104, has been right clicked which brings up the selection box 96. In the embodiment shown in FIG. 2G, by using the selection box 96 the remote device represented by the icon grouping 104 may be updated by changing the application in the remote device or by changing the configuration of the remote device.



FIG. 2H is FIG. 2G after the remote device represented by icon grouping 104 has been updated which may result in displaying the remote device icon 62 in a new color thus confirming the update. Also, another icon 106 has been added to the remote device icon 104 in FIG. 2H indicating that the remote device now has the ability to interpret postal code symbols.



FIG. 2I shows the process of dragging an icon from the selection panel to the detail panel, as indicated by dashed line 108. A single left click may highlight the icon group 110 and the associated information with a box 112, and the box can be dragged into the detail panel. The transfer into the detail panel leaves the icon group 74 in the selection panel in one embodiment of the present invention. Also, by double left clicking on one of the metrics, as indicated by arrow 114, causes a plot of the metric value for a predetermined number of dates to be presented in the chart panel.


When the remote device manager interface screen is closed, the last screen and the setting in the selection, map, detail, and chart panels are saved and restored to the user when the interface screen is brought up the next time.


The user interface screens shown in FIGS. 2A-2I allow a user to address configuration issues by providing a graphical configuration tool. In addition, new devices introduced into the system can be quickly identified and brought into a desired configuration using the graphical user interfaces described above.



FIG. 3 is a flow chart 120 showing a process for identifying faults or potential faults in the remote devices 62. The server 20 receives raw metric data which enter the system as indicated by box 122. Such metrics may include CPU load, scan times, and the other monitored events listed in U.S. Patent Publication 2008/0185432. The raw metric data can be sent to the server automatically or can be sent to the server as a result of a request for information by the server 20. The server 20 will cross reference the new data with specifications for the acceptable range of the metric data stored in the data storage module 34 to determine if a new metric is out of tolerance, and may also compare the new metric data with previous data to determine if the new metric data deviates significantly from the mean of the previous metric data for the same type and configuration of remote device 62 as indicated by boxes 124 and 126.


If the metric data is out of range, in that it is out of tolerance or deviates significantly from the mean of previous metric data, or in case of a notification from a remote device of an error or device fault, the server 20 would try to correlate this data with previous data to determine if the fault has previously occurred as indicated by box 128. In both cases the system would also attempt to find a correlation between the device with the issue and the device model, revision, installed software, etc. of other devices. In this way it would not only detect a problem, but detect precisely what other devices may have the same issue and, therefore, automatically update those devices. In the correlation process, indicated by box 128, the system will also attempt to make correlations between a metric that is out of range and devices that had the same or similar out of range condition, thus being able to anticipate if a system is likely to have a problem. The events that it would compare would not be limited to faults or out of tolerance metrics as even data that seems okay could be a predictor of an issue. As the database grows and its mesh of event correlations grows, the system would be increasingly effective at predicting issues.


If the metric data is out of range by the test described above and indicated in box 126, the server 20 determines if a fix is available for the out of range condition as indicated by box 130. If a fix is available, the fix is applied as indicated in box 132. If a fix is not available, a user is alerted as indicated in box 134. Here the term “user” refers to either the operator of the remote device or a person in charge of the remote devices 62, or both.


If it is determined that there is a pattern with the faulted device, the device that has a metric that is out of range, in the test indicated in boxes 126 and 128, then a determination is made whether the fault is critical as indicated in box 136. If the fault is critical, then the user is alerted as indicated by box 134, and if the fault is not critical, the server will wait for more metric data as indicated in box 138 by returning to receive new raw metric data indicated by box 122. If it is determined that there is not a pattern with the faulted device in box 128, then a check is made using a broader data base, such as a data base made available from a manufacturer of the particular remote device, or wait for more metric data as indicated in box 140 by returning to receive new raw metric data indicated by box 122.


While the invention has been described with reference to particular embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the scope of the invention.


Therefore, it is intended that the invention not be limited to the particular embodiments disclosed as the best mode contemplated for carrying out this invention, but that the invention will include all embodiments falling within the scope and spirit of the appended claims.

Claims
  • 1. A method for managing a plurality of remote devices, the method comprising: providing a user interface, the user interface comprising a map of a geographical region in which one or more remote devices of the plurality of remote devices are located, wherein each remote device of the plurality of remote devices is a mobile data collection device that is configurable by receiving one or more software updates from a server;displaying, for each remote device of the one or more remote devices, a respective icon representative of the respective remote device on the map at a first location on the map that corresponds to a first location of the remote device in the geographical region, the first location of the remote device on the map determined at least in part based upon a first location data obtained from the remote device;displaying, for each icon placed on the map, a first graphical characteristic of the respective icon to indicate a first configuration status;adjusting the first graphical characteristic to a second graphical characteristic in response to determining that the remote device has changed to a second configuration status, the second configuration status determined based on performance data comprising a scan time for the remote device to conduct symbology scanning, and wherein adjusting the first graphical characteristic to the second graphical characteristic comprises:determining whether the scan time deviates from a mean of previous scan times,in response to determining that the scan time deviates from the mean of previous scan times, determining that the performance data is out of specification and indicates a fault associated with the remote device, andassessing the second configuration status of the remote device based on an application of an update, which addresses the fault indicated by the performance data being out of specification, to the remote device based on the performance data being out of specification;adjusting the respective icon representative of the respective remote device on the map to a second location on the map from the first location of the remote device on the map in response to determining a second location of the remote device in the geographical region, the second location of the remote device on the map determined at least in part based upon a second location data obtained from the remote device; anddetermining a correlation between the remote device and at least one other remote device of the plurality of remote devices for ascertaining that the at least one other remote device is likely to exhibit the fault and, based on the determination, automatically applying the update to the at least one other remote device.
  • 2. The method of claim 1, further comprising: updating a configuration of the remote device to extend decoding capability of the remote device to a different or an additional symbology; andadding another icon on the user interface to indicate the additional symbology associated with the extended decoding capability of the remote device.
  • 3. The method of claim 1, further comprising, determining that the update addresses the fault indicated by the performance data being out of specification, determining that the update is available, and applying the update in response to the update being available, wherein the second graphical characteristic of the respective icon reflects the applied update.
  • 4. The method of claim 1, further comprising, based on selection of an icon on the map, displaying current data collected using the remote device represented by the selected icon, and displaying configuration data for the remote device represented by the selected icon, wherein the configuration data comprises an indication of a corresponding type of symbology that the remote device represented by the selected icon is configured to scan.
  • 5. The method of claim 1, further comprising, displaying, on the map, icons of all remote devices, of the one of more remote devices, which are of a selected type, and hiding, on the map, icons of all remote devices, of the one or more remote devices, which are of a type other than the selected type.
  • 6. The method of claim 5, further comprising, based on selection of an icon on the map, displaying current data collected using the remote device represented by the selected icon, and displaying configuration data for the remote device represented by the selected icon.
  • 7. The method of claim 1, further comprising displaying, on the user interface, a graph of an average scan time in relation to a scan time reported by a selected remote device.
  • 8. The method of claim 1, further comprising, displaying configuration information for the remote device by at least one of selecting or hovering over the icon.
  • 9. The method of claim 1, further comprising, receiving, a notification of the fault from the remote device, and in response, applying the update to the remote device.
  • 10. The method of claim 1, further comprising, providing, a selection panel on the user interface, the selection panel comprising multiple icon groupings, each icon grouping corresponding to a respective icon placed on the map, wherein an icon grouping comprises a device icon for the remote device represented by the icon, on the map, to which the icon grouping corresponds and further comprises at least one additional icon representative of at least one characteristic of the remote device represented by the icon, on the map, to which the icon grouping corresponds.
  • 11. The method of claim 10, further comprising: dragging and dropping selected icon groupings of the multiple icon groupings to an area of the selection panel;enclosing the area of the selection panel in a boundary, comprising enclosing the selected icon groupings within the boundary;applying a common software update to each of the remote devices represented by the icons, on the map, to which the selected icon groupings enclosed within the boundary correspond; andselecting an icon grouping of the selected icon groupings enclosed within the boundary and updating the remote device, represented by the icon, on the map, to which the selected icon grouping corresponds, with individual updates for that remote device.
  • 12. The method of claim 1, wherein based on the performance data being out of specification, the application of the update is withheld pending collection of further performance data, wherein a current configuration status is determined based further on collection of the further performance data.
  • 13. The method of claim 1, wherein the performance data comprises a central processing unit (CPU) load associated with the remote device, wherein adjusting the first graphical characteristic to the second graphical characteristic comprises: in response to determining that the CPU load deviates from a mean of previous CPU loads, determining that the performance data is out of specification and indicates the fault associated with the remote device.
  • 14. A system for managing a plurality of remote devices, the system comprising: a client device comprising a display;a central processing unit configured to communicate with the plurality of remote devices and the client device, wherein the plurality of remote devices are mobile data collection devices,wherein the central processing unit is further configured to: receive a first location data from the plurality of remote devices, wherein the first location data indicates a current location of a remote device of the plurality of remote devices;provide, to the client device, a map of a geographical region in which at least one of the plurality of remote devices are located, wherein the client device displays a user interface comprising the map;provide, to the client device, a respective icon representative of the respective remote device to be placed on the map at a first location on the map that corresponds to a first location of the remote device in the geographical region based on the first location data;obtain a performance data from at least one of the plurality of remote devices, wherein the performance data comprises data representative of a scan time for the remote device to scan a symbology;determine a current configuration status of the remote device by comparing the scan time for the remote device to scan the symbology to a mean of previous scan times in order to determine whether the performance data is out of specification and indicates a fault associated with the remote device, and wherein the current configuration status is determined based further on an application of a configuration update, which addresses the fault indicated by the performance data being out of specification, to the remote device based on the performance data being out of specification;determine a correlation between the remote device and at least one other remote device from the plurality of remote devices for ascertaining that the at least one other remote device is likely to exhibit the fault and, based on the correlation, automatically applying the configuration update to the at least one other remote device;provide, to the client device, at least one new icon indicating the current configuration status for at least one remote device represented by the icon, wherein the at least one new icon comprises an adjustment to a graphical characteristic of the icon representing the remote device; andprovide, to the client device, a second location for at least one icon placed on the map, wherein the second location of the respective icon indicates a second location of the remote device in the geographical region, the second location determined at least in part based upon a second location data obtained from the remote device.
  • 15. The system of claim 14, wherein the central processing unit is further configured to: update a configuration of the remote device to extend decoding capability of the remote device to an additional symbology; andadding another icon on the user interface to indicate the additional symbology associated with the extended decoding capability of the remote device.
  • 16. The system of claim 14, wherein the central processing unit is further configured to: determine that the configuration update addresses the fault indicated by the performance data being out of specification, determine that the configuration update is available, and apply the configuration update in response to the configuration update being available, wherein the current configuration status indicated by the adjusting of the graphical characteristic of the respective icon reflects the applied update.
  • 17. The system of claim 14, wherein, based on selection of an icon on the map, the central processing unit is further configured to display current data collected using the remote device represented by the selected icon, and display configuration data for the remote device represented by the selected icon.
  • 18. The system of claim 14, wherein the central processing unit is further configured to provide a selection panel of the user interface, the selection panel comprising multiple icon groupings, each icon grouping corresponding to a respective icon placed on the map, wherein an icon grouping comprises a device icon for the remote device represented by the icon, on the map, to which the icon grouping corresponds and further comprises at least one additional icon representative of at least one characteristic of the remote device represented by the icon, on the map, to which the icon grouping corresponds.
  • 19. The system of claim 18, wherein, based on dragging and dropping selected icon groupings of the multiple icon groupings to an area of the selection panel, and based on enclosing the area of the selection panel in a boundary, comprising enclosing the selected icon groupings within the boundary, the central processing unit is further configured to apply a group software update to each of the remote devices represented by the icons, on the map, to which the selected icon groupings enclosed within the boundary correspond.
  • 20. The system of claim 14, wherein the performance data comprises a central processing unit (CPU) load associated with the remote device, wherein the central processing unit is further configured to: in response to determining that the CPU load deviates from a mean of previous CPU loads, determine that the performance data is out of specification and indicates the fault associated with the remote device.
  • 21. A device for managing a plurality of remote devices, the device comprising: a display configured to display a user interface, wherein the user interface comprises a map of a geographical region in which at least one of the plurality of remote devices are located, wherein each remote device is a mobile data collection device;wherein the device is configured to: display, on the user interface, a plurality of icons, wherein each icon is representative of each remote device on the map at a first location on the map that corresponds to a first location of the remote device in the geographical region;display, on the user interface, a manipulated graphical characteristic of at least one icon to indicate a current configuration status for the remote device represented by the icon, wherein the current configuration status indicates whether a performance data of the remote device comprising a scan time for the remote device to conduct symbology scanning is out of specification and indicates a fault associated with the remote device based on comparing the scan time to a mean of previous scan times, and wherein the current configuration status further indicates an application of a configuration update, which addresses the fault indicated by the performance data being out of specification, to the remote device based on the performance data being out of specification;determine a correlation between the remote device and at least one other remote device from the plurality of remote devices for ascertaining that the at least one other remote device is likely to exhibit the fault and based on the correlation automatically applying the configuration update to the at least one other remote device; anddisplay, on the user interface, a second location for each icon placed on the map in response to determining that the remote device has moved from the first location in the geographical region to a second location in the geographical region.
  • 22. A network for remotely managing a plurality of remote devices, the network comprising: a server in communication with the plurality of remote devices that are mobile data collection devices; anda data processing system in communication with a display, wherein the data processing system is configured to perform a method comprising: providing a user interface, the user interface comprising a map of a geographical region in which one or more remote devices of the plurality of remote devices are located;assigning a common icon type for each remote device of a same type, and placing for each remote device of the one or more remote devices, a respective icon representative of the respective remote device on the map at a first location on the map that corresponds to a first location of the remote device in the geographical region, the first location of the remote device on the map determined at least in part based upon a first location data obtained from the first location of the remote device in the geographical region, wherein the common icon type is used for icons representative of remote devices of the same type;displaying, for each icon placed on the map, a first graphical characteristic of the respective icon to indicate a first configuration status;adjusting the first graphical characteristic to a second graphical characteristic in response to determining that the remote device has changed to a second configuration status, the second configuration status determined based on performance data comprising a scan time for the remote device to conduct symbology scanning, and wherein adjusting the first graphical characteristic to the second graphical characteristic comprises: in response to determining that the scan time deviates from a mean of previous scan times, determining that the performance data is out of specification and indicates a fault associated with the remote device, andassessing the second configuration status of the remote device based on an application of an update, which addresses the fault indicated by the performance data being out of specification, to the remote device based on the performance data being out of specification;adjusting the respective icon representative of the respective remote device on the map to a second location on the map from the first location of the remote device on the map in response to determining a second location of the remote device in the geographical region, the second location of the remote device on the map determined at least in part based upon a second location data obtained from the remote device; anddetermining a correlation between the remote device and at least one other remote device of the plurality of remote devices for ascertaining that the at least one other remote device is likely to exhibit the fault and based on the determination automatically applying the update to the at least one other remote device.
CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. patent application Ser. No. 12/961,627 for Remote Device Management Interface filed Dec. 7, 2010 (and published Jun. 9, 2011 as U.S. Patent Publication No. 2011/0138310), now U.S. Pat. No. 9,497,092, which claims the benefit of U.S. Patent Application No. 61/267,641 for Remote Device Management Interface filed Dec. 8, 2009. Each of the foregoing patent applications, patent publication, and patent is hereby incorporated by reference in its entirety.

US Referenced Citations (401)
Number Name Date Kind
1726343 Danziger Aug 1929 A
5109486 Seymour Apr 1992 A
5261044 Dev et al. Nov 1993 A
5402316 Volz et al. Mar 1995 A
5463742 Kobayashi Oct 1995 A
5504921 Dev et al. Apr 1996 A
5546145 Bernardi et al. Aug 1996 A
5552959 Penniman et al. Sep 1996 A
5579001 Dempsey et al. Nov 1996 A
5579529 Terrell et al. Nov 1996 A
5579775 Dempsey et al. Dec 1996 A
5587560 Crooks et al. Dec 1996 A
5615625 Cassidy et al. Apr 1997 A
5640953 Bishop et al. Jun 1997 A
5655081 Bonnell et al. Aug 1997 A
5687734 Dempsey et al. Nov 1997 A
5724509 Starkweather et al. Mar 1998 A
5742286 Kung Apr 1998 A
5752917 Fuchs May 1998 A
5774793 Cooper et al. Jun 1998 A
5793967 Simciak et al. Aug 1998 A
5798951 Cho et al. Aug 1998 A
5805442 Crater et al. Sep 1998 A
5815735 Baker Sep 1998 A
5819110 Motoyama Oct 1998 A
5825617 Kochis et al. Oct 1998 A
5835733 Walsh et al. Nov 1998 A
5848253 Walsh et al. Dec 1998 A
5862349 Cho et al. Jan 1999 A
5867714 Todd et al. Feb 1999 A
5875312 Walsh et al. Feb 1999 A
5878256 Bealkowski et al. Mar 1999 A
5889964 Cho et al. Mar 1999 A
5904727 Prabhakaran May 1999 A
5921459 Heraly et al. Jul 1999 A
5931909 Taylor Aug 1999 A
5935244 Swamy et al. Aug 1999 A
5941965 Moroz et al. Aug 1999 A
5961337 Kordes Oct 1999 A
5978591 Batholomew et al. Nov 1999 A
6032202 Lea et al. Feb 2000 A
6037788 Krajec et al. Mar 2000 A
6049454 Howell et al. Apr 2000 A
6070012 Eitner et al. May 2000 A
6085244 Wookey Jul 2000 A
6088752 Ahem Jul 2000 A
6091602 Helot Jul 2000 A
6098097 Dean et al. Aug 2000 A
6108717 Kimura et al. Aug 2000 A
6109039 Hougham et al. Aug 2000 A
6142593 Kim et al. Nov 2000 A
6151643 Cheng et al. Nov 2000 A
6158430 Pfeiffer et al. Dec 2000 A
6160719 May et al. Dec 2000 A
6161133 Kikinis Dec 2000 A
6171559 Sanders et al. Jan 2001 B1
6188572 Liao et al. Feb 2001 B1
6195265 Choi et al. Feb 2001 B1
6199108 Casey et al. Mar 2001 B1
6202209 Bartholomew et al. Mar 2001 B1
6226739 Eagle May 2001 B1
6240297 Jadoul et al. May 2001 B1
6247074 Shin et al. Jun 2001 B1
6256691 Moroz et al. Jul 2001 B1
6267475 Lee et al. Jul 2001 B1
6279059 Ludtke et al. Aug 2001 B1
6279154 Davis Aug 2001 B1
6285911 Watts, Jr. et al. Sep 2001 B1
6297963 Fogle Oct 2001 B1
6301106 Helot et al. Oct 2001 B1
6311321 Agnihotri et al. Oct 2001 B1
6324692 Fiske Nov 2001 B1
6330597 Collin et al. Dec 2001 B2
6339745 Novik Jan 2002 B1
6341274 Leon Jan 2002 B1
6341320 Watts, Jr. et al. Jan 2002 B1
6360362 Fichtner et al. Mar 2002 B1
6378128 Edelstein et al. Apr 2002 B1
6407335 Franklin-Lees et al. Jun 2002 B1
6407915 Derocher et al. Jun 2002 B1
6425126 Branson et al. Jul 2002 B1
6442639 McElhattan et al. Aug 2002 B1
6452325 Dupont Sep 2002 B1
6456306 Chin et al. Sep 2002 B1
6457076 Cheng et al. Sep 2002 B1
6461181 Goh et al. Oct 2002 B1
6467088 Alsafadi et al. Oct 2002 B1
6477588 Yerazunis et al. Nov 2002 B1
6484315 Ziese Nov 2002 B1
6489932 Chitturi et al. Dec 2002 B1
6505121 Russell Jan 2003 B1
6506009 Nulman et al. Jan 2003 B1
6511031 Lin Jan 2003 B2
6519143 Goko et al. Feb 2003 B1
6539358 Coon et al. Mar 2003 B1
6542943 Cheng et al. Apr 2003 B2
6558049 Shin May 2003 B1
6560643 Shepherd et al. May 2003 B1
6584336 Ali et al. Jun 2003 B1
6584499 Jantz et al. Jun 2003 B1
6587874 Golla et al. Jul 2003 B1
6593528 Franklin-Lees et al. Jul 2003 B2
6594534 Crowell Jul 2003 B1
6606678 Nakamura et al. Aug 2003 B1
6614979 Bourdeau et al. Sep 2003 B2
6615405 Goldman et al. Sep 2003 B1
6628517 Helot et al. Sep 2003 B1
6633482 Rode Oct 2003 B2
6658659 Hiller et al. Dec 2003 B2
6668296 Dougherty et al. Dec 2003 B1
6683786 Yin et al. Jan 2004 B2
6684241 Sandick et al. Jan 2004 B1
6697032 Chitturi et al. Feb 2004 B2
6722192 Benedict et al. Apr 2004 B2
6725260 Philyaw Apr 2004 B1
6725281 Zintel et al. Apr 2004 B1
6728956 Ono et al. Apr 2004 B2
6742025 Jennery et al. May 2004 B2
6751681 Torli et al. Jun 2004 B2
6754723 Kato et al. Jun 2004 B2
6760761 Sciacca Jul 2004 B1
6763403 Cheng et al. Jul 2004 B2
6766175 Uchiyama Jul 2004 B2
6766956 Boylan, III et al. Jul 2004 B1
6770028 Ali et al. Aug 2004 B1
6772264 Dayan et al. Aug 2004 B1
6778824 Wonak et al. Aug 2004 B2
6779068 Kim et al. Aug 2004 B2
6784855 Matthews et al. Aug 2004 B2
6806813 Cheng et al. Oct 2004 B1
6832082 Ramaswamy et al. Dec 2004 B1
6832373 O'Neill Dec 2004 B2
6833787 Levi Dec 2004 B1
6833989 Helot et al. Dec 2004 B2
6850158 Williams Feb 2005 B1
6854112 Crespo et al. Feb 2005 B2
6857013 Ramberg et al. Feb 2005 B2
6863210 Becker et al. Mar 2005 B2
6864891 Myers Mar 2005 B2
6868468 Boz et al. Mar 2005 B2
6886104 McClurg et al. Apr 2005 B1
6889263 Motoyama May 2005 B2
6895261 Palamides May 2005 B1
6895445 Ying et al. May 2005 B2
6898080 Yin et al. May 2005 B2
6904457 Goodman Jun 2005 B2
6907603 Scott Jun 2005 B2
6915514 Machida Jul 2005 B1
6920631 Delo Jul 2005 B2
6928493 Motoyama Aug 2005 B2
6944854 Kehne et al. Sep 2005 B2
6944858 Luu Sep 2005 B2
6947612 Helms et al. Sep 2005 B2
6954142 Lieberman et al. Oct 2005 B2
6955517 Nulman et al. Oct 2005 B2
6959172 Becker et al. Oct 2005 B2
6961586 Barbosa et al. Nov 2005 B2
6966058 Earl et al. Nov 2005 B2
6968550 Branson et al. Nov 2005 B2
6970952 Motoyama Nov 2005 B2
6973799 Kuehl et al. Dec 2005 B2
6976062 Denby et al. Dec 2005 B1
6981086 Wetzel et al. Dec 2005 B2
6985945 Farhat et al. Jan 2006 B2
6987988 Uchiyama Jan 2006 B2
6990549 Main et al. Jan 2006 B2
6990660 Moshir et al. Jan 2006 B2
6993615 Falcon Jan 2006 B2
6993760 Peev et al. Jan 2006 B2
6996634 Herrod et al. Feb 2006 B1
6999898 King et al. Feb 2006 B2
7000228 Mortazavi Feb 2006 B2
7003560 Mullen et al. Feb 2006 B1
7013331 Das Mar 2006 B2
7020571 Lee et al. Mar 2006 B2
7024189 Wonak et al. Apr 2006 B2
7039688 Matsuda et al. May 2006 B2
7043537 Pratt May 2006 B1
7054423 Nebiker et al. May 2006 B2
7054977 Kadambi et al. May 2006 B2
7069006 Wonak Jun 2006 B2
7072675 Kanakubo Jul 2006 B1
7076536 Chiloyan et al. Jul 2006 B2
7080371 Arnaiz et al. Jul 2006 B1
7085805 Ruberg et al. Aug 2006 B1
7085824 Forth et al. Aug 2006 B2
7086049 Goodman Aug 2006 B2
7089551 Fordemwalt et al. Aug 2006 B2
7099152 Gasbarro et al. Aug 2006 B2
7100271 Bauiler et al. Sep 2006 B2
7107380 Mohan Sep 2006 B1
7111055 Falkner Sep 2006 B2
7114021 Seshadri Sep 2006 B2
7117239 Hansen Oct 2006 B1
7117286 Falcon Oct 2006 B2
7130896 Engel et al. Oct 2006 B2
7133939 Desal et al. Nov 2006 B1
7149792 Hansen et al. Dec 2006 B1
7159016 Baker Jan 2007 B2
7185014 Hansen Feb 2007 B1
7185075 Mishra Feb 2007 B1
7188160 Champagne et al. Mar 2007 B2
7188171 Srinivasan et al. Mar 2007 B2
7191435 Lau et al. Mar 2007 B2
7194526 Kanemitsu et al. Mar 2007 B2
7216343 Das et al. May 2007 B2
7272711 Suda et al. Sep 2007 B2
7289995 Motoyama et al. Oct 2007 B2
7290258 Steeb et al. Oct 2007 B2
7316013 Kawano et al. Jan 2008 B2
7363359 Tripathy et al. Apr 2008 B1
7367514 Soule, III et al. May 2008 B2
7375654 Culpepper et al. May 2008 B2
7487114 Florance et al. Feb 2009 B2
7539862 Edgett et al. May 2009 B2
7564376 Jang Jul 2009 B2
7857222 Kosecki et al. Dec 2010 B2
7979854 Borole et al. Jul 2011 B1
8635309 Berthiaume et al. Jan 2014 B2
8907603 Shibata Dec 2014 B2
9497092 Gomez et al. Nov 2016 B2
20010042112 Slivka et al. Nov 2001 A1
20020073304 Marsh et al. Jun 2002 A1
20020083160 Middleton Jun 2002 A1
20020086703 Dimenstein et al. Jul 2002 A1
20020087392 Stevens Jul 2002 A1
20020087668 San Martin et al. Jul 2002 A1
20020087960 Hisatake Jul 2002 A1
20020092008 Kehne et al. Jul 2002 A1
20020092013 Delo Jul 2002 A1
20020094208 Palumbo Jul 2002 A1
20020095484 Pagani et al. Jul 2002 A1
20020100036 Moshir et al. Jul 2002 A1
20020103900 Cornelius Aug 2002 A1
20020109665 Matthews et al. Aug 2002 A1
20020129350 Wang et al. Sep 2002 A1
20020129355 Velten et al. Sep 2002 A1
20020139855 Dvorkis Oct 2002 A1
20020147974 Wookey Oct 2002 A1
20020174223 Childers Nov 2002 A1
20020179715 Kawai Dec 2002 A1
20020184349 Manukyan Dec 2002 A1
20020184350 Chen Dec 2002 A1
20020187024 Nulman Dec 2002 A1
20020191940 Bourdeau Dec 2002 A1
20020198969 Engel et al. Dec 2002 A1
20030018694 Chen et al. Jan 2003 A1
20030031539 Nulman et al. Feb 2003 A1
20030046675 Cheng et al. Mar 2003 A1
20030051235 Simpson Mar 2003 A1
20030059022 Nebiker et al. Mar 2003 A1
20030084436 Berger et al. May 2003 A1
20030088651 Wilson May 2003 A1
20030097427 Parry May 2003 A1
20030101021 Shah et al. May 2003 A1
20030111245 Haggerty Jun 2003 A1
20030154471 Teachman et al. Aug 2003 A1
20030188306 Harris et al. Oct 2003 A1
20030198015 Vogt Oct 2003 A1
20030217357 Parry Nov 2003 A1
20030217358 Thurston et al. Nov 2003 A1
20030221190 Deshpande et al. Nov 2003 A1
20030225939 Ying et al. Dec 2003 A1
20030231211 Shah et al. Dec 2003 A1
20040002943 Merrill et al. Jan 2004 A1
20040015949 Taylor Jan 2004 A1
20040020974 Becker et al. Feb 2004 A1
20040024933 Billington et al. Feb 2004 A1
20040049233 Edwards Mar 2004 A1
20040050247 Topping Mar 2004 A1
20040083471 Nam et al. Apr 2004 A1
20040098571 Falcon May 2004 A1
20040103172 Chen et al. May 2004 A1
20040123281 Olrik et al. Jun 2004 A1
20040127210 Shostak Jul 2004 A1
20040139757 Kuehl et al. Jul 2004 A1
20040143032 Auschra et al. Jul 2004 A1
20040148600 Hoshino Jul 2004 A1
20040154014 Bunger Aug 2004 A1
20040168167 Ono Aug 2004 A1
20040177380 Hamel et al. Sep 2004 A1
20040181593 Kanojia et al. Sep 2004 A1
20040192329 Barbosa et al. Sep 2004 A1
20040199615 Philyaw Oct 2004 A1
20040205709 Hiltgen et al. Oct 2004 A1
20040206821 Longacre, Jr. Oct 2004 A1
20040210897 Brockway et al. Oct 2004 A1
20040212822 Schinner Oct 2004 A1
20040216099 Okita et al. Oct 2004 A1
20040235532 Matthews et al. Nov 2004 A1
20040243991 Gustafson et al. Dec 2004 A1
20040243995 Sheehy Dec 2004 A1
20040255023 Motoyama et al. Dec 2004 A1
20040268340 Steeb et al. Dec 2004 A1
20050044544 Slivka et al. Feb 2005 A1
20050050538 Kawamata et al. Mar 2005 A1
20050052156 Liebenow Mar 2005 A1
20050060862 Baulier Mar 2005 A1
20050065822 Ying et al. Mar 2005 A1
20050086328 Landram et al. Apr 2005 A1
20050093821 Massie et al. May 2005 A1
20050097543 Hirayama May 2005 A1
20050097544 Kim May 2005 A1
20050108700 Chen et al. May 2005 A1
20050132348 Meulemans et al. Jun 2005 A1
20050132349 Roberts et al. Jun 2005 A1
20050132350 Markley et al. Jun 2005 A1
20050132351 Randall et al. Jun 2005 A1
20050144612 Wang et al. Jun 2005 A1
20050144614 Moslander et al. Jun 2005 A1
20050156715 Zou Jul 2005 A1
20050159847 Shah et al. Jul 2005 A1
20050168700 Berg et al. Aug 2005 A1
20050204036 Farhat et al. Sep 2005 A1
20050204353 Ji Sep 2005 A1
20050210458 Moriyama et al. Sep 2005 A1
20050210459 Henderson et al. Sep 2005 A1
20050210466 Carter et al. Sep 2005 A1
20050223372 Borchers Oct 2005 A1
20050223373 Gage et al. Oct 2005 A1
20050229171 Henry et al. Oct 2005 A1
20050235076 Winarski et al. Oct 2005 A1
20050246703 Ahonen Nov 2005 A1
20050251799 Wang Nov 2005 A1
20050254776 Morrison et al. Nov 2005 A1
20050257205 Costea et al. Nov 2005 A1
20050257209 Adams et al. Nov 2005 A1
20050273229 Steinmeier et al. Dec 2005 A1
20050278001 Qin et al. Dec 2005 A1
20060010437 Marolia Jan 2006 A1
20060013646 Baulier et al. Jan 2006 A1
20060019679 Rappaport Jan 2006 A1
20060029489 Nulman et al. Feb 2006 A1
20060031617 Falcon Feb 2006 A1
20060031828 Won et al. Feb 2006 A1
20060041881 Adkasthala Feb 2006 A1
20060049677 Lawrence et al. Mar 2006 A1
20060069813 Biamonte et al. Mar 2006 A1
20060070055 Hodder et al. Mar 2006 A1
20060082965 Walker et al. Apr 2006 A1
20060091216 Page May 2006 A1
20060099971 Staton May 2006 A1
20060106965 Falcon May 2006 A1
20060130037 Mackay Jun 2006 A1
20060132964 Lau et al. Jun 2006 A1
20060136893 Blossom et al. Jun 2006 A1
20060142129 Siaperas Jun 2006 A1
20060149321 Merry et al. Jul 2006 A1
20060149322 Merry et al. Jul 2006 A1
20060149323 Merry et al. Jul 2006 A1
20060150177 Liu et al. Jul 2006 A1
20060156302 Yamamoto et al. Jul 2006 A1
20060168578 Vorlicek Jul 2006 A1
20060168581 Goger et al. Jul 2006 A1
20060172873 Beard Aug 2006 A1
20060179431 Devanathan et al. Aug 2006 A1
20060200812 Mizutani et al. Sep 2006 A1
20060206888 Mavrinac et al. Sep 2006 A1
20060218545 Taguchi Sep 2006 A1
20060220840 Culpepper Oct 2006 A1
20060236518 Baulier Oct 2006 A1
20060238364 Keefe Oct 2006 A1
20060238384 Hess et al. Oct 2006 A1
20060248522 Lakshminarayanan et al. Nov 2006 A1
20060248524 Seely Nov 2006 A1
20060265446 Elgressy et al. Nov 2006 A1
20060277299 Baekelmans Dec 2006 A1
20070006207 Appaji Jan 2007 A1
20070006213 Shahidzadeh et al. Jan 2007 A1
20070006214 Dubal et al. Jan 2007 A1
20070033279 Battat Feb 2007 A1
20070038990 White et al. Feb 2007 A1
20070055969 Yang Mar 2007 A1
20070055970 Sakuda et al. Mar 2007 A1
20070074201 Lee Mar 2007 A1
20070083630 Roth et al. Apr 2007 A1
20070093243 Kapadekar et al. Apr 2007 A1
20070169073 O'Neill et al. Jul 2007 A1
20070169089 Bantz et al. Jul 2007 A1
20070169090 Kang Jul 2007 A1
20070169092 Lee Jul 2007 A1
20070169093 Logan et al. Jul 2007 A1
20070171093 Jang Jul 2007 A1
20070174834 Purkeypile et al. Jul 2007 A1
20070220505 Bukovec et al. Sep 2007 A1
20070234331 Schow et al. Oct 2007 A1
20070245333 Ferlitsch Oct 2007 A1
20080070495 Stricklen et al. Mar 2008 A1
20080141166 Goldberg Jun 2008 A1
20080185432 Caballero et al. Aug 2008 A1
20080209411 Koziol et al. Aug 2008 A1
20090013258 Hintermeister Jan 2009 A1
20090019152 Huang Jan 2009 A1
20090030556 Castelli et al. Jan 2009 A1
20090044003 Berthiaume Feb 2009 A1
20090138826 Barros May 2009 A1
20090210814 Agrusa Aug 2009 A1
20090300179 Srinivasan Dec 2009 A1
20100087188 Griff Apr 2010 A1
20100131455 Logan et al. May 2010 A1
20120221954 Tanaka Aug 2012 A1
Non-Patent Literature Citations (37)
Entry
Fifth Chinese Office Action in counterpart Chinese Application No. 2016110301554670 dated Nov. 8, 2016, pp. 1-8 [All references previously cited].
English-translation of Fifth Chinese Office Action in counterpart Chinese Application No. 2016110301554670 dated Nov. 8, 2016, pp. 1-11.
Fourth Chinese Office Action in related application CN201010601656.0. dated May 3, 2016, English Machine Translation provided, 26 pages [Previoulsy submitted in parent application].
First Chinese Office Action in Patent Application 201010601656.0 dated Sep. 5, 2014; Original and English translation provided. 22 pages [Previously submitted in parent applicaton].
Second Chinese Office Action in related Application No. 201010601656.0, dated May 14, 2015, 17 pages, English translation provided. [Previously submitted in parent application].
Third Chinese Office Action in related Application No. 201010601656.0, dated Dec. 31, 2015, 18 pages, English translation provided. [Previously submitted in parent application].
Decision on Rejection in counterpart Chinese Application No. 201010601656.0 dated Sep. 6, 2017, pp. 1-7 [All references previously cited].
English-translation of Decision on Rejection in counterpart Chinese Application No. 201010601656.0 dated Sep. 6, 2017, pp. 1-10.
Author unlisted, “iPass Policy Orchestration Automates Continuous Endpoint Security”, Redwood Shores, California, Nov. 15, 2004, iPass Inc., press release found at http://www.ipass.com/pressroom/pressroom_printfriendly.html?rid=132, pp. 1 through 3, printed Feb. 26, 2007. [Previously submitted in parent application].
Author unlisted, “iPass makes Mobile Device Management Easier and More Cost-Effective With New, Web-Based Version of Endpoint Policy Management ”, Redwood Shores, California, May 15, 2006, iPass Inc., press release found at http://www.ipass.com/pressroom/pressroom_printfriendly.html?rid=204, pp. 1 through 2, printed Feb. 26, 2007. [Previously submitted in parent application].
Author unlisted, “iPass Solves End-User Compliance Issues With New Solution for Trusted Mobility”, Redwood Shores, California, Jun. 27, 2005, iPass Inc., press release found at http://www.ipass.com/pressroom/pressroom_printfriendly.html?rid=163, pp. 1 through 3, printed Feb. 26, 2007. [Previously submitted in parent application].
Hand Held Products Partners with SOTI on Remote Device Management and Security, article found at http://www.handheld.com/Site.aspx/na/en/news_events/news_listing/listing/article/?article . . . , pp. 11 through 2, printed Mar. 31, 2009. [Previously submitted in parent application].
Author unlisted, Honeywell, NaurTech, CETerm, “Industrial Browser & Terminal Emulation”, pp. 1 through 2. [Previously submitted in parent application].
Author unlisted, Honeywell, SOTi.net, MobiControl v5, Honeywell Imaging and Mobility, 700 Visions Dr., Skaneateles Falls, NY 13153-0208, found at www.honeywell.com/aidc, pp. 1 and 2. [Previously submitted in parent application].
Sixth Chinese Office Action in counterpart Chinese Application No. 201010601656.0 dated Mar. 2, 2017, pp. 1-7 [All references previously cited].
English-translation of Sixth Chinese Office Action in counterpart Chinese Application No. 201010601656.0 dated Mar. 2, 2017, pp. 1-10.
Notice of Reexamination in counterpart Chinese Application No. 201010601656.0 dated Jul. 5, 2018, pp. 1-7 [All references previously cited].
English-translation of Notice of Reexamination in counterpart Chinese Application No. 201010601656.0 dated Jul. 5, 2018, pp. 1-9.
Reexamination Decision in counterpart Chinese Application No. 201010601656.0 dated Oct. 12, 2018, pp. 1-13 [All references previously cited].
English-translation Rexamination Decision in counterpart Chinese Application No. 201010601656.0 dated Oct. 12, 2018, pp. 1-7.
Fourth Chinese Office Action in related application CN201010601656.0. dated May 3, 2016, English Machine Translation provided, 26 pages [References have been previously cited and considered].
Advisory Action dated Jan. 6, 2016 for U.S. Appl. No. 12/961,627.
Advisory Action dated Jul. 8, 2013 for U.S. Appl. No. 12/961,627.
Advisory Action dated Mar. 25, 2015 for U.S. Appl. No. 12/961,627.
Applicant Initiated Interview Summary Mailed on Jan. 6, 2016 for U.S. Appl. No. 12/961,627.
Applicant Initiated Interview Summary Mailed on Jul. 5, 2013 for U.S. Appl. No. 12/961,627.
Applicant Initiated Interview Summary Mailed on May 23, 2013 for U.S. Appl. No. 12/961,627.
Applicant Initiated Interview Summary Mailed on Sep. 24, 2015 for U.S. Appl. No. 12/961,627.
Examiner initiated interview summary dated Aug. 15, 2013 for U.S. Appl. No. 12/961,627.
Examiner initiated interview summary dated Jun. 29, 2016 for U.S. Appl. No. 12/961,627.
Final Rejection dated Apr. 12, 2013 for U.S. Appl. No. 12/961,627.
Final Rejection dated Jan. 15, 2015 for U.S. Appl. No. 12/961,627.
Final Rejection dated Oct. 9, 2015 for U.S. Appl. No. 12/961,627.
Non-Final Rejection dated Aug. 14, 2014 for U.S. Appl. No. 12/961,627.
Non-Final Rejection dated Jun. 17, 2015 for U.S. Appl. No. 12/961,627.
Non-Final Rejection dated Oct. 26, 2012 for U.S. Appl. No. 12/961,627.
Notice of Allowance and Fees Due dated Jun. 29, 2016 for U.S. Appl. No. 12/961,627.
Related Publications (1)
Number Date Country
20170060383 A1 Mar 2017 US
Provisional Applications (1)
Number Date Country
61267641 Dec 2009 US
Continuations (1)
Number Date Country
Parent 12961627 Dec 2010 US
Child 15348326 US