hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.3 Input processing | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.3.1 Reception of parent Transport Streams | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.3.1.1 Overview | The Daughter Site Adapter (DSA) receives one or several parent multiplex(es). Those are indicated by the DSA Configuration Information (DSACI) the DSA receives from the CSG (see clause 5.7). The Daughter Site Adapter receives one or several parent Transport Streams. These DVB TS packets may be received over any standar... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.3.1.2 Arrival timestamping | For each input TS on interface(s) H, packets shall have a timestamp (__) computed according to the incoming PCRabs values: • For the packet of index n, holding the kth PCRabs value in adaptation field: __ = • For packet of index p, holding the (k+1)th PCRabs value in adapta... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.3.1.3 Calculation of Virtual Arrival Timestamps (VATs) | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.3.1.3.1 Overview | The Virtual Arrival Timestamping method enables insertion of TS packets that are not present in the Parent Signal or of TS packets that are regenerated by the DSA. This may be done to save bandwidth in the Parent Signal, for example by generating DTT PMT or EIT sections on daughter site as an alternative to receiving t... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.3.1.3.2 CBR operation mode | The Virtual Arrival Timestamp of TS packets is calculated by the DSA based on a time interval indicated as part of the DSA Configuration Information. The time interval in question is equivalent to the indicated table_repetition_period. The DSA converts that table_repetition_period into a time interval for the insertion... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4 TS re-multiplexing | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.1 Overview | The TSs for each PLP shall be created by first generating a Reference TS (see clause 6.4.2), and then replacing null packets with selected packets from the incoming parent TSs, with packets stemming originally from the incoming parent TSs but were modified, and with packets generated locally by the DSA. Figure 6 illust... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.2 Generation of Reference Transport Streams | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.2.1 Overview | A Reference Transport Stream (RTS) is a Transport Stream made up entirely of null packets (ISO/IEC 13818-1 [5]) but with a defined timing in terms of the SIS system clock. Each packet is connected to an associated PCRabs value. The Reference Transport Stream acts as a placeholder with correct time positions for the nul... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.2.2 DVB-T2 case | There shall be one RTS for each data PLP, but the RTSs for the PLPs within the same PLP_GROUP shall be identical in case a common PLP is present, see ETSI EN 302 755 [2]. The RTS shall include packets with PCRabs values equal to values of the PCRFTSP signalled in the F&TI signalling packets for the relevant PLP. Betwee... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.2.3 DVB-T case | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.2.3.1 Overview | In the case of DVB-T, a mega-frame building block, see ETSI TS 101 191 [4], sits between the Reference Transport Stream generator and the TS remultiplexer, see figure 6. The latter remultiplexer is directly connected to interface L, see figure 6 as well. |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.2.3.2 Extraction of F&TI packets | The F&TI packets are extracted by the DSA. The modulation parameters TPS are derived from the F&TI packets. The DSA shall remove the megaframe_timestamping function when building the MIP packet for the DVB-T transmission and shall change the PID to the standardized PID 1516. PCRabs is then assigned to the MIP packet. T... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.3 Selection of relevant content from input TSs | The services and service components that shall be extracted for terrestrial re-transmission are determined by the DSA Configuration Information (DSACI). Within a Transport Stream, the TS packets are selected by PID. The PID component selection shall also be used for remapping of PSI/SI sent on hidden PIDs as per clause... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.4 Processing and generation of Layer 2 signalling (PSI/SI) | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.4.1 Background | Terrestrial PSI/SI is inserted into the output TS in a way that it enables the receiver/decoder to select and locate the broadcast services and the components of the services. PSI/SI is partly dynamic and time-accurate to support changes in the service status and changes in the service composition. PSI/SI for the terre... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.4.2 Pass-through remultiplexing of selected parent tables/sections | When a Parent Signal component is also applicable to a DTT multiplex, it may be passed to the output without content modification. When the CSG builds a DSACI that complies with this situation (see clause 5.7), the DSA shall pass- through all packets of the target PSI/SI component. According to the DSACI, the output PI... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.4.3 Conversion of parent table/sections on the fly (patching) | In addition to the method described above, the conversion mechanism may be used to modify table attributes according to the DSACI inserted by CSG (see clause 5.7). This method is applicable when the modified table does not need re- packetization: Only CRC updates and section invalidation using stuffing sections are all... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.4.4 Static table regeneration | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.4.4.1 Overview | • PAT, PMT , SDT, CAT regeneration: - The PAT table is created in compliance with ISO/IEC 13818-1 [5], clause 2.4.4.3. The DSACI configures the TS_id, version_number and lists the output program_number and the associated PMT_PIDs. The services are asserted in ascending order based on the output program_number. - The CA... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.4.4.2 SDT and BAT regeneration | The SDT table is created in compliance with ETSI EN 300 468 [6], clause 5.2.3. DSACI supplies the transport_stream_id, the version_number, the ONID, the list of input service to select. Each service_id_is associated with the output service_id with EIT_schedule_flag, EIT_present_following_flag, running status, free_CA_m... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.4.5 Dynamic table regeneration | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.4.5.1 Overview | The Event Information Tables (EITs) shall provide the output (DTT) transport streams with information about: • the Present/Following events for the Actual / Others DTT Transport Streams; and • the Scheduled events for the Actual / Others DTT Transport Streams. The repetition rates of the EIT tables for DTT systems shal... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.4.5.2 Phase (A): Creation of a list of EIT_slots | For each output (DTT) multiplex, a DSACI configuration file specifies the EIT_insertion_window duration, the repetition rate EIT_repetition_rate (EIT_category (i)) required for all I categories of EIT and the list of services extracted from various input (DTH) multiplexes to build up the "actual" and the "others" outpu... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.4.5.3 Phase (B): Creation of the EIT_sections database | The EIT_sections database shall be populated by Nb_records records as outline with figure 12, the EIT_sections_data being elements extracted from the input (DTH) Transport Stream(s). Figure 12: EIT_sections database entry Where Nb_records is defined as follows: Nb_records = 0; for (i=0; i < number_of_Category; i++) { f... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.4.5.4 Phase (C): Playout of the EIT_slots list | All elements in these arrays are time-stamped with a "Arrival Time-Stamp". In the case of the filtered EIT_sections, the timestamp is a "Virtual Arrival Time-stamp" (VAT). The "VAT" computation of EIT TS packet is described below. The VAT for each EIT_slot is computed using the EIT_offset defined for each EIT_slot and ... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.4.5.5 Parameter definitions | EIT_category: An EIT_category regroups all the sections associated to a given type (actual or other) and a given horizon, the different EIT_categories are defined in table 18. EIT_slot: a time interval associated to a given service for a given EIT_category. EIT_sections: EIT table sections. EIT_insertion_window_duratio... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.5 Placement of incoming packets in the outgoing TS | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.5.1 Overview | The deterministic scheduling of incoming packets is based on the arrival timestamps computed at the input, in conjunction with the departure timestamps from the Reference TS generation. Incoming packets - and locally DSA-generated packets (belonging to PSI/SI tables regenerated by the DSA), which are equipped with Virt... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.4.5.2 Deterministic scheduling | Scheduling is based on a first-in first-out process, with additional rules to solve packet collisions. The following rules apply for selecting an input TS packet for insertion into an output TS performed by the deterministic TS remultiplexer: • An input TS packet that has to be played out replaces the first null packet... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.5 Framing | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.5.1 DVB-T2 case | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.5.1.1 TS splitting (optional) | The PLP_GROUP_ID and PLP_TYPE fields of the configurable L1-post signalling - see ETSI EN 302 755 [2] - shall be used to determine whether a data PLP belongs to a PLP group. Each group of PLPs may contain one common PLP. If a common PLPs belongs to a PLP group, the TS Splitting model defined in Annex D of ETSI EN 302 7... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.5.1.2 Partial Mode Adaptation | Mode Adaptation shall be performed on the TS (or TSPS) for a given PLP that was generated as described in clause 6.4 (if common PLPs are used, see also clause 6.5.1.1 and ETSI EN 302 755 [2], Annex D). The partial Mode Adaptation process shall comprise: • SYNC byte removal. • Dummy ISSY insertion (if applicable). • Dum... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.5.1.3 Allocation of TS bits to Interleaving Frames | The bits of the partially Mode-Adapted Transport Stream (see clause 6.5.1.2) shall be allocated to Interleaving Frames according to the signalling in the T2-MI packet of type F016 (F&TI) extracted in clause 6.6. If Null Packet Deletion (NPD) is not enabled, the bits shall be allocated such that the first complete packe... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.5.1.4 Null Packet Deletion | If enabled, Null Packet Deletion shall now be performed. The DSA shall perform the following process: • The last complete packet of an Interleaving Frame shall always be transmitted, i.e. it shall not be deleted. • Any other null packet shall be deleted unless 255 previous null packets have already been deleted, in whi... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.5.1.5 ISSY generation | The three ISSY variables are inserted according to ETSI EN 302 755 [2]. When BUFS is inserted, it shall have the value indicated by BUFS in the relevant F&TI T2-MI packet (see clause 5.6.2) for the relevant PLP. When ISCRlong is used, the third byte shall be coded as defined in ETSI EN 302 755 [2]. TTO is inserted once... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.5.1.6 Generation of BBFRAMEs | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.5.1.6.1 Overview | The bits allocated to an Interleaving Frame shall be mapped onto the number of BBFRAMEs indicated in the dynamic L1 signalling for the relevant PLP and Interleaving Frame. The relevant L1 signalling will be contained in an L1-current T2-MI packet extracted as described in clause 6.6. The number of bits allocated to an ... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.5.1.6.2 Allocation of bits to the BBFRAMEs of the Interleaving Frame | In the case of not applying NPD, the number of payload bits in the Interleaving Frame number n is: = _ + _ _ × −_ + 1 FIRST_SYNCD(n) is signalled by the FIRST_SYNCD field of the Framing & Timing Information for Interleaving Frame n. FIRST_SYNCD(n+1) is identical t... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.5.1.6.3 Mapping of mode-adapted bits into the BBFRAMES | The bits of the mode-adapted TS shall be mapped into the Data Fields of the BBFRAMEs of the Interleaving Frame according to the DFL values of the BBHEADERs calculated as described in clause 6.5.1.6.2. |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.5.1.6.4 BBHEADER generation | BBHEADERs are part of each BBFRAME and are 10 bytes long. Depending on the mode used - Normal Mode (NM) or High Efficiency Mode (HEM), see ETSI EN 302 755 [2] - they consist of the parameters outlined below with figures 13 and 14, respectively. Those figures illustrate the two header formats. The related parameter defi... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.5.2 DVB-T case | As explained in clause 6.4.2.3, the DVB-T-related mega-framing takes place as part of the TS re-multiplexing stage - between the Reference Transport Stream generator and the TS re-multiplexer. Between the TS re-multiplexer and the DSA output interface L no further processing is applied to the stream of DVB-T mega-frame... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.6 Extraction of T2-MI packets | T2-MI packets (see ETSI TS 102 773 [1]) are received by the DSA in encapsulated form, i.e. embedded in TS packets compliant to the data piping method specified in ETSI TS 102 773 [1]. All T2-MI packets are decapsulated from the aforementioned TS packets - should their PID identify a T2-MI stream whose content is requir... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.7 Output processing | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.7.1 DVB-T2 case | |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.7.1.1 T2-MI multiplexing | When addressing DVB-T2 modulators with a T2-MI stream, the DSA inserts the L1 signalling - received via one of its inputs - into the output T2-MI stream. All T2-MI packet types - apart from types 0016 and F016 - shall be inserted unmodified into the output T2-MI stream. The order of T2-MI packets at the related input o... |
2856f86d792d9715f54e6f6c52d19dc8 | 103 615 | 6.7.1.2 Transport of T2-MI packets in MPEG-TS | The encapsulation of the T2-MI packets into TS packets shall follow the data piping mechanism described in ETSI TS 102 773 [1]. The overall TS bitrate, the PID value of the encapsulated T2-MI stream, and the presence of PCR may follow the related DSACI parameter settings, but other user-defined values may be used. For ... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 2 References | |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 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... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 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... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 3 Definition of terms, symbols and abbreviations | |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 3.1 Terms | For the purposes of the present document, the following terms apply: allowance zone: geographical area within which a radio equipment is allowed to operate radio transmitters on its assigned spectrum resource NOTE 1: An allowance zone is defined using specific measurement quantities and thresholds, e.g. a maximum field... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 3.2 Symbols | Void. ETSI ETSI TS 103 655-1 V1.2.1 (2022-09) 8 |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3G (mobile) Partnership Project COM Communications CON Context dBµ deciBel relative to one microvolt EIRP Effective Isotropic Radiated Power EU European Union FPGA Field Programmable Gate Array FUNC Functional aspects GNSS Global Navigati... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 4 Requirement Organization and Methodology | |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 4.1 Requirement Organization | The requirements are organized into two categories. Category one defines the function requirements and category two the performance requirements. Both categories are further split up into different groups. Figure 1 visualizes the categories and its enclosed groups. ETSI ETSI TS 103 655-1 V1.2.1 (2022-09) 9 Figure 1: Re... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 4.2 Requirement Format | A letter code is defined to uniquely identify each requirement R<CAT><GROUP><XX>. It is constructed as follows: • R-:standard requirement prefix. • <CAT>: Code Category FUNC Functional aspects PERF Performance aspects • <GROUP>: Requirement group identifier. A three letter code will be used for this identifier. • <XX>:... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 4.3 Requirement Formulation | A requirement is formulated in such a way that it is uniquely defined. It is built as follows: • Title: <Title Description> |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 5 Working Assumptions | The working assumptions described below are based on ETSI TR 103 587 [i.1]. There a radio interface engine is defined to comprise the following use cases which all rely on context information, such as current and predictive location information of the wireless device: • Decision making based on context information of e... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6 Functional System Requirements | |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.1 Requirements for radio and hardware processing resources | |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.1.1 R-FUNC-RHR-01: Reconfiguration for each WD | The system shall support the reconfiguration of both the Hardware Processing Resources (HPR) and the Radio Resources (RR) for each supported Wireless Device (WD). Explanation: The system should be able to perform resource reconfiguration of both the hardware processing resources and the radio resources for each support... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.1.2 R-FUNC-RHR-02: Reconfiguration between WDs | The system shall support reconfiguration of both HPR and RR between different WDs. Explanation: The system can reconfigure multiple WDs with flexibility in terms of the percentage of HPR and RR between different WDs according to the status of the network. |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.2 Requirements for functions supporting the reconfiguration | |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.2.1 R-FUNC-REC-01: Gathering and processing function | The system shall support a gathering and processing function to gather and process radio related metrics and parameters. Explanation: After having gathered radio related metrics and parameters, the gathering and processing function may process them to make decisions on reconfiguration in order to optimize radio perform... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.2.2 R-FUNC-REC-02: Support of trigger events for reconfiguration | The system shall support trigger events for reconfiguration. ETSI ETSI TS 103 655-1 V1.2.1 (2022-09) 11 Explanation: Trigger events are described by certain parameters (e.g. thresholds, hysteresis) in order to define the condition under which an event is happening. When one or more events occur, the system starts to ev... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.2.3 R-FUNC-REC-03: Support for reconfiguration function | The system shall support a reconfiguration function to make decisions for radio resource reconfiguration and inform RBSs to perform the reconfiguration e.g. triggered by events in clause 6.2.2. Explanation: The reconfiguration function shall make radio resource reconfiguration decisions such as, reconfiguration time, r... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.2.4 R-FUNC-REC-04: Support for execution function | The system shall support the execution function in order to perform the reconfiguration. Explanation: The system WDs should support mechanisms in order to be reconfigured according to the reconfiguration decision of the reconfiguration function. EXAMPLE: An example is to exchange location estimates between WDs to impro... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.2.5 R-FUNC-REC-05: Support of learning function | The system shall support a learning function to improve and optimize the reconfiguration decisions. Explanation: For example, the learning capability may consist in monitoring the performance of the system after each reconfiguration and verifying whether the decisions meet or not the reconfiguration target. Another pos... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.2.6 R-FUNC-REC-06: Support of information provisioning function | The system shall support an information provisioning function to provide updated network configuration information to the appropriate system devices. Explanation: After a reconfiguration, the information related to the new network configuration and policies are expected to be efficiently provided to the system devices ... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.3.1 R-FUNC-MOB-01: Mobility management of the WDs | The system shall guarantee the mobility management of the WDs. Explanation: Network reconfiguration (e.g. change of WD in currently used band or starting operations in a new band using a WD already deployed or a new WD) may imply the change of radio parameters, such as neighbour cells relation information (e.g. the nei... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.3.2 R-FUNC-MOB-02: Connectivity management of the WDs | The system shall manage the connectivity of the WDs during the reconfiguration. Explanation: When a WD is in connected mode and operating on radio resources that may be reconfigured, an appropriate decision has to be evaluated by the system in order to maintain the connectivity of the involved WDs. In the following, di... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.3.3 R-FUNC-MOB-03: Scalability of connections of the WDs | The system shall consider scalability of the potentially active mobile WDs that are either managed by the network or a central unit. EXAMPLE: Mobile WDs may operate in a peer-to-peer mode and demand resources (spectrum, power) in a predictive manner. Therefore, scalability is supported by the predictive demand of the m... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 6.3.4 R-FUNC-MOB-04: Support of authentication | The system shall support authentication methods to provide traceable and trustable data sources from WDs. Explanation: If data is exchanged between WDs that is used for determining the context information it is relevant that an authenticated source that can be trusted provides the information. Therefore, the risk of ch... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 7 Key Performance Requirements | |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 7.1 Key Performance Indicators for Communications | 7.1.1 R-PERF-KPI-COM-01: Selecting the best PHY/MAC of the communication system The system shall select the best PHY/MAC protocol depending on context information such as network and user requirements. EXAMPLE: A given WD, e.g. a Wi-Fi® node, is using a certain MAC protocol, which provides a certain QoS under the curre... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 7.1.2 R-PERF-KPI-COM-02: Reliability of the communication link | The system shall perform predictive handover to keep the transmission reliable. EXAMPLE: The acquired context information is exploited in order to identify the best possible working point for a concerned Wireless Equipment. For this purpose a combination of instantaneous observations together with historical (averaged)... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 7.1.4 R-PERF-KPI-COM-04: Preselecting relevant sensor data | The system shall preselect data that is maybe no longer relevant because it is outdated to improve the net-throughput. The decision can be done at the WD. EXAMPLE: The WD is sharing relevant correction data for ionospheric effects to improve GNSS based location estimation. If this data is outdated but will be used it c... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 7.2 Key Performance Indicators for Context Information | |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 7.2.1 R-PERF-KPI-CON-01: Accuracy of the localization estimation | The system shall assess the accuracy. Such an assessment may be performed by known ground truth points, or estimating the noise level, or the bias due to non-line-of-sight conditions. EXAMPLE: A set of known fixed ground truth points act as a reference points. Distance measurements depending on the reference points tog... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 7.2.2 R-PERF-KPI-CON-02: Integrity of the localization performance | The system shall assess the integrity of the estimated localization performance. EXAMPLE: Known reference points allow to establish an integrity level to derive a confidence level of exploitable context information. Other methods could be location measurement units share their integrity measurements to be prepared to d... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 7.2.3 R-PERF-KPI-CON-03: Geometric constellation of WD | The system shall assess the geometrical constellation of all active and passive WDs to decide how the location estimation process is affected, and therefore the resources are reasonably invested. ETSI ETSI TS 103 655-1 V1.2.1 (2022-09) 14 EXAMPLE: Two WDs that support the localization process are placed in line behind ... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 7.2.4 R-PERF-KPI-CON-04: Sensor reliability | The system shall assess the reliability of sensors that assess data to be integrated as context information (such as pressure and humidity) and provide the measurement data. EXAMPLE: Sensor information such as humidity or pressure could predict a change of the weather. Therefore rain could harm the transmission at cert... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 7.2.5 R-PERF-KPI-CON-05: Spectrum requirements | The system shall adapt the spectrum depending on the current accuracy requirements, especially in the context of a second WD. EXAMPLE: Broader spectrum allows estimate the ranging performance more accurately. However, depending on the requirements this is not necessary and could allow a second WD to estimate with its o... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 7.2.6 R-PERF-KPI-CON-06: Waveform adaptations | The system shall adapt the applied waveform to optimally choose the current waveform on scenarios with line-of-sight or non-line-of-sight conditions. EXAMPLE: The waveform determines the performance with a given spectrum. This is of interest in simultaneously ranging between WDs that are collocated. |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 7.2.7 R-PERF-KPI-CON-07: Location methods | The system shall adapt its location methods depending on the performance requirements, available sensor data, update rate and potential power consumption. EXAMPLE: Different location methods exist with constraints in respect to complexity, latency and used sensor data. The key constraints limit the power consumption an... |
e4f52c26d2c20002e3b67bd57c08f608 | 103 655-1 | 7.2.8 R-PERF-KPI-CON-08: Horizontal and vertical accuracy performance | The system shall differentiate between the horizontal and vertical accuracy performance. EXAMPLE: Human addressed use cases exploit location information only on a single floor (in the horizontal dimension). Therefore, the performance requirements shall be different between the horizontal and vertical dimension. ETSI ET... |
422ac8948550190292e4df89f508aa1f | 103 732-5 | 1 Scope | The present document defines a PP-Module for Consumer Mobile Device (CMD) which adds additional security requirements focused on the bootloader and storage configuration. The present document identifies key security requirements for how the bootloader should be configured to protect the integrity of the CMD. The presen... |
422ac8948550190292e4df89f508aa1f | 103 732-5 | 2 References | |
422ac8948550190292e4df89f508aa1f | 103 732-5 | 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... |
422ac8948550190292e4df89f508aa1f | 103 732-5 | 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... |
422ac8948550190292e4df89f508aa1f | 103 732-5 | 3 Definition of terms, symbols and abbreviations | |
422ac8948550190292e4df89f508aa1f | 103 732-5 | 3.1 Terms | For the purposes of the present document, the following terms apply: bootloader: program used to load the main OS (or alternative recovery systems or boot modes) into memory consumer mobile device: user customizable device utilizing an operating system, supporting installation and maintenance of applications, with wire... |
422ac8948550190292e4df89f508aa1f | 103 732-5 | 3.2 Symbols | Void. |
422ac8948550190292e4df89f508aa1f | 103 732-5 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CC Common Criteria CMD Consumer Mobile Device CEM Common Evaluation Methodology CPU Central Processing Unit ECD Extended Component Definition OS Operating System PP Protection Profile RoT Root of Trust SAR Security Assurance Requirement SFR Se... |
422ac8948550190292e4df89f508aa1f | 103 732-5 | 4 TOE Definition | |
422ac8948550190292e4df89f508aa1f | 103 732-5 | 4.1 TOE Overview | The Base-PP [6] does not specify any requirements related to the bootloader, apart to run a suite of self tests on it to verify its integrity (see FPT_TST.1 TSF testing in ETSI TS 103 732-1 [6]), or the establishment of a Root of Trust of the CMD. A Root of Trust provides a way to ensure that the device has not been ta... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.