High speed data classification system

[0001] 1. Technical Field

[0002] The invention relates to computer networks. More particularly, the invention relates to an information processing system.

[0003] 2. Description of the Prior Art

[0004] Communication between computers over the Internet can be compared to the delivery of mail and packages by the United States Postal Service. Users access the Internet through a variety of options, e.g. phone modems, DSL modems, cable modems, T-1 lines, local area networks, wireless networks, and wide area networks.

[0005] In the world of the U.S. Postal Service, access to the mail system could be through a mail-slot in the door of your home, a mailbox at the street in front of your home, a post office box on a street corner, a post office counter, or a post office box. By analogy, each user of the Internet is assigned an address, and the Internet infrastructure learns how to deliver messages intended for them.

[0006] In the world of the Postal Service, the zip code, city, street, and street number are used progressively to determine how to route and deliver the mail. Users of the Internet rely on various networking protocols to transfer messages between computers.

[0007] In the world of the Postal Service, the protocols for delivering the mail include First Class Delivery, Next Day Air, Parcel Post, and Bulk. In the world of the Internet, messages are sent in packets, as opposed to the letters that are sent in the world of the Post Office. These packets contain information necessary for delivery, and this information is found in the Packet Header. This packet header includes the recipient's addresses and the sender's address, as well as the delivery method and style of message. The packet header is comparable to all of the information that is visible on the outside of a letter or package, i.e. recipient's address, return address, mail type, and specific handling instructions, such as FRAGILE. The remainder of an Internet packet contains user data. This user data is comparable to what is found inside an envelope or package. The Internet infrastructure has no more need to see the user data to route and deliver the message to the intended computer accurately than the post office has to open the mail it handles to figure out where to send it. Table A below shows a typical Internet packet.

[0008]

TABLE A
Typical Internet Packet
	Packet Header	Data Payload

[0009] As computers are tied together over the World Wide Web, the physical connections between the computers look like a giant spider web. The thick strands of this web transfer huge numbers of packets between big cities to move them along their way. This is comparable to the air or truck traffic carrying millions of letters between postal hubs. At each connection point on the World Wide Web, a sorting function must be performed to determine which direction a message should be sent. This sorting of packets is similar to the process where high-speed postal sorters scan letters to determine their addresses and figure out which direction to send them. Sorting of data packets is often referred to as packet classification

[0010] An optical router is a device that has many input/output (I/O) ports or connections. Each I/O port connects through an optical fiber to another optical router, optical switch, or optical adapter that can be located a long distance geographically from the first device. In simplistic terms, the purpose of an optical router is to receive data packets on each I/O port, to interpret the headers within the packet, and to route the packet out the appropriate I/O port towards the destination computer. If an optical router is unable to sort packets quickly enough, packets backup and are potentially lost by the router. In such case, the Internet slows down and computer users may lose their connections. As more and more people use the Internet, the situation internal to the optical routers that makeup part of the Internet infrastructure can start to look as chaotic as the Post Office at Christmas time.

[0011] The goal of an optical router is to interpret the packet header for each received packet as fast as possible so that the packets can be sent out the correct I/O port. This avoids delays, backups, and potentially lost packets. One problem is that thousands of different users can be sending messages through a router at the same time, and the packets all need to be sorted and routed differently. Table B below shows how the number of possible headers that can be received increases dramatically as the number of bits in the packet header increases.

[0012]

TABLE B
Possible Headers versus Header Bit Length
Packet Header Bit
Length	Possible Headers
8	256
16	65536
32	4.29 E9
64	1.84 E19
128	3.40 E38
256	1.16 E77
512	1.34 E154
1024	1.80 E308

[0013] The problem of receiving a packet and identifying critical header information to decide where to route the packet is much like finding a needle in a haystack. Initially, routers used microprocessors and large lookup tables in memory to search for addresses and header information. Later, as data rates increased, system designers moved to content addressable memories (CAMs) to allow the received packet header to be compared to all previously analyzed packet headers simultaneously. The architecture of a CAM permits the user to apply the received header information to the memory and to determine to which location(s) it matches.

[0014] Because the performance of CAM's could not keep up with ultra-high speed router implementations, some manufacturers switched to custom ASICs (Application Specific Integrated Circuits) to evaluate packet headers in a rapid fashion.

[0015] Optical networking is a significant business opportunity because of the tremendous increases in data bandwidth requirements resulting from the increasing use of Internet. The capability of optical fibers to transmit and receive data exceeds the capability of electronic and electro-optical interface products to keep up with increasing data rates. Presently, OC-192 standard networks that operate at 10 Gbit/sec are beginning to be used. Presently available optical routers address the need attendant with processing and routing packets from OC-192 systems.

Existing Optical Network Packet Classification Schemes

[0016] High performance optical routers have been generally implemented using either CAMs or custom ASICS to perform packet classification. The custom ASIC approach must rely on filtering and interpreting some subset of possible packet data patterns to determine how to route packets. The approach is inflexible and may be difficult to scale with new standards and new protocols. The CAM approach is more flexible and is popular in high end routers. CAMs are designed to be cascaded so that greater numbers of data bits can be analyzed. CAMs are designed to permit various levels of “don't care” functionality that has increased their flexibility and usefulness.

CAM Based Classification Systems

[0017] A typical router is shown in FIGS. 1a and 1b and is used to describe some of the problems associated with increasing data rates to 10 Gbit/sec, 40 Gbit/sec, and beyond. In FIG. 1a, the optical interface 11 translates the light stream into electrical signals and vice-versa. In the receive mode, the data framer 12 is responsible for extracting a serial receive clock and corresponding serial receive data stream. The serial data stream must then be converted into a parallel sequence of words that correspond to a packet. The parallel sequence of words can be operated on by a network processor 13, and eventually routed into the switch fabric 14 where they are sent to the appropriate destination.

Custom ASIC Solution (Juniper Networks ASIC2)

[0018] Juniper Networks (Sunnyvale, Calif.) provides high performance routers that use a custom ASIC solution that is marketed as the Juniper Networks ASIC2. The Juniper Networks ASIC2 in conjunction with the Juniper “Junos” software allows up to 40 M packets/sec to be forwarded in the Juniper system. From Juniper's data sheets, the following:

• • [0019] Juniper's routers leave the packet in the shared memory and move only a packet pointer through the queues. When packets arrive they are immediately placed in distributed shared memory where they remain until being read out of memory for transmission. This shared memory is completely nonblocking, which in turn, prevents head-of-line blocking.

[0020] FIG. 1b shows how a Juniper router is believed to be implemented, and how it relies on a very high speed shared SRAM 17 where packets are stored and operated on. This architecture avoids the movement of packets around in memory which can take up a considerable amount of time.

CAM and Custom ASIC Shortcomings for Packet Classification of OC-192 and Beyond

[0021] A variety of problems are beginning to plague CAM and customer ASIC based systems as data rates are moving to OC-192 (10 Gbits/sec) and OC-768 (40 Gbits/sec). Some of the biggest problems have to do with raw forwarding throughput, which is related to how many packets per second can be processed; latency, which is related to the absolute delay through a router; system power consumption; and board area. A key component of packet latency through a router is the time necessary to perform packet classification. As latency increases, the chances of experiencing upper level networking protocol timeouts for a packet increase.

[0022] Typical CAM structures have a width that is associated with how many bits the user desires to analyze, and a depth that is based on the number of possible patterns that the user wishes to differentiate between. CAMs are cascadable to meet both the width and depth that is required. The downside of cascading is that it costs money, increases board area, and increases power consumption. On the other hand, the ASIC2 solution from Juniper Networks does not appear to be cascadable. It appears to operate on data in the SRAM, and permits qualified searches on only certain fields and bits. This limits the ASIC2 solution approach when new search criteria are desired to be used.

Packet Classification Forwarding Rate and Latency Issues

[0023] The issues of forwarding rate and latency are intertwined and need to be addressed together. There are two significant architectural issues that affect forwarding rate and latency, i.e. the design of a packet's data flow through the system, and the underlying performance of the packet classification hardware.

[0024] In a CAM based system, such as that in FIG. 1a, parallel data from the data framer and any associated memory must be moved by the network processor or custom hardware into the CAM 15 for analysis. This is done after a packet has been received. This data must be moved quickly or additional latency is introduced. Table C below shows how the spacing between words in a received data pattern decreases as the serial data rate is increased. Each word that must be transferred to the CAM requires a read from the data framer's memory and a write to the CAM. In the case of very short data packets, which are the hardest for a router to handle, most of the packets must be transferred into the CAM. Even if reading from the data framer and writing to the CAM could be each done in a single cycle, this would require a dedicated 1/(3.2 nsec/2)=625 MHz processor and memory system to keep up at OC-192 rates with a 32 bit data framer. The problem becomes four times worse at OC-768 speeds and would require a processor and memory system running at 2.5 GHz.

[0025]

TABLE C
Data Framer Output Word Separation vs. Data Rate
		OC-48	OC-192	OC-768
		2.5 Gbit/sec	10 Gbit/sec	40 Gbit/sec
Output Separation	12.8 nsec	3.2 nsec	0.8 nsec
(for a data Framer with a 32
Bit Output Word)
Output Separation	25.6 nsec	6.4 nsec	1.6 nsec
(for a data Framer with a 64
Bit Output Word)

[0026] In addition to the delays and uncertainty associated with transferring the data from the data framer into the CAM memory, there is the delay of the CAM memory in processing the data once the final word has been presented. Typical CAM memories have delays of approximately 100 nsec from application of data to input match. This is expected to improve as CAM technologies improve, but is not likely to experience anything close to four times improvements as users move from OC-192 to OC-768. Due to this inherent access delay of CAM memories, the delay in receiving routing information becomes worse relative to data rate as speeds increase. This results in the need to increase queue's and storage depths to account for buffering data prior to knowing to where it should be routed.

[0027] Present CAM classification systems are claimed to operate at full line data rates. The problem is that they require packets to be received, staged, and then sent into the classification engine to determine an appropriate route or other required information. This delay increases the latency through the router for a packet to be sent. Eventually, this latency through a router can start to impact connections going through the router and can result in higher layer timeouts. As new CAM technologies are implemented, the focus is on increasing size and maintaining access time. Therefore, the access time is not scaling anywhere near as quickly as data rate.

[0028] In the case of the Juniper Network's ASIC2 solution (FIG. 1b), it is difficult to glean detailed technical information from their website. It appears as though the ASIC2 approach operates on a packet that is in shared SRAM. The appropriate bits of this packet appear to be transferred into the ASIC2 18 so that it can perform packet classification. This transfer has measurable delays associated with it, depending upon the hardware architecture and the memory speed. If the shared SRAM has a 10 nsec access time, and it is 64 bits wide, it takes 40 nsec to transfer 256 bits into the ASIC2 chip before a classification begins. The ASIC2 specification identifies a performance metric that provides a raw maximum 40 Million Packets/se of classification performance, which implies a classification every 25 nsec. This could be for packets requiring only a single data write into the ASIC2 part because it is a top end specification. Even in the Juniper ASIC2 solution, the parallel movement of data into the ASIC2 part must limit the performance of the overall packet classification system. The ASIC2 solution has a much lower inherent latency than present CAM solutions, but it's packet classification time varies based on packet movement and memory access prioritization. Even with it's higher performance, the ASIC2 solution does not begin packet classification until well after a data packet has been received. As data rates continue to increase this becomes an architectural limitation for the ASIC2 custom approach.

Power Consumption and Board Area Issues.

[0029] The overall power consumption of a router system increases because the network processor speed must be increased to process higher data rates. In addition, CAM memories have a static current draw that must be accounted for and scaled up. As an example, a currently available network data base search engine using CAM technology draws 6 Amps @1.5 Volts running at 1000 MHz. This is an extremely high 9 Watts on a single chip. This impacts the usability of this solution in applications where space is tight and power is limited. It is noted the increased power consumption also raises issues of heat dissipation that must be addressed.

[0030] As packet classification searches farther into a packet, such as to 512 or 1024 bits deep, CAM based solutions require multiple parts to be operated in parallel. This significantly increases power consumption and board area. In the case of the ASIC2 solution, increasing the depth of the classification requires an entirely new part to be developed. In addition, the ASIC2 solution could require greater memory bandwidths with higher speeds, which would entail more parts and larger ASICs.

[0031] It would be advantageous to provide an improved system for ultra-high speed packet classification of optical data that has been framed into a serial data stream.

[0032] The herein disclosed invention provides a system that permits flexible, low latency, ultra-wide, and deep classification of high speed data. A presently preferred embodiment of the invention comprises an optical network packet classification architecture that addresses the packet classification requirements for OC-768 optical routers and beyond. Packet classification involves understanding the source and destination of a packet, as well as interpreting information within the packet header to determine what the optical network processor should do with the packet. As the data rates of optical networks move up to OC-768 and beyond, the job of performing packet classification is becoming increasingly more difficult. The approach used in the herein disclosed system allows for true “Light Speed” classification of optical data packets.

[0033] The herein disclosed system is used for ultra-high speed packet classification of optical data that has been framed into a serial data stream. The presently preferred embodiment of the invention provides a system that operates in the receive path, where electronic data are provided by the optical interface to the data framer. The preferred embodiment of the invention incorporates unique features into a traditional optical data framer chip and relies on a complex ASIC to permit the user to differentiate between up to 10,000 different patterns at light speed. One purpose of the general purpose system disclosed herein is to eliminate the need for costly and power consumptive content addressable memory systems, or customer pattern specific ASICs, to perform network packet classification. The system operates on a principle of adaptive programmable randomization to permit a differentiation between the input vectors to be made. The invention dramatically reduces the processing burden required by high-speed optical routers or switches.

[0034] The modified data framer that is used in the preferred system is referred to herein as the novel data framer; the complex ASIC that is used to control the adaptive programmable randomizer is referred to herein as the ASIC, both of which are discussed in greater detail below.

[0057] The herein disclosed system is used for ultra-high speed classification of data that have been organized into a serial or parallel data streams. The presently preferred embodiment of the invention provides a system that operates in the receive path, where electronic data are provided by the optical interface to a data framer. In one embodiment, the invention incorporates unique features into a traditional optical data framer chip and relies on a complex ASIC to permit the user to differentiate between up to 10,000 different patterns at light speed. One purpose of the general purpose system disclosed herein is to eliminate the need for costly and power consumptive content addressable memory systems, or customer pattern specific ASICs, to perform network packet classification. The system operates on a principle of adaptive programmable randomization to permit a differentiation between the input vectors to be made. The invention dramatically reduces the processing burden required by high-speed optical routers or switches.

[0058] The modified data framer that is used in the preferred system is also referred to as the novel data framer; the complex ASIC that is used to control the adaptive programmable randomizer is also referred to as the ASIC, both of which are discussed in greater detail below.

[0059] The herein disclosed optical network packet classification system analyzes the packet headers of messages sent over the Internet. At their lowest possible level, these packet headers are made up of a sequence of bits that are either a 1 or a 0. The address and networking information for each Internet packet are encoded into these header bits. Depending upon the method of sending the packet, it is possible for there to be many hundreds of bits in the packet header. These bits of data are transferred through optical fibers by pulsing light on or off.

[0060] For discussion purposes, the Table D below shows how a packet header would look if it were broken into discrete bits. In this example, the packet header is made up of only ten bits. The first bit to be sent using a light pulse is B0, and the last bit to be sent is B9. The sequence of light pulses corresponding to this packet header is 1110101001.

[0061]

TABLE D
Sample 10 bit Packet Header (Example only)
	Bit
	B0	B1	B2	B3	B4	B5	B6	B7	B8	B9
Value	1	1	1	0	1	0	1	0	0	1

System Specifications

[0062] The following specifications (Table E) apply to a system comprising the presently preferred embodiment of the invention. The general specifications apply to the overall system performance. The bit masking specifications apply to the ability to mask, or ignore, bits in the received packet header. In the case of the herein disclosed system, there is extensive flexibility for masking bits in one operation and then removing the masking in a later step. The masking operation is comparable to looking at a piece of mail and first checking only the zip code to which it is being sent. The next step with the piece of mail might be to look at the city and the street address to determine which mail carrier should be given the letter.

[0063]

TABLE E
System Specifications
Specification
Group	Specification Name	Specification
General	Maximum Number of Inputs	10,000 (Note 1)
	Maximum Input Length	1024 bits
	Maximum Classifiable Bits	10,240,000 bits
	Average Input	>50 Million Packets/sec
	Classification Rate (excluding	(Note 2]
	Flexible Masking).
	Maximum Input Classification	<50 nsec (Note 3]
	Time per Masking step.
Bit Masking	Types of Bit	Fixed Block and Flexible
	Masking Provided
	Fixed Block Masking Length	Permits gating off one
		block of data bits that
		ranges from 1 to 1023 bits
		in length.
	Flexible Masking Bits	128 individually
		programmed bits in four
		selectable 32 bit blocks.
	Number of Flexible Masking	8 patterns that encompass
	Patterns permitted	all 128
		individually programmed
		masking bits.
	Maximum number of	8 steps that include
	sequential	either a final
	flexible masking steps	data pattern or one of the
	per input verification.	flexible masking patterns.
System	novel custom ASIC	Heart of the system for
Components		analyzing received data and
		determining the input.
	Novel data Framer	Standard data Framer
		product with modifications
		to support the System
		classification protocol.
	SRAM and DRAM	Size based upon the
		number of inputs
		SRAM = 7 nsec–15 nsec
		Access
		DRAM = 50 nsec Access
Note 1 - The initial system chipset is designed to handle 10,000 inputs. Architecturally, this could be increased to 40,000 inputs in a second version of the part. Ultimately, the architecture permits 80,000, 160,000, or more inputs with increased memory and ASIC sizes, but with no speed degradation. The programmable masking patterns of the system permit significantly more than 10,000 inputs to be handled effectively by the system.
The 10,000 input number refers to the number of either inputs or mask patterns that can be stored.
Note 2 - Expected values through the use of 7 nsec SRAMs in the system and based upon an average of 2.35 SRAM accesses per classification.
Note 3 - Expected values through the use of 7 nsec SRAMs in the system and based upon a maximum of 6 SRAM accesses per classification.

[0064] The number of fixed block masking periods and the number of flexible masking bits can be increased with increased ASIC sizes. The fixed block masking is intended for a long sequence of bits that are always ignored, while the flexible masking bits are provided to deal with individual fields of bits.

Example of Fixed Block Masking

[0065] Table F shows a setup where the length of the packet header to be evaluated is 564 bits. This value is called the input length. All bits that are received after the 564^th bit are not used in the packet classification because they exceed the Input Length. A fixed block masking period from bits 136–227 is used in the example. This means that bits falling within this bit window are not used in the input classification evaluation. As an example, the fixed block masking is comparable to ignoring the sender's address when trying to determine where mail should be sent.

[0066]

TABLE F
Fixed Block Masking
Bit
Number	Bits 0–135	Bits 136–227	Bits 227–563	Bits 564–1023
Sample	Bits Used in	Bits not Used	Bits Used in	Bits not Used due
Header	Evaluation	due to Fixed	Evaluation	to exceeding
		Block Masking		Input Length

Example of Flexible Masking (Blocks)

[0067] Table G shows a setup where two, of a possible four, 32 bit flexible masking blocks are enabled. These blocks can be setup to fall on any valid 32 bit boundaries after the start of the header. In the example, the first flexible masking block #1 is setup to range from bits 96–127, which lies on a 32 bit boundary. The second flexible masking block #2 is setup to range from bits 352–383, which again lies on a 32-bit boundary. As an example, flexible masking is comparable to ignoring the destination city and street selectively for the recipient of a piece of mail in a rough check, and then looking at these only if the letter was sent using Next Day Air delivery.

[0068]

TABLE G
Example of 2 Flexible Masking Blocks
	Bit Number
	Bits 0–95	Bits 96–127	Bits 128–351	Bits 352–383	Bits 384–703	Bits 704–1023
Sample	Bits Used	Flexible	Bits Used	Flexible	Bits Used	Bits not Used
Header	in	Masking	in	Masking	in	due to
	Evaluation	Block #1	Evaluation	Block #2	Evaluation	exceeding
						Input Length

Example of Flexible Masking (sub-Block)

[0069] Table H below shows bits 96–101 from flexible masking block #1 in Table G above. These five bits are shown to illustrate how the system permits bit level masking flexibility for any bit in a flexible masking block. To account for different possible masking configurations based upon the network protocols, addresses or fields that are received in the header, the presently preferred embodiment of the system provides eight selective masking patterns for each flexible masking block. The eight selective masking patterns are illustrated in Table H. In the case of selective masking pattern #1, bits 96, 98, 99, and 100 are masked (=1), while bits 97 and 101 are not masked (=0).

[0070]

TABLE H
Selective Masking Patterns for Flexible Masking Bits
(sub-Block)
	Bit 96	Bit 97	Bit 98	Bit 99	Bit 100	Bit 101
Selective	1	0	1	1	1	0
Masking
Pattern
#1
Selective	0	0	0	1	1	1
Masking
Pattern
#2
.
.
.
Selective	1	1	1	1	1	0
Masking
Pattern
#8

System Benefits

[0071] The system provides a range of performance, cost, power, and size benefits. The following are some of the key benefits provided by the herein disclosed system:

• • [0072] Extremely Fast and Flexible Packet Classification—The system exceeds the speed of content addressable memory systems in packet processing. It permits extremely deep processing of bits in the packet header without impacting classification speed. When compared to custom solutions, the system provides deeper and more flexible processing at comparable throughputs.
  • [0073] Unparalleled Search Latency—The system starts classifying a packet immediately after the last bit has been received. There is no overhead in performing data transfers to memory or to custom ASICs. This opens up new optical routing and switch architectures for ultra high performance.
  • [0074] Low System Power Consumption—After the initialization process, the system has much lower power consumption than CAM or ASIC alternatives.
  • [0075] Flexible and Programmable Masking—The system provides both fixed block and flexible masking. The flexible masking can be pre-programmed to go through sequential operations without external intervention. This feature is a significant advantage vis-à-vis content addressable memory approaches.
    System Theoretical Background

[0076] The system uses a technique of adaptive, programmable, predictive, and sequential randomization to permit extremely rapid differentiation between a limited number of serial data bits. Optical networking relies on high speed transmission of digital data packets in a serial format. Optical routers and switches require that these serial packets be analyzed to determine the appropriate source and destination of the data packet so that they can be properly forwarded and at the correct priority level. All known present systems of packet analysis require serial data packets to be translated into a parallel format and then analyzed through the help of a combination of network processors, content addressable memories, custom ASICs, and high speed memories.

[0077] The randomization in the ASIC portion of the herein disclosed system is performed using compact, programmable feedback shift registers that are driven by the serial data stream. A general description as to how these programmable feedback shift registers are used in the system is provided below. The final state of these shift registers is used as an index into a memory array to determine which if any input data pattern has been matched. These shift registers require a simple register with exclusive OR feedback taps that can be programmed to be enabled or disabled. They have been designed to minimize power consumption, and the feedback tap enabling or disabling does not have an affect on the propagation delay of the feedback mechanism. The feedback mechanism has been kept simple, and minimal in terms of gate delays, to permit operation at extremely high serial data rates. More importantly, the various programmable feedback paths that are possible in the herein disclosed architecture have been selected specifically to guarantee that output values from one feedback value are uncorrelated to output values from another feedback value. This uncorrelated feature permits general probability theory to be used to evaluate the randomization of the data.

[0078] The predictive nature of the randomization comes from the fact that the randomization is pre-calculated for each possible input data pattern. This pre-calculation is done at the time that a new input data pattern is entered into the system for use. A critical feature of the system is that it implements a full hardware calculation of expected randomization outputs for each input that is applied. This hardware implementation allows many randomizer feedback values to be evaluated in real-time when a new input is applied. These randomizer output values are stored in memory for each randomizer feedback that is being considered at the time.

[0079] The adaptive randomization results from the system adjusting the randomization, over time, to handle the changing input data patterns that are to be analyzed in the best fashion. The high speed predictive nature of the system permits a significant number of possible randomization feedback paths to be maintained in memory at any time. The system can adjust the possible randomization feedback value after any packet has been received. This is done if the existing feedback randomization is significantly less ideal than another feedback randomization that has been evaluated. The system maintains statistics on all presently evaluated feedback randomization to determine the best randomization, as well as any randomization that may be no longer usable. When a randomization is no longer usable, the system can quickly bring all of the input data patterns back to evaluate other possible randomization patterns.

[0080] The sequential randomization that is permitted in the system results from the ability for the user to implement sequential masking operations on the input data. The system permits fixed or programmable masking of selected bit patterns within an input serial data stream. The masking operations of the system permit the user to pre-program a series of masking decisions that can result in a final input data pattern match.

Theoretical Randomization Probabilities

[0081] Detailed probability analysis is critical to an understanding of the system. The success of having a usable feedback randomization pattern, for a random set of inputs, depends upon the effective mapping of the input data patterns to output vectors by the randomizer. For practical implementations, with significant numbers of input vectors and reasonable sized memories, a system must be able to handle a limited number of cases where two or more input data patterns are mapped to the same output value. In the presently preferred embodiment of the system this is handled through a variety of methods including permitting a set value of multiple output cases where two, three, or four input data patterns map to the same output pattern. In addition, a secondary randomizer is used to separate between the multiple outputs so that the appropriate input can be determined.

[0082] The detailed theory behind evaluating any given randomizer pattern is presented below. This theory has been done in terms of the number of possible output states that are generated by the randomizer, and the number of possible input vectors that are being differentiated. The length of the input data patterns affects the predictive evaluation of the randomization outputs in hardware by the system, but it does not have a first order affect on the randomization probabilities. One part of the discussion below develops the theory to show the odds that a randomizer produces a specific case of a certain number of non-paired outputs, paired outputs, tripled outputs, or quadrupled outputs for a certain number of input data patterns. Another part of the discussion below evaluates how permitting various numbers of multiple outputs affects the possibility that a certain randomizer feedback is usable. For purpose of this discussion, unusable randomizer feedback occur when too many input data patterns map to the same output, or when as a group, there are too many sets of input data patterns that map to different but common outputs. As an example, if 4000 input data patterns mapped to 2000 different outputs where there were two input data patterns for each output, and the system permitted only 1000 multiple outputs, the randomizer feedback is unusable.

Primary Randomizer Feedback Selection Probabilities

[0083] The primary randomizer in the system is used to perform the mapping of each input data pattern to an output value. Given a number of input data patterns, there are always certain randomizer feedback values that are unusable. The system has been designed to make sure that enough randomizer feedback are simultaneously evaluated so that a usable feedback is always available. For purposes of evaluation, the system evaluates the number of paired, tripled, and quadrupled output vectors in determining which randomizer feedback to use, as well as to determine when a randomizer feedback should be discarded.

[0084] For a given number of output states, a given number of input data patterns, and a given number of multiple outputs, it is possible to determine the probability that any specific randomizer feedback maps the input data patterns into a usable set of output states. The analysis below uses a total of 10000 input data patterns, 65536 (2^16) possible output states, and 1024 (2^10) possible multiple outputs. For this scenario, it can be calculated that any possible randomizer feedback has an 95% chance of producing a usable mapping of the input data patterns. By using a set of eight possible randomizer feedback, the odds of having a usuable mapping are 99.9999999961%.

[0085] The presently preferred embodiment of the system can use a total of 128 (2^7) possible randomizer feedback. When one or more of the eight randomizer feedback whose mapping has been evaluated becomes unusable, the system can use one of the remaining (128−8)=120 randomizer feedback. It should be noted, that from a practical standpoint, new feedback paths can be swapped in while the input data patterns are loaded into the system.

Secondary Randomizer Feedback Selection Probabilities

[0086] The secondary randomizer differentiates between input data patterns that have been mapped to the same output value. The calculations for the odds of having a usable secondary randomizer feedback value are shown below. The probability analysis for this operation is much different than for the primary randomizer because, in this case, it is only necessary to be sure that the entries in each multiple are different from each other.

Randomizer Scaling for Additional Inputs

[0087] If the user wants to support additional inputs using the system, it is possible to scale up the size of the randomizers to achieve functionality. If the number of inputs were scaled to 40,000 input data patterns, the number of outputs could be increased to 262,144 outputs, and the number of multiple outputs could be increased to 4096. This would require an increase in the length of the primary and secondary randomizers to 18 bits in length. In addition, the memory requirements for storing the randomizer feedback mappings would increase by a factor of four.

System Overview

[0088] The primary method of operation for the system is used for ultra-high speed packet classification of optical data that has been framed into a serial data stream. This method of operation is referred to herein as the serial mode of classification. The invention provides packet classification at the serial data stream level, as opposed to doing this after data has been put into a parallel format and transferred into a network processor system. This feature of the invention allows the system to produce extremely fast characterization in a predictable timeframe that exceed anything done in a traditional parallel form such as the example previously shown of a CAM based system. The serial mode of classification requires modifications to a standard data framer part in addition to the other components that make up the system.

[0089] A secondary method of operation for the system provides fast packet classification of data packets that have already been stored in memory as successive parallel words of data. This method of operation is referred to herein as the parallel mode of classification. The purpose of this method of operation is to provide a legacy mode of operation that can support on or more ports that may or may not have modified data framers supporting the system. A design in which all ports have modified data framers supporting the system does not require use of the parallel mode of classification.

[0090] For the primary mode of operation, the system incorporates unique features into a traditional optical data framer chip, and relies on a complex ASIC to permit the user to differentiate between thousands of different patterns at light speed. One reason for the general purpose system is to eliminate the need for costly and power consumptive content addressable memory systems, or customer pattern specific ASICs, to perform network packet classification. The system operates on a principle of adaptive programmable randomization to permit the differentiation between the input vectors to be made. The system can dramatically reduce the processing burden required by high-speed optical routers or switches.

[0091] FIG. 2a is a block schematic diagram that shows an optical router or switch 11 using the system. The modified data framer 22 that is used in the system is referred to as the novel data framer. The complex ASIC 25 that is used to control the adaptive programmable randomizer is referred to as the custom ASIC. In addition to these two parts, the system relies on a standard high speed SRAM 26 for internal processing, as well as a low speed DRAM 27 to store input patterns and other user values.

[0092] FIG. 2b is a block schematic diagram that shows an optical router or switch using the system in which the parallel mode of classification is used.

[0093] The presently preferred implementation of the herein disclosed architecture supports identification of up to 10,000 distinct input vectors that can be up to 1024 bits in length. Both the number of vectors and length of each vector can be modified should the situation require. Increasing the number of vectors beyond 10,000 would require increasing the length of the programmable randomizers and the width of the SRAM memory used by the custom ASIC. Increasing the length of the inputs results in a fairly linear increase in the overall size of the custom ASIC and would require slight modifications to the data framer ASIC.

Novel Data Framer

[0094] The novel data framer modifications are made to the serial data stream of a standard data framer chip. If a descrambling function is done, it is important that the data framer modifications be done after the descrambling function. The serial data stream must be the same as the parallel data that is going to be passed to the network processor. It is also important that the data framer be able to access the data framer outputs that byte align the start of the packet, as well as count the number of bytes received.

[0095] FIG. 3 is a block diagram that shows the novel data framer. The modifications to a standard data framer start with a primary and secondary randomizer, 31, 32 respectively, that are programmably configured by the custom ASIC. The PRIMFB[14:0] and SECFB[14:0] registers in the data framer are used to setup the feedback configurations for the randomizers, and it is important that they be modified only after the reception of a packet has been completed. These two randomizers are preferably compact circuits that operate at the full serial data rate. They should preferably operate at 40 Gbit/sec serial data rates and beyond.

[0096] The next change to a standard data framer part involves the addition of a randomizer enable control block 33. The clock to the primary and secondary randomizers are gated ON and OFF by the enable randomizer signal that is generated by this block. The enable randomizer signal is turned on at the start of a packet.

[0097] An optional implementation allows the data to the randomizers to be programmably turned OFF (Set to a 0) and then turned ON again to allow blanking out a portion of every packet received. This is done with the gate randomizer signal. The implementation shown in FIG. 3 allows a single block of bits to be blanked out, but this could be extended to multiple blanking periods should the application warrant this change. Finally, the enable randomizer signal is turned OFF after a user prescribed number of bits has been received. The system has been nominally designed to handle up to 1024 bits, but with modifications to the custom ASIC and the data framer it could be easily extended to a larger number of bits should the application warrant.

[0098] The optional masking control block 34 in the data framer allows programmable, sequential, user controlled masking of groups of user defined bits. The implementation that is shown allows four different 32-bit wide blocks of data to be captured for masking purposes. The user is able to configure with MASK0_START[4:0] to MASK3_START[4:0] four starting locations for 32-bit words to be sampled. The masking control block takes these four START values, in addition to the BIT_COUNT[9:0] register which is a count of the number of bits from the start of the packet, to determine when to sample the MASKING data.

[0099] The PAR_DATA[31:0] is parallel data from the serial to parallel converter 35 which is implemented within any data framer. This PAR_DATA[31:0] is sampled at the appropriate times to generate MASK0DATA[31:0] to MASK3DATA[31:0] which are four 32-bit wide masking registers that are associated with the packet, and can be read by the custom ASIC when they become available. The number of MASK registers can be modified with changes to the data framer as well as the custom ASIC should an application warrant this being done.

[0100] The output register synchronization and queue 36 assures that the primary randomizer, secondary randomizer, feedback registers, and MASKING registers are stored for each packet. If a queue of packets is implemented in the data framer, then these registers must be similarly queued so that they are associated with the appropriate data packets. Ideally, these registers should be available to the custom ASIC as soon as the number of bits identified by the STOP register are received, so that they can be used to determine the appropriate input pattern match.

Primary and Secondary Randomizers

[0101] The primary and secondary randomizers are two equivalent circuits, and are designed so that their physical layout can be done so as to minimize gate propagation delays and hence to permit extremely fast operating speeds. These randomizers are expected to easily operate at 10 Gbits/sec, and as technology improves in the coming years, the step up to 40 Gbit/sec should be possible.

[0102] The randomizers for the system are sixteen bits in length. They are constructed using sixteen stages of D Flip/Flops in a serial shift register as shown in FIGS. 8a and 8b. The clocking of the serial shift register is qualified, and is done to all stages simultaneously. The Clock is gated with an Enable signal during the time periods between the start and end of a packet where a bit is to be clocked into the randomizers. During periods within the packet reception where the MASK ON/OFF functions is to be performed, the Clock to the randomizers is gated off. During periods within the packet reception where programmable mask bits are being captured, the Clock to the randomizers remains gated on.

[0103] A global Clear signal is also applied to the randomizers. This signal is used to initialize the randomizers to a known all 0's state between packet receptions. The Clear signal is not time critical so long as it is applied after the randomizer values have been latched, and prior to the start of reception of the next data packet.

[0104] The feedback for the randomizers is structured as an XOR tree that potentially sums up all sixteen of the serial shift register bits and adds them to the Input data bit. For the case of a 16-bit randomizer, this translates to five levels of exclusive-or logic. The randomizer feedback are turned on and off with the PRIMFB[14:0] and SECFB[14:0] registers. The last shift register bit is always applied to the feedback network, and hence the reason that there are only fifteen feedback selection bits. Each feedback bit is used to gate the output of its corresponding serial shift register stage using a two input AND gate. The PRIMFB[14:0] and SECFB[14:0] registers should only be written to between receptions of data packets. Changing these values does not affect the actual primary randomizer or secondary randomizer outputs if it is done while the randomizer clocks are gated off.

Enable and ON/OFF Circuitry

[0105] A key addition to a standard data framer is the generation of an Enable signal for the primary and secondary randomizers. At a minimum, this signal should enable the randomizers when a packet reception begins, and should disable the randomizers when a specified number of bits have been received. The optional ON/OFF circuitry in the custom ASIC handles gating off large blocks of data that are not desired to be analyzed, occurring in the middle of data fields the user wants to analyze with the system. This could consist of cyclic redundancy checks or other fixed blocks of data in the received packet that are not pertinent to the packet classification process. The purpose of the ON/OFF circuitry is to provide greater flexibility for use of the variable MASKING bits.

[0106] FIG. 9 shows a block diagram for the Enable and ON/OFF circuitry. An enable state machine 90 is driven by inputs to turn the Enable signal ON or OFF. At the start of a packet, the Start of Packet signal from existing data framer circuitry is expected to go active, and the Bit Count is expected to be 0. This forces the Enable signal ON at the beginning of the packet. In a minimal configuration, when the Bit Count reaches the STOP value, the enable state machine turns the Enable signal OFF. A 10-bit comparator 91 is used to compare the status of the Bit Count value to the value stored in the STOP register 92, and when these two signals are equal, the END_EVAL signal is generated, followed by the Enable signal being turned OFF.

[0107] In the optional case where ON/OFF circuitry is implemented, additional registers and comparators are required. For each long blanking period that is desired, an additional two 10-bit registers 93, 94 are needed to store the ON and OFF bit periods. In addition, two 10-bit comparators 95, 96 are required to compare these ON and OFF values to the actual bit count. The outputs of all of the comparators drive the enable state machine. To increase the number of ON/OFF periods that are blanked requires additional logic and power consumption. The enable circuitry comparators are operating at the full clock rate of the system because they are driven by the bit count value.

Programmable Masking Circuitry

[0108] The ability to execute programmable masking in the data framer is entirely optional. In the world of content addressable memories, this feature is akin to a ternary CAM having three levels, i.e. one, zero, and don't care. The programmable masking circuitry permits blocks of data to be captured so that they can be programmably masked in the final output result. To reduce power consumption and chip area, the programmable mask registers have been defined to be on even 32-bit boundaries, and to be 32 bits in length. The size, boundary, and length of these registers could all be adjusted based on user requirements. The programmable masking circuitry performs a function similar to a logic analyzer, by capturing blocks of data at the appropriate time, and then permitting them to be analyzed in the future in the custom ASIC.

[0109] In the implementation shown in FIG. 10, there are four masking start registers labeled: Mask_Start0 100, Mask_Start1 101, Mask_Start2 102, and Mask_Start3 (not shown). Because the total possible length of the data pattern being evaluated is 1024 bits, and the Mask_Start registers are intended to be on 32-bit boundaries, there are a total of 32 possible values for each mask start register. These 32 values can be stored in a 5-bit number, and hence the Mask_Start registers are 5-bit values. This reduces the comparison with the previously mentioned Bit Count register to only the upper five bits. The lower five bits of the Bit Count register are compared with 0 because the value must be on a 32-bit boundary.

[0110] The masking data are captured in a set of 32-bit registers labeled MASKDATA0 103, MASKDATA1 104, MASKDATA2 105, and MASKDATA3 (not shown). These registers are clocked when the Bit Count equals the value stored in the respective Mask_Start register. The data input to the MASKDATA registers is from the serial to parallel data converter that exists in a standard data framer part. Once masking data are captured, they must be read from the output registers prior to the next packet being received.

Output Register Synchronization and Queue

[0111] It is critical that the primary and secondary randomizer values be synchronized to the feedback values that were used in determining them (see FIG. 11). The other registers in the system including the Mask_Start, ON/OFF, etc. are not expected to be changed after initialization. If this is desired, then these need to be captured and stored with the primary and secondary randomizer values, and the received packet, so that they are correlated. It is the responsibility of the data framer to keep the randomizer values and associated feedback values with the correct received packets.

Custom ASIC Implementation

[0112] FIG. 4 is a block schematic diagram that shows the custom ASIC. The custom ASIC contains the intelligence, algorithms, and adaptive functionality for the system. The custom ASIC is responsible for maintaining multiple input pattern mappings associated with different primary and secondary randomizer equations. It determines the best randomizer selection, and decides when to switch randomizer values. The custom ASIC must also determine when a randomizer value is no longer useful, and an entirely new mapping should be generated.

[0113] The preferred embodiment of the custom ASIC has four primary interfaces to the outside world, i.e. the microprocessor interface 41 is used to communicate to a host processor system, the DRAM interface 42 is used to communicate with either a standalone DRAM or shared dual port DRAM for storing data patterns to be matched, the SRAM interface 43 is used to communicate with a dedicated SRAM that contains mappings for various primary and secondary randomizer settings, and the interface 44 is used to communicate with the modified data framer part. Internally, the custom ASIC handles mapping user inputs into values that are stored in SRAM. Individual masking and mapping optimization functions are performed internal to the ASIC.

[0114] The following discussion views the custom ASIC from a data flow perspective:

[0115] For the custom ASIC to start it's process, the user is required to make various pointer and register configurations (see below). Next, the user must load input patterns into the custom ASIC. These patterns are made up of a combination of data and, in some cases, masking steps that should be done on the data in a potentially sequential fashion. For instance, the custom ASIC permits mapping a range of data values to a single mask step output, and when that mask step output is reached, additional programmable masking or verification can be executed. Input patterns are handled by the input manager control and state machines function 45 where they are directed into the input register 46. They are also loaded into external DRAM for use in cases where an equation mapping is discarded, and a new mapping must be generated from scratch. The input register is 1024 bits long to permit patterns up to 1024 bits to be analyzed. This length could be adjusted up or down in embodiments, and would not affect the data framer ASIC. Input data are manipulated in 32-bit words, and masking is permitted for 32-bit lengths on 32-bit word boundaries. Masking information is stored in conjunction with the input data so that an entire input pattern can be regenerated should new equation mappings need to be generated.

[0116] When the 1024 bit input register contains a complete data pattern, and when all masking information is loaded in the masking and enabling logic section 47, it is possible to use the 1024 equation mapper 48 to generate a related randomizer value. The masking and enabling logic 47 is responsible for enabling only those input register bits that the user is interested in examining. For instance, if the user is interested in reviewing only the first 200 bits of an incoming data packet, the last 824 bits are blanked out by the masking and enabling logic, and are not sent into the primary and secondary randomizers in the data framer. The masking function of the masking and enabling logic allows data bits within the input pattern to always be masked out and not analyzed, as well as permits bits to be masked selectively in a user programmable sequence.

[0117] The equation mapper 48 permits a randomizer value to be calculated in a single cycle. This is done by implementing the mapper in pure logic gates in hardware. It calculates randomizer mappings for 128 different equations simultaneously to permit extremely fast calculations and data storage of randomizer values generated by different randomizer equations. This feature permits the custom ASIC to adjust adaptively to select optimal randomizer settings based on the input and masking patterns that have been applied to the part. It allows many randomizer mappings to be stored at one time without adversely affecting the setup time for the part, and makes the action of generating entirely new mappings possible in the case where some of the mappings stored on the custom ASIC are no longer usable due to excessive randomizer output duplication.

[0118] The mapper multiplexer 49 is implemented in hardware to allow immediate selection between each of the possible 128 randomizer outputs associated with each of the 128 possible randomizer equations. This function preferably consists of sixteen individual 128:1 multiplexers, where there is a multiplexer associated with each of the sixteen output bits of the randomizer. If the length of the randomizer is increased, the size of this multiplexer increases in a linear fashion with the number of bits in the randomizer output. The number of equations used in the equation mapper and the mapper multiplexer can be adjusted up or down with a direct impact on the number of gates used in their implementation.

[0119] The mapper storage control and storage state machine 54 is responsible for saving and retrieving values from the various equation mapping tables. The state machines in this block handle determining whether the present location pointed to by a primary randomizer value contains 0, 1, 2, 3, or 4 entries. This state machine is responsible for handling the creation and destruction of multiple entries, and the adjustment of the multiple entry tables that dictate those entries that are used. This function works directly with the external SRAM in storing and retrieving these values. This function works closely with the masking engine, especially in those cases where mask steps are involved.

[0120] The masking engine 51 handles all aspects of permitting the user to setup sequential masking operations. This function takes user inputs that setup which, if any, 32-bit blocks of data are operated on in a masking fashion. The user is permitted to signify data bits as always being masked, or as selectively being masked when certain circumstances arise. Once the masking engine knows what bits may be masked, it is responsible for calculating the effect of each bit on the output vector. These effects are referred to as masking impact bits. To execute this operation, the masking engine injects a single “1” into the input vector stream at each bits location. The output primary randomizer value shows the impact of this input on the output vector. This value is then used by the masking engine, along with the masking data that is received from the data framer ASIC, to remove the effects of the masked data when a packet is received. The masking functions used in the system are described in greater detail below.

[0121] The time accelerator 52 is responsible for re-mapping a received randomizer value to generate the randomizer value that would have been received if zero values had been clocked into the randomizer for a fixed number of cycles after the received randomizer value was captured. This function is described below, and permits a flexible and fast way to skip forward to the end of the 1024 input bits that are always used to calculate randomizer values. As an example, if the user wishes to analyze only 200 bits of data, while the novel custom ASIC always calculates using an input vector length of 1024 bits, the time accelerator block generates the effect of having 824 trailing 0's shifted into the randomizer after the data of interest. This method reduces time latency, and permits the randomizers to be turned off much sooner to reduce power consumption.

[0122] The mapper engine, statistics and state machine 50 is responsible for determining the equations to be used by the system, and to determine when equations are no longer usable and need to be replaced. This function maintains statistics on all equation mappings that are maintained in memory. Using these statistics, it selects the best mapping and sends it to the data framer ASIC.

[0123] The master control block 53 is responsible for initializing the entire system at startup. It also handles communicating with other control blocks to execute system wide functions such as a hard reset.

SRAM Memory

[0124] Dedicated SRAM is required for the custom ASIC. The size of the SRAM memory is dictated by the size of the primary randomizer/secondary randomizer words, and the number of equations that are permitted. The speed of the SRAM is critical because it sets the performance of the system. As an example, a 16-bit primary randomizer value, in conjunction with a 16 bit secondary randomizer value, dictates that the core of the primary randomizer lookup table be 2*2^16=131,072 entries long and sixteen bits wide. In addition, a multiple entry table of 1024 entries contains slightly more than 8,096 locations that are sixteen bits wide. In this example, it takes a total of approximately 140,000×16 bits of SRAM storage per equation. A 512K×16 SRAM handles approximately three and one-half equations worth of data.

DRAM Memory

[0125] A dual port DRAM could be used for the DRAM required in the system. The lowest cost configuration is a synchronous DRAM. The fact that the custom ASIC is the only device talking to the DRAM, unless a dual port approach is used, permits a purely synchronous approach to be simply implemented. The speed of the DRAM memory directly impacts how fast new input vectors can be stored in the system. The microprocessor interface to the ASIC is a 32-bit interface. If the DRAM is sixteen bits wide, then it's interface must be twice as fast. Burst operation is very critical because an entire input could be stored away at one time.

System Benefits

Fastest Packet Processing Possible.

[0126] As soon as the last serial data bit that is under analysis has been received, the system's primary randomizer, secondary randomizer and masking bit values are available from the data framer ASIC. These words can be read into the custom ASIC using high speed parallel 32 bit transfers (taking<5 nsec). Once these data are transferred to the novel custom ASIC, the time to match a pattern is a function of three variables, i.e. the number of masking operations that the user wants to perform, the speed of the SRAM used by the custom ASIC, and the distribution of multiple outputs within the search that is performed.

[0127] Multiple outputs are distributed in a probabilistic fashion throughout the search process. The odds described below assume that there are up to 968 paired outputs, up to 50 tripled outputs, and up to six quadrupled outputs within a 10000 input data pattern space. In this scenario, the odds of a pair are less than 2*968/10000=19.4%, the odds of a triple are less than 3*50/10000=1.5%, and the odds of a quadruple are less than 4*6/10000=0.24%. These are extremely conservative bounds because, in the example, all of the probability distribution is for cases that are less than or equal to the 968 pair, 50 triple, and six quadruple scenario. When a pair, triple, or quadruple output is hit, the system uses the secondary randomizer value to differentiate between the different input data patterns.

[0128] The speed of the SRAM used by the custom ASIC dictates the time associated with sequential SRAM access to determine the appropriate input data pattern. In addition, each sequential masking step, excluding a fixed masking of bits which does not entail SRAM cycle overhead, results in an additional search through SRAM memory.

[0129] The search time for a pairs, triples, and quadruples is shown in Tables I–L below. Each of these tables lists the average and maximum time to complete a search.

[0130]

TABLE I
Time associated with Searching a Single Match
SRAM
Search
Step	Action	Probability of Step
1	Read primary randomizer Value	1.0
	(Contains Input)
2	Check secondary randomizer Value	1.0
	Average Search Steps	2.0
	Maximum Search Steps	2.0

[0131]

TABLE J
Time associated with Searching a Pair Match
SRAM
Search
Step	Action	Probability of Step
1	Read primary randomizer Value	1.0
	(Contains pointer to Multiple
	Structure)
2	Check First secondary randomizer	1.0
	Value in the Multiple Structure
3	Check Second secondary	0.5
	randomizer Value in the Multiple
	Structure
4	Read the input number for the	1.0
	correct secondary randomizer Value
	in the Multiple structure.
	Average Search Steps	3.5
	Maximum Search Steps	4.0

[0132]

TABLE K
Time associated with Searching a Triple Match
SRAM
Search
Step	Action	Probability of Step
1	Read primary randomizer Value	1.0
	(Contains pointer to Multiple
	Structure)
2	Check First secondary randomizer	1.0
	Value in the Multiple Structure
3	Check Second secondary	0.67
	randomizer Value in the Multiple
	Structure
4	Check Third secondary randomizer	0.33
	Value in the Multiple Structure
5	Read the input number for the	1.0
	correct secondary randomizer Value
	in the Pair structure.
	Average Search Steps	4.0
	Maximum Search Steps	5.0

[0133]

TABLE L
Time associated with Searching a quadruple Match
SRAM
Search
Step	Action	Probability of Step
1	Read primary randomizer Value	1.0
	(Contains pointer to Multiple
	Structure)
2	Check First secondary randomizer	1.0
	Value in the Multiple Structure
3	Check Second secondary	0.75
	randomizer Value in the Multiple
	Structure
4	Check Third secondary randomizer	0.50
	Value in the Multiple Structure
5	Check Fourth secondary randomizer	0.25
	Value in the Multiple Structure
6	Read the input number for the	1.0
	correct secondary randomizer Value
	in the Pair structure.
	Average Search Steps	4.5
	Maximum Search Steps	6.0

[0134] In calculating the average search steps per mask step, the previous probabilities for multiple outputs can be used.

[0135] The SRAM speed, could be increased to improve the overall search time. The flexible masking steps are an additional feature that require additional searches in CAM solutions. It should be remembered that there is no additional overhead for a fixed masking of data bits. The search time provided by this embodiment of the invention is approximately five times faster than comparable CAM implementations, and is on par with the search time of a hardwired ASIC2 approach by Juniper Networks. The highlights with this approach are that it is extremely deep in it's search, it is flexible in terms of allowing multiple masking operations, and it has the lowest latency of any solution.

Lowest Possible Search Latency

[0136] The system has the lowest possible packet search latency that is presently known. This occurs due to the fact that the system operates on a serial data stream prior to any parallel operations of transferring the data into memory. Alternative CAM or ASIC based systems must transfer all appropriate data bytes from a data framer into either a processor memory or directly into a CAM or ASIC solution for evaluation. The time required to perform this function adds latency to the packet through either a router or switch product. Reducing this latency helps guarantee that higher level protocols do not time out as packets are routed over an entire link.

[0137] The system can produce a guaranteed upper bound on the time required to evaluate a received packet after the packet is received. This deterministic delay could be useful in an alternative system where optical routing is performed using a detection system and an optical delay line.

[0138] FIG. 5 is a block schematic diagram that shows an embodiment of the invention in which an optical delay line 51 is used to make a decision as to where to route a packet prior to the packet arriving at the end of the delay line. Using this capability, an optical switch 52 directs the data into the correct path without having to store and regenerate the optical signal.

[0139] The optical router architecture shown in FIG. 5 has some clear advantages and limitations. Light traveling down the optical delay line takes longer than the combination of the system's packet search time and the time to have the optical switch actually switch and settle out. The network processor is much simpler because it's basic function is to configure the system, and to set the selection signals for the all optical switch. If the system could guarantee a packet routing decision in 50 nsec, and the all optical switch could switch and settle in 50 nsec, then the optical delay line would have to be 100 nsec long. This would entail using over 100 feet of optical fiber within the router for each input that was to be sampled.

[0140] In addition to the physical challenges of the delay line, the signal protocol issues would have to be developed. All optical switches being developed today setup a connection and leave it there for a long period of time. This means that their switching time is not critical, and the connection is bi-directional.

Lower System Power Consumption

[0141] Power consumption is a critical parameter on line cards and in other networking gear. Reducing power consumption can have a ripple effect on overall system costs, and can also provide more degrees of freedom for the board and system designer. The system has been designed to take the most processing intensive burden away from the network processor. This permits designers to react by reducing clock speeds or decreasing memory bandwidths and achieve equivalent performance. Either of these choices reduces power consumption and cost.

[0142] The system has been designed for minimal power consumption. The data framer primary and secondary randomizers operate at full clock speeds, but are only driven during the portion of a receive data packet that is being evaluated. The design of these randomizers minimizes their power consumption. The remainder of the data framer consists of configuration or sampling registers that are read or written only once per packet, and hence draw very little power.

[0143] As with the data framer, the custom ASIC has also been designed for minimum power consumption. The custom ASIC and associated memory system are very active during configuration and draw higher power levels at that time. Once configuration is complete, the custom ASIC is fairly static. It executes SRAM cycles when primary and secondary randomizer words are read from the data framer, but these are limited in duration. Otherwise, the custom ASIC operates with little dynamic power consumption. In contrast to the system, both a prior art custom ASIC and a CAM system require extensive power consumption while they are active.

Flexible and Programmable Masking on the Fly.

[0144] Typical CAM based search engines permit global masking and bit specific masking of any bit in the data pattern. Generally, there are a limited number of bit patterns where this capability is required. The flexible and pre-programmable masking sequences that the system permits, offload additional processing work from the network processor. Based on the type of packet being received, the system can process the packet with different sequential masking operations.

Using the System on a Router Backbone

[0145] In the interest of cost savings, the system permits multiple data framers to be operated from a single custom ASIC. Many systems, such as the Juniper ASIC2 and prior art CAM based systems, can operate with the packet classification processing done on a network router backbone as opposed to on each channel. In the system, each input channel requires a data framer ASIC, but a performance tradeoff allows a single custom ASIC to be used for N data framers.

[0146] FIG. 6 is a block schematic diagram that shows the system on a router backbone 60. The use of the system in the router backbone configuration does not have the latency improvement benefits of the implementation on each optical channel. In this configuration the system competes with large CAM based processing systems, and with Juniper Networks ASIC2 solution. The system is faster than the CAM based alternatives, and is at least as fast as the ASIC2 solution. It is also possible to use multiple custom ASICs to increase aggregate processing power in terms of packets/second.

[0147] In terms of implementation, the data framer interfaces are preferably all in parallel so that a single custom ASIC 25a could write to each data framer 22 at once. This entails setting up the randomizer feedback values. The randomizer outputs, masking registers, and feedback values used to analyze each packet are added on to each received packet. These packets are sent through each network processor 61 onto the router backbone. On the router backbone, a main router processor 62 is responsible for queuing the packets, stripping the data off and routing it into the custom ASIC, and using the custom ASIC outputs to determine how to route the packet.

Unsynchronized Data Pattern Extraction Capability

[0148] The architecture of the system provides a unique opportunity to perform ultra-high speed searching for many unsynchronized data patterns in a stream of high speed serial data. By the term unsynchronized data pattern, what is meant is a data pattern where the start of the pattern is not known, and the pattern is embedded in a stream of data. In the case of searching a data stream for specific text or other patterns, the system allows up to 10000 patterns of up to 1024 bits to be searched simultaneously in a rapid fashion. In the future of genetic research, if it was possible to take a sample of genetic information, and break it down into it's sequences while doing this in a brute force fashion on all chromosomes simultaneously, the following based approach would permit all of the genetic data to be scanned rapidly for matches with up to 10000 genetic sequences. In this way, an extremely rapid analysis of a genetic fingerprint for an individual could be made. Each base in a DNA strand can be represented with two bits of data, so the ASIC could find strands that are up to 512 bases in length. The length could be increased beyond 512 bases with a simple redesign to the novel custom ASIC.

[0149] The system for scanning random data for a match can be implemented using multiple novel style circuits as shown in FIG. 7. The total number of novel circuits 22a is equal to the number of bits that are to be analyzed in the receive data stream. An additional N bit counter 71 is used for two purposes, i.e. to generate a “Start of Pattern” signal, and to be used to select the appropriate novel circuitry output using a multiplexer 72. The “Start of Pattern” signal is shifted in one clock cycle increments so that each novel circuit begins checking the pattern at a position 1 bit shifted from the previous novel circuit. This offset means that regardless of where the start of the actual data pattern lies in the receive data stream, one of the novel circuits starts the primary and secondary randomizers on the first bit of the data pattern.

[0150] The single bit offset between novel data framers also means that one of the data framers produces an output each bit period. The n:1 multiplexer routes the correct data framer output to the novel custom ASIC 25 during each bit period. During this time, the primary and secondary randomizer outputs and any masking outputs must be transferred into the novel custom ASIC and used there. The serial speed of this system is limited by the search time of the system. The current worst case pattern match takes six SRAM cycles for the case of a quadruple output match. Using a worst case of 50 nsec for a match, the serial data rate can be up to 20 Mbits/sec if only fixed masking operations are used. A serial data rate of 20 Mbits/sec allows the data framer ASIC circuitry to be implemented easily in silicon.

[0151] One issue that affects the asynchronous data stream much more than the optical networking situation is the case of false detection. If sixteen bit primary and secondary randomizers are used, there is a one in 65,536 chance that a valid primary randomizer number has random data generate a matching secondary randomizer value. There are a variety of ways in which this can be handled. A first method is to check the data always to make sure that it was a match; a second method is to increase the size of the memory and hence reduce the odds of both valid primary and secondary values; and a third method is to use an offset pattern check to make sure that two successive readings point to the same value. The offset pattern check can be used if less than ¼ of the possible data patterns are being searched. In this case, the length of the search pattern can be increased by one bit. Every desired pattern is prepended by 0, prepended by 1, appended by 0, and appended by 1 to generate four new patterns that are each one bit longer than the desired pattern. When the system receives a match for a specific data pattern, there must always be a match for the very same specific data pattern on the very next bit period. If this does not occur, there was a false detection. This approach decreases the odds of a false detection by a factor of four billion (2^16)2^.

[0152] Another issue that could arise in searching the genome is the fact that input data patterns are of various lengths based on the gene. This requires there to be additional masking registers to permit a wide range in data lengths. As an example, if strands of 26, 52, 64, 78, 84, 100, 160, 220, and 330 bits in length were to be checked, the masking would have to be done sequentially, and would reduce the overall throughput. All strands would be verified for the first 26 bits, and the result would direct towards measuring the next (52−26)=26 bits for all cases that were not the 26 bit strand. At that point, the (52−26)=26 bits would be verified, and the result would direct towards measuring the next (64−52)=12 bits for those cases that were not the 52 bit strand. This would extend on until all the steps were taken.

[0153] Normally, if ten masking steps were used, the throughput of the system would be reduced by a factor of ten, but the throughput reduction could be greatly minimized through a variety of methods. In the case of genetic pattern matching, the frequency of cases where more than one mask step would be taken is extremely small, and usually would occur only if a valid pattern was correctly bit aligned. As a result, the system must handle extremely rare cases where multiple masking steps may be taken. This could be done efficiently by using a FIFO (first in first out) buffer in front of the novel custom ASIC to buffer the incoming randomizer values to handle the multiple masking cases, or by shutting off the serial data clock until a check has been completed. The important criteria here is that the most efficient searches occur when all of the data patterns to be checked are of the same length.

[0154] The novel data system opens up exciting opportunities in the arena of data mining and pattern matching. Table M identifies the time that this sort of an asynchronous data pattern detection system would take to search through the entire Human Genome. Printed text is not a good example of an asynchronous data stream because it is already framed at the character level, and can be easily translated to be framed at the word and/or sentence level.

[0155]

TABLE M
Asynchronous data Search Times using Novel System
Item	Search Time	Notes
Entire Human Genome	300 seconds	This is a futuristic concept
with no marker framing	(5 Minutes)	that relies on base pair
(3 Billion base pairs)		sequencing without regard
		to markers.
		Each Base Pair is 2 bits
		of information, and all
		elements being searched
		are the same length.

Features of the System
Highly Specialized Programmable randomizer in a Serial Data Path

[0156] The programmable randomizer in the system is unique in a number of ways ranging from the method of programmability, the random nature of it's outputs, the simplicity of making predictive calculations as to it's value over a long stream of inputs, and the ease of predicting the affects of any specific input on the output state to effect rapid masking calculations.

[0157] Linear feedback shift registers have been used for decades in a variety of applications including cyclical redundancy check generators (CRCs), pseudo random bit sequence generators (PRBSs), and data scramblers. In most of the known applications, the feedback taps on these shift registers are selected at the point of design to maximize their randomization features. The pseudo random bit sequence generator and data scrambler applications use a linear feedback shift register to produce a serial data pattern that is as random as possible. The cyclical redundancy check generators operate on a serial data stream, and produce a parallel word at the completion of reception that is used to verify that the correct data stream has been received. In this respect, the system's use of a linear feedback shift register is similar to the application of a cyclical redundancy check generator.

[0158] The system differs dramatically from a CRC generator in the respect that it has programmable taps that allow 2^(n−1) different programmable feedback to be selected instead of a single fixed feedback. The “n−1” term arises because the final “nth” stage of the shift register must always be fedback in the preferred implementation. Further, the feedback are setup to exclusively-or the serial data with any combination of (n−1) shift register stages. The exclusive-or feedback allows a fixed tree of exclusive or gates to be used to exclusively-or all of the selected feedback outputs. Each output is gated with an “and” gate to control programmably whether or not it is used by the exclusive-or tree. A key feature of this approach is that it is extremely compact and easy to program. This dramatically reduces die size and power consumption because the circuitry is meant to operate at extremely high serial data rates, and the more logic that is toggling at these data rates, the more power that is consumed.

[0159] A purpose of the randomizers is to differentiate between input data patterns, and not to provide the most random possible pattern. What is more critical, is that each input affects outputs differently when switching between various feedback mechanisms. This orthogonality between how different outputs are impacted by each input, through a range of equation feedback, permits general random probability theory to be used in calculating output distributions.

[0160] The design and choice of the randomizer is critical to the ability to predict quickly in hardware the mapping from an input data stream to an output randomizer value. The sole use of exclusive-or gates in the feedback mechanism, as opposed to other forms of logic such as “AND,” “NAND,” “OR,” or “NOR” gates greatly simplifies the predictive ability in hardware. In addition, the use of exclusive-or gates makes it possible to single out each individual input, and identify it's effect on each bit of the output pattern. This feature is critical for permitting simple masking to be performed. Finally, this approach is critical to permitting variable length packets to be easily analyzed. This is possible by the fact that any bit that is beyond the length of data to be evaluated, can be forced to a 0 in the analysis hardware tree, and the bit is effectively eliminated.

Single Cycle Hardware Calculation of Randomizer Values

[0161] The system operates on the ability to pick the best feedback mechanism for mapping input data patterns into output vectors in a rapid fashion. This requires that the system must be able to calculate output vectors in an extremely rapid fashion for a number of feedback selections. The system uses a hardware tree of exclusive-or gates to calculate output vectors for a large number of feedback selections (nominally 1000 feedback selections) in a single clock cycle. This is possible to implement by analyzing the effects of each and every input bit on the output pattern using a computer program in advance. Once these computer mappings are performed, they can be merged together for all of the possible feedback so that as many logic gates as possible are re-used. Finally, an output multiplexer allows the appropriate output vector to be selected for the feedback mechanism that is being evaluated.

Randomizer Gating Implementation

[0162] The primary and secondary randomizers in the system are gated on and off for three specific reasons, i.e. at the initiation of reception of a data packet they are turned on, at the completion of the reception of the data bits of interest they are turned off, and during any period in which the user always desires to blank out analysis of a sequence of data bits they are turned off and then back on at the end of the sequence. This ON/OFF gating of the randomizers, through user programmable control, is a unique feature to the system. This ON/OFF gating capability works in tandem with the single cycle hardware calculation of randomizers circuitry, where data bits during any “OFF” period are forced to a “0” from the perspective of randomizer calculations.

Programmable Masking Architecture

[0163] In CAM or ASIC implementations of packet classification systems, data bits can be masked off by essentially not considering them in a bit by bit comparison. The masking capability in the system is very unique. Instead of the traditional approach of blanking out or ignoring a data bit to mask it, the system calculates the effect of each data bit that the user desires to mask on the randomizer outputs, captures the actual masked data bits, and then effectively subtracts the masked data bits out of the randomizer output result using specialized hardware. The data framer incorporates the circuitry to capture the masked data bits, and the custom ASIC incorporates extensive circuitry to calculate the effects of each masked data bit on the output predictively, as well as the circuitry to subtract out the effects of the masked data bits.

Sequential Masking Capability

[0164] In addition to the ability to mask out data bits in a received packet stream, the system allows the user to setup programmed sequential masking of data bits where initial pattern matches can automatically drive subsequent masking operations without user intervention during the processing of the randomizer outputs. This sequential masking capability is normally done through processor intervention based on the outputs of various decisions. The system permits this decision driven masking to be setup proactively in advance of a packets reception. This reduces the overhead required of a network processor, and reduces the latency in making a routing decision.

Adaptive Randomizer Feedback Analysis and Selection

[0165] The architecture revolves around the ability to develop and maintain information regarding a number of randomizer feedback at any given instant in time, and to pick the best randomizer feedback adaptively using established criteria. The custom ASIC manages the memory (SRAM) tables associated with each feedback selections mappings. In addition, counters for the number of pairs, triples, quadruples, and overflow output vectors are maintained in hardware. These counters are used to identify the randomizer feedback that is least likely to need to be changed, as well as any randomizer feedback that are no longer viable. The evaluation and swapping of randomizer feedback is a real time and adaptive process based on the latest information as to the input data patterns being evaluated.

Input Manager Control and State Machines

[0166] In the preferred system, the user is allowed to provide up to 10000 different inputs that are up to 1024 bits long. This memory is a maximum of 10,240,000 bits of storage. The system returns a pointer to the data input that matches the incoming data stream. Therefore, the user should store the data in sequential locations. A single valid bit for each input is used to signify that the input data pattern is valid and should be used by the system. The external memory system is specified as using 32-bit wide memory. Therefore, it requires 32 memory accesses to read a maximum length data input. The user can write an input, and then activate that input by writing to it's associated valid bit.

External Memory Input Data and Input Valid Structures

[0167] The purpose of the external DRAM memory storage is to store input data patterns and masking information for potential future needs. If certain randomizer feedback must be eliminated due to excessive multiple structures or multiple structure overflows, it is necessary for the system to read all of the input data patterns back into the system from memory so that new patterns can be evaluated. Another reason for storing the input data is to permit users to read back any input data pattern that is being used in the custom ASIC system to evaluate the pattern, or to modify it to create another input data pattern.

[0168] The user can define the location in the external memory where the custom ASIC stores the input table. This table is called the INPUT_DATA array, and it's starting location is pointed to by the 32-bit pointer INPUT_DATA_BASE that is located on the custom ASIC. Thirty-two bits of width allows for an addressable memory size of 4.29 G.

[0169] The user must define the number of bits of data that each input data pattern contain, and this value is stored in INPUT_DATA_LENGTH that is located on the custom ASIC. This value can be in one bit increments, but from a storage perspective, input data patterns are stored in 32-bit words. Any data bits beyond this length value are masked out. In the case of an exclusive-or function, this is done by masking the input to a 0. For the custom ASIC, the maximum valid value is 1024 bits. In embodiments this value could be extended in length.

[0170] In addition to the input data pattern, the system must know what masking is required for the specified input. This information is referred to as the present masking step. Any bits in the pattern that are masked are ignored from the perspective of the stored input data pattern. If a masking step is performed after the present input data pattern with optional masking is evaluated, the next masking step must be specified. These two masking steps are stored after all of the input data pattern data words and are associated with the specific input data pattern (see Table N below).

[0171]

TABLE N
Storage of Input data Pattern and Mask Step Information
(Single INPUT_DATA entry)
	Bits 31:24	Bits 23:16	Bits 15:8	Bits 7:0
Data Word 0	Input Data	Input Data	Input Data	Input Data
	Pattern[31:24]	Pattern[23:16]	Pattern[15:8]	Pattern[7:0]
Data Word 1	Input Data	Input Data	Input Data	Input Data
	Pattern[63:56]	Pattern[55:48]	Pattern[47:40]	Pattern[39:32]
.	.	.	.	.
.	.	.	.	.
.	.	.	.	.
Data Word n	Input Data	Input Data	Input Data	Input Data
	Pattern	Pattern	Pattern	Pattern
	[(n*32)+31:	[(n*32)+23:	[(n*32)+15:	[(n*32)+7:
	(n*32)+24)]	(n*32)+16]	(n*32)+8]	(n*32)]
Masking	X	X	Next Mask Step	Present Mask Step
Word

[0172] The user must also signify which inputs are valid. This is done with the INPUT_VALID array, where a single bit is used to signify the validity of each user input. To conserve on data, this array is a 10000×1 bit array that can be accessed in 32-bit reads/writes. The first 32-bit location in the array signifies the status of inputs 0–31. The second 32 bit location in the array signifies the status of inputs 32–63, etc . . . Coverage of 10,000 Input data patterns requires a total of 313 32-bit words. The INPUT_VALID_BASE is used to indicate the location of the array that contains the valid status for each input location (see Table O below).

[0173]

TABLE O
Storage of Input Valid Information (Entire INPUT_VALID array)
	Bits 31:24	Bits 23:16	Bits 15:8	Bits 7:0
Input Valid	Input Valid [31:24]	Input Valid [23:16]	Input Valid	Input Valid
Word 0			[15:8]	[7:0]
Input Valid	Input Valid [63:56]	Input Valid [55:48]	Input Valid [47:40]	Input Valid [39:32]
Word 1
. . .	. . .	. . .	. . .	. . .
Input ValidWord 312			Input Valid[(n*32) + 15:(n*32) + 8]	Input Valid[(n*32) + 7:(n*32) + 8]

[0174] The shaded area includes valid entries for Inputs 10,000 to 10,015 which are unspecified.

[0175] The INPUT_DATA and INPUT_VALID information is all stored in external DRAM memory. Table P below describes the location of these arrays.

[0176]

TABLE P
External Memory Input Structures (Entire DRAM Storage)
	Length
Name	(in 32 Bit Words)	Starting Location	Notes
INPUT_VALID	313	INPUT_VALID_BASE	Each bit in this array
			signifies the validity of an
			input data pattern.
			Initialized as all zeros.
INPUT_DATA	330,000 (maximum)	INPUT_DATA_BASE	The Maximum size per
	20,000		input data pattern is 33 × 32
	(minimum)		bit words (1024 bits
			of Input data plus one
			Masking Word). The
			actual size will depend
			upon the
			INPUT_LENGTH. This
			array requires no
			initialization.

Registers Associated with Input Data Structures

[0177] The following registers are located on the custom ASIC, and are used to write and clear user input data patterns located in the external INPUT_DATA array. In addition, they are used to modify the INPUT_VALID array appropriately. The INPUT_DATA_BASE and INPUT_VALID_BASE registers store the base addresses of the external structures as described herein, and the INPUT_DATA_LENGTH register stores the length of each input as previously described. The INPUT_DATA_WORD_COUNT is used as a counter to point to the individual words in the INPUT_DATA array. This value is automatically incremented after each word is written to, or read from, the INPUT_DATA array. The INPUT_DATA_NUMBER refers to the input data location that is being operated on, and falls in the range of 0 to 9,999. This location must be written to prior to operating on the INPUT_DATA array, and is stored in the USER_INPUT_DATA_NUMBER location. The INPUT_AUTO_LOCATION register is used by the system to identify the next available user input that has not been setup as valid. If the user wishes to use this input for the next Input data Pattern, the value should be read, and then written into the USER_INPUT_DATA_NUMBER register.

[0178] Within the input manager control and state machine, the necessary information regarding masking regards the masking required for the described input, and whether the randomizer results drive an additional mask step, or whether they are a final result. A later section on masking describes in detail how the masking is handled and calculated. The PRESENT_MASK_STEP value stores the masking step to be used on the present data inputs. Any bits that are covered by this masking operation are disregarded with respect to their storage in the INPUT_DATA array. The NEXT_MASK_STEP value dictates whether there is an additional masking step. A NEXT_MASK_STEP value of 0 indicates that this is a final value, and when reached, the user receives the INPUT_NUMBER for the corresponding INPUT_DATA pattern that has been matched. The two MASK registers are stored automatically by the system after all of the input data words have been loaded into DRAM.

[0179] In addition to the aforementioned registers, there are a group of registers within the input manager control and state machines (see Table Q below) that are used for internal operations. INPUT_STRUCT_PTR is a general purpose pointer used to manipulate data. INPUT_STRUCT_VALUE is a general purpose register used to store either INPUT_DATA or INPUT_VALID information. INPUT_VALID_ENCODE is used to store the result of a 32 to 1 priority encoder, and the INPUT_CONTROL_REG is described below.

[0180]

TABLE Q
Storage Associated with User Inputs
Address	Name	Size	R/W	Default	Notes
0x00	INPUT_VALID_BASE	32	R/W	0	Points to the
		Bits			first entry in the
					INPUT_VALID data
					structure.
0x01	INPUT_DATA_BASE	32	R/W	313	Points to the
		Bits			first entry in the
					INPUT_DATA
					Structure.
0x02	INPUT_DATA_LENGTH	10	R/W	1023	This is the
		Bits			length in bits of the
					user input data pattern
					that is to be evaluated.
0x03	INPUT_DATA_WORD_COUNT	5	R/W	X	This register
		Bits			stores the word count
					within the input data
					pattern.
0x04	USER_INPUT_DATA_NUMBER	16	R/W	X	This is the
		Bits			number of the input
					data pattern that is
					being operated on. It
					is used for both writing
					and clearing input data
					patterns.
	SYS_INPUT_DATA_NUMBER	16		X	This is the
		Bits			number of an input
					data pattern that the
					system wishes to
					operate on. It is used
					when checking the
					validity of inputs, or
					loading inputs from the
					system.
	INPUT_NUM_SOURCE_SEL	1 Bit		X	This selects
					the user written
					USER_INPUT_DATA—
					NUMBER when set to
					a 0, and the System
					selected
					SYS_INPUT_DATA_NUMBER
					when set to a
					1. The output of this
					register is referred to
					as the
					INPUT_DATA_NUMBER.
0x05	INPUT_AUTO_LOCATION	16	R	X	This is used
		Bits			by the system when it
					determines the next
					available input to write.
0x06	PRESENT_MASK_STEP	4	R/W	X	This selects
		Bits			the Masking that
					should be done on this
					Input Pattern. A value
					of 0 indicates that this
					is not a masking step.
0x07	NEXT_MASK_STEP	4	R/W	X	This dictates
		Bits			whether an additional
					MASK step will be
					taken when this
					pattern is detected. A
					value of 0 indicates
					that this is a final
					value.
0x08	INPUT_STRUCT_PTR	32	X	X	This is a
		Bits			general purpose
					register to be used as
					a pointer into either the
					INPUT_DATA or
					INPUT_VALID
					structures.
0x09	INPUT_STRUCT_VALUE	32	R/W	X	This is a
		Bits			general purpose
					register to be used to
					store values to be read
					or written to the
					INPUT_DATA array, or
					to the INPUT_VALID
					array.
0x0A	INPUT_VALID_ENCODE	5		X	This is a
		Bits			general purpose
					register to be used to
					hold the output of a 32
					bit priority encoder
					used for the
					INPUT_VALID
					structure.
0x0B	INPUT_CONTROL_REG	9	R/W	X	Control
		Bits			Register for Input data
					and Valid
					Manipulation. See
					detailed Description.

INPUT_CONTROL_REG Details

[0181] The INPUT_CONTROL_REG (see Table R below) contains all of the control bits associated with modifications to the INPUT_DATA array and the INPUT_VALID array. These bits include those necessary to Initialize the INPUT_VALID array, to write new INPUT_DATA, and to read INPUT_DATA. The special AUTO_LOCATION feature is used to permit the system to determine the next available INPUT_DATA location. This is an option that is permitted in cases where the user does not want to keep track of this process in a tight fashion.

[0182]

TABLE R
INPUT_CONTROL_REG
BIT 9	BIT 8	BIT 7	BIT 6	BIT 5	BIT 4	BIT 3	BIT 2	BIT 1	BIT 0
Input	I/O Ready	Buffer	Unused	Inputs	Wrap	Command	Command
Valid		Full	Input	Full		Complete

• • [0183] BITS [2:0] The Command field is used to select an input data pattern operation to perform. A command of 0 signifies that no operation should be done, and is the steady state for this register. A write of a non-zero value will start an operation, and immediately clear the Command Complete bit. When an operation has been totally completed, the Command Complete bit will be set. An operation can only be terminated with a Reset Command of all Ones. On Power-Up, the Command field will be set to “001” to Initialize the Input Valid array. When the Initialization sequence completes, the Command Complete bit is set.
    • [0184] Code Command
    • [0185] “000” No-Operation
    • [0186] “001” Initialize Input Valid array
    • [0187] “010” Write/Load Input into DRAM
    • [0188] “011” Write Input into DRAM
    • [0189] “100” Read Input from DRAM
    • [0190] “101” Clear Input from DRAM
    • [0191] “110” Check Input Valid
    • [0192] “111” Reset Command
  • [0193] BIT 3 The Command Complete bit is set to a “1” when the specified command has been completed. If the Command Complete bit is a “0”, only the Reset Command can be written to the Command field.
  • [0194] BIT 4 The Wrap Bit is used to signify that the system has wrapped over the maximum value in the INPUT_VALID array. This is used in the process of searching an unused input.
  • [0195] BIT 5 The Inputs Full Bit is used to signify that there are no open inputs available in the structure.

[0196] BIT 6 The Unused Input bit is used to signify that the system has identified the next available input location, and the input number is stored in the INPUT_AUTO_LOCATION register.

• • [0197] BIT 7 The Buffer Full bit is used to indicate that either the Write Buffer when setting up a pattern, or the Read Buffer when reading back a pattern is full.
  • [0198] BIT 8 The I/O Ready bit is used to signify that the system is ready for a write or a read operation that has been previously setup.

[0199] BIT 9 The Input Valid bit is used to signify that an input being checked is storing a valid input that is being used by the system.

Inputs and Equation Correlation

[0200] It is critical that there be correlation between the inputs that are stored and the ones that have been mapped by various equations. As inputs are written or cleared, they are always calculated for all active equations at that time. The equation update generator uses an EQUATION_INPUT_UPDATE_PTR to cycle through all of the valid inputs. If a new input is stored in the middle of this process, or an input is cleared, the EQUATION_INPUT_UPDATE can be temporarily discontinued to allow that to occur. When equation updates are being made, it is necessary to initialize (clear) out the entire primary and secondary randomizer tables.

Processes Associated with Input Control

[0201] The processes shown in Table S below are used to manipulate the input array and the input valid databases.

[0202]

TABLE S
Processes Associated with Input Control
Process/Macro Name	Process Type	Description
INIT_INPUT_VALID	Internal	Used to initialize the Input Valid Array.
USER_CHECK_VALID	External	Used by the user to determine whether a
		specific Input Number is Valid and being
		used by the equation Mappers.
SYS_CHECK_VALID	Internal	Used by the system to determine whether a
		specific Input Number is Valid and being
		used by the equation Mappers.
SYS_GET_AVAIL_INPUT	Internal	Used to determine the next available input
		location in the user input array.
USER_INPUT_WR_LOAD	External	Used to write a user input into DRAM for
		storage, and loads it into the Input Register.
USER_INPUT_WRITE	External	Used to write a user input into DRAM for
		storage. This procedure does not load the
		input register.
USER_INPUT_READ	External	Used to read a user input from DRAM.
		This procedure does not load the input
		register.
USER_INPUT_CLEAR	External	Used to clear out a user input from DRAM.
		This process automatically involves loading
		it into the Input Register.
SYS_INPUT_LOAD	Internal	Used to read a user input from DRAM and
		load it into the Input Register without having
		the user read the value. This process is
		used for internal equation table
		regeneration.

Input Register Arbitration and DRAM Access Arbitration

[0203] There are five processes that require access to the DRAM. Two of these processes, USER_INPUT_WR_LOAD, and USER_INPUT_CLEAR, also load the input register. The user should be accessing only one of the three user/external processes at a time because it is the user's responsibility to finish one action prior to starting another. From the perspective of the 1024-bit input register, there are three processes that result in it being loaded: USER_INPUT_WR_LOAD, USER_INPUT_CLEAR and SYS_INPUT_LOAD. The SYS_INPUT_LOAD and USER_SYS_INPUT_VALID procedures can be initiated by the system, as part of a full equation swap, and are less critical than an immediate change by the user with either the USER_INPUT_WR_LOAD or the USER_INPUT_CLEAR processes (see Table T below).

[0204]

TABLE T
Input Register Arbitration
Process	Priority	Rationale
USER_INPUT_WR_LOAD	Highest	When the user wishes to add a
		new input to the system, this
		should take the highest priority.
USER_INPUT_CLEAR	Medium	Clearing an input is less
		critical than writing a new
		input into the system.
SYS_INPUT_LOAD	Lowest	This routine is called when
		refreshing an equation which
		should take the lowest priority.

[0205] The DRAM memory can be accessed by a number of processes described above. It is necessary to have arbitration between these processes, so that any two do not conflict over the use of internal registers. The weights in the Table U below are meant to show how often one of the following actions should be taken when two actions are being requested. The real issue here is the relative weights. For example, a USER_INPUT_WR_LOAD occurs eight times for every USER_INPUT_LOAD if both are continually being requested.

[0206]

TABLE U
DRAM Access Arbitration
	Priority And
	Arbitration
Process	Weight	Rationale
INPUT_VALID_INIT	10/10	Must be done on initialization prior
		to any other operation on the user
		data.
USER_INPUT_WR_LOAD	8/10	High priority since new user writes
		are more critical than reads or
		clears.
USER_INPUT_WRITE	2/10	Lower priority since this write is not
		being presently used or mapped.
USER_INPUT_READ	5/10	Read may be needed to calculate a
		new value to write into the chip.
GET_AVAIL_INPUT	4/10	May be critical for a new write to
		occur.
SYS_INPUT_LOAD	2/10	Used by the system for equation
		updates.
USER_INPUT_LOAD	1/10	Should rarely take priority over user activities.

Inter-Block Communication

[0207] It is necessary for the mapper engine, statistics, and equation state machine to be able to read input data values from DRAM into the input registers so that they can be mapped and stored. This is important for the equation update process.

[0208] The I/O ready bit in the input control register is used to hold-off read or writes to the custom ASIC until the proper internal function has been completed. In addition, the I/O ready bit is used to handle the larger issue of holding off the user while the system uses the input registers to recalculate an equation. A round robin arbiter is used to make sure that the system and the user get alternating preference on occasions where a conflict exists. As the user issues a command, the system determines whether the mapper engine, statistics, and equation state machine is also requesting access. If the internal mapper . . . ” block has priority, the I/O ready bit is kept at a level until the internal operation completes (see Table V below).

[0209]

TABLE V
Inter-Block Signals (Input Manager Control and State Machine
<-> mapper Engine, Statistics and equation state machine)
	Input Manager
Signal	Direction	Notes
Request	Input	Signifies that the mapper Engine wishes
Input Control		to perform an operation
Input Control	Output	Passes control of the Input Manager
Acknowledge		registers to the mapper Engine
Load Input	Input	Used by the mapper Engine to start a
Register		fetch from DRAM. The
		USER_INPUT_DATA_NUMBER
		must be previously loaded by
		the system.
Input Register	Output	Tells the mapper Engine that the data in
Loaded		the Input Register is for a complete
		input.

1024-Bit Input Registers

[0210] There are four sources of data that need to be able to drive the equation mapper, i.e. a new user input that should be mapped and stored for future use, a previously stored user input that should be brought back for analysis with a new equation, special bit patterns required for input data masking analysis, and parallel data that is received and requires packet classification. The discussion above described how arbitration between new user inputs and previously stored user inputs is performed. Neither of these functions is time critical, but either requires significant overhead in setup and should not be interrupted prior to completion. The special bit patterns required for input data masking analysis are described herein, and they are independently generated and multiplexed into the source of the equation mapper. Finally, parallel data that are received and require packet classification have a time critical component. Due to the time criticality for parallel classification, an independent set of registers is used to store this data. This permits decisions to be made rapidly, and results in minimal disruption to the new user input and previous user input analysis that may be occurring concurrently.

1024-Bit Input Register for Analysis

[0211] There are 1024 input bits in the custom ASIC that store and operate on user defined input data patterns. The INPUT_STRUCT_VALUE holding register routes to 32 different input data registers that are each 32 bits in length. The select for each bank of registers is cycled through from Bank0 to Bank31 as a total input vector is loaded into the custom ASIC. The input data registers are not externally readable or writeable by the user. The INPUT_DATA_WORD_COUNT register routes the INPUT_STRUCT_VALUE to the appropriate INPUT_REG_BANKn (see Table W below).

[0212]

TABLE W
Input Register data Structure
Name	Size	Notes
INPUT_REG_BANK0	32 Bits	Contains Input data Pattern Bits[31:0]
INPUT_REG_BANK1	32 Bits	Contains Input data Pattern Bits
		[63:32]
INPUT_REG_BANK2	32 Bits	Contains Input data Pattern Bits
		[95:64]
.
.
.
INPUT_REG_BANK31	32 Bits	Contains Input data Pattern Bits
		[1023:991]

[0213] The user's access to input data patterns is through the INPUT_STRUCT_VALUE register. The user can indirectly load the input registers through writing a new input data pattern into the custom ASIC, by reading and modifying a value stored in DRAM, and by clearing a value stored in memory. The system also is responsible for loading these registers during the operation of generating new randomizer values for a new equation. Table X below describes operations that result in loading the 1024-bit input register.

[0214]

TABLE X
Table of Operations that Load the 1024-Bit Input Register
Process	Initiator	Data Source
USER_INPUT_WR_LOAD	User	INPUT_STRUCT_VALUE
		(Written by User)
USER_INPUT_CLEAR	User	DRAM
SYS_INPUT_LOAD	System	DRAM

1024-Bit Input Register for Classification

[0215] There are 1024 input classification bits in the custom ASIC that analyze received data patterns for parallel classification. The INPUT_CLASS_VALUE holding register routes to 32 different input data registers that are each 32 bits in length. The select for each bank of registers is cycled through from Bank0 to Bank31 as a total input classification pattern is loaded into the custom ASIC. The input classification registers are not externally readable or writeable by the user. The INPUT_CLASS_WORD_COUNT register routes the INPUT_CLASS_VALUE to the appropriate INPUT_CLASS_REG_BANKn (see Tables X and Y below).

[0216]

TABLE X
Registers Associated with Parallel Input Classification
Name	Size	Note
INPUT_CLASS_VALUE	32 Bits	Contains Input Classification bits
INPUT_CLASS_WORD_COUNT	5 Bits	Selects one of 32 Input Classification
		Registers to direct the
		INPUT_CLASS_VALUE to. Automatically
		increments after write. When this exceeds
		the INPUT_DATA_LENGTH, it interrupts
		the Master Controller so that a Parallel
		Classification will be performed.

[0217]

TABLE Y
Input Classification Register data Structure
Name	Size	Notes
INPUT_CLASS_REG_BANK0	32 Bits	Contains Input Classification Bits[31:0]
INPUT_CLASS_REG_BANK1	32 Bits	Contains Input Classification Bits[63:32]
INPUT_CLASS_REG_BANK2	32 Bits	Contains Input Classification Bits[95:64]
.
.
.
INPUT_CLASS_REG_BANK31	32 Bits	Contains Input Classification Bits[1023:991]

[0218] The user's access to input classification patterns is through the INPUT_CLASS_VALUE register. The user directly loads the input classification registers through writing a new input data pattern into the custom ASIC

Masking and Enabling Logic and Masking Engine Details

[0219] The masking and enabling logic and the masking engine in the custom ASIC handle all aspects of the programmable masking function. The first major function is storage of user masking information including a description of the input data bits that are to be masked, as well as information identifying what bits are to be masked at what step of the sequential masking process. The second major function is the circuitry to generate the fixed masking of specified data bits. The third major function is the mask impact calculation circuitry. This circuitry drives the input data to determine the effect of each data bit on the output vector, so that when the bit is masked, it's effect can be cancelled out when interpreting a randomizer value. The fourth major function involves interpreting the outputs of the data framer to account for masking.

User Masking Information

[0220] The first level of masking information that must be stored by the system is the masking of all data bits beyond the length of data that the user desires to analyze, and the masking of data within a fixed OFF/ON period after the start of the input data pattern. To implement the length and OFF/ON period masking, a set of 1024 input enable bits is used to gate the input data bits to a zero in the cases where the bit is to be ignored. The INPUT_DATA_LENGTH register in the input section identifies the number of data bits that must be evaluated. The following registers identify the bit range that is to be masked by the OFF/ON period, and they are both user readable and writeable. The enable bits dictate whether the register are used and it's value is sent to the data framer (see Table Z below).

[0221]

TABLE Z
Off/On Register Description
Address	Name	B10	B9-B0
0x10	MASK_OFF_CYCLE_REG	Enable	Mask Off Start
			Location
0x11	MASK_ON_CYCLE_REG	Enable	Mask On Start
			Location

[0222] The user is supplied with four 32-bit input blocks that can be used for fixed and/or programmable bit masking. To achieve the effect of forced masking for bits covered by each enabled Programmable Mask register, the user must explicitly mask the bit pattern for each masking step pattern that is used. The 32 bit input blocks occur on 32-bit word boundaries, and can be described with simple five bit numbers (1024/32=32 or five bits). These 5-bit values identify bits in the received data pattern that are captured by the data framer in it's masking registers. In addition, a sixth bit is used to identify whether the mask register is to be enabled or disabled. This impacts whether the data framer captures the corresponding data. Disabling unnecessary masking conserves overall system power consumption. All of the mask register enable bits are set to 0 at power-up so that masking is disabled. All of the mask register start registers are both user writeable and user readable (see Table AA below).

[0223]

TABLE AA
Programmable Mask Registers
Address	Name	B5	B4	B3	B2	B1	B0
0x12	MASK_REGISTER_0	Enable	Mask Start Value 0
0x13	MASK_REGISTER_1	Enable	Mask Start Value 1
0x14	MASK_REGISTER_2	Enable	Mask Start Value 2
0x15	MASK_REGISTER_3	Enable	Mask Start Value 3

[0224] The custom ASIC provides up to eight selective masking steps, and permits the user to use any combination of these steps for a specific data circumstance. Selective Mask Step 0 is always used as the initial masking step when a packet is received. Selective Mask Steps 1–7 are used to handle occasions where the user wishes to mask subsets of data based upon specific packet types or parameters. Each of the 32×4=128 maskable bits have eight selective masking bits associated with them for a total of 1024 selective masking step bits. All selective masking step registers are both user readable and user write-able. If a MASK_REGISTER is disabled, the selective step bits are ignored (see Table AB below).

[0225]

TABLE AB
Selective Masking Step Registers
Address	Name	B31:B5	B4	B3	B2	B1	B0
0x20	MASK_REG0_SMS0	Forced Masking bits for Mask Register 0
0x21	MASK_REG0_SMS1	Masking Bits for Mask Register 0 with Selective
		Masking Step 1.
0x22	MASK_REG0_SMS2	Masking Bits for Mask Register 0 with Selective
		Masking Step 2.
0x23	MASK_REG0_SMS3	Masking Bits for Mask Register 0 with Selective
		Masking Step 3.
0x24	MASK_REG0_SMS4	Masking Bits for Mask Register 0 with Selective
		Masking Step 4.
0x25	MASK_REG0_SMS5	Masking Bits for Mask Register 0 with Selective
		Masking Step 5.
0x26	MASK_REG0_SMS6	Masking Bits for Mask Register 0 with Selective
		Masking Step 6.
0x27	MASK_REG0_SMS7	Masking Bits for Mask Register 0 with Selective
		Masking Step 7.
0x28	MASK_REG1_SMS0	Forced Masking bits for Mask Register 1
0x29	MASK_REG1_SMS1	Masking Bits for Mask Register 1 with Selective
		Masking Step 1.
0x2A	MASK_REG1_SMS2	. . .	1	1	1	1	0
0x2B	MASK_REG1_SMS3	. . .	0	1	0	1	0
0x2C	MASK_REG1_SMS4	. . .	1	1	1	0	1
0x2D	MASK_REG1_SMS5	Masking Bits for Mask Register 1 with Selective
		Masking Step 5.
0x2E	MASK_REG1_SMS6	Masking Bits for Mask Register 1 with Selective
		Masking Step 6.
0x2F	MASK_REG1_SMS7	Masking Bits for Mask Register 1 with Selective
		Masking Step 7.
0x30	MASK_REG2_SMS0	Forced Masking bits for Mask Register 2
0x31	MASK_REG2_SMS1	Masking Bits for Mask Register 2 with Selective
		Masking Step 1.
.	.
.	.
.	.
0x3E	MASK_REG3_SMS6	Masking Bits for Mask Register 3 with Selective
		Masking Step 6.
0x3F	MASK_REG3_SMS7	Masking Bits for Mask Register 3 with Selective
		Masking Step 7.

[0226] In Table AB, the addresses 0x2A, 0x2B and 0x2C have been expanded for bits 0 to 4 for illustration purposes. In this example in selective masking pattern 2 for mask register 1, bits 1–4 are masked. In selective masking step 3 for mask register 1, bits 1 and 3 are masked. In selective masking step 4 for mask register 1, bits 0 and 2–4 are masked.

Forced Masking Circuitry

[0227] The custom ASIC includes 1024 bits that are used to enable or disable the bit from consideration. These bits are used to drive the selection of whether an input data bit drives the mapper circuitry, or whether a “0” value is switched in to mask out the value (see table AC below). All bits that are contained within the fields of enabled Programmable Mask Registers will automatically be enabled for purposes of driving the mapping circuitry.

[0228]

TABLE AC
Input Enable Registers
Name	Size	Notes
INPUT_ENAB_BANK0	32 Bits	Contains Enables for Input data
		Pattern Bits[31:0]
INPUT_ENAB_BANK1	32 Bits	Contains Enables for Input data
		Pattern Bits[63:32]
INPUT_ENAB_BANK2	32 Bits	Contains Enables for Input data
		Pattern Bits[95:64]
.
.
.
INPUT_ENAB_BANK31	32 Bits	Contains Enables for Input data
		Pattern Bits[1023:991]

[0229] Within the masking and enabling logic, there is a block of initialization circuitry that can load up the INPUT_ENAB_BANKn registers. The steps of this initialization include: setting all of the bits to enabled, clearing out all enables after the INPUT_DATA_LENGTH value, and disabling bits that occur between the MASK_OFF_CYCLE_REG and the MASK_ON_CYCLE_REG. The forced masking steps affect every input data pattern, and as such, it is expected that they are setup once upon initialization. If any of these registers are changed, the entire custom ASIC and respective mappings become invalid, and require recalculation. The forced masking state machine is started after the appropriate user setup sequence (see Table AD below).

[0230]

TABLE AD
Forced Masking State Machine Registers
Name	Size	Notes
SET_ENAB_BANK	5 Bits	Counter to count through the 32 possible input
		banks
SET_ENAB_BIT	5 Bits	Counter to count through the 32 bit locations
		within an input bank.
SET_ENAB_FROM_SMS0	1 Bit	Signifies that there has been a match with one
		of the four mask registers.
SET_ENAB_SMS0_SELECT	2 Bits	Signifies the specific mask register that has
		been matched.
FORCE_MASK_ON	1 Bit	When this bit is set, bits will be Force Masked
		as a result of a MASK ON/OFF function or
		exceeding the INPUT_DATA_LENGTH.
WRITE_BIT	1 Bit	This is a bit that is ready to write into the
		appropriate enable register.

Mask Impact Calculation Circuitry

[0231] The masking impact of each bit that is in one of the four 32-bit masking registers must be calculated for each equation that is used. As a new equation is swapped in, theses bits must be calculated prior to re-evaluating all of the available inputs. Each input bit can affect any of the sixteen output bits in the primary randomizer pattern. Therefore, there are a maximum of 16×4×32=2,048 bits that must be stored per each equation. With a set of eight equations, this translates to a total of 8×2048=16,384 masking impact bits. Because it is critical that the masking impact bits be available in real time for equation calculations, it is important that these mask impact registers be stored on the custom ASIC. The masking impact registers are internal, and are not user-readable (see Table AE below).

[0232]

TABLE AE
Masking Impact Register Structure
(Internal to custom ASIC)
Name	Description
EQ0_MASK_REG0_IMP_BIT0	equation 0, Mask Register 0, Bit 0–16 Bit mask impact
EQ0_MASK_REG0_IMP_BIT1	equation 0, Mask Register 0, Bit 1–16 Bit mask impact
.	.
.	.
.	.
EQ0_MASK_REG0_IMP_BIT31	equation 0, Mask Register 0, Bit 31–16 Bit mask impact
EQ0_MASK_REG1_IMP_BIT0	equation 0, Mask Register 1, Bit 0–16 Bit mask impact
EQ0_MASK_REG1_IMP_BIT1	equation 0, Mask Register 1, Bit 1–16 Bit mask impact
.	.
.	.
.	.
EQ0_MASK_REG1_IMP_BIT31	equation 0, Mask Register 1, Bit 31–16 Bit mask impact
EQ0_MASK_REG2_IMP_BIT0	equation 0, Mask Register 2, Bit 0–16 Bit mask impact
EQ0_MASK_REG2_IMP_BIT1	equation 0, Mask Register 2, Bit 1–16 Bit mask impact
.	.
.	.
.	.
EQ0_MASK_REG2_IMP_BIT31	equation 0, Mask Register 2, Bit 31–16 Bit mask impact
EQ0_MASK_REG3_IMP_BIT0	equation 0, Mask Register 3, Bit 0–16 Bit mask impact
EQ0_MASK_REG3_IMP_BIT1	equation 0, Mask Register 3, Bit 1–16 Bit mask impact
.	.
.	.
.	.
EQ0_MASK_REG3_IMP_BIT31	equation 0, Mask Register 3, Bit 31–16 Bit mask impact
EQ1_MASK_REG0_IMP_BIT0	equation 1, Mask Register 0, Bit 0–16 Bit mask impact
EQ1_MASK_REG0_IMP_BIT1	equation 1, Mask Register 0, Bit 1–16 Bit mask impact
.	.
.	.
.	.
EQ1_MASK_REG0_IMP_BIT31	equation 1, Mask Register 0, Bit 31–16 Bit mask impact
.	.
.	.
.	.
.	.
.	.
.	.
EQ7_MASK_REG3_IMP_BIT0	equation 7, Mask Register 3, Bit 0–16 Bit mask impact
EQ7_MASK_REG3_IMP_BIT1	equation 7, Mask Register 3, Bit 1–16 Bit mask impact
.	.
.	.
.	.
EQ7_MASK_REG3_IMP_BIT31	equation 7, Mask Register 3, Bit 31–16 Bit mask impact

[0233] The calculation of the masking impact bits is done by injecting a single “1” pattern into every appropriate bit in the input data pattern. As an input of a “1” in a specific masked bit is applied, the output of the mapper circuit is a 16-bit mask impact that needs to be stored. This mask impact can then be calculated for each of the eight active equations before the walking “1”s pattern is advanced (see FIG. 12). The walking 1's pattern is generated by writing a 10-bit value into the WALKING_ONE_VALUE register, and having it drive a 10:1024 decoder. The output of the decoder is a single “1” in the location identified by the WALKING_ONE_VALUE register.

[0234] The input source select directs whether the input register or the walking one's pattern should be used to drive the mapping circuitry (see Tables AF and AG below).

[0235]

TABLE AF
Internal Register associated with Masking Impact Calculation
Register	Size	Notes
WALKING_ONE_VALUE	10 bits	Signifies the input that is
		to be set to
		a “1” for Masking Impact test
		purposes.
INPUT_SOURCE_SELECT	1 bit	“1” selects the Input Register
		to drive the mapping circuitry.
		“0” selects the Walking One's
		pattern to
		drive the mapping Circuitry.
INPUT_CLASS_SELECT	1 bit	“1” selects parallel input
		classification mode.
		“0” selects
		the input register pattern used
		to calculate mapping values.
EQUATION_STORE_ENTRY	3 bits	Signifies the equation being
		used. Valid equations range
		from 0 to 7.

[0236]

TABLE AG
Output Signals from the 10 bit decoder
Decoder Output Signals	Notes
WALKING_ONE_OUTPUT[1023:0]	Routes to multiplexers
	associated with each input data
	bit.

[0237] The walking ones pattern must be driven by the system into the inputs that are associated with each MASK_REGISTER. A state machine sequences through the registers to accomplish this task (see Table AH below).

[0238]

TABLE AH
Internal Signals driving the 1024 equation Mapper
Signal	Size	Notes
MAPPER_SOURCE0[31:0]	32 Bits	Signal Bits[31:0] that drive
		the Mapper
MAPPER_SOURCE1[31:0]	32 Bits	Signal Bits[63:32] that drive
		the Mapper
.	.	.
.	.	.
.	.	.
MAPPER_SOURCE31[31:0]	32 Bits	Signal Bits[1023:991] that drive
		the Mapper

[0239] The mapper outputs must be routed to the appropriate mask impact registers for the equation that is being addressed. For instance, when equation 1's mapping is being checked for MASK_REG0 and the system is looking at the impact of bit 31 in the register, the mapper value is written to the register EQ1_MASK_REG0_IMP_BIT31. The mapper outputs must be routed to a total of 1024=(8 equations*4 mask registers*32 bits) mask impact registers. The novel custom ASIC must be able to generate an enable for each of these registers that is based on the equation number, the bit number, and the MASK_REGISTER.

Output Mask Adjustments

[0240] When a randomizer value from the data framer is received, the system must adjust it by canceling out any bits that have been masked. This operation is done using the mask impact registers and effectively adding the appropriate values into the received word based on the equation being used at the time. In the case of the primary and secondary randomizer values, different equations are used to generate these numbers (see Table AI below).

[0241]

TABLE AI
Randomizer Received Registers
Address	Name	Size	Notes
0x00	PRIM_RANDOMIZER_RX	16 Bits	Novel data framer
			ASIC primary
			randomizer received
			value
0x01	SEC_RANDOMIZER_RX	16 Bits	Novel data framer
			ASIC secondary
			randomizer received
			value

[0242] The storage registers for the mask capture data from the data framer are used in the calculation to cancel out the effect of masked bits (see Table AJ below).

[0243]

TABLE AJ
Mask Register Capture Data
Address	Name	Size	Notes
0x02	MASK_CAPTURE_DATA_0	32 Bits	Novel data
			framer ASIC Mask Capture data for
			MASK_REGISTER_0
0x03	MASK_CAPTURE_DATA_1	32 Bits	Novel data framer ASIC Mask
			Capture data for
			MASK_REGISTER_1
0x04	MASK_CAPTURE_DATA_2	32 Bits	Novel data framer ASIC Mask
			Capture data for
			MASK_REGISTER_2
0x05	MASK_CAPTURE_DATA_3	32 Bits	Novel data framer ASIC Mask
			Capture data for
			MASK_REGISTER_3

Parallel Classification Output Mask Adjustments

[0244] When a parallel data pattern is loaded into the system from the microprocessor interface for classification, the system must adjust it by canceling out any bits that have been masked. This operation is done using the mask impact registers and effectively adding the appropriate values into the received word based on the equation being used at the time. In the case of the primary and secondary randomizer values, different equations are used to generate these numbers (see Table AK below).

[0245]

TABLE AK
Parallel Classification randomizer Registers
Name	Size	Notes
PRIM_RANDOMIZER_PAR	32 Bits	This value is latched from
		the output
		of the mapper Multiplexer.
SEC_RANDOMIZER_PAR	32 Bits	This value is latched from the
		output of the
		mapper Multiplexer.

[0246] The storage registers for the mask capture data from the data framer are used in the calculation to cancel out the effect of masked bits (see Table AL below).

[0247]

TABLE AL
Parallel Classification Mask Register Capture Data
Name	Size	Notes
MASK_CAPTURE_PAR_0	32 Bits	Mask Capture Register 0
		for Parallel Classification mode.
MASK_CAPTURE_PAR_1	32 Bits	Mask Capture Register 1 for
		Parallel Classification mode.
MASK_CAPTURE_PAR_2	32 Bits	Mask Capture Register 2 for
		Parallel Classification mode.
MASK_CAPTURE_PAR_3	32 Bits	Mask Capture Register 3 for
		Parallel Classification mode.

Illustration of Programmable Masking

[0248] To determine the post masking result for any bit in a randomizer pattern, there are a total of four values that must be considered, i.e. the non-masked randomizer output (PRIM_RANDOMIZER_RX or SEC_RANDOMIZER_RX), the sequential mask step for the specific bit for the specific equation being analyzed (MASK_REGm_SMSp_EQn), the mask impact for the specific bit (EQn_MASK_REGm_IMP_BITq), and the actual captured status of the masked bit (MASK_CAPUTURE_DATA_m). From a masking perspective, there are a total of 128 (32×4) bits that can be masked. At this point, the mask registers, the mask capture data registers, and the mask impact registers are all relative, and we are not concerned with the absolute location within the data word. What is important is whether a specific bit is being masked in a specific selective masking sequence, whether the bit impacts the output vector, and whether the bit was actually captured as a one. Due to the nature of the randomizer implementations, data bits that are 0 do not impact the output vector (see Table AM below).

[0249]

TABLE AM
Internal Register to choose the Selective Masking Step
Register
Name	Size	Notes
SELECTIVE_MASK_SELECT	3 Bits	This register is written by the
		system to choose the Selective
		Masking pattern to be used in
		calculations.

[0250] The programmable masking function can operate on either the primary or the secondary randomizer value. The system must be able to switch between these between any two cycles because evaluation of the primary and secondary values must be done in successive operations when searching the database. The RANDOMIZER_SELECT register determines which of these two randomizer values is analyzed.

[0251] The novel custom ASIC permits analysis of either data (serial) or parallel data passed over from the microprocessor. The SOURCE_SER_PAR signal is used to select between these two sources of data. This signal permits the system to operate while receiving packet classification information through these two possible interfaces (see Table AO below).

[0252]

TABLE AO
Internal Register to choose the
randomizer Output to be analyzed
Name	Size	Notes
RANDOMIZER_SELECT	1 Bit	This register is written by the system
		to choose the randomizer to be
		analyzed by the Masking Analyzer. A
		“0” value selects the primary
		randomizer, while a “1” value selects
		the secondary randomizer value.
SOURCE_SER_PAR	1 Bit	This register selects between
		classifying data from the Serial
		interface or the Parallel
		Microprocessor interface. A value of
		“0” selects the Novel interface, and a
		value of “1” selects the Parallel
		Interface.

[0253] To illustrate the programmable masking function, consider one of the possible 128 bits that can be masked (see FIG. 13). The use of buses in this example signify that there are parallel implementations of the logic for each of the data bits. The outputs for this bit must be sent through an exclusive-or tree to add them in with the remaining 127 mask bits and the initial randomizer value.

[0254] In this example, an XOR tree masks the 128 possible masked bits with the selected randomizer output. The system permits a sequential selective masking approach (see Table AP below). In a sequential masking approach, the output of the first masking must point to a location in memory.

[0255] The system allows the user to specify a sequence of masking steps that can be taken for a given data pattern. In other words, the primary randomizer output can be changed for bits 0–4 of one of the masking words in the first pass, and then bits 5–7 in the second pass. The masking steps are provided in the primary randomizer table entries. The custom ASIC could be developed for expansion of the ability to logic analyzer capture serial data in the event a simple change to the data framer is made.

[0256]

TABLE AP
Sequential Masking Protocol
Process Step	Action	Next Process Step Determination
Initial primary	Read the primary randomizer	1) Use the Forced Masking primary
randomizer	value from the Novel Data	randomizer Output value to index into the
Read	Framer.	primary randomizer Table.
	Mask Original primary	1.1) If this is a final entry, then verify the
	randomizer value with	secondary randomizer value (if
	SELECTIVE_MASK_STEP0 to	configured to do so). If there is a
	generate an initial selective	valid match, then report the input to
	masking primary randomizer	the user.
	Output. This is done internal to	1.2) If the entry is a Selective Masking
	the Novel 10K ASIC	Entry, then progress to the specified
		Selective Masking Level.
Selective	Mask Original primary	1) Use the latest Selective Masking primary
Masking	randomizer Pattern with the	randomizer Output value to index into the
	chosen Selective Masking	primary randomizer Table.
	Pattern to generate a new	1.1) If this is a final entry, then verify the
	Selective Masking primary	secondary randomizer
	randomizer Output. This is	value (if configured to do so). If
	done internal to the Novel 10K	there is a valid match, then report
	ASIC.	the input to the user.
		1.2) If the entry is a Selective Masking
		Entry, then progress to the specified
		Selective Masking Level.

Processes Associated with the “Masking and Enabling Logic” Block

[0257] Table AQ below shows processes are used to setup the enable bits and to calculate the masking Impacts for each selected bit.

[0258]

TABLE AQ
Processes Used to Setup Enable Bits
	Process
Process/Macro Name	Type	Description
INIT_FORCED_MASK	Internal	Used to setup all of the bits that
		will be masked off from use in the
		randomizer Calculations. Requires
		INPUT_DATA_LENGTH,
		MASK_ON_CYCLE_REG, and
		MASK_OFF_CYCLE_REG
		be finalized.
INIT_PROG_MASK	Internal	Used to calculate the impact of
		all bits in each Programmable
		mask register that is enabled.
		This must be done any time a brought
		new equation is into the
		system. It should also be done on
		initialization, once all of the Selective
		Mask Registers have been initialized.

Equation Mapper

[0259] The equation mapper takes the latest pattern in the input register, as post operated on by the masking logic, and maps it through a giant XOR gate logic tree to derive a corresponding randomizer value. On average, each randomizer output bit is made up of half the input data bits. In this case, each output is the XOR of 512 inputs. An XOR tree for 512 inputs takes a total of (256+128+64+32+16+8+4+2+1=) 511 two input XOR gates. Each mapping uses 16 bits, or a total of (16*511=) 8176 gates to produce the randomizer output. When more and more equations are used, there is significant redundancy in the logic gates making up this XOR tree.

[0260] The analysis shown in Tables AR and AS below breaks down the tree into levels. The first level operates on groups of two inputs from the input data pattern. If these inputs are referred to as A and B, there is a single XOR term possible (A XOR B), and there are two single terms that flow through to the next level: A and B. At the second level of the tree, one can view the combinations of the groups (A,B) and (C,D). There are a total of six inputs for this block at the second level (A, B, A XOR B, C, D and C XOR D). When working with the tree, each of the inputs from the A,B group can be XOR'd with each of the inputs from the C,D group. This results in a total of nine possible XOR terms at this level. The output terms from each higher level=(Output Terms from previous level ^^2+2*Output terms from previous level). The 2*Output terms from previous level accounts for the pass through values.

[0261]

TABLE AR
Size for 1024 Equations
				Number	Max	Max XOR	XOR
			Maximum	of	Output	Terms Per	Gates/Level
	Inputs	Output	XOR	Blocks	Terms	Block	(*Number of
	per	Terms from	Terms	for 1024	limited by	Limited by	Blocks for
Level	Block	each Block	Per Block	Inputs	Equations	Equations	1024 Inputs)
1	2	3	1	512	3	1	512
2	4	15	9	256	15	9	2304
3	8	255	225	128	255	225	28800
4	16	65535	65025	64	1024	1024	65536
5	32	4.29E9	4.29E9	32	1024	1024	32768
6	64	1.84E+19	1.84E+19	16	1024	1024	16384
7	128	3.40E+38	3.40E+38	8	1024	1024	8192
8	256	1.16E+77	1.16E+77	4	1024	1024	4096
9	512	1.34E+154	1.34E+154	2	1024	1024	2048
10	1024	Overflow	Overflow	1	1024	1024	1024
Total Number of XOR Gates in Tree per Output Bit	161,664
Total Number of XOR Gates for Entire Tree	2,586,624

[0262]

TABLE AS
Size for 128 Equations
				Number	Max	Max XOR	XOR
			Maximum	of	Output	Terms Per	Gates/Level
	Inputs	Output	XOR	Blocks	Terms	Block	(*Number of
	per	Terms from	Terms	for 1024	limited by	Limited by	Blocks for
Level	Block	each Block	Per Block	Inputs	Equations	Equations	1024 Inputs)
1	2	3	1	512	3	1	512
2	4	15	9	256	15	9	2304
3	8	255	225	128	128	128	16384
4	16	65535	65025	64	128	128	8192
5	32	4294967295	4294836225	32	128	128	4096
6	64	1.84467E+19	1.84467E+19	16	128	128	2048
7	128	3.40282E+38	3.40282E+38	8	128	128	1024
8	256	1.15792E+77	1.15792E+77	4	128	128	512
9	512	1.3408E+154	1.3408E+154	2	128	128	256
10	1024	Overflow	Overflow	1	128	128	128
Total Number of XOR Gates in Tree per Output Bit	35,456
Total Number of XOR Gates for Entire Tree	567,296

Mapper Multiplexer

[0263] The mapper multiplexer circuitry must take equation mapper outputs and select the appropriate randomizer bit pattern for the equation that is being used. The size of the mapper multiplexer is dependent upon the number of equations being used. The register sown in Table AT below is used to signify the mapping that is to be selected.

[0264]

TABLE AT
Internal Register to Select the equation Mapping
Name	Size	Notes
EQUATION_MAP_SELECT	10 Bits	This register is written by the
		system to choose the equation
		mapping pattern to be used.

[0265] The mapper multiplexer size can be calculated using the formula that a multiplexer tree for 2^n bits contains 2^n−1 2:1 multiplexers. Table AU below shows the number of multiplexers that are needed as a function of the number of equations that are implemented.

[0266]

TABLE AU
Calculation of 2:1 Multiplexers needed
as a function of Equations
	Multiplexers per	Total 2:1 Multiplexers
Number of Equations	randomizer Bit	Required
128	127	2032
256	255	4080
512	511	8176
1024	1023	16368

[0267] The output of the equation multiplexer corresponds to the calculated randomizer value for the selected equation, and it is used to drive the mapper storage control block.

[0268]

TABLE AV
Internal Signal name for the equation Multiplexer
Output
Name	Size	Notes
CALC_RANDOMIZER_VALUE	16 Bits	This output is the calculated
		randomizer value for the
		selected equation.

Mapper Storage Control and Storage State Machine

[0269] The mapper storage control and storage state machine handles storing and retrieving randomizer values and associated table information. When new inputs are provided, the system must calculate and store randomizer values for all equations of interest. When the system receives a randomizer value from the data framer, it must access these tables to identify the proper input.

Primary Randomizer Output Vectors

[0270] The output of the primary randomizer is a 16-bit number that maps to an input. For instance, if Input #5356 produces a value of 24593 in the primary randomizer, then whenever the primary randomizer value of 24593 is received, the system returns input #5356. Tables AW and AX below show how inputs map when randomized by different equations (A, B, C, . . . n).

[0271]

TABLE AW
Primary randomizer mapping Table
	Primary	Primary	Primary		Primary
	randomizer	randomizer	randomizer		randomizer
Input #	A Output	B Output	C Output	. . .	“n” Output
1	1A	1B	1C		1n
2	2A	2B	2C		2n
3	3A	3B	3C		3n
4	4A	4B	4C		4n
5	5A	5B	5C		5n
6	6A	6B	6C		6n
7	7A	7B	7C		7n
.
.
.
10,000	10000A	10000B	10000C		10000n

[0272]

TABLE AX
Primary randomizer Decoder Table
	Primary	Primary		Primary
	randomizer	randomizer		randomizer
Output Vector	A Map	B Map	. . .	“n” Map
0	5356A	x		4678n
	x	x		8888n
	x	x		589n
	x	x		6688n
1	234A	3256B		x
	3678A	x		x
	x	x		x
	x	x		x
2	x	7890B		x
	x	576B		x
	x	x		x
	x	x		x
3	9735A	x		2222n
	121A	x		x
	5678A	x		x
	x	x		x
.
.
.
65,535	7764A	125B		x
	x	987B		x
	x	x		x
	x	x		x

[0273] In the above Table AX, there are six example locations with no inputs that map into a specific state: A map 2, B map 0, B map 3, n map 1, n map 2, and n map 65535. There are four example locations with one input that maps to a specific state: A map 0, A map 65535, B map 1, and n map 3. There are three locations with two inputs that map to a specific state: A map 1, B map 2, and B map 65535. There is one location where three inputs map into a specific state: A map 3. There is one location where four inputs map into a specific state: n map 0.

[0274] The example in the above Table AX has a much higher rate of one, two, three, or four inputs being mapped into a specific state than would be found in an actual implementation. This has been done for illustrative purposes only.

Primary Randomizer Table Entries

[0275] This discussion describes all of the entries in the primary randomizer table for the various possibilities of: no match, single match, pair match, triple match, quadruple match, overflow and masking (see Tables AY, AZ, and BA below).

[0276]

TABLE AY
primary randomizer Decoder Table Entry
OFF-	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT
SET	15	14	13	12	11	10	9	8	7	6	5	4	3	2	1	0
0	STAT1	STAT0	Input Number
1	secondary randomizer Value

STAT Bits

• • [0277] 00 There is not a valid input that matches this value.
  • [0278] 01 There is one valid match for this input, and it's secondary Randomization pattern is contained in bits 0–13.
  • [0279] 10 There are two valid matches for this input, and they are stored in the Multiple Location found in bits 0–9.
  • [0280] 11 There are three (or more) valid matches for this input, and they are stored in the Multiple location found in bits 0–9.

[0281]

TABLE AZ
primary randomizer Decoder Table Entry for No Match
	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT
OFFSET	15	14	13	12	11	10	9	8	7	6	5	4	3	2	1	0
0	0	0	XXX
1	XXX

[0282]

TABLE BA
primary randomizer Decoder Table Entry for Single Match
	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT
OFFSET	15	14	13	12	11	10	9	8	7	6	5	4	3	2	1	0
0	0	1	Input Number
1	secondary randomizer Number

[0283] The determination as to where to check the secondary randomization pattern is left to a later time. This is due to the fact that the user could chose to ignore the secondary randomization pattern. Of special interest is the case where a single match occurs that is a masking value and not a final input value. This case is handled in the Triple/Overflow/Mask case, where there are sufficient bits to encode the situation. In many ways, the MASK situation can be viewed as a multiple input situation (see Table BB below).

[0284]

TABLE BB
Primary randomizer Decoder Table Entry for Pair Match
	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT
OFFSET	15	14	13	12	11	10	9	8	7	6	5	4	3	2	1	0
0	1	0	XXX	Multiple Match Table Entry
1	XXX

[0285] The Multiple Match Table Entry points to one of 1024 multiple match table entries (see Table BG below).

[0286]

TABLE BC
Primary randomizer Decoder Table Entry for Triple Match
	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT
OFFSET	15	14	13	12	11	10	9	8	7	6	5	4	3	2	1	0
0	1	1	0	0	XXX	Multiple Match Table Entry
1	XXX

[0287] The Multiple Match Table Entry points to one of 1024 multiple match table entries (see Table BG below).

[0288]

TABLE BD
Primary randomizer Decoder Table Entry for quadruple
Match
	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT
OFFSET	15	14	13	12	11	10	9	8	7	6	5	4	3	2	1	0
0	1	1	0	1	XXX	Multiple Match Table Entry
1	XXX

[0289] The Multiple Match Table Entry points to one of 1024 multiple match table entries (see Table BG below).

[0290]

TABLE BE
Primary randomizer Decoder Table Entry for Overflows
	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT
OFFSET	15	14	13	12	11	10	9	8	7	6	5	4	3	2	1	0
0	1	1	1	0	#Over	Multiple Match Table Entry
1	XXX

[0291] The multiple match table entry points into the multiple match table, with the exception that the table format changes so that only the input numbers are stored and not the secondary randomizer numbers. This allows up to eight inputs to be stored. Because an overflow table entry evolves from a quadruple table entry, one does not move the four inputs that were previously stored, but the new inputs overwrite the existing secondary randomizer values in the structure.

[0292] The number of overflows(#Over) value specifies how many inputs are stored in what is normally the secondary randomizer section of the multiple match table entry structure. If there is a single overflow, this value is ‘01’. If there are two overflows this value is ‘10’, if there are three overflows this value is ‘11’, and if there are four overflows this value is ‘00’ (see Table BF below).

[0293]

TABLE BF
Primary randomizer Decoder Table Entry for Masking
	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT	BIT
OFFSET	15	14	13	12	11	10	9	8	7	6	5	4	3	2	1	0
0	1	1	1	1	XXX	Next Mask Step
1	secondary randomizer Value

Multiple Match Table

[0294] The custom ASIC uses a 1024 entry multiple match table (see Table BG below) to handle the cases where two, three, four, or the overflow case of (5–8) input vectors map to the same primary randomizer output. For each possible pair, there are two possible inputs and associated secondary randomizer values that need to be stored. For each possible triple, there are three possible inputs and associated secondary randomizer values that need to be stored. For each possible quadruple, there are four possible inputs and associated secondary randomizer values that need to be stored. In cases of 5–8 inputs which are signified as being overflow cases, the secondary randomizer values are dropped.

[0295] The primary randomizer table entry dictates the inputs and secondary randomizer values in the multiple match table entry that are valid.

[0296]

TABLE BG
Multiple Match Table Entry
OFFSET	B15	B14	B13	B12	B11	B10	B9	B8	B7	B6	B5	B4	B3	B2	B1	B0
0	First Value secondary randomizer Output
1	Second Value secondary randomizer Output
2	Third Value secondary randomizer Output
3	Fourth Value secondary randomizer Output
4	0	X	First Value Input Pointer (Final Value)
	1	XXX		First Value Next Mask
				Step
5	0	X	Second Value Input Pointer (Final Value)
	1	XXX		Sec Value Next Mask
				Step
6	0	X	Third Value Input Pointer (Final Value)
	1	XXX		Th Value Next Mask
				Step
7	0	X	Fourth Value Input Pointer (Final Value)
	1	XXX		Fth Value Next Mask
				Step

Multiple Match Table Valid Entries

[0297] The VALID_MULT_ARRAY (see Table BH below)stores information as to which multiple match table entries have been used by a particular mapping. There are 1024 multiple match table entries associated with each mapping, and the VALID_MULT_ARRAY is therefore 1024/16=64 values long to identify where there are open multiple entries. In addition, a second step of having four 16-bit values to signify where there are available entries that are used. One could conceivably use a pointer or pair of pointers in the ASIC to keep track of the next available inputs.

[0298]

TABLE BH
Valid Multiple Match Entry Array Table
Offset	16 Bit Value Description	Comments
0	First Block of Valid	0=Unused Table Entry
	Multiple Entry Tags	Bit 0=Multiple Entry 0
	(0–15)
1	Second Block of	0=Unused Table Entry
	Valid Multiple Entry	Bit 0=Multiple Entry 0
	Tags (16–31)
63	Sixty Fourth Block of Valid	0=Unused Table Entry
	Multiple Entry Tags)	Bit 0=Multiple Entry 0
	(1007–1023
64	Super Block Descriptor for	0=Unused Table Entry in Block
	Blocks (0–15)
65	Super Block Descriptor for	″
	Blocks (16–31)
66	Super Block Descriptor for	″
	Blocks (32–47)
67	Super Block Descriptor for	″
	Blocks (48–63)

Storage Required for Each Equation

[0299] Table BI below shows the memory storage required for each mapping that is stored.

[0300]

TABLE BI
Storage Associated with Each primary Mapping
Offset	Block	Length	Comments
0	primary randomizer	131072	Two 16 Bit words per
	Decoder Table		primary randomizer State.
131072	Multiple Match Table	8192	Eight 16 Bit words per
			Multiple Match Table Entry
139264	Valid Pair Array Table	68	Identifies entries in
			the Multiple Match
			Table that are used.
139332	mapping End

Registers Used in Storing and Reading a New Randomizer Entry

[0301] Table BJ below lists the registers used to access and modify the randomizer table. The output of the mapper is the CALC_RANDOMIZER_VALUE. The selection of the equation mapper uses the EQUATION_MAP_SELECT register. The storage value is EQUATION_STORE_ENTRY which dictates where the value is stored in the primary randomizer table. In the case of storing a new value into the randomizer table, the INPUT_DATA_NUMBER is the output of a multiplexer that selects between the USER_INPUT_DATA_NUMBER and the SYS_INPUT_DATA_NUMBER and it contains the input number for the value while the PRESENT_MASK_STEP and NEXT_MASK_STEP store the necessary masking information.

[0302] When interpreting a randomizer value from the data framer, the RANDOMIZER_SELECT value is used to determine whether to analyze the primary or secondary randomizer values. The PRIM_RANDOMIZER_RX register contains the primary randomizer value, and the SEC_RANDOMIZER_RX register contains the secondary randomizer value. The PROG_MASK_RX signal is the masked value of the received primary or secondary randomizer signal (see Table BJ below).

[0303]

TABLE BJ
Randomizer Control Registers
NAME	SIZE	COMMENTS
PRIM_RAND_TABLE_BASE	32 Bits	Located on Fire-Hose 10K ASIC.
		User Read/Writeable
		This is the base address in SRAM of the primary
		randomizer Table. It is variable to permit the user
		the set it up at any location in memory.
PRIM_RAND_LENGTH	32 Bits	Located on Fire-Hose 10K ASIC.
		User Readable
		This is the length in bytes of a primary
		randomizer Table for a single equation
PRIM_RAND_LOCATION	32 Bits	Located on Fire-Hose 10K ASIC. This register
		stores the location in the primary randomizer
		table that is being addressed by the primary
		randomizer Value
PRIM_RAND_ENTRY	16 Bits	The value that is stored in a primary randomizer
		Location.
MULT_TABLE_OFFSET	32 Bits	The Offset from the base primary randomizer
		Table Entry for the Multiple Entry Table.
		This is a fixed constant.
MULT_VALID_OFFSET	32 Bits	The Offset from the base primary randomizer
		Table Entry for the Multiple Entry Valid Table.
		This is a fixed constant.
TEMP_POINTER0	32 Bits	This pointer is used as a second pointer for
		creating new inputs in the primary Randomization
		Table.
TEMP_POINTER1	32 Bits	This pointer is used as a third pointer for creating
		new inputs in the primary Randomization Table
TEMP_VALUE0	16 Bits	This register is used as a temporary 16 bit
		storage for SRAM reads.
TEMP_VALUE1	16 Bits	This register is used as a temporary 16 bit
		storage for SRAM reads.
TEMP_ENCODE0	5 Bits	This is an encoded value showing the lowest
		unused position in a 16 bit word. The 5th bit is
		used to signify that there are none available.
TEMP_ENCODE1	5 Bits	This is an encoded value showing the lowest
		unused position in a 16 bit word. The 5th bit is
		used to signify that there are none available.
TEMP_COUNT	16 Bits	This is a temporary counter used to help walk
		through the Multiple Tables.

Registers Associated with Initializing all Randomizer Mappings

[0304] The following registers are associated with clearing out a randomizer table and with clearing out the multiple table entries for any equation. Due to the fact that the system may be dynamically clearing out an equation entry in the middle of updating new equations, it is important that there be independent registers to point into the SRAM for the initialization process (see Table BK below).

[0305]

TABLE BK
Randomizer Initialization Registers
NAME	SIZE	COMMENTS
RAND_INIT_VALUE	16 Bits	This is the value that will be stored into memory
		for the randomizer table during initialization.
RAND_INIT_ADDRESS	32 Bits	This is the present address in the randomizer
		table that initialization values are being stored
		into.
RAND_INIT_COUNT	16 Bits	This is a counter variable used in clearing out a
		randomizer Table Value.
RAND_INIT_EQ	8 Bits	This is used to maintain the equation number of a
		randomizer Table that is being cleared.

Processes for Randomizer Table Manipulations

[0306] There are a number of independent operations to manipulate the primary randomizer tables. These involve initialization, storage and retrieval of data (see Table BK below).

[0307]

TABLE BK
Processes for randomizer Table Manipulations
Process Name	Type	Description
RAND_INIT	Internal	Used to Initialize and clear out a randomizer
		Table for one specific equation.
PRAND_ADD_ENTRY	Internal	Adds a randomizer Table Entry for a single
		equation and mapping.
GET_NEW_MULT_ENTRY	Internal	Used to find and tag the next available Multiple
		Table Entry for the specific equation that is being
		operated on.
PRAND_SUB_ENTRY	Internal	Subtracts an input value from the primary
		randomizer Table for a single equation and
		mapping.
CLEAR_MULT_ENTRY	Internal	Used to free up a Multiple Table Entry location.
IDENTIFY_MULT_INPUT	Internal	Used to identify the position in a Multiple Table
		Entry where the specific input or mask step is
		located.

Mapper Engine, Statistics and Equation State Machine

[0308] The purpose of the mapper engine, statistics, and equation state machine is to cycle through the various equation mappings for new inputs, maintain statistics for each equation mapping, select the appropriate equations to use, and initiate swapping out equations that do not produce appropriate mappings. This block has a state machine that operates on inputs across all equations. It implements counters in hardware to maintain statistics for each equation.

Primary Randomizer Equation Analysis

[0309] The system maintains data for a total window of eight primary randomizer equations on-chip. The system selects between these eight mappings to pick the best one using a variety of characteristics. Each of these equations have counters associated with the number of triples, quadruples, or overflow values that they contain. Based upon programmable criteria (values written into registers), the user can decide how often an equation is deemed to be non-usable and a search is initiated for a replacement. This directly affects power consumption because any time a search for a better equation is done, there are a large number of accesses to DRAM. On the flip side of the equation, when the equation set is static, there is extremely low power consumption from the custom ASIC.

Equation Status Counters

[0310] The following set of counters (Table BL below) is maintained for each equation on the custom ASIC. The output of these registers is used to determine the best equation for use, and whether certain equations need to be switched out.

[0311]

TABLE BL
Equation Status Counters/Registers
Register Name	Bits	Description
EQ0_TRIPS	8	Counts the number of triples for equation 0
		A value of 255 disables the equation from use.
EQ0_QUADS	6	Counts the number of quadruples for equation 0
		A value of 63 disables the equation from use.
EQ0_MULTS	10	Counts the number of Multiple Entries for
		equation 0
		A value of 1023 disables the equation from use.
EQ0—	2	Counts the number of Overflow Entries for
OVERFLOW		equation 0.
		A value of 3 disables the equation from use.
EQ0—	1	Register bit to indicate whether the equation is
COMPLETE		complete in terms of implementing all inputs.
.	.	.
.	.	.
.	.	.
EQ7_TRIPS	8	Counts the number of triples for equation 7
EQ7_QUADS	5	Counts the number of quadruples for equation 7
		A value of 32 disables the equation from use.
EQ7_MULTS	10	Counts the number of Multiple Entries for
		equation 7
		A value of 1023 disables the equation from use.
EQ7—	2	Counts the number of Overflow Entries for
OVERFLOW		equation 7.
		A value of 3 disables the equation from use.
EQ7—	1	Register bit to indicate whether the equation is
COMPLETE		complete in terms of implementing all inputs.

[0312] The following error conditions are serious for a specific equation, and must be handled quickly by the custom ASIC:

• • [0313] The number of Overflow Entries (EQn_OVERFLOW) exceeds 0
  • [0314] The number of Multiple Entries (EQn_MULTS) exceeds 1024

[0315] In the worst case, a serious error results in an incoming packet not being identified by the custom ASIC. Any of the errors listed above would result in a vector not being found in the primary mapping table. A large majority of packets, i.e. 9999/10000, would still continue to be received as expected, and quickly, the chip would change the primary mapping equation to handle the serious fault.

Optimal Primary Equation Selection

[0316] The issues associated with picking the optimal primary equation are numerous. The greater the number of multiple entries, the longer the average lookup time is for the equation and the greater the probability that the multiple table entries is exceeded. The number of quadruples is an early indicator of possible problems because a quadruple is a single new input vector away from creating a serious error condition. Any equation that has reached an overflow condition for must be eliminated out of hand if possible. If no equation meets these criteria, then it is critical that the least offensive of the remaining equations be used. It is also critical that only equation mappings that contain all inputs be considered in this evaluation. This is necessary because there are times when equations are swapped out, and new ones are evaluated.

[0317] The following equation shows how the EQm_DISABLE bit is calculated. This bit is necessary to be able to shut down the use of equations that are inappropriate. The thresholds for quadruples and triples have been set to very high levels that have an extremely low probability of occurrence in real life, and that pose a added burden to the receiver should they be used.
EQm_DISABLE=(EQm_OVERFLOW==3)∥
(EQm_MULTS==1023)∥
(EQm_QUADS==63)∥(EQm_TRIPS==255))

[0318] The equation optimization comparator input word for each of the eight possible equations has been designed so that the best equation is the one with the lowest word. This way, the eight equation optimization comparator input words can be sent through a 4->2->1 tree of 2:1 comparators to determine the optimal equation. In looking at the word, the highest priority for disqualification occurs when the equation table is incomplete. The second highest priority is that the equation has been disabled due to either overflow conditions or an excessive number of quadruple or triple matches. Next, the number of overflow conditions is used, which it is hoped is zero. The number of multiple inputs comes next in the priority structure, followed by the number of quadruples and triples in that order.

[0319] The equation optimization comparator produces the OPTIMAL_EQUATION output that signifies the best equation mapping at the present time (see Table BM).

[0320]

TABLE BM
Equation Optimization Comparator Inputs
(equation 0 Example)
Word
Section	MSB	LSB
EQm_INPUT	EQm—	EQm—	EQm—	EQm—	EQm—	EQm_TRIPS
	INCOMPLETE	DISABLE	OVERFLOW	MULTS	QUADS

[0321] The system identifies equations that are not usable, i.e. EQm_DISABLE==1, and determines when they reach a threshold programmed by the user (EQ_UPDATE_THRESH). When this threshold is reached, the system sets the EQm_INCOMPLETE bit for each disabled equation, clears out the disabled equations, and then updates the disabled equation (see Table BN below). This decision process also relies on equation aging which is described below.

[0322]

TABLE BN
Registers associated with Updating Equations
Address	Register Name	Bits	Notes
0xA0	EQ_UPDATE_THRESH	3	When this threshold is reached,
			the system will update all
			equations that have been
			disabled
	OPTIMAL_EQUATION	3	This is the output of the equation
			Optimization Comparator, and
			tells which of the equations is the
			best.
	SECOND_BEST_EQUATION	3	This is an output of the equation
			Optimization Comparator, and
			tells which of the equations is the
			second best.
	EQ_INPUT_COUNT	16	Used to count through the inputs
			when updating a set of equations
	EQ_POINTER	3	Points to the equation being
			operated on presently.
	PRIM_RAND_VALUE	16	primary randomizer value that is
			a latched value of the
			CALC_RANDOMIZER_VALUE
	SEC_RAND_VALUE	16	secondary randomizer value that is a
			latched value of the
			CALC_RANDOMIZER_VALUE

Method to Track Mappings to Equation Values

[0323] There are eight different primary equation mappings that are used at any time by the custom ASIC. These equations map to one of 128 equations that are implemented in the mapper, which in turn map to one of the 32768 possible feedback paths for the randomizers. Actually, the important thing is that one stores a secondary mapping with each table for reference, and a way to determine whether there are duplicates. Storing whether a secondary mapping produced a duplicate would require a new bit. Primary and secondary randomizer values must be stored in the equation map for use because it is necessary to have their mask impact bits available on custom ASIC. Therefore, one needs to make sure that recently used primary and secondary randomizer equations are available.

[0324] Table BO below lists the registers associated with storing the mapping information. These values can be directly applied to the mapper multiplexer to determine the value. The system has 128 possible mappings, and uses a total of eight equations that each correspond to one of the mappings. Any time that an equation is found to be bad, a value of eight is added to the equation number. This guarantees that one will never have two equations that map to the same value. At any given time, one should use the best available mapping as the secondary randomizer equation value for new equations. The odds of this equation going bad is significantly less than other equations in the table, and the problem of being forced to keep it around has similarly less impact.

[0325]

TABLE BO
Registers that Store the Relation between mapper values and Equations
Register Name	Bits	Notes
EQ0_PRIM_MAP	8	Value of 0–127 corresponding to the primary
		randomizer mapping used for equation 0.
EQ0_SEC_EQ_NUM	4	Identifies which of the 8primary map Equations is
		being used as the secondary randomizer
		equation for equation 0. The MSB signifies that
		the equation is no longer valid when it is set to a 1.
EQ1_PRIM_MAP	8	Value of 0–127 corresponding to the primary randomizer
		mapping used for equation 0.
EQ1_SEC_EQ_NUM	4	Identifies which of the 8primary map Equations is
		being used as the secondary randomizer
		equation for equation 1. The MSB signifies that
		the equation is no longer valid when it is set to a 1.
.	.	.
.	.	.
.	.	.
EQ7_PRIM_MAP	8	Value of 0–127 corresponding to the primary
		randomizer mapping used for equation 7.
EQ7_SEC_EQ_NUM	4	Identifies which of the 8primary map Equations is
		being used as the secondary randomizer
		equation for equation 7. The MSB signifies that
		the equation is no longer valid when it is set to a 1.

Maintenance of Equation Mappings

[0326] It is critical to maintain primary randomizer equation mappings that have been sent to the data framer for a reasonable time period. This is necessary to avoid a problem where an equation is swapped out and a value is read from the data framer that has no corresponding table for evaluation. In the case of parallel modes of operation, it is possible to use any of the equations and this is not a problem.

[0327] When a user is using the data framer, it is presumed that there is a time critical nature to the analysis of data packets. For this reason, it is possible to use a set of timers for each equation to indicate how long ago the equation was used in a data framer. These timers are a maximum of one second in length, and once one second has expired, the equation is considered as having been aged out. In the future, it may be valuable to permit a programmably variable shorter time to indicate that an equation has been aged out.

[0328] The equation aging registers are clocked at a 4 msec rate. When new primary and new secondary randomizer equations are written into the data framer, their equation aging registers are set to 0. The primary and secondary randomizer equations that are used for the data framer are be the ones used for parallel classification. All other equation aging registers are permitted to count upward. When an equation aging register counts up to a value of 255, it stops to signify that the counter has aged out (see Table BP below).

[0329]

TABLE BP
Registers Associated with equation Aging
Register Name	Bits	Notes
EQ0_AGING	8	8 bits of counter, and the MSB bit shows that the
		equation has aged out.
EQ1_AGING	8	8 bits of counter, and the MSB bit shows that the
		equation has aged out.
.	.	.
.	.	.
.	.	.
EQ7_AGING	8	8 bits of counter, and the MSB bit shows that the
		equation has aged out.

Processes Used for Mapping Analysis

[0330] There are a number of processes associated with initializing and maintaining information regarding the equations used by the system (see Table BQ below).

[0331]

TABLE BQ
Processes used for mapping Analysis
Process/Macro Name	Type	Description
INITIALIZE_ONE_EQ	Internal	Initializes the mapping and Statistics registers
		used for a single equation
INITIALIZE_ALL_EQ	Internal	Initializes all of the equations being used in
		the system.
ADD_INPUT_ALL_EQ	Internal	Handles mapping and storing an input for all
		sets of equations.
SUB_INPUT_ALL_EQ	Internal	Handles mapping and removing an input for
		all sets of equations.
UPDATE_DISABLED_EQS	Internal	This process is used to update equations that
		are no longer valid. It is not called until a
		certain programmable threshold of equations
		are disabled.

Time Accelerator Block

[0332] The purpose of the time accelerator block is to advance a received randomizer value through “n” cycles of time in a single hardware cycle on the custom ASIC. The custom ASIC is running at extremely high speeds, and it is desirable to shut down the randomizers whenever possible to avoid power consumption. The calculated randomizer values in the custom ASIC are based upon a 1024-bit input word being used for the calculations, with all 1024 input bits being shifted into the randomizer. The custom ASIC has been structured such that bits occurring after the user selected data length are set to zero in the calculation (see FIG. 16). Therefore, to produce an equivalent result the data framer would be required to clock in the equivalent number of trailing zeros to it's randomizer. This clocking of trailing zeros could result in significant power consumption, and would result in additional latency between the reception of the packet header and identification of the matching input.

[0333] To solve this problem, the time accelerator block has been added to the custom ASIC. This block is able to take a randomizer value and shift it forward by the equivalent of “n” cycles of zero clocked input data all within a single cycle. The theory behind this time acceleration revolves around the fact that any shift of “n” cycles can be viewed as a remapping of the initial state of the randomizer stage values (qinit0, qinit1, . . . qinit15). To shift forward by a specific time of “n” cycles requires a specific remapping of the initial values to the final values. To accomplish a variable shift of any chosen value of “n” cycles, the novel custom ASIC implements a binary weighted programmable shifter. To accomplish a variable shift of from 1 to 1024 bits in length, the system implements a 512-bit shifter, a 256-bit shifter, a 128-bit shifter, a 64-bit shifter, a 32-bit shifter, a 16 bit -shifter, an 8-bit shifter, a 4-bit shifter, a 2-bit shifter, and a 1-bit shifter. Based on the selected shift value “n”, each of these fixed shifter stages is either switched into the data path or bypassed. Each shifter stage relies entirely on its own inputs to produce a direct mapping to its own outputs. There is no interaction between groups of stages other than the fact that the individual stages are producing a one-to-one mapping of inputs to outputs. To simplify this block, and the time associated with making calculations, the time accelerator may be modified to advance in 32-bit increments only. This would permit 512-bit shifts, 256-bit shifts, 128-bit shifts, 64-bit shifts, and 32-bit shifts only, but does nothing to affect the theory of operation for this block.

Time Accelerator Register

[0334] The TIME_ACC_CYCLE is used to setup the number of cycles of acceleration to be applied to a received randomizer value. The source of the time accelerator block is chosen by the RANDOMIZER_SELECT value that chooses between the primary and secondary randomizer values that have been received. The equation that is being used in the analysis of the randomizer is critical for determining the mapping, and it is stored in the EQUATION_STORE_ENTRY register (see Table BR below).

[0335]

TABLE BR
Registers associated with Time Acceleration
Register Name	Bits	Notes
TIME_ACC—	10	Value of 0 to 1023 that contains the number of
CYCLE		cycles that the primary and secondary
		randomizers need to be advanced through under
		the condition of having a zero input.

Time Accelerator Logic Stage

[0336] The preferred implementation of one of the time accelerator stages using a large number of XOR gates and a smaller number of multiplexers (see FIG. 14). The input to the stage is qstagein[15:0] which can be either the output of a previous stage, or an actual randomizer value. The stage consists of 128 mappings of qstagein[15:0] to qstageout[15:0] to handle each of the possible equation mappings. Each of the bits in qstageout[15:0] is a function of qstagein[15:0], and can be implemented with an XOR tree of all of the applicable bits. For instance, qstageout[0] may be qstagein[0]+qstagein[3]+qstagein[7]+qstagein[1] which can be implemented with XOR gates. Each of the possible outputs is a function of qstagein[n], and uses half of the inputs on average. Once the outputs for all 128 equations have been calculated, a 128:1 multiplexer chooses the correct output for the equation being considered.

[0337] The example above shows how an individual bit in the output is calculated. This is multiplied by sixteen to handle each output bit in the remapping situation. The benefit of this approach is that the XOR trees for all of the equations, and for all of the output bits are shared. There is a limit to how many XOR gates can be used when there are a total of only sixteen inputs.

[0338]

TABLE BS
Size for 16 Bits
					Max	Max XOR	XOR
					Output	Terms Per	Gates/Level
	Inputs	Output	Maximum	Number of	Terms	Block	(*Number of
	per	Terms from	XOR Terms	Blocks for	limited by	Limited by	Blocks for
Level	Block	each Block	Per Block	16 Inputs	Equations	Equations	16 Inputs)
1	2	3	1	8	3	1	8
2	4	15	9	4	15	9	36
3	8	255	225	2	128	128	256
4	16	65535	65025	1	128	128	128
Maximum Total XOR Gates Per Stage	428

[0339] This approach uses a maximum of 428 XOR gates in it's implementation for the entire stage, and it uses only 16×128:1 multiplexers which each contain 127 2:1 multiplexers. This is a total of 2,460 gates per timing accelerator stage.

Overall Timing Accelerator Architecture

[0340] The timing accelerator (See FIG. 15) uses a total of ten programmable shifter stages to calculate it's output. Each of these stages must be either passed through or bypassed to achieve the desired result.

Interface

[0341] The interface provides the functions of configuring the data framer and reading and interpreting data when a packet is received.

[0342] In configuring the data framer, the data length must be provided. The INPUT_DATA_LENGTH register described herein must be transferred to the data framer upon initialization

[0343] In configuring the data framer, a set of masking registers need to be initialized. The MASK_OFF_CYCLE_REG and MASK_ON_CYCLE_REG registers are described herein. In addition, MASK_REGISTER_0, MASK_REGISTER_1, MASK_REGISTER_2 and MASK_REGISTER_3 are described in the context of their start values. These six masking registers have associated enable bits to determine whether or not they must be loaded into the data framer. All masking registers are expected to be loaded into the data framer upon initialization or reset, but are not expected to be changed during operation.

[0344] In addition to the MASK and length registers, the data framer randomizer feedback registers must be configured. These are described in Table BT below, and their calculation is described later in this discussion.

[0345]

TABLE BT
Additional Registers to be written into the data framer
for Configuration
Address	Register Name	Bits	Notes
0x00	PRIME_RAND—	16	Value to be latched into the
	FEEDBACK		data framer ASIC for the
			primary randomizer Feedback.
0x01	SEC_RAND—	16	Value to be latched into the
	FEEDBACK		data framer ASIC for the
			secondary randomizer
			Feedback.

[0346] In receive mode, the custom ASIC latches data from the data framer so that it can be analyzed. A FIFO structure may be necessary to permit packets to back up if necessary. With the new parallel mode of operation, it becomes more likely that an operation may preclude immediate access to the randomizer state machines because many channels could be using the same custom ASIC. Ideally, the interface always has the highest priority because it is the high performance interface. The implementation that is listed below supports storing a single register snapshot, but it could be easily increased to being a set of FIFOs.

[0347] In receive mode, the received randomizer values must be read from the data framer. The discussion herein describes the PRIM_RANDOMIZER_RX and the SEC_RANDOMIZER_RX registers that contain these two values. In addition, mask capture data must be received from the data framer, and this is stored in the MASK_CAPTURE_DATA_0, MASK_CAPTURE_DATA_1, MASK_CAPTURE_DATA_2 and MASK_CAPTURE_DATA_3 registers that are described herein.

[0348] Finally, the custom ASIC must know the randomizer feedback values that were used in calculating the primary and secondary randomizer values. If the feedback values have changed because the last packet, then a flag is set in the interface to show that these should be read. Otherwise, the custom ASIC can chose not to read these values. The description of these registers is found in Table BU below.

[0349]

TABLE BU
Additional Registers to be read from the data framer
Address	Register Name	Bits	Notes
0x02	FLAME_PRIM_FB	16	randomizer feedback from the
			data framer ASIC that was used
			to calculate the primary
			randomizer value.
0x03	FLAME_SEC_FB	16	randomizer feedback from the
			data framer ASIC that was used
			to calculate the secondary
			randomizer value.

Equation Recovery Section

[0350] The feedback value that is returned from the data framer must be converted into a relative equation number from 0 to 7 that points to a primary randomizer table. To execute this feature, eight feedback register values must be stored along with their equation mapping (see Table BV below and FIG. 16).

[0351]

TABLE BV
Registers associated with equation Recovery
Register Name	Bits	Notes
EQ0_FEEDBACK	16	EQ0 primary randomizer Feedback
EQ1_FEEDBACK	16	EQ1 primary randomizer Feedback
.
.
.
EQ7_FEEDBACK	16	EQ7 primary randomizer Feedback
EQ_REC_SEL	1	Selects the randomizer feedback source to be
		used to determine the original equation.
PRIM_RAND—	4	The equation Number for the primary
EQ_NUM		randomizer in the data framer ASIC.
		MSB indicates validity.
SEC_RAND_EQ—	4	The for the secondary randomizer in the data
NUM		framer ASIC.
		MSB indicates validity.

Randomizer Setup Section

[0352] Given the equation number, the proper EQn_FEEDBACK register can be selected to drive the data framer. This section shares the equation feedback registers with the equation recovery section. The OPTIMAL_EQUATION is driven in logic, and it is used to select the PRIM_RAND_FEEDBACK (see FIG. 17). At the time that the primary randomizer table is stored for the OPTIMAL_EQUATION, a specific secondary randomizer is used, and this is stored in the EQ[OPTIMAL_EQUATION]_SEC_EQ_NUM register. The frequency that the PRIM_RAND_FEEDBACK and SEC_RAND_FEEDBACK is updated with the UPDATE_FEEDBACK signal is no faster than the time required to load, calculate, and store or remove an input value. The feedback values only need to be updated when a change is made to the randomizer tables.

Processes Associated with the Interface

[0353] The updating of the interface registers should be done as infrequently as possible to avoid churning. When a new equation is desired, new feedback registers must be latched into the data framer. On initialization, it is also necessary to load masking registers into the data framer.

Detailed State Diagrams

[0354] In all cases below, the process implementation tables are organized in the form: State name—activity—next state, whether or not status indicated in a Table heading.

State Machines for the “Input Manager Control and State Machines” Block

[0355] The following state machines are used to manage the user inputs in the system (see Tables BW-CN below).

[0356]

TABLE BW
INPUT_VALID_INIT - Process Description
Process Name	INPUT_VALID_INIT
Process Function	This Process is called to initialize the Input Valid
	Table so that all entries are 0. This reflects the fact that
	at power up, there are no input values stored
	in the system.
Return Value(s)	none
Required Inputs	none
Modified	INPUT_STRUCT_PTR
Registers	INPUT_VALID array
	INPUT_CONTROL_REG
Error Conditions	None

[0357]

TABLE BX
INPUT_VALID_INIT - Process Implementation
STATE NAME	ACTIVITY	NEXT STATE
IDLE	If the Input Control Register Command	START
	field is set to “Initialize Input Valid	PROCESS
	Array”. Set the “Command Complete”
	bit to a 0 to signify that the system is
	Initializing.
	Else	IDLE
START_PROCESS	Load the INPUT_VALID_BASE into	CLEAR_ARRAY
	INPUT_STRUCT_PTR. The
	INPUT_STRUCT_PTR now points to
	the first location in the
	INPUT_VALID array.
CLEAR_ARRAY	Write a 0 into the 32 bit location	INCREMENT_SEARCH
	addressed by the
	INPUT_STRUCT_PTR.
INCREMENT_SEARCH	Add a value of 4 to the	CONDITION_PTR
	INPUT_STRUCT_PTR.
CONDITION_PTR	Check the value that is stored in the
	INPUT_STRUCT_PTR location.
	If INPUT_STRUCT_PTR>=	IDLE
	{INPUT_VALID_BASE+313}
	Set the “Command Complete” bit in the
	INPUT_CONTROL_REG to a 1 to show
	that the initialization is completed.
	Else	CLEAR_ARRAY
	This is a valid value, and the system will
	continue initializing