Information Processing Apparatus, Method, Program, and System

Abstract

Provided are an information processing apparatus, method, program, and system that reduce the workload of creating, publishing, and operating a website using a font distributed under a contract with a font distributor involving multiple entities. 【Solution means】The method includes steps of: generating unique embedding information for each contract, which is embedded in the source code of the website to display a paid font for a contract for paying a usage fee according to the use of the paid font; identifying the paid font used based on the embedding information when a viewer accesses the website; allowing the viewer to view the website in a state where the identified paid font is used; receiving from a user an operation of changing information of a contractee who uses the font without changing the embedding information; and updating the contractee information and storing it in a storage unit.

Description

Technical Field

[0001] The present disclosure relates to an information processing apparatus, method, program, and system.

Background Art

[0002] In order to further improve the appearance and diversification of designs, various fonts have been developed and provided. Some of these fonts are provided for a fee. For example, on a website, a web page that adopts a font provided by a font producer may be provided.

[0003] There is a technology that enables a user to view content using a font provided by a font producer without having the font file on the user's terminal. Patent Document 1 mainly describes "a font distribution system and a font distribution method for distributing a font to a user terminal via a communication line so that characters on a web page such as an HTML file viewed using a web browser can be viewed in a font not owned by the user terminal."

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In making a website public, an operator of the website may commission the production of the website to a business operator that produces the website. Also, while commissioning part of the production of the website, the operator of the website may also perform work. Thus, multiple entities may be involved in the production before the website is made public.

[0006] In such a website, fonts may be adopted subject to conditions such as payment of consideration based on a contract for using fonts provided by a font distributor. For example, any one of a plurality of entities involved in creating a website may adopt a font provided by a font distributor to create a website, enable other entities to view the created website, and transfer the creation work. In this way, the entity of the contract with the font distributor may differ between the stage of creating a website and the stage of operating it. Therefore, there is a need for a technology that further promotes the creation, publication, and operation of a website that uses the fonts distributed by the font distributor to achieve better design and diversification by further reducing the workload of creating, publishing, and operating the website.

[0007] An object of the present disclosure is to provide a technology that further reduces the workload of creating, publishing, and operating a website using fonts that can be distributed under a contract with a font distributor when multiple entities may be involved in creating, publishing, and operating the website.

Means for Solving the Problem

[0008] To solve the above problems, a program according to an aspect of the present disclosure is a program that operates a computer including one or more computer processors. The storage unit is configured to store information on paid fonts that require payment of a usage fee according to usage, and information on a contractor who uses the paid fonts. The program causes one or more computer processors to generate, for each contract, embedding information that is to be embedded in the source code of the website to display the paid font on the website, for a contract to pay a usage fee according to the use of the paid font, so that the information is unique for each contract; store the generated unique embedding information in the storage unit in association with the contract information; identify the paid font used on the website based on the embedding information of the website when a viewer accesses the website with a browser for the website where the paid font is used; and cause the viewer of the website to view the website with the identified paid font being used, by responding to the identified paid font. The program also causes the computer to execute steps including accepting from a user an operation to change information on a contractor related to a contract for using a font for which a usage fee is payable on the website, without requiring a change to the embedding information generated for the website; and updating and storing in the storage unit information on the contractor who uses the paid font on the website, in response to the operation to change the information on the contractor related to the contract, without requiring a change to the unique embedding information generated before the change.

Advantages of the Invention

[0009] According to the present disclosure, when multiple entities may be involved in the production, publication, and operation of a website, a technique can be provided to further reduce the workload of producing, publishing, and operating a website that uses fonts distributed under a contract with a font distributor. As a result, it is possible to further promote the production, publication, and operation of websites that use fonts distributed by font distributors and achieve better design appearance and diversification.

Brief Description of Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all the drawings for describing the embodiments, the same reference numerals are assigned to common components, and repeated descriptions are omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Also, not all of the components shown in the embodiments are essential components of the present disclosure. Further, each figure is a schematic diagram and is not necessarily strictly illustrated.

[0012] Also, in the following description, the "processor" is one or more processors. At least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may also be other types of processors such as a GPU (Graphics Processing Unit). At least one processor may be single-core or multi-core.

[0013] Also, at least one processor may be a processor in a broad sense, such as a hardware circuit (e.g., FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit)) that performs part or all of the processing.

[0014] Also, in the following description, expressions such as "xxx table" may be used to describe information from which an output is obtained for an input. This information may be data of any structure or a learning model such as a neural network that generates an output for an input. Therefore, "xxx table" can be referred to as "xxx information".

[0015] Also, in the following description, the configuration of each table is an example. One table may be divided into two or more tables, or all or part of two or more tables may be one table.

[0016] Also, in the following description, the "program" may be used as the subject to describe the processing. However, since the program is executed by the processor to perform the defined processing while appropriately using a storage unit and / or an interface unit, etc., the subject of the processing may be the processor (or a device such as a controller having that processor).

[0017] The program may be installed in a device such as a computer, or may be, for example, on a program distribution server or a computer-readable (e.g., non-transitory) recording medium. In the following description, two or more programs may be implemented as one program, or one program may be implemented as two or more programs.

[0018] In the following description, an identification number is used as identification information for various objects, but identification information of other types (e.g., an identifier including letters or symbols) may be adopted.

[0019] In the following description, when describing without distinguishing between elements of the same type, reference signs (or common signs among the reference signs) are used, and when describing by distinguishing between elements of the same type, the identification numbers (or reference signs) of the elements may be used.

[0020] In the following description, the control lines and information lines indicate those considered necessary for explanation, and not necessarily all the control lines and information lines on the product are shown. All the components may be interconnected.

[0021] <Overview of Embodiment> <1.1 System Configuration Diagram> FIG. 1 is a diagram showing the configuration of system 1.

[0022] The system 1 shown in FIG. 1 includes a font distribution server 20, a terminal 10, an origin server 40, an edge server 30, and a font production tool 50. Regarding the terminal 10, in the illustrated example, as other examples of the terminal 10, examples of the terminal 10A of a website viewer, the terminal 10B of a font producer user, the terminal 10C of a website operator user, and the terminal 10D of a website production person user are shown. These devices are communicatively connected via a network 80.

[0023] The server 20 of the font distribution system manages information on fonts that can be used based on a contract for using fonts, and is a device for providing a service of distributing font information based on a contract for using the fonts to be managed. The server 20 manages, as font information, a character font formed in a font such as a Mincho font or a Gothic font, or a font program for reproducing characters in a font such as a Mincho font or a Gothic font. The server 20 receives, as a request, at least information indicating characters on a web page and information indicating the name of the font of the characters, and distributes information such as a font file for displaying the font.

[0024] In this embodiment, the server 20 will explain an example in which a paid font managed by the server 20 is used by a viewer to view a web page of a website as a distribution destination of the paid font. In addition to this, although not generally known, the server 20 may distribute a paid font managed by the server 20 in a document, video, etc. managed in a storage that can be viewed by a person with viewing authority.

[0025] The origin server 40 is managed by an operator who operates a website, and holds contents such as text, images, and videos for displaying the website on the browser of the user's terminal 10. The origin server 40 holds the information on the contents of the web page of the website as described above, and responds to the request from the edge server 30 by sending the contents to the edge server 30.

[0026] The edge server 30 acquires and holds the content information from the origin server 40, and provides the content information held to the user's terminal 10A, etc. in response to an access from a user's terminal 10A, etc. that views the website.

[0027] The font production tool 50 provides a production tool for font production to users who are font producers. The font production tool 50 outputs font files in various formats such as PostScript, TrueType, OpenType, SVG, and bitmap fonts according to the operations of the users for font production.

[0028] In this embodiment, each device (terminal device, server, etc.) can also be regarded as an information processing device. That is, the aggregate of each device can be regarded as one "information processing device", and the system 1 may be formed as an aggregate of a plurality of devices. The way of distributing the plurality of functions required to implement the system 1 for one or more pieces of hardware can be appropriately determined in view of the processing capabilities of each piece of hardware and / or the specifications required for the system 1.

[0029] Hereinafter, the outline of the hardware configuration of the terminal 10 and the server 20 will be described. The terminals 10A, 10B, 10C, and 10D may have the same hardware configuration as the terminal 10. The edge server 30, the origin server 40, and the font production tool 50 may have the same hardware configuration as the server 20.

[0030] The terminal 10 is a device operated by a user. The terminal 10 is realized, for example, as follows. · Handheld portable terminals such as smartphones and tablets · Desktop PCs (Personal Computers) and laptop PCs · Wearable terminals worn by users (such as wristwatch type and glasses type) The terminal 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, a storage 16, and a processor 19.

[0031] The communication IF 12 is an interface for inputting and outputting signals for the terminal 10 to communicate with external devices.

[0032] The input device 13 is a device for receiving input operations from a user (for example, a pointing device such as a touch panel, a touch pad, a mouse, etc., a keyboard, etc.).

[0033] The output device 14 is a device for presenting information to the user (a display, a speaker, etc.).

[0034] The memory 15 is for temporarily storing programs and data processed by programs and the like, and is, for example, a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0035] The storage 16 is for storing data, and is, for example, a flash memory or an HDD (Hard Disc Drive).

[0036] The processor 19 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, registers, peripheral circuits, etc.

[0037] The server 20 includes a communication IF 22, an input / output IF 23, a memory 25, a storage 26, and a processor 29.

[0038] The communication IF 22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices.

[0039] The input / output IF 23 functions as an interface with an input device for receiving input operations from a user and an output device for presenting information to the user.

[0040] The memory 25 is for temporarily storing programs and data processed by programs and the like, and is, for example, a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0041] Storage 26 is for storing data and can be, for example, a flash memory or an HDD (Hard Disc Drive).

[0042] Processor 29 is hardware for executing an instruction set described in a program and is composed of an arithmetic unit, registers, peripheral circuits, etc.

[0043] <1.2 Functional Configuration of Server 20 of Font Distribution System> FIG. 2 is a diagram showing the configuration of server 20 of the font distribution system. As shown in FIG. 2, server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0044] Communication unit 201 performs processing for server 20 to communicate with an external device.

[0045] Storage unit 202 stores various databases such as user database 211, contract database 212, fee plan database 213, usage management database 214, and paid font data file 215.

[0046] User database 211 is a database that manages information of each user who uses the service of the font distribution system. Details will be described later.

[0047] Contract database 212 is a database that manages the contract status of each contract for using the service of the font distribution system. Details will be described later.

[0048] Fee plan database 213 is a database that manages information on fee plans for using the font distribution system. Details will be described later.

[0049] Usage management database 214 is a database that manages the aggregation result of the amount of fonts distributed by the font distribution system being used. Details will be described later.

[0050] The paid font data file 215 is information on the data file of the paid font managed by the font distribution system.

[0051] The control unit 203 is realized by the processor 29 reading the program stored in the storage unit 202 and executing the instructions included in the program. By operating according to the program, the control unit 203 functions as a reception control module 2041, a transmission control module 2042, a user management module 2043, a contract registration module 2044, an unauthorized use determination module 2045, a usage amount management module 2046, a font usage billing module 2047, and a reward granting module 2048.

[0052] The reception control module 2041 controls the process of the server 20 receiving signals from an external device according to the communication protocol.

[0053] The transmission control module 2042 controls the process of the server 20 transmitting signals to an external device according to the communication protocol.

[0054] The user management module 2043 is a program module that manages information on each user who uses the font distribution system.

[0055] More specifically, the user management module 2043 manages the information of each user by accepting the registration of information of each user, such as font producers, website operators, and website producers, as users who use the font distribution system.

[0056] The contract registration module 2044 is a program module that accepts the registration of a contract for using the fonts managed by the font distribution system on a website or the like.

[0057] More specifically, the contract registration module 2044 accepts, as fonts managed by the font distribution system, the specification of the font name of a paid font, the specification of the domain using the font, the specification of the contract start date, etc., and manages it as a contract. When the contract registration module 2044 accepts the specification of a font and a domain by the user, it generates a CSS file (in which information on the paid font is specified) for using the font on the website. The server 20 manages the generated CSS file in the contract database 212, and generates link information for the access destination so that the link to the generated CSS file is unique, and manages it in the contract database 212. Thereby, when displaying a font on the website, the server 20 can determine based on which contract to distribute the font in response to access based on the unique link to the CSS file.

[0058] The contract registration module 2044 accepts the specification of a domain for using a font, etc. within the scope of the user's contract for the fee plan (for example, the number of available fonts and the number of available domains may differ depending on the fee plan). Depending on the user's contract for the fee plan, when the contract registration module 2044 cannot use a font (for example, when attempting to use a font beyond the conditions such as the upper limit of the number of available fonts and the number of available domains defined in the fee plan), it may display a prompt to change the fee plan.

[0059] The unauthorized use determination module 2045 is a program module that determines whether the request for the font distributed by the font distribution system is legitimate by the contract holder or improper by a non - contract holder.

[0060] More specifically, the unauthorized use determination module 2045 can determine which contract the access to the CSS file is based on the unique link to the CSS file managed in the contract database 212. The unauthorized use determination module 2045 determines whether the domain using the font in the contract is managed in the contract database 212. If the request for the CSS file is from a domain other than the domain specified in the contract database 212, the unauthorized use determination module 2045 does not distribute the managed font, assuming that the link tag to the CSS has been obtained illegally. This can prevent the paid font from being illegally displayed even if there is access from a website that has illegally obtained the link (link tag) to the CSS file described on the web page in a legitimate contract.

[0061] The usage management module 2046 is a program module that totals the usage amount of the font used on the web page when the font managed by the font distribution system is used.

[0062] More specifically, the usage management module 2046 totals the number of times a paid font has been distributed to the user's terminal (the number of views of the web page where the paid font is used) according to the link tag to the CSS file.

[0063] The font usage billing module 2047 is a program module that performs a billing process for the contractor of the contract managed in the contract database 212 according to the usage amount of the font managed by the font distribution system.

[0064] The reward awarding module 2048 is a program module that determines the reward to be awarded to the font producer according to the amount of the font managed by the font distribution system that has been used (the result totaled by the usage management module 2046).

[0065] <1.3 Functional Configuration of Edge Server 30> FIG. 3 is a diagram showing the configuration of the edge server 30. As shown in FIG. 3, the edge server 30 functions as a communication unit 301, a storage unit 302, and a control unit 303.

[0066] The communication unit 301 performs processing for the edge server 30 to communicate with an external device.

[0067] The storage unit 302 stores various types of information such as contract information 312, usage information 314, and the blocked paid font data file 315.

[0068] The contract information 312 is information on the contract (the subject of the contract, the fee plan for the contract) managed in the contract database 212 by the server 20 of the font distribution system for the domain in which the edge server 30 holds the content. The edge server 30 obtains the information in the contract database 212 held by the server 20 by communicating with the server 20 and manages it as the contract information 312.

[0069] The edge server 30 totals the usage amount of the font (the number of times the font is distributed to the user's terminal 10, the number of times the web page on which the font is used is viewed) by the same processing as the usage amount management module 2046 of the server 20 and manages it as the usage information 314 described later, and determines whether it conforms to the upper limit of the usage amount defined in the fee plan of the contract information 312.

[0070] The edge server 30 refers to the contract information 312 and determines whether the font request for viewing the web page is legitimate by the contractor or improper by a non - contractor by the same processing as the unauthorized use determination module 2045 of the server 20.

[0071] The usage information 314 is information on the aggregated result of the number of times a font is distributed to a user's terminal (the number of times a web page including the font is viewed) in response to viewing a web page of a website for the font distributed by the font distribution system. The usage information 314 holds information on the result of aggregating the usage amount of the font in association with the domain information and transmits it to the server 20.

[0072] The blocked paid font data file 315 is obtained by pre-splitting the data of the paid font data file 215 of the server 20 into a plurality of blocks. For the fonts managed by the server 20 of the font distribution system, by preferentially extracting the character types with high usage frequency as blocks, the block containing the characters requested by the terminal A of the viewer of the website is distributed from the edge server 30 to the terminal 10A. Thereby, it is possible to shorten the font download time at the terminal 10A and improve the display speed of the web page compared to distributing the entire font data file.

[0073] The control unit 303 causes the processor of the edge server 30 to read the program stored in the storage unit 202 and execute the instructions included in the program, thereby exerting the functions shown as the reception control module 3041, the transmission control module 3042, the content acquisition module 3043, the contract information acquisition module 3044, the unauthorized use determination module 3045, the usage amount management module 3046, and the content provision module 3047.

[0074] The reception control module 3041 controls the process in which the edge server 30 receives a signal from an external device according to the communication protocol.

[0075] The transmission control module 3042 controls the process in which the edge server 30 transmits a signal to an external device according to the communication protocol.

[0076] The content acquisition module 3043 is a program module that acquires and holds the content constituting the website from the origin server 40.

[0077] More specifically, the content acquisition module 3043 is such that, in response to access to the website by a website viewer, the edge server 30 requests the origin server 40 for the content of the website and holds the content received from the origin server 40. When there is access to the website from a website viewer, if the content is held in the edge server 30, the content acquisition module 3043 responds to the browser of the website viewer without inquiring the origin server 40 about the held content. In this way, the edge server 30 functions as a content delivery network (CDN).

[0078] The contract information acquisition module 3044 is a program module that acquires, from the server 20, the information on the contract related to the domain of the website when the font managed by the font delivery system is used on the website.

[0079] More specifically, the contract information acquisition module 3044 acquires the contract information (information managed in the contract database 212 regarding the domain) from the server 20 and stores it in the storage unit 302 as the contract information 312.

[0080] Similar to the unauthorized use determination module 2045, the unauthorized use determination module 3045 is a program module that determines, by referring to the contract information 312, whether the request for the font distributed by the font delivery system is a legitimate one by the contractor or an improper one by a non - contractor.

[0081] The usage management module 3046 is a program module that, as a function similar to the usage management module 2046, aggregates the usage amount of fonts used when the fonts managed by the font distribution system are used on a web page.

[0082] The content providing module 3047 is a program module that accepts access to the website from a website viewer and transmits the content of the website to the terminal 10A of the website viewer instead of the origin server 40.

[0083] <1.4 Configuration of Terminal 10> Figure 4 is a diagram showing the configuration of the terminal 10.

[0084] As shown in Figure 4, the terminal 10 includes a plurality of antennas (antenna 111, antenna 112), a communication unit corresponding to each antenna (first communication unit 120, second communication unit 121), an input device 130 (including a touch-sensitive device 131), a display 132, an audio processing unit 140, a microphone 141, a speaker 142, a position information sensor 150, a camera 160, a motion sensor 170, a storage unit 180, and a control unit 190. The terminal 10 also has functions and configurations not particularly shown in Figure 3 (for example, a battery for holding power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.). As shown in Figure 3, each block included in the terminal 10 is electrically connected by a bus or the like.

[0085] The antenna 111 radiates the signal emitted by the terminal 10 as an electromagnetic wave. In addition, the antenna 111 receives an electromagnetic wave from space and gives the received signal to the first communication unit 120.

[0086] The antenna 112 radiates the signal emitted by the terminal 10 as an electromagnetic wave. In addition, the antenna 112 receives an electromagnetic wave from space and gives the received signal to the second communication unit 121.

[0087] The first communication unit 120 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 111 in order for the terminal 10 to communicate with other wireless devices. The second communication unit 121 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 112 in order for the terminal 10 to communicate with other wireless devices. The first communication unit 120 and the second communication unit 121 are communication modules including a tuner, an RSSI (Received Signal Strength Indicator) calculation circuit, a CRC (Cyclic Redundancy Check) calculation circuit, a high-frequency circuit, and the like. The first communication unit 120 and the second communication unit 121 perform modulation / demodulation, frequency conversion, etc. of the wireless signals transmitted and received by the terminal 10, and provide the received signals to the control unit 190.

[0088] The input device 130 has a mechanism for receiving a user's input operation. Specifically, the input device 130 is configured as a touch screen and includes a touch-sensitive device 131. The touch-sensitive device 131 receives a user's input operation on the terminal 10. The touch-sensitive device 131 detects the contact position of the user on the touch panel, for example, by using a capacitive touch panel. The touch-sensitive device 131 outputs a signal indicating the contact position of the user detected by the touch panel to the control unit 190 as an input operation.

[0089] The display 132 displays data such as images, videos, and texts according to the control of the control unit 190. The display 132 is realized by, for example, an LCD, an organic EL display, or the like.

[0090] The audio processing unit 140 demodulates and modulates the audio signal. The audio processing unit 140 modulates the signal given by the microphone 141 and gives the modulated signal to the control unit 190. Also, the audio processing unit 140 gives the audio signal to the speaker 142. The audio processing unit 140 is realized by, for example, a processor for audio processing. The microphone 141 receives an audio input and gives an audio signal corresponding to the audio input to the audio processing unit 140. The speaker 142 converts the audio signal given by the audio processing unit 140 into audio and outputs the audio to the outside of the terminal 10.

[0091] The position information sensor 150 is a sensor that detects the position of the terminal 10, for example, a GPS (Global Positioning System) module. The GPS module is a receiving device used in a satellite positioning system. In the satellite positioning system, signals from at least three or four satellites are received, and based on the received signals, the current position of the terminal 10 equipped with the GPS module is detected.

[0092] The camera 160 is a device that receives light by a light receiving element and outputs it as a captured image. The camera 160 is, for example, a depth camera that can detect the distance from the camera 160 to the object to be photographed.

[0093] The motion sensor 170 includes an acceleration sensor, an angular velocity sensor, etc., and detects the movement of the terminal 10.

[0094] The storage unit 180 is composed of, for example, a flash memory, etc., and stores the data and programs used by the terminal 10. Various information stored in the storage unit 180 will be described later.

[0095] The control unit 190 controls the operation of the terminal 10 by reading the program stored in the storage unit 180 and executing the instructions included in the program. The control unit 190 is, for example, an application processor. By operating according to the program, the control unit 190 functions as an operation reception unit 191, a transmission / reception unit 192, a data processing unit 193, a notification control unit 194, and a storage control unit 195.

[0096] The operation reception unit 191 performs a process of receiving a user's input operation on an input device such as the touch-sensitive device 131. Based on the information of the coordinates where the user touches the touch-sensitive device 131 with a finger or the like, the operation reception unit 191 determines the type of operation, such as whether the user's operation is a flick operation, a tap operation, a drag (swipe) operation, or the like.

[0097] The transmission / reception unit 192 performs a process for the terminal 10 to transmit and receive data to and from an external device such as the server 20 according to a communication protocol.

[0098] The data processing unit 193 performs a process of performing calculations on the data received by the terminal 10 according to a program and outputting the calculation results to a memory or the like.

[0099] The notification control unit 194 performs a process of displaying a display image on the display 132, a process of outputting sound from the speaker 142, and a process of generating vibration.

[0100] The storage control unit 195 controls the storage of data in the storage unit 180.

[0101] Explanation is given for various information stored in the storage unit 180. In a certain aspect, the storage unit 180 stores each information such as user information 181.

[0102] The user information 181 includes, for example, information such as the user's login ID in the service when using the service provided by the server 20 of the font distribution system.

[0103] <Two Data Structures> FIG. 5 is a diagram showing the data structure of the user database 211. The user database 211 includes an item "User ID", an item "User Attribute", an item "Contact Information", an item "Affiliation", an item "Name", an item "Font Production Record", and an item "Font Usage Record".

[0104] The item "User ID" is information for identifying each user.

[0105] The item "User Attribute" is information on the type of each user.

[0106] The item "User Attribute" may include the following as the type of user who uses the font distribution system. · Font producer who produces fonts · Web producer who produces websites · Web operator who operates websites The item "Contact Information" is information on the contact information of each user.

[0107] More specifically, the item "Contact Information" includes contact information as information for identifying the user who logs in to the font distribution system.

[0108] The item "Affiliation" is information on the affiliation of each user.

[0109] More specifically, the item "Affiliation" is information for identifying the affiliation of each user.

[0110] The item "Name" is information on the name of each user.

[0111] The item "Font Production Record" is information on the fonts produced by the user.

[0112] The item "Font Production Record" may be associated with the item "Paid Fonts to be Used" in the contract database 212 described later.

[0113] The item "Font Usage Record" is information on the record of the fonts used by the user.

[0114] The item "Font Usage Record" may also be associated with the item "Paid Fonts to be Used" in the contract database 212 described later. Information for identifying fonts that the user has used in the past may be included as information on the record of the fonts used by the user.

[0115] FIG. 6 is a diagram showing the data structure of the contract database 212. The contract database 212 includes an item "Contract ID", an item "Contracting User ID", an item "Paid Fonts to be Used", an item "Paid Font Defined CSS File", an item "Domain for Using Paid Fonts", an item "Link to CSS File", an item "Contract Start Date", an item "Contract End Date", an item "Status", and an item "Fee Plan".

[0116] The item "Contract ID" is information for identifying each contract of a user in the service provided by the server 20 of the font distribution system.

[0117] The item "Contracting User ID" is information for identifying the contracting party of the contract for using the font.

[0118] The item "Contracting User ID" may also be associated with the item "User ID" in the user database 211.

[0119] The item "Paid Fonts to be Used" is information for identifying the fonts specified for use by the contracting party in the contract.

[0120] More specifically, the item "Paid Fonts to be Used" is the identification information of the fonts issued for each font managed by the server 20 of the font distribution system.

[0121] The item "Paid Font-Defined CSS File" is information on a CSS data file in which using the fonts specified in the contract is stipulated.

[0122] More specifically, the item "Paid Font-Defined CSS File" is information on the CSS file generated by server 20 accompanying the contract (in which using the specified fonts is defined).

[0123] The item "Domains Using Paid Fonts" is information on the domains targeted to use fonts in the contract.

[0124] More specifically, the item "Domains Using Paid Fonts" includes information on the domains specified according to the conditions stipulated in the fee plan in the contract (for example, the upper limit on the number of domains that can use paid fonts).

[0125] The item "Link to CSS File" is information on the link uniquely generated to access the CSS file generated in the contract.

[0126] The item "Contract Start Date" is information on the timing of the start of the contract for using fonts.

[0127] The item "Contract End Date" is information on the timing of the end of the contract for using fonts.

[0128] The item "Status" is information on the status of each contract.

[0129] The item "Status" may include the following as the status of the contract. · In use (The website can be browsed using the fonts specified in the contract) · Use ended (Although fonts were once used according to the contract, the contract has ended, and fonts are not being distributed for browsing the website) ·During the contract procedure (while setting the contract conditions such as fonts, domains, etc. for using the font, but not yet at the stage of starting the contract) The item "fee plan" is information that identifies the fee plan in each contract.

[0130] The item "fee plan" may be associated with the item "fee plan ID" in the fee plan database 213 shown in FIG. 7.

[0131] FIG. 7 is a diagram showing the data structure of the fee plan database 213. The fee plan database 213 includes an item "fee plan ID", an item "plan name", an item "monthly fee", an item "usage limit", an item "number of available fonts", and an item "number of available domains".

[0132] The item "fee plan ID" is information that identifies each fee plan.

[0133] The item "plan name" is information about the name of the fee plan.

[0134] The item "plan name" may include the following as the name of the fee plan. ·A free plan (in the illustrated example, "free plan") ·A paid plan with multiple levels set according to usage (in the illustrated example, "plan 1", "plan 2") The item "monthly fee" is information about the charge amount corresponding to the fee plan.

[0135] More specifically, as shown in the illustration, the item "monthly fee" is information indicating the monthly fee.

[0136] The item "usage limit" is information about the limit on the usage amount of the font according to the fee plan.

[0137] The item "usage limit" may include the following as information about the usage limit. ·What is determined as the usage amount in the regular payment shown in the item "monthly fee" · Conditions when the above-defined usage amount is exceeded. In the illustrated example, the charge amount corresponding to the exceeded usage amount is defined. When the usage amount exceeding the monthly usage amount corresponding to the monthly fee is exceeded, the charge amount corresponding to the exceeded usage amount may be automatically charged without the operation of the contract party, or the contract party may purchase an additional charge fee (in the illustrated example, in "Plan 1", font distribution can be used up to 300,000 page views, but if it exceeds 300,000 page views, a fee of 600 yen is required for every 100,000 page views). When the server 20 receives an operation to purchase the additional charge fee for the exceeded page views, the font may also be distributed corresponding to the purchased additional charge fee for the exceeded page views. When the usage amount is exceeded, the font may not be distributed within the period of the monthly fee (the distribution of the font may be resumed by paying the additional charge fee for the exceeded amount or updating the fee plan). The server 20 may separately manage, in the usage amount management database 214 described later, the number of times the web page where the font to be managed is used is viewed and the number of times the font is displayed on the web page (since the upper limit of the usage amount defined in the fee plan is reached, the web page may be viewed but the font may not be transmitted to the user's terminal 10A). Thereby, the server 20 can display the page views of the web page and the number of times the font is displayed among them to the contract party as described above, making it easier for the contract party to consider paying the additional charge fee and changing the fee plan. The item "Number of available fonts" is information on the upper limit of the number of fonts that can be used in the fee plan.

[0138] The item "Number of available fonts" may include the following as information on the upper limit of the number of available fonts. · As illustrated, the higher the fee plan (the larger the payment amount), the more the number of available fonts increases. For example, when the fee plan is a certain amount or more, the upper limit of the number of available fonts may be unlimited. The item "Number of available domains" is information on the upper limit of the number of domains that can be used in the fee plan.

[0139] The item "number of available domains" may include the following as information on the upper limit of available domains. · As shown in the figure, it may be that the higher the fee plan (the larger the payment amount), the greater the number of available domains. Depending on the fee plan, it may also be that there is no upper limit on the number of available domains. FIG. 8 is a diagram showing the data structure of the usage management database 214. The usage management database 214 includes an item "contract ID", an item "aggregation period", an item "aggregation target domain", an item "usage amount", an item "status", and an item "charge amount during the aggregation period".

[0140] The item "contract ID" is information for identifying each user's contract in the service provided by the server 20 of the font distribution system.

[0141] The item "contract ID" may be associated with the item "contract ID" in the contract database 212.

[0142] The item "aggregation period" is information on the period for aggregating the usage amount of fonts.

[0143] The item "aggregation period" may include the following as the aggregation period of the usage amount of fonts. · Aggregate the usage amount at any time after the start of the aggregation period (for example, accumulate the aggregation results daily). · An aggregation period corresponding to the payment period of the fee plan in the fee plan database 213 (for example, in the case of monthly payment, divide the aggregation period monthly). The item "aggregation target domain" is information on the domain for which the usage amount of fonts is to be aggregated.

[0144] The item "usage amount" is information on the aggregated usage amount of fonts.

[0145] The item "usage amount" may include the following as information on the aggregated usage amount of fonts. · The number of fonts distributed to the terminal 10A of a user who views a website using the font · The number of times the web page of a website using the font is viewed · As shown in the figure, it may also include information indicating that the upper limit of the fee plan defined in the fee plan related to the contract has been reached, together with the usage amount of the font during the aggregation period The item "Status" is information on the distribution status based on the contract for the fonts managed by the font distribution system

[0146] The item "Status" may include the following as information on the distribution status · The status of distributing the font based on the contract · In the fee plan, when the upper limit of the usage amount is defined and the font is not displayed on the website (the font is not distributed to the user's terminal 10A) when the usage amount is exceeded, the status of restricting the font distribution by exceeding the upper limit of the plan The item "Charge amount during the aggregation period" is information on the charge amount to the contract customer determined by the usage amount of the font during the period shown in the item "Aggregation period" and the fee plan

[0147] <3 Operations> FIG. 9 is a diagram showing the flow of a process of generating embedding information to be embedded in the source code of a website based on a contract for using a font managed by the server 20 of the font distribution system

[0148] In step S921, the contract registration module 2044 of the server 20 outputs an operation screen for using the paid font to the terminal 10D of the user who is responsible for website production

[0149] In step S911, the terminal 10D accepts from the user the specification of the font to be used, the specification of the domain for using the font, and the specification of the fee plan as operations for making a contract. The terminal 10D transmits information related to the contract for the paid font to the server 20

[0150] In step S923, the contract registration module 2044 of the server 20 updates the contract database 212 according to the operation of the contractor by receiving information related to the contract of the paid font from the terminal 10D. The contract registration module 2044 generates a CSS file for using the specified paid font on the website. The CSS file defines the information of the font specified by the contractor.

[0151] In step S925, the contract registration module 2044 of the server 20 generates a unique link for accessing the generated CSS file. The link is different for each CSS file. In this way, for a contract that pays a usage fee according to the use of the paid font, the contract registration module 2044 generates embedding information to be embedded in the source code of the website to display the paid font on the website so that the information is unique for each contract. The contract registration module 2044 stores the generated unique embedding information in the contract database 212 in association with the information of the contractor related to the contract.

[0152] Specifically, the contract registration module 2044 generates a style sheet that specifies the paid font to display the paid font on the website related to the contract with the contractor. The contract registration module 2044 generates unique embedding information by generating a unique link to the generated style sheet.

[0153] In step S927, the contract registration module 2044 of the server 20 generates a link tag for embedding in the source code of the website based on the unique link to the generated CSS file and updates the contract database 212. The contract registration module 2044 outputs the information of the generated link tag to the terminal 10D.

[0154] Here, the contract registration module 2044 may accept from the contractor a contract for the use of a temporary paid font on the premise of a change of the contractor, and store the contractor's information and the unique information for embedding in the storage unit 202 (for example, in the contract database 212). In this case, before the change of the contractor, the contract registration module 2044 may provide the paid font to the viewer of the website using the paid font under certain restrictive conditions corresponding to the temporary contract for the viewing of the viewer of the website using the paid font. The following may be such restrictive conditions. · In the case of a temporary contract, change the subject of the contract by satisfying certain conditions For example, when the upper limit of the usage amount of the paid font is reached in the contract with the previous subject, the subject of the contract may be changed to a previously specified change destination. Also, when the usage period of the paid font reaches a certain period in the contract with the previous subject, the subject of the contract may be changed to a previously specified change destination. Thereby, for example, the person in charge of creating the website concludes a contract with the server 20 to use the font managed by the font distribution system under his / her own contract, has the operator of the website confirm the website to be created, and satisfies conditions such as reaching a certain amount or period of use of the paid font, so as to change the subject of the contract to a predetermined one (for example, the operator of the website), thereby reducing the trouble of changing the subject of the contract.

[0155] In step S913, the terminal 10D displays information related to the use of the paid font, such as the domain using the paid font, the font style to be used, and link tags.

[0156] FIG. 10 is a diagram showing the flow of a process of changing the subject of a contract for using a font managed by the server 20 of the font distribution system without changing the information for embedding.

[0157] In step S1021, the contract registration module 2044 of the server 20 outputs an operation screen for changing the contract of the paid font to the terminal 10D of the user who is in charge of website production. In this way, in the example of FIG. 10, an example will be described in which, by the operation of the user in charge of website production, an operation for changing the subject of the paid font contract is accepted, the subject of the contract is changed to the changed one, and the contract database 212 is updated.

[0158] Note that, as for the server 20 accepting an operation for changing the subject of the contract, it may accept the operation of the user of the original (in the example of FIG. 10, the user in charge of website production) and change the subject of the contract without the user of the changed (in the example of FIG. 10, the website operator) confirming.

[0159] Also, as for the server 20 accepting an operation for changing the subject of the contract, it may accept the operation of the user of the original, notify the user of the changed (it may not notify), and accept the operation of the user of the changed approving the change of the subject of the contract, and then change the subject of the contract and update the contract database 212.

[0160] Furthermore, as for the server 20 accepting an operation for changing the subject of the contract, it may accept the operation that requests to change the subject of the contract starting from the user of the changed, notify the user of the original (it may not notify), and accept the operation of the user of the original approving the change of the subject of the contract, and then change the subject of the contract and update the contract database 212.

[0161] In step S1011, the terminal 10D displays a list of contracts, and accepts from the user an operation of designating a contract for changing the subject of the contract and an operation of specifying the changed subject of the contract without changing the link tag based on the unique link to the CSS file that defines the paid font. The terminal 10D transmits information regarding the change of the subject of the paid font contract to the server 20.

[0162] In step S1023, the contract registration module 2044 of the server 20 changes the contract subject without changing the link tag in response to the operation of changing the contract subject received from the terminal 10D, and updates the contract database 212.

[0163] In this way, the contract registration module 2044 accepts from the user an operation of changing the information of the contractee who uses the font for which the usage fee is paid on the website, without requiring a change in the information for embedding generated for the website. In response to the operation of changing the information of the contractee, the contract registration module 2044 updates the information of the contractee who uses the paid font on the website and stores it in the contract database 212 without requiring a change in the unique information for embedding generated before the change.

[0164] FIG. 11 is a diagram showing a process flow for controlling the edge server 30 not to provide fonts managed by the server 20 of the font distribution system unless they are pre-registered domains. By performing the process of checking the compatibility of whether the domain is a target for distribution of the fonts managed by the server 20 of the font distribution system and checking whether the usage amount of the fonts has reached the upper limit defined in the fee plan (if it has reached, the fonts are not transmitted to the user's terminal 10A) on the edge server 30 instead of the server 20 of the font distribution system, the response time of the process of allowing the user's terminal 10A to view the web page where the fonts are used can be shortened and the viewing experience can be further improved. In addition, the processing load on the server 20 of the font distribution system can be reduced, security can be enhanced, and unauthorized access to requests for fonts by unregistered domains can be suppressed.

[0165] In step S1111, the terminal 10A of the website viewer accepts from the user an operation of accessing the website by the browser.

[0166] In step S1121, the control unit 203 of the edge server 30 responds with information (such as HTML, content such as images and videos that make up the web page) for displaying the website on the user's terminal.

[0167] In step S1113, the terminal 10A refers to the information of the link tag embedded in the source code (HTML) of the website and requests the CSS file indicated by the link.

[0168] In step S1123, based on the unique link to the CSS file, the control unit 203 of the edge server 30 identifies the contract for using the paid font by referring to the contract information 312, referring to the contract database 212 of the server 20, etc. The control unit 203 determines whether it is an access from the domain specified in the contract based on the information of the contract for using the paid font by referring to the contract information 312, etc. If it is an access from an unauthorized domain not specified in the contract, the control unit 203 does not send the font file of the paid font related to the contract to the user's terminal 10A, and if it is an access from the specified domain, the control unit 203 responds with the font file of the font specified in the contract to the user's terminal 10A.

[0169] In this way, when a viewer accesses a website using a paid font via a browser, the control unit 203 identifies the paid font used for the website based on the information for embedding the website. By responding with the identified paid font, the control unit 203 allows the viewer of the website to view the website with the identified paid font used. More specifically, the control unit 203 identifies the paid font used for the website by providing the file of the style sheet referred to by the link to the browser based on the information of the unique link to the style sheet embedded in the source code of the website.

[0170] As described above, the contract information 312 and the contract database 212 store unique embedding information in association with the domain specified by the contractor. The control unit 203 acquires information on the domain of the website accessed by the viewer. When the acquired domain is the domain specified by the contractor in the contract information 312 or the like, the control unit 203 responds with a paid font and allows the viewer of the website to view the website using the paid font. On the other hand, when the domain is not the specified domain, the control unit 203 does not allow the viewer of the website to view the website when the paid font is used. For example, when the acquired domain is different from the specified domain, the control unit 203 does not distribute the paid font to the viewer's terminal, so that the viewer of the website is not allowed to view the website when the paid font is used.

[0171] The website allows the viewer to view the website through an edge server that temporarily holds the content of the web page of the website and provides the held content of the web page in response to an access from the viewer's terminal, and an origin server that holds information on the content of the web page of the website and provides the content to the edge server in response to a request from the edge server. In the edge server, it is determined whether the domain information of the website accessed by the viewer and including unique embedding information is the domain specified by the contractor. The server 20 receives the result of the determination in the edge server from the edge server. The server 20 determines whether to respond with a paid font according to the received result of the determination. When the server 20 responds with a paid font, the server 20 causes the paid font to be provided to the viewer's terminal via the edge server. When the server 20 does not respond with a paid font, the server 20 does not cause the paid font to be provided to the viewer's terminal.

[0172] Also, in the contract database 212 or the contract information 312, as information on the paid font, an upper limit on the degree to which the website where the paid font is used is viewed and the usage fee are stored as information on the fee plan (fee plan database 213). In the control unit 203 of the edge server, it may be determined whether the upper limit defined in the fee plan applicable to the contract matches the amount of access by viewers to the website (usage information 314).

[0173] If the amount of access by a viewer to the website where the paid font is used exceeds the upper limit, the control unit 203 may not provide the paid font to the terminal of the viewer who views the website, and may notify the contractor of the fee plan to prompt a change in the fee plan in response to the amount of access by the viewer approaching the upper limit.

[0174] In step S1115, when the terminal 10A is for the domain specified in the contract, it receives the font file of the paid font and displays the web page including the paid font using the browser.

[0175] FIG. 12 is a diagram showing the flow of a process in which, in the edge server 30, the font files of the fonts managed by the server 20 of the font distribution system are divided in advance and held as blocks, and in response to access by viewers of the website, the font files held as blocks are provided. By the following process, for example, for fonts with a large number of characters such as Japanese text, which may take time to be distributed from the server 20 of the font distribution system, the font files are divided for each frequently used character type and arranged in the edge server 30, and when a font request is made from the terminal 10A, the block of the font file containing the characters being used is transmitted to the terminal 10A, thereby shortening the font download time and improving the display speed of the web page where the font is used, so that the experience of viewing the web page can be further improved.

[0176] In step S1221, the control unit 203 of the edge server 30 communicates with the server 20 of the font distribution system, and for the font file of the paid font, it receives as blocks divided for each frequently used character type according to the usage frequency of the character type, and holds the data of the received blocks as the blockified paid font data file 315.

[0177] In this way, in the storage unit 302 of the edge server 30, the font file of the font managed by the font distribution server is divided and held in advance as a plurality of blocks. In the storage unit 302 of the edge server 30, for each font distributed by the font distribution server, the blocks of the divided font file are held in advance as blocks that gather the character types that are relatively frequently displayed on the website.

[0178] In step S1225, the control unit 203 of the edge server 30 responds to the user's terminal 10A with the blocks of the font file that is the font specified in the contract and includes the character types used on the web page, based on the information of the contract for using the paid font.

[0179] In this way, the control unit 203 distributes the font specified in the contract to the terminal of the user accessing, and without requesting the font specified in the contract from the server 20 of the font distribution system, by referring to the blockified paid font data file 315 acquired and held in advance from the server 20, it transmits the font file of the block corresponding to the font displayed on the browser of the user's terminal 10A.

[0180] In step S1215, the terminal 10A receives the blocks of the font file and displays the web page including the paid font specified in the CSS file on the browser.

[0181] FIG. 13 is a diagram showing the flow of a process in edge server 30 of aggregating the usage amount of fonts and determining the compatibility with the fee plan applicable to the contract, and a process of transmitting the aggregation result of the font usage amount to server 20 of the font distribution system. In the illustrated example, as in the processes of steps S1321, S1325, etc. described later, edge server 30 aggregates the usage amount of fonts and transmits the aggregation result to server 20 of the font distribution system for explanation. However, the process of aggregating the usage amount of fonts (step S1321) and the process of transmitting the aggregation result to server 20 of the font distribution system (step S1325) may be performed as separate processes. For example, the frequency of the aggregation process and the frequency of transmitting the aggregation result to server 20 may be different. Also, edge server 30 may receive an inquiry from server 20 of the font distribution system and respond to server 20 with information on the aggregation result of the usage amount of fonts for domains that can be aggregated by edge server 30. Server 20 of the font distribution system may periodically send the above inquiry to edge server 30.

[0182] In step S1321, the usage management module 3046 of edge server 30 aggregates the amount of paid fonts used (the number of page views of the web page) for each domain based on the access log to the web page.

[0183] Upon receiving an access from a user's terminal to a web page that utilizes fonts distributed by the server 20 of the font distribution system, the content acquisition module 3043 of the edge server 30 requests the server 20 if the edge server 30 does not hold the font files of the fonts utilized on the web page. The content acquisition module 3043 receives and holds the font files of the fonts from the server 20. The content providing module 3047 enables the browser of the user's terminal to view the web page that utilizes the fonts by transmitting the fonts to the user's terminal that has made the access. The usage management module 3046 totals the number of times a web page that utilizes the fonts managed by the server 20 has been viewed on the browser of the user's terminal.

[0184] In step S1323, the usage management module 3046 of the edge server 30 refers to the contract information 312 to collate the amount of usage of paid fonts per domain and the fee plan of the contract for using the paid fonts, and determines the suitability of the fee plan (whether it exceeds the upper limit of the number of page views specified in the fee plan). The usage management module 3046 may notify the contractor according to the determination result. (It is also possible to notify the server 20 from the edge server 30 of the above usage amount and the determination result of the contract suitability, and have the server 20 notify the contractor according to the determination result.) The server 20 manages information on the upper limit of the number of times a specific font can be viewed in the fee plan for the contract (fee plan database 213).

[0185] The usage management module 3046 of the edge server 30 determines whether the aggregated result of the usage amount of the paid fonts has reached the upper limit of the number of times the fonts of the fee plan for the contract of the contract information 312 can be viewed. If the usage management module 3046 determines that the aggregated result has reached the upper limit of the number of times, it may also allow the user's terminal to view the web page without providing the fonts managed by the server 20.

[0186] The usage management module 3046 may notify the contracting party when the aggregated result of the usage amount of the fonts managed by the server 20 is approaching the upper limit of the number of times of viewing in the fee plan. For example, the usage management module 3046 may determine that it is approaching the upper limit when the usage fee reaches a predetermined ratio (e.g., 90% etc.) of the upper limit.

[0187] In step S1325, the usage management module 3046 of the edge server 30 transmits information on the aggregated result of the amount of paid fonts used for each domain to the server 20 of the font distribution system.

[0188] Specifically, the usage management module 3046 aggregates the number of times the web pages using the fonts managed by the server 20 are viewed in the browser of the user's terminal for each domain of the web page and holds it as usage information 314. By referring to the usage information 314, the usage management module 3046 transmits the aggregated result for each domain to the server 20.

[0189] In step S1311, the usage management module 2046 of the server 20 receives the aggregated result of the font usage amount for each domain from the edge server 30 and updates the usage management database 214. In this way, the usage management module 2046 holds information on the aggregated result for each domain in association with the contract. The usage management module 2046 refers to the information on the aggregated result in the usage management database 214 and presents the usage status of the fonts for each domain managed by the server 20 to the user. For example, the usage management module 2046 may display information on the font usage amount for each domain specified by the contractor in the contract.

[0190] FIG. 14 is a diagram showing the flow of a process of charging according to a contract according to the font usage amount and a process of granting remuneration to the font producer in the server 20 of the font distribution system.

[0191] In step S1421, the font usage charging module 2047 of the server 20 refers to the usage management database 214, and based on the information on the usage amount of fonts for each domain and the fee plan related to the contract (fee plan database 213), it calculates the charge amount corresponding to the usage amount of fonts for each contractor and updates the usage management database 214.

[0192] In this way, based on the information on the aggregated result of the usage amount of fonts associated with the contract (the aggregated result of the number of times the fonts were viewed) held in the usage management database 214, the font usage charging module 2047 imposes the consideration for using the fonts in the contract on the contractor, and thus performs the billing process for the contractor. The font usage charging module 2047 performs charging processing on payment means such as credit cards and account numbers specified in advance by the contractor, for example.

[0193] In step S1423, the reward granting module 2048 of the server 20 refers to the usage management database 214 and determines the reward amount for the font producer according to the usage amount of fonts for each domain. In the example shown, the processing of the reward granting module 2048 is described as being performed following the processing of the font usage charging module 2047, but each processing may also be performed separately.

[0194] In step S1425, the font usage charging module 2047 of the server 20 notifies the contractor of the calculated charge amount. The reward granting module 2048 notifies the font producer of the determined reward amount. In this way, the reward granting module 2048 grants a reward to the font producer who produced the font according to the number of times the font managed by the server 20 was viewed.

[0195] In step S1411, the terminal 10C of the user who is the website operator displays the charge amount corresponding to the usage amount of the paid font.

[0196] FIG. 15 is a diagram showing the flow of a process for presenting the usage status of fonts managed by the server 20 of the font distribution system.

[0197] In step S1521, the usage amount management module 2046 of the server 20 refers to the usage amount management database 214 and generates information on the usage status of fonts for each domain.

[0198] In step S1523, the usage amount management module 2046 of the server 20 outputs information on the usage status of the fonts (including paid fonts) managed by the server 20 to the font producers.

[0199] The usage amount management module 2046 presents the usage status of fonts in each domain, and displays the usage amounts of fonts used in each domain in a comparable manner between domains in units of domains. At this time, the usage amount management module 2046 may also display the breakdown of the types of fonts used in each domain. This makes it easy for font producers to check in which domains the fonts produced by the font producers themselves are being used, and can serve as a reference for font production.

[0200] In addition, the usage amount management module 2046 may display the usage status of the fonts produced by the users of the font producers to the font producers, or may display the usage status of fonts including those produced by other users (for example, all fonts or some fonts managed by the server 20). This makes it easy to check in which domains various fonts are being used, and can serve as a reference for font production.

[0201] The usage management module 2046 displays the usage amounts of fonts used in each domain in a comparable manner among fonts, with each font as a unit, in order to present the usage status of fonts in each domain managed by the server 20. At this time, the usage management module 2046 may also display the breakdown of domains in which fonts are used for each type (font style) of font.

[0202] The usage management module 2046 may present the usage status of fonts in each domain on the condition that it is at least one of the font producer who produces the fonts managed by the server 20 or the contractor who uses the fonts managed by the server 20 under a contract, in order to output information on the usage status of fonts managed by the server 20. For example, for a contractor who uses fonts on a website or the like, it becomes even easier to grasp the tendency of what fonts are being used, can be used as a reference for font selection, and the publication of a website or the like using the fonts can be further promoted.

[0203] In step S1511, the terminal 10B of the user who is the font producer displays the usage status of fonts in each domain managed by the server 20.

[0204] <4 Screen example> FIG. 16 is a screen example of an operation screen that presents the contract details of the service of the server 20 of the font distribution system and the information for embedding in the source code of the website for the production staff in charge of website production.

[0205] The contract operation screen 1600 is an operation screen for setting a contract to use the fonts managed by the server 20.

[0206] The contract operation screen 1600 corresponds to step S921 in FIG. 9 and the like.

[0207] The account display area 1602 is an area for displaying information on the user who logs in to the service provided by the server 20.

[0208] More specifically, the account display area 1602 displays various types of information of the user managed in the user database 211 as information of the logged-in user.

[0209] The setting display area 1604 is an area for displaying contract settings.

[0210] The setting display area 1604 corresponds to step S911 in FIG. 9 and the like.

[0211] The fee plan display area 1606 is an area for displaying the fee plan to be contracted by the user.

[0212] In the illustrated example, the fee plan display area 1606 is configured to display the details of each fee plan as shown in the fee plan database 213. It is assumed that the user's operation on the fee plan display area 1606 is received, and an operation screen for changing the fee plan may be displayed by overlaying, transitioning to another screen, etc., according to the user's operation. Thereby, it is possible to easily change the fee plan while referring to the contract content of the contract content specifying unit 1608 described later.

[0213] The contract content specifying unit 1608 is an operation member that receives the specification of the content of the contract using the font managed by the server 20.

[0214] The contract content specifying unit 1608 may include the following in receiving the specification of the contract content. · The domain for using the font. Depending on the fee plan, there may be an upper limit on the number of available domains. In the illustrated example, it is shown that the font can be used in a maximum of three domains depending on the fee plan. · The font (typeface) to be used. As shown in the illustration, it may be possible to display the information of the font producer together with the name of the font. · Information on a unique link to a CSS file generated by specifying a domain and font and entering into a contract for using the font. In the illustrated example, a link tag to be embedded in the HTML file of a web page is displayed. Also, in the illustrated example, before the start-of-use operation, a message indicating that a link tag to the CSS file is generated is displayed. Thereby, when using the font, the contractee is suggested to embed a link tag to the CSS file in the HTML file, facilitating the understanding of the work content after the start of use. · State of using the font. In the illustrated example, for what has started to be used, "In use" is displayed. After receiving a domain and font specification and before the start-of-use operation, the start-of-use operation unit 1610 described later is displayed to receive a start-of-use operation (an operation to confirm the domain and font specification) by the user. The start-of-use operation unit 1610 is an operation member that receives an operation to start using the font distribution for the domain and font specified by the contract content specifying unit 1608.

[0215] In the illustrated example, the start-of-use operation unit 1610 is configured such that an operation to the start-of-use operation unit 1610 becomes valid by receiving a specification for the domain and the font to be used under the constraints (such as the number of domains and the number of available fonts) defined in the fee plan.

[0216] The subject change operation unit 1612 is an operation member that receives an operation to change the subject of the contract without changing the unique link to the CSS file indicated by the link tag.

[0217] In the illustrated example, the subject change operation unit 1612 is configured to receive a change in the subject of the contract with the service provided by the server 20 after specifying the domain for using the font shown in the contract content specifying unit 1608. This corresponds to steps S1011, S1023, etc. in FIG. 10. As described above, when the server 20 is specified a domain and a font type for using a font, it generates a CSS file and also generates a link tag including a unique link to the CSS file.

[0218] For example, even if another contracting party newly specifies the same domain and font type as above, a different link to the CSS file will be generated. Therefore, when a website is produced by multiple parties (for example, when a person in charge of website production first produces a website and then transfers the work to a website operator to add content), while checking the operation of the website including the unique link to the CSS file generated by the first party's contract, if trying to transfer to the second party, operations such as deleting the link and embedding the link tag of the unique link to the CSS file generated by the second party's contract may be required.

[0219] In contrast, by preparing a subject change operation unit 1612 and enabling the change of the contracting party without changing the link tag including the unique link to the CSS file, in the above cases, the party succeeding in website production does not need to separately embed the link tag, making website production and publication even easier.

[0220] The change reservation operation unit 1614 is an operation member that accepts an operation for making a contract on the premise of changing the contracting party.

[0221] The change reservation operation unit 1614 may include the following as a contract on the premise of changing the contracting party. · In the contract, set the usage period of the font by the party before the change, and when the usage period elapses, the contract will be changed to the predetermined party after the change. · In the contract, set the upper limit of the usage amount of the font by the party before the change, and when the upper limit is exceeded, the contract will be changed to the predetermined party after the change. This makes it easy for the person in charge of website production to create a website where the font is used, and after the website operator has confirmed the content, to take over the operation of the website. In this case, even if a different pricing plan is prepared from that defined in the pricing plan database 213, it may be acceptable.

[0222] FIG. 17 is an example screen of an operation screen for changing the contract entity of the service provided by the server 20 of the font distribution system while keeping the information for embedding as it is.

[0223] The entity update operation unit 1616 is an operation member that accepts an operation to update the contract entity.

[0224] The entity update operation unit 1616 corresponds to steps S1011, S1023, etc. in FIG. 10. In the illustrated example, an example is shown in which the entity before the change performs an operation to change the contract entity, and the entity after the change accepts an approval operation to update the contract database 212.

[0225] FIG. 18 is an example screen of an operation screen for presenting the aggregation result of the usage amount of the fonts related to the contract to the contract customer of the server 20 of the font distribution system.

[0226] The contract customer operation screen 1618 is an operation screen for contract customers and is an operation screen that accepts operations based on the aggregation result of the usage amount of fonts.

[0227] The aggregation result display area 1620 is an area for displaying the aggregation result of the usage amount of the fonts related to the contract of the contract customer.

[0228] The aggregation period display area 1622 is an area for displaying the aggregation period for aggregating the usage amount of fonts.

[0229] In the illustrated example, the aggregation period display area 1622 displays up to the period for which the aggregation has been completed, while basically performing monthly aggregation in accordance with the billing timing of the fee plan (for example, based on the beginning to the end of the month). As a result, it becomes even easier to select a fee plan according to the usage amount of the font at any time.

[0230] The usage amount display area 1624 is an area that displays the aggregation result of the usage amount of the font in each domain covered by the contract.

[0231] In the illustrated example, the usage amount display area 1624 displays, for each domain, the font (typeface) being used and the number of times (page views) the web page containing the font has been viewed. Also, the usage amounts of the fonts in each domain may be arranged and displayed in descending order of page views.

[0232] The plan change operation unit 1626 is an operation member that accepts an operation to change the fee plan.

[0233] In the illustrated example, the plan change operation unit 1626 suggests to the user whether to pay the overcharge fee or review the fee plan by displaying that the aggregation result of the usage amount of the font in each domain covered by the contract is approaching the upper limit shown in the contracted fee plan.

[0234] The fee display area 1628 is an area that displays the fee based on the usage amount of the font.

[0235] In the illustrated example, the charge display area 1628 calculates the assumed usage amount until the end of the aggregation period based on the increasing pace of the font usage amount up to the middle of the aggregation period, assuming the basic aggregation period (for example, the monthly period in line with the billing timing), and displays the assumed usage amount and the assumed monthly charge amount based on the charge plan. Further, in the charge display area 1628, when there is a charge set based on the excess in the charge plan, the assumed charge for the excess is also displayed. In addition to this, it may also be possible to display the monthly charge based on the font usage amount up to the period for which the aggregation has been completed with respect to the basic aggregation period. This makes it easier for the contractor to consider whether the charge plan is reasonable, and makes it even easier to change the charge plan suitable for the font usage amount.

[0236] The overall aggregation result display area 1630 is an area that displays the aggregation result of the font usage amounts used by each user of the services provided by the server 20, not limited to the font usage amount used by the contractor.

[0237] The per-font ranking operation unit 1632 is an operation member that accepts an operation to check the aggregation result of the usage amounts in the domain of each user for each font.

[0238] More specifically, the per-font ranking operation unit 1632 accepts an operation to check the status of the font usage amount in a ranking format. In response to the user's operation, it may also be possible to display the breakdown of the domains where each font is used while arranging the fonts with larger usage amounts in order.

[0239] The per-domain ranking operation unit 1634 is an operation member that accepts an operation to check the aggregation result of the font usage amounts of each user for each domain.

[0240] More specifically, the per-domain ranking operation unit 1634 receives an operation to check the usage status of fonts for each domain in a ranking format. In response to the user's operation, while arranging the domains with large font usage amounts in order, it may also display the breakdown of the fonts used in each domain.

[0241] FIG. 19 is an example screen of an operation screen for displaying the usage status of fonts managed by the server 20 of the font distribution system.

[0242] The operation screen 1636 for font producers is an operation screen for font producers and receives operations based on the aggregated results of font usage amounts.

[0243] The recipient operation unit 1638 is an operation member that receives an operation for aggregating the usage amounts of fonts produced by font producers.

[0244] The usage amount display area 1640 is an area for displaying the aggregated results of the usage amounts of fonts in each domain for the produced fonts.

[0245] More specifically, the usage amount display area 1640 is as follows.

[0246] The reward display area 1642 is an area for displaying the amount of reward for the use of the produced fonts.

[0247] More specifically, the reward display area 1642 displays the amount of reward that varies according to the usage amount of the font. As the usage amount of the font is larger, it can be considered that the contribution of the font producer is greater, and the reward can be set by increasing the contribution ratio of the font producer in the billing amount of the contractor due to the use of the font.

[0248] The production tool startup operation unit 1644 is an operation member that receives an operation to start the font production tool 50.

[0249] In the illustrated example, the production tool activation operation unit 1644 has a link to a service that provides the font production tool 50 embedded therein, and activates a service site or an application installed on the terminal according to the link. Thereby, it is possible to facilitate the operation of producing a new font for the font producer while referring to the usage status of the font.

[0250] <Modified Example> In addition to the aspects described in the above embodiments, the following may also be adopted.

[0251] Note that all or part of each hardware configuration can be distributed and provided to a plurality of computers, and the computers can be virtually realized by connecting them to each other via a network. In this way, the computer is a concept that includes not only a single housing or a computer housed in a case but also a virtualized computer system.

[0252] The database refers to a relational database and is for managing by associating with each other a table format table, a data set called a master, which is structurally defined by rows and columns. In a database, a table is called a table, a master, a column of a table is called a column, and a row of a table is called a record. In a relational database, the relationships between tables and masters can be set and associated.

[0253] Normally, a column serving as a primary key for uniquely identifying a record is set for each table and each master, but setting a primary key for a column is not essential. The control unit can cause the processor to execute addition, deletion, and update of records to a specific table and master stored in the storage unit according to various programs.

[0254] Further, by storing data, various programs, and various databases in the storage unit, the information processing apparatus and the information processing system according to the present disclosure can be regarded as being manufactured.

[0255] In addition, the database and master in the present disclosure may include any data structure (such as a list, dictionary, associative array, object, etc.) in which information is structurally defined. The data structure shall also include data that can be regarded as a data structure by combining data with functions, classes, methods, etc. described in any programming language.

[0256] Moreover, each of the above configurations, functions, processing units, processing means, etc. may be realized in hardware by designing a part or all of them, for example, in an integrated circuit. Also, the present invention can be realized by the program code of software that realizes the functions of the embodiments. In this case, a storage medium recording the program code is provided to a computer, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing it constitute the present invention. As the storage medium for supplying such a program code, for example, a flexible disk, CD-ROM, DVD-ROM, hard disk, SSD, optical disk, magneto-optical disk, CD-R, magnetic tape, non-volatile memory card, ROM, etc. are used.

[0257] Also, the program code for realizing the functions described in the present embodiment can be implemented in a wide range of programs or script languages such as assembler, C / C++, perl, Shell, PHP, Java (registered trademark), etc.

[0258] Furthermore, by distributing the program code of software that realizes the functions of the embodiments via a network, it can be stored in a storage means such as a hard disk or memory of a computer or a storage medium such as a CD-RW or CD-R, and a processor included in the computer reads and executes the program code stored in the storage means or the storage medium.

[0259] The functions realized by the components described in this specification may be implemented in circuitry or processing circuitry, including a general-purpose processor, a special-purpose processor, an integrated circuit, ASICs (Application Specific Integrated Circuits), a CPU (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to realize the described functions. A processor includes transistors and other circuits and is regarded as circuitry or processing circuitry. The processor may be a programmed processor that executes a program stored in a memory.

[0260] In this specification, circuitry, unit, and means are hardware programmed to realize the described functions or hardware that executes. The hardware may be any hardware disclosed in this specification or any hardware known to be programmed or execute to realize the described functions.

[0261] When the hardware is a processor regarded as a type of circuitry, the circuitry, means, or unit is a combination of hardware and software used to configure the hardware and / or the processor.

[0262] Some embodiments of the present disclosure have been described above. However, these embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are to be included in the scope and gist of the invention, as well as in the invention described in the claims and the scope of equivalents thereof.

[0263] (Supplementary Note) The matters described in each of the above embodiments are appended below.

[0264] (Supplementary Note of the First Embodiment)

[0265] (Supplementary Note 1) A program for operating a computer comprising one or more computer processors, which is configured to store in a storage unit information on a paid font that requires payment of a usage fee according to usage and information on a contractor who uses the paid font. The program causes one or more computer processors to perform the steps of: generating, for each contract, embedding information to be embedded in the source code of a website so that the paid font can be displayed on the website, the embedding information being unique for each contract; storing the generated unique embedding information in the storage unit in association with the contract information; identifying, based on the embedding information of the website, the paid font used on the website when a viewer accesses the website through a browser; and causing the viewer of the website to view the website with the identified paid font being used, by responding to the identified paid font. The program also causes the steps of accepting from a user an operation of changing information on a contractor related to a contract for using a font subject to payment of a usage fee on a website without requiring a change in the embedding information generated for the website, and updating and storing in the storage unit information on a contractor who uses a paid font on the website in response to the operation of changing information on the contractor related to the contract, without requiring a change in the unique embedding information generated before the change.

[0266] (Supplementary Note 2) In the generating step, a style sheet specifying the paid font is generated to display the paid font on the website related to the contract with the contractor, and unique embedding information is generated by generating a unique link to the generated style sheet. In the specifying step, by the information of the unique link to the style sheet embedded in the source code of the website, the file of the style sheet referred to by the link is provided to the browser, thereby specifying the paid font used for the website. The program according to Appendix 1.

[0267] (Appendix 3) In the step of storing the unique embedding information in the storage unit, the unique embedding information is stored in the storage unit in association with the domain specified by the contractor. The program further causes one or more computer processors to obtain the information of the domain of the website accessed by the viewer, and when the obtained domain is the specified domain, respond with the paid font and let the viewer of the website view the website using the paid font. On the other hand, when it is not the specified domain, the viewer of the website is not allowed to view the website in a state where the paid font is used. The program according to Appendix 2.

[0268] (Appendix 4) When the domain obtained in the obtaining step is different from the specified domain, by not distributing the paid font to the terminal of the viewer of the website, the viewer of the website is not allowed to view the website in a state where the paid font is used. The program according to Appendix 3.

[0269] (Appendix 5) The website allows visitors to view the website through an edge server that temporarily holds the content of the web pages of the website and provides the held content of the web pages in response to access from the visitor's terminal, and an origin server that holds information on the content of the web pages of the website and provides the content to the edge server in response to a request from the edge server. At the edge server, it is determined whether the domain information of the website accessed by the visitor, which includes unique embedding information, is the domain specified by the contractor. The program causes one or more computer processors to further execute the steps of receiving, from the edge server, the result of the determination at the edge server, and determining whether to respond with a paid font according to the received determination result. As a result of the determination step, when responding with a paid font, the paid font is provided to the visitor's terminal via the edge server, and when not responding with a paid font, the paid font is not provided to the visitor's terminal. The program described in Supplementary Note 3.

[0270] (Supplementary Note 6) In the storage unit, as information on the paid font, the information on the fee plan that determines the usage fee for using the paid font according to the degree to which the website using the paid font is viewed, and the information on the contractor are associated and stored. The program described in Supplementary Note 2.

[0271] (Supplementary Note 7) In the storage unit, as information on paid fonts, it is configured to store, as information on the fee plan, the upper limit of the degree to which a website using a paid font is browsed and the usage fee. The website temporarily holds the content of the web page of the website and, in response to an access from the viewer's terminal, provides the content of the held web page. The website is browsed by the viewer by an edge server that provides the content of the web page of the website to the viewer and an origin server that holds the information on the content of the web page of the website and provides the content to the edge server in response to a request from the edge server. In the edge server, a program described in Appendix 5 that determines whether the upper limit defined in the fee plan conforms to the amount of access by the viewer to the website.

[0272] (Appendix 8) In the storage unit, as information on paid fonts, it is configured to store, as information on the fee plan, the upper limit of the degree to which a website using a paid font is browsed and the usage fee. When the amount of access by the viewer to the website using the paid font exceeds the upper limit, the paid font is not provided to the viewer's terminal for browsing the website. In response to the amount of access by the viewer approaching the upper limit, a notice prompting a change in the fee plan is sent to the contractor of the fee plan. A program described in Appendix 6.

[0273] (Appendix 9) The program further causes one or more computer processors to accept, from the contractor, a temporary contract for using a paid font on the premise of a change in the contractor, and store the contractor's information and unique embedding information in the storage unit. Before the change of the contractor, for the browsing of the website using the paid font by the viewer, the paid font is provided to the viewer of the website under certain restrictive conditions according to the temporary contract. A program described in Appendix 1.

[0274] (Appendix 10) A method of operating a computer comprising one or more computer processors, configured to store in a storage unit information on a paid font that requires payment of a usage fee according to usage and information on a contractee who uses the paid font, the program comprising steps of: generating, by one or more computer processors, for a contract for paying a usage fee according to usage of a paid font, embedding information for embedding into the source code of the website to display the paid font on the website, so as to be unique information for each contract; storing the generated unique embedding information in the storage unit in association with the contract information; identifying, based on the embedding information of the website, a paid font used on the website when a viewer accesses the website by a browser; and causing the viewer of the website to view the website in a state where the identified paid font is used by responding to the identified paid font; receiving from a user an operation of changing information on a contractee regarding a contract for using a font subject to payment of a usage fee on a website without requiring change of the embedding information generated for the website; and updating and storing in the storage unit information on a contractee who uses a paid font on the website without requiring change of the unique embedding information generated before the change in response to the operation of changing information on the contractee regarding the contract.

[0275] (Appendix 11) An information processing apparatus configured to store, in a storage unit, information on a paid font that requires payment of a usage fee according to usage and information on a contractor who has a contract for using the paid font, and a control unit of the information processing apparatus includes: a step of generating, for a contract for paying a usage fee in response to the use of a paid font, embedding information to be embedded in the source code of the website to display the paid font on the website so as to be unique information for each contract; a step of storing the generated unique embedding information in the storage unit in association with the contract information; a step of identifying a paid font used on the website based on the embedding information of the website when a viewer accesses the website by a browser; a step of allowing the viewer of the website to view the website in a state where the identified paid font is used by responding to the identified paid font; a step of receiving, from a user, an operation of changing information on a contractor related to a contract for using a font subject to payment of a usage fee on the website without changing the embedding information generated for the website; and a step of updating and storing, in the storage unit, information on a contractor who uses a paid font on the website without changing the unique embedding information generated before the change in response to the operation of changing information on the contractor related to the contract.

[0276] (Appendix 12) A system consisting of a font distribution server, a user's terminal, an edge server, and an origin server. The font distribution server manages information on fonts that can be used based on a contract for using fonts, and distributes font information based on a contract for using the fonts it manages. The origin server holds information on the content of the web pages of a website and responds to requests from the edge server by providing the content to the edge server. The edge server acquires and holds information on the content from the origin server, and provides the held content information to the user's terminal in response to access from the user's terminal that browses the website. The font distribution server is configured to store in a storage unit information on paid fonts that require payment of a usage fee according to usage, and information on contract holders who use the paid fonts. The control unit of the font distribution server performs steps of generating, for each contract, embedding information to be embedded in the source code of the website in order to display a paid font on the website, such that the information is unique for each contract; storing the generated unique embedding information in the storage unit in association with the contract information; identifying a paid font used on the website based on the embedding information of the website when a viewer accesses the website using a browser; responding with the identified paid font to allow the viewer of the website to view the website with the identified paid font being used; receiving from the user an operation to change the information on the contract holder regarding a contract for using a font for which payment of a usage fee is required on the website without requiring a change in the embedding information generated for the website; and updating and storing in the storage unit the information on the contract holder who uses the paid font on the website in response to the operation to change the information on the contract holder regarding the contract, without requiring a change in the unique embedding information generated prior to the change.

[0277] (Appendix of the Second Embodiment)

[0278] (Appendix 1) A system comprising a font distribution server, a user's terminal, an edge server, and an origin server, wherein the font distribution server manages information on fonts available based on a contract to use the fonts, and distributes the font information based on the contract to use the fonts being managed; the origin server holds information on the content of the web page of the website and responds to a request from the edge server by providing the content to the edge server; the edge server acquires and holds the content information from the origin server, and in response to an access from the user's terminal that browses the website, provides the held content information to the user's terminal; and the processor of the edge server, in response to an access from the user's terminal to a web page that uses a specific font managed by the font distribution server, requests the font distribution server if the specific font used on the web page is not held by the edge server, receives and holds the specific font from the font distribution server, and, in response to an access from the user's terminal to a web page that uses a specific font managed by the font distribution server, when the specific font information is held by the edge server, causes the browser of the user's terminal to browse a web page that uses the specific font by transmitting the specific font to the user's terminal without requesting the specific font from the font distribution server.

[0279] (Appendix 2) The program according to Appendix 1, wherein the processor of the edge server further executes a step of aggregating the number of times a web page that uses a specific font is browsed by the browser of the user's terminal.

[0280] (Appendix 3) The processor of the edge server further executes a step of transmitting the aggregation result aggregated in the aggregation step to a font distribution server, and the font distribution server, in association with a contract, holds information on the aggregation result and charges a contract customer for the consideration of using a font in the contract based on the aggregation result of the number of times a specific font has been viewed. The system described in Appendix 2.

[0281] (Appendix 4) The font distribution server manages information on the upper limit of the number of times a specific font can be viewed in the fee plan related to the contract, and the processor of the edge server further determines whether the aggregation result aggregated in the aggregation step reaches the upper limit of the number of times a specific font can be viewed in the fee plan related to the contract. When it is determined that the aggregation result has reached the upper limit of the number of times, the system described in Appendix 3 is used to allow the user's terminal to view the web page without providing the specific font.

[0282] (Appendix 5) When the aggregation result is about to reach the upper limit of the number of times of viewing in the fee plan, the processor of the edge server further executes a step of notifying the parties to the contract of that fact. The system described in Appendix 4.

[0283] (Appendix 6) The font distribution server grants a reward to the font creator who created the font according to the number of times the font it manages has been viewed. The system described in any one of Appendices 3 to 5.

[0284] (Appendix 7) In the storage unit of the edge server, the font file of the font managed by the font distribution server is divided in advance and held as a plurality of blocks. In the step of allowing viewing, instead of requesting the font distribution server for a specific font, the font file of the block corresponding to the font displayed on the browser of the user's terminal is transmitted to the user's terminal when a specific font is distributed to the user's terminal. The system described in any one of Appendices 1 to 6.

[0285] (Appendix 8) In the memory unit of the edge server, for each font distributed by the font distribution server, as a block that groups character types that are relatively frequently displayed on the website, the edge server pre-holds blocks of the divided font files, the system according to Appendix 7.

[0286] (Appendix 9) In the step of aggregating, at the edge server, for each domain of the web page, the edge server aggregates the number of times a web page using a specific font is viewed by the browser of the user's terminal, and the processor of the edge server further executes a step of sending the aggregation result for each domain aggregated in the aggregation step to the font distribution server. The font distribution server associates with the contract, holds the information of the aggregation result for each domain, and refers to the information of the aggregation result and presents the usage status of the font in each domain managed by the font distribution server, the system according to any one of Appendix 2 to 8.

[0287] (Appendix 10) As presenting the usage status of the font in each domain, the font distribution server displays the usage amount of the font used in each domain in a comparable manner between domains in units of domains, and displays the breakdown of the types of fonts used in each domain, the system according to Appendix 9.

[0288] (Appendix 11) As presenting the usage status of the font in each domain, the font distribution server displays the usage amount of the font used in each domain in a comparable manner between fonts in units of fonts, and displays the breakdown of the domains where the font is used for each type of font, the system according to any one of Appendix 9 to 10.

[0289] (Appendix 12) A system according to any of Appendices 9 to 11 that presents the usage status of a font in each domain, provided that the font distribution server is at least one of a font creator who creates a font managed by the font distribution server or a contractor who uses the font managed by the font distribution server under a contract.

[0290] (Appendix 13) A method executed by a system including a font distribution server, a user's terminal, an edge server, and an origin server, where the font distribution server manages information on fonts available based on a contract to use the fonts and distributes the font information based on a contract to use the fonts it manages. The origin server holds information on the content of a web page of a website and responds to requests from the edge server by sending the content to the edge server. The edge server acquires and holds the content information from the origin server and provides the held content information to the user's terminal in response to access by the user's terminal that browses the website. The method includes steps where the processor of the edge server requests the font distribution server when the edge server does not hold specific fonts used on a web page in response to access by the user's terminal to a web page that uses specific fonts managed by the font distribution server, receives and holds the specific fonts from the font distribution server, and when the edge server holds information on the specific fonts, enables the user's terminal browser to view a web page that uses the specific fonts by sending the specific fonts to the user's terminal accessing the web page without requesting the specific fonts from the font distribution server.

[0291] (Appendix 14) An edge server in a system comprising a font distribution server, a user's terminal, an edge server, and an origin server, wherein the font distribution server manages information on fonts available based on a contract for using the fonts, and distributes the font information based on the contract for using the fonts to be managed, the origin server holds information on the content of the web page of the website, and responds to the edge server with the content in response to a request from the edge server, the edge server acquires and holds the content information from the origin server, and provides the held content information to the user's terminal in response to an access by the user's terminal that browses the website, and the control unit of the edge server requests the font distribution server when the edge server does not hold the specific font used on the web page for the access of the user's terminal to the web page that uses the specific font managed by the font distribution server, receives and holds the specific font from the font distribution server, and when the edge server holds the information of the specific font in response to the access of the user's terminal to the web page that uses the specific font managed by the font distribution server, without requesting the specific font from the font distribution server, transmits the specific font to the user's terminal accessing thereto to cause the browser of the user's terminal to view the web page using the specific font, An edge server that executes

[0292] (Appendix 15) A program for operating an edge server in a system consisting of a font distribution server, a user's terminal, an edge server, and an origin server. The font distribution server manages information on fonts available based on a contract for using the fonts and distributes the font information based on the contract for using the fonts it manages. The origin server holds information on the content of a web page of a website and responds to a request from the edge server by sending the content to the edge server. The edge server acquires and holds the content information from the origin server and provides the held content information to the user's terminal in response to an access from the user's terminal that browses the website. The program causes the processor of the edge server to, in response to an access from the user's terminal to a web page that uses a specific font managed by the font distribution server, request the font distribution server when the specific font used on the web page is not held by the edge server, receive and hold the specific font from the font distribution server, and, in response to an access from the user's terminal to a web page that uses a specific font managed by the font distribution server, when the edge server holds the information on the specific font, cause the user's terminal that accesses to browse a web page using the specific font by sending the specific font to the user's terminal without requesting the specific font from the font distribution server.

Claims

1. A program for operating a computer having one or more computer processors, The storage unit is configured to store information on paid fonts that require payment of a usage fee depending on the use, and information on contractors who use the paid fonts, The program causes the one or more computer processors to: generating embedding information to be embedded in a source code of a website in order to display the paid font on the website, the embedding information being unique for each contract for which a fee is paid according to the use of the paid font; storing the generated unique embedding information in a storage unit in association with information of the contract; Identifying the paid font used on a website based on the embedding information of the website when a viewer accesses the website using a browser on the website where the paid font is used; and causing a browser of the website to browse the website in a state in which the specified paid font is used by responding with the specified paid font; receiving, from a user, an operation to change information of a contractor under a contract for using the font for which the fee is paid on the website, without requiring a change to the embedding information generated for the website; and updating and storing in the storage unit, in response to an operation for changing the information of the subscriber relating to the contract, the information of the subscriber who uses the paid font on the website, without the need to change the unique embedding information generated before the change.

2. In the generating step, generating a style sheet that designates the paid font in order to display the paid font on a website under a contract with the contractor; generating the unique embedding information by generating a unique link to the generated stylesheet; 2. The program of claim 1, wherein in the identifying step, the paid font used on the website is identified by providing the browser with a style sheet file referenced by information of a unique link to the style sheet embedded in the source code of the website.

3. In the step of storing the unique embedding information in the storage unit, The unique embedding information is stored in the storage unit in association with a domain designated by a subscriber, The program further comprises: acquiring information on the domain of a website accessed by the viewer; If the acquired domain is the specified domain, the paid font is sent as a response to the visitor of the website, allowing the visitor to view the website using the paid font; 3. The program according to claim 2, wherein if the domain is not the specified domain, the visitor to the website is not allowed to view the website in a state in which the paid font is used.

4. The program according to claim 3, further comprising: if the domain acquired in the acquiring step is different from the specified domain, the paid font is not delivered to a terminal of a visitor to the website, thereby preventing the visitor from viewing the website while the paid font is being used.

5. The website: an edge server that temporarily stores the content of a web page of the website and provides the stored content of the web page in response to an access from a terminal of a viewer; an origin server that holds information about the content of web pages of the website and provides the content to the edge server in response to a request from the edge server, thereby allowing the viewer to view the website; the edge server determines whether domain information of the website accessed by the viewer and including the unique embedding information is a domain designated by the subscriber; The program further comprises: receiving a result of the determination in the edge server from the edge server; and determining whether or not to respond with the paid font according to the result of the determination regarding the reception. The program of claim 3, wherein, as a result of the determining step, if the paid font is responded to, the paid font is provided to the viewer's terminal via the edge server, and if the paid font is not responded to, the paid font is not provided to the viewer's terminal.

6. The program according to claim 2, wherein the memory unit is configured to store, as information about the paid font, information about a fee plan that determines the usage fee for using the paid font depending on the degree to which a website in which the paid font is used is viewed, in association with information about the subscriber.

7. The storage unit is configured to store, as the information on the paid font, information on a fee plan that defines an upper limit on the number of times a website using the paid font is viewed and a usage fee for using the paid font, The website: an edge server that temporarily stores the content of a web page of the website and provides the stored content of the web page in response to an access from a terminal of a viewer; an origin server that holds information about the content of web pages of the website and provides the content to the edge server in response to a request from the edge server, thereby allowing the viewer to view the website; The program according to claim 5 , further comprising: determining, in the edge server, whether the upper limit set in the rate plan is met with respect to the amount of access by the viewer to the website.

8. The storage unit is configured to store, as information on the paid font, an upper limit on the degree to which a website using the paid font is viewed and the usage fee as information on the fee plan, When the amount of access by a viewer to the website using the paid font exceeds the upper limit, the paid font is not provided to a terminal of the viewer viewing the website; 7. The program according to claim 6, further comprising the step of notifying said contract holder of said fee plan of a request to change said fee plan in response to the amount of access by said viewer approaching said upper limit.

9. The program further comprises: accepting a temporary contract for use of the paid font from the contractor, on the premise of changing the contractor, and storing the contractor information and the unique embedding information in the storage unit; The program according to claim 1, wherein before the change of the subscriber, the paid font is provided to a viewer of the website under certain restrictive conditions corresponding to the temporary contract with respect to the viewer's viewing of the website that uses the paid font.

10. 1. A method of operating a computer having one or more computer processors, comprising: The storage unit is configured to store information on paid fonts that require payment of a usage fee depending on the use, and information on contractors who use the paid fonts, The method further comprises the step of: generating embedding information to be embedded in a source code of a website in order to display the paid font on the website, the embedding information being unique for each contract for which a fee is paid according to the use of the paid font; storing the generated unique embedding information in a storage unit in association with information of the contract; Identifying the paid font used on a website based on the embedding information of the website when a viewer accesses the website using a browser on the website where the paid font is used; and causing a visitor to the website to view the website in a state in which the visitor uses the identified paid font by responding with the identified paid font; receiving, from a user, an operation to change information of a contractor under a contract for using the font for which the fee is paid on the website, without requiring a change to the embedding information generated for the website; and updating and storing in the storage unit, in response to an operation for changing the information of the subscriber related to the contract, the information of the subscriber who uses the paid font on the website, without the need to change the unique embedding information generated before the change.

11. An information processing device, The storage unit is configured to store information on paid fonts that require payment of a usage fee depending on the use, and information on contractors who use the paid fonts, A control unit of the information processing device generating embedding information to be embedded in a source code of a website in order to display the paid font on the website, the embedding information being unique for each contract for which a fee is paid according to the use of the paid font; storing the generated unique embedding information in a storage unit in association with information of the contract; Identifying the paid font used on a website based on the embedding information of the website when a viewer accesses the website using a browser on the website where the paid font is used; and causing a visitor to the website to view the website in a state in which the visitor uses the identified paid font by responding with the identified paid font; receiving, from a user, an operation to change information of a contractor under a contract for using the font for which the fee is paid on the website, without requiring a change to the embedding information generated for the website; and updating and storing in the memory unit, in response to an operation to change the information of the subscriber related to the contract, without the need to change the unique embedding information generated before the change.

12. A system comprising a font distribution server, a user terminal, an edge server, and an origin server, the font distribution server manages information on available fonts based on a contract for using the fonts, and distributes the information on the fonts based on the contract for using the fonts it manages; the origin server holds information on the content of web pages of a website, and responds to the edge server with the content in response to a request from the edge server; the edge server acquires information on the content from the origin server and stores it, and provides the stored information on the content to a terminal of the user in response to an access from the terminal of the user browsing a website; The font distribution server includes: The storage unit is configured to store information on paid fonts that require payment of a usage fee depending on the use, and information on contractors who use the paid fonts, A control unit of the font distribution server, generating embedding information to be embedded in a source code of a website in order to display the paid font on the website, the embedding information being unique for each contract for which a fee is paid according to the use of the paid font; storing the generated unique embedding information in a storage unit in association with information of the contract; Identifying the paid font used on a website based on the embedding information of the website when a viewer accesses the website using a browser on the website where the paid font is used; and causing a visitor to the website to view the website in a state in which the visitor uses the identified paid font by responding with the identified paid font; receiving, from a user, an operation to change information of a contractor under a contract for using the font for which the fee is paid on the website, without requiring a change to the embedding information generated for the website; and updating and storing in the memory unit, in response to an operation for changing the information of the subscriber relating to the contract, the information of the subscriber who uses the paid font on the website, without the need to change the unique embedding information generated before the change.

Images