hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.1.4.3 R-FUNC-TER-13 Configuration of Sensing Parameters | The sensing function shall support the configuration of sensing duration, silent period duration and frequency/channel. Explanation: In certain cases, the sensing function will control multiple WSDs involved in sensing and it will be able to configure each of these devices. A silent period requires all WSDs managed by ... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.2 Spectrum Management Requirements | |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.2.1 Requirements for systems supporting carrier aggregation | These requirements are focused on a system supporting carrier aggregation in TVWS. |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.2.1.1 R-FUNC-SPE-01 Carrier Aggregation in TVWS | The system may support carrier aggregation of a primary component carrier with one or more secondary component carriers operating in TVWS. The primary component carrier may be in TVWS, or any other band where system operation is allowed. |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.2.2.2 R-FUNC-SPE-02 TVWS Component Carrier Management and Configuration | If carrier aggregation is supported, the system should be able to quickly adapt to variations in channel availability and quality through activation, deactivation and reconfiguration of the TVWS component carriers. Explanation: Availability and quality of TVWS channels is not guaranteed. Decisions for TVWS component ca... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.2.2 Requirements for Spectrum Coordination Function | The system may support a spectrum coordination function to facilitate efficient and fair spectrum use and management. This function evaluates the actual demands of the CRSs requesting White Space spectrum and determines the spectrum assignment strategy. The clauses below define the requirements for the spectrum coordin... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.2.2.1 R-FUNC- SPE-COOR-01 Spectrum resource assignment decision | The spectrum coordination function shall support decision making for spectrum resource assignment based on the actual demands of the CRSs. Explanation: The actual demands of the CRSs will be evaluated according to the network load status, communication quality, etc. Based on these demands, the spectrum coordination fun... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.2.2.2 R-FUNC-SPE-COOR-02 Requirement for Spectrum Release | The spectrum coordination function shall be able to force the CRS to release the spectrum based on an evaluation of the CRS needs and priority. Explanation: The spectrum coordination function can force one CRS to release TVWS spectrum resources in order to reallocate them to other CRSs, if other CRSs are in greater nee... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.2.2.4 R-FUNC-SPE-COOR-04 Priority Use of Channels for TVWS Usage | The spectrum coordination function shall be able to reserve a subset of channels for TVWS usage to satisfy CRSs with guaranteed QoS requirements. The spectrum coordination function shall ensure that such priority use channels are assigned exclusively to such CRSs for a certain reservation time. The spectrum coordinatio... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.2.2.5 R-FUNC-SPE-COOR-05 Support for Spectrum Resource Reassignment | The spectrum coordination function shall be able to reassign the available spectrum resources among CRSs using the information of the current resource utilization by CRSs. Explanation: The spectrum coordination function obtains information on the amount of available spectrum resources from the geo-location database. Th... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.3 Coexistence Requirements | This clause defines the coexistence requirements for the CRS operation in UHF TV White Spaces. The requirements cover the coexistence between the TVWS CRS and incumbent spectrum users as well as the coexistence between TVWS CRS spectrum users. |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.3.1 Requirements for coexistence among TV White Space CRSs | This clause defines the requirements for the system, which facilitate the coexistence among TV White Space CRSs in UHF TV band White Spaces. |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.3.1.1 R-FUNC-COE-COOR-01 Support for heterogeneous networks | The system should ensure the coexistence with dissimilar and/or independently operated TV White Space CRSs which operate in UHF TV band White Spaces. 7.3.1.2 R-FUNC-COE-COOR-02 Support for Coordinated and non-Coordinated Coexistence The system should allow coexistence between TV White Space CRSs using coordinated and/o... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.3.1.3 R-FUNC-COE-COOR-03 Support for a coexistence function | The system may support a coexistence function to facilitate the coexistence among TV White Space CRSs. A TV White Space CRS may subscribe to the coexistence function (e.g. in the coordinated approach) in order to facilitate the efficient usage of the TV band White Space with multiple TV White Space CRSs. The clauses be... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.3.1.3.1 R-FUNC-COE-COOR-03-1 Support for different decision making topologies | The coexistence function shall enable different coexistence decision making topologies, such as distributed, centralized, and combination of distributed and centralized. Explanation: Different coexistence decision making topologies enable flexibility in the coexistence management among the heterogeneous TV White Space ... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.3.1.3.2 R-FUNC-COE-COOR-03-2 Support for acquiring information for coexistence | The coexistence function shall be able to obtain information required for coexistence from the TV White Space CRS and from other entities, for instance from the geo-location database. Explanation: The TV White Space CRS node provides information of its capabilities, operation parameters, and radio environment, e.g. mea... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.3.1.3.5 R-FUNC-COE-COOR-03-5 Support for WSD interferer discovery | The coexistence function shall be able to discover potential conflicts between the TV White Space CRSs which subscribe to the coexistence function. Explanation: The TV White Space CRSs which use the coexistence function provide information related to their geo-location and spectrum needs. Thus, the coexistence function... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.3.1.3.6 R-FUNC-COE-COOR-03-6 Support for Spectrum Resource Classification | The coexistence function may use information acquired from different TV White Spaces CRSs to facilitate the classification of the available (i.e. not used by incumbent) spectrum resources, for TV White Spaces CRSs at the specific geo-locations. ETSI ETSI TS 102 946 V1.1.1 (2014-07) 19 Explanation: The coexistence funct... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.3.1.3.9 R-FUNC-COE-COOR-03-9 Providing a Ranked Channel List to a CRS | The coexistence function shall be able to provide information on available channels to a CRS in the form of a ranked list, or other arrangement, in order to indicate the most recommended channels. Explanation: The quality of each channel can be assessed by the coexistence function based on measurements (such as sensing... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.4 Radio Access Requirements | The use of TVWS is assumed to be unlicensed and therefore: • there is no designation of UL or DL TVWS channels. Also we assume that operating of UL and DL within the same TVWS channel is only possible via some Time division scheme; • there is a need to adapt to changes in TVWS channel availability (in time and space) a... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.4.1 General Requirements | |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.4.1.1 R-FUNC-RAD-01 Reliability of Control and Data Transmission | The system shall ensure reliability of the control information and data transmission while operating in TVWS within the power limits set for the system. Explanation: The system may need to operate in the TVWS with high levels of interference from other WSD users or from incumbent radio services operating at high power ... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.4.1.2 R-FUNC-RAD-02 Radio Reconfiguration Management | The system shall support radio reconfiguration via reconfiguration commands delivered to one WSD, several or all WSDs simultaneously. Explanation: Radio reconfiguration commands can be sent to one WSD when the radio reconfiguration is related to this WSD only, or radio reconfiguration commands can be sent to several or... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.4.2 Requirements on usage of LTE in TVWS | The requirements herein described are focused on an LTE system operating in TVWS band. ETSI ETSI TS 102 946 V1.1.1 (2014-07) 21 |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.4.2.1 R-FUNC-RAD-03 LTE Modes of Operation | It should be possible to operate LTE-TDD in TVWS as a stand-alone system or to provide a Secondary Carrier in TVWS in the context of LTE carrier aggregation with the primary carrier provided via non TVWS frequencies. It should be possible to operate LTE-FDD DL or LTE-FDD UL in TVWS in the context of LTE carrier aggrega... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.4.2.2 R-FUNC-RAD-04 LTE Core Network capacity limitation | The Available Core Network capacity should be considered when initiating the connection establishment in the UHF TV band White Space. Explanation: The reconfiguration of CRS is not only based on RAN radio access capacity but also the remaining capacity of the appropriate Core Networks node (e.g. MME in LTE). |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.4.2.3 R-FUNC-RAD-COOR-05 LTE Assignment of Parameters | The coexistence function may provide means to agree on use of different sets of frequencies to be used by each LTE system in an area. The co-existence function may also provide a means to agree on a common cell bandwidths, operation modes, and different sets of physical Cell Ids for an LTE cell, e.g. if it is not possi... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.5 Requirements for User Mobility and Spectrum availability | |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.5.1 R-FUNC-USE-01 Support for Changing the Operating Channel | The system shall be able to change its operating channel(s). Explanation: Two examples when a system would need to change channel(s) are the following: - a primary service indicates that it will use the channel(s) at a given time; - the interference on the channel(s) becomes too high for the system to operate reliably. |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.5.2 R-FUNC-USE-02 Support for continuous service | In order to ensure service continuity when a master WSD changes its channel: • The master WSD should provide to slave WSDs all the information necessary for service continuity before changing to the new TVWS channel. • The slave WSDs should measure the received channel qualities of the target TVWS channels and should r... |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.6 QoS Requirements | |
6a78228fc84e6416f23a73502c6c422c | 102 946 | 7.6.1 R-PERF-QOS -01 Delay of the service | The system should meet the delay budget defined for the service (e.g. PDB) when operating in TV White Spaces. ETSI ETSI TS 102 946 V1.1.1 (2014-07) 23 History Document history V1.1.1 July 2014 Publication |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 1 Scope | The present document provides the test suite structure and test purpose specification for the ISO protocols specified in ISO 29281-1 [1] in compliance with the relevant requirements, and in accordance with the relevant guidance given in EG 202 798 [i.1]. |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ISO 29281-1:2013: "Intelligent transport systems -- Communication access for land mobiles (CALM) -- Non-IP networking -- Part 1: Fast networking & transport layer protocol (FNTP)". [2] ETSI TS 102 985-1: "Intelligent Trans... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI EG 202 798: "Intelligent Transport Systems (ITS); Testing; Framework for conformance and interoperability testing". [i.2] Void. [i.3] ISO 24102-3... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 3 Definitions and abbreviations | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO 29281-1 [1], TS 102 985-1 [2] and EG 202 798 [i.1] apply. |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO 29281-1 [1], TS 102 985-1 [2], EG 202 798 [i.1] and the following apply: FNTP Fast Networking & Transport Protocol IUT Implementation Under Test SUT System Under Test |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 4 Test suite structure | In general, the conformance test system architecture presented in the ITS testing framework [i.1] extended as illustrated in Figure 1 applies. Codec Figure 1: General conformance test system architecture for SUTs Such SUTs which support ITS station-internal management communications [i.4] may benefit from the conforman... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 5 TP basics | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 5.1 TP definition conventions | The TP definition is built according to the guidelines provided in the ITS testing framework [i.1], applying a formalized language with pre-defined keywords for the behaviour description. |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 5.2 TP identifier naming conventions | The identifier of the TP is built according to Table 1 as recommended in the ITS testing framework [i.1]. ETSI ETSI TS 102 985-2 V1.2.1 (2014-06) 8 Table 1: TP naming convention for FNTP [1] TP/<root>/<gr>/<sgr>/<x>/<nn> <root> = root FNTP Fast Networking & Transport Layer Protocol <gr> = group TXP Transmit Packets RXP... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 5.3 Rules for behaviour description | The description of the TP is built according to the guidelines provided in the ITS testing framework [i.1]. |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 5.4 Sources of TP definitions | All TPs are specified according to [1]. |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 5.5 TP proforma | [i.1] proposes a TP proforma which is used in the present document. The fields of this proforma as used in the present document are explained in table 2. Table 2: TP proforma field description TP Header TP ID The TP ID is a unique identifier according to the TP naming conventions in Table 1. Test objective Short descri... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 5.6 PICS mnemonics | The PICS mnemonics presented in Table 3 are used in the TP proforma. Table 3: PICS mnemonic for ISO 29281-1 [1] Mnemonic PICS item PICS_ROLE_RONLY [2] A.2/1 PICS_ROLE_HONLY [2] A.2/2 PICS_ROLE_RH [2] A.2/3 PICS_EXT [2] A.3/2 PICS_ITS_S_INW [2] A.4/1 PICS_SEC [2] A.4/2 PICS_NHOPBC [2] A.4/3 PICS_LPP [2] A.4/4 PICS_CIP [... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6 TPs for FNTP | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.1 Transmit packets | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.1.1 Basic Procedure | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.1.1.1 Valid behaviour tests | TP Id FNTP/TXP/BP/BV/01 Test objective Single hop broadcast transmission request with known VCI Reference ISO 29281-1 [1], clause 7.6.1 and clause 7.6.2 PICS Selection PICS_ROLE_RH Initial conditions with { the IUT having an FNTP forwarding table with proper entry in support of the local port number of the ITS-S applic... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.1.1.2 Invalid behaviour tests | Invalid test purposes will be defined once ISO has implemented the concept of path and flow management in the architecture standard ISO 21217 [i.5] and subsequently in ISO 29281-1 [1]. |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.1.2 Extended Procedure | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.1.2.1 Valid behaviour tests | TP Id FNTP/TXP/EP/BV/01 Test objective N- hop broadcast transmission request with known VCI Reference ISO 29281-1 [1], clause 7.6.3 PICS Selection PICS_EXT AND PICS_ROLE_RH AND PICS_NHOPBC Initial conditions with { the IUT having an FNTP forwarding table with proper entry in support of the requested local port number o... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.1.2.2 Invalid behaviour tests | TP Id FNTP/TXP/EP/BI/01 Test objective N- hop broadcast transmission request with invalid FNTP control field, and with known VCI Reference ISO 29281-1 [1], clause 7.6.3 PICS Selection PICS_EXT AND PICS_ROLE_RH AND PICS_NHOPBC Initial conditions with { the IUT having an FNTP forwarding table with proper entry in support... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.1.3 Forwarding Procedure | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.1.3.1 Valid behaviour tests | TP Id FNTP/TXP/FP/BV/01 Test objective TX from ITS-S host Reference ISO 29281-1 [1], clause 7.6.4 PICS Selection PICS_ITS_S_INW AND (PICS_ROLE_HONLY OR PICS_ROLE_RH) Initial conditions with { the IUT having an FNTP forwarding table with proper entry in support of the requested local port numbers of the ITS-S applicatio... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.1.3.2 Invalid behaviour tests | TP Id FNTP/TXP/FP/BI/01 Test objective TX from ITS-S host - unknown access to ITS station-internal network Reference ISO 29281-1 [1], clause 7.6.4 PICS Selection PICS_ITS_S_INW AND (PICS_ROLE_HONLY OR PICS_ROLE_RH) Initial conditions with { the IUT having an FNTP forwarding table with no entry related to an ITS-S inter... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.2 Receiving packets | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.2.1 Basic Procedure | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.2.1.1 Valid behaviour tests | TP Id FNTP/RXP/BP/BV/01 Test objective Single hop unicast reception from peer station Reference ISO 29281-1 [1], clause 7.7.1, clause 7.7.2 and clause 7.7.3 PICS Selection PICS_ROLE_RH Initial conditions with { the IUT having a proper entry in the FNTP forwarding table with Service Port such that no ITS station-interna... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.2.1.2 Invalid behaviour tests | TP Id FNTP/RXP/BP/BI/01 Test objective Single hop broadcast reception to unknown Service Port Reference ISO 29281-1 [1], clause 7.7.1 and clause 7.7.2 PICS Selection PICS_ROLE_RH OR PICS_ROLE_RONLY OR PICS_ROLE_HONLY Initial conditions with { the IUT having an entry in the FNTP forwarding table for Service Port = port1... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.2.2 Extended Procedure | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.2.2.1 Valid behaviour tests | TP Id FNTP/RXP/EP/BV/01 Test objective N-hop broadcast reception with forwarding Reference ISO 29281-1 [1], clause 7.7.5 PICS Selection PICS_ROLE_RH AND PICS_NHOPBC Initial conditions with { the IUT having an FNTP forwarding table with proper entry in support of the local port number of the ITS-S application } Expected... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.2.2.2 Invalid behaviour tests | TP Id FNTP/RXP/EP/BI/01 Test objective Reception of packet with not supported FNTP control field value Reference ISO 29281-1 [1], clause 7.7.4 PICS Selection PICS_EXT AND PICS_ROLE_RH Initial conditions with { the IUT having setup properly the FNTP forwarding table } Expected behaviour ensure that { when { the IUT havi... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.2.3 Forwarding Procedure | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.2.3.1 Valid behaviour tests | TP Id FNTP/RXP/FP/BV/01 Test objective TX from ITS-S router to ITS-S host Reference ISO 29281-1 [1], clause 7.7.8 PICS Selection PICS_ITS_S_INW AND (PICS_ROLE_RONLY OR PICS_ROLE_RH) Initial conditions with { the IUT having set up properly the FNTP forwarding table } Expected behaviour ensure that { when { the IUT havin... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.2.3.2 Invalid behaviour tests | TP Id FNTP/RXP/FP/BI/01 Test objective RX at ITS-S host - unknown Service Port Reference ISO 29281-1 [1], clause 7.7.2 PICS Selection PICS_ITS_S_INW AND (PICS_ROLE_HONLY OR PICS_ROLE_RH) Initial conditions with { the IUT having no entry for the required Service Port } Expected behaviour ensure that { when { the IUT hav... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.3 CI parameter management | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.3.1 Basic Procedure | The sub-group BP is not applicable for the group CIP. |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.3.2 Extended Procedure | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.3.2.1 Valid behaviour tests | TP Id FNTP/CIP/EP/BV/01 Test objective CIP in NPDU for single-hop BC transmission Reference ISO 29281-1 [1], clause 7.10.1 PICS Selection PICS_CIP AND PICS_ROLE_RH Initial conditions with { the IUT having setup properly the FNTP forwarding table } Expected behaviour ensure that { when { the IUT having received a correc... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.3.2.2 Invalid behaviour tests | None. |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.3.3 Forwarding Procedure | |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.3.3.1 Valid behaviour tests | TP Id FNTP/CIP/FP/BV/01 Test objective TX from ITS-S host to ITS-S router with CIPs Reference ISO 29281-1 [1], clause 7.10.2 PICS Selection PICS_CIP AND PICS_ITS_S_INW AND (PICS_ROLE_HONLY OR PICS_ROLE_RH) Initial conditions with { the IUT having set up properly the FNTP forwarding table } Expected behaviour ensure tha... |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.3.3.2 Invalid behaviour tests | None. |
efa165b2e4a82e783166d1171059af6d | 102 985-2 | 6.4 Secure communications | None. ETSI ETSI TS 102 985-2 V1.2.1 (2014-06) 26 History Document history V1.1.1 July 2012 Publication V1.2.1 June 2014 Publication |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 1 Scope | ECC Decision ECC/DEC/(04)06 [i.2] of the 19th March 2004 and amended on the 26th June 2009 provides a possibility for a GSM-R extension into the bands 873 MHz to 876 MHz and 918 MHz to 921 MHz on a national basis. The present document defines the requirements for radio Transmission and Reception of mobile station (MS) ... |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI EN 300 919: "Digital cellular telecommunications system (Phase 2+) (GSM); Types of Mobile Stations (MS) (GSM 02.06)". [2] ETSI TS 100 607-1: "Digital cellular telecommunications system (Phase 2+); Mobile Station (MS) ... |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 101 748: "Digital cellular telecommunications system (Phase 2+) (GSM); Abbreviations and acronyms (GSM 01.04)". [i.2] ECC/DEC/(04)06: "ECC Dec... |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 3 Abbreviations | For the purposes of the present document, the abbreviations given in TR 101 748 [i.1] apply. |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 4 Frequency bands and channel arrangement | i) Railways GSM 900 Band, R-GSM (includes Standard and Extended GSM 900 Band): - for Railways GSM 900 band, the system is required to operate in the following frequency band: 876 MHz to 915 MHz: mobile transmit, base receive; 921 MHz to 960 MHz: base transmit, mobile receive. ii) Extended Railways GSM 900 Band, ER-... |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 5 Transmitter characteristics | |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 5.1 Base station System (BSS) | Transmitter characteristics shall be the same as specified in TS 100 910 [3] with the exceptions that the requirements are applicable to the entire ER-GSM Band. |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 5.2 Mobile station (MS) | Transmitter characteristics shall be the same as specified in TS 100 910 [3] with the exceptions that the requirements are applicable to the entire ER-GSM Band. This apply to MSs defined in EN 300 919 [1] and in TS 102 933-1 [6]. |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 5.3 Repeaters | Transmitter characteristics shall be the same as specified in EN 300 609-4 [5] with the exceptions that the requirements are applicable to the entire ER-GSM Band. |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 6 Receiver characteristics | |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 6.1 Base station System (BSS) | Receiver characteristics shall be the same as specified in TS 100 910 [3] with the exceptions that the requirements are applicable to the entire ER-GSM Band. |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 6.2 Mobile station (MS) | Receiver characteristics shall be the same as specified in TS 100 910 [3] and TS 102 933-1 [6] with the exceptions that the requirements are applicable to the entire ER-GSM Band. This apply to MSs defined in EN 300 919 [1] and in TS 102 933-1 [6]. |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 6.3 Repeaters | Receiver characteristics shall be the same as specified in TS 100 910 [3] with the exceptions that the requirements are applicable to the entire ER-GSM Band. ETSI ETSI TS 102 932-1 V1.1.1 (2011-11) 8 |
86ab90604488e6550ddca0bb5c09d4cf | 102 932-1 | 7 Other requirements | RF characteristics which are not explicitly addressed in the present document shall be taken from TS 100 910 [3] and from TS 102 933-1 [7]. Unless otherwise stated, the environmental requirements defined in the corresponding standards to specified equipment shall apply. ETSI ETSI TS 102 932-1 V1.1.1 (2011-11) 9 Annex A... |
da23acec8b7cb8465231a9f5f80bec0a | 102 980 | 1 Scope | The present document defines a backward compatible extension of the Dynamic Label feature used in Digital Audio Broadcasting (DAB) (ETSI EN 300 401 [1]). |
da23acec8b7cb8465231a9f5f80bec0a | 102 980 | 2 References | |
da23acec8b7cb8465231a9f5f80bec0a | 102 980 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
da23acec8b7cb8465231a9f5f80bec0a | 102 980 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
da23acec8b7cb8465231a9f5f80bec0a | 102 980 | 3 Definition of terms, symbols and abbreviations | |
da23acec8b7cb8465231a9f5f80bec0a | 102 980 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 300 401 [1] and the following apply: category: group of content types content type: classification of the content of a DL Plus object Dynamic Label (DL): feature of DAB for providing a programme with text messages; it also provides commands, e.g. for ... |
da23acec8b7cb8465231a9f5f80bec0a | 102 980 | 3.2 Symbols | Void. |
da23acec8b7cb8465231a9f5f80bec0a | 102 980 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CD Compact Disc CRC Cyclic Redundancy Check DAB Digital Audio Broadcasting DL Plus Dynamic Label Plus DL Dynamic Label EPG Electronic Programme Guide FIG Fast Information Group FM Frequency Modulation IR Item Running IT Item Toggle MMS Multime... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.