Physical Layer Runtime Memory Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing memory systems require memory controllers to handle various runtime services specific to different memory technologies, increasing complexity and cost, as they need to perform training routines and power management for each technology, which can be cumbersome and inefficient.

Innovation Solution

The implementation of a physical layer (PHY) that performs runtime services such as training routines and power management, allowing generic memory controllers to work with multiple memory technologies without needing to understand the specifics of each technology, by receiving requests from the memory controller, performing the necessary routines, and communicating the completion status.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the memory controller handles runtime services for multiple memory technologies, then the system supports multiple memory types, but the memory controller complexity increases

Engineering Contradiction:
Improvesupport for multiple memory technologiesVSAvoidmemory controller complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A PHY layer is introduced as an intermediary between the memory controller and the memory device. The PHY layer handles technology-specific runtime services (training routines, power management) while the memory controller maintains a generic design. This mediator absorbs the complexity of different memory technologies, allowing the controller to remain simple while supporting multiple memory types.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is segmented into distinct functional layers: the memory controller handles high-level memory management, while the PHY layer handles technology-specific runtime services. This segmentation separates concerns, allowing each component to be optimized independently - the controller for portability and the PHY for technology adaptation.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If the memory controller performs training routines and power management, then runtime services are handled, but the cost and complexity of the memory controller increase

Engineering Contradiction:
Improveruntime service handlingVSAvoidmemory controller complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The PHY layer serves as an intermediary that performs training routines and power management operations. Instead of the memory controller directly handling these complex technology-specific tasks, the PHY layer mediates between the controller and the memory device, executing the runtime services and returning results to the controller.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The PHY layer is designed to autonomously handle runtime services without requiring the memory controller to understand the specifics of training routines or power management. The PHY layer self-manages these operations, making the system easier to operate while keeping the controller simple.

Inventive Principle:
Principle #25Self-service

3Device complexity

If a generic memory controller is used for multiple memory technologies, then cost is reduced, but the controller needs external support for technology-specific services

Engineering Contradiction:
Improvememory controller complexityVSAvoidsupport for multiple memory technologies
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system architecture is segmented such that the memory controller remains generic and simple, while the PHY layer handles technology-specific adaptations. This segmentation allows the controller to be reused across different memory technologies without modification, reducing cost while maintaining versatility through the PHY layer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The PHY layer acts as an intermediary that enables a generic memory controller to work with multiple memory technologies. The PHY layer translates between the generic controller interface and the specific requirements of different memory technologies, providing versatility without increasing controller complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20240371427A1Runtime Memory Services in Physical Layer
Publication Date: 2024.11.07 ATI TECHNOLOGIES ULC
  • US20240371427A1 patent drawing
  • US20240371427A1 patent drawing
  • US20240371427A1 patent drawing

AI summary

A memory system includes a memory controller, a physical layer (PHY), and a memory (e.g., DRAM). Data is written to and read from the memory in different manners for different memory technologies, such as using different signals or signal timings for different memory technologies. Various runtime services specific to the memory technology are performed by the PHY rather than the memory controller. Examples of such runtime services include performing a training routine to train or re-train an interface between the PHY and the memory, performing a power management routine (e.g., to put the main memory in a self-refresh mode), and so forth.