KR20220158643A - Korean syllable character input method and device on screen keyboard - Google Patents

Abstract

Proposed is a technology that can simultaneously process input of modern Korean language and Korean archaic language. Moreover, proposed is the technology that can input numbers and English alphabets in a Korean language mode. In the present invention, a consonant is recognized in response to the pressing of the consonant button, and a vowel is recognized in response to the pressing of the vowel button.

Description

Korean syllable character input method and device on screen keyboard{.}

The present invention relates to an alphabetic input device and method in a keypad, and more particularly to an alphabetic input device and method in a keypad having a small number of keys such as a telephone keyboard.

.

With the development of mobile communication, a function for transmitting and receiving digital information such as text has been added to a portable terminal focused on voice communication. Therefore, initially, the keypad provided in the portable terminal for the purpose of inputting a phone number also includes a means for inputting text. However, since the size of a keypad used as an input means of a portable terminal is getting smaller, the number of buttons included in the keypad has its limit. On the other hand, the alphabet of each language greatly exceeds the number of 12 keys included in the keypad. Therefore, in order to input one alphabet using the phone keypad, the alphabet must be expressed by combining one or two or more buttons on the keypad.

.

A technology that can simultaneously process modern Korean and Korean archaic input is presented. In addition, a technology that can input numbers and English alphabets in Korean mode is presented.

Figure 1-1. An example of configuring a standard keypad using the standard English keypad
Figure 1-2. When assigning about 3 alphabets to each button, the central alphabet is set as the representative alphabet, and the alphabets arranged on the left and right are successive alphabets.
Figure 1-3. An example of configuring a standard keypad when assigning 3 to 4 alphabets to each button
Figure 2-1. An example of configuring a Japanese follow-up keypad (1)
Figure 2-2. An example of configuring a Japanese follow-up keypad (2)
Figure 2-3. Graph of 2D recycling control processing method
Figure 2-4. Graph of two-dimensional crossing control processing method
Figure 3-1. An example of configuring a follow-up keypad (Arabic)
Figure 3-2. An example of configuring a follow-up keypad (Arabic, using 2 control buttons)
Figure 3-3. When assigning about 3 alphabets to each button, the central alphabet is set as the representative alphabet, and the alphabets arranged on the left and right are successive alphabets.
Figure 4-1. Example 1 of assigning basic consonants and basic vowels to each button in pairs (Korean)
Figure 4-2. Example 2 of assigning basic consonants and basic vowels to each button in pairs (Korean)
Figure 4-3. Example 3 of assigning basic consonants and basic vowels to each button in pairs (Korean)
Figure 4-4. Flowchart of inputting basic consonants and basic vowels by repeated selection method (example of Korean language)
Figure 4-5. Example of applying three collection elements
Figure 4-6. Examples of solving and expressing Figures 4-5 from the viewpoint of applying the repetitive selection method using four vowel elements
Figure 4-7. Example of assigning 4 collection elements to 4 buttons
Figure 4-8. Examples of solving and expressing Figs. 4-7 from the viewpoint of applying the iterative selection method
Figure 4-9. Deformation display example of Fig. 4-5
Figure 4-10. Examples of modern Korean vowels "ㅡ", "ㄴ", and "ㅣ"
Figure 4-11. Example of deformation display in Fig. 6
Figure 4-12. Deformation display example of Fig. 4-10 ("+" type)
Figure 4-13. Deformation display example of Fig. 4-10 ("-A" type)
Figure 4-14. Example of deformation display in Fig. 4-10 ("H" type)
Figure 4-15. Deformation display example of Fig. 4-10 ("A" type)
Figure 4-16. Example of transforming 4 rows of buttons into 1 row on a 3*4 keypad (1)
Figure 4-17. Example of transforming 4 rows of buttons into 1 row in a 3*4 keypad (2)
Figure 4-18. Examples using modern Korean vowels "ㅡ", "ㄴ", "sh", "ㅣ"
Figure 4-19. Deformation display example of Fig. 4-12
Figure 4-20. A case of combining vowels using modern Korean vowels "ㅡ", "ㄴ", "ㅣ" (graph)
Figure 4-21. A case of combining vowels using modern Korean vowels "ㅡ", "ㄴ", and "ㅣ" (Graph 2)
Figure 4-22. Flow chart of keypad Korean input processing
Figure 4-23. 2 Flow chart of Korean input processing in the beolsik keyboard
Figure 4-24. Flowchart of keypad Korean input processing (when applying the repeated selection method to consonant input)
Figure 4-25. Flow chart of keypad Korean input processing (when a specific button combination is applied to consonant input)
Figure 4-26. Flow chart of keypad Korean input process (general)
Figure 4-27. Flow chart of keypad Korean input processing (added when the character completion button is applied)
Figure 5-1. Chinese character input using Pinyin dictionary and Pinyin
Figure 5-2. Example of text input in English using a premise-associated simple code
Figure 5-3. Case of processing input value as promised simple code in parallel input method (1)
Figure 5-4. Case of processing input value as promised simple code in parallel input method (2)
Figure 5-5. Examples of application of parallel input method through client and server
Figure 5-6. Grouping examples of phrases (words or phrases) stored in the index
Figure 6-1. Case in which the server (intermediary server) interprets the simple code received from the client and transmits the information obtained by interpreting the simple code to a third server that requires the information
Figure 7-1. An example of a subsequent keypad that can input various symbols by the control processing method (English keypad)
Figure 7-2. An example of a follow-up keypad that can input various symbols by the control processing method (Korean keypad)
Figure 8-1. Example of a conventional mobile phone in which various function buttons are placed above the 3*4 numeric keypad
Figure 8-2. Case 1 where various function buttons are placed under the 3*4 numeric keypad
Figure 8-3. Case 2 where various function buttons are placed under the 3*4 numeric keypad
Figure 8-4. Example of arranging various function buttons on the left/right side of the 3*4 numeric keypad
Figure 8-5. Example of using various function buttons as control buttons 1
Figure 8-6. Case 2 of using various function buttons as control buttons
Figure 8-7. Case 3 of using various function buttons as control buttons
Figure 8-8. Case 4 of using various function buttons as control buttons
Figure 9-1. Example of displaying the function corresponding to each button as an icon when using the up, down, left, and right movement buttons as addition, subtraction, increase, and subtraction buttons
Figure 9-2. A case in which symbols related to each number button are iconified and displayed on a liquid crystal
Figures 10-1 to 10-4. Case of Consonant Separation Keypad in a Language Using the Roman Alphabet
Figure 10-5. Examples of shortened input method in consonant separation keypad and case of processing input value as promised simple code in parallel input method
Figure 10-6. Example of consonant separation keypad in a language using the Roman alphabet (5)
Figure 10-7. Flowchart of applying the language restriction input method in the consonant separation keypad (1)
Figure 10-8. Flowchart of applying the language restriction input method in the consonant separation keypad (2)
Figure 10-9. Flow chart of applying language restriction input method in incomplete consonant separation keypad
Figure 10-10. (In a system with all words) Parallel input method application case (1)
Figures 10-11. (In a system with all words) Parallel input method application case (2)
Figures 10-12. (In a system equipped with all words) Parallel input method application flow chart (1)
Figures 10-13. (In a system equipped with all words) Language restriction parallel input method application flow chart (2)
Figures 10-14. Application of full code input method (and parallel input method) in the system
Figures 10-15. Example of application of parallel input method in a system equipped with an index of phrases (words or phrases) consisting only of representative alphabets (1)
Figures 10-16. Application case of the parallel input method in a system equipped with an index of phrases (words or phrases) consisting only of representative alphabets (2)
Figures 10-17. Example of processing recommendation sound input as a primary simple code (shortened input value)
Figure 11-1. Example of system configuration diagram when input values are interpreted on the client side
Figure 11-2. Example of system configuration diagram when input values are analyzed on the server side
Fig. 11-3 ~ 11-10. Examples of processing simple codes (in the parallel input method)
Figures 11-11. Examples of simplecode (i.e., shortcode or shortcode) type
Figure 12-1. Example of inputting function by control processing method
Figure 12-2. Example of displaying controls assigned to each button on the LCD screen
Figure 13-1 ~ 13-4. Example of processing part of input value as full code and other part as simple code
Figure 14-1 ~ 14-2. Example of control processing method using long press
Figure 14-3. Example of long press followed by short press
Figure 14-4. Example of using long press after short press

A summary of the inventions presented in the applicant's earlier applications (Application No. 10-2000-0031879 and PCT/KR00/00601) is as follows.

First of all, according to the "part-to-all selection method", a predetermined number of grids are configured for each button on the keypad in a form corresponding to the arrangement of all buttons in the keypad, alphabets are arranged in the grids, and the alphabet to be input (hereinafter referred to as "target A desired alphabet is input by combining and pressing the first button on which the first button (abbreviated as “alphabet”) is arranged and the second button on the keypad corresponding to the arrangement position of the alphabet in the grids of the first buttons. For example, in Fig. 1-1, "A = [1] + [2] is entered.

Among the grids of buttons, using some grids, including a reference grid in which the first button and the second button are the same, using some grids, but the convenience of the combination of the first button and the second button is high The key to the partial-total selection method was to preferentially use the lattice of order. In this way, the core of the partial-total selection method lies in the reference grid, and the keypad that can utilize the concept of the reference grid is named “reference keypad”.

Next, the standard repetition selection method measures the number of button presses in the order close to the standard grid from the alphabet of the standard grid position on the standard keypad configured to apply the partial selection method (order of convenience of button combination in the partial selection method). It was a way to select the alphabet according to The standard repetition selection method is to apply the repetition selection method to the standard keypad. The exclusive use of the standard keypad for the repetition selection method is named "simple keypad", and for convenience, the repetition selection method is applied to the simple keypad as previously used. This is called the simple iterative selection method.

And there was "control processing method", which included "subscript control processing method" and "subsequent control processing method". The subscript control processing method was a method of inputting a modified alphabet by combining the subscript control and basic alphabet when inputting a modified alphabet consisting of a subscript and a basic alphabet. The follow-up control processing method sets the alphabets of a group assigned to a button in the relationship between the representative alphabet and the follow-up alphabet, and inputs the follow-up alphabet by combining the representative alphabet and the sub-rank attached to the representative alphabet when inputting the follow-up alphabet. was to make it possible. For example, in FIG. 4-1, "ㅋ = a + [*]" can be entered.

The subscript control process and the subsequent alphabet control process are essentially similar, and the subsequent control process can be seen as more general. This is because even in the case of subscript control processing, it can be seen that modified alphabets are attached in a certain order to the basic alphabet in a specific alphabet group. In the case of monoscript control processing, since modified alphabets can be decomposed into subscripts and basic alphabets, this is the case where alphabet groups have a strong relationship in their shape, and subsequent control has a strong relationship in their order or pronunciation. is the case

The advantage of applying the control processing method is that the layout of the keypad can be simplified by not displaying the subsequent alphabet (or modified alphabet) on the keypad through the relationship between the basic alphabet and the subsequent alphabet (or modified alphabet) , it was possible to input alphabets without ambiguity through control processing. The keypad simplified by omitting subsequent alphabets was called "subsequent keypad", the keypad simplified by omitting modified alphabets was called "simplified keypad", and the combination of both was called "simplified keypad". The keypad displaying all subsequent alphabets (or modified alphabets) was called "full display keypad" in preparation for the simplified keypad.

It is said that even in the full display keypad, the subsequent alphabet (or modified alphabet) can be input through the control processing method, and on the contrary, even in the simplified keypad, users who memorize the arrangement of the entire display keypad can use the input method in the full display keypad. did In this way, the simplified keypad can be expanded to form a full display keypad, and the compatibility that the subsequent alphabet can be input through the control processing method according to the user's convenience in the entire display keypad was one of the characteristics of the previous application.

One of the effects of applying the control processing method is, in addition to the effect of removing ambiguity, as shown in the previous application, through the relationship between the representative alphabet and the subsequent alphabet, the subsequent alphabet is not displayed on the keypad and "hidden" By doing so, it is possible to simplify the keypad. For convenience, this is referred to as "hidden control processing method". However, as mentioned in the earlier application, the subsequent alphabet (or modified alphabet) can be input through the control processing method even in the entire display keypad displaying the subsequent alphabet (or modified alphabet) on the keypad. For convenience, this is referred to as a "non-hidden control processing method".

Since it is essential to explain with specific examples due to the nature of the present invention, details will be described through examples.

First, the contents of the earlier application for each language are supplemented as follows. Among the contents mentioned in one language below, it is obvious that the contents applicable to other languages can be applied to other languages even if they are not specifically mentioned in other languages.

1. Common Supplements

1.1 Application scope of keypad in the previous application and the present invention

It is obvious that the keypad presented in the previous application and the present invention can be applied to all fields in the form of a telephone keyboard, such as a numeric keypad of a mobile terminal or standard keyboard or a keypad or door lock configured by software on a screen. In addition, although the numeric keypad provided in the standard keyboard has a different layout of the keypad and number buttons presented in the prior application and the present invention, it is obvious that the arrangement on the keypad buttons in the prior application and the present invention can be applied to the keypad provided in the keyboard. . For example, in the previous application and in the present invention, the alphabets placed on the [1] button are placed on the [1] button of the numeric keypad provided on the keyboard, and arranged in the same way below to allow for alphabet input, utilization of simple codes, and various codes. It can be used for memorization.

1.2 Setting of continuous hitting delay time and other delay time

In languages in which consonants and vowels appear alternately, such as Korean and Hindi, in applying a method of assigning a pair of representative consonants and representative vowels to each button, and selecting one consonant and two vowels for a consonant, a certain delay time ( For example, if an algorithm is implemented to recognize two strokes of the same button input within an interval of 0.1 second as a vowel primarily, it can be implemented efficiently while reducing the user's reluctance. This delay time should be determined in consideration of the universally pressed time interval for a certain period of time when the same button is continuously pressed. For convenience, this delay time is referred to as "battery delay time". In addition, it can be implemented so that two strokes of the same button input over a certain delay time (for example, 1 second) interval are primarily recognized as two consonants. For convenience, this delay time is referred to as "this other delay time". This can be applied even when the same button is pressed three times or more.

For example, in FIG. 4-1 or FIG. 4-2, if [1] + [1] is input with a delay time of 0.08 seconds, it is primarily recognized as a vowel "ㅗ", and if a delay time of 1.1 seconds If it is entered with , it is recognized as two consonants ("ㄱ", "ㄱ") primarily. If it is input with a time delay of 0.5 seconds, it can be determined whether one vowel or two consonants are input through the consonant and vowel appearance structure of the language. In addition, even when input is delayed by 0.08 seconds or 1.1 seconds, it is possible to finally determine whether one vowel or two consonants are input through the appearance structure of consonants and vowels in the language.

Previously, only one stroke was set at a certain time interval (for example, 1 second), and if the same button was pressed consecutively within that time, it was recognized as two consecutive strokes, and if two strokes of the same button were pressed after a delay of more than that time, each was recognized as one stroke. . The difference is that the standard time delay value (eg 0.1 second) judged as two consecutive strokes and the time delay value (eg 1 second) judged as one stroke each are set differently.

In general, among the partial selection method and the repeated selection method of the previous application, the iterative selection method is superior in terms of input convenience. Therefore, this means that ambiguity can be largely avoided by using the structure of a specific language in which consonants and vowels appear alternately while utilizing the advantages of the repeated selection method (simplicity and convenience of input rules), It has the advantage of simplifying the implementation of the algorithm by setting the delay time and the delay time differently, and allowing the user to designate them.

1.3 Chain type control processing method

In the earlier application, the subscript control processing method is essentially the same as the subsequent control processing method, and the subsequent control processing method is said to be a more general method. In other words, in the Korean example of the previous application, the relationship between a, ㅋ, and ㄲ was explained as the relationship between the representative alphabet and the modified alphabet, and ㅋ = a + {sound}, ㄲ = a + {hard sound}, but a (representative alphabet) , ㅋ (2nd), ㄲ (3rd), because the result is the same even if you put the relationship between the representative alphabet and the subsequent alphabet.

In the case of Japanese in FIG. 2-1, an input example by the subsequent control processing method is shown again as follows. Like あ (representative alphabet), い (2nd), う (3rd), え (4th), お (5th), with the relationship between the representative alphabet and subsequent alphabets, select あ with one stroke of the [1] button (あ= [1]), and the 2nd, 3rd, 4th, and 5th controls are placed on an arbitrary control button (ex. [*]), and the subsequent alphabet is created by combining the representative alphabet and the subsequent alphabet by repeatedly selecting according to the number of times the button is pressed. can be entered. For convenience, the state of control selection is indicated with curly brackets. = [1]+[*]+[*], え = あ+{4th} = [1]+[*]+[*]+[*], お = あ+{5th} = [1]+[ *]+[*]+[*]+[*].

Here again, establish the relationship between the representative alphabet and the subsequent alphabet, such as あ (representative alphabet), い (2nd), う (3rd), え (4th), and お (5th), but place the subsequent control on the control button and select it repeatedly Instead of selecting it as a method, it is possible to select the "subsequent" or "next" control by pressing a specific control button (eg [*]) once, and when entering the second subsequent alphabet (eg い), the representative alphabet and "next control" (that is, い = あ + {next} = あ + [*]), and when entering the 3rd subsequent alphabet え, the preceding alphabet (secondary subsequent alphabet) is used for the 3rd subsequent alphabet It is regarded as a new representative alphabet (secondary representative alphabet) and can be input by combining the second follow-up alphabet and "next control". That is, う = い + {next} = [1] + [*] + [*]. Similarly, when entering the 4th successive alphabet え, the previous preceding alphabet (third successive alphabet) う is regarded as a new representative alphabet (tertiary representative alphabet) for the 4th successor alphabet, and when え is input, え = う + {next} = You can input like [1]+[*]+[*] + [*]. The same applies to the 5th order subsequent alphabet.

This result is the same result as inputting a combination of the representative alphabet and subrank control while arranging sub-ranking controls (2nd, 3rd, 4th, 5th, ...) on the control button and selecting them by the repetitive selection method. to be. Here, if the first representative alphabet あ can be selected without ambiguity, it is easy to see that the second successor alphabet い can be entered without ambiguity, and the same is true for the rest of the subsequent alphabets. In other words, え = い + {next} = [1] + [*] + [*]. I was able to enter い without ambiguity, and い is also a form that is combined with "next control", so as a result, the subsequent alphabet without ambiguity. In え, you can enter.

In this way, in the relationship between the representative alphabet and the subsequent alphabet, it is assumed that there is only one “next” control instead of a subordinate control on the control button, and when the subsequent alphabet is input, the preceding alphabet is regarded as a new representative alphabet, and this preceding alphabet and “next” " The method of combining and inputting controls is called "chain-type follow-up control processing method" for convenience. In the previous application, even if the subordinate control is not displayed on the subsequent control button, the user only needs to be aware that a specific button is a subsequent control button. Even if it is displayed on a button, the display can be simplified. In the present invention, since the results of the "subsequent control processing method" and the "chain-type subsequent control processing method" described in the previous application are the same, they are used interchangeably.

1.4 Skip control processing method

In the subscript control processing method, when inputting the modified alphabet ё consisting of ".. + e", it was shown that it can be input by combining .. and e respectively. Alternatively, with e as the basic alphabet and the rest of the appended alphabets related to it in shape or rank as subsequent alphabets, it was possible to enter the combination of the subordinate rank and the basic alphabet (e.g. e (basic alphabet), ^/ e(2nd), ^{^} e(3rd), . . . ). In addition, the control buttons, in which controls that can have meaning only when combined with alphabets (ie, specific number buttons) are placed, can be used repeatedly to input modified alphabets or subsequent alphabets without ambiguity.

In the case of Roman letters, 11 variant alphabets ( ^/ e, ^{^} e, `e, ё, `a, ^{^} a, ^{^} i, `u, <sup>^</sup> u, c, <sup>^</sup> o) are used in French, and are used in the modified alphabet. There are 5 types of upper points (/, ^, `, .., s). If the selection order of subscript control is /, ^, `, .., s, <sup>^</sup> a = a+[*]+[*] should be entered. However, since only two suffixes "`" and "^" can be combined with the alphabet a in French, the suffix "/" cannot be added ^. = a+[*]. For convenience, this is referred to as a "skip control processing method". That is, it is the same as inputting the subsequent alphabet (or modified alphabet) as a control processing method with sub-orders of subsequent alphabets such as a (basic alphabet), `a (2nd), ^{^} a (3rd).

Similarly, in Japanese, the only lines in which long sounds exist are the letters つ among the letters of the lines あ and や and the lines of TA, and the lines with voiced sounds are only the letters of lines KA, さ, TA, and ほ, and semitones are only It exists only in the alphabet of line ほ. As a result, it can be seen that there are two modified alphabets of long sound and voiced sound in the alphabet つ, and two modified alphabets of voiced sound and semi-voiced sound in the alphabet of row ほ. Therefore, when inputting the modified alphabets of the remaining alphabets except for the six alphabets in which two modified alphabets exist, it can be made possible by pressing the subscript control button once. For example, if you set the control button to [*] and apply post-control input, you can do ぁ = あ+[*], が = か+[*]. In the case of six alphabets in which two variant alphabets exist, controls can be selected in the order of frequency of use of the variant alphabet when inputting the variant alphabet. For example, when the control button is set to the [*] button and the post-control input is applied, っ = つ+[*], づ = つ+[*]+[*], ぼ = ほ+[ *], ぽ = ほ + [*] + [*]. That is, in the control selection, the control that cannot be combined with the basic alphabet does not take effect. For example, even if が = か+[*], [*] can be treated as selecting a long sound control rather than a long sound control. , This is because it is skipped and the silent sound control is selected.

The advantage of strictly applying the selection of controls is that it is possible to input alphabets that are not actually used. For example, although there is no alphabet with a subscript ".." in the French alphabet b, it is possible to input such an alphabet, and there is no alphabet with a dot in the Japanese alphabet あ, but such alphabets can also be input. that can be made possible.

Even if the control is selected as the repeated selection method, if the representative alphabet displayed on the keyboard can be entered without ambiguity when input through control processing (for example, even if there is only one or multiple representative alphabets displayed on the keyboard, ambiguity such as partial selection method) If the method without ) is applied, the remaining subsequent alphabets can also be entered without ambiguity. This is because ambiguity is removed through control processing, and this is due to the fact that control cannot represent a specific alphabet alone and must be combined with other alphabets.

1.5 Input by control processing method of numbers and English alphabet

As suggested in the previous application, it was explained that the native language alphabets could be arranged in "an order close to the standard grid", and then numbers and English alphabets could be arranged. It has been explained that native language alphabets and numbers can be selected. Similarly, in applying the subsequent control processing method, numbers and English alphabets (in the case of non-Roman alphabets) as well as the native language alphabet belonging to a specific button can be input through the subsequent control processing method.

Numbers or English alphabets may be placed as subsequent alphabets following the native language subsequent alphabets. For convenience, in the case of Japanese, for example, あ (representative alphabet), い (2nd), う (3rd), え (4th), お (5th), 1 (6th), . (7th), q (8th), z (9th). Also, if there are available buttons for controlling numbers or English alphabets, the control buttons for あ (representative alphabet), い (2nd), う (3rd), え (4th), and お (5th) can be set to any button. button (eg [*] button), and other buttons (eg [#] button) as buttons for numbers or English alphabets, あ (representative alphabet), 1 (2nd), . (3rd), Numbers or English alphabets can be entered in the relationship of q (4th) and z (5th). For example, 1 = あ+[#] = [1]+[#], . = あ+[#]+[#] = [1]+[#]+[#], q = あ+[#]+[#]+[#] = [1]+[#]+[#] It becomes like +[#]. If control buttons are available, a control button for inputting numbers and a control button for English alphabets can be placed separately.

This can be applied to other languages as well as input of various symbols described later.

1.6 Grouping according to English alphabet pronunciation

In configuring the keypad for each language in the previous application, considering the application of the control processing method and use for memorization, the alphabet was grouped into similar pronunciation groups and assigned to each number button. In the case of English, a method of grouping alphabets by 3 or 4 according to dictionary order and assigning each group to each number button is widely used, but it is also possible to group and assign each group to each number button considering the similarity of pronunciation. . The following are some examples of grouping English consonants into 9 groups according to similarities in pronunciation.

B P / C S X / D T / F V H / G K Q / J Z / L R / M N / W Y

B P V / C S X / D T / F H / G K Q / J Z / L R / M W / N Y

An example of grouping English consonants into 8 groups is as follows.

B F P V / C G K Q / S X / D T / J Z / L R / M W H / N Y

B F P V / C G K Q / S X / D T / J Z / L R / M N / W Y H

In addition to the above examples, many variations are possible. Five vowels can be properly put into groups grouped by two. This can provide convenience when applying a shortcut input method using a simple code, which will be described later. In the case of non-English languages, when assigning the grouped English alphabets to each button, it can be assigned considering the similarity with the pronunciation group of the native language. For example, in the case of Korean, groups G, K, and Q are assigned to buttons assigned with the letter "ㄱ" with a similar pronunciation. In the case of Japanese, groups G, K, and Q are assigned to buttons assigned with the alphabet "KA" with a similar pronunciation. Therefore, even in the grouping of English alphabets, grouping can be performed in consideration of grouping of native language alphabets of each language.

2. Supplements for each language

*Hereinafter, the contents of the earlier application for each language are supplemented and the developed matters are described as follows. Among the contents described in the supplementary matters for each language, if the contents described in one language can be applied to other languages, it is obvious that they can be applied to other languages without specifically pointing out this.

2.1 English

Just as subsequent alphabets can be entered through the control processing method in the entire display key pad in the previous application, even in the case of English, it is possible to display alphabets other than the representative alphabet on the keyboard and input through control processing. In the case of English, subsequent controls (2nd, 3rd) can be placed on the same control button (eg [#] button), or each can be separately placed on another button (eg [*], [#] button). In the case of English, when ABC is placed on one button, if A is the representative alphabet, B and C are input through subsequent control processing, respectively, and if B is the representative alphabet, A and C are each subsequent control input through processing. As mentioned in the earlier application, the sub-order of the representative alphabet and the subsequent alphabet can be determined in consideration of the frequency of use.

For example, if A is the representative alphabet in A, B, and C groups, the 2nd and 3rd controls are placed on the [*] button, and input is applied after control, B = A+{2nd} = [2]+[*] , C = A+{3rd} = [2]+[*]+[*]. If B is the representative alphabet, and the 2nd and 3rd controls are placed on the [*] and [#] buttons, respectively, and the input is applied after control, A = B+{2nd} = [2]+[*], C = B+{3rd} = [2]+[#]. 1-2 is an example in which the central alphabet among the alphabets of each group is set as the representative alphabet in the center and subsequent alphabets are placed on the left and right to further facilitate the identification of the alphabet. D = E+{2nd} = [3]+[*].

In this way, inputting only the representative alphabet with one stroke of the button to which the representative alphabet belongs and inputting the remaining alphabets by the control processing method is called “Control Processing Method Except Representative Character (CPMERC)” for convenience.

In addition, when four alphabets P, Q, R, and S are assigned to the [7] button, and four alphabets W, X, Y, and Z are assigned to the [9] button, as pointed out in the Korean embodiment of the previous application, , the partial-total selection method can be applied by arranging one of the four alphabets in a lattice forming a top-down adjacent combination. See Figures 1-3.

2.2 Japanese

In the case of Japanese in the previous application, alphabets are grouped based on 50 sounds, and the alphabets in column あ (あ, か, さ, …) are used as representative alphabets, and the rest of the alphabets can be used as subsequent alphabets for subsequent control processing. disclosed in the earlier application. In applying the sub-order of subsequent alphabets presented in the earlier application, the 50-note chart can be simply applied as shown in the following table, almost similar to Method 3 of the earlier application. This can give users a sense of familiarity with the simplicity of sub-ordering. As in the previous application, ん can be treated as belonging to any representative alphabet. In addition, it can be considered that 50 sound alphabets (for example, い, う, え) are attached to the empty places of the や line or わ line, or ん is attached.

Prior application method 3 How to use simple 50 notes reference grid ^2nd 3rd 4th 5th reference grid ^2nd 3rd 4th 5th あ い う え お あ い う え お か き く け this か き く け this さ Shi s せ そ さ Shi s せ そ た ち つ て と た ち つ て と な に ぬ ね の な に ぬ ね の ha ひ ふ へ ほ ha ひ ふ へ ほ ま み む め も ま み む め も や ゆ よ や ゆ よ lah ri る レ ろ lah ri る レ ろ わ を ん わ を

In the case of Japanese in the previous application, for convenience, the alphabet in the first column, which can be regarded as the most representative, was used as the representative alphabet. can also be done with Also, in assigning the alphabets of each row as a group to each button, as mentioned in the prior application, the row of buttons on the keypad is based on ([1], [2], [3], [4], . . . ), or based on columns ([3], [6], [9], [2], [5], . . . ). Similarly, it is also possible to assign randomly, rather than assigning by row or by column.

In addition, in the Japanese example of the previous application, if "ん" is placed at the standard grid position of the [0] button, and the 2nd, 3rd, and 4th, 5th controls are placed on the [*] button and [#] button, respectively, the [0] button In order to use as a control button for inputting long sound/voice sound/semi-tone sound, it has been assumed that "ん" is assigned to any number button other than the [0] button. However, in this case, "n" may be placed at the position of the standard grid of the [0] button, and additional controls for long sound/voice/semi-voiced sound may be placed in an order close to the standard grid, and the repeated selection method may be applied to control selection. This is because "ん" does not appear consecutively in a single word. See Figure 2-1. Alphabets that do not appear consecutively are selected on the first stroke of the button where the corresponding alphabet is placed, and the second stroke, third stroke, ... Allowing the selection of different controls for . is applicable for all other languages as well. This property is also utilized in the method using Korean vowel elements described later.

2.3 Arabic

There are 28 consonants in Arabic. In the previous application, the Arabic consonants with numerical meanings are grouped as follows and assigned to the keypad buttons, and each alphabet with the smallest numerical meaning is used as the representative alphabet of each group, and placed at the position of the standard grid A method of arranging the remaining alphabets on the keypad in an order close to the standard grid (described in the previous application) from the alphabet having the meaning of small numbers has been proposed. In addition, in the previous application, a method of inputting alphabets by control processing has been proposed in the case of Japanese, Roman alphabetic languages, Korean, Indian languages, and Arabic. Even in the case of Arabic, a method of controlling subscripts by considering vowels that are rarely used as subscripts has been proposed.

Here, I would like to present a method of controlling Arabic consonants (subsequent control processing). The following is an example of grouping Arabic consonants in the previous application and assigning them to each button.

[1] Among the alphabets with the meaning of 1, 10, and 100 assigned to the button, the alphabet with the meaning of 1 is displayed on the keypad as the representative alphabet, and the remaining alphabets with the meaning of 10 and 100 can be subsequently controlled. have. As for the control button, any button can be used as in the previous application. If the [*] button is used as the subsequent control button and the 2nd and 3rd controls are placed, the average number of input strokes for consonant input is 2 strokes. Since only one alphabet is placed per button, it is not necessary to select the alphabet displayed on the button using the partial-total selection method. Since the arrangement of alphabets is conceptual, it is possible not to arrange alphabets on the keypad as described below.

Again, as in the case of Japanese in the previous application, subsequent controls can be separated into different buttons. For example, if the 3rd control is distributed and assigned to the [#] button, the average input strokes will be about 1.7 strokes ((1+2+2)/3) and 28 consonants can be entered without ambiguity as suggested in the previous application. do.

In this application, regardless of the frequency of use of the alphabet of each unit, an alphabet with a small number of meanings is the representative alphabet of each group, and even in the alphabets of the remaining units, an example in which an alphabet with a meaning of a small number can be selected first see. Controls can be input first or second input.

= [*] +

가 되고,

= [*] + [*] +

가 된다. 나머지 알파벳에 대해서도 동일하다. 이 경우 [#]버튼을 모음컨트롤처리를 위해 사용할 수도 있다. If all subsequent controls are placed on the [*] button, the alphabet of 1 unit is the representative alphabet, and the control button pre-input is applied when selecting the 10 unit alphabet,

= [*] +

become,

= [*] + [*] +

becomes Same for the rest of the alphabet. In this case, the [#] button can be used for vowel control processing.

= [0] 이 된다. 1000의 의미를 가지는 알파벳을 1그룹알파벳으로 처리할 수도 있다. 이 경우

= [*]+[*]+[*]+

가 될 것이다. 혹은 1000의 의미를 가지 는 알파벳이 70의 의미를 가지는 알파벳(

)에 윗점이 붙은 형태이므로, 윗점컨 트롤을 각종 모음컨트롤에 앞서 선택되도록 하여 컨트롤처리하는 것도 가능하다. 즉 윗점컨트롤 선입력시

= [윗점컨트롤] +

로 입력할 수 있는 것이다. 윗점이 붙어 이루어진 다른 알파벳에도 이러한 윗점컨트롤처리를 다른 입력방법과 병행하여 허용할 수 있다. 이 경우 [0] 버튼을 다른 용도의 컨트롤버튼(예를 들 어 모음컨트롤버튼)으로 활용하는 것이 용이하게 된다. If you place only one alphabet that has the meaning of 1000 on the [0] button,

= [0]. An alphabet having a meaning of 1000 may be processed as a 1 group alphabet. in this case

= [*]+[*]+[*]+

will be Or an alphabet with a meaning of 1000 is an alphabet with a meaning of 70 (

), it is possible to control by selecting the upper point control before various vowel controls. That is, when the upper point control is pre-entered

= [top control] +

that can be entered as For other alphabets composed of upper points, this upper point control process can be allowed in parallel with other input methods. In this case, it is easy to use the [0] button as a control button for other purposes (for example, a vowel control button).

= [#] +

가 된다. 이 경우도 선출 원의 일본어의 경우와 같이 입력시,

= [*] + [*] +

을 병행하여 허용 할 수 있다. 1000의 의미를 가지는 알파벳을 1그룹알파벳에 속하게 할 경우, 경 우

= [*]+[*]+[*]+

혹은

= [#]+[#]+

가 된다. 즉 [*] 버튼에 2nd, 3rd, 4th 컨트롤이 배치되어 있는 것으로 그리고 [#] 버튼에 3rd, 4th 컨트 롤이 배치되어 있는 것으로 생각하면 된다. 아랍인들이 우에서 좌로 가로쓰기를 하는 점을 고려하여, 즉 [#] 버튼에 2nd, 3rd, 4th 컨트롤을 배정하고, [*] 버튼 에 3rd, 4th 컨트롤을 배치하는 것도 가능하다. If the control is separated and the 3rd control (in this case, the 100 unit control) is used as the [#] button, the alphabet with the meaning of 200

= [#] +

becomes In this case, as well as in the case of Japanese of the original application, at the time of input,

= [*] + [*] +

can be allowed concurrently. In case of making alphabets with meaning of 1000 belong to group 1 alphabets

= [*]+[*]+[*]+

or

= [#]+[#]+

becomes In other words, it can be considered that the 2nd, 3rd, and 4th controls are placed on the [*] button, and the 3rd and 4th controls are placed on the [#] button. Considering that Arabs write horizontally from right to left, it is also possible to assign the 2nd, 3rd, and 4th controls to the [#] button and the 3rd and 4th controls to the [*] button.

This means that in Arabic, the mainly used consonants can be entered without ambiguity in an average of about 1.7 strokes, and since Arabs know the meaning of numbers in their native language alphabets, There is a great advantage of being able to input the alphabet without displaying the unit alphabet, that is, the representative alphabet. In other words, when applying the method in this application through a keypad displaying only numbers, the representative alphabet is which unit of alphabet, the control button is the control button for which unit of alphabet, and the subsequent control is one control button If you use , you can input most of the alphabets (Arabic consonants) needed in real life by familiarizing yourself with the rules such as the selection order of each subsequent control and whether to input the control buttons first.

As pointed out in the previous application, vowels can also be controlled. When both [#] and [*] are used for consonant control processing, as in the Japanese of the previous application, the alphabet with the meaning of 1000 is displayed on the [0] button. Instead of arranging, place it on the [1] button for control processing, designate the [0] button as a control button for vowel processing, and select subscripted vowels (vowel control, subscript control) by the repeated selection method. The method is to select a vowel control (a vowel in the form of a subscript) according to the number of button presses in the order of frequency of use. If only [*] is used as the follow-up control button for consonants, [#] can be used as the control button for vowels, or both [#] and [0] can be used.

In the examples of FIGS. 3-1 and 3-2, the alphabets having meanings of 1 to 9 (one-unit alphabets) are used as representative alphabets for each group, but the most frequently used alphabets in each group may be used as representative alphabets. . In addition, in order to reduce confusion, an alphabet of any unit among 1 unit alphabet (an alphabet with meanings of 1 to 9), 10 unit alphabet (an alphabet with meaning of 10 to 90), and 100 unit alphabet (an alphabet with meaning of 100 to 900) can be used as the representative alphabet. 3-3 shows the 10-unit alphabet as the representative alphabet, placing it in the center of each group, and using the control buttons assigned to the left and right of the remaining alphabets (100-unit alphabet, 1-unit alphabet) assigned to the left and right Input by the control processing method is a case of

Likewise, the alphabet selected by the subsequent control can be the alphabet of each unit according to the frequency of use. For example, if the 100-unit alphabet is the most frequently used, set it as the representative alphabet, and if the 1-unit alphabet is the most frequently used, the 2nd control (i.e., the 1-unit control here) and the representative alphabet can be entered in combination. It is to allow 10 unit alphabets to be input by combining the 3rd control (ie, 10 unit control) and the representative alphabet.

Since it is said that it is possible to input subsequent alphabets through the control processing method in the entire display key pad in the previous application, it is possible to input consonants by the subsequent control processing method and input vowels by the subscript control processing method in the keypad of the previous application as well. do. In the 3*4 keypad, if the [0] button is the subscript control button for vowels, it is possible to distribute the control buttons for consonant input to the [*] button and the [#] button.

2.4 Korean

2.4.1 Application of various controls

4-1 to 4-3 show a method of assigning basic Korean consonants and basic vowels in pairs to each button, and inputting the basic consonants and basic vowels displayed on the keypad by the repeated selection method. In Fig. 4-1, aspirated consonants, tense consonants, and extended vowels were input by the control processing method, and in Fig. 4-2, only aspirated consonants and tense consonants were input by the control processing method. 4-3 is an example in which aspirated consonants, tense consonants, basic vowels, and extended vowels are input by the control processing method.

2.4.2 Program implementation

4-4 is just an example of a flow chart for implementation, and more efficient programming is possible. For example, in FIG. 4-4, when the consonant part of the support comes, a slightly more efficient implementation is possible by checking in advance whether the consonant can form a double support.

The Korean example presented in the previous application can also be applied to other languages with similar characteristics (a structure in which consonants and vowels alternate). In the case of other languages, it is sufficient to reflect the consonant appearance characteristics of other languages.

For example, if you want to construct a Hindi input system using a pair of basic consonants and basic vowels, it can be implemented similarly to the case of Korean by reflecting the characteristics of Hindi. The simpler the rules, the easier it is to implement.

2.5 Hindi

In the applicant's earlier application, Hindi consonants are grouped into 9 groups and assigned to buttons [1] to [9], so that the vowel assigned to button [0] is selected with one stroke of the [0] button. It is grouped into groups, and the representative sound can always be selected as one stroke, and 10 vowels can be selected as two strokes. The vowel ___(ri), which is not placed on the keypad and is not frequently used, can be processed by the control processing method. In grouping consonants into 10 groups, as suggested in the previous application, a method of grouping considering the similarity of pronunciation is possible. An example of grouping into 10 groups is as follows.

And it is said that the first vowel ___(a) in Hindi can be omitted between consonants. That is, the consonants appear consecutively. In this case, even if "consonant + ___(a) + consonant" is entered, it is very easy to display "consonant + consonant". Of course, it is possible to directly input "consonant + consonant", but in this case, the same representative sound is selected in succession, so there is a high possibility that two consonants can be recognized as one vowel. Therefore, both (automatic omission of vowel ___(a) or omission input by the user) can be allowed.

2.6 Burmese

There are 33 consonants in Myanmar language. As in the example of Hindi, it is grouped into 9 or 10 groups, a representative alphabet is determined, and the remaining consonants can be input by the subsequent control processing method.

3. Multi-dimensional intersection control processing method

2-2 is an example of assigning alphabets to each button in alphabetical order by using the alphabets of the "あ" column as representative alphabets according to the table above. In the case of the previous application, the 4nd and 5th controls could be additionally assigned to the control buttons to which the 2nd and 3rd controls were assigned. see.

The method of inputting subsequent alphabets in FIG. 2-2 is as suggested in the previous application. For example, when applying post-control input, it becomes like い = あ+[*]. Next, we show how to input the long sound, voiced sound, and semitone sound, which are the modified alphabets of each alphabet. In Fig. 2-2, all buttons available as control buttons ([*] button, [#] button) are used as subsequent control buttons. Therefore, there is no control button for the modified alphabet. However, if the basic alphabet of the target alphabet is a subsequent alphabet, after inputting the subsequent alphabet, the subsequent control button that is not used as a subsequent control button can be used as a modified alphabet control button (this is called "opposite control button" for convenience) to input. can

For example, ぃ = い + "opposite control button" = あ+[*] + [#], ご = こ + "opposite control button" = か+[#]+[#] + [*] do. This can be seen as using the opposite control button that is not used as a subsequent control button as a modified alphabet control button in order to input ぃ in applying the control processing method by considering ぃ as a modified alphabet of the basic alphabet い. As in the example, the skip control processing method of the previous application can be applied here as well. From the point of view of the chain-type control processing method, by pressing the control button on the opposite side once, it can be seen as selecting the "next control" to input a modified alphabet (ご in the example) of the previously entered alphabet (こ in the example) can

Since there are two types of modified alphabets in the alphabet of the は line, voiced sound and semitone sound, in the case of a long sound, you can press the control button on the opposite side once, and in the case of a semitone sound, press the control button on the opposite side twice. That is, ぶ = ふ + "opposite control button" = は+[*]+[*] + [#],ぷ = ふ + "press the opposite control button twice" = は+[*]+[*] + [# ]+[#].

Next, if the basic alphabet of the target alphabet is a representative alphabet, the above method cannot be applied as it is. In this case, the target alphabet can be input by placing the modified alphabet of the representative alphabet as the subsequent alphabet in addition to any button among the subsequent control buttons.

For example, when inputting a modified alphabet (long sound, dull sound, semi-tone sound) of the representative alphabet using the [*] button, あ = あ + [*] + [*] + [*]. In other words, the modified alphabet (long sound, voiced sound, semitone sound) of the representative alphabet is regarded as the 4th subsequent alphabet that can be input using the [*] button. Summarizing the above, it becomes:

In this way, using the opposite control button to expand the use of the control button and use it for more alphabetic or other input is called "cross control processing method" or "zigzag control processing method" or "multi-dimensional cross control processing method" for convenience. call This can be applied even when three or more buttons are used as control buttons.

In the table above, it is obvious that the cells of the remaining columns, except for the first column, can also be used for inputting other alphabets or various symbols. In the example above, the opposite control button is applied once. In other words, when inputting ぷ, ぷ = ふ + "Press the opposite control button twice" = は+[*]+[*] + [#]+[#] Use the control button on the opposite side repeatedly to use it as a subsequent control button. The opposite control button ([#] button) is applied only once to the selected [*] button. This is referred to as "two-dimensional cross-control processing" or "two-step cross-control processing" for convenience.

In other words, when only one control button is used to input one alphabet, this can be referred to as "one-dimensional control processing". This can be seen as using the control button “one-dimensionally”. However, in the two-dimensional (cross) control processing method, two different control buttons are used to input one alphabet. In other words, when entering ご, ご is regarded as a modified alphabet of こ, so ご = こ + "opposite control button" = KA+[#]+[#] + [*], where the opposite control button is already a representative alphabet Even though it was defined as a control button for inputting き and く, which are the alphabets following the 1st and 2nd of KA, the control button on the opposite side ([*] button) is like a modified alphabet control button for inputting the modified alphabet ご of こ. that can be utilized. This can be seen as using two control buttons “two-dimensionally” compared to using one control button one-dimensionally for one alphabet input.

ぷ = ふ + "Press the opposite control button once" + "Press the opposite control button once for the previous control button" = は+[*]+[*] + [#]+[*] may be In other words, if it is not possible to input the transformed alphabet by repeatedly using the control button ([#] button in the example) that was finally used for the input of ぶ, in the same way, use the opposite control button for the opposite control button again to You can enter a modified alphabet or a subsequent alphabet. For convenience, this is referred to as "three-dimensional cross-control processing" or "three-step cross-control processing". This means that the number of possible inputs of alphabets that can be input in the keypad or those related to other alphabet inputs can be infinitely expanded using the cross control processing method. Moreover, there is a great significance in that subsequent alphabets or modified alphabets that are related to the pre-entered alphabets can be naturally input by the control processing method.

If the above content is explained in the form of a graph with an example of the は row in which two modified alphabets (voiced sound and semi-voiced sound) exist, it is as shown in FIGS. 2-3. In Fig. 2-3, what is marked with ". . ." in a circle with a dim color is what you want to input additionally if necessary, as can be used to input other alphabets or symbols in the empty space in the table above ( alphabets or symbols) can be input by the multi-dimensional control processing method. In FIGS. 2-3, the [*] button and the [#] button are used in a right angle direction, respectively.

In the previous application, the [*] button was assigned the 2nd, 3rd, 4th, and 5th control, which is not the representative alphabet among the 50 phonetic alphabets, and the [*] button was used as a control button to input modified alphabets such as long sound, sound sound, and half sound sound. Compared to the method used, it can be seen that the two-dimensional control process is applied in the method of the previous application. That is, ぃ = い + {transformation} = い +[*]+[#] is entered because two control buttons are used. The difference is that in the previous application, the use of the control button was used only as a follow-up control (2nd, 3rd, 4th, 5th) button and only as a modified alphabet (long sound, voiced sound, semitone sound) control button, and the two-dimensional control of the present invention In the process, after inputting the subsequent alphabet, the subsequent control button is again used as the modified alphabet control button. In order to distinguish the use of the main-use control button (subsequent control button in the example) as a modified alphabet control button from the 2-dimensional control processing method of the previous application, for convenience, "2-dimensional recycling control processing method" or "2-dimensional multi-purpose control processing method" "Let's call it

The method of the previous application has the advantage of being simple and consistent in the input method, but has the disadvantage of relatively slightly increasing the number of input strokes. In order to easily show the difference from the present invention, the case where the control buttons in the previous application were used only as subsequent control buttons (2nd, 3rd, 4th, 5th) and only as control buttons for modified alphabets (long sound, voiced sound, semitone sound) is graphed When shown, it is as shown in Figs. 2-4. In FIGS. 2-3 and 2-4, the shaded parts can be expanded and applied.

In applying the cross control processing method above, an example of post-control input was shown, and this also applies to control pre-input or post-input in applying the control processing method in the previous application, by control pre-input can also be entered. For example, ぃ = "opposite control button" + い = [#] + [*]+あ. However, in applying the cross control processing method, it will be convenient to input the control afterward.

This can be equally applied not only to Japanese but also to all other languages. For example, if [*] and [#] are used to input subsequent alphabets by applying the control processing method excluding representative alphabets in Arabic, multi-dimensional cross control processing method can be used to input vowels in the form of subscripts. can In addition, even when using the [*] button and the [#] button as control buttons for inputting subsequent consonants and subsequent vowels in Thai, a multi-dimensional cross-control processing method can be used to input tonal codes.

4. Korean input method

4.1. How to use vowel elements in Korean

In the past, there was a method of assigning the elements constituting the alphabet to each button and inputting the alphabet with a combination of each element (eg →, ↓, ↙, ↘, ⊃, O, etc.). In addition, currently in Korea, there has been a case in which only Korean vowels are separated into three vowel elements (ㅡ, ., ㅣ => ie, angso), and the alphabet is entered on the keypad with a combination of each vowel element.

In Korean, a vowel can be divided into several vowel elements (hangso). For example, ㅡ, ., ㅣ can be divided into 3 vowel elements (also simply called “3 vowels” for convenience), and 4 vowel elements ㅡ, ., :, ㅣ (for convenience, simply called “4 vowels”) It can be thought of divided into (also called), and among them, ㅡ and ㅣ exist as vowels themselves, so it is possible to think of using vowel elements in the Korean input method on the keypad. Anyone who knows Korean knows that Korean vowels can be input by combining three vowel elements or by combining four vowel elements.

Hereinafter, it will be described in detail through examples.

4.1.1. 10 consonant 3 vowel method

First, as the basic alphabet for inputting Korean, 10 consonants, plain sounds (basic consonants), 3 vowel elements, and tense consonants and aspirated consonants for input by the control processing method (input in combination of basic consonants and controls), aspirated consonants You can think of 15 elements such as controls. Since this must be assigned and entered on a 3*4 keypad equipped with 12 buttons, basic consonants in which hard and aspirated consonants do not exist among 10 basic consonants on 9 buttons (for convenience, "9-button dropped consonants" or "10-9 consonants" or more simply called "-9 consonants"), the remaining 9 basic consonants are assigned to 9 buttons, and each of the 3 vowel elements, aspirated control, horn control, and 3 consonants dropped from the 9 buttons are randomly assigned. You can group them by two and assign them to the remaining three buttons. The basic consonant assigned to the 9 buttons is entered with 1 stroke of the assigned button, the vowel element is entered with 1 stroke of the assigned button, and the control grouped with the vowel element "." or the consonants dropped from 9 buttons are entered with 3 strokes of the assigned button. can do. For convenience, this will be referred to as the "10 consonant three-vowel method with aspirated consonant/hard consonant control processing" or "the three vowel method with aspirated consonant/inspired consonant control processing". Here, the control grouped with the vowel element "." or the selection with 3 buttons assigned to the 9 button dropped consonants can be seen as applying the repeated selection method as described later.

Here, in order to use the Korean keypad for memorization, it is desirable to assign 10 basic consonants to each of the 10 numeric buttons. Figures 4-5 show one such embodiment. In Figures 4-5, "ㅎ" is grouped with the vowel element "." as a 9-button dropped consonant and assigned to the [0] button, which is a number button. This is because it gives Koreans a sense of naturalness as it is at the end of the order, while causing less inconvenience even if the input button is low and cannot be entered with one stroke of the assigned button. 4-5, since the remaining basic consonants are also assigned to each number button in alphabetical order, there is an advantage in providing good location identification (readability) to the user.

When input after control is applied, ㅋ = a + {sound (control)} = [1]+[*]+[*], ㄲ = a + {sound (control)} = [1]+[#]+[# ] can be entered. As in the case of Japanese in the previous application of the applicant, this is to use the property that the vowels "ㅡ" and "ㅣ" do not appear consecutively in Korean, so that the aspirated consonant control and the aspirated consonant control can be selected by the repeated selection method. In the case of "ㅔ" or "ㅖ", the vowel "ㅣ" appears in succession, but the vowel element "." precedes it, so the system knows that pressing "##" did not select a control, but entered a vowel. In the previous application, it was said that even if the control is not displayed on the button, the user just needs to be aware that the control can be selected by pressing the corresponding button. You can remember to select the aspirated consonant control by pressing the button to which "ㅡ" is assigned twice, and similarly, by assigning the consonant control with the vowel "ㅣ", the user intuitively presses the button to which the vowel "ㅣ" is assigned twice. There is an advantage in knowing that the horn sound control is selected by pressing, and this property is also one of the elements to be protected as a right in the applicant's invention, and the same applies to the four-vowel method described later. This is not limited to the embodiment presented by the applicant, and can be equally used in other applications, and it is obvious that this is also included in the scope of the applicant's invention. For convenience, this will be referred to as "aspirated consonant/consonant control processing method using line-shaped vowel elements ("ㅡ", "ㅣ") buttons.

In the case of Fig. 4-5, the vowel element "." is implicitly placed by assigning the vowel element "." can do. After all, it is possible to compose a Korean input system by concisely arranging only one alphabet on the keypad. Similarly, as shown in Figures 4-9, it consists of "ㅎ = . + ㅡ + ㅇ", and a concise keypad can be configured by displaying "." of "ㅎ" in red and visually allocating only one grapheme.

In the 10-consonant 3-vowel method of aspirated/horizontal control processing, only the aspirated consonant is not entered by the control processing method, but by pressing the button to which the basic consonant of the aspirated consonant is assigned twice (i.e., by the hidden repetition selection method), it can be input. have. For convenience, this will be referred to as the "three-vowel method of aspirated repetition selection and tense consonant control processing". Alternatively, only the hard sound can be input by pressing the button to which the basic consonant of the hard sound is assigned twice (i.e., by the hidden repetitive selection method) without relying on the control processing method (this is It can also be viewed as entering as .). For convenience, this will be referred to as a "repeated selection method for horn control processing of horn sound repetition selection". Alternatively, both the aspirated consonant and the tense consonant can be input by the repetitive selection method without inputting them by the control processing method. When both aspirated consonants and hard consonants are entered by the repeated selection method, the repeated selection order may be basic consonants (1 stroke) - hard consonants (2 strokes) - aspirated consonants (3 strokes). It can be entered as a combination of basic consonants, and it can be regarded as inputting the aspirated sound with 3 strokes of the button to which the basic consonant belongs), and the basic consonant (1 stroke) - aspirated sound (2 strokes) - hard sound (3 strokes) . For convenience, the former case will be referred to as the "prior consonant repeated selection 3 vowel method", and the latter case will be referred to as the "prior consonant repetition selection 3 vowel method". For convenience, the several described in this paragraph will be collectively referred to as the "triple consonant/consonant repetition selection method".

In addition, while maintaining the aspirated/hard consonant control processing 3 vowel method, the "aspirated/hard consonant repeated selection 3 vowel method" can be applied. can also be applied. While maintaining the three-vowel control method for aspirated consonants/hard consonants, it is possible to apply the repeated selection method for only aspirated consonants, or to apply the repeated selection method for only tense consonants, or to apply the repeated selection method for prior tense consonants. Various combinations are possible, such as applying the aspirated consonant repetition selection method. Conversely, while maintaining the three-vowel method of repeated selection of aspirated consonants and tense consonants, it is possible to apply the control processing method of only the aspirated consonant, the control processing method of only the aspirated consonant, or the control processing method of both the aspirated consonant and the aspirated consonant. have. Alternatively, aspirated consonants can be entered only by the control processing method, and aspirated consonants can be entered only by the repetitive selection method. Conversely, aspirated consonants are entered only by the control processing method, and tense consonants are entered only by the repeated selection method (i.e., combination of basic consonants). You may. Combinations similar to those exemplified may further exist, and for convenience, this will be referred to as the “triple vowel method using aspirated consonant/serious consonant control process repeated selection mixed use”. In general, the case where the input method of aspirated consonants and tense consonants is not specifically designated is referred to as "10 consonant three-vowel method" for convenience. In case of inputting tense and aspirated consonants, it is also possible to allow the user to set a convenient input method.

The frequency of ambiguity that occurs when applying the repeated selection method for both aspirated and tense sounds is about 1 in 140 characters, which is about 15 characters in Samsung Electronics' input system. It occurs much less often than it does in Hangul characters. Whether the aspirated or aspirated consonant is input by the repeated selection method or the control processing method, the aspirated or aspirated consonant may be additionally allocated and arranged to each number button, and this is also included in the scope of the present invention, of course.

4.1.2. 10 consonant four vowel method

The cases of FIGS. 4-5 and 4-9 can be solved and expressed as in FIGS. 4-6. In Figures 4-6, the same input method as in Figures 4-5 can be applied. As shown in Figures 4-6, this is a vowel element necessary for inputting Korean vowels "ㅕ" or "ㅛ", etc. It acts as a horizontal or vertical stroke, but here, for convenience, the horizontal stroke ':')" is grouped together with the vowel element "." and assigned to the same button, and the vowel elements ".", ":" It can be seen that the button 1 and 2 are selected respectively by the repeated selection method, but the vowel element “:” is not explicitly placed on the button. Of course, as shown in FIGS. 4-6, the result is the same even if it is explicitly assigned and the alphabet displayed on the keypad is selected by the repetitive selection method. However, even if the vowel element ":" is not displayed on the button, the user intuitively inputs the combination of the vowel element "." (i.e. ":" = "." + "." = [0]+[0]). can be thought of as In the end, Figures 4-5 also use four vowel elements ("ㅡ", ".", ":", "ㅣ"), but one of the three vowel elements " Grouped with "." and the vowel element ":" and assigned to an arbitrary button, ".", ":" and the 9 button dropped consonants (in the case of Figs. 4-5) assigned together, respectively, by the repeated selection method However, it can be seen that the vowel element ":" is not displayed on the button. This is the same result as the above-mentioned “10 consonant 3 vowel method”, but for convenience, “10 consonant dot vowel element repeated selection 3 vowel method” or “10 consonant dot vowel element repeated selection 4 vowel method” or “10 consonant dot vowel element repeated selection 4 vowel method” It is called the consonant point (點) vowel element repetition selection vowel element method". A tense sound and a vowel sound can be input by the various methods described above. In fact, the same result, but the explanation with a separate name means that Fig. 4-5 also utilizes four vowel elements and applies the repeated selection method, but it can be seen that the vowel element ":" is not displayed on the button. (Even if it is not displayed as in Fig. 4-5, the input method and the algorithm constituting the input system are the same as in Fig. 4-6), which means that the existing Korean input system of Samsung Electronics only uses three vowel elements. While it was an approach that utilizes, the input system presented by the applicant intends to emphasize what can be seen from a different perspective (using four vowel elements).

4-7 shows a case where the vowel element ":" is not grouped together with the vowel element ".", but grouped into different groups. That is, four vowel elements (“ㅡ”, “.”, “:”, “ㅣ”) are assigned to different buttons, and for convenience, this is called “10 consonant 4 vowel method” or “4 vowel method”. . Since the 4-vowel method has many points in common with the 3-vowel method, it will be explained relatively briefly. Terminology can also be used similarly to the term used in the three-vowel method.

As in the 4 vowel method, among the 10 basic consonants, except for the 2 basic consonants that do not have aspirated and aspirated consonants, the remaining consonants are assigned to 8 buttons, respectively, and each of the 4 vowel elements, aspirated consonant control, and aspirated consonant control, 8 buttons The two consonants not assigned to (for convenience, called "8 button dropped consonants" or "10-8 consonants" or more simply "-8 consonants") are grouped by two each, and the vowel elements are entered with one stroke of the assigned button , Controls or dropped consonants assigned together can be entered with two strokes of the assigned button (i.e., entered by the repeated selection method).

Here, too, it is possible to use it for memorization by assigning 10 basic consonants to each number button. In addition, by assigning the vowel element "." to the [0] button with a similar shape and displaying it within the number "0", concise placement on the button can be enabled (or the shape is similar even if the display within the number is omitted, so the user can easily recognizable), by assigning the vowel element ":" to the [8] button with a similar shape, and displaying it inside the number "8" (or omitting the mark inside the number, the shape is similar, so the user can easily recognize it There is an advantage in that only one alphabet can be placed per button. As shown in Fig. 4-7, if the buttons to which the vowels "ㅡ" and "ㅣ" are assigned are the [*] button and the [#] button, pressing the adjacent button when inputting various vowels in Korean reduces the fingering distance It works.

In the case of the 4-vowel method, similarly to the case of the 3-vowel method, the repeated selection method can be applied to the input of aspirated and tense consonants, and this method is collectively referred to as the "4-vowel method for aspirated/hard consonant repetition selection" for convenience. In addition, as in the case of the 3-vowel method, it is possible to apply the repeated selection method in combination, and it is collectively referred to as the "four-vowel method using repeated selection with aspirated sound / hard sound control processing" for convenience.

The keypad of FIGS. 4-7 can also be solved and expressed as shown in FIGS. 4-8 from the viewpoint of the repetition selection method. Comparing Figs. 4-6 and 4-8, the difference between Figs. 4-5 and 4-7 can be clearly seen. 4-8 is the same result as the vowel element ":" selected with two strokes of the [0] button in Fig. 6 and Figures 4-8 are slightly different, but this can be unified). In addition, the vowel element ":" consisting of two dots can be applied by dividing it into a horizontal vowel element ":" and a vertical vowel element "..", and if you dare to name it, five vowel elements ("ㅡ" , ".", ":", "..", "ㅣ") can be called the "five vowel method". However, compared to the 4-vowel method of FIGS. 4-7, there are not many advantages in terms of input strokes, recognition ability improvement, etc., so they are not mentioned further in the present invention.

The vowel element "." and ":" can be assigned to the [*] button and the [#] button, but in this case, as shown in Figs. .

For example, input based on Fig. 4-7: ㅕ = : + ㅣ = [8] + [#], ㅑ = ㅣ + : = [#] + [8], ㅠ = ㅡ + : = [*] + [ 8], and when inputting the 8-button dropped consonant by the repeated selection method, ㅁ = [8]+[8], ㅎ = [8]+[8]. If the vowel element ":" is replaced with the vowel element "." If it is allowed to input with 2 strokes of this arranged button, "ㅎ" can be entered with 3 strokes of the button assigned with ".", as in the previous application.

As an input example, in the case of "wo" or "we", the dotted vowel element ".." between the vowels "ㅡ" and "ㅣ" can be entered as the vowel element ":". The system may recognize that you have entered "U + ..." temporarily, but since the vowel "ㅣ" cannot appear after "U", the system may recognize that you have entered "Wo". In the "10 consonant dot vowel element repeat selection 3 vowel method", in the case of "Wo", when entering a dot-shaped vowel element between "ㅡ" and "ㅣ", enter the vowel element "." twice or a vowel It can be understood as entering the element ":" once.

Some of the contents described above are explained again as follows. First, when inputting Korean on the keypad by applying the repeated selection method, the method using three vowel elements (ㅡ, ., ㅣ) uses 10 consonant plain sounds, three vowel elements, and two controls (warp, aspirated sound) ) A total of 15 elements are grouped and assigned in a 4*3 keypad to apply the repeated selection method, but grouping "3 vowel elements" and "2 controls and 1 consonant plain sound (9 button dropped consonants)" respectively it is assigned

The method using 4 vowel elements (ㅡ, ., :, ㅣ) is a repeated selection method by grouping and assigning 10 consonant plain sounds, 4 vowel elements, and 16 elements including 2 controls in a 4*3 keypad. However, "4 vowel elements" and "2 controls and 2 consonants (8 button dropped consonants)" are grouped and assigned respectively.

For the natural use of simple codes (especially syllable-based initial codes) in both methods, a case was shown in which 10 consonant plain sounds were assigned to 10 number buttons.

The 3-vowel method (collectively referring to the various 3-vowel methods titled above) and the 4-vowel method proposed by the applicant use various characteristics of a specific language (in this case, Korean) and have little or no ambiguity even when the repeated selection method is applied. It provides a way to enter. This is because in inputting the alphabet displayed on the keypad using the repeated selection method, especially in inputting Korean, among the "language restriction input methods" presented by the applicant in the previous application, the "repetitive selection method for Korean restrictions" among the "repetitive selection methods for language restrictions" It can be seen as suggesting a Korean input method optimized for ".

In fact, as suggested by the applicant in the earlier application, when a pair of basic consonants and basic vowels is assigned to each button in Korean, etc., and the repeated selection method is applied, the Korean consonant and vowel appearance rules (i.e., word generation rules, alphabet It is in the same context as showing that ambiguity in the iterative selection method can be greatly reduced by using the combination rule). In Figures 4-5 to 4-8 using three Korean vowel elements or four vowel elements, Korean vowels (elements) "ㅡ" and "ㅣ" do not appear consecutively, but appear consecutively (example of prior application In "ㅖ"), it is also understandable from a similar point of view that it is possible to select the consonant control and the vowel control assigned with the vowel element by the repeated selection method by using the property of knowing whether a vowel or a control is entered in "ㅖ"). can

4.1.3. Complete control processing 3-vowel method/4-vowel method and using the dropped consonant assignment button Complete control processing 3-vowel method/4-vowel method

In FIG. 4-5, even if the aspirated consonant and the tense consonant are input by the control processing method, ambiguity may occur in the case of "iheo <=> ahi" and "iheo <=> aheo <=> yahi" (both full codes values are all the same). In the example, the case where "ㅡ" is used instead of the vowel "ㅣ" is the same, and other similar cases will be known to those who know Korean. However, this case does not occur in many cases in actual words, and can be effectively overcome through the setting of the "battery delay time" and "other delay time" mentioned in the previous application. There may be a similar case in the 4-vowel method of FIGS. 4-7. In FIGS. 4-7, there is no case like "ahhe <=> yahi", but there may be cases like "and <=> yami". However, this is also not a common case and can be overcome through time delay. The number of occurrences can be investigated based on the frequency of actual use of Korean consonants and vowels, but since it is expected to occur in the form of Korean characters in hundreds of characters, it can be seen that there are virtually no cases where ambiguity occurs due to this.

Of course, as mentioned in the previous application, if you input the 9-button dropout sound ("ㅎ" in the example drawing) in the 3-vowel method as shown in Figs. It is possible. For example, heh = ㅇ + {aspirated consonant} = [8]+[*]+[*]. For convenience, this will be referred to as the "complete control processing 3 vowel method". Likewise, in the 4-vowel method similar to 5, the 8-button dropped consonants ("ㅎ" and "ㅁ" in the example drawing) are controlled by the method (as described, for example, "ㅁ" is converted to "ㄴ" in the modified alphabet) , "ㅎ" is regarded as a modified alphabet of "ㅇ") and can be entered without ambiguity. For convenience, it may be called the "complete control processing 4 vowel method".

However, inputting 9-button/8-button dropped consonants by the 3-vowel method / 4-vowel method of complete control hinders naturalness in relation to the use of simple codes. Therefore, in the present invention, it is proposed to input the 9-button dropped consonants ("ㅎ" in the example) in the 3-vowel method with a combination of buttons and controls assigned to the corresponding alphabet (applicable only to input after control, example description). For example, in the three-vowel method of Figures 4-5, heh = . + {aspirated consonant} = [0]+[*]+[*]. This is like a vowel element "." that inputs the 9-button dropped consonant with one stroke of the button to which the corresponding alphabet is assigned. It is entered like a modified alphabet of . This method can also completely remove ambiguity, and by using the [0] button to input "ㅎ", it is possible to maintain naturalness in the use of simple codes. For convenience, this will be referred to as "complete control processing using the dropped consonant assignment button". The same can be applied to the 4-vowel method. If this method is applied, the first letter of "ㅎ" ends with a letter with a seed sound (support) (eg "Gak"), and then when "ㅎ" is input, it can be temporarily recognized as "Go + ㅡ". However, since the vowel "ㅡ" + "ㅡ" cannot appear consecutively, the system can recognize that the user has selected the control, and the vowel element "." of "go" can be combined with the vowel control. Since there is no ".+ㅡ+ㅡ", the system can recognize it as "ㅎ". If the preceding letter ends with a vowel that can be combined with the vowel element "." In the value "0**", "0" is temporarily combined with the preceding vowel, and the system can temporarily recognize that the vowel "ㅡ" + "ㅡ" has been entered, but the system can similarly recognize the input value of "**" It knows that this control is selected, and since it cannot be combined with the preceding vowel element ".", the system knows that "ㅎ" is entered. Further, if the letter ends with a vowel that cannot be combined with the vowel element "." The system may consider it as inputting "ㅎ" and display it to the user. Also, even if "**" is entered after [0], it can be regarded as having entered "ㅎ" after all.

Here, it can be seen that the button assigned to the vowel "ㅡ" must be used as a control button for inputting the dropped consonant in the 3-vowel method (including the 4-vowel method) for complete control processing using the dropped consonant assignment button. As mentioned in the previous application, it is because the cases of "ㅔ" and "ㅖ" exist in Korean. The four-vowel method of complete control using the dropped consonant assignment button is also the same. Similarly, when "ㅁ" assigned to the [8] button in Fig. 4-7 is input, ㅁ = [8] + [*] + [*] can be entered. Full control processing using the dropped consonant assignment button Since the input case in the 4-vowel method is the same, it is omitted.

4.2. Temporary language restriction release delay time

In the previous application, it was said that "delay delay time" and "delay delay time" can be applied even when three or more alphabets are assigned to one button. For example, if the [2] button is pressed twice within 0.1 second by setting the hitting delay time to 0.1 second on the standard English keypad, the system can consider that B has been entered.

Likewise, when the [2] button is pressed three times in succession (i.e., [2]+[2]+[2]), the first input value and the second input value (i.e., the first [2] button and the second [2] button) If the delay time interval between is within the time set as the hitting delay time (eg 0.1 second), and the delay time interval between the second input value and the third input value is within the time set as the hitting delay time (eg 0.1 second) ( That is, [2] + within 0.1 seconds + [2] + within 0.1 seconds + [2]), and the system can recognize that C is entered. Or, when the [2] button is pressed 3 times in succession (i.e., [2]+[2]+[2]), if the total input time is within twice the delay time (e.g. 0.2 sec), enter C. You can also make the system recognize it.

The various delay times mentioned in the previous application and the main application are summarized as follows.

Continuous hitting delay time ≤ Hitting delay time ≤ Temporary language restriction release delay time

All three delay times may be set the same, but it would be preferable to set the delay time longer than the continuous hitting delay time, and the temporary language restriction release delay time longer than the other delay time.

4.3. Interaction between client system and server system

In the earlier application (filed in 2000 through claiming priority), it was said that the alphabet input program on the keypad could be loaded on the terminal (client) side or on the server side. In the case of being installed on the server side, the client side transmits numerical input values to the server side, and the server side interprets the input values. In the entire system consisting of a client (terminal) and a server, it was also possible to interpret the input value on the client side and transmit the character string to the server side. It is obvious that this can be similarly applied to all character input methods of the applicant.

4.4. Use of separate buttons other than 4*3 keypad

Previously, a method to perfectly process Korean input within the 4*3 keypad was presented. However, a vowel element or a part of a vowel element may be assigned using a separate button other than the 4*3 keypad. For example, in FIGS. 4-5, if the vowel element "." is assigned to a separate button, the dropped consonant "ㅎ" assigned together is selected as one stroke of the assigned button. Similarly, in Fig. 4-7, if the vowel elements "." and ":" are assigned to separate buttons (two can be placed on one button, or each can be placed on two buttons), the 8-button dropped consonant " ㅁ" can be selected with one stroke of the assigned button.

In addition, a separate button may be used, but an up movement button, a high movement button, or a left movement button, which are not frequently used in the text input mode, may be used.

4.5. Typing of the Korean Archaic Alphabet

The present invention goes further and proposes a method for inputting Korean archaic words through a keypad.

In Korean, archaic words (losing alphabets) that are rarely used in modern times, vowels are araeah (represented by "ㆍ"), consonants are half-chium (represented by triangle "ㅿ"), and soft hig (without a dot in "ㅎ") There are “ㆆ”), Yeeeeung (“ㅇ” with a dot on top and “ㆁ”), and Soongyeongeum (“ㅅ” with a circle attached on it and “ㅸ”).

Among the archaic words, the vowel lower ah is often used even in relatively modern words. For example, it can be seen in the trade name "ㄱ.ㅁ.goeul", and also in "ㅎ.ㄴgeul", a famous word processor made by Hangeul and computer companies (in "ㄱ.ㅁ.goeul", "ㄱ" +." is one letter, "ㅁ+." is one letter, and "ㅎ+.+ㄴ" in "ㅎ.ㄴwriting" is one letter, but the Korean Intellectual Property Office editor does not support downa, so it is written like this). As in the example, the vowel ariha is often used in various trade names, so it can be usefully used for input such as a phone book.

In the applicant's earlier application, the vowel anaerah has the same shape as the vowel element ".", so if the vowel element "." There is no case where another vowel appears consecutively after the vowel ariah, so the input rule does not change. . Of course, if the button to which the vowel element "." is assigned is pressed twice, the system can recognize that it is for inputting "ㅕ" or "ㅖ" rather than being input twice consecutively under the vowel. Likewise, if the vowel element "." is pressed twice in succession after the vowel "ㅣ", the system may recognize that the vowel "ㅑ" or the vowel "ㅒ" is input.

The consonants of old words can also be entered by considering them as modified alphabets of basic consonants (consonant plain sounds). For example, the half consonant "ㅿ" is regarded as a modified alphabet of "ㅅ" (eg, aspirated sound), and the soft heep "ㆆ" is regarded as a modified alphabet of "ㅇ" (eg, an aspirated sound or a hard sound), and the old one is "ㆁ" can be entered as a modified alphabet of "ㅇ" (aspirated consonant or tense consonant). The input method can also be defined in the case of the consonant sound "ㅸ" (e.g., automata processing that enables the combination of "ㅅ" and "ㅇ"), but it is an alphabet that is not actually used in modern Korean and is a modified alphabet of "ㅅ" Since both the hard consonant "ㅃ" and the aspirated consonant "P" exist in the present invention, it is not mentioned in detail any more in the present invention.

Just one example, you can enter "ㅸ = ㄴ+**** = 6****" or "ㅸ = ㄴ+#### = 6####". As mentioned in the input of various symbols, the control button is used repeatedly to input valid alphabets, but it is the same as inputting various symbols by repeatedly pressing the control button. It becomes "6*** = プ", but you can enter an archaic language (an archaic language as a modified alphabet of "ㅅ") with "6****". Likewise, by repeatedly using the control buttons (here, the [*] and [#] buttons to which the vowels "ㅡ" and "ㅣ" are assigned) will be able to input various symbols.

Entering consonants of Gore can be applied in the same way in other earlier applications of the applicant. However, in the method using the vowel elements (ㅡ, ., ㅣ) among the previous applications of the applicant, there is an advantage in that the vowel lower ah can be input naturally and easily.

Through the present invention, it is possible to input even archaic alphabets intermittently used in modern Korean through the keypad. Currently, even in the input method of Samsung Electronics in Korea using vowel elements, it is not supported to input the vowel lower ah. Therefore, in the present invention, it can be said that the biggest difference is that even in a relatively modern language, it is possible to input the vowel underah, which is used in a special case.

4.6. Characteristics when applying parallel input method

In the previous application, "shortened/full parallel input method" or simply "parallel input method" was explained. This is, for example, when applying the parallel input method with the full input method as the default input mode, the system examines the input value every time an input value is entered, so that the input value does not form the full code of the specific full input method. The moment the system recognizes it, the system regards the input value as a simple code and processes it (for convenience, this is called "full-priority parallel input method"). Or conversely, when applying the parallel input method with the short input method as the default input mode, the system examines the input value every time an input value is entered, and the input value no longer exists in the index of the simple code to be searched. The moment the system confirmed that it was not, the system considered the input value as full code and processed it (for convenience, this is referred to as "short-priority parallel input method").

It was explained that when using the "part-to-all selection method" as the full input method, it is easily possible to process the input value as a short code at the moment when the input value violates the full code generation rule in the full-priority parallel input method.

When the repeated selection method is applied as the full input method, it is not known explicitly whether the input value violates the full code in the full-priority parallel input method. However, when applying the language-restricted iterative selection method as a full input method, the moment the input value violates the word generation rule of a specific language, the system can treat the input value as a short code and process it.

In the method using the three vowel elements (ㅡ, ., ㅣ) of Korean (examples in Figures 4-5), the syllable-based initial code is used as a short code (ie, used in the index of the simple code to be searched Simple code means syllable-based initial code) When applying the full-priority parallel input method, when “12~” is input as an input value, the moment the second input value “2” is input, the input value forms a Korean syllable (letter) Since the system cannot recognize that the full code cannot be achieved, the system can treat the input value as a simple code. Anyone who knows Korean can easily recognize it, but when the user enters a simple code (syllable-based initial code) when applying the full-priority parallel input method in a form similar to Figure 4-5, in most cases the second input value It has a good characteristic of knowing that the input value is a simple code the moment it is input.

This is also in the same context as the system treats the input value as a simple code (short code) the moment the input value violates the Korean word generation rule in the Korean restricted input method using three Korean vowel elements. In Figures 4-5 using three vowel elements in Korean, when "100~" is input as an input value (full-priority parallel input method), the system uses "a + .." can be recognized as input and outputted, but if the fourth input value is a number button without the vowel element "ㅡ" or "ㅣ" input, the input value cannot form a full code. At that moment, the input value is recognized as a simple code (short code), and the phrase corresponding to the input value can be output (visual means or auditory means) by referring to the simple code index. Eventually, when the full-priority parallel input method is applied in a form similar to FIG. city).

Similarly, in FIG. 4-7 using four vowel elements (ㅡ, ., :, ㅣ), when the full-priority parallel input method is applied, when the user inputs “18~”, the system responds with “go” or “go” In order to input "a+.", it can be recognized and outputted, but if a number button (corresponding to a consonant) is entered as the third input value, the input value cannot form a full code, The system can treat the input value as a simple code. When a maximum of three buttons are input, the system has a good characteristic of being able to know whether the input value is a full code or a simple code (when applying the 4-vowel method of aspirated/inspired control processing).

In Figs. 4-5 and 4-7, the assignment of each number button of the basic consonant (consonant plain sound) is different, but since Fig. 4-5 and Fig. 4-7 are only examples, the arrangement of consonant plain sounds can be kept the same. can In Fig. 4-5, "ㅎ" was implicitly assigned to the [0] button, and in Fig. 4-7, the vowel element "." . For convenience, similar to Fig. 4-5, the input method using three vowel elements is called "3 vowel Korean input method (more simply, 3 vowel method or 3 vowel method)", and similar to Fig. The input method using vowel elements is referred to as "4 vowel Korean input method (more simply, 4 vowel method or 4 vowel method)".

4.7. Compatibility between 3-vowel method keypad and 4-vowel method keypad and application to memorization keypad and general keypad displaying only numbers

Although the buttons to which the basic consonants are assigned are slightly different in the keypad of Figs. 4-5 and the keypad of Fig. 4-7, the basic consonant arrangement of both can be the same. (eg, the method described in Fig. 4-5) or the 10 consonant 4 vowel method (eg, the method described in Fig. 4-7). ) is there. Furthermore, the user can use the 10 consonant 3 vowel method or the 10 consonant 4 vowel method in the "memorization" keypad in which Korean consonant plain sounds are assigned to each number button. Going one step further, users familiar with the 3-vowel method or 4-vowel method will be able to use simple codes and input Korean by the 3-vowel method or 4-vowel method even on keypads where consonant plain sounds are not displayed on the keypad. Using a simple code on a keypad displaying only numbers or a keypad displaying only consonant sounds on 10 number buttons for memorization, and using Korean input by the 3-vowel method and 4-vowel method are within the scope of protection of the applicant's invention. Inclusion is self-evident.

4.8. Entering dropped consonants

When applying the complete control processing method as a method of inputting the dropped consonant "ㅎ" in the three-vowel method in the previous application (applying input after control), input without ambiguity as "ㅎ = 0** = .ㅡㅡ = ㅗㅡ" said it could be done. In addition, by improving this, it was possible to input with one stroke of the [0] button when the dropped consonant "ㅎ" appears at the beginning of the word (since the vowel element '.' does not appear at the beginning of the word). In addition, vowels that cannot be combined with the vowel element "." He said that "heh" can be entered with one stroke of the [0] button.

When entering "ㅎ" with 3 strokes of the [0] button, the vowel element "." It was pointed out that in the case where "ㅎ" comes after this combinable vowel ('.combinable vowel'), ambiguity may occur, such as "heh <=> aheo <=> yahi" as described above, and ambiguity In order to enter without, it was said that "ㅎ = 0**" or "ㅎ = 0*" can be entered by applying the complete control processing method. In addition, when inputting without ambiguity, it is recommended to input "0**" rather than "0*" for the regularity of the input method. Here, in inputting the dropped consonant "ㅎ", when applying the repeated selection method using the button assigned to the dropped consonant, "." It can be seen that ambiguity can arise only in special cases. Conversely, if "ㅎ" comes after a consonant, you can enter "ㅎ" without ambiguity by pressing the [0] button three times. That is, when "ㅎ" is input after a consonant, "ㅎ" can be input without ambiguity even if either method of "0**" or "000" is applied.

Here, if "ㅎ" comes after ".combinable vowel", it can be seen that "0*" can be input. (If 'ㅎ' comes after an uncombinable vowel, you can input it with one stroke of the [0] button.) This is because ".+ㅡ" is never combined after ".combinable vowel" in Korean.

Summarizing the above, in order to make the input of the dropped consonant "ㅎ" as convenient as possible, when "ㅎ" appears at the beginning of the word and after ".uncombinable vowel", enter it with one stroke of the button assigned to the dropped consonant, "ㅎ" after "combinable vowel" can be entered as "0*" or "0**", and when "ㅎ" appears after a consonant, it can be entered as "000".

Of course, for the regularity of the input method, you can always input "ㅎ = 0**". At this time, it is also possible to coexist with the input method of "ㅎ" summarized above. For example, "0 = ㅎ" at the beginning of a word, then "0* = ㅎ" when "*" is pressed, and "0** = ㅎ" again when "*" is pressed once more. It will be. Here, if “*” is pressed more, “0*** = huh” becomes, and if “*” is pressed more, “0**** = huh”.

Similarly, after pressing "0*" to input "ㅎ" after ".combinable vowel", if "*" is pressed again, the same "0** = ㅎ" (the input method is the same as '0 ** = ㅎ'), if "*" is pressed again, it may become "0*** = h".

It is self-evident that the above information can be equally applied to the case of using the three Korean vowels (eg "ㅡ", "아", "ㅣ"), which will be described later, and the same applies to the following. In addition, inputting "ㅎ = .+ㅡ+ㅡ = 0**" is made in the shape of "ㅎ = ㅗ + ㅇ", and it is said that it is to be able to input as if writing "ㅎ". Furthermore "." Even when entering "ㅎ" after a vowel that can be combined with (such as "a" when using three vowels in Korean) is entered, "ㅎ = .+ㅡ+ㅡ" is input for consistency of the input rule. For the user's convenience, when up to ".+ㅡ" is input, it can be displayed as "ㅗ". For convenience, this is called "ㅎjungㅗ input". As a standard, if "gihi = 1#0**#" to "1#0" is entered, "ga" is displayed, and if "*" is entered once more, "gaㅡ". However, as mentioned above, "ㅎ If you apply “entering middle”, when up to “1#0*” is entered, “Ki” is displayed and if “*” is pressed once more, “Ki (‘ㅎ’ is the base in unicode, in KSC5601 'ㅎ' becomes the first consonant of the next letter)" and if "#" is pressed more, it becomes "gihi". The difference is that the vowel ending in "." When "ㅡ" is entered after being input, "." entered right before "ㅡ" and "ㅡ" is recognized and processed as a vowel "ㅗ". "1#0* = Kiㅗ" is entered Then, when the delete button is pressed, it can be set to “Ga”, which is the state of “1#0.” This is the same as entering “ㅎ = .+ㅡ+ㅡ”, except that the form displayed in the middle of the input is different in a special case. .

To make the above a little more general, it is defined as inputting in combination with "ㅗ = X + Y" in a specific input method, and "X" entered after a series of vowel inputs is the promised If a specific grapheme (vowel) is formed and then successively input "Y" does not form the promised specific vowel, the finally input "X + Y" is recognized and processed as the letter vowel "ㅗ". "X" may be a vowel element "." as shown in the example, or may be "a", "sh", "TT", ..., etc., as in the method using three Korean vowels described later, , "Y" can be "ㅡ".

From the above results, it can be seen that if "ㅡ" is input after the letter vowel "ㅗ" is input, "ㅗ+ㅡ" is processed as "ㅎ". That is, inputting "ㅎ" using the [0] button to which "ㅎ" is assigned at the beginning of a word is not applied, and after entering "ㅗ" as "0*" in the word start state, "ㅡ (= *)" is input, "0**" can be recognized as "ㅎ" and processed. Going one step further, if "ㅇ" is input after the letter vowel "ㅗ" is input, "ㅗ (letter vowel) + ㅇ" can be recognized and processed as "ㅎ". Also, since "ㅗㅇ" is not a normal Korean character, the combination of "ㅗㅇ" is treated as "ㅎ". However, when "ㅗ" is not a vowel, as in a word such as "study", "ㅗ + ㅇ" does not become "ㅎ". In the case of "gihi" as exemplified above, it becomes "1#0* = giㅗ", so if "ㅇ (= 8)" is entered in succession next time, "gihee ('ㅎ' is the base in unicode, in KSC5601 'ㅎ' becomes the first consonant of the next letter)", and if "ㅣ (= #)" is input again, it can be recognized and processed as "gihi". In the example, "ㅎ" was input, but any character element can be input by the above means. However, it would be natural to enter "ㅎ", which is geometrically related.

Although the 3-vowel method was mainly explained above, the 4-vowel method can also be applied to the input of dropped consonants in the same way. In entering "ㅁ" assigned with ".." to the [8] button in Figures 4-7 and 4-8, when the dropped consonant "ㅁ" comes at the beginning of the word, enter it with the corresponding button [1]. , and the vowel element ".." assigned together cannot be combined (that is, vowels and vowel elements except for the vowels 'ㅡ' and 'ㅣ') followed by "ㅁ", press the [8] button 1 stroke that can be entered. Likewise, if the consonant followed by the dropped consonant "ㅁ", you can enter "ㅁ" without ambiguity with two strokes of the corresponding button. In addition, if the missing consonant "ㅁ" comes after the vowel that can be combined with the vowel elements assigned together, "8*" can be entered. Of course, even in the case of the 4-vowel method, application of the complete control processing method simply using the dropped consonant assignment button and application of the control processing method of considering the dropped consonant as a modified alphabet of other basic consonants (aspirated or tense) are applied in the input of dropped consonants. It is possible.

In addition, in the input of symbols, it is possible to apply the control processing method using basic consonants that do not have aspirated / tense consonants.

4.9. Symbol input example

In the input of symbols, as much as possible, a combination of buttons assigned to basic consonants without aspirated / aspirated consonants and vowel element buttons (in particular, "ㅡ" and "ㅣ" buttons that can be used like control buttons) to be input it would be convenient That is, it can be seen as applying the aspirated/hard sound input method.

For example, various symbols can be input as follows based on FIGS. 4-5, and the following information is already presented in the previous application, and not only in the character input method proposed in the present invention, but also in other character input systems. It is obvious that it can be applied similarly (ie, using the control processing method).

▶ Exclamation mark (!) = 2** : Can be easily recalled from "Neu = 2*..." of "exclamation mark"

▶ Slash (/) = 2## : Can be easily recalled from "I = 2#..." in "Division"

▶ Tilde (~) = 4**: Reminiscent of the wavy shape in the shape of the letter "ㄹ" and the pronunciation of "LE"

▶ Golbaengi (@) = 4##: Reminiscent of "ㄹ+ㅣ" in the loop shape of the "@" symbol

▶ Question mark (?) = 5** : Can be easily recalled from "Water = 5*..." of "Question mark"

▶ Period (.) = 5## : Easy to associate with "Ma = 5#..." of "period"

▶ Comma (,) = 5###: Press “#” once more after entering “period”

▶ Colon (:) = 5#### : Press "#" once more after entering "comma"

▶ Semicolon (:) = 5##### : Press “#” once more after inputting “colon”

If the [*] button or the [#] button is not used as a vowel button in a character input system, it is possible to input an exclamation point by combining the button assigned to "ㄴ" with a control button (eg [*] button). will be. Even in an input system in which the [*] button or [#] button is used as a control button rather than a vowel button, as described in the police tone input, repeated pressing of the button assigned to "ㄴ" and the control button is required even in a system where the control button is used as a control button. Combinations of exclamation marks can be entered. For example, if you input modern language that takes precedence over archaic language, and a button assigned to "ㄴ" and an arbitrary control button (e.g. [*] button) are pressed up to two times, enter "exclamation mark = ㄴ+***" It can be.

Period (.) + "ㅣ" = comma (,), which also uses the property that the vowel "ㅣ" cannot be normally combined after a specific symbol (period in the example). If you want to input the vowel "ㅣ" after the period, enter "ㅣ" after entering the period (.) and confirm the period by allowing a certain amount of time (e.g., the language restriction release delay time) to elapse. After inputting (.), press a specific button (eg right arrow or 'space + delete') to confirm the period, and then input the vowel "ㅣ" to enter ".ㅣ". This is also the case for the input of the above-described archaic Hangul.

It is self-evident that symbols other than the exclamation mark above can be similarly applied in other input systems (a combination of buttons and control buttons assigned with recognizable Korean consonants), and input of various other symbols as an extension of the above. this is possible

Above, examples of symbol input optimized for the Hangul input method proposed in the present invention have been shown. That is, various symbols are input using consonant buttons and vowel buttons (buttons to which vowels "ㅡ" and "ㅣ" are assigned) where there is no aspirated / tense sound as much as possible. However, as shown in the previous example of inputting pure hard sound "ㅸ = 6****" or "ㅸ = 6####", even using the consonant button with aspirated / hard sound, archaic letters or various symbols can be entered.

Furthermore, as in the cases described in 10 and 11 below, even when the vowel button is repeatedly pressed and various vowels are selected/input, symbols, etc. can be input. For example, in Fig. 4-5, when "ㅡ" is selected with 1 stroke of the [*] button to which vowel "ㅡ" is assigned, "TT" is selected with 2 strokes, and "ㅠ" is selected with 3 strokes (i.e., vowel In the case of "ㅡ", "TT", and "ㅠ" being selected according to the number of repeated presses of the corresponding button), "5*** = mu".

Usually, in the method in which a specific grapheme is selected by repeatedly pressing a specific button, "maximum possible repetition" (eg, when the [*] button is pressed 3 times) again in the first state (ie, when pressed once, "ㅡ" becomes In many cases, the selected state is cycled, that is, "5**** = M". This is mainly in consideration of the case where it is pressed more than the desired number of times due to a typo (however, this is the applicant's It is sufficient to use the deleting function of the input value unit suggested in the previous application) or "5**** = 5*** + * = mu-". As shown in the input, the system detects that an uncombinable alphabet (vowel) is input, and the entire input value can be recognized as one specific alphabet (eg, corresponding grid sound, archaic word, or specific symbol).

In other words, in this case (when the vowels "ㅡ", "TT", and "ㅠ" are selected according to the number of repeated presses of the corresponding button in the order - where three vowels are actually displayed on the [*] button and some vowels (eg, including all cases where only the vowel "ㅡ") is displayed), "question mark (?) = 5****" can be entered. When the [*] button is pressed consecutively after "5****", when [#] is pressed after a period (.) in the example above is entered, a series of symbols (in the example above , comma (,), colon (:), semicolon (;), etc. in a broad sense can recognize various alphabets), and can be recognized as promised symbols. Therefore, as a non-symbol example, the grid sound "ㅋ = 1****" and "key = 1*****" may be input.

This allows the promised "ㅡ", "TT", and "ㅠ" to be selected according to the number of repeated presses of the [*] button to which the vowel "ㅡ" is assigned, and in addition, "Symbol Control 1", It can be seen in the same context as making "Symbol Control 2", "Symbol Control 3", ... selected. That is, it is the same as "5+{Symbol Control 1} = 5**** = question mark (?)". Similarly, according to the number of repeated presses of the [*] button to which the vowel "ㅡ" is assigned, the promised "ㅡ", "ㅜ", and "ㅠ" are selected, and in addition, "2nd" and "3rd" are selected according to the number of consecutive repeated presses. ", "5th"... etc. is the same as making sure subsequent controls are selected. For example, "5+{2nd} = 5**** = question mark (?)". In other words, the [5] button has "ㅁ" as the representative alphabet and "?" is implicitly determined as {2nd} successor alphabet. This can be seen in a similar context to the case of using a vowel button as a control button, as suggested in the applicant's previous application (the application number is not necessarily specified).

If the button to which the vowel "ㅡ" is assigned is used only as an input of "ㅡ", the maximum possible repetition of the vowel "ㅡ" following the consonant is 1, so input as "question mark (?) = 5**" This can be seen as possible. By expanding this, even when the maximum possible number of repetitions is one or more (three times in the example above), various symbols can be input. Of course, even if the symbol is not recognized in combination with the consonant button, only the input of the vowel button can be recognized as a symbol. For example, if three vowels are entered like "ㅡ", "ㅜ", and "ㅠ" by repeatedly pressing the [*] button to which "ㅡ" is assigned, "5**** = ?" without "**** = ?" As a result, a specific alphabet (eg, symbol) can be recognized. However, this is not a good method because only one symbol and the symbols promised when the [*] button is continuously pressed can be input using the [*] button. In the case of recognition as a combination with a consonant button, combinations with other buttons (e.g., number buttons assigned with consonants) as well as combinations with the [5] button in the example can be recognized as a specific symbol (alphabets are also possible). It is obvious that the input of various symbols can be implemented with a small number of input strokes.

As the above mentioned in the previous application by the applicant, it can be seen as using the button to which the vowel is assigned as a control button, and the control button can be input first or later according to the input rules. That is, it can be entered as "question mark (?) = 5**" or as "**5". For example, if "**5" is entered after "A" is entered, the moment the last "ㅁ" is entered in "Ga+ㅡ+ㅡ+ㅁ", the system recognizes the input value as "A?" do. If "**5" is entered after "gam", the moment the last "ㅁ" is entered in "Gamuㅡㅁ", the last input "5**" can be detected and the input value can be recognized as "gam?" have. The same goes for the rest.

To summarize the above, in the method in which a certain vowel button is used repeatedly and a certain alphabet is selected according to the number of presses, the system detects the moment when the vowel button is input more than the maximum possible repetition number and inputs a series of vowel buttons pressed. A combination of a value and a specific (consonant) button (a series of vowel buttons can be input first or second, depending on what is decided) is processed as an input of the promised alphabet (symbol).

This can be applied to various function inputs as well as alphabets (including symbols). When applied to the input of functions, as shown in the "multidimensional cross control processing method" of the previous application of the applicant (when inputting alphabets with N-dimensional cross control processing method, inputting functions by cross combination of control buttons N+1 times) , It is desirable to set the input of a specific function so that various alphabets (symbols, etc.) are input by repeatedly pressing the control button, and to be done at the end. (eg. 5**** = question mark (?), 5***** = exclamation mark (!), 5****** = activate the enter function)

If "5***** = Enter function activated" and "5****** = exclamation point (!)", enter function is activated by "5*****" and [*] again When the button is pressed, the system invalidates (cancels) the executed enter function and interprets the entire input value "5******" as an exclamation point (!), which is unnatural in terms of implementation and confusing to users. to be. This means that when the vowel buttons used as control buttons are used up to N times when inputting various alphabets (including symbols), it is desirable to input the function using repeated pressing more than that (ie, N + 1 times) to be.

4.10. Input of an arbitrary vowel (e.g. vowel "A") using the vowel element "."

It was shown that the archaic word "araeah" can be naturally input by using the vowel element "." The vowel element "." is similar to Haerah in terms of shape, so it can give users a sense of familiarity. When entering the vowel element "." below, in the vowel combination process (i.e., vowel processing process), from the start of vowel combination (eg, after entering a consonant) to the end of vowel combination (eg, input the next consonant or space, etc.) If only the [0] button is pressed during the activation of a function that is present), it is processed as below.

Basically, inputting vowels using vowel elements is to form a certain single vowel with a combination of vowel elements. The vowel combination process means from the start of vowel combination to the end of vowel combination. The vowel combination start state means after a consonant is input, after a function such as a space is activated, or when it is recognized that the currently input vowel is not combined with a previously recognized vowel. For example, when "*" is pressed in the vowel input value "1#*... = Kiㅡ ...", the vowel element "ㅡ" is combined after the previously recognized vowel "ㅣ" to create another single vowel. cannot be formed, so it is recognized as a new vowel combination start state. Likewise, the vowel combination end state means when a new consonant is recognized, when function activation such as a space is recognized, and so on. In the description example below, for convenience, the vowel combination process between consonants (from the start of vowel combination to the end of vowel combination) is described as an example.

For example, "105 = a + . + ㅁ" will be one letter with the lower ah as a vowel. When "1" is pressed to recognize a consonant and then "0" is pressed, the system primarily recognizes the start of the vowel combination process. For the input value "10~", the system returns "a+." (Process of entering "geo", "braff", "go", or "gyo"). However, when it is recognized that "5" is pressed to start the consonant processing process and end the vowel combination process, the input value "0" can be processed as below. That is, the input value “105” is recognized as “a => a+. => a+.+ㅁ”. Here, what is represented by using the "+" symbol means that it appears as a single letter with the old word araeah (ie, '.') as a vowel.

Among the three vowel elements "ㅡ", ".", and "ㅣ" used in the 3 vowel method, "ㅡ" and "ㅣ" exist as vowels by themselves, but only the vowel element "." is combined with other vowel elements, Represents Korean vowels. Here, it is shown that by using the vowel element ".", it is possible to input a single vowel (eg, "a") that is frequently used in modern Korean without inputting araeah, which is rarely used in modern Korean.

In inputting a modern Korean single vowel using the [0] button to which the vowel element "." is assigned, it is recommended to input the modern Korean vowel "a", which is the most frequently used and has a similar (actually identical) pronunciation to Haerah. would be preferable

Entering the vowel "a" with the button to which the vowel element "." is assigned is similar to inputting the word "a" with the button to which the vowel element "." is assigned. For example, when "105" is input and "1" is pressed, the system recognizes it as a consonant "a", and then when "0" is pressed, the system primarily ('0**' or '000' If it is input, it becomes a consonant processing process), so the vowel combination process is performed. Similarly for the input value "10", the system returns "a+." ) It can be recognized as an intermediate step of entering "geo", "chicken", "go", or "gyo", but if the next consonant input "5" is entered (or a space that can end the vowel combination process and activation of other functions), the system can recognize the input value “0” as the promised vowel “A” after the vowel combination process is finished. That is, the input value “105” is recognized as “a => a+. If another vowel (eg 'ㅣ') is input here, it is obvious that the entire input value becomes "105# = kami".

The exemplified process of "105 = gam" is actually the same as the process of "a => ki => ga => gam" for "1#05". If "5" is pressed after "1#0", the end of the vowel combination process is recognized and the vowel "A" is determined for the input value "#0". However, when "a = ㅣ+. = #0" is input, the system outputs according to the input value is similar to the process of writing the vowel "a", so it only gives the user a sense of familiarity.

It is true that entering the frequently used vowel "a" as the vowel element "." is less natural in terms of naturalness than inputting the vowel elements "ㅣ" and "." sequentially. However, the vowel element "." At the same time as entering the vowel "A" only, it is not a problem because you can also enter "A" as a combination of "ㅣ" and "." (that is, '#0' in the drawing).

Here, the input of Gore Ahahah can be input as "00". For the same example, if "100" is pressed, the system enters "a+.+." However, if the vowel button that can be combined with the next input value does not come and the activation of other functions that can give the end of the consonant or other vowel combination process is recognized, the system converts “100” to “a + haerah”. come to recognize "1005" = "a + below ah + m" is recognized. Again, if there is little need for input of gore words, other vowels such as the frequently used vowel "o" can be input with two strokes of the [0] button.

Depending on the user, the vowel element "." may be less preferred due to lack of intuition about the point of inputting "a" without inputting lower ah. For these users, it is possible to input the lower ah with one stroke of the [0] button, and input the vowel "a" with two strokes of the [0] button. Since the process is the same as described above, it is omitted. Even in this case, it will be possible to input "A = ㅣ +. = #0" at the same time. Entering the vowel "a" with two strokes of the [0] button (i.e. '00') to which the vowel element "." is assigned is also more convenient than entering "ㅣ+. = #0" in terms of input convenience. degree is high

The button to which the vowel element "." presented above is assigned (the [0] button in the example drawing) determines whether to input "A" with one stroke or enter Gore Ahah with one stroke and enter "A" with two strokes. It can be set according to the user's preference. Furthermore, it is also possible to input a vowel other than "A", and this will also be set by the user.

Since the vowel "a" is overwhelmingly used in Korean, it is preferable to enter "a" rather than other vowels in enabling the input of any vowel used in modern languages using the vowel element "." . The vowel "a" has a frequency of use of about 22% of all Korean vowels. In addition, if the frequency of use is in order of "a", "ㅣ", and "ㅡ", these three vowels account for about 50% of the total frequency of use in Korean. In other words, by enabling the input of "a" as the vowel element ".", it means that about half of the actually used vowels can be input with one specific button, respectively.

Although the three-vowel method has been described above, the same can be applied to the four-vowel method. That is, in the vowel combining process (vowel combining start ~ vowel combining end) in Figs. If only is recognized, it can be processed as a promised vowel (eg 'A'), and when the vowel element ".." is recognized (ie, pressing the [8] button), it can be treated as another promised single vowel (eg, below or 'ㅇ') can be processed. In addition, it goes without saying that it can be applied to an input system using vowel elements currently used in Korea.

Since the vowel combining process means from the start of vowel combination to the end of vowel combination, other vowels cannot be combined in addition to these vowel inputs. This means that you cannot enter "dog" by entering the vowel "ga" with "10" and combining it with the vowel element "ㅣ". "10#" becomes "sh" because the vowel combination process started when "0" was input and the vowel combination process continued when "#" was pressed. In other words, the above description can be applied only to vowel inputs used alone, not to vowels in which additional vowel elements are combined and changed (eg, vowel "a" or "ga + end of word" in "gam"). in "A").

Among the vowel elements, the vowel element ".", which originally does not exist as a vowel by itself, exists as a vowel element and as a vowel alone, but is a vowel that can be additionally combined with a vowel element (or a vowel by itself). As a vowel created by combining "ㅡ", "ㅣ" and vowel elements that exist as "A", "ㅑ" ..., vowels that can be additionally changed by combining vowel elements) are "element collections" It is called. Here, "ㅡ" and "ㅣ" are both vowel elements and element collections at the same time.

In the above, a vowel is input using the Korean vowel elements "ㅡ", ".", and "ㅣ", but processing the input of the [.] button that starts the vowel combination as "a", and the [.] button It has been described that the processing of "o" for pressing twice is described. Since the Korean keypad in the present invention has compatibility, the contents applied in the vowel input using three modern Korean vowels (eg "a", "ㅣ", "ㅡ") in (4.11) can be additionally applied. can That is, "ㅘ = .+ㅡ+." As a result, "ㅙ = .+ㅡ+.+ㅣ", "ㅝ = ㅡ+.+.+.", and "ㅞ = ㅡ+.+.+.+ㅣ" can be entered.

4.11. Vowel input method using 3 vowels of modern Korean (e.g. "a", "ㅣ", "ㅡ") and Korean input system using the same

The most used vowels in Korean are said to be three vowels in the order of "a", "ㅣ", and "ㅡ". In particular, the vowel "A" is the most used vowel. Hereinafter, a method of processing Korean vowels using three vowels including "ㅡ", "ㅣ" and one arbitrary vowel (in the example, the vowel "A") is shown. As introduced in the previous application, 13 alphabets of 10 flat consonants and three vowels "a", "ㅣ", and "ㅡ" of Korean are used as basic alphabets, so in a keypad equipped with 12 buttons, one consonant per button and an example of having one vowel is exemplified. However, apart from these examples, combining and processing the following vowels is different (various consonant input methods suggested in the previous application, consonant input methods in other systems, as well as any new consonants to appear in the future) Input method) can also be applied in the same way. It is obvious that the contents mentioned in other chapters of the present application below are also applicable to the following.

Considering the invention in the previous application, FIGS. 4-10 and 4-11 are cases in which the vowel "a" and the consonant "ㅎ" are provided in one button. In Fig. 4-10, in order to keep the keypad concise, the vowel "a" is displayed in the number "0" of the [0] button, which has the same meaning as in Fig. 4-11. In the case of FIGS. 4-10, the vowels "ㅡ", "아", and "ㅣ" can be selected/input by the [*] button, the [0] button, and the [#] button, respectively. Of course, this is just one example, and it is easy to see that variations are possible. For convenience, below [*] button [*] button or vowel "ㅡ" button, [0] button [0] button or vowel "A" button, [#] button [#] button or vowel "ㅣ" button let's call it In particular, the [0] button assigned with the consonant "ㅎ" is also called the "ㅎ" button in some cases.

In the following, since the [0] button in FIGS. 4-10 and 4-11 is primarily applied as the "A" button, the consonant ("ㅎ" in the example drawing) is not assigned to the button to which "A" is assigned. Same if not. It can also be applied when a consonant is assigned to the remaining vowel buttons or when assigned with an arbitrary control. However, the input of the consonant assigned together with the vowels "ㅡ" and "ㅣ" must not affect the input of the vowel ("ㅋ = ㄱ+ㅡ+ㅡ = 1**" input is "consonant + ㅡ" Next, it uses the property that the vowel "ㅡ" does not appear consecutively and does not affect the input of the vowel as a result - as mentioned, it is a property that is treated as "critical").

In the following, Table 1 shows an example of inputting the remaining vowels using the three vowels proposed in the present invention.

For the contents of Table 1, input Korean vowels using three vowel elements "ㅡ", ".", and "ㅣ", but "." It is the same as entering the vowel "A" with one stroke of the assigned button. For example, in Table 1, it is defined as "TT = ㅡ + A", which uses the property that the vowel "A" does not appear consecutively after the vowel "ㅡ" in Korean, so that the entire input value ("ㅡ + ") can be considered as the vowel "TT" defined so that the system recognizes it. In the case of the vowel "ㅐ", it is decomposed into "ㄴ" and "ㅣ", so it may be natural to enter "0#", but since the vowel "sh = 0#" is defined, "ㅐ = #0# It is defined to be entered as ". It is similarly conceivable to define combinations for the rest of the vowels. According to the definitions in Table 1, 21 Korean vowels can be entered without ambiguity.

When a corresponding input value among the input values in Table 1 is detected in a state in which a vowel processing process (ie, a vowel combination process) is initiated by recognizing that any one vowel button in Table 1 is pressed, the system identifies the corresponding vowel. do. For example, after one of the consonant buttons [1] to [9] in Figure 4-10 is pressed, or after input of a consonant is recognized as a series of inputs (eg, "1** = ㅋ" ), when one of the vowel buttons ([#], [0], [#] buttons in Fig. 4-10) is pressed, the system recognizes that the vowel processing process starts and the input of the corresponding vowel button and subsequent By detecting input of a series of input values (vowel buttons), it is possible to identify vowels corresponding to the corresponding input values according to Table 1.

However, in the case of a collection marked with a circle indicating whether (vowel) can be confirmed (available) in Table 1, it can be confirmed that it is a corresponding collection with respect to the input of the corresponding input value, but other collections can be made according to the following input values. have. For example, if "0#" is pressed, the system can recognize the input of "o" according to Table 1, but if "#" is pressed one more time, the system returns the entire input value "0#". #" is recognized as the vowel "ㅔ". In Table 1, there is no case where another input value is added after "0##" so that the system recognizes the entire input value as another input value, so the system converts the input value "0##" to the vowel "ㅔ". can be definitively recognized.

" 혹 은 "ㄱㆍ" 혹은 "ㄱ@" 혹은 "가" 등의 형태 중의 임의의 한가지로 출력될 수 있다. 다음 입력으로 자음버튼이 입력되거나 자음의 입력이 인식되면(예를 들어 "1" 이 추가로 입력), 전체 입력값 "101"에서 중간에 입력된 "0"을 모음 "ㅏ"로 확정적으로 인식하고, "각"을 출력할 수 있는 것이다. 여기서 "ㅏ = 0" 으로 입 력하도로 하였으나, "#0" 으로 역시 "ㅏ"를 입력할 수 있도록 하는 것을 허용할 수 있다. Similarly, in the case of vowels not circled in the confirmed (available) column in Table 1, they can be recognized as other vowels according to the following input values. The vowel "A = 0" can also become a vowel such as "sh", "ㅕ", "ㅗ", "ㅛ", ... according to the following input, so if the vowel [0] button was pressed after the consonant (e.g. "10"), the output format is "a"

It can be output in any one of the forms such as " or "ㄱㆍ" or "ㄱ@" or "가". When a consonant button is input as the next input or a consonant input is recognized (for example, "1" With this additional input), "0" entered in the middle of the entire input value "101" is definitively recognized as the collection "A", and "Gak" can be output, where "A = 0" is input. However, it is possible to allow "#0" to also input "A".

") 하여 줄 수 있으며, 확정적으로 인식되는 순간 다시 적절하게 표시(예. "각")하여 줄 수 있는 것이다. 마찬가지로 "10"이 입력된 후 단어의 종료(예. 공백, 입력의 종료 등)가 인식되면, 시스템은 기 입력 된 "10 = 가"로 확정적으로 인식할 수 있는 것이다. 표1에서는 일부의 경우만 입 력중 출력형태를 예시하였다. Here, the problem of the system "recognizing" the corresponding collection for a specific series of input values (including all cases of temporarily recognizing and definitive recognition) and "outputting" the recognized content (e.g., displaying on liquid crystals) are completely separate. is the problem of (Depending on the system, there may be cases where it is not necessary to output the recognized contents, and whether or not to output the recognized contents is an optional matter) Regarding the temporarily recognized contents (recognized vowels in this case), example As described above, output in an appropriate form (e.g., "a

"), and as soon as it is recognized definitively, it can be displayed appropriately (eg, "each"). Likewise, after "10" is entered, the end of the word (eg, blank, end of input, etc.) If is recognized, the system can reliably recognize the already input “10 = 가” In Table 1, the output form during input is illustrated in only some cases.

11-1 is a diagram presented in the previous application of the applicant, in which the input value input through the keypad in the terminal (client) is interpreted by referring to the memory in the control unit (controller), and the interpreted result (string) is displayed on the display unit ( display unit) or transmitted to the server side through the sender. The problem of displaying the interpreted character string on the display unit (eg, liquid crystal, etc.) and the problem of transmitting it to the server side are optional problems separate from the process of interpreting the input value. Even in the hardware configuration, it is a problem that may have including from the control unit to the memory, unlike the example drawing, and is not absolute. 11-2 is also a diagram presented in the previous application, and shows an example of transmitting an input value from the client side to the server side and interpreting the input value on the server side.

Here, it is also possible that the right arrow "→" is applied instead of the vowel "ㅡ", and the down arrow "↓" is applied instead of the vowel "ㅣ", giving a similar effect. In <Table 1>, the arrows "→" and "↓" can be applied instead of the vowels "ㅡ" and "ㅣ" respectively. Instead of the vowels "ㅡ" and "ㅣ", it would be better in terms of user friendliness if the vowels "ㅡ" and "ㅣ" are displayed rather than "→" and "↓" respectively displayed on the keypad buttons. This is the same in the "vowel input method using four vowels" to be described later. Furthermore, it is also possible to use shapes such as horizontal lines and vertical lines similar to the vowels "ㅡ" and "ㅣ".

As suggested by the applicant in the previous application, inputting the vowel lower with "." assigned to the [0] button in Figs. In the combination, the three vowels "ㅡ", "ㅣ", and ". (Araeah)" buttons are combined to input. The method of inputting all vowels with three vowels "ㅡ", "ㄴ", and "ㅣ" is also the button assigned to the vowel (indicated by "." in the drawing) (in Figs. 4-5 and 4-9 [0] button) is essentially the same as the example in which the most frequently used vowel "A" is entered.

Therefore, it is obvious that various properties presented in the applicant's previous application can be used. For example, lattice/hard consonant input by repeatedly pressing a button to which a basic consonant is assigned, vowel input by repeated pressing of a vowel button, lattice sound by a control processing method (ie, combination with a vowel button) / Input of light consonants, input of consonants assigned with vowels (eg "ㅎ"), etc. In addition, it is possible to process "00" continuously input together with the start of the vowel processing process as a promised vowel.

For example, if input of the [0] button twice is promised as the vowel "o", when inputting "1001", the first input of "1" is recognized as "a", and the second input of "0" is treated as a vowel. It recognizes that the process has started, and when the third “0” is input, it is temporarily recognized as a vowel “o”, and when the fourth “1” input is input, it recognizes the end of the vowel processing process and continuously It is definitely recognized as "sh", and it can be recognized as "gwa" for the input value "1001". In the lattice sound input in Figs. 4-10 and 4-11, by the control processing method applying post-control input, input as "ㅋ = a + {sound control} = a + ㅡ + ㅡ = 1**" can make it If up to "1*" is entered, the system recognizes it as "that", but by seeing "*" that is subsequently input, the entire input value "1** = ㅋ" is deterministically recognized by the system. will be. If "*" is entered as the 4th input value after "101", the system recognizes the input value as "Gag". This is very natural as a Hangul automaton on the 2-beol keyboard. Next, if "*" is entered as the 5th input value, the last input "1**" in "...1**" is recognized as "ㅋ" and confirmed, so the entire input value "101**" For ", it is recognized as "Ga + ㅋ". (Note: When using the Unicode system, 'ㅋ' should be displayed as one letter as the final support for 'a', but it is displayed as 'Ga + ㅋ' because the electronic document editor of the Korean Intellectual Property Office supports only the KSC 5601 complete form.) ) means that the moment "1**" is detected among a series of input values "...1**", "1**" is converted to "ㅋ", that is, as if the [ㅋ] button on the PC keyboard is input. It means that it can be processed and recognized as if it had been done.

Similarly, in the light consonant input, "ㄲ = ㄱ + {hard sound control} = 1 ## = ㄱ + ㅣ + ㅣ". For the input of "ㅎ", consider "ㅎ" as a modified alphabet (lattice sound) of "ㅇ" and enter "ㅎ = ㅇ + {sound control} = ㅇ+ㅡ+ㅡ = 8**", or Considering "ㅎ" as a modified alphabet of "아", "ㅎ = A+ㅡ+ㅡ = 0**" can be entered without ambiguity. Also, in the beginning state of a word, "ㅎ" is pressed with one stroke of the [0] button, and vowels such as "ㅡ", 'ㅣ', "ㄴ", "ㅜ", and "ㅚ" (the vowel "아" - that is, in the example [ After a vowel other than a vowel (which can become another vowel by combining the 0] button -) is identified, "ㅎ" can be input with one stroke of the [0] button, which is the same as described in other embodiments. Furthermore, even if "ㅎ" can be entered with one stroke of the button assigned to "ㅎ", it is also possible to make "0**" or "8**" be recognized as "ㅎ". It is also possible to apply the modified alphabet "3+stroke" input method to input more than 3 strokes (eg "a = 1", "ㅋ = 111", "ㄲ = 1111" or "a = 1", "ㄲ = 111", "ㅋ = 1111". This case is very rare, but there may be ambiguity). Also, as mentioned above, lattice consonants, hard consonants, or dropped consonants (consonants considered as modified alphabets of basic alphabets, e.g. It is also obvious that the simple repetitive selection method by a predetermined selection order can be applied to the input of the dropped consonant "ㅎ" for the basic consonant "ㅇ" and the dropped consonant "ㄹ" for the basic consonant "ㄴ"). For example, a = 1, ㅋ = 11, ㄲ = 111 or a = 1, ㄲ = 11, ㅋ = 111 or ㄴ = ㄴ, ㄹ = ㄴ + ㄴ ("ㄹ" is a variation of "ㄴ" light consonants)) or ㅇ = ㅇ, ㅎ = ㅇ + ㅇ (ㅇ = 8, ㅎ = 88 based on Figure 4-10) However, if input without ambiguity by the control processing method Compared to, inputting modified alphabets (lattice consonants, hard consonants, dropped consonants, etc.) by the “3+” input method and simple repetition selection method causes ambiguity and has advantages such as no significant difference in the number of input strokes. Of course, the proposed vowel input technology can be applied separately from the application of the specific consonant input technology mentioned or not mentioned in the present invention, and the above is described above. As long as, it is obvious that the same can be applied to the contents of inputting "a" as the vowel element "."

When the above consonant and vowel input method is applied, consonants and vowels can be identified "deterministically" with respect to the input value, so combining consonants and vowels to form Hangul syllables (block letters) is an existing technology ( For example, it can be easily processed by applying the consonant combination automata in the double keyboard. As a deterministic input method when the above contents are applied, the system can identify consonants and vowels, and there is no difficulty in understanding them, so a flowchart is not necessarily presented.

It was said that "sh" can be input by pressing the [A] button (ie, the [0] button) twice by repeatedly pressing a specific vowel button. That is, it becomes "00 = 0" or "0# = 0". If "ㅐ" is input only as "00", "0#" can be defined only as "ㅐ" rather than "ㅐ" and entered as "ㅐ = 0#". However, "0## = ㅔ", but when pressed to "0#", there is a point where "ㅐ" with a different shape from "ㅔ" can be displayed. For example, if "10#" is pressed, it will be recognized (and displayed) as "dog", and if "#" is pressed once more, "10## = crab" will be recognized. At this time, the user may associate "ㅔ" by pressing "ㅣ" once more after inputting "dog" so that the center dot (or small horizontal stroke) of "ㅐ" is pushed inward. As mentioned in the previous application, the input of "ㅑ" can be defined as pressing the "a" button twice in succession, that is, "ㅑ = A + A", but in this case, input as "ㅐ = A + I" It becomes difficult to do (since you have to enter "sh = a +ㅣ" here).

In Table 1, it is defined as "ㅘ = A+ㅡ+ㅣ+A = 0*#0", but it can also be defined as "ㅘ = [ㅗ+A] = A+ㅡ+A = 0*0". What is shown in "[...]" is a decomposition of the complex vowel for better understanding. However, if this is applied, when the [0] button is pressed after the vowel "ㅗ = A+ㅡ = 0* (araeah, that is, the vowel "ㅗ" that '.' cannot be combined), together with the [0] button It becomes difficult to input the assigned consonant ("ㅎ" in the example) with one stroke of the [0] button. However, it is possible to input "ㅎ" by other means (eg, 0**, 8**, 0*, .., etc.). Similarly, it is also possible to define "ㅙ = [ㅗ + ㅐ] = A + ㅡ + A + l = 0 * 0 #". The definition of "ㅘ = A+ㅡ+A (= 0*0)" and the definition of "ㅙ = A+ㅡ+A+ㅣ(= 0*0#)" are "ㅘ = A+" in Table 1. ㅡ+ㅣ+A (= 0*#0)", which can be applied simultaneously with the definition of "ㅙ = A+ㅡ+ㅣ+아+ㅣ(= 0*#0#)", and either one can be selectively applied. and can be set according to the user's choice. Defining “ㅘ = A + ㅡ + A (= 0 * 0)” and “ㅙ = A + ㅡ + A + ㅣ (= 0 * 0 #)” have fewer input strokes, so apply them first. , additionally (optionally) "ㅘ = A+ㅡ+ㅣ+아(= 0*#0)", "ㅙ = A+ㅡ+ㅣ+A+ㅣ(= 0*#0#)" It would be desirable to allow The definition of "ㅘ = A + ㅡ + A (= 0 * 0)" and the definition of "ㅙ = A + ㅡ + A +ㅣ (= 0 * 0 #)" are "sh = A + A (= 00)" (that is, it is possible even if it is not defined as "sh = a + a (= 00)").

For reference, in the Korean keypad of FIGS. 4-5 illustrated in the previous application, the vowel elements are arranged from left to right in the order of "ㅡ", ".", and "ㅣ", which serves to increase the naturalness of input do. If you look closely at "ㅡ", ".", and "ㅣ", the complex vowels "ㅢ", "ㅟ", "ㅝ", "ㅞ", . . You can observe the shape of complex vowels such as . However, conversely, if they are arranged in the order of "ㅣ", ".", and "ㅡ" as in the keypad of Samsung Electronics Co., Ltd., the consonant vowels are not observed well. In addition, there is a disadvantage in that the input of the complex vowel cannot be input naturally as it flows from left to right. Similarly, going one step further, entering "ㅘ = A + ㅡ + A (= 0 * 0)" will reduce the number of strokes than entering "ㅘ = A + ㅡ + I + A (= 0 * # 0)" Meaningful, but increases the naturalness of the input. In the illustrated Korean keypad of FIG. 4-10, Korean vowels are arranged from left to right in the order of "ㅡ", "ㄴ", and "ㅣ", and entering "...#0" is done by pressing the right button ([ After pressing the #] button, pressing the left button ([0] button) hinders naturalness.

Furthermore, "sh = 00" can be applied to complex vowel inputs such as "ㅝ" and "ㅞ", as in the case of "a = 0". For example, in Table 1, "ㅝ = ㅡ + A + A + ㅣ = *00#" is defined, but "ㅝ" in "ㅝ" is set to "A + A = 00", so that "ㅝ = [ TT+sh] = ㅡ+a+a+a = *000". Also in Table 1, it is defined as "ㅞ = ㅡ +a+a+ㅣ+ㅣ", but "sh" in "ㅞ" is set to "a+a = 00", so that "ㅞ = [TT+sh+ㅣ ] = ㅡ+a+a+a+ㅣ = *000#". As in the case of "ㅘ" and "ㅙ", "ㅝ = ㅡ+a+a+a (= *000)" and "ㅞ = ㅡ+a+a+a+ㅣ(= *000#)" It is possible independently of defining "o = A + A = 00", and it may be applied simultaneously with the definition of "ㅝ" and "ㅞ" in Table 1, or it may be applied selectively. If the input of "sh" is defined only as "sh = A + A (= 00)" rather than "sh = A+ㅣ (= 0#)", "ㅐ = A+ㅣ (= 0#)" you will be able to input

When applying "ㅝ = ㅡ+a+a+a (= *000)", "ㅞ = ㅡ+a+a+a+ㅣ(= *000#)", when pressed up to "1*00", " However, if the [0] button is pressed once more, it is recognized as "Ku". If [#] is pressed once more, it will be recognized as "box". Similarly, in this case, "*000" means input of a normal vowel (ie, "ㅝ"), so the vowel "ㅠ(=*00)" followed by "ㅎ (ie, [0] button assigned with a vowel It is obvious that "ㅎ" cannot be input with one stroke of the button to which "consonant)" is assigned.

- 숫자 '0' 안에 'ㅏ' - 가 배치) 을 "아래아(.)"처럼 연상하여 나머지 모음을 입력할 수 있는데, "ㅑ"는 음 가를 기준으로 조합하여 입력하게 되는 점이 있다. 마찬가지로 표1에서 "ㅒ = ㅣ +ㅏ+ㅏ+ㅣ (=#00#)" 으로 되어 있으나, 이를 "ㅒ = [ㅑ+ㅣ] = ㅣ+ㅏ+ㅣ (= #0#)" 으로 정의하여 입력할 수 있다 ("ㅐ = ㅣ+ㅏ+ㅣ"가 아닌 "ㅐ = ㅏ+ㅣ"로 입력한다 는 전제). 마찬가지로 모음 "ㅑ = ㅣ+ㅏ+ㅏ"로 하는 것과 "ㅑ = ㅣ+ㅏ"로 하는 것, 그리고 모음 "ㅒ = ㅣ+ㅏ+ㅏ+ㅣ"로 하는 것과 "ㅒ = ㅣ+ㅏ+ㅣ"로 하는 것은 동시에 적용될 수도 있고 선택적으로 적용될 수도 있다. "ㅑ = ㅣ+ㅏ"로 "ㅒ = ㅣ+ㅏ+ㅣ"로 하면 모음 "ㅑ"와 "ㅒ"의 입력타수가 표1의 경우보다 1타씩 줄어들게 된다. 이 내용을 선출원에서 기술하지 않은 이유는 모음 "ㅑ"와 "ㅒ"는 사용빈도 가 많지 않은 모음이므로 입력타수 감소에는 많은 영향이 없기 때문이다. Similarly, "a" can be entered with the [a] button ([0] button in the drawing) to which "a" is assigned, or it can be entered as "a = ㅣ+a (=#0)" (Section 4.10 and Section 4.11). When entering only "sh = A + A (= 00)", as in "ㅐ = A + l (= 0#)" instead of "Sh = A + l (= 0#)", "A = If you define only "A = A (= 0)" instead of "ㅣ+A (= #0)", it is possible to input other alphabets with the combination of "ㅣ+A". For example, it is defined as "ㅑ = ㅣ + A + A (= #00)", but the input rule can be defined to input "ㅑ = ㅣ + A (= #0)". The sound value of the vowel "ㅑ" is "ㅣ + A", which is known to anyone who has received a certain level of education. However, enter the vowel using the most frequently used vowels "ㅡ", "ㄱ", and "ㅣ", but the button assigned to the vowel "A" (i.e., in the example drawing

- 'A' - placed in the number '0') can be entered like "Aeraeah (.)" and the remaining vowels can be entered, but "ㅑ" is entered in combination based on the sound value. Similarly, in Table 1, "ㅒ = ㅣ +a+a+ㅣ (=#00#)", but by defining it as "ㅒ = [ㅑ+ㅣ] = ㅣ+a+ㅣ (= #0#)" You can enter (provided that you enter "ㅐ = ㄴ+ㅣ" rather than "ㅐ = ㅣ+아+ㅣ"). Similarly, the vowel "ㅑ = ㅣ+a+a" and "ㅑ = ㅣ+a", and the vowel "ㅒ = ㅣ+a+a+ㅣ" and "ㅒ = ㅣ+a+ㅣ" It can be applied simultaneously or selectively. If "ㅑ = ㅣ + A" and "ㅒ = ㅣ + A + ㅣ", the number of input strokes for the vowels "ㅑ" and "ㅒ" is reduced by one stroke compared to the case of Table 1. The reason why this content is not described in the earlier application is that the vowels "ㅑ" and "ㅒ" are not frequently used vowels, so they do not have much effect on reducing the number of strokes entered.

"ㅡ", ".", "ㅣ" In vowel input using three vowel elements, if the "." button is input after a consonant (eg "a"), it is temporarily displayed as "a.", and the next If "ㅡ" is entered in ".+ㅡ" is recognized as "ㅗ" and "high" is displayed. That is, there is a disadvantage in that the complete form of Hangul is not displayed in the middle of input. However, if you input a vowel by combining modern Korean vowels ("ㅡ", "ㄴ", "ㅣ" in this example), the button assigned to "ㄴ" after any consonant (eg "ㄱ") is pressed When lost, it has the advantage of being able to display the complete form of Hangul, such as "ga". Even when "o = A + A" is applied, "ga" is displayed for the input of "10", and when "0" is pressed once more, a complete Korean character such as "geo" can be displayed. Of course, the problem of recognizing and identifying a specific alphabet (or Korean character) by a specific procedure (algorithm) and the problem of displaying this recognized specific alphabet (or Korean character) are separate issues.

In addition, it is natural that the input method (input procedure) and the problem of how to mark the Korean character elements or the code form representing the Korean character elements in an appropriate form on the keypad button for the input method are separate issues. For example, as shown in Fig. 4-5, the vowel element "." Just as it is possible to input a vowel by considering the [0] button as the “A” button on the keypad marked with this mark (red dot inside the number “0”), the notation on the keypad button can be modified. It has been mentioned in the previous application that this input method can be applied even to keypads where Korean characters are not marked. Examples of modified forms of several keypad marks are shown in FIGS. 4-12. 4-12 is a keypad displaying the vowels "a" and "o" by putting "+" in the number "0 (Zero)" at the same time, and FIG. 4-13 is also the number "0 (zero) This is an example of a keypad that puts the shape of "-A" in " )" so that "A" can be associated with "o" in priority. In addition, as shown in Figures 4-14, a keypad case in which "H" shape, which is a form of attaching "A" and "o" to the left and right, is put in the number "0 (zero)" to remind "A" and "o" to be. It is the same that the form temporarily displayed during input can also be diverse like this. 4-15 is an example of displaying "a" and "o" respectively. In other cases, as in FIGS. 4-15, the number "0" may be displayed separately, and various other variations are possible, and all variations other than the application of the vowel combination method of the present invention are also within the scope of the present invention. is self-explanatory. In the exemplary drawing, the fact that "ㅎ" is displayed in a light gray color means that "ㅎ" may not be marked as mentioned.

를 표시할 수 있다 (도 4-13 에서와 마찬가지로 "ㅏ"를 우선 연상할 수 있도록 하여 좌측 왼편의 수평선을 회색으로 한 사례로 회색으로 표시된 부분이 없는 경우도 포함함). 또는 해당버튼을 이용하여 1상하향모음을 입력하는 경우

형태를 버튼상에 표시할 수 있다. 다른 경우에서와 마찬가지로 입력 중간에 표시되는 형태로 사용될 수도 있음은 마찬가지이다. 해당 버튼을 이용하여 우선적으로 입력되는 모음에 따라 첫번째 제시한

형태의 좌우대칭형 또는 두번째 제시한

형태의 상하대칭형이 이용될 수 있다. (이러한 형상이 [0] 버튼에 표시될 경우) 다른 사례에서와 마찬가지로 숫자 "0" 이 함께 표시되거나 함께 표시되지 않을 수 있고, 역시 "ㅎ" 도 함께 표시되거나 표시되지 않을 수도 있다. 제시하는 형상은 어느 광고에 나오는 "우주의 질서와 땅의 조화" 또 거기에 인간중심(人間中心)의 사상을 담고자 한 것이다. If one or more of the "1 up and down vowels (a, sh, ㅗ, TT)" is input using a specific button (e.g. [0] button), if a form that can be displayed on the button is additionally presented As follows. In the form of "-a" presented in Fig. 4-13

can be displayed (as in FIGS. 4-13, the horizontal line on the left side is grayed out so that “a” can be first recalled, including cases where there is no grayed part). Or when inputting 1 up and down vowel using the corresponding button

A shape can be displayed on a button. It is the same that it may be used in the form displayed in the middle of the input as in other cases. According to the vowels that are preferentially entered using the corresponding button, the first

Bilateral symmetrical form or the second presented

A top-bottom symmetrical form can be used. (If this shape is displayed on the [0] button), as in other cases, the number “0” may or may not be displayed together, and “ㅎ” may also be displayed together or not. The proposed shape is the "order of the universe and the harmony of the earth" in an advertisement, and it is intended to contain the human-centered ideology.

형태 또는

형태에서 각각 왼쪽, 아래쪽에 흐린 회색으로 표현된 분은, 다른 키패드 도면에서 "ㅎ"을 표시할 수도 있고 표시하지 않을 수도 있다고 한 것처럼, 표시될 수도 있고 표시되지 않을 수도 있음은 쉽게 알 수 있다.

형태에서 좌측의 회색부분을 제외하면, 도4-10 에서 동그라미 또는 숫자 "0" 안에 "ㅏ" 가 있는 형상과 유사하게, "ㅏ"에 동그라미 또는 숫자 "0"이 걸쳐있는 형상이 된다.

형태는 도4-13에서 "-ㅏ" 에 동그라미 또는 숫자"0"이 걸쳐 있는 모양인데, 마찬가지로 도4-12의 "+"에 동그라미 또는 숫자 "0"이 걸쳐있는 모양으로 변형될 수도 있음은 자명하다.

form or

In the form, it is easy to see that those expressed in gray on the left and bottom, respectively, may or may not be displayed, as in other keypad drawings, "ㅎ" may or may not be displayed.

Except for the gray part on the left side of the shape, similar to the shape with "A" in a circle or number "0" in Fig. 4-10, it becomes a shape with a circle or number "0" over "A".

The shape is a shape in which a circle or number "0" is crossed over "-A" in Fig. self-explanatory

As mentioned, due to the characteristics of Hangeul, it can represent flat consonants (eg "ㄱ"), lattice sounds (eg "ㅋ") and hard consonants (eg "ㄲ") corresponding to the flat consonants, and in pronunciation and shape Because of the similarity, the modified alphabet is not displayed on the keypad, but hidden, and only plain consonants (eg "a") are displayed on the keypad, and the rest of the consonants are naturally associated and input (eg, control processing method, repetition selection method, modified alphabet All methods including 3+ other input methods, etc.) can be used. As exemplified by utilizing the characteristics of Hangeul, the most scientific writing system existing on earth, it can be said that one of the great characteristics of Hangeul is that it can compose a naturally concise keypad (minimum number of character elements placed on buttons). Of course. However, it is obvious that in some cases, keypads in which modified alphabets (lattice consonants, hard consonants, and dropped consonants) are assigned together with basic consonants (plain consonants) are also included in the scope of the present invention. If the dropped consonant "ㅎ" is regarded as a modified alphabet of "ㅇ" (grid or light consonant), "ㅇ" and "ㅎ" can be displayed together on the keypad, and the dropped consonant "ㄹ" is replaced by "ㄴ" If it is regarded as a modified alphabet (as mentioned in the earlier application, in this case "ㅎ" can be the basic consonant), "ㄴ" and "ㄹ" can be displayed together. It is obvious that the application of the keypad marked on the keypad button by writing the modified alphabet together with the plain consonant in the exemplified drawing also falls within the scope of the present invention. That is, it is possible to display only the lattice sound along with the flat consonant on the keypad, and it is also possible to display only the hard consonant along with the flat consonant on the keypad button. It is also possible to display all of them. In addition, it is obvious that all cases are included in the scope of the present invention, such as when only some of the lattice consonants are additionally displayed together with flat consonants, or when only some of the hard consonants are displayed together with flat consonants.

It has been explained that all Korean keypads presented by the applicant in the previous application and this application can have compatibility. The composition system of Hangeul consists of consonants on the left, vowels on the right (i.e., consonants on the right), and vowels on the bottom of consonants on the top (i.e., box submodel). And in the notion of Korean people, "ㄱ" corresponds to the number "1", "ㄴ" corresponds to the number "2", and "ㄴ" corresponds to the number "3". When configuring serial numbers for item classification, (1), (2), (3), (4), … I also write numbers like "go", "me", "da", "la", ... Or ㉠, ㉡, ㉢, ㉣, … It is easy to know even when writing . “a”, “b”, “c”, … Original characters ㉠, ㉡, ㉢, … It can be said that the existence of this KSC5601 character set also proves this. i.e. the numbers 1, 2, 3, 4... "ㄱ", "ㄴ", "ㄴ", "ㄹ" in order on the buttons... It is obvious that assigning is the optimal form that meets our concept of letters and numbers.

Another example was the use of numbers (not Arabic numerals, Chinese characters 一, 二, 三, 4, 5, …) in the position of Korean consonants in a rudimentary form of cryptography during the Joseon Dynasty. For example, "shi" is displayed as "七ㅣ" and "me" as "五sh". In fact, it is very easy for Koreans to find out the original sentence by looking at words or phrases that display numbers corresponding to the consonant positions of Hangul. This is true even for those who are not aware of these rules. For example, in a TV program called Survival History Quiz, “三ㅐ 五や 四ㅣ” was shown among sentences written in the Joseon Dynasty and when asked what it meant, “all” participants guessed that the original sentence was “bald.” (Of course, the quiz participants were unaware of the rule that the first consonant was marked with a number)

Therefore, as shown in the drawing presented by the applicant, assigning plain consonants (in order) to number buttons and assigning vowels to buttons at the bottom corresponds to Korean people's numerical concept related to consonants and also corresponds to the composition of the "box and bottom model" Hangul. It is self-evident to do However, in Korea, Samsung Electronics' keyboard using three vowel elements "ㅡ", ".", and "ㅣ" is widely used. Due to the influence of the giant company Samsung Electronics' keyboard, some companies have a desire to place the vowel button (or vowel element button or element vowel button) above the consonants. Although it is never desirable, the [*], [0], [#] buttons at the bottom of the keypad are placed on top of the [1], [2], [3] number buttons to form the same shape as Figures 4-16 and 4-17. The keyboard of can be configured. Although the arrangement of consonants in the box-under-shaped pattern is violated, consonants can be assigned to number buttons in order. It is obvious that the exemplary drawings are also included in the category of the prior application of the applicant. And in the example drawing, you can see the letters "Han" or "ㅎ.ㄴ ('.' is below)" of "Hangul". The fact that "ㅎ" is expressed in gray means that the aforementioned "ㅎ" may not be displayed. However, by displaying "ㅎ" on the [0] button, arranging 10 flat consonants on 10 number buttons ([1] ~ [0] buttons) means accepting the current Korean standard keypad (KSC-xxxx) have

The above shows an example of inputting all vowels using the three vowels "A", "ㅡ", and "ㅣ", which are most frequently used in Korean (about 50% of the total vowel usage frequency). It is obvious that the same can be applied to all similar cases. For example, it includes applying any vowel except for "ㅡ", "ㅣ", and "ㄴ" (eg, any other vowel including "sh" or "ㅗ") instead of "ㄱ". When "o" is applied instead of "a", it can be "ㅠ = ㅡ+o+o", and in the table presented above, the vowel "a" is replaced by a vowel ("o") to form a combination of vowels You can do it. However, since the vowel "A" is used overwhelmingly more frequently than other vowels (as mentioned, 22% of the total frequency of use of the vowel), the case where the vowel "A" is used is not as good in terms of input efficiency.

By generalizing Table 1 a little more, processing vowels using three vowels (and three vowel buttons) of (element) vowels "ㅡ", "ㅣ", and "X" can be done as follows. In the table below, among the 21 vowels in Korean, among the 19 vowels excluding "ㅡ" and "ㅣ", the vowel used as vowel "X" is the button assigned to vowel "X" (i.e., the [X] button) 1 It is self-evident that it can be input in other words.

collection 3 vowels to be combined X X One all ㅣ+X 2 eh ㅣ+ X +ㅣ 3 hey ㅣ+ X + X 4 this guy ㅣ+ X + X +ㅣ 5 yes X + l 6 to X +ㅣ+ㅣ 7 woman X + X +I 8 yes X + X +ㅣ+ㅣ 9 fuck you X +- 10 ㅘ X +ㅡ+ㅣ+ X 11 ㅙ X +ㅡ+ㅣ+ X +ㅣ 12 ㅚ X +ㅡ+ㅣ 13 blanket X + X +- 14 sob ㅡ+ X 15 ㅝ ㅡ+ X + X +ㅣ 16 ㅞ ㅡ+ X + X +ㅣ+ㅣ 17 ㅟ ㅡ+ X +ㅣ 18 ㅠ ㅡ+ X + X 19 ㅡ ㅡ 20 ㅢ ㅡ+ㅣ 21 tooth tooth

By further generalizing this, vowels can be input by a combination similar to the table above using any three vowel buttons in Korean. For example, you can input vowels "A", "B", and "X" as element vowels and input the remaining vowels in combination similar to the following. It is also obvious that the vowels "A", "B", and "X" can be input with one stroke of the button assigned to each vowel. For user convenience and minimization of the number of input strokes, it is preferable to use three vowels including “ㅡ”, “ㅣ” and “A”.

collection 3 vowels to be combined X X A A B B One all B+X 2 eh B+X+B 3 hey B+ X + X 4 this guy B+X+X+B 5 yes X+B 6 to X+B+B 7 woman X+X+B 8 yes X + X +B+B 9 fuck you X+A 10 ㅘ X +A+B+ X 11 ㅙ X+A+B+ X+B 12 ㅚ X+A+B 13 blanket X+X+A 14 sob A+X 15 ㅝ A+X+X+B 16 ㅞ A+ X + X +B+B 17 ㅟ A+X+B 18 ㅠ A+X+X 19 ㅡ 20 ㅢ A+B 21 tooth

As suggested, it is possible to efficiently input vowels using the three vowels ("아", "ㅡ", "ㅣ") of Korean (and the three vowel buttons). An example of the vowel input method is additionally presented as follows. The following example is an example of using the vowels "sh", "ㅡ", and "ㅣ". Here, for convenience, the control processing method is not applied to the input of consonants. (This is because "ㅡ" or "ㅣ" appears consecutively in the vowel input rule in the case below.)

collection collection
decomposition 3 vowels to be combined (B) When applicable, not applicable (A) (B) One all ㅣ+ㅣ ㅣ+ㅡ or ㅇ+ㅇ 2 eh ㅣ+sh
(ㅣ+ㅣ+ㅣ (X)) ㅣ+ㅡ+ㅣ 3 hey ㅣ+ㅣ+ㅣ ㅣ+ㅡ+ㅡ or
ㅣ+ㅣ+ㅡ 4 this guy ㅑ+ㅣ
A+sh ㅣ+ㅣ+ㅣ+ㅣ or
ㅣ+ㅣ+sh ㅣ+ㅡ+ㅡ+ㅣor
ㅣ+ㅣ+ㅡ+ㅣ 5 yes yes 6 to ㅇ+ㅣ ㅇ+ㅣ ㅡ+ㅣ+ㅣ ㅟ(B), ㅠ(B) 7 woman ㅡ+sh
(ㅡ+ㅡ+ㅣ (X)) 8 yes ㅕ+ㅣ ㅡ+ㅇ+ㅣ 9 fuck you ㅣ+ㅡ or
o + o 10 ㅘ ㅗ+a ㅣ+ㅡ+ㅣ+ㅣ ㅣ+ㅡ+ㅣ+ㅡ 11 ㅙ ㅘ+ㅣ
ㅚ+sh ㅣ+ㅡ+ㅣ+ㅣ+ㅣ
ㅣ+ㅡ+ㅣ+sh ㅣ+ㅡ+ㅣ+ㅡ+ㅣ
ㅣ+ㅡ+ㅣ+sh 12 ㅚ ㅗ+ㅣ ㅣ+ㅡ+ㅣ 13 blanket ㅣ+ㅣ+ㅡ 14 sob ㅡ+ㅡ 15 ㅝ TT + ㅇ ㅡ+ㅡ+ㅇ
ㅡ+ㅣ+ㅡ or
ㅡ+ㅣ+ㅡ+ㅣ ㅞ(B-1) 16 ㅞ ㅝ+ㅣ ㅡ+ㅡ+sh+ㅣ or
ㅡ+ㅡ+sh+sh ㅡ+ㅣ+ㅡ+ㅣ or
ㅡ+ㅣ+ㅡ+ㅣ+ㅣ ㅝ(B-2) 17 ㅟ TT+ㅣ ㅡ+ㅡ+ㅣ ㅡ+ㅣ+ㅣ ㅔ(B), ㅠ(B) 18 ㅠ ㅡ+ㅡ+ㅡ ㅡ+ㅣ+ㅣ ㅔ(B), ㅟ(B) 19 ㅡ ㅡ 20 ㅢ ㅡ+ㅣ 21 tooth tooth

The decomposition of complex vowels in the "vowel decomposition" column above is indicated for better understanding. Presenting several (multiple) input rules for one vowel as (A), (B) and "or" shows that various cases are possible.

One of the characteristics of the above case is to input "A" and "ㅑ" by repeatedly pressing the vowel "ㅣ" button, and input "TT" and "ㅠ" by repeatedly pressing the vowel "ㅡ" button. That is, when the "ㅡ" button is pressed once, it becomes "ㅡ", when it is pressed twice, it becomes "TT", and when it is pressed three times, it becomes "ㅠ". (As described in the previous application of the applicant, it provides the convenience of repeatedly pressing the same button and the feeling of adding a stroke by pressing the button, providing naturalness of input)

Another feature is to input the rest of the vowels using the horizontal and vertical lines of the vowels "ㅡ" and "ㅣ". At this time, "sh", "ㅢ", and "TT" are all a combination of "horizontal line shape and vertical line shape". Among these vowels, it is appropriate to enter "ㅢ = ㅡ+ㅣ". The vowel "sh" can be entered with one stroke of the button to which "sh" is assigned, and the vowel "TT" can be naturally entered by repeatedly pressing the "ㅡ" button. In addition, the vowels "ㅟ = [ TT+ㅣ]" and "ㅕ" can be expressed as "ㅡ+ㅡ+ㅣ", but (if "TT = ㅡ+ㅡ" of "ㅟ"), "ㅕ" = ㅡ + ㅡ + ㅣ instead of "ㅕ = ㅡ + ㅇ", it is possible to do "ㅟ = ㅡ + ㅡ + ㅣ". "ㅐ" is also "ㅐ = ㅣ+ㅣ+ㅣ" instead of "ㅐ = ㅣ+ㅇ", so "ㅑ = ㅣ+ㅣ+ㅣ".

The characteristic of the above case is that a vowel containing the vowel "sh" (for example, ㅔ, ㅕ, ㅖ, ㅝ, ㅞ, and furthermore, vowels such as "ㅐ", "ㅒ", "ㅙ") is naturally entered. It can be done. In the case of "ㅕ", if you enter "ㅡ+ㅡ+ㅣ", the number of strokes will be 3, and it will be difficult to enter "ㅟ = [ㅜ+ㅣ] = ㅡ+ㅡ+ㅣ". Of course, if "ㅟ = ㅡ+ㅣ+ㅣ", it can be done as "ㅕ = ㅡ+ㅡ+ㅣ", but the "TT" included in "ㅟ" is the input method of the collection "TT" (TT = ㅡ+ ㅡ) and input in a different way, which is not good in terms of simplicity of input rules, user convenience, and WYSWYG.

In the table above, the meaning of "not applicable when (B) is applied" applies to only one vowel because (B) of the vowels "ㅔ", "ㅟ", and "ㅠ" are all "ㅡ+ㅣ+ㅣ" It means you can.

The above case can be modified to become "ㅗ" or "ㅛ" by repeatedly pressing the "ㅡ" button, or to "sh" or "ㅕ" by repeatedly pressing the "ㅣ" button. (One of the two or both) However, it will not be better in terms of the naturalness of input and user convenience than shown in the case above.

In the above case, except for the input cases in which the vowels "ㅡ" or "ㅣ" appear consecutively at the beginning of the vowel processing process, the rest of the input methods are inputting modified alphabets (case / hard consonants, etc.) by the control processing method (provided, however, that it does not conflict with the input rules of the case where modified alphabets are entered by the control processing method). Likewise, among the input cases in <Table 1>, etc., the above case can be selectively applied as long as it does not conflict with the above case (ie, it is not defined identically for other vowels). It is obvious that this is applicable throughout the present invention.

Next, similarly to the above, enter "sh", "ㅕ" and "A", "ㅑ" by repeatedly pressing the vowels "ㅡ" and "ㅣ", and the horizontal shape of the vowels "ㅡ" and "ㅣ" This is an example of using the three vowel buttons of "a", "ㅡ", and "ㅣ" while inputting the remaining vowels using a combination in the form of a vertical line.

collection collection
decomposition 3 vowels to be combined (B) When applicable, not applicable (A) (B) One all all ㅣ+ㅣ ㅛ(A), ㅑ(A-4) 2 eh A + l ㅣ+ㅡ+ㅣ 3 hey A + ㅡ or
ㅣ+ㅣ+ㅣ or
ㅣ+ㅣ+ㅡ or
ㅣ+ㅣ ㅣ+ㅡ+ㅡ 4 this guy ㅑ+ㅣ A+ㅡ+ㅣ ㅣ+ㅡ+ㅡ+ㅣ 5 yes A + A 6 to ㅇ+ㅣ A + A + l ㅡ+ㅣ+ㅣ ㅟ(B), ㅠ(B) 7 woman ㅡ+A or
ㅡ+A+A or
A+A+A or ㅡ+ㅡ+ㅣ ㅟ(A) 8 yes ㅕ+ㅣ ㅡ+ㅡ+ㅣ+ㅣ or
A+A+A+A 9 fuck you ㅣ+ㅡ 10 ㅘ ㅗ+a ㅣ+ㅡ+A 11 ㅙ ㅘ+ㅣ ㅣ+ㅡ+A+ㅣ 12 ㅚ ㅗ+ㅣ ㅣ+ㅡ+ㅣ 13 blanket ㅣ+ㅣ+ㅡ 14 sob ㅡ+ㅡ 15 ㅝ TT + ㅇ ㅡ+ㅡ+A or
ㅡ+ㅣ+ㅡ ㅡ+ㅡ+A+A or
ㅡ+ㅣ+ㅡ+ㅣ ㅞ(A-2) 16 ㅞ ㅝ+ㅣ ㅡ+ㅡ+A+ㅣ or
ㅡ+ㅣ+ㅡ+ㅣ ㅡ+ㅡ+A+A+ㅣ or
ㅡ+ㅣ+ㅡ+ㅣ+ㅣ 17 ㅟ TT+ㅣ ㅡ+ㅡ+ㅣ ㅡ+ㅣ+ㅣ ㅔ(B), ㅠ(B) 18 ㅠ ㅡ+ㅡ+ㅡ ㅡ+ㅣ+ㅣ ㅔ(B), ㅟ(B) 19 ㅡ ㅡ 20 ㅢ ㅡ+ㅣ 21 tooth tooth

The frequency of use of vowels "sh", "ㅡ", and "ㅣ" is about 40% of the total frequency of use of vowels, and the frequency of use of vowels "a", "ㅡ", and "ㅣ" is about 50%, so " Using ", "ㅡ", and "ㅣ" can be efficient in terms of input strokes. In addition, there is an advantage of naturally inputting vowels (eg, "ㅐ", "ㅑ", "ㅒ", "ㅘ", "ㅙ", etc.) including the vowel "아". However, in order to input "ㅟ = ㅡ+ㅡ+ㅣ", there is a disadvantage such as not being able to input "ㅕ = ㅡ+ㅡ+ㅣ". Therefore, if you enter "ㅕ = A + A + A", "A", "sh", and "ㅕ" will be generated according to the press of the "A" button.

It has been described that only one of the input methods for one vowel or several can be applied simultaneously. However, similarly, if there are multiple vowels with the same input value (the same vowel combination in the case above), only one is required.

In (A) of the "ㅝ" input, "ㅝ = ㅡ + ㅡ + A" is input as "ㅝ = ㅡ + ㅡ + A" because there is no Korean vowel that is combined with "a" after the vowel "TT" It has been shown that the number of strokes can be reduced. However, it is a disadvantage in terms of simplicity and consistency of input rules. Therefore, as in (B) of the "ㅝ" input at the same time as "ㅝ = ㅡ+ㅡ+A", "ㅝ = [ㅜ+sh] = ㅡ+ㅡ+아+아" can be input as well. At the same time, it shows that it is possible to use a combination of horizontal and vertical lines of the vowels "ㅡ" and "ㅣ" in the input of "ㅝ".

Also, as mentioned above, it is obvious that there is compatibility between the keypads of FIG. 4-*. (For example, the input method described in 4-10 can be applied in 4-9)

As a similar example, while using the three vowels of modern Korean, among them the vowels "a", "ㅡ", and "ㅣ", press the "ㅣ" button repeatedly to obtain "sh", "ㅕ", and "ㅖ". , input "TT" and "ㅠ" by repeatedly pressing the "ㅡ" button, enter "ㅑ" by repeatedly pressing the "A" button, and enter "ㅗ" and "ㅛ" in the form of horizontal/vertical lines With a combination of vowels "ㅡ" and "ㅣ" (i.e., "ㅗ = ㅣ+ㅡ", "ㅛ = ㅣ+ㅣ+ㅡ") 10 basic vowels (i.e., A, ㅑ, sh, ㅕ, ㅗ , ㅛ, TT, ㅠ), and the remaining vowels are entered as a combination of these vowels.

collection collection
decomposition 3 vowels to be combined (B) When applicable, not applicable (A) (B) One all all 2 eh A + l 3 hey A + A 4 this guy ㅑ+ㅣ A + A + l 5 yes ㅣ+ㅣ 6 to ㅇ+ㅣ ㅡ+ㅣ+ㅣ 7 woman ㅣ+ㅣ+ㅣ 8 yes ㅕ+ㅣ ㅣ+ㅣ+ㅣ+ㅣ 9 fuck you ㅣ+ㅡ 10 ㅘ ㅗ+a ㅣ+ㅡ+A 11 ㅙ ㅘ+ㅣ ㅣ+ㅡ+A+ㅣ 12 ㅚ ㅗ+ㅣ ㅣ+ㅡ+ㅣ 13 blanket ㅣ+ㅣ+ㅡ 14 sob ㅡ+ㅡ 15 ㅝ TT + ㅇ
ㅠ+ㅣ ㅡ+ㅡ+ㅣ+ㅣ or
ㅡ+ㅡ+ㅡ+ㅣ 16 ㅞ ㅝ+ㅣ
ㅠ+ㅣ+ㅣ ㅡ+ㅡ+ㅣ+ㅣ+ㅣ or
ㅡ+ㅡ+ㅡ+ㅣ+ㅣ 17 ㅟ TT+ㅣ ㅡ+ㅡ+ㅣ 18 ㅠ ㅡ+ㅡ+ㅡ 19 ㅡ ㅡ 20 ㅢ ㅡ+ㅣ 21 tooth tooth

In the case above, the combination of vowels "ㅡ" and "ㅣ" was used only for "ㅗ" and "ㅛ", which are not entered by repeatedly pressing the "ㅡ" button among the 10 basic vowels. And even for the input of "ㅔ", the combination of "ㅡ" and "ㅣ", which are vowels in the form of horizontal/vertical lines, was used as "ㅔ = ㅡ+ㅣ+ㅣ". If "ㅕ = ㅡ+ㅡ+ㅣ" is made by combining the vowels "ㅡ" and "ㅣ" instead of "ㅕ = ㅣ+ㅣ+ㅣ", "ㅔ = [sh+ㅣ] = "ㅣ+ㅣ +ㅣ". Vowels other than the 10 basic vowels are all entered as a combination of the 10 basic vowels entered above. However, "ㅞ = [TT+ㅔ] = ㅡ+ㅡ+ㅣ+ㅣ With +ㅣ", "ㅔ" included in "ㅞ" is set to "ㅣ +ㅣ+ㅣ" It can be seen that the input rule that is easy to recognize is applied as a whole.

In the input of vowels using a combination of "ㅗ", "ㅛ", "ㅔ", etc. as well as horizontal and vertical vowels "ㅡ" and "ㅣ" above, the same input rules as in <Table 1> are selectively Of course, it can be applied.

An example of inputting Korean vowels using three Korean vowels (and three vowel buttons) is as follows. First, the 21 vowels used in modern Korean are classified according to their vertical/horizontal form for convenience as follows.

"ㅡ" is called a "horizontal vowel" for convenience, and "ㅣ" is called a "vertical vowel" for convenience. "ㅘ", "ㅙ", ㅚ", "ㅝ", "ㅞ", "ㅟ", "ㅢ" containing "ㅡ" and "ㅣ" are called "vertical and horizontal vowels". "ㅗ", "ㅛ", "ㅜ", and "ㅠ" in the form of small strokes added are called "horizontal (basic) type vowels." "A", "ㅐ", "ㅑ", "ㅒ", "sh", "ㅔ", "ㅕ", "ㅖ" are called "vertical (basic) vowels".

In addition, the 10 basic vowels (a, ㅑ, sh, ㅕ, ㅗ, ㅛ, ㅜ, ㅠ, ㅡ, ㅣ) are classified according to the direction as follows. "A", "ㅑ" are right-facing vowels, "sh", "ㅕ" are left-facing vowels, "ㅗ", "ㅛ" are upward vowels, "TT", " ㅠ" is a descending vowel, and the basic "ㅡ" and "ㅣ" are undirected vowels. If further divided, "A" with one small stroke added to the right can be called "1-right vowel", and "ㅑ" with two small strokes added to the right can be called "2-right vowel". The rest of the vowels (sh, ㅕ, ㅗ, ㅛ, TT, ㅠ) can be called in the same way. Upward vowels and downvowels can be combined to be called "upward and downvowels", rightward vowels and upvowels together can be called "upward vowels", and vowels in the other directions can be called similarly. The vowels "ㅗ" and "TT" can be collectively referred to as "1-up and down vowels", and the vowels "a" and "sh" can be collectively referred to as "1-left and right vowels". Similarly, "ㅛ" and "ㅠ" can be combined to be called "2-Upward and Downward Vowels", and "ㅑ" and "ㅕ" can be collectively referred to as "2-Left and Rightward Vowels". Among the vowels other than the 10 basic vowels, "ㅔ" and "ㅖ" can be similarly classified.

*Based on the undirected vowels "ㅡ" and "ㅣ", by repeatedly pressing the button to which "ㅡ" is assigned, upward vowels can be input, and downward vowels can be input, and 1- up and down vowels can be input. It can be entered, and both up and down vowels can be entered. Similarly, by repeatedly pressing the button to which the undirected vowel "ㅣ" is assigned, left-handed vowels can be input, right-handed vowels can be input, 1-left-handed vowels can be input, left-right You can also have all vowels entered. It goes without saying that the order of selection according to repeated pressing can be determined in consideration of the dictionary order or the frequency of use. For reference, the frequency order of Korean vowels is "a, ㅣ, ㅡ, sh, ㅗ, TT, ㅕ, ㅐ, ㅔ, ㅢ, ㅘ, ㅚ, ㅛ, ㅑ, ㅝ, ㅟ, ㅠ, ㅖ, ㅙ, ㅞ, It is called the order of ㅒ", and the top 9 vowels account for 90% of the total frequency of use.

First, the method of combining vowels using three vowel elements of "ㅡ", ".", and "ㅣ" based on Figs. 4-5 is currently widely used. Of course, "ㅎ" may or may not be placed on the [0] button. In the current method (the method by vowel stroke combination used by Samsung Electronics), when entering letters such as "Go", "Gyo", "Geo", and "Gyeol", complete Korean characters are not made in the middle of the input. said that there is (Example. When inputting “kyo”, “a => a. Therefore, this problem can be solved by inputting upvowels and leftward vowels by repeatedly pressing "ㅡ" and "ㅣ". For example, if it is defined that an upward vowel is input according to repeated pressing of a button to which "ㅡ" is assigned, "ㅡ" => "ㅗ" => "ㅛ" according to repeated pressing of the button. If you press "1***", it becomes "a => that => high => "kyo". This prevents forms such as "ㄱㆍ" and "ㄱㆍㆍ" from appearing in the middle of input as in the existing method. Likewise, if a leftward vowel is input by repeatedly pressing the button to which "ㅣ" is assigned, "ㅣ => ㅕ => ㅕ" can be made according to the repeated pressing of the button. It can be seen that the convenience of input is higher than in the existing method of inputting "ㅗ", "ㅓ", etc. For the input of the remaining vowels, the existing method, the method proposed in the previous application or the present invention can be used. It can be selectively applied. However, when repeatedly pressing the "ㅣ" button to input left vowels, there is a disadvantage that inputs such as "ㅔ" and "ㅖ" are not natural. Using a combination of equilibrium vowels, "ㅔ = ㅡ+ㅣ+ㅣ ("ㅡ+ㅣ = ㅢ" in the middle of the input)" and "ㅖ = ㅡ+ㅡ+ㅣ+ㅣ" will be possible.

It is possible to input "up and down vowels" by repeatedly pressing the button to which "ㅡ" is assigned. For example, according to repeated pressing of the button to which "ㅡ" is assigned, "ㅡ => ㅗ => TT" (=> "ㅛ => ㅠ") is made. The order in which "up and down vowels" are selected according to repeated pressing can be arbitrarily determined. It can be determined by considering the dictionary order and frequency of use. It would be preferable to first select "1-Upper and Downward Vowels", which are used more frequently than "2-Upper and Downward Vowels", which are used less frequently. Since it is not good for the convenience and intuitiveness of input that the number of repeated presses to input a specific vowel is too large, for "2-up and down vowels", input in a combination of the corresponding 1-up and down vowels and "ㆍ" can make it For example, "ㅛ = [ㅗ+ㆍ] = ㅡ+ㅡ+ㆍ (= **0)". Also [ . . . ] is a decomposition of vowels for better understanding. Here, "ㆍ" can be considered as a vowel element or as a follow-up control. In other words, it is natural to think that there is "ㅛ" as the subsequent alphabet of "ㅗ". That is, after entering "ㅗ", select the subsequent control (in the example, one stroke of the [0] button) to input the subsequent alphabet of "ㅗ" (reference control processing method, chain type control processing method). "ㅛ = [ㆍ+ㅗ] =ㆍ+ㅡ+ㅡ (=0**)", but based on Figs. 4-5, "ㆍ" is displayed in the middle of the input to display complete Korean characters There are things that don't work. "ㅠ = [TT+ㆍ] = ㅡ+ㅡ+ㅡ+ㆍ (= ***0)". Compared to the existing input method, the number of strokes for inputting “ㅠ” increased by one stroke, but since “ㅠ” is a vowel that is not used very often, it does not significantly affect the increase in the total number of input strokes.

Similarly, upvowels can be input by repeatedly pressing the button to which “ㅡ” is assigned, and downvowels can be input by repeatedly pressing the button to which “ㅡ” is assigned. If an upvowel is input, "ㅡ" => "ㅗ", => "ㅛ" in response to repeated pressing of the button to which "ㅡ" is assigned, and if a downvowel is input, "ㅡ" => "TT" => It becomes "ㅠ". In the same way, a leftward vowel or a rightward vowel can be input by repeatedly pressing a button to which "ㅣ" is assigned.

The same can be applied to the button to which "ㅣ" is assigned. That is, if left and right vowels are input according to repeated pressing of the button to which "ㅣ" is assigned, "ㅣ => A => ㅇ" (=> "ㅑ => ㅕ"). For example, when displaying the input value, "ㅣ = #", "A = ##", "sh = ###", . . . becomes like Putting "ㅑ" and "ㅕ" in parentheses means that it may or may not be input. Here, it takes 3 strokes ("###") to input the vowel "sh", which is used frequently. Even for the input of "ㅑ", "ㅑ = [A+ㆍ] = ㅣ+ㅣ+ㆍ (= ##0)" as "ㅕ = [sh+ㆍ] = ㅣ+ㅣ+ ㅣ+ㆍ (= ## #0)". In addition, inputs such as "ㅔ", "ㅐ", "ㅖ", and "ㅒ" are not natural. Of course, the existing input method (Samsung Electronics method) or a combination of vertical/horizontal vowels can be applied to inputs such as "ㅔ", "ㅐ", "ㅖ", and "ㅒ", but inputs that the user should be aware of more rules When using a combination of horizontal/vertical vowels, "ㅔ = ㅡ+ㅣ+ㅣ" and "ㅐ = ㅣ+ㅡ+ㅣ" can be used, but small strokes or short strokes (the first stroke in "ㅔ", "ㅐ There is a bit of unnaturalness about combining the middle stroke from " to "ㅡ". To overcome this, "ㅣ" => "A" => "sh" => "ㅐ" => "ㅔ" according to repeated pressing of the button to which "ㅣ" is assigned, and "ㅒ", " ㅖ" can be entered as a combination of "ㅐ", "ㅔ" and "ㆍ" respectively. Again, there is a disadvantage in that the number of repetitions (eg 5 times) is too large for input of a vowel (eg "ㅔ") that is used a lot. Also, for the input of "ㅐ" and "ㅔ", it is natural to input "ㅐ = [A+ㅣ] = . . ." and "ㅔ = [sh+ㅣ] = . . .", but it is not so. There are also downsides.

In the above additional case, vowels are input using repeated pressing of the vowel button, so to apply the control processing method to the input of modified alphabets (lattice consonants, light consonants, dropped consonants), in combining flat consonants and vowel buttons, One stroke must be added to the maximum number of repetitions for creation. For example, if "ㅡ" => "ㅗ" => "ㅜ" by repeatedly pressing the "ㅡ" button (that is, if it takes up to 3 strokes to input vowels), "ㅋ = A + ㅡ + ㅡ + ㅡ + ㅡ (= 1****)". This is also true in other embodiments. Also, there is a disadvantage in that a large number of repeated presses are required to input one grapheme. As in the repeated selection method, it is always possible to input consonants by repeatedly pressing the consonant button.

It is revealed that the contents described below are the core of this application. Currently, Samsung Electronics' input method and keypad are widely used, and Samsung Electronics is the largest company in Korea, so the applicant's prior application technology using "Korean 3 vowels and their combinations" does not conflict with the existing technology at all. In spite of this, it is a reality that small and medium-sized enterprises without expertise in patents are concerned about adopting the applicant's technology even if they want to adopt it. To this end, the following additional examples are presented.

In the case of using the vowel elements of "ㅡ", "ㆍ", and "ㅣ" suggested above, it was pointed out that the input of "ㅐ" and "ㅔ" was not natural. In addition, there was a point that the number of input strokes increased than before when inputting up and down vowels and left and right vowels by repeatedly pressing the "ㅡ" and "ㅣ" buttons. In the following example, modern Korean vowels "ㅡ", "아", "ㅣ" or "ㅡ", "sh", "ㅣ" are used, and the vowel combination can be input naturally by repeatedly pressing the vowel button. Show examples of possible All keypads in Fig. 4-* were said to be compatible. In particular, in the drawings where "ㆍ" is displayed on the [0] button, and "a" is displayed (or "+", "-A", "H", "ㅋ", etc. are displayed as variations of "A") The [0] button marked with "ㆍ" can be thought of as a button marked with "a", and the user can use the [0] button marked with "a" in "0" by recognizing it as "ㆍ". It is revealed that the [0] button marked with “a” in the example drawing is used to input “ㆍ”, which can be regarded as “vowel element” or “subsequent control”.

In the case of using "ㅡ", "ㆍ", and "ㅣ" presented to explain this embodiment, the same part as in the case will be avoided, and the part that overcomes the case pointed out as a disadvantage will be mainly described. First, it is an example of using "ㅡ", "ㄴ", and "ㅣ". You can input "ㅐ", "ㅔ" by repeatedly pressing the "ㅣ" button. The order selected by repeatedly pressing the “ㅣ” button can be arbitrarily determined. For example, if "ㅐ" is selected first, "ㅐ = ㅣ+ㅣ (= ##)" and "ㅔ = ㅣ+ㅣ+ㅣ (= ###)". Inputting "ㅐ" as "ㅣ+ㅣ" is naturally adaptable from the user's point of view because two vertical lines can be seen in the shape of "ㅐ". As mentioned, the user can imagine that by pressing "ㅣ" one more time after "ㅐ", the small stroke in the middle of "ㅐ" is pushed to the left. For example, "Dog = 1##" and "Crab = 1###".

"ㅒ" is entered as a combination of "ㅐ" and "ㆍ" (the order of combinations can also be arbitrarily determined), and "ㅖ" is entered naturally as a combination of "ㅔ" and "ㆍ". For example, based on FIGS. 4-5, "ㅒ = [ㅐ+ㆍ] = ㅣ+ㅣ+ㆍ (= ##0)", and "ㅖ = [ㅔ+ㆍ] = ㅣ+ㅣ+ㅣ+ ㆍ (= ###0)". Based on Figs. 4-10 to 4-13, "ㅒ = [ㅐ+ㆍ] = ㅣ+ㅣ+A (= ##0)", and "ㅖ = [ㅔ+ㆍ] = ㅣ+ㅣ+ ㅣ+A (= ###0)". In Figs. It's easy to see that you just need to enter it consciously, like a "bet) button". This is also the case below. As another example, "ㅒ = [ㅐ+ㅡ] = ㅣ+ㅣ+ㅡ (= ##*)", "ㅖ = [ㅔ+ㅡ] = ㅣ+ㅣ+ㅣ+ㅡ (= ###*) " can also be done with It can be seen that this also uses the "ㅡ" button as a control button (subscript control or subsequent control). Likewise, the order of combining with the "ㅡ" button is the same as that the "ㅡ" button can be input first or second, as long as it does not conflict with the input value of another vowel. This shows that complex vowels other than vowels input by repeated pressing of the same button can be input by various combination methods.

By repeatedly pressing the button to which "A" is assigned, "A" => "sh" (=> "ㅑ" => "ㅕ") can be entered. That is, "1-left-right vowel" or "left-right vowel" is input by repeatedly pressing the button to which "A" is assigned. The selection order according to repeated pressing can be determined by considering the dictionary order and frequency of use. If up to "1-left and right vowels (i.e., "a", "sh")" are input, this becomes similar to the previously presented <Table 1> and the input method of FIGS. 4-20 and 4-21. Considering the frequency of use of the vowel input by repeated pressing, "A" can be made "A" => "sh" => "ㅕ" => "ㅑ" according to the repeated pressing of the button assigned to "A" is of course Here, too, when inputting vowels such as "ㅑ" and "ㅕ", the number of repeated presses increases. At this time, using the inputs of "ㅑ" and "ㅕ" presented in another embodiment, "ㅑ = [a + ㅡ] (= 0 *)", "ㅕ = [sh + ㅡ] (= 00 *)" Inputting "left and right vowels" by repeatedly pressing the button to which "A" is assigned can be applied in the same way even when inputting using three vowels "ㅡ", "sh", and "ㅣ". There is. Or, by repeatedly pressing the button to which “ㅣ” is assigned, “Left and Right Vowels” including the vowels assigned to the button can be entered by repeatedly pressing the button to which “ㅣ” is assigned, and other vowels can be entered. In addition, by enabling the input of vowels having similar shapes, natural input is possible while arranging the minimum number of graphemes on the keypad. When pressed, "A" is entered, and when pressed twice, it becomes "o". In other words, when the button to which "A" is assigned is pressed twice, the input "A" is entered as "o" in the form of the left and right reversed centering on the vertical line. , The user can easily associate the rule of changing left and right symmetrical when pressing the "a" button twice.

In this way, inputting left-right vowels, left-hand vowels, or 1-left-right vowels by repeatedly pressing the button to which "a" (or "q") is assigned is shown in the form of a graph, as shown in FIG. 4-28. Compared to the existing input method that combines vowel elements, "A", a vowel with a high frequency of use, can be entered in one stroke, while "ㅕ", a vowel with a relatively low frequency of use (or "ㅑ" depending on the selection order) Since the number of input strokes of ") is increased by one stroke, it can be seen that the total number of input strokes is much smaller than that of the existing vowel combination method. In addition, since vowels can be input by repeatedly pressing the same button, it can be said that the convenience of input is also increased. Similarly, when the vowel "ㅗ" or the vowel "TT" is used instead of the vowel "아", it is easy to see that up and down vowels (or 1-up and down vowels) can be input by repeatedly pressing the corresponding button.

If you repeatedly press the button to which "a" (or "sh") is assigned to enter up to 2-left and right vowels ("ㅑ", "ㅕ"), the number of times that you press repeatedly to enter one vowel is high. There is a downside to losing. As suggested in the previous application here, "ㅑ = [A + ㅡ] = A + ㅡ (= 0 *)", "ㅕ = [sh + ㅡ] = A + A + ㅡ (= 00 *)" have. This basically shows that combinations of vowels other than the vowels ("A", "sh") input by repeated pressing can appear in various ways.

In the input of the vowel "ㅘ", it is easy to understand that "ㅘ = [ㅗ + A] = ㅡ + ㅡ + A (= **0)". As described above, it is possible to input up vowels, up and down vowels, or 1-up and down vowels by repeatedly pressing the “ㅡ” button. "Upward vowel or up/down vowel" is written as "up(down) up vowel". Similarly, if you input 1-up and down vowels like "ㅡ" => "ㅗ" => "TT" by repeatedly pressing the button to which "ㅡ" is assigned here, "ㅛ", which is a 2-up and down vowel, is combined with "ㅗ" By combining "ㆍ", "ㅛ = [ㅗ+ㆍ] = ㅡ+ㅡ+a (= **0)", "ㅠ = [ㅜ+ㆍ] = ㅡ+ㅡ+ㅡ+a (= ** *0)", "ㅛ (= 00*)" has the same code value as "ㅘ (= 00*)", so it collides. Therefore, by repeatedly pressing the "ㅡ" button, an upward vowel can be input so that "ㅡ" => "ㅗ" => "ㅛ". That is, "ㅛ = ㅡ+ㅡ+ㅡ (= ***)" does not collide with or overlap with "ㅘ = **0". Downward vowels can be entered as suggested in the previous application (eg, <Table 1> and other examples). For example, "TT = ㅡ+a (= *0)" can be used as "ㅠ = ㅡ+a+a (= *00)".

In the input of the rest of the vowels, "ㅟ = [TT + ㅣ] = TT + ㅣ = *0#", "ㅝ = [TT + osh] = TT + SH (= *0 00)", "ㅞ = [TT+sh+ㅣ] = TT+sh+ㅣ (= *000#) When inputting all up and down vowels with the button assigned "ㅡ", repeat the button assigned "ㅡ" Depending on the press, "ㅡ" => "ㅗ" => "TT" => "ㅛ" => "ㅠ" Inputs such as "ㅛ" and "ㅠ" have the disadvantage of increasing the number of input strokes, but like this In the case of input of the vowel "ㅝ", "ㅝ = [TT+sh] = ㅡ + ㅡ + ㅡ + A + A (= ***00)", and after entering "TT", the vowel "a" appears Since there is no "ㅝ = [TT+sh] = ㅡ+ㅡ+ㅡ+sh (= ***00)", not "ㅝ = [ㅜ+sh] = ㅡ+ㅡ+ㅡ+A (= ***0 )". In other words, after inputting "TT", press the button to which "A" is assigned to enter "ㅝ". 4-12 to 4-14, where "+", "-A", "H", etc., which can be associated at the same time, have the advantage of being able to enter "ㅝ" more naturally. "ㅛ", " As suggested in the embodiment of the previous application, the input of "ㅠ" may be input in a combination of vertical / horizontal vowels "ㅡ" and "ㅣ". For example, "ㅛ = ㅣ+ㅣ+ㅡ (= # #*)", and "ㅠ = ㅡ+ㅣ+ㅣ (= *##)".

Some of the above contents are summarized in tabular form as follows, and summarized in graph form as shown in Fig. 4-29. In inputting one vowel, only some vowel input cases in which the repeated input of the same button does not exceed 3 times are summarized. Not all explanations are organized in tables, and not all contents in tables are organized in drawings. The most important feature in this embodiment is that when trying to define rules for inputting vowels by repeatedly pressing three vowel element buttons, the input of "ㅐ" and "ㅔ", which were the most unnatural and difficult to process, was performed using the "ㅣ" button One point to allow natural input by repeatedly pressing the "A" button, one point to input "A" and "o" by repeatedly pressing the "A" button, or "ㅡ" by repeatedly pressing the "ㅡ" button. , "ㅗ", "ㅛ", etc. can be mentioned. Vowels input by repeatedly pressing the vowel button, which is a key part in this embodiment, are displayed in gray in the graph. In this way, it was shown that the remaining vowels can be input naturally using these vowels that can be input by repeated pressing, and various combination methods are possible for one vowel in the input of the remaining vowels. It is obvious to those skilled in the art that vowel combinations in other embodiments may be selectively or additionally applied as long as they do not conflict in the input of specific vowels, and many variations may occur.

collection collection
decomposition 3 vowels to be combined 4-* Button input value on example keypad One all all 0 2 eh ㅣ+ㅣ ## 3 hey
A+ㅡ A+A+A or
A+ㅡ 000 or
0* 4 this guy ㅑ+ㅣor
ㅐ+ㆍor
ㅐ+ㅡ A+A+A+ㅣ or
ㅣ+ㅣ+A or
ㅣ+ㅣ+ㅡ 000# or
##0 or
##* 5 yes A + A 00 6 to ㅣ+ㅣ+ㅣ ### 7 woman
ㅇ+ㅡ A+A+A+A or
A+A+ㅡ 0000
00* 8 yes ㅔ+ㆍ or
ㅔ+ㅡ ㅣ+ㅣ+ㅣ+A or
ㅣ+ㅣ+ㅣ+ㅡ ###0 or
###* 9 fuck you ㅡ+ㅡ ** 10 ㅘ ㅗ+a ㅡ+ㅡ+A **0 11 ㅙ ㅘ+ㅣ ㅡ+ㅡ+A+ㅣ **0# 12 ㅚ ㅗ+ㅣ ㅡ+ㅡ+ㅣ **# 13 blanket ㅡ+ㅡ+ㅡ *** 14 sob ㅡ+ㆍ ㅡ+A *0 15 ㅝ TT + ㅇ ㅡ+a+a+a *000 16 ㅞ TT + ㅇ+ㅣ ㅡ+a+a+a+ㅣ *000# 17 ㅟ TT+ㅣ ㅡ+A+ㅣ *0# 18 ㅠ ㅡ+A+A *00 19 ㅡ ㅡ * 20 ㅢ ㅡ+ㅣ ㅡ+ㅣ *# 21 tooth tooth #

Another embodiment is further presented as follows. In the above embodiment, "ㅐ" was input by repeatedly pressing the "ㅣ" button, and "sh" was input by repeatedly pressing the "A" button, but "ㅡ", "ㅐ = [아+ㅣ] = . . ." It is natural to think of entering as . Of course, in the embodiment related to Table 7, "ㅐ = [A+ㅣ] = . . ." can also be entered as However, "ㅐ = [a+ㅣ] = . . ." Since it can be input as "ㅣ", it can be input as "ㅣ" => "sh" (=> "ㅔ") by repeatedly pressing the button assigned to "ㅣ". That is, by repeatedly pressing "ㅣ", "1-leftward vowel" is input. Here, "sh = ㅣ+ㅣ (= ##)", so "ㅔ" is a combination of "sh" and "ㅣ", so naturally "ㅔ = [sh+ㅣ] = sh+ㅣ (= ###)" becomes For example, for the input of "1##", it becomes "a => Ki => Big", so the user fills in the small stroke to the left of "ㅣ" (i.e., the negative side) with two strokes of the button to which "ㅣ" is assigned. You just need to familiarize yourself with the entry rules.

Similarly, next, an upward vowel is input by repeatedly pressing the "-" button. That is, "ㅡ" => "ㅗ" => "ㅛ" is entered according to the repeated pressing of the "ㅡ" button. For "1**" input, "a => that => high", so if the user knows only the input rule that the upper (ie, consonant) small stroke is filled in by repeatedly pressing the button to which "ㅡ" is assigned, do. The input of the downward vowels "TT" and "ㅠ" can also be input by the method described in the previous application and other embodiments (eg Table 1). For example, "TT = ㅡ+a (= *0)" can be used as "ㅠ = ㅡ+a+a (= *00)".

For the input of "ㅐ", "ㅐ = [A+ㅣ] = A+ㅣ (= 0#)". The input of "ㅕ", "ㅒ", "ㅖ", respectively, is a combination of "sh", "ㅐ", "ㅔ" and "ㆍ (buttons assigned "a" in " 0" in the example keypad)" You can do this by typing That is, "ㅕ = [sh+ㆍ] = ㅣ+ㅣ+A (= ##0)", "ㅒ = [ㅐ+ㆍ] = A+ㅣ+A (= 0#0)", " ㅖ = [ㅔ+ㆍ] = ㅣ+ㅣ+ㅣ+ㆍ (= ###0)”. Here, "ㅕ = [sh+ㅡ] = ㅣ+ㅣ+ㅡ (= ##*)", "ㅒ = [ㅐ+ㅡ] = A+ㅣ+ㅡ (= 0#*)", " ㅖ = Various combinations are possible, such as [ㅔ+ㅡ] = ㅣ+ㅣ+ㅣ+ㅡ (= ###*). "ㅑ" can be input with two strokes of the button assigned "A" by inputting the modified alphabet of "아" or the subsequent alphabet by the repeated selection method. That is, "ㅑ = A + A (= 00)". Here, you can also see that "ㅒ = [ㅑ +ㅣ] = A + A +ㅣ (= 00#)". The rest of the vowels (complex vowels) can be easily entered using a combination of the previously described vowel inputs. That is, "ㅘ = [ㅗ+a] = ㅡ+ㅡ+a (= **0)", "ㅚ = [ㅗ+ㅣ] = ㅡ+ㅡ+ㅣ (= **#)", "ㅙ = [ ㅗ+a+ㅣ] = ㅡ+ㅡ+a+ㅣ (= *0#)" to "ㅟ = [TT+ㅣ] = ㅡ+ A+ㅣ (=*0#)" to "ㅝ = [TT +sh] = ㅡ+a+ㅣ+ㅣ(= *0##)" To "ㅞ = [ㅜ+sh+ㅣ] = ㅡ+아+ㅣ+ㅣ+ㅣ(= *0###)" can do.

Summarizing the key contents in the above embodiment, input a vowel using three vowels "ㅡ", "A", and "ㅣ", but by repeatedly pressing the button to which "ㅣ" is assigned, "ㅣ", "sh", "ㅔ" or "ㅣ", "sh" (since "ㅔ = ㅇ+ㅣ", it can also be done as "###"), and by repeatedly pressing the button to which "A" is assigned, " Allows input of "a", "ㅑ", and inputs "ㅡ", "ㅗ", "ㅛ", etc. by repeatedly pressing the button to which "ㅡ" is assigned, a vowel that is overall simple and easy to understand. It is an input method. In the end, "ㅡ", "ㆍ", and "ㅣ" were used, and "ㅔ" and "ㅐ", etc., which were unnatural to input vowels by repeated pressing, were replaced by "ㅡ", "A", and "ㅣ". It was shown that the remaining vowels can be input naturally while using a combination of three modern Korean vowels and using repeated pressing. After inputting "ㅡ", the user inputs "ㅗ" by repeatedly pressing the button assigned to "ㅡ" once more, and after inputting "ㅣ", pressing the button assigned to "ㅣ" once more inputs "o". It is easy to understand because it is consistent. Vowels other than the vowels entered by repeated pressing were easy to understand and could be input naturally in various ways. In addition, the rest of the vowels could be input with a combination of the basic vowel and the subsequent control button ([0] button). It has already been described that the user can use the button to which "A" is assigned (a button marked with "A" in the number "0" in the exemplary drawing) in some cases associating with "ㆍ". Some of the above contents are summarized in table form as shown in Table 8, and summarized in graph form as shown in Fig. 4-30. Not all explanations are organized in tables, and not all contents in tables are organized in drawings. In Fig. 4-30, the most essential part, the vowel input by repeated pressing, is marked with gray fill. When there are multiple methods for the same vowel input, it indicates that all of them can be applied or selectively applied. For the intuitiveness of the input method, the case where the same button is pressed three or more times in one grapheme input is summarized, and in the input of a specific vowel, other embodiments are used unless they overlap or conflict with the vowel input method of other embodiments. It is also apparent that the method in can be selectively applied.

collection collection
decomposition 3 vowels to be combined 4-* Button input value on example keypad One all all 0 2 eh A + l A + l 0# 3 hey A + A 00 4 this guy ㅑ+ㅣor
ㅐ+ㆍ or
ㅐ+ㅡ A+A+ㅣ or
A+ㅣ+A or
A+ㅣ+ㅡ 00# or
0#0 or
0#* 5 yes ㅣ+ㅣ ## 6 to ㅇ+ㅣ ㅣ+ㅣ+ㅣ ### 7 woman ㅇ+ㆍ or
ㅇ+ㅡ ㅣ+ㅣ+A or
ㅣ+ㅣ+ㅡ ##0 or
##* 8 yes ㅔ+ㆍ or
ㅔ+ㅡ ㅣ+ㅣ+ㅣ+A or
ㅣ+ㅣ+ㅣ+ㅡ ###0 or
###* 9 fuck you ㅡ+ㅡ ** 10 ㅘ ㅗ+a ㅡ+ㅡ+A **0 11 ㅙ ㅘ+ㅣ ㅡ+ㅡ+A+ㅣ **0# 12 ㅚ ㅗ+ㅣ ㅡ+ㅡ+ㅣ **# 13 blanket ㅡ+ㅡ+ㅡ *** 14 sob ㅡ+ㆍ ㅡ+A *0 15 ㅝ TT + ㅇ ㅡ+A+ㅣ+ㅣ *0## 16 ㅞ TT + ㅔ =
TT + ㅇ+ㅣ ㅡ+A+ㅣ+ㅣ+ㅣ *0### 17 ㅟ TT+ㅣ ㅡ+A+ㅣ *0# 18 ㅠ ㅡ+A+A *00 19 ㅡ ㅡ * 20 ㅢ ㅡ+ㅣ ㅡ+ㅣ *# 21 tooth tooth #

Next, an example of combining vowels using three vowels "ㅡ", "sh", and "ㅣ" is additionally shown. Since it is similar to Table 8 and related examples among the examples in which “ㅡ”, “a”, and “ㅣ” are applied, a detailed description is avoided. In the drawings of 4-* presented as an example, it is considered that " ⓓ" is placed in the [0] button (ie, the [0] button is the "ⓓ" button).

Since the vowel "sh" can be entered with one stroke of the button assigned to "sh", "ㅣ" => "ㄴ" (=> "ㅐ") can be input by repeatedly pressing the button assigned to "ㅣ" . Since "ㅐ = [A+ㅣ]", if "A = ㅣ+ㅣ (= ##)" is entered, naturally "ㅐ = [A+ㅣ] = ㅣ+ㅣ+ㅣ (= ###)" do. It can be entered naturally with the vowel "ㅔ = [sh+ㅣ] = sh+ㅣ (= 0#)". As in the above-described embodiment, "ㅖ = [ㅔ + ㆍ] = ㅔ + ㅣ + ㅇ (= 0 # 0)", "ㅒ = [ㅐ + ] = ㅣ + ㅣ + ㅣ + ㅇ (= ## #0)". "ㅕ" can be input by repeatedly pressing the button to which "ㅕ" is assigned. As "ㅚ = [ㅗ+ ㅣ] = ㅡ+ㅡ+ㅣ (= **#)", as "ㅘ = [ㅗ+A] = ㅡ+ㅡ+ㅣ+ㅣ (= **##)" as "ㅙ = [ㅗ+아+ㅣ] = ㅡ+ㅡ+ㅣ+ㅣ+ㅣ (= **###)" If you set "ㅠ = [ㅡ+ㆍ+ㆍ] = ㅡ+ ㅇ+sh (= *00)", it will collide with "ㅝ = [ㅜ+sh] = ㅡ+sh+sh = (= *00)" All. In this case, "ㅠ" can be set as "ㅠ = ㅡ+ㅣ+ㅣ (= *##)" as a combination of horizontal/vertical vowels. The input of the vowel "ㅠ" as "ㅠ = ㅡ+ㅣ+ㅣ (= *##)" can also be applied to other embodiments.

As another method, as suggested above, by repeatedly pressing the button to which "ㅡ" is assigned, "ㅡ => ㅗ => ㅜ => ㅛ => ㅠ" is entered as up and down vowels, and "ㅘ = [ ㅗ + A ] = ㅗ + A (= **##)", and "ㅝ = [TT + osh] = TT + osh = ***0". The rest of the complex vowels can be processed as the input of the vowels constituting the complex vowel, and a detailed description is avoided.

Examples of other embodiments may be similarly used for the input of the remaining vowels. If the above contents are summarized in a table, it is shown in Table 9, and if summarized in a graph form, it is shown in Fig. 4-31. The biggest feature of the above embodiment is that when combining the remaining vowels using three vowels "ㅡ", "sh", and "ㅣ", "ㅣ" => "A" = by repeatedly pressing the button to which "ㅣ" is assigned. > It is possible to point out that "ㅐ" was input, "sh" and "ㅕ" were input by repeatedly pressing the button to which "sh" was assigned, and, as a result, a natural vowel combination method was suggested. . It was shown that the remaining vowels can be input in various ways using vowels input by pressing once and repeatedly.

collection collection
decomposition 3 vowels to be combined 4-* Button input value on example keypad One all ㅣ+ㅣ ## 2 eh A + l ㅣ+ㅣ+ㅣ ### 3 hey A+ㆍ ㅣ+ㅣ+sh ##0 4 this guy ㅑ+ㅣor
ㅐ+ㆍ ㅣ+ㅣ+A+ㅣ or
ㅣ+ㅣ+ㅣ+sh ##0# or
###0 5 yes yes 0 6 to ㅇ+ㅣ 0# 7 woman o + o 00 8 yes ㅔ+ㆍ ㅇ+ㅣ+ㅇ 0#0 9 fuck you ㅡ+ㅡ ** 10 ㅘ ㅗ+a ㅡ+ㅡ+ㅣ+ㅣ **## 11 ㅙ ㅘ+ㅣ ㅡ+ㅡ+ㅣ+ㅣ+ㅣ **### 12 ㅚ ㅗ+ㅣ ㅡ+ㅡ+ㅣ **# 13 blanket ㅡ+ㅡ+ㅡ *** 14 sob ㅡ+ㆍ ㅡ+sh *0 15 ㅝ TT + ㅇ ㅡ+sh+sh+sh *000 16 ㅞ TT + ㅇ+ㅣ ㅡ+sh+sh+sh+ㅣ *000# 17 ㅟ TT+ㅣ ㅡ+ㅇ+ㅣ *0# 18 ㅠ ㅡ+ㅣ+ㅣ *## 19 ㅡ ㅡ * 20 ㅢ ㅡ+ㅣ ㅡ+ㅣ *# 21 tooth tooth #

Examples related to Table 9 using "ㅡ", "sh", and "ㅣ" correspond to examples related to the contents of Table 8 among examples using "ㅡ", "A", and "ㅣ" to be. As examples using "ㅡ", ㅇ', and "ㅣ", the examples related to Table 7 have many similarities to the contents of Table 7, so a detailed description is avoided and briefly mentioned. "sh => A (=> ㅕ => ㅑ)" can be made by repeatedly pressing the button to which "sh" is assigned. In other words, the left and right vowels are input by repeatedly pressing the "o" assignment button. It is the same as making "ㅣ => ㅐ (=> ㅔ)" by repeatedly pressing the button to which "ㅣ" is assigned. However, since "ㅔ = [sh+ ㅣ] = ㅇ+ㅣ (= 0#)", it is possible to make "ㅣ => ㅐ => ㅒ" by repeatedly pressing the button to which "ㅣ" is assigned. have. When “ㅡ => ㅗ => ㅛ” is obtained by repeatedly pressing the button to which “ㅡ” is assigned (i.e., upvowel input), or “ㅡ => ㅗ => TT (=> ㅛ => ㅠ)” ( That is, (1-) up and down vowel input), "ㅘ = [ㅗ + A] = ㅡ + ㅡ + A (= **00)", but since there is no vowel that "ㅗ" is joined after "ㅗ" It can be done with "ㅘ = **0". The input of the rest of the vowels can be applied similarly, and tables and graphs are omitted.

The characteristics of the above-presented examples (Tables 7, 8, and 9 and related descriptions) are summarized as follows. A vowel is input using three vowels "ㅡ", "ㄴ", and "ㅣ", but a left-right vowel (or 1-left-right vowel) is entered by repeatedly pressing the button assigned to "A", " By repeatedly pressing the button to which ㅣ" is assigned, "ㅣ", "sh", and "ㅔ" are input, or "ㅣ", "ㅐ", and "ㅔ" are input. In addition, in inputting a vowel using three vowels "ㅡ", "sh", and "ㅣ", the point that a left and right vowel (or 1-left and right vowel) is input with the button to which "sh" is assigned, "ㅣ By repeatedly pressing the button to which " is assigned, "ㅣ", "ㄴ", and "ㅐ" are input, or "ㅣ", "ㅐ", and "ㅒ" are input. In addition, while inputting vowels using "ㅡ", "X", and "ㅣ", by repeatedly pressing the button to which "ㅡ" is assigned, upward vowels (or up and down vowels or 1-up and down vowels) are entered. can

In Tables 7, 8, and 9 and related examples, "ㅡ", "ㄴ", "ㅣ" or "ㅡ", "sh", "ㅣ" is a vowel input by pressing once or repeatedly pressing the button assigned It was said that other vowels can be used selectively as long as they do not conflict with vowel input in other embodiments. For example, after entering "TT" in Table 8 (various methods can be applied for the input method of "TT"), press the button assigned to "ㅣ" (the [#] button in the example) once to I entered "ㅟ", pressed it again to enter "ㅝ", and pressed it again to enter "ㅞ". This is natural because "ㅣ", "sh", and "ㅔ" are entered by repeatedly pressing the button to which "ㅣ" is assigned in Table 8. Similarly, after entering "ㅗ" in Table 9 (also, the input method of "ㅗ" may be a method other than the method in Table 9), press the button assigned to "ㅣ" once to input "ㅚ", and once "ㅘ" was entered by pressing more, and "ㅙ" was entered by pressing again. Also, in the embodiment related to Table 9, it is natural that "ㅣ", "아", and "ㅐ" are input by repeatedly pressing the button to which "ㅣ" is assigned. In inputting complex vowels, using repeated pressing rather than pressing the left and right buttons can help improve the convenience of input. Since the input method of "ㅚ", "ㅘ", and "ㅙ" in the embodiment related to Table 9 does not conflict with the input method of "ㅚ", "ㅘ", and "ㅙ" in the embodiment related to Table 8, related to Table 8 In the embodiment, the "ㅚ", "ㅘ", and "ㅙ" input methods in Table 9 related examples can be applied. Likewise, since the input method of "ㅟ", "ㅝ", and "ㅞ" in the embodiment related to Table 8 does not conflict with the input method of "ㅟ", "ㅝ", and "ㅞ" in the embodiment related to Table 8, related to Table 8 In the embodiment, the "ㅟ", "ㅝ", and "ㅞ" input methods in Table 9 related examples can be applied.

Here, if "ㅡ" is inputted by repeatedly pressing the button assigned to "ㅡ", "ㅡ => ㅗ => TT" is obtained by repeatedly pressing the button assigned to "ㅡ". In Table 8, if the "ㅘ" input method ("ㅘ = [ㅚ+ㅣ] = …") of Table 9 is applied, as shown in Table 8, "ㅘ = [ㅗ + A] = ㅡ+ㅡ+A (= **0)", so "ㅛ = [ㅗ+ㆍ] = ㅡ+ㅡ+ A (= **0)". Similarly, "ㅠ = [TT+ㆍ] = ㅡ+ㅡ+ㅡ+a (= ***0)". In Table 8 and related examples, "ㅕ = [sh+ㆍ] = ㅣ+ㅣ+A (= ##0)". In addition, "ㅑ" is entered by repeatedly pressing the "A" button (press twice), and if you solve it, you can see "ㅑ = [A+ㆍ] = A+A (=00)", so overall 2- In inputting four up and down left and right vowels (ㅑ, ㅕ, ㅛ, ㅠ), 1-up and down left and right vowels corresponding to each 2-up and down left and right vowels (i.e., a, sh, ㅗ, TT) and modified alphabet You can see that the control or follow-up controls are entered regularly. Of course, as a control button, a button assigned with "A" (eg, the [0] button with "A" in "0" on the keypad) was used. In Table 8, "ㅖ", "ㅒ", etc. have already been input consistently by combining the corresponding vowels "ㅔ", "ㅐ" and "ㆍ (modified alphabet control or subsequent control)", so overall simple input You can see that it is entered according to the rules. (Of course, "ㅒ = [ㅑ+ㅣ] = …" could also be entered) In the editorial, "ㅔ" and "ㅐ" are called "2-vertical vowels", and "ㅔ" is called "1-leftward + 2-vertical vowels" called "collection". "ㅖ" can be called "2-left + 2 vertical vowels". In addition, "ㅐ" is called "1-centered + 2 vertical vowels" and "ㅒ" is called "2-centered + 2 vertical vowels".

Since it is consistent to press "ㅣ" and press it once more to become "sh" and press the "ㅡ" button once to enter "ㅡ" and then press it again to become "ㅗ", it is necessary to repeatedly press a specific button on the keypad button. It is not necessary to display the input vowels together (eg, display "ㅡ ㅗ ㅜ" together with the [*] button). Of course, it is obvious that all or part of the vowels input by repeated pressing are displayed together on the keypad button also belong to the scope of the present invention. The point where the user can only input "ㅣ", "sh", ("ㅔ") by repeatedly pressing the button to which "ㅣ" is assigned, and by repeatedly pressing the button to which "ㅡ" is assigned, "ㅡ", " ㅗ", "TT" can be input, 1-up, down, left and right vowels and the [0] button in the example drawing (think "ㆍ") 2-up, down, left and right vowels can be input , "ㅘ", "ㅙ" can be entered by repeatedly pressing the "ㅣ" button after "ㅚ", "ㅘ", "ㅙ" by repeatedly pressing the "ㅣ" button after "ㅟ" You just need to be aware of the points you can enter.

If the above contents are summarized in the form of a table, it is as follows, and if summarized in a graph, it is shown in Fig. 4-32. Not all of the information described has been summarized in the table, and not all of the information in the table has been summarized in a graph. In Examples related to Table 9, the "ㅚ", "ㅘ", and "ㅙ" input methods in the Examples related to Table 8 were applied, and 1-up and down vowels (i.e., "ㅡ" were assigned by repeatedly pressing the button assigned). If you enter ㅗ", "ㅠ"), and enter 2-up, down, left, right and left vowels in combination with the corresponding 1-up, down, left and right vowels and subsequent control buttons ([0] button to which "A" is assigned in the example), the table It is almost identical to 10. However, only the part where "sh => ㅕ" is input and the part where "a" and "ㅑ" are input by repeatedly pressing the button to which "sh" is assigned differs. It is not necessarily presented in the form of tables and graphs. As mentioned, "a" is used much more frequently than "q", so it is worse than in Table 10 and related examples.

In Table 10 and related embodiments, it takes 3 strokes (3 strokes of the button to which "ㅡ" is assigned) to input "TT", but since the same button is repeatedly pressed (zero fingering distance), in terms of input convenience It can be seen that there is no significant difference. In addition, among the 9 vowels (a, ㅣ, ㅡ, sh, ㅗ, ㅜ, ㅕ, ㅐ, ㅔ) that occupy the top 90% of the frequency of use, all vowels except "ㅕ" and "ㅐ" (all used About 80% or more of the frequency) is input with a single press or repeated press of a specific vowel button, and a combination of adjacent buttons is used for the input of the remaining vowels (about 20% of the total frequency of use), so the fingering distance of vowel input is greatly reduced. can know that In addition, since "ㅡ", "ㄴ", and "ㅣ", which account for 50% of the total frequency of use, can be entered in one stroke, the minimum number of strokes can be maintained by using the minimum number of buttons (3 buttons). can know that

collection collection
decomposition 3 vowels to be combined 4-* Button input value on example keypad One all all 0 2 eh A + l A + l 0# 3 hey A + A 00 4 this guy ㅑ+ㅣor
ㅐ+ㆍ or
ㅐ+ㅡ A+A+ㅣ or
A+ㅣ+A or
A+ㅣ+ㅡ 00# or
0#0 or
0#* 5 yes ㅣ+ㅣ ## 6 to ㅇ+ㅣ ㅣ+ㅣ+ㅣ ### 7 woman ㅇ+ㆍ or
ㅇ+ㅡ ㅣ+ㅣ+A or
ㅣ+ㅣ+ㅡ ##0 or
##* 8 yes ㅔ+ㆍ or
ㅔ+ㅡ ㅣ+ㅣ+ㅣ+A or
ㅣ+ㅣ+ㅣ+ㅡ ###0 or
###* 9 fuck you ㅡ+ㅡ ** 10 ㅘ ㅚ+ㅣ ㅡ+ㅡ+ㅣ+ㅣ **## 11 ㅙ ㅘ+ㅣ ㅡ+ㅡ+ㅣ+ㅣ+ㅣ **### 12 ㅚ ㅗ+ㅣ ㅡ+ㅡ+ㅣ **# 13 blanket ㅗ+ㆍ ㅡ+ㅡ+A **0 14 sob ㅡ+ㅡ+ㅡ *** 15 ㅝ ㅟ+ㅣ ㅡ+ㅡ+ㅡ+ㅣ+ㅣ ***## 16 ㅞ ㅝ+ㅣ ㅡ+ㅡ+ㅡ+ㅣ+ㅣ+ㅣ ***### 17 ㅟ TT+ㅣ ㅡ+ㅡ+ㅡ+ㅣ ***# 18 ㅠ TT+ㆍ ㅡ+ㅡ+ㅡ+a ***0 19 ㅡ ㅡ * 20 ㅢ ㅡ+ㅣ ㅡ+ㅣ *# 21 tooth tooth #

Vowel input by repeatedly pressing the same button, except for some vowels (e.g., some vowels such as "TT" and "ㅐ" according to the embodiment) among the nine vowels belonging to the top 90% of the above frequency of use. Reduced the fingering distance and improved the convenience of input. In the exemplary drawing, it is obvious that a keypad in which a vowel input by repeatedly pressing a specific vowel button is also applied to the corresponding button, and is included in the scope of the present invention. For example, in an embodiment using “ㅡ,” “ㄴ”, and “ㅣ”, when “ㅣ” and “sh” are input by repeatedly pressing the button to which “ㅣ” is assigned, “ㅣ ㅇ” is input to the [#] button. (or "ㅣ ㅇ ㅔ"), and if "A" or "ㅑ" is input by repeatedly pressing the button to which "A" is assigned, "A ㅑ" is displayed on the [0] button, and "ㅡ" If "ㅡ", "ㅗ", "ㅛ" is input by repeatedly pressing the button assigned to , "ㅡ ㅗ" (or "ㅡ ㅗ ㅛ") is displayed. However, it is one of the Korean vowels taking a geometric shape. , Although there is a high frequency of use, only the basic vowels "ㅡ" and "ㅣ" (up to "a" or "o" according to each embodiment) are displayed on each button, and the vowel input by repeated pressing is hidden. It is one of the characteristics of the present invention that it is easy to understand the input rules while configuring a simple keypad, and it is also a surprising feature of our Korean language that it can do this.

It was said that in the input of lattice and hard consonants, it was possible to input by combining the maximum number of repetitions + 1 stroke for flat consonants and vowel input. For example, if "ㅣ", "sh", and "ㅔ" are entered by repeatedly pressing the "ㅣ" button, it takes up to 3 times to input vowels, so "ㄲ = ㄱ+ㅣ+ㅣ+ㅣ+ㅣ = 1 ####". However, since the number of repeated presses to input one grapheme of the input becomes too large and unnatural, the input of the modified alphabet (lattice consonant, light consonant, dropped consonant) A repeated selection method by repeated pressing or a modified alphabet 3+ other input method can be applied. Of course, "ㄲ = ㄱ+ㅣlength = 1#~" can be done by using "long press" described later, but it is not good to input the character elements necessary for normal Korean input by long pressing because it interferes with the input flow. not. (In the example, "ㅣlength" is a long press of "ㅣ" and "#~" is a long press of the [#] button)

It can be seen that the input of the dropped consonant "ㅎ" does not have a vowel input as "0*" in the examples of Tables 8 to 10. Therefore, if "ㅎ" is assigned to the [0] button, "ㅎ = [ㆍ+ㅡ+(ㅇ)] = A+ㅡ (= 0*)" can be entered. Of course, the dropped consonant "ㅎ" can be entered by repeatedly pressing the button assigned to the consonant "ㅇ", which is considered the basic alphabet, by applying the repeated selection method (two strokes of the button assigned to "ㅇ"). There may be ambiguities. In Table 7, "ㅑ = [A + ㅡ] = A + ㅡ (= 0*)", but if this is not applied (because there are other methods for inputting "ㅑ" in Table 7), the dropped consonant "ㅎ = 0*" can be entered without ambiguity, and if "ㅑ = 0*", "ㅎ = 0**" can be entered without ambiguity. If there is no vowel input with three strokes of the [0] button, it is explained in the previous application that three strokes of the [0] button can be used for input of "ㅎ", and in this case, ambiguity may also occur. The dropped consonant "ㅎ" as an example does not necessarily have to be "ㅎ", and as mentioned in the previous application, among the consonants that do not have lattice and hard consonants, "ㄴ" is set as the basic alphabet and "ㄹ" is the modified alphabet ( Or, it can be regarded as a subsequent alphabet) and "ㄹ" can be left out as a consonant. In the end, it means that the input of the consonant assigned to the button to which "A" is assigned can be entered as "0*", which does not exist as a vowel input value.

Even in the Korean automata of the generalized double keyboard, "ㅢ" is input in combination by inputting "ㅡ" and then "ㅣ". However, since the keyboard is equipped with a large number of vowel buttons, inputting only some vowels such as "ㅢ", "ㅝ", "ㅞ", "ㅘ", "ㅙ", etc. as a combination of vowel buttons (ie, vowel combination rules) is the only difference. Vowel combinations using three vowels ("ㅡ", "ㅣ", "아" or "ㅡ", "ㅣ", ".(araeah)" only differ in that more vowels are entered according to the promised combination. Figure 4-20 is a graph showing the vowel processing process according to the vowel combination based on Table 1. In Figure 4-20, "start" means the start of the vowel processing process. For example, " When 10*..." is pressed, the vowel processing process starts from "0", which is the vowel pressed next to the consonant (i.e., "a = 1"). When [ㅡ] is entered, the system recognizes that the vowel combination process starts when the [ㅡ] button, which is a vowel button that can be combined, is pressed, and the next input value is “ㅇ” when [ㅣ] is pressed, the entire input value [a] + [ㅡ] If [a] is pressed after [a] + [ㅡ], the end of the vowel combination process started from the input of [ㅡ] is recognized and the entire input value is recognized as "pole". It is self-evident.

로 표시된 것은 ㆍ(아래아) 와 "ㅏ"를 동시에 연상시킬 수 있는 장점이 있음도 쉽 게 알 수 있다. Among the contents described above, including the parts different from Table 1, it is summarized again in the form of a graph, as shown in Figures 4-21. In Fig. 4-21, the vowel indicated by dotted line and the vowel indicated by gray fill are overlapping. may or may not apply. Vowel "A" included in some of the single vowels (eg "gam" to "a") or element collections (eg "and" to "a") only at the time of mock input shown in gray fill in Fig. 4-21 It can be seen that it is input by recognizing it as "a", and the vowel "a" used in the other cases is entered by associating with ㆍ (araeah). [0] button

It is also easy to see that what is marked with has the advantage of being able to remind of both ㆍ (araeah) and "a" at the same time.

In program implementation, it will be possible to process the consonants and vowels recognized by the input values on the keypad as input values for the double keyboard Hangul automata program, but in light of the infrastructural nature and various applications of the character input system, It is pointed out that it is not so desirable for precise implementation.

In the above, even if you are not a person in the field, you know Hangul and have basic knowledge of software, you can fully understand this system, but I would like to present a simple flow chart. A vowel button (eg, [0] button) assigned with a consonant (ie, a consonant that has been dropped) is called a "(dropped) consonant assignment vowel button" for convenience. Grid consonants and light consonants are input according to the control processing method (apply input after control, "ㅋ = ㄱ + ㅡ + ㅡ", "ㄲ = ㄱ + ㅡ + ㅡ"), and drop out consonants (eg "ㅎ") Also, input (eg "ㅎ = ㅇ+ㅡ+ㅡ" or "ㅎ = A+ㅡ+ㅡ" or "ㅎ = .+ㅡ+ㅡ") is to be performed according to the control processing method.

In the flow chart of FIG. 4-22, parts (1) to (4) are the same as Hangul automata in the existing generalized two-beol type keyboard, and only the parts (A) and (B) marked in gray are visible. It can be seen that the part reflects the characteristics of the input method according to the power system. Part (B) shows that when a consonant assignment vowel button (eg, [0] button) that cannot be combined is pressed after a series of vowel buttons are input, the input of the consonant assigned to the vowel button is recognized. In FIG. 4-22, the fact that part (B) is marked with a dotted line means that it may be omitted. In Fig. 4-22, if the first input value is the vowel button assigned to the vowel button, it is very simple to process the input of the dropped consonant assigned to the vowel button, so it is not expressed in order to keep the flow chart concise. Likewise, when the vowel button is pressed as the initial input value, the vowel combination process as a letter is not separately displayed for convenience. The flow charts in FIGS. 4-22 generally show that the Hangul input technology and the vowel input technology presented in the present invention can be operated as simply as possible and as easily as possible to understand, and in actual implementation, details are changed and modified. Of course, it can be, and it is obvious that this is also included in the scope of the present invention. For example, it goes without saying that details may vary slightly depending on whether the "Unicode" system or only the "KSC5601 complete" system is used in a computing environment that currently uses the complete text system. For reference, FIG. 4-23 is a drawing in which the characteristic parts ((A) and (B) parts) of this input method in FIG. However, in the part (3) of Fig. 4-22, in the part of checking whether a vowel corresponding to the "vowel combination rule" exists, the vowel combination rule presented in the present invention (Table 1, various graphs and presented in the description of the present invention) It is quite natural that this applies.

Although the applicant has revealed that the vowel input method (vowel combination method) proposed in the present invention can be applied regardless of a specific consonant input method, the flow chart of the case where the repeated selection method is applied to consonant input in nopasim is also shown in Figure 4- equal to 24 The repetitive selection method proposed by the applicant in the present invention and earlier applications (selection in the order of flat consonant - lattice consonant - hard consonant, selection in order of flat consonant - hard consonant - lattice consonant) or modified alphabet 3 + other input method is applied It is obvious that the same can be applied not only in this case, but also in the case of similar (identification of consonants by repeated pressing of consonant buttons - input of consonant buttons does not affect the combination of vowel buttons) when applied with all consonant input methods . In identifying consonants in part (4), consonants can be identified according to a specific procedure for a specific consonant input technology. Part (B) is of course not required. In order to keep the flow chart concise, in case of ambiguity, the part that confirms the previously entered characters using the right arrow [>] button or a specific function button is not expressed, but it is already generalized and widely used, and it is widely used in the art. Everyone knows it, even if you are not a worker, so I don't bother to show it. Likewise, of course, it is possible to use it with the consonant input method of Samsung Electronics Co., Ltd., which inputs consonants by the repeated selection method.

Likewise, in the Korean input system currently employed by LG Electronics, consonants are identified by combining the consonant button, "provisional stroke button" and "byeongseo button" (e.g. "ㄴ = ㄴ + stroke"), similar to this consonant It is obvious that the vowel input technology proposed in the present invention can be applied to the consonant input technology for identifying consonants by a combination of a button and a specific function button. Likewise, the input of the consonant button and the specific function button does not affect the vowel combination. Again, if you simply present the flow chart in this case to the old woman, it is shown in Figure 4-25.

I believe that it has been sufficiently explained so far, but in a system that recognizes consonants and vowels of Korean (Hangul) and processes Korean letters, as mentioned in the previous application, regardless of the specific consonant input technology, the vowel combination technology proposed in the present invention can be used. It is self-evident that it can Also, if you present a flow chart to the old woman, it is as shown in Figure 4-26. As a matter of course, the vowel combination technology of the present invention is applied even when a consonant of a specific consonant input method can be identified when a consonant button or a vowel button or a specific function button is pressed in FIGS. 4-26 (Fig. 4 In (4) part of -26) shows that it can be. Likewise, it is self-evident that it is applicable to all methods of combining Korean vowels by combining three Korean vowels (eg "ㅡ", "ㄴ", "ㅣ") on any type of keypad in which consonants and vowels are mixed and assigned. do. For example, in the case of applying the input of the dropped consonant "ㅎ" with three strokes of the [0] button in the example drawing (it has already been pointed out that ambiguity may occur, that is, the input of the consonant "ㅎ" affects the vowel input It is obvious that the vowel combination method of the present invention can be applied even in a case where it is crazy: it can be solved by a promised time delay or letter confirmation using the [>] button). In this way, even when consonants and vowels are assigned together, and even when consonant combinations affect vowel combinations, it is already widely used, so it is possible to delay the promised time or input a specific function button (e.g. right arrow [>] button). It is obvious that the vowel combination method of the present invention can be applied by intentionally confirming the input letter and processing it as being input in the word start state. In the flow chart of FIG. 4-26, it is already widely known that when the "character end button" is pressed, the contents being input are confirmed and proceeded from the "start" state. When presented again in the form of a flow chart to the old woman, it is the same as in Figure 4-27, and in Figure 4-26, only the part that checks the pressing of the letter completion button is added.

This can be seen as content that specifies that it is applicable to other parts (embodiment) of the contents described in one part (embodiment) of this application, and this contents are also other parts of the present invention (e.g., a collection using four collections). Combination method, etc.) can be applied, of course. For example, as mentioned above, all of the repetition selection method, modified alphabet 3+ other input method, control processing method, etc. are applied to the input of modified alphabets (lattice consonants, hard consonants, dropped consonants, etc.), or input of some consonants It is also obvious that some methods can be selectively applied (eg, grid consonants are input as a control processing method, light consonants are input as a repetitive selection method, etc.) can also be applied together with the present vowel combination method. It is also easy to see that it can be applied to an input system that identifies a specific consonant (promised consonant) by using a "long press" of a specific button as described below. Likewise, as in the input system employed by LG Electronics, even when some consonants are input in combination with a select button and some consonants are input by the repeated selection method (consonant input does not affect vowel combinations) It is also obvious that the vowel combination method of the present invention can be applied. The same applies to the case where the consonant input method of the input system used by LG Electronics is slightly modified to place "ㅅ" on a separate button and input it with one stroke of the button. (Currently, LG Electronics' recruitment system inputs "ㅅ = ㅁ + 喜料")

4.12. Vowel input method using four modern Korean vowels (e.g. "a", "ㅣ", "ㅡ", "sh") and Korean input system using the same

Likewise, as shown in FIGS. 4-18 and 4-19, a Korean input system that processes vowels can be configured using a combination of four arbitrary vowels including "ㅡ" and "ㅣ". For example, four vowels including the frequently used vowels "A" and "sh" may be used. These four vowels have a frequency of use of about 60% of the total vowels. Table 11 is an example of using a combination of four vowels.

Since it can be applied almost the same as the content described in the case of using three vowels, a detailed description is not provided. In Fig. 4-18, the vowel "o" is displayed inside the number "8", and in Fig. 4-19, it is displayed outside, but as before, this is a drawing with the same meaning. As in the examples in Figs. 4-18 and 4-19, if consonants are not assigned to the [8] button [0] button, conversely, consonants are assigned to the buttons to which "ㅡ" and "ㅣ" are assigned. As described above, it can be similarly applied even if there is.

In FIGS. 4-18 and 4-19, the positions (assigned buttons) of the vowels "a" and "o" may be interchanged. In addition, the definition of the vowels combined by the four vowels based on the drawings of FIGS. 4-18 and 4-19 may be defined as a combination in which “a” and “q” are interchanged in Table 11.

The user can use the [0] button to which the vowel "A" is assigned as if it were a button, and the [8] button to which the vowel "◯" is assigned can be used as if it has two buttons. It is easy to associate this with the shape of the number "0" and the shape of the number "8". After the system detects the start state of the vowel processing process, the input value is interpreted as a vowel according to the rules set forth in Table 11.

Similar to the above, in the input of "A", "#0" can also be recognized as "A", and in the input of "o", "0#" can also be recognized as "o" . Similarly, the same applies when an arbitrary vowel (eg vowel "ㅗ", "TT") is used as four vowels together with the vowels "ㅡ" and "ㅣ" instead of "ㄴ" and "sh".

An example of inputting a vowel by combining the four vowel buttons used in modern Korean using four vowel buttons including the vowels "ㅡ" and "ㅣ" and arbitrary vowels "X" and "Y" is as follows. can be like the table. In the following table, the vowels used as vowels "X" and "Y" among the 19 vowels excluding "ㅡ" and "ㅣ" among the 21 vowels in the Korean language are the buttons assigned to the vowels "X" and "Y" respectively. (ie [X] button, [Y] button) It is obvious that each can be input with one stroke.

collection 4 vowels to be combined X Y One all ㅣ+X 2 eh ㅣ+X+ㅣ 3 hey ㅣ+Y 4 this guy ㅣ+Y+ㅣ 5 yes X+I 6 to X+ㅣ+ㅣ 7 woman Y+I 8 yes Y+ㅣ+ㅣ 9 fuck you X+- 10 ㅘ X+ㅡ+ㅣ+X 11 ㅙ X+ㅡ+ㅣ+X+ㅣ 12 ㅚ X+ㅡ+ㅣ 13 blanket Y+ㅡ 14 sob ㅡ+X 15 ㅝ ㅡ+Y+ㅣ
or ㅡ+X+X+ㅣ 16 ㅞ ㅡ+Y+ㅣ+ㅣ
or ㅡ+X+X+ㅣ+ㅣ 17 ㅟ ㅡ+X+ㅣ 18 ㅠ ㅡ+Y 19 ㅡ 20 ㅢ ㅡ+ㅣ 21 tooth

By generalizing this more, you can input a vowel by a combination similar to the table above using any three vowel buttons in Korean. For example, vowels "A", "B", "X", and "Y" can be used as element collections, and the rest of the vowels can be entered in combination similar to the above. It is also obvious that the vowels "A", "B", "X", and "Y" can be input with one stroke of the button assigned to each vowel. For user's convenience and minimization of the number of input strokes, it would be desirable to use four vowels including "ㅡ", "ㅣ" and "아", "sh".

Even in the input of consonants in Figs. 4-12 and 4-13, "ㅎ = 0** = A + ㅡ + ㅡ" and "ㅇ = 8 ** = ㅇ + ㅡ + ㅡ" is the same Here, the frequently used consonant "ㅇ" is assigned to the [8] button together with the vowel "ㅇ", which is inconvenient for input, but the arrangement of the consonant "ㅇ" can be appropriately modified.

An example of a vowel input method using the four vowels of modern Korean is additionally presented as follows. In the case of using three vowels, input "a" and "ㅑ" by repeatedly pressing "ㅣ", and input "TT" and "ㅠ" by repeatedly pressing the "ㅣ" button, while entering the vowels "ㅡ" and " This is an example of inputting the remaining vowels using a combination of horizontal and vertical lines of ㅣ". In the following example, an example of using four vowels " ㅇ", "ㅗ", "ㅡ", and "ㅣ" in order to secure the naturalness of the input rule is as follows. You can naturally input vowels including "ㅗ" or "ㅗ". It is similar to the case of using three vowels, so a detailed explanation is avoided.

collection collection
decomposition 4 vowels to be combined (B) When applicable, not applicable (A) (B) One all ㅣ+ㅡ ㅣ+ㅣ ㅑ(A-3) 2 eh A + l ㅣ+ㅡ+ㅣ 3 hey ㅣ+ㅣ+ㅣ or
ㅣ+ㅣ+ㅡ or
ㅣ+ㅣ ㅣ+ㅡ+ㅡ 4 this guy ㅑ+ㅣ
A+sh ㅣ+ㅣ+sh or
ㅣ+ㅣ+ㅡ+ㅣ ㅣ+ㅡ+ㅡ+ㅣ 5 yes yes 6 to ㅇ+ㅣ ㅇ+ㅣ ㅡ+ㅣ+ㅣ ㅟ(B), ㅠ(B) 7 woman ㅡ+sh 8 yes ㅕ+ㅣ ㅡ+ㅇ+ㅣ 9 fuck you fuck you 10 ㅘ ㅗ+a ㅗ+ㅣ+ㅣ 11 ㅙ ㅘ+ㅣ ㅗ+ㅣ+ㅣ+ㅣ 12 ㅚ ㅗ+ㅣ ㅗ+ㅣ 13 blanket ㅣ+ㅗ 14 sob ㅡ+ㅡ 15 ㅝ TT + ㅇ ㅡ+ㅡ+ㅇ ㅡ+ㅣ+ㅡ or
ㅡ+ㅣ+ㅡ+ㅣ 16 ㅞ ㅝ+ㅣ ㅡ+ㅡ+sh+ㅣ ㅡ+ㅣ+ㅡ+ㅣ or
ㅡ+ㅣ+ㅡ+ㅣ+ㅣ 17 ㅟ TT+ㅣ ㅡ+ㅡ+ㅣ ㅡ+ㅣ+ㅣ ㅔ(B), ㅠ(B) 18 ㅠ ㅡ+ㅡ+ㅡ ㅡ+ㅣ+ㅣ ㅔ(B), ㅟ(B) 19 ㅡ ㅡ 20 ㅢ ㅡ+ㅣ 21 tooth tooth

4.13. A method of inputting a specific (single) vowel by continuous input of a specific button to which a specific vowel element (or collection of elements) is assigned

In the illustrated drawings (Figs. 4-5 to 4-9), it is assumed that the vowel element button is not assigned to the consonant / horn control and the dropped consonant, and is used purely as a vowel element button. Therefore, it is assumed that there is a separate control button or that vowels and horns are selected by repeatedly pressing the button to which the basic consonant is assigned, and that the dropped consonant is selected by repeatedly pressing the button to which the consonant considered as the basic consonant is assigned. .

The frequency of use of vowels in Korean is in the order of "a", "ㅣ", "ㅡ", "sh", "ㅗ", and "TT", and these six vowels account for about 77% of the total. In the input method using vowel elements, it was shown that a specific single vowel can be input by using the vowel element ".", which does not exist as a vowel by itself. Furthermore, in the vowel combining process (from vowel combining start to vowel combining end), continuous input of only the same vowel element button can be detected so that a certain single vowel can be recognized.

When the button to which the vowel element "ㅡ" is assigned is pressed once, the vowel "ㅡ" is recognized, and when pressed one more time in succession, "TT" can be recognized. For example, in inputting “Gum”, “1*05” may be entered as a combination of vowel elements, but “1**5” may also be entered. Similarly, when the button to which the vowel element "ㅣ" is assigned is pressed once, "ㅣ" is recognized, and when it is pressed once more, "A" can be recognized. For example, it means that "1#05" or "1##5" can be used to input "Persimmon".

As described above, when entering a single vowel using the button to which the vowel element "." is assigned, it is recognized as an intermediate process of entering the vowels "sh", "ㅕ", "ㅗ", "ㅛ", etc. Until it recognizes the end of the process, just "." could be output as However, when using the button to which the vowel elements "ㅡ" and "ㅣ" are assigned, the vowel element (or element vowel) "ㅡ By using the property that " does not appear consecutively (i.e. 'ㅡ+ㅡ') and the vowel element "ㅣ" does not appear consecutively (i.e. "ㅣ+ㅣ"), the promised vowel is created even before the vowel combination process is terminated. It can be recognized and output definitively. For example, when inputting "1##(5)", "a => Ki => (=> Gam)" can be displayed according to the input. In the case where it can be reliably recognized in this way, other vowel elements can be additionally combined, as in the case of input by combining vowel elements. That is, in the illustrated FIGS. 4-5, "1**# = ear" and "1### = dog" can be made. If a specific vowel is recognized by repeatedly pressing the button to which the vowel element is assigned in this way and then another vowel element can be combined to form another vowel, the moment the input of the vowel element that cannot be combined is recognized, the previous input Up to the value can be recognized as the end of the vowel combination process, and the current input value can be recognized as the start state of the vowel combination process.

It is also possible to input another single vowel by pressing the button to which the vowel element is assigned three or more times. For example, if a button assigned to "ㅡ" is pressed three times, "ㅠ" may be recognized (here, "Guo" may be input as "Gyu+ㅣ= 1***#") . Similarly, if the button to which "ㅣ" is assigned is pressed three times, as mentioned above, "ㅐ" can be recognized, or "ㅑ" can be recognized (of course, 'ㅐ' and 'ㅑ' are compatible here) If you can't do it, and if you enter 'ㅐ' with 3 strokes, you can enter 'ㅑ' with 4 strokes). Again, "." It is possible to input "ㅕ" with 3 strokes of this assigned button and "ㅛ" with 4 strokes. (Here, it is assumed that the button to which the vowel element "." is assigned is not assigned to the button assigned to the vowel element, but only the vowel element is assigned.) As a criterion, by using the property that the vowel element "." cannot appear more than three times in a row, "1000 = bran" and "10000 = bridge" can be reliably recognized. However, in three or more inputs, there is no great difference in terms of convenience of input or input with a combination of vowel elements, and it is also insufficient in terms of intuitiveness of the input method.

The above results show that the input convenience of some frequently used vowels has been increased. In summary, it can be seen that the repeated selection method was applied with specific vowels (TT, ㅠ, ...) having a similar shape as the subsequent vowels of "ㅡ". Likewise, it can be seen that the repeated selection method is applied with a specific vowel (eg, a, ㅐ, ㅑ, ... or a, ㅑ, ㅐ) as a subsequent vowel of "ㅣ". Similarly, it can be seen that a specific vowel (eg, sh, ㅗ, ㅕ, ㅛ, ...) can be input by the repeated selection method using the button to which "." is assigned. In the method of using four vowel elements, "sh" and "ㅗ" are input by repeatedly pressing the button to which the vowel element "." is assigned, and repeatedly pressing the button to which the vowel element ".." is assigned. You can also input "ㅕ", "ㅛ" by .

In order of "ㅡ, ㅜ, ㅠ, ..." using the button assigned to the vowel element "ㅡ", "ㅣ, AH, ㅐ,..." or "ㅣ, ㄴ, ㅑ" for "ㅣ" , ㅐ, ..." and using the button to which the vowel element "." is assigned to input the vowels "sh" and "ㅗ" starting with the vowel element "." It is intended to give, but it is only an example, and other specific vowels may be input in a different order.

Going one step further, the concept of the present invention can be utilized even in a method other than a method using three or four vowel elements. [ A] button 2 strokes, "ㅕ" can be entered with 2 strokes of the [sh] button, "ㅛ" with 2 strokes of the [ㅗ] button, and "ㅠ" with 2 strokes of the [TT] button. Similarly, it is possible to enter "ㅐ", which is used more frequently, with two strokes of the [a] button. This can also be reliably recognized immediately as input because there is no case where the same vowels appear consecutively among the vowels "a", "sh", "ㅗ", and "TT". If you can input 10 basic vowels like this, you can input the rest of the vowels as a combination of these 10 vowels (e.g. 'ㅝ = TT+sh' or 'ㅝ = ㅠ+ㅣ', 'ㅞ = TT+ ㅇ+ㅣ'). Similarly, it is possible to input other vowels (eg, complex vowels, extended vowels) with three or more strokes of the specific vowel button.

This means that the vowel "ㅑ" can be input by the repetitive selection method with the vowel "ㅑ" as the follow-up alphabet with "아" as the basic vowel, without having a button to which the vowel element "." is assigned. In addition to the convenience of repeated pressing without ambiguity, this input similar to the process of taking notes according to button presses can give a user a sense of familiarity. In addition, even in an input system equipped with 7 vowel buttons by adding a button to which the vowel element "." is assigned, it is possible to input by repeatedly pressing the vowel button or combining it with the vowel element "." For example, "ㅕ" can be input with two strokes of the [sh] button or a combination of the [.] button and the [sh] button.

5. How to overcome ambiguity through indexing

When the repeated selection method is applied, ambiguity may occur because several words are expressed as one code. In the input example of FIG. 4-1, it was pointed out that there is an ambiguity in which “Goi” can be recognized as “Goi” and “Goi” can be recognized as “Goi”. However, words are usually entered word by word. For example, the word "very" exists, but the word "troublesome" does not exist. In Fig. 4-1, both have the same code value. Therefore, the terminal (client) or server prepares an index for words that may cause ambiguity with respect to a specific keypad and a specific alphabet input method, and registers them. When "very" or "troubling" is entered and it is impossible to distinguish between the two even by time delay, etc., if "very" is registered as the correct word in the index, the word the user wants to input (below for convenience referred to as the "target word") is "very much". This is applied only when an ambiguity that the system cannot distinguish occurs, and if it is possible to distinguish by the time delay value defined by the system (terminal-side or server-side system) or the time delay value defined by the user, it is natural to follow it. do. That is, if the user intentionally interrupts (by using a time delay or space, right-moving button or other specific buttons), even if it is a semantically incorrect word, the word is the target word, so "trouble" is entered. " should be output.

As for the method of preparing the index, only the correct word (eg "very" in the example) or the wrong word (eg "highly") can be registered for words in cases where ambiguity may occur. . In addition, it is okay to register both correct and incorrect words, and the system only needs to have information about which words in the index are correct and incorrect.

This can be applied to all cases where the repetitive selection method is applied on the keypad. For example, in the input method of Samsung Electronics in Korea, ambiguity such as "Country <=> Guka" occurs, but it can be applied here as well. In addition, similar to Fig. 4-1, when a pair of consonants is placed on each button and the syllable completion button is pressed in units of syllables (letters) while enabling selection of consonant 1 stroke, aspirated 2 stroke, horn 3 stroke, and vowel 1 stroke can also be applied to When the user inputs "very", even if "noisy" is temporarily output, it can be modified to "very" by referring to the index at the moment the word ends (for example, blank input).

At this time, if the word index exists on both the client side and the server side, the client side index is first searched to try to identify the correct word, and if the identification fails, the server side index is searched secondarily to finally find the correct word Can identify words.

As anyone can think of, distinguishing a unit of a word can be done by identifying a word and an element that distinguishes the word. For example, between a space and a space, between a word start and a space, between a space and the end of an input, between a space and a mode change, etc. can be considered. Determining the correct word by referring to the index is performed on a word-by-word basis, so when inputting an element that distinguishes words, the index reference is made and the correct word can be determined.

This can be applied to all cases where ambiguity occurs by applying the iterative selection method. For example, in Samsung Electronics' method currently used in Korea, ambiguity may occur when the final and initial consonants belong to the same button. For example "country" <=> "gukka". When entering a code by alphabet, input without recognizing the syllable (letter) unit, so in fact, in many cases, if you input "country" unconsciously, it becomes "gukka". Even in this case, if it is not known which of the two words is the target word due to a time delay or the like, the system (terminal or server) can find out the target word by referring to the index. However, in this case, even if the final consonant "a" of "country" and the initial consonant "a" of "ga" are pressed consecutively, in most cases the target word is "country", so the index can be indexed regardless of the time delay. A method of identifying a target word by reference may also be effective.

In addition, it is obvious that this is not limited to Korean and can be applied to all languages in the case of using the iterative selection method. For example, in English input or in English mode of other language keypads, if [2]-[2]-[2] is entered as "AB" or "BA", if ambiguity occurs, "AB" If " is registered in the index as a correct word, it can be recognized and provided as a target word to the user. If a plurality of words in which ambiguity occurs are all registered in the index as correct words, frequently used words may be primarily provided to the user, and the user may finally determine the target word.

If there is ambiguity about the input of a certain word, if all the words corresponding to the input are recognized as correct words even after referring to the index, the user can be given feedback by an appropriate method (visual or auditory) to make a selection. .

A method for allowing the user to determine the target word is to list a plurality of words recognized as correct words in the order of frequency of use (or order of priority) on the display window, and scroll up and down or use the number buttons corresponding to the displayed order. This allows the user to determine the target word. Alternatively, you can display the next most frequently used word by selecting a control (referred to as "next word control" for convenience) to display only the most frequently used word and to display the next word if it is not the target word. And, if it is not the target word, similarly, by selecting the next word control again, the target word can be continuously searched. In this case, after searching for the target word, the target word is confirmed by inputting any other button (for example, selecting another alphabet or pressing any button other than selecting the next word control selection such as blank or mode switch). can

The selection of the next word control can be applied to both the "partial whole selection method" or the "repetitive selection method (standard/simple)" described in the previous application. If it is assumed that the next word control is arranged at the position of the reference grid of a specific button, the next word control will be selected with one stroke of the specific button.

6. simple code Utilization method and shortcut input method/parallel input method

6.1 Alphabet related simple code generation method

When accessing an information system using an information communication terminal, it is essential to input the alphabet. Alternatively, the alphabets to be input may be input by numeric coding. Miniaturized information communication terminals often employ keypad-type interfaces. The code referred to here refers to all types of codes, and representative examples include phone numbers, securities (listed company) codes, city codes, department codes, subway station codes, bank codes, and the like. The advantage of coding and inputting various names is that input can be simplified.

Information communication terminals include all types of information communication terminals such as PCs, mobile communication devices, smart phones, PDAs, interactive texting devices, and ATMs (automated teller machines). In addition, it covers terminals without communication functions, such as electronic notebooks. Information systems include all types of systems, such as systems that can be accessed visually through a GUI, as well as systems that can be accessed only by sound, such as ARS. In addition, the system narrowly means a server-side system, and broadly includes client software of a terminal compatible with the server system.

It can be usefully used for memorizing various codes by using the alphabets arranged on the keypad. In using for memorization of codes, there may be methods by simple naming, initial naming, and full naming. A brief summary of its contents is as follows:

Simple naming is to designate a number associated with a word or phrase to be coded (a word or phrase collectively hereinafter simply referred to as “phrase”) as a code. For example, in the case of Korean, in the case of a company name code, the code of "Gasan Electronics" based on Figure 4-2 is "1799" associated with a, ㅅ, ㅅ, ㄴ as a simple code. In this case, it is possible to make it easier to know the simple code of a specific word by highlighting and displaying the simple code "1799" and the simple code "1799" in "Gasan Electronics". can also be extracted. In the case of simple naming, since a number related to a certain alphabet belonging to a word to be coded is determined as a code, the example code of "Gasan Electronics" does not necessarily need to be "1799". For example, as the simple code of "stock" can be a simple code for the values associated with ㅅ, ㅅ, ㅣ, and ㄹ, in the case of additive electrons, for example, "1729" associated with ㄱ, ㅅ, ㄴ, ㄴ , or "1749" associated with a, ㅅ, sh, ㅅ, or "13294293" associated with the entire alphabet constituting "additional electrons". For convenience, the code associated with the entire alphabet constituting the phrase is called "all related simple naming" for convenience, and the designation of a simple code in association with some alphabets of a specific phrase is called "partially related simple naming" for convenience. In any case, simple naming (i.e., simple code) can be seen as specifying a code in relation to the alphabet constituting the phrase in a phrase unit. This can be applied to languages other than Korean as well. For example, "2786" associated with the consonant "CPTN" in "captain" can be a simple code.

If a consonant-related simple code is generated for a word that starts with a vowel, such as "escape", it becomes "727" corresponding to "SCP", which is the same as the consonant-related simple code of "scape". Therefore, while using an abbreviated simple code, it is possible to think of a simple code that associates the first vowel and consonant in order to minimize duplication of the defined simple code and the corresponding phrase of the simple code, and to add convenience in use. For convenience, this is called "first vowel + consonant standard simple code". This first vowel + consonant related simple code also has the advantage of being able to mechanically generate a simple code for a specific word, like other simple codes.

Not only words but also phrases can be coded by simple naming. "8314" mapped to ㅇ, ㄴ, ㄱ, ㄹ can be used as a simple code by using the letters (syllables) that best imply the meaning in the phrase "Where are you going?" In the case of English, "3886" related to d, t, t, and n having sound values in "date tonight" as an example in the previous application can be used as a simple code.

Initial naming is a special case of partially associated simple naming. In the case of Korean, initial naming may be a method of specifying a number mapped to an initial consonant (first consonant) based on a syllable (letter) as a code. For convenience, this is referred to as "syllable (letter) based initial naming". In the case of "Gasan electron", the initial code by syllable-based initial naming becomes "1799" related to the initial consonant of each syllable (letter). Syllable-based initial naming can also be applied to languages other than Korean. For example, in the case of English, the initial code by syllable-based initial naming of the word "entertainment" may be "3886" associated with e, t, t, and m. Syllable-based initial naming can be more useful in the case of Korean, where one syllable forms one letter. It can be usefully used not only in Korean but also in other languages such as Chinese and Japanese, where one syllable forms one character. In the case of Chinese, the syllable-based initial code of Beijing (Beijing: a 4-tone sign is attached to the first 'e' and a 2-tone sign is attached to the last 'i') is “25” related to b and j based on Figure 1-1. , and is “14” based on FIGS. 10-1 to 10-4.

Similarly, initial naming is possible for phrases. In the phrase “Where are you going?” as an example in the previous application, “81” associated with the first letters of each word, ㅇ and a, can be used as the initial code. In the case of English, the initial code of the word-based initial naming for the phrase "dance with the wolf" as an example in the earlier application is "3979" associated with d, w, t, and w. Word-based initial naming can be usefully used in all languages when codes are assigned to entire phrases.

Simple code (total related simple code, partially related simple code) and initial code (syllable-based initial code, word-based initial code) are collectively referred to as "simple code (i.e. simple code in a broad sense)" or "short code" for convenience do. All-related simple codes, consonant-related simple codes, syllable-based initial codes, and word-based initial codes are especially regular in their code generation, so they can be used universally, and others have created simple codes with such rules. Even if it is easy to use.

Full naming is the input value of a phrase to be coded by a specific character input method. Therefore, this may vary depending on the character input method applied, and can be seen as a code of a numerical value corresponding to a certain phrase in an alphabetic unit. In the case of "Seoul" as an example in the earlier application, the full code by the partial partial selection method (mentioned in the earlier application) is "7745888944" based on Figure 4-2. If the full code by the standard repetition selection method (mentioned in the earlier application) is "7448884". If a keypad different from that in Fig. 4-2 or another alphabet input method is applied, there will be a corresponding full code value.

6.2 Existing Chinese Hanja Input Method

As with the Chinese character input method in Hangul, it is common to enter English corresponding to Chinese pronunciation and select and input the corresponding Chinese character when a Chinese character that can be converted is obtained using a "Chinese character conversion key". In other words, when Chinese Pinyin was entered in the Roman alphabet, the system searched for the corresponding Chinese character and provided it to the user. See Figure 5-1. In Chinese, the full code can be determined based on the English pronunciation of Chinese.

6.3 Unique simple code

If the simple code can be decoded on the client side (ie, when the client side has a specific phrase and a simple code value corresponding to the specific phrase), the phrase corresponding to the entered simple code is transmitted to the server side. can Even if the simple code can be decoded on the client side, if the server side requires a simple code depending on the nature of the application, the simple code itself (ie, a sequence of numbers) can be transmitted to the server side, and the server side can send this simple code. should be interpreted. This means that the decryption of the simple code can be done either on the client side or on the server side.

When a simple code is defined and used for a plurality of phrases, a plurality of phrases corresponding to the same simple code may exist. The ambiguity that may occur between simple codes is referred to as "secondary ambiguity" for convenience. In this case, a unique code value can be created and stored by appending a serial number to a simple code with the same value inside the system, but since the user mainly uses a simple code related to a specific phrase, secondary ambiguity occurs. In this case, it is natural that the system should be able to recommend such phrases to the user according to usage priority. In the case of different phrases but having the same simple code, serial numbers can be used as priorities to recommend to users by attaching serial numbers to the simple codes according to the priority according to the frequency of use of the phrases inside the system. Of course, it is not always necessary to attach a serial number, and the system may have the priority information separately, and this is just an example of how it can be done.

For example, if the simple code of "securities information" is the same as the syllable-based initial code "9196" and the simple code of "sovereign information" is also the syllable-based initial code "9196", according to the frequency of each word A serial number can be attached and the serial number can be used as a priority for recommending to the user. If the frequency of use of "stock information" is high, priority can be given to it, and "stock information" = "91961" and "sovereign information" = "91962". Likewise, if the syllable-based initial code of 先生 (xiansheng: vowel a is the first tone) and student (xuesheng: the first e is the second tone) are the same as “97,” serial numbers are added according to the frequency of use of each word. You can use that serial number as a priority. If the frequency of use of 先生(xianshen g) is higher than that of student(xuesheng), you can set 先生(xiansheng) = 971 and 學生(xuesheng) = 972. The simple code generated by adding a serial number in this way is called "unique simple code" for convenience, and the simple code with redundancy without attaching a serial number is simply called "simple code", and both are encompassed and also called "simple code". code".

In the example of 先生(xiansheng) and 學生(xuesheng), if the user only inputs “97”, the system can provide 先生(xiansheng) and 學生(xuesheng) to the user, let the user double-select, If it recognizes this from the beginning and inputs "971", the system can recognize it as "先生(xiansheng)".

Here, by emphasizing and displaying "x, s" used as the basis of the syllable-based initial code, a better visual effect can be given to the user. One of the methods of emphasizing and displaying is a capital letter such as 先生 (XianSheng). It is to be displayed as .. Further, the system may interpret the simple code “97” from the capitalized words.

6.4 Use case of simple code

An example of assigning a simple code (syllable-based initial code) to a city name is as follows. This can be usefully used in railway information systems and the like.

. Seoul = 78, Suwon = 78, Daejeon = 39, Sintanjin = 739, . . .

Here, since Seoul and Suwon have the same syllable-based initial code, in order to avoid this, simple codes such as "Seoul = 781" and "Suwon = 782" can be uniqueized by attaching serial numbers in the system. If the user transmits only "78" to the system, the system gives appropriate feedback (for example, provides a list of Seoul and Suwon or informs by voice), and allows the user to select one of Seoul and Suwon. If the user recognizes this from the beginning and inputs "781", the system can recognize it as "Seoul".

If the server side system does not require the simple code "78" but the word "Seoul" itself, the client side interprets the simple code "78" and transmits "Seoul" to the server side. Alternatively, even if the client side can interpret the simple code, if the server side requires the simple code itself according to the nature of the application, the input simple code itself can be sent to the server side.

As another example of giving a simple code (full associated simple code, syllable-based initial code, consonant-related simple code, first vowel + consonant-related simple code) for city names, based on Figure 1-1, Beijing (Beijing ), the syllable-based initial code is “25” related to b and j, the overall related simple code is “2345464”, and the consonant related simple code is “2564” related to b, j, n, and g.

Again, an example of a securities issue (listed company) is as follows. This can be usefully used in various stock information systems.

. Dongwha Pharmaceutical = 3098, Digital Chosun = 39397, Hantong Freetel = 83643, . . .

Here, for example, in the case of "Digital Chosun", a better visual effect can be given to the user by emphasizing and displaying "c, ㅅ, ℓ, ㅅ, ㅅ" used as the basis of the syllable-based initial code.

An example of a bank code is: This can be useful in ATMs and various financial information systems.

. Kookmin (bank) = 14, Hana (bank) = 82, . . .

Here, it is obvious that the predefined simple code can be used for phrase input by interpreting the predefined simple code on the client (terminal) side when the user inputs it and showing it to the user. This is called a "short-cut input method" and will be described in detail with the "parallel input method" next.

6.5 Automatic reassignment of priorities based on frequency of selection

Furthermore, although the priorities of "securities information" and "sovereign information" were initially designated as 1st and 2nd respectively, if a specific user selects "sovereign information" significantly more, the priority of "sovereign information" can be adjusted to be higher than the priority of "securities information". As explained, there are various methods, but it can be realized by changing the serial number. If priority information is separately provided in the system, it is possible by changing the priority information.

The criterion for determining whether or not the number of times of selecting "sovereignty information" is remarkably high can be determined by the system or (re)designated by the user. As an example of such a criterion, if selection is made differently from a pre-specified priority 8 times or more out of 10 times, the existing priorities may be automatically corrected. Depending on the option, the user may be asked to confirm the correction.

The same can be applied to other languages, and the same can be considered when “sovereign information” and “stock information” are changed to “senior (xiansheng)” and “learning (xuesheng)” respectively in the above case.

6.6 Simple code automatic designation and simple code related alphabet display

In particular, consonant-related simple codes, syllable-based initial codes, and word-based initial codes, in addition to all related simple codes, have regularity in simple code generation as described above, so when a user designates a simple code for a specific phrase, simple code is generated If a specific phrase is entered in the state of designating a rule, the corresponding simple code can be automatically extracted and stored in the system. In addition, by emphasizing and displaying the alphabet related to the simple code, the convenience of use can be increased. In the case of English, the alphabet related to the simple code is highlighted and displayed, and it can be displayed by using capital letters.

Also, in the previous application, "shortened input method" and "shortened/full parallel input method" were suggested. A simple code for short input may be defined by the system, the user may change it, and the user may designate a simple code for a new phrase.

In determining a simple code for a new phrase, simple code generation rules such as total related simple code, partially related simple code, consonant related simple code, syllable-based initial code, and word-based initial code introduced in the previous application can be used. . For example, in generating a simple code for "dance with the wolf", if the user wants to use a word-based initial code as a simple code, enter "dance with the wolf" in the simple code creation mode, and The word-based initial code "3983" must be entered. Similarly, when generating a simple code for “securities information”, if you want to use a syllable-based initial code as a simple code, you must enter “securities information” and “9196” in the simple code generation mode.

However, if the user designates a simple code for a specific phrase, the user stores the type of simple code desired by the system and inputs the phrase to generate a simple code, without having to enter the code for the specific phrase. A simple code can be assigned automatically. In the above example, by setting the system to use a syllable-based initial code and entering only "securities information", the simple code for "securities information" can be automatically designated as "9196". Similarly, by setting the system to use a syllable-based initial code and entering 先生 (xiansheng), the simple code for 先生 (xiansheng) can be automatically designated as “97”.

In the case of English, it was said that capital letters can be used to highlight and display the alphabet to be used as a simple code. Therefore, the simple code designation method can be set in advance to use uppercase letters as simple codes, and when "DaTe ToNignt" is input, "3886" corresponding to uppercase letters "DTTN" can be automatically designated as simple codes, or "ToNignt ShoW" " When inputting, "8679" corresponding to the capital letter "TNSW" can be automatically designated as a simple code.

6.7 Shortcut input method and parallel input method of phrase using simple code

When entering a simple code (initial code is a special case of simple code, unless otherwise specified, it is included in simple code), the system (client-side system or server-side system) uses the phrase corresponding to the simple code can be recognized and processed. Therefore, it is natural that if a phrase corresponding to a specific simple code is recognized and shown to the user again, it can be used for word input.

In fact, in the foreign alphabet input method, the index with “all related simple codes” assigned to each word is stored in the terminal (client-side system), and when the user enters the code, the corresponding word is displayed according to the priority of each word, and the target It implements a character input system by allowing words to be confirmed. For this, you can refer to two Internet sites, http://www.tegic.com and http://www.zicorp.com. For convenience, this method is referred to as "all-related short-cut input method" or "foreign method" in the present invention. Or, since the representative input system using this approach is Tegic's “T9”, it will be called “T9LIM: T9 Like Input Method”. Figure 5-2 shows an example of input in Tegic's T9 system. As shown in Fig. 5-2, in order for the user to input meet, “622 … ” is entered, the system initially provides “off” to the user, but when “6228” is entered, “meet” is displayed.

Comparing Tegic's and Zi's method with the alphabet input method on the keypad proposed by the applicant, the applicant's alphabet input method assigns a unique code to each alphabet unit, and it is possible to input the target alphabet or target phrase by the full code. In the foreign method mentioned above, a simple code associated with the whole is given in word units, and the target word can be input by the simple code.

The disadvantage of the foreign method is that only predefined words can be entered by giving a code in word units, and if it is a different word but has the same code, you can use a toggle button or a move button to input a word that is not frequently used. It is not easy to input by selecting and confirming the target word, a word other than the target word may temporarily appear during input, and it takes up a lot of storage capacity of the system and requires a lot of cost to implement.

Here, it is pointed out that a simple code (partial association or total association) is assigned to a common phrase (a concept including both a common word or a common phrase), and a target phrase can be input using the simple code. Simple codes for common phrases may be pre-defined in the system and provided to users, or the user should be able to designate them as a matter of course. Alternatively, the user should be able to arbitrarily modify the simple code previously defined in the system. The fact that the user can arbitrarily designate has the advantage that the user can easily know the simple code value for a specific common phrase.

In the present invention, the method of inputting a target phrase using a simple code (including all of partially related simple codes, fully related simple codes, and initial codes) is called a "short input method" for convenience, and a method of inputting a target alphabet by a full code For convenience, it is called "full input method" in comparison to the short input method. In addition, as described below, the shortcut input method and the full input method can be applied in parallel, and for convenience, the method of applying the shortcut input method and the full input method in parallel is called "shortened/full parallel input method" or simply " It will be called "parallel line input method".

Among the full input methods that give a unique code in alphabetical units and input the code to input the target alphabet, the ambiguity caused by using the iterative selection method is called "primary ambiguity" or "alphabetic ambiguity" for convenience. to call On the other hand, in the method of assigning a code to every word and enabling the input of a target word through this code, as in the foreign method, there is an ambiguity in which several different words exist for the same code. It will be called "secondary ambiguity" or "word ambiguity". In the present invention, ambiguity simply means primary ambiguity.

For a specific input value, it is primarily interpreted as a simple code (i.e., the short input method is applied first or the short input mode is applied as the basic input mode), and if there is no simple code corresponding to the input value, the full code is secondarily It is possible to construct scenarios such as recognizing (i.e., secondarily applying the full input method), and conversely, inspecting whether the full code is primarily formed for the input value (i.e., applying the full input method primarily or default Scenarios such as application of full input mode as input mode) and recognition as simple code if full code cannot be formed (i.e. application of shortened input method secondarily) are possible. Interpreting the input value primarily as a simple code can be seen as applying the "shortened input mode" as the basic input mode, and on the contrary, interpreting the input value primarily as a full code sets the "full input mode" as the basic input mode. can be seen as applied. For users who mainly use common phrases in character input, it is desirable to first apply the short input method (ie, use the short input mode as the basic input mode), and for users who do not, first apply the full input method (That is, use the full input mode as the default input mode).

Here, when the basic input mode is set to the full input mode, the input value is primarily regarded as a full code and interpreted, so even when a simple code is input, the input value can form a full code, and the user can A word other than the target word may be input. For example, in the case of applying the standard repetition selection method as the full input method in FIG. 4-2, the simple code of the word "corn" is set to "877" (using the syllable-based initial code), and the primary is regarded as a full code, so it can be recognized as "Yeo". This happens in cases where the initial consonants of the second and third letters correspond to the same button, such as "corn", "corn", "inexhaustible", "warreu", "excellence", "wajangchang", and "udangtang". Conversely, when the short input mode is set as the basic input mode, the input value is primarily regarded as a simple code and interpreted, so even if a full code is input, it can be recognized as a word other than the target word. That is, this is the ambiguity between the simple code and the full code, which will be referred to as "third-order ambiguity" for convenience.

Even in the case of this third ambiguity, it can be overcome by the toggle method or the method of selecting from the list, similar to the existing method. Alternatively, there may be another method, which is to switch from the full input mode to the short input mode or from the short input mode to the full input mode on a word-by-word basis before inputting an input value that can cause ambiguity. As suggested in the applicant's earlier application, this is done by selecting a hiragana / katakana conversion control in word units with the "A / A" control, inputting one word in katakana in hiragana mode or inputting one word in katakana in katakana mode It's similar to being able to do it. For example, if the basic input mode is the full input mode, the system recognizes the input value as a simple code from the beginning and returns to the input value by referring to the index. The corresponding target word can be provided to the user. Similarly, when using the short input mode as the basic input mode, the input value entered after selecting the "short/full" control can be recognized and processed as full code from the beginning. The "short/full" control may be entered either before or after the target word, but in this case, it would be convenient to make it enter first.

When applying the parallel input method, the determination of whether the input value is full code or simple code can be made in word units as if referring to the index to remove the first ambiguity, or whether the input value is full code in the middle of input as follows. It may be judged whether it is a simple code.

When the full input method is set as the basic mode and the parallel input method is applied, every time each code is input, whether the input value forms a full code is checked, and at the point when it is judged that the full code cannot be formed, the input value is changed to a simple code It is possible to double the efficiency of the parallel input method by referring to the simple code index and showing the corresponding phrase to the user. Likewise, when the parallel input method is applied as the default mode, the input value and the index are compared for each code input, and the moment it is confirmed that there is no word matching the input value in the index, it is set in the full input method. It can be judged and processed with the full code of This means that the third-order ambiguity occurring in the middle of input can be removed at the beginning of input by applying the rules in each full input method. This can also be applied to the case of using an alphabet input method not suggested in the previous application as a full input method. For example, based on the pool input method (standard repetition selection method, partial selection method) presented in the previous application, it is as follows.

In the case of Korean, for example, when the standard repetition selection method is applied based on Figure 4-2 as a full input method, the second and third input values of all syllables by full code must always have the same value. If these conditions are violated, the input value can be determined as a simple code and processed. When processing double consonants as a combination of basic consonants is allowed, the corresponding criteria can be applied. This is applicable in all cases where the standard iteration method is applied.

In addition, in all languages, when the partial selection method is applied as the full input method, two input values correspond to one alphabet, and the second input value is limited for the first input value of the two input values have. For example, in the case of English, when using only the combination of left and right straight lines as shown in FIG. ) is used as the first input value corresponding to one alphabet, the values that can come as the second input value are also the buttons in the first row ([1], [2], [3]). Likewise, if [2]+[1] is input and then the buttons ([4], [5], [6]) of the second row are input again, the value that can come next to form the full code is also the second row It is one of the buttons ([4], [5], [6]) of The moment the input value violates this, the system regards the input value as a simple code, and can recommend words corresponding to the simple code to the user according to priority. For example, as shown in FIG. 5-3, in the parallel input method in which the partial selection method is the full input method and the full input method is the basic input mode, when the user inputs the simple code of “help” as 4357, the second The moment input value 3 is entered, the system recognizes that the input value does not form a full code, and can treat the input value as a simple code and process it.

If the partial-total selection method is applied to FIG. 4-2, the next button that can come to the input of the first [1] button to form a full code is only the [1] or [2] button. If this is violated, it is determined that the input value is a simple code rather than a full code, and the target word corresponding to the input value can be recommended to the user according to the priority by referring to the index. As shown in Figures 1-3, when the four alphabets of P, Q, R, and S are assigned to the [7] button, as pointed out in the previous application, one of the four alphabets is placed in a lattice that forms an upper and lower adjacent combination. And even in this case, if the [7] button is input to form a full code for one alphabet, the button that can come next is the button in the third row ([7], [8], [9] ) or a top-bottom adjacent combination button ([4] button), so if this is violated, the input value can be processed as a simple code. This is applicable to all languages when applying the partial-total selection method presented in the earlier application.

For example, in the state where “25” is stored as the syllable-based initial code of Beijing (Beijing) simple code in the simple code index based on Figure 1-1, use the full partial selection method as a full input method, When the user inputs “25” with the full input mode as the default input mode, the system first inputs [2] and then inputs [5], the input value “25” becomes the full code. cannot be achieved (because the button of the left and right straight combination that can come after [2] is one of [1], [2], and [3]), and refer to the simple code index to enter the input value “25 “Beijing” corresponding to “Beijing” can be provided to the user. In the case of Chinese, it is possible to provide the user with a Chinese character (漢字, 北京) as a phrase corresponding to the specially illustrated simple code “25” (because the Chinese character “北京” is the target word). In a language using phonetic characters other than Chinese, the system will provide “Beijing” corresponding to the simple code “25” to the user. If there are several phrases corresponding to the simple code “25”, it is provided in the form of a list or by repeatedly pressing a specific button (by a toggle method), the user can select the phrase he wants. Fig. 5-4 see

After all, applying the parallel input method as shown in Fig. 5-4 registers simple codes for frequently used words such as “北京 (Beijing)” in the index, and uses the general full input method and short input simultaneously without mode switching. However, when entering a word registered as a simple code, it is possible to enter it with a small number of strokes.

In the case of Figures 4-5, since only one basic consonant is assigned to each button, when using a syllable-based initial code that can be used universally in Korean as a simple code, the shortened input method and the full input method are applied in parallel It also has good properties that allow input without third-order ambiguity. In other words, when the parallel input method is applied, if the user inputs the syllable-based initial code, the input value cannot form a full code from the second input (in case of entering the consonant and aspirated consonant by the control processing method), so the index of simple code It is possible to search for and recommend appropriate words according to the priority to the user. The case of full code input is the same.

As mentioned above, one of the "cores" of the present invention is to be able to determine whether an input value is a simple code or a full code in the middle of input when the parallel input method is applied. This applies not only to the case of using the full input method proposed by the applicant, but also to the case of using other full input methods. For example, there is a method of inputting alphabets by combining a first button assigned to each alphabet and a second button corresponding to the rank of the alphabet in the first button. That is, in FIG. 1-1, P = [7] + [1] was input. In this case, the second button becomes one of the [1], [2], and [3] buttons in Fig. 1-1, so the moment the input value violates this rule, the system considers the input value as a simple code that can be dealt with. In particular, the full input method proposed by the applicant has a good characteristic in that it is easy to know whether the input value forms a full code even in the middle of input when the parallel input method is applied as in the example above.

Also, as mentioned in the prior application of the applicant, interpreting the simple code or the full code may occur on the client side or on the server side. And in looking up the index to overcome the primary ambiguity (alphabetic ambiguity) in the previous application, interpreting the simple code or full code in the scenario that primarily refers to the index on the client side and secondarily refers to the index on the server side It can also be applied in Conversely, it is also possible to refer primarily to the server-side index and secondarily to the client-side index. In addition, the input value is interpreted as simple code first, and the index on the client side is firstly referred to, and the index on the server side is secondarily referred to. However, it is possible to analyze primarily on the client side, and secondarily on the server side if the client side does not have such an analysis function. As another example, it is possible to interpret the input value primarily as a simple code, but refer to both the client-side index and the server-side index, provide it to the user, and allow the user to select the target word. In this way, a similar transformation is possible in applying the analysis method (simple code, full code) and analysis place (client side, server side). In other words, in summary, various combinations are possible in the application of analysis methods (simple code, full code) and analysis places (client side, server side). That is, the order of (A)-(B)-(C)-(D) or the order of (A)-(C)-(B)-(D) in FIG. ), (B), (C), and (D).

The advantages of applying the short input method and the full input method in parallel are as follows. First of all, since the full input method can be used, the user can input all words, even words that do not exist in the dictionary other than predefined words, and simple codes for using the short input method for common phrases are provided for convenience (partial association /all related) can be specified, and the number of input strokes can be significantly reduced by specifying a partial related simple code. In addition, there is an advantage in that word-based initial codes can be assigned not only to words but also to phrases. However, foreign methods use word-based indexing for all word input, so in order to minimize the case in which the same code is assigned to different words, a fully associated simple code has to be used.

In addition, the system must have an "index" that has a specific common phrase and a code value for that common phrase, which requires a much smaller storage space than foreign methods that have an "index" for all words. do. And this "index" should have an "index" for the correct word or an "index" for the wrong word for words that may cause ambiguity in order to eliminate ambiguity. can be used jointly.

Since consonants have the phonetic value of a specific word in all languages, the technique of extracting consonants to create abbreviations has already been widely used. In the case of English, for example, extract the consonant "CPT" having a phonetic value from "captain" among military terms and use it as an abbreviation, use "PVT" as an abbreviation in "private", and use "SG T" in "sergent" " as an abbreviation, "SSG" as an abbreviation in "staff sergent", and SFC as an abbreviation in "sergent first class", and so on. Of course, the examples of "captain" and "private" each consist of two syllables, but the consonants extracted as abbreviations here can be seen as consonants representing each syllable. Therefore, in the case of "captain", "278" related to "CPT" can be designated as a simple code.

In this way, being able to apply the shortened input method by specifying partially related simple codes for common phrases arbitrarily based on syllables is significant in addition to reducing input effort. Phonetically, syllables are defined as "psychological entities". Also, it is consonants that have phonetic values in syllables. In the case of extracting only the vowel "AAI" from the example captain, it is almost impossible to infer the captain. However, the captain can be easily inferred by extracting the consonants "CPTN" or "CPT". It is said that in an English sentence, even if vowels are removed for each word and only consonants are listed, the original sentence can be inferred. In other words, the use of partially associated simple codes in relation to each consonant, which is the subject of a syllable, means that the user can naturally adapt to the shortened input method and can provide convenience to the user.

In particular, in the English-speaking world, it is common to use abbreviations, and in the case of listed company names, a certain number of abbreviations are designated, so simple codes can be utilized based on these abbreviations.

Allowing the user to designate a simple code (partial association, total association) for a specific phrase has the advantage of making it easy to remember the code value for the common phrase. Furthermore, if a user needs only a small number of common phrases (for example, using only 10 or less common phrases), codes related to alphabets of common phrases are not necessarily assigned, but only for each phrase 1, 2, 3, . . . A simple code can be given, such as

6.8 Simple code/corresponding phrase grouping and designation of search range

If a simple code is specified for a large number of phrases, there is a possibility that a lot of redundancy may occur. By grouping the phrases corresponding to the simple code and searching for a simple code only for a specific phrase group, ambiguity between simple codes (secondary ambiguity) ) can be reduced. A phrase does not necessarily belong to only one group, but may belong to several groups.

For example, simple naming phrases can be listed company names, city names, common phrases, … Groups such as common phrases can be grouped into sub-groups such as social field, political field, etc., and grouped in tree form. In this example, 2-step tree-type grouping is presented, but tree-type grouping is possible with 3-step, 4-step, or more steps. See Figures 5-6. If the user (or the system) limits the simple code search range to the listed company name group, when a specific simple code is entered, the system searches for the named phrase corresponding to the entered simple code only in the category of the listed company name group. It can reduce ambiguity. Likewise, if the search range is a common phrase, it can be made into a search range including all subgroups below the common phrase group. If the social field group of the common phrase group is designated as the search range, only the groups below it (in the tree-type group structure) including the social field will be the search range.

The tree-type group in Figs. 5-6 can be thought of as a folder in Windows explorer. The search range may be automatically reassigned by the system. For example, when a hierarchical structure of administrative districts is stored as subgroups of city names, and the user selects a specific city, the search range for the next input value is, of course, the name of the sub-administrative district unit of the specific city. will be For example, after the user selects “Seoul” among cities, the next selection range is “Gu” in Seoul, and once the user selects “Yangcheon-gu” again, the next selection range is “Gu” in Yangcheon-gu. Dong” will be.

6.9 Utilization of relay server

Interpretation of the simple code may be performed on the client side or the server side. Decryption of such simple code (including full code in some cases) is dedicated to providing phrases corresponding to the simple code to the client side or other server side. A relay server can be provided. Reference may be made to Figure 6-1. In addition, in FIG. 6-1, if the client side first decodes the simple code and fails to interpret the phrase corresponding to the input simple code, the relay server secondarily interprets and interprets the phrase corresponding to the input simple code. In case of failure, it is possible to interpret the phrase corresponding to the simple code input from each server in a third way. The tertiary simple code decryption server (referred to as "tertiary server" for convenience) becomes a server loaded with an application using the input simple code or a phrase corresponding to the simple code.

If there is a relay server, even if the tertiary server side requires a phrase other than a simple code, the user enters the simple code, and the tertiary server side does not store the simple code and the phrase corresponding to the simple code. In this case, it is possible for the relay server to interpret the simple code input from the user and deliver the phrase corresponding to the simple code to the tertiary server.

Whenever each code value of the simple code is entered, the index corresponding to the simple code is searched and the feedback can be given to the client side or each server side, or it can be given in word units.

6.10 Classification of word units

In the present invention, a word unit means from the beginning of a word to the end of a word. This can be identified through the combination of all elements (word start, space, mode change, enter, …) that can distinguish words from words. For example, space ~ space, space ~ mode switching, etc. can identify that a word is input through word start ~ word end, etc. Giving feedback in word units can be sufficiently implemented through a language that supports the current network environment.

6.11 Simple code/corresponding phrase download

Furthermore, it is possible to download the simple code on the server side and the phrase corresponding to the simple code to the client side without the user directly inputting and storing it.

The unit to be downloaded can be downloaded in units of individual phrases, or in groups of phrases (tree structure group) as exemplified above. If you select a higher group, you can download lower groups as well. It can be downloaded while maintaining the tree structure of the server-side phrase group, or phrases belonging to the corresponding group and subgroups can be downloaded as a group designated by the user on the client-side. If there is a relay server whose main function is decryption of simple codes, the relay server may be in charge of this function.

7. Input of symbols

As suggested in the previous application, it was explained that the native language alphabets could be arranged in "an order close to the standard grid", and then numbers and English alphabets could be arranged. It has been explained that native language alphabets and numbers can be selected. Similarly, in applying the subsequent control processing method, numbers and English alphabets as well as native language alphabets belonging to a specific button can be input through the subsequent control processing method.

In the present invention, the present invention goes one step further and presents a method (that is, by a hidden control processing method) that can efficiently input various symbols, etc., which were displayed on the keypad in the previous application so that they can be input do.

That is, "symbol control" is placed in an appropriate grid among the grids in which controls are arranged in the previous application, and symbols are input by combining symbol controls and buttons that can signify symbols (buttons other than control buttons). Here, as an example of a button that can mean a symbol, in the case of a period, "ㅁ" can be easily associated with the period, so it becomes the [5] button.

For example, in the Korean language embodiment (Fig. 4-2) among the inventions of the previous application, the symbol control can be placed in a grid position that can be selected by pressing the [*] button twice in succession. In other words, it is to establish a relationship between representative alphabets and subsequent alphabets, such as ㄱ (representative alphabet), ㅋ (2nd), symbol (3rd), .... In the case of control pre-input, when entering "period", ㅁ = {symbol} + ㅁ = [*]+[*]+[5]. When inputting after control, ㅁ = ㅁ+{Symbol} = [5]+[*]+[*]. If the symbol control is placed on a grid position that can be selected by pressing the [*] button three times, in the example, inputs of the [*] button can be added one by one.

If there is only one symbol control, only about 10 symbols can be input even if one symbol is assigned to each of the 10 number buttons. An example of assigning the meaning of a symbol to each button is as follows.

[1] button: ? Giving the meaning of ("ㄱ" is placed, but the shape is similar to ?)

*[2] button: ! The meaning of ("ㄴ" is placed, the same as the first letter of "exclamation mark")

[3] Button: Meaning of $

[4] button : . . .

[5] button : . The meaning of ("ㅁ" is placed, the same as the first letter of "period")

[6] Button: Meaning of * ("ㅅ" is placed, the same as the first letter of "asterisk")

[7] button: Meaning of , (“ㅅ” is placed, same as the first letter of “comma”)

[8] Button: Meaning of " ("ㅇ" is placed, same as the first letter of "quotation mark")

[9] Button: Meaning of ~ (The vowel "ㅡ" is placed, and the shape is similar to ~)

[0] button: meaning of @ (number 0 is placed, similar to @)

As above, you can input symbols by combining buttons and symbol controls that can remind you of various symbols. Giving the meaning of a symbol to each button is, as in the example, the relationship between the native language name/shape of the symbol and the arranged alphabet, or the relationship between the English name/shape and the arranged English alphabet, and the arranged number name/shape The meaning of the sign can be given by considering the relationship with Since this may vary according to individual taste, it is not necessarily necessary to be as above, and it is possible to (re)set the meaning of the symbol for each button.

Through this, as in the example, frequently used symbols can be processed as if they are subsequent alphabets belonging to number buttons that are easy to associate. In the example above, the question mark is associated with the [1] button where "a" is placed considering the similarity of shape because the period that is used more frequently than the question mark starts with "ㅁ".

Likewise, in giving meaning to symbols for each button, an English name/shape or a numeric name/shape can be used. The example below can be applied in combination with the case of the native language.

[1] button: ? Meaning of (Alphabet "q" is placed, same as the first letter of "Question mark")

[2] Button: Meaning of , ("c" is placed, same as the first letter of "Comma")

[3] button : . Meaning of ("d" is placed, the same as the first letter of "Dot")

[4] button: ! Meaning of ("i" is placed, similar in shape to "!")

[5] button: . . .

[6] button : . . .

[7] Button : Meaning of / ("s" is placed, same as the first letter of "Slash")

[8] Button: Meaning of : (The number "8" is placed, similar in shape to : )

[9] button: ! The meaning of ("x" is placed, it is related to pronunciation with "eXclamation mark")

[0] button: meaning of @ (number 0 is placed, similar to @)

Giving the meaning of symbols based on English can be useful even in non-English speaking countries that use keypads marked with a mixture of English. In addition, setting the colon with the similarity of the shape of the number 8 also has the advantage of being universally used regardless of language. Similarly, comma can also be regarded as a subsequent alphabet belonging to the [9] button due to its similarity in shape with the number 9, but this was not the case in the example above.

Symbol controls can be set to appropriate buttons. In the case of English, if you do not place a control for another purpose on the [*] button in Fig. 1-1, select the symbol control with one stroke of the [*] button (ie, place the symbol control at the position of the [*] button reference grid) You may. In the case of European languages in which modified alphabets with subscripts exist, symbol controls can be placed at the position of the standard grid of the [0] button or [#] button. However, in the case of putting the symbol control on the [0] button, it is recommended not to give the meaning of the "@" symbol as in the example above.

If the symbol control is placed on the [*] button and input after control is applied, in the case of English, when entering colon (:) in Fig. 1-1, as in : = [8] + {Symbol} = [8] + [*] do.

As shown in the example above, if the meaning of the symbol related to each button is given one by one and the symbol control is placed on only one grid of the control button, only about 10 symbols can be entered. In addition, in assigning meaning to each button, as in the example of English, meanings such as slash, semi-colon, period, etc. can be assigned to the button to which "s" is assigned, but only one of them, slash, is given. Since the button assigned "d" also has the meaning of dot, in the case of an exclamation mark, inevitably considering the similarity of shape, the button assigned "i" has "!" meaning was given.

Therefore, by placing a plurality of symbol controls (for example, symbol control 1, symbol control 2, . . . ) so that the control can be selected, more symbols can be input through the control processing method. For example, giving the meaning of dot to the button assigned to "d" (or giving the meaning of "period" to the button assigned to "ㅁ"), and comma with a similar shape as if it were the subsequent alphabet of dot. can be dealt with

An example of a symbol input associated with a button to which a basic consonant with a lattice consonant or a light consonant is assigned can be “dot (.) = 3****”. Since “3*** = big”, you can enter the symbol promised by the [*] button 4 times. As in “comma(,) = 3*****”, input is possible by pressing the [*] button one more time after inputting in dot(.). This is because Korean syllables do not start with the vowel “ㅡ”. it was used Input of comma(,) can be understood from the point of view of chain type follow-up control processing method.

If the aspirated consonant is not entered according to the control processing method (that is, it is considered that there is no aspirated consonant control), it is natural that "Symbol Control 1" is selected for the 2 strokes of the [*] button (skip control processing). Likewise, colons and semi-colons with similar shapes are regarded as subsequent alphabets assigned to the same button, and can be entered by the control processing method. A similar procedure can be applied to other symbols.

Even in the case of using two symbol controls as "Symbol Control 1" and "Symbol Control 2", the meaning of a symbol must be given to each button and it must be remembered, and there is a limit to the number of symbols that can be entered. do. Therefore, you can enter more symbols by grouping symbols in the same way as grouping dot and comma, colon and semi-colon, and placing multiple symbol controls.

It is also desirable to allow the method of grouping symbols to be done according to the user's convenience. In the present invention, an example of symbol grouping that can be generally used is shown. First, based on the shape of various symbols, the deformed form of dot can be set as one group. For example, dot(.), comma(,), colon(:), semi-colon(;), quotation mark("), . . . , question mark(?), exclamation mark(!), . . It is possible to group as in. This is a grouping of symbols in dot form, that is, "0-dimensional" form. Here, ? and ! have both 0-dimensional form and 1-dimensional form, so 0-dimensional form ( It is included in a group in the form of dot). In determining the sub-order of the group, as mentioned in the previous application, the frequency of use can be considered, but it would be better to allow the user to set it as well. When the number of symbols to be considered is large, it will be convenient to input the symbol control afterward, and in a terminal with a display window, you can see that the symbol changes according to the press of the control button.

Associating the grouped dot-shaped (0-dimensional) symbols with a specific button can also be set according to the user's convenience. For example, if it can represent a group and the most frequently used symbol is dot, it can be regarded as a follow-up alphabet belonging to the [3] button containing the "d" of dot. In the example of FIG. 7-1 where a symbol control is added to FIG. 1-1, if the symbol control button is set to [*] button and input after control is applied, dot = [3] + [*], comma = [3] +[*]+[*], colon = [3]+[*]+[*]+[*], semi- colon = [3]+[*]+[*]+[*]+[*] , . . . becomes like Or, since it is a 0-dimensional form, if it is regarded as a subsequent alphabet belonging to the [0] button, it will be combined with the [0] button, not the [3] button. Alternatively, since the dot form is the most basic form, it can be regarded as a subsequent alphabet belonging to the [1] button.

Next, line-type, that is, "one-dimensional" type symbols can be grouped into groups. For example, slash (/), cap (^), question mark (?), exclamation mark (!), round bracket 1 ((), round bracket 2 ()), angle bracket 1 (<), square bracket 2 (>), right angle bracket 1 ([), right angle bracket 2 (]), tilde (~), minus (-), arrow 1 (<-), arrow 2 (->), . . . can be grouped, etc. Also, as described in the previous application, it is sufficient to set the order of subs in consideration of the frequency of use, etc., and associating it with the subsequent alphabet of a specific button can set an appropriate button as described above. For example, it is regarded as a subsequent alphabet belonging to the [1] button or a subsequent alphabet of the [5] button in which the alphabet “l” is placed.

Then, the combination of lines, that is, "two-dimensional" symbols can be grouped into groups. For example, at(@), ampersent(&), asterisk(*), sharp(#), dollar($), won symbol(W+=), yen symbol(￥), . . . , heart1(♡), heart2(♥), clover1(♧), white triangle 1(◁), white triangle 2(▷), white triangle 3(∇), . . . , black triangle 1(◀), . . You can group them like ., ☏, ☎, ☜, ♨, etc. Again, sub-orders can be set considering the frequency of use, and an appropriate method can be selected to associate them with a specific button. However, it is only necessary to associate it with a button other than the button associated with the 0-dimensional symbol and 1-dimensional symbol in the previous section.

As shown above, when symbols are grouped into three groups of 0-dimensional, 1-dimensional, and 2-dimensional forms (called "three major groups" for convenience), there is an advantage in that only three related number buttons need to be remembered. In case of inputting symbols, there is a disadvantage of pressing the control button several times. Therefore, an example of subdividing the group slightly (this is called a "subgroup" for convenience) is as follows.

First, the two-dimensional symbol group is divided into a symbol group that forms a combination of lines (eg, *, #, %, ...) and a symbol group that forms a single closed curve (eg, ◁, ◀, ...). can Also, in a group, symbols such as ☏, ☎, ☜, ☞, ♨, ... can be placed as a separate group. You can also leave it as the subsequent alphabet belonging to the appropriate button. When these groups are separated, these symbols may or may not be excluded from the preceding symbol groups, and the same shall be true for other cases.

Next, the symbols used in mathematical expressions among the one-dimensional or two-dimensional symbols, that is, +, -, *, /, root (√), sigma (∑), integral (∫), . . . etc. can be placed in a separate group. You can also leave it as the subsequent alphabet belonging to the appropriate button.

There are also symbols that can indicate directions, namely →, ←, ↑, ↓, ↗, ↙, ↖, ↘, ◁, ▷, ◀, . . . can be divided into groups. Again, consider the subsequent alphabet in association with the appropriate button.

And the various parentheses that can relatively reasonably form another group: (, ), [, ], {, }, <, >, . . . may be placed as another group. Also, when grouping in the form of parentheses, the left parenthesis and the right parenthesis may be grouped respectively.

In the case of not placing only the three major groups, but placing subgroups so that symbols can be entered by them, it was said that the alphabet belonging to the subgroups may or may not be left in the three major groups. should be put on the back burner.

An example of considering each symbol group as a subsequent alphabet of a specific button by applying the above symbol grouping to FIG. 1-1 is as follows. The 0-dimensional symbol group is regarded as the subsequent alphabet belonging to the [0] button, the 1-dimensional symbol group is regarded as the subsequent alphabet belonging to the [1] button, and the 2-dimensional symbol group is regarded as the [2] button Regarded as the subsequent alphabet belonging to, among the two-dimensional symbol groups, the symbol group in the form of a single closed curve is regarded as the subsequent alphabet belonging to the [8] button, and among the two-dimensional symbol groups, the symbol group in the form of a picture is considered as the [7] button Considered as a subsequent alphabet belonging to, mathematical symbol group regarded as a subsequent alphabet belonging to the [6] button, direction symbol group regarded as a subsequent alphabet belonging to the [3] button, parenthesis symbol group belonging to any button among the remaining number buttons It can be regarded as a successor alphabet. As described above, in associating a symbol group with each button, this is only one example, and may be set according to the user's convenience.

Summarizing the above, the symbols can be grouped into 3 groups (0-dimensional, 1-dimensional, 2-dimensional) in control processing by considering the symbols as subsequent alphabets belonging to a specific button, or subdivided slightly into 10 or less groups It is one of the key points of the present invention to show that almost all symbols can be input by grouping into. In addition, in considering the group of each symbol as a subsequent alphabet belonging to a specific button, it is treated as a subsequent alphabet belonging to a button related to a group of symbols such as name, dimension, shape, etc. It is one of the key points of the present invention to be able to use the "hidden follow-up control processing method" while maintaining the alphabet arrangement.

In this application, the [*] button or any of the up and down buttons was mainly used as a control button for symbols, but the [#] button can be used as a follow-up control button for numbers and English alphabets. For example, if the [#] button is already being used as a follow-up control button, additional controls for numbers and English alphabets can be placed in the grid available on the [#] button. In this case, in the control selection, as mentioned above, controls that cannot be combined with the representative alphabet can be skipped and the next available control can be selected.

8. How to use the move button

8.1 Use of movement buttons as control buttons

In the previous application, it was said that the control buttons on which various controls are arranged can be placed on any button in the 4 * 3 keypad or on a separate button other than the 4 * 3 keypad. In addition, in the earlier application, especially in languages with a large number of alphabets and a large number of modified alphabets, you may have experienced a lack of buttons to be used as control buttons in the 4 * 3 keypad. In the present invention, it is pointed out that the primary function of the left/up/down movement buttons, which are not used relatively frequently in the text input mode, can be utilized as the control buttons mentioned in the previous application and the present invention, and shows such an example. That is, in using a separate button outside the 4*3 keypad as a control button in the text input mode, the up/down/left movement buttons are used as control buttons.

8-1 shows the buttons of a clamshell terminal that is currently typically used. The [i] button marked with a broken line is a button for Internet access, and this button may or may not exist depending on the terminal. Here, the right movement button is used for blank input, and is also used as a syllable (letter) confirmation button to remove primary ambiguity in Korean. In the menu selection mode other than the text input mode, the up/down/left movement buttons are usefully used as movement buttons for menu selection. However, in the text input mode, the up/down/left movement buttons are not frequently used, especially the up/down movement buttons are not frequently used. For convenience, the up/down/left movement buttons are collectively referred to as "up/down/left movement buttons" or "up/down left buttons", and the up/down movement buttons are referred to as "up/down movement buttons" or "up/down buttons". The same procedure is used when referring to only one direction movement button.

8.2 Placement at the bottom of the movement button

First of all, these up and down buttons are usually placed above the number buttons. However, in order to utilize the primary function of these buttons as buttons for entering various alphabets in character input mode, it is useful to place them at the bottom of the 4*3 keypad along with the [*] and [#] buttons, which are mainly used as control buttons. can know 8-2 and 8-3 show this. However, it is not necessary to do this, and for convenience, the example of the present invention will be described as an example in which the movement button is disposed at the bottom of a 4*3 keypad.

Here, it can be seen that a 5*3 keypad can be configured by combining the 4*3 keypad and the up and down buttons. This means that each button can be divided into 15 lattices of 3x5 when the partial-total selection method is applied. Likewise, it is not necessary to arrange the up and down buttons to configure a 5*3 keypad as shown in FIG. 8-3.

8.3 Placement of the left or right side of the movement button

Up, down, left and right movement buttons can be placed on the left or right side of the 4*3 keypad. In this case, in applying the partial-total selection method, a 4*4 keypad can be configured by combining the 4*3 keypad and the movement button. 8-4 is an example of a case where up, down, left and right movement buttons are provided on the right side of a 4*3 keypad.

This tends to increase the size of the liquid crystal in the terminal, and there is an advantage in that the size of the liquid crystal in the terminal can be made larger. In addition, there is a good characteristic when the side battery mounting method in the mobile terminal presented in the applicant's Korean Patent Application Nos.

8.4 Examples of various uses as control buttons and buttons for alphabet input

In the following, an example of using the move button is given. However, it is not limited to the cases below.

8.4.1 Example of use as a symbol control button

In the Korean language embodiment, there was a case where a consonant control and a consonant control were placed on the [*] button and the [#] button, respectively. In addition, there were cases in which aspirated consonant controls and aspirated consonant controls were placed on the [*] button, only basic vowel controls and extended vowel controls were placed on the [#] button, and only extended vowel controls were placed on the [#] button. In this case, if the symbol control is placed on the [*] button or the [#] button, the aspirated sound or horn sound comes out first according to the input after the control button, and then the symbol is selected. This is also true for other languages.

However, if the symbol control is separated and placed on any of the up, down, left and right buttons, the symbol can be input immediately by combining the button associated with the symbol group and the symbol control button in which the symbol control is placed. 8-5 is an example of using the primary function of the down movement button as a control button for selecting a symbol control. To show an example of applying post-control input to a 0-dimensional symbol group, dot = [3]+[v], comma = [3]+[v]+[v], colon = [3]+[v] +[v]+[v], semi-colon = [3]+[v]+[v]+[v]+[v], . . . became like

8.4.2 Cases of use as vowel element buttons in Korean

In particular, in the case of utilizing vowel elements (ㅡ, ㅣ, .) in Korean examples in the previous application, there was inconvenience in inputting "ㅎ" by placing the vowel elements "." and "ㅎ" together, but the vowel element This inconvenience can be overcome by arranging the button at any one of the up, down, and left buttons. If the symbol control is placed on the down movement button and the vowel element "." is placed on the up movement button, two buttons are used on the up and down left buttons. Alternatively, three Korean vowel elements may be placed on the up, down, and left buttons, respectively.

As with the symbol control on the button with the aspirated consonant control, the Korean vowel element "." , and symbol controls may be placed in order close to the reference grid. 8-6 is such an example. Even in this case, since the vowel element "." is not used alone, even if the vowel element and symbol control arranged by the repeated selection method are selected, the vowel element and symbol control can be selected without ambiguity. In Fig. 8-6, if you press the [v] button once, the vowel element "." is selected, if you press it twice, symbol control 1 is selected, and if you press it three times, symbol control 2 is selected.

8.4.3 Use case of subscript control button in Japanese

Even in the case of Japanese, when the arrangement of the 50 sound charts corresponds to each button, the 2nd and 3rd subsequent controls are placed on the [*] button, and the 4th and 5th subsequent controls are placed on the [#] button (assignment method 3 of the prior application) ), the control for long/voice/half voice input can be placed on any of the up/down/left buttons. Reference may be made to Figures 8-7.

8.4.4 Application of subscript control button for vowel input in Arabic

In the case of Arabic, controls for processing subscripted vowels can be distributed to any button(s) among the up, down, and left buttons.

8.4.5 Example of use as a control button in Thai

In the case of Thai, consonant control and vowel control were not separated, and one control button was used as a follow-up control button. Or you can use it as a control button on a guitar.

8.5 Use case of short/full conversion control button

When the parallel input method is applied, there is a tertiary ambiguity that occurs between the simple code and the full code. For example, to enter a word by the short input method when the full input method is the default mode and the parallel input method is applied, first select the "short/full" switching control and enter a space (right movement button), It was a simple code entry. Of course, the order of the spaces and the "short/full" toggle controls can be reversed. Here, the "short/full" conversion control in word units can be placed on any button among the up, down, and left buttons. Alternatively, a control functioning as a combination of a "short/full" switching control and a space (right movement button) can be placed at a standard grid position of any button among the up, down, and left buttons. Reference may be made to Figures 8-8.

If it is assumed that the English alphabet of FIG. 1-1 is arranged in the number button of FIG. If you want to enter, you can enter as "~ full code input +[^]+[4]+[3]+[5]+[7]+ [>]+ full code input ~". In other words, since the movement function of the upward movement button [^] is limited and the "short/full" conversion function and the space function are combined in word units, the moment the [^] button is pressed, the system moves to the next "[4]+... " Recognizing that this is a simple code rather than a full code, it is possible to recommend words closest to the input [4] to the user by referring to the index. As soon as the [4]+[3]+[5]+[7] input is completed and the space button ([>] button) is pressed, the word ends, so the "short/full" mode conversion in word units is also terminated, and the system waits for the input of the full code again. If the [^] button is pressed again after entering the simple code 4357, the system will also recognize that the word has ended, confirm the help corresponding to the simple code 4357, and wait for the input of the simple code again.

If only one right button (space button) is used in the parallel input method, as mentioned in the previous application, there may be tertiary ambiguity between the full code and the simple code. To avoid this, the system Each time, it was necessary to check whether the simple code existed or whether the promised full code was achieved. However, by placing a button that combines word-based "short/full" mode switching and spaces, the system can recognize in advance whether the input value is full code or simple code, reducing calculation and search, improving system performance. It will be possible.

8.6 Example of use of addition, subtraction, multiplication, and subtraction buttons in calculator mode

The four movement buttons can be usefully used as the most frequently used addition/decrement/multiplication (+, -, x, /) buttons in calculator mode regardless of their location. Addition, subtraction, multiplication and division symbols can be marked on the buttons, but they may not be marked on the buttons because the calculator will not be used frequently compared to alphabet input. This is because each button will be used as a movement button or control button in the alphabet input mode.

In addition, it is possible to place operators that can be used in the calculator on the addition, subtraction, multiplication, and subtraction buttons, and select them by the (hidden) repetitive selection method. Operators (binary operators) frequently used in calculator mode use properties that do not appear repeatedly. For example, there can be no calculation of 2++1. Also, 24 can be solved as 2xx4 so that the "square" operator can be selected by repeatedly pressing the multiplier (x) button. That is, it is the same as repeating selection assuming that the multiplication (x) button has a square (xx) operator as a subsequent operator. Similarly, (O3) can be solved by 3//2 to select the "square root" operator by repeatedly pressing the (/) button. Since other binary operators do not appear redundantly, it can be set as a successor operator belonging to an appropriate addition, subtraction, multiplication, division button, and the successor operator can be selected by the iterative selection method.

Additive (+, -, /) operators are placed on three of the up, down, left, and right movement buttons, and the [*] button can be used for the multiplication (x) operator.

9. Enable help function

In each input mode, functions that are not displayed on the buttons (up/down/left/right) can be displayed on the screen (liquid crystal) for added convenience. In this case, there is a disadvantage of consuming part of the liquid crystal. Of course, the user who knows the function of each operator button does not need to display it while consuming the space of the liquid crystal, but it can be of great help to users who do not. have. Reference may be made to FIG. 8-1, and FIG. 9-1 is an example of a case in which up, down, left and right buttons are arranged in a similar form as in FIG.

Displaying the function of a button (that is, an operator assigned to a button or a symbol group related to each button) according to the user's convenience and intention is called "activation of the help function" for convenience. Activation of the help function may be performed for each mode (eg alphabet input mode, calculator mode), or for necessary functions in each mode (eg use of number buttons or control buttons related to symbol groups in alphabet input mode). can also be

Likewise, the number buttons related to the function of the control button or the symbol group presented in the previous application can also be displayed on the liquid crystal when the user needs it, so that the user's convenience can be promoted. See Figure 9-2. 9-2 is an example in which the number buttons related to each symbol group are iconified and displayed on a liquid crystal based on the symbol group classification exemplified above. Among the symbols of the symbol group associated with each number button, only the symbol selected first for convenience is added to the number button icon.

10. How to use the delete button

When using the delete button, it can be used as "cancellation of final input" introduced in the previous application. For example, in Figure 4-2, I tried to input "a", but I entered "ㅋ" by typing [1] + [*], but I returned it to "a" by canceling the final input ([*]) by pressing the delete button. it can be done This can be useful when inputting subsequent alphabets by repeatedly pressing the control button. In the case of continuously pressing the cancel button, the already input alphabet may be deleted in the usual way. For example, if you press the cancel button once in the state of entering "Kanaㅋ", it becomes "Kana A", if you press it once more, it becomes "Kana", and if you press it again, it becomes "Ga". In the case of the Roman alphabet, "ab a.." is entered (the last "a.." is a modified alphabet consisting of "..+a"), and pressing the delete button once becomes "aba", and pressing it again " It becomes "ab", and if you press it again, it becomes "a". That is, the already formed alphabets are deleted in units of alphabets.

11. of the keyboard with numeric keypad Unification of keypads in telephone terminals

It is obvious that the keypad presented in the previous application and the present invention can be applied to all fields in the form of a telephone keyboard, such as a numeric keypad of a mobile terminal or standard keyboard or a keypad or door lock configured by software on a screen. In addition, although the numeric keypad provided in the standard keyboard has a different layout of the keypad and number buttons presented in the prior application and the present invention, it is obvious that the arrangement on the keypad buttons in the prior application and the present invention can be applied to the keypad provided in the keyboard. . For example, in the previous application and in the present invention, the alphabets placed on the [1] button are placed on the [1] button of the numeric keypad provided on the keyboard, and arranged in the same way below to allow for alphabet input, utilization of simple codes, and various codes. It can be used for memorization.

However, in order to reduce confusion and increase the convenience of use, the number arrangement of the phone keypad can be utilized in configuring the numeric keypad of the keyboard. That is, in the number arrangement of the numeric keypad of the keyboard, as in the keypad of the phone, buttons [1], [2], and [3] are placed on the buttons of the first row, and buttons [4] and [5] are placed on the buttons of the second row. , [6] buttons, and [7], [8], and [9] buttons on the third row. In addition, [*] button and [#] button can be placed as in the keypad of the phone.

12. Language restriction input method

The language restriction input method means reducing ambiguity in character input by using consonant and vowel combination rules in word generation of a specific language, which will be described in detail below.

It is obvious that among the contents mentioned in one language below, the contents applicable to other languages can be applied to other languages without special mention. Furthermore, similar concepts can be applied to languages that do not use the Roman alphabet.

12.1 Chinese Restriction Repeat Selection Method on Consonant Separation Keypad in Languages Using Roman Alphabet

12.1.1 Composition of Chinese virgin and mica

(^e) 는 거의 사용되지 않는다고 함)가 있다고 한다. 성모는 자음에 해당하고, 운모는 모음에 해당한다 고 한다. 중국대륙에서는 중국어음을 표기하는 방법으로 한어병음방안을 이용하 고, 대만에서는 주음부호를 이용하여 중국어음을 입력한다고 한다. 한어병음은 라틴자모즉 로마알파벳을 이용하여 중국어음을 표기하는 것이다. 주음부호와 그 에 대응되는 한어병음(로마알파벳)을 괄로안에 표시하면 다음과 같다. In Chinese there are 21 virgins and 16 mica (double

(^e) is said to be rarely used). It is said that the Virgin corresponds to consonants and mica corresponds to vowels. In mainland China, the Chinese Pinyin method is used as a method of displaying Chinese sounds, and in Taiwan, Chinese sounds are input using the main sound code. Chinese Pinyin is to express Chinese sounds using the Latin alphabet, that is, the Roman alphabet. The main sound code and the Chinese pinyin (Roman alphabet) corresponding to it are shown in parentheses as follows.

The following is an explanation of Chinese combined mica. Combined mica is said to be a combination of three vowels i, u, ..u with other mica behind it. The following table is a list of combined mica and indicates cases in which bonding is possible.

In the table above, it can be seen that ia can be combined, but io cannot be combined.

12.1.2 Input of Chinese Pinyin using Roman alphabet

Eventually, as can be seen from the table above, when using the Roman alphabet, all 21 Chinese characters can be entered as a combination of 18 Roman alphabets, and 16 mica can be entered as a combination of 7 single mica or a combination of Roman alphabet vowels and Roman alphabets. All combinations of alphabetic consonants can be entered.

In addition, among monomica, ^e and ..u can be input by the control processing method, considering them as modified alphabets of e and u, respectively. Next, four tonal codes can be attached to the five basic vowels, which can also be input by the control processing method. In the end, in the case of Chinese using the Roman alphabet, all Chinese mica can be input using the five basic vowels of the Roman alphabet. This is the input of the modified alphabet that does not exist in the English alphabet (ie, the Roman alphabet) by the control processing method, which has already been shown in inputs such as French and German. An example of setting the subrelationship between the basic alphabet (basic vowel) and the subsequent alphabet (subsequent vowel) when Chinese mica is input by the control processing method is as follows.

In the example above, the alphabets with tonal signs from 1 to 4 became the subsequent alphabets, and ^e was rarely used, so the subordinate order was placed at the lowest. Of course, the sub-order may vary depending on the frequency of use. For example, you can set ..u as the 2nd follow-up alphabet instead of the 6th, and set the sub-orders of the remaining follow-up alphabets one by one.

As an input example, when using the [*] button as a control button and applying input after control, ^- e = e + [*], ^/ e = e + [*]+[*], ^v e = e + [*] +[*]+[*], `e = e + [*]+[*]+[*]+[*], ^e = e + [*]+[*]+[*]+[*] +[*] becomes equivalent. If the partial-total selection method is applied to "e" displayed on the keypad in Fig. 1-1, e = [3] + [2], so -e = [3] + [2] + [*]. If the alphabet displayed on the keypad in Fig. 1-1 is selected by the partial-total selection method, the full code of 人 (r ^/ en: 2nd star) becomes “7832 ** 65”. Here, it is obvious that any other input method (eg, simple repetitive selection method) other than the partial-total selection method can be used to input "e" displayed on the keypad.

After all, since only one control button is used, the input method can be simplified. This can be equally applied even when the Roman alphabet is not used and the main note is used (for example, the same input method is applied to the keypad displaying the main note corresponding to the English alphabet in FIG. 1-1).

12.1.3 Chinese Restriction Repeat Selection Method on Consonant Separation Keypad

You can enter all 18 Chinese Virgins in the Roman alphabet, but only zh, ch, and sh have consecutive Roman alphabet consonants. In Chinese, when a syllable consisting only of mica without a mother is written in Chinese Pinyin, it is said to be formally marked with y, w, etc. For example, "衣 = yi (1 star)", "五 = wu (3 stars)".

And, as mentioned in the previous application, using a syllable-based initial code as a simple code in Chinese, where Chinese characters form one syllable, can provide a lot of convenience. Therefore, it is desirable to assign possible 18 Roman alphabet consonants to each number button. In the present invention, 18 Roman alphabet consonants are grouped into two groups and assigned to number buttons [1] to [9].

b p / d t / g k / z j / c q / s x / m n / l r / h f

The above example is a case of grouping based on similarity of pronunciation. When using a simple code, if there are multiple phrases (words or phrases) corresponding to the same simple code (syllable-based initial code), phrases with similar pronunciation are based on the same syllable It was a consideration to have an initial code. The above example is just one example, and many variations are possible. It can be grouped by similarity of pronunciation, and grouping is possible by various criteria, such as the dictionary order of English alphabets and the lexical order of notes corresponding to English alphabets. Another advantage of grouping similar pronunciations into the same group and assigning them to the same button is that in all languages using the Roman alphabet, consonants with similar pronunciations rarely occur consecutively, so there is less possibility of ambiguity. will lose In addition, in the use of simple codes (especially syllable-based initial codes), even if there are many phrases corresponding to the same simple code, since the phrases have similar pronunciation (phonetic value), confusion to users is minimized and It can give you a natural look.

Another thing is that zh, ch, and sh exist as the mother of Chinese characters, so that z and h, c and h, and s and h are not grouped into the same group. (In Chinese, syllables are usually composed of "Virgin + Mica", but in this embodiment, it does not matter much if they are grouped into the same group. However, when entering w, y, v, etc., which are not shown in Fig. 10-1, s, Allocate h, w, etc. together and do not input with 3 assigned buttons)

As shown in FIG. 10-1, the 9 groups exemplified above can be randomly assigned to the 9 buttons [1] to [9], and the repeated selection method can be applied to the input of each alphabet. Due to the characteristics of Chinese, there is no case where Roman alphabet consonants appear consecutively except for zh, ch, and sh when entering the Virgin Mary. Therefore, even if an alphabet is entered by the repeated selection method, it is possible to input without ambiguity. For example, in FIG. 10-1, b = [1], p = [1] + [1] can be input. Of course, which alphabet among the alphabets assigned to each button is to be selected as one stroke can be determined according to the frequency of use of the alphabet so that an alphabet with high frequency of use can be selected as one stroke.

The Roman alphabet "v", which is rarely used in Chinese, can be placed in any of the 9 groups. For example, you can add a "v" to a group with a similar sounding "f" (or not explicitly assign it) and have the button press 3 to enter "v". The w and y used in "衣 = yi (1 voice)", "五 = wu (3 voices)", etc. are also placed in appropriate consonant groups (or not explicitly assigned) and entered by repeated selection (eg .W and y can be entered with 3 strokes of the button to which each alphabet belongs). For example, if y is placed in the group to which / l and r / belong, input “l” with one stroke of the corresponding button ([8] button in Fig. 10-1), input “r” with two strokes, Enter “y” with 3 strokes, and if w is placed in a group where / m and n / are weak, enter “m” with the corresponding button ([7] button in Fig. 10-1) 1 stroke, and “n” with 2 strokes ” and enter “w” with 3 strokes.

Applying the repetitive selection method and using the property of alternating Roman alphabet consonants and vowels when inputting Chinese Pinyin to drastically reduce ambiguity is called “Chinese Restricted Repetitive Selection Method” for convenience. When this property is applied in general to all languages, not just Chinese, it is called “Language Restricted Repeat Selection Method (LRRSM)” for convenience, and when it is specially applied to Chinese, it is called “Chinese Restricted Repeat Selection Method (Chiese Restricted RSM)”. The repeated selection method for language restrictions assigns a pair of basic consonants and basic vowels to each button in Korean or Hindi, etc., and when applying the repeated selection method, consonants and vowels alternate so that they can be entered with less ambiguity. It is in the same context as In addition, in the method using Korean vowel elements, it is similar that the vowel control can be selected by the repeated selection method by using the property that the vowel “ㅡ” does not appear consecutively, which is similar to the “Korean limited repetition selection method”. ” can be said.

In particular, as shown in FIGS. 10-1 to 10-4, separate the buttons to which consonants are assigned (called “consonant buttons” for convenience) and the buttons to which vowels are assigned (called “vowel buttons” for convenience) (i.e., consonants and Vowels are not assigned to the same button), and when the repeated selection method is applied, there is a good feature that greatly reduces ambiguity by using the characteristics of each language in which consonants and vowels are combined. Similarly to FIGS. 10-1 to 10-4, the consonant buttons and vowel buttons are separated from each other, and a predetermined number (eg 1 to 3) of consonants or vowels are assigned to each button. Let's call it the keypad (CVSK (Consonant Vowal Separated Keypad)”.

In FIG. 10-1, it is easy to see that the Roman alphabet consonants and vowels displayed on the keypad can be input without ambiguity even when inputting Chinese Han Chinese Pinyin by the repeated selection method. When the same button among the consonant buttons (buttons [1] to [9] in Fig. 10-1) is continuously pressed for the input of the Virgin Mary, the system can easily know that the second consonant displayed on the keypad has been entered. This is because there is no case where the same Roman alphabet appears consecutively to input the Chinese Virgin. Here, the button pressed twice is a button to which w, y, v, etc. are assigned, and when the same button is pressed once more (ie, when pressed 3 times), as described above, to input w, y, v, etc. The system can easily know what to do. [7] If you enter “w = 777” with 3 strokes of the button, it can be interpreted as “mmm” or “mn” or “nm”, because there is no case that the Chinese mother is composed like this.

As shown in Fig. 10-1, the six vowels of a, e, i, o, u, ..u are divided into three groups of two each, and three buttons of a 4 * 3 keypad (eg [*], [0 ], [#] buttons), and each vowel can be entered without ambiguity by the repeated selection method. This is possible because there is no case where the same Roman alphabet vowel appears twice in a row in Chinese. For example, when a certain Chinese character is written in Chinese Pinyin, there is no case like "...aa...".

However, if you look at the complex mica ai, ei, ou and the combined mica ia, ie, uo here, you can see that a and i, e and i, and o and u should not be grouped into the same group. If a and i are grouped into the same group and assigned to the same button (eg [*] button), whether or not entering 3 strokes of the button (ie '***') is 'ai' This is because ambiguity may occur in which it is not known whether ia' was entered. 10-1 shows an example of grouping in consideration of these contents. Of course, the vowel grouping and arrangement of FIG. 10-1 are not absolute and can be modified as long as the above constraints are satisfied. In Fig. 10-1, each vowel can be input by the repeated selection method. For example, i = [0], o = [0]+[0], iao = [0]+[*]+[0]+[0].

Unless a and i, e and i, and o and u are grouped into the same group, “a, e, o” are grouped (see FIGS. 10-2 and 10-4), and the remaining vowels “i, u, u” can be made into one group. Also, many variations are possible. Assign each of these 2 vowel groups to a random button (e.g. [*], [#] buttons respectively) within the 3*4 keypad, and assign the consonants “w, y, v” as separate groups to the remaining buttons ( eg [0] button). When three alphabets are grouped in one group (eg "a, e, o"), the corresponding button representing a combination of vowels (eg "ae", "ea", "aaa") corresponds to 3 strokes Since Chinese mica does not exist, "o" can be recognized without ambiguity with three strokes of the corresponding button. In the example, when “ao” is input, the corresponding button becomes 4 strokes, but since “oa” does not exist as a Chinese Pinyin, it can also be recognized without ambiguity. Refer to FIG. 10-6. In FIG. 10-6, “v” is Chinese Since it is not used for the input of, it may not be displayed, and grouping “w, y”, etc. into one group and assigning them to the same button has the effect of assigning half consonants (i.e., half vowels) to the same button.

In Figures 10-2, 10-4, and 10-6, “a, e, and o” are grouped into the same group, but only a combination of “ao” is possible. If only “a, o” is assigned to one button, 3 strokes of the corresponding button can be recognized as “ao” without ambiguity. However, if three alphabets are assigned and selected in the order of “a - o - e” according to the number of button presses, ambiguity may occur, not knowing whether the button was pressed 3 times as “ao” or “e” . Therefore, in this case (when three or more vowels are assigned to the same button and one combination of two vowels out of three vowels is possible), the two vowels that can be combined are not selected as 1 stroke and 2 stroke respectively, respectively, Ambiguity can be removed by using language restrictions by selecting 1 stroke or 3 strokes (or 2 strokes or 3 strokes, and 5 strokes of the corresponding button can be recognized as “ao”). In summary, in determining the selection order according to the number of button presses in the three alphabet groups, the selection order is determined so that alphabets that can appear consecutively are not selected with the corresponding button 1 and 2 strokes, respectively.

10-1 to 10-4, when the Virgin Mary is entered in Roman alphabet, the same button can be pressed up to 2 or 3 times, and the system recognizes the number of repeated presses of the button, and the target is selected according to the number of repeated presses. alphabet can be identified. When inputting mica in Roman alphabet, also in FIGS. 10-1 and 10-3, if the same button can be pressed three times in succession, the [0] button is used to input “io” of combined mica “iou” Only if it is pressed 3 times in succession. Regarding the user's input, the system temporarily recognizes it as "0 = i" and confirms it when a button other than the [0] button is pressed. When the [0] button is pressed once more, the system temporarily recognizes it as "00 = o" , and similarly, if a button other than the [0] button is pressed once more, it is confirmed. Here, if the [0] button is pressed once more, the system can confirm “000 = io” because the input of Chinese Pinyin This is because “oi” is used without “Chinese restriction.” In the case of the [*] button, it can be pressed up to two times, so the system temporarily recognizes it as “* = a” and “** = e” This is because the same Roman alphabet vowels do not appear consecutively when inputting Chinese Pinyin, and vowels assigned to the same button do not appear consecutively.

The reason why the input system can be configured without ambiguity in the consonant separation keypad (or with significantly less ambiguity in cases other than Chinese) is that the same consonant button (eg, [1] button in Fig. 10-1) is pressed once or continuously While being pressed, the system recognizes that one of the consonants within the same button is entered, and when another consonant button (eg, [9] button in FIG. because you will recognize it. Another reason is that about 2 letters are assigned to each button instead of about 3 letters. As mentioned in the previous application in the case of grouping consonants and vowels in pairs, the possibility of ambiguity is significantly reduced when two alphabets are assigned to each button compared to when three alphabets are assigned to each button, which can be easily seen. In addition, when two alphabets are assigned to each button, the continuous hitting delay time and hitting delay time suggested by the applicant can be applied more effectively.

10-7 shows the procedure of a general repetitive selection method in the consonant separation keypad, except for part (R). 10-7, for convenience, the input value is a consonant button or a vowel button. That is, it is assumed that there is no special purpose or function (eg, a follow-up control button for input of a follow-up alphabet). Figures 10-7 are not absolute and are for reference only. In FIG. 10-7, detailed procedures such as temporarily recognizing an alphabet corresponding to one press of a specific button as a target alphabet when a specific button is pressed once are not displayed. However, this process may be performed in process (R0) in FIG. 10-7. The language restriction can be determined in the (R) process, and the (R) process can be intervened in any part of the flow chart. That is, if the first input value is one of the consonant buttons, a button to which only two consonants are assigned to the continuously pressed button, and the alphabet assigned to the same button does not appear in succession (e.g., [1] button in Fig. 10-1 ), (R1), the moment the same button is pressed twice, the input value can be determined as one consonant (eg, “P” in Fig. 10-1). This is similar to removing ambiguity using language restrictions in Fig. 4-4 (determining the target alphabet without ambiguity or with little ambiguity when applying the iterative selection method). It can be seen that the procedure of FIG. 10-7 is much simpler than that of FIG. 4-4.

Identical or unequal consonant buttons are continuously pressed, and when the vowel button is pressed, the system determines the target alphabet from the input values of the previously entered consonant buttons, proceeds with the vowel processing process, and performs the initial input in the vowel processing process. The value becomes the vowel button entered last in the consonant processing process. The same applies to the case of changing from the vowel processing process to the consonant processing process.

10-7, the method of judging by language restriction (R) is a list of combinable consonants and vowels (eg “ch”, “sh”, “zh”, “iao”, “iou”, “ia”, “ie”, “ uai”, “uei”, “ua”, “uo”, “ue”, “ai”, “ao”, “ua”, “uo”, “..ue”, “ou” … ) or a list of uncombinable consonants and vowels (eg “bb”, “aa”, “ee”, “oa”, …) (in case ambiguity may occur in a specific keypad), while the system has the input value In cases where this ambiguity can occur, it is generally possible to make the system recognize combinable cases as target alphabets, except for uncombinable cases. For example, in FIG. 10-2 (limited to Chinese) When “ao = 0000” is input, the system can recognize “ao” as the target alphabet for the input value “0000” while having “ao” in the vowel combinable list. Another method is FIG. 10 -2, In the consonant separation keypad of FIG. 10-4, when there is no user input error, only the [0] button can be pressed up to 4 times, considering only the special case where ambiguity can occur, in this case “ 0000 = ao” can be recognized. The rest of the process follows the process shown in FIG. 10-7.

It can be seen that the procedures of the parts omitted in FIG. 10-7 are similar to the previously displayed procedures. If Fig. 10-7 is further generalized and expressed without omitted parts, it is as shown in Fig. 10-8. Fig. 10-8 has the same meaning as Fig. 10-7. In Fig. 10-8, {1} virtually means that button input is made, and “n <- (n + 1)” indicated by the arrow entering part (1) means that the number of button presses increases by one more it means.

In the pinyin representation of Chinese syllables, when mica such as "en", "eng", "an", "ang", and "er" is used, the end of the syllable ends with an English consonant (English alphabet consonant) (Ex. ren: 人). That is, the consonants of the English alphabet that can come to the end of any syllable in the middle of a word or phrase are "n", "g", "r", etc. Consonants that can be at the end of any syllable of Pinyin are referred to as "Consonants which Can be at the End of a Syllable of Pinyin (CCESP)" for convenience.

In the case of syllables in which such pinyin ending consonants are used (ie, syllables in which mica such as "en", "eng", "an", "ang", and "er" are used), typically, the English of the next syllable If the consonant is an English consonant of the preceding syllable, ambiguity may occur. For example, in the case of Zhongguo (中國), "~gg~" can be recognized as "~k~". In this very special case, ambiguity can occur, which is caused by selecting possible pinyin syllable consonants (eg "n", "g", "r" ...) with two strokes of the corresponding button in each group to which they belong. can be removed (when only two alphabets are assigned to the group to which "n", "g", "r", etc. belong, as in Fig. 10-6).

In Figure 10-6, "n", one of the consonants that can end the pinyin syllable, is selected with two strokes of the corresponding button ([7] button), so in the case of "rennai (忍耐)", "88**7777*#" can be entered without ambiguity. same as can To enter "nn", you enter "7777", which can be recognized as "nn" without ambiguity ("mmmm", "nmm", "mnm", "in the middle of a word or phrase in Pinyin) mmn" and so on are not possible). That is, if the selection order of "g" and "k" in Fig. 10-6 is "k - g", Pinyin can be input without ambiguity.

In this way, in order to be able to remove ambiguity by allowing the pinyin syllable ending consonant to be selected as two strokes in the corresponding group, two alphabets must be grouped in the corresponding group. If, as shown in Fig. 10-4, three English alphabets "m, n, w" are grouped and selected in the order of "m - n - w" according to the number of button presses, "n" is the corresponding button 2 Even if it is selected as other, inputting "renmin (人民)" will cause ambiguity with "rewin" (here "rewin" does not actually exist in Chinese Pinyin, so the system converts the input to "renmin (人民)) )", but since "rewin" is a possible Pinyin combination).

Therefore, as shown in Figure 10-4, if it is possible to group English consonants by three, the possible consonants at the end of the pinyin syllable ("n", "g", "r", etc.) are a group in which two English consonants are grouped It can be seen that grouping is necessary. In addition, even when consonants are grouped by two, it can be seen that ambiguity may also occur when "n" and "r", and "g" and "r" of pinyin consonants are grouped into the same group. . For example, if two English consonants "n" and "r" are grouped into the same group, "~rnr~" input will cause ambiguity with "~rn~". The same applies when "g" and "r" are grouped into the same group.

In Figure 10-*, "n" and "g" are assigned to different buttons, so they can be entered without ambiguity. Of course, even if "n" and "g" are grouped in the same group, if only "n" and "g" are grouped, they can be input without ambiguity. For example, if "n" and "g" are grouped into the same group and assigned to the [5] button, when the [5] button is pressed three times to input "vowel + ng" (i.e., "555" is input ), it can be recognized as "vowel + ng" rather than "vowel + gn". This is because in Pinyin, you can use the language restriction that "vowel + gn" cannot occur in the middle of a word. If "n" and "g" are grouped into the same group, if the selection order according to the number of button presses is "g - n", when the button is pressed twice, "g" is displayed, and When pressed, "ng" can be displayed, so naturally WISWYG (What You See is What You Get, more precisely, What You Press is What You See) can be realized. In Figs. 10-2, 10-4, and 10-6, the vowels "a", "e", and "o" are grouped into one group and assigned to the [*] button (example of Fig. 10-6), If the selection order according to the number of times the button is pressed is "o - e - a", when the [*] button is pressed 3 times, the system can recognize and display it as "a", and then [*] When the button is pressed once more, "ao" is naturally displayed, giving a more friendly feeling to the user.

When only "n" and "g" are grouped into the same group and assigned to a button ([5] button in the example), if "5555" is entered after the vowel button is pressed, it is recognized as "vowel + ngg" and if "55555" is entered, it will be recognized as "vowel + ngn". If "vowel + ng" is used relatively frequently in Chinese Pinyin, input convenience can be improved by grouping "n" and "g" into the same group. However, it is not a good approach because it is natural to group consonants with similar pronunciation into the same group for the use of simple codes.

When English consonants other than "n" and "g" (e.g. 'm') are grouped together, the sequence of "m - n - g" or "m - g - n" is used to input Pinyin without ambiguity. (ie, if consonants other than 'n' and 'g' are selected with one stroke of the corresponding button), they can also be recognized without ambiguity. For example, when selecting in the order of "m - g - n" according to the number of button presses, pressing the button 5 times after the vowel button is pressed is recognized as "(vowel) + ng", and pressing the button 6 times Pressing 7 times is recognized as "(vowel) + ngm", pressing 7 times is recognized as "(vowel) + ngg", and pressing 8 times can be recognized as "(vowel) + ngn" without ambiguity. However, it will not be desirable because the number of repeated presses when "ng" is input is excessively increased.

In Figures 10-7, 10-8, and 10-9, "nX", "ngX", and "rX" in the process of consonant processing in the middle of a word rather than at the beginning of a word (capital letter "X" represents the English consonant Even when consonants appear consecutively, such as ), the input value can be processed with consonant combinations possible in Pinyin. This is because English consonants, such as "nX", "ngX", and "rX", do not appear consecutively at the beginning of a word. After all, in Pinyin input, English consonants that can appear in the middle of a word or phrase are theoretically up to four, such as "~ngch~", "~ngsh~", and "~ngzh~", and Figures 10-7, 10 In -8, 10-9, these language restrictions can be used in the process of processing consonants in the middle of words.

By moving English consonants to the end of syllables, we proposed a method that can be entered without ambiguity even when ambiguity may occur. In the alphabet group assigned to each button, the selection order according to the number of button presses can be arbitrarily determined, so this can be seen as a detailed description of the content presented in the previous application. Pinyin syllable ending consonants are consonants that can be used both at the beginning and at the end of a syllable, so they can be seen as relatively frequently used consonants. Since pinyin that does not exist ("rewin" in the example) can be excluded by referring to the Pinyin/Chinese character index, considering the convenience of input, etc., possible pinyin syllable ending consonants in each group to which the pinyin syllable ending consonant belongs are You will be able to determine the order in which they are selected.

In Figure 10-1, which contains the above, each Roman alphabet can be entered at an average of 1.5 strokes, and if the frequent alphabet is selected as one stroke in consideration of the frequency of use in actual Chinese, it will be possible to input with fewer input strokes. will be.

12.1.4 Original function input of function buttons used as control buttons

In Fig. 10-1, when inputting a modified alphabet with a subscript attached to a Roman alphabet vowel, any “separate button” outside the 3 * 4 keypad can be used as a control button to input. For example, if you use the left (left) movement button ([<]) as a control button in Chinese input mode, ^- e = e + [<], ^/ e = e + [<]+[<], ^v e = e + [<]+[<]+[<], `e = e + [<]+[<]+[<]+[<], ^e = e + [<]+[<]+[ You can input like <]+[<]+[<], and if you press the left movement button 5 times in succession, you can no longer select the control that is combined with “e”, so the movement function can be activated ( “e” is entered). If the delete button (marked as “[X]” for convenience) is used as a control button for entering modified alphabets, <sup>-</sup> e = e + [X], <sup>/</sup> e = e + [X]+[X], <sup>v</sup> e = e + [X]+[X]+[X], `e = e + [X]+[X]+[X]+[X], ^e = e + [X]+[X]+[X ]+[X]+[X] can be entered, and if the delete button is pressed 5 times in succession, the previously entered “e” can be deleted. A button with such a different function can be used as a control button, but after a control is selected according to the number of presses of the control button, if there is no control to be selected anymore, the original function (e.g. movement function) can be selected. have.

In the example above, after the left movement function is activated, it is in the word start state, so even if the left movement button [<] is pressed once, the left movement function is input. That is, if you press the control button [<] button 5 times after entering “e”, the cursor moves one space to the left while only “e” is entered, and if you press it again, it moves one space to the side. This is applicable in all languages.

12.1.5 Chinese Restriction Repeat Selection Method on Consonant Separation Keypad (Input of Transformed Alphabet in 3*4 Keypad)

Here, it is shown that even modified alphabets with subscripts on top of Roman alphabet vowels (including tonal codes attached) can be entered within the 3 * 4 keypad.

Looking at the combined mica list, it can be seen that the vowels that cannot come after "i" are "i" and "u" (in other words, 'a' or 'e' or 'o' can come). Also, it can be seen that the vowels that cannot come after "u" are "u" and "i" (in other words, 'a' or 'e' or 'o' can also come). Therefore, the arrangement of vowels as shown in FIG. 10-2 is possible. In Fig. 10-2, when attaching tonal symbols to the vowels "i, a, e" on the left, the [#] button to which "u" is assigned on the right can be used as a control button. Likewise, when attaching tonal marks to the vowels "o, u" on the right, use the [*] button on the left like a tonal symbol control button. For example, /o (second voice) = o + [*]+[*] = [0]+[0]+[0] + [*]+[*], so /a (second voice) = a + [#]+[#] = [0] + [#]+[#] so that ^e = e + [#]+[#]+[#]+[#]+[#] = [0 ]+[0] + [#]+[#]+[#]+[#]+[#]. It can be entered as complex mica ao = a + o = [0] + [0]+[0]+[0], and vowels a, e, etc. cannot come after vowel a, and there is no case like oa, It can be identified by the system without ambiguity. Since the vowel ^.. u is similar in shape to the vowel u, the button assigned to u can be entered with two strokes (repetitive hidden selection method).

In Chinese, among the vowels "a, e, o", the vowel u does not appear after a and e, and the vowel i does not appear after vowel o. The constraints described above, that is, do not put a and i, e and i, and o and u in the same group, assign two vowels to three buttons, and use the Chinese Roman alphabet vowel combination rule. Fig. 10 As in -2, it can be seen that it is impossible to use a button to which a vowel is assigned as a control button. In FIG. 10-2, i and u are placed on the [*] button or [#] button in consideration of the fact that these buttons are used like control buttons to facilitate recognition and balance of arrangement. The average number of input strokes of the vowels in FIG. 10-2 is also about 1.5 strokes as in FIG. 10-1.

As a modified example of FIG. 10-2, some of the three alphabets assigned to the [0] button may be separated as “separate buttons” outside the 4*3 keypad. For example, some of the three alphabets can be separated and assigned to any of the up/down/left buttons.

In FIGS. 10-1 to 10-4, the consonant buttons ([1] to [9] buttons) and the vowel buttons [*], [0], [ #] button) was separated, and the Roman alphabet's consonant and vowel appearance rules were used when Chinese was written in Chinese Pinyin.

12.2 English Restriction Repeat Selection Method on the Consonant Separation Keypad

Even in the case of English, similar to the case of Chinese, it is possible to input with less ambiguity by applying the repeated selection method in the consonant-consonant separation keypad (CVSK) similar to FIGS. 10-1 to 10-4. This is because in all languages using the Roman alphabet, the structure of words consists of alternating consonants and vowels.

In the case of English, the case where the consonant group is repeated as much as possible from "word beginning" is called "CCCVCCCC" as in "strengths" (C is a consonant and V is a vowel). Up to three consonants can be present at the beginning of a word, but this is only the case when it starts with "st ~" or "sp ~" (eg, spree, spleen, strength, etc.).

Similar to Fig. 10-1, the user inputs the English word "student" on a keypad in which about 2 to 3 consonants are assigned (for convenience, it is assumed that only "..u" is not assigned in Fig. 10-1) When entering "622~" for this purpose, the system can process "622" entered after "word start" as entering "st" rather than "sdd" (3 in a specific word in English). If consonants can come out consecutively, it is said that it starts with "st ~" or "sp ~", and the system only needs to remember these English word generation rules or alphabet combination rules). When entering “u” in “stu~”, the button assigned to the vowel is pressed, so it can be seen that the consonant group (“st” in the example) ends and the vowel (“u” in the example) comes. If "2" is input to input "d" after inputting "stu", the system knows that the consonant starts again. Likewise, when the user inputs "~**7722" to input "~ent" of "student", when "**" is entered, as described in the previous application, "a" appears consecutively in English. Since it is not "aa", the system can easily know that "e" was entered, and "7722" can also be interpreted as "mmt", "ndd", "nt", "mmdd", etc. As mentioned above, the ambiguity generated in the repeated selection method can be greatly reduced by setting the "hit delay time" and the "hit delay time" differently.

Even in the current standard English keypad (Fig. 1-1), in which consonants and vowels are mixed and assigned to each button, the word generation rule (alphabetic combination rule) of a specific language is reflected in this way to eliminate ambiguity that may occur when the repeated selection method is applied. can reduce However, when consonants and vowels are mixed and assigned to one button, it is very difficult to apply the language-restricted input method (especially the repetitive selection method as the full input method). For example, in FIG. 1-1, when the user inputs "student" using the repeated selection method, "stu ~" becomes "777888 ~", and it is assumed that "777" is recognized as "s" by the system Also, it is unknown whether the next "888" is "ut (i.e. sut)", "tu (i.e. stu)", or "v (i.e. sv)" (of course, when the English restriction input method is applied, "s Since "ttt" cannot occur after ", the system may consider the input value "888" not "ttt"). Similarly, even when the user inputs "333" to input "~de~", it is unknown whether it is "de" or "ed", but "888777" entered before "~de~" is "sut", " Since it can be interpreted as "stu" or "s v", all cases of "~de~" and "~ed~" can come for each of the three cases.

Even if the language-restricted input method is applied, the reason why a lot of ambiguity occurs when the repeated selection method is applied as a full input method is that the consonant and vowel appearance rules (ie word generation rules, alphabet combination rules) in the language-restricted input method is used, because it is not clearly distinguished whether the input value is for entering consonants or vowels. As shown in Fig. 10-1 and Fig. 10-4, if the consonants and vowels are separately assigned, when the button assigned to the vowel is pressed when the repeated selection method is applied, the button to which the consonant is assigned is pressed to input the vowel. Since the system can recognize it for inputting ground consonants, it is possible to significantly reduce ambiguity.

In the case of English using the Roman alphabet, there are many cases in which two or more vowels appear in succession (eg, ‘ai’ in captain). In addition, the case where the same vowels (basic vowels a, e, i, o, u) appear consecutively in real words is relatively frequent in the case of oo and ee, such as food and teen, and rare in the case of uu, such as vacuum. . The applicant has not yet seen a case in which ... aa ... and ... ii ... appear consecutively among words that exist in the English dictionary. Therefore, in assigning the five basic vowels of English to the [*], [0], and [#] buttons, if 'a' is selected as one stroke and the rest of e, o, and u are selected as two strokes, there are actually many In this case, ambiguity is removed. For example, if the [*] button has the vowels 'a, o' and the repeated selection method is applied, when two [*] buttons are input, it is assumed that the two vowels aa were not entered, but the vowel o was entered. system can be considered. Likewise, if 'i, u' is assigned to the [0] button and the repeated selection method is applied, when two [0] buttons are input, it is also not two vowels ii, but a vowel u. system can recognize it. Even if it is not absolute that words do not appear consecutively, such as aa and ii, ambiguity can be almost eliminated by setting differently the “hit delay time” and “other delay time” mentioned in the previous application. The remaining vowel ‘e’ can be assigned to the remaining [#] button and entered with one stroke.

If you want to use one of the buttons [*], [0], and [#] as a button for a special purpose, you can place the vowel ‘e’ on any button to which the vowel is assigned. For example, ‘i, e, u’ can be placed on the [0] button. The vowel u is entered with three strokes of the [0] button, because the vowel u is the least frequently used vowel in English. After all, if 'i, e, u' is assigned to the [0] button and there is no case where i appears consecutively in English (i.e. ...ii...), i and e can be entered without ambiguity ( 1 stroke and 2 strokes, respectively), when u is inputted with the [0] button 3 strokes, ambiguity arises in which it is unknown whether it is u, ie, or ei. The low frequency of use of u means that this case will occur less frequently.

In the end, ambiguity can be greatly reduced by using the consonant and vowel separator pad, and furthermore, in assigning multiple vowels to one button, among English words in the dictionary, vowels in which the same vowel does not appear consecutively are counted as one stroke. In inputting a vowel by the repeated selection method on a button to which a plurality of vowels are assigned by selecting, it is possible to input with almost no ambiguity.

Selecting vowels that do not appear consecutively as one stroke and selecting the least frequently used vowel as three strokes can be equally applied even when about 2 to 3 consonants are assigned to each button.

In the above, the case of English using the Roman alphabet has been described as an example, but the same can be applied to other languages using the Roman alphabet.

12.3 Repetitive Selection Method for Indonesian Restrictions on the Consonant Separation Keypad

Indonesian also uses the Roman alphabet (English alphabet) to mark words. A syllable in Indonesian is said to consist of the following case. (C is a consonant, V is a vowel)

V: be-a tariff

VC: catch am-bil

CV: go-sok rub

CVC: pon-dol cabin

CCV: tra-di-si tradition

CCVC : con-trak contract

CVCC : teks-tur fabric

CCCV: construction of kon-struk-si

CCCVC : strip-tis nude dance

As you can easily see, if there are three or more consonants, it is a foreign word from English. As can be seen from the above, even in the case of Indonesian, if you do not start with “st~” or “sp~”, you can guess that three or more consonants do not appear repeatedly at the beginning of a word. Therefore, it is possible to apply the Indonesian language-restricted repetition selection method using these word generation rules (alphabetic combination rules).

It is said that q and x are used in natural science symbols such as physics and mathematics. In other words, it is considered that it is hardly used for text input. Therefore, q and x may not be explicitly placed in a specific group, and even in the input, they can be input in 3 strokes. In addition, as in the case of Chinese, there are cases in which two or more Roman alphabets are combined to represent one Indonesian sound, and there are four such as ny, sy, kh, and ng.

Other consonant groups that are not divided include bl, br, dr, dw, dy, fl, fr, gl, kr, ks, kw, pl, ps, rps, rs, sk, skr, sl, sp, spr, sr, str , sw, etc. are said to exist. In particular, since “skr~”, “spr~”, and “str~” can appear at the beginning of a word, they can be used as a means of determining whether an input value is full code or simple code in the language-restricted parallel input method described later. (As an applicant, I do not know if there are cases where “rps” appears at the beginning of a word, but if so, it can be used as well.)

Any method of grouping 19 consonants excluding q and x among the 21 consonants of the English alphabet into 9 groups is possible, but grouping is sufficient to reflect the characteristics of Indonesian. for example,

BP/DT/GK/CJ/MN/LR/SZ/FV/HWY

can be grouped as

q and x can be grouped into appropriate groups. For example, you can put q in the “GK” group and group x in the “SZ” group.

Five vowels a, i, u, e, and o are used to mark Indonesian vowels. There are also three diphthongs ai, au, and oi, and oi is said to be used very rarely. Therefore, even when grouping 5 vowels into 2 or 3 groups, it would be desirable to avoid grouping a and i and a and u into the same group as much as possible. For example, grouping like ae / uo / i. In addition, as in the case of English, it would be desirable to select a vowel in which the same vowel does not appear consecutively (even if it appears consecutively, the frequency of occurrence is low) as one stroke of the button to which the vowel belongs in each group.

12.4 Japanese Restriction Repeat Selection Method on the Consonant Separation Keypad

In Japanese input, the method of inputting Japanese pronunciation using the Roman alphabet and converting it back to Japanese has been widely used. Therefore, it will be possible to input Japanese sounds using the Roman alphabet on the consonant and vowel separation keypad similar to those shown in FIGS. 10-1 to 10-4 and convert them into Japanese.あ, い, う, え, お can be written as a, i, u, e, o respectively.な, に, ぬ, ね, and の can be written as na, ni, nu, ne, and no, respectively, and the rest of the alphabet can be written in a combination of Roman alphabet consonants and vowels.

In Japanese, when a consonant in the Roman alphabet appears twice in a row, it is when a tactile sound or a yoeum (indicated in small letters) is used. In addition, if you look at the case where the Roman alphabet vowels appear consecutively, assuming that it is not common for the combination of あ, い, う, え, お to appear consecutively in a word, it is at most about 2 times, and it is very rare to occur more than 3 times in succession. It can be seen that it is rare Therefore, even if the five vowels (a, i, u, e, o) of the Roman alphabet are divided into three groups similar to Figs. It can be seen that there is not much ambiguity. In particular, in the case of Japanese, it is easy to see that when “a” is entered, the corresponding Japanese is “あ”, and when “na” is entered, the corresponding Japanese is “な” (the same applies to the rest of the Japanese alphabet). Therefore, the moment the user inputs “na” and the system confirms that the input value is “na”, the system can provide “な” to the user.

There are 14 Roman alphabet consonants used in the Japanese transcription of the 50-tone table: k, s, t, n, h, m, y, r, w, g, z, d, b, p. In the notation of yoeum, it is expressed by combining two consonants of the Roman alphabet (eg cha, sha), by combining “y” (eg kya), or by using “j”. Roman alphabet consonants occur two or more times in succession in cases such as ch, sh, ky, ny, hy, my, ry, gy, py, py, and when tactile sounds are used. When tactile sounds are used, there are cases where the same alphabet appears consecutively among k, s, t, and p (eg ippai). Therefore, it can be seen that 16 (14 + c, j) Roman alphabet consonants are essential for Japanese input, and the consonant separation keypad can be configured to facilitate input of consonants essential for Japanese input. The remaining five Roman alphabet consonants (f, l, q, v, x) will also be needed to input English, etc., but they can be grouped around 16 alphabets. For example:

BP / DT / GK / CJ / H / MN / R / SZ / YW / => Grouping into 9 groups

BP / DT / GK / CJ / H / MN / Y / SZ / RW / => Grouping into 9 groups

BP / DT / GK / CJ / HR / MN / SZ / YW / => Grouping into 8 groups

Five Roman alphabet consonants required for English input can be appropriately added to each group as in the case of Chinese. In the case of grouping into eight groups, the remaining four buttons on the 3*4 keypad can be used as vowel buttons, or if only three vowel buttons are used, the remaining one button can be used for consonants required for English input. may be

12.5 Intentional Language Restriction Release

The language restriction iterative selection method sacrifices the advantage of the "full input method" that allows all words to be entered regardless of whether or not they exist in the dictionary, so the user can decide whether or not to impose these language restriction restrictions. It is desirable to be able to set whether it will be in advance. However, even in the "Language Restricted Input Mode" that enables the language-restricted input method, if the user wants to input a word that does not exist in the dictionary and violates the word generation rule (alphabetic combination rule), a specific function (e.g. For example, after inputting a space, left movement, word ending, etc.) to intentionally determine the target alphabet, all alphabet combinations can be input by inputting the next alphabet. For example, in FIG. 10-1, if the user inputs "622~" in the "English restricted input mode", the system recognizes it as "st~" rather than "sdd~", but if the user enters "sdd~" If you want to enter "62", enter a space and left movement function, then enter "2" or enter "62" and then select "word end function (or control that can give effect of word end)" Just enter "2" followed by some other means to activate it. If the word end function is activated after entering "62", the system can recognize it as "d" because the next input "2" appears first after "word start". Overcoming the language restriction in a specific language restriction input mode by intentionally inputting the word termination function in this way will be referred to as "intentional language restriction release" for convenience. An example of "sdd~" is "intentional release of English restriction".

Similarly, in FIG. 10-2, in "Chinese restricted input mode (Chinese restricted repeated selection method applied)", if the user wants to input "ui", a vowel combination that does not exist in Chinese Pinyin but exists in English, "u" After entering the means to terminate the word (mentioned in the previous example), enter "i" again. Otherwise, if you press the button to which "i" is assigned after entering "u" in "Chinese restricted input mode (Chinese restricted repeated selection method applied)" based on Fig. 10-2, as mentioned in the previous application, the modified alpha of "u" Bet (e.g., an alphabet with a tonal sign attached to "u" or an alphabet with ".." attached to "u" - when inputting "..u" as a modified alphabet of "u") will be entered (Since it was said that when applying the Chinese restriction repeated selection method, the button assigned to "i" is used like a control button if inputted after the vowels "u" and "o"). As a result, the user can input a combination of words that do not exist in Chinese Pinyin (for example, all alphabetic combinations such as English words) even in the Chinese restricted input mode. In other words, a user who mainly uses Chinese can input all alphabet combinations that do not exist in Chinese without changing the setting again while setting the Chinese restriction input mode (Chinese restriction repeated selection method application mode). . This is equivalent to "intentional lifting of the Chinese language restriction".

In the method using the three Korean vowel elements of FIGS. 4-5, the same can be applied to the input of consonants or vowels as single characters. For example, if you want to input the consonant "a" and the vowel "ㅡ" as single letters in Figures 4-5, enter [1] in the "word start" state, then enter a means to give the word end function, Again, enter [*] at the beginning of the word. This is because if you input the [1] button and the [*] button consecutively, it becomes "that". In the standard keyboard (standard keyboard for English and Korean), when the right arrow button is pressed, the word end function is activated without entering a "word end" space, and in the present invention, if the right arrow button is additionally provided, this is the same can be applied

12.6 Language Restriction Release Delay Time

It was said that "hit delay time" and "hit delay time" can be applied even when three or more letters are assigned to one button. For example, in the standard English keypad of FIG. 1-1, if the [2] button is pressed twice within 0.1 second by setting the hitting delay time to 0.1 second, the system can consider that B has been entered.

Likewise, when the [2] button is pressed three times in succession (i.e., [2]+[2]+[2]), the first input value and the second input value (i.e., the first [2] button and the second [2] button) If the delay time interval between is within the time set as the hitting delay time (eg 0.1 second), and the delay time interval between the second input value and the third input value is within the time set as the hitting delay time (eg 0.1 second) ( That is, [2] + within 0.1 seconds + [2] + within 0.1 seconds + [2]), and the system can recognize that C is entered. Or, when the [2] button is pressed 3 times in succession (i.e., [2]+[2]+[2]), if the total input time is within twice the delay time (e.g. 0.2 sec), enter C. You can also make the system recognize it.

In addition, in the case of English, for example, assuming that there is no "..u" in FIG. If applied, when entering an abbreviation such as "NII", it will be possible to input "NII" in English restriction repeated selection mode through "intentional English restriction cancellation" by entering the word termination function. However, after a certain period of time has elapsed after entering "NI", NI can be determined even if the word termination function is not entered. This predetermined time may be set equal to the "other delay time" mentioned in the previous application, but it would be preferable to set it longer than the "other delay time". For example, if 2 seconds pass after inputting "NI", NI is confirmed even if the word ending function is not input, and the system returns to the "word start" state. For this convenience, it is called "temporary language restriction release delay time", and it would be desirable to allow the user to set it as well. It is self-evident that this can be applied equally to all languages.

The various delay times are summarized as follows.

Continuous hitting delay time ≤ Hitting delay time ≤ Temporary language restriction release delay time

All three delay times may be set the same, but it would be preferable to set the delay time longer than the continuous hitting delay time, and the temporary language restriction release delay time longer than the other delay time.

12.7 How to select the repetition of Portuguese words on the consonant separation keypad

In Portuguese, k, w, and y are said to be used only for abbreviations or foreign words, but they will also be needed for character input. In Portuguese, double consonants are said to be:

bl, cl, dl, fl, gl, pl, tl,

br, cr, dr, fr, gr, pr, tr, vr

In addition, there are double consonants such as gn, mn, pn, ps, pt, tm, ch, lh, nh, rr, and ss. Therefore, in configuring the consonant separation keypad for the Portuguese restricted input method, it is necessary to prevent the above alphabets from being grouped into the same group. See Fig. 10-* for example. However, “mn” is grouped into the same group, but it can be appropriately modified and placed in another group. The reason why the keypad of FIG. 10-* can be similarly applied to other languages is based on the similarity of pronunciation (eg, voiced and unvoiced sounds having similar phonetic values in the same group - eg. /b p/, /d t/, /g k/ . . . - Grouping) was grouped, and there are few cases in which alphabets with similar pronunciations appear consecutively.

There are five basic vowels in Portuguese: a, e, i, o, and u, of which a, e, and o are strong vowels, I and e are called weak vowels. When two different vowels appear consecutively, there are 6 types of “strong + weak vowel” (ai, au, ei, eu, oi, ou) and 1 type of “weak + weak vowel” (ui). It is said. That is, strong vowels and weak vowels can be grouped into separate groups (eg, without “..+u” in FIG. 10-6). In addition to such grouping, it is also possible to group weak vowels and strong vowels into an arbitrary number of groups by preventing them from being the same group. For example, it can be grouped like /a / e o / u i/.

12.8 Spanish Restriction Repetition Selection Method on Consonant Separation Keypad

Spanish has an alphabet that does not exist in English, “~+n (the alphabet with ~ above n)”. It is said that k and w are used only for notation of foreign words, but they will also be needed for character input. In Spanish, double consonants are:

bl, cl, dl, fl, gl, pl

br, cr, dr, fr, gr, pr, tr

That is, in configuring the consonant separation keypad for the Spanish restricted input method, it is necessary that l and r are not assigned together, and the alphabets that can compose the above double consonants are grouped into the same group and assigned to the same button. do. Reference may be made to consonant groupings in FIGS. 10-1 to 10-4 and FIG. 10-6.

There are five basic vowels in Spanish: a, e, i, o, and u, of which a, e, o are strong vowels, I and e are called weak vowels. When two different vowels appear in succession, there are 6 types of “strong vowels + weak vowels”, 6 types of “weak vowels + strong vowels”, and 2 types of “weak vowels + weak vowels” (iu, ui). do. In the case of a triple vowel, it is said that it is combined like “weak vowel + strong vowel + weak vowel”. That is, when strong vowels and weak vowels are grouped into separate groups (eg, without “..+u” in FIG. 10-6), there is ambiguity only in the case of “weak vowels + weak vowels”. In this case, since both iu and ui are possible, the ambiguity can be overcome by applying the delay time between hitting and hitting or using the method proposed by the applicant, such as intentional language restriction release. The same applies to cases in which identical vowels appear consecutively, cases in which identical consonants appear consecutively, and other cases in which ambiguity may occur.

12.9 Italian Restriction Repeat Selection Method on the Consonant Separation Keypad

In Italian, j, k, w, x, and y are said to be used only for archaic or loanwords. It will be necessary for input such as English. In the grouping of consonants, the remaining consonants excluding these five consonants may be grouped, and the remaining five consonants may be appropriately grouped.

Diphthongs in Italian are ia, io, ie, iu, ai, ei, oi, ui, uo, ou, eu. Again, except for iu and ui, it is a combination of strong vowels (a, e, o) and weak vowels (u, I). In the case of triplet vowels, the structure is “weak vowel + strong vowel + weak vowel”. Therefore, grouping of strong vowels and weak vowels can be used, such as /a e o/ and /u I/, and ambiguity can occur in the case of ui and iu.

12.10 German Restriction Selection Method in the Consonant Separation Keypad

Double consonants in German include ch, chs, ck, ds, dt, ng, nk, pf, ph, sch, sp, st, th, ts, tz, tsch. Consonant grouping in FIG. 10-* can also be referred to for grouping so that consecutive consonants are not grouped into the same group. In addition, in the case of “sch~” in German, it is said that three or more consonants can appear at the beginning, so it can be used in the language restriction parallel input method described later. Tsch can also appear in the beginning, but it is said to be used very rarely.

There are five short vowels in German, and there is a side vowel with “..” above a, o, and u. Diphthongs include au, ei, ai, eu, “..au”, ie, etc. When inputting vowels using only short vowels (basic vowels), there are cases of ie and ei, so it is necessary to group i and e into different groups. For example, /a e o/, /I u/ can be grouped, and many variations are possible.

When the same consonant or vowel appears consecutively, ambiguity can be avoided by various methods suggested by the applicant.

12.11 Vietnamese language restriction input method

12.11.1 How to input Vietnamese restrictions on the consonant separation keypad

It is said that syllables in Vietnamese are mainly composed of “vowel”, “consonant + vowel”, “vowel + consonant”, and “consonant + vowel + consonant”. In particular, it is said that monosyllabic words form the basis of Vietnamese. Although the number of evangelical words is increasing, the fact that there are many monosyllabic words means that it is easy to configure the input system on the consonant separator keypad.

In Vietnamese, there are 5 basic vowels a, e, i(y), o, u, “v + a (a vowel with a v attached to it. This 'x + vowel' is a vowel with an 'x' attached to the top of the vowel)”, “^ It is said that there are 6 vowels such as +a”, “^+o”, “,+o”, and “,+u”. “y” is said to pronounce “i” long. A consonant vowel separation keypad can be configured with only five basic vowels, and the remaining vowels can be input by the control processing method. A consonant-vowel separation keypad can be constructed with only some basic vowels and variations, or a consonant-vowel separation keypad can be configured with all 11 vowels.

Vietnamese double vowels and triple vowels have various combinations, so it is not easy to group five basic vowels into 2 or 3 groups similarly to Fig. 10-* so that there is no ambiguity when applying the repeated selection method. In addition, there are six tones in Vietnamese, and five tonal signs appear above or below vowels. In addition, there is no case where the same vowel appears consecutively in Vietnamese, which is a useful property for inputting Vietnamese vowels. Therefore, it is conceivable to put 5 basic vowels into 5 groups, input the vowels by the hidden repetition selection method, and attach tonal codes to the basic vowels and the vowels by the control processing method. Here, y can be regarded as a vowel of i. That is, vowels / 'a', 'v+a', '^+a' / 'o', '^+o', ',+o' / 'u', ',+u' / 'i', It is divided into five groups of 'y' / 'e' and '^+e' /. It is also possible to modify this and combine groups with a small number of vowels into four groups. For example / 'a', 'v+a', '^+a' / 'o', '^+o', ',+o' / 'u', ',+u' / 'i', It is divided into four groups: 'y', 'e', '^+e' /. If there are only five groups, it is possible to input vowels without ambiguity by applying the repeated selection method. In each group, an arbitrary alphabet can be displayed on the keypad as a representative alphabet, and the rest of the alphabets may not be displayed. It would be natural for mainly single vowels to be the representative alphabet, and in the case of dividing into four groups, it is possible for both i and e to be displayed. The selection order according to the number of button presses may be determined in consideration of the frequency of use.

Vietnamese consonants include “-+d (‘-‘ in the middle of ‘d’)” that are not found in English, and English f and z are not used. ‘-+d’ is regarded as a modified alphabet of ‘d’, and the (hidden) repetition selection method or control processing method can be applied. Some textbooks say that f, w, and z are not used in Vietnamese, and some textbooks say that w and j are used as half consonants. At least f and z are not used, and w is rarely used. In the present invention, w is considered not to be used, but if necessary, it can be included in an appropriate group.

In addition, it is said that there are double consonants such as ch, gh, gi, kh, ng, ngh, nh, ph, qu, th, and tr. Since gi and qu are morphologically a combination of consonants and vowels, they are not considered here. The fact that Vietnamese is mainly composed of monosyllables means that, unlike other languages, syllables consisting of “ja+mo+ja” rarely appear in succession, and consonants and consonants appear consecutively, except for the case of the double consonant above. That means there are very few cases. In the end, when consonants are divided into several groups and the repeated selection method is applied, if the consonants constituting the above consonants are grouped so that they are not grouped into the same group, the consonants can be entered without ambiguity, as in the case of Chinese.

For example, it can be grouped into 8 groups such as b p / d t / g k / c q / s x / m n / l r / h v j. It can also be divided into six groups, such as b p v / d t / g k q / s x c / m n j / h l r /. Grouping into arbitrary groups will also be possible. Unused consonants such as f, z, etc. can be additionally included in appropriate groups.

If consonants are divided into 8 groups and vowels are divided into 4 groups, both consonants and vowels can be accommodated within a 3*4 keypad. If the consonants are divided into 6 groups and the vowels are divided into 5 groups, consonants and vowels can be accommodated on 11 buttons, and the remaining one button can be used as a control button to attach tonal signs to vowels. If the consonants are divided into 6 groups and the vowels are divided into 4 groups, 10 number buttons can accommodate both consonant and vowel buttons, which has the effect of making the simple code consist only of numbers in the use of simple codes there is The remaining two buttons can be used as a control button for inputting a tonal code and a follow-up control button for removing ambiguity.

12.11.2 Vietnamese restriction input method using consonant and vowel pairs

Vietnamese vowels and consonants can be grouped in pairs and a repetitive selection method can be applied. You can refer to the case of Korean. If the number of pairs of consonants and vowels is set to 10, the remaining consonants and vowels can be input according to the control processing method.

12.12 Russian Restriction Input Method on Consonant Separation Keypad

In order to construct a consonant separation keypad for Russian, reference may be made to the prior application PCT/KR02/00247 of the applicant.

There are 33 alphabets in Russian. It consists of 10 vowels, 20 consonants, 1 half vowel (or half consonant), and 2 symbol alphabets (hard consonant code, soft consonant code).

The following is a list of uppercase and lowercase letters in alphabetical order of the 33 letters.

АБВГДЕЁЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯ

абвгдеёжзийклмнопрстуфхцчшщъыьэюя

The 20 consonants are divided into voiced and voiceless consonants as follows. Parentheses indicate pronunciation.

Vowels are divided into hard vowels and soft vowels.

In properly grouping Russian consonants, voiced and unvoiced consonants having similar phonetic values can be grouped. For example /б(b) п(p) / д(d) т(t) / … to be classified as Consonants that are not phonetically paired can be properly grouped as suggested in the previous application. A few examples are as follows, and various variations are possible while grouping paired unvoiced and voiced sounds together.

10 groupings

Example 1: БП/ ДТ/ ГК/ ВФ/ ЗС/ ЖШ/ ЛР/ МН/ ХЦ/ ЧЩ

Case 2: БВ/ ГК/ ДТ/ ЖЗ/ ЛР/ МН/ ПФ/ СХ/ ЦЧ/ ШЩ

9 grouping examples: (b) п(p) / д(d) т(t) /г(g) к(k) / в(v) ф(f) х(x) / з(z) с( s) / ж(zh) ш(sh) / ц(ts) ч(tsh) щ(shsh) / л(l) р(r) /м(m) н(n)

8 grouping examples: (b) п(p) / д(d) т(t) /г(g) к(k) / в(v) ф(f) х(x) / з(z) с( s) ж(zh) / ш(sh) ц(ts) ч(tsh) щ(shsh) / л(l) р(r) / м(m) н(n)

7 grouping examples:

. . . . . .

In the example above, the half consonant Й, hard consonant Ъ, and soft consonant Ь can also be included in the appropriate group. Also, in allocating these groups to each button, some alphabets (eg Й, Ъ, Ь and other alphabets) may be omitted and not displayed in order to keep the keypad simple.

Vowels may also be grouped into 5 groups by using pairs of hard vowels and soft vowels. There are 10 vowel alphabets in Russian, and there are 11 vowel sounds in pronunciation. Of these, (e) and (o) are said to appear only under stress. In other words, the vowel phonemes (a) and (o) can be seen as strong vowels. The vowel phoneme in the unstressed position is called the remaining three. Therefore, with 5 basic alphabets among the 10 vowel alphabets of the Russian language, vowels corresponding to double strong vowels can be divided into one group and the remaining three basic vowels can be divided into one or more groups. This is because it can be expected that it is difficult for the same kind of vowel to occur consecutively (eg, hard vowel followed by strong vowel). а(a) о(o) / у(u) э(e) и(i) / in two groups or а(a) о(o) / у(u) э(e) / и (i) / can be put into three groups. Paired vowels corresponding to the basic vowels can be put together in the group to which the basic vowels belong, and the repeated selection method can be applied, or the control processing method can be applied by considering them as modified alphabets of the basic vowels.

Consonant and vowel groups can be properly used to configure a consonant-consonant separation keypad within a 3*4 keypad (eg 5 groups of vowels and 7 groups of consonants, 3 groups of vowels and 9 groups of consonants). In Russian, as in English, there are cases in which a number of consonants are consecutive (eg CCCVC...), but the typical syllable structure is a consonant and vowel repetition structure (CV, CVCV, CVCVCV, ...). This means that Russian words can be entered without ambiguity (that is, with very little ambiguity) in most cases when the repeated selection method is applied on the consonant separation keypad.

12.13 Hindi restriction input method on consonant separation keypad

In the prior application PCT/KR00/00601 of the applicant, a case of grouping Hindi consonants into 9 groups based on similarity of pronunciation was shown, and a case of grouping into 10 groups was shown in the present invention. In the case of Hindi, it was also shown that group consonants with strong similarity in pronunciation can be grouped into the same group. For example, group consonants with pronunciations of (k), (kh), (g), and (gh) in the figure presented above are grouped into one group. The same applies to the rest of the similar pronunciation groups. Among the 35 consonants of Hindi presented above, 33 consonants, excluding __(ud) and __(udh) with lower points, can be grouped into 9 groups or 8 groups arbitrarily. __(ud) and __(udh) are regarded as modified alphabets of __(d) and __(dh), respectively, and can be placed in the group to which the basic alphabet belongs.

The following is a collection of Hindi words described in the earlier application.

Hereinafter, for convenience, Hindi vowels are written in English pronunciation in parentheses next to the underscore (the Hindi alphabet of the corresponding pronunciation is considered to be in the underline) or simply written in English alphabet in parentheses. For convenience, __(aa) becomes (a-), __(ee) becomes (i-), __(oo) becomes (o-), __(ae) becomes (e), and __(aae) becomes ( ai).

The vowel __ (ri) is said to be classified as a consonant. Ten vowels, excluding the vowel __(ri), can be grouped into five groups by pairing two pairs as above.

Vowels in Hindi are largely divided into short vowels (a), (i), and (u) and long vowels __ (a-), __ (i-), and __ (u-), and the remaining four vowels are compound vowels. It is said that it can be expressed as a combination of single vowels. That is, __(e) = (a) + (i) or (a) + (i-), __(ai) = (a) + (e), __(o) = (a) + (u) or ( It is said that a) + (u-), __(au) = (a) + (o). Therefore, the basic vowels (a), (i), and (u) are divided into three groups and assigned to three buttons, and a basic vowel is entered with one stroke of each button, and the long vowel corresponding to the basic vowel is the basic vowel. It can be entered with two strokes of the assigned button, and the remaining four complex vowels can be entered as a combination of basic vowels.

For example, if (a), (i), and (u) are assigned to buttons [*], [0], and [#] respectively, __(a-) = ** and e = *0 or * to enter 00. If **0 is pressed, the system recognizes it as __(a-) when it is pressed up to “**”, but the moment “0” is pressed next, **0 is (a) + (e) = __(ai) can be recognized as Likewise, when **# is pressed, the system recognizes it as __(a-) when “**” is pressed, but the moment “#” is pressed, **# is (a) + (o) = __(au) can be recognized as

This is possible if the 10 Hindi vowels do not appear consecutively in a single word. If there are cases where vowels in Hindi appear consecutively, ambiguity may occur. That is, when **0 is entered, it is unknown whether __(a-) and __(i) were entered or __(ai) was entered. However, even if there are cases in which 10 basic vowels appear consecutively, if the frequency is small, the system basically recognizes the input value as a complex vowel when it can mean a complex vowel __(ai), such as **0. Any restrictions may be applied. In this case, if the user wants to input a combination of long vowels, __(a-), and short vowels __(i), it can be solved by using “intentional language restriction release” or “language restriction release delay time”. That is, in the example, ** is entered, and after a certain amount of time or intentionally activating the word termination function, 0 is entered.

In Hindi, the main syllable structure is the alternation of consonants and vowels, but there are also cases in which consonants appear consecutively. If another consonant occurs after a consonant ending in a vertical line, the vertical line disappears and is combined with the next consonant to form a combined consonant. A consonant without a vertical line is said to be combined with the next consonant with a “,” similar symbol at the bottom of the alphabet. In addition, there are some rules and there are irregular cases. In this way, when consonants are recognized as being input continuously (temporarily recognized or definitively recognized), it is easy to implement an automata that displays combined consonants.

Even in countries where English is not used as a native language, the English alphabet is written on the keypad and used for English input. Since Hindi and English are used as official languages in India, naturalness can be added to the use of simple codes and text input by assigning Hindi consonants and English consonants with similar pronunciation to the same button. For example, it is as follows, and variations are possible.

Above, English consonants such as z and w may be added or separately placed in appropriate groups as in the case of Chinese. In addition, in order to simplify the arrangement on the keypad, only a part of alphabets in each group may be displayed on the keypad (applying the hidden repetition selection method). For example, when assigning the first group to an arbitrary button in the above grouping, only __(k) and __(g) can be assigned. The order of selection according to the number of button presses in each group can be determined arbitrarily. You can also assign the vowel __(ri) to a button to which R L is assigned.

Again, only English vowels (English alphabet vowels) can be marked to simplify the arrangement on the keypad. As shown in the previous example, since Hindi vowels have a strong phonetic similarity with English vowels, it is very natural to mark only English vowels. Furthermore, in the case of consonants, /G K/, /M N/, /D T/, /B P/, /R L/, which have a strong similarity in pronunciation, as shown in the comparison table of Hindi consonants and English vowels above. . . The keypad can be made more concise by displaying only English consonants without omitting and displaying Hindi consonants corresponding to the group of . Of course, even if the Hindi alphabet is omitted in this way, just as Pinyin could be input without ambiguity in the Chinese restricted input mode in the Chinese example, Hindi is input without ambiguity according to the Hindi restricted input mode.

In the following, some of the contents described in the previous application are rearranged, and details are further summarized.

(k)" 다음에 "

(a-)" 가 오면 "

(a-)"의 축약형(즉, 자음결합형) "

"이 "

(k)" 와 합쳐져 "

" 로 되는 것이다. 나머지 모음에 대해서도 같으며, 자음 다음에 특정 모음이 왔을 때, 결합형으로 표시되는 것은 이미 인도어 워드프로세서에서 널리 사용되고 있다. When a Hindi vowel comes after a consonant, it is combined with the preceding consonant and expressed as the "abbreviated form" illustrated above. For example, "

(k) " followed by "

(a-)" when "

(a-) Abbreviation of "(i.e., consonant combination)"

"this "

(k) merged with "

". It is the same for the rest of the vowels, and when a specific vowel comes after a consonant, the combined form is already widely used in Indian word processors.

(a)" 의 축약형은 존재하지 않는 것으로 되어 있는데, 자음만 표기된 상태 (예. "

(k)") 가 모음 "

(a)" 를 포함하고 있는 것이라고 한다. 음성학적으로는 "

" 는 (k) 가 아닌 (ka) 라는 것이다. 가장 보편적으로 사용되는 힌디어 워드프로세서(예. "MS Word 2000 의 힌디어 IME" 를 포함하여 몇몇 제품. 이하에서는 특별히 다른 언급을 하지 않는 한 Microsoft사의 "MS Word 2000 의 힌디어 IME"을 의미) 에서는 자음 다음에 모음 "

(a)" 키가 눌러졌을 때, 자음 아래에 콤마형태(힌디어에서는 "할"이라고 함)가 결합된 글자를 출력한다. 예를 들어 "

(k)" 다음에 "

(a)" 키를 누르면, "

(k)" 를 인식하고 출력하는 것이다. 자음아래에 콤마형태가 붙은 자음(반자음=순수자음) 다음에 다른 자음이 입력되면, 소정의 규칙에 의하여 "복합자음"이 형성된다. 예를 들어 "

(k)" 다음에 "

(y)" 가 입력되면, 복합자음 "

" 가 되는 것이다. 이는 마치 한국어에서 종성으로 이중받침을 형성할 수 있는 자음들(예. "ㄹ" 과 "ㅁ")이 연속해서 입력되면, 작은 글씨로 종성 "ㄻ"이 입력되는 것과 유사하게 볼 수 있을 것이다. 복합자음 생성에는 규칙적인 형태도 있고, 불규칙한 형태도 있다고 하며, 자세한 내용은 힌디어 교과서를 참고하면 된다. 이상의 사항은 특별한 내용이 아니라 힌디어 초급교과서에 있는 내용이며 또한 이미 널리 알려진 여러 제품(힌디어 워드프로세서 등)에서 이미 널리 쓰이고 있는 내용이다. Likewise, as briefly mentioned in the earlier application, even when a consonant is followed by a consonant to form a "compound consonant", it is said that there is a certain rule (corresponding to Hindi spelling) that forms a combined letter between consonants, and it is already applied in Hindi word processors and widely It is being used. collection "

(a) The abbreviation of " does not exist, but only consonants are marked (e.g. "

(k)") is a vowel "

(a)". Phonetically, "

" is (ka), not (k). Several products, including the most commonly used Hindi word processor (eg "Hindi IME for MS Word 2000". Below, unless otherwise specified, Microsoft's " In MS Word 2000, meaning "Hindi IME"), a consonant followed by a vowel "

(a) When the " key is pressed, a letter with a comma form (called "hal" in Hindi) is output under a consonant. For example, "

(k) " followed by "

(a) When the " key is pressed, "

(k)" is recognized and output. If another consonant is input after a consonant with a comma under the consonant (half consonant = pure consonant), a "composite consonant" is formed according to a predetermined rule. For example, "

(k) " followed by "

(y)" is entered, the compound consonant "

". This is similar to how the final consonant "ㄻ" is entered in small letters when consonants that can form double endings (eg "ㄹ" and "ㅁ") are entered consecutively in Korean. It is said that there are regular and irregular forms in the production of compound consonants, and for details, you can refer to Hindi textbooks. It is already widely used in products (such as Hindi word processors).

(a)" 키가 입력되었을 때, 이를 자음아래에 할(콤마형상)이 붙은 자음이 생성되도록 할 수 있음은 자명하다. 예를 들어, "

(k)" 또는 "

(k)"를 포함한 다른 알파벳이 [1]버튼에 배정되어 있고, [1]버튼 한번 누름으로 "

(k)" 를 입력하고 나서, "

(a)" 가 배정된 버튼 (예. [*]버튼)을 누르면, "

(k)" 로 인식하는 것이다. 기존의 워드프로세서 제품의 경우에서 언급한 바와 같이, 여기서 "

(y)" 가 입력되면, 복합자음 "

" 가 되는 것은 동일하다. 다만, "

(k)" 까지 인식된 후, "

(a)"가 배정된 버튼이 한번 더 눌려지면 "

(a-)" 이 인식되어, 결과는 "

(k) +

(a-) =

" 이 되는 것은 선출원에서 출원인이 제시한 내용이다. 마찬가지로 "

(k)" 까지 인식된 후, "

(u)"가 입력되면, "

(k) +

(o) =

" 가 된다. (선출원에서 이미 언급한 대로, 복합모음을 기본모음(a, i, u)의 조합으로 입력시, "

(o) =

(a) +

(u)" 이므로)Similarly, in the present invention, after a consonant, a vowel "

(a) It is obvious that when the " key is input, it is possible to generate a consonant with a division (comma shape) under the consonant. For example, "

(k)" or "

(k) Other alphabets including " are assigned to the [1] button, and pressing the [1] button once "

(k)", then "

(a) If you press the button to which " is assigned (e.g. [*] button),

(k)". As mentioned in the case of existing word processor products, here "

(y)" is entered, the compound consonant "

Being " is the same, except that "

(k) After being recognized up to "

(a) When the button to which " is assigned is pressed once more, "

(a-)" is recognized, the result is "

(k) +

(a-) =

" What becomes is the content presented by the applicant in the earlier application. Likewise "

(k) After being recognized up to "

(u)" is entered, "

(k) +

(o) =

". (As already mentioned in the earlier application, when entering a compound vowel as a combination of basic vowels (a, i, u), "

(o) =

(a) +

(u)" so)

(a)" 키가 입력되므로 현실적으로는 자음버튼이 한번 이상 눌러지고 다음에 모음 "

(a)" 키가 눌러지고 다시 자음키가 한번 이상 눌러지는 것이다. 따라서 본 발명을 적용함에 있어서 힌디어 자음 입력에 "반복선택방법" 을 적용하더라도 모호성 없이 힌디어 단어를 입력할 수 있음을 의미한다. It is said that a word with one syllable in Hindi is made up of "(consonant) + vowel + (consonant)". Consonants in parentheses mean that the consonant may or may not occur. Likewise, two-syllable words are said to be made up of "(consonant) + vowel + consonant + vowel + (consonant)". That is, there are two vowels between the consonants to form two syllables. The same is true for words with more than two syllables. Even if the consonant is a compound consonant, the vowel "between the consonants and consonants forming the compound consonant

(a) Since the " key is entered, in reality, the consonant button is pressed more than once, and the next vowel "

(a)" key is pressed and then the consonant key is pressed one or more times. Therefore, in applying the present invention, even if the "repetitive selection method" is applied to input of Hindi consonants, it means that Hindi words can be input without ambiguity.

(a-)" 의 경우 "

(a-)"으로), 이는 명백히 사용자의 편의성에 반하는 것이다. 자음 다음에 입력되는 경우가 아닌 경우, 사용자는 모음으로 시작하는 단어를 입력하기를 의도하는 것이므로, 자동으로 모음이 기본형(예. "

(a-)")으로 인식되고 표시되어야 할 것이다. 현재 워드프로세서에서는 "shift" + "

(a-)" 버튼을 입력해야 기본형으로 인식되고 출력된다. 본 발명에서는 키보드를 사용하는 워드프로세서에서, 자음 다음에 입력되는 경우가 아닌 경우(예. 단어의 처음) 힌디어 기본형 모음이 자동으로 인식되는 발명을 추가로 제시하는 것이다. When a vowel appears at the beginning of a word, it need not appear as an abbreviation. That is, in all cases other than the case where the vowel button is pressed after the consonant is recognized (e.g., inputting the vowel key at the beginning of a word), the vowel is recognized as "basic" rather than "abbreviated" for vowel key input, and It is preferable to print out Similarly, in the Hindi word processor, when entered at the beginning of a word or after a vowel rather than after a consonant, it is displayed as an abbreviation (e.g. "

For (a-)""

(a-)"), which is obviously against the user's convenience. If it is not entered after a consonant, the user intends to enter a word that begins with a vowel, so the vowel is automatically added to the default form (eg. "

(a-)"). In current word processors, "shift" + "

(a-)" button must be input to be recognized and output as a basic form. In the present invention, in a word processor using a keyboard, when it is not entered after a consonant (eg, the beginning of a word), the basic Hindi vowel is automatically recognized It is to further present the invention to be.

(a)"키가 눌러지면, 기본형 모음 "

(a)" 가 인식되는 것이다. 본 발명에서 적용하는 예를 들면, 단어의 시작상태(예. 입력모드로 진입 직후, 또는 공백 입력 직후)에서 모음 "

(a)" 가 배정된 버튼(예. [*]버튼)을 한번 누르면, 기본형 모음 "

(a)" 가 인식되고, 다시 모음 "

(a)"를 한번 더 누르면, 모음 "

(a-)"가 인식되는 것이다. For example, when applied on the keyboard, the vowel "

(a)"When the key is pressed, the basic vowel"

(a)" is recognized. For example, applied in the present invention, in the beginning state of a word (eg, immediately after entering the input mode or immediately after entering a space), the vowel "

(a) If you press the button to which " is assigned (e.g. [*] button) once, the basic collection "

(a) " is recognized, and recollected "

(a) If you press " once more, the vowel "

(a-)" is recognized.

(a)" 버튼이 길게 눌러지면, 기본형 모음 "

(a)"로 인식하는 것이다. 다음으로 모음 "

(u)" 버튼이 짧게 눌러지면, 모음 "

(a)" 버튼의 길게누름과 모음 "

(u)" 버튼의 짧게 누름의 조합을 기본형 모음 "

(o)" 로 인식하고 출력하는 것이다. 마찬가지로 "

(k)" 다음 "

(a)" 가 눌러지면 "

"이 되고, 다시 "

(a)" 가 한번 더 눌러지면, "

=

(k) +

(a-)" 이 되고, 다시

(i) 가 입력되면 "

=

(k) +

(ai)" 가 된다. 그러나 마지막

(i) 를 길게 눌러줌으로써, "

" 를 입력할 수 있는 것이다. 여기서

(i) 가 한번 더 눌러지면 "

" 이 된다. 정리하면 모음버튼 길게누름을 통해 강제적으로 모음의 기본형이 표시되도록 할 수 있으며, 길게누름 이후 조합되는 모음 역시 기본형모음으로 표시됨을 의미한다. 이는 출원인이 제시한 모든 모음조합에 적용가능하며, 모음이 조합되는 최초의 모음버튼의 길게누름 이후 모음 버튼의 짧게 누름의 조합에 의하여 다른 모음의 기본형을 인식할 수 있다. 이는 출원인이 제시한 모음조합((a), (i), (u)의 조합) 뿐만 아니라 다른 방식의 모음조합에 의하여 모음을 입력하는 경우에도 적용할 수 있다.In the previous application, a technology for recognizing alphabets by "short press after long press" is introduced. Similarly, a "basic" vowel can be input by "long pressing" the vowel button at the beginning of vowel combination, and other basic vowels can be combined by short pressing the vowel button to be combined thereafter. For example, in the vowel combination start state after consonant input, vowel "

(a) When the " button is long pressed, the basic collection "

(a)". Next, the vowel "

(u) When the " button is pressed briefly, the vowel "

(a) " Long press and vowel of the button "

(u) " A combination of short presses of the button "

(o)" to be recognized and printed. Likewise, "

(k) "next"

(a) When " is pressed, "

"become, again"

(a) When " is pressed once more, "

=

(k) +

(a-)", then again

If (i) is entered "

=

(k) +

(ai)". But the last

(i) By long pressing, "

". Here

(i) If is pressed once more, "

". In summary, it means that the basic form of a vowel can be forcibly displayed by pressing and holding the vowel button, and the vowel that is combined after long pressing is also displayed as a basic type vowel. This can be applied to all vowel combinations proposed by the applicant. And, it is possible to recognize the basic type of another vowel by a combination of a short press of the vowel button after a long press of the first vowel button in which the vowel is combined. This is the vowel combination proposed by the applicant ((a), (i), ( It can be applied not only to the combination of u) but also to the case of inputting vowels by other types of vowel combinations.

(ri)"의 입력은 임의의 기본모음의 3번 눌러짐으로 입력할 수 있다. 예를 들어 발음이 유사한 모음 "

(i)" 버튼의 3번 눌러짐으로 입력할 수 있다. 참고로 선출원에서 "

(e) =

(a) +

(i) 또는

(a) +

(i-)" 으로 입력할 수 잇다고 하였는데, "__(e) = __(a) + __(i)" 로 입력하면 되며, 굳이 "__(e) = __(a) + __(i-)"으로 입력할 필요는 별로 없다. 다음으로 모음 "

(a-)" 에 반달표가 붙은 모음 "

" 역시 모음 __(a) 가 배정된 버튼(예. [*]버튼) 의 3번누름으로 입력할 수 있다. On the premise that four complex vowels are entered as a combination of basic vowels, "

(ri)" can be input by pressing an arbitrary basic vowel 3 times. For example, a vowel with a similar pronunciation "

(i)" can be entered by pressing the button 3 times. For reference, in the previous application, "

(e) =

(a) +

(i) or

(a) +

(i-)", but you can enter it as "__(e) = __(a) + __(i)". "You don't really need to type it as a vowel to "

(a-)" followed by a half-moon vowel "

" It can also be entered by pressing the button 3 times to which the vowel __(a) is assigned (e.g. [*] button).

(ud)", "

(udh)" 가 있고, 5개의 차용자음으로 "

(k)", "

(kh)", "

(g)", "

(j)", "

(ph)" 가 있다. 5개의 차용자음은 거의 사용되지 않는다고 한다. 이렇게 아랫점이 붙는 글자의 입력은 각 자음을 발음의 유사성에 근거하여 기 제시한 자음그룹에 두고 해당 버튼의 반복누름에 의하여 선택되도록 할 수 있다. 다음의 표는 아랫점이 붙은 자음을 발음의 유사성에 근거하여 함께 그룹핑한 사례이다. 물론 각 그룹은 임의의 버튼에 할당할 수 있으며, 변형이 가능하다. 이 경우, 하나의 버튼에 명시적으로 또는 암시적으로 할당된 알파벳의 수가 많아지면, 버튼의 반복누름의 횟수가 많아지는 단점이 있다. You can see that there is a consonant with a dot (.) under the consonant. For convenience, this will be referred to as "lower point". Among the basic consonants in Hindi, "

(ud)", "

(udh)", with five borrowed consonants "

(k)", "

(kh)", "

(g)", "

(j)", "

(ph)". Five borrowed consonants are said to be rarely used. In order to input letters with a lower point, each consonant is placed in a previously suggested consonant group based on the similarity of pronunciation and selected by repeatedly pressing the corresponding button. The following table is an example of grouping consonants with lower dots based on similarity of pronunciation. Of course, each group can be assigned to any button, and variations are possible. In this case, one button If the number of alphabets explicitly or implicitly assigned to is increased, there is a disadvantage in that the number of repeated presses of the button increases.

(k)" 는 [1]버튼에 배치, "

(ch)" 는 [2]버튼에 배치, ... "

(r)" 은 [9]버튼에 배치)할 수 있다. 또한 예를 들어 모음은, __(a), __(i), __(u) 를 각각 [*], [0], [#] 버튼에 배치하면 매우 안정감있는 키패드가 구성된다. 위의 그룹은 단지 예시일 뿐이며, 변형이 가능함은 자명하다. 또한 각 그룹을 대표하는 자음 하나씩 만을 키패드에 표시할 수도 있으나, 복수로 표시(예. [1]버튼에 "

(k)" 와 "

(g)" 표시 또는 2개 이상 표시)하는 것도 가능하며, 각 그룹은 임의의 버튼에 배정될 수 있음은 자명하다. 상기 예시에 의하여 나열된 순서로 버튼의 반복누름에 따라 알파벳이 선택된다고 하면, "

(k)"가 배정된 버튼을 한번 누르면 "

(k)" 가 인식되고, 한번 더 누르면 "

(g)" 가 인식되고, 한번 더 누르면 "

(kh)" 가 인식되는 식이다. Based on the table above, one consonant representing each consonant group can be arbitrarily placed on each button. For example, the first consonant of the above 9 groups is placed on each of the [1] to [9] buttons (i.e. "

(k)" is placed on button [1], "

(ch)" is placed on the [2] button, ... "

(r)" can be placed on the [9] button). Also, for example, for vowels, __(a), __(i), and __(u) are respectively [*], [0], [#] When placed on a button, a very stable keypad is formed. The above groups are just examples, and it is obvious that variations are possible. In addition, only one consonant representing each group can be displayed on the keypad, but multiple displays (eg. [1] button "

(k)" and "

(g)" or two or more) is also possible, and it is obvious that each group can be assigned to an arbitrary button. Assuming that the alphabet is selected by repeatedly pressing the buttons in the order listed according to the above example, "

(k) When the button to which " is assigned is pressed once, "

(k)" is recognized, and if you press it once more, "

(g)" is recognized, and if you press it once more, "

(kh)" is a recognized expression.

(d)" 를 입력한 후, 약속된 버튼(예. [6]버튼)을 길게 눌러 "

(ud)" 를 입력할 수 있다. 이 방법을 사용하면, 아랫점이 붙지 않는 알파벳에도 아랫점을 덧붙인 글자를 입력할 수 있는 범용성이 있다. Next, the "control processing method using a long press" disclosed in the previous application of the applicant can be used. For example, the consonant "

(d) After entering ", press and hold the promised button (e.g. [6] button) to "

(ud)" can be entered. Using this method, there is versatility to input characters with a bottom dot added to the alphabet without a bottom dot.

(k)" 을 입력한 후, 약속된 버튼(예. [9]버튼)을 길게 눌러 "

" 를 입력할 수 있다. And there is a consonant with a dot on top of the consonant as a sign of a half consonant (half of a non consonant). For convenience, this dot is called "upper dot". Alphabets with upper points can also be entered with "Control processing method using long press". For example, the consonant "

(k)", press and hold the promised button (e.g. [9] button) to "

" can be entered.

" - 점선으로 된 동그라미 부분에는 자음 또는 모음이 위치함)가 붙는 것이다. 이를 편의상 "반달점" 이라 부른다. 모음 "

(a)" 는 생략되어 표시되지 않으므로, 실제로는 반달점이 모음 또는 자음위에 붙게된다. 마찬가지로 "길게누름을 이용한 컨트롤처리방법" 으로 입력할 수 있다. 예를 들어, "

(k)" 다음 "

(a-)" 을 입력하면 "

(ka-)" 가 되고, 다시 약속된 버튼(예. [8]버튼)을 길게 누르면, "

" 가 된다. 역시, "

(k)" 다음 약속된 버튼(예. [8]버튼)을 길게 누르면, "

" 가 된다. 만약 "

(k)" 를 포함한 알파벳 그룹이 [8]버튼에 할당되고, [8]버튼에 "

(k)" 하나 또는 다른 알파벳이 함께 배치되어 있다면, "

" 는 "88~" 로 입력됨을 알 수 있다. (여기서 "8~" 은 [8]버튼을 길게 누르는 것을 의미)Next, the nasal vowel (nasal vowel) in which the vowel is nasalized is a "half-moon + dot" symbol ("

" - A consonant or vowel is placed in the dotted circle part). This is called a "half-moon point" for convenience. Vowels "

(a)" is omitted and not displayed, so the half-moon point is actually attached to the vowel or consonant. Likewise, it can be entered with "Control processing method using long press". For example, "

(k) "next"

(a-)" if you type "

(ka-)", and if you press and hold the promised button (e.g. [8] button), "

" becomes. After all, "

(k)" Press and hold the next promised button (e.g. [8] button), "

" becomes. If "

(k) An alphabetic group including " is assigned to the [8] button, and the [8] button is "

(k)" if one or the other alphabets are co-located, "

" is entered as "88~". (Here, "8~" means long-pressing the [8] button)

Next, we will briefly show an example of applying the parallel input method under the Hindi input method exemplified above. It was said that a Hindi syllable starts with "consonant + vowel + ..." or "vowel + ...", and has a structure in which consonants and vowels alternate. Therefore, when inputting Hindi, parallel input using "(first vowel) + syllable standard initial code" or "(first vowel value) + syllable standard initial value simple code" is possible. Similarly, "(first vowel) + simple code based on consonant" or "(first vowel value) + simple code based on consonant value" can be utilized. Parentheses are used for "first vowel" and "first vowel value" because some syllables start with consonants.

(s) 가 입력되고 나서 모음버튼이 입력되지 않고, 다른 자음버튼(예. (t) 그룹의 알파벳이 배정된 버튼)이 입력되는 순간 자음이 연속하므로 힌디어 제한(힌디어 단어생성 규칙)을 위반하므로 입력값을 심플코드로 해석하는 것이다.

(s) 가 입력되고 나서

(t') 가 입력되면 단어의 처음이 "

(s)__

(t')..." 와 일치하는 단어를 사용자에 추천(예. 리스트 형태)하여 줄 것이다. 만약 한번 더 (t)그룹의 알파벳이 배정된 버튼이 눌러지면, "

(s)__

(th)..." 와 일치하는 단어를 사용자에 추천하여 줄 것이다. (밑줄부분에는 모음이 있음을 의미) "

(s)__

(th)..." 까지 입력되면 이에 일치하는 단어 "

", ... 등등의 단어를 사용자에 추천하여 줄 수 있다. 마찬가지로 "모음+자음" 이 인식되고, 다시 모음버튼의 입력없이 다른 자음버튼이 눌러지는 순간 입력값을 심플코드로 해석하여 처리할 수 있다. 이 경우는 "첫모음+자음+___+자음..."이 일치하는 단어를 사용자에 추천하여 주게 될 것이다. Assuming that "(first vowel value) + syllable standard initial value simple code" is used as the short input value, an example of the full-priority parallel input method is as follows. If a consonant is entered as the first input after the word starts and the consonant is entered again without the vowel button being pressed, it violates the Hindi restriction (Hindi word generation rule) in which consonants and vowels alternate. , and a word in which the consonants of the first syllable and the consonants of the second syllable match are recommended to the user. as a specific example

The vowel button is not entered after (s) is entered, and the consonant continues at the moment when another consonant button (eg. (t) group alphabet assigned button) is entered, violating the Hindi restriction (Hindi word generation rule). It is to interpret the input value as a simple code.

After (s) is entered

If (t') is entered, the beginning of the word is "

(s)__

(t')..." will be recommended to the user (eg in the form of a list). If the button assigned to the alphabet of the (t) group is pressed once more, "

(s)__

(th)..." will be suggested to the user. (The underscore means there is a vowel) "

(s)__

If up to (th)..." is entered, the word that matches "

Words such as ", ..., etc. can be recommended to the user. Likewise, "vowel + consonant" is recognized, and the moment another consonant button is pressed without inputting the vowel button again, the input value is interpreted as a simple code and processed. In this case, words that match "first vowel + consonant + ___ + consonant..." will be recommended to the user.

(k)__

(g)..." 와 같은 입력값을 처리하려면, " (k)" 입력후 일정시간(선출원에서 언급한 언어제한해제 지연시간 또는 이타지연시간) 동안의 시간지연을 통하여 "

(k)" 를 확정하고 나서, "

(g)" 를 입력하는 식으로 가능하다. 또는 약속(예. 우측이동버튼 누름)에 따라 기 입력된 "

(k)" 를 확정하고 나서 "

(g)" 를 입력하는 식으로 가능하다. 이러한 병행입력방법의 사례는 모두 선출원에서 언급(PC용 키보드 및 키패드에서 적용가능함)한 것으로 새로운 내용이 아니다. If a combination of only consonants on the same button (e.g. "

(k)__

In order to process an input value such as "(g)...", after inputting "(k)", through a time delay for a certain time (language restriction release delay time or other delay time mentioned in the earlier application), "

(k) After confirming "

(g) It is possible by entering "

(k) after confirming "

It is possible by entering "(g)". All examples of these parallel input methods are mentioned in the previous application (applicable to PC keyboards and keypads), and are not new.

In the present invention, it has been described that alphabets are recognized in response to "button pressing". In the detailed part of the program, in practice, a predetermined alphabet is recognized when a button is pressed, an alphabet is not recognized when a button is pressed, and a predetermined alphabet is recognized when a button is pressed and then released. Of course, the expression "button pressing" in the present invention includes the case where the alphabet is recognized the moment it is pressed and released. This is also the same in other contents of the present invention.

12.14 Language Restriction Input Method on the Consonant Separation Keypad

Half consonants (i.e., half vowels) are slightly different for each language. In English, w, y, j, etc. are generally treated as half consonants, and some languages exclude j, while others include v. do it too In general, w and y seem to be treated as half consonants in common in almost all languages.

Here, since half consonants have similar properties and phonetic values to vowels, putting half consonants into a separate group is an extension of grouping consonants based on similarity in pronunciation.

In addition, among the English alphabets for each language, there are alphabets that are not used in a specific language (for example, k and w, which are said to be used only in foreign words in Spanish), and alphabets other than English alphabets (applicants call them modified or additional alphabets for convenience). ) is also used. Alphabets that are not used among English alphabets will also be needed for input of commonly used English. Therefore, if there are not many Roman alphabets that are not used in a specific language, they can be grouped together with half consonants and assigned to the same button. Reference may be made to Fig. 10-6 in Chinese.

Also, alphabets that are not used in a specific language can be grouped together and assigned to the same button.

12.15 Language Restriction Input Method on Incomplete Consonant Separation Keypad

In the present invention, it was shown that ambiguity can be removed or minimized by constructing a consonant separation keypad optimized for each language and applying a repetitive selection method. In addition, by configuring the consonant separation keypad in this way, the algorithm of the input system can be simplified. It is obvious that various modifications are possible based on this. Therefore, the case of slightly modifying this and assigning consonants and consonants to some buttons is also a modified category of the language restriction input method in the consonant sound separation keypad presented in the present invention. For convenience, this is called an "incomplete consonant-consonant separation keypad", and a button assigned with consonants is called a "consonant-consonant mixing button" for convenience.

For example, in the consonant and vowel separation keypad, the vowel “i” and (half) consonant “y” are grouped together, assigned to a specific button, and consonants (here, half consonants) and vowels are grouped in a predetermined order according to the number of button presses. It can also be selected (the remaining buttons are separated into consonant buttons and vowel buttons). If there are no consecutive occurrences like “iy” or “yi”, Chinese pinyin input is possible without ambiguity by applying the Chinese restriction input method. In this case, assuming that consonants are selected in the order of “y” (press once) and “i” (press twice) according to the number of presses of the specific button mixed and assigned, and after the consonant button is pressed, the consonant sound mixture button The moment it is pressed once, since the input of the previous consonant button is confirmed as having entered a consonant, the system does not temporarily consider that “y” was input for the consonant mixture button being pressed once, and the vowel “i” is input. can be determined as This is because in Chinese you can use language restrictions where the consonant “y” cannot occur after a certain consonant.

For another example, the vowel “i” and the consonant “j” or the vowel “i” and the consonant “k” can be grouped into the same group, and the repeated selection method (language restriction) can be applied. When inputting Chinese Pinyin, “… ik… " or "… ki… Ambiguity may occur if there are consecutive cases such as “.” Assigning consonants and vowels to some buttons together for no particular reason complicates the input algorithm, reduces the efficiency of the input system configuration, and is not better than applying the language-restricted input method on a complete consonant-consonant separation keypad. . However, due to the nature of each language, consonant-consonant mixture buttons may be placed on some buttons for the special purpose of allocating consonants to all 10 number buttons (refer to the case of Korean).

This can be applied by modifying the flowchart of FIG. 10-7. See Figures 10-9. The case where there is one or more consonant-vowel mix buttons is the same, and the case where two or more consonant vowels are assigned to one consonant-vowel mix button is the same. Applying language restrictions on the incomplete consonant-consonant separation keypad is a little more complicated (see the case of “i” and “y” above), and since the consonant and vowel combination rules for each language must be applied, each language A flow chart in which language restrictions are applied in detail may be more complicated than in FIGS. 10-9. 10-9 is considered to be a partial modification of FIG. 10-7 and a very simplified expression of only the general content.

For example, when inputting Chinese pinyin on the standard English keypad of FIG. 5-1, since five vowels are assigned to different buttons, the vowels can be recognized without ambiguity. In the case of a consonant, if a consonant comes after "~ vowel + n", it can be recognized without ambiguity. When "~ vowel + n + m" is entered in "~ n + X" ('X' is the English consonant for the Virgin Mary), the vowel "o" assigned together to the [6] button is combined. When a possible vowel (for example, the vowel 'a') is encountered, it can be temporarily recognized as "~ao". However, since normal Chinese bottle syllables do not end with "m", the previous input value can be recognized as "~ anm + vowel" by looking at the vowel recognized by the next input value. If "a" is entered after a vowel that cannot be combined (for example, 'e') and "n + m = 666" is entered, it is not "~eo" by using the language restriction that "eo" cannot be combined. It can be processed with "~enm~" (since '~emn~' is not possible in Chinese Pinyin).

When a consonant follows a syllable ending in "~ vowel + ng", ambiguity may occur. For example, "~ngg~" can be recognized as "~nh~". For Chinese, the system can retrieve all Chinese characters matching "~ngg~" and "~nh~" from the index and provide them to the user. In the case of "~ ngh + vowel ~", it can be recognized as "~ ni + vowel". If the next recognized vowel is a vowel that cannot be combined after "i" (for example, 'u'), the input value can be recognized as "~nghu". Chinese characters corresponding to all of "~ni+vowels~" can be searched and processed. In addition, when some ambiguity occurs, all words matching possible interpretation results can be searched and provided to the user.

In the standard English keypad of Fig. 1-1, when Chinese Pinyin is input by applying the Chinese restriction repetition selection method, there are cases where "~ ngh + vowel ~" can be recognized as "~ ni + vowel", and in this case, both It was said that matching phrases can be searched and processed in the Pinyin index. When all full codes (full codes in the iterative selection method based on Figure 1-1) are stored in the Pinyin index, all cases where the input value can be generated (e.g. .“~ngh+vowel” and “~ni+vowel”), the system can recognize matching phrases by searching the index.

For example, when applying the repeated selection method in FIGS. 1-1 and 5-1, “222” can be recognized as “aaa”, “ab”, “ba”, and “c”. Therefore, in FIGS. 1-1 and 5-1, "beijing = 22334445444664", where a group of consecutive numbers can be recognized as a plurality of alphabet combinations. “22~”, a group of consecutive numbers, can be interpreted as “aa” or “b”. “~33~” can be interpreted as “dd” or “e”. Therefore, “2233~” can be interpreted as “aadd~”, “aae~”, “bdd~” or “be~”. As the input value increases, the number of possible combinations increases exponentially. Such an interpretable alphabet combination for the input value is also called a “possible alphabet combination” or a “candidate alphabet combination” for convenience.

However, when “22~” is pressed, it can be interpreted as “aa~” or “b~”, and when the system checks that the word starting with “aa~” no longer exists in the index by referring to the index, , the system can process the input value “22~” as “b~”, excluding combinations starting with “aa~”. This can be seen similarly to the way that the input value “22~” can be interpreted as “b~” using the Chinese restriction that Chinese Pinyin does not start with “aa~”. Therefore, when “2233~” is pressed, the index is searched only for the two combinations of “bdd~” and “be~”, and here again, the phrase starting with “bdd~” no longer exists in the index. When the system confirms, combinations starting with “bdd~” are no longer considered, and only “be~” is processed according to the following input values. It can also be seen as similar to processing “input value “2233~” as “be~” by using the Chinese restriction that “bdd~” is not possible in Chinese Pinyin. It can be interpreted as “beg~” for the input value “22334~”. In addition, the input value “223344~” can be interpreted as “begg~” or “beh~”. The moment the system searches the Pinyin index and confirms that there are no more words starting with “begg~”, the system inputs The value “223344~” is processed as “beh~”. This can be seen as similar to using a Chinese restricted input method (e.g., an input method using Chinese restrictions where “begg~” is not a valid syllable and only “beh ~” is a valid Pinyin syllable based on Chinese Pinyin generation rules). If “4” is pressed once more and the input value becomes “2233444~”, it can be interpreted as “behg~” or “bei~”. As soon as the system confirms that it does not, the input value can be processed as “bei~”, and since this is a Pinyin combination where “behg~” is not possible in the Chinese restricted input method, the input value “2233444~” is interpreted as “bei~” It can be seen as similar to processing

In a system that stores all words and full codes to be entered, the number of candidate alphabet combinations in “beijing = 22334445444664” is 2*2*4*1*4*2*1 = 128. Of course, it is also included in the scope of the present invention to compare all of these 128 candidate alphabet combinations with the index and process only matching words. However, in a system that can recognize an input value from the beginning of the input, as the input value increases, alphabet combinations that do not exist in the index (in the example above, 'aa~', 'bdd~', behg~', etc.) Excluding at the beginning of the input would be useful.

In this way, among a large number of candidate alphabet combinations generated as the same input value in the iterative selection method continuously increases, the system can search for only some candidate alphabet combinations existing in the index. If it is confirmed that all candidate alphabet combinations by the input value do not exist in the index, the system can treat the input value as a simple code of the promised type.

12.16 Application of non-hidden control processing method

In the consonant separation keypad above, an arbitrary button (a button within the 3*4 keypad or a separate external button) is set as a control button, only the representative alphabet is selected with one stroke of the corresponding button, and the rest of the alphabet can be input by the control processing method can For example, in the keypad of FIG. 10-6, “w, y, v” assigned to the [0] button is assigned to any consonant button, and the [0] button is used as a control button to obtain “p = b + 0 = 10” (when applying input after control). This has already been mentioned in the earlier application.

13. of the input Parallel input method judged by length

The length of the shortcode stored in the index may be less than a certain number in some cases. In addition, in a specific case, the type of short code entered by the user or by the system (eg, type 1 (city name), type 2 (bank name), . . . In the previous application, type 1 and type 2 are grouped in a tree form) can be built) can be specified. Assuming that the type of shortcode entered as type 1 (city name) is specified and the length of the city name shortcode is 3 or less, when the parallel input method with the short input method as the default mode is applied, the length of the input value is 3 When it exceeds , the system considers the input value as a full code and can process it. Conversely, when applying the full-priority parallel input method, if three input values are entered and a word termination function (eg, blank) is entered, the system can treat the input value as a simple code.

This will be particularly useful in cases where the length of a short code of a specific type (city name - Beijing, company name - 四通集團, . . . ) can be less than a certain length, such as Korean and Chinese (specific Since tangible nouns are often composed of a certain number of syllables or less, and it is natural to use them as short codes for syllable-based initial codes. The length of the code becomes 2).

It determines whether the input value is a short code or a full code at the beginning of the input and does not have to provide it to the user. It can also be useful if That is, it is possible to simplify the implementation and improve the performance of the system because it does not search the shortcode index every time an input value is entered, but only checks whether the length of the input value is greater than or equal to a certain length.

14. Parallel input method with language restrictions

The language-restricted parallel input method applies the full-priority parallel input method, the moment the input value violates the “word generation rule” of a specific language (ie, the moment it violates the language restriction), the system considers the input value as a simple code and is to process If it is confirmed that the value matching the input value no longer exists in the simple code index, the input value can be treated as a full code again.

14.1 Language-restricted parallel input method using the language-restricted repeated selection method as the full input method

14.1.1 Chinese

In particular, the Chinese syllable-based initial code based on Figs. 10-1 to 10-4 has only the numeric values of consonant buttons [1] to [9] (even when vowels a, o, and e are used alone It is said that there is, but it is said to be an exclamation, and practically there are few, and when the vowels i, u, ..u are used alone, y, w, and y are added in front, respectively). In the example of Figures 10-1 to 10-4, the full code to which the repeated selection method is applied is the second or at least the third input value in most cases is one of the [*], [0] or [#] buttons for vowel input. should be entered. As mentioned in the Korean example of the previous application (method using vowel elements), this property is a good property to know whether or not the input value forms a full code at the beginning of the input when the "parallel input method" is applied. provides

For example, in the parallel input method (full-priority parallel input method) using the repetitive selection method based on Figs. 10-1 to 10-4 as the full input method and using the full input mode as the basic input mode, input If the value "693 ... = shk ..." is entered, the moment the third value [3] is entered, the input value does not form a full code (even if it is possible up to 'sh', the next consonant 'k' Since the system can recognize it, the system can treat the input value as a simple code. Again, “112 … =pd... ” is entered, the moment the third input value [2] is entered, the input value does not form a full code (in Chinese input, '11' cannot be 'bb' and can only be interpreted as 'p', If the Roman alphabet consonant d or t comes after p, the system recognizes the Chinese syllable), and the system can treat the input value as a simple code. Similarly, “7771 … =wb... ” is entered, the moment the 4th input value [1] is entered, the system can process the input value as a simple code. After all, in most cases, when the second or third input value is entered, the system can know whether the input value is full code or not.

“14 … = bj... ” is entered, the moment the second input value [4] is entered, the system recognizes that the input value does not form a valid Chinese syllable (because there are no cases where Roman alphabet consonants are combined, such as bj in the Chinese Virgin Mary), The input value can be treated as a simple code. That is, in FIG. 10-5, the system can provide the user with “Bejing” or “Beijing”, which is a corresponding phrase of the simple code “14”. If there is no “14” or simple code starting with “14” in the simple code index, the system considers the input value as full code again and provides “bj” to the user.

This is the same as in the case of Korean language using vowel elements (Figs. 4-5). The full input method in FIGS. 4-5 described above can be seen as a Korean-restricted iterative selection method, and when applying the full-priority parallel input method, when “12” is input, the input value does not form a valid Korean syllable, so the system considers the input value as a simple code and provides the user with a phrase corresponding to the simple code by referring to the simple code index. However, if it is confirmed that the simple code matching “12” no longer exists in the simple code index, the system considers the input value as full code again and provides “ㄱㄴ” to the user.

In order to help understanding, the simple codes are displayed in a sorted state in the simple code index of FIGS. 5-4 and 10-5, but it does not matter in what form they are stored inside the system. However, if necessary when searching the simple code index, the system is to sort the simple codes and check whether the input value exists in the simple code index any more.

In addition, a parallel input method using the shortened input mode (assuming that only syllable-based initial codes consisting of [1] to [9] are stored based on Fig. 10-1 in the simple code index to be searched) as the basic input mode (Short-priority parallel input method), the moment the second value [*] in the input value "1* ..." is entered, the system can recognize and process the input value as full code without searching the simple code index. have. This is also the same as the case of Korean in FIG. 5-4.

In Figures 5-4 and 10-5, the Pinyin/Chinese character index and the simple code index are described as one index. However, as shown in Fig. 5-1, there is a Pinyin / Chinese character index (simply called "Pinyin index". An index that stores "Pinyin + Pinyin corresponding Chinese characters" - for searching corresponding Chinese characters from the input Pinyin), and a simple code /Pinyin index (simply called "simple code index". It is self-evident that an index that stores "simple code + simple code corresponding Pinyin + Pinyin corresponding Chinese character" or "simple code + simple code corresponding Pinyin") can be separately placed do.

As shown in FIGS. 5-4 and 10-5, it is not necessary that only the syllable-based initial code is stored in the simple code index, and other types of simple codes such as the consonant-based initial code may be stored together. Likewise, depending on the type of simple code, it may be implemented by putting each index, such as a syllable-based initial code index, a consonant-based initial code index, or a total associated simple code index.

As shown in FIGS. 10-10, it is assumed that "Beijing" has a syllable-based initial code "14", a consonant-based simple code "1473", and a total association simple code "1*#4#73". When applying the Chinese restriction full priority parallel input method in the keypad of FIGS. 10-10, in the case of the syllable-based initial code "14" and the consonant-based simple code "1473", the moment the second input value "7" is pressed, the system inputs The value can be regarded as a simple code and processed by searching the index. By the way, in the case of "1*#4#73", the overall related simple code of "beijing", if the input value "1*#4 ..." is interpreted as a full code, it becomes "baiz ...", and "1* Up to #4" does not violate the rules of pinyin generation. However, "baiz ..." (and "baij ..." - since it can be "baij ..." according to the following input value) is not a Pinyin that exists in the Pinyin index of Figures 10-11. Therefore, the system interprets the input value as a full code according to each input value, and the input value becomes "b... => ba... => bai... => baiz..." For each recognition, the pinyin index is consulted to find a matching phrase. As shown in Figure 10-10, it is possible to find matching Pinyin up to "bai~", but as soon as the input value is recognized as "baiz~" (and potential "baij~"), the system no longer matches the phrase in the Pinyin index. It is possible to confirm that there is no (see (1) in Fig. 10-10). Therefore, the input value "1*#4 ..." up to "baiz~" is regarded as a simple code, and a matching phrase can be searched by referring to the simple code index (Fig. 10-11 (2)-(A ), see (2)-(B)). Here, even in the simple code index, if a phrase matching the input value "1*#4# ..." cannot be found, the system may consider the input value as full code again and process it as "bai ...".

Due to the characteristics of Chinese, which is a meaning character, all Pinyin and Chinese character indexes (Pinyin/Hanja index) must be stored in the system, so even if the input value forms a valid Pinyin syllable, the system confirms that it does not exist in the Pinyin/Hanja index This means that the value is treated as a simple code. This can be seen in the same context as processing the input value as a simple code the moment the system recognizes that the input value does not form a full code.

When there are different types of simple codes for the same word, it is possible to have a simple code in any form as a multiple kata for one Pinyin as shown in FIG. 10-10 or FIG. 10-11. In processing by considering the input value as a simple code (that is, processing by considering the input value as an abbreviated input), the processing of (2)-(A) or (2)-(B) in FIG. 10-11 Optionally possible. If the process of (2)-(B) in Figs. 10-11 is used, it is not necessary to have a simple code in the index. The process of (2)-(B) compares the combination of pinyin that can be achieved by the input value with the pinyin of the index for each input value, and searches for the matching pinyin. The combination of pinyin that the input value can achieve is that 2 alphabets are assigned to the [1] button and 3 alphabets are assigned to the [*] button, so when “1*” is pressed, the alphabets assigned to each button It is easy to see that 6 (= 2x3) combinations of are possible. For convenience, this is referred to as "simple code possible alphabet combination" or "possible alphabet combination". In Figures 10-11, since two alphabets are assigned to the [#] button, 12 combinations are possible when "1 * #" is pressed, and 24 combinations are possible when "1 * # 4" is pressed. However, when implemented in the system, since there is no Pinyin starting with "poi ..." in the actual Chinese Pinyin dictionary, combinations below "poi ..." can be excluded from consideration. That is, with respect to the input value "1*#4", "poi..." and "poij..." which are combinations below "poi..." can also be excluded. Similarly, it is possible to search for Pinyin that matches the input value while excluding "poi ..." as well as combinations that do not exist in the Pinyin index among possible alphabet combinations.

Using the process of (2)-(A) in Figs. 10-11 requires a simple code in the index, but it can also handle cases where an irregularly defined simple code is used. Using the process of (2)-(B) does not require storing simple codes in the index, but requires the premise that simple codes with certain rules (for example, all related simple codes) are input, and the system It is necessary to know in advance the promised simple code type (eg, fully associated simple code).

Due to the nature of Chinese, which must have an index of all Pinyin / Chinese characters you want to input, as shown in Figs. 10-12 and 10-13, when the value interpreted as a full code does not exist in the index, the input value , Shortcut input value) and processing is possible. When applying the full-priority parallel input method, FIGS. 10-12 show procedures generally applicable to Chinese input. This can be equally applied to a full-priority parallel input method using a syllable-based initial code or a consonant-based simple code. For example, if a syllable-based initial code is entered, the system interprets it as a full code and searches the Pinyin index. In most cases, the moment the second or third input values are entered, the input value no longer exists in the Pinyin index Because the system can recognize it. 10-13 show that a procedure for checking whether the input value constitutes a valid Pinyin syllable is added before searching the Pinyin index using the linguistic characteristics of Chinese.

In the input system of not only Chinese but also other languages, when the system stores the index of all words to be input, as in the procedures in FIGS. 10-12 and 10-13, each input value is input. Each time, the input value is interpreted as a full code, the word in the index is searched for and matched, and if the matching word no longer exists, it is possible to treat the input value as a short code and process it.

14.1.2 English, etc.

When the 4th consonant is recognized as input from the start of the first word starting with "st~" or "sp~", and 3 from the start of the first word without starting with "st~" or "sp~" As soon as it is recognized that the th consonant is input, the system can treat the input value as a simple code.

For example, when the simple repetition selection method is applied to the keypad of FIG. Since it violates, the system can treat the input value as a simple code. If “4678255 = install”, the simple code related to all installs, is stored in the simple code index, the system can provide the simple code corresponding phrase, install, to the user. In the simple code index of the search range, “467… If there is no simple code that matches ”, the input value can be treated as a full code again.

And, as described above, if the English restriction repetition selection method is used as a full input method on the consonant separation keypad, the input value is set according to the English input rules (e.g., without starting with "st~" or "sp~" from the beginning of the word). Since it is easy to see whether the three consonants violate), the parallel input method can be applied more efficiently.

14.2 Parallel input method with language restrictions using the control processing method excluding representative alphabets as the full input method

In FIG. 1-1, when the first alphabet of each button is input as one stroke of the corresponding button as the representative alphabet, and the remaining alphabet is input by the control processing method (ie, the control processing method other than the representative alphabet is applied), the English described above By utilizing the word generation rule, it is possible to apply the language restriction parallel input method that treats the input value as a simple code when the word generation rule is violated.

For example, in FIG. 1-1, when the first alphabet is the representative alphabet and the remaining alphabets are input by the control processing method, the moment the third input value [7] is input when “467 ... = gms ...” is input Since the input value violates the word generation rules of English, the system can treat the input value as a simple code.

Likewise, it can be similarly applied to languages other than English, and the rest is similar to the language-restricted parallel input method in which the repetitive selection method is the full input method.

14.3 Overcoming the 3rd ambiguity in the language restriction parallel input method

In the case of entering “72673”, a simple code related to the whole of “scope”, when the system first recognizes it as a full code, it becomes “72673 = pampd” and the input value does not violate the English word generation rule, so the system firstly recognizes the input value as a full code, and secondarily interprets the input value as a simple code and recognizes it as a scope corresponding to the simple code, resulting in “third ambiguity”. Here, as the full input method, a simple repetition selection method is applied based on FIG. 1-1.

In this case, the system primarily provides pampd to the user. However, if the user wants to enter the scope, he or she can select the scope by pressing a specific button (for example, the down arrow [v] button). Or, when “72673” is entered and word input is terminated (for example, when a space is entered), “pampd”, which interprets the input value primarily as full code, and “scope”, which interprets the simple code as user You can also provide it as a list and let the user select it.

The above case can be similarly applied to the parallel input method using the control processing method excluding representative alphabets as the full input method. In addition, in the short-priority parallel input method rather than the full-priority parallel input method, even if the input value exists in the simple code index at the time the word ends after inputting the input value, when the input value is regarded as a full code, language restrictions are not enforced. If there is no violation (if third-order ambiguity occurs), the user can be made to make a selection (press a specific button repeatedly or select from a list).

It can be similarly applied to languages other than English (in particular, the case of Japanese to which the control processing method excluding representative alphabets is applied).

In order to select one of a plurality of candidates, it is possible to select a target phrase among candidate phrases output by the system by using an arbitrary button that is not frequently used among the movement buttons. It has already been described that this can be applied not only to cases where tertiary ambiguity occurs, but also to all cases where ambiguity occurs.

15. Parallel input method using character strings that violate language restrictions

It was said that the input value (full code or simple code) could be interpreted either on the client side or on the server side. 11-1 and 11-2 are views of the previous application showing a case of analysis on the client side and a case of analysis on the server side, respectively. In other words, if you simply say "system", it is a concept that encompasses both client-side and server-side systems. If the input value is a simple code, if the client side interprets it and transmits the simple code corresponding phrase to the server side as a text, the server side can use it to provide various services. Similarly, when the input value is transmitted as a number to the server side and interpreted by the server side, the server side can interpret the simple code and use it for various services. Sending a DTMF tone on the client side and receiving and utilizing this input value on the server side is, of course, one of the cases of transmitting numeric values from the client side to the server side.

In the language-restricted parallel input method, when the input value violates the language restriction (ie, the input value does not form valid syllables of a specific language), the system treats the input value as a simple code and processes it, but enters it in the index of the simple code. A simple code that matches the value may not exist. In this case, it is said that the input value is regarded as a full code again. However, for example, when the user inputs "7799" with "Samsung Electronics" in mind based on Figs. If you don't store "e", the system will simply assume that "ㅅㅅㅅㅅ" was entered by the user. In the case of a securities information system, if the client side transmits the input value "7799" to the server side, or if Samsung Electronics corresponding to the input value "7799" is transmitted to the server side, the stock information server can interpret "7799". (Assuming that the stock information server has the simple code "7799" and the simple code corresponding phrase "Samsung Electronics"). However, after the user inputs "7799" in the character input mode on the client side, the client side considers the input value as a simple code and processes it, and since "7799" does not exist in the client side simple code index, it is returned to full code. When the character string "ㅅㅅㅅ지" is transmitted to the server side, it becomes difficult to utilize it in the stock information server.

Therefore, in the stock information server, if the transmitted string "ㅅㅅㅅ지" is not a value that has meaning, "7799" used to input "ㅅㅅジジ" is extracted, and "Samsung Electronics", the corresponding phrase of the simple code "7799", is extracted. It can be tracked and utilized in the system. Or, as another method that can be applied only when using a syllable-based initial code as a simple code in Korean, the system tracks "Samsung Electronics" whose first consonant of a syllable matches "ㅅㅅㅅ지" among phrases corresponding to simple codes and utilizes it. service can be provided.

This can be equally applied in a PC environment using a keyboard rather than a keypad. That is, in a stock information system using an existing PC as a client, the user had to input "Samsung Electronics" to inquire the stock price of "Samsung Electronics", but even if he only inputs "ㅅㅅㅅㅅㅅ" and transmits it to the server side, the stock information server The system recognizes that "ㅅㅅ지지" does not exist in the listed company name as a list of words, and uses the two methods described above (after extracting "7799", "Samsung Electronics" is tracked or the first consonant of the syllable is matched with It is possible to provide services by tracking "Samsung Electronics".

Another method is to register not only “7799 (simple code), Samsung Electronics (word corresponding to simple code)” in the server-side index, but also “ssjj (referred to as 'simple code correspondence' for convenience)”, and send After confirming that the value “ㅅㅅㅅ지” does not form a valid Korean syllable and comparing it with the stored simple code corresponding character, it is possible to find out that the user's intention is “Samsung Electronics”.

If the above contents are summarized in a figure, it is as shown in Fig. 11-3, and (A), (B), and (C) are selectively possible.

Furthermore, even in the case of inputting characters through a device such as a keyboard on a client such as a PC (for example, when inputting characters using a word processor of a PC), syllable-based initial codes are used. By entering only the first consonant of a syllable and converting it into a target phrase in the system (client or server), it is possible to input text at high speed or to utilize it in various information systems. For example, if the user wants to enter “Samsung Electronics”, and the user enters “ㅅㅅㅁ지”, the system can search the index and provide “Samsung Electronics” with the first consonant of the syllable as “ㅅㅅㅅㅅ” to the user. The other methods described above (simple code extraction and index search of input values based on a specific keypad promised, and storing characters corresponding to simple codes in the index) can also be applied. Reference may be made to Fig. 11-5. (A), (B), and (C) are optionally possible.

Up until now, in registering common phrases and inputting them, it was simply designated to be input by combining special function buttons and number buttons, etc., regardless of their relationship with phrases. For example, register "Samsung Electronics" as a common phrase and input "alt + 1".

Similarly, based on Fig. 10-2, the syllable of “四通集團 (satongjipdan: since the applicant does not know Chinese pronunciation, Korean pronunciation is regarded as Chinese Pinyin for convenience, but similarly applied to Chinese pronunciation)” The standard initial code is “6242” corresponding to s, t, j, and d. When the user inputs “6242”, if 6242 and Satongjipdan are not registered in the simple code index of the client-side system, the client-side system only provides “sdzd” to the user. When the user transmits “sdzd” to the server side, since “sdzd” does not form a valid Chinese syllable, the server side extracts the input value “6242” entered by the user from “sdzd” and uses a simple code (here, the syllable-based initial Code) “四通集團” corresponding to “6242” can be searched (assuming that the server side system stores simple codes and corresponding phrases).

In the case of Korean, “sdzd” and other deformable consonant combinations ( For example, “xdjd”, “stjt”, “sdjt”, … 16 cases) and the first consonant of each syllable can be provided to the user.

Also, since the server side stores the simple code corresponding character “sdzd” together, and the value “sdzd” transmitted from the client side does not form a valid Chinese syllable, the transmitted value and the simple code corresponding character of the index are compared to determine what the user intends. The system can find out that it is “Four Communications Group”.

The above contents are summarized in figures as shown in Fig. 11-4, and (A), (B), and (C) are selectively possible.

The processing in Figs. 11-3 and 11-4 may be performed on the server side or on the client side.

In information communication devices such as PCs as well as devices equipped with keypads, when a user inputs “stjd”, a word (“四通集團”) matching the first consonant of a syllable of Chinese Pinyin can be searched and provided to the user. Or, when the user inputs “stjd”, the system (eg PC) registers the short code (simple code corresponding character) as “stjd”, the first consonant of each syllable, and the moment the second consonant is entered, the Chinese language restriction is violated ( Since two Roman alphabet consonants, not sh, ch, zh, etc., appear), the input value can be regarded as a shortened input value (considered that the user is entering a shortened input) and processed. Extracting a simple code from the input value “stjd” can extract a simple code (eg 6242) by a pre-arranged keypad (eg 10-2). 11-6 can be referred to, and (A), (B), and (C) are optionally possible.

11-6 (B) shows the word that the input value generates and that does not generate a valid Pinyin syllable (in the example, “stjd” as “syllable standard initial value”) and the first letter of each syllable of the phrase stored in the index ( "sa-tong-jip-dan => stjd") to find matching phrases. This can be seen as using the syllable-based initial value as a shortened input value. In the keypad of Fig. 10-*, the syllable standard initial value corresponding to "stjd" is "622442". 11-6(B), as can be easily seen from the drawing, it is possible only to have a pinyin index for inputting Chinese characters without having a simple code index. Likewise, even if the input value is "consonant reference input value", the system can search for a word (string) generated by the input value and a phrase whose consonant of the phrase stored in the index matches.

In summary, the type of input value that can be recognized regularly is "syllable-based initial value" similar to the type of simple code (for example, the syllable-based initial value of "beijing" is "144 = bj" ), "consonant standard input value" ("beijing"'s consonant standard input value becomes "144773 = bjng"), "first vowel + syllable standard initial value", "word standard initial value", etc. The system treats the input value as an abbreviated input value the moment the input value violates the language restriction.

The types of "short-cut input values" presented so far are summarized in the table of Figs. 11-11. In Fig. 11-11, the abbreviated input value (A) covers (B) to (L), which shows the types of abbreviated input values that the system can recognize according to certain rules, which have been presented so far. Some associated simple codes determined in relation to some arbitrary alphabets and short input values consisting of only some arbitrary alphabets are also included. It can be seen that the "total input value" (Z) becomes the full code of the full input method.

As previously suggested, if an input value violates the full code generation rule or does not form valid syllables in a specific language, etc., the input value is regarded as an abbreviated input value and processed. (In other words, the input value is regarded as not the full code of the promised full input method and processed) Since this is the core content of the parallel input method, even when a shortened input value not suggested in the present invention is used, the parallel input of the present invention is used. It is self-evident that it is included in the category of methods. Shortcut input values of (H) to (L) in the table of FIGS. 11-11 can be used not only in devices equipped with keypads but also in devices such as PCs, as shown in FIGS. 11-5 and 11-6. (B) of FIG. 11-6 shows an example in which "syllable reference initial value" is used as a shortened input value. The term simple code or short code was used as a general term for short input values, and the short input values of (H) to (L) can also be seen as simple codes in a comprehensive sense. That is, (I) "syllable reference initial value" in Figures 11-11 can be referred to as "syllable reference initial value simple code", and the shortened input values of (H) to (L) can also be named similarly .

In FIG. 10-*, if "14 = bz" is input as the syllable-based initial value, the system will search the index for phrases in which "bz" and the consonants of each syllable match. If "4" is entered here again, since "144 = bj", a phrase matching "bj" with the first consonant of each syllable (for example, "beijing") will be searched from the index.

The present invention goes one step further and shows that when any short-cut input value among the short-cut input values exemplified above is input, it can be interpreted as various types of short-cut input values. For example, for a certain shortened input value, it is primarily regarded as a predetermined shortened input value (eg, syllable reference initial value) and processed, and secondarily, other shortened input values (eg, consonant reference input value ), it is treated as another short-cut input value thirdly, and it is suggested that one short-cut input value can be interpreted as several types of short-cut input values. Based on Figure 10-*, when the short input value "144 = bj" is entered, the system primarily searches the index for a phrase (eg, "beijing") in which the first letter of each syllable matches "bj" and , regardless of whether the primary search result exists or not, it is possible to search for a secondary phrase whose consonant matches among the phrases in the index.

This shows that the system can interpret any short-cut input value presented in FIGS. 11-11 by the user. If this is applied, there can be multiple search results for one shortcut input value, and the output priority can be applied according to the type of shortcut input value to be applied. For example, the searched phrase(s) by interpreting as a syllable-based initial value is first interpreted as a consonant-based input value, and the searched phrase(s) is output next. If a user mainly uses the syllable-based initial value as an abbreviated input value, it would be desirable to set the phrase(s) interpreted by the syllable-based initial value to be output primarily. Therefore, it is desirable to allow the user to designate the priority according to the type of shortcut input value. In addition, if a user wants to use only the consonant standard initial value, it would be desirable to be able to set the abbreviated input value to be interpreted only as the consonant standard initial value. As already mentioned, the output priority of the phrases obtained by interpreting the same type of short input value can be determined by factors such as frequency of use. In addition, the output priority may be determined according to the frequency of use of each of the searched phrases regardless of the type of abbreviated input applied to the interpretation of the abbreviated input value.

In the case of "jinzhi (禁止) and zhuijian (逐ㅇ), the syllable-based initial values are "jz" and "zj", respectively, and both are "444". In this case, when the full-priority parallel input method is applied, the third input value is "4" The moment " is entered, the system can recognize that the input value does not form a pinyin syllable. Based on Fig. In other words, for the shortened input value "444", search for all phrases matching "zj" and phrases in which each syllable matches "jz".

Similarly, even when the abbreviated priority parallel input method is applied, the input value can be processed by considering it as the abbreviated input value of (B) to (L) in FIGS. 11-11. In addition, the input value is firstly treated as a syllable-based initial value, secondly treated as a syllable-based initial code, thirdly treated as a consonant-based initial value, and treated as other abbreviated input values in the same way below. It is possible. As soon as it is confirmed that the input value is processed as a shortened input value and no matching words exist in the index, the system treats the input value as a full code and processes it. It would be desirable to allow the user to specify in advance the type of commonly used shortcut input value.

“In the case of jinzhi (禁止) and zhuijian (逐ㅇ), in order to solve the problem of using the syllable-based initial value, the syllable-based initial value simple code and syllable-based initial code of the recommended sound can be done as follows. In Chinese, the recommended sounds “ch”, “sh”, and “zh” are in fact a single mother, and are expressed as one symbol as the main note, but are a combination of two alphabets when written in the English alphabet. Therefore, the syllable standard initial value simple code of zhuijian according to FIG. 10-6 can also be “4944” corresponding to “zh + j” including “h”. The syllable-based initial code will be “494” corresponding to “zh + j”. In the keypad of FIG. There is no ambiguity when both syllable standard initial value simple codes of “禁止)” and “zhuijian (逐ㅇ)” are set to “444”.

In the full-priority parallel input method using the syllable-based initial value simple code as a short input value, the input value “4~” is recognized as “z~”, and the input value “49~” is recognized as “zh~” and will be dealt with. However, since there are many words that start with “zh~”, even if the system processes the input value “49~” as “zh~” and outputs the corresponding phrase to the user, it will be meaningless. Therefore, for the input value “49”, the system can interpret it as a syllable-based initial value simple code and output a phrase whose syllable composition is “z__h__” (the underlined part means that the vowel is located). If “49” is interpreted only as “zh”, it becomes difficult to enter a word with a syllable-based initial value of “z__h__” in abbreviation. In the case of Chinese, since most of the words consist of one syllable (letter) or two syllables (letter), it is necessary to process the recommended consonant input as a shortened input for the shortened input of the two-syllable word. See Figures 10-17. In Fig. 10-17, [禁止] in the liquid crystal phase followed by [. . .] means that if there are many words of “z__h__”, other words in the lower order are output. Of course, the words “zh__” can be output in the lower order, and the word “zh__” can be set to be output first according to the user’s preference, but in general, it is better to output the word “z__h__” first. It will be convenient.

When a vowel input is recognized after “49” (for example, when the vowel button is pressed), the system processes the input value as “zh__” (ie, processes the input value as a full code). When a consonant input is recognized after “49” (for example, when the consonant button is pressed), the system processes the input value as “zh__X__” (capital ‘X’ is an English consonant representing an arbitrary Virgin). In other words, even in the full-priority parallel input method, inputs such as “ch”, “sh”, and “zh” of recommended sounds are primarily interpreted as simple codes (syllable-based initial value simple code or syllable-based initial code), and the next input Depending on whether the value is a vowel or a consonant, it is interpreted as a full code or a simple code.

The above is a similar result to applying the consonant standard initial value simple code as the shortened input value and applying the shortened priority parallel input method. However, the syllable-based initial value simple code is applied as the shortened input value, and the full-priority parallel input method is applied, but only at the beginning of the word (after the confirmation button is pressed or the word ends in the form promised in the input system) When a recommended sound is entered, the input value is regarded as a shortened input value and processed (in the example, the initial consonant of the word is “z__h__” (in the case of other recommended sounds such as 'ch' and 'sh', it is followed). ) will do.

Although the above has been described based on FIG. 10-*, it is obvious that the above concept can be applied to other keypads as well.

Furthermore, the same can be applied not only to the keyboard and keypad of the PC, but also to all types of similarly modified keyboards (the types of keyboards implemented on the screen can be very diverse).

16. simple code Parallel input method using possible alphabet combinations

Among the methods described above, when using a syllable-based initial code as a simple code, comparing with the first consonant of each syllable does not have a simple code index (eg 6242 / satongjipdan / 四通集團) on the client side, but only a specific It can be usefully applied even if you only have an index of phrases (eg satongjipdan / 四通集團). For example, “62… As soon as the second [2] in “” is entered, the system recognizes that the input value violates the Chinese language restriction, and the input value, “62… = sd... , st... , xd... , xt... (For convenience, it is called ‘possible alphabet combination’)” and the words in the index, the first consonant of each syllable can be searched for and provided to the user. As the number of button presses increases, the number of possible alphabet combinations increases, and the possible alphabet combinations are used to compare/search with phrases in the index. Reference may be made to Figs. 11-7. In the index of FIG. 11-7, “s t j p” and “s d .. ”, “x d .. ”, “x d … ”, “x t … ” (2**4 = 16 possible), and the input value “sd … ” could be compared with this multi-value in each record to provide the user with a 4-way map. This is also not recommended because the same concept or implementation is difficult and has no advantages. See Figures 11-9. In either method, it is the same as comparing possible alphabet combinations that can be expressed as input values and phrases in the index (Pinyin in Fig. 11-9).

Similarly, if the client does not have a simple code index (eg 7799, Samsung Electronics), but only has an index of a specific phrase (eg Samsung Electronics), the user has “Samsung Electronics” in mind, and “77… ”, the system recognizes that the input value violates the Korean language restriction the moment the second [7] is entered, and the input value “77…” is entered. = s s... , ss… , ss… , ㅆㅆ… (For convenience, it is called 'possible alphabet combination')” and the words in the index, the first consonant of each syllable can be searched for and provided to the user. Reference may be made to Figs. 11-8.

If it is confirmed that the phrase matching the input value no longer exists in the index, the input value can be regarded as a full code and provided to the user. Under the premise that the user inputs only the value of the syllable-based initial code, it is possible to produce an effect similar to the parallel input method without putting a simple code in the index, but only putting the index of words. However, this method is also the same until the system detects the moment when the input value violates the full code generation rule in the full-priority parallel input method or the input value violates the language restriction in the full-priority language-restricted parallel input method. , only the procedure of searching for the phrase corresponding to the input value is different. That is, at the moment when the full code generation rule is violated or the language restriction is violated, the system considers the input value as not a full code, but uses the fact that the input value is a syllable-based initial code without using a simple code. The phrase corresponding to is interpreted (or searched) and provided to the user.

The core content of the parallel input method is that the system automatically detects the moment when the full code generation rule is violated or the language restriction is violated, and the input value is regarded as a simple code (i.e., when the user inputs abbreviated input instead of full input). ), which was eventually modified by limiting only the part of searching for the phrase corresponding to the input value in the previously presented parallel input method to a special case (using a syllable-based initial code).

As in the case of syllable-based initial codes, if a simple code can be automatically extracted because it has regularity, such as all related simple codes, consonant related simple codes, first vowel + consonant related simple codes, " It is possible to search the target phrase from the index by comparing the phrase of the index against the "possible alphabet combinations". 10-11, the system interprets the input value as a full code whenever each input value is entered, and the moment it confirms that the Pinyin interpreted as a full code does not exist in the Pinyin index, the system considers the input value as an abbreviated input value. Thus, the target phrase can be searched by comparing the "possible alphabet combination" for the input value with Pinyin. 11-10 shows this as a drawing, which expresses a part ((2)-(B) part) of FIG.

17. full code in the input system that stores Full input method and parallel input method

It can be seen from the foregoing that there are cases in which it is a little complicated to identify the correct word for the input value by the specific language restriction full input method on a specific keypad. (Example: English input and Chinese Pinyin input by repetitive selection method on the standard English keypad) As described above in Chinese, if the system has an index of all words to be input not only in Chinese but also in other languages, the input value It is possible to interpret firstly as full code, and secondly to interpret it as promised simple code if it does not exist in the index.

Hereinafter, for convenience, the case of Chinese will be described as an example. As shown in FIGS. 10-14, if all full codes are stored in a system that stores all Chinese Pinyin (possible words in other languages), the system simply searches for phrases that match the input value and recognizes the target alphabet. can pay If the full-priority parallel input method is applied, the moment it confirms that the matching full code value no longer exists in the index, the system treats the input value as a simple code of the promised type and processes it. In FIGS. 10-14, the process of inputting "北京" can be seen as a process of interpreting and processing the input value as a full code. Since the full code is stored in the index, the full code is analyzed through the index search.

In the case of applying the full input method in which words can be identified without ambiguity by the language restricted input method, it is not useful to store the full code in the index. However, it can be useful if you apply an ambiguous full input method, such as the repeated selection method, and store all indexes of the phrase you want to input. As described above in “Language Restriction Input Method in Incomplete Consonant Separation Keypad”, if all words to be input are stored in the index when applying the full input method that can cause ambiguity (not only in Chinese but also in other languages) can be applied), and the input value can be processed using this full code index.

Although the above has been described with the example of Chinese, it is obvious that it can be applied to cases other than Chinese. In addition, it can be similarly applied to the keypad of FIG. 1-1 as well as the keypad of FIG. 10-* and other keypads.

18. input value At the same time Several type of as code (input) Parallel input method to process

A parallel input method that considers and processes input values as certain types of codes (input values) is possible. For example, in FIGS. 10-14, if the input value is treated as a full code (A) and a full associated simple code (B) at the same time, the system interprets the input value "1 * #" as a full code. "bei" can be recognized when interpreted as "bai" and the overall association simple code. In this case, the system can provide "bai" and "bei" to the user at the same time.

The difference is that in the case of the full-priority parallel input method, only "bei" is output when interpreted as a full code, and in the case of the short-priority parallel input method, only "ba i" is output, which is the result of interpreting the short code promised. Even in this parallel input method, as soon as it is confirmed that the input value no longer exists in a specific type of code, it is possible to treat the input value only as a different type of code, and eventually this is included in the category of the already mentioned parallel input method. will say yes The index of the system does not necessarily have to store full codes and all associated simple codes as shown in Figs.

19. Priority of words where ambiguity occurs

In any one specific input method (eg, a specific full input method or a specific type of short input method), when ambiguity occurs for the same input value, a specific input method is applied as shown in FIGS. 10-14 and other drawings. Target phrases may be output according to the order based on the order of priority when ambiguity occurs. For example, if ambiguity occurs when applying the full input method in FIGS. 10-14, the target phrase can be output and recommended to the user according to "(A) priority", which is the priority between full codes (A). have.

Next, a case where an input value is interpreted as various types of predetermined codes will be described. As illustrated above, in FIGS. 10-14, if the input value "1*#" is interpreted as a full code, it becomes "bai", and if it is interpreted as an overall associated simple code, it becomes "bei", which is interpreted as different types of codes. When ambiguity occurs, the system selects the target phrase according to the priority when simultaneously interpreting the full code ((A) in Fig. 10-14) and the entire associated simple code ((B) in Fig. 10-14). can be provided to the user.

For example, the input value is primarily treated as a full code, but it is confirmed that the full code generation rule is violated, the syllable generation rule of a specific language is violated, or the full code corresponding to the index no longer exists. At the moment, in the parallel input method that treats the input value as a syllable-based initial code and a syllable-based initial value simple code, when processing the input value as a short code, "syllable-based initial code" and "syllable-based initial value" When ambiguity between "value simple code" occurs, it can be processed based on the priority. (That is, if the syllable-based initial code is (C) and the syllable-based initial value simple code is (D), outputting the target phrase by "(C) + (D) priority")

Chinese was explained as an example, but it is obvious that the same can be applied to other languages if Pinyin is used as the target phrase rather than Chinese characters.

20. Control processing method full input method parallel input method

As shown in Figs. 2-1 and 2-2, when the control buttons are [*] and [#] buttons and a control processing method other than the representative alphabet is applied, the parallel input method is applied, but the word consisting only of the representative alphabet is applied to the index It was pointed out that if all are saved and the shortcut priority parallel input method is applied, the moment "*" or "#" is pressed as the input value, the system can process the input value as a full code.

In the case of Japanese in FIGS. 2-1 and 2-2, it is assumed that all short codes consist of only numeric values. In this case, put an index (which may be included in the short code index or configured separately from the short code index) that stores all words consisting of only representative alphabets, and apply the parallel input method, but use the number buttons as input values. While only is continuously pressed, the result of interpreting the input value as a full code and the result of interpreting the input value as a short code by referring to the index of words consisting only of representative alphabets (or the simple code index including it) are given a certain priority. As a result, it can be provided to the user as a target phrase.

For example, if the input value “111” is processed as a full code in FIGS. 2-1 and 2-2 (that is, if the full-priority parallel input method is applied), it is interpreted as “あああ”, if By referring to the index of all words consisting only of representative alphabets, if there is no word that starts with “ああ~” and only “あい” or “あい~” exists, “あい” or “あい~” is replaced with “ああ~” Priority can be provided to the user.

See Figs. 10-15 and 10-16. In Figures 10-15, the input value “11” is interpreted as a full code, but since this is a word made up of only representative alphabets, it is searched again for “index of all words made up of only representative alphabets” to check if it is a valid word. Here, if “ああ”, which interprets “11” as a full code, exists in the index, it can be recognized as a valid word for the input value. As soon as it is confirmed that there is no longer a phrase corresponding to the input value in the index of all words consisting only of representative alphabets, the system interprets the input value again as a simple code and recognizes the corresponding “あい”. 10-15, the system recognizes “あい” as the highest priority for the input value “11”. Depending on the input value after “11”, it can be “あい...” (“...” is when another alphabet is added after “あい”), so the system ranks it next to “あい”. can also be printed out. Likewise, even if it does not exist in the index, the target phrase may be “ああ”, so this may also be output as the next rank of “あい”. In FIGS. 10-15, “あい ...” and “ああ” are displayed in pale colors and in the second and third recommended order indicates that the system can output this way and only output “あい”.

*In Figures 10-15, (1), (2), and (3) may occur sequentially or simultaneously as mentioned in “Concurrent input method for recognizing input values as multiple types of codes at the same time.” have. Similarly, the indication of full code and simple code in the index is only for helping understanding, and it is self-evident that the same procedure can be performed even if the full code and simple code are not stored (the simple code is a syllable-based initial code or In the case of simple code that can be interpreted regularly, such as fully associative simple code). As shown in FIGS. 10-16, the case where the index of all words consisting only of representative alphabets and the index of simple codes exist as one index is the same. Implementation data structure can be realized in various forms.

The operation result of the system is similar to the parallel input method described above, but it can be seen as applying the full-priority parallel input method or general parallel input method rather than applying the short-priority parallel input method.

This can be equally applied to all parallel input methods that use the control processing method as the full input method as well as the parallel input method that uses the control processing method as the full input method, excluding representative alphabets.

21. Enter function

Among the functions, when entering a phrase (sentence), a space is an essential function, and a deletion (cancellation of input) function is also required. The enter function can be solved without input for a certain period of time after input, but it can also be said to be a necessary function. These three functions are collectively referred to as "three basic functions" for convenience. In addition, in languages where uppercase and lowercase letters exist, such as English, a case conversion function is also required. Among the up/down/left/right movement functions, the left/right movement function can be replaced with the delete and blank functions, and the up/down movement function is not an essential function.

Here, a few examples of various functions for inputting phrases in order of essential functions are as follows. Of course, this is just a reference, not an absolute standard, and may vary slightly depending on the specific situation. This is because if Chinese is input through the English keypad, the Chinese character conversion function will be the most essential function. In addition, the Chinese character conversion function can be an important function even in Chinese characters such as Japanese or Korean.

1. Space - Enter - Delete - Case conversion - Native language/number/English mode conversion - Move (up/down/left/right)

2. Space - Delete - Enter - Native language/number/English mode conversion - Uppercase/lowercase conversion - Move (up/down/left/right)

3. Space - Enter - Delete - Chinese character conversion - Native language/number/English conversion - Move (up/down/left/right)

4. Chinese character conversion - space - enter - delete - English/number mode conversion - move

17.1 Function input by control processing method

It has been explained that alphabets and various symbols can be selected by the control processing method. The same can also be applied to selecting various functions. 12-1 is an example showing that the meaning of various functions is given to number buttons and it can be implemented by combining them with “function control”. Numeric buttons associated with each button can be assigned in association with each other so that you can easily remember them. In FIG. 12-1, the left, right, up, and down arrows can be intuitively recognized, and putting the enter in the center is also to make it easy to know the number buttons and their related functions. The remaining necessary functions can also be easily memorized by associating them with buttons arranged with alphabets related to the names of functions for each language. In FIG. 12-1, the shift function is associated with the [7] button to which “S” is assigned.

In Figure 12-1, as in the case of the Korean language of the previous application for convenience, assuming that the aspirated consonant control and the consonant control are selected according to the number of pressing the [*] button, and then the function control is selected, enter = [5] + { function} = [5]+[*]+[*]+[*]. If the alphabet selected with one stroke of the [5] button is an alphabet that does not have aspirated / tense sounds, skip control processing can be applied and enter can be assumed when [5] + [*] is pressed.

Functions related to each button may or may not be displayed on the number buttons. However, it was pointed out that convenience of use can be added while maintaining a simple arrangement without displaying on the buttons by displaying the number buttons related to groups of various symbols on a part of the liquid crystal screen so that it can be easily recognized. The same can be applied here. See Figure 12-2. Also, as pointed out in the symbol input, the function associated with the function and number buttons can be redefined by the user.

As in the case of English, if the [*] or [#] button is not used as another control button, you can select “function control” with one stroke of the [*] button. You can enter a function by pressing the [*] button once.

17.2 Function input by multi-dimensional cross control processing method (using cross combination of control buttons)

The case where one control button is used to input one alphabet is called a one-dimensional control processing method. The same applies when the same control button is used repeatedly.

[*] and [#] are used as control buttons, and when alphabets and various symbols are input as a one-dimensional control processing method, the cross combination of control buttons (in this case, [*]+[#], [#]+[ *]) to input various functions. If the control button is not used repeatedly, the function can be entered using [*]+[*] or [#]+[#]. Since “[*]+[#]” looks like it goes from left to right, users can easily recognize it when using it as a right movement function (or a space). Conversely, [#]+[*] can be easily recognized by the user when used as a left-to-right movement function (or deletion).

This can be understood from the perspective of the multidimensional intersection control processing method. In the case of inputting ^a = a + [*] by applying post-control input as an input example, if the user inputs “a + [*] +[#]”, the system returns up to a + [*] ^a is recognized as input, but since [#] cannot come next (even if the [#] button is used as another control button), the moment [#] is entered, the system responds with “[*] +[ #]” can be recognized as inputting the right movement function. It can be seen that the case where it is specified as a control line input is similar.

In the case of Japanese, a two-dimensional control processing method was applied. In this case, the function can be implemented by alternately combining the control buttons 3 times (or more). For example, blank = [*]+[#]+[*], delete = [#]+[*]+[#]. In the example of the space function, the shape formed when pressing [*]+[#]+[*] reminds us of the arrowhead of the right arrow, so we can easily remember this. Similarly, in the case of delete, when you press [#]+[*]+[#], you can remind yourself of the arrowhead of the left arrow, so you can remember it easily. The reason this is possible is the same as described above.

Summarizing this, it can be seen that various functions can be input by changing the control buttons twice in case of applying the one-dimensional control processing method, and combining the control buttons three times in case of applying the two-dimensional control processing method. have. That is, when the N-dimensional control processing method is applied to input alphabets and various symbols, various functions can be input by alternately combining control buttons N+1 times.

22. Kanji Conversion

Korean and Chinese Chinese Pinyin and Chinese characters have a correspondence relationship of 1:Many. For example, the Chinese characters corresponding to “courtesy” are 禮意, 禮儀, 銳意… There will be many like

In the case of Chinese, Chinese characters corresponding to “beijing” also have Beijing, 背景, etc. (unless a tonal code is added). Therefore, by repeatedly pressing the Chinese character conversion button, the next Chinese character (eg, 北京 (2nd), 背景 (3rd)) can be selected. For example, if you press the Chinese character conversion function once after entering beijing for example, it becomes Beijing, and if you press it once more, it becomes 背景. Or you can choose from a list.

In the case of Chinese, in order to input Chinese characters, all Chinese characters (called “target Chinese characters” for convenience) must be stored in the index. can be provided to For example, “beij… If the only word that starts with ” is “北京”, when the user inputs up to “beij”, “北京” can be provided to the user. If there is only one "beijing(北京)" in the pinyin index, even if the user does not confirm the target Chinese character in the middle of input, the system converts "beijing" to "北京" as soon as "beijing" is recognized as definitive. that can be printed out.

And in the case of Japanese, hiragana and katakana have a 1:1 correspondence relationship, and hiragana or katakana and Chinese characters have a 1:many relationship. Therefore, it has been explained that it is possible to convert to katakana by inputting a katakana conversion control (eg, “a / a” control in FIG. 2-1) after inputting hiragana. If the modified alphabet is entered by the cross control processing method in FIG. 2-1, the “A/A” control can be selected with two strokes of the [0] button. Here again, Chinese characters corresponding to a specific hiragana or katakana can be selected by repeatedly pressing the [0] button. For example, if you set the “A/A” control to post-input, if you press [0]+[0] after entering a hiragana word (or alphabet), it will be converted to the katakana corresponding to the entered hiragana, and then [0 If you press the ] button, the first Chinese character is converted, and if you press the [0] button once again, the next Chinese character is converted. Conversely, in the katakana input mode, pressing [0]+[0] after inputting katakana converts it to the corresponding hiragana, and pressing the [0] button once again converts it to kanji.

23. simple code Building an index

Among the simple codes presented by the applicant, all related simple codes, syllable-based initial codes, consonant-related simple codes, first vowel + consonant-related simple codes, and word-based initial codes are mechanically (ie, automatically) specific phrases (words or phrases). ) has a good property of extracting a simple code from it. Therefore, a simple code index (an index made up of simple codes and simple code corresponding phrases) is automatically constructed for a word once input by the user using the full input method, and can be used in the parallel input method. The simple code may be stored on the client side or the server side in an environment similar to FIG. 5-5, or may be stored on both the client side and the server side.

For the same phrase, different types of simple codes (eg, fully associated simple codes and syllable-based initial codes) can be generated. However, in general, it will be convenient to use a specific type of simple code, and the user only needs to be aware of the type of automatically generated simple code, which can be used when applying the parallel input method. If this is applied, there is an effect that the simple code index becomes richer as the user inputs more characters.

In order to extract a syllable-based initial code from a specific phrase in a specific language, syllables must be separated from a specific word. Separating syllables from a specific word in a specific language is possible according to the rules of division (syllable separation) of a specific language. Since each language has a splitting rule, it is not difficult to automatically separate syllables from a specific word using this, and it is not discussed in detail here.

For example, in the case of "Zhongguo" in Chinese Pinyin, the syllables can be separated into "Zhong" and "guo" centering on the vowels "o" and "uo", which is faster than the process of recognizing Pinyin in the present invention. It can be done much more easily. In an example of separating syllables by forward scanning from the front of a word, it is not known whether the consonant "n" after "zho" is the consonant of the next syllable, but it can be seen that the consonant "g" belongs to the first syllable. Similarly, "g" may be a consonant of the next syllable, but looking at the next "g", the first "g" is a consonant belonging to the first syllable, and the second "g" is a consonant constituting the next syllable. . (Any syllable in Pinyin can end in "~ng") The first syllable "zhong" can be isolated by scanning up to "zhongg". Next, the system may recognize that "u" is a vowel constituting the second syllable, and the consecutive vowel "o" is also a vowel constituting the second syllable. (In Pinyin, the English vowel "uo" can appear consecutively) Since there are no more letters after "o", the system can separate the syllables of "zhongguo" into "zhong" and "guo", so the sound It can recognize that the initial value of the clause is "zg", and it can be identified that the syllable-based initial code of "zhongguo" is "43" (based on drawing 10-6). Of course, in the case of other languages, syllables can be automatically separated from a specific word or phrase according to the syllable separation rules of the language.

24. From phrases without special code (subscript) target phrase Translate

In the case of beijing, it is said that it corresponds to both “北京” or “背景” if no tonal sign is attached to the vowel, and in this case, you can select a target phrase by repeatedly pressing a specific button, or select one of the two from the list. said there is

Similarly, in languages other than Chinese, if a tonal sign is not attached or if only a basic vowel is entered even though a subscripted vowel must be entered, the index is searched in response to repeated pressing of a specific button to provide the user with a target phrase or to search the index Therefore, a list of corresponding phrases including subscripted vowels can be provided to the user so that the user can select it.

This will be useful in languages such as Vietnamese, which have a large number of modified alphabets and complex tonal codes. However, the system must have an index of phrases formed by adding subscripts to the basic alphabet. Likewise, building such an index can also be built from words already entered by the user. For example, when a user enters the word “^+abc” (when a subscript '^' is attached to 'a') through character input, the system stores "^+abc" in the system (the system saves It is okay to store “^+abc” corresponding to “abc” and “abc”), and if the user presses a specific button after inputting “abc”, “^+abc” is provided to the user or the user presses “abc” When inputting , a list of phrases corresponding to “abc” can be provided to the user, such as “^+abc”. If “abc” is the target phrase, the user will choose “abc” even if he does not press a specific button or the system provides a list of related phrases. The point at which the list is provided can be the point at which input of words ends, or it can be any point in the middle of input.

25. Part of a phrase (word or phrase) full input method Parallel Input

The technique of outputting the words matching the input contents from the index according to the word input (full code input) and allowing the user to select it has been widely used. For example, think of the “autocomplete feature” of Windows. Even during full input (entry by full code), it refers to the index (eg index for parallel input) and outputs matching phrases among the phrases (words or phrases) stored in the index and allows the user to select/confirm. Of course you can.

This will be described based on the input systems of FIGS. 4-5 to 4-8. For example, assume that the index stores words such as “thank you” and “thank you”. If up to “10* = high” is entered, the system will match words with “go…” (i.e. words starting with “go”, such as “thank you”, “thank you”, . . . ) in the appropriate form. can be printed out. In a mobile phone-like environment, the content generated by the input value is displayed on the input line (top of the liquid crystal in Fig. 13-1), and the candidate phrases (words or phrases) output by referring to the index are listed at the bottom or can be output in the form The user can select a desired word using a movement button (navigation button), etc., and then confirm and input the word. Take a mobile phone liquid crystal as an example and refer to FIG. 13-1. 13-1 is an example of outputting a word matching a syllable formed according to full input at the bottom of the liquid crystal.

When entering “thank you” here, after entering “go”, the remaining syllables can also be entered as abbreviated input (in the example, a shortened input using a syllable-based initial value simple code). In other words, “Go + ㅁㅅㄴㄹ = 10 * + 5723” is entered. Here, the user may be provided with a word in which the first syllable is “go” and the rest of the syllables have initial values corresponding to “ㅁㅅㄴㅅ” (that is, “thank you”).

However, about half of Korean syllables are syllables with a final consonant (support), and the other half are syllables without a final consonant. In the case of “Thank you”, if “1*05723” is entered continuously, it becomes “bear”. Recognizing that part of the value does not form a normal Korean syllable, the part that does not form the rest of the syllable (eg “ㅅㄴㅅ = 723”) can be treated as a shortened input. This also belongs to the category of “parallel input method (full (input) priority parallel input method)” mentioned in the earlier application, and the syllables recognized by full input (eg “bear”) are of course interpreted as full code, and the rest The input value (eg “ㅅㄴㅇ = 723”) is interpreted as a simple code.

Here, it is possible to find and provide matching words in the index (eg, when “bear” is stored in the index), including pre-formed syllables by full input, or to provide You can either provide a word (eg, if “yes” is stored in the index), or print both cases. When outputting both, a specific word is given according to a predetermined promise (e.g., priority is given to words containing parts interpreted as full code, or conversely, or according to the priority of words, or priority is given to specific groups of words) can be output at the top. Since various means are possible, it would be desirable to allow the user to set this output order.

In case of outputting both, in response to “bears”, when “bears” and “bears” are output at the bottom of the screen, if the user selects “bears”, the entire “bears” is displayed as “bears”. It will be replaced with “Yes”, and if “Yes” is selected, it is natural that the corresponding “ㅅㄴㅅ” will be replaced with “Yes” and become “It is bear”.

Here, if only “Thank you” is stored in the index, “Thank you” cannot be output in response to continuous input of the input value “1*05723”. Therefore, the system can additionally interpret “1*05723” as “bear” and “go” and refer to the index to output matching words (provided to the user). Interpreting “bear” as “go You can put it between “go” and “ㅅ” as a single consonant. It looks a bit complicated, but those who have basic knowledge about Hangul processing can easily understand it. When a double consonant is used as a final consonant, it can be similarly applied. 13-2 shows the priority of output as “word(s) of a specific group specified as priority output - word(s) including a part interpreted as full code - word(s) not including a part interpreted as full code ( field) - . . .” An example of outputting candidate words by applying the order of is shown. Here, “yes” is output first, and it belongs to the designated group and is output at the top.

If the user wants to be interpreted only as “GoㅁㅅㄴDD”, the promised operation that can give syllable confirmation after inputting up to “10* = Go” (e.g., no input for the promised period of time, or pressing the right arrow [>] button once) Etc.) and then pressing “5723”, it can be interpreted only as “Goㅁㅅㄴㄱ” and only the corresponding word can be searched. In this case, it is also possible to output a word corresponding to “goㅁㅅㄴㄴ (eg, “thank you”) including the already recognized syllable “go”, or to output a single word corresponding to “ㅁㅅㄴㅅ” except for “go”. (eg, if “yes” is stored in the index), or both. See Figure 13-3.

Here, pressing the right arrow button (hereinafter referred to as “[>] button”) as an operation button for intentional syllable confirmation can act as syllable confirmation. In addition, the [>] button can also be used as a blank button, and after the syllable is confirmed, it can act as a blank input. In other words, if the [>] button is pressed once after entering “high”, the syllable “high” is confirmed, and if the [>] button is pressed once more, it becomes “high” (‘high’ + blank). That is, if “10*>5723” is input, the system can interpret it as “Goㅁㅅㄴㄴ” and provide the corresponding word “Thank you” to the user. Of course, if the system refers to the example index, it is obvious that the system can output “thank you” even if only “10*>57 = goㅁㅅ” is entered.

In this parallel input method, processing including syllables formed by full input will be useful when a target word is determined from a list of candidate words when matching candidate words are provided in the middle of full input. In addition, in the case of outputting candidate words corresponding only to input values processed by abbreviated input (i.e., input values interpreted as simple codes) excluding pre-formed syllables, frequently used suffixes or word investigations are quickly entered as abbreviated input. It will be useful. For example, after inputting “thank you” (confirm the input contents with a predetermined method), enter “yes (assuming that it is stored in the index)” with “ㅅㄴㅅ”. In this way, frequently used suffixes such as “...” can be placed in a separate group (eg, suffix group) in the index, and the words of that group can be output preferentially when outputting candidate words in parallel input. If “thank you” and “thank you” are stored in the index, both “thank you” and “yes” may be output in the candidate word list.

For one more example, when inputting “Sejong = 70##90*838”, up to “Sejong” can be processed as a full input, and “38” that does not form an appropriate syllable can be processed as a shortened input value. Likewise, if there is only “King Sejong the Great” in the index, “King Sejong the Great” will be output. Conversely, if there is only “Great” in the index, only “Great” will be output. If both “King Sejong” and “The Great” are present, both may be output, but it would be desirable to output only one (including/excluding the part processed as full input) by promise. Also, in the case of “The Great King Munmu”, if you input “ㄴㅇ” continuously after inputting “Munmu” as a full input, it will become “Munmu-ㅇ”. Therefore, if you want to enter “Munmu” as a full input and enter only “Daewang” as a shortened input, enter “Munmu” and confirm the entered syllable “Munmu” (e.g. the right arrow [>] button to end the syllable) After confirming by pressing once), you can enter “38 = ㅇ”. Here, even if “Great King” has a lower priority than other words in the index corresponding to “ㄴㅇ = 38” (eg “Dawa”), if “Munmu the Great” is stored in the index, the input value is “5*025*0”. For “>38”, “The Great” can be output prior to other candidate words (eg “Dawa”).

Furthermore, even if some syllables are input by full input after inputting by short input, such as “ㄱㅁㅇㄴㅇ = 157*623”, it is possible to process it as “thank you” corresponding to it. If up to “157 = ㄱㅁㅅ” is entered, the system interprets the simple code (syllable-based initial value simple code or syllable-based initial code in the example) “157” and searches for words in which each syllable corresponds to “ㄱㅁㅅ”. If “*6” is input again, the system can recognize that the syllable “7*6 = wet” is formed with “157*6 = ㄴㅇ”. That is, if the system recognizes that the previously input “15” is a shortened input value, and “23” is input again, it can be processed as a shortened input value because an appropriate syllable is not formed. Also in this case, the system can interpret some of the syllables in “ㄱㅁㅇㄴㄴ” as a full code, and interpret some syllables as a short code, and provide a corresponding “thank you” to the user.

In the case of Chinese, it is said that one syllable consists of “Virgin Mother + Mica”. When displaying Chinese pinyin, “Sungmo” is a consonant of the Roman alphabet, and “mica” is a vowel of the Roman alphabet, “vowel + n” or “vowel + ng”. In other words, it can be seen that one Chinese character (one syllable) represented by Pinyin is composed of “consonant + vowel” or “consonant + vowel + n” or “consonant + vowel + ng” of the Roman alphabet. Rarely, there may be syllables beginning with the vowels “a”, “e”, or “o”. Here, it has already been pointed out that only “n” or “ng” is possible for the Roman alphabet consonant that can come at the end of a pinyin syllable. This can be regarded as a final consonant in Korean. Only “n” or “ng” can be used as a final consonant (the final consonant of a syllable).

For example, “中華(zhonghua)”, “民國(minguo)”, “中華民國 (zhonghuaminguo)”, . . . Assuming that such words are stored, enter Pinyin by full input until “中華 (zhonghua = 49***7739##*, based on Figure 10-6)”, and enter only “民國 (minguo)” as abbreviation An example of inputting “mg = 73 (based on FIG. 10-6)” as (in the example, a short input using a syllable-based initial value simple code as a short input value). In the input of “中華”, after inputting the corresponding Pinyin (“zhonghua = 49***7739##*”), the process of selecting and confirming the selection among the listed candidates is mediated, and then “mg = 73” can be entered, or Pinyin After inputting “zhonghua = 49***7739##*”, “mg = 73” may be input continuously. In the former case, “Minguk (minguo)”, 民歌 (minge), . . . It is natural to output only words such as etc. as candidate words. In the case of the latter, it is better to interpret the input value “49***7739##*” as “China” and output “People’s Republic of China” together with “People’s Country” corresponding to “73” recognized as a shorthand input value. It is also obvious. Regarding the input value “49***7739##*73 = zhonghua + mg”, for inputs up to “49***7739##*7”, the last “7” is a pinyin voice input, which is a normal full input , the system recognizes it, but the moment the last “3” is input, the system recognizes that the last two input values “73” are short input values. This is the same as the case of Korean as described above. Therefore, for the input value “49***7739##*73”, the system selects “China” corresponding to the full input value “49***7739##*” and “People’s Republic” corresponding to the shortened input value “73”. “People’s Republic of China,” which is a word made up of “.” See Figures 13-4.

Conversely, after entering “zh = 49” by abbreviated input, “7#773##***” is entered without selecting “China” among the candidate words and inputting “People’s Republic” in full. Even when inputted (i.e., “497#773##*** = zhminguo”), “People’s Republic of China” corresponding to “z__h__minguo” can be output. Similarly, when inputting “73##***” for the input of “民國 (minguo)”, it can be interpreted as “73##*** = mguo = m__guo” and output “民國”. The moment “73” is pressed, the system regards it as a shortened input and searches for and processes the word corresponding to “m__g__”, but processes the following “##*** = uo” as a vowel that forms the second syllable. . Entering “uo” after “mg” serves to compress “Minguk” among the candidate words corresponding to “m__g__”.

After entering the Chinese character “Chinese” by other means (shortened input, full input, input using strokes, etc.), and then inputting “Minguk” as “73” by shortened input, simply input value If “73” is interpreted as a simple code and a word corresponding to “m__g__” is provided to the user, a number of candidate words (eg “民國(minguo)”, 民歌 (minge), . . .) will be output in the form However, if "People's Republic of China" is stored, it is possible to interpret "People's Republic of China" as "People's Republic of China", apart from the fact that "People's Republic of China" is stored in the index. In this case, “中華” has already been entered as a Chinese character, so in response to the input value “mg = 73”, “People’s Country” is output prior to other candidate words (eg “民歌(minge)”, . . .) can do.

When “zhong...” is entered here, the system may interpret it as “zho” + “n__g__” or “zhon” + “g__”. However, in fact, since there is no syllable consisting of “zho” or “zhon” in Chinese Pinyin (ie, of course, it is not even in the Pinyin index), “zhong...” is interpreted as “中” by referring to the index. If it exists, it can be output as a candidate word according to a predetermined output order when “zhong” is input. Based on Figure 10-6, for the input of “zhongg... = 49***7733”, it may be interpreted as “zhonk..” = “zho” + “n__k__” or “zhon” + “k__”. There will be. This is in a similar context to the parallel input method that interprets the input value as a full code and a shortened input value (simple code) at the same time as previously presented.

In the above example, a case of using “syllable-based initial value simple code” for convenience as a shortened input value (simple code) was presented, but when “syllable-based initial code” is applied as a shortened input value, in simple code interpretation, Fig. 11- 3 ~ The contents mentioned in FIGS. 11-10 can be applied.

26. Character input method using long press and long press Control processing method used

In general, “Alphabet, etc.” encompasses one object (e.g. alphabet, number, English alphabet, symbols (special characters), functions, and controls for various purposes) with one button press. ) can be expressed. Here, while pressing a specific button once, it is possible to express an object different from the object expressed simply by pressing a specific button once using “long press”. Hereinafter, pressing and holding a specific button will be referred to as “long press” or “long hit”. Hereinafter, what is not expressed as “long press” means a normal button press, and is referred to as “short press” when it is explained in contrast to a particularly long press. In the following, the general contents are explained in the case of English, and the application examples are given for each language, but it is obvious that the contents described in one language can be equally applied to other languages.

26.1 English (and common)

26.1.1 Alphabet input using long press

Currently, it is used to input a corresponding number by long pressing a specific number button. However, it is not always possible to input only numbers. For example, pressing each number button once in FIG. Assuming that it is input), it can be done by inputting the second alphabet (eg “B”) by long pressing. However, long pressing is a factor that breaks the natural flow of input, so it is not desirable to apply it to frequently entered alphabetic input. Therefore, it is preferable to apply input by long pressing (long hit) to input an object that is not frequently used. In addition, it would be desirable to allow the user to set the time that is recognized as a long press as long as possible according to each user's skill level.

In the present invention, a long press is appropriately used, but through this, it is shown that the input rules of a specific input method can be simplified, the expression range can be expanded, and furthermore, ambiguity can be removed. Here, for convenience, the long press of the [2] button is expressed as “2~” by attaching a tilde (~) after “2”. As mentioned, when the existing repetitive selection method is applied, when the [2] button is pressed three times in FIG. 1-1, it is possible to know whether “222” is “C”, “AAA”, “AB” or “BA”. ambiguity arises.

1-1, “A” presses the [2] button for a long time or presses the button once, “B” presses the button once after inputting “A”, and “C” presses the corresponding button once after inputting “B” (or It is the same as pressing 2 times after entering “A”). If the alphabet on the same button is input continuously, in the second and subsequent alphabet inputs, if you start with a long press, you can also input without ambiguity. For example, when inputting “DACB”, you can input “3 2 2~22 2~2” without ambiguity, and “ACB ” on the same button appears continuously, but when you input “C” or “B”, long press By being mediated, it is possible to identify without ambiguity. This case can be entered with a feeling almost similar to the existing repetitive selection method, and only when the alphabets assigned to the same button are entered consecutively, there is an effect of removing ambiguity by using a long press. Of course, in the case of “DACB = 322~222~2”, it is also possible to use a long press of the [2] button (ie, “2~”) for the “A” input.

In the case above, an arbitrary alphabet (eg “A”) among the alphabets assigned to a specific button (including both explicit and implicit assignments) is set as the representative alphabet, and the rest of the alphabets are the successor alphabets (eg “B”). , “C”), it can be seen that the subsequent alphabet is input by pressing the button assigned to the representative alphabet and the subsequent alphabet a predetermined number of times. In other words, “A (Representative Alphabet) - B (2nd Subsequent Alphabet) - C (3rd Subsequent Alphabet)” relationship, “A = 2~”, “B = A + 2 = “2~2”, “C = B + 2 = A + 2 + 2 = 2 to 22”. In addition, the fact that “A” can be input with a normal press (i.e., a single hit) rather than a long press means that, unless the alphabet assigned to the same button is input continuously, the existing repetition in the input of the representative alphabet This is because it is possible to input with a normal single press (ie, single stroke) as in the selection method. Hereinafter, for convenience, this is referred to as “repeated selection method by pressing and holding the representative alphabet”.

If you input only two alphabets using one button, you can define one alphabet as a regular single press (ie, single hit) and the other alphabet as a long press (ie, long hit). (Ex. “B = 1”, “P = 1~” in Fig. 10-1) However, as shown in Fig. 1-1, three alphabets are assigned to each button (explicitly assigned or implicitly assigned). (eg [2] button), define the first alphabet as one press (eg “A = 2”, define the second alphabet as a long press (eg “B = 2~”, 3rd alphabet) If you press twice (eg “C = 22”) or long press and press once (eg “C = 2~2”), there will also be ambiguity when entering the third alphabet. “C = 22” This is because it can be interpreted as “AA” when defined as “C = 2~2”, and can also be interpreted as “BA” when defined as “C = 2 ~ 2.” In this case, the first, second, and third alphabets are arbitrarily defined. In this case, the number of times that ambiguity can occur is significantly reduced compared to the normal simple iterative selection method.

The advantage of the repeated selection method using a long press is that it can be input without ambiguity, and it can be more useful when entering not only the alphabet assigned to each button, but also numbers and symbols related to each button. For example, certain alphabet(s) “A1, A2, A3, ...” are associated (explicitly assigned or implicitly assigned) to a certain “button x”, and a certain number “N1” Assume that it is related, and that the specific symbol(s) “S1, S2, S3, ...” are related. Here, it can be defined as inputting an arbitrary alphabet related to “button x” by long pressing. For example, designate the alphabet “A1” as the representative alphabet and input by long pressing “button x”. If inputting “A1, A2, A3, N1, S1, S2, S3” related to “button x” is shown in the form of a graph, it is shown in FIG. 14-3. 14-3, it can be seen that “A1S1 = xx~xxxx” or “A1S1 = x~x~xxxx” is input. Here, if English is not the native language, the English alphabet "E1, E2, E3, ..." may be additionally associated and input.

Furthermore, in inputting objects related to “button x” (eg, “A1, A2, A3, N1, S1, S2, S3”), it is not the repeated selection method by pressing and holding the representative alphabet, but the normal repeated selection By applying the method, it is also possible to input related numbers and various symbols (special characters). However, since ambiguity occurs when objects related to the same button are entered consecutively, after entering one object, “delay of a certain time promised” or separator (e.g., in “Complements in the parallel input method”) It is necessary to prevent ambiguity from occurring by the input of the explained [>] button once). For example, if “A1, A2, A3, N1, S1, S2, S3” are related to “button x” and “S1A1” is entered by the repeated selection method, “S1A1 = xxxxx>x” is entered. It can be. This is a technique used to overcome ambiguity in applying the repeated selection method, but the difference is that it allows input in association with a specific number and symbol group to a specific button.

Currently, if there is a native language alphabet “A1, A2, A3” associated (assigned) to “button x”, “x =A”, “xx = B”, “xxx = C”, or a defined maximum repetition When pressed exceeding the number of presses (eg, “button x” was pressed 4 times), it cycled toggling like “xxxx = A” and “xxxxx = B”. The circular toggle seems to be a consideration to input the target alphabet again by repeatedly pressing the button that was pressed when an input error occurred when the repeated selection method was applied. However, as suggested by the applicant, if the input of the delete button acts as the deletion of the “recent input value” rather than the deletion of the entire alphabet being created, it is not necessary to apply the circular toggle method. You only need to press “xx = B”, but if you enter “xxx = C”, you can enter “B” by pressing the delete button once, even if you do not enter “B” by additionally pressing “xx” .

14-4 shows the process of inputting alphabets by pressing a specific button for a long time after a short press. In Fig. 14-4, lines A1, A2, A3, ... are the input process by the existing repetitive selection method. B2 can be seen that A1 is input by a short press of a certain button (eg, button “x”), and then a long press of the same button is combined and input. That is, “A1 = x”, “B2 = xx~”. Here, if an alphabetic input is not defined only by a long press of button x, and assuming that only alphabets A1 and B2 are input using button x, it can be recognized without ambiguity. Even if the long press of button x is defined as a certain alphabet (eg alphabet E1), if “A1” and “E1” do not appear at the same time, this language restriction (language restriction that A1 and E2 do not appear at the same time) is overcome. can be used to enter A1, B2, E1 without ambiguity.

Also in FIG. 14-4, if the long press of “button x” is not defined as any alphabetic input, A1, B2, and C3 can be recognized without ambiguity. In addition, in the case of A1, A2, and D3, there may be ambiguity as “A1 = x” and “A2 = xx = A1A1”, but if A1 does not appear consecutively in a language, these language restrictions (A1 does not appear consecutively) language restrictions), A1, A2, and D3 can be entered without ambiguity. The same method as in FIG. 14-4 is called “repeated selection method by long press after short press” for convenience. For example, in Figure 10-6, “i = #”, “u=#~” is determined, and “##~” is an arbitrary vowel (eg, “ ^.. u” - “u” with a subscript “ ..”) can be entered without ambiguity (in Chinese Pinyin, “i” and “u” do not occur consecutively). Of course, since “i” does not appear consecutively, it is also possible to enter any other object with “##”. The same can be applied to other languages as well. In FIG. 14-4, it can be used to input the lower order alphabets (eg S1, S2, S3, ...) of rows A1, A2, and A3.

26.1.2 Control processing method using long press

Next, an example of application to control selection is shown. In the following case, it is assumed that the control is input later. In the previous example, the [2] button expresses “A” for both short and long hits, just to give an example that can be input with a feeling similar to the existing repetitive selection method. However, a specific object can be expressed by pressing a specific button once, and another object can be expressed by long-pressing the same button. For example, one press of a specific button (eg [1] button) triggers a specific target (eg, a random “alphabet x” - where “x” means a random alphabet, not the actual “x”). can be expressed, and a long press can express another specific object (eg, arbitrary “alphabet y”). That is, “alphabet x = 1”, “alphabet y = 1~”. Some of the “alphabet x” and “alphabet y” examples here are conceptual, so even if they were defined as “A = 2~” or “A = 2” in the “repetitive selection method by pressing and holding the representative alphabet for a long time” “A” by normal pressing (ie single hit) corresponds to the alphabet x, and “A” by long pressing corresponds to the “alphabet y”.

The same can be applied to the selection of controls. For example, a single press of an arbitrary button (eg [*] as a control button) can express a specific object (eg, an arbitrary “control a1”), and a long press of the same button can express another specific target (eg, an arbitrary “control a1”). Yes, you can express any “control b1”). It is said that “a2 control”, “a3 control”, etc. can be selected by repeatedly pressing the control button. The important thing here is that after selecting “b1 control” by pressing and holding the control button, “b2 control”, “b3 control”, “b4 control”, etc. can be selected by repeatedly pressing rather than long pressing. will be. Again, ambiguity does not occur. This can refer to the case in which only the representative alphabet “A” is input by long pressing in the previous example, and single strokes are combined in the selection of the remaining subsequent alphabets.

For convenience, if the object entered by the combination of a specific button (eg [1] button) and “b1 control” is displayed as “B1”, it becomes as follows.

“A1 = x + {a1control} = 1*”, “A2 = x + {a2control} = 1**”, “A3 = x + {a3control} = 1***”, . . . ,

“B1 = x + {b1control} = 1*~”, “B2 = x + {b2control} = 1*~*”, “B3 = x + {b3control} = 1*~**”, . . .

Of course, it is also possible to apply 1 long hit, 2 long hits, and 3 long hits to the selection of the b1, b2, and b3 controls, respectively. However, it is a very obvious fact that it is not good to use long press frequently. As in the case of B1, B2, B3, ..., inputting by normal pressing after long pressing the control button once is called "repeated pressing after long pressing" for convenience. Control processing method by repeated pressing”. The A1, A2, ... series mean the previously presented control processing method, and the B1, B2, ... series mean "the control processing method by long pressing and then repeatedly pressing". The above contents are shown in a graph form as shown in FIG. 14-1. The above is an extended case by applying one long press only to the first control selection, as in the repeated selection method by pressing and holding the representative alphabet. In addition, as shown in Fig. 14-2, various extensions (eg, C series, D series) are possible by mediating an additional long press.

Of course, if a long press of a button other than a control button (eg, [1] button) is applied (eg, “alphabet y”), another target can be expressed. Furthermore, the alphabet displayed on each keypad button (eg, “A = 2 ~”, “B = 2 ~ 2”, “C = 2 ~ 22”) using a long press Since it is said that it is possible to identify three alphabets) without ambiguity, after selecting three alphabets that can be selected by operating the number buttons, by repeatedly pressing the control button or long pressing and then repeatedly pressing, different groups of modified alphabets can be input. will be. That is, after inputting “A” in FIG. 1-1, by repeatedly pressing the control button, it is possible to input the alphabet (meaning encompassing symbols, numbers, native language, English alphabet, etc.) of a specific group (eg group 1), You can input the alphabet of another specific group (eg group 2) by “long press and then repeat press”. Similarly, the alphabet of group 3 can be input by the combination of “B” input and repeated pressing of the control button, and the alphabet of another group, group 4, can be input by pressing and holding and then pressing repeatedly. In addition to the three alphabets displayed on the keypad buttons in Figure 1-1, a random rule (eg “2 to 222”) is set, and for this, an arbitrary group is selected by repeatedly pressing and holding the control button and then pressing repeatedly. It is also possible to input the alphabet.

The control processing method by pressing and holding for a long time is the same as in the case of Korean (Fig. 4-5 ~ Fig. 4-8) and Japanese (Fig. 2-1, 2-2), etc. If it takes input, it will be very useful for inputting intermittently used numbers in sentences and inputting English alphabets (in a language other than English). Below, application examples for each language are briefly mentioned, and may be applied to other languages that are not mentioned.

26.2 Korean

In the case of Figs. 4-5 to 4-8, the modified alphabet (eg lattice/hard consonant and dropped consonant) is input by repeatedly pressing the button to which the basic consonant belongs (eg “a=1”, “ㄲ= 11”, “ㅋ = 111” or “ㄱ = 1”, “ㅋ = 11”, “ㄲ = 111”). That is, when alphabets belonging to the same button appear consecutively, when inputting the second and subsequent alphabets, press and hold to input. For example, if continuous pressing of the [1] button is defined as “ㅋ” in FIGS. 4-5, when “a” appears consecutively, it can be recognized as “ㅋ” rather than “a + a”. When inputting “a”, if you press and hold it, it can be recognized as “a + a”. In other words, long press is used when inputting “a” of the second syllable in “country”. Even when inputting “Kukka,” input “ㅋ = 1~1” by long pressing the “ㅋ” input of the second syllable. This can be selectively applied (only one of the two, or both at the same time) to inputting the modified alphabet by the control processing method.

As an example of inputting some alphabets other than representative alphabets by long pressing, you can input by long pressing either a lattice sound or a light consonant. For example, if it is defined as input by pressing and holding the lattice sound, hard consonants (twin consonants) can be input as a combination of basic consonants. Of course, as mentioned in the previous application, in the case of “Ottogi,” there is ambiguity in “Oddugi” (“c” is the consonant of “O”).

Similarly, a long press can be applied to the input of a consonant assigned with a vowel (eg, “ㅎ” assigned to the [0] button in Figs. 4-5 and 4-6). In other words, it becomes like “ㅎ = 0~”. As the applicant's personal opinion, “ㅎ = 8**” or “ㅎ = 0**” or “ㅎ = 0 (only special cases previously suggested in the earlier application)” based on Figures 4-5 as previously presented in the previous application It is presumed that inputting with ' is better in terms of input efficiency than using a long press. The input method of the previously suggested dropped consonant (eg “ㅎ”) and the input method by long pressing can be selectively applied.

It is said that it is possible to input a target by using a short press after a long press, but in the drawings of Figs. When a certain object is defined as input, a series of objects related to the specific button can be input by pressing a certain button for a long time and then pressing it briefly. The reason is as described above “. (period) = ㅁ+ㅡ+ㅡ”, since there is no Korean character starting with the vowel “ㅡ” after “some object (period in the example)” that is not a Korean consonant, “, (comma) = ㅁ+ㅡ +ㅡ+ㅡ” is the same as what can be defined. If “-(hyphen)” is defined as a long press of the [*] button (the button to which “ㅡ” is assigned), it can be defined by long-pressing any other object (e.g. underscore) and then repeatedly pressing it. . That is, “- (hyphen) = *~” and “_ (underscore) = *~*”. This is also due to the fact that vowels in Hangeul do not appear at the beginning of words. Using the property that the vowel element “.” does not appear at the beginning of Korean, a short press of the button assigned “.” (the [0] button in the example) in the “word start state” can be input as “ㅎ” As revealed, the pressing of the vowel button in the “word start state” can be defined as the input of a specific object (eg, a special character related to the vowel button). For example, when a button assigned “ㅡ” ([*] button in the example) is pressed at the beginning of a word, it can be set to “-(hyphen)”. However, when applying this, there is a disadvantage that the vowel “ㅡ” cannot be entered as a character. Of course, even in this case, after a specific object (“-” in the example) that is not a consonant is recognized by the input of the button to which “ㅡ” is assigned, and then the button to which “ㅡ” is assigned is pressed, it is associated with another object (eg. It can be defined to be input of special character “_”).

Next, an example of applying “control processing method by long press and then repeated press” is presented. Applicant's representative Korean input system is introduced along with a simulator on the homepage http://www.simplecode.net (introduction of archaic language, symbol input and parallel input technology), and input of numbers and English alphabets is also switched to mode. It is mentioned that it is possible without

It is revealed that this application was inevitably executed because there was a request from people in the industry to provide input technology for numbers and English without mode conversion. (For reference, the company that made this request did not adopt the Korean input technology of the applicant. It is a pity.)

The general frequency of use in input can be seen in the order of “national language alphabet - various symbols (special characters) - numbers - English alphabet”. As shown in FIGS. 4-5, etc., there is no control button that can be used to input numbers and English. Here, it is possible to input a number in combination with a long press of the number button and the [*] button (ie, “*~ = number control”). That is, “number 1 = 1*~”. The [*] button is primarily a vowel button and is used as a control button at the same time. Pressing the [*] button once displays the vowel “ㅣ”, but pressing the [*] button once for a long time is an arbitrary target (in the example, “ number control”).

The English alphabet can be input in various ways. For example, “A = 2#~”, “B = 2#~#”, “C = 2#~#” can be defined. Regarding “2#~#” input, what is not recognized as “A” and vowel “ㅣ” and can be recognized as “B” is the property of no syllables starting with vowel “ㅣ” in Korean (a kind of Korean restriction) is to use If long pressing and repeated pressing of the [#] button is used for other purposes, the English alphabet is regarded as the subsequent alphabet of numbers, and “A = 2*~*” or “A = 2*~# (cross control processing Method)” can be defined in various ways, such as “B = 2*~**” or “B = 2*~##”.

One more example of a control processing method by a long press is presented. In Figures 4-5 to 4-8, inputting “TT” and “ㅠ” by repeatedly pressing the button assigned to the vowel “ㅡ” (i.e., “ㅡ = *”, “TT = ** ”, “ㅠ = ***”), it takes up to 3 strokes (that is, the maximum possible number of repetitions) of consecutive pressing of the [*] button to input the alphabet. In this case, the aspirated consonant control can be selected by pressing “maximum number of repetitions + 1” times (ie, [*] button 4 times). “In other words, “ㅋ = 1 ****”. In this case, in order to alleviate the burden of pressing 4 times in succession, it can be defined as “ㅋ = ㄱ+{Acoustic consonant control} = 1*~” with “aspirated consonant control = *~”. The same can be applied to dropped consonants that are considered hard consonants and modified alphabets. In addition, it can be applied to all cases in which the consonant control is selected by the repeated selection method in the control processing method, and the modified alphabet input by long pressing and the modified alphabet input by conventional repeated pressing are optional (either one or both Of course, both are possible. In this case, you can use other buttons (eg [#] button) to input numbers.

26.3 Japanese

As in the case of Japanese in FIGS. 2-1 and 2-2, there are many subsequent alphabets, which can be useful when inputting subsequent alphabets by the repeated selection method. That is, “あ = 1” or “あ = 1~”, “い = 1~1”, “う = 1~11”, “え = 1~111”, “お = 1~1111” will be. As mentioned, if the alphabets assigned to the same button appear consecutively, only the second alphabet among the letters assigned to the same button is entered using a long press (ie, “1 ~ ”), otherwise, simply Even if it is entered by pressing once, it is entered without ambiguity. However, in the Japanese cases of FIGS. 2-1 and 2-2, it has already been shown that input can be input without ambiguity with a small number of input strokes by applying the follow-up control processing method, which can be applied together with the repeated selection method by long-pressing the representative alphabet. have.

* In the case of inputting the subsequent alphabet as a control method without applying the repeated selection method by pressing and holding the representative alphabet, the case of inputting the modified alphabet using long pressing is shown. When inputting subsequent alphabets by the control processing method in Fig. 2-2, when inputting modified alphabets (eg, “ば”, “ぱ”) of representative alphabets (eg, “は”) as shown in Fig. 2-3, input strokes It can be seen that there are rather many and unnatural. In this case, a long press of the corresponding button (button [6] in FIG. 2-2) can be defined as a modified alphabet (eg “ば”) of the representative alphabet. The rest of the modified alphabet can be defined as “ぱ = ば + predetermined control button (eg [*] button) = 6~*”.

Here, if the modified alphabet is not input by using the long press of the button assigned to the alphabet, the repeated selection method by long press of the representative alphabet and the subsequent alphabet input by the control processing method can be applied together. The input of modified alphabets (eg “ば”, “ぱ”) can be performed by long-pressing an arbitrary control button (eg [*] button) and a combination of the representative alphabet “は” to enter “ぱ”. . That is, it can be defined as “ば (any modified alphabet) = は + *~ = 6*~” and “ぱ (any other modified alphabet) = は + *~* = 6*~*”. If there are many modified alphabets of “は”, it is possible to input without ambiguity by pressing and holding repeatedly, such as “6 * ~ **”, “6 * ~ ***”, ... Of course. Just as “*” and “*~” can represent different objects, “**” and “*~*” can represent different objects (in this case, arbitrary controls).

What is important here is that not only can an arbitrary control be selected by long press, but also another object (eg, arbitrary control) can be expressed.

Likewise, in the input of numbers and English alphabets, what has been described in Korean can be applied. For example, “number 2 = 2#~” can be defined, “A = 2#~# ”, “B = 2#~##”, . . . can be defined as

26.4 Chinese

It was shown that Chinese pinyin can be input without ambiguity (or almost without ambiguity) on keypads such as Figs. 10-1 to 10-6. However, when entering “bb = 11” to shorten a word composed of “b__b__” (the underscore part is a Pinyin syllable composed of vowels), if the language restriction that “bb” does not appear consecutively in Chinese Pinyin is applied, “ 11 = p ” will be recognized. In this case, as mentioned above, after inputting “b = 1”, the input value “1” is intentionally confirmed as “b” by a predetermined time delay or a specific operation (eg, pressing the [>] button), and then “b” = 1” must be entered. It can also be seen as a problem of ambiguity that occurs when alphabets assigned to the same button are entered consecutively. In this case, it can be solved by applying the control processing method by pressing and holding the representative alphabet (representative alphabet “b ” of the [1] button as “b = 1~”). For example, “bb = 1~1~” or when the alphabets assigned to the same button appear consecutively, “bb = 11~” can be obtained by applying a long press to the alphabet input after the second.

Next, it shows entering numbers and symbols. It will be described based on Fig. 10-6. Input of English in Chinese is not mentioned because it is not necessary to convert it to Chinese characters after inputting English alphabets. Based on Figure 10-6, it can be defined as "number 1 = 1 * ~". In Fig. 10-6, pressing the [*] button once is recognized as “a”, but long pressing (“*~”) can represent a separate object (“numerical control” in the example). 10-6, it is preferable to apply a control processing method using a long press and repeated press of the [#] button to various symbol inputs. For example, associate dot(.), comma(,), colon(:), semi-colon(;), etc. with the [2] button, “dot(.) = 2#~”, “ comma(,) = 2#~#”, “colon(:) = 2#~##”, “semi-colon(;) = 2#~###”. “2#~#” is not recognized as “dot(.) + i” but can be recognized as “comma(,)” because Chinese Pinyin uses the Chinese restriction that does not start with “i”. (Refer to Korean example) Likewise, “2#~##” is not recognized as “dot(.)+i+i” or “comma(,)+i”, but can be recognized as “colon(:)”. If you want to input “dot(.)+i”, as mentioned, after inputting “2#~” and confirming “dot(.)” after a certain amount of time has elapsed, or for a specific operation (e.g. [>] After confirming “dot (.)” by pressing the button), input “# = i”.

The reason why the [*] button was not used to input the symbol(s) of a specific group in Fig. 10-6 is that there are rare Pinyin that start with “a”, “e”, “o”, etc. This is because ambiguity may occur when using “repeated press”. This is because there is only one number in the case of numbers, so you only need to press and hold the [*] button once. In the case of Figs. 10-1 to 10-5, since there is no pinyin starting with “i” and “u” assigned to the [*] button and the [#] button, use the [*] button and the [#] button to It is always possible to input numbers, symbols, etc. as a control processing method using repeated pressing after pressing.

It is obvious that the above information can be similarly applied to other keypads as well as the keypads of FIGS. 10-1 to 10-6.

26.5 Languages using the Roman alphabet

In European languages using the Roman alphabet, there are many modified alphabets with subscripts attached to the basic alphabet. By applying various long presses described above, it can be applied to input of modified alphabets and input of special characters.

27. Device and method for inputting Korean syllables (= consonant characters) by unbroken dragging on the screen keyboard

27.1 Existing input method using drag technique

Recently, with the advent of convergence devices such as UMPC (Ultra Mobile PC), a number of technologies for inputting characters through a drag technique on a keyboard displayed on a liquid crystal (screen) have been introduced. The representative technology is an input device called "Moaki", and the representative concept is to touch a specific consonant (eg "ㅇ") with a pen (or click with a mouse) on a liquid crystal keyboard as shown in Fig. When dragging to the left/right side, "oh/right/uh/ah" is input respectively. If you touch and release only one consonant (ie, without dragging), the [ㅡ] button, [ㆍ] button, and [ㅣ] button that can input vowels pop up around the touched consonant as shown in Fig. 15-2. Allows additional vowels to be entered. Here, "drag" is also referred to as a "gesture" and means dragging and moving without releasing the touch or click in a state of being touched or clicked. The point at which the dragging ends is the moment when the pen touch is released or the mouse click is released after the dragging. The concept of drag can be easily understood after using a program that supports mouse gestures, and the term "drag" is used in the present invention.

Due to the characteristics that other input methods have not provided, Moaki enjoys some popularity despite the limitation of operating only on the touch screen. There are some downsides, such as the inability to input emoticons (e.g. "TT", "TT", "ㅡ.ㅡ", ...) that express emotions with Korean vowels, and the 19 consonant buttons on the screen. In the case of a PDA, about half of the screen is consumed as a keyboard, and the same input technology cannot be used for button input.

In addition, there is content that allows input of two buttons starting and ending with dragging on a specific keyboard by the dragging. For example, if you start a pen touch (or mouse click) from the [a] button, drag it to the [ㅣ] button, and then release it, "ki" is input. This does not necessarily apply only to "primary + neutral", but applies to all cases. However, this case is always applied only to two buttons: a point (start button) to a point (end button). It is also very simple to implement, just process the "drag start button" where the drag started and the "drag end button" where the drag ended are pressed. The start of dragging can be detected by detecting that the first touched position (coordinates) moves in the state where the pen touch (or mouse click) starts and the pen does not drop (or the mouse click does not drop). This is the same as detecting a "mouse gesture" that is widely used on a PC, and since it is a technique widely known to the extent that many individual users are already distributing their own mouse gesture programs, the present invention mentions the above procedures and processes in detail. I never do that.

27.2 Configuration of syllable input technology by continuous drag presented in the present invention

The present invention proposes a technique for inputting one Korean syllable (consonant letter) by one continuous drag. It was directly confirmed that this technology was not presented in the "Moaki" product.

The contents of the present invention can be applied to all cases of inputting syllables by dragging consonant and vowel buttons on a liquid crystal display keyboard (keypad, keyboard, and all other modified forms). For convenience, a mobile phone keyboard will be described as an example, and in particular, the keyboard and input method presented by the applicant in the previous application will be described. All types of Korean keyboards are divided into consonant buttons with consonants and vowel buttons with vowels. Typically, drawing 15-3 is a mobile phone keyboard of Samsung Electronics, and drawing 15-4 is a mobile phone keyboard of LG Electronics. Each input method is too well known to be described here. However, in all input methods, the consonant placed on each consonant button (at least the first consonant when multiple consonants are placed) is entered by pressing the corresponding button once, and the vowel is also entered by pressing the vowel button where vowels are placed once. However, the vowel buttons are composed of a small number (usually 3 to 4 buttons), and the remaining vowels are input by combining the vowel buttons with a predetermined method provided by the corresponding input method.

The most important thing in the present invention is that when configuring a Korean keyboard in any input method, consonant buttons are grouped together and vowel buttons are grouped. Even if you don't do that, it doesn't matter to apply the corresponding input method, but anyone is doing it for the user's "identification of button position". For example, it means that no one will mix and match consonant buttons and vowel buttons. This is also the case with the Korean keyboard. One of the keyboards proposed by the applicant (explained in Chapter 4 of the applicant's previous application and detailed description of the present invention. In particular, the contents described in 4.1.1 and 4.11. Hereinafter referred to as "applicant's Korean input method") is shown in Figure 15-5 ( It is the same as a) or Fig. 15-5 (b), and similarly, the consonant buttons are grouped together, and the vowel buttons are grouped together. Figures 15-5 (a) and Figure 15-5 (b) were called keypads (keyboards) that can be interchanged with each other. Being mutually compatible means that the input method described based on Figure 15-5 (a) can also be applied to Figure 15-5 (b), and conversely, the input method presented based on Figure 15-5 (b) is shown in Figure 15-5 (b). This means that it can also be applied in 15-5(a). In the existing keypad Korean input method in Fig. 15-3 and Fig. 15-4 and the Korean input method proposed by the applicant, the number of vowel buttons is relatively less than the number of consonant buttons in most cases.

About half of Korean syllables (consonant characters) consist of "initial consonant + neutral", and about half of them consist of "initial consonant + neutral + final consonant". This is the same as the meaning that about half of the letters composed of "consonants + vowels" and about half of the letters composed of "consonants + vowels + consonants".

Fig. 15-6 is a drawing in which Fig. 15-5 (a) is applied to a "numeric keypad" of a PC, and the same keyboard (keypad) is presented. In the following, it is assumed that there are only 12 character buttons ([a] ~ [j] consonant buttons 9, [ㅡ], [a], [ㅣ] vowel buttons 3) in Drawing 15-6, unless there is a special case , Based on Figure 15-5 (a) (ie, based on the applicant's Korean input method presented in Figure 15-5 (a) and related description). When inputting "high" based on the input method suggested by the applicant in "Applicant's Korean input method" based on Fig. 15-6, press [a] + [a] + [ㅡ]. In terms of implementation (programming), a character (eg "a") can be displayed on the screen the moment a specific button (eg the [a] button) is pressed, or a character can be displayed on the screen the moment a specific button is pressed and released. may be In most screen input devices (e.g., screen keyboards), characters are input the moment you press and release a button on the screen (ie, the moment you press and release the button instead of the moment you press the pen, or the moment you click and release the mouse, not the moment you click). Yes, it is a built-in screen keyboard in MS Windows), and there is no difference in technology. In the case of mobile phones, depending on the manufacturer, some products display letters the moment the button is pressed, and some products do not display letters while the button is pressed, but display letters the moment you release it, and there is no difference between the two.

Hereinafter, it is mainly explained based on the applicant's Korean input method presented by the applicant, and it is obvious that the same or similar application can be applied to other input methods. The content described below based on the applicant's Korean input method is a proven technology implemented as a program, and will be released as a programmed character input device product through the homepage http://www.simplecode.net after the patent application for the present invention is filed. to be. 15-6 is a UI (User Interface) applied to the character input device to be disclosed.

Based on drawing 15-6, if the user starts from the [a] button to write the letter "high" and drags through the [a] button to the [ㅡ] button, as shown in drawing 15-7, the button (i.e. , the button being dragged) will be multiple buttons. When the system recognizes the buttons being dragged, the position of the pen or mouse cursor changes in a predetermined short time (eg 1/100 second) interval from the moment the button on the screen is touched (or mouse clicked) until it is released. You just need to check which button it is located on.

In order to facilitate the description of the present invention, "dragging" is referred to as "drag" or "drag operation" as shown in Figs. . In Fig. 15-7, the "drag start button" where the drag operation starts is the [a] button, the "drag end button" where the drag operation ends is the [ㅡ] button, and the "dragged button" is the [a] button, [ These are the b] button, the [ㅁ] button, the [ㅇ] button, the [j] button, the [a] button, and the [ㅡ] button. When the button(s) dragged by the dragging operation of FIG. 15-7 are marked, [a → b → ㅁ → ㅇ → ㅣ → ahn → ㅡ] will be marked. For convenience of description, when dragging is displayed as shown in FIG. 15-7, the drag start button is indicated by putting a circle (●), and the end point of the drag is indicated by an arrowhead.

It is easy to input adjacent buttons by dragging. However, when there are a large number of dragged buttons, determining which button is the button the user intends to input is a worrisome problem. In Fig. 15-6, if you start dragging from [a] to input "that", you go to the [ㅡ] button through the [ㄹ] button and the [ㅅ] button. It is intended to present a very efficient method for determining which button is the button the user intended to input, and this content is the core of the present invention.

In order to go from a large number of consonant button groups ([a] button to [j] button) to a relatively small number of vowel button groups, it is determined that the user intended to press all the dragged consonant buttons. I never do that. That is, when dragging from the consonant button to the vowel button in Fig. 15-7, the first consonant button (drag start button) where the drag started is determined to be at least the button the user intended to input, and the next consonant button ( In the example, [ㄴ] button, [ㅁ] button, [ㅇ] button, and [ㅅ] button) do not form a valid initial consonant together with the drag start button, so they are regarded as buttons that the user did not want to input and are ignored. This is due to the nature that consonants do not appear consecutively at the beginning of Korean syllables (consonant characters). Next, the first vowel button ([A] button in the example) is regarded as the vowel button that the user intends to input, and can be combined with the [A] button already considered as a valid button to form "ㅗ". [ㅡ] button is also considered as a valid button. Excluding the buttons ignored by the system among the dragged buttons [a → b → ㅁ → ㅇ → ㄴ → a → ㅡ], if only the buttons recognized by the system are marked as valid buttons, [a → a → ㅡ] becomes [a → a → ㅡ]. Depending on the user, as shown in Fig. 15-8 (a), it may be dragged as follows [a → b → ㅁ → f → ㅣ → a → ㅡ]. Also in this case, "ㄴ → ㅁ → ㄴ → ㄴ" is invalidated, so the button recognized as valid is [a → a → ㅡ]. Even if the user drags as shown in Fig. 15-8 (b), the result is the same.

If the user did not end the drag operation above and dragged up to the [b] button (i.e., without releasing the pen touch or mouse click from the [ㅡ] button, release the pen touch or mouse click from the [b] button) release), it also goes through a number of consonant buttons. For example, as shown in Fig. 15-9, the total number of dragged buttons becomes [a → b → ㅁ → ㅇ → ㄴ → ㄱ → ㅡ → ㅇ → ㅁ → ㄴ]. Even in this case, a number of consonant buttons (in the example, [ㄴ] button, [ㅁ] button, [ㅇ] button, [ㅅ] button in the initial part, and [ㅇ] button, [ㅁ] button in the final part buttons) are all ignored without determining that the user wanted to enter (i.e., a valid button). This is because Korean syllables consist of "consonant + vowel + consonant", so it is reasonable to judge that you wanted to input only the consonant ("ㄴ" in the example) that ends the final drag. If only valid buttons are displayed among the dragged buttons, [a → a → ㅡ → b], and the syllable (consonant letter) recognized (or recognized) as a result of the dragging becomes "gon".

As seen in the above case, the first drag start button and the last drag end button are always recognized by the system as valid buttons, and only the buttons necessary to form Korean syllables are recognized as valid buttons The core of the present invention is to input Korean syllables by dragging once as the rest of the dragged buttons are ignored.

Next, it is shown that input by pressing the same vowel button twice can be input by dragging. If you want to input "Y", you will have to drag [ㅇ → ㅡ → A] to input "right", and then click the [A] button to input "Y". If you suggest two different methods, drag it up to [ㅇ → ㅡ → A], drag it to the [ㅡ] button, which is a vowel that cannot be combined with the vowel "TT", without ending the dragging, and then drag it again with the [A] button. . If you mark the dragged button, it becomes [ㅇ → ㅡ → A → ㅡ → A]. Similarly, the [ㅡ] button, which is a vowel button that cannot be combined after "TT", is ignored, and only the next [A] button is recognized as a valid button. The disadvantage of this method is that there are cases where the input of only the current vowel is used as a kind of emoticon (eg "TT"), but this case cannot be expressed. For example, if the above content is not applied, in order to input "TT", you can input "TT" at once by dragging [ㅡ → A → ㅡ → A]. In the product (http://www.simplecode.net) that is planned to be implemented and distributed as a program, "TT" is entered as [ㅡ → ア → ㅡ → ア]. Another method is to drag from the [A] button to a random consonant button ([ㅅ] button in the example) without stopping dragging after [ㅇ → ㅡ → A], and then drag it back to the [A] button. In other words, if you drag [ㅇ → ㅡ → A → ㅣ → A], you can input "U". In order for the final consonant to be entered, the dragging must end at the consonant button ([i] button in the example). to treat it as That is, the [j] button that is not valid due to the final input serves only to inform that the [a] button dragged thereafter has been input “once more”. Of course, it is natural to end dragging to [ㅇ → ㅡ → A], input "right", and then touch (or click) the [A] button once. If [ㅇ → ㅡ → A → ㄴ → A → ㄴ → ㄴ → ㅁ] is dragged, the system recognizes and processes it as "yum" (Fig. 15-10. is ignored)

The above is possible even when dragging is additionally started in a state in which only "initial consonant" is input, in a state in which "initial consonant + neutral" is input, or in a state in which "initial consonant + neutral + final consonant" is input. Some examples of input are as follows based on Figs. 15-5 (a) and 15-6. For convenience, it is stated that among the buttons that are dragged, the buttons that are invalidated (ignored) may not be displayed. When inputting "Wing", if you drag [ㅇ → ㅅ → ㅡ → A → ㅣ → ㅅ → ㅇ], you can input "Wing" with one drag motion. The [ㅅ] button next to the [ㅇ] button is ignored because it does not form a valid initial consonant, and the [ㅅ] button is also ignored because "ㅇ" is the final consonant. This is because if "ㅅ" was the initial consonant the user wanted, the drag would have started at "ㅅ", and if "ㅅ" was the final consonant, the drag would have ended at "ㅅ". In Figure 15-6, it is possible to drag from the [ㅇ] button to [ㅇ → ㅡ → ...] without passing through the [ㅅ] button, but this is an example presented to show the case where the [ㅅ] button is ignored. If it is dragged to [ㅇ → ㅅ → ㅡ → A → ㅣ → ㅅ → ㅇ → ㄴ] as in Fig. 15-11, "up + ㅅ" ('up' + 'ㅅ' base) will be input. Even if multiple consonant buttons are dragged after the [ㅇ] button (e.g. [ㅇ → ㅅ → ㄹ → ㅁ → ㅇ → ㅡ →...]), only the first [ㅇ] button is considered a valid initial consonant and the vowel Other consonant buttons before the [ㅡ] button are ignored. Likewise, even if dragged like [...→ ㅅ → ㅇ → ㄴ], only the last [ㄴ] button is considered as a valid final consonant, and the remaining consonant buttons are ignored. That is, in the initial consonant, only the button forming the initial consonant in a predetermined input method, including the drag start button, was considered a valid button, and similarly, in the final consonant, only the button constituting the final consonant in a predetermined input method, including the drag end button, was considered a valid button. will be.

As another input example, to input "ㄺ + ㄺ" ('ㄺ' for 'ㄺ'), drag [ㅅ → (ㅁ → ㅇ) → ㅡ → ] and enter "B", then [a → Drag to ㅣ] and input "B", then drag to [ㅣ → (ㄴ → ㅇ → ㅁ) → ㄹ] and enter "V + ㄹ" (subject to 'ㄹ' to 'V'), then click the [ㄱ] button You can do it. Refer to Fig. 15-12 (a). Buttons marked with parentheses, such as "(ㅁ → ㅇ)" and "(ㅁ → ㅇ → ㅁ)", are ignored (invalidated) buttons, and may not be marked below for convenience. Another thing is to input "V" with [ㅅ → ㅡ → A → ㅣ → A → ㅣ → ㅣ → ㅣ], then enter "V + ㄺ" ('ㄺ' in 'V') with [ㄹ → ㄱ] do. Refer to drawing 15-12 (b). The two [i] buttons entered when inputting "V" were entered to distinguish the continuous input of the [ㅣ] button for continuous input of the [a] button, respectively. When the button being dragged starts from the consonant button and goes through the consonant button to the vowel button, the middle consonant button is disabled, but when the drag starts from the consonant button and ends at the consonant button, the consonant button where the drag starts and the consonant button where the drag ends It is natural to assume that all are entered. Therefore, the final consonant "ㄺ" is input by dragging [ㄹ → ㄱ]. Of course, [ㄴ → ㅡ → A → ㄴ → A → ㅣ → ㄴ → ㅣ → ㄹ] at once to enter "V + ㄹ" ('D' followed by 'D'), then press the [ㄱ] button to enter "V + ㄺ" You can also enter "('ㄺ' for 'ㄺ'). All of the above has been demonstrated by being implemented as a program, and all will be released as products through http://www.simplecode.net after the application of the present invention.

The following is the content scheduled for implementation (programming). Furthermore, based on Figure 15-6, if it is defined as dragging [a → b] and inputting "ㅋ", dragging [a → b → ㅁ → ㅇ → ㅡ], dragging "a → b" The initial consonant "ㅋ" is processed as input (ie, the [a] button and [b] button constituting the initial consonant are regarded as valid inputs), and the middle [ㅁ] button and [ㅇ] button are ignored, so the system It can recognize and process the input of "K". If dragging from the [a] button to the left outside the button is defined as "ㅋ" input, as shown in Fig. 15-13 (a), dragging to [a → 外 → ㅡ] is "k" input can be treated as Also, if it is defined as inputting "ㄲ" by dragging to [a → 文/Num], dragging to [a → 文/Num → a → ㄹ → ㅅ → ㅡ] as shown in Figure 15-13 (b), The system can recognize and process it as "Off".

A few more examples based on other text input technologies are as follows. Based on the drawing 15-4 of the character input device adopted by LG Electronics, start dragging from the [a] button, pass through other consonant buttons, pass the [overwrite] button, and then [ㅗ] button, [a] button, [ㅣ] When the drag is completed from the [b] button via the button, "pleasure + a" ('plea' followed by 'a') is input by continuous dragging. Drawings exemplifying the dragging process are drawings 15-14, and the dragged button is marked [a → ㄹ → ㅅ → overwrite → ㅅ → ㅇ → ㅁ → ㅗ → A → 外 → ㅣ → ㅇ → ㅁ → ㄴ→ ㄱ ] becomes. As shown in Fig. 15-4, if the buttons are separated from each other, you can go directly to the button located diagonally, but assuming that there is no gap between the buttons, it is dragged past the button in the vertical / horizontal direction. Fig. 15 -14 was expressed. This is because the normal screen keyboard does not have a space between the buttons on the liquid crystal. In the process of dragging to input "ㅋ", it passes the [ㄹ] and [ㅅ] buttons, but since two consonants do not come in succession in Korean syllables, the [ㄹ] and [ㅅ] buttons can be ignored. There is. Similarly, in order to drag from the [ㅣ] button to the [ㄱ] button, the [ㅇ] button, [ㅁ] button, and [ㄴ] button are passed, but only the [a] button, which is the consonant button after the drag is terminated after the vowel, is valid. (That is, ignore the [ㅇ] button, [ㅁ] button, and [ㄴ] button). For one more example, similarly, if the drag starts from the [a] button, passes through the [ㅗ] button, and ends at the [ㅁ] button, it can be treated as having entered "bear". However, when the dragged button becomes [a → ㄴ → ㅁ → ㅗ → ㅁ → ㅇ → ㅅ → Overwrite → ㅅ → ㄹ → ㅁ] as shown in Fig. 15-15, the button dragged after the vowel "ㅗ" [add It can be processed as inputting "Kyo + ㅁ" ('Kyo' followed by 'ㅁ') with the [Write] button. If one of the dragged "ㅁ", "ㅇ", and "ㅅ" is entered after the vowel "ㅗ", a drag is entered from one of the [ㅁ] button, [ㅇ] button, and [ㅅ] button next to the [ㅗ] button. should have ended On the keyboard of Samsung Electronics, when the drag operation starts from the [ㅅ] button, passes through the [ㅣ] button, [ㆍ] button, and the drag operation ends at the [ㅇ] button, "Up" is input. (See drawings 15-16)

Next, an example is given based on the case where the Korean double keyboard used in the current PC is on the liquid crystal. For convenience, it is assumed that there are only consonant buttons and vowel buttons marked with Korean consonants in Figures 15-17, and the case where the position of the key is changed for efficiency is also included. In Fig. 15-17, if the dragged button is [a → ㅅ → ㅎ → ㅗ → ㅇ → A → ㅣ → A → ㅗ → ㅗ → ㅎ → ㄹ → ㅇ], in this case, the drag start button [a You can ignore the [ㅅ] and [ㅎ] buttons after the ] button. Next, the [ㅗ] button, which is the first dragged collection button, is considered a valid button, so the [sh] button and the [a] button that cannot be combined with the [ㅗ] button can also be ignored, and the [ㅗ] button can be combined. The [ㅣ] button can be regarded as a valid button. Next, the [A] button, [sh] button, and [ㅗ] button that cannot be combined with "ㅚ" are also ignored, and among the last three consonant buttons, the [ㅎ] button and the [ㄹ] button are also ignored, and the drag ends. Only the [ㅇ] button can be considered as a valid button. As a result, "Awesome" is entered. The above result is a result obtained based on the input method on the double keyboard.

The timing of outputting the result recognized (or recognized) by the system to the user (displayed on the screen or transmitted by voice) can be output at the moment the system recognizes it as a valid button among the buttons dragged in the middle of the dragging. It can also be output when all are finished. There is no significant difference between the two, and rather, the output of letters in the middle of dragging is a little confusing. One unit recognized by the user is a completed consonant, vowel, or syllable (consonant letter), and since one syllable is input by dragging once, after the end of dragging, it is recognized/recognized by the system (or It doesn't seem too bad to output a single syllable (which was entered into the system by

With the above procedure, it was shown that Korean syllables were input with one drag. In particular, under the exemplified input method of the applicant, most Korean syllables can be input by dragging once. It is obvious that various modifications are possible under the contents described in the present invention. For example, it can be applied even when a collection button pops up after touching (or clicking) one button, as in the Moaki keyboard of Figure 15-2. Of course, Moaki does not support drag input in units of syllables as suggested above. Moreover, Moaki input technology can be applied only to the touch screen method due to the nature of the technology, but as the technology proposed in the present invention, the same Korean character input technology can be used by button pressing method and pen touch or drag method on the touch screen. There are advantages to being

The drag technique described above can be applied both to a case of pen touch on a keyboard on a touch screen and to a case of clicking a mouse on a keyboard on a screen. Since touch screen and screen keyboard technologies are already common technologies, hardware structures are not described. Even if a hardware configuration technology that is slightly more precise than the current touch screen hardware configuration emerges, it is self-evident that there is no problem in applying the spirit of the present invention, and it is not at all to describe a device configuration for a touch screen or screen keyboard that is already generalized. Because it has no meaning.

The above contents are summarized in the form of claims and are as follows.

In a keyboard equipped with a plurality of buttons on a screen (liquid crystal), based on a predetermined input method, Korean letters (consonants, vowels, consonant letters, words or phrase) in the method of inputting,

(a) detecting the start of a drag operation and recognizing the button (drag start button) on which the drag starts

(b) recognizing the buttons dragged by the drag operation, and recognizing only the consonant buttons that can form Korean initial consonants, including the drag start button, as valid inputs among the dragged buttons by a predetermined input method step

Korean character input method by continuous dragging on a liquid crystal (screen) keyboard, characterized in that characters are input with

In addition, may include:

(c) Recognizing that a vowel button (or vowel buttons) is dragged by the dragging operation

(d) Recognizing vowels formed by the dragged vowel buttons, including the initially dragged vowel button, by the predetermined input method

Korean character input method by continuous dragging on a screen (liquid crystal) keyboard, characterized in that characters are input with

Or, as shown in the case of dragging on the on-screen double keyboard,

(c) Recognizing that a vowel button (or vowel buttons) is dragged by the dragging operation

(d) Recognizing only the vowel buttons that can form Korean neutrals by the predetermined input method among the dragged vowel buttons, including the first dragged vowel button, as valid vowel buttons

Korean character input method by continuous dragging on a screen (liquid crystal) keyboard, characterized in that characters are input with

in addition to

(e) Recognizing that the drag operation is terminated

(f) processing the consonant button for which the drag is terminated as a valid input

Korean character input method by continuous dragging on a screen (liquid crystal) keyboard, characterized in that characters are input with

can include

In addition, the main idea of the present invention is to determine that the drag start button and the drag end button are always valid buttons among the dragged button(s), and only the buttons that can be effectively combined with the drag start button according to a predetermined input method are effective. It can be seen that it is essential to determine the button as a button and to determine only the button that can be effectively combined with the drag end button as a valid button. Of course, the button determined as a valid button is processed by the predetermined letter input method, and the system recognizes the input letter and outputs it to the user. In addition, among the dragged buttons excluding the drag start button and the drag end button (for convenience, "the dragged button except for start and end"), buttons that cannot form Korean syllables (consonant consonants) are invalidated (ignored) and Korean syllables can be formed. This includes judging and processing only possible buttons as valid buttons.

therefore,

In a keyboard equipped with a plurality of buttons on a screen (liquid crystal), based on a predetermined input method, Korean letters (consonants, vowels, consonant letters, words or phrase) in the method of inputting,

(a) recognizing the button(s) being dragged by the drag operation;

(b) determining a drag start button and a drag end button among the dragged buttons as valid buttons for the letter input;

(c) Determining a button that can be combined with the drag start button as a valid button according to a predetermined Korean character input method

Korean character input method by continuous dragging on a liquid crystal (screen) keyboard, characterized in that it comprises

As shown in Fig. 15-1 to Fig. 15-17, valid buttons are judged except for invalidated (ignored) buttons among the dragged buttons, additionally.

Determining the valid button in (c) above is based on the Korean consonant combination rules for forming Korean syllables.

Korean character input method by continuous dragging on a liquid crystal (screen) keyboard, characterized by

can include Of course, Korean characters recognized as a result can be output (displayed on the screen or output as voice...).

28. Device for inputting Korean syllables (= consonant characters) by unbroken dragging on the screen keyboard and its method, Part 2

In the present invention, an additional technology is presented as an extension of the “Korean syllable (= consonant character) input device and method by uninterrupted drag on the screen keyboard” introduced in Chapter 27 above.

28.1 Prototype of input method using drag technique

A long time ago, a web browser called “Opera (http://www.opera.com)” provided a function called “Mouse Gesture”. Now, it has become a common technology used by many people in Internet Explorer (IE), which is basically installed in MS Windows through various utility programs. Figure 16-1 (a) and Figure 16-1 (b) show the operation of the “mouse gesture” function in the latest version (v9.6) Opera browser. In Fig. 16-1 (a), clicking the right mouse button and dragging to the right shows the next page, and in Fig. 16-1 (b), clicking the right mouse button and dragging to the left shows the previous page. The button to move to the “previous page” is displayed as a “left arrow button” in any web browser, and the button to move to the “next page” is displayed as a “right arrow button”.

Next, Fig. 16-2(a) is the initial screen of the Pocket PC 2000 emulator included in Embeded Visual C++ 3.0 distributed free of charge by Microsoft, and Fig. 16-2(b) is when the word processor is executed in the emulator. , This is the screen keyboard screen that appears. Figure 16-2 (c) is an option setting screen of the screen keyboard input device. As shown in Figure 16-2 (c), at this time, input by dragging in four directions was already provided. Summarizing the contents of drawing 16-2(c), it is the same as drawing 16-3, and if you click (or touch) once, the alphabet “X”, which is the basic character marked on the button, is input, and if you drag upward, Shift and Combined characters are input, dragging to the right inputs a space, dragging to the bottom inputs the enter function, and dragging to the left inputs the backspace function.

Figure 16-4 shows an application example in Japanese. If you touch it once, the basic character “あ” is input, and according to the graph in the up, down, left, and right directions, the remaining characters of the “A” line in the Japanese 50-note scale, “い”, “う”, “え”, and “お”, respectively is entered In addition, there are many types of drag input techniques.

28.2 Technical problem to be solved by the present invention

Currently, Samsung Electronics’ “Moaki” input device, which is the most used drag input technology, supports drag input for the four vowels “ㅗ”, “아”, “ㅜ”, and “sh”. Since the four vowels “ㅗ”, “아”, “ㅜ”, and “sh” have a frequency of use of about 49.16% in Korean, it can mean that about half of the vowels can be input by dragging. .

The vowels “ㅡ” and “ㅣ” have a frequency of use of about 28% in total. However, in the existing method, the vowels “ㅡ” and “ㅣ” cannot be input by dragging, so the input method is consistent and unified. this is not being maintained. In addition, it is impossible to input one Korean syllable (consonant letter) by dragging one continuous time suggested by the applicant in Chapter 27 (referred to as “Invention of Drag Part 1” for convenience).

In Korean Hangeul, a single character (syllable), which is a combination of consonants and vowels, can be seen as the basic unit of thought. In other words, rather than thinking and recognizing in units of phonemes (consonants or vowels) in our thinking system, we recognize them in units of letters in which consonants and vowels are combined. Chapter 27 “Part 1 Invention” and the present invention are intended to suggest that syllables (including final consonants), which are one thought unit, are input with one drag in a consistent method.

6 vowels by adding the 4 vowels of “ㅗ”, “ㄴ”, “ㅜ” and “sh” (frequency of use 49.16%) and 2 vowels of “ㅡ” and “ㅣ” (frequency of use of about 28%) Since has a frequency of use of about 77.23%, it is possible to input about 3/2 or more of the six vowels in a consistent way. In addition, the four vowels “ㅛ”, “ㅑ”, “ㅠ”, and “ㅕ” have a frequency of use of about 6.98%. 2 vowels of “ㅡ” and “ㅣ” (frequencies of use of about 28%), 4 vowels of “ㅗ”, “ㄴ”, “ㅜ” and “sh” (frequencies of use of 49.16%), and “ㅛ”, The frequency of use of 10 vowels, which is the sum of the four vowels “ㅑ”, “ㅠ”, and “ㅕ” (frequency of use 6.98%), is about 84.22%, so most of the Korean vowels can be input by a consistent drag input method. there will be In addition, if the applicant applies the technology presented in Part 1, all vowels can be entered in one consistent method. In addition, by incorporating the technology presented in Part 1 by the applicant, it is possible to input with one continuous drag, including the final support, with one continuous drag.

The invention of Drag 1 is scheduled to be released as an implemented product (a product for a PDA) in the near future, so the present invention (contents of Chapter 28) has been filed, and the details of the present invention will be described below through examples.

28.3 Configuration of syllable input technology by continuous drag presented in the present invention

First, it is shown that the technology in the first piece of invention can be applied to the existing technology (typically, Moaki input device).

The main idea in the Moaki of Fig. 15-1 and Fig. 15-2 is to input “ㅗ” by upper drag, input “A” by right drag, input “TT” by lower drag, and It is to input “ㅇ” by dragging. That is, as shown in Fig. 16-5 (b), when dragging from the [a] button to the right, “a” is input, and as shown in Fig. 16-5 (b), when dragging downward from the [a] button, “sphere” is entered. is entered

However, as shown in Fig. 16-6 (a), if dragged to the right side for a short time and then dragged to the lower side longer, the result is "a" instead of "a". In addition, as shown in Fig. 16-6 (b), if dragged to the lower side and then dragged to the right longer (than the lower drag length), “A” is input as a result. As shown in Fig. 16-6 (c), when dragging in an oblique direction of about 45 degrees, the result sometimes becomes “ga” or “sphere”. Here, Moaki’s implementation method calculates the X-axis movement distance (referred to as “dX” for convenience) and the Y-axis movement distance (referred to as “dY” for convenience) of the drag start point and drag end point, so that the X-axis movement distance dX moves the Y-axis. If the distance is greater than dY, it is recognized as a horizontal drag (right drag in this case), and if dY is greater than dX, it is recognized as a vertical drag (in this case, a lower drag). It has been confirmed that this works in the same way in the “Moaki 2.0” version applied to the latest phones such as Omnia of Samsung Electronics.

However, in order to apply the invention of Part 1, it is newly defined as recognizing the vowel “a” once dragging in the right direction is performed. If dragged [a → ㅅ → ㅎ] as in Fig. 16-6 (a), “a” is recognized as being dragged from [a] to the right of [ㅅ] (the result is “a” combined with “a”). is”) and “ㅎ” is recognized as the last button, so “red” is recognized as a result. In Figure 16-6 (c), it seems ambiguous whether it was dragged with [a → ㅅ → ㅎ] or [a → ㅅ → ㅎ], but if it was dragged with [a → ㅅ → ㅎ], “red” is recognized If it is dragged in [a → ㄹ → ㅎ], “TT” is recognized as being dragged from [a] to the lower direction of [d] (the result is “9”), and the last button of dragging is the [ㅎ] button Therefore, the result is recognized as “Gu + Heh ('Heh' support under 'Gu')”. Here, the vowel is recognized by the dragging direction, and for convenience, the vowel is written in curly braces as {x}. That is, [a → ㅅ → ㅎ] can be written as [a → {A} → ㅎ], and [a → ㄹ → ㅎ] can be written as [a → {ㅜ} → ㅎ] .

If you want to enter “each”, you can do something like this: In Fig. 16-7(a), it was dragged to [a → ㅅ → a], and right dragging from the [a] button to the [ㅅ] button is recognized as “a”, so [a → {a} → a] The result can be recognized as "angular". However, in Moaki 2.0 version, the drag that is dragged to the right and then returned to the original position is treated as recognizing “another collection”. For example, as shown in Fig. 16-7 (a), the drag operation returning to the drag start button after right drag is processed as a vowel “ㅐ”. If this is applied, the drag of Fig. 16-7 (a) will be recognized as a "dog". In this case, a different type of drag operation will be required to input “Gak”. For example, as shown in drawing 16-7(b), if you drag [a → ㅅ → ㅎ → m → ch → ㄹ → a] = [a → {a} → heh → p → ch → d → a] , “A” is recognized by right dragging from the [a] button to the [ㅅ] button, and “P”, “ch”, and “d” are invalidated except for the last button of the drag, “ㄱ”, so the result is “Angle” is recognized. [a → ㅅ → ㅎ → ㄹ → ㄱ] = [a → {a} → ㅎ → π → ch → ㄹ → ㄱ] Even when dragged, “Gak” is recognized as the same result. Even if dragged from the [a] button to the [ㅅ] button as shown in Fig. 16-7 (c) and then dragged in a complicated path, it can be seen that the final recognized result is the same.

In Moaki version 2.0, when dragging starts from the [a] button, drags to the right, and then returns to the [a] button, the vowel “ㅐ” is recognized (as a result, “dog” is recognized). If you return to the drag start button after dragging to the left, “ㅔ” is recognized, if you drag up and return to the drag start button again, “ㅚ” is recognized, and if you drag down and return to the drag start button again, “ㅟ” is recognized. . However, when actually used, the same phenomenon as in Fig. 16-6 (*) occurs. (In Figure 16-6(*), the “*” sign means all) That is, as shown in Figure 16-6(c), if you drag in the direction of about 45 degrees and then return to the drag start button, in some cases, “ㅐ ” is recognized (ie processed as right drag), and in some cases “ㅟ” is recognized (ie treated as lower drag). This is the logic as pointed out in Figure 16-6, and it can be seen that the direction of the drag (in this case, right drag or down drag) is processed by comparing the maximum movement distance in the X-axis direction with the maximum movement distance in the Y-axis direction. have. However, for convenience of description, right drag is described as being dragged to an adjacent right button and then returning to the original button. The rest of the cases (up/down/left drag) are the same.

To input “gang”, just drag [a → ㅅ → a → c → ㅇ] as shown in Figure 16-8 (a). Starting from the [a] button, being dragged to the [ㅅ] button on the right and then returning to the [a] button is defined as “ㅐ”, so it can be explained as [a → {ㅐ} → c → ㅇ], Since the consonant “ㅇ”, the last button dragged after “dog”, is a valid button, “c” is invalid. The result is that the “gang” is recognized. If you want to input “object”, drag it to [a → ㅅ → a → d → a], as shown in Fig. 16-8 (b). [a → ㅅ → ㄱ → ㄹ → ㄱ] can be described as [a → {ㅐ} → ㄹ → ㄱ], and after “dog” is recognized, only “a”, the last button to drag, is recognized as a valid button, This is because “d” is nullified. After [a → ㅅ → ㄱ] is recognized as [a → {ㅐ}], dragging down to [a → ㄹ → ㄱ] and then returning to the original button will not be recognized as “ㅟ”. [a → ㅅ → a → . . . → A] can handle all cases dragged in the same way. “. . .” As in 16-8 (c), means that it is dragged through a number of other buttons (including text buttons, function buttons, or the outside of the keyboard skin).

As above, Samsung Electronics Moaki, a representative existing drag character input device, applied the contents of the first part of the invention (processing the last button of the dragged consonant buttons as a valid button after “initial consonant + neutral” was recognized and invalidating the remaining consonant buttons) In order to do this, the input logic was partially modified and applied, and an example of inputting up to the final support by dragging was shown. However, even in this case, eight vowels can be input by dragging, but all Korean vowels cannot be input consistently by dragging. Next, in the present invention, all vowels are consistently input by dragging, and contents that can be input even to the final consonant will be described. As mentioned in Part 1 of the invention, the following information can be equally applied to all other text input devices (e.g., text input devices adopted by Samsung Electronics and text input devices adopted by LG Electronics), but for convenience, http://www.simplecode.net The description will be based on the character input technology of the introduced applicant.

In Chapter 27, Part 1 Invention, it was mentioned that Figures 15-5 (a) and Figure 15-5 (b) are compatible keyboards. In Figure 15-6, which is the “character input device for pc/one-handed handicapped” screen introduced on the http://www.simplecode.net site, an option to set whether to display the [a] button as “ㆍ” is displayed. It is provided, and the basic setting when installing the program is to display the [a] button as “ㆍ” (ie, Figure 15-5 (b)). 16-9(a) and 16-9(b) are also screens of programs to be released as products for pdas in the near future. Figure 16-9 (b) is the basic setting, but the following is explained with the keyboard in Figure 16-9 (a), and the vowel input technology by basic button combination is introduced on the http://www.simplecode.net site This is the application of “Basic Hangeul 2”.

First of all, in the drag input technology of the existing moaki method, the vowels “ㅗ”, “ㅜ”, “sh”, and “ㄴ” are input by dragging up/down/left/right from the consonant buttons, respectively. As a result, the vowels “ㅡ” and “ㅣ”, which had a frequency of use of about 28%, could not be entered at all by dragging. In the present invention, it is appropriate to input the vowel “ㅡ” by dragging from left to right, and to input the vowel “ㅣ” by dragging from top to bottom for consistent input by dragging and in accordance with “writing habits” point out The applicant was most curious about this part while using Moaki products. When dragging from left to right, of course “ㅡ” should be entered together. If you drag from top to bottom, of course the vowel “ㅣ” should be entered together. It was intuitively whether it was more in line with our notions. It is probably due to reference to the examples of drawings 16-3 and 16-4. As shown in Fig. 16-10 (a), when dragged to the right, the vowel “ㅡ” is recognized. That is, [a → b] becomes [a → {ㅡ}], and the input result is recognized as “that”. The button does not necessarily have to be different for the right drag. As in Fig. 16-10 (b), even within the same button, if dragged as much as “a certain length”, the result can be recognized as an input of “ㅡ”. Also, as in Fig. 16-10 (c), since the vowel “ㅡ” in “that” is below “a”, dragging starts from the [d] button under the [a] button to the right [ㅁ] button. When dragged, it can be recognized as “he”. Similarly, when dragged within the [d] button under the [a] button as much as “a certain length”, the result can be recognized as “that”. Hereinafter, for convenience, the description will be made based on Figure 16-10 (a), and of course it can be equally applied to other cases (16-10 (b), (c), (d)). However, drawings 16-10 (a) and (b) cannot be applied simultaneously with drawings 16-10 (c) and (d), and one of them can be selectively applied (designated by the developer or selected by the user in environment settings). It is natural that you can Since the drawing of Fig. 16-10 (*) can be equally applied to the case of the vowel “ㅣ”, the description of the vowel “ㅣ” is avoided.

Next, inputting the last name becomes [a → {ㅡ} → ㅁ → ㄹ] by dragging [a → b → ㅁ → ㄹ] as shown in drawing 16-11 (a), so “ㅁ” is invalid and the drag Only the last button “ㄹ” is recognized as a valid button and “Text” is recognized. Similarly, to input “pole”, drag [a → b → m → d → a] as shown in drawing 16-11 (b), [a → {ㅡ} → m → d → a], and “ㅁ ”, “ㄹ” is invalidated, so the result is recognized as “extreme”. As suggested below, this can be done by inputting “pole” by dragging [a → b → a], unless another vowel (eg “a”) is input. As in Fig. 16-11 (c), it is obvious that even if dragged to [a → b → (outside) → a], “pole” is recognized as input. Here, “(外)” can be engraved as “other than text buttons” or “outside the keyboard skin”. Even buttons other than character buttons involved in drag character input (eg, Space, Enter, Mode, Skin, Back Space, Chinese character conversion) can be regarded as “(外)”.

Next, the four vowels “ㅗ”, “아”, “ㅜ”, and “sh” were dragged upwards according to the shape of the vowels, and then dragged to the drag start button again, “ㅗ” was recognized and dragged to the right. When is dragged to the drag start button again, “A” is recognized, and when is dragged downward and then dragged to the drag start button again, “TT” is recognized, and when is dragged to the left and then dragged to the drag start button again, “sh” is displayed. Present what is recognized.

First of all, in the case of “a”, as shown in Fig. 16-12 (a), “a” is placed on the right side of “a”. Therefore, as shown in Fig. 16-12 (b), if it is dragged to the right with [a → b → a] and then dragged again with the drag start button, it will be natural to recognize it as “a”. Similarly, as in Fig. 16-12 (c), even if the button does not change, the case of moving to the right by a predetermined length and then returning can be treated in the same way, but hereinafter, for convenience of description, Although explained in the form of a drag, it is obvious that the same can be applied to other cases. Here, as shown in Fig. 16-12 (b), it is possible to define all cases where the drag is performed with the right button and then returned to the drag start button. For example, if dragged to [a → b → all consonant buttons except “a”, “b”… → b → a], the same can be done. Since the case of "Gu" is the same as the case of "A" above, drawings are not presented separately.

In the case of “almost”, as shown in Fig. 16-13 (a), “o” is placed on the left side of “a”. Therefore, as shown in Fig. 16-13 (b), starting dragging from the [b] button on the right side of “a”, dragging in the left direction constituting “o” and then returning to the drag start button (ie, [b → a → b]) can be recognized as “giant”. However, considering the dragging habits of current users, as shown in Figs. 16-13(c), it is dragged from the [a] button to the left according to the shape of the vowel “o” and then returns to the [a] button (that is, , [a → (outside = mode button) → a]) can be recognized as “large”. Of course, as shown in Fig. 16-12(c), even if the button does not change, moving within the same button by a predetermined length and returning again can be processed in the same way. For example, in the case of Fig. 16-13 (b), it is dragged to the left by a predetermined length within the [b] button and then dragged to the right again, and in the case of Fig. 16-13 (c), the [a] button It is dragged to the left and then dragged to the right again. However, hereinafter, for convenience of explanation, it will be described with reference to FIGS. 16-13(c). The case of “high” is the same as the case of “almost”. For example, since the vowel “ㅗ” is at the bottom of “ㄱ”, the [d] button located at the bottom of the [a] button is used as the drag start button, and the dragged [d → a → d] is treated as “high” You will be able to. However, this cannot coexist in one system with inputting “high” by dragging the [a] button as the drag start button [a → (outside = upper side of the skin) → a], and the developer’s choice or user It is obvious that only one should be applied according to the setting of (if the user is allowed to select).

In the input of “ㅗ”, “ㄴ”, “ㅜ”, and “sh”, when dragged within the same button (or applicable to dragging outside the button) by a predetermined distance and then returned, rightward In the description of the input cases of “ㅡ” and “ㅣ”, the determination of whether the process has been carried out or in the downward direction is based on the dX, dY and dX, dY values of the coordinates of the maximum dragged point from the coordinates of the drag start point. You can easily judge which one is larger and which is smaller. The time of judgment may be when the drag start button is entered or when it is closest to the drag start point. As a simple example, if dX, the deviation in the X-axis direction, is within a predetermined distance (or length. In the program, it will be expressed as the number of pixels), and dY is greater than a predetermined distance and dY is a positive number, it can be recognized as a drag in the right direction. . The other cases are similar, and since they are not difficult, detailed descriptions are not made. However, for convenience of description, it is said that determining a drag in a certain direction (eg, right) is typically described with a case where the dragged button changes (eg, [a → b]), but even from the user's point of view, a predetermined Rather than judging by the length, judging by the change of the obviously dragged button is a good approach that can definitely reduce input errors. If it is judged by the predetermined length change of the dragged length (including the case of being dragged within the same button or with another button), the user thought that it would be sufficiently recognized as a drag and dragged, but in the system, it is not dragged and simply clicked ( or touch), but if you apply the rule of button change (eg [a → b]) on a screen keyboard partitioned in a grid, you can clearly recognize and drag clearly from the user's point of view. This reduces the possibility of errors by that much. The keyboard skin design of Figure 16-9 (*) is also designed in consideration of this point. As 12 character input buttons are located in the center, the user can enter without having to drag only within the button when dragging up, down, left, or right even on the most distal button (e.g. [a], [c], [ㅡ], [ㅣ] button) You can definitely drag it outside the button in .

As shown in Figure 16-14 (a), the vowel “ㅑ” in “gyah” is a shape that is lined up next to a consonant. Therefore, in accordance with the shape, as shown in Figure 16-14 (b), it is reasonable to drag from left to right and then return to the drag start button, and then drag from left to right again and then return to the drag start button. . It was dragged to [a → b → a → b → a] in Fig. 16-14 (b), which can be expressed as [a → {ㅑ}] in the form of braces. Alternatively, it can be associated with being dragged to the right and then returning to the drag start button twice (input of the vowel “a”), and inputting “a” twice in succession is recognized as “ㅑ”. This can be expressed as [a → b → a → b → a] = [a → {a+a}] = [a → {ㅑ}]. Also, it is the same even if it is dragged with [a → b → c → b→ a → b → a], but if the first drag goes to the [c] button and returns to the drag start button [a] button, “a” can be entered. Since it is said that there is, it can be thought like [a → b → c → b→ a → b → a] = [a → {a+a}] = [a → {ㅑ}]. The case of “Kyu” is the same as the case of “Gya”, so no further explanation is given.

In the case of “braff”, it corresponds to [description of “a” above: explanation of “major” above = description of “gyya”: explanation of “braff”], so detailed description is not provided either. However, since the vowel “ㅕ” is placed on the right side of the consonant “a”, as in the case of inputting “something” in Fig. 16-13 (b), the [b] button, which is the right button of the [a] button, is used as the drag start button You can also define “chaff” by dragging like [b → a → b → a → b]. If you use the [a] button as the drag start button and drag it to the left and then return it twice, it can be dragged like [a → (outside = mode) → a → (outside = mode) → a]. This can be interpreted as [a → {sh+sh}] = [a → {ㅕ}]. However, as Fig. 16-13(b) cannot coexist with Fig. 16-13(c) in one system, it is only necessary to determine and use one according to the programmer's implementation or the user's setting. The drawing is not attached separately, and the case of “bran” is the same as that of “bran”.

From the above, the two vowels “ㅡ” and “ㅣ” have a frequency of use of about 28%, and the four vowels “ㅗ”, “a”, “TT” and “sh” have a frequency of use of about 50%. and “ㅛ”, “ㅑ”, “ㅠ”, and “ㅕ” four vowels with a frequency of use of about 7%, and input 10 vowels with a frequency of use of about 84% by dragging in a consistent manner seemed to do For convenience, hereinafter, this vowel input method will be referred to as “directional drag” or “vowel input by directional drag” in contrast to the drag vowel input technology in Part 1 of the invention. Next, the meaning of the input rule by dragging of the above definition when combining vowels by continuous dragging will be explained. Inputting with continuous drag until the final support can refer to the case of applying the invention of Part 1 to the Moaki. In addition, this Part 2 invention has the meaning that it can coexist and be used in one system together with the contents of Part 1 invention.

First of all, in the input of “ㅗ”, “아”, “ㅜ”, and “sh”, it is shown that the input is performed by continuous dragging to the final support. If you type “a” by dragging in the right direction as in Moaki, when dragged [a → b → c → f → ㅣ → ㅣ], [a → {a} → invalidate buttons... → ㅣ] , it can be seen that dragging from the [a] button to the [b] button in the right direction was for inputting the vowel “a” together with “a” or “a + ㅡ = that” was dragged continuously (1 It is difficult to determine whether the process was performed for dragging to the [ㅡ] button in order to input by referring to the invention. For convenience, the vowels recognized by dragging in one direction (eg {A}) are called “implicit dragged vowels”, and the vowels recognized by continuous dragging (eg “ㅡ”) are called “explicit dragged vowels”. Let's call it ”. The solution would be something like this:

(A) simultaneously admit both implicit and explicit dragged collections if they are combinable;

(B) if the implicit and explicit dragged collections cannot be combined, only the explicit dragged collections are recognized;

(C) To disregard implicit dragged collections whenever there is an explicit dragged collection, and only accept explicit dragged collections.

. . . . . . .

etc. may be present. If the above (A) is applied, all [a → {a} + ㅣ] will be recognized and the result will be “dog”. If the explicitly dragged vowel was “ㅡ”, it becomes [a → {A} + ㅡ], but if “{A}+ㅡ” is not defined as any vowel, “that” will be recognized. (Above (B)) In the basic character input technology presented in the case of the present invention (“Basic Hangeul 2” at http://www.simplecode.net), it is defined as “a + ㅡ = ㅗ”, but this is [ㆍ It is applied when the [A] button and the [ㅡ] button, which can also be expressed as the ] button, are combined, and the combination of the implicit dragged vowel {a} and the explicit dragged vowel “ㅡ” is “ㅗ The question of whether or not to admit it as a ” is a separate issue.

As briefly reviewed above, the input of vowels by dragging in one direction causes a slightly complicated problem when combining other vowels by continuous dragging. In the case of the present invention, the vowel button is located below the consonant button, but in the form of the keyboard, the vowel button may be above the consonant button like the keyboard of Samsung Electronics, and the vowel button is to the right of the consonant button like the keyboard of LG Electronics. It may be in, and other various forms will be possible. In the present invention, only “ㅡ” and “ㅣ” are defined as one-way drag inputs, and in this case, the above (A), (B), or (C) may be applied. For example, if dragged to [a → b → consonant buttons... → ㅣ], it will be recognized as [a → {ㅡ} → ㅣ] = “gui”.

However, in the present invention, the method of inputting the implicitly dragged “A” is defined as returning to the drag start button rather than dragging in one direction. Although it was an “implicit dragged vowel” in one-way dragging, the “A” vowel can be explicitly recognized (specified) due to the process of returning to the drag start button again. For example, if it is dragged to [a → b → a → consonant buttons... → ㅣ], it is clear that the user inputs the vowel “a” through the process of returning to the “a → b → a” drag start button you know it's going to happen Therefore, the result will be [a → {a = explicitization} → ㅣ] and “dog” will be recognized. As shown in Part 1 of Invention, if the user wanted to input “ki” by continuous dragging, he should have dragged [a → consonant buttons ... → ㅣ], and dragged from the [a] button to the [b] button and then again This is because there is no reason to return to the [a] button. In other words, by dragging back to the drag start button, it has the meaning of removing the implicitness of vowel input by directional drag, and it is possible to combine vowels that can be combined by continuous dragging, so that all vowels can be input with one uninterrupted drag. You can do it. For example, [a → (outside = upper side) → a → consonant buttons... → a] = [a → {a = explicit} → a], and the result is “and”. [a → (outside = upper side) → a → consonant buttons... → a → ㅣ] = [a → {a = explicitization} → a → ㅣ] will be recognized as a “triangle”. If you see an example of inputting up to the final consonant, [a → (outside = upper side) → a → consonant buttons ... → a → (consonant buttons ...) → ㅇ] = [a → {a = clarification } → A → → ㅇ], and the result is “light”. The “ㅗ”, “a”, “sh”, and “TT” inputs presented in the present invention can be combined with the contents of the first piece of invention to input the collection of vowels by continuous dragging, and input by continuous dragging to the final support It has meaning to make it possible. (Elimination of suggestibility for vowels with a frequency of use of about 50% = explicit, continuous dragging possible) The same can be applied to “ㅛ”, “ㅑ”, “ㅠ”, and “ㅕ”.

Since the vowel “ㅡ” is input with the right drag and the vowel “ㅣ” is input with the lower drag, only the drags (right drag, lower drag) are used for vowel input with one-way drag. As suggested in Figures 15-13 (a) of Part 1 of the invention, the left drag is to input the grid sound (eg “ㅋ”) corresponding to the flat consonant (eg “ㄱ”) placed on the drag start button. can do. Similarly, the upper drag is to input a light consonant (eg, “ㄲ”) corresponding to a flat consonant (eg, “a”) disposed on the drag start button, as shown in Figure 15-3 (b) of Part 1 of the Invention. can be done with As shown in Figure 16-3, the upper drag is defined as “Shift+X” input, so it corresponds to the existing concept of use (in Pocket PC 2002 and 2003 emulators, confirm that the upper drag works even on the Korean keyboard) . However, in Figure 15-3 (b), dragging to [a → (外=upper side) → a → ㄹ → ㅅ → ㅡ] is expressed as “off” being recognized, but in the present invention, [a → (外= Since upper side) → a] is defined as “high”, to avoid conflict with this rule and to recognize “off”, as shown in Fig. 16-15 (a), [a → (外 = upper side) → not “a” Other consonant buttons... → ㅡ] should be dragged to [a → {light consonant} → ㅡ] = “off”. The result of dragging in Fig. 16-15 (b) will be "Kung". As suggested in the case of the present invention, in the case of a keyboard in which the vowel button is placed below the consonant button, even if it is a one-way drag, there is no concern about suggestibility (confusion) in the upper drag. Because dragging should start from an arbitrary consonant button and drag should almost always proceed toward the vowel button at the bottom (Part 1 invention), but something promised by the upper drag (e.g. light consonant or lattice sound) that was dragged upward Because it is clear that you dragged to input, it makes it clear that you wanted to input something that was promised.

The contents of the present invention, which combines the directional drag and the contents of the first part of the invention, may have vowel buttons displayed on the keyboard skin as in the example keyboard, but can be similarly applied even when vowel buttons pop up as in the case of Moaki. .

Next, since the case of inputting the final support by continuous dragging is similar to the case of inputting the final support by applying the first piece of invention in Moaki in the present invention, a few examples will be briefly described.

First, [a → b → a] is recognized as “a”, so to input “pole”, drag it to [a → b] as shown in Fig. 16-16(a) so that “it” is recognized, and again [a] Instead of dragging with a button, you can detour and drag the last button to become the [a] button. Next, if you drag [a → b] to input “that”, “that” is recognized. To input “root,” drag [a → b] and then use another button (or including outside the skin) in succession. After moving it, make it the [b] button with the last button of dragging. For example, it can be as shown in Fig. 16-16 (b). To input “귿”, simply drag [a → b → c], [a → {ㅡ} → c] = “귿”. That is, if you explicitly drag from the [a] button to the right adjacent button [b] button, it is recognized as a right drag ({ㅡ}).

In order to input “liver”, drag it to [a → b → a → b] as shown in Fig. 16-17 (a). This is because it can be interpreted as [a → {a} → b]. Likewise, in order to input “Gak”, as shown in Fig. 16-17 (b), drag up to [a → b → a] so that “a” is recognized, move to another button (including buttons or outside the skin), and drag the last The button should be the [a] button. The cases of “ㅛ”, “ㅑ”, “ㅠ”, and “ㅕ” are similar, so a detailed explanation is avoided.

29. Korean consonant input method using continuous pressing of the same button

Currently, the Korean input technology that is commercialized and mainly used by large domestic companies (eg Samsung Electronics) is a method using repeated pressing of consonant buttons. In the present invention, it is expressed as "repetitive selection method", and in the text input industry, it is called "multi-tap method". For convenience, the term "repetitive selection method" is used. The downside of this approach is that it is ambiguity.

In the keypad of Fig. 4-*, "ㅋ" and "ㄲ" are additionally arranged in the buttons where "a" is arranged, or logically "ㅋ" and "ㄲ" are "a" even if they are not physically arranged. It is a keypad associated with an array of buttons. And in the currently used keypad of Samsung Electronics, "a" and "ㅋ" are arranged on one button, and "ㄲ" is a keypad related to that button. In the keypad of Fig. 4-* of the present invention or the current Samsung Electronics keypad, "a" is recognized (or input) by pressing the button once, "ㅋ" is recognized by pressing it twice, and "ㅋ" is recognized by pressing the button three times. It was said that when "ㄲ" is recognized by pressing, there is an ambiguity that becomes "Kuka" when "country" is entered.

In the following, the basic properties of the iterative selection method are summarized, and a technology that improves convenience and dramatically improves ambiguity is presented. The following description is based on the current Unicode Hangul characters, and can be applied to additional Hangul characters that can be expressed in Unicode in the future.

29.1 Characteristics and Current Applications of Iterative Selection Methods

The basic and common properties of the iterative selection method (ie, the multi-tap method) are as follows. When N alphabets are arranged, the first alphabet is input when the button is pressed once, the second alphabet is input when the button is pressed twice, the third alphabet is input when the button is pressed third, ... , For the Nth pressing, the Nth alphabet is input. If N letters are arranged or associated for a button, the cycle is completed when N times are pressed. As mentioned, there is an ambiguity in not knowing which button is pressed twice, whether the second alphabet is input or the first alphabet is input twice.

In order to resolve this ambiguity, there is an application case in which a timer is set so that the input state is initialized after a certain time elapses. For example, if the corresponding button is pressed once and a predetermined time elapses, the first alphabet is confirmed, so when it is pressed again, the first alphabet is input once more.

Another method that is being used to overcome ambiguity is "circular toggle". For example, if you press the button with the three letters "a b c" once, "a" is recognized, if you press it twice, it recognizes "b", if you press it three times, it recognizes "c", and if you press it four times, it cycles. “a” is recognized again, and “b” is recognized when pressed 5 times. This means that when N+1 is pressed, only the first alphabet is recognized, and when N+2 is pressed, only the second alphabet is recognized. For convenience, this will be referred to as a “circular toggle-type iterative selection method”. If only the common basics of the repeated selection method are applied, "c" is input by pressing three times, and then "a" is additionally input after the already entered "c" if pressed one more time. . For convenience, this will be referred to as a "basic iterative selection method" or a "non-recursive iterative selection method".

Cyclic toggle type repeat selection method

(1 time pressed) → a → (2 times pressed) → b → (3 times pressed) → c (cycle end) → (4 times pressed) → a → (5 times pressed) → b → ( 6 times) → c (end of cycle) → (7 times pressed) → a → . . .

Basic repetition selection method (non-recursive repetition selection method)

(1 time pressed) → a → (2 times pressed) → b → (3 times pressed) → c (cycle end) → (4 times pressed) → ca → (5 times pressed) → cb → ( 6 times) → cc (end of cycle) → (7 times pressed) → cca → . . .

The basic iterative selection method and the circular toggle-type iterative selection method are illustrated in Fig. 17-1 to make it easier to understand.

The "(presses twice)" means that the corresponding button is "presses a total of two times", and of course means that the corresponding button is pressed twice, including "(presses once)". This is also the same in Fig. 17-1. The two exemplified above (circular toggle/non-cyclic repetitive selection method) are all operations shown in current products, and are sometimes used in combination with the timer operation. The present inventors have a view that the operation of the basic iterative selection method is more appropriate, but the circular toggle method of repeated selection is currently widely used by large companies.

29.2 Current Application in Korean

In Korean, there is a case of inputting a hard consonant (also called a "twin consonant" when morphologically called) by pressing the button assigned to the flat consonant twice. The operation in this case is an improved operation of the automata in the double-style Korean keyboard, and is also a double-style operation in a large flow. In Korean, when consonants appear in succession like "XY" among normal syllables (consonants), "X" is the base of the first letter and "Y" is the initial consonant of the second letter. It is also revealed that two consecutive consonants can be interpreted as the support of the first letter and the initial consonant of the second letter.

For example, if the "a" button is pressed once in the initial input state, "a" is input, and if it is pressed once more, "ㄲ" becomes. If you press it once more, it becomes "ㄲㄱ". This is an operation to which the basic iterative selection method is applied. If the circular toggle type repeated selection method is applied, it will be "a" instead of "ㄲㄱ". There seems to be a reason for the circular toggle method to be applied in the initial input state or initial consonant input state, but it seems undesirable to apply the cycle toggle method in the case of a series of consecutive inputs.

"이 된다. 이는 "ㄱ"이 이미 입력된 "ㄱ"과 결합하여 "ㄲ"으로 한국어 음절(자모결합글자)를 이룰 수 있으면 한국어 자모결합글자로 처리하는 것이다. 이렇게 입력된 "

" 다음에 모음(예. "ㅏ")가 입력되면 "각가"가 된다. 이 역시 기존의 2벌식 한글키보드 오토마타(이하 "2벌식 한글오토마타")에서 받침있는 글자 다음에 모음이 입력되면, 앞글자의 받침이 다음 글자의 초성자음으로 빠져나오는 동작(예. "각" 다음에 "ㅏ"가 입력되면 "가가"로 됨)과 동일하다. 만약 상기 "

" 다음에 "ㄱ"버튼이 한번 더 눌러지면 입력된 "ㄱ"이 앞글자와 결합할 수 없으므로 "

ㄱ"이 된다. 이 역시 기존의 2벌식 한글오토마타에서 앞글자와 결합할 수 없는 자음이 입력되면, 다음 글자의 초성자음으로 처리하는 것과 동일하다. 같은 논리로 상기 "

ㄱ" 다음에 "ㄱ"버튼이 한번 더 눌러지면 "

ㄲ"로 된다. 상기 "

ㄲ" 다음에 "ㄱ"버튼이 한번 더 눌러지면, 기본 반복선택방법 적용시는 "

ㄲㄱ"이 되고, 최초입력상태 또는 초성자음입력상태에서는 순환토글식 반복선택방법 적용하면, "

ㄱ"이 된다. If "A" button is pressed once in the state where "Gak" is entered, "

". This means that if "ㄱ" can be combined with already entered "ㄱ" to form a Korean syllable (consonant combination character) with "ㄲ", it will be processed as a Korean consonant combination character.

If a vowel (eg, "a") is entered after ", it becomes "Gakga". This is also the case when a vowel is entered after a supported letter in the existing 2-beol-sik Hangul keyboard automata (hereinafter "2-beol-sik Hangul automata"). It is the same as the operation in which the base of a letter escapes with the initial consonant of the next letter (eg, if "a" is entered after "gak", it becomes "ga").

" Next, if the "a" button is pressed once more, the entered "a" cannot be combined with the preceding letter, so "

This is also the same as processing it as the initial consonant of the next letter if a consonant that cannot be combined with the preceding letter is input in the existing two-beol type Hangul automata.

If the "a" button is pressed one more time after "a"

ㄲ". The above "

If the "a" button is pressed one more time after "ㄲ", when applying the basic repetition selection method, "

ㄲㄱ", and in the initial input state or initial consonant input state, if the circular toggle repeat selection method is applied, "

becomes "a".

Summarizing the case where the basic repetition selection method is applied in the form of the graph above, when "ㄲ" is assigned as the second alphabet or related to the "a" button to which "a" is assigned,

(Pressed 1 time) → ㄱ → (Pressed 2 times) → ㄲ → (Pressed 3 times) → ㄲㄱ → (Pressed 4 times) → ㄲㄲ → (Pressed 5 times) → ㄲㄲㄱ → . . .

ㄲㄱ" 사례) 이 아닌, "ㄱ" (상기 "

ㄱ" 사례) 이 되도록 할 수 있다. However, in the initial consonant state, the circular toggle repeat selection method is applied, so that "ㄲㄱ" (above "

ㄲㄱ case), not "ㄱ" (above "a")

A" case) can be made.

29.3 Improvement of Prior Application and Optimization for Korean Consonant Input

The basic system of modern Korean consonants that everyone in Korea knows is as follows.

The flat consonant "ㄱ", the hard consonant "ㄲ", and the grating consonant "ㅋ" form a group that has a strong similarity in pronunciation and form. The lattice sound "ㅋ" is a form of "ㄱ" arranged vertically, and the hard consonant sound "ㄲ" is a form of "ㄱ" arranged left and right. "P" and "C" also have strong morphological associations with the corresponding flat consonants "ㅅ" and "ㅅ", respectively, but "ㅃ" and "ㅃ" have a Slightly weaker than the morphological association.

Examples of "ㄱ", "ㄲ", and "ㅋ" below include other plain consonants (eg "ㄴ"), other grid sounds (eg "ℓ"), and other hard consonants (eg "ㄸ"). ) can be applied in the same way.

In the case of inputting "ㅋ" by pressing the "a" button twice, as in the current Korean input technology of Samsung Electronics, the phenomenon of "gukka" cannot be avoided when entering "country". However, as in the case above, when "ㄲ" is input by pressing the "a" button twice, inputting "country" does not become "gukka". Also, as pointed out, hard consonants have a stronger relationship with flat consonants than lattice consonants. In addition, as shown in the keypad of 4-* by the applicant, a concise keypad can be configured by arranging only flat consonants that can represent light consonants and grid sounds on buttons.

In the "3+ other input method" proposed by the applicant, "a" is recognized by pressing the "a" button once, "a" is recognized once more by pressing the "a" button twice, and "ㅋ" is recognized by pressing the "a" button three times. Recognized, there was a case where "ㄲ" was recognized by pressing 4 times. Until the "a" button is pressed 4 times, one cycle is formed. To input one character element "ㄲ", it must be pressed 4 times in succession. However, as suggested above, it is the core of the present invention that when the "a" button is pressed twice, sometimes it becomes "ㄲ" and sometimes it becomes "ㄱㄱ" by the 2-beol type Hangul automata. That is, in some cases, even if you do not press the "a" button up to 4 times to input "ㄲ", it is possible to press only 2 times.

기"의 "

기" 에서 "ㄲ"과 "ㄱ"이 연속하여 나온다. 기본 반복선택방법을 적용하여 "떡

기"를 입려하면 "떡보키"로 될 것이다. "

기"가 입력되는 과정을 보면, "복" → "

" → "

" → "보키" 와 같이 될 것이다. 이는 "ㄱ"버튼을 2번 누른 것이 절대적으로 "ㄲ"이 되는 것이 아니라 2벌식 한글오토마타에 의하여 때로는 "ㄲ" (예. "

")이 되기도 하고, 때로는 "ㄱㄱ" (예. "복기")이 되기 때문이기도 하다. 그러나, "

기"에서와 같이 "ㄲㄱ"이 연속하여 나오거나("ㄲ"받침 다음 "ㄱ"초성자음), "ㄱㄲ"이 연속하여 나오는 경우("ㄱ"받침 다음 "ㄲ"초성)는 "극히" 드물다. "ㄲㄱ"와 같이 "받침+초성자음"이 나오는 경우는 0.013% 이고, "ㄱㄲ"과 같이 "받침+초성자음"이 나오는 경우는 0.038% 이다. 다른 평자음(예. "ㄷ")과 경자음(예. "ㄸ")의 경우도 유사하므로, 사실상 거의 무시할 수 있는 수준이다. If "a" and "ㄲ" (by pressing twice) appear in succession, or "ㄲ" (by pressing twice) and "a" appear in succession, "ㄱㄲ", "ㄲㄱ", "ㅋ" has the same input value, so there may be ambiguity. For example, "rice cake

of "ki"

"ㄲ" and "ㄱ" appear in succession in "ki". By applying the basic repetitive selection method, "tteok"

If you try to wear "ki", you will become "tteokboki"."

If you look at the process of inputting "ki", "bok" → "

" → "

" → "vokey". This means that pressing the "a" button twice does not absolutely become "ㄲ", but sometimes "ㄲ" (eg "

"), and sometimes it becomes "ㄱㄱ" (eg "revival"). However, "

As in "ki", it is "extremely" rare for "ㄲㄱ" to appear consecutively ("ㄲ" ending followed by "ㄱ" initial consonant) or "ㄱㄲ" to appear consecutively ("ㄱ" ending followed by "ㄲ" initial consonant). 0.013% of cases in which "support + initial consonant" occurs, such as "ㄲㄱ", and 0.038% in the case of "support + initial consonant", such as "ㄱㄲ". The case of hard consonants (eg "ㄸ") is similar, so it is practically negligible.

기"의 "ㄲ"을 "ㄱ"버튼 4번 눌러짐으로 입력하면 모호성없이 입력할 수 있다. 이 역우, 기본 반복선택방법으로 "

기"가 입력되는 과정을 보면, "복" → "

" → "

" → "

" → "

ㄱ" → "

기" 가 된다. "ㄱ"버튼 2번 누름에 의한 "ㄲ"은 다음 입력(예. 모음입력)에 따라 "ㄱㄱ"으로 될 수 있지만, "ㄱ"버튼 4번 눌러짐이 항상 "ㄲ"이 되므로 "

기"의 경우는 모호성없는 입력이 가능하다. "오뚜기"의 경우도 "ㄷ"버튼 2번 눌러짐으로 "ㄸ"을 입력하면, "

두기"와 같이 된다. 즉, "오뚜기=

두기"인 모호성이 있는 것이다. 그러나 "ㄷ"버튼 4번 눌러짐으로 "ㄸ"을 입력하면 모호성없이 "오뚜기"로 올바르게 입력할 수 있다. "오뚜기"를 입력하기 위하여 "ㄷ"버튼을 눌러 "오ㄸ"을 입력하는 과정과 "가까이"를 입력하기 위하여 "

"을 입력하는 과정을 보이면 다음과 같다. 아래에서 모음 "ㅜ" 및 "ㅏ"의 입력에는 본 발명에서 제시한 모음입력기술 또는 다른 어떠한 모음입력기술이 적용될 수 있으며, 이하 유사한 경우에서도 같다.In addition, since the technology in which "ㄲ" is input by pressing 4 times is applied,

If you enter "ㄲ" of "Gi" by pressing the "a" button 4 times, you can enter it without ambiguity.

If you look at the process of inputting "ki", "bok" → "

" → "

" → "

" → "

a" → "

"ㄲ" by pressing the "a" button twice can become "ㄱㄱ" according to the next input (eg vowel input), but pressing the "a" button 4 times always results in "ㄲ" so "

In the case of "Ottogi", input without ambiguity is possible. In the case of "Ottogi", if you enter "ㄸ" by pressing the "c" button twice,

It becomes like "Doogi". In other words, "Ottogi =

However, if "ㄸ" is entered by pressing the "c" button 4 times, "Ottogi" can be entered correctly without ambiguity. To enter "Ottogi", press the "c" button to " The process of entering "oh" and "near" to enter "

The process of inputting " is as follows. The vowel input technology proposed in the present invention or any other vowel input technology may be applied to the input of the vowels "TT" and "A" below, and the same applies in similar cases below.

→

ㄷ →

→ 오ㄸ →("ㅜ"입력)→ 오뚜Oh →

→

c →

→ Oh ㄸ → (Enter "TT") → Odu

→

→

→("ㅏ"입력)→ 가까Go → Gak →

→

→

→(enter "a")→ close

" 다음에 "ㅏ"가 입력되면 "각가"가 되지만, "ㄱ"버튼 4번 누름은 항상 절대적으로 "ㄲ"이 된다고 하였으므로, "ㄱ"버튼 4번 누름 다음에 "ㅏ"가 입력되면 "가까"가 된다. "Entered by pressing the "a" button twice

If "a" is entered after ", it becomes "gagga", but it is said that pressing the "a" button 4 times is always absolutely "ㄲ", so if "a" is entered after pressing the "a" button 4 times, "near""It becomes

Even when "ㄲ" is input by pressing the "a" button four times, there is ambiguity because "ㄱㅋ", "ㅋㄱ", and "ㄲ" have the same input value. But in practice, in our words, this case is also "extremely" rare. The case of "support + initial consonant" such as "ㄱㅋ" is 0.013%, and the case of "support + initial consonant" such as "ㅋㅋ" is investigated as 0%. Other flat consonants (eg "c") and lattice consonants (eg "t") are similar, so they are virtually negligible.

The change when the "a" button is continuously pressed by applying the basic repeated selection method is as follows.

ㄱ → ㄲ or ㄱㄱ → ㅋ → ㄲ (end of cycle) → ㄲㄱ → ㄲㄱㄱ or ㄲㄲ → ㄲㅋ → ㄲㄲ (end of cycle) → ㄲㄲㄱ → . . .

Applying the basic repetitive selection method, the change when the "a" button is pressed consecutively after the letter "a" is as follows.

→

→

(사이클 종료) →

ㄱ →

ㄲ →

ㅋ →

ㄲ (사이클 종료) → . . .Go → Gak →

→

→

(end of cycle) →

a →

ㄲ →

ㅋ →

ㄲ (end of cycle) → . . .

"이고, 8번 눌러진 상태는 "

ㄲ"이 된다. 4번 눌러지고 나면 입력규칙 사이클이 종료되었으므로 기 입력된 글자(예."

")는 완성되고, 5번째 눌러짐은 다시 1번 눌러짐(새로 "ㄱ"입력)과 동일한 효과를 내게된다.The state in which the "a" button is pressed 4 times after "a" is "

", and the state pressed 8 times is "

ㄲ". After being pressed 4 times, the input rule cycle is over, so the previously entered character (eg. "

") is completed, and the fifth press produces the same effect as pressing the first time (new "a" input).

ㄲ" 상태에서 한번 더 "ㄱ"버튼이 눌러지면, 다음의 2가지로 처리될 수 있다. 기본 반복선택방법이 적용되면, "

ㄲㄱ"이 될 것이다. 사이클 종료후, 눌러진 "ㄱ"버튼이 한번 더 눌러졌을 때, 입력중인 글자가 초성자음 상태에서는 순환토글식 반복선택방법이 적용된다면, "

ㄱ"이 될 것이다. 이 상태에서 "ㄱ"버튼이 한번 더 눌러진다면 "

ㄲ"이 될 것이다. 상기 기본 반복선택방법 적용의 경우, 그리고 사이클종료후 초성자음일 때 순환토글식 반복선택방법이 적용시의 경우를 조금 더 이해하기 쉽게 그림으로 나타내면 도면17-2와 같다. 도면17-2에서, 4번 눌러졌을 때의 "ㄲ"은 1사이클이 완료되었을 때의 결과이고, 8번 눌러졌을 때의 "ㄲㄲ"은 2사이클이 완료되었을 때의 결과인 것이다.In the transition state from the input of the support to the initial consonant, it is preferable that the circular toggle method of repeated selection is not applied. of the last "

If the "a" button is pressed once again in the "ㄲ" state, the following two processes can be processed. If the basic repetition selection method is applied, "

After the cycle ends, when the pressed "a" button is pressed once more, if the circular toggle method of repeated selection is applied in the initial consonant state of the letter being input, "

In this state, if the "a" button is pressed once more, "

ㄲ". In the case of applying the basic repetition selection method and in the case of application of the circular toggle repetition selection method when the initial consonant is a consonant after the end of the cycle, the figure is shown in Fig. 17-2 to make it easier to understand. In Fig. 17-2, "ㄲ" when pressed four times is the result when one cycle is completed, and "ㄲㄲ" when pressed eight times is the result when two cycles are completed.

Among Korean support (final consonant), there is a double support (deep support) such as "ㄺ". In the form of a double support "xy", "x" can be combined with "ㄱ" to form "xy". The operation in this case is also the same. For example, if you try to enter "ㄲ" by pressing the "a" button twice to enter "know", it becomes "go to know". However, it is easily solved by pressing the "a" button 4 times so that it always becomes "ㄲ". The case where the "a" button is pressed after "Al" is as follows, and can be applied to other similar cases as well. When pressed 2 times, it becomes "ㄱㄱ" (eg. "ㄴㄱ"), when pressed 3 times, it becomes "ㅋ" (eg, "Alㅋ"), and when pressed 4 times, it always produces "ㄲ" (eg. " It will become known"). In the following, the vowel input technology proposed in the present invention or any other vowel input technology may be applied to the input of vowel "a", and the same applies in similar cases below.

Al → Yes → Yes → Yes → No

In our Korean language, there are many cases of "ㅅ" consonant followed by "ㅅ" consonant (i.e., "ㅆㅅ"), such as "~ I did" and "~ I was", but conversely, "ㅅ" consonant followed by "ㅆ" consonant Rarely does this come out. When applying the basic repetition selection method, it is natural that "ㅅ" becomes "ㅅ" when the "ㅅ" button is pressed after the "ㅆ" base. This is because only "ㅅ" and "ㅆ" are arranged or related to the "ㅅ" button. The keypad of Fig. 4-* is also the same.

수" 와 같이 된다. 이 경우도 "ㅅ"버튼 4번 누름으로 "ㅆ"을 입력하면 간단히 해결되며, 동작은 다음과 같다. "얼" 다음에 "ㅅ"버튼이 눌러질 때의 변화이다. 2번 눌러졌을 때 "ㅅㅅ" (예. "

ㅅ") 이 되고, 3번 눌러졌을 때 "ㅅㅆ" (예. "

ㅆ") 이 되고, 4번 눌러졌을 때 절대적으로 "ㅆ"이 되므로 "얼ㅆ"가 된다. 아래에서 모음 "ㅜ"의 입력에는 본 발명에서 제시한 모음입력기술 또는 다른 어떠한 모음입력기술이 적용될 수 있으며, 이하 유사한 경우에서도 같다.Among the double support "xy", when "ㅅ" comes to the position of "y", there are "ㄳ", "ㄽ", and "ㅄ". In the case of "ㄱㅆ", "ㄹㅆ", and "ㄴㅆ", it is difficult to input "ㅆ" by simply pressing the "ㅅ" button twice. For example, in the case of "Ulsu", if you try to enter "ㅆ" by pressing the "ㅅ" button twice,

In this case, it is simply solved by pressing the "ㅅ" button 4 times and entering "ㅆ", and the operation is as follows. This is the change when the "ㅅ" button is pressed after "Eol". When pressed twice, "ㅅㅅ" (eg. "

ㅅ"), and when pressed 3 times, "ㅅㅆ" (eg. "

ㅆ"), and when it is pressed 4 times, it absolutely becomes "ㅆ", so it becomes "Eol ㅆ". Below, the vowel input technology proposed in the present invention or any other vowel input technology will be applied to the input of the vowel "TT". It can be, and the same applies in similar cases below.

→

ㅅ →

ㅆ → 얼ㅆ →("ㅜ"입력)→ 얼쑤Earl →

→

ㅅ →

ㅆ → ㅆ → (enter "TT") → ulsu

There are cases where "ㅆ" comes out as a first consonant after a vowel. For example, in the case of "assa", if "ㅆ" is input with the "ㅅ" button 2 times, it becomes "assa" by the Hangul automata. The right arrow (→) below means that the "ㅅ" button is pressed. Any vowel input method (including other input methods not suggested by the applicant) can be applied to the input of the vowel "A". For example, it may be input as "ㅣㆍ" as before, or as suggested in the previous application, it may be input by pressing the "ㆍ" button once. This is the change when the "ㅅ" button is pressed after "Ah".

Ah → Oops → Got → (Input "A") → Assa

For consistent input rules and input without ambiguity, pressing the "ㅅ" button 4 times can be treated as "ㅆ". "ㅆ" by pressing 2 times can be changed to "ㅅㅅ" according to the next input (eg vowel input), but "ㅆ" by pressing 4 times is absolutely applied, as in the case of "ㄲ". Pressing 3 times becomes "ㅆㅅ" as described above. The input process of "assa" by pressing the "ㅅ" button 4 times is as follows.

Ah → Ah → Yes → Yes → Yes → (Input "a") → Yes

If there is ambiguity (eg, enter "ㄱㅋ" as the base and initial consonant), the way to overcome the ambiguity is to end the input token by applying a timer (check no input for a certain period of time), press the space button, or right There is a method such as ending an input token by pressing an arrow button. To input "ㄱㅋ" (with support and initial consonant), after inputting "ㄱ", press the right arrow button to disconnect the input token, and then press the "ㄱ" button three times to input "ㅋ". Here is a list of cases where there is ambiguity:

ah 0.013 lol 0 ㄲ 0.038 haha 0 dt 0 td 0.064 dㄸ 0.002 TT 0 oops 0.013 Pff 0.004 ㅃ 0.001 ㅍ ㅍ 0.001 ss 0.003 jch 0.059 chj 0.002 xx 0 congrats 0.003 Sum 0.203

In Korea, the ratio of "support + initial consonant" and "neutral vowel + initial consonant" is about half and half. In the present invention, there is no ambiguity in the case of "neutral vowel + leading consonant". This is because a hard consonant (eg, "ㄲ") can be input by pressing the flat consonant (eg, "a" button) 4 times. Therefore, the sum of 0.2% is 0.1% for the entire case. This can be seen as meaning that ambiguity occurs once in 1000 characters, and the Korean input technology presented in the keypad of Figure 4-* of the present invention takes about 3.5 strokes per character, so if you press about 3500 strokes, ambiguity occurs once. . In fact, it can be seen that there is almost no ambiguity. The reason for this low ambiguity is also because there are very few consecutive consonants with similar phonetic values (eg "ㄱ" and "ㅋ") in Korean Hangul.

기"를 입력한 것이 "보키"로 되지 않음. "오뚜기"를 입력한 것이 "

두기"로 되지 않음)가 있다. The above result is 4 to input "ㄲ" in one case of "3 + other input method" (press once for "a", press 3 times for "ㅋ", press 4 times for "ㄲ") of the applicant's previous application. Pressing twice in succession can be somewhat boring, but in most cases, pressing the "a" button twice has the effect of allowing "ㄲ" to be input. Cognitively, "ㄲ" is in the form of "ㄱ" overlapping left and right, so it is possible to input "ㄲ" by pressing the "ㄱ" button twice, which is a method that can match the sentiment of Korean users who write horizontally. There is one effect. In addition, the above results show that "ㄲ" is recognized by pressing the "a" button twice, and "ㄲ" is input by pressing the "a" button four times in the previous application of the applicant, in which "ㅋ" is recognized by pressing the "a" button three times, greatly reducing ambiguity. reduced effect (e.g. "

Entering "ki" does not turn into "voki". Entering "Ottogi" does not result in "vokey"

It does not become "leave").

In the case of continuous pressing of the flat consonant button, it was pointed out that the basic repeated selection method is more suitable than the circular toggle method of repeated selection when inputting from the base to the initial consonant. However, it was mentioned that when the cycle is completed, the circular toggle method of repeated selection can be applied. Furthermore, if the hard consonant recognized by pressing the flat consonant button twice is a "primary consonant", it may not be necessary to process the pressed four times as a hard consonant again. That is, pressing the "a" button once is recognized as "a", pressing it twice is recognized as "ㄲ" or "ㄱㄱ", and pressing it three times is recognized as "ㅋ". If "ㄲ" recognized when pressed twice by the 2-beol-sik Hangul automata was an initial consonant, the cycle is completed by being pressed 3 times, and when pressed again, the recognized "ㅋ" and "ㅋ ㄱ" (default When the repeated selection method is applied) or "a" (when the circular toggle type repeated selection method is applied). If this is expressed in a picture, it becomes as shown in Figure 17-3. In Figure 17-3, a graph (or diagram) format and a flowchart format are integrated and expressed for convenience. However, for the consistency of the input rule, pressing 4 times can always be treated as "ㄲ" (ie, a hard consonant), and in the opinion of the present inventor, it is always a hard consonant to press 4 times consistently in the input rule. It looks desirable.

The above case was a case where flat consonants were used as basic consonants, and hard consonants and lattice consonants were also input. The above case can be applied to the keypad shown in Figure 4-* and also to other types of keypads not suggested by the applicant. In addition, the above case may be applied with the vowel input method proposed by the applicant in the previous application and the present invention, and may be applied with other vowel input methods that currently exist or will appear in the future.

It can be applied simultaneously with the control processing method using the vowel button (eg, "ㅋ = ㄱㅡㅡ", "ㄲ = ㄱㅣㅣ"), which is a technology that can be input without any ambiguity, presented in the applicant's previous application. When inputting lattice sounds and light consonants, if the control processing method using the vowel button (eg, "ㅋ = ㄱㅡㅡ", "ㄲ = ㄱㅣㅣ") presented in the applicant's previous application is used in combination, the ambiguity There will be fewer. Based on the keypad of Fig. 4-*, the input of "ㅎ" was not suggested, but the earlier application explained that "ㅎ" could be separated as a separate button. The key point of the present invention is to show that it is possible to input with "extremely" little ambiguity in a simple keypad (eg Fig. 4-*) by regularly using the relationship between flat consonants, lattice consonants, and hard consonants. This is a key point that can be applied “commonly” to any modified case as well as to the keypad of FIG. 4-* of the present invention. The input of "ㅎ" (or "ㄹ"), which was expressed as a dropped consonant in the previous application of the applicant, can be applied to the input of a lattice sound or a light consonant as described below, and will be separately mentioned below.

The above input technology, which is a key matter of the present invention, is a technology of "Basic Hangeul 3" and will be released as a product through the site http://www.simplecode.net.

29.4 Optimization of the processing of dropped consonants (eg "ㅎ") by repeated pressing

Next, additional examples of transformation are presented. It is assumed that "ㅎ" is additionally arranged or related to the "ㅇ" button. In the case of the earlier application, "ㅎ" is regarded as a modified alphabet (lattice consonant or hard consonant) of "ㅇ". In the previous application, it corresponds to the case of treating "ㅎ" as a modified alphabet (lattice consonant or hard consonant) of "ㅇ". If the basic repetition selection method is applied as the "ㅇ" button is pressed, it will be as follows.

ㅇ → ㅇㅇ → ㅎ (end of cycle) → ㅎㅇ → ㅎㅇㅇ → haha (end of cycle) → ㅎㅇ → . . .

In modern Korean, there is no "ssang-yi-eung", but if you can input "ssang-yi-eung", an archaic character element, the "ㅇ" button pressed twice by the double-beol type Hangul automata will be "ssang-i-eung" in some cases.

In addition, as in the case presented in the previous application, "ㄴ" and "ㄹ" may be arranged or associated with one button as a group to be processed. In this case, the processing of "ㄴ" and "ㄹ" can be processed similarly to the case of "ㅇ" and "ㅎ". If "ㄹ" is regarded as a modified alphabet of "ㄴ" (i.e., a lattice sound or a light consonant) and processed, 9 basic consonants can be assigned to 9 buttons from [1] to [9], so "ㅇ" and "ㅎ" may be assigned to different buttons.

If "ㅇ" and "ㅎ" are input by the basic repetitive selection method exemplified above, including the case where "ㅇ" and "ㅎ" appear consecutively, the above suggested (once in about 1000 characters or about 3500 Once in a while) there is more ambiguity.

However, it can be applied simultaneously with the control processing method using the vowel button (eg "ㅋ = ㄱㅡㅡ", "ㄲ = ㄱㅣㅣ"), which is a technology that can be input without any ambiguity, presented in the applicant's previous application. If "ㅎ" is always entered as "ㅎ = ㅇㅡㅡ" or "ㅎ = ㆍㅡㅡ" presented in the previous application of the applicant, the above method of repeated pressing is used for input of all grid sounds and light consonants Even so, ambiguity will occur once in about 1000 characters (about 3500 strokes). The same applies to the case where the earlier application requires input as "ㅎ = ㅡㅡ". Also, even when entering "ㅋ", which is not a normal word but is widely used in the younger generation, it is possible to input without ambiguity by entering "ㅋ" with "ㄱㅡㅡ". When inputting lattice sounds and light consonants, if the control processing method using the vowel button (eg, "ㅋ = ㄱㅡㅡ", "ㄲ = ㄱㅣㅣ") presented in the applicant's previous application is used in combination, the ambiguity There will be fewer.

Next, one of the contents presented in the previous application of the applicant, inputting "ㅎ" by pressing the "ㆍ" button (assigned to the number button [0] button) 3 times can be applied. As mentioned in the previous application, this has the meaning of providing input rules consistent with inputting lattice sounds by pressing the flat consonant button 3 times, and inputting "ㅎ" related to the "ㆍ" button by pressing the "ㆍ" button. . If the "ㆍ" button is pressed three times after the consonant and "ㅎ" is input, there is no ambiguity, and there is ambiguity as suggested in the previous application, but it is very small. First, a brief look at the case where the vowel input method used by Samsung Electronics is applied is as follows. In cases where there may be ambiguity, the vowel "A" (input as "ㅣㆍ" in the conventional method), then "ㅑ", then "TT", then "ㅠ" followed by "ㅎ" (support or initial consonant of the next letter) ), there may be ambiguity. If the basic iterative selection method is applied, it will be as follows. The case where the "ㆍ" button is continuously pressed after "group", "that", etc. is as follows. The right arrow "→" below is expressed including the pressing of the "ㆍ" button, and the same is true below.

Ki → Ga → Gya → Gyaㆍ →

He → Gu → Gyu → Gyuㆍ →

If only the basic iterative selection method is applied without transforming the automata, if "ㅎ" comes after "ga", "gyya", "gu", "gyu", etc., "ㅎ = ㅇㅡ ㅡ" or "ㅎ = ㆍㅡㅡ" can be used. The case where "ㅎ" comes next as a support after "아", "ㅑ", "ㅜ", and "ㅠ" is 0.022%, 0.001%, 0%, and 0%, respectively. The cases where "ㅎ" comes as the initial consonant after "a", "ㅑ", "ㅜ", and "ㅠ" are 0.563%, 0.02%, 0.4%, and 0.094%, respectively. Among them, it is a negligible level, except for the case where "ㅎ" comes as the initial consonant after "A". Applying the basic repetitive selection method to form Korean syllables as much as possible, it becomes as follows.

→ 갛 →

→

ㆍ(or 가ㅎㆍ) →

ㆍㆍ(or 갸ㅎㆍㆍ)Ki → Ga → Gya → Gyaㆍ →

→ red →

→

ㆍ(or 가ㅎㆍ) →

ㆍㆍ(or Gyahehㆍㆍ)

→

→

→

ㆍ(or 규ㅎㆍ) →

ㆍㆍ(or 규ㅎㆍㆍ)He → Gu → Gyu → Gyuㆍ →

→

→

→

ㆍ(or Kyuheㆍ) →

ㆍㆍ (or Kyu heh ㆍ ㆍ)

"을 입력하고 싶었다면, 상기 "갸" 다음에 "ㆍ"버튼의 연속누름을 종료해 주는 수단(예. 우측이동버튼 또는 스페이스버튼 등등. 이하 대표하여 "우이동버튼"으로 표현)을 누른 후, "ㆍ"버튼 3번 누름으로써 "

"을 입력하도록 할 수 있다. 또는 타이머에 의하여 "갸" 입력후 일정시간(예. 0.2초)이 경과하면 "ㆍ"버튼 연속누름에 의한 처리가 종료되는 것으로 하여, "갸" 다음 0.2초 경과후 "ㆍ"버튼 3번 눌러짐으로 "

"을 입력할 수 있다. 상기 "갛" 상태에서 "가호"를 입력하기 위하여 "ㆍ"버튼을 한번 더 누르면 "

"이 되는데, 이 경우도 "갛" 상태에서 상기 우이동버튼 또는 상기 타이머에 의하여 "갛"을 확정한 상태에서 "ㆍ"버튼과 "ㅡ"버튼을 순차적으로 눌러 "가호"를 입력할 수 있다. In the case of the above case, if the input value that is input following the middle of the input is the "ㆍ" button (eg, "symbol = gah"), there may be ambiguity. However, the cases where the neutral vowels "ㅑ" and "ㅠ" followed by the consonant "ㅎ" and the initial consonant "ㅎ" occur at 0.001%, 0%, 0.02%, and 0.094%, respectively, which are almost negligible. As described above, there may be ambiguity when the "ㆍ" button is continuously pressed.

If you wanted to input ", after pressing the means for ending the continuous pressing of the "ㆍ" button after the "Kya" (e.g., the right movement button or the space button, etc., hereinafter represented by the "right movement button"), By pressing the "ㆍ" button 3 times, "

" can be entered. Or, if a certain amount of time (eg 0.2 seconds) elapses after entering "gyya" by the timer, the process by continuously pressing the "ㆍ" button ends, and 0.2 seconds after "gyah" After that, by pressing the "ㆍ" button 3 times, "

" can be input. If you press the "ㆍ" button once more to input "protective protection" in the "red" state, "

In this case, "Red" can be input by sequentially pressing the "ㆍ" button and the "ㅡ" button in the state where "Red" is determined by the right movement button or the timer in the "Red" state.

In the past, since the input character is confirmed by the right-move button or the timer, when the right-move button is pressed in the “gyya” state, “gyah” is confirmed, and when the “ㆍ” button is pressed three times and “ㅎ” is input , It became "Gyahah". However, in the above case, it plays a role of breaking the automata by continuously pressing the “ㆍ” button. As in the past, completely confirming the input character (eg "gyya" or "red") is to press the right button twice or for a certain period of time by the timer (eg, a value greater than 0.2 seconds is 0.3 seconds). ) can be treated as elapsed. In other words, if there is ambiguity by the "ㆍ" button, the token of continuous pressing of the "ㆍ" button is primary (eg pressing the right button once or a timer for 0.2 seconds) by conventional means (e.g. right-move button, timer). It can be treated as cut off and confirmed as a secondary (e.g., pressing the right movement button one more time or a timer with a value greater than 0.2 seconds) that has been previously entered. This can be equally applied to the case below.

Another method is to terminate the continuous pressing token of the "ㆍ" button for consonant input (initialize the logic of continuous pressing of the "ㆍ" button for consonant input) when the delete button is pressed during continuous pressing of the "ㆍ" button. can be done with Vowel input can operate in the same way as before. For example, when the delete button is pressed in the "red" state, "ㅎ", which is a character element unit or cognitive unit (described below), is deleted and becomes "ga". Since the delete button was pressed once, the process of continuous pressing of the existing “ㆍ” button ended, and in this state, if the “ㆍ” button was pressed three times again, it became “red”. This can also be applied equally to the cases below. The advantage of this method is that when a character the user does not want is displayed, the user presses the delete button to correct it, but the unwanted character does not appear again according to the logic before pressing the delete button, and the desired character can be input.

Also, since consonants (supporting consonants or leading consonants) rarely appear after "ㅑ" or "ㅠ", the following modified automata can be applied.

→ 갛 → 갛ㆍ(or 가ㅎㆍ) → 갛ㆍㆍ(or 가ㅎㆍㆍ) →

ㆍㆍ(or 갸ㅎㆍㆍ)Ki → Ga → Gya → Gyaㆍ →

→ Red → Redㆍ (or Gaㅎㆍ) → Redㆍㆍ(or Gaㅎㆍㆍ) →

ㆍㆍ(or Gyahehㆍㆍ)

→

→

ㆍ(or 구ㅎㆍ) →

ㆍㆍ(or 구ㅎㆍㆍ) →

ㆍㆍ(or 규ㅎㆍㆍ)He → Gu → Gyu → Gyuㆍ →

→

→

ㆍ (or Guheh ㆍ) →

ㆍㆍ(or Guㅎㆍㆍ) →

ㆍㆍ (or Kyu heh ㆍ ㆍ)

In the previous application, a technique of inputting the vowel "A" by pressing the "ㆍ" button once was presented. In addition, a technique of inputting "o" by pressing the "ㆍ" button twice has been proposed. As shown in Fig. 4-*, instead of the "ㆍ" button, a button reminiscent of the vowel "A" is used (e.g., a button shaped like "A" button or a combination of "A" and the number "0", etc.) The case is the same. Hereinafter, for convenience, a "•" button will be described. In this case, one of the cases where the basic iterative selection method is applied is as follows. Also, the right arrow (→) below was expressed including the pressing of the "ㆍ" button.

ㄱ → 가 → Geo → ㄱㅎ → Red → か

The above case shows that the "ㆍ" button being input is processed as forming Korean syllables at the maximum, so that the input of "ㅎ" in "red", "か", etc. can be processed by pressing the "ㆍ" button 3 times. . When the "ㆍ" button is pressed after "group" and "that", the modified automata can also be applied as suggested above.

→ 갛 → 가하 → 가허 → 갸허Ki → Go → Gya → Gyaa →

→ Red → Gaha → Gaheo → Gyaheo

→

→ 구하 → 구허 → 규허That → Gu → Gyu → Gyu →

→

→ Guha → Guheo → Kyuheo

Here, "red" (or "gaㅎ" included) can use the technique presented in "a → ga → geo → a heh → red → gg". In the case of "a", which is a frequently used vowel of more than 22%, it can be entered by pressing the "ㆍ" button once, but there are not many users who dare to input it with two strokes like "ㅣㆍ". Therefore, transformation automata can be applied as follows.

→ 기하 → 기허 → 가허 → 갸허Ki → Go → Gya → Gyaa →

→ Giheo → Giheo → Gaheo → Gyaheo

If the user wanted to input "gaho", press the delete button once in the "gaheo" state so that it becomes "gaㅎ" (or "red"), and again according to the predetermined vowel input method (eg "ㆍㅡ") You can enter "gaho" by entering "ㅗ". As suggested above, by pressing the delete button, the continuous input processing logic of the "•" button for input of the dropped consonant (eg, "ㅎ") may be initialized. To become "Ga ㅎ" by pressing the delete button in the "Permit" state, you can refer to the "Improvement of the delete button process" presented below. If the user wants to input a "symbol", in the "geometry" state, according to the vowel input method of the previous application, the word "symbol" can be input by pressing the "ㅡ" button.

29.5 Optimization of Input Technology Using Iterative Selection Methods

In our modern Korean Unicode system, there are five hard consonants (double consonants): "ㄲ", "ㄸ", "ㅃ", "ㅆ", and "ㅆ". It's just "ㅆ". The pair consonants "ㄸ", "ㅃ", and "ㅃ" that cannot be final consonants are called "non-final consonants" for convenience, and the corresponding plain consonants "ㄴ", "ㅅ", and "ㅅ" are called "pair consonants" for convenience. It will be called a flat consonant without consonant formation."

In the above "29.3 Improvement of previous application and optimization of Korean consonant input", the applicant's previous application was improved, and as the flat consonant button (eg, [a] button) is pressed, "a → ㄲ or ㄱㄱ → ㅋ → ㄲ → . . ." It has been suggested that input as . What is important in the above is that when the [a] button is pressed twice, it is recognized as a double consonant (light consonant), and when the next vowel is input, it becomes two plain consonants (i.e., "ㄱㄱ"), so [a] button 2 The consonant when pressed once can be seen as a temporary consonant.

As mentioned, in the previous application of the applicant, it was suggested that "a → ㄲ → ㅋ" is input according to the pressing of the flat consonant button (eg, [a] button). By improving this, as suggested in "29.3 Improvement of previous application and optimization of Korean consonant input", the double consonant (eg "ㄲ") when the [a] button is pressed twice is changed according to the next input. It can be treated as a temporary double consonant that can also be divided into "ㄱㄱ".

"이 되지만 이 상태에서 모음(예. "ㅏ")이 입력되면 "각가" 가 되는 것이다. "

"상태에서 "ㄱ"이 입력되면 "

"이 되고, "

"상태에서 "ㄴ"이 입력되면 "

ㄴ"이 된다. 평자음버튼의 2번 눌러짐이 쌍자음으로 되는 것은 2벌식 한글조합규칙에 따라, 동일한 평자음이 2번 입력된 것을 쌍자음으로 처리할 수 있으면 쌍자음으로 인식하고, 2개의 평자음으로 처리할 수 있으면 2개의 평자음으로 인식하는 것이다. 상기 내용을 다시 정리하면, 평자음버튼의 연속 눌러짐에 따라 적합한 한국어 자모결합규칙(한글오토마타)에 의하여 적합한 자모결합글자가 형성되는 한에서 "평자음 → 쌍자음 또는 2개의 평자음 → 격자음"으로 인식되는 것을 의미한다. That is, as the flat consonant button is pressed, it becomes like "a → ㄲ or ㄱㄱ → ㅋ". As explained, if the [a] button is pressed twice after "A", "

", but if a vowel (eg "A") is entered in this state, it becomes "gakga". "

"If "a" is entered in the status "

"becoming"

"If "b" is entered in the status "

b". Pressing the flat consonant button twice becomes a double consonant according to the 2 beolsik Hangul combination rule, if the same flat consonant can be treated as a double consonant, it is recognized as a double consonant, and 2 If it can be processed as two plain consonants, it is recognized as two plain consonants. If the above contents are rearranged, suitable consonant combination letters are formed according to the appropriate Korean consonant combination rules (Hangul automata) according to the continuous pressing of the flat consonant button. It means that it is recognized as "a flat consonant → a double consonant or two flat consonants → a lattice sound" as long as it is possible.

The ambiguity of processing as above is as follows. First of all, since there is an ambiguity of 0.1% suggested above, a case where a pair consonant comes as an initial consonant after a neutral vowel is added as follows. This is because the absolute input of double consonants is excluded by pressing the flat consonant button 4 times.

Vowel + ㄲ Vowel + ㄸ Vowel + ㅃ Vowel + ㅆ Vowel + ㅔ Sum 0.856 0.44 0.144 0.219 0.169 1.828

Since the above is the case where the initial consonant comes after the neutral vowel, it is the frequency of occurrence in the case where there is no final consonant. In our Korean language, about half of the letters (54% to be exact) end with a neutral vowel without a final consonant, and about half (46% to be exact) of letters with a final consonant. To be precise, it should be considered as a proportion of 54%, but about half and half, and it can be said that there is ambiguity of 0.9%, which is about half of the above 1.8%. When combined with the above 0.1% ambiguity, it can be seen that there is about 1% ambiguity.

If the simple repetitive selection method is applied instead of the circular toggle repeat selection method, "a → ㄲ or ㄱㄱ → ㅋ (cycle end) → ㅋ ㅋ → ㅋ ㄲ → ㅋ → . ." becomes like In the "XY" form, if "X" is a final consonant and "Y" is a leading consonant, the circular toggle repeat selection method may be applied only when the input state is the leading consonant state. For example, "a → ㄲ or ㄱㄱ → ㅋ → ㅋa → ㅋㄲ → ㅋㅋ → ㅋㄱ → ㅋㄲ → ㅋ . ." becomes like Currently, phrases such as "ㅋ" or "ㅋ" are often used among young people, so even if "X" is in the initial consonant state, it may be better to apply a simple repetitive selection method rather than a circular toggle repetitive selection method.

ㄷ"와 같이 되는 것이다. ("오" 아래 종성자음으로 "ㄸ"이 올 수 없으므로) 즉, 중성모음까지 입력된 상태에서 쌍자음종성불가 평자음이 2번 연속하여 입력되면 자연히 1번째 입력은 종성자음으로, 2번째 입력은 초성자음으로 나누어지게 된다. In the above, when the plain consonant button (eg, the [a] button) is pressed twice, becoming a double consonant (eg, "ㄲ") always occurs in the initial consonant state. However, when the final consonant is input, pressing the [c] button (or the [b] button or the [j] button twice) will always be recognized as two flat consonants (eg "c") rather than a pair consonant. do. For example "

(Because "ㄸ" cannot come as a final consonant under "Oh") In other words, if a plain consonant without a double consonant consonant is input twice in a state where up to a neutral vowel is input, the first input is naturally As the final consonant, the second input is divided into the leading consonant.

Even if the input rule is presented as "flat consonant → double consonant or two flat consonants → lattice sound" (e.g. "a → ㄲ or ㄱㄱ → ㅋ"), it is easy for users to recognize it as "flat consonant → double consonant → lattice sound" . Of course, it is recognized that the double consonant when pressing the flat consonant button such as "a" can be divided into two flat consonants in some cases, but if the double consonant is not output when the flat consonant button is pressed twice, it will feel strange It could be. Therefore, a modified form of the above embodiment is suggested by using the property that the final consonant cannot be a final consonant.

Consonant consonants (eg "ㄲ", "ㅆ") are always displayed as supporting consonants when the flat consonant button is pressed twice in the neutral vowel state (eg "Ga"), and are displayed as they are according to the next input. It can be a double consonant or divided into two flat consonants, so it is natural for the user and there is no problem. In the case of flat consonants that cannot form double consonants (ie, "ㄸ", "ㅃ", and "ㅔ"), when the flat consonant button is pressed twice in succession in the neutral vowel state (eg "가"), if the above logic is followed It should be displayed as two flat consonants (final consonant + initial consonant), but since the user recognizes that the flat consonant button is pressed twice as a double consonant (hard consonant), it is processed as a double consonant to the initial consonant. For example, if the [c] button is pressed twice in succession after "a", it is processed as "ga ㄸ". The advantage of doing this is that pressing the flat consonant button twice is always displayed as a double consonant. The downside is that if the first consonant "c" appears consecutively after the final consonant "c", the user manually handles it (e.g., a predetermined time delay by a timer, manual by pressing the classification button after entering the first "c") distinction, ...) is to be done. (Since pressing the [c] button twice is treated as the initial consonant "ㄸ") Calculating the rate at which ambiguity occurs in this case is as follows.

Vowel + ㄲ 0.856 c + c 0.015 b+f 0.071 Vowel + ㅆ 0.219 j+j 0.03 Sum 1.191

As mentioned above, since about 54% of the letters without a final consonant (support) in our Korean language are "neutral vowels + initial consonants" (e.g. "vowels + ㄲ"), it should be considered exactly as 54% of the weight, and the final consonants ( Support) is about 46%, so in the case of "consonant + consonant" (e.g. "c + c"), it should be considered exactly as 46%, but letters with final consonants (support) and letters without support Since is about half and half, it is the result of simple summing assuming that the ratio is 50:50. Dividing this 1.191% in half gives an ambiguity of about 0.6%. If we add the 0.1% ambiguity presented above to this, we have about 0.7% ambiguity. This has an effect of reducing ambiguity compared to about 1% ambiguity that occurs when only "flat consonants → double consonants or two flat consonants → lattice sounds" are presented as the input rule above.

Here, "ㅅ" has only double consonants (hard consonants) and no lattice sounds. Therefore, it is possible to apply the technology proposed by the applicant (by pressing the [ㅅ] button, "ㅅ → ㅆ or ㅅㅅ → ㅅㅅ or ㅅㅆ → ㅆ"), and in this way, the case of "vowel + ㅆ" Since the above sum is 0.972% and divided by half, it is about 0.5%, so it can be said that there is an ambiguity of about 0.6% when combined with the above 0.1%. Again, there is an effect of reducing ambiguity compared to about 1% ambiguity that occurs when only "flat consonants → double consonants or two flat consonants → lattice sounds" are presented as the input rule above.

Of course, in the case of "ㄱ" here, pressing the [a] button 4 times is treated as an absolute "ㄲ", and in the case of a flat consonant that cannot form a pair consonant, pressing the flat consonant button 4 times is treated as "two flat consonants". (Example. If you additionally apply "c → ㄸ → t → dc"), there is only 0.1% ambiguity as described as processing all flat consonant buttons pressed 4 times as absolute double consonants. .

In the previous application of the applicant, "3+ other input methods" and examples of improvement were presented. In the existing repetitive selection method, when [x y z ...] is arranged (including both explicit arrangement or implicit association) on a button, the first "x" is input by pressing the button once, and the second Arranged "y" is input by pressing the button twice, third array "z" is input by pressing the button three times, ... nth arrayed alphabet is the button n times It is entered by pressing. It is natural (same as on a keyboard) to input an alphabet arranged on a specific button (eg "x") by pressing it once, and the second arranged alphabet and the rest of the alphabet are pressed twice or more Since it is input by pressing, the existing repetitive selection method can also be referred to as "2+other input method".

A summary of the above invention is as follows. Summarizing the method presented in "29.3 Improvement of Prior Application and Optimization for Korean Consonant Input", the repeated pressing of the [x y z ...] button in which "x", "y", "z", ... is arranged It is the same as "x → xx (corresponding to 'ㄱㄱ') or z (corresponding to 'ㄲ') → y (corresponding to 'ㅋ') → z (corresponding to 'ㄲ') → ...". As the double consonant incongruent flat consonant button described in the present invention is continuously pressed, "c → ㄸ → ℓ" is the same as "x → y → z". Therefore, becoming "ㅅ → ㄸ → テ → ㄴㄴ" is the same as becoming "x → y → z → xx". This is useful because "x", "y", and "z" are arranged on a button and the input system is configured so that "x" is input by pressing the corresponding button once, usually "x" is used most frequently. Because there are many. Therefore, while there is an advantage that existing users can easily understand the input of "x → y → z" according to repeated pressing of the corresponding button by the repeated selection method, there is a disadvantage that it is difficult to input "xx". The number of alphabets arranged (or related) on the button + 1" button press, which enables two alphabets (ie "x") to be input by pressing the corresponding button once (ie "xx") It has meaning. The application of "ㄴ → ㄸ → ㄴ → ㄴㄱ" to the [C] button can be equally applied to flat consonants that cannot be consonant (i.e., "ㄴ", "ㅅ", "ㅅ"), and consistency For this purpose, it can also be applied to the flat consonants that can be consonant (i.e., "a", "ㅅ"). In this way, by pressing the button "number of alphabets arranged (or related) on the button + 1" times, two alphabets input by pressing the corresponding button once are input for convenience, "2 alphabet input method by pressing more than 1 number of arrays" let's call it

"Arranged number exceeding 1 press 2 alphabet input method" is when there are two alphabets arranged or related to the button (i.e. [x y] button with "x" and "y" arranged) (e.g. "ㅅ" and It is obvious that only "ㅆ" can be equally applied to arrangement or association). For example, it can also be applied to the keypad of Dongmyeon 10-*. That is, "x → y → xx" according to button press, and "xx" is input by button press "arrangement or number of related alphabets (2) + 1" times. When applied to Korean, the "conventional" circular toggle repeat selection method is applied to initial consonants (ie, "x → y → x → y → x → ..." as the button is repeatedly pressed), and the final consonant It is also possible to apply the above invention only when consonants are input. When "x" is the final consonant, the second "x" of "xx" is the initial consonant of the next letter.

If you generalize and express "the method of pressing 2 alphabets by pressing the number of arrays exceeding 1", "N" (N = 1 or a natural number greater than 1) of alphabets A_1, A_2, A_3, ... A_N are arranged or related to the button When the button is pressed once, the first arranged or related alphabet A_1 is recognized, and when the button is pressed N times, the Nth arranged or related alphabet A_N is recognized, and when pressed N+1 times Two A_1 are recognized.

It is obvious that the "arranged number of pressing more than 1 alphabet input method" presented in the present invention can be applied not only to the keypad of Fig. 10-*, but also to all other keypads and computer keyboards.

29.6 Optimization of input by continuous pressing of the flat consonant button

In "29.5", the pair consonants (i.e., ㄸ, ㅃ, ㅔ) of "C", "ㅅ", and "ㅅ" are not used as final consonants, so in the present invention, for convenience, they are named "consonants that cannot be consonants." . And among "ㄴ", "ㅅ", and "ㅅ", only "ㅅ" and "ㅅ" are used as the second letter (eg ㅅ, ㄴ) constituting a double support (eg ㄼ, ㄵ). The twin consonants of "ㄱ" and "ㅅ" (ie, ㄲ, ㅆ) are used as final consonants, so for convenience, they are named "pair consonants that can be finalized with twin consonants". Both "ㄱ" and "ㅅ" are used as the second letter constituting a double support (eg ㄺ, ㄳ).

A complex phenomenon may appear when the initial consonant of the next letter appears after the final consonant in the two-beol-type automata of our Korean language. In the case of "Ulsu", "?d" was entered, then "?dㅅ", and then "Ulsu" was entered (29.3). In the following, the appearance of changing a plain consonant after being input as a final consonant will be described as an example, and since there is no complexity in the case where a plain consonant is input as a leading consonant, the non-cyclic or circular processing proposed in the previous application can be applied.

Since double consonants are in the form of two flat consonants, it may be cognitively natural to input by pressing the flat consonant twice. However, in this case, continuous pressing is not guaranteed for perfect Korean input. In the present invention (29.6), it is intended to present an input method that is cognitively natural and minimizes ambiguity while inputting double consonants by pressing flat consonants twice.

In describing the embodiment of the present invention, even if the keypad shown in FIG. 10-* is mainly described as an example, the existing two-beol keyboard (computer keyboard), short vowel keyboard (in the two-beol keyboard, 'ㅑ', 'ㅕ', 'ㅛ', It is self-evident that it can be applied to all keyboards, such as keyboards without 'ㅠ'. In presenting an example where a flat consonant is entered as a final consonant and then the same button is continuously pressed to lead to the initial consonant of the next letter, the first letter already entered is mainly used.

First, in order to clearly show the difference between the present invention (29.6) and the applicant's earlier application, the contents presented in the applicant's earlier application are briefly summarized.

Let's take a look at the case of inputting a double consonant by inputting a flat consonant twice. In a situation where up to a neutral vowel is entered (eg 'ga'), if "c" is input, it becomes "trap", and if "c" is input again, it can be "trap" or "ga ㄸ". The treatment as "kpa" and the treatment as "ga ㄸ" have already been suggested in the previous application (29.5) of the applicant.

Go → Trapped → Go

Based on the actual frequency of use, it was suggested in the previous application of the applicant that it is advantageous to treat it as "ga ㄸ". Also, in the previous application, since "ㄸ" and "T" are related to the [c] button of Figure 10-*, if "c" is input once more in the "Ga ㄸ" state, it becomes "same", and "c" is It was suggested that if more input was made, it would become "trapped". The same applies to "ㅅ" and "ㅅ".

Go → Kapp → Ga ㄸ → Same → Kapp c

A → A → Gaㅃ → Repay → Gab

ga → have → ga t → 갗 → have

Among the plain consonants that cannot be consonant with double consonants, "ㅅ" and "ㅅ" can be used as the second letter of the double support, such as "ㄼ" and "ㄵ", and this case is as follows based on Figure 10-*.

Go → ?E → Go → ?H → ?Ef

Liver → ?C → Liver → Liver → ?C

Regarding the flat consonants that can form double consonants, the following is done based on Figure 10-*.

A → Gak → ?A → ?J → Gak

↘ (Enter a vowel (eg. ㅡ)) → Gakkeu

Go → gnaw → galㄲ → galkk → gnaw

Go → Gat → Gat → Gats

↘ (Enter a vowel (ex. ㅡ)) → Katsu

Gak → ?B → Gakㅆ → ?Bㅅ

Based on the above drawing 10-*, the contents presented in the previous application (29.5) of the applicant are summarized. Hereinafter, an example of optimizing the input for each letter with respect to the matters presented in the previous application of the applicant is shown.

In the following, the consonant "XY" is expressed as a consonant in which the first letter is the final consonant and the second letter is the initial consonant. However, in some cases, two initial consonants may be expressed. According to the frequency of use of our Korean language, the cases of "D", "B", and "Ji" were 0.015%, 0.071%, and 0.03%, respectively, and the total was 0.116%, which is very small. In addition, only 0.055% of cases appear as "ㅅㅅ". The frequency of occurrence of letters ending in vowels (e.g. 'ga', 'na', 'da',...) followed by final consonants and initial consonants "ㅅㅅ", "ㅅㅅ", "ㅅㅅ", "ㅅㅅ" All together, it is only about 0.171%. On the other hand, the frequencies of "ㄸ", "ㅃ", "ㅆ", and "ㅆ" appearing as initial consonants after a letter ending in a vowel are 0.44%, 0.144%, 0.169%, and 0.219%, respectively, for a total of 0.972%, which is about 1. close to % Therefore, it can be seen that it is advantageous to treat the twin consonants of "ㅅ → ㄸ → ℓ" as absolute twin consonants, as in the applicant's previous application (29.5), for "ㅅ", "ㅅ", "ㅅ", and "ㅅ".

When a flat consonant without double consonants is pressed 4 times, a few examples of non-cyclic processing without recognizing two flat consonants are as follows.

ga → locked → ga ㄸ → equal (cycle end) → equal

A → A → Ga ㅃ → Pay (end of cycle) → Pay

GA → GA → GA → 갗 (cycle end) → 갗

If you view "pyeong consonant → double consonant → lattice consonant" as one cycle, and process it in a non-circular manner, you can enter "DD", "PB", and "CJ" by pressing each button 4 times. In the following, unless absolutely necessary, the point of "end of cycle" is not indicated. The frequencies of "D", "P-B", and "C-J" are 0.064%, 0.004%, and 0.002%, respectively, and the sum of all is 0.07%. It can be seen that 0.07% is slightly less than 0.116% when it comes out as "dc", "bb", and "jj", but both frequencies are very small. Nevertheless, the reason for presenting the acyclic process is that since the lattice sound is input by pressing the flat consonant button 3 times, it is cognitively more natural that "lattice sound + flat consonant" is input by pressing the flat consonant button 4 times. because it's ugly

Here are some examples of circular processing:

Go → Caught → Ga ㄸ → Same → Caught

A → A → Ga ㅃ → Repay → A

ga → have → gayeot → 갗 → have

Cognitively, after pressing the [c] button 3 times to enter "ㅅ", pressing the [c] button once more will recognize "ㅅ", so pressing the [c] button 4 times will input "ㅅ", which is non-cyclical. It is cognitively more natural for the user than processing in a circular fashion. If you show that it is processed in a non-circular way when it is pressed more than 5 times, it is as follows.

Go → Kapp → Go → Same → Same c → Same ㄸ → Same → Same → Same

A → A → Gaㅃ → Repay → Repay → → Repay → Repay → → Repay

ga → ga → gajj → 갗 → 갗j → 갗 → 갗ch → ?Ochj

A case in which a double consonant can be formed by combining a plain consonant with a final consonant of a pre-entered initial letter is as follows.

Liver → ?C → Liver → Liver ch → ?Cch (Cycle ends. Press 4 times = 'jch')

or

Liver → ?C → Liver → Liver (cycle end) → Liver

You can input "ch" by pressing the [j] button 3 times, and "jch" corresponds to pressing the [j] button 4 times. It has cognitively good features. However, since 0% of the actual frequency of use is "ㄵㅁ", pressing the [j] button 4 times (when the number of consonants associated with the button is pressed) is not treated as "jch". it is desirable As shown in the above case, the cycle node may vary depending on the situation (whether the flat consonant button is pressed after the final consonant that can be combined with a double support, ...) and how the input rule is defined.

Similarly, we look at "ㄺ", which becomes a double support by combining with "ㄱ", a flat consonant that can form double consonants.

Gal → gnaw → Gal ㄲ → Gal ㅋ → Gnaw (Cycle ends. Press 4 times = 'ㄱㅋ')

or

Gal → gnaw → Gal ㄲ → Gal ㅋ (Cycle ends) → Gal ㅋ ㅋ (Non-circular processing. Press 4 times = 'ㅋ ㄱ')

In Figure 10-*, only "ㅅ" and "ㅆ" are associated with the [ㅅ] button. As explained in the previous application (29.3) of the applicant, it was explained that "ㅅ → ㅆ or ㅅㅅ → ㅅ → ㅅ ㅅ or ㅅㅆ → ㅆㅆ" according to pressing the [ㅅ] button. In fact, in terms of frequency of use, "ㅆㅅ" is used a relatively large number (frequency 0.375%) such as "I did", "I went", "I came", ..., so pressing the [ㅅ] button 3 times is treated as "ㅆㅅ" It is much more natural and cognitively valid. Likewise, in the case of "?B→...", "ㅅㅆ" in the form of three "ㅅ" can be input by pressing the [ㅅ] button three times. The case of "ㅅㅅ" is 0.055%, and the case of "ㅅㅅ" is 0.003%, so both are almost insignificant, so it can be processed in one direction that is cognitively valid (by pressing the [ㅅ] button 3 times to enter 'ㅅㅆ') have.

가 → Gat → 가 → ㅅ → 가 (earlier application 29.3)

↘ (Enter a vowel (eg. ㅡ)) → Gods (earlier application 29.3)

↘ (Enter a vowel (ex. ㅡ)) → Katsu (earlier application 29.5)

↘ God (invention. Press 3 times =- 'ㅅㅆ')

Gak → ?B → Gakㅆ → ?Bㅅ (earlier application 29.5)

↘ ?B ㅆ (Invention. Press 3 times = 'ㅅㅆ')

If the [ㅅ] button is pressed once more in the "God ㅆ" state, it may be treated as "Ga ㅆ", but since the frequency of use of "ㅆ ㅆ" is 0%, there is no need to process it as "ㅆ ㅆ". When the [ㅅ] button is pressed 3 times after a letter ending in a vowel, the frequency of "ㅅㅆ" is 0.055%, whereas the frequency of "ㅅㅆ" is much higher at 0.375%. It is reasonable to make "ㅆㅅ" be recognized instead of ".

Go → Go → Go (Cycle End) → Go

And in reality, "ㄳㅆ", "ㄽㅆ", and "ㅄㅆ" are 0%, 0%, and 0.02%, respectively. Therefore, if you do not process "ㄳㅆ" and "ㄽㅆ" that do not actually exist, and process them in a non-circular manner, it becomes as follows. Since it is treated as "ㅆㅅ" in the same way as when the [ㅅ] button is pressed 3 times after a letter ending in a vowel, a unified and consistent feeling of use can be provided to the user.

each → ?B → each ㅆ (end of cycle) → each ㅆㅅ

Gal → ?F → Gal ㅆ (cycle end) → Gal ㅆㅅ

If processed in a circular fashion, it becomes:

Each → ?B → Each → ?B

Go → ?F → Go → ?F

However, since there are at least 0.02% of cases where "ㅄㅆ" appears like "cheap", it is better to process it so that it is recognized as "ㅅㅆ" (exactly 'xㅅㅆ'. x=ㅅ) by pressing the [ㅅ] button 3 times as follows. It is reasonable, and this is one of the important points of the present invention. Schematically, it looks like this:

A → Value → A ㅆ → Value ㅆ (end of cycle)

Based on Figure 10-*, the flat consonant once pressed is combined with the final consonant of the preceding letter to form a double support, and the frequency of "ㄵCh", "ㄳㅆ", "ㄽㅆ", and "ㄺㅋ" is 0, respectively. %, and only "ㅄㅆ" has a meaningful usage frequency. If the above invention is compared with the previous applications (29.3, 29.5) of the applicant, it is as follows.

A → Value → Value ㅅ → Value ㅆ → Ga ㅆ (Refer to the case of 'Ulsu' in Prior Application 29.3)

A → value → value ㅆ → value ㅅ (earlier application 29.5)

The cases of "ㄱㅆ", "ㄹㅆ", and "ㄴㅆ" are 0.023%, 0.171%, and 0.017%, respectively, and the sum of all is 0.21%. On the other hand, "ㄳㅅ" and "ㄽㅅ" are 0% each, and "ㅄㅅ" is only 0.02%. In the previous application (29.3), "ㄳㅅ", "ㄽㅅ", and "ㅄㅅ" with little or no frequency of use were processed by pressing the [ㅅ] button twice, and "ㄱㅆ" and "ㄹㅆ" with relatively high frequency ", "ㅅㅆ" was processed by pressing the [ㅅ] button 4 times. In addition, in the previous application (29.5), "ㄱㅆ", "ㄹㅆ", and "ㄴㅆ" were processed by pressing the [ㅅ] button twice, but "ㅄㅆ" was not processed by pressing the [ㅅ] button 3 times. However, in the present invention, while "ㄱㅆ", "ㄹㅆ", and "ㄴㅆ", which are relatively more frequently used, are processed by pressing the [ㅅ] button twice, "ㅄㅆ" can be naturally processed by pressing the [ㅅ] button 3 times. There are advantages to being able to

Even if it is not mentioned in other parts of the present invention, if the input rule is not defined such as "?Fㅅ" (including other similar cases), after inputting "?F", a predetermined means (eg, the user ends the syllable) It is obvious that it is possible to end character input by pressing means) and input "ㅅ".

Next, when a vowel is input after "A → each → ?A", it is a matter of whether to process it as "ㄱㄱ" (earlier application 29.3) or "ㄲ" (earlier application 29.5).

"ㄱㄱ" is 1.096% and occupies a relatively high frequency. And "ㄲ" appears as the initial consonant after a letter that ends with a vowel is 0.859%. In Korean Hangul, the number of letters without a final consonant is about 54% and the number of letters with a final consonant is about 46%, so the frequency of letters without a final consonant (eg 0.859%) is set at 54%, and the frequency of letters with a final consonant is set at 54%. (Ex. 1.096%) should be considered as a percentage of 46%. So far, since both are approximately half and half, comparisons have been made simply without applying weights (54%, 46%), but here, a more precise comparison by considering weights (54%, 46%) is as follows.

If it comes out as "ㄱㄱ", 46% of 1.096% = 0.504

When it comes out as vowel + initial consonant "ㄲ", 54% of 0.859% = 0.46%

Since the frequency of "ㄱㄱ" is slightly higher, it is slightly more advantageous to process it as "ㄱㄱ", but it can be seen that there is virtually no difference between the two. Therefore, one of the previous applications (29.3, 29.5) of the applicant can be applied. As suggested in the previous application (29.3) of the applicant based on Figure 10-*, pressing the [a] button twice can be treated as "ㄲ" or "ㄱㄱ", and pressing 4 times can be treated as absolute "ㄲ". can

A → Gak → ?A → ?J → ?A → (Enter a vowel (ex. ㅡ)) → Gakkeu

↘ (Enter a vowel (eg. ㅡ)) → Each

Furthermore, if "ㄱ" can be combined with the final consonant x (ex. It can be treated or treated in a non-circular or cyclic type. However, since the frequency of "ㄺㅋ" is 0%, it is preferable not to process it as "ㄱㅋ".

gal → gnaw → galㄲ → galㅋ → gnaw (Cycle ends. Press 4 times = Recognized as 'ㄱㅋ')

or

Gal → gnaw → Gal ㄲ → Gal ㅋ (Cycle ends) → Gal ㅋ ㅋ (Non-circular processing. Press 4 times = 'ㅋ ㄱ')

Since "ㄾ" and "ㄿ" can be used as separate double supports, it is preferable that they become "ㅅ" and "β" rather than "DTI" and "WF" when pressed 4 times.

Go → Go → Go → ?G (cycle end) → ?G

Go → ?E → Go → ?H (cycle end) → ?Hf

Processing the pressing of the [a] button 4 times as "ㅋㅋ" rather than "ㄱㅋ" (in this embodiment, input as 'ㄺㅋ') is "ㄴㄴ" (in this embodiment, input as 'ㄾㄴ'), It becomes consistent with recognizing and processing "P-B" (in this embodiment, input as 'ㄿ-'). In addition, actual users often use expressions such as "ㅋ", and there is an advantage in that you can input "ㅋ" by pressing the [a] button 6 times in succession after "go".

Based on Figure 10-*, the application of the applicant's previous application (29.5) to the continuous pressing of the [a] button is as follows.

A → Gak → ?A → ?J → Gak A (earlier application 29.5)

↘ (Enter a vowel (ex. ㅡ)) → Gakkeu

The processing as described above has the advantage of maintaining consistency with the fact that two presses of the "c", "b", "ㅅ", and "ㅅ" buttons are always treated as twin consonants in the present invention. However, as suggested in the present invention, among the plain consonants with twin consonants, inputting "c", "ㅅ", "ㅅ", and "ㅅ" twice in succession, respectively, is always processed as each pair consonant, " ㄱㄱ" (eg, the final consonant and the initial consonant in 'country') is cognitively recognized by the user as always having two "a", so it may be more desirable to treat pressing the [a] button twice as "ㄱㄱ" have. If "ㄱ" is pressed 4 times after a letter ending with a final consonant (eg, 'ㅁ') that cannot be combined with a double support (eg, 'gam'), it should be "gam ㄱㄱ". However, if pressing the [a] button 4 times becomes "ㄱㄱ", it is to process the transition from the final consonant to the initial consonant. It is reasonable to view until pressed three times as a cycle node. This also means that the cycle node may vary slightly depending on the situation or viewpoint.

It is also obvious that it can be input in combination with a vowel button, such as "ㄲ = ㄱㅣㅣ" and "ㅋ = ㄱㅡㅡ" presented in the applicant's previous application.

As shown in the embodiment of the present invention, the fact that a specific letter (eg. ㅅ) is recognized after a letter ending with a final consonant (eg. ㅅ) is double if it is combined with the preceding consonant to form a double support It means that it is entered as a support (eg ㅄ), and if a double support cannot be achieved, it means that it is entered as its own consonant.

Based on Figure 10-*, the above contents are summarized as follows.

The alphabet first arranged or related to each button is recognized as one press of each button.

For flat consonants that cannot be consonant with double consonants ('c', 'b', 'j'), the corresponding flat consonant is recognized by pressing once. Pressing twice is always recognized as the corresponding consonant. This means that even if a flat consonant with no consonant consonants is entered twice after a letter that ends with a vowel, it is not recognized as "c". It has been explained that this processing is advantageous in terms of cognitive aspect (user's perception that "ㄸ" is input by pressing "c" twice) and frequency of use. Pressing 3 times is always recognized as the corresponding grating sound. Pressing 4 times is recognized as a corresponding lattice sound and a corresponding flat consonant sound. This is also an optimized result by integrating both the cognitive and practical aspects as described above.

In the [ㅅ] button, "ㅅ" and "ㅆ" are associated or arranged. "ㅅ" is recognized by pressing the [ㅅ] button once. Pressing twice is always recognized as "ㅆ". This means that after a letter ending in a vowel, the [ㅅ] button is pressed twice and recognized as "ㅆ", and even if a vowel is entered again, it does not become "ㅅㅅ" and is recognized as the initial consonant "ㅆ", and also "ㅅ" Even if "ㅅ" is pressed twice after a letter ending with a final consonant (eg 'ㄱ') that can be combined, "ㅅㅅ" is recognized, and as a result, it is always recognized as "ㅆ" rather than "ㄳㅅ". It means. Pressing the [ㅅ] button three times is recognized as "ㅆㅅ". This also means that "ㅅ" is recognized as "ㅆㅅ" instead of "ㄳㅆ" even if "ㅅ" is pressed 3 times after a letter ending with a final consonant (eg 'ㄱ') to which "ㅅ" can be combined. However, it is preferable that when the [ㅅ] button is pressed three times after a letter ending in the final consonant "ㅅ", it is recognized as "ㅅㅆ" and the result is "ㅄㅆ".

For "a", two types of processing are possible. Pressing the [a] button once is recognized as "a". Pressing the [a] button twice is recognized as "ㄲ" or "ㄱㄱ". What is recognized as "ㄱㄱ" includes several of the following. If the [a] button is pressed twice after a letter ending in a vowel, the final consonant "ㄲ" becomes the final consonant, but if the next vowel is entered, it is recognized as "ㄱㄱ", and the final consonant that "ㄱ" can be combined (eg. d) Next, when the [a] button is pressed twice, "ㄱㄱ" is recognized, and as a result, "ㄺㄱ" means. Pressing the [a] button three times is recognized as "ㅋ". And pressing the [a] button 4 times is always recognized as "ㄲ". This means that even if a vowel comes after the final consonant "ㄲ" input by pressing 4 times, it does not become "ㄱㄱ".

Based on Figure 10-*, the above presented a comprehensively optimized process when inputting double consonants and lattice sounds by continuously pressing the same flat consonant button in consideration of both cognitive and practical aspects. Although described based on Figure 10-*, the same can be applied to similar cases.

Another processing by pressing the [a] button in the above is as follows. However, as in the detailed description of the present invention, the techniques presented in the above summary are recommended. Pressing the [a] button once is recognized as “a”. Pressing the [a] button twice is always recognized as "ㄲ". This means that even if a vowel comes after the "ㄲ" input as the final consonant, it does not become "ㄱㄱ". Pressing the [a] button three times is always recognized as "ㅋ". Pressing the [a] button 4 times is recognized as "ㄱㄱ".

The contents described in the present invention are rearranged as follows.

A method of inputting Korean on a keypad having a plurality of buttons, each button having one or more Korean alphabets arranged or related, and pair consonants and lattice sounds corresponding to the flat consonants are related or arranged in flat consonant buttons, respectively. in

When the button is pressed once, the alphabet first arranged or related to the pressed button is recognized,

The flat consonant is recognized by pressing any one of the buttons "c", "b", and "ㅅ", which are flat consonants that cannot be formed as twin consonants,

The corresponding consonant is recognized by pressing the same button twice in succession among the "c", "b", and "j" buttons,

When the same button is pressed 3 times in succession among the "c", "b", and "j" buttons, the corresponding grid sound is recognized.

When the same button is pressed 4 times in succession among the "c", "b", and "j" buttons, the corresponding lattice sound and the corresponding flat consonant sound are recognized,

"ㅅ" is recognized by pressing the "ㅅ" button once,

By pressing the "ㅅ" button twice, "ㅆ" is recognized, and when the vowel button is continuously input after the final consonant "ㅆ", the initial consonant "ㅆ" is recognized,

"ㅅㅅ" is recognized by pressing the "ㅅ" button 3 times,

By pressing the "a" button once, "a" is recognized,

By pressing the "a" button twice, "ㄲ" or "ㄱㄱ" is recognized, and when a vowel is continuously input after the final consonant "ㄲ", it is recognized as "ㄱㄱ" of the final consonant and the initial consonant,

"ㅋ" is recognized by pressing the "a" button three times,

"ㄲ" is recognized by pressing the "a" button 4 times, and when a vowel is continuously input after the final consonant "ㄲ" by this, it is recognized as the initial consonant "ㄲ"

Korean input method on the keypad characterized by

The following may be additionally applied to the above.

In the above,

"ㅅㅆ" is recognized by pressing the "ㅅ" button three times consecutively after a letter ending in the final consonant "ㅅ" ('ㅄㅆ' is input by combining with the previously entered final consonant "ㅅ")

Korean input method on the keypad characterized by

The following may be additionally applied to the above.

In the above,

Consonants entered by pressing the consonant button once include at least the consonants of "a", "b", "c", "ㅁ", "ㅅ", "ㅅ", "ㅇ", and "ㄴ"

Korean input method on the keypad characterized by

The following may be additionally applied to the above.

In the above, the Korean input method on the keypad, characterized in that it is processed in a non-circular manner after the end of the cycle

Also, instead of the [a] button pressing process in the above, when the [a] button is pressed twice, "ㄲ" is absolutely recognized, and when the [a] button is pressed three times, "ㅋ" is recognized, and by pressing the [a] button four times, It can be applied that "ㄱㄱ" is recognized as a burden.

Next, "ㄲ", "ㄸ", "ㅃ" buttons "a", "c", "ㅅ", "ㅅ", "ㅅ", respectively, like the double keyboard (computer keyboard) or Google's "single vowel keyboard" Let's take a look at processing when only ", "ㅆ", and "ㅆ" are associated. Google's single vowel keyboard is missing 'ㅑ', 'ㅕ', 'ㅛ', and 'ㅠ' from the computer keyboard, and ㅑ = AH, ㅕ = sh, ㅛ = ㅗㅗ, ㅠ = TT is entered. Since it is widely used through the Android Market (Google Play Store), drawings and descriptions of the single vowel keyboard are omitted. However, even if the description is based on a computer keyboard, it is obvious that the technical idea of the present invention can be equally applied to other keyboards.

Currently, many programs show that double consonants are processed by pressing flat consonants twice in the existing double keyboard. However, if it is pressed twice consecutively within a predetermined time, it is processed as a double consonant, and if it is pressed twice consecutively beyond a predetermined time, it is processed as two plain consonants. However, when the user inputs a double consonant, he presses it twice quickly, and when he inputs a flat consonant twice, he does not press it twice slowly. If there is a user who hits 300 to 400 strokes per minute, it can be seen that the user mercilessly always presses quickly. After all, the problem of "ambiguity" that traditionally existed in 12-button keyboards is still an important issue.

In the past, when a flat consonant was pressed twice, it was generally processed as follows.

Go → Trapped → Trapped → Trapped

Applying the applicant's earlier application (29.5), we get: The same is true for other consonants (i.e., ㄱ, ㄴ, ㅅ, ㄴ).

Go → Kapp → Ga ㄸ → Kapp c

Here, since only two pair consonants corresponding to the corresponding flat consonant are associated with the flat consonant button, pressing the flat consonant button three times becomes "ㅅ U". Cognitively, it is a little unnatural to input an even number of consonants with an odd number of presses. The fact that processing the [c] button twice as "ㄸ" is cognitively natural for the user has already been explained in the previous application (29.3) of the applicant.

As already mentioned, the cases in which the paired consonant incongruent plain consonants appear as "dc", "bb", and "jj" are 0.015%, 0.071%, and 0.03%, respectively, and the total is 0.116%, which is very small. Therefore, pressing the flat consonant button 3 times can be processed as "□ㄸ" as follows.

ga → trapped → ga ㄸ → trapped ㄸ

A → A → Ga ㅃ → A ㅃ

ga → have → ga pp → have

The case where a flat consonant (eg, ㅅ, ㅅ) that can be combined with a double support following a final consonant is pressed is as follows.

Go → ?E → Go → ?Eㅃ

Liver → ?C → Liver → ?C

This is the same as the case of “gal → gnaw → gal ㄲ → gal ㅋ → gnaw” already described in the present invention. In terms of the frequency of use, only 0.002%, 0.001%, and 0% of "Dㄸ", "ㅅㅃ", and "ㅅㅃ" were used, respectively. In addition, "ㄼㅃ" and "ㄵㅅ" are 0% and 0.002%, respectively. The sum of all five cases is 0.005%. It is much less than 0.116%, which is the case with "D", "B", and "J" presented above. Nevertheless, it is suggested that the consonants (eg, □ㄸ) can be processed as described above in terms of "cognitive compatibility" for consonants composed of three specific consonants.

Even if there is a letter or final consonant ending in a vowel, the number of letters associated with a specific button (in the example, two plain consonants and two consonants ), it is recognized and processed as a "flat consonant consonant" when it is pressed in excess of ).

Since "ㅆ" can be a final consonant, if the [ㅅ] button is pressed consecutively after a vowel, it can be processed as suggested in the applicant's previous application and the present invention. For example, it becomes like "Go → Gat → Gone → Gwas". However, if the [ㅅ] button is pressed three times in succession after a letter ending with a final consonant (e.g., "ㅅ", "ㄱ", "ㄹ") that can be combined with "ㅅ", As such, it can be processed as "A → value → value ㅆ → value ㅆ". The case of "ㄲ" is the same as that of "ㅆ". For example, when a consonant consonant is combined with a double support, it can be processed as “gal → gnaw → gal ㄲ → gnaw ㄲ”. All three presses of the flat consonant button are recognized and processed as "ㅅㅆ" or "ㄱㄲ".

All of the above cases are processed as final consonants when the flat consonant button is pressed, and in the case of initial consonants when the flat consonant button is pressed in the initial state, as already suggested in the previous application, it is simply a non-cyclic or circular process.

If this is generalized, it is expressed as follows. When A_1 is a flat consonant with no double consonants, and N Korean consonants, such as A_1, A_2, A_3, ... A_N, are related to one button, pressing N times is recognized as a consonant corresponding to the number of presses. , It means that “N+1 times” is recognized and processed as “A_1 A_N”. As already explained, "A_1 A_N" is a final consonant and a leading consonant like "XY". The recognized A_1 is a final consonant or combined with a previously input final consonant to form a double base, and the recognized A_N is treated as a leading consonant.

However, if A_1 is a plain consonant that cannot form a pair consonant, it is the case where the button is pressed continuously after a letter ending with a vowel or a final consonant that can be combined with an input flat consonant to form a double support, and A_1 is a pair In the case of a plain consonant capable of consonant ending, the corresponding button is pressed continuously after a letter ending with a final consonant that can form a double support by combining with A_1.

To summarize this:

It has a plurality of buttons, and on the buttons, Korean consonants (A_1, A_2, ... A_N) of N (N is 1 or a natural number including 1 or more) are arranged or related to Korean by the repetitive selection method on the keypad. In the input method,

The A_1 is a flat consonant that cannot be formed as a double consonant, and after a letter ending with a vowel or a final consonant that can form a double support by combining with A_1 is input,

or

The A_1 is a flat consonant capable of forming a pair consonant, and after a final consonant that can form a double support in combination with A_1 is input,

When the button is pressed once, A_1 is recognized,

When the button is pressed twice, A_2 is recognized,

When the button is pressed N times, A_N is recognized,

Recognizing "A_1 A_N" when the button is pressed N+1 times

Korean input method on the keypad characterized by

Additionally, in the above, A_2 may further include a pair consonant.

29.7 Resolving ambiguity when inputting dropped consonants (eg "ㅎ") by repeated pressing

In the previous application (29.4) of the applicant, it was proposed to input "ㅎ" associated with or arranged in the [•] button by pressing the [•] button three times based on Figure 10-*. In some cases, it has been explained that pressing the [ㆍ] button once is treated as “a” and pressing the [ㆍ] button twice as “o” as follows.

ㄱ → 가 → Geo → ㄱㅎ → Red → か

In the above, if you press "ㆍㅡ" in the "red" state to input "gaho", it will be "geuh". It was explained in the previous application (29.4) that there is no problem in becoming a “geo-ho” by pressing “ㆍㅡ” in the “g” state.

In the case of inputting "a" as "ㅣㆍ", it has been explained that the following can be processed by continuously pressing the [ㆍ] button.

Gi → Go → Gya → ?? → red → ?y

Even in this case, "??" If you press "ㆍㅣ" in the status, it will become "Gahi". Likewise, if you press "ㆍㅣ" in the "Red" state to enter "Gaheo", it will become "Gyahi". The same problem occurs in the case of "symbol" (entered as ㅗ=ㆍㅡ), and "Gaheo" as well as "Gaheo" as in "Kiheo". In other words, the input value of "giheo ↔ gahi" is the same, but there is ambiguity that can appear differently.

In general, means for resolving such ambiguity include “entering after a certain period of time” or “pressing the hangup button” (a [blank] button can also be used as a hangup button). In the past, when a predetermined time elapsed or when the cutoff button was pressed, the already input character (eg '??') was completed, and then "ㆍㅡ" was inputted to become "??ㅗ". That is, as follows.

Gi → Go → Gya → ?? → red → ?y

↘ (Elapsed time or hang up button, press ㆍㅡ) → ??ㅗ

However, in the case of the present invention, the state that the already input character "??" has been input up to the final consonant is maintained for the elapse of a predetermined time or when the disconnect button is pressed, but the press of "ㆍㅡ" is not treated as "possibly", It should be treated as a "sign". That is, the letter combination is not completely terminated by the lapse of a predetermined time or by pressing the cut-off button, and a change (e.g., '?? → Red') to the already input "??" will not be given. For convenience, this will be referred to as “determination of the input state by elapse of a predetermined time or by pressing the disconnect button” or “determination of the input state” for short.

As seen in the above case, if a predetermined time elapses or the hangup button is not used, "ㅎ" is input by pressing the [ㆍ] button 3 times, and then the character by pressing the [ㆍ] button successively to input the next vowel. It can be seen that a problem occurs in the case of . The present invention proposes a technique that can solve this problem without using the lapse of a predetermined time or pressing the disconnect button.

After "ㅎ" is input by pressing the [ㆍ] button three times in succession, there is no problem when a vowel starting with the [ㅡ] button or the [ㅣ] button is input instead of the vowel starting with the [ㆍ] button. none. In other words, if "ㅣ" is entered in "??", it becomes "gihi", and if "ㅣ" is entered in "red", it becomes "gahi". No problems at all so far.

Here, after the dropped consonant "ㅎ" is entered, pressing the [ㅡ] button twice will not input another alphabet (other consonants), so if "ㅣ" is entered once more in the "gihi" state, it can be processed as "giheo". have. If only the change of the vowel according to the [ㅣ] button is pressed, it can be expressed as "ㅣ → ㅇ". In the diagram below, the right arrow contains the "ㅣ" button pressed. (Below, if "ㅣ" is pressed continuously or "ㅡ" is pressed continuously, (ㅣinput) or (ㅡinput) is not marked separately between the arrows.)

?? → Gihi → Giheo

If "ㅣ" is entered once more in the "Giheo" state, it becomes "Gihe". (Because ㅔ=shㅣ) To input "ㅕ", you can input "ㅕ" by pressing the [ㆍ] button once after "sh" entered as "ㅣㅣ". When “ㅣ” is pressed once more in the state where “ㅕ” is recognized, “ㅖ” becomes “ㅖ”. To summarize this:

?? → Gihi → Giheo → Gihe

↘ (ㆍInput) → Giheol → Gihye

It is natural that "ㅖ" becomes "ㅖ" by pressing "ㅣ" after "ㅕ" input by "ㅣㅣㆍ" (ie, "ㅇㆍ"). It is the same as being processed in the "red" state.

red → gahi → gaheo → gahe

↘ (ㆍInput) → Gyeol → Gahye

It has been explained in the previous application (29.4) that there is no problem in inputting "gyaheo" by pressing "ㆍㅣ" or "ㆍㆍ" in the "?y" state. However, for consistency in use, the above information can be applied, and if it is shown schematically, it is as follows.

?y → Gyahi → Gyaheo → Gyahe

↘ (ㆍinput) → Gyaheo → Gyahye

Next, it shows the case of inputting "ㅗ" or "ㅛ" after the consonant (eg. ㅎ) entered by pressing the [ㆍ] button 3 times.

remind "??" In the state, pressing the [ㅡ] button twice can be treated as "ㅗ".

?? → gich → sign

In the above, if only the change of the vowel according to the pressing of the [ㅡ] button is expressed, “ㅡ → ㅗ” becomes. In the case of the vowel "ㅗ", since there is no vowel to which "ㅡ" is combined after "ㅗ", pressing the [ㅡ] button three times can be treated as "ㅛ". In addition, "ㅗㆍ" can be treated as "ㅛ" for consistency with the processing case of "ㅕ". Only one of the two may be applied, or both may be applied simultaneously. If you look at it schematically, it looks like this:

?? → Gihe → Symbol → Gihyo

↘ (ㆍInput) → Term

If only inputting "ㅛ" with [ㅡ] button 3 is applied, as shown in the previous application, pressing "ㅗㆍ" can be treated as "ㅘ". If it becomes "ㅘ" and then "ㅣ" is pressed, it will become "ㅙ".

?? → Gihe → Symbol → Gihyo

↘ (ㆍinput) → Vaporization → (ㅣinput) → Kihyeom

When “ㅣ” is pressed in the “symbol” state, it becomes “opportunity”, when “ㆍ” is pressed in the “opportunity” state, it becomes “vaporization”, and when “ㅣ” is pressed in the “vaporization” state, “kihyon” becomes do.

?? → Gihe → Symbol → (ㅣInput) → Opportunity → (ㆍInput) → Kihwa → (ㅣInput) → Gihyeop

"??" The example of input in the state was shown, but the processing in the "red" state was also "??" Since it is completely the same as the processing in the state (only '??' and 'ki' are changed to 'red' and 'ga', respectively), the description is omitted. Similarly "?R" state and "??" The processing in the state is also exactly the same as the processing in the "??" and "red" states, so the description is omitted.

By applying the present invention above, while inputting consonants (eg, heh) arranged together on the [ㆍ] button by pressing the [ㆍ] button 3 times, at the same time “a, b, c, d, ㅁ, f, ㅅ, ㅇ By completely arranging 10 consonants (consonant groups) one by one on each of the 10 number buttons, it is possible to utilize the correspondence between numbers and Korean consonants, while realizing perfect Korean input without ambiguity. have.

In the "?y" state, "sh = ㆍㅣ" or "sh = ㆍㆍ" can be processed, and "ㅕ = ㆍㆍㅣ" can be processed. However, it goes without saying that even in the "?y" state, "gyaheo", "gyyaeo", "gyyaho", and "gyahyo" can be input by applying the present invention.

In the above, a technology that can be input without ambiguity was shown when a consonant (eg. ㅎ) input by pressing the [ㆍ] button 3 times is input as a final consonant. If the initial consonant is entered by pressing the [ㆍ] button three times, as before, “sh=ㆍㅣ”, “ㅕ=ㆍㆍㅣ”, “ㅗ=ㆍㅡ”, “ㅛ=ㆍㆍㅡ” input does nothing. there was no problem. However, even when the initial consonant is input by pressing the [•] button three times, the vowel input rule proposed in the present invention can be applied to provide consistency to the user.

In the previous application, it was shown that "lattice = plain consonantㅡㅡ", "twin consonant = flat consonantㅣㅣ", and after this lattice consonant and double consonant, press "ㅡㅡ" or "ㅣㅣ" to enter another consonant If not (in other words, if another consonant is not input with "lattice + ㅡㅡ" or "lattice + ㅣㅣ"), the vowel input rule presented in the present invention can be applied similarly.

Furthermore, even if inputting "lattice = flat consonant ㅡㅡ" or "twin consonant = flat consonant ㅣ" is not applied, it can be processed in such a way that it can be cognitively matched while minimizing ambiguity while inputting only by pressing in place. A way has been suggested. Therefore, if inputting lattice consonants and double consonants by pressing "ㅡ" or "ㅣ" twice in succession is not applied, the vowel input technology of the present invention can be applied in all cases in order to provide consistency in use to the user. have. For example, if it is shown that the present invention is applied in the state where up to "each" is input, it is as follows.

Gak → Gag → Gago → Bridge

↘ (ㆍInput) → Bridge or Addition

Gak → Go → Go → Go → Shop

↘ (ㆍEnter) → Go →

The input of the rest of the vowels not exemplified is based on the existing method using the vowel elements "ㅡ", "ㆍ", and "ㅣ" and the vowel input rules suggested in the applicant's previous application (e.g. ㅢ=ㅡㅣ, ㅚ=ㅗㅣ, ㅘ =ㅗA, ㅙ=ㅗㅐ=ㅗ아ㅣ, ...) can be applied as already described in the present invention.

To summarize this:

In the method of inputting Korean vowels using three buttons arranged respectively for vowel elements "ㅡ", "ㆍ", and "ㅣ" known as Cheonjiin,

"ㅣ" is recognized by pressing the "ㅣ" button once,

"ㅇ" is recognized by pressing the "ㅣ" button twice,

If "ㆍ" is pressed after the recognized "ㅕ", it is recognized as "ㅕ",

If "ㅣ" is pressed after the recognized "sh", it is recognized as "ㅔ",

“ㅡ” is recognized by pressing the “ㅡ” button once,

By pressing the "ㅡ" button twice, "ㅗ" is recognized,

If "ㆍ" is pressed after the recognized "ㅗ", it is recognized as "ㅛ" or "ㅘ",

Korean vowel input method on the keypad characterized by

In addition, the above may additionally include:

In the above,

If "ㆍ" is pressed after the recognized "ㅗ", it is recognized as "ㅘ",

When "ㅡ" is pressed after the recognized "ㅗ", it is recognized as "ㅛ"

Korean vowel input method on the keypad characterized by

In the above,

The pressing of the vowel button is the pressing of the vowel button after the consonants associated with or arranged in the "ㆍ" button are recognized as pressing the "ㆍ" button three times.

Korean vowel input method on the keypad characterized by

30. Improved handling of the delete button

30.1 Deletion button processing based on "perception unit"

In the current keypad input technology, the deletion (cancellation) logic of the character element unit is mainly applied. For example, if you press the "Delete" button while entering "E", it becomes "ㅇ". When entering "ㅔ" on the keyboard, press the "ㅔ" button once to enter it, so it is natural that the last input "ㅔ" is deleted and becomes "ㅇ". However, in the keypad including Fig. 4-*, "ㅔ" is input in combination like "ㅇ+ㅣ=ㆍㅣㅣ". For convenience, the process of inputting "e" with the vowel input method currently applied by Samsung Electronics is as follows. The right arrow indicates that "ㆍ", "ㅣ", and "ㅣ" are pressed, respectively.

ㅇ → ㅇㆍ → uh → eh

The user recognizes and inputs "ㅇ+ㅣ". Therefore, deletion logic in recognition units can be applied. When the delete button is pressed in the state where "e" is input, "ㅣ" recognized as the last input is deleted to become "uh", and when the delete button is pressed once more, it becomes "ㅇ". If "a" is pressed in the "uh" state, it will be "billion".

In summary, the deletion logic is applied to the "recognition unit" in which the character elements are combined rather than the "character element unit". For some other examples, if "ㅇㅣㆍㅣ" is entered when "AE" is entered, the user recognizes that "ㅐ" has been entered with "A+ㅣ", so if the delete button is pressed once in "AE" state, "Ah" ", and when pressed once more, it becomes "ㅇ". When the delete button is pressed in the "A" state, it may be questioned whether it becomes "this". However, the unit recognized by the user is “A”, and “ㆍ” in “ㅣㆍ” is not an independent recognition unit.

As a representative example, the following is a case of deletion by cognitive unit when Samsung Electronics' vowel input method is applied, and it can be similarly applied to other cases of inputting vowels on the keypad. For example, it can be similarly applied to the technology of inputting "A" with the "ㆍ" button. The 10 basic vowels "아", "ㅑ", "sh", "ㅕ", "ㅗ", "ㅛ", "ㅜ", "ㅠ", "ㅡ", and "ㅣ" are all cognitive units, so It is deleted by pressing the delete button once. For convenience, only one case that is the same as the operation of the existing double keyboard is indicated. The right arrow (→) below means that the delete button is pressed, and the same applies to similar cases below.

ㅔ → ㅔ → All deleted

ㅐ → A → All deleted

A → All deleted

ㅇ → All deleted

. . .

ㅝ → ㅜ → All deleted (same as the existing 2-beol keyboard)

ㅞ → ㅝ → ㅜ → All deleted

ㅒ → ㅑ → all deleted

ㅙ → ㅘ → ㅗ → all deleted

Representative cognitive units in keypad Korean input may include the following. "ㅔ" is mainly entered as a combination of "ㅇ" and "ㅣ". Therefore, "ㅇ" and "ㅣ" can be separate cognitive units. "ㅐ" is usually entered as a combination of "아" and "ㅣ". Therefore, "A" and "ㅣ" can be separate cognitive units. In the case of "ㅙ", since it is entered as a combination of "ㅗ", "아", and "ㅣ", each can be a separate recognition unit. Since "ㅞ" is also entered as a combination of "TT", "sh", and "ㅣ", each can be a separate recognition unit.

30.2 Recombination of inputted characters after pressing delete button

There may be another application in the deletion logic by pressing the delete button. The following is the case of application of the 2-bit Hangul automata on the current PC. The right arrow (→) includes the delete button being pressed, the same in the case below.

Kana → Kana a → Kana → A → . . .

Examples of transforming automata that have recently been applied to smartphones are as follows.

KanaDa → GaKit → Kana → Gan → A → A

The characteristic is that when the neutral vowel is deleted and only the initial consonant remains, if it can become the final consonant of the initial letter, it is combined with the final consonant of the initial letter. As a similar example, if the delete button is pressed once in "grinding", it becomes "gnawing". When the above "gan" is reached, when "a" is pressed, it becomes "gani", and when "ㅣ" is pressed, it becomes "gani". This can be one of the elements that give flexibility in correcting typos. However, the user was psychologically "expecting" that the user clicked the delete button on "Kanada" to become "Kanad", but becoming "Ganada" could be a confusing factor. If the user wanted to input "thin", press the delete button once and immediately add "da". However, if you want to modify it to "Ganard", it can be embarrassing because it becomes "Ganard", which is different from what you expected.

Therefore, an intermediate form is suggested. For example:

Ganora → Ganod → Kano → Gb → G → A

Even if the character being finally input is deleted by continuously pressing the delete button, the input token does not break and the character can be recombined. When the neutral vowel is deleted, the initial consonant is not combined with the final consonant of the preceding will be. At the same time, if the button press newly pressed after entering the delete button can be combined with the remaining letters, it is combined. For example, if "ㅇ" is pressed in the "Kano" state, it becomes "Ganon", and if "ㅣ" is pressed in the "Gano" state, it becomes "Ganeoe". This may provide flexibility when using the delete button with less confusion to the user.

31. Means for Disambiguation

31.1 English, etc. common

For convenience, an example of English is given below, but the same can be applied to other languages.

When applying the repeated selection method (multi-tap method) in Fig. 1-1 (standard English keypad), the input value "222" explains in the previous application that there is ambiguity such as "aaa", "ab", "ba", "c" did Previously, there were two ways to input "ab" instead of "aaa", "ba", and "c". As described in the previous application, after pressing "2" to input "a" and after a predetermined time elapses and "a" is confirmed, "22" can be pressed to input "b". That is, it is a classification method by time delay, and for convenience, it will be called "time delay method" or "timer method". Another method is to press "2" to input "a", press a predetermined classification button (eg [#] button) to confirm "a", and then press "22" again to input "b". it was to become That is, it is an artificial method by pressing a classification button, and for convenience, it will be referred to as a “classification button method”.

In the applicant's previous application (26.1.1), it was pointed out that in order to input "acb" without ambiguity, you can do something like "2 2~22 2~2" ("2~" means pressing and holding the [2] button). . In addition, it was said that the input value "2" for inputting the first "a" can be input by long pressing. That is, when alphabets arranged (or related) on the same button are continuously input, the first input value for inputting the alphabet after the second (ie, including the third, fourth, ...) is pressed and held. If you were to type "abc", it would be something like "2 2~2 2~22". For readability, it is expressed by putting a space between input values (eg "2", "2~2", "2~22") representing one alphabet (eg "a", "b", "c") However, blanks do not have any meaning at all, and this is the same in the following.

Looking at this process in more detail: In the repeated selection method, "a" can be entered by the input value "2", so it can be expressed as "a = 2". Similarly, it can be expressed as “b = 22” and “c = 222”. Therefore, it can be expressed as "abc = 222222". However, "222222" can be either "bbb" or "cc". In the applicant's earlier application, long press the first input value of "222" to input "c" following "a", and then press the first input value of "22" to input "b" following "c" It is treated as a long press. When the alphabets assigned to the same button come out in succession, processing by long pressing the first input value of the next alphabet is called "post-alphabet processing" for convenience. More precisely, it can be called "the first (first) button long hit processing of the trailing alphabet", but it is simply called "the trailing alphabet long hitting processing".

Next, as a similar case, an example of inputting "cab" by another method is shown. In the previous application, when the alphabets assigned to the same button appear consecutively, the first alphabet appears as it is, and then it was shown that it can be input by long-pressing the alphabet. However, it shows that the first alphabet can be entered by long hitting. For example, when entering "cab", the input value can be "222~ 2~ 22". It is input by pressing and holding the last input value constituting the preceding alphabet. Spaces in the notation of input values "222~ 2~ 22" are included to improve the readability of those who read this patent document, and the spaces have no meaning. Of course, when entering "cd", you can do something like "222 3", and you do not have to press and hold it. Similarly, when inputting "cad", a long press is applied only to the input of "c", such as "222~ 2 3", and there is no need to use a long press when inputting "a". This is because "a" is followed by "d", which is not an alphabet arranged on the same button. Similarly, for convenience, this is referred to as "last (last) button long hit processing of preceding alphabet", and will be more simply called "preceding alphabet long hitting processing".

When this repeated selection method is applied, when using a long hit to the input of the preceding alphabet (eg "ca" to "c") to eliminate ambiguity, the last input value must be treated as a long hit, and the trailing alphabet (eg "ac" It is important to treat the first input value as a long hit when removing ambiguity by using a long hit for the input of "c") in . The "preceding alphabet sluggish processing" and the "later alphabet sluggish processing" cannot be applied simultaneously, but one of them is selectively applied. When implemented as a program, the user can select and use one of the two in "environment setting".

31.2 Means for inputting Korean archaic language (old Hangul) and removing ambiguity

The present invention proposes a method for inputting both modern Korean and Hangul archaic characters. It is stated in advance that the information described below is a technology that can be applied not only to the keypad of Figure 4-* but also to other types of keypads and PC keyboards.

Figure 4-33 (a) to Figure 4-33 (c) show the Korean language that was added as Unicode in 2007. In the above drawing, the part marked with a yellow background is a newly added letter. All characters in Fig. 4-33(a) to Fig. 4-33(c) are currently confirmed as Unicode, and Fig. 4-33(d) to Fig. 4-33(f) are Unicode v6. It shows that it is registered as 0. As such, Unicode characters are continuously being added through revision. The present invention proposes a technology capable of efficiently inputting Korean archaic words, and it is revealed that a method of expressing Korean alphabetic characters including Korean archaic words in a computer is not a subject of the present invention. The problem of how to handle Korean Gore in a compatible way with Unicode-complete Hangul on computers (PCs, smartphones, mobile phones, etc.) will be a "super-large national project" that requires additional research. For reference, as a representative method of expressing Hangul letters combined with Korean alphabets, including Korean archaic words, "end combination type" is known, and in any other method (ie, Unicode completion type, start combination type, ...), the input of the present invention technology can be applied.

31.2.1 Input of Korean old consonants

In the previous application of the applicant, some methods of inputting Korean archaic words were introduced. The following is a summary of the case of inputting Korean language on the keypad of Fig. 4-*. In the present invention, displaying the input value as a "Korean button value" (eg, "ㄱㅡㅡ", etc.) rather than a "number button value" (eg, "1**", etc.) increases readability and makes it easier for readers to read this document. It is for the convenience of the people, and it is revealed in advance that the contents are completely the same. First of all, in the previous application, for the input of "y", the original technology of inputting "y = xㅡㅡ" or "z = xㅣㅣ" was presented. For example, "ㅋ = ㄱㅡㅡ", "P = ㄴㅡㅡ" were entered. In addition, it was shown that even Korean language can be input by doing something like "ㅸ = プㅡㅡ = ㄴㅡㅡㅡㅡ". For convenience, this will be referred to as a "control processing method using a vowel button". While maintaining the keypad of Figure 4-* as it is, it is possible to input even the related Korean archaic consonants naturally. Looking at the similarity with the representative sound, the flat consonant "ㅅ", "ㅸ" may have a stronger similarity than "P", but modern Korean input is given priority and Korean archaic words can be additionally processed.

)은 서로 바뀌어서 구성될 수도 있다. Priority is given to the input of modern Korean, and an example of processing even archaic consonants by the control processing method using the vowel button is shown in Figure 4-34 (a). In Unicode, newly discovered Korean archaic (old Korean) characters are continuously added, so other alphabets may be added in addition to Figure 4-34 (a), but input is possible with a configuration similar to Figure 4-34 (a). It is possible. In Figure 4-34 (a), the first pair of pairs (ㆀ) and the second pair of pairs (ㆀ)

) may be configured interchangeably.

In "ㅸ = ㅡㅡ", "y" is "ㅸ", and "x" is "P". Likewise, "ㅹ = ㅃㅣㅣ = ㄴㅣㅣㅣ". In the above, the consonant marked on the left under the flat consonant (eg "ㄱ") (eg "ㅋ") is entered by pressing the "ㅡ" button twice, and the consonant marked on the right (eg "ㄲ") is " It can be input by a combination of pressing the ㅣ" button twice. In the above example, the [ㅡ] button or the [ㅣ] button may be changed and applied. For the alphabet to be "primary combination", press the "ㅡ" or "ㅣ" button twice consecutively after the plain consonant, and for the alphabet to be "secondary combination", press the "ㅡ" or "ㅣ" button next to the first combination. This is pressed twice in succession, and the “3rd combination” alphabet is followed by the “ㅡ” button or the “ㅣ” button two times in succession after the second combination alphabet. As a result, the “ㅡ” or “ㅣ” button in the “secondary combination” is continuously pressed four times. It is pressed 6 times in the 3rd combination and 8 times in the 4th combination.

" 와"

" (및 "

" 와"

"가 포함된 한글 고어 모음)를 각각 [ㅡ]버튼 2번 누름과 [ㅣ]버튼 2번 누름으로 입력하지 않고 다른 수단(예. 각각 [ㅡ]버튼 길게 누름, [ㅣ]버튼 길게 누름)으로 입력하는 경우에 가능하다. 만약 "

" 와"

"를 각각 [ㅡ]버튼 2번 누름과 [ㅣ]버튼 2번 누름으로 입력한다면, "y = x +(최대반복누름 가능횟수+1회)" 로 하여야 하므로, "ㅋ = ㄱㅡㅡㅡ" 와 같이 된다. "

= ㄱㅡㅡ"로 되고, 한글고어에서도 자음 다음에 모음 "ㅡ"가 연속하여 3번 나오는 경우는 없으므로, "최대반복누름 가능횟수" 는 정상적으로 한국어 자모결합글자를 이루는 최대횟수로써 2회가 된다. 이를 적용하면, 도면 4-34(a)에서 "ㅡ" 또는 "ㅣ"가 조합되는 횟수는 각각 3회씩 된다. As described above, the combination of pressing the [ㅡ] button or the [ㅣ] button 2 times, 4 times, 6 times, and 8 times, respectively, is one of the Korean Gore collections.

"Wow"

" (and "

"Wow"

A collection of Korean words that contain "") by pressing the [ㅡ] button twice and pressing the [ㅣ] button twice, respectively, but by other means (e.g. long-pressing the [ㅡ] button, long-pressing the [ㅣ] button) It is possible if you type in. If "

"Wow"

If you enter " by pressing the [ㅡ] button twice and pressing the [ㅣ] button twice, respectively, "y = x + (maximum number of repetitions + 1 time)", so "ㅋ = ㅡㅡㅡ" It becomes like."

= ㅡㅡ", and since there is no case where the vowel "ㅡ" appears three times in succession after a consonant even in Korean archaic language, the "maximum number of repetitions possible" is normally 2 times as the maximum number of Korean consonant combinations. If this is applied, the number of times "ㅡ" or "ㅣ" is combined in Fig. 4-34(a) is 3 times, respectively.

", "

", ...)에 대해서만 [ㅡ]버튼 또는 [ㅣ]버튼의 3회 눌러짐의 조합으로 입력할 수 있는 기술은 아래 "한글고어 모음의 입력 및 모호성 제거 수단" 에서 따로 설명한다. 이하에서는 1차조합되는 알파벳(예. "ㅋ")은 [ㅡ]버튼 또는 [ㅣ]버튼 2번 눌러짐이 적용되고, 2차조합 또는 그 이상 차수로 조합되는 알파벳은 [ㅡ]버튼 또는 [ㅣ]버튼의 3번 눌러짐이 적용되는 것으로 사례를 제시한다. In the future, there may come a time when archaic Hangul is used in keypad Korean input, but even if that time comes, it will be used much less than modern Korean characters. Therefore, at least modern Korean consonants (eg "ㅋ") can be input with a combination of pressing the [ㅡ] button or the [ㅣ] button twice, and in Fig. ."

", "

The technique that can be input by pressing the [ㅡ] button or the [ㅣ] button three times only for ", ...) will be separately described in "Means for inputting Korean vowels and removing ambiguity" below. Alphabets that are combined in the first order (eg "ㅋ") are applied by pressing the [ㅡ] button or [ㅣ] button twice, and in the alphabets that are combined in the second order or higher order, the [ㅡ] button or [ㅣ] An example is presented in which the button is pressed three times.

"은 유니코드에는 포함되어 있지 않으나, 일부 프로그램에서는 사용되고 있다. 먼저 여린히읗 "ㆆ = ㅇㅡㅡ" 로 입력한 후, [ㅣ]버튼을 2번 누르면 "

"가 되고, [ㅡ]버튼이 한번 더 눌러지면 (즉, "ㆆㅣㅣㅣ = ㅇㅡㅡㅣㅣㅣ") "

" 가 인식될 수 있다. 또는 여린히읗 "ㆆ = ㅇㅡㅡ" 로 입력된 후, [ㅡ]버튼이 3번 눌러지면 (즉, "ㆆㅡㅡㅡ = ㅇㅡㅡㅡㅡㅡ") "

"로 처리될 수 있다. 옛이응과 쌍이응의 입력사례를 더 보이면, 쌍이응 "ㆀ = ㅇㅣㅣ"로 입력되고, 옛이응 "

= ㆀㅣㅣㅣ = ㅇㅣㅣㅣㅣㅣ" 로 될 수 있다. "

" is not included in Unicode, but is used in some programs. First, softly enter "ㆆ = ㅇㅡㅡ" and then press the [ㅣ] button twice to "

", and when the [ㅡ] button is pressed once more (ie, "ㆆㅣㅣㅣ = ㅇㅡㅡㅣㅣㅣ") "

" can be recognized. Or, after entering softly "ㆆ = ㅇㅡㅡ", if the [ㅡ] button is pressed 3 times (ie, "ㆆㅡㅡㅡ = ㅇㅡㅡㅡㅡㅡ") "

" can be processed. If you show more input examples of the old and the double, the pair is input as "ㆀ = ㅇㅣㅣ", and the old is "

= ㆀㅣㅣㅣ = ㅇㅣㅣㅣㅣㅣ”.

In the current PC keyboard input, "ㅸ" is a combination of "ㅅ" and "ㅇ", "ㅱ" is a combination of "ㅁ" and "ㅇ", and "ㅹ" is a combination of "ㅃ" and "ㅇ". do it too Since this can also be equally applied to keypad input, in Fig. 4-34 (a), these alphabets (eg "ㅸ") are expressed by putting them in round brackets. In this case, ambiguity may occur, which can be resolved by the method suggested below.

"를 허용하지 않을 경우) 또는 "ㆅ = ㅎㅣㅣㅣ" ("

"를 허용할 경우)로 입력할 수 있다. In the keypad case of 4-*, "ㅎ" is explicitly or implicitly assigned to the [0] button, but "ㅎ" cannot be entered by pressing the [0] button once. (Except for special cases presented in the earlier application) The earlier application states that "ㅎ = ㆍㅡㅡ" or "ㅎ = ㅇㅡㅡ" can be entered. In terms of logic, it may feel natural to type in "ㆆ = ㅇㅡㅡ", but it is revealed that it can be done with "ㅎ = ㅇㅡㅡ" by giving priority to modern Korean. In Fig. 4-34 (a), it is expressed as if there is a separate [ㅎ] button, but as in the keypad of Fig. Similarly, "ㅎ" can be entered with a combination of buttons. If you do "ㆆ = ㅇㅡㅡ", you can do it with "ㅎ = ㆍㅡㅡ" or "ㅎ = ㆍㆍㆍ". "ㆅ = ㅎㅣㅣ"("

") or "ㆅ = ㅎㅣㅣㅣ"("

" if allowed).

4-34(b) is an example of a case in which the remaining consonants are input by repeatedly pressing the flat consonant button (ie, by the repeated selection method). 4-34(b), it is obvious that the order of alphabets input by pressing the button twice or more can be appropriately modified. Similarly, in Fig. 4-34 (b), it is expressed as if "ㅎ" is input by pressing the [ㅎ] button once, but as in the keypad of Fig. 4-*, "ㅎ" is input by pressing any button once. If it is not possible, you can enter "ㅎ" with a combination of buttons as suggested in the previous application. For example, if you input "ㅎ = ㆍㅡㅡ", it becomes "ㆅ = ㆍㅡㅡ ㆍㅡㅡ", which is expressed as "press twice" in Fig. 4-34 (b).

Looking at Fig. 4-34 (a) and Fig. 4-34 (b), only the combination method (eg, application of "control processing method using vowel button" and application of "3+ other input method") is different, but the basic alphabet (eg, It can be seen that there is a commonality in composing alphabets related to flat consonants) in a consistent form. Looking at the characteristics of the configuration presented in Fig. 4-34 (b), by applying "3 + other input method", in order to process the case where the same plain consonant appears consecutively as a final consonant and a leading consonant in modern Korean, plain consonants The biggest feature is that when the button is pressed twice in succession, two flat consonants are produced. Of course, as shown in parentheses in Fig. 4-34 (b), when the flat consonant button is pressed twice, it can be a light consonant (double consonant), but if a vowel is input next, it becomes two flat consonants. In Figure 4-34 (b), among the alphabets input by pressing three or more times, the Korean archaic alphabet, which is not a modern Korean consonant, will actually have a significantly lower frequency of use.

It was pointed out that all of the keypads of 4-* of the present invention are compatible, and the [ㆍ] button may be displayed in a shape representing [A] or “A”, and input “A” by pressing the [ㆍ] button once. Since it has been revealed that it can be done, in the above or following description, the input value "ㆍ" may be replaced with the input value "A", but for the sake of readability and convenience of the present invention, "A" by pressing the [ㆍ] button once Even when inputting, the input value is expressed as "ㆍ".

31.2.2 Means for removing ambiguity when inputting modern Korean and Korean archaic consonants

In modern Korean, two or more consonants do not occur consecutively as initial consonants. For example, forms such as "ㅦ" and "ㅳ" do not appear as initial consonants. In modern Korean, hard consonants (morphologically, twin consonants) are considered as one grapheme. "ㄲ" is also entered as "shift + ㄱ" on the PC's keyboard. Therefore, when the vowel button is pressed after the final consonant is input, one consonant that can be the initial consonant among the previously input final consonants becomes the initial consonant of the next letter. For example, if "ㅣ" is pressed after "scratch", it becomes "writing". This is the basics of the modern Korean double-syllabic automata (ie, "two-syllabic Korean consonant combination rule") currently used by Koreans.

" 를 입력하면 현대 한국어 오토마타에서는 "간다"로 된다. 즉 바꾸어 말하면, 동일한 입력값에 대하여 "

"와 "간다"로 될 수 있는 모호성이 있는 것이다. 이는 초성자음 위치에 따른 모호성이므로 편의상 "초성자음위치 모호성"이라고 부를 수 있다. 물론 현대 한국어의 입력을 우선해야 하므로 단순히 연속입력하였을 경우는 "간다"로 되는 것은 당연하다. 그렇다면, "

"를 입력하기 위하여 기존 테크닉을 적용하면, "가"를 입력한 후 소정의 시간이 경과하면 "가" 라는 글자가 확정되도록 한 다음 "

"를 입력하면 된다. 또는 "가"를 입력한 다음 글자의 종료를 확정하는 "구분버튼"을 눌러 "가"를 확정한후 "

"를 입력하면 된다. 이 경우 "ㄴ"과 "ㄷ"의 연속입력이 초성자음 "ㅦ" 으로 되는 것은 한글고어를 포함하는 2벌식오토마타(한글조합규칙)이 적용되므로 자명한 것이다. Consonants made up of combinations of consonants (eg, ㅦ, ㅫ, .., etc.) are naturally preferably entered as a combination of each consonant. (Ex. "ㅦ = ㄴ+ㄴ") However, "

If you enter ", it becomes "go" in modern Korean automata. In other words, for the same input value, "

There is an ambiguity that can be "and" goes. This is an ambiguity according to the position of the initial consonant, so it can be called "ambiguity in the position of the initial consonant" for convenience. It is natural to be "going". Then, "

Applying the existing technique to input ", after a predetermined time elapses after entering "A", the character "A" is confirmed, and then "

You can enter ". Or, after entering "a", press the "separate button" to confirm the end of the letter, confirm "a", and then "

In this case, it is obvious that the continuous input of "b" and "c" becomes the initial consonant "ㅦ" because the double-acting automata (Korean combination rule) including Korean archaic is applied.

= ㄱㅣㆍ~ㄴㄷㅣㆍ" 또는 "

= ㄱㆍ~ㄴㄷㆍ"로 입력하는 것이다. The present invention proposes a technology that enables this without using a division button. As mentioned in the previous application, "x ~" means long pressing the [x] button. First, when entering "a", the letter "a" is confirmed by long pressing the last input button, and then the initial consonant "ㅦ" is input by inputting "b" and "c". For example, if you enter "a" as "ㅣㆍ", press and hold "ㆍ" to confirm the letter "ga", and the next input is processed as the initial consonant of the next letter, not the final consonant of "ga". . That is, pressing and holding "ㆍ" in "ㄱㅣㆍ" (ie, the input value "ㄱㅣㆍ~"). If you input "a" by pressing the "ㆍ" button once, you press and hold "ㆍ" in "ㄱㆍ" (ie, the input value "ㄱㆍ~"). This is similar to the "preceding alphabet sluggish processing" described above. Expressed as an expression, "

= Aㅣㆍ~ㄴㅇㆍ" or "

= Aㆍ~ㄴㅇㆍ” is entered.

= ㄱㅣㆍㄴ~ㄷㅣㆍ" 또는 "

= ㄱㆍㄴ~ㄷㆍ"로 입력하는 것이다. "ㄴ"을 입력하기 위한 버튼을 길게 누름으로써, "ㄴ"이 "가"의 받침이 아닌 다음 글자의 초성자음임을 명시화해주는 것이다. 이는 상기 설명한 "후행알파벳장타처리"와 유사하다. 다만, 길게누름에 의하여 입력되는 글자(예. "ㄴ")가 다음 글자의 초성자음임을 명시화하는 것이다. 현대 한국어만을 처리한다면, "ㄴ"에 이어서 "ㄷ"을 입력하는 것이 "ㄴㄷ"으로 2개의 낱자음이 입력되겠지만, 한글고어의 입력을 포함하는 2벌식 오토마타를 적용한다면 "ㄴ"과 "ㄷ"의 입력이 "ㅦ"으로 되는 것은 당연한 것이다. Next, after entering "a", press and hold (long hit) the initial consonant "b" of the next letter. Expressed as an expression, "

= ㄱㅣㄴㅇㅇㆍ" or "

= ㄱㆍㄴ~ㄴㆍ”. By pressing and holding the button to input “ㄴ”, it is specified that “ㄴ” is not the base of “가”, but the initial consonant of the next letter. This is It is similar to the described "Long Hit Processing of Trailing Alphabets". However, it is specified that the letter input by long pressing (eg "b") is the initial consonant of the next letter. If only modern Korean is processed, "b" is followed by "b" Although inputting "ㅅ" will result in two consonants being input as "ㄴㄴ", it is natural that the inputs of "ㄴ" and "ㄴ" become "ㅦ" if we apply the two-beol type automata that includes the input of Korean language. .

" 으로 될 것이다. 물론 그 다음 모음(예. "ㅏ")이 입력되면 "간다"와 같이 현대 한국어 2벌식 오토마타가 적용되는 것 역시 당연한 것이다. If "ㄱㅣㄴㄴ" or "ㄱㆍㄴㄴ" is pressed without a long press as above, "ㅦ" becomes the final consonant in the 2-beol type automata that supports Hangul Gore.

". Of course, when the next vowel (eg "a") is entered, it is also natural that the modern Korean double-beol automata is applied, such as "go".

In the previous application of the applicant, a technique for inputting modern Korean without ambiguity was presented, and a technique for inputting modern Korean with very little ambiguity was presented. For example, when the flat consonant button (eg, the [a] button) is repeatedly pressed, "a - ㄱㄱ - ㅋ - ㄲ" is said to have ambiguity about once in about 1000 character inputs. In the case of "chicken skewers", there may be ambiguity if the initial consonant "ㄲ" comes after the "ㄱ" base. If the preceding alphabet long hit processing is applied, when “a” of “chicken” is input, the letter “chicken” is confirmed by long pressing, and when the same [a] button is pressed next, it is processed as a consonant, so that input without ambiguity is achieved. It is possible. If the trailing alphabet sluggish processing is applied, when the [a] button is pressed for a long time after inputting "chicken", it is specified that the initial consonant starts without being combined with the "a" of the previously input "chicken". Subsequently, if the [a] button is pressed once more, the initial consonant "ㄲ" is recognized, if it is pressed once more, it is recognized as the initial consonant "ㅋ", and if it is pressed once more, it is recognized as the initial consonant "ㄲ".

31.2.3 Means for Inputting Korean Vowels and Eliminating Ambiguity

Modern Korean vowels consist of 21 vowels, but in the case of archaic languages, there are much more diverse types of vowels. There are various forms, but most of them are in the form of diphthongs or double vowels, so it is possible to input with a combination of basic vowels. First, looking at the number of vowels, there are 71 vowels from Unicode 1161 to 11A7 in Figure 4-33 (*) (50 ancient vowels excluding 21 vowels in modern Korean), and in Figure 4-33 (*) There are 23 vowels from Unicode D7B0 to D7C6, and 94 Korean vowels have been registered in Unicode v6.0 so far, including 21 modern Korean vowels. The following is a summary of the vowels among the Korean alphabets included in the Unicode of Figure 4-33 (*) so that they can be easily seen at a glance.

In the above (2), "ㅣㅕ" means a vowel that is a combination of "ㅣ" and "ㅕ", and "ㅣㅖ" means a vowel that is a combination of "ㅣ" and "ㅖ". Based on the PC keyboard, most vowels can be input as a combination of vowels on the keyboard (eg, vowels that can be input by pressing a button on the keyboard once or pressing simultaneously with shift).

First, when inputting a vowel as a combination of three vowel elements "ㅡ", "ㆍ", and "ㅣ" known to the general public as "ㆍ" without entering "a" with the [ㆍ] button (for convenience) Looking at the Korean vowel input of the "Area 3 vowel method") is as follows. If you input up to the Korean vowel, pressing the [ㆍ] button once will enter the Korean vowel "Aeraeah". This is the content already presented in the applicant's earlier application. When the [ㆍ] button is pressed twice, a vowel (Unicode 11A2 vowel, 5th row, 5th vowel in (2) above) with two lower words attached to the left and right is input. An example is shown as follows, and the same can be applied to cases that are not illustrated.

= ㅣㆍㆍㅡ ("

"와 모호성 있음)

= ㅣㆍㆍㅡ ("

"with ambiguity)

= ㅣㆍㅡㆍ

= ㅣㆍㅡㆍ

= ㅣㆍㆍㆍㅡ

= ㅣㆍㆍㆍㅡ

= ㅣㆍㆍㆍㆍㅡ

= ㅣㆍㆍㆍㆍㅡ

= ㆍㅣㆍㅡ

= ㆍㅣㆍㅡ

= ㆍㅣㅡㆍ

= ㆍㅣㅡㆍ

= ㆍㅣㅡ

= ㆍㅣㅡ

= ㆍㆍㅣㆍㅡ

= ㆍㆍㅣㆍㅡ

= ㆍㆍㅣㅡㆍ

= ㆍㆍㅣㅡㆍ

= ㆍㅣㆍㅡ

= ㆍㅣㆍㅡ

= ㆍㅣㅣㆍㅡ

= ㆍㅣㅣㆍㅡ

= ㆍㆍㅣㅣㆍㅡ

= ㆍㆍㅣㅣㆍㅡ

= ㆍㅡㆍㅡ

= ㆍㅡㆍㅡ

= ㆍㅡㅡㆍ

= ㆍㅡㅡㆍ

= ㆍㆍㅡㅣㆍㆍ

= ㆍㆍㅡㅣㆍㆍ

= ㆍㆍㅡㅣㆍㆍㅣ

= ㆍㆍㅡㅣㆍㆍㅣ

= ㆍㆍㅡㆍㆍㅣ

= ㆍㆍㅡㆍㆍㅣ

= ㆍㆍㅡㆍㅡ

= ㆍㆍㅡㆍㅡ

= ㆍㆍㅡㅣ

= ㆍㆍㅡㅣ

= ㅡㆍlㆍ

= ㅡㆍlㆍ

= ㅡㆍlㆍl

= ㅡㆍlㆍl

= ㅡㆍㆍㅣㅡ

= ㅡㆍㆍㅣㅡ

= ㅡㆍㆍㆍㅣㅣ

= ㅡㆍㆍㆍㅣㅣ

= ㅡㆍㅡㆍ

= ㅡㆍㅡㆍ

= ㅡㆍㆍㅣㆍ

= ㅡㆍㆍㅣㆍ

= ㅡㆍㆍㆍㅣ

= ㅡㆍㆍㆍㅣ

= ㅡㆍㆍㆍㅣㅣ

= ㅡㆍㆍㆍㅣㅣ

= ㅡㆍㆍㆍㆍㅣ

= ㅡㆍㆍㆍㆍㅣ

= ㅡㆍㆍㆍㆍㅣㅣ

= ㅡㆍㆍㆍㆍㅣㅣ

= ㅡㆍㆍㅡㆍ

= ㅡㆍㆍㅡㆍ

= ㅡㆍㆍㅣ("ㅝ"와 모호성 있음. 별도 설명)

= ㅡㆍㆍㅣ(There is ambiguity with "ㅝ". Explain separately)

= ㅡㅡㆍ

= ㅡㅡㆍ

= ㅡㅡ

= ㅡㅡ

= ㅡㅣㅡㆍ

= ㅡㅣㅡㆍ

= ㅣㅣㆍ

= ㅣㅣㆍ

= ㅣㅣㆍㆍ

= ㅣㅣㆍㆍ

= ㅣㆍㅡ ("

"와 모호성 있음)

= ㅣㆍㅡ ("

"with ambiguity)

= ㅣㅡㆍ

= ㅡㆍ

= ㅣㅡ

= ㅡ

= ㅣㆍ ("ㅏ"와 모호성 있음. 별도 설명)

= ㅣㆍ (There is ambiguity with "a". Separate explanation)

= ㆍ

= ㆍ

= ㆍㆍㅣ ("ㅕ"와 모호성 있음. 별도 설명)

= ㆍㆍㅣ (There is ambiguity with "ㅕ". Separate explanation)

= ㆍㅡㆍ

= ㆍㅡㆍ

= ㆍㅣ ("ㅓ"와 모호성 있음. 별도 설명)

= ㆍㅣ (There is ambiguity with "sh". Separate explanation)

= ㆍㆍ

= ㆍㆍ

= ㅣㆍㅡ ("

"와 모호성 있음)

= ㅣㆍㅡ ("

"with ambiguity)

= ㅣㆍㆍㅡㆍ

= ㅣㆍㆍㅡㆍ

= ㆍㆍㅣㅣㆍㆍ

= ㆍㆍㅣㅣㆍㆍ

= ㆍㅡㅣㆍㆍ

= ㆍㅡㅣㆍㆍ

= ㆍㅡㅣㆍㆍㅣ

= ㆍㅡㅣㆍㆍㅣ

= ㆍㅡㆍㆍㅣ

= ㆍㅡㆍㆍㅣ

= ㆍㅡㅡㆍ (추가 설명 있음)

= ㆍㅡㅡㆍ (with additional explanation)

= ㆍㆍㅡㅣㆍ

= ㆍㆍㅡㅣㆍ

= ㆍㆍㅡㅣㆍㅣ

= ㆍㆍㅡㅣㆍㅣ

= ㅡㆍㆍㆍㅣ (참고 [ㆍ]버튼 3번)

= ㅡㆍㆍㆍㅣ (Reference [ㆍ] button 3)

= ㅡㆍㅣㅣ ("

"와 모호성 있음)

= ㅡㆍㅣㅣ ("

"with ambiguity)

= ㅡ ㆍㆍㅣㆍㅣ

= ㅡ ㆍㆍㅣㆍㅣ

= ㅡ ㆍㆍㆍㅡ (참고 [ㆍ]버튼 3번)

= ㅡㆍㆍㆍㅡ (Note [ㆍ] button 3)

= ㅡㅣㆍ

= ㅡㅣㆍ

= ㅡㆍㅣ ("ㅟ"와 모호성 있음)

= ㅡㆍㅣ (there is ambiguity with "ㅟ")

= ㅡㆍㅣㅣ ("

"와 모호성 있음)

= ㅡㆍㅣㅣ ("

"with ambiguity)

= ㅡㆍㅡ

= ㅡㆍㅡ

= ㅣㅣㆍㆍㆍㅡ (참고 [ㆍ]버튼 3번)

= ㅣㅣㆍㆍㆍㅡ (Note [ㆍ] button 3)

= ㅣㅣㆍㆍㅣ

= ㅣㅣㆍㆍㅣ

= ㅣㆍㆍㅣ ("ㅒ"와 모호성 있음)

= ㅣㆍㆍㅣ (There is ambiguity with "ㅒ")

= ㅣㆍㆍㅣㅣ

= ㅣㆍㆍㅣㅣ

= ㆍㅣㅡㆍ

= ㆍㅣㅡㆍ

= ㅣㆍㆍㅡ ("

"와 모호성 있음)

= ㅣㆍㆍㅡ ("

"with ambiguity)

= ㅣㅡㆍㆍ

= ㅣㅡㆍㆍ

= ㅣㅣ

= ㅣㅣ

= ㆍㅣㆍ

= ㆍㅣㆍ

= ㆍㆍㅣㅣ ("ㅖ"와 모호성 있음. 별도 설명)

= ㆍㆍㅣㅣ (There is ambiguity with "ㅖ". Separate explanation)

. . . . . .

"를 입력하기 위하여 " ㅣㆍㅡ"까지 입력하였을 때, "ㅏ"와 "ㅡ"가 결합된 모음이 없으므로 "ㅏㅡ"로 일시적으로 되었다가 [ㆍ]버튼이 눌러지면 전체 입력값 "ㅣㆍㅡㆍ"이 "

" 로 된다. 이는 다른 유사한 경우에 있어서도 동일하게 동작할 수 있다. There may be more cases where there is ambiguity in the above, but it can be applied similarly to the description below. In the case of inputting 21 modern Korean vowels using the combination of "ㅡ", "ㆍ", and "ㅣ", complete vowels were always combined without ambiguity even in the middle of input. However, in the case of inputting up to Korean vowels, complete vowels may not be made in the middle of input. For example "

When you input up to "ㅣㆍㅡ" to input ", since there is no vowel combined with "A" and "ㅡ", it temporarily becomes "ㄴㅡ", and when the [ㆍ] button is pressed, the entire input value "ㅣㆍ ㅡㆍ"Lee"

". This may work in the same way in other similar cases.

In the case of inputting a Korean vowel as a combination of three vowel elements, there may be two or more vowels for the same input value. Some examples include:

= ㅡㆍㆍㅣㅝ =

= ㅡㆍㆍㅣ

= ㅣㆍA =

= ㅣㆍ

= ㆍㅣㅇ =

= ㆍㅣ

= ㆍㆍㅣㅕ =

= ㆍㆍㅣ

= ㆍㆍㅣㅣㅖ =

= ㆍㆍㅣㅣ

. . . . . .

" 의 입력시, 기존의 시간지연(즉, 타이머) 기법을 적용한다면 "ㅠ"까지 입력하고 소정시간 경과하여 "ㅠ"가 확정된 다음 "ㅣ" 를 눌러 "

"를 입력하게 된다. 또한 구분버튼을 사용한다면 "ㅠ"입력후 구분버튼을 눌러 "ㅠ"를 확정후 "ㅣ"를 눌러 "

"를 입력하게 된다. 기존에는 "ㅠ"입력후 구분버튼 또는 시간지연 등의 수단으로 "ㅠ" 확정후 "ㅣ"를 누르면 "ㅠㅣ"와 같이 "ㅣ"가 낱자모음으로 입력되었으나, 한글고어 모음의 입력이 전제된 한글조합규칙 적용시 "

"로 조합되어야 한다. 출원인이 설명했던 "선행알파벳장타처리"를 적용하면, "ㅠ"의 마지막 입력값인 "ㆍ"을 길게 눌러 "ㅠ"를 확정한 다음 "ㅣ" 를 눌러 "

"를 입력할 수 있다. 표현식으로 나타내면 "

= ㅡㆍㆍ~ㅣ" 가 된다. 또는 "후행알파벳장타처리"를 적용하면 "ㅠ" 다음에 눌러지는 [ㅣ]버튼을 길게 누름으로써 기 눌러진 "ㅡㆍㆍ"이 "ㅠ"로 인식하고 여기에 "ㅣ"가 결합되어 결과적으로 "

"가 되도록 할 수 있다. 표현식으로 나타내면, "

= ㅡㆍㆍㅣ~" 가 된다. 상기 "

", "

", "

", "

" 의 입력도 동일하게 처리할 수 있다. This can also be seen as "ambiguity" at the time of vowel input. For convenience, it may be called "ambiguity within the alphabet", and narrowly referred to as "ambiguity within the vowel". Since the input of modern Korean should be prioritized, it is natural that modern Korean vowels "ㅝ", "아", "sh", and "ㅕ" are input when the input value is pressed. "

When inputting ", if the existing time delay (i.e., timer) technique is applied, input up to "ㅠ" and after the predetermined time elapses, "ㅠ" is confirmed, and then press "ㅣ"

" is entered. Also, if you use the classification button, after inputting "ㅠ" and pressing the classification button to confirm "ㅠ", press "ㅣ" to "

" is entered. In the past, if you press "ㅣ" after inputting "ㅠ" and confirming "ㅠ" by means such as a classification button or time delay, "ㅣ" is input as a vowel like "ㅠㅣ", but it is an old Korean language. When applying the Korean combination rule, which presupposes the input of vowels, "

". If the "preceding alphabet long hit processing" explained by the applicant is applied, press and hold "ㆍ", the last input value of "ㅠ" to confirm "ㅠ", and then press "ㅣ" to "

You can type ". Expressed as an expression, "

= ㅡㆍㆍ~ㅣ". Or, if "trailing alphabet long hit processing" is applied, by long pressing the [ㅣ] button pressed after "ㅠ", the previously pressed "ㅡㆍㆍ" is recognized as "ㅠ" Here, "ㅣ" is combined, resulting in "

". Expressed as an expression, "

= ㅡㆍㆍㅣ~". Above "

", "

", "

", "

The input of " can be processed in the same way.

Next, while inputting a vowel with a combination of three vowel elements "ㅡ", "ㆍ", and "ㅣ", press the [ㆍ] button once to input "A", or "ㅡ", "ㄴ", "ㅣ" " If you look at the Korean vowel input using the three vowel buttons, it is as follows. For convenience, this will be referred to as "Aeraeah = A 3 vowel method". Hereinafter, the "a" ("a" input by pressing the [ㆍ] button once or "a" of the [a] button) is any other vowel (e.g. "sh", "ㅗ", "TT") , ...) is also the case. In the following description, for convenience, it is indicated by "•". As suggested in the previous application, to input the lower child alone, press the [ㆍ] button twice to input. In other Korean vowel combinations, the [ㆍ] button is used like a stroke “ㆍ” that is combined as it is. For example, "sh = ㆍㅣ" is entered as "ㅕ = ㆍㆍㅣ". It is the same as the case of inputting a Korean vowel with the three vowel buttons "ㅡ", "ㆍ", and "ㅣ" (in case of inputting "ㆍ" with the [ㆍ] button), or "ㅣ" for inputting "ㄴ". The description is also omitted when “ㆍ” is simply replaced with “ㆍ”. The input case is almost similar to that in the "Area 3 vowel method", so it is not presented separately.

"의 입력시, "ㅏ"를 "ㆍ"으로 입력하는 것을 적용하면 "

"의 입력값은 "ㆍㆍㅡ"가 되는데, 이는 현대 한국어 모음의 "ㅑ"와 같게 된다. (즉 "

"와 "ㅑ"의 모호성이 있게 되는 것이다. 현대 한국어의 입력을 우선하여 잘 작동하도록 하여야 하므로 "

"의 "ㅏ"는 "ㅣㆍ"로 입력하여 "

= ㅣㆍㆍㅡ" 로 되어야 한다. "

When inputting ", applying "a" to "ㆍ" inputs "

The input value of " becomes "ㆍㆍㅡ", which is the same as "ㅑ" in modern Korean vowels.

There is ambiguity between " and "ㅑ". Since modern Korean input must be given priority to make it work well, "

The "a" of "is entered as "ㅣㆍ" to "

= ㅣㆍㆍㅡ".

", "

", "

", "

", "

", "

", ...)의 아래아를 입력하는 방법에는 2가지가 있을 수 있다. 첫번째는 [ㆍ]버튼 1번 눌러짐으로 입력되도록 하는 것이며, 이는 상기 "아래아 3모음법" 에서와 동일하다. 또한가지 방법은 이렇게 형태적으로 아래아가 온전히 포함된 모음의 아래아부분은 [ㆍ]버튼 2번 눌러짐으로 입력되록 하는 것이다. "아래아=ㅏ 3모음법"에서의 한글고어 모음입력을 말할 때는 특별한 경우가 아닌 한 이경우 [ㆍ]버튼 2번 누름으로 아래아를 입력하는 것으로 한다. Morphologically, "ㆍ" is not a vowel attached to another vowel (eg, "sh", "ㅕ", ..), but a vowel containing the lower ah (eg, "

", "

", "

", "

", "

", "

There can be two ways to input the lower ah of ", ...). The first is to input by pressing the [ㆍ] button once, which is the same as in the "3 lower ah method". Also, One way is to input the lower part of the vowel that contains the lower part completely in this way by pressing the [ㆍ] button twice. In this case, if it is not, press the [ㆍ] button twice to input the lower a.

"가 입력되도록 할 수도 있다. "ㅣㆍ=ㅏ"가 아닌 "ㅣㆍ=

"로 적용되는 것은 키패드에서 한글고어의 입력이 보편적으로 사용되는 시기에 적용되는 것이 바람직할 것이다. 상기 알파벳내 모호성이 있는 4가지 모음에 대해 "아래아=ㅏ 3모음법" 적용시의 모호성은 다음과 같다. The same applies to the case of "ㅝ", "아", "ㅋ", and "ㅕ" with ambiguity in the vowel. However, by pressing the [ㆍ] button once after the consonant, you can enter a single vowel "a" (not "a" included in other Korean vowels), so in the case of "ㅣㆍ" (vowel "ㅣ" If "ㆍ" pressed next is considered to act as "ㆍ") is "

" can also be entered. Instead of "ㅣㆍ=A", "ㅣㆍ=

It would be desirable to apply " to the time when the input of Korean archaic words is universally used on the keypad. The ambiguity when applying the "araeah = 3 vowel method" to the four vowels with ambiguity in the alphabet is as follows Same as

= ㅡㆍㆍㅣㅝ =

= ㅡㆍㆍㅣ

= ㅣㆍㆍ (모음에 포함되어 있는 단일한 "ㆍ"을 [ㆍ]버튼 2타로 입력하므로. 이하 동일)ㅑ =

= ㅣㆍㆍ (Since the single “ㆍ” included in the vowel is entered with two strokes of the [ㆍ] button. The same below)

= ㆍㆍㅣㅕ =

= ㆍㆍㅣ

= ㆍㆍㆍㅣ

= ㆍㆍㆍㅣ

= ㆍㆍㆍㅣㅣ

= ㆍㆍㆍㅣㅣ

= ㆍㆍㆍㆍ

= ㆍㆍㆍㆍ

= ㆍㆍ

= ㆍㆍ

= ㆍㆍㅡㆍ

= ㆍㆍㅡㆍ

= ㆍㆍㅣㅡㆍ

= ㆍㆍㅣㅡㆍ

. . . . . .

= ㅡㆍㆍ~ㅣ", "

= ㅣ~ㆍㆍ", "

= ㆍㆍ~ㅣ", "

= ㆍㆍ~ㆍㅣ", "

= ㆍㆍ~ㆍㅣㅣ" 로 입력된다. 후행알파벳장타처리 적용시, "

= ㅡㆍㆍㅣ~", "

= ㅣㆍ~ㆍ", "

= ㆍㆍㅣ~", "

= ㆍㆍㆍ~ㅣ", "

= ㆍㆍㆍ~ㅣㅣ" 로 입력된다. When applying preceding alphabet long hit processing, "

= ㅡㆍㆍ~ㅣ", "

= ㅣㆍㆍ", "

= ㆍㆍ~ㅣ", "

= ㆍㆍ~ㆍㅣ", "

= ㆍㆍ~ㆍㅣㅣ". When applying trailing alphabet long hit processing, "

= ㅡㆍㆍㅣ~", "

= ㅣㆍ~ㆍ", "

= ㆍㆍㅣ~", "

= ㆍㆍㆍ~ㅣ", "

= ㆍㆍㆍ~ㅣㅣ" is entered.

"의 경우를 제외한 4가지 경우는 모두 아래아 형태가 모음의 일부로 포함되어 야기된 모호성임을 알 수 있다. 따라서 선/후행장타처리와 상관없이, 상기와 같이 모호성이 있는 모음이 입력되는 경우, [ㆍ]버튼의 길게 누름을 아래아로 할 수도 있다. 예를 들어, "

= ㅣㆍ~", "

= ㆍ~ㅣ", "

= ㆍ~ㆍㅣ", "

= ㆍ~ㆍㅣㅣ" 로 입력된다. "

"의 경우만 선행알파벳장타처리(예. "

= ㅡㆍㆍ~ㅣ") 또는 후행알파벳장타처리(예. "

= ㅡㆍㆍㅣ~")를 선택적으로 적용하면 된다. 상기와 같이 "모음내 모호성"이 없는 경우(예. "ㅜ")는 [ㆍ]버튼이 길게 눌러졌더라도(예. 입력값 "ㅡㆍ~") 보통의 눌러짐(예. 입력값 "ㅡㆍ")과 동일하게 처리할 수 있다. 이렇게 [ㆍ]버튼의 길게 누름으로 절대적으로 아래아를 입력하는 것은 선/후행장타처리의 로직을 사용자가 생각하지 않아도 모호성이 있는 상기 경우에 한글고어 모음을 정확히 입력할 수 있다. 다만, 선출원에서 제시하였던 [ㆍ]버튼의 길게 누름으로 "ㅎ"을 입력하는 것은 함께 적용하지 못하는 것은 당연하다. 이렇게 [ㆍ]버튼 길게누름으로 모음요소 "ㆍ"을 입력하거나 (예. "ㅜ = ㅡㆍ~") 아래아의 형상이 포함된 한글고어 모음(예. "

", "

", "

", "

", ...)의 아래아를 절대적으로 입력하는 것을 "아래아버튼장타처리"라고 부르기로 한다. Another method that can be commonly applied to the "Area 3 vowel method" and the "Area = A 3 vowel method" is as follows. Among the above 5 cases, "

In all four cases except the case of ", it can be seen that the ambiguity caused by the inclusion of the lower-ah form as a part of the vowel is ambiguity. Therefore, regardless of the leading / trailing sluggish treatment, if a vowel with ambiguity is input as described above, [ㆍ You can also do a long press of the ] button down, for example, "

= ㅣㆍ~", "

= ㆍ~ㅣ", "

= ㆍ~ㆍㅣ", "

= ㆍ~ㆍㅣㅣ" is entered. "

Only in the case of ", the leading alphabet is sluggish (e.g. "

= ㅡㆍㆍ~ㅣ") or trailing alphabet long hit processing (e.g. "

= ㅡㆍㆍㅣ~") can be applied selectively. As described above, if there is no "ambiguity within a vowel" (eg "TT"), even if the [ㆍ] button is pressed for a long time (eg, the input value "ㅡ ㆍ~") can be processed in the same way as a normal press (eg, input value "ㅡㆍ"). Entering an absolute bottom with a long press of the [ㆍ] button in this way reduces the logic of first/following long hitting. Even if the user does not think, the Korean vowel can be accurately input in the case of ambiguity.However, it is natural that inputting "ㅎ" by long pressing the [ㆍ] button suggested in the previous application cannot be applied together. In this way, by pressing and holding the [ㆍ] button, enter the vowel element "ㆍ" (eg "ㅜ = ㅡㆍ~"), or a collection of Korean old words including the shape of Haerah (eg "

", "

", "

", "

Absolutely inputting the bottom of ", ...) will be called "lower button long hit processing".

We look at how to input Korean vowels while applying the technology of using the vowel button proposed by the applicant as a control button (eg "y = xㅡㅡ" or "z = xㅣㅣ"). Representatively, what the applicant suggested was entered as "ㅋ = ㅡㅡ" or "ㄲ = ㄱㅣㅣ". That is, when “ㅡ” is pressed twice after a consonant (eg “a”) is input, or “ㅣ” is pressed twice, “ㅋ” or “ㄲ” is input. This was to use the property that "ㅡ" does not appear twice in a row and "ㅣ" does not appear twice in a row in modern Korean.

", "

", "

", "

", "

", "

", ... 등이 있다. 입력값 "ㄱㅡㅡ"를 누른 것이 "ㅋ" 도 될 수 있고, "

" 도 될 수 있는 것이다. 이는 입력되는 결과인 알파벳(예. "ㅋ")과 자모결합글자(예. "

") 간의 모호성으로 편의상 "알파벳-글자間 모호성" 또는 "알파벳-글자 모호성" 이라고 부를 수 있을 것이다. 상기에서 언급한 바와 같이, "

" 와 "

"를 각각 [ㅡ]버튼 2번 누름 그리고 [ㅣ]버튼 2번 누름으로 입력한다면, "ㅋ = ㄱㅡㅡㅡ"로 입력되어야 한다. 그러나 과연 얼마나 사용될지도 모르는 한글 고어의 입력을 위해 현대 한국어 알파벳(예. "ㅋ")의 입력에 불편(예. [ㅡ]버튼 3번 누름의 조합)을 초래하는 것은 바람직하지 않다. 따라서 현대 한국어와 한글고어의 입력을 함께 적용하더라도, 현대 한국어의 입력을 우선하여 고려하는 것이 타당하다. 그렇다면 "ㅋ"의 입력과 "

"의 입력을 어떻게 처리할 수 있는지를 다음에서 보인다. However, there are cases in which "ㅡ" or "ㅣ" appears twice in a row after a consonant in Korean language. For example, "

", "

", "

", "

", "

", "

There are ", ..., etc. Pressing the input value "ㄱㅡㅡ" can also be "ㅋ", and "

" can also be. This is the input result of the alphabet (eg "ㅋ") and consonant characters (eg "

") may be conveniently referred to as "inter-alphabetic-letter ambiguity" or "alphabet-letter ambiguity". As mentioned above, "

" Wow "

", respectively, by pressing the [ㅡ] button twice and pressing the [ㅣ] button twice, it should be entered as "ㅋ = ㅡㅡㅡ". It is not desirable to cause inconvenience (eg, combination of pressing the [ㅡ] button 3 times) to the input of (eg "ㅋ"). Therefore, even if modern Korean and Korean archaic input are applied together, modern Korean input It is reasonable to consider it first. Then, the input of "ㅋ" and "

The following shows how to process the input of ".

"를 입력하기 위해서는 "ㄱ"을 누른후 소정시간 지연(즉, 타이머) 또는 구분버튼 눌러짐에 의하여 "ㄱ"을 확정하고 "ㅡㅡ"를 2번 누르도록 하면된다. "알파벳-글자 모호성"을 해결하는 과정은 일련의 버튼누름(예. "ㄱㅡㅡ")이 하나의 알파벳(예. "ㅋ")으로 인식되지 않고 자음과 모음의 조합(예. "

")으로 인식되도록 특별히(예. 시간지연, 구분버튼, 선/후행장타, ...) 처리하는 것이므로, 그 성질은 "알파벳내 모호성" 과 유사하다. Since the input of modern Korean should be considered first, it is reasonable that "ㅋ" is displayed when "ㄱㅡㅡ" is pressed. Applying the existing time delay or timer technique, "

In order to enter ", after pressing "a", confirm "a" by delaying a predetermined time (ie, timer) or by pressing the division button, and press "ㅡㅡ" twice. "Alphabet-letter ambiguity" The process of solving is that a series of button presses (eg "ㄱㅡㅡ") are not recognized as one alphabet (eg "ㅋ"), but a combination of consonants and vowels (eg "

"), so it is specially processed (eg time delay, division button, leading/trailing long hit, ...), so its nature is similar to "ambiguity within the alphabet".

" 가 되는 것이다. 어떤 자음 다음에 모음 "

"가 입력되는 것은 그 앞에 입력된 자음이 어차피 초성자음으로 처리될 수 밖에 없기 때문이다. 만약 현대 한국어에서도 사용되는 "ㅋ"을 입력하기 위한 것이었다면 [ㄱ]버튼의 길게 누름(즉, "ㄱ~ㅡㅡ")이 아닌 보통의 누름(즉, "ㄱㅡㅡ")으로 누르면 된다. 이는 주로 사용되는 현대 한국어 자음의 입력에는 길게 누름을 사용하지 않으면서 동시에 조합되는 모음버튼(예. [ㅡ]버튼 또는 [ㅣ]버튼)의 눌러짐도 2회만 적용되는 장점이 있다. 도면4-34(a)에서 회색음영으로 표시된 알파벳은 현대 한국어 자음을 나타낸다. 도면4-34(a)에서 1차조합에 의하여 입력되는 자음은 [ㅡ]버튼 또는 [ㅣ]버튼의 2번 눌러짐의 조합으로 입력된다. 자음 다음에 "ㅡ"가 연속하여 2번 나오는 고어 글자(예. "

")의 입력을 허용하지 않는다면 2차조합, 3차조합, ... 에 의하여 입력되는 자음도 [ㅡ]버튼 또는 [ㅣ]버튼의 2번 눌러짐의 조합으로 입력되지만, 상기와 같은 고어 글자(예. "

")의 입력을 허용한다면 2차조합, 3차조합, 4차조합, ... 에 의하여 입력되는 자음은 [ㅡ]버튼 또는 [ㅣ]버튼 3회 눌러짐의 조합으로 입력된다. 예를 들어, "ㅸ =

ㅡ = ㅍㅡㅡㅡ = ㅂㅡㅡㅡㅡㅡ" 와 같이 되는 것이다. If the preceding alphabet long hit processing is used, long press "a" to confirm "a", and then press "ㅡ" twice. Even if this is done, it does not conflict with the input of the trailing alphabet sluggish processing in the initial consonant position ambiguity (ie, ambiguity does not occur), and even if there is ambiguity in extremely special cases, it is virtually non-existent. In other words, press and hold "ㄱ" to confirm the initial consonant, then press "ㅡ" twice to "ㅋ" instead of "ㅋ"

It becomes ". A consonant followed by a vowel "

" is entered because the consonant entered before it is bound to be treated as a first consonant anyway. If it was to input "ㅋ", which is also used in modern Korean, press and hold the [a] button (i.e., "~ㅡㅡ"), but press it with a normal press (i.e., "ㄱㅡㅡ"). This is a combination of vowel buttons (eg, [ㅡ ] button or [ㅣ] button) has the advantage of being applied only twice. In Fig. 4-34 (a), the gray shaded alphabet represents modern Korean consonants. In Fig. 4-34 (a), the first The consonant input by combination is entered by a combination of pressing the [ㅡ] button or the [ㅣ] button twice.

If the input of ") is not allowed, the consonants entered by the secondary combination, tertiary combination, ... are also entered with the combination of pressing the [ㅡ] button or the [ㅣ] button twice, but the same old letters as above (Yes. "

If input of ") is allowed, the consonants entered by the 2nd combination, 3rd combination, 4th combination, ... are input in combination by pressing the [ㅡ] button or the [ㅣ] button three times. For example, , "ㅸ =

ㅡ = ㅡㅡㅡ = ㅡㅡㅡㅡㅡ”.

" 와 "

"은 눌러지는 버튼(즉, 입력값)이 같다. 본 발명에서 설명한 바와 같이, 한글고어(예. "

")보다 현대 한국어(예. "ㅌ")이 우선하여 쉽게 입력되어야 하므로, 길게 누름을 사용하지 않는 입력값 "ㄷㅡㅡ"는 "ㅌ"으로 되고, "ㄷ~ㅡㅡ" 는 "

"로 되는 것이다. 이는 "초성자음위치 모호성"에서 "후행알파벳장타처리" 적용시 길게누름에 의하여 입력되는 자음을 초성자음으로 처리하는 것과 일치하게 된다. 즉, "

" 이 아닌 "간ㄷ"을 입력하기 위하여, 후행알파벳장타처리를 적용하여 "ㄷ"을 길게 눌러 입력하는 것과 같게 된다. In order to input the consonant that is firstly combined in Fig. 3-34 by pressing the [ㅡ] button or the [ㅣ] button twice, there are some matters to be considered in some Korean automata (Korean consonant combination rules). "liver

" Wow "

" is the same as the button being pressed (i.e., the input value). As described in the present invention, Korean language (eg "

") rather than modern Korean (e.g. "ℓ") should be entered easily, so the input value "ㅅㅡㅡ" that does not use a long press becomes "ℓ", and "ㅅ~ㅡㅡ" is "

". This is consistent with processing the consonant input by long pressing as the initial consonant when applying "Long Hit Processing of Trailing Alphabet" in "Position Ambiguity of Initial Consonant". In other words, "

In order to input "Kan" instead of ", it is the same as pressing and holding "c" by applying the trailing alphabet sluggish processing.

")을 형성할 수 있으면 이를 각각의 낱자음(예. "ㅅ")과 초성자음(예. "ㄷ")으로 인식(예. "ㅅㄷ")하지 않고, 입력값 전체(예. "ㅅㄷ~")를 초성자음(예. "

")으로 처리할 수 있다. 이렇게 입력된 "

" 다음에 모음이 오면 "

" 전체가 초성자음으로 된다. "ㅅ"이 초성자음이라는 것을 명확히 하기 위하여 입력값으로 "ㅅ~"이 눌러진 이후에 "ㄷ~"이 눌러진 경우(예. 입력값 "ㅅ~ㄷ~")도 결과는 동일하다. "

" 와 "

" 은 눌러지는 버튼이 동일한데, 역시 현대 한국어의 입력을 우선하여, 길게 누름을 사용하지 않는 "ㄷㅡㅡ"는 "ㅌ"이 되고, 길게 누름을 사용하는 "ㅅㄷ~ㅡㅡ"는 "

"이 되도록 할 수 있다. 앞서 간단히 언급한 대로 도면3-34에서 2차조합, 3차조합, ... 에 의하여 입력되는 자음은 모두 한글고어 자음으로 사용빈도가 매우 적을 것이므로 [ㅡ]버튼 또는 [ㅣ]버튼 3번 눌러짐의 조합으로 입력되는 것이 적합해 보인다. In addition, when applying "Long Hit Processing for Initial Consonants" in "Positional Ambiguity of Initial Consonants", the consonant entered just before the long press (eg "ㅅ") is recognized as the initial consonant, not the final consonant, and the consonant entered by the subsequent long hitting process ( Ex. "c") is combined to form the first consonant (ex. "

"), it is not recognized as individual consonants (eg "ㅅ") and initial consonants (eg "ㅅ"), but the entire input value (eg "ㅅㅅ~"). ") as a first consonant (eg. "

"). "

"Next comes the vowel"

" The whole becomes a leading consonant. In order to clarify that "ㅅ" is a leading consonant, if "ㅅ~" is pressed after "ㅅ ~" is pressed as an input value (e.g., the input value "ㅅ~ㅅ~" ) has the same result."

" Wow "

" is the same button to be pressed, but also prioritizes modern Korean input, so "ㅅㅡㅡ" that does not use a long press becomes "T", and "ㅅㄴ~ㅡㅡ" that uses a long press "

As mentioned briefly above, the consonants input by the secondary combination, tertiary combination, ... in Fig. 3-34 are all Hangul Gore consonants and are very rarely used, so the [ㅡ] button or It seems appropriate to enter the combination of pressing the [ㅣ] button three times.

= ㅡ~ㅡㆍ"가 된다. For "alphabet-letter ambiguity", if trailing alphabet long hit processing is applied, press "a", press "ㅡ" for a long time, and then press "ㅡ" once more. For example, "

= ㅡ~~ㅡㆍ".

"를 입력하는 것으로 정의할 수도 있다. 마찬가지로 [ㅣ]버튼 한번 길게 누르는 것을 "

"로 정의할 수도 있다. 예를 들어, "

= ㅡ~ㅡㆍ"가 아닌 "

= ㅡ~ㆍ"로 입력되는 것이다. 이는 "후행알파벳장타처리"를 적용하는 경우 "

" 입력시 길게누름을 이용해야만 하는 불편함이 있는데, 입력타수를 1타 줄여주며, 직관적으로도 "

"를 "ㅡ" 길게누름으로 입력하는 것으로 연상할 수 있으므로 사용자에게 쉽게 이해될 수 있는 잇점이 있다. 이를 편의상"수직/수평모음장타처리 (입력방법)" 이라고 부르기로 한다. In the above, cases of "preceding alphabet long hitting processing" or "later alphabet long hitting processing" were shown for ambiguity in various cases. "

It can also be defined as inputting ". Likewise, long-pressing the [ㅣ] button once "

". For example, "

= ㅡ~~ㅡㆍ " not "

= ㅡ~ㆍ" is entered. This is the case when "trailing alphabet long hit processing" is applied.

" There is an inconvenience of having to press and hold for input, but it reduces the number of input strokes by one stroke, and intuitively "

It can be associated with inputting "ㅡ" by long pressing, so there is an advantage that users can easily understand. This is called "vertical/horizontal vowel long hitting processing (input method)" for convenience.

", "

", "

", "

", "

", "

", ... 등이 있는데, 이러한 모음의 입력에 [ㅡ]버튼 또는 [ㅣ]버튼 길게 누름으로 상기 모음에 포함된 "

" 또는 "

"를 각각 입력되도록 할 수 있다. 이 역시 "수직/수평모음장타처리"를 이용하는 것이 된다. (상기 "

= ㅡ~ㆍ"로 입력하는 사례 참조) 현재까지 등록된 유니코드v2.0에서는 "ㆍㅡㅡ = ㅗㅡ" 가 결합된 형태의 모음은 없다. 그러나 "

" 를 "ㆍㅡㅡㆍ"으로 입력한다면 그 과정에서 눌러지는 "ㆍㅡㅡ" 가 "ㅎ"으로 해석될 수 있다. 따라서 현대 한국어의 입력을 우선하여 "ㆍㅡㅡ" 를 항상 "ㅎ"으로 인식되도록 한다면, "

"를 입력하기 위하여는 "ㆍㅡ~ㆍ"으로 할 수 있다. 즉 "

"에 포함되어 있는 "

"를 [ㅡ]버튼 길게 누름에 의하여 입력하는 것이다. As exemplified above, a vowel in which "ㅡ" or "ㅣ" can be pressed twice in succession after a consonant is "

", "

", "

", "

", "

", "

There are ", ..., etc., and in the input of these vowels, press and hold the [ㅡ] button or the [ㅣ] button to "

" or "

" can be entered separately. This also uses "vertical/horizontal vowel long hitting processing". (The above "

= ㅡㅡㆍ") In Unicode v2.0 registered so far, there is no vowel in the form of "ㆍㅡㅡ = ㅗㅡ" combined. However, "

If you enter "ㆍㅡㅡㆍ" as "ㆍㅡㅡㆍ", "ㆍㅡㅡ" pressed in the process can be interpreted as "ㅎ". Therefore, "ㆍㅡㅡ" is always replaced with "ㅎ", giving priority to modern Korean input. If it is to be recognized, "

To input ", you can use "ㆍㅡ~~ㆍ". In other words, "

"included in"

" is entered by long pressing the [ㅡ] button.

= ㅡㆍㅣㅣ"와 같이 모음이 먼저 인식되고 나서 "ㅣ"가 연속하여 나오는 경우는 상기와 같이 자음이 인식되고 나서 "ㅣ" (또는 "ㅡ")가 연속 나오는 경우와 구별되기 때문에 "알파벳-글자 모호성"이 없으므로 굳이 길게누름을 이용하여 입력할 필요는 없다. 일관성을 위하여, "ㅔ", "ㅞ", "

", ... 등에 들어 있는 "

"를 길게누름으로 입력하도록 허용할 수도 있다. 예를 들어, "ㅔ = ㆍㅣ~" 으로 하는 것이나, 권장하지 않는다. 특히 "알파벳내 모호성"에 대해 후행알파벳장타처리로 입력하는 것과 충돌되는 부분이 있어 함께 적용하지 못할 수 있다. "ㅔ = ㆍㅣㅣ", "ㅞ = ㅡㆍㆍㅣㅣ", or "ㅞ = ㅡㆍㆍㅣㅣ"

= ㅡㆍㅣㅣ", the vowel is recognized first and then "ㅣ" appears consecutively, as described above, since the case where "ㅣ" (or "ㅡ") appears consecutively after the consonant is recognized, the "alphabet -There is no “letter ambiguity”, so there is no need to press and hold to input. For consistency, “ㅔ”, “ㅞ”, “

", in ... etc."

It is also possible to allow input by pressing and holding ". For example, "ㅔ = ㆍㅣ~", but it is not recommended. In particular, for "ambiguity within the alphabet", the part that conflicts with input by long-pressing the trailing alphabet They may not be applied together.

In the above, cases such as "initial consonant position ambiguity", "alphabet ambiguity", and "alphabet-letter ambiguity" have been cited. For each case, the preceding alphabet sluggish processing and the following alphabet sluggish processing can be selectively applied. For example, in the case of “initial consonant position ambiguity,” the trailing alphabet sluggish processing is applied, in the case of “alphabet ambiguity,” the preceding alphabet sluggish processing is applied, and in the case of “alphabet-letter ambiguity,” the preceding alphabet sluggish processing is applied. It can be done. From the user's point of view, the preceding alphabet long hitting processing has a feeling that the moment a specific button is pressed for a long time among a series of button presses, the result of the input value including the long pressed button is confirmed, and the following alphabet long hitting processing has a feeling that a specific button is long pressed. The moment it is pressed, it can be felt as if the previously pressed input value is confirmed and a new input is started. In either case, it can be used selectively (e.g. pre-setting in environment settings) according to the user's preference.

= ㅡㆍㆍ~ㅣ")하고, "알파벳내 모호성"의 경우에는 아래아버튼장타처리를 적용하고, "알파벳-글자 모호성"에 대해서는 선행알파벳장타처리를 적용하는 것을 들 수 있다. 상기와 같이 적용하였을 때, 일련의 버튼누름에 의한 한국어 입력중 다음글자의 초성자음으로 돌출되어 나타나게 되는 자음은 길게누름으로 확정하고, "

"를 입력하기 위한 "ㄱ"은 [ㄱ]버튼 길게 누름으로 "ㄱ"을 확정하는 일관성있는 사용이 가능하다. 또한 "아래아버튼장타처리"를 이용하여 현대 한국어 모음과 한글고어 모음간의 모호성이 있는 경우에도 단일한 규칙("

" 예외)으로 처리가 가능해진다. 또한 [ㅡ]버튼 또는 [ㅣ]버튼의 길게누름은 사용되지 않으므로, [ㅡ]버튼과 [ㅣ]버튼의 길게누름을 다른 용도로 활용할 수 있다. In the opinion of the applicant, a good application case is to apply trailing alphabet long hitting treatment in the case of "initial consonant position ambiguity" (except for

= ㅡㆍㆍ~ㅣ"), and in the case of "ambiguity within the alphabet", the lower button long hitting process is applied, and for "alphabet-letter ambiguity", the preceding alphabet long hitting process is applied. Apply as above. When it is done, the consonant that appears as the initial consonant of the next letter during Korean input by pressing a series of buttons is confirmed by long pressing, and "

"ㄱ" for inputting "a" can be used consistently by long-pressing the [a] button to confirm "a". In addition, by using the "down button long hit processing", there is ambiguity between modern Korean vowels and Korean old Korean vowels. Even if a single rule ("

" exception). In addition, long pressing of the [ㅡ] button or [ㅣ] button is not used, so long pressing of the [ㅡ] button and the [ㅣ] button can be used for other purposes.

In the above, a technology that can input modern Korean and Korean archaic at the same time was presented.

31.3 Extended notation method and display method using old Korean language (old Hangul)

31.3.1 Extended notation method of Hangul

There have been attempts in the past to mark the pronunciation of foreign languages that are not in Korean. As an approach, the first method is to use the old Korean language (old Hangeul) that is not used now, and the second method is to create a new consonant corresponding to the pronunciation of a foreign language.

"Byeongseo" is a method of expressing new pronunciation by writing Korean consonants side by side, such as "ㄲ", "ㅄ", "ㅳ", "ㅴ", ..., etc., and "Yeonseo" is "ㅸ", It is a method of expressing a new pronunciation by writing Korean consonants vertically, such as "ㆄ", ..., etc.

", "

", "

","

", ... 등을 들 수 있다. 우리 한글의 옛글자까지 포함된 모음은 워낙 다양한 복모음이 가능하므로 (유니코드상의 한글 모음 약 100글자) 외국어 표기에 있어서도 별로 논란이 되지 않고 있다. 그리고 실제로 실질적인 음가를 가지고 있는 것이 자음이기 때문이기도 한 것 같다. 옛한글을 포함하는 한글자모를 사용하여 현대 한국어 발음으로 사용되지 않는 외국어 발음을 표기함에 있어서, 다음의 몇가지 원칙을 생각해볼 수 있다. Representative foreign language sounds that do not have the same pronunciation in modern Korean are "v", "f", "r"('r' in the consonant sound), "z", "

", "

", "

","

", ..., etc. Vowels, including the old letters of our Korean alphabet, can have so many different vowels (about 100 Hangul vowels on Unicode), so there is not much controversy in foreign language transcription. And actually It seems that it is also because it is the consonant that has the actual sound value.In writing foreign language pronunciations that are not used as modern Korean pronunciation using Hangul consonants, including old Hangul, the following several principles can be considered.

First, when the marked letter is pronounced by an ordinary person or when there is a brief explanation, similar pronunciation should be possible.

Second, if there is a method by conjugation or conjugation that can properly express the pronunciation, consider the method of conjunctive writing and conjunctive writing rather than creating a new letter.

Third, in the case of a letter or combination letter, it is good that the letter that is the basis of the sound comes out first.

Hereinafter, a method of expressing foreign language pronunciation mainly using Byeongseo (hereinafter 'Byeongseo' is used as a concept including 'Yeonseo') will be described.

"라고 표기한 경우도 있었다. "v"발음 윗이빨을 아랫입술에 살짝 대어 발음하는 "v"의 발음에 "

"라는 표기가 더 적절하다고 할 수 있다. 그러나 이러한 "

" 표기에는 약간의 문제가 있다. 먼저 현대 한국어 발음에서 자음 "X"에 "ㅢ"가 결합된 글자의 현실 발음은 "Xㅣ"로 거의 통합되고 있다. 예를 들어 "희"의 경우 정확한 발음은 "흐이"를 1음절로 빨리 발음하는 것이나, 현실 발음은 "히"로 발음되고 있는 현상이 있는 것이다. "ㅢ"의 발음이 정확히 살아 있는 경우는 음가가 없는 "ㅇ" 다음 순수하게 모음 "ㅢ"가 나오는 경우로 보인다. 예를 들어 "의자" 에서 "의"는 정확하게 "으이"가 1음절로 빨리 발음되는 형태로 발음되고 있다. 또 한가지 문제는 "bi"와 "vi"에서 자음이 달라졌는데도, 한글 표기에서는 같은 자음(즉, "ㅂ")을 사용하고, 모음의 표기가 달라져야 하는 것(즉, "비", "

")도 표기의 불일치를 준다. 모음을 달리 표기하여 각기 다른 자음의 발음을 표현한 사례는 "show" 의 "" 발음을 "s"와 동일한 "ㅅ"으로 표기하면서 모음을 "ㅛ"로 사용한 사례(즉 "쇼" 또는 "쑈")도 있다. Currently, both "b" and "v" pronunciations are written as "ㅅ" in Korean, so it is not distinguishable between "b" and "v". When writing the alphabet "b" in Korean, it is written as "B", and when writing the alphabet "v" in Korean, it is written as "V". In the past beginner English books, "v" was replaced with "

"v" pronunciation The pronunciation of "v", which is pronounced by lightly touching the upper teeth to the lower lip, "

"" may be more appropriate. However, these "

" There is a slight problem with the notation. First of all, in modern Korean pronunciation, the actual pronunciation of the letter combining the consonant "X" with "ㅢ" is almost integrated into "Xㅣ". For example, in the case of "hee", the correct pronunciation is to pronounce "heui" quickly with one syllable, but there is a phenomenon in which the pronunciation of "ㅢ" is pronounced as "hi." It seems that "ㅢ" comes out. For example, in "chair", "ui" is pronounced exactly as "eui" is pronounced quickly with one syllable. Another problem is that the consonants in "bi" and "vi" Even though it has changed, the same consonant (i.e., "ㅅ") is used in Hangul transcription, and the vowel transcription must be different (i.e., "bi", "

") also gives inconsistency in notation. In the case of expressing the pronunciation of different consonants by writing the vowel differently, the case of using the vowel as "ㅛ" while transcribing the "" pronunciation of "show" as "ㅅ" the same as "s" (i.e. "show" or "show").

Traditionally, it has been pointed out that it is appropriate to express the pronunciation of "v" using the consonant sound "ㅸ". If the literal interpretation of "sounding sound" is a "sound of light lips", it is possible to explain that it is closer to the sound value of "v". Of course, there is no way to know what the exact sound of the past police officer "ㅸ" was. In the same logic, there was also an opinion about writing "f" pronunciation with "ㆄ". In the above, representative examples of notation of "v" and "f" pronunciations have been described, and some existing opinions on the notation of "v" and "f" pronunciations are summarized as follows.

v: "ㅸ", "ㅎㅅ" (byeongseo), "ㅅㅎ" (byeongseo), ...

f: "ㆄ", "ㅎπ" (byeongseo), "ㄴㅎ" (byeongseo), ...

The suggestion to use "PH" as the "f" pronunciation above seems to have come from the fact that the English letter "ph" is usually pronounced as "f". With the same logic, it can be seen that a plan to use "ㅅㅎ" for the pronunciation of "v" has come out.

In our Hangeul, there is a phenomenon in which "pyeong consonant sound + ㅎ" or "ㅎ + flat consonant sound" is sounded as "lattice consonant sound". For example, since "a lot" sounds like "manta", you can see that "ㅎ + ㄴ" sounds like "ℓ", and "eaten" sounds like "mucky", so "ㄱ+ㅎ" sounds like "ㅋ" ", you can hear the sound. Here, it cannot be proven whether "flat consonant + ㅎ" or "ㅎ + flat consonant" is correct, and it can be said that both are correct as in the case above. It is easy to understand that "ㅎ" with the sound "heh" is combined with a normal sound (flat consonant, eg "ㄱ") to produce sounds such as "ㅋ", "ℓ", "P", ... It can be. In phonetics, it seems to be expressed in difficult words that are organic. That is, when "ㅎ" is combined, it can be seen that the original sound (eg "ㄱ") becomes a little stronger. It is inappropriate to express the "v" pronunciation because it is obvious that "ㅅㅎ" corresponds to the "P" pronunciation, and similarly, it is inappropriate to express the "f" pronunciation with "ㄴㅎ".

Traditionally, phonetics uses the systemic classification of sounds by articulation points and articulation methods, and Korean Hangeul can also be said to be a scientific product created by the excellent insight and intuition of King Sejong, a phonetic scholar. However, it seems unreasonable that ordinary people should understand and use the knowledge of phonetics for foreign language pronunciation transcription.

In the case where the pure consonant "ㅸ" combined with "ㅅ + ㅇ" is expressed as a first consonant, it can be recognized as a pronunciation combining "ㅅ" and "ㅇ" from the "general person's point of view", not a phonetic scientist, but the initial consonant "ㅇ" Since "" has no sound value, it can be recognized that the pronunciation of "ㅅ" is weakened. Again, from the point of view of the general public, not a phonetician, the "v" pronunciation is perceived as weaker than the "b" pronunciation, so it can be said that it is reasonable to express "v" with the sound "ㅸ".

"라고 표기했던 적이 있는데, 순경음 "ㅸ"을 이용하여 "

"라고 표기하였을 때와 비교해 보면 공통점이 있음을 알 수 있다. "

"라고 표기해 놓고 사전 지식이 없는 일반인에 읽어 보라고 하면 어떻게 읽을지 고민하다가, 1차적으로 "ㅂ"과 "ㅇ"을 분해하고 "(브)"라는 "ㅂ"발음을 앞에 두고, 그 다음 남아 있는 "이"와 붙여서 빨리 발음하려고 할 수 있다. (이는 "ㅝ"를 발음할 때 "ㅜ"와 "ㅓ"를 빨리 발음하면 "ㅝ"가 되는 것을 생각할 수 있다. 모음의 경우는 복모음이 완전하게 단모음의 조합으로 설명되나, 다음에 설명하는 자음의 경우는 약간 다른 듯 하다) 즉 "(브)" 로 음절이 체 완성되기 전에 "이"와 붙여서 발음하면 현재 표기하고 있는 "브이"를 빨리 발음한 결과와 유사하게 된다. 다음으로 이는 "

"의 발음과 유사하게 된다. 물론 "

"의 발음 역시 "v"와 완전히 일치하는 것은 아니므로 "

" 의 표기를 "v"로 정의하고 발음하게 하는 "교육"이 필요하게 된다. 다만 "그렇듯한" 그리고 "타당해 보이는" 표기를 해당 발음으로 "정의"하는 것이 필수적이다. 예를 들어 "ㄲ"을 모르고 "ㄱ" 의 발음만 알고 있는 사람이 "ㄲ"을 보고 어쩐지 "끄"하고 발음하고 싶은 생각이 든다면, 그리고 "ㅋ"을 모르고 "ㄱ"의 발음만 알고 있는 사람이 "ㅋ"을 보고 어쩐지 "크" 라고 발음하고 싶다면 "그럴듯한" 좋은 표기인 것이다. 여기에 이론과 교육이 더해져 "ㄲ"은 "ㄱ"을 좌우로 배열한 글자 이므로 "끄"라는 소리가 난다는 배경이 설명된다면, 사용자는 "ㄲ"의 표기와 그에 따른 발음을 매우 자연스럽게 사용할 수 있게 되는 것이고 이러한 점이 우리 한글의 과학성 중의 한가지라고 할 수 있을 것이다. In modern Korean, "v" is written as "V", and in the past "

", but using the sound "ㅸ"

If you compare it with when it was marked as “, you can see that there is a commonality.”

", and thinking about how to read it if you ask the general public without prior knowledge to read it, first disassemble "ㅅ" and "ㅇ", put "(B)" in front of the "ㅅ" pronunciation, and then You can try to pronounce it quickly by attaching it to "i" that is present. (This can be thought of as "ㅝ" when pronouncing "TT" and "sh" quickly when pronouncing "ㅝ". In the case of vowels, the consonant vowel is perfect. It is described as a combination of single vowels, but the case of the consonants described next seems to be slightly different) In other words, if you pronounce it in conjunction with "i" before the syllable is completed with "(B)", you can quickly pronounce "V" currently written. It will be similar to the pronounced result. Next, it will be "

It becomes similar to the pronunciation of ". Of course "

The pronunciation of " is not exactly the same as "v", so "

It is necessary to "educate" to define and pronounce the notation of " as "v". However, it is essential to "define" the notation of "like" and "reasonable" with the corresponding pronunciation. For example, "ㄲ If a person who does not know " and only knows the pronunciation of "ㄱ" sees "ㄲ" and somehow wants to pronounce it as "Kuu", and a person who does not know "ㅋ" but only knows the pronunciation of "ㄱ" feels like "ㅋ" If you want to pronounce "keu" somehow, it is a "plausible" notation. Here, the theory and education are added to explain the background that "ㄲ" is a letter arranged with "ㄱ" on the left and right, so it sounds like "kkeu" If so, the user will be able to use the notation of "ㄲ" and its pronunciation very naturally, and this can be said to be one of the scientific properties of our Korean language.

" 로 표기하고 이를 "v"발음으로 사용하자는 주장도 있으나, "

" 의 표기와 "v"발음간의 어떠한 상관관계도 없음에도 불구하고 그 표기법을 주장하는 것은 타당하지 않아 보인다. Some inventors put a dot on "rain" and said "

There is an argument to mark it as " and use it as a "v" pronunciation, but "

Even though there is no correlation between the notation of " and the pronunciation of "v", it does not seem reasonable to insist on the notation.

"으로 표현하는 것이 타당하다면, "v"와 유사계열의 발음은 "f" 역시 "ㆄ" 또는 "

" 으로 표기하는 것이 가능하다. If the "v" is pronounced as a cop sound "ㅸ" or "

If it is appropriate to express it as ", the pronunciation of "v" and similar series "f" is also "ㆄ" or "

" can be denoted as

"의 경우는 가장 유사한 현대 한국어 발음이 "ㄷ"이라고 할 수 있다. 또한 동시에 "ㄷ"보다는 약한 느낌의 발음이다. 따라서 "ㄷ"과 "ㅇ"이 상하로 연서 또는 좌우로 병서된 글자로 표기하는 것을 생각할 수 있다. 이하에서 자음 "X"와 이응 "ㅇ"이 순서대로 연서 또는 병서된 글자는 같은 글자로 간주하며 그 이유는 아래에서 별도로 설명한다. 일반인의 관점에서 보면 "

ㅣ" 를 발음할 때 "(드)"라는 음절이 완전히 형성되기 이전에 "이" 와 빨리 합쳐져서 발음되므로 "ㄷ"과 "ㅇ"(음가 없음)의 중간 발음 (즉, "ㄷ"의 발음이 약화된 발음) 정도로 발음을 시도해 볼 수 있을 것이다. 이렇게 시도한 발음이 비록 "" 발음과 완전히 일치하지 않더라도 유사하다면(최소한 강약의 느낌에 있어서), 상기 표기를 "" 발음의 표기로 검토해 볼 수 있는 것이다. 영어의 "this"에서 "" 발음을 "

ㅣ" 와 같이 표기할 수 있게 된다. 음성학자가 아닌 일반인인 본 발명자의 느낌으로는 "

" 를 표시하는데 "ㄷ"와 여린ㅎ "ㆆ"을 연서 또는 병서한 형태도 가능해 보인다. 물론 음성학자의 관점에서 보면 "유성음"인 ""의 발음을 "

" 또는 "

" 으로 표기하는 것이 부정확하므로, "

" 표기하기 위한 새로운 글자를 만드는 것이 정확하다는 주장을 할 수도 있다. to the next "

In the case of ", the most similar modern Korean pronunciation can be said to be "ㄴ". Also, at the same time, it is a weaker pronunciation than "ㄴ". Therefore, "ㄴ" and "ㅇ" are written in a combination of letters up and down or left and right. Hereinafter, the consonant "X" and the consonant "ㅇ" are considered to be the same letter in conjunction with each other in order, and the reason will be explained separately below. From the point of view of the general public, "

When pronouncing ㅣ", before the syllable "(de)" is completely formed, it is pronounced as it is quickly combined with "이", so the middle pronunciation of "ㄴ" and "ㅇ" (no sound) (i.e., the pronunciation of "ㄴ" If the pronunciation tried in this way is similar to the "" pronunciation even if it does not completely match (at least in terms of the feeling of strength and weakness), the above notation can be reviewed as a notation of the "" pronunciation. In English "this", "" pronunciation "

ㅣ". In the opinion of the present inventor, who is not a phonetician, "

" is also possible in the form of a combination of "ㅅ" and soft "ㆆ". Of course, from the point of view of a phonetician, the pronunciation of "voiced sound"

" or "

Since it is inaccurate to write " as "

“It could be argued that it is correct to create new letters for writing.

" 발음의 경우는 현대 한국어에서 가장 유사한 기본 발음이 "ㅆ"이라고 볼 수 있다. "

" 발음이 "ㅆ"보다 약한지는 모르겠으나, "ㅆ"보다 강한 발음이라고는 느껴지지 않는다. 따라서 "ㅆ"과 "ㅇ"을 상하로 연서하여 "

"로 표현할 수 있다. "though"를 "

ㅗㅌ" 또는 "

ㅗ트"로 표기(자모결합 글자로 표기되어야 하나 편의상 중성모음과 종성자음을 늘어 썼음)한다면 "(쓰)"라는 발음이 형성되기 전에 "

" 또는 "오트"와 결합된 형태로 발음하려 할 것이다. 이 발음이 "

" 와 동일한 발음은 아니지만 "

" 발음과 유사한 느낌을 준다면, "

"를 "" 발음의 표기로 사용할 수 있는 것이다. 영어의 "thank you"를 현재의 한글로 표기할 때, "쌩큐"라고도 하고, 어떤 사람은 "땡큐"라고도 표기한다. 따라서 "ㄸ+ㅇ"의 연서(또는 병서) 형태를 적용하는 것도 가능할 것 같다. "

" In the case of pronunciation, the most similar basic pronunciation in modern Korean can be seen as "ㅆ". "

" I don't know if the pronunciation is weaker than "ㅆ", but I don't think it's stronger than "ㅆ". Therefore, "ㅆ" and "ㅇ" are linked together "

" can be expressed as "though"

s" or "

If it is written as "ㅗte" (it should be written as a consonant letter, but for convenience, the neutral vowel and the final consonant are increased), before the pronunciation of "(tsu)" is formed, "

" or "ot". This pronunciation is "

It's not the same pronunciation as ""

"If it gives you a feeling similar to the pronunciation,"

"" can be used as a notation for the pronunciation of "". When transcribing "thank you" in English in the current Korean language, it is also called "Thank you", and some people also write "thank you". Therefore, "ㄸ + ㅇ" It seems that it is also possible to apply the conjunctive (or conjunctive) form of

"의 경우는 현대 한국어에서 가장 유사한 발음은 "ㅅ" 이다. 역시 "ㅅ"보다는 약한 느낌의 발음이다. 따라서 "ㅅ"을 기본 글자로 하고 역시 연서 또는 병서된 글자인 "

" 또는 "

" 로 표현할 수 있다. "show" 를 "ㅅㅇㅗ" (자모결합 글자로 표기되어야 하나 편의상 중성모음과 종성자음을 늘어 썼음)로 적으면 일반인은 "(스)"라는 음절이 완성되기 전에 "오"와 결합되는 식으로 발음하는 것을 고민할 수 있다. 우리 한글에서 "ㅣ+ㅗ = ㅛ"인데 "ㅡ+ㅗ"는 "ㅛ"는 아니지만 유사한 발음의 변형이 될 것으로 짐작된다. "ㄱ"이 "ㅎ"과 합쳐지면 "ㅋ" 소리가 나는데, 일반인의 느낌으로 "" 발음은 기본이 되는 "ㅅ"(또는 "ㅆ")에 "ㅎ"이 합쳐진 소리보다는 많이 약하지만, "ㄱ+ㅎ"의 경우 처럼 "흐"하는 기운이 아주 약간 섞여 있는 느낌이 있다. 따라서 시옷과 여린ㅎ이 좌우로 병서된 "ㅅㆆ"로 또는 상하로 연서된 글자로 표현될 수도 있어 보인다. "z"는 반치음 "ㅿ" 으로 표기하자는 주장이 있다. "

In the case of ", the most similar pronunciation in modern Korean is "ㅅ". It is also a weaker pronunciation than "ㅅ". Therefore, "ㅅ" is the basic character, and "

" or "

It can be expressed as "." If "show" is written as "ㅅㅇㅗ" (it should be written as a consonant letter, but for convenience, the neutral vowel and final consonant are increased), the general public will say "oh" before the syllable "(s)" is completed. In our Korean language, "ㅣ+ㅗ = ㅛ", but "ㅡ+ㅗ" is not "ㅛ", but it is assumed that it will be a variation of similar pronunciation. When combined with "ㅎ", a "ㅋ" sound is produced. To the general public, the "" pronunciation is much weaker than the basic "ㅅ" (or "ㅆ") plus "ㅎ" sound, but "ㄱ+ㅎ" As in the case of , there is a feeling that the energy of "heu" is very slightly mixed. Therefore, it seems that siot and soft ㅎ can be expressed as "ㅅㆆ" written side by side or as letters linked up and down. "z" is a half-tone. There is an argument to write "ㅿ".

"은 현대 한국어의 "ㅈ"과 가장 유사한데 "ㅈ"보다는 부드러운 발음으로 느껴진다. 따라서 "

" 또는 "

"으로 할 수 있다. "d"은 "" 보다 강한 발음이다. 따라서 "ㅉ+ㅇ"의 연서(또는 병서) 형태로 표기하는 것을 고려할 수 있다. "church" 등에서 나타나는 "ch"에 대응되는 발음은 현재 "ㅊ"으로 통용되고 있으므로 언급하지 않는다. "

"is most similar to modern Korean "ㅅ", but it feels softer than "ㅅ". Therefore, "

" or "

"d" is a stronger pronunciation than "". Therefore, it can be considered to write in the form of a conjugation (or conjugation) of "ㅳ + ㅇ". Pronunciation corresponding to "ch" in "church" etc. is not mentioned because it is currently used as "ㅋ".

" 또는 "

" 과 같이 표기할 수 있다. The pronunciation of "l" in English is written as "ㄹ" in modern Korean, and there seems to be no objection. If "l" in English is "ㄹ", "r" in English has "ㄹ" as the basic sound and can be seen as a weaker pronunciation than "ㄹ".

" or "

" can be written as

In the above, we have explained how to express some representative pronunciations that are present in English but not in modern Korean using the existing Hangul consonants. The above can be similarly applied to phonetic transcriptions of other languages.

31.3.2 Display method of extended Korean

Displaying foreign language pronunciations that are not in modern Korean as described above will be referred to as "extended Hangul" for convenience. It is a concept that includes both the use of the old Hangul itself in Unicode and the methods described above.

The characters in Unicode in Figure 4-33 (*) are Korean archaic words contained in old literature in the past registered as Unicode. Therefore, if you look at the Unicode of Figure 4-33 (*), you can observe the characters used in the old literature. By the way, if you look at the letters written in combination with "X + ㅇ" or "ㅇ + X", you can see that there is "X + ㅇ" and "ㅇ + X" at the same time. Here, "X" is any consonant, and "ㅇ" is "Leeung". That is, the pronunciation of the letters "X + ㅇ" and the letters "ㅇ + X" are different, and it is assumed that they tried to express the subtle difference in pronunciation. Of course, in-depth investigation of old literature is required to confirm this, but the present inventor, who is not a Korean linguist, cannot afford to do so.

"과 같이 병서된 글자가 유니코드에 있으면 "

"과 같이 연서된 글자는 없는 것이다. 단 하나 예외처럼 보이는 것이 "

" 과 "

"인데, "

"에서의 이응은 "옛이응" 이므로 "

"에서의 "ㅇ"과는 다르다고 할 수 있다. 결국 "X+ㅇ" 형태에서 연서된 글자가 유니코드에 존재하면 병서된 글자는 유니코드에 없고, 반대로 병서된 글자가 유니코드에 존재하면 연서된 글자는 유니코드에 존재하지 않는다고 할 수 있다. 이를 정리하면, "X+ㅇ" 형태의 글자를 상하 연서 또는 좌우 연서로 표현한 것은 2가지 다 같은 발음을 나타내는 것으로 정의할 수 있는 것이다. What is described below is the essence of the present invention. The important thing is that if "X + ㅇ" has letters written vertically, there are no letters written side-by-side. For example, if a concatenated letter such as "ㅸ" is in Unicode, a concatenated letter such as "ㅅㅇ" is not in Unicode (ie, in the old literature). Likewise "

"If there are conjoined characters in Unicode, such as "

There are no letters written together like ". The only thing that looks like an exception is "

" class "

"It is,"

The yi-eung in " is "old yi-eung", so "

It can be said that it is different from "ㅇ" in ". In the end, if the concatenated characters in the form of "X + ㅇ" exist in Unicode, the conjugated characters do not exist in Unicode, and conversely, if the concatenated characters exist in Unicode, they are concatenated. It can be said that characters do not exist in Unicode. To summarize this, if a letter in the form of "X + ㅇ" is expressed as a top-down sequence or a left-right sequence, both of them can be defined as expressing the same pronunciation.

Next, a method of expressing the letters written together or written in parallel will be described. In Korean Hangeul, the consonant is on the left side and the vowel is on the right side (e.g. "ga". For convenience, (1) type or vowel right type), the consonant is on the upper side and the vowel is on the lower side. There is a form (eg "gu". For convenience, (2) form or vowel lower form), and an intermediate form (for convenience (3) form. eg "and").

"로 표시하고, 모음 "ㅜ"와 결합하면 "

"와 같이 좌우로 병서된 형태로 표시되는 것이 바람직하다. (3)번형태의 경우는 연서 또는 병서 중 어느 한가지를 적용할 수 있는데, 절충방안으로는 유니코드에 있는 형태(연서 또는 병서)대로 적용하는 방안이 있을 수 있다. 예를 들어, "ㅸ"은 유니코드에 상하 연서 형태로 있으므로 "ㅘ"와 결합시 연서형태로 표시하는 것이고, "

"은 좌우 병서 형태로만 유니코드에 있으므로 "ㅘ"와 결합시 병서 형태로 표시하는 것이다. (3)번형태를 표시하는 방법은 초성자음만이 입력되었을 때도 유용하게 응용될 수 있다. 모음이 입력되기 전에 초성자음으로써 "X+ㅇ"형태의 자음이 입력되면, 상하 연서로 표시할 지, 좌우 병서로 표기할 지 정하기 어려운데, 유니코드의 기본형을 표시할 수 있는 것이다. 예를 들어 처음 입력상태에서 "ㅂ"와 "ㅇ"이 눌러져서 초성자음 "X+ㅇ"가 인식되었을 때, 유니코드에 있는 상하 연서로 "ㅸ" 으로 표시할 수 있는 것이다. 그 다음에 "ㅡ" 또는 "ㅜ"가 입력되면 "

" 또는 "

"로 표시되는 것이다. 만약 초성자음 "ㅸ" 다음에 "ㅣ"가 입력된다면 "

"로 표시될 것이다. 이는 "

"에 대해서도 마찬가지이다. Therefore, when consonants in the form of "X + ㅇ" are expressed as initial consonants, it is preferable to display them in the form of consonants up and down in the form of (1), and in the form of left and right in the form of (2) it is desirable In the form (3) above, a concatenated or combined form can be selectively applied. For example, in Unicode, only upper and lower concatenation forms such as "ㅸ" are presented, but when combined with the vowel "ㄴ", "

", and when combined with the vowel "TT", "

It is desirable to display it in the form of writing left and right like ". (3) In the case of the form, either conjugation or conjugation can be applied. As a compromise, the form (conjunction or conjugation) in Unicode For example, since "ㅸ" is in the form of a top-down concatenation in Unicode, it is displayed in a concatenated form when combined with "ㅘ".

Since " is only left-right consonant form in Unicode, it is displayed in consonant form when combined with "ㅘ". The method of displaying the form (3) can be usefully applied even when only initial consonants are input. Vowels are input If a consonant in the form of "X + ㅇ" is entered as the initial consonant before it becomes a consonant, it is difficult to specify whether to display it as a top-down consonant or a left-right consonant, but it is possible to display the basic form of Unicode. For example, in the first input state, " When the initial consonants "X + ㅇ" are recognized by pressing "ㅅ" and "ㅇ", it can be displayed as "ㅸ" by upper and lower consonants in Unicode. Then, if "ㅡ" or "ㅜ" is entered, "

" or "

". If "ㅣ" is entered after the initial consonant "ㅸ", "

". This will be displayed as "

"The same goes for

"과 같이 표시할 수 있다. 네모꼴로 표현되는 자모결합글자에서 종성자음이 위치할 공간을 확보하기 위해서이다. 표시되는 순서는 "ㅸ" 이 소정의 수단(예. "ㅂ"과 "ㅇ"의 순차입력 또는 특정 문자입력시스템에서 정해진 수단)에 의하여 "ㅸ"이 초성자음으로 인식되었을 때는 "ㅸ"으로 표시되고, 이어서 "ㅣ"가 입력되면 "ㅸㅣ"로 표시되고, "ㄱ"이 입력되면 "

" 이 표시되는 것이다. In the above (1), (2), and (3) forms, examples of cases where there is no final consonant are given, but if there is a final consonant (eg "gak", "guk", "gwak". For convenience, number (4) Regardless of the presence or absence of a final consonant, "X + ㅇ" as a leading consonant may be displayed in a left-right consonant form or a top-down consonant form according to the form (1), (2), and (3) above, and the above ( 1) As in the form, the initial consonant "X + ㅇ" can be displayed. In the case of letters with final consonants, even if the vowels of the vowel right type are combined, displaying them as left and right consonants is to secure the area where the final consonants will be located. For example, even when the vowel "ㅣ", which is a vowel-like vowel, is combined, if there is a final consonant "ㄱ", the initial consonant is left and right and "

It can be displayed as ". This is to secure a space for the final consonant in the consonant consonant expressed in a square shape. When "ㅸ" is recognized as a leading consonant by sequential input or by means determined in a specific character input system), it is displayed as "ㅸ", and when "ㅣ" is input, it is displayed as "ㅸㅣ" and "ㄱ" is input When "

" will be displayed.

" 을 종성자음으로 사용하는 경우 비록 유니코드에는 상하 연서의 형태로 되어 있으나, "

" 형태로 표시하는 것이 바람직하다. 예를 들어 "

" 과 같이 "ㄹ+ㅇ"을 좌우 연서로 표시하는 것이 상하 연서로 표시하는 것보다 형태적인 안정감을 주는데 훨씬 도움이 된다. 이는 "X+ㅇ" 형태의 모든 자음이 종성자음으로 사용될 때 동일하게 적용될 수 있다. Consonants linked up and down appear only in the form of "X + ㅇ". Even when the letters in the form of "X + ㅇ" exist only in the form of upper and lower consonants in Unicode, when used as a final consonant, it is preferable to always display them in the form of left and right concatenation. For example, to indicate the pronunciation of "~er" in English, "

When " is used as a final consonant, although it is in the form of upper and lower consonants in Unicode, "

It is preferable to display it in the form of ". For example, "

Displaying "ㄹ + ㅇ" as a left-right sequence, such as ", is much more helpful in giving a sense of morphological stability than displaying it as a top-down sequence. This can be equally applied when all consonants in the form of "X + ㅇ" are used as final consonants. .

" 을 들 수 있고, "XYY"형의 사례는 "

" 를 들 수 있고, "XXY"형의 사례는 "

" 를 들 수 있고, "XYZ"형의 사례는 "ㅴ" 를 들 수 있다. 상기 "XXX"형의 경우는 삼각형 형태로 "X" 아래에 "XX" 를 두는 형태로 표시되거나, 역삼각형 형태로 "XX"아래에 "X"를 두는 형태로 표시되는 것이 바람직하다. 예를 들어 "

"을 삼각형 형태로 표시하면 "

" 가 된다. "XYY"형의 경우는 삼각형 형태로 "X"아래에 "YY"를 두는 형태로 표시되는 것이 바람직하다. 예를 들어 "

"을 삼각형 형태로 표시하면 "

" 이 된다. "XXY"형의 경우는 역삼각형 형태로 "XX" 아래에 "Y"를 두는 형태로 표시되는 것이 바람직하다. 예를 들어 "

" 을 역삼각형 형태로 표시하면 "

" 이 된다. "XYZ" 형태는 삼각형 형태로 "X" 아래에 "YZ"를 두거나, 역삼각형 형태로 "XY" 아래에 "Z"를 두는 형태로 표시되는 것이 바람직하다. 예를 들어 "ㅴ"을 삼각형 형태로 표시하면 "

" 가 된다. 이렇게 하는 것이 우리 한글의 형태미를 살리는데 훨씬 도움이 된다. Going one step further, looking at the form in which three or more alphabets used in our old Korean language (old Hangul) are written in parallel is as follows. There are "XXX" type, "XYY" type, "XXY" type, and "XYZ" type. Cases of type "XXX" are "

", and the case of type "XYY" is "

", and the case of type "XXY" is "

", and examples of the "XYZ" type include "ㅴ". In the case of the "XXX" type, it is displayed in the form of a triangle with "XX" placed under "X", or in the form of an inverted triangle. It is preferable to display it in the form of putting "X" under "XX". For example, "

If " is displayed in the form of a triangle, "

". In the case of "XYY" type, it is preferable to display "YY" under "X" in the form of a triangle. For example, "

If " is displayed in the form of a triangle, "

In the case of the "XXY" type, it is preferable to display it in the form of placing "Y" under "XX" in the form of an inverted triangle. For example, "

If " is displayed in the form of an inverted triangle, "

It is preferable to display "XYZ" in the form of placing "YZ" under "X" in the form of a triangle or placing "Z" under "XY" in the form of an inverted triangle. For example, "ㅴ If " is displayed in the form of a triangle, "

". Doing this is much more helpful in preserving the beauty of the shape of our Hangeul.

" 을 표시하려면, "

"에 대응되는 새로운 코드를 유니코드에 등록하여야 하는 것이 아닌가 의심할 수도 있다. 그러나 낱자로의 유니코드를 사용하여 자모결합된 글자를 표현한다면 (예. 첫가끝조합형, .... 등등), 순경음 "ㅸ" 의 유니코드를 그대로 사용할 수 있다. 단, 버튼의 눌러짐에 따라 한글조합을 처리함에 있어 모음우치형의 모음(예. "ㅏ")이 입력되면 상하 연서된 형태(예. "ㅸ")로 처리하고, 모음하치형의 모음(예. "ㅡ")가 입력되면 좌우 병서된 형태(예. "

")로 처리하는 것이다. 이는 다른 "X+ㅇ" 형 자음에 대해서도 마찬가지이며, "XXX"형, "XYY"형, "XXY"형, "XYZ"형 자음에 대해서도 마찬가지이다. not in unicode"

To display ", "

You may wonder whether a new code corresponding to " should be registered in Unicode. However, if you use Unicode as a character to express conjoined characters (e.g. end-to-end combination, .... etc.), Unicode of the consonant sound "ㅸ" can be used as it is However, in processing the Korean combination as the button is pressed, if a vowel of the vowel type (eg "a") is input, the form of conjugation up and down (eg "ㅸ"), and if a vowel-shaped vowel (eg "ㅡ") is entered, it is written in a left-right format (eg "

"). This is the same for other "X + ㅇ" type consonants, and the same for "XXX" type, "XYY" type, "XXY" type, and "XYZ" type consonants.

32. Entering spaces, numbers, and English alphabets in Korean mode

32.1 Entering Spaces

In the above, it was proposed to solve the ambiguity when inputting Korean Gore without using a separate distinguishing button. In the keypad in Fig. 15-3 adopted by Samsung Electronics, the [#] button, which is not used directly for character input, is used as a separator button and a blank button. In reality, among the up/down/left/right movement buttons, the right movement button (usually a right arrow or similar symbol is displayed on the button) is used as a separator button and a space button, and it is not an input of one word. In the case of inputting a sentence, since the up/down/left/right movement buttons are virtually essential for editing a previously entered sentence, it is not very meaningful to use the [#] button for this purpose. However, there may be a requirement that up to blanks be entered within 12 buttons including 10 number buttons and [*] and [#] buttons.

In the previous application of the applicant, it was shown that "y = xㅡㅡ" was entered, and it is obvious that this can be applied to input of special characters or spaces. In the case of inputting only modern Korean, there is a case where the [ㅡ] button or [ㅣ] button pressed twice after input of a consonant without a lattice sound or hard consonant (ie, double consonant) (eg, "ㄹ") was treated as a blank. have. For example, "blank = ㄹㅣㅣ". This has a disadvantage in that a space cannot be added between words when the right movement button is also used as a space button, but in this case, it can be usefully used. For example, in order to add a space between "A" and "I" after inputting "Kanada", a space is not added even if the cursor is placed on "B" with the move button and the right button is pressed again. In this case, as exemplified above, "blank = ㅣㅣ" can be added. After a space is entered once, vowels do not appear consecutively in the input start state (ie, immediately after entering a space) in Korean, so pressing the [ㅣ] button once more can be treated as a space being entered once more. For example, it can be done with "2 spaces = ㅣㅣㅣ".

In the case of inputting even Korean words, the [ㅡ] button or the [ㅣ] button does not apply unless "trailing alphabet long hitting processing" is applied to "alphabet-letter ambiguity" or "vertical/horizontal vowel long hitting processing" is applied. No long press. Therefore, one of pressing and holding the [ㅡ] button or the [ㅣ] button can be treated as a blank input. If the [ㅣ] button is pressed for a long time and a space is entered for the first time, using the property that a letter does not start with a vowel after a space in Korean, we can treat one press of the [ㅣ] button as entering a space once more can For example, "2 spaces = ㅣ~ㅣ", 3 spaces = ㅣ~ㅣㅣ", .... Of course, you can enter "2 spaces = ㅣ~ㅣ~" .

Treating the vowel button pressed after a space (eg, the [ㅣ] button) as a space (eg, "2 spaces = ㅣ~ㅣ") has the disadvantage of making it difficult to input a vowel after a space. In real life, vowels starting with "ㅡ" like "ㅠ" are used relatively frequently, but vowels starting with "ㅣ" are not used very much. Therefore, it would be better to use the long press of the [ㅣ] button and the continuous press after the long press as a blank input and continuous blank input.

Next, a long press of the [ㅡ] button can be used for other functions such as the “mode conversion” function. Since the mode switching function is not a function that is frequently used, there is no big problem with mode switching by pressing and holding for a long time. Realistically, since the [mode conversion] button will be provided as a separate button, it has no practical meaning and only shows the possibility of doing so. Because if it is necessary to input a letter such as "ㅠㅠㅠ" rather than a complete word such as "name", "company name", ..., it is necessary to input a large number of words and sentences, This is because liquid crystals for viewing words, sentences, ...), up/down/left/right movement buttons for editing, and mode conversion buttons will be provided separately.

32.2 Entering numbers in Korean mode

Currently, when inputting modern Korean, pressing and holding a number button in Hangul mode often inputs a corresponding number. For example, if you press and hold the [a] button to which the number "1" is assigned in the Korean mode, the number "1" is input. However, even in the keypad illustrated in Figure 4-*, inputting only modern Korean is possible without ambiguity (or very little ambiguity when input by repeated pressing, such as "3 + other input method"), so it is possible to input Korean by long pressing the number button. You can enter a number. However, when inputting up to Korean archaic words, a long press of the consonant button (ie, number button) can be used for "initial consonant position ambiguity". That is, in order to input modern Korean as well as Korean language, it is impossible to input numbers by long-pressing the number buttons.

In order to input a number of numbers such as phone numbers and resident registration numbers, it is not realistic to input using long presses of the number buttons in the Korean mode, and you will have to switch to the number mode and input them. However, it will be necessary to provide a means for inputting a number entered in the middle of the Korean input in the Korean mode. The following describes the technique of inputting numbers in Korean mode.

As the applicant suggested in the previous application, it was suggested that "y = x + (the maximum number of times that the vowel button can be pressed repeatedly + press one more time)". The "maximum number of times that the vowel button can be pressed repeatedly" means the maximum number of times in which Korean combinations are possible. In the above, “y” may be a “number”, “x” may be an input consonant, and “vowel button” may be a [ㅡ] button, a [ㆍ] button, or a [ㅣ] button. First, for example, when only modern Korean is input, "K = ㅡㅡㅡ", so "number 1 = ㅡㅡㅡㅡ" can be used. As another method, since it is said that the [ㆍ] button is pressed up to two times after a consonant is entered, “number 1 = ㄱㆍㆍㆍ” can also be used. In the previous application, the technique of pressing the [•] button three times was shown as "ㅎ", which can be applied simultaneously. The input value "ㄱㆍㆍㆍ" can also be interpreted as "ㄱㅎ", but if "ㅎ" is combined after the initial consonant of "ㄱ" and does not form a consonant letter, input the number "1" as above that can be treated as However, if the pressing of the [a] button among a series of button presses is not the initial consonant but the final consonant, it must be entered clearly that "a" is the initial consonant. For example, "Number 1 = A ~ㆍㆍㆍ" should be applied by applying "trailing alphabet long hit processing".

"가 결합된 글자로 될 수 있다. 그러나 현재까지 유니코드v2.0에 등록된 한글고어 모음에서도 "ㅡ"가 3개 연속결합된 모음은 존재하지 않는다. 따라서 "숫자 1 = ㄱㅡㅡㅡㅡㅡ"로 할 수 있다. 그러나 한글고어의 입력을 포함하면 "숫자 7", "숫자 9" 등의 경우는 도면4-34(a)에 있는 것처럼 훨씬 더 많은 횟수가 눌러져야 하는 문제가 있다. 한글고어의 입력을 포함하는 "아래아 3모음법"에서도 자음의 입력 다음에 [ㆍ]버튼은 최대 2번까지 눌러질 수 있다. 따라서 상기 "숫자 1 = ㄱㆍㆍㆍ"을 유사하게 적용할 수 있다. 다만 한글고어에서는 "xy" 형태의 자음이 초성으로도 나올 수 있으며, "y"위치에 "ㅎ"이 있는 경우(예. "

")도 있기 때문에 완전히 동일하게 적용하기 어렵다. Next, in the case of inputting modern Korean as well as Korean language, the input of numbers in the Korean mode will be examined. "ㄱㅡㅡㅡㅡ" is "ㅋ" under "ㅋ"

" can be a combined character. However, even in the collections of Korean ancient words registered in Unicode v2.0, there is no vowel in which three consecutive "ㅡ" are combined. Therefore, "number 1 = ㅡㅡㅡㅡ ㅡ". However, if you include the input of Korean language, "number 7", "number 9", etc. have a problem that you have to press a lot more times, as shown in Fig. 4-34 (a). Even in the "Area 3 Vowel Method" including the input of Korean Gore, the [ㆍ] button can be pressed up to 2 times after consonant input. Therefore, the above "number 1 = ㄱㆍㆍㆍ" can be similarly applied However, consonants in the form of "xy" can also appear as initial consonants in Korean Gore, and if there is "ㅎ" in the position of "y" (e.g. "

"), so it is difficult to apply them exactly the same.

As described above, in the case of using the [ㅡ] button or the [ㅣ] button repeatedly after inputting consonants, the number of repeated button presses becomes too large, including inputting Korean Gore consonants with a combination of vowel buttons (See Fig. 4-34 (a)) has a disadvantage in that the number of pressing is excessively increased. Therefore, it can be "number y = xㅡ~" (ie, "number y = x *~) or "number y = xㅣ~" (ie, "number y = x #~"). In the above, "x " is 10 number buttons from [1] to [0]. It is natural that this is applicable as long as long pressing of the [ㅡ] button or [ㅣ] button is not applied to the input of Korean Gore. For example, It can be done with the number "1 = ㄱㅣ~ = 1 #~". To reorganize this, number input in Korean mode is "pressing the button with numbers arranged once + long pressing the button with non-numbers arranged" It is treated as a combination.

This can also be applied to Korean keypads of existing large manufacturing companies in Figs. 15-3 and 15-4. That is, number input in the Korean mode is performed by "pressing the number button once + long pressing the button on which numbers are not arranged". For example, in the keypad of Samsung Electronics Co., Ltd. in Figure 15-3, the number "2 = ㆍ+ #~" and the number "4 = a + #~" can be used. In the keypad of Figure 15-4, you can do something like the number "2 = B + #~".

32.3 Input of English alphabet in Korean mode

Above, the technique of inputting numbers in Hangul mode was shown. Next, inputting English alphabets in Korean mode is presented. Usually, as shown in Fig. 1-1, an English keypad in which three alphabets are assigned to one button is mainly used. In addition, syllables in Korean always start with consonants, not with vowels. Therefore, the English alphabet assigned to the button can be input with the input of a number and the vowel button of [ㅡ], [ㆍ], or [ㅣ] pressed after the number. This is because normal syllables do not start with vowels in Korean Hangul. Expressed as an expression, it is like "English alphabet y = number + vowel button". For example, it may be "a = 2 + vowel button = ㄴㅣ + vowel button".

In a normal case, about three English alphabets (eg "a b c") are arranged in one button (eg, [2] button) as shown in Fig. 1-1. Each alphabet can be input according to the vowel button [ㅡ], [ㆍ], or [ㅣ] button pressed after the number input. That is, the first arranged English alphabet (eg "a") is "number 2 + ㅡ", the second arranged English alphabet (eg "b") is "number 2 + ㆍ", and the third arranged English alphabet ( Ex. "c") can be "Number 2 + ㅣ". For example, if pressing the vowel button [ㅡ] button is applied to the input of the English alphabet “a” (ie, the first English alphabet arranged), “a = 2ㅣ = ㄴㅣ~ ㅡ” is obtained. If pressing the vowel button [ㆍ] button is applied to the input of the English alphabet “b” (ie, the second arranged English alphabet), it becomes “b = 2ㆍ = ㄴㅣㆍ”, and the English alphabet “c” (ie , If you apply the press of the vowel button [ㅣ] button to the input of the third arranged English alphabet), it becomes "c = 2ㅣ = ㄴㅣ~ ㅣ". If you enter "2a", it will be "2a = ㄴㅣ ㄴㅣㅡ". As described above, blanks in the display of the input values are meant to improve readability and make the readers of this document more comfortable, but do not have meaning.

In the above description, you may have doubts whether "English alphabet = number + vowel button repeatedly pressed". If, after entering a number, pressing the [ㅡ] button once is “a”, pressing the [ㅡ] button twice is “b”, and pressing the [ㅡ] button three times is “c”, the existing This is because there is ambiguity as in the iterative selection method of .

When the above is applied, if a vowel (eg, "ㅠ") appears consecutively with the number "2" (ie, "2ㅠ"), it cannot be entered. Similarly, conventional means such as a time delay (ie, a timer) and a division button may be applied. However, in reality, there will be very few cases where "2ㅠ" is input like this.

As shown in Figs. 1-3, when four alphabets of "p", "q", "r", and "s" are assigned to the [7] button, the three alphabets can be processed as described above. The other alphabet can be input with "one of the three alphabets + vowel button not pressed". For example, if "p", "q", and "r" are entered as "a", "b", and "c", respectively, "s = r + unpressed vowel button = p ㆍ or p ㅣ or q ㅡ or q ㅣ or r ㅡ or r ㆍ". Here, it is easy to see that "pㆍ = ㅅㅡㅡㅡㆍ" and "pㅣ = ㅅㅡㅡㅣ".

As described above, inputting the English alphabet by pressing a combination of "input of numbers" and "a button in which Korean consonants are not arranged (more precisely, a button that does not start inputting consonants)" is pressed in FIGS. 15-3 and 15- It can also be applied to other keypads such as 4. For example, in the keypad of Figure 15-3, "a = 2+ㅣ~ = ㆍ#~ㅣ", "b = 2+ㆍ~ = ㆍ#~ㆍ", "c = 2+ㅡ~ = ㆍ# You can do something like "~ㅡ". In the keypad of Figure 15-4, as in "a = number 2 + * = B # ~ *", "b = number 2 + 0 = B # ~ 0", "c = number 2 + # = B # ~ #" can do. The reason why the [*] button (ie, the [Overwrite] button) and the [#] button (ie, the [Side by side] button) can be used in the last combination in Figure 15-4 is the input rule of the keypad in Figure 15-4. ㅋ = ㄱ*", so the input of consonants does not start with pressing the "*" button.

Furthermore, the same can be applied to the case of inputting a number by long pressing a button assigned to a number in the Korean mode (typically, Korean consonants are also arranged). If the number "2" is input by pressing and holding the [2] button (ie, the [b] button) in the 4-* keypad of the present invention (applies long pressing to alphabet input, such as preceding alphabet long hitting processing and trailing alphabet long hitting processing) On the premise that it does not), "a = (number) 2ㅡ = b~ㅡ = (button) 2~ㅡ" can be done. As another example, the above description is the same even when the number 4 is input by long pressing the button to which the number "4" is assigned in Fig. 15-3 (ie, the [4] button and the [A] button at the same time). can be applied In Figure 15-3, after inputting the number "4 = a ~ = 4 ~", if any button that does not start inputting a consonant (eg, [ㅣ] button) is pressed once, any of the buttons arranged in the [4] button An alphabet (eg, "g", the first English alphabet) can be input. That is, "g = a ~ l = 4 ~ 1". Similarly, in the keypad of Figure 15-4, "a = b ~ * = 2 ~ *" can be input.

33. Korean input on a keyboard such as a PC

33.1 Improvements in Korean input with Korean double keyboard

The double keyboard currently used as a standard in PCs is shown in Figure 18-1 (a). Fig. 18-1 (b) shows only the left part including the character button in Fig. 18-1 (a). As everyone knows, when the [a] button marked with "a" is pressed once, "a" is recognized. In addition, "ㄲ" marked on "a" indicates that "ㄲ" is recognized when the [a] button is pressed simultaneously with the [Shift] button. The question of whether “ㄲ” or the like is additionally displayed on the button is optional (eg, “ㄲ” may or may not be additionally displayed on the [a] button).

In the current two-beol keyboard, the [ㄹ] button (the [F] button in the English keyboard function) is the reference button where the left index finger is located, and the [sh] button (the [J] button in the English keyboard standard) is the right index finger This is the standard button to be located. The left hand area for pressing buttons using the left hand includes 15 buttons on the left including the [ㅅ], [ㅎ], and [ㅠ] buttons, and the buttons in the right hand area for pressing buttons using the right hand are [ㅛ], [ㅗ These are 11 buttons on the right, including ] and [TT] buttons. The fact that there are 11 character buttons in the right hand area is based on only buttons arranged with English alphabets. The composition of the consonant arrangement of the current standard 2 beolsik keyboard is arranged with 14 consonants of "a", "b", "c", ... "p", "heh", and the vowels are "a", " ㅑ", "sh", "ㅕ", "ㅗ", "ㅛ", "TT", "ㅠ", "ㅡ", "ㅣ" plus 10 consonants including "ㅐ" and "ㅔ" It consists of 12 buttons. As a result, if 14 consonants are arranged in the left hand area composed of 15 buttons, one button remains, and if 12 vowels are arranged in the right hand area composed of 11 buttons, one button is missing. As a result, the current two-beol keyboard is a form in which the least frequently used “ㅠ” is arranged on the remaining buttons in the left hand area.

Unlike a keypad in the form of a numeric keypad, the user does not recognize which alphabet is in which position, and uses the autonomic nervous system with "hands" and "body" instead of "eyes" and "head". However, the presence of the vowel "ㅠ" in the left hand area, which can be seen as a consonant area, is an element that gives an unconventional and unnatural feeling. This is the same for those who have used the Korean keyboard for more than 25 years like the present applicant, and if you search on the Internet, you can easily search for cases that complain of inconvenience and point out the need for improvement for these reasons.

The five light consonants (twin consonants) "ㄲ", "ㄸ", "ㅃ", "ㅆ", "ㅆ" are each It is recognized by simultaneously pressing the "j" buttons. For example, "ㄲ = Shift^ㄱ". Here, "^" is used for convenience, and "^" is to express that the [a] button is pressed while the [Shft] button in front of it is pressed. However, "^" may be replaced with "+" indicating successive pressing. It is the same expression as "Shift+X" in the previous application. It was said that "+" may not be displayed in the expression of the input value, and in order to make the input value easier to read, sometimes "+" is displayed, sometimes "+" is not displayed, but it is the same expression. Even if it is expressed without "^" or "+" like "Shft X", [Shift] is considered to be pressed together with the next pressed button. Even in Windows OS, if the "Sticky Key" function is set to be used, the same input can be performed by sequentially pressing "Shift+X" instead of pressing "Shft^X" simultaneously, and in the present invention, the sticky key is Of course, it also includes cases where it is applied. Using shift becomes an element that hinders the convenience of using the keyboard, and there have been many attempts to input without using shift. Most of them were attempts to apply the two-beol-style Hangul automata by slightly modifying it. [ ㅐ] button is pressed twice to input "ㅒ" (ie, "ㅒ = ㅐ + ㅐ").

There have been endless attempts to place "ㅆ", which is significantly used among the five hard consonants, on an independent button. Professor K of S University, a scholar and inventor, placed "ㅆ" on the [ㅠ] button (ie, [B] button) in Figure 18-1 (a) or Figure 18-1 (b), and placed it in the most difficult position to press. It is proposed to place "ㅠ" after subtracting "ㅔ" from the position of the [ㅔ] button (ie, the [P] button) in . "ㅠ" is recognized as pressing the [ㅠ] button (ie, the [P] button) once, but since "ㅔ" is not arranged on the button, it is recognized as a combination of the [sh] button and the [ㅣ] button. That is, "ㅔ = ㅕ + ㅣ", "ㅖ = ㅕ + ㅣ". Another slightly modified this, placing "ㅆ" on the current [ㅠ] button (i.e., "B" button), and recognizing "ㅠ" by pressing the [TT] button twice (i.e., "ㅠ=TT"). + TT") was also suggested. Here, as in the case of inputting "ㅖ = ㅔ + ㅔ" and "ㅒ = ㅐ + ㅐ", inputting "ㅠ = TT + TT" was also used as a modified double-type automata on the keyboard. You can easily find out if you search for "Saenaru" input method on the Internet.

Among the five hard consonants (double consonants), the frequency of use of one "ㅆ" is overwhelmingly about 1.5 times the sum of the frequencies of use of all the other four hard consonants. In the combined frequency of consonants and vowels, "ㅆ" ranks 20th with a frequency of 1.135%, and "ㅠ" ranks 33rd with a frequency of 0.216%. Among 30 consonants (including double endings), "ㅆ" ranks 11th with a frequency of 1.913%, and among 21 vowels, "ㅠ" ranks 17th with a frequency of 0.513%.

"을 "ㅜ+ㅜ"로 입력하지 못하는 문제가 있다. 물론 "

= Shift^ㅜ"로 한다면, "ㅠ = ㅜ+ㅜ"로 할 수도 있다. 그러나 "ㅠ = ㅜ+ㅜ"로 한다면, 형태적으로 "ㅜ" 2개로 이루어진 모음인 "

"를 "ㅜ+ㅜ"로 입력하는 것이 가장 자연스러움에도 불구하고 그렇게하지 못하는 것이다. In the present invention, the most frequently used "ㅆ" among light consonants is placed on the current [ㅠ] button (ie, [B] button) in the left-hand area (ie, consonant area) (ie, [B] button once Recognizing "ㅆ" by pressing), [Shift] button and [TT] button are combined to input "ㅠ" (ie, recognizing "ㅠ = Shift^TT"). Since "ㅆ" was placed on the [B] button without "ㅠ", a method to input "ㅠ" must be presented together. See Figure 18-2. It can be done with the currently used "ㅠ = TT + TT", but in this case, "TT" is a vowel in which "TT" is linked up and down in Korean old language vowels.

There is a problem that " cannot be entered as "TT + TT". Of course, "

= Shift ^ TT", you can also do "ㅠ = TT + TT". However, if you use "ㅠ = TT + TT", morphologically, "TT" is a collection of two "TT"

Although it is the most natural to enter "TT + TT" as "TT + TT", it is not possible to do so.

In the past, in the problem of inputting Korean archaic words (ie, old Hangul), there has been difficulty in how to input the half-tone "ㅿ". A typical editor program that can input old Hangeul is "Aeraeah Hangul". In a word processor, enter "ㅿ = Shift^ㅁ". However, it is not logical to say that the half consonant "ㅿ" is related to the completely unrelated consonant "ㅁ". Therefore, if it is settled to arrange "ㅆ" on the [B] button and input by pressing the corresponding button once, use the [ㅅ] button related to pronunciation and form to enter "ㅿ = Shift^ㅅ" it is reasonable

However, currently, a modified 2-beol type input technology that inputs "ㅆ" by pressing the [ㅅ] button twice is also used. (Refer to the old Hangul input function of the Hangul Hangul word processor, Saenaru Hangul input method, etc.) It is uncertain whether the time when the old Hangul halftone "ㅿ" will be used in real life will come, and even if it does, the frequency of use is significantly higher than that of modern Korean consonants and vowels. will be low Therefore, prior to modern Korean input, "ㅆ" can be input by pressing the [ㅅ] button twice, and the half-tone "ㅿ" can be input by pressing the [ㅅ] button 3 times. However, in this case, there is a problem that pressing "ㅅㅅㅅ" is not recognized as the final consonant "ㅆ" and the initial consonant "ㅅ", but is recognized as a half consonant "ㅿ". Therefore, as stated in the previous application of the applicant, as the [ㅅ] button is repeatedly pressed, it operates as "ㅅ → ㅆ or ㅅㅅ → ㅆㅅorㅅㅆ → ㅆ", and 5 consecutive presses of the [ㅅ] button are treated as a half-tone "ㅿ" can do. However, in practice, there may not be many cases in which the [ㅅ] button is pressed 4 times in a change due to repeated pressing of the [ㅅ] button, which should be treated as an absolute "ㅆ". Therefore, as the [ㅅ] button is repeatedly pressed, "ㅅ → ㅆ or ㅅㅅ → ㅆㅅorㅅㅆ", and pressing the [ㅅ] button 4 times can be treated as a half-tone "ㅿ". That is, pressing 3 times, 4 times, or 5 times of the [ㅅ] button can be defined and used as a half-tone "ㅿ".

As mentioned, the keyboard using 10 fingers is a device that is used by the trained autonomic nervous system, so it may be difficult to change existing habits. Therefore, "ㅆ = Shift^ㅅ" is given priority to modern Korean input, but if "ㅆ" by "Shift^ㅅ" is continuously input, it can be processed as a half-tone "ㅿ". That is, it is made with a half tone "ㅿ = Shift^ㅅ + Shift^ㅅ" or "ㅿ = Shift^ㅅ+ㅅ". For "ㅿ = Shift^ㅅ + Shift^ㅅ", enter "ㅆ" by "Shft^ㅅ", then press "Shft^ㅅ" again while releasing both the [Shift] button and the [ㅅ] button. "ㅿ = Shift^ㅅ+ㅅ" is to press and release the [ㅅ] button while holding down the [Shft] button, and press the [ㅅ] button once more while the [Shift] button is still pressed. That means, both are the same expression that expresses pressing "Shift^ㅅ" twice. According to the usage frequency table of our modern Korean language, there is no case where the initial consonant "ㅆ" appears after the final consonant "ㅆ" (i.e., 0%). Of course, in reality, there is a possibility that there may be one or two words in which the initial consonant "ㅆ" appears after the final consonant "ㅆ", but it is not so much that it affects modern Korean life.

" 이 있다. 별도의 버튼으로 독립시킨 [ㅆ]버튼(즉, [B]버튼)과 [Shift]버튼을 조합하여 어떤 대상을 입력할 수 있는데, "ㅿ" 또는 "

" 중 어느 하나가 입력되도록 할 수 있다. 기존에 "ㅆ"을 "Shift^ㅅ"으로 입력하였던 습관을 고려한다면, "

= Shift^ㅆ" 으로 하는 것이 타당할 것이다. " Shift^ㅆ"으로 "ㅿ" 와 "

" 중 어느 하나를 입력한다고 하더라도, "ㅿ"가 연속하여 나오거나, "

"가 연속하여 나오는 경우는 거의 없을 것이다. 따라서 "Shift^ㅆ" 2번 눌러짐에 의하여 "ㅿ" 또는 "

" 중 나머지 한가지가 입력되도록 하는 것이 가능하다. 여기("ㅿ = Shift^ㅆ")에서 "ㅆ"은 [ㅆ]버튼(즉, [B]버튼)을 의미한다.Old Hangeul (Old Hangul), which has a strong relationship with "ㅅ", is the half-tone "ㅿ" and "

". You can input an object by combining the independent [ㅆ] button (i.e., [B] button) and the [Shift] button as a separate button.

Any one of " can be entered. Considering the habit of entering "ㅆ" as "Shift^ㅅ" in the past, "

= Shift^ㅆ" would make sense. With "Shift^ㅆ", "ㅿ" and "

Even if you enter any of ", "ㅿ" comes out in succession, or "

" will rarely appear in succession. Therefore, by pressing "Shift^ㅆ" twice, "ㅿ" or "

It is possible to have the remaining one of " input. Here ("ㅿ = Shift^ㅆ"), "ㅆ" means the [ㅆ] button (ie, the [B] button).

"을 입력할 수 있는 또 다른 방법은 [ㅅ]버튼과 [ㅆ]버튼의 눌러짐으로 인식되도록 하는 것이다. 즉, "

= ㅅ+ㅆ"이 된다. 우리 현대 한국어 사용빈도표에서 "ㅅ" 다음에 "ㅆ"이 연속하여 나오는 경우는 "0.003%" 로 조사되어 있으므로, 사실상 무시될 수 있을 정도의 미미한 수준이다. 단, "ㅆ" 다음에 "ㅅ"이 나오는 경우는 매우 많으므로, "

"의 입력에 "ㅆ+ㅅ"을 사용할 수는 없다. 또한 [ㅅ]버튼 3번 눌러짐으로 "

"을 입력하기 어려운 것은, "ㅆ = ㅅ+ㅅ"을 허용하는 경우 현대 한국어에서 "ㅆ" 다음에 "ㅅ"이 나오는 경우가 빈번하기 때문이다. "

= ㅅ+ㅆ"에서 "ㅆ"의 입력은 [ㅆ]버튼 한번누름에 의하는 것만이 가능한 것은 아니다. 기존 2벌식키보드에서처럼 "ㅆ = Shift^ㅅ" 으로 완전하게 "ㅆ"을 입력할 수 있는 수단으로 입력하는 것도 포함한다. "ㅆ = ㅅㅣㅣ" 와 모호성없이 완전하게 "ㅆ"을 입력하는 수단에 의하는 것(참고. 도면4-*의 키패드에서의 입력 사례)도 마찬가지로 가능하다. 만약 "

= ㅅ+ㅆ"으로 입력한다면, "Shift^ㅆ"으로 반치음 "ㅿ"을 입력하도록 할 수 있다. 현재는 키보드에서 "

"을 [ㅅ]버튼 3번 눌러짐으로 입력하고 있는데, 이 역시 가능하다. "

"은 초성자음으로만 쓰이고 종성자음으로는 쓰이지 않기 때문에 종성자음 "ㅆ" 다음에 "ㅅ"이 입력된 것을 "

"으로 처리하는 것이 아니고, "ㅆㅅ"으로 처리한다. "ㅆㅅ"다음에 [ㅅ]버튼이 2번 눌러지면 "ㅆ

"이 된다. "

Another way to input "is to be recognized as pressing the [ㅅ] and [ㅆ] buttons. In other words, "

= ㅅ + ㅆ". In our modern Korean usage frequency table, the case where "ㅅ" followed by "ㅆ" appears consecutively is "0.003%", so it is a negligible level. , "ㅅ" is often followed by "ㅅ", so "

"ㅆ + ㅅ" cannot be used for the input of ". Also, by pressing the [ㅅ] button 3 times, "

The reason why it is difficult to enter " is that "ㅅ" often appears after "ㅆ" in modern Korean when "ㅆ = ㅅ + ㅅ" is allowed. "

= ㅅ + ㅆ", the input of "ㅆ" is not only possible by pressing the [ㅆ] button once. As in the existing 2-beol type keyboard, "ㅆ = Shift^ㅅ" can completely input "ㅆ" It is also possible to enter "ㅆ = ㅅㅣㅣ" and "ㅆ" completely without ambiguity (Reference. Example of input on the keypad in Fig. 4-*). what if "

= ㅅ + ㅆ", you can input the half-tone "ㅿ" with "Shift^ㅆ". Currently, "

" is being entered by pressing the [ㅅ] button 3 times, but this is also possible."

Since " is used only as a first consonant and not a final consonant, "ㅅ" is entered after the final consonant "ㅆ"

", not "ㅆㅅ". If the [ㅅ] button is pressed twice after "ㅆㅅ", "ㅆㅅ"

"It becomes

At the time of the creation of Hunminjeongeum, 28 characters of Korean Hangeul were announced, and the characters "ㆍ, ㅿ, ㆆ, ㆁ" are not currently used. Since there is an attempt to write the unused four letters as well, inputting them naturally is also a necessary element in the invention of Hangul input technology. Below, "ㆍ" is done by pressing the [a] button twice or by "Shift^a", soft "ㆆ = Shft^ㅎ", oldieung "ㆁ = Shft^ㅇ", all of which can be said to be reasonable and natural. can However, the half-tone "ㅿ = Shift^ㅁ" is used, but the half-tone "ㅿ" is related to the unrelated "ㅁ", which harms the scientific nature of our Korean language. In the present invention, use the [ㅅ] button or [ㅆ] button associated with the halftone "ㅿ" (eg, press "Shfit^ㅅ", "Shfit^ㅅ" twice, or the [ㅅ] button three or more times. [ By pressing the [ㅆ] button twice or "Shift^ㅆ"), the halftone "ㅿ" can be entered without ambiguity (or almost without ambiguity).

Summarizing the above invention, since only consonants are placed in the button of the left hand area, which can be called the consonant area, confusion in consciousness can be eliminated, and "ㅆ" is recognized as two phonemes in modern Korean life, but rather one It is recognized as a grapheme, but at the same time, "ㅆ", which has a relatively high frequency of use, can be entered as "ㅠ = Shift^TT" while entering the [ㅆ] button once. The halftone "ㅿ" can also be input using the [ㅅ] button or [ㅆ] button, which has a strong correlation.

It is obvious that the present invention can be equally applied even when the position of the alphabets arranged on each button in the current two-beol Korean keyboard is partially changed or the alphabets arranged on the current two-beol Korean keyboard are slightly different.

33.2 Hangul 2 Beolsik Keyboard Hangul Gore Input

" 등)의 입력에 대하여 언급하였다. 제31장에서 한글 고어의 입력을 위한 수단을 제시한 바 있다. 이하에서 2벌식 키보드에서 일반적으로 한글고어를 입력할 수 있는 수단을 추가로 제시한다. Some of the old Korean consonants associated with "ㅅ" above (eg, half-tone "ㅿ", "

", etc.) has been mentioned. In Chapter 31, a means for inputting Korean archaic words has been suggested. Below, a means for inputting Korean archaic words in general on a two-beol type keyboard is additionally presented.

On the double keyboard, light consonants (double consonants) are entered as a combination of Shift and flat consonants (eg "ㄲ = Shift ^ ㄱ"). And grid sounds are arranged on a separate button (eg [ㅋ] button). By applying the modified Hangul combination logic, hard consonants are input (eg "ㄲ = ㄱ + ㄱ") by pressing the flat consonant button twice. The logic in Fig. 4-34(b) can also be applied to the keyboard.

"이 되고, 한번 더 눌러지면 역시 동일하게 "

"이 된다. 한번 더 눌러지면 "

ㄱ"이 될 수 있다. [ㄱ]버튼이 2번 눌러졌을 때의 "

" 다음에 모음(예. "ㅣ")이 입력되면 "

기"가 된다. [ㄱ]버튼이 3번 눌러졌을 때의 "

" 다음에 모음(예. "ㅣ")이 입력되면 "가끼"가 된다. However, since the lattice sound is separated as a separate button, pressing the flat consonant button 3 times may not be treated as a lattice sound. Therefore, the "3+ other input method" proposed by the applicant in the previous application can be applied only to the input of hard consonants input by the combination of the [Shift] button and the flat consonant button on the double-beol keyboard. That is, pressing the flat consonant button (eg, [a] button) three times is processed as a hard consonant (eg, "ㄲ"). Here, when the flat consonant button is pressed twice, it can be processed as "ㄱㄱ" or a temporary "ㄲ". As described above, when a vowel is input after the temporary "ㄲ", the final consonant "a" and the initial consonant "a" of the next letter are entered. For example, if the [A] button is pressed once after "A", it becomes "Gak", and if it is pressed once more, "

", and when pressed once more, the same as "

". When pressed once more, "

It can be "a". When the [a] button is pressed twice, "

If a vowel (e.g. "ㅣ") is entered after the "

When the [a] button is pressed 3 times, the "

If a vowel (eg "ㅣ") is entered after ", it becomes "Kaki".

As in the description of Fig. 4-34(b), in the case of "a" followed by "ㄲ", there is ambiguity. However, on the frequency of use table, this case is negligible. Considering only modern Korean input, pressing the flat consonant button 3 times is recognized as an absolute hard consonant (double consonant), so pressing the [a] button once more (i.e., pressing a total of 4 times) means "hard consonant + It is natural for modern Korean input to be "pyeong consonant" (eg "ㄲㄱ"). If the "a" button is pressed 5 times, it becomes "ㄲㄲ". The second "ㄲ" was input by pressing "ㄱ" twice, but since it is an initial consonant, it cannot be divided into "ㄱㄱ", so there is no need to process "ㄲ" with the third input of "ㄱ". However, for consistency of use, pressing one more time (ie, pressing "a" 6 times) may be treated as "ㄲㄲ". In any case, pressing one more time in "ㄲㄲ" means that the letter following the light consonant in Figure 4-34 (b) (eg "ㅱ", "ㅸ", "ㆁ", ..., etc. It can be used for the input of "the letter following the consonant"). For example, if pressing the flat consonant button three times is applied only to processing it as a light consonant sound, pressing the [ㅅ] button four times can be made into a light consonant sound "ㅸ". Refer to Fig. 4-34 (b). Pressing the [ㅇ] button 4 times can be changed to "ㆁ". If pressing the flat consonant button 4 times only applies to "light consonant + flat consonant", pressing the [ㅇ] button 5 times can be changed to "ㆁ" and pressing the [ㄴ] button 5 times to "ㅸ" have. If pressing the flat consonant button 5 times applies only to "hard consonant + hard consonant", you can enter "the letter following the double consonant" by pressing the flat consonant button 6 times, and presses the flat consonant button 6 times to "hard consonant + light consonant" If you apply to "light consonants", you can enter "the letter following the double consonants" by pressing 7 times. On the keyboard, since a light long consonant (double consonant) can be input as "Shift ^ flat consonant", pressing the flat consonant button 3 times can be processed as the input of the "letter following the double consonant". For example, pressing the [ㅇ] button three times is treated as "ㆁ".

", "

", ... "

", "

", ...) 역시 절대적인 것은 아니고 단지 예시일 뿐이므로, 적절하게 변형될 수 있음은 자명하다. 상기 내용을 종합하면, 키보드에서 "3+타 입력방법"을 적용시 평자음버튼 3번 눌러짐 또는 3번 이상 눌러짐에 의하여 "쌍자음다음글자"를 입력하도록 하는 것이다. The "letter following a double consonant" illustrated in Fig. 4-34 (b) is only an example, and is not absolute. As described above, since "ㅸ" can be entered as a combination of "ㅅ" and "ㅇ", it may be omitted from "letter following double consonants" in Fig. 4-34(b). Since it can also be entered as a soft heh "ㆆ = Shift ^ heh", it may also be omitted from "the letter following the double consonant". The order of "letter after double consonant" in Figure 4-34 (b) (eg "

", "

", ... "

", "

", ...) is also not absolute and is only an example, so it is obvious that it can be modified appropriately. Summarizing the above, when applying the "3 + other input method" on the keyboard, press the flat consonant button 3 times By loading or pressing three or more times, "the letter following the double consonant" is entered.

", "

", "

", "

", "

", "

", ... 와 같이 자음 다음에 "ㅡ" 또는 "ㅣ"가 연속 2번 나오는 모음을 [ㅡ]버튼 2번 누름 또는 [ㅣ]버튼 2번 누름으로 처리한다면, 상기 "쌍자음다음글자"의 입력을 위해서는 [ㅡ]버튼 3번 눌러짐 또는 [ㅣ]버튼 3번 눌러짐이 적용되어야 한다. 즉, "ㅇ" 다음에 "ㅡ"는 "으"로 되고 한번 "ㅡ"가 입력되면 "

"가 되고, 한번 더 "ㅡ"가 입력되면 여린ㅎ "ㆆ"이 되는 것이다. In the previous application of the applicant, the technology of inputting "y = xㅡㅡ" or "z = xㅣㅣ" was introduced. Grid consonants and hard consonants were input in the same way as above, but on a keyboard with more than 26 buttons, there is a separate grid sound button, and hard consonants are input as "Shift ^ flat consonants", so the above technique can be used to input other alphabets. can be applied to That is, it can be used for the input of the above-mentioned "letter following a double consonant". For example, it can be done with "ㅸ = ㄴㅡㅡ" in Sungyeongeumbieup, and "ㆆ = ㅇㅡㅡ" in a soft ha. but here "

", "

", "

", "

", "

", "

If you process a vowel in which "ㅡ" or "ㅣ" occurs twice consecutively after a consonant, such as ", ..., by pressing the [ㅡ] button twice or the [ㅣ] button twice, the "letter following the double consonant" For the input of, pressing the [ㅡ] button three times or pressing the [ㅣ] button three times must be applied.

", and if "ㅡ" is entered once more, it becomes a soft "ㆆ".

", "

", "

", "

", "

", "

", ... 앞에 오는 초성자음을 입력시 초성자음이라는 것을 명확히 하여(예. 길게 누름에 의하여 초성자음 입력)입력하는 방법을 제시한 바 있다. 본 발명에서 In another way, as mentioned in the earlier application, "

", "

", "

", "

", "

", "

When inputting the initial consonant that precedes ", ..., a method of inputting the initial consonant by clarifying that it is the initial consonant (eg, inputting the initial consonant by long pressing) has been proposed. In the present invention,

", "

", "

", "

", "

", "

", ... 등에 포함되어 있는 "

" 또는 "

" 입력시 "Shift^ㅡ" 또는 "Shift^ㅣ"를 이용할 수 있다. 이를 적용하면 "

", "

", "

", "

", "

", "

", ... 앞에 오는 초성자음 입력시 길게누름 등을 적용하지 않아도 된다. 이렇게하면, "y = xㅡㅡ" 또는 "z = xㅣㅣ" 로 원하는 모든 글자(예. "쌍자음다음글자")를 입력할 수 있게 된다. 2번째로 "y = xㅡㅡ" 또는 "z = xㅣㅣ" 에서 "ㅡㅡ" 및 "ㅣㅣ"를 각각 "Shift^ㅡ" 및 "Shift^ㅣ"를 이용하여 입력하는 것이다. 즉 "y = x+Shift^ㅡ" 또는 "z = x+Shift^ㅣ" 로 하는 것이다. 역시 모호성없이 "쌍자음다음글자"의 입력이 가능하다. 도면4-34(a)에서 이를 적용한 사례를 보이면, 반치음 "ㅿ = ㅅ+ Shift^ㅡ" 로, "

= ㅿ + Shift^ㅡ = ㅅ+ Shift^ㅡ + Shift^ㅡ" 로 할 수 있는 것이다. 상기에서 "Shift^ㅡ" 를 2번 누르는 것은 [Shift]버튼을 누르고 있는 상태에서 [ㅡ]버튼을 2번 누르는 동작도 동일한 것은 이미 설명한 바와 같다. 즉, "Shift^ㅡ + Shift^ㅡ"는 "Shift^ㅡ+ㅡ"로도 표현될 수 있다. A technique using "Shift^ㅡ" or "Shift^ㅣ" is additionally presented. It can be applied in two ways, the first is "

", "

", "

", "

", "

", "

contained in ", ..., etc."

" or "

" When inputting, "Shift^ㅡ" or "Shift^ㅣ" can be used. Applying this "

", "

", "

", "

", "

", "

You do not need to press and hold when entering the initial consonant before ", .... In this way, you can type all the letters you want with "y = xㅡㅡ" or "z = xㅣㅣ" (e.g. "the letter following the double consonant "). Second, in "y = xㅡㅡ" or "z = xㅣㅣ", "ㅡㅡ" and "ㅣㅣ" are replaced with "Shift^ㅡ" and "Shift^ㅣ" respectively. It is input using. That is, "y = x + Shift ^ ㅡ" or "z = x + Shift ^ I". It is also possible to input "the letter following the double consonant" without ambiguity. Figure 4-34 If you show an example of applying this in (a), with a half tone "ㅿ = ㅅ + Shift^ㅡ", "

= ㅿ + Shift^ㅡ = ㅅ+ Shift^ㅡ + Shift^ㅡ". Pressing "Shift^ㅡ" twice above means pressing the [ㅡ] button 2 times while holding down the [Shift] button. It has already been described that the operation of pressing once is the same, that is, "Shift^ㅡ + Shift^ㅡ" can also be expressed as "Shift^ㅡ+ㅡ".

Above, it was shown that pressing the [ㅡ] button twice is treated as "Shift^ㅡ" in a technique using two presses of the [ㅡ] button (eg, "y = xㅡㅡ"). Furthermore, since the keyboard has additional vowel buttons (e.g., [ㅑ] button, [ㅕ] button, [ㅛ] button, ...) other than the [ㅡ] button and the [ㅣ] button, "y = x+ A vowel button other than "ㅡ" or "ㅣ" may be applied to "Press the vowel button twice". It is preferable that a vowel in which the same vowel does not appear twice in a row is applied. Currently, the two-beol-type automata that inputs "ㅑ", "ㅕ", "ㅛ", and "ㅠ" corresponding to two presses of the vowels "아", "sh", "ㅗ", and "TT" is used in some have. In addition, there is a vowel in which "TT" appears twice and a vowel in which "ㅗ" appears twice in the input of Korean vowels. If you do not apply that another vowel is input by pressing the same vowel twice among "a", "sh", "ㅗ", and "TT", the vowels "a", "sh", "ㅗ", and "TT" It is also possible to use Even if another vowel is input by continuously pressing the same vowel among "a", "sh", "ㅗ", and "TT", the method presented in the case of using "ㅡ" and "ㅣ" is the same. can be applied

= ㅿ+ㅛㅛ = ㅅ+ㅛㅛㅛㅛ"로 할 수 있는 것이다. 마찬가지로 "ㅆ"을 "ㅅ+ㅑㅑ"로 하지 않고 "Shift^ㅅ" 또는 [ㅆ]버튼 한번 눌러짐으로만 한다면, "

= ㅅ+ㅑㅑ" 로 할 수 있는 것이다. 도면4-34(*)의 나머지 글자(예. "쌍자음다음글자")에 대해서도 같다. Among the vowels arranged on the double keyboard, "ㅑ" and "ㅕ" of the "ㅣ" series include Korean old vowels (see Unicode v6.0 in Figure 4-33(*)), and the same vowels are used twice in succession. doesn't come out In addition, "ㅛ" and "ㅠ" in the "ㅡ" series also do not appear twice in a row. Therefore, "y = xㅛㅛ", "z = xㅑㅑ", etc. can be used. It is possible to apply "ㅠ" instead of the above "ㅛㅛ", and it is also possible to apply "ㅕㅕ" instead of "ㅑㅑ". By using the combination of two consecutive pressings of the vowel button that does not appear twice in this way, as in the case of "ㅡ" and "ㅣ" above, all desired letters can be written without long pressing or using the [Shift] button. be able to input. For example, with the half-tone "ㅿ = ㅅ + ㅛㅛ", "

= ㅿ+ㅛㅛ = ㅅ+ㅛㅛㅛㅛ". Likewise, if you do not change "ㅆ" to "ㅅ+ㅑㅑ" and only press "Shift^ㅅ" or the [ㅆ] button once, "

= ㅅ + ㅑㅑ". The same is true for the remaining letters (eg, "the letter following the double consonant") in Figure 4-34 (*).

34. Korean syllable input method by continuous drag using regression drag on the screen keyboard

The present invention is a further development of the Korean language input technique (Chapter 27 of this specification) by the applicant's continuous drag. This is the first achievement in about six years since the introduction of the invention in Chapter 26 in 2008.

In Chapter 27, it was shown that the initial, neutral, and final consonants were input with continuous dragging. For example, input "go" by dragging as shown in Figs. 15-7 and 15-8, and input "gon" by dragging as shown in Fig. 15-9. The drag in Chapter 27 is called "sequential drag" or "sequential drag" for convenience.

In drawings 15-13, in a special case, the lattice sound (eg "ㅋ") and the pair consonant (eg "ㄲ") related to the flat consonant button (eg "a") are input by continuous dragging as the initial consonant. showed that it could However, in the process of inputting "de", the user can naturally drag "c → b → ... → ㅡ" to input "de", but when drawing 15-13 is applied, the system inputs "de" It may be treated incorrectly. In addition, in Chapter 27, there was a disadvantage in that consonants not displayed on the button (eg grid consonants, double consonants) could not be input with one drag as the final consonant by continuous dragging. Similarly, in FIGS. 15-14, 15-15, and 15-16, when two consonants are related to one button, a method for inputting the second related consonant by dragging is not presented. In the present invention, even if it is not displayed on the button or displayed on the button with one drag, even the second or more related consonants (eg "ㅋ", "ㄲ", ...) can be input without errors. present.

The following technology has been verified by being partially implemented through the applicant's text input device for Android, and will be released through http://www.simplecode.net and the Google Play Store (Android Market) at an appropriate time.

34.1 Summary of related concepts and terms

For convenience in describing the present invention, some key terms related to drag defined by the inventors and their concepts will be briefly summarized.

Figure 19-1 is a keyboard image of a product published on the official website http://www.simplecode.net and the Google Play Store (Android Market) of the applicant's product. In Fig. 19-1, "ㆍ" of the [0] button may be displayed as "A" or other forms (eg, the form shown in Fig. 15-*) as suggested in the previous application of the present invention, and in applying the present invention same.

As shown in Fig. 19-1, it is possible to drag to the left based on the [ㅁ] button (ie, the [5] button) and then return to the original position. Likewise, it is possible to drag to the right and then return to the original position, to drag to the top and then return, and to drag to the bottom and then return to the original position. In this way, a drag that proceeds with another button and returns to its original position will be called a "regressive drag" or more simply a "regressive drag". A drag that proceeds to the left and returns again is called a "leftward regression drag" for convenience, and the remaining cases are called "rightward regression drag", "upward regression drag", and "downward regression drag", respectively.

It can be seen that the leftward regression drag was dragged as [ㅁ → ㄹ → ㅁ], and the rightward regression drag was dragged as [ㅁ → ㄴ → ㅁ]. Since the leftward and rightward regression drags are drags that proceed in a horizontal direction and return again, they can be collectively referred to as "horizontal regression drags". Similarly, since the up-regression drag and the down-regression drag are drags that proceed in the vertical direction and then return again, both can be called "vertical recursion drags".

In addition, there may be a leftward regression drag as shown in Fig. 19-2. In Figure 19-3, it is a case of dragging to the left within one button and then returning to the original position. In this way, it is possible to identify a regression drag within the same button by detecting "bending" at a predetermined angle after progressing a predetermined distance or more, and then detecting that the predetermined distance has proceeded again. However, this method has a disadvantage in that it is difficult for the user to know whether the drag has been dragged by a critical distance that can be recognized as a drag, and there is a high possibility of error. On the other hand, as shown in Fig. 19-1, moving from the button where the drag started (eg the [ㅁ] button) to the adjacent button and then returning to the original button allows the user to change the drag trajectory to the adjacent button partitioned in a grid pattern. Since it can be checked with the naked eye, there is a good effect that the possibility of error by the user is greatly reduced.

As shown in Fig. 19-2, the regression drag performed within the same button is called "regression drag within the button" for convenience, and the regression drag that proceeds to the surrounding button and then returns to the original button as shown in Fig. 19-1 is referred to as "regression drag outside the button" for convenience. Let's call it "regression drag". In reality, the keyboard on the touch screen terminal is not very large and the buttons are also very small, and since the regression drag other than the button has better properties as described above, the regression drag will be described as a regression drag other than the button. It is also one of the important features of the present invention that it is based on the good properties of the non-button regression drag.

Fig. 19-3 shows an example of a regression drag in which the drag proceeds beyond an adjacent button and then returns to the button where the drag started. Looking at the trajectory of the rightward regression drag in Figure 19-3, it can be seen that it was dragged [ㅁ → ㄴ → Qwerty → ㄴ → ㅁ]. For convenience, as shown in Fig. 19-3, dragging beyond one more adjacent button and returning to the original button where the initial drag started is called "two-stage regression drag". Likewise, Fig. 19-1 can be called a "step 1 regression drag", and Fig. 19-2 can be called a "step 0 regression drag". That is, non-button regression drags are regression drags with more than one stage (eg, stage 1, stage 2, stage 3, ...).

Looking at the drag trajectory of Figure 19-4, it was dragged [ㅁ → ㄹ → ㅅ → ㅇ → ㅁ]. It was initially dragged to the left, and it did not return to the first button from the adjacent button [L] button, but returned to the first drag start button [ㅁ] button through another button. This can also be seen as a form of two-stage regression drag. Actually, I returned to the original button in 4 times ([ㅁ → ㄴ → Qwerty → ㅇ → ㅁ]) in drawing 19-3, but 4 times in drawing 19-4 ([ㅁ → ㄹ → ㅅ → ㅇ → ㅁ]) You can see that it returns to the original button after a while. Fig. 19-4 If the direction of the drag is attached, it can be called "two-stage leftward regression drag". Of course, since the drag pattern of the leftward regression drag in Fig. 19-3 and the leftward regression drag in Fig. 19-4 are different, different input targets may be identified.

Although not exemplified in the drawing, even if the first-stage regression drag occurs twice in succession, it can also be regarded as a kind of two-stage regression drag. For example, in the case where the button trajectory is [a → b → a → b → a], one-stage rightward regression drag occurred twice in succession. If the button trajectory of [a → b → a → d → a] is a case where there is one rightward regressive drag and one more consecutive downward regressive drag. This is also the case where the first stage regression drag occurred twice in succession. Since the 2-stage regression drag, in which the 1-stage regression drag occurs twice in succession, also has a different pattern from those in Figs. 19-3 and 19-4, other input objects can be identified.

Similarly, diagonal regression dragging can also be considered. Dragging that was dragged in the upper left direction (or upper left direction) and then returned was performed in the upper left regression drag (or upper left regression drag) or upper right direction (or upper right direction). A drag that returns again is an upward regression drag (or an upright regression drag), a drag that has been dragged in a left-down direction (or a downward-left direction) and a return drag is a downward-left regression drag (or a downward-leftward regression drag), a right-down direction (or a downward-left direction) A drag that is dragged in a direction) and then returns is called a downward-right regressive drag (or a downward-regressive drag), respectively. Referring to Fig. 19-5, for convenience, the four types of oblique regression drags in Fig. 19-5 are collectively referred to as "oblique regression drags".

Looking at the button trajectory of the downward-left recursion drag in Fig. 19-5, it can be seen that it was dragged [ㅁ → ㄹ → ㅅ → ㅇ → ㅁ]. Or [ㅁ → ㅇ → ㅅ → ㄹ → ㅁ] is also a downward-left regressive drag (exactly, a downward-left regressive drag). Drawing 19-4 was also dragged to [ㅁ → ㄹ → ㅅ → ㅇ → ㅁ]. That is, if only the button trajectory is compared, the drag of Fig. 19-4 can be viewed as a downward-left regressing drag. Therefore, the drag of FIG. 19-4 and the [ㅁ → ㄹ → ㅅ → ㅇ → ㅁ] drag of FIG. 19-5 can be applied by considering only the button trajectory as a drag of the same pattern. However, if the number of input objects (eg alphabets) to be expressed is large, the drag of Fig. 19-4 and the button trace [ㅁ → ㄹ → ㅅ → ㅇ → ㅁ] drag of Fig. 19-5 can be applied to different input targets can be used to express The method for distinguishing the downward-left regressive drag ([ㅁ → ㄹ → ㅅ → ㅇ → ㅁ]) of Fig. 19-5 and the two-stage left regressive drag of Fig. 19-4 detects the "bend" angle of the drag as well as the button trajectory It is possible by doing In Figure 19-4, three bends occur at an angle of about 90 degrees, whereas in Figure 19-5, it is sufficient to detect that one bend has occurred at an angle of about 180 degrees, and distinguish both drag patterns with the program It's not that difficult to do. In the end, the oblique regression drag in Figure 19-5 can be interpreted as a "one-stage oblique regression drag" by considering the "bending" angle, or it can be interpreted as a "two-stage regression drag" by judging only the button trajectory without considering the "bending" angle. can also be interpreted.

Regression drag in the diagonal direction can also be within-button regression drag (ie, 0-step regression drag) within a button, and two-step regression drag dragged beyond the range of adjacent buttons (top, bottom, left, right, and diagonally adjacent buttons). There may be. Marks on the drawings are omitted. Considering the small size of the keyboard and buttons in current smartphones, etc., the regression drag within the button (i.e., 0-step regression drag) is the same regardless of the direction (e.g., horizontal, vertical, diagonal, ...). It can be used to identify the input target (eg alphabet).

Above, the core concepts for applying the present invention have been summarized through the terms defined by the present inventors. Hereinafter, a specific keyboard is used to process the input target (eg "ㄲ", "ㅋ", number, function...) associated with a specific consonant button (eg [a] button) according to the concept described above. An example is presented as a reference. It is obvious that what has been described once in the following embodiment can be equally applied to other embodiments. Also, in the keypads of all embodiments below, it is considered that the buttons are densely arranged with no gaps between the buttons.

34.2 Example of inputting related consonants using regression drag (applicant's keyboard)

Based on Figure 19-1, the input rule suggested by the applicant is "ㅋ = ㅡㅡ", "ㄲ = ㄱㅣㅣ" or "ㄲ = ㄱㄱ", "ㅋ = ㄱㄱㄱ", etc. As a result, in Figure 19-1, it can be seen that "ㄲ" and "ㅋ" are associated with the [a] button in addition to "a" displayed on the button. Similarly, other flat consonant buttons (eg, [c] button) are associated with corresponding grid sounds (eg, "t") and double consonants (eg, "ㄸ"). Considering that the "a" displayed on the button is also related to the [a] button, "a" can be seen as the first related alphabet, and "ㄲ" and "ㅋ" are respectively subordinate (eg. It can be seen as an alphabet related to the third, ...).

In this embodiment, a case in which a lattice sound is input through a horizontal regression drag (ie, a leftward regression drag and a rightward regression drag) and a double consonant is input through a vertical regression drag (ie, an upward regression drag and a downward regression drag) is shown. . Of course, a consonant (eg "ㄲ") related to a specific button (eg, [a] button) is recognized with a single regression drag, and another continuous regression drag (eg, 1-stage regression drag is 2 consecutive). It is also possible to recognize other related consonants (eg "ㅋ") with a two-stage regression drag that occurs once. However, since it is easier to input the required object with one regression drag than to perform two regression drags in succession to recognize the consonants associated with a specific button, each input target for vertical regression drag and horizontal regression drag It is to present an example of this recognition.

Showing an embodiment in which horizontal regression drag is mainly used for lattice sound input and vertical regression drag is mainly used for double consonant input is the shape of Korean lattice sounds (eg "ㅋ", "ℓ", "P", " ㅋ") ideally corresponds to the horizontal direction, and the shape of double consonants (e.g. "ㄲ", "ㄸ", "ㅃ", "ㅆ", "ㅃ") is vertical because the flat consonants are side by side. Because it ideologically corresponds to the direction. However, it is not always necessary to use horizontal regression drag for lattice consonants, and it is not always necessary to use vertical regression drag for double consonants. Conversely, vertical regression drag may be applied to lattice input, and horizontal regression drag may be applied to consonant input. Also, among the horizontal regression drags, only one of the leftward regression drag or the rightward regression drag can be applied, and among the vertical regression drags, only one of the upward regression drag and the downward regression drag can be applied. Similarly, a specific button (e.g. [a] button) by the oblique regression drag in Fig. 19-5 (specifically, it means four patterns of dragging, and depending on interpretation, one-stage oblique regression drag or two-stage regression drag) It is possible to recognize consonants related to (eg "ㄲ", "ㅋ", ...). What is important is that consonants associated with a specific button are recognized by a non-button regression drag (ie, one-step or more than one-step regression drag).

According to the applicant's earlier application (Chapter 27), the result of dragging [a → b → a → d → ㅅ → ㅡ → ㆍ → ㅇ → ㅁ → ㅇ in Figure 19-6 is "heel". The [a] button, which is the button where the drag started, becomes a valid input, and the consonant buttons below it are invalidated, and the vowel buttons [ㅡ] and [ㆍ] are recognized as valid buttons, and similarly, the consonant button where the drag is finished [ㄴ] This is because the button is recognized as a valid button. However, in the embodiment of the present invention, if the lattice sound is recognized by horizontal regression drag, the input result is "Coop". If the user intended to enter "heel", there is no reason to start dragging from the [a] button, go through the [b] button on the right and return to the [a] button, and of course [a → ㄹ → ㅅ → ㅡ → . ..] because it would have been dragged. In other words, if the user wants to input only "a" as the initial consonant, start dragging from the [a] button and go back to the [a] button, and go through another button to enter the vowel button (e.g., [ㅡ] button). that it would have been dragged to . However, the return to the button that started the drag allows the user to clearly identify without any errors that the user inputs the promised alphabet (eg "ㅋ") to the regression drag (eg horizontal regression drag). In Fig. 19-6, it is shown that the lattice sound is input by rightward regression drag, but if all horizontal regression drags are recognized as lattice sounds, [a → Mode → a → ㄹ → ㅅ → ㅡ → ㆍ ㆍ → ㅇ → ㅁ → ㅅ] can also be made to recognize "coop".

Detecting the right-handed drag in Fig. 19-6 is very simple. The consonant button that started dragging is recognized as valid, but the [a] button that started dragging reappears (the third dragged " It is possible to detect a"). Since the second dragged button is located to the right of the [a] button, which is the button where the drag was started with the [b] button, it is easy to detect that a rightward regression drag was performed only with the button trajectory. If dragged as "a → Mode → a → ㄹ → ㅅ → ...", the second dragged [Mode] button is located to the left of the [a] button, so a leftward regressive drag can be detected.

Next, it shows recognizing double consonants by vertical regression drag. The drag of Fig. 19-7 is also recognized as a "heel" according to the applicant's previous application (Chapter 27). However, if double consonants are recognized by vertical regression drag (downward regression drag in Fig. 19-7), the result is "Kub". To detect upward dragging by the button trajectory, it is easily possible by setting a fake button with a small invisible height in the area above the [a] button. This is because, in general, keyboard programs do not recognize areas outside the keyboard. Figure 19-8 shows an example of setting a small height fake button (actually, it is desirable to make it almost invisible) at the top of the keyboard. Figure 19-9 shows an example of inputting consonants as initial consonants by upward recursion drag based on Figure 19-8. If the top five fake buttons in Figure 19-9 are DB1, DB2, DB3, DB4, and DB5, respectively, for convenience, in Figure 19-9, they were dragged to "a → DB2 (a up button) → a → ...", and the result "Kup" is recognized.

If "ㅆ" is entered as the initial consonant, if a downward drag is applied as in [ㅅ → ㅡ → ...], "s" is recognized as input. However, if an upward recursion drag is applied like [ㅅ → ㄹ → ㅅ → ㅡ → ...], "th" can be recognized without any problem. In the case of "ㅅ", there is no lattice sound, so horizontal regression drags (ie, leftward and rightward regression drags) can also be treated as "ㅆ".

Next, it is a case where "ㅎ" is related to the [ㅇ] button. Since there is no lattice sound corresponding to "ㅇ" in modern Korean, both vertical and horizontal regression drags can be treated as "ㅎ". If dragged downward like [ㅇ → ㆍ → ㅇ], it is recognized as "ang" (refer to Chapter 27 of the previous application). Therefore, upward regression drag [ㅇ → ㅁ → ㅇ → ...], leftward regression drag [ㅇ → ㅅ → ㅇ → ...], rightward regression drag [ㅇ → ㅅ → ㅇ → ...] can be processed as "ㅎ" input. Drawings of input cases are omitted.

In the previous application of the applicant, "ㅎ" was also associated with the [ㆍ] button. According to the previous application, when dragging [ㆍ → ㅇ → ㆍ → ㅣ], the [ㆍ] button from which the drag started is valid, the [ㅇ] button that cannot be combined with it is invalid, and the remaining combineable vowel buttons [ㆍ] Since the button and the [ㅣ] button are valid, the result is recognized as "ㅕ". One consonant letter can be input by dragging, but in some cases, it is preferable to input by combining normal pressing and dragging. Also, in some cases, the initial consonant may be input by tapping, and only the neutral vowel (eg "ㅕ") may be input by dragging. Therefore, in the embodiment of the present invention, as in the case of "ㅕ", one-step drag started from the vowel button (in the case of [ㆍ → ㅇ → ㆍ → ...], one-step upward drag started from the [ㆍ] button) Assume that vowels are recognized. If so, "ㅎ" associated with the [•] button can be input by upward dragging in 2 steps or more (3 steps, 4 steps, ...). For example, [ㆍ → ㅇ → ㅁ → ㅇ → ㆍ] 2-step upward drag can be handled as "ㅎ". Reference can be made to the input of the initial consonant "ㅎ" in the input case of "Hi + ㅎ (final)" in Figures 19-13.

It has been described that the first-stage regression drag started from the vowel button is processed as a vowel input, and the second-stage regression drag is processed as an input of a promised consonant (eg "ㅎ"), but the opposite can be defined. That is, it is also possible to process a first-stage regression drag started from the vowel button as an input of a promised consonant (eg "ㅎ"), and process a second-stage regression drag as a vowel input. This is because the user usually starts dragging from the consonant button and ends dragging from the vowel button (i.e., inputs a letter consisting of "initial consonant + neutral vowel"), or starts dragging from the consonant button, passes through the vowel button, and ends dragging from the consonant button. (That is, a letter consisting of "initial consonant + neutral vowel + final consonant") in most cases, and there will be few cases where dragging starts from the vowel button. In any case (one-stage regression drag or two-stage regression drag), it is the same that the regression drag that starts from the vowel button and returns to the vowel button can be treated as the promised consonant (eg "ㅎ"), This is also an embodiment presented for the first time in the present invention.

Above, we showed the case of inputting the second or more related alphabet for the initial consonant by regression drag. Next, an example in which even the final consonant can be entered is shown.

In the previous application (Chapter 27) of the applicant, only the last dragged consonant button was treated as valid. This means that only the nine consonants (a, b, c, d, ㅁ, f, ㅅ, ㅇ, ㄴ) displayed on the button in Figure 19-1 can be input as final consonants by one continuous drag. According to the earlier application, Figures 19-10 are recognized as "heels". In the present invention, it is the same that the last dragged consonant button is treated as a valid button. When the present invention is applied, it is recognized as "?m". It was dragged from drawing 19-10 to [a → b → a → d → ㅅ → ㅡ → ㆍ → ㅇ → ㅁ → ㄴ → ㅁ → ㄴ ]. The button trajectory after the [ㆍ] button, which is the last dragged vowel button, is the same as [... → ㅇ → ㅁ → ㅇ → ㅁ → ㄴ]. If the user intended to enter only "ㅅ" as the final consonant, the drag should have ended with [... → ㅇ → ㅁ → ㄴ] without the need to drag [... → ㅇ → ㅁ → ㄴ] .

Detecting leftward drag in the final consonant input can be done very simply by analyzing the button trajectory in reverse order from the last dragged [ㄴ] button. In [... → ㄴ → ㅁ → ㄴ], the [ㅁ] button was dragged in front of the [ㄴ] button in front of the last dragged button, and the [ㅁ] button located to the left of the [ㄴ] button was dragged in between. The application of the left drag (a form of horizontal drag) of the [ ] button to the final input can be detected very easily and without user error (e.g., user error in the 0-step regression drag). The initial consonant detects the regression drag based on the consonant button where the drag started, but the final consonant detects the regression drag based on the consonant button where the drag ends.

According to the earlier application (Chapter 27), drawings 19-11 are recognized as "corner". However, since the button trajectory is [a → ㄹ → ㅅ → ㅇ → ㆍ → ㅇ → ㅁ → ㄹ → a → ㄹ → ㄱ], if the present invention is applied, the final drag that is considered valid after the [ㆍ] button, which is a valid vowel button Since there is "a → d" in front of the [a] button, which is a consonant button, it detects that a downward regression drag (the [d] button is placed under the [a] button) is applied to the final input, and the result is "cut".

In [ㅇ → ㆍ → ㅣ → ㅅ → ㅇ → ㅅ → ㄹ → ㅅ] in Figures 19-12, "uh" is recognized according to the previous application. However, when the present invention is applied, "was" is recognized. This is because it can detect that the upward regressive drag of [...→ ㅅ → ㄹ → ㅅ] is applied to the final input. If the original intention was for the user to enter "uh", the drag should have ended at [ㅇ → ㆍ → ㅣ → ㅇ → ㅇ → ㅅ] without the need to drag back to [...→ ㅅ → ㄹ → ㅅ]. because it does In the case of "ㅅ", there is no corresponding lattice sound, so horizontal regression drags (ie, leftward regression drags and rightward regression drags) can also be treated as "ㅆ". That is, instead of [...→ ㅅ → ㄹ → ㅅ] of Figures 19-12, [...→ ㅅ → Space → ㅅ] of leftward regression drag and [...→ ㅅ → ㅇ → ㅅ] of rightward regression Drag can also be processed with the final consonant "ㅆ". The example of the final consonant "ㅆ" is given, but the same applies to the input of "ㅎ" related to the [ㅇ] button (i.e., upward regressive drag, leftward regressive drag, and rightward regressive drag for the [ㅇ] button are "ㅎ" ") is possible, and case drawings are omitted.

In the embodiment of the present invention, a one-stage drag initiated from the vowel button is recognized as a vowel input, and two or more stages of drag are processed as a promised alphabet (eg, "ㅎ"). The button trajectory in Fig. 19-13 is [ㆍ → ㅇ → ㅁ → ㅇ → ㆍ → ㅇ → ㄴ → ㅣ → ㆍ → ㅇ → ㅁ → ㅇ → ㆍ]. It can be seen that dragging started from the [ㆍ] button, which is a vowel button, and dragged up two steps ([ㆍ → ㅇ → ㅁ → ㅇ → ㆍ → ...]), so the promised consonant "ㅎ" is recognized as the initial consonant. . The next dragged consonant button [...→ ㅇ → ㅅ → ...] is invalid because it cannot be combined with "ㅎ". Since the drag ends at the vowel button, if the previous application (Chapter 27) is applied, the valid button [ㅣ → ㆍ → ... → ㆍ] is recognized as the vowel "ㅑ". However, according to the present invention, if a two-step upward recursion drag is detected and applied, including the last dragged button [ㆍ] following the valid vowel button [ㅣ], the result is “Hi + ㅎ (final tone)”. If it is dragged like [ㆍ → ㅇ → ㅁ → ㅇ → ㆍ → ㅇ → ㄴ → ㅣ → ㆍ ㅇ → ㆍ → ㅇ → ㅁ → ㅇ → ㆍ], it becomes "?K".

For better understanding, the case of inputting the initial consonant "ㅎ" as a consonant related to the [ㅇ] button by horizontal regression drag, and inputting the final consonant "ㅎ" as a consonant related to the [ㆍ] ㄴ button by two-stage vertical regression drag When shown, it is shown in drawing 19-14. If the previous application is applied, "Ya" (the first vowel button is regarded as a valid vowel button and the remaining combinable vowel buttons are treated as valid buttons) or "Ya" (all dragged vowel buttons are treated as valid buttons). When the present invention is applied, since the [ㅇ] button is dragged in a leftward rotation, the initial consonant "ㅎ" is recognized, the vowel "a" is recognized, and the final consonant "ㅎ" is dragged upward two steps from the [ㆍ] button, which is the last dragged button. " is recognized and the result is "?K". The description of the button trajectory is omitted. In this embodiment, the 2-step upward drag from the [ㆍ] button was processed as “ㅎ” input, but in the case of the initial consonant, the 1-step upward drag was treated as the final consonant “ㅎ” as in the description, and the 2 However, it is also possible to process the upward recursion drag as a vowel input.

34.3 Example of inputting related consonants using regression drag (Samsung Electronics keyboard)

Figures 15-16 and 19-15 are 12-button Hangul keyboards from Samsung Electronics, which are currently widely used. In Figures 19-15, "ㅋ" is arranged second in the [a] button, so it can be seen that "ㅋ" is a consonant related to the [a] button. It is easy to see that "ㄹ" is related to the [ㄴ] button because "ㄹ" arranged secondly on the [ㄴ] button is also input by pressing the [ㄴ] button twice. This is the same for the [ㅅ] button and the [ㅇ] button. The consonants are not arranged, but since "ㄲ" is input by pressing the [a] button three times, it can be seen that "ㄲ" is related to the [a] button. The same is true for the rest of the consonants.

In the previous application (Chapter 27) of the applicant, it was not possible to input the second related consonant with one continuous drag. In the embodiment of the present invention, an embodiment in which the second arranged consonant is input by horizontal regression drag and a pair of consonants is input by vertical regression drag is shown.

In the drawings 15-16 of the previous application, it was shown that "phase" was input with one continuous drag. When dragged as shown in Figs. 19-16, "above" is recognized according to the previous application, but becomes "a" when the present invention is applied. Looking at the button trajectory, it is [ㅅ → ㅅ → ㅅ → ㄴ → ㄱ → ㅣ → ㆍ → ㄴ → ㅅ → ㅇ → period → ㅇ]. "ㅎ" is recognized in the rightward regression drag of [ㅅ → ㄴ → ㅅ → ...], "a" is recognized in [...→ ㅣ → ㆍ → ...], and [...→ ㅇ → Period → ㅇ] "ㅁ" is recognized in the leftward regression drag.

Figures 19-17 are recognized as "liver" according to the prior application. According to an embodiment of the present invention, it can be recognized as "cal". The initial consonant "ㄲ" was recognized by the downward regressive drag, and the final consonant "ㄹ" was recognized by the rightward regressive drag.

According to the earlier application, Figures 19-18 are recognized as "liver", but according to an embodiment of the present invention, the result of Figures 19-18 is "knife". In Figures 19-18, if the second associated consonant is recognized by horizontal regression drag, "ㅋ" is recognized by leftward regression drag. In addition, since "ㄴ" does not have a corresponding double consonant, the vertical regression drag (eg, downward regression drag) in Figs.

In Figures 19-18, an important property is to be pointed out. If "Gak" is input and then dragged as shown in Figs. 19-18, the leftward regression drag started from the [a] button is interpreted as "ㅋ" but the [a] button is treated as being pressed twice, "each " Next, it will be recognized as "Kakal", not "Kakkal", which is a "knife". The reason why the [a] button is pressed three times is that it becomes “ㄲ” on the keyboard in Figs. 19-18. However, if dragged from the consonant button ends at the vowel button (i.e., a letter consisting of "consonant + vowel"), or dragged from the consonant button via the vowel button and ends at the consonant button (i.e., "consonant + vowel + consonant") ) can process the input from the drag start button to be one consonant letter. Then the result will be "angular knife". When inputting only by pressing (Tap) on the keyboard of Figures 19-18, there is ambiguity of "Gakkal ↔ Gakkal" for the same button value, but without ambiguity through the present invention in which one consonant letter is input with one drag It shows important properties that can be entered. If the user wants to input "Gakkal", enter "Ga" (any drag or press method is possible), and then drag as shown in Figs. 19-17, and the result will be "Gakkal".

In summary, the drag input of the present invention can be used interchangeably with the tap method, but is related to the consonant (eg "a") consecutively after the consonant (eg "a") that came out as the final consonant before. Even when consonants (eg "ㅋ", "ㄲ") appear as initial consonants, they show an important property that can be processed without ambiguity, unlike the case of using only the pressing method, which is also one of the important features of the present invention. This is possible by considering the "consonant + vowel" or "consonant + vowel + consonant" recognized by dragging as a unit, and the dragged syllable regardless of the final consonant (eg "a") of the previous letter is "initial + neutral" " or "initial consonant + neutral + final consonant".

34.4 Example of inputting related consonants using regression drag (LG Electronics keyboard)

Figures 15-14, Figures 15-15 and 19-19 are LG Electronics' 12-button Korean keyboard. In drawings 19-19, enter "ㅋ = ㄱ + add stroke", "ㄲ = ㄱ + double consonant", and "ㄴ = ㄴ + add stroke", "ℓ = ㄴ + add stroke + add stroke", "ㄸ = Enter as "b + stroke addition + double consonants". Since it is a popular keyboard, a detailed description of the input rules using the keyboard is omitted.

19-19, it can be seen that "a" is associated with the [a] button first, and "ㅋ" and "ㄲ" are associated with the second or more. Since "ㅋ = ㄱ + Add stroke" is entered, the [ㄱ] button becomes the main button of "ㅋ", and the function button [Add stroke] is used as an auxiliary button. In addition, since "ㄲ = ㄱ + double consonant" is input, the [a] button becomes the main button of "ㄲ", and it can be seen that the function button [twin consonant] is used as an auxiliary button.

In the same logic, "b" is associated with the [b] button first, and "c", "t", and "ㄸ" are associated with the second or more. Similarly, the [ㅁ] button is associated with "ㅅ", "P", and "ㅃ", the [ㅅ] button is associated with "ㅅ", "C", and "ㅔ", and the [ㅇ] button is associated with "ㅎ" "It is related. Three consonants are associated with the [ㄴ] button, [ㅁ] button, and [ㅅ] button, respectively. It is desirable to recognize ", because the flat consonants "c", "b", and "j" are used much more frequently than lattice consonants and double consonants. In the embodiment of the present invention, it is shown that "c", "ㅅ", and "ㅅ" associated with the [b] button, the [ㅁ] button, and the [ㅅ] button are recognized by the leftward regressive drag. This is because the rightward regression drag is "consonant + vowel + consonant" and other letters are recognized, so the leftward regression drag must be used in the keypad (keyboard) of Figures 19-19. In addition, for consistency with other embodiments, it is assumed that "twin consonants" are recognized by vertical regression drags (ie, upward regression drags and downward regression drags).

If the earlier application (Chapter 27) is applied, drawings 19-20 are recognized as "names". In the embodiment of the present invention, if "ㅅ" is recognized by the one-stage leftward regression drag and "ㅎ" is recognized by the leftward regression drag based on the [ㅇ] button, which is the button where the drag is ended, the result is "??" becomes A detailed description of the button trajectory is omitted. In Figures 19-20, an example of leftward regression drag to input the final consonant "ㅎ" was shown, but since only "ㅇ" and "ㅎ" are associated with the [ㅇ] button, leftward regression drag (eg [...→ ㅇ → ㅅ → ㅇ]), but upward recursion drags (ex. [...→ ㅇ → ㅁ → ㅅ]) can also be handled with "ㅎ".

The lattice sounds "t", "p", and "ch" associated with the [b] button, the [ㅁ] button, and the [ㅅ] button, respectively, can be recognized by a two-stage horizontal regression drag. According to the earlier application, the result of Figures 19-21 is recognized as "South", but according to the embodiment of the present invention, it is recognized as "Top". In Figures 19-21, two-step leftward regressions started from the [b] button show an example in which "T" is recognized.

It shows that "ㅅ" is recognized by dragging started from the [ㅅ] button. The [ㅅ] button is in a position where it is difficult to use the 2-stage horizontal regression drag in a straight line. First, it is possible to use the "add stroke" button as shown in Figs. 19-22. From the [ㅅ] button, which is the drag start button, "ㅅ" is recognized because it was dragged as follows: [ㅅ → Add stroke → ㅅ (invalidation) → Add stroke → ...]. This is a part already described in the previous application (eg, Figures 15-14). The results of Figures 19-22 are recognized as "True". In the case of the "top", it is also possible to use the [Add stroke] button as shown in Figs. 19-22.

Another method is to use the two-stage regression drag in Fig. 19-4. In Figure 19-23, it was dragged to [ㅅ → Space → Hangul → ㄹ → ㅅ → ...], and it can be seen that a two-stage leftward regression drag was performed as shown in Figure 19-4. If you look at the node where "ㅅ" appears again from the drag start button [ㅅ] button in the button trajectory, it is not [ㅅ → X → ㅅ → ...], but [ㅅ → X → Y → Z → ㅅ → ...] Since it is the same as , it can be recognized as a two-stage regression drag. Of course, as already described, an upward-left homing drag in an oblique direction can also have the same button trajectory, but in this embodiment, the button trajectory is treated as a leftward homing-drag. Therefore, the result of Figs. 19-23 is recognized as "True".

An example of another modified form of two-stage regression drag is shown in Fig. 19-24. In Fig. 19-24, it was dragged as [ㅅ → space → ㅅ → space → ㅅ → ...], and two consecutive 1-stage regression drags can be regarded as 2-stage regression drags and recognized as "ㅅ". The result of Figures 19-24 also becomes "True". Of course, it is also possible to apply the single-stage regression drag twice consecutively to the input of “t” of “top” in Fig. 19-22 in the same way as the input of “ch” in Fig. 19-24.

An example of inputting "ㅅ" with a horizontal regression drag and recognizing "ㅅ" in combination with the [Add stroke] button is shown in Fig. 19-25. The button trajectory of drawings 19-25 was dragged to [ㅅ → ㅇ → ㅅ → Add stroke → ...], "ㅅ" was recognized in [ㅅ → ㅇ → ㅅ → ...] and the [Add stroke] button continued As "ch" can be recognized. The result of Figs. 19-25 also becomes "True". Although the use of the [Add stroke] button in Figures 19-25 was shown in earlier applications, the present invention showed that related consonants can be input by regression drag without using the Add stroke button. will be.

Next, an example of inputting double consonants by vertical regression drag is shown. In Figures 19-26, it can be seen that upward dragging started from the [ㅅ] button. The results in Figures 19-26 are "pairs". Since there is an [Add stroke] button under the [ㅅ] button, downward regression drag was not applied. Likewise, since the button trajectory in Fig. 19-27 starts from the [b] button and is dragged down [b → ㅁ → b → ...], the consonant "ㄸ" associated with "b" is recognized. As a result of Figs. 19-27, "sweat" is recognized. The same is true for the remaining twin consonants "ㄲ", "ㅃ", and "ㅃ", so the example drawings are omitted.

19-27 is processed as if the consonant of "b" is "ㄸ". In order to clarify the logic, “c” can be recognized by horizontal regression drag in the [b] button, and “ㄸ” can be recognized by continuous vertical regression drag without interruption. For example, if the button trajectory is [b → a → b → m → b → ...], starting from the [b] button, one rightward regressive drag occurred, followed by one downward regressive drag. Able to know. That is, "c" is recognized by rightward regression drag (horizontal regression drag), and "ㄸ" is recognized by successive downward regression drag (vertical regression drag). The same can be applied to "ㅃ" and "ㅃ" related to the [ㅁ] button and the [ㅅ] button.

The [Twin Consonant] function button for inputting double consonants on LG Electronics' keyboard is located in the lower left corner at the [#] position, and there is a [ㅣ] button on the top of the [ㅡ] button on the left, dragging the [Twin Consonant] button To do this, you must go through the [ㅡ] button and the [ㅣ] button. However, in the drag input through the present invention, consonants including lattice sounds and double consonants can be input as initial consonants and final consonants with one uninterrupted drag without dragging with the [twin consonant] button. one of the achievements

34.5 Example of inputting related consonants using regression drag (Pantech keyboard)

Drawings 19-28 are Pantech's 12-button Korean keyboard. Since the input rule according to Figs. 19-28 is widely known, it is not described in detail in this embodiment. It can be seen that "ㅋ" and "ㄲ" are related to the [a] button, including "a". This is the same for the [c] button, the [b] button, and the [j] button, respectively. In addition, it can be seen that the [ㄴ] button, the [ㅁ] button, and the [ㅇ] button are associated with "ㄹ", "ㅅ", and "ㅎ", respectively, including the corresponding consonants. The number of related alphabets does not exceed a maximum of three, and the second or more related alphabets are a maximum of two. Similarly, examples of recognizing lattice consonants or second-arranged consonants by horizontal regression dragging and recognizing double consonants by vertical regression dragging are shown.

The button trajectory in Figures 19-29 is [a → c → a → ㅣ → a → backspace →a → sh → b → f → mchi → f]. A downward regressive drag can be detected in [a → c → a → ...] starting from the [a] button, and as a result, "ㄲ" can be recognized. The button trajectory from the vowel button to the vowel button is [...→ ㅣ → A → Backspace → A → ㅇ → ...]. The keypads in Figures 19-29 must be dragged through the [ㅣ] button or the [q] button to input the vowel "a". In the previous application, as a method of recognizing vowels, the initially dragged vowel button is treated as valid, and the vowel buttons that can be combined, including the initially dragged vowel button, are treated as valid buttons (see drawings 15-17). As another alternative, processing all dragged vowel buttons as valid vowel buttons has been suggested in the previous application.

This is because all vowel buttons are adjacent to the consonant button area, such as the applicant's keyboard (eg drawing 19-6), Samsung Electronics' keyboard (eg drawing 19-15), and LG Electronics' keyboard (eg drawing 19-19). There is no problem if they are arranged. However, if there is a vowel button (eg [A] button) that is not adjacent to a consonant button, such as the Korean QWERTY keyboard or the Pantech keyboard in Fig. 29-28, the vowel (eg vowel "a") and the vowel There is a disadvantage of not being able to input related vowels. The [A] button in Figs. 19-28 is adjacent to the consonant button [b] at a diagonal vertex, but is considered not adjacent to it in this embodiment. This is because the buttons are densely packed, so they cannot be dragged to the [A] button without passing through the [B] button and the [ㅣ] button or the [q] button. Even if there is a slight gap between the buttons, it is impossible to drag from the [b] button to the [ㅣ] button or the [q] button without passing through the gap to the [A] button.

Therefore, through this embodiment, an example of processing a vowel button that is not adjacent to a consonant button in this way is shown. The button trajectory from the vowel button to the vowel button in Figs. 19-29 is [...→ ㅣ → A → Backspace → A → ー → ...]. "ㅣ+A" does not exist in the input rule in Figures 19-29. In addition, it can be seen that "A" is not followed by another vowel, but "Backspace" and "A" again are for entering "ㅑ", which is obviously "A + A". If "ㅣ" is dragged after "ㅑ", "ㅒ" will be recognized. However, "o" dragged after "ㅑ" does not form an appropriate vowel according to the input rule of FIGS. 19-29. Therefore, it can be seen that "o" dragged to the end just passes to input the final consonant. This can also be seen from the fact that the button where the drag ends is a consonant button (eg, the [ ] button). The button trajectory after the last vowel button is [...→ ㄴ → ㄴ → ㅁ → ㄴ]. The final dragged consonant "ㅅ" is always considered valid, but it is recognized as the final consonant "P" because it can be detected that it is dragged leftward with [ㅅ → ㅁ → ㄴ]. Eventually, the result of Figs. 19-29 becomes "??".

The consonant input is almost similar to the embodiment shown in the keyboard of Samsung Electronics Co., Ltd. in 23.3, so detailed description is omitted. In this embodiment, inputting vowels by continuous dragging on a keyboard having vowel buttons that are not adjacent to consonant buttons is summarized as follows.

Description will be made based on drawings 19-28. First of all, "a" can be input by dragging [a → ㅣ → ahn]. As described above, the previously dragged [ㅣ] button is regarded as an invalid button because "ㅣ+A" is not defined as another vowel input. This is because if the user had intended to input "ki", the drag would have ended at the [ㅣ] button. Similarly, when dragged as [a → ... → sh → a], it can be recognized as "a". This is because if the user had intended to input “something”, the drag would have ended at the [sh] button. Next, "gyah" can be done with "a → ㅣ → a → backspace → a] as shown in drawing 28-9. Since the third dragged [a] button is the user's intended button, prior to [a] This is because the [ㅣ] button that cannot be combined is invalidated and the last [A] button is a valid button.The consonant button and the remaining vowel buttons adjacent to the consonant button can be processed as described in the applicant's previous application, so the description is omitted.

Next, we will show you how to solve it by placing a fake button at the top of the keypad (keyboard). In drawing 19-30, fake buttons are placed in line with the 5th row at the top. For convenience, we will call the five fake buttons DB1, DB2, DB3, DB4, and DB5. In the embodiment of the present invention, it does not matter if one DB fake button is placed at the top, but in order to identify the two-stage regression drag in Fig. 19-4 and the oblique regression drag in Fig. 19-5, Placing fake buttons in numbers is more flexible.

The button trajectory in Fig. 19-30 is [a → DB2 → a → DB3 → DB4 → a → lor → b → c → a → c → a]. "ㄲ" is recognized because upward dragging was performed in [a → DB2 → a → ...] from the [a] button, which is the drag start button. The button trajectory from the vowel button to the vowel button is [...→ a → sh → ...]. Since it was dragged to the [A] button through the fake buttons (DB3, DB4), it is reasonable to treat the [A] button as a valid button in this case. If the user was to input "sh", the [sh] button is adjacent to the consonant button, so drag as [a → DB2 → a → c → b → sh → ...] because it would have Since “a+sh” is not defined in the input rule of FIGS. 19-30, the vowel button [q] is invalid. In the button trajectory after the last vowel button [...→ b → c → a → c → a], the [a] button, which is the consonant button finally dragged, is a valid button and downward recursion dragged in front of it, so the consonant "ㄲ" this is recognized As a result, the result of Figs. 19-30 is recognized as "sharp".

As a result of FIGS. 19-30, the user must think in his or her brain whether the input vowel is "A" or "Q" while the user is familiar with the detailed drag input rule. Figures 19-31 make it easier to enter "cut". The button trajectory in Fig. 19-31 is [a → DB2 → a → DB3 → DB4 → a → DB4 → DB3 → DB2 → a → c → a]. Since the dragged vowel button is only the [A] button, the user does not have to think about whether the input vowel is "A" or "sh" when dragged to [...→ DB4 → A → sh →...]. Recognizing the initial consonant "ㄲ" and the final consonant "ㄲ" is as described in Figs. 19-30.

34.6 Example of inputting related alphabets using regression drag (QWERTY Korean keyboard)

Figure 18-1 (*) is a double keyboard that is currently used as a standard in PCs, etc., and is commonly referred to as a QWERTY Korean keyboard. It consists of 14 consonant buttons and 12 vowel buttons. The consonants "ㄲ", "ㄸ", "ㅃ", "ㅆ", and "ㅃ" correspond to the [a] button, [c] button, [ㅅ] button, [ㅅ] button, and [ㅅ] button, respectively. It is related. This can be easily seen from inputting "ㄲ = shift + a". When inputting consonants by continuous dragging, it is possible to process using the above-described vertical regression drag or horizontal regression drag.

For example, "??" can be recognized by dragging as shown in Fig. 19-32. Since the consonants associated with the [a] button are only "ㄲ" except for "a", the fact that "ㄲ" can be recognized by vertical regression drag or horizontal regression drag is as described in other embodiments.

The QWERTY Korean keyboard has a vowel button located on a side that is not adjacent to the consonant button. In this way, vowel input by continuous dragging on a keyboard with a vowel button that is not adjacent to a consonant button is separately organized in Chapter 35.

34.7 Summary of input examples of related consonants using regression drag

In the present invention, an embodiment in which even consonants (eg "ㄲ", "ㅋ", ...) associated with a consonant button (eg [a] button) are input as initial consonants and final consonants using regression drag seemed In summary, the initially dragged consonant button is regarded as a valid consonant button, and among the consonant buttons dragged before the vowel button, a regression drag is detected and treated as a promised consonant (eg "ㅋ"). Similarly, the consonant button dragged out (i.e., the consonant button dragged last) is considered a valid consonant button, and among the consonant buttons dragged after the last dragged vowel button, the last dragged consonant button (eg "a") It is to detect regression drag by comparing it with and process it as a promised consonant (eg "ㄲ").

As already described, each regression drag represented in FIGS. 19-1 to 19-5 can be defined so that each individual input object is recognized. In the embodiment of the present invention, consonants (eg, "ㄲ", "ㅋ") associated with a specific consonant button (eg, [a] button) through a non-button regression drag (ie, one-step or more than one-step regression drag) Recognized examples were shown. More specifically, a case of recognizing the second associated or arranged consonant or grid sound by horizontal regression drag was shown, and a case of recognizing twin consonants by vertical regression drag was shown.

It is described in steps as follows. The following cases are cases in which dragging starts from the consonant button and ends with the vowel button, or dragging starts with the consonant button and ends with the consonant button.

On a keyboard equipped with a plurality of consonant buttons and a plurality of vowel buttons on a screen (liquid crystal) densely in a lattice form, Korean letters (consonants , vowel, consonant letter, word or phrase) in the method of inputting,

A plurality of consonants are associated with one or more consonant buttons among the consonant buttons,

(a) detecting the start of the drag operation and recognizing the button trajectory including the consonant button (drag start button) where the drag started

(b) Button trajectory from the drag start button to the front of the vowel button

or

If there is no vowel button among the dragged buttons, the button trajectory from the drag start button to the drag end button

Detecting a regression drag including the drag start button in

(c) Recognizing consonants promised for the regression drag among the consonants related to the consonant button from which the dragging started.

Korean character input method by continuous dragging on a screen (liquid crystal) keyboard, characterized in that characters are input with

The above is the case where the drag ends at the vowel button [ㆍ] among the drag button trajectories [a → b → a → d → ㅅ → ㅡ → ㆍ → ㅇ → ㅁ → ㅇ → ㅁ → ㅁ] in Fig. 19-10 (i.e., You can refer to [a → b → a → d → ㅅ → ㅡ → ㆍ]). It has been explained that regression drag can be detected in the button trajectory [a → b → a → ...].

The following is a case where dragging starts from the consonant button, passes through the vowel button, and ends at the consonant button.

On a keyboard equipped with a plurality of consonant buttons and a plurality of vowel buttons on a screen (liquid crystal) densely in a lattice form, Korean letters (consonants , vowel, consonant letter, word or phrase) in the method of inputting,

A plurality of consonants are associated with one or more consonant buttons among the consonant buttons,

The drag starts from the consonant button and ends with the consonant button including the vowel button,

(a) detecting the start of the drag operation, recognizing the consonant button (drag start button) where the drag has started as a valid button, and recognizing the promised initial consonant from the buttons up to the first vowel button in the dragged button trajectory

(b) Recognizing vowels promised as neutral vowels in the button trajectory from the first vowel button to the final vowel button in the drag button trajectory.

(c) Detecting the regression drag of the consonant button, which is the drag end button, from the button trajectory from the button next to the last dragged vowel button to the consonant button, which is the drag end button

(e) Recognizing, among the consonants associated with the consonant button that is the drag end button, a consonant promised for the detected regression drag as a final consonant.

Korean character input method by continuous dragging on a screen (liquid crystal) keyboard, characterized in that characters are input with

The above content may refer to the drag button trajectory [a → b → a → d → ㅅ → ㅡ → ㆍ → ㅇ → ㅁ → ㅇ → ㅁ → ㅁ] in Fig. 19-10. In the button trajectory [...→ ㄴ → ㅁ → ㄴ], it is possible to recognize the input of a consonant (e.g. "P") related to the button by detecting the regression drag of the [ㅅ] button, which is the consonant button where the drag is terminated. explained that it can.

Also additionally,

In the above two cases,

The regression drag is a one-step or more than one-step regression drag.

Korean character input method by continuous dragging on a screen (liquid crystal) keyboard, characterized by

And in the above,

Recognizing the second consonant arranged in the grid sound or consonant button by horizontal regression drag

and

Recognizing double consonants by vertical regression drag

Korean character input method by continuous dragging on a screen (liquid crystal) keyboard, characterized by

Detect horizontal regression drag (more precisely, "rightward regression drag") from the drag button trajectory [a → b → a →...] and the positional relationship between the [a] button and the [b] button in Fig. 19-10 explained that it could be done.

In Fig. 19-13 and Fig. 19-14, the drag is started from the vowel button (eg [ㆍ] button) and the consonant promised by the regression drag returning to the vowel button (eg [ㆍ] button) (eg, [ㆍ] button). "ㅎ") was possible to be recognized. To summarize this, it is as follows.

On a keyboard equipped with a plurality of consonant buttons and a plurality of vowel buttons on a screen (liquid crystal) densely in a lattice form, Korean letters (consonants , vowel, consonant letter, word or phrase) in the method of inputting,

The promised consonant is recognized by the regression drag from the vowel button to the button other than the vowel button and back to the vowel button

Korean character input method by continuous dragging on a screen (liquid crystal) keyboard, characterized by

Although not described in the embodiment of the present invention, a number corresponding to each button may be input with one of the diagonal regression drags in Fig. 19-5. Of course, the downward-left regression drag can be the same as the two-stage leftward regression drag of Figure 19-4 if only the button trajectory is compared, so if there is another input target input by the two-stage leftward regression drag of Figure 19-4, it is "bend". angles must be taken into account.

Furthermore, the number corresponding to each button can be recognized by diagonal dragging instead of regression dragging. This can be easily implemented by analyzing only the button trajectory without calculating the "bend" angle, since it is only necessary to determine whether the button on which the drag has ended is a button in the diagonal direction. However, if the drag starts from the vowel button and ends with the consonant button (e.g. dragging upward from the [sh] button on the LG Electronics keyboard and ending with the [ㄴ] button), it is treated as an input of "vowel + consonant" It is treated as a numeric input without Explain that in the case of upward-left or upward-left-dragging from the button located at the top, it can be easily solved without the possibility of errors (errors in the 0-stage drag and 0-stage regression drag) by placing the fake buttons of DB1 ~ DB5 at a small height. did

35. Vowel recognition by continuous dragging on a keyboard with a vowel button that is not located on the side adjacent to the consonant button

The double keyboard (ie, QWERTY Korean keyboard) of Figure 18-1 (*) has 12 vowel buttons. There are 21 vowels in modern Korean, among which "ㅒ" is related to the [ㅐ] button and "ㅖ" is related to the [ㅔ] button. This can be easily seen from inputting "ㅒ = shift + ㅐ" and "ㅖ = shift + ㅔ". Except for 14 of the 21 modern Korean vowels (12 displayed on the button + ㅒ, ㅖ), the remaining 7 vowels are "ㅚ", "ㅘ", "ㅙ", "ㅟ", "ㅝ", "ㅞ", "ㅢ" is a diphthong consisting of a combination of two vowels. It can be seen that 5 of the 7 diphthongs are finally combined with "ㅣ".

In the previous application (Chapter 27), the first dragged vowel button was assumed to be a valid button, but as shown in Fig. 19-32, if there are vowel buttons that are not adjacent to the consonant button, the vowels "o" and "o" Entering a vowel that is not adjacent to a consonant button, such as ", ..., as a neutral vowel will be described. The key to this embodiment is to identify the vowel buttons that form valid syllables. When there are multiple valid vowels (ie, when there is ambiguity), it is also possible to display a list and let the user select. However, embodiments of the present invention suggest identifying exactly one vowel with a reasonable rule.

In the Korean QWERTY keyboard, the vowel button consists of three rows (lines). The vowels "ㅛ", "ㅕ", "ㅑ", "ㅐ", and "ㅔ" in the first row are not used as front vowels constituting a diphthong. Therefore, dragging from the vowel button in the first row to the vowel in the second or third row does not form a diphthong. Also, vowels arranged on the right side of the second row do not generally form diphthongs with vowels arranged on the left side. For example, "ㅣ" (right vowel) and "ㄴ", "sh", and "ㅗ" (left vowel) do not form diphthongs, and "a" (right vowel) and "sh" (left vowel) do not form diphthongs. It does not form a diphthong, and "sh" (right vowel) and "ㅗ" (right vowel) do not form a diphthong. This can be considered that most diphthongs are in the form of "X + ㅣ" and not in the form of "ㅣ + X". Also, vowels in the 3rd row (eg "ㅜ") and vowels in the 2nd row (eg "sh", "ㅣ") can form a diphthong, but vowels in the 2nd row (eg "sh") and vowels in the third row (eg "ㅡ") do not form diphthongs.

In inputting a vowel that is not adjacent to the consonant button as a neutral vowel, the vowel located on the right and the vowel located on the left do not form a diphthong, the vowel located in the second row and the vowel located in the first row It is an important property of the Korean QWERTY keyboard in applying the present invention that the vowel does not form a diphthong, and that the vowel located in the second row and the vowel located in the third row do not form a diphthong.

If the user drags [ㅇ → ... ㅛ → ㅕ → ㅑ → A → sh → ㅗ → ... ㅇ] as shown in Fig. 20-1 to input "ang", look at it. In this case, the user drags to the vowel button in the first row to input the vowel "a", proceeds to the intended vowel "a" in the second row, and proceeds to the left consonant button again in the second row. In the previous application (Chapter 27), assuming that all vowel buttons are adjacent to the consonant button, the first dragged vowel (eg, [ㅛ] button) was considered a valid button, but if the user clicked "ㅛ" If it was for entering [...→ ㅛ →ㅕ → ㅑ → A → ...]", there is no reason to proceed further to the right, and after dragging to [ㅛ], dragging again toward the consonant button on the left Since [...→ ㅛ → ㅕ → ㅑ → A → ㅛ → ㅗ → ...] does not form a diphthong, it is reasonable to determine that the rightmost vowel "a" is the vowel intended by the user. Therefore, the result is recognized as "ang".

The core of the present invention is that there is a vowel button surrounded only by the vowel button without being adjacent to the consonant button like the Korean QWERTY keyboard, and the vowel buttons dragged from the keyboard where the consonant button is placed on the left and the vowel button is located on the right. Among them, the rightmost vowel button is regarded as a valid vowel and processed. Among the vowel buttons dragged in this way, the rightmost vowel button is referred to as a "dragged rightmost vowel button", and will be more simply referred to as a "rightmost vowel button" or a "rightmost vowel". In addition, when forming a diphthong with the rightmost vowel, which is a vowel button considered as a valid button, the diphthong ("ㅚ" in Figs. 15-17) is recognized.

The button quests of drawings 15-17 of the previous application are [a → ㅅ → ㅎ → ㅗ → ㅇ → a → ㅣ → a → osh → ㅗ → ㅎ → ㄹ → ㅇ]. The button trajectory of the vowel part is [...→ ㅗ → ㅗ → A → ㅣ → A → ㅗ → ㅗ →...]. As already explained, it makes sense for "goong" to be recognized. This is because the rightmost vowel [ㅣ] is an effective vowel button even if interpreted according to the spirit of the present invention, and becomes a double vowel "ㅚ" by combining with "ㅗ" in front of it. The reason why it does not become "hoe" in Figures 15-17 is that there is a separate [ㅐ] button on the QWERTY Korean keyboard, so enter "ㅙ = ㅗㅐ" instead of entering "ㅙ = ㅗㅐ". If it was for the user to input "Kang", the user intentionally avoided the vowel button [ㅗ] (e.g. dragging to the vowel in the first row or the vowel in the third row) to the [A] button. Drag and drag again with the consonant button.

Korean Hangul has a syllable (consonant letter) consisting of "initial consonant + neutral" (i.e., "consonant + vowel"), and a syllable consisting of "initial consonant + neutral + final consonant" (i.e., "consonant + vowel + consonant") ( There is a consonant letter). In the case of "primary consonant + neutral consonant", the drag ends at the vowel button, so the problem becomes much simpler. The last dragged vowel button is regarded as a valid button and processed, and if a double vowel can be formed with the last dragged vowel button, the double vowel can be recognized. That is, if the user starts dragging from the consonant button and ends dragging from the vowel button to input a letter consisting of "initial consonant + neutral", the last dragged vowel button regardless of the position of the vowel button (eg, the rightmost vowel) is treated as the rightmost vowel.

In the case where there is a consonant button group on the left side and a vowel button group on the right side, such as the Korean QWERTY keyboard, it is reasonable to consider the rightmost vowel as a valid vowel button as described above. However, if a vowel button group that is not adjacent to a consonant button is on the upper side, the uppermost vowel is treated as a valid vowel button, if it is on the lower side, the lowermost vowel is treated as a valid vowel button, and if it is on the left side, the leftmost vowel is treated as a valid vowel button. Of course it is reasonable to do so. The rightmost vowel, the leftmost vowel, the uppermost vowel, the lowest vowel, etc. will be collectively referred to as the "most vowel" (more precisely, "the dragged most vowel button" or "the most recent vowel button"). For convenience, the term "rightmost vowel" is used as it is.

Let's take a look at the case of being dragged as shown in Fig. 20-2. A vowel in the third line (eg "TT") and a vowel in the second row (eg "ㅣ") can form a diphthong, and a vowel in the third row (eg "TT") and a vowel in the first row A vowel in (eg "ㅔ") can form a diphthong. The button trajectory from the first dragged vowel button to the last dragged vowel button in Fig. 20-2 is [...→ ㅗ → ㅠ → ㅜ → ㅡ → A → ㅣ → ㅔ → ...]. Considering "ㅗ+ㅣ", "TT+ㅣ", and "TT+ㅔ", it is determined whether the user wanted to input "ㅚ", "ㅟ", or "ㅞ". Hard to do. However, since the rightmost vowel is "ㅔ", it can be determined that "ㅞ" was intended to be input together with the vowel "TT" that can be previously combined with "ㅔ". As a result of Fig. 20-2, "wack" is recognized. If there is no diphthong that can be combined with the top vowel "ㅔ" in the button trajectory above, it is natural that "ㅔ" is treated as a valid button.

Currently, the technique of displaying a list of recommended words using a word dictionary in a smartphone is widely used. If it is assumed that words such as "woo", "wow", ... are stored in the word dictionary, and if the previously input letter is "woo" before the drag of drawing 20-2 occurs, the drag of drawing 20-2 It is also possible to interpret "Wi" and "Wow" and display "Wuuu" and "Wow" on the list of recommended words. This is because it can be seen that the user dragged the rightmost vowel [ㅔ] button in the process of inputting "Wuuu" by dragging for a longer time. This presupposes that there is "predominance" in the word dictionary, and even if it is not the rightmost vowel or a diphthong that can be combined with the rightmost vowel, it is possible to form a word in the word dictionary among a plurality of candidate vowels that can be recognized. The vowel is interpreted as a vowel that the user intends to input, and the user is given a choice. If there is no word dictionary or there is no word dictionary even if there is a word dictionary, it would be reasonable to recognize and output the result of FIG. 20-2 as “weck” based on the rightmost vowel “ㅔ”.

As already explained, the property that the vowel on the right and the vowel on the left do not form a diphthong in the QWERTY Korean keyboard is that when the user drags and inputs a diphthong, dragging a vowel that forms a diphthong while dragging from left to right It provides good properties to be As shown in Figure 20-2, the user drags [...→ TT → ... → ㅔ → ...] to input the vowel "ㅞ" and inputs the final consonant "a". It means that the vowels when sweeping toward the button (ie, from right to left) generally have a good property of not forming a diphthong by combining with the rightmost vowel.

Figure 20-3 is an example of putting 10 fake buttons, DB1 to DB10, from left to right at a small height according to the 10 columns at the top of the QWERTY Korean keyboard. In the QWERTY Korean keyboard such as Fig. 20-3, the consonant buttons and the vowel buttons adjacent to the surface are three buttons: [ㅛ] button, [ㅗ] button, and [ㅠ] button. However, as shown in Fig. 20-3, if you make it possible to drag through the fake button area or detour to the outside of the keyboard, the vowel in the first row (eg "ㅕ", "ㅑ", "ㅐ", "ㅔ") is a consonant It can be directly dragged from a button to a specific vowel (eg "ㅑ") without passing through other vowel buttons. Vowels in the third row (eg "TT", "ㅡ") are also specific vowels (eg "TT") ) can be dragged directly to Even in the case of a vowel button that is not adjacent to a consonant button, if there is a bypass means that can be directly dragged to a specific vowel button, there is an effect similar to that adjacent to the consonant button. However, in the case of a vowel button completely surrounded only by vowels, such as the [sh] button and the [a] button, it is necessary to apply the core idea of the present invention, and even if the vowel button is not completely surrounded only by vowel buttons, the user can bypass In the case of not dragging, the core idea of the present invention (processing the rightmost vowel as an effective vowel button) may be applied.

As shown in Fig. 20-3, if a "recommended word area" is provided that has a word index in the text input system and provides a list of recommended words at the top of the keyboard, even if the fake button area is not placed, the recommended word area is like a fake button area. You can use it. The word recommendation function is similar to the "auto-completion function" in the address bar of Windows or web browsers. You can think of the suggested word area as an area that displays an auto-completion candidate list. This is currently widely used in text input applications such as smartphones. Case presentation by drawing is not provided.

It was explained that "ㅒ" related to the [ㅐ] button and "ㅖ" related to the [ㅔ] button could be input by regression dragging. There is no confusion and the easiest way to input "ㅒ" is to drag it to [... → DB9 → ㅐ → DB9 → ㅐ → ...] in Fig. 20-3. In the case of "ㅖ", you can input "ㅖ" by dragging [...→ DB10 → ㅔ → DB10 → ㅔ → ...]. The drawing by the rag trajectory is abbreviate|omitted.

However, since the regression drag has the feature that the same button appears twice, it can be easily identified without using the fake button DBx. The button trajectory in Fig. 20-4 is [...→ ㅐ → A → ㅑ → ㅐ → A → ...]. Since the [ㅐ] button appears twice, it is easy to see that the regression drag was performed for the [ㅐ] button, and since the [A] button appears twice, it is easy to know that the regression drag was performed for the [A] button. . It is possible to determine that the neutral vowel intended by the user is "ㅒ" in two ways. First, since the alphabet associated with the [A] button is not defined in the Korean QWERTY keyboard, the regression drag of the [A] button is not defined as a specific vowel. For example, it is not defined as "X (specific alphabet) = function button (shift) + A" or "X (specific alphabet) = A A". Second, even if the regression drag of the [a] button is defined as a specific vowel input, the system determines that the vowel intended by the user is "ㅒ" because the rightmost vowel among "ㅐ" and "a" is the [ㅐ] button. can do. The most obvious thing is that the [ㅐ] button regression drag was performed before the [A] button regression drag, so it can be determined that the user's intended alphabet is "ㅒ". [..→ ㅐ → X → ... → ㅐ → ...] After the regression drag of the [ㅐ] button is finished, the regression drag for the [a] button is not made separately, but the regression of the [ㅐ] button In the process of dragging the surrounding buttons for dragging, [A] recursion dragging happened by chance. As a result of Fig. 20-4, "long&quot; is recognized.

The above description appears similarly in the case of Pantax's Hangul keyboard in Figures 19-28. In the case of Figures 19-30, it was dragged past the [ㅣ] button that can be combined with "A" to input the vowel "A", and past the "o" button that cannot be combined with "A". As shown in Fig. 19-30, when there are a plurality of rightmost vowels ("a" and "o" in Fig. 19-30), it is difficult to determine which rightmost vowel among the plurality of rightmost vowels is to be an effective vowel button. need. In the case of Figs. 19-29, since regression drag has occurred for the [A] button, it can be clearly seen that the intended vowel button is the [A] button (ie, the recognition result collection is “ㅑ”). In the case of FIGS. 19-30, the rightmost vowel dragged first among the dragged rightmost vowels (eg, [a] button, [q] button) is treated as a valid button. When there are many rightmost vowels dragged in this way, it is reasonable to process the first rightmost vowel among the rightmost vowels as a valid button. If there are multiple rightmost vowels, the user can use various means (e.g. fake button, function button, outside button, drag from 1st row to 2nd row in QWERTY Korean keyboard, ...) to proceed with dragging to the intended collection. This is because you can drag the input to the intended collection through

In the present invention, through the examples of the Pantech company's Korean keyboard and Korean QWERTY keyboard, it was shown that vowels are recognized by continuous dragging when there is a vowel button that is not in contact with a consonant button. Various types of keyboards are currently being introduced on the touch screen, and it is obvious that the idea of the present invention (eg, considering the rightmost vowel as an effective vowel button) can be equally applied to other keyboards. One more example of another keyboard is the example of Google's single vowel keyboard. In the QWERTY Korean keyboard, "ㅑ", "ㅕ", "ㅛ", and "ㅠ" are missing, so the QWERTY Korean keyboard is composed of 8-row keyboard compared to the 10-row keyboard. "ㅑ = Aa", "ㅕ = shr", "ㅛ = ㅗㅗ", "ㅠ = TT" are entered, so the [A] button, [sh] button, [ㅗ] button, and [TT] button have "ㅑ" respectively. , "ㅕ", "ㅛ", and "ㅠ" are related. This is the same as "ㅒ" and "ㅖ" are related to the [ㅐ] button and the [ㅔ] button on the QWERTY Korean keyboard, respectively, and you can refer to the "ㅒ" input example of the QWERTY Korean keyboard. Since it is a keyboard that is currently widely known, the presentation of drawings is omitted. The fact that "ㅣ", which mainly forms the back vowel of a double vowel, is located on the rightmost side of the second row also has a similar property to the QWERTY Korean keyboard. Google's single vowel keyboard also treats the rightmost vowel as a valid button, as described in the QWERTY Korean keyboard in the same principle, so the example is omitted.

The above contents are summarized in steps as follows.

On a keyboard equipped with a plurality of consonant buttons and a plurality of vowel buttons on a screen (liquid crystal) densely in a lattice form, Korean letters (consonants , vowel, consonant letter, word or phrase) in the method of inputting,

The keyboard has one or more vowel buttons that are not in contact with consonant buttons,

(a) Recognizing the dragged first vowel button, the middle dragged button, and the dragged last vowel button

(b) Recognizing the last vowel farthest from the consonant button group among the dragged buttons as a valid vowel button

(c) determining whether a double vowel is formed by combining with a vowel recognized as the effective vowel button among the dragged buttons;

Korean character input method by continuous dragging on a screen (liquid crystal) keyboard, characterized in that characters are input with

.

Claims (1)

In the method of inputting Korean on a keyboard equipped with a Korean consonant button and a Korean vowel button,
A consonant is recognized in response to pressing the consonant button,
A vowel is recognized in response to pressing the vowel button,

Images