Later, in step 21, the SP selects the best VIP to which he submits a service negotiation request (step 22).
The user device starts connecting to the selected neighboring transmitter by sending a link switching request (step 8).
The broker replies with a list of VIPs offering service enablers that comply with the request (step 20).
The VIP then sends a resource negotiation request (step 6), specifying the requested essential services and their constraints, to the selected PIP.
Meanwhile, a SP (wishing to create VN2) sends (using its VRNF) the broker a VIP discovery request (step 19) containing a document describing the service enablers to be used, their desired availability, cost, and constraints.
In turn, the VIP (wishing to create VN1) sends a PIP discovery request (step 3) containing a document describing the resources to be leased, their desired availability, cost, and constraints.
He formulates a request (Step 1), gets a response in terms of a composed service (Step 2), executes the composed service (Step 3) and rates his degree of satisfaction regarding the execution result (Step 4). Figure 4 The OTF Computing process, involving end user, OTF provider and service providers.
At this point, the proposed admission control mechanism retrieves both soft and hard limits from the request (step 1), computes the forward candidate set (FCS) for the target (steps 2 and 3) (by selecting nodes that are closer to the destination, based on the ETX metric, than the current node), and computes the total available bandwidth on the FCS (steps 4 and 5).
When a streaming request of a user is submitted as shown in Figure 1 (step 2) the IP-Address of an edge server is requested (step 3), selected and delivered by the load balancer plugin.
