hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f8ca67144ad9abf1f1869e5caac05c87 | 102 804 | 4 Operational modes | The operational mode is described by a generic mode, i.e. the standard, and the specific mode, e.g. annex and band plan. G.992.5/ADSL2plus [1] and G.993.2/VDSL2 [2] are examples of generic modes. The present document defines the following six operational modes. These are explained in tables 1 and 2: 1) A_A2P_ATM (ADSL2... |
f8ca67144ad9abf1f1869e5caac05c87 | 102 804 | 5 Definitions of DSL multi-operation | The following types of DSL multi operation (MO) are defined: 1) MO1: V2_BB8b_PTM or V2_BB17a_PTM or A_B2P_ATM; 2) MO2: V2_BB8b_PTM or V2_BB17a_PTM or A_J2P60_ATM; 3) MO3: V2_BA17_PTM or A_A2P_ATM. |
f8ca67144ad9abf1f1869e5caac05c87 | 102 804 | 6 Performance and functional requirements | Performance and functional requirements of the multi-operation types MO1 and MOM2 are defined for each of the underlying VDSL2- or ADSL2plus-related operational modes, for which the following Broadband Forum test specifications shall apply: • Broadband Forum TR-100: "ADSL2/ADSL2plus Performance Test Plan" [5]; • Broadb... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 1 Scope | The present document defines the architecture and functional blocks for a C-PMSE system together with the protocols and interfaces which link them. The findings are based on the technical recommendations in TR 102 799 [i.1]. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 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... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI EN 300 422-1 (V1.3.2): "Electromagnetic compatibility and Radio spectrum Matters (ERM); Wireless microphones in the 25 MHz to 3 GHz frequency range; Part 1: Technical characteristics and methods of measurement". |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 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 102 799: "Electromagnetic compatibility and Radio spectrum Matters (ERM); Operation methods and principles for spectrum access systems for PMS... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 3 Definitions and abbreviations | |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 102 799 [i.1] and the following apply: Configuration File: file containing the PMSE setup/scene NOTE: See clause 9. C-PMSE link: wireless connection, which incorporates the content and control planes Service Level Agreement (SLA): set of pe... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 102 799 [i.1] and the following apply: ABT Ask Before Talk AISG Antenna Interface Standards Group AMCT Adaptive Modulation and Coding Table API Application Programming Interface ASCII American Standard Code for Information Interchange ASQ Action Se... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 4 Refined C-PMSE Architecture | |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 4.1 Overview | The refined functional architecture of C-PMSE is shown in figure 1. In comparison to the block diagram described in TR 102 799 [i.1] the following differences are inserted: • The RRM contains two more elements: - Radio Environmental Map (REM); - Action Sequencer (ASQ). • Furthermore the CEN is depicted by its four main... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 4.2 Radio Resource Manager (RRM) | Two new elements are introduced in this clause (see figure 1): • one storage block: Radio Environmental Map (REM); • one executing block: Action Sequencer (ASQ). The REM is a database that hosts a map of wider frequency range of interest in comparison to FAT, which lists frequencies allowed by the regulator and frequen... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 4.3 Cognitive Engine (CEN) | The CEN shall include the following main elements (see figure 1): • Fusion Engine (FEN): The FEN merges all information about the environment coming from the Scanning Receiver Controller (SCC), from the Frequency Coordinator (FCO), from own radio links and possibly from RRMs of co-located C-PMSEs. The result of the mer... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 4.4 Interfaces | Three external interfaces are used for communication between C-PMSE and • Scanning Receiver Controller: sci; • Frequency Coordinator: fci; • Co-located C-PMSE: cpi. These external interfaces need a standardized format to support communication between SCC, FCO with C-PMSE of all vendors, even communication between co-lo... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5 Technical Specification of the Cognitive Engine | This clause presents the functional architecture of the CEN and its technical specification. Figure 2 depicts the functional architecture of the CEN. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.1 Functional architecture of the CEN | To develop the cognitive functionalities described in TR 102 799 [i.1], the CEN shall include the following components: • Cyclic Unit (CYU): This component acts as the central controller and scheduler of all processes in the CEN. • Fusion Engine (FEN): This component extracts and merges information about the radio envi... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.1.1 Requirements on CEN Architecture | Each component shall constitute a separate software process (module) that interfaces and exchanges data with the other components through some generic interface (e.g. TCP sockets, which would allow distribution of the components among different networked hosts). A modular architecture will allow replacement of any func... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.2 Cyclic Unit: CYU | This component is the core of the CEN. It schedules the call and timing processes of all other components. Each component of the CEN should be defined around a basic state machine that interfaces with the CYU (see figure 3). ETSI ETSI TS 102 800 V1.1.1 (2011-01) 14 Generic command structure of the CYU: <component>:<com... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.2.1 C-PMSE initialisation process | The CYU is in charge of initialising the C-PMSE. Therefore, the following actions are required: • det initial cycle time; • initialise interfaces, e.g. set update period for push/pull processes at the interfaces: - sci API; - rmi API; - sli API; - cmi API. • request user to enter service level in the SLE; • request RRM... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.3 Fusion Engine: FEN | FEN extracts and merges information about the radio environment (figure 4) coming from: • SCC; • FCO; • RRM: old state of the REM and current LPS; • RRM of neighbour C-PMSEs (optional). Figure 4: Input and output of the fusion process in the FEN A standard approach for encoding the radio environment data in the FEN is ... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.4 Decision Engine: DEN | DEN analyzes and classifies the current operation context of the C-PMSE given by: i) its radio capabilities and constraints stored in the RRM (LPS); and ii) the status of the radio environment stored in the RRM (REM), and determines an optimal response to the current operation context. The DEN should be built around a ... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.4.1 Reasoning Module | The reasoning module classifies the C-PMSE operation context, in a first step into critical (reactive path) and uncritical (proactive path) situations (see also figure 8), while in a second step it may break the operation context into different use cases. For the classification, the reasoning module has to compute the ... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.4.2 Learning Module | The learning module continuously refines the classification of the operation context into use cases based on past experience. Training and learning are necessary for the CEN to achieve satisfactory performance. ETSI ETSI TS 102 800 V1.1.1 (2011-01) 17 |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.4.3 Case Database (CDB) | The case database stores for each use case that the reasoning module has learned to differentiate: • the panic action set; • the result of the optimisation process. Critical aspects of the decision-making process are convergence time, implementation complexity and stability. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.5 Optimisation engine (OEN) | The OEN should be built around a state machine process that listens for a request to process some data from the CYU. With the process request, the CYU provides the OEN with the information necessary to run the optimisation process. Each optimisation algorithm will require the problem definition, i.e. the objective func... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.6 rmi API | This component controls the rmi interface that serves to transfer the RRM tables from the RRM to the CEN and vice versa. rmi API has to control two services: • Push service (time critical): CEN transfer of data to the RRM (ASQ and REM), as shown in the left hand side of figure 6. This service can overwrite the content ... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.7 cmi API | The cmi API is in charge of running the protocol described in clause 8.3. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.8 sci API | The sci API is in charge of running the protocol described in clause 10.4. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.9 sli API | This component controls the sli interface that serves to transfer monitored performance information from the SLM to the CEN. The sli API offers a pull service from the CEN to the SLM, i.e. CEN asks the SLM to deliver monitored performance information, as shown for start up and update in figure 7. The pull service is sy... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 5.10 Functional Processing Flow | The cognitive cycle and the associated actions are shown in figure 8. Both the reactive and proactive paths are shown. ETSI ETSI TS 102 800 V1.1.1 (2011-01) 19 Figure 8: Processing flow cognitive cycle 6 Technical Specification of the Radio Resource Manager RRM This clause presents the technical specification of the RR... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 6.1 Radio Resource Manager | The detailed architecture of the RRM is depicted in figure 9. The RRM consists of two data storage blocks, namely the Radio Environmental Map (REM) and the Link Parameter Set (LPS), and an executing block called the Action Sequencer (ASQ). These elements are further described in the following clauses. Figure 9: RRM det... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 6.1.1 Action Sequencer | The Action Sequencer (ASQ) receives from the CEN the sequence of actions that should be next applied to the radios attached to the C-PMSE. The ASQ sequentially pushes the actions received by the CEN as commands to the PMSE devices. It is important to keep the right sequence for the execution of the commands, since they... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 6.1.2 Data storage Blocks | RRM comprises two data storage blocks: Radio Environmental Map (REM) and Link Parameter Set (LPS). |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 6.1.2.1 Radio Environmental Map (REM) | The REM is a multi-domain database for structured storing of radio environment data. The information stored in REM is the outcome of the Fusion Engine (FEN) and characterizes the radio environment in which the C-PMSE system finds itself. ETSI ETSI TS 102 800 V1.1.1 (2011-01) 21 F [Hz] Observed frequencies (REM) Granted... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 6.1.2.2 Link Parameter Set (LPS) | The LPS comprises four databases representing the current settings and performance of the C-PMSE links: FAT, PAT, DAT, and AMCT. The functionality and structure of each database are described in detail in the following clauses. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 6.1.2.2.1 Frequency Allocation Table (FAT) | The FAT hosts a list with the actual allocated frequencies of each of the radio links. It will be updated each time a physical modification of the frequency resource of a radio link takes place. 6.1.2.2.1.1 Mandatory FAT syntax Mandatory FAT syntax is shown in table 3. ETSI ETSI TS 102 800 V1.1.1 (2011-01) 22 Table 3: ... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 6.1.2.2.2 The Power Allocation Table (PAT) | The PAT lists the currently set EIRP power level of the radio device in dBm. 6.1.2.2.2.1 Mandatory PAT syntax The mandatory PAT syntax is shown in table 4. Table 4: Mandatory PAT syntax Link number Control plane TX Pout [dBm] Content plane TX Pout [dBm] L1 0 10 L2 0 0 … … … Ln 0 3 |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 6.1.2.2.3 Device Allocation Table (DAT) | The DAT is a database that hosts a list of installed devices. It contains information concerning which type of equipment is used for a particular audio link. For an uplink audio link, it contains the wireless microphone and receiver product code. The product code is important as specific interference robustness paramet... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 6.1.2.2.4 Adaptive Modulation and Coding Table (AMCT) | The AMCT is a database consisting of: • A non-mandatory, non-shared part that contains the current modulation and coding parameters used for each link shown in table 5. These parameters may be vendor specific, and therefore it may not be appropriate to exchange them between competing C-PMSE systems. Table 5: Non-mandat... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 6.1.2.2.5 Interface cpi | The cpi reflects the interface between RRMs of different, co-located C-PMSEs. In tables 6 and 7. typical commands and their results exchanged between co-located C-PMSE are summarized. The commands and results are separated into two groups: • mandatory commands (table 6); • optional commands (table 7). ETSI ETSI TS 102 ... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 7.1 Frequency Coordinator FCO | The Frequency Coordinator FCO contains a database that manages the licenses granted to various services and users based on a given regulatory framework. The FCO is a key network element in supporting the functionality of ABT. The FCO might not be run by a regulator itself. It may be an outsourced functionality. It is i... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 7.2 Rationale for an hierarchical database approach | For spectrum management, a hierarchical arrangement of databases at the regulator, at the Frequency Coordinator (FCO) and at the multiple C-PMSE systems is foreseen as depicted in figure 11. Figure 11: Arrangement of hierarchical databases ETSI ETSI TS 102 800 V1.1.1 (2011-01) 24 Database at Regulator Optional Regional... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 7.3.1 Overview | To achieve efficient usage of the scarce frequency spectrum, the network elements involved FCO, REM, FEN, SCC have to efficiently interact. Therefore a common structure and language for all databases involved is preferable. The following categories may appear in a slightly modified manner with all databases. By that, a... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 7.3.2 Definition of database language elements | The classification in table 8 may be necessary to cover e.g. inconsistencies between regulations and de facto usage. Table 8: Database language elements Parameter Description Validity: Defines the scope of the relevant database (e.g. International, national, regional, local, other) Legal Status: Defines the binding cha... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 7.4 Processing of database language | fci sci Figure 13: Fusion process The challenge for the fusion engine FEN now is to merge the information that is delivered from the various information sources SCC, FCO and REM to create an updated entry into the REM (figure 13). The interference condition is described in a different way by the SCC and by the FCO. The... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 7.4.1 fci interface | The fci interface uses the language elements described above. A spectrum negotiation process is based on a specific set of parameters called a Negotiation Set (table 10). The process is done via commands which are exchanged between the FCO and the C-PMSE. ETSI ETSI TS 102 800 V1.1.1 (2011-01) 27 NegotiationSet (contain... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 7.4.2 cpi interface | The database structure and language defined above will also be used on the cpi interface for exchange of the REM table between co-located C-PMSE. The commands used on the cpi interface are defined in clause 6.1.2.2.5. ETSI ETSI TS 102 800 V1.1.1 (2011-01) 28 8 Technical Specification of the Performance Monitor (PMO) |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 8.1 Performance Monitor (PMO) | The PMO is a human-machine-interface allowing a human to inspect a C-PMSE System and to trace its performance. It creates a PMO logfile of every C-PMSE session containing quantitative system parameters and their history. The performance monitor (PMO) provides dynamic insight into actual parameters and performance behav... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 8.2 Data tansfer from RRM to PMO (rpi) | All services via the rpi interface are based on a push service. At start up, the service is executed (figure 15) for the first time: • RRM sends its parameter set to PMO. During operation, a parameter change inside RRM initiates the transmission of the parameter set to PMO. If no parameters are changed, no push service... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 8.3 Data transfer from CEN to PMO (cmi) | Like the data transfer from RRM to PMO, the service between CEN and PMO is based on a push service. It is executed at start up the first time. Every time CEN changes its parameter during operation, the new parameter set is transmitted to PMO (figure 16). ETSI ETSI TS 102 800 V1.1.1 (2011-01) 30 CEN PMO CEN parameters S... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 8.4 Logfile | The logfile is a mandatory element of PMO. Every time a push service is executed it triggers the PMO to write the new set of parameters to its logfile. It is used to store all received parameters, the current and the preceding of both network entities. This makes it possible to watch and debug the trend of the system p... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 8.5 Visualization | The PMO may have a graphical user interface to interact between user and C-PMSE. This optional GUI is used to display the current content of the logfile with a predefined update rate. Visualized quantitative parameters may be: • lists of FAT, DAT, AMCT, DAT; • content of REM; • radio parameters; • KPIs of CEN; • CDB of... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 9 SLE / SLM | |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 9.1 Service Level Entry (SLE) | The human machine interface (HMI) consists of SLE (feeds SLM) and PMO (fed by RRM and CEN). It provides the tools for configuring, managing and monitoring multiple elements in a C-PMSE. The user is able to set quality thresholds and service level entries for every PMSE link through the SLE. This might be possible throu... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 9.1.1 Offline / Online | SLE is a planning tool; the entry of quality threshold parameters can be done with or without connection to a C-PMSE, i.e. offline or online. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 9.1.1.1 Offline (GUI is not connected to the CEN) | A configuration file stores the planned PSME setup, which can be uploaded to the SLE when switching to online mode. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 9.1.1.2 Online (CEN is connected) | If the entry of the quality threshold parameters is done online, the performance monitor (PMO) might show actual quality parameters depending on the connected radio devices. The PMO might show additional information (e.g. scanning results, available spectrum, frequencies to choose from, etc.). |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 9.1.2 Quality thresholds | SLAs are quality thresholds agreed between user or contractor and service provider. One or more SLE will form an SLA. The SLA values are the minimum levels the C-PMSE has to meet. An under-run of those levels should not occur. ETSI ETSI TS 102 800 V1.1.1 (2011-01) 32 A possible example for setting quality thresholds in... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 9.1.3 SLE connected to SLM and DAT | SLE is connected to SLM and DAT. The date transfer set up is: • connection to SLM: SLM pulls information from SLE; • connection to DAT: SLE pulls information from DAT. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 9.2 Service Level Monitor (SLM) | The SLM receives user threshold parameters from the SLE and real time measurement data from each PSME link. After pulling data from the SLE, the SLM maps the qualitative figures from the SLE into quantitative figures. The SLM then compares the data and provides the information to the CEN (CEN pulls) and the PMO (SLM pu... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 9.2.1 Data received by SLM from SLE and PMSE link | SLE data (SLA parameters) are described in clause 11. PMSE link provides data associated with link-id. Examples of the received data are: • Bit Error Rate (BER); • RF signal strength (RSSI); • C/(N+I) indicator; • Squelch headroom (examples: tone squelch, noise squelch, RF squelch). |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 9.2.2 SLM data sent to CEN | The SLM calculates service level operating margins with the received measurement data from the PMSE link and with the given thresholds received from the SLE. The CEN receives the quality status in conjunction with the link-ID (margins, delta) through the interface sli and transfers it to REM using the interface rmi. Th... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.1 Scanning Receiver Subsystem (SCR) | |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.1.1 Overview | The Scanning Receiver Subsystem (SCS) is composed of multiple scanning receivers spread at different locations around an event and one Scanning Receiver Controller (SCC). The SCS will assist the Fusion Engine (FEN) inside the Cognitive Engine (CEN) to compose a trustworthy Radio Environmental Map (REM), not only being ... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.1.2 Installation | The SCS typically will be a fixed installation at an event location; however it may also be set up for specific events only. Therefore the SCS may belong to the infrastructure offered by an event location, a production company or even an equipment supplier. ETSI ETSI TS 102 800 V1.1.1 (2011-01) 34 |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.1.3 Connectivity | It is envisioned that scanning receivers are linked via regular Ethernet so not to mandate specific dedicated cabling. Existing, low cost infrastructure for connecting the scanning receivers (SCRs) to the Scanning Receiver Controller (SCC) and SCC to the CEN should be usable. An Ethernet of at least 1 Mbit/s is assumed... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.1.4 Sharing of SCS | One SCS may be used by several C-PMSE that are co-located. By that, costs for multiple SCR and SCC can be shared, and each individual C-PMSE is given a larger base of spectrum sensing data to derive conclusions and support the proactive behaviour of the CEN. A typical case may be two theatres next to each other. Multip... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.2 Scanning Receiver (SCR) | |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.2.1 Location of SCRs | Preferably multiple scanning receivers at various locations with different distance to the centre of the C-PMSE coverage area are installed. The placement of SCRs at different locations is key to support the proactive behaviour of the C-PMSE. By sensing at different locations, trends in the interference conditions can ... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.2.2 Features | |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.2.2.1 Support for different measurement types | An SCR needs to serve a certain frequency range and allows at least energy detection with a certain frequency resolution. However under certain circumstances, especially with pulsed emitters it is necessary not only to sense the average power in a frequency bin but also the peak power. Stage with PMSE transmitters Mixi... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.2.2.2 Queuing of Jobs | Queuing of scanning jobs will be located inside the SCC. Therefore an SCR does not have to include this functionality. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.2.2.3 Antenna pattern control | An SCR needs to support control of antenna patterns, allowing steering antenna patterns in different directions. At least two antenna connectors should be supported. An SCR for sensing the L-Band needs to support even more different beams to detect directions of incoming signals by a hemispherical scan (azimuth plus el... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.2.2.4 Automatic detection of location | An SCR may support automatic detection of location by GNSS or any other localization system. However as satellite based services are typically unavailable indoors, at least a manual entry should be possible. Location should be stored in two formats in geo coordinates and also in verbose format. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.2.2.5 Automatic detection of time | Every measurement report returned should include a time stamp, reflecting the time the measurement was conducted. This is especially needed as the time a scanning job was sent from CEN to SCC and is conducted by SCR can differ strongly due to the queue inside the SCC. Time might be detected automatically by different t... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.3 Scanning Receiver Controller SCC | The SCC acts as a concentrator of data gathered by multiple SCR. By sensing the level at different locations, an estimate of the location of an emitter is derived together with an uncertainty range. It is clear, the more SCR are connected, the more accurate the estimate gets. An essential functionality of the SCC is a ... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.5.2 Scanning jobs | A scanning job sent from CEN to SCR is composed of the mandatory data given in table 18. Table 18: Data - scanning jobs Parameter Description start_frequency stop_frequency frequency_resolution (bin) averaging_time measurement_type Selection of type of measurement: spectrum, power versus time, IQ samples At least spect... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.5.3 Scanning report | After performing the scanning job, the SCR will return a measurement report comprising the following data given in clauses 10.5.3.1 through 10.5.3.4. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.5.3.1 Frequency domain measurement report | • SCR location or ID; • Measurement time stamp; • Antenna pattern number used; • Frequency bin | average power | peak power. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.5.3.2 Time domain measurement report | • SCR location or ID; • Measurement time stamp; • Antenna pattern number used; • Time | power. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.5.3.3 IQ samples measurement report | • SCR location or ID; • Measurement time stamp; • Antenna pattern number used; • Centre frequency; • Time | I sample | Q sample. ETSI ETSI TS 102 800 V1.1.1 (2011-01) 39 |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 10.5.4 Other commands | Besides scanning jobs sent to an SCR, there are also further commands that need to be supported. These are given in table 19. Table 19: Additional commands supported by SCR Command Description write_location Stores information about location in SCR read_location Will return the location of SCR in coordinates read_locat... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 11 RF Parameters & Service Levels | |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 11.1 Introduction | The purpose of the present document is to define the parameters used by the cognitive engine of the C-PMSE for radio resource management. The CEN gathers information about the characteristics of the radio units it manages and their cognitive capabilities. The required performance of each link results from a service lev... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 11.2 Performance indicators | The performance describes the requirements on a per link basis on which the CEN will base its decisions are given in table 20. Table 20: Performance Requirements Name Value Comments Bit Error Rate [ … ] % Audio SNR [ … ] dB RSSI [ … ] % of maximum ETSI ETSI TS 102 800 V1.1.1 (2011-01) 40 |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 11.3 Device Characteristics / Capabilities | Interactive values of performance related parameters of the C-PMSE system are listed in tables 21 through 24. Indicative values for transmitter characteristics (on a per link basis) are given in table 21. Table 21: Transmitter Characteristics (on a per link basis) Name Value Configurable Comments RF power maximum > 250... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 12 Spectral efficiency definitions | Various terms have been used in relation to defining spectral efficiency. With the next clauses, a definition of the various terms is given. |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 12.1 Terminology | |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 12.1.1 Spectral efficiency of selected modulation scheme | A selected modulation format is characterized by its symbol alphabet and its transmit pulse. A model of information flow with a transmitter is given in figure 19. Figure 19: Model of information flow with a transmitter Information theory defines spectral efficiency of a point-to-point connection as the number of bits t... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 12.1.2 Spectral efficiency related to information source | If spectral efficiency is defined as the number of bits from an information source transported per second and divided by the bandwidth occupied (bit/(s·Hz)), then of course source coding and channel coding also impact it. Source coding techniques e.g. MP3 or SLQ (Spherical Logarithmic Quantization) of course would impr... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 12.1.3 Spectral efficiency of a communication system | The spectral efficiency of a communication system is defined as the number of total bits transported aggregated over all users per second and within a given bandwidth and area. So the dimension is either bit/s/Hz/cell or bit/s/Hz/km2. It can be improved by increasing the density of access points or base stations. Infor... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 12.1.4 Efficiency of spectrum usage | The efficiency of spectrum usage is measured as the average number of bits transported within a certain bandwidth per second and per Hz bandwidth across all users and all services within a certain area. So the dimension is bit/s/Hz/km2. This figure can be improved by implementing secondary services that use free resour... |
ebaa45125388638e5939bc9fc5935abd | 102 800 | 12.2 Conclusion | C-PMSE systems mainly target improving "efficiency of spectrum usage" while ensuring a high quality of the PMSE link. With respect to a transition from analogue PWMS systems to digital ones, one of the goals is to increase spectral efficiency of a PMSE link. However as analogue compander techniques also work very well,... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 1 Scope | The present document provides the Abstract Test Suite (ATS) and partial PIXIT proforma for the protocols specified in ISO 24102-4 [1], ISO 24102-5 [2] based on the related TSS & TP specification TS 102 797-2 [4] and the PICS proforma TS 102 797-1 [3] and in accordance with the relevant guidance given in ISO/IEC 9646-1 ... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 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... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ISO 24102-4:2013: "Intelligent transport systems -- Communications access for land mobiles (CALM) -- ITS station management -- Part 4: Station-internal management communications". [2] ISO 24102-5:2013: "Intelligent transpo... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 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] ISO 24102-3:2013: "Intelligent transport systems -- Communications access for land mobiles (CALM) -- ITS station management -- Part 3: Service access ... |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 3 Definitions and abbreviations | |
077cc2fe8c4c016045fdddf02703eea4 | 102 797-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO 24102-4 [1], ISO 24102-5 [2], TS 102 797-1 [3], TS 102 797-2 [4], ISO/IEC 9646-1 [5], ISO/IEC 9646-2 [6], ETS 300 406 [7], ES 201 873-1 [8], ES 201 873-7 [9], ES 202 784 [10], ISO 24102-3 [i.1], ISO 21217 [i.2], ISO 21218 [i.3] and EG 202 ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.