1. Slide 1 World Radiocommunication Seminar Geneva, 15-19 November 2004 AP30/30A Plans & Lists Workshop Submission of Appendix 4 information under Articles 4 and 5

2. Slide 2 World Radiocommunication Seminar Geneva, 15-19 November 2004 Data capture by the SpaceCap (version 5) software Notices under Articles 4 and 5 of Appendices 30 and 30A submit Appendix 4 data items SPS (Space Plans Systems) database - Contains the basic characteristics and reference situation of the assignments (AP30/30A Plans, Lists and Article 4 networks, notified assignments under Article 5) - Similar structure SNS (SRS_ALL) database, with some differences in usage of the tables and fields Starting SpaceCap: - open a SPS (Space Plans Systems) database - select the Plan button (on the top right toolbar) Note: Open Plan for Inquiry only option enables to access on read only

3. Slide 3 World Radiocommunication Seminar Geneva, 15-19 November 2004 Data organization in the SpaceCap software (1) Notice Beam 1Beam 2Beam 3 Group 1 (3) Group 1Group 2Group 3 Attachments Coordination Strapping (Region 2) Common data to all frequencies of a network (satellite name, orbital position…) Diagrams data (type (Paper, GXT, File), file name, description) Note: normally filled in through other data entry forms Strapping information for Region 2 Agreements reached Note: captured in the Coordination data entry form Antenna beam characteristics (satellite antenna gain, boresight…) Group of frequencies (common characteristics such as polarization type and service area…)

4. Slide 4 World Radiocommunication Seminar Geneva, 15-19 November 2004 Data organization in the SpaceCap software (2) Group 1 (3) Group 1Group 2Group 3 Emission/ Frequencies Srv. Area/ Typ. Antenna Assoc Specific Earth Ant. (feeder-link only) Assoc Specific Earth Ant. (feeder-link only) Modulation characteristics Emission characteristics of a specific group (frequencies, power and modulation characteristics) Service area, test points and typical earth station antenna characteristics of a specific group Specific earth station antenna characteristics of a certain group in the case of feeder-link only (if any)

5. Slide 5 World Radiocommunication Seminar Geneva, 15-19 November 2004 AP4 data capture observation concerning items specific to Art 4 & 5 of AP30/30A (1) SpaceCap Data Entry Form Annex 2 to AP4 Data Item Item No. Description Observation NoticeA.1.b Beam identification Required only in the following submissions: - § 4.1.27 of Article 4 of AP30/30A - § 4.2.6 of Article 4 of AP30/30A in the case of modification to existing assignments in the Region 2 Plan - § 4.2.24 of Article 4 of AP30/30A for the suppression of existing assignments in the Region 2 Plan - § 5.1.2 of Article 5 of AP30 and § 5.1.6 of Article 5 of AP30A in the case of notification of Plan assignments - § 4 of the Annex to Resolution 42 NoticeA.11Regular hours of operation (UTC) Before capturing this data item, at least one Group of one Beam must be captured. For full-time operation 0 to 24 should be indicated NoticeA.13c A.13d Notice ID of the corresponding network previously processed under Article 4/5 of Appendices 30 or 30A Article 4: modification to a network in the Regions 1 and 3 List or to a network already successfully entered into the Region 2 Plan - cancellation of a Plan, List or Article 4 network - submission of the final characteristics of a network under § 4.1.12 or § 4.2.16 of Article 4 Article 5: - notification of a network in the Regions 1 and 3 Plan or List or a network already entered into the Region 2 Plan - cancellation of previously notified assignments

6. Slide 6 World Radiocommunication Seminar Geneva, 15-19 November 2004 AP4 data capture observation concerning items specific to Art 4 & 5 of AP30/30A (2) SpaceCap Data Entry Form Annex 2 to AP4 Data Item Item No. Description Observation Emissions/ Frequencies of Group C.2.a.2The channel number If the user enters first the channel number, the corresponding center frequency in the Plan will be set by SpaceCap that could be modified by the user. If the frequency is entered first, the corresponding channel is calculated using the following formula: Channel = Integer((Frequency + Channel_Spacing / 2 – Plan_Frequency) / Channel_Spacing) + 1 Where: Frequency: center frequency of the assignment (C.2.a.1); Channel_Spacing: 19.18 MHz for Regions 1 and 3; 14.58 MHz for Region 2; Plan_Frequency: The center frequency of channel 1 of the Plans as follows: Regions 1 and 3: Downlink: 11727.48 MHz Feeder-link (14GHz): 14525.30 MHz Feeder-link (17GHz): 17327.48MHz Region 2: Downlink: 12224.00 MHz Feeder-link: 17324.00 MHz Emissions/ Frequencies of Group C.8.b.1 C.8.b.1 C.8.h Total power and power density values For digital emissions, if the power density field is empty, a default value (assuming uniform distribution of the power over the necessary bandwidth) is calculated once the total power is entered using the following formula: pwr-10 log(B) where pwr is the total power and B is the necessary bandwidth

7. Slide 7 World Radiocommunication Seminar Geneva, 15-19 November 2004 AP4 data capture observation concerning items specific to Art 4 & 5 of AP30/30A (3) SpaceCap Data Entry Form Annex 2 to AP4 Data Item Item No. Description Observation Modulation characteristics A.12Range of automatic gain control See also observation on item C.9.b Modulation characteristics C.9.bModulation characteristics To open this data entry form, the user should click on the corresponding designation of emission on the Emissions/Frequencies form. In order to copy the modulation characteristics of a specific designation of emission into all corresponding emissions, the user should activate the following option on the Modulation characteristics data entry form of SpeceCap: Apply these characteristics to all emissions in all groups of this notice with the same designation of emission GroupC.15.athe MSPACE group identification code Article 4 assignments are usually grouped with the co-channel & co-orbital position assignments of the responsible administration in the Plan, or List, or other previously submitted Article 4 assignments of the same administration, unless the coverage areas are largely separated. This issue should be clarified in the fax or email corresponding to the submission. For describing the internal grouping of the assignments of the network, a MSPACE group code should be assigned to this item for each group of assignments on the Group from of SpaceCap. If this field is blank, it is understood that no MSPACE internal grouping is applicable to the assignments of the corresponding Group. It is to be noted that multiple MSPACE grouping for a specific assignment is not possible. For instance if assignment A should be grouped with assignments B and C, these two assignments have also to be grouped since they shall have the same MSPACE group code of assignment A. See

8. Slide 8 World Radiocommunication Seminar Geneva, 15-19 November 2004 AP4 data capture observation concerning items specific to Art 4 & 5 of AP30/30A (4) SpaceCap Data Entry Form Annex 2 to AP4 Data Item Item No. Description Observation StrappingD.1.aThe connection between uplink and downlink frequency assignments in each transponder for each intended combination of receiving and transmitting beams. This item is only required for the submissions in Region 2 where the OEPM (overall downlink and feeder-link Equivalent Protection Margin calculation) is applicable. After capturing all assignments of all downlink and feeder-link beams, the Strap wizard on the Strapping data entry form of the SpaceCap should be used to connect downlink and feeder-link assignments. On the wizard, each time before pressing the Strap button, only one of the connection listed on the following slide shall be selected. Before exiting that form, the Validation button should be pressed to verify that all assignments have strapped. For recording the intermediate changes into the database, the Finish button should be pressed. Then the Validate button shall be used to check whether for all downlink and feeder-link channels there is at least one connection to an opposite link channel. At the end the Strapping tab or the notice itself shall be closed in order to save changes to the database and update the internal table beam_tr in the working database.

9. Slide 9 World Radiocommunication Seminar Geneva, 15-19 November 2004 AP4 data capture observation concerning items specific to Art 4 & 5 of AP30/30A (5) Strapping method Description Condition Example Downlink Beam channels Feeder-link Beam channels Beam level strapping Connecting one downlink beam to a feeder-link beam For each downlink group of frequencies, a feeder-link group with frequencies having the same downlink channel number shall exist and vice-versa. Beam: Bmdl Grp1: 1, 3, 5, 7 Grp2: 2, 4, 6, 8 Beam: Bmfl Grp3: 1, 3, 5, 7 Grp4: 2, 4, 6, 8 Group level strapping Connecting one downlink group of frequencies to a feeder- link group of frequencies The channel numbers of the downlink group shall be equal to those of the feeder-link group. Beam: Bmdl Grp1: 1, 3, 5, 7 Beam: Bmfl Grp3: 1, 3, 5, 7 Assignment level strapping Connecting one downlink frequency to a feeder-link frequency Any downlink channel could be connected to any feeder-link channels. Beam: Bmdl Grp1: 3 Beam: Bmfl Grp4: 6

10. Slide 10 World Radiocommunication Seminar Geneva, 15-19 November 2004 More detailed information about Appendix 4 data capture for AP30/30A notices can be found on the ITU website at the following address: http://www.itu.int/ITU-R/space/plans/FAQ/SpaceCap5.html