hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 5.2.2 Technical details | CSA3, as specified for common DVB applications has been designed to minimise the likelihood of piracy attack over a long period of time and thus contains highly security sensitive information. The technical details of the scrambling algorithm can only be made available to bona-fide users upon signature of a Non-Disclos... |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 5.2.3 Licensing | The CSA3 Descrambling System is licensed to manufacturers of decoders and their components, and to providers, designers and other entities engaged in conditional access. The CSA3 Scrambling Technology is licensed to manufacturers of scramblers, who in turn sublicense to the purchasers of scramblers. CSA3 is made availa... |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 5.2.4 CSA-3 for DVB IPTV Scrambling | For the purpose of DVB IPTV scrambling, CSA3 shall only be used in standard mode as specified in TS 100 289 [3]. |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 5.3 DVB Common Scrambling Algorithm version 1 | |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 5.3.1 Introduction | CSA Version 1 (CSA1) is a device, apparatus or mechanism (whether implemented as hardware or software) designed or specifically adapted, totally or partially, to render unintelligible a service compatible with Standards by the use of CSA1 Scrambling Technology and any modifications and improvements thereof and which ca... |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 5.3.2 Technical details | The CSA1 Scrambling Algorithm has been designed to minimise the likelihood of piracy attack over a long period of time (at least 10 years from inception) and thus contains highly security sensitive information. The technical details of the scrambling algorithm can only be made available to bona-fide users upon signatur... |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 5.3.3 Licensing | CSA1 is licensed to manufacturers of decoders and their components, and to providers, designers and other entities engaged in conditional access. The Scrambling Technology is licensed to manufacturers of scramblers, who in turn sublicense to the purchasers of scramblers. CSA1 is made available by the custodian upon sig... |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 5.3.4 CSA for IPTV scrambling | CSA-1 was designed in 1994 to provide adequate security for a period of at least ten years. In 2007, DVB adopted CSA-3 in order to continue providing an adequate level of security taking into account advances in technology. CSA-1 is not expected to provide adequate security for another ten years and is not recommended ... |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 6.1 Introduction | This clause describes the Common IPTV Software-oriented Scrambling Algorithm (CISSA) version 1, which is the software-friendly scrambling algorithm which shall be used for MPEG2-TS IPTV services. CISSA is an algorithm for which the descrambling method is software-friendly. In other words, it is suitable for efficient e... |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 6.2 General Description (informative) | The Common IPTV Software-oriented Scrambling Algorithm (CISSA) uses the AES cipher described in [1] as its basic building block, with 128-bit (16 bytes) keys, called Control Words (CWs). ETSI ETSI TS 103 127 V1.1.1 (2013-05) 10 |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 6.2.1 TS level scrambling | The basic unit of scrambling (or descrambling) is an MPEG-2 transport stream packet (TS). Each packet is scrambled independently from all others, allowing random access. A packet consists of a header and optional adaptation field that are left in the clear followed by a payload that is processed as described below. AES... |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 6.2.2 PES level scrambling | The PES level scrambling method requires that the PES packet header is not scrambled (as required in ISO/IEC 13818-1 [i.1]) and TS packets containing parts of a scrambled PES packet do not contain an Adaptation Field (with the exception of the TS packet containing the end of the PES packet). The header of a scrambled P... |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 6.3 Normative Elements | This clause provides the normative description of CISSA version 1. Notations are as defined in clause 3.2. |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 6.3.1 Encryption Elements | |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 6.3.1.1 Block Cipher | AES-128, as defined in NIST FIPS 197 [1], shall be used as underlying block cipher for CISSA. |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 6.3.1.2 Initialization Vector | The Initialization Vector shall have the following value: • IV=0x445642544d4350544145534349535341 |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 6.3.1.3 Chaining Mode | CBC, as defined in NIST SP800-38A [2], shall be used as chaining mode. |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 6.3.2 TS packet Scrambling and Descrambling | Each TS packet shall be processed separately. The TS packet header and adaptation field, if present, shall be left in the clear. The payload size (payload_size) and the encrypted payload size (encrypted_payload_size) shall be computed as follows: • payload_size = 188 - (header_size + adaptation_field_size) • encrypted_... |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 6.3.3 PES level Scrambling and Descrambling | In order to apply PES level scrambling or descrambling, the following conditions shall be verified: • Scrambling shall only occur at one level (TS or PES) and is not allowed to occur at both levels simultaneously. • The header of a scrambled PES packet shall not exceed 184 bytes. • The TS packets carrying parts of a sc... |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 7 Signalling | |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 7.1 Scrambling descriptor (informative) | This clause explains the selection mechanism as defined in EN 300 468 [4] for the transport of signalling information to indicate which DVB IPTV scrambling algorithm is used. The scrambling descriptor indicates the selected mode of operation for the scrambling system. As defined in EN 300 468 [4], it is located in the ... |
e6d068f8d8bb4202c69c3f8e03f1e904 | 103 127 | 7.2 Use of the scrambling descriptor | For the purposes of the present document, only values 0x02, 0x03, and any value from the range for DVB-CISSA (0x10 to 0x1F) shall be used. NOTE: As specified in EN 300 468 [4], other scramblers that are not listed in table 2 can be used and signalled by user defined scrambler descriptors (in the range 0x80 - 0xFE). ETS... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 1 Scope | The present document contains the Test Framework and the Profile Test Specification (PTS) for "DECT Ultra Low Energy (ULE); Machine to Machine Communications; Part 1: Home Automation Network (phase 1) (TS 102 939-1 [10])". The present document covers both the Portable (PT) and the Fixed (FT) Radio terminations. The obj... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 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 referenced document (including any amendments) applies. Referenced documents which a... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI EN 300 175-1: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 1: Overview". [2] ETSI EN 300 175-2: "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 2:... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 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 EN 300 176-1: "Digital Enhanced Cordless Telecommunications (DECT); Test specification; Part 1: Radio". [i.2] ETSI EN 301 406: "Digital Enhanced ... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 3 Definitions and abbreviations | |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 102 939-1 [10], EN 300 175-1 [1], ISO/IEC 9646-7 [i.7] and the following apply: block of data: number of octets intended for transmission without interruptions in one or several bursts NOTE: It may contain one or several SDUs. certification... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 3.2 Symbols and abbreviations | For the purposes of the present document, the symbols and abbreviations defined in TS 102 939-1 [10], EN 300 175-1 [1], ISO/IEC 9646-1 [i.4], ISO/IEC 9646-6 [i.6], ISO/IEC 9646-7 [i.7] and the following apply: API Application Programming Interface ICS Implementation Conformance Statement IUT Implementation Under Test P... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 4 Overview and structure | |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 4.1 Structure of the present document | The present document contains the following elements of the conformance test specifications of DECT Ultra Low Energy (ULE); Part 1: Home Automation Network (phase 1) (TS 102 939-1 [10]): • Test framework and test architecture • Test interface specification • Test Specification conventions • Profile Test Specification, ... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 4.2 Overview of the different sections | |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 4.2.1 Overview and Structure | "Overview and Structure" is the present clause of the present document. It explains the structure and content of the different parts of the present document and other parts of this multi-part deliverable. |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 4.2.2 Test framework and test architecture | Test architecture and Test method used to test the protocol conformance of DECT ULE equipment are described in clause 5. Clause 5 starts with an overview on the global ULE protocol architecture and the foreseen DECT ULE standards ecosystem. Then, the specific test configurations for PT and FT conformance testing are in... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 4.2.3 Test interface specification | Clause 6 defines the test interfaces TF1 and TP1 created by the test architecture and used in the rest of the present document. In order to make possible some flexibility in the initial implementation of the interface, only a top level definition, named "functional definition" is provided. This allows flexibility for m... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 4.2.4 Profile Test Specification, Introduction and conventions | Clause 7.1 is an introductory section to the Profile Test Specification (PTS). It provides an overview and defines the conventions that will be used in the rest of the clause. 4.2.5 Profile Test Specification, Test Cases and Test Purposes (definition view) The "Profile Test Specification, Test Cases and Test Purposes (... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 4.2.7 Description format of U-plane test vectors | The description format of the U-plane vectors is described in annex A. The bit content of the vectors themselves will be given in the Test Case Library. The annex may be seen as an extension of clause 6 defining the interfaces TP1 and TF1. |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 4.2.8 Parameters for static and negotiated capabilities | Annex B introduces the list of parameters describing capabilities that are either inherent of the IUT or that are negotiated using an application protocol and that need to be exchanged through the interfaces TP1 or TF1 during the test preparation process. The test commands "Retrieve Static capabilities" and "Store Nego... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 4.2.9 PT and FT Test Case Library | The Test Case Library defines the detailed content of the Test Cases, including sequence diagrams, states, stimulus and pass criteria. The Test Cases and Test Purpose are defined in clause 7.2 of the present document. The Test Case Library will be implemented as a separate part (part 2) of this multi-part deliverable. |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 4.2.10 Run time view of the Test Specification | The Run time view of the Test Specification defines the execution view of the test certification program. In order to do that, the Test Cases are grouped in execution sequences that will be a functional execution unit in the test systems. Sequences are chosen according to technical convenience for the design and implem... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 4.2.11 Protocol Implementation Conformance Statement (PICS) | The Protocol Implementation Conformance Statement (PICS) proforma is the document that shall be filled by the supplier of any implementation subject to test under the scope of the present document stating which capabilities have been implemented. |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 5 Test Framework and test architecture | This clause describes the Test architecture and Test method used to test the protocol conformance of DECT ULE equipment. The device under test can be either a FT part or a PT part depending on the test and on what feature is tested. ETSI ETSI TS 103 159-1 V1.1.1 (2014-04) 11 |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 5.1 Overall ULE protocol architecture | The general ULE phase 1 architecture is depicted in figure 1. Figure 1: General ULE phase 1 architecture showing interfaces to application layers The part of the overall architecture that is described by TS 102 939-1 [10] comprises the complete DECT stack from physical (PHY) to the Network (NWK) layer at C-plane and to... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 5.2 ULE standards ecosystem | The foreseen standards ecosystem for the whole ULE technology is depicted in figure 2. The different parts of the diagram are described below. Figure 2: DECT ULE standards ecosystem. |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 5.2.1 ULE DECT subsystem | The ULE DECT sub-system for both parts is defined in a TS 102 939-1 [10] and further parts of the same multi-part deliverable which are application profiles based on the DECT Common Interface (DECT CI) EN 300 175 parts 1 to 8 [1] to [8]. At the time of writing the present document, only TS 102 939-1 [10] (DECT Ultra Lo... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 5.2.2 Interfaces (Service Access Points) of the DECT subsystem | According to DECT standardization methodology, a series of primitives (see EN 300 175 parts 1 to 8, [1] to [8]) are used for accessing the different DECT layers. However, this primitive model is not considered suitable for practical implementation and has not been standardized beyond what is defined in EN 300 175 speci... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 5.2.3 Routing and addressing sub-system | The "Routing and addressing" sub-system is located at the FP side and is in charge of resolving addressing and providing internal and external routing based on such addressing. The "Routing and addressing" sub-system is not defined at the time of writing the present document. It is identified as a potential element for... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 5.2.4 Application logic | On top of the "routing and addressing" sub-system (FP) and on top of the interface SP1 (PP), there is the true application logic (layer 7). The application logic may be standardized or proprietary. NOTE: In the case of standardized application logic functionality, dedicated specific application standards will be develo... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 5.3 Problem and solution to the testing of ULE phase 1 | With the current state of standardization the main problem for conformance testing is the lack of clearly defined interfaces SF1 and SP1. The radio air interface is not an issue since it is clearly defined by TS 102 939-1 [10] up to NWK and IWU layers. Application protocol is, however, not standardized, but it can be r... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 5.4 Test configurations: general approach | The present clause presents the general test configurations for testing PT and FT. This general approach is applicable to all Test scenarios and allows both fully automated and manual test configurations. |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 5.4.1 Test configuration for PT conformance testing | The test configuration for PT conformance testing is shown in figure 3. The key elements of the configuration are the following: • The Implementation Under Test (IUT): - The implementation under test shall provide the DECT ULE radio interface linking it via radio with the test system. ETSI ETSI TS 103 159-1 V1.1.1 (201... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 5.4.2 Test configuration for FT conformance testing | The test configuration for FT conformance testing is shown in figure 4. The key elements of the configuration are the following: • The Implementation Under Test (IUT): - The implementation under test shall provide the DECT ULE radio interface linking it via radio with the test system. - In the case of FT testing, the r... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6 Test interfaces | The present clause defines the interfaces TF1 and TP1 used by the present document. |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.1 Level of definition: functional definition | In order to allow some flexibility in the initial implementation of the interface, only a top level definition, named "functional definition" is provided by the present document. This top level definition is implementation agnostic and compatible with any of the approaches (general or human based) described in clause 4... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.1.1 Possible implementations | The present document allows the implementation of the interfaces by means of Man-Machine Interfaces, and this is the planned schema for the initial stages of the test certification program. Nevertheless, a direct implementation based on a software interface is not ruled out and should be possible even with the present ... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.2 General conventions | |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.2.1 Definitions and terminology | When possible, this section has been written considering any possible implementation of the interface, either via Man-Machine Interfaces or via a direct interface between systems. ETSI ETSI TS 103 159-1 V1.1.1 (2014-04) 20 |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.2.1.1 "Commands" and "signals" | The terms "commands" and "signals" are used interchangeably. Since the present document assumes that first implementations of the interface will be based on MMI, "commands" are normally used for messages sent downstream (towards the IUT) and "signals" for information from the IUT and shown in a MMI. However differentia... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.2.1.2 TP1 and TF1 | Both interface points (TF1 and TP1) are defined in the same set of tables. This organization has been chosen as most commands are identical for both interfaces. A column in the tables indicates if the "command" is applicable to TP1, TF1 or both. The instance indicator is used only for TF1 interface (FP test). |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.2.1.3 Instance indicator | In the Fixed Part side (interface TF1) it is assumed that there may be multiple instances. Each instance refers to a separate DECT context intended for transmission to different PTs. The instance indicator provides the addressing when multiple instances of the DECT protocol (several PPs linked to the FP under test) are... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.2.1.4 "Upstream" and "downstream" | "Up" and "down" column indicates the direction of the command. "Down" means a message sent downstream from the Test system (or from the test operator in case of "human" implementation) towards the IUT. "Up" means a message sent upstream from the IUT to the test system (or a message shown in a MMI to a test operator in ... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.2.2 Organization of the messages | Regarding the organization of the messages, the messages are grouped in three groups: test preparation commands, execution commands and post-processing commands: • Test preparation commands are used before starting the test, but not during the test itself. They are used, i.e. for preloading the test vectors. • Executio... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.3 Semantic definition for interfaces TP1 and TF1 | |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.3.1 Test preparation commands | These commands (see table 1) are used during the test preparation stage and have the purpose to preload the test vectors needed by the test process into the IUT. Two variants are provided: variant 1 loads a vector from a library that is known by both sides of the interface (the test system and the IUT driver/MMI), vari... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.3.2.2 Execution commands and signals: MAC control over ULE connection | These commands (see table 3) are related to MAC operations over the ULE connection different from normal transmission commands given in the previous table. Table 3: Execution commands and signals: other MAC control over ULE connection Direction Signal Parameters Description Applicable to Notes Down Force RELEASE_req (r... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.3.2.3 Execution commands and signals: Mobility Management | These commands (see table 4) are related to Mobility Management operations. Table 4: Execution commands and signals: Mobility Management Direction Signal Parameters Description Applicable to Notes Down REGIST_req (PARI) (PIN) Causes the initial registration procedure of the IUT TP1 Up REGIST_cfm (PARI) Confirmation of ... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.3.2.4 Binding control commands | These commands (see table 5) are only part of the interface TF1 and they are used during FP testing. The bind command is sent upstream when the FP detects that a ULE capable PP has been registered in that FP. The FP then opens an instance in the interface TF1 and allocates the first free instance number to such PP. The... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.3.2.6 Execution commands and signals: CC VC control | The commands described in table 7 are related to Call Control operations related to the ULE VC. Table 7: Execution commands and signals: CC VC control Direction Signal Parameters Description Applicable to Notes Down CONFIG_VC_req (state, flag force state yes/no, attribute content, instance) Causes a "normal" Service Ch... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.3.2.7 Execution commands and signals: IWU-to-IWU transport | These Commands (see table 8) apply to Call Control operations related to the transmission of IWU-to-IWU messages which, in turn, are related to the ULE VC over a Service Call. IWU-to-IWU is assumed to operate as an ancillary channel to normal U-plane. Each IWU-to-IWU transmission is assumed to be a single SDU of this a... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.3.2.8 Execution commands and signals: Paging descriptors | Table 9 describes the commands related to the Paging descriptors. Table 9: Execution commands and signals: Paging descriptors Direction Signal Parameters Description Applicable to Notes Down Retrieve Paging CONFIG_req (instance) Causes the IUT to send the current paging descriptor configuration without any air interfac... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.3.2.9 Execution commands and signals: Paging | Table 10 describes the commands related to Paging. Table 10: Execution commands and signals: Paging Direction Signal Parameters Description Applicable to Notes Down Normal_PAGE_req (Instance, opt repetition time) Causes the FP to send a page to the given PP which has paging descriptors allocated. Paging offset and repe... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 6.3.3 Test post-processing commands | These commands (see table 11) are executed after completion of a test sequence. They allow the test system to retrieve the reception buffer contents for analysis. Post-processing operations start with a "retrieve" command send downstream. Such command is included foreseeing the future evolution of the interface towards... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7 Profile Test Specification | |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.1 Introduction and conventions | |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.1.1 Overview | The Profile Test Specification (PTS) is the core part of the test specification suite. It defines the Test Purposes (TP) and the individual Test Cases (TC) that will define the conformance test of DECT Ultra Low Energy (ULE); Machine to Machine Communications; Part 1: Home Automation Network (phase 1) (TS 102 939-1 [10... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.1.1.1 Description of the different views | The meaning of each view is described in clauses 4.2.5, 4.2.6 and 4.2.10 of the present document. |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.1.2 Test Purposes and Test Cases conventions | This clause defines the Test Purposes (TP) and the Test Cases (TC) required for conformance testing. |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.1.2.1 Organization and terminology | The Test Cases are defined by two tables: one for Portable Part (PP) and other for Fixed Part (FP). The organization in each one of the tables is structured in Test Groups (TGs), Test Purposes (TPs) and Test Cases (TCs). Each Test Group contains one or several Test Purposes (TPs). Each Test Purpose (TP) contains one or... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.1.2.2 Format for Test Purposes (TPs) | The following terminology is used for the Test Purposes: TP_ULE1_XXY Where TP_ULE1 is the common part and refers to "Test Purpose for ULE series 1". The number 1 here is just a conventional identification of a series and does not necessarily mean ULE part 1. While it is true that all Test Purposes for ULE phase 1 will ... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.1.2.3 Format for Test Cases (TCs) | The following terminology is used for the Test Cases: TC_PT_ULE1_XX_TCYZZ for Portable Part Test Cases; TC_FT_ULE1_NA_TCYZZ for Fixed Part Test Cases. Where TC_PT_ULE1 (or TC_FT_ULE1) is the common part and stands for "Test Case for Portable Part ULE series 1" (or "Test Case for Fixed Part ULE series 1"). XX is the gro... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.1.2.4 Column "status" | The status column indicates the status of the Test Cases. It can have the following values: "M" means that the Test Case is mandatory and should be tested in all cases "O" means a Test Case needed by an optional (or conditional) feature (or service or procedure). The need to pass the Test Case or not depends on the spe... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.1.3 General remarks | The following remarks should be taken into account: • In general, a Test Purpose may require several Test Cases to be fully tested. • The same Test Case may be testing several procedures during its execution and in some cases several services or features. This may be identified by means of the traceability tables provi... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.2 Profile Test Specification, Test Cases and Test Purposes (definition view) | |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.2.1 Portable Part Test Purposes | This clause defines the list of Test Purposes and Portable Part Test Cases required for the conformance test of Portable Radio Terminations implementing "DECT Ultra Low Energy (ULE); Machine to Machine Communications; Part 1: Home Automation Network (phase 1)" (TS 102 939-1 [10]). Table 12: Portable Part Test Purposes ... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.2.2 Fixed Part Test Purposes | This clause defines the list of Test Purposes and Fixed Part Test Cases required for the conformance test of Fixed Radio Terminations implementing "DECT Ultra Low Energy (ULE); Machine to Machine Communications; Part 1: Home Automation Network (phase 1)" (TS 102 939-1 [10]). Table 13: Fixed Part Test Purposes Test Grou... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.3 ULE Services, features and procedures to Test Cases traceability tables | |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.3.1 Purpose of this clause | The purpose of this clause is to establish the back traceability between the Test Cases defined in the present document and the services, features and procedures defined in TS 102 939-1 [10]). In other words, the tables included in this clause provide information about which Test Cases are testing the different service... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.3.2 Physical layer (PHL) | The Physical layer (PHL) is out of the scope of the present document. Physical layer is tested by the test specifications EN 300 176-1 [i.1], EN 301 406 [i.2], and (for IMT-2000 bands) EN 301 908-10 [i.3]. ETSI ETSI TS 103 159-1 V1.1.1 (2014-04) 67 |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.3.3 MAC layer | Table 14 gives the list of Portable Part and Fixed Part Test Cases related to the MAC layer services and procedures specified by "DECT Ultra Low Energy (part 1) Home Automation network phase 1" (TS 102 939-1 [10]). Table 14: MAC layer Test Case to procedure mapping for PT and FT MAC layer Service Procedure Reference (s... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.3.4 DLC layer | Table 15 gives the list of Portable Part and Fixed Part Test Cases related to the DLC layer services and procedures specified by "DECT Ultra Low Energy (part 1) Home Automation Network phase 1" (TS 102 939-1 [10]). Table 15: DLC layer Test Case to procedure mapping for PT and FT DLC layer Service Procedure Reference (s... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.3.5 Network (NWK) layer | Table 16 gives the list of Portable Part and Fixed Part Test Cases related to the Network (NWK) layer features and procedures specified by "DECT Ultra Low Energy (part 1) Home Automation Network phase 1" (TS 102 939-1 [10]). Table 16: NWK layer Test Case to procedure mapping for PT and FT NWK layer Feature Procedure Re... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.3.6 Application layer | Table 17 gives the list of Portable Part and Fixed Part Test Cases related to the DECT Application layer features and procedures specified by "DECT Ultra Low Energy (part 1) Home Automation Network phase 1" (TS 102 939-1 [10]). NOTE: This clause refers to the DECT C-plane features named "Application layer" in TS 102 93... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.3.7 Management Entity | Table 18 gives the list of Portable Part and Fixed Part Test Cases related to the Management Entity Services and procedures specified by "DECT Ultra Low Energy (part 1) Home Automation Network phase 1" (TS 102 939-1 [10]). ETSI ETSI TS 103 159-1 V1.1.1 (2014-04) 88 Table 18: Management Entity Test Case to procedure map... |
bcea6c83bb1c38dba3ec1dfeb14c102b | 103 159-1 | 7.3.8 U-plane and interworking services | Table 19 gives the list of Portable Part and Fixed Part Test Cases related to the U-plane and interworking services specified by "DECT Ultra Low Energy (part 1) Home Automation Network phase 1" (TS 102 939-1 [10]). ETSI ETSI TS 103 159-1 V1.1.1 (2014-04) 89 Table 19: U-plane and interworking service Test Case to proced... |
49b8909d15b0b845904375ac54bf1b74 | 103 092 | 1 Scope | The present document contains OMA DM [2] compatible management objects for three ETSI M2M mgmtObj instances: etsiSclMo M2M-TS 102 690 [4], etsiAreaNwkInfo M2M-TS 102 690 [4] and etsiAreaNwkDeviceInfo M2M-TS 102 690 [4]. |
49b8909d15b0b845904375ac54bf1b74 | 103 092 | 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... |
49b8909d15b0b845904375ac54bf1b74 | 103 092 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] OMA-WP-AC-MO-20090127-A: "White Paper on Provisioning Objects", January 2009. [2] OMA-TS-DM_Protocol-V1_3-20121009-C: "OMA Device Management Protocol", October 2012. NOTE: Available at http://member.openmobilealliance.org/... |
49b8909d15b0b845904375ac54bf1b74 | 103 092 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 102 725: "Machine to Machine Communications (M2M); M2M definitions". NOTE: Explanations on the acronyms and abbreviations used in the present ... |
49b8909d15b0b845904375ac54bf1b74 | 103 092 | 3 Definitions, symbols and abbreviations | |
49b8909d15b0b845904375ac54bf1b74 | 103 092 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 102 725 [i.1] apply. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.