WO2003105402A1 - Verfahren und system zum übertragen von datenpaketen - Google Patents
Verfahren und system zum übertragen von datenpaketen Download PDFInfo
- Publication number
- WO2003105402A1 WO2003105402A1 PCT/DE2003/001820 DE0301820W WO03105402A1 WO 2003105402 A1 WO2003105402 A1 WO 2003105402A1 DE 0301820 W DE0301820 W DE 0301820W WO 03105402 A1 WO03105402 A1 WO 03105402A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- receiver
- transmitter
- data packet
- sent
- timer
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/27—Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
Definitions
- the present invention relates to a method and a system for transmitting data packets.
- Such methods and systems are used, inter alia, in mobile radio networks.
- the so-called multicast transmission is a better option.
- the various subscribers to whom the same message is to be transmitted are combined to form a group (multicast group) and this is assigned only one address (multicast address).
- the data to be transmitted are then only sent once to this multicast address.
- the multicast messages are only sent once over common connection paths from the sender to the receivers.
- the transmitter does not have to know where and how many recipients are hidden behind the multicast address.
- To receive messages from a specific multicast group a subscriber must subscribe to this multicast group.
- broadcast area The area in which the messages are sent out is referred to as the broadcast area.
- the size of the broadcast area is determined by the network operator. Ideally, as with multicast, the message is only sent once via common connection paths.
- the disadvantage here, however, is that all participants within the broadcast area have the option of reading broadcast messages. In order to read only certain messages and to discard or filter others, participants can make the appropriate settings on their end devices. An explicit registration for a broadcast service is not required.
- Subscribers only want to pay for a service if they have actually received the messages from the service. If, due to transmission problems, certain data does not arrive at the mobile radio terminal, the subscriber may not be charged for it.
- a news service such as multicast or broadcast must therefore be sufficiently reliable.
- Such a required reliability can be guaranteed, for example, in that subscribers who have not received certain data send appropriate non-reception information back to the network and the subscribers are then retransmitted to the "lost" data of the message.
- the problem here is that such a multi-transmission, in order to guarantee the reception of data, is very complex, especially since this data is retransmitted to a whole group of participants, ie also to participants who have already received the data correctly.
- the multicast or broadcast The advantage achieved in terms of saving transmission capacity is lost again.
- a service such as broadcast or multicast, since the data is sent from the sender to the receiver without confirmation.
- future paid services the participants only want to pay for the data if they have actually received it.
- the method for transmitting data packets has the steps of sending a data packet from a sender to a receiver and sending a confirmation message for the receipt of the data packet from the receiver to the sender, a timer for checking the receipt of the confirmation message when the data packet is sent is started.
- the present invention is preferably used in a third generation mobile radio network, such as UMTS (Universal Mobile Telecommunications System).
- UMTS Universal Mobile Telecommunications System
- the transmitter is, for example, a UMTS base station connected to a network and the receiver is a UMTS mobile radio terminal.
- the data packets or the confirmation message can in principle be sent on the basis of any mobile radio standard.
- the timer determines the time between sending the data packet and confirmation via a confirmation delivery message or checks whether a confirmation message arrives at the sender within a predetermined time interval.
- data packets are no longer sent from the transmitter to the receiver if no confirmation message arrives at the receiver within a time window started by the timer. In such a case, it can be assumed that the data packets either did not arrive at the recipient or that the recipient does not send any confirmation messages back to the sender.
- the data packets are not billed if no confirmation message arrives at the receiver within a time window started by the timer.
- Users of the receiver who receive data packets from the transmitter only want to pay a fee for receiving data packets if the data packet was not only sent by the transmitter, but if they actually received it. It is possible that a sender has sent a data packet, but this e.g. never arrived at the receiver due to dead spots. In such a case, it is obvious that the user of the recipient does not want to pay any fees for the unused data packet. As a result, there is no charge in such a case.
- a status query is directed from the transmitter to the receiver if no confirmation message arrives at the receiver within a time window started by the timer.
- the status of the recipient can be checked by such a status query. If, for example, the recipient is no longer able to send confirmation messages to the sender, this can be determined using the status query. It is also conceivable that the end device of the user is manipulated in this way was that this no longer sends confirmation messages. As a result, no proof is provided that the data packet has actually been received by the terminal. In such a case, the status query can be used to check whether there is any manipulation.
- the timer when the sender receives a confirmation message, the timer is reset and the data packet is billed. This is the normal case. After receiving the confirmation message, the timer is reset and started again when a new data packet is sent. Since there is proof of correct receipt of the data packet by the recipient, the data packet can then be billed.
- a non-reception message is sent from the receiver to the transmitter.
- a data packet is not received correctly, i.e. if a data packet was not received completely or only partially by the receiver, a non-receive message is sent to the sender. In such a case, there will be no charge. It can be provided that the incorrectly transmitted data packet is sent again.
- a non-reception message is also sent from the receiver to the transmitter. In this case, too, there is no billing or the data packet that has not been received is sent again.
- the number of received non-reception messages is stored in the transmitter.
- the number of non-receive messages received is a measure of incorrectly transmitted data packets. If there are too many incorrectly transmitted data packets, the sender must check whether this is a basic ches problem or whether there is tampering with the recipient.
- a status query is directed from the transmitter to the receiver. This status query can in turn be used to check why a number of non-reception messages above the predetermined limit value was sent to the transmitter.
- the task set at the outset is also achieved by a system for transmitting data packets with means for sending a data packet from a sender to a receiver and means for sending a confirmation message for the receipt of the data packet from the receiver to the sender, wherein a timer sends the data packet is started to check the receipt of the confirmation message.
- the present invention further relates to a terminal for use in a method according to the invention and a terminal for use in a system according to the invention.
- the terminal is preferably a mobile radio terminal.
- the recipient sends the network an acknowledgment of receipt upon receipt of data packets.
- the sender is notified of the correct receipt of the data at the receiver.
- the recipient will then be charged accordingly.
- the acknowledgment of receipt will preferably also be sent back to the network after receipt of a related set of data packets, since an incomplete data record may no longer be decipherable and thus has no value for the subscriber.
- the confirmation information can either be either be transmitted back to the transmitter via receiver-specific or shared channels.
- the sender After receiving an acknowledgment of receipt, the sender knows that the data has been received by the participants. Accordingly, the service can be billed to the subscriber. If the sender does not receive an acknowledgment of receipt, the transmitted data of the service will not be charged to the subscriber. It must be ensured that a recipient cannot be manipulated in such a way that it never sends an acknowledgment of receipt, since in this case the subscriber could receive the service free of charge. Under certain conditions, a request about the status or status of the receiver can be sent for this, why no reception information can reach the transmitter anymore.
- a receiver makes sense for a receiver to send a confirmation message back to the sender when the reception is correct, and to send a non-reception message back to the sender if the reception is incorrect.
- This non-receipt message then has the effect that the data are not invoiced to the subscriber. It must be ensured that a recipient does not always only send non-receive messages back to the sender and that the subscriber can therefore receive the service free of charge. For this purpose, a request about the status or status of the recipient can be sent under certain conditions, inquiring why the recipient only sends non-received messages.
- Figure la is a flowchart of a correct flow of a
- FIG. 1b shows a flowchart of an incorrect transmission of a data packet
- Figure 2 shows an embodiment of a transmission of several
- FIG. 1 shows a correct transmission of a data packet P3 from a transmitter S to a receiver E.
- a timer is started in the transmitter S.
- the receiver E receives the data packet P3.
- the receiver E sends a confirmation message 2 to the transmitter S, which is received by the transmitter S at the time tx.
- the time tx lies before the end of the time window t2 started by the timer, which is defined by the time tl, i.e. the sending of the data packet P3 is predetermined.
- Figure lb shows an incorrect transmission of a data packet P3 from a transmitter S to a receiver E.
- tl i.e. at the point in time at which the data packet P3 is sent by the transmitter S, a timer is again in the
- FIG. 2 shows a transmission of a series of data packets from a transmitter S to a receiver E.
- a message consisting of the data packets P1 to P10 is transmitted to a group of receivers via broadcast or multicast becomes.
- the data are transmitted across all receivers common channels (resources).
- To the confirmation and Sending non-confirmation information back to the network uses either dedicated or shared channels.
- only the transmitter S and a receiver E are considered in the exemplary embodiment shown in FIG. The statements apply equally to each of the recipients of the same message.
- the transmitter S begins with the transmission of the data packets 1 to 10 and sends them successively to the recipient (s).
- the data packet P3 is sent from the transmitter S to the receiver E.
- the latter confirms receipt by sending a confirmation message 11 to the transmitter S.
- a timer (not shown) is started until the confirmation information is expected to expire. Comes in this time interval, i.e. until the end of the time interval specified by the timer, an acknowledgment from the receiver E, the timer is stopped and the transmission of the data is charged accordingly. If the recipient E does not send a confirmation message before the timer expires, the data will not be charged to the subscriber.
- a so-called send window can be set up on the network side.
- Such a window must be managed in the transmitter for each receiver.
- the transmitter S is to transmit the data packets P1 to P10 to the receiver E.
- the transmitter S receives, for example, a confirmation message after the data packet P3 has been sent, and the send window is then "pushed on" in such a way that the start lies with the data packet P4 and the end with the data packet P7. If the sender S does not receive a confirmation message after sending the packet P4, the transmission window is not moved on. The start of the send window remains with the data packet P4.
- the data packets P5, P6 and P7 are then transmitted, even if no confirmation messages are sent to the receiver E. After the transmission of the data packet P7 and assuming that no further confirmation message has been transmitted, the end of the transmission window has been reached.
- a timer is started after sending the data packet P7. As soon as this timer has expired and when the end of the transmission window has been reached, a request for the status or state of the receiver E is sent. It is asked why no confirmation messages have been sent. There is a possibility that the receiver is in a dead zone or cannot be reached for other reasons. In such a case, he should no longer be billed for the service. The send window can then be moved again until the beginning of the window is the last data packet sent.
- the recipient E has been manipulated in such a way that it never sends confirmation messages, this can be determined via the sent request, in which case the subscriber can be deprived of the right to receive messages to recieve. This can be done, for example, by the network initiating an alert from the recipient group or, for example, by withdrawing the key for decrypting the messages.
- the transmitter S receives a confirmation message again before the timer expires, the timer is reset, the transmission window is shifted (by one position) and the next data packet (P8) can be transmitted. In this case, no request about the status of the end device is sent.
- the send window can be moved again until the start of the window lies with the packet currently being sent.
- a counter can be set up on the transmitter side, which counts the number of successive non-received messages. For this purpose, such a counter is managed in the transmitter S per receiver.
- the mode of operation is similar to the method of the transmission window described above, with the number of consecutive non-reception messages now being counted and then for a given one freely selectable meter reading a request about the status or the state of the terminal E is sent.
- the receiver is in a dead zone or that data transmission is not possible for other reasons.
- the recipient should no longer be billed for the service.
- the counter can be reset to zero.
- the recipient is manipulated in such a way that it only sends non-receive messages, this can be determined via the sent request.
- the subscriber can then be deprived of the right to receive the messages. This can again be done, for example, by a network-initiated message from the recipient group or by the withdrawal of the key for decrypting the messages.
- the counter is not increased further and the next data packet can be transmitted. No request about the status of recipient E is sent. If correct confirmation messages are subsequently received again for all packets, the counter is reset to zero.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Communication Control (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2003243911A AU2003243911A1 (en) | 2002-06-05 | 2003-06-02 | Method and system for transmitting data packets |
EP03756960A EP1510038A1 (de) | 2002-06-05 | 2003-06-02 | Verfahren und system zum übertragen von datenpaketen |
US10/516,775 US20060164994A1 (en) | 2002-06-05 | 2003-06-02 | Method and system for transmitting data packets |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE10224994A DE10224994A1 (de) | 2002-06-05 | 2002-06-05 | Verfahren und System zum Übertragen von Datenpaketen |
DE10224994.6 | 2002-06-05 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2003105402A1 true WO2003105402A1 (de) | 2003-12-18 |
Family
ID=29557557
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/DE2003/001820 WO2003105402A1 (de) | 2002-06-05 | 2003-06-02 | Verfahren und system zum übertragen von datenpaketen |
Country Status (6)
Country | Link |
---|---|
US (1) | US20060164994A1 (de) |
EP (1) | EP1510038A1 (de) |
CN (1) | CN1659823A (de) |
AU (1) | AU2003243911A1 (de) |
DE (1) | DE10224994A1 (de) |
WO (1) | WO2003105402A1 (de) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7716289B2 (en) * | 2002-10-17 | 2010-05-11 | At&T Intellectual Property I, L.P. | Transferring instant messaging (IM) messages |
US20040078445A1 (en) * | 2002-10-17 | 2004-04-22 | Malik Dale W. | Forwarding instant messaging (IM) messages |
JP2005079647A (ja) * | 2003-08-28 | 2005-03-24 | Toshiba Corp | 通信制御装置、通信システム及び通信制御方法 |
US8180840B2 (en) * | 2003-10-14 | 2012-05-15 | At&T Intellectual Property I, L.P. | Automatically replying to instant messaging (IM) messages |
WO2021056154A1 (zh) * | 2019-09-23 | 2021-04-01 | Oppo广东移动通信有限公司 | 一种窗口调整方法及装置、网络设备、终端设备 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2000079494A1 (en) * | 1999-06-22 | 2000-12-28 | Andrew Mark Stringer | Computer network payment system |
EP1128591A2 (de) * | 1995-01-19 | 2001-08-29 | Starburst Communications Corp. | Methode zur Mehrfachaussendung in Netzwerken mit ARQ zur Vermeidung unnötiger Wiederholungsübertragungen |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7237007B2 (en) * | 2001-12-05 | 2007-06-26 | Qualcomm Incorporated | Method and system for flow control between a base station controller and a base transceiver station |
US7860806B2 (en) * | 2002-03-12 | 2010-12-28 | Nokia Corporation | System and method for charging for data reception |
-
2002
- 2002-06-05 DE DE10224994A patent/DE10224994A1/de not_active Withdrawn
-
2003
- 2003-06-02 CN CN038128977A patent/CN1659823A/zh active Pending
- 2003-06-02 US US10/516,775 patent/US20060164994A1/en not_active Abandoned
- 2003-06-02 AU AU2003243911A patent/AU2003243911A1/en not_active Abandoned
- 2003-06-02 WO PCT/DE2003/001820 patent/WO2003105402A1/de not_active Application Discontinuation
- 2003-06-02 EP EP03756960A patent/EP1510038A1/de not_active Withdrawn
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1128591A2 (de) * | 1995-01-19 | 2001-08-29 | Starburst Communications Corp. | Methode zur Mehrfachaussendung in Netzwerken mit ARQ zur Vermeidung unnötiger Wiederholungsübertragungen |
WO2000079494A1 (en) * | 1999-06-22 | 2000-12-28 | Andrew Mark Stringer | Computer network payment system |
Non-Patent Citations (3)
Title |
---|
SANJOY PAUL ET AL: "RELIABLE MULTICAST TRANSPORT PROTOCOL (RMTP)", IEEE JOURNAL ON SELECTED AREAS IN COMMUNICATIONS, IEEE INC. NEW YORK, US, vol. 15, no. 3, 1 April 1997 (1997-04-01), pages 407 - 420, XP000683937, ISSN: 0733-8716 * |
TANENBAUM A S: "Computer Networks, PASSAGE", COMPUTER NETWORKS, LONDON: PRENTICE-HALL INTERNATIONAL, GB, 1996, pages 203 - 219, XP002227656, ISBN: 0-13-394248-1 * |
TANENBAUM S: "Computer Networks, THE TRANSPORT LAYER", COMPUTER NETWORKS, LONDON: PRENTICE-HALL INTERNATIONAL, GB, 1996, pages 536 - 542, XP002233582, ISBN: 0-13-394248-1 * |
Also Published As
Publication number | Publication date |
---|---|
DE10224994A1 (de) | 2003-12-18 |
EP1510038A1 (de) | 2005-03-02 |
US20060164994A1 (en) | 2006-07-27 |
CN1659823A (zh) | 2005-08-24 |
AU2003243911A1 (en) | 2003-12-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE60033539T2 (de) | Mehrfachübertragungsverfahren und system | |
DE3638675A1 (de) | Rechnergestuetztes schulungssystem und verfahren zur wirtschaftlichen rechnergestuetzten schulung | |
DE19848340A1 (de) | Lokales Netzwerk mit Brücken-Terminal zur Übertragung von Daten zwischen mehreren Sub-Netzwerken | |
DE19639845C1 (de) | Lokales Netzwerk mit Sende- und Empfangsvorrichtung | |
WO2007128693A1 (de) | Verfahren zum ermöglichen einer steuerung der dienstqualität und/oder der dienstvergebührung bei telekommunikationsdiensten | |
DE60026006T2 (de) | System zum Empfang von Mehrfachdaten | |
EP1273138B1 (de) | Verfahren zum übertragen breitbandiger ip-basierter datenströme in einem punkt-zu-mehrpunkt-kommunikationsnetz | |
EP1519598B1 (de) | Senden einer Information (NACK) von einem Teilnehmer-Endgerät bezüglich des Empfangs eines Datenblocks in einem Punkt-zu-Multipunkt-Funkübertragungssystem | |
EP0020893B1 (de) | Funknetz | |
WO2003105402A1 (de) | Verfahren und system zum übertragen von datenpaketen | |
EP0996259A2 (de) | Automatische Konfigurierung eines Brücken-Terminals zur Uebertragung von Daten zwischen mehreren Sub-Netzwerken in einem lokalen Netzwerk | |
DE673407C (de) | Schaltungsanordnung zur Verbindungszaehlung in Fernschreibvermittlungsanlagen mit Waehlerbetrieb | |
DE3236130A1 (de) | Schaltungsanordnung fuer fernmeldeanlagen, insbesondere fernsprechvermittlungsanlagen mit zentralen informationsverarbeitungseinrichtungen mit ueberlastsignalaussendung | |
DE102006024707B3 (de) | Verfahren und Anordnung zum Aufbau von Kommunikationsbeziehungen | |
EP1452002B1 (de) | Verfahren und system zur übertragung von nicht explizit angeforderten daten in einem mobilfunksystem | |
WO2005112330A1 (de) | Verfahren, sende- sowie empfangseinrichtung zur übertragung von digitalen informationspaketen in einem datennetz | |
DE10225428A1 (de) | Verfahren zur Übertragung von Daten | |
DE102008003588B4 (de) | Verfahren zur Broadcasting-Übertragung von in Datenpaketen angeordneten Informationen | |
DE102006018483B4 (de) | Verfahren zur Übertragung von Daten über die DECT-Luftschnittstelle | |
DE102009016094A1 (de) | Begrenzung der Datenübertragungsrate für eine Datenverbindung in einem Mobilfunksystem | |
DE19852276C2 (de) | Verfahren zum Empfang einer Nachricht über einen seriellen Datenbus, Funktionseinheit und lokales Netzwerk | |
EP1615374B1 (de) | Verfahren zum Senden und Empfangen von Ereignismeldungen | |
EP1128630A2 (de) | Verfahren zur Übertragung von Informationen an einen Empfänger | |
EP4195552A1 (de) | Verfahren zum übermitteln eines nachrichteninhalts mittels einer mehrzahl von broadcast-nachrichten, telekommunikationsnetz oder system zum übermitteln eines nachrichteninhalts mittels einer mehrzahl von broadcast-nachrichten, kommunikationsteilnehmer, insbesondere sender oder empfänger, computerprogramm und computerlesbares medium | |
EP2278758B1 (de) | Prioritätsbasiertes Kommunikationsnetzwerk und Kommunikationsverfahren |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2003756960 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2006164994 Country of ref document: US Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10516775 Country of ref document: US Ref document number: 20038128977 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2003756960 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: JP |
|
WWP | Wipo information: published in national office |
Ref document number: 10516775 Country of ref document: US |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 2003756960 Country of ref document: EP |