Method for informing a user about scheduling information, messaging device, user equipment and a computer program product

• US 20020032595A1
• Filed: 09/05/2001
• Published: 03/14/2002
• Est. Priority Date: 09/08/2000
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Hundscheidt, Frank, Hameleers, Heino
• Application Number:
  US09/947,249
• Publication Number:
  US 20020032595A1
• Time in Patent Office: Days
• US Class Current: 705/8
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The invention relates to a messaging device, capable of sending information.

According to the invention the messaging device contains at least one scheduling server (SCS) which is capable of generating scheduling information.

The invention further relates to a method for informing a user about an expected waiting time, a user equipment and to a computer program and a computer program product for handling scheduling information.

Claims

1. A method for informing a user about scheduling information, characterised by the following steps:

a user equipment sends a request to a scheduling server,

the scheduling server receives the request,

the scheduling server generates scheduling information,

the scheduling information is sent to the user equipment.

2. The method according to claim 1, characterised in that a message which contains the scheduling information is sent to the user equipment.

3. The method according to any of the claims 1 or 2, characterised in that the messaging device sends the information in a format which is readable by a WAP enabled device.

4. The method according to any of the claims 1 to 3, characterised in that the scheduling information is updated automatically.

5. The method according to claim 4, characterised in that the information is updated if a user checks in or out.

6. The method according to any of the claims 1 to 5, characterised in that the scheduling information is available real-time.

7. The method according to any of the claims 1 to 6, characterised in that the generation of the scheduling information and/or a notification of the user about the scheduling information depends on location data of the user.

8. The method according to any of the claims 1 to 7, characterised in that a software agent initiates a transfer of information from and/or to the user equipment.

9. The method according to claim 8, characterised in that the software agent checks the scheduling information and decides whether a user which has authorized the agent should check in.

10. The method according to any of the claims 1 to 9, characterised in that the user equipment sends a registration message (RM) to register in the scheduling server (SCS).

11. The method according to any of the claims 1 to 10, characterised in that the scheduling server (SCS) sends a registration actualisation message (RAM) to the data base.

12. The method according to any of the claims 1 to 11, characterised in that the scheduling server (SCS) sends a waiting time information message (WTIM).

13. The method according to any of the claims 1 to 12, characterised in that the user equipment sends a registration confirmation message (RCM).

15. The messaging device according to claim 14, characterised in that the scheduling server contains a data base with expected waiting times for different users.

14. Messaging device, characterised in that it contains at least one scheduling server which is capable of receiving a request from a user equipment, that the scheduling server generates scheduling information and that the messaging device is capable of sending the scheduling information to the user equipment.

16. The messaging device according to any of the claims 14 or 15, characterised in that it contains an interface for an information exchange with a data base which contains expected waiting times of users.

17. The messaging device according to any of the claims 14 or 16, characterised in that it sends the information in a format which is readable by WAP enabled device.

18. The messaging device according to any of the claims 14 to 17, characterised in that the scheduling server is connected to an interface for receiving check-in messages of users.

19. The messaging device according to any of the claims 14 to 18, characterised in that it contains a software agent.

20. The messaging device according to any of the claims 14 to 19, characterised in that it contains a serving company interface.

21. User equipment, capable of communicating in a multiple access communication system, characterised in that it contains means for receiving and treating scheduling information and that it is capable of notifying a user about the scheduling information.

22. The user equipment according to claim 21, characterised in that it contains a logical element which automatically informs a user about waiting status.

23. The user equipment according to any of the claims 21 or 22, characterised in that it displays a remaining waiting time and/or a probability indicator which shows a probability for the user of being served within a certain time.

24. The user equipment according to any of the claims 21 to 23, characterised in that the user equipment displays a number of persons with a better waiting status than the user of the user equipment and/or a current average waiting time.

25. The user equipment according to any of the claims 21 to 24, characterised in that it contains a software agent.

26. The user equipment according to any of the claims 21 to 25, characterised in that it contains a client interface.

27. The user equipment according to any of the claims 21 to 26, characterised in that it is WAP enabled.

28. The user equipment according to any of the claims 21 to 27, characterised in that the user equipment is capable of communicating in a communication system which is designed as Universal Mobile Telecommunication System.

29. The user equipment according to any of the claims 21 to 28, characterised in that it contains means for allowing a deregistration of a user from a waiting queue.

30. Computer program product, characterised in that it generates and/or modifies scheduling information in dependency of at least one request of a user equipment.

31. The computer program product according to claim 30, characterised in that the computer program generates the scheduling information by using data stored in a data bank.

32. The computer program product according to any of the claims 30 or 31, characterised in that it is capable of fetching a queue number for an attending user.

33. The computer program product according to any of the claims 30 to 32, characterised in that it uses historical information to calculate expected waiting times.

34. The computer program product according to any of the claims 30 to 33, characterised in that it applies at least one queuing series to calculate expected waiting times.

35. The computer program product according to any of the claims 30 to 34, characterised in that it is capable of acting as a software agent.

36. The computer program product according to any of the claims 30 to 35, characterised in that it is loadable in a messaging device.