METHOD AND SYSTEM FOR PERMITTING OR DENYING SERVICE

• US 20090158403A1
• Filed: 12/14/2007
• Published: 06/18/2009
• Est. Priority Date: 12/14/2007
• Status: Abandoned Application

• Current Assignee: DLB Finance & Consultancy BV, HITD Information Technology BV
• Original Assignee: DLB Finance & Consultancy BV, HITD Information Technology BV
• Inventors: Benchop, Henderik Reinout, Benschop, Dirk Leonard
• Application Number:
  US11/956,572
• Publication Number:
  US 20090158403A1
• Time in Patent Office: Days
• US Class Current: 726/5
• CPC Class Codes: G06F 21/606 by securing the transmission between two devices or processes
• CPC Class Codes: G06F 21/629 to features or functions of an application
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: H04L 63/102 Entity profiles

Abstract

Aspects of the invention relate to a computer-implemented method and system of permitting or denying service for a user device of a user of a service in relation to a recipient, who is the counterparty, is proposed. The method is executed in a system configured for connecting to the user device. The system is configured for accessing a recipient requirement list of the recipient and a user profile of the user. The recipient requirement list comprises at least one criterion regarding an item of said user profile. A service request is received from the user device. The service request contains an identifier of the recipient. The recipient requirement list is traced on the basis of this identifier. Subsequently, it is checked whether an item of the user profile satisfies the at least one criterion of the traced recipient requirement list. Service is permitted if the item of the user profile satisfies said at least one criterion of said recipient requirement list. Service initiation or service establishment is denied if said item of said user profile does not satisfy said at least one criterion of said recipient requirement list.

Claims

1. A computer-implemented method of permitting or denying service for a user device of a user in relation to a recipient in a server system configured for connecting with said user device, wherein the server system has access to a recipient requirement list of said recipient and a user profile of said user and wherein said recipient requirement list comprises at least one criterion regarding an item of said user profile, the method comprising the steps of:

receiving a service request from said user device, said service request comprising a contact identifier of said recipient;

tracing said recipient requirement list on the basis of said contact identifier;

checking whether said item of said user profile satisfies said at least one criterion of said traced recipient requirement list; and

permitting said service if said item of said user profile satisfies said at least one criterion of said recipient requirement list and denying said service if said item of said user profile does not satisfy said at least one criterion of said recipient requirement list.

2. The method according to claim 1, wherein said server system has access to a user requirement list of said user and a recipient profile of said recipient and wherein said user requirement list comprises at least one criterion relating to an item of said recipient profile, the method further comprising the steps of:

tracing said user requirement list;

checking whether said item of said recipient profile satisfies said at least one criterion of said traced user requirement list;

permitting said service only if said item of said recipient profile also satisfies said at least one criterion of said user requirement list.

3. The method according to claim 2, further comprising the step of tracing said user requirement list on the basis of at least one of login data received from said user device and from a contact identifier received from a device of said recipient.

4. The method according to claim 1, wherein said server system is configured for permitting or denying service for at least a first service and a second service, the method comprising the step denying said service initiation of said first service and said second service if said item of said user profile does not satisfy said at least one criterion of said recipient requirement list.

5. The method according to claim 4, wherein said server system has access to a user requirement list of said user and a recipient profile of said recipient and wherein said user requirement list comprises at least one criterion relating to an item of said recipient profile, the method further comprising the steps of:

tracing said user requirement list;

checking whether said item of said recipient profile satisfies said at least one criterion of said traced user requirement list;

permitting service of said first service and said second service only if said item of said recipient profile also satisfies said at least one criterion of said user requirement list.

6. The method according to claim 4, further comprising the step of receiving a service selection in at least one of said user requirement list and said recipient requirement list.

7. The method according to claim 1, wherein said criterion is independent of said contact identifier of said recipient.

8. The method according to claim 1, wherein said at least one item comprises a system item and/or a user defined item.

9. The method according to claim 8, wherein said system item is a spam related item.

10. The method according to claim 1, wherein said items of said profile(s) comprise verified items and unverified items.

11. The method according to claim 10, wherein said server system receives from at least one of a device of said user and a device of said recipient a verification indication that said at least one criterion of said requirement list relates to a verified item or an unverified item of said profile.

12. The method according to claim 1, wherein one or more of said items are prevented from checking and wherein, optionally, said server system receives from at least one of a device of said user and a device of said recipient a checking prevention indication indicating that one or more items of said profile are prevented from checking.

13. The method according to claim 12 comprising the step of transmitting a notification request to a device of the user or recipient for whom a checking prevention indication applies, said notification request presenting an option to ignore said checking prevention indication to permit checking of said at least one item against a corresponding criterion of a requirement list.

14. The method according to claim 1, wherein said server system is configured for initiating at least a first service and a second service and said contact identifier comprises a public unique identifier suitable for use in both said first service and said second service.

15. The method according to claim 14, wherein said server system is configured for a first service and a second service in relation to said same recipient, the method comprising the steps of:

receiving said public unique identifier of said recipient;

receiving a message indicating a request for said first service and initiating said first service relating to said recipient on the basis of said public unique identifier;

receiving a message indicating a request for said second service and initiating said second service relating to said recipient on the basis of said public unique identifier.

16. The method according to claim 1, wherein said service(s) include two or more of the following services:

a payment service, a telephony service, an electronic messaging service, a streaming media service, a web browsing service, a regular mail service and a navigation service.

17. The method according to claim 15, further comprising the steps of:

converting said public unique identifier to at least one of a payment address identifier and a communication address identifier;

connecting to a payment system for initiating said payment service using said payment address identifier;

connecting to a communication system for initiating said communication service using said communication address identifier.

18. The method according to claim 15, wherein said server system provides at least one of said first service and said second service, said method comprising the steps of:

determining whether said recipient uses said at least one of said first service and said second service at said server system;

initiating said at least one of said first service and second service using said public unique identifier as at least one of a first service address identifier and a second service address identifier.

19. The method according to claim 1, further comprising the step of receiving a login request from a payment device or communication device, said login request comprising at least one personal identifier.

20. The method according to claim 19, wherein at least said login request is transmitted over a network to said server system in a secure manner.

21. A computer program comprising software code portions adapted for, when installed on and executed by an electronic system, performing the method according to claim 1.

22. A carrier containing the computer program of claim 21.

23. A server system configured for permitting or denying service, said server system being configured for connecting with a user device of a user in relation to a recipient, wherein the server system comprises:

a receiver configured for receiving a service request from said user device, said service request comprising a contact identifier of said recipient;

a tracer configured for tracing a recipient requirement list of said recipient on the basis of said contact identifier, said recipient requirement list comprising at least one criterion regarding an item of a user profile;

an analyzer configured for analyzing whether said item of said user profile satisfies said at least one criterion of said traced recipient requirement list; and

a service initiator configured for permitting said service if said item of said user profile satisfies said at least one criterion of said recipient requirement list and denying said service if said item of said user profile does not satisfy said at least one criterion of said recipient requirement list.

24. The server system according to claim 23, wherein:

said tracer is further configured for tracing a user requirement list of said user and a recipient profile of said recipient, said user requirement list comprising at least one criterion relating to an item of said recipient profile;

said analyzer is further configured for analyzing whether said item of said recipient profile satisfies said at least one criterion of said traced user requirement list;

said service initiator is configured for permitting said service only if said item of said recipient profile also satisfies said at least one criterion of said user requirement list.

25. The server system according to claim 24, wherein said system comprises a login module for receiving login data and said tracer is configured for tracing said user requirement list on the basis of said login data or on the basis of a user identifier received from a device of said recipient.

26. The server system according to claim 23, wherein said server system is configured for permitting or denying service for at least a first service and a second service and said service initiator is configured for denying said service initiation of said first service and said second service if said item of said user profile does not satisfy said at least one criterion of said recipient requirement list.

27. The server system according to claim 26, wherein said server system has access to a user requirement list of said user and a recipient profile of said recipient and wherein said user requirement list comprises at least one criterion relating to an item of said recipient profile, wherein said service initiator is configured for permitting service of said first service and said second service only if said item of said recipient profile also satisfies said at least one criterion of said user requirement list.

28. The server system according to claim 26, wherein said server system further comprises a service selector configured for containing a service selection in at least one of said user requirement list and said recipient requirement list.

29. The server system according to claim 23, wherein said criterion is independent of said contact identifier of said recipient.

30. The server system according to claim 23, wherein said at least one item comprises a system item and/or a user defined item.

31. The server system according to claim 30, wherein said system item is a spam related item.

32. The server system according to claim 23, wherein said items of said profiles comprise verified items and unverified items.

33. The server system according to claim 32, further comprising a verification indication receiver configured for receiving and processing a verification indication from at least one of a device of said user and a device of said recipient, said verification indication indicating that said at least one criterion of said requirement list relates to a verified item of said profile.

34. The server system according to claim 23, wherein one or more of said items are prevented from checking, the system optionally comprising a checking prevention indication receiver configured for receiving and processing a checking prevention indication from at least one of a device of said user and a device of said recipient, said checking prevention indication indicating that one or more items of said profile are prevented from checking by said analyser.

35. The server system according to claim 23, wherein said system further comprises a notification transmitter configured for transmitting a notification request to a device of the user or recipient for whom a checking prevention indication applies, said notification request presenting an option to ignore said checking prevention indication to permit checking of said at least one item against a corresponding criterion of a requirement list.

36. The server system according to claim 23, wherein the system is configured for providing a first service and a second service with said same recipient, wherein said receiver is a public unique identifier receiver configured for receiving a public unique identifier of said recipient suitable for use in both said first service and said second service.

37. The server system according to claim 36, wherein said server system further comprises:

a first service initiator configured for receiving a message indicating a request for said first service and initiating said first service relating to said recipient on the basis of said public unique identifier;

a second service initiator configured for receiving a message indicating a request for said second service and initiating said second service relating to said recipient on the basis of said public unique identifier;

38. The server system according to claim 23, wherein said service(s) include at least one of a payment service, a telephony service, an electronic messaging service, a streaming media service, a web browsing service, a regular mail service and a navigation service.

39. The server system according to claim 23, wherein said server system further comprises:

a converter configured for converting said public unique identifier to at least one of a first service address identifier and a second service address identifier;

a first service connection module for connecting to a first service system for initiating said first service using said first service address identifier;

a second service connection module for connecting to a second service system for initiating said second service using said second service address identifier.

40. The server system according to claim 23, further comprising:

a first service module configured for executing a first service in relation to said recipient;

a second service module configured for executing a second service in relation to said recipient;

a determination module configured for determining whether said recipient uses said at least one said first service and said second service;

and wherein at least one of said first service module is configured for initiating said first service using said public unique identifier as a first service address identifier and said second service module is configured for initiating said second service using said public unique identifier as a second service address identifier.

41. The system according to claim 23, further comprising a login module configured for receiving a login request from a payment device or a communication device, said login request comprising at least one personal identifier.

42. The system according to claim 41, wherein said login module is configured for receiving said login request in a secure manner.