SDP Search and Record generator
OVERVIEW:
Recognizing the difficulty in creating an SDP service description and search
from scratch, Microsoft is providing a sample utility in bthnscreate.cxx to
automatically create a service or record. This utility can be run to create
an SDP record or to setup an SDP Service, Attribute, or ServiceAttribute
search based on information stored in a human readable file.
This gives examples of Session Description Protocol (SDP)
offer/answer exchanges. Examples include codec negotiation and
selection, hold and resume, and addition and deletion of media
streams. The examples show multiple media types, bidirectional,
unidirectional, inactive streams, and dynamic payload types. Common
Third Party Call Control (3pcc) examples are also given.
SDP, Service Delivery Platform, is more for telecom operators who want to manage the Data Service better delivered to the end device users by bridging with back-end content providers. Operators rely on the content provider to create & distribute data content to different types of devices. This is different from the open world in the internet communication. Operators must control who can access what content based on his rate plans. Also, based the content access results, the process will be recorded as the transaction records based on which billing statements can be generated to collected the money and shared by operators and content providers. I am working on the conceptual architecture level and the real implementation is very complicated due to too many types of service from different content providers to different types of devices based on the different types of the rate plans.
SDP, Service Delivery Platform, is more for telecom operators who want to manage the Data Service better delivered to the end device users by bridging with back-end content providers. Operators rely on the content provider to create & distribute data content to different types of devices. This is different from the open world in the internet communication. Operators must control who can access what content based on his rate plans. Also, based the content access results, the process will be recorded as the transaction records based on which billing statements can be generated to collected the money and shared by operators and content providers. I am working on the conceptual architecture level and the real implementation is very complicated due to too many types of service from different content providers to different types of devices based on the different types of the rate plans.
