hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.1 Wireless USB | |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.1.1 Certified Wireless USB (CWUSB) | Certified Wireless USB (CWUSB), from the USB Implementers Forum [i.7], is a new short-ranged high-bandwidth wireless extension to USB intended to combine the speed and security of wired technology with the ease-of-use of wireless technology. CWUSB is based on Ultra-WideBand (UWB) wireless technology defined by WiMedia ... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.1.2 CWUSB Technical Specification and Architecture | CWUSB specification does not support the use of hubs. Although a CWUSB host supports the architectural limit of 127 devices. A new Wire Adapter device class has been defined. Also known as a Host Wire Adapter; it acts as a host for a CWUSB system and provides a way to upgrade an existing PC to have CWUSB. In addition, ... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.1.3 Versions and Data Rates | CWUSB is capable of sending 480 Mbit/s at distances up to 3 meters, and 110 Mbit/s at up to 10 meters. It operates in the 3,1 GHz to 10,6 GHz band-range and spreads communication over an ultra-wideband of frequencies. NOTE: There is also another wireless technology developed by Cypress Semiconductor [i.9] which is desi... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.1.4 UWB Noise | Due to the low power and spread-spectrum nature of the signal, an UWB receiver operating within the ISM band should see (at worst) a slight rising of the noise background. For example, in the US the radiated power is regulated by FCC where the specification relates to a spread-spectrum signal. The power limit is define... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.2 Bluetooth® | Bluetooth® [i.10] is a radio standard and communication protocol primarily designed for low power consumption, with a short range based around low-cost transceiver microchips in each device. Bluetooth® allows these devices to communicate with each other when they are in range. The devices use a radio communication syst... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.2.1 Technical Specification and Features | Bluetooth® systems operate in the unlicensed Industrial-Scientific-Medical (ISM) radio band at 2,4 GHz. Low-power RF transmission provides communication between devices over a range of 10 meters to 100 meters. A Bluetooth® device playing the role of the "master" can communicate with up to 7 devices playing the role of ... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.2.2 Versions, Features and Data Rates | Bluetooth® 1.1 • Many errors found in the 1.0B specifications were fixed. • Added support for non-encrypted channels. • Received Signal Strength Indicator. • The general or basic rate modulation is GFSK. Data is transmitted using one bit per symbol at a data rate of 1 Mbit/s. Bluetooth® 1.2 This version is backwards co... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.3 Infrared Data Association | The Infrared Data Association (IrDA) [i.11] defines physical specifications communications protocol standards for the short range exchange of data over infrared light, for uses such as personal area networks. IrDA is a very short-range example of free-space optical communication. ETSI ETSI TR 102 021-9 V1.2.1 (2010-12)... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.3.1 Technical Specification and Features | The mandatory Infrared Physical Layer Specification (IrPHY) is the lowest layer of the IrDA specifications. IrDA transceivers communicate with infrared pulses in a cone that extends minimum 15 degrees half angle off centre. The IrDA physical specifications require that a minimum irradiance (Radiant power incident per u... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.3.2 Versions, Features and Data Rates | Transmission rates fall into three broad categories: SIR, MIR, and FIR. Serial Infrared (SIR) speeds cover those transmission speeds normally supported by an TIA/EIA-232 [i.17] port (9 600 bit/s, 19,2 kbit/s, 38,4 kbit/s, 57,6 kbit/s and 115,2 kbit/s). Since the lowest common denominator for all devices is 9 600 bit/s,... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.4 Comparisons between Wireless Solutions | |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.4.1 Support of High Data Rates | USB, USB OTG and Bluetooth® support maximum transmission rate required by TETRA Release 2 technology. However, IrDA supports lower transmission speeds and it would be a useful technology for transmission of small files such as text. ETSI ETSI TR 102 021-9 V1.2.1 (2010-12) 23 |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.4.2 Data Reliability | In the absence of interference, the Bit Error Rate (BER) for Bluetooth® system is almost negligible for the transmitter powers and ranges under consideration. In other words, the signal-to-noise-ratio (SNR) is high enough so that the BER is less than 10-5. When there is interference from the other system, this factor i... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.4.3 Power Efficiency | Underlying, the technology of Wireless USB is UWB. Because UWB transmits energy over such a wide spectrum, it should transmit at very low power to avoid interfering with numerous other wireless applications. In the US, the FCC has specified a maximum transmit power density of -41 dBm/MHz; essentially the level of elect... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.4.4 Robustness | As the wireless devices are not connected using cables, connections between peripheral equipments and TETRA mobiles would be more robust in harsh conditions and emergency cases where the users are on the move (in comparison with the wired solutions). However the receiver and transmitter should be kept within the range;... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.4.5 Ease-of-Use | Wireless USB and Bluetooth® are very easy to use. The only consideration is to keep transmitter and receiver within their effective communication range. Establishing a stable connection is more difficult in the case of IrDA, where the transmitter and receiver should face each other in a restricted space. ETSI ETSI TR 1... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 6.4.7 Security | Wireless USB Wireless implementations of USB are wire-replacement technologies, where it provides two security services [i.7]: 1) it connects the nodes the owner/user specifically wants connected; 2) it protects all data in transit from casual observation or malicious modification by external agents. The goal of USB Se... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 7 Background Conclusions | |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 7.1 Comparison of technologies | In this report, different aspects of wired and wireless communication links that were initially considered suitable to be recommended as a physical link for the PEI of the TETRA Release 2 are presented. To summarize this study and provide a recommendation, tables 7.1 and 7.2 assess both wired and wireless solutions. Le... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 7.1.1 Summary of table 7.1 | USB OTG is recommended as the best candidate. Considerations: • Firewire and TIA/EIA-485 [i.18] would be a better choice in cases where the peripheral equipments need to be connected using long cables (> 5 m). • Firewire, E TIA/EIA-485 [i.18], USB and USB OTG all provide data rates required by TETRA Release 2. ETSI ETS... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 7.1.2 Summary of table 7.2 | Considerations: • Based on the specifications CWUSB and WUSB would outperform the Bluetooth® 2.1 (2007) however CWUSB and WUSB are not really successfull in the market (2010). • IrDA is recommended to be considered as a physical link option only if compatibility with legacy peripheral equipments. 8 User Requirements fo... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.1 Introduction | The enhancements of the TETRA Peripheral Equipment Interface standard aim at: • Providing a state-of-the-art point-to-point physical link. • Providing Multimedia capability. • Providing QoS negotiation. The following clauses state user requirements for these enhancements. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.2 Physical Link | The PEI physical link for TETRA 2 should support the following as standard: • Multiplexing of multiple communication paths down one physical link. NOTE: This does not stop an MT from implementing more than one instance of the PEI physical link. • Support the speeds of TETRA 2 TEDS. • Should support secure data communic... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.2.1 USB | The TETRA PEI on terminals should support a USB interface. The electrical USB interface should enable to connect the TETRA MS directly (without extra electrical interfaces) to existing PCs, PDAs. The use of USB in an MT implemented according to the TETRA 2 PEI standard should support the ability to be either a function... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.2.2 Bluetooth® | The TETRA PEI should support Bluetooth®. The Bluetooth® interface should enable to connect the TETRA MS directly (without extra electrical interfaces) to existing PCs, PDAs. The Bluetooth® interface needs to support secure pairing. A Bluetooth® interface needs to support Bluetooth® 2.0 or later. A Bluetooth® interface ... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.2.3 Wireless USB | Wireless USB should be considered for the TETRA PEI. The Wireless USB should support secure associations and pairing of devices, and support all the facilities of the wired USB interface. A Wireless USB interface if implemented should meet the requirements of the relevant national technical agencies for security if use... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.3 Multimedia capability | The PEI for TETRA 2 should allow multi-media connections to be set-up through it in either direction. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.4 QoS negotiation | The TETRA 2 PEI should support the ability to negotiate and maintain a quality of service across the PEI link between TE and MT. NOTE: This does not prevent the PEI from supporting end-to-end quality of service negotiation and maintenance. The TETRA 2 PEI should allow IETF methods of traffic QoS marking to be supported... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.5 Circuit mode data, SDS, and STATUS messaging | The TETRA 2 PEI should support circuit mode data and packet data. The TETRA 2 PEI should allow SDS and STATUS messaging concurrently with with an active packet data session, e.g. PPP link. ETSI ETSI TR 102 021-9 V1.2.1 (2010-12) 29 |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.6 Multiple services on PEI | The PEI for TETRA 2 should support as standard the ability to run multiple virtual connections multiplexed on to a single physical link instance. NOTE: This does not prevent a mobile station from supporting more than one instance of the PEI physical link. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.7 Mobile device charger standard | The Micro-USB interface is the new standard charger for mobile phones. In September 2007, the Open Mobile Terminal Platform group announced that its members had agreed on micro-USB as the future common connector for mobile devices. On 17 February 2009, the GSM Association announced that they had agreed on a standard ch... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.8 Multiple applications | The TETRA 2 PEI should support the ability for multiple applications to be hosted on a TE. The MT should support steering of data to the correct application in the TE in some way, e.g. through the support of IETF port numbers for UDP and TCP and software such as portmappers. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.9 Embedded systems | The TETRA2 PEI should be capable of efficient implementation in embedded systems, which are often characterized by finite memory and processor capacity. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.10 Legacy applications support (TETRA and GSM) | The TETRA 2 PEI should be backward compatible with the TETRA 1 PEI, in terms of: • Supporting the same mandatory ITU-T Recommendation V.250 [i.13] commands and extensions as in EN 300 392-5 [i.14]. • Supporting the ability for existing TETRA applications to work unchanged at OSI-RM layer 3 and above. • Supporting the a... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.11 Standardized complete support similar by all manufacturers | The TETRA 2 PEI should be implemented by all manufacturers in a complete way. ETSI ETSI TR 102 021-9 V1.2.1 (2010-12) 30 |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.12 Interoperable | The TETRA 2 PEI should support the concept of the open standard and open market such that applications designed to work according the TETRA 2 PEI should be able to work with MT from more than one manufacturer. NOTE 1: Using existing published standards should help in meeting this requirement. NOTE 2: The TETRA Associat... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.13 Developing a driver from scratch | The definition of the TETRA 2 PEI standard should help manufacturers of MT and applications in developing the necessary software to implement the standard on the operating system of their choice. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.14 Multiple platforms | The TETRA 2 PEI standard should be defined in detail such that: • Manufacturers of applications and MT can implement the standard on the operating system of their choice. • Manufacturers can implement the standard on both big-endian and little-endian microprocessor based devices. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.15 Ease of application developers | The TETRA 2 PEI should be defined in a clear and unambiguous manner and in sufficient detail that it is clear for application developers to implement and know which features are mandatory for compliance with the standard. NOTE: The use of formal notation such as ASN-1 should be considered to assist in meeting this requ... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.16 Terminal management | Terminal management functionality should be as a minimum: • The application can be informed of the terminals status on the system, namely: registration, details broadcast from the network, cell service level information and the current signal strength. • The application can check aspects of the terminal through the PEI... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.17 Minimum cost | The TETRA 2 PEI standard should be designed such that the resources required to implement it are minimized. NOTE: The re-use of existing published standards from other bodies should assist in meeting this requirement. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.18 Time to market | The TETRA 2 PEI standard should be designed such that it facilitates rapid time to market. NOTE: The re-use of existing published standards from other bodies should assist in meeting this requirement. ETSI ETSI TR 102 021-9 V1.2.1 (2010-12) 31 |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.19 Open source driver layers | The TETRA 2 PEI standard should be defined such that existence of open source software drivers is considered. NOTE 1: The existence of open source drivers under licences such as GPL should be used as a consideration in meeting this requirement. NOTE 2: The licensing on FRAND terms of drivers in source code to applicati... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.20 Freely available drivers | The TETRA 2 PEI standard should be designed such that it uses standards that are currently available as commercial or open source software in order to limit implementation time and expense for application or MT manufacturers. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.21 IPR licensing costs - FRAND | Any technology incorporated in the TETRA 2 PEI standard should be licensed on FRAND terms in accordance with the ETSI IPR policy. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.22 Resilient to errors on the interface | The TETRA 2 PEI should be resilient to errors on the PEI interface. Errors should be detected and indicated to applications and MTs. Applications and MT should be able to implement different classes of error correction that meets the QoS requirements of the application being implemented. NOTE: Some applications do not ... |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.23 Future upgradeability | The TETRA 2 PEI standard should use technology and standards from other bodies that have a roadmap of future enhancements. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.24 Hot-pluggable | The TETRA 2 PEI standard should support the connection and disconnection of the physical links whilst either the TE, MT or both devices are powered on. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.25 Easy to test and certify | The TETRA 2 PEI standard should be defined such that it is easy to test and certify for compliance with the standard and interoperability. NOTE: The reuse of existing standards and technology that already has certification processes and test tools available should assist in meeting this requirement. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.26 Low CPU and memory overhead | The TETRA 2 PEI standard should be defined such that it is capable of being implemented on TE and MT that have low CPU and memory capabilities. The amount of CPU and memory required to implement the TETRA 2 PEI standard should be estimated. ETSI ETSI TR 102 021-9 V1.2.1 (2010-12) 32 |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.27 Battery life concerns | The TETRA 2 PEI standard should be defined such that it can be implemented on low weight, battery powered devices. |
9cbc82c34ef7dfe5dd8ec21147303c2f | 102 021-9 | 8.28 Flow control | The TETRA 2 PEI should implement flow control in order to avoid buffer overflow conditions. NOTE 1: Buffer overflow in either the TE or MT may cause loss of data. NOTE 2: Causing deliberate buffer overflow to occur is a well known security attack technique. ETSI ETSI TR 102 021-9 V1.2.1 (2010-12) 33 Annex A: Indicative... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 1 Scope | The present document describes and enumerates various requirements on metallic (horizontal) out of band spectrum for analogue terminals connected to the PSTN. An attempt to create an envelop of the various requirements is made and a limit for an out of band spectrum requirement protecting xDSL service is proposed to fa... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 2 References | For the purposes of this Technical Report (TR), the following references apply: [1] ETSI TBR 021: "Terminal Equipment (TE); Attachment requirements for pan-European approval for connection to the analogue Public Switched Telephone Networks (PSTNs) of TE (excluding TE supporting the voice telephony service) in which net... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 3 Definitions and abbreviations | |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: dBm: Power (dBm) = 10 log (Power1 /1 mWrms) where Power1 is measured in mWrms dBV: Voltage (dBV) = 20 log (Voltage1 / 1 Vrms) where Voltage1 is measured in Vrms out of band: any unwanted emission above 4,3 kHz NOTE 1: Below 4,3 kHz app... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: PSTN Public Switched Telephone Network Rbw Resolution bandwidth TE Terminal Equipment ETSI ETSI TR 101 960 V1.2.2 (2006-01) 7 |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4 Various standards requirements | The disclosed information is simplified for comparison purpose. For more detail please refer to original document. |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.1 TBR 021 | Requirement: As described in TBR 021 [1], clause 4.7.3.4 the total voltage level in a bandwidth, defined in table 4.1, wholly contained within the frequency range 4,3 kHz to 200 kHz, arising from normal operation of the TE when in an on-line, non-dialling state, and when terminated with ZR, shall not exceed the limits ... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.2 TR 103 000-2-1 | Requirement: As described in TR 103 002-2-1 [2], clause 4.3.2 the total voltage level in a bandwidth, defined in table 4.2, wholly contained within the frequency range 4,3 kHz to 200 kHz, arising from normal operation of the TE when in an on-line, non-dialling state, and when terminated with ZR, shall not exceed the li... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.3 FCC Part68 / EIA/TIA/IS-968 | Requirement: As described in [3] 68.308c the total voltage level in a bandwidth shall not exceed the limits shown in table 4.3 and figure 4.3. Table 4.3: Maximum sending level above 4 kHz Points Frequency range (kHz) Maximum sending level U in a specified bandwidth (dBV) Spectral Voltage U/√√√√B (dBV/√√√√Hz) Measuremen... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.4 AS/ACIF S002:2001 (incl. Amendment No.1) | Requirement: As described in [4], clause 5.4.2 the total voltage level in a bandwidth shall not exceed the limits shown in table 4.4.1 and figure 4.4.1 and in table 4.4.2 and figure 4.4.2. Table 4.4.1: Maximum sending level above 3,4 kHz in 10 kHz bandwidth Points Frequency range (kHz) Maximum signal level P (dBm) Spec... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.5 CNC-ST2-44-01 | Requirement: As described in CNC-st2-44-01 [5], clause 4.2.3 the total voltage level in a bandwidth shall decrease as - 6 dB per Octave. |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.6 NET 001/92 | Requirement: As described in NET 001/92 [6], clause 5.6.3 the total voltage level in a bandwidth shall not exceed the limits shown in table 4.6 and figure 4.6. Table 4.6: Maximum sending level above 4 kHz Points Frequency range (kHz) Maximum sending level in an unspecified bandwidth (dBm) Measurement bandwidth Referenc... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.7 HKTA 2011 Issue2 | Requirement: As described in [7], clause 3.4 the total voltage level in a bandwidth shall not exceed the limits shown in table 4.7 and figure 4.7. Table 4.7: Maximum sending level above 4 kHz Points Center frequency in (kHz) Maximum sending level U in a specified bandwidth (dBV) Spectral Voltage U/√√√√B (dBV/√√√√Hz) Me... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.8 NO. S/INT-02W/01 | Requirement: As described in [8], clause 2.1.3.4.3.7.3 the total voltage level in a bandwidth shall not exceed the limits shown in table 4.8 and figure 4.8. Table 4.8: Maximum sending level above 3,4 kHz Points Frequency range (kHz) Maximum sending level in an unspecified bandwidth (dBm) Measurement bandwidth Reference... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.9 STEL D-001-1996 | Requirement: Not specified in [9]. |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.10 JATE 04/2001 | Requirement: As described in [10] article 14 the total voltage level in a bandwidth shall not exceed the limits shown in table 4.10 and figure 4.10. Table 4.10: Maximum sending level above 4 kHz Points Frequency range (kHz) Maximum signal level P (dBm) Spectral Power P/B (dBm/Hz) Measurement bandwidth (B) Reference imp... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.11 Art20 1998 | Requirement: As described in [11], clause 3 the total voltage level in a bandwidth shall not exceed the limits shown in table 4.11 and figure 4.11. Table 4.11: Maximum sending level above 4 kHz Points Center Frequency (kHz) Maximum sending level U in a specified bandwidth (dBV) Spectral Voltage U/√√√√B (dBV/√√√√Hz) Mea... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.12 PTC200-1997 | Requirement: As described in [12], clause 4.3 the total voltage level in a bandwidth shall not exceed the limits shown in table 4.12 and figure 4.12. Table 4.12: Maximum sending level above 4 kHz Points Frequency range (kHz) Maximum signal level P (dBm) Spectral Power P/B (dBm/Hz) Measurement bandwidth (B) Reference im... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.13 GOST 26557-85 | Requirement: As described in [13], clause 6.4.1.3 the total voltage level in a bandwidth shall not exceed the limits shown in table 4.13 and figure 4.13. Table 4.13: Maximum sending level above 3,4 kHz Points Frequency range (kHz) Maximum sending level in an unspecified bandwidth (dBm) Measurement bandwidth Reference i... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.14 IDA TS PSTN1 issue4 2000 | Requirement: As described in [14], clause 6.4.1.3 the total voltage level in a bandwidth shall not exceed the limits shown in table 4.14 and figure 4.14. Table 4.14: Maximum sending level above 3,4 kHz Points Frequency range (kHz) Maximum sending level in an unspecified bandwidth (dBm) Measurement bandwidth Reference I... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.15 TE-001 | Requirement: As described in [15], clause 14.4 the total voltage level in a bandwidth shall not exceed the limits shown in table 4.15 and figure 4.15. Table 4.15: Maximum sending level above 3,4 kHz Points Frequency range (kHz) Maximum signal level P (dBm) Spectral Power P/B (dBm/Hz) Measurement bandwidth (B) Reference... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.16 PSTN 01 | Requirement: As described in [16], clause 5.1.8 the total voltage level in a bandwidth shall not exceed the limits shown in table 4.16 and figure 4.16. Table 4.16: Maximum sending level above 4 kHz Points Frequency range (kHz) Maximum signal level P (dBm) Spectral Power P/B (dBm/Hz) Measurement bandwidth (B) Reference ... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 4.17 Estimated POTS model from TR 101 830-1 | Description: As described in [17], clause 8.1.3 the total voltage level in a bandwidth is estimated not to exceed the limits shown in table 4.17 and figure 4.17. Table 4.17: Break points of the narrow-band voltage limits Frequency (F) Impedance (Z) Signal Level (U) Power Bandwidth (B) Spectral Voltage (U/√√√√B) 30 Hz Z... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 5 Comparison attempt between 10 kHz and 10 MHz | Hypothesis: • All limits are translated into a dBm/Hz scale. • Whenever Rbw is not defined in the specification, it is supposed to be 1 kHz. NOTE: Those values are derived from formal documents but might not correspond exactly to the national applicable requirement because in some case assumption were made to overcome ... |
1cc084d1fa033f2e7e70ca1742709ebd | 101 960 | 7 Conclusion | The possibility of a common measurement method and a limit value for the frequency domain of the requirements is discussed and suggestions for future global standardization work specified. The information in the present document should be of assistance for spectrum management studies, PSTN and xDSL devices (terminals a... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 1 Scope | The present document provides information on the intended applications, the technical parameters and the radio spectrum requirements for UWB communication equipment in the frequency range from 3,1 GHz to 10,6 GHz. Additional information is given in the following Annexes: • Annex A: Detailed market information; • Annex ... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 2 References | For the purposes of the present document the following references apply: [1] CEPT/ERC Recommendation 70-03: "Relating to the use of Short Range Devices (SRD)". [2] ITU-R SG1 TG1-8 Report from the 1st meeting of ITU-R SG1 TG 1-8, Geneva 21 - 24 January 2003 (Document 1-8/047). [3] Intel Labs (J. Foerster, A. Stephens): ... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 3 Definitions and abbreviations | |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: activity factor: actual on-the-air time divided by active session time or actual on-the-air emission time within a given time window isochronous: isochronous transmission transmits asynchronous data over a synchronous data link necessa... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AC3 type of audio application CDMA Code Division Multiple Access CE Consumer Electronics CEPT European Conference of Post and Telecommunications administrations dB deciBel dBi deciBel relative to an isotropic radiator dBm deciBel relative to o... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 4 Executive summary | UWB technology holds potential for a wide variety of new Short Range Devices (SRD) for communications, measurement, imaging, surveillance and medical systems. UWB technology is typically used for transmitting short-range digital signals over a wide range of frequencies. High data rate communication with up to 500 Mbps ... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 4.1 Status of the present document | Version 1.0.0 had been approved by ERM TG31A and submitted to ERM RM # 25 for approval. Version 1.1.1_1.0.5 was the result of the revision by ERM RM#25 (green text have been reviewed and agreed). That version was sent for a two-week consultation period within ETSI (first deadline 16th of September 2003, 16:00). Several... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 4.1.2 Further comments from Vodafone group plc | This clause provides explanation of the comments previously made by Vodafone, which were supported by Nokia, Deutsche Telekom AG and Ericsson. |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 4.1.2.1 In-band power limits | The in-band power limit proposed by ERM TG31A (see clause B.2.1) is greater than is justified by information presented in the present document. Figure 1 of the present document is a graph of the available data rate of a UWB system (presumably meeting FCC requirements) as a function of range. Clause C.5 contains a numbe... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 4.1.2.2 Out-of-band power limits | Vodafone has serious concerns about the out-of-band power limits proposed by ERM TG31A (see clause 4.1.5). The FCC spectrum mask has an emissions limit of -61,3 dBm/MHz immediately outside of the frequency range for intended emissions (3,1 GHz to 10,6 GHz). However, at lower frequencies (the GPS bands and below), the l... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 4.1.3 Comments from Nokia (supported by Deutsche Telekom AG) | We propose that the intended frequency range (where -41,3 dBm applies) should NOT include the 5,15 GHz to 5,85 GHz band since this is used by WLAN and CEPT studies have shown that interference would result. Furthermore any use in the range 3,1 GHz to 5,15 GHz band should be on a strict DCA/listen before talk basis, as ... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 4.1.4 Comments from Siemens MC | Clause B.1.1 contains bullets requirements, taken from FCC regulations, which show a clear contradiction in the three bullets (bullet 1, 6 and 7). The first one claims for -10 dB bandwidth included within 3,1 GHz to 10,6 GHz, while the last two contradict that statement asking for -20 dB outside that band, making the f... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 4.1.5 Comments from ERM TG31A | In reaction to comment in clause 4.1.3, ERM-TG31A indicated it is of the opinion that UWB can share a congested spectrum better. In reaction to comment in clause 4.1.4, ERM-TG31A indicated clause B.1.1 is for informative purpose only. ERM-TG31A had proposed limits that include 20 dB tighter limits for the unwanted emis... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 4.1.6 Comments from EP BRAN | A new type of fixed wireless access standard has been developed in ETSI BRAN: HiperMAN. Manufacturers of HiperMAN systems are targeting indoor deployment of the Subscriber Stations, in order to reduce installation costs. UWB devices may be among the types of handheld device used in the same room as a HiperMAN receiver.... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 4.1.7 Comments from INTEL CORPORATION SARL | INTEL CORPORATION SARL provided the following technical justification supporting the proposed UWB in-band level of -41,3 dBm/MHz In the spread sheet attached to the present document (see annex B.2), a simple link budget table shows that we are just on the border of achieving 110 Mbps at 10 m and 480 Mbps at 4 m, which ... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 4.2 Technical system description | For detailed technical UWB information, see annex B. |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 4.3 Market information | For detailed market information, see annex A. 4.4 Impact on radio services inside and outside the proposed frequency band ETSI fully supports the actions of CEPT to allow the operation of UWB in Europe while insuring the compatibility with the other services. ETSI is also asking that due care be also given to the impli... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 5 Current regulations | There are no current regulations permitting the operation of UWB in Europe. Article RR No. 4.4 has been relied upon by national administrations (and CEPT as well) in many contexts to authorize applications not conforming with the Table of Frequency Allocations in the Radio Regulations (e.g. Short Range Devices which ar... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 6 Main conclusions | From the market information collected from the UWB industry, it is clear that there is a potential for a variety of UWB communication applications as well as an increasing number of (indoor) sensing and positioning applications. Technology is still advancing, so that it is at the moment not possible to describe a singl... |
f52f87c4e737db2b1ba0ad16a4dad162 | 101 994-1 | 7 Expected ECC actions | Mandate M/329 covering UWB calling for completion of Harmonized Standards for UWB by the end of the year 2004 was received by ETSI. ETSI accepted this mandate (see ETSI Work Item DEN/ERM-TG31A-0112-1). Therefore, ETSI requests ECC to consider the present document which includes necessary information to support the co-o... |
8e3767d8ae9467e9edbfd8b01e1e28b7 | 101 987 | 1 Scope | The present document analyses and provides recommendations regarding Air Interface enhancements that have been proposed for TETRA Release 2. The target audience is EPT, and the purpose is to enable informed decisions to be made by EPT regarding prioritization and feasibility of AI enhancement standardization work, and ... |
8e3767d8ae9467e9edbfd8b01e1e28b7 | 101 987 | 2 References | For the purposes of this Technical Report (TR), the following references apply: [1] ETSI EN 300 392-2 (V2.3.2): "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 2: Air Interface (AI)". |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.