ebRTC). Enabling horizontals across third-party verticals via a federated approach. Using common core smart/predictive analytics and policy-based closed loop response capabilities. Leveraging broad cloud deployment locations to place latency-sensitive capabilities and applications close to the edge as needed. Leveraging partners and hosted platforms for vertical-specific IoT businesses where needed. Supporting flexible deployment options and support structures: Hosted on a cloud and managed by the service provider Hosted and managed by the vendor on the service provider's cloud Hosted and managed by the vendor Horizontal/cross-vertical capabilities across vertical platforms will be enabled using cloud- driven and API exposure principles and API/platform federation. Each vertical platform is sup- ported on a cloud and exposes its APIs to an API development studio, which is part of a service enablement platform. This studio is used to develop horizontal/cross-vertical applications that con- nect to the vertical platforms via APIs. The APIs are used by the application to trigger cross-vertical capabilities as needed. An example is enabling quick passage of an ambulance by adjusting traffic lights via API federation across the "Connected Car" and "Smart Cities" IoT verticals. An applica- tion can be built to connect the connected car and smart cities verticals via APIs exposed by the API platform. Another example is delivering emergency medicine in case of accidents or disasters via API federation across the drones and mHealth verticals. The services would leverage reusable Service Platforms service enabler capabilities that are currently supported by the network to expand the breadth of IoT services offered including WebRTC voice and video, messaging, notification, speech recog- nition, VoLTE, etc. These capabilities can be combined with any service provider's network for IoT service offerings. Examples of this are use of speech recognition for connected car services, WebRTC real-time video and telematics data feed 