WO2013086685A1

WO2013086685A1 - Microblog application and microblog account associated with printer

Info

Publication number: WO2013086685A1
Application number: PCT/CN2011/083882
Authority: WO
Inventors: Yang Huang
Original assignee: Hewlett-Packard Development Company, L.P.
Priority date: 2011-12-13
Filing date: 2011-12-13
Publication date: 2013-06-20

Abstract

An apparatus comprises a processor and a memory storing a microblog application, the microblog application comprising instructions executable by the processor to send printer information to a microblog and/or to process a command sent to a printer by a microblog server.

Description

MICROBLOG APPLICATION AND MICROBLOG ACCOUNT ASSOCIATED

WITH PRINTER

BACKGROUND

[0001] Various methods exist for remote management and configuration of printers. For example, a user may be able to view printer status through an application installed on a desk top computer.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Some examples are described in the following figures:

Figure 1 is a schematic diagram of a system for managing a printer with a microblog according to one example;

Figure 2 is a schematic diagram of a system for managing a printer with a microblog according to another example;

Figure 3 is a flow chart showing an example of a method for sending printer information to a microblog;

Figure 4A is a table showing an example of text conveying printer information;

Figure 4B is a screen shot showing an example of the user interface of a microblog associated with a printer;

Figure 5 is a flow chart showing an example of a method of controlling the communication of printer information via a microblog according to the information type;

Figure 6 is a flow chart showing a method of distributing printer information with a microblog according to one example;

Figure 7 is a flow chart showing a method of sending commands to a printer via a microblog according to one example;

Figure 8 is a schematic diagram showing a printer or printer server having a microblog application according to one example; and

Figure 9 is a schematic diagram showing a microblog server having a microblog account associated with a printer. DETAILED DESCRIPTION

[0003] As used herein, the term "printer" is not limited to just standard printers, but includes scanners, multifunction printers and various other types of electronic devices that perform one or more functions such as printing, scanning, faxing or copying.

[0004] Figure 1 shows one example of a system for managing a printer with a microblog according to the present disclosure. The system comprises a micro-blog enabled printer 10, a microblog server 20 and a client device 30. The printer 10 can communicate with the microblog server 20 over a direct communication link or a network, such as the Internet, a LAN, WLAN etc. Likewise the client device 30 can communicate with the microblog server 20 over a direct communication link or a network.

[0005] By 'micro-blog enabled' it is meant that the printer 10 can communicate with a microblog. This functionality may for instance be provided by a 'microblog application' 20 stored in a memory of the printer, which enables the printer to send and/or receive messages to and from a microblog account on the microblog server 20.

[0006] A microblog is a web based application which enables users to publish content (e.g. short comments or strings of text) online. Twitter and Weibo are well known examples of microblogs. Users may follow a microblog through a website, through an application on their client device or otherwise. A user may register as a 'follower' of a microblog account by sending a request to the microblog server or service provider. The microblog account resides on the microblog server and the microblog server typically has software to manage publication of content, forwarding of messages between users and lists of users registered to 'follow' each account.

[0007] In the example of Figure 1, a microblog account hosted by the microblog server is associated with a particular printer. There may be several microblog accounts each associated with a different printer. The microblog server may also host other microblog accounts which are not associated with a particular printer, but rather conventional microblogs associated with a person or an organization.

[0008] A client device is any electronic device which may remotely access a microblog account through the microblog server, e.g. a desktop computer, laptop computer, tablet device, mobile or smart phone etc. [0009] Figure 2 shows another example of a system in accordance with the present disclosure. As in Figure 1, there is a microblog server 20 and a client device 30. In addition there are two printers 10a and 10b which are not microblog-enabled. Rather these printers communicate with the microblog server 20 via a print server 15 which has a microblog application 20 for facilitating communication between the microblog and the printers. Printer 10c is a microblog enabled printer similar to that described in Figure 1. While the microblog enabled printer 10c is able to

communicate directly with the microblog server 20 and is arranged in this way in Figure 2, in an alternative configuration it would also be possible for the printer 10c to communicate with the microblog server indirectly via the print server 15 or another print server. Each of the printers 10a, 10b and 10c may have an associated microblog account hosted by the microblog server 20.

[0010] Figure 3 is a flow diagram showing a method of managing a printer according to one example. At 110 it is determined that the printer has "printer information" to communicate to the microblog server. This determination may be carried out by the printer itself, for instance by a 'microblog application' residing on the printer; alternatively in the case of non-microblog enabled printers the

determination may be carried out by a print server having a microblog application as shown in Figure 2.

[0011] The "printer information" may for instance be printer status information such as printer online status (whether the printer is power off, asleep or awake), printer cartridge status, printer paper status etc. However the printer information is not limited to 'printer status' information and may for instance be a print job notification, scan job notification, or a response to a command that was previously issued to the printer.

[0012] At 110 the printer communicates the "printer information" to the microblog server 20 either directly, or via a printer server 15 or one or more intermediate devices.

[0013] Typically the printer information may be sent to the microblog server as text embedded in a message protocol supported by the microblog. The message protocol may for instance indicate if the text is to be published by the microblog or forwarded to another user as a private message.

[0014] The text which conveys a particular piece of printer information may be fixed, or alternatively may be user-configurable. For example, the text which is used to convey particular printer information may be stored in a file which is editable by a system administrator.

[0015] An example is given in Figure 4A. The left column of the table indicates the type of printer information which is to be conveyed, while the right column indicates the text which is sent to the microblog. For easy understanding, the left column is given in simple English in this example, but in certain implementations may instead contain particular printer codes or information in a printer language.

[0016] Figure 4A

[0017] In this example, the text to be distributed by the microblog (e.g. published on the microblog or forwarded to another user via a private message), are determined by a 'microblog application' and/or stored in a file on the printer or a printer server. It should be noted that the translation table is just an example of one implementation and may not be needed in all cases. For example, the text sent to the microblog may be predetermined by the printer or the code of the microblog application and sent to the microblog directly without translation.

[0018] Figure 4B shows a screen shot of a printer microblog according to one example. The microblog account may have a microblog account number or name, a personalized name and an avatar 150. A space 160 may also be provided for further information about the printer or related websites. A user may select or click on an icon 165 to register as a follower the microblog account. The screen area 170 contains a series of microblog posts (e.g. tweets) published by the printer. The microblog may provide further functionality to sort or filter these by type or date, read and unread or to display only public microblog posts, posts only viewable by registered followers or all posts etc.

[0019] In this example, post 171 is a printer status update indicating that the printer is out of paper. In this case it employs user customized text "Oh no I am OUT OF PAPER! !" to give a more friendly, informal feel to the microblog. In other contexts more formal language could be used; but the microblog application gives flexibility for the user to define the language used.

[0020] Post 172 is a print job notification indicating that a print job has been completed, which again has user customized text.

[0021] Post 173 is a printer sleep status update, while post 174 is a printer awake status update.

[0022] Post 175 is a scan job notification and includes a link to a location from which the scan job can be retrieved and viewed.

[0023] Post 176 is a printer status update indicating that new cartridges have been installed.

[0024] Screen area 180 gives some information about the printer microblog account. For example, the number of microblog posts is indicated at 181, the number of accounts which the printer is following (e.g. user microblog accounts which may send commands to the printer) is indicated at 182 and the number of followers (user microblog accounts registered to follow the printer) is indicated at 183.

[0025] Of course Figure 4B is just an example and many variations with different configurations and different information are possible.

[0026] One advantage of the microblog format is that it may easily be viewed by a mobile device. For example, it may be viewable through a webpage or through a special application on the client device (e.g. a smart phone 'app'). Further, the printer manufacturer need not design a new user interface from scratch or worry about compatibility of the printer management system with different client devices as these issues may be taken care of by the microblog provider or the microblog reader applications residing on client devices (e.g. an application on a mobile phone, computer etc for reading the microblog).

[0027] Privacy is an important issue for some users and it may be desirable to restrict the users to whom printer information is made available by the microblog. There may be various levels of privacy depending upon the printer information in question. Figure 5 is a flow chart showing an example of a method for determining how the printer information is communicated, depending upon the type of printer information in question.

[0028] At 210 it is determined if the printer information is of a public type which may be made available to all. The types of printer information falling into this category may be set by a system administrator and for example may include printer online status, cartridge status and paper status. If the printer information falls into this category then it is published by the microblog at 215 (e.g. as a 'post' or a 'tweet' associated with the microblog account and viewable on the webpage of that microblog account).

[0029] While the content published at 215 is notionally viewable by all; the microblog server may have a list blocking certain users.

[0030] If the printer information is not of a public type, then at 220 it is determined if the printer information is of a type that may be made available to all followers of the microblog account; ie. all users who registered with the microblog account as a 'follower' . The microblog service may automatically accept all users who register or may require confirmation from a system administrator on behalf of the printer which is being 'followed' . Restricting access in this way means that the information is only available to users who are both aware of the printer's microblog account and have successfully registered with it.

[0031] The types of printer information falling into this category may be set by a system administrator and may for example include a print job notification and a scan job notification. Printer information of this type is published on the microblog at 230, e.g. as a post or 'tweet' only viewable by users registered to follow the printer's microblog account.

[0032] If the printer information is not of a type that can be made available to all followers, then at 240 it is determined which user or users the information can be made available to and then sent to them as a private message at 250.

[0033] The type of printer information that may only be seen by certain users may be set by the system administrator. For example, confirmations that a command has been received or responses to a command requesting specific printer information may be sent by private message to the relevant user only (e.g. the user who sent the command), or only to a small set of users (e.g. system administrators) having the right to access this information.

[0034] The process shown in Figure 5 may be carried out by the microblog application (at the printer or printer server) and the relevant instruction sent to the microblog server - e.g. to publish content on the microblog or to forward a private message. Alternatively some or all of the decisions may be made by the microblog server. Further, while Figure 5 shows the printer information being determined by a sequence of decisions, this is an example only and the type may be determined by a single decision or by a different sequence.

[0035] Figure 6 shows the process from the point of view of the microblog server. At 310 the microblog server receives printer information from the printer or printer server. At 320 the printer information is published by the microblog (e.g. as a public post which is visible to all, or as a post which is visible only to registered followers), or sent as a private message to one or more users. Which of these options is chosen may be determined by the microblog application (at the printer or printer server) or by the microblog server itself or a combination thereof. The option may be chosen by a process such as that shown in Figure 5 for instance.

[0036] Communicating printer information with a microblog has several advantages. By publishing the printer information on a microblog, it may be viewed as a permanent (or semi-permanent) record. For example, if the printer is powered off, then a user can ascertain this by checking the microblog which may have posts indicating that the printer is powered off. In contrast, if a user were to query a printer directly (without a microblog) they would not receive a response when the printer was powered off and would not know whether this was because the printer was powered off or because of a communication error. Likewise if the printer is asleep, then the microblog may have a post indicating that the printer is asleep, or even the time at which it went to sleep and the time when it will wake up again.

[0037] Further, as mentioned above, the microblog is easy for mobile devices to access as it may be viewed through a webpage or through a microblog reading application on the mobile device.

[0038] In addition the software and user interface support for the microblog may be provided by the microblog provider. Thus in many cases the printer manufacturer need simply provide a printer (or printer server) that can communicate with the microblog in the specified format/protocol for the microblog which may enable the printer to communicate with many different types of client device.

[0039] Certain implementations, as described above, allow differentiation of users such that privacy can be maintained and the number of updates sent to any particular user reduced. Further, it is easy for a system administrator to set up a group of users who can view the printer information through the microblog. For example they can simply inform people in an office of the printer' s microblog account and people who regularly use the printer can register to follow the microblog account. This avoids, for example, sending emails with printer status updates to everyone in the office.

[0040] Figure 7 is a flow chart showing an example method for sending commands to the printer via a microblog. A command is an instruction for the printer to perform an operation or to provide printer information; for instance a command could be a status update, a wake up request, a sleep request, a power off request, a print request, a scan request, a copy request etc.

[0041] At 410 the microblog server receives a printer command sent to a microblog account by a client device. At 420 the microblog server checks whether the user sending the command is on a list of blocked users and if so the message containing the command is not forwarded and the process stops at 425.

[0042] Otherwise, at 430, the microblog server forwards the command to the printer or to a printer server associated with the printer.

[0043] At 440 the command is received by the printer or the printer server.

[0044] At 450 the printer or printer server checks if the client device has the right to send the command to the printer. Any commands issued by users not having a right to issue that type of command may be ignored or replied to with a message stating they do not have permission at 455.

[0045] There may be several levels of microblog user each with different rights with regard to interacting with the microblog. For instance, normal users registered to follow the microblog may not be permitted to issue commands. Users designated as a Commander may have permission to issue certain commands such as a status update request, a print request, scan request or a copy request. Users designated as a System Administrator may be permitted to issue power off and sleep or wake up commands. System Administrators may also be permitted to issue commands relating to user account management - e.g. to approve requests from users to follow the microblog, to appoint users as Commanders or System Administrators and to change user status and/or access rights. The above user groups are just examples and other groupings of command rights and user types could be used.

[0046] If the user has the right to send the command then at 460 the microblog application on the printer or print server translates the command into a printer understandable language and instructs the printer to processes the command. For example there may be a table which maps command text to commands in a language understood by the printer. The command text may be user definable, e.g. by a system administrator, to allow personalization of the printer. Once translated, the printer processes the command, e.g. by executing the relevant instructions.

[0047] While not necessary in all cases, after the printer executes the command, the printer or printer server may send a response to the microblog server at 470. For example the response may be a microblog post or a private message providing a requested status update or indicating that the command has been completed.

[0048] Fig. 8 shows an example of an apparatus 500, such as a printer or a printer server, which has a microblog application 20 for facilitating communication between a printer and a microblog. The apparatus comprises a processor 510 and memory 520 storing the microblog application 20. The microblog application 20 may comprise machine readable instructions which when executed by the processer implement the methods described herein, for instance the methods described with reference to the flow charts of Figures 3 and 5-7. The processor may be any suitable processor, for example a CPU, logic unit, ASIC, FPGA, processing unit etc. The memory may be any non-transitory storage medium and may for instance be in the form of volatile or non- volatile storage such as a ROM, whether erasable or rewritable or not, RAM, memory chips, device or integrated circuits etc. The memory and processor may be single units or distributed over several units.

[0049] While the memory and processor are shown as separate units in Figure 8, in some implementations they may be combined as one functional unit. Indeed, the microblog application may be implemented as any form of hardware or software module or a combination of hardware and software modules.

[0050] The memory may store a translation table 530 for converting printer information, such as a printer status update or notification, into user configurable text for conveying the printer information (as discussed above in relation to Figure 4A). The same, or a different, translation table stored in the memory may contain information for converting command text sent from the microblog into a command in a language understandable by the printer. The command text may be user definable. Alternatively the translation function may be embedded into the machine readable instructions of the microblog application itself. The memory may also store a user list 540 defining which users have permission to issue which commands and/or which users have permission to see which types of printer information.

[0051] Figure 9 shows an example of a microblog server 15. The microblog server has a processor 610, a memory 620 and an I/O module 630 for communicating with client devices. The memory stores one or more files 622 containing the contents of the microblog accounts residing on the microblog server and a microblog control module 624 for controlling operation of the microblogs, publishing of posts, forwarding of private messages and responding to microblog related requests from client devices etc. The microblog control module 624 may comprise machine readable instructions which are executable by the processor. Further, the memory may store a user list or user lists 626 of users registered to follow each microblog account. In some cases the memory may also have a list of users blocked from accessing one or more microblog accounts. The memory may be any non-transitory machine readable memory, for instance a ROM, ROM, EEPROM, hard disk, tape device etc. While one memory is illustrated in Figure 9 it is to be understood that there may be several memories and the above described contents may be distributed across the several memories.

[0052] In the above examples, the microblog application on the printer or printer server translated commands from users into a language understandable by a printer. However, in alternative implementations the microblog server itself may have functionality for translating commands into a language understandable by the printer. For example a memory of the microblog server may store a translation table for translating predefined commands into printer understandable language and machine readable instructions executable by a processor of the server to translate received commands and forward them to the printer or a print server associated with the printer.

[0053] Likewise, in the examples described above the user access and command rights were controlled by the microblog application 20 on the printer or printer server. However, in alternative implementations some or all of these functions may be carried out by the microblog server 15. Thus in some implementations the user list 626 on the microblog server may define the access and/or command rights accorded to different users. Likewise, while not shown in Figure 9, in some implementations a memory of the microblog server may store a translation table, such as the one described above in relation to Figure 4A and instructions for translating information sent by a printer into user definable text for publication or forwarding by the microblog.

[0054] All of the features disclosed in this specification (including any

accompanying claims, abstract and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or steps are mutually exclusive. [0055] Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features.

Claims

WHAT IS CLAIMED IS:

1. An apparatus comprising a processor and a memory storing a microblog

application, the microblog application comprising instructions executable by the processor to send printer information to a microblog.

2. The apparatus of claim 1 wherein the printer information is a printer online status, printer cartridge status, print job notification, fax job notification, copy job notification, scan job notification or a printer paper status.

3. The apparatus of claim 1 wherein the apparatus is a printer and wherein the instructions to send printer information are instructions to send the printer information to a microblog account associated with the printer.

4. The apparatus of claim 1 wherein the apparatus is a print server associated with a printer and wherein the instructions to send printer information are instructions to send the printer information to a microblog account associated with said printer.

5. The apparatus of claim 1 wherein the instructions to send printer information are instructions to publish the printer information on the microblog.

6. The apparatus of claim 5 wherein the instructions to publish the printer

information are instructions to publish the printer information such that only registered followers of the microblog can view the printer information.

7. The apparatus of claim 1 wherein the instructions to send printer information to a microblog comprise instructions to send a private message to a follower of the microblog in response to a command from the follower.

8. The apparatus of claim 1 wherein the microblog application allows the printer information to be sent as user configurable text.

9. The apparatus of claim 1 wherein the microblog application comprises

instructions to process a command sent to the printer by a user of the microblog.

10. An apparatus comprising a processor and a memory storing a microblog

application, the microblog application comprising instructions executable by the processor to process a command sent to the printer by a microblog server.

11. The apparatus of claim 10 wherein the apparatus is a printer or a printer server.

12. The apparatus of claim 10 wherein the instructions comprises instructions to verify that the user has the right to issue the command.

13. The apparatus of claim 10 wherein the instructions comprise instructions to convert the received command into a printer command in a language understandable by the printer.

14. The apparatus of claim 10 wherein the instructions comprise instructions to send a message or status update confirming receipt and/or completion of the command.

15. The apparatus of claim 10 wherein the command is a status update request, a wake up request, a sleep request, a power off request, a print request, a scan request, fax request or a copy request.

16. The apparatus of claim 10 wherein said microblog application has access to a list of users that are permitted to send commands to the printer via the microblog service and wherein said microblog application comprises instructions to check that a user from whom a command has been received has the right to send the command.

17. A microblog server having a microblog account associated with a printer, said microblog server having a processor and a memory storing machine readable instructions executable by the processor to translate a command received from a microblog user into language understandable by a printer and to forward the translated command to a printer or printer server.

18. The microblog server of claim 17 wherein a memory of the microblog server stores a list of users subscribed to follow the printer via the microblog.

19. The microblog server of claim 17 wherein a memory of said microblog server stores a list of users, said list defining several categories of users having different access rights.

20. The microblog server of claim 17 wherein said processor has access to a list of microblog users having the right to send a command to the printer and said machine readable instructions comprise instructions to check whether a user sending a command to a printer or printer server via the microblog server has the right to send the command.

21. A microblog server having a microblog account associated with a printer, said microblog server having a processor and a memory storing machine readable instructions executable by the processor to translate printer information received from a printer into text and to publish said text as a post on said microblog account or forwarding said text as a private message to a microblog user.