Web program, printing program, server, and system
The web program on a server simplifies label data printing by enabling users to select and print data through screen operators, automating the process and reducing user effort.
Patent Information
- Application Number
- JP2024053999
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-03-28
- Publication Date
- 2025-10-09
AI Technical Summary
Existing systems require users to perform multiple operations to print label data from a browser to a label printer, making the process time-consuming.
A web program on a server that allows users to select label data for printing through operators on a screen, sending a call instruction to the user's device to launch a print program, which downloads and prints the data automatically.
Minimizes user effort by allowing easy selection and printing of label data through simple screen operations, reducing the time required for the printing process.
Smart Images

Figure 2025152210000001_ABST
Abstract
Description
[Technical Field]
[0001] The technical field disclosed in this specification relates to a web program, a printing program, a server, and a system used in a system that utilizes label data. [Background technology]
[0002] A conventional system for utilizing content data is known in which a server that stores content data is provided on the Internet, content data is posted from a user's device, i.e., uploaded to the server, and the content data is then downloaded to another user's device.
[0003] An example of a document disclosing the above-mentioned system is Patent Document 1. In the points management system disclosed in Patent Document 1, when photo data is uploaded from User A's PC to a WWW server and purchased by User B's PC and downloaded from the WWW server, points are added to User B, the purchaser, according to the purchase amount, and further points are added to User A, the contributor, according to the data size of the photo data when the photo data is uploaded or downloaded. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-99746 Summary of the Invention [Problem to be solved by the invention]
[0005] In recent years, there have been systems that utilize label data used to print labels on a label printer as content data. In such systems, label data available from a server is displayed and viewable on a browser installed on a user's device, for example. When printing the label data viewed on this browser on a label printer, the user must operate the browser to download the label data to be printed to their own device, then launch a printing program installed on their device and instruct the printing program to print the downloaded label data. This requires a lot of operations and is time-consuming for the user to perform before printing. [Means for solving the problem]
[0006] a web program that has been made to solve the above-mentioned problems and is executable by a server computer, the server being able to access a label database in which a plurality of label data can be registered; the computer being configured to include, on a screen provided to an information processing device connected to the server, an operator indicating a print instruction for selected label data from the label data registered in the label database, and to execute a reception process for receiving an operation on the operator; the computer being further configured to execute a transmission process for sending, to the information processing device, a call instruction to call a print program installed on the information processing device in response to receiving an operation on the operator from the information processing device; the print program being able to control a label printer, and the call instruction being provided with label information necessary for downloading the selected label data; the information processing device receiving the call instruction being able to call the print program and pass the label information provided in the call instruction to the print program; the print program called by the call instruction being able to download the label data from the server using the passed label information, and having the label printer perform printing based on the downloaded label data.
[0007] A web program on a server having the above configuration includes operators corresponding to print instructions for selected label data on a screen provided to an information processing device and accepts operations on those operators. In response to accepting an operation on that operator, the web program sends a call instruction with label information attached to the information processing device, causing the information processing device, upon receiving the call instruction, to call a print program. The label information is passed to the called print program, which then downloads the label data to be printed indicated in the label information and causes the label printer to print. As a result, a user can select label data to be printed and automatically print based on the selected label data simply by operating the operators displayed on the screen, minimizing the user's effort in printing based on the label data and making it easy to print the selected label data.
[0008] A server, system, and control method for realizing the functions of the above-mentioned web program, a storage medium readable by a computer of a server that stores the web program, a printing program, a storage medium readable by a computer of an information processing device that stores the printing program, and an information processing device that can execute the printing program are also new and useful. [Effects of the Invention]
[0009] The technology disclosed in this specification realizes a technology that allows label data stored on a server to be easily printed in a system that utilizes label data. [Brief explanation of the drawings]
[0010] [Figure 1] FIG. 1 is an explanatory diagram schematically illustrating a label data sharing system according to a first embodiment. [Figure 2] FIG. 1 is a diagram illustrating an example of a URL scheme. [Figure 3] FIG. 2 is a diagram illustrating an example of a user database. [Figure 4] FIG. 2 is a diagram illustrating an example of a label database. [Figure 5] FIG. 10 is a sequence diagram illustrating an example of a posting process. [Figure 6] FIG. 10 is a sequence diagram illustrating an example of a download printing process. [Figure 7] FIG. 10 is a diagram illustrating an example of a screen transition. [Figure 8] FIG. 10 is a sequence diagram illustrating an example of an automatic startup process included in the simple download process. [Figure 9] FIG. 10 is a sequence diagram illustrating an example of an automatic download printing process included in the simple download process. [Figure 10] FIG. 10 is a sequence diagram illustrating a simple download process executed in the label data sharing system of the second embodiment. DETAILED DESCRIPTION OF THE INVENTION
[0011] An embodiment of a web program, a print program, a server, and a system for sharing label data will be described in detail with reference to the accompanying drawings. This embodiment discloses a system in which an information processing device incorporating a print program and a server incorporating a web program can be connected via a network.
[0012] (First embodiment) A label data sharing system 100 (hereinafter referred to as "system 100") of the first embodiment shown in Fig. 1 is a system provided by, for example, a label printer vendor. The system 100 comprises a label management server 3 and a terminal 1, and the label management server 3 and terminal 1 are connected via the Internet 9. The terminal 1 is connectable to a label printer 2. The system 100 is an example of a "system." The label management server 3 is an example of a "server." The terminal 1 is an example of an "information processing device." The Internet 9 is an example of a "network."
[0013] 1 shows only one terminal 1 that can be connected to the label management server 3, but in reality, many terminals 1 are connected to the label management server 3. The label printer 2 may be connected to multiple terminals. Furthermore, the terminal 1 may be used by multiple users.
[0014] The label printer 2 is a device that has at least a printing function and a communication function. The label printer 2 is connected to the terminal 1 via wireless LAN communication such as Wi-Fi (registered trademark) or short-range wireless communication such as Bluetooth (registered trademark). The label printer 2 may also be connected to the terminal 1 via a wired connection using the USB communication standard.
[0015] For example, the tape that can be installed in the label printer 2 is predetermined for each model. Multiple types of tape with different tape widths, tape colors, and character colors can be interchangeably installed in the label printer 2. When the label printer 2 receives a print job that includes label data, it prints based on the label data while feeding the tape and ejects the printed tape outside the machine. A label of a specified size is formed using the ejected tape.
[0016] The terminal 1 is an information processing device used by the owner or user (hereinafter referred to as "user") of the label printer 2. The terminal 1 is, for example, a smartphone, a tablet terminal, or a personal computer (PC). The terminal 1 has a controller 10 including a CPU 11 and a memory 12. The CPU 11 is an example of a "computer of an information processing device." The terminal 1 has a user interface (hereinafter referred to as "user IF") 13 and a communication interface (hereinafter referred to as "communication IF") 14, which are connected to the controller 10.
[0017] The label management server 3 is a server provided by the vendor of the label printer 2. The label management server 3 of this embodiment comprises a controller 30 including a CPU 31 and a memory 32. The CPU 31 is an example of a "server computer." The label management server 3 comprises a user interface (hereinafter referred to as "user IF") 33, a communication interface (hereinafter referred to as "communication IF") 34, and an interface 35, which are connected to the controller 30.
[0018] Note that the controllers 10 and 30 in Figure 1 are general terms for the hardware and software used to control the terminal 1 or the label management server 3, and do not necessarily represent a single piece of hardware that actually exists in the terminal 1 or the label management server 3.
[0019] The CPU 11 of the terminal 1 and the CPU 31 of the label management server 3 execute various processes according to programs read from the memory 12 of the terminal 1 and the memory 32 of the label management server 3, respectively, and based on user operations. The memories 12 and 32 store various programs and various data. The memories 12 and 32 are also used as work areas when various processes are executed. The buffers provided in the CPUs 11 and 31 are also an example of memory. Note that examples of the memories 12 and 32 are not limited to ROM, RAM, HDD, etc. built into the terminal 1 or the label management server 3, but may also be storage media readable and writable by the CPUs 11 and 31, such as recording media, for example, CD-ROM, DVD-ROM, etc.
[0020] The user IF 13, 33 includes hardware that displays a screen for notifying the user of information and hardware that accepts user operations. For example, the user IF 13 includes a display 13a that displays information. The user IF 13, 33 may be a combination of a display that can display information and a mouse, keyboard, or the like that has an input acceptance function, or may be a touch panel that has both a display function and an input acceptance function.
[0021] The communication IFs 14 and 34 include hardware for communicating with external devices. The terminal 1 and the label management server 3 can connect to the Internet 9 via the communication IFs 14 and 34 and communicate with each other. The terminal 1 can connect to the label printer 2 via the communication IF 14. The communication IFs 14 and 34 can use communication standards such as Ethernet (registered trademark), Wi-Fi (registered trademark), and USB. The terminal 1 and the label management server 3 may be equipped with multiple communication IFs 14 and 34 that support multiple communication standards.
[0022] The memory 12 of the terminal 1 stores various programs and data, including an operating system (hereinafter referred to as "OS") 21, a browser 45, and a print application program (hereinafter referred to as "print app") 46. The browser 45 and the print app 46 are also referred to as "client apps." The print app 46 is an example of a "print program."
[0023] OS21 is a multitasking OS that can process multiple tasks in parallel by managing and switching between them. Examples of OS21 include Windows (registered trademark), macOS (registered trademark), Linux (registered trademark), iOS (registered trademark), and Android (registered trademark).
[0024] The OS21 of this embodiment has a mechanism for launching a program by a URL scheme and executing a function specified by the URL scheme. The OS21 has registered therein programs to be launched by the URL scheme. That is, the OS21 stores, for example, the scheme name of the URL scheme and the program to be launched by the scheme name in association with each other.
[0025] As shown in Fig. 2, a URL scheme has a function designation section 110 and a data designation section 120. The function designation section 110 designates a program to be launched by the URL scheme and a function to be executed by the launched program. For example, in this embodiment, the function designation section 110 describes the scheme name of the print application 46 and a print command for executing the function of downloading and printing label data. The OS 21 stores the scheme name of the print application 46 in association with the print application 46.
[0026] Data to be used when executing a function specified by a URL scheme is specified in data specification section 120. In this embodiment, label information indicating the object to be downloaded is specified in data specification section 120.
[0027] Returning to Figure 1, the browser 45 is a program used to browse websites. The browser 45 is launched by the user of the terminal 1, and when launched, has the function of displaying on the display 13a a web page provided by a web server (e.g., the label management server 3) indicated by a specified URL. The browser 45 may be supplied by the OS 21 vendor and incorporated into the OS 21, or it may be installed on the terminal 1 separately from the OS 21.
[0028] The print application 46 is an application program provided by the vendor of the label printer 2. The print application 46 has a function to send a print job including label data to the label printer 2 and cause the label printer 2 to print based on the label data. The label printer 2 that performs printing may be registered in advance in the print application 46, or may be selected during print settings. The print application 46 may also have a function to create and edit label data on the terminal 1.
[0029] The memory 32 of the label management server 3 stores various programs and data, including a web application program (hereinafter referred to as a "web app") 36. The web app 36 is an application program that can be used on the browser of the terminal 1 without being installed on the terminal 1. The web app 36 is an example of a "web program."
[0030] The terminal 1 can access the Web application 36 using the browser 45 or the browser function of the print application 46 and use the services provided by the Web application 36. For example, the Web application 36 can provide services such as registering label data uploaded, i.e., posted from the terminal 1 (hereinafter also referred to as "posted label data"), to the label management server 3 and downloading the registered label data from the label management server 3 to the terminal 1, on the condition that the terminal 1 is logged in.
[0031] The Web application 36 of this embodiment includes a front-end application 37 and a back-end application 38. The front-end application 37 and the back-end application 38 may be held by different servers.
[0032] The front-end application 37 has, for example, a web server function. The front-end application 37 can be directly accessed from the terminal 1. The front-end application 37 has prepared therein various types of page information to be displayed on the screen of the terminal 1.
[0033] The backend application 38 has a function separate from the web server function. Basically, the backend application 38 cannot be accessed directly from the terminal 1. The backend application 38 can access, via the interface 35, for example, a user database (hereinafter referred to as "user DB 5") 5, a label database (hereinafter referred to as "label DB") 6, or a content database (hereinafter referred to as "content DB") 7, to store and search for information.
[0034] The content database 7 stores information about content available to users. The content includes, for example, fonts, emojis, images, and functions. The content database 7 stores records that associate, for example, a font ID, font data including information about the shape and color of the included characters, the font name, a description of the font, and the font creator.
[0035] 3, the user DB 5 can store user information about users who can use the services provided by the system 100. In the user DB 5, a record including a user ID 51, a user name 52, a password 53, a name 54, an address 55, and purchase information 56 is created for each user.
[0036] The user ID 51 stores information for identifying a user. The user name 52, password 53, name 54, and address 55 store the user name, password, name, and address entered by the user at the time of user registration and used when using the system 100. The user DB 5 may store personal information other than the name and address, such as an email address, postal code, or telephone number. The purchase information 56 stores, for example, information indicating content that the user has purchased and downloaded to the terminal 1. The user DB 5 may store points earned by the user in association with the user ID. The points can be used to purchase various products, such as label data, content, and consumables.
[0037] As shown in Fig. 4, the label DB 6 stores information about label data that can be provided to users. The label data stored in the label DB 6 may be data prepared in advance by the vendor of the label printer 2, or may be posted label data posted by users who use the label management server 3. In the label DB 6, a record including a label ID 61, a user ID (creator) 62, label data 63, label supplemental information 64, and a label data posting date 65 is created for each piece of label data. The label ID 61 is an example of "label information" or "label data identification information."
[0038] Information for identifying label data is stored in the label ID 61. The user ID of the user who posted the label data is stored in the user ID (creator) 62. For label data created by someone other than the user, the ID of an administrator may be stored in the user ID (creator) 62, or the user ID (creator) 62 may be left blank.
[0039] The label data 63 stores label data including information constituting the label data in a predetermined storage format. The information constituting the label data includes, for example, information and arrangement of the objects constituting the label data, character strings, images, etc. For example, label data including a text object includes, for example, text and font data of the font set for the text. The font data includes a font ID for identifying the font data.
[0040] The label supplemental information 64 stores information received on the posting screen for posting label data. The label supplemental information 64 includes, for example, the label name, category, and an image showing an example of how the label is used. The label data posting date 65 stores information indicating the date the label data was posted.
[0041] Next, the operational procedures executed in the system 100 of this embodiment will be described with reference to the drawings. Note that in this embodiment, each process other than user operations basically indicates the processing of the CPUs 11 and 31 in accordance with instructions written in programs such as the print application 46, front-end application 37, and back-end application 38. In this specification, various processes performed by the controllers 10 and 30 or the CPUs 11 and 31 in accordance with programs such as the OS 21, browser 45, print application 46, front-end application 37, and back-end application 38 may be described as if each program independently performs various processes, for convenience's sake. The processing by the CPUs 11 and 31 also includes hardware control using the API (application programming interface) of the OS. In this specification, the operation of each program will be described without a detailed description of the OS. Furthermore, the term "acquire" is used as a concept that does not necessarily require a request.
[0042] (Posting process) The posting process for posting label data to the label management server 3 will be described with reference to Fig. 5. Here, the case where user A (hereinafter referred to as "poster A") creates and posts label data will be described as an example. For ease of explanation, the reference numerals of the terminal 1 used by poster A and its components will be given the suffix "A".
[0043] As shown in FIG. 5, contributor A, for example, launches the print application 46A (A01) and creates label data (A02). For example, upon receiving an instruction to create a label, the print application 46A opens an editing screen and accepts the selection of objects to be included in the label data and various settings for the selected object. For example, if a text object is selected, the print application 46A can accept text input, font selection, character size settings, and the like. The print application 46A can also accept settings for label width, margins, label color, character color, and the like via the editing screen. Upon receiving a save instruction, the print application 46A saves the created label data in memory 12A.
[0044] Thereafter, the print application 46A performs an upload operation (A03). For example, the print application 46A accesses the label management server 3 using its own browser function, and then, upon receiving an operation on the post button, requests the label management server 3 to send a posting screen using the communication IF 14A. The front-end application 37 provides a posting screen (not shown) to the print application 46A on the condition that poster A has logged in, and causes the posting screen to be displayed on the display 13aA of the terminal 1A. For example, upon receiving, on the posting screen displayed on the terminal 1A, instructions to specify label data to be posted, input supplemental label information, and execute a new post, the front-end application 37 receives a posting instruction from the terminal 1A (A04). The posting instruction includes the label data specified on the posting screen.
[0045] When the front-end application 37 receives a posting instruction from terminal 1A via communication IF 34, it transfers the posting instruction to back-end application 38 (A05). The posting instruction includes the posted label data posted from terminal 1A, the label supplemental information entered on the posting screen, and the user ID of logged-in poster A. The back-end application 38 accesses the label DB 6 using the interface 35 and registers the posted label data of poster A in the label DB 6 (A06).
[0046] 3, the backend application 38 creates a new label ID and creates a record in which the new label ID is stored in label ID 61 in the label DB 6. After that, for the record including the new label ID 61, the backend application 38 stores the user ID attached to the posting instruction, the posted label data of poster A, and label supplemental information in user ID (creator) 62, label data 63, and label supplemental information 64, respectively. In addition, the backend application 38 stores the posting date of the posted label data in label data posting date 65.
[0047] When the registration of the label data is completed, the back-end application 38 notifies the terminal 1A of "registration complete" via the front-end application 37 (A07, A08). Upon receiving the "registration complete" notification, the terminal 1A displays, for example, a message indicating that the registration of the posted label has been completed (A09). This allows the poster A to know that the posting has been completed.
[0048] In this embodiment, the posting process is performed using the browser function of the print application 46A, but for example, the terminal 1A may perform the posting process using the browser 45A. That is, the poster A may log in to the label management server 3 via the browser 45A and display the posting screen on the browser 45A.
[0049] (Download printing process) 6, the download print process in which a user starts the print application 46 and performs printing will be described. Here, an example will be described in which user B (hereinafter referred to as "printer B") accesses the label management server 3 via the browser 45, downloads the posted label data of poster A, and then prints the downloaded label data. For ease of explanation, the reference numerals of the terminal 1 used by printer B and its components will be given the suffix "B."
[0050] For example, when the browser 45B of the terminal 1B connects to the label management server 3 (B01), it displays a web page provided by the label management server 3 on the display 13aB (B02, B03). For example, the web page 300 shown in FIG. 7(A) includes a login button 312, a posted label display tab 321, a content display tab 322, and a label search field 323. When the posted label display tab 321 is operated, the web page 300 switches to a screen that displays label data registered in the label management server 3. When the content display tab 322 is operated, the web page 300 switches to a screen that displays content data such as fonts registered in the label management server 3.
[0051] For example, when the posted label data of poster A is selected on the web page 300 displayed on the terminal 1B (B11), the front-end application 37 requests the back-end application 38 to transmit the viewing information of the selected label data (B12). The request includes the label ID of the selected label data.
[0052] The back-end application 38 accesses the label DB 6 and acquires viewing information related to the viewing from the posted label data of contributor A that corresponds to the label ID attached to the label data viewing request (B13). The viewing information may include, for example, a sample image of the specified label data, a recommended tape name, a label width, a label color, a text color, and a label ID. The viewing information may also include the label name, purpose, category, and the username of contributor A who created the label. The back-end application 38 passes the acquired viewing information to the front-end application 37 (B14).
[0053] The front-end application 37 includes the viewing information received from the back-end application 38 in a web page and sends it to terminal 1B, which is the requestor of the label data viewing request (B15). When terminal 1B receives the web page using communication IF 14B, it causes browser 45B to display a viewing screen for viewing poster A's posted label data on display 13aB (B16).
[0054] For example, the viewing screen 500 shown in Fig. 7(B) displays information included in the viewing information. Furthermore, the viewing screen 500 includes a first operation button 501, a second operation button 502, and a third operation button 503. The first operation button 501 is an operator that instructs the user to download the label data to be viewed. The second operation button 502 is an operator that instructs the user to print the label data to be viewed. The third operation button 503 is an operator that instructs the user to return to the previous screen.
[0055] When the first operation button 501 is operated, the front-end application 37 receives a download request for the selected posted label data from the terminal 1B (B21). If the print owner B has not yet logged in, the front-end application 37 performs login authentication, and, on the condition that the print owner B has logged in, transfers the received download request to the back-end application 38 (B23). The download request includes the label ID of the selected posted label data.
[0056] The back-end application 38 accesses the label DB 6, acquires the posted label data of poster A based on the label ID attached to the download request (B24), and passes it to the front-end application 37 (B25). The front-end application 37 transmits the posted label data of poster A to terminal 1B, which is the source of the download request, via the communication IF 34 (B26). Upon receiving the posted label data via the communication IF 14B, terminal 1B stores it in a storage area for print application 46B provided in memory 12B (B27).
[0057] Thereafter, user B starts the print application 46B, for example, by operating the start-up icon of the print application 46B displayed on terminal 1B (C01). The started print application 46B accepts the selection of submitted label data to be printed (C02), and upon accepting a print instruction (C03), sends a print job including the selected label data to the selected label printer 2B (C04). The print target and print instruction may be accepted on an editing screen for editing the label data, or on a screen that displays a list of label data saved on terminal 1B. The label printer 2B executes printing based on the print job (C05).
[0058] For example, if the downloaded label data includes font data that has not been purchased, user B will not be able to print the downloaded label data. In such a case, terminal 1B connects to the label management server 3 using browser 45B or the browser function of print application 36B. The label management server 3 accepts a download request for unpurchased font data from terminal 1B, for example, via web page 300 shown in FIG. 7A. The label management server 3 obtains the specified font data from content DB 7 and sends it to terminal 1B. Terminal 1B receives the font data and stores it in memory 12. This enables terminal 1B to print the downloaded label data. The label management server 3 also accesses user DB 5 and stores the font ID of the font data sent to terminal 1B in the purchase information associated with user B's user ID. This allows the label management server 3 to manage downloaded font data for each user without accessing the print application 46.
[0059] (Simple download printing process) Next, the simple download printing process will be described with reference to Figures 8 and 9. In the download printing process described above, for example, after downloading label data to terminal 1B using browser 45B, it is necessary to launch print application 46B and specify the downloaded label data and enter print instructions, which is time-consuming. Therefore, in the simple download printing process, a control for accepting a print instruction for the label data is provided on the web page provided by web application 36, and in response to operation of the control, print application 46 is called and download printing is performed. The simple download printing process will be described below using an example in which user B downloads and prints submitted label data from user A.
[0060] As shown in Fig. 8, when the browser 45B connects to the label management server 3 via the communication IF 14B, the front-end application 37 causes the terminal 1B to display the web page 300 shown in Fig. 7(A). When the posted label data of poster A is selected via the web page 300, the front-end application 37 causes the terminal 1B to display the viewing screen 500 shown in Fig. 7(B) (B11 to B16).
[0061] When the front-end application 37 accepts the operation of the second operation button 502 via the web page displayed on terminal 1B (E20), if print user B is not already logged in, it performs login authentication and generates a URL scheme on the condition that print user B is logged in (E22). Specifically, the front-end application 37 writes the scheme name of the print application 46 and a print command for executing the function of downloading and printing label data in the function designation section 110 of the URL scheme, and writes the label ID of the specified posted label data in the data designation section 120 of the URL scheme. E20 is an example of an "acceptance process." The second operation button 502 is an example of an "operator indicating a print instruction for selected label data."
[0062] In addition, when the front-end application 37 receives an operation of the second operation button 502, it may not create a URL scheme, or if the print owner B is not already logged in, it may perform login authentication and generate a URL scheme on the condition that the print owner B is logged in.
[0063] The front-end application 37 uses the communication IF 34 to transmit the generated URL scheme to the terminal 1B (E23). The URL scheme is received by the OS 21B of the terminal 1B. E23 is an example of a "transmission process." The generated URL scheme is an example of a "call instruction."
[0064] The OS 21B passes a start instruction to the print application 46B associated with the scheme name of the received URL scheme (E24). The start instruction is accompanied by the label ID specified in the data specification unit 120 of the URL scheme. The print application 46B is automatically started in response to the start instruction (E25).
[0065] When the third operation button 503 on the viewing screen 500 is operated, the front-end application 37 returns to the previous screen without creating a URL scheme, and can accept reselection of label data.
[0066] As shown in FIG. 9, the print application 46B launched by the URL scheme queries the label printer 2B selected by the print application 46B or OS 21B for printer information and acquires the printer information from the label printer 2B (E01). The printer information is information indicating at least one of the label printer's capabilities and paper information indicating the paper loaded in the label printer. The label printer's capabilities include, for example, the tape width, tape type, and optional functions that the label printer can support. An optional function is, for example, a cutting function that automatically cuts the tape. The paper information is the tape model number. The print application 46B may also acquire the printer information by reading it out from the printer application 46B or OS 21B.
[0067] The print application 46B connects to the label management server 3 and requests transmission of a download URL (E41). This request includes the label ID that was attached to the launch instruction at E24 in Fig. 8, i.e., the label ID attached to the posted label data by poster A, and the printer information acquired at E31 in Fig. 9. The "download URL request" at E41 is an example of a "download request."
[0068] The front-end application 37 transfers the download URL request with the label ID and printer information attached to it to the back-end application 38 (E42).
[0069] The backend application 38 processes the label data corresponding to the label ID attached to the request and generates processed label data (E43). E43 is an example of "first server processing processing" and "second server processing processing." The processed label data processed in E43 is an example of "first processed label data" and "second processed label data."
[0070] For example, the backend application 38 accesses the label DB 6 and copies the posted label data of poster A based on the label ID attached to the request. The backend application 38 processes the copied label data based on the printer information attached to the request.
[0071] Specifically, for example, if the tape width included in the printer information differs from the label width of the copied label data, or if the tape model number included in the printer information does not correspond to the tape width set in the copied label data, the backend application 38 changes the label width of the copied label data to match the tape width or tape model number included in the printer information.
[0072] Furthermore, the backend application 38 changes the margins of the duplicated label data in response to changes in the label width. Specifically, the backend application 38 increases the margins when the label width is widened, and decreases the margins when the label width is narrowed. Furthermore, the backend application 38 changes the size of the objects that make up the label data in response to changes in the label width and margins. Specifically, the backend application 38 may enlarge or reduce the objects included in the duplicated label data to make them easier to see, using a predetermined algorithm, in response to changes in the tape width and margins.
[0073] Furthermore, for example, if the tape color or text color included in the printer information, or the tape color or text color corresponding to the tape model number in the paper information, differs from the label color or text color set in the copied label data, the back-end application 38 adjusts the label color or text color of the copied label data to match the tape color or text color in the printer information or paper information.
[0074] For example, if the copied label data uses a font that was not downloaded by user B, even if user B downloaded the label data, the print application 46B may not be able to reproduce the font, resulting in an error. Therefore, the back-end application 38 accesses the user database 5 to determine whether the font ID of the font data included in the copied label data is included in the purchase information associated with user B's user ID. If the back-end application 38 determines that the font ID is not included, it converts the text data included in the copied label data into image data. If the font ID is not included, it does not convert the text data into image data.
[0075] The backend application 38 stores the processed label data processed in E43 in a predetermined storage area (E44). If the backend application 38 does not process the label data based on the printer information or purchase information in E43, it stores the copied label data as processed label data in a predetermined storage area. The predetermined storage area may be located inside or outside the label management server 3.
[0076] The back-end application 38 creates a download URL indicating the save destination of the processed label data (E45). The back-end application 38 returns the created download URL to terminal 1B via the front-end application 37 (E46, E47). E42 to E47 are an example of a "reply process." The "download URL" that the label management server 3 returns to terminal 1B is an example of a "URL used to download label data corresponding to the identification information" and a "URL used to download first processed label data."
[0077] When the print application 46B receives the download URL using the communication IF 14B, it uses the download URL to request the backend application 38 of the label management server 3 to download the label data (E51). The backend application 38 reads out the processed label data stored in E44 (E52) and returns it to the requesting terminal 1B (E53). The print application 46B acquires the received processed label data using the communication IF 14B. E41, E47, E51, and E53 are examples of a "download process." The downloaded processed label data is stored in a nonvolatile area of the memory 12B and is erased when the print application 46B is terminated.
[0078] Thereafter, the print application 46B displays a preview screen 630, for example, as shown in FIG. 7C, on the display 13aB (E71). The preview screen 630 includes an image of the label shown in the downloaded processed label data, a print button 631 to instruct printing, and a cancel button 632 to cancel printing, and can accept a choice of whether to print. E71 is an example of a "preview process."
[0079] For example, if the label width, margins, label color, and text color of the copied label data are changed, the preview screen 630 shown in Fig. 7(C) will display a preview image different from the image of the posted label data displayed on the viewing screen 500 in Fig. 7(B), and a label width, label color, and text color different from those on the viewing screen 500. Therefore, before printing, user B can check the processing details of the posted label data via the preview screen 630 and decide whether or not to print.
[0080] When user B operates the print button 631, the print application 46B accepts the print execution instruction (E81) and sends a print job including the downloaded processed label data to the label printer 2B (E82). The label printer 2B executes printing based on the print job and prints the processed label data on the attached tape to create a label (E83). E83 is an example of a "print process." Note that when user B operates the cancel button 632, the print application 46B accepts the cancel instruction and does not execute printing. The print application 46B terminates after E81 (E84).
[0081] As described above, the Web application 36 incorporated in the label management server 3 of the first embodiment includes the second operation button 502, which corresponds to a print instruction for selected label data, on the viewing screen 500 provided to the terminal 1B, and accepts an operation on the second operation button 502 via the browser 45B. In response to accepting the operation on the second operation button 502, the Web application 36 sends a URL scheme including a label ID to the terminal 1B. Upon receiving the URL scheme, the terminal 1B invokes the print application 46B via the OS 21 and passes the label ID to the invoked print application 46B. Based on the received label ID, the print application 46B can download the label data to be printed, which is indicated in the label information, from the label management server 3 and cause the label printer 2B to print it. As a result, the user selects the label data to be printed, and simply operates the second operation button 502 displayed on the viewing screen 500; printing based on the selected label data is therefore automatically performed. This reduces the effort required of the person B to print based on the label data, and allows the selected label data to be printed easily.
[0082] (Second embodiment) Next, a web program, print program, server, and system according to the second embodiment will be described with reference to the drawings. In the system according to the second embodiment, as shown in FIG. 10, the web application 36 creates a URL scheme including a download URL in response to the operation of the second operation button 502 and sends it to terminal 1B, and the print application 46B processes the label data downloaded to terminal 1B. This differs from the first embodiment, in which the web application 36 creates a URL scheme including a label ID in response to the operation of the second operation button 502 and sends it to terminal 1B, and the web application 36 processes the label data sent to terminal 1B. Here, differences from the first embodiment will be mainly described, and the same reference numerals as in the first embodiment will be used for configurations and processes common to the first embodiment, and descriptions thereof will be omitted where appropriate.
[0083] When the second operation button 502 is operated while corresponding label data is specified on the viewing screen 500 (B11 to B16, B20), the front-end application 37 requests the back-end application 38 to send a download URL indicating the save destination of the specified label data (E111). The request includes the label ID of the specified label data.
[0084] The back-end application 38 acquires the download URL corresponding to the label ID attached to the request (E112) and passes it to the front-end application 37 (E113).
[0085] The front-end application 37 generates a URL scheme by writing the scheme name of the print application 46 and a print command indicating the download print function in the function specification section 110, and writing a download URL in the data specification section 120 (E114). The front-end application 37 transmits the generated URL scheme to the requesting terminal 1B (E115). The URL scheme including the download URL is an example of a "call instruction." The download URL is an example of "label information." E115 is an example of a "transmission process."
[0086] When the OS 21B of the terminal 1B receives the URL scheme using the communication IF 14B, it passes a launch instruction to the print application 46B (E116) and launches the print application 46B (E117). The launch instruction includes a download URL included in the URL scheme.
[0087] The print application 46B accesses the backend application 38 using the download URL attached to the startup instruction and requests the download of label data (E51). The backend application 38 reads the label data from the storage location specified in the download URL (E52) and sends it to terminal 1B (E53). The print application 46B acquires the label data using the communication IF 14B. The acquired label data is stored in a non-volatile area of memory 12B and is erased when the print application 46B is terminated. E53 is an example of a "download process."
[0088] The print application 46B acquires printer information from the label printer 2B (E131). The method for acquiring printer information is the same as E31 in Fig. 9, so a detailed explanation will be omitted. E131 is an example of "acquisition processing."
[0089] The print application 46B processes the downloaded label data based on the acquired printer information (E132). The processing method is the same as E43 in Figure 9, so a description thereof will be omitted. E132 is an example of "first client processing."
[0090] To explain one example of processing, when downloaded label data includes text data, the printing application 46B determines whether the font set in the text data is compatible. If the font data for the font included in the text data is not stored in memory 12, the printing application 46B determines that the font is not compatible. In this case, the printing application 46B converts the text data containing the incompatible font to a default font. This conversion process is an example of a "second client processing process." Note that if the font data for the font included in the text data is stored in memory 12, the printing application 46B determines that the font is compatible and does not convert the font of the text data to the default font.
[0091] The print application 46B displays a preview screen 630 on the display 13aB (E71). The preview screen 630 includes a preview image showing the label data processed in E132. When the print application 46B receives an instruction to execute printing via the preview screen 630 (E81), it sends a print job including the processed data processed in E132 to the label printer 2B (E82). Upon receiving the print job, the label printer 2B executes printing based on the processed label data and creates a label. E82 is an example of a "printing process."
[0092] The Web application 36 of the second embodiment described above assigns a URL used to download label data as label information, so that the print application 46B can use that URL to access the label management server 3 and download the label data. Furthermore, after being called by the URL scheme, the print application 46B can immediately download the label data using the download URL, thereby reducing the communication load on the terminal 1B.
[0093] The embodiments disclosed herein are merely examples and are not intended to limit the scope of the present invention. Therefore, the technology disclosed herein can naturally be improved and modified in various ways without departing from the spirit and scope of the present invention. For example, the program used for posting and displaying the web page 300 and the viewing screen 500 may be either the print application 46 or the browser 45.
[0094] For example, the Web application 36 may call the print application 46B using a deep link instead of a URL scheme. A deep link is an example of a "call instruction."
[0095] For example, if print application 46B is already running when OS21B receives the URL scheme at E23 in FIG. 8 or E115 in FIG. 10, OS21B can have the already running print application 46B download and print the label data specified by the label ID or download URL included in the URL scheme.
[0096] 9 may be omitted. In this case, the request of E42 may include a label ID, but not printer information. However, the web application 36 or print application 46B can process the selected label data to suit the label printer and print based on the processed label data, thereby creating a label that suits the label printer 2B owned by user B.
[0097] For example, the processes of E131 and E132 in Fig. 10 may be omitted. However, the print application 46B can process the downloaded label data to suit the label printer 2B and print based on the processed label data, thereby enabling printing to be performed in a manner suitable for the label printer 2B owned by the user.
[0098] For example, in E43 in Fig. 9 or E132 in Fig. 10, it is not necessary to adjust the label width and margins to a width and margin that can be printed by the label printer 2B. However, by adjusting the size of the label data to match the tape set in the label printer 2B, it is possible to avoid size errors in the label printer 2B.
[0099] For example, in E43 of Fig. 9, it is not necessary to convert the text data included in the label data into image data. However, if the web application 36 converts the text data into image data and passes it to the print application 46B, it is more likely that label data containing text data with fonts that the print application 46B does not support can be printed via the print application 46B.
[0100] 10, the font of the text included in the label data does not have to be converted to the default font. However, if the print application 46B converts the font of the text included in the downloaded label data to the default font before printing, it is more likely that label data containing text data set in a font that the print application 46B does not support can be printed via the print application 46B.
[0101] For example, E71 in Figure 9 or Figure 10 may be omitted. However, the print application 46B can prevent printing that the user does not intend by having the user confirm the contents of the downloaded label data before printing. This is particularly effective when there is a possibility that the label data will be processed in E43 in Figure 9 or E132 in Figure 10, as this could result in processing that the user does not intend.
[0102] For example, in FIG. 10, the print application 46B may download label data from the label management server 3 after acquiring the printer information.
[0103] In any sequence diagram disclosed in the embodiments, any of a plurality of processes can be executed in any order or in parallel as long as no contradiction occurs in the process content.
[0104] The processes disclosed in the embodiments may be executed by hardware such as a single CPU, multiple CPUs, or ASIC, or a combination thereof. The processes disclosed in the embodiments may also be realized in various ways, such as a recording medium on which a program for executing the processes is recorded, or a method. [Explanation of symbols]
[0105] 1 device 2. Label printer 3 Label Management Server 6 Label DB 9 Network 11 CPU 21 OS 31 CPU 36 Web Apps 46 Printing App 100 Label Data Sharing System
Claims
1. a web program executable by a server computer, the server being able to access a label database, and a plurality of label data being able to be registered in the label database; The computer, an operator indicating a print instruction for the selected label data from the label data registered in the label database is included on a screen provided to an information processing device connected to the server, and a reception process is executed to receive an operation on the operator; The computer further comprises: a sending process is executed to send to the information processing device a call instruction to call a print program installed in the information processing device in response to receiving an operation on the operator from the information processing device, the print program being capable of controlling a label printer, and label information required for downloading the selected label data is attached to the call instruction, the information processing device receiving the call instruction calls the print program and passes the label information attached to the call instruction to the print program, the print program called by the call instruction uses the passed label information to download the label data from the server, and causes the label printer to print based on the downloaded label data; A web program configured to:
2. 2. The web program according to claim 1, In the transmission process, the call instruction, to which the identification information of the selected label data has been assigned, is sent to the information processing device, with the identification information being used as the label information; the information processing device, upon receiving the call instruction, calls the print program and passes the identification information assigned to the call instruction to the print program; the print program called by the call instruction then sends a download request to the server, to which the passed identification information has been assigned; The computer, when the download request to which the identification information is attached is received, a reply process is executed to reply with a URL used to download the label data corresponding to the identification information, and the printing program downloads the label data from the server using the returned URL and causes the label printer to print based on the downloaded label data. A web program configured to:
3. 3. The web program according to claim 2, The computer, When the download request with the identification information attached is received, a first server processing process is executed to perform processing based on the label data corresponding to the identification information before executing the return process, and the print program called by the call instruction acquires printer information indicating at least one of the capabilities of the label printer and paper information indicating the paper loaded in the label printer, and sends the download request with the passed identification information and the acquired printer information attached to it to the server, In the first server processing, based on the printer information attached to the download request, process the label data corresponding to the identification information to generate first processed label data printable by the label printer; In the reply process executed after the first server processing process, the URL used to download the first processed label data generated in the first server processing process is returned, and the printing program uses the returned URL to download the first processed label data from the server and cause the label printer to print based on the downloaded first processed label data. A web program configured to:
4. 4. The web program according to claim 3, In the first server processing, adjusting the width and margins of the label to a width and margin that can be printed by the label printer, based on the printer information added to the download request; A web program configured to:
5. 3. The web program according to claim 2, The computer, When the download request to which the identification information is attached is received, a second server processing process is executed to process the label data corresponding to the identification information before executing the reply process. In the second server processing, generating second processed label data by converting text data included in the label data corresponding to the identification information into image data; In the reply process executed after the second server processing process, the URL used to download the second processed label data generated in the second server processing process is returned, and the printing program uses the returned URL to download the second processed label data from the server and causes the label printer to print based on the downloaded second processed label data. A web program configured to:
6. 2. The web program according to claim 1, In the transmission process, a URL used to download the selected label data is used as the label information, and the call instruction with the URL attached is sent to the information processing device; the information processing device, upon receiving the call instruction, calls the print program and passes the URL attached to the call instruction to the print program; the print program called by the call instruction uses the passed URL to download the label data from the server, and causes the label printer to print based on the downloaded label data. A web program configured to:
7. 2. The web program according to claim 1, In the transmission process, a deep link that calls the print program installed in the information processing device, the deep link specifying the label information, is sent to the information processing device as the call instruction, the print program is a program corresponding to the deep link, the label information can be specified in the deep link that calls the print program, the print program called by the deep link uses the specified label information to download the label data from the server, and causes the label printer to print based on the downloaded label data; A web program configured to:
8. 2. The web program according to claim 1, In the transmission process, a URL scheme for calling the print program installed in the information processing device, the URL scheme specifying the label information, is sent to the information processing device as the call instruction, the print program is a program corresponding to the URL scheme, the label information can be specified in the URL scheme for calling the print program, the print program called by the URL scheme downloads the label data from the server using the specified label information, and causes the label printer to print based on the downloaded label data; A web program configured to:
9. A printing program executable by a computer of an information processing device, the information processing device being capable of communicating with a label printer and a server having a web program, the server being capable of accessing a label database, and a plurality of label data being capable of being registered in the label database, the printing program being capable of controlling the label printer, and being a program called from an operating system of the information processing device in response to a call instruction, The computer, when called by the call instruction sent from the web program, the web program executes a download process to download the label data from the server using label information attached to the call instruction, and when the web program receives from the information processing device a print instruction for selected label data from the label data registered in the label database, the web program sends the call instruction, to which the label information required for downloading the selected label data is attached, to the information processing device, and the information processing device that has received the call instruction calls the print program and passes the label information attached to the call instruction to the print program, The computer further comprises: executing a print process that causes the label printer to print based on the label data downloaded in the download process; A printing program configured to:
10. 10. The printing program according to claim 9, The computer, After the download process is executed, but before the printing process is executed, a preview process is executed in which an image of the label shown in the label data downloaded in the download process is displayed on a user interface of the information processing device and a selection is made as to whether or not to execute printing. When the selection to execute printing is accepted in the preview processing, the printing processing is executed, and when the selection not to execute printing is accepted in the preview processing, the printing processing is not executed. A printing program configured to:
11. 10. The printing program according to claim 9, The computer, when called by the call instruction transmitted from the web program, executes the download process and an acquisition process of acquiring printer information indicating at least one of the capabilities of the label printer and paper information indicating the paper loaded in the label printer; The computer, after the download process is executed and before the print process is executed, a first client processing process is executed to process the label data downloaded in the download process into data that can be printed by the label printer, based on the printer information acquired in the acquisition process; In the printing process executed after the first client processing process, the label printer is caused to print based on the label data processed in the first client processing process. A printing program configured to:
12. 10. The printing program according to claim 9, The computer, After the download process is executed and before the printing process is executed, if an incompatible font is set in the text data included in the label data downloaded in the download process, a second client processing process is executed to convert the text data into a default font; In the printing process executed after the second client processing process, the label printer is caused to print based on the label data processed in the second client processing process. A printing program configured to:
13. A server connectable to an information processing device via a network, The server A label database can be accessed, and a plurality of label data can be registered in the label database; The server further comprises: a receiving process for receiving an operation on the operator, the receiving process including an operation button indicating a print instruction for the selected label data from among the label data registered in the label database, on a screen provided to an information processing device connected to the server; The server further comprises: a sending process is executed in response to receiving an operation on the operator, to send to the information processing device a call instruction to call a print program installed in the information processing device, the print program being capable of controlling a label printer, and label information required for downloading the selected label data is attached to the call instruction, the information processing device receiving the call instruction calls the print program and passes the label information attached to the call instruction to the print program, the print program called by the call instruction uses the passed label information to download the label data from the server, and causes the label printer to print based on the downloaded label data; A server configured to:
14. A system including an information processing device and a server, wherein the information processing device is connectable to the server via a network, The server A label database can be accessed, and a plurality of label data can be registered in the label database; The information processing device includes: a printing program is installed, and the printing program is a program that is called from an operating system of the information processing device in response to a call instruction; The server further comprises: a receiving process for receiving an operation on the operator, the receiving process including an operation button indicating a print instruction for the selected label data from among the label data registered in the label database, on a screen provided to an information processing device connected to the server; The server further comprises: executes a transmission process for transmitting the call instruction for calling the printing program to the information processing device in response to receiving an operation on the operator from the information processing device, and adds label information required for downloading the selected label data to the call instruction; The information processing device includes: Upon receiving the call instruction from the server, the print program is called, the label information attached to the call instruction is passed to the print program, the print program called by the call instruction uses the passed label information to download the label data from the server, and the label printer is caused to print based on the downloaded label data. A system configured as follows:
Citation Information
Patent Citations
Point managing method and device storage medium and point managing system
JP2002099746A