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.
The TeleHome Approach of Service Provisioning
andreas.sayegh@telekom.de, Deutsche Telekom AG
10.23.03
Starting Point
Enable service providers to perform their services in an effective,
secure and easy to use way.
Dynamic hom...
Features of TeleHome
Broadband (ADSL) connections to the home.
Service application support by providing Core Services: Rem...
Connected Domains
Service Provider
Service
Application
(Backend)
Portal Provider
HostingProvider
Service
Application
(Back...
WAN Connections
ADSL – Connects an OSGi gateway to the Internet.
SOAP over S-HTTP – Connects external service
applications...
SOAP over S-HTTP
Easy to use: Standardized, simple and proven technology.
Not constraining: Gives freedom of choice regard...
Example: Remote Meter Reading (1/3)
Simple Scenario: The ACME utility wants to read the electricity
consumption of a home....
Example: Remote Meter Reading (2/3)
The service application uses the Remote Control Web Service’s locate
operation to find...
Example: Remote Meter Reading (3/3)
Now it uses the invoke operation the contact the bundles (again Java
notation):
byte[]...
Operator’s Major TO-DOs
Constitute a group of operators working on:
Alignment of functional requirements joint with (poten...
Future: The Service Provisioning “Router”
Embedded, OSGi-based device that provides Web
Services interfaces for TeleHome S...
Future: The Service Provisioning “Router”
Service Provider
Service
Application
(Backend)
Portal Provider
HostingProvider
S...
Questions?
Upcoming SlideShare
Loading in …5
×

The TeleHome Approach of Service Provisioning - A Sayegh

397 views

Published on

OSGi World Congress 2003

Published in: Technology
  • Be the first to comment

  • Be the first to like this

The TeleHome Approach of Service Provisioning - A Sayegh

  1. 1. The TeleHome Approach of Service Provisioning andreas.sayegh@telekom.de, Deutsche Telekom AG 10.23.03
  2. 2. Starting Point Enable service providers to perform their services in an effective, secure and easy to use way. Dynamic home configurations and service application stock requires dynamic platform behavior: Dynamic service offering, plug & play driver installation etc. Not constrain the functionality of service applications (too much) Access to any resource of a customer must be under his control. Support service application development by providing Core Services.
  3. 3. Features of TeleHome Broadband (ADSL) connections to the home. Service application support by providing Core Services: Remote Control, Notification, Net Storage, Localization, Accounting. Access to Core Services using Web Services technology. Representation of Core Services on the OSGi service platform as OSGi services. Sharing of profiles for users, devices, service features etc. even in between service applications. Controlled access to all shared resources. Unified authentication with Liberty Project Specification.
  4. 4. Connected Domains Service Provider Service Application (Backend) Portal Provider HostingProvider Service Application (Backend) Service Application (Backend) Service Application (Portlet) TeleHome Service Aggregation Platform (Operator) Internet TeleHome Service Aggregation Platform (Operator) OSGi Service Platform T-DSL Service Application (Bundle) HomeNetworks(UPnP,IEEE1394,EHS,...) Home Appliances Home Appliances TeleHomeWebServices
  5. 5. WAN Connections ADSL – Connects an OSGi gateway to the Internet. SOAP over S-HTTP – Connects external service applications and Core Service bundles to TeleHome Web Services. Optional: VPN Tunnel – Connects an Internet connection to TeleHome platform.
  6. 6. SOAP over S-HTTP Easy to use: Standardized, simple and proven technology. Not constraining: Gives freedom of choice regarding service application backend platform (.NET, J2EE, …) Secure: SSL-based: Identification of calling parties with SSL certificates. Certification Authority (CA) needed.
  7. 7. Example: Remote Meter Reading (1/3) Simple Scenario: The ACME utility wants to read the electricity consumption of a home. Therefore it needs to contact it’s device driver bundle on the OSGi service platform of a customer’s gateway and ask it for the currently consumed amount of kW/h. For fine-grained access control, the service application backend can’t directly connect to the gateway. The service application communicates with the Operator platform to establish a link between the service application backend and the driver. The driver bundle for the metering device exports remote controllable functionality. It registers a CommandService service within the OSGi service registry.
  8. 8. Example: Remote Meter Reading (2/3) The service application uses the Remote Control Web Service’s locate operation to find an OSGi bundle (in Java notation): String[] locate(java.util.Map properties) The service application expects the following OSGi service properties: objectClass=com.acme.ElectricityMeter meterPrincipal=ACME Utility The service application receives session IDs for the found device driver bundles (if it has access rights on these). OSGi Service PlatformACMEDomain TeleHome Web Services TeleHome Service Aggregation Platform Remote Control Service E-Meter Driver Bundle Remote Control Web Service Remote Control Agent locate locate locate Command Service OSGi service registry Metering App Access Control
  9. 9. Example: Remote Meter Reading (3/3) Now it uses the invoke operation the contact the bundles (again Java notation): byte[] invoke(String id, byte[] in) Contents of the sent and received byte arrays are transparent to the Operator platform. The service application expects the returned byte array to contain the electricity consumption value. OSGi Service PlatformACMEDomain TeleHome Web Services TeleHome Service Aggregation Platform Remote Control Service E-Meter Driver Bundle Remote Control Web Service Remote Control Agent invoke invoke invoke Command Service Metering App
  10. 10. Operator’s Major TO-DOs Constitute a group of operators working on: Alignment of functional requirements joint with (potential) service providers. Evaluate usability, security & scalability issues of a Service Enabling Platform. Agree on and standardize Service Provisioning APIs.
  11. 11. Future: The Service Provisioning “Router” Embedded, OSGi-based device that provides Web Services interfaces for TeleHome SP access. Better load distribution, reduces single points of failure. Increases freedom of the operator’s and the service provider’s network layout. “Out-of-the-box” service provisioning. Operator platform could remain transparent. APIs need to be standardized (like e. g. Parlay X Web Services)
  12. 12. Future: The Service Provisioning “Router” Service Provider Service Application (Backend) Portal Provider HostingProvider Service Application (Backend) Service Application (Backend) Service Application (Portlet) TeleHome Service Aggregation Platform (Operator) Internet TeleHome Service Aggregation Platform (Operator) OSGi Service Platform T-DSL Service Application (Bundle) HomeNetworks(UPnP,IEEE1394,EHS,...) Home Appliances Home Appliances TeleHomeWebServices Router TeleHomeWebServices Router TeleHomeWebServices Router
  13. 13. Questions?

×