# US 2025/0165142 A1 · Communication Network, Method and Device for operating with a Distributed Memory Space

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

- Number: US 2025/0165142 A1
- Document ID: US20250165142A1
- Status: Published application
- Kind: A1
- Application number: 18/947,708
- Filed: 2024-11-14
- Published: 2025-05-22
- Earliest claimed: 2023-11-17
- Assignees: NXP USA, Inc.
- Applicants: NXP USA, Inc.
- Inventors: Elvis Gabriel Nica; Laura-Anca Viscotel
- Web page: https://patentgrep.com/patent/US20250165142A1

## CPC

- G06F 3/0607: {by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device}
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 3/0659: {Command handling arrangements, e.g. command buffers, queues, command scheduling}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 9/544: {Buffers; Shared memory; Pipes}
- G06F 9/4401: Bootstrapping (security arrangements therefor G06F21/57)
- H04L 67/104: Peer-to-peer [P2P] networks
- H04L 67/108: {characterised by resources being split in blocks or fragments}
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- 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)

## Abstract

A communication network (401) for operating a distributed memory system (DMS) is described. The communication network (401) comprises a plurality of non-operating system (non-OS) embedded devices having at least one memory (390) wherein the at least one memory (390) of the plurality of non-OS embedded devices is configured to have a first portion of memory (310, 330, 350, 370) reserved for the non-OS embedded device and a second portion of memory (320, 340, 360, 380) reserved and available for at least one other non-OS embedded device from the plurality of non-OS embedded devices within the communication network to use.

## Claims

### Claim at position 1

1-15. (canceled)

### Claim 16

A communication network for operating a distributed memory system, DMS, the communication network comprising a plurality of non-operating system, non-OS, embedded devices having at least one memory wherein the at least one memory of the plurality of non-OS embedded devices is configured to have a first portion of memory reserved for the non-OS embedded device and a second portion of memory reserved and available for at least one other non-OS embedded device from the plurality of non-OS embedded devices within the communication network to use.

### Claim 17 (depends on 16)

The communication network of claim 16 wherein a first non-OS embedded device of the plurality of non-OS embedded devices comprises:
a first receiver configured to receive a data chunk;
a first transmitter; and
a signal processor operably coupled to the first receiver, the first transmitter and the at least one memory, and configured to determine whether the at least one memory has memory capacity to store the received data chunk;
and in response to the at least one memory not having memory capacity to store the received data chunk, the first signal processor and first transmitter are configured to send a storage request message to at least one of the plurality of non-OS embedded devices.

### Claim 18 (depends on 17)

The communication network of claim 17 wherein the storage request message comprises at least one of: a write_data_request command; a broadcast storage request message; a multicast storage request message; a storage request message that is directly sent to an identified one of the plurality of non-OS embedded devices indicated by a data mapping algorithm employed by the signal processor.

### Claim 19 (depends on 18)

The communication network of claim 18 wherein the storage request message comprises the write_data_request command and the data chunk is identified by a data chunk identifier, file_id, chunk_id, and a data file_length.

### Claim 20 (depends on 17)

The communication network of claim 17 wherein the first signal processor is configured to divide the received data chunk into fixed-size parsed data chunks and the storage request message is configured to include at least a portion of the fixed-size parsed data chunks, wherein the at least one of the plurality of non-OS embedded devices is configured to store the at least a portion of the fixed size parsed data chunks for use by the first non-OS embedded device.

### Claim 21 (depends on 17)

The communication network of claim 17, wherein a second non-OS embedded device is the at least one of the plurality of non-OS embedded devices and comprises:
a second receiver configured to receive the storage request message from the first non-OS embedded device,
at least one memory operably coupled to the second receiver; and
a second signal processor operably coupled to the second receiver and the at least one memory and configured to determine that the at least one memory has available memory capacity to store the received data chunk, and the at least one memory is configured to store the received data chunk in response thereto.

### Claim 22 (depends on 21)

The communication network of claim 21 wherein the second non-OS embedded device further comprises a second transmitter operably coupled to the second signal processor and the at least one memory, wherein the second signal processor is further configured to:
transmit a data chunk request to the first non-OS embedded device in response to the received storage request message and a determination that the at least one memory has available memory capacity to store the received data chunk; and
receive the received data chunk in response to the transmitted data chunk request.

### Claim 23 (depends on 22)

The communication network of claim 22 wherein, in response to the first non-OS embedded device having received multiple requests for the data chunk from the plurality of non-OS embedded devices, the processor of the first non-OS embedded device is configured to select a request from one of the plurality of non-OS embedded devices being indicative of at least one of: a quality of service, QoS, a proximity-based criteria of a sending device, a load-based analysis.

### Claim 24 (depends on 17)

The communication network of claim 17, wherein, in response to the data chunk being identified as a high priority data chunk, the plurality of non-OS embedded devices is configured to store the same data chunk.

### Claim 25 (depends on 17)

The communication network of claim 17 wherein the storage request message comprises an over-the-air, OTA, system update data file transfer that is sent to a plurality of different non-OS embedded devices in the communication network, wherein the data file transfer is divided into multiple data chunks and respective data chunks of the multiple data chunks are stored temporarily or permanently on a different plurality of non-OS embedded devices across the communication network.

### Claim 26 (depends on 25)

The communication network of claim 25 wherein the first non-OS embedded device is configured to receive the OTA system update data file transfer from at least one of the plurality of different non-OS embedded devices in the communication network and, once validated, load the OTA system update data file transfer into its at least one memory by an overwrite operation of an existing system data file.

### Claim 27 (depends on 26)

The communication network of claim 26 wherein the first non-OS embedded device is configured to perform a write operation of the existing system data file to the plurality of different non-OS embedded devices in the communication network that provides a back-up of the existing system data file prior to an overwrite operation of the existing system data file.

### Claim 28 (depends on 25)

The communication network of claim 25, wherein at least one of: the OTA system update data file transfer, a back-up of an existing system data file prior to an overwrite operation of the existing system data file, is configured to be available to the plurality of different non-OS embedded devices in the communication network.

### Claim 29 (depends on 16)

The communication network of claim 16, wherein the signal processor and transmitter of at least one of: the first non-OS embedded device, the second non-OS embedded device is configured to determine that the non-OS embedded device where it resides requires data, and in response thereto sends a data request message in the communication network to other non-OS embedded devices, wherein the data request message is a request for one of: a data chunk or a whole data file.

### Claim 30 (depends on 16)

The communication network of claim 16 wherein the communication network is configured as an Internet of Things, IoT, network.

### Claim 31

A non-OS embedded device operational within a communication network with plurality of non-OS embedded devices, the non-OS embedded device comprising:
a receiver configured to receive a new data chunk;
a transmitter configured to transmit messages to the plurality of non-OS embedded devices;
at least one memory; and
a signal processor operably coupled to the receiver, the transmitter and the at least one memory, and configured to determine whether the at least one memory has memory capacity to store the received new data chunk;
wherein the at least one memory is configured to comprise:
a first portion of memory reserved for the non-OS embedded device where the at least one memory resides; and
a second portion of memory reserved and available for at least one other non-OS embedded device from the plurality of non-OS embedded devices within the communication network to use.

### Claim 32 (depends on 31)

The non-OS embedded device of claim 31 wherein the at least one memory comprises read only memory, ROM, a network shared ROM, a random access memory, RAM, a network shared RAM, at least one flash memory and at least one network shared flash.

### Claim 33

A method for operating a distributed memory system, DMS, by a communication network, the method comprising:
providing a plurality of non-OS embedded devices operational within the communication network with at least one memory;
configuring the at least one memory of the plurality of non-OS embedded devices to comprise:
a first portion of memory reserved for the non-OS embedded device where the at least one memory resides; and
a second portion of memory reserved and available for at least one other non-OS embedded device from the plurality of non-OS embedded devices within the communication network to use.

### Claim 34 (depends on 33)

The method for operating a DMS of claim 33 further comprising:
receiving a data chunk;
determining whether at least one memory of the the non-OS embedded device has memory capacity to store the received data chunk;
and, in response to the at least one memory not having memory capacity to store the received data chunk, sending a storage request message to at least one other of the plurality of non-OS embedded devices.

### Claim 35 (depends on 34)

The method for operating a DMS of claim 34 wherein the storage request message comprises at least one of: a write_data_request command; a broadcast storage request message; a multicast storage request message; a storage request message that is directly sent to an identified one of the plurality of non-OS embedded devices indicated by a data mapping algorithm employed by the signal processor.
