MSK

Minimum-shift keying

Physical Layer →
Introduced in Rel-8 Also in: Core Network, Services

MSK is a constant-envelope, continuous-phase frequency-shift keying modulation scheme that is spectrally efficient and resilient to non-linear amplification, historically used in GSM and mobile communications.

Category
Physical Layer
Introduced
Rel-8
Where
Security
Also touches
2 segments
Specifications
15 specs
MSK Description Purpose Related Classification Detected Changes Specifications

Description

Minimum-shift keying (MSK) is a specific type of continuous-phase frequency-shift keying (CPFSK) characterized by a modulation index of 0.5. This choice of index results in the minimum frequency separation between the two symbol states (typically representing binary 0 and 1) that allows them to be orthogonal over a symbol period, hence the name 'minimum-shift'. The constant envelope and continuous phase of the modulated signal are its defining properties. The constant envelope means the signal's amplitude does not vary with the modulating data, which allows it to be amplified by highly efficient, non-linear power amplifiers (like Class C amplifiers) without significant spectral regrowth or distortion. The continuous phase ensures there are no abrupt phase transitions, leading to a compact power spectral density with low out-of-band emissions.

Mathematically, an MSK signal can be represented as a form of offset quadrature phase-shift keying (OQPSK) with sinusoidal pulse shaping. This equivalence is valuable for understanding its generation and detection. In practice, MSK can be generated using a voltage-controlled oscillator (VCO) modulated directly by the data, or more stably using the OQPSK-like modulator structure with a sinusoidal weighting function on the in-phase (I) and quadrature (Q) data streams. The demodulation of MSK can be performed using coherent detection, similar to PSK, or using non-coherent detection like discriminator detection, which was advantageous in early, simpler receivers.

In 3GPP systems, MSK's most notable application was in the GSM standard for the 0.3 GMSK (Gaussian Minimum Shift Keying) modulation used in the radio interface. GMSK is MSK with Gaussian pre-modulation filtering to further smooth the phase transitions and constrain the spectral occupancy even more tightly, which was critical for meeting GSM's stringent adjacent channel power requirements. While later 3GPP systems (UMTS, LTE, 5G NR) moved to linear modulation schemes like QPSK and QAM for higher spectral efficiency, MSK/GMSK principles remain relevant for understanding constant-envelope modulation, and MSK itself is still used in other wireless standards like Bluetooth (using GFSK, a generalization) and satellite communications.

Purpose & Motivation

MSK was developed to address the need for a power-efficient and spectrally efficient digital modulation scheme for channels with non-linear characteristics, particularly in mobile radio and satellite communications. Linear modulation schemes like QPSK, while spectrally efficient, have varying envelopes. When passed through non-linear power amplifiers (which are more power-efficient), these variations cause spectral spreading into adjacent channels (spectral regrowth) and signal distortion. MSK's constant envelope property makes it inherently immune to these effects, allowing the use of efficient, saturated amplifiers without requiring costly and inefficient linearization techniques.

The 'minimum-shift' property (modulation index = 0.5) was chosen to maximize spectral efficiency for a given bit error rate performance under non-coherent detection, which was simpler to implement in early mobile receivers. It represents the optimal trade-off in CPFSK: a smaller index would reduce bandwidth but sacrifice noise immunity, while a larger index would improve noise performance at the cost of bandwidth. MSK provided a good balance, enabling reliable communication within constrained radio spectrum. Its evolution to GMSK in GSM was a direct response to the need for even tighter control of the spectrum to support high-capacity cellular networks with minimal interference between adjacent radio channels.

Classification

Specific typesGMSKFSK

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (15 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Studied in Rel-8, normative work from Rel-15.

Rel-15 4 changes

In Release 15, the MSK (MBS Service Key) function was introduced as part of the multicast/broadcast service (MBS) security context, which is managed by the MBSF and MB-SMF. The specification defines procedures for establishing this context during session setup and for updating the MSK, which triggers a session update to distribute the new key to UEs. Furthermore, it clarifies the interaction for MSK provisioning via the control plane and specifies that MSK updates necessitate a PDU Session Modification procedure.

  • Mobility - Correcting AS re-keying and NAS re-keying in N2-handover TS 33.501CR0242
  • Mobility - Resolving EN and corrections in AS re-keying TS 33.501CR0305
  • Interworking - correcting keying material in HO request message (EPS to 5GS) TS 33.501CR0390
  • Shift of text from SEPP intro to subclause TS 33.501CR0458
Rel-16 2 changes

In Release 16, the MSK (MBS Service Key) function was enhanced to enable its provisioning and updates via the control plane through the MB-SMF, specifically for multicast security. The procedure allows the MBSF, acting as the security function, to initiate updates by providing an updated MSK and optional MTK to the MB-SMF, which then triggers a PDU Session Modification to distribute the new security context to UEs. Notably, this defined procedure is explicitly not applicable when only the MTK requires updating without an MSK change.

  • Minimum length of port management information container in SM messages TS 24.501CR2480
  • Minimum length of "Plain 5GS NAS message" TS 24.501CR2564
Rel-17 3 changes

In Release 17, the specification introduced new procedures for handling the MSK (MBS Service Key) within the multicast/broadcast security context. Specifically, it defined mechanisms for updating the MSK via control plane procedures initiated by the MBSF and for providing this updated key to UEs through PDU Session Modification. Furthermore, it clarified the interaction for MSK updates separately from MTK-only updates and aligned Non-Seamless WLAN Offload (NSWO) procedures for the MSK and PMK.

  • Usage of indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure TS 24.501CR3843
  • CR on MTK or MSK processing TS 23.247CR0139
  • NSWO alignment for MSK and PMK TS 33.501CR1427
Rel-18 4 changes

In Release 18, a key enhancement for the MSK function was enabling the AUSF to send back the MBS Service Key to the W-AGF following successful EAP authentication. This change specifically facilitates the provisioning of the MSK for an MBS session via the control plane when the MBSF acts as the MBS security function. The update procedure allows the MBSF to provide an updated MSK, and optionally an updated MTK, to the MB-SMF for distribution to UEs in the related MBS session.

  • Minimum length of Alternative NSSAI IE TS 24.501CR5556
  • AUSF sends back MSK to W-AGF after successful EAP authentication TS 33.501CR1810
  • Maximum and minimum length of NSAG information IE TS 24.501CR4679
  • Correction on the minimum length of the SLAC TS 24.501CR6061
Rel-19 2 changes

In Release 19, the MSK (MBS Service Key) function was enhanced to support Standalone Non-Public Networks (SNPN) and to resolve an issue related to the 3GPP-Charging ID-v2. Furthermore, the specification provided a clarification regarding the minimum value of the T3540 timer within the MSK update procedures.

  • Support MSK for SNPN and resolve EN for 3GPP-Charging ID-v2 TS 29.561CR0197
  • Clarification to the minimum value of T3540 TS 24.501CR6810

Explore further

Broader topics and technologies where MSK plays a role.

Defining Specifications

3GPP specifications that define or reference MSK, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.247 vj30 5G Multicast/Broadcast Service Architecture Rel-19
TS 24.501 vj50 5G NAS Protocols Specification Rel-19
TS 26.346 vj20 MBMS User Services Media Codecs & Protocols Rel-19
TS 26.517 vj10 5G MBS User Service Protocols and Formats Rel-19
TR 26.946 vj00 MBMS User Services Overview Rel-19
TS 29.561 vj30 5G Interworking with External Data Networks Rel-19
TS 31.102 vj40 USIM Application Specification Rel-19
TS 33.246 vj00 MBMS Security Specification Rel-19
TS 33.320 vj00 H(e)NB Subsystem Security Architecture Rel-19
TS 33.402 vj00 Security for non-3GPP access to EPS Rel-19
TS 33.501 vk00 5G Security Architecture and Procedures Rel-20
TS 33.545 vj20 Security for NR Femto Subsystem Rel-19
TR 33.882 vi01 Technical Report on 5G Security for Personal IoT Networks Rel-18
TS 33.888 vc10 Security Study for Group Communication in LTE Rel-12
TS 38.769 vk00 Ambient IoT Solutions in NR Rel-20