In-vehicle network system

US10116570B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10116570-B2
Application numberUS-201615159894-A
CountryUS
Kind codeB2
Filing dateMay 20, 2016
Priority dateMay 29, 2015
Publication dateOct 30, 2018
Grant dateOct 30, 2018

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

An in-vehicle network system includes a receiver node and a sender node, among which the receiver node adds payload length information to a flow control frame, and sends the flow control frame to a sender node using a control protocol, and the sender node determines a payload length of a consecutive frame based on the payload length information for the sending of the consecutive frame after the reception of the flow control frame, thereby variably changing the payload length and reducing communication load of the network bus, without complicating a configuration and/or a control of the network system.

First claim

Opening claim text (preview).

What is claimed is: 1. An in-vehicle network system, the system comprising: in-vehicle devices in a vehicle; and a network bus communicably connecting plural nodes controlling the in-vehicle devices, the plural nodes communicating with each other using a control protocol, and comprising a sender node connected to the network bus and sending a first frame, and a receiver node connected to the network bus and sending a flow control frame after receiving the first frame, wherein the receiver node sends the flow control frame to the sender node after adding payload length information to the flow control frame according to the control protocol, and the sender node determines a payload length of a consecutive frame to be transmitted after receiving the flow control frame, based on the payload length information. 2. The in-vehicle network system of claim 1 , wherein the flow control frame further comprises a header, the receiver node is capable of changing a data length code in the header of the flow control frame, and the sender node determines the payload length of the consecutive frame based on the data length code. 3. The in-vehicle network system of claim 1 , wherein the receiver node adds the payload length information to a payload of the flow control frame. 4. The in-vehicle network system of claim 2 , wherein the receiver node makes the payload length information to determine a shorter payload length of the consecutive frame, as communication load of the network bus increases. 5. The in-vehicle network system of claim 2 , wherein the receiver node makes the payload length information to determine a shorter payload length of the consecutive frame, when a fault of one of the in-vehicle devices occurs. 6. The in-vehicle network system of claim 2 , wherein the receiver node makes the payload length information to determine a shorter payload length of the consecutive frame, as a number of active state nodes connected to the network bus increases. 7. An in-vehicle network system for controlling in-vehicle devices in a vehicle, the system comprising: a network bus communicably connecting plural nodes communicating with each other using a control protocol, the plural nodes comprising; a sender node connected to the network bus and sending a first frame; and a receiver node connected to the network bus and sending a flow control frame after receiving the first frame, wherein the sender node makes a payload length of a consecutive frame that is sent after the reception of the flow control frame shorter, as a response time of a node of the plural nodes connected to the network bus increases. 8. An in-vehicle network system, comprising: a network bus; a sender node connected to the network bus and sending a first frame; and a receiver node connected to the network bus and sending a flow control frame after receiving the first frame, wherein the receiver node sends the flow control frame to the sender node after adding payload length information to the flow control frame according to a control protocol, and the sender node determines a payload length of a consecutive frame to be transmitted after receiving the flow control frame, based on the payload length information.

Assignees

Inventors

Classifications

  • H04L47/13Primary

    in a LAN segment, e.g. ring or bus · CPC title

  • Network utilisation, e.g. volume of load or congestion level · CPC title

  • specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10116570B2 cover?
An in-vehicle network system includes a receiver node and a sender node, among which the receiver node adds payload length information to a flow control frame, and sends the flow control frame to a sender node using a control protocol, and the sender node determines a payload length of a consecutive frame based on the payload length information for the sending of the consecutive frame after the…
Who is the assignee on this patent?
Denso Corp
What technology area does this patent fall under?
Primary CPC classification H04L47/13. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Oct 30 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).