creation of electronic notices with spacecap …...creation of electronic notices with spacecap...

Creation of electronic notices Creation of electronic notices with SpaceCap software with SpaceCap software

for submissions under Appendices for submissions under Appendices 3030, , 30A30A and and 30B30B

Presented by Mark Griffin

ITU-BR Space Regulatory Workshop, July 2008

June 2008 BR / SSD / SNP 2

PresentationPresentationBroadcasting Space Service (BSS) Plan and associated feeder-link –(Ap30/30A Art.4/5)

General submission schema and data organization in the SpaceCap software

Exercise on AP30 / questions (40’)

Annex1: Fixed Satellite Service (FSS) Plan – (Ap30B Art. 6/8)

Annex2: Space Operating Function (SOF) service – (Ap30/30A Art.2A)


Ap30/30A Ap30/30A –– General submission schemaGeneral submission schema

Notices under Articles 4 and 5 of Ap30/30A submit Appendix 4 (Ap4) data items

SPS (Space Plans Systems) databaseContains basic characteristics and reference situation of the assignments (Ap30/30A Plans, Lists and Article 4 networks, notified assignments under Article 5 and SOF Article 2A)

Similar structure as in SNS (SRS_ALL) database, with some differences in usage of the tables and fields

Electronicnotice

created bySpaceCap

SPSdatabase

SpaceCapsoftware

Sent by the submittingAdministration to BR to

be processed

Ref situationand data

published by BR

RR Appendix 4

View TSUMwith SpacePub

software Starting SpaceCap (version 6) softwareopen an SPS (Space Plans Systems) databaseselect the “Plan” button (on the top right toolbar)

Note: “Open Plan for Inquiry only” option enables read only access


Ap30/30A Ap30/30A -- Data organization in the SpaceCap softwareData organization in the SpaceCap software (1)(1)

Common data to all frequencies of a network (satellite name, orbital position…)

Attachments to submission(type (Paper, GXT, File), file name, description)

Note: normally filled in through other data entry forms

Strapping information for Region 2

Agreements reachedNote: captured in the “Coordination” data entry form

Satellite beam characteristics (satellite antenna gain, boresight…)

Groups of frequencies (common characteristics such as polarization type and

service area…)

Notice

Beam 2Beam 1

Attachments CoordinationStrapping(Region 2)

Beam 3

Group 2Group 1 Group 3


Ap30/30A Ap30/30A -- Data organization in the SpaceCap softwareData organization in the SpaceCap software (2)(2)

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)

Group 1

Emission /Frequencies

Srv Area /Typical Antenna

Group 2 Group 3

Modulationcharacteristics

Assoc SpecificEarth Ant.

(feeder-link only)

Assoc SpecificEarth Ant.

(feeder-link only)


Exercice/Questions (40’)

Select New Notice

SetTemplateto PLAN

SetPLAN ID

at least one “Group” of one “Beam”must be captured previously.

For full-time operation = 0 to 24

Depending of the notice type, “beam identification”

or “notice ID”of previously published notices


List from the APL reference library


Select Common data

If blank, no MSPACE internal grouping applicable


Common dataCommon data

Close to capture other data…


Automatic calculation ofchannel number from frequency

orFrequency from channel number

As defined in Appendix 1

Click to capture modulation

characteristic data…

Automatic calculation


Modulation CharacteristicsModulation Characteristics

List of references proposed


Up to 20 test points within the service area


List of attachments to the submission


List of agreements obtained from other adminsitrations

Electronic notice ready to be submitted to BR

Creating a TSUM with SpacePub


SpaceValSpaceVal


Ap4 data capture observation concerning specific items Ap4 data capture observation concerning specific items to Articles 4 and 5 of Ap30/30A to Articles 4 and 5 of Ap30/30A (1)(1)

SpaceCap Data Entry

Form

Annex 2 to Ap4 Data Item

No. Description

Observation

Notice A.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

Notice A.11 Regular 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

Notice A.13cA.13d

Notice ID of the corresponding network previously processed under Article 4/5 of Ap30/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 of Ap30/30A

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



SpaceCap Data Entry

Form

Annex 2 to AP4 Data Item

No. Description

Observation

Emissions/Frequencies

of Group

C.2.a.2 Channel number

1/ If the user enters first the channel number, the corresponding center frequency in the Plan will be set by SpaceCap and then can be modified by the user.

2/ If the user enters first the frequency (freq), the corresponding channel (cha) is calculated using the following formula:

Cha = Integer((Freq + Cha_Spacing / 2 – Plan_Freq) / Cha_Spacing) + 1

Where:Freq: center frequency of the assignment (C.2.a.1);Chan_Spacing: 19.18 MHz for Regions 1 and 3; 14.58 MHz for Region 2;Plan_Freq: center frequency of channel 1 of the Plans as follows:

Regions 1 and 3:Downlink: 11727.48 MHzFeeder-link (14GHz): 14525.30 MHz Feeder-link (17GHz): 17327.48MHz

Region 2:Downlink: 12224.00 MHzFeeder-link: 17324.00 MHz

Emissions/Frequencies

of Group

C.8.b.1 C.8.b.2 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: total power B: necessary bandwidth



SpaceCap Data Entry

Form

Annex 2 to Ap4 Data Item

No. Description

Observation

Modulation characteristics

A.12 Range of automatic gain control

See also observation on item C.9.b

Modulation characteristics

C.9.b Modulation characteristics

To open this form, click on the corresponding designation of emission on the “Emissions/Frequencies” form.

To copy the modulation characteristics of a specific designation of emission into all corresponding emissions, activate option on the “Modulation characteristics” form:“Apply these characteristics to all emissions in all groups of this notice with the same designation of emission”

Group C.15.a MSPACE group identification code

Application of internal grouping: Article 4 assignments are usually grouped with the co-channel and co-orbital position assignments of the responsible administration in the Plan, or List, or other previously submitted Article 4 assignments of the same administration.

Note: Not applicable when the coverage areas are largely separated! This issue should be clarified in the telefax or e-mail corresponding to the submission.

For describing the internal grouping of the assignments of the network, a MSPACE software group code (MSPACEgrp) should be assigned to this item for each group of assignments on the “Group” form of SpaceCap software (SCAPgrp). If this field is blank, it is understood that no MSPACE internal grouping is applicable to the assignments of the corresponding SCAPgrp.

Note: 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 MSPACEgrp of assignment A.



SpaceCap Data Entry

Form

Annex 2 to Ap4Data Item

No. Description

Observation

Strapping D.1.a Connection between uplink and downlink frequency assignments in each transponder for each intended combination of receiving and transmitting beams

Only for submissions in Region 2 where OEPM (overall downlink and feeder-link Equivalent Protection Margin calculation) applicable.

After capturing all assignments of all downlink and feeder-link beams, the “Strap wizard” on the “Strapping” form should be used to connect downlink and feeder-link assignments.

Notes:1/ Before each click on “Strap” button, only one connection on the following slide shall be selected!

2/ Before exiting that form, click “Validation” button to verify that all assignments for all downlink and feeder-link channels have strapped!

For recording the intermediate changes into the database, click “Finish” button. Then click “Validate” button.

At the end, the “Strapping” tab or the notice itself shall be closed in order to save changes and update the internal table beam_tr in the working database.


Ap4 data capture observation concerning strapping methodAp4 data capture observation concerning strapping methodto Articles 4 and 5 of Ap30/30Ato Articles 4 and 5 of Ap30/30A

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: BmdlGrp1: 1, 3, 5, 7Grp2: 2, 4, 6, 8

Beam: BmflGrp3: 1, 3, 5, 7Grp4: 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: BmdlGrp1: 1, 3, 5, 7

Beam: BmflGrp3: 1, 3, 5, 7

Assignment level strapping

Connecting one downlink frequency to a feeder-link frequency

Any downlink channel can be connected to any feeder-link channels.

Beam: BmdlGrp1: 3

Beam: BmflGrp4: 6


Annex 1Annex 1

Fixed Space Service (FSS) Plan Fixed Space Service (FSS) Plan

Creation of electronic submissionsCreation of electronic submissions

Appendix 4 information submitted underArticles 6 and 8 of Appendix 30B (Ap30B)


FSS Plan FSS Plan –– Art.6 and 8 of Ap30BArt.6 and 8 of Ap30BData organization in the SpaceCap softwareData organization in the SpaceCap software (1)(1)

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

Agreements reachedNote: captured in the “Coordination” data entry form

Antenna beam characteristics(satellite antenna gain, boresight…)

Groups of frequencies(common characteristics, service area…)

Notice

Beam 2Beam 1

Attachments CoordinationStrapping

Beam 3



FSS Plan FSS Plan –– Art.6 and 8 of Ap30BArt.6 and 8 of Ap30BData organization in the SpaceCap softwareData organization in the SpaceCap software (2)(2)

Emission characteristics of a specific group (frequency bands available for 4500frequency bands available for 4500--4800MHz,67254800MHz,6725--7025MHz, 7025MHz,

10.7010.70--10.95GHz, 11.2010.95GHz, 11.20--11.45GHz, 12.7511.45GHz, 12.75--13.25GHz,13.25GHz,

noise temperature (C/I protection ratio)noise temperature (C/I protection ratio), power…)

Service area, test points and typical earth station antenna characteristics of a specific group

Group 1

Emission /Frequencies

Srv Area /Typical Antenna

Group 2 Group 3


Annex 2Annex 2

Space Operating Function (SOF) ServiceSpace Operating Function (SOF) Service

Creation of electronic submissionsCreation of electronic submissions

Appendix 4 information submitted underArticles 2A Appendices 30 and 30A (Ap30/30A)


SOF SOF –– Art.2A of Ap30/30AArt.2A of Ap30/30AData organization in the SpaceCap softwareData organization in the SpaceCap software (1)(1)

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

Antenna beam characteristics(satellite antenna gain, boresight…)

Groups of frequencies(common characteristics such as polarization type

and service area…)

Notice

Station

Beam 2Beam 1

AttachmentsNoiseGamma

Strapping(optional)

Beam 3



SOF SOF –– Art.2A of Ap30/30A Art.2A of Ap30/30A Data organization in the SpaceCap softwareData organization in the SpaceCap software (2)(2)

Emission characteristics of a specific group (frequency guard bands availablefrequency guard bands available)

Agreements reachedNote: captured in the “Coordination”

data entry form

Associated earth station

antenna characteristics of a specific group

Group 1

Emission

AssocEarth Station

Coordination

Frequencies

Group 2 Group 3

SpecialSection


Creation of electronic Ap30/30A notices with SpaceCap software:

http://www.itu.int/ITU-R/software/space/spacecap/

SPS databases:

http://www.itu.int/ITU-R/space/plans/AP30-30A/http://www.itu.int/ITU-R/space/plans/MIFR/

Web links for further informationWeb links for further information


Questions?

creation of electronic notices with spacecap …...creation of electronic notices with spacecap...

Documents