Title of Invention	REDUNDANT PROCESSOR SYSTEM, TIME RESPONSE SYSTEM AND METHOD FOR RESPONDING TO A TIME OF DAY REQUEST
Abstract	In an implementation of time of day response, time logic (310) executed by each processor element (304) of a logical processor (112) generates a logical time in response to a time of day request. The logical time is generated to approximate the actual time such that each processor element (304) of the logical processor (112) returns the same logical time.

Full Text

TIME OF C TECHNICAL FIELD [0001] This invention relates to time of day response. BACKGROUND [0002] Multiple redundant processor systems are implemented as fault-tolerant systems to prevent downtime, system outages, and to avoid data corruption. A multiple redundant processor system provides continuous application availability and maintains data integrity such as for stock exchange systems, credit and debit card systems, electronic funds transfers systems, travel reservation systems, and the like. In these systems, data processing computations can be performed on multiple, independent processing elements of a processor system. [0003] Processors in a multiple redundant processor system can be loosely synchronized in a loose lock-step implementation such that processor instructions are executed at slightly different times. This loosely synchronized implementation provides that the processors can execute instructions faster than a typical tight lock-step configuration because the processors are not restricted to synchronized code execution. However, when an application requests a time of day response to time-annotate a banking or stock transaction, for example-, the redundant processors all execute the same instruction set in response to the request, but may alt return a different time of day response. The different time responses will appear as an error to the application that has requested the time of day. Case 200400432-1 BRIEF DESCRIPTION OF THE DRAWINGS [0004] The same numbers are used throughout the drawings to reference like features and components: Fig. 1 illustrates an exemplary redundant processor system in which an embodiment of time of day response can be implemented. Fig. 2 further illustrates various components of the exemplary redundant processor system shown in Fig, 1. Fig. 3 illustrates various components of an exemplary redundant processor system in which embodiments of time of day response can be implemented. Fig. 4 is a flow diagram that illustrates an embodiment of a method for time of day response. Fig. 5 is a flow diagram that illustrates an embodiment of a method for time of day response. DETAILED DESCRIPTION [0005] The following describes embodiments of time of day response. Time of day logic is implemented in a redundant processor system to generate a logical time in response to a time of day request, such as from an application that controls or is implemented in a stock exchange system, a credit and debit card system, an electronic funds transfers system, a travel reservation system, an electronic mail system, cellular telephone application, and the like. The logical time is generated as an approximation of the real time, and such that each processor element of a logical processor in the Case 200400432-1 redundant processor system returns the same logical time in response to a time of day request [0006] Although a logical time response is only an approximation of the actual time in a loosely-synchronized redundant processor system, it can be a close approximation, such as within a few microseconds, that does not affect the application requesting the time of day. For example, a banking or stock transaction may be recorded to within one second, one-tenth of a second, or even one-hundredth of a second of the transaction time which is determinable from an approximate logical time that is within a few microseconds of the actual time. [0007] Although embodiments of time of day response may be implemented in various redundant processor systems, time of day response is described with reference to the following processing environment in which the actual time can be approximated for loosely-synchronized processor elements. The actual time is approximated as a logical time such that the processor elements do not suffer the performance impact of having to request the actual time from a common source each time that a request for the time of day is received. [0008] Fig. 1 illustrates an example of a redundant processor system 100 in which an embodiment of time of day response can be implemented. The redundant processor system 100 includes a processor complex 102 which has processor groups 104(1-3). Each processor group 104 includes any number of processor elements which are each a microprocessor that executes, or processes, computer executable instructions. Processor group 104(1) includes processor elements 106(1-N), processor group 104(2) Case 200400432-1 includes processor elements 108(1-N), and processor group 104{3) Includes processor elements 110(1-N). Although the processor complex 102 includes only three processor groups 104(1-3) in this embodiment of time of day response, a processor complex may include two, four, or any other combination of processor groups. [0009] Processor elements, one each from the processor groups 104(1-3), are implemented together as a logical processor 112(1-N). For example, a first logical processor 112(1) includes processor element 106(1) from processor group 104(1), processor element 108(1) from processor group 104(2), and processor element 110(1) from processor group 104(3). Similarly, logical processor 112(2) includes processor elements 106(2), 108(2), and 110(2), while logical processor 112(3) includes processor elements 106(3), 108(3), and 110(3). [0010] The three processor elements combine to implement a logical processor 112 and cooperate to perform the computations of the logical processor 112. Logical computations for an input / output operation or an interprocessor communication are executed separately three times in a logical processor 112, once each in the three processor elements of the logical processor 112. Additionally, the three processor elements in a logical processor 112 can coordinate and synchronize with each other to exchange data, replicate input data, and vote on input / output operations and communication outputs. [0011] Each processor group 104(1-3) has an associated memory component 114(1-3), respectively. A memory component 114 can be implemented as any one or more memory components, examples of which Case 200400432-1 include random access memory (RAM), DRAM, SRAM, a disk drive, and the like. Although the memory components 114(1-3) are illustrated as independent components, each processor group 104 can include a respective memory component 114 as an integrated component in an alternate embodiment. [0012] In this example, processor complex 102 is a triplex redundant processor system having triple modular redundancy in that each logical processor 112 includes three redundant processor elements. A faulty processor element can be replaced and reintegrated into the system while the redundant processor system 100 remains on-line without a loss of processing capability to provide data integrity. [0013] The processor elements of a logical processor 112 are loosely synchronized in a loose lock-step implementation such that instructions may be executed, or processed, in each of the processor elements at a slightly different time. This implementation provides that the logical processors can execute instructions faster than a typical tight lock-step configuration because the processor elements and logical processors 112 are not restricted to synchronized code execution. This implementation also provides for non-deterministic execution among the processor elements, in a logical processor, such as non-deterministic branch prediction, cache replacement algorithms, and the like. The individual processor elements can also perform independent error recovery without losing synchronization with the other processor elements. [0014] Fig. 2 further illustrates various components 200 of the redundant processor system 100 shown in Fig. 1. The processor elements Case 200400432-1 106(1-N) of processor group 104(1) are shown, one each of a respective logical processor 112(1-N). Each processor element 106(1-N) is associated with a respective memory region 202(1-N) of the memory component 114(1) for data storage. The memory component 114(1) associated with processor group 104(1) is partitioned among the processor elements 106(1-N) of the processor group 104(1). In an alternate embodiment, each memory region 202(1 -N) can be implemented as an independent, separate memory for data storage. Although not shown, the processor elements 108(1-N) of processor group 104(2) are each associated with a respective partitioned memory region of the memory component 114(2). Similarly, the processor elements 110(1-N) of processor group 104(3) are each associated with a respective partitioned memory region of the memory component 114(3). [0015] Each of the logical processors 112(1-N) correspond to one or more respective logical synchronization units 204(1-N). A logical synchronization unit 204 performs various rendezvous operations for an associated logical processor 112 to achieve agreements on synchronization issues between the processor elements that cooperate to form a logical processor 112. For example, input / output operations and/or interprocessor communications can be communicated from each processor.element of a logical processor 112 to an associated logical synchronization unit 204 to compare and vote on the input / output operations and/or interprocessor communications generated by the processor elements. [0016] A rendezvous operation may further be implemented by a logical synchronization unit 204 to exchange state information and/or data among the processor elements of a logical processor 112 to synchronize operations and Case 200400432-1 responses of the processor elements. For example, a rendezvous operation may be implemented such that the processor elements deterministically respond to incoming asynchronous interrupts, to accommodate varying processing rates of the processor elements, to exchange software state information when performing operations that are distributed across the processor elements, and the like. [0017] Fig. 3 illustrates various components of an exemplary redundant processor system 300 in which embodiments of time of day response can be implemented. The redundant processor system 300 includes various components of the redundant processor system 100 shown in Figs.1 and 2, such as the multiple logical processors 112(1-N) and the associated logical synchronization units 204(1-N). For illustration, however, only one logical processor 112 and one associated logical synchronization unit 204 is shown in Fig. 3. The logical synchronization unit 204 may be implemented as described with reference to the logical synchronization units 204(1 -N) shown in Fig. 2. In this embodiment, the logical synchronization unit 204 includes an actual time register 302 which is a register that consistently increments at a specific frequency, independent of other operations, to track the actual time. [0018] The logical processor 112 includes processor elements 304(1-3) which are each a microprocessor that executes, or processes, computer executable instructions. The redundant processor system 300 includes the memory components 114(1-3) that are each associated with a respective processor group 104(1-3) as shown in Fig. 1. Each of the processor elements 304(1-3) are one of the processor elements in a respective processor group, and each processor element 304 is associated with a partitioned memory Case 200400432-1 region in a respective memory component 114(1-3). For example, processor element 304(1) corresponds to memory region 306(1) in memory component 114(1), processor element 304(2) corresponds to memory region 306(2) in memory component 114(2), and processor element 304(3) corresponds to memory region 306(3) in memory component 114(3). [0019] The memory regions 306(1-3) form a logical memory 308 that corresponds to logical processor 112. The processor elements 304(1-3) of the logical processor 112 each correspond to a respective partitioned memory region 306(1-3) of the logical memory 308. [0020] The memory components 114(1-3) each include time of day logic 310(1-3) that corresponds to a respective processor element 304(1-3) of the logical processor 112. In this example, the time of day logic 310(1-3) is implemented as a software application and is stored in the memory components 114(1-3). Each of the processor elements 304(1-3) execute an instantiation of the time of day logic 310 (e.g., as software) to implement time of day response. [0021] As used herein, the term "logic" (e.g., the time of day logic 310, or components thereof) can also refer to hardware, firmware, software, or any combination thereof that may be implemented to perform the logical operations associated with time of day response. Logic may also include any supporting circuitry utilized to complete a given task including supportive analog operations. For example, logic may also include analog circuitry, memory components, input/output (I/O) circuitry, interface circuitry, power providing/regulating circuitry, and the like. Case 200400432-1 [0022] The time of day logic 310(1-3) generates a logical time in response to a time of day request, such as from an application that time-annotates a banking or stock transaction. The logical time is generated as an approximation of the real, or actual time, and such that each processor element 304(1-3) returns the same logical time in response to a request Although a logical time response is only an approximation of the actual time, it can be a very close approximation (e.g., within a few microseconds) and does not affect the application that requests the time of day. In practice, a banking or stock transaction can be recorded to within one second, one-tenth of a second, or even one-hundredth of a second of the transaction which is determinable from a logical time that is within a few microseconds of the actual time. [0023] The memory components 114(1-3) also each include logical time registers 312(1-3), response counters 314(1-3), and time response flags 316(1-3) each corresponding to one of the respective processor elements 304(1-3). A logical time register 312 maintains the current logical time, such as the last logical time generated In response to a time of day request. When a time of day request is received, the time of day logic 310 reads the current logical time maintained by the logical time register 312 and, in one embodiment, increments the current logical time and returns the incremented logical time. The time of day logic 310 then stores the incremented logical time as the current logical time (e.g., the last logical time response) in the logical time register 312. The logical time can be fncremented by any integer or fraction thereof providing that each processor element 304(1-3) increments the logical time deterministically and returns the same logical time in response Case 200400432-1 to a request The incremental value of the logical time can be situation, application, and/or implementation specific. [0024] Each time that the time of day logic 310(1-3) corresponding to a respective processor element 304(1-3) responds to a request with a logical time, the time of day logic 310(1-3) increments the respective response counter 314(1-3). The response counter is reset (e.g., to zero, or to a similarly determinable logic state) when the time of day logic 310 obtains the actual time and/or when the actual time is provided, such as from the actual time register 302 in the logical synchronization unit 204. The time of day logic 310(1-3) monitors the respective response counter 314(1-3) and obtains the actual time when the counter meets or exceeds a set number of responses. The number of responses is implementation specific, as well as whether to initiate obtaining the actual time when the counter meets or exceeds the determined number of responses. [0025] The logical synchronization unit 204 provides the actual time from the actual time register 302 when requested from the time of day logic 310(1-3). Alternatively, the logical synchronization unit 204 can provide the time of day when responding to any other synchronization operation, such as interrupt handling for the processor elements 304(1 -3). , .. [0026] When the actual time is obtained or received, the time of day logic 310(1-3) determines whether the current logical time maintained by the respective logical time register 312(1-3) is greater than or less than the actual time. If the current logical time is less than the actual time, the respective time response flag 316(1-3) is set to a logic state (e.g., logic state one) and the logical time is set equal to the actual time. When the time of day logic Case 200400432-1 310(1-3) next responds to a request for the time of day, the current logical time can be incremented to approximate the actual time accordingly. As described above, the current logical time can be incremented by any integer or fraction thereof providing that each processor element 304(1-3) increments the logical time deterministically and returns the same logical time in response to a request. The incremental approximations are implementation specific and can be determined to best approximate and track the actual time with respect to the particular application(s) that may be requesting a time of day response from the redundant processor system 300. [0027] If the current logical time maintained by a logical time register 312(1-3) is greater than the actual time when the actual time is obtained or received, the respective time response flag 316(1-3) is set to a logic state (e.g., logic state zero) to indicate that the current logical time is not to be incremented when the time of day logic 310(1-3) next responds to a request for the time of day. In response to a request for the time of day, the current logical time is returned as a static value (e.g., does not go backwards in time, but may be returned as the same value multiple times which is non-increasing) to allow the actual time to advance up to and/or past the current logical time. [0028] The processor elements 304(1-3) of the logical processor 112 are not clock synchronized and a time of day value generated by one processor element 304 would differ from the other processor elements. The logical synchronization unit 204 maintains the actual time with actual time register 302 from which the processor elements can obtain the actual time. However, applications may request the time of day so often that processor Case 200400432-1 performance in the redundant processor system is degraded when the processor elements continually request and coordinate the actual time from the logical synchronization unit 204. Accordingly, the time of day logic coordinates the processor elements 304(1-3) to respond to time of day requests with a deterministic extrapolated value that is a logical time which represents an approximation of the actual time. [0029] Methods for time of day response, such as exemplary methods 400 and 500 described with reference to Figs. 4 and 5, respectively, may be described in the general context of computer executable instructions. Generally, computer executable instructions include routines, programs, objects, components, data structures, procedures, modules, functions, and the like that perform particular functions or implement particular abstract data types. The methods may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices. [0030] Fig. 4 illustrates an embodiment of a method 400 for time of day response. The order in which the method is described, is not intended to be construed as a limitation, and any number of the described method blocks may be combined in any order to implement the method. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof. [0031] At block 402, a request for a time of day is received. In response to the request, the time of day logic 310(1-3) (Fig. 3) generates a Case 200400432-1 logical time to approximate an actual time. At block 404, a determination is made as to whether a response counter exceeds a set number of responses to time of day requests. If the response counter does exceed the set number of responses (i.e., "yes" from block 404), then the method can proceed to Fig. 5 to obtain an actual time update. As described above, the number of responses is implementation specific, as well as whether to initiate obtaining the actual time when the counter meets or exceeds the determined number of responses. When an actual time update is obtained as described with reference to Fig. 5, the method returns to block 406 to respond to the time request received at block 402. [0032] If the response counter does not exceed the set number of responses (i.e., "no" from block 404), then a determination is made as to whether the logic state of the time response flag indicates that the logical time is less than the actual time at block 406. In this example, a logic state one indicates that the logical time is less than the actual time. If the logical time is less than the actual time (e.g., the time response flag indicates a logic one state) (i.e., "yes" from block 406), then the current logical time maintained by the logical time register is incremented at block 408. At block 410, the logical time maintained by the logical time register is returned as the logical time response to the time of day request. In this example, the logical time response is the incremented current logical time from block 408. At block 412, the response counter is incremented. The time of day logic 310(1-3) increments the respective response counter 314(1-3) to track the number of logical time responses. Case 200400432-1 [0033] If the logical time is greater than the actual time (e.g., the time response flag indicates a logic zero state) (i.e., "no" from block 406), then the logical time maintained by the logical time register is returned as the logical time response to the time of day request at block 410. In this example, the logical time is greater than the actual time. Accordingly, the current logical time maintained by the logical time register is not incremented, and the logical time response is the same as for a previous logical time response. This provides that the current logical time is returned as a static value (e.g., does not go backwards in time, but may be returned as the same value multiple times which is non-increasing) to allow the actual time to advance up to and/or past the current logical time. Again, at block 412, the response counter is incremented. [0034] Fig. 5 illustrates an embodiment of a method 500 for time of day response. The order in which the method is described is not intended to be construed as a limitation, and any number of the described method blocks may be combined in any order to implement the method. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof. [0035] At block 502, the actual time is obtained .or received. For example, the time of day logic 310(1-3) (Fig. 3) can obtain the actual time of day from the logical synchronization unit 204 which maintains the actual time with actual time register 302. Alternatively, the logical synchronization unit 204 may provide the actual time of day according to actual time register 302 when responding to any other synchronization operation, such as interrupt handling. At block 504, the response counter is reset (e.g., to zero). Case 200400432-1 [0036] At block 506, a determination is made as to whether the logical time is less than the actual time obtained or received at block 502. If the logical time is less than the actual time (i.e., "yes" from block 506), then a time response flag is set to a logic state (e.g., a logic state one) that indicates the logical time is less than the actual time at block 508. In this example, a logic state one indicates that the logical time is less than the actual time. At block 510, the logical time is set equal to the actual time obtained or received at block 502 to update the logical time. In an event that a long duration elapses between requests for the time, the actual time may advance well ahead of the logical time and the logical time is updated accordingly, [0037] If the logical time is not less than the actual time (e.g., the logical time is greater than the actual time) (i.e., "no" from block 506), then the time response flag is set to a logic state (e.g., a logic state zero) that indicates the logical time is greater than the actual time at block 512. In this example, a logic state zero indicates that the logical time is greater than the actual time. The logic state zero of the time response flag is an indication to the time of day logic 310(1-3) for each respective processor element 304(1-3) not to increment the current logical time when a time of day request is received, and to return the non-incremented current logical time. [0038] Although embodiments of time of day response have been described in language specific to structural features and/or methods, it is to be understood that the subject of the appended claims is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as exemplary implementations of time of day response. Case 200400432-1 CLAIMS 1. A redundant processor system (300), comprising: a logical processor (112) that includes processor elements (304); and time logic (310) executed by each processor element (304) of the logical processor (112), the time logic (310) configured to generate a logical time in response to a time of day request, the logical time being generated to approximate the actual time such that each processor element (304) of the logical processor (112) returns a same logical time. 2. A redundant processor system (300) as recited in claim 1, further comprising a logical time register (312) configured to maintain a current logical time, and wherein the time logic (310) is further configured to determine whether to increment the logical time register (312) to generate the logical time in response to the time of day request. 3. A redundant processor system (300) as recited in claim 1, further comprising a logical time register (312) configured to maintain a current logical time, and wherein the time logic (310) is further configured to: obtain an actual time; determine whether the current logical time is less than the actual time; and increment the logical time register (312) to generate the logical time if the current logical time is less than the actual time. Case 200400432-1 4. A redundant processor system (300) as recited in claim 1, further comprising a logical time register (312) configured to maintain a current logical time, and wherein the time logic (310) is further configured to: obtain an actual time; determine whether the current logical time is greater than the actual time; and return the current logical time if the current logical time is greater than the actual time. 5. A time response system (300) comprising time logic (310) configured to generate a logical time in response to a time of day request, the logical time being generated to approximate actual time such that each processor element (304) that executes the time logic (310) in a logical processor (112) returns a same logical time in response to the time of day request. Case 200400432-1 6. A time response system (300) as recited in claim 5, wherein the time logic (310) is further configured to: determine whether a response counter (314) exceeds a set number of logical time responses; obtain an actual time if the response counter (314) exceeds the set number of logical time responses; determine whether a current logical time is less than the actual time; and update the current logical time to the actual time if the current logical time is less than the actual time. 7. A time response system (300) as recited in claim 5, wherein the time logic (310) is further configured to: determine whether a response counter (314) exceeds a set number of logical time responses; obtain an actual time if the response counter exceeds the set number of logical time responses; determine whether a current logical time is less than the actual time; and increment a logical time register (312) to generate the logical time if the current logical time is less than the actual time. Case 200400432-1 8. A method (400), comprising: receiving (402) a time of day request; generating (408) a logical time in response to the time of day request, the logical time being generated to approximate an actual time; and returning (410) the logical time such that each processor element (304) of a logical processor (112) returns a same logical time in response to the time of day request. 9. A method (400) as recited in claim 8, further comprising: maintaining (410) a current logical time; and determining (406) whether to increment the current logical time to generate the logical time. 10. A method (400) as recited in claim 8, further comprising: maintaining (410) a current logical time; determining (404) whether a response counter (314) exceeds a set number of logical time responses; obtaining (502) an actual time if the response counter (314) exceeds the set number of logical time responses; setting (508) a time response flag (316) to a logic state that indicates the current logical time is less than the actual time; and updating (510) the current logical time to the actual time according to the logic state of the time response flag (316)

Documents:

0858-che-2005-abstract.pdf

0858-che-2005-assignement.pdf

0858-che-2005-claims.pdf

0858-che-2005-correspondnece-others.pdf

0858-che-2005-description(complete).pdf

0858-che-2005-drawings.pdf

0858-che-2005-form 1.pdf

0858-che-2005-form 26.pdf

0858-che-2005-form 3.pdf

0858-che-2005-form 5.pdf

858-CHE-2005 AMENDED CLAIMS 31-12-2013.pdf

858-CHE-2005 AMENDED PAGES OF SPECIFICATION 31-12-2013.pdf

858-CHE-2005 AMENDED CLAIMS 05-01-2015.pdf

858-CHE-2005 CORRESPONDENCE OTHERS 02-01-2012.pdf

858-CHE-2005 EXAMINATION REPORT REPLY RECEIVED 05-01-2015.pdf

858-CHE-2005 EXAMINATION REPORT REPLY RECEIVED 31-12-2013.pdf

858-CHE-2005 FORM-1 31-12-2013.pdf

858-CHE-2005 FORM-13 31-12-2013.pdf

858-CHE-2005 FORM-13-1 31-12-2013.pdf

858-CHE-2005 FORM-3 31-12-2013.pdf

858-CHE-2005 FORM-5 31-12-2013.pdf

858-CHE-2005 OTHER PATENT DOCUMENT 31-12-2013.pdf

858-CHE-2005 OTHER PATENT DOCUMENT 1 31-12-2013.pdf

858-CHE-2005 OTHERS 31-12-2013.pdf

858-CHE-2005 POWER OF ATTORNEY 02-01-2012.pdf

858-CHE-2005 POWER OF ATTORNEY 05-01-2015.pdf

858-CHE-2005 POWER OF ATTORNEY 31-12-2013.pdf