user requests creating of network service composed of one reservation which starts in home domain

• users sends user:create message to his home domain
• home domain creates new network service entity, assigns unique identifier and returns it to user using user:result
• home domain creates new reservation entity marked as PENDING and assigns unique identifier and starts timeout clock for it
• home domain checks if there is sufficient resources and allocated resources at whole path within its domain, these resources are considered reserved and may not be allocated to other reservation
• home domain sends transaction:operation (manager=home) with reservation:create to the second domain
• the second domain checks if there is sufficient resources and allocated resources at whole path within its domain, these resources are considered reserved and may not be allocated to other reservation
• the second domain sends transaction:operation (manager=home) with reservation:create to the third domain
• the third domain checks if there is sufficient resources and allocated resources at whole path within its domain, these resources are considered reserved and may not be allocated to other reservation
• the third domain sends forward:forward (destination=home) with transaction:ack (manager=home) to the second domain
• the second domain sends forward:forward (destination=home) with transaction:ack (manager=home) to home domain
• home domain stops timeout clock for reservation and marks it as OK, network service is also marked OK because all reservations are OK
• user periodicaly sends user:getDetails and receives user:details; when status is OK for service, it is finished

user requests creating of network service composed of one reservation which does not start or end in home domain

• user sends User:Create to his home domain
• home domain creates network service entity and assigns unique identifier and returns it to user using User:Result
• home domain creates new reservation entity marked as PENDING and assigns unique identifier and starts timeout clock for it
• home domain recognizes that it is not starting point of requested flow and sends message to the next domain using Forward:Forward(destination=start domain) with encapsulated Transaction:Operation(manager=home) and Reservation:Create
• the second domain determines that is not starting point of flow and forwards message to the third domain – Forward:Forward with Transaction:Operation(manager=home) and Reservation:Create
• the third domain is the one where flow begins, Reservation:Create message is extracted
• the third domain checks if there are sufficient resources at whole path within its domain, these resources are considered reserved and may not be allocated to other reservation
• the third domain sends Transaction:Operation (manager=home) with Reservation:Create to the next domain
• process repeats until the last domain in requested flow is reached
• the last domain sends Forward:Forward (destination=home) with Transaction:Ack (manager=home) to previous domain
• process repeats until home domain is reached
• home domain stops timeout clock for reservation and marks it as OK, network service is also marked as OK because all reservations are OK
• user periodically sends User:getDetails and receives User:Details; when status is OK for service, it is finished

user requests creating of network service composed of two reservations, one starts in home domain, second ends in home domain

• user sends User:Create to his home domain
• home domain creates new network service entity, assigns unique identifier and returns it to user using User:Result
• home domain creates two new reservation entities marked as PENDING and assigns unique identifier and starts timeout clock for them
• first flow is created similary as flow in the first scenario, the second one is described below
• home domain recognizes that it is not starting point of requested flow and sends message to the next domain using Forward:Forward (destination=start domain) with encapsulated Transaction:Operation(manager=home) and Reservation:Create
• the second domain determines that is not starting point of flow and forwards message to the third domain – Forward:Forward (destination=start domain) with Transaction:Operation(manager=home) and Reservation:Create
• the third domain is the one where flow begins, Reservation:Create message is extracted
• the third domain checks if there are sufficient resources at whole path, these resources are considered reserved and may not be allocated to other reservation
• the third domain sends Transaction:Operation (manager=home) with Reservation:Create to the second domain
• the second domain checks if there are sufficient resources at whole path within its domain, these resources are considered reserved and may not be allocated to other reservation
• the second domain sends Transaction:Operation (manager=home) with Reservation:Create to first(home) domain
• home domain checks if there are sufficient resources at whole path, these resources are considered reserved and may not be allocated to other reservation
• because flow ends in home domain there is no need to send Transaction:Ack message
• home domain stops timeout clock for reservations and marks them as OK, network service is also marked as OK because all reservations are OK
• user periodically sends User:getDetails and receives User:Details; when status is OK for service, it is finished

user requests creating of network service, one domain rejects to make a reservation

• user sends User:Create to his home domain
• home domain creates new network service entity, assigns unique identifier and returns it to user using User:Result
• home domain creates new reservation entity marked as PENDING and assigns unique identifier and starts timeout clock for it
• home domain sends Transaction:Operation (manager=home) with Reservation:Create to the second domain
• second domain checks if there is sufficient resources and allocated resources at whole path within its domain, these resources are considered reserved and may not be allocated to other reservation
• the second domain sends Transaction:Operation (manager=home) with Reservation:Create to third domain
• the third domain checks if there are sufficient resources and says “no available resources at the moment” and makes no reservation
• the third domain sends Transaction:Nack (manager=home) and Reservation:Reject to the second domain
• the second domain releases reserved resources and sends Transaction:Nack (manager=home) and Reservation:Reject to home domain
• home domain releases reserved resources
• home domain stops timeout clock for reservation and marks it as REJECTED, network service is also marked as REJECTED because not all reservations are OK
• user periodicaly sends User:getDetails and receives User:Details; when status is REJECTED for service, it is finished

user requests creating of network service, one domain breaks

• user sends User:Create to his home domain
• home domain creates new network service entity, assigns unique identifier and returns it to user using User:Result
• home domain creates new reservation entity marked as PENDING and assigns unique identifier and starts timeout clock for it
• home domain sends Transaction:Operation (manager=home) with Reservation:Create to the second domain
• second domain checks if there are sufficient resources and allocated resources at whole path within its domain, these resources are considered reserved and may not be allocated to other reservation
• the second domain sends Transaction:Operation (manager=home) with Reservation:Create to the third domain
• the third domain crashes and reservation process cannot be continued
• home domain detects that timeout has expired, then it releases reserved resources and starts to send message Transaction:Operation with Reservation:Rollback
• home domain marks reservation as REJECTED, network service is also marked as REJECTED
• the second domain releases reserved resources and sends Transaction:Operation message with Reservation:Rollback to the third domain
• the third domain releases reserved resources and responses with Transaction:Ack to the second domain
• the second domain sends Transaction:Ack to home domain
• user periodicaly sends User:getDetails and receives User:Details; when status is REJECTED for service, it is finished

user requests cancellation of network service composed of three reservations

• assumed that three reservations are already made
• user sends User:Cancel message to his home domain
• home domain dispatches three messages – Transaction:Operation with Reservation:Cancel to appropriate flows
• home domain waits for three Transaction:Ack messages. For each flow Transaction:Ack message is marked as CANCELLED. When they all arrive, network service is marked as CANCELLED
• user periodicaly sends User:getDetails and receives User:Details; when status is CANCELLED for service, it is finished

user requests creating of network service, acknowledgement lost

• user sends User:Create message to his home domain
• home domain creates new network service entity, assigns unique identifier and returns it to user using User:Result
• home domain creates new reservation entity marked as PENDING and assigns unique identifier and starts timeout clock for it
• home domain checks if there are sufficient resources and allocated resources at whole path within its domain, these resources are considered reserved and may not be allocated to other reservation
• home domain sends Transaction:Operation (manager=home) with Reservation:Create to the second domain
• the second domain checks if there are sufficient resources and allocated resources at whole path within its domain, these resources are considered reserved and may not be allocated to other reservation
• the second domain sends Transaction:Operation (manager=home) with Reservation:Create to the third domain
• the third domain checks if there are sufficient resources and allocated resources at whole path within its domain, these resources are considered reserved and may not be allocated to other reservation
• the third domain sends Forward:Forward (destination=home) with Transaction:Ack (manager=home) to the second domain
• the second domain tries to send Forward:Forward (destination=home) with Transaction:Ack (manager=home) to home domain but is unable because of network problems
• home domain detects that timeout has expired and reservation must be rollbacked(all reserved resources must be released)
• home domain sets new timeout(to get acknowledgement from rollback operation), relseases reserved resources and sends Transaction:Operation (manager=home) with Reservation:Rollback to the second domain
• the second domain releases allocated resources and sends Transaction:Operation (manager=home) with Reservation:Rollback to the third domain
• if the third domain is available then it releases allocated resources and sends back Forward:Forward with Transaction:Ack to the second domain, if not then home domain will detect lack of Rollback Acknowledgement and will send Transaction:Operation (manager=home) with Reservation:Rollback again
• when home domain will get Forward:Forward with Transaction:Ack then it marks reservation as REJECTED, network service is also marked as REJECTED
• user periodicaly sends User:getDetails and receives User:Details; when status is REJECTED for service, it is finished

user requests creating of network service, acknowledgement lost, rollback acknowledgement lost

• user sends User:Create message to his home domain
• home domain creates new network service entity, assigns unique identifier and returns it to user using User:Result
• home domain creates new reservation entity marked as PENDING and assigns unique identifier and starts timeout clock for it
• home domain checks if there are sufficient resources and allocated resources at whole path within its domain, these resources are considered reserved and may not be allocated to other reservation
• home domain sends Transaction:Operation (manager=home) with Reservation:Create to the second domain
• the second domain checks if there are sufficient resources and allocated resources at whole path within its domain, these resources are considered reserved and may not be allocated to other reservation
• the second domain sends Transaction:Operation (manager=home) with Reservation:Create to the third domain
• the third domain checks if there are sufficient resources and allocated resources at whole path within its domain, these resources are considered reserved and may not be allocated to other reservation
• the third domain sends Forward:Forward (destination=home) with Transaction:Ack (manager=home) to the second domain
• the second domain tries to send Forward:Forward (destination=home) with Transaction:Ack (manager=home) to home domain but is unable because of network problems
• home domain detects that timeout has expired and reservation must be rollbacked
• home domain sets new timeout(to get acknowledgement from rollback operation), releases allocated resources and sends Transaction:Operation (manager=home) with Reservation:Rollback to the second domain
• the second domain does not respond so home domain's timeout expires
• home tries to resend Transaction:Operation (manager=home) with Reservation:Rollback to the second domain
• process continues until Transaction:Ack will be sucessully delivered to home domain (which means that rollback operation is done)
• home domain marks reservation as REJECTED, network service is also marked as REJECTED
• user periodicaly sends User:getDetails and receives User:Details; when status is REJECTED for service, it is finished

-- BartoszBelter - 14 Jun 2005

-- MichalB - 14 Jun 2005

-- MarcinKaminski - 03 Jun 2005