hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.2.1.1 Message Flow Diagrams | The message flow diagrams for the IMS Service Access are show below. These highlight the interactions between NGN and core IMS elements for UE attachment and individual sessions. It is assumed that those sessions require dynamic per-session resource allocations. For permanent or semi-permanent sessions resource allocat... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.2.2 IMS Service Access - Mesh network based (2) | As a further enhancement of scenario 1, dynamic QoS packet classification can be introduced in both satellite link directions by modification of STs with RCEFs. This would be particularly applicable to mesh satellite networks. This architecture is particularly appropriate for both the emergency services and smart grid ... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.2.2.1 Message Flow Diagrams | The message flow diagram for this scenario is similar to the previous one except that now at session establishment the RACS communicated with the local ST RCEF hence results in more BSM network signalling. ETSI ETSI TS 102 855 V1.1.1 (2011-03) 22 Figure 5.5: IMS Service Access with ST-based RCEF ETSI ETSI TS 102 855 V1... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.2.3 Efficient IMS Peering (3) | Here the BSM network is used as a backbone for interconnecting isolated ISP/MSP (Mobility Service Providers) supporting IMS for backhauling. A BSM mesh network would suit this configuration, avoiding double hop delay. The satellite network operator does not need to be an IMS operator, but should provide functions to ma... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.3 Detailed Functional Architecture | This clause provides a short description of those elements of the BSM architecture that will require some adaptation to comply with the NGN/IMS architecture. Since the goal of such integration is to move user and session management functions towards standardised NGN functions and integrate resource management into the ... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.3.1 BSM RACS | The functional architecture of the Resource Admission Control Function (RACS) in the BSM network is shown in figure 5.7. The BSM Star network architecture case is shown (see clause 5.2.1). ETSI ETSI TS 102 855 V1.1.1 (2011-03) 24 Rq SPDF A-RACF RACS RCEF BGF NASS AF BSM Network Hub/ST Ia Re ST e4 Gq’ NGN Service Layer ... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.3.1.1 SPDF | The Service-based Policy Decision Function (SPDF) provides the Application Function (AF) with a single point of contact. The Service Policy Decision Function (SPDF) acts as a final Policy Decision Point for Service-Based Policy control (SBP) for each administrative domain (e.g. BSM network) it resides in. It may also c... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.3.1.2 A-RACF | The Access-Resource Admission Control Function (A-RACF) is the version of the RACF is appropriate when the BSM network is employed as an access network. The A-RACF acts as a Policy Decision Point (PDP) in terms of subscriber access admission control, as well as in terms of resource handling control. ETSI ETSI TS 102 85... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.3.2 BSM NASS | The functional architecture of the Network Attachment Subsystem (NASS) in the BSM network is shown in figure 5.8. The NASS comprises the following functional entities: • Network Access Configuration Function (NACF). • Connectivity session Location and repository Function (CLF). • User Authentication and Authorization F... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.3.2.1 Network Access Configuration Function (NACF) | The Network Access Configuration Function (NACF) is responsible for the IP address allocation to the UE. It may also distribute other network configuration parameters such as address of DNS server(s), address of signalling proxies for specific protocols (e.g. address of the P-CSCF when accessing to the IMS). The NACF s... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.3.2.2 Connectivity session Location and repository Function (CLF) | The Connectivity session Location and repository Function (CLF) registers the association between the IP address allocated to the UE and related network location information provided by the NACF, i.e.: access transport equipment characteristics, line identifier (Logical Access ID), IP Edge identity, etc. The CLF regist... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.3.2.3 User Authentication and Authorization Function (UAAF) | The User Authentication and Authorization Function (UAAF) performs NASS User authentication, as well as authorization checking, based on NASS User profiles, for network access. For each NASS User, the UAAF retrieves authentication data and access authorization information from the NASS User network profile information ... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.3.2.4 Profile Data Base Function (PDBF) | The Profile Data Base Function (PDBF) is the functional entity that contains NASS User authentication data (NASS User identity, list of supported authentication methods, key materials etc.) and information related to the required network access configuration: This data is called "NASS User network profile". The NASS Us... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.3.2.5 CNG Configuration Function (CNGCF) | The CNGCF is used during initialization and update of the CNG. The CNGCF provides to the CNG additional configuration information (e.g. configuration of a firewall internally in the CNG, QoS marking of IP packets, etc.), with respect to the configuration information provided by the NACF. This data differs from the netw... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 5.4 Interfaces and Reference Points | The Reference Points below (which have the properties of interfaces) are those between BSM network entities and NGN entities within a BSM System and assume that certain entities are integrated into BSM entities (e.g. the RCEF) as indicated in figures 5.1, 5.2, 5.4 and 5.6. They are all based on the TISPAN definitions f... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 6 BSM Adaptation Functions for NGN | In this clause the specific elements necessary to provide NGN interoperability in BSM networks and systems are defined. The goal of the clause is not to go into design details of these elements but to provide descriptions of some essential functional elements beyond what the previous clause defined for the management o... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 6.1 Signalling Application Server | The Signalling Application Server is needed to adapt the SIP signalling for transmission over the BSM network and to account for added delay, losses and bottleneck resources. The SIP message contains the end point addresses as well as the addresses of the different proxies that will handle the session and of the regist... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 6.2 BSM IWF | We assume that the existing BSM protocols are the basis from which the NGN functionality will be implemented. The primary IWF development effort will be to interface existing resource management functionality to the NGN access elements. The BSM architecture already gives the ability to use IP protocols hence there is n... |
42c5055335a9667cbcb1b0a21452da6f | 102 855 | 6.3 Mobile/Fixed Satellite System Convergence | Satellite mobile/fixed convergence, in particular service and device mobility, should be enabled by the NGN/IMS architecture and the IMS core elements. This topic is intended for further study. ETSI ETSI TS 102 855 V1.1.1 (2011-03) 30 Annex A (informative): The IP Multimedia Subsystem (IMS) This annex provides a short ... |
a4d9c784395ee860b833c6896d611966 | 102 870-1 | 1 Scope | The present document provides the Protocol Implementation Conformance Statement (PICS) pro forma for Conformance test specifications for Geonetworking Basic Transport Protocol as defined in ETSI EN 302 636-5-1 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC... |
a4d9c784395ee860b833c6896d611966 | 102 870-1 | 2 References | |
a4d9c784395ee860b833c6896d611966 | 102 870-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... |
a4d9c784395ee860b833c6896d611966 | 102 870-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... |
a4d9c784395ee860b833c6896d611966 | 102 870-1 | 3 Definition of terms, symbols and abbreviations | |
a4d9c784395ee860b833c6896d611966 | 102 870-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 302 636-5-1 [1], ISO/IEC 9646-1 [i.1] and ISO/IEC 9646-7 [i.2] apply. ETSI ETSI TS 102 870-1 V1.2.1 (2022-03) 6 |
a4d9c784395ee860b833c6896d611966 | 102 870-1 | 3.2 Symbols | Void. |
a4d9c784395ee860b833c6896d611966 | 102 870-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ICS Implementation Conformance Statement ITS Intelligent Transportation Systems IUT Implementation Under Test PICS Protocol Implementation Conformance Statement SUT System Under Test |
a4d9c784395ee860b833c6896d611966 | 102 870-1 | 4 Conformance requirement concerning PICS | If it claims to conform to the present document, the actual PICS pro forma to be filled in by a supplier shall be technically equivalent to the text of the PICS pro forma given in annex A, and shall preserve the numbering/naming and ordering of the pro forma items. An ICS which conforms to the present document shall be... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 1 Scope | The present document contains the Abstract Test Suite (ATS) for Decentralized Environmental Notification Basic Service (DEN) as defined in ETSI EN 302 637-3 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.7]. The objective of the present document ... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 2 References | |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 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... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 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... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 3 Definition of terms, symbols and abbreviations | |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 302 637-3 [1], ISO/IEC 9646-1 [i.4] and ISO/IEC 9646-7 [i.7] apply. |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 3.2 Symbols | Void. |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation One ATM Abstract Test Method ATS Abstract Test Suite BO Exceptional or abnormal behaviour BV Valid test events for Behaviour tests CAN Controller Area Network DEN Decentralized Environmental Notification Basic Se... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 4 Abstract Test Method (ATM) | |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 4.1 Abstract protocol tester | The abstract protocol tester used by this test suite is described in figure 1. The test system simulates valid and invalid protocol behaviour, and analyses the reaction of the IUT. Figure 1: Abstract protocol tester - DEN Test System SUT ITS-G5/ LTE V2X IUT DENM ITS-G5/ LTE V2X Lower tester PDUs Upper Tester GeoN GeoN ... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 4.2 Test Configuration | This test suite uses a unique test configuration in order to cover the different test scenarios. In this configuration, the tester simulates one ITS station implementing the DEN protocol. |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 4.3 Test architecture | The present document implements the general TTCN-3 test architecture described in ETSI EG 202 798 [i.1], clauses 6.3.2 and 8.3.1. Figure 2 shows the test architecture used in for the DEN ATS. The DEN test component requires using only the Main Test Component (MTC). The MTC communicates with the DEN SUT over the denmPor... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 4.4 Ports and ASPs (Abstract Services Primitives) | |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 4.4.1 Introduction | Two ports are used by the DEN ATS: • The denmPort, of type DenmPort. • The utPort of type UpperTesterPort. |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 4.4.2 Primitives of the denmPort | Two types of primitives are used in the denmPort: • The DenmInd primitive, containing the received messages of type DenmPdu, and a timestamp corresponding to the receipt time. • The DenmReq primitive containing the sent messages of type DenmPdu. The DenmPdu type is declared in the DENM.asn ASN.1 module, following the A... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 4.4.3 Primitives of the utPort | This port uses two types of primitives: • The UtInitialize primitive used to initialize IUT. • The UtTrigger primitive used trigger upper layer events in IUT. |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 4.5 Executing DEN tests in secured mode | All the DEN tests, with the exception of the SSP tests, can be executed with security enabled or with security disabled. The choice of running the DEN tests in secured or non-secured mode has no impact on the result of the DEN tests because the test verdicts assess DEN protocol behaviour only. The SSP tests can only be... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 4.6 ETSI test adapter | All information of the ETSI test adapter is described in ETSI TR 103 099 [i.3]. |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 5 Untestable Test Purposes | Table 1 gives a list of TPs, which are not implemented in the ATS due to the chosen ATM or other restrictions. Table 1: Untestable TP Test purpose Reason TP/DEN/EVGN/BV-08 In order to achieve the situation of sequenceNumber wrap-around, 65 535 DENMs would need to be generated. With 10 DENMs sent per second, the test wo... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 6 ATS conventions | |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 6.1 Introduction | The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS. The ATS conventions contain two clauses, the testing conventions an... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 6.2 Testing conventions | |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 6.2.1 Testing states | |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 6.2.1.1 Initial state | All test cases start with the function f_prInitialState. This function brings the IUT in an "initialized" state by invoking the upper tester primitive UtInitialize. |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 6.2.1.2 Final state | All test cases end with the function f_poDefault. This function brings the IUT back in an "idle" state. As no specific actions are required for the idle state in ETSI EN 302 637-3 [1], the function f_ poDefault does not invoke any action. As necessary, further actions may be included in the f_poDefault function. |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 6.2.2 Message types - ASN.1 definitions | ASN.1 definitions from ETSI EN 302 637-3 [1] are directly imported in TTCN-3 using the ASN.1 import method specified in ETSI ES 201 873-7 [i.10]. The following example shows the TTCN-3 import statement used to import ASN.1 definitions in the TTCN-3 modules: import from DENM_PDU_Descriptions language "ASN.1:1997" all; E... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 6.3 Naming conventions | |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 6.3.1 General guidelines | The naming convention is based on the following underlying principles: • in most cases, identifiers should be prefixed with a short alphabetic string (specified in table 2) indicating the type of TTCN-3 element it represents; • suffixes should not be used except in those specific cases identified in table 2; • prefixes... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 6.3.2 ITS specific TTCN-3 naming conventions | Next to such general naming conventions, table 3 shows specific naming conventions that apply to the ITS TTCN-3 test suite. Table 3: ITS specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier ITS Module Use upper-case initial letter Its"IUTname"_ ItsDenm_ Module containing types... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 6.3.3 Usage of Log statements | All TTCN-3 log statements use the following format using the same order: • Three asterisks. • The TTCN-3 test case or function identifier in which the log statement is defined. • One of the categories of log: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT. • Free text. • Three asterisks. EXAMPLE 1: log("*** f_awaitD... |
b439e048cd151e4a338ab9118ea4996e | 102 869-3 | 6.3.4 Test Case (TC) identifier | Table 4 shows the test case naming convention, which follows the same naming convention as the test purposes. Table 4: TC naming convention Identifier: TC_<root>_<gr>_<x>_<nn> <root> = root DEN <gr> = group MSGF Message Format EVGN Event Generation SSCI Specific Situation Container Information SLCI Specific Location Co... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 1 Scope | The present document describes an XML based Architecture Description Language (ADL), used to define the composition of software components in distributed and parallel infrastructures. The standard will help enterprises and laboratories to manage large-scale computer and telecom infrastructures with the necessary virtua... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 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... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 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 828: "GRID; Grid Component Model (GCM); G... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 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] "The Fractal Component Model". NOTE: Available a... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 3 Definitions and abbreviations | |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: client interface: component interface that emits operation invocations component: abstraction of a software entity with a well-defined interface for both server and client parts component content: is (recursively) made of subcomponents... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADL Architecture Description Language API Application Programming Interface FC2 Format Commun (Version 2) FIACRE Intermediate Format for the Architectures of Embedded Distributed Components GCM Grid Component Model VCE Vercors Component Editor... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4 Overall Structure of the ADL | |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.1 Principles | The GCM ADL is an extensible language to define component architectures for the GCM component model ([i.2],[i.3]). It is an extension of the Fractal component model [i.1]. Consequently, the present document can also be considered as a definition of Fractal's ADL. Elements specific to GCM are the export and composition ... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.1.1 Component Structure | The main element of the ADL is the Component. The most basic component is a primitive component that is a component entirely implemented in a programming language (typically Java). Primitive components can be combined into composite components. More generally, a composite component is a component built by aggregating s... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.1.2 Interfaces | A component's relationship to the "external world" is defined by its interfaces. There are two kinds of interfaces, the ones the component provides ("server" role), and the ones it requires ("client" role). For instance a "calculator" component may provide an interface consisting of "add", "subtract", multiply", and "d... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.1.3 Deployment | To enable the deployment of components on a grid environment, it is possible to specify the Virtual Node on which the component will be deployed. Additionally, the ADL can rename and compose virtual nodes of sub-components of a composite in order to expose different assemblies, and names of virtual nodes at a higher le... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.1.4 Behaviour | The behaviour element allows specification of the behaviour of a component. This allows using different semantic formalisms and underlying models to reach similar goals, i.e. to guarantee that components in a composite system behave smoothly together and respect some user requirements. The <behaviour> element has two f... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.1.5 Relationship with the Management API | A GCM ADL definition provides a static description of a component architecture. The instantiation into an actual set of running components is done through the GCM API, by a Factory object: the factory typically receives an ADL from which it is able to instantiate a component system; the system is created by invoking me... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.2 component and definition | The root element of the GCM ADL is the definition. A definition describes a single component structure. Within it you can find (among other things) declarations of (sub) components, interfaces, bindings, and virtual nodes. There can be several components declared in a definition, since a component may be an aggregate o... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.3 interface | Interfaces are the outlets which the components can be bound with. Components interfaces are of two kind: 'server', for interfaces which are offered by the component, and 'client', for interfaces which the component requires. An interface element has the following attributes: • name: (string) the name of the interface ... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.4 virtualNode | It is possible to specify among virtual nodes of a GCM deployment specification file, which of them should be used for the deployment of the component. This is done through a list of virtualNode elements. A virtualNode element has no child element, and the following attributes: • name: (string) the name of the virtual ... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.5 exportedVirtualNode | Virtual nodes can be exported and composed. Export and compose allow respectively to rename and merge virtual nodes. This extends reusability of existing components. When exported, a virtual node can take part in the composition of other exported virtual nodes. An exportedVirtualNode element has the following attribute... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.6 composingVirtualNode | A composingVirtualNode element has the following attributes: • component: (string) the component which defines the composing virtual node (required); • name: (string) the name of the composing virtual node (required). Figure 6 |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.7 binding | Bindings define links between the client interface of a component to the server interface of another component. A binding element may contain a sequence of elements of type comment. It also has the following attributes: • client: (string) the name of the client interface from which the binding is made (required); • ser... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.8 content | A content element may contain a sequence of elements of type comment. It also has the following attributes: • class: (string) the class implementing the component (required). Figure 8 ETSI ETSI TS 102 829 V1.1.1 (2009-03) 14 |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.9 attributes | The attributes element has the following child elements: • comment: (comment type) a comment (0-unlimited); • attribute: (attribute type) an attribute (0-unlimited). An attribute element may also contain a sequence of comments. It also has the following attributes: • name: (string) the name of the attribute (required);... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.10 controller | A controller element may contain a sequence of comments. It also has the following attributes: • desc: (string) the name of the component's controller (required). Figure 11 ETSI ETSI TS 102 829 V1.1.1 (2009-03) 15 |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.11 behaviour | The <behaviour> element cannot have any children. It can have the following attributes: • language: (string): the specification language used by the behaviour file or value (required); • file: (string) the path to the behaviour specification file; • value: (string) the behaviour specification, specified inline. File an... |
77739b856770d6d5bb956d5bcd81fbe4 | 102 829 | 4.12 comment | A comment element has the following attributes: • language: (string) the language of the comment's text (required) • text: (string) the comment itself (required) Figure 13 ETSI ETSI TS 102 829 V1.1.1 (2009-03) 16 Annex A (normative): GCM ADL Schema <?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:xsd="http://ww... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 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... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 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... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 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 ... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 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... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 3 Definitions and abbreviations | |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 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... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 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 CN Customer Network CND Customer Network Device CNG Customer Network Gateway CPE Customer Premises Equipment CPN Customer Premises Network CPS Common Power Sup... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 4 Electrical Specifications | |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 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,6 A, when operated ... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 4.2 Output Requirement | |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 4.2.1 Output Voltage, Current And Ripple | Table 3: Output voltage, current and ripple Input normal voltage (Vac) Output Nominal Voltage (V dc) Output Regulation Minimum Load (A) Maximum Load (A) Maximum ripple (mVp-p) Output power (W) 100 to 240 12 ±5 % 0,0 3,2 120 38,4 NOTE 1: Output voltages shall be measured at the output connector. NOTE 2: Measurements sha... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 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... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 4.2.3 Output Over Voltage Protection | When 12 V output voltage reaches to 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. Output Polarity PIN# Output Level 1 RTN(－) 2 +12 V Figure 1: Output polarity ETSI ETSI TS 102 874-6 V1.1.1 (2012-02) 14 |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 4.3 Performance Requirement | |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 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 W. • The CPS shall provide an efficiency of at least 85,2 %, measured as the average of the efficiencies at 25 %, 50 %, 75 % and 100 % of the rated load. In addition, the CPS must... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.