# US 2020/0349292 A1 · Data bundle generation and deployment

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

- Number: US 2020/0349292 A1
- Document ID: US20200349292A1
- Status: Published application
- Kind: A1
- Application number: 16/898,174
- Filed: 2020-06-10
- Published: 2020-11-05
- Earliest claimed: 2019-04-30
- Assignees: JFrog Ltd.
- Applicants: JFrog Ltd.
- Inventors: Yoav Landman
- Web page: https://patentgrep.com/patent/US20200349292A1

## CPC

- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06F 8/60: Software deployment
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 21/565: {by checking file integrity}
- G06F 21/602: {Providing cryptographic facilities or services}
- H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/3236: {using cryptographic hash functions}
- H04L 9/3247: {involving digital signatures}
- H04W 12/08: Access security
- G06F 21/107: {License processing; Key processing}
- H04L 2209/805: Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The present disclosure provides a method, system, and device for distributing a software release. To illustrate, based on one or more files for distribution as a software release, a release bundle is generated that includes release bundle information, such as, for each file of the one or more files, a checksum, meta data, or both. One or more other aspects of the present disclosure further provide sending the release bundle to a node device. After receiving the release bundle at the node device, the node device receives and stores at least one file at a transaction directory. After verification that each of the one or more files is present/available at the node device, the one or more files may be provided to a memory of a node device and meta data included in the release bundle information may be applied to the one or more files transferred to the memory.

## Claims

### Claim 1

A method for distributing a software release, the method comprising:
receiving, by one or more processors, an indication from a distributor device of one or more files for distribution;
generating, by the one or more processors, a bundle based on the one or more files, the bundle comprising release bundle information generated based on the one or more files;
securing, by the one or more processors, the bundle to generate a secured bundle;
receiving, by the one or more processors, a selection from the distribution device of one or more node devices to receive the secured bundle; and
initiating, by the one or more processors, transmission of the secured bundle to each of the one or more node devices.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving, by one or more processors, a list of release updates from the distributor device, the list of release updates corresponding to the one or more files;
identifying, by the one or more processors, the one or more files based on the list of release updates; and
accessing, by the one or more processors, each of the one or more files.

### Claim 3 (depends on 1)

The method of claim 1, where generating the bundle comprises:
generating, by one or more processors, the release bundle information based on the one or more files.

### Claim 4 (depends on 1)

The method of claim 1, where:
the one or more files include one or more parts;
generating the release bundle information comprises:
for each part of the one or more parts, generating a checksum; and/or
generating a bundle checksum for an entirety of the one or more or more files; and
the bundle does not include the one or more files.

### Claim 5 (depends on 1)

The method of claim 1. where securing the bundle comprises:
attaching, by the one or more processors, a signature to the bundle to generate a signed bundle, the secured bundle including the signed bundle.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
generating, by the one or more processors, the signature based on a private key corresponding to the distributor device.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
verifying, by the one or more processors, that the secured bundle is transmitted to the one or more node devices.

### Claim 8 (depends on 7)

The method of claim 7, where verifying that the secured bundle is transmitted to the one or more node devices comprises:
verifying, by the one or more processors, the one or more files are included in a transaction directory corresponding to the one or more node devices based on a checksum verification.

### Claim 9 (depends on 7)

The method of claim 7, further comprising:
receiving, by the one or more processors, for each file of at least one file included in the transaction directory, a corresponding checksum; and
for each of the received checksums of the at least one file included in the transaction directory, determining whether the checksum matches a checksum of the one or more files.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
based on input received from the distributor device, replacing, by the one or more processors, at least one file of the one or more files with a different file, the bundle generated based on the different file.

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
receiving, by the one or more processors, distribution parameters from the distribution device, the distribution parameters comprising a date, a time, or both, corresponding to the transmission of the secured bundle.

### Claim 12 (depends on 1)

The method of claim 1, further comprising:
receiving, by the one or more processors, a request to initiate a distribution transaction session from the distribution device:
initiating, by the one or more processors, presentation at the distribution device of a user interface for the distribution transaction session;
receiving, by the one or more processors, a transmission request from the distribution device to distribute the secured bundle to the one or more node devices; and
after verification that the secured bundle is transmitted to the one or more node devices and each of the one or more files are present at the one or more node devices, closing, by the one or more processors, the distribution transaction session.

### Claim 13 (depends on 1)

The method of claim 1, where a first node device of the one or more node devices comprises an Internet of things (IoT) device.

### Claim 14 (depends on 1)

The method of claim 1, where the secured bundle is immutable.

### Claim 15

A system for distributing a software release, the system comprising:
at least one memory storing instructions; and
one or more processors coupled to the at least one memory, the one or more processors configured to execute the instructions to cause the one or more processors to:
receive an indication from a distributor device of one or more files for distribution;
generate a bundle based on the one or more files;
secure, by the one or more processors, the bundle to generate a secured bundle;
receive a selection from the distribution device of one or more node devices to receive the secured bundle; and
initiate transmission of the secured bundle to each of the one or more node devices.

### Claim 16 (depends on 15)

The system of claim 15, where the one or more processors are further configured to execute the instructions to cause the one or more processors to generate the bundle comprising release bundle information generated based on the one or more files.

### Claim 17 (depends on 16)

The system of claim 16, where, to generate the release bundle information, the one or more processors are further configured to execute the instructions to cause the one or more processors to, for each file of the one or more files:
generate a corresponding checksum; and
identify corresponding meta data comprising a size of the file, a version of the file, a source of the file, or a combination thereof.

### Claim 18 (depends on 16)

The system of claim 16, where, to generate the release bundle information, the one or more processors are further configured to execute the instructions to cause the one or more processors to, for an entirety of the one or more files, generate a checksum.

### Claim 19 (depends on 15)

The system of claim 15, where to secure the bundle, the one or more processors are further configured to execute the instructions to cause the one or more processors to attach a signature to the bundle to generate a signed bundle, the secured bundle including the signed bundle.

### Claim 20

A method for receiving a software release, the method comprising:
initiating, by one or more processors, a release bundle transaction session corresponding to a software release;
receiving, by the one or more processors, a bundle including secured release bundle information;
verifying, by the one or more processors, a source of the secured release bundle information;
after verification of the source, identifying, by the one or more processors, a transaction directory;
verifying, by the one or more processors, each of one or more files corresponding to the secured release bundle information is included in the transaction directory; and
closing, by the one or more processors, the release bundle transaction session in response to verification, based on the secured release bundle information, that each of the one or more files is included in the transaction directory.

### Claim 21 (depends on 20)

The method of claim 20, where the secured release bundle information comprises signed release bundle information.

### Claim 22 (depends on 21)

The method of claim 21, where the signed release bundle information includes, for each of the one or more files, a checksum and meta data corresponding to the file; where verifying the source of the signed release bundle information comprises:
identifying, by the one or more processors, a signature corresponding to the signed release bundle information, the signature generated based on a private key of a distributor device;
accessing, by the one or more processors, a public key from a memory of a node device, the public key corresponding to the private key; and
decoding, by the one or more processors, the signature based on the public key.

### Claim 23 (depends on 20)

The method of claim 20, further comprising:
identifying, by the one or more processors, one or more files based on the secured release bundle information; and
receiving, by the one or more processors, a file to be loaded into the transaction directory.

### Claim 24 (depends on 20)

The method of claim 20, further comprising:
in response to verification that each of the one or more files is included in the transaction directory, generating, by the one or more processors, a checksum for an entirety of the one or more files; and
identifying, by the one or more processors, a checksum for the whole bundle.

### Claim 25 (depends on 24)

The method of claim 24, further comprising:
comparing, by the one or more processors, the checksum for the entirety of the one or more files and the checksum for the whole bundle;
authorizing, by the one or more processors, transfer of the one or more files from the transaction directory to a memory of a node device based on a match between the checksum for the entirety of the one or more files and the checksum for the whole bundle; and
applying meta data included in the secured release bundle information to the one or more files transferred to the memory.

### Claim 26 (depends on 24)

The method of claim 24, where closing the release bundle transaction session is further based on the checksum for the entirety of the one or more files and the checksum for the whole bundle.

### Claim 27 (depends on 24)

The method of claim 24, further comprising:
in response to a determination that each of one or more files corresponding to the secured release bundle information is not included in the transaction directory, rejecting, by the one or more processors, the software release.

### Claim 28

A system for receiving a software release, the system comprising:
at least one memory storing instructions; and
one or more processors coupled to the at least one memory, the one or more processors configured to execute the instructions to cause the one or more processors to:
initiate a release bundle transaction session corresponding to a software release;
receive a bundle including secured release bundle information;
verify a source of the secured release bundle information;
after verification of the source, identify a transaction directory;
verify each of one or more files corresponding to the secured release bundle information is included in the transaction directory; and
close the release bundle transaction session in response to verification, based on the secured release bundle information, that each of the one or more files is included in the transaction directory, making the one or more files corresponding to the software release available for download via an application program interface (API).

### Claim 29 (depends on 28)

The system of claim 28, where the secured release bundle information comprises signed release bundle information and where the one or more processors are further configured to execute the instructions to cause the one or more processors to:
identify a signature corresponding to the signed release bundle information, the signature generated based on a private key of a distributor device;
access a public key from a memory of a node device; and
decode the signature based on the public key.

### Claim 30 (depends on 28)

The system of claim 28, where the one or more processors are further configured to execute the instructions to cause the one or more processors to distribute the one or more files.
