Summary of Session 4: SDP standardization status and requirements

1
Summary of Session 4 SDP standardization status
and requirements
ITU Workshop on Service Delivery Platforms
(SDP) for Telecommunication Ecosystems from
todays realities to requirements and challenges
of the future(Geneva, Switzerland, 17 October
2011 )

• Huilan Lu, Ph.D.
• SG 13 Vice Chairman

2
Summary (1/3)

• There are good synergies on SDP-related efforts
  among ATIS CSF, IEEE P1903, ITU-T SG 13, and OMA
• ITU-T SG 13 has published Recommendations on open
  service environments and NGN-SIDE requirements,
  and is, among other things, developing the
  NGN-SIDE functional architecture and resource
  management for virtualized network-based cloud
  services (Y.VNC)
• ATIS CSF has completed the CDN Interconnection
  Use Case Specification and High Level
  Requirements and continues on a fast track to
  address the next priorities, including CDN-I,
  Telepresence, Cloud Lifecycle Checklist, Virtual
  desktop infrastructure (VDI), Virtual Private
  Network (VPN)-Oriented Data Center Services
  (VDCS)
• IEEE P1903 is addressing service composition,
  content delivery, and self-organizing management
• OMA standardizes key aspects of the SDP,
  including enablers, policy enforcement, and APIs,
  and has developed many related specifications.

3
Summary (2/3)

• Future challenges and requirements include
• Real-time transactions for M2M
• Service components and 3rd-party applications
  running in the users devices
• Security of users' devices and applications
  running there
• Flexible accounting and payment model to allow,
  e.g., a service component to be executed on
  behalf of a specific user
• Ever faster pace of related standardization
  efforts, and balance of commercial interests and
  true openness
• Instant composition of Web user interface
• SDPs interconnection/federation for geographical
  pervasiveness

4
Summary (3/3)

• Dynamically adaptive, context aware, and self
  organizing services
• Dynamic offering, negotiation and subscription
  for accessing the exposed service components
• High Efficient Rule Engine for service adaptation
• Dynamic update of policies for protecting the
  exposed service components (e.g., policies on
  load control), according to the changes to the
  active subscriptions
• Dynamic mechanisms for optimizing the allocation
  of resources according to the requests of the
  applications, and for guaranteeing a fair use of
  them in the open marketplace
• Decentralized (distributed) SDPs
• All services on demand (i.e., cloud-based SDP)
• Data enhanced SDP (e.g. via data mining
  capabilities)