G06F8/65

Methods and systems for continuous asynchronous code deployment

Systems, methods and computer program products are presented for the automated deployment of a code update to a device. One or more clusters of devices may be connected to a development environment for deployment of one or more code updates through respective development pipelines to the respective clusters of devices. A first cluster of devices receives a module for implementation of an agent for the first cluster of devices and a central queue local to a centralized controller of the development environment. The agent reports at least one status of a respective device to the centralized controller of the development environment, whereby that status may correspond to a code update image pulled onto the respective device. The agent retrieves one or more instruction messages from the centralized controller in response to the reported status of the respective device.

Methods and systems for continuous asynchronous code deployment

Systems, methods and computer program products are presented for the automated deployment of a code update to a device. One or more clusters of devices may be connected to a development environment for deployment of one or more code updates through respective development pipelines to the respective clusters of devices. A first cluster of devices receives a module for implementation of an agent for the first cluster of devices and a central queue local to a centralized controller of the development environment. The agent reports at least one status of a respective device to the centralized controller of the development environment, whereby that status may correspond to a code update image pulled onto the respective device. The agent retrieves one or more instruction messages from the centralized controller in response to the reported status of the respective device.

Method for updating firmware of optical transceiver
11579863 · 2023-02-14 · ·

Provided is an optical transceiver including: a controller configured to output firmware update data for updating firmware of another optical transceiver connected to the optical transceiver through an optical cable; and a transmitter configured to generate an optical signal by superposing input payload data and the firmware update data, and to transmit the optical signal to the other optical transceiver. According to embodiments, the firmware of a remote optical transceiver at a remote location is automatically updated without affecting payload data, which is information to be transmitted.

Method for updating firmware of optical transceiver
11579863 · 2023-02-14 · ·

Provided is an optical transceiver including: a controller configured to output firmware update data for updating firmware of another optical transceiver connected to the optical transceiver through an optical cable; and a transmitter configured to generate an optical signal by superposing input payload data and the firmware update data, and to transmit the optical signal to the other optical transceiver. According to embodiments, the firmware of a remote optical transceiver at a remote location is automatically updated without affecting payload data, which is information to be transmitted.

Method and control unit for configuring an addon interface
11579900 · 2023-02-14 · ·

A method and control unit for configuring an add-on interface of a vehicle are presented. The vehicle comprises at least one vehicle internal system, at least one add-on system, the add-on system being arranged in the vehicle after the vehicle is produced by a manufacturer, and at least one internal communication unit arranged for communication with at least one vehicle external communication unit. The method comprises: receiving, using the at least one internal communication unit, configuration information related to at least one sensor of the vehicle from the at least one vehicle external communication unit; and configuring, based on the configuration information, how at least one sensor signal S.sub.sensor from the at least one sensor is to be processed by an add-on interface, the add-on interface being arranged in the vehicle as an interface between the at least one vehicle internal system and the at least one add-on system.

Method and control unit for configuring an addon interface
11579900 · 2023-02-14 · ·

A method and control unit for configuring an add-on interface of a vehicle are presented. The vehicle comprises at least one vehicle internal system, at least one add-on system, the add-on system being arranged in the vehicle after the vehicle is produced by a manufacturer, and at least one internal communication unit arranged for communication with at least one vehicle external communication unit. The method comprises: receiving, using the at least one internal communication unit, configuration information related to at least one sensor of the vehicle from the at least one vehicle external communication unit; and configuring, based on the configuration information, how at least one sensor signal S.sub.sensor from the at least one sensor is to be processed by an add-on interface, the add-on interface being arranged in the vehicle as an interface between the at least one vehicle internal system and the at least one add-on system.

Provisioning network devices using a vendor-neutral platform

Network devices are provisioned using a single vendor-neutral data model with a non-relational database. Provisioning requirements are collected upon detecting a new network device that needs to be configured and/or installed. Based on the provisioning requirements, a configuration object is retrieved using a data model in the non-relational database. The configuration object is transformed to a concrete configuration file for the network device. After applying the configuration file to the network device, a separate process validates the configuration of the network device by comparing the observed network configuration with the initial target configuration data included in the configuration object.

Provisioning network devices using a vendor-neutral platform

Network devices are provisioned using a single vendor-neutral data model with a non-relational database. Provisioning requirements are collected upon detecting a new network device that needs to be configured and/or installed. Based on the provisioning requirements, a configuration object is retrieved using a data model in the non-relational database. The configuration object is transformed to a concrete configuration file for the network device. After applying the configuration file to the network device, a separate process validates the configuration of the network device by comparing the observed network configuration with the initial target configuration data included in the configuration object.

Method and engineering system for modifying a program of an industrial automation component

A method for modifying a program of an industrial automation component, wherein the program includes a plurality of program elements, where the program is structured in units, a unit includes a group of program elements and can include both published program elements having an interface that can be referenced by the program elements of other units and unpublished program elements, and where a checksum is calculated and is assigned to the unit using the interfaces, such that if at least one program element of the version of the unit stored in the engineering system is modified, then the modified checksum is compared with the previous checksum version present in the automation component, and only the modified unit is transferred if the checksums match such that consistency of the program is maintained and the software updateable more quickly.

Method and engineering system for modifying a program of an industrial automation component

A method for modifying a program of an industrial automation component, wherein the program includes a plurality of program elements, where the program is structured in units, a unit includes a group of program elements and can include both published program elements having an interface that can be referenced by the program elements of other units and unpublished program elements, and where a checksum is calculated and is assigned to the unit using the interfaces, such that if at least one program element of the version of the unit stored in the engineering system is modified, then the modified checksum is compared with the previous checksum version present in the automation component, and only the modified unit is transferred if the checksums match such that consistency of the program is maintained and the software updateable more quickly.