Satellite Interference! …SDA, Carrier ID, VSAT Statistics and Difficult Cases

Presented by Martin Coleman - Executive Director sIRG www.satirg.org

STOP Interference Now! (it’s a SIN!)

Satellite Interference!

…SDA, Carrier ID, VSAT Statistics and Difficult Cases

satellite Interference Reduction Group

are dealing with…

formerly



…background on IRG

The former Satellite Users Interference Reduction Group (SUIRG) was restructured in February 2011 and rebranded:

satellite Interference Reduction Group (IRG)…focused on Technology Solutions!

It will actively pursue interference reduction by promoting: Coordination with other industry organizations to address regulatory issues, and

ensure adoption of Carrier ID Investigation and development of new technologies and techniques Assist in the development of best operational practices, training and certification

programs for installers and users through the End User Initiative (EUI now part of IRG; was RFI-EUI)

Support & coordinate with GVF, WBU-ISOG, APSCC, SSPi, MilSatCom

Members total 32, including satellite operators and other organizations More input needed, to get new ideas, grow participation, expand industry-wide

implementation of interference mitigation initiatives.



What is Interference?…

Sustainability of space – two main aspects: Physical security (collision avoidance, debris mitigation) Electro Magnetic Interference (EMI) / Radio Frequency Interference (RFI)

Satellites are a shared resource (space, satellite, transponder) In-band RFI (RFI within the operating frequency range of the satellite)

Out-of-band (RFI from adjacent frequency bands from the satellite) Much higher power (e.g. terrestrial/mobile services) can affect the adjacent

very low power satellite signals

Frequency spectrum of a satellite transponder-Blue trace is the authorized user signals-Purple trace is authorized plus interference

Users must be:-On the right satellite-At the right frequency-At the right power



Greater number of satellites

Reduced orbital separation

Growth of small ground terminalsLow equipment cost; lower quality; lower marginsPoor installations and maintenanceLack of operational trainingFaulty equipmentSometimes intentional, but rare

Satellites in geosynchronous orbit – courtesy of Analytical Graphics, Inc.

What is the cause of RFI?...



Putting in to Perspective…



The SES Experience with RFI…



Satellite RFI: the big 4!

Problems:

1. Improper Installations

2. Sub-Standard Equipment

3. Unidentified Carriers

4. Insufficient Incident

Coordination

Solutions (Tools):Proactive …

Training & Certification

Type Approvals

Network Validation

Reactive …

Carrier ID/Geolocation

Data Sharing/SDA

Statistics/VSATs



…IRG Working Groups & how they fitSatellite Operators, Vendors, Users, Agencies, VARs, Interested Parties

GVF

EUI

IRG

Intentional Interferenc

e

VSAT Analysis

Carrier ID Video/SCP

C

SDA

Host for CID global

database

ITU

Regulatory &

Spectrum

VSAT WG

ETSI

DVB

Implementation of CID on

uplinks

National Regulatory Agencies Satellite Operators

Broad-casters

VSAT VendorsSatellite Operators

VARs

Create Standards

Create Specification

Data Sharing for Conj. Analysis and

RFI Mitigation

Define Regulations, Investigate Offenders

Best Practice

s

Training & Type Approvals Training &

Certification - SNG



Working Group remits…

CID…

1.Setting up Processes

2.2.ID Database CreationID Database Creation3.Moving forward with the new DVB Standard4.Work with Manufacturers5.CID Ready Logo6.Engage the Broadcaster/Uplinker

7.7.Better Spectrum Better Spectrum MonitoringMonitoring8.Start with SNG & NIT9.Guide/Advise FCC Part 25 & OFCOM

VSAT…

1.Assess all new Data

2.2.Assess Root CausesAssess Root Causes3.Study at “Closed-Loop” Techniques4.Study Tx Amplifier Technology – Remote Power Levelling5.Study Cross-Pol Error Detection6.Modernise Hub Controllers

7.7.Feed GVF VSAT Feed GVF VSAT Working GroupWorking Group8.Assist GVF with Training Programs

DIFFICULT CASES…

1.Better Geo-Location2.Predictive Methods3.Suppression

4.4.Data & RecordsData & Records

5.5.Set Standards for Set Standards for Monitoring, Data & Monitoring, Data & Recording ProcessesRecording Processes6.Formal Evidence7.Future Satellite Technology…

a) Electronic Beam Shaping

b) On-Board Geo



The EUI - now part of IRG (was RFI-EUI)…

BEST PRACTICES, DOCUMENTATION & TECHNOLOGY:

1. ITU Rec. GAP for Uplinking2. Developing GMP for proper Maintenance Procedures3. On-going Mitigation Techniques4. Collect and Log Data & Records5. Set Standards for Monitoring, Data & Recording Processes6. Better Geolocation7. Future Satellite Technology…

a) Electronic Beam Shapingb) On-Board Geolocation

TRAINING & CERTIFICATION:

1.With All Industry Groups Create Quality Interactive & Hands-on Testing for SNG Uplinkers2. Study “Closed-Loop” Techniques3. Follow X-Pol Error Detection4. Modernize Hub Controllers5. Co-ord with GVF VSAT WG 6. Assist GVF / IRG with Training Programs & future Developments7. Progress movement toward “Required Certification”



Events from IBC 2012 to Date…

1. APSCC - Seoul Sept 20122. HBO/SATCON - NY Nov 20123. InterBEE - Tokyo Nov 20124. IRG Conference - Dubai Nov 20125. WBU-ISOG - Geneva Nov 20126. MILSATCOM - London Nov 20127. PTC - Hawaii Jan 20138. CabSat - Dubai March 20139. Sat Show (SDA) - DC March 201310. MilSatCom – Abu Dhabi May 201311. WBU-ISOG - LA May 201312. GVF HTS - DC May 201313. CommunicAsia - Singapore June 201314. Secure World Foundation (SWF) – DC

June 2013 (Steve Smith)15. GVF Maritime – London June 2013

16. China Satellite (via Skype) - Beijing Sept 2013

17. IBC - Amsterdam Sept 201318. COMSYS VSAT Forum - Amsterdam Sept

201319. APSCC - Hong Kong - Sept 201320. IRG Conference - Rio Oct 201321. Space & Satellite Regulatory Colloquium

(Jones Day/SDA) - DC Oct 201322. MilSatCom - London Nov 201323. WBU-ISOG - Rio (via Skype) Nov 201324. SATCON - NY Nov 201325. ARABSAT Forum - Athens Dec 201326. GVF HTS - London Dec 201327. ESA - Amsterdam 201428. Sat Show - DC March 2014



Intentional Interference Events…

Meetings/Events with full IRG participation from our IRG Conference (Dubai) 18/19th November 2012

BBC World Service (London) 20th November 2012Eutelsat (Paris) 18th January 2013CabSat (Dubai) 12th March 2013Satellite Show (DC) 21st March 2013MilSatCom (Abu Dhabi) 8th May 2013ITU (Geneva) 10th June 2013ASBU (Tunis) 6th October 2013 Others not budgeted for but IRG has been asked to attend…ITU x2 - Fiji Oct 2013 & Bangkok Nov 2013



Regulatory/Type Approvals & Other Events…

OFCOM…London Feb, July & Dec 2013

Type Approvals/QA…London Inmarsat Dec 2012

SSPi...NY Nov 2012Washington DC March 2013London June 2013Amsterdam Sept 2013 (at IBC EUSatCom)



for more Working Group Information - Contact…

CID: Roger Franklin (Crystal Solutions)

Email: [email protected]

DIFFICULT CASES: Yaser Hassan (ArabSat)


VSAT: Thomas van den Driessche (Newtec)




for more Group Information - Contact…

sIRG: Exec Director: Martin Coleman


GVF: Secretary General: David Hartshorn


WBU-ISOG: http://www.worldbroadcastingunions.org/wbuarea/committees/isog.asp

EUI: Co-Chairs: Dick Tauber


Rich Wolf


(…for the Broadcaster perspective)

SDA Future Plans



SDA Current Participants

Multi-national, open to all space operators, in all orbital regimes24 contributing operators3 civil satellite operators



Space Data Center - Current Participation

3 civil satellite operators 23 participating operators 118 LEO/MEO satellites from 7 operators 241 GEO satellites from 18 operators



Space Data Association - Objectives for 2014

SDA Grow Membership Develop Government and Industry Relationships Develop Space Insurance Relationships Secure Access to Additional Data Sources

SDC Reduce Operating Costs and Improve Service Implement Data Sharing for RFI Mitigation Carrier ID Database Supports RFI initiative of other industry bodies (IRG,

EUI, GVF, WBU-ISOG)



SDA Future Consideration

Space Weather Improved data distribution & alerts Controlled sharing of proprietary data Improved modeling with feedback

Space insurance Secure preferred terms for SDA members based on

better management of risk



SDA Future Challenges

Data Sources SDA/SDC built on user data, including ‘future knowledge’ Full catalogue requires additional data:

Increase participation >>> 100% of satellite operators Access other data sources to fill gaps and verify existing

Increasing tracking capabilities/data is key

Funding SDA is funded solely by participants Funding levels limit future developments External funding could affect independence Fee-paying ‘added value’ service models considered




…Carrier ID


are dealing with…

formerly



DVB completed its work on CID February 28th 2013

http://www.dvb.org/technology/standards/a164_DVB-CID_Carrier-ID_spec.pdf

ETSI published the standard 29th May 2013!

ETSI TS 103 129http://www.etsi.org/deliver/etsi_ts/103100_103199/103129/01.01.01_60/ts_103129v010101p.pdf

The End of the Beginning!

DVB CID Update…



We have an ETSI Standard (May 2013) & NIT! 70% of all supplied Modulators are DVB CID ready now! 80% of all supplied Encoders are NIT CID ready now! SDA CID Database in production (ready for June 2014) Detection Systems available now! Eutelsat, Intelsat & SES putting CID Systems in place now! WBU-ISOG Resolutions created CID targets! (May 2013) ASBU Action Plan requires CID (Oct 2013) FCC require ALL SNG/Flyaway Broadcast Platforms to be

DVB CID compliant by 1st June 2016 Start CID rollout – 1st January 2015!

…so where are we?



So moving forward…

Based on these particular WBU-ISOG resolutions with the aim to start rollout by 2015:

1. By 1 January 2015: All new modulators purchased for video uplinking will contain CID meeting ETSI DVB-CID standard

2. To meet Resolution 1, all Uplinkers of SCPC and MCPC video and data, fixed and mobile, will include DVB-CID in all RFPs for new modulators

3. By 1 January 2018: All uplinkers shall use DVB-CID on their SCPC and MCPC video and data transmissions

Can we find out who has CID (NIT or DVB)? Who is requiring it? (Commercial/Military) What planning is being done?

How we can support…

Providing better information, how? Workshops, Events, Sessions?



Carrier ID is a unique identification code embedded on a transmitted carrier

This will be decoded by Satellite Operators to identify the uplinker of an interfering carrier

No customer information (location or contacts) need be included with the CID (although it may be optionally included). So privacy is ensured for the customer

Initially for DVB OU/SNG, video, data. Not VSAT TDMA Two formats:

CID-NIT (old spec, to be phased out, may be compatible with existing equipment, requires uplinker to program the NIT)

DVB-CID (new spec, robust in presence of overlapping interference, spread spectrum technology, minimal user action)

What is CID?



What are the benefits?

Considerable effort and time is required for Operators to identify and resolve interference

CID will help identify interfering carriers Not a magic solution for RFI, but a positive step that will help Benefits:

Rapidly identify interfering carriers Enable faster action to resolve interference Improved QoS for customers (especially those affected by

RFI)



How does DVB-CID work?

[Graphics courtesy of Newtec]

CID is transported in a spread spectrum carrier below the noise floor, under the main carrier

CID can be decoded even in presence of overlapping interfering carriers

DVB-CID carrier is at typically 27dB below the level of the main carrier

Degradation of the main carrier is <0.28dB



DVB CID standard relies on spread spectrum technology in modems/ modulators to embed CID in satellite transmissions

Optional Information – Added by end user

Carried in the Content ID table:

Latitude and longitude

Telephone numbers (up to 3)

User defined data fields (up to 7)

Mandatory Information – Fixed by the equipment manufacturer

64-bit DVB CID Global Unique Identifier: Derived from a 48 bit MAC address or a 48 bit Space Data Association (SDA) modulator identifierCID Format: A revision code anticipating possible changes in the revision number and possible content of the fields in the Content ID table

DVB CID Summary…



Implementation of standard by manufacturers

Some already implemented

70% by endof 2013

How best to encourage all to

implement?

Requirement for CID by end users in all new

purchases

What will encourage end users to require

it?

Finalize CID standard

Complete by June 1, 2013

Requirement for CID by

satellite operators in all

uplink transmissions

Target date: January 1, 2015

Completion of the CID standard is only the beginning…now the real work begins

Next Steps…



Sat Ops #1

CID (using NIT) - the Olympics - the Process (Manual)…

Each Satellite Operator (e.g. Intelsat, SES & Eutelsat) ensures the NIT contains the…– Manufacturer’s Code – Carrier ID # (Serial No/MAC Address –12 Characters max)Optional - Satellite Operator name and contact info in to the User Field

Sat Ops #2

This ensures Customer Data stays secure with the responsible Satellite Operator!

Geo Stationary satellite subjected to Interference

Satellite coverage on earth surface

LegitimateSignal

E.g. Sat Ops #1 detects & reports an Interfering Carrier Carrier ID extracted & examined (e.g. User Info = Sat Ops #2)…

Then manually, cooperation between Operators…

Sat Ops #2 contacted & provided with Carrier ID#...

Sat Ops #n

Sat Ops #2, using the reported Carrier ID#, determinesCustomer and contacts for corrective action!



Timeline

sIRG objective: To prove CID process, use CID for World Cup OU video, June 2014

Based on WBU-ISOG resolutions:1. By 1 January 2015: All new modulators purchased for video uplinking will

contain CID meeting ETSI DVB-CID standard2. To meet Resolution 1, all uplinkers of SCPC and MCPC video and data,

fixed and mobile, will include DVB-CID in all RFPs for new modulators3. By 1 January 2018: All uplinkers shall use DVB-CID on their SCPC and

MCPC video and data transmissions4. By 1 January 2018: All use of CID-NIT shall be phased out by this date5. By 1 January 2015: All Satellite Operators shall start the transition to use

CID that meets CID-NIT or DVB-CID standards (phasing out CID-NIT by 1 Jan 2018)

Based on new FCC Part 25 Rule (Digital ATIS): By 1 June 2016: All SNG video transmissions must use the DVB-CID

(ETSI) standard



Latest WBU-ISOG Resolutions…At the conclusion of the recent WBU-ISOG Forum (May 15-16, 2013) held at Fox Networks in Los Angeles, there was agreement to issue a resolution in support of the recently adopted Carrier ID standard issued by ETSI (European Telecommunications Standards Institute) – ETSI TS 103 129 v1.1.1 (2013 – 05). With this positive step forward by the industry to identify satellite transmissions of video content and as a means to mitigate harmful satellite interference, WBU-ISOG supports the following resolutions:

Exclusions and their DefinitionThe requirements for transmission of Carrier ID do not apply to MSS systems which automatically configure frequency, power level, polarization and transmit inhibit according to commands issued by a central control mechanism which is in the control of the satellite operator.

The ETSI (European Telecommunications Standards Institute) – ETSI TS 103 129 v1.1.1 (2013 – 05) standard does not address systems that use TDMA or other types of burst carriers, and as such, equipment or systems that use TDMA or burst carriers are excluded at present from these resolutions.

RESOLUTIONS:WBU-ISOG supports the requirement that, by no later than January 1, 2015, all new model modulators and codecs with integrated modulators purchased by end users for video uplinking contain a Carrier ID (CID) that meets the ETSI TS 103 129 standard issued May 29, 2013.

Based on Resolution #1 and with immediate effect, the WBU-ISOG supports the requirement that all uplinkers of SCPC and MCPC Video and Data, fixed and mobile systems shall include Carrier ID functionality in the required specifications of all current and future RFP’s (Request for Proposal) or RFQ’s (Request for Quote) issued to equipment manufacturers regarding the purchase of modulators and/or codecs with integrated modulators.

The WBU-ISOG supports the requirement that all satellite operators, by no later than January 1, 2015 start the transition to use Carrier ID that meets WBU-ISOG NIT or the ETSI standard for all SNG, DSNG and any other New Uplink transmission services.

The WBU-ISOG supports the requirement that all uplinkers by no later than January 1, 2018 shall ensure that Carrier ID is included for all their respective SCPC and MCPC Video and Data transmissions.

The WBU-ISOG supports the requirements that CID NIT shall be phased-out in preference to the ETSI standard by January 1, 2018.



Moving Forward with CID…

Use both NIT (ideal start for SNG) & migrate to DVB Standard…

Simple ID, simple fix! Operator-to-Operator

Automation - SDA) Use MAC Address only Secure ID-to-Operator Link Simple Trace: Carrier-to-

Operator Hold applicable Carrier Data

details - Operator only! Accuracy & Maintenance



Satellite Operator Tasks

Develop CID ops processes Key objective: minimize complexity and expense for users Decode ID during line-up/ routine monitoring, enter in carrier dbase

Specify inter-Operator (e.g. via global dbase) processes Develop global CID database (prototype June 2014, final in 2015) Implement CID decoding in monitoring systems (basic functionality

by June 2014, full functions for 2015) Need rollout plan. Large Operators have dozens of mon sites to equip

Promote CID to customers (uplinkers) Info to sales teams and customers, industry presentations

Implement CID at our own teleports (uplinks) Target 2015-2018 depending on modem capability and refresh cycle

Longer term automation plans Auto detection of CID and immediate checking of databases



CID Global Database

Carrier IDDatabase

CID Decoder

Payload Ops Center

Sat Operator ‘A’

CID Decoder

Payload Ops Center

Sat Operator ‘B’

1

2

3

4

5

1. Detect RF Interference2. Decode Carrier ID from interference3. Operator ‘A’ checks Carrier ID in global database, and finds

association of the CID with Operator ‘B’4. Database returns name and contacts for Operator ‘B’5. Operator ‘A’ calls Operator ‘B’ to request resolution of interference

SDA will develop and host a global database for Operators to associate a CID with the name of the Satellite Operator who is transmitting the carrier with that code

Allows an Operator who is affected by interference to quickly find the name of the Satellite Operator to contact, to investigate and resolve the interference



Carrier ID Process “Road Map” - way forward

Broadcasters/Users/Industry

sIRG

SatelliteOperators

...CID Process Im

plemented!

2015201320122011

1st January, 2015

Timeline… 2014




…VSAT


are dealing with…

formerly



Types of RFI and taking a look at VSATs…

To put it in perspective: The amount of capacity affected by RFI at any time, is very small

compared to the total capacity However, for an affected customer, it is harmful interference

Impact to industry: Poor quality of service; affects revenue; bad perception of satellites














…Difficult Cases


are dealing with…

formerly



Deliberate Jamming…

Abu Dhabi MilSatCom Intro for reference… “As satellite communication technology evolves and continuous to grow, satellite networks are increasingly subject to radio frequency interference from a variety of ground transmitters. In an interesting panel, regions SatCom users outline steps they undertake to eliminate interference and outlines measures they expect from operators, regulators and system providers that can help their efforts.”

Affects to the Broadcaster & Regulation…Jamming – Cover both Intentional and typical instances of InterferenceMention Short Wave issues (BBC World Service/VoA) (Something the BBC reminded me of at CabSat!)

ITU Perspectives of where we are regarding harmful Interference, Geneva meeting 10th June where IRG/GVF helped present a day forum to National Entities on this subject.

Note, previous Meetings/Events with full IRG participation…IRG Conference (Dubai) 18/19th November 2012BBC World Service (London) 20th November 2012Eutelsat (Paris) 18th January 2013CabSat (Dubai) 12th March 2013Satellite Show (DC) 21st March 2013MilSatCom (Abu Dhabi) 8th May 2013ITU (Geneva) 10th June 2013 (What happened?)



Jamming - continued…

Proactive Solutions/Prevention…An Audience reminder on Training, Installation, Certification & Quality Assurance/Type Approval Update on what is now available for SNG, how does Training help prevent – GVF Initiatives… Note, we can add as part of the discussion period about RFI-EUIs role General Access Procedures and SNG Training, using this & other tools to help prevent interference in the first place, etc. etc. Carrier ID…Carrier ID DVB Standard - Bring us up-to-date with the DVB/ETSI, leading what really must be done to get CID implemented, require it, customers to specify it, etc. (see other parts of this presentation)




Reactive Solution – Processes, Tools & Technology…Interference & Geo-Location

•Brief to intro Geolocation for the audience as the final approach when all other avenues have been exhausted…•New standards to be developed for Geolocation Data output (agreed at CabSat 2013 between SAT Corp, Siemens & Zodiac Aerospace) including ITU request to initialize development of a standard for all ITU submissions. ITU Template received by IRG, first draft Geolocation Output Data template in time for Geneva meeting, 10th June 2013; with a view to creating an ISO standard… •Thus improving evidence gathering! •Discussion on allowing more monitoring stations to submit Geolocation data, with that standard, to allow more evidence of any single threat for the ITU to put forward to any entity, national or otherwise, to ensure accurate, common format, independently registered sourced evidence to provide that compelling case!




Reactive Solution – Processes, Tools & Technology (continued)…Interference & Geo-Location

•Predictive Geolocation, using the politics to govern where the most likely target services & put a “watch” on those services.

•Suppression (more to come on this ready for Geneva & Communic Asia); smart receivers/filtering; Better Service/Frequency Planning Strategies…

Leading to issues raised at other events on Deliberate Jamming, Database for Difficult Interference Case Events – next 3 slides…



Database for Difficult Interference Case Events…

Creation of a database of all interference events – especially those caused Intentionally or by Piracy…

What Data would go into the Database?

1.Interference Received – satellite, transponder, start time, end time (when there is one)

2.Affected party – CID, geo-location of transmission, content, modulation parameters, company and contact

3.Interfering party – CID, geo-location of transmission, content (if any), modulation parameters (if any), company/contact (if known)

4.Spectrum details, Plots, Recordings, Log of Detection and Resolution Activity, etc.




So Questions that should be Answered are… a)What use would the Data be put to? (e.g. Space Data Association SDA)

b)Who are the expected Contributors?

c)How possible is it to ensure that the Data was correct and that it was not being distorted by false information?

d)Would everyone be happy for their Data to be used for whatever purpose required by the users or administrators of the system (We understand that it would be against the rules to use it for commercial ends, but what about political situation?)





the Thinking...

This database would be populated and corroborated only by satellite operators. The affected party, and possibly the interfering party, would provide details to the satellite operators so that the data entered by satellite operators are as accurate as possible. The data would be used for trend analysis – content that is jammed, jammers, etc. Offenders, along with collected evidence, could be turned over to the ITU, the UN, and the governments of the affected and interfering party to support political negotiations.

Anonymous (without company, contacts or specific geo-location) data might be made available to research teams, overseen by IRG/SDA, that can use the data to design filters and other methods that would render jamming attempts ineffective.





…Space Data Association


are dealing with…

formerly

Carrier ID Database Development

October 2013



What is the Carrier ID Database?

Centralized database for all satellite operators to use, at no charge, to store/search for Carrier Unique IDs

The database will associate Carrier unique IDs with the satellite operator whose satellite is transmitting the carrier with that unique ID

Allows satellite operator who is affected by interference, to quickly find out who is responsible for the interfering carrier

User account administration by sIRG and/or SDA (to be decided) The database will support the new DVB-CID specification, and the

previous NIT CID encoding (which will eventually be phased out)



Carrier ID Database Concept

Carrier IDDatabase

CID Decoder

Payload Ops Center

Sat Operator ‘A’

CID Decoder

Payload Ops Center

Sat Operator ‘B’

1

2

3

4

5

1. Detect RF Interference2. Decode Carrier ID from interference3. Operator ‘A’ checks Carrier ID in global database, and finds

association of the CID with Operator ‘B’4. Database returns name and contacts for Operator ‘B’5. Operator ‘A’ calls Operator ‘B’ to request resolution of interference



Status of the CID Database (CIDB)

SDA has approved hosting of the CIDB High level requirements are drafted Development of a prototype CIDB by AGI is in progress and will be

first demonstrated to satellite operators and industry at the sIRG Conference in Brazil, 16-18 Oct 2013

Feedback on the prototype will lead to more detailed definition of the requirements for development of a production database

Target timeframe for readiness of a production CIDB is early-2014 The SDA has a requirements team overseeing RFI/CID functional

development, and will work with sIRG CID WG



CIDB Top-Level Functions (1 of 3)

Centralized, global database, accessible by all satellite operators at no charge

Sufficient controls for user access and data security User administrators will be authorized by sIRG/SDA (TBD), and

user accounts will be controlled by operator company administrators CIDB will support the new DVB-CID specification and former DVB-

NIT format. (NIT usage to be phased out) The data fields in the DVB-CID and NIT specs will be supported in

the CIDB CIDB will have user GUI and also web services access




Basic CIDB search functions: Search for a CID unique identifier (meeting DVB-CID spec), and

obtain satellite operator associated with that CID If the CID appears on multiple satellites (e.g. an SNG service), all

operators will be listed Search for a NIT identifier (made up of equipment manufacturer

and serial number, in accordance with DVB-NIT spec), and obtain satellite operator associated with that identifier

Search for a satellite operator and obtain contact details Search for the name of a contact person and obtain the satellite

operator associated with that name and contact details




Basic CIDB edit functions: Satellite operators can edit their own contact information and

create CID records associated with their company CID records cannot be deleted. This will retain a history of a

CID (modem) Mandatory fields are Unique ID, and satellite operator. All other

data fields are optional An operator can create a CID record, even if that CID already

exists for another operator. This may be applicable for modems that are used on multiple satellites, such as SNG services

Records will be date/time stamped



CID Prototype Demo…



CID Prototype Demo (cont.)






























THANK YOU!


formerly

Documents

Satellite Interference! …SDA, Carrier ID, VSAT Statistics and Difficult Cases