Printing apparatus, method for controlling a printing apparatus, printing system, and program

Abstract

To provide a printing device that can suppress ink leakage during packing work or transportation when a user transports a printing device and leakage of user setting information retained in a printing device after cancellation of service contract for the printing device, and to provide a method for controlling a printing device and a program.SOLUTION: A printing device executes a transportation preparatory operation that is a preparatory operation to be executed before transportation on the basis of cancellation of contract by a user.SELECTED DRAWING: Figure 14

Description

Technical Field

[0006] , , , ,

[0001] The present invention relates to a printing apparatus, a control method for the printing apparatus, a printing system, and a program.

Background Art

[0002] In recent years, in a printing apparatus, a service is provided in which, by concluding a contract, a cartridge filled with a recording material according to the usage situation is delivered to the user. Patent Document 1 discloses a method for clarifying the timing of completion of cancellation of a service contract for a printing apparatus.

[0003] When canceling a service contract for a printing apparatus, there is a service form in which the user must return the printing apparatus. When transporting the printing apparatus upon return, as a transport preparation operation, in order to prevent ink from leaking to the outside, the ink in the ink flow path including the recording head is removed in advance, or in order to prevent leakage of user setting information in the printing apparatus, it is necessary to erase the user setting information.

[0004] In Patent Document 1, the server receives a response indicating that the cartridge has been changed to a state where it cannot be used in the printing apparatus, thereby clarifying the timing of completion of cancellation of the service contract.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, since the printing apparatus described in Patent Document 1 does not confirm whether the transport preparation operation has been performed, if the user has not performed the transport preparation operation, there was a risk that ink may leak when the printing apparatus is transported, or that user setting information may remain inside the printing apparatus, leading to information leakage.

[0007] Therefore, the present invention provides a printing device, a control method for the printing device, and a program that can suppress packaging work, ink leakage during transportation, and leakage of user setting information inside the printing device when a user transports the printing device after the termination of a service contract for the printing device. [Means for solving the problem]

[0008] Therefore, the printing apparatus of the present invention is a printing apparatus provided to a user based on a contract and returned by the user by transport after the termination of the contract, and is equipped with control means that controls the execution of transport preparation operations, which are preparatory operations performed before transport and include a blocking operation to prevent ink leakage, based on the user's termination of the contract. The control means then performs a reset operation to reset the user's settings information after the blocking operation. It is characterized by the following: [Effects of the Invention]

[0009] According to the present invention, it is possible to provide a printing device, a control method for the printing device, a printing system, and a program that can suppress packaging work, ink leakage during transportation, and leakage of user setting information within the printing device when a user transports the printing device after the termination of a service contract for the printing device. [Brief explanation of the drawing]

[0010] [Figure 1] This is a diagram showing the configuration of a printing system. [Figure 2] (a) through (c) are diagrams showing printers. [Figure 3] This is a block diagram showing the printer configuration. [Figure 4] This diagram shows the module configuration of the software that runs on the printer. [Figure 5]It is a block diagram showing the configuration of a cloud server. [Figure 6] It is a diagram showing the module configuration of software operating on a cloud server. [Figure 7] (a) and (b) are diagrams showing the WebAPI data structure of a cloud server. [Figure 8] (a) to (e) are diagrams showing the data structure of records. [Figure 9] It is a flowchart showing the request processing of a cloud server. [Figure 10] It is a flowchart showing the processing of a cloud server when receiving a request. [Figure 11] It is a flowchart showing the processing of a cloud server when receiving a job status notification request. [Figure 12] It is a flowchart showing the processing content of a cloud server when receiving a printer status notification request. [Figure 13] It is a flowchart showing the content of transport mode processing (transport preparation operation). [Figure 14] It is a flowchart showing the content of service contract cancellation processing. [Figure 15] It is a flowchart of the initialization process executed by a printer. [Figure 16] It is a schematic diagram showing the display screen displayed on the operation panel of a printer. [Figure 17] [[ID=3)6]]It is a flowchart showing the initialization process executed by a printer. [Figure 18] It is a schematic diagram showing the display screen displayed on the operation panel of a printer.

Embodiments for Carrying Out the Invention

[0011] (First Embodiment) Hereinafter, the first embodiment of the present invention will be described with reference to the drawings.

[0012] FIG. 1 is a diagram showing the configuration of a printing system 100 to which the present embodiment is applicable. The system 100 includes a cloud server 200 and a device group 400 connected by a local area network 102 and the Internet 104. The devices 400 include various devices capable of network connection. The various devices include, for example, a smartphone 500, a printing device (hereinafter also referred to as a printer) 300, a client terminal 401 such as a personal computer or a workstation, a digital camera 402, and the like. Note that the device group 400 is not limited to these types, and may include, for example, home appliances such as a refrigerator, a television, and an air conditioner.

[0013] The devices 400 are interconnected by the local area network 102 and can be connected to the Internet 104 via a router 103 installed in the local area network 102. Here, the router 103 is illustrated as a device connecting the local area network 102 and the Internet 104, but it is also possible to provide a wireless LAN access point function constituting the local area network 102. In this case, in addition to connecting to the router 103 by a wired LAN, each device 400 can be configured to connect to an access point by a wireless LAN and participate in the local area network 102. For example, the printer 300 and the client terminal 401 can be configured to be connected by a wired LAN, and the smartphone 500 and the digital camera 402 can be configured to be connected by a wireless LAN.

[0014] Each device 400 can communicate with the cloud server 200 via the internet 104 connected through the router 103. Furthermore, each device 400 can communicate with each other via the local area network 102. The smartphone 500 and the printer 300 can also communicate via short-range wireless communication 101. This short-range wireless communication 101 could utilize wireless communication compliant with Bluetooth® or NFC standards. The smartphone 500 is also connected to a mobile phone network 105, and can communicate with the cloud server 200 via this mobile phone network 105.

[0015] Note that this configuration is merely an example in this embodiment, and the effect will not change even if a different configuration is used. For example, although an example is shown in which router 103 has access point functionality, the access point may be made up of a different device from router 103.

[0016] Figure 2(a) is a perspective view showing the external appearance of the printer 300, Figure 2(b) is a view showing the top view of the printer 300, and Figure 2(c) is a horizontal cross-sectional view of the printer 300 as seen from the paper output side.

[0017] In this embodiment, the printer 300 can, based on the service usage agreement, issue an ink delivery request when ink delivery is necessary depending on the status of the printer 300, manage the number of pages printed by the printer 300, and restrict printing to a maximum limit. Furthermore, after the contract is terminated, the user returns the printer 300 by transport.

[0018] In this embodiment, a multifunction printer (MFP) that also functions as a scanner and other functions will be used as an example of the printer 300. The document tray 301 is a transparent glass-like tray used when placing a document on it to scan it. The document tray pressure plate 302 is a cover that presses the document against the document tray to prevent it from lifting when scanning, and also prevents external light from entering the scanner unit. The paper insertion slot 303 is an insertion slot for inserting paper of various sizes. Paper inserted into the paper insertion slot 303 is transported to the printing section one sheet at a time, and after the desired printing is performed, the paper is discharged from the paper output slot 304.

[0019] An operation panel 305 and a short-range wireless communication unit 306 are located above the document pressure plate 302. The operation panel 305 consists of a touch panel type liquid crystal display that can display various information and allow the user to input operations to the printer 300. The printer 300 is a printer that records by ejecting liquid (hereinafter also referred to as ink) from a print head 602, and the built-in ink tank 601 and the print head 602 are connected via an ink tube (connection part) 603. Ink is stored in the built-in ink tank 601, and by opening the tank valve 608, the ink in the built-in ink tank 601 is supplied to the print head 602 via the ink tube 603. The ink supplied to the print head 602 is ejected from the print head 602 based on the recording data received by the print head 602. Furthermore, by closing the tank valve 608, the supply of ink from the built-in ink tank 601 to the print head 602 can be stopped, preventing ink from leaking from the print head 602.

[0020] The printer 300 supports the carriage 605, which carries the print head 602, with the carriage support section 604, and moves the carriage 605 from side to side along the carriage support section 604, while simultaneously ejecting ink droplets from the print head 602 to record on the recording paper. In this embodiment, a serial printer in which the carriage 605 moves along the support section 604 is described as an example, but a line printer or page printer may also be used. Furthermore, in this embodiment, ink is supplied to the print head 602 from the built-in ink tank 601 via the ink tube 603, but the ink tank may be inserted directly into the print head 602 to supply ink.

[0021] The cap 606 can protect the print head 602 from drying out by sealing it tightly against the print head 602 and excluding it from the atmosphere. When the carriage 605 is positioned on the cap 606, raising the convex carriage lock pin 607 engages the carriage lock pin 607 with a concave member (not shown) on the back of the carriage 605. In this state, the tight seal between the cap 606 and the print head 602 can be maintained even if the housing is tilted or subjected to vibration. Furthermore, by sealing the cap 606 tightly against the print head 602, ink that has become unable to be ejected due to surface concentration or solidification is discharged, bringing fresh ink to the surface, making it possible to eject ink droplets from the print head 602.

[0022] The short-range wireless communication unit 306 is a unit for short-range wireless communication and can communicate with the short-range wireless communication unit of a communication partner within a predetermined distance. The wireless LAN antenna 307 has an embedded antenna for connecting to the local area network 102 and communicating using wireless LAN.

[0023] Figure 3 is a block diagram showing the configuration of the printer 300. The printer 300 comprises a main board 310 that controls the entire device, a wireless LAN unit 308, and a short-range wireless communication unit 306. The microprocessor-type CPU 311 located on the main board 310 operates according to the control program stored in the ROM-type program memory 313 connected via the internal bus 312, and the contents of the RAM-type data memory 314.

[0024] The CPU 311 controls the scanner mechanism control circuit 315 to read the document and store it in the image memory 316 in the data memory 314. The CPU 311 also controls the printing mechanism control circuit 317 to print the image from the image memory 316 in the data memory 314 onto a recording medium. The CPU 311 communicates wirelessly with other communication terminal devices via wireless LAN by controlling the wireless LAN unit 308 through the wireless LAN communication control unit 318. Furthermore, the CPU 311 can detect connections with other short-range wireless communication terminals and send and receive data with other short-range wireless communication terminals by controlling the short-range wireless communication unit 306 via the short-range wireless communication control circuit 320. The CPU 311 can display the status of the printer 300 and function selection menus on the operation panel 305 and accept operations from the user by controlling the operation control circuit 320.

[0025] Figure 4 shows the module configuration of the software running on the printer 300. The software 1300 running on the printer 300 runs on the embedded control operating system (OS) 1301. The modules are broadly classified into the system control layer 1310, the job management layer 1320, the middleware layer 1330, and the application layer 1340. The embedded control OS 1301 is the operating system (OS) that governs the basic operation of the printer control software 1300, and generally a real-time OS with excellent responsiveness is used. The system control layer 1310 is a group of modules that mainly govern the hardware control of the printer 300. The print control module 1311 is a control module that controls the print mechanism control circuit 317 to execute the printing operation of the printer 300.

[0026] The reading control module 1312 is a control module that controls the scanner mechanism control circuit 315 to perform the scanning operation of a document placed on the document glass 301. The panel control module 1313 is a control module that controls the display on the printer 300's operation panel 305 and detects various key operations. The memory management module 1314 is a control module that manages the dynamic allocation of data memory 341 and image memory 316, etc.

[0027] The power control module 1315 is a control module that controls the power supply of the printer 300, supplying the necessary power to each hardware block for operation and controlling power saving mode. The proximity wireless communication control module 1316 is a control module that controls the proximity wireless communication unit 306 to communicate with terminal devices such as smartphones 500. The network communication control module 1317 is a control module that controls the wireless LAN unit 308 to perform physical layer communication control for LAN communication with external devices.

[0028] The job management layer 1320 is a group of modules that utilize the system control layer 1300 to perform various operations, such as allocating hardware resources, performing mutual exclusion, and scheduling, in response to job execution requests from higher layers.

[0029] The middleware layer 1330 is located between the application layer 1340 and the job management layer 1320, and it brings together a group of modules that are commonly used by multiple functional modules in the application layer 1340.

[0030] The application framework 1331 is a framework module commonly used when requesting job execution from the application layer 1340 to the job layer 1320. The network protocol stack 1332 is a module for performing communication in accordance with various network protocols such as HTTP and TCP / IP. The cryptographic processing module 1333 is a module for performing encryption and decryption processing required for network communication, etc. The web server module 1334 is a module for operating the printer 300 as a web server in order to deliver remote UI content. The application layer 1340 is a group of applications that realize the various functions of the printer 300.

[0031] The copy application 1341 is an application module for performing copy operations, such as scanning a document and printing it. The driver print application 1342 is an application module for receiving and executing jobs from the printer driver of the smartphone 500 or client terminal device 401. Jobs from the driver include print jobs that perform printing operations, scan jobs that scan a document and output image data, and maintenance jobs that exchange information with external devices to configure and manage the printer 300. The standard print application 1343 is an application module for receiving and executing jobs from the standard print service of the smartphone 500's system.

[0032] Jobs from the standard print service include print jobs that perform printing operations and scan jobs that read documents and output image data. However, since the standard print service is provided by smartphone manufacturers and standard OS vendors, it has the limitation that it cannot perform specific settings or management for printer models from individual manufacturers. The remote UI module 1344 is a module that provides the remote UI functions of the printer 300 to external devices using the web server module 1334.

[0033] The remote UI module 1344 enables the configuration and management of the printer 300. In particular, with the printer 300 shown in this embodiment, the information that can be displayed and configured on the operation panel 305 is limited, so the remote UI module 1344 is used for more detailed configuration and management. Also, if a dedicated driver is not available for the smartphone 500 or client terminal device 401, only the standard printing service will be available, so the use of the remote UI module 1344 is essential for detailed configuration and management.

[0034] Figure 5 is a block diagram showing the configuration of the cloud server 200. The cloud server 200 comprises a main board 210 that controls the entire device, a network connection unit 201, and a hard disk unit 202. The microprocessor-type CPU 211 located on the main board 210 operates according to the control program stored in the program memory 213, which is connected via the internal bus 212, and the contents of the data memory 214. The CPU 211 connects to a network such as the Internet 104 and communicates with other devices by controlling the network connection unit 201 via the network control circuit 215. The CPU 211 can read and write data to the hard disk unit 202, which is connected via the hard disk control circuit 216. The hard disk unit 202 stores the operating system and control software for the cloud server 200 that are loaded into the program memory 213, as well as various other data. A GPU 217 is connected to the main board 210, and it is possible to have it perform various calculation processes on behalf of the CPU 211.

[0035] Figure 6 shows the module configuration of the software running on the cloud server 200. The software 1200 running on the cloud server 200 runs on the operating system (OS) 1201. Each module is broadly classified into a data storage layer 1210, a middleware layer 1220, and an application layer 1230. Each module, stored in the hard disk unit 202, is loaded into the program memory 213 and data memory 214 as needed and executed.

[0036] The data storage layer 1210 consists of a database and file storage that stores and manages information used by various services. The database 1211 stores data from relational databases managed by the database management system 1223. The file storage 1212 stores files managed by the file system 1224. Examples of files stored in the file storage 1212 include image data for print jobs to be printed by the printer 300 and image data scanned by the printer 300. The middleware layer 1220 is located below the application layer 1230 and is a collection of modules commonly used by multiple application modules in the application layer 1230.

[0037] The network protocol stack 1222 is a module for performing communication in accordance with various network protocols such as HTTP and TCP / IP. The WebAPI 1221 is a module for performing WebAPI processing for services provided by the cloud server 200. The WebAPI 1221 is defined as a data structure exchanged using the HTTP protocol. The WebAPI 1221 uses the network protocol stack 1222 to receive HTTP requests and, depending on the content of those requests, requests processing from the various service modules 1231 to 1235 in the application layer 1230. The WebAPI 1221 also receives the processing results from the requested modules and uses the network protocol stack 1222 to return an HTTP response to the requester.

[0038] The database management system 1223 is a module that provides management functions for accessing information in the database 1211 from various services 1231 to 1235 in the application layer 1230. The file system 1224 is a module that provides management functions such as reading and writing files to the file storage 1212 from various services 1231 to 1235 in the application layer 1230.

[0039] The application layer 1230 is a group of services that provide various functions of the cloud server 200. The printer management service 1231 provides management functions related to the information of registered printers 300. The functions provided by the printer management service 1231 include the following: receiving and managing status notifications from the printer 300; issuing ink delivery requests when ink delivery is necessary based on the status of the printer 300 according to the service usage agreement; and managing the number of pages printed by the printer 300 and restricting printing to the upper limit based on the service usage agreement.

[0040] The account management service 1232 provides management functions for information related to registered service users. The functions provided by the account management service 1232 include the following: managing information about service users; managing the amount of data stored in the file storage 1212 based on the service usage agreement and limiting the storage of data exceeding the upper limit, etc. The job management service 1233 provides management functions for information related to jobs that service users use to perform printing, scanning, etc. using the registered printer 300. The functions provided by the job management service 1233 include the following: receiving job execution requests from service users, spooling job data to file storage, and notifying the printer 300; receiving inquiries from the printer 300 and returning job information; receiving and managing job status notifications from the printer 300 and deleting completed job data from file storage, etc.

[0041] Contract management service 1234 provides management functions for service usage contract information related to the use of printer 300 registered by service users. Functions provided by contract management service 1234 include managing service usage contract information. Ink delivery management service 1235 provides management functions for information related to the delivery of ink, a consumable used in printer 300, from the service provider to the service user, based on the service usage contract. Functions provided by ink delivery management service 1235 include the following: receiving ink delivery requests from printer management service 1231 and carrying out the necessary ink delivery procedures to service users; and managing information related to ink delivery.

[0042] In this embodiment, it is assumed that the cloud server 200 is built as a single physical server, but the above-mentioned modules may be configured to be distributed across two or more physical servers. For example, each of the application layer services 1231 to 1235 may be run on a different physical server. Alternatively, the application server providing these services, the database 1211, and the file storage 1212 may be run on different physical servers.

[0043] Figures 7(a) and 7(b) show the Web API data structure of the cloud server 200. Figure 7(a) shows the data structure of API request 3000. API request 3000 is sent from printer 300 to cloud server 200 as an HTTP request. API request 3000 is written entirely as text data, and its structure is determined by lines separated by newline characters. The first line of API request 3000 is request line 3001. Request line 3001 begins with the HTTP method being requested, followed by the URI (Universal Resource Indenter) that identifies the requested resource, the protocol version notation, and ends with a newline character.

[0044] Here, the URI is formed by concatenating "base," which is the URI indicating the location of the cloud server 200, with a string indicating the name of the API request. The lines following request line 3001 until the first blank line appear constitute the request header 3002. The request header 3002 is used to pass additional information about the request and the HTTP client that made the request to the HTTP server that received the request. Here, as an example, the name string "userid:" is followed by a string 3004 that identifies the user, and the name string "printerid:" is followed by a string 3005 that identifies the printer.

[0045] Furthermore, other parameters can be written from line 3006 onwards. The lines after the blank line following the request header 3002 are called the message body 3003. The message body 3003 describes the data itself that is passed from the HTTP client to the HTTP server, depending on the type of HTTP method of the request. Note that depending on the type of API, the message body 3003 may not exist.

[0046] Figure 7(b) shows the data structure of the API response. This data structure is used to send the response from the cloud server 200 to the printer 300 in response to API request 3000 as an HTTP response. The API response 3010 is written entirely as text data, and its structure is defined in lines separated by newline characters. The first line of the API response 3010 is the status line 3011. The status line 3011 begins with the protocol version, followed by a numerical status code and a string, and ends with a newline character.

[0047] The status header 3012 consists of lines following status line 3011 until the first blank line appears. The status header 3012 is used to pass additional information to the HTTP client that made the request, such as the status and data passed in the message body 3013 included in the HTTP response. In this example, the name string "userid:" is followed by a string 3014 that identifies the user, and the name string "printerid:" is followed by a string 3015 that identifies the printer. Further parameters can be written from line 3016 onwards.

[0048] The lines following the status header 3012 (after the blank line) are called the message body 3013. The message body 3013 contains the data itself that is passed from the HTTP server to the HTTP client. Here, as an example, we show the case where API return data 3017 is stored, but depending on the type of API, the message body 3013 may not exist.

[0049] Figures 8(a) to 8(e) show the data structure of records stored in the database of the cloud server 200. The data structure of each table is defined as a collection of multiple attribute values. Attributes include a primary key that uniquely identifies the record stored in the table and a foreign key that references records in other tables. Here, the data structure is divided into upper and lower boxes, with the primary key in the upper box and attributes including foreign keys in the lower box.

[0050] Figure 8(a) shows the data structure of a user information record 3100 stored in the user information table. User ID 3101 is the primary key, which uniquely identifies the desired record from among multiple records stored in the user information table. User details 3102 stores attribute information such as the user's address, name, and age. Current period upper limit storage capacity 3103 stores the upper limit storage capacity for the user in the current period. Current period used storage capacity 3104 stores the storage capacity used by the user in the current period. The current period is a management period determined based on the contract, and is managed based on a predetermined period such as one month or one year.

[0051] The current period limit storage capacity 3103 is set to the storage capacity limit value 3137 of the contract information record 3130 described later, for each management period, but can be increased or decreased within the period depending on the service usage. This makes it possible to allow users to temporarily exceed the storage capacity stipulated in the contract. If the current period used storage capacity 3104 exceeds the current period limit storage capacity 3103, the user will no longer be able to save any further data to the cloud server 200. The currently held points 3105 stores the point information held by the user. Points are awarded according to the number of pages printed and ink consumption, and users can use the awarded points to receive various services. For example, they can be used to pay for charges related to the contract or to pay for goods sold by the service provider.

[0052] Figure 8(b) shows the data structure of a printer information record 3110 stored in the printer information table. The printer ID 3111 is the primary key, which uniquely identifies the desired record from among multiple records stored in the printer information table. The printer status 3112 stores information such as whether or not an error has occurred in the printer 300, and if an error has occurred, the type of error. The ink level 3113 stores information about the remaining ink level in the printer 300. If the ink level falls below a predetermined amount, a warning is issued or the operation stops as an error.

[0053] The current print count 3114 stores the number of pages printed by the printer 300 during the current period. The current print limit 3115 stores the maximum number of pages that can be printed by the printer 300 during the current period. The current print limit 3115 is set for each management period by the value of the print limit 3136 in the contract information record 3130 described later, but it can be increased or decreased within the period depending on the service usage. This makes it possible to allow users to temporarily exceed the number of pages stipulated in the contract. If the current print count 3114 exceeds the current print limit 3115, the printer 300 will no longer be able to perform any further printing.

[0054] Figure 8(c) shows the data structure of a job information record 3120 stored in the job information table. The job ID 3121 is the primary key, which uniquely identifies the desired record from among multiple records stored in the job information table. The user ID 3122 is a foreign key, which identifies the user who requested the job and is used to retrieve information about that user from the user information table. The printer ID 3113 is a foreign key, which identifies the printer 300 on which the job should be executed and is used to retrieve information about that printer from the printer information table.

[0055] The job status information 3124 stores the current status information for the job in question. The status can take values ​​such as "Waiting to print," "Printing," "Printing complete," or "Alternative print completed." The print parameter settings 3125 stores parameter information that specifies the printing conditions to be used for the job in question. This can include information such as paper size, paper type, and ink type to be used. The print job data 3126 stores information that identifies the print image data to be printed for the job in question. This consists of information such as the location of the job stored in the file storage 1212. The reprint flag 3117 indicates whether the job in question is subject to alternative printing. It is set when reprinting is necessary after alternative printing, and is cleared when reprinting is complete.

[0056] Figure 8(d) shows the data structure of contract information record 3130 stored in the contract information table. Contract ID 3131 is the primary key, which uniquely identifies the desired record from among multiple records stored in the contract information table. User ID 3132 is a foreign key, which identifies the user covered by the contract and is used to retrieve information about that user from the user information table. Printer ID 3133 is a foreign key, which identifies the printer covered by the contract and is used to retrieve information about that printer from the printer information table.

[0057] Contract type 3134 stores the type of the relevant contract. Contract types include usage-based contracts, flat-rate contracts, and delivery contracts. A usage-based contract is a contract where charges are based on the amount of printer usage. That is, charges are based on the number of pages printed or the amount of consumables consumed. A flat-rate contract is a contract where a fixed usage fee is charged at predetermined intervals, regardless of printer usage. This contract may have a limit on the number of pages printed at predetermined intervals or a limit on the amount of print data stored on the cloud server 200, allowing unlimited use within those limits for a flat rate. A delivery contract is a contract where consumables such as ink are automatically ordered and delivered when they run low, and the user pays the purchase price according to the ordered consumables. Note that the contract types described here are merely examples, and other usage forms may be provided by contract.

[0058] Contract details 3135 stores detailed information about the contract in question. This may include information such as the contract period, terms of use, and amount. Print limit 3136 stores the contractual maximum number of prints for the printer 300 related to the contract. Storage capacity limit 3137 stores the contractual maximum storage capacity for the user related to the contract.

[0059] Figure 8(e) shows the data structure of a delivery information record 3140 stored in the delivery information table. The order ID 3141 is the primary key, which uniquely identifies the desired record from among multiple records stored in the delivery information table. The contract ID 3142 is a foreign key, which identifies the contract on which the delivery is based and is used to reference information about that contract from the contract information table. The order details 3143 stores detailed information about the relevant delivery, including information such as ink type and quantity. The order date 3144 stores the date on which the delivery was arranged. The expected arrival date 3145 stores the date on which the delivered goods are expected to arrive at the user's location.

[0060] Figure 9 is a flowchart showing the request processing of the cloud server 200. This request processing is executed by the CPU 211 of the cloud server 200 each time the cloud server 200 receives a Web API request from an external source. The request processing of the cloud server 200 in this embodiment will be described below using a flowchart. The series of processes shown in Figure 9 are performed by the CPU 211 of the cloud server 200 expanding the program code stored in the program memory 213 into the data memory 214 and executing it. Alternatively, some or all of the functions of the steps in Figure 9 may be implemented by hardware such as an ASIC or electronic circuit. The symbol "S" in the description of each process means that it is a step in the flowchart.

[0061] When request processing begins, the CPU 211 of the cloud server 200, upon receiving a Web API request, determines the type of the received Web API request in S901. The following steps are then performed according to the type of Web API request received.

[0062] If the request in S901 is for job execution from a user terminal, CPU211 proceeds to S902 and performs the job execution process described later. If the request in S901 is for job inquiry from printer300, CPU211 proceeds to S903 and sends job data if there is a job for printer300. Here, the job data may be sent by returning the spooled job data itself as the WebAPI response, or by returning a URL pointing to the spooled job data as the response.

[0063] If the request in S901 is a job status notification from printer 300, CPU 211 proceeds to S904 and performs the job status notification processing described later. If the request in S901 is a printer status notification from printer 300, CPU 211 proceeds to S905 and performs the printer status notification processing described later. If the request in S901 is a delivery status inquiry, CPU 211 proceeds to S906, retrieves the corresponding delivery information record 3140 from database 1211 and returns it as a WebAPI response.

[0064] If the request in S901 is a contract status inquiry, CPU211 proceeds to S907, retrieves the corresponding contract information record 3130 from database 1211, and returns it as a Web API response. If the request in S901 is a contract change notification, CPU211 proceeds to S908, and updates the contract information details 3135 of contract information record 3130 stored in database 1211. If the request in S901 is any other request, CPU211 proceeds to S909 and performs the appropriate processing, but a detailed explanation is omitted here.

[0065] Figure 10 is a subflow of the job execution process in S902 of Figure 9, and is a flowchart showing the processing content of the cloud server 200 when a request is received. This process is executed by the CPU 211 of the cloud server 200 when the request is a job execution from a user terminal.

[0066] When the cloud server 200 receives a job execution request, the CPU 211 determines in S1001 whether the number of printed pages for the current period exceeds the maximum number of pages. This is done by referring to the printer information record 3110 to determine whether the current number of printed pages 3114 exceeds the current maximum number of printed pages 3115. If the current number of printed pages 3114 does not exceed the current maximum number of printed pages 3115, the CPU 211 proceeds to S1002 and generates a new job. If the current number of printed pages 3114 exceeds the current maximum number of printed pages 3115 in S1001, the CPU 211 proceeds to S1005, returns a limit exceeding error as a WebAPI response, and terminates processing.

[0067] After generating a new job in S1002, in S1003, the CPU 211 spools the data of the received job to the file storage 1212. Then, in S1004, the CPU 211 notifies the printer 300 of the registration of the new job and terminates the job execution process.

[0068] Figure 11 is a subflow of the job status notification process in S904 of Figure 9, and is a flowchart showing the processing content of the cloud server 200 when a job status notification request is received. This process is executed by the CPU 211 of the cloud server 200 when the request is a job status notification from the printer 300.

[0069] When the cloud server 200 receives a job status notification request, the CPU 211 updates the information in the corresponding job information record 3120 in the database 1211 in S1101. Subsequently, in S1102, the CPU 211 refers to the notified job status information and determines whether the notification indicates that the job has completed successfully. If it has completed successfully, the CPU 211 proceeds to S1103 and deletes the job data for the corresponding job spooled in the file storage 1212. On the other hand, if it has not completed successfully in S1102, the CPU 211 determines in S1104 whether the reprint flag 3127 for the corresponding job information record 3120 is set.

[0070] If the reprint flag 3127 is set, the CPU 211 proceeds to S1105 and holds the job data for reprinting. The reprint jobs held here will be executed again after consumables such as ink and paper are replenished and the system returns to its normal state.

[0071] Figure 12 is a subflow of the printer status notification process in S905 of Figure 9, and is a flowchart showing the processing content of the cloud server 200 when a printer status notification request is received. This process is executed by the CPU 211 of the cloud server 200 when the request is a printer status notification from the printer 300.

[0072] When the cloud server 200 receives a printer status notification request, the CPU 211 updates the information in the corresponding printer information record 3110 in the database 1211 in S1201. Then, in S1202, the CPU 211 determines whether the ink level 3113 has changed to a predetermined amount or less. This can be done by comparing the ink level 3113 in the printer information record 3110 before the update with the ink level 3113 in the printer information record 3110 after the update, and determining whether the ink level 3113 has changed from above a predetermined amount to below a predetermined amount. Here, the predetermined amount may be a fixed amount that is set in advance, but it may also be configured to vary depending on the user or contract, or it may be configured to be set by the user.

[0073] In S1202, if the CPU 211 determines that the ink level has fallen below a predetermined amount, it proceeds to S1203 and requests ink delivery from the ink delivery management service 1235. On the other hand, if the ink level is not below a predetermined amount in S1202, the CPU 211 determines in S1204 whether the ink has been replenished. This is done by comparing the ink level 3113 in the printer information record 3110 before the update with the ink level 3113 in the printer information record 3110 after the update, and determining whether the ink level 3113 has changed from below a predetermined amount to above a predetermined amount. If it is determined that the ink has been replenished, the CPU 211 proceeds to S1205 and determines whether there are any jobs specified for reprinting for the printer 300. If there are reprint jobs, the CPU 211 proceeds to S1206 and notifies the printer 300 of the reprint jobs and terminates processing. If it is determined in S1204 that the ink has not been replenished, or if there are no reprint jobs in S1205, processing also terminates.

[0074] Figure 13 is a flowchart showing the contents of the transport mode processing (transport preparation operation) for changing the printer 300 from normal print mode to transport mode. Here, transport mode is a state in which the printer 300 has performed preparation operations for transport, and is distinguished from normal print mode, which is used for normal printing. In normal print mode, ink can be ejected from the print head 602, and the carriage 605 can move left and right along the carriage support part 604. In transport mode, the supply of ink to the print head 602 is stopped by closing the valve, the ink from the print head 602 is discharged, and the carriage 605 is fixed in place.

[0075] If the printer 300 is returned and transported in a state other than transport mode, ink may leak or user settings information may remain in the printer, making it impossible to start using the printer 300 in that condition. In other words, before reusing a returned printer 300, cleaning of any leaked ink and deletion of user settings information must be performed.

[0076] Therefore, by putting the printer 300 into transport mode when transporting it, it is possible to suppress ink leakage during packing and transport, as well as leakage of user setting information within the printing device. Transport mode processing is achieved by the CPU 311 reading the program stored in the program memory 313 into the data memory 314 and executing it.

[0077] When transport mode processing is initiated, the CPU 311 closes the tank valve 608 (see Figure 2) in S1301 (blocking operation). By closing the tank valve 608, the supply of ink from the built-in ink tank 601 to the print head 602 can be stopped, preventing ink from leaking from the print head 602. Here, the means for closing the tank valve 608 may be either by the printer 300 automatically closing it using a motor or the like, or by the CPU 311 displaying the screen shown in Figure 16(a), described later, on the printer 300's operation panel 305 and allowing the user to close it manually.

[0078] Subsequently, in S1302, the CPU 311 discharges ink from the print head 602 and ink tube 603 to the cap 606 (discharge operation). By discharging ink from the print head 602 and ink tube 603 in this way, it is possible to suppress ink leakage from the print head 602 if the casing of the printer 300 is tilted or subjected to vibration during transport. Next, in S1303, the CPU 311 fixes the carriage 605 (fixing operation). By moving the carriage 605 to a position opposite the cap 606 and raising the convex carriage lock pin 607, the concave member on the back of the carriage 605 engages with the carriage lock pin 607, and the carriage 605 is fixed. In this state, for example, even if the casing of the printer 300 is tilted or subjected to vibration during transport, the tight seal between the cap 606 and the print head 602 can be maintained.

[0079] Then, in S1304, the CPU 311 resets the user settings information stored in the printer 300 to its factory default state. This prevents the leakage of user settings information within the printer 300. Since the user settings information may contain information necessary for operating the printer 300, the user settings information is reset to its factory default state after the processing of each part (such as valve closing operation and carriage locking operation) is completed during transport mode processing. Subsequently, in S1305, the CPU 311 changes the status to "transport mode processing completed" and terminates the process. Specifically, the CPU 311 stores information (flag) in the data memory 314 indicating that transport mode processing has been completed.

[0080] In this way, during transport mode processing, the printer 300 automatically executes any processes that can be performed automatically, and if a process needs to be performed manually by the user, the process details are displayed on the control panel 305, and the user performs the process.

[0081] In this embodiment, the transport mode processing includes, but is not limited to, the actions of closing the valve, discharging ink, locking the carriage, and resetting user settings, as described above. For example, it may also include other actions such as fixing movable parts other than the carriage.

[0082] Figure 14 is a flowchart illustrating the process for terminating a service contract. The contract termination process is performed when a service user terminates the contract at their own discretion, and is initiated when the printer 300 receives a contract termination notification from the cloud server 200. The contract termination process is achieved when the CPU 311 reads the program stored in the program memory 313 into the data memory 314 and executes it. Note that contract termination includes both termination during the contract period and termination at the end of the contract period.

[0083] When the contract termination process is initiated, in S1401, the CPU 311 determines whether the transport mode processing for the printer 300 has been completed. Specifically, the determination is made based on whether or not information (flags) indicating that the transport mode has been completed is stored in the data memory 314. If the transport mode processing has been completed, the CPU 311 proceeds to S1405 and changes the state of the printer 300 to the contract termination state. On the other hand, if the transport mode processing has not been performed in S1401, the CPU 311 proceeds to S1402 and performs the transport mode processing as described in Figure 13. In the following S1403, the CPU 311 determines whether the transport mode processing in S1402 has completed successfully. If it has completed successfully, the CPU 311 proceeds to S1405 and changes the state to the contract termination state. If the transport mode processing in S1402 has not completed successfully, the CPU 311 proceeds to S1404, displays the error screen shown in Figure 16(b) below on the printer 300's control panel 305, and terminates the process without transitioning to the contract termination state.

[0084] In this way, the system checks whether the transport mode processing has been performed during the contract termination process, and if not, it performs the transport mode processing. As a result, by completing the contract termination process, the printer 300 completes the transport mode processing, which helps to reduce the need for packaging during transport, prevent ink leakage during transport, and prevent the leakage of user setting information within the printing device.

[0085] Figure 15 is a flowchart of the initialization process performed by the printer 300. The printer 300 functions as a printable printer after completing the initialization process. The initialization process is achieved by the CPU 311 reading the program stored in the program memory 313 into the data memory 314 and executing it. The initialization process is performed when the printer 300 is first used after purchase, or when it is first used again after transportation.

[0086] When the initialization process begins, in S1501, the CPU 311 determines whether or not the printer 300 is under a service contract (contract check). If the service contract is not ongoing, the CPU 311 proceeds to S1502 and displays the error screen shown in Figures 16(c) and (d) below on the printer 300's control panel 305. On the other hand, if in S1501 it is determined that the service contract is ongoing, the CPU 311 proceeds to S1503 and determines whether transport mode is being executed. If transport mode processing is not being executed, the system is in normal print mode, and the initialization process ends there.

[0087] If transport mode has already been executed in S1503, the CPU 311 proceeds to S1504, where it changes the state of the printer 300 from transport mode to normal print mode, making it ready for printing. In this embodiment, the tank valve 608 is opened to allow ink to be ejected from the print head 602, enabling ink to be supplied from the built-in ink tank 601. In addition, the convex carriage lock pin 607 is lowered to allow the carriage 605 to move along the carriage support 604.

[0088] Figure 16 is a schematic diagram showing the display screens shown on the control panel 305 of the printer 300. Figure 16(a) is the screen displayed on the control panel 305 of the printer 300 when the user is instructed to manually close the tank valve 608. Figure 16(b) is the screen displayed on the control panel 305 of the printer 300 when the transport mode processing has not been completed successfully. Figures 16(c) and (d) are screens displayed on the control panel 305 of the printer 300 when it is determined that the printer 300 is not under a service contract.

[0089] In this embodiment, an example was described in which the transport mode processing is performed during the contract termination process. However, the invention is not limited to this, and the transport mode processing may be made possible by the user pressing a button or the like on the printer 300.

[0090] In this way, based on the user's contract termination, preparatory actions for transport, which are carried out before transport, are performed. This makes it possible to provide a printing device, a control method for the printing device, a printing system, and a program that can suppress packing work, ink leakage during transport, and leakage of user setting information when transporting the printing device after the termination of the service contract for the printing device. (Second embodiment) A second embodiment of the present invention will be described below with reference to the drawings. Since the basic configuration of this embodiment is the same as that of the first embodiment, only the characteristic configurations will be described below.

[0091] Figure 17 is a flowchart showing the initialization process performed by the printer 300 in this embodiment. This process is achieved by the CPU 311 reading the program stored in the program memory 313 into the data memory 314 and executing it. This embodiment differs from the first embodiment in that the first step of the initialization process determines whether the printer 300 can communicate with the cloud server 200, and the printer 300 has a provisional print mode. In this embodiment, as in the first embodiment, the initialization process is performed when the printer 300 is first used after purchase or after transportation.

[0092] In this embodiment, when the initialization process starts, in S1701, the CPU 311 determines whether the printer 300 can communicate with the cloud server 200 (communication determination). If communication with the cloud server 200 is not possible, the CPU 311 proceeds to S1702 and displays the error screen shown in Figure 16(c) on the operation panel 305 of the printer 300. Subsequently, in S1703, the CPU 311 determines whether the transport mode process is being executed.

[0093] If it is determined in S1703 that the transport mode processing has not been performed, the CPU 311 proceeds to S1705 and sets the state of the printer 300 to provisional print mode. In this embodiment, the printer 300 has a provisional print mode in addition to the normal print mode and transport mode. Here, provisional print mode is a mode in which the printing device 300 is operated in a state in which communication with the server is not possible, ink can be ejected from the print head 602, and the carriage 605 can move along the carriage support part 604. However, since the printer 300 cannot communicate with the cloud server 200, services such as ink delivery and management of the number of printed pages cannot be received.

[0094] On the other hand, if the CPU 311 determines in S1703 that the transport mode processing has already been performed, it proceeds to S1704 and displays the screen shown in Figure 18 (described later) on the printer 300's control panel 305, prompting the user to choose whether to switch to provisional print mode. If the user chooses to switch to provisional print mode, the CPU 311 proceeds to S1705 and switches the printer 300's state to provisional print mode.

[0095] Furthermore, in S1701, if communication with the cloud server 200 is possible, the CPU 311 proceeds to S1706 to determine if the service has been deactivated. If the service has been deactivated, the CPU 311 proceeds to S1707 and displays the error screen shown in Figure 16(d) on the printer 300's control panel 305. On the other hand, if in S1706 it is determined that the service has not been deactivated, the CPU 311 proceeds to S1708 to determine if the transport mode processing is being performed. If the transport mode processing is being performed, the CPU 311 proceeds to S1709 and changes the printer 300's state from transport mode to normal print mode.

[0096] Figure 18 is a schematic diagram showing the display screen displayed on the control panel 305 of the printer 300. The display screen shown in Figure 18 is the screen displayed on the control panel 305 of the printer 300 when the user is asked to choose whether to switch to provisional print mode in S1704 of Figure 17. The user can operate the screen by pressing the "Yes" or "No" button depending on whether or not to switch to provisional print mode.

[0097] In this embodiment, a configuration was described in which operation in provisional print mode is possible even if communication with the cloud server 200 is not possible and the service contract status cannot be confirmed, but this is not the only configuration. If the service contract status cannot be confirmed, the printer may be configured to stop operating.

[0098] Thus, a printing device may be configured such that, during the initialization process, it is determined whether or not the printer 300 can communicate, and if communication is not possible, it can enter a provisional print mode.

[0099] (Other embodiments) The present invention can also be realized by supplying a program that implements one or more of the functions of the above-described embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit (e.g., an ASIC) that implements one or more functions. [Explanation of symbols]

[0100] 100 Printing Systems 200 cloud servers 300 printers 311 CPU 601 Built-in ink tank 602 Printhead 605 Carriage

Claims

1. A printing device provided to the user under contract and returned by the user by transport after termination of the said contract, Based on the user's contract termination, the system includes control means for controlling the execution of preparatory actions performed before transportation, including sealing actions to prevent ink leakage. The printing apparatus is characterized in that the control means performs a reset operation to reset the user's settings information after the blocking operation.

2. The printing apparatus according to claim 1, characterized in that, upon contract termination by the user, it receives a contract termination notice from the server and performs the transport preparation operation.

3. The system further includes a determination means for determining whether or not the aforementioned transport preparation operation has been performed. The printing apparatus according to claim 1 or 2, characterized in that if the determination means determines that the transport preparation operation has not been performed, the control means controls the system to perform the transport preparation operation.

4. A carriage means that moves while being equipped with a dispensing means for dispensing liquid, The system comprises a storage means connected to the discharge means by a connecting portion, which stores the liquid supplied to the discharge means via the connecting portion, The printing apparatus according to claim 1, characterized in that the transport preparation operation includes a fixing operation to fix the carriage means so that it does not move, a blocking operation to close the connection part, and a discharge operation to discharge the liquid inside the connection part and the liquid inside the discharge means.

5. The printing apparatus according to claim 4, characterized in that the control means performs the reset operation after the fixing operation, the blocking operation, and the discharge operation.

6. The printing apparatus according to any one of claims 1 to 5, characterized in that it is configured to perform the transport preparation operation regardless of the user's termination of the contract.

7. The system further includes a contract determination means for determining whether the aforementioned contract is in effect or not. The printing apparatus according to any one of claims 1 to 6, characterized in that a determination is made by the contract determination means when use begins.

8. The printing apparatus according to claim 7, characterized in that if the contract is continued as a result of the determination by the contract determination means, it transitions to a state where it can print.

9. The system further includes a communication determination means for determining whether or not communication with the server is possible. The printing apparatus according to claim 7 or 8, characterized in that, if the result of the determination by the communication determination means determines that communication is possible, the determination by the contract determination means is performed.

10. The printing apparatus according to claim 9, characterized in that it includes a provisional print mode that operates the printing apparatus without communicating with the server if, as a result of the determination by the communication determination means, it is determined that communication is impossible.

11. The printing apparatus according to claim 9, characterized in that it stops operation if, as a result of the determination by the communication determination means, it is determined that communication is impossible.

12. The printing apparatus according to any one of claims 1 to 11, characterized in that, in the transport preparation operation, processes that can be executed automatically are executed automatically, and when a process is to be performed manually by the user, the content of the process is displayed on the display screen.

13. A method for controlling a printing device provided to a user under a contract and returned by the user by transport after termination of the contract, Based on the user's contract termination, the system has a control process that controls the execution of preparatory actions performed before transportation, including sealing actions to prevent ink leakage. A control method for a printing apparatus, characterized in that, in the control step, a reset operation is performed to reset the user's settings information after the blocking operation.

14. A printing device provided to the user under contract and returned by the user by transport after termination of the said contract, A printing system comprising: a server that is communicatively connected to the printing device and manages the user's contract, The printing apparatus includes control means that controls the execution of preparatory operations performed before transport, including a blocking operation to prevent ink leakage, based on information indicating contract termination by the user notified from the server. The printing system is characterized in that the control means performs a reset operation to reset the user's settings information after the blocking operation.

15. A program for causing a computer to function as one of the means of the printing apparatus according to any one of claims 1 to 12.

Images