Upgrading a physical security system having multiple server nodes

• US 10,474,449 B2
• Filed: 04/27/2018
• Issued: 11/12/2019
• Est. Priority Date: 04/10/2015
• Status: Active Grant

• Current Assignee: Motorola Solutions, Inc.
• Original Assignee: Avigilon Corporation (Motorola Solutions, Inc.)
• Inventors: Aw, Kevin, Chen, Kan Ru, Chiang, Avery, Goldenberg, Tomer, Grieman, Jonathon, Ho, Thanh Tam, Pan, Feng
• Primary Examiner(s): Nguyen, Phillip H
• Application Number:
  US15/964,810
• Publication Number:
  US 20180285095A1
• Time in Patent Office: 564 Days
• Field of Search: 717168, 717174
• CPC Class Codes: G06F 21/51 at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G07C 9/00571 operated by interacting with a central unit
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A physical security system that includes multiple server nodes may be upgraded by receiving an upgrade installation package from a client and propagating the installation package between at least two of the server nodes. One of the server nodes (“source server”) receives the installation package from the client and another of the server nodes (“requesting server”) requests and receives the installation package from the source server. To transfer the installation package from the source to the requesting server, the source server notifies the requesting server that the installation package is present at the source server, the requesting server then sends the source server a request for the installation package, and the source server then sends the installation package to the requesting server in response to the request. The requesting server may then be upgraded by running the installation package.

Claims

1. A method comprising:

receiving, at a first server running a first operating system, an installation package from a client of a physical security system;

sending, from the first server to a computer appliance running a second operating system different than the first operating system, a notification indicating that the installation package is at the first server;

after the computer appliance receives the notification, sending a request from the computer appliance to the first server for the installation package;

sending the installation package to the computer appliance from the first server in response to the request; and

upgrading a second server on the computer appliance by running the installation package at the computer appliance.

2. The method of claim 1 wherein the notification includes sending an identifier for the installation package from the first server to the second server.

3. The method of claim 2 wherein the second server uses the identifier to determine whether the second server already has the installation package, and wherein the second server sends the request when the second server determines it does not already have the installation package.

4. The method of claim 1 wherein the installation package includes part of an installer blob that is received at the first server, the installer blob further including installer metadata associated with the installation package.

5. The method of claim 4 wherein the installation package received from the client includes the installer metadata, and the method further comprising:

generating, at the source server and after receiving the installer metadata, a database entry including the installer metadata.

6. The method of claim 5 wherein the notification includes the database entry.

7. A method comprising:

receiving, at a first server on a computer appliance running a first operating system, an installation package from a client of a physical security system;

sending, from the first server to a second server running a second operating system different than the first operating system, a notification indicating that the installation package is at the first server;

after the second server receives the notification, sending a request from the second server to the first server for the installation package;

sending the installation package to the second server from the first server in response to the request; and

upgrading the second server by running the installation package at the second server.

8. The method of claim 7 wherein the notification includes sending an identifier for the installation package from the first server to the second server.

9. The method of claim 8 wherein the second server uses the identifier to determine whether the second server already has the installation package, and wherein the second server sends the request when the second server determines it does not already have the installation package.

10. The method of claim 7 wherein the installation package includes part of an installer blob that is received at the first server, the installer blob further including installer metadata associated with the installation package.

11. The method of claim 10 wherein the installation package received from the client includes the installer metadata, and the method further comprising:

generating, at the source server and after receiving the installer metadata, a database entry including the installer metadata.

12. The method of claim 11 wherein the notification includes the database entry.