This document provides information on the required fields in the CellRefs file for network configuration data. It lists the fields always required for all technologies and solutions, as well as additional required fields for specific technologies like GSM. The fields store information about sites, sectors, cell identifiers and parameters. Proper format and populated fields are necessary for network analysis tools to work correctly.
Cutc izp deployment guide for nss(draft)Phuoc Phuoc
This document provides an overview and deployment guide for Intelligent Paging on CDMA networks. It describes how the network is divided into paging zones to improve paging channel capacity. When mobiles move between zones or are paged, only the base stations in that zone process the page instead of the entire network. It outlines the call processing and configuration changes needed to implement this feature.
The document discusses Nortel's Multi-Carrier Traffic Allocation (MCTA) feature for 1xRTT networks. MCTA dynamically balances traffic across multiple RF carriers serving the same sector. It operates at call setup and can support up to 3 carriers per sector. The MCTA algorithm selects the best carrier using factors like frequency priority, capacity threshold, and capacity estimates reported by each BTS. MCTA makes decisions either at the BTS or SBS depending on the network configuration.
The document defines and provides default values for several important WCDMA parameters used in change requests (CR) by engineers. It includes parameters for layer management (e.g. soft/hard handover types), cell selection/reselection (e.g. sInterSearch, sIntraSearch), triggered events, and their typical values. The purpose is to familiarize new engineers with the key parameters used in their daily work when creating CRs.
CSFB and eCSFB Overview and call flow desMani132076
Circuit switch fallback (CSFB) and enhanced CSFB (eCSFB) allow users with dual-mode devices to make voice calls on 1xRTT networks while camped on an LTE network. CSFB involves releasing the UE from LTE to CDMA for voice, while eCSFB uses handover coordination between the networks. The document discusses the architectures, parameters, and counters involved in CSFB and eCSFB, including prerequisites, signaling interfaces, broadcast parameters, timers, and troubleshooting steps.
Drive Test and Optimization Tutorial - I.pdfhamdi_saif
The document discusses drive testing procedures and measurements. It describes the required tools for drive testing including a laptop, GPS device, and test software. It outlines key radio parameters measured for 2G, 3G, and 4G networks including signal strength, quality, interference, and throughput. Examples of drive test activities are given such as new site acceptance tests involving calls, SMS, and internet usage to check coverage and quality.
Types Of Window Being Used For The Selected GranuleLeslie Lee
The document discusses different types of mode selective devices that can be used for mode multiplexing over few-mode fiber. Free-space based devices are bulky while fiber based devices are more compact and easier to integrate. Early demonstrations transmitted data over 107 Gb/s using the LP01 and LP11 fiber modes and 58.8 Gb/s using dual modes with electronic MIMO processing for mode separation. Mode selective devices can be categorized as either free-space based or fiber based, with fiber based being preferable due to their compact size and integration capabilities.
Physical design involves taking a synthesized netlist as input and performing floorplanning, placement, and routing to produce a physical layout. Key inputs include the netlist, timing constraints, physical libraries, and technology files. The process involves floor planning to determine block placement and routing areas, power planning to create the power distribution network, and pre-routing of standard cells and power grids. The goal is to meet timing constraints while minimizing area.
ATM is a cell switching and multiplexing technology designed to unify telecommunication network infrastructures. It uses fixed length cells to transport data and signaling information. ATM networks support connections with different quality of service (QoS) levels for various media like voice, video, and data. ATM allows for predictable delivery of real-time media through constant bit rate connections while also supporting bursty data traffic.
Cutc izp deployment guide for nss(draft)Phuoc Phuoc
This document provides an overview and deployment guide for Intelligent Paging on CDMA networks. It describes how the network is divided into paging zones to improve paging channel capacity. When mobiles move between zones or are paged, only the base stations in that zone process the page instead of the entire network. It outlines the call processing and configuration changes needed to implement this feature.
The document discusses Nortel's Multi-Carrier Traffic Allocation (MCTA) feature for 1xRTT networks. MCTA dynamically balances traffic across multiple RF carriers serving the same sector. It operates at call setup and can support up to 3 carriers per sector. The MCTA algorithm selects the best carrier using factors like frequency priority, capacity threshold, and capacity estimates reported by each BTS. MCTA makes decisions either at the BTS or SBS depending on the network configuration.
The document defines and provides default values for several important WCDMA parameters used in change requests (CR) by engineers. It includes parameters for layer management (e.g. soft/hard handover types), cell selection/reselection (e.g. sInterSearch, sIntraSearch), triggered events, and their typical values. The purpose is to familiarize new engineers with the key parameters used in their daily work when creating CRs.
CSFB and eCSFB Overview and call flow desMani132076
Circuit switch fallback (CSFB) and enhanced CSFB (eCSFB) allow users with dual-mode devices to make voice calls on 1xRTT networks while camped on an LTE network. CSFB involves releasing the UE from LTE to CDMA for voice, while eCSFB uses handover coordination between the networks. The document discusses the architectures, parameters, and counters involved in CSFB and eCSFB, including prerequisites, signaling interfaces, broadcast parameters, timers, and troubleshooting steps.
Drive Test and Optimization Tutorial - I.pdfhamdi_saif
The document discusses drive testing procedures and measurements. It describes the required tools for drive testing including a laptop, GPS device, and test software. It outlines key radio parameters measured for 2G, 3G, and 4G networks including signal strength, quality, interference, and throughput. Examples of drive test activities are given such as new site acceptance tests involving calls, SMS, and internet usage to check coverage and quality.
Types Of Window Being Used For The Selected GranuleLeslie Lee
The document discusses different types of mode selective devices that can be used for mode multiplexing over few-mode fiber. Free-space based devices are bulky while fiber based devices are more compact and easier to integrate. Early demonstrations transmitted data over 107 Gb/s using the LP01 and LP11 fiber modes and 58.8 Gb/s using dual modes with electronic MIMO processing for mode separation. Mode selective devices can be categorized as either free-space based or fiber based, with fiber based being preferable due to their compact size and integration capabilities.
Physical design involves taking a synthesized netlist as input and performing floorplanning, placement, and routing to produce a physical layout. Key inputs include the netlist, timing constraints, physical libraries, and technology files. The process involves floor planning to determine block placement and routing areas, power planning to create the power distribution network, and pre-routing of standard cells and power grids. The goal is to meet timing constraints while minimizing area.
ATM is a cell switching and multiplexing technology designed to unify telecommunication network infrastructures. It uses fixed length cells to transport data and signaling information. ATM networks support connections with different quality of service (QoS) levels for various media like voice, video, and data. ATM allows for predictable delivery of real-time media through constant bit rate connections while also supporting bursty data traffic.
The PDF contains one of the six parts to learn Verilog in the simplest possible way.
It contains notes of first three chapters of the reference book Verilog HDL by Samir Palnitkar
After installing the TEMS software and opening the data collection window, the document discusses setting up a workspace to save drive test windows and make future tests less tedious. It then covers opening various windows needed for a 3G drive test like the serving cell information, neighbors, radio parameters, layer 3 messages, and throughput charts. Key aspects of each window are defined, such as what the active set, cell ID, scrambling code, and other parameters represent. Finally, it briefly touches on hard and soft handovers between frequencies and nodes.
After installing the TEMS software and opening the data collection window, the document discusses setting up a workspace to save drive test windows and make future tests less tedious. It then covers opening various windows needed for a 3G drive test like the serving cell information, neighbors, radio parameters, layer 3 messages, and throughput charts. Key aspects of each window are defined, such as what the active set, cell ID, scrambling code, and other parameters represent. Finally, it briefly touches on hard and soft handovers between frequencies and nodes.
This document provides an overview of CDMA (Code Division Multiple Access), including its access schemes, coding, codes, spreading process, power control, handover, multipath and rake receivers. It describes how CDMA uses unique spreading codes to spread data before transmission. Receivers use correlators to despread the signal and filters to isolate the desired signal from interference. Power control is important to limit interference in this interference-limited system. Soft handovers allow connections between multiple cells. Multipath signals are combined using rake receivers to strengthen the signal.
The demand for portable electronic devices that offers increase in functions, performance at lower costs and smaller sizes increased rapidly. Designing complex SOCs is a challenge, especially at 90 nanometers Technology, where new problems crop up - power efficiency is being the biggest of problems. For different modes we cannot design different operating circuits, better to have technique that will have minimum circuit changes and in all modes it will save power which is wasted. This paper provides some guidelines on how Low Power design using UPF approach can be introduced for a design.
The document discusses drive testing using TEMS Investigation software. It provides an overview of the tools needed for drive testing including a laptop, dongle, mobile set, modem, GPS, and more. It outlines the steps to setup the software and ensure all tools are connected and functioning properly. These include attaching the required devices, loading cell files, and selecting the log collection location. The document also describes some key parameters that can be analyzed during drive testing like signal strength, interference, and throughput.
The document discusses drive testing using TEMS Investigation software. It provides an overview of the tools needed for drive testing including a laptop, dongle, mobile set, modem, GPS, and more. It outlines the steps to setup the software and ensure all tools are connected and functioning properly. These include attaching the required devices, loading cell files, and selecting the log collection location. The document also describes some key parameters that can be analyzed during drive testing like signal strength, interference, and throughput.
A wireless local area network (WLAN) uses radio frequency technology to transmit and receive data over the air, providing mobility and flexibility as an extension or alternative to wired networks. Key advantages of WLANs include productivity, convenience, lower installation costs and mobility. However, WLANs also have disadvantages such as higher costs for wireless network cards and access points, susceptibility to environmental interference, and lower bandwidth capacity compared to wired networks. Common applications of WLANs include use in corporate, education, medical and temporary settings.
- The document analyzes the effect of varying antenna gain and sectorization on site requirements for an LTE radio access network.
- It models three site layouts: single omni-directional antenna sites, 3-sector sites with directional antennas per sector, and 6-sector sites.
- Link budget calculations are performed for different clutter types to estimate the number of sites needed to cover the deployment area under each configuration.
What is Handoff in mobile network?
What is the Search Window?
How to optimize handoff parameters?
Upon completion of this course, you will be able to:
Know handoff principle and classification.
Know search window and key parameters.
Master handoff tuning in network.
Chapter 1 Basic Concept
Chapter 2 Handoff in CDMA
Chapter 3 Optimization Command
Chapter 4 Summary
Soft handoff
It is a process of establishing a link with a target sector before breaking the link with the serving sector.
Softer handoff
Similar to the soft handoff, but the softer handoff is occurred among multi-sectors in the same base station.
Hard handoff
Hard handoff occurs when the two sectors are not synchronized or are not on the same frequency. Interruption in voice or data communication occurs but this interruption does not effect the user communication.
CDMA soft handoff is driven by the handset
Handset continuously checks available pilots
Handset tells system pilots it currently sees
System assigns sectors (up to 6 max.), tells handset
Handset assigns its fingers accordingly
All messages sent by dim-and-burst, no muting!
Each end of the link chooses what works best, on a frame-by-frame basis!
Users are totally unaware of handoff
Welcome to International Journal of Engineering Research and Development (IJERD)IJERD Editor
call for paper 2012, hard copy of journal, research paper publishing, where to publish research paper,
journal publishing, how to publish research paper, Call For research paper, international journal, publishing a paper, IJERD, journal of science and technology, how to get a research paper published, publishing a paper, publishing of journal, publishing of research paper, reserach and review articles, IJERD Journal, How to publish your research paper, publish research paper, open access engineering journal, Engineering journal, Mathemetics journal, Physics journal, Chemistry journal, Computer Engineering, Computer Science journal, how to submit your paper, peer reviw journal, indexed journal, reserach and review articles, engineering journal, www.ijerd.com, research journals
The document discusses various parameters that are important to monitor during drive testing of a mobile network. It provides definitions and explanations of parameters in the "Current Channel", "Radio Parameters", and "Serving + Neighbor" windows that are analyzed during drive testing to evaluate network performance and quality. Key parameters include signal strength, interference levels, error rates, cell identifiers, frequencies, and more. Understanding these parameters is crucial for effectively analyzing network operation and identifying areas for improvement.
lte-enodeb-s1-startup-sib-rrc-connection.pdfJunaid Alam
The document summarizes the sequence of events for an eNodeB performing an S1 setup with the EPC and then initiating broadcasts of system information blocks (SIBs) to UEs. It shows the eNodeB sending the RRC Connection Setup message containing UE specific configuration information. The eNodeB first establishes an S1 connection with the MME and then broadcasts the master information block and various SIBs. It then facilitates the random access procedure and sends the RRC Connection Setup message to the UE.
This document provides instructions for configuring IEC 61850, GOOSE, FTP, and HTTP communication for Easergy P3 devices. It describes setting the main IEC 61850 configuration parameters such as IED name, logical nodes, data sets, and redundancy protocol. It also explains how to configure GOOSE publishing and subscribing, as well as file transfer using FTP. The document contains step-by-step examples for common configuration tasks.
This document discusses an LTE cell planning support tool called CELPLA L that was developed by NTT DOCOMO to help optimize the design of cell planning parameters for their LTE network. The tool automatically designs optimal values for key parameters like Physical Cell ID (PCI), Random Access Channel (RACH) Root Sequence (RRS), and Neighbor Relation Table (NRT). It does this through a three step process of inputting base station information, calculating the parameters, and outputting the results. The document focuses on how CELPLA L designs PCI and RACH parameters in particular. It groups sectors and assigns identifiers like local ID, cell-group ID, and hopping pattern to help determine PCI values
Performance Improvement of IEEE 802.22 WRAN Physical LayerIOSR Journals
The spectrum available for the wireless services is limited, the increased demand of wireless
application has put a lot of limitations on the utilization of available radio spectrum. For the efficient spectrum
utilization for wireless application IEEE 802.22 standard i.e. WRAN (Wireless Regional Area Network) is
developed which is based on cognitive radio technique that senses the free available spectrum. It allows sharing
of geographically unused channels allocated to the TV Broadcast Service, without interference.
In this paper we are evaluating the performance of WRAN over physical layer with QPSK, 16-QAM
and 64-QAM modulation with Convolution coding with code rate of 1/2, 2/3, 3/4, 5/6 and obtaining the BER
curves for rician channel. Simulation is performed in MATLAB
Performance Improvement of IEEE 802.22 WRAN Physical LayerIOSR Journals
Abstract: The spectrum available for the wireless services is limited, the increased demand of wireless application has put a lot of limitations on the utilization of available radio spectrum. For the efficient spectrum utilization for wireless application IEEE 802.22 standard i.e. WRAN (Wireless Regional Area Network) is developed which is based on cognitive radio technique that senses the free available spectrum. It allows sharing of geographically unused channels allocated to the TV Broadcast Service, without interference. In this paper we are evaluating the performance of WRAN over physical layer with QPSK, 16-QAM and 64-QAM modulation with Convolution coding with code rate of 1/2, 2/3, 3/4, 5/6 and obtaining the BER curves for rician channel. Simulation is performed in MATLAB. Keywords - CC, CP, CR, OFDMA, PHY Layer, WRAN
Performance Improvement of IEEE 802.22 WRAN Physical LayerIOSR Journals
Abstract: The spectrum available for the wireless services is limited, the increased demand of wireless
application has put a lot of limitations on the utilization of available radio spectrum. For the efficient spectrum
utilization for wireless application IEEE 802.22 standard i.e. WRAN (Wireless Regional Area Network) is
developed which is based on cognitive radio technique that senses the free available spectrum. It allows sharing
of geographically unused channels allocated to the TV Broadcast Service, without interference.
In this paper we are evaluating the performance of WRAN over physical layer with QPSK, 16-QAM
and 64-QAM modulation with Convolution coding with code rate of 1/2, 2/3, 3/4, 5/6 and obtaining the BER
curves for rician channel. Simulation is performed in MATLAB.
Keywords - CC, CP, CR, OFDMA, PHY Layer, WRAN
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
The PDF contains one of the six parts to learn Verilog in the simplest possible way.
It contains notes of first three chapters of the reference book Verilog HDL by Samir Palnitkar
After installing the TEMS software and opening the data collection window, the document discusses setting up a workspace to save drive test windows and make future tests less tedious. It then covers opening various windows needed for a 3G drive test like the serving cell information, neighbors, radio parameters, layer 3 messages, and throughput charts. Key aspects of each window are defined, such as what the active set, cell ID, scrambling code, and other parameters represent. Finally, it briefly touches on hard and soft handovers between frequencies and nodes.
After installing the TEMS software and opening the data collection window, the document discusses setting up a workspace to save drive test windows and make future tests less tedious. It then covers opening various windows needed for a 3G drive test like the serving cell information, neighbors, radio parameters, layer 3 messages, and throughput charts. Key aspects of each window are defined, such as what the active set, cell ID, scrambling code, and other parameters represent. Finally, it briefly touches on hard and soft handovers between frequencies and nodes.
This document provides an overview of CDMA (Code Division Multiple Access), including its access schemes, coding, codes, spreading process, power control, handover, multipath and rake receivers. It describes how CDMA uses unique spreading codes to spread data before transmission. Receivers use correlators to despread the signal and filters to isolate the desired signal from interference. Power control is important to limit interference in this interference-limited system. Soft handovers allow connections between multiple cells. Multipath signals are combined using rake receivers to strengthen the signal.
The demand for portable electronic devices that offers increase in functions, performance at lower costs and smaller sizes increased rapidly. Designing complex SOCs is a challenge, especially at 90 nanometers Technology, where new problems crop up - power efficiency is being the biggest of problems. For different modes we cannot design different operating circuits, better to have technique that will have minimum circuit changes and in all modes it will save power which is wasted. This paper provides some guidelines on how Low Power design using UPF approach can be introduced for a design.
The document discusses drive testing using TEMS Investigation software. It provides an overview of the tools needed for drive testing including a laptop, dongle, mobile set, modem, GPS, and more. It outlines the steps to setup the software and ensure all tools are connected and functioning properly. These include attaching the required devices, loading cell files, and selecting the log collection location. The document also describes some key parameters that can be analyzed during drive testing like signal strength, interference, and throughput.
The document discusses drive testing using TEMS Investigation software. It provides an overview of the tools needed for drive testing including a laptop, dongle, mobile set, modem, GPS, and more. It outlines the steps to setup the software and ensure all tools are connected and functioning properly. These include attaching the required devices, loading cell files, and selecting the log collection location. The document also describes some key parameters that can be analyzed during drive testing like signal strength, interference, and throughput.
A wireless local area network (WLAN) uses radio frequency technology to transmit and receive data over the air, providing mobility and flexibility as an extension or alternative to wired networks. Key advantages of WLANs include productivity, convenience, lower installation costs and mobility. However, WLANs also have disadvantages such as higher costs for wireless network cards and access points, susceptibility to environmental interference, and lower bandwidth capacity compared to wired networks. Common applications of WLANs include use in corporate, education, medical and temporary settings.
- The document analyzes the effect of varying antenna gain and sectorization on site requirements for an LTE radio access network.
- It models three site layouts: single omni-directional antenna sites, 3-sector sites with directional antennas per sector, and 6-sector sites.
- Link budget calculations are performed for different clutter types to estimate the number of sites needed to cover the deployment area under each configuration.
What is Handoff in mobile network?
What is the Search Window?
How to optimize handoff parameters?
Upon completion of this course, you will be able to:
Know handoff principle and classification.
Know search window and key parameters.
Master handoff tuning in network.
Chapter 1 Basic Concept
Chapter 2 Handoff in CDMA
Chapter 3 Optimization Command
Chapter 4 Summary
Soft handoff
It is a process of establishing a link with a target sector before breaking the link with the serving sector.
Softer handoff
Similar to the soft handoff, but the softer handoff is occurred among multi-sectors in the same base station.
Hard handoff
Hard handoff occurs when the two sectors are not synchronized or are not on the same frequency. Interruption in voice or data communication occurs but this interruption does not effect the user communication.
CDMA soft handoff is driven by the handset
Handset continuously checks available pilots
Handset tells system pilots it currently sees
System assigns sectors (up to 6 max.), tells handset
Handset assigns its fingers accordingly
All messages sent by dim-and-burst, no muting!
Each end of the link chooses what works best, on a frame-by-frame basis!
Users are totally unaware of handoff
Welcome to International Journal of Engineering Research and Development (IJERD)IJERD Editor
call for paper 2012, hard copy of journal, research paper publishing, where to publish research paper,
journal publishing, how to publish research paper, Call For research paper, international journal, publishing a paper, IJERD, journal of science and technology, how to get a research paper published, publishing a paper, publishing of journal, publishing of research paper, reserach and review articles, IJERD Journal, How to publish your research paper, publish research paper, open access engineering journal, Engineering journal, Mathemetics journal, Physics journal, Chemistry journal, Computer Engineering, Computer Science journal, how to submit your paper, peer reviw journal, indexed journal, reserach and review articles, engineering journal, www.ijerd.com, research journals
The document discusses various parameters that are important to monitor during drive testing of a mobile network. It provides definitions and explanations of parameters in the "Current Channel", "Radio Parameters", and "Serving + Neighbor" windows that are analyzed during drive testing to evaluate network performance and quality. Key parameters include signal strength, interference levels, error rates, cell identifiers, frequencies, and more. Understanding these parameters is crucial for effectively analyzing network operation and identifying areas for improvement.
lte-enodeb-s1-startup-sib-rrc-connection.pdfJunaid Alam
The document summarizes the sequence of events for an eNodeB performing an S1 setup with the EPC and then initiating broadcasts of system information blocks (SIBs) to UEs. It shows the eNodeB sending the RRC Connection Setup message containing UE specific configuration information. The eNodeB first establishes an S1 connection with the MME and then broadcasts the master information block and various SIBs. It then facilitates the random access procedure and sends the RRC Connection Setup message to the UE.
This document provides instructions for configuring IEC 61850, GOOSE, FTP, and HTTP communication for Easergy P3 devices. It describes setting the main IEC 61850 configuration parameters such as IED name, logical nodes, data sets, and redundancy protocol. It also explains how to configure GOOSE publishing and subscribing, as well as file transfer using FTP. The document contains step-by-step examples for common configuration tasks.
This document discusses an LTE cell planning support tool called CELPLA L that was developed by NTT DOCOMO to help optimize the design of cell planning parameters for their LTE network. The tool automatically designs optimal values for key parameters like Physical Cell ID (PCI), Random Access Channel (RACH) Root Sequence (RRS), and Neighbor Relation Table (NRT). It does this through a three step process of inputting base station information, calculating the parameters, and outputting the results. The document focuses on how CELPLA L designs PCI and RACH parameters in particular. It groups sectors and assigns identifiers like local ID, cell-group ID, and hopping pattern to help determine PCI values
Performance Improvement of IEEE 802.22 WRAN Physical LayerIOSR Journals
The spectrum available for the wireless services is limited, the increased demand of wireless
application has put a lot of limitations on the utilization of available radio spectrum. For the efficient spectrum
utilization for wireless application IEEE 802.22 standard i.e. WRAN (Wireless Regional Area Network) is
developed which is based on cognitive radio technique that senses the free available spectrum. It allows sharing
of geographically unused channels allocated to the TV Broadcast Service, without interference.
In this paper we are evaluating the performance of WRAN over physical layer with QPSK, 16-QAM
and 64-QAM modulation with Convolution coding with code rate of 1/2, 2/3, 3/4, 5/6 and obtaining the BER
curves for rician channel. Simulation is performed in MATLAB
Performance Improvement of IEEE 802.22 WRAN Physical LayerIOSR Journals
Abstract: The spectrum available for the wireless services is limited, the increased demand of wireless application has put a lot of limitations on the utilization of available radio spectrum. For the efficient spectrum utilization for wireless application IEEE 802.22 standard i.e. WRAN (Wireless Regional Area Network) is developed which is based on cognitive radio technique that senses the free available spectrum. It allows sharing of geographically unused channels allocated to the TV Broadcast Service, without interference. In this paper we are evaluating the performance of WRAN over physical layer with QPSK, 16-QAM and 64-QAM modulation with Convolution coding with code rate of 1/2, 2/3, 3/4, 5/6 and obtaining the BER curves for rician channel. Simulation is performed in MATLAB. Keywords - CC, CP, CR, OFDMA, PHY Layer, WRAN
Performance Improvement of IEEE 802.22 WRAN Physical LayerIOSR Journals
Abstract: The spectrum available for the wireless services is limited, the increased demand of wireless
application has put a lot of limitations on the utilization of available radio spectrum. For the efficient spectrum
utilization for wireless application IEEE 802.22 standard i.e. WRAN (Wireless Regional Area Network) is
developed which is based on cognitive radio technique that senses the free available spectrum. It allows sharing
of geographically unused channels allocated to the TV Broadcast Service, without interference.
In this paper we are evaluating the performance of WRAN over physical layer with QPSK, 16-QAM
and 64-QAM modulation with Convolution coding with code rate of 1/2, 2/3, 3/4, 5/6 and obtaining the BER
curves for rician channel. Simulation is performed in MATLAB.
Keywords - CC, CP, CR, OFDMA, PHY Layer, WRAN
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Dive into the realm of operating systems (OS) with Pravash Chandra Das, a seasoned Digital Forensic Analyst, as your guide. 🚀 This comprehensive presentation illuminates the core concepts, types, and evolution of OS, essential for understanding modern computing landscapes.
Beginning with the foundational definition, Das clarifies the pivotal role of OS as system software orchestrating hardware resources, software applications, and user interactions. Through succinct descriptions, he delineates the diverse types of OS, from single-user, single-task environments like early MS-DOS iterations, to multi-user, multi-tasking systems exemplified by modern Linux distributions.
Crucial components like the kernel and shell are dissected, highlighting their indispensable functions in resource management and user interface interaction. Das elucidates how the kernel acts as the central nervous system, orchestrating process scheduling, memory allocation, and device management. Meanwhile, the shell serves as the gateway for user commands, bridging the gap between human input and machine execution. 💻
The narrative then shifts to a captivating exploration of prominent desktop OSs, Windows, macOS, and Linux. Windows, with its globally ubiquitous presence and user-friendly interface, emerges as a cornerstone in personal computing history. macOS, lauded for its sleek design and seamless integration with Apple's ecosystem, stands as a beacon of stability and creativity. Linux, an open-source marvel, offers unparalleled flexibility and security, revolutionizing the computing landscape. 🖥️
Moving to the realm of mobile devices, Das unravels the dominance of Android and iOS. Android's open-source ethos fosters a vibrant ecosystem of customization and innovation, while iOS boasts a seamless user experience and robust security infrastructure. Meanwhile, discontinued platforms like Symbian and Palm OS evoke nostalgia for their pioneering roles in the smartphone revolution.
The journey concludes with a reflection on the ever-evolving landscape of OS, underscored by the emergence of real-time operating systems (RTOS) and the persistent quest for innovation and efficiency. As technology continues to shape our world, understanding the foundations and evolution of operating systems remains paramount. Join Pravash Chandra Das on this illuminating journey through the heart of computing. 🌟
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
1. Required CellRefs Fields
This topic provides a summary of the fields that must be present in the CellRefs file for Analyzer to work
correctly. There are some fields that are always required and others that are required for specific technologies
and solutions.
Required Fields: All Technologies and Solutions
Site-Level Fields
Sector-Level Fields
Additional Fields by Technology
Sector-Level Fields
GSM
In This Topic See Also
All Technologies and Solutions
Additional Fields by Technology
Additional Fields Used by Veritune
CellRefs Fields: CDMA
CellRefs Fields: EVDO
CellRefs Fields: GSM
CellRefs Fields: UMTS TDD (UTDD)
CellRefs Fields: WCDMA
Field Description
SiteID The ID of the site (base station).
Latitude The site's latitude expressed as a decimal number representing the degrees in the WGS 84
projection system.
Longitude The site's longitude expressed as a decimal number representing the degrees in the WGS 84
projection system.
Field Description
TECHNOLOGY_SiteIDForCell The ID of the site to which the sector belongs.
Sector_ID The ID of the cell or sector within the site.
Azimuth The sector's azimuth angle relative to true North, expressed in degrees. If
this field is missing or does not contain a sensible value, the sector will be
shown pointing due North on the map.
Beamwidth The sector's beam width angle expressed in degrees. Used to control the
size of the sector wedges on the map. If this field is missing or does not
contain a sensible value, the sector will be shown on the map as a narrow
line rather than a wedge.
Field Description
BCCH The base station control channel.
CI The cell identity code.
BSIC The base station identity code.
MCC The mobile country code. This is an optional field. However, in some networks the CI is
not sufficient to uniquely identify each cell. In these circumstances, the MCC is
required for the full cell global identity (CGI, which consists of the MCC, MNC, LAC, and
CI) that is necessary for the correct identification of each cell.
MNC The mobile network code. This is an optional field. However, if the CI is not sufficient
to uniquely identify each cell, the MNC is required (along with the MCC and LAC) for
the full CGI.
LAC The location area code. This is an optional field. However, if the CI is not sufficient to
uniquely identify each cell, the LAC is required (along with the MCC and MNC) for the
full CGI.
TCHList A list of traffic channels. This is required for the TCH Co/adjacent Channel feature in
Spotlight and the GSM Cell Plan Viewer.
NBorCI A list of neighbor cell IDs. This is required for the Neighbor List Analysis in Spotlight
and the GSM Cell Plan Viewer.
adjacentChannel This field is required by the GSM Cell Plan Viewer in versions of Analyzer earlier than
Spotlight. It is a special internal field that must be present as the last field for the GSM
cell network element in the .ini configuration file. However, the cellrefs file does not
need to store data for this field, because it is populated by the GSM Cell Plan Viewer.
This field is not required from the introduction of Spotlight onwards.
2. CDMA/EV-DO
UMTS
UMTS TDD (UTDD)
iDEN
IS 136/IS 54
Additional Fields Used by Veritune
The following table lists the additional sector-level fields used by Veritune. Except where stated otherwise,
these fields are required.
Field Description
PN The pseudo noise code for the sector.
Field Description
SC The sector's scrambling code.
WCDMANeighborList This is an array field is required only by the 3G missing neighbor analysis to store
the scrambling (SC) codes of the 3G neighbors. Although this field must be present
on the WCDMA_Cell network element, it does not need to store data, because the
3G missing neighbor analysis will automatically suggest neighbors. If this field does
store data, the analysis will suggest cells for removal when they do not meet the
defined criteria.
GSMNeighborList This is an array field that is required only by the 3G-2G missing neighbor analysis to
store the cell identity (CI) codes of the 2G neighbors. Note that these must match CI
codes of GSM sector elements within the CellRefs file.
Although this field must be present on the WCDMA_Cell network element, it does not
need to store data, because the 3G-2G missing neighbor analysis will automatically
suggest neighbors. If this field does store data, the analysis will suggest cells for
removal when they do not meet the defined criteria.
Field Description
Toffset The time offset for the sector.
UARFCN The UTRA absolute radio frequency channel number.
Field Description
CCCH Common control channel. Can be used to color the sector wedges.
Color_Codes A list of color codes (SAT and DVCCs) that match the entries in the Traffic_Channels field.
Used for determining likely serving and neighbor cells.
Field Description
Color_Codes A list of color codes (SAT and DVCCs) that match the entries in the Traffic_Channels field.
Used for determining likely serving and neighbor cells.
Technology Field Description
All Antenna_key A unique identifier for the antenna mask in use on the site. The
antenna mask identifies a specific electrical downtilt configuration
for a particular antenna type. This key must correspond to a key
in the antenna pattern database.
Height Height in meters of the base station antenna above ground level.
Tilt The tilt of the antenna measured in degrees. This is positive for
downtilt and negative for uptilt.
GSM EIRP This optional field stores outward power of the sector in dBm. If
this field is present, Veritune adjusts it when you enter a value in
the Relative Power box. If this field is not present, Veritune
adjusts the measured power value instead.
UMTS PA Power The maximum PA output power in dBm. Integer.
Pilot_Power The CPICH power in dBm. Integer.
Sync_Power The combined P-SCH and S_SCH power in dBm. Integer.
Other_Common_Powers The combined power for other common downlink channels in dBm.
Integer.
EV-DO CDMA_Freq This optional field indicates the frequency in MHz in multi-
frequency network configurations where PN varies with frequency.
3. Technology-Specific Information
CellRefs Fields: CDMA
CellRefs Fields: EVDO
CellRefs Fields: GSM
CellRefs Fields: UMTS TDD (UTDD)
CellRefs Fields: WCDMA
See Also
Structure of the CellRefs File
CellRefs Preferences
Veritune Preferences
Adding New Fields to the CellRefs File
Lines to Cells
CellRefs History
CellRefs Limits
Send feedback on this topic
If this field is absent, all frequencies are assumed. Integer.
EIRP This optional field stores outward power of the sector in dBm. If
this field is present, Veritune adjusts it when you enter a value in
the Relative Power box. If this field is not present, Veritune
adjusts the measured power value instead.
CDMA CDMA_Freq This optional field indicates the frequency in MHz in multi-
frequency network configurations where PN varies with frequency.
If this field is absent, all frequencies are assumed. Integer.
EIRP This optional field stores outward power of the sector in dBm. If
this field is present, Veritune adjusts it when you enter a value in
the Relative Power box. If this field is not present, Veritune
adjusts the measured power value instead.
PctPilot Percentage of power allocated to pilot channel. Integer.
PctTraffic Percentage of power allocated to traffic channels. Integer.
PctPaging Percentage of power allocated to paging channel. Integer.
PctSync Percentage of power allocated to synchronization channels.
Integer.
4. Structure of the CellRefs File
Contents
Introduction
The DefNetworkData.ini file
The CellRefs file
Introduction
Network configuration information (such as the names, IDs, and locations of the cell sites, etc.) is stored in a
text file that is called the CellRefs file. This topic provides information about the structure of this file and the
configuration file (called DefNetworkData.ini), which defines its structure and format. You set the location of
the CellRefs file in the Preferences dialog box. See CellRefs Preferences for more information.
The cellrefs file is a text file that stores information about actual physical network elements. The first line of the
file must be as follows:
; #NetworkData - datafile
Each subsequent line in the file stores information about an individual network element (such as a cell or site).
The information that is stored for each network element must correspond to the definition specified for that
type of network element in the DefNetworkData.ini file.
The DefNetworkData.ini file
The DefNetworkData.ini file is a configuration file that defines the structure and format of the information in the
CellRefs files. The default DefNetworkData.ini file is located in the Program FilesActixAnalyzerBin folder.
However, you can override the default file with a custom one—for example, if you want to store additional data
about the network elements. This is done by creating a custom configuration file with the same name as the
cellrefs file but with an .ini filename extension and placing it in the same folder as the cellrefs file. (For
example, if the cellrefs file is called cellrefs.txt, the custom configuration file must be called cellrefs.ini.) Note
that the default configuration file is totally ignored when a custom configuration file is present.
The DefNetworkData.ini file contains two key sections—[Network Elements] and [Fields] and one or more
additional sections defining the root object in the hierarchy of net elements for a technology. The default
DefNetworkData.ini file contains one of these elements, [GSM_MSC].
[Network Elements]. This section defines the different types of network element and the fields that are
stored for each one using the Network_Element_Name=Field1 Field2 Field3... syntax. For example:
[Network Elements]
CDMA_Site=Site_Name SiteID Latitude Longitude
CDMA_Cell=CDMA_SiteIDForCell Sector_ID Azimuth Beamwidth EIRP PN MCC SID NID BID PctPilot PctTraf
GSM_MSC=ID MSCName
GSM_BSC=ID MSCID BSCName
GSM_Site=Site_Name SiteID Latitude Longitude
GSM_Cell=GSM_SiteIDForCell Sector_ID Azimuth Beamwidth EIRP BCCH MCC MNC LAC CI BSIC BSCID Face_D
.
.
.
[Fields]. This section defines the properties of each field, including:
The format group (such as string, integer, degrees, or percentage) to be used for the data in the field.
Format groups specify the data type and control how the information is formatted (for example, when it is
displayed in the Map view). The format group can also be used to define valid values to be used to validate
the data when it is imported.
Whether the field is Required (must be present) or Key (must be present and unique).
Whether the field is an array field, which means that the field can contain a variable-length list of values
(such as a neighbor list). These fields are specified using the array keyword, as shown for the
CDMANeighborList field below.
If the field maps one network element to another, the related field is defined using the
Ref:NetworkElement:Field:RelationTypeToOther#RelationToMe syntax. RelationTypeToOther specifies
the relationship between the network element and the linked object (typical examples are Parent and
CellSite). RelationToMe specifies the reverse relationship (for example, Child and Cell).
In the snippet from the [Network Elements] section shown above, the CDMA_SiteIDForCell field has been
highlighted. Below is a snippet from the [Fields] section, in which the same field has been highlighted. Notice
that the Ref keyword has been used to specify that this field is linked to the SiteID field in the CDMA_Site
6. Technology-Specific Information
CellRefs Fields: CDMA
CellRefs Fields: EVDO
CellRefs Fields: GSM
CellRefs Fields: UMTS TDD (UTDD)
CellRefs Fields: WCDMA
Related Topics
CellRefs Preferences
Map Projections
Send feedback on this topic
7. CellRefs Preferences
The CellRefs settings in the Preferences dialog provide configuration options for the CellRefs file, which stores
information about the physical network.
Introduction
CellRefs preferences
Using the manual import feature to create an import template
CellRefs fields
Import file specification
Data validation
Introduction
When you first install the software, it is configured with an empty CellRefs file (called cellrefs.txt) located in the
BinCellRefs folder within the user data area.
CellRefs files must have a specific format (which is described in Structure of the CellRefs File) and must contain
specific fields. The fields that are required depend on the technology and solution you are using and are
described in Required CellRefs Fields.
If you already have an appropriately formatted CellRefs file containing your network data, you can simply
change the CellRefs File Location in the Preferences dialog to the name and location of your file. Otherwise,
you need to import your network data and save it as a CellRefs file.
Network data can come from a wide range of databases and systems, such as planning tools. Generally these
provide a mechanism for exporting the data in a delimited text format that is suitable for import. You can
configure the software so that it automatically imports the network data again whenever it has changed.
Alternatively you can import new network data manually when necessary or make small modifications in the
Network Explorer.
Note: Currently only one CellRefs file can be used at a time.
CellRefs preferences
If you change the CellRefs file and the new file relates to the same technology (or combination of technologies)
that you were using before, you no do not need to restart the application in order for the changes to take
effect. But if you change the CellRefs file after loading log files, you may see some unexpected results—for
example, when you use the Lines to Cells feature on the map with those log files. Therefore, after changing the
CellRefs file, you should generally close any log files that you loaded earlier, and if necessary, reload them.
However, you must restart the application if you change a new CellRefs file that relates to a different
technology or combination of technologies.
File Location. Specifies the name and location of the current CellRefs file. This can either be an existing valid
CellRefs file or a blank text file that starts with the following line and into which you will import your network
configuration data:
8. ; #NetworkData - datafile
Note that the file you specify here will be overwritten if you select an Enable Import Source option below or
manually import network configuration data in Network Explorer and save your changes.
Enable Association with Log Files. Select this option if you want the application to track which CellRefs file
is in use when you load a log file. A warning will then be displayed if you subsequently attempt to load the log
file using a different CellRefs file. This is useful if you tend to work with log files from different regions, which
require different CellRefs files. The default is deselected.
Automatic Import. This feature automatically imports network configuration data into the CellRefs file
specified above. This is useful when your network is updated frequently and means that whenever new network
configuration data becomes available, it automatically gets imported when the application starts up. You can
automatically import data from up to four different sources. This is useful if your network configuration data
comes from more than one database—for example, if your GSM configuration data comes from one database or
planning tool and your UMTS data from another.
However, automatic import is not suitable for use with Spotlight. If necessary you should use the automatic
import feature to import data from your planning tools prior to setting up your Spotlight project. Then before
you create the Spotlight project, save the cellrefs file into which the data has been imported to another location
and deselect the Enable Import Source options.
Note that the imported information will be written to the CellRefs file specified in the File Location option
above.
For each source, the options are:
Enable Import Source. Select this option to enable the automatic import from this source. The default is
deselected.
Automatic Import Input File. Specifies the delimited text file containing the network configuration data to
be imported. See Import file specification below for more information. Typically you would do a manual
import before starting to use the automatic import in order to ensure that the file and template (see next
option) are set up correctly.
The data in this file will be imported and saved to the CellRefs file specified above whenever you start up
the application after any of the following:
„ You have changed the automatic import input file.
„ You have changed the automatic import template.
„ A new version of the automatic import file has become available (that is, the date and time stamp on the
file has changed).
For performance reasons, it is recommended that you work with moderate amounts of network data focused
on a particular region and create an archive folder structure to store these files. (See CellRefs Limits for
more information.) For example, here is a Network Data Archive folder in Windows Explorer.
Notice that subfolders are used to separate the files used for manual and automatic imports. The files in the
Automatic folder are overwritten every day, in order to ensure that users always import the latest network
data. Generally, each engineer will work with data from a single region and so will not need to change his or
her settings after initially configuring them. The files in the Manual folder would typically have filenames
that include the date and would be kept for historical reference.
Automatic Import Template. Specifies the template to be used for the automatic network data import.
You can select one of the default templates that are provided for the various network technologies.
Alternatively, you can create your own template using the manual import feature as described below. Any
templates that have been saved in the BinCellRefsTempates folder within the user data area automatically
appear in the drop-down list.
9. Note: The network data is validated as it is imported and details of any errors are written to a log file,
described in Data validation below.
Using the manual import feature to create an import template
In order to import it, network information needs to be in the form of a text file in which a specified character
(typically the tab, space, or comma) is used to separate the various items of data and optionally the first row
provides the names of the columns. Most databases and planning tools can export data in a suitable format.
See Import file specification below for further information.
Here is an example of an input file in which the tab character has been used as the delimiter:
Technology Site Name Site ID Lat Long Sector ID AZIMUT Antenna 3db Hor EIRP
GSM 01A1 01A 32.89725 44.485166667 01A1 40 65 0 No
GSM 01A2 01A 32.89725 44.485166667 01A2 160 65 0 No
GSM 01A3 01A 32.89725 44.485166667 01A3 280 65 0 No
GSM 02B1 02B 32.80002778 44.354666667 02B1 70 65 0 No
GSM 02B2 02B 32.80002778 44.354666667 02B2 190 65 0 No
GSM 02B3 02B 32.80002778 44.354666667 02B3 310 65 0 No
Templates specify how the file is formatted (for example, which separators are being used) and map the
various columns in the text file to the fields that are defined for the CellRefs file. A number of sample templates
(which you can optionally modify) are supplied or you can set up your own.
You set up a new template and import the data using the import options in the Network Explorer.
Import From New Template. Use this option to create a new template and import data using your new
template.
Import Using Template. Use this option to import data using an existing template. You can choose
between the templates that are supplied and any that you have created yourself (provided they are located
in the templates folder described below). Also use this option if you want to modify an existing template.
To illustrate how it works, we will set up a new template for the demonstration import file shown above.
From the Cells menu, choose Network Explorer, to open the Network Explorer.
From the Open menu in the Network Explorer, choose Import From New Template. This opens the Select
Data File to Import dialog.
Select the delimited text file.
This opens the first page of the import wizard.
10. Enter a name for the template.
Notice that the first page of the wizard has options for entering the field delimiter, the separators used for
lists and decimal numbers, whether the first row contains headers, the latitude and longitude format and
the coordinate system that is used to record the locations. In this example we do not need to change any of
these options because the defaults are suitable for use with our example file.
The lower part of the page provides a preview of the data, showing the column names and the values they
contain. If your text file uses a different delimiter, you need to specify the correct delimiter in the upper
part of the page, in order for the data preview to be displayed correctly.
Click Next, to move to the second page of the wizard, which you use to associate the columns in the text
file with the CellRefs fields.
11. Notice that the top part of the page lists all of the items that are currently defined for the CellRefs file. In
this example we will ignore all of the items that are not relevant to our data.
In this example our data stores GSM site and sector information only, which correspond to the GSM_Site
and GSM_Cell items. These top-level items are called network elements.
Expand the GSM_Cell and GSM_Site network elements and, for each field, select the corresponding
column in the import file as shown in the following table. For fields for which we are not importing data,
select Ignore.
Network Element CellRefs Field Column Default Value
GSM_Cell Sector_ID Sector ID
Azimuth AZIMUT
Beamwidth Antenna 3db Hor
EIRP Ignore 0
BCCH BCCH
MCC MCC
MNC MNC
LAC LAC
CI CI
BSIC BSIC
Face_Display Ignore
Azimuth_Display Ignore
Phase_Display Ignore
RAC Ignore
LayerType Ignore
Height Ignore
Tilt Ignore
Antenna_key Ignore
TCHList Ignore
GSM_Site Site_Name Site Name
12. Notice that although our import file contains an EIRP column, it does not contain valid data, so we have
selected Ignore for this column and entered a default value of zero. This means that this field will be set to
zero for every row. For more information about the various types of fields and how to add new fields, see
CellRefs fields below.
When you have finished, click Finish.
This imports the data using our new template and saves the template in the BinCellRefsTempates folder
within the user data area. This means that the template will automatically appear in the list of templates for
both automatic and manual imports.
The network data is validated as it is imported and details of any errors are written to a log file. If any errors
occur, you need to open the log file and use the information it contains to track down the errors and correct
them, before attempting to import the data again. For more information. see Data validation below.
If the import is successful, the details are displayed in the Network Explorer. When you are satisfied that the
details are correct, click the Save button (circled in red below) to save the details in the CellRefs file specified
in the Preferences dialog.
CellRefs fields
This section provides information about setting the fields on the second page of the wizard.
Icons. These are used in the import wizard to indicate the various types of fields as shown in the following
table.
Defaults. If you enter a default value for a field that is linked to a column, the default value is used when
there is a gap in the input data. If you enter a default for a field that is set to Ignore, the default value is used
for every row.
CellRefs fields. The CellRefs fields are defined in the configuration file, as described in Structure of the
CellRefs File. Detailed information is available about the standard CellRefs fields for the following technologies:
CDMA
EVDO
SiteID Site ID
Latitude Lat
Longitude Long
Icon Type Description
Key The field must be linked to an import data column in which the value in every row is
unique. You cannot set key fields to Ignore.
Required You need to link this field with a column, in order for it to work properly. Although you
can create a template that ignores a required field, an error will be logged and some
features may not work correctly. For example, if you ignore the Beamwidth field and do
not enter a sensible default, cells will be shown on the map as narrow lines rather than
wedges.
Optional The field can be ignored safely.
13. GSM
UMTS TDD (UTDD)
WCDMA
For other technologies, see Required CellRefs Fields.
Adding new fields. Sometimes you may find that your network data contains items that are not defined as
fields in the configuration file. When this happens you can define new fields. See Adding New Fields to the
CellRefs File for more information. However, note that this can adversely affect performance. See CellRefs
Limits for more information.
Import file specification
The network data input file should be a tab-, space- or comma-separated file with one row of data per cell. A
heading row is optional. Latitude and longitude may be represented in any of the supported coordinate
systems.
The following table shows the minimum fields that are required for the various technologies.
Note there are some additional optional fields and others that are required for Veritune and some other Actix
solutions, see Required CellRefs Fields.
Some fields contain a list (also called an array) of values. Common examples are the Color_Codes and
optional CDMA neighbor list fields. If you want to import values into these fields, they must be in a single
column in the import file, with the individual values separated using a different character from that used for
separating the columns. Then you need to specify the separator being used on the first page of the import
wizard. For example, if the main items are separated using the tab character, you could separate the neighbor
list values using commas.
Data validation
The network data is validated as it is imported. This helps to ensure that the software works correctly. The
validity checks include:
Validating the fields against their definition in the configuration file.
Validating the values against the data type (integer, string, etc.) specified in the configuration file.
Checking that values are within an appropriate range—for example, the Mobile Network Code should
represent a real network. Valid values are defined in the format group specified for the field in the
configuration file.
For information about the configuration file, see Structure of the CellRefs File.
If any errors occur, details are written to a log file called ImportErrors.log in the BinCellRefs folder within the
user data area. Typically this is:
C:Documents and SettingsAll UsersApplication DataActixAnalyzerBinCellrefsImportErrors.log
To view the error log:
Open the file in Notepad.
Here is an example:
Actix Analyzer CellRefs Importer
Import File: C:TestDataGSMCellrefsExampleCellRefsImport.txt
Technology Columns
All SiteID
Latitude
Longitude
Sector_ID
Azimuth
Beamwidth
GSM BCCH
CI
BSIC
CDMA/EV-DO PN
UMTS SC
IS 136/IS 54 Color_Codes
iDEN CCCH
Color_Codes
14. Import Template: DemoTemplate
Time of template Definition: 27/06/1426 14:09:49
Import Errors.
Line 2 : GSM_Cell : Field EIRP. Failure to convert value "0 Not in use" to type an integer.
Line 3 : GSM_Cell : Field EIRP. Failure to convert value "0 Not in use" to type an integer.
Line 4 : GSM_Cell : Field EIRP. Failure to convert value "0 Not in use" to type an integer.
Line 5 : GSM_Cell : Field EIRP. Failure to convert value "0 Not in use" to type an integer.
Line 6 : GSM_Cell : Field EIRP. Failure to convert value "0 Not in use" to type an integer.
Line 7 : GSM_Cell : Field EIRP. Failure to convert value "0 Not in use" to type an integer.
Related Topics
Preferences
Structure of the CellRefs File
Required CellRefs Fields
Adding New Fields to the CellRefs File
CellRefs History
CellRefs Limits
Technology-Specific Information
CellRefs Fields: CDMA
CellRefs Fields: EVDO
CellRefs Fields: GSM
CellRefs Fields: UMTS TDD (UTDD)
CellRefs Fields: WCDMA
Send feedback on this topic
15. CellRefs Fields: CDMA
In Analyzer, network configuration information is stored in a text file called the CellRefs file. This topic
provides information about the standard fields that are used in the CellRefs file for CDMA. The structure of the
CellRefs file is defined in the CellRefs configuration file (DefNetworkData.ini). This topic provides information
about all of the CDMA fields that are defined in the default configuration file, plus an additional field that can
optionally be added for use by Spotlight. This field is marked with an asterisk (*) and needs to be manually
added as described in Adding New Fields to the CellRefs File.
See CellRefs Preferences for an introduction to the CellRefs file and information about setting it and importing
data into it.
CDMA site fields
CDMA sector fields
Field Required? Description
SiteID Always The ID of the site (base station).
Site_Name No A text description, which can optionally be displayed on the map.
Latitude Always The site's latitude expressed as a decimal number representing the degrees in the
WGS 84 projection system.
Longitude Always The site's longitude expressed as a decimal number representing the degrees in
the WGS 84 projection system.
Field Required? Description
CDMA_SiteIDForCell Always The ID of the site to which the sector belongs.
Sector_ID Always The ID of the cell or sector within the site.
Azimuth Always The sector's azimuth angle relative to true North, expressed in degrees.
Used to orient the sector wedges on the map. If this field is missing or
does not contain a sensible value, the sector will be shown pointing due
North on the map.
Beamwidth Always The sector's beam width angle expressed in degrees. Used to control the
size of the sector wedges on the map. If this field is missing or does not
contain a sensible value, the sectors will be shown on the map as
narrow lines rather than wedges.
EIRP No This optional field can be used to store the outward power of the sector
in dBm. If this is present, it is used by Veritune, which adjusts it when
you enter a value in the Relative Power box. If this field is not present,
Veritune adjusts the measured power value instead.
PN Always The sector's pseudo noise code.
MCC No The mobile country code.
SID No The system identity code.
NID No The network identity code.
BID No The broadcast identity code.
PctPilot Veritune The percentage of power allocated to the pilot channel. Integer.
Required for Veritune.
PctTraffic Veritune The percentage of power allocated to the traffic channels. Integer.
Required for Veritune.
PctPaging Veritune The percentage of power allocated to the paging channel. Integer.
Required for Veritune.
PctSync Veritune The percentage of power allocated to synchronization of channels.
Integer. Required for Veritune.
SRCH_WIN_A CDMA
Toolkit
The size of the search window in the active pilot set. Integer. Required
for Search Window Optimization in CDMA Toolkit.
SRCH_WIN_N CDMA
Toolkit
The size of the search window in the neighbor pilot set. Integer.
Required for Search Window Optimization in CDMA Toolkit.
CDMANeighborList Neighbor
List Analysis
This is an array field that is required by the CDMA missing neighbor
analysis to store the PN codes of the neighbors. Although this field must
be present, it does not need to store data, because the analysis will
automatically suggest neighbors. If this field does store data, the
analysis will suggest cells for removal when they do not meet the
defined criteria.
Face_Display No An integer value.
16. Technology-Specific Information
CellRefs Fields: EVDO
CellRefs Fields: GSM
CellRefs Fields: UMTS TDD (UTDD)
CellRefs Fields: WCDMA
Related Topics
CellRefs Preferences
Structure of the CellRefs File
Required CellRefs Fields
Adding New Fields to the CellRefs File
Lines to Cells
CellRefs Limits
Send feedback on this topic
Azimuth_Display No A value in degrees.
Phase_Display No An integer value.
LayerType No This field can be used to enter a text to group sectors on some user-
defined criteria. Typical examples are purpose (microcell, macrocell,
underlay, overlay) and status (Planned, Built, Integrated). When data is
displayed on the map, sectors are placed in separate layers according to
the value in this field. This means that you can use the Layer Control
dialog to hide sectors that have a particular status, for example.
Height Veritune Height in meters of the antenna above ground level. Required for
Veritune. Optional for Spotlight.
Tilt Veritune The mechanical tilt of the antenna measured in degrees. This is positive
for downtilt and negative for uptilt. Required for Veritune.
Antenna_key Veritune A unique identifier for the antenna mask in use on the site. The antenna
mask identifies a specific electrical downtilt configuration for a particular
antenna type. This key must correspond to a key in the antenna pattern
database. Required for Veritune. Optional for Spotlight.
CDMA_Freq No This optional field indicates the frequency in MHz in multi-frequency
network configurations where PN varies with frequency. If this field is
absent, all frequencies are assumed. Integer. Used by Veritune.
Channel No The channel number of the RF carrier frequency. Integer.
Max_ServerDist
* No This can be used to specify a threshold that indicates the maximum
distance in meters that the sector should serve. Spotlight considers
samples beyond this distance to be overshooting. If this is not present in
the CellRefs file, Spotlight uses the general SL_Overspill_Dist_Threshold
user-defined threshold instead.
* Indicates that this field must be added to the configuration file manually as described in Adding New Fields
to the CellRefs File.
17. CellRefs Fields: EVDO
In Analyzer, network configuration information is stored in a text file called the CellRefs file. This topic
provides information about the standard fields that are used in the CellRefs file for EVDO. The structure of the
CellRefs file is defined in the CellRefs configuration file (DefNetworkData.ini). This topic provides information
about all of the CDMA fields that are defined in the default configuration file, plus an additional field that can
optionally be added for use by Spotlight. This field is marked with an asterisk (*) and needs to be manually
added as described in Adding New Fields to the CellRefs File.
See CellRefs Preferences for an introduction to the CellRefs file and information about setting it and importing
data into it.
EVDO site fields
EVDO sector fields
Field Required? Description
SiteID Always The ID of the site (base station).
Site_Name No A text description, which can optionally be displayed on the map.
Latitude Always The site's latitude expressed as a decimal number representing the degrees in the
WGS 84 projection system.
Longitude Always The site's longitude expressed as a decimal number representing the degrees in
the WGS 84 projection system.
Field Required? Description
CDMA1xEVDO_SiteIDForCell Always The ID of the site to which the sector belongs.
Sector_ID Always The ID of the cell or sector within the site.
Azimuth Always The sector's azimuth angle relative to true North, expressed in
degrees. Used to orient the sector wedges on the map. If this
field is missing or does not contain a sensible value, the sector
will be shown pointing due North on the map.
Beamwidth Always The sector's beam width angle expressed in degrees. Used to
control the size of the sector wedges on the map. If this field is
missing or does not contain a sensible value, the sector will be
shown on the map as a narrow line rather than a wedge.
EIRP No This optional field can be used to store the outward power of the
sector in dBm. If this is present, it is used by Veritune, which
adjusts it when you enter a value in the Relative Power box. If
this field is not present, Veritune adjusts the measured power
value instead.
PN Always The sector's pseudo noise code.
MCC No The mobile country code.
SID No The system identity code.
NID No The network identity code.
BID No The broadcast identity code.
SRCH_WIN_A CDMA
Toolkit
The size of the search window in the active pilot set. Integer.
Required for Search Window Optimization in CDMA Toolkit.
SRCH_WIN_N CDMA
Toolkit
The size of the search window in the neighbor pilot set. Integer.
Required for Search Window Optimization in CDMA Toolkit.
CDMANeighborList Neighbor
List Analysis
This is an array field that is required by the CDMA missing
neighbor analysis to store the PN codes of the neighbors.
Although this field must be present, it does not need to store
data, because the analysis will automatically suggest neighbors.
If this field does store data, the analysis will suggest cells for
removal when they do not meet the defined criteria.
Face_Display No An integer value.
Azimuth_Display No A value in degrees.
Phase_Display No An integer value.
SubnetMask No The subnet identifier that corresponds to the sector. Integer.
Color_Code No The color code that corresponds to the sector. Integer.
LayerType No This field can be used to enter a text to group sectors on some
user-defined criteria. Typical examples are purpose (microcell,
18. Technology-Specific Information
CellRefs Fields: CDMA
CellRefs Fields: GSM
CellRefs Fields: UMTS TDD (UTDD)
CellRefs Fields: WCDMA
Related Topics
CellRefs Preferences
Structure of the CellRefs File
Required CellRefs Fields
Adding New Fields to the CellRefs File
Lines to Cells
CellRefs Limits
Send feedback on this topic
macrocell, underlay, overlay) and status (Planned, Built,
Integrated). When data is displayed on the map, sectors are
placed in separate layers according to the value in this field. This
means that you can use the Layer Control dialog to hide sectors
that have a particular status, for example.
Height Veritune Height in meters of the antenna above ground level. Required for
Veritune. Optional for Spotlight.
Tilt Veritune The mechanical tilt of the antenna measured in degrees. This is
positive for downtilt and negative for uptilt. Required for
Veritune.
Antenna_key Veritune A unique identifier for the antenna mask in use on the site. The
antenna mask identifies a specific electrical downtilt configuration
for a particular antenna type. This key must correspond to a key
in the antenna pattern database. Required for Veritune. Optional
for Spotlight.
CDMA_Freq No Indicates the frequency in MHz in multi-frequency network
configurations where PN varies with frequency. If this field is
absent, all frequencies are assumed. Integer. Used by Veritune.
Channel No The channel number of the RF carrier frequency. Integer.
Max_ServerDist
* No This can be used to specify a threshold that indicates the
maximum distance in meters that the sector should serve.
Spotlight considers samples beyond this distance to be
overshooting. If this is not present in the CellRefs file, Spotlight
uses the general SL_Overspill_Dist_Threshold user-defined
threshold instead.
* Indicates that this field must be added to the configuration file manually as described in Adding New Fields
to the CellRefs File.
19. CellRefs Fields: GSM
In Analyzer, network configuration information is stored in a text file called the CellRefs file. This topic
provides information about the standard fields that are used in the CellRefs file for GSM. The structure of the
CellRefs file is defined in the CellRefs configuration file (DefNetworkData.ini). This topic provides information
about all of the CDMA fields that are defined in the default configuration file, plus some additional fields that
can optionally be added for use by Spotlight and the GSM Cellplan Viewe. These fields are marked with an
asterisk (*) and need to be manually added as described in Adding New Fields to the CellRefs File.
See CellRefs Preferences for an introduction to the CellRefs file and information about setting it and importing
data into it.
The default CellRefs configuration can handle four levels of network infrastructure:
MSC. This corresponds to the Mobile services Switching Center. It is an optional level. However, it becomes
mandatory if the BSCID field is filled in at the sector level.
BSC. This corresponds to the Base Station Controller. It is an optional level. However, it becomes
mandatory if the BSCID field is filled in at the sector level.
Site. This is mandatory and describes the ID and location of the site.
Sector. This is also mandatory and describes sector-specific data such as Azimuth, Beamwidth, BCCH, CI,
and BSIC. If the optional BSCID field is filled in, there must be a corresponding BSC row describing the BSC
ID and MSC ID.
The main advantage of including the BSC and MSC definitions is that they can be used in the map legend,
allowing cells to be color-coded according to their BSC.
GSM MSC fields
GSM BSC fields
GSM site fields
GSM sector fields
Field Required? Description
ID Only if the BSCID field is filled in at the sector level. The ID of the MSC.
MSCName No A text description.
Field Required? Description
ID Only if the BSCID field is filled in at the sector level. The ID of the BSC.
MSCID Only if the BSCID field is filled in at the sector level. The ID of the MSC to which the BSC belongs.
BSCName No A text description.
Field Required? Description
SiteID Yes The ID of the site (base station).
Site_Name No A text description, which can optionally be displayed on the map.
Latitude Yes The site's latitude expressed as a decimal number representing the degrees in the
WGS 84 projection system.
Longitude Yes The site's longitude expressed as a decimal number representing the degrees in the
WGS 84 projection system.
Field Required? Description
GSM_SiteIDForCell Always The ID of the site to which the sector belongs.
Sector_ID Always The ID of the cell or sector within the site.
Azimuth Always The sector's azimuth angle relative to true North, expressed in
degrees. Used to orient the sector wedges on the map. If this field is
missing or does not contain a sensible value, the sector will be shown
pointing due North on the map.
Beamwidth Always The sector's beam width angle expressed in degrees. Used to control
the size of the sector wedges on the map. If this field is missing or
does not contain a sensible value, the sector will be shown on the map
as a narrow line rather than a wedge.
EIRP No This optional field can be used to store the outward power of the sector
in dBm. This is used as follows:
„ Veritune adjusts the value in this field (if it is present) when you
enter a value in the Relative Power box. If this field is not present,
20. Veritune adjusts the measured power value instead.
„ When this is present for a sector, Spotlight uses it instead of the
general SL_GSM_EIRP_Threshold user-defined threshold.
BCCH Always The base station control channel. This field must be present for the
lines to neighboring cells feature to work correctly on the map.
MCC Sometimes The mobile country code. This is an optional field. However, in some
networks the CI is not sufficient to uniquely identify each cell. In these
circumstances, the MCC is required for the full cell global identity (CGI,
which consists of the MCC, MNC, LAC, and CI) that is necessary for the
correct identification of each cell.
MNC Sometimes The mobile network code. This is an optional field. However, if the CI is
not sufficient to uniquely identify each cell, the MNC is required (along
with the MCC and LAC) for the full CGI.
LAC Sometimes The location area code. This is an optional field. However, if the CI is
not sufficient to uniquely identify each cell, the LAC is required (along
with the MCC and MNC) for the full CGI.
CI Always The cell identity code. This field must be present for the lines to serving
cells feature to work correctly on the map.
BSIC Always The base station identity code. This field must be present for the lines
to neighboring cells feature to work correctly on the map.
BSCID No ID of the base station controller. If this is filled in, the BSC and MSC
levels become mandatory and a BSC row with the same ID must exist.
GSMNeighborList GSM 2G
Missing
Neighbors
Analysis
This is an array field that is required only by the 2G missing neighbor
analysis to store the cell identity (CI) codes of the neighbors. Note that
these must match CI codes of GSM sector elements within the CellRefs
file.
Although this field must be present, it does not need to store data,
because the 2G missing neighbor analysis will automatically suggest
neighbors. If this field does store data, the analysis will suggest cells
for removal when they do not meet the defined criteria.
Face_Display No An integer value.
Azimuth_Display No A value in degrees.
Phase_Display No An integer value.
RAC No The routing area code.
LayerType No This field can be used to enter a text to group sectors on some user-
defined criteria. Typical examples are bands (900 MHz, 1800 MHz,
1900 MHz), purpose (microcell, macrocell, underlay, overlay) and
status (Planned, Built, Integrated). When data is displayed on the map,
sectors are placed in separate layers according to the value in this
field. This means that you can use the Layer Control dialog to hide
sectors that have a particular status, for example.
Height Veritune Height in meters of the antenna above ground level. Required for
Veritune. Optional for Spotlight.
Tilt Veritune The mechanical tilt of the antenna measured in degrees. This is positive
for downtilt and negative for uptilt. Required for Veritune.
Antenna_key Veritune A unique identifier for the antenna mask in use on the site. The
antenna mask identifies a specific electrical downtilt configuration for a
particular antenna type. This is required for Veritune and must
correspond to a key in the antenna pattern database. Optional for
Spotlight.
TCHList Cell
Visualization
A list of traffic channels. This is required for the TCH Co/adjacent
Channel feature in Spotlight and the GSM Cell Plan Viewer.
NBorCI
* Neighbor List
Analysis
A list of neighbor cell IDs. This is required for the Neighbor List Analysis
in Spotlight and the GSM Cell Plan Viewer.
BTS_Sens
* No This can be used to specify the BTS receiver sensitivity threshold for
individual sectors. If present, this is used in the Spotlight ULDL
pathloss difference calculation instead of the general
SL_GSM_BTS_Sens_Threshold user-defined threshold.
Ant_Gain
* No This can be used to specify the antenna gain threshold in dB for
individual sectors. If present, this is used in the Spotlight ULDL
pathloss difference calculation instead of the general
SL_GSM_Ant_Gain_Threshold user-defined threshold.
21. Technology-Specific Information
CellRefs Fields: CDMA
CellRefs Fields: EVDO
CellRefs Fields: UMTS TDD (UTDD)
CellRefs Fields: WCDMA
Related Topics
CellRefs Preferences
Structure of the CellRefs File
Required CellRefs Fields
Adding New Fields to the CellRefs File
Lines to Cells
CellRefs Limits
Send feedback on this topic
Max_ServerDist
* No This can be used to specify a threshold that indicates the maximum
distance in meters that the sector should serve. Spotlight considers
samples beyond that distance as overshooting. If present, this is not
present in the CellRefs file, Spotlight uses the general
SL_Overspill_Dist_Threshold user-defined threshold.
adjacentChannel No This field is required by the GSM Cell Plan Viewer in versions of
Analyzer earlier than Spotlight. It is a special internal field that must be
present as the last field for the GSM cell network element in the .ini
configuration file. However, the cellrefs file does not need to store data
for this field, because it is populated by the GSM Cell Plan Viewer. This
field is not required from the introduction of Spotlight onwards.
* Indicates that this field must be added to the configuration file manually as described in Adding New Fields
to the CellRefs File.
22. CellRefs Fields: UMTS TDD (UTDD)
In Analyzer, network configuration information is stored in a text file is called the CellRefs file. This topic
provides information about the standard fields that are used in the CellRefs file for UMTS TDD (sometimes
referred to as UTDD). The structure of the CellRefs file is defined in the CellRefs configuration file
(DefNetworkData.ini). This topic provides information about all of the CDMA fields that are defined in the
default configuration file.
See CellRefs Preferences for an introduction to the CellRefs file and information about setting it and importing
data into it.
UMTS-TDD is a mobile data network standard built upon the UMTS 3G cellular mobile phone standard, using
a TD-CDMA air interface and Time Division Duplexing to duplex spectrum between the up-link and down-
link. While a full mobile UMTS implementation, it is mainly used to provide Internet access in circumstances
similar to those where WiMAX might be used. UMTS-TDD is not directly compatible with UMTS: a device
designed to use one standard cannot, unless specifically designed to, work on the other, because of the
difference in air interface technologies and frequencies used.
UTDD site fields
UTDD sector fields
Technology-Specific Information
CellRefs Fields: CDMA
CellRefs Fields: EVDO
CellRefs Fields: GSM
CellRefs Fields: WCDMA
Related Topics
CellRefs Preferences
Structure of the CellRefs File
Required CellRefs Fields
Adding New Fields to the CellRefs File
Lines to Cells
CellRefs Limits
Send feedback on this topic
Field Required? Description
SiteID Always The ID of the site (base station).
Site_Name No A text description, which can optionally be displayed on the map.
Latitude Always The site's latitude expressed as a decimal number representing the degrees in the
WGS 84 projection system.
Longitude Always The site's longitude expressed as a decimal number representing the degrees in
the WGS 84 projection system.
Field Required? Description
UTDD_SiteIDForCell Always The ID of the site to which the sector belongs.
Sector_ID Always The ID of the cell or sector within the site.
Azimuth Always The sector's azimuth angle relative to true North, expressed in degrees.
Used to orient the sector wedges on the map. If this field is missing or
does not contain a sensible value, the sector will be shown pointing due
North on the map.
Beamwidth Always The sector's beam width angle expressed in degrees. Used to control the
size of the sector wedges on the map. If this field is missing or does not
contain a sensible value, the sector will be shown on the map as a narrow
line rather than a wedge.
EIRP No This optional field can be used to store the outward power of the sector in
dBm.
Toffset Always The time offset for the sector.
MCC No The mobile country code.
MNC No The mobile network code.
LAC No The location area code.
UTDD_CI No The UMTS TDD cell identity code.
UARFCN Always The UTRA absolute radio frequency channel number.
23. CellRefs Fields: WCDMA
In Analyzer, network configuration information is stored in a text file called the CellRefs file. This topic
provides information about the standard fields that are used in the CellRefs file for WCDMA (UMTS). The
structure of the CellRefs file is defined in the CellRefs configuration file (DefNetworkData.ini). This topic
provides information about all of the CDMA fields that are defined in the default configuration file, plus some
additional fields that can optionally be added for use by Spotlight. These fields are marked with an asterisk (*)
and need to be manually added as described in Adding New Fields to the CellRefs File.
See CellRefs Preferences for an introduction to the CellRefs file and information about setting it and importing
data into it.
WCDMA site fields
WCDMA sector fields
Field Required? Description
SiteID Always The ID of the site (base station).
Site_Name No A text description, which can optionally be displayed on the map.
Latitude Always The site's latitude expressed as a decimal number representing the degrees in the
WGS 84 projection system.
Longitude Always The site's longitude expressed as a decimal number representing the degrees in
the WGS 84 projection system.
Vendor No The name of the software vendor.
RNC No The name of the RNC.
Software No The version of the software.
Field Required? Description
WCDMA_SiteIDForCell Always The ID of the site to which the sector belongs.
Sector_ID Always The ID of the cell or sector within the site.
Azimuth Always The sector's azimuth angle relative to true North, expressed in
degrees. Used to orient the sector wedges on the map. If this field is
missing or does not contain a sensible value, the sector will be shown
pointing due North on the map.
Beamwidth Always The sector's beam width angle expressed in degrees. Used to control
the size of the sector wedges on the map. If this field is missing or
does not contain a sensible value, the sector will be shown on the map
as a narrow line rather than a wedge.
EIRP No This optional field can be used to store the outward power of the
sector in dBm. This is used as follows:
„ Veritune adjusts the value in this field (if it is present) when you
enter a value in the Relative Power box. If this field is not present,
Veritune adjusts the measured power value instead.
„ When this is present for a sector, Spotlight uses it instead of the
general SL_EIRP_Threshold user-defined threshold.
SC Always The sector's scrambling code.
MCC No The mobile country code.
MNC No The mobile network code.
LAC No The location area code.
WCDMA_CI No The WCDMA cell identity code.
WCDMANeighborList Neighbor
List Analysis
This is an array field that is required by the 3G missing neighbor
analysis to store the scrambling (SC) codes of the 3G neighbors.
Although this field must be present, it does not need to store data,
because the 3G missing neighbor analysis will automatically suggest
neighbors. If this field does store data, the analysis will suggest cells
for removal when they do not meet the defined criteria.
GSM_BSIC No The GSM base station identity code.
LayerType No This field can be used to enter a text to group sectors on some user-
defined criteria. Typical examples are whether HSDPA is enabled,
purpose (microcell, macrocell, underlay, overlay) and status (Planned,
Built, Integrated). When data is displayed on the map, sectors are
placed in separate layers according to the value in this field. This
means that you can use the Layer Control dialog to hide sectors that
24. Technology-Specific Information
CellRefs Fields: CDMA
CellRefs Fields: EVDO
CellRefs Fields: GSM
CellRefs Fields: UMTS TDD (UTDD)
Related Topics
CellRefs Preferences
Structure of the CellRefs File
Required CellRefs Fields
Adding New Fields to the CellRefs File
Lines to Cells
CellRefs Limits
Send feedback on this topic
have a particular status, for example.
GSMNeighborList 3G-2G
Neighbor
List Analysis
This is an array field that is required only by the 3G-2G missing
neighbor analysis to store the cell identity (CI) codes of the 2G
neighbors. Note that these must match CI codes of GSM sector
elements within the CellRefs file.
Although this field must be present, it does not need to store data,
because the 3G-2G missing neighbor analysis will automatically
suggest neighbors. If this field does store data, the analysis will
suggest cells for removal when they do not meet the defined criteria.
UARFCN Always The UTRA absolute radio frequency channel number.
Height Veritune Height in meters of the antenna above ground level. Required for
Veritune. Optional for Spotlight.
Tilt Veritune The mechanical tilt of the antenna measured in degrees. This is
positive for downtilt and negative for uptilt. Required for Veritune.
Antenna_key Veritune A unique identifier for the antenna mask in use on the site. The
antenna mask identifies a specific electrical downtilt configuration for a
particular antenna type. This key must correspond to a key in the
antenna pattern database. Required for Veritune. Optional for
Spotlight.
PA_Power Veritune The maximum PA output power in dBm. Integer. Required for
Veritune.
Pilot_Power Veritune The CPICH power in dBm. Integer. Required for Veritune.
Sync_Power Veritune The combined P-SCH and S_SCH power in dBm. Integer. Required for
Veritune.
Other_Common_Powers Veritune The combined power for other common downlink channels in dBm.
Integer. Required for Veritune.
LayerSize No An integer between 1 and 5 that indicates the size of the wedges on
the map relative to GSM sector wedges.
BTS_Sens
* No This can be used to specify the BTS receiver sensitivity threshold for
individual sectors. If present, this is used in the Spotlight ULDL
pathloss difference calculation instead of the general
SL_BTS_Sens_Threshold user-defined threshold.
Ant_Gain
* No This can be used to specify the antenna gain threshold in dB for
individual sectors. If present, this is used in the Spotlight ULDL
pathloss difference calculation instead of the general
SL_Ant_Gain_Threshold user-defined threshold.
Max_ServerDist
* No This can be used to specify a threshold that indicates the maximum
distance in meters that the sector should serve. Spotlight considers
samples beyond this distance to be overshooting. If this is not present
in the CellRefs file, Spotlight uses the general
SL_Overspill_Dist_Threshold user-defined threshold instead.
* Indicates that this field must be added to the configuration file manually as described in Adding New Fields
to the CellRefs File.