Communication infrastructure arrangement for multiuser

• US 20040030787A1
• Filed: 04/28/2003
• Published: 02/12/2004
• Est. Priority Date: 10/27/2000
• Status: Abandoned Application

• Current Assignee: Terraplay Systems AB (Syniverse Corp.)
• Original Assignee: Terraplay Systems AB (Syniverse Corp.)
• Inventors: Jandel, Magnus, Stenhoff, Martin, Karlsson, Roland
• Application Number:
  US10/415,271
• Publication Number:
  US 20040030787A1
• Time in Patent Office: Days
• US Class Current: 709/229
• CPC Class Codes: H04L 12/1813 for computer conferences, e.g. chat rooms instant messaging H04L51/04; protocols for multimedia communication H04L65/1101; arrangements for multi-party communication H04L65/403; telephonic conference arrangements H04M3/56; television conference systems H04N7/15
• CPC Class Codes: H04L 12/185 with management of multicast group membership
• CPC Class Codes: H04L 67/131 Protocols for games, networked simulations or virtual reality
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

This invention relates to a communication infrastructure arrangement in and a computer readable program product for a data processing system for multi-user applications, i.e. applications for multiple clients, enabling simultaneous communication across an application communication network (1) between several clients joined in at least one client group (CG). At least one distributed multi-user application is provided on the application communication network (1). Each multi-user application has nodes (AC, ASNS, ACG, AR, AS, APDB, ALS, ANMS, CAS, CGH) and databases (11, DB1, APDB) for handling each client group (CG). A set of attributes (7, 8, CGDB) for each client group (CG) determines the function and usage of the client group. At least one session (13) is provided, in which the attributes are listed. The selection of attributes is made to fit the intended function of the client group (CG) and the capabilities of the application communication network (1).

Claims

1. A communication infrastructure arrangement in a data processing system for multi-user applications, i.e. applications for multiple clients, enabling simultaneous communication across an application communication network (1) between several clients joined in at least one client group (CG), said infrastructure arrangement comprising:

a) at least one distributed multi-user application on the application communication network (1), each multi-user application having nodes (AC, ASNS, ACG, AR, AS, APDB, ALS, ANMS, CAS, CGH) and databases (11, DB1, APDB) for handling each client group (CG);

b) a set of attributes (7, 8, CGDB) for each client group (CG) determining the function and usage of the client group, at least one of said attributes being selected among the following;

Receiver, Source, Membership protection mode, Event distribution mode, Name and Alias, Distribution mode, Termination conditions, Client profile, Parents, Ancestors, Children, Descendants;

c) at least one session (13), in which the attributes are listed;

d) the selection of attributes being made to fit the intended function of the client group (CG) and the capabilities of the application communication network (1), said infrastructure arrangement being characterized in that it further comprises;

e) a receiver client group for distributing identical data to all members of the client group, the receiver client group having an associated network address (e.g. an IP multicast) or an application address; and

an application server (AS) for distributing the application data to application clients and client groups (CG) according to queries, requests or subscriptions, such queries, requests or subscriptions may be expressed in terms of subscriptions to application data units (9) carrying application tags.

2. A communication infrastructure arrangement according to claim 1, characterized in that each attribute is set independently of the other attributes.

3. A communication infrastructure arrangement according to claim 1 or 2, characterized in that the client group address is either a network addressor an application address, and a sender knowing the client group address transmits data to all members of the group.

4. A communication infrastructure arrangement according to any one of the preceding claims, characterized by a source client group being the owner or the source of application data units, the source client group acting as a sender of the data unit.

5. A communication infrastructure arrangement according to claim 4, characterized by a pseudo client being a source client group having at least one active member using the client group as an alias, e.g. for providing a persistent service to the session.

6. A communication infrastructure arrangement according to any one of the preceding claims, characterized in that some clients are authorized clients and have particular rights, the authorized client group being called the master group, unauthorized clients have prescribed limitations regarding operations to perform.

7. A communication infrastructure arrangement according to claim 6, characterized by a security system where only authorized clients are accepted as members to protect the right to become a member and/or to leave of a client group.

8. A communication infrastructure arrangement according to claim 6 or 7, characterized in the authorized clients are the owners of the client group or any member of the client group.

9. A communication infrastructure arrangement according to any one of the claims 6 to 8, characterized in that the security systems have at least two membership protection modes, of which one is secure to be closed for non-authorized clients and open only for authorized clients and the other is free for all clients to join and leave, as they like.

10. A communication infrastructure arrangement according to any one of the preceding claims, characterized by a client group handler (CGH) providing information to the members of the client group (CG) about group events, such as clients joining, clients leaving, data units created and deleted, data subscriptions etc.

11. A communication infrastructure arrangement according to claim 10, characterized in that the client group handler (CGH) has at least two distribution modes, of which there are at least one called Verbose, where the members get their information, and another is Silent, where at least some members in the client group could get no such information.

12. A communication infrastructure arrangement according to claim 11, characterized in that there are several verbose modes, in which the members can be provided with different amounts and/or kinds of information, prescribed in the individual verbose modes.

13. A communication infrastructure arrangement according to anyone of the claims 10 to 12, characterized in that the client group handler (CGH) stores a name or alternative names of the client group, such that a network address or an application address could identify a client group in order to support operations on client groups.

14. A communication infrastructure arrangement according to any one of the preceding claims, characterized by application tags serving as client group identifier means for identifying the client group.

15. A communication infrastructure arrangement according to any one of the preceding claims, characterized by an application server (AS) distributing application data to application clients and client groups (CG) according to queries, requests or subscriptions.

16. A communication infrastructure arrangement according to claim 14 or 15, characterized in that the queries, requests or subscriptions are expressed in terms of subscriptions to application data units (9) carrying application tags.

17. A communication infrastructure arrangement according to any one of the claims 10 to 16, characterized in that the client group handler (CGH) comprises a database (DB1) containing data about client groups, the data including for each client group the list of members, and, a list of the attributes of the client group.

18. A communication infrastructure arrangement according to claim 17, characterized in that the database (DB 1) also comprises a list of invited members, and a list of client group owners.

19. A communication infrastructure arrangement according to any one of the preceding claims, chracterized in that a network address or an application address identifies a client group, a client group has also a name that is known by the application and stored in an application session name server (ASNS) or in the client group handler (CGH).

20. A communication infrastructure arrangement according to any one of the preceding claims, characterized in that at least one of the client groups also has one or several alternative names called aliases.

21. A computer readable program product comprising a computer useable medium having computer readable code embodied therein for causing a computer to store an unpredictable amount of time-valued or log data in a file system of a computer operating system executing an application program, said computer readable code comprising:

computer readable program and code devices configured to cause a device with computational capacity to install a software environment and user interface for management of software components for providing communication infrastructure in a data processing system for multi-user applications, i.e. applications for 1 multiple clients, enabling simultaneous communication across an application communication network (1) between several clients joined in at least one client group (CG), comprising

a) computer readable programs and code devices configured to cause at least one distributed multi-user application on the application communication network (1), each multi-user application having nodes (AC, ASNS, ACG, AR, AS, APDB, ALS, ANMS, CAS, CGH) and databases (11, DB1, APDB) for handling each client group (CG);

b) computer readable programs and code devices configured to cause a set of attributes (7, 8, CGDB) for each client group (CG) determining the function and usage of the client group, at least one of the attributes being selected among the following;

Receiver, Source, Membership protection mode, Event distribution mode, Name and Alias, Distribution mode, Termination conditions, Client profile, Parents, Ancestors, Children, Descendants;

c) computer readable programs and code devices configured to cause at least one session (13), in which the attributes are listed;

d) the selection of attributes being made to fit the intended function of the client group (CG) and the capabilities of the application communication network (1), said computer program product being characterized by;

e) computer readable programs and code devices configured to cause a receiver client group for distributing identical data to all members of the client group, the receiver client group having an associated network address (e.g. an IP multicast) or an application address; and

f) computer readable programs and code devices configured to cause an application server (AS) for distributing the application data to application clients and client groups (CG) according to queries, requests or subscriptions, such queries, requests or subscriptions may be expressed in terms of subscriptions to application data units (9) carrying application tags.

22. A computer readable program product according to claim 21, characterized in that each attribute is set independently of the other attributes.

23. A computer readable program product according to claim 22, characterized in that the client group address is either a network address or an application address, and a sender knowing the client group address transmits data to all members of the group.

24. A computer readable program product according to any one of the claims 21 to 23, characterized by computer readable programs and code devices configured to cause a source client group being the owner or the source of application data units, the source client group acting as a sender of the data unit.

25. A computer readable program product according to claim 24, characterized by computer readable programs and code devices configured to cause a pseudo client being a source client group having at least one active member using the client group as an alias, e.g. for providing a persistent service to the session.

26. A computer readable program product according to anyone of the claims 21 to 25, characterized in that some clients are authorized clients and have particular rights, the authorized client group being called the master group, un-authorized clients have prescribed limitations regarding operations to perform.

27. A computer readable program product according to claim 26, characterized by computer readable programs and code devices configured to cause a security system where only authorized clients are accepted as members to protect the right to become a member and/or to leave of a client group.

28. A computer readable program product according to claim 26 or 27, characterized in that the authorized clients are the owners of the client group or any member of the client group.

29. A computer readable program product according to anyone of the claims 26 to 28, characterized in that

the security systems have at least two membership protection modes, of which one is secure to be closed for non-authorized clients and open only for authorized clients and the other is free for all clients to join and leave, as they like.

30. A computer readable program product according to anyone of the claims 21 to 29, characterized by computer readable programs and code devices configured to cause a client group handler (CGH) providing information to the members of the client group (CG) about group events, such as clients joining, clients leaving, data units created and deleted, data subscriptions etc.

31. A computer readable program product according to claim 30, characterized in that the client group handler (CGH) has at least two distribution modes, of which there are at least one called Verbose, where the members get their information, and another is Silent, where at least some members in the client group could get no such information.

32. A computer readable program product according to claim 31, characterized in that there are several verbose modes, in which the members can be provided with different amounts and/or kinds of information, prescribed in the individual verbose modes.

33. A computer readable program product according to anyone of the claims 29 to 32, characterized in that the client group handler (CGH) stores a name or alternative names of the client group, such that a network address or an application address could identify a client group in order to support operations on client groups.

34. A computer readable program product according to anyone of the claims 21 to 33, characterized by computer readable programs and code devices configured to cause application tags serving as client group identifier means for identifying the client group.

35. A computer readable program product according to anyone of the claims 21 to 34, characterized by computer readable programs and code devices configured to cause an application server (AS) distributing application data to application clients and client groups (CG) according to queries, requests or subscriptions.

36. A computer readable program product according to the claims 33 and 35, characterized in that the queries, requests or subscriptions are expressed in terms of subscriptions to application data units (9) carrying application tags.

37. A computer readable program product according to anyone of the claims 30 to 36, characterized in that the client group handler (CGH) comprises a database (DB1) containing data about client groups, the data including for each client group the list of members, and, a list of the attributes of the client group.

38. A computer readable program product according to claim 37, characterized in that the database (DB1) also comprises a list of invited members and a list of client group owners.

39. A computer readable program product according to anyone of the claims 21 to 38, chracterized in that a network address or an application address identifies a client group, a client group has also a name that is known by the application and stored in an application session name server (ASNS) or in the client group handler (CGH).

40. A computer readable program product according to anyone of the claims 21 to 39, characterized in that at least one of the client groups also has one or several alternative names called aliases.