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 .
DETAILED ACTION
This office action is in response to the claim listing filed on 04/02/2025. Claims 1-16 are currently pending.
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 04/02/2025. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
Claim Rejections - 35 USC § 103
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.
Claims 1-16 are rejected 35 U.S.C. 103 as being unpatentable over Kessler et al. (USPGPUB No. 2017/0220502 A1, hereinafter referred to as Kessler) in view of Diab et al. (USPGPUB No. 2012/0173900 A1, hereinafter referred to as Diab).
Referring to claim 1, Kessler discloses a vehicle-mounted device {vehicle-mounted devices “slave nodes 104” ([0122], 1st sentence)} to be used in a vehicle-mounted network {vehicle-mounted “system 100” (see Fig. 1, [0121], 1st sentence) including network } that includes a vehicle-mounted relay device {“slave nodes 104 may operate as active/intelligent [relay device] repeater nodes” ([0122], 1st sentence)} that relays frames that are transmitted and received {“selectively forward, drop, and add information.”, see Figs. 1 and 11 [0122], 1st sentence} between vehicle-mounted functional units {“head unit (e.g., [functional units] a master node 102 or a host 110 included in a head unit)”, see Figs. 23 and 24, [0201], 1st sentence}, the communication-circuit group includes a plurality of target communication circuits that are communication circuits {“peripheral device 108, one or more radio receivers such as FM [communication circuits] (frequency modulation) receivers, AM (amplitude modulation) receivers, satellite radio receivers, television/media receivers, or other over-the-air signal receivers”, see Figs. 23 and 24 [0200], 1st sentence}, the communication-port group includes a plurality of target communication ports {“I2C-compatible peripheral device 108 coupled to the slave node 104 at one or more I2C ports of the slave node 104”, see Fig. 1 [0085], last sentence} that are communication ports respectively corresponding to the plurality of target predetermined condition is satisfied {“to ensure that the preamble 182 can be uniquely [satisfied] identified by the slave nodes 104 or to reduce the likelihood that the preamble 182 shows up elsewhere in the synchronization control frame 180”, see Fig. 1 [0084], 1st sentence}, the vehicle-mounted device comprises a notification unit configured to {“control circuitry 154 may be notified [by a notification unit] of the failure and will not perform any control commands in the control data 184 of the synchronization control frame 180”, see Fig. [0104], 2nd sentence}, in a state where one or more existing functional units {“head unit (e.g., [functional units] a master node 102 or a host 110 included in a head unit)” (see Figs. 23 and 24, [0201], 1st sentence) performing/recognizing “slave node 104 in a discovery transaction matches an existing [one or more functional unit] slave node 104” ([0092], last sentence)} that are among the vehicle-mounted functional units are connected to some of the plurality of target communication ports {“one or more designated slave nodes 104”, see Fig. 1 [0085], 2nd sentence}, when a new functional unit that {“formats for the synchronization control frame 180 in normal mode, I2C mode, and discovery mode [to find new functional units]”, see Fig. 5 [0074], 3rd sentence} is one of the vehicle-mounted functional units is communication circuits {“remotely access a [communication circuit] peripheral device 108 that acts as an I2C slave with respect to an associated slave node 104”, see Figs. 1 and 5, [0077], last sentence}, and connected to a target communication port to which none of the one or more existing functional units is connected {“NAM field may provide for four node addressing modes, including “none” [of the one or more existing functional units]”, see Fig. 1 [0076], last sentence};
Kessler does not appear to explicitly disclose that are communication circuits in which types of sleep modes need to be unified;
perform notification processing to provide a notification of a communication port that is to be a connection destination of the new functional unit based on a combination of types of sleep modes that are to be applied to the plurality of target communication circuits.
However, Diab discloses that are communication circuits {“If [communication circuits] power savings is to be enabled…”, see Figs. 124 and 125 [0667], 1st sentence} in which types of sleep modes need to be unified {by determining whether to employ an individual power saving option or a [unified] power island power saving option 1968”, see Figs. 124 and 125 [0667], 1st sentence};
perform notification processing to provide a notification of a communication port {“by performing the network configuration adjustment 632 and [provide a notification] sending an acknowledgement of its completion 634”, see Figs. 32 and 33 [0242], last sentence} that is to be a connection destination {“its completion 634” of a connection destination when “determining a network configuration adjustment 630”, see Figs. 32 and 33, [0242], 1st sentence} of the new functional unit based on a combination of types of sleep modes {“change network configuration, change resource allocation, adjust traffic routing, adjust load-balancing, activate redundant link or path upon any failures, etc” (see Figs. 32 and 33 [0242], last two sentences)} that are to be applied {among such network configuration via “network interface 1944 may connect to the network fabric (vehicular communication network) via a wireless connection and/or a wired connection 1950” (see Fig. 124, [0658], 2nd sentence)}, to the plurality of target communication circuits {“ determining whether the network task includes a [targeting] memory access request 612.”, see Figs. 32 and 33 [0240], 1st sentence; “device power savings options 1958 for a particular device [requested/targeted]”, see Fig. 124, [0660], 1st sentence}.
Kessler and Diab are analogous because they are from the same field of endeavor, vehicle-based network message(s).
Before the effective filing date of the claimed invention, it would have been obvious to one of ordinary skill in the art, having the teachings of Kessler and Diab before him or her, to modify Kessler’s “node transceiver 126” incorporating Diab’s “performing the network configuration adjustment 632” (see Figs. 32 and 33 [0242], last sentence).
The suggestion/motivation for doing so would have been to enable electronic components using different bus protocols to communicate with each other, by implementing one or more bus gateways may be included in the vehicle network (Diab [0010] 1st sentence).
Therefore, it would have been obvious to combine Diab with Kessler to obtain the invention as specified in the instant claim(s).
As per claim 2, the rejection of claim 1 is incorporated and Kessler discloses wherein the notification unit performs notification of a communication port {“control circuitry 154 may be notified [by a notification unit] of the failure and will not perform any control commands in the control data 184 of the synchronization control frame 180”, see Fig. 7, [0104], 2nd sentence} other than the target communication ports {“NACK is received (meaning that at least one slave node 104 did not “agree” to clear the [other target communication port] bus GPIO port”, see Fig. 35 [0254]} as the communication port to be the connection destination {“slave node 104 may also provide routing data in response to actuation of the conferencing user interface element to indicate the source of the microphone data and/or the desired destination(a)”, see Fig. 1 [0163], last sentence}.
As per claim 3, the rejection of claim 2 is incorporated and Diab discloses wherein, if a sleep mode that is to be applied to the target communication circuits {“one or more of: placing the [target communication circuit] device in a sleep mode”, see Figs. 124 and 125 [0060], 1st sentence} corresponding to the target communication ports to which the one or more existing functional units are connected is different {different “power savings options 1958”: “reducing the clock rate of the device, disabling power to the device, limiting the current to the device and using a lower power physical layer communication link for the device” (see Figs. 124 and 125 [0660], 1st sentence)} from a sleep mode that is to be applied {“savings options 1962 for a particular power island may include [applied], for example, one or more of: placing each of the devices in the power island in a sleep mode”, see Figs. 124 and 125, [0660]} to the target communication circuit corresponding to the target communication port to which the new functional unit is connected {“the device may be a newly [ECU/functional unit] added device or an existing device”, see Figs. 68A, [0407], 2nd sentence}, the notification unit performs notification of a communication port {“performing the network configuration adjustment 632 and sending an acknowledgement of its completion 634”, [0242], last sentence} other than the target communication ports {“forwarding database, a routing table, a filtering table, a mission-critical database [whether the ports targeted or not]”, see Fig. 32 [0240], last sentences} as the communication port to be the connection destination {“critical processing module destination, or destinations 582”, see Fig. 30, [0235] 1st sentence.}.
As per claim 4, the rejection of claim 2 is incorporated and Diab discloses wherein, in a state where a first sleep mode {by determining whether to employ an individual power saving option or a [plurality] power island power saving option 1968”, see Figs. 124 and 125 [0667], 1st sentence} is applied to the target communication circuits {“determining whether the network task includes a [targeting] memory access request 612.”, see Figs. 32 and 33 [0240], 1st sentence; “device power savings options 1958 for a particular device [requested/targeted]”, see Fig. 124, [0660], 1st sentence} corresponding to the target communication ports to which the one or more existing functional units are connected {“monitoring an [one or more] existing device in accordance with a particular use mode to determine whether the existing device is a damaged device within a vehicular communication network”, see Fig. 71, [0420], 1st sentence}, when a second sleep mode {“With reference to the power saving options table” comprising a plurality of sleep modes, see Figs. 124 and 125 [0661], 2nd sentence} in which power consumption of a communication circuit {“using a lower power physical layer communication link [among communication circuits] for the device”, see Figs. 124 and 125 [0660], 1st sentence} is larger than that of the first sleep mode {“using a lower power physical layer communication link” having a larger power consumption versus a deep sleep mode “placing each of the devices in the power island in a sleep mode, reducing the supply voltage to each of the devices in the power island”, see Figs. 124 and 125 [0660]} is to be applied to the target communication circuit corresponding to the target communication port to which the new functional unit is connected {“sensors, output side of ECUs, etc., and a plurality of analog input devices (e.g., analog input device_1 . . . analog input device_n), such as actuators, input side of ECUs”, see Fig. 66a [0391], last sentence, [0427], see Fig. 72}, the notification unit performs notification of a communication port {“by performing the network configuration adjustment 632 and [provide a notification] sending an acknowledgement of its completion 634”, see Figs. 32 and 33 [0242], last sentence} other than the target communication ports as the communication port to be the connection destination {other communication ports “power sourcing port 1118a and powered device port 1112b1 and PSE/PD 1110g only receives power from PSE/PD 1110f via power sourcing port 1118f2 and powered device port 1112g2”, see Fig. 63B [0365], 1st sentence}.
As per claim 5, the rejection of claim 1 is incorporated and Diab discloses vehicle-mounted device including:
an acquisition unit configured to acquire functional unit information {“by collecting vehicle data,” by an appropriate acquisition unit, see Fig. 122 [0655], 2nd sentence} of the new functional unit when the new functional unit is connected to the target communication port {“data from one or more sensors of the vehicle, diagnostic data, performance data, occupant data” via an appropriate target communication port, see Fig. 122 [0655], 2nd sentence};
and a sleep control unit {“the device 000 001 [with appropriate sleep control unit] may be placed in a sleep mode when inactive”, see Fig. 124 [0663]} configured to select a type of sleep mode {“power saving option 1 [type])”, see Fig. 124 [0663]} that is to be applied to the target communication circuit {“data from one or more sensors of the vehicle, diagnostic data, performance data, occupant data” via an appropriate target communication port, see Fig. 122 [0655], 2nd sentence} corresponding to the target communication port to which the new functional unit is connected {“mission critical destinations 1188 (e.g., safety actuators), and mission critical [targeted functional units] processing modules 1190 (e.g., safety ECUs) ”, see Fig. 72 [0427]}, from a plurality of types of sleep modes {plurality of sleep modes “power adjusted by placing it in a sleep mode when inactive (i.e., power saving option 1), have its supply voltage reduced (i.e., power saving option 3), have its clock rate reduced (i.e., power saving option 4), and/or use a lower power physical layer communication link (i.e., power saving option 6)”, see Fig. 124 [0661], last sentence}, based on the functional unit information of the new functional unit acquired by the acquisition unit {“by collecting vehicle data,” by an appropriate acquisition unit, see Fig. 122 [0655], 2nd sentence}, wherein the notification unit performs the notification processing {“by performing the network configuration adjustment 632 and [provide a notification] sending an acknowledgement of its completion 634”, see Figs. 32 and 33 [0242], last sentence} based on the type of sleep mode selected by the sleep control unit {based on “change network configuration, change [sleep/power] resource allocation, adjust traffic routing, adjust load-balancing, activate redundant link or path upon any failures, etc” (see Figs. 32 and 33 [0242], last two sentences)} and the type of sleep mode that is to be applied to the target communication circuits corresponding to the target communication ports {“requests access to one or more processing resources 1900 to augment, or off-load, video processing within the vehicle 1884” by offloading to respective target communication circuits from “vehicle 1884” to “resources 1900”, see Fig. 121 [0652], last two sentences} to which the one or more existing functional units are connected {“selecting a [existing functional unit] device coupled to the network fabric 1964”, see Fig. 125 [0665], last two sentences}
As per claim 6, the rejection of claim 1 is incorporated and Diab discloses wherein the notification unit performs the notification processing based on the number of communication circuits to which a predetermined type of sleep mode {“[predetermined type of] devices and/or modules within a power island may be related by device type, device function and/or device location within the vehicular communication network”, see Fig. 124 [0659], last two sentences} is to be applied when the new functional unit is connected {“change network configuration, change resource allocation, adjust traffic routing, adjust load-balancing, activate redundant link or path upon any failures, etc” (see Figs. 32 and 33 [0242], last two sentences)} to the communication port {“by performing the network configuration adjustment 632 and [provide a notification] sending an acknowledgement of its completion 634”, see Figs. 32 and 33 [0242], last sentence} other than the target communication ports and the number of communication circuits to which the {other communication ports “power sourcing port 1118a and powered device port 1112b1 and PSE/PD 1110g only receives power from PSE/PD 1110f via power sourcing port 1118f2 and powered device port 1112g2”, see Fig. 63B [0365], 1st sentence} to which the predetermined type of sleep mode {“[predetermined type of] devices and/or modules within a power island may be related by device type, device function and/or device location within the vehicular communication network”, see Fig. 124 [0659], last two sentences} is to be applied when the new functional unit is connected to the target communication port {“change network configuration, change resource allocation, adjust traffic routing, adjust load-balancing, activate redundant link or path upon any failures, etc” (see Figs. 32 and 33 [0242], last two sentences)}.
Referring to claim 7 is a method claim reciting claim functional language corresponding to the device claim of claim 1, thereby rejected under the same rationale as claim 1 recited above.
Referring to claim 8 is a computer program product claim reciting claim functional language corresponding to the device claim of claim 1, thereby rejected under the same rationale as claim 1 recited above.
As per claims 9-16 are device claims reciting claim functional language corresponding to the device claim of claim 2-6, thereby rejected under the same rationale as claim 2-6 recited above.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. The following references are indicative the current state of the art regarding claim 1’s “vehicle mounted device”, “relay frames”, or “communication circuits”: US 10917253 B2, US 11336470 B2, US 12463845 B2, US 20210243049 A1, US 20230216704 A1, AND US 20250175358 A1.
Contact Information
Any inquiry concerning this communication or earlier communications from the examiner should be directed to CHRISTOPHER A. BARTELS whose telephone number is (571)270-3182. The examiner can normally be reached on Monday-Friday 9:00a-5:30pm EST.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Dr. Henry Tsai can be reached on 571-272-4176. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/C. B./
Examiner, Art Unit 2184
/HENRY TSAI/Supervisory Patent Examiner, Art Unit 2184
