# Patent

## Title
Method for processing K node count fields using an intensity variable

## Abstract

In a KStore having K nodes with respective K node counts a method for updating the K node counts includes processing a K node in accordance with a received particle to provide a processed K node and updating a node count in response to the processing. The processing of the processed K node includes building the processed K node in response to the received particle. A node count of a beginning of sequence node is updated. A beginning of sequence node includes a beginning of thought node. The received particle can be a particle of sensor data having a corresponding sensor node to provide a sensor node determination. A node count of the corresponding sensor node is updated in response to the sensor node determination. A subcomponent node is determined in response to the sensor determination and a K node count of the subcomponent node is updated.

## Background
a. The present application is a continuation-in-part of application Ser. No. 10,666,382, filed Sep. 13, 2003, entitled “SYSTEM AND METHOD FOR STORING AND ACCESSING DATA IN AN INTERLOCKING TREES DATASTORE” by MAZZAGATTI et al, now U.S. Pat. No. 7,158,975; and
b. The present application is a continuation-in-part of application Ser. No. 11/185,620, filed Jul. 20, 2005, entitled “METHOD FOR PROCESSING NEW SEQUENCES BEING RECORDED INTO AN INTERLOCKING TREES DATASTORE” by MAZZAGATTI now abandoned.


BACKGROUND OF THE INVENTION
1. Field of Invention
This invention relates to computing and, in particular to the field of database storage technology and the field of interlocking trees data stores
2. Description of Related Art
While interlocking trees datastores are covered in other patents by inventor Mazzagatti, it may be useful to provide a brief background summary of KStore and various features of said interlocking trees datastores.
A system and various methods for creating and using interlocking trees datastores and various features of the interlocking trees datastores have been developed. We refer to an instantiation of these interlocking trees datastores that we have developed as a KStore or just K. In particular, these structures and methods have been described in U.S. Pat. No. 6,961,733 and copending patent application Ser. No. 10/666,382, (now published as 20050076011A1) by inventor Mazzagatti. Additionally, we described a system in which such interlocking trees datastores could more effectively be used in U.S. Ser. No. 11/185,620, entitled “Method for Processing New Sequences Being Recorded into an Interlocking Trees Datastore.” This invention provides the process invented to build and access the structure.
In U.S. Pat. No. 6,961,733 and U.S. Ser. No. 10/666,382, (now published as 20050076011), also by inventor Mazzagatti, we explained some preferred methods used to build and access an interlocking trees datastore. The methods taught in both of these patents were written at a level that taught the methodology of how an interlocking trees datastore is built and accessed.
All references cited herein are incorporated herein by reference in their entireties.
BRIEF SUMMARY OF THE INVENTION
In a KStore having a plurality of K nodes with a plurality of respective K node counts a method for updating the K node counts of the plurality of respective K node counts includes processing a K node of the plurality of K nodes in accordance with a received particle to provide a processed K node and updating a node count in response to the processing. The processing of the processed K node includes building the processed K node in response to the received particle. A node count of a beginning of sequence node is updated. A beginning of sequence node includes a beginning of thought node. The received particle can be a particle of sensor data having a corresponding sensor node to provide a sensor node determination. A node count of the corresponding sensor node is updated in response to the sensor node determination. A subcomponent node is determined in response to the sensor determination and a K node count of the subcomponent node is updated.
A Result node of an asCase node of a current K node is compared with the sensor node to provide a processed subcomponent node determination. The received particle can be determined to be a delimiter particle to provide a delimiter determination. An end product node is determined in response to the delimiter determination and a K node count of the end product node is updated. The KStore has a plurality of levels including a current level and at least one lower level below the current level. A lower level delimiter is determined in response to the delimiter determination to provide a lower level delimiter determination. An end product node is determined in response to the lower level delimiter determination. A K node count of the end product node is updated. The KStore has a plurality of levels including a current level and at least one higher level above the current level and a further K node is determined on the at least one higher level. A K node count of the further K node is updated. The building can include a learn operation and the updating occurs based upon a learn determination. The updating of a K node count is determined by a learn type. The updating occurs based upon a query determination. The updating of a K node count is determined by a query type. The experiencing of the processed K node comprises traversing the processed K node. The updating includes adding an intensity value to the K node count.
While the K Engine is traversing and creating the K structure, a record of how many times each K path has been traversed may be needed to perform calculations related to the events, for example for calculating the potential of various events occurring. A count field may be added to each K node to contain a value that may be updated according to the processes related to traversing to query or create a K. In one implementation a parameter attached to the K Engine call indicates whether or not the count field is to be incremented. Typically, the count is incremented for learning functions and not incremented for query functions.
An example of this in a field/record universe is that as transaction records are recorded into the K, the count field for each K node traversed may be incremented by 1. Newly created K nodes might be initialized to 1. As queries about the transaction records are processed, the count fields may remain unchanged.
The increment value however may not always be 1. In a field/record universe the increment may be any value. For example, if the transaction records being recorded in the K are sorted so that all duplicate records are together, the learn routine may send the duplicate record only once with a larger intensity value to be used to increment or initialize the K node count fields. Furthermore, the intensity value need not always be positive. Records or paths may be deleted from the K by subtracting an intensity value.
A method for processing a particle stream in a KStore having a sensor level of elemental root nodes and a first level above the sensor level, the particle stream having a plurality of input particles, including receiving at least one particle within the particle stream to provide a received particle and first determining a current K node to determine a partial sequence location. The method also includes second determining a match in accordance with the received particle and the current K node to provide a match determination and processing the current K node based upon the match determination. A new node is created if the second determining is negative. A current K node is set to the new node. A node count is incremented and a particle type of the received particle is determined. The particle type is determined to be a delimiter. A match is determined between the delimiter and a Result node of an asCase node of the current K node to provide a delimiter match determination. An end product node is built if the delimiter match determination is negative. The current K node is set to a sequence beginning location. The sequence beginning location can be a beginning of thought location. The current K node is set to beginning of sequence if the delimiter match determination is positive.
The process used to create and access a K structure herein utilizes a procedure, which is called the praxis procedure. The praxis procedure can receive individual particles of incoming data, determine the type of particle and, based on the sensors and delimiters, access and construct the multiple levels of an interlocking trees datastore.
The KEngine creates and accesses a K structure from a stream of particles. Some of the particles in the particle stream may be identified as delimiters. Delimiters can be indicators that a portion of the particle stream is a complete thought. As an example, a white space between characters in printed text indicates that one word is ending and another is beginning. The KEngine is required to recognize the delimiters and create K structure to record the represented data. Furthermore, the KEngine is designed to recognize and process particles as either delimiters or sensors. If a particle cannot be identified as either a delimiter or a sensor it can be ignored as noise.
Sensor particles are processed by the KEngine as extensions of a current sequence of events. If there is structure that has previously recorded the sequence, the K can be traversed to reposition the current K location pointer. If there is no previous structure recording the sequence, new K structure can be created to record the event.
While the KEngine is processing the particle stream some particles are recognized as ending a sequence and beginning a new sequence. For example, within the field record universe the particle stream is divided into fields and groups of fields are divided into records. A common method of identifying the end of one field and the beginning of the next is to insert a particle, such as a comma, into the stream to indicate the limits of the field and a different character, such as a semi-colon, to indicate the limits of a record.
When the KEngine recognizes a comma particle, an EOT node can be appended to the current K path being created at a first level above the sensors, thereby completing a field entry. A new path beginning with the BOT node can then be established as the current K path for a further field entry. Particle processing then continues.
When the KEngine recognizes a semicolon particle, an EOT node can be appended to the current K path being created at the level above the field variable level. This can complete a record entry. A new K path beginning with the BOT node can be established as the current path for a record entry. In addition, the K path at the field variable below the record level can be completed and particle processing continues.



BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS
The invention will be described in conjunction with the following drawings in which like reference numerals designate like elements and wherein:
FIG. 1 shows a block diagram representation of the main components which can be used with the present invention.
FIG. 2A is a graphical representation of an interlocking trees datastore showing a structure representing the words CATS ARE FURRY.
FIG. 2B is a graphical representation of a portion of the interlocking trees datastore of FIG. 2A showing a structure representing the word CATS.
FIG. 2C is a graphical representation of a portion of the interlocking trees datastore of FIG. 2A showing a structure representing the word CATS.
FIG. 3 is a flowchart representation of a praxis procedure, which is a process that can match incoming particles of data with lists of delimiters, sensory data, and unidentified particles.
FIG. 4 is a flowchart representation of a procedure for building and accessing a K structure from individual incoming particles of sensed data.
FIG. 5A is a flowchart representation of a procedure for processing a delimiter.
FIG. 5B is a flowchart representation of a procedure for processing a delimiter indicating a complete level of a K structure.
FIG. 5C is a flowchart representation of a procedure for processing a delimiter and creating and accessing upper level subcomponent nodes.
FIG. 6A is a diagram of an exemplary particle stream in a field/record universe of textual data containing a record with three fields and exemplary delimiters that separate each.
FIG. 6B shows a generalized particlized stream using pixels as the individual data particles and exemplary delimiters that separate each.
FIG. 7 is an exemplary node within K containing a count as an additional field.
FIG. 8 is a table of records for sales activities from a fictional organization useful for heuristic purposes.
FIG. 9A is a possible KStore node diagram based on the sales records in FIG. 8.
FIG. 9B is a possible KStore node diagram depicting the deletion of a sequence from the KStore of FIG. 9 when some of the counters are decremented to 0 and are maintained within the structure to provide a history.



DETAILED DESCRIPTION OF THE INVENTION
Referring now to FIG. 1, there is shown a block diagram representation 100 of a KStore environment in which the system and method of the present invention can be implemented. Within such a KStore environment, information can flow bi-directionally between the KStore 14 and the remainder of the system through the K Engine 11. The transmission of information to the K Engine 11 may be by way of a learn engine 6 and the data source 8. The transmission of information may be by way of an API utility 5 and the application 7 as also understood by those skilled in the art. Providing graphical user interfaces 13, 12 to data source 8 and the application 7 can thus permit an interactive user to communicate with the system.
The KEngine
The K Engine 11 receives a particle from somewhere outside the K engine 11 and creates or accesses the K structure 14. The K structure 14 contains elemental nodes that represent recognized particles of data. FIG. 2A is a graphical representation of an interlocking trees datastore having the K structure for representing CATS ARE FURRY. The graphical representation of FIG. 2A is used throughout this patent as an exemplary K structure for illustrative purposes.
Also represented within the K structure are the relationships that exist between the nodes. Each node in the K structure that is constructed can be assigned an address in memory. Additionally, each node can contain two pointers, a Case pointer and a Result pointer. The case pointer and the Result pointer of a node point to the two nodes from which it is formed. Also contained in a K node may be pointers to two pointer arrays, the asCase and the asResult array. The asCase array can contain pointers to the nodes whose Case pointers point to the K node. The asResult array, which contains pointers to the nodes whose Result pointers point to the K node. How the individual K nodes within a structure are constructed and accessed is the subject of numerous references by Mazzagatti, including U.S. Pat. No. 6,961,733.
Data Particles
As mentioned above, data passed from the learn engine 6, the utilities 4 or the API utilities 5 to the K Engine 11 are particlized. For example, each word in a sentence may be treated as an individual particle of data, or each letter in a word can be treated as an individual particle of data. For example, in a textual data stream containing the words CATS ARE FURRY, the individual word CATS can be a particle, which can be sensed by a word particle sensor. Additionally, the word ARE and the word FURRY are particles which can be sensed by word particle sensors.
Each character or letter in a word, such as CAT, can be considered to be a particle which can be sensed by a sensor, in this case a character particle sensor (i.e., C is a particle of CAT as is A and T). Each of these may be a particle of data in a field/record textual universe of data. By textual it is meant that data are made up of alphanumeric characters (e.g. the letters A through Z), special characters (e.g. punctuation) and numeric data (e.g. numbers). The term field/record is a carry over from traditional database terminology, wherein a field represents the title of a column in a table and a record represents the rows within the table and contains the actual data.
However, textual data is not the only type of data that can be streamed by the learn engine 6, utility 4 or API utility 5 into the K Engine 11. Those skilled in the art will understand that any kind of data that can be digitized can be particlized and streamed into K. For example, if the data universe is image data, the particles that can be digitized can be pixels. If the data universe is auditory data, the particles can be digitized sound waves. If the data universe is pressure data, particles can be digitized pressure values. If the data universe is olfactory data, particles can be digitized chemical molecules representing odors.
In many of the explanations that follow, the examples use data from the field/record universe. This means that in the examples, it is assumed that the data which is learned or accessed within K can come from traditional tabular databases or other traditional data structures in the form of text, numbers and special characters arranged in fields within records. But, it should be remembered that any type of data from any source that can be digitized can be learned and accessed within a K and therefore could have been used in the examples that follow. Also, the K structure can contain more than two levels of structure. As well, in the following, a KStore node diagram, as shown in FIG. 2A, is used to illustrate an interlocking trees datastore depicting the creation of the words +CATS, +ARE and +FURRY and the sentence CATS ARE FURRY.
Generating an Interlocking Trees Datastore (K) from Particlized Data
As taught in U.S. Pat. No. 6,961,733 and illustrated in FIG. 1 herein, an exemplary system 100 for generating the interlocking trees datastore 14 in one embodiment can include the K Engine 11. The K Engine 11 can receive particles of data from a data stream from the learn engine 6, from the API utility 5 or from any other utility 4. The K Engine 11 is designed to recognize and process particles of data that it receives. Note that some of the particles can be created and used strictly within the K Engine 11. For example, BOT, end of list (EOL), end of record (EOR) or end of identity (EOI) can be elemental nodes. In the current embodiment there are three types of particles that the K Engine can recognize: sensors, delimiters, and unidentified particles.
Praxis Procedure
A procedure that can recognize particles of sensor data, delimiters or unidentified particles according to the system and method of the invention can be the praxis procedure. FIG. 3 shows a flowchart representation of a portion of the praxis procedure 300 which can be used for recognizing input particles in the system of the present invention. In the current embodiment, there can be three procedures corresponding to the three types of particles that may be received as input during the praxis procedure 300: (1) a procedure for processing a delimiter 301, (2) a procedure for processing unidentified particles (ignore sensor) 302 and (3) a procedure for processing sensor data 303. The following teaches the praxis procedure 300 in a preferred embodiment with special emphasis on how delimiters are processed and used to build and access an interlocking trees datastore consisting of multiple levels of K structure and how K location pointers or state are utilized.
Sensor Data, Delimiters, and Unidentified Particles
Before teaching in detail how sensor data, delimiters and unidentified particles are processed, it is necessary to explain what each of the three types of particles includes.
Sensor Data
A sensor can be any digitized data. A sensor is maintained within the K structure as an elemental root node. The elemental root nodes representing sensors may contain or point to values that match the digitized value of the sensor. In a field/record data universe, sensor data may include, but is not limited to, alphanumeric characters. The alphanumeric characters can include the letters in the alphabet, numbers and special characters such as punctuation and other special characters. Depending on how a system is configured a particle of sensor data may include only single letters, numbers, or characters, or they may be whole words, phrases, sentences, paragraphs, chapters, or even entire books, etc. Furthermore, particles may include pixel values forming images of single letters or images of any other type. Thus, as mentioned above, data particles are not limited to textual data and may consist of any other forms of digitized data (e.g. pixels forming other images, sound waves, etc.).
Delimiters
Delimiters are particles that are used to identify an ending of a set of sensors. Furthermore, delimiters may be used to group sensor sets into hierarchies. For instance in a field/record universe, sets of letters may be grouped into words by delimiters. The words can then be grouped into field names or field values by delimiters. The field names or field values can be further grouped into fields and then into records.
Delimiters may be equivalent to individual sensors or sets of sensors. Or they may contain different values altogether. In the current embodiment, delimiters may include alphanumeric characters such as the letters of the alphabet, special characters such as, but not limited to, commas (,), semicolons (;), periods (.), and blanks ( ). Numbers in any base systems may also be used as delimiters. For example, in the current embodiment hexadecimal (base 16) numbers may be used as delimiters. However, as mentioned above, because particles are not limited to characters in the textual field/record universe, delimiters may also be any different type of digitized particle. For example, in a universe of digitized pixels, a single pixel or group of pixels may be used as a delimiter.
Unidentified Particles
Unidentified particles are any particles other than the ones that a current set of particle sensors and delimiter sensors recognizes. Unidentified particles, often called noise, may be, for example, particles of data from a different data character set (e.g. an Arabic or Chinese character). They may be particles from a different data universe, or they may just be an unprintable character that is not in the current set of sensors or delimiters.
Determining Particle Types
Refer back to FIG. 3. As taught above, the praxis procedure 300 can determine the particle type of an incoming particle received by a K Engine within a K system such as the K system 100. Based on the type of particle determined, the praxis procedure 300 can initiate one of three processes to process delimiters, sensor data or unidentified particles.
Comparing Particles to Delimiter List
In the praxis procedure 300 a particle of incoming data can be compared to a currently defined list of delimiters as shown in block 304. If the input particle matches an entry in the currently defined list of delimiters a process delimiter procedure is performed as shown in block 301. A process delimiter procedure that can be performed when a particle is determined to be a delimiter according to block 301 is taught below as the process delimiter procedure 500 in FIG. 5A.
Comparing Particles to Sensor List
If the input particle does not match any of the current delimiters as determined according to the comparison of block 304 the praxis procedure 300 can continue to block 305. At block 305 the praxis procedure 300 can compare the incoming particle to a currently defined list of sensors.
The example in the following discussion uses the letter C as an exemplary particle of data from a textual field/record universe. Assume that in the example the letter C does not match any delimiter in the current set of delimiters and execution of the praxis procedure 300 proceeds to block 305. The praxis procedure 300 can then attempt to match the particle C with a list of current sensors in block 305. As taught in the above mentioned patents, in the current embodiment sensors can be maintained in the K structure as elemental root nodes. Lists of these elemental root nodes can be stored in arrays, hash tables, within the K 14 or a separate K structure or in any other manner understood in those skilled in the art.
For example, refer back to the exemplary structure shown in FIG. 2A, which is a graphical representation of an exemplary interlocking trees datastore. The exemplary interlocking trees datastore includes structure representing the exemplary record CATS ARE FURRY. In this example, a particle C is found, for example, in a sensor array (not shown). Since there is a match, the praxis procedure 300 saves the location of the elemental root node for the C particle to a variable to be used later. In this example, the location which is saved is location 225, as shown in FIG. 2A.
It should be mentioned here that if the particle does not match anything in the sensor list, the ignore sensor process can be performed as shown in block 302 of FIG. 3. The ignore sensor process may choose to discard any particle that is not recognized as a current sensor or delimiter, thereby treating it as noise. One skilled in the art will recognize that these discarded particles may be handled in numerous ways including notifying users via error or log files where other processes may be performed or users may review the contents. Additionally, an error condition may be detected in a particle sequence being received by a KStore. In one embodiment of the invention a procedure may be initiated to set the current K pointers to BOT. Under these circumstances the KStore can, for example, await a valid sequence. In a preferred embodiment of the invention the receipt of a null character can be used to indicate that the current K nodes should be reset. If the incoming particle matches something on the sensor list, the procedure of process sensor data block 303 is initiated.
Processing Sensor Data
Refer to FIG. 4, which is a flowchart representation of a process sensor data procedure 400 according to the present invention. The process sensor data procedure 400 is suitable for processing sensor data to build or access a K structure according to an incoming particle of sensory data. Initiation of the process sensor data procedure 400 can occur pursuant to execution of the process sensor data block 303 within the praxis procedure 300, when an input particle does not match any entries in the current set of delimiters but does match an entry in the current set of sensors.
As shown in block 401 of the process sensor data procedure 400, the current K node on the current level of the K structure is determined, wherein terms such as “current K node,” “current K location” and “current K pointer” are understood to refer to the location of the last experience on a selected level. When block 401 is executed the incoming particle has just been matched with the root node corresponding to the incoming particle according to block 305 of the praxis procedure 300. Therefore, the current level is known to be the level above the elemental root nodes. Accordingly, the current K node of the level above the root nodes is determined in block 401.
In a preferred embodiment of the invention, a list or any other kind of structure, can be maintained to store state variables indicating the current K location corresponding to each level. For example, in the case of a multilevel K structure an array setting forth the correspondence between each level of the K structure and a variable indicating the current node of the level can be provided. The current K locations, or the current K node state data, of the levels of the K are known and stored according to the last event experienced on each level. The array or other data structure storing the current K node state data can be referred to as a state array or state table.
In one preferred embodiment each K location pointer can be used to identify both the current K level and the position on the current K level where the last event was experienced. Additionally, the foregoing structure for storing the correspondence between each level of the K structure and its current K node location pointer can store a list of the current set of delimiters, wherein the delimiters are described above with respect to block 304 of the praxis procedure 300 and in further detail below. However, the delimiter level data can be stored in any manner known to those skilled in the art. The structure may also contain a set of sensors appropriate for that particular level. The array of other data structure storing the current K state can be referred to as the state array or state table.
Furthermore, a correspondence between the defined delimiters and the levels of the K structure can be stored. Storage of this information permits the system to determine a relationship between an input delimiter and a level of the Kstructure that is being ended by the delimiter. It will be understood that the current K node state data and the delimiter level information do not need to be stored in the same data structure. It will also be understood that multiple delimiters may be appropriate for a single level.
As shown in block 402, the process sensor data procedure 400 can then determine the adjacent nodes of the current K node that was determined in block 401. As well known to those skilled in the art, the adjacent nodes of the current K node are determined by accessing an asCase list pointed to by an asCase pointer of the current K node. The asCase list contains pointers to each of the asCase nodes to be located in block 402. It will be understood by those skilled in the art that the asCase nodes located in this manner contain pointers to their Result nodes.
As shown in block 403, the Result nodes of the asCase nodes found in block 402 are determined according to their Result pointers. As shown in block 404, the Result nodes located in block 403 are then compared with the root node representing the received particle. If a match is found in decision 405 between a Result node of an asCase node found in block 402 and an elemental root node representing an input particle, the matched asCase node becomes the current K node. Therefore, the first level K pointer is advanced to point to the matched asCase node as shown in block 407.
For example, assume that the current K node determined in block 401 is the beginning of thought (BOT) node 200 in FIG. 2A. As described in block 402, the process sensor data procedure 400 determines the asCase nodes of the BOT node 200. In order to do this the asCase list of the BOT node 200 is examined. The nodes in the asCase list of the BOT node 200 are the nodes 205, 210, 215 and 220. It will thus be understood by those skilled in the art that each asCase node 205, 210, 215 and 220 includes a Case pointer pointing to the BOT node 200.
It will also be understood that each asCase node 205, 210, 215 and 220 includes a Result pointer pointing to its Result node. Thus, in block 403 the process sensor data procedure 400 can determine the Result node of each node 205, 210, 215 and 220 on the asCase list of the current K node by following its respective Result pointer to its respective root node. The Result nodes determined in this manner in block 403 can be compared with the elemental root node of the sensor corresponding to the received particle as shown in block 404. A determination can thus be made whether the Result node of any of the nodes 205, 210, 215 and 220 on the asCase list of the current K node match the elemental root node for the sensor of an input particle in block 404 of the process sensor procedure 400. The determination whether there is a match with the elemental root node for the sensor of the input particle can be made in decision 405.
Further to the foregoing example, the input particle in FIG. 2A can be the letter particle C and the root node 225 can correspond to the value C of the input particle. If the Result nodes of the asCase nodes 210, 215, and 220 are compared in block 404 with the root node 225 no matches are found in decision 405 because none of the asCase nodes 210, 215 and 220 has a Result pointer pointing to the C elemental root node 225.
However, the asCase node 205 does contain a Result pointer pointing to the C elemental root node 225. Decision 405 of the process sensor data procedure 400 can therefore find that the Result node of the subcomponent node 205 is a match with the input particle. The current K location pointer can be set to the node +C 205, which has become the current K location of the level as shown in block 407. (For exemplary purposes in the diagrams, when the prefix notation “+” is placed before a value in a node in the figure, it indicates that the prefixed node has a valence, which will be understood to stand in for the entire thought up to but not including the prefixed node.) It will be understood that the asCase nodes of the current K node can be compared in any order and that once a match is found no more comparisons are needed.
In a different example, the current K location could be the subcomponent node 205 and the input particle could be the letter particle A. Pursuant to block 402 the asCase node of the node 205 is determined to be the subcomponent node 206. Since the Result node of the node 206 is the elemental root node representing the letter particle A, a match is found in decision 405. Thus, in block 407 the current K node is incremented to the subcomponent node 206.
Creating New Nodes
In some cases it may turn out that none of the nodes on the asCase list determined in block 402 has a Result pointer pointing to the root node of the input particle. Under these circumstances a match is not found in decision 405. Thus, it may be necessary to create new K structure as shown at block 408. The process of creating a new node is disclosed in several of the references incorporate herein, such as U.S. Pat. No. 6,961,733 and U.S. Pat. Ser. No. 11/185,620, entitled “Method for Processing New Sequences Being Recorded Into an Interlocking Trees Datastore” for detailed explanation of how new nodes are created. Regardless of whether execution of the process sensor data procedure 400 proceeds by way of block 407 or by way of block 408 the intensity count can be incremented as shown in block 409.
Processing Delimiters
Refer back to FIG. 3, showing the praxis procedure 300. As described in the foregoing description of the process sensor data procedure 400 of FIG. 4, when a sensor is detected by the praxis procedure 300, execution of the praxis procedure 300 can proceed by way of block 303 to process the detected sensor in the process sensor data procedure 400. However, the praxis procedure 300 may detect a delimiter particle rather than a sensor particle in an input particle stream. Under these circumstances the system and method of the invention can execute procedures suitable for processing the received delimiter.
As previously described, after comparing an input particle of data to the current list of delimiters in block 304 of the praxis procedure 300 a decision is made in decision 308 whether there is a match. If the input particle is found to match a currently defined delimiter in decision 308 the procedure of block 301 is initiated in order process the received delimiter. The procedure initiated by block 301 is the process delimiter procedure 500 of FIG. 5A. Before teaching the process delimiter procedure 500 in detail, it is important to understand what delimiters are used for in the preferred embodiment of the invention.
In the preferred embodiment of the invention delimiters are used to indicate the end of a set of particle sequences of data as they are streamed into the K Engine 11. For example, as mentioned above, in the field/record universe, data may come from traditional databases in the format of fields and records.
Refer to FIG. 6A showing a diagram of an exemplary particle stream 600. The exemplary particle stream 600 can represent a data record that can be stored in the K structure 14 and can therefore be referred to as the exemplary record 600. The exemplary particle stream 600 can represent three fields: Last Name 601, First Name 602, and Telephone Number 603. However, any number of fields of any size can be represented in other field/record universe particle streams, of which the exemplary particle stream 600 is but one example.
The first field in the exemplary particle stream 600 is the Last Name field 601 and is shown with the data sequence Cummings. The second field is the First Name field 602 and is shown with the data sequence William. The third field is the Telephone Number field 603 and is shown with the data sequence 7547860. At the end of the fields 601, 602 there is shown an end of field (EOF) delimiter 1D 604.
The hexadecimal character 1D 604 is thus used as an end of field delimiter for ending the first two fields 601, 602. However, the hexadecimal character 1E 605 is used as both an end of field delimiter for ending the last field 603, and an end of record delimiter for ending the exemplary record 600. As such, it is a single delimiter that ends both the field 603 and exemplary particle stream 600, and, in general, in particle streams such as the exemplary particle stream 600 a delimiter is not required for dosing each level of the KStore.
Thus, significantly, the hexadecimal character 1E 605 may be used to simultaneously end both: (i) its own level in the K structure (the record level), and (ii) a lower level of the K structure (the field level). Accordingly, in the embodiment of the invention represented by the exemplary particle stream 600, each level of a particle stream is not required to have its own separate dosing delimiter. Furthermore, a higher level delimiter such as the delimiter 1E can complete any number of incomplete thoughts, and thereby close any number of lower levels, in the manner that the field level of the exemplary particle stream 600 is dosed.
Since textual data is not the only data that can be particlized and streamed into the K Engine 11, a more generalized explanation of delimiters may be helpful. In general, particles coming into the K Engine 11 may be thought of as incomplete thoughts which can operate cooperatively to form complete thoughts. Each incomplete thought can represent an individual particle, set of particles of data, or the absence of particles. Individual incomplete thoughts may be streamed into the K Engine 11 to form complete thoughts. This is analogous to individual fields (incomplete thoughts) such as the fields 601, 602, 603 forming a complete record (complete thought) such as the complete record 600.
FIG. 6B shows a more generalized stream of particles with incomplete thoughts 606 making up a complete thought 610. In FIG. 6B each incomplete thought 606 is shown as groups of pixels. However, incomplete thoughts 606 could easily have been shown with textual data or data from any other data universe. In the complete thought 610 the EOT delimiter 607 is shown as the hexadecimal character 1D and the final end of product delimiter 608 is shown as the hexadecimal character 1E. This relationship is shown in FIG. 2A at the nodes 265, 282.
Although the hexadecimal characters 1D and 1E are used as delimiters 607, 608 in the illustrative examples, it will be understood that any other particle may be defined to serve as delimiters 607, 608. For example, a comma, another numerical character including characters that are not hexadecimal characters or a specific group of pixels. Thus, delimiters may be any particle that is defined as such for the praxis procedure 300 when the processing of the delimiter particles begins.
It should be noted that incomplete thoughts are not limited to single particles of data. An incomplete thought may be any sequence of data that is experienced before an EOT delimiter is experienced. An incomplete thought may also include the absence of particles indicating a null value, terminated by an EOT delimiter.
Again referring back to the praxis procedure 300 in FIG. 3, an incoming particle can be compared to a list of currently defined delimiters as shown in block 304. If the input particle matches one of the currently defined delimiters as determined in decision 308, the procedure of process delimiter block 301 can be initiated to process the received delimiter particle. The procedure for processing the received delimiter particle according to process delimiter block 301 is the process delimiter procedure 500 of FIG. 5A.
Refer now to FIG. 5A, which is a flowchart representation of the process delimiter procedure 500 for processing delimiters found in an input particle stream. The process delimiter procedure 500 can be initiated by the process delimiter block 301 of the praxis procedure 300 when a match is found between an input particle and an entry on the list of currently defined delimiters by decision 308.
As previously described, it is possible for the praxis procedure 300 to receive a higher level delimiter for completing its own level of the K structure while lower levels of K structure are still incomplete. Under these circumstances, the higher level delimiter can complete as many incomplete lower levels as necessary prior to completing its own level.
For example, refer above to the exemplary particle stream 600 shown in FIG. 6A. An EOF delimiter hexadecimal 1D 604 is shown at the ends of the fields 601, 602. The hexadecimal delimiter character 1D 604 is thus used as the delimiter for the first two fields 601,602. However, there is no delimiter character 1D 604 at the end of the field 603. Rather, only the hexadecimal delimiter character 1E 605 is shown at the end of the field 603, wherein it is understood that the level of the delimiter character 1E 605 is higher than the level of the field 603. Therefore, the received delimiter character 1E 605 is used to indicate both the end of the last field 603, and the end of the exemplary particle stream 600. Under these circumstances, the received delimiter character 605 performs both the operation of completing the incomplete thought 603, at a lower level, and the operation of ending the record 600, at a higher level.
Thus, at the time the delimiter character 605 is received: (i) the field 603 represents an incomplete thought on an incomplete lower level, and (ii) the delimiter character 605 is a delimiter for a higher level of K structure than the current level of field 603. Accordingly, the system and method of the present invention can determine both: (i) that the level of the field 603 must be completed, and (ii) that the level of the record 600 must be completed. Additionally, the system and method of the present invention can perform the operations necessary for completing both the field 603 and the record 600.
Furthermore, those skilled in the art will understand that a received delimiter can indicate the end of any number of lower levels in the manner that the delimiter character 605 indicates the end of only a single lower level. Accordingly, the system and method of the invention can perform the operations necessary for completing as many lower levels as required in addition to completing the level of the received delimiter.
Therefore, the process delimiter procedure 500 of FIG. 5A is provided to perform the operations of completing as many incomplete levels as necessary below the level of a received delimiter, as well as completing the level of the received delimiter itself. In block 501 of the process delimiter procedure 500 the level associated with the input delimiter is determined. This determination can be made according to a list of currently defined delimiters and the K location structure or state structure setting forth the corresponding delimiter level as previously described. Additionally, the variable Input Delimiter Level is set equal to the determined level in block 501.
As previously described in the current embodiment, sets of particle sequences, such as the sets of sequences forming the incomplete thoughts 606 in FIG. 6A, can be entered into the K structure 14 in levels. Thus, in effect, hierarchy is determined by the organization or location of the delimiters. For example, any number of levels may appear in a K structure and multiple types of end product nodes may be present in any one level. Refer back to FIG. 2A. The interlocking trees datastore shown in FIG. 2A includes three exemplary levels: 0, 1 and 2. An individual K structure is not limited to three levels and may contain as many as necessary. Note that the level numbers indicated in these descriptions are used for the sake of clarity of the discussion. Levels may be linked by any means desired with the concept of an “upper” level being relative to whatever linked structure is utilized. The structure used to link the levels, as discussed previously for the K location pointers or state structure, may be an array, a linked list, a K structure or any other structure known to those skilled in the art.
Level 0 (230) of the K shown in FIG. 2A can represent the elemental root nodes. For example, using field/record textual universe data of FIG. 2A, level 0 can represent the elemental root nodes 200, 225, 271, 265, or 282 as well as the other elemental root nodes that have not been provided with reference numerals in FIG. 2A.
Level 1 (235) can represent the subcomponent nodes and end product nodes of the paths 240, 245 and 250. The Result pointers of the nodes in level 1 point to the elemental root nodes in level 0.
For example, the path 240 includes the nodes 200, 205, 206, 207, 208 and 260. Assume that a delimiter for end of field, such as the delimiter 1D 265 similar to the delimiter 1D 604 in FIG. 6A, is recognized while the K location pointer for level 1 is positioned at the exemplary node 208. The nodes of the path 240 from the BOT node 200 to the node 208 thus represent an incomplete thought for the exemplary sequence BOT-C-A-T-S. The delimiter 1D 265 recognized at this point indicates the termination of the field sequence from the BOT node 200 to the node 208. Thus, an end product node 260 can be built. The addition of the end product node 260, having the EOT delimiter 1D 265 as its Result node, completes the incomplete thought, and the exemplary word CATS is thus represented by the path 240. It is the recognition of a delimiter 1D in this manner, after experiencing an incomplete thought, that completes the thought.
Level 2 (255) represents the subcomponent nodes whose Result pointers point to the complete thoughts of level 1 in FIG. 2A. The complete thoughts of level 1 are represented by the end product nodes +CATS 260, +ARE 270 and +FURRY 275. The addition of the end product node 283, having the EOT delimiter 1E 282 as its Result node, can be used to complete the incomplete thought, thus completing the record CATS ARE FURRY.
Referring back to FIG. 5A. As explained above, in block 501 of the process delimiter procedure 500 an incoming delimiter is associated with its defined level within the interlocking trees datastore and the variable Input Delimiter Level is set equal to the associated level. For example, within a field/record universe the exemplary hexadecimal character 1D 607 in FIG. 6A may be used to represent the end of a field 606 (i.e. the end of a complete field thought) as previously described. As also described, the exemplary hexadecimal character 1E may be used to represent the end of a record (i.e. the end of a complete record thought). Both of the delimiters 1D, 1E in the current embodiment may initiate processing that indicates completion of a specific level within the K structure. Thus, the level is identified with which the experienced delimiter is associated.
The process delimiter procedure 500 can next determine which, if any, levels lower than Input Delimiter Level are incomplete at the time the input delimiter is received. This determination can be made with reference to the list of the current K nodes in the K structure. As previously described, this list can contain the current K pointers for each level of the K structure. In one embodiment the K location pointer for each level can indicate the node in that level where the last event for that level was experienced, and the K location pointer for completed levels can point to any location designated as a thought beginning location. In one preferred embodiment the thought beginning location can be the BOT node 200. The process for ending the incomplete thoughts located in this manner can begin with the lowest such level as shown in block 502. Execution of the process delimiter procedure 500 can then proceed to block 503 where the process complete level procedure 550 of FIG. 5B is initiated in order to begin ending incomplete thoughts as necessary.
For example, in FIG. 2A, assume that a previous particle S 271 in the sequence BOT-C-A-T-S was the last particle sensed in level 1 (235). The sensing of the particle S 271 can permit the forming of the incomplete thought at the node 208, as previously described. At this point, the K location pointer for level 1 points to the node 208, thereby indicating that the last event experienced on level 1 (235) was at the node 208. Thus, level 1 is incomplete at this point. Therefore, level 1 is the starting level determined in block 502 of the process delimiter procedure 500 when a delimiter 1D is received. The incomplete thought +S 208 can be completed by the process complete level block 503 which initiates the process complete level procedure 550 of FIG. 5B.
Refer to FIG. 5B, which shows the process complete level procedure 550. In a preferred embodiment of the invention, the process complete level procedure 550 is initiated by the execution of block 503 of the process delimiter procedure 500 when an incomplete level is determined. The process complete level procedure 550 is adapted to complete the processing of the incomplete levels determined in block 502. The presence of unfinished lower level can be determined with reference to the table of current K node pointers of each level as previously described. The lower levels are dosed starting from the lowest incomplete level and proceeding upward through the determined level.
In block 504 of FIG. 5B, the Result nodes of the asCase nodes of the current K node are compared with the determined delimiter. The process of block 504 is substantially similar to the operations of blocks 401-404 of the process sensor data procedure 400 described above. In decision 505 a decision is made whether any of the asCase nodes of the current K location for the determined current K level have a Result node that matches the root node for the determined delimiter. If no matches are found in decision 505 an end product node has not been built and processing continues to block 506. In block 506 a new end product node can be created in order to complete the incomplete thought of the determined current K level and the current K location pointer is set to the new node.
Refer to FIG. 2B, which illustrates a K structure in the process of being built. In this exemplary figure, assume again that the node 208 is the last node formed and that the input particle received matched the level 1 delimiter 1D. Therefore, the K location pointer for level 1 points to the node 208. As explained above, the asCase list of the current K node 208 is checked. It is determined by decision 505 that there are no nodes in the asCase list of node 208. Therefore, processing of the process complete level procedure 550 proceeds to block 506 where the end product node 260 is created. The end product node 260 created in this manner links the node 208 to the elemental root node 265 for the field delimiter 1D for the current level which in this case is level 1. The K location pointer for level 1 is then set to the node 260 where it indicates that the level is complete. In this exemplary figure, the end product node 260 is in level 1.
In a further example of the case in which execution of the process complete level procedure 550 proceeds from decision 505 and builds a new node, assume that the current K pointer is pointing to the subcomponent node 274 of FIG. 2A when the delimiter 1D is received. If the +EOT node 275 has not previously been built the decision 505 of the process complete level procedure 550 will not find any asCase nodes. Under these circumstances processing can proceed to block 506 where the end product node 275 can be created, as described in the foregoing example.
However, when an end product asCase node of a current K node has already been experienced and built, execution of the process complete level procedure 550 can proceed from decision 505 to block 507. For example, if the field represented by the path 250 has previously been experienced by the K structure at least once, the asCase list of the node 274 is not empty. Thus, a comparison between the Result node of the asCase node 275 and the elemental root node for the delimiter can be positive. In the current example, such a match is found because the asCase node (the node 275) of the current K node (274) does, in fact, have a Result pointer pointing to the 1D delimiter sensor 265.
Thus, in this example, execution of the process complete level procedure 550 can proceed to block 507. In block 507 the previously existing node 275 can become the current K node and the count of the nodes can be incremented.
Whether execution of the process complete level procedure 550 proceeds by way of block 506 to create a new node and advance the current K pointer, or by way of block 507 to merely advance the current K pointer to a preexisting node, the count of the node is incremented and a determination is made whether there are potentially any higher levels above the current level as shown in decision 508. The determination whether there are higher levels is made by accessing the list of defined delimiters as previously described and determining where the determined delimiter is located in the defined hierarchy.
If there are no levels higher than the current K level, the K location pointer is set to the BOT node 200 to indicate that the current K level is complete as shown in block 509. The system can then wait for the next input particle. Processing by the process complete level procedure 550 is then complete. Processing can then return to the process delimiter procedure 500 in FIG. 5A and proceed from block 503 to block 511. If there is a higher level in the K structure, as determined in block 508, processing continues to the process upper level subcomponent block 510 where a subcomponent node can be built if necessary. The processing performed by the process upper level subcomponent block 510 initiates the process upper level subcomponent procedure 590 shown in FIG. 5C.
Refer to FIG. 5C, which is a flowchart representation of the process upper level subcomponent procedure 590. The process upper level subcomponent procedure 590 is initiated by process upper level subcomponent node block 510 of the process complete level procedure 500.
The upper level subcomponent procedure 590 can begin with blocks 514a-d. The operations of blocks 514a-d of the process upper level subcomponent procedure 590 are substantially similar to the operations of blocks 401-404 of the process sensor data procedure 400 described above
As shown in block 514a, the current K node on the upper level can be determined. For example, referring back to FIG. 2B, the current K node on the upper level (255) can be the BOT node 200. As shown in block 514b, the asCase list of the BOT node 200 can be used to locate the asCase nodes of the BOT node 200. The node 205 is thus located. As shown in block 514c, the Result pointers of the asCase nodes of the BOT node 200 are followed to find any Result nodes. The elemental root node 225 is thus located. As shown in block 514d, the Result node located in this manner is compared with the end product node for the previous level node 260.
In decision 515 a decision is made whether any of the asCase nodes of the current K location for the current level have a Result node that matches the root node or end product node for the previous level. If there is a match the upper level K location pointer is set to the matched node as shown in block 516. However, if the end product node has not been experienced before at this level then no matches are found by decision 515 and processing continues to block 517. In block 517 a new subcomponent node can be created in the higher level and the current K location pointer for the higher level can be set to the new node.
For example, refer to FIG. 2C, which is a graphical representation of a portion of an interlocking trees datastore, for example, a portion of the interlocking trees datastore that was originally shown in FIG. 2A. The datastore in FIG. 2C was previously begun in FIG. 2B, as previously described. However, the datastore of FIG. 2C has an additional node, not present in the datastore of FIG. 2B, the level 2 subcomponent node 220 representing the sequence BOT-CATS. The Result node of the node 220 is the +EOT node 260 of level 1. The +EOT node 260 is the end product node of the path 240 representing BOT-C-A-T-S-EOT.
Further to FIG. 2B, the current K location for the upper level or level 2 (255), is the BOT node 200. At this point the asCase list of the BOT node 200 is checked and found to contain only one node, the node 205. The Result pointer for the node 205 is then checked and found to point to the elemental root node 225. The elemental root node 255 represents the particle C.
The elemental root node 205 thus does not match the end product node pointed to by the K location pointer for level 1, the +EOT node 260. Now refer to FIG. 2C. In FIG. 2C, a new subcomponent node may be created at the upper level (255), which in this exemplary case is the BOT-CATS node 220. The subcomponent node 220 is then set as the current K location node for the upper level. Processing then returns to FIG. 5B and proceeds from block 510 to block 509 where the current K location pointer for level 1 (235) is set to the node BOT 200. After completion of block 509 the K location pointer for level 1 points to the BOT node 200 and the K location pointer of level 2 points to the node 220. Processing can then continue to block 511 of FIG. 5A by way of calling block 503. Processing Upper Levels
The foregoing descriptions disclose how delimiters can signal the end of complete thoughts at lower levels (e.g. field levels in a field/record data universe). The following discussion discloses how delimiters are used to signal the end of complete thoughts at upper levels (e.g. record levels in a field/record data universe). In this part of the explanation, assume that portions of an upper level have already been established.
It will be understood that to some extent the procedures for completing upper levels are similar to those for completing the lower levels as they were previously described. Therefore, where the following procedures are similar to those that have previously been taught above, the explanation may refer back to the earlier explanations. Also, the following discussion is taught using the exemplary delimiters from the field/record universe. And, before continuing, some assumptions can be made before explaining in detail how the upper level delimiters are processed.
Process Upper Level when Lower Levels are Complete
Assume in the following discussion that a K structure such as K 14 shown in FIG. 2A continues to be built. Also assume that the lower level delimiters (e.g. the 1D delimiter in the exemplary case) are experienced at the end of incomplete thoughts, thereby completing the incomplete thoughts. Also assume that eventually an upper level delimiter, e.g. 1E in a field/record universe, is experienced. Again, it should be noted that particles from a field/record universe are not the only particles that the K Engine 11 can process. Additionally, the delimiters used in the following examples (hexadecimal characters 1D and 1E) are not the only delimiters that may be used within the KStore system. Furthermore, those skilled in the art will realize that the praxis procedure 300 of the invention is not limited to field/record data, and that any data that can be digitized (e.g. pixels) may be represented as a K structure through the praxis procedure 300.
As mentioned above, the following discussion uses the K structure shown in FIG. 2A to explain the process of completing the upper levels of a K structure. As the following discussion begins, refer to FIG. 2A and assume the following about each level.

    
    
        Level 0 (230)—Contains all of the elemental root nodes of the K Store 14.
        Level 1 (235)—The paths 240, 245, and 250 are complete. The K location pointer for level 1 points to the BOT node 200.
        Level 2 (255)—The sequences that can be represented by the subcomponent nodes 220, 280, and 281 have been processed and the K location pointer for the level 2 points to the node 281.
    
    


As the following discussion begins, the next particle that is experienced is the delimiter 1E, wherein the delimiter 1E closes its own level (level 2) as shown in the exemplary particle string 610 of FIG. 6A.
As explained above, the praxis process 300 shown in FIG. 3 begins in block 304 by determining whether the received particle is a currently defined delimiter. Since the particle is a delimiter, execution proceeds to the process delimiter procedure 500 of FIG. 5A by way of block 301 of FIG. 3.
Refer back to the process delimiter procedure 500 in FIG. 5A, which is a flowchart representation of a procedure for processing delimiters. Since in the example the received hexadecimal character 1E is defined to represent an end of record, it is known that this delimiter is associated with level 2 (255) by accessing the delimiter level data or state structure as shown in block 501. The process shown in block 502 determines that the lowest incomplete level is level 2 (255) because the K location pointer for level 1 (235) is at BOT node 200.
Again, as explained above in detail, the process complete level procedure 550 shown in FIG. 5B is initiated by way of block 503. The procedure steps shown in blocks 504, 505 and 506 are completed and the end product node +EOT 283 is created in block 506 and set as the K location pointer for level 2. When the procedure 550 reaches block 508, a determination is made whether there are any potentially higher levels within the KStore. In the exemplary case, no other higher level delimiters are defined beyond the hexadecimal character 1E. Thus, there are no other higher levels in the K. Therefore, the K location pointer for level 2 (255) is set to the BOT node 200 as shown in FIG. 2A and block 509 of FIG. 5B.
From block 509, the process complete level procedure 550 returns to the calling block 510 in FIG. 5A and proceeds to block 511. In block 511 the level is set to the next upper level. Since there is no level higher than this one, the current level is set to a value larger than the maximum level, in this case level 3. In blocks 512 the current level is compared to the Input Delimiter Level and in block 513 of the procedure 500 determines whether the current level is greater than the level of the input delimiter. In the example, the input delimiter is at level 2. Since level 3 is greater than level 2, the question in decision block 513 is answered YES, indicating completion of the delimiter processing in the procedure 500. Execution can then return to block 303 of the praxis procedure 300 in FIG. 3. At this point the praxis procedure 300 can return to its calling procedure, block 301, where the system awaits the next incoming particle.
Process Upper Level when Lower Levels are not Complete
Assume in the following discussion that a Kstructure such as K 14 shown in FIG. 2A continues to be built. Also assume that the last lower level delimiter (e.g. the 1D delimiter in the exemplary case) has not yet been experienced at the end of the last incomplete thought. Also assume that eventually an upper level delimiter, e.g. 1E in a field/record universe, is experienced. Again, it should be noted that particles from a field/record universe are not the only particles that the K Engine 11 can process. Additionally, the delimiters used in the following examples (hexadecimal characters 1D and 1E) are not the only delimiters that may be used within the KStore system. Furthermore, those skilled in the art will realize that the praxis procedure 300 of the invention is not limited to field/record data, and that any data that can be digitized (e.g. pixels) may be represented as a K structure through the praxis procedure 300.
As mentioned above, the following discussion uses the K structure shown in FIG. 2A to explain the process of completing the upper levels of a K structure. As the following discussion begins, refer to FIG. 2A and assume the following about each level.

    
    
        Level 0 (230)—Contains all of the elemental root nodes of the KStore 14.
        Level 1 (235)—The paths 240 and 245 are complete. Within the path 250, the sequences that can be represented by the nodes 215, 216, 272, 273 and 274 have been experienced, and the K location pointer for level 1 points to the node 274.
        Level 2 (255)—The sequences that can be represented by the subcomponent nodes 220 and 280 have been processed and the K location pointer for the level 2 points to the node 280.
    
    


As the following discussion begins, the next particle that is experienced is the delimiter 1E, wherein the delimiter 1E closes both its own level (level 2) and the level below it (level 1) as shown in the exemplary particle string 600 of FIG. 6A. Thus, in general, in particle streams such as the exemplary particle stream 600 a delimiter is not required for closing each level of the KStore.
As explained above, the praxis process 300 shown in FIG. 3 begins in block 304 by determining whether the received particle is a currently defined delimiter. Since the particle is a delimiter, execution proceeds to the process delimiter procedure 500 of FIG. 5A by way of block 301 of FIG. 3.
Refer back to the process delimiter procedure 500 in FIG. 5A, which is a flowchart representation of a procedure for processing delimiters. Since in the example the received hexadecimal character 1E is defined to represent an end of record, it is known that this delimiter is associated with level 2 (255) by accessing the delimiter level data or state structure as previously described. The process shown in block 502 determines that the lowest incomplete level is level 1 (235) because the K location pointer for level 1 (235) is not at BOT node 200. Rather, it points to the subcomponent node 274 of the K path 250 within level 1 (235) in the current example. It is also determined from the delimiter level data or state structure that the delimiter for level 1 is 1D.
As explained above, the process delimiter procedure 500 can proceed by way of block 503 to initiate the process complete level procedure 550 of FIG. 5B, in order to complete the incomplete lower level 1 (235) of the K before processing the upper level (255). The level, level 1, and the determined delimiter, 1D, are passed to the process complete level procedure. In block 504 the asCase node of the K location pointer for this level (level 1), node 274, if any, is located. If the +EOT node 275 has already been created there is a match in decision 505 between its Result node 265 and the determined delimiter, wherein it is understood that the determined delimiter 1D is the delimiter associated with level 1 (235). The current K node for level 1 is advanced to point to the +EOT node 275 in block 507 and the intensity is incremented.
If the +EOT node 275 has not already been created, there is no end product node and no match in decision 505. The process complete level procedure 550 can then proceed to block 506 where the +EOT node 275 can be created. Since the new node is to be located on level 1 (235) the Result node of the new +EOT node 275 is set to EOT 1D 265.
The procedure 550 can increment the count and proceed to decision 508 where a determination can be made whether there are any higher levels. Because there is a level above level 1 (235), namely level 2 (255), the process upper level subcomponent procedure 590 of FIG. 5C is initiated by way of block 510.
As the process upper level subcomponent procedure 590 of FIG. 5C is initiated by way of block 510 of FIG. 5B, the procedures in blocks 514a-d are performed. In these operations the asCase nodes, if any, of the current K node (the node 280) of level 2 (255) can be located. The Result nodes of any asCase nodes located can be compared to the end product node for the previous level. In the current example the asCase node 281 can be located. The Result node of the asCase node 281 is compared with the end product or root node of the previous level or node 275. Since node 275 matches the K location pointer for the previous level, the K location pointer for the upper level or level 2 is set to node 281 representing “BOT-CATS-ARE-FURRY”, as shown in FIG. 2A. If there had been no match a new subcomponent node would have been created in block 517 and the current K location for level 2 advanced to the newly created node. The process returns to FIG. 5B block 509, at which point the K location pointer for level 1 is set to BOT. The process then returns to FIG. 5A block 511.
The current level is then set to the next highest level in block 511 of the process delimiter procedure 500. In the current example the next highest level is delimiter level 2 (255). This is the record level in the field/record universe of data of the current example. As shown in block 512 of the process delimiter procedure 500 the new level is compared to the variable Input Delimiter Level of block 501. In the example, the input delimiter is 1E, which represents level 2 (235), and the current K level is also level 2 (235). In the decision block 513 a determination is made whether the current K level is greater than the variable Input Delimiter Level. Since both level numbers are 2 in the current example the answer to decision 513 is NO. The process delimiter procedure 500 can therefore proceed from the decision 513 by way of the process complete level block 503 to the process complete level procedure 550 of FIG. 5B to complete the processing for level 2 (255).
Again, as explained above in detail, the process complete level procedure 550 shown in FIG. 5B is initiated. The procedure steps shown in blocks 504, 505 and 506 are completed and the end product node +EOT 283 is set as the K location pointer for level 2. When the procedure 550 reaches block 508, a determination is made whether there are any potentially higher levels within the KStore. In the exemplary case, no other higher level delimiters are defined beyond the hexadecimal character 1E. Thus, there are no other higher levels in the K. Therefore, the K location pointer for level 2 (255) is set to the BOT node 200 as shown in FIG. 2A and block 509 of FIG. 5B.
From block 509, the process complete level procedure 550 returns to the calling block 510 in FIG. 5A and proceeds to block 511. In block 511 the level is set to the next upper level. Since there is no level higher than this one, the current level is set to a value larger than the maximum level or, in this case, level 3. In blocks 512 the current level is compared to the Input Delimiter Level and in block 513 of the procedure 500 determines whether the current level is greater than the level of the input delimiter. In the example, the input delimiter is at level 2. Since level 3 is greater than level 2, the question in decision block 513 is answered YES, indicating completion of the delimiter processing in the procedure 500. Execution can then return to block 303 of the praxis procedure 300 in FIG. 3. At this point the praxis procedure 300 can return to its calling procedure, block 309, where the system can await the next incoming particle.
Count Fields
While count fields within interlocking trees datastores have been discussed in Ser. No. 10/666,382, the following disclosure teaches some preferred methods of updating these fields. As has been previously taught, the K nodes of an interlocking trees data store may include additional fields representing any type of information associated with the nodes. This may be illustrated using FIG. 7 which shows the exemplary node 700/701. Additional fields 703 within the K nodes may be used to store a count, a node type indicator or any other information about the nodes if desired. The node 700/701 may include a count field 702 and other additional fields 703 which may have many uses. Thus, nodes such as the node 700/701 need not be limited to one additional field. Often, however, an additional field may contain a count. The count field 702 may be initialized and/or incremented with an intensity variable. The value of the intensity variable may vary with conditions within the system when the count field is being referenced.
An intensity variable may be defined as a mathematical entity holding at least one value. A simple example of an intensity variable may be a single ordinal field value, such as 1, to be used to increment or decrement count fields 702 to record the number of times that a node is accessed or traversed within a KStore. By making this term so broad an intensity variable populated count field 702 may be used for applications of the inventive interlocking trees structure dealing with learning, forgetting, erroneous recorded data, recording which entity is doing an inquiry, recording the type of inquiry being used and other processes of interest which may be occurring when using the data.
The count field 702 is added to a node 700/701 in order facilitate the use of the knowledge store represented by the interlocking trees structure and is particularly useful when statistics, such as frequency and probability, are sought.
Count Fields 702 and the Praxis Procedure 300
Refer back to FIG. 4, which shows a high level flowchart of the procedure 400, showing how sensors may be processed in accordance with the present invention. After a new node has been created as shown in block 408, or when the K location pointer has been set to a matched node as shown in block 407, counts within the referenced nodes may be increased or decreased as shown in block 409 depending on different situations. Similar updates to the count fields 702 may occur in FIGS. 5B and 5C. This process will be explained in more detail below.
Incrementing Count
Typically, the count may be incremented for learning functions and not incremented for query functions. As an example of this in a field/record universe, the count field 702 for each K node traversed may be incremented by 1 as new transaction records are recorded into the K. Newly created K nodes may be initialized to 1. An example of a case in which a count field 702 may not be incremented within a KStore is a dictionary spell checker in which a user may not be concerned about the number of times a word is misspelled.
FIG. 8 shows an exemplary set of five fictional records 800 which may be used to help illustrate the various methods of establishing or updating counts. The fictional records 800 identify sales of a period for a furniture store salesman named Bill. FIG. 9A is a node diagram 900 of a possible KStore, illustrating how the nodes might be established in a KStore in the ordinary course of processing the particlized data from FIG. 8 in the K Engine as described in the discussion on the praxis procedure 300 and in earlier patent documents referenced and incorporated herein above.
Counts are shown in FIG. 9A as the numbers within each node. Note that the value in the count field is higher in some nodes than in others since the event that the node represents has been processed more often than others. For example, in FIG. 9A the node 901 is associated with the sequence Bill-Tuesday and is shown with a count of 1. Referring back to the fictional records in FIG. 8, notice that only one record contains the particle sequence Bill-Tuesday. For this reason, the count field 702 for the node 901 is set to 1 in FIG. 9A. The node 902, which represents Bill, has a count of 5 since all five of the fictional records in FIG. 8 start the particle sequence with the particle Bill.
As shown in FIG. 9A, the K paths 903, 904 and 905 are established by following the praxis procedure 300 as explained above. For example, using the exemplary fictional data of the record set 800, the K structure 900 in FIG. 9A may be established as follows. The first fictional record processed may have been Bill_Tuesday_Sold_PA. As the praxis procedure 300 is followed, assume that in FIG. 9A, the K path 903 includes five nodes that are established for this record. The first field particle sequence in the record is Bill. Therefore, the node 902 may be the first node established in the K path 903 (after the BOT node). The node 902 may be initialized to 1 since the intensity variable is set to 1 and this is the first time the field particle sequence Bill is processed. The BOT node and the root node for the particle sequence Bill (not shown) may be incremented by 1 as well. Following the praxis procedure 300, the rest of the nodes of the K path 903 may be processed and built in the K structure. Each of the counts of the K nodes being built for the first record of the record set 800 may be incremented to 1. The corresponding root nodes may also be incremented to 1.
The second exemplary fictional record of the record set 800 processed in the building of the KStore represented by the node diagram 900 can be Bill_Monday_Sold_NJ. Since Bill was already processed, a new node for Bill is not created in the praxis procedure 300, as explained earlier. However, because the particle Bill is processed a second time, the count for the subcomponent node 902 as well as the Bill root node and the BOT node, are incremented to 2. Since this is the first time Monday is processed, a new node 906 is established to represent Monday. The counter of the new node 906 is set to 1. The root node for Monday is incremented to 1 also. The remaining nodes in path 904 for Sold and NJ are established in the same way in order to represent the second record. After all records 800 have been processed, the counts reflect the number of times each of the particle sequences has been processed. In the node diagram 900 representing the set of records 800, for example, Trial was processed three times. Therefore, there is a count of 3 in the Trial elemental root node. NJ was processed only once. Therefore, the NJ elemental root node has a count of 1.
In a preferred embodiment of the invention, the foregoing process occurs as events are learned into a K structure. When queries are performed on a K structure that contains the transaction records, count fields 902 may remain unchanged. It should be noted however that querying may update the count fields for some alternate embodiments.
Variable Intensity Values
The increment value however may not always be 1. If a situation requires it, the increment may be any value. As previously, described, the routines used by the praxis procedure 300 may update the count when they are called. The called routines may then use the increment value, or intensity value, when incrementing the count field. For example, see block 409 of FIG. 4 or the corresponding boxes in FIGS. 5B and 5C. If the transaction records being recorded are pre-sorted so that all duplicate records are grouped together, the learn routine might send the record only once with a larger intensity value to be used to increment or initialize the K node count field 702.
Referring back to FIG. 8, five fictional furniture store records 800 are shown. Notice that the last three records contain the same values:
Bill_Monday_Trial_PA. In one preferred embodiment of the invention, it may be advantageous to pre-sort the five records into three records: Bill_Tuesday_Sold_PA, Bill_Monday_Sold_NJ and Bill_Monday_Trial_PA. The first two records may be learned with an intensity value of 1 as previously described. Prior to being learned into K, the intensity value for the last record Bill_Monday_Trial_PA may be set to 3. Since the Bill node 902 was already processed twice, its counter may be incremented by the praxis procedure 300 in block 409 of FIG. 4 from 2 to 5 as well as the BOT node and the Bill elemental root node. The node 906 may be incremented from 1 to 4 by the same intensity value of 3 as well as the Monday elemental root node. The counts for the newly created subcomponent nodes 907 and 908, and the end product node 909 of the path 905 may be initialize to 3 because their counts are initialized to the current intensity value of 3. Note that the elemental root nodes for Trial, PA and EOT may also be incremented by the intensity variable of 3.
Furthermore, the intensity variable may change to different values and in different directions for various functions. A simple example of different intensities might be the addition of a value +1 each time a query traverses a node, and the addition of a value of −100 if a path containing a certain node (or certain sequence of nodes) is deemed (for some overarching reason not of importance to this explanation) to be a mistake. For example, a sequence may be determined to be a misspelling.
Additionally, a sensor may determine that an area contains a dangerous chemical. A human child simulator may touch and bum itself on a hot stove in a simulation.
In an alternate embodiment a separate additional field may hold a new intensity value for each different type of node traversal. For instance, one count additional field may be incremented whenever an Item is learned and a different count additional field may be incremented whenever the node is traversed for a query. Additional counts may be kept for traversals of different query or learn types; type one, type two, experience one, experience two, etc. ad infinitum. In an alternate preferred embodiment, intensity variables in a count field may provide a simple approach to this problem. If this alternative is considered, an approach of using a separate node, possibly even an elemental node, or root node, to record a count for the number of traversals of each type of sequence related to the node is one way to implement this approach. The praxis procedure 300 may then handle the updating of this node as shown in FIG. 5B.
Thus, in one embodiment, a count field 702 of a K node may be incremented when new data is incorporated in an interlocking trees data store, while incrementing the count field may be omitted when the interlocking trees data store is being queried. This approach yields a bigger value for new data and no change for inquiries. Accordingly, the intensity variable must be chosen for its suitability to the problem being addressed by the invention.
Negative Intensity Values
As shown above, the intensity value need not always be positive. Records or paths may be deleted from the K by subtracting an intensity value from their counts. In a field/record universe if a situation requires it, the count may be decremented to delete a record from the structure. The record to be removed can be presented as particles to the praxis procedure 300 in the same manner as a new record or a query, except that a negative intensity value may be provided.
Refer to FIG. 9B where the node diagram 1000 is shown. The node diagram 1000 differs from the node diagram 900 of FIG. 9A in that the counts for the nodes of the path 903 have been decremented by an intensity of 1. If the system has been so configured, and a record has been marked to be deleted (after already having been established into a K structure), the count field 702 for the nodes in the path 903 may be decreased by 1. This may result in the count fields of some of the nodes being zeroed as is shown in path 903 of the node diagram 1000.
In some preferred embodiments of the invention the count may be decremented to 0 but the nodes may remain in the K structure to indicate a history. In other embodiments, if the count is decremented to 0 or some other low value, the nodes may be entirely deleted from the K structure. The praxis procedure 300 may determine whether to delete the nodes having a low count within block 409 of FIG. 4, or the corresponding blocks in FIGS. 5B and 5C. In FIG. 9B the nodes in path 903 have been decremented to 0 but the path remains in the structure to provide a history.
While the invention has been described in detail and with reference to specific examples thereof, it will be apparent to one skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope thereof.

## Claims

1. In a KStore having a plurality of K nodes with a plurality of respective K node counts, a method for updating said K node counts of said plurality of respective K node counts, comprising:
processing a K node of said plurality of K nodes of said KStore, comprising elemental K nodes representing particles of data; and
updating a K node count in response to said processing;
wherein each K node of the plurality of K nodes comprises a Case pointer and a Result pointer;
said Case pointer and said Result pointer pointing to two K nodes from which said K node is formed;
said K node also comprising pointers to an asCase array and an asResult array;
said asCase array comprising pointers to K nodes whose Case pointers point to said K node: and
said asResult array comprises pointers to K nodes whose Result pointers point to said K node in accordance with a received particle to provide a processed K node: and
said KStore comprises a set of interlocking trees comprising a multi-rooted tree of asCase branches forming an asCase tree depending from a first root and asResult branches forming multiple asResult trees depending from multiple roots, wherein an asResult tree comprising a second root node link to an end product leaf node of the asCase tree accesses the branches of the asCase tree terminating in the end products, in inverted order.

2. The method for updating said K node counts of said plurality of respective K node counts of claim 1, wherein said processing of said processed K node comprises building said processed K node in response to said received particle.

3. The method for updating said K node counts of said plurality of respective K node counts of claim 1, comprising updating a K node count of a beginning of sequence node.

4. The method for updating said K node counts of said plurality of respective K node counts of claim 3, wherein a beginning of sequence K node comprises a beginning of thought K node.

5. The method for updating said K node counts of said plurality of respective K node counts of claim 1, further comprising determining that said received particle is a particle of sensor data having a corresponding sensor node to provide a sensor node determination.

6. The method for updating said K node counts of said plurality of respective K node counts of claim 3, further comprising updating a K node count of said corresponding sensor node in response to said sensor node determination.

7. The method for updating said K node counts of said plurality of respective K node counts of claim 3, further comprising determining a subcomponent node in response to said sensor determination; and updating a K node count of said subcomponent node.

8. The method for updating said K node counts of said plurality of respective K node counts of claim 7, further comprising comparing a Result node of an asCase node of a current K node with said sensor node to provide a processed subcomponent node determination.

9. The method for updating said K node counts of said plurality of respective K node counts of claim 1, further comprising determining that said received particle is a delimiter particle to provide a delimiter determination.

10. The method for updating said K node counts of said plurality of respective K node counts of claim 9, further comprising: determining an end product node in response to said delimiter determination; and
updating a K node count of said end product node.

11. The method for updating said K node counts of said plurality of respective K node counts of claim 9, wherein said KStore has a plurality of levels including a current level and at least one lower level below said current level further comprising determining a lower level delimiter in response to said delimiter determination to provide a lower level delimiter determination.

12. The method for updating said K node counts of said plurality of respective K node counts of claim 11, further comprising:
determining an end product node in response to said lower level delimiter determination; and updating a K node count of said end product node.

13. The method for updating said K node counts of said plurality of respective K node counts of claim 10, wherein said KStore has a plurality of levels including a current level and at least one higher level above said current level further comprising:
determining a further K node on said at least one higher level; and
updating a K node count of said further K node.

14. The method for updating said K node counts of said plurality of respective K node counts of claim 2, wherein said building comprises a learn operation.

15. The method for updating said K node counts of said plurality of respective K node counts of claim 1, wherein said updating occurs in accordance with a learn determination.

16. The method for updating said K node counts of said plurality of respective K node counts of claim 15, wherein said updating of a K node count is performed in accordance with a learn type.

17. The method for updating said K node counts of said plurality of respective K node counts of claim 1, wherein said updating is performed in accordance with a query determination.

18. The method for updating said K node counts of said plurality of respective K node counts of claim 1, wherein said experiencing of said processed K node comprises traversing said processed K node.

19. The method for updating said K node counts of said plurality of respective K node counts of claim 1, wherein said updating comprises adding an intensity value to said K node count.

20. The method for updating said K node counts of said plurality of respective K node counts of claim 19, wherein said intensity value is equal to one.

21. The method for updating said K node counts of said plurality of respective K node counts of claim 19, wherein said intensity value is not equal to one.

22. The method for updating said K node counts of said plurality of respective K node counts of claim 21, wherein said intensity value is greater than one.

23. The method for updating said K node counts of said plurality of respective K node counts of claim 19, wherein said intensity value is negative.

24. The method for updating said K node counts of said plurality of respective K node counts of claim 19, wherein said K node count is reduced to a low value.

25. The method for updating said K node counts of said plurality of respective K node counts of claim 24, wherein said K node is removed from said KStore in accordance with said low value.

26. The method for updating said K node counts of said plurality of respective K node counts of claim 24, wherein said K node is maintained within said KStore to provide a history.

27. The method for updating said K node counts of said plurality of respective K node counts of claim 19, wherein said intensity value is zero.

28. The method for updating said K node counts of said plurality of respective K node counts of claim 19, wherein said KStore is provided with a plurality of sequences for transmission to said KStore and for learning of said sequences into said KStore comprising:
determining a plurality of identical sequences;
determining a number of times an identical sequence of said plurality of identical sequences occurs; and
determining said intensity value in accordance with said number of times said identical sequence occurs to provide a multi sequence intensity value.

29. The method for updating said K node counts of said plurality of respective K node counts of claim 28, further comprising transmitting only a single occurrence of said plurality of identical sequence to said KStore.

30. The method for updating said K node counts of said plurality of respective K node counts of claim 29, wherein said single occurrence of said sequence is represented by a further plurality of K nodes having a further plurality of respective node counts further comprising adding said multi sequence intensity value to node counts of said further plurality of respective K nodes.