Technical Report Document Number
Download 0.83 Mb.
|
- Navigate this page:
- Industry Segment oneM2M Use Cases
- Public Services
- Transportation
1 ScopeThe present document includes a collection of use cases from a variety of M2M industry segments (listed in table 1). Each use case may include a description, source, actors, pre-conditions, triggers, normal and alternative flow of sequence of interactions among actors and system, post-conditions, illustrations and potential requirements. The potential requirements provide an initial view of what oneM2M requirements could arise from the Use Case as seen by the contributor. These are intended to help the reader understand the use case's needs. These potential requirements may have been subsequently submitted by the contributor for consideration as candidate oneM2M requirements, which may or may not have been agreed as a oneM2M requirement (often after much editing). As such, there may not be a direct mapping from the potential requirements to agreed oneM2M requirements [i.15]. Table 1 1
Directory: Deliverables Deliverables -> ArtistDesign Noe jpia year 4 Deliverables -> Cluster: Hardware Platform and mpsoCs D13- 2)-Y4 Deliverables -> Cluster: Modeling and Validation D6- 2)-Y4 Deliverables -> Version number: Version 0 Final Deliverables -> European Holocaust Research Infrastructure Theme [infra-2010 4] ga no. 261873 D19. 2 Metadata Registry Deliverables -> Technical Report Document Number Deliverables -> Project acronym: oversee project title: Open Vehicular Secure Platform Deliverables -> Eco report 03 the licensing of ‘mobile bands’1 in cept 26 January 2015 Deliverables -> Version number: Version 4 Main author Deliverables -> University of central florida project management plan Download 0.83 Mb. Share with your friends:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||