hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.2 General Format | The web-based AML messages are sent using the HTTPS protocol, which offers encryption and authentication to secure the delivery of location messages. Each message consists of a number of header fields and a body, holding the content for the message. For an AML message it shall use the common format used for web-based f... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.3 Security considerations | There are two possible routes for the message to be sent to the Public Safety Answering Point (PSAP). Either the message is sent directly from the handset, or it could be sent via an intermediate server (i.e. not the AML endpoint server): a) If direct from the handset, the handset's Operating System (OS) will not be ex... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.4 Header | The HTTPS header contains a number of standard fields, including content-type, content-language and so on. As noted above, if an Intermediate Server is being used it is also recommended to include extra header fields to help deal with the messages. A password would increase security slightly, a message type would help ... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.5 Body | The body of the message shall consist of a number of name-value pairs, just as for any web-based form application. These shall hold the values sent from the handset, including location details and handset identification. This is not a fixed length message and not all name/value pairs are required as detailed in annex B... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.6 Detailed Format | |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.6.1 Header | The following fields should be added to the HTTPS header by an intermediate server to help the PSAP in dealing with the message. ETSI ETSI TS 103 625 V1.2.1 (2022-04) 16 Table 1 Name Format Description MsgType String up to 16 chars Operating System used by originating handset Password String up to 16 chars Simple strin... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.6.2 Body | The data should come through in the body of the POST message as a block of text following the x-www-form- urlencoded format: using the & character as a field separator and the = character to separate field name and value. A portion of the message will look like this: ….location_time=1471528826884&cell_home_mcc=234&devi... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.7 Receipt of HTTPS Message by PSAP | |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.7.1 Overview of message receipt | To receive HTTPS messages PSAPs shall implement a web server application that receives the HTTPS messages. |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.7.2 Example Message Sequence | Figure 4 ETSI ETSI TS 103 625 V1.2.1 (2022-04) 17 |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.7.3 Example Message Content | The following text shows an example message body from an HTTPS message, including the optional fields (for example device_model). Note that there are no spaces in the text. V=1&device_number=%2B447477593102&location_latitude=55.85732&location_longitude=- 4.26325&location_time=1476189444435&location_accuracy=10.4&locati... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.7.4 Response Values | The standard HTTP values shall be used for the response message from the PSAP server. In particular the following values shall be used: • 200 - OK, and other 2XX codes should also be accepted. • 400 - bad format. • 401 - authentication failed. • 500 - internal server error. The HTTP response code should only be used to... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.8 Limitations | |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.8.1 Availability of MSISDN | Emergency services need to be able to match the voice call with the data message, and to do so they can use the Mobile Station International Subscriber Directory Number (MSISDN). In some instances, the MSISDN can be accessed by the handset's AML functionality (e.g. from the SIM card or information entered by the subscr... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 6.4.8.2 Data connectivity | There is required to be a data connection for the HTTPS method to be used, which can be provided by either an authorized connection to the 3GPP network or to a Wi-FiTM access point. For the 3GPP connection the user may also need to have credit to support a chargeable transaction, as it is not thought to be readily poss... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 7 Mobile Network capabilities | |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 7.1 Simultaneous SMS/HTTPS and emergency voice | As an important development consideration, AML functionality shall not interfere with the voice emergency communication. The mobile network shall be able to simultaneously support a standard 3GPP emergency voice call, establishment of GNSS/Wi-FiTM location and AML transmission to the PSAP by the chosen transport mechan... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 8 Operational Guidance | |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 8.1 PSAP reception of location (location endpoint) | Emergency services are organized differently in each country. In some countries there is only one centralized PSAP receiving all 112 calls from all areas of the country, but in others, there is one PSAP for each region or for each province. The AML information is sent to a single AML end-point for each country which is... |
0babc727d3ba332c662f434a5ba454ca | 103 625 | 9 Next Generation 112 | Communication Provider networks and PSAPs are moving to SIP as part of their migration to Next Generation 112. When VoLTE or VoNR are used for emergency communications, SIP signaling is used for call orgination and management and also conveyance of location per IETF RFC 6442 [3]. ETSI TS 103 479 [5] defines how to conv... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 1 Scope | The scope of the present document is to define the high level system requirements for reconfigurable Radio Equipment enabling the provision of Radio Applications. The work is based on the Use Cases defined in ETSI TR 103 062 [i.1], ETSI TR 102 944 [i.2], ETSI TR 103 585 [i.3] and ETSI EN 302 969 [i.4]. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 2 References | |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 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... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 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 103 062: "Reconfigurable Radio Systems (RRS); Use Cases and Scenarios for Software Defined Radio (SDR) Reference Architecture for Mobile Devic... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 3 Definition of terms, symbols and abbreviations | |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 3.1 Terms | For the purposes of the present document, the following terms apply: distributed computations: model in which components located on networked computers communicate and coordinate their actions by passing messages interacting with each other in order to achieve a common goal Functional Block (FB): function needed for re... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 3.2 Symbols | Void. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASIC Application Specific Integrated Circuit BER Bit Error Rate CAT CATegory CR Cognitive Radio FB Functional Block FEC Forward Error Correction FFT Fast Fourier Transform HAL Hardware Abstraction Layer IoT Internet of Things IR Intermediate R... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 4 Requirement Organization and Methodology | |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 4.0 General | This clause is containing the description of how the requirements are organized and the related format. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 4.1 Requirement Organization | As shown in Figure 1, all requirements described in the present document belong to one single category (the functional requirements category). Requirements are, in turn, organized into groups. ETSI ETSI TS 103 641 V1.1.1 (2019-03) 9 Figure 1: Overall requirements structure |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 4.2 Requirement Format | A letter code system is defined which makes a unique identification of each requirement R-<CAT>-<GROUP>-<XX>. Each requirement is constructed as follows: • R-: Standard requirement prefix. • <CAT> Code Category FUNC Functional aspects • <GROUP>: Requirement group identifier. A letter code will be used for this identifi... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 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> • Description: the description of a requirement will be formulated using the terms as described in the clause "Modal verbs terminology" above. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 5 Working assumptions | |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 5.1 Assumptions | |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 5.1.1 Radio Equipment Reconfiguration Classes | As it is expected that the reconfiguration capabilities of a Radio Equipment will evolve over time, Radio Equipment Reconfiguration Classes (RERC) are introduced. As shown in Figure 2, 7 different classes of reconfigurable RE are introduced (RERC-0 corresponds to a non-reconfigurable device). Figure 2: Definition of RE... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6 Functional Requirements | |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.1 Requirements on RAT Link Support and Management | 6.1.1 R-FUNC-RAT–01 Function for RERC-1 to RERC-7 A reconfigurable radio equipment should support parallel connections to more than one Radio Access Technology. 6.1.2 R-FUNC-RAT–02 Function for RERC-1 to RERC-7 If a reconfigurable radio equipment allows parallel connections to RATs (in alignment to R-FUNC-RAT-01), in-d... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.2 Radio Application Requirements | |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.2.0 General | The following requirements are based on the Use Cases described in ETSI TR 102 944 [i.2]. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.2.1 R-FUNC-RA-01 Radio Applications Support for RERC-1 to RERC-7 | Reconfigurable radio equipment shall support the execution of Radio Applications. ETSI ETSI TS 103 641 V1.1.1 (2019-03) 14 |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.2.2 R-FUNC-RA-02 Composition for RERC-1 to RERC-7 | Radio Applications shall be composed of SFBs and/or UDFBs. Explanation: The resulting Radio Applications will be composed by combining SFBs and/or UDFBs. They will be used, for example, for baseband signal processing and real-time Media Access Control (MAC) data processing. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.2.3 R-FUNC-RA-03 Concurrency for RERC-1 to RERC-7 | Reconfigurable radio equipment should support concurrent execution of Radio Applications. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.2.4 R-FUNC-RA-04 Data for RERC-1 to RERC-7 | Radio Applications should support the function of transferring receive (Rx)/transmit (Tx) data to/from the networking stack. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.2.5 R-FUNC-RA-05 Context Information for RERC-1 to RERC-7 | Radio Applications should support the function of delivering context information. Explanation: Access to context information metrics is provided. As an example, the metrics can be related to: Signal to Interference-plus-Noise Ratio (SINR) Received Signal Strength Indication (RSSI) Packet Error Rate (PER) Bit Er... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.2.6 R-FUNC-RA-06 Pipelining for RERC-2 to RERC-7 | Radio Applications shall be applicable to fixed pipeline, programmable pipeline, and hybrid pipeline architectures. Explanation: The pipeline of functional blocks is determined by the contents of metadata included in the Radio Application Package. Modem chip manufacturer selects one of the 3 pipeline structures for the... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.3 Radio Application Functional Block Requirements | |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.3.1 R-FUNC-FB-01 Implementation for RERC-2 to RERC-7 | Each instance of a functional block shall be implemented with a corresponding program code characterized by the implementation properties and shall be accessed by a corresponding interface. ETSI ETSI TS 103 641 V1.1.1 (2019-03) 15 Explanation: The typical structure of the functional block is shown in Figure 3. The corr... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.3.2 R-FUNC-FB-02 Execution for RERC-2 to RERC-7 | Each instance of a functional block shall be executed only by calling the corresponding interface. Explanation: The execution of an instance of a functional block requires an external trigger, for example in order to avoid recursion. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.3.3 R-FUNC-FB-03 Side Effects for RERC-2 to RERC-7 | The internal state of an instance of each functional block shall not be shared with any other instances of functional blocks. Explanation: The behaviour of an instance of a functional block depends only on its inputs and not on the state of another instance of a functional block. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.3.4 R-FUNC-FB-04 Shared Data for RERC-2 to RERC-7 | The reconfigurable radio equipment should support data sharing with other instances of functional blocks. Explanation: Input and/or output of each functional block can be shared with other instances of functional block(s). |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.3.5 R-FUNC-FB-05 Concurrency for RERC-2 to RERC-7 | The reconfigurable radio equipment should support the concurrent execution of instances of functional blocks. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.3.6 R-FUNC-FB-06 Extendability for RERC-2 to RERC-7 | A library extension shall be supported. Explanation: A Radio Application consists of UDFBs as well as SFBs. Meanwhile, the Radio Library of a reconfigurable radio equipment consists of SFBs only and not of UDFBs. Therefore, the reconfigurable radio equipment needs a normative library extension to support UDFBs. In othe... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.4 Radio Equipment Reconfiguration Requirements | 6.4.1 R-FUNC-RER-01 Platform-specific Executable Code for RERC-2, RERC-3 or RERC-4 The configuration of a reconfigurable radio equipment compliant to RERC-2, RERC-3 or RERC-4 shall be realized with a Radio Application Package of which the user defined functional blocks, if any, are provided in platform-specific executa... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.4.4 R-FUNC-RER-04 Radio Programming for RERC-1 to RERC-7 | The reconfigurable radio equipment shall provide a suitable interface which conveys structural and behavioural information of RAs for the reconfigurable radio equipment reconfiguration. Explanation: The interface enables the provision of reconfiguration code onto the reconfigurable radio equipment. The structural infor... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.4.5 R-FUNC-RER-05 Dynamic Execution for RERC-4, and RERC-7 | The reconfigurable radio equipment shall support dynamic execution of functional blocks. Explanation: In case of dynamic Resource sharing, the Resource allocation is performed in run time. 6.4.6 R-FUNC-RER-06 Independency on Memory Model for RERC-1 to RERC-7 Different radio platform memory models shall be supported. Th... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.4.7 R-FUNC-RER-07 Code for RERC-2 to RERC-7 | The interface related to R-FUNC-RER-04 shall support the provision of executable code (for RERC-2 to RERC-4) and IR and/or Source Code (for RERC-5 to RERC-7). |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.4.8 R-FUNC-RER-08 IR Format for RERC-5 to RERC-7 | IR shall be defined in a format suitable for human reading/writing and automated processing. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.4.9 R-FUNC-RER-09 Timing Constraints for RERC-1 to RERC-7 | The interface related to R-FUNC-RER-04 shall support timing constraints for radio processing. Explanation: This requirement relates to real time execution. The execution of concerned functional blocks will be in accordance to the provided timing constraints. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.4.10 R-FUNC-RER-10 Platform Independency for RERC-5 to RERC-7 | The reconfigurable radio equipment architecture shall provide suitable interfaces in order to ensure platform independency. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.4.11 R-FUNC-RER-11 Radio Application for RERC-5 to RERC-7 | The Software representation (i.e. IR or Source Code) of an RA shall be independent of the target hardware platform. Explanation: The independence of the RA from the target hardware platform indicates that the RA can be provided to multiple platforms supporting the interfaces related to R-FUNC-RER-10. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.4.12 R-FUNC-RER-12 Function Granularity for RERC-1 to RERC-7 | Functional blocks may have different granularity. Explanation: The functional blocks might be for example arithmetic operations or functions like FFT or even whole Radio Applications like WiFi, LTE, etc. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.4.13 R-FUNC-RER-13 Radio Virtual Machine for RERC-2 to RERC-7 | Radio Application(s), SFB(s) or UDFB(s) shall be executed on a suitably configured Radio Virtual Machine, including the application of a suitable protection class. Explanation: A RVM execution environment should be provided in such a way that a proper RVM (protection) class can be selected by each vendor. The RVM appro... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.5 Radio Frequency (RF) Transceiver Requirements | |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.5.0 General | The following requirements are related to the RF transceiver which allows for the selection of RF configuration parameters. However, it does not limit the manufacturer in the choice of supported features in a given platform. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.5.1 R-FUNC-RFT-01 RF Configuration for RERC-1 to RERC-7 | The reconfigurable radio equipment shall provide a suitable interface for RF transceiver configuration. Explanation: The interface will enable the exchange of control and data information between the Radio Applications and the RF transceiver. ETSI ETSI TS 103 641 V1.1.1 (2019-03) 20 6.5.2 R-FUNC-RFT-02 Extendibility fo... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.6.0 General | The following requirements are related to End-to-End Security which allows to ensure that only approved Radio Applications may be downloaded to and executed on a target Radio Equipment. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.6.1 R-FUNC-SEC-01 REConfPol-RAP-Security | Cryptographic functions shall be provided to support the digital signature strategy providing confidentiality, integrity, and authenticity of RE Configuration Policy and RAP(s), and the non-repudiation strategy. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.6.2 R-FUNC-SEC-02 Administration-Security | A security function in the Communication Service Layer shall ensure that only approved RAP(s) are processed and executed on a target platform. Explanation: Typically, an Administrator Security Function is added to the Administrator entity in the Communication Service Layer. |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.6.3 R-FUNC-SEC-03 Secure Management | Security functions shall be provided to allow remote parties to securely attest to the status of the Radio Equipment, configure the Radio Equipment, and manage it over extended period of time. Explanation: Typically, an Attesting Entity is present on the device (possibly in a distributed fashion), that can act as a roo... |
ec7519964e2e1ed76a1ab9836b769a8d | 103 641 | 6.6.4 R-FUNC-SEC-04 Root of Trust | A root of trust shall provide security services to the reconfigurable platform. Explanation: components are required in order to provide a high level of security assurance throughout the lifecycle of the Radio Equipment. ETSI ETSI TS 103 641 V1.1.1 (2019-03) 22 History Document history V1.1.1 March 2019 Publication |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 1 Scope | The present document covers following applications: • Liquid cooling at the cabinet/rack level. • Liquid cooling at the product level. • Liquid cooling via immersion in dielectric liquid. The present document specifies the following items: • Liquid circulation layout (connection of multiple units). • Liquid flow rate r... |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 2 References | |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 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... |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 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... |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 3 Definition of terms, symbols and abbreviations | |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 3.1 Terms | For the purposes of the present document, the following terms apply: cabinet: free-standing and self-supporting enclosure for housing electrical and/or electronic equipment component: part or sub-part of an equipment that dissipates heat and needs to be cooled CoolEff: ratio between the energy consumption of the equipm... |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: Cp Specific heat (J/kg/°C) dP Pressure drop (Pa) P Electrical power consumed by the equipment (W) Qm Mass flow rate (kg/s) Qvair Air volume flow rate (l/min). Qvliquid Liquid volume flow rate (l/min) ρ Liquid density (kg/m3) T Temperature (°C) Tamb ... |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AC Alternating Current CDU Cooling Distribution Unit CTE Coefficient of Thermal Expansion DC Direct Current HEX Heat Exchanger ICT Information and Communication Technology IEC International Electrotechnical Commission ISO International Organiz... |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 4.1 Introduction | In the present clause, the liquid cooling requirements and energy efficiencies of equipment are defined. |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 4.2 Cooling requirements for equipment | Liquid cooled equipment for non-weather protected locations shall be compliant with ETSI EN 300 019-1-4 [2] and shall be compliant with any of the liquid inlet temperature class defined in table 1. Liquid cooled equipment for weather protected locations shall be compliant with ETSI EN 300 019-1-3 [1] and shall be compl... |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 4.3 Liquid cooled equipment energy efficiency | Energy efficiency targets shall be measured in the following normal conditions: • External (Outdoor) temperature Text = 45 °C. • Ambient (Room) temperature Tamb = 25 °C. The equipment power consumption shall be considered at its maximal value. The key indicator shall represent the impact of the cooling energy on the wh... |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 5 Specifications for liquid cooling solutions | |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 5.1 General requirements | Liquid cooled equipment shall be compliant with ETSI EN 300 019-1-3 [1] or ETSI EN 300 019-1-4 [2] depending on their locations. |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 5.2 Liquid flow rate range vs. dissipated power | Liquid flow rate (in l/min) and dissipated power are linked by the following steady state power balance: QV = (60 000 x P) / (ρ x Cp x (Tliq_out - Tliq-in)) |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 5.3 Temperature of touchable parts | For safety purpose, the temperature of touchable part will be compliant with the applicable safety standards (e.g. EN 60950-1 [i.1] or IEC 62368-1 [i.3]). |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 5.4 Maximum pressure drop per liquid flow rate | Pressure drop per liquid flow rate shall not be higher than: dPliquid = 25 x Qvliquid² Qvliquid is the liquid volume flow rate expressed in l/min. |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 5.5 Maximum pressure drop per air flow rate | If the cooling system consists in transferring heat from air flow to liquid flow (examples in clause B.1), pressure drop per air flow rate shall not be higher than: dPair= 1,3 x 10-6 x Qvair² Qvair is the air volume flow rate expressed in l/min. |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 5.6 Pipe threads | If pipe threads are used, they shall be compliant with ISO 228-1 [3]. ETSI ETSI TS 103 586 V1.3.1 (2022-10) 11 |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 5.7 Coolants and cooling distribution units | If the equipment is cooled internally by another closed loop fluid than the liquid used at the room and building level (e.g. oil, low pressure two phase fluid, very pure water), the supplier shall provide CDU(s) with at least N+1 system-level pump redundancy to adapt to room where water cooling is available (where N is... |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 5.8 Max pressure and tightness | The equipment shall be tested at a pressure level of three times of the nominal pressure with the method described in EN 805 [7]. To ensure proper operation of the whole cooling system, commissioning shall be made at full load. |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 5.9 Liquid connectors positions | For equipment installed on raised floors, fluid connections shall be provided at the bottom of the rack/cabinet. For equipment installed on slab floors, fluid connections shall be provided at either the top or the bottom of the rack/cabinet. |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 5.10 Accessibility in case of cooling with heat exchanger | If the HEX is not a part of the cabinet, it shall be easily moved to gain access to equipment for servicing. If the HEX is a part of the cabinet (for example figure B.1c), it shall be easily removed or be mounted on a door to gain access to equipment for servicing. 6 Benchmark methods to evaluate cooling system efficie... |
0f3218d1eea758ab415ff66b3c95b87d | 103 586 | 7 Reliability test requirement | If a CDU is provided, it shall be considered as a part of the equipment, the CDU should be tested with ICT equipment. If the liquid cooling is compatible with different types of liquids, all types of liquids should be tested. The liquid cooling test requirements related to reliability of system shall be as defined in t... |
ec9366d6891164f86d2e1eadea31eda0 | 103 584 | 1 Scope | The present document defines an audio renderer associated with the DTS-UHD codec defined in ETSI TS 103 491 [1]. The inputs to the renderer are one or more sets of audio waveforms along with mixing instructions, and the output is a single set of waveforms mapped to a defined speaker configuration. Each set of waveforms... |
ec9366d6891164f86d2e1eadea31eda0 | 103 584 | 2 References | |
ec9366d6891164f86d2e1eadea31eda0 | 103 584 | 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... |
ec9366d6891164f86d2e1eadea31eda0 | 103 584 | 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... |
ec9366d6891164f86d2e1eadea31eda0 | 103 584 | 3 Definitions and abbreviations | |
ec9366d6891164f86d2e1eadea31eda0 | 103 584 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: audio object: waveform or set of waveforms that have been assigned a location in space hull: collection of points forming a surface mesh to be used as a basis for panning output feeds: set of audio waveforms mapping one to one to the p... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.