Master device: Determined by the Must be Not to be UK 8MHz channel direct connect to database; supported in used in the allocation (OFCOM) database; Transmit power Master UK but Related Slave device: no control required devices. included to document: 9 Possibly need to contacct aid Nov 2010 and database, managed Consultation and by master device FM radio bands and other bands Final rules to be identified pending Not defined as Europe 8MHz channel Determined by the Must be Optional devices with (CEPT allocation database; supported. specific (ECC)) Transmit power roles/features. 470-790 MHz Related control required document: ECC Report 159 Still in progress Canada 6MHz channel Fixed; Fixed: Max EIRP Must be To be allocation 6dBW; supported in considered (Industry Mobile: both Fixed in the Mobile: Mode I: slave and Mode II future 54-72, 76-88, device- no direct Mode I: Max devices. when Related 174-216, access to database); EIRP; 20dBm; technology document: Mode II: master Mode II: Max is mature. device- direct EIRP; 11 access to database Still in progress Singapore VHF 7MHz Will be developed Sensing devices: Required Mandatory (IDA) and UHF in future 100mW per channel; for both 8MHz channel 4dBm with adjacent analogue Related allocation channeloperated by and digital document: incumbent; broadcast IDA services; Space with N+2 VHF: between Technology channel operated by optional for 174 to 230 Information incumbent; both MHz and UHF: Package, 7 analogue between 494 to Device with only April 2010 and digital 790 MHz geolocation: 100mW wireless per channel Still in progress GDB - Geolocation Database (Sum’s comment: Up-to-date, there is no regulatory requirement in Singapore. Thus it is recommended that this field to be removed. Soo-Young’s comment: there are no fixed rules except for US so far. I tried to gather information on regulatory directions in various domains to help proposers. One of them is Singapore. So I would recommend the group to keep this row unless its contents are not in accordance with their directions.)
UK (OFCOM) Related document: 9 Nov 2010 Consultation Final rules pending 8MHz channel allocation Possibly and and FM radio bands and other bands to be identified Master device: direct connect to database; Slave device: no need to contacct database, managed by master device Determined by the database; Transmit power control required Must be supported in Master devices. Not to be used in the UK but included to aid Europe (CEPT (ECC)) Related document: ECC Report 159 Still in progress 8MHz channel allocation 470-790 MHz Not defined as devices with specific roles/features. Determined by the database; Transmit power control required Must be supported. Optional Canada (Industry Related document: Still in progress 6MHz channel allocation 54-72, 76-88, 174-216, Fixed; Mobile: Mode I: slave device- no direct access to database); Mode II: master device- direct access to database Fixed: Max EIRP 6dBW; Mobile: Mode I: Max EIRP; 20dBm; Mode II: Max EIRP; Must be supported in both Fixed and Mode II devices. To be considered in the future when technology is mature. Singapore (IDA) Related document: IDA Space Technology Information Package, 7 April 2010 Still in progress VHF 7MHz and UHF 8MHz channel allocation VHF: between 174 to 230 MHz and UHF: between 494 to 790 MHz Will be developed in future Sensing devices: 100mW per channel; 4dBm with adjacent channeloperated by incumbent; with N+2 channel operated by incumbent; Device with only geolocation: 100mW per channel Required Mandatory for both analogue and digital broadcast services; optional for both analogue and digital wireless GDB - Geolocation Database (Sum’s comment: Up-to-date, there is no regulatory requirement in Singapore. Thus it is recommended that this field to be removed. Soo-Young’s comment: there are no fixed rules except for US so far. I tried to gather information on regulatory directions in various domains to help proposers. One of them is Singapore. So I would recommend the group to keep this row unless its contents are not in accordance with their directions.) 11
15-11-0684-06-004m-tg4m-technical-guidance-document.docx