For the IPTV service, we use the SDP as the IPTV service provider, service broker and con- tent broker. Hence, SDP service interfaces are required to support these roles and satisfy the
associated business relationship policies. However, the SDP must also provide diverse ser- vice interfaces for the external IPTV application provider and media provider. These service interfaces aid in IPTV application development and content management respectively. To uncover the required SDP services and interfaces, we define the use cases shown in Figure 10.4. The use cases illustrate functions required by the SDP to perform service provider, service broker and content broker roles. In addition, the use cases show functions provided by the SDP to satisfy external application and media providers. The use cases and their descriptions are:
Set User Presence: the IPTV application changes end-user presence information stored by the SDP.
Get User Presence: the IPTV application requests end-user presence information from the SDP.
Setup Call: the IPTV application requests a normal or multiparty voice/video call to be setup between end-users.
Send Message: the IPTV application requests a message be sent to an end-user.
Find Content: the IPTV application requests a list of specific content from content broker, who is the SDP. The application may query details on content contained in the list. Deliver Content: the IPTV application requests the delivery of content from a media source
to end-users. The content includes audio, video and data.
Register Content: the media provider application registers itself as a content provider with the SDP (content broker). In addition, the application provides information about its available content, such as location, format, description, time of availability and length.
Manage Content: the media provider application updates its available content informa- tion that has been registered with the SDP. The media provider application may also remove content from its registration or add new content.
Register Services: the IPTV service provider, who is also the SDP, uses an application to register its IPTV service, such that end-users can locate, register and use it.
Manage Subscribers: the IPTV service provider application requests registration of end- users to access and use the IPTV service. The application may also deregister end- users and verify login information.
Get User Presence Send Message Set User Presence Setup Call IPTV App Provider Media Provider Find Content Deliver Content Register Content Manage Content
Content Broker Role Service Provider
Role
Service Delivery Platform
IPTV Service Provider Manage Subscribers Service Broker Role IPTV End-User/ Service Subscriber Find Me Services Manage Accounts Register Service
Figure 10.4: SDP Specific Use Cases
Manage Accounts: the IPTV service provider application obtains information about end- users billable accounts. The application may also modify these accounts, such as billing end-users for delivery of special content.
Find Me Services: the end-user application requests the SDP, who is also a service bro- ker, to obtain a list of available services, such as the IPTV service. The end-user application also obtains details on the available services in the list.
Based on these use cases and the previous SDP reference model, business model and IPTV use cases, we define the SDP to provide the following services:
presence service: provides an interface that manages end-users presence information. call service: provides and interface that enables application to invoke classical and en-
hanced telephony services.
messaging service: enables messaging functions to be performed on its interface.
stream service: enables applications to invoke its interface, so as to delivery content from a media source to end-users.
content management service: exposes an interface for applications to register, manage and locate content.
Simple Service Middleware
Service Function Middleware
Resource Function Middleware
Resource Middleware
Intermediate Service Middleware
Complex Service Middleware IPTV Service Provider App IPTV Provider App End-User IPTV App Service Function Service Function Service Function Service Function Service Function Service Function Service Function Resource Function Resource Function Resource Function Resource Function Resource Function Resource Function Resource Function
Resource Resource Resource
Resource Resource Resource Resource
Media Provider App
Subscription Presence Call
Service Manager
Billing Message Stream
Content Content Manager
End-User Domain Subscriber Domain Service Platform Domain Enterprise Domain
Connectivity Provider Domain Converged Network Domain OSS/BSS Domain
Figure 10.5: SDP Framework with Simple Services Enabling IPTV
service management service: provides an interface to enable end-user applications to lo- cate the IPTV service offered by a service provider.
subscription service: provides an interface for the IPTV service provider application to register, deregister and verify login details of end-users.
billing service: its interface abstracts access to telco OSS/BSS functionality, such as charg- ing end-users and providing account management.
We present the identified SDP services and their interfaces within the SDP framework. This SDP framework is shown in Figure 10.5. In the figure, we contain these services in the simple GSOA. This enables IPTV and media provider applications to use converged network capabilities at a high level of abstraction. As a result, the providers do not require extensive telco network knowledge.
To complete the framework we require intermediate and complex services. Also, lower layer functions must be present with their associated physical resources. However, rather than building all GSOAs and physical resources, we reuse existing technologies. These technologies must provide open standard-based service interfaces that are applied across all GSOA layers of the SDP framework.