Remote Embedded Device Update Platform Apparatuses, Methods and Systems

• US 20160294605A1
• Filed: 01/06/2016
• Published: 10/06/2016
• Est. Priority Date: 07/07/2014
• Status: Abandoned Application

• Current Assignee: Harman Connected Services, Inc. (Samsung Electronics Co. Ltd.)
• Original Assignee: Symphony Teleca Corporation (Samsung Electronics Co. Ltd.)
• Inventors: Searle, Mark Douglas, Griffin, Owen James, Kempf, Robert Franz Klaus
• Application Number:
  US14/989,684
• Publication Number:
  US 20160294605A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/052 using standardised network management architectures, e.g. telecommunication management network [TMN] or unified network management architecture [UNMA]
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0873 Checking configuration conflicts between network elements
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

The Remote Embedded Device Update Platform Apparatuses, Methods and Systems (“REDUP”) transforms telemetry inputs via REDUP components into remote embedded updates outputs. The REDUP may include a memory and processor with instructions to: obtain a remote embedded device connection request message from a remote embedded device and analyze the message to determine a version of embedded instructions on the remote embedded device. With that, the REDUP may determine if other remote embedded a devices similar to the remote embedded device have provided request messages by searching a remote embedded device connection request message database. This allows the REDUP to determine if a potential issue requiring updates on the remote embedded device exists. With that, the REDUP may determine and provide an update for the remote embedded device.

Claims

1. A remote connected device event data administering apparatus, comprising:

a memory;

a component collection in the memory, including;

an event logging administering component;

a processor disposed in communication with the memory, and configured to issue a plurality of processing instructions from the component collection stored in the memory,

wherein the processor issues instructions from the event logging administering component, stored in the memory, to;

retrieve, via processor, event logging configuration settings for a device, wherein the event logging configuration settings include data regarding what kinds of events to log and an event data format in which to log events data;

obtaining, via processor, event data for a reported event associated with a device component of the device;

ascertain, via processor, whether a network connection to a remote server is available;

determine, via processor, upon ascertaining that a network connection is available, an offloadable event to upload to the remote server;

generate, via processor, an event message that includes event data for the offloadable event, wherein the event data for the offloadable event is formatted in accordance with the event data format; and

send, via network, the event message to the remote server.

2. The apparatus of claim 1, wherein the event logging configuration settings include data regarding memory usage thresholds.

3. The apparatus of claim 1, wherein the device is a vehicle.

4. The apparatus of claim 3, wherein the device component is an electronic control unit of the vehicle.

5. The apparatus of claim 3, wherein the device component is an app installed on an infotainment unit of the vehicle.

6. The apparatus of claim 1, wherein, upon ascertaining that a network connection is not available, the device opportunistically looks to establish a network connection with the remote server using any of a plurality of network interfaces available to the device.

7. The apparatus of claim 6, wherein the device periodically checks for network connectivity at any of the plurality of network interfaces.

8. The apparatus of claim 1, further comprising:

the processor issues instructions from the event logging administering component, stored in the memory, to;

store, via processor, upon ascertaining that a network connection is not available, event data for the reported event in the memory.

9. The apparatus of claim 8, wherein the event data for the reported event is stored in volatile memory.

10. The apparatus of claim 9, further comprising:

the processor issues instructions from the event logging administering component, stored in the memory, to;

transfer, via processor, event data for an event from volatile memory to non-volatile memory upon determining that a memory usage threshold associated with the volatile memory has been exceeded.

11. The apparatus of claim 10, wherein event data for the oldest event with the lowest priority is transferred.

12. The apparatus of claim 8, further comprising:

the processor issues instructions from the event logging administering component, stored in the memory, to;

delete, via processor, event data for an event from the memory upon determining that a memory usage threshold associated with the memory has been exceeded.

13. The apparatus of claim 1, wherein the offloadable event is the newest event with the highest priority.

14. The apparatus of claim 1, wherein the remote server is associated with a device manufacturer of the device, and the sent event data are not shared with other device manufacturers.

15. The apparatus of claim 1, wherein the remote server is associated with a plurality of device manufacturers, and the sent event data are shared among the plurality of device manufacturers.

16. A processor-readable remote connected device event data administering non-transient physical medium storing processor-executable components, the components, comprising:

a component collection stored in the medium, including;

an event logging administering component;

wherein the event logging administering component, stored in the medium, includes processor-issuable instructions to;

retrieve, via processor, event logging configuration settings for a device, wherein the event logging configuration settings include data regarding what kinds of events to log and an event data format in which to log events data;

obtaining, via processor, event data for a reported event associated with a device component of the device;

ascertain, via processor, whether a network connection to a remote server is available;

determine, via processor, upon ascertaining that a network connection is available, an offloadable event to upload to the remote server;

generate, via processor, an event message that includes event data for the offloadable event, wherein the event data for the offloadable event is formatted in accordance with the event data format; and

send, via network, the event message to the remote server.

17. A processor-implemented remote connected device event data administering system, comprising:

an event logging administering component means, to;

retrieve, via processor, event logging configuration settings for a device, wherein the event logging configuration settings include data regarding what kinds of events to log and an event data format in which to log events data;

obtaining, via processor, event data for a reported event associated with a device component of the device;

ascertain, via processor, whether a network connection to a remote server is available;

determine, via processor, upon ascertaining that a network connection is available, an offloadable event to upload to the remote server;

generate, via processor, an event message that includes event data for the offloadable event, wherein the event data for the offloadable event is formatted in accordance with the event data format; and

send, via network, the event message to the remote server.

18. A processor-implemented remote connected device event data administering method, comprising:

executing processor-implemented event logging administering component instructions to;

retrieve, via processor, event logging configuration settings for a device, wherein the event logging configuration settings include data regarding what kinds of events to log and an event data format in which to log events data;

obtaining, via processor, event data for a reported event associated with a device component of the device;

ascertain, via processor, whether a network connection to a remote server is available;

determine, via processor, upon ascertaining that a network connection is available, an offloadable event to upload to the remote server;

generate, via processor, an event message that includes event data for the offloadable event, wherein the event data for the offloadable event is formatted in accordance with the event data format; and

send, via network, the event message to the remote server.