JP7679253B2 - Image processing system, terminal device, server device, control method thereof, program, and storage medium - Google Patents

Description

The present invention relates to an image processing system.

In an application for creating and printing poster content, one use case is when a company has a "head office and branches," and creates a poster template at the head office, and the branch office adds the finishing touches and prints it. In this type of use, poster creators need to be able to create poster content easily in a variety of environments. For example, it needs to be possible to use it on a PC or tablet without installing a dedicated app, and it needs to be possible for the poster creator and the printer to share the created content. As a method for achieving this, Patent Document 1 discloses technology that enables printing with a web app.

JP 2012-160009 A

However, the technology disclosed in Patent Document 1 requires authentication processing with the printer that will perform the printing in order to ensure sufficient security when printing over the Internet, which creates the problem of cumbersome operations.

The present invention has been made in consideration of the above-mentioned problems, and its purpose is to provide an image processing method that can improve the convenience of creating and printing content without having to perform cumbersome authentication processing with the printer.

The image processing system according to the present invention is an image processing system in which a terminal device and a server device are communicatively connected, the server device includes an editing means for editing image data and a rendering means for rendering the image data, the terminal device includes a setting means for making print settings for printing the image data and a generating means for generating print data for printing the image data, the terminal device determines a rendering size of the image data according to the print settings made by the setting means, requests the server device to render the image data based on the rendering size, receives the data rendered by the server device, and generates the print data.

The present invention makes it possible to improve the convenience of creating and printing content without having to go through cumbersome authentication processes with the printer.

1 is a diagram showing the configuration of a print processing system according to an embodiment of the present invention. FIG. 2 is a block diagram showing the configuration of a terminal device. FIG. 1 is a block diagram showing the configuration of a printing apparatus. FIG. 2 is a diagram showing the configuration of a Web application server. FIG. 2 is a software configuration diagram of a Web application server. FIG. 2 is a software configuration diagram of the terminal device. FIG. 4 is a schematic diagram showing an editing screen of a web application. FIG. 4 is a schematic diagram showing an editing screen of a print application. FIG. 4 is a sequence diagram showing the main operation of the entire system. 5 is a flowchart showing an operation performed by the terminal device according to a Frontend program. 11 is a flowchart showing a Backend operation. 6 is a flowchart showing the operation of a print application. 6 is a flowchart showing the operation of a print setting screen of a print application. 6 is a flowchart showing the operation of a print process of a print application.

The following embodiments are described in detail with reference to the attached drawings. Note that the following embodiments do not limit the invention according to the claims. Although the embodiments describe multiple features, not all of these multiple features are necessarily essential to the invention, and multiple features may be combined in any manner. Furthermore, in the attached drawings, the same reference numbers are used for the same or similar configurations, and duplicate explanations are omitted.

In the following embodiment, a smartphone is used as an example of an information processing device, but the type of information processing device is not limited to this, as long as it is a device that can handle files to be printed. For example, various devices can be applied, such as mobile terminals other than smartphones, notebook personal computers (PCs), desktop PCs, tablet terminals, PDAs (Personal Digital Assistants), digital cameras, etc. In addition, as a printing device, an inkjet printer, a laser beam printer, etc. can be used as a printer. Also, a multifunction device that has not only a printing function but also a scanning function for reading a document, a copying function, and a facsimile function may be used.

<Overall system configuration>
FIG. 1 is a diagram showing a configuration of a print processing system 1000 according to an embodiment of the present invention. The print processing system (image processing system) 1000 includes a terminal device 200 and a printing device 300 that can communicate with each other. The terminal device 200 communicates with the printing device 300 via a network constructed by the access point 100. The terminal device 200 stores programs such as a print application, which will be described later. Print data created using the print application is transmitted from the terminal device 200 to the printing device 300 via the network. In addition, since the access point 100 of this embodiment functions as a wireless LAN router, the terminal device 200 is connected to the Internet via this wireless LAN router. Therefore, the terminal device 200 can communicate with a user authentication server 101 and a Web application server 102 via the Internet. The terminal device 200 and the printing device 300 can also be connected to the access point 100 via a wired LAN.

The web application server 102 is a server for controlling the web application described below. The user authentication server 101 is a server for managing users and performing authentication processing for the Frontend program of the web application described below and the print application.

<Configuration of Terminal Device>
2 is a block diagram showing the configuration of a terminal device 200 used in the print processing system 1000. The terminal device 200 is configured to include a main board 205 that controls the entire device, a wireless LAN unit 202, an NFC (Near Field Communication) unit 203, a line connection unit 201, and a touch panel display 204 for operating programs. Here, the NFC unit 203, the wireless LAN unit 202, and the line connection unit 201 are capable of communication using NFC, a wireless LAN, and a mobile phone line network, respectively, which are not shown.

The CPU 206 in the form of a microprocessor arranged on the main board 205 operates according to a control program stored in a program memory 207 in the form of a ROM connected via an internal bus 216, and the contents of a data memory 208 in the form of a RAM. The program memory 207 can store an embedded operating system (OS) and programs such as the print application program of this embodiment. In this embodiment, each application program stored in the program memory 207 is subjected to software execution control under the management of the OS. Specifically, this is realized by the CPU 206 reading out the application program stored in the program memory 207 into the data memory 208 in the form of a RAM and executing it.

The CPU 206 controls the wireless LAN unit 202 via the wireless LAN control circuit 212 to communicate with other communication terminal devices via the wireless LAN. Note that the wireless LAN unit 202 is capable of data (packet) communication using a communication method that complies with the IEEE 802.11 series (IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, etc.).

The CPU 206 also controls the NFC unit 203 via the NFC control circuit 213 to detect an NFC connection with another NFC terminal and to transmit and receive data to and from the other NFC terminal.

The CPU 206 can also control the line connection unit 201 via the line control circuit 211 to connect to a mobile phone network and make calls and send and receive data. The device may also be equipped with a unit for implementing the Bluetooth (registered trademark) Low Energy (BLE) communication method.

The CPU 206 can display on the touch panel display 204 and accept operations from the user by controlling the operation unit control circuit 214. Furthermore, the CPU 206 can control the camera unit 215 to capture images, and store the captured images in the image memory 209 in the data memory 208. In addition to captured images, it is also possible to store images acquired from outside via a mobile phone network, wireless LAN, or NFC in the image memory 209, or conversely, transmit them to the outside.

The non-volatile memory 210 is composed of a memory such as a flash memory, and can store data that is to be kept even after the power is turned off. For example, telephone directory data, various communication connection information, information on previously connected devices, and image data that is to be saved are stored. Application management information managed by the poster creation application of this embodiment is also stored in the non-volatile memory 210.

The terminal device 200 may be a mobile terminal equipped with iOS or Android (registered trademark) OS, or a host device equipped with Windows/macOS/Linux (registered trademark).

<Configuration of Printing Device>
3 is a block diagram showing the configuration of the printing device 300. The printing device 300 is configured to include a main board 304 that controls the entire device, a wireless LAN unit 301, an NFC unit 302, and an operation panel 303. Here, the wireless LAN unit 301 and the NFC unit 302 function as a communication unit of the printing device 300.

The CPU 305 in the form of a microprocessor arranged on the main board 304 operates according to a control program stored in a program memory 306 in the form of a ROM connected via an internal bus 314, and the contents of a data memory 307 in the form of a RAM.

The CPU 305 controls the scanner unit 309 to read an original document and store the image in the image memory 308 in the data memory 307. The CPU 305 can also control the printing unit 313 to print an image in the image memory 308 in the data memory 307 on a recording medium. It is also possible to transmit scanned image data to the terminal device 200 via the wireless LAN unit 301 controlled by the wireless LAN control circuit 310.

The CPU 305 controls the wireless LAN unit 301 through the wireless LAN control circuit 310 to communicate with other communication terminal devices 200 via the wireless LAN. Note that the wireless LAN unit 301 is capable of data (packet) communication using a communication method that complies with the IEEE 802.11 series (IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, etc.).

The CPU 305 also controls the NFC unit 302 via the NFC control circuit 311 to detect an NFC connection with another NFC terminal and to transmit and receive data to and from the other NFC terminal.

The CPU 305 controls the operation unit control circuit 312 to display the status of the printing device 300 and a function selection menu on the operation panel 303, and can also accept operations from the user.

The printing device 300 of this embodiment can receive and print data in JPEG file format with printer control commands.

Furthermore, the printing device 300 may be a printing device capable of printing using spot color ink. Spot color ink is ink that produces a spot color (hereinafter also referred to as "spot color"), and is, for example, an ink whose color produced during printing cannot be displayed in the SRGB color space. In other words, the printer 14 is configured to be capable of spot color printing, which is printing using spot color ink (i.e., spot color ink, hereinafter also referred to as "spot color ink") other than normal ink.

"Normal ink" refers to ink used for printing process colors (normal colors), such as cyan (C), magenta (M), yellow (Y), and black (K), which are the basic process colors. A process color is a color that is expressed using one color from CMYK, or a combination of two or more colors from CMYK.

In this embodiment, fluorescent pink ink and fluorescent orange ink are used as spot color inks. In other words, spot colors are colors that are different from process colors and cannot be expressed using only one color among CMYK, or a combination of two or more colors among CMYK.

However, this is not limited to this form, and the number and colors of spot color inks may be any, and inks of colors other than fluorescent colors may be used. For example, violet ink, green ink, orange ink, gold ink, silver ink, etc. may be used as spot color inks. Inks of other metallic colors may also be used. Furthermore, inks that are mixtures of spot color inks and other inks (for example, normal inks) may also be treated as spot color inks.

In addition, in this embodiment, an object in the image data that is to be printed in a spot color is associated with information (called spot color information) indicating that it will be printed in a spot color. A pixel to which spot color information has been added is printed in the spot color corresponding to the RGB value of that pixel. The RGB value of a pixel corresponding to a spot color can also be used as the RGB value of a pixel corresponding to a color that is expressed only with normal ink (i.e., a normal color). In other words, the same RGB value as the RGB value of a pixel corresponding to a spot color may also be set for a pixel corresponding to a color that is expressed only with normal ink. In that case, whether or not special ink is used to print a pixel of that RGB value is controlled by whether or not special color information has been added.

<Web Application Server Configuration>
4A is a block diagram showing the hardware configuration of the Web application server 102. The Web application server 102 includes a CPU 421 that controls the entire server, a volatile memory 422, a non-volatile memory 423, and a communication circuit 424.

The CPU 421 controls the entire Web application server 102 by expanding the programs stored in the non-volatile memory 423 into the volatile memory 422 and executing them. The CPU 421 also executes the above programs to realize modules realized by software such as Frontend 400 and Backend 404 shown in FIG. 4B. The communication circuit 424 is also capable of communicating with the terminal device 200 via the Internet.

<Software configuration>
FIG. 4B is a diagram showing the software configuration in the Web application server 102. Frontend 400 mainly controls the display of the Web browser of the terminal device. Specifically, Frontend 400 manages and holds a program (JavaScript) executed on the browser. Specifically, Frontend 400 manages and holds a program (JavaScript) for executing a UI (user interface) control unit 402 that controls user operations on the browser, a work editing unit 401 that processes work editing created by an application, and a user authentication unit 403 that performs user authentication. Then, Frontend 400 transmits these programs to the terminal device, causing the Web browser of the terminal device to display the programs. That is, when the terminal device receives the program, it uses the program to display a screen corresponding to the program on the Web browser.

Backend 404 is configured with a user management unit 405 that manages users, a content management unit that manages content, and a rendering processing unit that performs rendering. Frontend 400 and Backend 404 are realized by the CPU 421 in the Web application server 102 executing a program stored in the non-volatile memory 423.

Figure 5 (a) is a diagram showing the software configuration when the terminal device is a PC. Representative web browsers 500 include "Internet Explorer", "Microsoft Edge", "Google Chrome", "Safari", "Firefox", etc. The print application 501 is an application program that prints based on print settings made by the user. The print application 501 has a print setting processing unit 502 that makes print settings, and a thumbnail display unit 503 that displays thumbnails. In this embodiment, the print application 501 is downloaded and installed from a server different from the web application server 102 to the terminal device, and is then saved in the terminal device.

When the terminal device is a PC, the print data generation process is performed by a printer driver 504. The printer driver 504 has printer model information 505 and a print data generation processing unit 506. The printer driver 504 is distributed by the printer vendor and can be used by the user by installing it. It may also be included with the OS.

The model information 505 stores print setting information that can be used by the printer. Specifically, this includes setting values and function information that can be used by the printer. Examples of usable setting values include settings for the paper feed method and the paper type. Examples of usable function information include information on whether the spot color printing function can be used.

Figure 5(b) is a diagram showing the software configuration when the terminal device is a mobile terminal. Only the differences from Figure 5(a) will be explained. In the case of a mobile terminal, a printer driver does not exist. Therefore, a print processing module 507 that performs print data generation processing is provided. The print processing module 507 includes a model information acquisition processing unit 508. The model information acquisition processing unit 508 communicates with the printing device 300 to acquire model information 505, which is stored in the data memory 208 or the non-volatile memory 210 (see Figure 2).

<Application configuration>
6 is a diagram showing a screen of a web application displayed on a browser by the UI control unit 402. Note that, as described above, the screen is displayed on the browser of the terminal device by transmitting a program held by the Frontend 400 to the terminal device.

In this embodiment, an example will be described in which the web application is an application for printing posters. When any of the template button 600, photo button 601, and clip art button 602 is pressed, a list of content corresponding to the pressed button is displayed in the list display area 603. For example, when the template button 600 is pressed, a list of selectable templates is displayed in the list display area 603. When a desired template is selected from the list displayed in the list display area 603, it is displayed in the editing area 604 and becomes editable. The user edits the template and ultimately generates work data. Here, the work data includes image data and various print settings.

When the photo button 601 is pressed, a list of selectable images is displayed in a list display area 603, and when a desired image is selected, it is added and superimposed on the template displayed in the editing area 604. Similarly, when the clip art button 602 is pressed, a list of selectable clip art is displayed in a list display area 603, and when a desired clip art is selected, it is added and superimposed on the template displayed in the editing area 604. The template is described as an example of SVG (Scalable Vector Graphics), but it may also be in Canvas format.

When the export button 605 is pressed, the created work data information can be downloaded and saved in the data memory 208 or non-volatile memory 210 of the terminal device 200. When the proceed to print button 606 is pressed, the print application 501 is launched.

In the palette area 607, selectable colors are displayed, and when a desired color is selected while the clip art in the editing area 604 is active, the color can be changed to the selected color. In the spot color palette area 608, selectable spot colors are displayed, and when a desired color is selected while the clip art in the editing area 604 is active, the color can be changed to the selected color.

In this embodiment, the display contents of this screen are controlled by a program that Frontend 400 sends to the terminal device. In this embodiment, the Web application server 102 having Frontend 400 does not recognize the capabilities of the printer to which the print data is sent. Therefore, the Web application server 102 does not recognize whether the printer to which the print data is sent is a printer that can use special ink (can perform spot color printing). Therefore, in this embodiment, in the print setting screen as shown in FIG. 4B, which is controlled by a program that Frontend 400 sends to the terminal device, an area such as area 608 for performing settings related to printing using spot color ink is displayed regardless of whether the printer to which the print data is sent can use special ink.

The original size selection section 609 allows you to select the desired original size. The final completed work data contains information about the original size, clip art to which spot colors have been applied, and information about the R, G, and B values to which the spot colors are applied.

Figure 7 is a diagram showing the screen of the print application 501. In this embodiment, the terminal device 200 is described as a mobile terminal, but the effects that can be achieved are the same as when the terminal device 200 is a PC. Note that the display content in Figure 7 is controlled by the print application 501, which is a program that is not sent from the web application server 102. Also, Figure 7 is a screen that is not displayed on a web browser.

The preview display area 700 displays a thumbnail of the work data to be printed, created by Backend 404. The printer selection unit 701 allows the user to select the printer to be used for printing. If the terminal device 200 is a mobile terminal, the selectable printers must be registered in advance in order for the printer selection unit 701 to display the selectable printers.

The paper feed method selection section 702 displays a list of paper feed methods that can be used with the selected printer, and the desired paper feed method can be selected from the list. The paper type selection section 703 displays a list of paper types that can be used with the selected printer, and the desired paper type can be selected from the list.

The enlargement/reduction print selection section 704 has check boxes, and when checked, enlargement/reduction processing is performed according to the radio button located below the check box and printing is performed. When the long edge fit button 705 is selected, the work data is enlarged and printed so that the long edge matches the width of the roll paper provided in the printing device 300. When the short edge fit button 706 is selected, the work data is enlarged and printed so that the short edge matches the width of the roll paper provided in the printing device 300.

When the Fit to Printable Area button 707 is selected, the image is enlarged/reduced according to the output paper size selection area 708 located below the button and then printed. The list displayed in the output paper size selection area 708 lists only the paper sizes that can be selected for the selected printer. If the check box in the enlarged/reduced print selection area 704 is not checked, the radio buttons located below cannot be selected.

The special ink selection section 709 has a check box, allowing the user to select whether or not to use special ink. When a check is enabled, printing is performed with special ink applied according to the radio button located below the check box. When the Use fluorescent spot color button 710 is selected, the clipart part selected in the fluorescent spot color palette area 608 is printed in the fluorescent spot color. When the Make everything vivid button 711 is selected, predetermined R, G, and B pixels are printed in the fluorescent spot color when rendering the work data into RGB data.

If the check box of the special ink selection section 709 is not checked, the radio button located below is disabled. If the work data does not include information on the fluorescent spot color, the check box of the special ink selection section 709 is disabled. In this embodiment, the terminal device can control the display content of the screen using the print application 501 according to the capabilities of the printer. Therefore, regardless of whether the work data includes information on the special ink, the terminal device checks the model information 505, and even if the printer cannot use spot colors, the terminal device controls the check box of the special ink selection section 709 to be disabled. In other words, if the work data created by the Web application server 102 includes information on the special ink and the printer to which the print data is sent cannot use the special ink, the print settings related to printing using the special ink cannot be executed in the print application 501. Specifically, the screen for executing the print settings is not displayed in the print application 501. Note that when information about special ink is included in the work data created by the Web application server 102, that is, when settings related to printing using special ink are executed in the Web application server 102 as settings for printing the work data created by the Web application server 102.

<Overall sequence>
The main operation of the entire system will be described with reference to the sequence diagram of FIG. 8. Details of the individual processes of the program (hereinafter, the Frontend program) transmitted from the Frontend 400 to the terminal device, the Backend 404, and the print application 501 will be described later. Note that the process described as the process executed by the Backend 404 is actually realized by the CPU 421 of the Web application server 102 executing a program corresponding to the Backend 404. Also, the process described as the process executed by the Frontend program is actually realized by the CPU 206 executing the Frontend program. Also, the process described as the process executed by the print application 501 is actually realized by the CPU 206 executing the print application 501.

When the user generates work data in the browser and presses the Proceed to Print button 606, in step S801, the Frontend program requests Backend 404 to create a print job. In step S802, Backend 404 creates a thumbnail to be passed to the print application 501. Next, in step S803, the Frontend program launches the print application 501.

After the print application 501 is launched, it performs authentication processing in step S804. After completing the authentication processing, the print application 501 receives thumbnails from Backend 404 in step S805 and launches the screen in FIG. 7. When the user configures print settings and presses the print button in step S806, the print application 501 requests Backend 404 to render the work data in step S807.

Next, Backend 404 renders the work data in step S808. Next, the print application 501 receives the rendered data in step S809. The print application 501 generates print data from the received rendered data in step S810, and transmits the print data to the printing device 300 in step S811.

<Processing flow>
9 is a flowchart showing the operation of the terminal device according to the Frontend program. The process shown in this flowchart is realized by the CPU 206 executing the Frontend program.

When the user causes the CPU 206 to open the web browser 500 on the terminal device and inputs the URL of the web application server 102, the CPU 206 causes the user authentication unit 403 to display an authentication screen (not shown) in step S901.

When the user inputs a login ID and password, in step S902, the CPU 206 checks with the user authentication unit 403 whether the input information is registered information. If the user is registered, in step S903, the UI control unit 402 displays the main screen and enters an event waiting state. If the user is not registered, the process returns to step S901 and the authentication screen is displayed again.

When an event is received in step S905, in step S906, the CPU 206 determines whether the received event is an editing event. If the received event is an editing event, in step S907, the CPU 206 causes the work editing unit 401 to perform editing processing such as editing the template.

In step S908, the CPU 206 determines whether the received event is a press event of the export button 605. If the received event is a press event of the export button 605, in step S909, the CPU 206 performs an export process of the work data.

In step S910, the CPU 206 determines whether the received event is a press event of the Proceed to Print button 606. If the received event is a press event of the Proceed to Print button 606, in step S912, the CPU 206 transmits job information to the Frontend 400, mainly including the work data and the Token information acquired during authentication.

In step S913, the CPU 206 launches the print application 501 in the terminal device. The custom URL scheme of the print application 501 is registered in the OS, and the print application 501 can be launched from the Frontend program by calling the scheme from a web browser. The method of launching from the browser may be a method other than launching using a custom URL scheme, such as FireBase Dynamic Link.

In step S911, the CPU 206 determines whether the received event is an event that instructs the application to be terminated. If the received event is an event that instructs the application to be terminated, this flow ends. If not, the flow returns to step S904 and the application waits for an event.

Figure 10 is a flowchart showing the operation of Backend 404. The processing shown in this flowchart is realized by the CPU 421 of the Web application server 102 executing a program corresponding to Backend 404.

In step S1001, Backend 404 receives job information from Frontend 400. Note that the job information is sent to Frontend 400 from a terminal device.

In step S1002, Backend 404 checks the Token information included in the job information. If the Token information is invalid, such as expired, Backend 404 displays an error in step S1012 and ends the process.

If the check of the Token information is completed correctly, Backend 404 renders the work data included in the job information and generates a thumbnail in step S1003. The thumbnail generated may be JPEG data or PNG data. Next, Backend 404 waits for a request from the print application 501 in step S1004.

When Backend 404 receives a request from print application 501 in step S1005, Backend 404 checks the Token information included in the request from print application 501 in step S1006. If the Token information is invalid, such as expired, Backend 404 displays an error in step S1012 and ends the process.

If the check of the token information is completed correctly, Backend 404 determines in step S1007 whether the request from print application 501 is a request for a thumbnail. If the request from print application 501 is a request for a thumbnail, Backend 404 sends the thumbnail created in step S1003 to print application 501 in step S1008.

In step S1009, Backend 404 determines whether the request from print application 501 is a request for rendering. If the request from print application 501 is a request for rendering, Backend 404 performs rendering based on the size information included in print application 501 in step S1010. The rendered data may be JPEG data or PNG data. If the request from print application 501 is not a request for rendering, the process returns to step S1004 and waits for a request from print application 501.

In step S1011, Backend 404 sends the rendered rendering data to the print application 501.

Figure 11 is a flowchart showing the operation of the print application 501. The processing shown in this flowchart is realized by the CPU 206 executing the print application 501. Furthermore, the processing described as being executed by the print application 501 is actually realized by the CPU 206 executing the print application 501.

Because the user using the print application 501 must be the same user who created the work data with the Frontend program, the print application 501 displays an authentication screen in step S1101. When the user enters a login ID and password, the user authentication unit of the print application 501 checks in step S1102 whether the entered information is registered information. If the user is a registered user, the print application 501 transitions to processing of the print setting screen in step S1103, and if the user is not a registered user, the process returns to step S1101 and displays the authentication screen again.

Figure 12 is a flowchart showing the operation of the print setting screen. The process shown in this flowchart is realized by the CPU 206 executing the print application 501.

In step S1201, the print application 501 obtains thumbnails from Backend 404. In step S1202, the print application 501 displays a print setting screen, and in step S1203, the print application 501 enters an event waiting state.

When the print application 501 receives an event in step S1204, the print application 501 determines in step S1205 whether the event is a setting update event. If the event is a setting update event, the print application 501 executes processing to update the print settings in step S1206.

In step S1207, the print application 501 determines whether the event is a print execution event. If the event is a print execution event, the print application 501 executes print processing in step S1208. Details of the print processing will be described later.

In step S1209, the print application 501 determines whether the event is an event that instructs the application to end. If the received event is an event that instructs the application to end, the flow ends. If not, the flow returns to step S1203 and the application waits for an event.

Figure 13 is a flowchart showing the operation of the print process. The process shown in this flowchart is realized by the CPU 206 executing the print application 501.

In step S1301, the print application 501 calculates the rendering size to be requested from Backend 404. If the check box in the enlarged/reduced print selection section 704 on the print settings screen is not checked, the rendering size is calculated from the document size information received from the Frontend program. If the check box in the enlarged/reduced print selection section 704 is checked and Fit to printable area is selected, the rendering size is calculated based on the output paper size. If the long edge fit button 705 is selected, the enlargement process is performed so that the roll paper width of the printing device 300 matches the long side of the work data, so the calculation is made to the size when enlarged. If the short edge fit button 706 is selected, the enlargement process is performed so that the roll paper width of the printing device 300 matches the short side of the work data, so the calculation is made to the size when enlarged.

In step S1302, the print application 501 requests rendering from Backend 404. In step S1303, the print application 501 checks whether rendering is complete. If rendering is not complete, it waits until it is complete.

In step S1304, the print application 501 receives the rendering data. In step S1305, the print application 501 generates print data from the rendering data, and in step S1306, transmits the print data to the printing device 300.

As described above, in the above embodiment, the server includes a work editing unit, a UI control unit, a user authentication unit, and a rendering processing unit, while the terminal device includes model information, a print setting processing unit, and a print data generation processing unit. The rendering size is then determined according to the print settings determined in the print setting process of the terminal device, and a request is made to the server for rendering at that size. The rendered data is then received and print data is generated. With this configuration, work data can be edited on a terminal device such as a PC or tablet without installing a dedicated app, and content can be printed without having to go through complicated authentication processes with the printer.

[Other embodiments]
Needless to say, the object of the present invention can also be achieved by supplying a recording medium on which is recorded software program code that realizes the functions of the above-mentioned embodiments to a system or device, and having the computer (or CPU or MPU) of the system or device read and execute the program code stored in the recording medium. In this case, the program code itself read from the storage medium realizes the functions of the above-mentioned embodiments, and the storage medium on which the program code is stored constitutes the present invention.

Storage media for supplying program code may include, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a non-volatile memory card, a ROM, a DVD, etc.

Furthermore, it goes without saying that not only are the functions of the above-mentioned embodiments realized by the computer executing the program code it has read, but also that the functions of the above-mentioned embodiments can be realized by an Operating System (OS) running on the computer performing some or all of the actual processing based on the instructions of the program code.

Furthermore, it goes without saying that this also includes cases where the program code read from the storage medium is written into the memory of an expansion board inserted into a computer or an expansion unit connected to a computer, and then a CPU or the like in the expansion board or expansion unit performs some or all of the actual processing based on the instructions of the program code, thereby realizing the functions of the above-mentioned embodiments.

100: Access point, 101: User authentication server, 102: Web application server, 200: Terminal device, 300: Printing device, 1000: Print processing system

Claims (15)

An image processing system in which a terminal device and a server device are communicatively connected,
the server device includes an editing unit that edits image data and a rendering unit that renders the image data;
the terminal device includes a setting unit for making print settings for printing the image data, and a generating unit for generating print data for printing the image data;
The image processing system is characterized in that the terminal device determines a rendering size of the image data in accordance with the print settings made by the setting means, requests the server device to render the image data based on the rendering size, receives the data rendered by the server device, and generates the print data. The image processing system according to claim 1, characterized in that the terminal device transmits the print data to a printing device. The image processing system according to claim 1 or 2, characterized in that the server device further comprises a UI control means for controlling a user interface. The image processing system according to any one of claims 1 to 3, characterized in that the server device further comprises a user authentication means for authenticating a user. The image processing system according to any one of claims 1 to 4, characterized in that the terminal device further comprises a storage means for storing model information of a printing device that prints the image data. The image processing system according to any one of claims 1 to 5, characterized in that when settings related to printing using special ink are executed in the server device as settings for printing the image data, and when the printing device to which the print data is sent cannot execute printing using special ink, the terminal device does not display a screen for executing settings related to printing using the special ink. The image processing system according to any one of claims 1 to 6, characterized in that a print application that runs on the terminal device and realizes the setting means and the generating means is started in response to an instruction from the server device. The image processing system according to claim 7, characterized in that the server device renders the image data in response to an instruction from the print application. The image processing system according to any one of claims 1 to 8, characterized in that the terminal device enables printing of the image data after authenticating the user. A terminal device capable of communicating with a server device, the server device including an editing unit that edits image data and a rendering unit that renders the image data,
A setting unit for performing print settings for printing the image data;
a generating unit for generating print data for printing the image data;
A terminal device characterized in that a rendering size of the image data is determined in accordance with the print settings made by the setting means, a rendering size of the image data is requested from the server device to render the image data based on the rendering size, the data rendered by the server device is received, and the generation means generates the print data. A server device capable of communicating with a terminal device,
An editing means for editing image data;
a rendering means for rendering the image data;
The server device is characterized in that the rendering means renders the image data based on a rendering size transmitted from the terminal device. A method for controlling a terminal device capable of communicating with a server device including an editing unit that edits image data and a rendering unit that renders the image data, comprising:
A setting step of performing print settings for printing the image data;
A generating step of generating print data for printing the image data,
A control method for a terminal device, characterized in that, in the setting process, a rendering size of the image data is determined in accordance with print settings, and the server device is requested to render the image data based on the rendering size, and, in the generation process, the data rendered by the server device is received and the print data is generated. A method for controlling a server device capable of communicating with a terminal device, comprising:
An editing process for editing image data;
A rendering step of rendering the image data,
A method for controlling a server device, wherein the rendering step performs rendering of the image data based on a rendering size transmitted from the terminal device. A program for causing a computer to execute each step of the control method according to claim 12 or 13. A computer-readable storage medium storing a program for causing a computer to execute each step of the control method according to claim 12 or 13.

Images