43
Radiocommunication Seminar 2010 SpaceCom SpaceCom Presented by Presented by K. P K. Peker eker (BR (BR-Space Services Dept.) Space Services Dept.)

SpaceCom WRC 2005 - ITU

  • Upload
    others

  • View
    6

  • Download
    0

Embed Size (px)

Citation preview

Page 1: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

SpaceComSpaceCom

Presented byPresented by

K. PK. Pekereker

(BR(BR--Space Services Dept.)Space Services Dept.)

Page 2: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Coordination of Satellite Coordination of Satellite

NetworksNetworks

Section II, Section II, Article 9Article 9“Procedure for effecting coordination “Procedure for effecting coordination

with or obtaining agreement of the with or obtaining agreement of the

other administrations”other administrations”

Contains (almost) all cases (forms) of Contains (almost) all cases (forms) of

coordination for satellite networks coordination for satellite networks

(GSO and Non(GSO and Non--GSO), earth and GSO), earth and

terrestrial stations terrestrial stations

Page 3: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Coordination is an obligation:Coordination is an obligation:

for the administration wishing to for the administration wishing to

assign a frequency to a station;assign a frequency to a station;

for any other administration whose for any other administration whose

services might be affected (No. 9.53)services might be affected (No. 9.53)

Page 4: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Application of No. 9.53AApplication of No. 9.53A

No.No. 9.529.52 objections to be submitted by administrations within four months of the date of publication of the BR IFIC

No. 9.52C for coordination requests under Nos.9.11 to 9.14 and 9.21, absence of disagreement within absence of disagreement within the 4 month period means agreementthe 4 month period means agreement

No. 9.53A the treatment by the Bureau of such comments in respect of a coordination request

Page 5: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Scope of No. 9.53AScope of No. 9.53A

Coordination fromCoordination from Coordination with respect toCoordination with respect to ProvisionProvision

9.11, 9.14, 9.21/C,9.11, 9.14, 9.21/C,

RS33#2.1RS33#2.1

GSO or NGSO or N--GSOGSO TerrestrialTerrestrial

NN--GSOGSO NN--GSOGSO

GSOGSO GSOGSO

9.129.12

9.139.13

9.12A9.12A

9.21/A9.21/A

9.21/B9.21/B

Page 6: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

resolves 2resolves 2 of Resolution 55(Rev. WRC07)of Resolution 55(Rev. WRC07)

As from 17 November 2007, all disagreements As from 17 November 2007, all disagreements submitted to the Bureau pursuant No. 9.52 in respect submitted to the Bureau pursuant No. 9.52 in respect

of coordination requests under 9.11 to 9.14 and of coordination requests under 9.11 to 9.14 and 9.21/A,B,C are to be provided in electronic format 9.21/A,B,C are to be provided in electronic format

created by created by SpaceComSpaceCom..

Radio Regulation Board fixed the deadline of Radio Regulation Board fixed the deadline of

01 July 200901 July 2009 as the effective date of application for as the effective date of application for mandatory electronic filing.mandatory electronic filing.

Beyond this date, disagreements described above will Beyond this date, disagreements described above will be taken into consideration only if submitted by be taken into consideration only if submitted by

SpaceComSpaceCom

Page 7: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

WhatWhat is SpaceCom?is SpaceCom?

SpaceCom SpaceCom

an application designed to assist an application designed to assist

administrations in the management of administrations in the management of

the objections under No. 9.52 the objections under No. 9.52

on CR/C Special Section on CR/C Special Section

concerning requests for coordination concerning requests for coordination

under under 9.119.11 to to 9.149.14,, 9.219.21 and and RS33#2.1RS33#2.1

and their treatment under 9.53A and their treatment under 9.53A

Page 8: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Telecommunication OperatorsTelecommunication Operators

Notifying AdministrationNotifying Administration

ITUITU--BRBR

Potentially Affected AdministrationPotentially Affected Administration

SpaceComSpaceComWho are the usersWho are the users??

Page 9: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Page 10: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Page 11: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Page 12: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar

December 2010 GENEVA

Exchange of informationExchange of information

Comments must

be sent in form of

fax, letter etc. but

not in .mdb file

Step

1

Step

2

Step

3 Step

4

Page 13: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Page 14: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Page 15: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Page 16: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Page 17: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Page 18: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

SpaceComSpaceComCR/C CR/C for the publication of for the publication of CR/D CR/D

How does it work???How does it work???

Page 19: SpaceCom WRC 2005 - ITU

Radiocommunication

Seminar 2010

Page 20: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Page 21: SpaceCom WRC 2005 - ITU

Radiocommunication

Seminar 2010

Page 22: SpaceCom WRC 2005 - ITU

Radiocommunication

Seminar 2010

Page 23: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Page 24: SpaceCom WRC 2005 - ITU

Import comments on CR/C from external database(s) to the Import comments on CR/C from external database(s) to the

local database in order to create a unique file to be sent to the local database in order to create a unique file to be sent to the

BRBR

Radiocommunication Seminar 2010

Page 25: SpaceCom WRC 2005 - ITU

Merge in house multiMerge in house multi--user commentsuser comments

Radiocommunication Seminar 2010

Page 26: SpaceCom WRC 2005 - ITU

Merge operator commentsMerge operator comments

Radiocommunication Seminar 2010

Page 27: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Your validation on the current Your validation on the current comments will comments will be considered as valid only if it is checked as be considered as valid only if it is checked as

'completed' whether you are identified or not by the BR 'completed' whether you are identified or not by the BR

Page 28: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar

December 2010 GENEVA

Confirm your addition in coordination for Confirm your addition in coordination for

provisions provisions

9.11, 9.14, 9.21/C, RS33 # 2.19.11, 9.14, 9.21/C, RS33 # 2.1

pfdpfd excess

Confirm your addition in coordination for Confirm your addition in coordination for

provisions provisions

9.12, 9.12A, 9.13, 9.21/A, 9.21/B9.12, 9.12A, 9.13, 9.21/A, 9.21/B

Confirm your addition for provisions Confirm your addition for provisions

9.11, 9.14, 9.21/C, RS33 # 2.19.11, 9.14, 9.21/C, RS33 # 2.1

the territory of

your Adm. is

visible from the

satellite and the

coordination is

required.

frequency

overlap

Potentially Affected Administration may have the possibility toPotentially Affected Administration may have the possibility to

Add comments Add comments

more information more information

may be requested to justify your request depending on the may be requested to justify your request depending on the

BR examination results and type of the current provisionBR examination results and type of the current provision

Page 29: SpaceCom WRC 2005 - ITU

Apply for provisions 9.11, 9.14, 9.21/C, RS33 # 2.1Apply for provisions 9.11, 9.14, 9.21/C, RS33 # 2.1

Radiocommunication Seminar 2010

Page 30: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Page 31: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Apply for provisions 9.12, 9.12A, 9.13, 9.21/A, 9.21/BApply for provisions 9.12, 9.12A, 9.13, 9.21/A, 9.21/B

Page 32: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Page 33: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Notifying AdministrationNotifying Administration

((ConfirmsConfirms a a draftdraft CR/D)CR/D)

Page 34: SpaceCom WRC 2005 - ITU

Radiocommunication

Seminar 2010

Your validation on the current Your validation on the current comments will comments will be considered as valid only if it is checked as be considered as valid only if it is checked as

'completed' whether you are identified or not by the BR 'completed' whether you are identified or not by the BR

Page 35: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

View draft CR/D mdb file

The database containing the draft CR/D information can be

viewed by any administration and is distributed in the BR IFIC

(Space Services) CD-ROM

Page 36: SpaceCom WRC 2005 - ITU

Radiocommunication

Seminar 2010

Page 37: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

In the case In the case

Notifying Administration Notifying Administration

acts on behalf of acts on behalf of

Potentially affected Administration Potentially affected Administration

thethe copy of the documents received from the copy of the documents received from the Potentially Potentially

Affected AdministrationAffected Administration must be send to the Bureau must be send to the Bureau

explaining why it is requested to be added in the explaining why it is requested to be added in the

coordination process.coordination process.

Notifying Administration have the possibility to input Notifying Administration have the possibility to input

comments not received by the BR, or received out of the comments not received by the BR, or received out of the

regulatory period by the BR. regulatory period by the BR.

Page 38: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

••Operators Operators should send their validated should send their validated

comment comment files directly to their files directly to their Administration Administration

NOTNOT to BRto BR

••All comments files should be merged into one All comments files should be merged into one

database file before being sent to the BR by database file before being sent to the BR by

the Administration.the Administration.

Page 39: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

QQ and Aand A

Q.Q. How I could use How I could use SpaceComSpaceCom software to send my software to send my comments in electronic format to provide comments in electronic format to provide

agreement in order to conclude coordination with agreement in order to conclude coordination with XY Administration?XY Administration?

A. A. SpaceComSpaceCom is not intended for sendingis not intended for sending agreements agreements but objections. Only but objections. Only AdminsAdmins that objected within 4 that objected within 4

months become part of final coordination months become part of final coordination requirements and this is published in special requirements and this is published in special

section CR/D (cf. 9.53A). section CR/D (cf. 9.53A).

AdminsAdmins. that do not have a reason or do not want . that do not have a reason or do not want to object need not send an agreement to object need not send an agreement -- absence of absence of

objection is sufficient. objection is sufficient.

Page 40: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Q. One of those Special Sections in which our Q. One of those Special Sections in which our

Administration is mentioned as being affected is not Administration is mentioned as being affected is not

included in the included in the SpaceComSpaceCom list for comments?list for comments?

A. In the context of A. In the context of SpaceComSpaceCom,, commentscomments in respect of in respect of

CR/C special section (=coordination of satellite CR/C special section (=coordination of satellite

networks in nonnetworks in non--planned services) are in fact objections planned services) are in fact objections

underunder No. 9.52 and that only in respect of the following No. 9.52 and that only in respect of the following

forms of coordination: Nos. 9.11 (or Res.33, Section 2), forms of coordination: Nos. 9.11 (or Res.33, Section 2),

9.11A (i.e. 9.12, 9.12A, 9.13 and9.11A (i.e. 9.12, 9.12A, 9.13 and 9.14), and 9.21 (9.14), and 9.21 (i.ei.e

9.21/A, 9.21B and 9.21/C). For these forms of 9.21/A, 9.21B and 9.21/C). For these forms of

coordination, what the BR identifies as potentially coordination, what the BR identifies as potentially

affected affected AdminsAdmins. is only for information (cf. 9.36.1). is only for information (cf. 9.36.1) ..

SpaceCom for CR/C does not cover other forms of

coordination notably 9.7

Page 41: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Q.Q. SpaceCom software fetches only 8 Special Sections SpaceCom software fetches only 8 Special Sections

CR/Cs instead of all 16 of that BR IFICXXYY?CR/Cs instead of all 16 of that BR IFICXXYY?

A.A. In BRIFIC XXYY there are only 8 CR/Cs which have In BRIFIC XXYY there are only 8 CR/Cs which have

forms of coordination covered by SpaceCom. Other 8 forms of coordination covered by SpaceCom. Other 8

CR/Cs concern 9.7. CR/Cs concern 9.7.

SpaceCom cannot be used for objections or agreements SpaceCom cannot be used for objections or agreements

concerning coordination under 9.7 and some others concerning coordination under 9.7 and some others

(all those listed(all those listed in the upper half of the table on the in the upper half of the table on the

cover page of CR/C). cover page of CR/C).

When you launch SpaceCom in CR/C mode against a When you launch SpaceCom in CR/C mode against a

particular IFIC, it selects only those CR/Cs that contain particular IFIC, it selects only those CR/Cs that contain

forms of coordination 9.11 to 9.14 and 9.21A/B/C.forms of coordination 9.11 to 9.14 and 9.21A/B/C.

Page 42: SpaceCom WRC 2005 - ITU

Radiocommunication Seminar 2010

Q. Our Administration has sent its objections with Q. Our Administration has sent its objections with

SpaceComSpaceCom database within 4 months deadline but it’s database within 4 months deadline but it’s

not listed in the Table I “summary of coordination not listed in the Table I “summary of coordination

requirements” of CR/D Special section as an requirements” of CR/D Special section as an

Administration requesting coordination. How is that Administration requesting coordination. How is that

possible?possible?

A. Your comments on the current CR/C will be A. Your comments on the current CR/C will be

considered as valid only if all provisions and all considered as valid only if all provisions and all

networks in the same IFIC are checked as “completed” networks in the same IFIC are checked as “completed”

whether your Administration is identified or not by the whether your Administration is identified or not by the

BR. BR.

Page 43: SpaceCom WRC 2005 - ITU

SpaceComSpaceCom Demo for CRCDemo for CRC

Radiocommunication Seminar 2010

DoubleDouble--click on Install_SpaceComDemo.exe setup.click on Install_SpaceComDemo.exe setup.

Use Database located in :Use Database located in :

F:F:\\WRSWRS--10_Space Workshop10_Space Workshop\\SSCSSC\\4 4

SpaceComSpaceCom\\DemoDemo\\ific2678.mdbific2678.mdb

Administration name is not lockedAdministration name is not locked

Comments files are stored in a different folder Comments files are stored in a different folder

(C:(C:\\SpaceCom_Comments_Demo) than the SpaceCom_Comments_Demo) than the

production folderproduction folder

*** Warning ****** Warning ***

Don't use it in production mode, as some features have been deactivatedDon't use it in production mode, as some features have been deactivated..