DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Response to Arguments
Applicant's arguments filed 06/05/2026 have been fully considered but they are not persuasive.
Applicants argue (REMARKS, page 8) “First, Casu does not teach or suggest generating messages at "a fixed time interval". Casu describes an "output module that is configured to transmit absolute data...at a first rate." See Casu, paragraphs 10 and 31. That is, Casu does not teach or suggest generating messages at a fixed time interval but rather is concerned with an interval of transmission of absolute or incremental data.”
The Office respectfully disagrees. Casu clearly states (Fig. 3, 5, Para. [0029], [0046]) “An output module [output circuit] of the sensor 104a is coupled to receive the sensed signal and configured to transmit absolute data based on the sensed signal. Thus, the absolute data is indicative of the sensed parameter.” “Absolute data 310 takes the form of a SENT signal including individual SENT messages 310a-310c [messages]”) at a fixed time interval (Fig. 4, Para. [0031], [0047], [0052]: “absolute data in the form of SENT messages can be sent on the message line 106 every 128 microseconds [fixed time interval]” “The SENT messages 310a-310c can have a user specified tick time and message format.” Hence, a person of ordinary skill in the art is fairly informed by Casu’s teachings that “SENT messages” is generated at fixed time interval, “
t
S
E
N
T
” as the claim language requires.
Applicants additionally argue (REMARKS, page 8) “ITO does not teach or suggest generating messages independent of a target speed (or any parameter) and rather teaches sending/transmitting sensor data in response to a trigger signal. See ITO, page 1-3.”
The Office respectfully disagrees. ITO discloses (Fig. 3) a sensor output signal is generated “independent of the target speed” (page 6: “The first sensor 42 may be configured to output a sensor signal at regular intervals” regardless of (page 1, 3) “a rotation speed…related to a control target”)”. Casu and ITO are in the same field of endeavor generation and transmission/outputting sensed signals/parameters such as (see Casu Para. [0027]) “motion of the target, such as rotation and/or position of the target, such as an angular position, to name a few example” and (see ITO) “sensing element that detects current, speed, acceleration, angle, position, rotation direction, rotation speed, rotation angle, and the like.” Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention that the SENT signal/message in Casu et al.’s invention can be generated regardless of (page 1, 3) “a rotation speed…related to a control target” as taught by ITO, where doing so (ITO, page 2) “can reduce sensor output data latency…reduce or eliminate ambiguity in sensor output data age.”
Applicants further argue (REMARKS, page 8) “modifying Casu to include "a first sensor... configured to output a sensor signal at regular intervals" as discussed in ITO would entirely change the principle of operation of Casu.”
The Office respectfully asserts that it has not modified “Casu to include "a first sensor... configured to output a sensor signal at regular intervals" as discussed in ITO.” The Office simply states that the SENT signal/message generated at fixed time intervals in Casu et al.’s invention can be “independent of the target speed” as taught be ITO who also generated sensed output signals in the SENT format. The technical means for varying/adjusting the fixed time interval is required/recited by the claim language and thus viewed as a moot argument.
Applicants finally argue (REMARKS, page 9) “Casu does not teach a fixed interval to be stored in a programmable memory ("a programmable memory to store the fixed time interval") or adjusted via an external signal ("a terminal to receive a signal for adjusting the fixed time interval").”
The Office respectfully disagrees. Casu fairly teaches (Para. [0031], [0052], [0076]) the “SENT messages can be sent on the message line 106 every 128 microseconds” such as SENT message 400 including “Data portion 406” where “number of data nibbles will be fixed for each application but can vary between applications…The user can program a particular desired frame rate”…“Memory 534 can be configured to store various values for use during sensor operation, some of which can be user-programmable.” “EEPROM 634 can store operating values and parameters, such as output signal format, gain and offset correction coefficients, and harmonic correction parameters as examples.” Hence, Memory 534/634 may store different fixed time interval, “
t
S
E
N
T
”/ “frame rate” “which can be user-programmable”); and receive a signal for adjusting the fixed time interval (Fig. 5, 6, Para. [0052], [0076], [0102]: the different/desired fixed time interval, “
t
S
E
N
T
”/ “frame rate” values stored in the memory 534/634 is adjustable/selectable by choosing a value depending on application by receiving a signal). Hence, a person of ordinary skill in the art is fairly informed by Casu’s teachings that “SENT messages”/“output signal format” of different fixed time interval, e.g. “
t
S
E
N
T
,” can be stored in a programmable memory and adjusted/programmed by a user, depending on applications, by a signal received via a terminal of the programmable memory.
The office maintains its previous rejection as detailed below.
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
Claims 1-7, 13-23 and 27-30 are rejected under 35 U.S.C. 103 as being unpatentable over Casu et al. (US 20220239462 A1 previously cited) in view of ITO (JP 2015228171 A machine English translated previously provided).
Regarding Claim 1 and 17, Casu et al. discloses;
A sensor and associated method for detecting speed of a target (Fig. 1, 5, Para. [0026], [0073]-[0075]: “one or more integrated circuits (ICs) 104a-104n”; “a sensor IC 510…each of sensing elements 520a, 520b can sense a position and/or movement of target 514”), comprising:
one or more magnetic field sensing elements (Fig. 1, 5, Para. [0027]-[0028]: “Sensor 104a includes one or more sensing elements…”) operable to generate one or more magnetic field signals indicative of a magnetic field associated with the target having a speed (Fig. 1, Para. [0027]: “Sensor 104a includes one or more sensing elements configured to sense a parameter associated with a target (as shown in FIG. 5)…The sensed parameter can be motion of the target, such as rotation and/or position of the target, such as an angular position, to name a few examples.” “Sensor 104a further includes a processor coupled to the sensing element and configured to generate a sensed signal indicative of the parameter associated with the target. In the case of a magnetic field sensor for example, the sensed signal can be the output signal of a magnetic field transducer such as a Hall effect or magnetoresistance element”);
detection circuitry (Fig. 5, 6, Para. [0077], [0098]: digital processor 530/630) configured to detect one or more parameters of the target using the magnetic field signals or representations thereof (Para. [0028]: “Sensor 104a further includes a processor [digital processor 530/630] coupled to the sensing element and configured to generate a sensed signal indicative of the parameter associated with the target. In the case of a magnetic field sensor for example, the sensed signal can be the output signal of a magnetic field transducer such as a Hall effect or magnetoresistance element”); and
output circuit (Fig. 5, “Output module 540”) configured to generate messages (Fig. 3, Para. [0029], [0046]: “An output module [output circuit] of the sensor 104a is coupled to receive the sensed signal and configured to transmit absolute data based on the sensed signal. Thus, the absolute data is indicative of the sensed parameter.” “Absolute data 310 takes the form of a SENT signal including individual SENT messages 310a-310c [messages]”) at a fixed time interval (Fig. 4, Para. [0031], [0047], [0052]: “absolute data in the form of SENT messages can be sent on the message line 106 every 128 microseconds [fixed time interval]” “The SENT messages 310a-310c can have a user specified tick time and message format”; “The number of data nibbles will be fixed for each application but can vary between applications”. Hence, a SENT messages is generated at fixed time interval, “
t
S
E
N
T
”), each message conveying information about the one or more parameters of the target (Para. [0052]: “The SENT message 400 can include a sequence of pulses transmitted by the sensor IC 104a and in the example angle sensor, the target angle can be converted into the pulses with data encoded as falling to falling edge periods.” Hence each SENT message 310a to 310c conveys at least a target angle information), wherein the sensor further comprises at least one of:
a programmable memory (Fig. 5, 6: Memory 534/634) to store the fixed time interval (Fig. 5, 6, Para. [0002], [0052], [0076]: “The number of data nibbles will be fixed for each application but can vary between applications…The user can program a particular desired frame rate”…“Memory 534 can be configured to store various values for use during sensor operation, some of which can be user-programmable.” “EEPROM 634 can store operating values and parameters, such as output signal format, gain and offset correction coefficients, and harmonic correction parameters as examples.” Hence, Memory 534/634 may store different fixed time interval, “
t
S
E
N
T
”/ “frame rate” “which can be user-programmable”); and
…receive a signal for adjusting the fixed time interval (Fig. 5, 6, Para. [0052], [0076], [0102]: the different/desired fixed time interval, “
t
S
E
N
T
”/ “frame rate” values stored in the memory 534/634 is adjustable/selectable by choosing a value depending on application by receiving a signal).
Casu et al. does not explicitly state that the signal for choosing/adjusting/selecting the different/desired fixed time interval, “
t
S
E
N
T
”/ “frame rate” values from the memory is performed via:
“a terminal.”
However, Casu et al. teaches (Fig. 5, 6, Para. [0032], [0076]) “a bidirectional format (e.g., a triggered SENT or Manchester format) may be used by the IC 104a to transmit data to the ECU 102 on the message line 106 after receiving a request from the ECU 102.” “Memory 534 can be configured to store various values for use during sensor operation, some of which can be user-programmable.” In other words, the memory 534/634 is configured to be accessible (reading and writing) for programming/storing/retrieving the different/desired fixed time interval, “
t
S
E
N
T
”/ “frame rate” values by providing a signal to choose/adjust/select/change a value among the “various values for use during sensor operation” by “receiving a request from the ECU 102” via the bidirectional communication terminal 550/650.
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention that the memory 534/634 of the sensor IC in Casu et al.’s invention would inherently include an input/output/access/read/write terminal/pin/node associated with at the memory 534/634 of the sensor IC so as to (Casu et al., Para. [0076]) receive signal to “store[retrieve/program/read/write] various values for use during sensor operation, some of which can be user-programmable.”
Casu et al. does not teach that the SENT signal generated at fixed time interval is generated:
“independent of the target speed.”
On the other hand, in the same field of endeavor (page 1: “a sensor system, a sensor, and a sensor signal output method”), ITO discloses (Fig. 3) a sensor output signal is generated:
“independent of the target speed (page 6: “The first sensor 42 may be configured to output a sensor signal at regular intervals” regardless of (page 1, 3) “a rotation speed…related to a control target”).”
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention that the SENT signal in Casu et al.’s invention can be generated regardless of (page 1, 3) “a rotation speed…related to a control target” as taught by ITO, where doing so (ITO, page 2) “can reduce sensor output data latency…reduce or eliminate ambiguity in sensor output data age.”
Regarding Claim 2 and 18, Casu et al. in view of ITO discloses all as applied to claim 1 and 17 above, where Casu et al. further teaches;
wherein the one or more parameters of the target include angle of rotation of the target (Para. [0027]: “The sensed parameter can be motion of the target, such as rotation and/or position of the target, such as an angular position [angle of rotation]”).
Regarding Claim 3 and 19, Casu et al. in view of ITO discloses all as applied to claim 2 and 18 above, where Casu et al. further teaches;
wherein the angle of rotation of the target conveyed at a second time is a difference in angle of rotation of target between a first time to the second time (Fig. 3, Para. [0030]: “The absolute data is an angle measurement (e.g., 275°)”. As depicted in Fig. 3, the angle of rotation of the target each absolute data at a second time, t4, is a difference in angle of rotation of target between a first time, t0 to the second time, t4, i.e. difference in angle = angle at t4 – angle at t0) the first and second times separated by the fixed time interval (Fig. 3: the interval between t4 and t0 is equal to the duration of SENT message 310a, “
t
S
E
N
T
”).
Regarding Claim 4 and 20, Casu et al. in view of ITO discloses all as applied to claim 2 and 18 above, where Casu et al. further teaches;
wherein each message also conveys information associated with the sensor (Fig. 3, 4, Para. [0052]: “The SENT message 400 can include… a Status and Serial Communication portion 404… Status and Serial Communication portion 404 is used to inform the ECU 102 of the sensor status or features (such as part numbers or error code information) and has a duration of between 12 and 27 ticks to provide 4 bits”).
Regarding Claim 5 and 21, Casu et al. in view of ITO discloses all as applied to claim 4 and 20 above, where Casu et al. further teaches;
wherein the information associated with the sensor includes a temperature associated with the sensor (Fig. 3, 4, Para. [0026], [0099]: “ICs 104a-104n may be the same type of sensor (e.g., each a magnetic field sensor) or may be different types of sensors (e.g., one is a temperature sensor and the others are magnetic field sensors)”; “Temperature may also affect signal amplitudes and offsets. Thus, processor 630 can be coupled to receive temperature information from a temperature sensor (not shown) and can operate to automatically track and compensate signal amplitudes and offsets.”).
Regarding Claim 6 and 22, Casu et al. in view of ITO discloses all as applied to claim 4 and 20 above, where Casu et al. further teaches;
wherein the information associated with the sensor includes diagnostics associated with the sensor (Fig. 4C, Para. [0065]: “The additional absolute information 470…can communicate various data… diagnostic information”).
Regarding Claim 7 and 23, Casu et al. in view of ITO discloses all as applied to claim 1 and 17 above, where Casu et al. further teaches;
wherein each message conveys the information about the one or more parameters of the target using a Single-Edge Nibble Transmission (SENT) protocol (Fig. 3, 4A-4D, Para. [0032]: “The format of the absolute data can be various unidirectional and/or bidirectional formats, including but not limited to…Single-Edge Nibble Transmission (SENT)”).
Regarding Claim 13, Casu et al. in view of ITO discloses all as applied to claim 1 above, where Casu et al. further teaches;
wherein the terminal configured to provide the messages and to receive the signal for adjusting the fixed time interval However, Casu et al. teaches (Fig. 5, 6, Para. [0032], [0076]) “a bidirectional format (e.g., a triggered SENT or Manchester format) may be used by the IC 104a to transmit data to the ECU 102 on the message line 106 after receiving a request from the ECU 102.” “Memory 534 can be configured to store various values for use during sensor operation, some of which can be user-programmable.” In other words, the memory 534/634 is configured to be accessible (reading and writing) for programming/storing/retrieving the different/desired fixed time interval, “
t
S
E
N
T
”/ “frame rate” values by providing a signal to choose/adjust/select/change a value among the “various values for use during sensor operation” by “receiving a request from the ECU 102” via the terminal 550/650 for bidirectional communication. Therefore, the terminal 550/650 functions as an input/output/access/read/write terminal/pin/node for providing the SENT messages and to receive the signal for adjusting the fixed time interval from the ECU 102.
Regarding Claim 14, Casu et al. in view of ITO discloses all as applied to claim 1 above, where Casu et al. further teaches;
wherein the one or more magnetic field sensing elements comprise one or more Hall elements (Para. [0028]: “Sensor 104a further includes a processor coupled to the sensing element and configured to generate a sensed signal indicative of the parameter associated with the target. In the case of a magnetic field sensor for example, the sensed signal can be the output signal of a magnetic field transducer such as a Hall effect or magnetoresistance element”).
Regarding Claim 15, Casu et al. in view of ITO discloses all as applied to claim 1 above, where Casu et al. further teaches;
wherein the one or more [[of]] magnetic field sensing elements comprise one or more magnetoresistance (MR) elements (Para. [0028]: “Sensor 104a further includes a processor coupled to the sensing element and configured to generate a sensed signal indicative of the parameter associated with the target. In the case of a magnetic field sensor for example, the sensed signal can be the output signal of a magnetic field transducer such as a Hall effect or magnetoresistance element”).
Regarding Claim 16, Casu et al. in view of ITO discloses all as applied to claim 1 above, where Casu et al. further teaches;
wherein the detection circuitry and the output circuit are provided as digital circuitry (Fig. 5, 6, Para. [0074]: Digital Processor 530/630 or detection circuitry and the output module/circuit 540/640 are provided as digital circuitry), wherein the sensor comprises an analog-to-digital converter (ADC) to convert the magnetic field signals to digital magnetic field signals (Fig. 5, Para. [0074]: a sensor system 500 includes “an analog-to-digital converter (ADC)” that converts a magnetic field sensed signal to digital magnetic field signals), wherein the detection circuitry is configured to detect the one or more parameters of the target using the digital magnetic field signals (Fig. 5, Para. [0077]: “A digital processor 530 [detection circuitry]” detects one or more parameters, e.g. speed, angle, direction etc., based on the received digital magnetic field signals from the ADC).
Regarding Claim 27 and 29, Casu et al. discloses;
A sensor and a method for detecting speed of a target (Fig. 1, 5, Para. [0026], [0073]-[0075]: “one or more integrated circuits (ICs) 104a-104n”; “a sensor IC 510…each of sensing elements 520a, 520b can sense a position and/or movement of target 514”), comprising:
one or more magnetic field sensing elements (Fig. 1, 5, Para. [0027]-[0028]: “Sensor 104a includes one or more sensing elements…”) operable to generate one or more magnetic field signals indicative of a magnetic field associated with the target having a speed (Fig. 1, Para. [0027]: “Sensor 104a includes one or more sensing elements configured to sense a parameter associated with a target (as shown in FIG. 5)…The sensed parameter can be motion of the target, such as rotation and/or position of the target, such as an angular position, to name a few examples.” “Sensor 104a further includes a processor coupled to the sensing element and configured to generate a sensed signal indicative of the parameter associated with the target. In the case of a magnetic field sensor for example, the sensed signal can be the output signal of a magnetic field transducer such as a Hall effect or magnetoresistance element”);
detection circuitry configured to detect one or more parameters of the target using the magnetic field signals or representations thereof (Para. [0028]: “Sensor 104a further includes a processor coupled to the sensing element and configured to generate a sensed signal indicative of the parameter associated with the target. In the case of a magnetic field sensor for example, the sensed signal can be the output signal of a magnetic field transducer such as a Hall effect or magnetoresistance element”); and
output circuit (Fig. 5, “Output module 540”) configured to generate messages (Fig. 3, Para. [0029], [0046]: “An output module [output circuit] of the sensor 104a is coupled to receive the sensed signal and configured to transmit absolute data based on the sensed signal. Thus, the absolute data is indicative of the sensed parameter.” “Absolute data 310 takes the form of a SENT signal including individual SENT messages 310a-310c [messages]”) at a fixed time interval (Fig. 4, Para. [0031], [0047], [0052]: “absolute data in the form of SENT messages can be sent on the message line 106 every 128 microseconds [fixed time interval]” “The SENT messages 310a-310c can have a user specified tick time and message format”; “The number of data nibbles will be fixed for each application but can vary between applications”. Hence, a SENT messages is generated at fixed time interval, “
t
S
E
N
T
”), each message conveying information about the one or more parameters of the target (Para. [0052]: “The SENT message 400 can include a sequence of pulses transmitted by the sensor IC 104a and in the example angle sensor, the target angle can be converted into the pulses with data encoded as falling to falling edge periods.” Hence each SENT message 310a to 310c conveys at least a target angle information), wherein the one or more parameters of the target include angle of rotation of the target (Para. [0027]: “The sensed parameter can be motion of the target, such as rotation and/or position of the target, such as an angular position [angle of rotation]”), wherein the angle of rotation of the target conveyed at a second time is a difference in angle of rotation of target between a first time to the second time (Fig. 3, Para. [0030]: “The absolute data is an angle measurement (e.g., 275°)”. As depicted in Fig. 3, the angle of rotation of the target each absolute data at a second time, t4, is a difference in angle of rotation of target between a first time, t0 to the second time, t4, i.e. difference in angle = angle at t4 – angle at t0) the first and second times separated by the fixed time interval (Fig. 3: the interval between t4 and t0 is equal to the duration of SENT message 310a, “
t
S
E
N
T
”).
Casu et al. does not teach that the SENT signal generated at fixed time interval is generated:
“independent of the target speed.”
On the other hand, in the same field of endeavor (page 1: “a sensor system, a sensor, and a sensor signal output method”), ITO discloses (Fig. 3) a sensor output signal is generated:
“independent of the target speed (page 6: “The first sensor 42 may be configured to output a sensor signal at regular intervals” regardless of (page 1, 3) “a rotation speed…related to a control target”).”
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention that the SENT signal in Casu et al.’s invention can be generated regardless of (page 1, 3) “a rotation speed…related to a control target” as taught by ITO, where doing so (ITO, page 2) “can reduce sensor output data latency…reduce or eliminate ambiguity in sensor output data age.”
Regarding Claim 28 and 30, Casu et al. discloses;
A sensor and associated method for detecting speed of a target (Fig. 1, 5, Para. [0026], [0073]-[0075]: “one or more integrated circuits (ICs) 104a-104n”; “a sensor IC 510…each of sensing elements 520a, 520b can sense a position and/or movement of target 514”), comprising:
one or more magnetic field sensing elements (Fig. 1, 5, Para. [0027]-[0028]: “Sensor 104a includes one or more sensing elements…”) operable to generate one or more magnetic field signals indicative of a magnetic field associated with the target having a speed (Fig. 1, Para. [0027]: “Sensor 104a includes one or more sensing elements configured to sense a parameter associated with a target (as shown in FIG. 5)…The sensed parameter can be motion of the target, such as rotation and/or position of the target, such as an angular position, to name a few examples.” “Sensor 104a further includes a processor coupled to the sensing element and configured to generate a sensed signal indicative of the parameter associated with the target. In the case of a magnetic field sensor for example, the sensed signal can be the output signal of a magnetic field transducer such as a Hall effect or magnetoresistance element”);
detection circuitry (Fig. 5, 6, Para. [0077], [0098]: digital processor 530/630) configured to detect one or more parameters of the target using the magnetic field signals or representations thereof (Para. [0028]: “Sensor 104a further includes a processor [digital processor 530/630] coupled to the sensing element and configured to generate a sensed signal indicative of the parameter associated with the target. In the case of a magnetic field sensor for example, the sensed signal can be the output signal of a magnetic field transducer such as a Hall effect or magnetoresistance element”); and
output circuit (Fig. 5, “Output module 540”) configured to generate messages (Fig. 3, Para. [0029], [0046]: “An output module [output circuit] of the sensor 104a is coupled to receive the sensed signal and configured to transmit absolute data based on the sensed signal. Thus, the absolute data is indicative of the sensed parameter.” “Absolute data 310 takes the form of a SENT signal including individual SENT messages 310a-310c [messages]”) at a fixed time interval (Fig. 4, Para. [0031], [0047], [0052]: “absolute data in the form of SENT messages can be sent on the message line 106 every 128 microseconds [fixed time interval]” “The SENT messages 310a-310c can have a user specified tick time and message format”; “The number of data nibbles will be fixed for each application but can vary between applications”. Hence, a SENT messages is generated at fixed time interval, “
t
S
E
N
T
”), each message conveying information about the one or more parameters of the target (Para. [0052]: “The SENT message 400 can include a sequence of pulses transmitted by the sensor IC 104a and in the example angle sensor, the target angle can be converted into the pulses with data encoded as falling to falling edge periods.” Hence each SENT message 310a to 310c conveys at least a target angle information), wherein each message also conveys information associated with the sensor (Fig. 3, 4, Para. [0052]: “The SENT message 400 can include… a Status and Serial Communication portion 404… Status and Serial Communication portion 404 is used to inform the ECU 102 of the sensor status or features (such as part numbers or error code information) and has a duration of between 12 and 27 ticks to provide 4 bits”), wherein the information associated with the sensor includes a temperature associated with the sensor (Fig. 3, 4, Para. [0026], [0099]: “ICs 104a-104n may be the same type of sensor (e.g., each a magnetic field sensor) or may be different types of sensors (e.g., one is a temperature sensor and the others are magnetic field sensors)”; “Temperature may also affect signal amplitudes and offsets. Thus, processor 630 can be coupled to receive temperature information from a temperature sensor (not shown) and can operate to automatically track and compensate signal amplitudes and offsets”).
Casu et al. does not teach that the SENT signal generated at fixed time interval is generated:
“independent of the target speed.”
On the other hand, in the same field of endeavor (page 1: “a sensor system, a sensor, and a sensor signal output method”), ITO discloses (Fig. 3) a sensor output signal is generated:
“independent of the target speed (page 6: “The first sensor 42 may be configured to output a sensor signal at regular intervals” regardless of (page 1, 3) “a rotation speed…related to a control target”).”
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention that the SENT signal in Casu et al.’s invention can be generated regardless of (page 1, 3) “a rotation speed…related to a control target” as taught by ITO, where doing so (ITO, page 2) “can reduce sensor output data latency…reduce or eliminate ambiguity in sensor output data age.”
Claims 8-10 and 24-26 are rejected under 35 U.S.C. 103 as being unpatentable over Casu et al. (US 20220239462 A1 previously cited) in view of ITO (JP 2015228171 A machine English translated previously provided) further in view of Hainz et al. (US 20180174441 A1 previously cited).
Regarding Claim 8 and 24, Casu et al. in view of ITO discloses all as applied to claim 1 and 17 above, however they do not teach wherein the each SENT message conveys the information about the one or more parameters of the target using:
“words comprising a speed pulse followed by a sequence of data pulses.”
On the other hand, in the same field of endeavor (Abstract: “A signal encoder for encoding a wheel speed sensor signal”), Hainz et al. discloses (Fig. 1A, 1B) outputting “an encoded WSS signal 104” conveying speed parameter of a target/wheel using:
words comprising a speed pulse followed by a sequence of data pulses (Fig. 1B, Para. [0026]-[0028]: “an encoded WSS signal 104” includes words comprising “speed pulse 105-1, 105-2, 105-3” each followed by “sequences of data pulses 110-1, 110-2, 110-3 carrying the additional information (e.g., rotational direction, error, and/or air gap reserve information)”).
Therefore, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention that the SENT messages conveying information about the one or more parameters of the target in Casu et al. in view of ITO’s invention can be done using words comprising speed pulse followed by sequence of data pulses as taught by Hainz et al., where doing so (Hainz et al., Para. [0003]) “can provide a reliable communication of the sensor data at higher data rates.”
Regarding Claim 9 and 25, Casu et al. in view of ITO further in view of Hainz et al. discloses all as applied to claim 8 and 24 above, where Hainz et al. further teaches;
wherein the data pulses are Manchester encoded (Fig. 1C, 1D, Para. [0029]: “The data bits (e.g., the data pulses) are coded binary by a Manchester code”).
Regarding Claim 10 and 26, Casu et al. in view of ITO further in view of Hainz et al. discloses all as applied to claim 8 and 24 above, where Hainz et al. further teaches;
wherein the speed pulses have a first current (Fig. 1B-1D, Para. [0029]: “A speed pulse 105-1 of the of an encoded WSS signal 104-C can be a 28 mA pulse”) and the data pulses have a second current different from the first current (Fig. 1B-1D, Para. [0029]: “A speed pulse 105-1 of the of an encoded WSS signal 104-C can be a 28 mA pulse…The data bits (e.g., the data pulses) are coded binary by a Manchester code with the current levels of 7 mA and 14 mA”).
Conclusion
THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to AMNEET SINGH whose telephone number is (571)272-2414. The examiner can normally be reached 9:30am to 5:30pm.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Sam K. Ahn can be reached at 5712723044. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/AMNEET SINGH/Examiner, Art Unit 2633 /SAM K AHN/Supervisory Patent Examiner, Art Unit 2633
Prosecution Insights