Physical Service Access Point

Description

The Physical Service Access Point (PHY-SAP) is a standardized service interface, a point where the Medium Access Control (MAC) layer accesses the services provided by the Physical Layer (PHY). It is not a physical connector but a logical reference point defined in 3GPP specifications (primarily TS 25.321 for MAC and TS 25.212 for PHY in UTRA, with equivalents in LTE and NR). The SAP defines a set of primitives—abstract, implementation-independent messages—that flow between the layers. These primitives represent requests, indications, responses, and confirmations for specific services.

How the PHY-SAP works involves the exchange of specific data units and control information. The primary data units are Transport Blocks (TBs). The MAC layer delivers one or more Transport Blocks to the PHY via the PHY-SAP for transmission on a specific transport channel (e.g., DCH, HS-DSCH, RACH). Each TB includes the data payload and associated control information from MAC, such as the Transport Format (TF) which specifies the block size, modulation, and coding scheme. Conversely, the PHY delivers received Transport Blocks up to the MAC layer via the same SAP. Additionally, the PHY-SAP carries Hybrid Automatic Repeat Request (HARQ) acknowledgments (ACK/NACK) for packet retransmission control and measurement reports (e.g., Channel Quality Indicator - CQI) from the PHY to the MAC to assist in scheduling decisions.

The key components of the PHY-SAP are the defined primitives and their parameters. Common primitives include PHY-DATA-REQ (request to transmit a TB), PHY-DATA-IND (indication of a received TB), PHY-STATUS-IND (for reporting measurements or errors), and primitives for controlling random access procedures. Its role in the network is to ensure a clean, standardized separation of concerns between the MAC and PHY layers. This allows for independent development, testing, and optimization of each layer. For example, a base station vendor can design a sophisticated PHY implementation (with advanced antennas) while adhering to the SAP, ensuring it works with a standard MAC scheduler from another vendor. It encapsulates the complexity of the radio transmission and reception process, presenting a simpler data transport service to the MAC layer.

Purpose & Motivation

The PHY-SAP exists to formalize the interaction between the MAC and PHY layers, promoting modularity and interoperability in wireless communication systems. It solves the problem of tightly coupled, proprietary implementations where the MAC and PHY are designed as a single, inseparable unit. This tight coupling would hinder innovation, complicate testing, and make it difficult to mix and match components from different suppliers in a multi-vendor network environment.

The historical motivation stems from the structured, layered approach of communication protocol design (like the OSI model). By defining a precise service interface, 3GPP ensures that the functional responsibilities of each layer are clear. The MAC layer handles logical channel multiplexing, scheduling, and priority handling, while the PHY handles the raw signal transmission. The SAP clearly demarcates this boundary. This was particularly important as 3GPP systems evolved to support multiple Radio Access Technologies (RATs) and carrier aggregation, where a single MAC layer might need to interface with different PHY instances (e.g., LTE and NR).

It addresses the limitation of ad-hoc interfaces that could change with each technology release, causing compatibility breaks. The PHY-SAP provides a stable abstraction. Even as the underlying PHY technology advanced dramatically from WCDMA to OFDMA-based LTE to flexible NR, the core concept of the SAP—exchanging transport blocks and control information—remained, allowing higher-layer protocols to evolve at a different pace. Its creation was driven by the need for a scalable, future-proof architecture that could accommodate new physical layer features (like new numerologies or massive MIMO) without redesigning the entire protocol stack, thus reducing development time and cost for equipment manufacturers.

Key Features

• Defines the abstract service primitives for data transfer between MAC and PHY
• Specifies the Transport Block (TB) as the fundamental data exchange unit
• Carries control information like Transport Format (TF) for transmission configuration
• Transports HARQ feedback (ACK/NACK) for retransmission management
• Delivers physical layer measurements (e.g., CQI, RSRP) to the MAC scheduler
• Enables layer independence and multi-vendor interoperability

Evolution Across Releases

Defining Specifications