Source: http://www.google.com/patents/US20090115646?ie=ISO-8859-1
Timestamp: 2016-02-07 11:45:01
Document Index: 626106840

Matched Legal Cases: ['arts 31', 'art 31', 'arts 32', 'arts 33', 'art 32', 'arts 32', 'arts 33', 'art 32']

Patent US20090115646 - Data processing system and method - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA method of processing an encoded data stream comprises determining one or more data strings of interest; wherein the data string comprises a predetermined sequence of characters; encoding (3) the or each data string using the same encoding that was used to encode to the data stream; and searching (4)...http://www.google.com/patents/US20090115646?utm_source=gb-gplus-sharePatent US20090115646 - Data processing system and methodAdvanced Patent SearchPublication numberUS20090115646 A1Publication typeApplicationApplication numberUS 12/250,931Publication dateMay 7, 2009Filing dateOct 14, 2008Priority dateNov 5, 2007Also published asCA2642946A1, EP2056462A2, EP2056462A3, EP2056462B1, US7821427Publication number12250931, 250931, US 2009/0115646 A1, US 2009/115646 A1, US 20090115646 A1, US 20090115646A1, US 2009115646 A1, US 2009115646A1, US-A1-20090115646, US-A1-2009115646, US2009/0115646A1, US2009/115646A1, US20090115646 A1, US20090115646A1, US2009115646 A1, US2009115646A1InventorsNeil DuxburyOriginal AssigneeRoke Manor Research LimtedExport CitationBiBTeX, EndNote, RefManPatent Citations (7), Referenced by (10), Classifications (9), Legal Events (2) External Links: USPTO, USPTO Assignment, EspacenetData processing system and method
US 20090115646 A1Abstract
[0001] This invention relates to a method of processing an encoded data stream, in particular in the field of internet data processing systems.
[0002] Data streams typically comprise files which are split into fragments called packets. In the example of internet based system, these packets are sent from one computer to another using transmission control protocol (TCP) sessions.
[0003] Data compression is a common method that is used to improve the performance of data transmission systems by decreasing the amount of data that needs to be transferred by reducing the redundancy within that data. Data encryption is also used within internet based, or other communications to secure data prior to transmission.
[0004] It is known to provide content scanning systems that search within packets of character data to identify one or more predetermined strings. A typical such system would be an email filtering system in which the string or strings being searched for are members of a predefined selection of banned words, such as swear words.
[0005] A problem with such systems is that their scanning capabilities are defeated when the data being scanned is encoded in some way, such as by compression or encryption. The act of compression, or encryption converts a sequence of characters into a different sequence of characters whose format is defined by the compression, or encryption algorithm used.
[0006] In accordance with a first aspect of the present invention, a method of processing an encoded data stream comprises determining one or more data strings of interest; wherein the data string comprises a predetermined sequence of characters; encoding the or each data string using the same encoding that was used to encode to the data stream; and searching for the encoded data string in the encoded data stream.
[0007] The invention avoids the need to decode the complete data stream in order to search for a particular string of interest by encoding the string of interest and searching for its encoded form.
[0008] Preferably, the searching comprises comparing the encoded data string with characters in a first section of the encoded data stream; and if the characters match, extracting the first section from the data stream.
[0009] Preferably, the number of characters in the first section is greater than the number of characters in the encoded data string.
[0010] The encoded characters which are searched for may act as an identifier for a larger section, which is then extracted.
[0011] Preferably, the encoding comprises at least one of compression and encryption.
[0012] Either one of the encoding types may be applied, or both together.
[0013] Preferably, the compression comprises at least one of a compression algorithm with dictionary encoding; or sliding window dictionary encoding.
[0014] Specific types of compression algorithm may be applied and if desired combined with encryption.
[0015] Preferably, the encoding of the, or each, data string comprises dynamic Huffman coding.
[0016] In this case, preferably, the method further comprises identifying packets in the encoded data stream which include a Huffman code table; extracting the Huffman code table; assembling a Huffman code tree from the extracted Huffman code table; and encoding the data string by constructing a bit sequence, representing the data string, using the Huffman code tree.
[0017] In one embodiment, the data stream contains fixed and variable data parts; wherein the data string of interest is dependent upon at least one variable data part; wherein an exemplar document is created from the fixed data parts; and wherein a search pattern is created from a fixed data part immediately preceding a variable data part.
[0018] Preferably, packets containing the search pattern are identified and the variable data part decoded using the packet containing the search pattern; and wherein the data string is extracted from the decoded variable data part.
[0019] Preferably, the variable data part is decoded using a combination of the exemplar document and the packet containing the search pattern.
[0020] Preferably, the decoded data is merged into the exemplar document; wherein a further representation of the data string is created from the merged document; and a further search is carried out in the next fixed data part.
[0021] Alternatively, the decoded data is merged into the exemplar document; wherein a different data string is created from the merged document; and a further search is carried out in the next fixed data part.
[0022] Preferably, the merging, creation and further search steps continue until the complete encoded data stream has been searched.
[0023] Preferably, an encrypted search pattern is created from a fixed data part and an encryption key.
[0024] Preferably, packets containing the encrypted search pattern are identified and decoded using the encryption key.
[0025] In accordance with a second aspect of the present invention, a data processing system comprises an input for an encoded data stream; an encoder for encoding a data string; wherein the data string comprises a predetermined sequence of characters; a comparator for comparing a section of the encoded data stream with the encoded data string; and a processor to extract sections of the encoded data stream when the comparator finds a match.
[0026] Preferably, the system further comprises a store for storing the extracted sections for further processing.
[0027] Preferably, the encoder comprises at least one of a sliding window dictionary encoder; a compression algorithm dictionary encoder; and an encryption device.
[0028] Preferably, the section comprises a transmission control protocol session.
[0029] Preferably, the data string comprises part of a data packet.
[0030] An example of a data processing system and a method of processing an encoded data stream will now be described with reference to the accompanying drawings in which:
[0031] FIG. 1 illustrates an example showing the steps involved in applying the present invention to data encoded with dynamic Huffman coding;
[0032] FIG. 2 illustrates an example showing the steps involved in applying the present invention to data encoded using an LZ77 algorithm;
[0033] FIG. 3 illustrates how the present invention is applied to a data stream made up of both variant and invariant parts;
[0034] FIG. 4 illustrates how the present invention is applied to data encoded using a combination of LZ77 and Huffman coding; and,
[0035] FIG. 5 illustrates the steps involved in applying the present invention to an encrypted data stream.
[0036] Huffman coding is an entropy encoding algorithm used for lossless data compression. The coding uses a variable length code table for encoding a source symbol, such as a character in a file, where the variable length code table has been derived in a particular way based on the estimated probability of occurrence (or frequency) for each possible value of the source symbol. The frequencies used can be generic ones for the application domain that are based on average experience, or they can be the actual frequencies found in the text being compressed, which is known as dynamic Huffman.
[0037] To decode the compressed data, the code table is used to build a Huffman tree. Encoded symbols are then decoded by traversing the tree using the compressed data a bit at a time until the decoded symbol is found. The decoded symbol is then emitted by the decoder. When using dynamic Huffman coding the code table must be carried as part of the encoded data. This is usually done by prepending the code table to the file it was used to compress. This amalgamation is then packetised and transmitted.
[0038] LZ77 is a lossless data compression algorithm published in a paper by Abraham Lempel and Jacob Ziv in 1977. LZ77 algorithms achieve compression by replacing portions of the data with references to matching data that has already passed through the encoder/decoder. A match is encoded by a pair of numbers called a length-distance pair, which is equivalent to the statement “each of the next length characters is equal to the character exactly distance characters behind it in the uncompressed stream.” When decoding the data, a history buffer of decoded symbols is required so that the length-distance pairs can be resolved to a character. This property of LZ77 causes a problem with packetised data in that, for an individual packet, the history required to interpret the length-distance pairs is not available. Consequently, in isolation a packet encoded with LZ77 cannot be decoded.
[0039] One of the most commonly used compression methods within internet communications is Deflate which is a combination of LZ77 and Huffman coding. First a file is compressed using LZ77 and a Huffman code table is then generated from the LZ77 symbols contained within the LZ77 compressed version of the file. The data is then further compressed with Huffman coding using the code table derived from the data. The code table is then attached to the compressed data and the result is packetised and transmitted over an internet session.
[0040] Encryption uses a secret key is used to encrypt a file using an encryption algorithm.
[0041] A simple method to handle this compressed, or encrypted data is as follows:
[0000] A. Collect all of the packets within a session carrying a compressed/encrypted file.
[0042] The present invention searches for the occurrence of one or more strings, e.g. words, each formed of a predetermined sequence of characters within a sequence of character data which has been packetised and encoded, either by compression or encryption prior to transmission. Specifically, the invention is applied to transmission of a session over the internet. Within an arbitrary number of TCP sessions containing packetised compressed, or packetised encrypted data for any of a plurality of strings each formed from a predetermined sequence of characters, if a packet is found that contains one of these strings its associated session is selected and filtered off for further analysis. Sessions which are associated with packets that do not contain a string of interest are discarded.
[0043] In particular the present invention relates to the identification of predetermined string or set of strings within sessions whose packets have been compressed or encrypted using one or more of an entropy encoder, such as Huffman coding; a self referential compression algorithm such as LZ77; a combination of LZ77 and Huffman coding such as Deflate; or a session that has been encrypted using a known encryption algorithm.
[0044] There are various applications of the method of the present invention, for example searching for a username in data which is being transmitted, but which data has been encrypted. Decrypting the whole data stream to search for the one name is CPU intensive, but taking a string of interest, e.g. a username, using encryption keys to encrypt that string, then searching for a subset of the encrypted username in the encrypted data stream means that it is possible to only select the desired section containing this part and decrypt that section, or store it for further analysis, rather than decrypting the complete data stream, i.e. the encrypted fragments effectively carry out a pre-selection. If a user is able to start from a document having known content, which is encoded, either by compression, encryption, or both, then if the algorithm used to compress or encrypt is known, it is possible to find something from the original e.g. a page from a text book.
[0045] In the instance where dynamic Huffman codes are used to encode the data, a string of interest within a packet can be identified as follows, as illustrated in FIG. 1. First the packets containing the Huffman code table are identified 1, then the Huffman code table is extracted 2 and a Huffman code tree is built. The Huffman code tree is used to construct 3 a bit sequence that represents the sequence of Huffman codes defined by the characters in the search string. This bit pattern can then be used to search 4 the compressed data directly. If an instance of the bit sequence is found within the compressed data then a match has been found. This methodology can be generalised to a set of patterns by generating a bit sequence for each string within the set of patterns. The search is then generalised by searching for the set of bit sequences in the compressed data.
[0046] In the instance where LZ77 is used to encode the data a string of interest within a packet can be identified by carrying out the following steps, as illustrated in FIG. 2:
[0047] If the contents of a document are known a priori to a search then instances of a string within the compressed packetised version of that document can be identified by representing the search string in the LZ77 format in which it will be present within the compressed form of the document (step 10).
[0048] Due to the properties of the LZ77 algorithm each instance of a search string will have a different format. However, as the original content of the document is known all these formats can be predicted by applying the LZ77 compression algorithm to the known document (step 11).
[0049] A packet containing an instance of a search string can be identified by searching for the set of LZ77 formats defined by compressing the known document using the LZ77 algorithm (step 12).
[0050] As stated previously, for an individual packet decompression is not possible as the decode buffer required for decoding the length-distance pairs is not available. However, if the contents of a document is known a priori to the search then the decode buffer can be provided by a copy, or exemplar of the known version. Thus, rather than use the length-distance pairs to find content in the decode buffer they instead are used to find content in the exemplar document (step 13). This step allows the data to be decoded on a per packet basis without the associated decode buffer.
[0051] However, when a document has varying content, e.g. an access log with a list of time stamps, then although it could be compressed or encrypted with a known algorithm, the actual content is not known, so this cannot be simply encoded and searched for. This is not such a problem if the algorithm is of a certain type, e.g. Huffman, i.e. a compression algorithm with a dictionary encoder, but it can be an issue with other types of encoding. If the dictionary, in this case the Huffman table, is known, then the search pattern can be encoded, either by compression, encryption, or both and the pattern searched for directly. A search is made for the whole pattern, which can be speeded up by doing a byte at a time pattern match, then addressing the remaining bits, rather than a bit at a time.
[0052] A further scenario is one in which data has a partly fixed, partly varying content, e.g. a webmail form. An example of such an application is collecting statistics on the number of users wanting to make particular train journeys, or demographic profiling in order to send targeted advertising. A third party could be looking at the data and adapting the adverts based on what journey information is requested by the user. The structure of the form which is visible is fixed in HTML, but the actual details entered are different for each user who completes the form. In this case, the known structure of the form can be used to predict where the varying data content occurs. The aim is to find the dynamic parts and resynchronise to the compression stream, then decode the data. All variable parts up to the part containing the predicted pattern within the data stream compressed file are decoded.
[0053] In the case where the content of a document is not known a priori to the search, for example, the user generated or variant content of an email message is not known before it is sent, there may be regions of the document that appear in every instance of a document of that type. For example, all emails have the same general structure and include regions of text that are common to all emails. In general a document can be viewed as a sequential series of invariant and variant (user generated) parts, as illustrated in FIG. 3.
[0054] The parts of the document that are known a priori to the search can be used to create an exemplar document (step 14). In this case the exemplar only contains the parts of the document that do not change due to user generated input, the invariant parts 31, 33, 35.
[0055] If a search string exists in a first invariant part 31 of the document (step 15), then a packet containing that string can be found and decompressed using the methodology of steps 10 to 13.
[0056] If the string to be found exists in one of the variant parts 32, 34 or within one of the invariant parts 33, 35 that lies beyond the first variant part 32 (step 10) then an instance of a search string can be found using the following methodology.
[0057] An exemplar document is created from the collection of invariant parts of a document as per step 14.
[0058] Using the exemplar document a search pattern is created from the sequence of characters that immediately precedes the first section of variant content (step 17).
[0059] The LZ77 form of this search pattern is then created using the contents of the first invariant part of the exemplar document (step 18).
[0060] The packet containing the LZ77 form of said search pattern is then identified by scanning for it in every packet (step 19).
[0061] Once this packet has been found the first variant part can be decompressed (step 20) using the contents of the exemplar document from step 14.
[0062] The decompressed data can then be scanned for instances of the search string. Any instances of the search string are then recorded (step 21).
[0063] The exemplar document is then updated by merging the decompressed data into it (step 22).
[0064] The LZ77 form(s) of the search string defined in step 11 are then recomputed for use in the second invariant section of the document (step 23). This allows the LZ77 form(s) of the search string defined in step 11 to be updated to take account of the user generated data contained in the first variant part of the document.
[0065] The updated LZ77 form(s) can then be used to find instances of search string in the second invariant part of the document (step 24). Any instances of the search string found are recorded.
[0066] The updated exemplar document is then used to create a search pattern (step 25) to find the next variant part of the document using similar methodology to step 18. Steps 16 to 24 are then repeated to find the subsequent instances of the search string in the document.
[0067] This process is repeated (step 26) until no data is left.
[0068] The advantage here is that the use of the exemplar document and the re-factoring of the search patterns means that the invariant parts of the data do not need to be decompressed. Consequently, it is possible to avoid decoding a large fraction of the packetised data and only decode those packets that contain the search strings of interest. This methodology can be generalised to a set of patterns by applying the methodology to the pattern set rather than just a single string.
[0069] Combining a method such as LZ77 with Huffman coding gives a higher compression ratio, but this makes it harder to find where to skip to. A Huffman data stream is bit aligned, so in order to decode the data at an arbitrary position in a compressed data stream it is necessary to find a way of re-synchronising at each point that is skipped to. In general, re-synchronisation can be achieved by creating a long bit sequence. This sequence can then be re-aligned to the bit stream at an arbitrary point by identifying sections whose bit sequence is the same as that of the test pattern. If the pattern is long enough then there will be an increasingly small probability of a mismatch. Once the data stream is synchronised, the data can be decoded in the normal way.
[0070] To handle Deflate encoding (a combination of LZ77 and Huffman coding) the methodology described for Huffman coding (FIG. 1) is applied to the patterns generated using the methodology for LZ77 (FIG. 2). This is illustrated in FIG. 4. First the packets containing the Huffman code table are identified (step 50), then the Huffman code table is extracted and built (step 51).
[0071] If the contents (step 52) of the document are known (step 53) a priori to a search then instances of a string within the compressed packetised version of that document can be identified by first representing (step 54) the string in the LZ77 format(s) in which it will be present within the compressed form of the document.
[0072] Due to the properties of the LZ77 algorithm each instance of a search string will have a different format. However, as the original content of the document is known all these formats can be predicted (step 55) by applying the LZ77 compression algorithm to the known document.
[0073] Once the set of LZ77 patterns have been devised the Huffman code table is used to convert (step 56) the set of LZ77 patterns into their Huffman encoded variants. A packet containing an instance of a search string can be identified by searching (step 57) for the set of Huffman encoded LZ77 formats defined by compressing the known document using the LZ77 algorithm.
[0074] When a Huffman encoded LZ77 pattern is found then the Huffman coding is removed (step 58) and then the LZ77 format is decoded (step 59) using the exemplar document based method described previously.
[0075] When a document has partly fixed and partly varying content, i.e. all the content is not known (step 60) a priori, a similar method to that used to handle the LZ77 format can be used. The method differs in that searches are made for the Huffman coded variants of the LZ77 patterns.
[0076] If the string exists in a first invariant part of the document then a packet containing that string can be found and decompressed using the methodology for a document where the content is known a priori (steps 54 to 59).
[0077] If the string to be found exists (step 16) in one of the variants parts 32, 34 or within one of the invariant parts 33, 35 that lies beyond the first variant part 32 then an instance of the string can be found using the following methodology.
[0078] As before, first the packets containing the Huffman code table are found (step 50) and the Huffman code table is built (step 51).
[0079] An exemplar document is then created (step 14) from the collection of invariant parts of the document. Using the exemplar a search pattern is created (step 17) from the sequence of characters that immediately precedes the first section of variant content.
[0080] The LZ77 form of this pattern is then created (step 18) using the contents of the first invariant part of the exemplar document.
[0081] The Huffman coded form of this LZ77 pattern is then created (step 61) using the Huffman code table.
[0082] The packet containing the Huffman coded LZ77 pattern is then identified (step 62) by scanning for it in every packet.
[0083] Once found the first variant part can be decompressed by re-synchronising (step 63) the Huffman pattern, decoding the Huffman (step 64) using the code table above and then decoding (step 65) the LZ77 using the exemplar document.
[0084] The decompressed data can then be scanned (step 66) for instances of the search string. Any instances of the search string are then recorded.
[0085] The exemplar document is then updated by merging (step 67) the decompressed data into it.
[0086] The LZ77 form(s) of the search string are then recomputed (step 68) with forms of the search pattern using the updated exemplar document, for use in the second invariant section of the document. This allows the LZ77 form(s) of the search string defined in the previous phase to be updated (step 69) by recomputing the Huffman coded version of the LZ77 pattern, to take account of the user generated data contained in the first variant part of the document.
[0087] The updated LZ77 form(s) of steps 68 to 69 can then be used (step 70) to find instances of the search string in the second invariant part of the document. Any instances of the search string found are recorded.
[0088] The updated exemplar document is then used (step 71) to create a search pattern to find the next variant part of the document using similar methodology to the previous phase. The method is then repeated to find the subsequent instances of the search string in the document.
[0089] This process is repeated (step 72) from step 18 onwards, with the “first invariant part” replaced with “updated exemplar” and with the “first variant part” replaced with “next variant part”, until no data is left.
[0090] The process for handling encrypted content is similar to that used to handle LZ77 content. Assuming that the encryption key is available then for documents in which the content is known a priori to a search, an instance of a string within the encrypted packetised version of that document can be identified by creating a set of patterns representing the search string in its encrypted formats. Note there may be several such patterns in the encrypted content as the search string may be mixed with different sections of the text that surround it during the encryption process. This action will modify the exact sequence of bytes which are output by the encryption algorithm.
[0091] Packets containing the search string(s) can be found simply by scanning for the set of encrypted patterns defined by the text and the encryption key in use.
[0092] For encrypted documents which are a series of invariant and variant parts a similar methodology to that used for LZ77 can be adopted. In this case if the search string lies within a section of variant text then the encrypted version of that text cannot be determined a priori to the search. Similarly, if an instance of the search string lies on the edge of a variant section then the encrypted version of that text cannot be determined a priori to the search.
[0093] These difficulties can be overcome by identifying and decrypting the sections of variant content. The methodology to achieve this is equivalent to that described in steps 16 to 25 of the LZ77 methodology:
[0094] First an exemplar document is created from the invariant parts of the plaintext document (step 40).
[0095] The first invariant part of the exemplar document along with the encryption key is used to compute the format(s) of the encrypted search pattern within the first invariant part (step 41). Any instances of these patterns are then recorded by identifying them with the set of encrypted patterns.
[0096] The exemplar document is then used to generate a search pattern to identify the text preceding the first variant part (step 42).
[0097] The packet containing this pattern is then identified (step 43).
[0098] The packet identified in step 43 is decrypted using the encryption key (step 44).
[0099] The decrypted data in step 44 is scanned for the search string and any instances are recorded (step 45).
[0100] The decrypted data in step 44 is then merged with the exemplar document of step 40 (step 46) and the updated exemplar document is used to create new search patterns to facilitate the identification of the search string within the subsequent sections of the file (step 47).
[0101] The above steps are repeated until all of the data in the file has been covered. This methodology can be generalised to a set of patterns by applying the methodology to the pattern set rather than just a single string.
[0102] Features of specific embodiments of the present invention include the re-factoring of a search string, or set of strings using a Huffman code table derived from data in the string. Patterns derived in this way are used to search packetised data. An exemplar document is used to create a set of search patterns for a search string of interest and the set of patterns are used to identify packets of interest within a session containing encoded packetised data. The exemplar document is then used to decode the packets identified as being of interest.
[0103] In situations where documents being searched consist of both variant and invariant parts, an exemplar document is created from the collection of invariant data and used to create a search pattern for identification of a sequence of characters that occurs before a section of variant content. The pattern is then used to find the packets containing variant content. The decoded variant data is merged with the invariant data within the exemplar document and subsequently new search patterns are generated from the merged form of the exemplar document, then later data is decoded using the merged form of the exemplar document.
[0104] The present invention has been described with particular reference to Huffman coding and LZ77, but is equally applicable to other types of coding which follow a similar structure.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5936636 *May 16, 1996Aug 10, 1999Sun Microsystems, Inc.Encoding schemesUS6005504 *Jan 20, 1998Dec 21, 1999Sony CorporationPosition information encoding apparatus and method thereof, position information decoding apparatus and method thereof, and map information processing apparatus and method thereofUS7102552 *Jun 7, 2005Sep 5, 2006Windspring, Inc.Data compression with edit-in-place capability for compressed dataUS7155063 *Feb 21, 2003Dec 26, 2006Canon Kabushiki KaishaImage processing apparatus and method of controlling sameUS7358874 *Jun 7, 2006Apr 15, 2008Windspring, Inc.Data compression using a stream selector with edit-in-place capability for compressed dataUS7616138 *Feb 27, 2008Nov 10, 2009Windspring, Inc.Data compression using a stream selector with edit-in-place capability for compressed dataUS20030161538 *Feb 21, 2003Aug 28, 2003Canon Kabushiki KaishaImage processing apparatus and method of controlling same* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS8782734Jan 14, 2011Jul 15, 2014Novell, Inc.Semantic controls on data storage and accessUS8811611Oct 8, 2009Aug 19, 2014Novell, Inc.Encryption/decryption of digital data using related, but independent keysUS8832103Apr 13, 2010Sep 9, 2014Novell, Inc.Relevancy filter for new data based on underlying filesUS8874578Dec 30, 2009Oct 28, 2014Novell, Inc.Stopping functions for grouping and differentiating files based on contentUS8983959Dec 30, 2009Mar 17, 2015Novell, Inc.Optimized partitions for grouping and differentiating files of dataUS9053120 *Dec 15, 2009Jun 9, 2015Novell, Inc.Grouping and differentiating files based on contentUS20110016101 *Jan 20, 2011Isaacson Scott AStopping Functions For Grouping And Differentiating Files Based On ContentUS20110016124 *Dec 30, 2009Jan 20, 2011Isaacson Scott AOptimized Partitions For Grouping And Differentiating Files Of DataUS20110016138 *Jan 20, 2011Teerlink Craig NGrouping and Differentiating Files Based on ContentUS20110225659 *Sep 15, 2011Isaacson Scott ASemantic controls on data storage and access* Cited by examinerClassifications U.S. Classification341/65, 341/106International ClassificationH03M7/40, H03M7/00Cooperative ClassificationH04L9/065, H04L2209/30, H03M7/30European ClassificationH03M7/30, H04L9/00Legal EventsDateCodeEventDescriptionJan 5, 2009ASAssignmentOwner name: ROKE MANOR RESEARCH LIMITED, UNITED KINGDOMFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DUXBURY, NEIL;REEL/FRAME:022057/0769Effective date: 20081113Apr 17, 2014FPAYFee paymentYear of fee payment: 4RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services