DE10156197A1 - Method for data transmission in a data communication network, associated transmitter / receiver unit and radio communication system - Google Patents

Abstract

In order to transmit data in a data communication network, control information (SI1) is allocated to the data signals (ZN1, ZN2) in one or several additional data elements (DE1) containing an identifier of the order of data objects of the same name.

Description

The invention relates to a method for data transmission in a data communication network, especially text and / or image data with and without sound.

The invention has for its object a way to show how data or Message signals in the most efficient way possible from one first user application unit to at least one second Transfer user application unit and be evaluated there can. This task is initiated in a procedure mentioned type in that the respective data signal at least one control information in at least one additional data element is assigned, the one Identification of the order of data elements of the same name included.

Through such additional control information with whose help data elements of the same name with regard to their Order can be marked in addition to each other these data elements of the same type or name in clearly related to each other, d. H. in be ordered in a defined manner. This makes it special possible in the respective receiving user application unit to subsequently reconstruct which order of the same name Data elements in the same data or message signal in the respective sending user application unit and / or whose transmission path through one or more intermediate components of the data communication network imprinted has been. This is in the respective receiving unit an efficient evaluation enables, since the individual Data elements now with the additional labeling can be compared and evaluated.

The invention also relates to a transmitting / receiving unit Data communication network used to carry out the the inventive method is formed.

The invention also relates to a radio communication system which at least one transmitting and / or receiving unit for Carrying out the method according to the invention.

Other developments of the invention are in the Sub-claims reproduced.

The invention and its developments are as follows explained in more detail with reference to drawings.

Show it:

Fig. 1 shows a schematic representation of the multiple forwarding of a message signal from a first transmitting unit of a data communication network, especially a radio communication system between user application units of time, each user application unit when forwarding assigns the messages to be transmitted signal in each case one or more additional data elements of the same type and according to the invention by a marking in accordance with the Procedure specified,

Fig. 2 shows a schematic representation of the basic structure of a header field in a message signal of the multimedia messaging service and / or Internet emails, and

Fig. 3, 4 in a schematic representation of the structure of a Empfängerzustellnachricht for a user application unit according to Fig. 1 which is a forward message to be transmitted to another user application unit and thereby enters by the inventive process control information in an additional data element for the identification.

Elements with the same function and mode of operation are provided with 4 in FIG. 1 with the same reference numerals.

Various services are used in communication technology applied a message exchange between units of this Enable service. Message types are often used used in addition to those actually to be transmitted Payload information also includes tax information in one Message header, a so-called header. To this Services include, for example, Internet e-mail, their Messages according to the specifications (RFC822 Standard for the Format of ARPA Internet Text Messages, Crocker D., August 1982 and RFC2045 Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies, Freed N. November 1996). Another service of the The type mentioned above is in particular the multimedia desired for UMTS Messaging Service (MMS). With this service Message signals such as B. language, data, images, music, sounds, etc. together on one or more subscriber devices, especially mobile devices, a predefinable group broadcast together. This is group transfer especially in a radio communication system according to the UMTS Standard provided (Universal Mobile Telecommunication System). This group forwarding and transmission of message signals is both about at least an air interface between the subscriber devices predefinable group and at least one base station carried out. On the other hand, this is sending and / or receiving Group messages in the multimedia messaging service too between the other network components of the Radio communication network carried out by the respective base station are assigned, or for other control and operation of the Serve radio communication system. The previous specification the multimedia messaging service is preferably based on two specifications of the third generation partnership Projects (3GPP), on the one hand, the service in principle describe (3G TS 22.140 version 4.1.0, Release 4; Third Generation Partnership Project; Technical Specification Group terminals; Multimedia messaging service (MMS); service Aspects; Stage 1, 2001) and secondly the concrete one Set functionality abstractly (3G TS 23.140 version 4.2.0, Release 4; Third Generation Partnership Project; Technical Specification Group Terminals; Multimedia messaging service (MMS); Functional description; Stage 2, 2001). A possible - and so far also the only one - realization of MMS is in three specifications of the WAP forum (Wireless Application Protocol) (WAP-205-MMS Architecture Overview, Specification; Wireless application protocol, multimedia Messaging service; Architecture Overview Specification, 2001; WAP-206-MMS Client Transactions, Specification; Wireless Application protocol; WAP Multimedia Messaging Service Client Transactions; 2001; WAP-209-MMS Encapsulation, Specification Change document; Wireless application protocol; multimedia Messaging service; Message encapsulation; 2001).

An implementation of MMS currently appears to be cheap via WAP (Wireless Application Protocol). To bridge the respective air interface between an MMS-capable Terminal and a respectively assigned WAP gateway on the Network side is especially according to WAP-209-MMS Encapsulation, Specification Change Document, Wireless Application Protocol, multimedia messaging service, message encapsulation, 2001 the use of the WAP Wireless Session Protocol (WSP) intended. In MMS, too, messages with a Message header containing header fields with tax information, and a data part with useful information between different units of this service exchanged.

Fig. 2 shows a schematic representation of the basic, logical structure of a header field KF according to the specification WAP-209-MMS Encapsulation, Specification Change Document, Wireless Application Protocol, Multimedia Messaging Service, Message Encapsulation, 2001. Such a header field of a message / data signal has a header field name KFN in a first section, to which a header field value KFW is assigned in a second section.

Messages may include some types of Header fields contain multiple to multiple information of the same Type in the same message. An example there are multiple addresses for this. H. when a message to several receiver units each with a separate header Receiver unit is addressed. Now it is desired, everyone Can encode recipient addresses in the same message this can be done, for example, such that for each Receiver address a separate header in the same message signal is used. In other words, for n Receiver addresses n header fields by the respective addressees generated and inserted into the same message. This A large number of header fields are then within the Data structure of the respective message signal preferably equivalent to. With the order of their appearance in the message preferably no order of contents is linked. The order of the header fields is often in the messages irrelevant and can / may during processing and / or Forwarding of the message can also be changed.

So far, it has not been possible in the above-mentioned message services to give several header fields of the same type, ie of the same type, an order in the sense of a weighting in a message. Instead, the contents of several header fields of the same type stand side by side in an equal message. Your order in the message is preferably irrelevant. The header fields of a multimedia message according to WAP contain, in addition to the information of the type of the header field, a value which, as a rule, does not contain an enumeration of several information elements of the same type. Rather, for several information elements of the same type, several header fields of the same type have so far been coded with one, ie the same, information element. The basic logical structure of such a header field is illustrated in FIG. 2. Further details can be found in particular in WAP-209-MMS Encapsulation, Specification Change Document, Wireless Application Protocol, Multimedia Messaging Service, Message Encapsulation, 2001.

In order now for such distribution messages, each to one Group of a plurality of receiving units are sent an improved evaluation option and more efficient Transmission and distribution in a data communication network provide the data of the respective Message signal one or more control information in one or one or more additional data elements associated with one Identification of the order of data elements of the same name contains. In particular, coding of the order of multiple header fields of the same type in the same message performed. This order is preferably independent of the coded order of the header fields in the message and establishes an order that z. B. a chronological Order, a logical order, a causal order, an order of priority, an order of spatial allocation to each other or any other Classification can be.

The additional identification of the order of a large number of data elements of the same name within one and the same message is shown below by way of example using the codes of messages exchanged in the MMS defined by the WAP forum. The time sequence of participants who have forwarded the same message in succession is specified as a classification or identification. For this purpose, a new header field with the name "X-Mms-Forwarded-By", not yet specified, is used. This field is expediently defined and inserted in each case as a header field in the MMS receiver delivery message, which is sent from an MMS connection unit in the data communication network to a further MMS user application, e.g. B. is sent on the end device of the respective subscriber or user to inform about the presence and the possibility of accessing an upcoming multimedia message (in WAP: M- Retrieve.conf message). The basic definition or structure of such a message in the WAP forum is shown schematically in FIGS. 3 and 4, which together comprise a large number of data elements of a recipient delivery message. The header field "X-Mms-Forwarded-By" has been newly introduced to illustrate the invention and is designated by DE1. In particular, it has a name which is the character string "X-Mms-Forwarded-By" in textual coding and a header field value which is referred to as "Forwarded-By-Value". The value includes the address of the subscriber who forwarded the message and also a numerical value, which by definition describes the chronological order of several forwarding processes. Here in the exemplary embodiment, the value "forwarded-by-value" is preferably assigned an integer positive number. Several header fields of this type then have different numbers, a larger number denoting a later point in time when the multimedia message is forwarded. Even with several header fields of this type, it is therefore possible to reconstruct the sequence of the forwarding processes at the respective receiver by means of control information SI1 additionally added in this way.

The respective coding of the header field value "forwarded-by-value" in messages of the MMS is carried out in particular according to the following principle:
Forwarded-By-Value = Integer-Value + Encoded-String-Value

This means that the Forwarded-By-Value is a field value assigned, which is formed by an integer positive number, which is the position of the field in a sequence of header fields determined (Integer-Value), and then one String that contains the address of the forwarding user (Encoded String Value).

Fig. 1, the forwarding illustrates a schematic representation of a multimedia message from a user application or output transmitting / receiving unit over a plurality of transmitting / receiving units or user applications of time. An MMS send request SA is first sent from a first MMS user application NA to a first MMS connection unit VA. An MMS delivery message ZN1 is then transmitted from the MMS connection unit VA to a further MMS connection unit VX. The latter then transmits an MMS recipient notification EB1 to a second MMS user application NG as the first recipient unit. This first receiver unit NG does not want to receive the multimedia message offered by the sending unit NA for sending itself, but rather only forward the delivery message, ie the offer to download the multimedia message, to at least one further MMS user application. For this purpose, the user application NG sends a forwarding request WL1 back to the MMS connection unit VX. This contains the address of the forwarding user application NG as information. The connection unit VX inserts this information into the delivery message ZN1, ie it forms the delivery message ZN2 to be forwarded by creating a first header field of the "X-Mms-Forwarded-By" type with the value "1 userG @ MMS service providerX" for the original control information (such as the sender address userA @ MMS service providerA) of the first delivery message ZN1. The connection unit VX then sends this extended delivery message ZN2 to a subsequent connection unit VE. The second connection unit VD sends a receiver notification EB2 to a further MMS user application NR as the second receiver unit according to the same principle as the first connection unit VX. The user application NR is informed about this that an MMS message is ready for retrieval at the sending unit NA. The user application NR also only forwards this request in the network by means of a forwarding request WL2 via the connection unit VD (and does not call up this multimedia message itself). The connection unit VD then generates a delivery message ZN3 and sends it to the subsequent MMS connection unit VT. It supplements the previous delivery message ZN2 with a further header field "X-Mms-Forwarded-By" with the value "2 usersR @ MMS service provider D", ie the delivery message ZN3 thus contains two header fields of the type "X-Mms-Forwarded-By""with the values" 1 userG @ MMS service providerX "and" 2 userR @ MMS service providerD ". The MMS connection unit VT in turn sends a recipient notification EB3 to a further MMS user application ML as the third recipient unit. This sends a forwarding request WL3 back to the connection unit VT in an analogous manner to the user application NG and user application NR. The latter then sends a delivery message ZN4 to at least one further MMS connection unit, which is indicated in FIG. 1 by three continuation points. The connection unit VT supplements the delivery message with a third header field of the "X-Mms-Forwarded-By" type with the value "3 UserL @ MMS service provider T". The MMS delivery message ZN4 then contains a total of three header fields of the "X-Mms-Forwarded-By" type with the values "1 userG @ MMS service providerX", "2 userR @ MMS service providerD" and "3 userL @ MMS service providerT ". Here in the exemplary embodiment, the recipient delivery message runs through a total of four MMS connection units, each with an associated MMS user application. The recipient delivery message is routed through the chain of MMS connection units. An MMS recipient delivery message is therefore sent from an MMS connection unit to an MMS user application which has previously been forwarded by four other users of the service. Based on the WAP implementation of MMS, the corresponding message is advantageously encoded as follows (only the header fields of the message are shown in the example here):

Recipient delivery message (in WAP: M-Retrieve.conf) MMS connection unit → MMS user application)

X-Mms-Message-Type: m-retrieve-conf

X-Mms-Transaction-ID: TRANSACTION-ID # 3

X-Mms version: 1.0

Date: Fri, August 24, 2001 13: 07: 00 +0100

From: UserA @ MMS service providerA

To: UserB @ MMS service providerB

X-Mms-Forwarded-By: 1 UserG @ MMS service providerX

X-Mms-Forwarded-By: 3 usersL @ MMS service providerT

X-Mms-Forwarded-By: 4 usersK @ MMS service providerZ

Subject: Quadruple forwarded multimedia message X-Mms-Forwarded-By: 2 usersR @ MMS service providerD

Content-Type: Application / *

• 1. NutzerG@MMS-DienstanbieterX
• 2. NutzerR@MMS-DienstanbieterD
• 3. NutzerL@MMS-DienstanbieterT
• 4. NutzerK@MMS-DienstanbieterZ

weitergeleitet wurde. The header field "X-Mms-Forwarded-By" is contained four times in the same message, here recipient delivery message. From the markings in the header fields it can be seen that the message is in the order

• 1. UserG @ MMS service providerX
• 2. UserR @ MMS service providerD
• 3.UserL @ MMS service providerT
• 4. UserK @ MMS service providerZ

was forwarded.

For this statement, the order of the header fields in the The message header and its position are therefore irrelevant. In terms of content, nothing changes in the statement if the Position of header fields within the head is changed.

The additionally inserted data elements with the addresses of the Forwarding user applications can also be in the Inquiry and notification signals in communication traffic between the respective connection unit and their respective assigned user application in a corresponding manner be included.

In this way, a Logging of a message carried out accordingly in what order they are from User applications or recipients has been forwarded. On this way it is in between and especially with that MMS user application that is actually the one of a Wants to retrieve the group application held ready, possible a chronological assignment from previously surveyed user applications from the recipient notification read and evaluate. This marking will an evaluation of delivery messages for each receiving user application facilitated. Because through the additional Identification of the order of data elements of the same name, that of such a delivery message after going through a User application is added each time, their reference can be subsequently reconstructed to each other and thus a selective evaluation and / or further processing be carried out at the receiving end.

In particular, it may be appropriate to use the labeling in such a way that in an added header field value in addition to the coded useful information, also a numerical value or a combination of letters and / or any other coding is encoded which is an order of Headers of the same type. Based on this determined Those contained in the header fields can order User information from the respective recipient of the message in a corresponding order can be brought afterwards. This Order can z. B. a chronological order, a logical one Order, a causal order, an order of Priority, a spatial assignment or any be another consequence. In particular, the importance of Order using the definition of one or more header fields be determined. The same applies to the type and Meaning of the mark of order. That way it especially for the receiving element or the receiving user application that enables the have actually delivered the provided group message wants to have previously made requests from others Read user applications from the received delivery message. In particular, this can be the history of a delivery message lived through on their way through a data communication network has recorded in a clear and selective manner be made evaluable.

This type of data transmission is preferably expedient in a radio communication system. This can preferably be designed according to the so-called UMTS standard (Universal Mobile Telecommunication System). The user applications can be implemented in particular in subscriber devices of this radio communication system. Subscriber device is preferably understood to mean a mobile radio device that is mobile in the radio cells of such a radio communication network. User applications corresponding to FIG. 1 may additionally be provided in a corresponding manner in the network components of such a radio communication system. Network components are in particular base stations and their associated higher-level radio network control units such as B. RNC (Radio Network Controller). Accordingly, this data transmission principle can also be used in a GPRS radio communication system (general package radio service).

Claims (8)

1. A method for data transmission in a data communication network, in particular text and / or image data with and without sound, characterized in that the respective data signal (ZN1, ZN2) is assigned at least one control information item (SI1) in at least one additional data element (DE1) that contain an identification of the order of data elements of the same name. 2. The method according to claim 1, characterized, that the respective data signal (ZN2) a variety of Has data elements. 3. The method according to any one of the preceding claims, characterized, that the order is a chronological order, an order of importance, a causal order, a logical order, a spatial order, or the like. 4. The method according to any one of the preceding claims, characterized, that the identification of the order by numbers, by Letters, by combinations of numbers and letters, and / or is realized by symbols and signs that are suitable as a basis for a comparison operation. 5. The method according to any one of the preceding claims, characterized, that the data elements within one or more Data signals (EB1) can be arranged freely. 6. The method according to any one of the preceding claims, characterized, that the UMTS standard for the data communication network (Universal Mobile Telecommunication System) is selected. 7. Sending / receiving unit of a data communication network, to carry out the method according to one of the preceding claims is formed. 8. Radio communication system with at least one Transceiver unit according to claim 7.