JP7504430B2 - Seal provision system - Google Patents

Description

The present invention relates to a system and method for managing the impression information of a seal provided to a user, and a system for providing a seal.

Conventionally, a system has been known that allows an orderer (user) to order a name seal by operating an order terminal connected to an order server via a network (see, for example, Patent Document 1). In this system, selectable kanji characters corresponding to the name (kana) entered by the orderer are displayed on the screen of the order terminal, with both common kanji characters and special kanji characters being displayed. By selecting the kanji characters (stamp content) displayed on the screen of the order terminal, the user can order not only name seals with common kanji characters (standard name seals) but also name seals with special kanji characters (non-standard name seals) online, thereby obtaining the desired name seal.

JP 2002-7807 A

However, as mentioned above, when both common kanji and special kanji are displayed, the display of the special kanji will be a display of unnecessary information for a user whose desired name seal is in common kanji, and the display of the common kanji will be a display of unnecessary information for a user whose desired name seal is in special kanji. Having to check the displayed content, including such unnecessary information, is troublesome for the user (the person receiving the name seal), and is inconvenient.

The present invention was made in consideration of the above circumstances, and its purpose is to provide a system and method that can improve the convenience of providing seals.

To solve the above problems, the present invention adopts the following measures.

The seal providing system of the first method is as follows:
A system for providing a seal to a user, comprising:
A first management means for managing information on a seal impression created based on the seal impression content input by a user;
A determination means for determining whether or not the print information managed by the first management means satisfies a predetermined standard;
A second management means for managing stamp face information of a standard seal;
A registration means for registering the seal information determined by the determination means to satisfy the predetermined standard in the second management means ,
When the seal information determined to satisfy the predetermined criteria is registered in the second management means, the registered seal information is managed as a similar type to the seal information of the standard seal,
A seal created based on the seal face information managed by the second management means can be provided in response to a request from a user.
The gist of the present invention is as follows.

According to this system, among the seal information (seal information managed by the first management means) of a seal created based on the seal contents input by the user, seal information that meets a predetermined standard is managed by the second management means as a type similar to the seal information of a standard seal. Then, a seal created based on the seal information managed by the second management means can be provided in response to a request from a user. This makes it easier for a user to select a desired seal by limiting the number of types of seals managed as standard seals, thereby improving convenience. It is also possible to avoid unnecessary registration in the management means (second management means) in which the seal information of standard seals is managed.

Note that "seal" includes not only actual seals such as rubber stamps, hard stamps, and ink stamps, but also electronic seals that can be stamped on a terminal by pasting the seal image, which is a digitalized version of the seal impression, onto an electronic document displayed on the terminal (same below). Also, "seal information" refers to information that constitutes the seal (seal impression), such as the seal characters, font, seal frame shape, seal size, color, seal layout (vertical writing, horizontal writing, with or without subtitles, with or without line breaks, etc.), and seal impression image (same below).

The seal providing system of the second aspect of the present invention is the seal providing system of the first aspect of the present invention,
A providing device that provides a seal to a user;
A seal creating device is provided.
the provider device includes the second management means,
the production side device includes the first management means, the determination means , and the registration means,
the providing device and the creating device are communicatively connected via a network;
The registration means transfers the seal information determined to satisfy the predetermined criterion to the providing side device and registers it in the second management means.

According to this system, the seal information of the seal created based on the seal contents input by the user is managed by the creating device, and the seal information that meets a predetermined standard is transferred to the providing device and registered in the second management means. This enables efficient management and provision of the seal information.

According to the present invention described above, it is possible to provide a system that can improve the convenience of providing a seal.

FIG. 1 is a configuration diagram of a system according to an embodiment of the present invention. FIG. 13 is a diagram showing an example of a seal face table. 13 is a flowchart of an electronic seal setting process. 13 is a flowchart of a seal request process. 13 is a flowchart of a print information management process. FIG. 13A is a diagram showing an example of a setting screen, and FIG. 13B is a diagram showing an example of a print content input screen. 13A and 13B are explanatory diagrams of seal information to be registered.

The following describes an embodiment of the present invention with reference to the drawings. In the following, we will explain an example in which the seal provided to the user is an electronic seal in which the impression of a name seal has been converted into image data.

[Overall system configuration]
As shown in Figure 1, the system of this embodiment (hereinafter referred to as "this embodiment") is composed of a terminal 1 used by a user, a service providing server 2 owned by a business that provides an electronic signature service using electronic seals (hereinafter referred to as "service providing business"), a web server 3 and a management server 4 owned by a business that creates electronic seals (hereinafter referred to as "electronic seal creating business"), and a network 5 such as the Internet. The service providing server 2 is an example of a "providing side device", and the web server 3 and management server 4 are examples of a "creating side device".

The service provider is a party that provides companies, individuals, etc. with a function that allows a document to be electronically signed by stamping (affixing) an electronic seal to the document (also called an "electronic signature service"). The electronic seal creation business is a party that provides the service provider with a standard electronic seal that can be used in the electronic signature service. The electronic seal provided to the service provider is provided by the service provider to a user who uses the electronic signature service. In this embodiment, the user refers to an employee of the company when the electronic signature service is provided to a company, and to the individual when the electronic signature service is provided to an individual. A standard electronic seal is, for example, an actual seal that is composed of a seal surface (impression) that is treated as a so-called "ready-made product" and can be provided quickly. In addition, a user can directly order a desired electronic seal from an electronic seal creation business, and in this case, the electronic seal (impression image) created upon receipt of the order is provided directly to the user by the electronic seal creation business, and this can be used for electronic signatures. This flow is realized by the system shown in Figure 1.

[Device configuration]
Next, the terminal 1 used by the user will be described. In Fig. 1, one terminal 1 is shown as a terminal used by the user (also called a "user terminal"), but the number is not limited to one and can vary depending on the number of users, and in reality, multiple user terminals are usually present. Furthermore, the terminal 1 (user terminal) may be a terminal used solely by one user, or a terminal shared by multiple users (shared terminal).

The terminal 1 (user terminal) is a communication terminal such as a personal computer (PC), a smartphone, or a tablet. As shown in FIG. 1, the terminal 1 includes a processing unit 11, a storage unit 12, a communication unit 13, a display unit 14, and an operation unit 15. This configuration (hardware configuration) is a typical configuration that is provided in known communication terminals.

The processing unit 11 executes various processes for controlling the operation of the terminal 1, and is composed of a CPU (Central Processing Unit) and the like. The processing unit is also called the "control unit." The storage unit 12 stores the OS (Operating System) that operates the terminal 1, various application programs, and other data necessary for the operation of the terminal 1, and is composed of a ROM (Read Only Memory), which is a non-volatile memory, a RAM (Random Access Memory), which is a volatile memory, a hard disk drive (HDD), which is an auxiliary storage device, and the like. Applications (application software) include document creation software for creating electronic documents, document viewing software for viewing electronic documents, and web viewing software (web browser) for viewing web pages.

The communication unit 13 communicates data with the service providing server 2 and the Web server 3 via the network 5. The display unit 14 displays various information and is constituted by a liquid crystal display or the like. The operation unit 15 is operated by the user to input various instructions and is constituted by a keyboard, a mouse, or the like. The display unit 14 may be a touch panel that combines a display function (output function) and an input function. In this case, the buttons, icons, keyboard, etc. displayed on the display unit 14 function as the operation unit 15.

[Service provision server configuration]
Next, the service providing server 2 will be described. The service providing server 2 provides electronic signatures, electronic seals, and other associated services to users of terminals 1 connected to the server 2 via a network 5. The service providing server 2 can be configured as a cloud-type server or an on-premise-type server. Furthermore, there may be multiple service providing servers 2, or the service providing server 2 may be a so-called virtualized server.

As shown in FIG. 1, the service providing server 2 includes a processing unit 21, a memory unit 22, and a communication unit 26. As with the terminal 1, the processing unit 21 is configured with a CPU, etc., and the memory unit 22 is configured with a ROM, RAM, HDD, etc. The communication unit 26 also performs data communication with the terminal 1 and management server 4 connected to the server 2 via the network 5, and other devices that have access rights to the server 2.

Programs for executing electronic signatures using electronic seals and the like are installed in the service providing server 2 and stored in the storage unit 22. Specifically, as shown in FIG. 1, an electronic seal DB 23, an electronic seal program 24, and an electronic signature program 25 are stored.

The electronic seal DB23 is a database that manages the seal information (seal data) of standard electronic seals provided by electronic seal creation businesses. This electronic seal DB23 is an example of the "second management means" and the "standard management means."

In the electronic seal DB 23, for example, the seal surface information (seal surface data) is managed by the seal surface table shown in FIG. 2. As shown in the figure, the seal surface table stores data that sets the components of the seal surface, such as the seal surface characters, the number of characters, the typeface (font), the frame shape, the seal surface size, the color, the length and width (vertical or horizontal writing), whether or not to use subtitles, and whether or not to use line breaks.

Of the components of the seal, the seal characters are the characters that make up the seal of the electronic seal (in this embodiment, a name seal), for example a family name (kanji). The number of characters is the number of characters that make up the seal, for example up to 5 characters. The typeface (font) is the typeface of the characters that make up the seal, for example regular script or Ming style. The frame shape is the shape of the frame (seal frame) that makes up the seal, for example round (circle) or square (angle). The seal size is the size of the seal, for example large, medium, small, etc. The color is the color of the seal impression (display color), for example vermilion or red. The length and width are the direction of the characters that make up the seal, for example vertical writing (vertical) or horizontal writing (horizontal). With or without subtitles refers to whether or not to add a lowercase letter in parentheses to the characters that make up the seal (for example one character of the given name), and for example if there are many people of the same gender, you can select with subtitles. The option to have line breaks or not refers to whether the characters that make up the seal are displayed on separate lines; for example, you can select to have line breaks when there are a large number of characters. The vertical and horizontal orientation, whether or not to have subtitles, and whether or not to have line breaks are collectively referred to as the "seal layout." The data that defines each of these components is the seal information (seal data), and this seal information is stored in the seal table.

In this embodiment, multiple pieces of seal information (e.g., about 3,000) corresponding to common family names are stored in the seal table as seal information for a standard electronic seal (also called "standard seal information"). In this embodiment, the standard seal information is as follows: seal character "family name written in kanji", font "regular script", frame shape "round", seal size "medium", color "vermilion", and seal layout "vertical writing, no small marks, no line breaks" (see Figure 2). Each component that makes up the standard seal information is also called "standard seal character", "standard font", "standard shape", "standard size", "standard color", and "standard seal layout". In the seal table shown in Figure 2, the management number is a value assigned to each piece of seal information stored in the seal table.

Registration and updating of seal information in the electronic seal DB 23 (seal table) is performed by accessing the service providing server 2 from a terminal (not shown) such as a PC owned by the electronic seal creation company (hereinafter referred to as the "creation company terminal") or the management server 4.

The electronic seal program 24 is a program for selecting and setting (assigning to a user) an electronic seal for a user who uses an electronic signature service, generating an image of a seal impression, etc. The electronic signature program 25 is a program for stamping (affixing) the user's electronic seal to an electronic document displayed on the display unit 14 of the terminal 1, thereby applying an electronic signature to the document.

The processing unit 21 is capable of executing an electronic seal program 24 and an electronic signature program 25 based on instructions from the terminal 1. The memory unit 22 also stores various data required for the execution of the programs and for the implementation of functions by the programs.

[Web Server Configuration]
Next, the Web server 3 will be described. The Web server 3 is a server that operates a website (also called a "seal request site") for ordering an electronic seal. The Web server 3 (seal request site) is accessible by users of the above-mentioned electronic signature service, and a service is provided for users of terminals 1 connected to the server 3 via a network 5, where the user can place an order for an electronic seal (seal image) that the user desires. The Web server 3 can be configured as a cloud-type server or an on-premise-type server. Furthermore, there may be a plurality of Web servers 3, or the Web server 3 may be a so-called virtualized server.

As shown in FIG. 1, the Web server 3 includes a processing unit 31, a storage unit 32, and a communication unit 35. As with the terminal 1 and the service providing server 2, the processing unit 31 is configured with a CPU, etc., and the storage unit 32 is configured with a ROM, RAM, HDD, etc. The communication unit 35 also performs data communication with the terminal 1 connected to the server 3 via the network 5, and other devices that have access rights to the server 3.

The web server 3 has installed thereon a program for executing an order for an electronic seal through the seal request site, and the program is stored in the memory unit 32. Specifically, as shown in FIG. 1, a configuration file 33 and a seal request program 34 are stored. The configuration file 33 is various data that constitutes the pages (web pages) of the seal request site.

The seal request program 34 is a program (Web application program) for carrying out processes related to requests (orders) for the creation of electronic seals, such as displaying various pages (order screens, etc.) of the seal request site on the display unit 14 of the terminal 1 connected to the Web server 3 and sending the order information for an electronic seal entered on the site to the management server 4. The order information is information indicating the contents of the order, such as information about the seal of the electronic seal to be ordered (seal information), the name of the person placing the order (user) and information about the delivery address (shipping destination) of the created electronic seal (user information).

The processing unit 31 is capable of executing the stamp request program 34 based on instructions from the terminal 1. The memory unit 32 also stores various data required for the execution of the program and for the realization of functions by the program.

[Administration Server Configuration]
Next, the management server 4 will be described. The management server 4 is a server that manages information regarding electronic seals ordered through the above-mentioned seal request site. This management server 4 is connectable to each of the terminal 1, the service providing server 2, and the Web server 3 via the network 5. The management server 4 can be configured as a cloud-type server or an on-premise type server. Furthermore, there may be multiple management servers 4, or the management server 4 may be a so-called virtualized server.

As shown in FIG. 1, the management server 4 includes a processing unit 41, a memory unit 42, and a communication unit 47. As with the terminal 1 and the service providing server 2, the processing unit 41 is configured with a CPU, and the memory unit 42 is configured with a ROM, RAM, HDD, and the like. The communication unit 47 also performs data communication with the terminal 1, the service providing server 2, and the Web server 3 connected to the server 4 via the network 5, and other devices that have access rights to the server 4.

In the management server 4, programs for managing information on electronic seals ordered through the seal request site are installed and stored in the memory unit 42. Specifically, as shown in FIG. 1, an order management DB 43, an order management program 44, a seal management DB 45, and a seal management program 46 are stored. In addition, a creator's terminal (not shown) can be connected to the management server 4.

The order management DB43 is a database that manages order information for electronic seals that have been ordered through the seal request site. The order information is information for managing the process of the ordered electronic seal from its creation to its delivery (provision), such as the name of the orderer (user), the delivery address (such as the user's email address), the contents of the seal (seal information), and the creation status.

The order management program 44 is a program for carrying out processes related to the ordering of electronic seals, such as accepting orders for electronic seals from the impression request site and registering the order information of the accepted electronic seals in the order management DB 43. The processing unit 41 is capable of executing the order management program 44 based on receiving order information from the impression request site (Web server 3) and instructions from the creator terminal. The memory unit 42 also stores various data required for the execution of the program and for the realization of functions by the program.

Here, the electronic seal creation business can create an electronic seal based on the order information managed in the order management DB43. The electronic seal is created using a specified creation tool owned by the electronic seal creation business. The creation process is not directly related to the gist of the present invention, so a description of it will be omitted. The completed electronic seal (seal data) can be delivered as data to the orderer (orderer, user) via email, website, etc. This makes it possible to quickly provide an electronic seal (seal data) created in response to a user's order.

The seal impression management DB45 is a database that manages the seal impression information of electronic seals created in response to orders from users via the seal impression request site. This seal impression management DB45 is an example of the "first management means" and the "creation management means."

The seal impression management DB45 has a database structure (table structure) similar to that of the electronic seal DB23 described above, and the data of each component of the seal impression table shown in FIG. 2 is managed as seal impression information for a newly created electronic seal. In order to distinguish it from the seal impression table of the electronic seal DB23, the seal impression table of the electronic seal DB23 is also called the "standard seal impression table," and the seal impression table of the seal impression management DB45 is also called the "custom seal impression table."

The seal impression management program 46 is a program for performing processes related to the management of the seal impression information of a newly created electronic seal, such as registering the seal impression information of a newly created electronic seal in response to an order from a user in the seal impression management DB 45, and registering seal impression information that satisfies a specified criterion among the seal impression information managed in the seal impression management DB 45 (registered in the seal impression management DB 45) in the electronic seal DB 23 (service providing server 2). The specified criteria will be described later.

The processing unit 41 is capable of executing the stamp management program 46 based on receiving order information from the stamp request site (Web server 3) and instructions from the creator terminal. The memory unit 42 also stores various data required for the execution of the program and for the realization of functions by the program.

Here, the electronic seal creation business can register the impression information of the electronic seal created based on the order information managed in the order management DB 43, i.e., the impression information based on the order information entered at the impression request site, in the impression management DB 45 by operating the creation business terminal. Note that the registration of impression information in the impression management DB 45 can also be performed by the impression management program 46 without operating the creation business terminal. For example, based on the order information entered at the impression request site being received by the management server 4, the order information can be read by the processing of the impression management program 46, the impression information can be extracted from the read order information, and the impression information can be registered in the impression management DB 45 by the processing of the impression management program 46.

[Electronic Seal Setting Process]
Next, the electronic seal setting process (S100) executed by the processing unit 21 of the service providing server 2 in accordance with the electronic seal program 24 will be described with reference to the flowchart shown in Fig. 3. In this specification, "S" in S100 and the like ("S" in the flowchart) means a step.

When a user (such as a company employee) who uses the electronic signature service provided by the service providing server 2 sets up his or her own electronic seal to be used in an electronic signature, the user operates the terminal 1 that is communicatively connected to the service providing server 2 to send an instruction to execute a process related to setting up the electronic seal (e.g., an execution start command) to the service providing server 2. When the service providing server 2 receives the execution instruction, the processing unit 21 executes the electronic seal setting process (S100).

As shown in Figure 3, the electronic seal setting process (S100) first causes the display unit 14 of the terminal 1 that sent the execution instruction to display a setting screen (S101). An example of this setting screen is shown in Figure 6 (A). As shown in the figure, the setting screen 210 is composed of an input area 211 and a print face preview display area 212 arranged vertically.

The input area 211 has an input field 213 for inputting the characters to be printed on the seal (for example, a family name), an OK button 214 for confirming the input, and a designation button 215 for specifying print data prepared by the user. Kanji, hiragana, katakana, and the alphabet can be input into the input field 213. However, since the print characters in the standard print information in this embodiment are the family name written in kanji, if anything other than that is input, a bespoke order will be made (supported by a print request site), as described below.

The seal impression preview display area 212 is provided with a setting button 216 for setting (registering) the seal impression preview (imprint image) displayed in the area 212 as the user's electronic seal, and a custom order button 217 for custom ordering an electronic seal consisting of a seal impression other than the seal impression preview (imprint image) displayed in the area 212.

The user can operate the operation unit 15 of the terminal 1 to enter characters into the input field 213 on the setting screen 210, press (click) various buttons on the setting screen 210, etc., to perform data communication with the processing unit 21 (service providing server 2).

Next, in S103, it is determined whether character input into the input field 213 has been completed (S103). Here, it is determined whether the OK button 214 has been pressed (clicked) with characters entered into the input area 211, and whether a notification that character input has been completed has been sent from terminal 1. As a result, if it is determined that character input has been completed (YES in S103), the electronic seal DB 23 (seal table) is searched for seal information (seal data) of the electronic seal corresponding to the entered characters (S105). The characters entered into the input field 213 correspond to the seal characters in the seal table (see Figure 2).

As mentioned above, the electronic seal DB 23 stores and manages the seal information (standard seal information) of standard electronic seals provided by electronic seal creation businesses. In S105, a search is performed for seal information (seal information requested by the user) corresponding to the characters entered in the input field 213 from the electronic seal DB 23 (seal table) in which the standard seal information is stored.

If the search in S105 results in the extraction of the relevant seal information (standard seal information) (YES in S107), the extracted seal information is acquired (S108), and a seal preview (imprint image) based on the seal information is generated (S109), which is displayed in the seal preview display area 212 on the setting screen 210 (S111). For example, if the character entered in the input field 213 is the kanji character "Sato" and the corresponding standard seal information is extracted, an imprint image of "seal character: Sato", "font: regular script", "frame shape: round", "seal size: medium", "color: vermilion", and "seal layout: vertical writing, no small marks, no line breaks" is displayed. Note that the process in S108 is an example of "acquisition means", and the processes in S109 and S111 are examples of "display means".

Next, in S113, it is determined whether a setting instruction to set an electronic seal has been input (S113). Here, it is determined whether the setting button 216 has been pressed (clicked) while displayed in the imprint preview display area 212, and a setting instruction notification has been sent from terminal 1. As a result, if it is determined that a setting instruction has been input (YES in S113), the electronic seal based on the imprint preview displayed in the imprint preview display area 212 is set (registered) as the electronic seal of the user who input the setting instruction (S115), and this process ends. From this point on, the user can use the electronic seal set in S115 to sign an electronic signature.

The above is the process for setting an electronic seal based on the standard seal information managed in the electronic seal DB 23. On the other hand, if it is determined in the above-mentioned S103 that the character input has not been completed (NO in S103), it is determined whether an instruction to specify an electronic seal based on the seal data prepared by the user (also called an "instruction to specify a different seal") has been input (S117). Here, it is determined whether the designation button 215 has been pressed (clicked) and a notification of the instruction to specify a different seal has been sent from the terminal 1. As a result, if it is determined that an instruction to specify a different seal has not been input (NO in S117), the process returns to S103, and if it is determined that an instruction to specify a different seal has been input (YES in S117), a seal data selection screen (not shown) for selecting seal data is displayed on the display unit 14 of the terminal 1 that sent the instruction to specify a different seal (S119).

The print data selection screen can be configured, for example, as a file selection dialog box displayed in front of the setting screen 210. The user operates the operation unit 15 of the terminal 1 to select the print data prepared by the user from the print data selection screen displayed on the display unit 14. The print data prepared by the user can be stored in advance, for example, in the memory unit 12 of the terminal 1.

Next, in S121, it is determined whether the selection of the seal data on the seal data selection screen has been completed (S121). Here, for example, a predetermined seal data file is selected on the seal data selection screen and an open button or the like (not shown) is pressed (clicked), and it is determined whether a notification that the selection of the seal data has been completed has been sent from the terminal 1. As a result, if it is determined that the selection of the seal data has not been completed (NO in S121), it waits as it is, and if it is determined that it has been completed (YES in S121), it generates a seal preview (imprint image) based on the selected seal data (S109) and displays it in the seal preview display area 212 on the setting screen 210 (S111). After this, when the setting button 216 on the setting screen 210 is pressed (clicked) and a setting instruction is input (YES in S113), the electronic seal based on the seal preview displayed in the seal preview display area 212, that is, the electronic seal based on the seal data prepared by the user himself, is set (registered) (S115).

In addition, if the result of the seal information search in S105 described above is that the corresponding seal information (standard seal information) is not extracted (NO in S107), for example, if the characters (family name) entered in the input field 213 are not standard, a message indicating that the corresponding seal information (standard seal information) does not exist is displayed in the seal preview display area 212 (S123). Next, it is determined whether an instruction to order an electronic seal (also called a "custom order instruction") has been entered (S125). Here, it is determined whether the custom order button 217 has been pressed (clicked) and a notification of a custom order instruction has been sent from the terminal 1. As a result, if it is determined that a custom order instruction has not been entered (NO in S125), it waits as it is, and if it is determined that a custom order instruction has been entered (YES in S125), it sends a connection request to the seal request site to the Web server 3 (S127), and this process ends. The process of S127 connects the terminal 1 to the seal request site.

Also, if it is determined in S113 described above that no setting instructions have been input (NO in S113), it is determined whether or not a custom instruction has been input, as in S125 (S129). This is to accommodate cases where, although it is possible to set (use) an electronic seal based on the standard seal information managed in the electronic seal DB 23, the user wishes to set (use) their own electronic seal. Then, if it is determined in S129 that a custom instruction has been input (YES in S129), a connection request to the seal request site is sent to the Web server 3 (S131), and this process ends. The process of S131 connects the terminal 1 to the seal request site.

[Seal request processing]
Next, the stamp request process (S200) executed by the processing unit 31 of the Web server 3 in accordance with the stamp request program 34 will be described with reference to the flowchart shown in FIG.

When the Web server 3 receives a connection request sent from the service providing server 2 by the processing of S127 or S131 described above, the processing unit 31 connects the terminal 1 and the impression request site so that they can communicate with each other, and executes the impression request processing (S200).

As shown in FIG. 4, in the stamp request process (S200), first, the display unit 14 of the terminal 1 connected to the stamp request site displays a stamp content input screen (S201). An example of the input screen is shown in FIG. 6 (B). As shown in the figure, the stamp content input screen 310 has a character input field 311 for inputting the stamp characters (e.g., family name), a typeface field 312 for selecting and inputting a typeface (font), a shape field 313 for selecting and inputting the shape of the stamp frame, a size field 314 for selecting and inputting the stamp size, a color field 315 for selecting and inputting the color of the seal impression, a layout field 316 for selecting and inputting the seal layout, and a preview button 317 for displaying a stamp preview (seal image) based on the contents entered in each field. These fields correspond to the elements (components of the stamp) that make up the stamp information (seal data) managed in the stamp management DB 45 (seal table) (see FIG. 2).

The character input field 311 allows the input of kanji, hiragana, katakana, and the alphabet.

The font field 312, shape field 313, size field 314, color field 315 and layout field 316 all allow data to be entered using drop-down lists.

In the font field 312, Kaisho, Reisho, Koin, Ming, Kakugo, Marugo, and Tensho are displayed in a drop-down list as selectable fonts, and the user can select and input one of them. In this embodiment, fonts other than Kaisho are non-standard fonts.

In the shape field 313, a drop-down list of selectable shapes displays circle and square, and you can select and enter one of them. In this embodiment, square is a non-standard shape.

In the size field 314, large, medium, and small are displayed as selectable sizes in a drop-down list, and one of these can be selected and entered. In this embodiment, large and small are non-standard sizes.

In the color field 315, vermilion, red, black, indigo, purple, and green are displayed in a drop-down list as selectable colors, and one can be selected and entered. In this embodiment, colors other than vermilion are non-standard colors.

In the layout field 316, "vertical writing, no subtitles, no line breaks", "vertical writing, with subtitles, no line breaks", "vertical writing, without subtitles, with line breaks", "vertical writing, with subtitles, with line breaks", "horizontal writing, no subtitles, no line breaks", "horizontal writing, with subtitles, no line breaks", "horizontal writing, without subtitles, with line breaks" and "horizontal writing, with subtitles, with line breaks" are displayed in a drop-down list as selectable print layouts, and one can be selected and entered. In this embodiment, print layouts other than "vertical writing, no subtitles, no line breaks" are non-standard print layouts.

The user can operate the operation unit 15 of the terminal 1 to enter the desired print content into each field 311 to 316 on the print content input screen 310, or press (click) the preview button 317, thereby communicating data with the processing unit 31 (Web server 3).

Next, in S203, it is determined whether an instruction to display a seal preview (imprint image) has been input (S203). Here, it is determined whether the preview button 317 has been pressed (clicked) after input into each of the fields 311 to 316 on the seal content input screen 310 has been completed, and whether a display instruction notification has been sent from terminal 1. As a result, if it is determined that a display instruction has not been input (NO in S203), the process waits as is, and if it is determined that a display instruction has been input (YES in S203), a seal preview (imprint image) based on the input contents into each of the fields 311 to 316 is generated, and a preview display screen (not shown) for displaying this is displayed on the display unit 14 (S205). Through this preview display screen, the user can check the seal contents of the desired electronic seal.

Next, in S207, it is determined whether an instruction to confirm the contents of the seal impression of the electronic seal to be ordered has been input based on the contents of the seal impression preview (imprint image) displayed on the preview display screen (S207). Here, it is determined whether a Confirm button (not shown) on the preview display screen has been pressed (clicked) and a notification of the instruction to confirm the seal impression has been sent from terminal 1.

If it is determined in S207 that an instruction to confirm the print face has not been input (NO in S207), it is determined whether an editing instruction has been input to make changes or corrections to the print face preview displayed on the preview display screen (S215). Here, it is determined whether an edit button (not shown) on the preview display screen has been pressed (clicked) and a notification of an editing instruction has been sent from terminal 1.

If it is determined in S215 that an editing instruction has not been input (NO in S215), the process returns to S207. If it is determined that an editing instruction has been input, an editing screen (not shown) is displayed on the display unit 14 (S217). This editing screen is a screen that allows various editing (imprint editing) such as modifying the imprint character or font, adding handwritten characters or figures, or changing the thickness of the lines that make up the imprint character or imprint frame by operating the operation unit 15 for the imprint preview displayed on the preview display screen (imprint editing means). This allows the user to create an original imprint (imprint image). Note that it is also possible to input editing instructions from the imprint content input screen 310, and to display the editing screen on the display unit 14.

Next, in S219, it is determined whether an end editing instruction to end editing on the editing screen has been input (S219). Here, it is determined whether an end button (not shown) on the preview display screen has been pressed (clicked) and a notification of an end editing instruction has been sent from terminal 1.

If it is determined in S219 that an instruction to end editing has not been input (NO in S219), the process waits as is, and if it is determined that an instruction to end editing has been input (YES in S219), the process returns to S207.

If it is determined in S207 that an instruction to confirm the seal has been input (YES in S207), a user information input screen (not shown) is displayed on the display unit 14 (S209). The user information input screen is a screen for inputting information about the user ordering the electronic seal, such as the orderer's name, contact information, and shipping (delivery) address. Based on the user information input on the user information input screen, the completed electronic seal (seal data) is delivered to the user (orderer).

The user information input screen also inputs information indicating whether or not the seal data (seal information) of the electronic seal to be ordered is permitted to be used by others (third parties) (also referred to as "usability information"). The usability information is input, for example, using a check box (not shown) provided on the user information input screen; checking the box indicates permission to use, and not checking the box indicates prohibition of use (unavailable). Information indicating permission to use is also referred to as "usability information," and information indicating prohibition of use (unavailable) is also referred to as "prohibition of use information." Since it is believed that some users who order electronic seals through the seal request site will wish to use an original seal, in this embodiment the usability information is provided as an input item. However, it is not necessary to provide the usability information.

Next, in S211, it is determined whether an order instruction for an electronic seal has been input (S211). Here, it is determined whether an order button (not shown) on the user information input screen has been pressed (clicked) and a notification of an order instruction has been sent from terminal 1. As a result, if it is determined that an order instruction has not been input (NO in S211), the process waits as is, and if it is determined that an order instruction has been input (YES in S211), the process transmits order information including the seal content (seal information) confirmed by the process of S207 described above, the user information entered on the user information input screen, and usability information to management server 4 (S213), and then this process ends.

The print content input screen 310 and the user information input screen displayed on the display unit 14 of the terminal 1 connected to the print request site are examples of "order screens", and the processes of S201 and S209 for displaying these input screens (order screens) on the display unit 14 are examples of "order screen display means".

The order information sent to the management server 4 by the processing of S213 is managed as order information in the order management DB 43. The order information (order information) can be registered in the order management DB 43 by a person in charge of the electronic seal creation company operating the creation company terminal. Alternatively, it can be performed by the order management program 44 without operating the creation company terminal. For example, based on the order information received by the management server 4 from the web server 3, the order information can be read by the processing of the order management program 44, and the read order information can be registered as order information in the order management DB 43 by the processing of the order management program 44.

Furthermore, the seal information (custom-made seal information) based on the order information sent to the management server 4 by the processing of S213 is registered and managed in the seal management DB 45 as described above. However, if the usability information entered on the user information input screen is use prohibition information indicating that use by others is prohibited (not permitted), the seal information based on the order information including the use prohibition information is not registered in the seal management DB 45. And, custom-made seal information that is not registered in the seal management DB 45 is not subject to the processing of 307 described below, i.e., is not subject to registration in the electronic seal DB 23 (service providing server 2). This makes it possible to prohibit (avoid) the use of the seal information by others (setting of the electronic seal by S115 described above) (use prohibition means).

[Print information management processing]
Next, the print face information management process (S300) executed by the processing unit 41 of the management server 4 in accordance with the print face management program 46 will be described with reference to the flowchart shown in FIG.

When the print information based on the order information is newly registered in the print management DB 45, the processing unit 41 executes the print information management process (S300) based on the information. The processing unit 41 may also execute the print information management process (S300) based on an instruction from a creator terminal connected to the management server 4.

As shown in FIG. 5, the seal information management process (S300) first determines whether custom-made seal information (non-standard seal information) managed in the seal management DB 45 satisfies the conditions (also called "registration conditions") for registration in the electronic seal DB 23 (service providing server 2) (S301). Specifically, the seal information stored in the seal table (custom seal table) of the seal management DB 45 is analyzed to determine whether there is seal information that satisfies the registration conditions. The process of S301 is an example of a "determination means".

The seal management program 46 incorporates a control (judgment program) that judges whether or not there is seal information that satisfies the registration conditions, and judges the seal information accordingly. The registration conditions are preprogrammed, and include, for example, a predetermined number (e.g., 3 or more) of seal information whose seal characters are identical or similar to each other, or a predetermined number (e.g., 3 or more) of seal information whose seal characters are identical or similar to each other and at least one of the font, size, color, and seal layout is non-standard but identical. The seal characters being identical or similar means that they are identical or similar based on the appearance (appearance) of the characters, and for example, the program can calculate the similarity of the character strings that make up the seal characters to judge their similarity (including identity). The predetermined number defined as the registration condition means the number of times an electronic seal is ordered through the seal request site. The registration condition is an example of a "predetermined criterion."

Note that the registration conditions are not limited to this, and other conditions may include, for example, that there is a predetermined number (e.g., 100 or more) of the same non-standard typeface (e.g., "clerical script"), or that there is a predetermined number (e.g., 100 or more) of the same non-standard color (e.g., "red"). In addition, it can be said that one of the registration conditions is that the aforementioned usability information is usage permission information indicating that use by others is permitted.

If the result of the determination in S301 is that there is no seal information that satisfies the registration conditions (NO in S303), that is, if there is no seal information to be registered that can be registered in the electronic seal DB 23 (service providing server 2), this process ends without performing the processes from S305 onwards.

On the other hand, if there is seal impression information that satisfies the registration conditions (YES in S303), that is, if there is seal impression information to be registered that may be registered in the electronic seal DB 23 (service providing server 2), that seal impression information is acquired (S305). The acquired seal impression information is then transferred to the service providing server 2 and registered in the electronic seal DB 23 (stored in the standard seal impression table) (S307), and this process ends. The process of S307 is an example of a "registration means".

When the seal information to be registered is registered in the electronic seal DB 23 (S307), the seal information to be registered that was previously managed in the seal management DB 45 may be deleted from the seal management DB 45 (custom seal table), or may be left in the seal management DB 45 without being deleted. If it is deleted, it is possible to prevent a capacity shortage in the seal management DB 45 (storage unit 42), and if it is left, it becomes easier for subsequent custom-made seal information that is similar to the seal information that was previously registered to be registered in the electronic seal DB 23.

An example of the seal impression information to be registered is shown in FIG. 7. FIG. 7(A) shows an example in which the registration condition is that there are three or more pieces of seal impression information with the same seal impression character and the same font in a non-standard font. In this example, as a result of the seal impression information determination by S301, seal impression information A1 to A3 with the seal impression character "Sato" and the font "clerical script" is extracted. This means that "clerical script" has been ordered a total of three times for the seal impression character "Sato". In this case, since it is expected that there will be a demand for "clerical script" for the seal impression character "Sato", seal impression information A1 to A3 are acquired as registration targets and registered in the electronic seal DB 23. As a result, seal impression information A1 to A3 are managed in the electronic seal DB 23 as being of the same type as standard seal impression information.

In this way, when the seal information A1 to A3 are registered in the electronic seal DB 23, when the user sets his/her own electronic seal to be used for electronic signature on the terminal 1 connected to the service providing server 2, if the character "Sato" is entered in the input field 213 of the setting screen 210 displayed by S101 of the electronic seal processing (S100), in addition to the seal preview based on the standard seal information, a seal preview based on the seal information A1 to A3 is displayed in the seal preview display area 212 of the setting screen 210 (S111), and it becomes possible to select one of these four seal previews on the setting screen. Then, it becomes possible to set the electronic seal based on the selected seal preview as the electronic seal to be used for electronic signature (S115). In this case, the number of types of electronic seals that the user can select increases, and the range of choices becomes wider, compared to when only the seal preview based on the standard seal information is displayed (default).

Of the seal impression information A1 to A3, the seal impression information A1 may be registered in the electronic seal DB 23, while the seal impression information A2 and A3 may not be registered. The seal impression information A1 is the same as the standard seal impression information except for the font, whereas the seal impression information A2 and A3 are both non-standard in color (red), and furthermore the frame shape and seal impression size of the seal impression information A3 are non-standard (square) and non-standard (large), respectively, so that the difference between the seal impression information A2 and the standard seal impression information is greater than that of the seal impression information A1, and the demand for the seal impression information A3 is considered to be low. Such criteria for whether or not to register can be determined appropriately according to the registration conditions.

Figure 7 (B) shows an example of a case where the registration condition is that there are three or more pieces of seal information with similar seal characters and the same non-standard font. In this example, as a result of the seal information determination by S301, seal information B1 with seal characters "Suzuki" (standard seal characters) and the font "rounded gothic" and seal information B2 and B3 with seal characters "Suzuki" (non-standard seal characters) and the font "rounded gothic" are extracted. This means that "rounded gothic" has been ordered a total of three times for "Suzuki" and "Suzuki", whose seal characters are similar to each other. In this case, since it is expected that there will be a need for "rounded gothic" for the seal characters "Suzuki" and "Suzuki", which are similar to each other, seal information B1 and B2 (or B3) are obtained as registration targets and registered in the electronic seal DB23. As a result, the seal information B1 and B2 (or B3) will be managed in the electronic seal DB23 as something similar to the standard seal information.

In this way, when the seal information B1 and B2 (or B3) are registered in the electronic seal DB 23, when the user sets his/her own electronic seal to be used for electronic signature on the terminal 1 connected to the service providing server 2, if the character "Suzuki" is entered in the input field 213 of the setting screen 210 displayed by S101 of the electronic seal processing (S100), in addition to the seal preview based on the standard seal information, a seal preview based on the seal information B1 is displayed in the seal preview display area 212 of the setting screen 210 (S111), and it becomes possible to select one of these two seal previews on the setting screen. Also, if the character "Suzumoto" is entered in the input field 213 of the setting screen 210, a seal preview based on the seal information B2 (or B3) is displayed in the seal preview display area 212 of the setting screen 210 (S111), and it becomes possible to set the electronic seal based on the seal preview as the electronic seal to be used for electronic signature (S115). Even in this case, the number of types of electronic seals that users can select increases, providing a wider range of choices compared to when only a preview of the seal based on standard seal information is displayed (default).

In this example, one of the seal impression information B2 and B3 is registered in the electronic seal DB 23 because the contents of both pieces of seal impression information are identical. For example, if seal impression information B2 and seal impression information B3 differ in at least one of the frame shape, size, color, and seal impression layout, both pieces of seal impression information may be registered in the electronic seal DB 23, or only the seal impression information that differs little from the standard seal impression information may be registered in the electronic seal DB 23. Such criteria for whether or not to register can be determined appropriately based on the registration conditions.

[Effects of this embodiment]
According to the above-described system and the method for managing seal information of the present embodiment, with regard to an electronic seal newly created in response to an order from a user who uses a service (electronic signature service) provided by a service provider, among the seal information of the electronic seal managed in the seal management DB 45 (management server 4) on the electronic seal creation business side, the seal information that satisfies the registration conditions in the electronic seal DB 23 (service providing server 2) on the service provider side is managed in the electronic seal DB 23 as the same type as the standard seal information. Therefore, it is possible to increase the types of electronic seals managed as standard electronic seals in the electronic seal DB 23 (service providing server 2) in a limited manner. This makes it possible to appropriately increase the options when a user selects an electronic seal to be used, making it easier for the user to select the seal he or she desires, and improving convenience. In addition, since only the seal information that satisfies the registration conditions among the seal information managed in the seal management DB 45 is registered in the electronic seal DB 23, it is also possible to avoid unnecessary registration in the electronic seal DB 23.

In addition, the seal information is managed in the seal management DB 45 based on the order information entered through the seal content input screen displayed on the terminal 1. This allows for efficient management of the seal information of electronic seals created in response to user orders. It also makes it easier to receive new orders for electronic seals from users, preventing missed orders.

In addition, the seal information of electronic seals created in response to orders from users (based on order information entered through the seal content input screen) is managed by the management server 4 (the server of the electronic seal creation company), and among them, seal information that satisfies the registration conditions is transferred to the service provision server 2 (the server of the service provider) and registered in the electronic seal DB 23. This enables efficient management and provision of seal information.

The seal impression management program 46 executed by the management server 4 also incorporates a control (determination program) that determines whether or not there is seal impression information that satisfies the registration conditions, and the seal impression information is determined accordingly. This makes it possible to appropriately extract seal impression information (seal impression information of a newly created electronic seal) to be registered in the electronic seal impression DB 23 (service providing server 2) from the seal impression information (seal impression information that is similar to the standard seal impression information) managed in the seal impression management DB 45 (management server 4).

In addition, while the seal information of a newly created electronic seal is managed in the seal management DB 45 (management server 4), seal information that meets the registration conditions is registered and managed in the electronic seal DB 23 on the service provider's side, making it possible to provide users with electronic seals to be used in the service (electronic signature service) provided by the service provider as quickly as possible.

The above describes an example of the application of the present invention to a system for providing electronic seals as an embodiment of the present invention, but the present invention can also be applied to physical seals such as rubber stamps, hard stamps, and ink-impregnated stamps in addition to electronic seals. Also, in the above embodiment, the type (impression type) of the electronic seal was a name stamp, but the present invention can be applied to any impression type of seal (including electronic seals) regardless of type, such as data stamps, company stamps, contract stamps, business stamps, commemorative stamps, and store stamps.

In addition, in the above embodiment, the conditions (criteria) for registering seal information from the seal management DB 45 (management server 4) to the electronic seal DB 23 (service provision server 2) are exemplified as conditions (criteria) based on the similarity of the appearance (appearance) of the seal characters. However, it is also possible to configure the registration conditions to be based on the similarity of the reading (pronunciation) of the seal characters or the similarity of elements other than the characters that make up the seal (for example, figures included in the seal, seal layout, etc.), and to calculate the similarity using a program to determine similarity (including identity). This makes it possible to increase the types of seal information that can be handled and broaden the scope of seal information management.

In the above embodiment, the registration conditions include a number (predetermined number) equivalent to the number of orders for electronic seals through the seal request site, and the number of extracted seal information (see, for example, FIG. 7) based on the determination of the seal information by S301 (the number of hits) is considered to be the number of orders. However, the program on the management server 4 side may count the number of orders and use this as a criterion for determining the registration conditions. For example, a table for managing information on the seal characters (for example, family names) and fonts may be provided in the seal management DB 45, and the number of orders for each type of non-standard font may be counted for each seal character, and whether or not the registration conditions are met may be determined based on the counted value. In this case, for example, for the seal character "Sato", the number of orders for each type of non-standard font, such as the number of orders for the clerical script, the number of orders for the old seal script, and the number of orders for the rounded gothic font, may be counted, and the typefaces that have been ordered a predetermined number of times (for example, 3 or more) may be determined to meet the registration conditions. This also makes it easier for users to select the electronic seal they desire while avoiding unnecessary registration in the electronic seal DB 23. This also applies to the case where the number of orders is counted for each type of seal component other than the font (seal character, frame shape, size, color, seal layout, etc.).

As a further registration condition, it may be possible to determine whether the seal surface components such as the characters and figures that make up the seal surface contain anything that is contrary to public order and morals (for example, characters that are generally not suitable for use in a name), and if such characters are included, it may be determined that the registration condition is not met, and if they are not, it may be determined that the registration condition is met. In this case, even if the conditions regarding the similarity of the appearance (look) and reading (pronunciation) of the seal surface characters are met, if the conditions regarding public order and morals are not met, the seal surface information may not be registered in the electronic seal DB 23. This also makes it possible to appropriately extract the seal surface information to be registered in the electronic seal DB 23.

In addition, in the above-described embodiment, when ordering an electronic seal through the seal request site, usability information is entered on the user information input screen (S207), and if that usability information is entered as prohibited use information, the seal information based on the order information including the prohibited use information is not registered in the seal management DB45. In contrast, the seal information may be registered in the seal management DB45 together with the usability information, and seal information corresponding to prohibited use information may be determined not to satisfy the registration conditions in S301 of the seal information management process (S300). This also makes it possible to prohibit the use of the seal information by others (prohibition means).

In addition, in the above-mentioned embodiment, when setting (registering) an electronic seal to be used in an electronic signature, the user can set an electronic seal using the seal data prepared by the user himself (including the seal data of an electronic seal ordered through a seal request site) (see S117 to S121). In this case, it is considered that there are users who do not want others to use the seal data because the seal data is highly unique. Therefore, for example, when a seal data file is selected on the seal data selection screen displayed based on a separate specification instruction (S117) (S119, S121), a screen for inputting usability information regarding the seal information (seal data) included in the seal data file may be displayed on the display unit of the user terminal, so that permission or prohibition of use by others can be set (selected). In this case, the seal information and usability information may be managed (registered in the electronic seal DB 23) as a set, and the seal information corresponding to the use prohibition information may not be extracted (hit) in the seal information search in S105. In this way, for example, even if a user with the same surname as the user who set up the electronic seal using seal data that he or she prepared (also called the "original user") enters his or her surname into input field 213 on setting screen 210, the seal information corresponding to the original user's electronic seal will not be extracted, making it possible to prohibit others from using the seal information.

In addition, in the above-described embodiment, there is a service provider that provides an electronic signature service and an electronic seal creation company that creates electronic seals to be used with the electronic signatures, and the service provider's server (service provision server 2) is provided with an electronic seal DB 23 (standard seal face table, standard seal face management DB) and the electronic seal creation company's server (management server 4) is provided with a seal face management DB 45 (custom seal face table, custom seal face management DB), but the electronic seal DB 23 and the seal face management DB 45 may be provided on the same server. In this case, the same server may be either the service provider's server or the electronic seal creation company's server, or it may be a server jointly owned by both parties.

In addition, in the above embodiment, one management server 4 is provided with an order management DB 43 and an order management program 44, and a seal impression management DB 45 and a seal impression management program 46, and the management of order information regarding ordered electronic seals and the management of seal impression information for created electronic seals are performed by the one management server 4, but the management of order information and the management of seal impression information may be performed by separate servers. That is, a server provided with the order management DB 43 and the order management program 44, and a server provided with the seal impression management DB 45 and the seal impression management program 46 may be provided.

In addition, in the above embodiment, the service provided by the service provider is an electronic signature service, but the service provided may be a service other than an electronic signature service, and the content of the service may be anything, such as a workflow service using an electronic seal. In addition, when the present invention is applied to a physical seal, the service provider and electronic seal creation business in the above embodiment may be, for example, a seal sales business and a seal manufacturing business.

1 terminal, 2 service providing server, 3 web server, 4 management server, 5 network, 11 processing unit, 12 memory unit, 13 communication unit, 14 display unit, 15 operation unit, 21 processing unit, 22 memory unit, 23 electronic seal DB, 24 electronic seal program, 25 electronic signature program, 26 communication unit, 31 processing unit, 32 memory unit, 33 configuration file, 34 seal request program, 35 communication unit, 41 processing unit, 42 memory unit, 43 order management DB, 44 order management program, 45 seal management DB, 46 seal management program, 47 communication unit.

Claims (2)

A system for providing a seal to a user, comprising:
A first management means for managing information on a seal impression created based on the seal impression content input by a user;
A determination means for determining whether or not the print information managed by the first management means satisfies a predetermined standard;
A second management means for managing stamp face information of a standard seal;
A registration means for registering the seal information determined by the determination means to satisfy the predetermined standard in the second management means ,
When the seal information determined to satisfy the predetermined criteria is registered in the second management means, the registered seal information is managed as a similar type to the seal information of the standard seal,
A seal created based on the seal face information managed by the second management means can be provided in response to a request from a user.
A seal providing system. A providing device that provides a seal to a user;
A seal creating device is provided.
the provider device includes the second management means,
the production side device includes the first management means, the determination means, and the registration means,
the providing device and the creating device are communicatively connected via a network;
The registration means transfers the seal information determined to satisfy the predetermined criteria to the providing side device and registers it in the second management means.
The seal providing system according to claim 1 .

Images