DE102006037029A1 - Device and method for realizing a data supply - Google Patents

Abstract

The invention relates to a device and a method for realizing a data supply with a first data connection interface (1) for realizing a data connection (http) to a server (S) via which data (W (KP)) coded according to a first transport protocol can be received , A first transport protocol unit (2) implements a data transport (O {W (KP) of the encoded data (W (KP)) on the data link (http) according to a second transport protocol. W (KP)) according to the first transport protocol, whereby the original supply data (KP) are generated, thus obtaining a very inexpensive data supply.

Description

The The present invention relates to a device and a Method for realizing a data supply and in particular to an apparatus and a method for realizing a data supply for mobile Telecommunication terminals via a packet-switching network.

Especially the use of mobile telecommunication terminals is increasing in recent years leaps and bounds. Mobile telecommunication terminals such as mobile phones, Smartphones and so-called PDAs (Personal Digital Assistant) are transforming from relatively simple end devices with individual functions too increasingly complex devices with Phone and PDA capabilities. With these improvements, however, there is a greater need for configurability and maintenance.

Often have to Therefore, configuration settings are changed on the mobile telecommunications terminals are stored. For example, it may be that a service provider the configuration settings of a subscriber in response to a change to change on duty MUST, or a setting that relates to a predetermined application in the terminal may require modification.

Usually becomes such a data supply from mobile telecommunication terminals to Realization of a corresponding configuration via so-called OTAP (Over The Air Provisioning). For example, you can use an SMS connection (Short Message Service) Configuration information from a server via Network are transmitted to a telecommunications terminal to order to allow a corresponding configuration of a service and / or the terminal. Such a conventional Configuration of tele communication terminals caused by an SMS connection but also extremely high costs for the provider of the configuration parameters, since sometimes a considerable Number of SMS or short messages required to complete a configuration record on a mobile device transferred to.

Of the The invention is therefore based on the object, a device and to provide a method for realizing a data supply, at least for the provider of configuration data a significant reduction allow the costs.

According to the invention this Object with regard to the device by the features of the claim 1 and with regard to the method by the measures of the claim 18 solved.

Realized according to the invention therefore, a first data connection interface is a data connection to a server, over which according to one first transport protocol encoded data are received. A first transport protocol unit realizes a data transport the coded data on the data connection according to a second transport protocol. Finally In a second transport protocol unit, a decoding is performed the coded data according to the first Transport protocol carried out, whereby the actual supply data are generated. Using suitable transport protocols give a particularly simple one Realization of the data structures with a simultaneous very simple and cost-effective data transport.

For example the first data connection interface is an "http" interface and the first transport protocol is a document-based protocol for Parameterization of clients. In particular, the first transport protocol an "open wave Provisioning "," OTAP 7.0 "or" OMA-CP ". The second transport protocol is, for example, a session-based protocol for the parameterization of clients and in particular the "OMA-DM" protocol Such concrete realization, in conventional mobile telecommunication terminals often already existing protocol structures are used, being for data transmission a cost-effective Data supply allows becomes. Preferably, therefore, as the first transport protocol unit uses an "OMA-DM" client, to a referencing of the second transport protocol unit has a node of its "OMA-DM" tree. a technical realization is further simplified.

alternative For this purpose, the first transport protocol unit can also be an "OMA-DL" client, as the place of delivery for the second transport protocol unit specifies a predetermined memory location. In this case, over a unidirectional connection a corresponding configuration record in the terminal be downloaded.

Further The "OMA-DM" client may provide a terminal identification in a node of its "OMA-DM" tree, which allows authentication of the encoded data. In this way it can be ensured that only those of one predetermined server sent data in a respective terminal as configuration data accepted become.

Furthermore, a second data connection interface for realizing a data connection be provided to the server, over which the encoded according to the first transport protocol data according to the first transport protocol are also transmitted. Preferably, WAP push messages can thus be transmitted via an SMS client, which enables an initial configuration of the data supply according to the invention via an SMS data connection interface which is usually present in each terminal.

Further can a third connection interface for the realization of a Data connection may be provided via the according to any transport protocol encoded data or uncoded supply data transmitted become. Such data connection interfaces are for example Bluetooth, WLAN, IrDA, USB or RS232, via for example, in a service department or a repair shop respective configuration data are loaded quickly and easily can.

Regarding of the method for realizing a data supply are de Supply data according to a coded first transport protocol for generating coded data, subsequently a data transport of the coded data according to a second transport protocol carried out and finally the coded data according to the first transport protocol to recover the supply data decoded again. Especially with a combination This makes OMA-CP and OMA-DM transport protocols particularly useful effective and cost effective Data supply especially for mobile telecommunication terminals be created.

In the further subclaims Further advantageous embodiments of the invention are characterized.

The Invention will now be described by way of embodiments with reference closer to the drawing described.

It demonstrate:

1 a simplified representation of a client-server system for realizing the data supply according to the invention;

2 a simplified block diagram illustrating essential functional blocks of in 1 illustrated structure according to a first embodiment;

3 a simplified block diagram of an apparatus for implementing a data supply according to a second embodiment; and

4 a simplified flow diagram illustrating essential steps of the method according to the invention.

1 shows a simplified representation of a so-called client-server system in which the present invention can be realized, for example.

According to 1 In this case, a server S, such as a configuration server, configuration data over a network N a telecommunications terminal TE provided, so this example, an e-mail service (electronic mail) without complicated input of configuration data in a simple and user-friendly way and Can realize manner. The network N can in this case comprise a circuit-switched network and / or a packet-switching network such as the Internet. The telecommunication terminal TE is, for example, a wireless terminal such as a mobile phone, smartphone or a so-called PDA, which are connected via an unillustrated mobile network to the network N. However, the telecommunication terminal TE may also be a wired terminal such as a PC.

2 shows a simplified block diagram of the in 1 illustrated system. According to 2 the configuration server S has a setting memory 7 on, for example, provides the necessary for a configuration of a terminal configuration parameter KP as supply data available. These supply data or configuration parameters KP are from a coding unit 8th coded according to a first transport protocol, whereby encoded data W (KP) are generated. For example, as a coding unit 8th in the configuration server S a so-called OTAP encoder (Over The Air Provisioning) used.

The first transport protocol is preferably the so-called "OMA CP" transport protocol (Open Mobile Alliance - Client Provisioning) for generating so-called "WAP Push" messages (Wireless Application Protocol) is used, wherein the WAP push messages the encoded data or configuration parameters KP can contain. These configuration parameters KP, which are encoded in a WAP push message W (KP), are then supplied to a server-side OMA-DM protocol unit (Open Mobile Alliance-Device Management), which uses a server-side data connection interface 10 performs a session-based data connection such as an "http" connection (hypertext transfer protocol) over the network N to the telecommunication terminal TE.

The according to the first transport protocol coded data or WAP push messages W (KP) are thus transmitted via the bidirectional "http" connection using a second transport protocol, that is, the OMA-DM protocol O {W (KP)}.

In the mobile telecommunication terminal TE is now a first data connection interface 1 for the realization of a terminal-side data connection to the configuration server S or its data connection interface 10 , Furthermore, the terminal TE has a first transport protocol unit 2 for implementing a data transport of the coded data or WAP push messages on the "http" data connection in accordance with a second transport protocol, the second transport protocol being a session-based protocol for parameterizing clients 2 a so-called OMA-DM client (Open Mobile Alliance - Device Management) used to implement an "OMA-DM" protocol, whereby the encoded according to the first transport protocol data or WAP push messages W (KP) particularly cost over the Network N. However, the configuration parameters KP are not resolved in the extremely complex tree structure customary for OMA-DM, but are supplied as a whole to a node of the "OMA-DM" tree, which is subsequently fed by a second transport protocol unit 3 can be read out.

The second transport protocol unit 3 is essentially a decoding of the encoded data or the WAP push messages W (KP) according to the first transport protocol, which again receives the original supply data or configuration parameters KP. These can then be stored in a registry memory or "registry" 4 are stored, which allows a configuration of the mobile telecommunication terminal TE or a respective service.

According to the invention consequently to be transferred Supply data or configuration parameters first according to a coded first transport protocol and then transmitted according to a second transport protocol, to conclude again according to the first one To be decoded transport protocol. The first transport protocol presents here a document-based protocol for the parameterization of Clients are preferably the first transport protocol the so-called "Open Wave Provisioning Protocol the company Open Wave, the "OTAP 7.0 "protocol Company Nokia or the "OMA-CP" protocol (Open Mobile Alliance Client Provisioning) used.

In contrast, be the thus coded supply data or configuration parameters according to the second Transport protocol over transmit the network N, for example, a session-based protocol for parameterization used by clients and in particular the "OMA-DM" protocol (Open Mobile Alliance - Device Management) is used.

Although the "OMA-DM" client 2 preferably a node of its "OMA-DM" tree structure as transfer location for the WAP push client (Wireless Application Protocol) 3 can in the "OMA-DM" client 2 also a referencing, ie indirect assignment, the second transport protocol unit 3 or the WAP push client to a node of the "OMA-DM" tree, in which case the OMA-DM client maps 2 the inbox of the WAP push client 3 to a node of its tree structure, the server S then sending a WAP push message via the OMA DM server 9 under the output of an ADD command for this node. The execution of such an ADD command places an object in the WAP Push Inbox and optionally can be the WAP push client 3 then prompt to process this object. In this way, status information such as success confirmation or error info could be sent to the server S, which is usually not possible when WAP push messages are sent over an SMS connection.

Optionally, the "OMA-DM" client 2 Furthermore, a terminal identification in a node of its "OMA-DM" tree structure, which allows authentication of the encoded data or the WAP push messages W (KP) Such a terminal identification can represent, for example, an IMSI (International Mobile Subscriber Identity, for example, which represents a number that uniquely identifies a subscriber to a mobile service on GSM (Global Communications for Mobile Communications) mobile networks, for example, NETWPIN authentication may be used as authentication for WAP push messages which is particularly user-friendly.

According to 2 may further include a second data connection interface 5 be provided for the realization of a data connection to the server S, via which the encoded according to the first transport protocol data or WAP push messages W (KP) are transmitted according to the first transport protocol.

Preferably, this second data connection interface 5 an SMS interface for the realization of an SMS connection. Such SMS data connection interfaces or SMS clients 5 are usually in any mobile anyway Telecommunication terminal realized because they represent the only way that can be automatically configured by a server S an initially unconfigured terminal. Preferably, therefore, a first configuration for the data supply according to the invention first via this SMS data connection interface 5 or the SMS client take place, with an appropriate SMS server on the server side 11 which also transmits encrypted according to the first transport protocol data or WAP push messages. Such a first configuration is also referred to as "bootstrapping." As soon as the telecommunication terminal TE has been configured according to the invention, a further data supply can subsequently be realized via the cost-effective "http" connection in accordance with, for example, OMA-DM. Basically, as a second data connection interface 5 an e-mail data connection interface may also be provided, the data being transmitted in an e-mail message.

Furthermore, according to 2 a third data connection interface 6 be provided for the realization of a further data connection over which encoded according to any transport protocol data or even uncoded supply data or configuration parameters KP can be transmitted. Such a data connection interface represents, for example, a Bluetooth, WLAN (Wireless Local Area Network), IrDA, USB or RS232 interface, which enables an associated connection in each case. In particular, for repair or maintenance work can such a third data connection interface 6 a simple and very effective configuration of the telecommunication terminal TE take place. In this case, the corresponding received configuration parameters KP can turn directly into the registration memory 4 be enrolled.

As a result, any transport mechanism may be used to transmit, for example, WAP push messages to a terminal. For example, the WAP push messages may represent XML-encoded (eXtended Markup Language) OTAP (Over The Air Provisioning) documents. The first transport log unit 2 extracts the original WAP push message and forwards it to the second transport protocol unit or the WAP push client 3 who, in turn, processes the document according to his standard procedures.

An OTAP document, such as a WAP push message, is thus made using the OMA DM server 9 as envelope or envelope via an "http" connection to the OMA DM client 2 of the mobile terminal TE. The OMA DM client 2 then extracts the WAP push message and passes it to the WAP push client 3 using the same interfaces as commonly used by an SMS client 5 used. The WAP push client 3 then process the document and write the settings or configuration parameters KP into the registration memory 4 , whereby the configuration of the terminal TE is performed or enabled.

3 shows a simplified block diagram of an apparatus for realizing a data supply according to a second embodiment, wherein like reference numerals designate like or corresponding elements, and therefore their repeated description is omitted below.

According to 3 The first transport protocol unit can also be an "OMA-DL" client 2A (Open Mobile Alliance - DownLoad), using a predetermined memory location 2 B in the telecommunication terminal as the transfer location for the second transport protocol unit or the WAP push client 3 is determined. With such an OMA DL client 2A with associated memory location 2 B For example, an OMA download mechanism can be implemented that allows downloading, for example, WAP push messages to a predetermined location in the file system of the terminal. This location 2 B is here by an agreement as a transfer point for the WAP push client 3 Are defined. As an alternative to the OMA-DL client, a download mechanism can also be performed using existing WAP or HTML browsers that can exist or be implemented in the terminal TE.

On that way Supply data such as configuration parameters are no longer over costly Short messages (SMS messages) are transmitted, but can over appropriate inexpensive Data connections are exchanged or transmitted. On reason coding in a first transport protocol such as a binary WBXML document can transfer the configuration parameters much faster be considered as exclusive Use of an OMA-DM architecture. Furthermore, in contrast to unidirectional SMS messages interactive features can be realized, for example a feedback for the transferred Enable configuration parameters to server S.

Furthermore, both server-side and terminal-side can be used on a variety of existing function blocks, which is why only minor modifications are required and thus continue to reduce costs can. In this way, results in a very fast and simple and cost-effective implementation of a data supply from a server to a telecommunications terminal.

4 shows a simplified flowchart for illustrating essential steps of the method according to the invention.

After a start in step S0, the supply data such as configuration parameters KP are first encoded according to a first transport protocol for generating encoded data W (KP). For example, a single binary WBXML document is created and placed in a WAP push message. In steps S2 and S3, a data transport of the data W (KP) encoded in this way is then carried out in accordance with a second transport protocol. More specifically, using an OMA-DM protocol, for example, an http data connection between a server S and a terminal TE is preferably realized, resulting in substantially reduced costs. In a step S4, the data W (KP) thus transmitted and yet coded are then decoded according to the first transport protocol for recovering the original supply data or configuration parameters KP. This can be found, for example, in the WAP push client 3 the terminal instead. Finally, in a step S5, the terminal TE is configured for a predetermined service, wherein, for example, the decoded supply data or configuration parameters are written into a registration memory. The method ends in a step S6.

The The invention has been described above by means of an "http" connection as a cost-effective data connection described. However, it is not limited to and includes the same There are also other session-based data connections.

1

first Data link interface

2

first Transport protocol unit

3

second Transport protocol unit

4

Registration memory

5

Second Data link interface

6

third Data link interface

7

setting memory

8th

encoder

9

server-side Transport protocol unit

10

server-side first data connection interface

11

server-side second data connection interface

S

server

TE

telecommunication terminal

2A

OMA DL client

2 B

DL-location

KP

Configuration parameters

W (KP)

coded dates

O {W (KP)}

according to the second Transport protocol encoded data

N

network

S0 to S6

steps

Claims (29)

Device for realizing a data supply comprising: a first data connection interface ( 1 ) for realizing a data connection (htpp) to a server (S) via which data encoded according to a first transport protocol (W (KP)) is received; a first transport protocol unit ( 2 ) for realizing a data transport of the coded data (W (KP)) on the data connection (http) according to a second transport protocol; and a second transport protocol unit ( 3 ) for realizing a decoding of the coded data (W (KP)) according to the first transport protocol for generating supply data (KP). Device according to claim 1, characterized by a registration memory ( 4 ) for storing the supply data (KP). Device according to claim 1 or 2, characterized by a second data connection interface ( 5 ) for the realization of a data connection (SMS) to the server (S) via which the data encoded according to the first transport protocol is transmitted according to the first transport protocol. Device according to one of the claims 1 to 3, characterized by a third data connection interface ( 6 ) for the realization of a data connection (Bluetooth) via the encoded according to any transport protocol data or uncoded supply data (KP) are transmitted. Device according to one of the claims 1 to 4, characterized in that the first data connection interface ( 1 ) represents an http interface. Device according to one of the claims 1 to 5, characterized in that the second data connection interface ( 5 ) represents an SMS or e-mail interface. Device according to one of the claims 1 to 6, characterized in that the third data connection interface ( 6 ) is a Bluetooth, WLAN, IrDA, USB or RS232 interface. Device according to one of the claims 1 to 7, characterized in that the first transport protocol a represents a document-based protocol for the parameterization of clients. Device according to claim 8, characterized in that the first transport protocol represents the "Open Wave Provisioning", "OTAP 7.0" or "OMA-CP" protocol. Device according to one of the claims 1 to 9, characterized in that the second transport protocol a session-based protocol for parameterizing clients. Device according to claim 10, characterized the second transport protocol is the "OMA-DM" protocol. Device according to one of the claims 1 to 11, characterized in that the first transport protocol unit ( 3 ) represents an "OMA-DM" client. Device according to claim 12, characterized in that the "OMA-DM" client ( 2 ) a referencing of the second transport protocol unit ( 3 ) to a node of its "OMA-DM" tree. Device according to one of the claims 1 to 13, characterized in that the "OMA-DM" client ( 2 ) has a terminal identification in a node of its "OMA-DM" tree, which enables authentication of the encoded data (W (KP)). Device according to one of the claims 1 to 11, characterized in that the first transport protocol unit comprises an "OMA-DL" client ( 2A ) with a transfer location for the second transport protocol unit ( 3 ) specified storage location ( 2 B ). Device according to one of the claims 1 to 15, characterized in that the encoded data (W (KP)) represent a "WAP Push" message. Device according to one of the claims 1 to 16, characterized in that the supply data (KP) configuration parameters for a mobile telecommunication terminal (TE). Method for implementing a data supply with the steps: Coding (S1) of supply data (KP) according to one first transport protocol for generating coded data (W (KP)); Perform (S2, S3) of a data transport (O {W (KP)}) of the encoded data (W (KP)) according to one second transport protocol; and Decoding (S4) the coded Data (W (KP)) according to the first Transport protocol to recover the Supply data (KP). Method according to claim 18, characterized the next step: Configure (S5) a telecommunication terminal (TE) with the recovered Supply data (KP). Method according to claim 18 or 19, characterized characterized in that the data transport is performed via an http connection. Method according to one of the claims 18 to 20, characterized in that the first transport protocol a represents a document-based protocol for the parameterization of clients. Method according to claim 21, characterized the first transport protocol represents the "Open Wave Provisioning", "OTAP 7.0" or "OMA-CP" protocol. Method according to one of the claims 18 to 22, characterized in that the second transport protocol a session-based protocol for parameterizing clients. Method according to claim 23, characterized the second transport protocol is the "OMA-DM" protocol. Method according to one of the claims 18 to 24, characterized in that during the data transport an "OMA-DM" client performs a referencing of the second transport protocol unit ( 3 ) to a node of its "OMA-DM" tree. Method according to one of the claims 18 to 25, characterized in that the data transport of the "OMA-DM" client terminal identification in a node of its "OMA-DM" tree, which allows authentication of the encoded data (W (KP)). Method according to one of the claims 18 to 26, characterized in that during data transport an "OMA-DL" download is performed. Method according to one of the claims 18 to 27, characterized in that the encoded data (W (KP)) represent a "WAP Push" message. Method according to one of the claims 18 to 28, characterized in that the supply data (KP) configuration parameters for a mobile telecommunication terminal (TE).