Identify Software Service/Location
A software service is a software functionality or a set of software functionalities which provide useful information to the citizens (Santana et al. 2016). This activity aims to capture the location (e.g. roads, bridges, airports, tunnels, buildings, etc.) where software services operate. Smart cities are required to monitor their own environment and events within that environment. Smart platforms can use the location of the software services to provide accurate information to citizens.
Relationship
- Operates in (Software Service, Location): A software service operates in a specific place of the city.
History
A number of smart platforms use data from the city such as the location of the software service to find the appropriate data to offer better services to citizens (Gil-Garcia et al. 2015)
Examples
- Citizens requires to discover software services dynamically, using contextual information such as the location of a service. They can request all software services in around 0.1 km with respect to the location of service identified by the URI (Nesi et al. 2016).
- A user might be interested in a service deployed in a specific location of the city. The user should interrogate the smart city systems to know which particular existing services in the requested urban area contain the information needed (e.g. weather information, intelligent traffic information, air quality information, etc.)(Hernández-Muñoz et al. 2011).
References
- Gil-Garcia, J.R., Pardo, T.A. & Nam, T., 2015. What makes a city smart? Identifying core components and proposing an integrative and comprehensive conceptualization. Information Polity, 20(1), pp.61–87.
- Hernández-Muñoz, J.M. et al., 2011. Smart cities at the forefront of the future internet, Springer Berlin Heidelberg.
- Nesi, P. et al., 2016. Km4City Smart City API: An Integrated Support for Mobility Services. In 2016 IEEE International Conference on Smart Computing, SMARTCOMP 2016. IEEE.
- Santana, E.F.Z. et al., 2016. Software platforms for smart cities: Concepts, requirements, challenges, and a unified reference architecture. ACM Computing Surveys (CSUR), 50(6), p.78.