Method for providing web font service by messaging service application and server for providing same

Abstract

To provide a method, device, and recording medium for implementing a web font service that can meet various needs for respective customers, protect the copyright of fonts themselves, and improve the rendering speed of web fonts in messaging application screens.SOLUTION: A method for providing a web font service includes: a step in which a message sender sends a message to at least one recipient via a first server of an application; a step in which the message sender and the recipient make a request to a second server for font files; and a step in which text rendering is performed on a screen using a requested and received subset web font file. Regarding the subset web font file, the second server verifies dedicated authentication keys for the message sender and the recipient, generates the subset web font file, and transfers it to the message sender and the recipient.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a method for providing a web font service through a messaging service application and a server for providing the same. [Background technology]

[0002] Web fonts are a technology that uses font files to display text within applications, and their use is increasing as the platforms for accessing applications become more diverse, such as mobile phones and tablets. This has led to a demand for the development of technology that can serve web fonts within application screens in a way that can meet the diverse needs of customers.

[0003] In this regard, in the case of conventional prior art related to web fonts, web fonts are provided in two subsets, a first subset font and a second subset font, and based on this, information about the font is provided only on the web page.

[0004] In providing web fonts in this prior patent (Web font server providing subset fonts and web font system including the same (Korean Patent Application No. 10-2012-0050470)), the method including a step of dividing subset fonts can slow down the rendering speed of web fonts in application screens, and if the rendering speed of web fonts slows down, various problems can occur.

[0005] For example, if the rendering speed of web fonts slows down, text may suddenly appear after being invisible (FOIT, Flash of Invisible Text) or flicker while changing (FOUT, Flash of Unstyled Text), which can cause inconvenience to customers using the application.

[0006] Furthermore, as the mobile messenger market expands, users prefer interfaces that reflect their individuality rather than uniform application interfaces. Therefore, there is a need to build and provide web font services that allow users to express their individuality in applications for sending and receiving messages.

[0007] Specifically, there is a need for a method of providing web font services that can meet various customer needs, protect the copyright of the fonts themselves, and improve the rendering speed of web fonts in messaging application screens. Summary of the Invention [Problem to be solved by the invention]

[0008] The present invention is intended to solve the above problems, and aims to propose a method for providing a web font service in response to a web font request from a customer who uses a messaging service of an application.

[0009] More specifically, the present invention aims to propose a font provision method that allows a primary user providing a messaging service and a sender and receiver exchanging messages within an application provided by the primary user's server to use web fonts.

[0010] Another object of the present invention is to propose a web font service method that minimizes the time consumed by each customer in using web fonts, thereby improving the rendering speed of application screens, and minimizes the possibility of web font leakage by providing a portion of the web fonts. [Means for solving the problem]

[0011] To solve the above technical problems, a method for providing a Web font messaging service for a messaging service application, performed by at least one processor according to the present invention, includes the steps of: a message sender sending a message to at least one recipient via a first server of the application; the message sender and recipient requesting font files from a second server; and the application rendering text on a screen using the requested and received subset Web font files, wherein the second server preferably verifies dedicated authentication keys for the message sender and recipient, generates subset Web font files, and transmits the subset Web font files to the message sender and recipient.

[0012] The second server may also include the steps of checking the first user's web font service usage information, which is composed of a list of available fonts; generating and storing an authentication key dedicated to the first user based on the usage information; providing the first user with the generated authentication key and web font SDK; and the first user adding font-related information to a messaging transmission / reception format within the first server based on the provided information, and reflecting it in an application provided by the first server.

[0013] In addition, the web font SDK can be inserted into an application provided by the first server for at least one operating system (OS) or programming language using the generated authentication key dedicated to the first user.

[0014] In addition, the message received via the first server of the messaging service application may include web font information selected by the sender and authentication key information exclusive to the sender.

[0015] In addition, the second server may, upon request from a sender and a receiver using an application provided by the first server, check the sender's authentication key, which includes expiration information for the authentication key, and based on this, generate a subset web font file and transmit it to at least one receiver's device.

[0016] Meanwhile, a method for providing web fonts for a messaging service application includes the steps of: a second server checking web font service usage information of the application and generating an authentication key dedicated to a user of the application; the application checking the user-specific authentication key and requesting a font for text rendering from the second server using a dedicated web font SDK; and the application performing text rendering on the user terminal using the received subset web font file, wherein the second server preferably checks the validity of web font request information including the user-specific authentication key, generates the subset web font file, and transfers it to the web font SDK.

[0017] In addition, the second server can verify the authentication key dedicated to the first user for user authentication, and based on this, generate an authentication key dedicated to the user that includes expiration information of the authentication key.

[0018] In addition, the web font SDK may have a cache function for recently used fonts in the step of requesting a font from the second server, and the cache function may include a function of reusing a recently used subset web font file or using a subset web font file containing frequently used text depending on the requested font text.

[0019] In addition, the second server may provide a subset web font file for frequently used text for the requested text, and may provide a subset web font file including predicted answer text calculated using an AI-based chatbot.

[0020] Meanwhile, the present invention can be realized as a computer-readable recording medium storing a program for performing the above-described method for providing a Web font service. [Effects of the Invention]

[0021] According to the present invention, when providing a web font messaging service, the dedicated authentication keys of the message sender and recipient are confirmed, and based on this, a subset web font file is used that is reflected in the application screen provided by the first server, thereby providing an optimized service for each customer who uses web fonts.

[0022] In addition, when providing a web font service, the present invention uses a user-specific web font SDK for application user authentication and subset web font generation, thereby minimizing the time consumed by using web fonts when rendering application screens, reducing the size of web fonts, shortening the download time for web fonts, and further reducing network traffic and costs. [Brief explanation of the drawings]

[0023] [Figure 1] 1 is an exemplary diagram illustrating a process for providing a web font messaging service according to an embodiment of the present invention. [Figure 2] 1 is a flowchart illustrating a process for providing a web font messaging service according to an embodiment of the present invention. [Figure 3]1 is a conceptual diagram illustrating a process of registering service usage information for using a web font messaging service according to an embodiment of the present invention. [Figure 4] 1 is a timing diagram illustrating a process for providing a web font messaging service according to an embodiment of the present invention. [Figure 5] 1 is an exemplary diagram illustrating a process for authentication and service provision for providing a web font messaging service according to an embodiment of the present invention. [Figure 6] 1 is a timing diagram illustrating a process for authentication and service provision for providing a web font messaging service according to an embodiment of the present invention. [Figure 7] 10 is an exemplary diagram illustrating a method for providing a web font messaging service according to another embodiment of the present invention. [Figure 8] FIG. 2 illustrates a computing device implementation of a server providing a web font service according to one embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0024] The following merely illustrates the principles of the invention. Thus, those skilled in the art will be able to invent various devices that embody the principles of the invention and are within the concept and scope of the invention, although not explicitly described or shown herein. Furthermore, all conditional terms and embodiments listed herein are expressly intended, in principle, solely for the purpose of enabling the concept of the invention to be understood, and are not limiting to the embodiments and conditions so specifically listed.

[0025] The above-mentioned objects, features, and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, which will enable those skilled in the art to easily implement the technical ideas of the invention.

[0026] In addition, when describing the invention, if it is determined that a detailed description of the prior art related to the invention may obscure the gist of the invention, the detailed description will be omitted. Hereinafter, a preferred embodiment of the present invention will be described in detail with reference to the accompanying drawings.

[0027] Hereinafter, a process for providing a web font messaging service by an application according to an embodiment of the present invention will be described with reference to FIG.

[0028] FIG. 1 is an exemplary diagram illustrating a process for providing a web font messaging service according to an embodiment of the present invention.

[0029] In this embodiment, the web font service system 1000 can be composed of a sender terminal 500-1 and a receiver terminal 500-2 that receive a messaging service to which web fonts are applied via a first server 200 that provides a messaging service and a second server 300 that provides a web font service.

[0030] In this embodiment, the first server 200 corresponds to a service provider that provides messaging services to the sender terminal 500-1 and the receiver terminal 500-2, and the second server 300 corresponds to a provider that provides web font services to the first server 200 and the user terminal 500 that uses it.

[0031] The second server 300 can generate and store various font files and subset web fonts and provide various font information to a font requester.

[0032] Specifically, the second server 300 can provide web font information and subset web font files in response to web font requests from user terminals 500, including a sender terminal 500-1 and a receiver terminal 500-2, and can perform web font service authentication procedures, web font service registration procedures, etc.

[0033] The second server 300 can generate and store unique authentication information for the first server 200 and the user terminal 500 that uses the first server 200 to provide the Web font service.

[0034] The source font storage module in the second server 300 stores and manages source font files by font, and if the font file requested by the sender / receiver terminals 500-1 and 500-2 is not available in the font providing module to provide a web font service, the source font storage module can transfer an encrypted file of the font to the font providing module.

[0035] Hereinafter, a process for providing a web font messaging service according to an embodiment of the present invention will be described with reference to FIG.

[0036] FIG. 2 is a flowchart illustrating a process for providing a web font messaging service according to an embodiment of the present invention.

[0037] In this embodiment, the sender terminal 500-1 transmits a message to at least one receiver terminal 500-2 via the first server 200 (S10).

[0038] The sender terminal 500-1 and the receiver terminal 500-2, which received the message sent by the sender terminal 500-1 from the first server 200, each request the font file selected by the sender terminal 500-1 from the second server 300 (S20). The second server 300 checks authentication information in response to the requests from the sender terminal 500-1 and the receiver terminal 500-2 and generates a subset web font file. The authentication information may include a primary authentication value for providing the first server 200 with a primary list of available fonts and a secondary authentication value for the font selected from the available font list.

[0039] Here, the sender terminal 500-1 can request a font file from the second server 300 by re-receiving a message including authentication information from the first server 200 in response to the sent message. The second server 300 can confirm that the first server 200 has completed the registration process and authentication of service usage information in a B2B format for the web font-based messaging service based on the primary authentication value in the authentication information, and can confirm that the user of the first server 200 has requested a font selected from the fonts provided based on the secondary authentication value.

[0040] Once authentication is complete, the second server 300 transfers the generated subset Web font file to the sender terminal 500-1 and the receiver terminal 500-2, and the sender terminal 500-1 and the receiver terminal 500-2 each use the received subset Web font file to text render the message (S30).

[0041] Hereinafter, the process of registering web font messaging service usage information according to the present embodiment will be described in more detail with reference to FIG.

[0042] FIG. 3 is a conceptual diagram illustrating a process of registering service usage information for using a web font messaging service according to an embodiment of the present invention.

[0043] In this embodiment, the second server 300 may register usage information in a font providing module in the second server 300 upon receiving a request for a web font service within the messaging service of the first server 200. Here, the usage information may include, as product information, at least one of a font list used by the first server 200, identification information of the messaging service to be applied, and a test IP.

[0044] The first server 200 can purchase each Web font individually for a set price, or purchase a license for a set period of time for a set price, or purchase a set of Web fonts within a specific range on a subscription basis for free use.

[0045] The purchasing method of the Web font is not limited to the above example, and the font can be purchased and used in various ways depending on the sales method of the second server 300.

[0046] The second server 300 is a module for providing fonts in conjunction with the messaging service of the first server 200, and may be comprised of a font providing module and a source font storage module for managing source information related to fonts.

[0047] Therefore, the font providing module stores a font file in advance and generates and provides a subset of glyphs included in a message of the messaging service. In this case, if the font file does not exist, the font providing module can request the source font file from the source font storage module.

[0048] The source font storage module transmits the encrypted file of the requested font to the font providing module, and the font providing module can decrypt and store the received encrypted font file.

[0049] Meanwhile, the font providing module and the source font storage module are not limited to being separate. For example, the source font storage module may exist as a single database of the font providing module. Alternatively, the source font storage module may be configured as an external server, and the font providing module may receive font files from the external server and provide the web font service described below. Here, the source font storage module may be configured as a separate server of a font rights holder that has the rights to each font, rather than being subordinate to the second server 300.

[0050] The second server 300 can generate and store authentication information for authenticating the first server 200, and can generate a dedicated authentication key containing the authentication information and a web font SDK (Software Development Kit) according to the registered service usage information of the first server 200 and provide them to the first server 200.

[0051] The web font SDK is a set of tools for developing programs to perform specific functions on a user terminal in a form that can be installed in a messaging application in conjunction with the above-mentioned font providing module. In this embodiment, the SDK includes libraries, APIs, etc. for identifying the font included in the message and the glyph to which the font is applied, and requesting a subset web font from the font providing module of the second server 300 along with authentication information.

[0052] Therefore, the SDK 515 provided by the second server 300 may be provided for each operating system (OS) of the user terminal or for each programming language capable of interfacing with the messaging service.

[0053] Next, the first server 200 can realize a service environment using an SDK module 515 realized by adding font-related information to a messaging transmission / reception data format and inserting a web font SDK provided by the second server 300 into the application 510. Here, the first server 200 inserts the web font SDK 515 using an authentication key dedicated to the first server 200, thereby providing a more stable service.

[0054] Hereinafter, a process for providing a web font messaging service according to an embodiment of the present invention will be described with reference to FIG.

[0055] FIG. 4 is a timing diagram illustrating a process for providing a web font messaging service according to an embodiment of the present invention.

[0056] For the sake of convenience, FIG. 4 will be used to explain the process of transmitting and receiving information between sender terminal 500-1 and receiver terminal 500-2, focusing on second server 300.

[0057] Referring to FIG. 4, as described in FIG. 3, the first server 200 can apply web font related information to the messaging transmission / reception data format in advance (S101).

[0058] Next, the sender terminal 500-1 can input a message including the font information selected for use via an application (S102) and transmit the message to the first server 200 (S103).

[0059] The sender terminal 500-1 and the receiver terminal 500-2 may receive the message transmitted to the first server 200 (S104). Specifically, the received message may include an authentication key and applied web font information.

[0060] The sender terminal 500-1 and the receiver terminal 500-2 that have received the above messages can request the font file from the second server 300 (S105).

[0061] Specifically, the request for the font file may include identification information about the font being used, text information about the message, and the received authentication key.

[0062] In response to the font file request, the second server 300 may check whether the authentication keys of the sender terminal 500-1 and the receiver terminal 500-2 are valid (S106). To check the validity, the second server 300 may check at least one of the sender ID included in the authentication key, whether the available font list matches the requested font, and the validity period.

[0063] If the second server 300 determines that the font request is valid by checking whether the authentication key is valid, it generates an optimized subset web font based on the requested web font request information (S107). Here, the subset web font may refer to a font file with a more compressed size by providing only fonts for glyphs used to improve dynamic loading performance. The subset web font file is data generated based on text information in the web font request information, and may also include an alternative font subset depending on whether an alternative font is included.

[0064] Specifically, the second server 300 may perform font subsetting based on text information in the web font request information and pre-stored web fonts to generate a subset web font.

[0065] In addition, the second server 300 may store the generated subset web font for a predetermined period of time, thereby providing a faster service for font file requests. Here, the predetermined period may be determined based on frequently used messages according to the characteristics of the messaging application, or may be variably determined based on the size of the subset web font.

[0066] Next, the second server 300 may transmit the subset Web font file generated based on the Web font request information to the sender terminal 500-1 and the receiver terminal 500-2 (S108).

[0067] When the second server 300 receives a web font request that is the same as the information previously requested from the sender terminal 500-1 and the receiver terminal 500-2, if rendering is possible using the glyphs in the stored subset web font file, the second server 300 can omit the above-mentioned generation (S107) step and immediately transfer the previously generated and stored subset web font file to the sender terminal 500-1 and the receiver terminal 500-2.

[0068] The sender terminal 500-1 and the receiver terminal 500-2 that received the subset Web font file from the second server 300 can display text on the screen using the received subset Web font file (S109).

[0069] As described above, according to the present invention, by providing a customer-specific web font service via the second server 300, the font desired by the user can be easily applied to the application 510 in the user terminal 500 along with the messaging service of the first user.

[0070] In addition, when service usage information changes, such as when the first server 200's service usage period expires or the messaging application version changes, the present invention can improve the stability of subset-based web fonts by providing a subset web font file to which substitute font information based on the font selected by the second server 300 is applied.

[0071] Hereinafter, a method for providing a web font messaging service according to an embodiment of the present invention will be described with reference to FIG.

[0072] FIG. 5 is an example diagram illustrating a method for authentication and service provision for providing a web font messaging service according to an embodiment of the present invention.

[0073] In this embodiment, when a user attempts to use a web font service by running an application 510 of the first server 200 using a user terminal 500, the SDK module 515 in the application 510 can request a user-specific authentication key from the second server 300, and the second server 300 can provide the user terminal 500 with the specific authentication key.

[0074] Then, the user terminal 500 requests the subset Web font file from the second server 300 based on the provided dedicated authentication key information, receives the Web font, renders it based on the provided subset Web font file, and displays text on the screen of the application 510.

[0075] Hereinafter, a method for providing a Web font messaging service according to this embodiment will be described with reference to FIG.

[0076] FIG. 6 is a timing diagram illustrating a method for providing a web font messaging service according to an embodiment of the present invention.

[0077] Referring to FIG. 6, a user can use a user terminal 500 to run an application 510 provided by the first server 200 (S201).

[0078] Next, the user terminal 500 can request a user-specific authentication key from the second server 300 through the activated application 510 (S202). Here, the information requested as the user-specific authentication key can include at least one of a user ID, a list of fonts available to the user, and an authentication key validity period.

[0079] The second server 300 can generate the requested authentication key (S203) and provide it to the user terminal 500 (S204).

[0080] The user terminal 500 checks font information for rendering the text included in the message using the Web font SDK module 515 (S205) and may request a subset Web font file from the second server 300 based on the authentication key (S206). The request information for the Web font file may include text data for the requested Web font and an authentication key required for the authentication procedure to use the Web font service.

[0081] In addition, the Web font SDK module 515 according to this embodiment may have a cache function that temporarily stores recently used fonts. The Web font SDK module 515 uses the cache function to reuse recently used subset Web fonts, and temporarily stores subset Web fonts of text for frequently used phrases (e.g., expressions for greetings, responses, etc.) in the user terminal 500, making them available without further requests.

[0082] Therefore, in the step of checking font information (S205), if the font and text included in the font request can be rendered using the subset web font returned from the font providing module within a predetermined period of time, the web font SDK 515 provides the stored subset web font to the user terminal 500 without a further request process, and the text can be displayed in the desired font.

[0083] The second server 300 checks the validity of the authentication key received in response to the web font file request from the user terminal 500 (S207), generates a subset web font file (S208), and can provide it to the user terminal 500 (S209). If the result of checking the validity of the authentication key shows that the caller ID cannot be identified, the available font list does not match the requested font, or the font's validity period has expired, the request can be determined to be invalid.

[0084] For example, if the second server 300 determines that the font file request is invalid and is an abnormal access, the second server 300 may transmit an error response to the user terminal 500 and notify the first server 200 of the abnormal access. Here, the second server 300 returns the error, and the web font SDK module 515 renders and displays text in the base font for sending and receiving user messages.

[0085] If the authentication key is found to be valid and the font request is found to be valid, the second server 300 generates an optimized subset Web font file based on the requested Web font request information.

[0086] Specifically, the second server 300 may perform font subsetting based on the text information in the web font request information and the pre-stored web fonts, as described above, to generate a subset web font file.

[0087] In addition, in the process of generating the subset web font, the second server 300 can generate and provide a frequently used text subset web font in advance, and can provide a subset web font including a predictable answer. To this end, the second server 300 can extract statistical information on the frequency of use from the short messaging text and continuously update the frequently used answer text configured in a predetermined size.

[0088] Furthermore, the second server 300 can predict the next word or sentence based on the requested glyph using a generative language model and generate a further subset. Therefore, the second server 300 can provide the user terminal 500 with a subset web font that includes fonts for glyphs of the expected answer text in a subset corresponding to the glyphs of the requested text.

[0089] The user terminal 500 can use the subset Web font file received from the second server 300 to render and display text on the application 510 screen (S210).

[0090] According to the present invention described above, by generating text information by assembling the text in the application 510 by font, and using the web font SDK module based on this, it is possible to minimize the time consumed by using web fonts when rendering the application 510.

[0091] In addition, by using an optimized subset of web fonts when providing web font information, the size of the web font can be reduced.

[0092] Furthermore, by reducing the size of the web font, the download time of the web font can be shortened, and network traffic and costs can be reduced.

[0093] Hereinafter, a process for providing a web font messaging service according to another embodiment of the present invention will be described with reference to FIG.

[0094] FIG. 7 is an exemplary diagram illustrating a method for providing a web font messaging service according to a further embodiment of the present invention.

[0095] In the above embodiment, the first server 200 and the second server 300 that provide the web font service are described as being separate configurations during the message sending and receiving process between the sender terminal 500-1 and the receiver terminal 500-2, but the first server 200 and the second server 300 may also be configured within a single server.

[0096] Specifically, the second server 300 can be configured with one font module 205 in the first server 200, and can provide fonts for messages sent and received by the first server 200 upon request from the user terminal 500.

[0097] Hereinafter, with reference to FIG. 8, a specific hardware implementation of the second server 300 as a computing device that provides the Web font messaging service according to this embodiment will be described.

[0098] 8, in some embodiments of the present invention, the second server 300 may be implemented in the form of a computing device. One or more of the modules constituting the second server 300 may be implemented on a general-purpose computing processor and may therefore include a processor 388, an input / output I / O 382, ​​a memory 384, an interface 386, and a bus 385. The processor 388, the input / output I / O 382, ​​the memory 384, and / or the interface 386 may be coupled to one another by a bus 385. The bus 385 corresponds to a path along which data travels.

[0099] Specifically, the processor 388 may include at least one of a central processing unit (CPU), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphic processing unit (GPU), a microprocessor, a digital signal processor, a microcontroller, an application processor (AP), and logic elements capable of performing similar functions.

[0100] The input / output I / O 382 may include at least one of a keypad, a keyboard, a touch screen, and a display device. The memory 384 may store data and / or programs.

[0101] The interface 386 can transfer data to or receive data from a communication network. The interface 386 can be wired or wireless. For example, the interface 386 can include an antenna or a wired / wireless transceiver. The memory 384 is a volatile operating memory for improving the operation of the processor 388 and protecting personal information, and can further include high-speed RAM and / or ERAM.

[0102] Also stored within memory 384 are programming and data structures that provide the functionality of some or all of the modules described herein, and may include, for example, logic that causes selected aspects of the learning methods described above to be performed.

[0103] A program or application containing a set of instructions containing steps for carrying out the above-described method stored in memory 384 is loaded to cause the processor to carry out the steps.

[0104] Furthermore, the various embodiments described herein may be implemented, for example, using software, hardware, or a combination thereof in a computer-readable storage medium or similar device.

[0105] According to a hardware implementation, the embodiments described herein may be implemented using at least one of application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, or other functionally performing electrical units. In some cases, the embodiments described herein may be implemented as the control module itself.

[0106] In a software implementation, the procedures and functions described herein may be implemented in separate software modules, each of which may perform one or more of the functions and operations described herein. The software code may be implemented by a software application written in a suitable programming language. The software code may be stored in a memory module and executed by a control module.

[0107] Specifically, the above description is merely an illustrative example of the technical concept of the present invention, and a person having ordinary knowledge in the technical field to which the present invention pertains can make various modifications, variations, and substitutions within the scope that does not deviate from the essential characteristics of the present invention.

[0108] Therefore, the embodiments and accompanying drawings disclosed in the present invention are for the purpose of explanation, not for the purpose of limiting the technical idea of ​​the present invention, and the scope of the technical idea of ​​the present invention is not limited by such embodiments and accompanying drawings. The scope of protection of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent range should be interpreted as being included in the scope of the present invention.

Claims

1. 1. A method for providing a web font messaging service for a messaging service application executed by at least one processor, comprising: a message sender terminal sending said message to at least one recipient terminal via a first server of said application; The message sender terminal and the recipient terminal request a font file from a second server; the second server verifying whether a dedicated authentication key between the sender of the message and the recipient is valid; generating a subset Web Font file by the second server after the verifying step; A step in which the sender terminal of the message and the recipient terminal receive the subset Web font file transferred by the second server; A step in which the sender terminal and the recipient terminal of the message use the received subset Web font file to perform text rendering on a user screen; Including, In the step of requesting the font file, a terminal of the sender of the message receives the message again from the first server, the message including the dedicated authentication key of the sender of the message, and requests the font file from the second server; the second server checks usage information of the web font service of the first server, which is configured as a list of available fonts, generates and stores an authentication key dedicated to the first server based on the usage information, and then provides the authentication key dedicated to the first server and a web font SDK to the first server; The first server adds font-related information to a messaging transmission / reception format in the first server based on the information provided by the second server, and reflects the font-related information in an application of the messaging service. A method for providing a web font messaging service, comprising:

2. The Web Font SDK includes: The method for providing a web font messaging service as described in claim 1, characterized in that the service is provided to applications provided by the first server for at least one operating system (OS) or programming language using an authentication key dedicated to the first server.

3. The method for providing a web font messaging service according to claim 1, characterized in that the message received through the first server of the messaging service application includes web font information selected by the sender and authentication key information dedicated to the sender.

4. 2. The method of claim 1, wherein the second server, in response to a request from the sender's terminal and the receiver's terminal using the application provided by the first server, checks the sender's authentication key including expiration information of the authentication key, and based on this, generates a subset web font file and transmits it to at least one of the receiver's terminals.

5. A method for providing web fonts by an application of a messaging service of a font server, comprising: The second server checks the usage information of the web font service of the first server, the usage information being configured as an available font list; generating and storing, by the second server, an authentication key dedicated to the first server based on the usage information; The second server provides the first server with an authentication key and a web font SDK dedicated to the first server; The second server confirms the web font service usage information of the application and generates an authentication key dedicated to the user of the application; Including, The first server adds font-related information to a messaging transmission / reception format in the first server based on the information provided by the second server, and reflects the font-related information in an application of the messaging service; The application confirms the user-specific authentication key and requests a font file for text rendering from the second server using a Web font SDK module; the message sender's terminal re-receives the message including the message sender's specific authentication key from the first server and requests the font file from the second server; the second server verifies whether the dedicated authentication keys of the sender and recipient of the message are valid; The second server generates a subset Web font file after verifying whether the dedicated authentication keys of the sender and the recipient of the message are valid; The terminal of the sender of the message and the terminal of the recipient receive the subset Web font file transferred by the second server; The terminal of the sender of the message and the terminal of the recipient use the received subset web font file to perform text rendering on a user screen. A method for providing a web font, comprising:

6. The method for providing web fonts described in claim 5, characterized in that the second server checks the dedicated authentication key of the first server to authenticate the user, and based on this, generates a dedicated authentication key for the user that includes expiration date information for the authentication key.

7. 6. The method of claim 5, wherein the web font SDK module temporarily stores a recently used font when requesting the font from the second server.

8. The second server responds to the requested text by:

6. The method for providing a Web font according to claim 5, further comprising providing a subset Web font file including additional fonts for predicted glyphs calculated using the generative model.

9. A terminal of a message sender; a terminal of a recipient of the message; a first server and a second server of a messaging service application; Equipped with a terminal of the sender of the message sends the message to at least one terminal of the recipient via the first server; The message sender's terminal and the recipient's terminal request a font file from the second server; the second server verifies whether a dedicated authentication key between the sender of the message and the recipient is valid; The second server generates a subset Web font file after verifying whether the dedicated authentication keys of the sender and the recipient of the message are valid; The terminal of the sender of the message and the terminal of the recipient receive the subset Web font file transferred by the second server; The sender's terminal and the recipient's terminal of the message use the received subset Web font file to perform text rendering on a user screen; In the operation of requesting the font file, a terminal of the sender of the message receives the message again from the first server, the message including the dedicated authentication key of the sender of the message, and requests the font file from the second server; the second server checks usage information of the web font service of the first server, which is configured as a list of available fonts, generates and stores an authentication key dedicated to the first server based on the usage information, and then provides the authentication key dedicated to the first server and a web font SDK to the first server; The first server adds font-related information to a messaging transmission / reception format in the first server based on the information provided by the second server, and reflects the font-related information in an application of the messaging service. An information processing system comprising:

10. A terminal of a message sender; a terminal of a recipient of the message; a first server and a second server of a messaging service application; Equipped with The second server checks the usage information of the web font service of the first server, which is configured as an available font list; the second server generates and stores an authentication key dedicated to the first server based on the usage information; The second server provides the first server with an authentication key and a web font SDK dedicated to the first server; The second server checks the web font service usage information of the application and generates an authentication key dedicated to the user of the application; The first server adds font-related information to a messaging transmission / reception format in the first server based on the information provided by the second server, and reflects the font-related information in an application of the messaging service; The message sender's terminal and the recipient's terminal confirm the user-specific authentication key and request a font file for text rendering from the second server using a Web font SDK module, and the message sender's terminal re-receives the message including the message sender's specific authentication key from the first server and requests the font file from the second server; the second server verifies whether a dedicated authentication key between the sender of the message and the recipient is valid; The second server generates a subset Web font file after verifying whether the dedicated authentication keys of the sender and the recipient of the message are valid; The terminal of the sender of the message and the terminal of the recipient receive the subset Web font file transferred by the second server; The terminal of the sender of the message and the terminal of the recipient use the received subset web font file to perform text rendering on a user screen. An information processing system comprising:

11. A computer-readable recording medium storing a program for performing the method for providing a Web font messaging service according to any one of claims 1 to 8.

Images