WO2002091702A1

WO2002091702A1 - Data communication system and a method for transmitting information

Info

Publication number: WO2002091702A1
Application number: PCT/DE2001/001825
Authority: WO
Inventors: Albrecht Kunz; Manfred Leitgeb; Joerg Swetina
Original assignee: Siemens Aktiengesellschaft
Priority date: 2001-05-10
Filing date: 2001-05-10
Publication date: 2002-11-14
Also published as: CN1507729A; EP1386466A1

Abstract

The invention relates to a data communication system comprising a network plane (10), a terminal plane (12) and an interface plane (14). The terminal plane (12) is provided with tool kits (26, 28), which are used to determine the characteristics of the terminal plane and the interface plane (14) permits information concerning the characteristics of the terminal plane (12) to be transmitted to the network plane (10). The invention is provided with an interface structure (30), which is allocated to the tool kits (26, 28) and which is used for the frequent transmission of information concerning the characteristics of the terminal plane (12) to the network plane (10). The invention also relates to a method for transmitting information.

Description

description

Data communication system and method for transmitting information

The invention relates to a data communication system with a network level, a terminal level and an interface, tool kits being provided in the terminal level, by means of which properties of the terminal level can be determined, and wherein information about properties of the terminal level can be transmitted to the network level. The invention further relates to a method for transmitting information about properties of a terminal to a network via an interface, toolkits being provided in the terminal.

Generic data communication systems and generic methods are used for communication over a network. A variety of services are offered by modern networks. In order to be able to use these services, terminals (terminal stations) are used on a terminal level, which are generally operated by a user. Such terminals are, for example, telephones, computers or other data processing devices. Since different terminals with different properties access the same services, it is generally provided that when an application starts, the properties of the terminal used when the application starts are transmitted via an interface level. The services provided by the network are then matched to the terminal properties.

So far, the interface properties, which is designed as a so-called API ("Application Programming Interface"), could only be queried once from the network level when building an application (for example, WAP or JAVA). The query takes place with the help of dated toolkits, which provide a corresponding process environment at the terminal level. The standardized toolkits MExE, SAT, USAT exist within the framework of modern network architectures (3GPP; "3G Partnerchip Pro ηect").

If neither the services offered by the network level nor the conditions at the terminal level change, then an adapted communication between the network level and the terminal level can take place during the entire application.

Such a consistency both at the network level and at the terminal level is, however, not fundamentally given. This consistency can no longer be assumed, particularly in the case of multimedia applications.

For example, it is possible that the setting or the properties of a terminal change during the use of a service. This can be done, for example, by connecting additional components to a terminal while using a service. For example, a laptop can be connected to a palmtop computer that initially built the application while the application is being used. This changes the settings or the term capabilities. For example, the display now has a higher resolution and longer sections of text can be displayed at the same time.

However, the reverse case is also conceivable, namely that a session is started with a display of high resolution and is subsequently transferred to a terminal structure with a lower resolution. Changes on the network side can result from, for example, switching from an alphanumeric font to a Japanese font while using a service. In all of these cases, no adaptation takes place according to the prior art, since a query is only made via the interface at the beginning of the use of a service.

The invention is based on the task of taking into account the changing conditions during the use of a network service in the communication between the network level and the terminal level.

This object is achieved with the features of claims 1 and 10.

Advantageous embodiments and further developments of the invention are specified in the dependent claims.

The invention is based on the generic data communication system in that an interface structure assigned to the toolkits is provided, via which information about properties of the terminal level can be frequently transmitted to the network level. In this way it is possible that the information about the properties of the terminal level is not only transmitted to the network level when the use of a service is built up. Rather, this information can practically be transferred continuously, so that the terminal structure can always be optimally used.

Advantageously, information about properties of the terminal level is transmitted to the network level at the request of the network level via the interface structure. In this way, an "enabling function" is made available to the network level. As soon as the network level activates this "enabling function", the interface structure in the terminal delivers the requested information. This

Functionality can be implemented in such a way that the 3GGP standardized interface OSA API ("Open Service Archi- tecture Application Programming Interface ") as a counterpart to the API in the terminal.

It can also be advantageously provided that the transmission of information about properties of the terminal level to the network level is actively initiated by the interface structure. The interface structure can transmit information about properties of the terminal level to the network level at regular intervals, for example without the influence of the network level. The interface structure is thus an active element in the terminal, which supports the user in communicating with the network structure.

The data communication system is developed in a particularly advantageous manner in that the interface structure is a personalized agent implemented by a software code. Such a "personalized agent" or "personalized intelligent agent" ("Personal Intelligent Agent") can take on tasks that relieve the user. For example, the agent automatically generates soft updates and can independently load applications from the network to the terminal level. Management functions are also taken over by the personalized agent.

In a further advantageous embodiment, the personalized agent is self-installing. The user can therefore automatically use the services of the personalized agent as soon as data communication takes place between the terminal level and the network levels.

In an advantageous embodiment, the personalized agent is arranged on the network level. As soon as a network service is used, the personalized agent is loaded into the memory area of the terminal. This can be done, for example, in the form of a JAVA applet. To When the service ends, the personalized agent can be transferred back to the network level.

However, it can also be useful for the personalized agent to be arranged on the terminal level. In particular in the case of terminals with sufficient storage capacity, it is possible for the personalized agent to be permanently stored in the storage area of the terminal. An initial loading of the personalized agent at the beginning of each session is therefore unnecessary.

It is particularly preferred if the personalized agent can be transferred between the network level and the terminal level. This is also useful if the personalized agent itself is arranged on the terminal level, that is to say if in principle no loading of the personalized agent is required at the start of a session. The possibility of transferring the personalized agent between the levels increases the flexibility of the system, for example if there is a current storage shortage despite the large storage capacity.

In a particularly advantageous embodiment of the data communication system, this is further developed in that the personalized agent is assigned to a user and in that the user configures the personalized agent. In this way, the basic task of more personalizing a terminal is usefully satisfied. Furthermore, the current wishes of a user who decides on certain services are known before the start of using a service. In this way, the service can be optimized for a specific user. Due to the fact that the agent is created or configured by the user himself, the user has complete control over the agent. He can therefore also decide which user profile data is not in the network should be visible. In this way, a high level of data security is achieved.

The invention builds on the generic method in that an interface structure assigned to the toolkits is provided, via which the information about properties of the terminal is frequently transmitted to the network. The advantages of the data communication system according to the invention are implemented by this method.

The method is developed in a particularly useful manner in that information about properties of the terminal level is transmitted to the network level at the request of the network level via the interface structure. It is therefore provided with an "enabling function".

However, it can also be useful to design the data communication system in such a way that the transmission of information about properties of the terminal level to the network level is actively initiated by the interface structure. The transmission can take place, for example, at regular intervals or depending on actual changes with regard to the properties of the terminal level.

The method according to the invention has particular advantages in that the interface structure is a personalized agent implemented by a software code. There is a user-specific relief for the user, for example, through the takeover of management functions by the personalized agent.

It is also useful if the personalized agent is self-installing. The personalized agent can therefore be used automatically when using services. It can be advantageous if the personalized agent is arranged on the network level. This is particularly useful in the context when terminals with low storage capacity are used.

However, it can also be advantageous if the personalized agent is arranged on the terminal level. In the case of terminals with sufficient storage capacity, it may not be necessary to load the personalized agent at the beginning of each use of a service.

In numerous procedural variants, it is useful if the personalized agent is transferred between the network level and the terminal level. As a result, there is great flexibility in the communication between the terminal level and the network level.

In a further preferred embodiment of the method according to the invention, this is further developed such that the personalized agent is assigned to a user and that the user configures the personalized agent. This has particular advantages with regard to data security. Since the user creates or configures the personalized agent himself, he can also decide which information should be transferred to the network level and which information should be treated confidentially.

The method according to the invention preferably has the following steps: determining whether a personalized agent is available and, if no personalized agent is available, executing further steps on the basis of predetermined properties. The method is therefore so flexible that it supports data communication between a terminal level and a network level even without the presence of a personalized agent. If there is no personalized agent, it is assumed that the proprietary agent terminals of the terminal are located in a minimal area. It is also possible for standardized terminal properties to be transmitted by other means.

The method is also advantageous with the following steps: determining whether a personalized agent is available, if a personalized agent is available, determining whether the personalized agent is arranged in the terminal, and if the personalized agent is not arranged in the terminal , transfer the personalized agent to the terminal. If the personalized agent already exists in the terminal, there is no need to transfer the personalized agent. In the other case, the personalized agent is transferred, for example as a JAVA applet, to the memory area of the terminal.

The method is particularly useful when the personalized agent communicates with toolkits in the terminal and when toolkits in the terminal query information about terminal properties and transmit it to the personalized agent. The personalized agent is designed as an interface superior to the toolkits. The toolkits take on the task of determining the terminal properties, while the personalized agent serves as an interface to the network level.

The invention is based on the knowledge that a personalized, intelligent agent creates numerous application advantages. On the one hand, the terminal surface is always used optimally. On the other hand, changes that occur on the network side can be taken into account. Agents can sometimes act independently for a user. For example, you can relieve the user of administrative tasks, such as creating and managing mailing lists and organizing and monitoring appointments. The management of a session can also be taken over, for example for multimedia video conferences, for online Purchasing and even when negotiating with other users or with agents of other users. The personalized intelligent agent advantageously supports a "Virtual Home Environment" (VHE), which is in particular a target of modern UMTS architectures ("Universal Mobile Telecommunications Systems").

The invention will now be explained by way of example with reference to the accompanying drawings using preferred embodiments.

It shows:

1 shows a block diagram to explain a data communication system according to the invention with a personalized agent and

FIG. 2 shows a flowchart to explain an embodiment of a method according to the invention.

FIG. 1 shows a block diagram to explain a data communication system according to the invention. This can be implemented in particular as an element within a VHE structure ("Virtual Home Environment") within the framework of UMTS technology. The general goal of a VHE structure is that a user always finds the same application surface. This means the same "look and feel" for the user. The block diagram shows a network 10 and a terminal 12. Furthermore, an interface 14 is shown. This interface 14 is a standardized application interface. Applications of an application level 16 can be used using the terminal 12 via this standardized user interface 14. A terminal agent 18 is provided within the network level 10 and functions as a network-side counterpart to the personalized intelligent agent 30. Terminal agent 18 is may produce information for the personalized intelligent agent 30. Communication between the network 10 and the application interface 14 takes place via this. The network includes, for example, the servers for GSM / UMTS 20, a client server 22 and an internet server 24.

The terminal includes toolkits, for example the MExE 26 toolkit or the toolkits 28 for SAT / USAT. A personalized agent 30 is provided as a further interface between the terminal 12 and the network 10. This personalized agent 30 can move back and forth between the network 10 and the terminal 12. A memory 32 is provided in the terminal 12, which is reserved for storing the personalized agent 30.

FIG. 2 shows a flow chart to explain typical process sequences that can take place in a data communication system according to the invention.

The steps shown mean in detail;

S01: Personalized intelligent agent available? S02: Perform service assuming minimal term properties.

S03: Is the personalized intelligent agent in the terminal? S04: Load personalized agents from the network level to the terminal level. S05: Communication of the personalized intelligent agent with toolkits at the terminal level. S06: Toolkits determine term properties and properties of the periphery. S07: Toolkits dynamically report term properties and properties of the periphery to the personalized intelligent agents. S08: The personalized intelligent agent frequently reports to the network service about the current state of the terminal properties and the properties of the peripherals. S09: termination of the service and optional retransmission of the personalized intelligent agent to the network level.

In step SOI, the requested service asks whether a personalized agent is available for the special service.

If this is not the case, the service goes to step

502 assume that the terminal has minimal capabilities, or standard terminal capabilities can be transferred by other means. If it is determined in step SOI that a personalized intelligent agent is available, then next in step S03 it is determined whether the personalized intelligent agent is arranged in the terminal. If this is not the case, the personalized intelligent agent is loaded from the network level to the terminal level in step S04. If the personalized intelligent agent is already arranged in the terminal and this in step

503 is determined, loading the personalized intelligent agent from the network level to the terminal level can be omitted. In step S05, the personalized intelligent agent can then communicate with the tokits at the terminal level.

S06 symbolizes a process level in which terminal properties and peripheral properties are determined by the toolkits. Such a determination is carried out dynamically by the toolkits. In process stage S07, the toolkits dynamically report the information obtained to the personalized, intelligent agent. In process level S08, the personalized intelligent agent in turn reports to the network service. After the service has ended, the personalized intelligent agent can be transferred back to the network level in step S09. The features of the invention disclosed in the above description, in the drawing and in the claims can be essential for realizing the invention both individually and in any combination.

LIST OF REFERENCE NUMBERS

10 network level

12 Terminal level 14 Interface level

16 applications

18 terminal agent (network side)

20 GSM / UMTS servers

22 client servers 24 internet servers

26 MExE toolkit

28 SAT / USAT toolkit

30 personalized intelligent agent (PIA)

32 memories for personalized agents

Claims

claims

1. Data communication system with a network level (10), - a terminal level (12) and an interface level (14), tool kits (26, 28) are provided in the terminal level (12), through which properties of the terminal level can be determined, and - whereby Information about properties of the terminal level (12) can be transmitted to the network level (10) via the interface level (14), characterized in that an interface structure (30) assigned to the toolkits (26, 28) is provided, via which a frequent Information about properties of the terminal level (12) can be transmitted to the network level (10).

2. Data communication system according to claim 1, so that the transmission of information about properties of the terminal level (12) to the network level (10) takes place at the request of the network level (10) via the interface structure (30).

3. Data communication system according to claim 1 or 2, that the transmission of information about properties of the terminal level (12) to the network level (10) is actively initiated by the interface structure (30).

4. Data communication system according to one of the preceding claims, characterized in that the interface structure (30) is a personalized agent implemented by a software code.

5. Data communication system according to one of the preceding claims, d a d u r c h g e k e n n z e i c h n e t that the personalized agent (30) is itself installed.

6. The data communication system as claimed in one of the preceding claims, that the personalized agent (30) is arranged in the network level (10).

7. The data communication system as claimed in one of the preceding claims, that the personalized agent (30) is arranged in the terminal level (12).

8. Data communication system according to one of the preceding claims, that the personalized agent (30) is transferable between the network level (10) and the terminal level (12).

9. Data communication system according to one of the preceding claims, namely that the personalized agent (30) is assigned to a user and that the user configures the personalized agent.

10. A method for transmitting information about properties of a terminal (12) to the network (10) via an interface (14), wherein toolkits (26, 28) are provided in the terminal (12), characterized in that that an interface structure (30) assigned to the toolkits (26) is provided, via which information about properties of the terminal (12) is frequently transmitted to the network (10).

11. The method as claimed in claim 10, so that information about properties of the terminal level (12) is transmitted to the network level (10) at the request of the network level (10) via the interface structure (30).

12. The method according to claim 10 or 11, so that the transmission of information about properties of the terminal level (12) to the network level (10) is actively initiated by the interface structure (30).

13. The method according to any one of claims 10 to 12, so that the interface structure (30) is a personalized agent implemented by a software code.

14. The method according to any one of claims 10 to 13, so that the personalized agent (30) is self-installing.

15. The method according to any one of claims 10 to 14, so that the personalized agent (30) is arranged in the network level (10).

16. The method according to any one of claims 10 to 15, characterized in that the personalized agent (30) is arranged in the terminal level (12).

17. The method according to any one of claims 10 to 16, so that the personalized agent (30) is transferred between the network level (10) and the terminal level (12).

18. The method according to any one of claims 10 to 17, so that the personalized agent (30) is assigned to a user and - that the user configures the personalized agent.

19. The method according to any one of claims 10 to 18 with the steps: - determining whether a personalized agent (30) is available

if no personalized agent (30) is available, further steps are carried out on the basis of predetermined properties.

20. The method according to any one of claims 10 to 19 with the steps:

Determine if a personalized agent (30) is available

- if a personalized agent (30) is available, determining whether the personalized agent (30) is arranged in the terminal (12), and if the personalized agent (30) is not arranged in the terminal (12), transferring the personalized agent ( 30) in the terminal (12).

21. The method according to any one of claims 10 to 20, wherein the personalized agent (30) communicates m t toolkits (26, 28) in the terminal and - toolkits (26, 28) in the terminal (12) information about

Query term properties and transmit them to the personalized agent (30).