---
sourceDocument: Yokohama Telecommunications Service Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/telecom-service-ops

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Telecommunications Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Telecom Discovery using Telecommunications Discovery Patterns

# Telecom Discovery using Telecommunications Discovery Patterns {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Telecom Discovery using Telecommunications Discovery Patterns

Telecommunications Discovery Patterns (TSOM Patterns) in ServiceNow enable the discovery of standalone network functions (xNFs) such as telecom routers and switches without relying on their management systems.
These patterns utilize protocols like SNMP and CLI, with NETCONF support planned, to gather detailed network infrastructure data.
Built on the Horizontal Discovery engine, TSOM Patterns provide a scalable approach to uncovering telecom network elements, generating comprehensive configuration item (CI) data for the CMDB.
Show full answer Show less  

## Key Features

* **Horizontal Discovery Integration:** Uses the versatile and scalable Horizontal Discovery application to collect multi-layer data across network, IT, and cloud environments.
* **Preconfigured Telecom Patterns:** Includes out-of-the-box patterns for discovering various telecom devices such as Cisco routers, Juniper MX routers, and switches, supporting both standard and vendor proprietary MIBs.
* **Standalone xNF Discovery:** Detects standalone network elements independently, bypassing management systems, enhancing visibility for telecom-specific infrastructure.
* **MID Server Utilization:** Facilitates secure communication and data transfer between ServiceNow and network devices within the customer's environment.
* **Identification \& Reconciliation Engine (IRE):** Supports data integrity by reconciling discovered data across multiple sources, maintaining CMDB accuracy.
* **CMDB Compliance Audits:** Enables certification and remediation of telecom CMDB data discrepancies through automated workflows.
* **Extensibility:** Customers can extend or create TSOM patterns to tailor discovery to their specific telecom assets and environments.
* **Configurable Execution:** Allows customers to choose whether to run only TSOM patterns or both TSOM and ITOM patterns for discovery, controlled by system properties.
* **TNI Model Alignment:** Discovery results conform to the Telecommunications Network Inventory (TNI) data model, ensuring consistent representation of complex hardware hierarchies.

## Practical Benefits for ServiceNow Customers

* **Comprehensive Telecom Asset Visibility:** Gain deep insights into standalone telecom devices without dependency on management systems, improving network inventory accuracy.
* **Enhanced CMDB Accuracy:** Leverage IRE and CMDB Compliance to detect and remediate data discrepancies, ensuring reliable telecom configuration data.
* **Improved Discovery Precision:** Utilize telecom-specific patterns that support proprietary MIBs and detailed hierarchy modeling, surpassing general IT discovery.
* **Flexible Deployment:** Integrate discovery seamlessly into existing ServiceNow environments with support for MID Servers and configurable pattern execution.
* **Future-Ready Architecture:** Benefit from ongoing enhancement plans including NETCONF protocol support and expanded device types.

## Next Steps for Implementation

To configure Telecommunications Discovery Patterns, customers should ensure they have the required TSOM Visibility plugin, update patterns from the ServiceNow Store, and set system properties according to their discovery preferences. Integration with TNI and use of MID Servers are essential components for effective deployment.  
The new Telecommunication Discovery Patterns (also known as TSOM Patterns) include patterns for discovering standalone xNFs. These patterns enable the discovery of standalone network elements without a management system, using SNMP, CLI, and NETCONF (roadmap) protocols.

## Architecture using Horizontal Discovery and Telecommunications Discovery Patterns {#telecom-discovery-using-telecommunication-discovery-pattern__section_r4g_45j_zdc}

This is an example of the implementation for standalone SNMP or/and CLI xNFs.

## Horizontal Discovery Application {#telecom-discovery-using-telecommunication-discovery-pattern__section_rtw_hvj_zdc}

The Horizontal Discovery application in ServiceNow is a versatile and highly scalable discovery engine
designed to operate effectively across network, IT, and cloud environments, collecting data across multiple layers to provide a holistic view of the infrastructure.

For more information, see [Horizontal discovery process flow with patterns](https://www.servicenow.com/docs/access?context=disco-process-flow-patterns&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US).

## Telecommunications Discovery Patterns (TSOM Patterns) {#telecom-discovery-using-telecommunication-discovery-pattern__section_jxg_qvj_zdc}

A pattern is a sequence of commands designed to detect attributes of a configuration item (CI) and its outbound connections. Telecom Discovery provides a set of preconfigured Patterns that cover a wide range of network elements. The
TSOM Discovery Patterns fall under the infrastructure category, which are used by Horizontal Discovery to generate lists and resource structure of xNFs.

This plugin introduces Patterns for discovering standalone xNFs, such as telecom routers and switches (with support for other device types planned in the future). These xNFs don't rely on a management system or require direct discovery by bypassing their management systems. Additionally, custom patterns are included for verifying various network devices. This is a customer-visible plugin.

## MID Server {#telecom-discovery-using-telecommunication-discovery-pattern__section_o4r_cwj_zdc}

MID Server is a Java application that runs as a Windows service or UNIX daemon on a server within your local network. The ServiceNow®
MID Server facilitates communication and data transfer between a ServiceNow instance and external applications, data sources, and services.

For more information, see [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).

## Identification \& Reconciliation Engine (IRE) {#telecom-discovery-using-telecommunication-discovery-pattern__section_mx4_swj_zdc}

IRE offers a centralized framework for identifying and reconciling data from multiple sources. It verifies the integrity of the CMDB and some non-CMDB tables when various data sources are used to create or update CI records.

For more information, see [Telecom Discrepancy Identification and Reconciliation](https://servicenow-prod.fluidtopics.net/SOGZrFfCJ5tSkJGZlOLDSA "Telecom Discrepancy Identification & Reconciliation confirms that ServiceNow’s CMDB/TNI accurately reflects the updated state of the network and remains synchronized with planned or designed inventory resources.").

## CMDB Compliance Certification Audits for Telecom Discrepancy Identification \& Reconciliation {#telecom-discovery-using-telecommunication-discovery-pattern__section_emb_wwj_zdc}

CMDB Compliance is a toolset that enables administrators to certify CMDB data for accuracy and resolve any discrepancies found. In Telecom Discrepancy Identification \& Reconciliation, we use the Certification Audits feature to
discover and analyze discrepancies in the CMDB, generate Certification Follow-on Tasks, and enable remediation workflows.

For more information on how it's used for Discrepancy Identification \& Reconciliation, see [Telecom Discrepancy Identification and Reconciliation](https://servicenow-prod.fluidtopics.net/SOGZrFfCJ5tSkJGZlOLDSA "Telecom Discrepancy Identification & Reconciliation confirms that ServiceNow’s CMDB/TNI accurately reflects the updated state of the network and remains synchronized with planned or designed inventory resources.").

## ITOM vs TSOM Discovery Behavior for Stand-alone SNMP or/and CLI xNFs {#telecom-discovery-using-telecommunication-discovery-pattern__section_dcn_fxj_zdc}

{#telecom-discovery-using-telecommunication-discovery-pattern__table_tlv_3xj_zdc__entry__2}

| ITOM Discovery | TSOM Discovery (Telecom) |
|-|-|
| Based on Horizontal Discovery Patterns. | Based on Horizontal Discovery Patterns (for Telecommunications). |
| Discover basic equipment flat information which is primarily used for the IT purposes. | Discover more attributes and a deeper CI hierarchy based on equipment type. |
| Only standard MIBs are supported. | Both standard and vendor proprietary MIBs are supported. |
| No discrepancy detection and remediation available OOB. | Discrepancy detection and automatic or manual remediation available OOB. |
[ ]

{#telecom-discovery-using-telecommunication-discovery-pattern__table_tlv_3xj_zdc}

* Telecom Discovery is built on the ITOM Discovery application, leveraging the Nebula Discovery Language (NDL).
* The solution includes a set of telecom-specific patterns and system properties.
* Users can choose whether to run TSOM or ITOM patterns.
* Customers can extend TSOM patterns or create their own if necessary.
* There's no dependency between TSOM Visibility and Telecom Network Inventory (TNI).
{#telecom-discovery-using-telecommunication-discovery-pattern__ul_jzx_nxj_zdc}

## Logic added to Telecom Discovery {#telecom-discovery-using-telecommunication-discovery-pattern__section_bkz_2yj_zdc}

Users can define whether they want to use Telecommunications Discovery Patterns (also known as TSOM patterns) with ITOM patterns for execution. By default, all patterns created in TSOM/Telecom Discovery execute the original ITOM
pattern (for example, the 'Telco Router' pattern also executes the 'Router' pattern). However, customers have the option to choose whether they want to execute only the TSOM pattern and exclude the ITOM pattern.

This parameter affects only the patterns developed as part of the TSOM Patterns application for Telco customers. If the property is set to true (default), the TSOM pattern will also execute specific ITOM shared libraries from the TSOM
pattern.

This logic is controlled via the system property: sn_tsom_patterns.itom_pattern_enabled.

Follows the TNI model -- Telecommunications Discovery Patterns always follow the TNI data model. This means that if Telecom Discovery identifies a card-on-card scenario, it doesn't insert it as a card-on-card.
Instead, it modifies the structure by synthesizing a subslot on the parent card and inserting the child card into that subslot.

TNI entity creation logic -- Whenever the system identifies that the customer has TNI installed, it will automatically create a TNI entity record for all network data discovered. If TNI is installed, a payload
like the one below will be added to the IRE payload for each item. As a result, the discovered CI is in both the cmdb_ci and tni_entity tables.
* **[Telecom Router Pattern](https://servicenow-prod.fluidtopics.net/_qUbxQs5WOzaGFu1IH_HDA#telecom-router-pattern)**   
  The ServiceNow® Telecom Discovery application uses the Telecom Router discovery pattern to find SNMP-based routers in the network. Discovering some of these resources requires updating the Telecommunications Discovery Patterns (TSOM Patterns) from the ServiceNow Store.
* **[Telecom Cisco 7613 Router Pattern](https://servicenow-prod.fluidtopics.net/Zr3T~2ZnMijWmEZDYOgEDA#telecom-cisco7613-router-pattern)**   
  The ServiceNow Telecom Discovery application uses the Telecom Cisco 7613 Router discovery pattern to find SNMP-based Cisco 7613 in the network. Discovering some of these resources requires updating the Telecommunications Discovery Patterns (TSOM Patterns) from the ServiceNow Store.
* **[Telecom Juniper MX SSH Router Pattern](https://servicenow-prod.fluidtopics.net/dEmOJVb8ZtHABwLGWhtQjQ#telecom-juniper-mx-ssh-router-pattern)**   
  The ServiceNow® Telecom Discovery application uses the Telecom Juniper MX SSHRouter discovery pattern to find SNMP and CLI -based Juniper MX Series routers in the network. Discovering some of these resources requires updating the Telecommunications Discovery Patterns (TSOM Patterns) from the ServiceNow® store.
* **[Telecom Cisco Switch Pattern](https://servicenow-prod.fluidtopics.net/DpmPgdyh9rAfWOpe~SAdbQ#telecom-cisco-switch-pattern)**   
  The ServiceNow® Telecom Discovery application uses the Telecom Cisco Switch discovery pattern to find SNMP-based Cisco switches in the network. Discovering some of these resources requires updating the Telecommunications Discovery Patterns (TSOM Patterns) from the ServiceNow® Store.
* **[Telecom Switch Pattern](https://servicenow-prod.fluidtopics.net/Jd4kYg6srDQq2z940K6S8w#telecom-switch-pattern)**   
  The ServiceNow® Telecom Discovery application uses the Telecom Switch discovery pattern to find SNMP-based Telecom switches in the network. Discovering some of these resources requires updating the Telecommunications Discovery Patterns (TSOM Patterns) from the ServiceNow® Store.
* **[Configure Telecommunications Discovery (TSOM) Patterns](https://servicenow-prod.fluidtopics.net/nco9q0vAZvRynA_Z0~wUfA#configuring-telecommunications-discovery-patterns)**   
  This document outlines the dependencies, requirements, and installation steps necessary for setting up Telecommunications Discovery Patterns (also known as TSOM Patterns) in TSOM Visibility in ServiceNow®.