Comments by Administrations using Spacecom Software - presented by Hon Fai Ng, International Telecommunication Union

1. © ITU
Comments
by Administrations using SpaceCom
International Telecommunication Union
Efficient use of the spectrum / orbit resource workshop, Cyprus 2014
Hon Fai Ng
Space Services Department

2. © ITU
A
API
C
Coordination
N
Notification
Start of regulatory
clock
Negotiate for
interference free
operation
Record in MIFR
(International
Recognition)
& BIU
Non-planned Procedures (Articles 9 & 11)
Source: Articles 9 and 11 of Radio Regulations

3. © ITU
C
Coordination
CR/C Publication
in BR IFIC DVD
Source: Article 9 of Radio Regulations

4. © ITU
CR/C Publication
in BR IFIC DVD
Source: Article 9 of Radio Regulations

5. © ITU

6. © ITU
Comment
to be included in
coordination process
Nos. 9.11, 9.11A, 9.21,
9.7, 9.7A, 9.7B
Source: Nos. 9.52, 9.52C, 9.41, 9.43, 9.48, 9.49 of Article 9 of Radio Regulations

7. © ITU
No. 9.7, 9.7A, 9.7B
Nos. 9.11, 9.11A, 9.21

8. © ITU
Comment within
4 MONTHS
of CR/C date of publication (Nos. 9.52C, 9.43)
Else regarded as unaffected,
cannot claim protection or cause harmful
interference (Nos. 9.48, 9.49)
Source: No. 9.43, 9.52C of Article 9 of Radio Regulations

9. © ITU
Comments
submission under No. 9.52
(Nos. 9.11, 9.11A, 9.21)

10. © ITU
9.52
If an administration, following its action under No. 9.50, does not
agree to the request for coordination, it shall, within four months of
the date of publication of the BR IFIC under No. 9.38, or of the date
of dispatch of the coordination data under No. 9.29, inform the
requesting administration of its disagreement and shall provide
information concerning its own assignments upon which that
disagreement is based. It shall also make such suggestions as it is
able to offer with a view to satisfactory resolution of the matter. A
copy of that information shall be sent to the Bureau.
9.52C
For coordination requests under Nos. 9.11 to 9.14 and 9.21, an
administration not responding under No. 9.52 within the same four-
month period shall be regarded as unaffected and, in the cases of
Nos. 9.11 to 9.14, the provisions of Nos. 9.48 and 9.49 shall apply.
Source: Nos. 9.52, 9.52C of Article 9 of Radio Regulations

11. © ITU
9.52
 Administration does not agree
 Within 4 months of CR/C
 Inform requesting administration
 Provide information on assignments
 Copy to BR
9.52C
 For Nos. 9.11, 9.11A, 9.21
 No response within 4 months
 Unaffected, Nos. 9.48 and 9.49 apply
Source: Nos. 9.52, 9.52C of Article 9 of Radio Regulations

12. © ITU
Nos. 9.11, 9.11A, 9.21

13. © ITU
Deadline for comments
Notifying Administration GSO Satellite

14. © ITU
Summary of applicable
forms of coordination

15. © ITU
Article 5 of Radio Regulations
Table of Frequency Allocation
9.11A applies
9.21 applies
Rules of Procedures
Table 9.11A-1
Source: Articles 5, 9 of Radio Regulations, Rules of Procedures on No. 9.11A
Article 9 of Radio Regulations

16. © ITU
GSO Satellites
Terrestrial
Non-GSO
Satellites
Forms of
coordination
9.13
9.21/B
9.11
9.14
9.21/C
9.21/A
Incoming network
(Network requesting
coordination)

17. © ITU
Bureau identifies
Forms of coordination
List of potentially affected administrations
For information only
(Nos. 9.36, 9.36.1)

18. © ITU
BSS GSO vs
Terrestrial Services
Territories with PFD threshold
exceeded
or
Recorded terrestrial stations with
frequency overlap and visible

19. © ITU
GSO vs NGSO NGSO with frequency overlap

20. © ITU
Territories with PFD threshold
exceeded
or
Recorded terrestrial stations with
frequency overlap and visible
GSO vs Terrestrial
Services

21. © ITU
GSO Satellites
Terrestrial
Non-GSO
Satellites
Forms of
coordination
Incoming network
(Network requesting
coordination)

22. © ITU
GSO Satellites
Terrestrial
Non-GSO
Satellites
9.12
9.21/B
Forms of
coordination
9.12A
9.21/A
9.11
9.14
9.21/C
Incoming network
(Network requesting
coordination)

23. © ITU
Overall Process
CR/C to Draft CR/D to CR/D

24. © ITU
CR/C
Potentially affected administrations
need to comment within 4 months
to be in coordination process with respect to
Nos. 9.11, 9.11A, 9.21
All Administrations
Examine with regards to
interference (No. 9.50)
Inform requesting Administration
and BR of disagreement (No. 9.52)
If no response within 4 months,
Administrations regarded as
unaffected with respect to Nos.
9.11, 9.11A, 9.21 (No. 9.52C)

25. © ITU
Draft
CR/D
Bureau
Collects and merges all comments,
publishes draft CR/D in BR IFIC
DVD
Notifying Administration
Verifies draft CR/D

26. © ITU
Bureau
Publishes CR/D Special Section in
BR IFIC (No. 9.53A)
CR/D

27. © ITU
HOW TO COMMENT?On CR/C Special Section with respect to Nos. 9.11, 9.11A, 9.21
Send to Bureau
Electronic submission with SpaceCom software
Send to Notifying Administration
Letter with comments/objections
Source: No. 9.52 of Article 9, resolves 4 of Resolution 55 of Radio Regulations

28. © ITU
Possible
Scenarios
Yes
No
Include
Exclude/
No reply
Include
with
reason

29. © ITU
Satellite
1
Each network
Satellite
2
Satellite
n
Group
2
Group
n
Each group
9.11
9.13
9.14
9.21A
9.21B
9.21C
Group
1
Repeat for all networks, all groups, all
provisions at every BR IFIC
Each provision
Yes
No
Include
Exclude/
No reply
Include
with
reason

30. © ITU
SpaceCom
Manages comments and objections with
respect to Nos. 9.11, 9.11A, 9.21
Electronic submission is mandatory
Source: Resolves 4 of Resolution 55 (Rev. WRC-12) of Radio Regulations

31. © ITU
SAM
Space Applications Manager
Click to run
SpaceCom

32. © ITU
Select CR/C
to comment on a
CR/C publication

33. © ITU
WHO ARE YOU?
Notifying administration
To validate draft CR/D
Potentially affected administration
To comment

34. © ITU
CR/C
WHO ARE YOU?
Notifying administration
To validate draft CR/D
Potentially affected administration
To comment

35. © ITU
Select Potentially
Affected
Administration
(if administration, leave
operator blank)
Potentially affected administration
To comment

36. © ITU
Enter BR IFIC
number1
Potentially affected administration
To comment
Locate IFIC.mdb
in BR IFIC DVD
Get list of CR/Cs
to comment
2
3
1
2
3
a Your administration
a

37. © ITU
Enter BR IFIC
number
Potentially affected administration
To comment
Locate IFIC.mdb
in BR IFIC DVD
Get list of CR/Cs
to comment
Click on a row to
select a CR/C
5
1
2
3
4
a Your administration b
List relevant CR/Cs in BR IFIC with
coordination under Nos. 9.11,
9.11A, 9.21
b
4
Click to comment
on selected CR/C
5

38. © ITU
1
2
Potentially affected administration
To comment
a Your administration
identified by BR
a
Select provision to
comment
1
2
Manually include
in coordination
process

39. © ITU
2
Potentially affected administration
To comment
a Your administration
identified by BR
Select provision to
comment
1
2
Manually include
in coordination
process

40. © ITU
Select provision to
comment
1
Automatically
include in
coordination
process (all
groups with your
administration
identified)
2
Manually include
in coordination
process
2’2’
3 Click when
comments are
completed
3
Potentially affected administration
To comment
a Your administration
identified by BR
4
Go to main page
to select another
CR/C
4

41. © ITU
Click on a row to
select a CR/C
1
Click to comment
on selected CR/C
2
1
2
Potentially affected administration
To comment

42. © ITU
Potentially affected administration
To comment
a
Your administration not
identified by BR
1
1
b
Auto-include does not work,
since your administration not
identified
b
a
a
If not identified,
can manually
include in
coordination
process
(justification
required)
Select check box,
then fill up pop-up
window
Pop-up window depends on
Coordination with respect to
Space Services (GSO/NGSO) or
Terrestrial Services
c
c

43. © ITU
Potentially affected administration
To comment
1
Enter satellite
network name
1
2
BR did not find
any network with
frequency overlap,
justification
required for
inclusion
2
With space services
Nos. 9.12, 9.12A, 9.13,
9.21/A, 9.21/B

44. © ITU
Potentially affected administration
To comment
1
Select
geographical area
2
Select terrestrial
services affected
With terrestrial
services
Nos. 9.11, 9.14, 9.21/C
(PFD threshold)
1
2
3
BR did not find
PFD excess over
your territory,
justification
required for
inclusion
3

45. © ITU
Potentially affected administration
To comment
1
BR did not find
any recorded
terrestrial station
with frequency
overlap and visible
Select
geographical area
With terrestrial
services
Nos. 9.11, 9.14, 9.21/C
(no PFD threshold)
1

46. © ITU
1 Click when
comments are
completed for all
provisions and
groups
Potentially affected administration
To comment
2 Go to main page
1
2

47. © ITU
1 Repeat process
for all CR/Cs until
comments are
completed
Potentially affected administration
To comment
3
Click Import to
multiple comments
databases
(if needed)
1
3
2 Auto complete
CR/Cs where your
administration not
identified
2

48. © ITU
Potentially affected administration
To comment
Merge comments
within an operator
Merge comments
from multiple
operators within an
administration
1 Click
Validate/Send to
send comments to
BR
1

49. © ITU
Potentially affected administration
To comment
1
Enter BR IFIC
number
Locate comments
database on local
drive
Validate if
comments
completed
Create an email
with comments
database attached
Send to
brmail@itu.int
1
2
3
4
2
3
4
a
If operator,
send to Administration b
If Administration,
send to BR
a
b
c
c
Date of receipt of database by BR
within 4 months of CR/C to be valid

50. © ITU
CR/C
WHO ARE YOU?
Notifying administration
To validate draft CR/D
Potentially affected administration
To comment

51. © ITU
WHO ARE YOU?Potentially affected administration
To comment
Draft
CR/D
Notifying administration
To validate draft CR/D

52. © ITU
Notifying administration
To validate draft CR/D
After 4-month period expires, all
comments are merged and validated
by BR
DRAFT CR/D
is published in a
subsequent BR IFIC DVD
(~1 month) to be validated by
notifying administration

53. © ITU
Click to run
SpaceCom
Notifying administration
To validate draft CR/D

54. © ITU
Select CR/C
to validate a draft
CR/D publication
Notifying administration
To validate draft CR/D

55. © ITU
Select Notifying
Administration
Notifying administration
To validate draft CR/D

56. © ITU
Notifying administration
To validate draft CR/D
1
Select BR IFIC
DVD drive
2
Select your
network (in red) to
validate
1
2
b
Other Administrations
can view c
Notifying Administration
can validate
cb
3
Click validate to
proceed
3
a
List of Draft CR/Ds in
BR IFIC DVD
a

57. © ITU
Notifying administration
To validate draft CR/D
1
Click on row to
review each
provision
1
2
Check comments
and add
Administrations, if
missing
2
3 Click when
validation is
completed
3
4 Go to main page
4
a
Notifying administration can input comments not received by BR or
after 4-month period
Copy of reason from potentially affected administration must be
sent to BR
a

58. © ITU
Notifying administration
To validate draft CR/D
1
Repeat process to
validate all draft
CR/Ds
for which you are
the notifying
administration
1
a
Take note of BR IFIC number (not the current BR IFIC DVD)
Draft CR/D related to CR/C which was published in previous
BR IFIC
a
2 Click Send
2

59. © ITU
Notifying administration
To validate draft CR/D
1
Enter BR IFIC
number (see
previous slide)
Locate validated
database on local
drive
Validate
Create an email
with validated
database attached
Send to
brmail@itu.int
1
2
3
4
2
3
4

60. © ITU
Notifying administration
To validate draft CR/D
BR receives validated draft CR/Ds
from notifying administration or if no
response
DRAFT CR/D
is published in a
subsequent BR IFIC DVD
SRS is updated and corresponding
coordination requirements under
Nos. 9.11, 9.11A, 9.21 in CR/C
replaced
Source: No. 9.53A of Article 9 of Radio Regulations

61. © ITU
CR/D
Corresponding
CR/C

62. © ITU
Administrations included
in coordination process
under No. 9.52 (Nos. 9.11,
9.11A, 9.21)

63. © ITU
CR/D
Final coordination requirements
CR/C
Published previously, for information only

64. © ITU
CR/C
CR/C
Mandatory coordination requirements
9.7, Ap30#7.1, Ap30A#7.1
CR/C
For information only
9.11, 9.11A, 9.21

65. © ITU
CR/C
CR/C
Mandatory coordination requirements
9.7, Ap30#7.1, Ap30A#7.1
CR/D
Final coordination requirements
9.11, 9.11A, 9.21

66. © ITU
Comments
submission under No. 9.41

67. © ITU
9.41
Following receipt of the BR IFIC referring to requests for
coordination under Nos. 9.7 to 9.7B, an administration believing that
it, or any of its satellite networks not identified under No. 9.36.2,
should have been included in the request, or the initiating
administration believing that an administration, or any of the satellite
networks identified under No. 9.36.2, in accordance with the
provisions of No. 9.7 (GSO/GSO) (items 1) to 8) of the frequency
band column), No. 9.7A (GSO earth station/non-GSO system) or
No. 9.7B (non-GSO system/GSO earth station) of Table 5-1 of
Appendix 5 should not have been included in the request, shall,
within four months of the date of publication of the relevant BR IFIC,
inform the initiating administration or the identified administration,
as appropriate, and the Bureau, giving its technical reasons for
doing so, and shall request that its name, or the name of any of its
satellite networks not identified under No. 9.36.2, be included, or
that the name of the identified administration, or any of its satellite
networks identified under No. 9.36.2, be excluded, as appropriate.
(WRC-12)
Source: Nos. 9.41, 9.43 of Article 9 of Radio Regulations

68. © ITU
9.41
 For Nos.
 9.7 (Coordination Arc)
 9.7A (GSO ES/non-GSO system)
 9.7B (non-GSO system/GSO ES)
 If an administration/network should be included or identified
administration/network should be excluded
 Within four months of CR/C
 Inform relevant administration and BR
 Give technical reasons
9.43
 No response under No. 9.41 within 4 months
 Unaffected, Nos. 9.48 and 9.49 apply
Source: Nos. 9.41, 9.43 of Article 9 of Radio Regulations

69. © ITU
GSO Satellites
Coordination Arc
Incoming network
(Network requesting
coordination)
No. 9.41 applicable
in frequency bands and services
where coordination arc applies
Coordination Arc
Table 5-1 of Appendix 5
C, Ku, Ka-bands and above
FSS, BSS, MetSat and associated Space Operations
(No. 9.41 not applicable to BSS 21.4 – 22 GHz)
Frequency overlap
Same direction of transmission
Orbital separation of 8°, 7°, 16°

70. © ITU
GSO Satellites
9.41/9.7
Incoming network
(Network requesting
coordination)
Outside coordination arc
Not identified under No. 9.7 (CA)
Potential to be included if conditions
are met (e.g. DT/T > 6%)
Coordination Arc

71. © ITU
Coordination Arc
Incoming network
(Network requesting
coordination)
GSO Satellites

72. © ITU
Coordination Arc
Incoming network
(Network requesting
coordination)
Inside coordination arc
Identified under No. 9.7 (CA)
Potential to be excluded if conditions
are met (e.g. DT/T ≤ 6%)
GSO Satellites

73. © ITU
GSO Satellites
Specific
Earth Station
Non-GSO
Satellites
9.7B
NGSO FSS vs specific
earth station
Criteria
Table 5-1 of Appendix 5
Certain Ku, Ka-bands (space-to-Earth) FSS
Frequency overlap
G/T ≥ 44 dB/K
ES gain ≥ 64 dBi (Ku), 68 dBi (Ka)
BW = 250 MHz (Ku), 800 MHz (Ka)
Exceeds EPFD limit (not applicable since no
software, see Res 85)
9.7A
Specific earth station vs
NGSO FSS

74. © ITU
No. 9.7, 9.7A, 9.7B

75. © ITU
Deadline for comments
Notifying Administration Incoming network ID

76. © ITU
Bureau identifies
Potentially affected administrations and
satellite networks
(Nos. 9.36, 9.36.2)
Additional potentially affected
administrations and satellite networks
can be included ? (No. 9.41)
Identified affected administrations and
satellite networks can be excluded ?
(No. 9.41)

77. © ITU
Identified under Coordination Arc
Assignments subject to Coordination Arc, No. 9.41 applicable
Your administration
identified for all groups?

78. © ITU
Networks identified under Coordination
Arc, can be excluded ?
Any networks not
identified that could
be included?

79. © ITU
CONDITIONS
for a valid No. 9.41 request
Administration Request Type Coordination
Arc Applicable
Request
received
DT/T
Sample
DT/T
Potentially
Affected
Inclusion of
networks outside CA
Yes
Within 4 months
of CR/C
Publication
One pair of
assignments
provided
> 6 %
Source: No. 9.41 of Article 9 of Radio Regulations, Rules of Procedures on No. 9.41, CR/322 of 25.01.2011

80. © ITU
CONDITIONS
for a valid No. 9.41 request
Administration Request Type Coordination
Arc Applicable
Request
received
DT/T
Sample
DT/T
Potentially
Affected
Inclusion of
networks outside CA
Yes
Within 4 months
of CR/C
Publication
One pair of
assignments
provided
> 6 %
Notifying
Exclusion of
networks within CA
≤ 6 %
Source: No. 9.41 of Article 9 of Radio Regulations, Rules of Procedures on No. 9.41, CR/322 of 25.01.2011

81. © ITU
SAM
Space Applications Manager
Click to run
GIBC

82. © ITU
Enter incoming
network ID
Enter your
Administration
symbol
Click Start
2
4
5
Select Check
Against Existing
3
2
3 4
5
a Path to results folder
Select Appendix
8 tab
1 1
a

83. © ITU
a Path to results folder
Appendix 8 List
Results in Group Level
Published in CR/C
Network List
List of affected networks
Published in CR/C

84. © ITU
a Path to results folder
Appendix 8 Optional List
DT/T samples for groups under CA
Network Optional List
List of affected networks
identified by DT/T

85. © ITU
Appendix 8 Optional List
DT/T samples for groups under CA
Sample DT/T

86. © ITU
Network Optional List
List of affected networks
identified by DT/T
DT/T

87. © ITU
CR/C
List of Affected Networks
NTW_OPT.LST
List of Affected Networks
Network not identified by BR
DT/T > 6%, request for
inclusion under No. 9.41

88. © ITU
APP8_OPT.LST
Sample DT/T
NTW_OPT.LST
List of Affected Networks
Network not identified by BR
DT/T > 6%, request for
inclusion under No. 9.41

89. © ITU
Overall Process
CR/C to CR/E

90. © ITU
CR/C
Administrations can request for
inclusion within 4 months and
with reason (No. 9.41)
If no response within 4 months,
Administrations not identified under
No. 9.7 regarded as unaffected
(No. 9.43)

91. © ITU
CR/C
Notifying Administration can
request for exclusion within 4
months and with reason (No. 9.41)

92. © ITU
Bureau
Collects and merges all comments
Publishes CR/E Special Section for
requests for inclusion (No. 9.42)
Publishes CR/C MOD Special
Section for requests for exclusion
(No. 9.42, CR/322)
CR/E

93. © ITU
HOW TO COMMENT?On CR/C Special Section with respect to No. 9.41
Send to Bureau
Electronic submission with SpaceCom software
Send to notifying administration (inclusion)
Letter to inform inclusion with technical reason
Send to identified administration (exclusion)
Letter to inform exclusion with technical reason
Source: No. 9.41 of Article 9, resolves 5 of Resolution 55 of Radio Regulations

94. © ITU
SpaceCom
Manages inclusion or exclusion with
respect to No. 9.41
Electronic submission is mandatory
Source: Resolves 5 of Resolution 55 (Rev. WRC-12) of Radio Regulations

95. © ITU
SAM
Space Applications Manager
Click to run
SpaceCom

96. © ITU
Select 9.41
Request
to include/exclude
under No. 9.41

97. © ITU
WHO ARE YOU?
Notifying administration
To exclude
Potentially affected administration
To include

98. © ITU
CR/C
WHO ARE YOU?
Notifying administration
To exclude
Potentially affected administration
To include

99. © ITU
Select Potentially
Affected
Administration
(if administration, leave
operator blank)
Potentially affected administration
To include

100. © ITU
Enter BR IFIC
number1
Potentially affected administration
To include
Locate IFIC.mdb
in BR IFIC DVD
Get list of CR/Cs
to comment
Click on a row to
select a CR/C
2
3
5
1
2
3
4
a Your administration b
List relevant CR/Cs in BR
IFIC with coordination
under No. 9.7 with CA
c
Auto complete CR/Cs
where your administration
does not request inclusion
a
b
c
4
Click to comment
on selected CR/C
5

101. © ITU
Select your
networks for
inclusion
Potentially affected administration
To include
Add reason for
inclusion or
attachment
reference, not
DT/T calculations
Click when
comments
completed
Go to main page
to select another
CR/C
1
2
3
4
1
2
3
4

102. © ITU
Potentially affected administration
To include
1 Repeat process
for all CR/Cs until
comments are
completed
1
2
If no further
inclusion, click on
auto complete
2

103. © ITU
Potentially affected administration
To include
1 Repeat process
for all CR/Cs until
comments are
completed
2
If no further
inclusion, click on
auto complete
2

104. © ITU
Potentially affected administration
To include
1 Repeat process
for all CR/Cs until
comments are
completed
3
Click Import to
merge multiple
comments
databases
(if needed)
2
If no further
inclusion, click on
auto complete
3

105. © ITU
Merge comments
within an operator
Merge comments
from multiple
operators within an
administration
1 Click
Validate/Send to
send comments to
BR
1
Potentially affected administration
To include

106. © ITU
Potentially affected administration
To include
1
Enter BR IFIC
number
Locate comments
database on local
drive
Validate if
comments
completed
Attach file with
sample DT/T > 6%
calculations for
each network
included
1
2
3
4
2
3
4
b
If operator, send to
Administration
If Administration, send to BR
c
b
c
Create an email
with comments
database & DT/T
attached
Send to
brmail@itu.int
5
5
a
APP8_OPT.LST file
could be attached
a
Date of receipt of database by BR
within 4 months of CR/C to be valid

107. © ITU
CR/C
WHO ARE YOU?
Notifying administration
To exclude
Potentially affected administration
To include

108. © ITU
WHO ARE YOU?Potentially affected administration
To include
Notifying administration
To exclude
CR/C

109. © ITU
Select Notifying
Administration
Notifying administration
To exclude

110. © ITU
Enter BR IFIC
number1
Notifying administration
To exclude
Locate IFIC.mdb
in BR IFIC DVD
Get list of CR/Cs
to comment
Click on a row to
select a CR/C
2
3
5
1
2
3
4
a Your administration b
List relevant CR/Cs of your
administration in BR IFIC with
coordination under No. 9.7 with CA
c
Auto complete CR/Cs
where your administration
do not request exclusion
a
b
c
4
Click to comment
on selected CR/C
5

111. © ITU
Enter networks for
exclusion
Add reason for
exclusion or
attachment
reference, not
DT/T calculations
Click when
comments
completed
Go to main page
to select another
CR/C
1
2
3
4
1
2
3
4
Notifying administration
To exclude

112. © ITU
1 Repeat process
for all CR/Cs until
comments are
completed
1
2
If no further
exclusion, click on
auto complete
2
Notifying administration
To exclude
3 Click
Validate/Send to
send comments to
BR
3

113. © ITU
1
Enter BR IFIC
number
Locate comments
database on local
drive
Validate if
comments
completed
Attach file with
sample DT/T ≤ 6%
calculations for
each network
included
1
2
3
4
2
3
4
a
Create an email
with comments
database & DT/T
attached
Send to
brmail@itu.int
5
5
Notifying administration
To exclude
a
Date of receipt of database by BR
within 4 months of CR/C to be valid

114. © ITU
After 4-month period expires, all
comments are merged and validated
by BR
For inclusion,
CR/E
is published in a
subsequent BR IFIC DVD
For exclusions,
CR/C MOD
is published in a
subsequent BR IFIC DVD
SRS is updated
Source: No. 9.42 of Article 9 of Radio Regulations

115. © ITU
CR/E
Corresponding
CR/C

116. © ITU
Administrations included
in coordination process
under No. 9.41/9.7

117. © ITU
Administrations
requested inclusion
under No. 9.41
Invalid - No DT/T
calculations
Invalid - No longer
exist or DT/T ≤ 6%

118. © ITU
Details on a group level,
list of administrations
newly added under No.
9.41/9.7

119. © ITU
List of networks newly
included under No. 9.41/9.7

120. © ITU
CR/C
CR/C
Mandatory coordination requirements
9.7
CR/E
Additional coordination requirements
9.41/9.7

121. © ITU
FINAL POINTS
 Use Spacecom to comment and be
included in coordination process
(Nos. 9.11, 9.11A, 9.21, 9.41)
 4 month deadline from CR/C
Publication
 No response means unaffected
(Nos. 9.52C, 9.43, 9.48, 9.49)

122. © ITU
Comments
by Administrations using SpaceCom
International Telecommunication Union
Efficient use of the spectrum / orbit resource workshop, Cyprus 2014
Hon Fai Ng
Space Services Department