Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

Communication information

Communication Information

Services →

Communication information is the data collected and registered by the MCID service for use in lawful interception and fraud detection within 3GPP networks.

Introduced
Rel-7
Where
Services
Specifications
3 specs
Communication information Description Purpose Neighbours Specifications

Description

Communication information is a term used in 3GPP specifications to describe the data collected and registered by the MCID (Malicious Communication Identification) service. The MCID service is a supplementary service that allows the network to identify and trace malicious or nuisance calls. It is specified in 3GPP TS 24.416, 24.516, and 24.616, which cover the MCID service for different core network domains (e.g., CS, PS, IMS). Communication information encompasses various details about a communication session, such as the calling party's identity, the called party's identity, the time and duration of the communication, and any other relevant parameters that can help identify the source of malicious calls. This information is collected and registered by the MCID service for later retrieval and analysis by authorized parties, such as law enforcement agencies or network operators.

The MCID service operates by monitoring incoming communications and, upon request or automatically, recording the communication information. In the context of the IP Multimedia Subsystem (IMS), the MCID service is implemented as an application server that interacts with the core IMS entities. When a user receives a malicious call, they can invoke the MCID service to register the communication information. The service then stores this information in a secure database, which can be accessed by authorized entities. The communication information typically includes the SIP headers, media type, timestamps, and other metadata that can help trace the call. In circuit-switched (CS) and packet-switched (PS) domains, similar mechanisms exist to collect and register communication information.

The collection and registration of communication information are subject to strict privacy and security regulations. The MCID service ensures that the information is only accessible to authorized personnel and is protected against unauthorized access. The service also provides mechanisms for the user to control the registration of communication information, such as enabling or disabling the service or specifying which calls to register. The communication information is stored for a limited period, after which it is deleted, unless required for ongoing investigations. The MCID service is an important tool for combating telecommunication fraud, harassment, and other malicious activities.

In terms of architecture, the MCID service involves several network elements. In IMS, the MCID Application Server (AS) is responsible for collecting and registering communication information. It communicates with the Serving-CSCF (S-CSCF) and the Home Subscriber Server (HSS) to obtain subscriber data and to manage the service. The communication information is stored in the MCID AS or in a separate database. In CS and PS domains, the MCID service may be implemented in the Mobile Switching Center (MSC) or the Serving GPRS Support Node (SGSN), respectively. The service is triggered by the user via a supplementary service code or by the network based on predefined criteria. The communication information is then registered and made available to authorized parties through a secure interface.

The term "communication information" is broad and can encompass various types of data depending on the context. In the MCID service, it specifically refers to the information collected and registered by the service. This includes, but is not limited to, the calling and called party numbers, the time and date of the call, the duration, the location of the calling party (if available), and any other information that can help identify the malicious caller. The exact set of information may vary depending on the network domain and the specific implementation. The 3GPP specifications define the requirements and procedures for the MCID service, ensuring that communication information is collected and registered in a consistent and secure manner across different networks and vendors.

Purpose & Motivation

The concept of communication information within the MCID service was introduced to address the growing need for identifying and tracing malicious or nuisance calls in telecommunication networks. Prior to the MCID service, users had limited means to report and trace such calls, and network operators lacked standardized mechanisms to collect and register the necessary information. The MCID service provides a standardized way to collect communication information, enabling users to report malicious calls and allowing authorized parties to investigate and take action. This is particularly important in the context of increasing telecommunication fraud, harassment, and other malicious activities.

The MCID service and the associated communication information solve several problems. First, they provide a legal and standardized framework for collecting call details, ensuring that privacy and data protection regulations are respected. Second, they enable network operators to offer a value-added service to their subscribers, enhancing customer satisfaction and trust. Third, they assist law enforcement agencies in investigating and prosecuting malicious callers. The communication information collected by the MCID service can be used as evidence in legal proceedings, provided it is collected and handled in accordance with applicable laws.

The introduction of the MCID service in Release 7 was motivated by the need for a unified approach to malicious call identification across different 3GPP domains, including CS, PS, and IMS. Before Release 7, various proprietary solutions existed, but they lacked interoperability and standardization. The 3GPP specifications (TS 24.416, 24.516, 24.616) define the MCID service for IMS, CS, and PS domains, respectively, ensuring consistent behavior and enabling multi-vendor deployments. The communication information collected by the service is a key enabler for these capabilities, providing the necessary data for tracing and identifying malicious callers. Overall, the MCID service and communication information represent a significant step forward in protecting users and networks from malicious activities.

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-7 Initial

Initial introduction of communication information as part of the MCID service. Defined as information collected and registered by the MCID service.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Wording changed slightly: line breaks removed, but the technical content remains identical to Rel-7.

Definition carried over unchanged from Rel-7.

Definition carried over unchanged from Rel-7.

Defining Specifications

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

SpecificationTitleRelease
TS 24.416 v700 Malicious Call Identification Service Rel-7 read
TS 24.516 v830 MCID Protocol Specification for NGN Rel-8 read
TS 24.616 vj00 Malicious Call Identification (MCID) Protocol Rel-19 read