IP Library › Granted Patent US 12,489,814
Granted Patent B2
US 12,489,814 · App. 18/596,981 · Granted Dec 2, 2025

Management device, vehicle communication system, vehicle, vehicle communication management method, and vehicle communication management program

Inventors: Yusuke Yamamoto (Osaka, JP); Koichi Takayama (Osaka, JP); Hideyuki Tanaka (Osaka, JP); Tatsuya Izumi (Osaka, JP); Junji Yano (Osaka, JP); Yasuhiro Yabuuchi (Yokkaichi, JP); Tadashi Matsumoto (Yokkaichi, JP); Takeshi Hagihara (Yokkaichi, JP)
Assignees: SUMITOMO ELECTRIC INDUSTRIES, LTD.; SUMITOMO WIRING SYSTEMS, LTD.; AUTONETWORKS TECHNOLOGIES, LTD.
H04L67/12H04L41/12H04L41/0813
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,489,814
App. No.
18/596,981
Filed
Mar 6, 2024
Granted
Dec 2, 2025
Kind
B2
Art Unit
2459
USPC
709/222
Abstract

A network of a new configuration is flexibly constructed while maintaining a stable operation in the network. A management device includes: a detection unit that detects addition of a function unit to a network including one or a plurality of on-vehicle function units; an acquisition unit that acquires function unit information of a new function unit that is the function unit the addition of which has been detected by the detection unit and function unit information of each on-vehicle function unit, each piece of function unit information including information regarding network configuration of a layer lower than an application layer; and a generation unit that, based on the pieces of function unit information acquired by the acquisition unit, generates configuration information of a new network that is the network further including the new function unit.

Claims (55)

1 . A vehicle communication system comprising:

a management device;

a storage device; and

one or a plurality of on-vehicle function units constructing a network, wherein

the management device detects addition of a function unit to the network, and acquires, from a new function unit that is the function unit the addition of which has been detected, function unit information including information regarding network configuration of a layer lower than an application layer,

the one or the plurality of on-vehicle function units each transmit, to the management device, its own function unit information including information regarding network configuration of a layer lower than an application layer,

the management device generates configuration information of a new network that is the network further including the new function unit, based on the function unit information acquired from the new function unit and on the function unit information received from the one or the plurality of on-vehicle function units, and

when feasibility of the new network is denied based on the function unit information and the configuration information, the management device newly generates configuration information based on a generation condition changed based on feasibility information indicating that the new network is infeasible, wherein

the function unit information includes information of a communication port that the on-vehicle function unit uses for communication, and a VLAN ID of a VLAN to which the on-vehicle function unit belongs,

the new function unit does not have a VLAN ID at the time the addition of the new function unit to the network is detected, and

the management device assigns, based on the communication port that the on-vehicle function unit uses for communication and the VLAN ID of the VLAN to which the on-vehicle function unit belongs, the VLAN ID corresponding to the communication port used by the new function unit in the new network to the new function unit that does not have a VLAN ID yet.

2 . The vehicle communication system according to claim 1 , wherein the configuration information includes both (i) information of a communication port that the function unit uses for communication, and (ii) a VLAN ID of a VLAN to which the function unit belongs.

3 . The vehicle communication system according to claim 1 , wherein the management device acquires the function unit information from at least one of the storage device and the on-vehicle function unit.

4 . A management device comprising a hardware processor configured to cause the management device to perform operations, and a storage device, the operations comprising:

detecting addition of a function unit to a network including one or a plurality of on-vehicle function units;

acquiring function unit information of a new function unit that is the function unit the addition of which has been detected and function unit information of each on-vehicle function unit, each piece of function unit information including information regarding network configuration of a layer lower than an application layer;

generating, based on the pieces of function unit information acquired, configuration information of a new network that is the network further including the new function unit; and

when feasibility of the new network is denied based on the function unit information and the configuration information, newly generating configuration information based on a generation condition changed based on feasibility information indicating that the new network is infeasible, wherein

the function unit information includes information of a communication port that the on-vehicle function unit uses for communication, and a VLAN ID of a VLAN to which the on-vehicle function unit belongs,

the new function unit does not have a VLAN ID at the time the addition of the new function unit to the network is detected, and

the generating includes assigning, based on the communication port that the on-vehicle function unit uses for communication and the VLAN ID of the VLAN to which the on-vehicle function unit belongs, the VLAN ID corresponding to the communication port used by the new function unit in the new network to the new function unit that does not have a VLAN ID yet.

5 . The management device according to claim 4 , wherein the operations further comprise notifying, based on the generated configuration information, at least one of the new function unit and the one or the plurality of on-vehicle function units which constitute the new network, of a setting content for performing communication in the new network.

6 . The management device according to claim 4 , wherein

the function unit information is information that allows recognition of at least one of: specifications of a plurality of hardware devices in the new network and a topology of the new network; restriction on allocation of the new function unit and the on-vehicle function units to the hardware devices in the new network; and restriction on a communication method in the new network.

7 . The management device according to claim 4 , wherein

the generating includes acquiring feasibility information indicating feasibility of the new network and corresponding to the generated configuration information.

8 . The management device according to claim 7 , wherein

the generating includes changing generation condition, based on the acquired feasibility information, and newly generating the configuration information according to the changed generation condition.

9 . The management device according to claim 4 , wherein the operations further comprise storing the generated configuration information.

10 . The management device according to claim 7 , wherein

the generating includes acquiring the feasibility information from another device.

11 . The management device according to claim 4 , wherein

the generating includes generating the configuration information, on the basis of the pieces of function unit information acquired, while taking logical configuration and physical configuration of the new network into consideration.

12 . The management device according to claim 4 , wherein the configuration information includes both (i) information of a communication port that the function unit uses for communication, and (ii) a VLAN ID of a VLAN to which the function unit belongs.

13 . The management device according to claim 4 , wherein the acquiring includes acquiring the function unit information from at least one of the storage device and the on-vehicle function unit.

14 . A vehicle communication management method performed by a management device, comprising:

detecting addition of a function unit to a network including one or a plurality of on-vehicle function units;

acquiring function unit information of a new function unit that is the function unit the addition of which has been detected and function unit information of each on-vehicle function unit, each piece of function unit information including information regarding network configuration of a layer lower than an application layer;

generating, based on the pieces of function unit information acquired, configuration information of a new network that is the network further including the new function unit; and

when feasibility of the new network is denied based on the function unit information and the configuration information, newly generating configuration information based on a generation condition changed based on feasibility information indicating that the new network is infeasible, wherein

the function unit information includes information of a communication port that the on-vehicle function unit uses for communication, and a VLAN ID of a VLAN to which the on-vehicle function unit belongs,

the new function unit does not have a VLAN ID at the time the addition of the new function unit to the network is detected, and

the generating includes assigning, based on the communication port that the on-vehicle function unit uses for communication and the VLAN ID of the VLAN to which the on-vehicle function unit belongs, the VLAN ID corresponding to the communication port used by the new function unit in the new network to the new function unit that does not have a VLAN ID yet.

15 . The vehicle communication management method according to claim 14 , wherein the configuration information includes both (i) information of a communication port that the function unit uses for communication, and (ii) a VLAN ID of a VLAN to which the function unit belongs.

16 . The vehicle communication management method according to claim 14 , wherein the acquiring includes acquiring the function unit information from at least one of a storage device and the on-vehicle function unit.

17 . A non-transitory computer-readable storage medium having, stored therein, a vehicle communication management program used in a management device, the program causing a computer to perform operations comprising:

detecting addition of a function unit to a network including one or a plurality of on-vehicle function units;

acquiring function unit information of a new function unit that is the function unit the addition of which has been detected and function unit information of each on-vehicle function unit, each piece of function unit information including information regarding network configuration of a layer lower than an application layer;

generating, based on the pieces of function unit information acquired, configuration information of a new network that is the network further including the new function unit; and

when feasibility of the new network is denied based on the function unit information and the configuration information, newly generating configuration information based on a generation condition changed based on feasibility information indicating that the new network is infeasible, wherein

the function unit information includes information of a communication port that the on-vehicle function unit uses for communication, and a VLAN ID of a VLAN to which the on-vehicle function unit belongs,

the new function unit does not have a VLAN ID at the time the addition of the new function unit to the network is detected, and

the generating includes assigning, based on the communication port that the on-vehicle function unit uses for communication and the VLAN ID of the VLAN to which the on-vehicle function unit belongs, the VLAN ID corresponding to the communication port used by the new function unit in the new network to the new function unit that does not have a VLAN ID yet.

18 . The non-transitory computer-readable storage medium according to claim 17 , wherein the configuration information includes both (i) information of a communication port that the function unit uses for communication, and (ii) a VLAN ID of a VLAN to which the function unit belongs.

19 . The non-transitory computer-readable storage medium according to claim 17 , wherein the computer includes a storage device, and the acquiring includes acquiring the function unit information from at least one of the storage device and the on-vehicle function unit.

Priority Claims (1)
JP 2019-039548 · Mar 5, 2019 · national
Continuity (2)
Continuation 17437027
Related Publication 20240223660A1 · Jul 4, 2024
References Cited (39)
US 8520512B2 · Gilde · 2013 [cited by examiner]
US 8751649B2 · Villait et al. · 2014 [cited by applicant]
US 8997091B1 · Watson · 2015 [cited by examiner]
US 9432260B2 · Wang et al. · 2016 [cited by applicant]
US 11397801B2 · Ben-Noon · 2022 [cited by examiner]
US 11956314B2 · Yamamoto · 2024 [cited by examiner]
US 20050004726A1 · Paquet · 2005 [cited by applicant]
US 20050216903A1 · Schaefer · 2005 [cited by examiner]
US 20100302974A1 · Niiyama · 2010 [cited by examiner]
US 20110044291A1 · Omar · 2011 [cited by examiner]
US 20130090820A1 · Frashure et al. · 2013 [cited by applicant]
US 20130091534A1 · Gilde et al. · 2013 [cited by applicant]
US 20130230124A1 · Chini et al. · 2013 [cited by applicant]
US 20130294453A1 · Han et al. · 2013 [cited by applicant]
US 20140280809A1 · Li · 2014 [cited by examiner]
US 20140337829A1 · Ito · 2014 [cited by applicant]
US 20150280992A1 · Wang · 2015 [cited by examiner]
US 20160065298A1 · Nakagawa et al. · 2016 [cited by applicant]
US 20160301577A1 · Lane · 2016 [cited by examiner]
US 20170033986A1 · Anderson · 2017 [cited by examiner]
US 20170048158A1 · Park et al. · 2017 [cited by applicant]
US 20170093866A1 · Ben-Noon et al. · 2017 [cited by applicant]
US 20180351791A1 · Nagarajan et al. · 2018 [cited by applicant]
US 20190342989A1 · Toyama · 2019 [cited by examiner]
US 20200274876A1 · Mathew et al. · 2020 [cited by applicant]
US 20200382446A1 · Jung · 2020 [cited by examiner]
US 20210261096A1 · Kabany · 2021 [cited by examiner]
US 20210397433A1 · Itatsu · 2021 [cited by examiner]
US 20210400452A1 · Baba · 2021 [cited by examiner]
US 20230142079A1 · Iwata · 2023 [cited by examiner]
JP 2003218928A · 2003 [cited by applicant]
JP 2011014033A · 2011 [cited by applicant]
JP 2017220220A · 2017 [cited by applicant]
JP 2018192876A · 2018 [cited by applicant]
Apr. 30, 2024 Notice of Allowance issued in U.S. Appl. No. 17/436,702. [cited by applicant]
U.S. Appl. No. 18/772,798. [cited by applicant]
English Translation of PCT/JP2019/041025 International Patent Application filed on Oct. 18, 2019. [cited by applicant]
U.S. Appl. No. 17/436,702, filed Sep. 7, 2021 in the name of Yusuke Yamamoto et al. [cited by applicant]
Jan. 4, 2024 U.S. Office Action issued in U.S. Appl. No. 17/436,702. [cited by applicant]