# Use Case Title

## Submitters
<!--
List use case submitters

Format:
- Name (Organization)
-->

## Changelog
<!--
List the changes to the document, incl. state, date, and PR URL.

State is one of: pending, approved, amended, deprecated
Date is an ISO 8601 (YYYY-MM-DD) string.
PR is the pull request that submitted the change, including information such as the diff, contributors, and reviewers.

E.g.:
- [approved](URL of PR) (2022-04-01)
- [amended](URL of PR) (2022-05-01)
-->

## Market Segments
<!--
What IoT market segments does this use case address? 
Examples are:
- Home (home automation, home improvement, energy efficiency)
- Lifestyle (wearable computing, entertainment and music, family, leisure, pets, toys, drones)
- Health (fitness, monitoring, measurement, diagnosis, surgery, patience care)
- Mobility (connected cars, eBikes, aerospace & airports, marine, rail & stations, automotive, traffic)
- Retail (stores, shops, convenience)
- Energy (transmission & distribution, fossil, nuclear, alternative)
- Cities (infrastructure, water & wastewater, HVAC, lighting, security, life safety)
- Manufacturing (mining, oil & gas, production, supply chain)
- Public & Services (schools, universities, government, banking, insurance, administration, commercial services)
- Other (environment, military, agriculture, hospitality)

Reference and more details: https://iot-analytics.com/iot-market-segments-analysis/

Name both the category and industry, e.g.:
- Retail (stores, convenience)
-->

## Motivation
<!--
Summarize the problems that are solved by the use case and why they are important in the relevant domain
-->

## Target Users
<!--
List all stakeholders that are involved in the use case. Examples are:
- Device Manufacturer
- Device Owner
- Device User
- Device Maintainer
- Cloud Provider
- Service Provider
- Network Operator
- Software Developer
- Software Deployer
- Software Integrator
-->

## Description
<!--
Provide the description of the use case from target users' perspective
-->

## Existing solutions
<!--
How is the given use case currently implemented in the industry, with or without EdgeX?
List and describe each approach. Highlight possible gaps.
-->

## Requirements
<!--
Provide a list of (non-)functional requirements that aren't addressed by EdgeX. 
Include security and privacy requirements that are specific to the given domain.
If appropriate, report requirements as feature requests on corresponding EdgeX projects and provide the URLs.

Format:
- Summary of the requirement ([repo#issue-num](URL))
-->

## Related Issues
<!--
List any reported issues that are relevant and useful to support this use case but aren't feature requests mapped to requirements. 

Format:
- Issue title ([repo#issue-num](URL)): description of the relevance
-->

## References
<!--
List additional references

Format:
- [Title](URL)

The following are references used to create this template:
- https://iot-analytics.com/iot-market-segments-analysis/
- https://www.w3.org/TR/wot-usecases
-->