# US 2018/0025556 A1 · Communication system for controlling or monitoring vehicle components

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0025556 A1
- Document ID: US20180025556A1
- Status: Published application
- Kind: A1
- Application number: 15/218,529
- Filed: 2016-07-25
- Published: 2018-01-25
- Earliest claimed: 2016-07-25
- Assignees: General Electric Company
- Applicants: General Electric Company
- Inventors: Sethu Madhavan; Dattaraj Jagdish Rao; Fang Zhou Chen; Arunachala Karthik Sridharan; Dinesh Balaraman Thilla; Prabhu Marimuthu
- Web page: https://patentgrep.com/patent/US20180025556A1

## CPC

- G06F 13/4027: {using bus bridges (G06F13/4022 takes precedence)}
- G06F 3/0637: {Permissions}
- G06F 21/121: {Restricting unauthorised execution of programs}
- G06F 21/31: User authentication
- G06F 21/44: Program or device authentication
- G06F 21/606: {by securing the transmission between two devices or processes}
- G07C 5/008: {communicating information to a remotely located station (transmission systems for measured values G08C)}
- G07C 5/0825: {using optical means}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G07C: TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE

## Abstract

A controller may receive interface information, associated with one or more interfaces used to communicate with one or more components of a vehicle, and may receive application information associated with one or more applications configured to receive information from the one or more components via the one or more interfaces. The controller may store, based on the interface information and the application information, registration information that indicates whether the one or more applications are permitted to communicate via the one or more interfaces. The controller may receive, from an application of the one or more applications, a request for vehicle information from an interface of the one or more interfaces. The controller may verify whether the application is permitted to communicate via the interface, and may selectively route the request for the vehicle information to the interface based on verifying whether the application is permitted to communicate via the interface.

## Claims

### Claim 1

A system, comprising:
a controller configured to:
receive interface information associated with one or more interfaces used to communicate with one or more components of a vehicle;
receive application information associated with one or more applications configured to receive information from the one or more components of the vehicle via the one or more interfaces;
store, based on the interface information and the application information, registration information that indicates whether the one or more applications are permitted to communicate via the one or more interfaces;
receive, from an application of the one or more applications, a request for vehicle information from an interface of the one or more interfaces;
verify whether the application is permitted to communicate via the interface; and
selectively route the request for the vehicle information to the interface based on verifying whether the application is permitted to communicate via the interface.

### Claim 2 (depends on 1)

The system of claim 1, where the interface is included in an interface group that includes a plurality of interfaces; and
where the controller, when verifying whether the application is permitted to communicate via the interface, is configured to:
verify whether the application is permitted to communicate via the interface group.

### Claim 3 (depends on 1)

The system of claim 1, where the controller, when verifying whether the application is permitted to communicate via the interface, is configured to:
determine one or more application types permitted to communicate via the interface;
determine an application type of the application; and
verify whether the application is permitted to communicate via the interface based on the application type of the application and the one or more application types permitted to communicate via the interface.

### Claim 4 (depends on 1)

The system of claim 1, where the controller, when verifying whether the application is permitted to communicate via the interface, is configured to:
determine one or more entities whose applications are permitted to communicate via the interface;
determine an entity associated with the application; and
verify whether the application is permitted to communicate via the interface based on the entity associated with the application and the one or more entities whose applications are permitted to communicate via the interface.

### Claim 5 (depends on 1)

The system of claim 1, where the controller is configured to receive the interface information and the application information based on loading one or more executables.

### Claim 6 (depends on 1)

The system of claim 1, where the one or more applications are separate from the one or more interfaces.

### Claim 7 (depends on 1)

The system of claim 1, where the one or more interfaces are separate from the one or more components of the vehicle.

### Claim 8

A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors, cause the one or more processors to:
store registration information that indicates whether an application, of one or more applications, is permitted to communicate via an interface of one or more interfaces,
the one or more interfaces being configured to be used to communicate with one or more sensors of a vehicle,
the one or more applications being configured to request information from the one or more sensors of the vehicle via the one or more interfaces;
receive, from the application, a request for vehicle information from a sensor of the one or more sensors;
verify, based on the registration information, whether the application is permitted to communicate via an interface, of the one or more interfaces, associated with the sensor; and
selectively provide the request for the vehicle information to the interface based on verifying whether the application is permitted to communicate via the interface.

### Claim 9 (depends on 8)

The non-transitory computer-readable medium of claim 8, where the registration information indicates whether the application is permitted to communicate with an interface group associated with the interface and associated with at least one other interface; and
where the one or more instructions, that cause the one or more processors to verify whether the application is permitted to communicate via the interface, cause the one or more processors to:
verify whether the application is permitted to communicate via the interface group.

### Claim 10 (depends on 8)

The non-transitory computer-readable medium of claim 8, where the interface is included in an interface group that includes a plurality of interfaces; and
where the one or more instructions, that cause the one or more processors to selectively provide the request for the vehicle information to the interface, cause the one or more processors to:
selectively provide the request for the vehicle information to the interface group.

### Claim 11 (depends on 8)

The non-transitory computer-readable medium of claim 8, where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
receive compatibility information that indicates whether communications of the application are compatible with the interface; and
where the one or more instructions, that cause the one or more processors to store the registration information, cause the one or more processors to:
store the registration information based on the compatibility information.

### Claim 12 (depends on 8)

The non-transitory computer-readable medium of claim 8, where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
determine whether one or more operating requirements, associated with the application, satisfy one or more criteria; and
where the one or more instructions, that cause the one or more processors to store the registration information, cause the one or more processors to:
store the registration information based on determining whether the one or more operating requirements satisfy the one or more criteria.

### Claim 13 (depends on 8)

The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to verify whether the application is permitted to communicate via the interface, cause the one or more processors to:
determine an application identifier associated with the application; and
verify whether the application is permitted to communicate via the interface based on the application identifier.

### Claim 14 (depends on 8)

The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to verify whether the application is permitted to communicate via the interface, cause the one or more processors to:
verify whether the application is permitted to communicate via the interface based on a global indicator that indicates whether any applications are permitted to access the interface.

### Claim 15

A method, comprising:
receiving, by a device, interface information associated with a plurality of interfaces used to communicate with a plurality of components of a vehicle;
receiving, by the device, application information associated with a plurality of applications configured to request information from at least one component, of the plurality of components, via at least one interface of the plurality of interfaces;
storing, by the device and based on the interface information and the application information, registration information that indicates whether an application, of the plurality of applications, is permitted to communicate via one or more of the plurality of interfaces;
receiving, by the device and from the application, a request for vehicle information from a component of the plurality of components;
verifying, by the device and based on the registration information, whether the application is permitted to communicate via an interface, of the plurality of interfaces, associated with the component; and
selectively providing, by the device, the request for the vehicle information to the interface based on verifying whether the application is permitted to communicate via the interface.

### Claim 16 (depends on 15)

The method of claim 15, where the plurality of applications, the plurality of interfaces, and the plurality of components are separate.

### Claim 17 (depends on 15)

The method of claim 15, where selectively providing the request comprises:
transmitting the request to the interface when the application is permitted to communicate via the interface; and
dropping the request when the application is not permitted to communicate via the interface.

### Claim 18 (depends on 15)

The method of claim 15, where the registration information indicates whether communications of the application are compatible with communications of the interface.

### Claim 19 (depends on 15)

The method of claim 15, where verifying whether the application is permitted to communicate via the interface comprises:
verifying whether the application is permitted to communicate via the interface based on at least one of:
an application identifier that identifies the application, or
a type of the application.

### Claim 20 (depends on 15)

The method of claim 15, where at least two of the plurality of applications are associated with different operating systems.
