Universal software communication bus

US11838375B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11838375-B2
Application numberUS-202117453985-A
CountryUS
Kind codeB2
Filing dateNov 8, 2021
Priority dateNov 12, 2020
Publication dateDec 5, 2023
Grant dateDec 5, 2023

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.

Methods and systems are provided for a device for a communications control system. In one example, the device includes a distributed component interconnect framework (DCIF) configured to enable communication between different software modules of a communications network based on already existing code. The DCIF allows simultaneous communication between multiple transport protocols.

First claim

Opening claim text (preview).

The invention claimed is: 1. A method for a communications control system of a vehicle, comprising: operating a distributed component interconnect framework (DCIF) to enable communication between a plurality of different software modules of a communications network based on already existing code; building, with a DCIF Daemon, a catalog of services available over different protocols of the plurality of different software modules; providing a standardized service contract based on the catalog of services available over the different protocols of the plurality of different software modules; and using, with the DCIF, domain specific language (DSL) to define interfaces and components arranged on different nodes and/or domains, wherein the communications network includes a Scalable Service-oriented Middleware over Internet Protocol (SoME/IP) bus of the vehicle; and wherein each of the plurality of different software modules is implemented in an electronic control unit (ECU) of the vehicle that is coupled to the SoME/IP bus. 2. The method of claim 1 , wherein the DSL is selected from a group consisting of: Franca Interface Definition Language (FIDL); and Component Description Language (CDL). 3. The method of claim 1 , wherein the DCIF is configured to support one or more of dynamic service discovery and static configuration. 4. The method of claim 1 , further comprising: building, with the DCIF Daemon, the catalog of services available over different protocols to manage policies and priorities for services in each node of the communications control system. 5. The method of claim 4 , further comprising: managing, with the DCIF, one or more of security, access control, privileges, discovery of services, N-number of transport protocols, encryption, and interface version compatibility. 6. The method of claim 1 , further comprising: hiding, with the DCIF, deployment details of the catalog of services behind the standardized service contract to provide service abstraction; and processing multiple applications simultaneously, the multiple applications configured for different types of hosts. 7. A method for a communications control system, comprising: operating a distributed component interconnect framework (DCIF) to identify and map a plurality of networks of the communications control system, and to determine a configuration of each of the plurality of networks and a plurality of transport protocol types corresponding with the plurality of networks; translating protocols of the plurality of networks to a common protocol via the DCIF to enable communication between the plurality of networks over a Scalable Service-oriented Middleware over Internet Protocol (SoME/IP); building, with a plurality of DCIF Daemons corresponding with the plurality of transport protocol types, a catalog of services available over the protocols of the plurality of networks, providing a standardized service contract based on services provided by the plurality of networks, and providing service abstraction by hiding deployment details of the catalog of services behind the standardized service contract; and processing multiple applications simultaneously, the multiple applications configured for different types of hosts, wherein each of the plurality of transport protocol types has a bus coupled to one of the plurality of DCIF Daemons; wherein each of the plurality of DCIF Daemons is directly coupled to a bus of the common protocol; and wherein each of the plurality of DCIF Daemons is indirectly coupled to the bus of the common protocol through one of a corresponding plurality of Service Data (SD) Daemons of the bus of the common protocol. 8. The method of claim 7 , wherein translating the protocols of the plurality of networks includes defining interfaces and components across different nodes and/or domains using a domain specific language. 9. A method for a communications control system, comprising: operating a distributed component interconnect framework (DCIF) in a connectivity module of the communications control system to allow communication between a plurality of transport protocols through a plurality of communication busses of a network of communication busses, the plurality of communication busses corresponding with the plurality of transport protocols; building a catalog of services available over different protocols of the plurality of transport protocols; and providing a standardized service contract based on the catalog of services provided by the plurality of communication busses, wherein a first electronic control unit (ECU) implements a first communication bus of the plurality of communication busses, a first DCIF Daemon, and a first Scalable Service-oriented Middleware over Internet Protocol (SoME/IP) Daemon; wherein the first communication bus is communicatively coupled to the first DCIF Daemon; wherein the first DCIF Daemon is communicatively coupled to an SoME/IP bus of the network, both directly and indirectly through the SoME/IP bus of the network; wherein a second ECU implements a second communication bus of the plurality of communication busses, a second DCIF Daemon, and a second SoME/IP Daemon; wherein the second communication bus is communicatively coupled to the second DCIF Daemon; and wherein the second DCIF Daemon is communicatively coupled to the SoME/IP bus of the network, both directly and indirectly through the SoME/IP bus of the network. 10. The method of claim 9 , further comprising: using, with the DCIF, a plurality of tools to enable model driven development, wherein the plurality of tools includes code generators. 11. The method of claim 10 , wherein the plurality of tools further includes one or more of modelling with domain specific language, validators, editors, and graphical viewers. 12. The method of claim 9 , wherein the DCIF is configured with a plurality of service interfaces. 13. The method of claim 12 , wherein the plurality of service interfaces includes one or more of a Service Application Programming Interface (SAPI), and a Common Application Programming Interface (CAPI). 14. The method of claim 9 , wherein the DCIF is configured with a plurality of communication protocols and wherein the plurality of communication protocols are middleware protocols used for control messages. 15. The method of claim 14 , wherein the plurality of communication protocols includes one or more of Tesseract, Distributed Service Interface (DSI), and Representational State Transfer (REST). 16. The method of claim 9 , wherein the DCIF is configured with inter-domain communication and wherein the inter-domain communication includes protocol translators and bridges between operating systems. 17. The method of claim 16 , wherein the inter-domain communication enables communication between one or more of Android platforms and QNX operating systems, Linux operating systems and QNX operating systems, Linux operating systems and Integrity operating systems, Android platforms and Integrity operating systems, Automotive open system architecture and Portable Operating System Interface operating systems. 18. The method of claim 9 , wherein the first ECU implements a first Middleware (MW) service; wherein the first communication bus is communicatively coupled to the first MW service; wherein the first MW service is communicatively coupled to the SoME/IP bus of the network; wherein the second ECU implements a second MW service; wherein the second communication bus is communicatively coupled to the second MW service; and wherein the second MW service i

Assignees

Inventors

Classifications

  • H04L67/51Primary

    Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title

  • Graphical or visual programming · CPC title

  • Installation · CPC title

  • by actively collecting configuration information or by backing up configuration information · CPC title

  • Protocols · 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 US11838375B2 cover?
Methods and systems are provided for a device for a communications control system. In one example, the device includes a distributed component interconnect framework (DCIF) configured to enable communication between different software modules of a communications network based on already existing code. The DCIF allows simultaneous communication between multiple transport protocols.
Who is the assignee on this patent?
Harman Int Ind
What technology area does this patent fall under?
Primary CPC classification H04L67/51. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Dec 05 2023 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 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).