NOTE

Network Operator Tunneling Exchange

Core Network →
Introduced in Rel-4 Also in: Services, Core Network

NOTE is a functional entity or reference point that facilitates secure tunneling and data exchange between network operators for services like SMS, MMS, or location-based services.

Category
Core Network
Introduced
Rel-4
Where
Management
Also touches
2 segments
Specifications
9 specs
NOTE Description Purpose Related Classification Detected Changes Specifications

Description

The Network Operator Tunneling Exchange (NOTE) is a 3GPP architectural concept that provides a standardized mechanism for one network operator to securely access and utilize services hosted within another operator's network domain. It acts as a gateway or an exchange point that encapsulates service requests and data within a secure tunnel, ensuring privacy, integrity, and controlled access. While the provided definition snippet is incomplete, the term's context across specifications like TS 22.261 (service requirements) and TS 29.238 (SIP-based signaling) suggests its role in enabling inter-PLMN service delivery for multimedia and messaging services.

Architecturally, NOTE can be implemented as a dedicated network node or a logical function, often residing at the boundary between two operators' networks. It typically interfaces with core network elements like the IP Multimedia Subsystem (IMS) or messaging gateways. For a service like Multimedia Messaging Service (MMS), if a subscriber on Operator A sends an MMS to a subscriber on Operator B, Operator A's MMS server may use the NOTE interface to relay the message through Operator B's network to the recipient. The NOTE function handles the necessary protocol adaptation, security (e.g., using IPsec or TLS), and routing, ensuring the service request is properly formatted and authorized for the foreign network.

Its operation involves several key components: a tunneling protocol stack to create a secure connection, authentication and authorization mechanisms to verify the requesting operator's identity, and service logic to translate or route the encapsulated service data units. The NOTE abstracts the complex topology and internal configurations of the partner operator's network. From the perspective of the home operator's service node, it simply forwards data to a NOTE address; the NOTE entity then assumes responsibility for delivering it to the correct internal endpoint within the visited network. This model simplifies inter-operator peering agreements and service integration, as operators only need to manage a single, standardized exchange point rather than multiple point-to-point connections to various internal network elements.

Purpose & Motivation

NOTE was created to solve the problem of scalable and secure inter-operator service delivery. In early mobile networks, enabling services like MMS or location-based services across different operators often required complex, bilateral integrations between specific network elements (e.g., MMS centers), which was not scalable with a growing number of operators and services. The purpose of NOTE is to provide a unified, standardized gateway function that decouples the internal network architecture of one operator from the service requests of another.

This addresses significant limitations of prior ad-hoc approaches, which were costly to establish and maintain, and could create security vulnerabilities due to the exposure of internal network interfaces. By funneling inter-operator traffic through a dedicated tunneling exchange, operators can enforce consistent security policies, perform centralized logging and charging for inter-operator transactions, and more easily manage roaming and peering partnerships. Its introduction, particularly noted around Rel-4 with the rise of packet-switched services and IMS, was motivated by the industry's move towards all-IP networks and a richer ecosystem of multimedia services that inherently required seamless cross-operator functionality to be valuable to end-users.

Classification

Part ofPLMN
Related approachesIMSMMS

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-4, normative work from Rel-17.

Rel-17 1 change

In Release 17, the NOTE function was enhanced to support operator-provided end-to-end security for factory networks. This specifically enables secure communication services over 5G LAN-type services within defined areas like a factory plant, ensuring the service meets pertinent QoS requirements. The security is applied end-to-end at the communication service interface.

  • Operator provided end-to-end security for factory networks TS 22.261CR0430

Explore further

Broader topics and technologies where NOTE plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 22.261 vk30 5G System Service Requirements Rel-20
TR 22.975 v1310 UMTS Numbering and Addressing Requirements Rel-4
TS 24.229 vj50 IMS call control protocol based on SIP and SDP Rel-19
TR 28.836 vi00 Technical Report on Intent Driven Management Rel-18
TS 29.238 vj00 H.248 Profile for IBCF-TrGW Interface Rel-19
TS 32.602 vj00 Basic Configuration Management IRP Information Service Rel-19
TS 32.612 vj00 Bulk Configuration Management IRP: Information Service Rel-19
TS 32.662 vj00 Configuration Management (CM); Kernel CM IRP Rel-19
TS 32.690 vj00 Inventory Management IRP Requirements Rel-19