reTHINK-project / use-cases

Definition
Artistic License 2.0
2 stars 0 forks source link

H2H inter-domain Manageable Conversation #2

Open pchainho opened 9 years ago

pchainho commented 9 years ago

Actors

Alice and Bob are Identified Consumer that are Conversation Participants

Alice and Bob are subscribers of different Communication Service Providers.

Pre-conditions

Similar to #1 but in this case Alice and Bob are subscribed to different CSPs. They are using the corresponding service behavior - user interface of their CSP (e.g. Alice conversation user experience is set by its service provider).

Differentiation - Market Relevance

Not currently possible with Web Communications. Essential to achieve seamless interoperabilty between any user without having the need to use more than one conversational App.

Remark: The above mentioned description is one option, in which each user keeps their original user experience. There is also the possibility that only one user experience is provided, this would mean that e.g. that Alice (who initiates the call) user experience is ported to Bob, once he accepts the call.

sdruesedow commented 9 years ago

The following is an commented and extended version of the first version above.

Referenced Scenario

Daily Life

Description

Similar to #1 but in this case each participant is subscribed to different CSPs, having each one the service behavior set by its CSP (e.g. Alice conversation usage experience is set by its service provider).

Actors

The emntioned entities above are are not actors as listed and described in "Actors and roles". These are business roles, which are sometimes also present under the same name as actor. Actors would be:

Pre-conditions

Post-conditions

success criteria

Alice communicates with Bob

failure criteria

no communication between Alice and Bob

General Flow / Steps

  1. Alice "calls" Bob with her own communication app via Bobs identifier
  2. Alice's app recognizes that Bob is not customer of own domain
  3. Alice's app contacts Interconnectivity Provider ("connect") to get information about Bob's identifier and communication endpoint
  4. Interconnectivity Provider provides information about Bobs Identity, inkl. Url of Protocol-on-the-fly communication stack
  5. Alice's app downloads/instantiates protocol stub for Bobs domain and establishes signalling channel with Bobs domain.
  6. Signalling is exchanged and communication is established.

Differentiation - Market Relevance

Not currently possible with Web Communications. Essential to achieve seamless interoperabilty between any user without having the need to use more than one conversational App. Overcomes the domination of established communications providers. Building bridges across network borders.

pchainho commented 9 years ago

@sdruesedow the actors described in "Actors and roles" are instances of generic Business Roles for the Usage Scenario. I've started describing these generic Business Roles at https://github.com/reTHINK-project/use-cases/blob/master/docs/D1.1/business-models/business-roles.md

But in general I agree with your more detailed description. A few additional comments:

sdruesedow commented 9 years ago

we (from W1/4 perspective) added authentication and authorization to the pre-condition in order to have a clear separation between registration (1-time process) and authentication/authorization, which happens on every login

pchainho commented 9 years ago

Agree, but what is the difference between registration and subscription?

rebecca-copeland commented 9 years ago

Subscription is taking on the service, creating an account, specifying preferences. Registration - if it is the same as logging to the service - is current participation which also signifies current availability.

My Best

Rebecca

On 10 March 2015 at 11:13, pchainho notifications@github.com wrote:

Agree, but what is the difference between registration and subscription?

— Reply to this email directly or view it on GitHub https://github.com/reTHINK-project/use-cases/issues/2#issuecomment-78034512 .

pchainho commented 9 years ago

In @sdruesedow comment there is a separation between registration and login, if I understood correctly

sdruesedow commented 9 years ago

sorry for the confusion. I agree with Rebecca's comment. In my previous comment I used the wrong term "registration" instead of "subscription"

Dimitrie commented 9 years ago

WP1 Telko reviewed and changed the use case.