Carrier Requirements for iOS 18 RCS Support

With the release of iOS 18, Apple added support for Rich Communication Services (RCS), modernizing cross-platform communication between iPhone and Android devices. However, enabling this functionality requires specific backend infrastructure updates from mobile network operators. This article outlines the core technical, protocol, and provisioning requirements carrier networks must implement to successfully deliver RCS messaging to iPhone users running iOS 18.

1. GSMA Universal Profile Compliance

Apple's implementation of RCS relies strictly on the GSMA Universal Profile (UP), primarily Universal Profile 2.4. Carriers must deploy an RCS backend that adheres to this standard. Unlike Android, which often routes RCS via Google Jibe by default, iOS does not rely on proprietary client overlays. Network operators must host their own GSMA-compliant RCS core or partner with an authorized hosted service provider that adheres directly to the GSMA specifications.

2. IP Multimedia Subsystem (IMS) Core

RCS operates as an IMS-based service. To support iOS 18 devices, the carrier's network must fulfill several IMS prerequisites:

  • VoLTE/VoNR Availability: Devices must be registered on an active IMS core typically used for Voice over LTE (VoLTE) or Voice over New Radio (VoNR).
  • SIP Signaling Support: The IMS core must properly handle Session Initiation Protocol (SIP) signaling to manage session setup, tear-down, and delivery reports (sent, delivered, read receipts).
  • APN Configuration: Proper Access Point Name (APN) routing must be configured to allow RCS signaling and media traffic without throttling or blocking protocol-specific ports.

3. Apple Carrier Bundle and Entitlement Integration

Apple regulates network-level features through carrier bundles distributed directly through iOS updates. To activate RCS:

  • Carrier Profile Update: The carrier must work with Apple to integrate RCS flags into their official carrier settings file (carrier.plist).
  • GSMA TS.43 Service Entitlement: Carriers must deploy a TS.43-compliant Entitlement Server. This allows iOS 18 devices to query the network during activation, authenticate the device, and check if the user's specific rate plan and SIM profile permit RCS messaging.
  • Apple RCS Provisioning: The toggle inside Settings > Apps > Messages > RCS Messaging only appears once Apple validates the carrier's network readiness and pushes the relevant carrier bundle.

4. Media Storage and Content Delivery

RCS allows for higher-resolution photo and video sharing, larger file transfers, and audio messaging. Carriers must maintain the appropriate data transfer mechanisms:

  • MSRP (Message Session Relay Protocol): Required for near real-time text exchange, typing indicators, and small payload deliveries within chat sessions.
  • HTTP File Transfer (FT over HTTP): Required for larger multimedia payloads. Carriers must deploy resilient content servers or Content Delivery Networks (CDNs) to temporarily store encrypted media assets until the recipient downloads them.

5. Inter-Carrier Peering and Interconnects

For RCS to work outside a single mobile network, operators must maintain functional interconnects:

  • Inter-Carrier Hubs: Operators must establish peering agreements through direct network interfaces (NNI) or third-party RCS transit hubs.
  • Number Portability and Routing: Routing registries must correctly resolve target numbers across competing carriers to prevent messages from falling back to SMS or MMS when sent to non-native networks.