Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

PTIN: Overview of a context platform for CaaS

637 views

Published on

These slides presents a brief overview of the context platform developed by Portugal Telecom Innovaçao. This platform will support the context-awareness features of the CDD environment of the CaaS project.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

PTIN: Overview of a context platform for CaaS

  1. 1. PTIN Context Platform CaaS Meeting January 2014 Telma Mota | telma@ptinovacao.pt Ricardo Azevedo | ricardo-a-pereira@ptinovacao.pt Este documento é propriedade intelectual da PT e fica proibida a sua utilização ou propagação sem expressa autorização escrita.
  2. 2. Outline  Context  Context Management  Context Architecture  Context Platform • Requirements • The Platform • The Technologies 27-02-2014 2
  3. 3. Typically what is context?  Information about an entity (e.g. person, room, device)  Examples: • Location • Sensors (e.g. temperature) • Social Networks (e.g. likes, friends) • Web (e.g. weather, calendar) • Activity (e.g. running, sleeping) • Well Being (e.g. heart beat) • …  ToDo: Define what will be the business context 27-02-2014 3
  4. 4. Context Management • Defines the architectural elements for creating non-vertical context-aware services • Context Sources detect context changes and inform Providers • Context Providers publish the context information in the Broker • Context Broker distributes the information to the Consumers • Context Consumers use the information to provide a service • Functions like • aggregate, learn, infer and predict are usually supported by more sophisticated Context Providers • keep a single point of acccess and history are usually supported by the Context Broker by is internal DB or external. 27-02-2014 4
  5. 5. Context Architetcture 27-02-2014 5
  6. 6. Context Platform Requirements • Take into account the ETSI M2M specifications • Resource Oriented Architecture; M2M Information Model • Protocol: CoAP • Publish/Subscribe Model • Typical from messaging architectures • Protocols: MQTT, AMQP, XMPP • History and Reporting • Big Data; Cloudera • Service Oriented Architecture • Service Enablers (e.g. recommendations) • JBoSS/Switchyard 27-02-2014 6
  7. 7. The Platform External Context Consumers Applications/CNA API BUS Context Consumers Support Services Context Broker Context Context Context Provider Provider Providers Context Context Context Provider Provider Sources
  8. 8. The Platform Details Context Consumers APP APP APP API BUS SE SE SE NA Support Services Network Service Cap.Layer Context Broker REST CoAP MQTT AMQP Context Context Context Provider Provider Providers Context Sources Sensors (Humidity, luminosity, t emperature,...) Web (Weather, Calendar, ... SNs(FB, Tweeter,...) Mobile Device (location, net measures
  9. 9. The Technologies • Jboss • Switchyard • Apache Camel + Apache ActiveMQ • ETSI Gateway: NA (Network Application) + NSCL (Network Service Capability Layer ) • Cloudera • Sentry, Hadoop, Impala, Hbase • Interfaces: • HTTP, REST/Jason • Protocols MQTT, AMQP, CoAP 27-02-2014 9
  10. 10. The Model Consumer subscribes 0...n 1 Broker mediates 1 Application Id name 1...n relates to 0...n Entity id entityName is charaterised by 0...n 0...n Provider 1 owns Context ype typeName has 0...n Source 1 1 1...n Context id attributeName attributeVariance value unity timestamp

×