LLC to GPRS Mobility Management service access point

Description

LLGMM (LLC to GPRS Mobility Management service access point) is a well-defined logical point of interconnection between the Logical Link Control (LLC) layer and the GPRS Mobility Management (GMM) sublayer within the protocol stack of a mobile station (MS) and the Serving GPRS Support Node (SGSN). It is one of several Service Access Points (SAPs) defined for the LLC layer, each identified by a Service Access Point Identifier (SAPI). The LLGMM-SAPI is specifically reserved for signaling messages related to GMM procedures. The SAP acts as a conduit: the GMM sublayer passes its protocol data units (PDUs) down to the LLC layer via the LLGMM SAP for transmission, and the LLC layer delivers incoming GMM PDUs up through the same SAP.

The operation involves the LLC layer providing a reliable, acknowledged-mode logical link for the LLGMM SAP. This is crucial because GMM signaling includes critical procedures such as GPRS attach and detach, routing area updates, authentication, ciphering key establishment, and service requests. These messages must be delivered securely and in sequence to maintain network registration, security, and mobility tracking. The LLC layer handles segmentation (if needed), ciphering using the GPRS ciphering key (if ciphering is activated), sequence numbering, error recovery via retransmissions, and flow control for the LLGMM data stream independently from user data streams (which use other SAPs like LLC-SAPI).

At the mobile station, the GMM sublayer generates signaling messages like ATTACH REQUEST or ROUTING AREA UPDATE REQUEST. These are passed as LLC service data units (SDUs) to the LLC layer via the LLGMM SAP. The LLC layer creates an LLC frame with the appropriate SAPI value for LLGMM, processes it (including possible ciphering), and forwards it to the RLC/MAC layer for radio transmission. At the SGSN, the reverse process occurs: the LLC layer receives the frame, deciphers it, validates sequence numbers, and delivers the GMM PDU to the SGSN's GMM entity via the LLGMM SAP. This separation of signaling and user data SAPs allows independent management and prioritization; for instance, signaling can be given higher priority or different reliability settings.

Purpose & Motivation

The LLGMM SAP was defined to create a clean, standardized interface for transporting GPRS mobility management signaling over the packet-switched domain. In early GSM, mobility management for circuit-switched services used different channels and protocols. With the introduction of GPRS, a dedicated, reliable signaling channel was needed for packet-data mobility, separate from user data, to ensure robust network attachment, security, and location management.

Its creation addresses the problem of multiplexing different types of traffic (signaling vs. user data) over the same logical link while applying appropriate treatment to each. By assigning a specific SAPI for GMM, the network can apply distinct LLC operational modes (acknowledged mode is mandatory for LLGMM) and potentially different ciphering contexts. This separation enhances security, as signaling messages for authentication and key agreement are protected, and improves reliability, ensuring that mobility events are processed correctly even in poor radio conditions through LLC retransmissions.

Historically, without a dedicated SAP like LLGMM, signaling might have been mixed with user data, leading to potential conflicts in reliability requirements and processing delays. The LLGMM SAP enables efficient handling of mobility procedures, which are time-sensitive for maintaining registration and enabling seamless mobility. It is a foundational element that supports core GPRS/UMTS functionalities like inter-SGSN routing area updates, where signaling integrity is paramount for transferring the mobile's context between network nodes without service interruption.

Key Features

• Defines the interface for GMM signaling between LLC and GMM layers
• Uses a specific Service Access Point Identifier (SAPI) reserved for GMM
• Operates exclusively in LLC acknowledged mode for reliability
• Supports ciphering of GMM signaling messages for security
• Allows independent processing from user data flows
• Essential for procedures like attach, routing area updates, and security control

Evolution Across Releases

Defining Specifications