Enabler Test Specification (Conformance) for Smart City

Draft Version: 1.0 - 2025-04-16

Open Mobile Alliance

uCIFI-OMA-ETS-Conformance-Smart-City-V1_0-20250416-D

Dev: 14 Jan 2026 16:09:00 rev: 656f03f

Unless this document is clearly designated as an approved specification, this document is a work in process, is not an approved Open Mobile Alliance™ specification, and is subject to revision or removal without notice.

You may use this document or any part of the document for internal or educational purposes only, provided you do not modify, edit or take out of context the information in this document in any manner. Information contained in this document may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior written permission of the Open Mobile Alliance. The Open Mobile Alliance authorizes you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document.

Each Open Mobile Alliance member has agreed to use reasonable endeavors to inform the Open Mobile Alliance in a timely manner of Essential IPR as it becomes aware that the Essential IPR is related to the prepared or published specification.
However, the members do not have an obligation to conduct IPR searches. The declared Essential IPR is publicly available to members and non-members of the Open Mobile Alliance and may be found on the “OMA IPR Declarations” list at https://www.omaspecworks.org/about/intellectual-property-rights/. The Open Mobile Alliance has not conducted an independent IPR review of this document and the information contained herein, and makes no representations or warranties regarding third party IPR, including without limitation patents, copyrights or trade secret rights. This document may contain inventions for which you must obtain licenses from third parties before making, using or selling the inventions. Defined terms above are set forth in the schedule to the Open Mobile Alliance Application Form.

NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE MADE BY THE OPEN MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER OR ITS AFFILIATES REGARDING ANY OF THE IPR’S REPRESENTED ON THE “OMA IPR DECLARATIONS” LIST, INCLUDING, BUT NOT LIMITED TO THE ACCURACY, COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR NOT SUCH RIGHTS ARE ESSENTIAL OR NON-ESSENTIAL.

THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS.

THIS DOCUMENT IS PROVIDED ON AN "AS IS" "AS AVAILABLE" AND "WITH ALL FAULTS" BASIS.

Copyright 2025 Open Mobile Alliance.

Used with the permission of the Open Mobile Alliance under the terms set forth above.

1. uCIFI Conformance Process

1.1. Scope

The uCIFI data model shall be implemented by Smart City device suppliers to run on constrained IoT networks such as NB-IoT, 6LowPAN, Wi-SUN and other generic TCP/IP networks that could support LwM2M over IPv4 and/or IPv6.

To ensure interoperability among devices implementing the uCIFI data model and help end-customers understand which device is compatible with the uCIFI data model, the Conformance Process has been defined.

1.2. Reference

1.2.1. Normative References

1.2.2. Informative References

1.3. Terminology and Conventions

1.3.1. Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

All sections and appendixes, except "Scope" and "Introduction", are normative, unless they are explicitly indicated to be informative.

1.3.2. Definitions

Kindly consult [OMADICT] for more definitions used in this document.

1.3.3. Abbreviations

1.4. Introduction

The objective of this document is to describe the overall uCIFI Conformance Process, including the uCIFI Conformance Tool.

1.4.1. Version 1.0

First version of the document

1.5. Implementation requirements

1.5.0.1. Supported Implementations

Supported targets may include

• Real Devices
• Software Implementations
• Bridge / Connectors (to interconnect legacy or other non-IP devices)

1.5.0.2. Supported Networks

The aim of uCIFI is to provide end-to-end interoperability. Implementations can fit on any standard IPv4 or IPv6 network: Cellular (NB-IoT, LTEM, xG), Wi-SUN, 6LowPAN, Ethernet or Wi-Fi.

uCIFI Data Model is currently modelled using OMA LwM2M objects and resources. For this reason a LwM2M client has to be provided within the implementation being tested. The certifications is performed relying on the Device Management and Information Reporting capabilities defined by the LwM2M standard.

1.5.0.3. Supported APIs

The following LwM2M functionalities should be supported by the client:

From LwM2M 1.0

• Bootstrap interface (optional)

• Client Registration Interface

• Device Management and Service Enablement Interface

  • Read, Discover (optional), Write, Write-Attributes (optional), Execute, Create and Delete
  • Operations on objects, object instances, resources and multiple resource instances

• Information Reporting Interface

  • Observe (optional) and Cancel Observation (optional)
  • Operations on object, objects instances and resource

• Security (optional)

  • DTLS-Based Security
  • Pre-Shared Keys and X.509 Certificates

• Data Formats

  • Plain Text

  • TLV

  • JSON (optional)

Additions from LwM2M 1.1

• Device Management and Service Enablement Interface

  • Read composite (optional)

  • Write composite (optional)

• Information Reporting Interface

  • Observe-composite (optional)

• Send operation handling (optional)

• Security (optional)

  • TLS-Based Security (to be confirmed)

  • OSCORE (optional)

• Data Formats

  • CBOR

  • SenML-JSON (optional)

  • SenML-CBOR

1.6. Steps

1.6.1. Step 1: Candidate product registration

The uCIFI Conformance Software shall provide screens to record information about the candidate product, including:

• Identity card of the candidate product:

• Product Name

• Endpoint Name

• Unique Identifier (GTIN, IMEI, EAN) - retrieved automatically from Device Object 3

• FW / SW Version (retrieved automatically from Device Object 3)

• LwM2M Client Version (retrieved automatically from Registration)

• Conformance Profile (Energy, Smart Streetlight, Environmental Monitoring, Smart Waste, Water Metering, Water Distribution Network, Public Safety, Parking, Traffic & Mobility)

• Supported networks: See 1.5. Implementation requirements

• Previous uCIFI Conformance: in case a previous version of the candidate product already received a uCIFI Conformance, the user shall enter the submission identifier corresponding to that previous certification.

• Declaration of Product Feature List: the uCIFI Conformance Software tests only the LwM2M and uCIFI features that are implemented in the candidate product. This can be managed using an approach similar to PICS (Protocol Implementation Conformance Statement)

It is user responsibility to properly connect the DUT with the correct LwM2M Server (either locally or on cloud)

1.6.2. Step 2: Test case selection

Each test case is specified with a unique name, directly derived from the Test Plan.

For example,

• test_uCIFI_3_1_verify_u_i_p_metering

• test_uCIFI_5_2_manual_switching_on_timestamp

Based on the profile selection, a number of mandatory test cases will be automatically selected.

For example, selecting Smart Streetlight profile would automatically select

• test_uCIFI_2_1_default_dimming_level
• test_uCIFI_3_1_verify_u_i_p_metering
• test_uCIFI_3_2_verify_energy_consumption
• test_uCIFI_5_1_manual_switch
• test_uCIFI_5_3_manual_dimming
• test_uCIFI_5_5_manual_override
• ...

To simplify the test identification, various profiles have been created under profiles folder

• generic_mandatory.txt
• generic_optional.txt
• smart_lighting_mandatory.txt
• smart_lighting_optional.txt

The user is then free to declare support for optional capabilities, thus including additional tests in the execution list.

The tests being executed have a direct correlation with what is declared (or required) to be supported in the Conformance Statement (see later).

1.6.3. Step 3: Test case execution

Test case execution should then be automatically performed, without any user interaction, except for starting them

Tests execution may be requested to halt or continue in case of a failure and tests can be re-executed in case of failure.

Nevertheless, in order to assess the compliance, all mandatory tests shall pass.

Various options to execute the tests can be accounted.

1.6.3.1. Command Line

Tests can be easily invoked from command line by selecting the aforementioned profiles

pytest @profiles/generic_mandatory.txt --leshan_server_ip 127.0.0.1 --leshan_server_port 8080 --device_endpoint dut_name --html=reports/generic_mandatory.html

pytest @profiles/generic_optional.txt --leshan_server_ip 127.0.0.1 --leshan_server_port 8080 --device_endpoint dut_name --html=reports/generic_optional.html

pytest @profiles/smart_lighting_mandatory.txt --leshan_server_ip 127.0.0.1 --leshan_server_port 8080 --device_endpoint dut_name --html=reports/smart_lighting_mandatory.html

pytest @profiles/smart_lighting_optional.txt --leshan_server_ip 127.0.0.1 --leshan_server_port 8080 --device_endpoint dut_name --html=reports/smart_lighting_optional.html

User may be able to follow the execution in real-time or get notified later on, being provided with the result.

1.6.3.2. Visual Studio Code

Visual Studio Code (VS Code) could be also used to execute test cases, providing a simplified interface to pytest

It can also be considered the preferred approach to debug the test executions or when developing new tests

Detailed instructions can be found on the official website https://code.visualstudio.com/docs/python/testing

A JSON settings file is already included into the test folder and should allow for easy customization

1.6.4. Step 4: Test report submission

The report should contain evidence about test execution, including failures, that may help the user to understand what need to be addressed (e.g. dry run, preliminary tests)

The generated report can be then zipped and sent to the Smart City Working Group for review.

[!NOTE]

The report archive should ideally contain the following content:

• one or more reports in HTML format

• the assets folder (needed to keep proper formatting)

• the conftest.py to clearly state the configuration parameters and the versioning

• network captures can be optionally included (such as Wireshark traces)

The user shall not alter the HTML report in any way before submission.

In addition to the report that is automatically generated, it may be required to manually fill an online survey as well (e.g. SurveyMonkey).

In this case coherent results should be indicated.

The following rules should be adopted to provide an acceptance criteria:

1. all mandatory tests should have been executed (ensured by profile selection)
2. all PICS functionalities declared as supported should have a corresponding test having been executed
3. all executed tests should have passed

1.6.5. Step 5: Test report publication

Products that passed the Conformance tests can be publicly listed on OMA Web Site together with the associated Conformance Statement.

2. uCIFI Data Model Implementation Conformance Statement

2.1. References

1. LightweightM2M (LwM2M) Object and Resource Registry
2. uCIFI Certification Test Cases for Generic Profile
3. uCIFI Certification Test Cases for Smart Lighting Profile

2.2. Introduction

To evaluate the conformance of a particular implementation to the uCIFI Data Model, it is necessary to have a statement of which capabilities and options have been implemented for a given implementation.

Such a statement is called Data Model Implementation Conformance Statement.

The implementer is asked to fill each row in the last column (labelled Implemented), specifying which requirement is satisfied or not.

In order to guarantee a minimum level of interoperability, some capabilities are considered mandatory and must be supported for a given use case. Other capabilities, instead, are considered optional and may be supported or not.

It is paramount that mandatory features must be implemented to pass the Conformance Test.

Each requirement is tested by one or more test cases. Tests will be then selected based on the implemented features . To comply with a requirement, all the associated tests should pass.

Each Feature mentioned in the Conformance Statement is associated with a mnemonic code (Item). To simplify readability, similar features are grouped together under the same high-level category.

2.3. Identification of the Implementation

2.4. Conformance Items

The Generic Profile is mandatory and must be supported by all the various use cases.

2.4.1. Generic Profile

2.4.2. Smart Lighting Profile

3. uCIFI Test Cases - Data Model Coverage

3.1. Scope

This section describes the uCIFI Data Model coverage in respect to the uCIFI test cases defined in the various profile specific documents.

3.2. Introduction

uCIFI has specified a certain number of test cases to ensure compliancy with the uCIFI Data Model.

The following tables list for each resource in the data model the corresponding tests that check the specific functionality.

They can be used to better understand which part of the data model may require further review and testing,

3.3. Data Model Coverage

3.3.1. Object 3 - Device

3.3.2. Object 3416 - Outdoor Lamp Controller

3.3.3. Object 3417 - Luminaire Asset

3.3.4. Object 3418 - Electrical Monitor

3.3.5. Object 3452 - Program Scheduler

3.3.6. Object 3453 - Calendar Rule

3.3.7. Object 3454 - Program Function

3.3.8. Object 3457 - Program Manager

3.3.9. Object 3459 - Distributed Sensor Group

3.3.10. Object 3461 - Sensor Group Device Capabilities

4. uCIFI Certification Test Cases for Generic Profile

4.1. Scope

This section describes the uCIFI Test Plan that is used when certifying devices.

4.2. Introduction

This document should cover the definition of test cases that are provided to ensure compliancy with the Data Model published by the uCIFI Alliance.

Test case definition is first done using a flow chart approach, in order to agree on the overall behaviour that has to be expected by Devices Under Test.

Then the test case is mapped into a separate file to be fed into an external tool that could perform automatic tests.

4.3. Specifications and use cases to be addressed

Tests may cover multiple use cases, from Smart Lighting to Smart Waste or more generic Sensor Networks and are divided into functional categories, similar for each use case:

4.3.1. Category #1 – Device On-Boarding

Checking that, when the device connects to LwM2M, the protocol and data model is properly implemented, and the device will work as expected for outdoor lighting.

4.3.2. Category #2 – Configuring

Checking that the device accepts and uses configuration parameters to work properly for outdoor lighting applications.

4.3.3. Category #3 – Monitoring

Checking that the device properly reads and reports electrical (voltage, current, power, energy) and other attributes (e.g. lamp burning hours, temperature, ambient light).

4.3.4. Category #4 – Alarming

Checking that the device reports alarms to the LwM2M servers as required in outdoor lighting applications

4.3.5. Category #5 – Controlling

Checking that the device implements various remote-control mechanisms as required in outdoor lighting applications.

4.3.6. Category #6 – Programming

Checking that the device accepts and properly runs control programs based on astronomical clocks, photocell or fixed time schedule and programs.

4.4. Progress & Notes

5. Test Cases for Generic Profile

5.1. Category #1 – Device On-Boarding

5.1.1. TEST CASE #GEN1.1 – Bootstrap and Security

Test Case Prerequisites

• DUT is connected to and active in the LwM2M server embedded in the Certification Tool

• Supplier declares to support :

  Outdoor Lamp Controller

  • all mandatory resources

Test Case Definition

graph LR
    A[Test Start] --> B[Check that the device is properly <br> connected to the LwM2M server]
    B --> C{Device is connected?}
    C --> |Yes| D["Check that the announced <br> security mechanism is in place <br> (mechanism to be defined)"]
    C --> |No| Fail[Test Failed]
    D --> E{Security is properly <br> implemented?}
    E --> |No| Fail
    E --> |Yes| Success[Test Success]

5.1.2. TEST CASE #GEN1.2 – Mandatory Objects & Resources Type

Test Case Prerequisites

• Client tested device is connected to and active in the LwM2M server embedded in the Certification Tool

• Supplier declares to support :

  Outdoor Lamp Controller

  • all mandatory resources

  Electrical Monitor

  • all mandatory resources

Test Case Definition

graph LR
    A[Test Start] --> B[For each attribute of each object <br> declared in the LwM2M server, <br> check the presence of each  <br> mandatory resource in the uCIFI <br> Data Model]
    B --> C{Each mandatory <br> resource is present?}
    C --> |No| Fail[Test Failed]
    C --> |Yes| D[For each attribute of each <br> object declared in the LwM2M <br> server, check the format of <br> each declared resource <br> compared to the uCIFI <br> Data Model]
    D --> E{Each resource <br> has the right <br> format?}
    E --> |No| Fail
    E --> |Yes| Success[Test Success]

5.2. Data Model Coverage

5.2.1. Object 3 - Device

6. uCIFI Certification Test Cases for Smart Lighting Profile

6.1. Scope

This section describes the uCIFI Test Plan that is used when certifying devices.

6.2. Introduction

This document should cover the definition of test cases that are provided to ensure compliancy with the Data Model published by the uCIFI Alliance.

Test case definition is first done using a flow chart approach, in order to agree on the overall behaviour that has to be expected by Devices Under Test.

Then the test case is mapped into a separate file to be fed into an external tool that could perform automatic tests.

6.3. Specifications and use cases to be addressed

Tests may cover multiple use cases, from Smart Lighting to Smart Waste or more generic Sensor Networks and are divided into functional categories, similar for each use case:

6.3.1. Category #1 – Device On-Boarding

Checking that, when the device connects to LwM2M, the protocol and data model is properly implemented, and the device will work as expected for outdoor lighting.

6.3.2. Category #2 – Configuring

Checking that the device accepts and uses configuration parameters to work properly for outdoor lighting applications.

6.3.3. Category #3 – Monitoring

Checking that the device properly reads and reports electrical (voltage, current, power, energy) and other attributes (e.g. lamp burning hours, temperature, ambient light).

6.3.4. Category #4 – Alarming

Checking that the device reports alarms to the LwM2M servers as required in outdoor lighting applications

6.3.5. Category #5 – Controlling

Checking that the device implements various remote-control mechanisms as required in outdoor lighting applications.

6.3.6. Category #6 – Programming

Checking that the device accepts and properly runs control programs based on astronomical clocks, photocell or fixed time schedule and programs.

6.4. Progress & Notes

6.5. Test Cases for Outdoor Lighting

6.5.1. Category #1 – Device On-Boarding

6.5.1.1. SL1.3 – Read Inventory Data

Test Case Prerequisites

• Client tested device is connected to and active in the LwM2M server embedded in the Certification Tool

• Supplier declares to support :

  Luminaire asset

  • all mandatory resources

Test Case Definition

graph LR
    A[Test Start] --> B[Check that the GTIN <br> is present and not null]
    B --> C{GTIN is present <br> and not null ?}
    C --> |No| Fail[Test Failed]
    C --> |Yes| D[For each declared attribute of <br> the Luminaire Asset object, <br> check that values are not null]
    D --> E{Values are <br> not null?}
    E --> |No| Fail
    E --> |Yes| Success[Test Success]

6.5.1.2. SL1.4 – GPS Position

Test Case Prerequisites

• Client tested device is connected to and active in the LwM2M server embedded in the Certification Tool

• Supplier declares to support :

  Location

  • all mandatory resources

  Global Navigation Satellite System

  • all mandatory resources

Test Case Definition

graph LR
    A[Test Start] --> B["Read Latitude and Longitude from <br> Location (/6/) or GNSS (/3430/) object"]
    B --> C{"Are lat and <br> lon valid <br> (not null)?"}
    C --> |No| Fail[Test Failed]
    C --> |Yes| D[If the GNSS object is implemented, <br> make two reads of lat and lon <br> from the GNSS object within <br> 1 minute interval]
    D --> E{Are values and <br> timestamp <br> consistent?}
    E --> |No| Fail
    E --> |Yes| Success[Test Success]

6.5.1.3. SL1.5 – Replace a Device

Test Case Prerequisites

• Client tested device is connected to and active in the LwM2M server embedded in the Certification Tool

• Supplier declares to support :

  Outdoor Lamp Controller

  • </3416/0/15> Lamp operating hours
  • </3416/0/16> Lamp operating hours reset
  • </3416/0/18> Lamp switch counter
  • </3416/0/19> Lamp switch counter reset

  Electrical Monitor

  • </3418/0/6> Cumulated active energy
  • </3418/0/7> Energy reset

Test Case Definition

graph LR
    A[Test Start] --> B[Read lamp operating hours, <br> lamp switch on counter and <br> cumulative energy value]
    B --> C{Are these values valid <br> and greater than zero?}
    C --> |No| Fail[Test Failed]
    C --> |Yes| D[Reset lamp operating hours, <br> lamp switch on counter and <br> cumulative energy value]
    D --> E{Are these values <br> now equal to zero?}
    E --> |No| Fail
    E --> |Yes| Success[Test Success]

6.5.2. Category #2 – Configuring

6.5.2.1. SL2.1 – Setting Default Dimming Level

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3416/0/3> Dimming level
  • </3416/0/4> Default dimming level

Test Case Definition

graph LR
    A[Test Start] --> B[* all schedules <br> shall have been <br> deleted in advance]
    B --> C["Set default dimming level <br> (/3416/0/4) to a random value <br> between 50 and 100"]
    C --> D[Wait a few <br> seconds]
    D --> E{Check that /3416/0/3 <br> is equal to /3416/0/4}
    E --> |No| Fail
    E --> |Yes| Success[Test Success] 

6.5.2.2. SL2.2 – Setting CLO Parameter

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support :

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/3> Dimming level
  • </3416/0/15> Lamp operating hours
  • </3416/0/16> Lamp operating hours reset
  • </3416/0/30> Constant light output

Test Case Definition

graph TD
    A[Test Start] --> B[Ask user to provide a light point <br> controller with lamp operating <br> hours being significant]
    B --> C{Check that lamp operating hours <br> /3416/0/15 &gt;&gt; 0}
    C --> |No| Fail[Test Failed]
    C --> |Yes| D[Set constant light output <br> /3416/0/30 to TRUE]
    D --> E[Set command /3416/0/1 to 100]
    E --> F{Check that dimming <br> level /3416/0/3 is <br> &lt; command /3416/0/1}
    F --> |No| Fail
    F --> |Yes| G[Reset lamp operating hours <br>/3416/0/16]
    G --> H{Check that dimming <br> level /3416/0/3 is <br> even smaller than <br> before}
    H --> |No| Fail
    H --> |Yes| Success[Test Success] 

6.5.2.3. SL2.3 – Setting VPO Parameter

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support :

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/3> Dimming level
  • </3416/0/41> Virtual Power Output

  Electrical Monitoring

  • </3418/0/4> Active Power

Test Case Definition

graph LR
    A[Test Start] --> B["Set Virtual Power Output <br> (/3416/0/41) to 100"]
    B --> C["Set /3416/0/1 to 100"]
    C --> D{"Check that <br> /3418/0/4 is &gt;&gt; 0 <br> Record it as <br> "max power""}
    D --> |No| Fail[Test Failed]
    D --> |Yes| E["Set Virtual Power Output <br> (/3416/0/41) to 80"]
    E --> F{"Check that /3418/0/4 <br> is equal to 80% <br> of "max power""}
    F --> |No| Fail
    F --> |Yes| Success[Test Success]   

6.5.3. Category #3 – Monitoring

6.5.3.1. SL3.1 – Verify U, I, P Metering Values Consistency

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support :

  Outdoor Lamp Controller

  • </3416/0/1 Command

  Electrical Monitoring

  • </3418/0/1> Supply voltage
  • </3418/0/2> Supply current
  • </3418/0/4> Active Power
  • </3418/0/5> Power Factor

Test Case Definition

graph TD
    A[Test Start] --> B[Set command <br> /3416/0/1 to 100]
    B --> C[Delay / Max <br> Timeout = 2 mins]
    C --> D{Read active power <br> 3418/0/4 and check <br> is &gt;&gt; 0}
    D --> |No| Fail[Test Failed]
    D --> |Yes| E[Read /3418/0/1, <br> /3418/0/2 and <br> /3418/0/5]
    E --> F{Check that <br> supply voltage <br> x supply current <br> = active power}
    F --> |No| Fail
    F --> |Yes| G[Set command <br> /3416/0/1 to 30]
    G --> H[Delay / Max <br> Timeout = 2 mins]
    H --> I{Read /3418/0/5 <br> and verify that <br> is between 0.5 <br> and 1.0}
    I --> |No| Fail
    I --> |Yes| Success[Test Success]   

6.5.3.2. SL3.2 – Verify Energy Consumption When Lamp is Burning

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support :

  Outdoor Lamp Controller

  • </3416/0/1> Command

  Electrical Monitoring

  • </3418/0/4> Active Power
  • </3418/0/6> Cumulated active energy

Test Case Definition

graph TD
    A[Test Start] --> B["Read /3418/0/6 <br> and record it as <br> 'Initial energy'"]
    B --> C["Set command <br> /3416/0/1 to 100"]
    C --> D{"Check that active <br> power /3418/0/4 <br> is &gt;&gt; 0"}
    D --> |No| Fail[Test Failed]
    D --> |Yes| E["Read /3418/0/6. <br> Repeat until change <br> is observed. Max <br> 1 hour timeout"]
    E --> F{"Check that 'initial energy' <br> + (active power * elapsed time) <br> = cumulated energy"}
    F --> |No| Fail
    F --> |Yes| Success[Test Success]   

6.5.3.3. SL3.3 – Verify Lamp Burning Hour Counter When Lamp is Burning

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support :

  Outdoor Lamp Controller

  • </3416/0/1> Command

  • </3416/0/15> Lamp operating hours

Test Case Definition

graph TD
    A[Test Start] --> B["Read /3416/0/15 <br> and record it as <br> 'initial operating hours'"]
    B --> C[Set command <br> /3416/0/1 to 100]
    C --> D{Check that active <br> power /3418/0/4 <br> is &gt;&gt; 0}
    D --> |No| Fail[Test Failed]
    D --> |Yes| E[Read /3416/0/15. <br> Repeat until change <br> is observed. Max <br> 1 hour timeout]
    E --> F{"Check that 'initial <br> operating hours' <br> + elapsed time = <br> lamp operating hours"}
    F --> |No| Fail
    F --> |Yes| Success[Test Success]   

6.5.3.4. SL3.4 – Verify Lamp Switch On Counter

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support :

  Outdoor Lamp Controller

  • </3416/0/1> Command

  • </3416/0/18> Lamp switch counter

  • </3416/0/19> Lamp switch counter reset

Test Case Definition

graph TD
    A[Test Start] --> B["Read /3416/0/18 <br> and record it as <br> 'initial switch counter'"]
    B --> C[Set command <br> /3416/0/1 to 0]
    C --> D[Delay 10 sec]
    D --> E[Set command <br> /3416/0/1 to 100]
    E --> F[Delay 10 sec]
    F --> G["Check that <br> lamp switch counter = <br> 'initial switch counter' + 1"]
    G --> |No| Fail[Test Failed]
    G --> |Yes| H[Reset counter /3416/0/19]
    H --> I{Check that lamp <br> switch counter is <br> equal to 0}
    I --> |No| Fail
    I --> |Yes| Success[Test Success]   

6.5.3.5. SL3.5 – Control Gear Extra Counters

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Since the test is performed using test functionality, device shall be put in such mode by the user prior to test execution

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3416/0/20> Control gear start counter

  • </3416/0/22> Control gear thermal derating

  • </3416/0/23> Control gear thermal derating counter

  • </3416/0/24> Control gear thermal derating counter reset

  • </3416/0/25> Control gear thermal shutdown

  • </3416/0/26> Control gear thermal shutdown counter

  • </3416/0/27> Control gear thermal shutdown counter reset

  uCIFI Test Object

  • <3463/0/0> Test Mode Enabled
  • <3463/0/2> Test Mode Uri
  • <3463/0/3> Test Mode Value

Test Case Definition

graph TD
    A[Test Start] --> B[Enable test mode <br> /3463/0/1 = true]
    B --> C["Write the following set of resources to specific values
             /3463/0/2 = &lt;/3416/0/20&gt; <br> /3463/0/3 = 1"]
    C --> D["/3463/0/2 = &lt;/3416/0/22&gt; <br> /3463/0/3 = true"]
    D --> E["/3463/0/2 = &lt;/3416/0/23&gt; <br> /3463/0/3 = 2"]
    E --> F["/3463/0/2 = &lt;/3416/0/25&gt; <br> /3463/0/3 = true"]
    F --> G["/3463/0/2 = &lt;/3416/0/26&gt; <br> /3463/0/3 = 3"]
    G --> H["Read back resources <br> /3416/0/[20,22,23,25,26]"]
    H --> I{Do they match with the <br> values just written?}
    I --> |False| Fail
    I --> |True| J[Reset counters <br> Execute /3416/0/24 <br> and /3416/0/27] 
    J --> K[Read back /3416/0/23 <br> and /3416/0/26]
    K --> L{Have such counters reset to 0?}
    L --> |False| Fail
    L --> |True| Success[Test Success] 

6.5.4. Category #4 – Alarming

6.5.4.1. SL4.1 – Lamp Failure Alarms

[!WARNING]

A uCIFI Test Object (3463) has been defined in order to simulate some specific conditions

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Since the test is performed using test functionality, device shall be put in such mode by the user prior to test execution

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3416/0/5> Lamp failure
  • </3416/0/6> Lamp failure reason

  uCIFI Test Object

  • <3463/0/0> Test Mode Enabled
  • <3463/0/2> Test Mode Uri
  • <3463/0/3> Test Mode Value

Test Case Definition

graph LR
    A[Test Start] --> B[Enable test mode <br> /3463/0/1 = true]
    B --> C["Write the following set of resources <br> to specific values
             /3463/0/2 = &lt;/3416/0/5&gt; <br> /3463/0/3 = true"]
    C --> D["/3463/0/2 = &lt;/3416/0/6&gt; <br> /3463/0/3 = 1"]
    D --> E[Read back resources <br> /3416/0/5 and /3416/0/6]
    E --> F{Do they match with the <br> values just written?}
    F --> |False| Fail
    F --> |True| Success[Test Success] 

6.5.4.2. SL4.2 – Unexpected Dimming Level

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3418/0/1> Command
  • </3416/0/3> Dimming level

Test Case Definition

graph TD
    A[Test Start] --> B[Message to user to <br> connect a valid driver]
    B --> C["Set constant light output <br> /3416/0/30 to FALSE <br> (if supported)"]
    C --> D[Write /3416/0/1 to 100]
    D --> E[Wait 10 seconds]
    E --> F{Check that /3416/0/3 <br> is close to 100}
    F --> |No| Fail
    F --> |Yes| G[Message to user to <br> disconnect the driver]
    G --> H[Write /3416/0/1 to 80]
    H --> I[Wait 10 seconds]
    I --> J{Check that /3416/0/3 <br> is still close to 100}
    J --> |No| Fail
    J --> |Yes| Success[Test Success] 

6.5.4.3. SL4.3 – High / Low Power Alarm

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3418/0/1> Command

  Electrical Monitor

  • </3418/0/4> Active power
  • </3418/0/10> Low power threshold
  • </3418/0/12> Low power
  • </3418/0/13> High power threshold
  • </3418/0/15> High power

Test Case Definition

graph TD
    A[Test Start] --> B[Write /3416/0/1 to 100]
    B --> C[Wait up to a few minutes]
    C --> D{Check that /3418/0/4 <br> is greater than 0}
    D --> |No| Fail
    D --> |Yes| E[Write /3418/0/10 = /3418/0/4 - 10% <br> Write /3418/0/13 = /3418/0/4 + 10%]
    E --> F{Read /3418/0/12}
    F --> |True| Fail
    F --> |False| G{Read /3418/0/15}
    G --> |True| Fail
    G --> |False| H[Write /3418/0/10 = /3418/0/4 + 10% <br> Write /3418/0/13 = /3418/0/4 - 10%]
    H --> I{Read /3416/0/12}
    I --> |False| Fail
    I --> |True| J{Read /3416/0/15}
    J --> |False| Fail
    J --> |True| Success[Test Success] 

6.5.4.4. SL4.4 – High / Low Voltage

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Electrical Monitor

  • </3418/0/1> Supply voltage
  • </3418/0/20> Low voltage threshold
  • </3418/0/21> Low voltage
  • </3418/0/22> High voltage threshold
  • </3418/0/23> High voltage

Test Case Definition

graph LR
    A[Test Start] --> B{Check that /3418/0/1 <br> is near 110 or 220 volt}
    B --> |No| Fail
    B --> |Yes| C[Write /3418/0/20 = /3418/0/1 - 10% <br> Write /3418/0/22 = /3418/0/1 + 10%]
    C --> D[Wait a few seconds]
    D --> E{Read /3418/0/21}
    E --> |True| Fail
    E --> |False| F{Read /3418/0/23}
    F --> |True| Fail
    F --> |False| G[Write /3418/0/20 = /3418/0/1 + 10% <br> Write /3418/0/22 = /3418/0/1 - 10%]
    G --> H[Wait a few seconds]
    H --> I{Read /3418/0/21}
    I --> |False| Fail
    I --> |True| J{Read /3418/0/23}
    J --> |False| Fail
    J --> |True| Success[Test Success] 

6.5.4.5. SL4.5 – High / Low Current

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/3> Dimming level

  Electrical Monitor

  • </3418/0/2> Supply current
  • </3418/0/16> Low current threshold
  • </3418/0/17> Low current
  • </3418/0/18> High current threshold
  • </3418/0/19> High current

Test Case Definition

graph TD
    A[Test Start] --> B[Write /3416/0/1 to 100]
    B --> C[Wait up to a few minutes]
    C --> D{Check that /3418/0/2 <br> is greater than 0}
    D --> |No| Fail
    D --> |Yes| E[Write /3418/0/16 = /3418/0/2 - 10% <br> Write /3418/0/18 = /3418/0/2 + 10%]
    E --> F[Wait a few seconds]
    F --> G{Read /3418/0/17}
    G --> |True| Fail
    G --> |False| H{Read /3418/0/19}
    H --> |True| Fail
    H --> |False| I[Write /3418/0/16 = /3418/0/2 + 10% <br> Write /3418/0/18 = /3418/0/2 - 10%]
    I --> J[Wait a few seconds]
    J --> K{Read /3418/0/17}
    K --> |False| Fail
    K --> |True| L{Read /3418/0/19}
    L --> |False| Fail
    L --> |True| Success[Test Success] 

6.5.4.6. SL4.6 – Low Power Factor

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3418/0/1> Command
  • </3418/0/3> Dimming level

  Electrical Monitor

  • </3418/0/5> Power factor
  • </3418/0/8> Low power factor threshold
  • </3418/0/9> Low power factor

Test Case Definition

graph LR
    A[Test Start] --> B[Write /3416/0/1 to 100]
    B --> C[Wait up to a few minutes]
    C --> D{Check that /3418/0/5 <br> is greater than 0}
    D --> |No| Fail
    D --> |Yes| E[Write /3418/0/8 = /3418/0/5 - 10%]
    E --> F{Read /3418/0/9}
    F --> |True| Fail
    F --> |False| G[Write /3418/0/8 = /3418/0/5 + 10%]
    G --> H{Read /3416/0/9}
    H --> |False| Fail
    H --> |True| Success[Test Success] 

6.5.4.7. SL4.7 – Extra Failures

[!WARNING]

A uCIFI Test Object (3463) has been defined in order to simulate some specific conditions

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Since the test is performed using test functionality, device shall be put in such mode by the user prior to test execution

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3416/0/7> Control gear failure

  • </3416/0/8> Control gear failure reason

  • </3416/0/9> Relay failure

  • </3416/0/10> Day burner

  • </3416/0/11> Cycling failure

  • </3416/0/12> Control gear communication failure

  uCIFI Test Object

  • <3463/0/0> Test Mode Enabled
  • <3463/0/2> Test Mode Uri
  • <3463/0/3> Test Mode Value

Test Case Definition

graph TD
    A[Test Start] --> B[Enable test mode <br> /3463/0/1 = true]
    B --> C["Write the following set of resources to specific values
             /3463/0/2 = &lt;/3416/0/7&gt;  <br> /3463/0/3 = true"]
    C --> D["/3463/0/2 = &lt;/3416/0/8&gt;  <br> /3463/0/3 = 1"]
    D --> E["/3463/0/2 = &lt;/3416/0/9&gt;  <br> /3463/0/3 = true"]
    E --> F["/3463/0/2 = &lt;/3416/0/10&gt; <br> /3463/0/3 = true"]
    F --> G["/3463/0/2 = &lt;/3416/0/11&gt; <br> /3463/0/3 = true"]
    G --> H["/3463/0/2 = &lt;/3416/0/12&gt; <br> /3463/0/3 = true"]
    H --> I[Read back resources from <br> /3416/0/7 to /3416/0/12]
    I --> J{Do they match with the <br> values just written?}
    J --> |False| Fail
    J --> |True| Success[Test Success] 

6.5.5. Category #5 – Controlling

6.5.5.1. SL5.1 – Manual Switching

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/2> Command in action
  • </3416/0/3> Dimming level

Test Case Definition

graph LR
    A[Test Start] --> B["Set constant light output <br> /3416/0/30 to FALSE <br> (if supported)"]
    B --> C[Write /3416/0/1 to 100]
    C --> D[Wait 10 seconds]
    D --> E{Check that /3416/0/2 <br> and /3416/0/3 <br> are close to 100}
    E --> |No| Fail
    E --> |Yes| F[Write /3416/0/1 to 0]
    F --> G[Wait 10 seconds]
    G --> H{Check that /3416/0/2 <br> and /3416/0/3 are 0}
    H --> |No| Fail
    H --> |Yes| Success[Test Success] 
    

6.5.5.2. SL5.2 – Manual Switching with ON Timestamp

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Device

  • </3/0/13> Current Time

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/2> Command in action
  • </3416/0/17> Lamp ON timestamp

Test Case Definition

graph LR
    A[Test Start] --> B[Write /3416/0/1 to 0]
    B --> C[Read /3/0/13 and record time T1]
    C --> D[Wait 10 seconds]
    D --> E[Write /3416/0/1 to 100]
    E --> F[Wait 10 seconds]
    F --> G[Read /3/0/13 and record time T2]
    G --> H{Check that /3416/0/17 is <br> greater than T1 and <br> smaller than T2}
    H --> |No| Fail
    H --> |Yes| Success[Test Success] 
    

6.5.5.3. SL5.3 – Manual Dimming

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/2> Command in action
  • </3416/0/3> Dimming level

Test Case Definition

graph LR
    A[Test Start] --> B["Set constant light output <br> /3416/0/30 to FALSE <br> (if supported)"]
    B --> C["Write /3416/0/1 to <br> [100,75,50,25,0]"]
    C --> D[Wait 10 seconds]
    D --> E{"Check that /3416/0/2 <br> and /3416/0/3 are close <br> to [100,75,50,25,0]"}
    E --> |No| Fail
    E --> |Yes| Success[Test Success] 
    

6.5.5.4. SL5.4 – Manual Dimming with Minimum Dimming Level

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/2> Command in action
  • </3416/0/3> Dimming level
  • </3416/0/37> Minimum dimming level

Test Case Definition

graph LR
    A[Test Start] --> B["Set constant light output <br> /3416/0/30 to FALSE <br> (if supported)"]
    B --> C[Write /3416/0/1 to 100]
    C --> D[Wait 10 seconds]
    D --> E{Check that /3416/0/2 <br> and /3416/0/3 are <br> close to 100}
    E --> |No| Fail
    E --> |Yes| F[Write /3416/0/1 to 1]
    F --> G[Wait 10 seconds]
    G --> H{Check that /3416/0/3 <br> is close to /3416/0/37}
    H --> |No| Fail
    H --> |Yes| Success[Test Success] 
    

6.5.5.5. SL5.5 – Manual Override

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/2> Command in action
  • </3416/0/3> Dimming level
  • </3416/0/4> Default dimming level
  • </3416/0/53> Manual override default duration
  • </3416/0/54> Manual override active

Test Case Definition

graph TD
    A[Test Start] --> B[Set default dimming level <br> /3416/0/4 = 80]
    B --> C[Set default duration <br> /3416/0/53 = 60]
    C --> D[Write dimming level <br> /3416/0/1 = 50]
    D --> E[Wait 10 seconds]
    E --> F{Check that /3416/0/2 <br> and /3416/0/3 <br> are close to 50}
    F --> |No| Fail
    F --> |Yes| G{Check that /3416/0/54 <br> is true}
    G --> |No| Fail
    G --> |Yes| H[Wait 60 seconds]
    H --> I{Check that /3416/0/2 <br> and /3416/0/3 <br> are close to 80}
    I --> |No| Fail
    I --> |Yes| J{Check that /3416/0/54 <br> is false}
    J --> |No| Fail
    J --> |Yes| Success[Test Success] 
    

6.5.6. Category #6 – Programming

6.5.6.1. SL6.1 – Simple ON/OFF Program

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/3> Dimming level

  Program Scheduler

  • </3452/0/1> State
  • </3452/0/2> Priority
  • </3452/0/4> Program Function
  • </3452/0/6> Output Instances
  • </3452/0/7> Output Targets

  Program Function

  • </3454/0/4> Time Input Array
  • </3454/0/5> Time Output Array

  Program Manager

  • </3457/0/16> Reset schedule objects

Test Case Definition

graph TD
    A[Test Start] --> B["Reset schedule objects &lt/3457/0/16>
            Set or get device time &lt/3/0/13>
            Set or get device timezone &lt/3/0/14>
            "]
    B --> C["Create the following Program Scheduler:
            /3452/0/1 = true
            /3452/0/2 = 0
            /3452/0/4 = 0
            /3452/0/6/0 = &lt/3416/0>
            /3452/0/7/0 = 1"]
    C --> D["Create the following Program Function:
            /3454/0/4/0 = now + 1 minute; now + 2 minutes
            /3454/0/5/0 = 100; 0
            "]
    D --> E[Wait 1 minute]
    E --> F{Check that <br> /3416/0/2 is 100}
    F --> |No| Fail
    F --> |Yes| G[Wait 1 minute]
    G --> H{Check that <br> /3416/0/2 is 0}
    H --> |No| Fail
    H --> |Yes| Success[Test Success] 
    

6.5.6.2. SL6.2 – Simple Dimming Program

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/3> Dimming level

  Program Scheduler

  • </3452/0/1> State
  • </3452/0/2> Priority
  • </3452/0/4> Program Function
  • </3452/0/6> Output Instances
  • </3452/0/7> Output Targets

  Program Function

  • </3454/0/4> Time Input Array
  • </3454/0/5> Time Output Array

  Program Manager

  • </3457/0/16> Reset schedule objects

Test Case Definition

graph TD
    A[Test Start] --> B["Reset schedule objects &lt/3457/0/16>
            Set or get device time &lt/3/0/13>
            Set or get device timezone &lt/3/0/14>
            "]
    B --> C["Create the following Program Scheduler:
            /3452/0/1 = true
            /3452/0/2 = 0
            /3452/0/4 = 0
            /3452/0/6/0 = &lt/3416/0>
            /3452/0/7/0 = 1"]
    C --> D["Create the following Program Function:
            /3454/0/4/0 = now+1mn; now+2mn; now+3mn; now+4mn; now+5mn
            /3454/0/5/0 = 100; 90; 80; 70; 0
            "]
    D --> E[Wait 1 minute]
    E --> F{Check that <br> /3416/0/2 is 100}
    F --> |No| Fail
    F --> |Yes| G[Wait 1 minute]
    G --> H{Check that <br> /3416/0/2 is 90}
    H --> |No| Fail
    H --> |Yes| I[Wait 1 minute]
    I --> J{Check that <br> /3416/0/2 is 80}
    J --> |No| Fail
    J --> |Yes| K[Wait 1 minute]
    K --> L{Check that <br> /3416/0/2 is 70}
    L --> |No| Fail
    L --> |Yes| M[Wait 1 minute]
    M --> N{Check that <br> /3416/0/2 is 0}
    N --> |No| Fail
    N --> |Yes| Success[Test Success] 
    

6.5.6.3. SL6.3 – Multiple Calendars and Programs

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Device

  • </3/0/13> Current Time

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/3> Dimming level

  Program Scheduler

  • </3452/0/1> State
  • </3452/0/2> Priority
  • </3452/0/3> Calendar Rules
  • </3452/0/4> Program Function
  • </3452/0/6> Output Instances
  • </3452/0/7> Output Targets

  Calendar Rule

  • </3453/0/2> Start Date
  • </3453/0/3> End Date
  • </3453/0/4> Date Rule

  Program Function

  • </3454/0/4> Time Input Array
  • </3454/0/5> Time Output Array

  Program Manager

  • </3457/0/16> Reset schedule objects

Test Case Definition

graph TD
    A[Test Start] --> B["Reset schedule objects &lt/3457/0/16>
            Set or get device time &lt/3/0/13>
            Set or get device timezone &lt/3/0/14>
            "]
    B --> C["Create the following Program Scheduler:
            /3452/0/1 = true
            /3452/0/2 = 2
            /3452/0/3/0 = 0
            /3452/0/4 = 0
            /3452/0/6 /0 = &lt/3416/0>
            /3452/0/7/0 = 1
            "]
    C --> D["Create the following Program Scheduler:
            /3452/1/1 = true
            /3452/1/2 = 1
            /3452/1/3/0 = 1
            /3452/1/4 = 1
            /3452/1/6/0 = &lt/3416/0>
            /3452/1/7/0 = 1
            "]
    D --> E["Create the following Program Scheduler:
            /3452/2/1 = true  
            /3452/2/1 = 0
            /3452/2/3/0 = 2
            /3452/2/4 = 2
            /3452/2/6/0 = &lt/3416/0>
            /3452/2/7/0 = 1
            "]
    E --> F["Create the following Calendar Rule:
            /3453/0/2/0 = --01-01
            /3453/0/3/0 = --06-31
            /3453/0/4 = * * *
            "]
    F --> G["Create the following Calendar Rule:
            /3453/1/2/0 = --07-01
            /3453/1/3/0 = --12-31
            /3453/1/4 = * * *
            "]
    G --> H["Create the following Calendar Rule:
            /3453/2/2/0 = --01-01
            /3453/2/3/0 = --12-31
            /3453/2/4 = * * 6,7
            "]
    H --> I["Create the following Program Functions:
            /3454/0/4/0 = 18:00; 21:00; 02:30; 06:00
            /3454/1/4/0 = 18:00; 21:00; 02:30; 06:00
            /3454/2/4/0 = 18:00; 21:00; 02:30; 06:00
            /3454/0/5/0 = 100; 80; 40; 0
            /3454/1/5/0 = 100; 75; 50; 0
            /3454/2/5/0 = 100; 60; 55; 0
            "]
    I --> J["The tool shall test 5 different dates, times
            and associated levels to make sure the
            scheduler/calendar is properly executed:
            
            Test 1 = 2023.01.03 – 23:00 => dimming = 80
            Test 2 = 2023.01.08 – 23:00 => dimming = 60
            Test 3 = 2023.01.09 – 04:00 => dimming = 40
            Test 4 = 2023.10.16 – 04:00 => dimming = 50
            Test 5 = 2023.10.16 – 10:00 => dimming = 0
            "]
    J --> K{"For each test, set the
            date/time with /3/0/13 and
            verify that /3416/0/2 is
            equal to the expected value"}
    K --> |False| Fail
    K --> |True| Success[Test Success] 
    

6.5.6.4. SL6.4 – Astro Program

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Device

  • </3/0/13> Current Time

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/3> Dimming level

  Program Scheduler

  • </3452/0/1> State
  • </3452/0/2> Priority
  • </3452/0/4> Program Function
  • </3452/0/6> Output Instances
  • </3452/0/7> Output Targets

  Calendar Rule

  • </3453/0/4> Date Rule

  Program Function

  • </3454/0/4> Time Input Array
  • </3454/0/5> Time Output Array

  Program Manager

  • </3457/0/16> Reset schedule objects

Test Case Definition

graph TD
    A[Test Start] --> B["Reset schedule objects &lt/3457/0/16>
            Set or get device time &lt/3/0/13>
            Set or get device timezone &lt/3/0/14>
            "]
    B --> C["Create the following Program Scheduler:
            /3452/0/1 = true
            /3452/0/2 = 0
            /3452/0/4 = 0
            /3452/0/6/0 = &lt/3416/0>
            /3452/0/7/0 = 1
            "]
    C --> D["Create the following Program Function:
            3454/0/4/0 = S; R
            3454/0/5/0 = 100; 0
            "]
    D --> E["Set location to Paris
            /3430/0/34 = 48.8588548
            /3430/0/35 = 2.347035
            "]
    E --> F["The tool shall test a few different dates,
            times and associated levels to make sure
            the scheduler/calendar is properly executed:
            
            Test 1 = 2023.06.20 – 21:30 => dimming = 0
            Test 2 = 2023.06.20 – 22:30 => dimming = 100
            Test 3 = 2023.06.21 – 05:15 => dimming = 100
            Test 4 = 2023.06.21 – 06:15 => dimming = 0
            "]
    F --> G{"For each test, set the
            date/time with /3/0/13 and
            verify that /3416/0/2 is
            equal to the expected value"}
    G --> |False| Fail
    G --> |True| Success[Test Success] 
    

6.5.6.5. SL6.5 – Run Condition

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Device

  • </3/0/13> Current Time

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/3> Dimming level

  Program Scheduler

  • </3452/0/1> State
  • </3452/0/2> Priority
  • </3452/0/4> Program Function
  • </3452/0/6> Output Instances
  • </3452/0/7> Output Targets
  • </3452/0/9> Off when inactive

  Program Function

  • </3454/0/1> Run Condition
  • </3454/0/4> Time Input Array
  • </3454/0/5> Time Output Array

  Program Manager

  • </3457/0/16> Reset schedule objects

Test Case Definition

graph TD
    A[Test Start] --> B["Reset schedule objects &lt/3457/0/16>
            Set or get device time &lt/3/0/13>
            Set or get device timezone &lt/3/0/14>
            "]
    B --> C["Create the following Program Scheduler:
            /3452/0/1 = true
            /3452/0/2 = 0
            /3452/0/3/0 = 0
            /3452/0/4 = 0
            /3452/0/6/0 = &lt/3416/0>
            /3452/0/7/0 = 1
            /3452/0/9 = true
            "]
    C --> D["Create the following Calendar Rules:
            /3453/0/4 = * * 1-5
            "]
    D --> E["Create the following Program Function:
            /3454/0/1/0 = 18:00~04:00
            /3454/0/4/0 = 00:00
            /3454/0/5/0 = 80
            "]
    E --> F["Set default dimming level
            /3416/0/4 = 20
            "]
    F --> G["The tool shall test a few different dates,
            times and associated levels to make sure
            the scheduler/calendar is properly executed:
            
            Test 1 = 2023.06.20 – 22:00 => dimming = 80
            Test 2 = 2023.06.21 – 06:00 => dimming = 0
            Test 3 = 2023.06.24 – 22:00 => dimming = 20
            Test 4 = 2023.06.25 – 06:00 => dimming = 20
            "]
    G --> H{"For each test, set the
            date/time with /3/0/13 and
            verify that /3416/0/2 is
            equal to the expected value"}
    H --> |False| Fail
    H --> |True| Success[Test Success] 
    

6.5.6.6. SL6.6 – Dynamic Control (Local)

[!WARNING]

A uCIFI Virtual Sensor (3464) has been defined in order to provide a simulated stimulus to the device under test

Test Case Prerequisites

• Client tested device is connected to and active in LwM2M servers embedded in the Certification Tool

• Success of all generic test cases

• Supplier declares to support:

  Outdoor Lamp Controller

  • </3416/0/1> Command
  • </3416/0/3> Dimming level

  Program Scheduler

  • </3452/0/1> State
  • </3452/0/2> Priority
  • </3452/0/4> Program Function
  • </3452/0/5> Input Sources
  • </3452/0/6> Output Instances
  • </3452/0/7> Output Targets

  Program Function

  • </3454/0/6> Single Sensor Input Array
  • </3454/0/8> Sensor Output Array

  Program Manager

  • </3457/0/16> Reset schedule objects

  uCIFI Virtual Sensor

  • </3464/0/3> Bool Value

Test Case Definition

graph TD
    A[Test Start] --> B["Reset schedule objects &lt/3457/0/16>
            Set or get device time &lt/3/0/13>
            Set or get device timezone &lt/3/0/14>
            "]
    B --> C["Create the following Program Scheduler:
            /3452/0/1 = true
            /3452/0/2 = 0
            /3452/0/4 = 0
            /3452/0/5/0 = &lt/3464/0/3>
            /3452/0/6/0 = &lt/3416/0>
            /3452/0/7/0 = 1
            "]
    C --> D["Create the following Program Function:
            /3454/0/6/0 = 0; 1
            /3454/0/8/0 = 0; 100
            "]
    D --> E["Simulate a stimulus
            /3464/0/3 = true"]
    E --> F{"Check current dimming
             /3416/0/2 = 100?"}
    F --> |False| Fail
    F --> |True| G["Clear the simulated stimulus
            /3464/0/3 = false"]
    G --> H{"Check current dimming
             /3416/0/2 = 0?"}
    H --> |False| Fail
    H --> |True| Success[Test Success] 
            
    

Appendix A. Change History (Informative)

A.1 Approved Version History