Enhanced Messaging Product

Transcription

1 CTIA s Wireless Internet Caucus Enhanced Messaging Action Team (EM Team) Enhanced Messaging Product Product Feature: Group Messaging Use Cases & Call Flows Documentation Final October 17, 2008 See also documentation for EM Product; Product Feature: Presence. EM Group Messaging Feature 1

2 Base Assumptions for Technical Support The inter-carrier messaging protocol will be based on OMA SIMPLE IM specs (see below) Both MSISDN/MDN and SIP URI could be used to address a group participant in a group conversation Use of aggregator (IWP/A) to interconnect carriers is optional but needs to be supported Standards will be followed for all Use Cases Reference to OMA SIMPLE IM V10: : main page: EM Group Messaging Feature 2

3 Base Assumptions for Customer Experience Ad Hoc groups are made extemporaneously, and are valid as long as they meet the criteria for starting and ending groups in this set of Use Cases. (04-01, and 05-01A, B, &C) Permanent groups are groups which have group ID and group members stored for use and reference at later dates, and can be communicated with outside of the timing parameters defined in this set of Use Cases. All UC & CF were created presuming only support for Ad Hoc groups at this time. A Polite Rejection/Block is one in which the User being blocked does not receive notification that they are blocked from joining the group. A Rude Rejection/Block is one in which the User being blocked does receive notification that they are being blocked from joining the group. EM Group Messaging Feature 3

4 Documentation Outline The following Use Cases and Call Flows represent the output of a Team effort to determine the minimal requirements needed to support a cross-carrier Enhanced Messaging Product with Product Feature of Group Messaging. Documentation for each Use Case include: Scenarios, Action Steps, and (CF) Call Flow. Presented in the following order: 04-01a Create a Group- manual Opt-In 04-01b Create a Group - automatic Opt-in User Declines a GM Invite 04-03a Sending MultiMedia - Content Embedded Sending MultiMedia - Content referenced via 04-03b link Joining an Active Group Removed Attempting to Join an Ended Group User Decides to Exit an Active Group User Re-Joins and Active Group after Exiting or Declining Receiving a List of Active Group Members Support of Display Name A Group Initiator Ends a Group Conversation 05-01b Rules to end a Group Conversation 05-01c Message sent after Group Ends A Group Initiator Blocks a Specific Group Member Legacy - EM carrier not EM device Legacy - non-em carrier EM Group Messaging Feature 4

5 Background for UC & CF Use Case Functional Areas: FA-04 Group Messaging Initiation and Sessions FA-05 Group Messaging Group Management FA-06 Group Messaging Legacy Support Enhanced Messaging Use Cases For each Use Case, the subscribers (a.k.a. actors or system users), the mobile carrier with which they have a relationship, and the Interoperability Use Cases that describe the system are defined. In this section, the main users and operators are described, and in the following section, their interaction via Use Cases. Note that these use cases are meant to cover the intercarrier aspects of enhanced messaging services only. In order to add context and understanding to the use cases, some actions are specified that would be undertaken by the use case actors, or their operator/service provider. In all cases, these user-specific (or operator-specific) actions are for example only, and do not indicate any specific implementation by a specific carrier. Such actions are identified by italicized, blue text. EM Group Messaging Feature 5

6 Mobile Carrier G Messenger User Property Name Name Brief Description Responsibilities Relationships Operations Attributes Characteristics Competence Requirements Diagrams Brief Description UserG A Mobile Carrier G customer (user) who has registered for Mobile Carrier G Enhanced Messenger. The lifecycle of the subscriber UserG begins with registration on the system. Once registered, UserG uses the Mobile Carrier G messaging functionality to communicate Has a billing relationship with Mobile Carrier G Has an account with Mobile Carrier G Messenger system Has Contacts on his Contact List Is on the Contact List of other users The user uses the following operations within the system: Add/Delete/Block Contacts Exchange Messages with Contacts Watch Presence Status information of Contacts Participate in Private Group discussions Mobile Carrier G, Mobile Carrier D, and Mobile Carrier Z all have relationships through an Interworking Partner/Aggregator (IWP/A) or direct connection to exchange certain attributes and message types. The Mobile Carrier G Messenger User is assumed to be a member of the general public who has a mobile phone (with Mobile Carrier G as Mobile Carrier) The Mobile Carrier G Messenger User is assumed to be able to write SMS messages. He is assumed to be familiar with at least one of the Mobile Carrier G Messenger clients (i.e. WAP, SMS. ) N/a EM Group Messaging Feature 6

7 Mobile Carrier D Messenger User Property Name Name Brief Description Responsibilities Relationships Operations Attributes Characteristics Competence Requirements Diagrams Brief Description UserD A Mobile Carrier D customer (user) who has registered for Mobile Carrier D Enhanced Messenger. The lifecycle of the subscriber UserD begins with registration on the system. Once registered, UserD uses the Mobile Carrier D messaging functionality to communicate Has a billing relationship with Mobile Carrier D Has an account with Mobile Carrier D Messenger system Has Contacts on his Contact Lists Is on the Contact List and/or special List of other users The user uses the following operations within the system: Add/Delete/Block Contacts Exchange Messages with Contacts Watch Presence Status information of Contacts Participate in Private Group discussions Mobile Carrier G, Mobile Carrier D, and Mobile Carrier Z all have relationships through an Interworking Partner/Aggregator (IWP/A) or direct connection to exchange certain attributes and message types. The Mobile Carrier G Messenger User is assumed to be a member of the general public who has a mobile phone (with Mobile Carrier G as Mobile Carrier) The Mobile Carrier G Messenger User is assumed to be able to write SMS messages. He is assumed to be familiar with at least one of the Mobile Carrier G Messenger clients (i.e. WAP, SMS.) N/a EM Group Messaging Feature 7

8 Mobile Carrier Z Customer (Non-Messenger) Property Name Name Brief Description Responsibilities Relationships Operations Attributes Characteristics Competence Requirements Diagrams Brief Description UserZ (ie Legacy) A Mobile Carrier Z customer (user) who is not an enhanced messaging customer because Mobile Carrier Z does not support the service from an intercarrier perspective. None Has a billing relationship with Mobile Carrier Z Has friends who use the Mobile Carrier Z or Enhanced Messaging services through Mobile Carriers D or G The customer uses the following operations within the system: Receive Invitations Registration Receives/sends messages from/to friends UserG and UserD Mobile Carrier G, Mobile Carrier D, and Mobile Carrier Z all have relationships through an Interworking Partner/Aggregator or direct connection to exchange certain attributes and message types. The Mobile Carrier Z Mobile Customer is assumed to be a member of the general public who has a mobile phone (with Mobile Carrier Z as Mobile Carrier) The Mobile Carrier Z Messenger User is assumed to be able to write SMS messages. N/a EM Group Messaging Feature 8

9 Use Case Create a Group Scenario 04-01A = Manual Opt-In Scenario 04-01B = Automatic Opt-In EM Group Messaging Feature 9

10 UC Create a Group; Scenarios Primary User UserD1, D2, G1, G2 Precondition User D1, D2, G1 and G2 are subscribers with Mobile Carriers D and G respectively. Each are enhanced messaging customers. Alternate Scenarios Or Extensions Message Content If either UserG1 or UserG2 decline the request from UserD1, UC applies. As long as the group session is still open, UserG1 or G2 could accept or decline (i.e. the invitation to the group does not expire as long as the group is still active). EM Server should support deferred messages. UC-04-01: <Invitation>: "You have been invited by User D1 to join Group XYZ. Would you like to join the Group?" UC-04-01: <Acceptance>: "User G1 has joined Group XYZ" EM Group Messaging Feature 10

11 Action Step UC Create a Group; Action Steps UserD1 is the initiator of the group conversation; D1 sends a message to UserD2, UserG1 and UserG2. Format could look like <Invitation> system message User G1 and User G2 receive prompts to opt-in and accepts the invitation. Response The group messaging system at Mobile Carrier D sends out System <Acceptance> messages to all group participants as it receives the acceptance messages. The messages indicate that specific users have joined the conversation. Mobile Carrier D sends the UserGen message created by UserD1 to each recipient as it receives opt-in responses from each destination. Mobile Carrier D is responsible for creating and managing the group messaging session. Mobile Carrier D must send requests to UserG1 and UserG2 to join the group conversation. This is done through the IWP/A. Since UserD2 is a Mobile Carrier D subscriber, that carrier has responsibility for how UserD2 will be added to the conversation. This is not an intercarrier issue. Mobile Carrier G sends an <Acceptance> message for UserG1 and UserG2 through the IWP/A back to the group messaging system at Mobile Carrier D. The IWP/A passes the <acceptance> messages to Mobile Carrier G. The IWP/A passes the UserGen messages to Mobile Carrier G. UserG1 and UserG2 receive the UserGen message UserG1 replies to the UserGen message The Group Messaging system at Mobile Carrier D sends the UserGen message to UserD1, UserD2, and UserG2. Mobile Carrier G passes the UserGen message to the IWP/A who must forward the group message to the group messaging function at Mobile Carrier D. UserD1, UserD2, and UserG2 receive the UserGen reply message EM Group Messaging Feature 11

12 CF 04-01A Create a Group Scenario A - Manual Opt-In EM Group Messaging Feature 12

13 UC 04-01B Scenario B = Automatic Opt In; Scenarios Number / Title UC-04-01B Automatic Opt-In Invite Scenario B Primary User Precondition Alternate Scenarios Or Extensions Message Content UserD1, D2, G1, G2 User D1, D2, G1 and G2 are subscribers with Mobile Carriers D and G respectively. Each are enhanced messaging customers. If any User opts out, UC applies. As long as the group session is still active, any User can opt out. EM Server should support deferred messages. <Auto Opt-in> You have been added to [groupxyz]. Optional information on opt out procedure or List the Following Members are in group <GroupXYZ> <UserG1, User, G2, User G3> Users who are opted-in in order of auto-acceptance: <Acceptance>: "User G1 has joined Group XYZ" EM Group Messaging Feature 13

14 Action Step UC 04-01B Scenario B = Automatic Opt In; Action Steps UserD1 is the initiator of the group conversation; D1 creates and sends a system <Auto Opt In> message to UserD2, UserG1 and UserG2. User G1, User G2, and User D2 are automatically opted into the group session. The group messaging system at Mobile Carrier D sends out system <Auto Opt In> messages to all group participants. The messages indicate that specific users have joined the conversation. Mobile Carrier D sends the UserGen messages created by UserD1 to each recipient as it receives opt-in responses from each destination. Response Mobile Carrier D is responsible for creating and managing the group messaging session. Mobile Carrier D sends system <Auto Opt In> notification messages to UserG1 and UserG2 to join the group conversation. This is done through the IWP/A. Since UserD2 is a Mobile Carrier D subscriber, that carrier has responsibility for how UserD2 will be added to the conversation. This is not an intercarrier issue. Mobile Carrier G sends a signaling acceptance back to the group messaging system at Mobile Carrier D. Mobile Carrier D acknowledges automatic acceptance by User D2. This is not an intercarrier issue. The IWP/A passes the acceptance messages to Mobile Carrier G. The IWP/A passes the UserGen group messages to Mobile Carrier G. UserG1 and UserG2 receive the User Gen message UserG1 replies to the Use Gen message The Group Messaging system at Mobile Carrier D sends the UserGen message to UserD1, UserD2, and UserG2. Mobile Carrier G passes the UserGen message to the IWP/A who must forward the group message to the group messaging function at Mobile Carrier D. UserD1, UserD2, and UserG2 receive the UserGen reply message EM Group Messaging Feature 14

15 CF 04-01B Create a Group Scenario B Automatic Opt-in EM Group Messaging Feature 15

16 Use Case User Declines a GM Invite EM Group Messaging Feature 16

17 UC User Declines a Group Messaging invitation; Scenarios Primary User Precondition Scope UserD1, D2, G1, G2 UserD1 has set up a Group Conversation among UserD2 and UserG1 and UserG2 (UC-04-01) This Use Case is relevant to 04-01A Manual Opt In. Message Content <Decline >: <User G1> has declined your invitation to join group <Group Name>. EM Group Messaging Feature 17

18 UC User Declines a Group Messaging invitation; Action Steps Action Step UserG1 declines the invitation to the group. Response Mobile Carrier G sends the system <decline> message to the IWP/A, who routes the system message back to the group messaging system at Mobile Carrier D. Mobile Carrier D removes UserG1 from the group messaging session. Since UserG1 declines the initial group request, a <decline> message is only sent back to the initiator of the group, UserD1. UserG1 no longer receives messages for this group (but could still participate in other groups). EM Group Messaging Feature 18

19 CF User Declines a GM invite User D1 User D2 EM Server D (Host) IWP/A EM Server G User G1 User G2 UserG1 declines the invitation to the group session G1 Declines invite conversation G1 Server forwards Decline message Host Server receives decline and removes G1 from sessioin A message is sent to the group originator indicating that UserG1 has declined the group invitiation. G1 has declined the conversation EM Group Messaging Feature 19

20 Use Case Sending Multi Media during Conversation Scenario 04-03A = Content Embedded in Message Scenario 04-03B = Content referenced with Link EM Group Messaging Feature 20

21 UC A & B Sending Multimedia Content during a Group Conversation Scenario A = Content Embedded; Scenario B = url Link Scenario Primary User Other Users Precondition UserD1, UserD2, UserG1 and UserG2 are in a group messaging session. UserD1 decides to send Multimedia content to the others in the group. UserD1 UserD2, UserG1, UserG2 All group members are engaged in a group conversation as specified in UC Alternate Scenarios Or Extensions Scope Size of content 04-03B = UserD1 sends an enhanced UserGen message with a url type link to Multimedia content to the group Multimedia may include video, pictures, music, audio or other new file types. Support of sizes by file type will be negotiated between carriers and can be expected to be adjusted over time. Note that embedded content sizes should- at a minimumfollow current standards specifications. EM Group Messaging Feature 21

22 UC 04-03A Sending Multimedia Content Scenario A = Content Embedded; Action Step Action Step UserD1 sends Multimedia content embedded in a UserGen message to the group Response Mobile Carrier D passes the UserGen message to Mobile Carrier G. All participants (excluding UserD1) receive the UserGen message on their devices through their respective mobile carriers. They are able to display or playback the multimedia content upon reading the message. EM Group Messaging Feature 22

23 UC 04-03B Sending Multimedia Content Scenario B = Content Referenced as url link; Action Steps Action Step UserD1 sends an enhanced UserGen message with a url type link to Multimedia content to the group Response Mobile Carrier D passes the UserGen message to Mobile Carrier G. All participants (excluding UserD1) receive the message on their devices through their respective mobile carriers. They are able to access the Multimedia content in the enhanced message by clicking the url link. EM Group Messaging Feature 23

24 UC A & B: Sending Multi Media EM Server D (Host) IPA/A EM Server G User D1 User D2 User G1 User G2 Option A: User D1 sends multimedia content in a message to the group Message w/multimedia Server forwards message Server forwards message Server forwards message Server forwards message Server forwards message Server forwards message Server forwards message Embedded Option B: User D1 sends multimedia content to the group which is distributed as a link to the content Message w/multimedia Stores Multimedia Content Server forwards message w/url Server forwards message w/url Server forwards message w/url Server forwards message w/url Server forwards message w/url Server forwards message w/url Server forwards message w/url As url link D2 uses URL to fetch multimedia content D2 uses URL to fetch multimedia content G2 does not fetch multimedia content EM Group Messaging Feature 24

25 Use Case Joining an Active Group EM Group Messaging Feature 25

26 UC Joining an Active Group; Scenario Scenario Primary User Precondition Scope Message Content UserD1 has started a group conversation (as per 04-01), which has been on going for a period of time when UserG2 decides to join. UserD1, D2, G1, G2 User D1, D2, G1 and G2 are subscribers with Mobile Carriers D and G respectively. Each are enhanced messaging customers. The group conversation must be active. Pre- Condition Note: if all group members are opted in automatically, then there would be no need for this Use Case. Receiving no past messages upon joining was discussed as the customer experience desired, and for storage reasons. <Acceptance>: "User G1 has joined Group XYZ" EM Group Messaging Feature 26

27 UC Joining an Active Group; Action Step Action Step UserD1 is the initiator of the group conversation; UserD1 creates and sends a UserGen message to UserD2, UserG1 and UserG2. Response As per scenarios, Mobile Carrier G could implement a service where all of its subscribers are automatically opted-in to a group messaging session. Or could require each subscriber manually approve their participation in the group. Nevertheless, the intercarrier use case requires that a positive response be sent back to Mobile Carrier D for the group session. For this case only UserG1 immediately joins the group. Group messages are created and sent between the current, active members of the group. After some period of time, UserG2 decides to accept the group invitation and sends their manual opt-in message as per 04-01A. The group messaging system at Mobile Carrier D sends out a system <acceptance> message to all group participants as it receives the positive response messages from UserG2. Mobile Carrier D is responsible for creating and managing the group messaging session. Mobile Carrier D must send requests (response can be either manual or Automatic as specified in 04-01A,B) to UserG1 and UserG2 to join the group conversation. This is done through the IWP/A. Since UserD2 is a Mobile Carrier D subscriber, each carrier has responsibility for how UserD2 will be added to the conversation. This is not an intercarrier issue. Mobile Carrier G sends a system <acceptance> message for UserG1 through the IWP/A back to the group messaging system at Mobile Carrier D. The IWP/A passes the group messages to Mobile Carrier G for UserG1. Mobile Carrier G sends a a system <acceptance> for UserG2 through the IWP/A back to the group messaging system at Mobile Carrier D. The IWP/A passes the <acceptance> messages to Mobile Carrier G. Accepting the invitation will result in UserG2 automatically receiving all future messages, but none from the past. EM Group Messaging Feature 27

28 CF Joining an Active Group EM Group Messaging Feature 28

29 Use Case Removed Removed Receiving Conversation History EM Group Messaging Feature 29

30 Use Case Joining an Ended Conversation EM Group Messaging Feature 30

31 UC Attempting to Join an Ended Group; Scenario Scenario Primary User Precondition Alternate Scenarios Or Extensions Scope Message Content UserD1 has started a group conversation, which has been on going for a period of time and then ends per UC At that point, UserG2 decides to join. UserD1, D2, G1, G2 User D1, D2, G1 and G2 are subscribers with Mobile Carriers D and G respectively. Each are enhanced messaging customers. The group conversation must be inactive. Opt In scenarios of Manual or Automatic will affect this Use Case. If a Group Name is no longer stored and is not recognized, then an error system message response of <Group Name does not Exist> will be sent. Given the Ad-Hoc group status, the above GroupXYZ may not be relevant. A permanent group would have a permanent Group name. <Acceptance>: "User G1 has joined Group XYZ" <Ended Message>: The group you are attempting to join, <Group Name>, has ended. <Group Name does not Exist>: The group you are attempting to join, <Group Name>, is not found in our records. EM Group Messaging Feature 31

32 UC Attempting to Join an Ended Group; Action Steps Action Step UserD1 is the initiator of the group conversation; D1 creates and sends a message to UserD2, UserG1 and UserG2. Response All participants except UserG2 join the group, as per Group conversation takes place between active members of the group. After some period of time, UserG2 decides to accept the group invitation and sends their opt-in message, as per 04-01A. The group messaging system at Mobile Carrier D recognizes that the group UserG2 is trying to join is ended. Mobile Carrier D will send an error system <Ended Group> message back to Carrier G s group messaging system. At some point, the group is ended per UC Mobile Carrier G sends a system <acceptance> message for UserG2 through the IWP/A back to the group messaging system at Mobile Carrier D. Mobile Carrier G receives the error system <Ended group> message. Further action by Mobile Carrier G is not an intercarrier issue. EM Group Messaging Feature 32

33 UC Joining an Ended Conversation (Based on 04-01A scenario) EM Group Messaging Feature 33

34 Use Case User Exits Active Group EM Group Messaging Feature 34

35 UC User Decides to Exit an Active Group; Scenario Primary User Precondition Message Content UserD1, D2, G1, G2 UserD1 has set up a Group Conversation among UserD2 and UserG1 and UserG2 (UC-04-01) < Exit >: User G1 has left Group XYZ" EM Group Messaging Feature 35

36 UC User Decides to Exit an Active Group; Action Steps Action Step UserG1 decides to exit the group conversation after already accepting. Response Mobile Carrier G sends the signaling <Exit> message to the IWP/A, who routes the message back to the group messaging system at Mobile Carrier D. Mobile Carrier D removes UserG1 from the group messaging session. In addition, a system <exit> notification message is sent to all of the remaining group participants indicating that UserG1 has left the conversation. The IWP/A takes the <exit> notification message from Mobile Carrier D and forwards it to Mobile Carrier G for delivery to UserG2 (who is still participating in the conversation). UserG1 no longer receives messages for this group (but could still participate in other groups). EM Group Messaging Feature 36

37 CF User Decides to Exit an Active Group User D1 User D2 EM Server D (Host) IWP/A EM Server G User G1 User G2 UserG1 decides to exit the group conversation after already accepting G1 decides to exit conversation G1 Server forwards exit message Host Server receives exit message and removes G1 from sessioin A message is sent to all of the remaining group participants indicating that UserG1 has left the conversation. G1 has left the conversation G1 has left the conversation G1 has left the conversation Mobile Carrier G receives G1 has left the conversation message Mobile Carrier G sends G1 has left the conversation to users still participating in session EM Group Messaging Feature 37

38 Use Case Re-Join an Active Group after exiting or declining EM Group Messaging Feature 38

39 UC User Re-Joins an Active Group after Exiting or Declining; Scenario Primary User Precondition UserD1, D2, G1, G2 UserD1 has set up a Group Conversation among UserD2 and UserG1 and UserG2 (UC-04-01A, B). UserG1 has left the group either by declining the original invitation (UC 04-02) or by exiting the group after joining (UC04-07). Alternate Scenario #1 Attempting to re-join an inactive group after leaving or declining is identical to UC Message Content <Acceptance>: "User G1 has joined Group XYZ" <Rejoin >: At this time, this will be supported on a carrier by carrier decision. EM Group Messaging Feature 39

40 UC User Re-Joins an Active Group after Exiting or Declining; Action Steps Action Step UserG1 uses their messaging inbox to select a group conversation they previously left or declined. UserG1 exercises the command to <Re-join> the group (or accept the group invitation they previously declined). Response Mobile Carrier G sends the system <Acceptance> message to the IWP/A, who routes the message back to the group messaging system at Mobile Carrier D. Mobile Carrier D adds UserG1 to the group messaging session. The group messaging system at Mobile Carrier D sends out a system <Acceptance> message to all group participants that UserG1 has joined the conversation. Joining the conversation will result in UserG1 automatically receiving all future messages, but none from the past. EM Group Messaging Feature 40

41 CF User rejoins an active group after exiting or declining EM Group Messaging Feature 41

42 Use Case Receiving a List of Active Group Members EM Group Messaging Feature 42

43 UC Receiving a List of Active Group Members; Scenario Scenario Primary User Precondition Message Content UserD1 has started a group conversation which has been on-going for a period of time when UserG2 decides to obtain a list of the current, active members of the group. UserD1, D2, G1, G2 User D1, D2, G1 and G2 are subscribers with Mobile Carriers D and G respectively. Each are enhanced messaging customers. The group conversation must be active. UserD1 has already started a group conversation and UserG2 has accepted the group invitation. <Get Active Members Query>: exact command code not determined technically across carrier. <Member List>: Format is yet to be finalized across carrier. Minimal across carrier support will be phone number and Display Name (See 04-10); or phone number only in the case of no available Display Name. EM Group Messaging Feature 43

44 UC Receiving a List of Active Group Members; Action Steps Action Step Mobile Carrier G supports the intercarrier command <Get Active Members Query>. UserG2 exercises that command from his device. Response Mobile Carrier G passes the command <Get Active Members Query> to the IWP/A who must forward the message to the group messaging function at Mobile Carrier D. The Group Messaging system at Mobile Carrier D sends a system <Member List> message of the current, active members of the group conversation to UserG2. UserG2 receives the entire active member list on their device. The format of its display is dependent on Mobile Carrier G requirements and is not an intercarrier issue. EM Group Messaging Feature 44

45 CF Receiving a List of Active Group Members User D1 User D2 EM Server D (Host) IWP/A EM Server G User G1 User G2 UserG2 Requests List of Active Group Members G2 requests list of active members G2 Server forwards request Host Server receives request for list of active members Host Server Generates List of Active Members and sends to UserG2 Host server sends list of active members Mobile Carrier G receives list of active members UserG2 receives entire list of active members Note: "<Get Active Members Query>" is always sent to the host EM Server since it maintains the list of active participants regardless of each participants carrier (i.e., the non-host EM servers do not know who is involved in the group). The host EM server then sends the list to the user who requested it. Therefore, the user who requested it should receive the list as one message. EM Group Messaging Feature 45

46 Use Case Support of Display Name EM Group Messaging Feature 46

47 UC Support of Display Name; Scenario Scenario Primary User Precondition Alternate Scenarios Or Extensions Scope MessageContent Note UserD1 has been invited to a group conversation. A Display Name is communicated during the active session, and will show when <Member List> is requested. UserD1, D2, G1, G2 User D1, D2, G1 and G2 are subscribers with Mobile Carriers D and G respectively. Each is enhanced messaging customers. Per UC-04-01, UserG2 has either manually opted in, or has been automatically opted-in to a group messaging session. Carrier D also uses Display name in admin messages to group members. In order to comply with intercarrier messaging requirements the display name shall only consist of ASCII characters and be limited to 12 characters. <Member List>: Format is yet to be finalized across carrier. The supported format of the <Member List> message will include at least Display Name, and Group Name. MSISDN/MDN would be displayed if no Display name is provided. The use of Display names will conform to OMA SIMPLE IM. The main OMA specification page This Use Case description is retained, the Team notes there is no associated Call Flow since the solution will be according to standards. The solution may encompass Presence Attributes and are outside the scope of the application server. Solutions will be decided on a carrier by carrier basis. EM Group Messaging Feature 47

48 UC Support of Display Name; Action Steps Action Step Mobile Carrier G could provide many different ways to capture a display name for its enhanced messaging customers. Mobile Carrier G can manage these name assignments however they choose. The Group Messaging system at Mobile Carrier D upon <Get Active Member Query> command sends a list of the current, active members of the group conversation to any user who requests the list via UC The supported format of the <Member List> message will include at least Display Name, and Group Name. MSISDN/MDN would be displayed if no Display name is provided. Response Mobile Carrier G passes the Display Name in finalized format within the opt-in message identified in UC to the IWP/A who must forward the message to the group messaging function at Mobile Carrier D. UserG2 receives the entire active member list on their device. EM Group Messaging Feature 48

49 Use Case Group Initiator Ends a Group Conversation EM Group Messaging Feature 49

50 UC 05-01A Group Initiator Ends a Group Conversation; Scenario Primary User Precondition Alternate Scenario #1 Message Content UserD1, D2, G1, G2 UserD1 has set up a Group Conversation among UserD2 and UserG1 and UserG2 (UC-04-01). Each participant in the group has accepted the invitation to join the group. Group conversation could also end if: 05-01B : all active members of the group exit the group or C: if no UserGen messaging traffic is passed among the group members for a period of 72 hours. <Group Ended>: The <groupxyz> is now closed by the initiator. <Group Closed>: Your message to <GroupXYZ> cannot be sent because it was closed by the initiator. EM Group Messaging Feature 50

51 UC 05-01A Group Initiator Ends a Group Conversation Carrier G 3 Conversation ends Carrier D G2 3 Conversation ends D2 D1 EM Server HOST EM Server 2 Conversation ends 2 Conversation ends G1 1 End Conversation Carrier U X2 EM Server X1 EM Group Messaging Feature 51

52 UC 05-01A Group Initiator Ends a Group Conversation; Action Steps Action Step UserD1 decides to end the group conversation with UserD2, G1 and G2. Response The group messaging system at Mobile Carrier D is responsible for sending out a signaling message to active group participants that the group session has ended. The IWP/A will route a system <group ended> messages to Mobile Carrier G for delivery to G1 and G2. UserG1 replies to a group conversation that ended The IWP/A routes the group message from Mobile Carrier G to Mobile Carrier D s group messaging system. Mobile Carrier D s group messaging system must recognize that the group session has ended and return a system <Group Closed> message to Mobile Carrier G through the IWP/A. EM Group Messaging Feature 52

53 CF 05-01A Group Initiator Ends a Group Conversation EM Group Messaging Feature 53

54 CF 05-01B All Participants Leave the Conversation IWP/A D1 D2 EM Server D EM Server G G1 G2 D1 has started the group conversation with D2, G1 and G2 Leave conversation OK D2 G1 Left conversation Leave conversation G1 Left conversation OK G1 OK G1 OK G1 Leave conversation G2 Left conversation G2 Left conversation OK G2 OK G2 Group Conversation ends G2 OK Group conversation ends (all left) D1 OK EM Group Messaging Feature 54

55 CF 05-01C No Activities for 72 Hours IWP/A D1 D2 EM Server D EM Server G G1 G2 D1 has started the group conversation with D2, G1 and G2 No Activities for 72 hours Group Conversation ends Group conversation ends (G1) Group conversation ends D2 OK Group conversation ends (G1) G1 OK Group conversation ends G1 OK G1 OK Group conversation ends (G2) Group conversation ends (G2) Group conversation ends G2 OK G2 OK G2 OK Group conversation ends (no activities) D1 OK EM Group Messaging Feature 55

56 CF G1 Sends Message after End of Group Conversation EM Group Messaging Feature 56

57 Use Case Group Creator Blocks a Specific Group Member EM Group Messaging Feature 57

58 UC A Group Initiator Blocks a Specific Group Member; Scenario Primary User Precondition Scope Message Content UserD1, D2, G1, G2 UserD1 has set up a Group Conversation among UserD2 and UserG1 and UserG2 (UC-04-01). Each participant in the group has accepted the invitation to join the group. Block message could be configurable on a carrier by carrier choice. <remove UserG2 command>: format TBD <Block Rude UserG2> DisplayName has been removed from the conversation at request of the initiator. <Block Polite UserG2> GroupXYZ is closed <Block Rude Members> UserG2 has been removed from GroupXYZ <Block Polite Members> UserG2 has left GroupXYZ EM Group Messaging Feature 58

59 UC A Group Initiator Blocks a Specific Group Member; Action Steps Action Step UserD1 decides to end the group conversation with one member, UserG2. In other words, UserG2 is removed from the conversation by the initiators request <Remove UserG2> command. Response The group messaging system at Mobile Carrier D is responsible for managing the group conversation and will remove UserG2 from the active group, upon receiving the command message <remove UserG2 command>. The group messaging system will also send two messages as follows: 1) UserG2 will be sent a blocked signaling message 2) All other remaining members of the group shall be sent a system message (UC-04-02) indicating that UserG2 has left the conversation. EM Group Messaging Feature 59

60 CF Group Creator Blocks a Specific Group Member EM Group Messaging Feature 60

61 Legacy Section UC 06-01: Legacy- EM carrier, non-em device UC 06-02: Legacy- Non-EM carrier EM Group Messaging Feature 61

62 UC Legacy- EM Carrier, non-em Device; Scenario Primary User Precondition Alternate Scenario #1 Scope Message Content UserD1, D2, G1, G2, G3 UserD1 has set up a Group Conversation among UserD2 and UserG1 and UserG2 (UC-04-01). In this use case, UserD1 has included UserG3 who is not an enhanced messaging subscriber. UserG3 could also decline the group messaging request (if Mobile Carrier G offers its subscribers that option). UserG3 should also be able to reply to any of the group messages to exit the group conversation. Mobile Carrier D should allow a reply of STOP to any message and remove UserG3 from the group conversation (US-04-02). Note the determination of multiple messages or truncating has not been finalized, see RFI Section 6, Questions <Invitation>: "You have been invited by User D1 to join Group XYZ. Would you like to join the Group?" EM Group Messaging Feature 62

63 Action Step UC Legacy- EM Carrier, non-em Device; Action Steps Response UserD1 is the initiator of the group conversation; D1 creates and sends a message to UserD2, UserG1, UserG2 and UserG3. As per 04-01A,B, Mobile Carrier G could implement where all of its subscribers are automatically opted-in to a group session. Or could require each subscriber to approve their participation in the group. The intercarrier UC requires that a positive response be sent back to Mobile Carrier D. For this case assumed positive. The group messaging system at Mobile Carrier D sends out system <acceptance> messages, as per Mobile Carrier D sends the UserGen message created by UserD1 to each recipient as it receives opt-in responses from each destination. (04-01) Mobile Carrier D is responsible for creating and managing the group messaging session. Mobile Carrier D must send system <invitation> messages to UserG1 and UserG2 and UserG3 to join the group conversation. (04-01) This is done through the IWP/A. Since UserD2 is a Mobile Carrier D subscriber, that carrier has responsibility for how UserD2 will be added to the conversation. This is not an intercarrier issue. Mobile Carrier G sends a system <acceptance> for UserG1 and UserG2 and UserG3 through the IWP/A back to the group messaging system at Mobile Carrier D. The IWP/A passes the <acceptance> messages to Mobile Carrier G for UserG1, UserG2 and UserG3. Mobile Carrier G is responsible for routing all messages to UserG3 through legacy systems (SMS & MMS). Whether carriers choose the above method or another method, below the IWP/A layer, is not an intercarrier issue. The IWP/A passes the group messages to Mobile Carrier G for UserG1, UserG2 and UserG3. Mobile Carrier G is responsible for routing all messages to UserG3 through legacy systems (SMS & MMS) Whether carriers choose the above method or another method, below the IWP/A layer, is not an intercarrier issue. UserG3 should be able to reply to the messages and such replies should be passed back to Mobile Carrier D for distribution to all other members of the group. The interface back to Mobile Carrier EM D Group in this Messaging case must Feature always be through the EM systems. 63

64 UC Legacy- EM Carrier, non-em device EM Group Messaging Feature 64

65 UC Legacy non-em Carrier; Scenario Primary User UserD1, D2, G1, G2, Other Users Precondition Alternate Scenario #1 Scope Message Content CustomerZ UserD1 has set up a Group Conversation among UserD2 and UserG1 and UserG2 (UC-04-01). In this use case, UserD1 has included CustomerZ who is not an enhanced messaging subscriber and whose carrier does NOT support enhanced messaging. This use case concentrates on the interaction with CustomerZ, all steps related to UserG1 and UserG2 and Mobile Carrier G are unchanged from UC CustomerZ could also decline the group messaging request. CustomerZ should also be able to reply to any of the group messages to exit the group conversation. Mobile Carrier D should allow a reply of STOP to any message and remove CustomerZ from the group conversation (UC-04-02). UserD1 could send messages including Multimedia content. Ad Hoc groups will have a different user experience than Permanent groups, note RFI Section 6, General Questions. *1 Note the determination of multiple messages or truncating has not been finalized, see RFI Section 6, Questions <Invitation>: "You have been invited by User D1 to join Group XYZ. Would you like to join the Group?" EM Group Messaging Feature 65

66 Action Step UC Legacy non-em Carrier; Action Steps UserD1 is the initiator of the group conversation; D1 creates and sends a message to UserD2, UserG1, UserG2 and CustomerZ. Response CustomerZ must approve their participation in the group. This requires that a positive response be sent back to Mobile Carrier D for the group session. For this case assumed positive. Mobile Carrier D sends the UserGen message created by UserD1 to each enhanced messaging recipient (per UC-04-01) as it receives opt-in responses from each destination. Mobile Carrier D is responsible for creating and managing the group messaging session. Mobile Carrier D must send a system <Invitation> message to CustomerZ. This is done through whatever existing messaging interface is in place between Mobile Carrier D and Mobile Carrier Z (assumed legacy SMS/MMS). Positive and negative responses should be possible. Mobile Carrier Z routes the acceptance for CustomerZ through whatever existing messaging interface is in place between Mobile Carrier D and Mobile Carrier Z (assumed legacy SMS/MMS). The group messaging system at Mobile Carrier D is not required to send out messages to CustomerZ as it receives the acceptance messages from other group participants. Nor should CustomerZ receive individual messages as group members exit the group. CustomerZ receives the message from UserD1. Within the body of the message, Mobile Carrier D has included up to 60 characters of information to inform CustomerZ of other participants within the group. Message bodies longer than 100 characters are truncated. Group participant info in the message could be mobile number, address, or Display Name. Participant info is truncated after 60 characters. *1 CustomerZ should be able to reply to the messages and such replies should be passed back to Mobile Carrier D for distribution to all other members of the group. Reply messages pass through whatever existing messaging interface is in place between Mobile Carrier D and Mobile Carrier Z (assumed legacy SMS/MMS). EM Group Messaging Feature 66

67 CF Legacy Non-EM carrier D1 D2 EM Server D IWG D Legacy Messaging D Legacy Messaging Z Z1 Start group conversation D2 (DN) G1 (DN) G2 (DN) Z1 (DN) Start conversation () Invitations to G1/G2 Invite Accept Invite Message (Invite) Message (Invite) Message (Invite) Message (Accept) Message (Accept) Message (Accept) Accept Group Conversation starts When anyone accepts EM Group Messaging Feature 67