JP7828237B2 - System, method and program - Google Patents

Description

The present invention relates to a system, method, and program.

An image processing system is known in which data for a work created using a web application is imported into an application installed on a terminal device and output from a printing device. Patent Document 1 describes a configuration in which print data is sent and received directly between a server and a printing device. Patent Document 1 also describes how a printer's authentication token is linked to image data and managed by the server, allowing the printer to request previously printed data from the server.

Japanese Patent Application Laid-Open No. 2015-179361

When processing data created by a web application via an application installed on a device, it is necessary to improve convenience and ensure security.

The present invention aims to provide a mechanism that improves convenience and ensures security when processing data created by a web application via the application.

To solve the above problem, the program of the present invention causes a computer of an information processing device to function as follows: in the web application, when an instruction to process data stored on a server providing the web application is received from a user on a web application screen displayed by a web browser, a first request means in the web application that requests temporary authentication information from the server; a first receiving means in the web application that receives the authentication information sent from the server in response to the request by the first request means; a first acquisition means in an application installed on the information processing device and executing the process that acquires the authentication information received by the first receiving means; a second request means in the application that requests account information issued to the user from the server using the authentication information; a second acquisition means in the application that acquires and holds the account information sent from the server in response to the request by the second request means; and a processing means in the application that acquires and processes the data from the server using the account information.

This invention makes it possible to improve convenience and ensure security when printing data created in a web application via a print application.

FIG. 1 illustrates a configuration of a print processing system. FIG. 2 is a block diagram showing the hardware configuration of a terminal device. FIG. 2 is a block diagram showing the hardware configuration of the printing apparatus. FIG. 2 is a block diagram showing the hardware configuration of a Web server. FIG. 2 is a block diagram showing the software configuration of a Web server. FIG. 2 is a block diagram showing the software configuration of the terminal device. FIG. 10 is a diagram showing a screen of a web application. FIG. 10 is a diagram illustrating a screen of a printing application. FIG. 10 is a sequence diagram showing a process for creating a poster image using a web application. FIG. 10 is a sequence diagram illustrating a printing process performed by a printing application. FIG. 10 is a sequence diagram showing a process of restoring a guest ID.

The following describes the embodiments in detail with reference to the attached drawings. Note that the following embodiments do not limit the scope of the claimed invention. While the embodiments describe multiple features, not all of these features are necessarily essential to the invention, and multiple features may be combined in any desired manner. Furthermore, in the attached drawings, the same reference numbers are used to designate identical or similar components, and redundant explanations will be omitted.

[First embodiment]
FIG. 1 illustrates an example of the configuration of a print processing system according to this embodiment. The print processing system includes a terminal device 101, a printing device 102, and a web server 103. A user can print data created using a web application provided by the web server 103 via the printing application. The terminal device 101 is an information processing device such as a smartphone, a personal computer (PC), a tablet device, a mobile phone, or a personal digital assistant (PDA). The printing device 102 is a printer that applies a recording agent such as ink to a recording medium such as paper to form (print) an image on the recording medium. The printing device 102 may also be a multifunction device equipped with multiple functions, such as a copying function, a fax function, and a printing function. Note that in this embodiment, the printing device 102 is assumed to be a device that prints using an inkjet recording method. However, the present invention is not limited to this configuration and may be a device that prints using an electrophotographic method or a thermal dye sublimation method, for example.

The terminal device 101 communicates with the printing device 102 via a network established by the access point 100. The terminal device 101 stores programs such as a printing application, which will be described later. Therefore, print data is sent from the terminal device 101 to the printing device 102 via the network using the printing application. The access point 100 also functions as, for example, a wireless LAN router, and the terminal device 101 is connected to the Internet via this wireless LAN router. Therefore, the terminal device 101 can communicate via the Internet with a web server 103, which controls a web application, which will be described later. The terminal device 101 and the printing device 102 may each be connected to the access point 100 via a wired LAN. The terminal device 101 and the printing device 102 may also be connected to each other via a wired LAN.

Figure 2 is a block diagram showing an example of the hardware configuration of the terminal device 101. As an example, the terminal device 101 has an input interface 201, a CPU 202, a ROM 203, a display unit 204, a RAM 205, an external storage device 206, a communication unit 207, and a short-range wireless communication unit 208. Note that the blocks shown in Figures 2 to 4 below are interconnected using, for example, an internal bus. Also, in Figures 2 to 4, multiple blocks may be combined into a single block, or a single block may be divided into two or more blocks.

The CPU 202 is a system control unit that controls the entire device. The RAM 205 is composed of, for example, static RAM (SRAM), which requires a backup power source. Because the RAM 205 uses a primary battery (not shown) for data backup, it can store data such as program control variables without volatilizing them. The RAM 205 also has a memory area for storing configuration information and management data for the terminal device 101. The RAM 205 is also used as the main memory and work memory for the CPU 202. The ROM 203 stores fixed data such as control programs, data tables, and OS programs executed by the CPU 202. The ROM 203 also stores the printing application described above. The operation of the terminal device 101 in this embodiment is realized, for example, by the CPU 202 reading programs stored in the ROM 203 into the RAM 205 and executing them.

The display unit 204 is composed of an LED (light-emitting diode) or LCD (liquid crystal display), and displays a UI screen based on various data. The display unit 204 may also be composed of a touch display or the like, and have the function of accepting various inputs from the user. In other words, the display unit 204 is an interface for accepting data inputs and operational instructions from the user, and may also be an operation panel composed of a physical keyboard, buttons, touch panel, etc.

The communication unit 207 includes a circuit and an antenna for communicating according to a specified wireless communication method. For example, the communication unit 207 can wirelessly connect to the access point 100. The communication unit 207 may also operate as a temporary access point. The wireless communication used in this embodiment may be communication that operates according to a wireless LAN wireless communication method (Wi-Fi) that complies with the IEEE 802.11 standard series, or communication that operates according to another wireless communication method.

The short-range wireless communication unit 208 performs short-range wireless communication with other devices that are within a certain short-range range of the terminal device 101. Note that the short-range wireless communication unit 208 communicates using a wireless communication method different from that used by the communication unit 207. Examples of communication methods include Near Field Communication (NFC), Bluetooth (registered trademark) Classic, Bluetooth Low Energy (BLE), and Wi-Fi Aware.

Figure 3 is a block diagram showing an example of the hardware configuration of the printing device 102. In the printing device 102, the printing function is realized by the printer unit 301, the scanner function is realized by the scanner unit 302, and the storage function is realized by the memory card insertion unit 303 and memory card 304. The printer unit 301 executes printing based on image data received from an external device or image data stored on the memory card 304. The printer unit 301 also manages consumable information such as remaining ink and paper. The scanner unit 302 optically reads an original placed on a platen (not shown) and converts it into electronic data. The converted electronic data is further converted into a specified file format, and the converted image data is sent to an external device via a network or stored in a storage area (not shown) such as a HDD. The copy function is realized by the scanner unit 302 reading an original placed on the platen and generating image data, which is then transferred to the printer unit 301, which then prints an image based on the image data on a recording medium.

Various file data are stored on the memory card 304 inserted into the memory card insertion section 303. This file data can be read and edited by an external device via a network. The external device can also store file data on the memory card 304.

The printing device 102 further comprises a CPU 305, program memory 306, work memory 307, display unit 308, operation unit 309, network communication unit 310, network connection unit 311, and flash memory 312. The CPU 305 is a processor that provides overall control of each unit within the printing device 102. The program memory 306 is composed of ROM or the like, and stores various program codes and an application 314 for communicating with the web server 103. The application 314 can also access the printer unit 301 to obtain consumable information, for example, by sending the remaining amount of consumables to the web server 103 at a predetermined timing. The work memory 307 is composed of RAM or the like, and temporarily stores and buffers image data and the like when each service is executed. The operation of the printing device 102 in this embodiment is realized, for example, by the CPU 305 reading programs stored in ROM into RAM and executing them.

The display unit 308 is composed of LEDs (light-emitting diodes) and LCDs (liquid crystal displays), and displays UI screens based on various data. The operation unit 309 is composed of switches and other devices that allow the user to perform various input operations. The network communication unit 310 is connected to a network such as the Internet via the network connection unit 311 and performs various communications. The network communication unit 310 communicates with the outside world, for example, via a wired LAN or wireless LAN. If the network communication unit 310 is compatible with a wired LAN, the network connection unit 311 is, for example, a connector for connecting a wired LAN cable. If the network communication unit 310 is compatible with a wireless LAN, the network connection unit 311 is, for example, an antenna. The network connection unit 311 may be compatible with both wired and wireless LANs. In this embodiment, the network communication unit 310 is compatible with a wireless LAN and connects to the access point 100 in accordance with a wireless LAN wireless communication method compliant with the IEEE 802.11 standard series. Flash memory 312 is a non-volatile memory for storing image data received by network communication unit 310. The above-mentioned units are interconnected via bus 313.

In this embodiment, the printing device 102 may also be capable of printing using spot color inks. Spot color inks are inks that produce spot colors (hereinafter also referred to as "spot colors"). For example, these are colors that are produced during printing and cannot be displayed in the SRGB color space. In other words, the printing device 102 is configured to perform spot color printing, which is printing using spot color inks other than regular inks (i.e., spot color inks, hereinafter also referred to as "spot color inks"). "Regular inks" are inks used to print process colors (regular colors), such as cyan (C), magenta (M), yellow (Y), and black (K), which are the basis of process colors. Note that a process color is a color expressed using one color from the CMYK palette, or a combination of two or more colors from the CMYK palette. In this embodiment, fluorescent pink ink and fluorescent orange ink are used as spot color inks. In other words, spot colors are colors that differ from process colors and cannot be expressed using only one CMYK color or a combination of two or more CMYK colors. However, this is not limited to this example, and the number and colors of spot color inks may be arbitrary, and non-fluorescent inks may also be used. For example, violet ink, green ink, orange ink, gold ink, silver ink, etc. may be used as spot color inks. Other metallic inks may also be used. Furthermore, inks blended with spot color inks and other inks (e.g., regular inks) may also be treated as spot color inks. In this embodiment, objects in the image data that are to be printed in spot colors are associated with information indicating that they will be printed in spot colors (referred to as spot color information). Pixels to which spot color information is added are printed using the spot color corresponding to the RGB values of the pixel. The RGB values of pixels corresponding to spot colors can also be used as the RGB values of pixels corresponding to colors expressed using regular inks alone (i.e., regular colors). In other words, the same RGB values as those of a pixel corresponding to a spot color may also be set for a pixel corresponding to a color expressed using only regular ink. In such cases, whether or not special ink is used to print the pixel with that RGB value is controlled by whether or not spot color information has been added.

Figure 4 is a block diagram showing an example of the hardware configuration of the web server 103. The CPU 401 is a processor that provides overall control of the device. The disk device 402 stores various files, as well as application programs 412, databases 413, and the OS that are read by the CPU 401. The external storage media reader 403 is a device for reading information such as files stored on external storage media such as SD cards. The memory 404 is composed of RAM or the like, and is used by the CPU 401 to temporarily store and buffer data as needed. In this embodiment, the operation of the web server 103 is realized, for example, by the CPU 401 reading a program stored in the disk device 402 into the memory 404 and executing it.

The display unit 405 is composed of LEDs (light-emitting diodes) and LCDs (liquid crystal displays), and displays UI screens based on various data. The operation unit 406 is composed of a keyboard, mouse, and other devices that allow the user to perform various input operations. The network communication unit 407 is connected to a network such as the Internet via a network connection unit 408, and performs various communications. The network communication unit 407 communicates, for example, via a wired LAN or wireless LAN. If the network communication unit 407 is compatible with a wired LAN, the network connection unit 408 is, for example, a connector for connecting a wired LAN cable, and if the network communication unit 407 is compatible with a wireless LAN, the network connection unit 408 is, for example, an antenna. The network connection unit 408 may be compatible with both wired LAN and wireless LAN. The USB (Universal Serial Bus) communication unit 410 is connected to various peripheral devices via a USB connection unit 411, and performs various communications according to the USB standard. The above-mentioned components are interconnected via a bus 409. The web server 103 may also be a server system made up of one or more servers. That is, for example, multiple servers may work in conjunction with one another to function as a single web server 103.

Figure 5 is a block diagram showing an example of the software configuration of the web server 103. The front end 502 mainly controls the display of the web browser of the terminal device 101. Specifically, the front end 502 manages and stores programs (JavaScript) executed on the web browser. More specifically, it manages and stores programs (JavaScript) for executing a UI (user interface) control unit 504 that controls user operations on the browser, a poster editing unit 503 that processes editing of works such as posters created by the application, and a user authentication unit 507 that performs user authentication. The front end 502 is then sent (downloaded) to the terminal device 101, causing the web browser of the terminal device 101 to display the above programs. In other words, when the terminal device 101 receives the above programs, it uses the programs to display a screen corresponding to the programs on the web browser. The backend 505 is composed of a user management unit 506, a user authentication unit 507, a content management unit 508, and a rendering processing unit 509. The user management unit 506 manages user information that identifies users. For example, user information contained in cookies is managed. The user authentication unit 507 issues a unique identifier for each user in association with the user information. The identifier is account information, such as a guest ID (described below). The content management unit 508 manages content such as image data created by an application. The rendering processing unit 509 performs rendering processing on content managed by the content management unit 508. Note that the frontend 502 and the backend 505 may be held by separate servers.

Figure 6(a) is a block diagram showing an example of the software configuration when the terminal device 101 is a PC. The web browser 601 is a web browser, and may be, for example, Internet Explorer, Microsoft Edge, Google Chrome, Firefox, or Safari. The terminal device 101 downloads the front end 502 by accessing the web server 103 using a specific URL with the web browser 601. The front end 502 then runs on the web browser 601. In other words, once the front end 502 has been downloaded, it also becomes part of the software configuration of the terminal device 101.

The print application 602 is an application program (hereinafter simply referred to as the application) for printing based on print settings set by the user, and includes a print setting processing unit 603 and a thumbnail display unit 604. For example, the print application 602 is a native application associated with the web application 501, and is an application for causing a printing device to print content data created by the web application 501. The print setting processing unit 603 performs print settings. The thumbnail display unit 604 displays thumbnails based on poster image data (poster data) created by the user. In this embodiment, the print application 602 is downloaded and installed to the terminal device 101 from a server different from the web server 103, and is then saved in the terminal device 101. When the terminal device 101 is a PC, the printer driver 605 generates print data for printing on the printing device 102. The printer driver 605 includes printer model information 606 and a print data generation processing unit 607. The printer driver 605 is distributed by the printer vendor and can be used by the user after installation. The printer driver 605 may also be included with the OS. The model information 606 stores setting information that can be used when printing for each printer. Usable setting information includes, for example, the paper feed method setting and paper type.

Figure 6(b) is a block diagram showing an example of the software configuration when the terminal device 101 is a mobile terminal. The differences from Figure 6(a) will be explained. When the terminal device 101 is a mobile terminal, the printer driver 605 does not exist. Therefore, the terminal device 101 is configured with a print processing module 608 that performs print data generation processing. The print processing module 608 includes a model information acquisition processing unit 609. The model information acquisition processing unit 609 acquires model information 606 from the printing device 102. The acquired model information 606 is stored, for example, in the external storage device 206.

Figure 7 shows an example of a screen of the web application 501 displayed on the web browser 601 by the UI control unit 504 of the front end 502. As described above, this screen is displayed on the browser of the terminal device 101 by a program stored in the front end 502. In this embodiment, a web application for creating and printing a poster image will be described as an example. Area 701 is an area where a list of poster image templates is displayed. Area 702 is an area where a list of photos that can be pasted on the poster image is displayed. Area 703 is an area where a list of clip art that can be pasted on the poster image is displayed. For example, when a user selects a desired template from the list in area 701, the selected template is displayed in editing area 704 and becomes editable. The user can edit the template displayed in editing area 704 and generate poster data. When a user selects a desired object from the list in each of areas 702 and 703, the selected object is displayed superimposed on the template displayed in editing area 704. When the user presses the save button 705, the poster data created by the user is saved as content in the content management unit 508. When the user presses the print button 706, the print application 602, which will be described later, is launched. The user information restore button 707 will be described later.

Figure 8 shows an example of the screen of the print application 602. Because this screen is the screen of the print application 602, it is displayed without using the web browser 601. The preview display area 801 displays a thumbnail of the poster data created by the backend 505. The printer selection button 802 is a button that allows the user to select the desired printer, and when pressed, a list of connected printers is displayed. When the user presses the print button 803 while a thumbnail of the poster data is displayed in the preview display area 801, processing begins to print the poster image on the printer selected in the printer selection 803.

In the print processing system shown in Figure 1, a user creates a poster image on the web application 501 using the web browser 601 of the terminal device 101. The created poster image is printed on a recording medium using the print application 602.

Figure 9 shows the sequence from when a user accesses the web application 501 using the web browser 601 until an ID corresponding to the user is issued. Once an ID corresponding to the user is issued, the user is able to create a poster image on the web application 501. Note that Figure 9 shows the sequence between the front end 502, which accepts user operations via the web browser 601 of the terminal device 101, and the back end 505 on the web server 103 side. Note that the processing of the front end 502 is executed after the front end 502 has been downloaded to the terminal device 101. In other words, the processing of the front end 502 corresponds to the processing executed by the front end 502 on the terminal device 101. More specifically, the processing of the front end 502 is realized by the CPU 202 executing programs such as the front end 502 and the web browser 601 stored in the ROM 203, etc. The processing of the back end 505 corresponds to the processing executed by the web server 103 via the back end 505. More specifically, backend 505 processing is realized by the CPU 401 executing programs such as backend 505 stored in the disk device 402, etc.

In S901, the user accesses the web application 501 using the web browser 601 of the terminal device 101. Access to the web application 501 is performed, for example, by the web browser 601 accepting a URI specification input by the user.

In S902, the front end 502 sends the web page request received via the web browser 601 to the back end 505. When the web page request is sent, the web browser 601 also sends a cookie or the like containing user information to the web server 103 (back end 505). For example, if the processing in Figure 9 has been performed previously, the user information sent in S902 includes a guest ID, which will be described later.

In S903, the backend 505 determines whether the web page request from the frontend 502 includes user information. If it is determined that user information is included, the backend 505 further determines whether the user information exists in the user management unit 506.

In S904, if the backend 505 determines that the web page request sent in S902 does not contain user information, or if it determines that the user information contained in the web page request does not exist in the user management unit 506, the user authentication unit 507 issues a user identifier (hereinafter referred to as a guest ID (or guest account)) and stores it in the user management unit 506.

In S905, the backend 505 sends the web page and the issued guest ID to the frontend 502. In S906, the frontend 502 saves the guest ID received from the backend 505 in the web browser 601.

Thereafter, when the user accesses the web application 501, the guest ID stored in the web browser 601 is sent to the backend 505 as user information. The backend 505 can recognize that the accessing user is the same user based on the guest ID. In this way, in this embodiment, the user does not need to perform a login operation to the web application 501, and there is no need to create an account to log in, thereby improving convenience.

Once a guest ID is issued and saved in the web browser 601, the user can create a poster image on the web application 501. The data for the created poster image (poster data) is printed via the print application 602 in accordance with a user instruction. Poster data created by the user on the web application 501 using the web browser 601 is saved in the backend 505. Therefore, in order to print, the print application 602 must query the backend 505 to acquire the poster data created by the user. In this embodiment, when acquiring the poster data, the guest ID issued by the backend 505 in S904 and saved in the web browser 601 in S906 is used. Here, since the guest ID is secure information used to identify the user, a mechanism is required that can reduce the possibility of its leakage.

For this reason, this embodiment uses temporary authentication information (hereinafter referred to as a one-time password). By using a one-time password, the guest ID of the web browser 601 can be securely passed to the print application 602.

Figure 10 is a flowchart showing the process of passing the guest ID of the web browser 601 to the print application 602 using a one-time password. Note that in Figure 10, the sequence between the front end 502 and the print application 602 is performed within the terminal device 101. Note that the processing of the front end 502 is executed with the front end 502 downloaded to the terminal device 101. In other words, the processing of the front end 502 corresponds to the processing executed by the terminal device 101 using the front end 502. More specifically, the processing of the front end 502 is realized by the CPU 202 executing programs such as the front end 502 and the web browser 601 stored in the ROM 203, etc. Furthermore, the processing of the print application 602 corresponds to the processing executed by the terminal device 101 using the print application 602. More specifically, the processing of the print application 602 is realized by the CPU 202 executing programs such as the print application 602 stored in the ROM 203, etc. Furthermore, the processing of the backend 505 corresponds to the processing executed by the web server 103 via the backend 505. More specifically, the processing of the backend 505 is realized by the CPU 401 executing a program such as the backend 505 stored in the disk device 402 or the like.

In S1001, the user presses the print button 706 on the screen of the web application 501 displayed on the web browser 601 of the terminal device 101. In S1002, the front end 502 requests the back end 505 to create a print job for the poster data to be printed. In addition, in S1003, the front end 502 launches the print application 602 using the URL schema.

If this is the first time the print application 602 is launched, the print application 602 does not have user information (guest ID). In this case, the processes of S1004 to S1012 use the one-time password passed from the front end 502 to obtain the guest ID via the back end 505. On the other hand, if user information (guest ID) does exist, the process proceeds from S1003 to S1013, and a request for poster data is sent from the print application 602 to the back end 505 using the guest ID.

In S1004, the print application 602 launches the web browser 601. At this time, a session using the guest ID has already been established between the web browser 601 and the web server 103. After the web browser 601 is launched by the print application 602, in S1005 the front end 502 adds the guest ID held by the web browser 601 and sends a one-time password request to the back end 505. In S1003 and S1004, the front end 502 does not pass the guest ID held in the web browser 601 to the print application 602.

In S1006, the backend 505 generates (issues) a one-time password associated with the user of the guest ID received from the frontend 502. Then, in S1007, the backend 505 sends the generated one-time password to the frontend 502.

In S1008, the front end 502 adds the one-time password to the URL schema and launches the print application 602. Through this launch operation, the front end 502 passes the one-time password to the print application 602. In this way, the print application 602 obtains, via the front end 502, the one-time password that was issued in the back end 505 and associated with the guest ID. Also in S1008, the front end 502 does not pass the guest ID held in the web browser 601 to the print application 602.

In S1009, the print application 602 uses the one-time password acquired from the backend 505 to directly send a request for a guest ID to the backend 505. In this embodiment, when the print application 602 receives a one-time password from the frontend 502, it is configured to send the one-time password, an authentication key, and a request for a guest ID to the backend 505. Here, the authentication key is defined between the print application 602 and the backend 505 and is pre-installed in the print application 602. In other words, even if the backend 505 receives a one-time password, it will not return a guest ID unless it also receives a legitimate authentication key. For example, if the print application 602 is a fake print application, either no authentication key will be sent in S1009 or a fake authentication key will be sent. In this case, the backend 505 will not return a guest ID. Furthermore, in this embodiment, the frontend 502 does not directly pass the guest ID to the print application 602. Therefore, this embodiment reduces the possibility of the guest ID being leaked. Additionally, the transmission of the authentication key is limited to the expiration date specified by the one-time password, reducing the chances of the authentication key leaking to external networks.

In S1010, the backend 505 receives the one-time password and acquires the guest ID linked to the one-time password. Then, in S1011, the backend 505 sends the guest ID acquired in S1010 to the print application 602. Note that it is assumed here that the print application 602 is a legitimate print application. However, if the print application 602 is a fake print application, authentication using the above authentication key will fail, and the guest ID will not be sent in S1011. In S1012, the print application 602 saves the guest ID sent from the backend 502.

In this way, in this embodiment, by using a one-time password issued by the backend 505, the guest ID stored in the frontend 502 can be securely passed to the print application 602 via the backend 505.

In S1013, the print application 602 sends a request for poster data to the backend 505 using the guest ID saved in S1012. In S1014, the backend 505 renders the poster data for the print job requested in S1002 and sends the poster data along with the print job to the print application 602. In S1016, the print application 602 submits a print job to the printing device 102, which prints a poster image on a recording medium based on the poster data received in S1015.

As described above, according to this embodiment, a user can print poster data created on the web application 501 without logging in to a previously created account in the web application 501 and the print application 602. This eliminates the need to create an account in advance to link the print application 602 to the web application 501, improving convenience. Linking the print application 602 to the web application 501 means making the poster data created on the web application 501 printable by the print application 602. Furthermore, in this embodiment, the user does not need to create an account in advance for linking, so the print application 602 and the web application 501 can be linked without communicating with a management server that manages accounts previously created by the user. In other words, the print application 602 and the web application 501 can be linked simply by communication between the web server 103 having the backend 505 and the terminal device 101 having the frontend 502 and the print application 602. This also eliminates the need for an authentication server that authenticates users individually, simplifying the configuration leading up to printing. Furthermore, the guest ID used to identify the user can be securely passed to the print application 602.

In this embodiment, poster data has been described as an example of print data to be printed by the printing device 102, but it is not limited to poster data. It is not limited to data for large-format printing such as poster printing, but may also be print data of a relatively small size, such as a postcard. The operation of this embodiment can be applied as long as the configuration allows image data created by the user on the web application 501 to be printed on the printing device 102 using the print application 602.

Second Embodiment
The second embodiment will be described below, focusing on differences from the first embodiment. In FIG. 9 , the backend 505 identifies users based on user information, such as cookies, stored in the web browser 601. Therefore, if the web browser 601 history is deleted or the user uses a different browser installed on the terminal device 101, the user is treated as a different user. Specifically, because user information is not sent in S902, a new guest ID is issued in the backend 505, and the new guest ID is returned to the frontend 502 and saved in the web browser 601 in S905. This means that the frontend 502 cannot display data created using the old guest ID saved in the backend 505. Therefore, in this embodiment, a process is performed to restore the old guest ID to the web browser 601 using the print application 602 that saves the old guest ID.

Figure 11 is a sequence diagram showing the process of restoring the guest ID of the web browser 601 using the print application 602. Note that in Figure 11, the sequence between the front end 502 and the print application 602 is performed within the terminal device 101. In this embodiment, it is assumed that the guest ID (first guest ID) is stored in the print application 602 by the operation of the first embodiment, and that the guest ID is not stored in the web browser 601 due to the above case.

In S1101, the user accesses the web application 501 using the web browser 601 of the terminal device 101. Access to the web application 501 is performed, for example, by the web browser 601 accepting a URI specification input by the user.

In S1102, the front end 502 sends the web page request received via the web browser 601 to the back end 505. When the web page request is sent, the web browser 601 also sends a cookie or the like containing user information to the web server 103 (back end 505).

When a web page request is sent in S1102, the sent information does not include a guest ID. Therefore, in S1103, the backend 505 considers the user to be a new user and issues a new guest ID (second guest ID), and in S1104 sends the web page and the issued second guest ID to the frontend 502. The frontend 502 saves the second guest ID received from the backend 505 in the web browser 601.

At this point, the first guest ID is not saved in the web browser 601, and the front end 502 cannot display the poster data created with the first guest ID. In this embodiment, even in such a case, pressing the user information restore button 707 restores the first guest ID to the web browser 601, making it possible to display the poster data created with the first guest ID on the front end 502.

In S1105, the user presses the user information restore button 707 on the screen of the web application 501 displayed in the web browser 601. In S1106, the front end 502 adds the second guest ID to the URL schema and launches the print application 602.

In S1107, after startup, the print application 602 reads the first guest ID. At this time, the print application 602 may save or discard the second guest ID received from the front end 502 in S1106. If multiple guest IDs are saved and can be managed, in S1107, the print application 602 may display a list of guest IDs that can be restored on its screen, allowing the user to select the guest ID they wish to restore. In S1108, the print application 602 launches the web browser 601 and shares the first guest ID read in S1107 with the web browser 601.

In S1109, the web browser 601 sends a request for poster data to the backend 505 using the first guest ID shared with the print application 602 in S1108. In S1110, the backend 505 reads the poster data corresponding to the first guest ID and sends it to the frontend 502 in S1111. This enables the frontend 502 to display data created by the user identified by the first guest ID. In S1112, the frontend 502 saves the first guest ID shared with the print application 602 in S1108 in the web browser 601.

As described above, according to this embodiment, a guest ID that has once expired can be restored from the print application 602 by using a new web browser, making it possible to access poster data created with a previous guest ID again.

The present invention can also be realized by supplying a program that realizes one or more of the functions of the above-described embodiments to a system or device via a network or storage medium, and 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 realizes one or more functions.

The disclosure of the present embodiment includes the following programs, systems, and methods.
(Item 1)
The computer of the information processing device,
a first request means for, when an instruction to process data stored in a server that provides a web application is received from a user on a screen of the web application displayed by a web browser, requesting temporary authentication information from the server in the web application;
a first receiving means, in the web application, for receiving the authentication information transmitted from the server in response to the request made by the first requesting means;
a first acquisition means for acquiring the authentication information received by the first reception means, in an application that is installed in the information processing device and that executes the process;
a second request means, in the application, for requesting account information issued to the user from the server using the authentication information;
a second acquisition means, in the application, for acquiring and holding the account information transmitted from the server in response to the request made by the second request means;
a processing means in the application for acquiring the data from the server using the account information and processing the data;
A program to function as a
(Item 2)
2. The program according to item 1, wherein the web browser is started by the application before the first acquisition unit acquires the authentication information.
(Item 3)
3. The program according to item 1 or 2, wherein the application obtains the account information from a back end of the web application, and does not obtain the account information from a front end of the web application.
(Item 4)
4. The program according to claim 1, wherein the request for authentication information by the first request means is made when the account information is not held in the application.
(Item 5)
5. The program according to any one of items 1 to 4, further causing a computer to function as a receiving unit for receiving the account information issued to the user by the server in the web application.
(Item 6)
a launching means for launching the application in the web application when the receiving means receives second account information different from the account information from the server while the account information is held in the application;
a third acquisition means for acquiring the account information from the application started by the starting means, in the web application;
6. The program according to item 5, further causing a computer to function as:
(Item 7)
7. The program according to item 6, wherein the launching means launches the application by accepting an instruction from the user on a screen of the web application.
(Item 8)
8. The program according to item 6 or 7, further causing a computer to function as a fourth acquisition means in the web application that acquires the data from the server using the account information acquired by the third acquisition means.
(Item 9)
9. The program according to any one of items 1 to 8, wherein the account information is a guest account.
(Item 10)
10. The program according to any one of items 1 to 9, wherein the web application is a web application for creating content.
(Item 11)
11. The program according to any one of items 1 to 10, wherein the application is a native application for causing a printing device to print content created by the web application.
(Item 12)
A system including a server and an information processing device,
The information processing device includes:
a first request means for, when an instruction to process data stored in a server that provides a web application is received from a user on a screen of the web application displayed by a web browser, requesting temporary authentication information from the server by the web application;
a first receiving means for receiving, by the web application, the authentication information transmitted from the server in response to the request made by the first requesting means;
a first acquisition means for acquiring the authentication information received by the first reception means by an application that is installed on the information processing device and that executes the process;
a second request means for requesting account information issued to the user from the server using the authentication information by the application;
a second acquisition means for acquiring and storing the account information transmitted from the server in response to a request from the second request means by the application;
a processing means for acquiring the data from the server using the account information by the application and processing the data;
The server
an issuing means for issuing the account information based on information used in accessing the server by the web browser;
a first transmitting means for generating the authentication information corresponding to the account information in response to a request from the first requesting means and transmitting the generated authentication information to the information processing device;
and second transmission means for transmitting the account information to the information processing device in response to a request from the second request means.
A system characterized by:
(Item 13)
Item 13. The system according to item 12, wherein the information used in accessing the server by the web browser is a cookie.
(Item 14)
A method executed in an information processing device,
a first request step of requesting temporary authentication information from a server that provides a web application when an instruction to process data stored in the server is received from a user on a screen of the web application displayed by a web browser;
a first receiving step of receiving, by the web application, the authentication information transmitted from the server in response to the request made in the first requesting step;
a first acquisition step of acquiring the authentication information received in the first reception step by an application that is installed in the information processing device and that executes the process;
a second request step of requesting account information issued to the user from the server using the authentication information by the application;
a second acquisition step of acquiring and storing the account information transmitted from the server in response to the request in the second request step by the application;
a processing step of acquiring the data from the server using the account information by the application and processing the data;
A method having the following.
(Item 15)
A method executed in a system including a server and an information processing device,
In the information processing device,
a first request step of requesting temporary authentication information from a server that provides a web application when an instruction to process data stored in the server is received from a user on a screen of the web application displayed by a web browser;
a first receiving step of receiving, by the web application, the authentication information transmitted from the server in response to the request made in the first requesting step;
a first acquisition step of acquiring the authentication information received in the first reception step by an application that is installed in the information processing device and that executes the process;
a second request step of requesting account information issued to the user from the server using the authentication information by the application;
a second acquisition step of acquiring and storing the account information transmitted from the server in response to the request in the second request step by the application;
a processing step of acquiring the data from the server using the account information by the application and processing the data;
In the server,
an issuing step of issuing the account information based on information used in accessing the server by the web browser;
a first transmission step of generating the authentication information corresponding to the account information in response to the request in the first request step and transmitting the authentication information to the information processing device;
a second transmitting step of transmitting the account information to the information processing device in response to the request in the second requesting step;
A method comprising:

The invention is not limited to the above-described embodiments, and various modifications and variations are possible without departing from the spirit and scope of the invention. Therefore, the following claims are appended to clarify the scope of the invention.

101 Terminal device: 102 Printing device: 103 Web server: 202, 305, 401 CPU

Claims (15)

The computer of the information processing device,
a first request means for, when an instruction to process data stored in a server that provides a web application is received from a user on a screen of the web application displayed by a web browser, requesting temporary authentication information from the server in the web application;
a first receiving means, in the web application, for receiving the authentication information transmitted from the server in response to the request made by the first requesting means;
a first acquisition means for acquiring the authentication information received by the first reception means, in an application that is installed in the information processing device and that executes the process;
a second request means, in the application, for requesting account information issued to the user from the server using the authentication information;
a second acquisition means, in the application, for acquiring and holding the account information transmitted from the server in response to the request made by the second request means;
a processing means in the application for acquiring the data from the server using the account information and processing the data;
A program to function as a The program described in claim 1, characterized in that the web browser is launched by the application before the first acquisition means acquires the authentication information. The program described in claim 1 or 2, characterized in that the application obtains the account information from the backend of the web application, and not from the frontend of the web application. The program described in claim 1 or 2, characterized in that the request for authentication information by the first request means is made when the account information is not stored in the application. The program described in claim 1 or 2 further causes a computer to function as a receiving means for receiving the account information issued to the user by the server in the web application. a launching means for launching the application in the web application when the receiving means receives second account information different from the account information from the server while the account information is held in the application;
a third acquisition means for acquiring the account information from the application started by the starting means, in the web application;
6. The program according to claim 5, further causing a computer to function as: The program described in claim 6, characterized in that the launching means launches the application by accepting an instruction from the user on the screen of the web application. The program described in claim 6 further causes the computer to function as a fourth acquisition means in the web application that acquires the data from the server using the account information acquired by the third acquisition means. The program described in claim 1 or 2, characterized in that the account information is a guest account. The program described in claim 1 or 2, characterized in that the web application is a web application for creating content. The program described in claim 1 or 2, characterized in that the application is a native application for printing content created by the web application on a printing device. A system including a server and an information processing device,
The information processing device includes:
a first request means for, when an instruction to process data stored in a server that provides a web application is received from a user on a screen of the web application displayed by a web browser, requesting temporary authentication information from the server by the web application;
a first receiving means for receiving, by the web application, the authentication information transmitted from the server in response to the request made by the first requesting means;
a first acquisition means for acquiring the authentication information received by the first reception means by an application that is installed on the information processing device and that executes the process;
a second request means for requesting account information issued to the user from the server using the authentication information by the application;
a second acquisition means for acquiring and storing the account information transmitted from the server in response to a request from the second request means by the application;
a processing means for acquiring the data from the server using the account information by the application and processing the data;
The server
an issuing means for issuing the account information based on information used in accessing the server by the web browser;
a first transmitting means for generating the authentication information corresponding to the account information in response to a request from the first requesting means and transmitting the generated authentication information to the information processing device;
and second transmission means for transmitting the account information to the information processing device in response to a request from the second request means.
A system characterized by: The system described in claim 12, characterized in that the information used by the web browser to access the server is a cookie. A method executed in an information processing device,
a first request step of requesting temporary authentication information from a server that provides a web application when an instruction to process data stored in the server is received from a user on a screen of the web application displayed by a web browser;
a first receiving step of receiving, by the web application, the authentication information transmitted from the server in response to the request made in the first requesting step;
a first acquisition step of acquiring the authentication information received in the first reception step by an application that is installed in the information processing device and that executes the process;
a second request step of requesting account information issued to the user from the server using the authentication information by the application;
a second acquisition step of acquiring and storing the account information transmitted from the server in response to the request in the second request step by the application;
a processing step of acquiring the data from the server using the account information by the application and processing the data;
A method having the following. A method executed in a system including a server and an information processing device,
In the information processing device,
a first request step of requesting temporary authentication information from a server that provides a web application when an instruction to process data stored in the server is received from a user on a screen of the web application displayed by a web browser;
a first receiving step of receiving, by the web application, the authentication information transmitted from the server in response to the request made in the first requesting step;
a first acquisition step of acquiring the authentication information received in the first reception step by an application that is installed in the information processing device and that executes the process;
a second request step of requesting account information issued to the user from the server using the authentication information by the application;
a second acquisition step of acquiring and storing the account information transmitted from the server in response to the request in the second request step by the application;
a processing step of acquiring the data from the server using the account information by the application and processing the data;
In the server,
an issuing step of issuing the account information based on information used in accessing the server by the web browser;
a first transmission step of generating the authentication information corresponding to the account information in response to the request in the first request step and transmitting the authentication information to the information processing device;
a second transmitting step of transmitting the account information to the information processing device in response to the request in the second requesting step;
A method comprising: