Client in a client-server network and a method of operation

• US 20060230104A1
• Filed: 02/09/2006
• Published: 10/12/2006
• Est. Priority Date: 02/11/2005
• Status: Active Grant

• Current Assignee: 12snap AG (Plan.Net Technology GmbH)
• Original Assignee: 12snap AG (Plan.Net Technology GmbH)
• Inventors: Winter, Moritz
• Granted Patent: US 7,620,681 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• 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/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: Y02D 30/50 in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

A client, in particular in a mobile terminal device, contains a memory unit external to a server. A server configuration is loaded in the client such that an application is self-dependently executable in the client. The client comprises, for example, an input-/output unit, a first module, an internal connection and an external connection to a server. Further, the server comprises a third module and a fourth module wherein the first module in client with the first module in the server an the second module in the client with the second module in the server correspond in terms of addresses or can be assigned elastically, that the mobile application is self-dependently executable in the client.

Claims

1. A client in a client-server network, comprising:

a memory unit being external to a server wherein a predefined server configuration is transferred from the server to the client, and said server configuration is loaded in the client such that an application is self-dependently executable in the client and a simulation of a server function is performed by the client.

2. The client according to claim 1 further comprising:

an input-output unit as user interface for a user;

a first module with a memory unit, on which data is stored;

a second module with a memory unit, on which

a computer program is provided to be self-dependently executable;

an internal connection with an interface, and an external connection with a transmission path to a server, wherein the server comprises a third module with a memory unit, on which data is stored and a fourth module with a memory unit, on which a computer program is provided to be executable, where the first module in the client with the third module in the server, and the second module in the client comprises a correspondence with the fourth module in the server such that the application is self-dependently executable in the client.

3. The client according to claim 1, wherein the application in the client is self-dependently executable by forming a flexible possibility of assignment of the memory units of the participating modules.

4. The client according to claim 2, wherein the possibility of assignment consists such that, on the data side, the first module in the client with the third module in the server, and, on the code side, the second module in the client with the fourth module in the server each comprise an elastical coupling for distribution of the memory units between client and server.

5. The client according to claim 2, wherein the first module in the client forms a correspondence with the third module in the server, by forming a contiguous memory area.

11. The client according to claim 2, wherein the possibility of assignment is such that the first module in the client with the fourth module in the server, and the second module in the client with the third module in the server comprises an elastical cross-coupling for distribution of the memory units between client and server.

12. The client according to claim 2, wherein the modules participating at the cross-coupling are operated as ring-buffer such that the information flow through the modules comprehends a movement of an eight.

13. The client according to claim 1, wherein a profile matrix is stored in the server, which closer denotes the resources being available on the client.

14. The client according to claim 13, wherein the profile matrix determines the degree of the self-dependency with which the application is executable on the client.

15. The client according to claim 13, wherein the profile matrix influences the flexible possibility of assignment of the memory units of the participating modules.

16. The client according to claim 13, wherein the profile matrix determines the elastic coupling of the corresponding modules.

17. The client according to claim 13, wherein the profile matrix determines the cross coupling.

18. The client according to claim 13, wherein parts of the profile matrix can be controlled time variant or event-dependent.

19. The client according to claim 1, wherein the application is executable on a client such kind in order to enable a validadation of user-inputs without the generation of connection costs.

20. The client according to claim 1, wherein a state in which the application is located, is transparently representable and transmittable to the server.

21. The client according to claim 1, wherein the application is executable such kind, in order to provide a contemporary evaluation of user-inputs and an acknowledgement to a user.

22. The client according to claim 1, wherein the application is executable such kind, in order to enable the user to build an interactive user profile with a menu structure where the user can switch of single elements or content.

23. The client according to claim 1, wherein the application is executable such kind, in order to support a dynamical swapping or a dynamical reloading.

24. The client according to claim 1, wherein the application is executable such that it provides a context sensitive dynamical menu structure, where certain menu elements, information or functions arise which are dependent from a context, a state or an event, in which the application is.

25. The client according to claim 1, wherein the application is executable such kind, that it supports a dynamical personalization, where the user-navigation on the client to the server is transmitted and enables to adapt the client on the basis of the navigation.

26. The client according to claim 2, wherein a transmission between the first module and the third module is performed by means of a transmission method, that allows a transmission by means of a channel bundling or several simultaneously occupiable channels of different transmission system.

27. The client according to claim 2, wherein a transmission between the second module and the fourth module is performed by means of a transmission method, that allows a transmission by means of a channel bundling or several simultaneously occupiable channels of different transmission system.

28. The client according to claim 1, wherein the application can build up and down a connection from client to server, which is time controllable.

29. The client according to claim 1, wherein the connection from client to server is event dependent, requirement dependent or semi permanent.

6. The client according to claim 6, wherein the second module in the client forms the correspondence with the fourth module in the server by forming a contiguous memory area.

7. The client according to claim 6, wherein the memory area is tiled.

8. The client according to claim 6, wherein the memory area is overlapping, duplicated or mirrored.

9. The client according to claim 6, wherein the memory area is formed as a buffer.

10. The client according to claim 9, wherein the buffer is operated as a ring-buffer area-wise.

30. A method of operating a client in a client-server network, comprising:

fixing or determining a server configuration in a server;

transmitting of the server configuration to the client; and

executing of the server configuration by the client based on the server configuration loaded on the client such that an application is independently executable in the client and a simulation of a server function is performed by the client.

31. The method according to claim 30, wherein in at least one of the steps a differential or incremental data shifting (delta update) is performed.

32. The method according to claim 30, wherein the server configuration itself is executable on the client.

33. The method according to claim 30 wherein the server configuration is carried out as Push or Pull.

34. The method according to claim 30, wherein the server configuration is carried out as broadcast.

35. The method according to claim 30, wherein the step of the fixation or determination of the server configuration is carried out based on a profile matrix.

36. The method according to claim 35, wherein the profile matrix determines the degree of self-dependency which with the application is executable on the client.

37. The method according to claim 35, wherein the parts of the profile matrix are controlled time variant or event-dependent.

38. The method according to claim 30, wherein the application is executable on the client in order to enable a validation of user-input without a generation of connection costs.

39. The method according to claim 30, wherein the application is executable in order to provide a contemporary evaluation of user-input and an acknowledgement to a user.

40. The method according to claim 30, wherein the application is executable in order to enable the user to build an interactive user profile with a menu structure where the user can switch of single elements or contents.

41. The method according to claim 30, wherein the application is executable in order to support a dynamic swapping or a dynamic reloading.

42. The method according to claim 30, wherein the application may run such that it provides a context-sensitive dynamic menu structure wherein certain menu elements, information or functions arise, which are dependent from a context, a state or event, in which the application is resting.

43. The method according to claim 30, wherein the application is such executable that it supports a dynamic personalization wherein the user navigation on the client is transmitted to the server and enables to adapt the client on the basis of the navigation.

44. The method according to claim 30, wherein the transmission between the second module and the fourth module (640) is performed by a transmission method that allows the transmission with several simultaneously occupiable channels of different transmission systems or allows a transmission by means of channel bundling.

45. The method according to claim 30, wherein the application builds up and down a connection from client to the server (600) which is time controllable.

46. A computer program product, which is either in the form of a machine-readable medium with program code stored on it, or in the form of a propagated signal comprising a representation of program code, wherein the program code is arranged to carry out a method, when executed on a computer system, of operating a client in a client-server network, said method comprising:

fixing or determining a server configuration in a server;

transmitting of the server configuration to the client; and

executing of the server configuration by the client based on the server configuration loaded on the client such that an application is independently executable in the client and a simulation of a server function is performed by the client.