1. Field of the Invention
This invention relates to the validation of character code sequences.
2. Discussion of the Related Art
Double-byte character encoding is commonly used for a number of purposes, among them encoding complex character sets such as GB 2312-80, the simplified Chinese characters used in mainland China. GB 2312-80 contains 7,445 Chinese characters represented as a pair of bytes wherein each byte is a number from 161 to 254. This allows the mixing of the Chinese characters with conventional ASCII text, which is represented by byte values in the range of 0 to 127. Technically, the simultaneous representation of GB 2312-80 with ASCII is called EUC-CN encoding, though we refer to it as GB 2312-80 throughout this specification for simplicity. This necessarily implies that bytes in the range of 161 to 254 must come in pairs and any string of such characters must have an even number of such bytes in a row between any two single-byte ASCII characters. Byte values in the range of 128 to 160 are invalid for GB 2312-80. Despite these rules, invalid characters and sequences, collectively referred to as “noise”, is found to occur in 5% to 10% of Chinese webpages and newswire texts. The origins of this noise is obscure.
Applications currently available for the processing of double-byte encodings are inadequate to cope with noise. For example, GB to unicode converters simply crash on the first invalid byte sequence and all information following the noise is lost.
Repairing such noise presents a problem of ambiguity. For example, consider the case of a nine-byte sequence of GB 2312-80 characters, all in the range of 161–254—which “half character” is the noise to be discarded? Discarding any one of the bytes will likely leave four perfectly valid Chinese characters, but in an incomprehensible sequence. In probability, only one of the bytes may be discarded so as to produce an intelligible string of characters.
What is needed is a method of validating strings of double-byte characters to detect and remove such noise.
Disclosed is a method of validating a byte sequence having a plurality of states, the method comprising designating one or more noise states from among the plurality of states, generating a most probable state sequence for the byte sequence, utilizing said state sequence to identify all noise in the byte sequence, and localizing said noise in said noise states.
In another aspect of the invention, the noise is then deleted from the byte sequence.
In another aspect of the invention, the noise state is an ASCII state.
In another aspect of the invention said generating of a most probable state sequence comprises calculating P(X0 . . . Xn|S0 . . . Sn), representing the conditional probabilities of said byte sequence given a state sequence.
In another aspect of the invention, said calculating P(X0 . . . Xn|S0 . . . Sn) comprises assigning a state label Si to each ith byte Xi of the byte sequence so as to maximize the equation:
wherein P0(S0) is the initial distribution of states; Ā(Si|Si−1) is a “state-to-state” transition matrix; and {overscore (B)}(Xi|Si) is a “byte-from-state” matrix of the probabilities of generating a byte value Xi given a state Si.
In another aspect of the invention,
where each p(Si−1→Si) is the probability that a particular Si state immediately follows an Si−1 state in a valid byte sequence having σ states.
In another aspect of the invention,
where each p(Si−1→Si) is the probability that a particular Si state immediately follows an Si−1 state in a valid byte sequence having three states.
In another aspect of the invention,
and said valid byte sequence is valid text in the GB 2312-80 character set.
In another aspect of the invention,
where hS(Xi) are histogram functions of the σ states and εj(Xi) are probabilities of associating noise with the noise state for bytes within r+1 ranges of byte values Xi.
In another aspect of the invention,
where hs(Xi) are histogram functions of the states, and εj(Xi) are probabilities of associating noise with the ASCII state within a plurality of Xi ranges for a three-state byte sequence.
Another aspect of the invention further comprises, providing a valid three-state byte sequence having an ASCII state and comprising valid ASCII and two-byte characters, computing an ASCII histogram hA(Xi) by a method comprising sampling valid ASCII text so as to measure the frequency of occurrence of each byte value; computing an unnormalized histogram of said sampling over the ASCII range of Xi; and normalizing said unnormalized histogram such that the entire column of the matrix containing said ASCII histogram sums to 1, and computing a first-byte histogram h1(Xi) by sampling valid two-byte text and computing the unnormalized first-byte histogram over the odd bytes, and normalizing said first-byte histogram such that the entire column of the matrix containing said first-byte histogram sums to 1, and computing a second-byte histogram h2(Xi) by sampling valid two-byte text and computing the unnormalized second-byte histogram over the odd bytes, and normalizing said second-byte histogram such that the entire column of the matrix containing said second-byte histogram sums to 1.
Disclosed is a program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform method steps for validating a byte sequence having a plurality of states, said method comprising designating one or more noise states from among the plurality of states generating a most probable state sequence for the byte sequence, utilizing said state sequence to identify all noise in the byte sequence, and localizing said noise in said noise states.
In another aspect of the device, said localizing of said noise in said noise states comprises examining each byte in said byte sequence that does not correspond to a noise state, determining if the byte is valid, and if the byte is not valid, then redesignating the state of said byte to a noise state.
In another aspect of the device, the device also comprises a lookup table of valid bytes, wherein said determination if a byte is valid is accomplished by accessing said lookup table.
Disclosed is a method of validating a byte sequence having a plurality of states including an ASCII state, the method comprising selecting the ASCII state as the noise state generating a most probable state sequence for the byte sequence by a method comprising: calculating P(X0 . . . Xn|S0 . . . Sn), representing the conditional probabilities of said byte sequence given a state sequence, wherein said calculating P(X0 . . . Xn|S0 . . . Sn) comprises assigning a state label Si to each ith byte Xi of the byte sequence so as to maximize the equation:
wherein P0(S0) is the initial distribution of states; Ā(Si|Si−1) is a “state-to-state” transition matrix; and {overscore (B)}(Xi|Si) is a “byte-from-state” matrix of the probabilities of generating a byte value Xi given a state SI; and utilizing said state sequence to identify all noise in the byte sequence, localizing said noise in said noise states, and deleting said noise from the byte sequence.
Referring to
Mathematically forcing a proper state sequence upon a corrupted byte sequence with the state-to-state matrix will result in invalid character codes, that is to say that there will be bytes labeled as ASCII state that don't correspond to any valid ASCII character and pairs of GB1 and GB2 bytes that don't correspond to any valid two-byte character. These invalid characters are detected and repaired by the repair module 110. As will be explained below, the repair module does this by “localizing” the invalid characters to one or more designated “noise states.”
The method utilized by the state sequence labeler to generate a state sequence for a particular byte sequence makes use of a probabilistic model. For any byte sequence:
X0, X1, X2 . . . Xn (1)
we wish to generate a corresponding state sequence:
S0, S1, S2, . . . Sn (2)
where each Xi is an integer from 0 to 255 (for eight-bit bytes) and each Si is either A, 1, or 2 for single-byte ASCII bytes, first double-byte bytes, or second double-byte bytes, respectively.
We may then model the conditional probabilities of the byte sequence of Equation 1 given the state sequence of Equation 2 as:
where P0(S0) is the initial distribution of states, namely P0(A)=P0(1)=P0(2)=⅓; Ā(Si|Si−1) is the state-to-state transition matrix and will have the properties of the Markov model being utilized; {overscore (B)}(Xi|Si) is the “byte-from-state” matrix of the probabilities of generating a byte value Xi given a state Si.
For any byte sequence having σ total states, the state-to-state matrix will be a σ×σ sized matrix:
The state-to-state matrix will have the following form in the case of the three-state Markov model shown in
where p(Si−1→Si) indicates the probability, or observed frequency, that a particular Si state for the ith byte immediately follows a particular Si−1 state for the immediately proceeding byte (i−1) in a valid byte sequence. It is to be understood that Equation 4b is the matrix for a three-state byte sequence. When applied to the GB 2312-80 character set, the state-to-state matrix is found to be as follows:
The significance of the matrix entries of
From Table 1 we see, for example, that the probability of an ASCII character (i.e., state A) being followed by another ASCII is p(A→A)=0.995157, while the probability of an ASCII being followed by the first byte of a two-byte character is only p(A →GB1)=0.004843. The numbers in Table 1 represent what the probabilities should be for valid text, and are derived from compiling statistics of actual valid text.
The {overscore (B)}(Xi|Si) matrix is described by:
where hs(Xi) are histogram functions of the states and εj(Xi) are probabilities of associating noise with the sth state within r+1 Xi ranges. This indicates that the sth state has been selected as the “noise state” in accordance with the invention as is more fully described below.
For the three-state Markov model of
where hA(Xi) is computed by sampling valid ASCII text, computing the histogram of its bytes, and then normalizing them so that the entire column of the matrix (including the epsilon's) sums to 1. First-byte histogram h1(Xi) is computed by sampling valid two-byte text and computing the histogram over the odd bytes, while the second-byte histogram h2(Xi) is computed over the even bytes. Histograms h1(Xi) and h2(Xi) are also then normalized to cause their respective columns to sum to 1. Notice that the above matrix implies that the ASCII state is the designated noise state.
The significance of the {overscore (B)}(Xi|Si) matrix entries with respect to GB 2312-80 is described by the following table:
where it can be seen, for example, that bytes associated with GB 2312-80 Chinese characters (i.e., 161≦Xi≦254) are most likely to have been generated by states GB1 and GB2, but have a small error probability, ε2, of deriving from an ASCII character.
To generate the state sequence for a given string of characters, Equation 3 is used to find the state sequence that maximizes the value of P(X0 . . . Xn|S0 . . . Sn). Then, all pairs of bytes labeled GB1 followed by GB2 are analyzed to confirm that they are valid GB characters (the GB 2312-80 character set contains some “gaps” within the valid range of bytes, so a preferred embodiment for such “gapped” character sets is to do this checking by looking up the values in a lookup table.) If they do not form a valid character both bytes are relabeled as the noise state, in this example as ASCII, in the state sequence.
The state sequence that results from the above operations is passed on to the repair module 110 and has the following properties:
where it can be seen that all of the noise is now localized into one state, namely the ASCII state. This is by way of illustration only, because we may modify the procedure of the sequence labeler 100 so as to localize all of the noise into one of the other states.
The repair module 110 simply identifies invalid ASCII characters in the sequence and deletes them. In another embodiment, the repair module 110 may also detect ambiguities in the string and make corrections by accessing a database of statistics of actual language samples.
Though we have described the invention with respect to the GB 2312-80 Chinese character set and with only three states and localized all the noise into the ASCII state, the invention is generalizable to any character set having a states, where a σ>1. Nor is the invention limited to character states having one and two-byte characters, but is generalizable to any combination of characters of any number of bytes. The fundamental procedure is to utilize a probabilistic model to localize all the error into a one or more designated noise states. Also, a state that represents forbidden transitions in byte values may always be added to the model and may also be used as a designated noise state. Hence, the invention may easily be generalized to all multibyte text and will be found useful as a filter for all manner of character converters and text translators, editors, search engines, and the like.
Further, it may be pointed out that more than one state may be designated as noise states and error assigned to each according to a set of rules. This is useful if one wishes to segregate different types of noise. Nor must the noise states correspond to actual valid states, but rather may be designated as separate individual states on their own.
The method of the invention may be executed as a program of instructions tangibly embodied upon a storage device readable by machine, such as a computer.
As an example of the workings of the invention, consider the following GB 2312-80 byte sequence where each two-byte sequence is shown with the Chinese letter it represents:
Now consider the case where the sequence is corrupted by a stray byte value, decimal 189, inserted at the beginning:
Current technology is incapable of determining whether the above sequence is valid or not, but a native speaker of Chinese would instantly recognized the corrupted sequence as gibberish. According to the invention, the corrupted byte string is passed to the state sequence labeler 100 of
The suspected byte sequence and the corresponding state sequence are passed to the repair module 110 where, assuming we have chosen to localize the noise to the ASCII state, the non-ASCII states are examined to test if they are within valid numeric ranges. Any found not to be are relabeled as ASCII. The ASCII states are then examined and any ASCII states not within acceptable byte values are considered invalid All the non-ASCII in our example are valid, however, so it only remains for the repair module 110 to move to the last step and flag or delete the invalid ASCII characters:
thereby recovering the correct sequence.
Of course, though we have depicted separate state sequence labelers 100 and repair modules 110, thesis is for illustrative and clarification purposes only. The functionality of the modules may be integrated together or conversely, further subdivided as desired by the practitioner of the invention.
It should be noted that the “states” of a byte sequence are ambiguous and therefore within the control of the user of the invention. The states selected for the method of the invention are dependent upon the noise one wishes to eliminate. In the above example, we used a three state Markov model with the ASCII state designated as the noise state. This is sufficient where the only noise we are interested in is invalid bytes, but we could expand the Markov model to find other noise. For example, additional states for punctuation, consonants, vowels, capitalized letters, and the like may be added to monitor other forms of corruption.
One may even use a Markov model that analyzes two or more bytes at a time, rather than one at a time. Hence the byte-from-state matrix {overscore (B)}(Xi|Si) would enlarge to 2562x# states with the definition of the states slightly modified. Such a model would pick out impermissible byte pairs (e.g., in an English version of the model, the letter q followed by anything other that a “u” could be picked out as noise, or any consonant not properly followed by a vowel).
It is to be understood that all physical quantities disclosed herein, unless explicitly indicated otherwise, are not to be construed as exactly equal to the quantity disclosed, but rather about equal to the quantity disclosed. Further, the mere absence of a qualifier such as “about” or the like, is not to be construed as an explicit indication that any such disclosed physical quantity is an exact quantity, irrespective of whether such qualifiers are used with respect to any other physical quantities disclosed herein.
While preferred embodiments have been shown and described, various modifications and substitutions may be made thereto without departing from the spirit and scope of the invention. Accordingly, it is to be understood that the present invention has been described by way of illustration only, and such illustrations and embodiments as have been disclosed herein are not to be construed as limiting to the claims.
This work was supported under a DARPA government contract, SPAWAR contract No. N66001-99-2-8916.
Number | Name | Date | Kind |
---|---|---|---|
4975916 | Miracle et al. | Dec 1990 | A |
5197810 | Zhang et al. | Mar 1993 | A |
5226148 | Littlewood | Jul 1993 | A |
5309358 | Andrews et al. | May 1994 | A |
5784069 | Daniels et al. | Jul 1998 | A |
5784071 | Tang et al. | Jul 1998 | A |
5793381 | Edberg et al. | Aug 1998 | A |
5898385 | Makino | Apr 1999 | A |
5940836 | Fukushima | Aug 1999 | A |
5964885 | Little et al. | Oct 1999 | A |
6018304 | Bessios | Jan 2000 | A |
6189006 | Fukushima | Feb 2001 | B1 |
Number | Date | Country | |
---|---|---|---|
20030070137 A1 | Apr 2003 | US |