6 Test Suite Structure (TSS)

6.1 Test groups

The test groups are organized in 2 levels. The first level defines the functional entity of oneM2M. The second level defines the common services functions which are represented in oneM2M functional architecture.

6.1.1 Functional Entity Groups

The functional entity groups identify the types of entity which are specified in oneM2M functional architecture(TS-0001 [1]).

  • AE

  • CSE

6.1.2 Common Services Functions Subgroups

The common services functions subgroups identify the general procedures in each common services functions specified in oneM2M functional architecture (TS-0001 [1]):

  • Registration

  • Data Management and Repository

  • Subscription and Notification

  • Group Management

  • Discovery

  • Location

  • Device Management

  • Communication Management and Delivery Handling

  • Security

6.1.3 oneM2M Resource Primitives specific Operations

A group of resource type specific procedures are defined in oneM2M functional architecture (TS-0001 [1]) and service layer core protocol (TS-0004 [2]). Those procedures can be potentially abstracted with requirements for generating test purposes for conformance testing purpose. Those resource type specific procedures are the complementary procedures to the general procedures defined in oneM2M Common Service Functions (CSF) and will use for subgroups of structures for oneM2M tests. A list of those procedures are including:

  • Resource announcement

  • timeSeries

  • location

  • 3GPP interworking

  • Semantic

  • HAIM

  • Dynamic Authorization

  • FlexContainer

6.2 Test Suite Structure (TSS) for oneM2M

The Test Suite Structure (TSS) for oneM2M will be present as below:

  • Group 1: General Capability (GEN):

    • Subgroup 1.1: Protocol Bindings

    • Subgroup 1.2: Serializations

  • Group 2: AE(AE):

    • Subgroup 2.1: General Capability (GEN)

    • Subgroup 2.2: Registration(REG)

    • Subgroup 2.3: Data Management and Repository(DMR)

    • Subgroup 2.4: Subscription and Notification(SUB)

    • Subgroup 2.5: Communication Management and Delivery Handling(CMDH)

    • Subgroup 2.5.1: Request Message Polling(PCH)

  • Group 3: CSE(CE):

    • Subgroup 3.1: General Capability (GEN)

    • Subgroup 3.2: Registration(REG)

    • Subgroup 3.3: Data Management and Repository(DMR)

    • Subgroup 3.4: Subscription and Notification(SUB)

    • Subgroup 3.5: Group Management(GMG)

    • Subgroup 3.6: Discovery(DIS)

    • Subgroup 3.7: Location(LOC)

    • Subgroup 3.8: Device Management(DMG)

    • Subgroup 3.8.1: Data Management using TimeSeries(TS)

    • Subgroup 3.9: Communication Management and Delivery Handling(CMDH)

    • Subgroup 3.9.1: Request Message Polling(PCH)

    • Subgroup 3.9.2: Response Type(RT)

    • Subgroup 3.10: Security(SEC)

    • Subgroup 3.11: Resource Announcement (ANNC)

    • Subgroup 3.12: 3GPP Interworking(3GPP)

    • Subgroup 3.13: FlexContainer (FLXC)

    • Subgroup 3.14: Dynamic Authorization (DAU)

    • Subgroup 3.15: Semantic (SEM)

    • Subgroup 3.16: Initial Service Provisioning (ISP)

    • Subgroup 3.17: Service Charging and Accounting (CSA)

    • Subgroup 3.18: Service Subscription Management(SSM)

    • Subgroup 3.19: Primitive Profile (PP)

    • Subgroup 3.20: Transaction Management (TMG)

    • Subgroup 3.21: Resource Schedule (SCH)

    • Subgroup 3.22: Process Management (PMG)

    • Subgroup 3.23: Software Management (SM)