US20170026525A1 - Analyzing sensor data of a device collected by a mobile endpoint device operating with the device - Google Patents
Analyzing sensor data of a device collected by a mobile endpoint device operating with the device Download PDFInfo
- Publication number
- US20170026525A1 US20170026525A1 US14/807,529 US201514807529A US2017026525A1 US 20170026525 A1 US20170026525 A1 US 20170026525A1 US 201514807529 A US201514807529 A US 201514807529A US 2017026525 A1 US2017026525 A1 US 2017026525A1
- Authority
- US
- United States
- Prior art keywords
- sensor data
- mobile endpoint
- operational sensor
- endpoint device
- collected
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 claims abstract description 51
- 238000004891 communication Methods 0.000 claims abstract description 42
- 230000002776 aggregation Effects 0.000 claims description 28
- 238000004220 aggregation Methods 0.000 claims description 28
- 230000007613 environmental effect Effects 0.000 claims description 10
- 238000004458 analytical method Methods 0.000 claims description 4
- 230000000977 initiatory effect Effects 0.000 claims description 2
- 238000007726 management method Methods 0.000 description 44
- 230000006870 function Effects 0.000 description 11
- 238000012544 monitoring process Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 239000000428 dust Substances 0.000 description 3
- 230000006872 improvement Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 230000007257 malfunction Effects 0.000 description 2
- 239000002184 metal Substances 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N1/00—Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
- H04N1/00002—Diagnosis, testing or measuring; Detecting, analysing or monitoring not otherwise provided for
- H04N1/00026—Methods therefor
- H04N1/00039—Analysis, i.e. separating and studying components of a greater whole
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/12—Digital output to print unit, e.g. line printer, chain printer
- G06F3/1201—Dedicated interfaces to print systems
- G06F3/1202—Dedicated interfaces to print systems specifically adapted to achieve a particular effect
- G06F3/121—Facilitating exception or error detection and recovery, e.g. fault, media or consumables depleted
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/12—Digital output to print unit, e.g. line printer, chain printer
- G06F3/1201—Dedicated interfaces to print systems
- G06F3/1223—Dedicated interfaces to print systems specifically adapted to use a particular technique
- G06F3/1229—Printer resources management or printer maintenance, e.g. device status, power levels
- G06F3/1234—Errors handling and recovery, e.g. reprinting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/12—Digital output to print unit, e.g. line printer, chain printer
- G06F3/1201—Dedicated interfaces to print systems
- G06F3/1278—Dedicated interfaces to print systems specifically adapted to adopt a particular infrastructure
- G06F3/1292—Mobile client, e.g. wireless printing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N1/00—Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
- H04N1/00002—Diagnosis, testing or measuring; Detecting, analysing or monitoring not otherwise provided for
- H04N1/00007—Diagnosis, testing or measuring; Detecting, analysing or monitoring not otherwise provided for relating to particular apparatus or devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N1/00—Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
- H04N1/00002—Diagnosis, testing or measuring; Detecting, analysing or monitoring not otherwise provided for
- H04N1/00026—Methods therefor
- H04N1/00037—Detecting, i.e. determining the occurrence of a predetermined state
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N1/00—Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
- H04N1/00002—Diagnosis, testing or measuring; Detecting, analysing or monitoring not otherwise provided for
- H04N1/00026—Methods therefor
- H04N1/00058—Methods therefor using a separate apparatus
- H04N1/00061—Methods therefor using a separate apparatus using a remote apparatus
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N1/00—Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
- H04N1/00002—Diagnosis, testing or measuring; Detecting, analysing or monitoring not otherwise provided for
- H04N1/00071—Diagnosis, testing or measuring; Detecting, analysing or monitoring not otherwise provided for characterised by the action taken
- H04N1/00074—Indicating or reporting
- H04N1/00079—Indicating or reporting remotely
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N2201/00—Indexing scheme relating to scanning, transmission or reproduction of documents or the like, and to details thereof
- H04N2201/0001—Diagnosis, testing or measuring; Detecting, analysis or monitoring not otherwise provided for
- H04N2201/0003—Method used
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N2201/00—Indexing scheme relating to scanning, transmission or reproduction of documents or the like, and to details thereof
- H04N2201/0077—Types of the still picture apparatus
- H04N2201/0094—Multifunctional device, i.e. a device capable of all of reading, reproducing, copying, facsimile transception, file transception
Abstract
Description
- The present disclosure relates generally to improving operation and maintenance of a device and, more particularly, to an apparatus and method for analyzing sensor data of a device collected by a mobile endpoint device operating with the device.
- Some devices may operate best under certain conditions. When certain environmental conditions are outside of desired operating conditions, the device may malfunction or operate inefficiently. However, the operating conditions near the devices are often not monitored. As a result, when the device fails, troubleshooting may not resolve the failure completely.
- In addition, some devices may operate without a communication connection to a management service for the devices. For example, these devices may operate without any monitoring of how the device is performing. Thus, without communication capabilities these devices remain isolated and cannot be part of the management service.
- According to aspects illustrated herein, there are provided a method, non-transitory computer readable medium and apparatus for analyzing operational sensor data of a device collected by a mobile endpoint device operating with the device. One disclosed feature of the embodiments is a method that receives the operational sensor data, a time stamp, a location of the device and a device identification (ID) from the mobile endpoint device, wherein the operational sensor data is collected by the mobile endpoint device from the device when the mobile endpoint device initiates a communication session with the device and transmits the operational sensor data to a management service, wherein the operational sensor data is analyzed to determine a cause of a failure of the device when the device fails.
- 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 operations that receive the operational sensor data, a time stamp, a location of the device and a device identification (ID) from the mobile endpoint device, wherein the operational sensor data is collected by the mobile endpoint device from the device when the mobile endpoint device initiates a communication session with the device and transmit the operational sensor data to a management service, wherein the operational sensor data is analyzed to determine a cause of a failure of the device when the device fails.
- 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 operations that receive the operational sensor data, a time stamp, a location of the device and a device identification (ID) from the mobile endpoint device, wherein the operational sensor data is collected by the mobile endpoint device from the device when the mobile endpoint device initiates a communication session with the device and transmit the operational sensor data to a management service, wherein the operational sensor data is analyzed to determine a cause of a failure of the device when the device fails.
- The teaching of the present disclosure can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:
-
FIG. 1 illustrates an example block diagram of a communication network of the present disclosure; -
FIG. 2 illustrates a flowchart of an example method for analyzing operational sensor data of a device collected by a mobile endpoint device operating with the device; -
FIG. 3 illustrates a flowchart of an example method for analyzing operational sensor data of a multi-function device (MFD) collected by a mobile endpoint device operating with the MFD; and -
FIG. 4 illustrates a high-level block diagram of a computer suitable for use in performing the functions described herein. - To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.
- The present disclosure broadly discloses a method and apparatus for analyzing operational sensor data of a device collected by a mobile endpoint device operating with the device. As discussed above, some devices may operate best under certain conditions. When certain environmental conditions are outside of desired operating conditions, the device may malfunction or operate inefficiently. However, the operating conditions near the devices are often not monitored. As a result, when the device fails, troubleshooting may not resolve the failure completely.
- In addition, some devices may operate without a communication connection to a management service for the devices. For example, these devices may operate without any monitoring of how the device is performing. Thus, without communication capabilities these devices remain isolated and cannot be part of the management service.
- Embodiments of the present disclosure leverage the ubiquity of mobile endpoint devices to collect operational sensor data at a location of a device that is part of a management service. The operational sensor data along with additional information (e.g., a time stamp or other information associated with the device) can be forwarded to an aggregation service provider. The aggregation service provider may then forward the collected data and other information to a management service that manages the device. At a later time when a failure of the device is detected, the management service may correlate the operational sensor data that was collected to correlate the operational sensor data to the failure to determine a cause of the failure of the device.
-
FIG. 1 illustrates anexample communication network 100 of the present disclosure. In one embodiment, thecommunication network 100 may include an Internet Protocol (IP)network 102. TheIP network 102 may include an application server (AS) 104 and a database (DB) 106. Although only asingle AS 104 and asingle DB 106 are illustrated inFIG. 1 , it should be noted that any number of application servers and databases may be deployed. - In one embodiment, the AS 104 may be deployed as a dedicated computer, for example the computer in
FIG. 4 and described below, for performing the functions described inFIG. 2 and described below. In one embodiment, the AS 104 may be an aggregation server that is owned and operated by an aggregation service provider. For example, the aggregation service provider may collect operational sensor data for adevice 110 that is managed by amanagement service 112 and transmit the operational sensor data to themanagement service 112 that is a subscriber to the aggregation services and manages thedevice 110. - In one embodiment, the DB 106 may store information that is collected by a
mobile endpoint device 108. The information may include, for example, operational sensor data, a time stamp, a location of adevice 110, a device identification (ID), and the like. The DB 106 may store information regarding whichmanagement services 112 have subscribed to an aggregation service and whichdevices 110 belong to whichmanagement services 112. - In one embodiment, the
management service 112 may be a service provider that manages devices, e.g., thedevice 110, for a company or enterprise. For example, themanagement service 112 may be a managed print service (MPS), and the like. Although only asingle management service 112 is illustrated inFIG. 1 , it should be noted that any number ofmanagement services 112 may subscribe with the aggregation service provider to receive operational sensor data for one ormore devices 110 of themanagement service 112. - As noted above, the
management service 112 may manage, monitor or service one ormore devices 110 for a company or enterprise. In one embodiment, thedevice 110 may be a multi-function device (MFD), a thermostat, an appliance, and the like. Thedevice 110 may operate most efficiently under certain parameters measured by a sensor (e.g., operational sensor parameters). The operational sensor parameters may include environmental conditions (e.g., temperature, humidity level, dust level, radio frequency interference, vibrations, etc.), a location (e.g., a location in a corner, a location in an open area, a particular floor of a building, near metal walls, etc.), device parameters (e.g., whether the device is level, how often the device operates, what types of jobs are being performed by the device, etc.), or any other sensor data that may be relevant (e.g., accelerometer data, a wireless communication signal strength (e.g., a Wireless Fidelity (Wi-Fi) signal, an Long-Term Evolution (LTE) signal, and the like), an ambient light level, an image of thedevice 110, a photograph of thedevice 110 and surroundings, and the like). - In one embodiment, the operational sensor parameters may be measured or obtained by a sensor. In one embodiment, the sensor may be within a
mobile endpoint device 108 that attempts to pair with thedevice 110. For example, themobile endpoint device 108 may include sensors that may be able to obtain Wi-Fi signal strength, accelerometer data, vibration data, an amount of ambient light data, take a photograph, and the like. In another embodiment, the sensor may be within thedevice 110. For example, the sensors may be able to determine a temperature, whether thedevice 110 is level, how of the device operates, and the like. - In another embodiment, the sensor may be one or more
external sensors 114 that are located near or in close proximity to thedevice 110. In other words, thesensor 114 may be at asame location 150 that thedevice 110 is located. The one or moreexternal sensors 114 may collect operational parameters such as humidity, magnetic interference, RF interference, location information, dust levels, or any other operational parameters that cannot be obtained by themobile endpoint device 108 or thedevice 110. Thesensor 114 may have wireless communication capabilities and may transmit operational sensor data that is collected to themobile endpoint device 108 over a wireless connection (e.g., Bluetooth, Wi-Fi, LAN, RF signals, and the like). - In one embodiment, a
mobile endpoint device 108 may attempt to initiate a communication session with thedevice 110. In one embodiment, the communication session may be a pairing request to control thedevice 110. Themobile endpoint device 108 may be any type ofmobile endpoint device 108 such as, for example, a smartphone, a tablet computer, a laptop computer, and the like. When themobile endpoint device 108 attempts to pair with thedevice 110, themobile endpoint device 108 may collect operational sensor data from one or more sensors within themobile endpoint device 108, within thedevice 110, and/or the one or moreexternal sensors 114. - For example, the
mobile endpoint device 108 may be a smartphone and thedevice 110 may be an MFD. The smartphone may use tap to print technology to tap or read a code on the MFD to pair with the MFD and print a document. When the pairing is initiated by the smartphone, the smartphone may collect operational sensor data from one or more of: the smartphone itself, the MFD or theexternal sensor 114. - In another example, the
mobile endpoint device 108 may be a smartphone and thedevice 110 may be a thermostat. The smartphone may initiate a pairing with the thermostat to remotely control the thermostat. When the pairing is initiated by the smartphone, the smartphone may collect operational sensor data from one or more of the smartphone itself, the thermostat or theexternal sensor 114. - It should be noted that although the examples above describe a single
mobile endpoint device 108 collecting operational sensor data from asingle device 110 that any numbermobile endpoint devices 108 may be collecting operational sensor data from any number ofdevices 110 at the same time or at different times. In other words, theAS 104 may be receiving operational sensor data for a plurality ofdifferent devices 100 from a plurality of differentmobile endpoint devices 108 continuously. - In one embodiment, in addition to the operational sensor data, the
mobile endpoint device 108 may collect additional information such as, for example, a time stamp, a location of the device 110 (e.g., using the global positioning system (GPS) data on the mobile endpoint device 108), and a device identification (ID). For example, the device ID may be a media access control (MAC) ID of thedevice 110, a user selected name for thedevice 110, or any other ID that can be used to identify aparticular device 110. The additional information may be used with the operational sensor data to correlate the operational sensor data to a failure of thedevice 110 and determine a cause of the failure, as discussed below. - In one embodiment, the
mobile endpoint device 108 may then transmit the operational sensor data that is collected to theAS 104 of the aggregation service provider when a trigger is detected. For example, the trigger may be a time period. For example, themobile endpoint device 108 may collect data from a plurality ofdifferent device 110 and periodically transmit the data to the aggregation service provider (e.g., every hour, every day, and the like). In another example, the trigger may be when a particular wireless communication protocol (e.g., a Wi-Fi connection, a cellular connection, a wide area connection, a long term evolution (LTE) connection, and the like) is detected. In other words, the operational sensor data may be collected from thedevice 110 over a first communication protocol and the operational sensor data may be transmitted to theAS 104 over a second communication protocol that is different from the first communication protocol. For example, thedevice 110 may communicate with themobile endpoint device 108 over a local wireless connection (e.g., Bluetooth). At a later time, when themobile endpoint device 108 detects a Wi-Fi network, themobile endpoint device 108 may transmit the operational sensor data to theAS 104. - In another embodiment, the
mobile endpoint device 108 may transmit the operational data immediately. In other words, the trigger may be when reception of the operational sensor data is complete. - In one embodiment, the
device 110 may be managed by themanagement service 112. Themanagement service 112 may have subscribed to operational sensor data aggregation services provided by the aggregation service provider. Thedevice 110 may not have any communication capabilities with themanagement service 112 that is located remotely from thedevice 110. In other words, thedevice 110 may only be capable of communicating locally with themobile endpoint device 108. However, using the embodiments of the present disclosure, themanagement service 112 may still be able to manage thedevice 110 using the operational data that is collected by themobile endpoint device 108, sent to theAS 104 of the aggregation service provider and received from theAS 104. - For example, the
management service 112 may receive an indication that thedevice 110 has failed. The indication may be from themobile endpoint device 108. For example, themobile endpoint device 108 may attempt to pair with thedevice 110 and thedevice 110 may fail to pair with themobile endpoint device 108. In another example, themobile endpoint device 108 may successfully pair with thedevice 110, but thedevice 110 may fail to perform a print job that themobile endpoint device 108 has sent. In another example, themobile endpoint device 108 may successfully pair with thedevice 110, but thedevice 110 may fail to change a temperature setting as instructed by themobile endpoint device 108. When the failure is observed by themobile endpoint device 108, themobile endpoint device 108 may send a notification with the operational sensor data to theAS 104. The aggregation service provider may then forward the notification to themanagement service 112 to indicate that thedevice 110 has failed. - The notification to the
management service 112 may initiate an analysis on the operational sensor data to correlate the operational sensor data to the failure of thedevice 110. For example, the correlation may be performed to determine a cause of the failure. In one example, the failure may be at a time the operational sensor data is collected by themobile endpoint device 108. For example, themobile endpoint device 108 may have been unable to pair with thedevice 110. Themanagement service 112 may analyze the operational sensor data to determine that RF interference is causing the failure to pair with themobile endpoint device 108. - In another example, the failure may be at a later time after operational sensor data is collected over a period of time. For example, the failure may be that the
device 110 repeatedly jams. Themanagement service 112 may analyze the operational sensor data to determine that a high level of humidity is causing paper to roll and jam thedevice 110. - In another example, the
management service 112 may analyze the operational sensor to determine that high vibration levels are causing the level of thedevice 110 to shift over time leading to the periodic paper jams in thedevice 110. In other words, environmental conditions that are collected as part of the operational sensor data may be correlated to other operational sensor data to determine a cause of the failure. Said another way, environmental conditions that may otherwise have been unrelated to the operation of thedevice 110 may be transformed into a cause of failure of thedevice 110. -
FIG. 2 illustrates a flowchart of amethod 200 for analyzing operational sensor data of a device collected by a mobile endpoint device operating with the device. In one embodiment, one or more steps or operations of themethod 200 may be performed by theAS 104 or a computer as illustrated inFIG. 4 and discussed below. - At
block 202 themethod 200 begins. Atblock 204, themethod 200 receives operational sensor data, a time stamp data, a location of a device and a device identification (ID) from a mobile endpoint device. For example, when the mobile endpoint device initiates a communication session with the device over a local wireless communication protocol (e.g., Bluetooth, Wi-Fi, and the like), the mobile endpoint device may collect operational sensor data, as discussed above. - In one embodiment, the operational sensor data may be received from the mobile endpoint device when a trigger is detected by the mobile endpoint device. As discussed above, the trigger may be a predefined time period, when a particular wireless communication connection is detected, when the collection of operational sensor data is complete, and the like.
- At
block 206, themethod 200 transmits the operational sensor data to a management service. In one embodiment, the operational sensor data may correlate the operational sensor data to reported faults and/or failures. If a correlation is detected, the operational sensor data may be analyzed by the management service to determine a cause of a failure of the device when the device fails. Atblock 208 themethod 200 ends. -
FIG. 3 illustrates a flowchart of anexample method 300 for analyzing operational sensor data of a multi-function device (MFD) collected by a mobile endpoint device operating with the MFD. In one embodiment, one or more steps, blocks, or operations of themethod 300 may be performed by themobile endpoint device 108 or a computer as illustrated inFIG. 4 and discussed below. - At
block 302 themethod 300 begins. Atblock 304, themethod 300 initiates a pairing with an MFD. For example, the mobile endpoint device may initiate a pairing with the MFD to control the MFD remotely (e.g., a tap to print). - At
block 306, themethod 300 collects operational sensor data, a time stamp, a location of the device and a device ID. In one embodiment, the operational sensor data may include environmental conditions (e.g., temperature, humidity level, dust level, radio frequency interference, vibrations, etc.), a location (e.g., a location in a corner, a location in the open, a particular floor, near metal walls, etc.), device parameters (e.g., whether the device is level, how often the device operates, what types of jobs are being performed by the device, etc.), or any other sensor data that may be relevant (e.g., accelerometer data, a wireless communication signal strength (e.g., a Wi-Fi signal, an LTE signal, and the like), an ambient light level, an image of thedevice 110, a photograph of thedevice 110 and surroundings, and the like). - In one embodiment, the operational sensor data may be measured by one or more sensors in the MFD. In another embodiment, the operational sensor data may be measured by one or more sensors in the mobile endpoint device. In another embodiment, the operational sensor data may be measured by one or more external sensors located in a same location at the MFD. In other words, the external sensors are located in close proximity to, near to or attached to the MFD. In one embodiment, the operational sensor data may be measured by all, or any combination of, the one or more sensors on the MFD, the one or more sensors on the mobile endpoint device or the one or more external sensors.
- At
block 308, themethod 300 determines if a trigger to transmit data is detected. As discussed above, the trigger may be a predefined time period, when a particular wireless communication connection is detected, when the collection of operational sensor data is complete, and the like. If the trigger is not detected, then themethod 300 may loop atblock 308 until the trigger is detected. When the trigger is detected, themethod 300 may proceed to block 310. - At
block 310, themethod 300 transmits the operational sensor data, the time stamp, the location of the device and the device ID to a sensor aggregation server. In one embodiment, the mobile endpoint device may collect operational sensor data, the time stamp, the location of the device and the device ID for a plurality of different devices between transmissions to the sensor aggregation server. - In one embodiment, after the operational sensor data is transmitted to the aggregation server, and conversely, the aggregation server transmits the operational sensor data to a management service that is a subscriber of the aggregation services, the management service may be responsible for monitoring operation of the devices. For example, the devices may have wireless or wired communication capabilities with the management service to report faults and/or errors, which can cause the management service to analyze the operational sensor data.
- At
optional block 312, themethod 300 may determine if a failure of the MFD is detected. For example, the MFD may only have local communications capabilities and be incapable of communicating with the management service. As a result, the failure may be optionally detected by the mobile endpoint device while interacting with the MFD. The failure may be detected from the initiation of the pairing request to a failure of the MFD to perform a job or a function requested by the mobile endpoint device. In one embodiment, the failure may be detected after an initial interaction between the mobile endpoint device and the MFD or after a period of time or several interactions between the MFD and the mobile endpoint device and/or other mobile endpoint devices. If a failure of the MFD is not detected, themethod 300 may proceed to block 316. When a failure of the MFD is detected, themethod 300 may proceed to block 314. - At
optional block 314, themethod 300 may transmit a notification to an aggregation service provider to initiate an analysis of the operational sensor data by a management service to correlate the operational sensor data to a failure of the MFD to determine a cause of the failure. The notification may indicate to the aggregation service provider that the device has failed. The aggregation service provider may then determine which management service manages the device that has failed and determine if the management service is a subscriber of the operational sensor data aggregation service. If the management service is a subscriber, the aggregation service provider may then send the notification to the management service so that the management service may initiate an analysis of the operational sensor data. Atblock 316 themethod 300 ends. - It should be noted that although not explicitly specified, one or more steps, functions, or operations of the
methods FIGS. 2 and 3 that recite a determining operation, or involve a decision, do not necessarily require that both branches of the determining operation be practiced. In other words, one of the branches of the determining operation can be deemed as an optional step. - As a result, the embodiments of the present disclosure improve the functioning of a computer or a device. For example, a device without any networking capability may be monitored by a management service to automatically identify failures and resolve failures in the device. In addition, the embodiments of the present disclosure transform operational sensor data that typically provides information about an environmental condition into a cause of a failure of the device, as discussed above. Notably, no previous machine or computer was capable of performing the functions described herein as the present disclosure provides an improvement in the technological arts of managed services of devices (e.g., managed print services).
-
FIG. 4 depicts a high-level block diagram of a computer that can be transformed to into a machine that is dedicated to perform the functions described herein. Notably, no computer or machine currently exists that performs the functions as described herein. As a result, the embodiments of the present disclosure improve the operation and functioning of the computer to improve monitoring of devices to automatically identify failures and resolve failures in the device, as disclosed herein. - As depicted in
FIG. 4 , thecomputer 400 comprises one or more hardware processor elements 402 (e.g., a central processing unit (CPU), a microprocessor, or a multi-core processor), amemory 404, e.g., random access memory (RAM) and/or read only memory (ROM), amodule 405 for analyzing operational sensor data of a device collected by a mobile endpoint device operating with the device, and various input/output devices 406 (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. Furthermore, although only one computer is shown in the figure, if the method(s) as discussed above is implemented in a distributed or parallel manner for a particular illustrative example, i.e., the steps of the above method(s) or the entire method(s) are implemented across multiple or parallel computers, then the computer of this figure is intended to represent each of those multiple computers. Furthermore, one or more hardware processors can be utilized in supporting a virtualized or shared computing environment. The virtualized computing environment may support one or more virtual machines representing computers, servers, or other computing devices. In such virtualized virtual machines, hardware components such as hardware processors and computer-readable storage devices may be virtualized or logically represented. - It should be noted that the present disclosure can be implemented in software and/or in a combination of software and hardware, e.g., using application specific integrated circuits (ASIC), a programmable logic array (PLA), including a field-programmable gate array (FPGA), or a state machine deployed on a hardware device, a computer or any other hardware equivalents, e.g., computer readable instructions pertaining to the method(s) discussed above can be used to configure a hardware processor to perform the steps, functions and/or operations of the above disclosed methods. In one embodiment, instructions and data for the present module or
process 405 for analyzing operational sensor data of a device collected by a mobile endpoint device operating with the device (e.g., a software program comprising computer-executable instructions) can be loaded intomemory 404 and executed byhardware processor element 402 to implement the steps, functions or operations as discussed above in connection with theexemplary methods - The processor executing the computer readable or software instructions relating to the above described method(s) can be perceived as a programmed processor or a specialized processor. As such, the
present module 405 for analyzing operational sensor data of a device collected by a mobile endpoint device operating with the device (including associated data structures) of the present disclosure can be stored on a tangible or physical (broadly non-transitory) computer-readable storage device or medium, e.g., volatile memory, non-volatile memory, ROM memory, RAM memory, magnetic or optical drive, device or diskette and the like. More specifically, the computer-readable storage device may comprise any physical devices that provide the ability to store information such as data and/or instructions to be accessed by a processor or a computing device such as a computer or an application server. - It will be appreciated that variants of the above-disclosed and other features and functions, or alternatives thereof, may be combined into many other different systems or applications. Various presently unforeseen or unanticipated alternatives, modifications, variations, or improvements therein may be subsequently made by those skilled in the art which are also intended to be encompassed by the following claims.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/807,529 US9544449B1 (en) | 2015-07-23 | 2015-07-23 | Analyzing sensor data of a device collected by a mobile endpoint device operating with the device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/807,529 US9544449B1 (en) | 2015-07-23 | 2015-07-23 | Analyzing sensor data of a device collected by a mobile endpoint device operating with the device |
Publications (2)
Publication Number | Publication Date |
---|---|
US9544449B1 US9544449B1 (en) | 2017-01-10 |
US20170026525A1 true US20170026525A1 (en) | 2017-01-26 |
Family
ID=57706107
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/807,529 Active US9544449B1 (en) | 2015-07-23 | 2015-07-23 | Analyzing sensor data of a device collected by a mobile endpoint device operating with the device |
Country Status (1)
Country | Link |
---|---|
US (1) | US9544449B1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111194014A (en) * | 2019-12-19 | 2020-05-22 | 株洲国创轨道科技有限公司 | Equipment fault real-time repair reporting system and method thereof |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10072951B2 (en) * | 2015-12-04 | 2018-09-11 | International Business Machines Corporation | Sensor data segmentation and virtualization |
US10536351B2 (en) * | 2016-07-29 | 2020-01-14 | Splunk Inc. | Analytics for edge devices |
US10460255B2 (en) | 2016-07-29 | 2019-10-29 | Splunk Inc. | Machine learning in edge analytics |
US11087236B2 (en) | 2016-07-29 | 2021-08-10 | Splunk Inc. | Transmitting machine learning models to edge devices for edge analytics |
JP2023027931A (en) * | 2021-08-18 | 2023-03-03 | シャープ株式会社 | Image processing device, system and control method |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5370832B2 (en) * | 2009-07-01 | 2013-12-18 | 株式会社リコー | State determination device and failure prediction system using the same |
US9235819B2 (en) * | 2011-11-04 | 2016-01-12 | Canon Kabushiki Kaisha | Printing system, image forming apparatus, and method |
JP5879316B2 (en) * | 2013-09-27 | 2016-03-08 | 株式会社沖データ | Image forming system and image forming apparatus |
-
2015
- 2015-07-23 US US14/807,529 patent/US9544449B1/en active Active
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111194014A (en) * | 2019-12-19 | 2020-05-22 | 株洲国创轨道科技有限公司 | Equipment fault real-time repair reporting system and method thereof |
Also Published As
Publication number | Publication date |
---|---|
US9544449B1 (en) | 2017-01-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9544449B1 (en) | Analyzing sensor data of a device collected by a mobile endpoint device operating with the device | |
US10200506B2 (en) | Method, system and device for monitoring data | |
EP3758295A1 (en) | Rules driven software deployment agent | |
US9792188B2 (en) | Remote cable access point reset | |
US9730085B2 (en) | Method and apparatus for managing wireless probe devices | |
JP2019509681A (en) | Cloud verification and test automation | |
US10445335B2 (en) | Computing environment connectivity system | |
US20210021458A1 (en) | Method and apparatus for providing trouble isolation via a network | |
EP3544330B1 (en) | System and method for validating correctness of changes to network device configurations | |
US9813308B2 (en) | Statistical monitoring of customer devices | |
US9658917B2 (en) | Server performance correction using remote server actions | |
JP2006215958A (en) | Peripheral device management system, its method, and peripheral device management program | |
JP2008090504A (en) | Computer maintenance support system and analysis server | |
US11750448B2 (en) | Network device-integrated asset tag-based environmental sensing with mutual authentication | |
US10432490B2 (en) | Monitoring single content page application transitions | |
US20220066427A1 (en) | System and method for distributing edge program in manufacturing field | |
JP6488600B2 (en) | Information processing system, program, and information processing apparatus | |
US10009488B1 (en) | Methods and systems for automatically initiating print device service requests using proactive incident detection and analysis | |
US9438761B1 (en) | Sharing devices via an email | |
US9220005B2 (en) | Device management services via mobile devices | |
JP5764090B2 (en) | Terminal state detection apparatus and terminal state detection method | |
US20230419806A1 (en) | Method and system for device monitoring and diagnostics | |
JP2017216504A (en) | Communication device, program, and information apparatus | |
JP2020038466A (en) | Information processor, information processing system, and program | |
WO2016099451A1 (en) | Method and apparatus for case management foresight and insight |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: XEROX CORPORATION, CONNECTICUT Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ZEHLER, PETER J.;TREDOUX, GAVAN LEONARD;RAJENDRAN, PREMKUMAR;SIGNING DATES FROM 20150723 TO 20150814;REEL/FRAME:040328/0762 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: CITIBANK, N.A., AS AGENT, DELAWARE Free format text: SECURITY INTEREST;ASSIGNOR:XEROX CORPORATION;REEL/FRAME:062740/0214 Effective date: 20221107 |
|
AS | Assignment |
Owner name: XEROX CORPORATION, CONNECTICUT Free format text: RELEASE OF SECURITY INTEREST IN PATENTS AT R/F 062740/0214;ASSIGNOR:CITIBANK, N.A., AS AGENT;REEL/FRAME:063694/0122 Effective date: 20230517 |
|
AS | Assignment |
Owner name: CITIBANK, N.A., AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:XEROX CORPORATION;REEL/FRAME:064760/0389 Effective date: 20230621 |
|
AS | Assignment |
Owner name: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:XEROX CORPORATION;REEL/FRAME:065628/0019 Effective date: 20231117 |
|
AS | Assignment |
Owner name: CITIBANK, N.A., AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:XEROX CORPORATION;REEL/FRAME:066741/0001 Effective date: 20240206 |