Presentation is loading. Please wait.

Presentation is loading. Please wait.

Regional Radiocommunication Conference (RRC-06) 15 May - 16 June 2006, Geneva, Switzerland RRC-06 Planning Interface Miroslav Ćosić, Andrea Manara Radiocommunication.

Similar presentations


Presentation on theme: "Regional Radiocommunication Conference (RRC-06) 15 May - 16 June 2006, Geneva, Switzerland RRC-06 Planning Interface Miroslav Ćosić, Andrea Manara Radiocommunication."— Presentation transcript:

1 Regional Radiocommunication Conference (RRC-06) 15 May - 16 June 2006, Geneva, Switzerland RRC-06 Planning Interface Miroslav Ćosić, Andrea Manara Radiocommunication Bureau

2 RRC May – 16 June 2006 Geneva Switzerland Outline Introduction Input data Service areas/Coverage analysis General analysis/Compatibility status Synthesis results Tools Future improvements

3 RRC May – 16 June 2006 Geneva Switzerland RRC-06 Planning Interface GUI application for Windows PCs RAD based on Microsoft.NET Formerly known as RRC06 Display 2 Introduced during IPG1 (see document IPG-1/20-E)IPG-1/20-E Ongoing improvements in features and performance

4 RRC May – 16 June 2006 Geneva Switzerland Installation Windows 2000 or XP Min. 1 GHz processor MB RAM Latest version available at: RRC_output_display/rrc_display.zip or from the PCs in the CICG Cyber-Caf é (level -1) RRC_output_display/rrc_display.zip No need for administrator privileges (only one time for.NET framework install) In case of installation (or any other) problem, contact

5 RRC May – 16 June 2006 Geneva Switzerland Release Notes and Help Release notes are in 5 languages or from the Help->Release Notes menu item in the application itself Feature set evolves faster than the help can be updated and translated Help is available in the main Help menu and in the PE and AD tools

6 RRC May – 16 June 2006 Geneva Switzerland Features Input data Service areas/Coverage analysis Compatibility analysis/status/details Synthesis results/Coverage analysis Planning exercise tool Administrative declarations tool Future improvements

7 RRC May – 16 June 2006 Geneva Switzerland Auxiliary Features Exporting to HTML, CSV or Excel Exporting input data subset to MDB Printing of graphics Per-table column positions, widths and visible/hidden are remembered Per-table sorting by up to 5 criteria can be saved as preferences

8 RRC May – 16 June 2006 Geneva Switzerland Input Data –Viewing notices from MDB file –Viewing notices from online database –Subsets of input data Digital requirements Administrative declarations (if available) Analogue TV broadcasting assignments Other primary services assignments –Allotment area displayed on map

9 RRC May – 16 June 2006 Geneva Switzerland Selection of CNG Geo Areas

10 RRC May – 16 June 2006 Geneva Switzerland Types of Requirements There are 4 main types of standalone and linked requirements –Standalone allotment (DT2 or DS2) –Standalone assignment (DT1 or DS1) –Single Frequency Network (SFN) –Assignment linked to an allotment (not an SFN) (DT2+DT1 or DS2+DS1)

11 RRC May – 16 June 2006 Geneva Switzerland Linked Requirements - SFN To determine the service area and to investigate incompatibilities, SFNs can be subdivided into three types –SFN without assignments (SFN DT2/SFN DS2) –SFN without an allotment (SFN DT1/SFN DS1) –SFN with both an allotment and assignments (SFN DT2+DT1, SFN DS2+DS1)

12 RRC May – 16 June 2006 Geneva Switzerland Requirements Statistics - DP Requirements for PlanningNotice Type Type (No. of Parts)No. of SetsDT1/DS1DT2/DS2 DT2/DS2 standalone DT1/DS1 standalone SFN DT2/DS2 (1)5236- DT1/DS1 (>1) DT2 (1) + DT1(>1) or DS2 (1) + DS1(>1) DT2 (1) + DT1 (1) or DS2 (1) + DS1 (1) 633 Total per Notice Type Grand Total

13 RRC May – 16 June 2006 Geneva Switzerland Service Areas – SFN DT1

14 RRC May – 16 June 2006 Geneva Switzerland Input Data – Coverage Analysis Coverage analysis provides the answer to the question How many (linked) requirement s service areas cover a given point? Since synthesis and MIG analysis results are not used, Band III (linked) requirements are subdivided into DVB-T and T-DAB

15 RRC May – 16 June 2006 Geneva Switzerland Coverage Analysis DT2/DS2, DT2+DT1/DS2+DS1, SFN DT2/SFN DS2, SFN DT2+DT1/SFN DS2 +DS1: allotment area is total service area DT1/DS1, SFN DT1/SFN DS1: (combined) assignment service area is total service area Right-clicking in the map of coverage analysis display distinguishes among these 6 types and subtypes

16 RRC May – 16 June 2006 Geneva Switzerland Coverage Analysis – SFN DT1

17 RRC May – 16 June 2006 Geneva Switzerland Compatibility Analysis Starting points: –Input data summary table or SFN parts list (new menu item available on right-click) –Compatibility status –Channel distribution statistics (if synthesis results are available) –General analysis per requirement General Analysis display for a particular requirement under investigation

18 RRC May – 16 June 2006 Geneva Switzerland Compatibility Status Lists all incompatibilities within one administration or between two adms 5 types of incompatibility: –Digital-to-Digital (d2d) –Analogue TV-to-Digital (a2d) –Digital-to-Analogue TV (d2a) –Other Services-to-Digital (o2d) –Digital-to-Other Services (d2o)

19 RRC May – 16 June 2006 Geneva Switzerland Compatibility Status - Usability Sorting and hiding columns may be used to better manage the amount of data displayed Right-click to access input data details or general analysis results Convenient way to generate additional admin declarations Draft Plan Case 1: > 6,7 M incompatibilities

20 RRC May – 16 June 2006 Geneva Switzerland Compatibility Status - Hints To get the full status of Case 1 self- incompatibilities, do the 5 queries, for each band (i.e. total 10 queries) To get the status of compatibility with another adm, do the 10 queries for B to A (i.e. administration A is submitting/affected) and then another 10 for A to B (i.e. 20 in all)

21 RRC May – 16 June 2006 Geneva Switzerland Channel Distribution Statistics Quick access to lists of requirements which did not get a channel assigned Future improvements –Distinguish between requirements with no assigned channel and those with no available channel, in a new column –Improve support for different types of linked sets of requirements

22 RRC May – 16 June 2006 Geneva Switzerland General Analysis All direct incompatibilities for a requirement at a glance Easy access to input data and general analysis results of others Improved support for linked sets Convenient way to generate new Digital-to-Digital admin declarations for one requirement (other types TBD)

23 RRC May – 16 June 2006 Geneva Switzerland General Analysis – DT2/DS2

24 RRC May – 16 June 2006 Geneva Switzerland General Analysis – DT1/DS1

25 RRC May – 16 June 2006 Geneva Switzerland GA – DT2/DS2 Part of SFN DT2/SFN DS2

26 RRC May – 16 June 2006 Geneva Switzerland Parts of SFN DT2/SFN DS2

27 RRC May – 16 June 2006 Geneva Switzerland GA – DT1/DS1 Part of SFN DT1/SFN DS1

28 RRC May – 16 June 2006 Geneva Switzerland Parts of SFN DT1/SFN DS1

29 RRC May – 16 June 2006 Geneva Switzerland GA – DT2/DS2 Part of SFN DT2+DT1/SFN DS2+DS1

30 RRC May – 16 June 2006 Geneva Switzerland Parts of SFN DT2+DT1/SFN DS2+DS1

31 RRC May – 16 June 2006 Geneva Switzerland GA – DT1/DS1 Part of SFN DT2+DT1/SFN DS2+DS1

32 RRC May – 16 June 2006 Geneva Switzerland GA – DT2/DS2 Part of DT2+DT1/DS2+DS1

33 RRC May – 16 June 2006 Geneva Switzerland GA – DT1/DS1 Part of DT2+DT1/DS2+DS1

34 RRC May – 16 June 2006 Geneva Switzerland GA – Detailed Analysis For any incompatibility, additional data can be calculated in real-time by right-clicking on Detailed analysis For d2a details, the directory with the pre-calculated analogue reference situation binary file must be given (if not detected in the same directory as the results database)

35 RRC May – 16 June 2006 Geneva Switzerland Detailed Analysis – d2d (incoming)

36 RRC May – 16 June 2006 Geneva Switzerland Detailed Analysis – d2d (incoming) (2)

37 RRC May – 16 June 2006 Geneva Switzerland Detailed Analysis – d2a

38 RRC May – 16 June 2006 Geneva Switzerland DA – Reference Situation for d2a

39 RRC May – 16 June 2006 Geneva Switzerland Detailed Analysis – d2a (3)

40 RRC May – 16 June 2006 Geneva Switzerland General Analysis - Hints All incompatibilities are presented in all cases (1, 2, 3 and 4), even if they have administrative declarations Sorting may be used to focus on those without declarations Sorting on descending values of margin and CNFS will place rows with missing values first, since these are cases of service area overlaps and Tx inside

41 RRC May – 16 June 2006 Geneva Switzerland General Analysis – More Hints In cases 1/2/3, some d2d results shown have no adverse effect, since there are no common or overlapping available channels Draft Plan Case 1: 2,8 M (or 52 %) d2d incompatibilities with no effect because of less available spectrum

42 RRC May – 16 June 2006 Geneva Switzerland GA Case 1– No Common Av. Ch.

43 RRC May – 16 June 2006 Geneva Switzerland Synthesis Results Channel distribution statistics Coverage analysis – option to limit the display to assigned channels Service areas – option to limit the display to assigned channels Future work: right-click menu must show the available channels/blocks and the assigned channel/block in addition to the acceptable channels/blocks

44 RRC May – 16 June 2006 Geneva Switzerland Planning Exercise Tool GUI for EBU TD planning software Supports 5 types of analysis and (optional) synthesis Supports new format of admin declarations (CR/254 addendum 1)CR/254 addendum 1 If using admin declarations, a new window will show which declarations have been validated/pair-checked

45 RRC May – 16 June 2006 Geneva Switzerland PE Tool – Input Data Input data can come from input data or results MDB files from BR web site RRC_Requirements must be used to edit/merge digital requirements data RRC_Requirements For d2a analysis, it is possible to use pre-calculated analogue TV reference situation binary files provided by BR

46 RRC May – 16 June 2006 Geneva Switzerland PE Tool – Admin Declarations Administrative declarations can be copied from a results database, or taken from one or more CSV files, or both (a CSV file must be for one adm) For testing, the PE tool can consider all declarations to be pair-checked, or it can enforce strict pair-checking

47 RRC May – 16 June 2006 Geneva Switzerland PE Tool d2d Example - Input

48 RRC May – 16 June 2006 Geneva Switzerland PE Tool d2d Example – Input (2)

49 RRC May – 16 June 2006 Geneva Switzerland PE Tool d2d Example – Input (3)

50 RRC May – 16 June 2006 Geneva Switzerland PE Tool d2d Example – Input (4)

51 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example – Step 1

52 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example – Step 2

53 RRC May – 16 June 2006 Geneva Switzerland PE Tool – Review ADs

54 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example – Run

55 RRC May – 16 June 2006 Geneva Switzerland PE Tool – Digital Reqs Validation

56 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d – Must Include Analogue

57 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example – Step 2 (2)

58 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example – Run (2)

59 RRC May – 16 June 2006 Geneva Switzerland PE Tool – Analogue Validation

60 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example – OK

61 RRC May – 16 June 2006 Geneva Switzerland PE - Compatibility Status

62 RRC May – 16 June 2006 Geneva Switzerland PE - Compatibility Status (2)

63 RRC May – 16 June 2006 Geneva Switzerland PE Tool - Hints For the next PE, the previous small results MDB can now serve as the input MDB After selecting an admin declarations CSV file, make sure to click on Add file

64 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example 2

65 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example 2 (2)

66 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example 2 (3)

67 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example 2 (4)

68 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example 2 (5)

69 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example 2 (6)

70 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example 2 (7)

71 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example 2 (8)

72 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example 2 (9)

73 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example 2 (10)

74 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example 2 (11)

75 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example 2 (12)

76 RRC May – 16 June 2006 Geneva Switzerland PE Tool – d2d Example 2 (13)

77 RRC May – 16 June 2006 Geneva Switzerland Administrative Declarations Tool Supports new format of admin declarations (CR/254 addendum 1)CR/254 addendum 1 Supports editing comments in place Supports opening a file in the old format and saving in the new format Can ensure creation of all possible 1-to-1 declarations among parts of sets of linked requirements

78 RRC May – 16 June 2006 Geneva Switzerland AD Tool – AD Rules File must have only one administration code on the left Conditional self-declarations are saved to file as un-conditional Declarations for analogue assignments only created for those assignments included in the planning (BC6=TRUE) Can ensure creation of all possible declarations among 2 sets of linked requirements, if requested

79 RRC May – 16 June 2006 Geneva Switzerland AD Tool – AD Rules (contd) Self-declarations are saved to file only in one direction, the other direction being considered as a duplicate Creating new duplicate declarations updates the intent (ADD/MOD/SUPP), the conditional flag, and the remark for the existing declaration

80 RRC May – 16 June 2006 Geneva Switzerland AD Tool – AD Rules for 1-to-1 D2D/O2D/D2O must have common or overlapping bandwidths A2D/D2A must have adjacent or common/overlapping bandwidths Self-declarations within a linked set are not created A2D/D2A declarations not created when D is a conversion from A

81 RRC May – 16 June 2006 Geneva Switzerland AD Tool - Hints The AD tool can be used to quickly generate many syntactically correct declarations, but that doesn t mean it should be used that way Exporting reciprocal declarations, importing (reciprocal) declarations are time-saving features found in the File menu

82 RRC May – 16 June 2006 Geneva Switzerland Future Improvements Display of each requirement s worst MIG according to the RSD (%) criteria Display of MIGs for an administration –Global MIGs with admin declarations –Global MIGs without self-declarations –Internal MIGs with admin declarations –Internal MIGs without self-declarations

83 RRC May – 16 June 2006 Geneva Switzerland Future Improvements (contd) Complementary analysis results Real-time calculation of the contour corresponding to a user-provided F/S CNG support improvements –Saving maps to graphics file –Generating maps of assigned/non- assigned requirements per channel

84 RRC May – 16 June 2006 Geneva Switzerland Rectangular Area Selection

85 RRC May – 16 June 2006 Geneva Switzerland Future Future Improvements Some form of terrain data display Other conference decisions as necessary Geneva hotel room reservation system – ensure equitable access

86 RRC May – 16 June 2006 Geneva Switzerland Thank you for your attention

87 RRC May – 16 June 2006 Geneva Switzerland Good Night and Good Luck


Download ppt "Regional Radiocommunication Conference (RRC-06) 15 May - 16 June 2006, Geneva, Switzerland RRC-06 Planning Interface Miroslav Ćosić, Andrea Manara Radiocommunication."

Similar presentations


Ads by Google