EP1552649B1 - Transfert de données multidestinations - Google Patents

Transfert de données multidestinations Download PDF

Info

Publication number
EP1552649B1
EP1552649B1 EP03808814A EP03808814A EP1552649B1 EP 1552649 B1 EP1552649 B1 EP 1552649B1 EP 03808814 A EP03808814 A EP 03808814A EP 03808814 A EP03808814 A EP 03808814A EP 1552649 B1 EP1552649 B1 EP 1552649B1
Authority
EP
European Patent Office
Prior art keywords
file
host
group
data packets
hosts
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP03808814A
Other languages
German (de)
English (en)
Other versions
EP1552649A1 (fr
Inventor
Janne Aaltonen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Oyj
Original Assignee
Nokia Oyj
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Oyj filed Critical Nokia Oyj
Publication of EP1552649A1 publication Critical patent/EP1552649A1/fr
Application granted granted Critical
Publication of EP1552649B1 publication Critical patent/EP1552649B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1881—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with schedule organisation, e.g. priority, sequence management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0093—Point-to-multipoint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]

Definitions

  • the invention relates to the simultaneous delivery of information to multiple hosts.
  • the invention relates to an apparatus and method for transferring text, audio, video or other data to multiple hosts in a communication system.
  • Unicast is a point-to-point delivery mechanism, where a source transmits a separate stream of data for each user.
  • the volume of data transmitted increases linearly with the number of users, leading to the consumption of an unacceptably high level of resources where the number of recipients is large.
  • the remaining two categories define point-to-multipoint or multipoint-to-multipoint delivery mechanisms. Broadcasting refers to the transmission of data to all hosts on a network. While this may work well in small networks, it requires the replication of a large number of data packets when used in a wide area network with many users. Furthermore, this method can be wasteful where the data is not of interest to a significant proportion of the recipients.
  • the third category is multicasting, which is the simultaneous transmission of data to a select group of users.
  • Multicasting has particular application in fields requiring streaming of content to multiple users in real time, such as news feeds, online gaming, Digital Video Broadcasting (DVB) and videoconferencing. Overviews of this technique are given in “ Multicast Networking and Application” by C. Kenneth Miller, Addison-Wesley 1988 [ISBN 0-201-30979-3 ] and in “ Deploying IP MULTICAST in the Enterprise” by T. Maufer, Prentice Hall PTR, 1998 [ISBN 0-13-897687-2 ].
  • the use of multicasting in a cellular radio access network is discussed in “ Multimedia Broadcast/ Multicast Service", 3rd Generation Partnership Project Technical Specification 3GPPTM TS 22.146 v1.0.0 2001 .
  • FIG. 1 is a block diagram of a prior communication system 1, for multicasting information from a content provider, i.e., host 2, to a plurality of receiver hosts 3 via a first network 4, such as the Internet, and a radio access network 5.
  • a data path 6 through the Internet 4 is depicted as extending directly from the content provider 2 to a router 7 without intervening stages, such as other transmitters, routers or servers, which may be located between these nodes.
  • Data paths leading from the content provider 2 to the receiver hosts 3a-3c diverge at the router 7. Situations where this divergence occurs include those where the receiver hosts 3 do not belong to the same sub-network, where the receiver hosts 3 are served by different transmitters 8 or where the radio access network 5 is not multicast enabled.
  • the content provider 2 provides a single data stream 6, which is transmitted over the Internet 4 to the point at which the paths to the individual receiver hosts 3a, 3b diverge, which in this example comprises the router 7.
  • the data stream of packets is replicated for onward transmission to the receiver hosts 3a, 3b individually, the router 7 being multicast-enabled in order to carry out the replication of the data.
  • other routers not shown in the network are also multicast enabled so that the data can be multicast to other receiver hosts individually.
  • the router 7 copies incoming data packets A-E, producing duplicate data streams 9a, 9b for transmission to the receiver hosts 3a, 3b.
  • the content provider 2 transmits only a single data stream 6, the use of its system resources and the network load are reduced when compared with a unicast system. Furthermore, as the transmission of replicated data is kept to a minimum, multicasting may be used in wide area networks where broadcasting is unfeasible.
  • a content provider has a reserved bandwidth for delivering a predetermined service to a group of end-users.
  • the second type allows end-users to select the service provided to them.
  • a user can receive the multicast stream of data by submitting a request to join the group by sending a message to the content provider in a format specified by the Internet Engineering Task Force (IETF). The user can leave the multicast group by submitting a corresponding request.
  • IETF Internet Engineering Task Force
  • Multicasting is a suitable mechanism for providing end-users with a continuous service but has limited applicability for "one-shot" transmissions.
  • a group of users may require the delivery of a file, for example, a multimedia clip, a web page, an mp3 file, a document or a software module for an application or a game.
  • the users of receiver hosts 3a, 3b may both request the file, which comprises data packets A-E, from the content provider 2.
  • the data packets are copied and forwarded to a radio transmitter 8, which transmits the encapsulated data packets to receiver hosts 3a, 3b as data streams 9a, 9b over a wireless network.
  • Prior systems have addressed this problem by defining a schedule of forthcoming transmissions.
  • a user can subscribe to a delivery list for a particular file, or set of files, and receive the relevant data at the next scheduled opportunity.
  • this delivery mechanism does not respond directly to the user's requirements and is inflexible as, again, once the file delivery transmission has begun, any other further users requiring the same file are excluded and must subscribe to the next scheduled transmission.
  • a host 3b may drop one or more packets or, having received the first data packets A-C, become unable to receive the remaining packets D, E in a file delivery transmission.
  • the host 3b cannot make use of the data packets it has received and, in order to receive the entire file, data packets A-E, must wait for file delivery transmission, which may necessitate joining another multicast group.
  • a mobile device receiving the data packets over a cellular communications network may be located in a first cell when joining the group and move into a different cell during the file delivery transmission. The mobile device cannot receive the remaining data packets in the file delivery transmission as the mobile device is no longer in the first cell.
  • software updates can be downloaded by multiple network terminations in a connectionless manner.
  • a fixed infrastructure broadcasts information regarding a channel over which fragments of a software file is to be sent and a group identity corresponding to the network terminations that require said software. The information is re-broadcast periodically and the transmission of the fragments is repeated to allow network terminations that did not receive the initial broadcast information to obtain the software file.
  • An object of the invention is to provide multicast file delivery in a manner that is more responsive to users' needs, with particular application to scalable multicasts such as unidirectional IP multicasts.
  • the invention has particular advantages in systems for transferring data to mobile devices comprising a cellular telecommunications network where a user may move between cells during the course of data transmission.
  • Another object of the invention is to provide efficient use of the air interface bandwidth.
  • a network element comprises a first logical interface for receiving a file from a content provider, a second logical interface for forwarding said file to one or more hosts as a sequence of data packets in a first file delivery transmission and to re-transmit said file to one or more hosts as a sequence of data packets in a second file delivery transmission, and a processor arranged to define a group of one or more hosts, wherein said network element is configured to transmit the file to the group so that a further host may start to receive the sequence of data packets during the first file delivery transmission, thereby receiving the remaining data packets in said first file delivery transmission, said network element being multicast enabled, so that the first and second file delivery transmissions are multicast transmissions, the network element being arranged to limit the group to hosts situated within a single locational area and the network element being arranged to receive a request to join the group from said further host during the first file delivery transmission and, if said further host is within said locational area, to transmit to said further host a start packet to
  • a method comprises receiving at a network element a request for the file from a first host, retrieving the file from a content provider, defining a group comprising the first host, forwarding the file to the group as a sequence of data packets in a first file delivery transmission over a network, wherein the group is limited to hosts within a same locational area as the first host, receiving a request from a further host to join said group, if said further host is within said locational area, responding to the request by adding said further host to a group for receiving the file, and transmitting to said further host a start packet to establish a connection between the network element and said further host, starting to transmit the data packets to the further host during said first file delivery transmission via said connection, so that said further host receives the remaining data packets in said first file delivery transmission, and forwarding the file to the group as a sequence of data packets in a second file delivery transmission over the network, the first and second file delivery transmissions being multicast transmissions.
  • a computer program comprising program instructions for causing a network element to perform such a method may be provided.
  • Various embodiments of the invention allow a user to join a group, receive the remaining data packets in an ongoing file transmission and receive any missed data packets in the subsequent file transmission. Therefore, the time period between the submission of a file request from a host and the completion of the file delivery is approximately the same for all hosts, although there will be small delays caused by the server sending additional packets for configuring connections. This compares favourably with the time period experienced in prior queuing systems, where the a host might have to wait until a previous file delivery transmission has been completed, and can lead to improved data transmission rates and a quality of service that can be guaranteed.
  • the ability to join ongoing transmissions and receive the remaining data packets in a sequence assists in efficient delivery of a file where data packets have been missed or dropped, or where the file delivery path to a receiver host changes during the transmission.
  • Figure 2 depicts an embodiment of a communication system 10 for multicast file delivery comprising a multimedia content provider 2, receiver hosts 3a-3c, a server 7, which includes means for performing the functions of a router, a radio transmitter 8 and a cache 11.
  • the data paths leading from the content provider 2 to the receiver hosts 3a-3c have a common portion 6 extending between the content provider 2 and the server 7 over the Internet 4 and diverge at the server 7, which is the last network element in the data paths to the individual receiver hosts 3a-3c before an air interface.
  • the data path 6 may include further elements, such as other transmitters, routers or servers, which may be located between the content provider 2 and server 7.
  • receiver hosts 3a-3c are mobile devices belonging to a cellular wireless DVB-T wide area network (WAN) 5.
  • WAN wide area network
  • the three receiver hosts 3a-3c are situated in an area covered by a single DVB-T cell C1, which is defined by a cell boundary 12 and associated with the transmitter 8.
  • the area covered by the DVB-T cell C1 is used to define the location of the receiver hosts 3, so that, in this example, the receiver hosts 3a-3c have a common location.
  • the server 7 forwards the multicast data to the radio transmitter 8, which sends the data to the receiver hosts over the DVB-T network 5 in accordance with a suitable communication protocol.
  • Suitable protocols include, but are not limited to, the following protocols: Reliable Multicast Transport Protocol (RMTP), Reliable Multicast File Transfer Protocol (RMFTP), Asynchronous Layered Coding (ALC), NACK-Oriented Reliable Multicast (NORM), Pragmatic General Multicast (PGM), Tree Acknowledgement based protocol (TRACK), User Datagram Protocol (UDP) and Unidirectional Hypertext Transfer Protocol (UHTTP).
  • RMTP Reliable Multicast Transport Protocol
  • RFTP Reliable Multicast File Transfer Protocol
  • ALC Asynchronous Layered Coding
  • NAM NACK-Oriented Reliable Multicast
  • PGM Pragmatic General Multicast
  • TRACK Tree Acknowledgement based protocol
  • UDP User Datagram Protocol
  • UHTTP Unidirectional Hypertext Transfer Protocol
  • SAP Session Announcement Protocol
  • the DVB-T network 5 is used for unidirectional communication only, communications between the receiver host 3a and the server 7, including file requests (REQ), are made via an alternative communication system, such as a cellular telecommunications network 13.
  • an alternative communication system such as a cellular telecommunications network 13.
  • the transmission of file data over the Internet 4 or DVB-T network 5 is indicated using solid lines, while communication over the telecommunications network 13 is shown with dashed lines. It is possible that, while belonging to a single DVB-T cell C1, the receiver hosts 3a-3c may belong to different cells in the telecommunications network 13, or even to separate telecommunications networks, however, for simplicity, only a single telecommunications network 13 and associated transmitter 14 are depicted in the figures.
  • the server 7 receives a request for a file, such as a multimedia clip, or a popular song in mp3 format, from a receiver host 3a (step s1) via the telecommunications network 13.
  • the request from receiver host 3a includes information about its location, in terms of the DVB-T cell C1 in which the receiver host 3a is located.
  • the server 7 requests the file from the content provider 2 (step s2), which responds by transmitting the file to the server 7, together with an associated delivery message.
  • the delivery message includes information about the time the file was created and an indication of when it will next be updated.
  • the file and delivery message are stored in the cache 11.
  • the server 7 defines a group and sets up a corresponding file delivery list with entries that indicate receiver hosts 3 which have requested the file and are situated within that locational area, i.e. within an area covered by the same DVB-T cell C1 (step s3).
  • the list contains only one entry, relating to receiver host 3a, although if a request for the same file is received from another receiver host (step s4) during retrieval of the file, the server 7 would check whether the new receiver host is located within the same DVB-T cell C1 as the first receiver host 3a (step s5). If so, the new receiver host is added to the group at this stage by adding a corresponding entry to the file delivery list (step s6).
  • the server 7 may set up a separate file delivery list for that location or, where a file delivery list for the second location C2 already exists, add the new receiver host to the relevant list.
  • the server 7 sends a "start" packet ST to the first receiver host 3a via the radio transmitter 8 (step s7).
  • the start packet ST is also sent to any other receiver host currently in the group.
  • the start packet ST is associated with an application that carries out the "handshake" procedure for establishing a connection between the server 7 and receiver host 3a.
  • Some communication protocols e.g. NORM or PGM, require a receiver host 3a to send a negative acknowledgement (NACK) to the server 7 where a data packet has not been received or where a corrupted data packet has been received.
  • NACK negative acknowledgement
  • a negative acknowledgement is a message requesting the retransmission of one or more missed data packets.
  • the connection between the server 7 and receiver host 3a is configured so that a period of time is allowed by the receiver host 3a before a negative acknowledgement message or status report is sent to the server 7. This period of time is longer than the time taken to receive the entire file. The reasons for this will be described later.
  • the file is then retrieved from the cache 11 and arranged into data packets A-G according to the appropriate communication protocol.
  • the header information included in the data packets A-G includes information regarding its position in the order of the data packets within the file.
  • the server 7 begins to forward copies of the data packets in sequence to the radio transmitter 8, where they are encapsulated in an IP datagram and sent to the group (step s8).
  • the group contains only the first receiver host 3a at this stage.
  • the present multicast system allows further receiver hosts 3 to join the ongoing file delivery transmission. For example, if a file request from a second receiver host 3b is received (step s9) while the file delivery transmission to receiver host 3a is in progress, e.g., after data packets A, B have been sent to the first receiver host 3a, the server 7 responds by checking whether the second receiver host 3b is at the same location as the first receiver host 3a, i.e. whether receiver host 3b is located in the area covered by DVB-T cell C1 (step s10). If so, the second receiver host 3b is added to the group (step s11) and a start packet ST is sent to the second receiver host 3b in order to establish a connection (step s12).
  • the server 7 makes an entry in the file delivery list logging the next data packet A-G to be transmitted (step s13). This information is used to determine the point in the data packet sequence at which the second receiver host 3b joined the group. Subsequent data packets C-G are copied to the receiver hosts 3a, 3b in the group (step s8). As the data packet headers indicate their position in the data packet sequence, the second receiver host 3b, having missed the initial packets A, B can arrange the incoming data packets C-G in the appropriate order in its IP stack.
  • the server 7 will send a start packet ST to the third receiver host 3c and add the third receiver host 3c to the group by including a corresponding entry to the file delivery list.
  • the third receiver host 3c will receive data packets E-G during the ongoing file transmission.
  • the server 7 sends an "end" packet END to the receiver hosts 3a, 3b in the group (step s15), which indicates that the end of the data packet sequence has been reached.
  • the server 7 checks whether the delivery of the file to each of the hosts 3a-3c has been completed (step s16). For example, the log associated with the file delivery list may be checked, so that the various points in the data packet sequence where the receiver hosts 3a-3c joined the file delivery transmission can be used to determine whether any of the hosts 3a-3c require further data packets (step s16).
  • connection between the server 7 and each receiver host 3a-3c may be configured so that it is terminated by either the server 7 or the receiver host 3a-3c and/ or the server 7 may remove the entry corresponding to that receiver host 3 from the file delivery list when the complete sequence of data packets A-G has been received.
  • the server 7 may not be necessary to terminate the connection between the server 7 and receiver host 3a when the file delivery to that receiver host 3a has been completed, as it is common practice to configure the receiver hosts 3 to drop any duplicate packets it receives.
  • the server 7 then allows a period of time for the receipt of requests for missing packets from receiver hosts 3 that have not received the full sequence of data packets A-G. For example, in the situation shown in Figure 4 , the first receiver host 3a has received the complete sequence of data packets A-G, while the second and third receiver hosts 3b, 3c have received only part of the data packet sequence C-G and F-G respectively, along with the start and end packets, ST, END. If one or more receiver hosts 3b, 3c have not received the complete file, the server 7 continues to transmit the data packets A-G (step s8), beginning at the start of the data packet sequence. As described above, the receiver hosts 3b, 3c use the information in the data packet header regarding the position of the incoming data packet in the sequence to assemble the data packets in the correct order.
  • a receiver host 3 that did not receive a packet for any other reason, e.g., such as a problem with its connection to the server 7, can use the data packets sent in the retransmission of the file to complete the data packet sequence in its IP stack. For example, if receiver host 3b has received packet C, E-G but had dropped packet D, the receiver host 3b can retrieve both the missing packets A, B and the dropped packet D from a subsequent file retransmission before the expiry of the time period allowed by the receiver host 3b before sending a negative acknowledgement. The use of data packets from subsequent file retransmissions reduces the number of negative acknowledgements and resulting retransmissions of data packets to individual receiver hosts 3, thereby lessening network traffic.
  • the negative acknowledgement procedure would be used where a receiver host 3 has lost a packet in the final file transmission in the file delivery process due to transmission failure or corruption.
  • the receiver host 3a would send a negative acknowledgement message to the server 7 via the cellular telecommunications network 13 requesting retransmission of the missing packets on the expiry of the time period.
  • Any negative acknowledgements that are sent by one of the receiver hosts, e.g. host 3c, are multicasted via the server 7 and radio transmitter 8 to the other receiver hosts 3a, 3b. This avoids the sending of multiple negative acknowledgements by the receiver hosts in relation to the same data packet.
  • a receiver host 3 may also miss data packets due to its movement out of the locational area associated with the group, i.e. out of the DVB-T cell C1 used to define the group location. For example, during the retransmission of data packet A shown in Figure 4 , receiver host 3b may move over the cell boundary 12, in the direction of arrow 15, to another DVB-T cell C2, as shown in Figure 5 . While the server 7 will continue the file delivery transmission, transmitting data packets to receiver host 3c, receiver host 3b can no longer receive data stream 9b. After the expiry of the allowed time period, the receiver host 3b will send one or more negative acknowledgement messages relating to data packets A, B via communications system 13, which include information regarding its new location.
  • a server 7' associated with the new DVB-T cell C2 which treats the NACK as a request for the file.
  • the server 7' then follows the procedure of Figure 3 , by requesting the file from the content provider 2, receiving the file via the Internet 4 over data path 6', storing it in a cache 11', setting up a group associated with the location C2 of the receiver host 3b and transmitting the file via transmitter 8' as data stream 9b'.
  • the server 7' will add the receiver host 3b to that group.
  • the server 7 associated with the original DVB-T cell C1 could then delete the receiver host 3b from its group as, in the absence of any negative acknowledgement messages, the file delivery to receiver host 3b would be considered complete, as described above in relation to step s16.
  • the servers 7, 7', transmitters 8, 8' and caches 11, 11' may be physically provided as a single server 7, transmitter 8 and cache 11 configured to serve both cells C1, C2.
  • the file in cache 11 is deleted (step s17), completing the file delivery process (step s18).
  • the deletion of the file in the cache 11 may be delayed for a predetermined period of time after the completion of file delivery, in order to meet any further requests for the file without repeating the step of retrieving the file from the content provider 2 (step s2).
  • the server 7 checks whether a copy of the file is already stored in its cache 11 and uses the information in the delivery message to determine whether the file in cache 11 is the latest available version and whether it is necessary to retrieve an updated file from the content provider 2. This procedure may also be followed by the second server 7' mentioned above.
  • the server 7 comprises an input/output interface 16 for receiving data from the content provider 2 and input/output interfaces 17-19 for forwarding data to the receiver hosts 3a-3c.
  • the file requests are received via the input/output interface 16, where file requests are submitted via a telecommunications network 13, as in the figures, or via the Internet 4.
  • the wireless network 5 is used for bi-directional communication
  • the file requests may be received at interfaces 17-19.
  • the interfaces 16-19 and a number of other components are connected by a data bus 20 as follows.
  • a processor 21, with an associated clock 22, monitors and controls routing operations, including generating processes for establishing and releasing connections between the server 7 and receiver hosts 3a-3c.
  • a storage device 23 is provided for storing the server application software.
  • An address processor 24 extracts the address information from incoming data packets and uses this information to determine how each data packet is to be processed, e.g., whether an incoming packet is a request for a file from a receiver host 3a-3c or file data.
  • Incoming file data is stored in the cache 11, although the server may also have access to an external buffer for storing large files.
  • File requests are forwarded to a file request handler 25, which manages the copying of data packets A-G for transmission to the receiver hosts 3a-3c and the encryption of information relating to the correct order of the data packets A-G in the packet headers.
  • the file request handler 25 also maintains the file delivery list.
  • the receiver hosts 3 may be mobile telephone handset terminals, such as that shown in Figure 7 .
  • the mobile telephone handset terminal 26 comprises an antenna 27, a transceiver 28, a central processing unit (CPU) 29 and a battery 30.
  • the transceiver 28, which is, for example, a GSM, GPRS, 3G, or similar bi-directional transceiver, is connected to the antenna 27 and the CPU 29. Also connected to the CPU 29 are a receiver (DVB-T) 31, a keypad 32 and a display 33.
  • the terminal 26 also includes other conventional features of mobile telephone handsets, but these are omitted from Figure 7 for the sake of clarity.
  • the time interval between the submission of a file request by a receiver host and the receipt of the full sequence of data packets A-G should be the same for each of the receiver hosts 3a-3c, allowing for small differences due to the transmission of further start packets ST to other receiver hosts 3.
  • This predictability allows a service provider to guarantee the quality of service in terms of data transmission rates.
  • This time interval compares favourably with a unicast system, or the prior multicast system where the available window for further receiver hosts 3b, 3c to join an ongoing file delivery transmission is small. This provides potential efficiency gains as the likelihood that a data packet A in a file delivery transmission is sent to a single receiver host is decreased, which reduces the number of file delivery transmissions needed to accommodate a given number of receiver hosts 3.
  • Tables 1 and 2 The improvement in performance between the invention and a prior system to the receiver hosts during an example file delivery process is shown in Tables 1 and 2.
  • the tables relate to the transmission of a 10 Mbit file, where the file delivery transmission to receiver host 3a commences at 0 s.
  • the second and third receiver hosts 3b, 3c join the file delivery transmission at 10 s and 20 s respectively.
  • Tables 1 and 2 presumes that no packets are dropped in the transmission, i.e., the data for the time of file delivery completion t d is the minimum time for the reception of the complete sequence of data packets A-G by a receiver host 3.
  • the values of t d are also approximate as they do not include small delays caused by sending the receiver hosts 3 start and end packets ST, END.
  • Table 1 illustrates an example where the system allocates a bandwidth of 100 kbit/ s per user.
  • the available bandwidth is effectively shared between the receiver host 3a-3c. Therefore, as further receiver hosts 3a-3c are included in the file delivery transmission, the data transfer rate experienced by each of the receiver hosts 3a-3c increases.
  • the first receiver host 3a receives data at 100 kbit/ s over the time interval 0-10 s, i.e., until the second receiver host 3b joins the group. Data is then transferred to the receiver host 3a at 200 kbit/ s during the time interval 10-20 s.
  • each receiver host 3a-3c stops when the complete file has been received, i.e., that the data transfer rate drops to 200 kbit/ s at 43 seconds, as the receiver host 3a has left the group. If the server 7 is configured to continue transmitting data to receiver host 3a until each host in the group has received the complete sequence of data packets A-G, the data transfer rate and perceived bandwidth will remain at 300 kbit/ s.
  • receiver hosts 3a, 3b and 3c would receive the file 100 s, 190 s and 280 s respectively, from the time that the file request from each receiver host 3 is submitted.
  • the end users of the receiver hosts 3a-3c perceive bandwidths of 100 kbit/ s, 53 kbit/ s and 36 kbit/ s respectively.
  • the time between submitting a request and completing the file delivery is 43 s, 39 s and 49 s respectively, so that the receiver hosts perceive bandwidths of 233 kbit/ s, 256 kbit/ s and 204 kbit/ s.
  • Table 2 compares the file delivery times and bandwidths perceived by end-users of receiver hosts 3 for the prior queue-based system and a system according to the invention in which the total allocated bandwidth is constant.
  • Table 2 Prior System Present system User Time of Request (s) File Size (Mbit) Transfer Rate (kbit/s) t d (s) PBW (kbit/s) t d (s) PBW (kbit/s) 1 0 10 100 100 100 100 100 100 100 100 100 100 100 100 2 10 10 100 190 53 100 100 3 20 10 100 280 36 100 100 100
  • each of the receiver hosts 3a-3c receive the file in 100 s, without allowing for dropped packets and the extra start and end packets ST, END, sent during the first file delivery transmission.
  • Each receiver host 3a-3c perceives the total available bandwidth of 100 kbit/ s.
  • the invention has been described by way of an example and can be used for transferring data packets other than IP packets. While a point-to-multipoint transmission has been described, the invention may also be used for multipoint-to-multipoint data transfer.
  • the receiver hosts 3a-3c may be fixed or mobile devices, e.g., mobile telephones or personal digital assistants (PDAs). It is not necessary for the receiver hosts 3a-3c to belong to the same local network or for the location of the hosts to be defined in terms of cell coverage.
  • the server 7 it is not necessary for the server 7 to transmit data to the receiver hosts 3a-3c using a wireless communication system.
  • the embodiment described relates to a system comprising a WAN, however, the invention is equally applicable to LAN networks or any other multicast enabled network and may be used for the transfer of files over networks other than the Internet or a DVB-T network, e.g., over DVB-S (satellite), DVB-C (cable), DVB-M, other DVB variants, Integrated Services Digital Broadcasting (ISDB), ATSC Digital Television or Digital Audio Broadcasting (DAB) networks or in multicast-enabled General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Universal Mobile Telecommunications Systems (UMTS), Wireless Code Division Multiple Access (W-CDMA), CDMA2000 or Bluetooth systems.
  • DVB-T e.g., over DVB-S (satellite), DVB-C (cable), DVB-M, other DVB variants, Integrated Services Digital Broad
  • the cellular telecommunications network 13 is used merely as an alternative communication system to the wireless system 5.
  • a different system such as the Internet 4, could be used to convey requests and negative acknowledgements from the receiver hosts 3 to the server 7. If the wireless system 5 is bi-directional, the invention could be implemented using a single system to handle file delivery to the receiver hosts 3 and file requests.
  • the location associated with the groups was defined in terms of the area covered by a DVB-T cell C1.
  • the location may be defined differently, as required, for example in terms of the cells of the telecommunications network 13, depending on the requirements of the user or a service provider.
  • the described embodiment comprised a server 7 located at the air interface
  • the invention may be implemented at any network element, e.g., a server, node or router, along the path between a content provider 2 and receiver hosts 3a-3c, while the receiver hosts may be fixed or mobile devices, including mobile personal digital assistants (PDAs).
  • PDAs mobile personal digital assistants

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Databases & Information Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)

Claims (14)

  1. Elément de réseau (7) comprenant :
    une première interface logique (16) conçue pour recevoir un fichier d'un fournisseur de contenus (2) ;
    une seconde interface logique (17, 18) conçue pour transférer ledit fichier à un ou plusieurs hôtes (3a, 3b) sous la forme d'une séquence de paquets de données dans une première transmission de livraison du fichier et pour retransmettre ledit fichier vers un ou plusieurs hôtes sous la forme d'une séquence de paquets de données dans une seconde transmission de livraison du fichier ; et
    un processeur (21) conçu pour définir un groupe d'un ou plusieurs hôtes (3a, 3b) ;
    dans lequel ledit élément de réseau (7) est configuré pour transmettre le fichier au groupe de telle façon qu'un hôte supplémentaire (3c) puisse commencer à recevoir la séquence de paquets de données pendant la première transmission de livraison du fichier, en recevant ainsi les paquets de données restants dans ladite première transmission de livraison du fichier ;
    caractérisé en ce que :
    ledit élément de réseau (7) est optimisé pour la diffusion multidestinations, les première et seconde transmissions de livraison du fichier étant des transmissions multidestinations ;
    ledit élément de réseau (7) est conçu pour définir le groupe qui doit être limité à des hôtes situés dans une seule zone de localisation (C1) ;
    ledit élément de réseau (7) est conçu pour recevoir dudit hôte supplémentaire (3c) une demande de rejoindre le groupe pendant la première transmission de livraison du fichier et, si ledit hôte supplémentaire (3c) est dans ladite zone de localisation (C1), pour transmettre audit hôte supplémentaire (3c) un paquet d'amorce pour établir une connexion entre l'élément de réseau (7) et ledit hôte supplémentaire (3c) en réponse à ladite demande, de telle façon que l'hôte supplémentaire (3c) puisse recevoir des paquets de données pendant les première et seconde transmissions de livraison du fichier.
  2. Elément de réseau (7) selon la revendication 1, configuré en outre pour transmettre le fichier via un premier réseau de communication (5) et pour recevoir des hôtes des demandes de rejoindre le groupe via un second réseau de communication (13).
  3. Elément de réseau (7) selon la revendication 1 ou 2, dans lequel la demande et/ou le fichier est transmis entre l'élément de réseau (7) et les hôtes (3a, 3b) via un réseau de communication cellulaire (13) et la zone de localisation est définie en termes d'une cellule, de telle façon que le groupe soit limité à des hôtes (3a, 3b) situés dans une zone de localisation couverte par une seule cellule.
  4. Elément de réseau (7) selon la revendication 1, 2 ou 3, configuré en outre pour transférer le fichier à l'hôte (3a, 3b) via un réseau de communication sans fil (5), en constituant le dernier élément de réseau situé avant une interface radio dans un chemin de livraison du fichier entre le fournisseur de contenus (2) et l'hôte (3a, 3b).
  5. Elément de réseau (7) selon l'une quelconque des revendications précédentes, comprenant en outre un gestionnaire de demandes de fichiers (25) conçu pour chiffrer des informations dans des en-têtes des paquets de données concernant l'ordre exact des paquets de données dans les transmissions de livraison du fichier.
  6. Elément de réseau (7) selon l'une quelconque des revendications précédentes, configuré en outre de façon à consigner le moment dans la première transmission de livraison du fichier auquel l'hôte supplémentaire (3c) rejoint le groupe.
  7. Elément de réseau (7) selon l'une quelconque des revendications précédentes, configuré pour recevoir un message d'accusé de réception négatif et pour traiter ledit message comme une demande d'obtention du fichier.
  8. Procédé comprenant les étapes consistant à :
    recevoir au niveau d'un élément de réseau (7) une demande d'obtention d'un fichier émanant d'un premier hôte (3a) ;
    récupérer le fichier auprès d'un fournisseur de contenus (2) ;
    définir un groupe comprenant le premier hôte (3a) ;
    transférer le fichier au groupe sous la forme d'une séquence de paquets de données dans une première transmission de livraison du fichier via un réseau ;
    commencer à transmettre les paquets de données à un hôte supplémentaire (3c) pendant ladite première transmission de livraison du fichier, de telle façon que ledit hôte supplémentaire (3c) reçoive les paquets de données restants dans ladite première transmission de livraison du fichier ; et
    transférer le fichier au groupe sous la forme d'une séquence de paquets de données dans une seconde transmission de livraison du fichier via le réseau ;
    caractérisé en ce que :
    lesdites première et seconde transmissions de livraison du fichier sont des transmissions multidestinations ;
    ladite définition du groupe comprend la limitation du groupe à des hôtes (3a, 3b) situés dans une seule zone de localisation (C1) ;
    et caractérisé par les étapes consistant à : recevoir une demande dudit hôte supplémentaire (3c) de rejoindre ledit groupe pendant la première transmission de livraison du fichier ; et
    si ledit hôte supplémentaire (3c) se situe dans ladite zone de localisation, répondre à la demande en ajoutant ledit hôte supplémentaire (3c) au groupe et transmettre audit hôte supplémentaire (3c) un paquet d'amorce pour établir une connexion entre l'élément de réseau et ledit hôte supplémentaire (3c) de telle façon que les paquets de données dans les transmissions de livraison du fichier soient transmis à l'hôte supplémentaire (3c) via ladite connexion.
  9. Procédé selon la revendication 8, dans lequel le fichier est transféré via un premier réseau de communication (5) et la demande du premier hôte (3a) est reçue via un second réseau de communication (13).
  10. Procédé selon la revendication 8 ou 9, dans lequel une demande et/ou le fichier est transmis entre l'élément de réseau (7) et le premier hôte (3a) via un réseau de communication cellulaire (13) et la zone de localisation est définie en termes d'une cellule, de telle façon que le groupe soit limité à des hôtes (3a, 3b, 3c) situés dans une zone couverte par une seule cellule.
  11. Procédé selon la revendication 8, 9 ou 10, comprenant en outre l'étape consistant à chiffrer des informations dans des en-têtes des paquets de données concernant l'ordre exact des paquets de données dans les transmissions de livraison du fichier.
  12. Procédé selon l'une quelconque des revendications 8 à 11, comprenant en outre l'étape consistant à consigner le moment dans la première transmission de livraison du fichier auquel ledit hôte supplémentaire (3c) rejoint le groupe.
  13. Programme d'ordinateur comprenant des instructions de programmation pour faire exécuter par un élément de réseau (7) le procédé selon l'une quelconque des revendications 8 à 12.
  14. Programme d'ordinateur selon la revendication 13, mis en oeuvre sur un support lisible par ordinateur.
EP03808814A 2002-10-16 2003-09-24 Transfert de données multidestinations Expired - Lifetime EP1552649B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
GB0224076 2002-10-16
GB0224076A GB2394386A (en) 2002-10-16 2002-10-16 Multicast data transfer
PCT/IB2003/004309 WO2004036827A1 (fr) 2002-10-16 2003-09-24 Transfert de donnees multidestinations

Publications (2)

Publication Number Publication Date
EP1552649A1 EP1552649A1 (fr) 2005-07-13
EP1552649B1 true EP1552649B1 (fr) 2009-12-30

Family

ID=9946024

Family Applications (1)

Application Number Title Priority Date Filing Date
EP03808814A Expired - Lifetime EP1552649B1 (fr) 2002-10-16 2003-09-24 Transfert de données multidestinations

Country Status (9)

Country Link
US (1) US7801165B2 (fr)
EP (1) EP1552649B1 (fr)
KR (1) KR100683813B1 (fr)
CN (1) CN100571145C (fr)
AT (1) ATE453976T1 (fr)
AU (1) AU2003265058A1 (fr)
DE (1) DE60330790D1 (fr)
GB (1) GB2394386A (fr)
WO (1) WO2004036827A1 (fr)

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2406462A (en) * 2003-09-25 2005-03-30 Nokia Corp Multicasting apparatus
US20050185604A1 (en) * 2004-02-23 2005-08-25 Samsung Electronics Co., Ltd. Method and apparatus for transferring connectionless-oriented data packets
DE102004036497A1 (de) * 2004-07-28 2006-03-23 Siemens Ag Terrestrisches digitales Fernsehsystem und Verfahren zum Betrieb eines solchen
JP2006165928A (ja) * 2004-12-07 2006-06-22 Hitachi Ltd 移動体向けデータ配信支援方法
US20060126556A1 (en) * 2004-12-14 2006-06-15 Roundbox, Inc. Territory mapping for efficient content distribution in wireless networks using broadcast/multicast
CN1332574C (zh) 2005-02-25 2007-08-15 华为技术有限公司 一种在移动数据广播中实现定向广播的方法
CN1328868C (zh) * 2005-03-01 2007-07-25 广东省电信有限公司研究院 在分布式对等流媒体服务系统中实现可靠组播的方法
US20070002851A1 (en) * 2005-06-30 2007-01-04 Toni Paila Transmission and reception of session packets
KR100717240B1 (ko) * 2005-07-20 2007-05-11 엔에이치엔(주) 신뢰성 있는 시퀀스 제공 방법 및 시스템
GB2439379A (en) * 2006-06-12 2007-12-27 Robert Denzil Onslow Providing confirmation of the receipt of files sent over the Internet
CN100459549C (zh) * 2006-06-26 2009-02-04 华为技术有限公司 一种加入广播/多播业务服务方法及装置
US8271683B2 (en) * 2008-03-21 2012-09-18 International Business Machines Corporation Content push service
US7948991B1 (en) * 2008-05-09 2011-05-24 Cisco Technology, Inc. Broadcast and multicast transmissions with acknowledgement scheduling
US20100121914A1 (en) * 2008-11-11 2010-05-13 Sk Telecom Co., Ltd. Contents delivery system and method based on content delivery network provider and replication server thereof
JP5282693B2 (ja) * 2009-07-27 2013-09-04 株式会社リコー 画像形成装置、表示制御方法、及びプログラム
US8520694B1 (en) * 2009-07-31 2013-08-27 Sprint Spectrum L.P. Mobile handset power conservation using connection-release buffering
US8902852B2 (en) 2011-05-19 2014-12-02 Telefonaktiebolaget L M Ericsson (Publ) Inter-rat handover control using empty GRE packets
US8861475B2 (en) * 2011-05-19 2014-10-14 Telefonaktiebolaget L M Ericsson (Publ) Inter-RAT handover control using sequence numbers
KR101909666B1 (ko) * 2012-06-08 2018-10-19 삼성전자주식회사 모바일 컨텐츠 센트릭 네트워크에서 핸드오버를 위한 방법 및 장치
CN102724201A (zh) * 2012-06-25 2012-10-10 北京像素软件科技股份有限公司 网络游戏系统以及在网络游戏系统中进行数据多播方法
US9577791B2 (en) 2012-12-05 2017-02-21 Intel Corporation Notification by network element of packet drops
US8989017B2 (en) * 2012-12-14 2015-03-24 Intel Corporation Network congestion management by packet circulation
EP3063629A1 (fr) * 2013-10-28 2016-09-07 Longsand Limited Diffusion continue et instantanée de la dernière version d'un fichier
CN113472959A (zh) * 2020-03-31 2021-10-01 兄弟工业株式会社 图像处理装置、服务器、以及图像处理装置的控制方法和只读存储器

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0959635A1 (fr) * 1998-05-20 1999-11-24 Alcatel Téléchargement de logiciel vers des terminaux sans fil en mode sans connexion

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5553083B1 (en) * 1995-01-19 2000-05-16 Starburst Comm Corp Method for quickly and reliably transmitting frames of data over communications links
US6453438B1 (en) * 1995-01-19 2002-09-17 The Fantastic Corporation System and method for automatically rescheduling a data transmission to members of a group
US5608726A (en) * 1995-04-25 1997-03-04 Cabletron Systems, Inc. Network bridge with multicast forwarding table
US5805825A (en) * 1995-07-26 1998-09-08 Intel Corporation Method for semi-reliable, unidirectional broadcast information services
JP2897711B2 (ja) * 1996-02-05 1999-05-31 日本電気株式会社 伝送制御システム
US5905871A (en) 1996-10-10 1999-05-18 Lucent Technologies Inc. Method of multicasting
US6154463A (en) 1997-08-26 2000-11-28 Lucent Technologies, Inc. System and method for multicast conferencing and online discussion groups
US6163810A (en) * 1998-06-02 2000-12-19 At&T Corp. System and method for managing the exchange of information between multicast and unicast hosts
EP1018240A1 (fr) 1998-06-30 2000-07-12 Sun Microsystems, Inc. Optimisation dynamique dans un protocole de multidiffusion fiable
US6515994B1 (en) * 1998-07-30 2003-02-04 Lucent Technologies Inc. Method of communication in a communications network and apparatus therefor
US6269080B1 (en) 1999-04-13 2001-07-31 Glenayre Electronics, Inc. Method of multicast file distribution and synchronization
US6208647B1 (en) * 1999-04-14 2001-03-27 Verizon Laboratories Inc. Multicast extension to data link layer protocols
US6917985B2 (en) * 2000-03-10 2005-07-12 The Regents Of The University Of California Core assisted mesh protocol for multicast routing in ad-hoc Networks
US6963972B1 (en) * 2000-09-26 2005-11-08 International Business Machines Corporation Method and apparatus for networked information dissemination through secure transcoding
JP2004529538A (ja) * 2000-10-26 2004-09-24 ジェネラル・インスツルメント・コーポレーション マルチメディアコンテンツのためのコンテンツの権利および条件の実施
US6865167B2 (en) * 2001-02-02 2005-03-08 Telcordia Technologies, Inc. Method and system for soft handoff in wireless code division multiple access (CDMA) internet protocol (IP) networks
US6999465B2 (en) * 2001-02-22 2006-02-14 Motorola, Inc. Methods for reliably sending IP multicast packets to multiple endpoints of a local area network
US6677864B2 (en) 2002-04-18 2004-01-13 Telefonaktiebolaget L.M. Ericsson Method for multicast over wireless networks
US6970698B2 (en) * 2002-07-23 2005-11-29 Sbc Technology Resources, Inc. System and method for updating data in remote devices
US20060154603A1 (en) * 2002-09-07 2006-07-13 Joachim Sachs Method and devices for efficient data transmission link control in mobile multicast communication systems

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0959635A1 (fr) * 1998-05-20 1999-11-24 Alcatel Téléchargement de logiciel vers des terminaux sans fil en mode sans connexion

Also Published As

Publication number Publication date
WO2004036827A1 (fr) 2004-04-29
GB2394386A (en) 2004-04-21
DE60330790D1 (de) 2010-02-11
ATE453976T1 (de) 2010-01-15
CN1689272A (zh) 2005-10-26
EP1552649A1 (fr) 2005-07-13
US7801165B2 (en) 2010-09-21
KR100683813B1 (ko) 2007-02-15
KR20050055010A (ko) 2005-06-10
AU2003265058A1 (en) 2004-05-04
US20060034313A1 (en) 2006-02-16
GB0224076D0 (en) 2002-11-27
CN100571145C (zh) 2009-12-16

Similar Documents

Publication Publication Date Title
EP1552649B1 (fr) Transfert de données multidestinations
US7536622B2 (en) Data repair enhancements for multicast/broadcast data distribution
CA2553069C (fr) Identification et retransmission de parties tronquees
KR100831654B1 (ko) 멀티캐스트 및 브로드캐스트 전송을 관리할 수 있는시스템에서 데이터 복구 방법
EP1604477B1 (fr) Transmission de donnees avec des informations de correction d'erreurs sans circuit de retour
US20050216472A1 (en) Efficient multicast/broadcast distribution of formatted data
US20020133615A1 (en) Nack suppression for multicast protocols in mostly one-way networks
EP1730870B1 (fr) Correction de donnees pour distribution de donnees de diffusion/multidiffusion
EP1543701B1 (fr) Transfert de donnees multidiffusion
KR100711829B1 (ko) 멀티캐스트 데이터 전송
MXPA06009229A (es) Metodo de reparacion de datos en un sistema capaz de manejar transmisiones de multidifusion y radiodifusion
MXPA06011288A (en) Data repair enhancements for multicast/broadcast data distribution

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20050302

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20060627

17Q First examination report despatched

Effective date: 20060627

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/18 20060101AFI20090717BHEP

RTI1 Title (correction)

Free format text: MULTICAST DATA TRANSFER

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 60330790

Country of ref document: DE

Date of ref document: 20100211

Kind code of ref document: P

REG Reference to a national code

Ref country code: NL

Ref legal event code: T3

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091230

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091230

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091230

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091230

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100430

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100410

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091230

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100330

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091230

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091230

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091230

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091230

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100331

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091230

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20100920

Year of fee payment: 8

26N No opposition filed

Effective date: 20101001

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091230

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100930

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20110531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100930

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100930

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100924

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20110924

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100701

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100924

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091230

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20120919

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20120919

Year of fee payment: 10

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20120908

Year of fee payment: 10

REG Reference to a national code

Ref country code: NL

Ref legal event code: V1

Effective date: 20140401

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20130924

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 60330790

Country of ref document: DE

Effective date: 20140401

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130924

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20140401

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20140401