# US 2021/0081335 A1 · Managing memory in an electronic device

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

- Number: US 2021/0081335 A1
- Document ID: US20210081335A1
- Status: Published application
- Kind: A1
- Application number: 16/996,448
- Filed: 2020-08-18
- Published: 2021-03-18
- Earliest claimed: 2019-09-12
- Assignees: NXP B.V.
- Applicants: NXP B.V.
- Inventors: Alexandre Frey; Ralf Malzahn; Frank Ernst Johannes Siedel; Shameer Puthalan; Andreas Lessiak; Daniel Kershaw
- Web page: https://patentgrep.com/patent/US20210081335A1

## CPC

- G06F 12/145: {the protection being virtual, e.g. for virtual blocks or segments before a translation mechanism}
- G06F 12/1483: {using an access-table, e.g. matrix or list}
- G06F 12/0238: {Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory}
- G06F 12/0292: {using tables or multilevel address translation means (G06F12/023 takes precedence; address translation in virtual memory systems G06F12/10)}
- G06F 12/0873: Mapping of cache memory to specific storage devices or parts thereof
- G06F 21/79: in semiconductor storage media, e.g. directly-addressable memories
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 21/552: {involving long-term monitoring or reporting}
- G06F 2212/7201: Logical to physical mapping or translation of blocks or pages
- G06F 2221/2141: Access rights, e.g. capability lists, access control lists, access tables, access matrices
- Y02D 10/00: Energy efficient computing, e.g. low power processors, power management or thermal management
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

There is described a method of managing memory in an electronic device, the method comprising creating a set of equally sized logical regions in a logical address space, each logical region comprising a plurality of consecutive logical addresses, and mapping a subset of consecutive logical addresses within each logical region to a set of physical addresses within a corresponding physical memory region, the subset of consecutive logical addresses comprising the first logical address within the logical region, said first logical address being mapped to a base address within the corresponding physical memory region. Furthermore, there is described a controller for managing memory in an electronic device and a method of determining a physical memory address in a physical memory region using such a controller.

## Claims

### Claim at position 1

1-15. (canceled)

### Claim 16

A method of managing memory in an electronic device, the method comprising
creating a set of equally sized logical regions in a logical address space, each logical region comprising a plurality of consecutive logical addresses, and
mapping a subset of consecutive logical addresses within each logical region to a set of physical addresses within a corresponding physical memory region, the subset of consecutive logical addresses comprising the first logical address within the logical region, said first logical address being mapped to a base address within the corresponding physical memory region.

### Claim 17 (depends on 16)

The method according to claim 16, further comprising
creating a permission mapping associating a permission type to each logical region and to each execution context of a plurality of execution contexts.

### Claim 18 (depends on 17)

The method according to claim 17, wherein each execution context of the plurality of execution contexts corresponds to one of a plurality of operating systems.

### Claim 19 (depends on 17)

The method according to claim 17, wherein creating the permission mapping comprises
creating a first permission table indicating for each logical region whether or not the logical region is accessible to each of the plurality of execution contexts, the first permission table further indicating a region type for each logical region, and
creating a second permission table indicating for each region type whether each of a plurality of permission types is given or not.

### Claim 20 (depends on 19)

The method according to claim 19, wherein the plurality of permission types comprises a read permission, a write permission, an execute permission, and a privileged permission.

### Claim 21

A controller for managing memory in an electronic device, the controller comprising
a memory comprising
a set of equally sized logical regions in a logical address space, each logical region comprising a plurality of consecutive logical addresses, and
a mapping of a subset of consecutive logical addresses within each logical region to a set of physical addresses within a corresponding physical memory region, the subset of consecutive logical addresses comprising the first logical address within the logical region, said first logical address being mapped to a base address within the corresponding physical memory region, and
a processing unit operable to access the memory and adapted to determine a physical address corresponding to any logical address based on the logical regions and the mapping.

### Claim 22 (depends on 21)

The controller according to claim 21, wherein the processing unit is adapted to determine the physical address by
identifying the logical region containing the logical address,
determining an offset for the logical address relative to the first logical address within the identified logical region,
identifying the base address within the corresponding physical memory region, and
determining the physical address by adding the identified base address and the determined offset.

### Claim 23 (depends on 21)

The controller according to claim 21,
wherein the memory further comprises a permission mapping associating permission types to each logical region and to each execution context of a plurality of execution contexts, and
wherein the processing unit is further adapted to determine permission types for a selected logical region and a selected execution context.

### Claim 24 (depends on 23)

The controller according to claim 23, wherein each execution context of the plurality of execution contexts corresponds to one of a plurality of operating systems.

### Claim 25 (depends on 23)

The controller according to claim 23,
wherein the permission mapping comprises
a first permission table indicating for each logical region whether or not the logical region is accessible to each of a plurality of execution contexts, the first permission table further indicating a region type for each logical region, and
a second permission table indicating for each region type whether each of a plurality of permission types is given or not, and
wherein the processing unit is further adapted to identify a region type corresponding to the selected logical region and to identify the permission types that are given for the identified region type.

### Claim 26 (depends on 25)

The controller according to claim 25, wherein the plurality of permission types comprises a read permission, a write permission, an execute permission, and a privileged permission.

### Claim 27

A method of determining a physical address in a physical memory region using a controller, the controller comprising a memory comprising a set of equally sized logical regions in a logical address space, each logical region comprising a plurality of consecutive logical addresses, and a mapping of a subset of consecutive logical addresses within each logical region to a set of physical addresses within a corresponding physical memory region, the subset of consecutive logical addresses comprising the first logical address within the logical region, said first logical address being mapped to a base address within the corresponding physical memory region, the method comprising
receiving a logical address,
identifying the logical region containing the logical address,
determining an offset for the logical address relative to the first logical address within the identified logical region,
identifying the base address within the corresponding physical memory region, and
determining the physical address by adding the identified base address and the determined offset.

### Claim 28 (depends on 27)

The method according to claim 27, wherein the memory further comprises a permission mapping associating permission types to each logical region and to each execution context of a plurality of execution contexts, the method further comprising
determining permission types for a selected logical region and a selected execution context.

### Claim 29 (depends on 28)

The method according to claim 28, wherein each execution context of the plurality of execution contexts corresponds to one of a plurality of operating systems.

### Claim 30 (depends on 28)

The method according to claim 28, wherein the permission mapping comprises
a first permission table indicating for each logical region whether or not the logical region is accessible to each of a plurality of execution contexts, the first permission table further indicating a region type for each logical region, and
a second permission table indicating for each region type whether each of a plurality of permission types is given or not,
the method further comprising
identifying a region type corresponding to the selected logical region, and
identifying the permission types that are given for the identified region type.
