hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.6.1 Authentication and Confidentiality | Refer to clause 8 for details concerning the use of IPsec to provide both authentication and confidentiality of the RADIUS messages, and the details of the correct usage of the RADIUS shared secret. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.6.2 Standard RADIUS Attributes | Each RADIUS message starts with the standard RADIUS header shown in table 22. Table 22: RADIUS Message Header Field Name Semantics Field Length Code Accounting-Request = 4 Accounting-Response = 5 1 byte Identifier Used to match accounting-request and accounting-response messages. 1 byte Length Total length of RADIUS me... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.6.3 IPCablecom RADIUS Accounting-Request Packet Syntax | <<RADIUS Accounting-Request> ::== <RADIUS message Header> <RADIUS NAS-IP-Address Attribute> <RADIUS Acct-Status-Type Attribute> <IPCablecom EM> <IPCablecom EM> ::== <RADIUS VSA for IPCablecom EM Header Attribute> <IPCablecom EM Attribute List> <IPCablecom EM Attribute List> ::== <RADIUS VSA for IPCablecom EM Attribute>... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 8 Security Requirements | Security for IPCablecom Multimedia interfaces utilizes security mechanisms defined in [16] as well as in [1]. Table 26 provides a summary of security mechanisms for each of the IPCablecom Multimedia interfaces. Table 26: Multimedia Security Interfaces Interface Description Security Mechanisms pkt-mm-1 CMTS - CM HMAC-ba... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 8.1 CMTS - CM QoS Interface (pkt-mm-1) | DOCSIS QoS messages are authenticated using an HMAC (Hash Message Authentication Code), which is a keyed cryptographic hash. Calculation of the HMAC attribute that must be included in DOCSIS QoS messages is specified in clause C.1 of [1]. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 8.2 Policy Server - CMTS COPS Interface (pkt-mm-2) | The Policy Server - CMTS COPS interface shall be secured using the IPsec ESP protocol, as specified in clause 7.2.1.3.2 of [16]. The key management requirements for this interface shall comply with clause 7.2.1.4.1 of [16]. For this interface, Policy Server shall comply with all the Gate Controller requirements listed ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 8.4 Policy Server - RKS Event Message Interface (pkt-mm-4) | The Policy Server - RKS Event Message interface shall be secured using the IPsec ESP protocol, as specified in clause 7.3.2 of [16]. The key management for this interface shall be identical to the one specified for a CMTS-RKS interface in clause 7.3.3.2 of [16]. IKE with pre-shared keys is required to implement, while ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 8.5 CMTS - RKS Event Message Interface (pkt-mm-5) | The CMTS - RKS Event Message interface shall be secured using the IPsec ESP protocol, as specified in clause 7.3.2 of [16]. The key management for this interface is specified in clause 7.3.3.2 of [16]. IKE with pre-shared keys is required to implement, while IKE with certificates and Kerberized IPsec are both optional ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9 Mapping a FlowSpec Traffic Profile to DOCSIS | A Traffic Profile defines the QoS attributes of the IP flow or the DOCSIS Service Flow to be used in performing authorization, reservation and commit operations. A Traffic Profile can be defined via one of the following methods: • FlowSpec • DOCSIS Service Class Name • DOCSIS Specific Parameterization • Upstream Drop T... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9.1 Mapping FlowSpecs to DOCSIS Scheduling Types | FlowSpecs support two types of services: Controlled Load and Guaranteed. Controlled Load services provide minimum bandwidth guarantees, but not latency/delay guarantees. Guaranteed services provide both bandwidth and latency/delay guarantees. Guaranteed service may be closely approximated through DOCSIS Real-Time Polli... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9.2 Mapping FlowSpecs to DOCSIS Traffic Parameters | The FlowSpec is made up of two parts, the TSpec and the RSpec. The TSpec describes the traffic for the flow, and the RSpec describes the desired service; note that for a controlled load service, the RSpec is not used. The RSpec parameters shall be specified for a guaranteed service. The CMTS shall ignore the RSpec para... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9.3 DOCSIS Upstream Parameters | For all of the upstream packet size calculations, the following formula must be used unless otherwise specified: The packet PDU shall be calculated from the first byte following the DOCSIS MAC HCS to the end of the CRC. This value includes the Ethernet header overhead of 18 bytes (6 bytes for source address, 6 bytes fo... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9.3.1 Unsolicited Grant Scheduling (UGS) | Unsolicited Grant Scheduling shall be used when the Service Number is 2 (Guaranteed), the Peak Rate, Bucket Rate, and the Reserved Rate are all equal, and Maximum Datagram Size is equal to Minimum Policed Unit. The DOCSIS upstream objects shall be set as stated below. All service flow quality of service TLV encodings t... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9.3.2 Real-Time Polling Scheduling | Real-Time Polling Scheduling shall be used when the Service Number is 2 (Guaranteed Service) and either the Peak Rate, Bucket Rate and Reserved Rate are not all equal (i.e. !(p==r==R)), or the Maximum Datagram Size is not equal to the Minimum Policed Unit. The DOCSIS upstream objects shall be set as stated below. All s... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9.3.3 Best Effort Scheduling | Best Effort Scheduling shall be used when the Service Number is 5 (Controlled-Load). The DOCSIS upstream objects shall be set as stated below. All service flow quality of service TLV encodings that are not defined here shall be given their default values as indicated by DOCSIS. The DOCSIS Traffic Priority shall be set ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9.3.4 Upstream Packet Classification Encodings | |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9.3.4.1 DOCSIS Upstream Packet Classification Requests | The DOCSIS upstream classification objects shall be set as stated below. All classification TLV encodings that are not defined here shall be given their default values as indicated by DOCSIS. The DOCSIS Classifier Identifier parameter shall be used. If the Extended Classifier is used, a CMTS may choose to use the Class... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9.4 DOCSIS Downstream Parameters | |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9.4.1 Downstream QoS Encodings for Guaranteed Service | The DOCSIS downstream service flow quality-of-service TLV encodings shall be set as stated below. All service flow quality of service TLV encodings that are not defined here shall be given their default values as indicated by DOCSIS. The downstream DOCSIS parameters are calculated using the DOCSIS MAC header from the b... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9.4.2 Downstream QoS Encodings for Controlled Load Service | The DOCSIS downstream service flow quality of service TLV encodings shall be set as stated below. All service flow quality of service TLV encodings that are not defined here shall be given their default values as indicated by DOCSIS. The downstream DOCSIS parameters are calculated using the DOCSIS MAC header from the b... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9.4.3 Downstream Packet Classification Encodings | |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 9.4.3.1 DOCSIS Downstream Packet Classification Requests | The DOCSIS downstream classification objects shall be set as stated below. All classification TLV encodings that are not defined here shall be given their default values as indicated by DOCSIS. The DOCSIS Classifier Identifier parameter shall be used. If the Extended Classifier is used, a CMTS may choose to use the Cla... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 10 Message Flows | This clause provides two interaction scenarios between the various network elements previously introduced in the present document. The first interaction outlines at a relatively high-level the basic message exchanges that take place within the IPCablecom Multimedia framework in order to authorize, reserve and commit ac... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 10.1 Basic Message Sequence | Policy Server 'm' Application Manager 'n' Application Manager Server 1 Application Manager Server 1 Application Manager 1 ... ... ... CMTS Policy Server 1 ... CM Client 1 8 2 7 6 3 5 4 Figure 8: Basic Message Sequence 1. Client issues a session setup request to the Application Manager via Application Layer signalling. ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 10.2 Detailed Message Sequence | Client CM CMTS PS RKS AM (1) Application Signaling (2) Gate-Set (3) Gate-Set (4) DSA-REQ (6a) DSA-ACK (5) DSA-RSP (6b) Gate-Set-Ack (6c) QoS_Reserve (6d) QoS_Commit (7a) QoS_Reserve Ack (7b) QoS_Commit Ack (7c) Gate-Set-Ack (7d) Policy_Request (8) Policy_Request_Ack (9) Application Signaling Session in Progress (10) Ap... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 1 Scope | The present document describes an XML schema for describing application constraints and resources to be used for deploying these applications on distributed and parallel infrastructures, like enterprise and scientific grids or job schedulers. The present document will help enterprises and laboratories to manage their I... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 102 827: "GRID; Grid Component Model (GCM); G... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] Proactive, INRIA. NOTE: Available at http://proa... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 3 Definitions | For the purposes of the present document, the terms and definitions given in TS 102 827 [1] and the following apply: component: abstraction of a software entity with a well-defined interface for both server and client parts component model: specification of how components are defined and interact together executable: a... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 4 Overall Structure of the GCM Application Description | |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 4.1 Principles | Like a deployment descriptor, an application descriptor is written in XML. Each element of the descriptor is defined as a single node, which can have attributes and child nodes. Also, see clause 6.1 of TS 102 827 [1]. |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 4.2 Overall XML structure | A deployment descriptor has the following structure: <environment> <descriptorVariable …/> <programVariable …/> <descriptorDefaultVariable …/> <programDefaultVariable …/> <includePropertyFile …> … </environment> <application> … </application> <resources> <nodeProvider> <file …/> … </nodeProvider> … </resources> The ele... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 4.2.1 Environment | The <environment> element can have the following children elements: • descriptorVariable: the value has to be set in the descriptor, and cannot be specified in the program; • descriptorDefaultVariable: a default value must be specified in the descriptor. The program has the ability to change the value at execution. If ... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 5 Application Specification | The <application> element is the core of the descriptor, as it describes the application which will be run on a GCM-described grid. It contains a single child which type determines the kind of application that will be launched on the grid. The types currently defined are: 1) Executable. 2) ProActive. ETSI ETSI TS 102 8... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 5.1 Executable | An executable defines an application which is actually a simple command to be run. It can have the following child elements: • nodeProvider (empty element with a single "refId" attribute): the id of a node provider (defined in the <resources> part). There can be any number of such element; • command (command): the comm... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 5.2 Extension of applicationNodeType (ProActive) | |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 5.2.1 Overall structure | The proactiveType is a more complex extension of applicationNodeType than executableType.It uses the technicalServices and virtualNode XML types as follows: <proactive> <technicalServices> </technicalServices> <virtualNode> <nodeProvider/> … </virtualNode> <virtualNode> … </virtualNode> … </proactive> The technicalServ... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 5.2.2 Definition of proactiveType | In addition to using standard GCM types, elements of type proactiveType can have the following children: • configuration: various configuration parameters. This element can have the following children: - bootClasspath (simple classpath): the boot classpath for the JVM; - java (path string): the path to the Java executa... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 5.2.3 Technical Services | A technical service is a non-functional requirement that may be dynamically fulfilled at runtime by adapting the configuration of selected resources. Such services are specified with a <technicalServices> element. This element holds a sequence of <class> children elements, which themselves hold a sequence of <property>... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 5.2.4 Data | The data tag allows describing the input and output data stores required by an application. Each data store has a unique identifier. The default input and output data stores are automatically tagged with the “default” identifier. Grid middleware are expected to provide an interface to upload and download data from the ... |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 6 Resource Specification | The <resources> element has no attributes and only contains a sequence of <nodeProvider> elements. There can be any number of such elements. Figure 6 ETSI ETSI TS 102 828 V2.1.1 (2010-03) 15 |
7158fdb2a686419dec98127cbffc1402 | 102 828 | 6.1 Node Provider | A <nodeProvider> can have the follow children: • file (file): this element can only have a single attribute ("path") which contains the path to the deployment descriptor file which the node provider uses. There can be any number of such elements. It can also have the following attribute: • id (id): a string identifying... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 1 Scope | The present document describes the specification for a high performance External Power Supply Unit for powering the Customer Premises Equipment to a maximum voltage rating of 12 V dc. The specifications define the input, output characteristics and performance requirements for a switching mode AC to DC CPS rated to a ma... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 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... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] Commission Regulation (EC) No 278/2009 of 6 April 2009 implementing Directive 2005/32/EC of the European Parliament and of the Council with regard to ecodesign requirements for no-load condition electric power consumption ... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 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 ES 202 874-1 (V1.1.1): "Access, Terminals, Transmission and Multiplexing (ATTM); External Common Power Supply for Customer Premises Network and A... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 3 Definitions and abbreviations | |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Customer Network (CN): in-house network composed by home gateway, end devices, network segments (physical wired or wireless connections between customer network elements), home network infrastructure devices such as network adapters (p... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABS Acrylonitrile Butadiene Styrene AC Alternating Current CE Commission Européenne CND Customer Network Device CNG Customer Network Gateway CPE Customer Premises Equipment CPN Customer Premises Network CPS Common Power Supply DC Direct Curren... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4 Electrical Specifications | |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.1 Input Requirements | The CPS shall be designed to meet the requirements and limits given in table 2. Table 2: Input voltage and frequency Normal Voltages (Vac) Voltage Variation Range (Vac) Normal Frequency (Hz) Frequency Variation Range (Hz) 100 to 240 90 to 264 50 to 60 47 to 63 The AC input current shall not exceed 1 A, when operated at... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.2 Output Requirement | |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.2.1 Output Voltage, Current And Ripple | Table 3: Output voltage, current and ripple Input normal voltage (Vac) Output Nominal Voltage (Vdc) Output Regulation Minimum Load (A) Maximum Load (A) Maximum ripple (mVp-p) Output power (W) 100 to 240 12 ±5 % 0 2,0 120 24 NOTE 1: Output voltages shall be measured at the output connector. NOTE 2: Measurements shall be... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.2.2 Short Circuit Protection And Over Current Protection | The CPS shall be protected from damage of a short circuit at the output or too high output current, irrespective of the duration of the existence of the fault and shall auto-recover when the fault is removed. The CPS shall not activate the over current protection at start up, while the output is connected to a 2 200 μF... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.2.3 Output Over Voltage Protection | When 12 V output voltage reaches its over- voltage protection trigger point the CPS shall be shutdown and output voltage shall not exceed 16 V Max. This includes Control Loop failure. ETSI ETSI TS 102 874-4 V1.2.1 (2012-03) 14 |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.2.4 Output Polarity | PIN # Output level 1 RTN (-) 2 +12 V Figure 1: Output polarity |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.3 Performance Requirement | |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.3.1 Efficiency | The power supply shall comply with the European Commission Regulation No 278/2009 [1]. That means: • No-load conditions shall not exceed 0,3 Watt. • The CPS shall provide an efficiency of at least 82,2 %, measured as the average of the efficiencies at 25 %, 50 %, 75 % and 100 % of the rated load. In addition, the CPS m... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.3.2 Turn On Delay Time | The CPS shall switch on in less than 2 s at maximum load and both 110 Vac/60 Hz and 220 Vac/50 Hz inputs. The measurement shall be made from the start of the input voltage, up to the moment the rated output voltage has been reached. |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.3.3 Hold-up Time | The hold-up time shall be a minimum of 10 ms at maximum load and both 110 Vac/60 Hz and 220 Vac/50 Hz. The measurement shall be made following AC voltage interrupt from the moment at which the input current ceases, to the moment the output voltage drops below the rated voltage minus 5 %. |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.3.4 Brown-out and recovery | Figure 2: Input voltage brown-out and recovery CPS must have clean ON/OFF and OFF/ON transition, maintaining the compliance to specification and without any permanent damage after the application of different voltages as described in figure 2. Input voltage will be reduced from 90 V to 0 Vac in 30 s, then immediately i... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.3.5 Dynamic Load | The CPS must be capable of a higher output current than the rated output current during a time interval as given below: • High Load: 250 %/30 ms of the rated load. • Low Load: 100 %/1 s of the rated load. • Slew Rate: 0,1 A/μs. |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.3.6 Max Open Circuit Voltage | When the circuit of over voltage protection is invalidated, the output voltage must be 16 V maximum. |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.3.7 Overshoot at turn on/Turn off | The overshoot at turn on and turn off shall not exceed 10 % of the nominal voltage value. |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.3.8 Output transient response/Transient load slew | With an input voltage, output load, ambient temperature and slew rate as given below, the undershoot or overshoot of output shall be not less than 5 % of the output voltage: • Input voltage: 90 V ~ 264 Vac/47 ~ 63Hz. • Output Load: 20 % to 80 %, 80 % to 20 %. • Ambient temperature: 25 ºC ± 3 ºC, Slew rate 1,0 A/μs, T1 ... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 4.3.9 Rise time | Rise time shall be less than 50 ms when measured from 10 % to 90 % of the output voltage at normal input voltage. 5 Operational, Storage and Transportation Requirements |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 5.1 Temperature and Humidity | The CPS shall be able to operate in the following environmental conditions: • Temperature: 5 °C to +40 °C. • Relative humidity: 5 % to 95 %. This corresponds to Class 3.1 "Temperature-controlled locations" of EN 300 019-1-3 [17]. The CPS shall be withstand the storage conditions defined in EN 300 019-1-1 [15].and relat... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 6 EMC, safety and Environmental requirements | |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 6.1 Product EMC | As this CPS is intended to be used for Information Technology Equipment (ITE), they should be tested with the associated telecommunication equipment according to the following EMC standards for ITEs: • CISPR 22, or EN 55022 [2], for the emission requirements. • CISPR 24 [26], or EN 55024 [23] for the immunity requireme... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 6.1.1 Electrostatic Discharge (ESD) | The CPS shall meet EN 61000-4-2 [5]: ±15 kV Air Discharge, ±8 kV contact discharge. |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 6.1.2 Harmonic Current | The CPS shall meet the requirements of EN 61000-3-2 [4]. |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 6.1.3 Voltage fluctuations and flicker | The CPS shall meet the requirements of EN 61000-3-3 [24]. |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 6.2 Product Safety | The power supply must meet the requirements of IEC 60950-1 [25] or EN 60950-1 [10]. |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 6.3 Environmental and Eco-Design Requirements | The following Ecodesign rules must be applied when manufacturing the CPS: • The external case of the CPS shall be manufactured using recyclable plastic. • The external case of the CPS should be manufactured using at least 50 % recycled plastic (preferred choice: ABS). The cables of the CPS should be manufactured using ... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 7 Reliability | |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 7.1 Burn-in | All power supplies shall be burned-in for 2 hours under nominal input and 70 % ~ 80 % load at an ambient temperature of 40 ºC. |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 7.2 MTBF Calculation | The MTBF, Mean-Time-Between-Failures, shall be calculated and reported for each quality class offered. The provisional model adopted is referring to the "bathtub curve" defining the behaviour of the failure rate as function of the time. While in the first part of the useful life the failure rate is higher, then it decr... |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 8 Mechanical Specification | |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 8.1 AC plug | The 230 VAC plug must form part of the main housing of the CPS or be part of a fixed cord of the main housing of the CPS. The AC plug of the CPS shall comply with EN 50075 [11], but without the cord. |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 8.2 DC cord | The DC cord must comply with the data below with typical cord length of 2 m. NOTE 1: Cable: UL 2468 style: 80 ºC, 300 V, 2 conductors. NOTE 2: Plug: Ø 4,95 x 1,95 x 9,5 mm (tuning fork annexure entire insulation) black. Figure 3: DC cord ETSI ETSI TS 102 874-4 V1.2.1 (2012-03) 18 |
abe6f837ab784403f6055fbeaad40b4a | 102 874-4 | 8.3 Label specification | The CPS shall be affixed with a label, with appropriate wording in the language specific for the intended country for deployment, stating the CPS compliance with the appropriate European regulations. ETSI ETSI TS 102 874-4 V1.2.1 (2012-03) 19 Annex A (informative): Details on Tests Procedures This annex is containing n... |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 1 Scope | The present document contains the Profile Test Specification (PTS) and the Test Case Library (TCL) for "New Generation DECT; Part 5: Additional feature set nr. 1 for extended wideband speech" (ETSI TS 102 527-5 [15]). The present document covers both the Portable (PT) and the Fixed (FT) Radio terminations. The present ... |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 2 References | |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 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... |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 101 178: "Digital Enhanced Cordless Telecommunications (DECT); A high Level Guide to the DECT Standardization". [i.2] ETSI TBR 006: "Digital E... |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 3 Definition of terms, symbols and abbreviations | |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 527-5 [15], ETSI TS 102 527-3 [14], ETSI TS 102 527-1 [13], ETSI EN 300 444 [12] and the following apply: GAP (PP, FP, device or equipment): PP, FP or any of them compliant with ETSI EN 300 444 [12] Golden device: ideal example of a device used as... |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: M mandatory to support (provision mandatory, process mandatory) O optional to support (provision optional, process mandatory) I out-of-scope (provision optional, process optional) not subject for testing C conditional to support (process mandatory) ... |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: BCD Binary Code Decimal BTPC Base manual Transmit Power Control CC Call Control CFB Call Forwarding on Busy subscriber CFNA Call Forwarding on No Answer CFU Call Forwarding Unconditional CI Common Interface CLIP Calling Line Identification Pre... |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 4 Test method | |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 4.0 General | The test method used to test the NG DECT Part 5 devices is the same as for NG DECT Part 3 devices (see ETSI TS 102 841 [16], clause 4). ETSI ETSI TS 102 843 V1.2.1 (2022-08) 14 |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 4.1 Test platform | |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 4.1.1 PP test platform | |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 4.1.1.0 General | The PP test platform outlined in clause 4.1.1 of ETSI TS 102 841 [16] applies to NG DECT Part 5 devices with the modifications given in the following clauses. |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 4.1.1.1 List content for tests | |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 4.1.1.1.1 List of Supported Lists | The List of Supported Lists outlined in clause 4.1.1.1.1 of ETSI TS 102 841 [16] also applies. |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 4.1.1.1.2 Missed Calls List | The Missed Calls List outlined in clause 4.1.1.1.2 of ETSI TS 102 841 [16] also applies to NG DECT Part 5 devices. |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 4.1.1.1.3 Outgoing Calls List | The Outgoing Calls List outlined in clause 4.1.1.1.3 of ETSI TS 102 841 [16] also applies to NG DECT Part 5 devices. |
fccfa8ede439ac2e73e6c14faea50b63 | 102 843 | 4.1.1.1.4 Incoming Accepted Calls List | The Incoming Accepted Calls List outlined in clause 4.1.1.1.4 of ETSI TS 102 841 [16] also applies to NG DECT Part 5 devices. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.