 Now we are talking about the service delivery the service delivery or in this case the managed delivery of services is Handled through a functional architecture, which is of course part of the NGN architecture But now it has some business-oriented names so the three players which are the stakeholders in this MDS based business model that is user Third-party a service provider and engine operator exchange certain information that we call as profiles So what are profiles? We are going to look at that and then we are going to look at the functions which Use these pieces of information that we call profiles To implement the service delivery smoothly and effectively So the MDS basically is Essentially a new business model in which Third-party and NGN operator can collaborate Coordinate exchange important information to realize better QoS oriented service delivery, which has its own Guarantees to the user as well The third-party and NGN implement this by exchanging certain critical information this information is basically Coming from the important Live and registration related parameters of all the three players. We call them as profiles So we have the MDS service profile. We have third-party profiles We have the user profiles and we also have the IDs of the important network elements and Servers which are going to be providing this MDS So the service profile essentially is the service type the class of service What kind of admission control treatment this service has to be offered like it would it always be admissible? Would it be admissible one time or when the bandwidth is available? Then the bandwidth information associated with this service type For instance, is it going to be permanent bandwidth assignment on-demand bandwidth assignment or the bandwidth assignment is very flexible And it's a variable requirement then certain information on security. For instance, what are the triple-a related? functional requirements to be met for this MDS then The port translation if it is using public and private ports then certain additional privacy requirements in terms of encryption Key exchange mechanism key sizes, etc There's another dimension to the service that is is this service a Unicast service or if it is multicast or broadcast service, then what are the parameters which should be addressed for Realizing multicasting or broadcasting then we have third-party Profiles third-party profiles are actually related to the identification mechanisms for the third-party service providers They are recognized mainly on the basis of the domain name the URLs the IP addresses Since each service provider has its own a set of servers known as server farm So there's also a requirement to recognize these servers through the IP addresses and the status as well because at times these servers are Going to be available and at times these servers are not going to be available So the overall capacity Availability and reliability of the services coming from the third-party are highly dependent on the current status of the servers Then we have the individual user Which subscribes to the MDS the user is recognized primarily through its user ID that is username password, etc now in the case of MDS The user is recognized by it by the user profile in MDS, but in the case of NGN user has its own NGN identifier as well. So the translation and mapping of NGN profile to MDS profile and backwards is essentially an important functionality that has to be implemented So at registration time the user has a certain Contract or initial understanding on the general aspects, which are quite abstract at that time On the service provisioning But when a user actually starts to use the service the user can actually select configure or Tailor a service to that time to that user requirements which appear on the fly so the status of The user if it is live or not, and if a user is live What are the current parameter settings that user has adopted have to be exchanged Then we have the Control profile control profile actually means if you look at a service that is a managed service now It requires something from NGN This requirement from NGN actually is in the form of certain control functions For instance service control session control the resource allocation Deallocation the transport and delivery Then the subscriber information has to be exchanged the number of subscribers Because if the number of subscribers vary and if the number of subscribers go excessively Huge that is there are so many subscribers in that case The service can get compromised So this current log in logging information of the users is also very important to be exchanged Each user is again recognized by certain IDs like login information the current port a user is using the service policy that user is Subservient to or is currently based upon Then there's another information which has to be taken care of and it has to be logged It has to be profiled that is the current network information the network state The network path which is being taken by this MDS or the current topology with its options in case Rerouting is required or some load balancing is required Then what are the functional elements or the network nodes which are currently transporting the traffic? And what is the device or per link bandwidth, which is available? So we can actually look at the functional requirements Which emerge out of the MDS and we can translate them into the Functional support which is available in NGN. We can start with the MDS functions on the left-hand side We have the service provider management. That is the third party service coordination between the user third party and The engine operator the session control that is a session and service control when to start a service when 20 service and Terminal access that is the network attachment now all these are Mappable to the engine functions that is application support function service support function Service control function and transport control function But now this is going to be essentially a recap because we already have covered all these aspects in pretty much Detail once we were covering the engine architecture and the IP multimedia subsystem IMS so the application support and service support essentially are used for identifying and Authenticating third party it is implemented through the application to network interface So application or network interface provides the overall abstraction to The third party and the engine operator. So this is a kind of interface that makes the To that is third party and this engine operator to different and distinct network elements the application support function and service support functions are Part of the overall service stratum which are used for identification and authentication of the third party the third party is verified authenticated through an interface that exists between the The user equipment the user side customer premises equipment and the network side So it is implemented through the application to network interface While doing so some kind of service coordination is also realized because the service has to be provisioned a Seamlessly in a very smooth manner that there's no disruption. There's no competition and no conflict as such The service control function is essentially the control of the service In order to initialize a service to terminate a service This is implemented like IP multimedia subsystem the proxy interrogating and serving Call session control functional entity if you recall we did this Few few modules away few modules back now the policy decisions which are to be implemented under certain user contract The path that the user can take and the service Authentication and authorization all this are covered in the service control function. So we are talking I'll recap. We are talking about the Managed delivery service the now the managed delivery service has a lot of interaction between the third party and the Engine operator now the transport control function essentially deals with the implementation down to the network elements in terms of the policies which are coming from the Service stratum the resource allocation has to be ensured The terminal or the user equipment has to be attached to the network so that the services can be delivered right down to the user equipment then location information for user access and whenever a user is moving depending upon its current network Identifier the user should be able to attach to the network by accessing it through certain configurations and parameter adjustment