KR20200110260A - Korean syllable characters input method and device on screen keyboard - Google Patents

Abstract

Provided is a technology which can simultaneously process the input of modern Korean and Hangul ancient languages. In addition, a technique for inputting numbers and English alphabets in the Korean mode is presented. In a method of inputting Korean on a screen keyboard having a Korean consonant button and a Korean vowel button, consonants are recognized in response to pressing of the consonant button on the screen keyboard, and vowels are recognized in response to pressing the vowel button on the screen keyboard.

Description

Method and device for inputting Korean syllable characters on a screen keyboard{.}

[0001] The present invention relates to an alphabetic input device and method thereof 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 to transmit and receive digital information such as texts has been added to portable terminals focusing on voice calls. Therefore, in the beginning, a keypad provided in a portable terminal for the purpose of inputting a phone number also included a means for inputting characters. However, since the size of a keypad used as an input means of a portable terminal becomes smaller and 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 telephone keypad, the alphabet must be expressed by combining one or two or more buttons on the keypad.

.

A technology that can simultaneously process the input of modern Korean and Hangul ancient languages is presented. In addition, a technique for inputting numbers and English alphabets in Korean mode was presented.

Fig. 1-1. An example of configuring a standard keypad using an English standard keypad
Fig. 1-2. When about 3 alphabets are assigned to each button, the central alphabet is set as the representative alphabet, and the alphabet placed on the left and right is an example of configuring a follow-up keypad as a follow-up alphabet.
Fig. 1-3. An example of configuring a standard keypad when assigning 3 to 4 alphabets to each button
Fig. 2-1. An example of configuring a successor keypad in Japanese (1)
Fig. 2-2. An example of configuring the successor keypad in Japanese (2)
Fig. 2-3. Graph of 2D recycling control processing method
Fig. 2-4. Graph of 2D cross control processing method
Fig. 3-1. An example of configuring the successor keypad (Arabic)
Fig. 3-2. An example of configuring a subsequent keypad (Arabic, using two control buttons)
Figure 3-3. When about 3 alphabets are assigned to each button, the central alphabet is set as the representative alphabet, and the alphabet placed on the left and right is an example of configuring a follow-up keypad as a follow-up alphabet.
Fig. 4-1. Example of assigning a basic consonant and a basic vowel to each button in pairs 1 (Korean)
Fig. 4-2. Example of assigning a basic consonant and a basic vowel to each button in pairs (Korean)
Fig. 4-3. Example 3 of assigning a basic consonant and a basic vowel to each button in pairs (Korean)
Figure 4-4. Flow chart of inputting basic consonants and basic vowels by repeat selection method (example of Korean)
Figure 4-5. Example of applying 3 vowel elements
Figure 4-6. A case in which Fig. 4-5 is expressed in terms of applying the iterative selection method using 4 vowel elements
Figure 4-7. Example of assigning 4 vowel elements to 4 buttons
Figure 4-8. An example of resolving and expressing Fig. 4-7 from the viewpoint of applying the iterative selection method
Figure 4-9. Example of deformation display in Fig. 4-5
Figure 4-10. Examples of modern Korean vowels "ㅡ", "ㅏ", "ㅣ"
Figure 4-11. Example of deformation display in Fig. 6
Figure 4-12. Example of deformation display in Fig. 4-10 ("+" type)
Figure 4-13. Example of deformation display in Fig. 4-10 ("-ㅏ" type)
Fig. 4-14. Example of deformation display in Fig. 4-10 ("H" type)
Figure 4-15. Example of deformation display in Fig. 4-10 ("ㅏㅓ" type)
Figure 4-16. Example of transforming 4 rows of buttons into 1 row on a 3*4 keypad (1)
Fig. 4-17. Example of transforming 4 rows of buttons into 1 row on a 3*4 keypad (2)
Figure 4-18. Examples of modern Korean vowels "ㅡ", "ㅏ", "ㅓ", and "ㅣ"
Fig. 4-19. Example of deformation display in Fig. 4-12
Figure 4-20. Examples of combining vowels using modern Korean vowels "ㅡ", "ㅏ", and "ㅣ" (graph)
Figure 4-21. Examples of combining vowels using modern Korean vowels "ㅡ", "ㅏ", and "ㅣ" (Graph 2)
Figure 4-22. Flowchart of Korean keypad input processing process
Figure 4-23. Flow chart of Korean input processing process on 2Beolsik keyboard
Figure 4-24. Keypad Korean input processing flow (when applying the method of repeat selection method flow to consonant input)
Figure 4-25. Keypad Korean input processing flow (when applying a specific button combination to consonant input)
Figure 4-26. Keypad Korean input processing flow chart (general)
Figure 4-27. Flowchart of the keypad Korean input processing process (added when applying the character completion button)
Figure 5-1. Chinese character input using Pinyin Dictionary and Pinyin
Figure 5-2. An example of text input in English using the prerequisite association code
Figure 5-3. Example of processing input values as promised simple codes in parallel input method (1)
Figure 5-4. Example of processing the input value with the promised simple code in the parallel input method (2)
Figure 5-5. Application of parallel input method through client and server
Figure 5-6. Grouping examples of phrases (words or phrases) stored in the index
Fig. 6-1. A case in which the server (intermediate server) interprets the simple code transmitted from the client, and transmits the information obtained by interpreting the simple code to a third server that needs the information.
Fig. 7-1. An example of a follow-up keypad that can input various symbols by the control processing method (English keypad)
Fig. 7-2. An example of a follow-up keypad that can input various symbols by the control processing method (Korean keypad)
Fig. 8-1. Example of an existing mobile phone with various function buttons arranged on the upper side of 3*4 numeric keypad
Figure 8-2. 3*4 Case where various function buttons are located below the numeric keypad 1
Fig. 8-3. 3*4 Case where various function buttons are arranged below the numeric keypad 2
Figure 8-4. Examples of various function buttons arranged on the left/right side of 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. Example of using various function buttons as control buttons 3
Figure 8-8. Example of using various function buttons as control buttons 4
Fig. 9-1. When using the up/down/left/right movement buttons as an increase/decrease/multiple button, the function corresponding to each button is converted into an icon and displayed on the LCD
Fig. 9-2. An example in which the symbol associated with each number button is converted into an icon and displayed on the liquid crystal.
Figures 10-1 to 10-4. An example of a consonant separator keypad in a language using the Roman alphabet
Fig. 10-5. Cases of shortened input method in consonant vowel separation keypad and case of processing input value with promised simple code in parallel input method
Figure 10-6. Example of a consonant separator keypad in a language using Roman alphabet (5)
Fig. 10-7. Flow chart of applying language restriction input method in consonant vowel separation keypad (1)
Fig. 10-8. Flow chart of applying language restriction input method in consonant vowel separation keypad (2)
Fig. 10-9. Flow chart of applying language restriction input method in incomplete consonant separation keypad
Fig. 10-10. (In a system with all words) Application case of parallel input method (1)
Fig. 10-11. (In a system with all words) Application case of parallel input method (2)
Fig. 10-12. (In a system with all words) Application flow diagram of the parallel input method (1)
Fig. 10-13. Flowchart of applying language restriction parallel input method (in a system with all words) (2)
Fig. 10-14. Example of applying the full code input method (and parallel input method) in the system
Fig. 10-15. Application of parallel input method in a system with index of phrases (words or phrases) consisting of only representative alphabets (1)
Fig. 10-16. Application of parallel input method in a system with index of phrases (words or phrases) composed of only representative alphabets (2)
Fig. 10-17. Case of handling the input of a winding sound primarily as a simple code (shortened input value)
Fig. 11-1. Example of system configuration when input values are interpreted on the client side
Fig. 11-2. Example of system configuration when input values are interpreted on the server side
Figures 11-3 to 11-10. Example of processing simple codes (in parallel input method)
Figure 11-11. Examples of simple code (i.e. short code or short input value) type
Fig. 12-1. Example of entering functions by control processing method
Figure 12-2. An example of displaying the controls assigned to each button on the LCD screen
Figures 13-1 to 13-4. An example of processing part of the input value as full code and processing other part as simple code
14-1 to 14-2. Example of control processing method using long press
Fig. 14-3. Case of using long press and then short press
Fig. 14-4. Case of using short press and then long press

The summary of the invention presented in the applicant's prior application (application number 10-2000-0031879 and PCT/KR00/00601) is as follows.

First, according to the "Partial All Selection Method", a predetermined number of grids are formed in a form corresponding to the arrangement of all buttons in the keypad for each button on the keypad, and alphabets are arranged in grids, and the alphabet to be entered (hereinafter, "target In the grids of the first button and the first button on which the alphabet is arranged), the desired alphabet is input by combining and pressing the second button on the keypad corresponding to the position of the alphabet. For example, in Fig. 1-1, input "A = [1]+[2].

Among the grids of buttons, some grids are used, including a reference grid in which the first and second buttons become the same, and some grids are used, but the combination of the first and second buttons is highly convenient. Using the ordered grid first was the core of the partial-total selection method. In this way, the core of the partial selection method lies in the standard grid, and the keypad that can utilize the concept of the standard grid was named "reference keypad".

Next, the reference repetitive selection method is the number of times the button is pressed in the order of the alphabet at the reference grid position to the reference grid (the order of convenience of button combinations in the partial selection method) on the reference keypad configured to apply the partial selection method. It was a way to select the alphabet according to. The standard repetitive selection method is to apply the repetitive selection method from the reference keypad, and the dedicated reference keypad to the repetitive selection method was named "simple keypad", and for convenience, the repetitive selection method is applied to the simple keypad as it is used previously. I named it the simple repetitive selection method.

And there was "control processing method", and there were "subscript control processing method" and "subsequent control processing method". In the subscript control processing method, when a modified alphabet consisting of a subscript and a basic alphabet is input, the modified alphabet can be input by combining the subscript control and the basic alphabet. The follow-up control processing method is to set a group of alphabets assigned to a button as the relationship between the representative alphabet and the subsequent alphabet, and when inputting the subsequent alphabet, the following alphabet is input by combining the representative alphabet and the subordinate rankings attached to the representative alphabet. To be able to do it. For example, in Fig. 4-1, you can enter "ㅋ = ㄱ+[*]".

Subscript control processing and subsequent alphabet control processing are essentially similar, and the subsequent control processing is considered to be more general. This is because, in the case of subscript control processing, it can be seen that the modified alphabets are appended in a certain order to the basic alphabet in a specific alphabet group. However, in the case of subscript control processing, since the modified alphabet can be divided into subscript and basic alphabet, it is the case that the alphabet group has a strong relationship in its shape, and the subsequent control has a strong relationship in its order or pronunciation. This 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 enter the alphabet without ambiguity through control processing. The simplified keypad by omitting the subsequent alphabet was referred to as "subsequent keypad", and the simplified keypad by omitting the modified alphabet was referred to as "simple keypad", and both were collectively referred to as "simplified keypad". The keypad in which all subsequent alphabets (or modified alphabets) were displayed was referred to as "full display pad" compared to the simplified keypad.

It is said that the entire display pad can also input the subsequent alphabet (or transformed alphabet) through the control processing method, and on the contrary, users who remember the layout of the entire display pad can use the input method in the full display pad. I did. One of the features of the previous application was that the simplified keypad can be expanded to configure the entire display pad, and the entire display pad can also be used to input subsequent characters through the control processing method according to the user's convenience.

One of the effects of applying the control processing method is that, in addition to the effect of removing ambiguity, as shown in the previous application, the subsequent alphabet is not displayed on the keypad through the relationship between the representative alphabet and the subsequent alphabet, and "hidden". By doing this, the keypad can be simplified. This is called “hidden control processing method” for convenience. However, as mentioned in the previous application, the subsequent alphabet can also be input through the control processing method in the entire display pad in which the subsequent alphabet (or modified alphabet) is displayed on the keypad. For convenience, this is called "non-hidden control processing method".

Due to the nature of the present invention, since it is essential to describe specific examples, detailed contents will be described through examples.

First, the contents of the previous application for each language are 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 Prior application and the scope of use of the keypad in 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 phone board, such as a numeric keypad of a mobile terminal or a standard keyboard, or a keypad or door lock configured in software on a screen. In addition, although the numeric keypad provided in the standard keyboard differs in the arrangement of the keypad and the numeric buttons proposed in the previous application and the present invention, it is obvious that the arrangement on the keypad buttons in the earlier application and the present invention can be applied to the keypad provided on the keyboard. . For example, in the previous application and in the present invention, the alphabet arranged on the [1] button is placed on the [1] button of the numeric keypad provided on the keyboard, and is arranged in the same manner as follows to input the alphabet, the use of simple codes, and the use of various codes. It can be used for memorization.

1.2 Setting the consecutive hitting delay time and the hitting (離打) delay time

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

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 the vowel "ㅗ", and if 1.1 seconds delay time If it is input with a, it is primarily recognized as two consonants ("ㄱ", "ㄱ"). 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 appearance structure of consonants and vowels in the language. In addition, even when input with a delay time of 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 continuously input 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 stroke was recognized as one stroke. . The difference is that the standard time delay value judged by two consecutive strokes (e.g. 0.1 second) and the time delay value judged by each one stroke (e.g. 1 second) are different.

In general, it can be seen that the repetitive selection method is superior in terms of input convenience among the partial and repetitive selection methods of the previous application. Therefore, this means that while utilizing the advantages of the repetitive selection method (simplicity and convenience of the input rule), ambiguity can be largely avoided by using the structure of a specific language in which consonants and vowels alternately appear. There is an advantage in that the implementation of the algorithm can be simplified by setting the and other delay times differently and allowing the user to specify 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 earlier application, the relationship between ㄱ, ㅋ, and ㄲ was explained as the relationship between the representative alphabet and the modified alphabet, and ㅋ = ㄱ +{Abbreviated}, ㄲ = ㄱ+{Kyungeum}, but ㄱ(representative alphabet) This is because the result is the same even if the relationship between the representative alphabet and the subsequent alphabet, such as, ㅋ(2nd), ㄲ(3rd).

In the case of Japanese in Fig. 2-1, an example of input by the subsequent control processing method is shown again as follows. As あ (representative alphabet), い (2nd), い (3rd), え (4th) and お (5th), select あ with one stroke of the [1] button (あ= [1]) Can be done, and the 2nd, 3rd, 4th, 5th control is placed on a control button (ex. [*]) and selected repeatedly according to the number of times the button is pressed, and the subsequent alphabet is selected by a combination of the representative alphabet and the subsequent alphabet. You can enter. For convenience, the state of selecting the control is indicated in braces, for example, when applying input after control, あ=[1], い = あ+{2nd} = [1]+[*], う = あ+{3rd} = [1]+[*]+[*], え = あ+{4th} = [1]+[*]+[*]+[*], お = あ+{5th} = [1]+[ *]+[*]+[*]+[*]

Here again, make the relationship between the representative alphabet and the subsequent alphabet, such as あ (representative alphabet), い (2nd), う (3rd), え (4th), and お (5th), but place the follow-up control on the control button and repeat selection. It is not selected by the method, but only the "follow" or "next" control can be selected by pressing a specific control button (eg [*]) once, and when the second successor character (eg. い) is entered, the representative alphabet And "next control" (that is, い = あ+{next} = あ+[*]), and when entering the 3rd succeeding character え, the preceding character (2nd succeeding character) is added to the 3rd succeeding character. It is regarded as a new representative alphabet (second representative alphabet), and can be entered by combining the second subsequent alphabet and "Next Control". That is, う = い+{next} = [1]+[*] + [*]. Similarly, when entering the 4th successor alphabet え, the preceding character (3rd successor alphabet) う is regarded as the new representative alphabet for the 4th successor alphabet (3rd generation table alphabet), and when inputting え = う+{next} = You can enter [1]+[*]+[*] + [*]. The same is true for the 5th successor alphabet.

This result is the same result as placing the sub-priority control (2nd, 3rd, 4th, 5th, ...) on the control button and selecting it by the repeat selection method, combining the representative alphabet and the sub-priority control. 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 remaining subsequent characters. That is, え = い+{next} = [1]+[*] + [*], but い could be entered without ambiguity, and い is also a form that is combined with "Daum Control", resulting in a subsequent alphabet without ambiguity. You can enter え.

Thus, in the relationship between the representative alphabet and the subsequent alphabet, it is assumed that the control button does not have a subordinate priority control, but only one "next" control, and when entering the subsequent alphabet, the preceding alphabet is regarded as the new representative alphabet, and this preceding alphabet and the "next" "The method of inputting a combination of controls is called "chain-type subsequent control processing method" for convenience. Even though the previous application did not display the sub-priority control on the subsequent control button, the user only needs to recognize that a specific button is the subsequent control button, but the advantage of this chain-type subsequent control processing method is to control the "next control". Even if it is displayed on the button, the display can be simplified. In the present invention, the results of the "follow-up control processing method" and "chain-type follow-up control processing method" described in the previous application are the same, so they are used interchangeably.

1.4 How to handle skip control

In the subscript control processing method, when entering the transformed alphabet ё consisting of ".. + e", it was shown that it can be entered by combining each of .. and e. Alternatively, it was possible to enter e as the basic alphabet and the remaining subsidiary alphabets that are related in shape or ranking as the successor alphabets, and input them as a combination of subordinate rankings and basic alphabets (e.g. e (basic alphabet), ^/ e(2nd), ^{^} e(3rd),... ). In addition, the control button, in which controls that can have meaning only when combined with an alphabet (that is, a specific number button) are used repeatedly, was able to input a modified alphabet or a subsequent alphabet without ambiguity.

In the case of Roman characters, 11 variants of the alphabet ( ^/ e, ^{^} e, `e, ё, `a, ^{^} a, ^{^} i, `u, <sup>^</sup> u, c, <sup>^</sup> o) are used in French, and are used for the modified alphabet. There are 5 types of upper points (/, ^, `, .., s). If the subscript control selection order is /, ^, `, .., s, you must enter <sup>^</sup> a = a+[*]+[*]. However, in French, only two subscripts "`" and "^" can be combined in the alphabet a, so the subscript "/" cannot be added, and if the subscript "^" that can be combined is selected by skipping this, ^{^} a You can enter = a+[*]. This is called "Skip Control Processing Method" for convenience. In other words, this is the same as entering the subsequent alphabet (or modified alphabet) as a control processing method by placing the sub-order of the subsequent alphabet such as a (basic alphabet), `a(2nd), ^{^} a(3rd).

Likewise, in Japanese, only つ among the alphabets of the あ, や and た lines is the line with the long sound, and the line with the sound tone is only the alphabet of the か line, さ line, た line, and ほ line, and the half tone is only It only exists in the alphabet of line ほ. As a result, it can be seen that in the alphabet つ there are two variants of the long sound and the sound sound, and in the alphabet of the ほ line, the two variants of the sound sound and the semi-voiced sound exist. Therefore, it can be made possible by pressing the subscript control button once when inputting the modified alphabets of the rest of the alphabet except for the 6 alphabets in which two modified alphabets exist. For example, if you set the control button as the [*] button and apply the input after control, you can do something like ぁ = あ+[*], が = か+[*]. In the case of 6 alphabets with two variant letters, when inputting a variant alphabet, the control can be selected in the order of the frequency of use of the variant alphabet. For example, when the control button is set as the [*] button and the input after control is applied, っ = つ+[*], づ = つ+[*]+[*], ぼ = ほ+[ *], ぽ = ほ+[*]+[*]. In other words, this is to ensure that controls that cannot be combined with the basic alphabet in control selection do not take effect. For example, even if が = か+[*], [*] can be treated as selecting a sound control, not a long sound control, because there is no long sound in the basic alphabet か that is combined with the control, the long sound control is not selected. This is because it is assumed that the sound tone control was selected by skipping over,.

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

Even if the control is selected by the repetitive selection method, if the representative alphabet displayed on the keyboard can be entered without ambiguity when entering through the control processing (for example, even if there is only one representative alphabet displayed on the keyboard, the partial selection method, etc. In the case of applying the missing method), the remaining subsequent characters can be entered without ambiguity. This is because the ambiguity is removed through the control process, because the control alone cannot represent a specific alphabet 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 native language alphabets can be placed in "order close to the standard grid", and then numbers and English alphabets can be placed. When applying the standard repetition selection method, it is also in the order close to the standard grid. Explained that the national language alphabet and number can be selected. Likewise, in applying the subsequent control processing method, not only the native language alphabet belonging to a specific button, but also numbers and English alphabets (in case of non-Roman language) can be entered through the subsequent control processing method.

Numerals or English alphabets may be placed as a subsequent alphabet following the national language alphabet. For convenience, in Japanese, for example, あ(representative alphabet), い(2nd), う(3rd), え(4th), お(5th), 1(6th), .(7th), q(8th), z (9th) It can be put together. Also, if there are buttons available to control numbers or English characters, press the control buttons for あ(representative alphabet), い(2nd), う(3rd), え(4th), お(5th). Button (for example, [*] button), and another button (for example, [#] button) as a button for numbers or English alphabet あ(representative alphabet), 1(2nd), .(3rd), Numbers or English alphabets can be entered by placing a relationship of q(4th) and z(5th). For example 1 = あ+[#] = [1]+[#],. = あ+[#]+[#] = [1]+[#]+[#], q = あ+[#]+[#]+[#] = [1]+[#]+[#] It becomes like +[#]. If a control button is available, it is also possible to have separate control buttons for numeric entry and control buttons for English alphabets.

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

1.6 Grouping according to English alphabet pronunciation

In configuring the keypad for each language in the previous application, in consideration of the application of the control processing method and use for memorization, alphabets were grouped into similar pronunciation groups and assigned to each number button. In the case of English, a method in which each group is assigned to each number button by grouping 3 or 4 alphabets in alphabetical order is widely used, but it is also possible to group and assign to each number button in consideration of the similarity of pronunciation. . The following are some examples of English consonants grouped into 9 groups according to the similarity of 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 example, many variations are possible. The 5 vowels can be put into groups of 2 grouped properly. This can be convenient when applying the shortened input method using a simple code to be described later. In the case of a non-English speaking language, in allocating the grouped English alphabets to each button, it can be allocated in consideration of 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 with a similar pronunciation of “a”. In the case of Japanese, groups G, K, and Q are assigned to buttons with the alphabet "か" with similar pronunciation. Therefore, even in the grouping of English alphabets, grouping can be performed in consideration of the native language alphabet grouping of each language.

2. Supplements for each language

* Hereinafter, the contents of the previous application for each language are supplemented and the advanced matters are described as follows. It is obvious that, among the contents described in the supplementary information for each language, if the contents described in one language can be applied to another language, it can be applied to other languages without specially pointing out this.

2.1 English

Just as the following alphabet can be input through the control processing method on the entire display 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 them through control processing. In the case of English, subsequent controls (2nd, 3rd) can be placed on the same control button (for example, [#] button), or each can be arranged separately on another button (for example, [*], [#] button). In the case of English, when ABC is placed on one button, if A is the representative alphabet, B and C are entered through the subsequent control processing, and if B is the representative alphabet, A and C are each subsequent control. It is input through processing. As mentioned in the previous application, the ranking of the representative alphabet and the subsequent alphabet may be determined in consideration of the frequency of use, etc.

For example, in groups A, B, and C, if A is the representative alphabet, 2nd, 3rd control is 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 2nd and 3rd controls are placed on the [*] button and [#] button, respectively, and the input is applied after control, A = B+{2nd} = [2]+[*], C = B+{3rd} = [2]+[#]. 1-2 is a case in which the central alphabet among the alphabets of each group is used as the representative alphabet, and the subsequent alphabets are arranged on the left and right, in order 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, will be called "CPMERC: Control Processing Method Except Representative Chanracter" for convenience.

In addition, when four alphabets P, Q, R, 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 example of the earlier application In addition, one of the four alphabets can be placed on a grid forming a top-bottom contiguous combination to apply the partial full selection method. See Fig. 1-3.

2.2 Japanese

In the case of Japanese in the earlier application, alphabets can be grouped based on 50 phonetic levels, followed by control processing with the letter あ as the representative alphabet (あ, か, さ, …) and the remaining alphabets as the subsequent alphabets. In the earlier application. In applying the subordinate rankings of the subsequent alphabets presented in the previous application, the 50-note chart may be simply applied as shown in the following table, almost similar to the method 3 of the previous application. This can give users a sense of familiarity with the simplicity of the subordinate ranking. As in the earlier application, ん can be treated as being considered appended to any representative alphabet. In addition, it can be regarded as appended with a 50-phonetic alphabet (for example, い, う, え) or ん in the empty place of the や line or the わ line.

Method of prior application 3 Simple method of using 50 notes Reference grid 2 ^nd 3rd 4th 5th Reference grid 2 ^nd 3rd 4th 5th あ い う え お あ い う え お か き く け こ か き く け こ さ し す せ そ さ し す せ そ た ち つ て と た ち つ て と な に ぬ ね の な に ぬ ね の は ひ ふ へ ほ は ひ ふ へ ほ ま み む め も ま み む め も や ゆ よ や ゆ よ ら り る れ ろ ら り る れ ろ わ を ん わ を

In the earlier application, the alphabet in the first column, which is considered to be the most representative for convenience in the case of Japanese, was used as the representative alphabet.Also, the alphabet in any column may be used as the representative alphabet, and an arbitrary alphabet in each group is used as the representative alphabet. You can also do it. In addition, in assigning the alphabet of each row to each button as a group, as mentioned in the previous application, the row of buttons on the keypad is standard ([1], [2], [3], [4],... ), or columns can be assigned as criteria ([3], [6], [9], [2], [5],... ). Likewise, it is not possible to allocate based on row or column, but can be randomly assigned.

Also, in the Japanese example of the earlier application, if "N" is placed at the standard grid position of the [0] button, and 2nd, 3rd, 4th, 5th controls are placed on the [*] button and the [#] button, respectively, the [0] button In order to use as a control button for inputting long/voiced/half voiced sounds, it was assumed that “n” was assigned to a random number button instead of the [0] button. However, in this case, you may place "N" at the position of the reference grid of the [0] button, additionally arrange long/voiced/half-voiced controls in the order close to the standard grid, and apply the repeat selection method to control selection. This is because "ん" does not appear consecutively in one word. See Fig. 2-1. Alphabets that do not appear consecutively are selected for one stroke of the button on which the corresponding alphabet is placed, and two strokes, three strokes,… Being able to select different controls on the machine can be applied to all other languages as well. This property is also utilized in the method using the vowel elements of Korean, which will be described later.

2.3 Arabic

There are 28 consonants in Arabic. In the earlier application, the Arabic consonants having the meaning of numbers are grouped as follows and assigned on the keypad buttons, and each alphabet is placed at the position of the reference grid with the alphabet having the smallest number as the representative alphabet of each group. A method has been proposed to arrange the remaining alphabets on the keypad in the order (explained in the previous application) from the alphabet having the meaning of small numbers to the standard grid. Also, in the case of Japanese, Roman language, Korean, Indian, Arabic, etc. in the previous application, a method of inputting the alphabet by control processing was suggested. In the case of Arabic, a method of handling subscript control has been suggested by considering vowels that are not used very much as subscripts.

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

[1] Among the alphabets having the meanings of 1, 10, and 100 assigned to the button, the alphabet having the meaning of 1 is displayed on the keypad as the representative alphabet, and the remaining alphabets having the meanings of 10 and 100 can be processed for subsequent control. have. The control button can use any button as in the previous application. When the [*] button is used for the subsequent control button and the 2nd and 3rd controls are arranged, the average number of strokes for consonant input is 2 strokes. Since only one alphabet is arranged per button, when selecting the alphabet displayed on the button, it is not necessary to select the partial whole selection method. Since the arrangement of the alphabet is conceptual, the alphabet may not be arranged on the keypad as described below.

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

In the present application, an example in which an alphabet with a small number meaning is used as the representative alphabet of each group regardless of the frequency of use of the alphabet in each unit, and an alphabet with a small number meaning can be selected first in the alphabet of the remaining units. see. The control can be entered first or later.

= [*] +

가 되고,

= [*] + [*] +

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

= [*] +

Becomes,

= [*] + [*] +

Becomes. The same is true for the rest of the alphabet. In this case, the [#] button can also be used for vowel control processing.

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

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

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

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

= [윗점컨트롤] +

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

= [0]. It is also possible to treat an alphabet with a meaning of 1000 as a single group alphabet. in this case

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

Will be Or, an alphabet with meaning of 1000 is an alphabet with meaning of 70 (

) Has a high point, so it is possible to control the high point control by selecting it before various vowel controls. That is, when entering the upper point control first

= [High Point Control] +

It can be entered as. This upper point control process can be allowed in parallel with other input methods for other alphabets with upper points attached. In this case, it becomes 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 (100 unit control in this case) is pressed with the [#] button, the alphabet meaning 200

= [#] +

Becomes. In this case as well as in the case of Japanese of the elected applicant,

= [*] + [*] +

Can be allowed in parallel. In the case that an alphabet with meaning of 1000 belongs to the 1 group alphabet

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

or

= [#]+[#]+

Becomes. In other words, you can think of the 2nd, 3rd, and 4th controls arranged on the [*] button and the 3rd, 4th controls on the [#] button. Considering the fact that Arabs write horizontally from right to left, that is, it is possible to assign 2nd, 3rd, 4th controls to the [#] button, and place 3rd, 4th controls to the [*] button.

This means that in Arabic, it is possible to enter the commonly used consonants at an average of about 1.7 strokes without ambiguity.Also, since Arabs know the meaning of the numbers in their native language alphabet, they dare to enter the alphabet on the keypad (in the example, 1 There is a very great advantage of being able to input an alphabet without displaying a unit alphabet, that is, a representative alphabet. In other words, when applying the method in this application through a keypad displaying only numbers, which unit of the representative alphabet is the alphabet, the control button is the control button for which unit of the alphabet, and the subsequent control is one control button. If you use, you can enter most of the alphabets (Arabic consonants) needed in real life if you understand the rules such as how to select each subsequent control and whether to pre-enter the control button.

As pointed out in the previous application, vowels can also be controlled. If both [#] and [*] are used for consonant control processing, the alphabet having the meaning of 1000 as in the Japanese of the previous application is displayed on the [0] button. Instead of placing it, it is possible to control by placing it on the [1] button, designating the [0] button as a control button for vowel processing, and selecting a subscripted vowel (vowel control, subscript control) by the repeated selection method. Similarly, the vowel control (subscript type vowel) is selected according to the number of times the button is pressed in the order of frequency of use. If only one [*] is used as the subsequent 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, alphabets (one unit alphabet) having meanings 1 to 9 are used as the representative alphabets of each group, but the most frequently used alphabets in each group may be used as the representative alphabets. . And in order to reduce confusion, the alphabet of any unit among 1 unit alphabet (alphabet meaning 1 to 9), 10 unit alphabet (alphabet meaning 10 to 90), and 100 unit alphabet (alphabet meaning 100 to 900) Can also be used as a representative alphabet. 3-3 shows the 10 unit alphabet as the representative alphabet, placed in the center of each group, and the remaining left and right alphabets (100 unit alphabet, 1 unit alphabet) are input by using the control button assigned to the left and right by the control processing method. This is an example.

Likewise, the alphabet selected by the subsequent control can be made with the alphabet of each unit according to the frequency of use. For example, if the 100-unit alphabet is the most frequently used, and this is the representative alphabet, and then the 1-unit alphabet is used frequently, the 2nd control (that is, 1 unit control in this case) and the representative alphabet can be combined and entered. In addition, the 10-unit alphabet can be entered by combining the 3rd control (ie 10-unit control) and the representative alphabet.

In the previous application, it was said that it was possible to input the subsequent alphabet through the control processing method on the entire display pad, so it is possible to input consonants by the subsequent control processing method on the keypad of the earlier application as well as the subscript control processing method. Do. In the 3*4 keypad, if the subscript control button for vowels is the [0] button, it is possible to distribute the control button 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 allocating a basic consonant and a basic vowel in Korean to each button in pairs, and inputting the basic consonant and basic vowel displayed on the keypad by the repeat selection method. In Fig. 4-1, aspirated, hard and extended vowels were input by the control processing method, and in Fig. 4-2, only aspirated and hard tones were input by the control processing method. 4-3 shows a case in which aspirated, hard, basic, and extended vowels are input by the control processing method.

2.4.2 Program Implementation

4-4 is just an example of a flowchart for implementation, and more efficient programming is possible. For example, if the consonant part of the support comes from Fig. 4-4, it is possible to implement a little more efficiently by checking whether it is a consonant that can form a double support.

The example of Korean presented in the previous application can be applied to other languages with similar characteristics (structures in which consonants and vowels alternately appear). In the case of other languages, it is sufficient to reflect the character of the other language.

For example, if you want to construct a Hindi input system using a pair of basic consonants and basic vowels, you can reflect the characteristics of Hindi and implement it similarly to the case of Korean. In the case of Hindi, the appearance of consonants and vowels than in the case of Korean. The simpler rules make it easier to implement.

2.5 Hindi

In the applicant's earlier application, Hindi consonants are grouped into nine groups and assigned to buttons [1] to [9], so that the vowel assigned to the [0] button is selected with one stroke of the [0] button. It is possible to group into groups of dogs, and always select the representative consonant as 1 stroke and 10 vowels as 2 strokes. Vowels ___(ri) that are not placed on the keypad and are not frequently used can be handled by the control processing method. In grouping consonants into 10 groups, it is possible to group consonants in consideration of the similarity of pronunciation as suggested in the previous application. 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 and consonants. In other words, consonants come out continuously. In this case, it is very easy to display "consonant + consonant" even if you enter "consonant + ___(a) + consonant". Of course, it is also possible to directly input "consonant + consonant", but in this case, the same representative consonant is successively selected, increasing the possibility that two consonants can be recognized as one vowel. Therefore, both (the vowel ___(a) is automatically omitted or the user inputs the omission) can be allowed.

2.6 Myanmar

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

3. Multidimensional cross control processing method

2-2 is an example in which the alphabet in the "あ" column is used as the representative alphabet according to the table above and assigned to each button in alphabetical order. In the case of the previous application, 4nd and 5rd controls could be additionally assigned to the control buttons assigned to the 2nd and 3rd controls, but in this case, only the 2nd and 3rd controls were allocated to minimize the number of input strokes and to make the most of the control buttons. see.

In Fig. 2-2, the method of entering the subsequent alphabet is as suggested in the previous application. For example, when applying input after control, it becomes い = あ+[*]. Next, we will show you how to input the long sound, sound sound, and half sound sound, which are variations of each alphabet. In Fig. 2-2, all the buttons ([*] button, [#] button) available as control buttons are being 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, the subsequent control button that has not been used as an inner control button after inputting the subsequent alphabet is used as a modified alphabet control button (this is called the "opposite control button"). I can.

For example, ぃ = い + "opposite side control button" = あ+[*] + [#], ご = こ + "opposite side control button" = か+[#]+[#] + [*] do. This can be seen as using the opposite control button, which is not used as a subsequent control button, as a modified alphabet control button 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, it can be seen that by pressing the opposite control button once, the "next control" is selected to input the modified alphabet (GO in the example) of the previously entered alphabet (こ in the example). I can.

In the alphabet of the row'ha', there are two types of transformed alphabets, sonic and semi-voiced, so you can press the control button on the opposite side once for long notes and the other control twice for semi-voiced notes. That is, ぶ = ふ + "opposite control button" = は+[*]+[*] + [#],ぷ = ふ + "press the opposite control button twice" = は+[*]+[*] + [# It becomes like ]+[#].

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

For example, if you use the [*] button to enter a variant of the representative alphabet (long sound, sound sound, half sound sound), it becomes あ = あ+[*]+[*]+[*]. In other words, the transformed alphabet (long sound, sound sound, half sound sound) of the representative alphabet is regarded as the 4th successor alphabet that can be entered using the [*] button. In summary, it becomes as follows.

In this way, using the opposite control button to expand the use of the control button and to use it for more alphabets or other inputs is called "cross control processing method" or "zigzag control processing method" or "multidimensional cross control processing method" for convenience. Call. This can also be applied when three or more buttons are used as control buttons.

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

That is, 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 transformed alphabet of こ, and ご = こ + "opposite control button" = か+[#]+[#] + [*], and the opposite control button is already a representative alphabet. Although it was defined as a control button for entering the inner alphabets き and く after 1st and 2nd of か, the opposite control button ([*] button) is like a modified alphabet control button for entering the transformed alphabet ご of こ. It can be utilized. This can be seen as using two control buttons in a "two-dimensional" way, as compared to using one control button in one dimension for inputting one alphabet.

ぷ = ふ + "Press the opposite control button 1 time" + "Press the opposite control button 1 time with respect to the previous control button" = は+[*]+[*] + [#]+[*] May be. In other words, if it is not possible to repeatedly use the control button ([#] button in the example) that was finally used for input of ぶ and input the modified alphabet again, use the opposite control button to the other control button in the same way. It is possible to enter a variant alphabet or a later alphabet. For convenience, this is called "three-dimensional cross control processing" or "three-stage cross control processing". This means that the number of possible inputs of alphabets or other alphabetic input-related items that can be input in the keypad can be infinitely expanded by using the cross control processing method. Moreover, it is of great significance that the subsequent or modified alphabets that are related to the pre-entered alphabet can be naturally input by the control processing method.

The above is illustrated in the form of a graph, for example, in the form of a graph, for example, of a row of Ha in which two modified alphabets (voiced sound and semi-voiced sound) exist. In Fig. 2-3, indicated by ".. ." in a circle with a gray color, as in the table above, which can be used to input other alphabets or symbols in the empty space, what you want to enter additionally if necessary ( It means that alphabets or symbols) can be entered by a multidimensional control processing method. In Fig. 2-3, the [*] button and the [#] button are used in a right angle direction, respectively.

In the earlier application, the 2nd, 3rd, 4th, 5th controls are assigned to the [*] button, which are not the representative alphabets, and the [*] button is used as a control button to input the modified alphabets such as long, sound, and semi-voiced sounds. Compared with the method used, it can be seen that the two-dimensional control process is applied to the method of the first application. In other words, ぃ = い+{transformation} = い +[*]+[#] because two control buttons are used. The difference is that in the elected source, the control button was used only as a follow-up control (2nd, 3rd, 4th, 5th) button and only as a modified alphabet (long tone, sound tone, half tone) control button, and the second-order control of the present invention. In the process, after inputting the subsequent alphabet, the subsequent control button was again used as the modified alphabet control button. In order to distinguish the use of the main purpose control button (following control button in the example) as a modified alphabet control button again from the two-dimensional control processing method of the previous application, for convenience, the "two-dimensional recycling control processing method" or the "two-dimensional multi-purpose control processing method" I will call it ".

The first application method has the advantage of being simple and consistent in the input method, but has the disadvantage of relatively increasing the number of input strokes. In order to easily show the difference from the present invention, a graph shows the case in which the control button was used only as a subsequent control button (2nd, 3rd, 4th, 5th) and a modified alphabet (long tone, sound tone, half tone) control button in the previous application. It is shown in Figure 2-4. Also in Figs. 2-3 and 2-4, the parts marked with a gray color can be expanded and applied.

In the application of the cross control processing method above, an example of the post-control input was shown. This is also the same as applying the control pre-input or the post-input control in the application of the control processing method in the previous application. You can also enter. For example, ぃ = "opposite control button" + い = [#] + [*]+あ. However, in applying the cross control processing method, it will be convenient to input the control afterwards.

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

4. How to input Korean

4.1. How to use vowel elements in Korean

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

In Korean, vowels can be divided into several vowel elements. For example, ㅡ, ., ㅣ can be divided into 3 vowel elements (for convenience, it is also simply called "3 vowels"), and 4 vowel elements of ㅡ, ., :, ㅣ (for convenience, simply "4 vowels") You can think of it by dividing it into (also called a), and among them, ㅡ, ㅣ exist as vowels themselves, so you can think of using vowel elements in the Korean input method on the keypad. Anyone who knows Korean can know that Korean vowels can be input by combining 3 vowel elements or 4 vowel elements in combination.

Hereinafter, it will be described in detail through examples.

4.1.1. 10-consonant 3-vowel method

First, as the basic alphabet for Korean input, the hard sound control and aspirated sound for input by the control processing method (input by a combination of basic consonants and controls) with 10 consonant plains (basic consonants) and 3 vowel elements You can think of 15 elements such as controls. Since this must be assigned and entered on a 3*4 keypad with 12 buttons, among the 10 basic consonants for 9 buttons, a basic consonant in which no hard or aspirated sound is present (for convenience, "9-button dropout" or "10-9 Consonants" or more simply called "-9 consonants"), and the remaining 9 basic consonants are assigned to 9 buttons, and each of the 3 vowel elements, aspirated sound control, hard sound control, and 9 dropout consonants are randomly selected. You can group them by 2 and assign them to the remaining 3 buttons. Basic consonants assigned to 9 buttons are input with 1 assigned button, vowel elements are input with 1 assigned button, control grouped with the vowel element "." or 9-button dropout consonants are input with 3 assigned buttons. can do. For convenience, this will be referred to as "aspirated/aspirated control processing 10-consonant 3-vowel method" or "hardened/aspirated control processing 3-vowel method". Here, the selection of the control grouped together with the vowel element "." or the selection of the 9-button drop-out consonants with 3 buttons assigned can be regarded as applying the repetitive selection method as described later.

Here, it is of course desirable that 10 basic consonants are assigned to each of the 10 numeric buttons in order to use the Korean keypad for memorization. Figures 4-5 show one such embodiment. In Fig. 4-5, "ㅎ" is grouped with a vowel element "." as a 9-button drop-off consonant, and assigned to the [0] button, which is a number button, which "ㅎ" does not exist, and is the most frequently used. This is because even if it is not possible to input with a single button assigned to it, it is less uncomfortable, and it is the last in the order, which can give the Koreans a natural feel. In Fig. 4-5, since the remaining basic consonants are also allocated to each number button in alphabetical order, there is an advantage of providing good location identification (readability) to the user.

When applying input after control ㅋ = ㄱ + {aspirated sound (control)} = [1]+[*]+[*], ㄲ = ㄱ + {hard sound (control)} = [1]+[#]+[# ]. In the applicant's earlier application, as in the case of Japanese, the vowels "ㅡ" and "ㅣ" in Korean do not appear consecutively, so that the aspirated control and the aspirated control can be selected as a repeat selection method. In the case of "ㅔ" or "ㅖ", the vowel "ㅣ" may appear consecutively, but the vowel element "." Since this precedes, the system knows that pressing "##" does not select a control, but enters a vowel. In the previous application, even if the control was not displayed on the button, the user only needs to be aware that the user can select the control by pressing the corresponding button. By grouping and assigning the aspirated control together with the vowel "-", the user intuitively provides the vowel " You can remember to select the aspirated control by pressing the button assigned with ㅡ" twice. Likewise, by assigning the horn control with the vowel "ㅣ", the user intuitively selects the button assigned with the vowel "ㅣ" twice. There is an advantage that it can be seen that pressing the horn control is selected, 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. It is obvious that this is not limited only to the embodiments presented by the applicant, and may be used equally in other applications, and this is also included in the scope of the applicant's invention. For convenience, this will be referred to as "acute sound/hard sound control method using line-shaped vowel elements ("ㅡ", "ㅣ") buttons".

In the example of Fig. 4-5, the vowel element "." is assigned to the [0] button, and the vowel element "." is implicitly placed in the number "0" (the red dot in the number "0"). can do. In the end, it is possible to construct a Korean language input system by concisely arranging only one alphabet on the keypad. Similarly, as shown in Fig. 4-9, it is composed of "ㅎ =. + ㅡ + ㅇ", and by displaying "." of "ㅎ" in red and externally assigning only one letter element, a concise keypad can be constructed.

In the 10-consonant 3-vowel method, the aspirated sound/hard sound control process can be entered by pressing the button assigned to the basic consonant of the aspirating sound twice (i.e., by the hidden repetition selection method), instead of entering only the aspirated sound by the control processing method. have. For convenience, this will be referred to as "acute sound repetition selection hard sound control processing 3 vowel method". Alternatively, it is not possible to input the hard sound only by the control processing method, but by pressing the button assigned the basic consonant of the hard sound twice (i.e., by the hidden repetition selection method) (this is a hard sound, that is, a combination of two consonants and basic consonants). You can also see it as typing). For convenience, this will be referred to as "hard sound repetition selection method of repetitive sound control processing". Alternatively, both aspirated sounds and hard sounds can be input by the repetitive selection method, rather than input by the control processing method. In the case of inputting both aspirated and hard sounds by the repetition selection method, the order of repetition selection can be made to be a basic consonant (1 stroke)-a hard sound (2 strokes)-a abbreviated sound (3 strokes), or It can be viewed as inputting a combination of basic consonants, and inputting a three-stroke button to which the basic consonant belongs), basic consonant (1 stroke)-aspirated sound (2 strokes)-hard sound (3 strokes). . For convenience, the former case will be referred to as "half attenuated repeated selection 3 vowel method", and the latter case will be referred to as "half aspirated repeated selection 3 vowel method". Some of the things described in this paragraph will be collectively referred to as "aspirated/hardened repeated selection tri-vowel method" for convenience.

In addition, while maintaining the 3-vowel method for aspirating/hard sound control processing, you can also apply the “3 vowel method for aspirating/hard sound repetition selection”. You can also apply While maintaining the three vowel method of aspirating/hard sound control processing, a repetitive selection method of only aspirated sound can be applied, or a repetition selection method of only hard sound can be applied, a repetition selection method of pre-tense sound can be applied, and the line Various combinations are possible, such as applying the aspirated repeat selection method. Conversely, while maintaining the 3-vowel method for aspirated / aspirated repetition, a control processing method of only aspirated sound can be applied, a control processing method of only hard sound can be applied, or a control method of both aspirating and aspirated sound can be applied. have. Alternatively, the hard sound can be input only by the control processing method, and the aspirating sound can be input only by the repetition selection method. Conversely, the aspirated sound is input only by the control processing method, and the hard sound is only input by the repeat selection method (i.e., a combination of basic consonants). You may. There may be more combinations similar to those described above, and this will be referred to as "aspirated/hard sound control processing repeated selection mixed 3-vowel method" for convenience. A case in which the input method of aspirated sound and hard sound is not specifically designated is generally referred to, and for convenience, it will be referred to as "10 consonant 3 vowel method". It is also possible to allow the user to set a convenient input method for inputting hard and aspirated sounds.

The frequency of ambiguity that occurs when applying the "Aspirated/Aspirated Repetition Selection 3 Vowel Method", which applies the repeat selection method to both aspirating and hard sound input, is about 140 characters in the form of one letter, and about 15 characters in the input system of Samsung Electronics. It occurs much less than that of the Hangul font. Whether inputted by a repetitive selection method of aspirated or hard sound, or input by a control processing method, an aspirated sound or hard sound may be additionally allocated and arranged to each number button, and this is also included in the scope of the present invention.

4.1.2. 10 consonants 4 vowels

4-5 and 4-9 can be solved and expressed as in FIG. 4-6. In Fig. 4-6, the same input method as in Fig. 4-5 can be applied. As shown in Fig. 4-6, this is a vowel element required when entering the Korean vowel "ㅕ" or "ㅛ", etc. It acts as a horizontal or vertical stroke depending on the case, but here, for convenience, horizontal stroke':' is displayed)" is grouped together with the vowel element "." and assigned to the same button, and vowel elements ".", ":" Each of the buttons assigned by the repeat selection method is selected as one stroke and two strokes, but it can be seen that the vowel element ":" is not explicitly placed on the button. Of course, as shown in Fig. 4-6, the result is the same even if the alphabet is explicitly assigned and the alphabet displayed on the keypad is selected by the repeat selection method. However, even if the vowel element ":" is not necessarily displayed on the button, the user intuitively inputs a combination of the vowel element "." (ie ":" = "." + "." = [0]+[0]). It can be thought of as doing. In the end, Fig. 4-5 also uses four vowel elements ("ㅡ", ".", ":", "ㅣ"), but one of the three vowel elements "aspirated control, horn control, and 9-button dropout sounds" Grouped together with ." and vowel element ":" and assigned to an arbitrary button, and 9-button drop-out consonants (in the case of Fig. 4-5) assigned together with "." and ":" are each repeated by the method However, it can be seen that the vowel element ":" is not displayed on the button. This is the same result as the above-described "10 consonants 3 vowel method", but for convenience, "10 consonants dot vowel element repetition selection 3 vowel method" or "10 consonants point (點) vowel element repeat selection 4 vowel method" or "10 The consonant point (點) vowel element repeated selection vowel element method" is called. Hard and aspirated sounds can be input by various methods described above. In fact, the same result, but specially labeled with a separate name, shows that Fig. 4-5 also utilizes four vowel elements and applies the repetitive selection method, but the vowel element ":" can be viewed as not displaying only on the button. (Even if it is not displayed as shown 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 Hangul input system of Samsung Electronics has only three vowel elements. While it was an approach to use, the input system proposed by the applicant is intended 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 is grouped into different groups. That is, four vowel elements ("ㅡ", ".", ":", "ㅣ") are assigned to different buttons, and for convenience, it will be called "10 consonants 4 vowels" or "4 vowels". . Since the 4 vowel method has many connections with the 3 vowel method, it is explained relatively briefly, and it is obvious that the contents applicable to the 4 vowel method among the contents described in the 3 vowel method can be applied as it is in the 4 vowel method. The terms used in the triphonic method can be used similarly.

In the same way in the 4-vowel method, the remaining consonants are assigned to 8 buttons, except for 2 basic consonants that do not have a pronounced and hard sound among 10 basic consonants, and each of the 4 vowel elements, aspirated sound control, aspirated sound control, and 8 buttons Two consonants that are not assigned to (for convenience, called "8-button drop-off consonants" or "10-8 consonants" or more simply "-8 consonants") are grouped by 2, and the vowel element is input with one assigned button. , Control or dropping consonants assigned together can be input with two assigned buttons (ie, input by the repeat selection method).

Here too, 10 basic consonants can be assigned to each number button to enable use for memorization. In addition, by assigning the vowel element "." to the [0] button having a similar shape and displaying it inside the number "0", it is possible to make concise arrangement on the button (or omitting the display in the number, the shape is similar, 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 that only one alphabet can be placed per button. As shown in Fig. 4-7, when the buttons to which the vowels "ㅡ" and "ㅣ" are assigned are the [*] button and the [#] button, when inputting various vowels in Korean, the adjacent button is pressed to reduce the fingering distance. It works.

In the case of the 4-vowel method, the repetition selection method can be applied as in the case of the 3-vowel method in the input of the aspirated sound and the hard sound, and this is collectively referred to as "abbreviated/tense repeat selection 4-vowel method" for convenience. In addition, as in the case of the 3-vowel method, the repetitive selection method can be mixed and applied, and this is collectively referred to as "aspirated/hard-tone control processing repeated selection mixed 4-vowel method" for convenience.

The keypad of Fig. 4-7 can also be expressed as shown in Fig. 4-8 from the viewpoint of the repetitive selection method. When comparing FIGS. 4-6 and 4-8, the difference between FIGS. 4-5 and 4-7 can be clearly seen. Fig. 4-8 shows the same result as the vowel element ":" selected by the [0] button 2 strokes in Fig. 4-6 and inputted as 1 stroke by moving the [8] button (of course, the arrangement of the basic consonants is Fig. 4- 6 and Figs. 4-8 are slightly different, but this should be unified). In addition, the vowel element ":" consisting of two dots can be divided into the vowel element in the horizontal direction ":" and the vowel element in the vertical direction "..". If you name it, you can apply the five vowel elements ("ㅡ" , ".", ":", "..", "ㅣ") can be called "5 vowels". However, compared to the four vowel method of Figs. 4-7, there are few excellent points in terms of the number of strokes and recognition ability, and thus will not be mentioned in the present invention any more.

Vowel element "." And ":" may be assigned to the [*] button and the [#] button, but in this case, as shown in Fig. 4-7, the vowel element is displayed in the number, so that only one alphabet cannot be placed on the surface. .

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

As an example of input, in the case of "Wo" or "We", the dot-shaped vowel element ".." between the vowels "ㅡ" and "ㅣ" is entered as the vowel element ":". The system may temporarily recognize that "Yu + ..." has been entered, but the vowel "I" cannot appear after "Yu", so the system can recognize that "Woo" has been entered. In the case of "Wa" in "10 consonant dot vowel element repeated selection 3 vowel method", when entering a dot-shaped vowel element between "-" and "ㅣ", the vowel element "." is entered twice or the vowel element is entered twice. It can be understood as entering the element ":" once.

Some of the contents described above will be described again as follows. First, in entering Korean on the keypad by applying the repetition selection method, the method using 3 vowel elements (ㅡ, ., ㅣ) is 10 consonant flat notes, 3 vowel elements, and 2 controls (honor, abbreviated sound). ) A total of 15 elements are grouped and assigned in a 4*3 keypad to apply the repeat selection method, but by grouping "3 vowel elements" and "2 controls and 1 consonant flat sound (9-button dropout consonants)" It was assigned.

The method using 4 vowel elements (ㅡ, ., :, ㅣ) is a repeat selection method by grouping and allocating 10 consonant flat notes, 4 vowel elements, and a total of 16 elements for 2 controls in a 4*3 keypad. However, "4 vowel elements" and "2 controls and 2 consonants (8-button drop-out consonants)" are grouped and assigned respectively.

In both methods, for the natural use of simple codes (especially syllable-based initial codes), 10 consonant flat notes were considered to be assigned to 10 number buttons.

The three vowel method proposed by the applicant (collectively referred to as the various three vowel methods previously titled) and the four vowel method have almost no or no ambiguity even when the repetitive selection method is applied using various characteristics of a specific language (here, Korean). It suggested a way to enter it. This means that when entering the alphabet displayed on the keypad using the repeat selection method, especially in entering Korean, among the "Language Restriction Input Method" and the "Language Restriction Repetition Selection Method", the "Korean Restriction Repetitive Selection Method" It can be viewed as suggesting a Korean input method optimized for ".

In fact, as suggested by the applicant in the earlier application, in Korean, etc., when a pair of basic consonants and basic vowels are assigned to each button and the repeat selection method is applied, the appearance rules of Korean consonants and vowels (i.e., word generation rules, alphabet It is in the same context as showing that the ambiguity in the iterative selection method can be greatly reduced by using the combination rule). In Figs. 4-5 to 4-8 using 3 vowel elements or 4 vowel elements in Korean, Korean vowels (elements) "ㅡ" and "ㅣ" do not appear in succession, but appear in succession (example of a previous application) In "ㅖ"), it is understood from a similar point of view that the tense control and the aspirating control assigned together with the vowel element can be selected by the repetitive selection method using the property of knowing whether a vowel has been entered or a control has been entered. I can.

4.1.3. Complete control processing 3-vowel method/4 vowel method and dropping consonant assignment button use Complete control processing 3-vowel method/4 vowel method

In Fig. 4-5, ambiguity may occur in cases such as "Lee Heo <=> Ahi" and "I Heo <=> Ahe <=> Yahi" even if aspirated and hard tones are input by the control processing method (full code of both Since all values are the same). In the example, "ㅡ" is used instead of the vowel "ㅣ", and other similar cases will be recognized by anyone who knows Korean. However, many of these cases do not occur in actual words, and it can be effectively overcome by setting the "battery delay time" and "the breakout delay time" mentioned in the previous application. There may be a similar case in the four vowel method of Figs. 4-7. In Fig. 4-7, there is no case such as "Ahe <=> Yahi", but there may be a case such as "I and <=> Yami". However, this is not a lot of cases, and can be overcome through time delay. The number of occurrences can be investigated based on the frequency of use of actual Korean consonants and vowels, but since it is expected to occur in Korean characters in hundreds of letters, it can be seen that virtually no ambiguity occurs due to this.

Of course, as mentioned in the previous application, if the 9-button dropout sound ("ㅎ" in the example drawing) is regarded as a modified alphabet of "ㅇ" in the 3-vowel method as shown in Fig. 4-5, input is possible without ambiguity. It is possible. For example, ㅎ = ㅇ + {aspirated sound} = [8]+[*]+[*]. This will be referred to as "complete control processing 3 vowel method" for convenience. Similarly, in the 4 vowel method similar to 5, the 8-button drop-out consonants ("ㅎ" and "ㅁ" in the example drawing) are controlled by the control processing method (for example, "ㅁ" is replaced with "b" as a modified alphabet. As a result, "ㅎ" is regarded as a variant of "ㅇ") You can enter without ambiguity. For convenience, it could be called "complete control processing 4 vowels".

However, inputting the 9 button / 8 button dropout consonants according to the complete control process 3 vowel method / 4 vowel method hinders the naturalness in relation to the use of simple codes. Therefore, in the present invention, it is proposed to input the 9-button drop-out consonant ("ㅎ" in the example) in the 3-vowel method as a combination of a button and a control to which the corresponding alphabet is assigned (applies only to the case of input after control, and an example description). For example, in the 3-vowel method in Fig. 4-5, ㅎ =. + {Aspirated sound} = [0]+[*]+[*]. This is like a vowel element "." in which the 9-button drop-out consonant is input by one button assigned to the alphabet. It is entered like a variant of the alphabet. This method can also completely remove ambiguity, and by using the [0] button for the input of "ㅎ", it is possible to maintain the naturalness in the use of simple codes. For convenience, this will be referred to as "complete control processing 3-vowel method using the dropping consonant allocation button". The same can be applied to the four vowel method. If this method is applied, when the first letter of "ㅎ" ends with a letter with a seed sound (ex. "each") and then "ㅎ" is entered, it can be temporarily recognized as "go+-o". 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 aspirated control. Therefore, the system can recognize that ".+ㅡ+ㅡ" has entered "ㅎ". If the initial letter ends with a vowel that can be combined with the vowel element "." without a seed sound (eg "ㅣ", "ㅡ", "ㅏ", "ㅜ", etc.), the input to enter "ㅎ" In the value "0**", "0" is temporarily combined with the previous vowel, and the system can temporarily recognize that the vowel "ㅡ" +"ㅡ" has been entered, but the system is also the "**" input value. Since you can see that this control is selected and cannot be combined with the preceding vowel element ".", the system knows you have entered "ㅎ". A little further, if the character ends with a vowel that cannot be combined with the vowel element "." (eg, the remaining vowels excluding "ㅣ", "ㅏ", and "ㅜ"), press the [0] button. The system considers "ㅎ" as input and may display it to the user. Also, even if "**" is entered after [0], it can be considered as having entered "ㅎ" in the end.

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

4.2. Temporary language restriction release delay time

In the earlier application, it was said that "Battery Strike Delay Time" and "Battery Strike Delay Time" can be applied even when three or more letters are assigned to one button. For example, if the batter delay time is set to 0.1 seconds on a standard English keypad and the [2] button is pressed twice within 0.1 seconds, the system can regard it as inputting B.

Similarly, when the [2] button is pressed 3 times in succession (ie [2]+[2]+[2]), the first input value and the second input value (ie, the first [2] button and the second [2] button) If the delay time interval between the intervals is within the time set as the battered delay time (eg 0.1 seconds), and the delay time interval between the second input value and the third input value is within the time set as the battered delay time (eg 0.1 seconds) ( In other words, [2] + within 0.1 seconds + [2] + within 0.1 seconds + [2]), C is entered so that the system recognizes it. Or, when the [2] button is pressed three times in a row (ie, [2]+[2]+[2]), if the total input time is within twice the multi-stroke delay time (eg 0.2 seconds), enter C. You can also make the system aware of it.

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

Battered Strike Delay Time ≤ Altruism Delay Time ≤ Temporary Language Restriction Release Delay Time

All three delay times may be set the same, but it would be desirable to set the altruism delay time longer than the battering delay time, and the temporary language restriction release delay time longer than the altruism delay time.

4.3. Correspondence between client system and server system

In the earlier application (application in 2000 through claiming priority), it was said that the alphabet input program on the keypad can be installed on the terminal (client) side or on the server side. When installed on the server side, the client side transmits the numeric input value to the server side, and the server side interprets the input value. 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 also be applied to all character input methods of the applicant.

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

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

In addition, a separate button may be used, but a phase movement button, a high movement button, or a left movement button that is not frequently used in the character input mode may be used.

4.5. Input of the Korean Gore alphabet

In the present invention, furthermore, a method for inputting Korean Gore through a keypad is proposed.

In Korean, old words (losing alphabets) that are rarely used in the modern age include vowels (indicated by "ㆍ"), consonants (indicated by triangle "ㅿ"), and soft hi-eop ("ㅎ") with no book dots. It is marked with "ㆆ"), old eung ("ㆁ" with a dot on top of "ㅇ"), and pure Kyung-eum ("ㅸ" with a circle under "ㅂ").

Among the archaic words, the vowel undera is often used in relatively modern languages. For example, it can be seen used in the company name "ㄱ.ㅁ.Goeul" and in the famous word processor "ㅎ.ㄴGul" made by Hangul and computer companies ("ㄱ.ㅁ.Goeul" in "ㄱ.ㅁ.Goeul"). "+." is one letter and "ㅁ+." is one letter, and "ㅎ+.+ㄴ" in "ㅎ.ㄴ" is one letter, but the JPO editor does not support it, so it is indicated as such). As in the example, since vowels are widely used in various trade names, they can be usefully used in inputting phonebooks, etc.

In the applicant's earlier application, since the vowel element "." has the same shape as the vowel element ".", if the vowel element "." is assigned to one tap to input the vowel element, the vowel element can be naturally input. Since no other vowels appear consecutively after the vowel, the input rule is unchanged (even if there is such a case, the vowel below the archetype is not often used, so it is sufficient that no other vowels appear consecutively after the vowel). . Of course, when the button to which the vowel element "." is assigned is pressed twice, the system recognizes that this is for inputting "ㅕ" or "ㅖ" rather than inputting the child under the vowel twice in succession. Likewise, if the vowel element "." is pressed twice in succession after the vowel "I", the system can recognize that the vowel "ㅑ" or the vowel "ㅒ" is input.

Consonants of Gore can also be entered as a variant of the basic consonant (plain consonant). For example, the half-chief "ㅿ" is regarded as a variant alphabet of "ㅅ" (eg aphrodisiac), and the soft hyep "ㆆ" is regarded as a modified alphabet of "ㅇ" (eg abbreviated sound or hard sound), and the old answer "ㆁ" Can be regarded as a modified alphabet of "ㅇ" (abbreviated or hard sound) and entered. In the case of "ㅸ", it is also possible to define the input method (eg, automata processing that enables a combination of "ㅂ" and "ㅇ"), but it is an alphabet that is not actually used in modern Korean and is a variant of "ㅂ". Since both the hard sound "ㅃ" and the abbreviated sound "ㅍ" exist, the present invention does not refer to it in detail any more.

However, for one example, you could enter "ㅸ = ㅂ+**** = 6****" or "ㅸ = ㅂ+#### = 6####". As mentioned in the input of various symbols, a valid alphabet is input by repeatedly using the control button, but it is the same as entering various symbols by repeatedly pressing the control button. "6*** = F", but "6****" can be used to enter gore (gore as a variant of "ㅂ"). Likewise, by repeatedly using the control buttons (here, the vowels "ㅡ", "ㅣ" assigned [*], [#] buttons), various symbols can be entered.

The input of Gore's consonants can be applied equally to the applicant's other earlier applications. However, in the method of using the vowel elements (ㅡ, ., ㅣ) among the applicant's earlier applications, there is an advantage that the vowel elements can be entered naturally and easily.

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

4.6. Characteristics when applying parallel input method

In the previous application, "shortened/full parallel input method" or simply "parallel input method" was described. This means that, for example, when applying the parallel input method in which the full input method is the default input mode, the system checks the input value every time each input value is input, 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 treats the input value as a simple code (this is referred to as "full priority parallel input method" for convenience). Or, conversely, when applying the parallel input method in which the shortened input method is the default input mode, the system examines the input value every time each 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 did not, the system considered the input value as a full code and processed it (this is referred to as "shortened priority parallel input method" for convenience).

It was explained that when the "Partial All Selection Method" is used as the full input method, the moment the input value violates the full code generation rule in the full priority parallel input method, it is possible to treat the input value as a short code and process it easily.

When applying the iterative selection method 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 restriction repetitive selection method as a full input method, the system can treat the input value as a short code at the moment the input value violates the word generation rule of a specific language.

In the method using the three vowel elements (ㅡ, ., ㅣ) in Korean (the example in Fig. 4-5), the syllable-based initial code is used as a short code (that is, the index used for the simple code to be searched) Simple code means syllable-based initial code) When applying the full-priority parallel input method, when "12~" is entered as the input value, the moment the second input value "2" is input, the input value forms a Korean syllable (character). 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 inputs a simple code (syllable-based initial code) in a form similar to Fig. 4-5 when applying the full-first parallel input method, in most cases, the second input value There is a good characteristic of knowing that the input value is a simple code at the moment of input.

This is also in the same context as the system treats the input value as a simple code (short code) as soon as the input value violates the word generation rule of Korean in the Korean restricted input method using the three vowel elements of Korean. When "100~" is entered as the input value in Fig. 4-5 using the three vowel elements of Korean (full priority parallel input method), the system uses "ㄱ+" in order for the user to input "Kyo" or "Kyo". .." is recognized as being input and can be output, but if the 4th input value is the vowel element "ㅡ" or "ㅣ" is not entered and the numeric button is pressed, the input value cannot achieve the full code. At that moment, the input value can be recognized as a simple code (short code), and a phrase corresponding to the input value can be output (visual or aural means) by referring to the simple code index. In the end, in a form similar to that of Fig. 4-5, when the maximum 4th input value is input when applying the full-priority parallel input method, the system can know whether the input value is a full code or a simple code. city).

Similarly, in Fig. 4-7 using four vowel elements (ㅡ, ., :, ㅣ), when applying the full-priority parallel input method, when the user inputs "18~", the system is "go" or "go" In order to input "ㄱ+.", it can be recognized as being input and output, but when a number button (corresponding to a consonant) is input as the third input value, the input value cannot achieve a full code. The system can process the input value by considering it as a simple code. When a maximum of 3 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 a four vowel method for acute/aspirated control processing).

In Figs. 4-5 and 4-7, the basic consonant (consonant flat tone) is assigned different number buttons, but Figs. 4-5 and 4-7 are only examples, so the arrangement of the consonant flat tone should be kept the same. I can. In Fig. 4-5, "ㅎ" is implicitly assigned to the [0] button, and in Fig. 4-7, the vowel element "." is implicitly assigned to the number "0", but it was pointed out that this is also the same. . For convenience, the input method using 3 vowel elements similar to Fig. 4-5 is called "3 vowel Korean input method (more simply, 3 vowel method or 3 vowel method)", and similar to Fig. 4-7, "4 The input method using the vowel element will be called "4 vowel Korean input method (more simply 4 vowel method or 4 vowel method)".

4.7. Compatibility between 3-vowel keypad and 4-vowel 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 from the keypad of Fig. 4-5 and the keypad of Fig. 4-7, the basic consonant arrangement of both can be the same. Therefore, in this case, the 10-consonant 3-vowel method is used in the same keypad. (Ex. the method described in Fig. 4-5) or the 10-consonant 4 vowel sound method (eg, the method described in Fig. 4-7), a good characteristic that allows the user to select and use a method convenient for them ). Furthermore, in the "memory" keypad in which Korean consonant flat tones are assigned to each number button, the user can use the 10-consonant 3 vowel method or the 10 consonant 4 vowel method. Here, a user who is familiar with the 3 vowel method or the 4 vowel method will be able to use the simple code and input Korean using the 3 vowel method or the 4 vowel method even on a keypad where the consonant flat sound is not displayed on the keypad. The use of simple codes on a keypad that displays only numbers or a keypad that displays only consonants on 10 numeric buttons for memorization, and the use of 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. Input of dropping consonants

When applying the complete control processing method as a method of entering the missing consonant "ㅎ" in the 3-vowel method in the previous application (applying input after control), input it without ambiguity as "ㅎ = 0** = .ㅡㅡ = ㅗㅡ" I said I could. In addition, it was improved that it was possible to input the drop-off consonant "ㅎ" at the beginning of a word with one stroke of the [0] button (since the vowel element'.' does not appear at the beginning of the word). In addition, the "." followed by a vowel that cannot be combined (that is, vowels excluding'ㅡ','ㅣ','ㅏ', and'ㅜ', which are the vowel elements'.' can combine) He said that it can be entered with one stroke of the [0] button.

When inputting "ㅎ" with 3 strokes of the [0] button, the vowel element "." It was pointed out that ambiguity may occur as described in the case where "ㅎ" follows this combinable vowel ('.joinable vowel'), as described above. In order to input without it, 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 enter "0**" rather than "0*" for regularity of the input method. Here, when entering the drop-out consonant "ㅎ", when applying the repeat selection method by using the button assigned to the drop-out consonant, among the cases where "ㅎ" is followed by ".combinable vowels", "." is followed by "ㅎ". It can be seen that ambiguity can arise only in special cases. Conversely, if "ㅎ" is followed by a consonant, you can enter "ㅎ" without ambiguity with 3 strokes of the [0] button. That is, if you enter "ㅎ" after the consonant, you can enter "ㅎ" without ambiguity even if you apply either method of "0**" or "000".

Here, if "ㅎ" comes after ".combinable vowels", it can be seen that input is possible as "0*". (If'ㅎ' is followed by a non-combinable vowel, it is possible to input it with one stroke of the [0] button) This is because there is no case where ".+ㅡ" is combined after ".combinable vowel" in Korean.

In summary, in order to make the input of the missing consonant "ㅎ" as convenient as possible, when "ㅎ" appears at the beginning of the word and after the ". uncombinable vowels", input the missing consonant with one stroke of the assigned button, and " The "ㅎ" after the concatenation can be entered as "0*" or "0**", and when "ㅎ" appears after the consonant, it can be entered as "000".

Of course, you can always enter "ㅎ = 0**" for the regularity of the input method. At this time, it is possible to coexist with the input method of "ㅎ" summarized above. For example, "0 = ㅎ" at the beginning of a word, next, when "*" is pressed, it becomes "0* = ha", and when "*" is pressed again, "0** = ㅎ" It becomes. Here, if "*" is pressed again, it becomes "0*** = ha", and when "*" is pressed again, it becomes "0**** = haha".

Similarly, if you press "0*" to enter "ㅎ" after ".combinable vowels", and then "*" is pressed again, it becomes "0** = ㅎ" (the same input method is '0 ** = ㅎ'), if "*" is pressed again, it may become "0*** = ha".

It is obvious that the above can be applied equally to the case of using three Korean vowels (eg, "ㅡ", "ㅏ", and "ㅣ") to be described later, and the following is also the same. Also, inputting as "ㅎ = .+ㅡ+ㅡ = 0**" consists of the shape of "ㅎ = ㅗ+ㅇ", and it is said that you can enter it as if you were writing "ㅎ". Furthermore "." Even if you enter "ㅎ" after entering a vowel that can be combined with ("ㅏ" when using 3 vowels in Korean), for the consistency of the input rule, enter "ㅎ = .+ㅡ+ㅡ" for consistency. It can be done", but for the convenience of the user, when ".+ㅡ" is entered, it can be displayed as "ㅗ". This is called "heojungㅗ input" for convenience. For example, Figure 4-* As a standard, when input from "Gee = 1#0**#" to "1#0", "A" is displayed, and when "*" is input again, it becomes "Ga-", but the above mentioned "ㅎ" If you apply "Middle Input", when "1#0*" is entered, "Gi" is displayed, and when "*" is pressed once more, "Giha ('ㅎ' in unicode is the base, and in KSC5601 'ㅎ' becomes the first consonant of the next letter)", and when "#" is pressed further, it becomes "gigi." The difference is that vowels ending with "." ("ㅏ" etc. when using 3 vowels). When "ㅡ" is entered after input, "ㅡ" and "." entered immediately before "ㅡ" are recognized and processed as single letter vowels "ㅗ". "1#0* = Giㅗ" is entered and Then, when the delete button is pressed, it can be set to "A", which is the state of "1#0". This is the same as entering "ㅎ = .+ㅡ+ㅡ", only the form displayed in the middle of the input is different in a special case. .

To summarize the above information more generally, it is defined as inputting in combination with "ㅗ = X+Y" in a specific input method, and "X" entered after entering a series of vowels is the promise of the input method. When a specific character element (vowel) is formed, and then successively input "Y" does not achieve the promised specific vowel, the final input "X+Y" is recognized and processed as a single character vowel "ㅗ". "X" may be a vowel element "." as illustrated, or "ㅏ", "ㅓ", "ㅜ", ..., etc., as in the method using three Korean vowels to be described later. , "Y" can be "ㅡ".

From the above result, it can be seen that if "ㅡ" is input after the single letter "ㅗ" is input, "ㅗ+ㅡ" is processed as "ㅎ". In other words, inputting "ㅎ" using the [0] button assigned "ㅎ" at the beginning of the word is not applied, but after entering "ㅗ" with "0*" in the word start state, "ㅡ (= If *)" is entered, "0**" is recognized as "ㅎ" and can be processed. Here, if the single vowel "ㅗ" is input and then "ㅇ" is input, "ㅗ (single vowel) +ㅇ" can be recognized as "ㅎ" and processed. Again, since "ㅗㅇ" is not a normal Hangul character, the combination of "ㅗㅇ" is treated as "ㅎ". However, as in words such as "study", if "ㅗ" is not a single vowel, "ㅗ+ㅇ" does not become "ㅎ". In the case of "Kihi" as exemplified above, "1#0* = Kiㅗ", so if "ㅇ (= 8)" is entered in succession, "kiha ('ㅎ' in unicode is the base, and in KSC5601, 'ㅎ' becomes the first consonant of the next letter)", and if "ㅣ (= #)" is entered again, it can be recognized and processed as "gigi". In the example, the input of "ㅎ" was heard, but you can enter any grapheme by the above means. However, it would be natural to enter "ㅎ" which is geometrically related.

The three vowel method was mainly described above, but the same can be applied to the input of the dropped consonant in the four vowel method. In Fig. 4-7 and Fig. 4-8, when inputting "ㅁ" assigned with ".." to button [8], when the missing consonant "ㅁ" appears at the beginning of the word, the corresponding button [1] When "ㅁ" is followed by a vowel that cannot be combined with the vowel element ".." allocated together (ie vowels and vowel elements excluding vowels'ㅡ' and'ㅣ'), [8] button 1 tarot You can type. Likewise, if a consonant is followed by a dropped consonant "ㅁ", you can enter "ㅁ" without ambiguity with the corresponding button 2 strokes. In addition, if the drop-off consonant "ㅁ" is followed by a vowel to which the vowel elements assigned together can be combined, it can be entered as "8*". Of course, even in the case of the 4 vowel method, when entering the missing consonant, the application of the complete control processing method by simply using the button for assigning the missing consonant and the application of the control processing method that regards the missing consonant as a transformed alphabet (abbreviated or hard) of other basic consonants It is possible.

In addition, in the input of symbols, it is possible to apply a control processing method using basic consonants in which no aspirated/hardened sounds exist.

4.9. Input example of symbols

For the input of symbols, as much as possible, a combination of buttons assigned with basic consonants without aspirated/acryonic sounds and buttons for vowel elements (especially “ㅡ” and “ㅣ” buttons that can be used like control buttons) is used to input them. It will be convenient. In other words, it can be seen as applying the input method of aspirated sound/hard sound.

For example, based on Fig. 4-5, various symbols can be entered as follows, and the following contents are already presented in the previous application, and not only in the character input method presented 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**: Easily reminiscent of "N = 2*..." in "Exclamation mark"

▶ Slash (/) = 2##: Easily associated with "I = 2#..." in "Divide"

▶ Tilde (~) = 4**: Reminiscent of wave shape in the shape of "ㄹ" and "le" pronunciation

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

▶ Question mark (?) = 5**: Easily reminiscent of "water = 5*..." in "question mark"

▶ Period (.) = 5##: Easily reminiscent of "Ma = 5#..." of "Period"

▶ Comma (,) = 5###: Enter "period" and press "#" once more

▶ Colon (:) = 5####: Enter "comma" and press "#" once more

▶ Semicolon (:) = 5#####: Enter "colon" and press "#" once more

If the character input system does not use the [*] button or the [#] button as a vowel button, an exclamation point can be entered by combining a button assigned with "b" and a control button (eg [*] button). will be. In the input system where the [*] button or the [#] button is used as a control button rather than a vowel button, even in a system that is used as a control button, repeatedly press the button assigned "b" and the control button, as explained in pure sound input. In combination, you will be able to enter an exclamation point. For example, if you enter a modern language that takes precedence over gore, and the button assigned with "b" and any control button (eg [*] button) are pressed up to 2 times, enter "exclamation point = ㄴ+***" 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 enter the vowel "ㅣ" after the period, make sure that a certain amount of time (eg, as long as the language restriction release delay time) elapses after entering the period (.), and after confirming the period, enter "ㅣ" or a period. After inputting (.), after confirming the period by pressing a specific button (eg, right arrow or'space+delete'), you will be able to enter ".ㅣ" by entering the vowel "ㅣ". This is the same for the input of the previously described Gore Hangul.

It is obvious that other symbols other than the exclamation mark above can be applied similarly to other input systems (combination of buttons and control buttons assigned with consonant Korean consonants), and input of various other symbols in the extension of the above. This is possible.

In the above, a symbol input case optimized for the Hangul input method presented in the present invention is shown. That is, as much as possible, various symbols were entered using consonant buttons and vowel buttons (buttons assigned with vowels "ㅡ" and "ㅣ") that do not exist. However, as it has already been shown to input pure tense "ㅸ = 6****" or "ㅸ = 6####", even if you use the consonant button with aspirated/honored sound, you can use the old alphabet or various symbols. You can enter.

As in the case of The Anaga 10 and 11 below, even when the vowel button is repeatedly pressed and various vowels are selected/input, symbols, etc. can be entered. For example, in Fig. 4-5, when a [*] button assigned with a vowel "ㅡ" is selected as "ㅡ" for one stroke, "TT" as a second stroke, and "ㅠ" as a third stroke (ie, vowel If it is selected in the order of "ㅡ", "TT", and "ㅠ" according to the number of times the button is repeatedly pressed), it becomes "5*** = Mu".

In general, in the method of selecting a specific grapheme according to the repeated pressing of a specific button, the "maximum possible number of repetitions" (eg, when the [*] button is pressed 3 times) becomes the first state (ie, "-" is pressed once again). In many cases, the selected state is cycled, that is, "5**** = M." This is mainly taken into account when a typo is used to press more than the desired number of times. It is usually enough to use the delete function of the input value unit suggested in the previous application) or "5**** = 5*** + * = mu-", but it is usually the case that the pure sound "ㅸ" As shown in the input, the system detects that an alphabet (vowel) that cannot be combined is input, so that the entire input value can be recognized as one specific alphabet (eg, corresponding trellis, archaic or specific symbols).

In other words, in this case (vowels are selected in the order of "ㅡ", "ㅜ", "ㅠ" according to the number of times the button is repeatedly pressed-Here, 3 vowels are actually displayed on the [*] button and some vowels (Ex. Includes all cases where only the vowel "ㅡ") is displayed), which can be entered as "question mark (?) = 5****". When the [*] button is pressed consecutively after "5****", a period (.) is entered in the example above and then [#] is pressed next, a series of symbols (in the example above, , Comma (,), colon (:), semicolon (;), etc., in a broad sense, various alphabets) can be recognized as promised symbols. Therefore, as an example that is not a symbol, it may be entered as a lattice sound "ㅋ = 1****" and "key = 1*****".

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

If the button assigned to the vowel "ㅡ" is used only as an input for "ㅡ", the maximum possible repetition number of the vowel "ㅡ" after the consonant is 1, so enter "question mark (?) = 5**" This can be seen as possible. By expanding this, various symbols can be entered even when the maximum possible repetition number is more than one (3 times in the example above). 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, when three vowels such as "ㅡ", "ㅜ", and "ㅠ" are input by repeatedly pressing the [*] button assigned with "ㅡ", "5**** = ?" Without "**** =?" By using, you can recognize a specific alphabet (eg symbol). However, this is not a good method because only one symbol and the promised symbols when the [*] button is pressed consecutively can be entered using the [*] button. In the case of recognizing a combination with a consonant button, not only the combination with the [5] button in the example, but also a combination with another button (eg, a number button assigned to a consonant) 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 strokes.

As mentioned in the previous application by the applicant, it can be seen that the button assigned to the vowel is used like a control button, and the control button may be input beforehand or after input according to the input rules. In other words, it can be entered as "question mark (?) = 5**" or "**5". For example, if "**5" is entered after "A" is entered, the moment the last "ㅁ" is entered in "A+ㅡ+ㅡ+ㅁ", the system recognizes the input value as "A?" do. If "**5" is input after "gamma", the moment the last "ㅁ" is input in "Game-ㅁ", the last input "5**" is detected and the input value can be recognized as "reduction?" have. The same goes for the rest.

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

This can be applied not only to alphabets (including symbols) but also to input of various functions. When applied to the input of a function, as shown in the "multidimensional cross control processing method" of the applicant's previous application (when entering the alphabet by the N-dimensional cross control processing method, the function is entered by a cross combination of N+1 control buttons) , It is preferable 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 made last. (E.g. 5**** = question mark (?), 5***** = exclamation mark (!), 5****** = enter function activated)

If "5***** = Activate the Enter function" and "5****** = Exclamation mark (!)", the Enter function is activated by "5*****" and then [*] When the button is pressed, the system disables (cancels) the executed enter function and interprets the entire input value "5******" as an exclamation point (!) because it is unnatural in implementation and confusing to the user. to be. This means that when a vowel button used as a control button is used up to N times when entering various alphabets (including symbols), it is desirable to enter the function by repeatedly pressing more than that (ie, N+1 times). to be.

4.10. Input of arbitrary vowels (eg vowel "ㅏ") using vowel element "."

It has been shown that it is possible to naturally input the old word "Daeah" by using the vowel element ".". The vowel element "." is similar to the lower child in shape, so it can give the user a sense of friendliness. When inputting the lower word as a vowel element ".", the vowel combination start (eg, after consonant input) in the vowel combination process (ie, vowel processing) and the vowel combination end (eg, the next consonant input or blank, etc.) can be given. If only the [0] button is pressed between activation of an existing function), it is processed as a lower arrow.

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

For example, "105 = ㄱ +. + ㅁ" would be a single letter with a vowel under a child. When "1" is pressed to recognize a consonant and then "0" is pressed, the system first recognizes the beginning of the vowel combining process. For the input value "10~", the system says "ㄱ+." It can be recognized as (the process of entering "Geo", "Gyo", "Go", or "Kyo"). However, if you recognize that "5" is pressed and the consonant processing process starts and the vowel combination process ends, the input value "0" can be processed as a lower row. That is, for the input value "105", it is recognized as "ㄱ => ㄱ+. => ㄱ+.+ㅁ". Here, the "+" sign is used to mean that it appears as a single letter with the archaic suba (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 in modern times. Express Korean vowels. Here, it is shown that the vowel element "." can be used to input a single vowel frequently used in modern language (eg "ㅏ"), rather than inputting a hawa, which is rarely used in modern Korean.

When entering a single vowel in modern Korean using the [0] button assigned with the vowel element ".", it is recommended to input the modern Korean vowel "ㅏ", which is the most frequently used and has a similar pronunciation (virtually the same) It would be desirable.

Entering the vowel "ㅏ" with the button assigned with the vowel element "." is similar to inputting the lower child with the button assigned with the vowel element ".". For example, when "1" is pressed when entering "105", the system recognizes it as a consonant "ㄱ", and when the next "0" is pressed, the system will first ('0**' or '000' When input, consonant processing is performed.) Vowel combination process is performed. Similarly for input "10", the system will say "ㄱ+." ) It can be recognized as an intermediate step of entering "geo", "gyo", "go", or "gyo", but the next time the consonant input "5" is entered (or a blank space that can give the end of the vowel combination process) And activation of other functions), the system ends the vowel combination process, and can recognize the input value "0" as the promised vowel "k". That is, the input value "105" is recognized as "ㄱ => ㄱ+. => sense". Here, if another vowel (eg,'ㅣ') is input, it is obvious that the entire input value becomes "105# = Gami".

The exemplified process of "105 = persimmon" is actually the same as that of "a => group => ga => persimmon" for "1#05". When "5" is pressed after "1#0", the end of the vowel combination process is recognized and the input value "#0" is determined as the vowel "ㅏ". However, when inputting with "ㅏ = ㅣ+. = #0", the system outputs according to the input value is similar to the process of writing the vowel "ㅏ", so it only gives the user a sense of affinity.

It is true that inputting the vowel "ㅏ", which is often used as the vowel element ".", is less natural than entering the vowel elements "ㅣ" and "." sequentially. However, the vowel element "." It is not a problem because you can enter the vowel "ㅏ" with only one and at the same time enter "ㅏ" as a combination of "ㅣ" and "." (that is,'#0' in the drawing).

Here, the input of the gore lower child may be entered as "00". Likewise, for example, if "100" is pressed, the system will enter "gyo" or "gyo" in the process of "ㄱ+.+." Can be recognized as, but when the activation of a consonant or other function that can terminate the consonant or other vowel combination process is recognized without the vowel button that can be combined with the next input value, the system changes "100" to "a + down". Become aware. "1005" = "a + down ah + ㅁ" is recognized. Again, if there is little need for input under Gore, other vowels, such as the vowel "ㅓ", which are frequently used can be entered with two [0] buttons.

Depending on the user, the point of entering "ㅏ" instead of entering the vowel element "." may be less intuitive due to lack of intuition. For such a user, the user can input the vowel "ㅏ" with the [0] button 1 stroke and the [0] button 2 strokes. The processing procedure is the same as previously described, so it is omitted. In this case, it will be possible to input "ㅏ = ㅣ+. = #0" at the same time. Entering the vowel "ㅏ" with the [0] button 2 strokes (ie '00') assigned the vowel element "." is also more convenient than entering with "ㅣ+. = #0" in terms of input convenience. The degree is high.

The button to which the vowel element "." is assigned as suggested above ([0] button in the example drawing) is required to input "ㅏ" for one stroke or gore for one stroke and "ㅏ" for two strokes. You can set it according to your preference. Furthermore, it is possible to input a vowel other than "ㅏ", and this will also be set by the user.

The vowel "ㅏ" is a vowel that is overwhelmingly used in Korean, so it is preferable to input "ㅏ" rather than other vowels in order to be able to input arbitrary vowels used in modern language using the vowel element "." . The vowel "ㅏ" has a frequency of about 22% of all Korean vowels. In addition, if the frequency of use is in the order of "ㅏ", "ㅣ", "ㅡ", these three vowels are about 50% of the total frequency of use of Korean. That is, by allowing you to enter "ㅏ" as the vowel element ".", it means that about half of the vowels actually used can be entered with one specific button.

Although described above based on the 3-vowel method, the same can be applied to the 4-vowel method. That is, the vowel element "." in the vowel combining process (vowel combining start ~ vowel combining end) in Figs. 4-7 and 4-8. If only is recognized, it can be treated as a promised vowel (eg'ㅏ'), and if the vowel element ".." is recognized (ie, press the [8] button), it is another promised single vowel (eg, below or below). It can be processed with'ㅓ'). In addition, it can be applied to the input system using vowel elements currently used in Korea.

Since it was said that the vowel combining process means from the beginning of the vowel combination to the end of the vowel combination, other vowels cannot be combined in addition to this vowel input. It means that you cannot enter "dog" by entering the vowel "A" with "10" and then combining the vowel element "ㅣ" here again. "10#" becomes "ㅓ" because the vowel combination process starts when "0" is entered and the vowel combination process continues when "#" is pressed. In other words, the above description can be applied only to the vowel input that is used alone, not the vowel that changes by combining additional vowel elements (eg, "Gam" to the vowel "ㅏ" or "A+word end". In "ㅏ").

Here, among the vowel elements, the vowel element "." that does not originally exist as a vowel alone is a vowel element and exists as a vowel alone, but additionally, a vowel (eg, a vowel by itself) that can be combined with a vowel element (or yaw sound). Vowels that can be changed by combining additional vowel elements such as "ㅏ", "ㅑ" ... as a vowel created by combining "ㅡ", "ㅣ" and vowel elements existing as "elementary collection" It is called Here, "ㅡ" and "ㅣ" are both vowel elements and element vowels.

In the above, vowels are input using the Korean vowel elements "ㅡ", ".", and "ㅣ", but for the input of the [.] button that starts the vowel combination, it is processed with "ㅏ" and the [.] button. It has been described that the two times of pressing are treated with "ㅓ". Since the Korean keypad in the present invention has compatibility, the content applied in vowel input using the three vowels (eg, "ㅏ", "ㅣ", "ㅡ") of modern Korean in the following (4.11) can be additionally applied. I can. That is, "ㅘ = .+ㅡ+." As a result, it can be entered as "ㅙ = .+ㅡ+.+ㅣ", "ㅝ = ㅡ+.+.+.", and "ㅞ = ㅡ+.+.+.+ㅣ".

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

The most frequently used vowels in Korean are said to be three vowels in the order of "ㅏ", "ㅣ", "ㅡ". In particular, the vowel "ㅏ" 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 "ㅏ") is shown. As shown in the previous application, 10 flat consonants in Korean and 13 alphabets of 3 vowels "ㅏ", "ㅣ", "ㅡ" are used as basic alphabets, so in a keypad equipped with 12 buttons, one consonant per button. And one vowel. However, apart from this example, the combination of vowels presented below is processed in different cases (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 be applied in the same way. It is obvious that the contents mentioned in the other chapters of the present application below are applicable to the following as well.

In consideration of the invention in the previous application, FIGS. 4-10 and 4-11 are examples in which the vowel "ㅏ" and the consonant "ㅎ" are provided in one button. In Fig. 4-10, in order to keep the keypad concisely, the vowel "ㅏ" is displayed in the number "0" of the [0] button, and has the same meaning as in Fig. 4-11. In the example of Fig. 4-10, the vowels "ㅡ", "ㅏ", and "I" may be selected/input by the [*] button, the [0] button, and the [#] button, respectively. Of course, this is only an example, and it is easy to see that it can be transformed. For convenience, the [*] button is the [*] button or the vowel "ㅡ" button, the [0] button is the [0] button or the vowel "ㅏ" button, the [#] button is the [#] button or the collection "ㅣ" button. I will call it. In particular, the [0] button with the consonant "ㅎ" assigned together will be called the "ㅎ" button in some cases.

In the following, in Figs. 4-10 and 4-11, the [0] button is primarily applied as the "ㅏ" button, so the consonant ("ㅎ" in the example drawing) is not assigned to the button to which "ㅏ" is assigned. If not, it is the same. It can also be applied when consonants are assigned to the rest of the vowel buttons or when assigned with a random control. However, the input of the consonant assigned together with the vowels "ㅡ" and "ㅣ" should not affect the input of the vowel ("ㅋ = ㄱ+ㅡ+ㅡ = 1**" is "consonant+ㅡ" Next, the vowel "ㅡ" is a property that does not appear in succession and does not consequently affect the input of the vowel-the property that is treated as "deterministic" as mentioned).

Table 1 shows an example of inputting the remaining vowels by using the three vowels presented in the present invention.

For the contents of Table 1, input Korean vowels using the three vowel elements "ㅡ", ".", and "ㅣ", and "." It is the same as entering the vowel "ㅏ" with 1 stroke assigned to the button. In Table 1, for example, it is defined as "ㅜ = ㅡ+ㅏ", which in Korean uses the property that the vowel "ㅏ" does not appear consecutively after the vowel "ㅡ", and the total input value ("ㅡ+ㅏ You can think of ") as the vowel "ㅜ" as defining the system to recognize. In the case of the vowel "ㅐ", it is decomposed into "ㅏ" and "ㅣ", so it may be natural to enter "0#", but since it is defined as the vowel "ㅓ = 0#", "ㅐ = #0# It is defined to be entered as ". It is also possible to think similarly to defining combinations for the rest of the vowels. According to the definition in Table 1, 21 vowels in Korean can be entered without ambiguity.

When a vowel processing process (that is, a vowel combination process) is started by recognizing that one of the vowel buttons in Table 1 is pressed, when a corresponding input value among the input values in Table 1 is detected, the system prompts the user to identify the vowel. do. For example, in Fig. 4-10, after one of the consonant buttons [1] to [9] is pressed, or after a consonant input 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 vowel button and subsequent By detecting the input of a series of input values (vowel button), it is possible to identify the vowel corresponding to the corresponding input value according to Table 1.

However, in the case of a vowel marked with a circle in Table 1 as to whether or not (vowel) is confirmed (possible), it can be confirmed that the vowel is the corresponding vowel with respect to the input of the corresponding input value. have. For example, if "0#" is pressed, the system can recognize the input of "ㅓ" according to Table 1, but the next time "#" is pressed again, the system will display the total input value "0#". The #" is recognized as the vowel "ㅔ". In Table 1, since another input value is added after "0##" and the system does not recognize the entire input value as another input value, the system uses the vowel "ㅔ" for the input value "0##". It can be recognized definitively.

" 혹 은 "ㄱㆍ" 혹은 "ㄱ@" 혹은 "가" 등의 형태 중의 임의의 한가지로 출력될 수 있다. 다음 입력으로 자음버튼이 입력되거나 자음의 입력이 인식되면(예를 들어 "1" 이 추가로 입력), 전체 입력값 "101"에서 중간에 입력된 "0"을 모음 "ㅏ"로 확정적으로 인식하고, "각"을 출력할 수 있는 것이다. 여기서 "ㅏ = 0" 으로 입 력하도로 하였으나, "#0" 으로 역시 "ㅏ"를 입력할 수 있도록 하는 것을 허용할 수 있다. Similarly, in the case of a vowel without a circle in the confirmation (possible) column in Table 1, it can be recognized as another vowel according to the next input value. The vowel "ㅏ = 0" can also be a vowel such as "ㅓ", "ㅕ", "ㅗ", "ㅛ", ... depending on the following input, so the vowel [0] button would have been pressed after the consonant. When (for example, "10"), the output form is "ㄱ

It can be output in any one of the forms such as "or "ㄱㆍ" or "ㄱ@" or "A." When the consonant button is input as the next input or the input of a consonant is recognized (for example, "1" This is an additional input), the "0" input in the middle of the total input value "101" is definitively recognized as the vowel "ㅏ", and the "angle" can be output, where "ㅏ = 0" is input. Although it was done as a base, it may be allowed to input "ㅏ" as "#0".

") 하여 줄 수 있으며, 확정적으로 인식되는 순간 다시 적절하게 표시(예. "각")하여 줄 수 있는 것이다. 마찬가지로 "10"이 입력된 후 단어의 종료(예. 공백, 입력의 종료 등)가 인식되면, 시스템은 기 입력 된 "10 = 가"로 확정적으로 인식할 수 있는 것이다. 표1에서는 일부의 경우만 입 력중 출력형태를 예시하였다. Here, the system is completely separate from the problem of "recognizing" the corresponding vowel for a specific set of input values (including all cases temporarily recognized and definitively recognized) and "printing" the recognized content (eg display on a liquid crystal, etc.). It's a matter of. (Depending on the system, there may be cases where it is not necessary to output the recognized content, and whether or not to output the recognized content is an optional matter) For the temporarily recognized content (recognized collection here), an example As mentioned above, output in an appropriate form considering that it may vary according to the next input value (ex. "ㄱ

") can be given, and the moment it is clearly recognized, it can be displayed properly (eg, "each"). Likewise, after "10" is entered, the word ends (eg blank, end of input, etc.) When is recognized, the system can definitively recognize the input “10 = A.” Table 1 shows the output type during input only in some cases.

11-1 is a drawing presented in the applicant's prior application. The controller interprets the input value inputted through the keypad in the client with reference to the memory, and displays the analyzed result (string) in the display unit ( display unit), or transmitted to the server through a 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 are optional problems independent of the process of interpreting the input value. In terms of the hardware configuration, unlike the example drawing, it is a problem that may have from the control unit to the memory, and is not an absolute one. Fig. 11-2 is also a diagram presented in the previous application, showing an example of transmitting an input value from the client side to the server side and interpreting the input value at the server side.

Here, it is possible to apply a right arrow "→" instead of the vowel "ㅡ" and a downward arrow "↓" instead of the vowel "ㅣ", and give a similar effect. Instead of the vowels "ㅡ" and "ㅣ" in <Table 1>, the arrows "→" and "↓" can be applied respectively. Instead of the vowels "ㅡ" and "ㅣ", it would be better to display the vowels "ㅡ" and "ㅣ" instead of the "→" and "↓" on the keypad buttons respectively, in terms of user-friendliness. This is the same in "Volume input method using 4 vowels" to be described later. Furthermore, it is possible to use shapes such as horizontal lines and vertical lines similar to the vowels "ㅡ" and" ㅣ".

As suggested by the applicant in the earlier application, in Fig. 4-5, the "." assigned to the [0] button to input the vowel bottom is to use the [0] button as the "bottom button", and the remaining vowels In combination, the three vowels "ㅡ", "ㅣ", and ". (below)" buttons are combined to input. In the method of entering all vowels with the three vowels "ㅡ", "ㅏ", and "I", a button assigned to the bottom of the vowel (indicated by "." in the drawings) (in Figs. 4-5 and 4-9) It is essentially the same as the case where the vowel "ㅏ", which is used most often, is entered as the [0] button).

Therefore, it is obvious that the various properties suggested in the applicant's earlier application can be used. For example, input of a lattice/hard consonant by repeatedly pressing a button assigned to a basic consonant, input of a vowel by repeatedly pressing a vowel button, a lattice sound by a control processing method (i.e., combined with a vowel button) / Input of hard consonants, input of consonants (eg "ㅎ") assigned with vowels, etc. It is also possible to process consecutively input "00" as a promised vowel at the start of the vowel processing process.

For example, if two inputs of the [0] button are promised as the vowel "ㅓ", the first "1" input is recognized as "a" when the first "1" is input, and the second "0" is input, the vowel is processed. It recognizes that the process has started, and when the third "0" is input again, it is temporarily recognized as a vowel "ㅓ". When the fourth "1" input is input, the end of the vowel processing process is recognized and the consecutively input "00" is By definitively recognizing as "ㅓ", the input value "1001" can be recognized as "worry". In the grid sound input in FIGS. 4-10 and 4-11, input as "ㅋ = ㄱ+{Aspirated Sound Control} = ㄱ+ㅡ+ㅡ = 1**" by the control processing method applying the input after control You can do it. If "1*" is entered, the system recognizes it as "the", but sees the "*" that is entered consecutively, and the total input value "1** = ㅋ" is deterministic that the system can recognize. will be. If “*” is entered as the fourth input value after “101”, the system recognizes the input value as “gag”. This is quite natural as Hangul automata on the 2 Beolsik keyboard. Next, if "*" is entered as the 5th input value, the last input "1**" in "...1**" is recognized and confirmed as "ㅋ", so the total input value "101**" It is recognized as "Ga+ㅋ" for ". (註: When using the Unicode system,'ㅋ' should be displayed as a single letter as the final support of'A', but the JPO electronic document editor supports only KSC 5601 complete form, so it is indicated as'A+ㅋ') Deterministic ) Means the moment "1**" is detected among a series of input values "...1**", "1**" is "ㅋ", that is, as if the [ㅋ] button on the PC keyboard is entered. It means that you can process and recognize it as if it was done.

Similarly, for hard consonant input, "ㄲ = ㄱ+{hard sound control} = 1## = ㄱ+ㅣ+ ㅣ". As for the input of "ㅎ", "ㅎ" is regarded as a modified alphabet (lattice consonant) of "ㅇ" and input as "ㅎ = ㅇ+{aspirated control} = ㅇ+ㅡ+ㅡ = 8**", or Considering "ㅎ" as a variant of "ㅏ", you can enter "ㅎ = ㅏ+ㅡ+ㅡ = 0**" without ambiguity. Also, in the beginning state of the word, "ㅎ" is changed to one tarot on the [0] button, and vowels such as "ㅡ",'ㅣ", "ㅏ", "ㅜ", and "ㅚ" (vowel "ㅏ"-that is, in the example, [ After a vowel other than the 0] button-is combined to form another vowel) is identified, it is the same as described in other embodiments that the user can input "ㅎ" with one stroke of the [0] button. It is also possible to allow "0**" or "8**" to be recognized as "ㅎ" even if you can enter "ㅎ" with one stroke of the button assigned "ㅎ". It is also possible to apply the input method of the transformed alphabet "3 + stroke" that inputs 3 strokes or more (eg "ㄱ = 1", "ㅋ = 111", "ㄲ = 1111" or "ㄱ = 1", "ㄲ = 111", "ㅋ = 1111". In this case, it is very rare, but it can be ambiguous.) Also, as mentioned earlier, a consonant, a hard consonant, or a dropping consonant (a consonant that is considered a variant of the basic alphabet, for example It is also obvious that the simple repetitive selection method according to a predetermined selection order can be applied to the input of the missing consonant "ㅎ" for the basic consonant "ㅇ" and the missing consonant "ㄹ") for the basic consonant "b". For example, ㄱ = 1, ㅋ = 11, ㄲ = 111 or ㄱ = 1, ㄲ = 11, ㅋ = 111 or ㄴ = ㄴ, ㄹ = ㄴ+ㄴ ("ㄹ" is a modified alphabet of "ㄴ" (lattice or Hard consonant)) or ㅇ = ㅇ, ㅎ = ㅇ+ㅇ (based on Fig. 4-10, ㅇ = 8, ㅎ = 88) However, in the case of input without ambiguity by the control processing method Compared to that, inputting by the modified alphabet (lattice consonant, hard consonant, dropping consonant, etc.) "3+" stroke input method and simple repetition selection method creates ambiguity and does not have a big difference in the number of strokes. It goes without saying that the proposed vowel input technique can be applied separately from the application of the specific consonant input technique mentioned or not mentioned in the present invention. It is obvious that the same can be applied to the contents of entering "ㅏ" as the vowel element ".".

When applying the above consonant and vowel input method, consonants and vowels can be identified "deterministic" with respect to the input value. Therefore, it is possible to combine consonants and vowels to form Hangul syllables (lump letters). Yes, it can be easily handled by applying the consonant combination automata in the 2 Beolsik keyboard. When applying the above, it is a deterministic input method, since the system can identify consonants and vowels, and there is no difficulty in understanding them, a flow chart is not necessarily presented.

It was said that "ㅓ" can be entered by pressing the [ㅏ] button (ie, the [0] button) twice by repeatedly pressing a specific vowel button. That is, "00 = ㅓ" or "0# = ㅓ". If you only enter "00" for "ㅓ", you can define "0#" as "ㅐ" instead of "ㅓ" and enter "ㅐ = 0#". However, "0## = ㅔ", but when pressed to "0#", there is a point where "ㅐ", which has 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, it will be recognized as "10## = crab". At this time, the user can recall that the center point (or small horizontal line stroke) of "ㅐ" is pushed inward to become "ㅔ" by pressing "ㅣ" once more after entering "dog". As mentioned in the previous application, the input of "ㅑ" can be defined as "ㅑ = ㅏ+ㅏ" by pressing the "ㅏ" button twice in succession, but if you do this, it is entered as "ㅐ = ㅏ+ㅣ" It becomes difficult to do this (since you have to enter "ㅓ = ㅏ +ㅣ" here).

In Table 1, it is defined as "ㅘ = ㅏ+ㅡ+ㅣ+ㅏ = 0*#0", but it can also be defined as "ㅘ = [ㅗ+ㅏ] = ㅏ+ㅡ+ㅏ = 0*0". What is marked in "[ ... ]" is an exploded representation of vowels for better understanding. However, if this is applied, when the [0] button is pressed after the vowel "ㅗ = ㅏ+ㅡ = 0* (the vowel, that is, the vowel "ㅗ" that'.' cannot be combined with)", 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 enter "ㅎ" by other means previously suggested (eg 0**, 8**, 0*, .., etc.). Similarly, it is also possible to define "ㅙ = [ㅗ+ㅐ] = ㅏ+ㅡ + ㅏ+ㅐ = 0*0#". The definition of "ㅘ = ㅏ+ㅡ+ㅏ(= 0*0)" and "ㅙ = ㅏ+ㅡ+ㅏ+ㅏ+ㅘ (= 0*0#)" is "ㅘ = ㅏ+" in Table 1 It can be applied at the same time as defined as ㅡ+ㅣ+ㅏ (= 0*#0)", "ㅙ = ㅏ+ㅡ+ㅣ+ㅏ+ㅣ(= 0*#0#)", and only one can be selectively applied. It can be set according to the user's choice. Defined as "ㅘ = ㅏ+ㅡ+ㅏ(= 0*0)" and "ㅙ = ㅏ+ㅡ+ㅏ+ ㅣ(= 0*0#)" has fewer input strokes, so apply first , Additionally (optionally) "ㅘ = ㅏ+ㅡ+ㅣ+ㅏ (= 0*#0)", "ㅙ = ㅏ+ㅡ+ㅣ+ㅏ+ㅣ(= 0*#0#)" It would be desirable to be able to. What is defined as "ㅘ = ㅏ+ㅡ+ㅏ(= 0*0)" and "ㅙ = ㅏ+ㅡ+ㅏ+ㅣ(= 0*0#)" is "ㅓ = ㅏ+ㅏ(= It is possible separately from the definition of "00)" (ie, even if it is not defined as "ㅓ = ㅏ+ㅏ (= 00)").

For reference, vowel elements are arranged from left to right in the order of "ㅡ", ".", and "ㅣ" in the Korean keypad of Fig. 4-5 illustrated in the previous application, which serves to increase the naturalness of the input. do. If you look closely at "ㅡ", ".", "ㅣ", the vowels "ㅢ", "ㅟ", "ㅝ", "ㅞ",. . You can observe the shape of vowels such as. However, on the contrary, if they are arranged in the order of "ㅣ", ".", and "ㅡ" as in the keypad of Samseongja Company, the vowels are not well observed. In addition, there is a disadvantage in that the input of vowels cannot be input naturally as it flows from left to right. Likewise, going one step further, entering "ㅘ = ㅏ+ㅡ+ㅏ(= 0*0)" reduces the number of strokes compared to entering "ㅘ = ㅏ+ㅡ+ㅣ+ㅏ(= 0*#0)" Although meaningful, it 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 "ㅣ". Entering "...#0" is the right button ([ After pressing the #] button), the left button ([0] button) is pressed, which hinders the naturalness.

Furthermore, as "ㅓ = 00", as in the case of "ㅏ = 0", this can be applied to input of vowels such as "ㅝ" and "ㅞ". For example, in Table 1, it is defined as "ㅝ = ㅡ+ㅏ+ㅏ+ ㅣ = *00#", but "ㅓ" in "ㅝ" is "ㅏ+ㅏ = 00", and "ㅝ = [ ㅜ+ㅓ] = ㅡ+ㅏ+ㅏ+ㅏ = *000". Also in Table 1, it is defined as "ㅞ = ㅡ +ㅏ+ㅏ+ㅣ+ㅣ", but by setting "ㅓ" in "ㅞ" as "ㅏ+ㅏ = 00", "ㅞ = [ㅜ+ㅓ+ㅣ" ] = ㅡ+ㅏ+ㅏ+ㅏ+ㅣ = *000#". As in the case of "ㅘ" and "ㅙ", "ㅝ = ㅡ+ㅏ+ㅏ+ㅏ(= *000)" and "ㅞ = ㅡ+ㅏ+ㅏ+ㅏ+ㅣ(= *000#)" It is possible separately from the definition of "ㅓ = ㅏ + ㅏ = 00", and can be applied at the same time as defining "ㅝ" and "ㅞ" in Table 1, or selectively only one can be applied. If the input of "ㅓ" is defined as "ㅓ = ㅏ +ㅏ (= 00)" instead of "ㅓ = ㅏ+ㅣ (= 0#)", it is "ㅐ = ㅏ+ㅣ (= 0#)" You may be able to enter it.

When applying "ㅝ = ㅡ+ㅏ+ㅏ+ㅏ(= *000)", "ㅞ = ㅡ+ㅏ+ㅏ+ㅏ+ㅣ(= *000#)", if it is pressed to "1*00", " It is recognized as "Kyu", but when the [0] button is pressed once more, it is recognized as "Goo". When [#] is pressed once more, it is recognized as a "bin". Likewise, in this case, "*000" means the input of a normal vowel (that is, "ㅝ"), so after the vowel "ㅠ(=*00)", "ㅎ (that is, the [0] button is assigned with the vowel. It is obvious that you cannot enter "ㅎ" with one button assigned to "consonant)".

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

-You can enter the rest of the vowels by reminiscent of the number '0'with'ㅏ'-Ga placement) like "Daeah(.)", but "ㅑ" is input by combining it based on the note value. Similarly, in Table 1, "ㅒ = ㅣ +ㅏ+ㅏ+ㅣ (=#00#)" is defined, but this is defined as "ㅒ = [ㅑ+ㅣ] = ㅣ+ㅏ+ㅣ (= #0#)" It can be entered (assuming that you input "ㅐ = ㅏ+ㅣ" instead of "ㅐ = ㅏ+ㅣ"). Similarly, the vowel "ㅑ = ㅣ+ㅏ+ㅏ" and "ㅑ = ㅏ+ㅏ", and the vowel "ㅒ = ㅣ+ㅏ+ㅏ+ㅣ" and "ㅒ = ㅏ+ㅏ" It can be applied simultaneously or selectively. If "ㅑ = ㅣ+ㅏ" and "ㅒ = ㅣ+ㅏ+ㅣ", the number of strokes entered for the vowels "ㅑ" and "ㅒ" decreases by one stroke than in the case of Table 1. The reason why this is not described in the previous application is because the vowels "ㅑ" and "ㅒ" are not frequently used vowels, so they do not have much effect on the number of input strokes.

In vowel input using three vowel elements "ㅡ", ".", "ㅣ", if the "." button is pressed after an arbitrary consonant (eg "ㄱ"), it is temporarily displayed as "ㄱ.", and then When "ㅡ" is entered, ".+ㅡ" is recognized as "ㅗ" and "go" is displayed. In other words, there is a disadvantage that the complete form of Hangul cannot be displayed in the middle of the input. However, when entering a vowel by combining modern Korean vowels ("ㅡ", "ㅏ", and "ㅣ" in this example), the button assigned "ㅏ" after any consonant (eg "ㄱ") is pressed and pressed. When it loses, it has the advantage of being able to display a complete form of Hangul such as "A". Even when “ㅓ = ㅏ+ㅏ” is applied, “A” is displayed for the “10” input, and if “0” is pressed once more, a complete Korean language such as “O” can be displayed. Of course, the problem of recognizing and identifying a specific alphabet (or Hangul character) by a specific procedure (algorithm) and the problem of displaying this recognized specific alphabet (or Hangul character) are separate problems.

In addition, it is natural that the issue of the input method (input procedure) and the question of how to display the Korean character character or the code format representing the Korean character character in an appropriate form on the keypad buttons for the input method are separate issues. For example, as shown in Fig. 4-5, the vowel element "." in the [0] button. Just as it is possible to input vowels by considering the [0] button as the “ㅏ” button on the keypad marked with this mark (the red dot in the number “0”), the notation form on the keypad buttons can be modified. It has been mentioned in the previous application that this input method can be applied even to keypads that are not marked with Korean characters. Some examples of variations of the keypad notation are shown in Figs. 4-12. Figure 4-12 is a keypad displayed so that the collections "ㅏ" and "ㅓ" can be represented simultaneously by putting "+" in the number "0 (Zero)", and Figure 4-13 is also the number "0 (zero)". This is an example of a keypad in which the shape of "-ㅏ" is put in ")" and "ㅏ" is given priority to "ㅓ". In addition, as shown in Fig. 4-14, an example of a keypad in which the shape of "H", which is a form of sticking "ㅏ" and "ㅓ" on the left and right, is reminiscent of "ㅏ" and "ㅓ" in the number "0 (zero)" to be. It is also the same that the temporarily displayed form during input can also be varied like this. 4-15 are examples in which "ㅏ" and "ㅓ" are displayed respectively. In other cases, as shown in Figs. 4-15, the number "0" may be separately displayed. In addition, various modifications are possible, and all modifications except as long as the vowel combination method of the present invention is applied are also the scope of the present invention. Is self-explanatory. In the exemplary drawings, "ㅎ" is indicated in light gray, which means that "ㅎ" may not be indicated as mentioned.

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

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

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

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

Can be displayed (as in Fig. 4-13, the case where the horizontal line on the left and left is grayed out by making it possible to first recall "ㅏ", including the case where there is no part marked in gray). Or, when entering 1 up-down vowel by using the corresponding button

The shape can be displayed on the button. As in other cases, it may be used in a form displayed in the middle of the input. First presented according to the vowels that are preferentially entered using the button

Form of symmetrical or second suggested

A vertical symmetrical type of shape can be used. (If such a shape is displayed on the [0] button) As in other cases, the number "0" may or may not be displayed together, and "ㅎ" may or may not be displayed together. The image presented is intended to contain the “harmony between the order of the universe and the earth” in an advertisement and the thought of human centeredness therein.

형태 또는

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

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

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

Form or

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

Excluding the gray part on the left side of the shape, similar to the shape in which "ㅏ" is in the circle or number "0" in Fig. 4-10, it becomes a shape in which the circle or number "0" is over the "ㅏ".

The shape is a shape in which "-ㅏ" is covered with a circle or a number "0" in Fig. 4-13, but it can also be transformed into a shape in which a circle or a number "0" is covered with "+" in Fig. 4-12. It is self-evident.

As mentioned, it can represent flat consonants (eg "ㄱ") and lattice sounds corresponding to the plain consonants (eg "ㅋ") and hard consonants (eg "ㄲ") due to the nature of Hangul, and in pronunciation and shape. Since there is a similarity, the transformed alphabet is not displayed on the keypad, but is hidden, only plain consonants (eg "ㄱ") are displayed on the keypad, and the remaining 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 done. As exemplified by utilizing the characteristics of Hangeul, the most scientific writing system existing on the earth, it can be said that one of the great characteristics of Hangeul is that it is possible to construct a naturally concise keypad (with at least a small number of letters on the button). Of course. However, in some cases, it is obvious that a keypad in which modified alphabets (lattice consonants, hard consonants, and dropped consonants) are assigned together with basic consonants (flat consonants) are also included in the scope of the present invention. When the missing consonant "ㅎ" is regarded as a modified alphabet (lattice or hard consonant) of "ㅇ", "ㅇ" and "ㅎ" can be displayed on the keypad together, and the missing consonant "ㄹ" When regarded as a modified alphabet (as mentioned in the previous application, "ㅎ" may be the basic consonant in this case), "b" and "ㄹ" may be displayed together. In the illustrated drawing, it is obvious that a keypad marked on a keypad button is also included in the scope of the present invention by adding a deformed alphabet together with a flat consonant. In other words, it is possible to display only the lattice sound among the lattice and hard consonants on the keypad along with the plain consonant, and it is also possible to display only the hard consonant on the keypad button along with the plain consonant. It is also possible to mark all. In addition, it is apparent that all cases, such as when only some of the lattice sounds are additionally displayed together with the flat consonants, or when only some of the hard consonants are displayed together with the flat consonants, are included in the scope of the present invention.

The applicant explained that all Korean keypads presented in the previous application and this application can be compatible. Hangul's constituent system consists of vowels on the right side of the consonant on the left (i.e., the left and right model), and vowels on the bottom of the consonant on the top (ie, the box lower model). And in Korean people's notions, "a" corresponds to the number "1", "b" to the number "2", and "c" to the number "3". This is (1), (2), (3), (4),… I also write numbers like "Go", "I", "Da", "La",… Or ㉠, ㉡, ㉢, ㉣,… It is easy to know even in writing. "A", "b", "c",… Original characters ㉠, ㉡, ㉢,… The existence of this KSC5601 character set can also be said to prove this. That is, the numbers 1, 2, 3, 4… Buttons in order "ㄱ", "b", "c", "ㄹ"… It is evident that the assignment of is the optimal form that fits our literal and numerical ideas.

Another example was the case where numbers (not Arabic numerals, but Chinese characters 一, 二, 三, 四, 五, …) were used at the consonant position of Hangul in a rudimentary ciphertext during the Joseon Dynasty. For example, "poetry" is expressed as "七ㅣ" and "mer" is expressed as "五ㅓ". In fact, it is very easy for Koreans to find out the original sentence by looking at a word or phrase indicating the number corresponding to the consonant position of Hangul. This is also the case for those who do not know these rules. For example, when asked what it means by showing "三ㅐ 五ㅓ 四ㅣ" among the sentences written in the Joseon Dynasty in a TV program called Survival History Quiz, "all" participants answered that the original sentence was "bald head". (Of course, the quiz participants were unaware of the rule that the first consonant was marked with a number)

Therefore, as in the drawings presented by the applicant, assigning flat consonants (in order) to the number buttons and vowels to the buttons at the bottom is consistent with the numerical concept of Korean people related to consonants and also the "box lower model" Hangul composition. It is self-explanatory. However, in Korea, the keyboard of Samsung Electronics using the three vowel elements "ㅡ", ".", and "ㅣ" is widely used. Due to the influence of the keyboard of giant Samsung Electronics, some companies have a desire to place the vowel button (or vowel element button or element vowel button) above the consonant. It is never desirable, but the [*], [0], and [#] buttons at the bottom of the keypad are placed on the top of the number buttons [1], [2], [3] to form the same shape as Figs. 4-16 and 4-17. You can configure the keyboard. Although the box lower model letter arrangement is violated, consonants can be assigned to the number buttons in order. It is obvious that the exemplary drawings are also included in the applicant's earlier application category. And in the example drawing, you can see the letters "Han" or "ㅎ.ㄴ ('.' is below)" of "Hangul". When "ㅎ" is expressed in light gray, it means that "ㅎ" may not be displayed as mentioned. However, by displaying “ㅎ” on the [0] button, placing 10 flat consonants on the 10 number buttons ([1] to [0] buttons) means accepting the current Korean standard keypad (KSC-xxxx). Have.

The above is an example of entering all vowels using the three vowels "ㅏ", "ㅡ", and "ㅣ" which are the most frequently used (about 50% of the total vowel frequency) in Korean. It is obvious that the same can be applied in all similar cases. For example, it includes applying any vowel (eg, any other vowel including "ㅓ" or "ㅗ", etc.) excluding "ㅡ", "I", "ㅏ" instead of "ㅏ". When applying "ㅓ" instead of "ㅏ", it can be "ㅠ = ㅡ+ㅓ+ㅓ", and a combination of vowels is formed using a vowel ("ㅓ") that replaces the vowel "ㅏ" in the table presented above. Just do it. However, since the vowel "ㅏ" is overwhelmingly used compared to other vowels (as mentioned, 22% of the total vowel frequency), the case where the vowel "ㅏ" is not used is not good in terms of input efficiency.

By generalizing Table 1 a little more, it is possible to process vowels using 3 vowels (and 3 vowel buttons) of (element) vowels "ㅡ", "ㅣ", and "X". In the table below, among the 21 vowels in Korean, vowels used as vowels "X" out of 19 vowels excluding "ㅡ" and "ㅣ" are buttons with the vowel "X" assigned (ie, [X] button) 1 It is self-evident that it can be entered as a tarot.

collection 3 vowels combined X X One ㅏ ㅣ+X 2 ㅐ ㅣ+ X +ㅣ 3 ㅑ ㅣ+ X + X 4 ㅒ ㅣ+ X + X +ㅣ 5 ㅓ X +ㅣ 6 ㅔ X +ㅣ+ㅣ 7 ㅕ X + X +ㅣ 8 ㅖ X + X +ㅣ+ㅣ 9 ㅗ X +ㅡ 10 ㅘ X +ㅡ+ㅣ+ X 11 ㅙ X +ㅡ+ㅣ+ X +ㅣ 12 ㅚ X +ㅡ+ㅣ 13 ㅛ X + X +ㅡ 14 ㅜ ㅡ+ X 15 ㅝ ㅡ+ X + X +ㅣ 16 ㅞ ㅡ+ X + X +ㅣ+ㅣ 17 ㅟ ㅡ+ X +ㅣ 18 ㅠ ㅡ+ X + X 19 ㅡ ㅡ 20 ㅢ ㅡ+ㅣ 21 ㅣ ㅣ

To further generalize this, vowels can be input using a combination similar to the above table using three arbitrary vowel buttons in Korean. For example, the vowels "A", "B", and "X" can be used as element collections, and the remaining vowels can be entered by combination similar to the following. It is also obvious that the vowels "A", "B", and "X" can be entered with one stroke of a button assigned to each vowel. It would be desirable to use three vowels including "-", "-" and "ㅏ" for user convenience and minimization of the number of strokes.

collection 3 vowels combined X X A A B B One ㅏ B+X 2 ㅐ B+ X +B 3 ㅑ B+ X + X 4 ㅒ B+ X + X +B 5 ㅓ X + B 6 ㅔ X +B+B 7 ㅕ X + X + B 8 ㅖ X + X +B+B 9 ㅗ X +A 10 ㅘ X +A+B+ X 11 ㅙ X +A+B+ X +B 12 ㅚ X +A+B 13 ㅛ X + X +A 14 ㅜ 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 ㅣ

As suggested, vowels can be efficiently entered using 3 vowels ("ㅏ", "ㅡ", "ㅣ") (and 3 vowel buttons) of Korean. An example of the vowel input method is additionally presented as follows. The following examples are examples of using the vowels "ㅓ", "ㅡ", and "ㅣ". Here, it is assumed that the control processing method is not applied to the input of the edited consonant. (Because there are cases where "ㅡ" or "ㅣ" appears consecutively in the vowel input rule in the example below)

collection collection
decomposition 3 vowels combined (B) When applied, not applicable (A) (B) One ㅏ ㅣ+ㅣ ㅣ+ㅡ or ㅓ+ㅓ 2 ㅐ ㅣ+ㅓ
(ㅣ+ㅣ+ㅣ (X)) ㅣ+ㅡ+ㅣ 3 ㅑ ㅣ+ㅣ+ㅣ ㅣ+ㅡ+ㅡ or
ㅣ+ㅣ+ㅡ 4 ㅒ ㅑ+ㅣ
ㅏ+ㅓ ㅣ+ㅣ+ㅣ+ㅣ or
ㅣ+ㅣ+ㅓ ㅣ+ㅡ+ㅡ+ㅣ or
ㅣ+ㅣ+ㅡ+ㅣ 5 ㅓ ㅓ 6 ㅔ ㅓ+ㅣ ㅓ+ㅣ ㅡ+ㅣ+ㅣ ㅟ(B), ㅠ(B) 7 ㅕ ㅡ+ㅓ
(ㅡ+ㅡ+ㅣ (X)) 8 ㅖ ㅕ+ㅣ ㅡ+ㅓ+ㅣ 9 ㅗ ㅣ+ㅡ or
ㅓ+ㅓ 10 ㅘ ㅗ+ㅏ ㅣ+ㅡ+ㅣ+ㅣ ㅣ+ㅡ+ㅣ+ㅡ 11 ㅙ ㅘ+ㅣ
ㅚ+ㅓ ㅣ+ㅡ+ㅣ+ㅣ+ㅣ
ㅣ+ㅡ+ㅣ+ㅓ ㅣ+ㅡ+ㅣ+ㅡ+ㅣ
ㅣ+ㅡ+ㅣ+ㅓ 12 ㅚ ㅗ+ㅣ ㅣ+ㅡ+ㅣ 13 ㅛ ㅣ+ㅣ+ㅡ 14 ㅜ ㅡ+ㅡ 15 ㅝ ㅜ+ㅓ ㅡ+ㅡ+ㅓ
ㅡ+ㅣ+ㅡ or
ㅡ+ㅣ+ㅡ+ㅣ ㅞ(B-1) 16 ㅞ ㅝ+ㅣ ㅡ+ㅡ+ㅓ+ㅣ or
ㅡ+ㅡ+ㅓ+ㅓ ㅡ+ㅣ+ㅡ+ㅣ or
ㅡ+ㅣ+ㅡ+ㅣ+ㅣ ㅝ(B-2) 17 ㅟ ㅜ+ㅣ ㅡ+ㅡ+ㅣ ㅡ+ㅣ+ㅣ ㅔ(B), ㅠ(B) 18 ㅠ ㅡ+ㅡ+ㅡ ㅡ+ㅣ+ㅣ ㅔ(B), ㅟ(B) 19 ㅡ ㅡ 20 ㅢ ㅡ+ㅣ 21 ㅣ ㅣ

In the above "vowel decomposition" column, the decomposed vowels are written for better understanding. Providing several (many) input rules for one vowel as (A), (B) and "or" shows that a variety of examples are possible.

One of the characteristics of the above example is to enter "ㅏ" and "ㅑ" by repeatedly pressing the vowel "ㅣ" button, and entering "ㅜ" and "ㅠ" by repeatedly pressing the vowel "ㅡ" button. In other words, if you press the "ㅡ" button once, it becomes "ㅡ", if you press it twice, it becomes "TT", and if you press it three times, it becomes "ㅠ". (As explained in the applicant's previous application, it provides a natural feeling of input because it can have the convenience of repeatedly pressing the same button and the feeling of adding a stroke by pressing the button)

Another feature is to input the rest of the vowels using the horizontal and vertical lines of the vowels "ㅡ" and "ㅣ". At this time, "ㅓ", "ㅢ" and "ㅜ" are all combinations of "horizontal and vertical". Of these vowels, it is reasonable to enter "ㅢ = ㅡ+ㅣ". The vowel "ㅓ" can be entered with one button assigned to the "ㅓ" by itself, and the vowel "ㅜ" can be entered naturally by repeatedly pressing the "ㅡ" button. In addition, the vowels "ㅟ = [ㅜ+ㅣ]" and "ㅕ" can also be expressed as "ㅡ+ㅡ+ㅣ", but (If you use "ㅜ = ㅡ+ㅡ" of "ㅟ"), then "ㅕ By doing "ㅕ = ㅡ+ㅓ" instead of ㅡ+ㅡ+ㅣ", you can do it with "ㅟ = ㅡ+ㅡ+ㅣ". "ㅐ" is also not "ㅐ = ㅣ+ㅣ+ㅣ" but by "ㅐ = ㅣ+ㅓ", so that "ㅑ = ㅣ+ㅣ+ㅣ".

The feature of the above example is to naturally input a vowel containing the vowel "ㅓ" (for example, vowels such as ㅔ, ㅕ, ㅖ, ㅝ, ㅞ, and even more "ㅐ", "ㅒ", "ㅙ") It can be done. In the case of "ㅕ", if you enter "ㅡ+ㅡ+ㅣ", the number of strokes is 3, and it becomes difficult to input "ㅟ = [ㅜ+ㅣ] = ㅡ+ㅡ+ㅣ". Of course, if you set "ㅟ = ㅡ+ㅣ+ㅣ", you can also use "ㅕ = ㅡ+ㅡ+ㅣ", but the input method of the vowel "ㅜ" by adding "ㅜ" included in "ㅟ" (ㅜ = ㅡ+ ㅡ) is input in a different way, so it is not good in terms of simplicity of input rules, user convenience, and WYSWYG.

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

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

In the example above, except for the input case in which the vowel "ㅡ" or "ㅣ" appears consecutively at the beginning of the vowel processing process, the other input method is to input the transformed alphabet (gap/hard consonant, etc.) by the control processing method. It can also be applied selectively in cases (however, as long as it does not conflict with the input rule of the case where the modified alphabet is entered by the control processing method). Similarly, as long as it does not conflict with the above case among the input cases in <Table 1> (ie, it is not defined identically for other vowels), it can be selectively applied with the above case. It is obvious that this is applicable to the entire invention.

Similar to the above, input "ㅓ", "ㅕ", "ㅏ", "ㅑ", etc. by repeatedly pressing the vowels "ㅡ" and "ㅣ", and the horizontal lines of the vowels "ㅡ" and "ㅣ" This is an example of a case where the remaining vowels are input using a combination of vertical line shapes, but three vowel buttons are used: "ㅏ", "ㅡ", and "ㅣ".

collection collection
decomposition 3 vowels combined (B) When applied, not applicable (A) (B) One ㅏ ㅏ ㅣ+ㅣ ㅛ(A), ㅑ(A-4) 2 ㅐ ㅏ+ㅣ ㅣ+ㅡ+ㅣ 3 ㅑ ㅏ+ㅡ or
ㅣ+ㅣ+ㅣ or
ㅣ+ㅣ+ㅡ or
ㅣ+ㅣ ㅣ+ㅡ+ㅡ 4 ㅒ ㅑ+ㅣ ㅏ+ㅡ+ㅣ ㅣ+ㅡ+ㅡ+ㅣ 5 ㅓ ㅏ+ㅏ 6 ㅔ ㅓ+ㅣ ㅏ+ㅏ+ㅣ ㅡ+ㅣ+ㅣ ㅟ(B), ㅠ(B) 7 ㅕ ㅡ+ㅏ or
ㅡ+ㅏ+ㅏ or
ㅏ+ㅏ+ㅏ or ㅡ+ㅡ+ㅣ ㅟ(A) 8 ㅖ ㅕ+ㅣ ㅡ+ㅡ+ㅣ+ㅣ or
ㅏ+ㅏ+ㅏ+ㅏ 9 ㅗ ㅣ+ㅡ 10 ㅘ ㅗ+ㅏ ㅣ+ㅡ+ㅏ 11 ㅙ ㅘ+ㅣ ㅣ+ㅡ+ㅏ+ㅣ 12 ㅚ ㅗ+ㅣ ㅣ+ㅡ+ㅣ 13 ㅛ ㅣ+ㅣ+ㅡ 14 ㅜ ㅡ+ㅡ 15 ㅝ ㅜ+ㅓ ㅡ+ㅡ+ㅏ or
ㅡ+ㅣ+ㅡ ㅡ+ㅡ+ㅏ+ㅏ or
ㅡ+ㅣ+ㅡ+ㅣ ㅞ(A-2) 16 ㅞ ㅝ+ㅣ ㅡ+ㅡ+ㅏ+ㅣ or
ㅡ+ㅣ+ㅡ+ㅣ ㅡ+ㅡ+ㅏ+ㅏ+ㅣ or
ㅡ+ㅣ+ㅡ+ㅣ+ㅣ 17 ㅟ ㅜ+ㅣ ㅡ+ㅡ+ㅣ ㅡ+ㅣ+ㅣ ㅔ(B), ㅠ(B) 18 ㅠ ㅡ+ㅡ+ㅡ ㅡ+ㅣ+ㅣ ㅔ(B), ㅟ(B) 19 ㅡ ㅡ 20 ㅢ ㅡ+ㅣ 21 ㅣ ㅣ

The frequency of vowels "ㅓ", "ㅡ", and "ㅣ" is approximately 40% of the total vowel use frequency, and the frequency of vowels "ㅏ", "ㅡ", and "ㅣ" is about 50%, so "ㅏ Using ", "ㅡ" and "ㅣ" can be efficient in the input batting surface. And there is an advantage of being able to naturally input a vowel including the vowel "ㅏ" (eg "ㅐ", "ㅑ", "ㅒ", "ㅘ", "ㅙ", etc.). However, in order to input "ㅟ = ㅡ+ㅡ+ㅣ", there is a disadvantage such as not being able to input "ㅕ = ㅡ+ㅡ+ㅣ". Therefore, if you input "ㅕ = ㅏ+ㅏ+ㅏ", it becomes "ㅏ", "ㅓ", and "ㅕ" by pressing the "ㅏ" button.

It is as described that only one of the input methods for a single vowel can be applied or several can be applied simultaneously. However, similarly, if there are multiple vowels with the same input value (the same vowel combination in the example above), only one need to be enabled.

In (A) of the "ㅝ" input, "ㅝ = ㅡ+ㅡ+ㅏ" is not a Korean vowel that combines "ㅏ" after the vowel "ㅜ", so enter "ㅝ = ㅡ+ㅡ+ㅏ" It showed that it can reduce the number of strokes. However, it is a disadvantage in terms of simplicity and consistency of input rules. Therefore, it is possible to input "ㅝ = ㅡ+ㅡ+ㅏ" and at the same time as "ㅝ = [ㅜ+ㅓ] = ㅡ+ㅡ+ㅏ+ㅏ" as in (B) of the "ㅝ" input. At the same time, it shows that it is possible to use a combination of the horizontal and vertical lines of the vowels "ㅡ" and "ㅣ" in the input of "ㅝ".

In addition, 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, three vowels of modern Korean are used. Among them, the vowels "ㅏ", "ㅡ", and "ㅣ" are used, and "ㅓ", "ㅕ", "ㅖ" by repeatedly pressing the "ㅣ" button. And enter "ㅜ" and "ㅠ" by repeatedly pressing the "ㅡ" button, and "ㅑ" by repeatedly pressing the "ㅏ" button, and "ㅗ" and "ㅛ" are horizontal/vertical lines 10 basic vowels (ie, ㅏ, ㅑ, ㅓ, ㅕ, ㅗ) as a combination of "ㅡ" and "ㅣ", which are vowels of "ㅗ = ㅣ+ㅡ", "ㅛ = ㅣ+ㅣ+ㅡ") , ㅛ, ㅜ, ㅠ), and the remaining vowels are entered as a combination of these vowels.

collection collection
decomposition 3 vowels combined (B) When applied, not applicable (A) (B) One ㅏ ㅏ 2 ㅐ ㅏ+ㅣ 3 ㅑ ㅏ+ㅏ 4 ㅒ ㅑ+ㅣ ㅏ+ㅏ+ㅣ 5 ㅓ ㅣ+ㅣ 6 ㅔ ㅓ+ㅣ ㅡ+ㅣ+ㅣ 7 ㅕ ㅣ+ㅣ+ㅣ 8 ㅖ ㅕ+ㅣ ㅣ+ㅣ+ㅣ+ㅣ 9 ㅗ ㅣ+ㅡ 10 ㅘ ㅗ+ㅏ ㅣ+ㅡ+ㅏ 11 ㅙ ㅘ+ㅣ ㅣ+ㅡ+ㅏ+ㅣ 12 ㅚ ㅗ+ㅣ ㅣ+ㅡ+ㅣ 13 ㅛ ㅣ+ㅣ+ㅡ 14 ㅜ ㅡ+ㅡ 15 ㅝ ㅜ+ㅓ
ㅠ+ㅣ ㅡ+ㅡ+ㅣ+ㅣ or
ㅡ+ㅡ+ㅡ+ㅣ 16 ㅞ ㅝ+ㅣ
ㅠ+ㅣ+ㅣ ㅡ+ㅡ+ㅣ+ㅣ+ㅣ or
ㅡ+ㅡ+ㅡ+ㅣ+ㅣ 17 ㅟ ㅜ+ㅣ ㅡ+ㅡ+ㅣ 18 ㅠ ㅡ+ㅡ+ㅡ 19 ㅡ ㅡ 20 ㅢ ㅡ+ㅣ 21 ㅣ ㅣ

In the above example, the combination of the vowels "ㅡ" and "ㅣ" was used only for "ㅗ" and "ㅛ" that are not entered by repeatedly pressing the "ㅡ" button among the 10 basic vowels. In the input of "ㅔ", a combination of "ㅡ" and "ㅣ", which are horizontal/vertical vowels, was used as "ㅔ = ㅡ+ㅣ+ㅣ". If "ㅕ = ㅡ+ㅡ+ㅣ" is not used as "ㅕ = ㅣ+ㅣ+ㅣ" but the combination of the vowels "ㅡ" and "ㅣ", then "ㅔ = [ㅓ+ㅣ] = "ㅣ+ㅣ +ㅣ". All vowels other than the 10 basic vowels are entered as a combination of the 10 basic vowels entered above. However, "ㅞ = [ㅜ+ㅔ] = ㅡ+ㅡ+ㅣ+ㅣ "ㅔ" included in "ㅞ" as "+ㅣ" is set to "ㅣ +ㅣ+ㅣ" It can be seen that an easy-to-recognize input rule is applied as a whole.

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

An additional 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 vertical/horizontal form for convenience as follows.

"ㅡ" is called "horizontal vowel" for convenience, and "ㅣ" is called "vertical vowel" for convenience. "ㅘ", "ㅙ", ㅚ", "ㅝ", "ㅞ", "ㅟ", and "ㅢ" including "ㅡ" and "ㅣ" are called "vertical and horizontal vowels", including "ㅡ" Therefore, "ㅗ", "ㅛ", "TT", and "ㅠ" in the form of adding small strokes are called "horizontal (basic) vowels", and in the form of adding small strokes including "ㅣ" "ㅏ", "ㅐ", "ㅑ", "ㅒ", "ㅓ", "ㅔ", "ㅕ", "ㅖ" are called "vertical (basic) vowels".

In addition, 10 basic vowels (ㅏ, ㅑ, ㅓ, ㅕ, ㅗ, ㅛ, ㅜ, ㅠ, ㅡ, ㅣ) are classified according to direction as follows. "ㅏ", "ㅑ" is a right-facing vowel, "ㅓ", "ㅕ" is a left-facing vowel, "ㅗ", "ㅛ" is an upward vowel, "ㅜ", " It can be said that ㅠ" is a downward (下向) vowel, and the basic "ㅡ", "ㅣ" is an unscented (無向) vowel. If you divide it further, "ㅏ" with one small stroke to the right is "1-right vowel", and "ㅑ" with two small strokes to the right is "2-right vowel". The rest of the vowels (ㅓ, ㅕ, ㅗ, ㅛ, ㅜ, ㅠ) can be called in the same way. The sum of the upward and downward vowels can be referred to as "up and down vowels", and the sum of the right and upward vowels can be referred to as "upward right vowels", and the other vowels can be called similarly. The vowels "ㅗ" and "ㅜ" can be collectively referred to as "1-up and down vowels", and the vowels "ㅏ" and "ㅓ" can be collectively referred to as "1-left and right vowels". Likewise, the combination of "ㅛ" and "ㅠ" can be called a "2-up and down vowel", and "ㅑ" and "ㅕ" can be collectively referred to as "2-left and right vowel". Among the 10 basic vowels, "ㅔ" and "ㅖ" can be similarly classified.

*Based on the undirected vowels "ㅡ" and "ㅣ", the upward vowel can be input by repeatedly pressing the button assigned with "-", the downward vowel can be input, and 1- the vertical vowel It can be input, or both up and down vowels can be input. Similarly, the left-facing vowel can be input by repeatedly pressing the button assigned to the undirected vowel "ㅣ", the right-facing vowel can be input, the 1-left-right vowel can be input, and the left-right You can also have all vowels entered. It is natural that the selection order 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 "ㅏ, ㅣ, ㅡ, ㅓ, ㅗ, ㅜ, ㅕ, ㅐ, ㅔ, ㅢ, ㅘ, ㅚ, ㅛ, ㅑ, ㅝ, ㅟ, ㅠ, ㅞ, ㅙ, ㅞ, It is called the order of "ㅒ", and the top 9 vowels occupy 90% of the total frequency of use.

First, a method of combining vowels using three vowel elements of "ㅡ", ".", and "ㅣ" based on FIG. 4-5 is currently widely used. Of course, you can put "ㅎ" on the [0] button or not. In the current method (the method by the vowel stroke combination used by Samsung Electronics), when entering characters such as "Go", "Kyo", "Geo", and "Rye", the complete Korean characters are not made in the middle of the input. There was said to be. (Example. When inputting "Gyo", it becomes "ㄱ => ㄱ. => ㄱ.. => Gyo") In other words, this phenomenon occurs when the upper left vowel (left and upward vowel) is input. Therefore, this problem can be solved by repeatedly pressing "-" and "-" to input an upward vowel and a left vowel. For example, if "ㅡ" is defined so that the upward vowel is input according to the repeated pressing of the assigned button, it becomes "ㅡ" => "ㅗ" => "ㅛ" according to the repeated pressing of the button. If you press "1***", it becomes "ㄱ => That => High => "Gyo", so that the forms such as "ㄱㆍ" and "ㄱㆍㆍ" do not appear in the middle of the input as in the existing method. Likewise, if the left-facing vowel is input by repeatedly pressing the button assigned with "ㅣ", it 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 conventional method of entering “ㅗ”, “ㅓ” in combination, etc. For the input of the remaining vowels, the conventional method, the previous application, or the method proposed in the present invention is used. It can be applied selectively, but there is a disadvantage that inputting "ㅔ" and "ㅖ" is not natural when repeatedly pressing the "ㅣ" button to input the left vowel. By using a combination of equilibrium vowels, it can be done as "ㅔ = ㅡ+ㅣ+ㅣ ("-+ㅣ = ㅢ" in the middle of the input)" and "ㅖ = ㅡ+ㅡ+ㅣ+ㅣ".

You can enter "up and down vowels" by repeatedly pressing the button assigned with "-". For example, depending on the repeated press of the button assigned with "ㅡ", it is to be "ㅡ => ㅗ => ㅜ" (=> "ㅛ => ㅠ"). The order in which “up and down vowels” are selected according to repeated pressing may be arbitrarily determined. It can be determined in consideration of the prior order and frequency of use. It would be desirable to select “1-up and down vowels” with a relatively high frequency of use rather than “2-up and down vowels” which are less frequently used. It is not good for the convenience and intuitiveness of input that the number of repeated presses is too high to enter a specific vowel, so for "2-up and down vowels", the corresponding 1-up and down vowels and "ㆍ" You can do it. For example, you can say "ㅛ = [ㅗ+ㆍ] = ㅡ+ㅡ+ㆍ (= **0)". Also [ . . . ] The vowels are decomposed to help understanding. Here, "·" may be considered as a vowel element or as a subsequent control. In other words, it is natural to think that there is "ㅛ" as the successor alphabet of "ㅗ". In other words, after entering "ㅗ", select the next control (one stroke of the [0] button in the example) and input the subsequent alphabet of "ㅗ" (reference control processing method, chain-type control processing method). "ㅛ = [ㆍ+ㅗ] =ㆍ+ㅡ+ㅡ (=0**)" can also be used, but based on Fig. 4-5, "ㆍ" is displayed in the middle of the input to display complete Korean characters. There is a point that does not work. You can do it with "ㅠ = [ㅜ+ㆍ] = ㅡ+ㅡ+ㅡ+ㆍ (= ***0)". Although the number of strokes for "ㅠ" input is increased by 1 stroke compared to the previous input method, "ㅠ" does not affect the increase of the total number of strokes as it is a vowel that is not used very often.

Similarly, an upward vowel can be input by repeatedly pressing a button assigned with "-", and a downward vowel can be input by repeatedly pressing a button assigned with "-". If an upward vowel is to be input, it becomes "ㅡ" => "ㅗ", => "ㅛ" in response to the repeated pressing of the button assigned with "-", and if the downward vowel is input, "-" => "ㅜ" => "ㅠ". In the same way, the left vowel or the right vowel can be input by repeatedly pressing the button assigned "I".

The same can be applied to the button assigned "I". In other words, if the left and right vowels are input according to the repeated pressing of the button assigned with "ㅣ", it becomes like "ㅣ => ㅏ => ㅓ" (=> "ㅑ => ㅕ"). For example, if the input value is displayed, "ㅣ = #", "ㅏ = ##", "ㅓ = ###",. . . Becomes like Placing "ㅑ" and "ㅕ" in parentheses means that you may or may not be asked to type. Here, 3 strokes are required ("###") for the input of the vowel "ㅓ", which is used with many frequency of use. In the input of "ㅑ", "ㅑ = [ㅏ+ㆍ] = ㅣ+ㅣ+ㆍ (= ##0)" and "ㅕ = [ㅓ+ㆍ] = ㅣ+ㅣ+ ㅣ+ㆍ (= ## You can do it with "#0)". In addition, there is a disadvantage that 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 the user must be familiar with the input There are many rules. If a combination of horizontal/vertical vowels is used, "ㅔ = ㅡ+ㅣ+ㅣ" and "ㅐ = ㅐ = ㅣ+ㅡ+ㅣ" can be used, but small or short strokes (the first stroke in "ㅔ", "ㅐ There is a little unnaturalness about combining "in the middle stroke" with "ㅡ". In order to overcome this, depending on the repeated press of the button assigned with "ㅣ", you can make "ㅣ" => "ㅏ" => "ㅓ" => "ㅐ" => "ㅔ", and "ㅒ", " ㅖ" can be entered as a combination of "ㅐ", "ㅔ" and "ㆍ", respectively. Again, it is one vowel (eg, "ㅔ"), but there is a disadvantage that the number of repeated presses (eg 5 times) is excessively increased in the input of a vowel that is frequently used. Also, it is natural to input "ㅐ" and "ㅔ" as "ㅐ = [ㅏ+ㅣ] =.. ." and "ㅔ = [ㅓ+ㅣ] =.. ." There is also a disadvantage that cannot be done.

In the above additional example, vowels are entered using the repeated press of the vowel button, so to apply the control processing method to the input of the transformed alphabet (lattice consonant, hard consonant, dropping consonant), in combining plain consonant and vowel button, vowel It must be input by adding 1 stroke to the maximum number of repetitions for creation. For example, if you press the "ㅡ" button repeatedly to "ㅡ" => "ㅗ" => "ㅜ" (that is, if it takes up to 3 strokes to enter a vowel), "ㅋ = ㄱ+ㅡ+ㅡ+ㅡ+ㅡ (= 1****)". This is also the case in other embodiments. Again, there is a disadvantage in that it takes a large number of repetitions to input one grapheme. As with the repeat selection method, it is always possible to input consonants by repeatedly pressing the consonant button.

It is revealed that the content described below is the core of this application. Currently, the input method and keypad of Samsung Electronics are widely used, and as Samsung Electronics is the largest company in Korea, the applicant's pre-application technology using "three Korean vowels and combinations" does not conflict with the existing technology with Samsung Electronics. Despite this, small and medium-sized enterprises (SMEs) who do not have expertise in patents are concerned about employing the applicant's technology even though they want to employ it. Accordingly, the following additional examples are presented.

In the case of using the vowel elements of "ㅡ", "ㆍ" and "ㅣ" additionally suggested above, it was pointed out that the input of "ㅐ" and "ㅔ" was not natural. In addition, when repeatedly pressing the "ㅡ" and "ㅣ" buttons, the number of strokes was increased compared to the previous one when entering up-down vowels and left-right vowels. In the following example, the modern Korean vowels "ㅡ", "ㅏ", "ㅣ" or "ㅡ", "ㅓ", "ㅣ" are used, and by repeatedly pressing the vowel button, a natural and combination of vowels can be entered. Show possible examples. All keypads in Fig. 4-* are said to be compatible. In particular, in drawings marked with "ㆍ" on the [0] button and drawings marked with "ㅏ" (or "+", "-ㅏ", "H", "ㅏㅓ", etc. as a variant of "ㅏ" The [0] button marked "ㆍ" can be thought of as the button marked "ㅏ", and the user can recognize and use the [0] button marked "ㅏ" as "ㆍ". It is noted that the [0] button marked with "ㅏ" or the like is used to input "·" which can be regarded as "collection element" or "subsequence control".

The same parts as in the case of using "ㅡ", "ㆍ", and "ㅣ" presented to explain the present embodiment avoid the explanation, and focus on the part that overcomes the case pointed out as a disadvantage. First, this is an example of using "ㅡ", "ㅏ", and "ㅣ". You can enter "ㅐ", "ㅔ" by repeatedly pressing the "ㅣ" button. The order of selection by repeatedly pressing the "I" button can be arbitrarily determined. For example, if "ㅐ" is selected first, it becomes "ㅐ = ㅣ+ㅣ (= ##)", and "ㅔ = ㅣ+ㅣ+ㅣ (= ###)". Entering "ㅐ" as "ㅣ+ㅣ" allows you to naturally adapt from the user's point of view because you can see two vertical lines in the shape of "ㅐ". As mentioned, the user can recall that the small stroke in the middle of "ㅐ" is pushed to the left by pressing "ㅣ" once more after "ㅐ". As an input example, it becomes "dog = 1##" and "crab = 1###".

"ㅒ" can be input as a combination of "ㅐ" and "ㆍ" (the order in which they are combined can be arbitrarily determined), and "ㅖ" can be naturally input as a combination of "ㅔ" and "ㆍ". For example, based on Fig. 4-5, "ㅒ = [ㅐ+ㆍ] = ㅣ+ㅣ+ㆍ (= ##0)", and "ㅖ = [ㅔ+ㆍ] = ㅣ+ㅣ+ㅣ+ ㆍ becomes "(= ###0)". Based on Figs. 4-10 ~ Fig. 4-13, it becomes "ㅒ = [ㅐ+ㆍ] = ㅣ+ㅣ+ㅏ (= ##0)", and "ㅖ = [ㅔ+ㆍ] = ㅣ+ㅣ+ It becomes ㅣ+ㅏ (= ###0)". In Figs. 4-10 to 4-13, the user presses the [0] button containing “ㅏ” in the circle or number “0” to “ㆍ” or “subsequent control” (that is, “ㅒ” is the next alpha of “ㅐ”. Bet) It is easy to see that you can input it consciously like a button. This is also the same below. In another case, "ㅒ = [ㅐ+ㅡ] = ㅣ+ㅣ+ㅡ (= ##*)", and "ㅖ = [ㅔ+ㅡ] = ㅣ+ㅣ+ㅣ+ㅡ (= ###*) You can do it with ". Again, you can see that the "ㅡ" button is used as a control button (subscript control or subsequent control). Likewise, the order of combination with the "ㅡ" button can be either first input or after input, as long as it does not collide with the input values of other vowels. This shows that vowels other than vowels input by repeatedly pressing the same button can be input by various combination methods.

By repeatedly pressing the button assigned with "ㅏ", it can be entered as "ㅏ" => "ㅓ" (=> "ㅑ" => "ㅕ"). In other words, "1-left and right vowels" or "left and right vowels" are input by repeatedly pressing the button assigned "ㅏ". The selection order according to repeated pressing can be determined in consideration of dictionary order and frequency of use. If "1-left and right vowels (that is, "ㅏ", "ㅓ")" are entered, this is similar to the input method of <Table 1> and FIGS. 4-20 and 4-21 previously presented. Considering the frequency of use of the vowel input by repeated pressing, it is possible to make "ㅏ" => "ㅓ" => "ㅕ" => "ㅑ" according to the repeated pressing of the button assigned "ㅏ" Of course. Here too, when entering vowels such as "ㅑ" and "ㅕ", the number of repeated presses increases. At this time, by using the input of "ㅑ" and "ㅕ" suggested in another embodiment, it can be set as "ㅑ = [ㅏ+ㅡ] (= 0*)" and "ㅕ = [ㅓ+ㅡ] (= 00*). In this way, inputting "left and right vowels" by repeatedly pressing the button assigned "ㅏ" can be applied equally to the case of inputting using three vowels "ㅡ", "ㅓ" and "ㅣ" For example, by repeatedly pressing a button assigned with "ㅓ", you can enter "ㅓ" => "ㅏ" (=> "ㅕ" => "ㅑ"). Like this, "ㅏ" ( Or, by repeatedly pressing the button assigned with "ㅓ"), you can input "left and right vowels" including the vowels assigned to the button. You can enter another vowel by repeatedly pressing the button assigned with "ㅓ". In addition, by allowing you to input vowels with similarity in shape, it allows natural input while arranging the minimum number of graphemes on the keypad, for example, pressing a button assigned with "ㅏ" once. When pressed, "ㅏ" is entered, and double-clicked to become "ㅓ". That is, when you press the button assigned "ㅏ" twice, the previously entered "ㅏ" is inputted with "ㅓ" in the form in which the left and right turns around a vertical line. , The user can easily recall a rule that changes to a left-right symmetrical type when pressing the "ㅏ" button twice.

As shown in Fig. 4-28, the input of the left-right vowel, the left-facing vowel, or the 1-left-right vowel by repeatedly pressing the button assigned "ㅏ" (or "ㅓ") is shown in graph form. Compared to the conventional input method of combining vowel elements, "ㅏ", which is a vowel that is used more frequently, can be entered in one stroke, and is a vowel that is relatively infrequently used (or "ㅑ" according to the order of selection. It can be seen that the number of strokes entered for ") has increased by one stroke, so the total number of stroked strokes is much less than the existing vowel combination method. In addition, since vowels can be input by repeatedly pressing the same button, the convenience of input is also increased. Likewise, if the vowel "ㅗ" or the vowel "TT" is used instead of the vowel "ㅏ", it is easy to see that the up and down vowels (or 1-up and down vowels) can be entered by repeatedly pressing the button.

If "ㅏ" (or "ㅓ") is pressed repeatedly by pressing the assigned button, up to 2-left and right vowels ("ㅑ", "ㅕ") are pressed repeatedly to input a single vowel. There is a downside to losing. Here, as suggested in the previous application, "ㅑ = [ㅏ+ㅡ] = ㅏ+ㅡ (=0*)" and "ㅕ = [ㅓ+ㅡ] = ㅏ+ㅏ+ㅡ (= 00*)" have. This basically shows that combinations of vowels other than the vowels ("ㅏ", "ㅓ") input by repeated pressing can appear in various ways.

In the input of the vowel "ㅘ", it is easy to understand that it can be done as "ㅘ = [ㅗ+ㅏ] = ㅡ+ㅡ+ㅏ (= **0)". It is as described above that the upward vowel, the upward and downward vowel, or the 1-up and downward vowel can be input by repeatedly pressing the "-" button. "Upward vowels or up-and-down vowels" are expressed as "upward (downward) vowels". Likewise, if you enter 1-up and down vowels such as "ㅡ" => "ㅗ" => "ㅜ" by repeatedly pressing the button assigned with "ㅡ", the 2-up and down vowel "ㅛ" is "ㅗ" and Combination of "ㆍ" to "ㅛ = [ㅗ+ㆍ] = ㅡ+ㅡ+ㅏ (= **0)", "ㅠ = [ㅜ+ㆍ] = ㅡ+ㅡ+ㅡ+ㅏ (= ** When inputting as *0)", "ㅛ (= 00*)" has the same code value as "ㅘ (= 00*)", so it crashes. Therefore, by repeatedly pressing the "ㅡ" button, the upward vowel can be input so that "ㅡ" => "ㅗ" => "ㅛ". In other words, it becomes "ㅛ = ㅡ+ㅡ+ㅡ (= ***)" and does not collide or overlap with "ㅘ = **0". The downward vowel can be entered as suggested in the previous application (eg <Table 1> and other examples). For example, "ㅜ = ㅡ+ㅏ (= *0)" and "ㅠ = ㅡ+ㅏ+ㅏ (= *00)".

For the input of the remaining vowels, "ㅟ = [ㅜ+ㅣ] = ㅜ+ㅣ = *0#", "ㅝ = [ㅜ+ㅓ] = ㅜ+ㅓ (= *0 00)", and "ㅞ = [ㅜ+ㅓ+ㅣ] = ㅜ+ㅓ+ㅣ (= *000#) In the case of inputting all up and down vowels with a button assigned with "-", repeat of the button assigned with "-" Depending on the press, "ㅡ" => "ㅗ" => "ㅜ" => "ㅛ" => "ㅠ" There is a disadvantage that the number of strokes is increased in the input of "ㅛ" and "ㅠ", but this In the case of the vowel "ㅝ", "ㅝ = [ㅜ+ㅓ] = ㅡ+ㅡ+ㅡ+ㅏ+ㅏ (= ***00)" is the vowel with "ㅏ" after entering "ㅜ" Because there is no "ㅝ = [ㅜ+ㅓ] = ㅡ+ㅡ+ㅡ+ㅓ (= ***00)", not "ㅝ = [ㅜ+ㅓ] = ㅡ+ㅡ+ㅡ+ㅏ (= ***0) )". That is, after entering "ㅜ", press the button assigned with "ㅏ" once to enter "ㅝ". Enter "ㅏ" and "ㅓ" on the button assigned with "ㅏ". In the case of Figs. 4-12 to 4-14 in which "+", "-ㅏ", and "H" that can be reminiscent of at the same time are displayed, there is an advantage of being able to input "ㅝ" more naturally. In the input of "T", it is also possible to input a combination of vertical/horizontal vowels "ㅡ" and "ㅣ" as suggested in the example of the previous application. For example, "ㅛ = ㅣ+ㅣ+ㅡ (= # # # #*)", "ㅠ = ㅡ+ㅣ+ㅣ (= *##)".

Some of the above contents are summarized in tabular form as follows, and if summarized in graph form as shown in Fig. When entering 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 descriptions are summarized in tables, and not all contents of the table are summarized in drawings. The most important feature of this embodiment is that when trying to define a rule for entering vowels by repeatedly pressing the three vowel element buttons, the input of "ㅐ" and "ㅔ", which is the most unnatural and difficult to process, is the "ㅣ" button. One point for natural input by repeatedly pressing of, "ㅏ" and "ㅓ" by repeatedly pressing the "ㅏ" button, or "ㅡ" by repeatedly pressing the "ㅡ" button , "ㅗ", "ㅛ", etc. can be entered, such as one point. In the present embodiment, vowels input by repeatedly pressing the vowel button, which is a key part, are displayed in gray on the graph. In this way, it was shown that the remaining vowels can be naturally input using these vowels that can be input by repeatedly pressing, and in the input of the remaining vowels, it has been shown that various combinations are possible for one vowel. It is obvious to the person skilled in the art that, as long as there is no conflict in the input of a specific vowel, vowel combinations in other embodiments may be selectively or additionally applied, and there may be many variations.

collection collection
decomposition 3 vowels combined 4-* Button input value from the yes key pad One ㅏ ㅏ 0 2 ㅐ ㅣ+ㅣ ## 3 ㅑ
ㅏ+ㅡ ㅏ+ㅏ+ㅏ or
ㅏ+ㅡ 000 or
0* 4 ㅒ ㅑ+ㅣor
ㅐ+ㆍor
ㅐ+ㅡ ㅏ+ㅏ+ㅏ+ㅣ or
ㅣ+ㅣ+ㅏ or
ㅣ+ㅣ+ㅡ 000# or
##0 or
##* 5 ㅓ ㅏ+ㅏ 00 6 ㅔ ㅣ+ㅣ+ㅣ ### 7 ㅕ
ㅓ+ㅡ ㅏ+ㅏ+ㅏ+ㅏ or
ㅏ+ㅏ+ㅡ 0000
00* 8 ㅖ ㅔ+ㆍ or
ㅔ+ㅡ ㅣ+ㅣ+ㅣ+ㅏ or
ㅣ+ㅣ+ㅣ+ㅡ ###0 or
###* 9 ㅗ ㅡ+ㅡ ** 10 ㅘ ㅗ+ㅏ ㅡ+ㅡ+ㅏ **0 11 ㅙ ㅘ+ㅣ ㅡ+ㅡ+ㅏ+ㅣ **0# 12 ㅚ ㅗ+ㅣ ㅡ+ㅡ+ㅣ **# 13 ㅛ ㅡ+ㅡ+ㅡ *** 14 ㅜ ㅡ+ㆍ ㅡ+ㅏ *0 15 ㅝ ㅜ+ㅓ ㅡ+ㅏ+ㅏ+ㅏ *000 16 ㅞ ㅜ+ㅓ+ㅣ ㅡ+ㅏ+ㅏ+ㅏ+ㅣ *000# 17 ㅟ ㅜ+ㅣ ㅡ+ㅏ+ㅣ *0# 18 ㅠ ㅡ+ㅏ+ㅏ *00 19 ㅡ ㅡ * 20 ㅢ ㅡ+ㅣ ㅡ+ㅣ *# 21 ㅣ ㅣ #

If another example is additionally presented as follows. In the above example, "ㅐ" was input by repeatedly pressing the "ㅣ" button, and "ㅓ" was input by repeatedly pressing the "ㅏ" button. On the keypad assigned "ㅏ" and "ㅣ", "ㅐ = [ㅏ+ㅣ] =.. ." You can naturally think of typing as. Of course, in the examples related to Table 7, "ㅐ = [ㅏ+ㅣ] =.. ." You can also enter as. However, "ㅐ = [ㅏ+ㅣ] =.. ." Since it can be entered as "ㅣ", it is possible to input "ㅣ" => "ㅓ" (=> "ㅔ") by repeatedly pressing the assigned button. In other words, it is to enter "1-to-left vowel" by repeatedly pressing "ㅣ". Here, "ㅓ = ㅣ+ㅣ (= ##)", so "ㅔ" is a combination of "ㅓ" and "ㅣ" naturally, "ㅔ = [ㅓ+ㅣ] = ㅓ+ㅣ (= ###)" Becomes. For example, for the input of "1##", it becomes "ㄱ => Ki => Go", so the user can fill in the small stroke to the left of "ㅣ" You just need to be familiar with the input rules.

Similarly, it is assumed that the upward vowel is input by repeatedly pressing the "ㅡ" button. In other words, "ㅡ" => "ㅗ" => "ㅛ" is input by repeatedly pressing the "ㅡ" button. For the input of "1**", it becomes "ㄱ => that => high", so if the user knows only the input rule that fills the upper (that is, the consonant) small stroke by repeatedly pressing the button assigned with "ㅡ" do. Input of the downward vowels "TT" and "ㅠ" can also be entered in the manner described in the previous application and other embodiments (eg, Table 1). For example, "ㅜ = ㅡ+ㅏ (= *0)" and "ㅠ = ㅡ+ㅏ+ㅏ (= *00)".

For the input of "ㅐ", you can set "ㅐ = [ㅏ+ㅐ] = ㅏ+び (= 0#)". The input of "ㅕ", "ㅒ", "ㅖ", and "ㅓ", "ㅐ", "ㅔ" and "ㆍ(the button with "ㅏ" in "0" in the example keypad)" You can do it by typing. That is, "ㅕ = [ㅓ+ㆍ] = ㅣ+ㅣ+ㅏ (= ##0)", "ㅒ = [ㅐ+ㆍ] = ㅏ+ㅣ+ㅏ (= 0#0)", " [ㅔ+ㆍ] = ㅣ+ㅣ+ㅣ+ㆍ (= ###0)". Here, "ㅕ = [ㅓ+ㅡ] = ㅣ+ㅣ+ㅡ (= ##*)", "ㅒ = [ㅐ+ㅡ] = ㅏ+ㅣ+ㅡ (= 0#*)", "ㅖ = Various combinations such as [ㅔ+ㅡ] = ㅣ+ㅣ+ㅣ+ㅡ (= ###*)" are possible. "ㅑ" is to input the modified alphabet of "ㅏ" or the subsequent alphabet by the repeat selection method, and can be input by two strokes of the button assigned "ㅏ". That is, "ㅑ = ㅏ+ㅏ (= 00)". Here, it can also be seen that "ㅒ = [ㅑ+ㅣ] = ㅏ+ㅏ+ㅣ (= 00#)". The remaining vowels (convex vowels) can be easily entered using a combination of the previously described vowel input. That is, "ㅘ = [ㅗ+ㅏ] = ㅡ+ㅡ+ㅏ (= **0)" to "ㅚ = [ㅗ+ㅣ] = ㅡ+ㅡ+ㅣ (= **#)", "ㅙ = [ ㅗ+ㅏ+ㅣ] = ㅡ+ㅡ+ㅏ+ㅣ (= *0#)" to "ㅟ = [ㅜ+ㅣ] = ㅡ+ ㅏ+ㅣ (=*0#)", "ㅝ = [ㅜ +ㅓ] = ㅡ+ㅏ+ㅣ+ㅣ (= *0##)" to "ㅞ = [ㅜ+ㅓ+ ㅣ] = ㅡ+ㅏ+ㅣ+ㅣ+ㅣ (= *0###)" can do.

In the above embodiment, if the key contents are summarized, input vowels using three vowels "ㅡ", "ㅏ", and "ㅣ", but by repeatedly pressing the button assigned "ㅣ", "ㅣ", "ㅓ", Enter "ㅔ" or "ㅣ", "ㅓ" (since "ㅔ = ㅓ+ㅣ", you can also use "###"), and repeat pressing the button assigned "ㅏ" to " A simple and easy-to-understand vowel by allowing you to enter "ㅏ", "ㅑ", and entering "ㅡ", "ㅗ", "ㅛ", etc. by repeatedly pressing the button assigned with "ㅡ" This is an input method. In the end, "ㅡ", "ㆍ", and "ㅣ" are used, and "ㅔ", "ㅐ", etc., which were unnatural in inputting vowels by repeatedly pressing, are converted to "ㅡ", "ㅏ", and "ㅣ". It was shown that a combination of three modern Korean vowels can be used and the rest of the vowels can be naturally input by using the repeat press. After inputting "ㅡ", the user repeatedly presses the button assigned with "ㅡ" once more to enter "ㅗ", and after entering "ㅣ", the user presses the button assigned with "ㅣ" again to input "ㅓ". It is easy to understand because it is consistent. Vowels other than the ones entered by repeatedly pressing were also easy to understand and were able to be entered naturally in various ways. In addition, the remaining vowels could be entered as a combination of the basic vowel and the subsequent control button ([0] button). It has already been explained that a button assigned with "ㅏ" (a button marked with "ㅏ" in the number "0" in the example drawing) can be associated with "ㆍ" in some cases. Some of the above contents are summarized in Table 8, and if summarized in graph form, they are shown in Fig. 4-30. Not all descriptions are summarized in tables, and not all contents of the table are summarized in drawings. In Figs. 4-30, vowels input by repeated pressing, which is the most essential part, are marked in gray. When there are several methods for the input of the same vowel, it indicates that all can be applied or can be applied selectively. For the intuitiveness of the input method, when the same button is pressed three or more times in one grapheme input, the contents avoided are summarized. In the case of inputting a specific vowel, other embodiments as long as it does not overlap or conflict with the vowel input method of the other embodiments. It is also apparent that the method in can be applied selectively.

collection collection
decomposition 3 vowels combined 4-* Button input value from the yes key pad One ㅏ ㅏ 0 2 ㅐ ㅏ+ㅣ ㅏ+ㅣ 0# 3 ㅑ ㅏ+ㅏ 00 4 ㅒ ㅑ+ㅣor
ㅐ+ㆍ or
ㅐ+ㅡ ㅏ+ㅏ+ㅣ or
ㅏ+ㅣ+ㅏ or
ㅏ+ㅣ+ㅡ 00# or
0#0 or
0#* 5 ㅓ ㅣ+ㅣ ## 6 ㅔ ㅓ+ㅣ ㅣ+ㅣ+ㅣ ### 7 ㅕ ㅓ+ㆍ or
ㅓ+ㅡ ㅣ+ㅣ+ㅏ or
ㅣ+ㅣ+ㅡ ##0 or
##* 8 ㅖ ㅔ+ㆍ or
ㅔ+ㅡ ㅣ+ㅣ+ㅣ+ㅏ or
ㅣ+ㅣ+ㅣ+ㅡ ###0 or
###* 9 ㅗ ㅡ+ㅡ ** 10 ㅘ ㅗ+ㅏ ㅡ+ㅡ+ㅏ **0 11 ㅙ ㅘ+ㅣ ㅡ+ㅡ+ㅏ+ㅣ **0# 12 ㅚ ㅗ+ㅣ ㅡ+ㅡ+ㅣ **# 13 ㅛ ㅡ+ㅡ+ㅡ *** 14 ㅜ ㅡ+ㆍ ㅡ+ㅏ *0 15 ㅝ ㅜ+ㅓ ㅡ+ㅏ+ㅣ+ㅣ *0## 16 ㅞ ㅜ+ㅔ =
ㅜ+ㅓ+ㅣ ㅡ+ㅏ+ㅣ+ㅣ+ㅣ *0### 17 ㅟ ㅜ+ㅣ ㅡ+ㅏ+ㅣ *0# 18 ㅠ ㅡ+ㅏ+ㅏ *00 19 ㅡ ㅡ * 20 ㅢ ㅡ+ㅣ ㅡ+ㅣ *# 21 ㅣ ㅣ #

Next, an example of combining vowels using three vowels "ㅡ", "ㅓ" and "ㅣ" is additionally shown. Among the examples to which "ㅡ", "ㅏ", and "I" are applied, they are similar to Table 8 and related examples, so a detailed description is avoided. In the drawing of 4-* presented as an example, it is assumed that "ㅓ" is arranged in the [0] button (ie, the [0] button is the "ㅓ" button).

Since the vowel "ㅓ" can be entered with one stroke of the button assigned with "ㅓ", "ㅣ" => "ㅏ" (=> "ㅐ") can be entered by repeatedly pressing the button assigned with "ㅣ" . Since "ㅐ = [ㅏ+ㅣ]", if you input "ㅏ = ㅣ+ㅣ (= ##)", naturally "ㅐ = [ㅏ+ㅣ] = ㅣ+ㅣ+ㅣ (= ###)" do. You can naturally enter the vowel "ㅔ = [ㅓ+ㅣ] = ㅓ+ㅣ (= 0#)". As in the above-described embodiment, "ㅖ = [ㅔ+ㆍ] = ㅓ+ㅓ +ㅓ (= 0#0)", and "ㅒ = [ㅐ+・] = ㅓ +ㅔ+ㅓ (= ## You can do it with "#0)". "ㅕ" can be entered by repeatedly pressing the button assigned with "ㅓ". "ㅚ = [ㅗ+ ㅣ] = ㅡ+ㅡ+ㅣ (= **#)" and "ㅘ = [ㅗ+ㅏ] = ㅡ+ㅡ+ㅣ+ㅣ (= **##)" by "ㅙ = [ㅗ+ㅏ+ㅣ] = ㅡ+ㅡ+ㅣ+ㅣ+ㅣ (= **###)" can be done. When "ㅠ = [ㅡ+ㆍ+ㆍ] = ㅡ+ ㅓ+ㅓ (= *00)", it collides with "ㅝ = [ㅜ+ㅓ] = ㅡ+ㅓ+ㅓ = (= *00)" All. In this case, "ㅠ" can be set as "ㅠ = ㅡ+ㅣ+ㅣ (= *##)" as a combination of horizontal/vertical vowels. The input of the vowel "ㅠ" with "ㅠ = ㅡ+ㅣ+ㅣ (= *##)" can be applied in other embodiments.

Alternatively, as suggested above, by repeatedly pressing the button assigned with "ㅡ", make the up and down vowels input as "ㅡ => ㅗ => ㅜ => ㅛ => ㅠ", and "ㅘ = [ㅗ+ㅏ" ] = ㅗ+ㅏ (= **##)", which means "ㅝ = [ㅜ+ㅓ] = ㅜ+ㅓ = ***0". The remaining vowels can be processed as inputs of vowels constituting the vowels, and detailed explanations are avoided.

In the input of the remaining vowels, examples of other embodiments can be similarly used. 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 greatest feature of the above embodiment is that when combining the remaining vowels using three vowels "ㅡ", "ㅓ", and "ㅣ", "ㅣ" => "ㅏ" = > A point to input "ㅐ", a point of entering "ㅓ" and "ㅕ" by repeatedly pressing a button assigned with "ㅓ", and a point that suggests the overall natural vowel combination method. . It was shown that the rest of the vowels can be input in various ways by using the vowels input by pressing once and repeatedly.

collection collection
decomposition 3 vowels combined 4-* Button input value from the yes key pad One ㅏ ㅣ+ㅣ ## 2 ㅐ ㅏ+ㅣ ㅣ+ㅣ+ㅣ ### 3 ㅑ ㅏ+ㆍ ㅣ+ㅣ+ㅓ ##0 4 ㅒ ㅑ+ㅣor
ㅐ+ㆍ ㅣ+ㅣ+ㅏ+ㅣ or
ㅣ+ㅣ+ㅣ+ㅓ ##0# or
###0 5 ㅓ ㅓ 0 6 ㅔ ㅓ+ㅣ 0# 7 ㅕ ㅓ+ㅓ 00 8 ㅖ ㅔ+ㆍ ㅓ+ㅣ+ㅓ 0#0 9 ㅗ ㅡ+ㅡ ** 10 ㅘ ㅗ+ㅏ ㅡ+ㅡ+ㅣ+ㅣ **## 11 ㅙ ㅘ+ㅣ ㅡ+ㅡ+ㅣ+ㅣ+ㅣ **### 12 ㅚ ㅗ+ㅣ ㅡ+ㅡ+ㅣ **# 13 ㅛ ㅡ+ㅡ+ㅡ *** 14 ㅜ ㅡ+ㆍ ㅡ+ㅓ *0 15 ㅝ ㅜ+ㅓ ㅡ+ㅓ+ㅓ+ㅓ *000 16 ㅞ ㅜ+ㅓ+ㅣ ㅡ+ㅓ+ㅓ+ㅓ+ㅣ *000# 17 ㅟ ㅜ+ㅣ ㅡ+ㅓ+ㅣ *0# 18 ㅠ ㅡ+ㅣ+ㅣ *## 19 ㅡ ㅡ * 20 ㅢ ㅡ+ㅣ ㅡ+ㅣ *# 21 ㅣ ㅣ #

Examples related to Table 9 using "ㅡ", "ㅓ", and "I" are examples that correspond to the examples related to the contents of Table 8 among the examples using "ㅡ", "ㅏ", and "ㅣ" to be. As examples using "-", ㅓ', and "I", the examples related to Table 7 have many similar parts to the contents of Table 7, so detailed descriptions are avoided and briefly mentioned. You can make "ㅓ => ㅏ (=> ㅕ => ㅑ)" by repeatedly pressing the button assigned "ㅓ". In other words, the left and right vowels are input by repeatedly pressing the "ㅓ" assignment button. It is the same to make "ㅣ" to become "ㅣ => ㅐ (=> ㅔ)" by repeatedly pressing the assigned button. However, as "ㅔ = [ㅓ+ ㅣ] = ㅓ+ㅣ (= 0#)", you can make "ㅣ => ㅐ => ㅒ" by repeatedly pressing the button assigned to "ㅣ" have. If "ㅡ" becomes "ㅡ => ㅗ => ㅛ" by repeatedly pressing the button assigned to "ㅡ" (that is, entering an upward vowel), or "ㅡ => ㅗ => ㅜ (=> ㅛ => ㅠ)" ( That is, (1-) up and down vowel input), "ㅘ = [ㅗ+ㅏ] = ㅡ+ㅡ+ㅏ (= **00)", but since there is no vowel with "ㅓ" after "ㅗ" You can do it with "ㅘ = **0". The input of the rest of the vowels can be applied similarly, and tables and graphs are omitted.

A summary of the features of the above-described embodiments (Tables 7, 8, 9, and related descriptions) is as follows. Enter vowels using three vowels, "ㅡ", "ㅏ", and "ㅣ", and press the button assigned with "ㅏ" repeatedly to input the left-right vowel (or 1-left-right vowel), " Entering "ㅣ", "ㅓ", and "ㅔ" by repeatedly pressing the button assigned with ㅣ", or entering "ㅣ", "ㅐ", and "ㅔ" can be cited. In addition, when entering vowels using three vowels, "ㅡ", "ㅓ", and "ㅣ", the point where the left-right vowel (or 1-left-right vowel) was entered with the button assigned with "ㅓ", "ㅣ You can enter "ㅣ", "ㅏ", and "ㅐ" by repeatedly pressing the button assigned with "," or the point where you entered "ㅣ", "ㅐ", and "ㅒ". Also, input vowels using "ㅡ", "X", and "ㅣ", but by repeatedly pressing the button assigned with "ㅡ", you can arrange points for entering up-and-down vowels (or up and down vowels or 1-up and down vowels). I can.

In Tables 7, 8, 9, and related examples, a vowel entered by pressing once or repeatedly pressing a button assigned with "ㅡ", "ㅏ", "I" or "ㅡ", "ㅓ", and "ㅣ" It was said that other vowels can be appropriately and selectively used unless they appear in the vowel input and in other embodiments. For example, after entering "ㅜ" in Table 8 (multiple methods can be applied to the input method of "ㅜ"), press the button assigned with "ㅣ" ([#] button in the example) once to " I entered "ㅟ", and pressed again to input "ㅝ", and pressed again to input "ㅞ". This is natural because "ㅣ", "ㅓ", and "ㅔ" are entered by repeatedly pressing the button assigned "ㅣ" in Table 8. Likewise, after entering "ㅗ" in Table 9 (also the input method of "ㅗ" may be a method other than that in Table 9), press the button assigned with "ㅣ" once to enter "ㅚ", and once Press again to input "ㅘ", press again to input "ㅙ". Also, in the example related to Table 9, "I", "ㅏ", and "ㅐ" are inputted as a repeating press of a button assigned with "I". In this way, the use of repeated pressing rather than pressing the left and right buttons in the vowel input can help improve the convenience of input. Since the input methods of "ㅚ", "ㅘ" and "ㅙ" in the related example of Table 9 do not conflict with the input methods of "ㅚ", "ㅘ", and "ㅙ" in the related example of Table 8, In the embodiment, the input methods "ㅚ", "ㅘ", and "ㅙ" in the example related to Table 9 may be applied. Similarly, since the input methods of "ㅟ", "ㅝ", and "ㅞ" in the related example of Table 8 do not conflict with the input methods of "ㅟ", "ㅝ", and "ㅞ" in the related example of Table 8, In the embodiment as well, the input methods "ㅟ", "ㅝ", and "ㅞ" in the example related to Table 9 can be applied.

Here, if you input "1-up and down vowel" by repeatedly pressing the button assigned with "-", it becomes "ㅡ => ㅗ => ㅜ" by repeatedly pressing the button assigned with "-". If you apply the "ㅘ" input method ("ㅘ = [ㅚ+ㅣ] = …") of Table 9 in Table 8, as in Table 8, "ㅘ = [ㅗ+ㅏ] = ㅡ+ㅡ+ㅏ (= Since there is no need to set it as "**0)", you can do it as "ㅛ = [ㅗ+ㆍ] = ㅡ+ㅡ+ ㅏ (= **0)". Likewise, it can be done with "ㅠ = [ㅜ+ㆍ] = ㅡ+ㅡ+ㅡ+ㅏ (= ***0)". In Table 8 and related examples, it is set as "ㅕ = [ㅓ+·] = ㅓ + ㅏ (= ##0)". In addition, "ㅑ" is entered by repeatedly pressing the "ㅏ" button (pressing twice). If you solve this, you can see "ㅑ = [ㅏ+ㆍ] = ㅏ+ㅏ (=00)", so overall 2- In entering 4 vertical vowels (ㅑ, ㅕ, ㅛ, ㅠ), 1-up, down, left and right vowels corresponding to each 2-up and down left and right vowels (i.e., ㅏ, ㅓ, ㅗ, ㅜ) and a modified alphabet It can be seen that the control or subsequent control is combined and entered regularly. Of course, as a control button, a button assigned with "ㅏ" (for example, a [0] button with "ㅏ" in "0" on the keypad) was used. In Table 8, "ㅖ", "ㅒ", etc. are inputted consistently as a combination of the corresponding vowels "ㅔ", "ㅐ" and "ㆍ(variant alphabet control or follow-on control)". You can see that it is entered according to the rules. (Of course, "ㅒ = [ㅑ+ㅣ] = …" could also be entered.) The costumes "ㅔ" and "ㅐ" are called "2-vertical vowels", and "ㅔ" is "1-left+2-vertical" It is called "vowel". "ㅖ" can be called "2-left + 2 vertical vowels". Also, "ㅐ" is called "1-central + 2 vertical vowels", and "ㅒ" is called "2-central + 2 vertical vowels".

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

The above contents are summarized in the form of a table as follows, and if summarized in a graph, it is shown in Fig. 4-32. Not all the contents described are summarized in the table, and not all the contents of the table are summarized in a graph. In the example related to Table 9, the input method of "ㅚ", "ㅘ", and "ㅙ" in the related example of Table 8 is applied, and 1-up and down vowel sounds (ie, " Enter “ㅗ”, “ㅠ”), and enter a table with a combination of 2-up/down/left/right vowels corresponding to 1-up/down/left/right vowels and subsequent control buttons ([0] button assigned "ㅏ" in the example). It becomes almost like 10. However, only the part where you enter "ㅓ => ㅕ" and the part where you enter "ㅏ" and "ㅑ" by repeatedly pressing the button assigned "ㅓ" is different. Do not present it in the form of tables and graphs. As mentioned, since "k" is much more frequently used than "k", it is worse than in Table 10 and related examples.

In Table 10 and related examples, 3 strokes (three strokes of a button assigned with "ㅡ") are required for input of "TT", but since the same button is repeatedly pressed (zero fingering distance), in terms of input convenience, There is no big difference. In addition, among the 9 vowels (ㅏ, ㅣ, ㅡ, ㅓ, ㅗ, ㅜ, ㅕ, ㅐ, ㅔ) occupying about 90% of the frequency of use, the rest of the vowels except for "ㅕ" and "ㅐ" The fingering distance of vowel input is drastically reduced because a combination of adjacent buttons is used to input the remaining vowels (approximately 20% of the total frequency of use) to input the frequency of about 80% or more) with one press of a specific vowel button or repeatedly press Can be seen. In addition, you can enter "ㅡ", "ㅏ", and "ㅣ", which account for 50% of the total frequency of use, in one stroke, so you can use the minimum number of buttons (3 buttons) to keep the minimum number of strokes. Can be seen.

collection collection
decomposition 3 vowels combined 4-* Button input value from the yes key pad One ㅏ ㅏ 0 2 ㅐ ㅏ+ㅣ ㅏ+ㅣ 0# 3 ㅑ ㅏ+ㅏ 00 4 ㅒ ㅑ+ㅣor
ㅐ+ㆍ or
ㅐ+ㅡ ㅏ+ㅏ+ㅣ or
ㅏ+ㅣ+ㅏ or
ㅏ+ㅣ+ㅡ 00# or
0#0 or
0#* 5 ㅓ ㅣ+ㅣ ## 6 ㅔ ㅓ+ㅣ ㅣ+ㅣ+ㅣ ### 7 ㅕ ㅓ+ㆍ or
ㅓ+ㅡ ㅣ+ㅣ+ㅏ or
ㅣ+ㅣ+ㅡ ##0 or
##* 8 ㅖ ㅔ+ㆍ or
ㅔ+ㅡ ㅣ+ㅣ+ㅣ+ㅏ or
ㅣ+ㅣ+ㅣ+ㅡ ###0 or
###* 9 ㅗ ㅡ+ㅡ ** 10 ㅘ ㅚ+ㅣ ㅡ+ㅡ+ㅣ+ㅣ **## 11 ㅙ ㅘ+ㅣ ㅡ+ㅡ+ㅣ+ㅣ+ㅣ **### 12 ㅚ ㅗ+ㅣ ㅡ+ㅡ+ㅣ **# 13 ㅛ ㅗ+ㆍ ㅡ+ㅡ+ㅏ **0 14 ㅜ ㅡ+ㅡ+ㅡ *** 15 ㅝ ㅟ+ㅣ ㅡ+ㅡ+ㅡ+ㅣ+ㅣ ***## 16 ㅞ ㅝ+ㅣ ㅡ+ㅡ+ㅡ+ㅣ+ㅣ+ㅣ ***### 17 ㅟ ㅜ+ㅣ ㅡ+ㅡ+ㅡ+ㅣ ***# 18 ㅠ ㅜ+ㆍ ㅡ+ㅡ+ㅡ+ㅏ ***0 19 ㅡ ㅡ * 20 ㅢ ㅡ+ㅣ ㅡ+ㅣ *# 21 ㅣ ㅣ #

Vowel input by repeatedly pressing the same button except for some vowels (eg, some vowels such as "TT" and "ㅐ" depending on the embodiment) among the 9 vowels belonging to the above 90% frequency of use. Reduced fingering distance and improved input convenience. In the exemplary drawings, a keypad in which a vowel input by repeatedly pressing a specific vowel button can be applied to the corresponding button, and it is obvious that it is included in the scope of the present invention. For example, in the embodiment using “ㅡ, “ㅏ”, and “ㅣ”, in the case of entering “ㅣ” and “ㅓ” by repeatedly pressing the button assigned with “ㅣ”, “ㅣ ㅓ” on the [#] button (Or "ㅣ ㅓ ㅔ") is displayed, and when "ㅏ" or "ㅑ" is entered by repeatedly pressing the button assigned with "ㅏ", "ㅏ ㅑ" is displayed on the [0] button, and "ㅡ" If you enter "ㅡ", "ㅗ", or "ㅛ" by repeatedly pressing the assigned button, "ㅡ ㅗ" (or "ㅡ ㅗ ㅛ") is displayed, but among the Korean vowels that take a geometric shape , The vowels "ㅡ" and "ㅣ" in the basic form (up to "ㅏ" or "ㅓ" depending on each embodiment) are displayed on each button, and the vowels entered by repeatedly pressing are hidden. One of the features of the present invention is that it is easy to understand the input rules while configuring a simple keypad, and it is also a surprising point of Korean Hangul that it can do this.

In the input of lattice and hard consonants, it was said that a combination of the maximum repetition possible number +1 stroke for plain consonant and vowel input can be entered. For example, if "ㅣ", "ㅓ", and "ㅔ" are input by repeatedly pressing the "ㅣ" button, it takes up to 3 times for vowel input, so "ㄲ = ㄱ+ㅣ+ㅣ+ㅣ+ㅣ = 1 It becomes ####". However, since the number of repeated presses to input one character element of the input becomes too high and becomes unnatural, the input of the transformed alphabet (lattice, hard consonant, dropping consonant) among consonants is the button to which the corresponding flat consonant is assigned. The repeat selection method by pressing repeatedly or the modified alphabet 3 + other input method can be applied. Of course, it is possible to make "ㄲ = ㄱ+ㅣ長 = 1#~" by using "long press", which will be described later, but it is good to input by long-pressing the character element required for general Korean input because it interferes with the flow of input. not. (In the example, "ㅣ長" is a long press of "ㅣ" and "#~" is a long press of the [#] button)

It can be seen that there is no vowel input as "0*" in the embodiments of Tables 8 to 10 as for the input of the missing consonant "ㅎ". Therefore, if "ㅎ" is assigned to the [0] button, you can enter "ㅎ = [ㆍ+ㅡ+( ㅇ)] = ㅏ+ㅡ (= 0*)". Of course, the missing consonant "ㅎ" can be entered by repeatedly pressing the button assigned to the consonant "ㅇ", which is regarded as the basic alphabet by applying the repeat selection method (two buttons assigned with "ㅇ"). There may be ambiguity. In Table 7, "ㅑ = [ㅏ+ㅡ] = ㅏ+ㅡ (= 0*)", but if this is not applied (because there are other methods for inputting "ㅑ" in Table 7), the dropout consonant "ㅎ = 0*" can be entered without ambiguity, and if "ㅑ = 0*" is used, "ㅎ = 0**" can be entered without ambiguity. If there is no vowel to input with the [0] button 3 strokes, it was explained in the previous application that the [0] button 3 strokes can be used for the input of "ㅎ", and in this case also ambiguity may arise. For example, the missing consonant "ㅎ" is not necessarily "ㅎ", and as mentioned in the previous application, "b" is the basic alphabet among consonants that do not have a lattice sound and a hard consonant, and "ㄹ" is a modified alphabet ( Or, it can be regarded as a subsequent alphabet), and "ㄹ" can be put as a missing consonant. In the end, it means that the input of the consonant assigned to the button assigned with "ㅏ" can be entered as "0*" which does not exist as a vowel input value.

In the Korean automata of the generalized 2beol-sik keyboard, "ㅢ" is combined by entering "ㅡ" and then "ㅣ". However, since the keyboard has a number of vowel buttons, only some vowels such as "ㅢ", "ㅝ", "ㅞ", "ㅘ", and "ㅙ" are entered as a combination of vowel buttons (ie, vowel buttons Combination rules) are only differences. Vowel combinations using three vowels ("ㅡ", "ㅣ", "ㅏ" or "ㅡ", "ㅣ", ". (below a)" only differ in that more vowels are entered according to the promised combination. Fig. 4-20 is a graph showing the vowel processing process according to the vowel combination based on Table 1. "Start" in Fig. 4-20 means the start of the vowel processing process. When 10*..." is pressed, the vowel processing process starts at the consonant (ie "ㄱ = 1") and then the pressed vowel "0". This is the [a]+[[a]+[ When ㅡ] is input, 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 the next input value is pressed. If [ㄱ] is pressed after [ㄱ]+[ㅡ], 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, if the other parts from Table 1 are included and reorganized in the form of a graph, it is shown in Fig. 4-21. In Fig. 4-21, the vowels marked with a dotted line and the vowels marked with a gray fill are overlapping. As the input method of the vowels marked with a gray fill has improved input efficiency, apply first, and the contents marked with a dotted line are optional. May or may not apply. In Fig. 4-21, the vowel "ㅏ" included in a part of a single vowel (eg "Gwa" to "ㅏ") or element collection (eg "Gwa" to "ㅏ") only at the time of entering the mock indicated by gray fill. It can be seen that you can recognize and input as "ㅏ", and the vowel "ㅏ" used in the rest of the cases reminiscent of ㆍ(below). On the [0] button

It is easy to see that the one marked with has the advantage of being able to associate ㆍ(below a) and "ㅏ" at the same time.

In the implementation of the program, it may be possible to process consonants and vowels recognized by the input values on the keypad as input values of the 2-beol-sik keyboard Hangul automata program, but in view of the infrastructure nature of the character input system and various applications, It is pointed out that it is not so desirable for precise implementation.

In the above, it has been described so that people who know Korean and have basic knowledge of software can fully understand the system, even if they are not in the field of art, but the flow chart will be briefly presented by the old woman. The vowel button (eg [0] button) assigned with a consonant (ie, a dropout consonant) is called a "(dropped out) consonant assignment vowel button" for convenience. Lattice and hard consonants are input according to the control processing method (apply input after control, "ㅋ = ㄱ+ㅡ+ㅡ", "ㄲ = ㄱ+ㅡ+ㅡ"), and dropping consonants (eg "ㅎ") are input. Also, input according to the control processing method (eg "ㅎ = ㅇ+ㅡ+ㅡ" or "ㅎ = ㅏ+ㅡ+ㅡ" or "ㅎ = .+ㅡ+ㅡ").

In the flowchart of Fig.4-22, parts (1) to (4) are the same as the Korean automata in the conventional 2beol-type keyboard, and only parts (A) and (B) marked in gray are It can be seen that this part reflects the characteristics of the input method according to the power system. Part (B) indicates that if 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, part (B) indicated by a dotted line means that it may be omitted. In Fig. 4-22, if the first input value is a dropout consonant assignment vowel button, it is very simple to process it as an input of the dropout consonant assigned to the vowel button, so it is not expressed in order to keep the flow chart concise. Similarly, when the vowel button is pressed as the initial input value, the vowel combination process as a single character is not displayed separately for convenience. The flowchart of FIG. 4-22 is an overview showing that the Hangul input technique and the vowel input technique proposed in the present invention can be operated as simple as possible, and in actual implementation, detailed parts are different 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, depending on whether the "Unicode" system or only the "KSC5601 complete" system is used in the computing environment that currently uses the finished door itself, the details may vary little by little. For reference, Fig. 4-23 is a diagram showing the Korean automata processing process in the generalized 2beol-sik keyboard with the characteristic part ((A), (B) part) removed from the input method shown in Fig. 4-22. However, in 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 the description of the present invention) It is natural that this applies.

The applicant revealed that the vowel input method (vowel combination method) proposed in the present invention can be applied regardless of the specific consonant input method, but also a flow chart in the case of applying the repetitive selection method for consonant input in the old man is shown in Figure 4- Same as 24. The repetition selection method suggested by the applicant in the present invention and in the previous application (selected in the order of flat consonants-lattice consonants-hard consonants, plain consonants-hard consonants-lattice consonants) or the modified alphabet 3 + other input method, etc. It is obvious that the same can be applied to all consonant input methods, as well as similar cases (consonants are identified by repeated pressing of consonant buttons-input of consonant buttons does not affect the combination of vowel buttons). . In identifying consonants in part (4), you can identify consonants according to a specific procedure for a specific consonant input technique. Of course, part (B) is not necessary. In order to keep the flow chart concise, when ambiguity occurs, the part that confirms the previously entered character by using the allegory [>] button or a specific function button is not expressed, but is already generalized and widely used. Even if you are not a worker, everyone knows it, so do not indicate it. Likewise, it is of course possible to use it together with the consonant input method of Samsung Electronics, which inputs consonants by the repetition selection method.

Likewise, in the Hangul input system currently employed by LG Electronics, consonants are identified by combining the consonant button, the "throw button", and the "byeongseo button" (eg "ㄷ = ㄴ+Strategy"). It is obvious that the vowel input technique presented in the present invention can be applied to a consonant input technique for identifying consonants by a combination of a button and a specific function button. Similarly, the input of the consonant button and the specific function button does not affect the vowel combination. Again, the flow chart in this case is simply presented to the old woman as shown in Fig. 4-25.

I believe it has been sufficiently explained so far, but in a system that processes Korean characters by recognizing consonants and vowels in Korean (Hangul), as mentioned in the previous application, the vowel combination technology proposed in the present invention is used regardless of the specific consonant input technology. It is self-evident. Also, if the flow chart is presented to the old woman, it is as shown in Fig. 4-26. It is quite natural, but when a consonant button, a vowel button, or a specific function button is pressed in Fig. 4-26, the vowel combination technique of the present invention is applied even when a consonant of a specific consonant input method can be identified (Fig. 4 -26 in section (4)). 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 assigned by mixing consonants and vowels. Do. For example, in the example drawing, when applying the input of the dropout consonant "ㅎ" with 3 strokes of the [0] button (it has already been pointed out that ambiguity occurs, 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 to the promised time delay or by determining the characters used such as the [>] button). In the case where consonants and vowels are allotted in this way, and when the consonant combination affects the vowel combination, it is already widely used. It is written by the input of a predetermined time delay or a specific function button (eg, right arrow [>] button). It is very obvious that the vowel combination method of the present invention can be applied by deliberately determining the input characters and processing them as being input at the beginning of the word. In the flowchart of Fig. 4-26, when the "letter end button" is pressed, the content being input is definitively recognized, and it is already known that it is necessary to proceed from the "start" state. If presented again in the form of a flow chart to the old woman, it is shown in Fig. 4-27, and in Fig. 4-26, only the part that checks the pressing of the letter completion button is added.

This can be seen as the content clarifying that it can be applied to another part (embodiment) among the contents described in one part (embodiment) in the present application, and this content is also a different part of the present invention (eg, vowels using four vowels). Of course, it can be applied in combination methods, etc.). For example, as previously mentioned, the repetition selection method, the 3+ other input method, and the control processing method are all applied to the input of the transformed alphabet (lattice consonant, hard consonant, dropped consonant, etc.), or some consonants are input. It is obvious that some of the methods can be selectively applied to the vowel combination method (eg, input by control processing method for lattice sound, input by repetition selection method for hard consonants, etc.) can also be applied with this vowel combination method. As described below, it is easy to see that it is applicable to an input system that identifies a specific consonant (promised consonant) by using a "long press" of a specific button. Similarly, as in the input system adopted by LG Electronics, some consonants are input in combination with the selection button and some consonants are input by the repetitive selection method (consonant input does not affect vowel combination). It is obvious that the vowel combination method of the present invention is applicable. The same is the case when the consonant input method of the input system adopted by LG Electronics is slightly modified, and "ㅂ" is placed on a separate button and input by one stroke of that button. (Currently, LG Electronics' hiring system inputs "ㅂ = ㅁ+Strategy")

4.12. Vowel input method using 4 vowels of modern Korean (eg "ㅏ", "ㅣ", "ㅡ", "ㅓ") and Korean input system using the same

Similarly, as shown in FIGS. 4-18 and 4-19, a Korean input system for processing vowels may be configured by using a combination of arbitrary four vowels including "-" and "-". For example, four vowels, including the frequently used vowels "ㅏ" and "ㅓ", can be used. These four vowels have a frequency of about 60% of the total vowels. Table 11 is an example of using a combination of four vowels.

In the case of using three vowels, it can be applied almost the same as the contents described, so detailed explanations are not provided. In Fig. 4-18, the vowel "ㅓ" is indicated inside the number "8", and in Fig. 4-19, it is indicated outside, but as before, this is a view of the same meaning. As in the examples in FIGS. 4-18 and 4-19, when a consonant is not assigned to the [8] button [0] button, conversely, the consonant is assigned to the button assigned "-" and "-". It is as described above that it can be similarly applied even if there is.

In Figs. 4-18 and 4-19, the positions (allocated buttons) of the vowels "ㅏ" and "ㅓ" may be interchanged. In addition, the definition of a vowel combined by four vowels based on the drawings of FIGS. 4-18 and 4-19 may be defined as a combination in which "ㅏ" and "ㅓ" are replaced with each other in Table 11.

The user can operate the [0] button with the vowel "ㅏ" as if it were a lower child button, and the [8] button with the vowel "ㅓ" as if it had two lower children. It is easy to recall this from the shape of the number "0" and the shape of the number "8". After the system detects the starting state of the vowel processing process, the input value can be interpreted as a vowel according to the rules set in Table 11.

Similar to the above, in the input of "ㅏ", "#0" can also be recognized as "ㅏ", and in the input of "ㅓ", "0#" can also be recognized as "ㅓ". . Likewise, the same applies when arbitrary vowels (eg vowels "ㅗ", "ㅜ") instead of "ㅏ" and "ㅓ" are used as 4 vowels together with the vowels "ㅡ" and "ㅣ".

Using four vowel buttons including vowels "ㅡ", "ㅣ" and arbitrary vowels "X" and "Y", the example of entering a vowel by combining four vowel buttons used in modern Korean is as follows: It can be as shown in the table. In the following table, vowels used as vowels "X" and "Y" out of 19 vowels excluding "ㅡ" and "ㅣ" among 21 Korean vowels are buttons with the vowels "X" and "Y" assigned respectively. (In other words, [X] button, [Y] button) It is obvious that each can be input by one stroke.

collection 4 vowels combined X Y One ㅏ ㅣ+X 2 ㅐ ㅣ+X+ㅣ 3 ㅑ ㅣ+Y 4 ㅒ ㅣ+Y+ㅣ 5 ㅓ X+ㅣ 6 ㅔ X+ㅣ+ㅣ 7 ㅕ Y+ㅣ 8 ㅖ Y+ㅣ+ㅣ 9 ㅗ X+ㅡ 10 ㅘ X+ㅡ+ㅣ+X 11 ㅙ X+ㅡ+ㅣ+X+ㅣ 12 ㅚ X+ㅡ+ㅣ 13 ㅛ Y+ㅡ 14 ㅜ ㅡ+X 15 ㅝ ㅡ+Y+ㅣ
or ㅡ+X+X+ㅣ 16 ㅞ ㅡ+Y+ㅣ+ㅣ
or ㅡ+X+X+ㅣ+ㅣ 17 ㅟ ㅡ+X+ㅣ 18 ㅠ ㅡ+Y 19 ㅡ 20 ㅢ ㅡ+ㅣ 21 ㅣ

To further generalize this, vowels can be input using a combination similar to the above table using three arbitrary vowel buttons in Korean. For example, the vowels "A", "B", "X", and "Y" can be used as element vowels, and the remaining vowels can be entered by combination similar to the above. It is also obvious that the vowels "A", "B", "X", and "Y" can be entered with one stroke of a button assigned to each vowel. It would be desirable to use four vowels including "-", "-", "ㅏ", and "ㅓ" for user convenience and minimization of the number of strokes.

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

An additional example of a vowel input method using the four vowels of modern Korean is presented as follows. In the case of using 3 vowels, enter "ㅏ" and "ㅑ" with the repeated press of "ㅣ", and enter "ㅜ" and "ㅠ" with the repeated press of the "ㅣ" button, and vowels " This is an example of entering the remaining vowels by using a combination of horizontal and vertical lines of ㅣ". In the following example, a simple example of using four vowels "ㅓ", "ㅗ", "ㅡ", and "ㅣ" to secure the naturalness of the input rule is as follows. Vowels containing "ㅗ" or "ㅓ" can be naturally entered. As it is similar to the case of using 3 vowels, avoid detailed explanation.

collection collection
decomposition 4 vowels combined (B) When applied, not applicable (A) (B) One ㅏ ㅣ+ㅡ ㅣ+ㅣ ㅑ(A-3) 2 ㅐ ㅏ+ㅣ ㅣ+ㅡ+ㅣ 3 ㅑ ㅣ+ㅣ+ㅣ or
ㅣ+ㅣ+ㅡ or
ㅣ+ㅣ ㅣ+ㅡ+ㅡ 4 ㅒ ㅑ+ㅣ
ㅏ+ㅓ ㅣ+ㅣ+ㅓ or
ㅣ+ㅣ+ㅡ+ㅣ ㅣ+ㅡ+ㅡ+ㅣ 5 ㅓ ㅓ 6 ㅔ ㅓ+ㅣ ㅓ+ㅣ ㅡ+ㅣ+ㅣ ㅟ(B), ㅠ(B) 7 ㅕ ㅡ+ㅓ 8 ㅖ ㅕ+ㅣ ㅡ+ㅓ+ㅣ 9 ㅗ ㅗ 10 ㅘ ㅗ+ㅏ ㅗ+ㅣ+ㅣ 11 ㅙ ㅘ+ㅣ ㅗ+ㅣ+ㅣ+ㅣ 12 ㅚ ㅗ+ㅣ ㅗ+ㅣ 13 ㅛ ㅣ+ㅗ 14 ㅜ ㅡ+ㅡ 15 ㅝ ㅜ+ㅓ ㅡ+ㅡ+ㅓ ㅡ+ㅣ+ㅡ or
ㅡ+ㅣ+ㅡ+ㅣ 16 ㅞ ㅝ+ㅣ ㅡ+ㅡ+ㅓ+ㅣ ㅡ+ㅣ+ㅡ+ㅣ or
ㅡ+ㅣ+ㅡ+ㅣ+ㅣ 17 ㅟ ㅜ+ㅣ ㅡ+ㅡ+ㅣ ㅡ+ㅣ+ㅣ ㅔ(B), ㅠ(B) 18 ㅠ ㅡ+ㅡ+ㅡ ㅡ+ㅣ+ㅣ ㅔ(B), ㅟ(B) 19 ㅡ ㅡ 20 ㅢ ㅡ+ㅣ 21 ㅣ ㅣ

4.13. How to enter a specific (single) vowel by continuously inputting a specific button assigned to a specific vowel element (or element vowel)

In the illustrated drawings (FIGS. 4-5 to 4-9), it is assumed that the vowel element buttons are not assigned aspirated/acne control and dropped consonants, and are used only as vowel element buttons. Therefore, it is assumed that there is a separate control button or that aspirated and hard sounds are selected by repeatedly pressing the button assigned to the basic consonant, and the dropped consonant is selected by repeatedly pressing the button assigned to the consonant that is regarded as the basic consonant. .

The frequency of use of Korean vowels is in the order of "ㅏ", "ㅣ", "ㅡ", "ㅓ", "ㅗ", and "ㅜ", and these 6 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 a vowel element "." that does not exist as a vowel by itself. Furthermore, in the process of combining vowels (from start of combining vowels to end of combining vowels), it is possible to detect a continuous input of only the same vowel element button so that a certain promised single vowel is recognized.

When the button assigned with the vowel element "ㅡ" is pressed once, the vowel "ㅡ" is recognized, and when pressed one more time in succession, "TT" can be recognized. For example, when entering "Gum", it is possible to enter "1*05" as a combination of vowel elements, but it is also possible to enter "1**5". Likewise, when the button assigned with the vowel element “ㅣ” is pressed once, “ㅣ” is recognized, and when pressed again, “ㅏ” can be recognized. For example, when entering "persimmon", it means that it can be set to "1#05" or "1##5".

As described above, when entering a single vowel using the button assigned with the vowel element ".", it is recognized as an intermediate process of entering the vowels "ㅓ", "ㅕ", "ㅗ", "ㅛ", etc. Until you recognize the end of the process, you just "." Will be able to be printed. However, in the case of using the buttons assigned to the vowel elements "ㅡ" and "ㅣ", the vowel element (or element vowel) "ㅡ after the consonant (ie, the vowel combining process start state) is "- By using the property that "" does not appear consecutively (ie,'ㅡ+ㅡ') and vowel element "ㅣ" does not appear consecutively (ie, "ㅣ+ㅣ"), the promised vowel is It can be recognized and printed definitively. For example, when entering "1##(5)", depending on the input, "ㄱ => group => can be displayed as (=> reduced)". In such a case that can be definitively recognized, other vowel elements can be additionally combined, as in the case of input by vowel element combination. That is, in the illustrated Fig. 4-5, "1**# = ear" and "1### = dog". If a specific vowel is recognized by repeatedly pressing the button assigned to the vowel element 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 starting state of the vowel combination process.

In addition, it is possible to input another single vowel by pressing the button assigned to the vowel element three or more times. For example, if a button assigned with "ㅡ" is pressed 3 times, it may be able to recognize "ㅠ" (here, "Goo" can be entered as "Gyu+ㅣ= 1***#") . Likewise, if the button assigned with "ㅣ" is pressed 3 times, as mentioned, "ㅐ" can be recognized, or "ㅑ" can be recognized. (Of course,'ㅐ' and'ㅑ' are compatible here. If you enter'ㅐ' in 3 strokes, you can enter'ㅑ' in 4 strokes). Likewise, "." This assigned button allows you to input "ㅕ" with 3 strokes and "ㅛ" with 4 strokes. (Here, it is assumed that dropping consonants are not assigned to the button to which the vowel element "." is assigned, but only the vowel element is assigned.) As mentioned in the input of the dropping consonant, in the vowel combination start state, see Fig. 4-5 As a standard, the vowel element "." can be definitively recognized as "1000 = chaff" and "10000 = bridge" by using the property that cannot appear more than three times in a row. However, in the case of three or more inputs, there is no significant difference in terms of inputting convenience diagram or inputting as a combination of vowel elements, and lack of intuition in the input method.

It can be seen that the above result improves the input convenience of some vowels that are frequently used. In summary, it can be seen that the repetitive selection method is applied by placing a specific vowel (ㅜ, ㅠ, ...) with similar shape as the successor vowel of "ㅡ". Likewise, it can be seen as applying the repetitive selection method with a specific vowel (eg, ㅏ, ㅐ, ㅑ, ... or ㅏ, ㅑ, ㅐ) as the successor vowel of "ㅣ". Likewise, it can be seen that a specific vowel (eg, ㅓ, ㅗ, ㅕ, ㅛ, ...) can be entered by the repeat selection method using the button assigned with ".". In the method of using the four vowel elements, enter "ㅓ" and "ㅗ" by repeatedly pressing the button assigned the vowel element ".", and repeatedly press the button assigned the vowel element ".." It is also possible to input "ㅕ" and "ㅛ" by.

Using the button assigned to the vowel element "ㅡ", in the order of "ㅡ, ㅜ, ㅠ, ...", "ㅣ, ㅏ, ㅐ,..." or "ㅣ, ㅏ, ㅑ" for "ㅣ" In the order of ", ㅐ, ...", and using the button assigned with the vowel element ".", the user has to enter the vowels "ㅓ" and "ㅗ" starting with the vowel element ".". It is for reference only, but is only an example, and other specific vowels may be input in a different order.

Here, the concept of the present invention can be utilized even in a method other than a method of using three or four vowel elements one step further. For example, in an input system where 6 vowels are assigned to 6 vowel buttons, such as "ㅡ", "ㅣ", "ㅏ", "ㅓ", "ㅗ", and "ㅜ", "ㅑ" is [ ㅏ] button 2 strokes, "ㅕ" with [ㅓ] button 2 strokes, "ㅛ" with [ㅗ] button 2 strokes, and "ㅠ" with [TT] button 2 strokes. Likewise, it is possible to input "ㅐ", which is more frequently used than two strokes of the [ㅏ] button. Again, since the same vowel among the vowels "ㅏ", "ㅓ", "ㅗ", and "TT" does not appear consecutively, it can be recognized immediately upon input. If 10 basic vowels can be entered in this way, the remaining vowels can be entered as a combination of these 10 vowels (e.g.'ㅝ = ㅜ+ㅓ' or'ㅝ = ㅠ+ㅣ','ㅞ = ㅜ+' ㅓ+ㅣ'). Likewise, it is possible to input other vowels (eg, compound vowels, extended vowels) with more than three strokes of a specific vowel button.

This means that there is no button to which the vowel element "." is assigned, and the vowel "ㅑ" can be input by the repeat selection method with the following alphabet with "ㅏ" as the basic vowel. This, too, can provide a feeling of familiarity to the user through input similar to the process of taking notes according to the push of a button, along with the convenience of input by repeatedly pressing without ambiguity. In addition, by adding a button to which the vowel element "." is assigned separately, it is of course possible to input it by repeatedly pressing the element collection button or combining it with the vowel element "." even in the input system equipped with 7 vowel buttons. For example, "ㅕ" can be entered in combination with the [ㅓ] button two strokes or the [.] button and the [ㅓ] button.

5. How to overcome ambiguity through indexing

When applying the repetitive selection method, multiple words may be expressed as a single code, resulting in ambiguity. In the input example of Fig. 4-1, it was pointed out that there is an ambiguity in which "goi" can be recognized as "good" and "good" as "goi". However, in general, words are entered in units of words. For example, the word "great" exists, but the word "goijang" does not exist. In Fig. 4-1, both have the same code value. Therefore, on the terminal (client) or server side, indexes for words that may cause ambiguity about a specific keypad and specific alphabet input method are prepared and registered. When "Great" or "Goijang" is entered, when both cannot be distinguished by time delay, etc., if "very" is registered as the correct word in the index, the word the user wants to input (for convenience, hereinafter "Target word") is what you can see is "great". This applies only when ambiguity that cannot be distinguished by the system occurs, and if it is possible to distinguish it 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 that it should be followed. Do. In other words, if the user intentionally cuts off (using a time delay or blank, or using the right-hand button or other specific buttons), even if it is a word that is wrong in meaning, the word is the target word, so Should print ".

The way to prepare the index is to register only the correct words ("Great" in the example) for words in case ambiguity may occur, or you can register only the wrong words ("Goijangi" in the example). . Also, it is okay to register both the correct and the wrong words, and the system only needs to have information about which words in the index are correct or wrong words.

This can be applied in all cases where the repetitive selection method is applied in the keypad. For example, an ambiguity such as "Country <=> Guka" arises in the input method of Samsung Electronics in Korea, but the same can be applied here. In addition, similar to Fig. 4-1, when a pair of letters is placed on each button, and a consonant 1 stroke, a pronounced 2 stroke, a hard sound 3 stroke, and a vowel 1 stroke are selected, and the syllable completion button is pressed in units of syllables (characters). It can also be applied to When the user inputs "Awesome", even if the "Great" is temporarily output, it can be corrected to "Awesome" by referring to the index at the moment the word ends (for example, entering a blank space).

At this time, if the index of the word exists on both the client side and the server side, the index of the client side is firstly searched to try to identify the correct word, and when the identification fails, the index of the server side is secondly searched and It can be used to identify words.

To distinguish the unit of a word, as anyone can think, it is only necessary to identify it by the element that separates the word from the word. For example, you can think of the case between a space and a space, between the beginning of a word and a space, between a space and the end of an input, between a space and a mode switch. Since determining the correct word by referring to the index is performed in units of words, index reference is made when an element that distinguishes the word is input, and the correct word can be determined.

This can be applied in all cases where ambiguity occurs by applying the iterative selection method. For example, in Samsung Electronics' method currently used in Korea, ambiguity may occur if the last and first consonants belong to the same button. For example, "country" <=> "guka". When entering a code for each alphabet, it is entered without recognizing the syllable (character) unit. In fact, in many cases, if you unconsciously input "country", it becomes "guka". In this case or even by a time delay, if it is not possible to know which of the two words is the target word, the system (terminal or server) can find out the target word by referring to the index. However, in this case, even if the final "a" of "guk" and the initial "a" of "a" are pressed in succession, in most cases, the target word is often "country", so the index is indexed regardless of time delay. The method of identifying the target word by reference can 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 repetitive selection method. For example, in English input or in the English mode of another language keypad, when there is an ambiguity that is not known whether the input of [2]-[2]-[2] is "AB" or "BA", "AB" If "is registered in the index with the correct word, it can be recognized and provided to the user as a target word. If a plurality of ambiguity-occurring words are all registered in the index with correct words, the word with high frequency of use is primarily provided to the user, and the user can finally determine the target word.

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

The method for allowing the user to determine the target word is to arrange a plurality of words recognized as correct words on the display in the order of frequency of use (or priority order), and use the number buttons corresponding to the displayed order by scrolling up and down. This allows the user to determine the target word. Alternatively, by selecting a control (referred to as "next word control" for convenience) that displays only words with high frequency use and displays the next word if it is not the target word, the next most frequently used word is displayed. Also, if it is not the target word, you can continue to search the target word by selecting the next word control again. In this case, after searching for the target word, the target word can be confirmed by pressing any other button (for example, selecting a different alphabet, blank, mode change, etc., not selecting the next word control selection, but by pressing all buttons). I can.

The selection of the next word control can be applied to either the "partial whole selection method" or the "repetitive selection method (standard/simple)" described in the previous application. If 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 that specific button.

6. Simple Code How to use and shortened input method / parallel input method

6.1 Alphabet-related simple code generation method

When accessing the information system using an information communication terminal, it is necessary to enter the alphabet. Alternatively, the alphabet to be entered can be entered into numeric codes. In miniaturized information communication terminals, there are many cases where a keypad-type interface is usually employed. The code referred to here refers to all kinds of codes, and representative examples include telephone numbers, securities (listed companies) codes, city codes, department codes, subway station codes, and bank codes. The advantage of coding and inputting various names is that input can be simplified.

Information and communication terminals include all types of information and communication terminals such as PCs, mobile communication devices, smart phones, PDAs, two-way text transmission and reception devices, and ATMs (automatic teller machines). In addition, it covers terminals that do not have communication functions such as electronic notebooks. The information system includes all types of systems such as systems that can be accessed visually through GUI, as well as systems that can only be accessed with sound, such as ARS. In addition, the system narrowly refers to the server-side system, and broadly includes the terminal's client software compatible with the server system.

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

Simple naming is to designate a number associated with a word or phrase (the word or phrase is collectively referred to as "phrase" below) to be coded as a code. For example, in the case of the Korean company name code, the code of “Gasan Electronics” is referred to as “1799” associated with a, ㅅ, ㅈ, ㅈ as a simple code based on Fig. 4-2. In this case, it is possible to make it easier to know the simple code of a specific word by highlighting the ㄱ, ㅅ, ㅈ, ㅈ related to the simple code "1799" in "Gasan Electronics", and furthermore, the simple code from such phrases. Can also be extracted. In the case of simple naming, since a number associated with a certain alphabet belonging to a word to be coded is determined as a code, it is not necessary to set the code of the example “additional electron” to “1799”. For example, just as the simple code of "stocks" can be the value associated with ㅈ, ㅅ, ㅣ, ㄹ, in the case of Gasan Electronics, for example, "1729" related to ㄱ, ㅅ, ㄴ, ㅈ It can be done with, or "1749" related to a, ㅅ, ㅓ, ㅈ, or "13294293" related to the entire alphabet constituting "additional electrons". For convenience, a simple code related to the entire alphabet constituting a phrase is called "All-related simple naming". For convenience, designating a simple code related to some alphabets of a specific phrase is called "Partially related simple naming". In any case, simple naming (i.e., simple code) can be viewed as specifying a code in association with the alphabet constituting the phrase in units of phrases. This is also applicable to languages other than Korean. For example, in "captain", "2786", which is related to the consonant "CPTN", can be used as a simple code, which is a partially related simple code, which will be called a "consonant related simple code" for convenience.

When 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, the abbreviated simple code is used, but in order to minimize the duplication of the defined simple code and the simple code corresponding phrase, and to add convenience in use, a simple code that associates the first vowel and consonant can be considered. For convenience, it is named "Simple code based on first vowel + consonant". The first vowel + consonant-related simple code has the advantage of mechanically generating a simple code for a specific word, like other simple codes.

Not only words but also phrases can be coded by simple naming. The simple code of “8314” mapped to ㅇ, ㄷ, ㄱ, and ㄹ can be made by using the letter (syllable) that best implies the meaning in the phrase "Where are you going" as an example in the previous application. In the case of English, "3886", which is related to d, t, t, and n, which have a phonetic value in "date tonight" as an example in the previous application, can be used as a simple code.

Initial naming is a special case of some related simple naming. In the case of Korean, initial naming may be a method of designating a number mapped to an initial consonant (first consonant) based on a syllable (character) as a code. For convenience, this is referred to as "syllable initial naming". In the case of "Gasan Electronics", the initial code based on syllable-based initial naming becomes "1799", which is related to the consonant initiality of each syllable (letter). The syllable-based initial naming can also be applied to languages other than Korean. For example, in the case of English, an initial code based on syllable-based initial naming of the word "entertainment" may be "3886" associated with e, t, t, and m. The syllable-based initial naming can be more useful in the case of Korean, in which one syllable constitutes 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 a single letter. In the case of Chinese, the syllable standard initial code of Beijing (Beijing: the first'e' with a four-tone sign and the last'i' with a two-tone sign) is "25" related to b and j based on Fig. 1-1. Becomes "14" based on FIGS. 10-1 to 10-4.

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

The simple code (the whole simple code, the partial related simple code) and the initial code (syllable-based initial code, word-based initial code) are collectively referred to as "simple code (ie, simple code in a broad sense)" or "shortened 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 you can use it easily.

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 applied character input method, and it can be seen that a numeric value corresponding to a phrase in alphabetical units is used as a code. In the case of "Seoul" as an example in the earlier application, the full code according to the partial-total selection method (referred to in the earlier application) is "7745888944" based on Fig. 4-2. If the standard iteration selection method (mentioned in the previous application) the full code is "7448884". If a keypad different from that of Fig. 4-2 or another alphabet input method is applied, there will be a full code value accordingly.

6.2 Traditional Chinese Hanja input method

As for Chinese input method, it is common to input English corresponding to Chinese pronunciation, and select and input the corresponding Chinese character when convertible Chinese characters are made using the "Hanja conversion key". That is, when Chinese pinyin is input in Roman alphabet, the system searches for the corresponding Chinese character and provides 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 (that is, when the client side has a specific phrase and a simple code value corresponding to the specific phrase), the phrase corresponding to the input simple code is transmitted to the server side. I can. Even if the simple code can be decoded by the client, if the server requires a simple code according to the nature of the application, the simple code itself (i.e., a number sequence) can be transmitted to the server side. Interpret it. It is said that the decoding of the simple code can be done on the client side or on the server side.

When a simple code is defined and used for a plurality of phrases, there may be multiple phrases corresponding to the same simple code. This ambiguity that can occur between simple codes is called "second order ambiguity" for convenience. In this case, it is possible to create and store a unique code value by adding a serial number to a simple code having the same value inside the system, but a second ambiguity occurs because the user mainly uses a simple code related to a specific phrase. In this case, it is natural that the system should be able to recommend such phrases to users according to their usage priority. In the case of having the same simple code as a different phrase, the serial number can be used as a priority for recommending the user to the simple code by attaching a serial number according to the priority according to the frequency of use of the phrase inside the system. Of course, it is not necessary to attach a serial number, and the system may have a separate priority information, and it is just an example of how to do so.

For example, if the simple code of "Stock Information" is the same as "9196", which is a syllable-based initial code and "9196", which is also the syllable-based initial code, the frequency of each word You can attach a serial number and use that serial number as a priority to recommend to users. If the frequency of use of "securities information" is high, priority can be given to "securities information" = "91961" and "stock information" = "91962". Similarly, if the syllable-based initial code of 先生 (xiansheng: vowel a is the first tones) and 學生 (xuesheng: the first e is the second tones) is the same as “97”, a serial number is 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 xuesheng, 先生 (xiansheng) = 971 and 學生 (xuesheng) = 972 can be used. The simple code generated by adding a serial number in this way will be referred to as a "unique simple code" for convenience, and a simple code with redundancy without a serial number is simply referred to as "simple code". It is called "code".

In the example of 先生(xiansheng) and 學生(xuesheng), if the user enters only “97”, the system provides 先生(xiansheng) and 學生(xuesheng) to the user, allowing the user to double-select. If “971” is entered from the beginning, the system can recognize it as “先生(xiansheng)”.

Here, by emphasizing the “x, s” used as the basis of the syllable-based initial code, it is possible to give a better visual effect to the user. One of the methods of emphasizing and displaying it is a capital letter such as XianSheng. Further, the system can interpret the simple code “97” from the capitalized words.

6.4 Simple Code Use Case

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

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

Here, since the syllable-based initial codes of Seoul and Suwon are the same, in order to avoid this, in the system, simple codes such as "Seoul = 781" and "Suwon = 782" can be made unique by adding consecutive numbers to avoid this. When the user sends only "78" to the system, the system gives appropriate feedback (eg, provides a list of Seoul and Suwon or informs them by voice), allowing the user to choose between Seoul and Suwon. If the user recognizes this from the beginning and enters "781", the system can recognize it as "Seoul".

If the server-side system does not need the simple code "78" but needs the word "Seoul" itself, the client side interprets the simple code "78" and transmits the "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 inputted simple code itself can be transmitted to the server side.

Another example of assigning a simple code (a simple code related to the whole, an initial code based on a syllable, a simple code related to consonants, and a simple code related to consonants + consonants) for a city name, see Fig. 1-1, Beijing (Beijing). ), the syllable reference initial code becomes “25” associated with b and j, the entire associated simple code becomes “2345464”, and the consonant associated simple code becomes “2564” associated with b, j, n, g.

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

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

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

An example of a bank code is as follows. This can be usefully used in ATMs and various financial information systems.

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

Here, it is obvious that when the user inputs such a predefined simple code, the client (terminal) interprets it and shows it to the user, so that it can be used for phrase input. This is called the "shortened input method", and will be described in detail with the "parallel input method".

6.5 Automatic priority reassignment according to selection frequency

Furthermore, if the priority of “Stock Information” and “Sovereign Information” was first and second respectively, but the number of times a specific user selects “Sovereign Information” is remarkably large, the priority of “Sovereign Information” Can be adjusted to be higher than the priority of "securities information". As described, there are various methods, but this can be realized by changing the serial number. If the system has priority information separately, it is possible by changing the priority information.

The criteria for determining whether the number of times to select “sovereign information” is remarkably large may be determined by the system or may be (re)designated by the user. For example, if a different priority is selected at least 8 times out of 10 times from the previously designated priority, the existing priority 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 it can be considered the same when “stock information” and “securities information” are changed to “先生(xiansheng)” and “學生(xuesheng)” respectively.

6.6 Simple code automatic designation and simple code-related alphabet highlighted

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 generating simple codes as described above, so when users designate simple codes for specific phrases, simple codes are generated. When a specific phrase is entered while the rule is specified, the corresponding simple code can be automatically extracted and saved in the system. In addition, it is possible to increase the convenience of use by highlighting and displaying the alphabet associated with the simple code. In the case of English, the alphabet related to the simple code is highlighted and displayed, but can be displayed using uppercase letters.

Also, in the earlier application, "shortened input method" and "shortened/full parallel input method" were suggested. The simple code for shortened input can be defined in the system, the user can change it, and the user can designate a simple code for a new phrase.

In deciding a simple code for a new phrase, the rules for generating simple codes, such as the whole series of interest code, partial 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, if the user wants to use the word-based initial code as a simple code when generating a simple code for "dance with the wolf", enter "dance with the wolf" in the simple code generation mode, and You must enter the word-based initial code "3983". Likewise, in generating a simple code for "securities information", if you want to use the syllable-based initial code as a simple code, you must enter "Stock Information" and then "9196" in the simple code generation mode.

However, if the user designates a simple code for a specific phrase, by storing the type of simple code desired by the user in the system and inputting the phrase to generate the simple code, it is not necessary to enter the code for the specific phrase. Simple codes can be automatically assigned. In the above example, the system sets that the syllable-based initial code is used, and by entering only the “stock information”, the simple code for “stock information” can be automatically designated “9196”. Similarly, it is possible to set the system to use syllable-based initial codes, and input 先生(xiansheng) so that the simple code for 先生(xiansheng) is automatically designated as “97”.

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

6.7 Shortened input method and parallel input method of phrases using simple code

When entering a simple code (the initial code is a special case of the simple code, it is considered to be included in the simple code, unless otherwise noted), from the system (client-side system or server-side system) to the phrase corresponding to the simple code. It is possible to recognize and process. 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 input of words.

In fact, in the foreign alphabet input method, an index with "all related simple codes" for each word is stored in the terminal (client system), and when the user enters the code, the corresponding word is displayed according to the priority of each word A character input system is implemented by enabling 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 will be referred to as "the whole association shortened 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”. 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... If you enter “”, the system initially provides “off” to the user, but if “6228” is entered, “meet” is displayed.

Comparing the method of Tegic and Zi with the method of entering the alphabet on the keypad suggested by the applicant, the method of entering the alphabet of the applicant gives a unique code in alphabetical units, and the target alphabet or target phrase can be entered by the full code. The foreign method mentioned above is to assign a simple code related to the whole word unit, and to input the target word by the simple code.

The disadvantages of foreign methods are that only predefined words can be entered by assigning a code in units of words. In case of having the same code as a different word, use a toggle button or a move button to input words that are not used frequently. By selecting and confirming the target word, it is not easy to input it, a word other than the target word may appear temporarily during input, and it takes up a lot of system storage capacity and requires a lot of cost to implement.

Here, it is pointed out that a simple code (some related or all related) is assigned to a common phrase (a concept including all common words or common phrases), and the target phrase can be entered using the simple code. It goes without saying that the simple code for the common phrase may be predefined in the system and provided to the user, or it must be arbitrarily designated by the user. Or, the user must be able to arbitrarily modify the simple code defined in the system. What 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, a method of inputting a target phrase using a simple code (including all of the partial related simple code, all related simple code, and initial code) is referred to as a "shortened input method" for convenience, and a method of entering the target alphabet by full code For convenience, it is called "full input method" compared to the shortened input method. In addition, as described below, the shortened input method and the full input method can be applied in parallel, and the method of applying the shortened input method and the full input method in parallel is described as "shortened/full parallel input method" or simply " It will be called "parallel input method".

Among the full input methods in which a unique code is assigned to each alphabet and the target alphabet can be input by entering the code, the ambiguity arising from the use of the repetitive selection method is referred to as "first-order ambiguity" or "alphabet ambiguity" for convenience. I decided to call it. On the other hand, in the method of assigning a code to all words as in foreign methods and allowing the target word to be input through this code, there is an ambiguity that there are several different words for the same code. It will be referred to as "differential ambiguity" or "phrase ambiguity". In the present invention, simply referring to ambiguity means first-order ambiguity.

A specific input value is primarily interpreted as a simple code (that is, a shortened input method is applied primarily or a shortened input mode is applied as the basic input mode), and if there is no simple code corresponding to the input value, the second is a full code. Scenarios such as recognition as (i.e., applying the full input method secondarily) can be configured, and on the contrary, the input value is primarily checked to see if the full code is achieved (i.e., the full input method is applied or the basic Scenarios such as applying the full input mode as the input mode) and recognizing the full code as a simple code (that is, applying the shortened input method secondarily) are possible. Firstly interpreting the input value as a simple code can be seen as applying the "shortened input mode" as the basic input mode. Conversely, firstly interpreting the full code as the basic input mode is "full input mode". It can be seen as applying. For users who mainly use common phrases in character input, it is desirable to apply the shortened input method first (that is, use the shortened input mode as the default input mode), and those who do not use the full input method first. (That is, it would be desirable to use 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 if a simple code is input, the input value can form a full code, 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" (the syllable-based initial code is used), and when entering this As it is regarded as a full code, it can be recognized as "female". This occurs when the first letter of the second and third letters corresponds to the same button, such as "corn", "corn", "infinity", "warr", "excellent", "wajangchang", and "woodangtang". 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 that even when 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.

This third-order ambiguity can also be overcome by a toggle method or a method of selecting from a list similar to the existing method. Alternatively, there may be other methods, such as allowing you to switch from full input mode to shortened input mode or from shortened input mode to full input mode on a word-by-word basis before entering input values that may cause such ambiguity. This is done by placing a "ah/ah" control as suggested in the applicant's earlier application and selecting it by placing a word-based Hiragana/Katakana conversion control, entering a single word of katakana in hiragana mode, or entering a single word of hiragana in katakana mode. It's similar to allowing you to do it. For example, if the default input mode is the full input mode, the system recognizes it as a simple code from the beginning and refers to the index for the input value that is input after selecting it by setting the “short/full” control. The target word can be provided to the user. Even if the shortened input mode is used as the basic input mode, the input value input after selecting the "shortened/full" control can be recognized as a full code from the beginning and processed. Likewise, the “shortened/full” control may be pre-entered or post-input for the target word, but in this case, it would be convenient to pre-enter it.

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

When the full input method is set as the basic mode and the parallel input method is applied, the input value is converted to a simple code at the point where it is judged that the full code cannot be formed by examining whether the input value forms a full code each time the code is entered. It is possible to double the efficiency of the parallel input method by showing the corresponding phrase to the user by referring to the simple code index. In the case of applying the parallel input method with the shortened input method as the basic mode, the same time as when each code is entered, the input value and the index are compared, and the moment it is confirmed that there is no word matching the input value in the index, this is the preset full input method. It can be processed by judging with the full code of. This means that the third-order ambiguity occurring in the middle of the input can be removed at the beginning of the input by applying the rules in each full input method. This can be applied to the case of using an alphabetic input method not suggested in the previous application as a full input method. For example, based on the full input method (standard repetition selection method, partial selection method) suggested in the previous application, for example:

In the case of Korean, for example, when the reference repetition selection method is applied based on Fig. 4-2 as the full input method, the second input value and the third input value of all syllables by the full code must always have the same value. If this condition is violated, the input value can be determined and processed as a simple code. When it is allowed to treat a pair of consonants as a combination of basic consonants, the criteria for judging accordingly may be applied. This is applicable in all cases where the standard iteration method is applied.

In addition, in all languages, when applying the partial full selection method as the full input method, two input values correspond to one alphabet, and the second input value is limited to the first input value among the two input values. have. For example, in the case of English, in the case of using only the left and right straight line combination as shown in Fig. 1-1, if the number is not selected by the partial selection method, the buttons in the first row ([1], [2], [3] ) Is used as the first input value corresponding to one alphabet, the value that can come as the second input value is also the button ([1], [2], [3]) in the first row. Similarly, if [2]+[1] is entered and then the second row of buttons ([4], [5], [6]) is pressed again, the next possible value to form the full code is also the second row. It is one of the buttons ([4], [5], [6]). As soon as the input value violates this, the system regards the input value as a simple code, and a word corresponding to the simple code can be recommended to the user according to priority. For example, 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 as shown in Fig. 5-3, when the user inputs 4357 simple code of “help”, the second As soon as the input value 3 is input, the system recognizes that the input value does not form a full code, and the input value can be treated as a simple code.

If the partial whole selection method is applied to Fig. 4-2, only the [1] or [2] button is the next button that can come to the input of the first [1] button to form a full code. If this is violated, it is determined that the input value is a simple code rather than a full code, and a target word corresponding to the input value can be recommended to the user according to priority by referring to the index. As shown in Fig. 1-3, when 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 grid forming a vertical adjoining combination. Even in this case, if the [7] button is pressed to form a full code for one alphabet, the next button is the button in the third row ([7], [8], [9] ) Or the adjacent top and bottom combination (button [4]) can come, so if it is violated, the input value can be processed as a simple code. This is applicable to all languages in the case of applying the partial selection method suggested in the previous application.

For example, in the simple code index based on Fig. 1-1, the simple code of Beijing is stored as “25” as the syllable-based initial code, and the partial full selection method is used as the 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 the moment [5] is input, the input value “25” is the full code. (Because the button of the right and left straight combination that can be followed by [2] is one of [1], [2], [3]), refer to the simple code index and refer to the input value “25 It is able to provide users with “Beijing” corresponding to “”. In the case of Chinese, it is possible to provide a user with a Chinese character (漢字, that is, 北京) as a phrase corresponding to the specially illustrated simple code “25” (since the Chinese character “北京” is the target word). For languages that use phonetic characters other than Chinese, the system will provide the user with “Beijing” corresponding to the simple code “25”. 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 desired phrase. Fig. 5-4 Refer to.

In the end, applying the parallel input method as shown in Fig. 5-4 is to register simple codes for frequently used words such as “Beijing” in the index, and execute the general full input method and shortened input in parallel without mode switching. However, when entering a word registered as a simple code, it is possible to enter a word with a small number of strokes.

In the case of Fig. 4-5, only one basic consonant per button is allocated, so when using a syllable-based initial code that can be used universally in Korean as a simple code, when applying the short-cut input method and the full input method in parallel. There is also a good characteristic that can be entered without third-order ambiguity. In other words, if the user inputs the syllable-based initial code when applying the parallel input method, the input value cannot be made full code from the second input (when inputting the hard sound or aspirating sound by the control processing method). It is possible to search for and recommend appropriate words according to priority to the user. The same is the case with full code input.

As an example above, when applying the parallel input method, it is one of the "cores" of the present invention to be able to determine whether an input value is a simple code or a full code during input. This applies not only to the case of using the full input method suggested by the applicant, but also to the case of using another full input method. As an example, there was a method of inputting an alphabet by combining a first button to which each alphabet is assigned and a second button corresponding to the order of the alphabet in the first button. That is, in Fig. 1-1, P = [7] + [1] was entered. 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 regards the input value as a simple code. You can handle it. In particular, the full input method proposed by the applicant has a good characteristic that it is easy to know whether the input value constitutes a full code when applying the parallel input method as in the above example.

Also, as mentioned in the applicant's earlier application, the interpretation of the simple code or the full code may occur on the client side or the server side. In order to look up the index to overcome the first order ambiguity (alphabetic ambiguity) in the previous application, the scenario of referring to the index on the client side and secondly referring to the index on the server side is interpreted as simple code or full code. It can also be applied to Conversely, it is possible to refer to the server-side index primarily and to the client-side index secondly. Furthermore, the input value is first interpreted as a simple code, but firstly the index on the client side is referred, and the server side index is secondly referred to, and if the simple code for the input value is not searched, it is interpreted as a full code again. However, it is possible to analyze primarily on the client side, and if there is no such analysis function on the client side, it is possible to interpret it on the server side secondarily. As another example, the input value is primarily interpreted as a simple code, but it is also possible to refer both the client-side index and the server-side index to provide it to the user and allow the user to select a target word. Similar modifications are possible in applying the analysis method (simple code, full code) and the analysis location (client side, server side) as described above. That is, in summary, various combinations are possible in the application of the analysis method (simple code, full code) and the analysis location (client side, server side). That is, for the input value, not only the order of (A)-(B)-(C)-(D) or (A)-(C)-(B)-(D) in FIG. ), (B), (C), (D) means that it can be applied in the order of various combinations.

The advantages of applying the shortened 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 enter all words even if there is no dictionary other than the predefined words, and a simple code for the use of the shortened input method for common phrases is conveniently (partially related /All associations) can be specified, and the number of input strokes can be significantly reduced by specifying a partial association simple code. In addition, it has the advantage of giving word-based initial codes not only for words but also for phrases. However, foreign methods use the method of using the index of word units to input all words, so to minimize the case where the same code is assigned to different words, it was necessary to use the all-related simple code.

In addition, the system must have a "index" that holds a specific phrase and the code value for that phrase, which requires much less storage than foreign methods that have "index" for every word. do. And this "index" must have a "index" for the correct word or a "index" for the wrong word for words that can cause ambiguity in order to eliminate this ambiguity. Can be used jointly.

Since it is consonants that 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, the consonant "CPT" which has a phonetic value from "captain" is extracted and used as an abbreviation, "PVT" is used as an abbreviation in "private", and "SG T" is used in "sergent". "" is used as an abbreviation, "SSG" is used as an abbreviation in "staff sergent", SFC is used as an abbreviation in "sergent first class", and so on. Of course, the examples "captain" and "private" each consist of two syllables, but the consonant extracted as an abbreviation here can be viewed as a consonant representing each syllable. Therefore, in the case of "captain", "278" related to "CPT" can be designated as a simple code.

In addition to reducing the input effort, being able to apply the shortened input method by arbitrarily designating a partial-linked simple code for a common phrase based on syllables has great significance. Phonetically, syllables are defined as "psychological entities." Also, it is consonants that have a phonetic value in a syllable. It is almost impossible to deduce the captain if only the vowel "AAI" is extracted from the example captain. However, by extracting the consonant "CPTN" or "CPT" you can easily deduce the captain. It is said that even if vowels are removed for each word from a sentence in English and only consonants are listed, in general, the original sentence can be inferred. In other words, using a partially-associated simple code in association with each consonant, which is a subject of a syllable, means that the user can naturally adapt to the shortened input method, and that it can provide convenience to the user.

In particular, it is common to use abbreviations in the English-speaking world, and since a certain number of abbreviations are designated in the case of a listed company name, a simple code can be used based on this abbreviation.

Allowing the user to conveniently designate a simple code (partial association, all association) for a specific phrase has the advantage of making it easy to memorize the code value for a common phrase. Furthermore, if a user needs only a small fraction of the common phrases (for example, using only 10 or fewer common phrases), the code related to the alphabet of the common phrases is not necessarily assigned, but only for each phrase. 1, 2, 3,. . . A simple code can also be assigned like this.

6.8 Grouping of simple code/correspondence phrases and designation of search scope

If a simple code is designated for a large number of phrases, there is a possibility that a lot of redundancy may occur.The phrases corresponding to the simple code are grouped, and the simple code is searched only for a specific phrase group. ) Can be reduced. A phrase does not have to belong to only one group, but may belong to multiple groups.

For example, simple-named phrases are listed company name, city name, commercial phrase,… You can group them into groups such as, etc., and then group the common phrase groups into subgroups such as social, political, ... In this example, two-stage tree-type grouping is presented, but a tree-type grouping is possible in three, four or more stages. See Figure 5-6. If the user (or the system) limits the search scope of the simple code to the listed company name group, when entering a specific simple code, the system searches for a named phrase corresponding to the simple code entered only in the category of the listed company name group. It can reduce ambiguity. Similarly, if the search range is a common phrase, the search range can be made to include all subgroups below the common phrase group. If a social field group among the common phrase groups is designated as the search range, only the lower group (in the tree-shaped group structure) including the social field will be the search range.

The tree-shaped group in Fig. 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 the hierarchical structure of administrative districts is stored as a subgroup of the city name, after the user selects a specific city, the search range for the next input value is naturally 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 after the user selects “Yangcheon-gu”, the next selection range is “Seoul” in Yangcheon-gu. Dong”.

6.9 Use of relay server

The interpretation of the simple code can be done on the client side or on the server side. It is dedicated to decryption of such simple code (including full code in some cases) and provides the phrase corresponding to the simple code to the client side or other server side. You can have a relay server to provide. See FIG. 6-1. In addition, in Fig. 6-1, if the client side firstly decodes the simple code and fails to interpret the phrase corresponding to the input simple code, the second interprets and interprets the phrase corresponding to the simple code input from the relay server. In case of failure, it is possible to interpret the phrase corresponding to the simple code input from each server again thirdly. The tertiary simple code decoding server (referred to as “tertiary server” for convenience) becomes a server that is equipped with an application that uses the input simple code or a phrase corresponding to the simple code.

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

Each time a code value of a simple code is input, the index in which the phrase corresponding to the simple code is stored is searched and feedback can be given to the client side or each server side, or the feedback can be given by word.

6.10 Classification of word units

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

6.11 Download of simple code/correspondence phrase

Furthermore, the simple code on the server side and the phrase corresponding to the simple code can be downloaded to the client side without the user directly inputting and saving the phrase.

The downloaded unit can be downloaded in units of phrases one by one, or as a group unit of phrases (tree-structured group) as shown above. If you select the upper group, you can download the lower group. It is possible to download while maintaining the tree structure of the phrase group on the server side, or download the phrases belonging to the group and subgroups as a group designated by the user on the client side. If there is a relay server whose main function is to decode the simple code, the relay server can handle this function.

7. Input of symbols

As suggested in the previous application, it was explained that native language alphabets can be placed in "order close to the standard grid", and then numbers and English alphabets can be placed. When applying the standard repetition selection method, it is also in the order close to the standard grid. Explained that the national language alphabet and number can be selected. Likewise, in applying the subsequent control processing method, not only the native language alphabet belonging to a specific button, but also numbers and English alphabets can be entered through the subsequent control processing method.

In the present invention, we go one step further and present a method for efficiently inputting various symbols without displaying on the keypad (that is, by a hidden control processing method) that allows input by displaying on the keypad in the previous application. do.

In other words, among the grids in which controls were placed in the previous application, "symbol control" is placed on an appropriate grid, and symbols are input by combining the symbol control and a button that can mean a symbol (a button other than the control button). Here, as an example of a button that can mean a symbol, a period becomes a [5] button because it can be easily reminiscent of "ㅁ" in a period.

For example, in the Korean embodiment (Fig. 4-2) of the invention contents 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, the relationship between the representative alphabet and the subsequent alphabet is established, such as a (representative alphabet), ㅋ (2nd), symbol (3rd), .... In the case of control line input, when “period” is input, ㅁ = {symbol} +ㅁ = [*]+[*]+[5]. When input after control, ㅁ = ㅁ+{symbol} = [5]+[*]+[*]. If the symbol control is placed in a grid position that can be selected by pressing the [*] button 3 times, you can add the input of the [*] button one by one in the example.

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

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

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

[3] Button: Meaning of $ ("ㄷ" is arranged, but the first letter of "Dollar" is the same)

[4] button:. . .

[5] button:. Meaning ("ㅁ" is arranged, but the first letter of "period" is the same)

[6] Button: Meaning of * ("ㅂ" is arranged, but the first letter of "asterisk" is the same)

[7] Button: The meaning of, ("ㅅ" is arranged, but the first letter of "comma" is the same)

[8] Button: The meaning of "("ㅇ" is arranged, but the first letter of "quotation mark" is the same)

[9] Button: Meaning of ~ (the vowel "ㅡ" is arranged, but the shape is similar to ~)

[0] button: Meaning of @ (number 0 is arranged, similar to @)

As above, you can enter a symbol by combining a button that can remind you of various symbols and a symbol control. Assigning the meaning of the symbol to each button is the relationship between the local language name/shape of the symbol and the arranged alphabet, or the relationship between the English name/shape and the arranged English alphabet, as in the example, and the arranged number name/shape. The meaning of the sign can be given in consideration of the relationship with and. Since this may vary according to individual preferences, it is not necessarily the same as the above, and individuals can be made to (re)set the meaning of the symbol for each button.

Through this, as in the example, frequently used symbols can be treated as if they were a subsequent alphabet belonging to a number button that is easy to associate with. In the above example, the question mark is associated with the [1] button in which "ㄱ" is placed in consideration of the similarity of shape because the period, which is used more frequently than the question mark, starts with "ㅁ".

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

[1] button:? The meaning of (the alphabet "q" is arranged, but the first letter of "Question mark" is the same)

[2] Button: The meaning of, ("c" is arranged, but the first letter of "Comma" is the same)

[3] button:. The meaning of ("d" is arranged, but the first letter of "Dot" is the same)

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

[5] button:. . .

[6] button:. . .

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

[8] Button:: Meaning (the number "8" is arranged: similar in shape to)

[9] button:! The meaning of ("x" is arranged, which is related to the pronunciation of "eXclamation mark")

[0] button: Meaning of @ (number 0 is arranged, similar to @)

Giving the meaning of the sign based on English can be usefully used even in non-English languages using a keypad marked by mixing English. In addition, setting the colon with the similarity of the shape of the number 8 also has the advantage that it can be used universally regardless of language. Likewise, comma can also be regarded as a successor alphabet belonging to the [9] button by putting a similarity in shape with the number 9, but this was not the case in the above example.

Symbol control can be set to the appropriate button. In the case of English, if a control for another purpose is not placed on the [*] button in Fig. 1-1, the symbol control is selected with one tarot [*] button (that is, a symbol control is placed at the position of the reference grid of the [*] button). You may. In addition, in the case of European languages in which modified alphabets with subscripts are present, symbol control can be placed at the position of the reference grid of the [0] button or [#] button. However, in the case of putting a symbol control on the [0] button, it is better not to give the meaning of the "@" symbol as in the example above.

If you put the symbol control on the [*] button and apply the input after the control, in the case of English, when entering a colon (:) in Fig. 1-1,: = [8]+{symbol} = [8]+[*] do.

As shown in the example above, when the meaning of the symbol associated with 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 English example, meanings such as slash, semi-colon, and period may be assigned to the button assigned with "s", but only the meaning of slash, one of them, was given. The meaning of dot is also given to the button assigned with "d", so in the case of exclamation mark inevitably, considering the similarity of shape, the button assigned with "i" has "!" The meaning of was given.

Therefore, by placing a number of symbol controls (for example, symbol control 1, symbol control 2,.. .), and allowing control to be selected, a greater number of symbols can be input through the control processing method. For example, assigning the meaning of dot to a button assigned with "d" (or giving the meaning of "period" to a button assigned with "ㅁ"), and comma with a similar shape as if it were the successor alphabet of dot You can handle it.

For example, “dot(.) = 3****” can be used as an example of a symbol input associated with a button to which a basic consonant with a lattice or hard consonant is assigned. Since it becomes “3*** = big”, you can enter the promised symbol number 4 on the [*] button. You can enter it in dot(.) like “comma(,) = 3*****” and then press the [*] button one more time. This means that Korean syllables do not start with the vowel “ㅡ”. I used it. The input of comma(,) can be understood from the point of view of the chain-type subsequent control processing method.

If it is decided not to input the aspirated sound by the control processing method (that is, assuming that there is no aspirate control), it is natural that "Symbol Control 1" is selected for the [*] button 2 (skip control processing). Similarly, colons and semi-colons of similar shape are regarded as successive characters assigned to the same button, and can be entered by the control processing method. A similar trick can be applied to other symbols.

In the case of using two symbol controls such as "Symbol Control 1" and "Symbol Control 2", you must give the meaning of the symbol to each button and remember it, and there is a limit to the number of symbols that can be entered. do. Therefore, it is possible to input more symbols by grouping symbols in the same way as grouping dots and comma, colon and semi-colon, and placing multiple symbol controls.

It is desirable that the method of grouping the symbols can also be done at the user's convenience. In the present invention, an example of symbol grouping that can be used in general is shown. First, it is possible to set the transformation type of dot as a group based on the shape of various symbols. For example, dot(.), comma(,), colon(:), semi-colon(;), quotation mark("),..., Question mark(?), exclamation mark(!),.. It is possible to group like .. This is a grouping of symbols in the form of a dot, that is, in the form of "0 dimensional", where? And! Have both a 0 dimensional shape and a 1 dimensional shape, so a 0 dimensional shape ( dot format) In determining the group's sub-ranking, the frequency of use can be considered as mentioned in the previous application, 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 would be convenient to enter the symbol control afterwards, and in a terminal with a display window, you can see that the symbol changes as the control button is pressed.

Associating the grouped dot-shaped (0-dimensional) symbol to a specific button can also be set at the user's convenience. For example, if a group can be represented and the most frequently used symbol is dot, it can be regarded as the successor alphabet belonging to the [3] button containing the "d" of the dot. In the example of Fig. 7-1 in which the symbol control is added to Fig. 1-1, if the symbol control button is set to [*] and the input after control is applied, dot = [3] + [*], comma = [3] +[*]+[*], colon = [3]+[*]+[*]+[*], semi- colon = [3]+[*]+[*]+[*]+[*] ,. . . Becomes like Or, if it is regarded as a subsequent alphabet belonging to the [0] button because it is in a 0-dimensional shape, it will be combined with the [0] button instead of 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, you can group the symbols in the form of lines, that is, in the form of "one-dimensional", into groups. For example, slash(/), hat sign(^), question mark(?), exclamation mark(!), round bracket 1((), round bracket 2()), angle bracket 1(<), angle bracket 2(>), right angle bracket 1([), right angle bracket 2(]), wave symbol(~), minus(-), arrow 1(<-), arrow 2(->),. . . Can be grouped like this. Also, as described in the previous application, it is necessary to place a subordinate priority in consideration of the frequency of use, etc., and to associate this with the subsequent alphabet of a specific button, an appropriate button can be set as described above. For example, it is regarded as the successor alphabet belonging to the button [1] or the successor alphabet of the button [5] in which the letter "l" is placed.

Then, you can group the symbols of the combination of lines, ie "two-dimensional" shapes, into groups. For example, at(@), ampersent(&), asterisk(*), sharp(#), dollar($), won symbol (W+=), yen symbol (￥),. . . , heart1(♡), heart2(♥), clover 1(♧), white triangle 1(◁), white triangle 2(▷), white triangle 3(∇),. . . , Black triangle 1(◀),. . You can group them like ., ☏, ☎, ☜, ♨, etc. Also, the sub-ranking can be placed in consideration of the frequency of use, and you can choose an appropriate method to associate with a specific button. However, you can relate it to a button other than the button that has associated the symbol of the 0-dimensional shape and the 1-dimensional shape in the front.

As shown above, when grouping symbols into 3 groups of 0, 1, and 2 dimensional shapes (this is called "three large groups" for convenience), it has the advantage of only needing to remember 3 associated number buttons, but it is not used frequently. When entering a symbol, there is a disadvantage of having to press the control button several times. Therefore, an example of subdividing groups slightly (this is called "subgroup" for convenience) is as follows.

First, the two-dimensional symbol group is divided into a symbol group that forms a combination of lines (ex. *, #, %, ...) and a symbol group that forms a single closed curve (ex. ◁, ◀, ...). I can. In addition, in a group, symbols that form a picture such as ☏, ☎, ☜, ☞, ♨, ... can be placed in separate groups. Again, you just need to leave it as the successor alphabet belonging to the appropriate button. If these groups are placed separately, these symbols may or may not be excluded from the preceding symbol group, and this is the same for other cases.

Next, one-dimensional or two-dimensional symbols used in mathematical expressions, namely, +, -, *, /, root(√), sigma(∑), integral(∫),. . . The lights can be put into separate groups. You can also leave it as a follow-up alphabet belonging to the appropriate button.

Also, symbols that can indicate direction, namely →, ←, ↑, ↓, ↗, ↙, ↖, ↘, ◁, ▷, ◀,. . . Can be divided into groups. Again, you can consider the subsequent alphabet in relation to the appropriate button.

And various parentheses that can form another group relatively reasonably, namely (, ), [, ], {, }, <, >,. . . You can also put them into another group. Also, when grouping in parentheses, the left parenthesis and the right parenthesis may be grouped together.

In the case of not having only the three groups, but having a sub-group so that symbols can be entered, it is said that the alphabet belonging to the sub-group may or may not be left in the three groups. It will have to be placed in the second place.

An example of applying the above symbol grouping to FIG. 1-1 to regard each symbol group as a subsequent alphabet of a specific button 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 two-dimensional symbol group is assigned to the [2] button. The symbol group in the form of a single closed curve among the two-dimensional symbol groups is regarded as the subsequent alphabet belonging to the [8] button, and the symbol group in the picture form among the symbol groups in the two-dimensional form is selected as the [7] button. It is regarded as the subsequent alphabet belonging to, the mathematical symbol group is regarded as the subsequent alphabet belonging to the [6] button, the direction sign group is regarded as the subsequent alphabet belonging to the [3] button, and the parenthesis symbol group belongs to any button among the remaining number buttons. It can be regarded as a subsequent alphabet. As described above, this is only an example in associating a preference group with each button, and it can be set at the user's convenience.

In summary, a symbol can be regarded as a subsequent alphabet belonging to a specific button, and can be grouped into 3 groups (0, 1, 2), or slightly more subdivided into 10 or fewer groups. It is one of the key points of the present invention to show that most of the symbols can be input by grouping them. In addition, when each group of symbols is regarded as the successor alphabet belonging to a specific button, it is treated as a successor alphabet belonging to the button associated with the 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 type subsequent control processing method" while maintaining the alphabetical arrangement.

In this application, the [*] button or an arbitrary button among the upper and lower left buttons was mainly used as a control button for symbols, but the [#] button can be used as a subsequent control button for numbers and English alphabets. For example, if the [#] button is already used as a subsequent control button, additional controls for numbers and English characters can be placed on the available grid on the [#] button. In this case, too, in the selection of controls, as mentioned above, controls that cannot be combined with the representative alphabet can be skipped so that the next available control is selected.

8. How to use the move button

8.1 Use of the move button as a control button

In the earlier application, it was said that the control button 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. And in the earlier application, especially in languages with a large number of alphabets and a large number of modified alphabets, you may have experienced the 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 button, which is not used relatively frequently in the character input mode, can be used as the control button mentioned in the previous application and the present invention, and such an example is shown. That is, in the case of using a separate button outside the 4*3 keypad as a control button in the character input mode, the up/down/left movement button is used as the control button.

8-1 shows a button of a folder type terminal that is currently typically used. The [i] button indicated by a broken line is a button for Internet access, and this button may or may not exist depending on the terminal. Here, the right move button is used for blank input, and in Korean, it is also used as a syllable (character) confirmation button to remove the primary ambiguity. 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 character input mode, the up/down/left movement buttons are not frequently used, and in particular, the up/down movement buttons are not used frequently. For convenience, the up/down/left movement buttons are combined to be called "up/down/left movement button" or "up/down/left button", and the up/down movement buttons are called "up/down movement buttons" or "up/down buttons". When referring to only the movement button in either direction, use the same trick.

8.2 Placement under the Move Button

First of all, these upper and lower left buttons are usually placed above the number buttons. However, in order to use the primary functions of these buttons as buttons for entering various alphabets in the character input mode, it is useful to place them at the bottom of the 4*3 keypad along with the [*] and [#] buttons that are mainly used as control buttons. Can be seen. 8-2 and 8-3 illustrate 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 moving button is disposed under the 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/down and left buttons. This means that when applying the partial selection method, each button can be divided into 15 grids of 3x5 and used. Likewise, it is not always necessary to arrange the upper and lower left buttons so that a 5*3 keypad can be configured as shown in Fig. 8-3.

8.3 Move button left or right side

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

This is a trend in that the size of the liquid crystal in the terminal is getting larger, and there is an advantage that the size of the liquid crystal of the terminal can be made larger. In addition, it has good characteristics when applying the side battery mounting method in a mobile terminal proposed in the applicant's Korean patent applications 10-2000-0002081, 10-2000-0005671, 10-2000-0067852, and 10-2001-0002137 in parallel.

8.4 Various use cases 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 following cases.

8.4.1 Use case as symbol control button

In the Korean example, there was a case where the aspirated sound control and the hard sound control were disposed on the [*] button and the [#] button, respectively. In addition, there were cases where the aspirated control and the aspirated control were placed on the [*] button, the basic vowel control and the expanded vowel control were only placed on the [#] button, and the extended vowel control was placed on the [#] button. In this case, if the symbol control is placed on the [*] button or the [#] button, the aspirated sound, a horn sound, etc. comes first, and then the symbol is selected according to the input after the control button. The same is true for other languages.

However, if the symbol control is separated and placed on any of the up, down and left buttons, the symbol can be entered immediately after input by combining the button associated with the symbol group and the symbol control button on which the symbol control is arranged. 8-5 is an example in which the primary function of the down movement button is used as a control button for selecting a preference control. In the example of applying the input after control to the 0-dimensional symbol group, dot = [3]+[v], comma = [3]+[v]+[v], colon = [3]+[v] +[v]+[v], semi-colon = [3]+[v]+[v]+[v]+[v],. . . It becomes like this.

8.4.2 Example of use as a vowel element button in Korean

In particular, in the case of using vowel elements (ㅡ, ㅣ, .) in the Korean example in the previous application, there was inconvenience in inputting "ㅎ" by placing the vowel elements "." and "ㅎ" together. By arranging it on any of the upper and lower left buttons, this inconvenience can be overcome. 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 in the up, down, and left buttons. Alternatively, three Korean vowel elements can be placed on the top, bottom, and left buttons.

Similar to the symbolic control on the button with the aspirated control, the Korean vowel element "." at the reference grid position of any button among the upper and lower left buttons. It is also possible to place symbol controls in an order close to the reference grid. 8-6 is such an example. In this case, the vowel element "." is not used alone, so even if the vowel element and symbol control arranged in the repeated selection method are selected, the vowel element and the symbol control can be selected without ambiguity. In Fig. 8-6, when the [v] button is pressed once, the vowel element "." is selected, when pressed twice, symbol control 1 is selected, and when pressed 3 times, symbol control 2 is selected.

8.4.3 Examples of subscript control buttons in Japanese

In the case of Japanese as well, when the arrangement of the 50-tone chart 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. ), the control for inputting long/voiced/half tone can be placed on any of the up/down/left buttons. See Figures 8-7.

8.4.4 Use case as subscript control button for vowel input in Arabic

In the case of Arabic, controls for processing vowels in the form of subscripts can be distributed and arranged on arbitrary button(s) among the upper and lower 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 subsequent control button. Any button among the upper, lower, and left buttons can be additionally used as a control button. Or it can be used as a control button on the guitar.

8.5 Use cases for short/full switching control buttons

When the parallel input method is applied, there is a third order ambiguity that occurs between the simple code and the full code. To eliminate this, a method of putting a "short/full" conversion control in units of words was proposed. For example, if the full input method is the default mode and the parallel input method is applied, in order to input words by the shortened input method, first select the "shortened/full" switch control and enter a blank (right move button), It was to enter a simple code. Of course, the order of the blank and "short/full" toggle controls can be reversed. Here, the word unit "shortened/full" conversion control can be placed on any button among the up, down, and left buttons. Alternatively, a control that combines the “shortcut/full” switch control and the blank (right move button) can be placed in the standard grid position of any of the up/down/left buttons. See Fig. 8-8.

If it is assumed that the English alphabet of Fig. 1-1 is arranged on the number buttons of Fig. 8-8, and the basic alphabet input mode is full input mode, enter the simple code "4357" associated with the entire help in the state of the full input mode, and the word help If you want to input, you can enter "~ full code input +[^]+[4]+[3]+[5]+[7]+ [>]+ full code input ~". In other words, since the movement function of the upper movement button [^] is limited and the “short/full” conversion function in word units and the blank function are combined, the moment the [^] button is pressed, the system appears next "[4]+... "Recognizing that this is a simple code rather than a full code, it is possible to recommend the words closest to the input [4] to the user by referring to the index. The word ends as soon as the blank button ([>] button) is pressed after the input of [4]+[3]+[5]+[7] is finished. Waits for full code input again. If the [^] button is pressed again after input of 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.

In the parallel input method, if only one right move button (blank button) is used, there may be a third order ambiguity that occurs between the full code and the simple code as mentioned in the previous application. Each time, it was necessary to check whether a simple code exists or a promised full code is achieved. However, by putting a button that combines the word unit "shortened/full" mode and spaces, the system can recognize in advance whether the input value is a full code or a simple code, reducing calculations and searching, improving system performance. It will be possible.

8.6 Examples of use of the calculator mode as an increase/decrement button

Regardless of their position, the four movement buttons can be usefully used as the most frequently used increase/decrease (+, -, x, /) buttons in the calculator mode. It is also possible to mark the button with an increase/decrease symbol, but it may not be indicated on the button because the calculator will not be used often compared to the alphabet input. This is because each button will be used as a move button or a control button in the alphabet input mode.

In addition, it is possible to select an operator that can be used in a calculator by the (hidden type) iterative selection method by placing it on the add/decrease/multiple button. Operators (binary operators) that are frequently used in the calculator mode are those that do not appear repeatedly. For example, there cannot be a calculation of 2++1. In addition, 24 can be solved to 2xx4, and the "square" operator can be selected by repeatedly pressing the win (x) button. That is, it is the same as repetitive selection assuming that there is a square (xx) operator as a subsequent operator on the win (x) button. Likewise, (O3) can be released to 3//2, and the "square root" operator can be selected by repeatedly pressing the (/) button. Since the other binomial operators do not appear in duplicate, it is possible to select the subsequent operators by the iterative selection method by placing them as the successor operators belonging to the appropriate increase/decrease/multiple buttons.

It is also possible to use the [*] button for the multiplication (x) operator while adding and subtracting (+, -, /) operators are placed on three of the up/down/left/right movement buttons.

9. Help function activation

Here, in each input mode, functions that are not displayed on the buttons (up/down/left/right) can be displayed on the screen (liquid crystal) to add convenience to use. In this case, there is a drawback of consuming part of the liquid crystal. Of course, users who use the function of each operator button do not need to display it while consuming space of the liquid crystal, but it can be very helpful to users who do not. have. 8-1 may be referred to, and FIG. 9-1 is an example of a case in which the up, down, left and right buttons are arranged on the right side of a 4*3 keypad as shown in Fig. 8-4, and are arranged in a similar form.

In this way, the function of the button (that is, the operator assigned to the button or the symbol group associated with each button) is displayed according to the user's convenience and intention, which is called "activating the help function" for convenience. Activation of the help function can be made for each mode (eg alphabet input mode, calculator mode), or for the required function in each mode (eg, use of numeric buttons or control buttons associated with a symbol group in alphabet input mode). You can also.

Likewise, the function of the control button suggested in the previous application or the number buttons associated with the symbol group can be displayed on the liquid crystal when the user needs it, thereby promoting the user's convenience. See Fig. 9-2. 9-2 is an example in which number buttons associated with each preference group are converted into icons and displayed on a liquid crystal based on the classification of preference groups illustrated above. Among the symbols of the symbol group associated with each number button, only the first symbol selected for convenience is added to the number button icon.

10. How to use the delete button

In using the delete button, it can be used as the "cancel final input" introduced in the previous application. For example, in Fig. 4-2, trying to enter "a", inputting [1]+[*] to enter "ㅋ", but pressing the delete button to cancel the final input ([*]) to return to "a" It can be done. This can be usefully used in the case of repeatedly pressing the control button to input a subsequent alphabet. When the cancel button is pressed consecutively, the already entered alphabet may be deleted in a normal manner. For example, if you enter "Kana ㅋ" and press the cancel button once, it becomes "Kana", if you press it again, it becomes "Gana", and if you press it again, it becomes "Go". In the case of Roman characters, "ab a.." is entered (the last "a.." is a transformed alphabet consisting of "..+a"). Pressing the delete button once becomes "aba", and pressing it again becomes "" It becomes "ab", and if you press it again, it becomes "a". That is, the already formed alphabet is deleted in alphabetical units.

11. On the keyboard With numeric keypad Unification of keypad in telephone terminal

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 phone board, such as a numeric keypad of a mobile terminal or a standard keyboard, or a keypad or door lock configured in software on a screen. In addition, although the numeric keypad provided in the standard keyboard differs in the arrangement of the keypad and the numeric buttons proposed in the previous application and the present invention, it is obvious that the arrangement on the keypad buttons in the earlier application and the present invention can be applied to the keypad provided on the keyboard. . For example, in the previous application and in the present invention, the alphabet arranged on the [1] button is placed on the [1] button of the numeric keypad provided on the keyboard, and is arranged in the same manner as follows to input the alphabet, the use of simple codes, and the use of various codes. It can be used for memorization.

However, in order to reduce confusion and add convenience to use, in constructing the numeric keypad of the keyboard, the numeric layout of the telephone keypad can be utilized. That is, in the numeric arrangement of the numeric keypad of the keyboard, as in the keypad of a phone, buttons [1], [2], and [3] are placed on the first row of buttons, and [4], [5] are placed on the second row of buttons. Put the buttons [6] and [7], [8], and [9] buttons on the 3rd row. In addition, you can have [*] buttons and [#] buttons as on the keypad of a phone.

12. Language restriction input method

The language-restricted input method refers to reducing ambiguity in character input by using a combination rule of consonants and vowels in generating words in a specific language, and will be described in detail below.

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

12.1 Chinese Restricted Repeat Selection Method on the Consonant Separation Keypad for Languages Using Roman Alphabet

12.1.1 Composition of Chinese Virgin Mary and Mica

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

(^e) is said to be rarely used). It is said that the holy mother corresponds to the consonant and the mica corresponds to the vowel. In mainland China, the Chinese language pinyin is used as a method of marking Chinese sounds, and in Taiwan, Chinese sounds are said to be input using the main yin code. Chinese Pinyin is a Chinese sound using Latin alphabet, or Roman alphabet. The main note code and the corresponding Chinese pinyin (Roman alphabet) are shown in parentheses as follows.

The following is an explanation of the combined mica in Chinese. Combined mica is said to have three vowels i, u, ..u in front, followed by other mica. The following table is a list of combined mica that shows the cases where binding is possible.

In the table above, it can be seen that the combination of ia is possible, but the combination of io is not possible.

12.1.2 Chinese Chinese Pinyin input using Roman alphabet

In the end, as shown in the table above, in the case of using Roman alphabets, 21 Virgins in Chinese can be entered as a combination of 18 Roman alphabets, and 16 mica can be entered as a combination of 7 monomica or Roman alphabet vowels and Roman alphabets. Any combination of alphabetic consonants can be entered.

In addition, ^e and ..u among monomica are regarded as transformed letters of e and u, respectively, and can be entered by the control processing method. 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 Roman alphabets, all Chinese mica can be entered using five basic vowels of Roman alphabets. This is the input of a modified alphabet that does not exist in the English alphabet (ie, the Roman alphabet) by the control processing method, which is already seen in the input of French and German. The following is an example of establishing a sub-relationship between the basic alphabet (basic vowel) and the subsequent alphabet (subsequent vowel) when Chinese mica is input by the control processing method.

In the above example, the alphabet with the tonal sign of 1 to 4 tones became the successor alphabet, and ^e is said to be rarely used, so the subordinate ranking is placed at the bottom. Of course, the order of attachment may vary depending on the frequency of use. For example, it is possible to set ..u as the 2nd successor alphabet instead of the 6th, and the subordinate rankings of the remaining successor alphabets one by one as a later order.

Using the [*] button, the control button as an input example, and when after the control input applied, ^- e = e + [*], ^/ e = e + [*] + [*], ^v e = e + [*] +[*]+[*], `e = e + [*]+[*]+[*]+[*], ^e = e + [*]+[*]+[*]+[*] It becomes like +[*]. In Fig. 1-1, if "e" displayed on the keypad is applied to the partial selection method, e = [3]+[2] becomes -e = [3]+[2] + [*]. In Fig. 1-1, when the alphabet displayed on the keypad is selected by the partial-to-all selection method, the full code of 人 (r ^/ en: 2nd star) becomes "7832**65". Here, it is obvious that any other input method (eg, simple repetition selection method) can be used to input "e" displayed on the keypad.

In the end, only one control button is used, so the input method can be simplified. This can be applied equally to the case where the Roman alphabet is not used and the main note code is used (for example, the same input method is applied in the keypad displaying the main note code corresponding to the English alphabet in Fig. 1-1).

12.1.3 How to select repeated Chinese restrictions on the consonant vowel separation keypad

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

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

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

The example above is an example of grouping based on the similarity of pronunciation.When using simple codes, when 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 considered to have an initial code. The above example is just one example, and many variations are possible. They can be grouped according to the similarity of pronunciation, and can be grouped according to various criteria such as English alphabet dictionary order, English alphabet corresponding main phonetic code dictionary order. 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 pronunciation are less likely to appear consecutively, so that ambiguity is less likely to occur. It is to lose. In addition, in the use of simple codes (especially syllable-based initial codes), even if there are many phrases that correspond to the same simple code, the phrases are phrases with similar pronunciation (phonic value), thus minimizing confusion for users and reducing the use of simple codes. It can be natural.

Another thing is that zh, ch, and sh exist as denominations in Chinese, 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 "Symbol + Mica", but it does not matter if they are grouped into the same group in this embodiment. However, when inputting w, y, v, etc. not shown in Fig. 10-1, s, All you have to do is assign h, w, etc. together, and do not input with the assigned button 3 strokes)

As shown in Fig. 10-1, the nine groups illustrated above can be arbitrarily assigned to nine buttons [1] to [9], and a repetitive selection method can be applied to the input of each alphabet. Due to the nature of Chinese, Roman alphabet consonants do not appear consecutively, except for zh, ch, and sh when entering the Holy Mother. Therefore, even if an alphabet is entered by the repetitive 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 to be selected as one stroke can be determined so that the alphabet with a large use frequency can be selected as one stroke according to the frequency of use of the alphabet.

The Roman alphabet "v", which is rarely used in Chinese, can be placed in any of the nine groups. For example, you can add "v" to a group with a similar "f" (or not explicitly assign it), and have the button type "v" with 3 strokes. W, and y used in "衣 = yi (1st)" and "5 = wu (3rd)" are also placed in the appropriate consonant group (or not explicitly assigned) and entered by the repeat selection method (eg You can enter w and y with 3 strokes of the button each alphabet belongs to). For example, if y is placed in the group to which / l and r / belong, the corresponding button ([8] button in Fig. 10-1) inputs “l” for 1 stroke, and “r” for 2 strokes, Enter “y” for 3 strokes, and if w is / m, n / in this extreme group, press the corresponding button ([7] button in Fig. 10-1) with 1 stroke and “n” for 2 strokes Enter "" and "w" for 3 strokes.

By applying the repetition selection method, when entering Chinese Pinyin, Roman alphabet consonants and vowels alternately appear to significantly reduce ambiguity, which is called “Chinese limited repetition selection method” for convenience. When this property is generally applied to all languages other than Chinese, it is called “Large Restricted Repeat Selection Method (LRRSM)” for convenience, and when applied to Chinese, “Chinese Restricted Repeat Selection Method” (Chiese Restricted RSM)”. In Korean or Hindi, the language-limited repetition selection method assigns a pair of basic consonants and basic vowels to each button, and when applying the repetition selection method, it is possible to input with little ambiguity using the property of alternating consonants and vowels. It is in the same context as did. In addition, in the method using the vowel elements in Korean, it is similar that the vowel “-” can be selected by the repetitive selection method using a property that does not appear consecutively. It can be said.

In particular, as shown in Figs. 10-1 to 10-4, a button to which a consonant is assigned (called a “consonant button” for convenience) and a button to which a vowel is assigned (referred to as a “vowel button” for convenience) are separated (that is, the consonant and Vowels are not assigned to the same button), and when the repetitive selection method is applied, there is a good feature that can significantly reduce ambiguity by using the characteristics of each language in which consonants and vowels are combined. In this way, similar to Figs. 10-1 to 10-4, the consonant button and the vowel button are separated, and a keypad composed of a predetermined number (eg, 1 to 3) of consonants or vowels is assigned to each button. It will be called "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 entered without ambiguity even when inputting Chinese Pinyin Chinese by the repeated selection method. When the same button among the consonant buttons (buttons [1] to [9] in Fig. 10-1) is pressed continuously for the input of the constellation, the system can easily know that the second consonant displayed on the keypad is input. This is because there is no case in which the same Roman alphabet appears consecutively to input the Holy Mother in Chinese. Here, the button pressed twice is the button assigned w, y, v, etc., and when the same button is pressed once more (that is, when pressed 3 times), as previously described, input w, y, v, etc. The system can easily see what is for. [7] If you enter "w = 777" with three buttons, it can be interpreted as "mmm" or "mn" or "nm", because there is no case in which our Lady of Chinese is composed like this.

As shown in Fig. 10-1, the 6 vowels of a, e, i, o, u, ..u are divided into 3 groups of 2 each and 3 buttons on a 4*3 keypad (ex. [*], [0] ], [#] button), and each vowel can be entered without ambiguity by the repeated selection method. This is possible because there are no two consecutive Roman alphabet vowels in Chinese. For example, when writing a Chinese character in Chinese Pinyin, it is not like "…aa...".

However, if we look at the bloc mica ai, ei, ou and ia, ie, uo of the combined mica, we 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 (e.g. [*] button), whether three strokes of the button (ie,'***') are input is'ai' This is because ambiguity may arise where it is unknown whether ia' is entered. 10-1 shows an example of grouping in consideration of these contents. It goes without saying that 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 repeat selection method. For example, i = [0], o = [0]+[0], iao = [0]+[*]+[0]+[0].

As long as a and i, e and i and o and u are not grouped into the same group, “a, e, o” is a group (refer to Figs. 10-2 and 10-4), and the remaining vowels “I, u, u” can be used as a group. Again, various variations will be possible. Each of these two vowel groups is assigned to an arbitrary button (eg, [*], [#] buttons respectively) within a 3*4 keypad, and the consonants “w, y, v” are assigned as separate groups and the remaining buttons ( Yes, it can be assigned to the [0] button). When 3 alphabets are grouped in one group (eg "a, e, o"), the corresponding button that represents 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 the corresponding button 3 strokes. In the example, when “ao” is input, the corresponding button becomes 4 strokes, but since “oa” does not exist in Chinese Pinyin, it can be recognized without any ambiguity, see Figure 10-6. Since it is not used for input of, it may not be displayed. Grouping “w, y”, etc. into a group and assigning them to the same button has the effect of assigning half consonants (ie, half vowels) to the same button.

In Figs. 10-2, 10-4, and 10-6, "a, e, o" is grouped into the same group, but only a combination of "ao" is possible. If only “a, o” is assigned to one button, the corresponding button 3 strokes can be recognized as “ao” without ambiguity. However, if 3 alphabets are assigned and selected in the order of “a-o-e” according to the number of button presses, ambiguity may arise that it is not known 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), two vowels that can be combined are not selected as one stroke and two strokes, respectively, and each By selecting 1 stroke, 3 strokes (or 2 strokes, 3 strokes are possible, and the 5 strokes of the button can be recognized as "ao"), ambiguity can be removed by using language restrictions. In summary, in determining the order of selection according to the number of button presses in the three alphabet groups, the order of selection is so that the alphabets that can appear consecutively are not selected as one or two strokes of the corresponding button, respectively.

When entering the Holy Mother in Roman alphabet in Figs. 10-1 to 10-4, the same button can be pressed up to 2 to 3 times, and the system recognizes the number of repeated presses of the button and targets according to the number of repeated presses. The alphabet can be identified. When inputting mica in Roman alphabet, if the same button can be pressed three times in succession in Figs. 10-1 and 10-3, the [0] button is pressed to input “io” of the combined mica “iou”. This is only the case when it is pressed three times in succession. Regarding the user's input, the system temporarily recognizes as “0 = i” and confirms when a button other than the [0] button is pressed, and when the [0] button is pressed again, the system temporarily displays “00 = o”. And, likewise, if a button other than the [0] button is pressed once more, the system can confirm as “000 = io” when the [0] button is pressed once more. This is because “Chinese language restrictions” are used, where “oi ”does not appear. [*] button can be pressed up to two times, so the system temporarily recognizes “* = a” and “** = e”, because the same Roman alphabet vowels do not appear consecutively when Chinese Pinyin is entered, and vowels assigned to the same button do not appear consecutively.

The reason why the input system can be configured without ambiguity (or with significantly less ambiguity in cases other than Chinese) in the consonant vowel separation keypad is that the same consonant button (eg button [1] in Fig. 10-1) is pressed once or continuously. While being pressed, the system recognizes that one of the consonants in the same button is input, and when another consonant button (eg, the [9] button in Fig. 10-1) is pressed, the system is considered to input consecutive consonants. Because it becomes aware. Another reason is that about 2 letters are assigned instead of about 3 letters per button. As mentioned in the case of grouping consonants and vowels into pairs, the possibility of ambiguity is significantly reduced when 2 alphabets are allocated compared to when 3 alphabets are allocated per button, which can be easily seen. In addition, when two letters are assigned per button, the battering delay time and the battering delay time suggested by the applicant can be applied more effectively.

10-7 shows the procedure of a general repetition selection method in the consonant vowel separation keypad, except for the part (R). In Fig. 10-7, for convenience, the input value is assumed to be a consonant button or a vowel button. In other words, it is assumed that there is no special use or function (eg, a subsequent control button for inputting a subsequent 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 FIGS. 10-7. Language restrictions can be determined in process (R), and process (R) can be intervened in any part of the flowchart. That is, if the first input value is one of the consonant buttons, and only two consonants are assigned to a button pressed consecutively, and no alphabets assigned to the same button appear consecutively (eg, button [1] in Fig. 10-1). ), the moment the same button is pressed twice in (R1), the input value can be confirmed as one consonant (eg, “P” in Fig. 10-1). This is similar to removing ambiguity using language restrictions in Fig. 4-4 (when applying the repetitive selection method, the target alphabet is determined with little or no ambiguity). It can be seen that the procedure of Fig. 10-7 is much simpler than that of Fig. 4-4.

When the same or unequal consonant buttons are pressed consecutively, and 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 enters the first in the vowel processing process. The value becomes the last vowel button entered in the consonant processing process. The same applies when the vowel processing is changed to consonant processing.

In Fig. 10-7, the method of judging by the language restriction (R) is a list of concatenable 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 on a specific keypad), and the input value In the case where this ambiguity can be caused, it is generally possible to make the system recognize the case where the combination is possible as a target alphabet except for the case where the combination is impossible. When “ao = 0000” is entered, the system can recognize “ao” as the target alphabet for the input value “0000”, while the system has “ao” in the vowel combination list. -2, when there is no mistaken input from the user in the consonant vowel separation keypad of Fig. 10-4, only the [0] button can be pressed up to 4 times. Considering only special cases where ambiguity may occur, in this case, “ 0000 = ao”. The rest of the process can be performed according to the process of Fig. 10-7.

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

In writing Chinese syllables in pinyin, if mica such as "en", "eng", "an", "ang", and "er" are used, the end of the syllable ends with an English consonant (English alphabetic consonant). (Eg. ren: 人). In other words, the consonants of the English alphabet that can be at the end of a syllable in the middle of a word or phrase are "n", "g", "r", etc. In this way, consonants that can come to the end of a syllable in Pinyin are called "Consonants which Can be at the End of a Syllable of Pinyin" for convenience.

In the case of a syllable in which the pinyin syllable end possible consonants are used (ie, a syllable in which mica such as "en", "eng", "an", "ang", "er" is used), representatively, the following syllable is English If the consonant is the 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 arise, which is ambiguity if pinyin-syllable end-possible consonants (eg "n", "g", "r" ...) are selected by the corresponding button 2 strokes in each group they belong to. Can be removed (when only two letters are assigned to the group to which "n", "g", "r", etc. belongs, as in Fig. 10-6).

In Figure 10-6, "n", one of the pinyin-end possible consonants, is selected by the corresponding button ([7] button) 2 strokes, so in the case of "rennai (忍耐)", "88**7777*#" can be entered without ambiguity. It's like you 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” is “k-g” in Fig. 10-6, Pinyin can be input without ambiguity.

In order to remove the ambiguity by selecting the pinyin syllable end consonants as two strokes in the corresponding group, two alphabets must be grouped in the corresponding group. If three English alphabets "m, n, w" are grouped as shown in Figure 10-4 and are selected in the order of "m-n-w" according to the number of times the button is pressed, "n" is the corresponding button 2 Entering "renmin (人民)" will cause ambiguity with "rewin" even if it is selected as "renmin" (here "rewin" does not actually exist in Chinese Pinyin, so the system will input "renmin (人民)" )", but "rewin" is a possible pinyin combination).

Therefore, when it is possible to group three English consonants as shown in Fig. 10-4, the pinyin syllable end possible consonants ("n", "g", "r", etc.) are grouped by two English consonants. You can see that it needs to be grouped. And even when two consonants are grouped, it can be seen that ambiguity may also occur if “n” and “r”, and “g” and “r” are grouped into the same group among the pinyin syllable end consonants. . For example, if two English consonants "n" and "r" are grouped into the same group, entering "~nr~" will cause ambiguity with "~rn~". The same applies when "g" and "r" are grouped into the same group.

In Fig. 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 entered without ambiguity. For example, if "n" and "g" are grouped into the same group and assigned to the [5] button, pressing the [5] button 3 times to enter "vowel +ng" (ie "555" is entered If so), it can be recognized as "vowel +ng" rather than "vowel +gn". This is because in Pinyin, it is possible to use language restrictions in which "vowel +gn" cannot appear 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 set to "g-n", when the button is pressed twice, "g" is displayed. When pressed, "ng" can be displayed, so you can naturally realize WISWYG (What You See is What You Get, more precisely What You Press is What You See). 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 it as "a" and display it again, [*] When the button is pressed once more, "ao" is displayed naturally, thereby giving a more friendly feeling to the user.

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

When English consonants other than "n" and "g" (eg'm') are grouped together, the order of "m-n-g" or "m-g-n" to enter Pinyin without ambiguity If it is selected as (that is, consonants other than'n' and'g' are selected with one stroke of the corresponding button), it can also be recognized without ambiguity. For example, in the order of "m-g-n" according to the number of button presses, after the vowel button is pressed, pressing the button 5 times is recognized as "(vowel)+ng", and 6 times pressed. Pressed 7 times is recognized as "(vowel)+ngm", pressed 8 times as "(vowel)+ngn" can be recognized without ambiguity. However, it would be undesirable because the number of repeated presses when entering "ng" increases excessively.

In Figures 10-7, 10-8, and 10-9, "nX", "ngX", "rX" (capital letter "X" is an English consonant in the process of consonant treatment in the middle of the word, not the beginning of the word. In case consonants appear consecutively, such as (meaning indicated by ), the input value can be processed with possible consonant combinations in Pinyin. This is because English consonants such as "nX", "ngX", and "rX" do not appear consecutively at the beginning of a word. In the end, in the input of Pinyin, there are theoretically up to 4 English consonants that can appear in the middle of a word or phrase, such as "~ngch~", "~ngsh~", and "~ngzh~", and drawings 10-7, 10 You can use these language restrictions in the course of consonant processing in the middle of words in -8, 10-9.

An English consonant is moved at the end of the syllable, so that even if ambiguity may occur, a method for inputting without ambiguity was suggested. In the alphabet group assigned to each button, the order of selection according to the number of times the button is pressed can be arbitrarily determined, so this can be seen as a detailed explanation of the content presented in the previous application. The pinyin syllable end note is a consonant that can be used both at the beginning and end of a syllable, so it can be regarded as a consonant that is used relatively often, and it can be said that this ambiguity is not common, and even when ambiguity may occur. Since pinyin ("rewin" in the example) that does not exist can be excluded by referring to the Pinyin/Hanja index, in consideration of the convenience of input, etc. You will be able to set the order of choice.

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

12.1.4 Enter the original function of the function button used as a control button

In FIG. 10-1, when inputting a modified alphabet with a subscript on a Roman alphabet vowel, an arbitrary “separate button” outside the 3*4 keypad can be used as a control button. For example, if utilized in the Chinese input mode, the left (左) side button ([<]) to the control ^{button, - e = e + [<} ], / e = e + [<] + [<], v e = e + [<]+[<]+[<],`e = e + [<]+[<]+[<]+[<], ^e = e + [<]+[<]+[ It can be entered as <]+[<]+[<], and if the left move button is pressed 5 times in succession, the control combined with “e” can no longer be selected, so the move function can be activated ( “E” is the input state). Only if about removed utilizing a button control buttons for (for convenience "[X]" shown in) deformation alphabet <sup>input, - e = e + [X</sup> ], / e = e + [X] + [X], v e = e + [X]+[X]+[X], `e = e + [X]+[X]+[X]+[X], ^e = e + [X]+[X]+[X It can be entered as ]+[X]+[X], and if you press the delete button 5 times in succession, the previously entered “e” can be deleted. Buttons with these different functions can be used as control buttons, but after the control is selected according to the number of times the control button is pressed, if there is no more selected control, the original function (eg, move function) can be selected. have.

In the example above, after the left movement function is activated, the word starts, so even if the left movement button [<] is pressed once, the left movement function is input. In other words, if you press the [<] button 5 times after inputting “e”, the cursor will move one space to the left while only “e” is input, and if you press it again, it will move one space to the side again. This is applicable in all languages.

12.1.5 How to select repeated Chinese restrictions on the consonant vowel separation keypad (enter the transformed alphabet in the 3*4 keypad)

In this case, it is shown that in the 3*4 keypad, it is possible to input the modified alphabet (including the case where the tonal code is added) with a subscript on the Roman alphabet vowel.

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

This is a property in which the vowel u does not appear after a and e among the vowels "a, e, o" in Chinese, and the vowel i does not appear after the vowel o. The constraints described earlier, i.e. a and i, e and i, and o and u, are not placed in the same group, but by assigning two vowels to three buttons, and using the Chinese Roman alphabet vowel concatenation rule, Figure 10 As in -2, it can be seen that it is impossible to use a button assigned a vowel as a control button. In Fig. 10-2, i and u are placed on the [*] button or the [#] button, in which these buttons are used as control buttons, taking into account the points for facilitating recognition and the balance of arrangement. The average number of strokes for vowels in FIG. 10-2 is 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 into a "separate button" outside the 4*3 keypad. For example, some of the 3 alphabets can be separated and assigned with a random button among the up/down/left buttons.

In Figs. 10-1 to 10-4, consonant buttons ([1] to [9] buttons) and vowel buttons [*], [0], [ #] button) was separated, and the rules of appearance of consonants and vowels in the Roman alphabet were used when writing Chinese in Chinese Pinyin.

12.2 How to select repeated English restrictions on the consonant vowel separation keypad

In the case of English, etc., similarly to the case of Chinese, it is possible to input with little ambiguity by applying the repetitive selection method in the consonant vowel separation keypad (CVSK) similar to Figs. 10-1 to 10-4. This is because in all languages that use the Roman alphabet, the structure of words is a structure in which consonants and vowels are alternately combined.

In the case of English, the case where the consonant group is repeated as much as possible from the "word start" is called the case of "CCCVCCCC" as in "strengths" (C is a consonant, V is a vowel). At the beginning of the word, up to 3 consonants can come, but this is only said to start with "st~" or "sp~" (for example, spree, spleen, strength, etc.).

Similar to Fig. 10-1, on a keypad in which about 2 to 3 consonants are assigned (assuming that only "..u" is not assigned in Fig. 10-1 for convenience), the user enters the English word "student". When entering "622~" for this purpose, the system can treat "622" entered after "word start" as entering "st" instead of entering "sdd" (3 The case where dog consonants can appear in succession is a case where they start with "st~" or "sp~", and the system needs to remember these English word generation rules or alphabetic combination rules). When entering "u" in "stu~", the button assigned to the vowel is pressed, so you can see that the consonant group ("st" in the example) ends and the vowel ("u" in the example) comes. When "2" is input to enter "d" after "stu" is input, the system knows that consonants start again. Similarly, when the user enters "~**7722" to enter "~ent" in "student", when "**" is entered, "a" appears consecutively in English as described in the previous application. Because it does not, the system can easily know that "e" is entered instead of "aa", and "7722" can also be interpreted as "mmt", "ndd", "nt", "mmdd", etc. As mentioned in the above, by setting the "battery delay time" and the "battery delay time" differently, the ambiguity that occurs in the repeat selection method can be greatly reduced.

The current standard English keypad (Fig. 1-1), where consonants and vowels are mixed and assigned to each button, reflects the word generation rule (alphabetical combination rule) of a specific language in this way, thereby creating ambiguity that may occur when applying the repeat selection method. Can be reduced. However, when consonants and vowels are mixed and assigned to one button, it becomes very difficult to apply the language restriction 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 repetitive selection method, "stu~" becomes "777888~". Assume that the system recognizes "777" as "s". Also, it is impossible to know whether the following "888" is "ut (i.e. sut)", "tu (i.e. stu)", or "v (i.e. sv)" (of course, when the English limited input method is applied, "s "Since "ttt" cannot be followed by ", the system may consider the input "888" as not "ttt"). Likewise, when the user enters "333" to enter "~de~", it is not known whether it is "de" or "ed", but "888777" entered before "~de~" is "sut", " Since it can be interpreted as "stu" and "sv", 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 repetitive selection method is applied as the full input method is the rule of appearance of consonants and vowels in the language-restricted input method (i.e., word generation rules, alphabet combination rules). Is used because it is not clearly distinguished whether the input value is for entering consonants or vowels. Fig. 10-1 When the consonant and vowel are assigned separately as shown in Fig. 10-4, when the button to which the vowel is assigned is pressed when applying the repeat selection method, it is for entering the vowel, and the button to which the consonant is assigned is pressed. This is for inputting ground consonants, and because the system can recognize them, it can significantly reduce ambiguity.

In English, which uses the Roman alphabet, there are many cases where two or more vowels appear in succession (eg, ‘ai’ in captain). In addition, when the same vowels (basic vowels a, e, i, o, u) appear consecutively in real words, oo, ee such as food and teen are relatively frequent, and uu such as vacuum is rare. . The applicant has not yet seen a case where ... aa ... and ... ii ... appear consecutively among the words existing 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 case the ambiguity is removed. For example, if the vowel'a, o'is placed on the [*] button and the repeat selection method is applied, when the [*] button is pressed twice, the vowel o is not input. The system becomes conceivable. Similarly, if'i, u'is assigned to the [0] button and the repeat selection method is applied, when the [0] button is pressed 2 strokes, two vowels ii are not input, but the vowel u is input. The 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 the “battery delay time” and the “emission delay time” mentioned in the previous application differently. The remaining vowel'e' can be assigned to the remaining [#] button and entered with one stroke.

If you want to use one of the [*], [0], or [#] buttons as a special purpose button, you can place the vowel'e' on any button assigned to the vowel. For example, you can put'i, e, u'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 (ie ...ii...), i and e can be entered without ambiguity ( When you input 1 stroke, 2 strokes, respectively, and u with 3 strokes of the [0] button, ambiguity arises that you cannot know whether it is u, ie, or ei. The low frequency of u means that these cases are less likely to occur.

In the end, ambiguity can be greatly reduced by using the consonant vowel separation pad, and further, in allocating multiple vowels to one button, vowels in which the same vowel does not appear consecutively among the English words in the dictionary are converted into one stroke. When a vowel is input by a repeat selection method from a button in which a plurality of vowels are assigned to be selected, it is possible to input it almost without ambiguity.

This selection of vowels that do not appear in succession as 1 stroke and the selection of the least frequently used vowel as 3 strokes can be applied equally even when about 2 to 3 consonants are allocated per 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 How to select repeated Indonesian language restrictions on the consonant vowel separation keypad

In Indonesian, words are written using the Roman alphabet (English alphabet). It is said that the syllables in Indonesian are composed as follows. (C is a consonant, V is a vowel)

V: be-a tariff

VC: am-bil catch

CV: go-sok rub

CVC: pon-dol hut

CCV: tra-di-si tradition

CCVC: con-trak contract

CVCC: teks-tur fabric

CCCV: kon-struk-si construction

CCCVC: strip-tis naked dance

If there are more than 3 consonants, it is a foreign word from English, etc., as you can easily see. As can be seen from the above, you can guess that in Indonesian language, if it does not start with “st~” or “sp~”, more than three consonants do not appear repeatedly at the beginning of the word. Therefore, it is possible to apply the Indonesian limited repetitive selection method using such a word generation rule (alphabetic combination rule).

It is said that q and x are used in natural science symbols such as physics and mathematics. That is, it is thought that it is rarely used for character input. Therefore, q and x may not be explicitly placed in a specific group, and they may be entered in 3 strokes as well. Also, as in the case of Chinese, two or more Roman alphabets are combined to indicate one Indonesian sound, and there are four types: ny, sy, kh, 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. In particular, “skr~”, “spr~”, and “str~” can appear at the beginning of a word, so it can be used as a means to determine whether the input value is a full code or a simple code in the language restriction parallel input method described later. (As an applicant, I don't know if there are cases where “rps” appears at the beginning of a word, but if so, you can use it as well.)

Of the 21 consonants of the English alphabet, 19 consonants excluding q and x may be grouped into 9 groups, but it is sufficient to group by reflecting the characteristics of Indonesian. For example,

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

Can be grouped like this:

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 indicate Indonesian vowels. In addition, there are 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 make sure that a and i and a and u are not grouped in the same group. For example, grouping like ae / uo / i. Also, 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, but the frequency of occurrence is small) with one button to which the vowel belongs in each group.

12.4 Japanese Restriction Repeat Selection Method on the Consonant Separation Keypad

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

In Japanese, the Roman alphabet consonants appear twice in succession when a tactile sound or a yo sound (indicated in small letters) is used. In addition, in the case of consecutive Roman alphabet vowels, under the assumption that it is not common for a combination of あ, い, う, え, and お to appear consecutively, it is at most about 2 times, and 3 or more times in a row. It can be seen that it is rare. Therefore, even if the 5 vowels (a, i, u, e, o) of the Roman alphabet are divided into 3 groups and assigned to 3 buttons similar to Figs. 10-1 to 10-4, and vowels are entered by the repeat selection method It can be seen that ambiguity rarely occurs. In particular, in the case of Japanese, when “a” is entered, it is easy to see that the corresponding Japanese is “あ”, and when “na” is entered, the corresponding Japanese is “な” (the same is true for the rest of the Japanese alphabet). Therefore, the moment the user inputs “na” and the system verifies that the input value is “na”, the system can provide “な” to the user.

The Roman alphabet consonants used in the Japanese notation of the 50-phone diagram are 14 of k, s, t, n, h, m, y, r, w, g, z, d, b, p. The main sound is expressed by combining two Roman alphabet consonants (eg cha, sha), a combination of “y” (eg kya), or using “j”. The cases where Roman alphabet consonants appear more than two times in a row are the cases of ch, sh, ky, ny, hy, my, ry, gy, py, py, and so on, and the case of aspiration. It is said that when a tactile sound is used, the same alphabet may appear 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 a 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 required to input English, but can be grouped around 16 alphabets. For example:

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

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

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

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

12.5 intentional release of language restrictions

The language restriction repetitive 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. It is desirable to be able to set whether or not. However, even in the "Language Restricted Input Mode", which enables the language-restricted input method, if the user wants to input a word that does not exist in the dictionary and is contrary to the word generation rule (alphabetical combination rule), after entering the alphabet, a specific function (eg For example, after deliberately confirming the target alphabet by inputting a space and a left progression or word ending), all alphabet combinations can be entered by entering the next alphabet. For example, in Fig. 10-1, when the user inputs "622~" in "English limited input mode", the system recognizes "st~" instead of "sdd~", but if the user is "sdd~" If you want to enter "62", then enter the space and left shift function, then enter "2", or enter "62" and then click the "word termination function (or a control that can give the effect of closing words)" Enter some other means of activation and enter "2". When the word end function is activated after entering "62", the system can recognize the next "2" as "d" because it comes out first after "word start". To overcome the language restriction in the specific language restriction input mode by intentionally inputting the word termination function in this way is called "intentional language restriction release" for convenience. An example of "sdd~" is "intentionally lifting English restrictions."

Similarly, if the user does not exist in Chinese Pinyin, but wants to input "ui", which is a vowel combination that exists in English, in "Chinese limited input mode (Applying Chinese limited repeat selection method)" in Fig. 10-2, "u" After entering, enter the means to terminate the word (as mentioned in the previous example) again, and then enter "i". Otherwise, as mentioned in the previous application, if you press the button assigned with “i” after entering “u” in “Chinese-limited input mode (applying Chinese-limited repetitive selection method)”, the modified alpha of “u” A bet (eg, an alphabet with a tonal sign in "u" or an alphabet with ".." over "u"-when "..u" is regarded as a variant of "u" and is entered). (Because it is said that the button assigned with "i" is used as a control button when the button assigned with "i" is entered after the vowels "u" and "o" when applying the Chinese restriction repeat selection method) In the end, even in the Chinese limited input mode, the user can enter words of combinations that do not exist in Chinese Pinyin (for example, all alphabetic combinations such as English words). In other words, a user who mainly speaks Chinese can enter all alphabetic combinations that do not exist in Chinese without changing the setting again while setting the Chinese restricted input mode (Chinese restricted repeat selection method application mode). . This means "intentionally lifting Chinese restrictions".

In the method using the three vowel elements of Korean in Fig. 4-5, the same can be applied to inputting consonants or vowels as single characters. For example, in Fig. 4-5, if you want to input the consonant "ㄱ" and the vowel "ㅡ" as single letters, enter [1] in the "word start" state, and then enter the means to give the word end function, Enter [*] in the word start state again. This is because if you press the [1] button and the [*] button consecutively, it becomes "that". In the standard keyboard (standard keyboard in English and Korean), when the right arrow button is pressed, the "word end" space is not entered and the word end function is activated. If the right arrow button is additionally provided in the present invention, this is the same. Can be applied.

12.6 Delay time for release of language restrictions

It was said that "Battery Strike Delay Time" and "Battery Strike Delay Time" can be applied even when three or more letters are assigned to one button. For example, in the standard English keypad shown in Fig. 1-1, if the batter delay time is set to 0.1 seconds and the [2] button is pressed twice within 0.1 seconds, the system can regard it as inputting B.

Similarly, when the [2] button is pressed 3 times in succession (ie [2]+[2]+[2]), the first input value and the second input value (ie, the first [2] button and the second [2] button) If the delay time interval between the intervals is within the time set as the battered delay time (eg 0.1 seconds), and the delay time interval between the second input value and the third input value is within the time set as the battered delay time (eg 0.1 seconds) ( In other words, [2] + within 0.1 seconds + [2] + within 0.1 seconds + [2]), C is entered so that the system recognizes it. Or, when the [2] button is pressed three times in a row (ie, [2]+[2]+[2]), if the total input time is within twice the multi-stroke delay time (eg 0.2 seconds), enter C. You can also make the system aware of it.

In addition, in the case of English, for example, assuming that there is no "..u" in Fig. 10-1, the nature of the English vowel "a" not appearing consecutively, and the nature of "i" not appearing continuously is strictly If applied, when entering an abbreviation such as "NII", you will be able to enter "NII" in the English restricted repeat selection mode through "Intentional English Restriction Release" by entering the word end function. However, if a certain time elapses after entering "NI", NI can be confirmed even if the word end function is not entered. This predetermined time may be set in the same manner as the "Everything Delay Time" mentioned in the previous application, but it would be preferable to set it longer than the "Everything Delay Time". For example, if 2 seconds elapse after inputting "NI", NI is confirmed even if the word end function is not entered, and the system enters the "word start" state again. 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 obvious that this can be applied equally in all languages.

The various delay times are summarized as follows.

Battered Strike Delay Time ≤ Altruism Delay Time ≤ Temporary Language Restriction Release Delay Time

All three delay times may be set the same, but it would be desirable to set the altruism delay time longer than the battering delay time, and the temporary language restriction release delay time longer than the altruism delay time.

12.7 How to Select Repetitive Portuguese Restriction on the Consonant Separation Keypad

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

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

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

In addition, it is said that there are double consonants such as gn, mn, pn, ps, pt, tm, ch, lh, nh, rr, ss. Therefore, in configuring the consonant vowel separation keypad for the Portuguese limited input method, it is necessary to prevent the above alphabets appearing consecutively from being grouped into the same group. For example, refer to Fig. 10-*. However, “mn” is grouped into the same group, which can be modified appropriately and placed into different groups. The reason that 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. /bp/, /dt/, /gk/ ... -Grouping), and there are few cases in which alphabets with similar pronunciation appear consecutively.

In Portuguese, there are 5 vowels of a, e, i, o, u, and a, e, o are called strong vowels I, e are weak vowels. When two different vowels appear in succession, 6 types of “strong vowel + weak vowel” (ai, au, ei, eu, oi, ou) and 1 type (ui) of “weak vowel + weak vowel” It is called. That is, strong vowels and weak vowels can be grouped into separate groups (eg, in a state where there is no “..+u” in Fig. 10-6). In addition to these groupings, it is also possible to group the weak vowels and strong vowels into an arbitrary number of groups by preventing them from being in the same group. For example, it can be grouped as /a / e o / u i/.

12.8 How to Select Repetitive Spanish Restriction on the Consonant Separation Keypad

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

bl, cl, dl, fl, gl, pl

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

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

The basic vowels in Spanish are a, e, i, o, and u. Of these, a, e, and o are called strong vowels I and e are weak vowels. When two different vowels appear in succession, 6 types of "strong vowel + weak vowel", 6 types of "weak vowel + strong vowel", and 2 types of "weak vowel + weak vowel" (iu, ui) do. In the case of triple vowels, it is said to be combined like “weak vowel + strong vowel + weak vowel”. That is, if the strong vowels and the weak vowels are grouped into separate groups (eg, there is no “..+u” in FIG. 10-6), only the case of “weak vowels + weak vowels” becomes ambiguity. In this case, since both iu and ui are possible, the ambiguity can be overcome by applying the battered delay time/the other delay time or by using a method suggested by the applicant, such as intentionally canceling language restrictions. The same applies to cases where the same vowels appear consecutively, the same consonants appear consecutively, and other ambiguities may occur.

12.9 How to Select Repeated Italian Restrictions on the Consonant Separation Keypad

In Italian, j, k, w, x, and y are said to be used only for archaic or foreign words. You will need it for input in English, etc. In the grouping of consonants, the remaining consonants excluding the five consonants may be grouped as the center, and the remaining five consonants may be properly grouped.

In Italian, diphthongs are said to be ia, io, ie, iu, ai, ei, oi, ui, uo, ou, eu, etc. Also, except for iu and ui, it is a combination of strong vowels (a, e, o) and weak vowels (u, I). In the case of triple vowels, the structure is "weak vowel + strong vowel + weak vowel". Therefore, grouping of strong and weak vowels can be used, such as /a e o/ and /u I/, and ui and iu may have ambiguity.

12.10 How to select repeated German restrictions on the consonant separator keypad

Vox consonants in German are said to be ch, chs, ck, ds, dt, ng, nk, pf, ph, sch, sp, st, th, ts, tz, tsch, etc. Also, consonant grouping in Fig. 10-* may be referred to in the grouping box so that consonants appearing consecutively 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 this can be used in the language restriction parallel input method described later. In the case of Tsch, it may appear dark, but it is said to be used very rarely.

There are 5 short vowels in German, and there are transposed vowels with “..” above a, o, and u. The double vowels are said to be au, ei, ai, eu, “..au”, ie, etc. When entering 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, it can be grouped as /a e o/, /I u/, and many variations are possible.

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

12.11 Vietnamese language restriction input method

12.11.1 How to input Vietnamese language restrictions on the consonant vowel separation keypad

It is said that Vietnamese syllables are mainly composed of "vowels", "consonants + vowels", "vowels + consonants", and "consonants + vowels + consonants". In particular, it is said that a single syllable is the basis for Vietnamese. Although the number of Gospel words is increasing, the number of monosyllables means that it is easy to configure the input system in the consonant separate keypad.

In Vietnamese, there are five basic vowels a, e, i(y), o, u and “v+a (a vowel with v on top of a. Lee Han'x+vowel' is a vowel with'x' on the vowel)”, “^ It is said that there are six vowels: +a”, “^+o”, “,+o”, and “,+u”. It is said that “y” is a long pronunciation of “i”. The consonant separate keypad can be configured with only five basic vowels, and the remaining vowels can be entered by the control processing method. A character vowel separation keypad can be configured with only some of the basic vowels and the variable vowels, or a consonant separation keypad can be configured with all 11 vowels.

Since Vietnamese double vowels and triple vowels have various combinations, it is not easy to group the five basic vowels into two to three groups similar to those in Fig. 10-* so that there is no ambiguity when applying the repetitive selection method. In addition, there are 6 tones in Vietnamese, and 5 tones are displayed above or below the vowel. In addition, the same vowel does not appear consecutively in Vietnamese, which is a useful property for inputting Vietnamese vowels. Therefore, it is conceivable to put five basic vowels into five groups, input the transformed vowels by the hidden repetitive selection method, and add tonal codes to the basic vowels and the variable vowels by the control processing method. Here, y can be regarded as the transformed vowel of i. That is, the vowels /'a','v+a','^+a' /'o','^+o',',+o' /'u',',+u' /'i', It is divided into 5 groups of'y' /'e' and'^+e' /. By modifying this, it is possible to 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 4 groups:'y','e', and'^+e' /. If only 5 groups are placed, vowels can be entered without ambiguity by applying the repetitive selection method. In each group, an arbitrary alphabet may be used as a representative alphabet and displayed on the keypad and the rest of the alphabet may not be displayed. It would be natural for a short vowel to become a representative alphabet, and in the case of dividing it into 4 groups, it is possible that both i and e are displayed. The order of selection according to the number of button presses can be determined in consideration of the frequency of use.

It is said that Vietnamese consonants include “-+d (‘-‘)”, which is not found in English, and English f and z are not used. '-+d' is regarded as a modified alphabet of'd', and the (hidden type) repetitive 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 considered to be used infrequently. In the present invention, it is considered that w is not used, but if necessary, it can be included in an appropriate group.

It is also said that there are ch, gh, gi, kh, ng, ngh, nh, ph, qu, th, tr, etc. Among them, gi and qu are not considered here because they are a combination of consonants and vowels in form. The fact that Vietnamese is mainly composed of monosyllables means that unlike other languages, syllables consisting of “ja+mo+ja” rarely appear consecutively. Except for the above case, consonants and consonants appear consecutively. It means that there are few cases. In the end, in applying the repetition selection method by dividing consonants into several groups, if the consonants constituting the above consonants are grouped so that they are not grouped into the same group, consonants can be input without ambiguity as in the case of Chinese.

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

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 consonants are divided into 6 groups and vowels are divided into 5 groups, 11 buttons can accommodate consonants and vowels, and the other button can be used as a control button to add tonal signs to vowels. If consonants are divided into 6 groups and vowels are divided into 4 groups, both consonant buttons and vowel buttons can be accommodated with 10 number buttons. This is an effect that simple codes consist of only numbers in the use of simple codes. There is. The remaining two buttons can be used as a control button for inputting a tone code and a subsequent control button to remove ambiguity.

12.11.2 Vietnamese restricted input method using pairs of consonants and vowels

Vietnamese vowels and consonants can be grouped into pairs and repetitive selection methods can be applied. You can refer to the case of Korean. If the pair of consonants and vowels is 10, the remaining consonants and vowels can be entered by the control processing method.

12.12 How to input Russian language restrictions on the consonant vowel separation keypad

Refer to the applicant's prior application PCT/KR02/00247 to construct a consonant separation keypad for Russian.

There are 33 alphabets in Russian. Among them, 10 are vowels, 20 are consonants, and consist of 1 semi-vowel (or semi-consonant), and 2 symbolic alphabets (hard consonant code, soft consonant code).

The following is an alphabetical order of 33 letters, listing uppercase and lowercase letters.

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

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

The 20 consonants are divided into voiced and unvoiced consonants as follows. The parentheses mean pronunciation.

Vowels are divided into hard vowels and soft vowels.

In proper grouping of Russian consonants, voiced and unvoiced sounds with similar phonetic values can be grouped. For example /б(b) п(p) / д(d) т(t) /… It is classified as. Consonants that do not form a pair in pronunciation can be grouped appropriately as suggested in the previous application. Some examples are as follows, and various variations are possible by grouping together unvoiced and voiced sounds that form a pair.

10 groupings

Case 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, it is also possible to include the semi-consonant Й and the hard consonant code Ъ and the soft consonant code Ь in the appropriate group. In addition, when assigning these groups to each button, some alphabets (eg, Й, Ъ, Ь, and other alphabets) may be omitted and not displayed to keep the keypad concise.

For vowels, 10 vowels can be grouped into 5 groups using a pair of hard vowels and soft vowels. There are 10 vowel alphabets in Russian, and 11 vowel sounds are pronounced, but the basic phonemes of vowels are said to be (a), (e), (i), (o), and (u). Of these, (e) and (o) are said to appear only under bullish conditions. That is, vowel phonemes (a) and (o) can be viewed as strong vowels. The remaining three vowel phonemes are said to be in the position without stress. Therefore, it is possible to divide the vowel corresponding to the double strong vowel into one group and the remaining three basic vowels into one or more groups with 5 basic alphabets out of 10 vowel alphabets in Russian. This is because it can be expected that vowels of the same type are difficult to appear consecutively (eg, contiguous vowels after strong vowels). For example, а(a) о(o) / у(u) э(e) и(i) / in two groups or а(a) о(o) / у(u) э(e) / и(i) / can be put into 3 groups. The vowels that form a pair corresponding to the basic vowel can be put together in the group to which the basic vowel belongs, and the repetitive selection method can be applied, or the control processing method can be applied by considering it as a modified alphabet of the basic vowel.

A consonant separation keypad can be configured within a 3*4 keypad by appropriately using groups of consonants and vowels (eg 5 groups of vowels and 7 groups of consonants, 3 groups of vowels and 9 groups of consonants). In Russian, like English, there are cases where a number of consonants are continuous (eg CCCVC...), but the typical syllable structure is called the repetition structure of consonants and vowels (CV, CVCV, CVCVCV, …). This means that when the repetitive selection method is applied in the consonant separator keypad, in most cases, Russian words can be entered without ambiguity (ie, with very little ambiguity).

12.13 Hindi language restriction input method on the consonant vowel separation keypad

In the applicant's prior application PCT/KR00/00601, a case of grouping Hindi consonants into 9 groups based on the similarity of pronunciation was shown, and in the present invention, a case of grouping into 10 groups was shown. In the case of Hindi, it was also shown that the group's sounds with strong pronunciation similarity can be grouped into the same group. For example, group consonants with the pronunciation of (k), (kh), (g), and (gh) in the previous picture are grouped into one group. The same is true for the rest of the pseudophonic groups. Among the 35 consonants in Hindi presented above, 33 consonants excluding __(ud) and __(udh) with lower points can be arbitrarily grouped into 9 groups or 8 groups. __(ud) and __(udh) are considered as variants 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 as described in the previous application.

Hereinafter, for convenience, the Hindi vowels will be expressed in English pronunciation in parentheses next to the underscore (regarded as the Hindi alphabet of the corresponding pronunciation in the underscore) or simply in English alphabets in parentheses. For convenience, __(aa) is (a-), __(ee) is (i-), __(oo) is (o-), __(ae) is (e), and __(aae) is ( ai).

The vowel __(ri) is also said to be classified as a consonant. It is also possible to group 10 vowels excluding the vowel __(ri) into 5 groups by forming pairs of 2 as above.

Vowels in Hindi are largely divided into short vowels of (a), (i), and (u) and long vowels of __(a-), __(i-) and __(u-), and the remaining 4 vowels are compound vowels. It is said that it can be expressed as a combination of short vowels. In other words, __(e) = (a) + (i) or (a) + (i-), __(ai) = (a) + (e), __(o) = (a) + (u) or ( a) + (u-), __(au) = (a) + (o). Therefore, basic vowels (a), (i), and (u) are assigned to 3 buttons in 3 groups, and basic vowels are input with 1 stroke of each button, and long vowels corresponding to basic vowels are basic vowels. You can enter the assigned button 2 strokes, and the remaining 4 complex vowels can be entered as a combination of basic vowels.

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

This is possible when ten vowels in Hindi do not appear consecutively in one word. If Hindi vowels appear consecutively, ambiguity may arise. That is, when you input **0, it is impossible to know whether you entered __(a-) and __(i) or __(ai). However, even if there are cases where 10 basic vowels appear in succession, 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. Language restrictions can be applied. In this case, if the user wants to input a combination of the long vowel and __(a-) and the short __(i), it can be resolved by using “intentional language restriction release” or “language restriction release delay time”. In other words, in the example, input **, activate the word termination function for a certain period of time or intentionally, and then enter 0.

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

Even in countries that do not use English as their mother tongue, English alphabets are also used on the keypad to input English. In India, since Hindi and English are used as official languages, Hindi consonants with similar pronunciations and English consonants can be assigned to the same button to add naturalness to the use of simple codes and character input. For example, it is as follows and can be modified.

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

Also, only English vowels (English alphabet vowels) can be displayed for concise arrangement on the keypad. As shown in the previous example, Hindi vowels have a strong pronunciation similarity to English vowels, so 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/, with strong pronunciation similarity, as shown in the comparison table between Hindi consonants and English vowels above. . . It is possible to make the keypad 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, just as Pinyin could be entered without ambiguity in the Chinese-restricted input mode in the example of Chinese, the Hindi-restricted input mode would input Hindi without ambiguity according to the Hindi language restrictions.

Hereinafter, some of the contents described in the earlier application are reorganized, and detailed details are further arranged.

(k)" 다음에 "

(a-)" 가 오면 "

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

"이 "

(k)" 와 합쳐져 "

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

(k)" then "

(a-)" comes "

Abbreviated form of (a-)" (ie, consonant combination) "

"This"

(k)" combined with "

The same is true for the rest of the vowels, and when a specific vowel comes after a consonant, the conjunctive expression 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 previous application, it is said that there is a certain rule (corresponding to Hindi spelling) that forms a conjoined letter between consonants even when consonants are combined with one another to form a "compound consonant", and it has already been applied in Hindi word processors and is widely used. Is being used. collection "

The abbreviation of "(a)" is supposed to be absent, but only consonants are indicated (eg. "

(k)") a vowel "

It is said to contain "(a)". Phonetically, "

"Is (ka), not (k). Some products, including the most commonly used Hindi word processors (eg "Hindi IME for MS Word 2000"). Hereinafter, unless otherwise noted, Microsoft's "" In MS Word 2000, it means "IME" in Hindi).

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

(k)" then "

(a)" key, "

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

(k)" then "

When (y)" is entered, the compound consonant "

This is similar to the input of consonants that can form a double support in Korean as a ending consonant (eg “ㄹ” and “ㅁ”) in a row, and the final consonant “ㄻ” is entered in small letters. It is said that there are regular and irregular shapes in the generation of complex consonants, and you can refer to the Hindi textbook for more details.The above is not a special content, but is in Hindi beginner textbooks, and is already widely known. It is already widely used in products (Hindi word processor, etc.).

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

(k)" 또는 "

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

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

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

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

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

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

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

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

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

(k) +

(a-) =

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

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

(u)"가 입력되면, "

(k) +

(o) =

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

(o) =

(a) +

(u)" 이므로)Likewise in the present invention, vowels after consonants "

(a) When the key is pressed, it is self-evident that it can be made to generate a consonant with a Hal (comma shape) under the consonant. For example, "

(k)" or "

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

(k)" and then "

(a)" is assigned to the button (eg [*] button),

(k)". As mentioned in the case of conventional word processing products, here "

When (y)" is entered, the compound consonant "

"It is the same to be. However, "

(k)" after being recognized, "

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

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

(k) +

(a-) =

"This is what the applicant suggested in the earlier application. Likewise "

(k)" after being recognized, "

When (u)" is entered, "

(k) +

(o) =

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

(o) =

(a) +

(u)" because)

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

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

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

(a)" The key is pressed and the consonant key is pressed again more than once. Therefore, in applying the present invention, even if the "repeated selection method" is applied to the input of the Hindi consonant, it means that a Hindi word can be input without ambiguity.

(a-)" 의 경우 "

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

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

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

(a-)" for "

(a-)"), which is obviously contrary to the user's convenience. Unless it is entered after a consonant, the user intends to enter a word beginning with a vowel, so the vowel is automatically in the basic form (eg. "

(a-)") should be recognized and displayed. In current word processors, "shift" + "

(a-)" button is input to recognize and output as basic type. In the present invention, in a word processor using a keyboard, when input is not after consonants (eg, the beginning of a word), Hindi basic vowels are automatically recognized. It is to further present the invention that becomes.

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

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

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

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

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

(a-)"가 인식되는 것이다. Applying on the keyboard, for example, at the beginning of a word (eg immediately after entering a space), the vowel "

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

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

(a) If you press the button assigned with" (eg [*] button) once, the basic vowel "

(a)" is recognized, again vowel "

(a)" 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 earlier application, a technique for recognizing the alphabet by "long press after short press" is introduced. Likewise, a "basic" vowel can be entered by pressing the vowel button at the beginning of the vowel combination, and other basic vowels can be combined by short pressing the vowel button to be combined later. For example, after entering a consonant, in the state of starting a vowel combination, the vowel "

(a)" If the button is long pressed, the basic vowel "

(a)" is recognized as ". Next vowel "

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

(a)" Long press of button and vowel "

(u)" A combination of a short press of a button is a basic vowel "

(o)" is recognized and printed. Similarly, "

(k)" next "

(a)" is pressed, "

"Become and again"

(a)" is pressed once more, "

=

(k) +

(a-)" becomes, and again

When (i) is entered, "

=

(k) +

(ai)", but the last

By long-pressing (i), "

You can type ". Here you can

When (i) is pressed again, "

In summary, it means that the basic type of the vowel can be forcibly displayed by long pressing the vowel button, and the vowel that is combined after the long press is also displayed as a basic vowel. This is applicable to all vowel combinations suggested by the applicant. The basic type of the other vowels can be recognized by the combination of the short press of the vowel button after the first vowel button to which the vowel is combined, which is suggested by the applicant ((a), (i), ( It can be applied not only to the combination of u), but also to the case of entering vowels by other vowel combinations.

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

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

(e) =

(a) +

(i) 또는

(a) +

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

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

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

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

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

(e) =

(a) +

(i) or

(a) +

It was said that you can enter "(i-)", but you can enter "__(e) = __(a) + __(i)", and you dare to enter "__(e) = __(a) + __(i-) You don't have to type it as ". Next to the vowel"

(a-)" vowel with half moon "

"Again, you can enter the vowel __(a) by pressing 3 times on the assigned button (eg [*] button).

(ud)", "

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

(k)", "

(kh)", "

(g)", "

(j)", "

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

(ud)", "

(udh)", with 5 borrowed consonants "

(k)", "

(kh)", "

(g)", "

(j)", "

(ph)" It is said that five borrowed consonants are rarely used. In this way, inputting letters with a lower dot is selected by repeatedly pressing the corresponding button by placing each consonant in the previously suggested consonant group based on the similarity of pronunciation. The following table is an example of grouping consonants with lower dots together based on the similarity of pronunciation: Of course, each group can be assigned to an arbitrary button and can be modified. When the number of alphabets explicitly or implicitly assigned to is increased, there is a disadvantage that the number of repeated pressing of a 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, place the first consonant of the above 9 groups on buttons [1] to [9] respectively (ie "

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

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

(r)" can be placed on the [9] button). Also, for example vowels, __(a), __(i), __(u) are [*], [0], [#] respectively When placed on a button, a very stable keypad is formed The above group is only an example, and it is obvious that it can be modified, and only one consonant representing each group can be displayed on the keypad, but it is displayed in plural (eg. [1] on the button "

(k)" and "

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

Pressing the button assigned with (k)" once

(k)" is recognized, press it again to "

(g)" is recognized, press it again to "

(kh)" is the recognized expression.

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

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

(d)" After inputting, press and hold the promised button (eg [6] button) to "

You can enter "(ud)". If you use this method, you can enter letters with a lower point even in an alphabet that does not have a lower point.

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

" 를 입력할 수 있다. In addition, there is a consonant with a dot on the consonant as a sign of a semi-non-consonant (a semi-tone of a non-consonant). For convenience, this fortune is called "upper point". Alphabets with a high point can also be entered as "control processing method using long press". For example, consonants "

After entering (k)", press and hold the promised button (eg [9] button) to "

You can enter ".

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

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

(k)" 다음 "

(a-)" 을 입력하면 "

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

" 가 된다. 역시, "

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

" 가 된다. 만약 "

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

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

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

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

(a)" is omitted and not displayed, so in reality, half-moon dots are attached to vowels or consonants. Likewise, you can enter "control processing method using long press". For example, "

(k)" next "

If you type (a-)""

It becomes (ka-)", and if you press the promised button again (eg [8] button), "

"Becomes. As expected,"

(k)" Then press and hold the promised button (eg [8] button), "

"Becomes. If"

Alphabetic groups including "(k)" are assigned to button [8], and "

(k)" If one or the other letters are placed together, "

You can see that "is entered as "88~" (where "8~" means long pressing the [8] button)

Next, a simple example of applying the parallel input method under the Hindi input method illustrated above will be shown. Hindi syllables start with "consonant + vowel +..." or "vowel +...", and consonant vowels alternate. Therefore, when entering Hindi, parallel input is possible using "(first vowel) + syllable reference initial code" or "(first vowel value) + syllable reference initial value simple code". Similarly, "(first vowel) + consonant-based simple code" or "(first vowel) + consonant-based simple code" can be used. The parentheses for "first vowel" and "first vowel value" are because some syllables begin with consonants.

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

(s) 가 입력되고 나서

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

(s)__

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

(s)__

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

(s)__

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

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

After (s) is entered, the vowel button is not entered, and the consonants continue as soon as another consonant button (e.g., a button assigned with the alphabet of the (t) group) is pressed, violating Hindi restrictions (Hindi word generation rules). It interprets the input value as a simple code.

After (s) is entered

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

(s)__

The word matching (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 suggest a word to the user (meaning there is a vowel in the underline) "

(s)__

(th)..." matches the word "

The user can recommend words such as ", ..., etc." Similarly, the moment "vowel + consonant" is recognized, and the moment the other consonant button is pressed without entering the vowel button again, the input value is interpreted as a simple code and processed. In this case, a word matching "first vowel + consonant + ___ + consonant..." will be recommended to the user.

(k)__

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

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

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

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

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

(k)__

In order to process input values such as "(g)...", after entering "(k)", use "(k)" by delaying for a certain amount of time (the language restriction release delay or other delay time mentioned in the previous application).

(k)" is confirmed, then "

This is possible by entering (g)". Or, according to the appointment (eg, pressing the right button), the previously entered "

(k)" after confirming "

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

In the present invention, it has been described that the alphabet is recognized in response to "pressing a button". 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 released. It goes without saying that the expression "button push" in the present invention includes a case where the alphabet is recognized at the moment of being pressed and then dropped. This is the same for other contents of the present invention.

12.14 Half-Consonant Separation Consonant Separation Method of entering language restrictions on the keypad

Half consonants (i.e., half vowels) are slightly different for each language.In English, w, y, j, etc. are generally treated as semi-consonants, and j is excluded in some languages, and v is included in other languages. Sometimes it does. In general, w and y seem to be treated as semi-consonants in common in almost all languages.

Here, because half-consonants have similar properties and phonetic values to vowels, putting them into separate groups is an extension of grouping consonants based on the similarity of 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 for foreign words in Spanish), and alphabets other than the English alphabet (the applicant is called a modified or additional alphabet for convenience. It is also used. Alphabets that are not used among English alphabets will also be required for input of commonly used English words. Therefore, if there are not many Roman alphabets that are not used in a particular language, they can be grouped together with half consonants and assigned to the same button. See Fig. 10-6 in Chinese.

You can also group alphabets that are not used in a specific language together and assign them to the same button.

12.15 How to input language restrictions on the keypad to separate incomplete consonants

In the present invention, it was shown that ambiguity can be removed or minimized by configuring a consonant separation keypad optimized for each language and applying a repetition selection method. Also, by configuring the consonant vowel 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. Accordingly, a case of slightly modifying this and allocating consonants to some buttons is a modified category of the language restriction input method in the character vowel separation keypad proposed in the present invention. This will be referred to as “incomplete consonant separation keypad” for convenience, and the button assigned with consonant vowels will be referred to as “character vowel mixing button” for convenience.

For example, the vowel “i” and the (half) consonant “y” are grouped together on the consonant vowel separation keypad, assigned to a specific button, and consonant (half consonant in this case) and vowel are formed in a predetermined order according to the number of button presses. It can also be selected (the remaining buttons are divided into consonant buttons and vowel buttons). If there are no consecutive cases like “iy” or “yi”, Chinese Pinyin input is possible without ambiguity by applying the Chinese restricted input method. In this case, assuming that the consonant is selected in the order of “y” (press once) and “i” (press twice) according to the number of times the specific button is pressed, this consonant note mixing button is pressed. The moment the button is pressed once, the input of the previous consonant button is determined to have input the consonant. Therefore, the system does not consider that "y" is temporarily input for the single press of the consonant combination button, and the vowel "i" is entered. Can be confirmed. This is because in Chinese language restrictions in which the consonant “y” cannot appear after a certain consonant can be used.

For another example, the vowel “i” and the consonant “j” or the vowel “i” and the consonant “k” may be grouped into the same group, and the (Language Restriction) repetition selection method can be applied. When entering Chinese Pinyin “… ik… " or "… ki… If there are consecutive cases such as ”, ambiguity can arise. Assigning consonants and vowels to some buttons without special reason complicates the input algorithm, reduces the efficiency of the input system configuration, and is worse than applying the language-restricted input method on a complete consonant separation keypad. . However, due to the characteristics of each language, some buttons may have a consonant combination button for a special purpose to allocate consonants to all 10 number buttons (see example in Korean).

This can be applied by modifying the flowchart of Fig. 10-7. See Figures 10-9. The same applies when there is more than one vowel mixing button, and the same applies when two or more vowels are assigned to one vowel mixing button. Applying the language restriction on the incomplete consonant separation keypad is a little more complicated (refer to the examples of “i” and “y” above), and it is necessary to apply consonant and vowel combination rules for each language. The flowchart in which the language restriction is applied in detail may be more complicated than that of FIG. 10-9. Fig. 10-9 may be considered as a very simplified representation of only the general contents after some modifications of Fig. 10-7.

For example, when Chinese Pinyin is input on the standard English keypad of Fig. 5-1, since five vowels are assigned to different buttons, vowels can be recognized without ambiguity. In the case of consonants, if a consonant follows "~vowel+n", it can be recognized without ambiguity. If "~vowel+n+m" is entered in "~n+X" ('X' is an English consonant), the vowel "o" assigned to the [6] button is combined. When a possible vowel (eg vowel'a') comes, it can be temporarily recognized as "~ao". However, since a normal Chinese piny syllable does 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 "n+m = 666" is entered after a vowel that "a" cannot be combined (for example,'e'), "eo" is not "~eo" by using language restrictions that cannot be combined. Can be processed as "~enm~" (since'~emn~' in Chinese Pinyin is impossible).

When a consonant comes after a syllable that ends in "~vowel+ng", ambiguity can occur. For example, "~ngg~" can be recognized as "~nh~". For Chinese, the system can search the index for all Chinese characters matching "~ngg~" and "~nh~" and provide them to the user. In the case of "~ngh+vowel~", it can be recognized as "~ni+vowel". If the following vowel is recognized as a vowel that cannot be combined after "i" (for example,'u'), the input value can be recognized as "~nghu", but otherwise, "~ngh+vowel~" and Chinese characters corresponding to all of "~ni+vowel~" can be searched and processed. In addition, when some ambiguity occurs, all words that match the possible interpretation results can be searched and provided to the user.

When inputting Chinese pinyin by applying the Chinese-restricted repeat selection method in the standard English keypad of Fig. 1-1, it was said that there were cases where “~ngh+vowels-” could be recognized as “~ni+vowels” in both cases. It was said that matching phrases could be searched and processed by Pineum Index. When all the full codes (full codes in the repetition selection method based on Fig. 1-1) are stored in the Pinyin index, as in applying the Chinese limited repetition selection method, in all cases where the input values can be generated (examples Search the index for “~ngh+collection” and “~ni+collection”) so that the system can recognize the matching phrase.

For example, when applying the repetitive selection method in FIGS. 1-1 and 5-1, “222” may be recognized as “aaa”, “ab”, “ba”, and “c”. Therefore, in FIGS. 1-1 and 5-1, “beijing = 22334445444664”, where a continuous group of numbers can be recognized as a combination of a plurality of alphabets. "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~” in four ways. As the input value increases, the number of possible combinations increases exponentially. Such an interpretable alphabet combination for the input value is also called “possible alphabet combination” or “candidate alphabet combination” for convenience.

However, when “22~” is pressed, it can be interpreted as “aa~” or “b~”. 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~” except for combinations starting with “aa~”. This can be seen similarly to the way that Chinese Pinyin can interpret the input value “22~” as “b~” by using Chinese restrictions that do not start with “aa~”. Therefore, when “2233~” is pressed, the index is searched only for two combinations of “bdd~” and “be~”. Here again, the phrase that starts with “bdd~” no longer exists in the index. When the system checks, the combination starting with “bdd~” is no longer considered, and only “be~” is processed according to the next input value. Also in Chinese Pinyin, “bdd~” can be viewed similarly to processing “input value “2233~” as “be~” by using the Chinese restriction, which is impossible. The input value “22334~” can be interpreted as “beg~”. In addition, the input value “223344~” can be interpreted as “begg~” or “beh~”. The moment the system checks that there are no more words beginning with “begg~” by searching the Pinyin index, the system inputs The value “223344~” is treated as “beh~”. This can be seen similarly to using the Chinese-restricted input method (eg, the Chinese-restricted input method in which “begg~” is not a valid syllable, but only “beh~” is a valid Pinyin syllable according to the Chinese Pinyin generation rules). When “4” is pressed once more and the input value becomes “2233444~”, it can be interpreted as “behg~” or “bei~”, but there are no more words starting with “behg~” by searching the index again. As soon as the system confirms that it does not, the input value can be processed as “bei~”. This is a Pinyin combination where “behg~” is impossible in the Chinese limited input method, so the input value “2233444~” is interpreted as “bei~” It can be seen similar to processing by doing.

In a system that stores all the words and full codes to be entered, the number of candidate alphabet combinations in simply “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 where the system can recognize the input value from the initial input value, alphabet combinations that do not exist in the index (in the example above,'aa~','bdd~', behg~', etc.) It would be useful to exclude them at the beginning of the input.

In this way, among a large number of candidate alphabet combinations that occur as the same input value in the iterative selection method increases successively, the system can search only for some candidate alphabet combinations existing in the index. If it is confirmed that none of the candidate alphabetic combinations by the input value 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 above consonant vowel separation keypad, select an arbitrary button (a button in the 3*4 keypad or a separate button on the outside) as a control button, select only the representative alphabet by one stroke of the corresponding button, and input the remaining alphabets by the control processing method. I can. For example, in the keypad of Fig. 10-6, “w, y, v” assigned to the [0] button is assigned to an arbitrary consonant button, and the [0] button is used as a control button, and “p = b+0” = 10” (when applying input after control). This was already mentioned in the earlier application.

13. Of the input Parallel input method judging by length

The length of shortcodes stored in the index may be less than a certain number in some cases. In addition, in certain cases, the types of shortcodes entered by the user or by the system (for example, type 1 (city name), type 2 (bank name),... In earlier applications, type 1 and type 2 are grouped in a tree form) It is said that it can be built) can be specified. If the type of abbreviated code entered as type 1 (city name) is specified and the length of the city name abbreviated code is 3 or less, when applying the parallel input method in which the abbreviated input method is the default mode, the length of the input value is 3 At the moment of exceeding, the system can process the input value as full code. Conversely, when applying the full-priority parallel input method, when three input values are input and a word end function (eg blank) is input, the system can process the input values as simple codes.

This will be particularly useful in cases where the length of a shortcode of a certain type (city name-Beijing, company name-四通集 團,...) Can be less than a certain length, such as Korean or Chinese. Since tangible nouns are often composed of a certain number of syllables or less, and it is natural to use them as a syllable-based initial code shortcode.For example, most bank names in Korean consist of two syllables, so the syllable-based initials for bank names are made up of two syllables. The length of the cord becomes 2).

It is determined whether the input value is a short code or a full code at the initial stage of the input and does not need to be provided to the user, i.e., if the length of the input value is more than or less than a specific length, it is determined whether the input value is a simple code or a full code. This can be useful if you can. That is, the shortcode index is not searched every time an input value is input, but only checks whether the length of the input value is longer than a certain length, thus simplifying implementation and improving system performance.

14. Language restriction parallel input method

Language restriction parallel input method is applied when the full priority parallel input method is applied, the moment the input value violates the “word generation rule” of a specific language (that is, the moment that violates the language restriction), the system regards the input value as a simple code. 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 restriction parallel input method using the language restriction repeat selection method as the full input method

14.1.1 Chinese

In particular, Chinese syllable-based initial codes based on Figs. 10-1 to 10-4 have only numeric values of the consonant buttons [1] to [9] (even when vowels a, o, and e are used alone. There is, but it is said that it is about interjection and practically not, and if the vowels i, u, ..u are used alone, y, w, y are added in front of them respectively). The full code to which the repetitive selection method is applied is one of the [*], [0] or [#] buttons for vowel input in most cases in the examples of Figs. 10-1 to 10-4. Should be entered. As mentioned in the Korean example of the previous application (method using vowel elements), this property is a good feature to know whether or not the input value forms a full code at the beginning of the input when applying the "parallel input method". Provides.

For example, using the repetitive selection method based on Figs. 10-1 to 10-4 as the full input method, and in the parallel input method (full priority parallel input method) in which the full input mode is the default input mode, input If the value "693 ... = shk ..." is entered, the input value does not form a full code at the moment the third value [3] is entered (up to'sh' is possible, but the next consonant'k' is Since it cannot come), the system can recognize the input value as a simple code and process it. After all, “112… = pd… When ”is entered, the input value does not form a full code the moment the third input value [2] is input (in Chinese input, '11' cannot be'bb' and can only be interpreted as'p', If p is followed by a Roman alphabet consonant d or t, the Chinese syllable cannot be formed), and the system can process the input value as a simple code. Likewise “7771… = wb… When ”is entered, the moment the fourth input value [1] is input, the system treats the input value as a simple code. After all, in most cases, when the second or third input value is input, the system can know whether the input value is a full code or not.

“14… = bj… When ”is entered, the system recognizes that the input value does not form a valid Chinese syllable (because there is no case where Roman alphabet consonants are combined like bj in Chinese Mothers) the moment the second input value [4] is input, 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 “Bijing”, which is a corresponding phrase of the simple code “14”. If there is no simple code starting with “14” or “14” in the index of the simple code, the system considers the input value as a full code again and provides “bj” to the user.

This is the same as in the case of Korean using vowel elements (Fig. 4-5). The full input method in Fig. 4-5 described above can be viewed as a Korean limited repetition selection method, and when applying the full priority parallel input method, if “12” is input, the input value does not constitute a valid Korean syllable. Regards 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, when it is confirmed that there is no more simple code matching “12” in the simple code index, the system considers the input value as a full code again and provides “ㄱㄴ” to the user.

For better understanding, simple codes are displayed in an ordered state in the simple code index of Figs. 5-4 and 10-5, but it does not matter in any form stored inside the system. However, if necessary when searching the simple code index, the system Sort the simplecodes and check whether the input value is no longer in the simplecode index.

In addition, a parallel input method using the shortened input mode (assuming that only the syllable-based initial code consisting of [1] to [9] is stored in the simple code index to be searched based on Fig. 10-1) as the basic input mode. In (shortened priority parallel input method), the moment the second value [*] from the input value "1* ..." is entered, the system recognizes that the input value is a full code without searching the simple code index and can be processed. have. This is also the same as the case of Korean in Fig. 5-4.

In Figs. 5-4 and 10-5, the Pinyin/Hanja index and the simple code index are described as one index. However, as shown in Fig. 5-1, there is a Pinyin/Hanja index (simply referred to as "Pinyin index". An index storing "Pinyin + Pinyin corresponding Chinese characters"-for searching the corresponding Chinese characters from the input Pinyin), and a simple code /Pinyin index (simply called "simple code index". It is self-evident that "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, only syllable-based initial codes are not necessarily stored in the simple code index, and other types of simple codes such as consonant-based initial codes may be stored together. Similarly, according to the type of simple code, it may be implemented by placing individual indexes such as syllable-based initial code index, consonant-based initial code index, and all-related simple code index.

As shown in Fig. 10-10, it is assumed that there is a syllable-based initial code "14", a consonant-based simple code "1473", and an all-associated simple code "1*#4#73" for "Beijing". When applying the Chinese-limited full-priority parallel input method on the keypad of Fig. 10-10, in the case of syllable-based initial code "14" and consonant-based simple code "1473", the system enters the moment the second input value "7" is pressed. The value can be regarded as a simple code and can be processed by searching the index. By the way, in the case of the simple code "1*#4#73" associated with the whole of "beijing", interpreting the input value "1*#4 ..." as a full code becomes "baiz ...", and "1* Until #4", Pinyin's rules of creation are not violated. However, "baiz ..." (and "baij ..."-because it can be "baij ..." depending on the next input value) is not a pinyin present in the pinyum index of Fig. 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..." Whenever each recognizes it, the Pinyin index is consulted to search for a matching phrase. As shown in Fig. 10-10, a matching Pinyin can be found up to "bai~", but the moment the input value is recognized as "baiz~" (and potential "baij~"), the system no longer matches the pinyum index. It can be confirmed that there is no (see (1) in Fig. 10-10). Therefore, the input value "1*#4..." up to "baiz~" can be regarded as a simple code, and matching phrases can be searched for by referring to the simple code index ((2)-(A ), (2)-(B)). Here, if a phrase that matches the input value "1*#4# ..." cannot be found in the simple code index, the system can treat the input value as "bai ..." again by considering the input value as a full code.

Due to the nature of Chinese, which is a meaning character, indexes of all Pinyin and Chinese characters (Pinyin/Hanja index) must be stored in the system, so the system inputs the moment when it is confirmed that the input value does not exist in the Pinyin/Hanja index even if the input value is a valid Pinyin/Hanja index. It 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 as soon as the system recognizes that the input value does not form a full code.

When different types of simple codes exist for the same word, it is possible to have a simple code for one pinyin in any form as a multiple katah as shown in Figs. 10-10 or 10-11. In processing the input value as a simple code (that is, processing the input value as a shortened input), the processing of (2)-(A) or (2)-(B) in FIG. Optionally possible. If the processing steps of (2)-(B) of Fig. 10-11 are used, it is not necessary to have a simple code in the index. The process of (2)-(B) is to search for matching Pinyin by comparing the pinyin combination that can be achieved by the input value and the pinyin index that can be achieved for each input value. As for the combination of pinyin that can be achieved by the input value, 2 alphabets are assigned to the [1] button and 3 alphabets are assigned to the [*] button, so the alphabet assigned to each button when "1*" is pressed. It can be easily seen that 6 combinations of (=2x3) are possible. For convenience, this will be referred to as "simple code possible alphabet combination" or "possible alphabet combination". In Fig. 10-11, since two alphabets are assigned to the [#] button, 12 combinations are possible when pressed up to "1*#", and 24 combinations are possible when pressed up to "1*#4". However, since there is no Pinyin starting with "poi ..." in the actual Chinese Pinyin dictionary when implemented in the system, combinations below "poi..." can be excluded from consideration. That is, for the input value "1*#4", "poiz..." and "poij...", which are combinations less than "poi...", may also be excluded. Likewise, it is possible to search for Pinyin matching the input value while excluding combinations that do not exist in the Pinyum index among possible alphabet combinations as well as "poi...".

In order to use the process of (2)-(A) of Fig. 10-11, a simple code should be included in the index, but it can also be processed when an irregularly defined simple code is used. (2)- To use the process of (B), it is not necessary to store the simple code in the index, but a simple code with a certain rule (for example, a simple code related to all) is required. It is necessary to know in advance the promised simple code type (for example, the all-related simple code).

Due to the nature of Chinese that must have indexes of all Pinyin/Chinese characters desired to be input, when a value interpreted as a full code as shown in Figs. 10-12 and 10-13 does not exist in the index, the input value is a simple code (i.e. , Shortened input value) and processed. When applying the full-priority parallel input method, Fig. 10-12 shows a procedure 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, when a syllable-based initial code is entered, the system interprets it as a full code and searches the Pinyin index.In most cases, the input value no longer exists in the Pinyin index as soon as the second to third input values are entered. This is because the system can recognize it. 10-13 shows a procedure for checking whether an input value constitutes a valid Pinyin syllable before searching for a Pinyin index using the linguistic characteristics of Chinese is added.

In the input system of not only Chinese but also other languages, when the system stores indexes of all words to be input, as in the procedures in Figs. 10-12 and 10-13, each input value is input. Each time, it is possible to interpret the input value as a full code, search for a word in the index to check whether it matches, and treat the input value as a short code when the matching word no longer exists.

14.1.2 English, etc.

When it is recognized that the 4th consonant is entered from the beginning of the first word starting with "st~" or "sp~", and 3 from the beginning of the first word without starting with "st~" or "sp~" As soon as the second consonant is recognized as being input, the system can process the input value as a simple code.

For example, the simple repetition selection method is applied on the keypad in Fig. 1-1, and the moment the third input value [7] is input when “467... = gms...” is input, the input value follows the English word generation rule. Since it violates, the system can treat the input value as a simple code. If there is a simple code “4678255 = install” associated with the entire install in the simple code index, the system can provide the simple code correspondence phrase install to the user. In the simple code index of the search range, “467… If there is no simple code matching ”, the input value can be treated as a full code again.

And, as described above, if the English limited repetition selection method is used as the full input method in the consonant vowel separation keypad, the input value does not start with the English input rule (eg, "st~" or "sp~" from the beginning of the word, and does not start with "st~" or "sp~" from the beginning of the word. Since it is easy to see if it violates 3 consonants), it is possible to apply the parallel input method more efficiently.

14.2 Language restriction parallel input method in which the control processing method except the representative alphabet is the full input method

In Fig. 1-1, when the first alphabet of each button is input as a representative alphabet and one stroke on the corresponding button, and the remaining alphabets are input by a control processing method (i.e., a control processing method other than the representative alphabet is applied), as described earlier in English If the word generation rule is violated by using the word generation rule, the language-restricted parallel input method can be applied, which treats the input value as a simple code.

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 when the third input value [7] is input when “467... = gms ...” is input. Since the input value violates the English word generation rule, the system can treat the input value as a simple code.

Similarly, it can be applied similarly to languages other than English, and the rest are similar to the language restriction parallel input method in which the repeat selection method is the full input method.

14.3 Overcoming the third ambiguity in the parallel input method of language restrictions

In the case of entering the simple code “72673” associated with the premise of “scope”, when the system first recognizes it as a full code, it becomes “72673 = pampd” and the input value does not violate the word generation rules of English. The input value is firstly recognized as a full code, and secondly, the input value is interpreted as a simple code, resulting in a “third-order ambiguity” that is recognized as a scope corresponding to the simple code. 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, when the user wants to enter a scope, they can select a scope by pressing a specific button (eg, the down arrow [v] button). Or, when the word input is finished after “72673” is entered (for example, if a blank is entered), the user selects “pampd” interpreted as a full code and “scope” interpreted as a simple code. It can also be provided as a list to the user and let the user choose.

The above case can be similarly applied to the parallel input method in which the control processing method excluding the representative alphabet is used as the full input method. In addition, even if the input value exists in the simple code index at the end of the word after the input value is entered in the shortened priority parallel input method rather than the full-priority parallel input method, language restrictions are applied when the input value is considered a full code. If it does not violate (third ambiguity occurs), it can allow the user to make a selection (pressing a specific button repeatedly or selecting from a list).

It can be applied similarly to languages other than English (especially in the case of Japanese that applies control processing methods other than the representative alphabet).

In order to select one of a plurality of candidates, a target phrase can be selected from the candidate phrases output by the system by using a random button that is not frequently used among move buttons. It has already been explained that this can be applied not only to cases where third-order ambiguity occurs, but also to all cases where ambiguity occurs.

15. Concurrent input method using character strings that violate language restrictions

It is said that the input value (full code or simple code) can be interpreted on the client side or on the server side. 11-1 and 11-2 are diagrams of an earlier application showing a case analyzed by the client side and a case analyzed by the server side, respectively. In other words, simply "system" is a concept that encompasses both client-side systems or server-side systems. If the input value is a simple code, the client side interprets it and transmits the simple code-corresponding phrase to the server side as a text string, and the server side uses this to provide various services. Similarly, when the input value is transmitted as a number to the server side and analyzed on the server side, the simple code can be analyzed on the server side and used for various services. The DTMF tone is transmitted from the client side and this input value is transmitted from the server side and used, of course, is one of the cases in which the numeric value is transmitted from the client side to the server side.

In the language restriction parallel input method, since the input value violates the language restriction (that is, the input value does not constitute a valid syllable of a specific language), the system treats the input value as a simple code, but enters it in the index of the simple code. There may not be a simple code that matches the value. In this case, it is said that the input value is regarded as a full code. However, for example, a user inputs "7799" with "Samsung Electronics" in mind based on Fig. 4-5, and "Samsung" corresponding to "7799" and "7799" in the simple code index in the client-side system If you don't store the "electronic", the system simply assumes that the user entered "". In the case of the stock information system, if the client sends the input value "7799" to the server side, or the Samsung Electronics corresponding to the input value "7799" to the server side, the stock information server can interpret "7799". Therefore, there will be no problem (assuming that the stock information server has a simple code “7799” and a simple code correspondence phrase “Samsung Electronics”). However, after the user enters "7799" in the character input mode on the client side, the client side treats the input value as a simple code, and since "7799" does not exist in the client side simple code index, it is converted to a full code. Considering that, if 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 meaningful value, "7799" used to input "ㅅㅅㅈㅈ" is extracted, and the corresponding phrase "Samsung Electronics" of the simple code "7799" You can track it and use it in the system. Or, as another method that can only be applied when a syllable-based initial code is used as a simple code in Korean, the system tracks and utilizes "Samsung Electronics" in which the first consonant of the syllable matches "ㅅㅅㅈㅈ" among the simple code correspondence phrases. To provide services.

This can be applied equally to a PC environment using a keyboard rather than a keypad. In other words, in the stock information system using an existing PC as a client, the user had to enter “Samsung Electronics” to inquire the stock price of “Samsung Electronics”, but even if only “ㅅㅅㅈㅈ” is input and transmitted to the server side, the stock information server The system recognizes that "ㅅㅅㅈㅈ" does not exist in the listed company name as a single letter, and after extracting the two methods ("7799" described above, "Samsung" tracking or "ㅅㅅㅈㅈ" and the first consonant of the syllable match) It is possible to provide a service by following "Samsung Electronics" tracking).

Another method is to register “7799 (simple code), Samsung Electronics (simple code correspondence phrase)” as well as “ㅅㅅㅈㅈ (referred to as'simple code correspondence character' for convenience)” in the server-side index, and send it from the client side. It can be checked that the value “ㅅㅅㅈㅈ” does not constitute a valid Korean syllable, and compared with the stored simple code correspondence character, it is possible to find out that the user intended is “Samsung Electronics”.

If the above is summarized in a picture, it is as shown in Fig. 11-3, and (A), (B), and (C) are selectively possible.

Furthermore, in the case of inputting characters through a device such as a keyboard in a client such as a PC (for example, inputting characters using a word processor of a PC), syllable-based initial codes are used. As a result, only the first consonant of a syllable is input, and the system (client or server) converts it into a target phrase, so that characters can be input at high speed or can be used in various information systems. For example, if the user wants to enter “Samsung Electronics”, when the user enters “ㅅㅅㅈㅈ”, the system can search the index and provide “Samsung Electronics” with the first consonant of the syllable “ㅅㅅㅈㅈ” to the user. Other methods described above (simple code extraction and index search of the input value based on the promised specific keypad, and simple code correspondence characters are stored in the index) can also be applied. See FIG. 11-5. (A), (B), (C) are optional.

Until now, when registering a common phrase and inputting it, it was a degree to specify that the input was simply combined with a special function button and a number button, regardless of the association with the phrase. For example, register "Samsung Electronics" as a commercial phrase and enter "alt + 1".

Similarly, the syllable of “四通集團 (satongjipdan: Applicant does not know the Chinese pronunciation, so the Korean pronunciation is regarded as Chinese Pinyin and used for convenience, but similarly applied to Chinese pronunciation)” The reference initial code becomes “6242” corresponding to s, t, j, 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, the server side does not constitute a valid Chinese syllable, so “6242” is extracted from the “sdzd” and the simple code (here, the syllable-based initial Code) It is possible to search for “四通集團” corresponding to “6242” (assuming that the server-side system stores simple codes and corresponding phrases).

As in the case of Korean, “ㅅㅅㅈㅈ” and the alphabet assigned with each consonant and a phrase that matches the first consonant of each syllable, based on Fig. 10-2, “sdzd ”and other possible consonant combinations ( Ex. “xdjd”, “stjt”, “sdjt”,… there are 16 cases) and words that match the first consonant of each syllable can be provided to the user.

Also, since the simple code corresponding character “sdzd” is stored in the server side and the value “sdzd” transmitted from the client side does not constitute a valid Chinese syllable, the user's intention is to compare the transmitted value with the simple code corresponding character in the index. The system can figure out what is “四通集團”.

If the above is summarized in a picture, it is 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.

Not only a device equipped with a keypad but also an information communication device such as a PC, when a user inputs “stjd”, a word (“四通集團”) that matches the first consonant of a Chinese pinyin syllable can be searched and provided to the user. Or, when the user enters “stjd”, the system (eg PC) registers the short code (simple code corresponding character) as the first consonant “stjd” of each syllable, and the moment the second consonant is input, the Chinese language restrictions are violated ( Since two Roman alphabet consonants appear instead of sh, ch, zh, etc.), the input value can be regarded as a shortened input value (regarded as a shortened input by the user) and processed. To extract the simple code from the input value “stjd”, the simple code (eg 6242) can be extracted by the previously promised keypad (eg 10-2). See Fig. 11-6, and (A), (B), and (C) are optional.

11-6(B) shows a word that an input value generates and does not generate a valid Pinyin syllable ("stjd" as a "syllable reference initial value" in the example) and the first alphabet of each syllable of the phrase stored in the index ( "sa-tong-jip-dan => stjd") to find a matching phrase. This can be seen as using the syllable reference initial value as the shortened input value. In the keypad of Fig. 10-*, the syllable reference initial value corresponding to "stjd" is "622442". As can be easily seen from the drawings, Figs. 11-6B are not provided with a simple code index, but it is only possible to have a pinyin index for inputting Chinese characters. Similarly, even if the input value is "consonant reference input value", the system can search for a phrase that matches the word (string) generated by the input value and the consonant of the phrase stored in the index.

In summary, the type of abbreviated input value that can be recognized regularly is "syllable reference initial value" similar to the type of simple code (for example, "beijing's syllable standard initial value is "144 = bj". ), "Consonant reference input value" (the consonant reference input value of "beijing" becomes "144773 = bjng"), "first vowel + syllable reference initial value", "word-based initial value", and so on. The system treats the input value as a shortened input value as soon as the input value violates the language limit.

The types of "shortened input values" presented so far are summarized in the table of Fig. 11-11. In Fig. 11-11, the shortened input value (A) encompasses (B) to (L), which shows the types of shortened input values that the system can recognize according to certain rules presented so far. Some associated simple codes determined in relation to some arbitrary alphabets and shortened input values consisting of only some arbitrary alphabets are also included. It can be seen that "total input value" (Z) becomes the full code of the full input method.

As previously suggested, if a certain condition (for example, the input value violates the full code generation rule, or does not constitute a valid syllable in a specific language, etc.), the input value is treated as a shortened input value. (In other words, the input value is regarded as not the full code of the promised full input method) This is the core content of the parallel input method, so even when a shortened input value not presented in the present invention is used, the parallel input of the present invention It is obvious that it is included in the scope of the method. In the table of Figs. 11-11, the shortened input values of (H) to (L) can be used in a device such as a PC as well as a device having a keypad, as shown in Figs. 11-5 and 11-6. 11-6(B) shows an example in which "syllable reference initial value" is used as the shortened input value. The term simple code or short code was used as a collective term for the shortened input value, and the shortened input values of (H) ~ (L) can also be viewed as simple codes in a comprehensive sense. That is, (I) "syllable reference initial value" in Fig. 11-11 may be referred to as "syllable reference initial value simple code", and shortened input values of (H) to (L) may also be named as well. .

In Fig. 10-*, when "14 = bz" is input as the syllable reference initial value, the system will search the index for a phrase that matches "bz" with the consonant of each syllable. If "4" is entered again here, "144 = bj", so it will search the index for phrases that match "bj" with the first consonant of each syllable (eg "beijing").

In the present invention, furthermore, it is shown that when an arbitrary shortened input value among the aforementioned shortened input values is input, it can be interpreted as various types of shortened input values. For example, a shortened input value is primarily regarded as a predetermined shortened input value (for example, a syllable reference initial value) and processed, and secondly, a different shortened input value (for example, a consonant reference input value) is treated. ), and treat it as another shortened input value thirdly, and it is suggested that one shortened input value can be interpreted as several types of shortened input values. If the shortened input value "144 = bj" is input based on Fig. 10-*, the system first searches for a phrase (for example, "beijing") that matches "bj" and the first alphabet of each syllable from the index. In other words, it is possible to search for phrases that match consonants among phrases in the index secondarily, regardless of whether or not there is a primary search result.

This shows that the system can interpret even if the user inputs any shortened input value suggested in Figs. 11-11. When this is applied, there can be multiple search results for one shortened input value, and the priority to be output may be applied according to the type of the applied shortened input value. For example, the phrase(s) retrieved by interpreting it as a syllable reference initial value is interpreted as a consonant reference input value and outputting the retrieved phrase(s) next. If a user mainly uses a syllable reference initial value as a short axis input value, it would be desirable to set the phrase(s) interpreted by the syllable reference initial value to be primarily output. Therefore, it is desirable to allow the user to specify the priority according to the type of shortened input value. Also, if a user wants to use only the consonant reference initial value, it would be desirable to be able to set the shortened input value to be interpreted only as the consonant reference initial value. The output priority of phrases obtained by interpreting the same type of shortened input value can be determined by factors such as frequency of use, as already mentioned. In addition, the priority to be output may be determined according to the frequency of use of each of the searched phrases regardless of the type of shortened input applied to the shortened input value analysis.

In the case of "jinzhi (禁止) and zhuijian (逐ㅇ), the syllable-based initial values are "jz" and "zj", respectively, which are both "444". In this case, when applying the full priority parallel input method, the third input value "4 At the moment "is input, the system can recognize that the input value does not form a pinyin syllable. Based on Fig. 10-*, if the syllable reference initial value is different alphabets assigned to the same button, all possible cases are searched. That is, for the shortened input value "444", you can search for all phrases that match "jz" and phrases where each syllable matches "jz".

Similarly, even when applying the single-axis priority parallel input method, the input value can be regarded as the single-axis input values in (B) to (L) of Figs. 11-11 and processed. In addition, the input value is treated primarily as a syllable reference initial value, secondly treated as a syllable reference initial code, and thirdly treated as a consonant reference initial value, and then processed as other shortened input values as well. It is possible to do. As soon as the input value is processed as a shortened input value and it is confirmed that no more matching words exist in the index, the system can treat the input value as a full code. It would be desirable to allow the user to pre-designate the type of shortcut input value that is mainly used.

“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 the syllable-based initial code of Kwonseol can be done as follows. In Chinese, the words “ch”, “sh”, and “zh ”are actually a single holy mother, and are marked with one symbol as the main note code, but when written in English alphabet, they are a combination of two alphabets. Accordingly, the simple code of the syllable reference initial value of zhuijian according to FIG. 10-6 may also be “4944” corresponding to “zh+j” including “h”. The syllable reference initial code will be “494” corresponding to “zh+j”. On the keypad of Fig. 10-*, the first letters “c”, “s”, and “z” that make up the winding sounds “ch”, “sh” and zh” are assigned to buttons different from the second letter “h”, so “jinzhi ( There is no ambiguity when the simple code of the syllable reference initial value of "禁止)" and "zhuijian(逐ㅇ)" is both "444".

In the full-priority parallel input method using the syllable-based initial value simple code as the shortened input value, the input value “4~” is recognized as “z~”, and when the input value “49~” is input, it is recognized as “zh~” And will take care of it. However, there are many words starting with “zh~”, so even if the system treats the input value “49~” as “zh~” and outputs the corresponding phrase to the user, it will have little meaning. Therefore, for the input value “49”, the system interprets the syllable standard initial value as a simple code and outputs and provides a phrase with the composition of the syllable “z__h__” (the underline indicates the location of the vowel). If “49” is interpreted as “zh” only, it is difficult to abbreviate a word whose syllable-based initial value is “z__h__”. In the case of Chinese, most words are composed of one syllable (letter) or two syllables (letters). Therefore, for abbreviated input of two-syllable words, it is necessary to process the input of winding seol sounds as abbreviated input. See Figs. 10-17. In Fig. 10-17, the liquid crystal phase is followed by [禁止] and then [. . Displayed as .] means that when there are multiple words of “z__h__”, other words in the lower order are displayed. Of course, the words “zh__” can be displayed as a subordinate priority, and according to the user's preference, the word “zh__” can be set to be displayed first. In general, it is recommended that the word “z__h__” is output first. It will be convenient.

When a vowel input is recognized after “49” (eg, when the vowel button is pressed), the system treats the input value as “zh__” (ie, the input value is processed as a full code). When a consonant input is recognized after “49 ”(for example, when the consonant button is pressed), the system treats the input value as “zh__X__” (capital ‘X’ is an English consonant that represents an arbitrary denomination). In other words, even in the full-first parallel input method, inputs such as “ch”, “sh”, and “zh” of the Kwonseol sound are primarily interpreted as a simple code (syllable-based initial value simple code or syllable-based initial code), and then 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 similar to the result of applying the consonant reference initial value simple code as the shortened input value and the shortened priority parallel input method. However, the syllable-based initial value simple code is applied as the shortened input value, and the parallel input method is applied first, but only at the beginning of the word (after the confirmation button is pressed or the word in the form promised in the input system ends). When a gwonseol sound is entered, the input value is regarded as a shortened input value and processed (in the example, the initial word of a word is “z__h__” (in the case of other gwonseol sounds such as'ch','sh', according to it), search for a word ).

Although described above with reference to Fig. 10-*, it is obvious that the above concept can be applied to other keypads.

Furthermore, the same can be applied not only to keyboards and keypads of PCs, but also to all similarly modified keyboards (the shape of the keyboards implemented on the screen can vary greatly).

16. Simple Code Parallel input method using possible alphabet combinations

In the case of using a syllable-based initial code as a simple code among the methods described above, comparison with the first consonant of each syllable does not have the index of the simple code (e.g. 6242 / satongjipdan / 四通集團) on the client side, and is only specific. It can be usefully applied even if it has only the index of the phrase (eg satongjipdan / 四通集團). For example, “62… As soon as the second [2] from "" is entered, the system recognizes that the input value violates the Chinese language limit and the input value, "62... = sd… , st… , xd… , xt… (For convenience, it is called “possible alphabet combination”)” and the words in the index that match the first consonant of each syllable can be searched and provided to the user. If the number of button presses increases, the number of possible alphabet combinations increases, and you can use this possible alphabet combination to compare/search with the phrase in the index. See FIG. 11-7. In the index of Fig. 11-7, “s t j p” and “s d .. ”, “x d. ”, “x t… While holding a list of ”(2**4 = 16 possible), the input value “sd… For ”, it could be compared to this multiple value of each record and give the user a 四通集團. This is also not recommended because the same concept or implementation is difficult and has no advantages. See Figures 11-9. Either way, comparing possible alphabet combinations that can be expressed as input values and the phrases of the index (pinyin in Figs. 11-9) are the same.

Similarly, if the client side does not have a simple code index (eg 7799, Samsung Electronics) and only has an index of a specific phrase (eg Samsung Electronics), the user has “Samsung Electronics” in mind and “77… When entering “”, the system recognizes that the input value violates the Korean language limit at the moment the second [7] is input, and the input value “77… = ㅅ ㅅ… , ㅅㅆ... , ㅆㅅ… , ㅆㅆ... (For convenience, it is called “possible alphabet combination”)” and the words in the index that match the first consonant of each syllable can be searched for and provided to the user. See Fig. 11-8.

If it is confirmed that a 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. This can produce a similar effect to the parallel input method under the premise that the user inputs only the value of the syllable-based initial code, without placing a simple code in the index, but placing only the index of the word. 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 restriction parallel input method. , The only difference is the procedure to search for the phrase corresponding to the input value. That is, at the moment when the full code generation rule is violated or the language restrictions are violated, the system considers the input value to be not a full code, but the input value is not using a simple code and the input value is a syllable-based initial 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. In the end, in the previously proposed parallel input method, only the part that searches for the phrase corresponding to the input value was modified in a special case (using syllable-based initial codes).

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 code, consonant-related simple code, first vowel + consonant-related simple code, the " It is possible to search for a target phrase from the index by comparing the phrases in the index with "possible alphabet combinations". In Fig. 10-11, the moment when the system interprets the input value as a full code and confirms that the pinyin interpreted as a full code does not exist in the Pinyum index, the system regards the input value as a shortened input value. Therefore, it is possible to search for a target phrase by comparing the "possible alphabet combination" for the input value and Pinyin. If this is shown as a drawing, it will be as shown in Fig. 11-10, which represents a part ((2)-(B) part) of Fig. 10-11 and is an example of a case in which the entire related flag code is used.

17. Full code In the stored input system Full input method And parallel input method

It can be seen from the above description that it is a little complicated to identify the correct word for an input value by a specific language restriction full input method on a specific keypad. (Ex. English input and Chinese pinyin input by repetitive selection method on standard English keypad) As explained above in Chinese, if the system has indexes of all the words to be input not only in Chinese but also in other languages, the input value Firstly, it is possible to interpret as a full code, and if it does not exist in the index, it is possible to interpret it as a secondly promised simple code.

Hereinafter, for convenience, the case of Chinese will be described as an example. As shown in Fig. 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 a phrase matching the input value and recognizes the target alphabet. I can do it. If a full-priority parallel input method is applied, the system treats the input value as a simple code of the promised type as soon as it is confirmed that the matching full code value no longer exists in the index. In Fig. 10-14, the process of inputting “北京” can be viewed as a process of interpreting and processing the input value as a full code. Since the full code is only stored in the index, the full code is analyzed through the search of the index.

In the case of applying the full input method in which words can be identified without ambiguity by the language restricted input method, storing the full code in the index is not useful. However, it can be useful if an ambiguous full input method such as the repetitive selection method is applied and all indexes of the phrase to be entered are stored. If all words to be entered are stored in the index when applying the full input method that may cause ambiguity, as described in “Language Restriction Input Method in Incomplete Consonant Separation Keypad” (in the case of not only Chinese but also other languages, Applicable), this full code index can be used to process the input value.

In the above, the example of Chinese has been described, but it is obvious that it can be applied to cases other than Chinese. In addition, it can be 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 variety Type of As code (input value) Parallel input method to process

A parallel input method is possible in which input values are treated as certain types of codes (input values). For example, in Fig. 10-14, if the input value is regarded as a full code (A) and an all-related simple code (B) at the same time, the system interprets the input value "1*#" as a full code. It is possible to recognize "bei" when interpreted as "bai" and all related simple code. In this case, the system can simultaneously provide "bai" and "bei" to the user.

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 "bai", which is the result of interpreting the promised shortcode, is output. 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 as only another type of code and, in the end, this is included in the category of the previously mentioned parallel input method. I would say it is. The system index does not necessarily have to store the full code and the entire related simple code as shown in Figs. 10-14, but can be applied equally to the case of simultaneously interpreting the input value as various types of codes.

19. Priority of words where ambiguity occurs

In any one specific input method (e.g., a specific full input method or a specific type of shortened 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. The target phrases can be output according to the order based on the priority when ambiguity occurs. For example, if ambiguity occurs when applying the full input method in Figs. 10-14, target phrases can be output and recommended to users according to "(A) priority," which is the priority between full codes (A). have.

Next, a case where the input value is interpreted as various types of predetermined codes will be described. As illustrated above, if the input value "1*#" is interpreted as a full code in Fig. 10-14, it becomes "bai", and if it is interpreted as an all-related simple code, it becomes "bei", which is interpreted as different types of codes. Thus, when ambiguity arises, the system selects the target phrase according to the priority when interpreting the full code ((A) in Figs. 10-14) and the entire related simple code ((B) in Figs. 10-14) at the same time. 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. In a parallel input method that treats the instantaneous input value as a syllable reference initial code and a syllable reference initial value simple code and processes the input value as a short code, "syllable reference initial code" and "syllable reference initial code" When ambiguity between "value simple code" occurs, it can be processed according to the priority. (In other words, if the syllable reference initial code is (C) and the syllable reference initial value simple code is (D), output the target phrase according to "(C) + (D) priority")

Although the explanation was given using Chinese as an example, it is obvious that if you do not input Chinese characters but use Pinyin as the target phrase, it can be applied equally to other languages.

20. Control processing method Full input method Parallel input method

2-1 and 2-2, when the control button is set to the [*] and [#] buttons and a control processing method other than the representative alphabet is applied, a parallel input method is applied, but a word consisting of only the representative alphabet is used in the index. It was pointed out that if you save all of them and apply the shortcut priority parallel input method, the system treats the input value as a full code as soon as "*" or "#" is pressed as the input value.

In the case of Japanese in FIGS. 2-1 and 2-2, it is assumed that all shortcodes are made up of numeric values only. In this case, an index that stores all words consisting of only the representative alphabet (which may be included in the short code index or may be configured separately from the short code index) is placed, and the parallel input method is applied, but the number button is used as the input value. While the bay is pressed continuously, the result of interpreting the input value as a full code and the result of interpreting as a short code by referring to the index of the word consisting of only the representative alphabet (or the simple code index containing it) are given priority. 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 Fig. 2-1 and Fig. 2-2 (that is, when the full-priority parallel input method is applied), it is interpreted as “あああ”, if If there is no word starting with “ああ~” and only “あい” or “あい~” exists, referring to the index of all words consisting of only the representative alphabet, “あい” or “あい~” is replaced with “ああ~” It takes precedence over what can be provided to users.

See Figs. 10-15 and 10-16. In Fig. 10-15, the input value "11" is interpreted as a full code, but since this is a word consisting of only the representative alphabet, it is checked whether it is a valid word by searching for "index of all words composed of only the representative alphabet". Here, if “ああ”, interpreted as a full code of “11”, exists in the index, it can be recognized as a valid word for the input value. As soon as it is confirmed that the phrase corresponding to the input value no longer exists in the index of all words consisting only of the representative alphabet, the system interprets the input value again as a simple code, and the system recognizes the corresponding “あい”. In Fig. 10-15, the system recognizes the input value "11" as "あい" with the highest priority. Depending on the input value after “11”, it can be “あい...” (“...” is followed by “あい” followed by another alphabet), so the system ranks it after “あ い”. You can also print it out. Likewise, even if it does not exist in the index, the target phrase may be “ああ”, so it can also be output as the next ranking of “あい”. In Fig. 10-15, “あい...” and “ああ” are displayed in dim colors and in the second and third recommended order, indicating that the system may output this way or only “あい”.

* In Fig. 10-15, (1), (2), and (3) may occur sequentially, or may occur at the same time, as mentioned in "A parallel input method for recognizing input values as multiple types of codes at the same time". have. Likewise, the indication of full code and simple code in the index is only to help understanding, and it is obvious that the same procedure can be performed even if the full code and simple code are not stored (simple code is a syllable-based initial code or In the case of a simple code that can be interpreted regularly, such as all-related simple code). As shown in Fig. 10-16, the same content is also applied when the index of all words consisting of only the representative alphabet and the simple code index exist as one index. Implementation data structures can be realized in various forms.

The operation result of the system is similar to the previously described parallel input method, but it can be seen that a single-axis priority parallel input method is not applied, but a full-priority parallel input method or a general parallel input method is applied.

This can be applied equally not only to the parallel input method in which the control processing method except for the representative alphabet is the full input method, but also to all parallel input methods in which the control processing method is the full input method.

21. Input of function

Among the functions, when entering a phrase (sentence), a blank is an essential function, and a delete (cancel input) function is also required. The enter function can be solved by no input for a certain period of time after input, but it is also a necessary function. These three functions are collectively referred to as "three basic functions" for convenience. In addition, a case conversion function is also required for languages with upper and lower case letters such as English. Among the up/down/left/right movement functions, the left/right movement function can be replaced with the delete and blank function, and the up/down movement function can be seen as not essential.

Here are a few examples that are listed in the order of essential functions among various functions for inputting phrases. Of course, this is for reference only, not an absolute standard, and may vary slightly depending on specific circumstances. This is because if Chinese is input through the English keypad, the Chinese character conversion function will be the most essential function. In addition, in Chinese-cultural languages such as Japanese or Korean, the Chinese character conversion function can be an important function.

1. Space-Enter-Delete-Case conversion-Local language/number/English mode conversion-Move (up/down/left/right)

2. Space-Delete-Enter-Local language/number/English mode conversion-Case/small letter conversion-Move (up/down/left/right)

3. Space-Enter-Delete-Chinese character conversion-National language/number/English conversion-Move (up/down/left/right)

4. Chinese character conversion-Space-Enter-Delete-English/numeric mode change-Move

17.1 Function input by control processing method

It was explained that alphabets and various symbols can be selected by the control method. The same can be applied to select various functions. 12-1 is an example showing that meanings of various functions are assigned to numeric buttons, and these can be implemented in combination with "function control". Number buttons associated with each button can be associated and assigned to make it easier to remember. In Fig. 12-1, the left and right arrows are intuitively recognizable, and putting an enter in the center is also to make it easy to know the number buttons and their related functions. As for the remaining necessary functions, it is possible to facilitate memory by associating the button with the alphabet related to the name of the function for each language. In Fig. 12-1, the shift function is associated with the [7] button assigned with "S".

In Fig. 12-1, for convenience, as in the case of the Korean version of the previous application, assuming that the aspirated sound control and the sound sound control are selected according to the number of times the [*] button is pressed, and then the function control is selected, enter = [5]+{ Function} = [5]+[*]+[*]+[*]. If the alphabet selected with [5] button 1 stroke is an alphabet that does not have aspirated/hardened sounds, it is possible to apply the skip control process and press Enter to enter [5]+[*].

The function associated with each button may or may not be displayed on the numeric buttons. However, it was pointed out that the number buttons associated with groups of various symbols can be displayed on a part of the LCD screen so that they can be easily recognized, so that it is not displayed on the buttons, and the convenience of use can be added while maintaining a concise arrangement. The same can be applied here. See Fig. 12-2. Also, as pointed out in the symbol input, the user can redefine the function associated with the function and the number button.

If the [*] or [#] button is not used as another control button as in the case of English, you can select “Function Control” with one [*] button. You can enter the 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.

[*], [#] are used as control buttons, and when alphabets and various symbols are input as a one-dimensional control processing method, cross combination of control buttons (in this case, [*]+[#], [#]+[ *]) can be used to input various functions. If the control button is not used repeatedly, you can also use [*]+[*] or [#]+[#] to enter the function. Since “[*]+[#]” is a shape that goes from left to right, users can easily recognize it when used as a right movement function (or blank). Conversely, [#]+[*] can be easily recognized by the user when used as a function to move left (or delete) from left to right.

This can be understood from the perspective of a multidimensional cross control processing method. As an example of input, if the user inputs ^a = a + [*] by applying the input after control, if the user inputs “a + [*] +[#]”, the system will enter a + [*] ^a is recognized as input, but the next [#] cannot be followed (even if the [#] button is used as another control button), the moment [#] is input, the system displays “[*] +[ It can be recognized that “#]” has entered the right movement function. It can be seen that the case of designating the control line input is similar.

In the case of Japanese, the 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, enter blank = [*]+[#]+[*], delete = [#]+[*]+[#]. In the case of the blank function, the shape formed when [*]+[#]+[*] is pressed is reminiscent of the arrowhead of the right arrow, so it is easy to remember this. In the case of deletion, when [#]+[*]+[#] is pressed, the arrowhead of the left arrow can be reminiscent, so it is easy to remember this. The reason this is possible is the same as described earlier.

In summary, it can be seen that various functions can be input by alternately combining the control buttons twice when applying the 1D control processing method, and combining the control buttons 3 times when applying the 2D 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 the control buttons N+1 times.

22. Chinese character conversion

Korean, Chinese, Chinese Pinyin and Chinese characters are a one-of-a-kind correspondence. For example, the Chinese characters corresponding to “Politeness” are 禮意, 禮儀, 銳意… There will be many with.

In the case of Chinese, Chinese characters that correspond to “beijing” include 北京, 背景, etc. (if no tonal code is added). Therefore, you can press the Chinese character conversion button repeatedly to select a subsequent Chinese character (eg, 北京(2nd), 背景(3rd)). For example, if you press the Chinese character conversion function after typing beijing, it becomes 北京, and if you press it again, 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, so if the target Chinese characters can be determined, users can Can be provided to. For example “beij… If the only word starting with "" is "北京", when the user inputs "beij", "北京" can be provided to the user. If there is only one "beijing" in the Pinyum index, the system converts "beijing" to "北京" at the moment when all "beijing" are recognized definitively, even if the user does not confirm the target Chinese character in the middle of the input. It can be printed.

In the case of Japanese, hiragana and katakana have a 1:1 correspondence, and hiragana or katakana and kanji have a 1:multi relationship. Therefore, it has been described that it is possible to convert into katakana by inputting hiragana and then inputting katakana conversion control (eg, “ah/a” control in Fig. 2-1). If the modified alphabet in Fig. 2-1 is input by the cross control processing method, the “Ah/Ah” control can be selected with two [0] buttons. Here again, you can select the kanji corresponding to a specific hiragana or katakana by repeatedly pressing the [0] button. For example, if the “A/A” control is designated as post-input, input a hiragana word (or alphabet) and then press [0]+[0] to convert to katakana corresponding to the input hiragana, and then [0] Pressing the] button converts the first Chinese character, and pressing the [0] button once again converts the next Chinese character. On the contrary, in Katakana input mode, pressing [0]+[0] after inputting katakana converts to the corresponding hiragana, and pressing the [0] button again can convert it to Chinese characters.

23. Simple Code Building the index

Among the simple codes suggested by the applicant, the entire related simple code, syllable standard initial code, consonant related simple code, first vowel + consonant related simple code, word-based initial code, etc. are mechanically (i.e. automatically) specific phrases (words or phrases) It has a good property to extract simple code from ). Therefore, a simple code index (an index consisting of a simple code and a simple code-corresponding phrase) is automatically constructed for a word once input by the user using the full input method, and this can be utilized 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.

Different types of simple codes (eg, all-related simple codes and syllable standard initial codes) may be generated for the same phrase. However, in general, it will be convenient to use a specific type of simple code, and the user only needs to know the type of the automatically generated simple code, and can use it when applying the parallel input method. When this is applied, the simple code index becomes richer as the number of characters input by the user increases.

In order to extract the syllable reference initial code from a specific phrase in a specific language, it is necessary to separate the syllable 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 divisional rule, it is not difficult to automatically separate syllables from specific words by using them, and it is not mentioned in detail here.

For example, in the case of "Zhongguo" in Chinese Pinyin, syllables can be separated into "Zhong" and "guo" centering on the vowels "o" and "uo", which is more than the process of recognizing pinyin in the present invention. It can be done much easier. If the example of separating the syllables by forward scanning from the front of the word is shown, it is not possible to know whether the consonant "n" after "zho" is the consonant of the next syllable, but by looking at the consonant "g", it can be seen that it belongs to the first syllable. Likewise, "g" can be a consonant of the next syllable, but by looking at the next "g", you can see that the first "g" is a consonant that belongs to the first syllable and the second "g" is a consonant that makes up the next syllable. . (In Pinyin, any syllable can end with "~ng") Scan up to "zhongg" to isolate the first syllable "zhong". Next, "u" is, of course, a vowel constituting the second syllable, and consecutive vowels "o" are also a vowel constituting the second syllable. (In Pinyin, the English vowel "uo" may appear consecutively.) Since there is no longer an alphabet after "o", the system can separate the syllables of "zhongguo" into "zhong" and "guo", so It can be recognized that the initial value of the clause is "zg", and that the syllable-based initial code of "zhongguo" is "43" (based on Figure 10-6). In the case of other languages, of course, syllables can be automatically separated from specific words or phrases according to the syllable separation rules of the language.

24. From phrases without special symbols (subscripts) Target phrase Translate

In the case of beijing, if the vowel is not marked with a tonal sign, it is said that it corresponds to both “北京” or “背 景”. In this case, you can select a target phrase by repeatedly pressing a specific button or select one of both from the list. Said there was.

Similarly, in languages other than Chinese, if only the basic vowel is entered even though the tonal code is not added or a subscripted vowel must be entered, the index is searched in response to the repeated pressing of a specific button and the target phrase is provided to the user or the index is searched. Thus, 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 that have a large number of transformed alphabets, such as Vietnamese, and have complex tonal codes. However, the system must have an index of a phrase made up of a subscript on the basic alphabet. Likewise, building such an index can be built from words pre-entered by the user. For example, when the user enters the word “^+abc” (when the subscript'^' is added to the'a') through character input, the system stores “^+abc” in the system (“ It is okay to store both “^+abc” corresponding to “abc” and “abc”). If the user enters “abc” again and presses a specific button, “^+abc” is provided to the user or the user “abc” When inputting, a list of phrases corresponding to “abc” such as “^+abc” can be provided to the user. If “abc” is the target phrase, the user will select “abc” even if they do not press a specific button or the system provides a list of related phrases. The time point at which the list is provided may be the time point at which the input of the word is terminated, and may be any time point in the middle of the input.

25. Part of a phrase (word or phrase) Full input method A parallel input method of inputting and inputting a part with the shortened input method

According to the input of the word (full code input), the method of outputting the word matching the input content from the index and allowing the user to select it has been widely used. For example, consider the "auto-complete function" of Windows. Even when full input (input by full code), matching phrases are displayed among phrases (words or phrases) stored in the index by referring to the index (e.g., index for parallel input), allowing the user to select/determine. Of course you can.

This will be described with reference to the input system of FIGS. 4-5 to 4-8 as follows. For example, suppose the index contains words such as "thank you" and "thank you". If "10* = high" is entered, the system will match the word "high..." (ie, words starting with "high", "thank", "thank you",...) In the proper form. You can print it out. In an environment similar to a mobile phone, the content generated by the input value is seen on the input line (top of the liquid crystal in Fig. 13-1), and candidate phrases (words or phrases) output by referring to the index are listed at the bottom or similar to the list. It can be output in the form. The user can select and enter a desired word using a move button (navigation button), etc. Refer to Figure 13-1, taking a mobile phone liquid crystal as an example. 13-1 is an example of outputting a word matching a syllable formed according to a full input to the lower portion of the liquid crystal.

Here, when entering “thank you”, you can also enter “high” as well as shortened input for the remaining syllables (abbreviated input using simple code based on syllable initial value in the example). That is, input as “high school+ㅁㅅㄴㄷ = 10*+5723”. Here, the first syllable is “go” and the other syllables may provide a word corresponding to “ㅁㅅㄴㄷ” (ie, “thank you”) to the user.

However, about half of the syllables in Korean are syllables with endings, and the other half are syllables without endings. In the case of “Thank you”, if you enter “1*05723” in succession, it becomes “Gomㅅㄴㄷ”. The system processes the normal full input power until “Gomme = 1*057”, and the moment “2” is input, input It recognizes that a part of the value does not make up a normal Korean syllable, and the part that does not make up the remaining syllables (eg “ㅅㄴ ㄷ = 723”) can be treated as a shortened input. This also belongs to the category of “parallel input method (full (input) first parallel input method)” mentioned in the previous application, and the syllables recognized by the full input force (eg “bear”) are naturally interpreted as full codes, and the rest of the code is interpreted as a full code. The input value (eg “ㅅㄴㄷ = 723”) is interpreted as a simple code.

Here, it is also possible to find and provide words that match in the index (eg, if “bear” is stored in the index), including syllables previously formed by full input, and correspond to the input value interpreted as a simple code. You can provide a word (eg, if there is “yes” stored in the index), or print both cases. When outputting both, a specific word according to a specified appointment (e.g., a word containing a part interpreted as a full code has priority, or vice versa, or based on the priority of a word, or a specific group of words). Can be output to the top. Since various means are possible, it would be desirable to allow the user to set this output order.

In the case of outputting both, when “gom” and “weep” are displayed at the bottom of the LCD, when the user selects “gom”, the entire “gom” is “ It will be replaced with “I bear”, and when “Yes” is selected, it is natural that the corresponding “ㅅㄴㄷ” is replaced with “I” and becomes “I bear”.

Here, if only “Thank you” is stored in the index, it will not be possible to output “Thank you” in response to the continuous input of the input value “1*05723”. Therefore, the system can additionally interpret “1*05723” as “gom” and “high”, which can be interpreted at the same time, and output matching words (provided to the user) by referring to the index. Interpreting “gomㅅㄴㄷ” as “goㅁㅅㄴㄷ” is when the syllable preceding “ㅅ” recognized as the beginning of the shortened input ends as a final consonant, exclude it from the preceding consonant (ie, “high”), and the final consonant Is a single consonant between “go” and “ㅅ”. It looks a little complicated, but anyone with basic knowledge of Hangul processing can easily know it. The case where the double consonant is used as the finality can be similarly applied. 13-2 shows the priority of output as “word(s) of a specific group designated as prioritized output-word(s) including a part interpreted as a full code)-word not including a part interpreted as a full code ( S)-. . .” An example of outputting candidate words by applying the order of is shown. Here, “Yes” is output first, and it is displayed at the highest level as belonging to the designated group.

If the user wants to be interpreted as “high school” only, the promised operation that can confirm the syllable after entering “10* = high” (eg, no input for a certain period of time, or press the right arrow [>] button once). Etc.) by pressing “5723”, it is interpreted only as “high school” and you can search only the words corresponding to it. Even in this case, words corresponding to “Goㅁㅅㄴㄷ” (eg, “Thank you”) including the recognized syllable “Go” (eg, “Thank you”) can be output, and except for “High”, the words corresponding to “ㅁㅅㄴㄷ” You can print a word (eg if “correct” is stored in the index), or both. See Fig. 13-3.

Here, pressing the right arrow button (hereinafter referred to as “[>] button”) as an operation button for intentionally determining syllables can act as syllable determination. In addition, the [>] button can also be used as a blank button. 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). In other words, if “10*>5723” is entered, the system interprets it as “high school” and provides 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 = high" is entered.

In such a 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 a matching candidate word is provided in the middle of the full input. In addition, in the case of outputting a complementary word after corresponding only to the input value processed as abbreviated input (i.e., the input value interpreted as a simple code) excluding pre-formed syllables, the frequently used suffix or word search, etc., are quickly input as shortened input. It will be useful. For example, after inputting “thank you”, (confirm the input information by a predetermined number of steps), then “yes (assuming that it is stored in the index)” as “ㅅㄴㄷ”. In this way, frequently used suffixes such as “...” can be placed in a separate group (eg suffix group) in the index, and when candidate words are output in parallel input, the words of the corresponding group can be displayed first. If you enter “Thank you”, if both “Thank you” and “Thank you” are stored in the index, both “Thank you” and “Thank you” may be displayed in the candidate word list.

For one more example, when “Sejong ㅇ = 70##90*838” is entered, up to “Sejong” is 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 “Sejong the Great” in the index, “Sejong the Great” will be displayed. Conversely, if there is only "great" in the index, only "great" will be displayed. If there are both “Sejong the Great” and “The Great”, both may be printed, but it would be desirable to output only one (including/not including the part processed as full input) by appointment. Also, in the case of “Moonmu the Great”, if you enter “Munmu” as a full input and then continuously input “C”, it will become “Moonmun”. Therefore, if you want to enter “Munmu” with full input and only “Great King” as abbreviated input, enter “Munmu” and then confirm the entered syllable “Munmu” (eg the right arrow [>] button to give the end of the syllable). Press once to confirm), then you can enter “38 = ㄷㅇ”. Here, even though “Great King” has a lower priority than other words in the index corresponding to “Cㅇ = 38” (eg “Dawa”), if “Moonmu the Great” is stored in the index, the input value “5*025*0” For >38”, it is possible to output “Great King” in preference to other afterwords (eg “Dawa”).

Furthermore, it is possible to input some syllables by full input while entering a shortened input such as “ㄱㅁweepㄴㄷ = 157*623”, corresponding to “thank you”. If “157 = ㄱㅁㅅ” is entered, the system interprets “157” as a simple code (syllable-based initial value simple code or syllable-based initial code in the example) and searches for a word corresponding to “ㄱㅁㅅ” for each syllable. When “*6” is entered again, the system can recognize that the syllable “7*6 = wet” is formed as “157*6 = ㄱㅁsp”. That is, if the system recognizes that the previously entered “15” is a shortened input value, and when “23” is input again, this can be processed as a shortened input value because an appropriate syllable is not formed. Also in this case, the system can interpret some syllables as full code in “Lingerie” and also interpret some syllables as shortcodes and provide the corresponding “Thank you” to the user.

In the case of Chinese, one syllable is said to consist of "Holy Mother + Mica". In pinyin in Chinese, it was said that “Holy Mary” is a consonant of Roman alphabet, and “Mica” is a Roman alphabet vowel or “vowel+n” or “vowel+ng”. In other words, it can be seen that one Chinese character (one syllable) written in Pinyin consists of "consonant + vowel" or "consonant + vowel + n" or "consonant + vowel + ng" in Roman alphabet. Rarely, there may be syllables beginning with the vowels “a”, “e”, or “o”. It has already been pointed out that only “n” or “ng” can be used as the Roman alphabet consonant that can come at the end of a pinyin syllable. This can be regarded as the finality of Korean. Only “n” or “ng” can be used as consonants that can be used as a final consonant (the last consonant of a syllable).

For example, "中華(zhonghua)", "民國(minguo)", "中華民國 (zhonghuaminguo)",. . . Assuming that words such as, etc. are stored, input Pinyin by full input to “中華 (zhonghua = 49***7739##*, based on Fig. 10-6)”, and shorten only “民國(minguo)” (In the example, abbreviated input using a syllable-based initial value simple code as a shortened input value) is an example of entering "mg = 73 (based on Fig. 10-6)". After entering the corresponding Pinyin (“zhonghua = 49***7739##*”) in the input of “中華”, “mg = 73” may be entered after the process of selecting and confirming the candidates listed is mediated, or Pinyin After entering “zhonghua = 49***7739##*”, “mg = 73” may be entered continuously. In the former case, “民國(minguo)”, 民歌 (minge),. . . It is natural to output only words such as, etc. as candidate words. In the latter case, interpreting the input value “49***7739##*” as “中華” and outputting “中華民國” along with “民國” corresponding to “73” recognized as abbreviated input value. It is also of course. Regarding the input value “49***7739##*73 = zhonghua + mg”, for inputs up to “49***7739##*7”, the last “7” is the input of pinyin and is a normal full input. As a result, the system recognizes, but the moment the last “3” is input, the system recognizes that the last two input values “73” are shortened input values. This is the same as in the case of Korean previously described. Therefore, for the input value “49***7739##*73”, the system is configured with “中華” corresponding to the full input value “49***7739##*” and the “private country” corresponding to the shortened input value “73”. The word "中華民國", which is composed of "can be printed out. See Figures 13-4.

On the contrary, after entering “中華” as “zh = 49” by abbreviated input, select “中華” among the candidate words and do not enter, but continuously “民國” as the full input “7#773##***” When entered (ie, “497#773##*** = zhminguo”), “中華民國” corresponding to “z__h__minguo” can be output. Similarly, when entering “73##***” for the input of “民國 (minguo)”, it can be interpreted as “73##*** = mguo = m__guo” and output “民國”. As soon as “73” is pressed, the system regards it as a shorthand input and searches for the word corresponding to “m__g__” and processes it, but the next “##*** = uo” is processed as a vowel constituting the second syllable. . Entering “uo” after “mg” serves to compress “民國” among the candidate words corresponding to “m__g__”.

When entering Chinese character “Chinese” using other means (shortened input, full input, input using stroke, etc.) and then inputting “Republic of Korea” as “73” by shortened input, simply input value If “73” is interpreted as a simple code and the word corresponding to “m__g__” is provided to the user, a number of candidate words (eg “民國(minguo)”, 民歌(minge),.. .) are listed. Will be printed in the form. However, if “中華民國” is stored, it is possible to interpret “中華+mg = 中華+73” as “中華民國” apart from the one in which “民國” is stored in the index. In this case, “中華” has already been entered in one character, so in response to the input value “mg = 73”, “民國” is output in preference to other candidate words (eg “民歌(minge)”,.. .) can do.

When “zhong...” is entered here, the system may be interpreted as “zho” + “n__g__” or “zhon” + “g__”. However, since there are no syllables composed of “zho” or “zhon” in Chinese Pinyin (that is, of course not even in the Pinyin index), “zhong...” is interpreted as “中” by referring to the index. If there is, when “zhong” is input, it can be output as a candidate word according to a predetermined output order. For the input of “zhongg... = 49***7733” based on Fig. 10-6, 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 previously proposed input value as a full code and a short input value (simple code) at the same time.

In the above example, the case of using the “syllable-based initial value simple code” as the shortened input value (simple code) for convenience is presented, but when the “syllable-based initial code” is applied as the shortened input value, Fig. 11- The contents mentioned in 3 to 11-10 can be applied.

26. Character input method using long press and Long press Control processing method used

In general, one object (eg, alphabets, numbers, English alphabets, symbols (special characters), functions, and controls for various purposes in languages that do not speak English as their mother tongue, etc.) with one push of a button. (Referred to as this) can be expressed. Here, you can express an object different from the object you are expressing by simply pressing a specific button once but using “long press”. In the following, long pressing of a specific button will be referred to as "long press" or "long hit". Hereinafter, not expressing “long press” means that a button is pressed normally, and when described in contrast to a special long press, it is referred to as “short press”. Hereinafter, general contents will be described in the case of English, and application cases for each language will be described, 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, by long pressing a specific number button, it is used to input the number. However, it is not always possible to input only numbers. For example, pressing each number button in Fig. 1-1 inputs the first alphabet among the alphabets assigned to the button (eg, “A” by pressing button 1 once. Assuming that you are entering), you can enter the second alphabet (eg “B”) by long pressing. However, long press is a factor that interrupts the natural flow of input, so it is not desirable to apply it to the input of frequently entered alphabets. Therefore, it is desirable to apply the input by long press (long hit) to input an object that is not used often. In addition, it would be desirable to allow the user to set a time recognized by pressing as long as possible according to the skill level of each user.

In the present invention, a long press is appropriately used, but through this, it is shown that the input rule of a specific input method can be simplified, the expression range widened, and furthermore, ambiguity can be removed. Here, for convenience, a long press of the [2] button is marked as “2~” by adding a tilde (~) after “2”. As mentioned, when applying the existing repetition selection method, if the [2] button in Fig. 1-1 is pressed 3 times, it is possible to know whether "222" is "C", "AAA", "AB" or "BA". There is no ambiguity.

In Fig. 1-1, "A" is a long press of the [2] button or the corresponding button is pressed once, "B" is "A" and then the corresponding button is pressed once, "C" is "B" and then the corresponding button is pressed once (or After inputting “A”, pressing twice is the same). In the case that the alphabet in the same button is continuously input, it is possible to input without ambiguity if it starts with a long press in the second and subsequent alphabet input. For example, when entering “DACB”, you can enter “3 2 2~22 2~2” without ambiguity, and “ACB ”on the same button appears consecutively, but long press when entering “C” and “B” By being mediated, identification is possible without ambiguity. This example can be input with a feeling that is almost similar to the existing repetition selection method, and only when the alphabet assigned to the same button is input continuously, 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~”) to input “A”.

In the example above, a random alphabet (eg “A”) among the alphabets assigned to a specific button (including both explicit and implicit assignments) is the representative alphabet, and the remaining alphabets are the subsequent alphabets (eg “B”) , “C”), it can be seen that the subsequent alphabet is input by pressing the button to which the representative alphabet and the subsequent alphabet are assigned a predetermined number of times. In other words, “A (representative alphabet)-B (2nd successor alphabet)-C (3rd successor alphabet)” has a relationship, “A = 2~”, “B = A + 2 = “2~2”, “C = B + 2 = A+2 + 2 = 2~22”. In addition, it is said that you can input “A” with a normal press (i.e., single stroke) rather than a long press, unless the alphabet assigned to the same button is continuously entered, the existing repetition in the input of the representative alphabet As in the selection method, it is possible to input with a normal single press (ie, single stroke). Hereinafter, for convenience, this is referred to as “repetitive selection method by long pressing of the representative alphabet”.

If only two letters are entered using one button, one letter can be defined as a normal single press (i.e., single stroke), and the other letter can be defined as a long press (i.e., long hit). (Ex. “B = 1”, “P = 1~” in Fig. 10-1) However, as shown in Fig. 1-1, 3 alphabets per button (either explicitly assigned or implicitly assigned) In case (eg [2] button), the first letter is defined as one press (eg “A = 2”, the second letter is defined as long press (eg “B = 2~”), the third alphabet) By pressing twice (eg “C = 22”) or long pressing and pressing once (eg “C = 2~2”), there is also an ambiguity when entering the third alphabet. This is because when defined as “AA” can also be interpreted as “BA” when defined as “C = 2~2.” In this case, the first, second, and third alphabets can be arbitrarily defined. Even 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 repetitive selection method using a long press can be more useful when inputting not only alphabets assigned to each button but also numbers and symbols associated with each button, along with the ability to input without ambiguity. For example, a certain alphabet(s) “A1, A2, A3, ...” is associated with an arbitrary “button x” (either explicitly assigned or implicitly assigned), and a specific number “N1” It is related, and it is assumed 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, it is assumed that the alphabet “A1” is designated as the representative alphabet, and input by long pressing the “button x”. Fig. 14-3 shows the input of "A1, A2, A3, N1, S1, S2, S3" related to "button x" in a graph form. In Fig. 14-3, it can be seen that "A1S1 = xx~xxxx" or "A1S1 = x~x~xxxx" is input. Here, if the language is not English as the first language, the English alphabet "E1, E2, E3, ..." may be additionally inputted.

Furthermore, in entering the objects related to “button x” (eg “A1, A2, A3, N1, S1, S2, S3”), it is not a repeat selection method by long pressing the representative alphabet, but a normal repeat selection. By applying the method, it is also possible to input associated numbers and various symbols (special characters). However, ambiguity occurs when inputting objects related to the same button in succession, so after entering one object, in "Promised Delay of a Definite Time" or Subdivision (eg, "Complementary Items in Parallel Input Method"). It is necessary not to cause ambiguity by the input of the described [>] button once). For example, “A1, A2, A3, N1, S1, S2, S3” is associated with “button x”, and if you input “S1A1” by repeat selection method, enter “S1A1 = xxxxx>x” Can be. This is a technique used to overcome ambiguity in applying the repetitive selection method, but one point is different so that a specific number and symbol group can be entered in association with a specific button.

Currently, if there is a national language alphabet "A1, A2, A3" associated (assigned) to "button x", it will be "x =A", "xx = B", "xxx = C", or a defined maximum repetition When it is pressed more than the number of times (eg “button x” is pressed 4 times), it is the degree to which it is toggled cyclically as “xxxx = A” and “xxxxx = B”. The cycle toggle seems to be a consideration so that the target alphabet can be input again by repeatedly pressing the button that was pressed when an input error occurred when applying the repeat selection method. However, as suggested by the applicant, if the input of the delete button is used to delete the “last input value” rather than the deletion of the entire alphabet being created, there is no need to apply a circular toggle method. You only have to press “xx = B”, because 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 a process of entering an alphabet by long pressing after a short press of a specific button. In Fig. 14-4, rows A1, A2, A3, ... are input processes according to the existing iterative selection method. As for B2, it can be seen that A1 is input by a short press of a 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 any alphabet input is not defined only by long pressing 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 by some alphabet (eg alphabet E1), if “A1” and “E1” do not appear at the same time, this language restriction (language restriction in which A1 and E2 do not appear at the same time) is applied. You can enter A1, B2, E1 without ambiguity.

Also in Fig. 14-4, if a long press of “button x” is not defined as an alphabetic input, A1, B2, and C3 can be recognized without ambiguity. Also, in the case of A1, A2, D3, there may be ambiguity as “A1 = x” and “A2 = xx = A1A1”, but if A1 does not appear consecutively in a language, this language restriction (A1 does not appear consecutively Language restriction), you can enter A1, A2, D3 without ambiguity. For convenience, the same method as in Fig. 14-4 is referred to as "repetitive selection method by long pressing after short pressing". For example, in Fig. 10-6, input “i = #”, “u=#~”, and use “##~” as an arbitrary vowel (eg “ ^.. u”-“u” superscript “.” ..”) can be entered without ambiguity (in Chinese Pinyin, “i” and “u” do not appear consecutively). Of course, since “i” does not appear consecutively, it is possible to input any other target with “##”. The same can be applied to other languages. In Fig. 14-4, it can be used to input the alphabet of the lower order of rows A1, A2, and A3 (eg S1, S2, S3, ...).

26.1.2 Control processing method using long press

Next, an example of application to control selection is shown. In the following cases, the description is assuming that the control is input afterward. In the previous example, the reason for expressing “A” for both short and long hits of the [2] button is only to give an example that can be input with a feeling similar to the existing repetition 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, a single press of a specific button (eg [1] button) may indicate a specific object (eg an arbitrary “alphabetx”-where “x” means a random alphabet, not an actual “x”). It can be expressed, and a long press can express other specific objects (eg, arbitrary “alphabet y”). That is, “alphabet x = 1”, “alphabet y = 1~”. Some examples of “alphabet x” and “alphabet y” are conceptual, so even if they are defined as “A = 2~” or “A = 2” in “Repeated Selection Method by Long Pressing the Representative Alphabet”, “A” by normal pressing (ie, single stroke) corresponds to alphabet x, and “A” by long pressing corresponds to “alphabet y”.

The same can be applied to the selection of controls. For example, one press of an arbitrary button (eg [*] button as a control button) can express a specific object (eg, arbitrary “control a1”), and a long press of the same button can express a different specific object ( Yes, arbitrary “control b1”) can be expressed. It was said that “a2 control”, “a3 control”, ... etc. can be selected by repeatedly pressing the control button. What is important here is that after selecting “b1 control” by long pressing the control button, you can select “b2 control”, “b3 control”, “b4 control”, ... etc. by repeatedly pressing instead of long pressing. will be. Again, there is no ambiguity. This can be referred to a case in which only the representative alphabet “A” is input by long pressing in the previous example, and the single stroke is combined in selecting the remaining subsequent alphabets.

For convenience, if an object input by a combination of a specific button (eg [1] button) and “b1 control” is displayed as “B1”, it becomes as follows.

“A1 = x + {a1 control} = 1*", “A2 = x + {a2 control} = 1**", “A3 = x + {a3 control} = 1***”,. . . ,

"B1 = x + {b1 control} = 1*~", "B2 = x + {b2 control} = 1*~*", "B3 = x + {b3 control} = 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 quite natural that it is not recommended to use long press frequently. As in the case of B1, B2, B3, ..., inputting by normal pressing after one long press of the control button is called "long press and repeat press" for convenience, and this control processing method is called "long press after It is called “control treatment method by repeatedly pressing”. A1, A2, ... series means the previously suggested control processing method, and B1, B2, ... series means "control processing method by repeatedly pressing after long press". The above contents are shown in Fig. 14-1 in the form of a graph. The above is an expanded example by applying only one long press to the initial control selection, as in the repeated selection method by long pressing the representative alphabet. In addition, as shown in Fig. 14-2, various expansions (eg, C series, D series) are possible by additionally long pressing.

It goes without saying that if you apply a long press of a button ([1] button in the example) instead of the control button (eg “alphabet y”), another object can be expressed. Furthermore, the alphabet displayed on each button of the keypad (3 in Fig. 1-1) is a repeat selection method using a long press (eg, “A = 2~”, “B = 2~2”, “C = 2~22”). 4 alphabets) can be identified without ambiguity, so you can enter the modified alphabets of different groups by repeatedly pressing the control button after selecting 3 alphabets that can be selected by operating the number buttons, or by repeatedly pressing the control button. will be. That is, after inputting “A” in Fig. 1-1, by repeatedly pressing the control button, the alphabet (symbols, numbers, mother tongue, English alphabet, etc.) of a specific group (eg group 1) can be input, Another specific group (eg group 2) alphabet can be entered by “long press and repeat press”. Likewise, the alphabet of Group 3 can be entered by a combination of “B” input and repeated pressing of the control button, and the alphabet of another group, Group 4, can be input by pressing repeatedly after a long press. Fig. 1-1 In addition to the 3 alphabets displayed on the keypad buttons, a random rule (eg, "2~222") is determined, and the control button is repeatedly pressed and the control button is pressed repeatedly. It is also possible to enter the alphabet.

The control processing method by repeatedly pressing after a long press is the case of Korean (Fig. 4-5 ~ Fig. 4-8) and Japanese (Fig. 2-1, 2-2). If required for input, it will be very useful for inputting numbers that are intermittently used among sentences and inputting English alphabets (in languages other than English). In the following, application examples for each language are briefly mentioned, and can be applied to other languages not mentioned.

26.2 Korean

In the examples of Figs. 4-5 to 4-8, the modified alphabet (eg, lattice/hard consonant and dropping consonant) is input by repeatedly pressing the button to which the basic consonant belongs (eg “ㄱ=1”, “ㄲ=”). 11”, “ㅋ =111” or “ㄱ=1”, “ㅋ=11”, “ㄲ=111”) can be similarly applied. That is, when the alphabet belonging to the same button appears consecutively, the second and subsequent alphabets are input by long pressing. For example, in Fig. 4-5, if the continuous pressing of the [1] button is defined as “ㅋ”, when “ㄱ” appears in succession, it may be recognized as “ㅋ” instead of “ㄱ +ㄱ”. When entering “ㄱ”, if you press and hold it, it can be recognized as “ㄱ+ㄱ”. In other words, when entering the second syllable “ㄱ” in “country”, long press is used. Even when inputting “Kukka”, it is entered as “ㅋ = 1~1” by long pressing on the “ㅋ” input of the second syllable. This can be applied selectively (one of the two, or both at the same time) as inputting the modified alphabet by the control processing method.

This is an example of inputting a part of the alphabet that is not the representative alphabet by long pressing, and can be input by long pressing one of the lattice or hard consonants. For example, if it is defined as inputting a lattice sound by long pressing, a hard consonant (double consonant) can be input as a combination of basic consonants. Of course, as mentioned in the previous application, in the case of “Ottogi”, there is an ambiguity that becomes “o c two gi” (“c” is the final support of “oh”).

Likewise, a long press can be applied to the input of the consonant (eg, “ㅎ” assigned to the [0] button in Figs. 4-5 and 4-6) along with the vowel. In other words, it becomes something like “ㅎ = 0~”. According to the opinion of the applicant, as previously suggested in the previous application, “ㅎ = 8**” or “ㅎ = 0**” or “ㅎ = 0” (only in special cases previously presented in the previous application)” It is presumed that inputting with long press is better in terms of input efficiency than using long press. The input method of the previously suggested dropping consonant (eg “ㅎ”) and the input method by long pressing can be selectively applied.

It is said that it is possible to input a certain object using a short press after a long press. In the drawings of Figs. 4-5 to 4-13, press and hold the vowel button (the button to which the vowel element or element vowel is assigned) to When it is defined as inputting a certain object, a series of objects related to the specific button can be input by pressing a long button and then shortly pressing a certain button. The reason is, as previously explained, “. When (period) = ㅁ+ㅡ+ㅡ”, there is no Korean character starting with the vowel “ㅡ” after “some object (period in the example)” which is not a Korean consonant, so “, (comma) = ㅁ+ㅡ It is the same as what can be defined as “+ㅡ+ㅡ”. If the long press of the [*] button (the button assigned with “-”) is defined as “- (hyphen)”, it can be defined by repeatedly pressing after long pressing any other object (eg underline). . That is, it becomes “- (hyphen) = *~” and “_ (underscore) = *~*”. This also uses the nature of Korean vowels that do not appear at the beginning of the word. By using the property that the vowel element “.” does not appear at the beginning of Hangul, a short press of the button assigned “.” in the “word start state” ([0] button in the example) can be entered as “ㅎ” As indicated, the press of a vowel button in the “word start state” can be defined as the input of a specific object (eg, a special character associated with the vowel button). For example, when a button assigned with “-” ([*] button in the example) is pressed at the beginning of a word, it can be changed to “- (hyphen)”. However, when applying this, there is a disadvantage in that it is not possible to input the vowel “ㅡ” as a single character. Of course, even in this case, if a specific object other than a consonant (“- ”in the example) is recognized by the input of the button assigned with “-” and then the button assigned with “-” is pressed in succession, it is associated with another object (eg. It can be defined as input of special character “_ ”).

Next, we present a case of applying the “control processing method by repeatedly pressing after long pressing”. Applicant's representative Korean input system is introduced on the website http://www.simplecode.net along with a simulator (gore, symbol input and parallel input technology), and input of numbers and English alphabets is also mode conversion. It mentions possible without.

It is revealed that the present application was unavoidably executed because there was a request from a person in the industry to provide input technology in numbers and English without changing the mode. (For reference, the company that made such a request has been decided not to adopt the applicant's Korean input technology. It is a pity)

For input, the general frequency of use can be seen in the order of “Native language alphabet-various symbols (special characters)-numbers-English alphabet”. As shown in Fig. 4-5, there is no control button that can be used to input numbers and English. Here, it is possible to enter a number in combination with a long press of the number button and [*] button (ie, “*~ = number control”). In other words, "number 1 = 1*~". The [*] button is primarily a vowel button and is used as a control button at the same time. One press of the [*] button indicates a collection “ㅣ”, but a long press of the [*] button is an arbitrary target (“ Because it can express "number control").

There are several ways to input the English alphabet. For example, it can be defined as “A = 2#~”, “B = 2#~#”, and “C = 2#~#”. For the input of “2#~#”, it is not recognized as “A” and the vowel “ㅣ”, but can be recognized as “B” is the property that there is no syllable starting with the vowel “ㅣ” in Korean (a kind of Korean restriction). Is to use. If long press and repeat press of the [#] button are used for other purposes, the English alphabet is regarded as the successor character of the number 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 the control processing method by long press is presented. In Figs. 4-5 to 4-8, inputting “TT” and “ㅠ” by repeatedly pressing the button to which the vowel “ㅡ” is assigned (ie, “ㅡ = *”, “ㅜ = ** If defined as ”, “ㅠ = ***”), consecutive pressing of the [*] button of up to 3 strokes (ie, the maximum possible number of repetitions) is required for alphabet input. In this case, the aspirated sound control can be selected by pressing the “maximum possible number of repetitions + 1” (ie, 4 times the [*] button). “That is, “ㅋ = 1****”. In this case, it can be defined as “ㅋ = ㄱ+{Aspirated Control} = 1*~” with “Aspirated Control = *~” to alleviate the burden of pressing four times in a row. The same can be applied to hard consonants and dropping consonants, which are regarded as modified alphabets. In addition, it can be applied to all cases in which aspirated control is selected by the repeat selection method in the control processing method, and input of a modified alphabet by long pressing and input of a modified alphabet by pressing repeatedly is optional (only one of the two or Of course, it is possible with both). In this case, you can use other buttons (eg [#] button) to enter numbers.

26.3 Japanese

As in the case of Japanese in FIGS. 2-1 and 2-2, there are a large number of subsequent characters, and it may be useful when inputting the following characters by a repetitive selection method. That is, “あ = 1” or “あ = 1~”, defined as “い = 1~1”, “う = 1~11”, “え = 1~111”, and “お = 1~1111” will be. As mentioned, if the alphabet assigned to the same button appears consecutively, only the second alphabet that appears among the alphabets 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 examples of Figs. 2-1 and 2-2, it has already been shown that inputting can be performed without ambiguity with a small number of input strokes by applying the subsequent control processing method. It can be applied together with the repeat selection method by long pressing the representative alphabet. have.

* In the case of inputting a subsequent alphabet as a control processing method without applying the repeated selection method by long pressing of the representative alphabet, a case of inputting the modified alphabet using long pressing is shown. When the subsequent alphabet is input by the control processing method in Fig. 2-2, when the modified alphabet (eg “ば”, “ぱ”) of the representative alphabet (eg “は”) is input as in FIG. 2-3, the number of input strokes It can be seen that there are more or less unnatural. In this case, a long press of the corresponding button (button [6] in Fig. 2-2) can be defined as a modified alphabet of the representative alphabet (eg “ば”). It can be defined as the remaining modified alphabet "ぱ = ば + predetermined control button (eg [*] button) = 6~*".

Here, if the modified alphabet is not input by long pressing of the button assigned to the alphabet, the repeat selection method by long pressing the representative alphabet and the subsequent alphabet input by the control processing method can be applied together. The input of the modified alphabet (eg “ば”, “ぱ”) can be entered by a combination of a long press of an arbitrary control button (eg [*] button) and the representative alphabet “は”. . That is, it can be defined as “ば (arbitrary variant alphabet) = は + *~ = 6*~”, and “ぱ (any other variant character) = は + *~* = 6*~*”. Even if there are many variations of “は”, it is possible to input without ambiguity by pressing repeatedly after pressing “6*~**”, “6*~***”, ... Of course. Just as “*” and “*~” can express different objects, “**” and “*~*” can express different objects (here, arbitrary control).

What is important here is not only that you can select an arbitrary control by long pressing, but also by repeatedly pressing the button (eg control button) used for long pressing after one long press, without ambiguity, to another object (eg, arbitrary). Control).

Likewise, in the input of numbers and English alphabets, what was described in Korean can be applied. For example, it can be defined as “number 2 = 2#~”, “A = 2#~# ”, “B = 2#~##”,. . . It can be defined as

26.4 Chinese

It was shown that Chinese pinyin can be input without ambiguity (or almost without ambiguity) on the keypads of Figs. 10-1 to 10-6. However, when entering “bb = 11” to abbreviate the word composed of “b__b__” (the underscore part is the pinyin syllable composed of vowels), if a language restriction in which “bb” does not appear consecutively in Chinese Pinyin is applied, “ 11 = p”. In this case, as mentioned above, after inputting “b = 1”, the input value “1” is intentionally determined as “b” by a predetermined time delay or a specific operation (eg, pressing the [>] button) and then “b” = 1” must be entered. Again, it can be seen as a problem of ambiguity that occurs when successive inputs of the alphabet assigned to the same button. In this case, too, by applying the control processing method by long pressing the representative alphabet (the representative alphabet “b ”of the [1] button is changed to “b = 1~”). For example, “bb = 1~1~” or when the alphabet assigned to the same button appears in succession, you can apply a long press to the second and subsequent alphabet input to make “bb = 11~”.

Next, it shows entering numbers and symbols. This will be described with reference to Fig. 10-6. The input of English in Chinese is not mentioned because it is not necessary to convert it to Chinese characters after entering the English alphabet. It can be defined as “number 1 = 1*~” based on Fig. 10-6. In Fig. 10-6, one press of the [*] button is recognized as “a”, but long press (“*~”) can represent a separate object (“numeric control” in the example). In Fig. 10-6, it is preferable to apply a control processing method using a long press and repeated pressing of the [#] button to input various symbols. For example, you can associate dot(.), comma(,), colon(:), semi-colon(;), etc. to the [2] button, and “dot(.) = 2#~”, “comma(,) = 2#~#", "colon(:) = 2#~##", and "semi-colon(;) = 2#~###". The reason “2#~#” is not recognized as “dot(.) + i” but can be recognized as “comma(,)” is because Chinese Pinyin uses Chinese restrictions that do not start with “i”. Likewise, “2#~##” can be recognized as “colon(:)” rather than as “dot(.)+i+i” or “comma(,)+i”. If you want to input “dot(.)+i”, as mentioned, after entering “2#~”, after a predetermined time elapses after “dot(.)” is confirmed or a specific operation (eg [>]) Press the button) to confirm “dot (.)” and enter “# = i”.

In Fig. 10-6, the reason why the [*] button is not used to input the symbol(s) of a specific group is rare, but there are pinyin starting with “a”, “e”, “o”, etc. This is because ambiguity may arise when using “repeated press”. In the case of numbers, there is only one, so you only need to combine them once by long pressing the [*] button. 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. 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 can be similarly applied not only to the keypads of FIGS. 10-1 to 10-6 but also to other keypads.

26.5 Romanized languages

In European languages using Roman characters, there are many variations of the basic alphabet with subscripts. By applying various long presses described above, it can be applied to the input of modified alphabets and special characters.

27. A device for inputting Korean syllables (= combined letters) by unbroken drag on the screen keyboard and its method

27.1 Existing input method using drag technique

Recently, with the advent of converged 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 "Moaki" as an input device. The representative concept is "Up/Down/Up" after touching (or clicking with a mouse) a specific consonant (eg "ㅇ") on the LCD keyboard as shown in Fig. 15-1. When dragging to the left/right side, “oh/right/uh/ah” is entered respectively. When only one consonant is touched and released (ie, without dragging), the [ㅡ] button, [ㆍ] button, and [ㅣ] button for entering vowels are popped up around the touched consonant as shown in Figure 15-2. Additional vowels can be entered. Here, “drag” is also referred to as “gesture” and means that the touch or click is dragged without releasing the touch or click. The time point at which the drag ends is the moment when the pen touch or mouse click is released after the dragging. The concept of drag can be easily understood by using a program that supports mouse gestures once, and the term "drag" is used in the present invention.

Moakey is gaining some popularity despite the limitation that it only works on the touch screen due to the characteristics that other input devices have not provided so far. There are a few disadvantages, including the inability to input emoticons (eg "ㅜㅜ", "ㅠㅠ", "ㅡ.ㅡ", ...) expressing emotions with Korean vowels, and 19 consonant buttons on the LCD. In the case of a release PDA, about half of the screen is required as a keyboard, and the same input technology cannot be used for button input.

In addition, there is a content in which two buttons that start and end drag on a specific keyboard are input by the drag. For example, if you start a pen touch (or mouse click) from the [a] button and drag it to the [ㅣ] button and release it, "ki" is input. This does not necessarily apply to "Initial + Neutral", but applies in all cases. However, in this case, it is always applied only to the two buttons of dot (start button) versus dot (end button). Implementing is also very simple, so you can treat the "start drag button" where the drag is started and the "end drag button" after the drag are pressed. Detecting the start of dragging is when the pen touch (or mouse click) starts and the first touched position (coordinate) moves in the state where the pen does not drop (or the mouse click does not fall). This is the same as detecting a "mouse gesture" that is widely used on a PC, and since it is a technology widely known to the extent that many individual users are distributing their own mouse gesture programs, the present invention refers to the above procedure and process in detail. I never do that.

27.2 Composition of syllable input technology by continuous drag suggested by the present invention

In the present invention, a technique for inputting one Korean syllable (jamo combined character) by one continuous drag is proposed. It was directly confirmed that this technology was not presented in the "Moaki" product.

The content of the present invention can be applied to all cases of inputting syllables by dragging consonants and vowel buttons on a keyboard (keypad, keyboard, and all other modified forms) displayed on a liquid crystal display. For convenience, a mobile phone keyboard is used as an example, and in particular, the description is based on the keyboard and input method suggested by the applicant in the previous application. All types of Korean keyboards consist of a consonant button with a consonant and a vowel button with a vowel. Representatively, 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 so well known that it is not described. However, in all input methods, consonants placed on each consonant button (or at least the first consonant in the case where multiple consonants are placed) are entered by pressing the button once, and vowels are also entered by pressing the vowel button on which the vowel is placed. 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 in 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 together. Even if you don't do that, it doesn't matter to apply the input method, but anyone does it for the user's "button location identification". This means, for example, that no one mixes consonant buttons and vowel buttons. The same is true of the Korean keyboard layout. One of the keyboard layouts suggested by the applicant (explained in Chapter 4 of the applicant's prior application and the 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 Figs. a) or as shown in Fig. 15-5(b), similarly, consonant buttons are grouped together and vowel buttons are grouped together. 15-5(a) and 15-5(b) are mutually compatible keypads. Interchangeability means that the input method described with reference to Figs. 15-5(a) can be applied to Figs. 15-5(b), and conversely, the input method suggested based on Figs. 15-5(b) is shown in the drawing. It means that it can also be applied in 15-5(a). In the existing keypad Korean input method and the Korean input method suggested by the applicant in FIGS. 15-3 and 15-4, the number of vowel buttons is relatively smaller than the number of consonant buttons.

In Korean syllables (jamo-combined letters), about half of the letters consist of "initial + neutral", and about half of the letters consisting of "initial + neutral + final". This means that about half of the letters consisting of "consonants + vowels" and about half of the letters consisting 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 shows the same keyboard (keypad). In Figure 15-6, unless there is a special case below, it is assumed that there are only 12 character buttons ([a] ~ [ㅈ] 9 consonant buttons, [-], [ㅏ], [ㅣ] 3 vowel buttons). , The description will be made on the basis of FIGS. 15-5(a) (that is, based on the applicant's Korean input method suggested in FIGS. 15-5(a) and related descriptions). According to the input method suggested by the applicant in "Applicant's Korean Input Method" based on Figure 15-6, when entering "Go", press [ㄱ]+[ㅏ]+[ㅡ]. For programming, the moment a specific button (eg [ㄱ] button) is pressed, the character (eg “ㄱ”) can be displayed on the screen, or the moment a specific button is pressed and released, the character is displayed on the screen. May be. In most screen input devices (e.g., screen keyboard), the moment the button on the screen is pressed and released (i.e., the moment when the button is pressed and released rather than the moment when the pen is pressed, or the moment when the mouse is clicked and released rather than the moment when the mouse is clicked) is implemented so that characters are entered ( Yes, there is a screen keyboard built into MS Windows), and there is no technical difference. In the case of mobile phones, depending on the manufacturer, some products display text as soon as the button is pressed, while some products do not display text when the button is pressed, but the text is displayed as soon as the button is released.

Hereinafter, the explanation is mainly based on the applicant's Korean input method suggested 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 disclosed as a programmed character input device product through the website http://www.simplecode.net after the patent application of the present invention is filed. to be. 15-6 is a UI (User Interface) applied to the text input device to be disclosed.

Based on Fig. 15-6, if the user starts with the [a] button and then drags to the [-] button through the [ㅏ] button to write the letter "high", the button that goes through as in Fig. 15-7 (ie , The button being dragged) will be multiple buttons. Recognizing the dragged buttons by the system is that the position of the pen or mouse cursor changes from the moment the button on the screen is touched (or mouse clicked) to the moment before the button is released at intervals of a predetermined short time (eg 1/100 second). Just check which button it is on.

In order to facilitate the description of the present invention, as shown in Fig. 15-7, "drag" is referred to as "drag" or "drag operation", and the button passed by the drag operation is referred to as "drag button". . In Fig. 15-7, the "drag start button" where the drag operation started is the [a] button, the "drag end button" after the drag operation is finished is the [ㅡ] button, and the "drag button" is the [a] button, [ B] button, [ㅁ] button, [ㅇ] button, [ㅈ] button, [ㅏ] button, [ㅡ] button. When indicating the button(s) dragged by the drag operation in Fig. 15-7, it will be indicated as [ㄱ → ㄴ → ㅁ → ㅇ → ㅈ → ㅏ → ㅡ]. For convenience of explanation, when displaying the drag as shown in Fig. 15-7, the drag start button is marked with a circle (●), and the end point of the drag is indicated with an arrowhead.

It is easy to input adjacent buttons by dragging. However, in the case of a large number of dragged buttons, the problem of determining which button is the button the user intends to input is a worrisome problem. In Fig. 15-6, if you start dragging in [ㄱ] to input "that", it goes to the [-] button after going 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.

To go from a group of consonant buttons ([a] button to [ㅈ] button) to a group of relatively few consonant buttons, it goes through a number of consonant buttons. It is determined that the user intended was to press all the dragged consonant buttons. I never do that. In other words, if starting from the consonant button and dragging to the vowel button in Fig. 15-7, it is determined that the first consonant button (drag start button) where the drag is started is at least the button intended to be input by the user, and then the consonant buttons ( In the example, [b] button, [ㅁ] button, [ㅇ] button, [ㅈ] button) do not form a valid initial voice together with the drag start button, so they are considered as buttons that the user did not attempt to input and are ignored. This is due to the property that consonants do not appear consecutively at the beginning of Korean syllables (jamo-combined characters). Next, the first vowel button ([ㅏ] button in the example) is regarded as the vowel button the user intended to input, and next, it can be combined with the [ㅏ] button already considered as a valid button to form "ㅗ". The [ㅡ] button that is present is also considered a valid button. Among the dragged buttons [ㄱ → ㄴ → ㅁ → ㅇ → ㅈ → ㅏ → ㅡ], if you mark only the buttons recognized by the system as valid buttons excluding the buttons ignored by the system, it becomes [ㄱ → ㅏ → ㅡ]. Depending on the user, as shown in Fig. 15-8(a), it may be dragged as [ㄱ → ㄴ → ㅁ → ㅂ → ㅈ → ㅏ → ㅡ]. In this case, too, "b → ㅁ → ㅂ → ㅈ" is invalidated, so the button recognized as valid is the same as [ㄱ → ㅏ → ㅡ]. Even if the user drags as shown in Fig. 15-8(b), the result is the same.

If the user drags to the [b] button without ending the above drag operation (ie, without releasing the pen touch or mouse click from the [ㅡ] button, release the pen touch from the [b] button or click the mouse). Release), also goes through a number of consonant buttons. For example, as shown in Figure 15-9, the total dragged button becomes [ㄱ → ㄴ → ㅁ → ㅇ → ㅈ → ㅏ → ㅡ → ㅇ → ㅁ → ㄴ]. Even in this case, a number of consonant buttons that go through the middle (in the example, the [b] button, [ㅁ] button, [ㅇ] button, [ㅈ] button in the initial part, and the [ㅇ] button, [ㅁ] in the ending part) All buttons) are ignored rather than judged as what the user wanted to input (i.e., as valid buttons). This is because Korean syllables consist of "consonant + vowel + consonant", so it is reasonable to judge that you wanted to input only the consonant ("b" in the example) where the final grag ends. If only valid buttons are shown among the dragged buttons, it is [ㄱ → ㅏ → ㅡ → ㄴ], and the syllable (character combined letter) recognized (or recognized) as a result of the drag becomes "gon".

As shown in the example above, the first drag start button and the last drag end button are always recognized by the system as valid buttons, and only the buttons required to form a Korean syllable among the buttons passed in the middle according to a predetermined input method are recognized as valid buttons. The rest of the dragged buttons are ignored, so that inputting Korean syllables by one drag is the core of the present invention.

Next, it is shown that the case of inputting by pressing the same vowel button twice can be input by dragging. If you want to input "Yu", drag it to [ㅇ → ㅡ → ㅏ] and input "Right", then click the [ㅏ] button to input "Yes". Two other ways are to drag it to [ㅇ → ㅡ → ㅏ] and drag it to the [ㅡ] button, which is a collection that cannot be combined with the vowel "ㅜ" without ending the drag, and then drag it again to the [ㅏ] button. . When the dragged button is marked, it becomes [ㅇ → ㅡ → ㅏ → ㅡ → ㅏ]. Likewise, it ignores the [-] button, which is a vowel button that cannot be combined after "TT", and only recognizes the next [ㅏ] button as a valid button. The disadvantage of this method is that there are cases where the input of only vowels is currently used like a kind of emoticon (eg "ㅜㅜ"), but this case cannot be expressed. For example, if the above content is not applied, in order to input "ㅜㅜ", you can enter "TT" at once by dragging to [ㅡ → ㅏ → ㅡ → ㅏ]. In the product (http://www.simplecode.net) that will be implemented and distributed as a program, it was decided to input "ㅜㅜ" as [ㅡ → ㅏ → ㅡ → ㅏ]. Another way is to drag from the [ㅏ] button to an arbitrary consonant button ([ㅈ] button in the example) and then drag it back to the [ㅏ] button without stopping the drag after [ㅇ → ㅡ → ㅏ]. That is, if you drag to [ㅇ → ㅡ → ㅏ → ㅈ → ㅏ], you can enter "Yu". In order to enter the finality, the drag must be ended at the consonant button ([ㅈ] button in the example), but the drag was continued and dragged back to the vowel button (the [ㅏ] button in the example). It is to be processed. In other words, the [ㅈ] button that has not been validated by the final input only serves to inform that the dragged [ㅏ] button has been input "one more time". Of course, it is natural to touch (or click) the [ㅏ] button once after ending the drag to [ㅇ → ㅡ → ㅏ] and inputting "right". If [ㅇ → ㅡ → ㅏ → ㅈ → ㅏ → ㅈ → ㅂ → ㅁ] is dragged, the system recognizes and processes it as "Yum" (Fig. 15-10, [ㅈ] button and [ㅂ] button in Fig. 15-10. Is ignored)

The above is possible even when only the "initial voice" is input, the "initial voice+neutral" is input, or the additional drag is started while the "initial voice+neutral+final voice" is input. Some examples of input are as follows based on Figs. 15-5(a) and 15-6. For convenience, it is revealed that the button that is invalidated (ignored) among the dragged buttons may not be marked. When inputting "Wing", dragging to [ㅇ → ㅅ → ㅡ → ㅏ → ㅣ → ㅈ → ㅇ] allows you to input "wing" in one drag motion. The [ㅅ] button after the [ㅇ] button is ignored because it does not make a valid initial voice, and the [ㅈ] button is also ignored because "ㅇ" is the final voice. This is because if "ㅅ" was the initial voice desired by the user, the drag would have started at "ㅅ", and if "ㅈ" was the final voice, the drag would have ended at "ㅈ". In Figure 15-6, it is possible to drag from the [ㅇ] button to [ㅇ → ㅡ → ...] without going through the [ㅅ] button, but this is an example presented to show the case where the [ㅅ] button is ignored. If dragged to [ㅇ → ㅅ → ㅡ → ㅏ → ㅣ → ㅈ → ㅇ → ㅈ] as in Fig. 15-11, "top + ㅈ" ('top' +'ㅈ' support) will be input. Even if a number of other consonant buttons are dragged after the [ㅇ] button (eg [ㅇ → ㅅ → ㄹ → ㅁ → ㅇ → ㅡ →....]), only the first [ㅇ] button is considered a valid initial vowel and is considered a vowel. Other consonant buttons before the [ㅡ] button are ignored. Likewise, even if dragged like [...→ ㅈ → ㅇ → ㅈ], only the last [ㅈ] button is regarded as a valid finality and the remaining consonant buttons are ignored. In other words, in the initial voice, only the buttons that form the initial voice with a predetermined input method, including the drag start button, were regarded as valid buttons. will be.

As another input example, in order to enter "Vo + ㄺ" ('ㄺ' to'V'), drag to [ㅂ → (ㅁ → ㅇ) → ㅡ → ㅏ] and enter "Part", then click [ㅏ → Drag to ㅣ] and input "Beep", then drag to [ㅣ → (ㅈ → ㅇ → ㅁ) → ㄹ] and input "Bow+ㄹ" ('ㄹ' to'B') and click the [ㄱ] button Just do it. Refer to Figure 15-12(a). Those marked in parentheses such as "(ㅁ → ㅇ)" and "(ㅈ → ㅇ → ㅁ)" are buttons that are ignored (invalid) and may not be indicated below for convenience. Another thing is [ㅂ → ㅡ → ㅏ → ㅈ → ㅏ → ㅣ → ㅈ → ㅈ] after inputting "boo" with [ㄹ → ㄱ] and inputting "boo+ㄺ" ('ㄺ' in'boo') do. Refer to Figure 15-12(b). The two [ㅈ] buttons entered when entering "V" are each entered to distinguish the continuous input of the [ㅏ] button and the [ㅣ] button. When the dragged button starts at the consonant button and goes through the consonant button to the vowel button, the middle consonant button is invalidated, but when the drag starts at 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 "ㄺ" is input by dragging [ㄹ → ㄱ]. Of course, press the [ㄱ] button to press the [ㄱ] button after inputting "Vo + ㄹ" at a time with [ㅂ → ㅡ → ㅏ → ㅈ → ㅏ → ㅣ → ㅈ → ㅣ → ㄹ] You can also enter "('ㄺ' in'V'). All of the above has been embodied and proven as a program, and all will be disclosed as products through http://www.simplecode.net after the application of the present invention.

The following is planned for implementation (programming). Further, based on Fig. 15-6, if it is defined as inputting "ㅋ" by dragging to [ㄱ → ㄴ], dragging with [ㄱ → ㄴ → ㅁ → ㅇ → ㅡ], dragging "ㄱ → ㄴ" The initial "ㅋ" is treated as input (that is, the [ㄱ] button and the [ㄴ] button forming the initial voice are considered valid inputs), and the middle [ㅁ] button and [ㅇ] button are ignored. It can recognize and process the input of "K". If dragging from the [ㄱ] button to the left outside the button is defined as "ㅋ" input, the dragged to [ㄱ → 外 → ㅡ] as in Figure 15-13(a) is entered as "Big" Can be treated as Also, if it is defined as inputting "ㄲ" by dragging to [ㄱ → 文/Num], dragging to [ㄱ → 文/Num → ㄱ → ㄹ → ㅅ → ㅡ] as in drawing 15-13(b), You have entered "off" so the system can recognize and process it.

Some more examples based on other character input techniques are as follows. Based on drawing 15-4 of the character input device adopted by LG Electronics, start dragging from the [a] button, go through the other consonant buttons, pass the [overwrite] button, then the [ㅗ] button, the [ㅏ] button, and the [ㅣ] When the drag is finished at the [b] button via the button, "Quick +ㄱ" ('A' to'Quick' support) is input by continuous drag. The drawing illustrating the drag process is Fig. 15-14, and when the dragged button is indicated, [ㄱ → ㄹ → ㅅ → overwrite → ㅅ → ㅇ → ㅁ → ㅗ → ㅏ → 外 → ㅣ → ㅇ → ㅁ → ㄴ→ ㄱ ] Becomes. As shown in Fig. 15-4, if the button is separated from the button, you can go directly to the button at the diagonal position, but assuming there is no gap between the buttons, it is assumed that the button is dragged past the vertical/horizontal direction. Fig. 15 Expressed in -14. This is because the screen keyboard is usually not spaced apart from the buttons on the liquid crystal. In the process of dragging to input "ㅋ", the [ㄹ] button and the [ㅅ] button are passed, but since two consonants do not appear in succession in the Korean syllable, the [ㄹ] button and the [ㅅ] button can be ignored. There is. Likewise, to drag from the [ㅣ] button to the [a] button, you go through the [ㅇ] button, the [ㅁ] button, and the [ㄴ] button, but only the [a] button, which is the consonant button after the vowel is dragged, is valid. (In other words, Ignore [ㅇ] button, [ㅁ] button, [b] button) It can be processed. For one more example, similarly, starting from the [a] button, passing through the [ㅗ] button, and ending the drag at the [ㅁ] button, it can be treated as inputting "bear". However, when the dragged button becomes [ㄱ → ㄴ → ㅁ → ㅗ → ㅁ → ㅇ → ㅅ → overwrite → ㅅ → ㄹ → ㅁ], the dragged button after the vowel "ㅗ" It can be processed as inputting "Kyo+ㅁ" ('ㅁ' support for'Kyo') with the [Write] button. If one of the dragged "ㅁ", "ㅇ", and "ㅅ" is entered after the vowel "ㅗ", click the [ㅗ] button, then the [ㅁ] button, the [ㅇ] button or the [ㅅ] button. Should have ended. Start the drag operation from the [ㅅ] button on the keyboard of Samsung Electronics, go through the [ㅣ] button [ㆍ] button, and end the drag operation at the [ㅇ] button, then "Up" is entered. (Refer to Fig. 15-16)

Next, I will give an example based on the case that the Hangul 2 Beolsik keyboard used in the current PC is on the LCD. For convenience, it is assumed that there are only consonant buttons and vowel buttons marked with Korean alphabets in Figs. 15-17, and the position of the key is changed for efficiency. In Figure 15-17, if the dragged button is [ㄱ → ㅅ → ㅎ → ㅗ → ㅓ → ㅏ → ㅣ → ㅏ → ㅓ → ㅗ → ㅎ → ㄹ → ㅇ], the drag start button [ㄱ] You can ignore the [ㅅ] button and the [ㅎ] button after the] button. Next, the [ㅗ] button, which is the first dragged bar button, is considered a valid button, so the [ㅓ] button and the [ㅏ] button that cannot be combined with the [ㅗ] button can also be ignored, and can be combined with the [ㅗ] button. The [ㅣ] button can be regarded as a valid button. Next, the [ㅏ] button, [ㅓ] button, and [ㅗ] button that cannot be combined with "ㅚ" are also ignored, and the [ㅎ] button and [ㄹ] button among the last three consonant buttons are also ignored, and the drag is finished. Only the [ㅇ] button can be regarded as a valid button. The result is entered as "awesome". The above result is the result based on the input method in the 2 Beolsik keyboard.

The point at which the result recognized (or recognized) by the system is output to the user (displayed on the liquid crystal or transmitted by voice) may be output as soon as the system recognizes it as a valid button among the buttons dragged in the middle of the drag. It can also be output when all of are finished. There is no significant difference between the two, but rather, it is a bit confusing that the text is printed in the middle of dragging. One unit recognized by the user is a completed consonant, vowel, or syllable (jamo combination letter).Since one syllable is input by one drag, it is recognized/recognized by the system (or It doesn't look bad to output one syllable (input to the system).

In the above procedure, it was shown to input Korean syllables with a single drag. In particular, under the illustrated applicant's input method, most Korean syllables can be entered with a single drag. It is obvious that various modifications are possible under the content described in the present invention. For example, it can be applied even when a vowel button pops up after a button is touched (or clicked) as in the Moakey keyboard of Fig. 15-2. Of course, Moaki does not support drag input of syllable units at all. In addition, the Moa key input technology can be applied only to the touch screen method due to the nature of the technology, but with the technology presented in the present invention, the same Korean character input technology can be used by a button press method and a pen touch or drag method on the touch screen. There is an advantage.

The drag technique described above can be applied to both a case where a pen is touched on a keyboard on a touch screen and a mouse is clicked on a keyboard on a screen. Since the touch screen and screen keyboard technologies are already common technologies, the hardware structure is not described. Even if a hardware configuration technology that is a little more precise than the current touch screen hardware configuration comes out, it is quite obvious that there is no problem in applying the spirit of the present invention, and it is not at all to describe the device configuration for a touch screen or screen keyboard that has already been generalized. Because it has no meaning.

The above contents are summarized in the form of claims and are as follows.

In a keyboard having a plurality of buttons on the screen (liquid crystal), based on a predetermined input method, Korean characters (consonants, vowels, alphabetic characters, words, or words) by dragging in a pen-touch (or mouse click) state. In the method of entering the verse),

(a) detecting the start of a drag operation and recognizing the button (drag start button) where the drag has started

(b) Recognizing buttons dragged by the drag operation, and recognizing only consonant buttons capable of forming Korean initials, including the drag start button among the dragged buttons, as valid inputs by a predetermined input method. step

Korean character input method by continuous drag on a liquid crystal (screen) keyboard, characterized in that characters are input by using

In addition to, it may include:

(c) recognizing that the vowel button (or vowel buttons) is dragged by the vowel button by the drag operation

(d) recognizing a vowel formed by the dragged vowel button by the predetermined input method, including the vowel button first dragged

Korean character input method by continuous drag on a screen (liquid crystal) keyboard, characterized in that characters are input by using

Or, as shown in the example of dragging on the screen 2 beolsik keyboard,

(c) recognizing that a vowel button (or vowel buttons) is dragged by the drag operation

(d) recognizing only vowel buttons capable of forming Korean neutrality among the dragged vowel buttons, including the first dragged vowel button, as a valid vowel button.

Korean character input method by continuous drag on a screen (liquid crystal) keyboard, characterized in that characters are input by using

In addition to

(e) recognizing that the drag operation is finished

(f) processing the dragged consonant button as a valid input

Korean character input method by continuous drag on a screen (liquid crystal) keyboard, characterized in that characters are input by using

It may include.

In addition, the main idea of the present invention is that among the dragged button(s), the drag start button and the drag end button are always determined to be valid buttons, and only buttons that can be effectively combined with the drag start button according to a predetermined input method are effective. It can be seen that the essential content is to determine as a button and to determine only a button that can be effectively combined with the drag end button as a valid button. Of course, a button determined to be a valid button is processed by the predetermined letter input method, so that the system recognizes the input letter and can output it to the user. In addition, among the dragged buttons excluding the drag start button and the drag end button (“the dragged button except for the start and end”), the buttons that cannot form a Korean syllable (jamo combination character) are invalidated (ignored) and form a Korean syllable. It includes determining and processing only possible buttons as valid buttons.

therefore,

In a keyboard having a plurality of buttons on the screen (liquid crystal), based on a predetermined input method, Korean characters (consonants, vowels, alphabetic characters, words, or words) by dragging in a pen-touch (or mouse click) state. In the method of entering the verse),

(a) Recognizing the button(s) dragged by the drag operation,

(b) among the dragged buttons, the drag start button and the drag end button are determined 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 drag on a liquid crystal (screen) keyboard comprising a

As shown in Fig. 15-1 to Fig. 15-17, except for the button that is invalidated (ignored) among the dragged buttons, it is shown that valid buttons are determined.

Determining a valid button in (c) above is based on the Korean alphabetic combination rules for forming Korean syllables.

Korean character input method by continuous drag on a liquid crystal (screen) keyboard, characterized in that

It may include. Of course, Korean characters recognized as a result can be output (displayed on the screen or output by voice...).

28. A device for inputting Korean syllables (= combined letters) by unbroken drag on the screen keyboard and its method Part 2

In the present invention, an additional technique is proposed in the extension of “A device and method for inputting Korean syllables (= combined characters) by unbroken drag on a screen keyboard” introduced in Chapter 27 above.

28.1 The prototype of the input method using the drag technique

A very long time ago, a web browser called "Opera (http://www.opera.com)" provided a function called "mouse gestures". Now, through various utility programs, it has become a common technology used by many people in Internet Explorer (IE), which is basically installed in MS Windows. Fig. 16-1(a) and Fig. 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 indicated by “left arrow button” in any web browser, and the button to move to “next page” is indicated by “right arrow button”.

Next, drawing 16-2(a) is the initial screen of the Pocket PC 2000 emulator included in Embeded Visual C++ 3.0 distributed by Microsoft for free, and drawing 16-2(b) is when the word processor is executed in the emulator. , This is the screen keyboard screen that appears. Fig. 16-2(c) is an option setting screen of the screen keyboard input device. As shown in Fig. 16-2(c), input by dragging in four directions was already provided at this time. If the contents of Fig. 16-2(c) are summarized, it is the same as Fig. 16-3. If you click (or touch) the button, the alphabet “X”, which is the basic character marked on the button, is entered. Combined characters are entered, and dragging to the right enters a blank space, dragging downwards to enter the enter function, and dragging to the left enters the backspace function.

Fig. 16-4 shows an application example in Japanese. When you touch it once, the basic character “あ” is entered, and the remaining characters of the “ah” line in the Japanese 50 phonemes are “い”, “う”, “え”, and “お” respectively. Is entered. There are many other types of drag input technology.

28.2 Technical problem to be solved in the present invention

Samsung Electronics' “Moaki” input device, which is currently the most used drag input technology, supports drag input for four vowels: “ㅗ”, “ㅏ”, “TT”, and “ㅓ”. Since the 4 vowels “ㅗ”, “ㅏ”, “ㅜ”, and “ㅓ” have a frequency of 49.16% in Korean, it can mean that about half of the vowels can be entered by dragging. .

Both the vowels “ㅡ” and “ㅣ” together have a frequency of use of about 28%. However, in the conventional method, the vowels “ㅡ” and “ㅣ” cannot be entered by dragging, so the input method is consistent and uniform. This is not being maintained. In addition, it is impossible to input a single Korean syllable (jamo combination character) by one continuous drag suggested by the applicant in Chapter 27 (referred to as the "Invention of Drag 1" for convenience).

In Korean Hangul, a single letter (syllable) in which consonants and vowels are combined can be viewed as a basic unit of thought. In other words, in our thinking system, rather than thinking and recognizing as per phonemes (consonants or vowels), we recognize them as a single letter unit that combines consonants and vowels. It is intended to be presented in Chapter 27, "Part 1 Invention" and the present invention, to input a syllable (including the ending support), which is one such unit of thought, with a single drag by a consistent method.

6 vowels that add the 4 vowels of “ㅗ”, “ㅏ”, “ㅜ”, and “ㅓ” above (49.16% frequency of use) and 2 vowels of “ㅡ” and “ㅣ” (about 28% frequency) Since has a frequency of use of about 77.23%, the 6 vowels can input more than about 3/2 of the vowels in a consistent manner. Also, the 4 vowels “ㅛ”, “ㅑ”, “ㅠ”, and “ㅕ” have a frequency of use of about 6.98%. 2 vowels of “ㅡ” and “ㅣ” (use frequency about 28%), 4 vowels of “ㅗ”, “ㅏ”, “ㅜ”, and “ㅓ” (use frequency 49.16%), and “ㅛ”, The frequency of use of 10 vowels combined with all four vowels of “ㅑ”, “ㅠ”, and “ㅕ” (frequency 6.98%) is about 84.22%, so most of the Korean vowels can be entered by a consistent drag input method. There will be. In addition, if the applicant combines the techniques presented in Part 1, all vowels can be entered by one consistent method. In addition, by grafting the technology presented in the first part, the applicant can input it with one continuous drag with one continuous drag including the final support.

Drag Part 1 The invention is scheduled to be published as a product (PDA product) sooner or later, so that 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 Composition of syllable input technology by continuous drag suggested by the present invention

First, it shows that the technology in the first part of the invention can be applied to the existing technology (typically a Moa key input device).

The main event in the Moa key of Figs. 15-1 and 15-2 is to input “ㅗ” by dragging the upper side, input “ㅏ” by dragging the right side, input “TT” by dragging the lower side, and It is to input “ㅓ” by dragging. That is, when dragging from the [a] button to the right as in Fig. 16-5(b), “A” is entered, and when dragging downward from the [a] button as in Fig. 16-5(b), “gu” Is entered.

However, as shown in Fig. 16-6(a), if the drag is short to the right and then drags to the lower for a longer time, the result is not “A”, but “A” is input. In addition, as shown in Fig. 16-6(b), if dragged downward and then dragged to the right longer (than the length of the lower drag), the result is “A”. As shown in Fig. 16-6(c), if you draw in a diagonal direction of about 45 degrees, the result may be "A" or "A" in some cases. Here, the implementation method of Moakey is 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, and the X-axis movement distance dX is the Y-axis movement. If it is greater than the distance 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 (lower drag in this case). It was confirmed that this works in the same way in the "Moaki 2.0" version applied to the latest phones such as Samsung Electronics' Omnia.

However, in order to apply the invention of Part 1, once the drag in the right direction proceeds, it is newly defined as recognizing the vowel “ㅏ”. If dragged to [ㄱ → ㅅ → ㅎ] as in Fig. 16-6(a), “ㅏ” is recognized as being dragged from [ㄱ] to the right of [ㅅ] (the result is “a” and “ “A”) and “ㅎ” is recognized as the last button, so the result is “red”. In drawing 16-6(c), it seems ambiguous whether it was dragged to [ㄱ → ㅅ → ㅎ] or [ㄱ → ㄹ → ㅎ], but “red” is recognized if dragged with [ㄱ → ㅅ → ㅎ] If it is dragged from [ㄱ → ㄹ → ㅎ], “ㅜ” is recognized as dragged downward from [ㄱ] to [ㄹ] (the result is “gu”), and the last button of the drag is the [ㅎ] button Therefore, the result is recognized as “gu+ㅎ ('ha' support under'gu')”. Here, for the convenience of recognizing vowels by the drag direction, the vowels are marked in curly brackets and marked as {x}. That is, [ㄱ → ㅅ → ㅎ] can be written as [ㄱ → {ㅏ} → ㅎ], and [ㄱ → ㄹ → ㅎ] can be written as [ㄱ → {ㅜ} → ㅎ] .

If you want to enter “each” you can do something like this: In Fig. 16-7(a), it was dragged from [ㄱ → ㅅ → ㄱ], but the dragged right from the [a] button to the [ㅅ] button is recognized as “ㅏ”, so [ㄱ → {ㅏ} → ㄱ] The result can be perceived as "each". However, in Moakey 2.0 version, dragging to the right and returning to its original position is handled as recognizing “another vowel”. For example, as shown in Fig. 16-7(a), the drag operation returning to the drag start button after the right drag is processed as a collection "ㅐ". If this is applied, the drag in Figs. 16-7(a) will be recognized as “dog”. In this case, a different type of drag operation will be required to input “each”. For example, if you drag to [ㄱ → ㅅ → ㅎ → ㅍ → ㅊ → ㄹ → ㄱ] = [ㄱ → {ㅏ} → ㅎ → ㅍ → ㅊ → ㄹ → ㄱ] as in Fig. 16-7(b), , “A” is recognized by right dragging from the [ㄱ] button to the [ㅅ] button, and “ㅍ”, “ㅊ” and “ㄹ” are invalidated except for the last button of the drag “ㄱ”, so the result is “Angle” is recognized. When dragging to [ㄱ → ㅅ → ㅎ → ㄹ → ㄱ] = [ㄱ → {ㅏ} → ㅎ → ㅍ → ㅊ → ㄹ → ㄱ], the result is also recognized as “angle”. Even if it is dragged from the [a] button to the [ㅅ] button as shown in Fig. 16-7(c) and then dragged to a complicated path, the final recognized result is the same.

In Moaki 2.0 version, when dragging starts from the [a] button, drags to the right, and returns to the [a] button, the vowel “ㅐ” is recognized (the result is “dog”). If you return to the drag start button after left dragging, “ㅔ” is recognized, if you return to the drag start button after dragging the upper side, “ㅚ” is recognized, and if you return to the drag start button after dragging the lower side, “ㅟ” is recognized. . However, when actually used, there is the same phenomenon as in Fig. 16-6(*). (The “*” symbol in Fig. 16-6(*) means all) That is, as in Fig. 16-6(c), if you drag in the direction of about 45 degrees and return to the drag start button, in some cases, the "" is recognized (ie, treated as a right drag), and in some cases "ㅟ" is recognized (ie, treated as a lower drag). This is the logic as pointed out in Figure 16-6, which compares the maximum travel distance in the X-axis direction and the maximum travel distance in the Y-axis direction, and it can be seen that the direction of drag (right drag or lower drag in this case) is processed. have. However, for convenience of explanation, the right drag is described as being dragged to the adjacent right button and then back to the original button. The rest of the case (up/down/left drag) is the same.

To enter “gang”, drag it to [ㄱ → ㅅ → ㄱ → ㄷ → ㅇ] as shown in Fig. 16-8(a). Starting from the [ㄱ] button, dragging to the [ㅅ] button on the right and returning to the [ㄱ] button is defined as “ㅐ”, so it can be described as [ㄱ → {ㅐ} → ㄷ → ㅇ], The consonant “ㅇ”, which is the last button to drag after “dog”, is a valid button, so “c” is invalid. The result is recognized as a “gang”. If you want to enter “Guest”, you can drag it to [ㄱ → ㅅ → ㄱ → ㄹ → ㄱ] as in Figure 16-8(b). [ㄱ → ㅅ → ㄱ → ㄹ → ㄱ] can be described as [ㄱ → {ㅐ} → ㄹ → ㄱ], and after the “dog” is recognized, only the last button of drag “a” is recognized as a valid button, Because “ㄹ” becomes invalid. After [ㄱ → ㅅ → ㄱ] is recognized as [ㄱ → {ㅐ}], dragging down to [ㄱ → ㄹ → ㄱ] and returning to the original button is not recognized as “ㅟ”. [ㄱ → ㅅ → ㄱ →. . . → It can be treated the same in all cases dragged to a]. “. . .” Means dragged through a number of other buttons (including text buttons, function buttons, or the outside of the keyboard) as in 16-8(c).

As mentioned above, the contents of the first invention (the last button of the dragged consonant button among the dragged consonant buttons after recognition of “initial + neutral” is recognized as a valid button and the remaining consonant buttons are invalidated) in Moakey, a representative drag character input device. In order to do this, a case was shown where the input logic was partially modified and applied, and the final support can be input by dragging. However, even in this case, 8 vowels can be entered by dragging, but all Korean vowels cannot be consistently entered by dragging. Next, in the present invention, all vowels are consistently input by dragging, and a description will be given of contents that can be input even to the final support. As mentioned in Part 1 Invention, the following can be applied equally to all other text input devices (eg, text input devices adopted by Samsung Electronics, text input devices adopted from LG Electronics), but for convenience, visit http://www.simplecode.net The description will be based on the introduced applicant's character input technology.

In Chapter 27, Part 1 Invention, it is mentioned that Figs. 15-5(a) and 15-5(b) are compatible keyboards. In Figure 15-6, which is the “character input device for pc/one-handed handicapped” introduced on the http://www.simplecode.net site, there is an option to set whether to display the [ㅏ] button as “ㆍ”. It is provided, and the default setting when installing the program is to display the [ㅏ] button as "ㆍ" (ie, Fig. 15-5(b)). Figures 16-9(a) and 16-9(b) are also screens of programs that will be released as pda products in the near future. Fig. 16-9(b) is the default setting, but Fig. 16-9(a) describes the following contents with the keyboard, and the vowel input technology using the basic button combination is introduced at http://www.simplecode.net. Korean “Basic Korean 2” was applied.

First, in the existing Moakey type drag input technology, vowels “ㅗ”, “TT”, “ㅓ”, and “ㅏ” are entered by dragging up/down/left/right from the consonant button. As a result, the vowels “ㅡ” and “ㅣ”, which have a frequency of use of about 28%, resulted in a result that you could not enter at all with drag. In the present invention, for consistent input by dragging, and in accordance with “writing habits”, it is appropriate to input the vowel “-” by dragging from left to right, and it is appropriate to input the vowel “ㅣ” by dragging from top to bottom. Point out. Applicants were most puzzled by this part while using Moaki products. If dragging from left to right, of course, "ㅡ" should be entered together. If you drag from the top to the bottom, the vowel “ㅣ” must be entered together. It was intuitively more inconsistent with our notions. Perhaps it is due to reference to the examples in Figures 16-3 and 16-4. When dragged to the right as in Fig. 16-10(a), the vowel “-” is recognized. In other words, [ㄱ → ㄴ] becomes [ㄱ → {ㅡ}] and the input result is recognized as “he”. The button does not have to be different for right dragging. As shown in Fig. 16-10(b), if dragged within the same button as much as "a certain length", the result can be recognized as an input of "-". In addition, as shown in Fig. 16-10(c), the vowel “ㅡ” in “that” is under “ㄱ”, so drag is started from the [ㄹ] button under the [ㄱ] button, and then click the right [ㅁ] button. When dragged, it can be recognized as “he”. Likewise, if you drag as much as "a predetermined length" within the [ㄹ] button under the [a] button, the result can be recognized as "he". Hereinafter, for convenience, it will be described with reference to FIGS. 16-10(a), and of course, the same can be applied to other cases (16-10(b), (c), and (d)). However, Figs. 16-10(a) and (b) cannot be applied simultaneously with Figs. 16-10(c) and (d), and one is applied selectively (designated by the developer or selected by the user in the environment setting). It is natural that you can. Since the drawings of Fig. 16-10(*) can be applied equally to the case of the vowel “ㅣ”, the description of the vowel “ㅣ” is avoided.

Next, input the finality is [ㄱ → ㄴ → ㅁ→ ㄹ] as shown in Fig. 16-11(a), it becomes [ㄱ → {ㅡ} → ㅁ → ㄹ], and “ㅁ” becomes invalid and drag Only the last button, “ㄹ”, is recognized as a valid button and “text” is recognized. Similarly, to input “pole”, drag [ㄱ → ㄴ → ㅁ → ㄹ → ㄱ] as in Fig. 16-11(b), and it becomes [ㄱ → {ㅡ} → ㅁ → ㄹ → ㄱ], and “ㅁ ”, “ㄹ” are invalidated, so the result is recognized as “play”. This can be done by entering “pole” by dragging [ㄱ → ㄴ→ ㄱ] unless other vowels (eg, “ㅏ”) are input as shown below. As shown in Fig. 16-11(c), it is obvious that even if dragged to [ㄱ → ㄴ → (外) → ㄱ], “pole” is recognized as input. Here, “(外)” can be engraved as “other than the text button” or “outside the keyboard skin”. Other buttons (eg Space, Enter, Mode, Skin, Back Space, Chinese character conversion) other than the character buttons involved in drag character input can be regarded as “(外)”.

Next, the four vowels “ㅗ”, “ㅏ”, “ㅜ”, and “ㅓ” are dragged upward according to the shape of the vowel and then dragged back to the drag start button, the “ㅗ” is recognized and dragged to the right. When is dragged back to the drag start button, “ㅏ” is recognized. If dragged downwards and then dragged again to the drag start button, “TT” is recognized. When dragging to the left and dragging again to the drag start button, “ㅓ” appears. Present what is perceived.

First, in the case of “A”, as shown in Fig. 16-12(a), “ㅏ” is placed on the right side of “a”. Therefore, as shown in Fig. 16-12(b), when dragging to the right with [ㄱ → ㄴ → ㄱ] and then dragging again with the drag start button, it will be natural to recognize “A”. Similarly, even if the button does not change as shown in Fig. 16-12(c), the case of moving to the right by a predetermined length and returning can be handled in the same way. It is described in the form of a drag, but it is obvious that the same can be applied to other cases. Here, as shown in Fig. 16-12(b), the case of dragging with the right button and returning to the drag start button can be defined. For example, all consonant buttons except for [ㄱ → ㄴ → “ㄱ” and “ㄴ”... → ㄴ → ㄱ] can be handled in the same way. The case of “old” is also the same as the case of “A”, so the drawings are not separately presented.

In the case of “near”, as shown in Fig. 16-13(a), “ㅓ” is placed on the left side of “a”. Therefore, as shown in Fig. 16-13(b), starting the drag from the [b] button on the right side of the “b”, dragging to the left direction constituting the “ㅓ”, and then returning to the drag start button (ie [B → ㄱ → ㄴ]) can be recognized as “near”. However, taking into account the dragging habits of current users, dragging from the [a] button to the left according to the form of the vowel “ㅓ” as shown in Fig. 16-13(c) and then returning to the [a] button (ie , [ㄱ → (外=mode button) → ㄱ]) can be recognized as “false”. Of course, even if the button does not change as shown in Fig. 16-12(c), moving within the same button by a predetermined length and then returning again can be processed in the same manner. 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 to the right again. However, in the following description, for convenience of description, it will be described with reference to FIGS. 16-13(c). The case of “high” is the same as the case of “near”. For example, since the vowel “ㅗ” is at the bottom of “ㄱ”, the drag start button is the [ㄹ] button located below the [ㄱ] button, and the dragged to [ㄹ → ㄱ → ㄹ] is treated as “high”. I will be able to. However, this cannot coexist in one system with dragging the [ㄱ] button as a drag start button and entering “high” by dragging [ㄱ → (外=upper skin) → ㄱ], and the developer's choice or user It is obvious that only one should be applied depending on the setting of (if the user can select it).

In the above input of “ㅗ”, “ㅏ”, “TT”, and “ㅓ”, when dragged within the same button (or can be applied by dragging outside the button) by a predetermined distance and then return, rightward To determine whether it has progressed or progressed in the downward direction, the dX, dY and dX, dY values of the coordinates of the maximum dragged point from the coordinates of the drag start point in the input case description of “ㅡ” and “ㅣ” above are You can easily judge from which one is bigger and smaller. The point of determination may be when the user enters the drag start button or is closest to the drag start point. As a simple example, if dX, which is the deviation in the X-axis direction, is within a predetermined distance (or length, which should be expressed as the number of pixels in the program), and dY is more than a predetermined distance and dY is positive, it can be recognized as a drag in the right direction. . Other cases are similar, and since it is not difficult, detailed explanation is not provided. However, for convenience of explanation, it was said that the determination of the drag in a certain direction (eg, right) is based on a case in which the dragged button is changed (eg [a → b]). Rather than judging by length, judging by the change of clearly dragged button is a good approach to reliably reduce typing errors. If it is judged by a predetermined change in length 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 the system does not drag it and simply clicks ( Or touch), but if you apply the rule of changing buttons on the screen partitioned in a grid form (eg [ㄱ → ㄴ]), you can clearly recognize and drag clearly from the user's perspective. It reduces the possibility of errors by that amount. The keyboard skin design in Fig. 16-9(*) was also designed in consideration of this point. As 12 character input buttons are located in the center, the user enters the user without the need to drag only within the button when dragging up, down, left and right, even at the most distal buttons (eg [a], [c], [ㅡ], [ㅣ] buttons). You can certainly drag it outside the button.

As shown in Fig. 16-14(a), the vowel “ㅑ” in “gya” is a shape arranged next to the consonant. Therefore, according to the shape, it is reasonable to drag from left to right as shown in Fig. 16-14(b), then return to the drag start button, drag from left to right once more, and then return to the drag start button. . In Fig. 16-14(b), it was dragged to [ㄱ → ㄴ → ㄱ → ㄴ → ㄱ], which can be expressed as [ㄱ → {ㅑ}] by using braces. Or drag it to the right and go back with the drag start button twice (entering the vowel “ㅏ”), and it can be recalled that inputting “ㅏ” twice in a row is recognized as “ㅑ”. If you express this, you can think as [ㄱ → ㄴ → ㄱ → ㄴ → ㄱ] = [ㄱ → {ㅏ+ㅏ}] = [ㄱ → {ㅑ}]. In addition, even if dragged to [ㄱ → ㄴ → ㄷ → ㄴ→ ㄱ → ㄴ → ㄱ], it is the same, but you can enter “ㅏ” even when the first drag goes to the [c] button and returns to the [ㄱ] button, the drag start button. Since it is said that there is, you can think like [ㄱ → ㄴ → ㄷ → ㄴ→ ㄱ → ㄴ → ㄱ] = [ㄱ → {ㅏ+ㅏ}] = [ㄱ → {ㅑ}]. The case of “gyu” is the same as the case of “gya”, so no additional explanation is given.

In the case of “gya”, the description of “a” above: the description of “geo” = the description of “gya”: the description of “gya”], so a detailed description is not provided. However, since the vowel “ㅕ” is placed on the right side of the consonant “ㄱ”, as in the case of “geo” input in Fig. 16-13(b), use the [b] button on the right of the [a] button as the drag start button. You can also define “chaff” by dragging like [b → ㄱ → ㄴ → ㄱ → ㄴ]. If you drag the [a] button as the drag start button and drag it to the left and then come back twice, it can be dragged as follows: [ㄱ → (外=mode) → ㄱ → (外=mode) → a]. This can be interpreted as [ㄱ → {ㅓ+ㅓ}] = [ㄱ → {ㅕ}]. However, this can be used by setting one according to the programmer's implementation or the user's setting, as Fig. 16-13(b) and Fig. 16-13(c) cannot coexist in one system. The drawings are not attached separately, and the case of “gyo” is the same as that of “cham”.

In the above, two vowels of “ㅡ” and “ㅣ” with a frequency of use of about 28%, and four vowels of “ㅗ”, “ㅏ”, “ㅜ”, and “ㅓ” with a frequency of use of about 50%. Enter 10 vowels with a usage frequency of about 84% by summing all four vowels of “ㅛ”, “ㅑ”, “ㅠ”, and “ㅕ” with a usage frequency of about 7% and 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 technique in the first part of the invention. Next, the meaning of the definition of the input rule by drag when combining vowels by continuous drag will be described. For inputting by a continuous drag to the final base, it is possible to refer to the case of applying the first part of the invention to the moa key. In addition, the second part of the invention has the meaning of being able to coexist and be used in one system together with the contents of the first part of the invention.

First of all, in the input of “ㅗ”, “ㅏ”, “TT”, and “ㅓ”, it is shown that the input is input by a continuous drag until the final support. If you input “ㅏ” by dragging in the right direction as in Moaki, when dragged to [ㄱ → ㄴ → ㄷ → ㅂ → ㅈ → ㅣ], [ㄱ → {ㅏ} → invalidate buttons... → ㅣ] It can be seen as, whether the dragged from the [a] button to the [b] button in the right direction was to input the vowel “ㅏ” with “ㄱ” or “ㄱ+ㅡ = that” in succession (1 It is difficult to determine whether the progress was made for dragging to the [-] button in order to input as (see Invention). For convenience, vowels recognized by dragging in one direction (eg {ㅏ}) are called “implicitly dragged vowels”, and vowels recognized by continuous dragging (eg “-”) are “explicitly dragged vowels” I will call it ". The solution would be as follows.

(A) if implicitly dragged vowels and explicit dragged vowels can be combined, both are acknowledged at the same time, or

(B) if implicitly dragged vowels and explicit dragged vowels cannot be combined, only explicit dragged vowels are accepted, or

(C) When there is an explicit dragged vowel, implicit dragged vowels are not always recognized, and only explicit dragged vowels are accepted.

. . . . . . .

Etc. If (A) above is applied, all [ㄱ → {ㅏ} + ㅣ] will be recognized and the result will be “dog”. If the explicitly dragged vowel was “ㅡ”, it becomes [ㄱ → {ㅏ} + ㅡ]. If “{ㅏ}+ㅡ” is not defined as any vowel, “he” will be recognized. (B) In the basic character input technology suggested in the example of the present invention ("Korean Basic 2" at http://www.simplecode.net), it is defined as "ㅏ+ㅡ = ㅗ", but this is [ㆍ This is applied when the [ㅏ] button and the [ㅡ] button, which can also be displayed as a] button, are combined. The combination of the implicitly dragged vowel {ㅏ} and the explicit dragged vowel “ㅡ” is “ㅗ” The question of whether to admit it as "is a separate matter.

As briefly described above, the input of a vowel by dragging in one direction causes a little complicated problem when combining other vowels by a continuous drag. In the case of the present invention, the vowel button is located at the bottom of the consonant button, but the keyboard may have the vowel button on the upper side of the consonant button like a keyboard of Samsung Electronics, or the vowel button is the right side of the consonant button, like the keyboard of LG Electronics. May be in, and many other forms may be possible. In the present invention, only “ㅡ” and “ㅣ” are defined as drag inputs in one direction, and in this case, the above (A), (B), or (C) may be applied. For example, if you drag to [ㄱ → ㄴ → consonant buttons... → ㅣ], it will be recognized as [ㄱ → {ㅡ} → ㅣ] = “긔”.

However, in the present invention, the method of inputting the implicitly dragged “ㅏ” is defined as returning to the drag start button instead of dragging in one direction. In the drag in one direction, it was "implicitly dragged vowel", but the "ㅏ" vowel can be explicitly recognized (specified) due to the process of returning to the drag start button. For example, if dragged to [ㄱ → ㄴ → ㄱ → consonant buttons... → ㅣ], it is clear that the user enters the vowel “ㅏ” through the process of returning to the “ㄱ → ㄴ → ㄱ” drag start button. It can be seen that it becomes. Therefore, the result will be [ㄱ → {ㅏ=specified} → ㅣ] and “dog” will be recognized. As shown in the invention of the first part, if the user wants to input “qi” by continuous dragging, it should have dragged [a → consonant buttons... → ㅣ], and then 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, it is meant to remove the suggestion of vowel input by directional drag by the drag returning to the drag start button, and the combinable vowels can be combined by continuous drag, so all vowels can be entered with one unbroken drag. You can do it. For example, [ㄱ → (外=upper side) → ㄱ → consonant buttons... → ㅏ] = [ㄱ → {ㅏ=specified} → ㅏ] and the result is recognized as “and”. [ㄱ → (外=upper side) → ㄱ → consonant buttons... → ㅏ → ㅣ] = [ㄱ → {ㅏ=specify} → ㅏ → ㅣ] will be recognized as "rule". If the example of inputting the final base is shown, [ㄱ → (outside = upper side) → ㄱ → consonant buttons... → ㅏ → (consonant buttons...) → ㅇ] = [ㄱ → {ㅏ=specified } → ㅏ → → ㅇ] and the result is recognized as “light”. The input of “ㅗ”, “ㅏ”, “ㅓ”, and “TT” suggested by the present invention can be combined with the contents of the first part of the invention to input the collected vowels by continuous dragging, and also to the final base by continuous dragging. It has a meaning to make it possible. (For vowels with a frequency of use of about 50%, implicit removal = explicit, continuous drag is possible) This can be applied equally to the cases of “ㅛ”, “ㅑ”, “ㅠ”, and “ㅕ”.

Since the vowel “ㅡ” is entered with the right drag and the vowel “ㅣ” is entered with the lower drag, only branch drag (right drag, lower drag) is used for vowel input with one-way drag. Left drag is to input the grid sound (eg “ㅋ”) corresponding to the flat consonant (eg “ㄱ”) arranged on the drag start button as shown in Fig. 15-13(a) of the first part of the invention. can do. Likewise, the upper drag inputs a hard consonant (eg “ㄲ”) corresponding to the flat consonant (eg “a”) placed on the drag start button as shown in Fig. 15-3(b) of the invention of the first part. It can be done. As shown in Fig. 16-3, the upper drag is defined as inputting “Shift+X”, so it conforms to the concept of use of the existing (Pocket PC 2002, 2003 emulator confirms that the upper drag works even on the Korean keyboard). . However, in Figure 15-3(b), dragging from [ㄱ → (out = upper) → ㄱ → ㄹ → ㅅ → ㅡ] is expressed as "off" being recognized. In the present invention, [a → (外= Upper side) → A] was defined as “high”, so in order to avoid conflict with this rule and recognize “off”, as shown in Fig. 16-15(a), [ㄱ → (外=upper side) → not “a” Other consonant buttons... → ㅡ] must be dragged to [ㄱ → {hard consonant} → ㅡ] = “off”. The drag result in Fig. 16-15(b) will be “Kung”. In the case of a keyboard in which the vowel button is disposed below the consonant button as suggested in the case of the present invention, even if it is a one-way drag, there is no concern of implicitness (confusing) of the upper drag. This is because dragging from an arbitrary consonant button should be started almost always toward the vowel button at the bottom (invention of the first part), but something promised by the upper drag that was dragged upward (eg hard consonant or grid sound) This is because it makes it clear that you want to enter something promised because it is certain that you dragged to input.

The contents of the present invention, which combines the directional drag and the contents of the first part, may be similarly applied to the case where the vowel button pops up as in the case of the Moa key, although the vowel button may be displayed on the keyboard skin like the illustrated keyboard. .

Next, since the case of inputting the final support to the final support by continuous drag is similar to the case of inputting the final support by applying the first part of the invention in Moaki in the present invention, it will be briefly described through several examples.

First, [ㄱ → ㄴ → ㄱ] is recognized as “a”, so to input “pole”, drag it to [ㄱ → ㄴ] as shown in Fig. 16-16(a) so that “he” is recognized, and then again [a] Instead of dragging with a button, you can bypass and drag the last button to become the [a] button. Next, if you drag to [ㄱ → ㄴ] to input “he”, “he” is recognized. To input “root”, drag [ㄱ → ㄴ] and place it with another button (or including outside the skin) in succession. Move and drag the last button to become the [b] button. For example, it can be done as shown in Fig. 16-16(b). To input “귿”, simply drag to [ㄱ → ㄴ → ㄷ], and it is recognized as [ㄱ → {ㅡ} → ㄷ] = “귿”. In other words, when explicitly dragging from the [a] button to the adjacent button [b] button to the right, it is recognized as a right drag ({ㅡ}).

To input “liver”, drag it to [ㄱ → ㄴ → ㄱ → ㄴ] as shown in Fig. 16-17(a). This is because it can be interpreted as [ㄱ → {ㅏ} → ㄴ]. Similarly, to input “each”, drag it to [ㄱ → ㄴ → ㄱ] as shown in Fig. 16-17(b) so that “A” is recognized, then move it to another button (including outside of buttons or skins) and drag it You just need to make it a [a] button with a button. In the case of “ㅛ”, “ㅑ”, “ㅠ”, and “ㅕ” are similar, avoid detailed explanation.

29. How to input Korean consonants using successive pressing of the same button

Currently, the Korean language input technology that has been commercialized by large domestic companies (eg, Samsung Electronics) is a method of repeatedly pressing the consonant button. In the present invention, it is expressed as a "repeated selection method", and is referred to as a "multi-tap method" in the character input industry. For convenience, the term "repeat selection method" is used. The downside to this approach is that it has ambiguity.

In the keypad of Figure 4-*, "ㅋ" and "ㄲ" are additionally arranged on the buttons arranged with "ㄱ", or logically "ㅋ" and "ㄲ" are "ㄱ" even if they are not physically arranged. It is a keypad associated with the arranged buttons. And in the keypad of Samsung Electronics currently used, "ㄱ" and "ㅋ" are arranged in one button, and "ㄲ" is the keypad associated with the button. In the keypad of Figure 4-* of the present invention or the current Samsung Electronics' keypad, "a" is recognized (or input) by pressing the button 1 time, "ㅋ" is recognized by pressing 2 times, and 3 times When "ㄲ" is recognized by pressing, when "country" is entered, there is an ambiguity of "guka".

In the following, the basic properties of the iterative selection method are summarized, and techniques that improve convenience and remarkably improve ambiguity are presented. The following description is based on the current Unicode Korean characters, and may be applied to additional Korean characters that can be expressed in Unicode in the future.

29.1 Properties of the iterative selection method and current application examples

The basic and common properties of the iterative selection method (that is, the multi-tap method) are as follows. When N alphabets are arranged, pressing the button 1 time inputs the first alphabet, pressing the button 2 times inputs the 2nd alphabet, pressing the 3rd time inputs the 3rd alphabet, ..., When the Nth is pressed, the Nth alphabet is input. If N letters are arranged or associated for a button, the cycle is completed when pressed N times. As mentioned, there is an ambiguity in which it is not possible to know which button is pressed twice whether the second alphabet is entered or the first alphabet is entered twice.

To solve this ambiguity, there is an application case in which a timer is set so that the input state is initialized after a certain period of time. For example, if the button is pressed once and a predetermined time elapses, the first alphabet is determined. When the button is pressed again, the first alphabet is input again.

Another method that is being used to overcome ambiguity is to "cycle toggle". For example, if you press a button with three alphabets of "abc" once, "a" is recognized, if you press twice, "b" is recognized, if you press 3 times, "c" is recognized, and if you press 4 times, it cycles. As a result, "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 again, and when N+2 is pressed, only the second alphabet is recognized again. For convenience, this will be referred to as "recursive toggle type repeat selection method". If only the common basics of the repeat selection method are applied, "c" is entered by pressing 3 times, and then "a" is additionally entered after "c" when pressed again once more. . For convenience, this will be referred to as "basic iterative selection method" or "acyclic iterative selection method".

Loop toggle type repeat selection method

(Pressed 1 time) → a → (pressed 2 times) → b → (pressed 3 times) → c (cycle end) → (pressed 4 times) → a → (pressed 5 times) → b → ( Pressed 6 times) → c (Cycle end) → (Pressed 7 times) → a →. . .

Basic repetitive selection method (non-cyclic repetitive selection method)

(Pressed 1 time) → a → (pressed 2 times) → b → (pressed 3 times) → c (cycle end) → (pressed 4 times) → ca → (pressed 5 times) → cb → ( 6 times pressed) → cc (cycle end) → (7 times pressed) → cca →. . .

Fig. 17-1 shows the basic repetitive selection method and the recursive toggle-type repetitive selection method as a picture for easier understanding.

The "(pressed twice)" means that the button is "pressed twice in total", and of course, refers to a case where the button is pressed twice including the "(pressed once)". This is also the same in Figure 17-1. Both of the two exemplified (cyclic toggle/non-circulating repetitive selection methods) are currently shown in products, and are also used in combination with the timer operation. The inventors of the present invention have a view that the operation of the basic repetitive selection method is more correct, but the recursive toggle repetitive selection method is currently widely used by large companies.

29.2 Current Korean application examples

In Korean, hard consonants (also called "double consonants" when morphologically called) are entered by pressing a button assigned to a flat consonant twice. The operation in this case is an improved operation of the automata on the 2 Beol-Sik Hangul keyboard, and is also the 2 Beol-Sik movement in a large trend. In the case of consecutive consonants such as "XY" in the list of normal syllables (character conjugated letters) in Korean, "X" is the base of the first letter and "Y" is the initial consonant of the last letter. Also, it is revealed that two consecutive consonants can be interpreted as the final consonant of the first letter and the initial consonant of the latter letter.

For example, when the "a" button is pressed once in the initial input state, "a" is input, and when it is pressed again, it becomes "ㄲ". When pressed once more, it becomes "ㄲㄱ". This is an operation to which the basic repetition selection method is applied. If the recursive toggle type repeat selection method is applied, it will be "a" instead of "ㄲㄱ". There seems to be a reason that the cyclic toggle repetitive selection method is applied in the initial input state or the initial consonant input state, but it seems undesirable that the cyclic toggle repetitive selection method is applied in a series of consecutive inputs.

"이 된다. 이는 "ㄱ"이 이미 입력된 "ㄱ"과 결합하여 "ㄲ"으로 한국어 음절(자모결합글자)를 이룰 수 있으면 한국어 자모결합글자로 처리하는 것이다. 이렇게 입력된 "

" 다음에 모음(예. "ㅏ")가 입력되면 "각가"가 된다. 이 역시 기존의 2벌식 한글키보드 오토마타(이하 "2벌식 한글오토마타")에서 받침있는 글자 다음에 모음이 입력되면, 앞글자의 받침이 다음 글자의 초성자음으로 빠져나오는 동작(예. "각" 다음에 "ㅏ"가 입력되면 "가가"로 됨)과 동일하다. 만약 상기 "

" 다음에 "ㄱ"버튼이 한번 더 눌러지면 입력된 "ㄱ"이 앞글자와 결합할 수 없으므로 "

ㄱ"이 된다. 이 역시 기존의 2벌식 한글오토마타에서 앞글자와 결합할 수 없는 자음이 입력되면, 다음 글자의 초성자음으로 처리하는 것과 동일하다. 같은 논리로 상기 "

ㄱ" 다음에 "ㄱ"버튼이 한번 더 눌러지면 "

ㄲ"로 된다. 상기 "

ㄲ" 다음에 "ㄱ"버튼이 한번 더 눌러지면, 기본 반복선택방법 적용시는 "

ㄲㄱ"이 되고, 최초입력상태 또는 초성자음입력상태에서는 순환토글식 반복선택방법 적용하면, "

ㄱ"이 된다. When "A" button is pressed once while "each" is entered, "

This means that if "ㄱ" can be combined with the already entered "ㄱ" to form a Korean syllable (jamo combined character) with "ㄲ", it is treated as a Korean alphabet combined.

When a vowel (eg, "ㅏ") is entered after ", it becomes "Each Ga." This is also in the existing 2 Beol-Sik Hangul Keyboard Automata (hereinafter "2 Beol-Sik Hangul Automata"), if a vowel is entered after the supporting letter, the front It is the same as the action of exiting the base of a letter into the initial consonant of the next letter (eg, if "ㅏ" is entered after "each", it becomes "gaga").

"Next, when the "ㄱ" button is pressed once more, the entered "ㄱ" cannot be combined with the first letter, so"

This is also the same as when a consonant that cannot be combined with the first letter is input in the existing 2-beol-sik Hangul automata, it is treated as the first consonant of the next letter.

When the "ㄱ" button is pressed once more after a"

ㄲ". The above "

When the "ㄱ" button is pressed once more after ㄲ", the default repeat selection method is "

ㄲㄱ", and in the initial input state or initial consonant input state, if the cyclic toggle type repeat selection method is applied, "

Becomes a".

When the basic repetitive selection method is applied in the graph form above, when "ㄲ" is assigned as the second alphabet or related to the "ㄱ" button assigned with "ㄱ",

(Pressed 1 time) → ㄱ → (pressed 2 times) → ㄲ → (pressed 3 times) → ㄲㄱ → (pressed 4 times) → ㄲㄲ → (pressed 5 times) → ㄲㄲㄱ →. . .

ㄲㄱ" 사례) 이 아닌, "ㄱ" (상기 "

ㄱ" 사례) 이 되도록 할 수 있다. However, in the initial consonant state, the cyclic toggle repetitive selection method is applied, so that "ㄲㄱ" (above "

ㄲㄱ" case), not "ㄱ" (above "

A" case) can be made.

29.3 Improvement of first application and optimization of 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 lattice sound "ㅋ" form a group with strong similarities in pronunciation and form. The lattice sound "ㅋ" is a form in which "ㄱ" is arranged vertically, and a hard consonant sound "ㄲ" is a form in which "ㄱ" is arranged left and right. "ㅍ" and "ㅊ" also have strong morphological associations for the corresponding flat consonants "ㅂ" and "ㅈ", but "ㅃ" and "ㅉ" each have for "ㅂ" and "ㅈ" A little weaker than the morphological association.

Hereinafter, examples of "ㄱ", "ㄲ", and "ㅋ" are different flat consonants (eg "c"), different grid sounds (eg "ㅌ"), and other hard consonants (eg "ㄸ"). The same can be applied to ).

As in the current Korean input technology of Samsung Electronics, if you enter "ㅋ" by pressing the "ㄱ" button twice, you cannot avoid the phenomenon of "guka" when you enter "country". However, in the case of inputting “ㄲ” by pressing the “a” button twice, as in the above example, inputting “country” does not become “Kuka”. Also, as pointed out, hard consonants have a stronger relationship with the corresponding plain consonants in terms of morphology than lattice sounds. In addition, by arranging only flat consonants representing hard consonants and lattice sounds on the buttons as shown in the 4-* keypad by the applicant, a concise keypad can be constructed.

In the "3+ other input method" suggested by the applicant, "ㄱ" is recognized by pressing the "ㄱ" button once, "ㄱ" is recognized once more by pressing the "a" button, and "ㅋ" is recognized by pressing 3 times. There was a case where "ㄲ" was recognized by being recognized and pressed 4 times. One cycle is formed until the "A" button is pressed 4 times. It has to be pressed four times in succession to enter one grapheme, "ㄲ". However, as suggested above, when the "a" button is pressed twice, it is sometimes "ㄲ" by the 2-beol-type Hangul automata, and sometimes "a" is the core of the present invention. That is, in some cases, even if the "a" button is not pressed up to 4 times to input "ㄲ", it is possible to press only 2 times.

기"의 "

기" 에서 "ㄲ"과 "ㄱ"이 연속하여 나온다. 기본 반복선택방법을 적용하여 "떡

기"를 입려하면 "떡보키"로 될 것이다. "

기"가 입력되는 과정을 보면, "복" → "

" → "

" → "보키" 와 같이 될 것이다. 이는 "ㄱ"버튼을 2번 누른 것이 절대적으로 "ㄲ"이 되는 것이 아니라 2벌식 한글오토마타에 의하여 때로는 "ㄲ" (예. "

")이 되기도 하고, 때로는 "ㄱㄱ" (예. "복기")이 되기 때문이기도 하다. 그러나, "

기"에서와 같이 "ㄲㄱ"이 연속하여 나오거나("ㄲ"받침 다음 "ㄱ"초성자음), "ㄱㄲ"이 연속하여 나오는 경우("ㄱ"받침 다음 "ㄲ"초성)는 "극히" 드물다. "ㄲㄱ"와 같이 "받침+초성자음"이 나오는 경우는 0.013% 이고, "ㄱㄲ"과 같이 "받침+초성자음"이 나오는 경우는 0.038% 이다. 다른 평자음(예. "ㄷ")과 경자음(예. "ㄸ")의 경우도 유사하므로, 사실상 거의 무시할 수 있는 수준이다. If "ㄱ" and "ㄲ" (by pressing twice) appear consecutively, or when "ㄲ" (by pressing twice) and "ㄱ" appear consecutively, "ㄱㄲ", "ㄲㄱ", "ㅋ" all have the same input value, so there may be ambiguity. For example "mochi

"Of"

"ㄲ" and "ㄱ" appear in succession in "ki". By applying the basic repetition selection method,

If you try to wear "ki", it will become "Tteokboki."

If you look at the process of entering "ki", "fortune" → "

"→"

"→ will be something like "vokey" This is not absolutely "ㄲ" by pressing the "ㄱ" button twice, but sometimes "ㄲ"(eg."

"), sometimes because it becomes "a" (eg, "restore"). However, "

It is rare that "ㄲㄱ" appears consecutively as in "ki"("ㄲ" followed by "ㄱ" initial consonant), or "ㄱㄲ" appears consecutively ("a" followed by "ㄲ" initial consonant) is "extremely" In the case of "consonant + initial consonant" such as "ㄲㄱ", it is 0.013%, and in case of "consonant + initial consonant" such as "ㄱㄲ", it is 0.038%. With other plain consonants (ex. "C") Hard consonants (eg "ㄸ") are similar, so they are virtually negligible.

기"의 "ㄲ"을 "ㄱ"버튼 4번 눌러짐으로 입력하면 모호성없이 입력할 수 있다. 이 역우, 기본 반복선택방법으로 "

기"가 입력되는 과정을 보면, "복" → "

" → "

" → "

" → "

ㄱ" → "

기" 가 된다. "ㄱ"버튼 2번 누름에 의한 "ㄲ"은 다음 입력(예. 모음입력)에 따라 "ㄱㄱ"으로 될 수 있지만, "ㄱ"버튼 4번 눌러짐이 항상 "ㄲ"이 되므로 "

기"의 경우는 모호성없는 입력이 가능하다. "오뚜기"의 경우도 "ㄷ"버튼 2번 눌러짐으로 "ㄸ"을 입력하면, "

두기"와 같이 된다. 즉, "오뚜기=

두기"인 모호성이 있는 것이다. 그러나 "ㄷ"버튼 4번 눌러짐으로 "ㄸ"을 입력하면 모호성없이 "오뚜기"로 올바르게 입력할 수 있다. "오뚜기"를 입력하기 위하여 "ㄷ"버튼을 눌러 "오ㄸ"을 입력하는 과정과 "가까이"를 입력하기 위하여 "

"을 입력하는 과정을 보이면 다음과 같다. 아래에서 모음 "ㅜ" 및 "ㅏ"의 입력에는 본 발명에서 제시한 모음입력기술 또는 다른 어떠한 모음입력기술이 적용될 수 있으며, 이하 유사한 경우에서도 같다.In addition, since the technology that "ㄲ" is input by pressing 4 times is applied, the "

If you enter "ㄲ" of "ki" by pressing the "ㄱ" button 4 times, you can enter it without ambiguity. This inverse, basic repeat selection method is "

If you look at the process of entering "ki", "fortune" → "

"→"

"→"

"→"

A" → "

"ㄲ" by pressing the "ㄱ" button 2 times can be "ㄱㄱ" depending on the next input (eg vowel input), but pressing the "ㄱ" button 4 times always means "ㄲ" So "

In the case of "ki", it is possible to input without ambiguity. In the case of "Ottogi", if you enter "ㄸ" by pressing the "C" button twice, "

It becomes like "Dougi", that is, "Ottogi=

There is an ambiguity of "Dougi". However, if you enter "ㄸ" by pressing the "C" button 4 times, you can correctly enter "Ottogi" 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 technique presented in the present invention or any other vowel input technique may be applied to the input of the vowels "TT" and "ㅏ" below, and the same applies in similar cases hereinafter.

→

ㄷ →

→ 오ㄸ →("ㅜ"입력)→ 오뚜Oh →

→

C →

→ Oㄸ →(Enter "ㅜ") → Otto

→

→

→("ㅏ"입력)→ 가까A → each →

→

→

→(Enter "ㅏ")→ Close

" 다음에 "ㅏ"가 입력되면 "각가"가 되지만, "ㄱ"버튼 4번 누름은 항상 절대적으로 "ㄲ"이 된다고 하였으므로, "ㄱ"버튼 4번 누름 다음에 "ㅏ"가 입력되면 "가까"가 된다. Entered by pressing the "ㄱ" button twice

"If "ㅏ" is entered next, it becomes "each price", but it is said that pressing the "ㄱ" button 4 times always becomes absolutely "ㄲ", so when "ㅏ" is input after pressing the "ㄱ" button 4 times, the "closer""It becomes.

Even if you input "ㄲ" by pressing the "ㄱ" button 4 times, since "ㄱㅋ", "ㅋㄱ" and "ㄲ" all have the same input value, there is ambiguity. But in practice, this is also "extremely" rare in the words we use. It is found that 0.013% of cases with "backup + initial consonants" such as "ㄱㅋ" appear, and 0% of cases with "backup + initial consonants" such as "ㅋㄱ". Other plain consonants (eg "c") and lattice sounds (eg "t") are similar, so they are virtually negligible.

The change when the "a" button is pressed consecutively by applying the basic repeat selection method is as follows.

ㄱ → ㄲ or ㄱㄱ → ㅋ → ㄲ (cycle ends) → ㄲㄱ → ㄲㄱㄱ or ㄲㄲ → ㄲㅋ → ㄲㄲ (cycle ends) → ㄲㄲㄱ →. . .

When the basic repeat selection method is applied and the "a" button is successively pressed after the letter "A", the change is as follows.

→

→

(사이클 종료) →

ㄱ →

ㄲ →

ㅋ →

ㄲ (사이클 종료) → . . .A → each →

→

→

(End of cycle) →

A →

ㄲ →

ㅋ →

ㄲ (End of cycle) →. . .

"이고, 8번 눌러진 상태는 "

ㄲ"이 된다. 4번 눌러지고 나면 입력규칙 사이클이 종료되었으므로 기 입력된 글자(예."

")는 완성되고, 5번째 눌러짐은 다시 1번 눌러짐(새로 "ㄱ"입력)과 동일한 효과를 내게된다.When the "a" button is pressed 4 times after "A", "

", the state pressed 8 times is "

ㄲ". After pressing 4 times, the input rule cycle has ended, so the previously entered character (eg."

") is completed, and the 5th press will have the same effect as the 1st press again (newly enter "a").

ㄲ" 상태에서 한번 더 "ㄱ"버튼이 눌러지면, 다음의 2가지로 처리될 수 있다. 기본 반복선택방법이 적용되면, "

ㄲㄱ"이 될 것이다. 사이클 종료후, 눌러진 "ㄱ"버튼이 한번 더 눌러졌을 때, 입력중인 글자가 초성자음 상태에서는 순환토글식 반복선택방법이 적용된다면, "

ㄱ"이 될 것이다. 이 상태에서 "ㄱ"버튼이 한번 더 눌러진다면 "

ㄲ"이 될 것이다. 상기 기본 반복선택방법 적용의 경우, 그리고 사이클종료후 초성자음일 때 순환토글식 반복선택방법이 적용시의 경우를 조금 더 이해하기 쉽게 그림으로 나타내면 도면17-2와 같다. 도면17-2에서, 4번 눌러졌을 때의 "ㄲ"은 1사이클이 완료되었을 때의 결과이고, 8번 눌러졌을 때의 "ㄲㄲ"은 2사이클이 완료되었을 때의 결과인 것이다.It is preferable that the cyclic toggle repetitive selection method is not applied in the state of transition from the input of the base to the initial consonant. Above the last "

If the "a" button is pressed once more in the "ㄲ" state, it can be processed in two ways: If the basic repetitive selection method is applied, "

After the cycle is over, when the pressed "ㄱ" button is pressed once more, if the character being input is in the initial consonant state, the cyclic toggle type repeat selection method is applied, "

It will become a". If the "a" button is pressed once more in this state, "

When the basic repetition selection method is applied and the case of applying the cyclic toggle type repetition selection method when the initial consonant is applied after the end of the cycle is shown in Fig. 17-2 for easier understanding. In Fig. 17-2, "ㄲ" when pressed 4 times is the result when 1 cycle is completed, and "ㄲㄲ" when pressed 8 times is the result when 2 cycles are completed.

There is a double base (layered base) such as "ㄺ" among Korean base (last consonant). In the same form as the double support "xy", "x" can be combined with "ㄱ" to form "xy". The operation in this case is also the same. For example, when you enter "know", if you try to enter "ㄲ" by pressing the "ㄱ" button twice, it becomes "go to go". However, it is solved simply by making it always "ㄲ" by pressing the "ㄱ" button 4 times. When the "A" button is pressed after "Al" is as follows, it can be applied to other similar cases. When it is pressed twice, it becomes "ㄱㄱ" (ex. "A"), when it is pressed 3 times, it becomes "ㅋ" (yes, "Al ㅋ"), and when it is pressed 4 times, it always becomes "ㄲ" (ex. " I know"). In the input of the vowel "ㅏ" below, the vowel input technique or any other vowel input technique suggested in the present invention can be applied, and the same applies in the case of similar hereinafter.

Al → A → A → A → Al → (Enter "ㅏ") →

In Korean, when "ㅅ" first consonants appear after "ㅆ" (that is, "ㅆㅅ"), there are many such as "~ had" and "~ was", but conversely, "ㅅ" followed by "ㅆ" first consonants Rarely comes out. When applying the basic repetition selection method, it is natural that when the "ㅅ" button is pressed after the "ㅆ" base, it becomes "ㅅ". This is because only "ㅅ" and "ㅆ" are arranged or associated with the "ㅅ" button. The same is true of the keypad in Figure 4-*.

수" 와 같이 된다. 이 경우도 "ㅅ"버튼 4번 누름으로 "ㅆ"을 입력하면 간단히 해결되며, 동작은 다음과 같다. "얼" 다음에 "ㅅ"버튼이 눌러질 때의 변화이다. 2번 눌러졌을 때 "ㅅㅅ" (예. "

ㅅ") 이 되고, 3번 눌러졌을 때 "ㅅㅆ" (예. "

ㅆ") 이 되고, 4번 눌러졌을 때 절대적으로 "ㅆ"이 되므로 "얼ㅆ"가 된다. 아래에서 모음 "ㅜ"의 입력에는 본 발명에서 제시한 모음입력기술 또는 다른 어떠한 모음입력기술이 적용될 수 있으며, 이하 유사한 경우에서도 같다.When "ㅅ" comes at the position of "y" among the double support "xy", there are "ㄳ", "ㄽ", and "ㅄ". In the case of "ㄱㅆ", "ㄹㅆ", and "ㅂㅆ", it is difficult to enter "ㅆ" by simply pressing the "ㅅ" button twice. For example, in the case of "Eolsu", if you try to enter "ㅆ" by pressing the "ㅅ" button twice, "

In this case, it is also solved simply by entering "ㅆ" by pressing the "ㅅ" button 4 times, and the operation is as follows: This is the change when the "ㅅ" button is pressed after "Ell". "ㅅㅅ" when pressed twice (ex. "

ㅅ"), and when pressed 3 times, "ㅅㅆ" (ex. "

ㅆ"), and when it is pressed 4 times, it is absolutely "ㅆ", so it becomes "Ul". In the input of the vowel "TT" below, the vowel input technique suggested in the present invention or any other vowel input technique is applied. It can be, and the same applies in the following similar cases.

→

ㅅ →

ㅆ → 얼ㅆ →("ㅜ"입력)→ 얼쑤Earl →

→

ㅅ →

ㅆ → Eol-ㅆ → (Enter "ㅜ") → Eolsu

There are cases where "ㅆ" appears as an initial consonant after the vowel. For example, in the case of "Asa", if you input "ㅆ" with the "ㅅ" button 2, it becomes "Assa" by the Hangul automata. Below, the right arrow (→) means that the "ㅅ" button is pressed. The input of the vowel "ㅏ" can be applied to any vowel input method (including other input methods not suggested by the applicant). For example, it may be entered as "ㅣㆍ" as in the past, or may be entered by pressing the "ㆍ" button once as suggested in the previous application. This is the change when the "ㅅ" button is pressed after "ah".

Ah → ah → ah → (enter "ㅏ") → asa

For consistent input rules and for unambiguous input, four presses of the “ㅅ” button can be treated as “ㅆ”. "ㅆ" by pressing 2 times can be changed to "ㅅㅅ" according to the next input (eg vowel input), but like the case of "ㄲ", "ㅆ" by pressing 4 times is absolutely applied. Pressing 3 times becomes "ㅆㅅ" as described earlier. The following is the input process of "Asa" by pressing the "ㅅ" button 4 times.

Oh → Oh → Ooh → Oo → O → (Enter "ㅏ") → Okay

If there is ambiguity (eg, input "ㄱㅋ" as a final consonant and an initial consonant), the way to overcome the ambiguity is to end the input token by applying a timer (check for no input of a certain time) as in the conventional method, press the space button, or right There are methods such as ending the input token by pressing an arrow button. To enter "ㄱㅋ" (with a final consonant), after entering "ㄱ", press the right arrow button to cut the input token, and press the "ㄱ" button 3 times to enter "ㅋ". A list of cases where there is ambiguity is as follows.

Aha 0.013 ㅋㄱ 0 ㄱㄲ 0.038 haha 0 ㄷㅌ 0 ㅌㄷ 0.064 ㄷㄸ 0.002 ㅌㅌ 0 ㅂㅍ 0.013 ㅍㅂ 0.004 ㅂㅃ 0.001 ㅍ ㅍ 0.001 ㅅㅆ 0.003 ㅈㅊ 0.059 ㅊㅈ 0.002 ㅈㅉ 0 ㅊㅊ 0.003 Sum 0.203

In Korea, the ratio is about half-and-half for the case of "support + initial consonant" and the case of "neutral vowel + initial consonant". In the present invention, there is no ambiguity in the case of "neutral vowel + initial consonant". This is because a hard consonant (eg, "ㄲ") can be input by pressing the flat consonant (eg "ㄱ" button) 4 times. Therefore, the total of 0.2% becomes 0.1% in all cases. It can be seen that ambiguity occurs once out of 1000 characters, and since the Korean input technology presented in the keypad of Figure 4-* of the present invention takes about 3.5 strokes per character, it can be seen that ambiguity occurs once by pressing about 3500 strokes. . It can be seen that there is virtually no ambiguity. The reason for this lack of ambiguity is that consonants with similar phonetic values (eg, "ㄱ" and "ㅋ") appear in succession in Korean Hangul.

기"를 입력한 것이 "보키"로 되지 않음. "오뚜기"를 입력한 것이 "

두기"로 되지 않음)가 있다. The above result is 4 to input "ㄲ" in one case of the applicant's "3+ other input method"("a" is pressed once, "ㅋ" is pressed 3 times, and "ㄲ" is pressed 4 times) Pressing twice in a row can give you a bit of boredom, but in most cases, pressing the "a" button twice has the effect of allowing you to enter "ㄲ". Cognitively, "ㄲ" is a form in which "ㄱ" is overlapped left and right, so it is possible to input "ㄲ" by pressing the "ㄱ" button twice, which is a way to match the emotions of Korean users who write horizontally. There is one effect. In addition, the result is that "ㄲ" is recognized by pressing the "a" button 2 times, and "ㄲ" is entered by pressing 4 times in the applicant's previous application where "ㅋ" is recognized by pressing 3 times. Reduced effect (eg."

Entering "ki" does not become "Boki". Entering "Ottogi" does not become "

There is "not put").

It was pointed out that the basic repetition selection method is more suitable than the cyclic toggle repetitive selection method when inputting from the base to the initial consonant in the continuous pressing of the flat consonant button. However, it was mentioned that when the cycle is completed, the recursive toggle method can be applied. Furthermore, if the hard consonant recognized by pressing the flat consonant button 2 times is "initial consonant", it may not be treated as a hard consonant again. In other words, one press of the "ㄱ" button is recognized as "ㄱ", the second press is recognized as "ㄲ" or "ㄱㄱ", and 3 times is recognized as "ㅋ". 2 If the recognized "ㄲ" when pressed twice by the beol-sik Hangul automata was the initial consonant, the cycle is completed by pressing 3 times, and the one pressed again is "ㅋㄱ" with the recognized "ㅋ" (default When the repetitive selection method is applied) or "a" (when the circular toggle type repetitive selection method is applied), it can be set. If this is expressed as a picture, it is as shown in Fig. 17-3. In Figure 17-3, for convenience, a graph (or diagram) format and a flowchart format are integrated and expressed. However, for the consistency of the input rule, pressing 4 times can always be processed as "ㄲ" (ie, hard consonant), and in the opinion of the present inventor, it is always a hard consonant to press the input rule consistently 4 times. Looks desirable.

The above case was a case where plain consonants were used as basic consonants, and hard consonants and trellis were input. The above example can be applied to the keypad shown in Fig. 4-*, and can also be applied to other types of keypads not suggested by the applicant. In addition, the above example may be applied together with the vowel input method proposed by the applicant in the previous application and the present invention, or may be applied together with other vowel input methods that exist or will appear in the future.

It can be applied simultaneously with the control processing method using vowel buttons (eg "ㅋ = ㄱㅡㅡ", "ㄲ = ㄱㅣㅣ"), which is a technique that can be entered without any ambiguity as suggested in the applicant's previous application. When inputting a lattice sound and a hard consonant sound, if the control processing method using the vowel button suggested in the applicant's previous application (eg, "ㅋ = ㄱㅡㅡ", "ㄲ = ㄱㅣㅣ") is used in combination, the ambiguity is It will be even less. Although the input of "ㅎ" was not suggested based on the keypad of Figure 4-*, it was described in the previous application that "ㅎ" may be separated by a separate button. In the present invention, it is essential to show that input can be performed with "extremely" less ambiguity on a concise keypad (eg, Fig. 4-*) by using the relationship between plain consonants, lattice sounds, and hard consonants regularly. This is a key matter that can be "commonly" applied not only to the keypad of Figure 4-* of the present invention, but also to any modified case. The input of "ㅎ" (or "ㄹ") expressed as a drop-out consonant in the applicant's previous application can be applied to the input of a lattice sound or hard consonant as described below, and will be separately mentioned below.

The above input technology, which is the core of the present invention, is a technology of "Basic Korean 3" and will be disclosed as a product through the site http://www.simplecode.net.

29.4 Optimization of processing of dropped consonants (eg "ㅎ") by repeated pressing

Next, additional examples of transformation are presented. This is the case assuming that "ㅎ" is additionally arranged or associated with the "ㅇ" button. This is the case where "ㅎ" is regarded as a modified alphabet of "ㅇ" (lattice consonant or hard consonant) as an expression of the earlier application. In the earlier application, it corresponds to the case where "ㅎ" is treated as a modified alphabet of "ㅇ" (lattice consonant or hard consonant). As the "ㅇ" button is pressed, applying the default repeat selection method will result in the following.

ㅇ → ㅇㅇ → ㅎ (cycle end) → ㅎㅇ → ㅎㅇㅇ → ㅎㅎ (cycle end) → ㅎㅎㅇ →. . .

In modern Korean, there is no "Ssang Yi-eung", but if it is possible to input "Ssang-e-eung", an archaic character element, "Ssang Yi-eung" may be made in some cases by pressing the "o" button twice by the 2-beol-sik Hangul automata.

In addition, as in the case presented in the previous application, "b" and "ㄹ" may be arranged or related to one button as a group. In this case, the processing of "b" and "ㄹ" can be processed similarly to the cases of "ㅇ" and "ㅎ". If "ㄹ" is treated as a modified alphabet of "b" (ie, a lattice sound or hard consonant), 9 basic consonants can be assigned to 9 buttons in [1] to [9], so "ㅇ" And "ㅎ" may be assigned to different buttons.

If "ㅇ" and "ㅎ" are entered according to the basic repetition selection method illustrated above, the above-mentioned items (once every about 1000 characters or about 3500), including cases where "ㅇ" and "ㅎ" appear consecutively, etc. There is more ambiguity than once in another stroke.

However, it can be applied simultaneously with the control processing method using vowel buttons (eg "ㅋ = ㄱㅡㅡ", "ㄲ = ㄱㅣㅣ"), which is a technique that can be entered without any ambiguity as suggested in the applicant's earlier application. If "ㅎ" is always entered as "ㅎ = ㅇㅡㅡ" or "ㅎ = ㆍㅡㅡ" suggested by the applicant's earlier application, the method by pressing the repeat above is used to input all lattice and hard consonants. Even so, ambiguity will occur once in about 1000 characters (about 3500 strokes). The same is true for the case where the previous application is required to enter "ㅎ = ㅏㅡㅡ". In addition, although it is not a normal word, it is possible to input it without ambiguity by entering "ㅋ" as "ㄱㅡㅡ" even when entering "ㅋㅋ", which is widely used in the younger generation. When inputting a lattice sound and a hard consonant sound, if the control processing method using the vowel button suggested in the applicant's previous application (eg, "ㅋ = ㄱㅡㅡ", "ㄲ = ㄱㅣㅣ") is used in combination, the ambiguity is It will be even less.

Next, one of the contents suggested in the applicant's previous application, by pressing the "ㆍ" button (allocated to the number button [0] button) three times, inputting "ㅎ" can be applied. As mentioned in the previous application, this means inputting a grid sound by pressing the flat consonant button 3 times and providing a consistent input rule and entering the "ㅎ" associated with the "ㆍ" button by pressing the "ㆍ" button. . When the "ㆍ" button is pressed 3 times after the consonant and "ㅎ" is input, there is no ambiguity. As suggested in the previous application, there is ambiguity, but very little. First, a brief look at the case of applying the vowel input method used by Samsung Electronics is as follows. If there may be ambiguity, then the vowel "ㅏ" (in the conventional method, it is entered as "ㅣㆍ"), then the "ㅑ", then the "TT", then the "ㅠ", then the "ㅎ" (the final consonant or the initial consonant of the next letter ), there may be ambiguity. If the basic iteration selection method is applied, it will look like this: The case where the "ㆍ" button is successively pressed after "ki", "that", etc. is as follows. The allegorical arrow "→" below is expressed including the pressing of the "ㆍ" button, and is the same in the following.

Ki → Ga → Gya → Gyaㆍ →

That → Gu → Gyu → Gyuㆍ →

If the automata is not modified and only the basic repetitive selection method is applied, in the case of "ha" followed by "ga", "gya", "gu", "gyu", etc., "ㅎ = ㅇㅡ" suggested by the applicant's previous application You can use "ㅡ" or "ㅎ = ㆍㅡㅡ". When "ㅎ" is followed by "ㅏ", "ㅑ", "ㅜ", and "ㅠ", it is 0.022%, 0.001%, 0%, and 0%, respectively. When "ㅎ" follows as an initial consonant after "ㅏ", "ㅑ", "ㅜ", and "ㅠ", it is 0.563%, 0.02%, 0.4%, and 0.094%, respectively. This is a negligible level, except for the case where "ㅎ" comes as the initial consonant after "ㅏ". It is as follows when applying the basic repetition selection method to make up a Korean syllable as much as possible.

→ 갛 →

→

ㆍ(or 가ㅎㆍ) →

ㆍㆍ(or 갸ㅎㆍㆍ)Ki → Ga → Gya → Gyaㆍ →

→ red →

→

ㆍ(or goㅎㆍ) →

ㆍㆍ(or gyhaㆍㆍ)

→

→

→

ㆍ(or 규ㅎㆍ) →

ㆍㆍ(or 규ㅎㆍㆍ)That → Gu → Gyu → Gyuㆍ →

→

→

→

ㆍ(or Gyuㅎㆍ) →

ㆍㆍ(or Gyuㅎㆍㆍ)

"을 입력하고 싶었다면, 상기 "갸" 다음에 "ㆍ"버튼의 연속누름을 종료해 주는 수단(예. 우측이동버튼 또는 스페이스버튼 등등. 이하 대표하여 "우이동버튼"으로 표현)을 누른 후, "ㆍ"버튼 3번 누름으로써 "

"을 입력하도록 할 수 있다. 또는 타이머에 의하여 "갸" 입력후 일정시간(예. 0.2초)이 경과하면 "ㆍ"버튼 연속누름에 의한 처리가 종료되는 것으로 하여, "갸" 다음 0.2초 경과후 "ㆍ"버튼 3번 눌러짐으로 "

"을 입력할 수 있다. 상기 "갛" 상태에서 "가호"를 입력하기 위하여 "ㆍ"버튼을 한번 더 누르면 "

"이 되는데, 이 경우도 "갛" 상태에서 상기 우이동버튼 또는 상기 타이머에 의하여 "갛"을 확정한 상태에서 "ㆍ"버튼과 "ㅡ"버튼을 순차적으로 눌러 "가호"를 입력할 수 있다. If the input value that is input after the middle of the input in the above example is a "ㆍ" button (eg "symbol = garh"), there may be ambiguity. However, in cases where the ending "ㅎ" and the initial consonant "ㅎ" appear after the neutral vowels "ㅑ" and "ㅠ", they are almost negligible as 0.001%, 0%, 0.02%, and 0.094%, respectively. If the "ㆍ" button is pressed consecutively as above, there may be ambiguity. If "

If you want to enter "," press the means for ending the continuous pressing of the "ㆍ" button after the "gya" (eg, right shift button or space button, etc. hereinafter represented by "right shift button"), By pressing the "ㆍ" button 3 times,

It is possible to input ". Or, if a certain time (eg 0.2 seconds) elapses after entering "Gya" by means of a timer, processing by continuous pressing of the "ㆍ" button is assumed to be terminated. Then press the "ㆍ" button 3 times to "

You can enter ". If you press the "ㆍ" button once more to enter "Analog" in the "red" state above, "

In this case, it is also possible to input "Analysis" by sequentially pressing the "ㆍ" button and the "-" button in a state in which "red" is confirmed by the right movement button or the timer in the "red" state.

In the past, the letters previously entered with the right move button or the timer are confirmed, so if the right move button is pressed in the "Gya" state, "Gya" is confirmed, and when the "ㆍ" button is pressed 3 times again, "ha" is input. , It became "Gyaha". However, in the above example, it serves to cut off the automata by continuously pressing the "ㆍ" button. To completely confirm the previously entered character (eg, "gya" or "red") is to press the right move button twice or a certain time by the timer (eg, the 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 the "ㆍ" button successively pressing the "ㆍ" button sequentially by the existing means (eg, right movement button, timer) primarily (eg, right movement button one push or 0.2 second timer) is used. It can be treated as being cut off, and the previously entered character can be confirmed secondarily (eg, pressing the right button one more time or a timer with a value greater than 0.2 seconds). The same can be applied to the following cases.

Another method is to terminate the continuous pressing token of the "ㆍ" button for consonant input when the delete button is pressed during continuous pressing of the "ㆍ" button (initialize the continuous pressing logic of the "ㆍ" button for consonant input). It can be done. For vowel input, it can operate the same as before. For example, if the delete button is pressed in the state of "Red", "ㅎ", which is a grapheme unit or recognition unit (described below), is deleted and becomes "A". Since the delete button is pressed once, the process of continuously pressing the "ㆍ" button is terminated, and when the "ㆍ" button is pressed 3 times in this state, it becomes "red". This can also be applied to the following cases. The advantage of this method is that when a character that the user does not want is displayed, the user presses the delete button to correct it, and the unwanted character does not appear again as the logic before the delete button was pressed, and has the advantage of being able to input the desired character.

In addition, since consonants (support or initial consonants) rarely appear after "ㅑ" and "ㅠ", a modified automata can be applied as follows.

→ 갛 → 갛ㆍ(or 가ㅎㆍ) → 갛ㆍㆍ(or 가ㅎㆍㆍ) →

ㆍㆍ(or 갸ㅎㆍㆍ)Ki → Ga → Gya → Gyaㆍ →

→ Red → Redㆍ (or Gohaㆍ ) → Redㆍㆍ(or Gohaㆍㆍ) →

ㆍㆍ(or gyhaㆍㆍ)

→

→

ㆍ(or 구ㅎㆍ) →

ㆍㆍ(or 구ㅎㆍㆍ) →

ㆍㆍ(or 규ㅎㆍㆍ)That → Gu → Gyu → Gyuㆍ →

→

→

ㆍ (or Guㅎㆍ) →

ㆍㆍ(or Guㅎㆍㆍ) →

ㆍㆍ(or Gyuㅎㆍㆍ)

In the earlier application, a technique for entering the vowel "ㅏ" with one push of the "ㆍ" button has been proposed. Also, the technique of entering "ㅓ" by pressing the "ㆍ" button twice has been suggested. This is a button that can resemble the vowel "ㅏ" instead of the "ㆍ" button as in Figure 4-*, etc. (eg, a "ㅏ" button or a button in the shape of a combination of "ㅏ" and number "0", etc.) The same is the case. Hereinafter, for convenience, it will be described as a "ㆍ" button. In this case, one of the cases in which the basic repetitive selection method is applied is as follows. Again, the allegorical arrow (→) below is expressed including the pressing of the "ㆍ" button.

A → go → go → a ha → red → 겋

The example above shows that the "ㆍ" button being input is processed as forming a Korean syllable as much as possible, so the input of "ㅎ" in "red", "겋", etc. can be processed by pressing the "ㆍ" button 3 times. . When the "·" button is pressed after "ki" and "the", the modified automata can also be applied as shown above.

→ 갛 → 가하 → 가허 → 갸허Ki → Ga → Gya → Gya →

Gat inflicting → → → → gaheo gyaheo

→

→ 구하 → 구허 → 규허That → Gu → Gyu → Gyuㅏ →

→

→ Guha → Guhe → Guhe

Here, for "red" (or including "gaha"), you can use the technique suggested in "ㄱ → go → go → ㄱㅎ → red → 겋" above. In the case of "ㅏ", which is a frequently used vowel over about 22%, it can be entered with one push of the "ㆍ" button, because there are not many users to enter in two strokes such as "ㅣㆍ". Therefore, the modified automata can be applied as follows.

→ 기하 → 기허 → 가허 → 갸허Ki → Ga → Gya → Gya →

→ Geometry → Giheo → Gaheo → Gaheo

If the user wants to enter "A", press the delete button once in the "Allowed" state to make it "go heh" (or "red"), and again according to a predetermined vowel input method (eg "ㆍ-"). You can enter "A" by entering "ㅗ". As described above, by pressing the delete button, the logic for processing the continuous input of the "ㆍ" button for inputting the dropped consonant (eg "ㅎ") may be initialized. If you press the delete button in the "licensed" state to become "go heh", you can refer to the "improvement of the delete button processing" presented below. If the user wishes to input a “symbol”, in the “geometric” 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 method

In our modern Korean Unicode system, there are five hard consonants (double consonants): "ㄲ", "ㄸ", "ㅃ", "ㅆ", and "ㅉ". The ones that can be used as double final consonants are "ㄲ" and It's just "ㅆ". In this way, the double consonants "ㄸ", "ㅃ", and "ㅉ" that cannot be final consonants are called "non-final consonants" for convenience, and the corresponding flat consonants "c", "ㅂ", and "ㅈ" are "paired" for convenience. I will call it "Pure consonant with no consonant finality".

In the above "29.3 Improvement of pre-application and optimization of Korean consonant input", the applicant's pre-application was improved and as the flat consonant button (eg [ㄱ] button) is pressed, "ㄱ → ㄲ or ㄱㄱ → ㅋ → ㄲ →. ." It has been suggested to be input as. The important thing in the above is that when the [a] button is pressed twice, it is recognized as a double consonant (hard consonant), and when the next vowel is input, it becomes two plain consonants (ie, "ㄱㄱ"), so that the [a] button 2 When pressed twice, diconsonants can be seen as temporary diconsonants.

As mentioned, in the applicant's earlier application, it was suggested that the flat consonant button (eg, [ㄱ] button) is pressed, and that the input is entered as "ㄱ → ㄲ → ㅋ". By improving this, as suggested in "29.3 Improvement of Prior Application and Optimization of Korean Consonant Input" above, a double consonant (eg "ㄲ") when the [a] button is pressed twice is then input 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 something like "ㄱ → ㄲ or ㄱㄱ → ㅋ". As explained, when the [a] button is pressed twice after "A", "

"It becomes, but if a vowel (eg "ㅏ") is entered in this state, it becomes "each". "

When "ㄱ" is entered in the "state,"

"Become,"

When "ㄴ" is entered in "Status", "

The two-time press of the flat consonant button becomes a double consonant, according to the 2-beol-sik Hangul Combination Rule, if the same plain consonant is input twice as a double consonant, it is recognized as a double consonant. If it can be processed as two plain consonants, it is recognized as two plain consonants.. In summary, as the plain consonant button is pressed consecutively, appropriate letter conjugated letters are formed according to the appropriate Korean letter combination rule (Hangul Automata). As far as possible, it means that it is recognized as "flat consonant → double consonant or two flat consonants → lattice sound".

The ambiguity when processed as described above is as follows. First, there is an ambiguity of 0.1% suggested above, so a case where a double consonant comes after a neutral vowel as an initial consonant is added as follows. This is because it excludes the absolute input of double consonants 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 a case where an initial consonant comes after a neutral vowel, it is the frequency of occurrence when there is no final consonant. In Korean, about half of the letters ending in a neutral vowel without a final consonant (54% to be exact), and about half (46% to be exact) with a final consonant. To be precise, it should be considered as a weight of 54%, but it is reported as about half and half, and there is an ambiguity of 0.9%, which is about half of 1.8%. When combined with the 0.1% ambiguity, it can be seen that there is about 1% ambiguity.

If a simple repetitive selection method rather than a recursive toggle type repetitive selection method is applied, "ㄱ → ㄲ or ㄱㄱ → ㅋ (cycle end) → ㅋㄱ → ㅋㄲ → ㅋㅋ →.. ." Becomes like In the "XY" form, if "X" is a final consonant, then "Y" is an initial consonant. Therefore, a cyclic toggle repetitive selection method may be applied only when the input state is in the initial consonant state. For example, "ㄱ → ㄲ or ㄱㄱ → ㅋ → ㅋㄱ → ㅋㄲ → ㅋㅋ → ㅋㄱ → ㅋㄲ → ㅋㅋ.. ." Becomes like Currently, phrases such as "ㅋㅋ" or "ㅋㅋㅋ" are frequently used among young people, so even if "X" is in the initial consonant state, it may be better to apply a simple repetition selection method rather than a cyclic toggle repetitive selection method.

ㄷ"와 같이 되는 것이다. ("오" 아래 종성자음으로 "ㄸ"이 올 수 없으므로) 즉, 중성모음까지 입력된 상태에서 쌍자음종성불가 평자음이 2번 연속하여 입력되면 자연히 1번째 입력은 종성자음으로, 2번째 입력은 초성자음으로 나누어지게 된다. In the above, when the flat consonant button (eg [a] button) is pressed twice, the double consonant (eg “ㄲ”) always occurs in the initial consonant state. However, in the case of input as a final consonant, pressing the [c] button (or [ㅂ] button or [ㅈ] button) twice is always recognized as two plain consonants (eg, "ㄷ"), not double consonants. do. E.g "

It becomes like "c". (Because "ㄸ" cannot come as a final consonant under "O") In other words, if a double-consonant non-final consonant is input twice in a row, the first input is naturally As the final consonant, the second input is divided into the initial consonant.

Even if the input rule is presented as “flat consonant → double consonant or two flat consonant → grid” (eg, “ㄱ → ㄲ or ㄱㄱ → ㅋ”), users can easily recognize it as “flat consonant → double consonant → grid” . Of course, it is perceived that the double consonant when the flat consonant button such as "a" is pressed twice can be divided into two flat consonants in some cases, but it will feel strange if the double consonant is not output when the flat consonant button is pressed twice. It could be. Therefore, a modified form of the above embodiment is suggested by using a property that cannot be a final consonant.

When the flat consonant button is pressed twice in the neutral vowel state (eg "A"), the final possible diconsonants (ex. "ㄲ", "ㅆ") are always displayed as ending diconsonants and according to the next input. Since it is a double consonant or it is divided into two flat consonants, it is natural to the user and there is no problem. In the case of flat consonants (i.e. "ㄸ", "ㅃ", "ㅉ"), when the flat consonant button is pressed twice in a row in the neutral vowel state (ex. "A"), follow the logic above. It should be displayed as two flat consonants (final consonant + initial consonant), but since the user recognizes that the user has pressed the flat consonant button twice as a double consonant (hard consonant), it is treated as a double consonant as an initial consonant. For example, if the [c] button is pressed twice in succession after "A", it is processed as "thin". The advantage of doing this is that the two presses of the flat consonant button are always displayed as double consonants. The disadvantage is that if the initial consonant "c" appears consecutively after "c" as the final consonant, the user handles it manually (e.g., a predetermined time delay by a timer, manual by pressing the classification button after entering the first "c" Distinction, ...). (Since the second press of the [c] button is treated as the initial consonant "ㄸ"), the rate at which ambiguity occurs in this case is as follows.

Vowel+ㄲ 0.856 C+c 0.015 ㅂ+ㅂ 0.071 Vowel+ㅆ 0.219 ㅈ+ㅈ 0.03 Sum 1.191

In the above, about 54% of letters without a final consonant (support) in Korean, so in the case of "neutral vowel + initial consonant" (eg, "vowel + ㄲ"), it should be considered as the weight of 54%, and the final consonant (final consonant). In the case of "consonant + consonant" (ex. "c+c"), it should be considered as a weight of 46%, since it is about 46% of cases with a final consonant (support) and letters without a final consonant. Since is about half and half, it is assumed to be the weight of 50:50 and is a simple summation result. Dividing the above 1.191% by half can be said to have an ambiguity of about 0.6%. Here, adding the 0.1% ambiguity presented above has about 0.7% ambiguity. This has the effect of reducing ambiguity compared to about 1% ambiguity that occurs when only the input rule is presented as "flat consonant → double consonant or two flat consonant → lattice sound".

Here, "ㅅ" has only double consonants (hard consonants) and no lattice sound. Therefore, it is possible to apply the technique proposed by the applicant ("ㅅ → ㅆ or ㅅㅅ → ㅆㅅ or ㅅㅆ → ㅆ"), according to the push of the [ㅅ] button, and in this way, the case of "vowel + ㅆ" Since it is omitted, the sum is 0.972%, and dividing it by half is about 0.5%, so it can be said that there is about 0.6% ambiguity in addition to the 0.1%. Also, there is an effect of reducing ambiguity compared to about 1% ambiguity that occurs when the input rule is only presented as "flat consonant → double consonant or two flat consonant → lattice sound".

Of course, here, in the case of "ㄱ", pressing of the [ㄱ] button 4 times is treated as an absolute "ㄲ", and in the case of a flat consonant in which two consonants cannot be finalized, 4 times pressing of the flat consonant button is treated as "2 flat consonants" (Ex. "C → ㄸ → ㅌ → ㄷ c") If you apply additionally, there will be only 0.1% ambiguity as explained as the 4th press of all flat consonant buttons is treated as an absolute double consonant. .

In the applicant's earlier application, "3+ other input method" and its improvement case were presented. In the existing repeat selection method, when [xyz ...] is arranged on a button (including both explicit arrangement or implicit association), the first "x" is input by pressing the button once, and the second Arranged "y" is input by pressing the button 2 times, and the 3rd arrangement "z" is input by pressing the button 3 times, ... n-th arranged alphabet is the button n times It is entered by pressing. It is natural to input by pressing the alphabet (eg "x") arranged on a specific button once (same as on the keyboard), and the second arranged alphabet and the rest of the alphabet are pressed twice or more Since the input is pressed, the existing repetitive selection method may be referred to as "2+ other input method".

The summary of the invention is as follows. In summary, the method suggested in "29.3 Improvement of Prior Application and Optimization of Korean Consonant Input" is due to repeated pressing of [xyz ...] buttons arranged with "x", "y", "z", ... It is the same as "x → xx (corresponding to'ㄱㄱ') or z (corresponding to'ㄲ') → y (corresponding to'ㅋ') → z (corresponding to'ㄲ') → ...". As the double consonant finalization impossible flat consonant button described in the present invention is continuously pressed, "c → ㄸ → ㅌ" is the same as "x → y → z". Therefore, "c → ㄸ → ㅌ → ㄷ" is the same as "x → y → z → xx". This is useful for configuring the input system so that "x", "y", and "z" are arranged in a button and "x" is input by pressing the button once. In general, "x" is the most frequently used. Because there are many. Therefore, it has an advantage that it can be easily understood by existing users to input "x → y → z" according to the repeated press of the button according to the repeated selection method, while there is a disadvantage that it is difficult to enter "xx". The number of alphabets arranged (or related) to the button + 1" by pressing the button, you can enter 2 alphabets (that is, "x") entered by pressing the button once (that is, "xx"). It makes sense. The application of "c → ㄸ → ㅌ → ㄷ" to the [c] button can be applied equally to flat consonants (ie, "c", "ㅂ", "ㅈ") that cannot be finalized. For this, it can also be applied to flat consonants (ie, "ㄱ", "ㅅ") that can be double consonants. For convenience, it is recommended to input 2 alphabets by pressing the button once by pressing the "number of alphabets arranged (or related) to the button + 1", for convenience, "how to enter 2 alphabets" I will call it.

"Arrangement number over 1 pressed 2 alphabet input method" is when the button has 2 alphabets arranged or associated with it (that is, the [xy] button in which "x" and "y" are arranged) (eg "ㅅ" and "Y"). It is apparent that only "ㅆ" can be applied equally to an arrangement or association). For example, it can be applied to a hibernating 10-* keypad. In other words, it becomes "x → y → xx" as the button is pressed, and "xx" is input by pressing the button "number of arrays or related alphabets (2) + 1" times. When applied to Korean, in the initial consonant, the "conventional" circular toggle repetitive selection method is applied (ie, "x → y → x → y → x → ...") as the button is repeatedly pressed. It is also possible to apply the above invention only when it is input as a consonant. When "x" is the final consonant, the second "x" of "xx" is the initial consonant of the next letter.

If you generalize and express "Array number over 1 press 2 alphabet input method", "N" (N=1 or a natural number greater than 1) alphabets A_1, A_2, A_3, ... A_N are arranged or related to the button. When the button is pressed once, the first arrangement or associated alphabet A_1 is recognized, when the button is pressed N times, the Nth arrangement or associated alphabet A_N is recognized, and when the button is pressed N+1 times Two A_1 are recognized.

It is obvious that the "Arrangement Number of Over 1 Press 2 Alphabet Input Method" suggested in the present invention can be applied not only to the keypad of Fig. 10-*, but also to all other keypads and keyboards of computers.

29.6 Optimization of input by continuous pressing of flat consonant buttons

In the above "29.5", "c", "ㅂ", "ㅈ" double consonants (i.e., ㄸ, ㅃ, ㅉ) are not used as final consonants, so for convenience in the present invention, they are named as "double consonant final impossibility flat consonants" . And only "ㅂ" and "ㅈ" out of "ㄷ", "ㅂ", and "ㅈ" are used as the second letter (ex. ㅂ, ㅈ) constituting the double support (ex. ㄼ, ㄵ). The double consonants of "ㄱ" and "ㅅ" (ie, ㄲ, ㅆ) are used as a final consonant, so for convenience, we named it "double consonant final possible flat consonant". Both "ㄱ" and "ㅅ" are used as the second letter of the double base (eg ㄺ, ㄳ).

When the first consonant of the next letter appears after the final consonant in the double-beol-type automata of Korean Hangul, a complex phenomenon can occur. In the case of "Eolsu", a case (29.3) was shown in which "?d" could be entered, then "?dㅅ" and then "Eolsu". Hereinafter, a state that changes mainly after a flat consonant is input as a final consonant is described as an example. In the case where a flat consonant is input as an initial consonant, there is no complexity, so the acyclic or cyclic processing suggested in the previous application may be applied.

Since the double consonant has two flat consonants, it can be cognitively natural to input it by pressing the flat consonant twice. However, in this case, it is not possible to guarantee perfect Hangul input with continuous pressing. In the present invention (29.6), an input method capable of inputting a double consonant by pressing a flat consonant twice while being cognitively natural and minimizing ambiguity is proposed.

In describing the embodiment of the present invention, even if the keypad shown in Fig. 10-* is mainly described as an example, the conventional 2 beolsik keyboard (computer keyboard), short vowels keyboard ('ㅑ','ㅕ','ㅛ' in the 2 beolsik keyboard, It is obvious that it can be applied to all keyboards such as the keyboard without'ㅠ'. A flat consonant is input as a final consonant, and then the same button is pressed consecutively to present an example that leads to the initial consonant of the next letter. The first letter previously entered is mainly "A".

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 us look at the case of inputting a double consonant by inputting a flat consonant twice. In a situation where a neutral vowel is entered (eg,'ga'), if "c" is entered, it becomes "trapped", and if "c" is entered again, it can be "trapped" or "gaㄸ". Treatment as "contained" and treatment as "kaㄸ" have already been proposed in the applicant's earlier application (29.5).

Go → trap → go

Based on the actual frequency of use, it was suggested in the applicant's earlier application that it is advantageous to treat it as "gaj". In addition, in the earlier application, "ㄸ" and "ㅌ" are associated with the [c] button in the drawing 10-*, so if "c" is entered once more in the "ga" state, it becomes "the same" and "c" is once It was suggested that more input would become "trapped". The same is true for "ㅂ" and "ㅈ".

Ga → Trapped → Gaㄸ → Same → Trapped

A → Ga → Gaㅃ → Repay → Gaㅂ

Go → Go → Go → Go → Go

Among the flat consonants that cannot be double consonants, "ㅂ" and "ㅈ" can be used as the second letter of the double support, such as "ㄼ" and "ㄵ". Looking at this case based on Fig. 10-*, it is as follows.

Go → ?E → Go → ?H → ?Eㅂ

Liver → ?C → Liver → Liver → ?Cㅈ

Looking at the flat consonants capable of double consonant finalization based on Fig. 10-*, they are as follows.

A → each → ?A → ?J → each a

↘ (Enter a vowel (ex. ㅡ)) → Gaoff

Go → go → go → go → go

Go → go → go → go

↘ (enter vowel (ex. ㅡ)) → katsu

Angle → ?B → Angle → ?Bㅅ

The contents presented in the applicant's earlier application (29.5) are summarized based on Figure 10-*. Hereinafter, an example of optimizing the input of each letter for the matters suggested in the applicant's prior application is shown.

In the following, the consonant "XY" is expressed, 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 Korean Hangul, it can be seen that the cases of "ㄷㄷ", "ㅂㅂ", and "ㅈㅈ" are 0.015%, 0.071%, and 0.03%, respectively, as 0.116%. In addition, only 0.055% of cases appearing as "ㅅㅅ". The frequency of the final consonant and initial consonant of "ㄷㄷ", "ㅂㅂ", "ㅈㅈ", and "ㅅㅅ" after the letters ending in vowels (eg'Ga','I','Da',...) In all, it is only about 0.171%. On the other hand, the frequencies of "ㄸ", "ㅃ", "ㅉ", and "ㅆ" appearing as initial consonants after the letter ending with a vowel were 0.44%, 0.144%, 0.169%, and 0.219% respectively, and 0.972% was approximately 1 It is close to %. Therefore, for "c", "ㅂ", "ㅈ", and "ㅅ", it can be seen that it is advantageous to treat the paired consonants of "c → ㄸ → ㅌ" as absolute diconsonants as in the applicant's earlier application (29.5).

When a flat consonant is pressed four times, the two flat consonants are not recognized as being recognized, but are processed in an acyclic manner.

A → Trapped → Gaㄸ → Equal (End of cycle) → Equal

A → A → Gaㅃ → Repay (cycle end) → Repay

A → GY → G A → 갗 (cycle end) → 갗ㅈ

If you see "flat consonant → double consonant → lattice sound" as one cycle, and treat it as acyclic, you can enter "ㅌㄷ", "ㅍㅂ", and "ㅊㅈ" by pressing each button 4 times. In the following, unless absolutely necessary, the time of "cycle end" is not necessarily indicated. The frequencies in "ㅌㄷ", "ㅍㅂ", and "ㅊㅈ" are 0.064%, 0.004%, and 0.002%, respectively, which is 0.07%. 0.07% is a little less than 0.116% when it comes out as "ㄷㄷ", "ㅂㅂ", "ㅈㅈ", but both frequencies are very low. Nevertheless, the reason for suggesting the acyclical treatment is that the lattice sound is input by pressing the flat consonant button 3 times, so it is cognitively more natural that "lattice + flat consonant" is input by pressing the flat consonant button 4 times. It is because it is awesome.

Some examples of recursive processing are as follows.

Go → trapped → go → same → trapped

A → A → A → Repay → A

Go → Go → Go → Go → Go

Cognitively, press the [C] button 3 times to input "ㅌ" and then press the [C] button once more to recognize "C", so you can enter "C" by pressing the [C] button 4 times. It is cognitively natural to the user that processing with is more natural than processing in a circular manner. If it is shown that it is processed in a non-circulating manner when it is pressed more than 5 times, it is as follows.

Ga → Trapped → Gaㄸ → Equal → Equal → Equal → Equal → Equal

A → A → Gaㅃ → Repay → Repay → Repay → Repay → Repay

Ga → Gae → Gaㅉ → 갗 → 갗ㅈ → 갗ㅉ → 갗ㅊ → ?Oㅊㅈ

The case where the plain consonant can be combined with the final consonant of the previously inputted letter to form a double support is as follows.

Liver → ?C → Liver → Liver → ?Cㅊ (Cycle ends. Press 4 times ='ㅈㅊ')

or

Liver → ?C → Liver ㅉ → Liver ㅊ (cycle end) → Liver ㅈ (non-circulating type. Press 4 times ='ㅊㅈ')

You can enter "ㅊ" by pressing the [ㅈ] button 3 times, and "ㅈㅊ" corresponds to pressing the [ㅈ] button 4 times. In the above case, "ㅈㅊ" is recognized by pressing the [ㅈ] button 4 times. It has a cognitively good feature. However, since the actual frequency of use is 0%, pressing the [ㅈ] button 4 times (when pressed in excess of the number of consonants arranged or associated with the button) is not treated as "ㅈㅊ". It is desirable. As shown in the above example, the cycle node may vary depending on the situation (whether the flat consonant button is pressed after the final consonant that can be combined into a double support,...) and how the input rule is defined.

Likewise, we will look at "ㄺ" which is a double support by combining with "a", which is a flat consonant with double consonants.

Go → 갉 → go → go → 갉ㅋ (Cycle ends. Press 4 times ='ㄱㅋ')

or

Gal → 갉 → galㄲ → galㅋ (cycle end) → galㅋㄱ (non-circulating type treatment. Press 4 times ='ㅋㄱ')

In Figure 10-*, only "ㅅ" and "ㅆ" are associated with the [ㅅ] button. As explained in the applicant's earlier application (29.3), it was explained that it can be "ㅅ → ㅆ or ㅅㅅ → ㅆㅅ or ㅅㅆ → ㅆㅆ" by pressing the [ㅅ] button. Actually, "ㅆㅅ" is used relatively many times (frequency 0.375%) such as "I did", "I went", "I came", ... in terms of frequency of use, so pressing the [ㅅ] button 3 times as "ㅆㅅ" It is much more natural and cognitively valid. Likewise, in the case of "?B→...", it is possible to input "ㅅㅆ" in the form of 3 "ㅅ" by pressing the [ㅅ] button 3 times. In the case of "ㅅㅅ", it is 0.055%, and in the case of "ㅅㅆ", it is 0.003%. Since both are almost insignificant, it can be processed in a cognitively valid direction (input'ㅅㅆ' by pressing the [ㅅ] button 3 times). have.

Go → Go → Go → Go → Go (Prior application 29.3)

↘ (Enter a vowel (ex. ㅡ)) → Gods (Prior application 29.3)

↘ (Enter a vowel (ex. ㅡ)) → Katsu (first application 29.5)

↘ GOD (Invention. Press 3 times =-'ㅅㅆ')

Each → ?B → Each → ?B (Prior application 29.5)

↘ ?Bㅆ (Invention. Press 3 times ='ㅅㅆ')

If the [G] button is pressed once more in the "Got" state, it may be treated as "Go", but since the frequency of use of "Got" is 0%, there is no need to treat it as "Got". When the [ㅅ] button is pressed 3 times after the letter ending with a vowel, the frequency of "ㅅㅆ" is 0.055%, whereas the case of "ㅆㅅ" is much higher as 0.375%, so it is treated as a non-circular expression and "ㅅㅆ" It is reasonable to make sure that "not" is recognized.

Go → Go → Go (cycle end) → Go

And actually, the cases in "ㄳㅆ", "ㄽㅆ" and "ㅄㅆ" are 0%, 0%, and 0.02% respectively. Therefore, if it is not treated with "ㄳㅆ" and "ㄽㅆ" that are not actually present, but in a non-circular way, it becomes as follows. After the letter ending as a vowel, it is treated as "ㅆㅅ" in the same way as when the [ㅅ] button is pressed three times, so that a unified and consistent feeling of use can be provided to the user.

Each → ?B → Each ㅆ (cycle end) → Each ㅆㅅ

Go → ?F → Go (cycle ends) → Go

If it is processed in a circular way, it becomes:

Angle → ?B → Angle → ?B

Go → ?F → Go → ?F

However, since "ㅄㅆ" like "cheap" is at least 0.02%, it is processed to be 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. If you see it schematically, it is as follows.

A → Value → A → Value (End of cycle)

Based on Figure 10-*, the frequency of "ㄵㅊ", "ㄳㅆ", "ㄽㅆ", and "ㄺㅋ" is 0, while forming a double support by combining the final consonant of the previous letter with the final consonant. %, and only "ㅄㅆ" has a meaningful frequency of use. The above invention is shown in contrast to the applicant's earlier applications (29.3, 29.5).

A → Value → Value ㅆ → Value ㅆ → Gap (Refer to the case of'Eolsu' in previous application 29.3)

A → Value → A → Value ㅅ (first application 29.5)

In the case of "aㅆ", "ㄹㅆ" and "ㅂㅆ", the sum of 0.023%, 0.171%, and 0.017%, respectively, is 0.21%. On the other hand, the case of "ㄳㅅ" and "ㄽㅅ" is 0% each, and the case of "ㅄㅅ" is only 0.02%. In the earlier application (29.3), "ㄳㅅ", "ㄽㅅ", and "ㅄㅅ" with no or relatively very little use were processed by pressing the [ㅅ] button twice, and the relatively frequent "aㅆ", "ㄹㅆ" ", "ㅂㅆ" 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 the "ㅄㅆ" was not processed by pressing the [ㅅ] button three times. However, in the present invention, while relatively more frequent use of "ㄱㅆ", "ㄹㅆ" and "ㅂㅆ" are processed by pressing the [ㅅ] button twice, you can naturally process "ㅄㅆ" by pressing the [ㅅ] button three times. There is an advantage to be able to.

Even if not necessarily mentioned in other parts of the present invention, if the input rule is not defined such as "?Fㅅ" (including other similar cases), input up to "?F" and then predetermined means (eg, the user finishes the syllable). It is obvious that it is possible to end the character input by pressing the means and enter "ㅅ".

Next, when vowels are entered after "A → each → ?A", it is a question of whether to treat as "ㄱㄱ" (first application 29.3) or as "ㄲ" (first application 29.5).

Those appearing as "ㄱㄱ" are 1.096% and occupy a relatively very large frequency. And it is 0.859% that "ㄲ" appears as an initial consonant after a letter that ends with a vowel. In Korean, about 54% of letters without a final consonant and 46% of letters have a final consonant. Therefore, the frequency of letters without a final consonant (ex. 0.859%) is 54%, and the frequency of letters with a final consonant. (Ex. 1.096%) should be considered as the proportion of 46%. Until now, since the two are roughly half and half, the comparison was simply done without applying the weights (54%, 46%), but here, the comparison is as follows by considering the weights (54%, 46%) more precisely.

46% of 1.096% = 0.504 in the case of "ㄱㄱ"

In the case of vowel + initial "ㄲ", 54% of 0.859% = 0.46%

Since even a little "a" is more frequent, it is slightly more advantageous to treat it as "a", but it can be seen that there is little difference between the two. Therefore, one of the applicant's earlier applications (29.3, 29.5) can be applied. As suggested in the previous application (29.3) of the applicant based on drawing 10-*, the [a] button can be processed as "ㄲ" or "ㄱㄱ" 2 times, and pressing the 4 times can be treated as an absolute "ㄲ" I can.

A → Each → ?A → ?J → ?A → (Enter a vowel (ex. ㅡ)) → Gao

↘ (Enter a vowel (ex. ㅡ)) → each

Furthermore, when the cycle ends (that is,'ㅋ' is entered in the cycle), "ㄱ" can be combined with the last consonant x (ex. ㄹ) of the first letter. It may be treated or may be treated in a non-circulating or circulating manner. However, since the frequency of "ㄺㅋ" is 0%, it is preferable not to treat it as "ㄱㅋ".

Go → 갉 → go → go → 갉ㅋ (Cycle ends. Press 4 = recognized as'ㄱㅋ')

or

Gal → 갉 → galㄲ → galㅋ (cycle end) → galㅋㄱ (non-circulating type treatment. Press 4 times ='ㅋㄱ')

Since "ㄾ" and "ㄿ" can be used as separate double feet, it is preferable to be "ㅌㄷ" and "ㅍㅂ" instead of "ㄷㅌ" and "ㅂㅍ" when pressed four times.

Gal → gal c → gal → ?G (cycle end) → ?G

Go → ?E → Go → ?H (Cycle end) → ?H?

Processing the [a] button 4 times as "ㅋㄱ" rather than "ㄱㅋ" (in this embodiment, input as'ㄺㅋ') is "ㅌㄷ" (in this embodiment, it is input as'ㄾㄷ'), It is consistent with what is recognized and processed as "ㅍㅂ" (in this embodiment, it is entered as'ㄿㅂ'). In addition, real users often use expressions such as "ㅋㅋ", and there is an advantage of being able to enter "ㅋㅋ" by pressing the [ㄱ] button 6 times in a row after "go".

A schematic view of the application of the applicant's prior application (29.5) to the continuous pressing of the [a] button based on Figure 10-* is as follows.

A → each → ?A → ?J → each a (first application 29.5)

↘ (Enter a vowel (ex. ㅡ)) → Gaoff

The processing as described above has the advantage of maintaining consistency in that two presses of the "c", "ㅂ", "ㅈ", and "g" buttons are always processed as double consonants in the present invention. However, as suggested in the present invention, inputting "c", "ㅂ", "ㅈ", and "ㅅ" twice in succession among flat consonants with a pair of consonants is always processed as each pair of consonants, " ㄱㄱ" (eg, final consonant and initial consonant in'country') cognitively always have 2 "ㄱ", so it may be more desirable to process the 2nd push of [ㄱ] button as "ㄱㄱ" have. If the [ㄱ] button is pressed 4 times after a letter (eg,'gam') that ends with a final consonant (eg'ㅁ') that cannot be combined with a double support, it should be "gamㄱㄱ". However, the 4th push of the [a] button is to process the transition from the final consonant to the initial consonant, so if the 1st push is recognized as a first consonant, as in the above case (sense + a...) It is reasonable to see the cycle until it is pressed 3 times. Again, this means that cycle nodes can vary slightly depending on the situation or perspective.

In addition, it is obvious that it can be entered in combination with a vowel button such as "ㄲ = ㄱㅣㅣ" and "ㅋ = ㄱㅡㅡ" suggested in the applicant's earlier 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. ㅂ) means that when it is possible to form a double support by combining with the preceding final consonant It means that it is input as a base (e.g. ㅄ), and when it is impossible to achieve a double base, it means that it is input as its own consonant.

The above contents are summarized based on Figure 10-* as follows.

The alphabet that is first arranged or associated with each button is recognized by pressing each button once.

For flat consonants ('ㄷ','ㅂ', and'ㅈ'), the corresponding plain consonant is recognized by pressing one time. Pressing twice is always recognized as a corresponding double consonant. This means that even if a double-consonant non-final consonant is entered twice after the letter ending with a vowel, it is not recognized as "ㄷㄷ". This process is advantageous in terms of cognitive aspects (user's perception that “ㄸ” is input by pressing “C” twice) and frequency of use. Pressing 3 times is always recognized as the corresponding grid tone. Pressing 4 times is recognized as the corresponding lattice sound and the corresponding flat consonant. This is also an optimized result by synthesizing both the cognitive and practical aspects as described above.

"ㅅ" and "ㅆ" are associated or arranged in the [ㅅ] button. By pressing the [ㅅ] button once, "ㅅ" is recognized. Pressing 2 times is always recognized as "ㅆ". This means that after the [ㅅ] button is pressed twice after the letter ending with a vowel, it is recognized as "ㅆ", and even if a vowel is entered again, it is not "ㅅㅅ" but is recognized as the initial consonant "ㅆ", and also "ㅅ" Even if "ㅅ" is pressed twice after the letter that can be combined with a final consonant (eg,'ㄱ'), "ㅅㅅ" is recognized, and as a result, "ㄳㅅ" is always recognized as "ㅆ". Meaning. Pressing the [ㅅ] button 3 times is recognized as "ㅆㅅ". This also means that even if "ㅅ" is pressed 3 times after a letter that ends with a final consonant (eg,'ㄱ') to which "ㅅ" can be combined, it is recognized as "ㅆㅅ" rather than "ㄳㅆ". However, if the [ㅅ] button is pressed 3 times after the letter ending with the final consonant "ㅂ", it is recognized as "ㅅㅆ" and the result is preferably "ㅄㅆ".

There are two possible treatments for "a". Pressing the [a] button once is recognized as "a". Pressing the [ㄱ] button twice is recognized as "ㄲ" or "ㄱㄱ". Recognized as "a" can be mentioned several things. If the [ㄱ] button is pressed twice after the letter ending with a vowel, it becomes the final consonant "ㄲ", but when the next vowel is input, it is recognized as "ㄱㄱ", and the final consonant that "ㄱ" can be combined (eg. ㄹ) When the [ㄱ] button is pressed twice, it means that "ㄱㄱ" is recognized and the result becomes "ㄺㄱ". Pressing the [ㄱ] button 3 times is recognized as "ㅋ". And pressing the [ㄱ] 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 "ㄱㄱ".

The above presented a comprehensively optimized processing when inputting double consonants and lattice sounds by continuously pressing the same flat consonant button in consideration of both the cognitive and practical aspects based on Fig. 10-*. Although described based on Figure 10-*, the same can be applied in similar cases.

In the above, another processing by pressing the [a] button is as follows. However, as in the detailed description of the present invention, the technique presented in the above summary is 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 a final consonant, it does not become "ㄱㄱ". Pressing the [ㄱ] button 3 times is always recognized as "ㅋ". Pressing the [ㄱ] button 4 times is recognized as "ㄱㄱ".

The contents described in the present invention are summarized as follows.

A method of inputting Korean language on a keypad that has a plurality of buttons, each button has one or more Korean alphabets arranged or associated, and a flat consonant button has a pair of consonants corresponding to the flat consonants and a lattice sound associated or arranged In,

When the button is pressed once, the alphabet that is first arranged or associated with the pressed button is recognized,

The corresponding plain consonant is recognized by pressing one button of the “c”, “ㅂ”, and “ㅈ” buttons, which are non-double consonants.

The corresponding double consonant is recognized by pressing the same button twice in succession among the "c", "ㅂ", and "ㅈ" buttons,

The corresponding grid sound is recognized by pressing the same button three times in succession among the "c", "ㅂ" and "ㅈ" buttons,

The corresponding grid sound and the corresponding flat consonant are recognized by pressing the same button four times in succession among the "c", "ㅂ", and "ㅈ" buttons.

"ㅅ" 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,

“ㄱ” is recognized by pressing the “a” button once,

By pressing the "ㄱ" button twice, "ㄲ" or "ㄱㄱ" is recognized, and when vowels are input consecutively after the final consonant "ㄲ", it is recognized as the final consonant and the "ㄱㄱ" of the initial consonant.

"ㅋ" is recognized by pressing the "ㄱ" button 3 times,

"ㄲ" is recognized by pressing the "a" button 4 times, and when vowels are continuously input after the final consonant "ㄲ", it is recognized as the initial consonant "ㄲ"

Korean input method on the keypad, characterized in that

The following may be additionally applied to the above.

In the above,

"ㅅㅆ" is recognized by pressing the "ㅅ" button three times in succession after the letter ending with the final consonant "ㅂ" ('ㅄㅆ' is input in combination with the previously entered final consonant "ㅂ")

Korean input method on the keypad, characterized in that

The following may be additionally applied to the above.

In the above,

Consonants input by pressing the consonant button once include at least consonants of "ㄱ", "ㄴ", "C", "ㅁ", "ㅂ", "ㅅ", "ㅇ", and "ㅈ"

Korean input method on the keypad, characterized in that

The following may be additionally applied to the above.

In the above, the Korean input method on the keypad, characterized in that after the end of the cycle is processed in a non-circulating type

In addition, instead of the [a] button press processing in the above, it is absolutely recognized as "ㄲ" by pressing the [a] button 2 times, "ㅋ" is recognized by pressing the 3 times, and pressing the [a] button 4 times It is possible to apply that "a" is recognized as a burden.

Next, like the 2 beolsik keyboard (computer keyboard) or Google's "short vowel keyboard", press "ㄲ", "ㄸ" and "ㅃ" on the "ㄱ", "c", "ㅂ", "ㅅ", and "ㅈ" buttons respectively. The processing in the case where only ", "ㅆ", and "ㅉ" are related will be described. Google's short vowel keyboard has missing'ㅑ','ㅕ','ㅛ', and'ㅠ' from the computer keyboard, and it is entered as ㅑ = ㅏㅏ, ㅕ = ㅓㅓ, ㅛ = ㅗㅗ, ㅠ = ㅜㅜ. Since it is widely used through the Android market (Google Play Store), drawings and descriptions for the short vowel keyboard are omitted. However, even if described based on the computer keyboard, it is obvious that the technical idea of the present invention can be applied equally to other keyboards.

Currently, treatment of double consonants by double-pressing flat consonants on the existing 2-beol-sik keyboard is shown in many programs. 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 a flat consonant input twice. However, when the user inputs a double consonant, it quickly presses it twice, and when entering a plain consonant no. 2, it does not press it slowly twice. If there is a user who hits 300 to 400 strokes per minute, that user can be considered to be mercilessly pressing quickly at all times. After all, the problem of "ambiguity" traditionally in the 12-button keyboard 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

If the applicant's prior application (29.5) is applied, it becomes as follows. The same is true for other consonants (ie, ㄱ, ㅂ, ㅅ, ㅈ).

Go → trapped → go → trapped

Here, since only two paired consonants corresponding to the flat consonant are associated with the flat consonant button, pressing the flat consonant button 3 times becomes "ㄷ". Cognitively, it is somewhat unnatural to input an even number of consonants by pressing an odd number of times. The perception that it is perceptually natural to the user that the [c] button is pressed twice as "ㄸ" has already been explained in the applicant's previous application (29.3).

As already mentioned, the cases in which flat consonants that cannot be finalized are "ㄷㄷ", "ㅂㅂ", and "ㅈㅈ" are 0.015%, 0.071%, and 0.03% respectively, which is very small as 0.116%. Therefore, pressing the flat consonant button 3 times can be processed as "ㄷㄸ" as follows.

Go → trapped → go → trapped

A → Gap → Gap → Gapㅃ

Go → Go → Go → Go

When the flat consonants (ex. ㅂ, ㅈ) that can be combined with the double support following the final consonant are pressed as follows.

Go → ?E → Go → ?Eㅃ

Liver → ?C → Liver → ?Cㅉ

This is already described in the present invention is the same as the case of "gal → 갉 → galㄲ → galha → kk" already presented in the present invention. In terms of the frequency of use, the cases in which they appear as "ㄷㄸ", "ㅂㅃ" and "ㅈㅉ" are only 0.002%, 0.001%, and 0%, respectively. In addition, "ㄼㅃ" and "ㄵㅉ" are 0% and 0.002%, respectively. If all five cases are combined, it is 0.005%. It is much less than 0.116%, which is the case with "c-", ""-", ""-". Nevertheless, it is suggested that the above can be processed in terms of "cognitive correspondence" for consonants (eg, ㄷㄸ) consisting of three specific consonants.

The above is the number of letters associated with a specific button when the previously entered final consonant is combined with the pressed plain consonant to form a double support even if there is a letter ending as a vowel or a final consonant (for example, a plain consonant and two double consonants). ) When pressed, it is recognized and processed as a "flat consonant double consonant".

In the case of "ㅆ", since it can be a final consonant, if the [ㅅ] button is pressed consecutively after the vowel, it can be processed as presented in the applicant's earlier application and the present invention. For example, it becomes like "go → go → go → go". However, if the [ㅅ] button is pressed three times in succession after the letter ending with the final consonant sound (eg, "ㅂ", "ㄱ", "ㄹ") that "ㅅ" can be combined with a double support, It can be processed as "A → Value → A → Value". The case of "ㄲ" is the same as the case of "ㅆ". For example, when the final consonant is combined with a double support, it can be treated as "gal → 갉 → galㄲ → 갉ㄲ". All three presses of the flat consonant button are recognized and processed as "ㅅㅆ" or "ㄱㄲ".

All of the above are cases in which the flat consonant button is pressed as a final consonant, and in the case of the initial consonant when the flat consonant button is pressed in the initial state, it can be simply processed in an acyclic or cyclic manner as previously suggested in the previous application.

This is generalized and expressed as follows. When A_1 is a flat consonant that cannot be finalized, and N Korean consonants such as A_1, A_2, A_3, ... A_N are associated with one button, pressing N times is recognized as a consonant corresponding to the number of presses. , "N+1 times" means to recognize and process the press as "A_1 A_N". As already explained, "A_1 A_N" is a final consonant and an initial consonant, such as "XY". Recognized A_1 is a final consonant or is combined with a previously input final consonant to form a double support, and the recognized A_N is processed as an initial consonant.

However, in the case of a flat consonant in which A_1 is a double consonant, it is the case that the corresponding button is pressed consecutively after the letter ending as a vowel or the letter ending as a final consonant that can be combined with the input plain consonant to form a double support, and A_1 is a pair. In the case of a consonant finalizable flat consonant, the button is pressed consecutively after the letter ending with a final consonant that can be combined with A_1 to form a double support.

This is summarized as follows.

It has a plurality of buttons, and the button contains N (N is a natural number including 1 or 1) Korean consonants (A_1, A_2, ... A_N) arranged or associated with Korean by repeat selection method on the keypad. In the input method,

The A_1 is a flat consonant that cannot be double consonant finality, and after a letter ended as a vowel or a final consonant that can be combined with A_1 to form a double support is input,

or

A_1 is a double-consonant final possible flat consonant, and after a final consonant that can be combined with A_1 to form a double support 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,

When the button is pressed N+1 times, "A_1 A_N" is recognized.

Korean input method on the keypad, characterized in that

Additionally, in the above, A_2 may further include a double consonant.

29.7 Resolving ambiguity when inputting dropped consonants (eg "ㅎ") by repeated pressing

In the applicant's earlier application (29.4), it was suggested to input "ㅎ" which is related or arranged in the [ㆍ] button by pressing the [ㆍ] button three times based on Fig. 10-*. In some cases, it has been explained that the following can be achieved by processing one push of the [ㆍ] button as "ㅏ" and the second push of the [ㆍ] button as "ㅓ".

A → go → go → a ha → red → 겋

If you press "ㆍ-" in "Red" state to enter "A" in the above, it will be "Great". It was explained in the previous application (29.4) that there is no problem in becoming a "no" by pressing "ㆍ-" in the "?" state.

It has been explained that when "ㅏ" is entered as "ㅣㆍ", it can be processed as follows by continuously pressing the [ㆍ] button.

Ki → Ga → Gya → ?? → red → ?y

Even in this case, "??" If you press "ㆍㅣ" in the state, it will become "good". Likewise, if you press "ㆍㅣ" in the state of "red" to enter "license", it will become "gyahi". The same problem occurs in the case of "symbol" (entered as ㅗ=ㆍ-), as well as "license" as in "sign". In other words, the input value of "Giheo ↔ Gahi" is the same, but there is ambiguity that can appear differently.

In general, as a means to resolve this ambiguity, there are "enter after a predetermined time elapsed" or "press the break button" (the [blank] button can also be used as a break button). In the past, when a predetermined time elapses or when the break button is pressed, the already entered character (eg,'??') is completed, and when "ㆍ-" is entered, it becomes like "??ㅗ". That is, as follows.

Ki → Ga → Gya → ?? → red → ?y

↘ (Prescribed time elapsed or stop button, press ㆍㅡ) → ??ㅗ

However, in the case of the present invention, the state that the already entered character "??" has been input to the final consonant for the elapse of a predetermined time or the press of the break button is maintained, but the pressing of "ㆍ-" is not processed as "height", It should be treated as a "symbol". In other words, the letter combination is not completely terminated by the elapse of a predetermined time or by pressing the break button, but a change (eg,'?? → red') to the already entered "??" for the next input "ㆍㅡ" It is not supposed to give. For convenience, this will be referred to as "determining the input state by the elapse of a predetermined time or pressing the break button" or "determining the input state" for short.

As shown in the example above, if a predetermined time has elapsed or the break button is not pressed, the letter that the [ㆍ] button is pressed consecutively to enter the next vowel after "ㅎ" is input by pressing the [ㆍ] button 3 times. It can be seen that a problem occurs in the case of In the present invention, a technique capable of solving this problem without the elapse of a predetermined time or the pressing of the break button is proposed.

If "ㅎ" is input by pressing the [ㆍ] button 3 times in a row, if the vowel starting with the [ㅡ] button or the [ㅣ] button is input instead of the vowel starting with the [ㆍ] button, there is no problem. none. In other words, if "I" is input in "??", it becomes "Gihi", and if "I" is input from "Red", it becomes "Gahi". There is no problem so far.

Here, after the drop-out consonant "ㅎ" is entered, another alphabet (different consonant) is not entered by pressing the [ㅡ] button twice, so if "ㅣ" is entered once more in the state of "gigi", it can be processed as "deceived". have. By expressing only the change in vowel according to the [ㅣ] button is pressed, it can be expressed as "ㅣ → ㅓ". In the diagram below, the right arrow includes pressing the "ㅣ" button. (In the following, when "ㅣ" is pressed consecutively or "ㅡ" is pressed continuously, (ㅣinput) or (-input) is not indicated separately between arrows)

?? → Giheo → Giheo

If "I" is input once more in the "Gi-He" state, it becomes "Gi-He". (Because ㅔ=ㅓㅣ) To enter "ㅕ", you can enter "ㅕ" by pressing the [ㆍ] button after "ㅓ" entered as "ㅓ". If "ㅕ" is pressed once more while "ㅕ" is recognized, it becomes "ㅖ". This is summarized as follows.

?? → Gihi → Gihe → Gihe

↘ (ㆍInput) → Contribution → Kihye

It is natural that "ㅖ" becomes "ㅖ" by pressing "ㅣ" after "ㅕ" input by "ㅣㅣㆍ" (ie, "ㅓㆍ"). The same is true for processing in the "red" state.

Red → Gahe → Gahe → Gahe

↘ (ㆍInput) → Mask → Gahye

It has been explained in the previous application (29.4) that there is no problem in entering "Gyahe" by pressing "ㆍㅣ" or "ㆍㆍ" in the "?y" state. However, for consistency in use, the above can be applied, and schematically, it is as follows.

?y → Gyahi → Gyahe → Gyahe

↘ (ㆍInput) → Gyat → Gyahye

Next, it shows the case of entering "ㅗ" or "ㅛ" after the consonant (ex. heh) input by pressing the [ㆍ] button 3 times.

remind "??" Pressing the [ㅡ] button twice in the state can be processed as "ㅗ".

?? → gich → symbol

In the above, if only the change of vowel is expressed by pressing the [ㅡ] button, it becomes "ㅡ → ㅗ". In the case of the vowel "ㅗ", since there is no vowel in which "ㅡ" is combined after "ㅗ", the [-] button 3 times can be processed as "ㅛ". Also, for consistency with the case of processing "ㅕ", "ㅗ·" can be treated as "ㅛ". Only one of them may be applied, or both may be applied at the same time. This is shown schematically as follows.

?? → gich → symbol → period

↘ (ㆍInput) → Expiration

If you apply only inputting "ㅛ" with the [-] button 3, it is possible to treat the "ㅗㆍ" being pressed as "ㅘ" as shown in the previous application. If "ㅘ" is then pressed, it will be "ㅙ".

?? → gich → symbol → period

↘ (ㆍInput) → Vaporization → (ㅣInput) → Energy

When "I" is pressed in the above "symbol" state, it becomes "opportunity", when "ㆍ" is pressed in the "opportunity" state, it becomes "evaporate", and when "ㅣ" is pressed in the "evaporation" state, "Gift" do.

?? → Gigh → Symbol → (ㅣInput) → Opportunity → (ㆍInput) → Vaporization → (ㅣInput) → Energy

"??" The input case in the state is shown, but the processing in the "red" state is also "??" It is completely the same as the processing in the state (only the'??' and'ki' are replaced with'red' and'au'), so the explanation is omitted. Likewise the "?R" state and "??" The processing in the state is also exactly the same as the processing in the "??" and "red" states, and thus a description thereof is omitted.

By applying the present invention above, while inputting consonants (eg. ha) arranged together on the [ㆍ] button by pressing the [ㆍ] button 3 times, at the same time, "ㄱ, ㄴ, ㄷ, ㄹ, ㅁ, ㅂ, ㅅ, ㅇ" , ㅈ, ㅎ" By completely arranging 10 consonants (consonant groups) on each of the 10 number buttons, it is possible to utilize the correspondence between numbers and Korean consonants, and to realize perfect Korean input without ambiguity. have.

In the "?y" state, it can be processed as "ㅓ = ㆍㅣ" or "ㅓ = ㆍㆍ", and it can be processed as "ㅕ = ㆍㆍㅣ". However, it goes without saying that even in the "?y" state, the present invention can be applied to input "Gyahe", "Gyagh", "Gyaho", and "Gyahyo".

In the above, a technique 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 input by pressing the [ㆍ] button 3 times, you can enter "ㅓ=ㆍㅣ", "ㅕ=ㆍㆍㅣ", "ㅗ=ㆍㅡ", "ㅛ=ㆍㆍㅡ" as before. there was no problem. However, even when an 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 to input as "lattice = flat consonant-ㅡ", "double consonant = flat consonantㅣㅣ". After this lattice and double consonant, press "ㅡㅡ" or "ㅣㅣ" to input other consonants. If not (in other words, "lattice consonant + ㅡ -" or "lattice consonant + ㅣ"), the vowel input rule suggested in the present invention can be applied as well.

In addition, even if you do not apply the input of "lattice consonant = flat consonant ㅡ" and "double consonant = flat consonant ㅣ", you can enter it by pressing in place, while minimizing ambiguity, so that it can be processed cognitively. I have suggested a way. Therefore, unless it is applied to input the lattice sound and the double consonant using two consecutive presses of "ㅡ" or "ㅣ", the vowel input technique of the present invention can be applied in all cases to provide consistency in use to the user. have. For example, if it shows that the present invention is applied in a state where "each" is entered, it is as follows.

Each → Gag → Go → Bridge

↘ (ㆍInput) → Bridge or add

Each → Go → Go → Shop

↘ (ㆍInput) → Go →

For the input of the remaining vowels that are not illustrated, the existing method using the vowel elements "ㅡ", "ㆍ", "ㅣ" and the vowel input rules suggested in the applicant's previous application (eg ㅢ=ㅡㅣ, ㅚ=ㅗㅣ, ㅘ) = ㅗㅏ, ㅙ = ㅗㅐ = ㅗㅏㅐ, ...) can be applied is as already described in the present invention.

This is summarized as follows.

In a method of inputting a Korean vowel using three buttons arranged in each of the 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 "I" is pressed after the recognized "ㅓ", it is recognized as "ㅔ",

By pressing the "ㅡ" button once, "ㅡ" is recognized,

"ㅗ" is recognized by pressing the "ㅡ" button twice,

If "ㆍ" is pressed after the recognized "ㅗ", it is recognized as "ㅛ" or "ㅘ",

Korean vowel input method on the keypad, characterized by

In addition, the following may additionally be included in the above.

In the above,

When "ㆍ" is pressed after the recognized "ㅗ", it is recognized as "ㅘ",

If "ㅡ" 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 or arranged with the "ㆍ" button are recognized as being pressed 3 times of the "ㆍ" button.

Korean vowel input method on the keypad, characterized by

30. Improvement of delete button handling

30.1 Deletion button processing based on "perception unit"

In the current keypad input technology, the deletion (cancellation) logic in units of graphemes is mainly applied. For example, if you press the "Delete" button while entering "E", it becomes "ㅇ". On the keyboard, when "ㅔ" is input, press the "ㅔ" button once, so it is natural that the last input "ㅔ" is deleted and becomes "ㅇ". However, in the keypad including Figure 4-*, "ㅔ" is input in combination as "ㅓ+ㅣ = ㆍㅣㅣ". For convenience, looking at the process of entering "in" as the vowel input method currently applied by Samsung Electronics, it is as follows. The allegorical arrows indicate that "ㆍ", "I", and "I" are pressed, respectively.

ㅇ → ㅇㆍ → uh → eh

The user recognized and entered "ㅓ+ㅣ". Therefore, the deletion logic for the recognition unit can be applied. When the delete button is pressed in the state of inputting "E", "I" recognized as the last input is deleted and becomes "uh", and when the delete button is pressed again, it becomes "o". If "a" is pressed in the above "uh" state, it will be "hundred".

In summary, the deletion logic is applied to the "cognitive unit" in which the grapheme is combined, not the "character subunit". For some other examples, if you enter "A" as "ㅇㅣㆍㅣ", the user will recognize that you have entered "ㅐ" as "ㅏ+ㅣ", so if the delete button is pressed once in the "A" state, "Ah" It becomes ", and when pressed again, it becomes "ㅇ". If the delete button is pressed in the "ah" state, it may be questionable whether it becomes "i". However, the unit recognized by the user is "ㅏ", and "ㆍ" in "ㅣㆍ" can be seen as not an independent recognition unit.

As a representative example, the example of application of deletion by recognition unit when Samsung Electronics' vowel input method is applied is as follows, and it can be similarly applied to other cases where vowels are input from a keypad. For example, it can be similarly applied to the technique of inputting "ㅏ" with the "ㆍ" button. The 10 basic vowels "ㅏ", "ㅑ", "ㅓ", "ㅕ", "ㅗ", "ㅛ", "ㅜ", "ㅠ", "ㅡ" and "ㅣ" are all one recognition unit. It is deleted by pressing the delete button once. For convenience, only one case is indicated in the case of the same operation as in the existing 2 Beol-Sik keyboard. The right arrow (→) below means that the delete button is pressed, and it is the same in the similar case below.

ㅔ → ㅓ → all deleted

ㅐ → ㅏ → all deleted

ㅏ → all deleted

ㅓ → All deleted

. . .

ㅝ → ㅜ → all deleted (same for the existing 2beolsik keyboard)

ㅞ → ㅝ → ㅜ → all deleted

ㅒ → ㅑ → all deleted

ㅙ → ㅘ → ㅗ → all deleted

Representative recognition units for Korean keypad input may include the following. "ㅔ" is mainly input as a combination of "ㅓ" and "ㅣ". Therefore, "ㅓ" and "ㅣ" can be separate cognitive units. "ㅐ" is mainly entered as a combination of "ㅏ" and "ㅣ". Therefore, "ㅏ" and "ㅣ" can be separate cognitive units. In the case of "ㅙ", it is also input as a combination of "ㅗ", "ㅏ", and "I", so each can be a separate recognition unit. In the case of "ㅞ", it is also input as a combination of "ㅜ", "ㅓ", and "ㅣ", so each can be a separate recognition unit.

30.2 Recombination of the entered characters after pressing the delete button

There may be another application in the deletion logic by pressing the delete button. The following are examples of the application of the 2 Beol-Sik Hangul Automata in PC. The right arrow (→) includes pressing the delete button, and the same is true for the example below.

Ghana → Ghanaa → Ghana → A →. . .

Examples of modified automata that are recently applied to smartphones are as follows.

Ghana → Ghana → Ghana → Gan → A → a

The characteristic is that when the neutral vowel is deleted and only the initial consonant remains, it is combined with the final consonant of the previous letter if it can be the final consonant of the previous letter. In a similar example, if the delete button is pressed once in the "mane", it becomes "". When the above "live" is reached, when "ㄱ" is pressed, it becomes "gan a", and when "ㅣ" is pressed, it becomes "garney". This can be one of the factors that give flexibility in correcting typos. However, the user was psychologically "expecting" to become "Gana" by pressing the delete button in "Ganada", but becoming "Gana" can be a confusing factor. If the user wanted to enter "Gainda", click the delete button once and immediately enter "Da" additionally. However, it can be embarrassing to change it to "Gannad" because it becomes "grainy" that is different from expectations.

Therefore, it presents an intermediate form. For example:

Ganora → Ganoㄹ → Gano → Gob → Go → a

By pressing the delete button continuously, the input token does not break even if the character being input is deleted, and the character can be recombined. When the neutral vowel is deleted, the initial consonant is not combined with the last consonant of the previous character. will be. At the same time, after the delete button is entered, the newly pressed button is combined if it can be combined with the remaining characters. For example, when "o" is pressed in the "gano" state, it becomes "farming", and when "l" is pressed in the "gano" state, it becomes "gano". This may provide flexibility in using the delete button while reducing confusion to the user.

31. Means for removing ambiguity

31.1 Common in English, etc.

For convenience, examples of English are used below, but the same can be applied to other languages.

When applying the repeat selection method (multi-tap method) in Fig. 1-1 (standard English keypad), the input value "222" is explained in the earlier application that there are ambiguities such as "aaa", "ab", "ba", and "c" I did. Previously, there were two main ways to enter "ab" instead of "aaa", "ba", or "c". As described in the previous application, after pressing "2" to input "a" and after a predetermined period of time elapses to confirm "a", you can press "22" to input "b". That is, it is a classification method based on a time delay, and for convenience, it will be referred to as a "time delay method" or a "timer method". Another way is to press "2" to enter "a", then press a certain classification button (eg, [#] button) to confirm "a" and then press "22" again to enter "b". Was to be. That is, it is an artificial method by pressing the classification button, and this is referred to as the "division button method" for convenience.

In the applicant's earlier application (26.1.1), it was pointed out that "acb" can be entered without ambiguity, such as "2 2~22 2~2" ("2~" means long press of the [2] button). . In addition, it is said that the input value "2" for inputting the first "a" can be long pressed. That is, when alphabets arranged (or related) to the same button are continuously input, the first input value for inputting the second and subsequent alphabets (ie, including the third, fourth, ...) is long pressed. If you want to enter "abc", it will be something like "2 2~2 2~22". For readability, a space is inserted between the input values (eg "2", "2~2", "2~22") representing one alphabet (eg "a", "b", "c"). However, the space does not mean anything, and it is the same in the following.

A closer look at this process is as follows. In the iterative selection method, "a" can be input 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 "bbb" and "cc". In the applicant's earlier application, press and hold the first input value of "222" to enter "c" after "a", and then press the first input value of "22" to enter "b" after "c". It was handled as a long press. When alphabets assigned to the same button appear in succession, processing by long pressing the first input value of the next alphabet is referred to as "processing of trailing alphabets" for convenience. More precisely, it may be called "the first (first) button hitting process of the trailing alphabet," but it is simply called "the trailing alphabet hitting process".

Next, as a similar example, an example of entering "cab" by another method is shown. In the earlier application, it was shown that when the alphabets assigned to the same button appear consecutively, the first alphabets can be entered as they were and then can be entered by long pressing the alphabet. However, it shows that the alphabet that appears first can be entered by long hits. For example, when entering "cab", the input value "222~ 2~ 22" can be used. It is entered by long pressing the last input value constituting the preceding alphabet. In the notation "222~ 2~ 22" of the input value, spaces are added to improve the readability of those who read this patent document, and spaces have no meaning. Of course, when entering "cd", you can do something like "2 2 2 3", and there is no need to intervene with a long press. Likewise, when entering "cad", apply a long press only to the input of "c", such as "222~ 2 3", and do not need to use a long press when entering "a". This is because "d" appears after "a", not the alphabet arranged in the same button. Similarly, for convenience, this is referred to as "last (last) button hitting treatment of the preceding alphabet", and more simply called "preceding alphabet hitting treatment".

When the repetitive selection method is applied in this way, when ambiguity is eliminated by using a long hit for the input of the preceding alphabet (eg "ca" to "c"), the last input value should be treated as a long hit, and the trailing alphabet (eg, "ac"). It is important to treat the initial input value as a long hit when removing ambiguity by using a long hit in the input of "c"). The "preceding alphabetical long hitting process" and the "posting alphabetic long hitting process" are not applicable at the same time, but one of them is selectively applied. When implemented as a program, the user can select and use either of them in "Environment Settings".

31.2 Hangul (Old Hangul) input and means of removing ambiguity

In the present invention, a method for inputting all characters including modern Korean and Hangul Gore is proposed. The contents described below are disclosed in advance that the technology is applicable not only to the keypad of Fig. 4-*, but also to other types of keypads and keyboards of a PC.

Figures 4-33(a) to 4-33(c) show Hangul Gore added as Unicode in 2007. In the drawing, the part marked with a yellow background is the newly added letter. All characters in Drawing 4-33(a) ~ Drawing 4-33(c) have been confirmed as Unicode, and Drawing 4-33(d) ~ Drawing 4-33(f) are Unicode v6. It shows that it was registered as 0. Like this, Unicode characters are continuously added through revision. In the present invention, it is suggested that a technique for efficiently inputting Hangul Gore is provided, and a method of expressing Jamo-combined Hangul characters including Hangul Gore in a computer is not the subject of the present invention. The question of how to handle Hangul Gore in a compatible way with Unicode completed Hangul in computers (PCs, smartphones, mobile phones, etc.) will be a "ultra-large national project" that requires additional research. For reference, as a representative method of expressing alphabetically combined Hangul characters including Hangul Gore, the "first tip combination type" is known, and the input of the present invention in any other method (ie, Unicode completion type, first tip combination type, ...) The technology is applicable.

31.2.1 Entering Hangul archaic consonants

In the applicant's earlier application, some methods of inputting Hangul Gore are introduced. An example of inputting Hangul Gore on the keypad in Figure 4-* is as follows. In the present invention, not “numeric button value” (eg, “1**”, etc.) but as “Korean button value” (eg “ㄱㅡㅡ”, etc.) to increase readability and read this document. It is for the convenience of people, and the content is completely the same. First of all, the original technology of inputting "y = xㅡㅡ" or "z = xㅣㅣ" was suggested for input of "y" in the previous application. For example, "ㅋ = ㄱㅡㅡ", "ㅍ = ㅂㅡㅡ" was to enter. In addition, it was shown that even Hangul archetype can be entered by doing something like "ㅸ = ㅍㅡㅡ = ㅂㅡㅡㅡㅡ". For convenience, this will be referred to as "control processing method using collection button". While maintaining the keypad in Figure 4-*, it is possible to naturally input the related Korean archetype consonants. Looking at the similarity with the representative consonant "ㅂ", "ㅸ" may have stronger similarity than "ㅍ", but it gives priority to the input of modern Korean and allows additional Hangul archaic processing.

)은 서로 바뀌어서 구성될 수도 있다. Fig. 4-34(a) shows an example in which modern Korean input is prioritized and even archaic consonants are processed by the control processing method using vowel buttons. Since newly discovered Hangul (Old Hangul) characters are being added to Unicode, 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 pairwise transfer (ㆀ) and the old transfer (

) Can also be configured interchangeably.

In "ㅸ = ㅍㅡㅡ", "y" is "ㅸ" and "x" is "ㅍ". Similarly, it becomes "ㅹ = ㅃㅣㅣ = ㅂㅣㅣㅣㅣ". In the above, the consonant (ex. "ㅋ") displayed on the left under the plain consonant (ex. "ㄱ") is input by a combination of pressing the "ㅡ" button twice, and the consonant (ex. "ㄲ") indicated on the right is "" It can be input by pressing the ㅣ"button 2 times. In the above example, the [-] button or the [-] button may be changed and applied. For "primary combination", the "ㅡ" or "ㅣ" button is pressed twice in succession after the flat consonant, and the "secondary combination" alphabet is the "ㅡ" or "ㅣ" button after the first-order combination. The alphabet that is pressed twice in a row and "3rd combination" is followed by the second combination alphabet and then the "ㅡ" button or the "ㅣ" button is pressed twice in succession. As a result, the "-" or "-" button is pressed four times in succession in the "secondary combination". 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 "

"Wow"

"(And"

"Wow"

Hangul Gore vowels containing ") are not entered by pressing the [ㅡ] button twice and pressing the [ㅣ] button twice, respectively, but by other means (eg long press the [ㅡ] button, long press the [ㅣ] button), respectively). This is possible if you type. If "

"Wow"

If you input "by pressing the [ㅡ] button twice and pressing the [ㅣ] button twice, respectively, you must say "y = x + (maximum number of possible repeated presses + 1 time)", so "ㅋ = ㄱㅡㅡㅡ" Becomes like this."

= ㄱㅡㅡ", and the vowel "ㅡ" does not appear three times in succession after a consonant in Hangul Gore, so the "maximum number of possible repetitions" is normally 2 times as the maximum number of conjugated Korean letters. If this is applied, the number of times "ㅡ" or "ㅣ" is combined in Fig. 4-34(a) is 3 times each.

", "

", ...)에 대해서만 [ㅡ]버튼 또는 [ㅣ]버튼의 3회 눌러짐의 조합으로 입력할 수 있는 기술은 아래 "한글고어 모음의 입력 및 모호성 제거 수단" 에서 따로 설명한다. 이하에서는 1차조합되는 알파벳(예. "ㅋ")은 [ㅡ]버튼 또는 [ㅣ]버튼 2번 눌러짐이 적용되고, 2차조합 또는 그 이상 차수로 조합되는 알파벳은 [ㅡ]버튼 또는 [ㅣ]버튼의 3번 눌러짐이 적용되는 것으로 사례를 제시한다. In the future, there may come a time when Hangul Gore will be 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 entered by pressing the [ㅡ] button or the [ㅣ] button twice. "

", "

A technique that can be input only for ", ...) by a combination of pressing the [ㅡ] button or the [ㅣ] button three times will be described separately in the following "Input of Hangul Gore Vowels and Ambiguity Removal Means." For the first order combination (ex. "ㅋ"), the [ㅡ] button or [ㅣ] button is pressed twice, and the second order combination or higher order is the [ㅡ] button or [ㅣ] An example is presented that the button is pressed three times.

"은 유니코드에는 포함되어 있지 않으나, 일부 프로그램에서는 사용되고 있다. 먼저 여린히읗 "ㆆ = ㅇㅡㅡ" 로 입력한 후, [ㅣ]버튼을 2번 누르면 "

"가 되고, [ㅡ]버튼이 한번 더 눌러지면 (즉, "ㆆㅣㅣㅣ = ㅇㅡㅡㅣㅣㅣ") "

" 가 인식될 수 있다. 또는 여린히읗 "ㆆ = ㅇㅡㅡ" 로 입력된 후, [ㅡ]버튼이 3번 눌러지면 (즉, "ㆆㅡㅡㅡ = ㅇㅡㅡㅡㅡㅡ") "

"로 처리될 수 있다. 옛이응과 쌍이응의 입력사례를 더 보이면, 쌍이응 "ㆀ = ㅇㅣㅣ"로 입력되고, 옛이응 "

= ㆀㅣㅣㅣ = ㅇㅣㅣㅣㅣㅣ" 로 될 수 있다. "

"Is not included in Unicode, but is used in some programs. First, enter "ㆆ = ㅇㅡㅡ" and press the [ㅣ] button twice.

"It becomes, and when the [ㅡ] button is pressed once more (that is, "ㆆㅣㅣㅣ = ㅇㅡㅡㅣㅣㅣ") "

"Can be recognized. Or, after entering as "ㆆ = ㅇㅡㅡ", if the [ㅡ] button is pressed 3 times (that is, "ㆆㅡㅡㅡ = ㅇㅡㅡㅡㅡㅡ")"

It can be processed as ". If the input cases of old and double-transfer are more shown, they are input as "ㆀ = ㅇㅣㅣ" and old-transfer "

= ㆀㅣㅣㅣ = ㅇㅣㅣㅣㅣㅣ".

In the current PC keyboard input, "ㅸ" is a combination of "ㅂ" and "ㅇ", "ㅱ" is a combination of "ㅁ" and "ㅇ", and "ㅹ" is a combination of "ㅃ" and "ㅇ" Sometimes it does. Since this can also be applied to keypad input in the same way, such an alphabet (eg, "ㅸ") is put in round brackets in Figure 4-34(a). In this case, ambiguity may arise, which can be solved by the method suggested below.

"를 허용하지 않을 경우) 또는 "ㆅ = ㅎㅣㅣㅣ" ("

"를 허용할 경우)로 입력할 수 있다. In the case of the 4-* keypad, "ㅎ" is explicitly or implicitly assigned to the [0] button, but you cannot enter "ㅎ" by pressing the [0] button once. (Except for special cases presented in the earlier application) It is revealed that in the earlier application, you can enter "ㅎ = ㆍㅡㅡ" or "ㅎ = ㅇㅡㅡ". In terms of logic, it may feel natural to enter "ㆆ = ㅇㅡㅡ", but it has been revealed that modern Korean can be given priority to "ㅎ = ㅇㅡㅡ". In Fig. 4-34(a), the [ㅎ] button is expressed as if there is a separate button, but if it is impossible to input “ㅎ” with one press of a button as in the keypad in Fig. 4-*, it is the same as suggested in the previous application. Likewise, you can enter "ㅎ" as a combination of buttons. If you say "ㆆ = ㅇㅡㅡ", you can do it with "ㅎ = ㆍㅡㅡ" or "ㅎ = ㆍㆍㆍ". "ㆅ = ㅎㅣㅣ"("

"If not allowed) or "ㆅ = ㅎㅣㅣㅣ"("

"If allowed) can be entered.

Fig. 4-34(b) shows a case in which the remaining consonants are input by repeatedly pressing the flat consonant button (that is, by the repeat selection method). In Figure 4-34(b), it is obvious that the order of the alphabet input by pressing the button twice or more can be appropriately changed. Similarly, in Figure 4-34(b), it is expressed as if "ㅎ" is entered by pressing the [ㅎ] button once, but as in the keypad in Figure 4-*, "ㅎ" is entered by pressing a certain button. If this is not possible, you can enter "ㅎ" as a combination of buttons as suggested in the previous application. For example, if you enter "ㅎ = ㆍㅡㅡ", it becomes "ㆅ = ㆍㅡㅡ ㆍㅡㅡ" expressed as "pressed twice" in Figure 4-34(b).

Looking at Fig. 4-34(a) and Fig. 4-34(b), the basic alphabet (example: applying "control processing method using a collection button" and applying "3+ other input method") is different. It can be seen that there is a commonality of composing alphabets related to plain consonants in a consistent form. Looking at the characteristics of the composition presented in Fig. 4-34(b), in order to process the case where the same flat consonant appears consecutively as the final consonant and the initial consonant in modern Korean by applying the "3+ other input method" The biggest feature is that it becomes two flat consonants when the button is pressed twice in succession. Of course, as shown in parentheses in Figure 4-34(b), when the flat consonant button is pressed twice, it can be a hard consonant (double consonant), but when a vowel is input after that, it becomes two plain consonants. In Figure 4-34(b), among the alphabets that are input by pressing three or more times, the Hangul Gore alphabet, which is not a modern Korean consonant, will actually be used less frequently.

It was pointed out that all 4-* keypads of the present invention are compatible, and the [ㆍ] button may be indicated as a shape representing [ㅏ] or "ㅏ", and input "ㅏ" by pressing the [ㆍ] button once. Since it has been revealed that it is possible, the input value "ㆍ" may be replaced with the input value "ㅏ" in the above or below description, but for the sake of readability and convenience of the present invention, the "ㅏ" button is pressed once. Even when inputting, the input value is expressed as "ㆍ".

31.2.2 Means to remove ambiguity when entering consonants in modern Korean and Hangul archetypes

In modern Korean, two or more consonants do not appear consecutively as a first consonant. For example, the initial consonant does not appear in the form of "ㅦ" or "ㅳ". In modern Korean, hard consonants (formally double consonants) are regarded as one phoneme. "ㄲ" is also entered as "shift + ㄱ" on the PC keyboard. Therefore, when the vowel button is pressed after the final consonant is input, one consonant that can be the first consonant among the previously input final consonants becomes the first consonant of the next letter. For example, if "ㅣ" is pressed after "scratch", it becomes "writing". This is a basic matter of the modern Korean 2-beol-sik automata (that is, the "2-beol-sik Hangul Jamo Combination Rule") currently used by Koreans.

" 를 입력하면 현대 한국어 오토마타에서는 "간다"로 된다. 즉 바꾸어 말하면, 동일한 입력값에 대하여 "

"와 "간다"로 될 수 있는 모호성이 있는 것이다. 이는 초성자음 위치에 따른 모호성이므로 편의상 "초성자음위치 모호성"이라고 부를 수 있다. 물론 현대 한국어의 입력을 우선해야 하므로 단순히 연속입력하였을 경우는 "간다"로 되는 것은 당연하다. 그렇다면, "

"를 입력하기 위하여 기존 테크닉을 적용하면, "가"를 입력한 후 소정의 시간이 경과하면 "가" 라는 글자가 확정되도록 한 다음 "

"를 입력하면 된다. 또는 "가"를 입력한 다음 글자의 종료를 확정하는 "구분버튼"을 눌러 "가"를 확정한후 "

"를 입력하면 된다. 이 경우 "ㄴ"과 "ㄷ"의 연속입력이 초성자음 "ㅦ" 으로 되는 것은 한글고어를 포함하는 2벌식오토마타(한글조합규칙)이 적용되므로 자명한 것이다. Consonants (eg, ㅦ, ㅫ, .., etc.) consisting of a combination of consonants are naturally preferably entered as a combination of each consonant. (Ex. "ㅦ = ㄴ+ㄷ") However, "

Typing "will result in "go" in modern Korean automata. In other words, "for the same input value"

There is an ambiguity that can be “and “go.” This is ambiguity according to the location of the initial consonant, so it can be called “ambiguity in the location of the initial consonant” for convenience. It is natural to be "go". Then, "

If the existing technique is applied to input "A", after a predetermined time elapses after entering "A", make sure that the letter "A" is confirmed and then "

Enter ". Or, after entering "A", press the "Separation button" to confirm the end of the letter to confirm "A" and then "

Enter ". In this case, the continuous input of "b" and "c" is the initial consonant "ㅦ", which is self-evident because the 2-beol-sik automata including Hangul Gore is applied.

= ㄱㅣㆍ~ㄴㄷㅣㆍ" 또는 "

= ㄱㆍ~ㄴㄷㆍ"로 입력하는 것이다. In the present invention, a technique that enables this without using a classification button is presented. As mentioned in the previous application, "x~" means long pressing the [x] button. First, when "A" is input, the letter "A" is confirmed by long pressing the last input button, and then the initial consonant "ㅦ" is input by entering "b" and "c". For example, if you enter "ㅏ" as "ㅣㆍ", the letter "A" is confirmed by long pressing "ㆍ" and the next input is processed as the first consonant of the next letter, not the final consonant of "A". . In other words, it is a long press of "ㆍ" in "ㄱㅣㆍ" (ie, the input value "ㄱㅣㆍ~"). If you input "ㅏ" by pressing the "ㆍ" button once, it means to press and hold "ㆍ" in "ㄱㆍ" (that is, the input value "ㄱㆍ~"). This is similar to the above-described "preceding alphabet long hitting process". Expressed as an expression, "

= ㄱㅣㆍ~ㄴㄷㅣㆍ" or "

= ㄱㆍ~ㄴㄷㆍ".

= ㄱㅣㆍㄴ~ㄷㅣㆍ" 또는 "

= ㄱㆍㄴ~ㄷㆍ"로 입력하는 것이다. "ㄴ"을 입력하기 위한 버튼을 길게 누름으로써, "ㄴ"이 "가"의 받침이 아닌 다음 글자의 초성자음임을 명시화해주는 것이다. 이는 상기 설명한 "후행알파벳장타처리"와 유사하다. 다만, 길게누름에 의하여 입력되는 글자(예. "ㄴ")가 다음 글자의 초성자음임을 명시화하는 것이다. 현대 한국어만을 처리한다면, "ㄴ"에 이어서 "ㄷ"을 입력하는 것이 "ㄴㄷ"으로 2개의 낱자음이 입력되겠지만, 한글고어의 입력을 포함하는 2벌식 오토마타를 적용한다면 "ㄴ"과 "ㄷ"의 입력이 "ㅦ"으로 되는 것은 당연한 것이다. Next, after entering "A", press and hold the initial consonant "ㄴ" of the next letter (long hitting). Expressed as an expression, "

= ㄱㅣㆍㄴ~ㄷㅣㆍ" or "

= ㄱㆍㄴ~ㄷㆍ". By long-pressing the button to input "b", it clarifies that "b" is the initial consonant of the next letter, not the base of "a". It is similar to the “posterial long hitting process” described above, except that the letter input by long pressing (eg “b”) is to clarify that the first consonant of the next letter is being processed. If only modern Korean is processed, it is followed by “b”. Entering "ㄷ" is "ㄴㄷ", and two single consonants are inputted, but if you apply the 2-beol-type automata including Hangul Gore input, it is natural that the input of "b" and "c" becomes "ㅦ". .

" 으로 될 것이다. 물론 그 다음 모음(예. "ㅏ")이 입력되면 "간다"와 같이 현대 한국어 2벌식 오토마타가 적용되는 것 역시 당연한 것이다. If "ㄱㅣㆍㄴㄷ" or "ㄱㆍㄴㄷ" is pressed without 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 "ㅏ") is entered, it is natural that the modern Korean 2-beol-sik automata is applied, such as "go".

In the applicant's earlier application, a technology for inputting modern Korean without ambiguity has been proposed, and a technology for inputting modern Korean with very little ambiguity has also been proposed. For example, when the flat consonant button (eg, [ㄱ] button) is repeatedly pressed, it is said that there is ambiguity about once for about 1000 characters in the case of "ㄱ-ㄱㄱ-ㅋ-ㄲ". In the case of "chicken skewers," there may be ambiguity when the initial consonant "ㄲ" follows the "ㄱ" support. If the preceding alphabetic long hitting process is applied, the letter "chicken" is confirmed by long pressing when entering "a" of "chicken", and the next time the same [a] button is pressed, it is processed as an initial consonant, so that the input without ambiguity It is possible. If the following alphabetic long hitting process is applied, it is clarified that the initial consonant is started without being combined with the “a” of the previously entered “chicken” when the [a] button is pressed long after the input of “chicken”. Subsequently, when the [ㄱ] button is pressed once more, the initial consonant "ㄲ" is recognized, when pressed again, it is recognized as the initial consonant "ㅋ", and when pressed again, it is recognized as the initial consonant "ㄲ".

31.2.3 Hangul Gore vowel input and ambiguity removal means

Modern Korean vowels are composed of 21 vowels, but in the case of Gore, there are many more various types of vowels. Although there are various forms, most of them are in the form of double vowels or double vowels, so it is possible to input a combination of basic vowels. First, looking at the number of vowels, there are 71 vowels from Unicode 1161 to 11A7 in drawing 4-33(*) (50 vowels excluding 21 vowels in modern Korean), and in drawing 4-33(*) There are 23 vowels from Unicode D7B0 to D7C6, and 94 vowels have been registered in Unicode v6.0 to date, including 21 vowels in modern Korean. The vowels of the Hangul Gore alphabet included in the Unicode in Fig. 4-33(*) can be easily viewed at a glance.

In (2) above, "ㅣㅕ" means a vowel combined with "ㅣ" and "ㅕ", and "ㅣㅖ" means a vowel combined with "ㅣ" and "ㅖ". Looking at the pc keyboard as a standard, most vowels can be entered as a combination of vowels on the keyboard (eg vowels that can be entered by pressing a button on the keyboard or pressing simultaneously with shift).

First, when entering a vowel as a combination of three vowel elements known to the public as "ㅡ", "ㆍ", and "ㅣ", and entering "ㆍ" without entering "ㅏ" with the [ㆍ] button (for convenience If you look at the vowel input of Hangul Gore in "Haeah 3 Vowel Method"), it is as follows. When inputting even Hangul Gore vowels, pressing the [ㆍ] button once will input Hangul Gore Vowel "Daeah". This is the content already suggested in the applicant's earlier application. When the [ㆍ] button is pressed twice, two vowels (Unicode 11A2 vowels, the 5th vowel in the 5th row of (2) above) are entered. The examples are 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 "ㅝ". Separate explanation)

= ㅡㅡㆍ

= ㅡㅡㆍ

= ㅡㅡ

= ㅡㅡ

= ㅡㅣㅡㆍ

= ㅡㅣㅡㆍ

= ㅣㅣㆍ

= ㅣㅣㆍ

= ㅣㅣㆍㆍ

= ㅣㅣㆍㆍ

= ㅣㆍㅡ ("

"와 모호성 있음)

= ㅣㆍㅡ ("

"With ambiguity)

= ㅣㅡㆍ

= ㅣㅡㆍ

= ㅣㅡ

= ㅣㅡ

= ㅣㆍ ("ㅏ"와 모호성 있음. 별도 설명)

= ㅣㆍ (There is ambiguity with "ㅏ". Separate explanation)

= ㆍ

= ㆍ

= ㆍㆍㅣ ("ㅕ"와 모호성 있음. 별도 설명)

= ㆍㆍㅣ (There is ambiguity with "ㅕ". Separate explanation)

= ㆍㅡㆍ

= ㆍㅡㆍ

= ㆍㅣ ("ㅓ"와 모호성 있음. 별도 설명)

= ㆍㅣ (There is ambiguity with "ㅓ". Separate explanation)

= ㆍㆍ

= ㆍㆍ

= ㅣㆍㅡ ("

"와 모호성 있음)

= ㅣㆍㅡ ("

"With ambiguity)

= ㅣㆍㆍㅡㆍ

= ㅣㆍㆍㅡㆍ

= ㆍㆍㅣㅣㆍㆍ

= ㆍㆍㅣㅣㆍㆍ

= ㆍㅡㅣㆍㆍ

= ㆍㅡㅣㆍㆍ

= ㆍㅡㅣㆍㆍㅣ

= ㆍㅡㅣㆍㆍㅣ

= ㆍㅡㆍㆍㅣ

= ㆍㅡㆍㆍㅣ

= ㆍㅡㅡㆍ (추가 설명 있음)

= ㆍㅡㅡㆍ (with additional explanation)

= ㆍㆍㅡㅣㆍ

= ㆍㆍㅡㅣㆍ

= ㆍㆍㅡㅣㆍㅣ

= ㆍㆍㅡㅣㆍㅣ

= ㅡㆍㆍㆍㅣ (참고 [ㆍ]버튼 3번)

= ㅡㆍㆍㆍㅣ (Reference [ㆍ] button 3)

= ㅡㆍㅣㅣ ("

"와 모호성 있음)

= ㅡㆍㅣㅣ ("

"With ambiguity)

= ㅡ ㆍㆍㅣㆍㅣ

= ㅡ ㆍㆍㅣㆍㅣ

= ㅡ ㆍㆍㆍㅡ (참고 [ㆍ]버튼 3번)

= ㅡ ㆍㆍㆍㅡ (Reference [ㆍ] button 3)

= ㅡㅣㆍ

= ㅡㅣㆍ

= ㅡㆍㅣ ("ㅟ"와 모호성 있음)

= ㅡㆍㅣ (There is ambiguity with "ㅟ")

= ㅡㆍㅣㅣ ("

"와 모호성 있음)

= ㅡㆍㅣㅣ ("

"With ambiguity)

= ㅡㆍㅡ

= ㅡㆍㅡ

= ㅣㅣㆍㆍㆍㅡ (참고 [ㆍ]버튼 3번)

= ㅣㅣㆍㆍㆍㅡ (Reference [ㆍ] button 3)

= ㅣㅣㆍㆍㅣ

= ㅣㅣㆍㆍㅣ

= ㅣㆍㆍㅣ ("ㅒ"와 모호성 있음)

= ㅣㆍㆍㅣ (There is ambiguity with "ㅒ")

= ㅣㆍㆍㅣㅣ

= ㅣㆍㆍㅣㅣ

= ㆍㅣㅡㆍ

= ㆍㅣㅡㆍ

= ㅣㆍㆍㅡ ("

"와 모호성 있음)

= ㅣㆍㆍㅡ ("

"With ambiguity)

= ㅣㅡㆍㆍ

= ㅣㅡㆍㆍ

= ㅣㅣ

= ㅣㅣ

= ㆍㅣㆍ

= ㆍㅣㆍ

= ㆍㆍㅣㅣ ("ㅖ"와 모호성 있음. 별도 설명)

= ㆍㆍㅣㅣ (There is ambiguity with "ㅖ". Separate explanation)

. . . . . .

"를 입력하기 위하여 " ㅣㆍㅡ"까지 입력하였을 때, "ㅏ"와 "ㅡ"가 결합된 모음이 없으므로 "ㅏㅡ"로 일시적으로 되었다가 [ㆍ]버튼이 눌러지면 전체 입력값 "ㅣㆍㅡㆍ"이 "

" 로 된다. 이는 다른 유사한 경우에 있어서도 동일하게 동작할 수 있다. There may be more ambiguities in the above, but it can be applied similarly to the description below. In the case of inputting 21 modern Korean vowels using a combination of "ㅡ", "ㆍ", and "ㅣ", complete vowels were always combined in the middle of the input without ambiguity. However, in the case of inputting even Hangul Gore vowels, complete vowels may not be made in the middle of the input. E.g "

When inputting "ㅣㆍㅡ" to input "," there is no vowel combined with "ㅏ" and "ㅡ", so it temporarily goes to "ㅏㅡ" and then when the [ㆍ] button is pressed, the total input value "ㅣㆍ ㅡㆍ"This "

". This can work the same in other similar cases.

When inputting Hangul Gore vowels with a combination of three vowel elements, there are cases where there are two or more vowels for the same input value. Some examples are as follows:

= ㅡㆍㆍㅣㅝ =

= ㅡㆍㆍㅣ

= ㅣㆍㅏ =

= ㅣㆍ

= ㆍㅣㅓ =

= ㆍㅣ

= ㆍㆍㅣㅕ =

= ㆍㆍㅣ

= ㆍㆍㅣㅣㅖ =

= ㆍㆍㅣㅣ

. . . . . .

" 의 입력시, 기존의 시간지연(즉, 타이머) 기법을 적용한다면 "ㅠ"까지 입력하고 소정시간 경과하여 "ㅠ"가 확정된 다음 "ㅣ" 를 눌러 "

"를 입력하게 된다. 또한 구분버튼을 사용한다면 "ㅠ"입력후 구분버튼을 눌러 "ㅠ"를 확정후 "ㅣ"를 눌러 "

"를 입력하게 된다. 기존에는 "ㅠ"입력후 구분버튼 또는 시간지연 등의 수단으로 "ㅠ" 확정후 "ㅣ"를 누르면 "ㅠㅣ"와 같이 "ㅣ"가 낱자모음으로 입력되었으나, 한글고어 모음의 입력이 전제된 한글조합규칙 적용시 "

"로 조합되어야 한다. 출원인이 설명했던 "선행알파벳장타처리"를 적용하면, "ㅠ"의 마지막 입력값인 "ㆍ"을 길게 눌러 "ㅠ"를 확정한 다음 "ㅣ" 를 눌러 "

"를 입력할 수 있다. 표현식으로 나타내면 "

= ㅡㆍㆍ~ㅣ" 가 된다. 또는 "후행알파벳장타처리"를 적용하면 "ㅠ" 다음에 눌러지는 [ㅣ]버튼을 길게 누름으로써 기 눌러진 "ㅡㆍㆍ"이 "ㅠ"로 인식하고 여기에 "ㅣ"가 결합되어 결과적으로 "

"가 되도록 할 수 있다. 표현식으로 나타내면, "

= ㅡㆍㆍㅣ~" 가 된다. 상기 "

", "

", "

", "

" 의 입력도 동일하게 처리할 수 있다. This can also be regarded as "ambiguity" when entering vowels. For convenience, it could be called "alphabet ambiguity", and narrowly it could be called "vowel ambiguity". Since the input of modern Korean should be given priority, it is natural that the modern Korean vowels "ㅝ", "ㅏ", "ㅓ", and "ㅕ" are input when the input value is pressed. "

When inputting ", if the existing time delay (ie, timer) technique is applied, input up to "ㅠ" and after a predetermined time elapses, "ㅠ" is confirmed, then press "ㅣ" to "

In addition, if you use the classification button, enter "ㅠ" and press the classification button to confirm "ㅠ", then press "ㅣ" to "

In the past, if you press "ㅣ" after confirming "ㅠ" by means of a classification button or time delay after entering "ㅠ", "ㅣ" was entered in single letter vowels like "ㅠㅣ". When applying the Hangul combination rule that presupposes input of vowels

It must be combined with ". When applying the "priority alphabet long hitting process" described by the applicant, press and hold "ㆍ", the last input value of "ㅠ" to confirm "ㅠ", then press "ㅣ" to "

You can enter ". When expressed as an expression, "

= ㅡㆍㆍ~ㅣ" Or, if "Travel Alphabet Long Strike Processing" is applied, by long pressing the [ㅣ] button pressed after "ㅠ", the previously pressed "ㅡㆍㆍ" is recognized as "ㅠ""ㅣ" is combined here, resulting in "

You can make it ". Expressed as an expression, "

= ㅡㆍㆍㅣ~" becomes "above"

", "

", "

", "

The input of "can be processed in the same way.

Next, input a vowel as a combination of three vowel elements "ㅡ", "ㆍ", and "ㅣ" and enter "ㅏ" with one click of the [ㆍ] button, or "ㅡ", "ㅏ", "ㅣ "Using the three vowel buttons, we look at the Korean Gore vowel input as follows. For convenience, this will be called "Daeah=ㅏ 3 vowel method". Hereinafter, the "ㅏ" ("ㅏ" input by pressing the [ㆍ] button once, or "ㅏ" of the [ㅏ] button) is any other vowel (eg, "ㅓ", "ㅗ", "ㅜ") , ... one of). In the following description, it is indicated by "·" for convenience. To enter the lower child alone, press the [ㆍ] button twice as suggested in the previous application. In other Hangul Gore vowel combinations, the [ㆍ] button is used as a stroke "ㆍ" as it is. For example, let's say "ㅓ = ㆍㅣ" and "ㅕ = ㆍㆍㅣ". It is the same as the case of entering Korean Gore vowels with the three vowel buttons of "ㅡ", "ㆍ" and "ㅣ" already described (in the case of entering "ㆍ" with the [ㆍ] button), or "ㅣ" for entering "ㅏ" In the case where "" is simply replaced by "", the description is also omitted. The input examples are almost similar to those in "Below 3 Vowels", so they are not presented separately.

"의 입력시, "ㅏ"를 "ㆍ"으로 입력하는 것을 적용하면 "

"의 입력값은 "ㆍㆍㅡ"가 되는데, 이는 현대 한국어 모음의 "ㅑ"와 같게 된다. (즉 "

"와 "ㅑ"의 모호성이 있게 되는 것이다. 현대 한국어의 입력을 우선하여 잘 작동하도록 하여야 하므로 "

"의 "ㅏ"는 "ㅣㆍ"로 입력하여 "

= ㅣㆍㆍㅡ" 로 되어야 한다. "

When inputting "," inputting "ㅏ" as "ㆍ" applies "

The input value of "becomes "ㆍㆍㅡ", which is the same as "ㅑ" in the modern Korean vowel (that is,"

There is an ambiguity between "and "ㅑ". Since the input of modern Korean should be given priority to make it work well,"

Enter "ㅏ" in "ㅣㆍ" to "

= ㅣㆍㆍㅡ".

", "

", "

", "

", "

", "

", ...)의 아래아를 입력하는 방법에는 2가지가 있을 수 있다. 첫번째는 [ㆍ]버튼 1번 눌러짐으로 입력되도록 하는 것이며, 이는 상기 "아래아 3모음법" 에서와 동일하다. 또한가지 방법은 이렇게 형태적으로 아래아가 온전히 포함된 모음의 아래아부분은 [ㆍ]버튼 2번 눌러짐으로 입력되록 하는 것이다. "아래아=ㅏ 3모음법"에서의 한글고어 모음입력을 말할 때는 특별한 경우가 아닌 한 이경우 [ㆍ]버튼 2번 누름으로 아래아를 입력하는 것으로 한다. Formally, "ㆍ" is not a vowel attached to another vowel (eg, "ㅓ", "ㅕ", ..), but a vowel (eg. "

", "

", "

", "

", "

", "

There can be two ways to input the lower child of ", ...). The first is to input by pressing the [ㆍ] button once, and this is the same as in the above "Here, three vowels". One way to do this is to make the lower sub part of the vowel that is completely included in the form like this by pressing the [ㆍ] button twice. Unless otherwise, it is assumed that in this case, press the [ㆍ] button 2 times to input the lower word.

"가 입력되도록 할 수도 있다. "ㅣㆍ=ㅏ"가 아닌 "ㅣㆍ=

"로 적용되는 것은 키패드에서 한글고어의 입력이 보편적으로 사용되는 시기에 적용되는 것이 바람직할 것이다. 상기 알파벳내 모호성이 있는 4가지 모음에 대해 "아래아=ㅏ 3모음법" 적용시의 모호성은 다음과 같다. The same applies to the case of "ㅝ", "ㅏ", "ㅓ", and "ㅕ" which have ambiguities in the vowel. However, it is possible to enter a single vowel "ㅏ" (not "ㅏ" included in other Korean Gore vowels) by pressing the [ㆍ] button after the consonant, so in the case of "ㅣㆍ" (vowel "ㅣ") If "ㆍ" pressed next is regarded as acting as "ㆍ") is "

It is also possible to input "." instead of "ㅣㆍ=ㅏ"

It would be desirable to apply "in the key pad when the input of Hangul Gore is commonly used. The ambiguity in the application of "Daeah=ㅏ 3 vowel method" for the four vowels with ambiguity in the alphabet is as follows: Same as

= ㅡㆍㆍㅣㅝ =

= ㅡㆍㆍㅣ

= ㅣㆍㆍ (모음에 포함되어 있는 단일한 "ㆍ"을 [ㆍ]버튼 2타로 입력하므로. 이하 동일)ㅑ =

= ㅣㆍㆍ (Because you input a single "ㆍ" included in the vowel with two [ㆍ] buttons. Same as below)

= ㆍㆍㅣㅕ =

= ㆍㆍㅣ

= ㆍㆍㆍㅣ

= ㆍㆍㆍㅣ

= ㆍㆍㆍㅣㅣ

= ㆍㆍㆍㅣㅣ

= ㆍㆍㆍㆍ

= ㆍㆍㆍㆍ

= ㆍㆍ

= ㆍㆍ

= ㆍㆍㅡㆍ

= ㆍㆍㅡㆍ

= ㆍㆍㅣㅡㆍ

= ㆍㆍㅣㅡㆍ

. . . . . .

= ㅡㆍㆍ~ㅣ", "

= ㅣ~ㆍㆍ", "

= ㆍㆍ~ㅣ", "

= ㆍㆍ~ㆍㅣ", "

= ㆍㆍ~ㆍㅣㅣ" 로 입력된다. 후행알파벳장타처리 적용시, "

= ㅡㆍㆍㅣ~", "

= ㅣㆍ~ㆍ", "

= ㆍㆍㅣ~", "

= ㆍㆍㆍ~ㅣ", "

= ㆍㆍㆍ~ㅣㅣ" 로 입력된다. When applying the preceding alphabet long hitting treatment, "

= ㅡㆍㆍ~ㅣ", "

= ㅣ~ㆍㆍ", "

= ㆍㆍ~ㅣ", "

= ㆍㆍ~ㆍㅣ", "

= ㆍㆍ~ㆍㅣㅣ" It is entered as "

= ㅡㆍㆍㅣ~", "

= ㅣㆍ~ㆍ", "

= ㆍㆍㅣ~", "

= ㆍㆍㆍ~ㅣ", "

= ㆍㆍㆍ~ㅣㅣ" is entered.

"의 경우를 제외한 4가지 경우는 모두 아래아 형태가 모음의 일부로 포함되어 야기된 모호성임을 알 수 있다. 따라서 선/후행장타처리와 상관없이, 상기와 같이 모호성이 있는 모음이 입력되는 경우, [ㆍ]버튼의 길게 누름을 아래아로 할 수도 있다. 예를 들어, "

= ㅣㆍ~", "

= ㆍ~ㅣ", "

= ㆍ~ㆍㅣ", "

= ㆍ~ㆍㅣㅣ" 로 입력된다. "

"의 경우만 선행알파벳장타처리(예. "

= ㅡㆍㆍ~ㅣ") 또는 후행알파벳장타처리(예. "

= ㅡㆍㆍㅣ~")를 선택적으로 적용하면 된다. 상기와 같이 "모음내 모호성"이 없는 경우(예. "ㅜ")는 [ㆍ]버튼이 길게 눌러졌더라도(예. 입력값 "ㅡㆍ~") 보통의 눌러짐(예. 입력값 "ㅡㆍ")과 동일하게 처리할 수 있다. 이렇게 [ㆍ]버튼의 길게 누름으로 절대적으로 아래아를 입력하는 것은 선/후행장타처리의 로직을 사용자가 생각하지 않아도 모호성이 있는 상기 경우에 한글고어 모음을 정확히 입력할 수 있다. 다만, 선출원에서 제시하였던 [ㆍ]버튼의 길게 누름으로 "ㅎ"을 입력하는 것은 함께 적용하지 못하는 것은 당연하다. 이렇게 [ㆍ]버튼 길게누름으로 모음요소 "ㆍ"을 입력하거나 (예. "ㅜ = ㅡㆍ~") 아래아의 형상이 포함된 한글고어 모음(예. "

", "

", "

", "

", ...)의 아래아를 절대적으로 입력하는 것을 "아래아버튼장타처리"라고 부르기로 한다. Other methods that can be commonly applied to the above "Haeah 3 vowel method" and "Haeah = ㅏ 3 vowel method" are as follows. Among the 5 cases above, "

In all four cases except the case of ", it can be seen that the form of the lower child is included as part of the vowel and is caused by ambiguity. Therefore, regardless of the line/post-long hitting process, when a vowel with ambiguity is input as described above, [ㆍ You can also press and hold the button down. For example, "

= ㅣㆍ~", "

= ㆍ~ㅣ", "

= ㆍ~ㆍㅣ", "

= ㆍ~ㆍㅣㅣ" is entered.

In the case of "only", the preceding alphabet long hitting is processed (eg. "

= ㅡㆍㆍ~ㅣ") or trailing alphabetic long hitting (ex. "

= ㅡㆍㆍㅣ~") If there is no "ambiguity in the vowel" as described above (eg "ㅜ"), even if the [ㆍ] button is long pressed (eg input value "ㅡ"ㆍ~") It can be processed in the same way as normal pressing (eg, input value "ㅡㆍ") In this way, by long pressing the [ㆍ] button, absolutely inputting the bottom child is the logic of the preceding/post-long hitting process. In the above case where there is ambiguity even if the user does not think about it, it is possible to accurately input the Hangul Gore vowels, but it is natural that inputting "ㅎ" by long pressing the [ㆍ] button suggested in the previous application cannot be applied together. In this way, by long-pressing the [ㆍ] button, enter the vowel element "ㆍ" (eg "ㅜ = ㅡㆍ~") or the Hangul Gore vowel containing the shape of the lower child (eg "").

", "

", "

", "

The absolute input of the lower child of ", ...) will be called the "lower button long hitting process".

Let's take a look at how to input Hangul Gore vowels while applying the technique of using the vowel button suggested by the applicant as a control button (eg "y = xㅡㅡ" or "z = xㅣㅣ"). Representatively, what the applicant suggested was entered as "ㅋ = ㄱㅡㅡ" or "ㄲ = ㄱㅣㅣ". That is, if "ㅡ" is pressed twice after the input of a consonant (eg, "ㄱ"), or "ㅣ" is pressed twice, "ㅋ" or "ㄲ" is input. In modern Korean, "ㅡ" does not appear twice in a row and "ㅣ" does not appear twice in a row.

", "

", "

", "

", "

", "

", ... 등이 있다. 입력값 "ㄱㅡㅡ"를 누른 것이 "ㅋ" 도 될 수 있고, "

" 도 될 수 있는 것이다. 이는 입력되는 결과인 알파벳(예. "ㅋ")과 자모결합글자(예. "

") 간의 모호성으로 편의상 "알파벳-글자間 모호성" 또는 "알파벳-글자 모호성" 이라고 부를 수 있을 것이다. 상기에서 언급한 바와 같이, "

" 와 "

"를 각각 [ㅡ]버튼 2번 누름 그리고 [ㅣ]버튼 2번 누름으로 입력한다면, "ㅋ = ㄱㅡㅡㅡ"로 입력되어야 한다. 그러나 과연 얼마나 사용될지도 모르는 한글 고어의 입력을 위해 현대 한국어 알파벳(예. "ㅋ")의 입력에 불편(예. [ㅡ]버튼 3번 누름의 조합)을 초래하는 것은 바람직하지 않다. 따라서 현대 한국어와 한글고어의 입력을 함께 적용하더라도, 현대 한국어의 입력을 우선하여 고려하는 것이 타당하다. 그렇다면 "ㅋ"의 입력과 "

"의 입력을 어떻게 처리할 수 있는지를 다음에서 보인다. However, in Hangul Gore, there are cases where "ㅡ" or "ㅣ" appears twice in a row after a consonant. E.g, "

", "

", "

", "

", "

", "

", ..., etc. Pressing the input value "ㄱㅡㅡ" can also be "ㅋ", and "

"It can also be. This is the result of inputting alphabets (eg "ㅋ") and alphabetic characters (eg "").

For convenience, the ambiguity between ") could be called "alphabet-letter ambiguity" or "alphabet-letter ambiguity". As mentioned above, "

" Wow "

If you input "by pressing the [ㅡ] button twice and pressing the [ㅣ] button twice, it should be entered as "ㅋ = ㄱㅡㅡㅡ". However, for the input of Hangul Gore, which may be used, the modern Korean alphabet It is not desirable to cause inconvenience (eg, a combination of pressing the [ㅡ] button 3 times) in the input of (eg, "ㅋ"). Therefore, even if the input of modern Korean and Hangul Gore is applied together, the input of modern Korean It is reasonable to consider first. If so, input "ㅋ" and "

The following shows how to handle the input of ".

"를 입력하기 위해서는 "ㄱ"을 누른후 소정시간 지연(즉, 타이머) 또는 구분버튼 눌러짐에 의하여 "ㄱ"을 확정하고 "ㅡㅡ"를 2번 누르도록 하면된다. "알파벳-글자 모호성"을 해결하는 과정은 일련의 버튼누름(예. "ㄱㅡㅡ")이 하나의 알파벳(예. "ㅋ")으로 인식되지 않고 자음과 모음의 조합(예. "

")으로 인식되도록 특별히(예. 시간지연, 구분버튼, 선/후행장타, ...) 처리하는 것이므로, 그 성질은 "알파벳내 모호성" 과 유사하다. Since the input of the modern Korean language should be considered first, it is reasonable to become "ㅋ" when you press "ㄱㅡㅡ". Applying the existing time delay or timer technique, "

To enter "a", press "a" and then confirm "a" by pressing the button for a predetermined time delay (ie, timer) or by pressing the separator button, and then press "ㅡ-" twice. "Alphabet-character ambiguity" The process of solving the problem is that a series of button presses (eg, "ㄱㅡㅡ") are not recognized as a single alphabet (eg, "ㅋ"), and a combination of consonants and vowels (eg. "

It is specially processed to be recognized as ") (eg time delay, division button, pre/post hit, ...), so its properties are similar to "ambiguity in alphabet".

" 가 되는 것이다. 어떤 자음 다음에 모음 "

"가 입력되는 것은 그 앞에 입력된 자음이 어차피 초성자음으로 처리될 수 밖에 없기 때문이다. 만약 현대 한국어에서도 사용되는 "ㅋ"을 입력하기 위한 것이었다면 [ㄱ]버튼의 길게 누름(즉, "ㄱ~ㅡㅡ")이 아닌 보통의 누름(즉, "ㄱㅡㅡ")으로 누르면 된다. 이는 주로 사용되는 현대 한국어 자음의 입력에는 길게 누름을 사용하지 않으면서 동시에 조합되는 모음버튼(예. [ㅡ]버튼 또는 [ㅣ]버튼)의 눌러짐도 2회만 적용되는 장점이 있다. 도면4-34(a)에서 회색음영으로 표시된 알파벳은 현대 한국어 자음을 나타낸다. 도면4-34(a)에서 1차조합에 의하여 입력되는 자음은 [ㅡ]버튼 또는 [ㅣ]버튼의 2번 눌러짐의 조합으로 입력된다. 자음 다음에 "ㅡ"가 연속하여 2번 나오는 고어 글자(예. "

")의 입력을 허용하지 않는다면 2차조합, 3차조합, ... 에 의하여 입력되는 자음도 [ㅡ]버튼 또는 [ㅣ]버튼의 2번 눌러짐의 조합으로 입력되지만, 상기와 같은 고어 글자(예. "

")의 입력을 허용한다면 2차조합, 3차조합, 4차조합, ... 에 의하여 입력되는 자음은 [ㅡ]버튼 또는 [ㅣ]버튼 3회 눌러짐의 조합으로 입력된다. 예를 들어, "ㅸ =

ㅡ = ㅍㅡㅡㅡ = ㅂㅡㅡㅡㅡㅡ" 와 같이 되는 것이다. If you use the preceding alphabet long hitting process, press and hold "ㄱ" to confirm "ㄱ", then press "ㅡ" twice. Even in this way, it does not collide with the input from the initial consonant position ambiguity (ie, ambiguity occurs), and in very unusual cases, there is virtually no level of ambiguity. In other words, if you press and hold "ㄱ" to confirm it as a first consonant and then press "ㅡ" twice, it is not "ㅋ" but "

"It becomes. A vowel after some consonant"

"" is input because the consonant input before it has to be treated as an initial consonant anyway. If it was to input "ㅋ", which is also used in modern Korean, long press the [ㄱ] button (that is, "ㄱ You can press it with a normal press (ie, “ㄱㅡㅡ”), not with ~ㅡㅡ"), which is a vowel button that is combined at the same time without using a long press for the input of mainly used modern Korean consonants (eg [ㅡㅡ) ] Button or [ㅣ] button) has the advantage of being applied only twice, in Figure 4-34(a), the alphabet marked with gray shades represents modern Korean consonants. The consonant input by the combination is input by pressing the [ㅡ] button or the [ㅣ] button twice.

If the input of ") is not allowed, the consonants input by the 2nd, 3rd, ... are also input by pressing the [ㅡ] button or the [ㅣ] button twice, but the archaic characters as above. (Yes. "

If the input of ") is allowed, the consonants input by the 2nd, 3rd, 4th, ... are input by pressing the [-] button or the [ㅣ] button three times. , "ㅸ =

ㅡ = ㅍㅡㅡㅡ = ㅂㅡㅡㅡㅡㅡ".

" 와 "

"은 눌러지는 버튼(즉, 입력값)이 같다. 본 발명에서 설명한 바와 같이, 한글고어(예. "

")보다 현대 한국어(예. "ㅌ")이 우선하여 쉽게 입력되어야 하므로, 길게 누름을 사용하지 않는 입력값 "ㄷㅡㅡ"는 "ㅌ"으로 되고, "ㄷ~ㅡㅡ" 는 "

"로 되는 것이다. 이는 "초성자음위치 모호성"에서 "후행알파벳장타처리" 적용시 길게누름에 의하여 입력되는 자음을 초성자음으로 처리하는 것과 일치하게 된다. 즉, "

" 이 아닌 "간ㄷ"을 입력하기 위하여, 후행알파벳장타처리를 적용하여 "ㄷ"을 길게 눌러 입력하는 것과 같게 된다. In order to input the consonants that are first combined in Fig. 3-34 by pressing the [-] button or the [ㅣ] button twice, there are several things to be considered in some Hangul automata (Hangul Jamo Combination Rules). "liver

" Wow "

"The button to be pressed (ie, the input value) is the same. As described in the present invention, Hangul Gore (eg."

Modern Korean (eg, "ㅌ") takes precedence over ") and must be easily entered, so the input value "ㄷㅡㅡ" that does not use a long press becomes "ㅌ", and "ㄷ~ㅡㅡ" is "

This is consistent with processing a consonant input by a long press as an initial consonant when applying the "post-alphabetic long hitting process" in the "initial consonant position ambiguity". That is, "

In order to enter "ganc" instead of ", it is the same as inputting by long pressing "c" by applying the trailing alphabet long hitting process.

")을 형성할 수 있으면 이를 각각의 낱자음(예. "ㅅ")과 초성자음(예. "ㄷ")으로 인식(예. "ㅅㄷ")하지 않고, 입력값 전체(예. "ㅅㄷ~")를 초성자음(예. "

")으로 처리할 수 있다. 이렇게 입력된 "

" 다음에 모음이 오면 "

" 전체가 초성자음으로 된다. "ㅅ"이 초성자음이라는 것을 명확히 하기 위하여 입력값으로 "ㅅ~"이 눌러진 이후에 "ㄷ~"이 눌러진 경우(예. 입력값 "ㅅ~ㄷ~")도 결과는 동일하다. "

" 와 "

" 은 눌러지는 버튼이 동일한데, 역시 현대 한국어의 입력을 우선하여, 길게 누름을 사용하지 않는 "ㄷㅡㅡ"는 "ㅌ"이 되고, 길게 누름을 사용하는 "ㅅㄷ~ㅡㅡ"는 "

"이 되도록 할 수 있다. 앞서 간단히 언급한 대로 도면3-34에서 2차조합, 3차조합, ... 에 의하여 입력되는 자음은 모두 한글고어 자음으로 사용빈도가 매우 적을 것이므로 [ㅡ]버튼 또는 [ㅣ]버튼 3번 눌러짐의 조합으로 입력되는 것이 적합해 보인다. In addition, when applying the "post-alphabetic long stroke" in "initial consonant position ambiguity", the consonant (eg "ㅅ") entered immediately before the long press is recognized as the initial consonant, not the final consonant, and then the consonant ( Ex. "C") is added to the initial consonant (Ex. "

If ") can be formed, it is not recognized (eg "ㅅㄷ") as individual consonants (eg "ㅅ") and initial consonants (eg "ㄷ"), and the entire input value (eg, "ㅅㄷ~"). ") to a first consonant (eg."

It can be processed with "). "

"The next time a vowel comes"

"The whole becomes a first consonant. In order to clarify that "ㅅ" is a first consonant, when "c~" is pressed after "ㅅ~" is pressed as an input value (ex. input value "ㅅ~ㄷ~" ), the result is the same."

" Wow "

"The button that is pressed is the same, but also prioritizes the input of modern Korean, and "ㄷㅡㅡ" without long press becomes "ㅌ", and "ㅅㄷ~ㅡㅡ" using long press is "

As briefly mentioned above, consonants input by 2nd, 3rd, ... in Drawing 3-34 are all Hangul Gore consonants and will be used very little, so the [-] button or It seems suitable to be input by pressing the [ㅣ] button 3 times.

= ㅡ~ㅡㆍ"가 된다. For "alphabet-character ambiguity", if you apply the trailing alphabet long hitting process, press "ㄱ", then long press "ㅡ", then press "ㅡ" again. E.g, "

= ㅡ~ㅡㆍ".

"를 입력하는 것으로 정의할 수도 있다. 마찬가지로 [ㅣ]버튼 한번 길게 누르는 것을 "

"로 정의할 수도 있다. 예를 들어, "

= ㅡ~ㅡㆍ"가 아닌 "

= ㅡ~ㆍ"로 입력되는 것이다. 이는 "후행알파벳장타처리"를 적용하는 경우 "

" 입력시 길게누름을 이용해야만 하는 불편함이 있는데, 입력타수를 1타 줄여주며, 직관적으로도 "

"를 "ㅡ" 길게누름으로 입력하는 것으로 연상할 수 있으므로 사용자에게 쉽게 이해될 수 있는 잇점이 있다. 이를 편의상"수직/수평모음장타처리 (입력방법)" 이라고 부르기로 한다. In the above, examples of "preceding alphabet long hitting" or "following alphabet long hitting" were shown for ambiguity in various cases. When applying the following alphabetic long hitting treatment in alphabet-character ambiguity, pressing the [-] button once long. "

It can also be defined as entering ". Similarly, pressing the [ㅣ] button once is "

It can also be defined as ". For example, "

= "Not ㅡ~ㅡㆍ"

= ㅡ~ㆍ" is entered. This is when applying "post-alphabetic long hitting"

"There is an inconvenience of having to use a long press when entering, but it reduces the number of strokes by one, and intuitively "

Since it can be reminiscent of inputting "-" with a long press, there is an advantage that can be easily understood by the user. This is called "vertical/horizontal vowel hitting processing (input method)" for convenience.

", "

", "

", "

", "

", "

", ... 등이 있는데, 이러한 모음의 입력에 [ㅡ]버튼 또는 [ㅣ]버튼 길게 누름으로 상기 모음에 포함된 "

" 또는 "

"를 각각 입력되도록 할 수 있다. 이 역시 "수직/수평모음장타처리"를 이용하는 것이 된다. (상기 "

= ㅡ~ㆍ"로 입력하는 사례 참조) 현재까지 등록된 유니코드v2.0에서는 "ㆍㅡㅡ = ㅗㅡ" 가 결합된 형태의 모음은 없다. 그러나 "

" 를 "ㆍㅡㅡㆍ"으로 입력한다면 그 과정에서 눌러지는 "ㆍㅡㅡ" 가 "ㅎ"으로 해석될 수 있다. 따라서 현대 한국어의 입력을 우선하여 "ㆍㅡㅡ" 를 항상 "ㅎ"으로 인식되도록 한다면, "

"를 입력하기 위하여는 "ㆍㅡ~ㆍ"으로 할 수 있다. 즉 "

"에 포함되어 있는 "

"를 [ㅡ]버튼 길게 누름에 의하여 입력하는 것이다. As exemplified above, a vowel to which "-" or "-" can be pressed twice in succession after a consonant is "

", "

", "

", "

", "

", "

There are ", ..., etc.," included in the vowel by long pressing the [ㅡ] button or [ㅣ] button in the input of these vowels.

" or "

"It can be entered separately. This is also to use the "vertical/horizontal vowel hitting process".

= Refer to the case of inputting with ㅡ~ㆍ") In Unicode v2.0 registered so far, there is no vowel in the form of "ㆍㅡㅡ = ㅗㅡ" combined.

If "is entered as "ㆍㅡㅡㆍ", "ㆍㅡㅡ" pressed in the process can be interpreted as "ㅎ". Therefore, "ㆍㅡㅡ" is always "ㅎ" with priority to the input of modern Korean. If you make it recognized, "

To input ", you can do it with "ㆍㅡ~ㆍ". That is, "

"Contained in"

"" is entered by long pressing the [ㅡ] button.

= ㅡㆍㅣㅣ"와 같이 모음이 먼저 인식되고 나서 "ㅣ"가 연속하여 나오는 경우는 상기와 같이 자음이 인식되고 나서 "ㅣ" (또는 "ㅡ")가 연속 나오는 경우와 구별되기 때문에 "알파벳-글자 모호성"이 없으므로 굳이 길게누름을 이용하여 입력할 필요는 없다. 일관성을 위하여, "ㅔ", "ㅞ", "

", ... 등에 들어 있는 "

"를 길게누름으로 입력하도록 허용할 수도 있다. 예를 들어, "ㅔ = ㆍㅣ~" 으로 하는 것이나, 권장하지 않는다. 특히 "알파벳내 모호성"에 대해 후행알파벳장타처리로 입력하는 것과 충돌되는 부분이 있어 함께 적용하지 못할 수 있다. "ㅔ = ㆍㅣㅣ", "ㅞ = ㅡㆍㆍㅣㅣ", or "

= When vowels are recognized first and then "ㅣ" appears consecutively, such as ㅡㆍㅣㅣ", it is distinguished from the case where "ㅣ" (or "ㅡ") appears consecutively after the consonant is recognized as above. -There is no letter ambiguity, so there is no need to enter by long press. For consistency, "ㅔ", "ㅞ", "

", ... on the back"

It is also possible to allow the input of "by long-pressing. For example, "ㅔ = ㆍI~" is not recommended. In particular, for "ambiguity in the alphabet", it is in conflict with the input of the following alphabetic hitting process. May not be applied together.

In the above, examples such as "ambiguity in initial consonant position", "ambiguity in alphabet", and "alphabet-letter ambiguity" have been cited. For each case, the preceding alphabet long hitting and the trailing alphabet long hitting treatment can be selectively applied. For example, in the case of "positional ambiguity of the initial consonant", the trailing alphabet long hitting treatment is applied, in the case of "ambiguity in the alphabet", the preceding alphabet long hitting treatment is applied, and for the "alphabet-character ambiguity", the preceding alphabet long hitting treatment is applied. It can be done. From the user's point of view, when a certain button is pressed for a long time during a series of button presses, there is a feeling that the result of the input value including the long-pressed button is confirmed. The moment it is pressed, the input value that was pressed up to that point can be confirmed and it feels as if a new input is started. In either case, it can be used selectively (e.g. preset in environment settings) according to user preference.

= ㅡㆍㆍ~ㅣ")하고, "알파벳내 모호성"의 경우에는 아래아버튼장타처리를 적용하고, "알파벳-글자 모호성"에 대해서는 선행알파벳장타처리를 적용하는 것을 들 수 있다. 상기와 같이 적용하였을 때, 일련의 버튼누름에 의한 한국어 입력중 다음글자의 초성자음으로 돌출되어 나타나게 되는 자음은 길게누름으로 확정하고, "

"를 입력하기 위한 "ㄱ"은 [ㄱ]버튼 길게 누름으로 "ㄱ"을 확정하는 일관성있는 사용이 가능하다. 또한 "아래아버튼장타처리"를 이용하여 현대 한국어 모음과 한글고어 모음간의 모호성이 있는 경우에도 단일한 규칙("

" 예외)으로 처리가 가능해진다. 또한 [ㅡ]버튼 또는 [ㅣ]버튼의 길게누름은 사용되지 않으므로, [ㅡ]버튼과 [ㅣ]버튼의 길게누름을 다른 용도로 활용할 수 있다. In the opinion of the applicant, a good application case is that in the case of "positional ambiguity of the initial consonant", the trailing alphabetic long hitting treatment is applied (except for "

= ㅡㆍㆍ~ㅣ"), and in the case of "ambiguity in the alphabet", the lower arburton long hitting treatment is applied, and for the "alphabet-character ambiguity", the preceding alphabet long hitting treatment is applied. When you do, the consonant that appears protruding as the first consonant of the next character among Korean input by pressing a series of buttons is confirmed as a long press, "

"ㄱ" for inputting "a" can be used consistently by confirming "ㄱ" by long pressing the [ㄱ] button. In addition, there is ambiguity between modern Korean vowels and Hangul archaic vowels by using the "Down Abort Long Hit Processing" Even if there is a single rule ("

It can be handled as "Exception) In addition, long-pressing of [ㅡ] button or [ㅣ] button is not used, so long pressing of [-] button and [ㅣ] button can be used for other purposes.

In the above, a technique that can input both Korean and Korean characters at the same time has been suggested.

31.3 Extended Marking Method and Display Method using Hangul Gore (Old Hangul)

31.3.1 Hangul extended notation method

There have been attempts from the past to indicate pronunciation of foreign languages that are not in Korean. The first approach is to use the old Hangul (old Hangul), which is not currently used, and the second, to create a new alphabet corresponding to the pronunciation of a foreign language.

"Byeongseo" is a method of expressing new pronunciation by writing Korean alphabets side by side, such as "ㄲ", "ㅄ", "ㅳ", "ㅴ", ..., and "Yeonseo" is "ㅸ", It is a method of expressing new pronunciation by writing Korean alphabets vertically, such as "ㆄ", ..., etc.

", "

", "

","

", ... 등을 들 수 있다. 우리 한글의 옛글자까지 포함된 모음은 워낙 다양한 복모음이 가능하므로 (유니코드상의 한글 모음 약 100글자) 외국어 표기에 있어서도 별로 논란이 되지 않고 있다. 그리고 실제로 실질적인 음가를 가지고 있는 것이 자음이기 때문이기도 한 것 같다. 옛한글을 포함하는 한글자모를 사용하여 현대 한국어 발음으로 사용되지 않는 외국어 발음을 표기함에 있어서, 다음의 몇가지 원칙을 생각해볼 수 있다. Representative foreign language sounds that do not have the same pronunciation in modern Korean are "v", "f", "r"('r' as a slang sound), "z", "

", "

", "

","

", ..., etc. There is not much controversy in foreign language notation as well, because vowels including old Korean characters can have so many different vowels (about 100 Korean vowels in Unicode). It seems that it is also because consonants are consonants that have a substantial phonetic value, and the following several principles can be considered in marking the pronunciation of foreign languages that are not used in modern Korean pronunciation by using Hangul characters including the old Hangul.

First, when the marked letter is pronounced by the general public, or when there is a simple explanation, it should be possible to have a similar pronunciation.

Second, if there is a method by Byeongseo or Yeonseo that can properly express the pronunciation, consider the method by Byeongseo and Yeonseo first rather than creating a new letter.

Third, in the case of Byeongseo or Yeonseo, it is recommended that the letters that are the basis of the sound appear first.

Hereinafter, a method of indicating the pronunciation of a foreign language will be described mainly using byeongseo (hereinafter,'byungseo' is used as a concept including'yeonseo').

"라고 표기한 경우도 있었다. "v"발음 윗이빨을 아랫입술에 살짝 대어 발음하는 "v"의 발음에 "

"라는 표기가 더 적절하다고 할 수 있다. 그러나 이러한 "

" 표기에는 약간의 문제가 있다. 먼저 현대 한국어 발음에서 자음 "X"에 "ㅢ"가 결합된 글자의 현실 발음은 "Xㅣ"로 거의 통합되고 있다. 예를 들어 "희"의 경우 정확한 발음은 "흐이"를 1음절로 빨리 발음하는 것이나, 현실 발음은 "히"로 발음되고 있는 현상이 있는 것이다. "ㅢ"의 발음이 정확히 살아 있는 경우는 음가가 없는 "ㅇ" 다음 순수하게 모음 "ㅢ"가 나오는 경우로 보인다. 예를 들어 "의자" 에서 "의"는 정확하게 "으이"가 1음절로 빨리 발음되는 형태로 발음되고 있다. 또 한가지 문제는 "bi"와 "vi"에서 자음이 달라졌는데도, 한글 표기에서는 같은 자음(즉, "ㅂ")을 사용하고, 모음의 표기가 달라져야 하는 것(즉, "비", "

")도 표기의 불일치를 준다. 모음을 달리 표기하여 각기 다른 자음의 발음을 표현한 사례는 "show" 의 "" 발음을 "s"와 동일한 "ㅅ"으로 표기하면서 모음을 "ㅛ"로 사용한 사례(즉 "쇼" 또는 "쑈")도 있다. Currently, both the pronunciation of "b" and the pronunciation of "v" are expressed as "ㅂ" in Korean, so different "b" and "v" cannot be distinguished. When the alphabet "b" is written in Korean, it is expressed as "B", and when the alphabet "v" is written in Korean, it is written as "V". In the past beginner English books, "v"

In some cases, "v" is pronounced. "v" is pronounced by gently placing the upper teeth on the lower lip.

"It can be said that the notation is more appropriate. However, this "

"There are some problems with the notation. First, in the modern Korean pronunciation, the actual pronunciation of a letter in which "ㅢ" is combined with the consonant "X" is almost integrated into "Xㅣ". For example, in the case of "Hee", the correct pronunciation is correct. Is pronounced "Hui" as one syllable quickly, but the actual pronunciation is pronounced as "Hee." If the pronunciation of "ㅢ" is exactly alive, then the pure vowel after "ㅇ" without a phonetic value " This seems to be the case where "ㅢ" appears. For example, "ui" in "chairs" is pronounced in a form where "oui" is pronounced quickly in one syllable. Another problem is that consonants are pronounced in "bi" and "vi". Although different, in Korean notation, the same consonant (that is, "ㅂ") is used, and the notation of vowels should be different (that is, "bi", "

") also gives inconsistency in notation. The case of expressing the pronunciation of different consonants by different vowels is the case of using the vowel as "ㅛ" while the "" pronunciation of "show" is marked with "ㅅ", which is the same as "s" There are also (ie, "show" or "show").

Traditionally, it has been pointed out that it is appropriate to express the "v" pronunciation using the copulation "k". If you literally interpret "Popyeongeum", it becomes "light lips", and it is possible to explain that it is closer to the pitch of "v". Of course, there is no way to know what the exact sound of the past cop sound "ㅸ" was. Similarly, there were opinions about the pronouncing "f" as "ㆄ". In the above, examples of notation of representative "v" and "f" pronunciations have been described. Some of the existing opinions on notation of "v" and "f" pronunciations are summarized as follows.

v: "ㅸ", "ㅎㅂ" (byungseo), "ㅂㅎ" (byungseo), ...

f: "ㆄ", "ㅎㅍ" (byungseo), "ㅍㅎ" (byungseo), ...

In the above, the suggestion to use "ㅍㅎ" as the pronunciation of "f" seems to have originated from the fact that the spelling "ph" is mainly pronounced as "f" in English. In the same logic, it can be seen that a plan came out to use "ㅂㅎ" for "v" pronunciation.

In Korean, "flat consonant + ㅎ" or "he + flat consonant" sounds as "lattice consonant". For example, "a lot" sounds as "manta", so you can see that "he+c" sounds as "ㅌ", and "eaten" sounds as "mucky", so "a+ㅎ" is "ㅋ "You can see that it sounds. Here, it cannot be proved whether "flat consonant + heh" or "he + heh + heh" is correct, and it can be said that both are correct as in the case above. It is easy to understand that "ㅎ", which has the sound of "h", is combined with ordinary sounds (flat consonants, eg, "ㄱ") to produce sounds such as "ㅋ", "ㅌ", "ㅍ", ... Can be. In phonetics, it seems to be expressed in difficult words that are organic sounding. In other words, it can be seen that when "ㅎ" is combined, the original sound (eg "ㄱ") becomes a little stronger. Since it is obvious that "ㅂㅎ" corresponds to the "ㅍ" pronunciation, it is inappropriate to express the "v" pronunciation, and similarly, expressing the "f" pronunciation with "ㅍㅎ" is inappropriate.

Traditionally, phonetics have used the systematic classification of voices by articulation points and articulation methods, and Korean Hangul can also be said to be a scientific product created by the excellent insight and intuition of the phonetician King Sejong. However, it seems unreasonable that the general public should understand and use the knowledge of phonetics for pronunciation in foreign languages.

In the case where "ㅂ+ㅇ" is combined with the pronouncing "ㅸ" as an initial consonant, it can be recognized as a combined pronunciation of "ㅂ" and "ㅇ" from the perspective of the public, not the phonetician. Since “is not sound,” it can be recognized that the pronunciation of “ㅂ” is weakened. Also, from the perspective of the general public, not the phonetician, the “v” pronunciation is perceived as weaker pronunciation than the “b” pronunciation, so it can be said that expressing “v” with the pure consonant “ㅸ” is valid.

"라고 표기했던 적이 있는데, 순경음 "ㅸ"을 이용하여 "

"라고 표기하였을 때와 비교해 보면 공통점이 있음을 알 수 있다. "

"라고 표기해 놓고 사전 지식이 없는 일반인에 읽어 보라고 하면 어떻게 읽을지 고민하다가, 1차적으로 "ㅂ"과 "ㅇ"을 분해하고 "(브)"라는 "ㅂ"발음을 앞에 두고, 그 다음 남아 있는 "이"와 붙여서 빨리 발음하려고 할 수 있다. (이는 "ㅝ"를 발음할 때 "ㅜ"와 "ㅓ"를 빨리 발음하면 "ㅝ"가 되는 것을 생각할 수 있다. 모음의 경우는 복모음이 완전하게 단모음의 조합으로 설명되나, 다음에 설명하는 자음의 경우는 약간 다른 듯 하다) 즉 "(브)" 로 음절이 체 완성되기 전에 "이"와 붙여서 발음하면 현재 표기하고 있는 "브이"를 빨리 발음한 결과와 유사하게 된다. 다음으로 이는 "

"의 발음과 유사하게 된다. 물론 "

"의 발음 역시 "v"와 완전히 일치하는 것은 아니므로 "

" 의 표기를 "v"로 정의하고 발음하게 하는 "교육"이 필요하게 된다. 다만 "그렇듯한" 그리고 "타당해 보이는" 표기를 해당 발음으로 "정의"하는 것이 필수적이다. 예를 들어 "ㄲ"을 모르고 "ㄱ" 의 발음만 알고 있는 사람이 "ㄲ"을 보고 어쩐지 "끄"하고 발음하고 싶은 생각이 든다면, 그리고 "ㅋ"을 모르고 "ㄱ"의 발음만 알고 있는 사람이 "ㅋ"을 보고 어쩐지 "크" 라고 발음하고 싶다면 "그럴듯한" 좋은 표기인 것이다. 여기에 이론과 교육이 더해져 "ㄲ"은 "ㄱ"을 좌우로 배열한 글자 이므로 "끄"라는 소리가 난다는 배경이 설명된다면, 사용자는 "ㄲ"의 표기와 그에 따른 발음을 매우 자연스럽게 사용할 수 있게 되는 것이고 이러한 점이 우리 한글의 과학성 중의 한가지라고 할 수 있을 것이다. In modern Korean, "v" is written as "V", and in the past, "

I used to write "", but by using the pure sound "ㅸ"

If you compare it with the words "", you can see that there is something in common."

If you mark "" and ask a general person without prior knowledge to read it, you will be thinking about how to read it, and then first disassemble "ㅂ" and "ㅇ", put the "ㅂ" pronunciation of "(B)" in front, and then remain You can try to pronounce it quickly by attaching it with a "이" (this is when you pronounce "ㅝ", you can think that if you pronounce "ㅜ" and "ㅓ" quickly, it becomes "ㅝ". In the case of vowels, the vowels are completely vowels. It is described as a combination of short vowels, but the consonants described below seem to be slightly different.) That is, if the syllable is pronounced with "i" before the completion of the syllable as "(B)", the current "V" is quickly displayed. It becomes similar to the result of pronunciation. Next, it is "

It becomes similar to the pronunciation of ". Of course "

The pronunciation of "also does not completely match "v", so"

"Education" is needed to define and pronounce the notation of "as "v", but it is essential to "define" the notation "so" and "appropriate" as the corresponding pronunciation. For example, "ㄲ If a person who does not know "b" and only knows the pronunciation of "ㄱ" sees "ㄲ" and somehow wants to pronounce it with "off", and a person who does not know "ㅋ" and only knows the pronunciation of "ㄱ" is "ㅋ" It is a good notation if you want to pronounce "big" by looking at "Like". The theory and education are added to this, and the background explains that "ㄲ" is a letter arranged with "ㄱ" left and right, so it sounds "off". 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 features of Korean Hangul.

" 로 표기하고 이를 "v"발음으로 사용하자는 주장도 있으나, "

" 의 표기와 "v"발음간의 어떠한 상관관계도 없음에도 불구하고 그 표기법을 주장하는 것은 타당하지 않아 보인다. Some inventors put an upper point on "rain"

There are claims to mark it as "and use it as the pronunciation of "v", but"

Even though there is no correlation between the notation of "and the pronunciation of "v", it does not seem reasonable to assert that notation.

"으로 표현하는 것이 타당하다면, "v"와 유사계열의 발음은 "f" 역시 "ㆄ" 또는 "

" 으로 표기하는 것이 가능하다. If the "v" is pronounced, the pure consonant "ㅸ" or "

If it is appropriate to express "v", the pronunciation of "v" and similar series is "f" also "ㆄ" or "

It is possible to mark it as ".

"의 경우는 가장 유사한 현대 한국어 발음이 "ㄷ"이라고 할 수 있다. 또한 동시에 "ㄷ"보다는 약한 느낌의 발음이다. 따라서 "ㄷ"과 "ㅇ"이 상하로 연서 또는 좌우로 병서된 글자로 표기하는 것을 생각할 수 있다. 이하에서 자음 "X"와 이응 "ㅇ"이 순서대로 연서 또는 병서된 글자는 같은 글자로 간주하며 그 이유는 아래에서 별도로 설명한다. 일반인의 관점에서 보면 "

ㅣ" 를 발음할 때 "(드)"라는 음절이 완전히 형성되기 이전에 "이" 와 빨리 합쳐져서 발음되므로 "ㄷ"과 "ㅇ"(음가 없음)의 중간 발음 (즉, "ㄷ"의 발음이 약화된 발음) 정도로 발음을 시도해 볼 수 있을 것이다. 이렇게 시도한 발음이 비록 "" 발음과 완전히 일치하지 않더라도 유사하다면(최소한 강약의 느낌에 있어서), 상기 표기를 "" 발음의 표기로 검토해 볼 수 있는 것이다. 영어의 "this"에서 "" 발음을 "

ㅣ" 와 같이 표기할 수 있게 된다. 음성학자가 아닌 일반인인 본 발명자의 느낌으로는 "

" 를 표시하는데 "ㄷ"와 여린ㅎ "ㆆ"을 연서 또는 병서한 형태도 가능해 보인다. 물론 음성학자의 관점에서 보면 "유성음"인 ""의 발음을 "

" 또는 "

" 으로 표기하는 것이 부정확하므로, "

" 표기하기 위한 새로운 글자를 만드는 것이 정확하다는 주장을 할 수도 있다. to the next "

In the case of "," the most similar modern Korean pronunciation can be said to be "ㄷ". Also, it is a pronunciation that has a weaker feeling than "C". Therefore, "ㄷ" and "ㅇ" are written in vertical or horizontal lines. In the following, the consonant "X" and the translation "ㅇ" in this order are regarded as the same letter, and the reason will be explained separately below.

When pronouncing ㅣ", the syllable "(de)" is quickly combined with "i" and pronounced before the syllable is completely formed, so the middle pronunciation of "c" and "ㅇ" (no sound) (that is, the pronunciation of "c" is You can try to pronounce the pronunciation as a weakened pronunciation). If the pronunciation you tried like this is similar (at least in terms of the feeling of strength and weakness), even if the pronunciation you tried does not completely coincide with the "" pronunciation, you can examine the above notation as the notation of the "" pronunciation. The pronunciation of "" in "this" in English is "

It can be written as "I". As the present inventor, who is not a phonetician, feels "

It is possible to express "ㄷ" and "ㆆ" in parallel or in parallel. Of course, from a phonetician's point of view, the pronunciation of "", which is "voiced", is ""

" or "

Since it is incorrect to write "

"You might argue that it is correct to create new letters for marking.

" 발음의 경우는 현대 한국어에서 가장 유사한 기본 발음이 "ㅆ"이라고 볼 수 있다. "

" 발음이 "ㅆ"보다 약한지는 모르겠으나, "ㅆ"보다 강한 발음이라고는 느껴지지 않는다. 따라서 "ㅆ"과 "ㅇ"을 상하로 연서하여 "

"로 표현할 수 있다. "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 feel that it's stronger than "ㅆ". Therefore, "ㅆ" and "ㅇ" are linked up and down to "

You can express "though" with "

ㅗㅌ" or "

If it is written as ㅗ트" (it should be written as a conjugated letter, but for convenience, the neutral vowel and the final consonant are added together), before the pronunciation of "(write)" is formed, "

"Or in combination with "oat."

Not the same pronunciation as ", but "

"If it feels similar to pronunciation,"

"" can be used as a notation for the pronunciation of "". When "thank you" in English is written in the current Korean language, it is also called "Sengkyu", and some people also write it as "Thank you". Therefore, "ㄸ+ㅇ" It seems that it is possible to apply the form of a serial (or byeongseo).

"의 경우는 현대 한국어에서 가장 유사한 발음은 "ㅅ" 이다. 역시 "ㅅ"보다는 약한 느낌의 발음이다. 따라서 "ㅅ"을 기본 글자로 하고 역시 연서 또는 병서된 글자인 "

" 또는 "

" 로 표현할 수 있다. "show" 를 "ㅅㅇㅗ" (자모결합 글자로 표기되어야 하나 편의상 중성모음과 종성자음을 늘어 썼음)로 적으면 일반인은 "(스)"라는 음절이 완성되기 전에 "오"와 결합되는 식으로 발음하는 것을 고민할 수 있다. 우리 한글에서 "ㅣ+ㅗ = ㅛ"인데 "ㅡ+ㅗ"는 "ㅛ"는 아니지만 유사한 발음의 변형이 될 것으로 짐작된다. "ㄱ"이 "ㅎ"과 합쳐지면 "ㅋ" 소리가 나는데, 일반인의 느낌으로 "" 발음은 기본이 되는 "ㅅ"(또는 "ㅆ")에 "ㅎ"이 합쳐진 소리보다는 많이 약하지만, "ㄱ+ㅎ"의 경우 처럼 "흐"하는 기운이 아주 약간 섞여 있는 느낌이 있다. 따라서 시옷과 여린ㅎ이 좌우로 병서된 "ㅅㆆ"로 또는 상하로 연서된 글자로 표현될 수도 있어 보인다. "z"는 반치음 "ㅿ" 으로 표기하자는 주장이 있다. "

In the case of ", the most similar pronunciation in modern Korean is "ㅅ". Again, it has a weaker feeling than "ㅅ". Therefore, "ㅅ" is used as the basic letter, and "ㅅ" is also a continuous or parallel letter, "

" or "

It can be expressed as ". If you write "show" as "ㅅㅇㅗ" (it should be written in letter conjugated letters, but for convenience, neutral vowels and final consonants are used in a row), the general public will say "oh" before the syllable is completed. It is possible to think about pronunciation in a way that is combined with ". In Korean Hangul, "ㅣ+ㅗ = ㅛ", but "ㅡ+ㅗ" is not "ㅛ", but it is assumed to be a variation of similar pronunciation. "ㄱ" is When combined with "ㅎ", "ㅋ" sounds, but as a general public's feeling, "" pronunciation is much weaker than the basic "ㅅ" (or "ㅆ") plus "ㅎ", but "ㄱ+ㅎ" As in the case of the case, there is a feeling that there is a very slight mixture of the energy of "flowing", so it seems that it can be expressed as "ㅅㆆ" in parallel with shiot and softness, or in vertically connected letters. "z" is half chieum There is an argument that it should be marked as "ㅿ".

"은 현대 한국어의 "ㅈ"과 가장 유사한데 "ㅈ"보다는 부드러운 발음으로 느껴진다. 따라서 "

" 또는 "

"으로 할 수 있다. "d"은 "" 보다 강한 발음이다. 따라서 "ㅉ+ㅇ"의 연서(또는 병서) 형태로 표기하는 것을 고려할 수 있다. "church" 등에서 나타나는 "ch"에 대응되는 발음은 현재 "ㅊ"으로 통용되고 있으므로 언급하지 않는다. "

"" is most similar to "ㅈ" in modern Korean, but it feels softer than "ㅈ". Therefore, "

" or "

It can be done with ". "d" is a stronger pronunciation than "". Therefore, it can be considered in the form of "ㅉ+ㅇ" in the form of a serial (or byeongseo). Pronunciation corresponding to "ch" in "church" etc. Is currently used as "ㅊ", so it is not mentioned.

" 또는 "

" 과 같이 표기할 수 있다. The pronunciation of "l" in English is written as "ㄹ" in modern Korean, and there seems to be no objection. If "l" in English is "ㄹ", then "r" in English uses "ㄹ" as the basic sound and can be seen as a weaker pronunciation than "ㄹ".

" or "

It can be written as ".

In the above, we have explained how to mark some representative pronunciations in English but not in Korean modern Koreans using existing Korean alphabets. The above can be similarly applied to the pronunciation of other languages.

31.3.2 How to display extended Korean

Displaying the pronunciation of a foreign language that is not in the above-described modern Korean will be referred to as “extended Hangeul” for convenience. It is a concept that includes both the use of the old Hangul in Unicode and the methods described above.

The characters in Unicode in Fig. 4-33(*) are the registered Hangul Gore in the old documents as Unicode. Therefore, if you look at the Unicode in Fig. 4-33(*), you can observe the letters used in old documents. By the way, if you look at the letters "X+ㅇ" or "ㅇ+X" linked or parallel, you can see that there is "X+ㅇ" and "ㅇ+X" at the same time. Here, "X" is an arbitrary consonant, and "ㅇ" is "Yes". In other words, the pronunciation of the letter "X+ㅇ" and the pronunciation of the letter "ㅇ+X" are different from each other, and it is guessed that they were trying to express the differences in subtle pronunciations, respectively. Of course, to confirm this, an in-depth investigation into the old literature is required, but the inventors who are not Korean language scholars cannot afford to do so.

"과 같이 병서된 글자가 유니코드에 있으면 "

"과 같이 연서된 글자는 없는 것이다. 단 하나 예외처럼 보이는 것이 "

" 과 "

"인데, "

"에서의 이응은 "옛이응" 이므로 "

"에서의 "ㅇ"과는 다르다고 할 수 있다. 결국 "X+ㅇ" 형태에서 연서된 글자가 유니코드에 존재하면 병서된 글자는 유니코드에 없고, 반대로 병서된 글자가 유니코드에 존재하면 연서된 글자는 유니코드에 존재하지 않는다고 할 수 있다. 이를 정리하면, "X+ㅇ" 형태의 글자를 상하 연서 또는 좌우 연서로 표현한 것은 2가지 다 같은 발음을 나타내는 것으로 정의할 수 있는 것이다. The content described below is the core of the present invention. The important thing is that if there are letters "X+ㅇ" that are vertically connected, there are no letters that are horizontally connected. For example, if there is a concatenated character such as "ㅸ" in Unicode, then a parallel character such as "ㅂㅇ" is not in Unicode (that is, in old literature). Likewise "

If there is a parallel character such as "in Unicode"

"There is no such thing as "there is no one that looks like the only exception"

"And"

"But,"

"In the case of "Yes," so "

It can be said that it is different from "ㅇ" in ". In the end, if a letter concatenated in the form of "X+ㅇ" exists in Unicode, the concatenated character is not in Unicode. On the contrary, if a concatenated character exists in Unicode, the concatenated character It can be said that letters do not exist in Unicode, in summary, the expression of "X+ㅇ" type letters in upper and lower consecutive letters or left and right joints can be defined as having the same pronunciation.

Next, a method of expressing such a series of letters or words will be explained. In Korean Hangul, the consonant is on the left and the vowel is on the right (eg, "a". For convenience, the consonant is on the top and the vowel is on the bottom). There are forms (eg, "old". For convenience, (2) form or vowel bowl type), and there are intermediate forms (for convenience, (3) form, eg, "family").

"로 표시하고, 모음 "ㅜ"와 결합하면 "

"와 같이 좌우로 병서된 형태로 표시되는 것이 바람직하다. (3)번형태의 경우는 연서 또는 병서 중 어느 한가지를 적용할 수 있는데, 절충방안으로는 유니코드에 있는 형태(연서 또는 병서)대로 적용하는 방안이 있을 수 있다. 예를 들어, "ㅸ"은 유니코드에 상하 연서 형태로 있으므로 "ㅘ"와 결합시 연서형태로 표시하는 것이고, "

"은 좌우 병서 형태로만 유니코드에 있으므로 "ㅘ"와 결합시 병서 형태로 표시하는 것이다. (3)번형태를 표시하는 방법은 초성자음만이 입력되었을 때도 유용하게 응용될 수 있다. 모음이 입력되기 전에 초성자음으로써 "X+ㅇ"형태의 자음이 입력되면, 상하 연서로 표시할 지, 좌우 병서로 표기할 지 정하기 어려운데, 유니코드의 기본형을 표시할 수 있는 것이다. 예를 들어 처음 입력상태에서 "ㅂ"와 "ㅇ"이 눌러져서 초성자음 "X+ㅇ"가 인식되었을 때, 유니코드에 있는 상하 연서로 "ㅸ" 으로 표시할 수 있는 것이다. 그 다음에 "ㅡ" 또는 "ㅜ"가 입력되면 "

" 또는 "

"로 표시되는 것이다. 만약 초성자음 "ㅸ" 다음에 "ㅣ"가 입력된다면 "

"로 표시될 것이다. 이는 "

"에 대해서도 마찬가지이다. Therefore, when expressing consonants in the form of "X+ㅇ" as an initial consonant, it is preferable to display them in a vertically connected form in (1) above, and in a horizontally parallel form in (2) above. It is desirable. In the form (3) above, a serial or parallel form can be selectively applied. For example, in Unicode, only the vertically connected form such as "ㅸ" is presented, but when combined with the "ㅏ" vowel, "

", and combined with the vowel "ㅜ", "

It is desirable to be displayed in a horizontally parallel form such as ". In the case of form (3), either serial or bilingual can be applied. As a compromise, the form in Unicode (serial or bilingual) There may be a way to apply it. For example, "ㅸ" is in the form of a vertical link in Unicode, so when combined with "ㅘ", it is displayed in a link form, and "

"Is in Unicode only in the form of left and right byeongseo, so when combined with "ㅘ", it is displayed in byeongseo form. The method of displaying form (3) can be usefully applied even when only the initial consonant is input. Vowels are input If a consonant in the form of "X+ㅇ" is input as an initial consonant before it is entered, it is difficult to determine whether to display it in vertical or horizontal lines, but it is possible to display the basic form of Unicode. When ㅂ" and "ㅇ" are pressed and the initial consonant "X+ㅇ" is recognized, it can be displayed as "ㅸ" in the upper and lower concatenation in Unicode. Then, when "ㅡ" or "ㅜ" is entered, ""

" or "

". If "ㅣ" is entered after the initial consonant "ㅸ", "

Will be displayed as ". This is "

The same is true for ".

"과 같이 표시할 수 있다. 네모꼴로 표현되는 자모결합글자에서 종성자음이 위치할 공간을 확보하기 위해서이다. 표시되는 순서는 "ㅸ" 이 소정의 수단(예. "ㅂ"과 "ㅇ"의 순차입력 또는 특정 문자입력시스템에서 정해진 수단)에 의하여 "ㅸ"이 초성자음으로 인식되었을 때는 "ㅸ"으로 표시되고, 이어서 "ㅣ"가 입력되면 "ㅸㅣ"로 표시되고, "ㄱ"이 입력되면 "

" 이 표시되는 것이다. In the above (1), (2), and (3) forms, there is a case where there is no final consonant, but when there is a final consonant (eg "Gak", "Guk", "Kwak". For convenience, (4)) In the form), "X+ㅇ" as an initial consonant can be expressed in the form of left and right byeongseo or vertical linkage according to the form of (1), (2), (3) above, regardless of the presence or absence of the final consonant, and the ( As in form 1), the initial consonant "X+ㅇ" can also be displayed. In the case of a letter with a final consonant, even if the vowel-like vowels are combined, the left and right characters are displayed in order to secure an area where the final consonant is located. For example, even if the vowel type “ㅣ” is combined, if there is a final consonant “ㄱ”, the first consonant is left and right, and “

It can be expressed as ". This is to secure a space for the final consonant to be placed in the conjugated letters expressed in a square shape. The order of display is "ㅸ" by a predetermined means (eg "ㅂ" and "ㅇ"). When "ㅸ" is recognized as an initial consonant by sequential input or a specific character input system), it is displayed as "ㅸ", and when "ㅣ" is input, it is displayed as "ㅸㅣ", and "a" is input. When it becomes "

"Is displayed.

" 을 종성자음으로 사용하는 경우 비록 유니코드에는 상하 연서의 형태로 되어 있으나, "

" 형태로 표시하는 것이 바람직하다. 예를 들어 "

" 과 같이 "ㄹ+ㅇ"을 좌우 연서로 표시하는 것이 상하 연서로 표시하는 것보다 형태적인 안정감을 주는데 훨씬 도움이 된다. 이는 "X+ㅇ" 형태의 모든 자음이 종성자음으로 사용될 때 동일하게 적용될 수 있다. The consonants connected up and down appear only in the form of "X+ㅇ". Even if the letter of the "X+ㅇ" type exists only in the form of upper and lower concatenation in Unicode, it is preferable that it is always displayed in left and right concatenation when used as a final consonant. For example, to indicate the pronunciation of "~er" in English, "

In the case of using "as the final consonant, although Unicode is in the form of upper and lower concatenation,"

It is desirable to display it in the form of ". For example "

Displaying "ㄹ+ㅇ" in left and right consonants, such as ", is much more helpful in giving a sense of morphological stability than displaying in vertical consonants. This can be applied equally 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"를 두는 형태로 표시되는 것이 바람직하다. 예를 들어 "ㅴ"을 삼각형 형태로 표시하면 "

" 가 된다. 이렇게 하는 것이 우리 한글의 형태미를 살리는데 훨씬 도움이 된다. Taking one step further, a look at the form of three or more alphabets used in Korean Gore (Old Hangul) is as follows. There are "XXX" type, "XYY" type, "XXY" type, and "XYZ" type. An example of "XXX" is "

", and the example of type "XYY" is "

", and the example of the "XXY" type is "

", and an example of the "XYZ" type is "ㅴ". In the case of the "XXX" type, it is displayed in the form of placing "XX" under the "X" in the form of a triangle, or in the form of an inverted triangle. It is preferable to display "X" under "XX". For example, "

When "is displayed in the form of a triangle,"

In the case of "XYY" type, it is preferable to display "YY" under "X" in a triangular shape. For example, "

When "is displayed in the form of a triangle,"

In the case of the "XXY" type, it is preferable to display a "Y" under "XX" in the form of an inverted triangle. For example, "

If "is displayed in the form of an inverted triangle,"

The "XYZ" shape is preferably displayed in the form of placing "YZ" under "X" in a triangular shape, or placing "Z" under "XY" in the form of an inverted triangle. For example, "T". When "is displayed in the form of a triangle,"

This is much more helpful in saving the beauty of Korean Hangeul.

" 을 표시하려면, "

"에 대응되는 새로운 코드를 유니코드에 등록하여야 하는 것이 아닌가 의심할 수도 있다. 그러나 낱자로의 유니코드를 사용하여 자모결합된 글자를 표현한다면 (예. 첫가끝조합형, .... 등등), 순경음 "ㅸ" 의 유니코드를 그대로 사용할 수 있다. 단, 버튼의 눌러짐에 따라 한글조합을 처리함에 있어 모음우치형의 모음(예. "ㅏ")이 입력되면 상하 연서된 형태(예. "ㅸ")로 처리하고, 모음하치형의 모음(예. "ㅡ")가 입력되면 좌우 병서된 형태(예. "

")로 처리하는 것이다. 이는 다른 "X+ㅇ" 형 자음에 대해서도 마찬가지이며, "XXX"형, "XYY"형, "XXY"형, "XYZ"형 자음에 대해서도 마찬가지이다. Not in Unicode

To display ", "

You may be wondering whether a new code corresponding to "should be registered in Unicode. However, if you use single-character Unicode to represent letters concatenated (eg, first-to-end combination, .... etc.), You can use the unicode of the pure Kyung sound "ㅸ" as it is, but when a vowel-like vowel (eg "ㅏ") is input in processing the Hangul combination as the button is pressed, the upper and lower concatenation (eg. "ㅸ"), and when a vowel bottom-type vowel (ex. "ㅡ") is input, the left and right side by side (ex. ")

This is the same for other "X+ㅇ" type consonants, and the same for "XXX" type, "XYY" type, "XXY" type, and "XYZ" type consonants.

32. Input of spaces, numbers, and English alphabet in Korean mode

32.1 Entering a space

In the above, it was suggested to solve the ambiguity when entering Hangul Gore without using a separate button. In the drawing 15-3 keypad adopted by Samsung Electronics, the [#] button, which is not directly used for character input, is used as both a separator button and a blank button. In reality, the right movement button (usually a right arrow or similar symbol is displayed on the button) among the up/down/left/right movement buttons is used as both a separator button and a blank button, and is not a single word input. In the case of entering a sentence, it is not meaningful to use the [#] button for this purpose as the up/down/left/right movement buttons are actually essential for editing the previously entered sentence. However, there may be a requirement to enter spaces within 12 buttons including 10 numeric buttons and [*] and [#] buttons.

In the applicant's earlier application, it was shown to input "y = xㅡㅡ", and it is obvious that this can be applied to input of special characters or spaces. In the case of inputting only modern Korean, a case where pressing the [ㅡ] button or [ㅣ] button twice after the input of a consonant (eg, "ㄹ") without a trellis or hard consonant (i.e. double consonant) is treated as a blank have. For example, "space = ㄹㅣㅣ". This has a disadvantage in that a space cannot be added between words when the right movement button is used as a blank button, and in this case, it can be useful. For example, after entering "Kanada", in order to add a space between "A" and "B", place the cursor on "I" with the move button and press the right move button again, the space is not added. In this case, as illustrated above, "space = ㄹㅣㅣ" can be added. After a blank is entered, vowels do not appear in succession in the input start state (ie, immediately after blank input) in Korean, so pressing the [ㅣ] button once more can be treated as having entered the blank once more. For example, it can be done with "2 blanks = ㄹㅣㅣㅣ".

In the case of inputting Korean archetypes, press the [ㅡ] button or the [ㅣ] button unless you apply the “post-alphabetic long hitting process” for the “alphabet-character ambiguity” or the “vertical/horizontal vowel hitting process” is applied. There is no case of long press. Therefore, one of long press of [ㅡ] button or [ㅣ] button can be processed as blank input. If the [ㅣ] button is pressed for the first time and a space is input for the first time, the character does not start as a vowel after the space in Korean, so that the pressing of the [ㅣ] button once more will be treated as inputting the space again. I can. For example, "2 spaces = ㅣ~ㅣ", 3 spaces = ㅣ~ㅣㅣ", .... Of course, you can enter "2 spaces = ㅣ~ㅣ~". .

Treating a vowel button pressed after a blank (eg [ㅣ] button) as a blank (eg, "2 spaces = ㅣ~ㅣ") has the disadvantage of making it difficult to enter a single vowel after the blank. In our literal life, single letter vowels starting with "ㅡ" like "ㅠㅠ" are used relatively frequently, but single letter vowels starting with "ㅣ" are not used very much. Therefore, it would be better to use long press of [ㅣ] button and continuous press after long press as input of blank and continuous input of blank.

Next, a long press of the [ㅡ] button can be used for other functions such as the "mode change" function. Since the mode switching function is not a frequently used function, it is not a problem to change the mode by long pressing. In reality, the [mode change] button will be provided as a separate button, so it has no practical meaning and only shows the possibility of doing so. Because if it is necessary to input letters such as "ㅠㅠ" rather than a complete word such as "name", "mutual name", ..., input of multiple words and sentences is required. This is because a liquid crystal for viewing words, sentences, ...), up/down/left/right movement buttons for editing, and mode change buttons will be provided separately.

32.2 Entering numbers in Korean mode

Currently, in the case of inputting modern Korean, the number is often input by long pressing the number button in the Korean mode. For example, if you press and hold the [a] button assigned to the number "1" in the Korean mode, the number "1" is entered. However, even in the keypad illustrated in Figure 4-*, inputting only modern Korean is possible without ambiguity (or very little ambiguity when input by repeatedly pressing "3+ other input method"), so long press of number buttons You can enter a number. However, in the case of inputting Korean Gore, long press of a consonant button (ie, a number button) may be used for "ambiguity of the initial consonant position". That is, in order to input Hangul Gore along with modern Korean, it is impossible to input numbers by long pressing of the number button.

In order to input a number of numbers such as a phone number or a resident number, it is not practical to input using a long press of a number button in the Korean mode, and it will be necessary to enter the number mode. However, it will be necessary to provide a means for inputting a number that is entered in the middle of Hangul input in Hangul mode. The following describes the technique of entering numbers in Korean mode.

As suggested by the applicant in the previous application, it has been suggested that "y = x + (maximum number of times you can press the collection button repeatedly + 1 more time)" can be entered. "Maximum number of times that the vowel button can be repeatedly pressed" means the maximum number of times that Korean combination is possible. In the above, "y" may be a "number", "x" may be an input consonant, and a "vowel button" may be a [-] button, a [ㆍ] button, or a [ㅣ] button. First, for example, when entering only modern Korean, it can be done as "K = ㄱㅡㅡㅡ", so "Number 1 = ㄱㅡㅡㅡㅡ". As another method, it is said that the [ㆍ] button is pressed up to 2 times after the consonant is input, so it can be set as "number 1 = ㄱㆍㆍㆍ". In the previous application, a technique was shown in which the [ㆍ] button is pressed three times as "ㅎ", which can be applied at the same time. The input value "ㄱㆍㆍㆍ" can also be interpreted as "ㄱㅎ", but if "ㅎ" is combined after the "ㄱ" initial consonant to form a conjugated letter, enter the number "1" as above. It can also be treated as. However, if the [a] button is pressed as a final consonant rather than an initial consonant among a series of button presses, the input must be made clearly indicating that "a" is a first consonant. For example, "Numer 1 = ㄱ~ㆍㆍㆍ" should be applied by applying "post-alphabetical long hitting treatment".

"가 결합된 글자로 될 수 있다. 그러나 현재까지 유니코드v2.0에 등록된 한글고어 모음에서도 "ㅡ"가 3개 연속결합된 모음은 존재하지 않는다. 따라서 "숫자 1 = ㄱㅡㅡㅡㅡㅡ"로 할 수 있다. 그러나 한글고어의 입력을 포함하면 "숫자 7", "숫자 9" 등의 경우는 도면4-34(a)에 있는 것처럼 훨씬 더 많은 횟수가 눌러져야 하는 문제가 있다. 한글고어의 입력을 포함하는 "아래아 3모음법"에서도 자음의 입력 다음에 [ㆍ]버튼은 최대 2번까지 눌러질 수 있다. 따라서 상기 "숫자 1 = ㄱㆍㆍㆍ"을 유사하게 적용할 수 있다. 다만 한글고어에서는 "xy" 형태의 자음이 초성으로도 나올 수 있으며, "y"위치에 "ㅎ"이 있는 경우(예. "

")도 있기 때문에 완전히 동일하게 적용하기 어렵다. Next, in the case of inputting Korean ancient words including modern Korean, the input of numbers in Korean mode is examined. "ㄱㅡㅡㅡㅡ" means "ㅋ" under "ㅋ"

"Can be a combined character. However, even in Hangul Gore vowels registered in Unicode v2.0 up to now, there is no vowel with 3 consecutive combinations of "ㅡ". Therefore, "number 1 = ㄱㅡㅡㅡㅡ However, if you include Hangul Gore input, there is a problem that a much more number of times must be pressed in the case of "number 7" and "number 9" as shown in Fig. 4-34(a). [ㆍ] button can be pressed up to two times after consonant input in "Haeah 3 vowel method" including Hangul Gore input, so the above "number 1 = ㄱㆍㆍㆍ" can be similarly applied. However, in Hangul Gore, consonants in the form of "xy" can also appear as an initial consonant, and if there is "ㅎ" in the "y" position (eg. "

") is also difficult to apply exactly the same.

In the case of repeatedly pressing the [ㅡ] button or the [ㅣ] button after inputting a consonant as described above, the number of repeated pressing of the button is too high, and it includes inputting a combination of vowel buttons to input Hangul Gore consonants. (Ref. Fig. 4-34(a)) has the disadvantage of excessively increasing the number of presses. Therefore, it can be done as "number y = xㅡ~" (ie, "number y = x *~) or "number y = xㅣ~" (ie, "number y = x #~"). "Is 10 numeric buttons from [1] to [0]. It is natural that this is applicable as long as long press of the [ㅡ] button or [ㅣ] button is not applied to the Hangul Gore input. For example, It can be done with the number "1 = ㄱㅣ~ = 1 #~". In summary, the input of numbers in Korean mode is "one press of a button with an array of numbers + a long press of a button with no numbers". It is a combination.

This can also be applied to Korean keypads of existing large manufacturing companies in Figures 15-3 and 15-4. In other words, the number input in the Korean mode is "one press of a number button + a long press of a button with no numbers". For example, in the keypad of Samsung Electronics in Fig. 15-3, the number "2 = ㆍ+ #~" can be used, and the number "4 = ㄱ + #~" can be used. In the keypad of Figure 15-4, you can do something like the number "2 = ㄴ + #~".

32.3 English alphabet input in Korean mode

In the above, the technique of entering numbers in the Korean mode was shown. Next, it is suggested to input the English alphabet in Korean mode. Usually, as shown in Fig. 1-1, an English keypad in which three alphabets are assigned to one button is mainly used. In addition, the syllables of Korean all the way to the Hangul Gore always start with a consonant and not a vowel. Therefore, the English alphabet assigned to the button can be input by inputting a number and vowel buttons of [ㅡ], [ㆍ], or [ㅣ] pressed after the number. This is because normal syllables do not start with vowels in Korean. When expressed as an expression, it becomes like "English alphabet y = number + collection button". For example, it can be "a = 2 + vowel button = ㄴㅣ-+ vowel button".

In a normal case, as shown in Fig. 1-1, about three English alphabets (eg "a b c") are arranged on one button (eg, [2] button). Each alphabet can be entered according to the vowel button [ㅡ], [ㆍ], or [ㅣ] button pressed after the number input. That is, the first arranged English alphabet (ex. "a") is "number 2 + ㅡ", the second arranged English alphabet (ex. "b") is "number 2 + ㆍ", and the third arranged English alphabet ( Ex. "c") can be "number 2 + ㅣ". For example, if you press the vowel button [ㅡ] button to the input of the English alphabet "a" (that is, the first arranged English alphabet), it becomes "a = 2ㅣ = ㄴㅣ~ ㅡ". When pressing the vowel button [ㆍ] button to the input of the English alphabet "b" (that is, the second arranged English alphabet), it becomes "b = 2ㆍ = ㄴㅣ~ ㆍ", and the English alphabet "c" (ie , If pressing the vowel button [ㅣ] button is applied to the input of the third arranged English alphabet), it becomes "c = 2ㅣ = ㄴㅣ~ ㅣ". If you enter "2a" it will be "2a = ㄴㅣ~ ㄴㅣ~ㅡ". In the display of the above input value, blanks are intended to improve readability and make the readers of this document more comfortable, but do not have meaning as described above.

In the above description, you may have doubts whether or not "English alphabet = number + repeated pressing of the vowel button". If pressing the [ㅡ] button once after entering the number is "a", pressing the [ㅡ] button twice as "b", and pressing the [ㅡ] button 3 times as "c". This is because there is ambiguity as in the iterative selection method of.

When the above is applied, if a single vowel (eg, "ㅠ") appears in succession with the number "2" (ie, "2ㅠ"), it is impossible to input it. Similarly, conventional means such as a time delay (ie, a timer) and a classification button may be applied. However, in reality, you will hardly ever enter "2ㅠ" like this.

As shown in Fig. 1-3, when four alphabets of "p", "q", "r" and "s" are assigned to the button [7], the three alphabets can be processed as described above. The other alphabet can be entered with "one of the 3 alphabets + non-pressed vowel button". For example, if you enter "p", "q", and "r" as "a", "b", and "c", respectively, "s = r + unpressed vowel button = p ㆍ or p ㅣ or It can be done with 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 the combination of pressing "Input of number" and "button in which Korean consonants are not arranged (more precisely, a button that does not start inputting consonants)" is pressed is shown 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 it like "~ㅡ". On the keypad in Figure 15-4, like "a = number 2+* = ㄴ#~*", "b = number 2+0 = ㄴ#~0", "c = number 2+# = ㄴ#~#" can do. In Figure 15-4, the reason why the [*] button (that is, the [overwrite] button) and the [#] button (that is, the [side by side] button) can be used for the last combination is " It is because the consonant input does not start by pressing the "*" button because it is set to ㅋ = ㄱ*".

Furthermore, the same can be applied to the case of inputting a number by long pressing of a button assigned with a number (usually, Korean alphabets are also arranged) in the Korean mode. If the number "2" in the 4-* keypad of the present invention is input by long pressing the [2] button (that is, the [b] button), a long press is applied to the alphabet input such as the preceding alphabet long hit processing and the following alphabet long hit processing. Under the premise that you don't do it), you can do it with "a = (number)2ㅡ = ㄴ~ㅡ = (button)2~ㅡ". For another example, even when the number 4 is input by long pressing the button assigned the number "4" (ie, the [4] button and the [a] button) in Fig. 15-3, the above description is the same. Can be applied. In Figure 15-3, after inputting the number "4 = ㄱ~ = 4~", if any button that does not start inputting consonants (eg, [ㅣ] button) is pressed once, whichever button is arranged in the [4] button. An alphabet (eg, "g", which is the first English alphabet) can be entered. That is, "g = ㄱ~ㅣ = 4~1". Similarly, you can enter "a = ㄴ~* = 2~*" in the keypad of Figure 15-4.

33. Korean input on a keyboard such as a PC

33.1 Hangul 2 Beolsik Keyboard Improvements in Korean Input

The 2beol-sik keyboard currently used as a standard in PCs is shown in Fig. 18-1(a). Fig. 18-1(b) shows only the left part including the letter button in Fig. 18-1(a). As everyone knows, when the [ㄱ] button marked "ㄱ" is pressed once, "ㄱ" is recognized. Also, "ㄲ" displayed above "a" indicates that "ㄲ" is recognized when the [ㄱ] button is pressed simultaneously with the [Shift] button. The question of whether "ㄲ" or the like is additionally displayed on the button is an optional matter (for example, a matter where "ㄲ" may or may not be additionally displayed on the [a] button).

On the current 2-beol-type keyboard, the [ㄹ] button ([F] button for the English keyboard's main function) is the reference button where the left index finger is located, and the [ㅓ] button (the [J] button for the English keyboard) is the right index finger. This is the reference button located. The left-hand area where the button is pressed with the left hand is 15 buttons on the left, including the [ㅅ], [ㅎ], and [ㅠ] buttons, and the buttons in the right-hand area where the button is pressed with the right hand are [ㅛ], [ㅗ]. There are 11 buttons on the right, including] and [ㅜ] buttons. The 11 character buttons in the right-hand area are based only on the buttons in which English alphabets are arranged. The consonant arrangement of the current standard 2 beolsik keyboard consists of 14 consonants: "ㄱ", "ㄴ", "ㄷ", ... "ㅍ", "ㅎ", and the vowels are "ㅏ", " Including "ㅐ" and "ㅔ" in 10 consonants of ㅑ", "ㅓ", "ㅕ", "ㅗ", "ㅛ", "ㅜ", "ㅠ", "ㅡ" and "ㅣ" It consists of 12 buttons. As a result, if 14 consonants are arranged in the left-hand region consisting of 15 buttons, one button remains, and if 12 vowels are arranged in the right-hand region consisting of 11 buttons, one button is insufficient. As a result, the current 2-beol-sik keyboard is a form that arranges the least frequently used "ㅠ" on the remaining buttons in the left hand area.

The keyboard is a device used by the autonomic nervous system as "hands" and "body" instead of "eyes" and "heads", unlike numeric keypad-type keypads. By the way, the presence of the vowel "ㅠ" in the left hand region, which can be seen as a consonant region, becomes an element that gives unnatural and unnatural feelings. This is the same for those who have used the Korean keyboard for more than 25 years, such as the applicant of the present invention, and when searching on the Internet, it is possible to easily search for cases that complain of inconvenience and point out the need for improvement for this reason.

The five hard consonants (double consonants) "ㄲ", "ㄸ", "ㅃ", "ㅆ", and "ㅉ" are the [Shift] button, and the "ㄱ", "c", "ㅂ", "ㅅ", It is recognized by simultaneously pressing the "ㅈ" button. For example, "ㄲ = Shift^ㄱ". Here, for convenience, "^" is used, and "^" is for expressing that the [a] button is pressed while the [Shft] button in front of it is pressed. However, in this case, "^" may be replaced with "+" indicating successive pressing. The same expression is indicated by "Shift+X" in the earlier application. In the expression of the input value, it is said that "+" may not be displayed, and sometimes "+" is displayed to make the input value easier to read, and sometimes "+" is not displayed, but it is the same expression. Even if expressed without "^" or "+" such as "Shft X", [Shift] is considered to be pressed with the next button pressed. In Windows OS, if you set the "Sticky Key" function to be used, you can input the same by pressing "Shift+X" sequentially instead of pressing "Shft^X" simultaneously. In the present invention, the fixed key Of course, it also includes cases where applicable. Using Shift is a factor 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 2-beol-sik Hangul automata slightly modified. For example, the original "ㅖ = Shift^ㅔ", "ㅒ = Shift^ㅐ" or "ㅖ" by pressing the [ㅔ] button twice (that is, "ㅖ = ㅔ+ㅔ") or [ It is mentioned that you input "ㅒ" by pressing the [ㅐ] button twice (that is, "ㅒ = ㅐ+ㅐ").

Among the five hard consonants, there have been constant attempts to arrange "ㅆ", which is used frequently, in one independent button. Professor K of S University, a scholar and inventor, places "ㅆ" on the [ㅠ] button (ie, the [B] button) in Fig. 18-1(a) or Fig. 18-1(b), and is the most difficult position to press. It was suggested to subtract "ㅔ" and place "ㅠ" at the position of the [ㅔ] button (ie, the [P] button) in the. "ㅠ" is recognized as one push of the [ㅠ] button (ie, the [P] button), but here, the "ㅔ" is recognized as a combination of the [ㅓ] button and the [ㅣ] button because it is not arranged on the button. That is, "ㅔ = ㅓ+ㅣ" and "ㅖ = ㅕ+ㅣ". Another person modified this slightly and placed "ㅆ" on the current [ㅠ] button (ie, "B" button), and recognized "ㅠ" by pressing the [TT] button twice (ie, "ㅠ=ㅜ +ㅜ") was also suggested. In the same way as inputting with "ㅖ = ㅔ+ㅔ" and "ㅒ = ㅐ+ㅐ", inputting with "ㅠ = ㅜ+ㅜ" was also used as a modified 2-beol-type automata on the keyboard. You can easily find it by searching the "Saenaru" input method on the Internet.

Among the five hard consonants (double consonants), the frequency of use of one "ㅆ" is about 1.5 times the sum of the frequencies of all the remaining four hard consonants. In the integrated frequency of consonants and vowels, "ㅆ" is ranked 20th and has a frequency of use of 1.135%, and "ㅠ" is ranked 33rd and has a frequency of use of 0.216%. Among the 30 consonants (including double endings), "ㅆ" is ranked 11th and has a frequency of use of 1.913%, and out of 21 vowels, "ㅠ" is ranked 17th and has a frequency of use of 0.513%.

"을 "ㅜ+ㅜ"로 입력하지 못하는 문제가 있다. 물론 "

= Shift^ㅜ"로 한다면, "ㅠ = ㅜ+ㅜ"로 할 수도 있다. 그러나 "ㅠ = ㅜ+ㅜ"로 한다면, 형태적으로 "ㅜ" 2개로 이루어진 모음인 "

"를 "ㅜ+ㅜ"로 입력하는 것이 가장 자연스러움에도 불구하고 그렇게하지 못하는 것이다. In the present invention, the most frequently used "ㅆ" among hard consonants is placed on the current [ㅠ] button (ie, the [B] button) in the left-hand area (ie, the consonant area) (ie, one button [B] Recognize "ㅆ" by pressing), [Shift] button and [TT] button are combined to input "ㅠ" (that is, recognition as "ㅠ = Shift^ㅜ"). Since "ㅠ" is subtracted from the [B] button and "ㅆ" is placed, a method to input "ㅠ" must be presented. See Figure 18-2. Currently used "ㅠ = ㅜ+ㅜ" can be used, but in this case, in this case, "ㅜ" is a vowel in which "ㅜ" is connected up and down.

There is a problem that you cannot enter "as "ㅜ+ㅜ". Of course,"

= Shift^ㅜ", you can also use "ㅠ = ㅜ+ㅜ". However, if you use "ㅠ = ㅜ+ㅜ", in the form of "TT", a vowel consisting of two "

Typing "as "ㅜ+ㅜ" is the most natural, but it doesn't.

In the past, in the problem of inputting Hangul Gore (that is, old Hangul), there has been a difficulty in how to input the half-chief "ㅿ". The representative editor program that can input old Korean is "Daeah Hangul" in word processor, "ㅿ = Shift^ㅁ". However, it is not logical to say that the half-chief "ㅿ" is associated with the consonant "ㅁ" which is not related at all. Therefore, if "ㅆ" is arranged on the [B] button and input by pressing the button once is settled, input as "ㅿ = Shift^ㅅ" using the [ㅅ] button that is related to the pronunciation. It makes sense.

However, currently, a modified 2-beol-sik input technology is also used to input "ㅆ" by pressing the [ㅅ] button twice. (Refer to the old Hangul input function of the AHangul word processor, Saenaru Hangul input device, etc.) It is unclear whether or not the period of use of the old Hangul half-chinese "ㅿ" in real life will come, and even if it is used, it is remarkably used compared to the modern Korean consonants. Will be low. Therefore, prior to entering the modern Korean language, you can enter "ㅆ" by pressing the [ㅅ] button twice, and press the [ㅅ] button three times to input the half-chief "ㅿ". However, in this case, pressing "ㅅㅅㅅ" is not recognized as the final "ㅆ" and the initial "ㅅ", but is recognized as the half-chief "ㅿ". Therefore, as stated in the applicant's earlier application, as the [ㅅ] button is repeatedly pressed, it operates as "ㅅ → ㅆ or ㅅㅅ → ㅆㅅorㅅㅆ → ㅆ", and the 5th consecutive press of the [ㅅ] button is treated as a half chime "ㅿ". can do. However, in reality, when the [ㅅ] button is pressed four times in a change caused by repeated pressing of the [ㅅ] button, it may not be necessary to treat it as an absolute "ㅆ". Therefore, by repeatedly pressing the [ㅅ] button, it is possible to make "ㅅ → ㅆ or ㅅㅅ → ㅆㅅorㅅㅆ", and pressing the [ㅅ] button 4 times can be treated as a half-chief "ㅿ". In other words, the [ㅅ] button can be pressed three times, four times, or five times as the half-chief "ㅿ".

As mentioned, the 10-finger keyboard is a device used by the autonomic nervous system, so it may be difficult to change existing habits. Therefore, the input of modern Korean is given priority to "ㅆ = Shift^ㅅ", but if "ㅆ" by "Shift^ㅅ" is continuously input, it can be processed as a half-chief "ㅿ". In other words, the half-chief is "ㅿ = Shift^ㅅ + Shift^ㅅ" or "ㅿ = Shift^ㅅ+ㅅ". For "ㅿ = Shift^ㅅ + Shift^ㅅ", enter "ㅆ" by "Shft^ㅅ" and then press "Shft^ㅅ" again while releasing both the [Shift] and [ㅅ] buttons. Giving is an expression, and "ㅿ = Shift^ㅅ+ㅅ" means pressing and releasing the [ㅅ] button while holding the [Shft] button, and pressing the [ㅅ] button once more while the [Shift] button is still pressed. It means that both are the same expression that expresses pressing "Shift^ㅅ" twice. According to the use frequency table of our modern Hangul, there is no case (ie 0%) of the initial consonant "ㅆ" after the final consonant "ㅆ". Of course, there is a possibility that there may be one or two words with the initial consonant "ㅆ" after the final consonant "ㅆ", but this is not enough to affect modern Korean life.

" 이 있다. 별도의 버튼으로 독립시킨 [ㅆ]버튼(즉, [B]버튼)과 [Shift]버튼을 조합하여 어떤 대상을 입력할 수 있는데, "ㅿ" 또는 "

" 중 어느 하나가 입력되도록 할 수 있다. 기존에 "ㅆ"을 "Shift^ㅅ"으로 입력하였던 습관을 고려한다면, "

= Shift^ㅆ" 으로 하는 것이 타당할 것이다. " Shift^ㅆ"으로 "ㅿ" 와 "

" 중 어느 하나를 입력한다고 하더라도, "ㅿ"가 연속하여 나오거나, "

"가 연속하여 나오는 경우는 거의 없을 것이다. 따라서 "Shift^ㅆ" 2번 눌러짐에 의하여 "ㅿ" 또는 "

" 중 나머지 한가지가 입력되도록 하는 것이 가능하다. 여기("ㅿ = Shift^ㅆ")에서 "ㅆ"은 [ㅆ]버튼(즉, [B]버튼)을 의미한다.Hangul (Old Hangul), which has a strong connection with "ㅅ", is the half-chief "ㅿ" and "

There is ". You can enter an object by combining the [ㅆ] button (that is, the [B] button) and the [Shift] button, which are independent as separate buttons, and you can enter "ㅿ" or "

Any one of "can be entered. Considering the habit of entering "ㅆ" as "Shift^ㅅ" in the past,"

= Shift^ㅆ" would make sense. "Shift^ㅆ" with "ㅿ" and "

Even if you enter any one of ",""ㅿ" appears consecutively, or "

"Will seldom appear in succession. So, by pressing "Shift^ㅆ" twice, "ㅿ"or"

It is possible to input the other one of ". Here ("ㅿ = Shift^ㅆ"), "ㅆ" means the [ㅆ] button (ie, the [B] button).

"을 입력할 수 있는 또 다른 방법은 [ㅅ]버튼과 [ㅆ]버튼의 눌러짐으로 인식되도록 하는 것이다. 즉, "

= ㅅ+ㅆ"이 된다. 우리 현대 한국어 사용빈도표에서 "ㅅ" 다음에 "ㅆ"이 연속하여 나오는 경우는 "0.003%" 로 조사되어 있으므로, 사실상 무시될 수 있을 정도의 미미한 수준이다. 단, "ㅆ" 다음에 "ㅅ"이 나오는 경우는 매우 많으므로, "

"의 입력에 "ㅆ+ㅅ"을 사용할 수는 없다. 또한 [ㅅ]버튼 3번 눌러짐으로 "

"을 입력하기 어려운 것은, "ㅆ = ㅅ+ㅅ"을 허용하는 경우 현대 한국어에서 "ㅆ" 다음에 "ㅅ"이 나오는 경우가 빈번하기 때문이다. "

= ㅅ+ㅆ"에서 "ㅆ"의 입력은 [ㅆ]버튼 한번누름에 의하는 것만이 가능한 것은 아니다. 기존 2벌식키보드에서처럼 "ㅆ = Shift^ㅅ" 으로 완전하게 "ㅆ"을 입력할 수 있는 수단으로 입력하는 것도 포함한다. "ㅆ = ㅅㅣㅣ" 와 모호성없이 완전하게 "ㅆ"을 입력하는 수단에 의하는 것(참고. 도면4-*의 키패드에서의 입력 사례)도 마찬가지로 가능하다. 만약 "

= ㅅ+ㅆ"으로 입력한다면, "Shift^ㅆ"으로 반치음 "ㅿ"을 입력하도록 할 수 있다. 현재는 키보드에서 "

"을 [ㅅ]버튼 3번 눌러짐으로 입력하고 있는데, 이 역시 가능하다. "

"은 초성자음으로만 쓰이고 종성자음으로는 쓰이지 않기 때문에 종성자음 "ㅆ" 다음에 "ㅅ"이 입력된 것을 "

"으로 처리하는 것이 아니고, "ㅆㅅ"으로 처리한다. "ㅆㅅ"다음에 [ㅅ]버튼이 2번 눌러지면 "ㅆ

"이 된다. "

Another way to enter "is to have the [ㅅ] button and the [ㅆ] button recognized as being pressed. That is,"

= ㅅ+ㅆ". In our modern Korean frequency table, the case where "ㅆ" appears consecutively after "ㅅ" is "0.003%", so it is in fact negligible. , "ㅆ" is followed by "ㅅ" in many cases, so "

You cannot use "ㅆ+ㅅ" for the input of ". Also, by pressing the [ㅅ] button 3 times, "

"It is difficult to enter "because "ㅅ" is often followed by "ㅆ" in modern Korean when "ㅆ = ㅅ+ㅅ" is allowed. "

It is not possible to input "ㅆ" in = ㅅ+ㅆ" by pressing the [ㅆ] button once. Like in the existing 2 Beolsik keyboard, you can completely enter "ㅆ" with "ㅆ = Shift^ㅅ" It includes inputting by means, it is also possible to input "ㅆ = ㅆ" and "ㅆ" completely without ambiguity (refer to Fig. 4-* example of input on the keypad). if "

= ㅅ+ㅆ", you can use "Shift^ㅆ" to enter the half-chief "ㅿ". Currently, the keyboard ""

"I'm entering by pressing the [ㅅ] button 3 times, but this is also possible."

"Because "is used only as an initial consonant and not as a final consonant, the input of "ㅅ" after the final consonant "ㅆ" is "

It is not processed with ", but is processed with "ㅆㅅ". If the [ㅅ] button is pressed twice after "ㅆㅅ", "ㅆ

"It becomes.

In Korean, 28 characters were announced at the time of the Hunminjeongeum creation, and the letters "ㆍ, ㅿ, ㆆ, ㆁ" are not currently used. Since there is an attempt to use the above four unused letters as well, inputting them naturally is also a necessary factor in the invention of the Hangul input technology. The "ㆍ" is a two-time [ㅏ] button press or "Shift^ㅏ", a soft "ㆆ = Shft^ㅎ", and the old adaptation is "ㆁ = Shft^ㅇ". I can. However, the half-chinese sound "ㅿ = Shift^ㅁ" is used, and the half-chinese "ㅿ" is associated with "ㅁ", which has no connection, which is a factor that hurts the scientificity of Korean Hangul. In the present invention, the [ㅅ] button or the [ㅆ] button that is related to the half-chief "ㅿ" is used (eg "Shfit^ㅅ", "Shfit^ㅅ" 2 times, or the [ㅅ] button 3 times or more. By pressing the [ㅆ] button twice or "Shift^ㅆ"), you can enter the half-chief "ㅿ" without ambiguity (or almost without ambiguity).

Summarizing the above invention, since only consonants are placed on the button of the left hand region, which can be called the consonant region, confusion of consciousness can be eliminated. In modern Korean life, "ㅆ" is recognized as two phonemes, but rather one It is recognized like a grapheme, but at the same time, it is possible to input "ㅆ" with a relatively high frequency of use by pressing the [ㅆ] button, and "ㅠ = Shift^ TT". The half-chief "ㅿ" can also be entered using the strongly related [ㅅ] button or [ㅆ] button.

It is apparent that the present invention can be applied equally to a case where the position of the alphabets arranged on each button in the current 2 beol-sik Korean keyboard is partially changed or the alphabets disposed on the current 2 beol-sik Korean keyboard are slightly different.

33.2 Hangul 2 Beolsik Keyboard Hangul Gore Input

" 등)의 입력에 대하여 언급하였다. 제31장에서 한글 고어의 입력을 위한 수단을 제시한 바 있다. 이하에서 2벌식 키보드에서 일반적으로 한글고어를 입력할 수 있는 수단을 추가로 제시한다. Some of the Hangul archaic consonants associated with "ㅅ" in the above (eg half-chinese "ㅿ", "

The input of ", etc." is mentioned. In Chapter 31, a means for inputting Hangul Gore is presented. Hereinafter, a method for inputting Hangul Gore in general on the 2 Beolsik keyboard is additionally presented.

On the 2beolsik keyboard, enter hard consonants (double consonants) as a combination of shift and flat consonants (eg "ㄲ = Shift^ㄱ"). And the grid sound is arranged on a separate button (eg [ㅋ] button). By applying the modified Hangul combination logic, hard consonants are input by pressing the flat consonant button twice (eg "ㄲ = ㄱ+ㄱ"). The logic in Fig. 4-34(b) can also be applied to the keyboard.

"이 되고, 한번 더 눌러지면 역시 동일하게 "

"이 된다. 한번 더 눌러지면 "

ㄱ"이 될 수 있다. [ㄱ]버튼이 2번 눌러졌을 때의 "

" 다음에 모음(예. "ㅣ")이 입력되면 "

기"가 된다. [ㄱ]버튼이 3번 눌러졌을 때의 "

" 다음에 모음(예. "ㅣ")이 입력되면 "가끼"가 된다. However, since the lattice sound is separated by a separate button, pressing the flat consonant button 3 times may not be processed as a lattice sound. Therefore, the “3+ stroke input method” suggested 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 2 Beolsik keyboard. In other words, pressing the flat consonant button (eg [a] button) three times is processed as a hard consonant sound (eg, "ㄲ"). Here, when the flat consonant button is pressed twice, it can be processed as "ㄱㄱ" or 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 as described above. For example, if the [a] button is pressed once after "A", it becomes "Angle", and if it is pressed again, it becomes "

"It becomes, and if it is pressed once again, it is the same"

"It becomes. If you press it again"

It can be "a". When the [a] button is pressed twice, "

If a vowel (eg "ㅣ") is entered after ", "

When the [ㄱ] button is pressed 3 times, the “

If a vowel (eg "ㅣ") is entered after ", it becomes "gaki".

In the above case, as in the description of Fig. 4-34(b), the case where "ㄲ" appears after "a" is ambiguous. However, in the frequency of use table, this case is negligible. Considering only the input of the modern Korean language, pressing of the flat consonant button 3 times is recognized as an absolute hard consonant (double consonant), so pressing the [a] button once more (ie, pressing a total of 4 times) means "hard consonant + What becomes "plain consonants" (eg "ㄲㄱ") is natural for modern Korean input. If the "ㄱ" button is pressed 5 times, it becomes "ㄲㄲ". The second "ㄲ" was input by pressing 2 times of "ㄱ", but because it is an initial consonant, it cannot be divided into "ㄱㄱ", so it is not necessary to process "ㄲ" with 3 times of "ㄱ". However, for consistency of use, it is also possible to treat the press once more (that is, press “a” 6 times) as “ㄲㄲ”. In any case, the letter after the hard consonant in Fig. 4-34(b) is pressed once more in "ㄲㄲ" (eg "ㅱ", "ㅸ", "ㆁ", ..., etc. In the following "pair" It can be used to input the consonant next letter"). For example, if the 3 times of the flat consonant button is pressed only to be processed as a hard consonant sound, the 4 times [ㅂ] button can be pressed as the pure consonant "ㅸ". Refer to Figure 4-34(b). Pressing the [ㅇ] button 4 times can be changed to "ㆁ". If pressing the flat consonant button 4 times as "hard consonant + flat consonant" is applied, pressing the [ㅇ] button 5 times as the old conversion "ㆁ", and pressing the [ㅂ] button 5 times as "ㅸ" have. If the flat consonant button is pressed 5 times as "hard consonant + hard consonant", you can enter the "two consonant next letter" by pressing 6 times, and when the flat consonant button is pressed 6 times, "hard consonant + If you apply to "hard consonant", you can enter "next double consonant" by pressing 7 times. In the keyboard, since the hard long (double consonant) can be entered as "Shift^ flat consonant", pressing the flat consonant button 3 times can be processed as the input of the "next double consonant". For example, pressing the [ㅇ] button 3 times is treated as "ㆁ".

", "

", ... "

", "

", ...) 역시 절대적인 것은 아니고 단지 예시일 뿐이므로, 적절하게 변형될 수 있음은 자명하다. 상기 내용을 종합하면, 키보드에서 "3+타 입력방법"을 적용시 평자음버튼 3번 눌러짐 또는 3번 이상 눌러짐에 의하여 "쌍자음다음글자"를 입력하도록 하는 것이다. The "double consonant next letter" illustrated in Fig. 4-34(b) is merely an example and is not an absolute. As described above, since "ㅸ" can be entered as a combination of "ㅂ" and "ㅇ", it may be omitted from the "next letter of double consonants" in Fig. 4-34(b). It can also be entered as a soft "ㆆ = Shift^ㅎ", so it can also be omitted from "two consonants next letter". The order of "next letter" in Figure 4-34(b) (ex. "

", "

", ..."

", "

", ...) is also not absolute and is only an example, so it is self-evident that it can be appropriately transformed. Summarizing the above, when applying the "3+ other input method" on the keyboard, press the flat consonant button 3 times. It is to enter the "next letter of double consonants" by pressing or pressing three or more times.

", "

", "

", "

", "

", "

", ... 와 같이 자음 다음에 "ㅡ" 또는 "ㅣ"가 연속 2번 나오는 모음을 [ㅡ]버튼 2번 누름 또는 [ㅣ]버튼 2번 누름으로 처리한다면, 상기 "쌍자음다음글자"의 입력을 위해서는 [ㅡ]버튼 3번 눌러짐 또는 [ㅣ]버튼 3번 눌러짐이 적용되어야 한다. 즉, "ㅇ" 다음에 "ㅡ"는 "으"로 되고 한번 "ㅡ"가 입력되면 "

"가 되고, 한번 더 "ㅡ"가 입력되면 여린ㅎ "ㆆ"이 되는 것이다. In the applicant's earlier application, the technique of entering "y = xㅡㅡ" or "z = xㅣㅣ" was introduced. Lattice and hard consonants were input in the same way as above, but a keyboard with more than 26 buttons has a separate grid button, and hard consonants are input as "Shift^ flat consonants". Can be applied to. That is, it can be used for input of the above-mentioned "two consonants next letter". For example, it can be done with "ㅸ = ㅂㅡㅡ" and "ㆆ = ㅇㅡㅡ". Only here "

", "

", "

", "

", "

", "

If a vowel in which "ㅡ" or "ㅣ" appears twice consecutively after a consonant, such as ", ..." is processed by pressing the [ㅡ] button twice or pressing the [ㅣ] button twice, the above "double consonant next letter" In order to input the [-] button 3 times or the [ㅣ] button 3 times must be applied, that is, after "ㅇ", "-" becomes "U" and once "-" is entered, "

It becomes ", and once more "ㅡ" is input, it becomes soft "ㆆ".

", "

", "

", "

", "

", "

", ... 앞에 오는 초성자음을 입력시 초성자음이라는 것을 명확히 하여(예. 길게 누름에 의하여 초성자음 입력)입력하는 방법을 제시한 바 있다. 본 발명에서 Alternatively, as stated in the earlier application, "

", "

", "

", "

", "

", "

", ... A method of inputting the initial consonant sound, clarifying that it is an initial consonant when inputting the preceding 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^ㅡ+ㅡ"로도 표현될 수 있다. An additional technique using "Shift^ㅡ" or "Shift^ㅣ" is presented. It can be applied in two ways. The first is "

", "

", "

", "

", "

", "

In ", ..., etc."

" or "

"When inputting, you can use "Shift^ㅡ" or "Shift^ㅣ". If this is applied,"

", "

", "

", "

", "

", "

You do not need to apply a long press when entering the first consonant preceding ", .... In this way, you can use "y = xㅡㅡ" or "z = xㅣㅣ" as all the letters you want (eg "Next letter of double consonants"). You can enter "). Secondly, in "y = xㅡㅡ" or "z = xㅣㅣ", change "ㅡㅡ" and "ㅣㅣ" to "Shift^ㅡ" and "Shift^ㅣ" respectively. It is to input using "y = x+Shift^-" or "z = x+Shift^-". Again, it is possible to input "next letter of double consonants" without ambiguity. In (a), an example of applying this is shown as the half-chief sound "ㅿ = ㅅ+ Shift^ㅡ", "

= ㅿ + Shift^- = ㅅ+ Shift^- + Shift^-". Pressing "Shift^-" twice above means holding down the [Shift] button and pressing the [-] button 2 The same thing for pressing twice is the same as already described, that is, "Shift^- + Shift^-" can also be expressed as "Shift^-+-".

In the above, in the technique of using the [-] button 2 times (eg "y = xㅡㅡ"), it has been shown that the 2 times [-] button is pressed as "Shift^-". Furthermore, since the keyboard has additional vowel buttons (eg [ㅑ] button, [ㅕ] button, [ㅛ] button, ...) other than the [ㅡ] button [ㅣ] button, "y = x+ A vowel button other than "ㅡ" or "ㅣ" may be applied to "Press the vowel button 2 times". It is preferable to apply vowels in which the same vowel does not appear twice in succession. The current vowels "ㅏ", "ㅓ", "ㅗ", and "TT" corresponding to two presses "ㅑ", "ㅕ", "ㅛ", "ㅠ" respectively is used in the 2 beolsik automata is used in some have. In addition, there are vowels in which "ㅜ" appears twice and there are vowels in which "ㅗ" appears twice. "ㅏ", "ㅓ", "ㅗ", "ㅜ", if you do not apply another vowel input by pressing the same vowel twice, "ㅏ", "ㅓ", "ㅗ", "ㅜ" vowel It is also possible to use. Even if other vowels are input by continuous pressing of the same vowel among "ㅏ", "ㅓ", "ㅗ", and "TT", the method suggested in the case of using the above "ㅡ" and "ㅣ" is the same. Can be applied.

= ㅿ+ㅛㅛ = ㅅ+ㅛㅛㅛㅛ"로 할 수 있는 것이다. 마찬가지로 "ㅆ"을 "ㅅ+ㅑㅑ"로 하지 않고 "Shift^ㅅ" 또는 [ㅆ]버튼 한번 눌러짐으로만 한다면, "

= ㅅ+ㅑㅑ" 로 할 수 있는 것이다. 도면4-34(*)의 나머지 글자(예. "쌍자음다음글자")에 대해서도 같다. 2 Among the vowels arranged on the Beolsik keyboard, "ㅑ" and "ㅕ" of the "ㅣ" series include Korean Gore vowels (refer to Unicode v6.0 in Fig. 4-33(*)), the same vowel twice in succession Does not come out. Also, the same vowels do not appear twice in succession in the "ㅡ" series "ㅛ" and "ㅠ". 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 "ㅑㅑ". If you use the combination of two consecutive presses of the vowel button that does not appear twice in this way, you can select all the desired letters without long press or use of the [Shift] button as in the examples of "ㅡ" and "ㅣ" above. You can enter. For example, with the half-chief "ㅿ = ㅅ+ㅛㅛ", "

= ㅿ+ㅛㅛ = ㅅ+ㅛㅛㅛㅛ" Likewise, if you do not set "ㅆ" to "ㅅ+ㅑㅑ" and just press "Shift^ㅅ" or [ㅆ] button once, you can say "

= ㅅ+ㅑㅑ". The same applies to the rest of the letters in Fig. 4-34(*) (eg "next letter of double consonants").

34. Korean syllable input method by continuous drag using regression drag on the screen keyboard

The present invention is a further development of a technique for inputting Korean language (Chapter 27 of this specification) by a series of applicants. This is an achievement in about six years since the introduction of the invention of Chapter 26 in 2008.

In Chapter 27 of the first, it was shown that the initial, neutral, and final voices were input with a continuous drag. For example, as shown in Figs. 15-7 and 15-8, dragging and entering "go", and dragging as shown in Fig. 15-9 and entering "gon". The drag in Chapter 27 will be referred to as "sequential drag" or "sequential drag" for convenience.

In Fig. 15-13, in a special case, a lattice sound (eg "ㅋ") and a double consonant (eg "ㄲ") related to a flat consonant button (eg "ㄱ") are used as initial consonants to be input by continuous dragging. Showed that you can. However, in the process of entering "de", the user may naturally drag "c → ㄴ → ... → ㅡ" to input "de". When drawing 15-13 is applied, the system inputs "t" It can be mishandled as one. Also, in Chapter 27, consonants that are not displayed on the button (eg, lattice sound, double consonant) cannot be entered as a final consonant with a single drag by continuous dragging. Similarly, in Figs. 15-14, 15-15, and 15-16, when two consonants are related to one button, a method of inputting the second related consonant by drag is not presented. In the present invention, even if it is not displayed on the button or displayed on the button with a single drag, a technology that can input even the second or more related consonants (eg "ㅋ", "ㄲ", ...) without error is provided. 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 Google Play Store (Android Market) at an appropriate time.

34.1 Arrangement of related concepts and terms

For convenience in describing the present invention, some of the key terms related to drag defined by the inventor and their concepts are briefly summarized.

Figure 19-1 is a keyboard image of the product published on the official website of the applicant's product at http://www.simplecode.net and the Google Play Store (Android Market). In Fig. 19-1, the "ㆍ" of the [0] button may be displayed in "ㅏ" or other form (eg, the form indicated 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. Similarly, dragging to the right and then back to the original position, dragging upwards and then back, and dragging downwards and then back again are possible. The drag that moves through the other buttons and then returns to the original position will be called "regressive drag" or more simply "regressive drag". The drag that proceeds to the left and returns again is called "left revolving drag" for convenience, and the rest of the cases are also called "return right drag", "return up drag", and "return down drag" respectively.

It can be seen that the leftward regression drag was dragged as [ㅁ → ㄹ → ㅁ], and the right regression drag was dragged to [ㅁ → ㅂ → ㅁ]. Since the leftward revolving drag and the rightward revolving drag are drags that progress in the horizontal direction and then return again, they can be summed up and referred to as “horizontal regression drag”. Similarly, since the upward regression drag and the downward regression drag are drags that progress in the vertical direction and then return again, both can be referred to as "vertical regression drag".

In addition, there may be a leftward revolving drag as shown in Fig. 19-2. In Fig. 19-3, it is a case of dragging to the left within one button and then returning to the original position. This is a method of detecting "bending" at a predetermined angle after proceeding more than a certain distance and detecting the progress of the predetermined distance again, so that the regression drag within the same button can be identified. However, this method has a disadvantage that it is difficult to know whether the drag has been dragged by a critical distance that can be recognized as a drag from the user's point of view, and there are many possible errors. On the other hand, as shown in Fig. 19-1, when the user moves from the button where the drag started (eg, the [ㅁ] button) to the adjacent button and returns to the original button, the user can change the drag trajectory to the adjacent button divided in a grid pattern. Since it can be checked visually, there is a good effect that the possibility of errors by the user is greatly reduced.

As shown in Fig. 19-2, the return drag within the same button is called "return drag within the button" for convenience, and the return drag that goes back to the original button after proceeding with the peripheral button as shown in Fig. 19-1 is called "except for the button". I will call it "regressive drag". In reality, the keyboard on the touch screen terminal is not very large and the buttons are also very small. As described above, the regression drag outside the button has a better property, and thus the regression drag will be described as a regression drag outside the button. It is also one of the important features of the present invention to be based on the good properties of the recursive drag other than the button.

Fig. 19-3 shows an example of a regression drag in which the drag progresses beyond the adjacent button and then returns to the button where the drag started. Looking at the trajectory of the rightward regression drag in Fig. 19-3, it can be seen that it was dragged to [ㅁ → ㅂ → Qwerty → ㅂ → ㅁ]. For convenience, as shown in Fig. 19-3, when dragging beyond one more adjacent button and returning to the original button where the first drag was started, it will be called "2-stage regression drag". Similarly, FIG. 19-1 may be referred to as "stage 1 regression drag", and FIG. 19-2 may be referred to as "0 stage regression drag". In other words, a regression drag other than the button is a regression drag of one or more stages (eg, 1st, 2nd, 3rd, ...).

Looking at the drag trajectory in Figure 19-4, it was dragged to [ㅁ → ㄹ → ㅅ → ㅇ → ㅁ]. It was first dragged to the left, and it did not return to the first button again from the adjacent button [ㄹ], but returned to the first drag start button [ㅁ] button through other buttons. This can also be seen as a form of two-stage regression drag. In fact, it returned to the original button after 4 times ([ㅁ → ㅂ → Qwerty → ㅂ → ㅁ]) in Drawing 19-3, but in Drawing 19-4, 4 times ([ㅁ → ㄹ → ㅅ → ㅇ → ㅁ]) It can be seen that the button has returned to the original. Figure 19-4 If you attach the direction of drag, it can be called "2-stage left-handed drag". Of course, since the left-reverse drag of Fig. 19-3 and the left-reverse drag of Fig. 19-4 have different drag patterns, different input targets may be identified.

Although not illustrated in the drawings, the occurrence of the first stage regression drag twice in succession may be regarded as a kind of two stage regression drag. For example, in the case of a button trajectory of [ㄱ → ㄴ → ㄱ → ㄴ → ㄱ], the 1st stage rightward regression drag occurred twice in succession. If the button trajectory of [ㄱ → ㄴ → ㄱ → ㄹ → ㄱ] is the case that there is one rightward regression drag and one consecutive downward regression drag occurs. Again, the first stage regression drag occurred twice in succession. The second-stage regression drag, in which the first stage regression drag occurs twice in succession, also has a different pattern from those of Figs. 19-3 and 19-4, so that different input targets can be identified.

Likewise, you can think of a regression drag in the diagonal direction, but dragging in the upper left direction (or upper left direction) and then returning again was performed in the upper left direction drag (or the upper left direction drag), and the upper right direction (or upper right direction). The drag that returns to the top right (or drag to return to the right), drag the drag to return to the bottom left (or downward or to the left), then drag the drag to return to the bottom left (or drag to return to the left or right), and to the right (or how to do it) The drag that is dragged in the direction of direction) and then returns again is called a right-down revolving drag (or a down-turning drag), respectively. Referring to Fig. 19-5, for convenience, the four types of diagonal regression drag in Fig. 19-5 will be collectively referred to as "diagonal regression drag".

If you look at the button trajectory of the downward-left regression drag in Fig. 19-5, it can be seen that it was dragged to [ㅁ → ㄹ → ㅅ → ㅇ → ㅁ]. Alternatively, it can be seen that [ㅁ → ㅇ → ㅅ → ㄹ → ㅁ] is also a downward-left regression drag (to be precise, a downward-left regression drag). Figure 19-4 was also dragged to [ㅁ → ㄹ → ㅅ → ㅇ → ㅁ]. That is, when comparing only the button trajectories, the drag in Fig. 19-4 can be viewed as a left-down regression drag. Therefore, the drag in Fig. 19-4 and [ㅁ → ㄹ → ㅅ → ㅇ → ㅁ] in Fig. 19-5 can be applied by comparing only the button trajectory and regarded as a drag of the same pattern. However, if the number of input objects (eg alphabets) to be expressed is large, the drag in Figure 19-4 and the button trajectory in Figure 19-5 [ㅁ → ㄹ → ㅅ → ㅇ → ㅁ] are used to select different input objects. Can be used to express. The method of distinguishing between the downward-left regression drag in Fig. 19-5 ([ㅁ → ㄹ → ㅅ → ㅇ → ㅁ]) and the two-stage leftward regression drag in Fig. 19-4 detects the "bending" angle of the drag as well as the button trajectory. It is possible by doing. In Fig. 19-4, the bending occurs three times at an angle of about 90 degrees, whereas in Fig. 19-5, it is necessary to detect that the bending occurs once at an angle of about 180 degrees. It is not that difficult to do it. In the end, the oblique regression drag in Fig. 19-5 can be interpreted as "1-stage oblique regression drag" considering the "bending" angle, and the "2-stage regression drag" is judged only by the button trajectory without considering the "break" angle. You can also interpret it.

Regression drag in the diagonal direction may also be a regression drag within the button (i.e., zero regression drag), and a 2-stage regression drag dragged beyond the range of the adjacent button (up/down/left/right adjacent button and diagonal adjacent button) There may be. Indications on the drawings are omitted. Considering that the size of the keyboard and buttons are small in current smartphones, etc., the regression drag within the button (ie, zero regression drag) is the same regardless of the direction (eg horizontal direction, vertical direction, oblique direction,...) It can be used to identify the input object (eg alphabet).

As described above, the core concepts for applying the present invention have been summarized through terms defined by the present inventors. In the following, a specific keyboard is used to input processing of input targets (eg "ㄲ", "ㅋ", numbers, functions...) related to a specific consonant button (eg, [a] button) according to the above-described concept. Examples are presented as a reference. It is obvious that what has been described in the following embodiments can be applied equally to other embodiments. In addition, in the keypads of all the following embodiments, it is assumed that the buttons are arranged densely without a gap between the buttons and the buttons.

34.2 Example of Inputting Associated Consonants Using Regression Drag (Applicant's Keyboard)

Based on Figure 19-1, the input rules suggested by the applicant are "ㅋ = ㄱㅡㅡ", "ㄲ = ㄱㅣㅣ" or "ㄲ = ㄱㄱ", "ㅋ = ㄱㄱㄱ", etc. As a result, it can be seen that in Fig. 19-1, "ㄲ" and "ㅋ" are related to the [a] button in addition to the "a" displayed on the button. Likewise, the corresponding lattice sound (eg "ㅌ") and double consonant sound (eg "ㄸ") are also associated with other flat consonant buttons (eg, [c] button). If the "ㄱ" displayed on the button is also related to the [ㄱ] button, "ㄱ" can be seen as the first associated alphabet, and "ㄲ" and "ㅋ" are respectively subordinated (ex. 2nd, 2nd, 2nd, 2nd, 2nd, 2nd, 2nd, 2nd, 2nd, 2nd, 2nd Third, it can be seen as an alphabet that is associated with...).

In this embodiment, a case of inputting a lattice sound through a horizontal regression drag (i.e., a left regression drag and a right regression drag) and a double consonant input through a vertical regression drag (i.e., upward regression drag and downward regression drag) is shown. . Of course, a consonant (eg "ㄲ") associated with a specific button (eg [a] button) is recognized with one regression drag, and another regression drag (eg 1st stage regression drag is 2 consecutively). It is also possible to recognize other related consonants (eg, "ㅋ") with a two-stage regression drag in the form of one occurrence. However, since it is easier to input the required object with one regression drag than having to execute two regression drags in succession to recognize the consonants associated with a specific button, each input object for vertical regression drag and horizontal regression drag. This is to present a recognized example.

An example that mainly uses horizontal regression drag for lattice input and vertical regression drag for double consonant input is the form of Korean Hangul's lattice tone (eg "ㅋ", "ㅌ", "ㅍ", "" ㅊ") ideologically corresponds to the horizontal direction, and the form of diconsonants (eg "ㄲ", "ㄸ", "ㅃ", "ㅆ", "ㅉ") is a shape with flat consonants side by side, so it is vertical. This is because it ideologically fits the direction. However, it is not necessary to use horizontal regression drag for lattice sound, and vertical regression drag must not be used for double consonants. Conversely, vertical regression drag may be applied to lattice input, and horizontal regression drag may be applied to diconsonant input. In addition, only one of the horizontal regression drags, leftward regression drag or rightward regression drag may be applied, and only one of the vertical regression drags, upward regression drag or downward regression drag may be applied. Similarly, a specific button (ex. [a] button) by the diagonal regression drag in Fig. 19-5 (specifically, it means the drag of 4 patterns, depending on the interpretation, the 1-stage diagonal regression drag or the 2-stage regression drag). Consonants related to (eg "ㄲ", "ㅋ",...) can be recognized. The important thing is to recognize the consonant associated with a specific button by regression drag other than the button (ie, regression drag in one or more stages).

According to the applicant's earlier application (Chapter 27), the drag result of [ㄱ → ㄴ → ㄱ → ㄹ → ㅅ → ㅡ → ㆍ → ㅇ → ㅁ → ㅂ] is entered as the drag result. The button [a], the button where the drag was started, becomes a valid input, and the consonant button below that is invalid, 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, assuming that the lattice sound is recognized by the horizontal regression drag, the input result becomes "coop". If the user intends to input "heel", there is no reason to start dragging from the [ㄱ] button and return to the [ㄱ] button again after going through the [ㄴ] button on the right, of course [ㄱ → ㄹ → ㅅ → ㅡ →. This is because it would have been dragged like ..]. In other words, if the user wants to input only "ㄱ" as the initial consonant, start dragging from the [ㄱ] button and the vowel button that the user wants to enter directly through another button without returning to the [ㄱ] button again (ex. [ㅡ] button) I would have dragged it. However, returning back to the button that started the dragging allows the user to clearly identify without any error that it is intended for the user to enter the promised alphabet (eg "ㅋ") in the regression drag (eg horizontal regression drag). In Figure 19-6, it was shown that grid sound is input by right-hand regression drag, but if all horizontal regression drags are considered to recognize grid sound, [ㄱ → Mode → ㄱ → ㄹ → ㅅ → ㅡ → ㆍ → ㅇ → ㅁ → Drag of [ㅂ] can also be regarded as "coop".

It is very simple to detect the rightward regression drag in Fig. 19-6. The consonant button that started dragging is recognized as valid, and the [ㄱ] button that started dragging from the button trajectory before the vowel button [ㄱ → ㄴ → ㄱ → ㄹ → ㅅ → ...] appears again (the third dragged " It is possible by detecting 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 the right-reverse drag has been made only with the button trajectory. If dragged to "ㄱ → Mode → ㄱ → ㄹ → ㅅ → ...", the second dragged [Mode] button is located to the left of the [ㄱ] button, so it is possible to detect the leftward drag.

Next, it shows that the double consonant is recognized by the vertical regression drag. The drag in Fig. 19-7 is also recognized as a "shoe" according to the applicant's earlier application (Chapter 27). However, if it is assumed that the double consonant is recognized by the vertical regression drag (downward regression drag in Fig. 19-7), the result is "replaced". In order to detect the upward regression drag by the button trajectory, it is easily possible by setting a small, invisible, fake button in the area above the [a] button. This is because, in general, keyboard programs cannot recognize areas outside the keyboard. Fig. 19-8 shows an example in which a small height of a fake button (in fact, it is desirable to make it almost invisible) is set on the top of the keyboard. Referring to Fig. 19-8, an example of inputting a double consonant as an initial consonant by an upward regression drag is shown in Fig. 19-9. If the top 5 fake buttons in Figure 19-9 are respectively DB1, DB2, DB3, DB4, and DB5 for convenience, in Figure 19-9 they are dragged to "ㄱ → DB2 (a upper button) → ㄱ → ...", and the result Is recognized as "replacement".

If you input "ㅆ" as the initial consonant, if you apply a downward drag like [ㅅ → ㅡ → ...], it is recognized that "su" is input. However, if you apply the upward regression drag like [ㅅ → ㄹ → ㅅ → ㅡ → ...], "write" can be recognized without any problem. In the case of "ㅅ", since there is no lattice sound, horizontal regression drag (ie, leftward regression drag and rightward regression drag) can also be processed as "ㅆ".

The next is the case where "ㅎ" is related to the [ㅇ] button. Since there is no lattice sound corresponding to "ㅇ" in modern Korean, both vertical regression drag and horizontal regression drag can be processed as "ㅎ". If dragged backwards as in [ㅇ → ㆍ → ㅇ], it is recognized as "ang" (refer to Chapter 27 of the previous application). Therefore, upward regression drag excluding downward regression drag [ㅇ → ㅁ → ㅇ → ...], leftward regression drag [ㅇ → ㅅ → ㅇ → ...], rightward regression drag [ㅇ → ㅈ → ㅇ → ...] Can be processed as "ㅎ" input. Drawings of input examples are omitted.

In the applicant's earlier application, "ㅎ" was also associated with the [ㆍ] button. According to the earlier application, when dragging to [ㆍ → ㅇ → ㆍ → ㅣ], the [ㆍ] button that started dragging is valid, and the [ㅇ] button that cannot be combined with it is invalidated, and the remaining [ㆍ] button, which can be combined, is Since the button and [I] button are valid, the result is recognized as "ㅕ". It is possible to input one letter combined by dragging, but in some cases, it is preferable to input by combining normal pressing and dragging. In addition, 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 "ㅕ", the first stage drag started from the vowel button ([· → ㅇ → ㆍ → ...] is the first stage upward drag started from the [ㆍ] button). It is assumed that vowels are recognized. If so, the "ㅎ" associated with the [ㆍ] button can be entered by dragging the 2nd or more (3rd, 4th,...) upward drag. For example, [ㆍ → ㅇ → ㅁ → ㅇ → ㆍ] 2nd stage upward drag can be processed as "ㅎ". The input of the initial consonant "ㅎ" may be referred to in the input case of "hi+he (lasting)" in Figures 19-13.

It has been described that the first stage regression drag starting from the vowel button is processed as a vowel input, and the second stage regression drag is processed as the input of a promised consonant (eg "ㅎ"), but the opposite can be defined. That is, it is possible to process the first stage regression drag starting from the vowel button as an input of a promised consonant (eg, "ㅎ"), and the second stage regression drag as a vowel input. This means that the user usually starts dragging from the consonant button and ends the dragging from the vowel button (ie, inputting a letter consisting of "initial consonant + neutral vowel"), or dragging from the consonant button and then the consonant button through the vowel button. (In other words, the letter consisting of "initial consonant + neutral vowel + final consonant") is most common, and there will be few cases where you start dragging from the vowel button. In some cases (1st stage regression drag or 2nd stage regression drag), it is the same that the regression drag that starts from the vowel button and returns to that vowel button can be treated as a promised consonant (eg "ㅎ"). This is also an example presented for the first time in the present invention.

As mentioned above, the case of inputting the second or more related alphabet with respect to the initial consonant by regression drag was shown. Next, we show an example where you can enter even the final consonant.

In the applicant's earlier application (Chapter 27), only the last dragged consonant button was considered valid. This means that only nine consonants (ㄱ, ㄴ, ㄷ, ㄹ, ㅁ, ㅂ, ㅅ, ㅇ, ㅈ) displayed on the button in Fig. 19-1 can be input as final consonants by one continuous drag. According to earlier applications, Figures 19-10 are recognized as "heels". In the present invention, it is the same that the last dragged consonant button is processed as a valid button. When the present invention is applied, it is recognized as "?m". In Figure 19-10, it was dragged to [ㄱ → ㄴ → ㄱ → ㄹ → ㅅ → ㅡ → ㆍ → ㅇ → ㅁ → ㅂ → ㅁ → ㅂ ]. The button trajectory after the last dragged vowel button [ㆍ] is the same as [... → ㅇ → ㅁ → ㅂ → ㅁ → ㅂ]. If the user intended to input only "ㅂ" as the final consonant, the drag should be ended with [... → ㅇ → ㅁ → ㅂ] without having to drag to [... → ㅂ → ㅁ → ㅂ] .

Detecting the leftward drag in the final consonant input is very simple 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. It is very easy to apply a left-hand drag (a form of horizontal drag) of the [ㅂ] button to the final input, and can be detected without an error by the user (eg, user error in the zero-stage regression drag). The initial consonant detects the regression drag based on the consonant button on which the drag was started, while the final consonant detects the regression drag based on the consonant button where the drag ends.

According to the earlier application (Chapter 27), Figures 19-11 are recognized as "angles". However, the button trajectory is [ㄱ → ㄹ → ㅅ → ㅇ → ㆍ → ㅇ → ㅁ → ㄹ → ㄱ → ㄹ → ㄱ], so if the present invention is applied, the final drag that is considered effective after the [ㆍ] button, which is a valid vowel button Since there is "ㄱ → ㄹ" in front of the [ㄱ] button, which is a consonant button, it detects that the downward regression drag (the [ㄹ] button is placed under the [a] button) is applied to the final input, and the result is "cut".

[ㅇ → ㆍ → ㅣ → ㅈ → ㅇ → ㅅ → ㄹ → ㅅ] in Fig. 19-12 is recognized as "what" according to the previous application. However, when the present invention is applied, "we" is recognized. This is because it can detect that the upward regression drag of [...→ ㅅ → ㄹ → ㅅ] is applied to the finality input. If the original intention was for the user to enter "what", the drag should have been ended in [ㅇ → ㆍ → ㅣ → ㅈ → ㅇ → ㅅ] without needing to drag back to [...→ ㅅ → ㄹ → ㅅ] Because it does. In the case of "ㅅ", since there is no corresponding lattice sound, it is said that horizontal regression drag (ie, leftward regression drag and rightward regression drag) can also be processed as "ㅆ". That is, instead of [...→ ㅅ → ㄹ → ㅅ] in Figure 19-12, drag the leftward regression of [...→ ㅅ → space → ㅅ] and the rightward regression of [...→ ㅅ → ㅇ → ㅅ] Drag can also be treated with the final consonant "ㅆ". The example of the final consonant sound "ㅆ" was given, but the same applies to the input of "ㅎ" related to the [ㅇ] button (ie, upward regression drag, left regression drag, and right regression drag "ㅎ" for the [ㅇ] button. ") is possible, and case drawings are omitted.

In an embodiment of the present invention, it is shown that a first-stage drag starting from a vowel button is recognized as a vowel input, and two or more drags are processed as a promised alphabet (eg, "ㅎ"). The button trajectory in Figure 19-13 is [ㆍ → ㅇ → ㅁ → ㅇ → ㆍ → ㅇ → ㅈ → ㅣ → ㆍ → ㅇ → ㅁ → ㅇ → ㆍ]. Since drag starts from the vowel button [ㆍ] button and it can be seen that the drag is 2nd stage upward ([ㆍ → ㅇ → ㅁ → ㅇ → ㆍ → ...]), the promised consonant "ㅎ" is recognized as an initial consonant. . The next dragged consonant button [...→ ㅇ → ㅈ → ...] cannot be combined with "ㅎ", so it is invalidated. Since the drag has been ended in the vowel button, the valid button [ㅣ → ㆍ → ... → ㆍ] is recognized as a vowel "ㅑ" when the first application (Chapter 27) is applied. However, according to the present invention, when it detects and applies that the two-stage upward regression drag has occurred including the last dragged button [·] after the valid vowel button [I], the result becomes "hi+he". If dragged like [ㆍ → ㅇ → ㅁ → ㅇ → ㆍ → ㅇ → ㅈ → ㅣ → ㆍ ㅇ → ㆍ → ㅇ → ㅁ → ㅇ → ㆍ], it becomes "?K".

For better understanding, an example of entering the initial consonant "ㅎ" as a consonant related to the [ㅇ] button by horizontal regression drag, and entering the final consonant sound "ㅎ" as a consonant related to the [ㆍ] button by two-stage vertical regression drag When is shown, it is as shown in Figure 19-14. Applying the earlier application results in "Ya" (regarding the first vowel button as a valid vowel button and treating the remaining combinable vowel buttons as a valid button) or "Ya" (treating all dragged vowel buttons as valid buttons). When the present invention is applied, the initial consonant "ㅎ" is recognized because it is dragged leftward at the [ㅇ] button, and the vowel "ㅏ" is recognized, and the final consonant sound "ㅎ" is dragged up two stages from the last dragged button [ㆍ]. If "is recognized, the result is "?K". A description of the button trajectory is omitted. In this embodiment, the two-stage upward regression drag from the [ㆍ] button was processed as an input of "ㅎ", but in the case of the initial consonant, the first-stage upward drag is processed as the final consonant "ㅎ" as described, and the second stage starting from the vowel button However, it is also possible to process the upward regression 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 Korean keyboards of Samsung Electronics, which are currently widely used. In Fig. 19-15, "ㅋ" is arranged second in the [a] button, so it can be seen that "ㅋ" is a consonant associated with the [a] button. It is easy to see that "ㄹ" is related to the [b] button because the second "ㄹ" arranged in the [b] button is also entered by pressing the [b] button twice. This is the same for the [ㅅ] button and the [ㅇ] button. Although the double consonants are not arranged, you can see that "ㄲ" is related to the [ㄱ] button because you press the [a] button 3 times to enter "ㄲ". The same is true for the rest of the consonants.

In the applicant's earlier application (Chapter 27), it was not possible to input the second consonant associated with it with one continuous drag. In the embodiment of the present invention, an embodiment in which consonants arranged secondly are input by horizontal regression drag and double consonants are input by vertical regression drag is shown.

In Figs. 15-16 of the previous application, it was shown to input "image" with one continuous drag. When dragged as shown in Figs. 19-16, "top" is recognized according to the previous application, but becomes "box" when the present invention is applied. When looking at the button trajectory, it is [ㅅ → ㅈ → ㅅ → ㅂ → ㄱ → ㅣ → ㆍ → ㄴ → ㅅ → ㅇ → period → ㅇ]. "ㅎ" is recognized in the rightward regression drag of [ㅅ → ㅈ → ㅅ → ...], "ㅏ" is recognized in [...→ ㅣ → ㆍ → ...], and [...→ ㅇ → "ㅁ" is recognized in the leftward revolving drag of the period → ㅇ].

Figures 19-17 are recognized as "liver" according to the earlier application. According to an embodiment of the present invention, it may be recognized as "color". The initial consonant "ㄲ" was recognized by the downward regression drag, and the final consonant "ㄹ" was recognized by the right regression drag.

According to the prior application, Figs. 19-18 are recognized as "liver", but according to an embodiment of the present invention, the result of Figs. 19-18 is "sword". In Figures 19-18, if it is assumed that the second related consonant is recognized by the horizontal regression drag, "ㅋ" is recognized by the left regression drag. In addition, since there is no corresponding double consonant in "b", the vertical regression drag (eg, downward regression drag) in Figs. 19-18 can also be processed as the second related consonant "ㄹ".

In Figures 19-18, it is intended to point out the fact that this is an important property. If "Angle" is entered and then dragged as shown in Fig. 19-18, the left revolving drag starting from the [a] button is interpreted as "ㅋ" but the [a] button is processed as being pressed twice, and the "Angle After "," it will be recognized as "sword", not "sword". The reason that the [a] button is pressed 3 times is because it becomes "ㄲ" on the keyboard in Fig. 19-18. However, when dragging from the consonant button ends at the vowel button (that is, a letter consisting of "consonant + vowel"), or the dragging from the consonant button ends at the consonant button through the vowel button (that is, "consonant + vowel + consonant") ) Can be processed so that the input from the drag start button is a single letter combined. Then the result will be "Gang Knife". In the case of inputting only by tapping on the keyboard of Fig. 19-18, there is an ambiguity of "Gakkal ↔ Gakal" for the same button value, but through the present invention, which inputs a single letter combined with a single drag, without ambiguity. It shows important properties that can be entered. If the user wants to input "thick color", after entering "a" (either dragging or pressing), and dragging as shown in Fig. 19-17, "thick color" will be input as the result.

In summary, the drag input of the present invention can be used in conjunction with the tap method, but it is connected to the consonant (eg, "a") successively after the consonant (eg "a") that came out before the final consonant (eg "a"). Even when consonants (eg, "ㅋ", "ㄲ") appear as an initial consonant, it shows 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 seeing "consonant + vowel" or "consonant + vowel + consonant" recognized by drag as a unit, so that the dragged syllable is "initial + neutral" regardless of the final consonant (eg "ㄱ") of the previous letter. It is possible by treatment with "or "initial + neutral + final".

34.4 Example of inputting associated consonants using regression drag (LG Electronics' keyboard)

Figures 15-14, 15-15, and 19-19 are 12 button Korean keyboards of LG Electronics. In Figure 19-19, enter "ㅋ = ㄱ+stroke addition", "ㄲ = ㄱ+double consonant", and "ㄷ = ㄴ+add stroke", "ㅌ = ㄴ+add stroke+add stroke", "ㄸ = Enter “b+stroke addition+double consonant”. Since the keyboard is widely known in the public, detailed description of the input rule by the keyboard will be omitted.

In Fig. 19-19, it can be seen that "a" is related to the first button, and "ㅋ" and "ㄲ" are related to 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 the auxiliary button. In addition, since "ㄲ = ㄱ+double consonant" is input, the [ㄱ] button becomes the main button of "ㄲ", and the function button [double consonant] is used as an auxiliary button.

According to the same logic, "ㄴ" is related to the [b] button first, and "c", "ㅌ", and "ㄸ" are related to the second or more. Likewise, "ㅂ", "ㅍ" and "ㅃ" are related to the [ㅁ] button, "ㅈ", "ㅊ", and "ㅉ" are related to the [ㅅ] button, and the [ㅇ] button is related to "ㅎ "This is related. Three consonants are associated with the [b] button, [ㅁ] button, and [ㅅ] button, and the flat consonants "c", "ㅂ", and "ㅈ" are each related by the most easy-to-use 1-stage regression drag. It is desirable to make "recognized, because flat consonants "c", "ㅂ", and "ㅈ" are used much more frequently than lattice and double consonants. In an embodiment of the present invention, it is shown that "c", "ㅂ", and "ㅈ", which are respectively related to the [b] button, the [ㅁ] button, and the [ㅅ] button, are recognized by the left-facing drag. This is because the left-facing drag must be used in the keypad (keyboard) of Fig. 19-19 because the right-reverse drag is "consonant + vowel + consonant" and other characters are recognized. In addition, it is assumed that "double consonants" are recognized by vertical regression drag (ie, upward regression drag and downward regression drag) for consistency with other embodiments.

Applying the earlier application (Chapter 27), Figures 19-20 are recognized as "names". In an embodiment of the present invention, if "ㅂ" is recognized by the first stage leftward drag, and the result is "??" when "ㅎ" is recognized by the leftward dragging based on the [ㅇ] button, which is the button where the drag is finished. Becomes. Detailed description of the button trajectory will be omitted. In Fig. 19-20, an example of a leftward regression drag is shown to input the final consonant "ㅎ". Since only "ㅇ" and "ㅎ" are associated with the [ㅇ] button, leftward regression drag (ex. [...→ ㅇ → ㅅ → ㅇ]), but upward regression drag (eg [...→ ㅇ → ㅁ → ㅅ]) can also be processed as "ㅎ".

The lattice sounds "ㅌ", "ㅍ", and "ㅊ" associated with the [b] button, [ㅁ] button, and [ㅅ] button can be recognized by two-stage horizontal regression drag. According to the earlier application, the result of Figs. 19-21 is recognized as "male", but according to an embodiment of the present invention, it is recognized as "top". In Fig. 19-21, two-stage leftward regressions starting from the [b] button show an example in which "ㅌ" is recognized.

It seems to recognize "ㅊ" by the drag started from the [ㅅ] button. The [ㅅ] button is in a position where it is difficult to use the two-stage horizontal regression drag in a straight line. First, it is possible to use the "add stroke" button as shown in Figs. 19-22. "ㅊ" is recognized as it was dragged like [ㅅ → Add stroke → ㅅ (disable) → Add stroke → ...] from the [ㅅ] button that is the drag start button. This is the part already described in the earlier application (eg Figs. 15-14). The result of Figures 19-22 is 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 way is to use the two-stage regression drag in Fig. 19-4. In Fig. 19-23, it was dragged to [ㅅ → space → Korean → ㄹ → ㅅ → ...], and it can be seen that a two-stage leftward regression drag was made as in the figure 19-4. If you see the node where "ㅅ" appears again from the [ㅅ] button, which is the drag start button in the button trajectory, it is not [ㅅ → X → ㅅ → ...], but [ㅅ → X → Y → Z → ㅅ → ...] As it is the same as, it can be recognized as a 2-stage regression drag. Of course, as already described, the left upward dragging in the diagonal direction may also have the same button trajectory, but in this embodiment, an example of processing the button trajectory as a leftward dragging is shown. Therefore, the result of FIGS. 19-23 is recognized as "true".

Figure 19-24 is an example of another modified form of two-stage regression drag. In Fig. 19-24, it was dragged to [ㅅ → space → ㅅ → space → ㅅ → ...], but it can be recognized as "ㅊ" by considering 2 consecutive times of 1st stage regression drag as 2nd stage regression drag. The result of Figures 19-24 is also "True". It goes without saying that it is possible to apply the first stage regression drag No. 2 in a row in the same way as the input of “ㅊ” in Figs. 19-24 to the input of "T" of the "top" of Figs. 19-22.

Figure 19-25 shows an example of recognizing "ㅊ" by inputting "ㅈ" by horizontal regression drag and combining it with the [Add Stroke] button. The button trajectory in Figure 19-25 was dragged to [ㅅ → ㅇ → ㅅ → Add stroke → ...], but "ㅈ" is recognized in [ㅅ → ㅇ → ㅅ → ...] and successive [Add stroke] buttons As "ㅊ" can be recognized. The result in Figures 19-25 is also "True". The use of the [add stroke] button in Figs. 19-25 was also seen in the previous application, but it can be said that it is an achievement of the present invention to show that the related consonants can be input by regression drag without using the stroke add button in the present invention. will be.

Next, we show an example of inputting double consonants by vertical regression drag. In Figures 19-26, it can be seen that starting from the [ㅅ] button and dragging upwards. The results in Figures 19-26 are "paired". Since there is a [Add Stroke] button under the [ㅅ] button, the downward regression drag was not applied. Likewise, since the button trajectory in Figs. 19-27 started from the [b] button and dragged downwards [b → ㅁ → ㄴ → ...], the double consonant "ㄸ" related to "b" is recognized. As a result of Figures 19-27, "sweat" is recognized. The case drawings are omitted because the remaining pair consonants "ㄲ", "ㅃ", and "ㅉ" are the same.

In Figures 19-27, it is processed as if the double 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 breaking. For example, if the button trajectory becomes like [b → ㄱ → ㄴ → ㅁ → ㄴ → ...], it starts from the [b] button, and the rightward regression drag occurs once, and the downward regression drag occurs once in a row. Able to know. That is, "c" is recognized by a 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 consonants] function button for inputting double consonants on the keyboard of LG Electronics is located in the lower left corner of the [#] position, and there is a [ㅣ] button above the [-] button on the left, so drag the [Twin consonants] button. To do this, you must go through the [ㅡ] button and the [ㅣ] button. However, in the drag input through the present invention, it is also possible to input consonants including trellis and diconsonants as initial and final consonants with a single uninterrupted drag without dragging with the [double consonant] button. It is one of the achievements.

34.5 Example of inputting related consonants using regression drag (Pantech keyboard)

Figures 19-28 are Pantech's 12-button Korean keyboard. The input rules according to Figs. 19-28 are widely known and are not described in detail in this embodiment. It can be seen that "ㅋ" and "ㄲ" are related to the [ㄱ] button, including "ㄱ". This is the same for the [c] button, [ㅂ] button, and [ㅈ] button, respectively. In addition, it can be seen that "ㄹ", "ㅅ", and "ㅎ" are associated with the [b] button, [ㅁ] button, and [ㅇ] button, respectively, including the corresponding consonant. The number of related alphabets does not exceed the maximum of 3, and the number of alphabets related to the second or more is maximum of 2. Similarly, a case of recognizing a lattice sound or secondly arranged consonants by horizontal regression drag, and recognizing diconsonants by vertical regression drag is shown.

The button trajectory in Figure 19-29 is [ㄱ → ㄷ → ㄱ → ㅣ → ㅏ → Backspace → ㅏ → ㅓ → ㄴ → ㅂ → ㅁ → ㅂ]. The downward regression drag can be detected in [ㄱ → ㄷ → ㄱ → ...] starting from the [ㄱ] button, and as a result, "ㄲ" can be recognized. The button trajectory from the vowel button to the vowel button is [...→ ㅣ → ㅏ → backspace → ㅏ → ㅓ → ...]. The keypad in Figures 19-29 must be dragged through the [l] button or the [ㅓ] button in order to enter the vowel "ㅏ". As a method of recognizing vowels in the earlier application, the first dragged vowel button is treated as valid, and the vowel buttons that can be combined including the first dragged vowel button are treated as valid buttons (see Fig. 15-17). Another alternative was to treat all the dragged vowel buttons as valid vowel buttons was 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, Figure 19-6), Samsung Electronics' keyboard (eg, Figure 19-15), and LG Electronics' keyboard (eg, Figure 19-19). There is no problem if they are arranged. However, if there is a vowel button (eg [ㅏ] button) that is not adjacent to the consonant button, such as the Korean QWERTY keyboard or the Pantech keyboard in Fig. 29-28, the vowel (eg vowel "ㅏ") and the vowel are in the vowel. There is a drawback of not being able to enter related vowels. The button [ㅏ] in Figs. 19-28 is adjacent to the consonant button [b] by a diagonal vertex, but is considered to be not adjacent in this embodiment. This is because the buttons are densely clustered, so they cannot be dragged to the [ㅏ] button without passing the [ㅣ] button or the [ㅓ] button through the [b] button. This is because even if there is a slight gap between the button and the button, it is impossible to drag from the [b] button to the [ㅏ] button without passing through the [ㅣ] button or the [ㅓ] button.

Accordingly, the present embodiment shows an example of processing a vowel button that is not adjacent to the consonant button in such a way. The button trajectory from the vowel button to the vowel button in Figure 19-29 is [...→ ㅣ → ㅏ → backspace → ㅏ → ㅓ → ...]. In the input rule in Figures 19-29, "I+ㅏ" does not exist. In addition, it can be seen that "ㅏ", which is clearly "ㅏ+ㅏ", is clearly indicated by "backspace" and "ㅏ" instead of consecutive vowels after "ㅏ". If “I” is dragged after “ㅑ”, “ㅒ” will be recognized. However, "ㅓ" dragged after "ㅑ" does not form an appropriate vowel according to the input rule of Figs. 19-29. Therefore, it can be seen that the "ㅓ" dragged to the end just passes to input the final consonant. This can be seen from the fact that the button on which the drag is finished is the consonant button (eg [ㅂ] button). The button trajectory after the last vowel button is [...→ ㄴ → ㅂ → ㅁ → ㅂ]. The final dragged consonant "ㅂ" is always considered valid. It is recognized as the final consonant "ㅍ" because it can detect the dragged leftward with [ㅂ → ㅁ → ㅂ]. Eventually, the result of Figures 19-29 becomes "??".

The consonant input is almost similar to the embodiment shown in the keyboard of Samsung Electronics Co. of 23.3, so detailed descriptions are omitted. In this embodiment, inputting vowels by continuous dragging on a keyboard having vowel buttons not adjacent to the consonant button in a face is summarized as follows.

It will be described based on Figures 19-28. First of all, "A" can be entered by dragging to [ㄱ → ㅣ → ㅏ]. As described above, since "I+ㅏ" is not defined as an input of another vowel, the previously dragged [I] button is regarded as an invalid button. This is because if it was for the user to input "ki", the drag would have ended at the [ㅣ] button. Likewise, when dragged to [ㄱ → ... → ㅓ → ㅏ], it can be recognized as "A". This is because if it was for the user to input "go", the drag would have ended at the [ㅓ] button. Next, "Gya" is possible as "ㄱ → ㅣ → ㅏ → Backspace → ㅏ], as shown in Fig. 28-9. Since the 3rd dragged [ㅏ] button is the button intended by the user, prior to [ㅏ] This is because the [I] button that cannot be combined is invalidated and the last [ㅏ] button is a valid button, and the rest of the vowel buttons adjacent to the consonant button can be processed as described in the applicant's earlier application, so the description is omitted.

Next, we show how to fix it by putting a fake button on the top of the keypad (keyboard). In Figure 19-30, fake buttons are placed in the top 5 rows. For convenience, the five fake buttons will be called DB1, DB2, DB3, DB4, and DB5. In the embodiment of the present invention, it is not necessary to put one fake button on the top of the DB, but in order to identify the two-stage regression drag in Fig. 19-4 and the oblique regression drag in Fig. 19-5, the column of the button It is more flexible to put fake buttons according to the number.

The button trajectory in Figure 19-30 is [ㄱ → DB2 → ㄱ → DB3 → DB4 → ㅏ → ㅓ → ㄴ → ㄷ → ㄱ → ㄷ → ㄱ]. "ㄲ" is recognized because it is dragged upward in [ㄱ → DB2 → ㄱ → ...] from the [ㄱ] button, which is the drag start button. The button trajectory from the vowel button to the vowel button is [...→ ㅏ → ㅓ → ...], in order for the user to intentionally drag to the vowel button [ㅏ] that is not adjacent to the consonant button in a face. Since it was dragged to the [ㅏ] button through the fake buttons (DB3, DB4), in this case, it is reasonable to treat the [ㅏ] button as a valid button. If the user was to input "ㅓ", the [ㅓ] button is adjacent to the consonant button in a face, so drag like [ㄱ → DB2 → ㄱ → ㄷ → ㄴ → ㅓ → ...] Because it would have been. Since "ㅏ+ㅓ" is not defined in the input rule of Fig. 19-30, the vowel button [ㅓ] is invalidated. The button trajectory after the last vowel button [...→ ㄴ → C → ㄱ → C → ㄱ], the last dragged consonant button [ㄱ] is a valid button and the consonant "ㄲ" Is recognized. Eventually, the result of Figs. 19-30 is recognized as "cut".

As for the result of Figs. 19-30, while the user is familiar with the detailed drag input rules, the user must think in the brain whether the input vowel is "ㅏ" or "ㅓ". Figures 19-31 make it easier to enter "click". The button trajectories in Figure 19-31 are [ㄱ → DB2 → ㄱ → DB3 → DB4 → ㅏ → DB4 → DB3 → DB2 → ㄱ → ㄷ → ㄱ]. Since the dragged vowel button is only the [ㅏ] button, the user does not need to think about whether the input vowel is "ㅏ" or "ㅓ" when it is dragged to [...→ DB4 → ㅏ → ㅓ →...]. 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 2-beol-type keyboard currently used as a standard in PCs, and is generally referred to as a QWERTY character board. It consists of 14 consonant buttons and 12 vowel buttons. Two consonants "ㄲ", "ㄸ", "ㅃ", "ㅆ", and "ㅉ" corresponding to the [a] button, [c] button, [ㅂ] button, [ㅅ] button, and [ㅈ] button Is related. This can be easily seen from entering "ㄲ = shift + ㄱ". When inputting a double consonant by a continuous drag, it is possible to process using the vertical regression drag or horizontal regression drag described above.

For example, “??” may be recognized by dragging as shown in FIGS. 19-32. Since the consonant associated with the [a] button is one "ㄲ" except for "a", it is as described in other embodiments that "ㄲ" can be recognized by vertical regression drag or horizontal regression drag.

On the QWERTY Korean keyboard, there is a vowel button located on the side not adjacent to the consonant button. In this way, the vowel input by continuous drag on the keyboard with the vowel button not adjacent to the consonant button is separately summarized in Chapter 35.

34.7 Summary of examples of inputting 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 an initial consonant and a final consonant using a regression drag. Showed. In summary, the first dragged consonant button is regarded as a valid consonant button, and a regression drag is detected among the consonant buttons dragged before the vowel button and processed as a promised consonant (eg, "ㅋ"). Likewise, the consonant button (that is, the last dragged consonant button) is regarded as a valid consonant button, and the last dragged consonant button among the dragged consonant buttons after the last dragged vowel button (eg "a"). It detects the regression drag compared to and treats it as a promised consonant (eg "ㄲ").

As already described, each regression drag expressed in FIGS. 19-1 to 19-5 can be defined so that an individual input object is recognized. In an embodiment of the present invention, a consonant (eg "ㄲ", "ㅋ") associated with a specific consonant button (eg, [a] button) through a regression drag other than the button (ie, regression drag in one or more steps) is provided. It showed a recognized case. More specifically, a case in which the second associated or arranged consonants or lattice sounds are recognized by horizontal regression drag was shown, and a case in which double consonants are recognized by vertical regression drag was shown.

The steps are as follows. The following is the case when drag starts from the consonant button and the drag ends at the vowel button, or the drag starts at the consonant button and the drag ends at the consonant button.

In a keyboard that has a large number of consonant buttons and a large number of vowel buttons on the screen (liquid crystal) densely arranged in a grid, Korean characters (consonants) by dragging the buttons continuously without being broken in the touch (or mouse click) state , Vowels, conjugated letters, words or phrases),

At least one consonant button among the consonant buttons is associated with a plurality of consonants,

(a) detecting the start of a drag operation and recognizing a button trajectory including a consonant button (drag start button) in which the drag is started

(b) Button trajectory from the drag start button to the front of the vowel button

or

If there is no collection button among the dragged buttons, the button trajectory from the drag start button to the drag end button

In the step of detecting a regression drag including the drag start button

(c) recognizing a consonant promised for the regression drag among consonants associated with the consonant button on which the drag has started

Korean character input method by continuous drag on a screen (liquid crystal) keyboard, characterized in that characters are input by using

The above is for the drag button trajectory [ㄱ → ㄴ → ㄱ → ㄹ → ㅅ → ㅡ → ㆍ → ㅇ → ㅁ → ㅂ → ㅁ → ㅂ] when dragging ends at the bar button [ㆍ] (ie You can refer to [ㄱ → ㄴ → ㄱ → ㄹ → ㅅ → ㅡ → ㆍ]). It was explained that the regression drag can be detected in the button trajectory [ㄱ → ㄴ → ㄱ → ...].

The following is a case where the drag starts from the consonant button and the drag ends from the consonant button through the vowel button.

In a keyboard that has a large number of consonant buttons and a large number of vowel buttons on the screen (liquid crystal) densely arranged in a grid, Korean characters (consonants) by dragging the buttons continuously without being broken in the touch (or mouse click) state , Vowels, conjugated letters, words or phrases),

At least one consonant button among the consonant buttons is associated with a plurality of consonants,

The drag starts at the consonant button and ends at the consonant button including the vowel button,

(a) detecting the start of a drag operation, recognizing the consonant button (drag start button) on which the drag has started as a valid button, and recognizing a promised initial consonant from the buttons in front of the first vowel button among the dragged button trajectories

(b) Recognizing the vowel promised in the button trajectory from the first vowel button to the last vowel button as a neutral vowel in the drag button trajectory

(c) Detecting the regression drag of the consonant button as the drag end button from the button trajectory from the button after the last dragged vowel button to the consonant button as the drag end button

(e) recognizing a consonant promised for the detected regression drag as a final consonant among consonants associated with the consonant button, which is the drag end button.

Korean character input method by continuous drag on a screen (liquid crystal) keyboard, characterized in that characters are input by using

For the above, refer to the drag button trajectory [ㄱ → ㄴ → ㄱ → ㄹ → ㅅ → ㅡ → ㆍ → ㅇ → ㅁ → ㅂ → ㅁ → ㅂ] in Fig. 19-10. In the button trajectory [...→ ㅂ → ㅁ → ㅂ], it detects the regression drag of the [ㅂ] button, which is a consonant button that has been dragged, and recognizes the input of the consonant (eg "ㅍ") related to the [ㅂ] button. Explained that you can.

Also additionally,

In the above two cases,

The regression drag is one or more regression drags.

Korean character input method by continuous drag on the screen (liquid crystal) keyboard, characterized in that

And in the above,

Consonants arranged second to the grid or consonant buttons are recognized by horizontal regression drag

And

Double consonants recognized by vertical regression drag

Korean character input method by continuous drag on the screen (liquid crystal) keyboard, characterized in that

Also, from the drag button trajectory [ㄱ → ㄴ → ㄱ →...] in Fig. 19-10 and the positional relationship between the [ㄱ] button and the [b] button, horizontal regression drag (more precisely, "right regression drag") is detected. Explained that it can be done.

In Figs. 19-13 and 19-14, a consonant (ex. [ㆍ] button) promised by a regression drag that starts dragging from a vowel button (eg [ㆍ] button) and returns to the vowel button (eg [ㆍ] button). It was possible for "he") to be recognized. This is summarized below.

In a keyboard that has a large number of consonant buttons and a large number of vowel buttons on the screen (liquid crystal) densely arranged in a grid, Korean characters (consonants) by dragging the buttons continuously without being broken in the touch (or mouse click) state , Vowels, conjugated letters, words or phrases),

Promised consonants are recognized by a regression drag from a vowel button to a button other than a vowel button and return to the vowel button

Korean character input method by continuous drag on the screen (liquid crystal) keyboard, characterized in that

Although not described in the embodiment of the present invention, a number corresponding to each button may be input by one of the diagonal regression drag lines in Figs. 19-5. Of course, the downward left regression drag can be the same as the two-stage leftward regression drag in Fig. 19-4 by comparing only the button trajectory, so if there is another input object to be input by the two-stage leftward regression drag in Fig. 19-4, it is "bent". You have to consider the angle together.

Furthermore, it is possible to recognize a number corresponding to each button by dragging in the diagonal direction, not by dragging in the regression. This can be easily implemented by analyzing only the button trajectory without calculating the "bending" angle because only the button on which the drag is finished is a button in the diagonal direction. However, when the drag starts from the vowel button and ends with the consonant button (eg, when the drag ends with the [b] button by dragging upward from the [ㅓ] button on the LG keyboard, it is treated as an input of "vowel + consonant" It is processed as input of numbers without doing so. In the case of dragging upward left or upward dragging from the top button, it is explained that it is possible to easily solve it without the possibility of errors (errors in the 0-stage drag and 0-stage return drag) by placing the false buttons of DB1 ~ DB5 at a small height. I did.

35. Vowel recognition by continuous drag on a keyboard with vowel buttons not located on the side adjacent to the consonant button

There are 12 vowel buttons on the 2-beol-sik keyboard (ie, QWERTY-Han keyboard) of Fig. 18-1(*). There are 21 vowels in modern Korean, of which "ㅒ" is related to the [ㅐ] button, and "ㅖ" is related to the [ㅔ] button. This can be easily seen from entering "ㅒ = shift + ㅐ" and "ㅖ = shfit + ㅔ". Excluding 14 of 21 modern Korean vowels (12 displayed on the button + ㅒ, ㅖ), the remaining 7 vowels are "ㅚ", "ㅘ", "ㅙ", "ㅟ", "ㅝ", "ㅞ", It is a double vowel consisting of a combination of all two vowels as "ㅢ". It can be seen that 5 vowels out of 7 double vowels are finally combined with "ㅣ".

In the earlier application (Chapter 27), the first dragged vowel button was assumed to be a valid button. However, if there is a vowel button that is not adjacent to the consonant button as shown in Fig. 19-32, the vowels "ㅓ" and "ㅏ It will be described to input vowels that are not adjacent to the consonant button as a neutral vowel, such as ", ...". The key in this embodiment is to identify vowel buttons that form valid syllables. When there are multiple valid vowels (i.e., if there is ambiguity), it is also possible to display a list for the user to select. However, in the embodiment of the present invention, it is suggested to identify exactly one vowel with a reasonable rule.

In the Korean QWERTY keyboard, the vowel button consists of three rows (line). The vowels "ㅛ", "ㅕ", "ㅑ", "ㅐ" and "ㅔ" in the first row are not used as front vowels constituting a double vowel. Therefore, dragging from the vowel button in the first row to the vowel in the second row or the third row does not form a double vowel. Also, the vowels arranged on the right side of the second row do not form a double vowel with the vowels arranged on the left. For example, "ㅣ" (right vowel) and "ㅏ", "ㅓ", "ㅗ" (left vowel) do not form a double vowel, and "ㅏ" (right vowel) and "ㅓ" (left vowel) It does not form a double vowel, and "ㅓ" (right vowel) and "ㅗ" (right vowel) do not form a double vowel. This can be considered that most of the double vowels 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 "ㅓ", "ㅣ") can form a double vowel, but vowels in the 2nd row (eg "ㅓ") And vowels in the 3rd row (eg "-") do not form a double vowel.

When entering a vowel not adjacent to the consonant button as a neutral vowel, the vowel on the right and the vowel on the left do not form a double vowel, the vowel on the 2nd row and the vowel on the 1st row. The fact that the vowels do not form a double vowel, and that the vowels located in the second row and the vowels located in the third row do not form a double vowel is an important property of the Korean QWERTY keyboard in applying the present invention.

Let's look at the case where the user drags in order to input "Ann" as shown in Figure 20-1, [ㅇ → ... ㅛ → ㅕ → ㅑ → ㅏ → ㅓ → ㅗ → ... ㅇ]. In this case, the user drags to the vowel button in the first row to input the vowel "ㅏ", proceeds to the intended vowel "ㅏ" in the second row, and proceeds to the left consonant button again in the second row. In the earlier application (Chapter 27), the first dragged vowel (eg [ㅛ] button) was considered to be a valid button assuming that all vowel buttons are adjacent to the consonant button in a face, but if the user says "ㅛ" If it was for inputting [...→ ㅛ → ㅕ → ㅑ → ㅏ → ...]", there is no reason to proceed further to the right, and after dragging to [ㅛ], the drag proceeded to the consonant button on the left again. [...→ ㅛ → ㅕ → ㅑ → ㅏ → ㅓ → ㅗ → ...] does not form a double vowel, so it is reasonable to judge that the rightmost vowel "ㅏ" is the intended vowel. So the result is recognized as "ang".

The core of the present invention is that there is a vowel button that is not adjacent to the consonant button in a plane like the Korean QWERTY keyboard but is surrounded only by vowel buttons, and the vowel buttons dragged from the keyboard where the consonant button is arranged on the left and the vowel button is located on the right. Among them, the vowel button located on the rightmost side is treated as a valid vowel. Among the dragged vowel buttons, the vowel button located on the rightmost side will be referred to as the "dragged rightmost vowel button", and more simply "the rightmost vowel button" or "the rightmost vowel button". In addition, when a vowel button that is considered a valid button, the rightmost vowel and a double vowel are formed, the double vowel ("ㅚ" in Fig. 15-17) is recognized.

The button question in drawing 15-17 of the previous application is [ㄱ → ㅅ → ㅎ → ㅗ → ㅓ → ㅏ → ㅣ → ㅏ → ㅓ → ㅗ → ㅎ → ㄹ → ㅇ]. The button trajectory of the vowel part is [...→ ㅗ → ㅓ → ㅏ → ㅣ → ㅏ → ㅓ → ㅗ →...]. As already explained, it is reasonable to recognize "awesome". Even if interpreted as the idea of the present invention, the rightmost vowel [ㅣ] is a valid vowel button, and it is combined with the preceding “ㅗ” to become a double vowel “ㅚ”. The reason why it is not "hoe" in Fig. 15-17 is because there is a separate [ㅐ] button on the QWERTY Korean keyboard, so you do not enter "ㅙ = ㅗㅏㅣ", but "ㅙ = ㅗㅐ". If the user was to input "strong", the user intentionally avoids the vowel button [ㅗ] (eg dragging to the first row vowel or the third row vowel) until the [ㅏ] button. Drag it and drag it back to the consonant button.

Korean Hangul has a syllable consisting of "initial + neutral" (that is, "consonant + vowel") and a syllable consisting of "initial + neutral + final" (that is, "consonant + vowel + consonant") There is an alphabetic combination). In the case of "Initial + Neutral", the problem becomes much simpler because the drag ends on the vowel button. The last dragged vowel button is treated as a valid button, and if a double vowel can be formed with the last dragged vowel button, the double vowel can be recognized. In other words, when the user starts dragging from the consonant button and the drag ends from the vowel button to input the letter consisting of "initial + neutral", regardless of the position of the vowel button (eg, the rightmost vowel), the last dragged vowel button Is treated as being the rightmost vowel.

If there is a consonant button group on the left and a vowel button group on the right, like the Korean QWERTY keyboard, it is reasonable to regard the rightmost vowel as a valid vowel button as described. However, if there is a group of vowel buttons that are not adjacent to the consonant button on the upper side, the uppermost vowel is treated as a valid vowel button, if the lower one is the lowest vowel, and if the left is the leftmost vowel. It is natural to do it. These rightmost vowels, leftmost vowels, top vowels, bottom vowels, etc. will be collectively referred to as "last vowel" (more precisely, "dragged last vowel button" or "last vowel button"), and this embodiment For convenience, the term "rightmost vowel" is used as it is.

It looks at the dragged case as shown in Fig. 20-2. The vowels in the 3rd row (eg "ㅜ") and the vowels in the 2nd row (eg "ㅣ") can form a double vowel, and the vowels in the 3rd row (eg "ㅜ") and the 1st row can form a double vowel. Vowels of (eg "ㅔ") can form a double vowel. The button trajectory from the first dragged vowel button to the last dragged vowel button in Figure 20-2 is [...→ ㅗ → ㅠ → ㅜ → ㅡ → ㅏ → ㅣ → ㅔ → ...]. When looking at "ㅗ+ㅣ", "ㅜ+ㅣ", and "ㅜ+ㅔ", it is determined whether the user wanted to enter "ㅚ", "ㅟ", or "ㅞ". Difficult 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 combined earlier in "ㅔ". In the result of Fig. 20-2, "Wok" is recognized. If there were no double vowels that could be combined with the highest priority vowel "ㅔ" in the above button trajectory, it is natural that "ㅔ" is treated as a valid button.

Currently, the technique of displaying a list of recommended words using a word dictionary on a smartphone is widely used. If it is assumed that words such as "predominance", "woock", ... were stored in the word dictionary, and the previously entered character was "right" before the dragging in drawing 20-2 occurred, dragging in drawing 20-2 It is also possible to interpret "up" and "woke" as "upper" and "woke" to display "predominance" and "woock" in the recommended word list. This is because a longer drag occurs in the process of a user trying to input "predominance", and it can be considered as dragged to the rightmost vowel [ㅔ] button. This is based on the premise that there is a "predominance" in the word dictionary, and even if it is not a double vowel that can be combined with the rightmost vowel or the rightmost vowel, it forms a word in the word dictionary among a number of candidate vowels that can be recognized. The vowel is interpreted as a vowel intended to be input by the user, and the user is given a choice. If there is no word dictionary or even if there is a word dictionary, if there is no "predominance" in the word dictionary, it will be appropriate to recognize and output the result of Fig. 20-2 as "Wok" based on the rightmost vowel "ㅔ".

As already explained, the property that the vowels on the right and the vowels on the left do not form a double vowel in a QWERTY font is that when a user drags and inputs a double vowel, dragging a vowel forming a double vowel while dragging from left to right Provides good characteristics to be. As shown in Fig. 20-2, the user drags the same as [...→ ㅜ → ... → ㅔ → ...] to input the vowel "ㅞ" and the consonant on the left to input the final consonant "ㄱ" This means that vowels when swiping toward the button (ie, from right to left) generally do not combine with the rightmost vowel to form a double vowel.

Figure 20-3 is an example of having 10 fake buttons of DB1 ~ DB10 from left to right with a small height in accordance with 10 columns on the top of QWERTY Hangul keyboard. The vowel buttons adjacent to the consonant button and the face in the QWERTY character board as shown in Figure 20-3 are three buttons: [ㅛ] button, [ㅗ] button, and [ㅠ] button. However, as shown in Fig. 20-3, if you can drag through the fake button area or bypass the keyboard outside the first row of vowels (eg "ㅕ", "ㅑ", "ㅐ", "ㅔ") is a consonant It can be directly dragged from a button to a specific vowel (eg "ㅑ") without going through another vowel button. Vowels in the 3rd row (eg "ㅜ", "ㅡ") are also specific vowels (eg, "ㅜ") in the consonant button through function button areas such as the [space] button, [Enter] button, and [backspace] button. ) Can be directly dragged. In the case of a vowel button that is not adjacent to the consonant button by a plane, if there is a detour 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 surrounded only by vowels, such as the [ㅓ] button and [ㅏ] button, the application of the core idea of the present invention is required, and the user bypasses it even if it is not a vowel button completely enclosed only by vowel buttons. In the case of not dragging, the core idea of the present invention (the rightmost vowel is treated as a valid vowel button) can be applied.

Even if there is no fake button area as shown in Fig. 20-3, if a "recommended word area" that provides a list of recommended words at the top of the keyboard while having a word index in the character input system is provided, this recommended word area is made like a fake button area. Just use it. The word recommendation function is similar to the "auto-complete function" in the address bar of Windows or web browsers, and you can think of the recommended word area as an area that displays the list of candidates for automatic completion. This is widely used in text input device applications such as smartphones. There is no case presentation by drawing.

It has been explained that "ㅒ" related to the [ㅐ] button and "ㅖ" related to the [ㅔ] button can be entered by regression drag. There is no confusion and the easiest way to enter "ㅒ" is to drag from Figure 20-3 to [...→ DB9 → ㅐ → DB9 → ㅐ → ...]. In the case of "ㅖ", you can enter "ㅖ" by dragging to [...→ DB10 → ㅔ → DB10 → ㅔ → ...]. Drawings based on the Grag trajectory are omitted.

However, since the regression drag has the feature that the same button appears twice, it can be easily identified without using a fake button DBx. The button trajectory in Figure 20-4 is [...→ ㅐ → ㅏ → ㅑ → ㅐ → ㅏ → ...]. Since the [ㅐ] button appears twice, it can be seen that the regression drag has been performed for the [ㅐ] button, and the [ㅏ] button comes out twice, so it is easy to know that the regression drag has been performed for the [ㅏ] button. . The user's intended neutral vowel can be judged in two ways. First, since the alphabet related to the [ㅏ] button is not defined in the Korean QWERTY keyboard, the regression drag of the [ㅏ] button is not defined as a specific vowel. For example, "X (specific alphabet) = function button (shift) + ㅏ" or "X (specific alphabet) = ㅏㅏ" is not defined. Second, even if the regression drag of the [ㅏ] button is defined as the input of a specific vowel, the system judges that the vowel intended by the user is "ㅒ" because the rightmost vowel among "ㅐ" and "ㅏ" is the [ㅐ] button. can do. The most obvious is that the [ㅐ] button regression drag was performed before the regression drag of the [ㅏ] button, so it can be determined that the alphabet intended by the user is "ㅒ". [..→ ㅐ → X → ... → ㅐ → ...] After the regression drag of the [ㅐ] button is finished, the regression drag for the [ㅏ] button was not performed separately, but the regression of the [ㅐ] button In the process of dragging the surrounding buttons for dragging, the [ㅏ] regression drag was made by chance. In the result of Figure 20-4, "Gam" is recognized.

The above description appears similarly in the case of Pantech's Korean keyboard in Figs. 19-28. In the case of Figure 19-30, in order to enter the vowel "ㅏ", it was dragged past the "ㅓ" button that cannot be combined with "ㅏ", not past the [ㅣ] button that can be combined with "ㅏ". When there are multiple rightmost vowels as shown in Fig. 19-30 ("ㅏ" and "ㅓ" in Fig. 19-30), it is necessary to determine which of the plurality of rightmost vowels is a valid vowel button. need. In the example of Figs. 19-29, it can be clearly seen that the vowel button intended to be used is the [ㅏ] button (ie, the recognition result vowel is "ㅑ") because the regression drag has occurred for the [ㅏ] button. In the example of Fig. 19-30, the first dragged rightmost vowel among the dragged rightmost vowels (eg [ㅏ] button, [ㅓ] button) is treated as a valid button. In the case of a plurality of dragged rightmost vowels, it is reasonable to process the first rightmost vowel among the rightmost vowels as a valid button. When there are multiple rightmost vowels, the user uses various means (e.g. fake buttons, function buttons, outside buttons, dragging from 1st row to 2nd row in QWERTY's font) to the intended vowel. This is because the input can be dragged to the intended vowel through.

In the present invention, it was shown through the examples of Pantech's Korean keyboard and Korean QWERTY keyboard that vowels are recognized by continuous drag in the case of having a consonant button and a vowel button that is not in contact with the face. Currently, various types of keyboards are on the touch screen, and it is obvious that the idea of the present invention (eg, regards the rightmost vowel as a valid vowel button) can be applied equally to other keyboards. One more example of another keyboard is Google's single vowel keyboard. "ㅑ", "ㅕ", "ㅛ", and "ㅠ" are omitted from the QWERTY Korean keyboard, so the QWERTY Korean keyboard is composed of an 8-row keyboard compared to a 10-row keyboard. Enter "ㅑ = ㅏㅏ", "ㅕ = ㅓㅓ", "ㅛ = ㅗㅗ", "ㅠ = ㅜㅜ", so you can use the [ㅏ] button, [ㅓ] button, [ㅗ] button, [ㅑ] button respectively. , "ㅕ", "ㅛ", and "ㅠ" are related. This is the same as "ㅒ" and "ㅖ" are associated with the [ㅐ] button and the [ㅔ] button in the QWERTY Korean keyboard, and you can refer to the input case of "ㅒ" in the QWERTY Korean keyboard. Since the keyboard is widely known at present, the drawing is omitted. The point where "ㅣ", which forms the back vowel of a double vowel, is located on the far right of the 2nd row also has similar properties to the QWERTY-han character board. Google's single vowel keyboard also handles the rightmost vowel as a valid button as explained in the QWERTY Chinese keyboard on the same principle, so the case presentation is omitted.

The above contents are summarized in steps as follows.

In a keyboard that has a large number of consonant buttons and a large number of vowel buttons on the screen (liquid crystal) densely arranged in a grid, Korean characters (consonants) by dragging the buttons continuously without being broken in the touch (or mouse click) state , Vowels, conjugated letters, words or phrases),

The keyboard includes at least one consonant button and one or more vowel buttons that are not in contact with the face,

(a) Recognizing the dragged first vowel button, the dragged button in the middle, and the dragged last vowel button

(b) recognizing the most distant vowel from the consonant button group as a valid vowel button among the dragged buttons

(c) determining whether a double vowel is formed by combining with a vowel recognized as the valid vowel button among the dragged buttons

Korean character input method by continuous drag on a screen (liquid crystal) keyboard, characterized in that characters are input by using

.

Claims (1)

In the method of inputting Korean on a screen keyboard having a Korean consonant button and a Korean vowel button,
A consonant is recognized in response to pressing the consonant button on the screen keyboard,
The vowel is recognized in response to the press of the vowel button on the screen keyboard,

Images