Image processing system, terminal device, server device, control method thereof, program, and storage medium

Abstract

To provide an image processing method capable of enhancing convenience in creating contents and performing printing without performing troublesome authentication process with a printer.SOLUTION: In an image processing system, a terminal device and a server device are communicatively connected. The server device includes: an editing unit for editing image data; and a rendering unit for rendering the image data. The terminal device includes: a setting unit for making print setting for printing the image data; and a generation unit for generating print data for printing the image data. The terminal device determines a rendering size of the image data according to the print setting by the setting unit, requests rendering of the image data based on the rendering size to the server device, receives data being rendered by the server device, and generates the print data.SELECTED DRAWING: Figure 8

Description

Technical Field

[0001] The present invention relates to an image processing system.

Background Art

[0002] In an application for creating and printing poster content, there is a usage method such as "a company with a 'head office / branch' creates a poster prototype at the head office and performs the final finishing and printing at the branch". In such a usage method, it is required that the poster creator can easily create poster content in various environments. For example, it is necessary to be able to use it without installing a dedicated application on a PC, tablet, etc., and to be able to share the created content between the poster creator and the printer. As a method for realizing these, a technology that can be printed by a web application is disclosed in Patent Document 1.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the technology disclosed in Patent Document 1, in order to ensure sufficient security when printing via the Internet, authentication processing with the printer that performs printing is required, and there is a problem that the operation becomes complicated.

[0005] The present invention has been made in view of the above-described problems, and an object thereof is to provide an image processing method capable of improving the convenience of creating and printing content without performing complicated authentication processing with a printer.

Means for Solving the Problems

[0006] The image processing system according to the present invention is an image processing system in which a terminal device and a server device are communicably 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 that performs print settings for printing the image data and a generation unit that generates print data for printing the image data. The terminal device determines the rendering size of the image data according to the print settings by the setting unit, 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.

Effects of the Invention

[0007] According to the present invention, it is possible to improve the convenience of creating and printing content without performing complicated authentication processing with a printer.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4A

Figure 4B

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Mode for Carrying Out the Invention

[0009] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the invention according to the claims. Although a plurality of features are described in the embodiments, not all of these plurality of features are essential to the invention, and the plurality of features may be arbitrarily combined. Further, in the accompanying drawings, the same reference numerals are assigned to the same or similar configurations, and redundant explanations are omitted.

[0010] Also, in the following embodiments, a smartphone is taken as an example of the information processing apparatus for description, but the type of the information processing apparatus is not limited to this as long as it can handle files to be printed. For example, various devices such as mobile terminals other than smartphones, notebook personal computers (PCs), desktop PCs, tablet terminals, PDAs (Personal Digital Assistants), digital cameras, etc. can be applied. Also, as the printing apparatus, as long as it is a printer, an inkjet printer, a laser beam printer, etc. can be used. Further, not only a printing function but also a composite machine having a scan function for reading documents, a copy function, and a facsimile function may be used.

[0011] <Configuration of the Entire System> FIG. 1 is a diagram showing the configuration of a printing processing system 1000 according to an embodiment of the present invention. The printing 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 an access point 100. Programs such as a printing application described later are stored in the terminal device 200. Printing data created using the printing application is transmitted from the terminal device 200 to the printing device 300 via the network. Also, since the access point 100 of the present 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.

[0012] The Web application server 102 is a server for controlling a Web application described later. The user authentication server 101 is a server for performing user management and authentication processing for a Frontend program of a Web application described later and a printing application.

[0013] <Configuration of the terminal device> FIG. 2 is a block diagram showing the configuration of the terminal device 200 used in the printing processing system 1000. The terminal device 200 includes 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 can communicate using an NFC, a wireless LAN, and a mobile phone line network (not shown), respectively.

[0014] The CPU 206 in the form of a microprocessor arranged on the main board 205 operates according to a control program stored in the program memory 207 in the form of a ROM connected via the internal bus 216 and the content of the 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 printing application program of the present embodiment. In the present embodiment, software execution control is performed on each application program stored in the program memory 207 under the management of the OS. Specifically, it is realized by the CPU 206 reading out the application program stored in the program memory 207 to the data memory 208 in the form of a RAM and executing it.

[0015] The CPU 206 controls the wireless LAN unit 202 via the wireless LAN control circuit 212 to perform wireless LAN communication with other communication terminal devices. Note that the wireless LAN unit 202 is assumed to be capable of data (packet) communication by a communication method compliant with, for example, the IEEE 802.11 series (IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, etc.).

[0016] Also, the CPU 206 can detect an NFC connection with another NFC terminal and perform data transmission and reception with the other NFC terminal by controlling the NFC unit 203 via the NFC control circuit 213.

[0017] Furthermore, the CPU 206 controls the line connection unit 201 via the line control circuit 211 to connect to a mobile phone line network and perform calls and data transmission and reception. Also, it may be provided with a unit for performing the communication method of Bluetooth (registered trademark) Low Energy (BLE).

[0018] The CPU 206 can control the operation unit control circuit 214 to display on the touch panel display 204 or receive operations from the user. Further, the CPU 206 can control the camera unit 215 to capture an image and store the captured image in the image memory 209 in the data memory 208. In addition to the captured image, it is also possible to store an image acquired from the outside through a mobile phone line network, a wireless LAN, or NFC in the image memory 209, or conversely, transmit it to the outside.

[0019] The non-volatile memory 210 is composed of a memory such as a flash memory and can store data that needs to be stored even after the power is turned off. For example, in addition to phone book data, various communication connection information, device information connected in the past, etc., image data that needs to be stored is also stored. The application management information managed by the application for creating posters in this embodiment is also stored in the non-volatile memory 210.

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

[0021] <Configuration of the printing device> FIG. 3 is a block diagram showing the configuration of the printing device 300. The printing device 300 includes 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 the communication unit of the printing device 300.

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

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

[0024] The CPU 305 controls the wireless LAN unit 301 through the wireless LAN control circuit 310 to perform wireless LAN communication with other communication terminal devices 200. Note that the wireless LAN unit 301 is assumed to be capable of data (packet) communication by a communication method compliant with, for example, the IEEE 802.11 series (IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, etc.).

[0025] Also, the CPU 305 controls the NFC unit 302 via the NFC control circuit 311 to detect an NFC connection with another NFC terminal and perform data transmission and reception with the other NFC terminal.

[0026] The CPU 305 can control the operation panel 303 by controlling the operation unit control circuit 312 to display the status of the printing device 300 and a function selection menu, or receive operations from the user.

[0027] The printing device 300 of this embodiment can receive and print data in the JPEG file format with a printer control command.

[0028] Furthermore, the printing device 300 may be a printing device capable of printing using special inks. Special inks are inks that express special features (hereinafter also referred to as "spot colors"). For example, they are inks whose colors expressed during printing cannot be displayed in the sRGB color space. That is, the printer 14 is configured to be capable of spot color printing, which is printing using spot color inks (i.e., special inks, hereinafter also referred to as "spot color inks") other than ordinary inks.

[0029] "Ordinary inks" are inks for printing process colors (normal colors), such as inks of colors such as cyan (C), magenta (M), yellow (Y), and black (K) that are the basis of process colors. Note that a process color is a color represented by one of CMYK or a combination of two or more of CMYK.

[0030] Also, in this embodiment, fluorescent pink ink and fluorescent orange ink are used as spot color inks. That is, a spot color is a color different from a process color and cannot be expressed only by one of CMYK or a combination of two or more of CMYK.

[0031] However, it is not limited to this form, and the number and colors of spot color inks may be arbitrary, and non-fluorescent color inks may be used. For example, as spot color inks, violet ink, green ink, orange ink, gold ink, silver ink, etc. may be used. Also, other metallic color inks may be used. Furthermore, inks in which special inks and other inks (e.g., ordinary inks) are blended may also be treated as special inks.

[0032] In this embodiment, information indicating that an object is printed with a feature (referred to as feature information) is associated with an object to be printed with a feature among the image data. Then, pixels with the feature information added are printed according to the feature corresponding to the RGB values of the pixels. Note that the RGB values of the pixels corresponding to the feature can also be used as the RGB values of the pixels corresponding to the color represented by only normal ink (i.e., the normal color). In other words, the same RGB values as those of the pixels corresponding to the feature may be set for the pixels corresponding to the color represented by only normal ink. In that case, whether to use special ink for printing the pixels with the RGB values is controlled by whether special color information is added.

[0033] <Configuration of Web Application Server> FIG. 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.

[0034] The CPU 421 controls the entire Web application server 102 by expanding and executing the program stored in the non-volatile memory 423 in the volatile memory 422. Also, the CPU 421 realizes modules implemented by software such as the Frontend 400 and Backend 404 shown in FIG. 4B by executing the above program. Further, the communication circuit 424 can communicate with the terminal device 200 via the Internet.

[0035] <Software Configuration> Figure 4B is a diagram showing the software configuration within the Web application server 102. The Frontend 400 mainly controls the display of the Web browser of the terminal device. Specifically, the Frontend 400 manages and holds programs (JavaScript) executed on the browser. Specifically, it manages and holds programs (JavaScript) for executing a UI (User Interface) control unit 402 that controls user operations on the browser, a work editing unit 401 that performs work editing processing created by the application, and a user authentication unit 403 that performs user authentication. Then, the Frontend 400 transmits those programs to the terminal device, causing the Web browser of the terminal device to perform display according to 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.

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

[0037] 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 printing application 501 is an application program that performs printing based on printing settings made by the user. The printing application 501 has a printing setting processing unit 502 that performs printing settings and a thumbnail display unit 503 that performs thumbnail display. Also, in this embodiment, the printing application 501 is downloaded and installed on the terminal device from a server different from the Web application server 102 and is thus stored on the terminal device.

[0038] When the terminal device is a PC, the printer driver 504 performs the generation process of the print data. 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 after installation. It may also be included in the OS.

[0039] The model information 505 stores print setting information and the like that can be used by the printer. Specifically, setting values that can be used by the printer and function information are listed. Examples of the available setting values include setting values for the paper feeding method, the type of paper, etc. Examples of the available function information include information on whether the spot color printing function can be used.

[0040] 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 described. In the case of a mobile terminal, there is no printer driver. Therefore, a print processing module 507 that performs the print data generation process 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 the model information 505 and stores it in the data memory 208 or the non-volatile memory 210 (see Figure 2).

[0041] <Configuration of the Application> Figure 6 is a diagram showing the screen of the web application displayed on the browser by the UI control unit 402. As described above, this screen is displayed on the browser of the terminal device when the program held by the Frontend 400 is transmitted to the terminal device.

[0042] In this embodiment, an example where the Web application is an application for printing posters will be described. When any one of the template button 600, photo button 601, and clip art button 602 is pressed, a list of contents 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 will edit the template and finally generate work data. Here, the work data includes image data and various printing settings.

[0043] When the photo button 601 is pressed, a list of selectable images is displayed in the list display area 603. When a desired image is selected, it is added on top of 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 the list display area 603. When a desired clip art is selected, it is added on top of 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 the Canvas format.

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

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

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

[0047] In the original document size selection section 609, a desired original document size can be selected. The finally completed work data includes original document size information, information on clip art to which spot color is applied, and information on the R, G, B values to which spot color is applied.

[0048] FIG. 7 is a diagram showing the screen of the print application 501. In this embodiment, the case where the terminal device 200 is a mobile terminal will be described as an example, but the achievable effects are the same as those when the terminal device 200 is a PC. Note that FIG. 7 is a screen not displayed on the web browser, and the display content is controlled by the print application 501, which is a program other than the program transmitted from the Web application server 102.

[0049] In the preview display area 700, a thumbnail of the work data to be printed created by Backend404 is displayed. The printer selection section 701 can select a printer for printing. When the terminal device 200 is a mobile terminal, it is necessary to register in advance the printers that can be selected in order to display the printers that can be selected by the printer selection section 701.

[0050] In the paper feeding method selection section 702, a list of paper feeding methods available for the selected printer is displayed, and a desired paper feeding method can be selected from the list. In the paper type selection section 703, a list of paper types available for the selected printer is displayed, and a desired paper type can be selected from the list.

[0051] The enlargement / reduction printing selection section 704 has a checkbox. When it is checked, enlargement / reduction processing is performed and printed according to the radio button placed under the checkbox. When the long side fit button 705 is selected, enlargement processing is performed so that the roll paper width provided in the printing device 300 matches the long side of the work data, and then printed. When the short side fit button 706 is selected, enlargement processing is performed so that the roll paper width provided in the printing device 300 matches the short side of the work data, and then printed.

[0052] When the fit to printable area button 707 is selected, enlargement / reduction processing is performed and printed according to the output paper size selection section 708 placed under the button. The list displayed in the output paper size selection section 708 lists only the paper sizes that can be selected by the selected printer. When the checkbox in the enlargement / reduction printing selection section 704 is not checked, the radio buttons placed below are in a non-selectable state.

[0053] The special ink selection section 709 has check boxes and can be used to select whether to use special ink. When the check is enabled, printing with the special ink applied is performed according to the radio buttons arranged under the check box. When the button 710 for using the fluorescent spot color is selected, the clip art portion selected in the fluorescent spot color palette area 608 is printed in the fluorescent spot color. When the button 711 for making the whole vivid is selected, when rendering the work data into RGB data, the predetermined R, G, and B pixels are printed in the fluorescent spot color.

[0054] If the check box of the special ink selection section 709 is not checked, the radio buttons arranged below are in a non-selectable state. Also, if the work data does not include information on the fluorescent spot color, the check box of the special ink selection section 709 is in a non-selectable state. Further, in the present embodiment, the terminal device can control the display content according to the capabilities of the printer for the screen using the printing application 501. Therefore, regardless of whether the work data includes information on special ink, the terminal device checks the model information 505 and controls the check box of the special ink selection section 709 to be in a non-selectable state even when the printer cannot use spot color. In other words, when the work data created by the Web application server 102 includes information on special ink and the printer to which the print data is to be sent cannot use special ink, the printing settings related to printing using special ink cannot be executed in the printing application 501. Specifically, the screen for executing the printing settings is not displayed in the printing application 501. Note that the case where the work data created by the Web application server 102 includes information on special ink means that, in the Web application server 102, as a setting for printing the work data created by the Web application server 102, the settings related to printing using special ink are executed.

[0055] <Overall Sequence> Using the sequence diagram of FIG. 8, the main operation of the entire system will be described. Details of the individual processes of the program (hereinafter referred to as the Frontend program) transmitted from the Frontend 400 to the terminal device, the Backend 404, and the printing application 501 will be described later. Note that the processes described as the processes executed by the Backend 404 are actually realized by the CPU 421 of the Web application server 102 executing the program corresponding to the Backend 404. Also, the processes described as the processes executed by the Frontend program are actually realized by the CPU 206 executing the Frontend program. Also, the processes described as the processes executed by the printing application 501 are actually realized by the CPU 206 executing the printing application 501.

[0056] When the user generates work data using a browser and the button 606 to proceed to printing is pressed, in step S801, the Frontend program requests the Backend 404 to create a print job. In step S802, the Backend 404 creates a thumbnail to pass to the printing application 501. Subsequently, in step S803, the Frontend program launches the printing application 501.

[0057] After the printing application 501 is launched, in step S804, it performs an authentication process. After the completion of the authentication process, in step S805, the printing application 501 receives the thumbnail from the Backend 404 and launches the screen of FIG. 7. When the user makes printing settings and presses the print button in step S806, the printing application 501 requests the Backend 404 to render the work data in step S807.

[0058] Next, Backend404 renders the work data in step S808. Next, the printing application 501 receives the rendered data in step S809. The printing 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.

[0059] <Flow of each process> FIG. 9 is a flowchart showing the operations executed by the terminal device by the Frontend program. The processes shown in this flowchart are realized by the CPU 206 executing the Frontend program.

[0060] When the user opens the web browser 500 on the CPU 206 on the terminal device and enters the URL of the web application server 102, the CPU 206 displays a screen for authentication (not shown) by the user authentication unit 403 in step S901.

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

[0062] When an event is received in step S905, in step S906, the CPU 206 determines whether the received event is an event related to editing. If the received event is an event related to editing, in step S907, the CPU 206 performs editing processes such as template editing by the work editing unit 401.

[0063] 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 export processing of the work data.

[0064] In step S910, the CPU 206 determines whether the received event is a press event of the button 606 to proceed to printing. If the received event is a press event of the button 606 to proceed to printing, in step S912, the CPU 206 transmits job information including mainly the work data and the Token information acquired at the time of authentication to the Frontend 400.

[0065] In step S913, the CPU 206 starts the printing application 501 in the terminal device. By registering the custom URL scheme of the printing application 501 with the OS and calling that scheme from the web browser, the printing application 501 can be started from the Frontend program. Regarding the method of starting from the browser, for example, it may be performed by a method other than starting by the custom URL scheme such as FireBaseDynamicLink.

[0066] In step S911, the CPU 206 determines whether the received event is an event instructing the termination of the application. If the received event is an event instructing the termination of the application, this flow ends. Otherwise, it returns to step S904 and enters the event waiting state.

[0067] FIG. 10 is a flowchart showing the operation of the 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 the Backend 404.

[0068] In step S1001, Backend404 receives job information from Frontend400. Note that the job information is sent from the terminal device to Frontend400.

[0069] In step S1002, Backend404 checks the Token information included in the job information. If the Token information is in an invalid state such as expired, Backend404 displays an error in step S1012 and ends the process.

[0070] If the check of the Token information is completed correctly, in step S1003, Backend404 renders the work data included in the job information and generates a thumbnail. The generated thumbnail may be JPEG data or PNG data. Then, in step S1004, Backend404 enters a waiting state for a request from the printing application 501.

[0071] In step S1005, when Backend404 receives a request from the printing application 501, in step S1006, it checks the Token information included in the request of the printing application 501. If the Token information is in an invalid state such as expired, Backend404 displays an error in step S1012 and ends the process.

[0072] If the check of the Token information is completed correctly, in step S1007, Backend404 determines whether the request of the printing application 501 is a thumbnail request. If the request of the printing application 501 is a thumbnail request, in step S1008, Backend404 sends the thumbnail created in step S1003 to the printing application 501.

[0073] In step S1009, Backend404 determines whether the request of the printing application 501 requires rendering. If the request of the printing application 501 requires rendering, then in step S1010, Backend404 performs rendering based on the size information included in the printing application 501. The data after rendering may be JPEG data or PNG data. If the request of the printing application 501 does not require rendering, it returns to step S1004 and waits for a request from the printing application 501.

[0074] In step S1011, Backend404 sends the rendered rendering data to the printing application 501.

[0075] Figure 11 is a flowchart showing the operation of the printing application 501. The processes shown in this flowchart are realized by the CPU 206 executing the printing application 501. Also, the processes described as the processes executed by the printing application 501 are assumed to be actually realized by the CPU 206 executing the printing application 501.

[0076] Since the user using the printing application 501 needs to be the same as the user who created the work data in the Frontend program, the printing application 501 displays a screen for authentication in step S1101. When the user inputs the login ID and password, the user authentication section of the printing application 501 checks in step S1102 whether the input information is registered information. If the user is a registered user, the printing application 501 transitions to the process of the printing settings screen in step S1103. If the user is not a registered user, it returns to step S1101 and displays the authentication screen again.

[0077] FIG. 12 is a flowchart showing the operation of the print settings screen. The processing shown in this flowchart is realized by the CPU 206 executing the print application 501.

[0078] In step S1201, the print application 501 acquires a thumbnail from the Backend 404. In step S1202, the print application 501 displays the print settings screen, and in step S1203, it enters a state of waiting for an event.

[0079] When the print application 501 receives an event in step S1204, it 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 a process to update the print settings in step S1206.

[0080] 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 the print process in step S1208. Details of the print process will be described later.

[0081] In step S1209, the print application 501 determines whether the event is an event instructing the termination of the application. If the received event is an event instructing the termination of the application, this flowchart ends. Otherwise, it returns to step S1203 and enters a state of waiting for an event.

[0082] FIG. 13 is a flowchart showing the operation of the print process. The processing shown in this flowchart is realized by the CPU 206 executing the print application 501.

[0083] In step S1301, the printing application 501 calculates the rendering size to request from the Backend 404. If the checkbox in the magnification / reduction printing selection section 704 on the printing settings screen is not checked, the rendering size is calculated from the manuscript size information received from the Frontend program. If the checkbox in the magnification / reduction printing selection section 704 is checked and "fit to printable area" is selected, the rendering size is calculated based on the output paper size. When the long side fit button 705 is selected, since an enlargement process is performed such that the roll paper width provided in the printing apparatus 300 matches the long side of the work data, the calculation is made to obtain the size at the time of enlargement. When the short side fit button 706 is selected, since an enlargement process is performed such that the roll paper width provided in the printing apparatus 300 matches the short side of the work data, the calculation is made to obtain the size at the time of enlargement.

[0084] In step S1302, the printing application 501 requests the Backend 404 to perform rendering. In step S1303, the printing application 501 checks whether the rendering has been completed. If the rendering has not been completed, it waits until it is completed.

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

[0086] As described above, in the above-described embodiment, a work editing unit, a UI control unit, a user authentication unit, and a rendering processing unit are provided in the server, and model information, a print setting processing unit, and a print data generation processing unit are provided in the terminal device. Then, according to the print settings determined in the print setting process of the terminal device, the rendering size is determined, rendering is requested from the server in that size, and the rendered data is received to generate print data. With such a configuration, it is possible to edit work data without installing a dedicated application on a terminal device such as a PC or a tablet, and to print content without performing a complicated authentication process with a printer.

[0087] [Other Embodiments] It goes without saying that the object of the present invention can also be achieved by supplying a recording medium recording a program code of software that realizes the functions of the above-described embodiment to a system or an apparatus, and causing a computer (or a CPU or an MPU) of the system or the apparatus to 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-described embodiment, and the storage medium storing the program code constitutes the present invention.

[0088] As a storage medium for supplying the program code, 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. can be used.

[0089] Further, by executing the program code read by the computer, not only the functions of the above-described embodiment are realized, but also based on the instructions of the program code, an Operating System (OS) or the like running on the computer performs part or all of the actual processing, and it goes without saying that the case where the functions of the above-described embodiment are realized by the processing is also included.

[0090] Furthermore, after the program code read from the storage medium is written into the memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, based on the instructions of the program code, a CPU or the like provided in the function expansion board or the function expansion unit performs part or all of the actual processing, and it goes without saying that the case where the functions of the above-described embodiments are realized by this processing is also included.

Explanation of Signs

[0091] 100: Access Point, 101: User Authentication Server, 102: Web Application Server, 200: Terminal Device, 300: Printing Device, 1000: Printing Processing System

Claims

1. 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.

2. 2. The image processing system according to claim 1, wherein the terminal device transmits the print data to a printing device.

3. 3. The image processing system according to claim 1, wherein the server device further comprises a UI control unit for controlling a user interface.

4. 4. The image processing system according to claim 1, wherein the server device further comprises a user authentication unit for authenticating a user.

5. 5. The image processing system according to claim 1, wherein the terminal device further comprises a storage unit for storing model information of a printing device that prints the image data.

6. An image processing system as described in any one of claims 1 to 5, characterized in that when settings for printing using special ink are executed on 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 for printing using special ink.

7. 7. The image processing system according to claim 1, wherein a print application that operates on the terminal device and realizes the setting unit and the generating unit is started in response to an instruction from the server device.

8. 8. The image processing system according to claim 7, wherein the server device performs rendering of the image data in response to an instruction from the print application.

9. 9. The image processing system according to claim 1, wherein the terminal device enables printing of the image data after authenticating a user.

10. 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 means 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.

11. 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.

12. 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.

13. 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.

14. A program for causing a computer to execute each step of the control method according to claim 12 or 13.

15. 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